No idea if this works on SATA, but there is an sdparm.
http://sg.torque.net/sg/sdparm.html
--
Archaic
Thanks. I've been playing with that. Actually some of hdparm still
works, the error messages are expected and apparently harmless. Sdparm
has no benchmark option. There are kernel
alter /etc/fstab - everything else should be OK I think?
Well, I could attempt to read your mind to determine what you are
subconsciously worrying about, but I think I'll just say
yes :) Oh, root= for your bootloader will need to refer to sdaX.
See - it was worth asking! I would have
Of Ken Moffat
I think this *might* be controlled by one of the SCSI
transport options
- there is some sort of deprecated option that conflicts with
SATA, but I'm on a ppc at the moment and I can't see it.
I'd noticed this deprecated option (conflicts with libata) but never
bothered to
Solved. I'm not sure if anybody felt the answer was too obvious - if so I
apologise. But it's not an answer I came across anywhere else and shells don't
work the way I thought they did.
The problem was a simple error in /etc/passwd - my userid didn't have the
default shell specified
First I thought I had some bad configuration, or maybe permissions
problem because I'm using package users. But several builds
later, the
issue persist. Got a feeling either not much people use NFS
anymore, or
noone really care too much about it..
--Tor Olav
Don't feel
Does she still need to use
smbmount to access my /pub/songs directory, or is there some
other means of addressing resources on a host when you have a
Linux-to-Linux connection? I'm not talking about copying
files, but opening them in-place on the server.
You'll get more experienced
