Date: Fri, 15 Jan 1999 19:17:23 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Mike Smith <mike@smith.net.au> Cc: Jaye Mathisen <mrcpu@internetcds.com>, current@FreeBSD.ORG Subject: Re: Can the bootloader create a file or set a flag in the bootblocks? Message-ID: <4751.916424243@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 15 Jan 1999 09:46:44 PST." <199901151746.JAA01235@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
That particular feature could also be done with "once-persistence" as in: On next reboot load this file... In message <199901151746.JAA01235@dingo.cdrom.com>, 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. >> >> Sort of a kernel-clean flag. Then 300 miles away, I can try stuff, and >> have at least some assurance that I'll eventually be able to get back to a >> kernel I could use. > >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!) > >-- >\\ Sometimes you're ahead, \\ Mike Smith >\\ sometimes you're behind. \\ mike@smith.net.au >\\ The race is long, and in the \\ msmith@freebsd.org >\\ end it's only with yourself. \\ msmith@cdrom.com > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! 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?4751.916424243>