Guess it’s time to either get a new pendrive, or enter the void.
These new pendrives wear out after 2 months of light usage, so I’m probably going to choose the second one, but I’m afraid that if I make this step, there’s no going back, and I’ll forever be sucked into the void.
I usually just use the ones that just spawn into existance, that way they don’t cost money. Last time I bought a toshiba, before that a kingston, and I don’t remember what was before that, but I know that if I buy, I buy from reputable brands and even those fail.
This might be a bad place (i.e. post, the community is correct), but looking at the void has got me interested so I wanted to ask: What are the main advantages of using runit compared to systemd? Like I don’t want to know all the differences (of which there are apparently many since people complain about systemd being too “bloated”/spread out over different systems?)
Also in all the “typical” discussion on systemd vs runit plenty of people talked about serious problems with runit and sometimes said something or other about process security? Is that substantiated in any way (as in “yeah technically during the boot process runit could be vulnerable to X if executing an unsafe script while systemd can’t do that because it does Y instead” or is it more like “yeah no, people just claim X when it’s not really possible or systemd also has the same problem, they just don’t talk about it”?)
(Hopefully this doesn’t turn into yet another thread about people bashing each other over this choice since that usually leads to no information being really trustworthy unless one wades through tons of long posts external to the thread…)
Since arch is a rolling release distro, can’t you just download an older iso from when it was below 1gb, install it and then update the system?
Check this page: https://archlinux.org/releng/releases/
Arch has an internet pxe option
Use netboot.xyz and let us know how it goes. I’ve always been curious.
I love netboot.xyz. I use it all the time when setting up VPS systems. A lot of KVM-based VPSes have iPXE as a boot option so you can chainload directly into netboot without having to use an ISO.
I prefer installing the OS myself over using any images provided by the provider, so that I know exactly how it was set up.
Netboot.xyz has tools to build your own custom version of it too, with your own options. Useful if you want to host it on an internal server. It’s essentially just a set of iPXE scripts.
*cough* netboot
I was about to edit in a disclaimer about not asking me that because I’ve never used it with Arch and was half joking because it’s probably a huge pain compared to the iso. I’m sure it works well for what it does for those who use it. But I’ve never done it specifically with Arch and you’d need to use Ethernet.
It’s not a huge pain when you have a motherboard with proper UEFI support and some basic EFI shell knowledge. You just need your thumb drive with an FAT32 filesystem, put the netboot EFI binary on it, boot into the shell and execute the binary. You will need a LAN cable for this because WiFi is not supported in UEFI (AFAIK). The netboot binary will download the ISO image into memory and start it right away. An even better solution is to create the path “/EFI/BOOT/” on the thumb drive and rename the netboot binary to “BOOTx64.EFI”, put it into the folder and your BIOS will boot it automatically at startup. If not, you can select it as a valid boot partition in the BIOS menu.
