[lkml]   [2001]   [Mar]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.4.2 ext2 filesystem corruption ? (was 2.4.2: What happened ? (No
Alan Cox wrote:
> > I'm not arguing it was a smart thing to do, but I would think that the
> > fs/kernel/driver writers could keep really nasty and un-expected things
> > from happenning. For instance, the driver could dis-allow any new (non-hdparm)
> Like stopping root from using rm -r ? Where is the line drawn

rm -r does not do un-expected things, and it does not corrupt your file
system, it merely removes it. That is the only thing it does, and it
does it every time.

However, messing with the hdparms options can do random things, at
least from my perspective as a user: It may bring exciting new performance
to your system, and it may subtly, or not so, corrupt your file system.

If the drivers can detect what type of HD/chipset we are using, surely
it can know not to allow the user to do stupid things that are out of
spec w/regards to the hardware?

For the power/insane user, there could be a --really-do-stupid-thing-i-told-you-to
option, and it should be that hard to type!!


Ben Greear (
Author of ScryMUD: 4444 (Released under GPL)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:29    [W:0.039 / U:8.800 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site