|
|
|
|
|
|
by grahamjperrin
312 days ago
|
|
|
Yep, the coherence is a strong point. Unfortunately, we now have a few people complaining about predictable, consistent behaviour with packaging that is coherent. The base system, FreeBSD, packaged. The complaints are about the effect of wilful force. Maybe I'm old-fashioned. When I force something with my eyes shut (ignoring warnings), I do expect the unexpected as a result of my ignorance ;-) |
|
|
No your not, even in the Sun-Solaris time they asked themself why rm should be able to delete /.
>The complaints are about the effect of wilful force.
Don't make a function no one uses (because it has no function) but is able destroy the system.
Compare it to a aircraft, shutdown your fuel has probably a emergency function, make a button to instantly destroy your aircraft has no real function nor will it ever be used (aka pkg remove -af).
>Unfortunately, we now have a few people complaining about predictable, consistent behaviour with packaging that is coherent.
That's not predictable but stupidity, try to remove all pkg/Application/Apps from MacOS, Windows, OpenBSD, NetBSD or Android...will the system boot or not? All those operating-systems make a clear distinction from the base-system to "apps" and the system should ALWAYS boot to a state where you can interact with it and so should FreeBSD.
There is not a single system (no OS and no living being) in this world wheres there is a function to destroy itself would not be called a error (the worst possible one)
But hey lets tell Linus (from Linus tech-tips, a Linux beginner) it's your fault because you forgot to read 100 lines, what a wannabe elitist think, there are ZERO point's, that a system should be able to make itself not booting anymore.
https://www.youtube.com/watch?v=V4L8Oci_2Bs