@ MarkBeepBeep :-
Have a read of this:-
https://igurublog.wordpress.com/2010/01/16/fear-not-root/
And then - if you haven't already done so - read this:-
https://linux.oneandoneis2.org/LNW.htm
Both WELL worth perusing.
We run as 'root' all the time in Puppy; it was always intended as a single-user system, and a "hobbyist" system at that.......designed for folks that enjoy tearing their system apart, and re-building it to suit themselves. Don't get me wrong; in a multi-user environment, the 'standard', protected-root user paradigm makes a LOT of sense.....but in the home environment, where most are the sole master of their wee kingdom, constantly entering 'sudo' to do the slightest little thing gets real old. Fast.
(To be fair, having the restrictions in place actually helps where noobs & beginners are concerned. It takes time to learn what you can and can't safely do with a Linux system. But in my case, I've been using Linux for over a decade now; I'm aware of all the pitfalls; I know which way is 'up', and have more than a passing acquaintance with what's what. Now, in MY case, why should I have to give myself permission to do anything on my own system.....especially where I'm the sole user? Makes NO sense.)
Puppy is naturally bullet-proof, anyway, running as it does from compressed, read-only files that unpack into a virtual file-system in RAM. It cannot get corrupted......and if you suspect you've picked up any nasties during a session, don't 'save' that session at shutdown. Just let it evaporate into cyberspace instead.....
Many mock Puppy's mode of operation, because they don't understand it. And other Linux users have more trouble understanding it than someone who's never used a 'puter in their lives. What does that tell you, hm..?
"Getting stuck in a rut" springs to mind......
Mike.
Edited by Mike_Walsh, 01 June 2024 - 11:47 AM.