Date: Thu, 27 Feb 2003 15:55:58 -0800 From: Marcel Moolenaar <marcel@xcllnt.net> To: Garance A Drosihn <drosih@rpi.edu> Cc: John Baldwin <jhb@FreeBSD.ORG>, current@FreeBSD.ORG Subject: Re: Any ideas why we can't even boot a i386 ? Message-ID: <20030227235558.GA1596@dhcp01.pn.xcllnt.net> In-Reply-To: <p05200f29ba84405d006d@[128.113.24.47]> References: <XFMail.20030227160443.jhb@FreeBSD.org> <p05200f29ba84405d006d@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 27, 2003 at 05:29:53PM -0500, Garance A Drosihn wrote: > >I doubt the usefulness of this. i386 kernels were just accidentally > >broken for almost a month and a half without anyone noticing. > >People wouldn't have noticed if phk@ hadn't asked for a volunteer > >either. I386_CPU kernel compiles have been broken in the past for > >rather long periods of time before being noticed as well. > > Well, doesn't that suggest that it would be GOOD if the release > process itself had to build a GENERIC_I386 kernel? It's never good to add to your release cycle something you don't build/validate during development. Releases are painful enough that you don't want to turn them into testbeds. If it's not worth testing during development, it's not worth releasing... -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net 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?20030227235558.GA1596>