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.
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...)
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.
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.
If they have any sense they'll not try to find out what's on it and send it straight to whatever electronics recycling is available.
Sticking a USB device of unknown provenance into your computer is just asking for trouble. (When you think about it, we even take a risk every time we buy one.)
Sure, you know it's harmless, but they don't know that, even if you tell them. Who are you? You're just someone who used to live in their house. As far as they know, you might be a freak who gets a kick out of leaving dodgy devices around for people to find.
I switched to using a NVMe SSD (M.2) in an USB enclosure. Bit larger than a stick but otherwise day and night. Make sure the enclosure chip is Realtek or Asmedia not JMicron.
They wear out if you write data on them, reading doesnt matter. if you just need them for install, you just write once and you can install the same arch on millions of computers
The key to make those cheap drives last a bit longer is by keeping as much free space as possible. For extra shitty drives, just leave half of its space alone (though they might die on their own no matter what you do).
It's true that you're often playing the lottery with them, that's why I just buy a few at a time. Like right now in the US, you can buy 16GB USBs for $4. The last three I've bought have lasted over 5 years each, thankfully. But I've had ones that have been bad right out of the package. That's why I just buy from places that have at least 30-day return policies.
Maybe if you use a file system that supports compression, e.g. btrfs, bcachefs, F2FS, squashfs, or EROFS. Of course, you'd need to add a separate FAT32 EFI System Partition for the bootloader, not sure how to do that.