On Fri, 18 Feb 2000, Richard Gooch wrote:
> Khimenko Victor writes:
> >
> >
> > On Fri, 18 Feb 2000, Richard Gooch wrote:
> >
> > > Khimenko Victor writes:
> > > > In <38AB518A.9D61228C@isn.net> Garst R. Reese (reese@isn.net) wrote:
> > > > > I have followed with some interest the saga of devfs.
> > > > > Complete with radical activists vs. Peter's questions of "what's it
> > > > > for?"
> > > > > Richard's patient explanations, and devoted support with timely patches.
> > > > > There is a big time lesson here for people with a strong belief in their
> > > > > idea.
> > > > > Hat's off to Richard Gooch for his persistance and also to hpa.
> > > > > There are many lessons here for contributors.
> > > > > Garst
> > > > > 46-5
> > > >
> > > > What should be done now is to clean up all stuff. Gooch done
> > > > everything he can himself. Now when devfs is part of official kernel
> > > > it's time to polish up devfs further. For example situation with ZIP
> > > > drives does not look right to me. When there are no zip disk in
> > > > drive and module is not loaded there are no
> > > > /dev/ide/host0/bus1/target1/lun0/part4 . If I'll put zip disk in
> > > > driver and will try to mount it ide-floppy will be loaded and
> > > > mounted. So far so good. The bad thing happens when I try to mount
> > > > zip disk when there are NO zip disk in drive. Then only
> > > > /dev/ide/host0/bus1/target1/lun0/disc is created, not
> > > > /dev/ide/host0/bus1/target1/lun0/part4 :-(( So even if I'll put zip
> > > > disk in drive I can not mount it :-((
> > > >
> > > > IMO right way to deal with this situation is to add some "rescan"
> > > > function in devices. So you can force rescan of attached devices
> > > > without driver unloading and loading again. This problem exists
> > > > there without devfs (if I turn my SCSI scanner after system reboot I
> > > > can not use it -- I need to restart system), devfs just make it more
> > > > pervasive...
> > >
> > > Devfs already has a rescan facility. SCSI and IDE removable drives are
> > > using this. Someone should look at the IDE subsystem and figure out
> > > if and why this isn't working. I can't test it myself.
> > >
> > How it should be iniciated ? It should be done by devfsd when I try
> > to access /dev/ide/host0/bus1/target1/lun0/part4 if it's not there
> > -- what I should write in devfsd config file to do so ?
>
> For now, something like:
> LOOKUP ide/host0/bus1/target1/lun0/part. MODLOAD <whatever>
>
> should work. I'll think about something more elegant.
>
I'm missing something or what ? How MODLOAD can help here ??? ide-floppy
was ALREADY in memory for the same /dev/ide/host0/bus1/target1/lun0/disc !
I can access the whole disk just fine. I just can not mount it: there was
no partitions on disk when driver was loaded and rescan occured so there
are no /dev/ide/host0/bus1/target1/lun0/part4 ... If I fire up
fdisk /dev/ide/host0/bus1/target1/lun0/disc
and type "w" then right thing happens: part4 created and I can access it.
Or I can do
mknod /dev/ide/host0/bus1/target1/lun0/part4 b 22 68
and then mount my ZIP disk but both things looks ugly :-/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:19 EST