Comments by "Lawrence D’Oliveiro" (@lawrencedoliveiro9104) on "Lil' Linux Lesson - Sudo for beginners!" video.

  1. 3:13 The key difference between “su” and “sudo”, as far as I’m concerned, is that “su” prompts for the root password, while “sudo” prompts for your password. “su” lets you become any user for which you know the password, not just root. It also allows the root user to become any user without knowing their password. “sudo” gives you more fine-grained control over what users are allowed to do. Many admins prefer it because it doesn’t require the root user to have a valid password. Linux faux pas I see too often: people using sudo to run su. Tisk.
    3
  2. There are quite a few other history substitutions, e.g. “!!” to substitute the last command “!«n»” to substitute command number «n» from your history “!«prefix»” to substitute the last command beginning with “«prefix»” “!?«substr»?” to substitute the last command containing “«substr»”.
    3
  3. So su me.
    2
  4. I never bothered with awk. I found Perl did everything awk could do and more, and do it just as concisely.
    1
  5. I tried “sudo mkdir ~/limbo”, and it was in my home dir. If sudo executes the command “as would root execute it”, it would be in root’s home dir, not mine. So you must be wrong.
    1
  6. That group is just one of the ways of controlling access to sudo.
    1
  7. System admin functions require privileged access that is not needed while doing normal user tasks. It is best to keep them separated. In particular, never log into a GUI session as the root user.
    1