Blind leading the blind
21 March 2009 in UncategorizedOne of the problems many veteran users have with the rise of Ubuntu is how message boards and communities get polluted with the clueless new users. Don’t get me wrong, there’s nothing wrong with looking for a little help or offering some of your own knowledge. But the old adage holds water; one can know just enough to cause trouble.
That’s what happens in a lot of circumstances. Communities get filled with those who know just enough to lead the new user astray. At least check your advice before espousing your knowledge! This post is an excellent example of just that. It recently hit Digg and Reddit and no doubt ruffled a lot of feathers with its lame tips. Not only are many of those “50 ways to impress your geeky linux friends” just plain incorrect, they’re asinine. That post is the rambling of someone who’s just discovered wobbly windows and the command line. If it’s text-mode, it must be leet!
It’s the blind leading the blind, and it ain’t pretty.
Let’s take this author’s example of ripping a DVD:

What’s wrong with this?
- Encrypted DVDs will not be ripped with this command. All you’ll get is a logfile and STDERR filled with errors as your drive gets confused by the CSS studios use to encrypt their content
- The output file, for as far as it may get, is created in the root of the filesystem. Classy.
- No blocksize specified. Unless you’re willing to wait an eternity for your disc to rip, better crank up the BS option to a sane level. Lord knows this post has enough BS of its own…
The correct advice would be to make sure you have the De-CSS encryption cracking library installed and to use handbrake, or another such utility to get the content from the disk. The author mentions none of this. Likely result? A frustrated user, banging their head on their keyboard after some terrible advice.
But that’s not all — how bout this gem?

This is when bad advice gets dangerous. What’s wrong with this? From shred’s own –help output:
CAUTION: Note that shred relies on a very important assumption:
that the file system overwrites data in place. This is the traditional
way to do things, but many modern file system designs do not satisfy this
assumption. The following are examples of file systems on which shred is
not effective, or is not guaranteed to be effective in all file system modes:* log-structured or journaled file systems, such as those supplied with
AIX and Solaris (and JFS, ReiserFS, XFS, Ext3, etc.)
Oh, hey, how about that? shred is telling you in its own goddamn help output that it’s useless on journaled filesystems. What’s the default these days? Oh, yes… a journaled filesystem. Once again, the author fails to mention a very important caveat. Now there’s a false sense of security.
Another example of just enough information:

That command will accomplish one thing: a single html file downloaded to your system. What the author meant was no doubt something like this:
wget -m -p -np http://example.com/interesting_subsection/
Otherwise, you get none of the interesting content on the page, like… images, stylesheets, linked pages.
Oh, you want to disable root logins via SSH?

Since we’re all running GNOME and X on our servers, I guess gedit is fine… But guess what? Wrong file! /etc/ssh/ssh_config exists, but that’s not quite where you want to add that option. Try /etc/ssh/sshd_config. And don’t forget to restart sshd!
Well, maybe we should give the author some slack. After all, this is supposed to be impressive stuff. If I were looking over your shoulder, and I saw you perform this next act of god-like mastery, I don’t know how I’d react:

Yes. Holy shit. This is it. Mecca, you are found. Should we mention how to query your package manager for installed files from a particular app? Nah…
The net and social bookmarking sites are all littered with inane crap like this. 20 of the coolest command line utilities! 30 of the best alternative free software packages! 75 ways to jack off with a terminal for fun and profit! And most of them are utter drivel.
7 Comments to Blind leading the blind
Trackbacks / Pingbacks
Leave a comment
Subscribe to receive your Secret Decoder Ring!
- Wikipedia, Notability, and Open Source Software, Part 2
20 March 2010 - Wikipedia, Notability, and Open Source Software
17 March 2010 - Real Linux advocates see shades of grey.
8 December 2009 - Command Line Idiocy
5 December 2009 - Choosing an OS is Not a Team Sport
29 November 2009
- Steve:
I stumbled onto this blog while reading some of my normal "news" regarding the L... - Kris Gesling:
Sorry but I just to join the campaign for reason and logic but I couldn't stand ... - Amy:
haha.. Well. Good to see that ya're finally up and running again. :D And i prom... - Steve:
Having personally given up on any kind of volunteering in 2006 it should be note... - forkbomb:
I've given up on editing Wikipedia excepting those occasional situations where I...


“4. disable system beep
Linux insists on beeping at you; this isn’t just any beep, however–it is a system beep, impervious to the mute button on your computer. If the startling, abrupt sound is like nails raking over a chalkboard to you, then this trick will let you kill that little beep forever.
Type:
sudo rmmod pcspkr
…and enjoy the silence.”
Until you restart your box for whatever reason. You’ll want to add it to your /etc/modprobe.d/blacklist file.
# echo “blacklist pcspkr” >> /etc/modprobe.d/blacklist
Make sure you put >> or else bad things will happen.
Your advice on shred is misguided re ext3 in its default mode. Read the rest of the shred man page:
In the case of ext3 file systems, the above disclaimer applies (and shred is thus of limited effectiveness) only in data=journal mode, which journals file data in addition to just metadata. In both the data=ordered (default) and data=writeback modes, shred works as usual. Ext3 journaling modes can be changed by adding the data=something option to the mount options for a particular file system in the /etc/fstab file, as documented in the mount man page (man mount).
And from the mount man page:
Specifies the journalling mode for file data. Metadata is
always journaled. To use modes other than ordered on the root
file system, pass the mode to the kernel as boot parameter, e.g.
rootflags=data=journal.
journal
All data is committed into the journal prior to being
written into the main file system.
ordered
This is the default mode. All data is forced directly
out to the main file system prior to its metadata being
committed to the journal.
writeback
Data ordering is not preserved – data may be written into
the main file system after its metadata has been commit‐
ted to the journal. This is rumoured to be the highest-
throughput option. It guarantees internal file system
integrity, however it can allow old data to appear in
files after a crash and journal recovery.
Could you, (OP), then provide some links, perhaps, guiding people like me to sane and grounded sites for advice?
-stupid should hurt and leave a mark. that is what’s wrong with the world. we made stupid painless.
this elitist snobbery is why people stay away from Linux in droves, filling Microsoft’s bank accounts and continuing their brand of mediocrity. but i guess that’s exactly what you want, pretty sad though, that is certainly not what is best for the linux cause.
stick -> ass.
lighten up, this guy gave some nice ubuntu noob tips. OK, not all were pure brilliance but the ones you didn’t mention weren’t all bad. At least it’ll encourage some people to give it a go.