Now, Ron, really. If you're going to make a comment like that, you're going to have to provide me with a long and rambling story about why Ken and Dennis aren't responsible and how it's really Richard's fault. In my limited (and possibly rose-tinted, or at least Guinness-tinted) recollection, I have not encountered a single Unix system where something similar to the above does not happen. Of course, I've been immersed in Linux systems for the last two and a half years so it's entirely possible that I've overwritten the memory of anything that did it right (whatever that might mean in this context)
Well, the problem there is that Linux has rm aliased to 'rm -i', which is why it politely asks if you really wanna remove it, only to tell you later, whoopsie, i can't do that. As for why we really needed an rmdir command in addition to rm, that one's definitely outside of my ken. But that ceased bugging me a while ago and i've actually come to consider it a feature.
Well, the problem there is that Linux has rm aliased to 'rm -i',
Oh, that. See, that could as easily have been my own setup (and has been, in the past, until I got so used to reflexively hitting 'y' after typing 'rm' that it became useless). It doesn't address the basic issue of doing a stat() call to determine that it's a directory, asking you if you want to remove it, and then telling you it can't unlink it because it's a directory. if ( not recursive && directory ) { go directly to error message, skipping prompt } isn't exactly hard to code. I mean, if I do rm -i foo when foo doesn't exist, it goes straight to the error message without first asking me if I want to delete the nonexistent file.
I consider this dead horse to be well and truly flogged at this point.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
no subject
no subject
no subject
Oh, that. See, that could as easily have been my own setup (and has been, in the past, until I got so used to reflexively hitting 'y' after typing 'rm' that it became useless). It doesn't address the basic issue of doing a stat() call to determine that it's a directory, asking you if you want to remove it, and then telling you it can't unlink it because it's a directory. if ( not recursive && directory ) { go directly to error message, skipping prompt } isn't exactly hard to code. I mean, if I do rm -i foo when foo doesn't exist, it goes straight to the error message without first asking me if I want to delete the nonexistent file.
I consider this dead horse to be well and truly flogged at this point.