On Mon, May 01, 2000 at 09:08:02PM -0700, Mike Smith wrote:
What sort of fallback behaviour would you want in case of error here?
Just let chroot() either succeed or fail. It's own "fallback behavior"
in such a case should prove adequate. :)
Hmm. Failure to chroot == failure to
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
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
What sort of fallback behaviour would you want in case of error here?
Just let chroot() either succeed or fail. It's own "fallback behavior"
in such a case should prove adequate. :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of
What sort of fallback behaviour would you want in case of error here?
Just let chroot() either succeed or fail. It's own "fallback behavior"
in such a case should prove adequate. :)
Hmm. Failure to chroot == failure to start init?
--
\\ Give a man a fish, and you feed him for a day.
In [EMAIL PROTECTED], Adam wrote:
On Sat, 29 Apr 2000, Jonathan Lemon wrote:
On Sun, Apr 30, 2000 at 11:15:47AM +0930, Greg Lehey wrote:
On Saturday, 29 April 2000 at 13:44:08 -0700, Jonathan Lemon wrote:
jlemon 2000/04/29 13:44:08 PDT
Added files:
lib/libstand
On Sat, 29 Apr 2000, Jonathan Lemon wrote:
On Sun, Apr 30, 2000 at 11:15:47AM +0930, Greg Lehey wrote:
On Saturday, 29 April 2000 at 13:44:08 -0700, Jonathan Lemon wrote:
jlemon 2000/04/29 13:44:08 PDT
Added files:
lib/libstand ext2fs.c
Log:
Add ext2fs support
