Date: Tue, 5 Oct 1999 12:23:00 +1000 From: "Andrew Reilly" <areilly@nsw.bigpond.net.au> To: Daniel Eischen <eischen@vigrid.com> Cc: des@flood.ping.uio.no, marcel@scc.nl, current@FreeBSD.ORG Subject: Re: new sigset_t and upgrading: a proposal Message-ID: <19991005122300.A79869@gurney.reilly.home> In-Reply-To: <199910011936.PAA11014@pcnet1.pcnet.com> References: <199910011936.PAA11014@pcnet1.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 01, 1999 at 03:36:11PM -0400, Daniel Eischen wrote: > But this still doesn't entirely solve the problem. You still have > to build and install a new kernel before installing the world. Of course! Installing the world _is_ upgrading your operating system. I don't see anyone suggesting that ELF applications should work on kernels that only support a.out binaries. Neither should programs that use 64-bit file offsets work on kernels that predate that change. (Note that this is entirely different from the issue of being able to use such a system to _build_ the new world.) > While this is typically what most -current folks do anyways, it > still prevents backing up to a previous kernel after the install > world. Yes. That's what backup tapes are for. If you're going to nuke your entire operating system, you'd better be ready to recover from tores. > It seems like libc should be built to be compatible with the kernel > that is currently running. After installing world and testing the > new kernel, a subsequent make world (or some other target to get > just the libs) can be done to make the libs use the new syscalls. > I like to keep old known working kernels around just in case there > are some serious bugs with the current one. Once a kernel has > proven itself somewhat stable, you can then upgrade the libs. Or, you could do it the sensible way: upgrade the kernel to support the new syscalls, and test it for a while _before_ building and installing a world that depends on it. -- Andrew 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?19991005122300.A79869>