Live data from Hacker News

Void Linux: Into the Void

michaelwashere.net

91–100 of 104 posts

Re: Void Linux: Into the Void

#91
post #35

I just installed Void Linux a VM. My first impression is that it feels really snappy. I am not sure if I like the cli interface of the package manager. But I will give this one a try. Can someone share their experiences regarding Void's stability? I am currently using openSUSE Tumbleweed on my desktop and primary laptop, and while I am mostly happy, things sometimes kind of break after installing a batch of updates.

I have been using it for now two years, and my only problem so far was a bad default umask with fish shell which wrongly set root-only permission on package search. Fixed with the correct umask in my fishrc.

Oh, and steam can't remember to keep me logged, but I'd probably blame Valve rather than void for this (very minor) inconvenience.

Re: Void Linux: Into the Void

#92

Earlier quoted context omitted.

Compiling Linux on computer running BSD. User has no computer running Linux, but she has computer running BSD. She builds needed toolchain, downloads and compiles Linux kernel. Its relatively easy to build BSD while running Linux. But vice versa?

Okay, so I tried it, and I'm going to say, "not easily". Started from base FreeBSD install, installed gcc and gmake, pulled down a tarball from kernel.org. Did a `gmake x86_64_defconfig` to get started. First problem: FreeBSD calls it "amd64", Linux calls it "ia86". Exported ARCH=ia86 and retried. It gets further now but appears to blow break trying to build some .S files (FreeBSD uses as from GNU binutils, but it's…

chroot into /emul/linux directory/jail with GNU/Linux libraries, headers and GCC toolchain as Linux binaries, not BSD ones, then build.

There are probably obvious reasons this wont work but without trying I do not know what they are.

Re: Void Linux: Into the Void

#94

"Because of this, xbps-src is in fact not a binary, it is a collection of very intricate shell scripts that use standard tooling available on almost any Linux distribution to bootstrap a compiler, build chroot, and XBPS itself." When he stepped away from NetBSD, I remember reading that it was because he wanted to work on a package manager. It might be that the entire raison d'etre for Void Linux is a package manager…

/consisting of/s//built from/

/bootstrap scripts/s/scripts/utility/

apologies for being a bit sloppy here

Re: Void Linux: Into the Void

#95
post #90

Earlier quoted context omitted.

Installed on an old Thinkpad X61s from the xfce4 live .iso ( Ran the installer script from a terminal in the live session - result is an ncurses dialogue that walks you through the steps. Disk already partitioned and skipped the network set-up stage and selected install from local. Rebooted into (graphical, xfce4) installed system in a few minutes. Network manager up and running, needed to log-in to local wifi again.…

It looks like you've already figured out some things like sound, wifi, and xbps, but: I found the following guide helpful in complementing the man pages: http://www.troubleshooters.com/linux/void/voidtips.htm More articles on Void from the same author, including an install guide: http://www.troubleshooters.com/linux/void/index.htm

Thanks.

I worked out that root defaults to /bin/sh before reading the voidtips page above. Also worth mentioning here that Firefox-esr (52) is installed by default from the xfce4 live iso. Firefox release (59) is also available as is Chromium (65). Some font-puggling is needed (fontconfig stuff) to get sub-pixel rendering.

In all, quite nice. I'll see how long it takes me to break this.

Re: Void Linux: Into the Void

#96
post #53

How do people compare this to Alpine Linux? I'm interested in both.

Alpine is musl only; Void has both glibc and musl variants. Void seems more desktop-focussed than Alpine, and (at least as of a year ago) I didn't have a lot of luck with ZFS on Alpine.

IIRC you can install glibc into Alpine when an application needs it but the packages are all musl.

Re: Void Linux: Into the Void

#97
post #53

How do people compare this to Alpine Linux? I'm interested in both.

I use both as daily drivers on laptops, and they are both very nice systems. Some differences: * Alpine is lighter-weight. As at least one point, Alpine packages are split into small parts (usually at least app, app-dev, and app-doc, respectively containing the actual program, the development headers, and the manpages/docs). Alpine also defaults to using Busybox for coreutils. * Void is rolling release with regular u…

The alpine userspace is also great to run in containers

my LXC container basically runs up DHCP to get an IP and a SSH server to provide a remote shell, everything else is per-server setup like webservers and stuff, compared to the ubuntu containers I run Alpine uses a LOT less memory and CPU.

Re: Void Linux: Into the Void

#98

Earlier quoted context omitted.

If you're into programming in C, and like simplicity, you might find more likeminded people there, similar to OpenBSD. Nix is more popular among functional programmers.

Nix is for everybody; I don't do functional programming but I still use Nix for everything. If OpenBSD is simple, or C is simple, and Void is also simple, then it sounds like I should not bother trying out Void.

I've explored potential Nix usage but I found it far to complicated and documentation on production usage rather lacking.

I would rather love something that explains me how to setup Nix on Alpine Linux and then deploy Nginx + PHP 7.1 with several websites. For desktop usage I enjoy tinkering with edge and upstream releases too much to consider Nix anyway.

Re: Void Linux: Into the Void

#99

A while ago I started looking for alternative linux distributions and void linux is my new darling that came out of this search. It has many binary packages, out of the box musl images, images for many of my arm boards (raspberry pi *, c2 and cubieboard for instance) and a nice packagemanager with source support and arch like syntax (it's splitted like the debian apt-get/apt-cache but worse... I still like it) If som…

I also love void. The reason I use it is for regression testing of musl. But boy the updater is so much faster than anything else.

Re: Void Linux: Into the Void

#100

Earlier quoted context omitted.

This is that case where you needed a smiley after the joke. I thought when you said that, that the reason was that it used a too simplistic init system a la OpenWRT, where you can’t check if the process is running, automatically restart daemons, etc.

but you can check if the process is running and automatically restarting supervised services is the norm.

The norm for what exactly? There are very simplistic init systems out there that do not supervise anything, and every daemon must come with its in shell script that checks if it is running. Without looking, I don’t know what Void does and the original comment here didn’t make it clear.
Post reply on HN