From owner-freebsd-current Sun May 9 14:21:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 1A3F51563F for ; Sun, 9 May 1999 14:21:31 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.1) id OAA13348; Sun, 9 May 1999 14:18:11 -0700 (PDT) (envelope-from obrien) Message-ID: <19990509141811.A13330@nuxi.com> Date: Sun, 9 May 1999 14:18:11 -0700 From: "David O'Brien" To: Poul-Henning Kamp , Chuck Robey Cc: freebsd-current@FreeBSD.ORG Subject: Re: kernel.old Reply-To: obrien@NUXI.com References: <21918.926281586@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <21918.926281586@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, May 09, 1999 at 10:26:26PM +0200 X-Operating-System: FreeBSD 3.2-BETA Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Something on the order of modules.old is going to need to > >be implemented. > > Not to mention /boot/kernel.old.config ... > > I think you are seeing -current as the norm. You shouldn't. Under > -stable the modules should (tm) continue to work since there are not > made API changes in -stable. BUT we shouldn't make it easy for our developers (who do need to run -CURRENT) to kill themselves. Our development time is limited, and recovering from a bum kernel can be a PITA in some situations, so lets not waste our development time when we don't need to. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message