5 ms·
I'll admit I'm a little confused by the "pure-Go userland" aspect. At first I thought this meant a userland consisting of common utilities (ls, grep, the usual
by 2bitencryption 7y ago
I'll admit I'm a little confused by the "pure-Go userland" aspect.
At first I thought this meant a userland consisting of common utilities (ls, grep, the usual GNU suspects) written in Go, but that doesn't seem to be the case.
Instead, it seems to be, if you can compile your Go program for AMD64, and it can build without glibc (or any c runtime), then it can be hosted by Gokrazy? Is that right?
- IshKebab 7y agoThey mean the whole userland. Like, init onwards. It's a great idea because the Linux userland is kind of a hacky mess, and takes active maintenance - not something you really want on an embedded device. This makes it more like a microcontroller, where basically the only process you have to worry about is your own. My only question is does it work with WiFi? I was under the impression that quite a lot of the Linux WiFi stack was implemented in userland (wpa_supplicant).
- xyzzy_plugh 7y agoDistros are where the mess lives, to be honest. You can do a lot with BusyBox.
- steevdave 7y agowpa_supplicant just does the heavy lifting of connecting to the WiFi network. The WiFi device itself is handled by the kernel's brcmfmac driver, and there is the usual firmware (also requires a .txt file) or you can use something like nexmon, which tweeks the firmware (and a patched driver to use it) for using monitor mode, injection and a few other misc things people have done with the firmware.