I was drawn to it because it doesn't use systemd. (There seem to be a lot of people who dislike systemd.) Void uses runit instead of systemd. This has made it (for me at least) easier to use than Arch/systemd.
It was also one of the first to adopt LibreSSL.
The main downside for me is I have to manually install browsers. Void's packages for desktop software is sometimes out-of-date. But, I'm willing to overlook it because of all the other positives.
Thanks for that. It says: "In other words, one can benefit from existing systemd unit files through automatic conversion in many cases." I'm worried it means, "many, but not all" cases.
There is also Manjaro Openrc. But, my buggy experience with it made me decide to go with a distro designed from scratch to use a different init system. Do you use Archnosh on a daily basis? Any issues converting systemd unit files over to nosh?
I don't use Archnosh because I do not possess an Arch Linux system. I do use the nosh toolset on a daily basis on Debian, FreeBSD, TrueOS, and OpenBSD.
I don't think that the conversion process not being capable of automatically converting every possible unit, just most of them, is something that should worry you. I suggest that you begin by reading the manual page on the subject as well as the sections on conversion in the nosh Guide and the worked example in the blurb:
That there are some outliers doing oddball things that this will not cover, requiring you to get your hands dirty writing run+stop+start+restart programs, is only a worry if you worry about writing such programs in the first place. If that is a worry, then observe that you have the same worry with runit. Ask yourself if you are worried about this with runit. (-:
At the time of writing, the nosh toolset has just over 540 pre-supplied service bundles, not counting log and etc services, from ModemManager through initctld to zfsd.
An interesting and somewhat topical example of the automatic conversion in practice was when I took the now-infamous example of a systemd unit that declared User=0day, ran it through the convertor, and started the resultant service. You can see what happened, and (more importantly) what did not happen:
You're right about converting init files not being a problem. Looking back, it was a stupid statement on my part. Even converting the few services I run to nosh/s6/runit/etc. from systemd wouldn't be a problem... and it would be fun.
What I really want to say is: Arch is heavily tied to systemd and I don't want to use any systemd-based distro, even if I can run something alongside it.
Another option (albeit fairly new) is Artix, which is an Arch-based distro with OpenRC. It seems to have alternate repos for the base system while still having the default Arch repos for "community" and "extra" (as well as AUR compatibility, of course). I had some trouble using the graphical installer when trying it out on a spare hard drive, but booting the text image and just doing an Arch install as normal with pacstrap (which I prefer a anyhow) worked smoothly, and I haven't had any issues with it after a couple weeks trying it out.
(Writing this from a Void Linux installation:) I don't know about Chromium, but Firefox 55 was no more than a week late, which I can totally live with.
You're correct. In the past the Firefox updates were very late sometimes (based an anecdotes I've read), but the situation has improved and should keep improving as more people adopt Void.
(I manually install Google Chrome and Opera. It's difficult for package managers to maintain them because of licensing and other issues.)
On second thought, you're right. The statment is wrong on my part. Systemd seems to have pleased the Arch developers and made their lives easier.
I was trying to say: Void seems easier to use and stable.
Thanks for pointing this out. Sorry for my carelessness.
(I still would never use a systemd-based distro. I've had fewer problems since leaving it. And I've read too many horror stories to go back. And I suspect it led to many if the problems I had installing and booting. Void has a smaller community than Arch and Ubuntu, yet installs and biots up faster on my junky machines than Arch and Ubuntu. Granted, I can't blame systemd for this.... but I'll include it anyway in the lineup of suspects.)
The Arch wiki doco is also wrong, which probably does not help. There's a glaring error in the first paragraph there. There are in fact nine places where system-level unit files are searched for, not two. Three are in the systemd doco. Three are intentionally undocumented. Two are build-configuration-dependent and usually the same as some of the others. And one was erased from the doco for an clearly invalid reason.
Not just Broadcom, but plenty of other networking SoCs use MIPS --- and in big-endian mode too. They're probably the only commonly encountered BE systems today.
> They're probably the only commonly encountered BE systems today.
Freescale's embedded PowerPC (e500 et. al) controllers are used in automotive powertrain ECUs (those that do not use TriCore), though it's debatable whether this counts as common.
Yes, what's funny about that is that is a Chinese designed processor which at first refused to pay royalties to MIPS. FYI for whoever: MIPS (the company) had major financial issues and was purchased by Imagination tech in 2013. But their patents ended up with a group of companies, including some which went to ARM. MIPS as at one point the fastest CPUs (from a millions instructions per seconds stand point) you could buy, and were in high-end SGI boxes.
I'm guessing they looked at other package managers, didn't like a bunch of decisions, and decided to write their own: XBPS claims it's totally compatible with POSIX/SUSv2/C99 standards, and released with a Simplified BSD license (2 clause). Other features: https://wiki.voidlinux.eu/XBPS#Features
It's very easy to write templates for new packages and the maintainers stay really busy, so I've found that void has more packages in the main repo than almost anything else, despite its lesser popularity.
The motivation comes down to little more than a couple of the main Void developers owning a witiboard. Perhaps there's other hardware floating around but there was quite a bit of discussion on IRC surrounding the witi.
I can't think of a single system that runs MIPS instructions.
Also, what does this distro do differently from the other 1000+ distos?
Why VOID? Why not something else?