Hacker News Reader

Comment by johnklos | Hacker News Reader

The overlap of people who might want to ssh and people who don't know how to configure their own wireless doesn't seem all that large.

On the other hand, I could see this being useful as an additional software package that gets run when the Pi can't find or join its usual network.

View on HN

My hassle is usually: Where do I dig up that keyboard and spare HDMI video source to bootstrap the Pi. Currently the MAME cabinet does that well, but not everyone has a MAME cabinet.

You don’t. You just enable ssh and connect it to network. Essentially ‘touch /boot/ssh’

But you can’t do that from a raspbian image, and if you want me to mod my file system post install that only works assuming I can mount it (eg I have another Linux box with keyboard).

I’ve had this problem multiple times and find this approach really nice (and wish it shipped with raspbian!)

/boot is a fat partition. You can mount that from most OSs.

Edit: forgive me, I see that's not what you meant at all. Or maybe it was? Either way, the point is valid.

But where was the SD card flashed? I think the idea is to enable ssh right after flashing the image.

Say on a Mac or windows box.

But /boot is a FAT32 partition, it's mountable on practiacally any os I'm aware of. On a mac it'll be under /Volumes/boot.

Unless I’m mistaken, /boot isn’t where any kind of network / ssh config would live.

Ssh can be enabled and wifi configured in /boot.

Yes. Touch (create) an empty file called "ssh" in /boot, and wifi details in wpa_supplicant.conf as mentioned elsewhere in the thread. Very handy!

Yes, I know. I was just telling GP that they are mistaken. :)

Reply on news.ycombinator.com