Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 01 May 2000 12:59:51 -0700
From:      Mike Smith <msmith@freebsd.org>
To:        "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc:        current@FreeBSD.ORG
Subject:   Re: cvs commit: src/lib/libstand ext2fs 
Message-ID:  <200005011959.MAA03141@mass.cdrom.com>
In-Reply-To: Your message of "Mon, 01 May 2000 12:33:11 PDT." <95629.957209591@localhost> 

next in thread | previous in thread | raw e-mail | index | archive | help
> > <wishlist>
> > Not sure if this is a silly question or not, but could the kernel somehow
> > view a specific dir on a ext2fs disk as the freebsd root and boot a
> > freebsd system from it?  Also being able to access the stuff below the
> 
> I think there's a more general need to have a loader variable which
> you can set for "chrootdir", that being the subdirectory of the rootfs
> which becomes "/".  Such a feature would be good for a lot more than
> just hosting a FreeBSD system inside your existing Red Hat
> installation. :)  Booting multiple versions of FreeBSD without having
> to play partition games comes to mind..

What sort of fallback behaviour would you want in case of error here?  
Calling chroot() inside the kernel before invoking init would be fairly 
easy, and I think that's all you'd need to get DWIM behaviour.  (It might 
not be perfect, but it'd be pretty damn close.)

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  msmith@freebsd.org
\\ and he'll hate you for a lifetime.             \\  msmith@cdrom.com




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005011959.MAA03141>