Just a wild idea... what kernel are you using?
Is this a problem you always had or something new?
I had the idea that the thread on this list started
by David Fokkema on the 17th of December might be
related to your problem.
At the end of the thread David reported that kernel
2.4.20 solved his problem of not being able to refer
to the disc0 device link as root device, only the
ide/host0/.../... full specification. In 2.4.18
only the full path can be specified, but in 2.4.20
the simplified name could be used too.
I haven't seen 2.4.20 yet so can't tell, but it is
possible that the simplified symlink is not behaving
exactly the way it used to and this way the symlink
and unlink actions of devfsd will fail.
Again, this was just a wild idea.
Ignore it if you want to.
Marton
----- Original Message -----
> >
> >
> > Less cryptic than it might seem at first glance. Trick
> > is to start from a working example. e.g., here is the
> > entry for my tape drive. "/dev/tapes/tape0/mt" is what
> > I want "/dev/tape" to look like. Paths are relative to
> > /dev/ (or whatever your mount point is). You can LOOKUP
> > a new device, REGISTER the "real" device as the "standard"
> > device or UNREGISTER the device. From there the logic is
> > not all that complicated:
> >
> > LOOKUP ^tape$ CFUNCTION GLOBAL
> > symlink tapes/tape0/mt tape
> > REGISTER ^tapes/tape0/mt$ CFUNCTION GLOBAL symlink tapes/tape0/mt
> > tape
> > UNREGISTER ^tapes/tape0/mt$ CFUNCTION GLOBAL unlink tape
> >
> >
> > Either way, you still have a bug in your devfsd.conf file.
> >
> > --
> > Steven Lembark 2930 W. Palmer
> > Workhorse Computing Chicago, IL 60647
> > +1 773 252 1080
>
> I know I didn't modify anything, but with your information, let me look
> that file over and get back to you. Thanks for helping out, regardless.
>
> --
> Robert <racsw@xxxxxxxxxxxxxxx>
--
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup
Meet Singles
http://corp.mail.com/lavalife
|