Use sed to color the output of a human-readable dmesg output
Much more useful then parsing syslog
this is helpful because dmesg is where i/o errors, etc are logged to... you will also be able to see when the system reboots or someone attaches a thumb drive, etc. don't forget to set yourself up in /etc/aliases to get roots email.
Check SATA controller type. 6.0 Gbps - SATA III 3.0 Gbps - SATA II 1.5 Gbps - SATA I Show Sample Output
Btrfs reports the inode numbers of files with failed checksums. Use `find` to lookup the file names of those inodes. The files may need to be deleted and replaced with backups.
Info about Bluetooth devices. Show Sample Output
The dmesg will show the kernel it is booting. No more dependency on files Show Sample Output
follow/wait for new kernel messages similar to `tail -f` available since util-linux 2.22.
dmesg -t: no timestamp -W: follow new messages -l: log-level notice gawk if the fourth word is "Attached" echo a sentence through espeak
Btrfs reports the inode numbers of files with failed checksums. Use `find` to lookup the file names of those inodes.
get cpu info from dmesg
commandlinefu.com is the place to record those command-line gems that you return to again and again. 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.
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
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: