From owner-freebsd-current Mon May 10 13:36:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 6DD6015CCC for ; Mon, 10 May 1999 13:36:26 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA09474; Mon, 10 May 1999 22:34:07 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA46629; Sun, 9 May 1999 23:13:16 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905092113.XAA46629@yedi.iaf.nl> Subject: Re: kernel.old In-Reply-To: from Chuck Robey at "May 9, 1999 4:14:58 pm" To: chuckr@picnic.mat.net (Chuck Robey) Date: Sun, 9 May 1999 23:13:16 +0200 (CEST) Cc: freebsd-current@FreeBSD.org X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Chuck Robey wrote ... > I was thinking about Peter Wemm's recent change to the kernel Makefile, > making a way to install multiple kernels without fragging your last > known good kernel, and it got me to thinking, scragging kernel.old, now > that we have good kld's, isn't the only way to find yourself well and > truly screwed if your new kernel decides it's shy. Shy enough to hide on the swap device after a panic ;-) ? Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message