Date: Tue, 19 Dec 1995 21:10:46 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: freebsd-hackers@freebsd.org (FreeBSD hackers) Subject: Re: General comments on 2.1 install Message-ID: <199512192010.VAA04805@uriah.heep.sax.de> In-Reply-To: <16718.819371781@time.cdrom.com> from "Jordan K. Hubbard" at Dec 19, 95 03:16:21 am
next in thread | previous in thread | raw e-mail | index | archive | help
As Jordan K. Hubbard wrote: > > Gee, guys, I've covered this a couple of times before. I can't launch the > shell until I chroot or I lose the floppy. I can't chroot until I've got a > reasonable enough environment to chroot *to* or it's kinda pointless! > > That's why it makes the most sense to chroot after I have the root > floppy. Yes, I agree it's a pain. Give me some fix for the problem > that clamps down on the root floppy and I'll happily fork off the EHS > any time you like! What's the exact error that's returned? I could think of two problems: The mounted floppy still has device nodes that are open. In this case, forcibly unmounting (umount -f, or unmount(..., MNT_FORCE)) would help. OTOH, i don't have a clue how the mfs_root mount is accomplished. Perhaps it's shadowing the mounted (by the boot process) floppy? In this case, i don't think there's a quick fix. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512192010.VAA04805>