Date: Fri, 5 Feb 1999 00:32:24 +0200 (SAT) From: Robert Nordier <rnordier@nordier.com> To: jonny@jonny.eng.br (Joao Carlos Mendes Luis) Cc: mike@smith.net.au, current@FreeBSD.ORG Subject: Re: Overview of the FreeBSD boot process, 3.1 and later Message-ID: <199902042232.AAA29549@ceia.nordier.com> In-Reply-To: <199902042147.TAA21532@roma.coe.ufrj.br> from Joao Carlos Mendes Luis at "Feb 4, 99 07:47:46 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Joao Carlos Mendes Luis wrote: > 1) Explain a bit more how boot0 works, and which consequences could > this behavior have on another operating systems installed. For > example, say that it remembers the last booted slice by rewriting > itself. BTW: Can this be disabled ? Sometimes this is not > needed/wanted, and the only current solution is to use os-bs. I think the best place to deal in detail with boot0 would be in a boot0(8) man page, similar in approach to the present boot(8). I'll try to get around to this in the next few days. It's useful that Mike's document touches on boot[012], but the loader is a big subject in it's own right -- and the one most people will want to read up on -- whereas boot0 is not even FreeBSD-specific, beyond being included in the distribution. To answer your question: yes, updates can be disabled. The easiest method at present is to define B0FLAGS (in the Makefile) as having bit 6 (0x40) set. Though a utility for installing and configuring the boot manager from the command line is in progress. -- Robert Nordier 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?199902042232.AAA29549>