Finally managed to get a static ip set and dns working properly, got a question though.

I followed this guide: https://www.howtoforge.com/linux-bas...c-ip-on-ubuntu and managed to get it work however it required a reboot for the changes to take effect.

The bottom part of the guide which has this command:

systemctl restart ifup@eth0

is supposed to bring the network back up right? I'm curious why the guide didn't suggest to use

sudo service networking restart

and I'm also curious why when I ran systemctl restart ifup@eth0 some red text appeared and asked me to authenticate.

Output:

==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to restart 'ifup@eth0.service'.
Authenticating as: wh33t,,, (wh33t)
Password:

I didn't just give out my password to my user account to some website did I?

Hi!

Originally Posted by wh33t and I'm also curious why when I ran systemctl restart ifup@eth0 some red text appeared and asked me to authenticate.

Because you need root (sudo) privileges to do that.

Originally Posted by wh33t I didn't just give out my password to my user account to some website did I?

No, you did not.

Best regards,
HMW

What you mistook for a website is actually a program name used by dbus. systemd/systemctl uses dbus to send instructions to programs. Every program has a "well-known-name" that is registered with dbus, and these use what is called reverse dns notation. The org suffix comes first, then the organisation, then the name -- the reverse of a normal url.

Originally Posted by hazel What you mistook for a website is actually a program name used by dbus. systemd/systemctl uses dbus to send instructions to programs. Every program has a "well-known-name" that is registered with dbus, and these use what is called reverse dns notation. The org suffix comes first, then the organisation, then the name -- the reverse of a normal url.

Awesome. Thank you for the information.

Would you happen to know if

sudo service networking restart

is obsolete now? It doesn't appear as thought it works as I expect it to anymore.

Yes, it depends on the distribution/version's init process. If you reread the link you posted you will see that for Ubuntu versions newer then 14 (>14) the command is systemctl which is used by systemd. While older Ubuntu versions used either upstart or sysv depending on how far you want to go back which use the old service command.

Originally Posted by michaelk Yes, it depends on the distribution/version's init process. If you reread the link you posted you will see that for Ubuntu versions newer then 14 (>14) the command is systemctl which is used by systemd. While older Ubuntu versions used either upstart or sysv depending on how far you want to go back which use the old service command.

I guess I'm just confused as to why the system still accepts an older-not-right way of doing things. Why isn't that removed from the system if it's no longer the right way to restart the networking services?

I believe it is for backwards compatibility if you still have services that use old init scripts. Check your /etc/rcx.d directories. The networking services are systemd.

I believe that by default, systemd creates temporary service files for init scripts that it finds in rc.S and rc.2. You should be able to find them in the /run tree somewhere.