From owner-freebsd-current Fri Oct 1 12:37:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 6FFDA14EA4 for ; Fri, 1 Oct 1999 12:37:20 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id PAA11014; Fri, 1 Oct 1999 15:36:11 -0400 (EDT) Date: Fri, 1 Oct 1999 15:36:11 -0400 (EDT) From: Daniel Eischen Message-Id: <199910011936.PAA11014@pcnet1.pcnet.com> To: des@flood.ping.uio.no, marcel@scc.nl Subject: Re: new sigset_t and upgrading: a proposal Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marcel Moolenaar wrote: > Dag-Erling Smorgrav wrote: > > > > How about this: early in make world, we check whether or not the > > current kernel supports the new syscalls. If it does, good. If it > > doesn't, we build and load a small module which installs syscalls > > which translate the sigset_t stuff into something the old syscalls can > > grok. Does that make sense to any of you guys? > > That has been proposed by someone (sorry, I can't remember who exactly). > We still need a consensus as to what we should do. Personally, I now > like to fix this at the core of the problem: truly support > cross-compilations. This implies (IMO) that the source tree is never > used to build the tools with which a world is built (ideally). Such a > solution may take too long to be implemented to be used as a solution > now, though. But this still doesn't entirely solve the problem. You still have to build and install a new kernel before installing the world. While this is typically what most -current folks do anyways, it still prevents backing up to a previous kernel after the install world. 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. This is why I kind of like (was it?) Peter Wemms libc hack. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message