From owner-freebsd-current Fri Oct 31 13:29:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA06205 for current-outgoing; Fri, 31 Oct 1997 13:29:08 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA06192 for ; Fri, 31 Oct 1997 13:28:44 -0800 (PST) (envelope-from shimon@sendero-ppp.i-connect.net) Received: (qmail 19808 invoked by uid 1000); 31 Oct 1997 21:29:02 -0000 Message-ID: X-Mailer: XFMail 1.2-beta-100797 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <23644.878328872@time.cdrom.com> Date: Fri, 31 Oct 1997 13:29:02 -0800 (PST) Organization: Atlas Telecom From: Simon Shapiro To: "Jordan K. Hubbard" Subject: Re: More on LINT Kernel Failure to compile Cc: John-Mark Gurney , freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi "Jordan K. Hubbard"; On 31-Oct-97 you wrote: > > Had I had to compile the LINT kernel, I know how to do it. The problem > > is > > that I assumed (hate that word :-) that the LINT kernel is sort of > > standard > > sanity check for sources and is supposed to compile all by itself, > > without > > me ``assisting'' it. > > And this is entirely correct. It used to be incumbent on people to > keep LINT in working order for exactly that reason and it's quite > unfortunate that this has been slacked off on a bit in -current > recently. It was never anyone's intention that a LINT kernel be > bootable, but it was supposed to at least compile and, now that it > doesn't, will be hiding any number of problems from detection in that > manner. It should be fixed by whomever broke it last, to paraphrase > Bruce. If no one in particular is maintainig LINT, I just volunteered. I'll add it to my short list of things to do :-) Simon