After you added those lines to your /etc/devfsd.conf , or uncommented them,
did you then do a mknod of the various character devices that VMware makes,
and others, into the /dev-state directory? ie,
mknod /dev-stat/crazy-vmware-char-dev [{bc} p] major minor
corleyja@xxxxxxxxxxxx wrote:
>
> Sadly, those lines are in my /etc/devfsd.conf file. No dice, especially
> with the devices VMware creates (various character devices) and no luck
> if I create, say a /dev/pilot symlink which points to /dev/usb/tts/1. Don't
> know what the deal is, but it saves permissions just fine. Just won't save
> new devices. Oh well. I stand by my assertion that devfs is poorly
documented.
> Do you know how long it took me to figure out that "mount -t devfs" is
> no longer correct? Probably longer than it should've I'll admit, but I
> figured the guy knew what he was talking about, he wrote the freaking thing.
> *sigh*
> Jason
>
> At 19 Jan 2001 19:08:59 EST, Brian Rossmeisl <brossmeisl@xxxxxxx> wrote:
>
> >
> >I don't mind you ranting. I appreaciate the info on the pcmcia-cs stuff,
> > it
> >was right in front of my face and I didn't think about it :), but to
> >get
> >devices to appear after a reboot you have to add a couple of lines of
> >options
> >to the /etc/devfsd.conf.
> >
> >REGISTER .* COPY /dev-state/$devname $devpath
> >CHANGE .* COPY $devpath /dev-state/$devname
> >CREATE .* COPY $devpath /dev-state/$devname
> >
> >this will copy any custom devices you have made in the /dev-state directory
> >to
> >the dev directory when devfsd starts, I could do that for my specific
> >PCMCIA
> >devices I have on my laptop, but I am still interested in seeing if
> >I can get
> >it working automaticaly, since I change machines & hardware quite often.
> >
> >corleyja@xxxxxxxxxxxx wrote:
> >>
> >> I don't mean to sidestep your point here, but could you do me a favor
> >if
> >> it's not too much trouble? It'll confirm a suspicion of mine. Create
> >a
> >> symlink, character device, whatever in /dev while devfs is running.
> > Reboot.
> >
> >> If it's still there when the box comes back up, tell me everything
> >you've
> >> done to set up devfs. Otherwise, I suspect you are like I was, in
> >that
> >> you think devfs is working until you need to do something (VMware
> >is a great
> >
> >> example of something that won't work across reboots due to this /dev
> >mangling).
> >> I'm not bashing devfs, I really like it, but I think a lot of people
> >(myself
> >> at the very head of this list) think they have it running when in
> >fact they
> >
> >> don't.
> >>
> >> Having not run PCMCIA on a box (no laptop) I would hazard a guess
> >that you
> >> need to enable the hotplug stuff in the kernel and then change all
> >the
> >device
> >> names manually, if possible. The PCMCIA web page
> >(http://pcmcia-cs.sourceforge.net)
> >> might be a good place to look for compatibility issues with devfs.
> >>
> >> Sorry for ranting at you,
> >> Jason
> >>
> >> At 19 Jan 2001 00:26:00 EST, Brian Rossmeisl <brossmeisl@xxxxxxx>
> >wrote:
> >>
> >> >
> >> >I am running slackware 7.2beta, and a 2.4.0 kernel, I am running
> >devfs
> >> >and
> >> >loving it, I have migrated most everything over to the new nameing
> >scheme,
> >> >except my /etc/pcmcia directory, the files in there make specific
> >calls
> >> >to
> >> >/dev/$device and such. So how do I get around this? any suggestions?
> >> >I was
> >> >thinking about making a /dev-stable/? directory and putting the devices
> >> >I
> >> >specificly need in there, but I figured someone would know of a better
> >> >way so
> >> >if I set it up on something other than my personal laptop I wouldn't
> >> >have to
> >> >be a super sleuth :)
____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1
|