Date: Sun, 5 Dec 2004 18:56:07 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Tim Kientzle <kientzle@freebsd.org>, Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: current@freebsd.org Subject: Re: [TEST/REVIEW]: rootfs mounting code rework Message-ID: <p0620073fbdd94a7e8beb@[128.113.24.47]> In-Reply-To: <41B34F8D.5030401@freebsd.org> References: <56325.1102236241@critter.freebsd.dk> <41B34F8D.5030401@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 10:12 AM -0800 12/5/04, Tim Kientzle wrote: > >Here's a situation that may be worth thinking about: > > * Working FreeBSD system that uses a > separate controller. / is /dev/da4. > > * Controller blows up. > > * Connect hard disk to the on-board controller. > >Note: kernel is now being loaded from /dev/da0, but /etc/fstab >still says / is /dev/da4. With the old rootfs code, this system >is unbootable. This is the kind of situation I was thinking of, where you get into a mess due to some hardware shuffling. It does not come up often, but it can be frustrating when you do run into it. I was just wondering if Poul's work might help in that situation. In a later message, Poul-Henning Kamp wrote: >First: I have _not_ changed the logic that decides _which_ rootfs >to mount, only the mechanics of how it is mounted. > >Second: I belive you could simply type something like: > > set vfs.root.mountfrom="ufs:/dev/da0" > >in the loader and your system would do what you expect it to. Ah, very good. I'll save that away for future reference. So with your changes, should we just check to see that it works the same as it used to work? Or is there any kind of new behavior that we should try to exercise? -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0620073fbdd94a7e8beb>