From: utzoo!decvax!harpo!floyd!vax135!lime!we13!rjk Newsgroups: net.unix-wizards Title: Re: recovering lost files Article-I.D.: we13.264 Posted: Sat May 29 11:35:33 1982 Received: Wed Jun 2 01:29:25 1982 References: duke.2177 I suspect that the overhead involved in idiot-proofing the "creat" syscall (eventually used by shell ">") or the "rm" program would be prohibitive. Here are some suggestions: 1) File is "foobar.c", you are developing it and want to protect it. Every so often you type: save foobar.c which stashes it in a safe deposit directory. (I'll be glad to post the source to this command) 2) File is writable data. Ok; same thing. After modifying it, save it. 3) File is readonly data. Easy: chmod 444 data_file. At least rm will now ask you and shell will not create. As said before, if YOU deem the file THAT important, then take a couple of seconds to ensure that YOU protect yourself. It's like asking auto manufacturers to ensure that we can't run into another object unless we REALLY mean to. (wreck -y??). You learn to drive, no? Then learn to be a careful UNIX user. It's more powerful that way. Randy King ..we13!rjk PS> Look in net.sources. I'll put "save" there. It's been running on our system for years.