After executing this step you are connected to your instance. We will have to install new packages. Some of them require root credentials, so you will have to set a new root password: sudo passwd root. Then login as root: su root.
Wouldn't using the "sudo su" command be a better approach? Granted I am only a developer not a sysadmin, but I thought the whole point of Ubuntu's sudo setup was to not have a usable root login.
Comments
I don't know about this part:
After executing this step you are connected to your instance. We will have to install new packages. Some of them require root credentials, so you will have to set a new root password: sudo passwd root. Then login as root: su root.
Wouldn't using the "sudo su" command be a better approach? Granted I am only a developer not a sysadmin, but I thought the whole point of Ubuntu's sudo setup was to not have a usable root login.
Yeah, it's pretty common practice to disable the root account from SSH access/never log in as root.
Linode has a pretty good getting-started guide for basic Ubuntu VPS security: http://library.linode.com/securing-your-server
Not really right or wrong in my opinion. That is the thing with Unix-like OS's. There are many ways to skin a cat. I prefer -- 'sudo su - root'.
Yes, it would. Also, "sudo -s".