Fabrice FACORAT wrote: > le sam 27-10-2001 at 20:40 Borsenkow Andrej a �crit : > >>Fabrice FACORAT wrote: >> >> >>>>/lib/dev-state is changed only when you change permission/modes or >>>>manually create file. It does not matter what is there. >>>> >>>> >>>so we must use the plain device name or else make sda4 in dev-state >>> >>> >> >>You realy do not understand? This will work only the first time ever. >>After media is ejected this is removed again. To add to confusion, when >>you eject using hardware button, Linux does not notice it immediately >>and does not remove link (so it looks "as if it works"); but if you >>eject programmatically, e.g. with eject command, link disappears. Now >>try to explain this to newbies. >> > > for me it is a bug and just a bug and until devfs is corrected ( or > kernel removable media detection ) we have to found a workaround.
It is the wrong list for this. You have to discuss this wit Richard Gooch (we may of course discuss it here as well, but t won't change anything). Actually this was discussed already. > In all HOWTO they just say : mount your zip to sda4 and that's all > I'm not going to say : mount it with /dev/scsi/host1/bus0/target0/lun0 Why? Contribute to howtos and say that in case of devfs you better do this. > So my question is ( I not longer have a zip drive ) does making the > device /dev/sda4 in /lib/dev-state solve the problem ? No. ( Even if we forget that existence of /lib/dev-state creates other problems). if not, is there > a way to make devfs not handle zip drive ? > or patch zip driver subsyteme to make it act as supermount ? > I do not understand it. What has it to do with supermount? -andrej
