Hehe, maybe I should have skipped the chalkboard comment. It's just a question of personal choice, convenience, security and how your OS is setup. When you're trying to explain to a novice user that certain commands require superuser permissions to execute, it gets difficult to explain it in certain situations so it's safer to just put "sudo" before the commands that need it so that you know the end user will be successful in following your instructions. In many cases distros will have sudo setup with nopasswd for all by default (which incidentally is highly insecure) so it's easier to lob in the occasional superuser command with sudo. Also you might not want to unleash a novice user on a root terminal if he's not completely aware of the implications, and he continues to use it even after following your instructions.
If on the other hand you have sudo setup with a password and you're prompted to enter it at each command, it just gets silly if your root password is complex (as it should be) and you have several commands to issue so then it makes more sense to save yourself some typing and go 'su' for the session. That's part of the reason why I never bother with sudo in the first place and either disable or remove it. So when I cringe when I see instructions prefaced with sudo at every command, that's just my problem.
Aaaaanyway, now that we've thoroughly hi-jacked Mobus' thread, I can only wonder if he's still around and got his issue fixed.
Well mobus came in this as a newbie so a little instruction can't hurt right? And we hijack threads as a matter of course. We're all friends here.
You wrote it as I think it...me a newbie teaching newbies, sudo is safer....su is a lot more convenient. What I have done is avoided getting into security issues and another level of instruction that is covered everywhere.
My goal is to keep older toughbooks working, not to teach Linux.
Thank you for the write up.
J'd...so where's mobus?...
_________________Fair for you/ Fair for me.
I chose to NOT be organized.