From owner-freebsd-current@FreeBSD.ORG Fri Mar 26 12:31:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BB9B16A4CE; Fri, 26 Mar 2004 12:31:25 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90E6043D31; Fri, 26 Mar 2004 12:31:24 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i2QKVLLh010079; Fri, 26 Mar 2004 21:31:22 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: Doug White From: "Poul-Henning Kamp" In-Reply-To: Your message of "Fri, 26 Mar 2004 12:23:58 PST." <20040326122333.S61326@carver.gumbysoft.com> Date: Fri, 26 Mar 2004 21:31:21 +0100 Message-ID: <10078.1080333081@critter.freebsd.dk> cc: Luigi Rizzo cc: "current@freebsd.org" Subject: Re: userland|unprivileged file system handling tools X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Mar 2004 20:31:25 -0000 In message <20040326122333.S61326@carver.gumbysoft.com>, Doug White writes: >On Wed, 24 Mar 2004, Doug Barton wrote: > >> > As far as -current goes, mknod is not anything worth mentioning because of >> > devfs. This is actually wrong, mknod is the important tool you need when you have "rm /dev/null"'ed your system and want to recover -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.