09:21 <beerman> while trying to build my own iso (with blackjack, hookers and zfs) - the Makefile could do with a few QOL changes, IMO

10:16 <beerman> well, i deleted a few packages (xorg, most of opt) but the biggest driver is the firmware package, which we need for wifi I guess

10:16 <beerman> not much you can do there, I think..

12:50 <jaeger> I'm out of town most of the day today, will check out packages.opt this weekend

12:50 <beerman> no problem

12:50 <beerman> i just tested your iso on a notebook, worked fine for an update

12:51 <beerman> we might need to care about nghttps2-libs which used to be in contrib and moved up to core with a sane name change

12:51 <beerman> users that have nghttp2-libs installed should have it uninstalled by setup I'd say

12:56 <beerman> best idea i have is a netboot iso that doesnt provide all firmwares but all of core for dhcpcd and thats it?

13:10 <jaeger> I used to provide one like that in the past, didn't get much use

13:10 <jaeger> Though I've considered it again

13:10 <beerman> ah, yeah well, seeing the process of getting an iso i can understand why you dropped the effort

13:11 <beerman> i made several changes to the Makefile which are not fit to be merged, for instance I changed the location of packages to be out of the ports dir (nfs share that has seperate folders for all my hosts on the network)

13:15 <beerman> memtest for some reason failed, and i forgot to check your iso if yours actually works (the downloaded gz was broken for some reason that i didn't check further)

13:26 <stenur> AlpineLinux uses nghttp2-libs, which makes it easy. Alphabetically, you know. And separation (xy-{dev,doc,libs,static}).

13:28 <stenur> It would be tremendous if Linux would offer an easy way to find out correlation in between modules/drivers and the firmware, so that selective firmware fetching/loading becomes possible. Firmware is a giant.

13:29 <stenur> (I think i only need ~100 KB of that 355 MB .tar.gz, but selectively downloading via github is also shi..y.

13:29 <stenur> ).

13:31 <stenur> Fyi there will be a "MODERATE" security release of all OpenSSL next week. (frinnst was subscribed there i think, i do not know about the others.)

13:32 <stenur> (What i mean is, last release also was shipped one week before an announced security release of OpenSSL, so that the ISO had to be updated immediately to get over that, which i found a bit unnecessary.)

13:33 <stenur> (iirc)

14:40 <farkuhar> stenur: +1 on the wish for "selective firmware fetching/loading". Something like https://man.openbsd.org/fw_update would be a massive improvement over downloading a 355-MB tarball every few months.

16:09 <beerman> jaeger: i dunno why but just for the record that setup didn't inject libmnl for nftables

21:04 <stenur> farkuhar: yes, except for "Since firmware with an acceptable license is already present in OpenBSD, fw_update exists purely to deal with firmware that may not be freely distributed with OpenBSD."

21:04 <stenur> bootstrapping is a problem though; you need internet, anyway.

22:26 <farkuhar> stenur: yes, the need for internet explains why the crux iso provides the entire linux-firmware tar.gz (and also ppp!), but if you wanted to roll your own iso, selectively downloading from git.kernel.org only the firmware needed for your machine is an option.

22:31 <farkuhar> bundle up into a custom port the 100kB of binary blobs that you actually need, and now you have an iso that can fit on a 700MB CD. It won't be useful for bringing online somebody else's machine with different hardware, though.