3 ms·

None I currently use (just tested with bash* on: Debian, Centos, Fedora, OpenWRT) or have used in the past few years (Arch) has it. I don't remember anything a

None I currently use (just tested with bash* on: Debian, Centos, Fedora, OpenWRT) or have used in the past few years (Arch) has it. I don't remember anything about my time with SUSE and Ubuntu, thats way back. * I normally use zsh with grmlzshrc and nearly no customization (which is why I love grmlzshrc -- usable defaults), which warns for `rm -rf foo/*` but not for `rm -rf foo`.

pjmlp 11y ago
Maybe I am wrong but I think Red-Hat, Mandrake and SuSE used to do it. Nowadays I spend most of my time in Windows and mobile OSes to remember it properly.
SEJeff 11y ago
Redhat based distros absolutely do enable alias rm='rm -i' out of the box, but only for the root user. As a career SysAdmin, that seems like a good compromise. If you want to take the safety net off, you can escape out the alias (or any alias) with a slash i.e.: \rm -rf somedir Yet by default, if you don't include the "\", you get rm -i
- Ao7bei3s 11y ago
  You're right about RedHat, sorry. .bash_history says I accidentally added `-f` on that host. I should have just checked with `which` instead of trying it out. Oops.
  - SEJeff 11y ago
    Actually even if you do rm -f, the -i will still be added if it is an alias. Better is to use the bash builtin "type": type rm is better than which rm, but it depends on what distro you're using. Some distros (Just checked on RHEL7) will fancify which as well ie: $ type which which is aliased to `alias | /usr/bin/which --tty-only --read-alias --show-dot --show-tilde'
    - Ao7bei3s 11y ago
      > Actually even if you do rm -f, the -i will still be added if it is an alias. Yes, I know, but rm ignores -i if -f is given. [root@example ~]# touch blah [root@example ~]# rm -i -f blah [root@example ~]# And hence: [root@example ~]# which rm alias rm='rm -i' /usr/bin/rm [root@example ~]# touch blah [root@example ~]# rm -f blah [root@example ~]# @type: yes, you're right, thanks for the reminder.

pjmlp 11y ago

Maybe I am wrong but I think Red-Hat, Mandrake and SuSE used to do it. Nowadays I spend most of my time in Windows and mobile OSes to remember it properly.

SEJeff 11y ago

Redhat based distros absolutely do enable alias rm='rm -i' out of the box, but only for the root user. As a career SysAdmin, that seems like a good compromise. If you want to take the safety net off, you can escape out the alias (or any alias) with a slash i.e.: \rm -rf somedir Yet by default, if you don't include the "\", you get rm -i

Ao7bei3s 11y ago
You're right about RedHat, sorry. .bash_history says I accidentally added `-f` on that host. I should have just checked with `which` instead of trying it out. Oops.
- SEJeff 11y ago
  Actually even if you do rm -f, the -i will still be added if it is an alias. Better is to use the bash builtin "type": type rm is better than which rm, but it depends on what distro you're using. Some distros (Just checked on RHEL7) will fancify which as well ie: $ type which which is aliased to `alias | /usr/bin/which --tty-only --read-alias --show-dot --show-tilde'
  - Ao7bei3s 11y ago
    > Actually even if you do rm -f, the -i will still be added if it is an alias. Yes, I know, but rm ignores -i if -f is given. [root@example ~]# touch blah [root@example ~]# rm -i -f blah [root@example ~]# And hence: [root@example ~]# which rm alias rm='rm -i' /usr/bin/rm [root@example ~]# touch blah [root@example ~]# rm -f blah [root@example ~]# @type: yes, you're right, thanks for the reminder.