From owner-cvs-all Sun May 13 23:11:21 2001 Delivered-To: cvs-all@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 502B637B423; Sun, 13 May 2001 23:11:15 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f4E6Avp16499; Mon, 14 May 2001 08:10:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Greg Lehey Cc: Eric Melville , Kris Kennaway , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: Destroying and remaking device nodes (was: cvs commit: src/sys/conf files options src/sys/alpha/conf GENERIC src/sys/i386/conf GENERIC NEWCARD NOTES src/sys/ia64/conf GENERIC src/sys/pc98/conf GENERIC src/sys/fs/devfs devfs_devs.c devfs_vfsops.c devfs_vnops.c) In-Reply-To: Your message of "Mon, 14 May 2001 10:51:22 +0930." <20010514105122.G88359@wantadilla.lemis.com> Date: Mon, 14 May 2001 08:10:57 +0200 Message-ID: <16497.989820657@critter> From: Poul-Henning Kamp Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010514105122.G88359@wantadilla.lemis.com>, Greg Lehey writes: >There are two issues here. Firstly, in the past it has always been >possible to remove device nodes with rm(1). If we want to keep this >functionality, we should not change the way we do it. Right, we want to be able to so that we can prune a DEVFS mounted jail/dev >On the other hand, though, is that what we want to do? The same as it always did: Deny access to the device from userland until the device node is recreated. >destroy_dev is >only half the picture. How do you recreate it? mknod has effectively >been consigned to the scrap heap. I'm sure phk will come up with some >valid arguments when he wakes up. To recreate a rm'ed devicenode I want to use "rm -W". But I don't want a jailed root to be able to, unless I permit him to. I also don't want my carefully pruned /jail/dev to show the new disk I'm adding (unless I say so), so I need some mountoptions for the subsequent mounts to tell how I want the mount to behave in these cases. I've been trawling eBay for preowned mount-options I could use, because all the 32 bits in the map are currently in use and nobody seems to want to brave the bikeshed to redesign the mount(2) API. -- 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message