Podcast (ogg): Play in new window | Embed
Brian Brodsky on G+
binary data on the usenet was originally in uuencode format, base64 came much later.
1)Manually configuring a static IP in Arch with systemd: systemd no longer defaults to /etc/system/interfaces to determine your network settings. The Arch wiki instead directs you to pick the most appropriate network profile from /etc/netctl/examples, copy/rename it into /etc/netctl, edit it to fit your situation, and change your config via “sudo netctl start profile” and make it permanent via “sudo netctl enable profile”.
[ https://wiki.archlinux.org/index.php/Network_configuration#Static_IP_address ]Unfortunately, the start command gave me errors, the enable command did not, but after a reboot, my server IP was still determined by DHCP.
Since netctrl was obviously supposed to just copy parameters into a config file, I looked into just editing that file directly. My answer came from Linode
( https://www.linode.com/docs/networking/linux-static-ip-configuration ). Edit /etc/systemd/network/interface.network directly. My RPI server’s file looks like:
2)Forcibly resetting root password: There is no security but physical security. Editing the /etc/shadow file. Recently, I set up DietPi to try to get Pi-hole and Nagios on the same machine. Somehow, the final step in DietPi config fouled up resetting the password w/o reinstalling.
1. Mount the SD card in another machine
2. Locate file /etc/shadow
1. In the first line, delete everything between “root:” and the next colon, i.e, line will now be root::random_string
2. Unmount SD
3. Boot as root on Pi
1. Create new password
As cheap as Pi’s are, I don’t feel I should have to buy one for each task (i.e., I’d like to put Pi-Hole and Nagios on the same box). I’m hoping the community can come together to give me a solution.
We all discuss what Linux systems we are running and why