reg@xxxxxxx wrote:
>
> I ran ver_linux on the two systems (actually diferent partitions on the same
> box), and the results along with your results are below. In all cases your
> versions are later than mine.
unfortunately things are so different I can't draw any conclusions...as to what
changed/broke.
me thinks that if devfsd is going to be publicly accepted w/ 2.4.X series
kernels
that it should compile out of the box with the latest stuff..
>
> HOWEVER, please note that my problem was with COMPILING devfsd, not running
> it (havent got that far yet), It would seem that some of the include files
> in the RH7.0 system are wrong (or at least different), and caused my problem.
Me too, devfsd won't compile!!!
I had to add this to devfsd.c
# define RTLD_NEXT ((void *) -1l)
that I yanked out of dlfcn.h
My guess is that it has something to do with glibc 2.1.X and later...
but I really haven't a clue...Richard Gooch would know but a direct
e-mail to him gathered no response.
So now it compiles, yeah there are probably other ways to do this and
probably more correct... but I wanted to play with devfsd and see what
it can do. It more or less works but Seg faults when I have GLOBAL
in the devfsd.conf file.
Do anyone have any idea what/where the following may be found (from man page)
REGISTER mydir/mydev CFUNCTION GLOBAL >>>symlink<<< $devname
mydev
UNREGISTER mydir/mydev CFUNCTION GLOBAL >>>unlink<<< mydev
wtf are the symlink/unlink functions? or are they symlink(2)/unlink(2)?
If I add anything with a CFUNCTION GLOBAL as in the cdrom example in the manpage
devfsd Seg. faults. on start up.
I wish there were a better description of what MFUNCTION/CFUNTION GLOBAL etc
does/is. Maybe a few examples of code/scripts cause the FAQ sucks in this
regard.
Some more working examples and descriptions would sure be nice!
What I want to do is, if there is a lookup on /dev/tty1 then I want devfsd to
create the symlink, when that reference goes away I want the tty1 symlink to
disappear.
REGISTER vc/.* MKOLDCOMPAT builds all kinds of crap in /dev that I don't want
to see.
(whats the point of going with a devfsd if that kind of name space pollution
occurs?)
right now most everything on my system has been converted to devfs naming
conventions
but there are still a few progs that want the old stuff...vmware etc. so I've
built
the symlinks in rc scripts, but i'd much rather devfsd do it on demand.
Martin
--------------------------------------------------------------------------------------
just a free loader using all this good/not so good GNU software that hasn't
a clue sometime (this time and more often than not)
|