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
Hello,
I have built a new kernel on a FreeBSD 5.2 system which doesn't boot
anymore. So I took a Freesbee and mounted the filesystems from the
harddisk and changed root to the harddisk's one. But there were no
devices in /dev. I tried some of /etc/rc.d/dev*. This only created a
/dev/null.
Trying
Hanspeter Roth [EMAIL PROTECTED] wrote:
Hello,
I have built a new kernel on a FreeBSD 5.2 system which doesn't boot
anymore. So I took a Freesbee and mounted the filesystems from the
harddisk and changed root to the harddisk's one. But there were no
devices in /dev. I tried some of
Hanspeter Roth wrote:
Hello,
I have built a new kernel on a FreeBSD 5.2 system which doesn't boot
anymore. So I took a Freesbee and mounted the filesystems from the
harddisk and changed root to the harddisk's one. But there were no
devices in /dev. I tried some of /etc/rc.d/dev*. This only created
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
