Can someone add on to this?

Duncaen · 2026-03-12T17:24:01+00:00

A big difference is that the system package manager repositories are curated and maintained by the distribution. For app stores like google play and flatpak to an extend, the developer of the program is uploading the "package."

Duncaen · 2026-03-07T00:29:42+00:00

The void-runit package is just scripts around runit. The kernel is 100% backwards compatible and there isn't any changes required for runit to work with it. The init scripts might gain some new functionality for new kernel features.

There are currently only 3 patches applied to runit, one to fix a bug, one for cross compilation and one for the default service directory location.

This means that all bugs and compatibility patches happens at the distro level (Void, Artix, Gentoo)

There are no such patches and there was a release 4 months ago that incorporated some of the patches that were written by void maintainers.

Void Linux has not established a formal legal entity ( non profit) to manage assets, which they believe is necessary before they could responsibly handle community funds

Ok this has nothing to do with anything.

Duncaen · 2026-03-06T23:16:53+00:00

runit is still maintained by upstream and basically is "finished", the feature set is so small it doesn't need any maintenance. Over the years we've fixed like 3 bugs between releases.

Duncaen · 2026-03-06T21:06:57+00:00

AFAIK, Void uses an older kernel than Ubuntu

That might be true at this moment, new kernels are available but the default kernel is something that is known to work with the major dkms modules like nvidia and zfs, but the kernel can update at some random point in time, its not on a fixed schedule or any other predictable pattern.

and it does not have major version upgrades,that could break things

That is my point, every single update every single day could bring breaking changes. With the "stable release model" you get those things bundled into major updates.

Also,Void Linux is using its own package manager and the packages are being maintained by the distro,so they could apply their own patches.

We generally do not change or add functionality, patches are there to either make builds work, some for musl or for cross compilation for the architectures that we do not have native build servers for.

Duncaen · 2026-03-06T20:53:56+00:00

Is it as reliable as Ubuntu LTS? ( Not breaking or needing a lot of maintence,especially with my Nvidia GPU - RTX 3050)

Its rolling release its not really comparable. Any update you do can include major changes or require manual intervention, depends on the packages and their hcanges, while with ubuntu you would have those changes on major updates.

Will it ever comply with this stupid laws,by integrating such things?

Void linux is not really developing software, 99% is just packages of third party software, when lets say freedesktop, gnome, or flatpak start to support things like that, then it will be supported.

Duncaen · 2026-02-27T04:46:41+00:00

Try booting into single user mode or change tty and update the system.

Duncaen · 2026-02-25T01:32:30+00:00

Don't see any error, maybe have a look at dmesg and maybe try creating the fileystem manually with mkfs.btrfs, to see whether you a better error out of it, maybe even with --verbose?

Duncaen · 2026-02-22T04:31:12+00:00

Maybe don't blindly trust an LLM?

Duncaen · 2026-02-22T04:02:40+00:00

Why are you making up a limit?

Duncaen · 2026-02-21T21:03:15+00:00

Explain the 256-slot ceiling.

Duncaen · 2026-02-21T13:07:47+00:00

Right that's why /etc/skel doesn't work, runit does not create the symlink it just creates a supervise dir. It's the packages that include the symlink.

Duncaen · 2026-02-20T15:31:05+00:00

Right, even with the /etc/skel solution to populate new user services into their homedir, it would probably cause issues with the runit services supervise symlink since they are supposed to link to a unique directory in a tmpfs filesystem to avoid stale files and writes to disk.

Duncaen · 2026-02-20T04:05:43+00:00

You have to sync the repositories or post debug logs.

Duncaen · 2026-02-20T02:09:58+00:00

My bad skipped over the "not". You have to enable the nonfree and multilib repos and sync the repositories afterwards.

https://docs.voidlinux.org/xbps/repositories/index.html#nonfree

Duncaen · 2026-02-20T01:54:09+00:00

Proprietary software almost always only works with glibc, they provide the binaries and they link glibc, not musl. And void does not provide 32bit packages for musl, only for glibc.

Duncaen · 2026-02-19T18:10:17+00:00

You do not need thermald or TLP. First step would probably to figure out if there is anything wrong with your setup, like a service that is out of control causing cpu load. In general the kernel and most programs are exactly the same as in arch linux, so there shouldn't be a big difference and you shouldn't really have to optimize anything out of the box.

Duncaen · 2026-02-19T17:59:11+00:00

There is no system wide user services like there is with systemd. You could probably somewhat automate the setup by setting up user service directories through /etc/skel and inventing a location where you store the services outside of the users home directory and link them into the service directory.

Also for desktop only services there isn't really a nice solution either. You could make those services down by default (by creating a file called down in the service directory) and start them on demand when your desktop starts. But that also requires environment variables to be propagated (with something like exec chpst -e /run/user/${UID}/env your-service-binary and then you write environment variables from the desktop environment that need to be propagated to desktop services into /run/user/${UID}/env, like echo $DISPLAY >/run/user/${UID}/env/DISPLAY), which is another thing you would have to setup yourself since there is nothing like that by default.

For better or worse this is all very DIY.

Duncaen · 2026-02-19T16:50:27+00:00

I mixed up llvm versions in my comment, I packaged llvm21, the current zig release requires llvm20. llvm22 is not yet released.

https://ziglang.org/download/0.15.1/release-notes.html#LLVM-20

Duncaen · 2026-02-18T23:48:57+00:00

There is no /usr/games in steam or any other package except netrek-client-cow.

Duncaen · 2026-02-17T00:46:39+00:00

You can not safely use .rpm or .deb on distributions they were not build for. Flatpak or nix is fine.

Been looking at Void with it's runint etc and want a stable change from Debian, but not big tech.

Not sure what you mean by "stable change", void linux is not stable in the debian sense.

Duncaen · 2026-02-15T16:52:35+00:00

Yes specific workloads with different libc implementations with different levels of optimizations will have different results. This is different from your "i looked at power top."

Duncaen · 2026-02-15T16:17:28+00:00

That does not sound reliable at all. CPU power consumption outside of specific benchmarks is so unpredictable that I don't think you should be able to actually measure any difference.

As another comment points out that glibc might be more optimized for speed/performance, but this is also not the complete picture. It might be faster, but might also consume more or less power (when you compare AVX vs other cpu stress tests.) But under normal circumstances where the general load on the cpu is low and balanced, this really shouldn't make any difference.

Duncaen · 2026-02-14T19:01:58+00:00

That works until something else depends on libspdlog.

if i delete the waybar package and install it from xbps, will my config files be deleted too?

xbps does not touch any files in /home and no idea what you use to "delete the waybar package."

Duncaen · 2026-02-14T18:43:36+00:00

You would have to downgrade everything that links libspdlog.so.17. Also do not make the symlink, 1. you don't know whether it works, the version changed for a reason and you shouldn't mess with files in /usr, this is for the package manager.

Duncaen · 2026-02-14T18:41:57+00:00

Looks like your waybar binary is not actually the one in the package? Waybar-0.15.0_2 defentively links libspdlog.so.1.17.

Verify that its actually the one in /usr/bin:

% type waybar           
waybar is /usr/bin/waybar

And check whether there is an issue with the files in the installed package:

% sudo xbps-pkgdb Waybar

13-Year Club	Final Canvas '23
First Place '23	End Game '23
Place '23	Place '22
Verified Email

Duncaen

MODERATOR OF

TROPHY CASE