Comments on: Blind leading the blind

By: thedude

thedude — Thu, 18 Mar 2010 20:13:05 +0000

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.

By: g pay

g pay — Fri, 05 Mar 2010 23:02:35 +0000

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.

By: stoictimebender

stoictimebender — Sat, 16 Jan 2010 19:53:02 +0000

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.

By: james

james — Sun, 06 Dec 2009 09:07:48 +0000

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.

By: Command Line Idiocy | A chronicle of Ubuntard stupidity.

Command Line Idiocy | A chronicle of Ubuntard stupidity. — Sat, 05 Dec 2009 21:49:48 +0000

[...] is a follow-up to “Blind Leading the Blind“, as another piece of monumental idiocy has stepped up to the [...]

By: Thomas Prescott

Thomas Prescott — Sat, 24 Oct 2009 21:50:26 +0000

“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.

By: Karmic Koala: The Trainwreck Around the Bend | A chronical of Ubuntard stupidity.

Thu, 03 Sep 2009 04:11:09 +0000

[...] gems tucked away for a later date, but these serve to illustrate the point. They’re just the blind leading the blind. 3 September 2009 [...]