4 ms·

I had a personal dev server running arch with a simple static IP. I had tutorials on arch telling me to manually create and edit systemd scripts to start and st

I had a personal dev server running arch with a simple static IP. I had tutorials on arch telling me to manually create and edit systemd scripts to start and stop the interface, then add and enable them. To configure a simple static IP, which should be an extremely trivial task. Now compare with FreeBSD, just add 1 single line to /etc/rc.conf and I'm done, 2 if I want a default gateway too. Here's a link to what I was dealing with: https://wiki.archlinux.org/index.php/Network_configuration#Persistent_configuration_on_boot_using_systemd https://wiki.archlinux.org/index.php/Network_configuration#P... 20+ lines vs 2. You tell me which is simpler. Also, our of curiosity, do you know what systemctl enable does? What files does it modify and how would you do it on a remote system (ie: one you'd mounted)? Would you need to chroot?

dnlrn 12y ago
You are comparing apples and oranges. Network management in Arch was replaced by netctl. It’s very easy to set up your static network that way (you just have to edit 1 line). systemctl actually tells you what it does as output. It symlinks a service file from one directory to another. You can always do that by hand.