I believe hdparm is actually a utility to set the kernel parameters.
That is why, for instance, when the ata100 driver first appeared in the
kernel, there was a new hdparm to use to enable it.
You can also get around the whole thing by passing kernel options at
boot, like "ide0=dma", which is what I use on my custom kernel with
udma66.
Buchan
b5dave wrote:
>
> Alex wrote
>
> > I have the following at the end of rc.local
> >
> ># hdparm stuff
> > echo -n "Harddrive optimizations"
> > /sbin/hdparm -c 1 -d 1 -k 1 /dev/hda
> > /sbin/hdparm -c 1 -d 1 -k 1 /dev/hdb
> > /sbin/hdparm -c 1 -k 1 /dev/hde
>
> and .....
>
> Bill wrote:
>
> >I've got mine as the last line of rc.sysinit. It works.
>
> Well if either one of you guys says that the install did indeed append
> that to either script, then that makes my initial question about a
> possible kernel parameter moot, and that's one more mystery solved. I'm
> perfectly happy with that. :-)
>
> ps Bill. Is that x-vcard attachment a *nix thing? I think I may have got
> one recently from an associate and flamed them for sending me yet another
> proprietary M$ attachment. OOPS!
>
> ---------
> 21-Dec-2000
> 22:30:11
> ---------
