From owner-freebsd-current Tue Nov 30 9:59:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 5BAA7159A6 for ; Tue, 30 Nov 1999 09:59:11 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA02308; Tue, 30 Nov 1999 18:58:24 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: frank@exit.com Cc: current@FreeBSD.ORG Subject: Re: block devices & dumpon. In-reply-to: Your message of "Tue, 30 Nov 1999 09:49:09 PST." <199911301749.JAA48348@realtime.exit.com> Date: Tue, 30 Nov 1999 18:58:23 +0100 Message-ID: <2306.943984703@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911301749.JAA48348@realtime.exit.com>, Frank Mayhar writes: >Thomas Stromberg wrote: >> I thought all I needed to do was "./MAKEDEV all" in /dev after a >> mergemaster (I also tried MAKEDEV drive) However, I guess this is not >> the case. Evidentally if I makedev a drive or all, it does not MAKEDEV >> the slices. I could of sworn it was supposed to.. alas! Learn something >> new every day. > >Personally, I think this is a needed enhancement for MAKEDEV. IMHO, it >violates the POLA that a "MAKEDEV all" doesn't make _all_ the necessary >devices to run one's system. I agree (patches accepted), although it is hard to figure out just exactly what is needed to "run one's system". Maybe a "remake" entry in MAKEDEV which remakes all current entries if possible. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message