Hide

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

OpenID
or
Sign in Register

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Hide

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for:

Hide

News

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

Check if network cable is plugged in and working correctly

Terminal - Check if network cable is plugged in and working correctly
mii-tool eth0
2009-06-24 08:43:55
User: flart
6
Up
Down
Check if network cable is plugged in and working correctly

with 'mii-tool -w eth0' you can watch the interface for changes of the link status

Show sample output | Add to favourites | Report as malicious

Alternatives

There are 12 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

Hmm. I don't know, but I get a little problem with it on my laptop:

sudo mii-tool eth1

SIOCGMIIPHY on 'eth1' failed: Operation not supported

Does it not work on WiFi connections? (Probably a stupid question, since it says "network cable")

Comment by kaedenn 204 weeks and 3 days ago

mii is an acronym from the older days when an ethernet card could support multiple physical interfaces (as in twisted pair RJ-45, or coax) and there was a "medium independent interface" layer. I don't know why it doesn't work for your wireless interface, but I know you can use mii-tool to turn off autonegotiation on a wired link for example and force communication at 10 mpbs rather than 100 mpbs or 1gbps. It would save power just like CPU frequency scaling does.

Comment by bwoodacre 204 weeks and 3 days ago

sudo ethtool eth0

"mii-tool" comand was replaced by "ethtool" command.

Comment by Playload 204 weeks and 2 days ago

"mii-tool" is indeed pretty buggy and deprecated nowadays. "ethtool" is preferred. Especially when dealing with Gigabit NICs mii-tool is showing wrong information and doing the wrong thing on several brands of NICs.

Comment by Signum 204 weeks and 1 day ago

Your point of view

You must be signed in to comment.

Related sites and podcasts