Comment by Raed667
running a funky chmod command recursively on my root dir and then learning how to fix it, probably taught me more about how linux works than any tutorial or article i've ever read.
have fun! break things!
running a funky chmod command recursively on my root dir and then learning how to fix it, probably taught me more about how linux works than any tutorial or article i've ever read.
have fun! break things!
One time I somehow set the permissions of the sudo executable to lower than they needed to be (0600?). Fixing that was fun :)
> One time I somehow set the permissions of the sudo executable to lower than they needed to be (0600?). Fixing that was fun :)
I know very little, admittedly, but without telling us how, it’s just a funny anecdote.
I would try to switch user to root and su instead of sudo, but I’m not sure if that would actually work. Would it? Probably not on rootless installs, but I don’t know how many of those systems most folks are able to break in the manner described above.
I broke enough things in my early Linux days and learned a lot, but enjoying that, seeing it as a positive, or even having the willingness and time to spend on such fixes is far from universal. Most people have severe mental blocks to doing anything on the command-line for fear of breaking everything. Having an environment where they can’t break anything is a fantastic way to help them build confidence and learn how the computer works.
There is a time and place for each approach. Recognising which is appropriate for each situation and user is a good skill to cultivate.