Re: devlinks: an alternative to devfs
Richard Gooch (rgooch@atnf.CSIRO.AU)
Fri, 9 Jan 1998 09:11:46 +1100
ketil@ii.uib.no writes:
> Kevin Lentin <kevinl@cs.monash.edu.au> writes:
>
> > Maybe I didn't quote enough. The problem being discussed was that if you
> > had devfs mounted twice you want a way to tell the system to not put new
> > devices in a chrooted devfs. I was suggesting a 'nocreate' option in the
> > devfs that effectively closes it. So when you create a chrooted filesystem
> > you can remove some devices you don't like, create a few you think might
> > turn up later that you do like and then 'close' the filesystem.
>
> But you want the devices that disappear during unloading of a kernel
> module to reappear when the module is reloaded. And you want to be able
> to mount/unmount the directory at will without having to run some script
> to configure the correct devices - don't you?
Yep, that's what we want. And that works now. In order for nodes to
appear in /gaol/dev (mounted with -o explicit), you have to manually:
# mknod <file> c 0 0
It doesn't matter if the device driver module was loaded before or
after the mknod: it all works as you'd want.
Regards,
Richard....