Borsenkow Andrej <Andrej.Borsenkow@xxxxxxxxxxxxxx> writes:
> > > > > blockdev is garanteed to exist on Mandrake that is currently my
> > > > > concern
> > > > > :-)
> > > > Well, thanks, but since blockdev isn't available everywhere, I can't
> > > > really use it in a generic configuration file. However, I wonderif
> > > > 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
> >
> > 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.
but we can use blockdev too as it's always here (util-linux is required by
basesystem)
|