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

21–30 of 104 posts

Re: Void Linux: Into the Void

#21

Post by alxlaz »

mdekkers wrote: post #10
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…

No systemd, so [...] you can't do much DevOps on Void Linux How so? How is DevOps linked or dependent on systemd in your view? Personally, I find systemd gets in the way of devops.

Oh, the downvote machine works here as well...

Whenever the line between a technical discussion and a systemd bashing thread becomes blurry, someone who does DevOps for a living invariably pops up to say how much they like systemd -- usually for pretty valid reasons.

It's also ubiquitous enough that, by this point in time, some of my younger colleagues who do DevOps for a living have never used anything but systemd. Doing Stack Overflow-driven (aka copy-paste) DevOps without systemd is pretty challenging nowadays.

Hence the joke.

Otherwise, yes, of course you can do DevOps on Void. I can't imagine what you couldn't do DevOps on; I know folks who were doing it on Novell Netware before the whole thing even had a name.

Re: Void Linux: Into the Void

#22

Post by alxlaz »

O_H_E wrote: post #16
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…

you can't do much DevOps on Void Linux Why is that ???

https://news.ycombinator.com/item?id=16671791

I can't edit my post anymore :-)

Re: Void Linux: Into the Void

#24

Post by IgorPartola »

alxlaz wrote: post #22
O_H_E wrote: post #16

Earlier quoted context omitted.

you can't do much DevOps on Void Linux Why is that ???

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.

Re: Void Linux: Into the Void

#26

Post by pknopf »

xfer wrote: post #7
BlackLotus89 wrote: post #4

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 used to use void-linux for many of these reasons(after arch for a few years). But i have now moved to nixos. It offers me the benefits of replicating system setup(i don't backup my system folders anymore, just my homedir and the nixos configuration files), cleanly removing system-wide packages(no more stale config hanging around) and of course the benefits of using nix for isolated/reproducible builds.

With Darch (I'm the author), you can use VoidLinux with a replicated setup.

Also, each boot is a clean boot (tempfs overlay). This ensures you capture your OS changes through your build script.

https://godarch.com/

This gives me what I love about Nix (scripted setup) with OSs I love (Arch and Void).

Re: Void Linux: Into the Void

#27

Post by parenthephobia »

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…

> something that's been working fine since the 1980s has recently been declared broken

Void Linux uses runit, which was released in 2004, so I guess they agree.

Re: Void Linux: Into the Void

#28

Post by zzzcpan »

alxlaz wrote: post #21
mdekkers wrote: post #10

Earlier quoted context omitted.

No systemd, so [...] you can't do much DevOps on Void Linux How so? How is DevOps linked or dependent on systemd in your view? Personally, I find systemd gets in the way of devops.

Oh, the downvote machine works here as well... Whenever the line between a technical discussion and a systemd bashing thread becomes blurry, someone who does DevOps for a living invariably pops up to say how much they like systemd -- usually for pretty valid reasons. It's also ubiquitous enough that, by this point in time, some of my younger colleagues who do DevOps for a living have never used anything but systemd.…

Isn't devops basically an infrastructure engineering, which if anything, is as anti-systemd as it gets. I guess people think of devops as something different then.

Re: Void Linux: Into the Void

#29

Post by bringtheaction »

I ran the musl libc version of Void Linux for a while on one of my laptops but ran into a lot of problems and buggy behavior.

If you are going to use Void Linux I would strongly recommend not picking the musl version unless you are specifically interested in improving musl support by filing and/or fixing bugs.

Re: Void Linux: Into the Void

#30

Post by kanbannoman »

pknopf wrote: post #26
xfer wrote: post #7

Earlier quoted context omitted.

I also used to use void-linux for many of these reasons(after arch for a few years). But i have now moved to nixos. It offers me the benefits of replicating system setup(i don't backup my system folders anymore, just my homedir and the nixos configuration files), cleanly removing system-wide packages(no more stale config hanging around) and of course the benefits of using nix for isolated/reproducible builds.

With Darch (I'm the author), you can use VoidLinux with a replicated setup. Also, each boot is a clean boot (tempfs overlay). This ensures you capture your OS changes through your build script. https://godarch.com/ This gives me what I love about Nix (scripted setup) with OSs I love (Arch and Void).

This is cool!
Post reply on HN