devfs
[Top] [All Lists]

Re: Error on boot and host0 business

To: Robert <racsw@xxxxxxxxxxxxxxx>
Subject: Re: Error on boot and host0 business
From: Steven Lembark <lembark@xxxxxxxxxxx>
Date: Tue, 14 Jan 2003 22:52:00 -0600
Cc: Devfs <devfs@xxxxxxxxxxx>
In-reply-to: <1042584159.3198.88.camel@localhost.localdomain>
References: <1042557538.2868.6.camel@localhost.localdomain> <199790000.1042575133@[192.168.200.4]> <1042584159.3198.88.camel@localhost.localdomain>
Reply-to: lembark@xxxxxxxxxxx
Sender: devfs-bounce@xxxxxxxxxxx


-- Robert <racsw@xxxxxxxxxxxxxxx>


Bug in your devfsd.comf file. Have you modified/added any
entries to it?


Nope, not at all. I had trouble with another issue before, and someone told me that I had to modify this file, but when I looked at it, it was so cryptic that I knew I didn't understand it well enough, and left it alone.

:-)


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

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