Date: Sat, 16 Jan 1999 11:21:42 -0800 From: Bill Trost <trost@cloud.rain.com> To: current@FreeBSD.ORG Subject: Re: Can the bootloader create a file or set a flag in the bootblocks? Message-ID: <30110.916514502@grey.cloud.rain.com> In-Reply-To: Your message of Fri, 15 Jan 1999 09:46:44 PST. <199901151746.JAA01235@dingo.cdrom.com> References: <199901151746.JAA01235@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Smith writes:
> It would be kind of cool if when managing a remote system if
> /kernel failed to boot, then on the next boot, the loader will
> fire up /kernel.old, or a /kernel.somethingorother.
We're trying to work out a clean way of managing that sort of
persistent state that doesn't involve nasty hacks like the
'nextboot' code did. It's kinda tricky if you don't want "write"
implemented in all your filesystems (bloat!)
Maybe I don't understand the problem here, but something akin to how
kernel configuration changes are handled seems like a good way to deal
with this problem. /boot/loader could stuff something into memory (sort
of like the way you can stuff a splash screen into memory), and a
user-level program can read that information and stuff it wherever it
needs to be stuffed.
That may be a little hard with tftp, but with most of the other media
types it seems like it should be relatively straightforward.
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?30110.916514502>