From owner-freebsd-current Tue Nov 10 16:11:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10915 for freebsd-current-outgoing; Tue, 10 Nov 1998 16:11:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10847; Tue, 10 Nov 1998 16:11:08 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id TAA19796; Tue, 10 Nov 1998 19:09:23 -0500 (EST) Date: Tue, 10 Nov 1998 19:09:23 -0500 (EST) From: Chuck Robey To: Mike Smith cc: "Jordan K. Hubbard" , current@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: Is it soup yet? :-) In-Reply-To: <199811102044.MAA00415@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Nov 1998, Mike Smith wrote: > > I'm just wondering when we're going to switch the kernel to ELF and > > put /usr/src/sys/modules into the build path. I'd really like the > > /usr/bin/linux command to start doing the right thing on current 3.0 > > SNAPshots, among other things. :-) > > I think we're about ready to do it. We probably want to insist that > people cut over to the new bootstrap first, perhaps with a HEADS UP > announcement from someone that hasn't cried wolf before. ??? Modules are *already* installed by buildworld. Peter did this, what, a week ago? As far as the kernel goes, I found out during my own conversion that the bootblocks from 2.2.6 will give you a non-booting machine ... that's the bar you have to jump, in getting elf kernels installed on everyone's machine, without major hassle from everyone who comes late to the game. I don't know enough about the bootblocks ... I just followed Mike's steps in getting myself installed ok, but is it possible to write a program that could probe the boot disk, read the bootblocks, and decide if they need upgrading ... and if they do, printing a warning message, and then refuse to install the new kernel? If this could be done, you know this will save a *lot* of complaints about insufficient warnings. You could warn until you're hoarse, they'll *still* miss it, unless the build process itself screams at them. > > -- > \\ 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 > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message