That particular feature could also be done with "once-persistence" as in: On next reboot load this file...
In message <199901151746.jaa01...@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. \\ m...@smith.net.au >\\ The race is long, and in the \\ msm...@freebsd.org >\\ end it's only with yourself. \\ msm...@cdrom.com > > > >To Unsubscribe: send mail to majord...@freebsd.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member p...@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 majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
