On Sun, Apr 6, 2008 at 12:24 PM, Sam Clemens
The Sunday 2008-04-06 at 11:39 -0400, Larry Stotler wrote:
that can cause kernel panics during boot if the SCSI drive was supposed to be sda and had been bumped. I wish they had used a different drive type for SATA, even tho it's basically like SCSI anyway. Oh well.
SATA can hook up to a SAS (serial attached SCSI) controller, but SCSI has a larger command set.
I've heard that, but I don't have any SAS drives to play with.
Basically, this current method can be convenient in some circumstances (replacing SATA disks with SAS disks) ...and annoying in many others (when you really do want to differentiate between your SCSI disks and your non-SCSI disks.... plus the new ridiculously low partition limit being blindly applied to both.
I generally don't use more than a few partitions, so that's not an issue for me. My son's Powerbook G3 Wallstreet uses more partitions than anything else I have(11 IIRC), mostly due to MacOS. The Linux system uses 4 - /, /files(storage), /boot(shared as a ProDOS with MacOS for kernel to be available to BootX under MacOS, and the swap partition.
The kernel devs must have been on drugs the month they merged that in without doing some basic sanity checking (is this a real SCSI disk, or a SATA disk?... figure it out by probing the hardware with the sg (generic scsi) device, and then choose a real device (SCSI or SATA) accordingly. ARG!!!
That's what happen with the anacronym guys come up with names that start with the same stuff. oh well. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org