On Sat, Feb 07, 2004 at 07:57:55PM -0800, Marc Wilson wrote: > On Sun, Feb 08, 2004 at 12:07:26AM +0000, Svens wrote: > > <hdparm suicide deleted> > > Gee, let's turn another cluebie loose with a shotgun, and see if he can > zorch his data. > > Let's not find out what modes his drives actually support, and let's make > sure that the kernel can't reset it if it's wrong. Let's unmask > interrupts, without finding out if his hardware can deal with it. Let's > try to force DMA on, without finding out whether or not his kernel supports > his IDE chipset. > > Never mind that the kernel can do 90% of this on its own, and a wonderful > first step should *always* be finding out why it HASN'T. > > People who write hdparm HOWTOs need to be hung up by their toenails. I've > yet to read one that tried to be an even minimally responsible resource. > > > good luck > > Yeah, he'll need it.
To be honest, I tried what he said and got very little speedup. I did try "hdparm -c" and saw that by default I was doing -c0. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
