A New Raspberry Pi Imager
11–20 of 21 posts
Re: A New Raspberry Pi Imager
#12Re: A New Raspberry Pi Imager
#13Earlier quoted context omitted.
Good news: rpi-imager --cli Has really expanded options over the previous versions. Including: --first-run-script --cloudinit-userdata --cloudinit-networkconfig Though it doesn't support the old simple config text file, presumably most of that is replaced by cloudinit network config. I am guessing this is available in the Windows version. I am seeing this from the macOS binary.
Yeah but I really really don't like tools doing black magic to be honest, I'd like some documentation what it does. And if it is just cloud-init, no big deal, I already know more than I'd ever wanted about this particular piece of annoyance from wrestling with AWS, just tell me what exactly the Pi userland expects me to hand to cloud-init... Thanks anyway for digging into the source, really appreciated!
Re: A New Raspberry Pi Imager
#14What about manual pre-provisioning? I just found out a few days ago that you can't pre-provision wifi via placing wpa_supplicant.conf in /boot any more, you now need to use that GUI provisioner. I appreciate that RPi is trying to make the ecosystem more accessible for newcomers - but not at the cost of power users, please!
Re: A New Raspberry Pi Imager
#15Earlier quoted context omitted.
Yeah but I really really don't like tools doing black magic to be honest, I'd like some documentation what it does. And if it is just cloud-init, no big deal, I already know more than I'd ever wanted about this particular piece of annoyance from wrestling with AWS, just tell me what exactly the Pi userland expects me to hand to cloud-init... Thanks anyway for digging into the source, really appreciated!
It feels odd to complain about "tools doing black magic" when the new way is "cloud init, a tool used by a ton of infra platforms" and the old way is "drop a file in this directory and it will somehow get slurped into the right space at the right time".
To me, "copies a file named wpa_supplicant.conf from /boot to /etc on first init" is simpler than "parses some yaml, the generates /etc/wpa_supplicant".
Maybe I'd find it worthwhile if I had encountered cloud init years ago before I invested in learning the other 900 linux networking configuration tools, but now it just feels like a case of XKCD 927 (+1 competing standards). If cloud init is even better, it definitely doesn't seem 10x better to be worth the change.
Re: A New Raspberry Pi Imager
#16Earlier quoted context omitted.
It feels odd to complain about "tools doing black magic" when the new way is "cloud init, a tool used by a ton of infra platforms" and the old way is "drop a file in this directory and it will somehow get slurped into the right space at the right time".
Isn't cloud init just slurping its own config file, then generating the "real" config files and slurping those into the right spaces? To me, "copies a file named wpa_supplicant.conf from /boot to /etc on first init" is simpler than "parses some yaml, the generates /etc/wpa_supplicant". Maybe I'd find it worthwhile if I had encountered cloud init years ago before I invested in learning the other 900 linux networking c…
I’m not making the case that it’s better, just that it’s no more “black magic” than wpa_supplicant’s config file is, and it’s less magical than dropping a wpa_supplicant file into /boot and the raspberry pi doing a bespoke RPi-specific shuffle to move it into place.
Re: A New Raspberry Pi Imager
#17Earlier quoted context omitted.
I had to go and read the docs to confirm this was true, I'm really surprised this has been removed (since Raspian Bookworm apparently). It was a ridiculously common way to configure wifi on RPis over the last decade! It's the little paper cuts like this that really hurt on a platform who's original aims were to target the education market, there is still a mountain of tutorials online advising to drop in that file fo…
> a mountain of tutorials online advising to drop in that file for wifi Cannot emphasize this enough. People with barely enough knowledge (“script kiddies” so to speak) are configuring and using RPi’s. They just want to follow the tutorial and get it working so they can do what they really want. (Eg image processing or run their 3D printer.) Nothing against this kind of user. I help them when, but… This creates a sit…
So far, I've been a big fan of netplan (which I guess is tied in with cloud-init?). Dropping a YAML file that declares the network setup I want and lets a swappable renderer make it so on the backend is a nice change from the brittle-over-time series of commands that it took previously.
Re: A New Raspberry Pi Imager
#18Conveniently for me, they keep releasing things right as I start to have an interest in using that thing.
Re: A New Raspberry Pi Imager
#19Re: A New Raspberry Pi Imager
#20https://github.com/nix-community/nixos-generators
They let you produce SD-card images with custom NixOS'es.
Very useful when you want an exact software layout, and exact system settings, like what user accounts and SSH keys to include, what systemd services should run, what directories should be tmpfs, and how to interact with the local network using avahi.