I do want to clarify: it’s not Linux itself, but specific distributions (or rather their package managers). As far as I know, Arch’s pacman would do nothing to stop me 🥰
True, Linux applications (e.g. apt, dnf, pip, but also rm, sudo, and many more) would be more precise.
For Arch, it’s probably not so easy to define “essential” packages, as it, for example, supports many different bootloaders. It is of course also a question of distro philosophy and target audience. Personally, I’ve noticed that “rm -r” as root prompts for every file on RHEL but does not on Arch…
Yeah, swapped out grub for systemd-init on a running Arch system not too long ago. Arch is cool with it. Be sure not to make any really bad typos while you’ve not got a boot manager, of course.
E: Removing essential system-critical packages is not permitted. This might break the system.You can still do it if you really want, but even Linux rightly has some protections against breaking your system.
I do want to clarify: it’s not Linux itself, but specific distributions (or rather their package managers). As far as I know, Arch’s pacman would do nothing to stop me 🥰
True, Linux applications (e.g. apt, dnf, pip, but also rm, sudo, and many more) would be more precise.
For Arch, it’s probably not so easy to define “essential” packages, as it, for example, supports many different bootloaders. It is of course also a question of distro philosophy and target audience. Personally, I’ve noticed that “rm -r” as root prompts for every file on RHEL but does not on Arch…
Yeah, swapped out
grubforsystemd-initon a running Arch system not too long ago. Arch is cool with it. Be sure not to make any really bad typos while you’ve not got a boot manager, of course.