thats been one of my pet peves since the begining, disks sould have a
volume id and mount commands should be able to use it, else bad things
happen when disks fail and the system reboots, say u have tmp mounted on
its own disk, the disk fails, system reboots as part of the boot up
procedure u rm -r /tmp/* to clean up, oops there goes the disk that
replaced tmp, only work around now is to make sure those types of disk
are last easier said the done, not sure what would happen it the disk was
part of a raid device
i
advantages can change scsi ids any time u want to whatever u whant, can
have a removable mo dive, dvd ram drive as first device and the system
will still work corectly or at least a hell of alot better than it does
now (gave up on that idea)
My opinions are my own and not that of my employer even if I am self employed
On Tue, 21 Mar 2000, Stanley Wu wrote:
> Thanks for sharing the info. It appeared Linux is a
> bit different in the device configuration. I have a
> couple questions:
> 1. Is there a kernel function call, from the driver,
> equivalent to "mknod" command?
> 2. How can I ensure the /dev/XXXn device remain
> consistent throughout reboots? It appears to me if I
> have handful of devices, some of them are powered off
> during reboot; I could be dealing with a different
> device while /dev/XXXn is the same
> Thanks
>
>
> __________________________________________________
> Do You Yahoo!?
> Talk to your friends online with Yahoo! Messenger.
> http://im.yahoo.com
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
