20 Mar 2013 17:56
sshramdisk general information
Tim Rightnour <root <at> garbled.net>
2013-03-20 16:56:38 GMT
2013-03-20 16:56:38 GMT
Recently, I added some code to evbarm to allow installation via sysinst over sshd. This allows a user to boot a headless Raspberry PI, ssh into it as "sysinst" with a password of "netbsd", and have it launch sysinst to begin the installation. It also supports the console, so if they don't want to ssh in, they can still install normally. There are a few reasons I think this is useful: 1) It's kinda annoying to buy an HDMI cable and USB keyboard just to install the PI, and then immediately disconnect them and toss them. 2) I envision this could be really useful, on a system like an NSLU2, where our current install instructions tell the user to solder a serial port onto the device. In this instance, they could instead boot the image, and just ssh in to kick sysinst off. 3) I wouldn't actually mind if other ports had this ability, as I could toss the cd in, boot, and go back to my desk rather than standing in front of my machine rack. How does it work? The embedded ramdisk contains dhcpcd, and sshd. Once the ramdisk boots, it fires up dhcpcd, gets an address, and then launches sshd. The master.passwd file has a sysinst user, with a homedir of /inst. /inst contains a profile that just kicks off sysinst. The user then installs normally. Putting sshd on the ramdisk image is a little tricky, as normally sshd pulls in 30-40 libraries. To cut that down, you need to disable PAM for the sshd build.(Continue reading)
RSS Feed