Date: Sat, 30 May 1998 00:50:29 -0700 From: David Greenman <dg@root.com> To: Greg Lehey <grog@lemis.com> Cc: Peter Wemm <peter@netplex.com.au>, "Jordan K. Hubbard" <jkh@time.cdrom.com>, Eivind Eklund <eivind@yes.no>, current@FreeBSD.ORG Subject: Re: Creating/deleting devfs nodes (was: I see one major problem with DEVFS...) Message-ID: <199805300750.AAA29816@implode.root.com> In-Reply-To: Your message of "Sat, 30 May 1998 15:30:46 %2B0930." <19980530153046.E20360@freebie.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>On Sat, 30 May 1998 at 13:11:29 +0800, Peter Wemm wrote: >> For the problem at hand though, I once suggested to Julian that we use >> undelete(2) to make files come back. "rm -W bpf4" could almost work as is, >> except that it wants to stat the file and look for whiteout flags first and >> 'rm' doesn't create a whiteout in devfs. (This might be an interesting >> approach to the problem if all unlinks caused a whiteout instead of the >> node disappearing entirely.) > >I don't really understand this. > >1. Why should it be possible to delete a device node from devfs? It > shouldn't be possible to remove individual nodes without removing > their functionality. rm isn't the right tool to do that, and I'd > consider it a bug to allow it. Yeah, people should use the file permissions to deny access to a device, not rm. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805300750.AAA29816>