Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Void Linux: Into the Void

michaelwashere.net

Post reply on HN
Print view View original

51–60 of 104 posts

Re: Void Linux: Into the Void

#51

Post by pknopf »

Vaelatern wrote: post #49
pknopf wrote: post #25

Hey guys. FYI, Darch (my project) has support for VoidLinux. https://godarch.com/concepts/recipes/distributions/

Question - is there any reason your project can only be used on x86_64? I can't readily find documentation about godarch that suggests it even requires 64bit hardware.

The base docker images (https://github.com/godarch/distributions) only supports x86_64. Docker images have support for having multiple embedded rootfs tarballs for multiple platforms, but it gets complicated. Maybe in the future.

Also, you have to build your recipes on the same target arch that you are going to deploy to. Irrelevant to your question, but something to note.

Re: Void Linux: Into the Void

#52

Post by ams6110 »

alxlaz wrote: post #5

I usually refrain from distro- (and editor-, and language-) related discussions but I think Void Linux deserves an exception here: - Everything is remarkably simple, (mostly) well-documented and straightforward. - Friendly, dedicated and very knowledgeable community - Open development, very few hooks to jump through if you have something to contribute - No systemd, so: rebooting your system isn't a lottery where, if…

90 seconds? You're lucky. I have machines running systemd (RHEL 7) that simply will not reboot unless I use the --force option. They will just sit there with a blank screen forever otherwise.

Re: Void Linux: Into the Void

#54

Post by nicklaf »

keithpeter wrote: post #19
fouc wrote: post #9

Nice, my past distros of choice were slackware & archlinux. This feels like a successor to those. I'm sold.

Slackware and Arch are still very much alive as projects. By 'successor' do you mean 'works in a similar way and I happen to like it better' or is there something that you think Void has got that slackware and arch don't have? PS: downloading the void live .iso now for a bit of distro-hopping on a spring morning.

As someone who switched from Slackware to Void several months ago, Void boots far faster. Also, though I haven't used Arch, Void really feels like a combination of a slimmed down Slackware + NetBSD (the author of Void is a NetBSD commiter IIRC). Of course, Gentoo portage was inspired by BSD ports, which I believe was an impetus for Arch's package manager.

I don't know what the story is for Arch, but I find that Void strives to make the system dead simple: it is even more minimalist than Slackware (it feels more like a BSD). It isn't just small, though: it has good defaults. There isn't a whole lot of documentation beyond the well-written man pages, and I believe this is in part because it isn't necessary.

Like Arch, though, it is a rolling release system: an update may break your system, and package indices quickly become stale as old packages are deleted from the server. You can easily fix this by updating the index.

Re: Void Linux: Into the Void

#55

Post by Vaelatern »

pknopf wrote: post #51
Vaelatern wrote: post #49

Earlier quoted context omitted.

Question - is there any reason your project can only be used on x86_64? I can't readily find documentation about godarch that suggests it even requires 64bit hardware.

The base docker images ( https://github.com/godarch/distributions ) only supports x86_64. Docker images have support for having multiple embedded rootfs tarballs for multiple platforms, but it gets complicated. Maybe in the future. Also, you have to build your recipes on the same target arch that you are going to deploy to. Irrelevant to your question, but something to note.

I'm having a .... not fun time updating darch to the latest version. Does your makefile still require git, or can I kill that code?

Re: Void Linux: Into the Void

#56

Post by Vaelatern »

nicklaf wrote: post #54
keithpeter wrote: post #19

Earlier quoted context omitted.

Slackware and Arch are still very much alive as projects. By 'successor' do you mean 'works in a similar way and I happen to like it better' or is there something that you think Void has got that slackware and arch don't have? PS: downloading the void live .iso now for a bit of distro-hopping on a spring morning.

As someone who switched from Slackware to Void several months ago, Void boots far faster. Also, though I haven't used Arch, Void really feels like a combination of a slimmed down Slackware + NetBSD (the author of Void is a NetBSD commiter IIRC). Of course, Gentoo portage was inspired by BSD ports, which I believe was an impetus for Arch's package manager. I don't know what the story is for Arch, but I find that Void…

Our initial author, and the primary author of xbps, came directly from the NetBSD community.

Re: Void Linux: Into the Void

#57

Post by pknopf »

Vaelatern wrote: post #55
pknopf wrote: post #51

Earlier quoted context omitted.

The base docker images ( https://github.com/godarch/distributions ) only supports x86_64. Docker images have support for having multiple embedded rootfs tarballs for multiple platforms, but it gets complicated. Maybe in the future. Also, you have to build your recipes on the same target arch that you are going to deploy to. Irrelevant to your question, but something to note.

I'm having a .... not fun time updating darch to the latest version. Does your makefile still require git, or can I kill that code?

You can remove the git stuff, as long as you are not building containerd and runc as well.

What issues are you running into? The AUR and VoidLinux package don't have an issue. Skype (paul.knopf1) me?

Re: Void Linux: Into the Void

#59

Post by checkyoursudo »

krylon wrote: 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 used Void on my previous laptop for about a year with no stability issues. The only reason I stopped using it was because I wanted to experiment with a no-grub EFI stub booted whole disk encryption using LUKS non-systemd setup, which I only really had an idea of how to do on Gentoo, so I went back to that. [Edit: I think I might have almost had this working on Void, in fact, but there was some piece that I couldn't get right, if I remember, but that I could do more easily in Gentoo. But I can't remember what that might have been. It's been a while since I did that.]

Otherwise, I probably would have stayed with Void for a while more. It was pretty nice.

Re: Void Linux: Into the Void

#60

Post by pleasestopthis »

IgorPartola wrote: post #24
alxlaz wrote: post #22

Earlier quoted context omitted.

https://news.ycombinator.com/item?id=16671791 I can't edit my post anymore :-)

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.
Post reply on HN