From owner-freebsd-hackers Mon Oct 30 04:27:16 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA20776 for hackers-outgoing; Mon, 30 Oct 1995 04:27:16 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id EAA20756 for ; Mon, 30 Oct 1995 04:26:16 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id NAA27215; Mon, 30 Oct 1995 13:22:00 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id NAA22449; Mon, 30 Oct 1995 13:21:59 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id JAA05371; Mon, 30 Oct 1995 09:57:20 +0100 From: J Wunsch Message-Id: <199510300857.JAA05371@uriah.heep.sax.de> Subject: Re: Lost my original /sbin/dset -q values To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 30 Oct 1995 09:57:19 +0100 (MET) Cc: freebsd-hackers@freebsd.org (FreeBSD hackers) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <522.815039913@time.cdrom.com> from "Jordan K. Hubbard" at Oct 29, 95 11:58:33 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1072 Sender: owner-hackers@freebsd.org Precedence: bulk As Jordan K. Hubbard wrote: > > > dset(8) writes directly into the kernel. Of course, if your /kernel > > and /kernel.GENERIC are hard-linked, it's no surprise that ``both'' > > kernels are affected. (Huh, Jordan? We shouldn't hardlink them at > > installation time!) > > It's either that or simply `mv' it since most folks don't budget space > for more than one image, especially "kitchen sink" ones like GENERIC. > Would you prefer I just move it? Hmm, no. People who are tight in space could remove it themselves, should they prefer. I'm always keeping a `standard' kernel around, and i rather rely on this being an unmodified one, so i can boot off it in case of emergency. (Heck, i also did this previously with Data General workstations. They also left the /dgux.starter around there unmodified, this was a good way to recover from a damaged regular /dgux file.) I think i'm not the only one. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)