From owner-freebsd-current Sat Apr 25 20:21:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02568 for freebsd-current-outgoing; Sat, 25 Apr 1998 20:21:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles322.castles.com [208.214.167.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02525 for ; Sat, 25 Apr 1998 20:21:47 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id UAA01808; Sat, 25 Apr 1998 20:18:56 -0700 (PDT) Message-Id: <199804260318.UAA01808@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Doug Rabson cc: current@FreeBSD.ORG Subject: Re: ELF kernels: When? In-reply-to: Your message of "Sat, 25 Apr 1998 10:19:18 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 25 Apr 1998 20:18:54 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 24 Apr 1998, Mike Smith wrote: > > The major issues are build-related; the NetBSD bootblocks have a > > ringworm-like grip on the rest of the kernel source tree which has > > resisted the last couple of efforts I've put into separating them. > > Sounds like we need src/contrib/netbsd. No, no, stop hitting me! 8) The problem with attacking the NetBSD bootblocks is that they have to be swallowed all at once; if you want to build using their existing infrastructure you need a kernel layout that looks exactly like theirs, as well as the NetBSD make (because they use some new hacks), and their includes, and... Ripping it all out and restructuring it somewhere else seems to make so much sense. 8) -- \\ 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