Making custom arch iso for reasons below - question about minimum required packages in live environment for default installation
Hey everyone. So I need to make a custom iso because I don't have access to the router from my apartment and my wifi antenna uses the rtl8192eu driver, which is not included by default. Hence, I decided a custom iso was the way to go. I don't want however to bloat it up, and since I'm making it on my laptop which is running Endeavour OS I can't trust the packages.x86_64 file in the releng directory to be the default plain arch install package list (following the archiso instructions on the wiki).
So what I am actually asking for: Before building my iso, what are the packages that the actual maintainers of Arch Linux would put in the packages.x86_64 file, which we would have access to from the live environment, that I should also include (plus the 5 packages I want to make sure I have, which is the custom part of this iso)?
How I understand it reading the install guide as well as a couple forum posts, the only truly necessary packages for an arch installation are base, linux, and linux-firmware. Correct me if I'm wrong please. After installing archiso on my endeavour os laptop I had around 130 packages in my packages.x86_64 file. Many seemed unnecessary.
Nothing wrong with building your own iso, but you can also simply put the required packages on the original install stick (unless you just dd the iso, then you need another) and then install the drivers once booted.
base is not a package but a meta package for the 28 chosen bare metal neccessities. Those packages have dependencies of their own. So it will never be just 3 packages.
I would need dkms installed to add the drivers no? But without an internet connection, there would be no way to get dkms other than a physical ethernet cable, which I don't have
I think you should be able to load the drivers within the live usb environment with lsmod without the need for dkms? You can install dkms at time of install and setup so that it adds the driver when you update the system after install, but at time of install you should be able to just load the drivers after copying to the usb as @voluntaryexilecat suggested