It was just a pun, cuz Arch is popular, I use Void actually 😊.
Same 😊.
Alpine is an advanced user distro. I’m sure there are workarounds for the broken stuff.
Yes, you are correct, reliable is the term needed there 👍.
Yeah, but no glibc 🤷… some of us need it, and I can’t chroot all the time.
It’s so freaking stable, it’s boring 😂.
It’s more like Arch than Endeavour though, just a heads up. Very little GUI things, especially the installer and all that. Well, the installed is TUI, so It’s not that hard to be honest.
Rolling release and stable. And no systemd… not by choice though, they’re not purists, you just can’t build it for musl.
Yep, believe it or not, it’s probably the most stable rolling release distro out there. I’ve used it for the past 4, 5 years or so, not once has it broken.
There are 2 main reasons why this is. One, they don’t roll with bleeding edge, they opt for stable, so cutting edge is more like it. And two, they don’t have something like the AUR. There is only the main repo and that’s it. The approval process for new packages is quite strict and it has to fulfil a lot of requirements, among which the software has to not just build, but also run on i686, x86_64, ARMv5/6/7 and ARM64. And not just on glibc, but also on musl. So basically, all that, times 2. Sometimes it may take up to a year to get new packages approved by the maintainers, depending on how big the package is and how integrated in the system it is.
Yep, I use it as a desktop OS. Why is it baffling?
Oh, come on, I use Void too, it was just a play on Void 😁.
Stability as well. It’s probably the most stable rolling release distro out there.
I know, it was just play on Void 😊.
Nah, it’s just play 😊.
It’s better than Arch if you ask me, I use it on all my rigs.
Prefetch and superfecth are just obnoxious services that waste disk space. You can safely disable them, there is no downside to not using prefetch or superfect on modern SSDs. On regular spinning drives, yes, they did make loading programs a bit faster.
Well, it’s under a permissive license, so there is little he can do legally, except maybe sue them for not mentioning the original project, which I’m sure they will add and that will be that eventually.
I don’t usually get my hopes up, but yes, it is a wonderfull feelling when it happens.
The real problem is catering to manufacturers demanding to have their own bespoke driver pack, often including some stupid branded management application, when it’s just the same as the other dozen manufacturers packaging of the same product. Then you end up with bloated “driver packs” and a system tray of a half dozen vendors screaming for you to pay attention to them and know that they are somehow contributing to your experience.
This is exactly why I use driverpacks in Windows (3rd party, like SDI). If the drivers are not in the pack, I download them from the manufacturer and if they’re packed with an app, I just extract the whole thing and point Windows (through manual driver update) to search for the drivers in that location. It will install only what it needs to work, nothing else.
they still sold their devices, but the users that were oblivious suffered
Or they did know, but the copy was a lot cheaper than the real thing. Hell, I’ve done it. If it does the same thing, why buy the more expensive thingie. I get IP rights and all that, but seriously, in the end, you just have to deal with these things. Unless you’re Intel, you should expect your device/chip to end up being copied. China doesn’t enforce western world IP laws, so it’s a “free for all” kind of a thing there. If you plan on doing this (making your own device/chip), your device/chip better be niche enough so it’s not viable to actually copy the design. Otherwise, copies will pop up left and right.
Yeah, I know, that’s why the kernel with the drivers is not more than 150MB. Otherwise, you’d have the Windows situation where driverpacks compressed with 7z (LZMA2, solid archive, 273 word dictionary size and 2GB decompression memory, which requires about 128GB of RAM to compress) take about 30GB.
You have to pack the driver from each manufacturer because of signatures, even though they might even be the same with other drivers in the pack… but, REV differs and oh well, the driver installer doesn’t recognize that driver as a valid one for that device.
Not mine, stole it.