devfs
[Top] [All Lists]

RE: modules.devfsd needs /dev/scsi/*/part* handling

To: "'Richard Gooch'" <rgooch@xxxxxxxxxxxxxxx>, "'Thierry Vignaud'" <tvignaud@xxxxxxxxxxxxxxxx>
Subject: RE: modules.devfsd needs /dev/scsi/*/part* handling
From: Borsenkow Andrej <Andrej.Borsenkow@xxxxxxxxxxxxxx>
Date: Thu, 24 Jan 2002 09:28:57 +0300
Cc: devfs@xxxxxxxxxxx
Importance: Normal
In-reply-to: <200201230533.g0N5XYv23380@vindaloo.ras.ucalgary.ca>
Sender: owner-devfs@xxxxxxxxxxx
> Thierry Vignaud writes:
> > Richard Gooch <rgooch@xxxxxxxxxxxxxxx> writes:
> >
> > >> Attached patch is against current Mandrake devfsd.conf. It works
just
> > >> fine here for SCSI; I'd appreciate anybody testing it for IDE. It
is
> > >> great because it means we can continue to use compatibility names
by
> > >> default without endless "hey, why it says no such device!"=20
> > >>
> > >> blockdev is garanteed to exist on Mandrake that is currently my
concern
> > >> :-)
> > >>
> > >> many thanks for idea (yes, sometimes you must really read TFM).
> > >
> > > Well, thanks, but since blockdev isn't available everywhere, I
can't
> > > really use it in a generic configuration file. However, I wonder
if
> > > blockdev is actually required. IIRC, merely opening the block
device
> > > should suffice to trigger media revalidation. Is this not the
case?
> > > What is blockdev doing that is special?
> > >
> > > Can you please try to use dd instead in your devfsd.conf file and
tell
> > > me if that works? An action like this:
> > >   EXECUTE dd if=$mntpnt/\1 of=/dev/null count=1
> >
> > this would add a dependancy on fileutils. as for mandrake, it's
> > required by basesystem package, so it's ok for us. should be the
> > same for rh & debian, but a check wouldn't hurt.
> 
> I'd first like to establish that this will actually work. Someone
> please try this and let me know.
> 

I am sorry I was off for several days.

Quick'n'dirty test works. I.e. if you boot without media and then insert
media and access it it works just fine (and that did not work before).

My concern is media revalidation. Blockdev forces partition table to be
reread while dd not (always). Specifically in case of Mandrake if you
use supermount on removable drive then supermount "steals" media changed
bit before partition code has chance to see it. I hope to get a closer
look at weekend.

Still as we officially do not support supermount for Zip/Jaz I guess dd
is just fine as general purpose example. We always can add
Mandrake-spefic patches here.

Thank you very much for your help.

-andrej

<Prev in Thread] Current Thread [Next in Thread>