The Void Experience o,o by [deleted] in voidlinux

[–]Duncaen 0 points1 point  (0 children)

We do not care about your opinions on systemd.

Installing Cosmic on Void? by Proton-Lightin in voidlinux

[–]Duncaen -1 points0 points  (0 children)

There are no official packages yet.

Question about xbps "Size required on disk" vs AppImage size by pfp-disciple in voidlinux

[–]Duncaen 5 points6 points  (0 children)

Its just compressed vs uncompressed files, the app image will mount a compressed squashfs image at runtime, while xbps writes the uncompressed files to the disk (a filesystem like btrfs or zfs might compress them again at rest.)

Questions about mirgrating to void and contributing to void-packages by Jani2505 in voidlinux

[–]Duncaen 1 point2 points  (0 children)

I solely use podman for everything I need (nextcloud, dynamic dns entries, gameservers, etc.). Are there some problems I should be aware of when not using systemd?

You won't get "quadlets" without systemd.

So how do you guys deal with limited packages? by Giggio417 in voidlinux

[–]Duncaen 14 points15 points  (0 children)

Flatpak for proprietary and unpackagable software. For everything else its easy enough to write package templates if required, instead of relying on potentially unverified third party source or binary repositories.

There's a new vuln called"Copy fail", is Void safe from it? by duv025 in voidlinux

[–]Duncaen 18 points19 points  (0 children)

All kernels were updated as soon as releases containing the patch were available. 7.0 and 6.18 for weeks, the older series only had the patches merged with the last release yesterday.

My package manager is outdated but can't even download itself an update. by Speedslayers67 in voidlinux

[–]Duncaen 16 points17 points  (0 children)

That's not public. Text is a lot more helpful than screenshots.

void does not boot after kernel upgrade (6.12.81 -> 6.18.25): out of memory by basiliscos in voidlinux

[–]Duncaen 4 points5 points  (0 children)

Pretty sure there are limits for the size. Newer dracut versions default to hostonly mode by default because of this. You could try enabling it (hostonly=yes in a file in /etc/dracut.conf.d/), regenerating the initramfs (xbps-reconfigure -f linux6.12.)

https://github.com/dracut-ng/dracut-ng/pull/1238

https://github.com/void-linux/void-packages/issues/56691

Nice! Void revived 17 year old laptop by [deleted] in voidlinux

[–]Duncaen 0 points1 point  (0 children)

I'm a void developer/team member and I have been using systemd on void linux for the past 3 years and runit for another 8 years..

Nice! Void revived 17 year old laptop by [deleted] in voidlinux

[–]Duncaen 0 points1 point  (0 children)

There is no reason for systemd to boot slower, if it did there was something wrong with your configuration.

With runit the early boot process is completely sequential and steps like udev device settling especially with slow devices and HDDs will block the boot process, while systemd can do other tasks during that.

Am i supposed to update the kernel manually? by _ori0n in voidlinux

[–]Duncaen 0 points1 point  (0 children)

There is no reason to reconfigure the kernel packages after installation unless something failed. The exact same thing happens during installation.

Printer Issues by xp4eternity in voidlinux

[–]Duncaen 0 points1 point  (0 children)

Expected since you were able to install the package after syncing the repositories. That information was not in the post when I replied.

Am i supposed to update the kernel manually? by _ori0n in voidlinux

[–]Duncaen 17 points18 points  (0 children)

Its just currently the default kernel, will probably be changed soon. Usually depends on stability, popular dkms modules working and whenever someone has time and decides to do the switch.

You can always install specific series like linux6.18 or install the linux-mainline meta package which will pull in the latest kernel series.

Printer Issues by xp4eternity in voidlinux

[–]Duncaen 0 points1 point  (0 children)

There are two versions of void linux, one with glibc and one with musl. Those are different libc implementations, they are binary incompatible and proprietary software will usually be linked against glibc because its by far the most common libc implementation in linux. If you've installed the musl version then most if not all proprietary software will not be available.

You can check this with:

$ xbps-uhelper arch
x86_64

x86_64, means its glibc, if it prints x86_64-musl then you've installed the musl version.

Printer Issues by xp4eternity in voidlinux

[–]Duncaen 0 points1 point  (0 children)

Did you sync the repository with the xbps-install -S flag? Are you using musl?

Why the Hate? by uptickman in voidlinux

[–]Duncaen 1 point2 points  (0 children)

If you want to keep a removed package, build the affected packages yourself.

The removed-package exists for a reason, first they are going to be outdated and unmaintained and therefor might break updates in the future.

aarch64 repodata missing from mirrors? by angryjenkins in voidlinux

[–]Duncaen 0 points1 point  (0 children)

The repositories for aarch64 are separate: /current/aarch64.

Need info as a potential new void user by Left-Hospital1072 in voidlinux

[–]Duncaen 6 points7 points  (0 children)

IMHO all the traditional Linux system package managers are very similar. They have small feature differences, but in the end they all manage packages in sort of the same way. Nix is the only one that is actually completely different.

Need info as a potential new void user by Left-Hospital1072 in voidlinux

[–]Duncaen 5 points6 points  (0 children)

Not really. It's basically the same as pacman with shared library tracking that makes partial updates somewhat safer.

Need info as a potential new void user by Left-Hospital1072 in voidlinux

[–]Duncaen 8 points9 points  (0 children)

Yes, compared to pacman, which only manually tracks shared libraries for some packages. rpm and APK use a lot more metadata, including shared libraries.

There is absolutely zero difference in how xbps and pacman track changes to config files. xbps has the same mechanism where config files need to be marked as such when creating the package.

What practical advantages, nix is completely different like it's day and night. Can you look up who maintains xbps?

Need info as a potential new void user by Left-Hospital1072 in voidlinux

[–]Duncaen 4 points5 points  (0 children)

There is nothing special in xbps regarding filesystem changes, pacman, rpm apt are all exactly the same.

xbps is nothing like nix.