cpghost wrote: > On Tue, 25 Sep 2007 21:58:37 +0900 > Daichi GOTO <daichi_at_freebsd.org> wrote: > >> Today is not unionfs. Introduction for safety expansion of rm(1). >> I know that some unix folks have a experience that you remove some >> files or directories accidentally. Yes, me too. LoL >> >> Have you any dreams that rm(1) autonomously judges target should >> be remove or not? To complexify system base command is objectionable >> behavior but adding some little and simple mechanism to prevent a >> issue is acceptable I suppose. >> >> We have created safety expansion for rm(1). If you have any interests, >> please try follow patch. >> >> http://people.freebsd.org/~daichi/safety-rm/ >> >> Thanks :) > > Interesting idea, but isn't that a violation of POLA? Imagine an What's POLA?? > unsuspecting sysadmin trying to rm something, and forgetting > or not knowing about ~/.rm? > > Isn't it better to protect important system directories with > something like: > # chflags sunlink /path/to/dir > and unprotect them with > # chflags nosunlink /path/to/dir > to avoid mistakes? Of course that's one of the ways, I suppose :) chflags is useful but root limitation feature is not useful for common users I suppose. With our expansion, common users can check files or directories on self-responsibility. And unusual commands like chflags I just suppose are no much point in this case. What is important is that adding mistake protecting functions into common commands like rm(1) itself. Of course I respect your opinions and all comments are welcome :) I have no intention to add our expansion to src tree. It just is a little patch for folks who have a interest of it. Thanks > Thanks, > -cpghost. -- Daichi GOTO, http://people.freebsd.org/~daichiReceived on Thu Sep 27 2007 - 09:27:58 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:18 UTC