On Sat, 27 Oct 2001 16:03:17 +0200
Fabrice FACORAT <[EMAIL PROTECTED]> wrote:

> Le Samedi 27 Octobre 2001 15:19, Charles A Edwards a �crit :
> 
> > I just did not remember seeing anything that matched my USB Zip behavior
> > since I am able to mount and umount at will as long as I boot with a disk
> > in the drive 
> 
> as for the ide drive.


The ide zip I can boot without a disk in the drive and an able to mount
and umount at will.
 


> > and it is on a system that because of its location I do not us
> > as much as the system with the ide zip.
> >
> > Keeping a disk in the drive during boot creates no problems and in itself
> > is an easy enough fix.
> 
> and what about doing the device manually in /lib/dev-state ?


I have another bit of strangeness for you.
Look at the following terminal output:

[charles@localhost .gnome-desktop]$ mount /mnt/zip
mount: special device /dev/sda4 does not exist
[charles@localhost .gnome-desktop]$ su
Password: 
[root@localhost .gnome-desktop]# mount /dev/sda4 /mnt/zip
mount: special device /dev/sda4 does not exist
[root@localhost .gnome-desktop]# mount /dev/sda /mnt/zip
mount: you must specify the filesystem type
[root@localhost .gnome-desktop]# exit
exit
[charles@localhost .gnome-desktop]$ mount /mnt/zip
[charles@localhost .gnome-desktop]$ umount /mnt/zip
[charles@localhost .gnome-desktop]$ mount /mnt/zip
[charles@localhost .gnome-desktop]$ 

I boot the system with no disk in the USB zip so of course could not mount it with 
mount /mnt/zip then when I su to root and try to mount /dev/sda /mnt/zip I get the fs 
type error.
At this point I exit back to user and can now mount and umount the disk
and then mount a different disk.

/lib/dev-state/scsi/host1/bus0/target0/lun0 remains enpty but
/dev/scsi/host1/bus0/target0/lun0 contains the block device entries disc and part4.


   Charles


   Charles




 



Reply via email to