Date: Thu, 12 Aug 2004 15:52:12 +0000 From: Hanspeter Roth <hampi@rootshell.be> To: freebsd-questions@freebsd.org Subject: Re: FreeBSD 5, chroot and /dev Message-ID: <20040812155212.A24338@gicco.homeip.net> In-Reply-To: <411ABADD.3050702@broadpark.no>; from henrik.w.lund@broadpark.no on Wed, Aug 11, 2004 at 05:33:33PM -0700 References: <20040811151539.GA1658@gicco.homeip.net> <411ABADD.3050702@broadpark.no>
next in thread | previous in thread | raw e-mail | index | archive | help
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 filesystem (which is > mounted under /dev, if you check your fstab). Greetings! ok, I have shown the "short" paths as of the mounted harddisk. They should all be prefixed with /mnt/ufs.1/. So when a filesystem usually containing /dev is mounted the /dev directory becomes /mnt/ufs.1/dev. So this directory had no entries. A had then tried to create a few entries by hand which are then visible after `chroot /mnt/ufs.1'. > So, messing with device nodes in a chrooted 5.x system is not possible > (someone correct me here, if I'm wrong). What happens when you try to > boot it normally? Well, I had specified the wrong cpu type in the kernel konfig. I encountered some page fault and dropped to the debugger. I'm now about to 'upgrade' to 5.2.1-release and shall retry with the proper cpu type. -Hanspeter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040812155212.A24338>