At first, I thought this is your April Fools joke, but it's actually their April Fools joke.
There is an error with servers. You can do your installation after it is fixed. For now, you can do nothing.
Upon further research (i.e. checking the void linux twitter) I was able to find this article Apparently void IS experiencing an infrastructure issue with package signing and repo syncing :)
I think Void Linux will run Intel-based Apple hardware. For earlier PowerPC hardware Void Linx PowerPC packages GNOME too. Void will keep your kernel more recent and more flexibly changed between kernel versions and series than other distros, an important consideration in the context of hardware support.
That's from the live-disc installer ISOs, not the repos. The xbps package manager can handle updates even with large gaps of time in between so it's not necessary to keep cutting edge images available. Here is the packages.
There are musl images, yes. https://voidlinux.org/download/
What exactly do you mean by "without bash" though. Do you want another shell? IIRC there shouldn't be any problems removing bash but I think dash is pretty unusable.
https://www.reddit.com/r/voidlinux/comments/fl6iku/shell_on_void_linux/fkwy1q2/
Doesn't look like it. The GitHub page suggests using the AppImage which will run on void.
For future reference you can check for available packages through xbps or on the website
https://voidlinux.org/news/2020/04/some-context.html
Look for "Does Void profit from xtraeme’s work?". The section is written at last paragraph of this headline.
Stuff that requires older packages (for one reason or another) I usually but into a lightweight container with its very own set of packages. Here's a nice guide, but take care to adjust the repo URLs: https://voidlinux.org/news/2017/12/advent-containers.html
Oh, and to unfuck your system, I do recommend the following: Get the full list of manually installed packages xpkg -m > pkglist
, put a copy of static xbps and static busybox at /usr/local/bin
. Exec a busybox shell exec /usr/local/bin/busybox.static ash
. Then do a xbps-remove -o
(and don't be scared by the huge number of packages, that will be removed!, that's why we got the list of manually installed packages). Now you can reinstall the manual packages xargs xbps-install.static -yA < pkglist
.
The problem with broken, unresolvable shlibs is, that eventually those will break the dependency graph, and xbps won't be able to resolve it. I have some half baked ideas for a bandaid
mode in xbps-intall, that will collect the owining packages for all broken shlibs sans version, then evaluate the results of a full system update and see if these packages get updated by that and if any broken shlibs are left after the update with the option to prune the package tree for everything that remains broken after the update.
https://voidlinux.org/faq/ https://wiki.gentoo.org/wiki/FAQ
Generally, the question 'X vs Y' is meaningless in the world of software without some sort of qualifying condition, as it is simply to broad to answer within acceptable levels of bias. Is mailx better than thunderbird? Depends on your preferences. Is nginx better than apache? Depends on your requirements. Is Emacs better than Vim? Yes.
If you do not have a specific use case in mind, you should just look into the FAQ links for the two options.
I have no idea how the input lag is compared to Windows, but I play only Danger Zone on EXWM and it feels fine.
(This is with the Void Linux distro.)
I have solved this problem differently:
I have a user-specific runit service directory with a script in ~/sv/delete-old-downloads/run
that deletes files in my downloads directory if they they are older than 2 days. It's based on snooze and runs at 05:00 every morning (or on next boot after that).
#!/usr/bin/zsh snooze -H 5 -s 1d -t timefile echo 'Deleting old downloads' DL_DIR='/home/anko/dl' FILES_TO_DELETE="$(find "$DL_DIR" -depth -maxdepth 1 -mtime +2 ! -path "$DL_DIR" -print0)" if [[ -z "$FILES_TO_DELETE" ]]; then print "Nothing to delete" else echo "$FILES_TO_DELETE" | xargs --null /bin/rm -r fi touch timefile
This replaces /tmp
's poorly defined behaviour with something that's pretty easy to understand and configure to whatever retention time you prefer.
The package name is wrong not your ending the package with “-dev” these types of packages will have the ending “-devel” instead and you can check for packages here
Different Linux distributions wanted a system with more features than the quite old "AT&T System V init" arrangement. SysV replaced earlier init arrangements, like the BSD system, with separate filesfor startup at different runlevels. SysV worked better than BSD when it came to packages installing or toggling init files, for example.
But SysV didn't have the concept of watching a process and then restarting it if it died, and a few other things. So several different inits were tried for a time: Upstart was used by Ubuntu and Fedora and CentOS for a while. But Red Hat switched to systemd, written by one of their staffers. Then when Debian decided to adopt systemd, Canonical immediately announced that it would adopt systemd as well -- to match upstream Debian, more or less. Canonical had been getting a lot of criticism every time it chose to do something different from the other distributions, you see.
So that's how it happened. Then later, more and more people realized that systemd didn't consider itself to have a narrow scope by any means, and had some other disadvantages. But that's a story for another time.
Today, the most mainstream of the distributions that don't use systemd by default might be Gentoo, which uses OpenRC. Alpine also uses OpenRC, and Void uses runit.
Not really. He dissapeared from the internet. Nobody knows where he is, but everybody is hoping that he's alright. The lead members have been working on securing the login/pass for github, irc and the webpage, which has been somewhat succesfull. There is still a lot of activity and it's not even close to dying :)
You can read more about the matter here
The real interesting piece of these minimal images (link to the Ubuntu blog post here) IMO is the container use case.
People have been talking about using Void Linux^1 as container bases for a while because of it's "minimal" nature; the thought being: for a base, your looking for a minimal OS, everything else that's unused is just attack surface.
The concern with Void (which I admittedly don't know much about) seems to be the fact it's maintained by a small team and people are worried about the ability of a small team to catch->patch->push security fixes (after all, security is the reason people seem to be using it.)
Canonical however obviously has the resources and incentive to dedicate man power towards these minimal images for containers. IMO it's pretty exciting these efforts are being made for that reason alone. I'm not sure boot time makes a huge difference when you're spinning up VMs to scale horizontally anyway considering those VMs are ether purchased outright or billed hourly and you can just adjust your volume trigger to accommodate boot time (which I believe is already standard practice.)
That aside, these benchmarks are far from comprehensive and less than relevant to production environments as noted in other comments in this thread.
Edit:
^1 and Alpine though I'm not sure the maintenance concerns are there.
AntiX. Lightweight, part of the MXLinux community, nice tools. Not the newest packages, however.
Void has newer packages and lots of unusual options (musl, runit, etc.).
If you can wait for 15.0 to go stable Slackware would also be good.
I'd run Openbox on whatever distro you use. There are lots of lightweight apps that go well with it, like Tint2, jgmenu, etc. Master the autostart file and you can have very fine-grained control over a nice-looking, lightweight system.
> xbps-install -S discord
False. There is no discord in repos. To check what's available there, one can always use https://voidlinux.org/packages/
OP: you need to install Discord outside of package manager. It's available on Flatpak and the official site provides .tar.gz archive. Your choice.
From https://voidlinux.org/ > Void is a general purpose operating system, based on the monolithic Linux kernel. Its package system allows you to quickly install, update and remove software; software is provided in binary packages or can be built directly from sources with the help of the XBPS source packages collection.
>Void Linux is an independent distribution, developed entirely by volunteers.
>Unlike trillions of other existing distros, Void is not a modification of an existing distribution. Void's package manager and build system have been written from scratch.
Its literally the 4th menu entry on every page: https://voidlinux.org/packages/
> I really want the faster boot with runit but it will all be in vain if I can't even use the applications I need.
The thing is voids boot time is not necessarily faster, early boot with void is sequential and there is no way to really optimize it further. While you can probably cut down systemd boot times by looking at systemd-analyze and tweaking a bunch of stuff.
Distro: Void Linux 10/10
Terminal: st (htop, cava)
Apps: Lemonbar, feh
Cool Wallpaper: Void Exodus (full website)
Compositor: Compton-tyrone
also yes i know that the battery is at zero percent lmao
It looks like Xenocara isn't packaged yet https://voidlinux.org/packages/?arch=x86_64&q=xenocara
So we could start from opening an issue on their github page with a package request and then open another issue asking for Xenocara to be the default one? Or maybe we could mix these two issues into one.
Luke's auto-ricing script has a manual built in for the shortcuts the he puts in his dotfiles and such, which I imagine you know since it's mentioned on larbs.xyz. That should contain most or all of what you need to know to use LARBS. The best way to learn Arch is to set it up yourself technically, but most of what you'll learn in Arch can be learned in virtually any other distribution, barring the minutia of configuring some things to the point of usability.
Also, if you're just installing it because Luke uses it and you haven't been keeping up, he uses Void now, and he also has a ricing script for it that uses more of the Suckless tools rather than just st like his Arch script does. All that being said, Luke's videos are good examples of things you can do in Linux with the programs available. Most of the stuff you'd do on Windows is doable with just as much ease with most distributions on Linux, so there's not as much to learn. Mastery of the command line and configuration files is what separates a Linux user from a Windows user properly, not the ability to change what operating system you use Chrome on.
I'm unsure if it's going to help, but regarding the last problem, try blacklisting the nvidia kernel module - I'm no expert in these regards, but at least it should be revertable if it doesn't work :)
https://voidlinux.org/download/ leads to https://a-hel-fi.m.voidlinux.org/live/current/
There's a lot to choose from so assuming x86_64 you want one of these:
I think cross compiling will work, It just needs some additional setup most likely. This void Linux post caught my eye yesterday. They suggested using qemu to cross compile some of their packages, basically using qemu-arm-static to run the build commands (without starting up a full vm). If regualr cross compiling doesn't work, you could try that as well.
As a programmer - with more than 30 years under my belt - I have been using Ubuntu, Mint, Siduction, Netrunner, Suse Tumbleweed, Arch ... but finally settled on Void Linux. I want the newest software, especially for development (C, C++, PHP, Node, ...) but I also don't want to spend time on configuration/management of my machine. Void Linux is perfect in that regard:
Rolling release, with a super fast package manager (XBPS).
Small and focused distribution.
Extremely fast boot times due to runit (instead of systemd)
Not a fork. But it's own thing.
Read more here: https://voidlinux.org/
​
It is surprisingly stable for a rolling release. And it suits my needs perfectly. Perhaps it will also suit your needs.
It doesn't make assumptions on your behalf. That's the main thing that I like about it. Give it a try. :)
GNOME should work just fine on Void.
As far as I know.
No issues here, basic software.
Not that I'm aware of, but I don't bother with it on my workstation.
Everything I've needed for basically any file format was in the main repo, with out having to build restricted packages locally.
https://voidlinux.org/packages/ - search here, and check that there's a -musl variant.
Seems to me that someone who has a true interest in something should research a bit more than you did. A very quick and simple Google search for Void Linux would turn up Void's page, which answers the questions you have; including that it is a Rolling Release, it is NOT A FORK, uses runit, that XBPS is it's package manager, etc.
​
If you are truly looking at changing your distro, or trying something new, Google it, go to its page, read up on it. Many lower-level questions can be answered quickly. Not to discourage asking questions, we welcome all people to try Void, but just look it up.
Thanks, Void looks promising, but this concerns me on their news page: https://voidlinux.org/news/2018/05/serious-issues.html
"The current project leader has disappeared. We have had no contact with him since the end of January, and no meaningful contact for well over a year. This itself would be concerning, on its own but no threat to the project.
The problem is that we currently have no ability to manage some of Void’s central resources."
Is this still a problem, going forward?
Rolling release without systemd (I don't have anything against systemd but for some it's a benefit). It does boot fast and it's easy to manager what is load or not. As for the packages you can search their package list on their website. You can of course install flatpak and others too. The installation handbook is easy to follow, the wiki is not as complete as the archwiki but still useful.
Have a look at this. Looks like flatpak is in the official musl repo so that might just work for you. You can use this page to search for available musl packages, just select "musl" from the dropdown.
I've used virtualbox on void, Been using qemu and virt-manager lately. No idea about games. You can search the void packages here. Maybe hunt through there for anything you're using on arch and see what you find.
Where did you get the iso you used? I recently tried to install with the unofficial ISOs and had the same problem even though I've used them before. I got an official one from here and it worked fine. Big update once you reboot, but otherwise good.
I like Void
It's rolling, stable, independent and different from a lot of other distros.
Flexible package manager and solid toolkit for building from source, musl support, multiarch, runit for init & supervision.
MocaccinoOS looks interesting but I've not played with it yet.
before leaping I would install it on a VirtualBox then see. Also, make a list of all essential packages you now use on your Arch box then check if they are available here: https://voidlinux.org/packages
If not, you may be able to install them (from source etc. ) with a bit of tinkering. e.g. brave browser, Nord VPN. Latter (Nord VPN) is not perfect on my void system, sometimes shows as connected when I cannot ping any internet address. So I have to disconnect and try the connection again.
Also, Void does not come with logging enabled as default. It's a 'build your own' distro apparently. So, I would look at enabling logs, just in case you run in to any issues at least you will have logs to go on. No distro is perfect. No good pretending it is. I've posted on here a link to a youtube video on how to enable logs on Void.
Download voidlinux base live-image.
There won't be anything pre-installed, just tty.
Rest is up to you, install packages of your will.
I mean it by saying anything, even vim or nano is not included.
Void base install is not bloated.
Void Linux is an increasingly popular distribution that ditches systemd (ironically despite being one of its earliest adopters) for runit. Some advantages, from their documentation, of using runit include:
>a small code base, making it easier to audit for bugs and security issues.
>
>each service is given a clean process state, regardless of how the service was started or restarted: it will be started with the same environment, resource limits, open file descriptors, and controlling terminals.
>
>a reliable logging facility for services, where the log service stays up as long as the relevant service is running and possibly writing to the log.
Void Linux is extremely lightweight and advocates a minimalism that echoes the original UNIX philosophy. Its use of runit rather than systemd grossly reduces the complexity of its userspace while suffering few if any consequences (some applications more heavily dependent on systemd APIs require patching, but many have been successfully - such as Gnome). Some users prefer this simplicity as an architectural principle.
Boring answer but openssl because it's the most common one and building software against it is simpler.
Void Linux used to have LibreSSL but not too long ago the maintainers decided to switch to OpenSSL. There is a blog post about it here: https://voidlinux.org/news/2021/02/OpenSSL.html
Just know that you should learn the command line if you want to come into Linux, it’ll be very handy.
Here, follow my lead and Enter the Void :) (or use PopOS for a more friendly starting distro if you feel intimidated by the command line)
See the news about OpenSSL and kernel hardening.
If this is responsible, try removing slub_debug and page_poison options from the grub kernel command line in /boot/grub/grub.cfg directly or reconfigure grub after removing those options from /etc/default/grub
C library diversity
Void Linux supports both the musl and GNU libc implementations, patching incompatible software when necessary and working with upstream developers to improve the correctness and portability of their projects.
I am currently trying void and I can recommend it. I have honestly had far more issues with out-of-date packages on debian than not available packages in void. The only thing I noticed was missing is qtile (which I wanted to try out, but oh well...). xbps is very fast and has a nicer interface than apt. runit also seems to be faster than systemd. It is available for a few architectures (x86_64, arm6, arm7, aarch64, i686) and you can choose musl over glibc if you want to. There is an installer and flavoured images, but I only did the ROOTFS tarball (chroot) install, which is well documented. I had no issues on x86_64 and aarch64 (RPi 3, RPi 4 is not working yet). Everything you need is on https://voidlinux.org/. If you have a spare drive and the time, I can only recommend you give it a try!
I was pondering this as well when I was reinstalling.
I found this
https://voidlinux.org/news/2020/12/pam-1.5.1.html
There has been a small little change. So in order to make sure even root is allowed to log in you need to things in this order:
If you are looking for a lightweight distribution probably Ubuntu is not a great choice. However there is Puppy Linux which is 300MB and gets packages from Ubuntu. I've never used it, so ymmv.
Otherwise you can install Void Linux. A basic installation should require no more than 700MB. I've also never used it but I've heard very very good things, both regarding the distro and its community.
If you go with Void, you need to know what you are doing. Some basic knowledge of Linux, the CLI and filesystem/bootloaders is required. It also has different repositories, a different package manager and it doesn't have systemd.
> So there were personal attacks in #xbps? Or only in private communications?
Both. And on GitHub.
> By "comes back" do you mean "is not banned from public channels"? Because that's all I'm questioning.
Given how aggressive they were when they first they came back, yes. After a lot of pressure they were given a commit-bit on the new project (Void had to move projects because they were gone so long -- they were not a part of the new project, because they were gone).
This whole ordeal has been grating and tiring.
It is like a tablet with a swinging keyboard.
You may want to try Void if the arch. matches. https://voidlinux.org/download/
The musl based editions run even lighter, and if it does work it will run circles around any Debian. The Ram will just limit any multi tab browsing or similar hi ram use application.
Sorry I am not that familiar with arm acrchitectures
Could you provide more context? The only thing I know about this situation is detailed in this void linux news article, but was wondering if maybe you wrote something up about your side of the story? It sounds as if they were frustrated so much that they don't want to converse with you. Have you tried reaching out to these members, having one-on-one's with them? Maybe that will clear things up
check out void linux, if you haven't yet. it follows a stable rolling release model. it has is own features (and some quirks maybe, like every distro haha), but works perfect for me. documentation is pretty sufficient and keeps growing.
it's definitely less stressful than arch imo. it's "chill" and doesn't cause much issues.
Feel free to take a look at Void. You will immediately notice the design will restore your desire to have fun once again. The installer is also ncurses-based, and you also get the feeling of using BSD-like scripts again. Runit is sane, robust and easily configurable, so you won't have much headaches. The package manager (XBPS) is lightning fast and efficient.
Overall, it's a wonderful projects for those of us who had our fair share of joy with both Slackware and the BSD family.
It's one of the easier ones to install I'd say but it's not much different from distros like arch. It boots up hella fast tho (because of runit). Most issues I've had were easy to resolve by either asking in #voidlinux or using the documentation on https://voidlinux.org. I never personally tried gentoo tho so I can't tell how it compares to that
Thanks for letting me know!
I can confirm this "Void does not accept donations. We appreciate the efforts of those that reach out from time to time wishing to support the project financially, but our expenses are minimal. If you want to contribute, you can help by updating packages, reviewing issues, or generally being a part of the community. If an individual maintainer chooses to solicit or accept a donation for their work, this is done separately from the project. International tax law is a complicated beast, and as a project we’re not comfortable accepting donations until we have the infrastructure in place to show where the money goes, and provide you with appropriate documentation."
It's not really necessary for a rolling release distribution like Void to have an up to date iso package as your system will update to the latest state during installation. You can just go ahead with the recommended iso package you found on the website
There's a process for that on the page, though I haven't walked through them to be able to tell you how it works. I have a pretty simple single-user desktop, and I haven't checked on the few things I need from the void packages repository since I installed them. Really, I think it was just rox-filer and spotify. Everything else I found via the usual repository search.
I finally got a Telegraf–InfluxDB–Grafana stack up. More importantly, I taught myself Salt so I could push changes to /etc/telegraf/telegraf.conf
to my three servers with minimal bother.
The servers:
As others have said: yes, it's available.
You can use https://voidlinux.org/packages/ if you want to know about void packages and can't use xbps (eg. you don't have an installation handy).
You were indeed correct. After installing those two packages, `silver` installed perfectly.
I have another two questions, that aren't really connected to this one, but I don't think those deserve a new post.
Thanks for your help!
You could always go to https://voidlinux.org/packages/ and search the musl repo.
A search for mega in the x86_64-musl repo shows both MEGAcmd and MEGAsdk available.
>a) Runit manuals are now here, here and here. b) Why haven't you described your issue here firsthand?
a) Never thought of it as looking it up as the service. Thinking that Void is known for being shipped with runit as the default init system, it never occurred to me that it would be listed under services and daemons.
b) Mainly because after running the system like this with the issue still at hand it is kinda embarrassing. But also since most of the time when wanting to post an issue I have, I usually fix it myself by researching and digging deeper into the necessary documentation.
And with Github. I'm not really into github. It's just not my cup of Tea. At least not at the moment.
Creating a your own void iso using void-mklive might be a good idea. You can use it to install as many packages as you want into the iso and then use that it to install void into your computers. And that includes the graphical environment as well. I prefer xfce as it's light, stable but still has a good amout of features, but i hear LXQT, LXDE are even lighter. You can search the void website for the packages you want to install.
To install mk-live, use your void linux laptop with internet access:
git clone https://github.com/void-linux/void-mklive, cd void-mklive, make, and use the ./mklive.sh script. You'll need to install dialog if you want to use the void tui installer.
sbin and bin have been merged in 2015:
https://voidlinux.org/news/2015/07/usr.sbin-transition.html
If you remove the void-installer
(not sure why you have it on a installed system) on a reboot the directory is going to be replaced with a symlink.
Alternatively just remove the /usr/sbin
directory and possibly other directories like /sbin
and /bin
if they are not symlinks yet.
I don't know how the packet manager for Void Linux works, but flightgear does appear if I search for it here. I'd install that and forget about compiling it.
Btw that is a memory-related error, so chances are it is a programming error (such as trying to free
a pointer twice). If you still need to compile from source, try downloading the latest stable release and not the development branch straight from their repo.
My own experiences of the Void community, having started using Void in the second half of last year, is that it's far from toxic - in fact, it's one of the least toxic communities i've yet experienced in my >20 years of using Linux and FOSS, with many knowledgeable and experienced people who are also friendly and helpful. A number of people are focusing on the deleted threads you mentioned, and not on the context described by /u/maldridge in this post. People who haven't been actively following what's been happening in the Void repos, including the void-packages repo, over the last several months, should refrain from making assessments based on such limited information.
I don't think Void is that difficult to install, configure and use, specially if you download a flavoured ISO (there's one with LXDE, which should be the lighter). And it has most common software (and a lot of the less common) already on its repos, no problem on that part. You can search anyway in the Void packages page for the software you use to check if that's there or not before deciding. https://voidlinux.org/packages/
That said, Void is absolutely NOT as noob friendly as others. The installation uses a term interface (but it's pretty straightforward) and some manual intervention and terminal job is generally required. Its package manager has some front ends, but is better managed -and usually advised to- in a terminal. It's rather easy to use though, you can do almost all your maintenance, installation et al with perhaps half a dozen commands.
Pros: musl or glibc to choose (if in doubt, choose glibc), runit as init (no systemd) so it's light and fast, very lightweight and KISS, rolling release (install once and no reinstall ever), supports partial upgrades, rock solid, nice community (check Reddit sub)... I have no cons. ;)
Anyway, if your distro works for you stick with it. Only try Void if you have the time, and feel like reading some docs, learn something new and are willing to sort some (possible) difficulties. If you finally decide to try it and have some doubt, ping me and I'll try to help. :)
This thread is a few days old, but I once fixed a similar issue that may help if you haven't already resolved this issue.
I once made the mistake of forgetting to add a /boot
entry to /etc/fstab
. The system would boot using the kernel in use at the time it was installed, but because the /boot
partition was not mounted, /boot
was a useless directory under /
that had no impact on actually booting up. Any changes to this directory had no bearing on the shadowed actual /boot
partition. Since this was just a testing VM I was blissfully unaware of my mistake until one day a kernel module was replaced that was incompatible with the version that booted and boom.
tl;dr ensure that /boot
is listed in /etc/fstab
. If that turns out to be the issue, I believe xbps-reconfigure will be necessary to ensure the kernel is properly installed.
No.
I'm using the package manager of the distribution I use.
In other words, I installed elixir from xbps in void linux
The error says that updating libcrypto would break the other packages, so I took a look at my versions (also checked here for i686 systems: void (packages)) and they are:
libcrypo45-3.0.2_2
libressl-3.0.2
libtls19-3.0.2
Unless you explicitly need your versions of libressl and libtls, you can try to remove them (xbps-remove
) and reinstall them (which should update to the current version).
It might also work to explicitly update libressl and libtls before doing a full update.
"The package maintainers have abandoned it" is incorrect. The person is likely refering to the event that happened almost 2 years ago where the original creator of Void stopped being active online with little contact with the rest of the team.
That led the team to create a new github organization (void-linux instead of voidlinux), and to change the website (voidlinux.org instead of voidlinux.de which was eventually purchased by someone else for their blog).
Afaik everything has already been migrated and the rest of the team was still quite active.
Now, the origional creator is semi active again, and packages are still being maintained and updated. Some package maintainers have left to move on to other distros (package maintainers can be regular users) and their packages are "orphaned" and can be adopted by other users who are willing to keep them up to date.
Refrences:
https://voidlinux.org/news/2018/05/serious-issues.html
https://voidlinux.org/news/2018/05/irc-back.html
https://voidlinux.org/news/2018/06/GitHub-Organisation-is-moving.html
If I am mistaken please let me know.
If it may be of help, you can search for packages here: https://voidlinux.org/packages/ And remember that, if you need some non-free package(s), you may search first if it is already in the nonfree repo, and enable that repository if you do want to install it/them: https://docs.voidlinux.org/maintenance/repositories/official/nonfree.html For building external packages, please check the proper documentation (linked here: https://docs.voidlinux.org/xbps/packages/building.html ).
Knoppix (hardly a general-purpose distribution) and Void Linux have migrated away from systemd in favor of other options. Other distributions never had it at all.
If you come from "arch'ish" distributions, you'll find void straight-forward and simple. It was also my "evolution" (I still use arch, freebsd and some other stuff)
Stuff to take care about
Quoting from the download page
>The x86_64 images have these requirements:
>
>EM64T CPU, 96MB RAM, 350MB disk, Ethernet/WiFi for network installation.
>
>The i686 images have these requirements:
>
>Pentium 4 CPU (SSE2), 96MB RAM, 350MB disk, Ethernet / WiFi for network installation.
So really most modern (2005+) machines would work. I managed to get it to run on an old i686 1GB ram laptop from 2003 with a few kernel tweaks.
As others have said, if you do have the hardware, there's no harm in trying.
Void - the distribution that us Arch'ers switch to upon realizing how bad systemd is - has had the package for quite a while now.
Trolling aside, this is a great achievement for Monero - and Arch!
Apart from "full package but you compile it all" Gentoo and "literally just the kernel" Linux-from-scratch, I know of Void Linux and KISS Linux, both of which seem to be even more minimal than Arch.
There used to a dedicated forum that was ran by a Void Linux user, but it was shutdown. The forum link in the navigation bar on Void Linux's website used to link to the forum. See: https://voidlinux.org/news/2018/11/forum-is-down.html
For future reference, the wiki is being replaced with https://docs.voidlinux.org/, so I'd recommend pointing people to the packages page if you want to find if a package is available.
Have you installed the firmware package required for your WiFi chip?
A search on https://voidlinux.org/packages/ with "firmware" as keyword might help you find the appropriate package.
It looks like Xenocara isn't packaged yet https://voidlinux.org/packages/?arch=x86_64&q=xenocara
So we could start from opening an issue on their github page with a package request and then open another issue asking for Xenocara to be the default one? Or maybe we could mix these two issues into one.
If you go to https://voidlinux.org, click on the Downloads section, and then scroll down to the Tier 1 and Tier 2 mirrors, you can get a recent iso. Just follow the link to one of the mirrors, click on the live/ link, and the most recent date (I think it is May 26, 2019). There you will find the live isos for x86_64, i386, etc.
xbps bug results in missing /bin/sh
Just recently. All rolling releases are going to break something sooner or later. You know, glass house, stone throwing, etc.
I am disappointed by all the responses I got so far. For readers from the future:
Do not be tempted purely by answers to this post. Most people here ignored details of the topic and don't realize the cost of maintaining distro-specific patches in major distributions like Debian or RHEL. Check out rolling-release distributions like Void Linux, especially its musl configuration. Think about Alpine, which uses it primarily and which is used heavily by DevOps across the world as a Docker image base.
Outside of anonymity scope, check out Tails, as it achieves security through anonymity. It is harder to perform even targeted attack against its user because of how uncommonly this system behaves. Its maintainers take CVEs truly seriously as well.
Do not use Qubes because Xen is a mere joke, from the perspective of security. And they use old Fedora releases as the default image.
Finally, take a look at hardened Gentoo guides. It gives the most control to the user without making it much harder to manage, to be honest - portage is a good package manager and USE flags are a blessing.
Oops, sorry for the delay in responding.
Hmm. I'm not sure why the vim-huge
package doesn't for you. According to https://voidlinux.org/packages/ it should definitely exist.
I'm afraid I'm at the limit of what I can try to help with without knowing a bit more about Void than I do. I'm not entirely sure how to get it working from here, and I apologise for that :/
There is a post regarding the whole philosophy of Void by one of the core devs. The last paragraph should answer your question about the docs.
The forum though has never been hosted by any Void service itself. I will link you to the official news why the forum has been gone.
Not as such. There's a quick breakdown on getting X11 working for non-"standard" window managers and such here: https://voidlinux.org/faq/#elogind
# xbps-install -S elogind
I remember it giving me issues with my initial 2016-running distribution build, but it's been working fine for me since I rebuilt from a 201707 (as memory serves) glibc. The VGA boot splash screen is different- the old one is black with a very minimal Void logo, but otherwise most of the userland is about the same.
The mirrors are all listed here: https://voidlinux.org/download/
Maybe you'd have better luck with one of the N. American mirrors? E.g. http://alpha.us.repo.voidlinux.org The default is a German mirror.
Can somebody make since of this void announcement, like what they did, etc? I was looking into Pam for my users, and I cam across this.
So! i read the response of KinkyMonitorLezard and i disagree in a few points (sorry if my english is bad somtimes too 😖)
My experience with Void was and still is a success, I love this distribution, for me the installation was much easier and simpler under Void than under Arch, even if under Arch it wasn't as complicated as everyone suggests.
Regarding package management and availability I was very scared of that too but to my surprise I found all the packages I was using on Arch under Void, it is true that I rarely use obscure packages but I doubt that a basic user will not find what he is looking for under Void
Common non-free packages are there! you just need to add the repository, for example if you want to add the repo non-free just do >sudo xbps-install void-repo-nonfree and voila!
Personally I have found all the documentation I needed on https://voidlinux.org and https://docs.voidlinux.org and if you want to see if your packages are available before installation just type their names here https://voidlinux.org/packages/
Runit is excellent and very simple, Xbps too and very fast frankly very happy to have made the big leap to Void I would never look back again I can only recommend it for fans of minimalism and cleanliness 😄
In case you're like me and have never heard of Void
They're not a fork of anything, they wrote their own package manager and service manager. Not sure why or what niche they're trying to fill but hey something new 🤷
>Not a fork! Void Linux is an independent distribution, developed entirely by volunteers. Unlike trillions of other existing distros, Void is not a modification of an existing distribution. Void's package manager and build system have been written from scratch.
see what version of libgconf-2 you have installed. Its possible your minecraft binaries are compiled for the wrong version. Or you are missing it.
I cant seem to find a 'libgconf' package at their package search site, but it may be under another name.
Quite a lot actually. It uses its own package manager, replaces OpenSSL with LibreSSL, offers a musl option alongside glibc builds, supports many architectures (although not quite as many as Debian), and uses runit as its default init system and service supervision suite.
Check out the homepage, https://voidlinux.org for more information.
Modify your mirrors in /usr/share/xbps.d/00-repository-main.conf
Official mirrors here https://voidlinux.org/download/#tier-1-mirrors
Include /current and /current/nonfree
xbps-install -Syu
xbps-install nvidia
It might say it skipped rebuilding the 4.18 kernel because you don’t have headers but from a fresh install -Syu should get you 4.19 and the headers.
Reboot.
> The package search (https://voidlinux.org/packages/) is also broken.
Really? What a mess! The Void project could definitely use a full-time web developer on staff.
Yes, I am using musl. I'm not really interested in using the nvidia drivers. I installed void on this laptop with the specific intention of not putting myself through the hell that is optimus / nvidia / bumblebee. I'm simply curious about the current state of affairs regarding the nvidia drivers for Linux. It seems like it was easier to get optimus working a few years ago according to what you're saying.
The package search (https://voidlinux.org/packages/) is also broken.
Are you using musl? nvidia doesn't exist for musl, only glibc. Also, you'll probably need to 'xbps-install -S' to synchronise the package list on your machine.
That's weird. It doesn't show up when I search for it on https://voidlinux.org/packages/ and performing 'xbps-query -Rs nvidia' with non-free-repos enabled doesn't find anything either.
Am I missing something?
Yes, this is possible. Good resource is: https://www.linuxsecrets.com/voidlinux-wiki/Macbook.html
Unfortunately the information regarding the trackpad is potentially incomplete dependent upon your model of trackpad. There is a bug in void that appears to have existed for a long time as described below. The solution described (manually adding the trackpad driver) works: https://github.com/voidlinux/void-packages/issues/3897
You will need internet to get the various packages (usb Ethernet adapter) The manual method of installing the Broadcom wl driver given on the wiki didn’t work. To get the “official” Broadcom driver you will need to enable the non-free repos and download Broadcom-wl-dkms. https://voidlinux.org/usage/xbps/#subrepositories
Hope that helps
Interesting read up
https://en.wikipedia.org/wiki/Void_Linux
It's really appealing that glibc and other components can be swapped out, I'll keep an ear out for Void and definitely keep it on my radar when I get some free time to explore linux without systemd.
I especially miss fbcondecor and the console / tty backgrounds from OpenSuse, I really miss that (hin't hint /r/unix_porn -- you guys go do the heavy lifting I know how far you'll go to tweak that http://jeandamiendurand.free.fr/debian/splashutils/ ).