From owner-freebsd-current Mon Mar 20 00:57:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA14221 for current-outgoing; Mon, 20 Mar 1995 00:57:57 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA14215 for ; Mon, 20 Mar 1995 00:57:56 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id AAA26243; Mon, 20 Mar 1995 00:57:43 -0800 From: Poul-Henning Kamp Message-Id: <199503200857.AAA26243@ref.tfs.com> Subject: Re: dset... To: ugen@netvision.net.il (Ugen J.S.Antsilevich) Date: Mon, 20 Mar 1995 00:57:43 -0800 (PST) Cc: freebsd-current@freefall.cdrom.com In-Reply-To: from "Ugen J.S.Antsilevich" at Mar 20, 95 10:47:37 am Content-Type: text Content-Length: 628 Sender: current-owner@FreeBSD.org Precedence: bulk > Ok..in the last 2 weeks i have not seen any single > complaint about dset.I suppose actually that this is just > because noone using it.So i'll try to uncomment it in /etc/rc > This looks now safe enough , and then we'll see.. Uhm, dset .... dset ... dset ? Is that the "boot -c" reader program ? I think you need to give people more time to test it. Last time I heard anything, it was that it wouldn't work... I'll give it a shot now... -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'