For "Device File System", Debian "devfsd" package, how might I test that "devfsd" properly creates files in /dev?
As a particular example, I work with the Debian "camserv" package,
so I added to devfsd's configuration file,
/etc/devfs/devfsd.conf
the line,
REGISTER ^v4l/video0$ CFUNCTION GLOBAL symlink v4l/video0 video0
When starting "camserv", I get the not so specific error message,
(V4L) video_open: No such file or directory
Unfortunately, this message does not specify the problematic file,
but I get neither the device /dev/v4l/video0 nor /dev/video0.
So, with several possible sources for this error
(camserv, devfsd, devfsd.conf),
I would like to test that "devfsd" properly creates devices in /dev.
For example, I would like some testing-tool that my command line
*** some-testing-tool /dev/video0
would induce "devfsd" to consider devfsd.conf, then create the following
device and link,
/dev/v4l/video0
/dev/video0 --> v4l/video0
Such a testing-tool would hopefully induce "devfsd" to create
any specified device, whether concerning video, audio, or mass-storage.
*** Does anyone know of such a "devfsd" testing-tool?
PS: I would address this question to a devfs email-list,
but the author's email-list site,
http://oss.sgi.com/projects/devfs/archive
no longer exists, and I find no replacement.
--
Jameson C. Burt, NJ9L Fairfax, Virginia, USA
[EMAIL PROTECTED] http://www.coost.com
(202) 690-0380 (work)
msg26076/pgp00000.pgp
Description: PGP signature
