Craig Armour writes:
> > How is Devfs behaving towards chroot jailed environments?
> > I haven't tried to install one, as a matter of fact I am still using
> > old-fashion device file system for an apache server.
> > The problem is I must create another /dev entry within a separate directory
> > and I don't know how to relate it to devfs .
> > What is, so, the current state of things?
> >
> > Thanks
>
> try the following
>
> mount -t devfs devfs /chroot/dev
That will give you a whole devfs tree. Binding individual entries is
better if you want a restricted chroot gaol. For example, just bind
/dev/null and /dev/zero.
> this is in addition to your standard /dev tree and seems to work
> quite fine. I can not see any reason why it would not. Effectively
> ( but not quite ), /dev and /chroot/dev become carbon copies. I
> mounted /tmp/dev in this fashion and could successfully eject my
> cdrom useing both device trees. it would be interesting if two
> process' tried to access the same device through a different tree at
> the same time though. Could this be a problem that may need to be
> addressed?
No more so than if you access the same device via the same path from
two processes.
> You will have to play with devfsd.conf if you want different things to
> happen within /chroot/dev and /dev. Is it possible to have devices
> appear in /dev and not /chroot/dev? etc...
Yes, by selectively binding stuff in /dev to /chroot/dev.
Regards,
Richard....
Permanent: rgooch@xxxxxxxxxxxxx
Current: rgooch@xxxxxxxxxxxxxxx
|