Solaris uses a numbering scheme based on the scsi controller, target, disk (in case of bridge boards that may have more than one disk on the same target, or scsi id) and partition (or slice). Specifically, /dev/dsk/c0t0d0s0 refers to the first partition on the first disk on the first target on the first controller, etc. On the other hand, Data General Unix, dgux, requires each disk to have a "name" that is user configurable. The operating system creates the device nodes for the logical disks on the fly as part of the boot process, under paths such as /dev/dsk/YourNameHere. This means that regardless of what relative order, scsi id or controller, each drive gets mounted the same.
Jonas Bofjall wrote: > > On Sat, 3 May 1997, Dave Cinege wrote: > > > This is what caused me to finally break linux. I moved OpenDOS from a > > primary (sda2) to a logical (sda5). > > I know Solaris numbers disks differently, I think it is based on the disks > serial number. A very good solution, however, you get away from this sort > of problems. This is a good reason the Linux kernel should have a > dev-filesystem, much like the proc-filesystem is implemented in the > kernel. I've seen it has been on the 'Linux Kernel Wishlist' for a while, > and I have heard that its being worked on FreeBSD. > So, start kernelhacking :) ! > > // Jonas <[EMAIL PROTECTED]> [2:201/262.37] > -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
