How does one provide one or two devices, e.g. /dev/null
for a chroot environment?
Device nodes created by mknod do not work.
mount_devfs creates an entire device tree, negating
the security of the chroot.
___
freebsd-questions@freebsd.org mailing list
On Thu, Dec 15, 2005 at 07:18:11PM +, Dieter wrote:
How does one provide one or two devices, e.g. /dev/null
for a chroot environment?
Device nodes created by mknod do not work.
mount_devfs creates an entire device tree, negating
the security of the chroot.
See the jail manpage (jail
On Aug 11 at 17:33, Henrik W Lund spoke:
I may be wrong here, but I think that in the 5.x system, /dev is
populated at boottime, courtesy of the GEOM layer and the devfs
filesystem. These two operate together, GEOM detecting hardware and
giving it proper device nodes in the special devfs
to build the kernel (with a different configuration) fails.
A regular file /dev/stdout has been created.
What is the recommended way to create the device nodes in /dev in a
chroot environment?
-Hanspeter
___
[EMAIL PROTECTED] mailing list
http
/rc.d/dev*. This only created a
/dev/null.
Trying to build the kernel (with a different configuration) fails.
A regular file /dev/stdout has been created.
What is the recommended way to create the device nodes in /dev in a
chroot environment?
This isn't a direct answer to your question
a
/dev/null.
Trying to build the kernel (with a different configuration) fails.
A regular file /dev/stdout has been created.
What is the recommended way to create the device nodes in /dev in a
chroot environment?
-Hanspeter
Greetings!
I may be wrong here, but I think that in the 5.x system, /dev
On Aug 11 at 11:25, Bill Moran spoke:
Hanspeter Roth [EMAIL PROTECTED] wrote:
What is the recommended way to create the device nodes in /dev in a
chroot environment?
This isn't a direct answer to your question, but it should help you
work around your problem.
After booting the CD
Henrik W Lund wrote:
Hanspeter Roth wrote:
[...]
What is the recommended way to create the device nodes in /dev in a
chroot environment?
-Hanspeter
[...]
So, messing with device nodes in a chrooted 5.x system is not possible
(someone correct me here, if I'm wrong).
It is possible to customise
