One thing I've learned is that anything that can be done in terminal can be done with SSH, since it's accessing another machine with a runlevel 3 interface.
Last night, I decided to boot openSUSE 13.2 to runlevel 3 on Triela and try to SSH into her to run updates, but I had no such luck; I tried again with Lie-chan a couple hours ago and still had the same problem.
After poking around on the net, I found the problem. The first was that the firewall was blocking SSH (port 22), and the second was that the daemon wasn't running or set to run on boot.
Once I get the chance to (probably tonight when I update Melty), I'll be able to boot any machine to runlevel 3 and remotely update it and shut it down.
Oh, when I was tinkering with the Raspi, I sent a halt signal (
sudo halt
) which wasn't the best idea, since the terminal session hung - oops! I found out a couple hours ago with Triela that I should type sudo init 6
to reboot, and with Lie-chan I sent sudo init 0
with SSH to shut her down. Sending init 0
over SSH to the target machine does a proper shutdown which then sends a logout signal to the SSH client from the target machine, making it a much cleaner experience.I tried to SSH into Taiga, but found that I was unable to since the dependencies for openssh-server were broken, so the server wasn't installed. I'll see if there's a way to fix it, though I think Debian PowerPC might make it problematic.
Things I've learned:
- Check to make sure SSH daemon is running/scheduled to run on boot
- Check to make sure firewall doesn't block incoming SSH signals
- Use
sudo init 0
to shut down machine instead ofsudo halt
- SSH is quite useful and I should have taken the time to learn it earlier
No comments:
Post a Comment