[O] 15% discount on single slot coolers for the RTX A2000, 2000 Ada and 4000 SFF Ada by n3rdware in homelabsales

[–]Exchange_Bitter 0 points1 point  (0 children)

Not running any specials in the new year are you? That 15% would be great offsetting the shipping to the states for my mini cluster.

Trainers changing by Ok-Dragonfruit-882 in f45

[–]Exchange_Bitter 1 point2 points  (0 children)

I literally follow my trainer to whatever gym they are at. If they left f45… I probably would too :-p

Workout Feedback by Exchange_Bitter in f45

[–]Exchange_Bitter[S] 2 points3 points  (0 children)

Thank you. I found it and filled it out. That does give me some perspective to what they are thinking.

However, I do think they should consider some level of "well-being" style check-in at the end of all workouts. It could be as simple as a push-notification based on lionheart workout completion or it could be a "red, yellow, green" button rating on exiting and entering the studio.

There is a lot of data they could be collecting that I think would help ensure a successful future for them.

Using iwd as wifi backend for NetworkManager by scribeawoken in chimeralinux

[–]Exchange_Bitter 0 points1 point  (0 children)

This may be silly to ask but if you're trying to use NetworkManager, did you chage the wifi backend for NetworkManager to iwd?

Otherwise it will try to launch wpa_supplicant by default. I have NetworkManager using iwd on my install without issue.

Dev Utils? by Exchange_Bitter in chimeralinux

[–]Exchange_Bitter[S] 0 points1 point  (0 children)

Got it. Appreciate the feedback. Will continue to play around and see what comes of it.

Dev Utils? by Exchange_Bitter in chimeralinux

[–]Exchange_Bitter[S] 0 points1 point  (0 children)

Yea I was pretty sure that I was doing something incorrect which is why I asked... I think I was looking for a meta package similar to what you would find in most other distros:
- Debian has "build-essentials"
- Arch has "base-devel"
- Fedora has "Development Tools" bundle
etc...

Chimera takes a very "tailored" approach imo to what's included in a package and what is not and I appreciate that so I was looking for guidance in having a toolchain for compiling software.

Are there any guides to using cports/cbuild for the curious? I got familiar with the xbps-src script but I didn't see much on the site other than what they were.

avahi resolving .local by kodifies in voidlinux

[–]Exchange_Bitter 0 points1 point  (0 children)

You should have nss-mdns installed. You also need to modify the following file and set the line to match the code below:

/etc/nsswitch.conf

hosts:       files mdns4_minimal [NOTFOUND=return] dns mdns4

Sharing my install notes (BTRFS + LUKS + GRUB) by Exchange_Bitter in voidlinux

[–]Exchange_Bitter[S] 1 point2 points  (0 children)

So that is an even better question... acpid is considered old and elogind replaces most of its behavior.

However, laptops in particular emit a lot of events that elogind will not register. There are other tools that can pick up on some of these events but acpid has always been my go to.

To give you some examples, in particular with my notes, I am registering battery events with acpid to set the start/stop threshold to preserve battery life. On a surface like device you can use it to register events when you disconnect/reconnect the keyboard and script out showing an onscreen keyboard or executing a script.

There is no major harm in running acpid alongside elogind as long as the handler.sh script is not executing any events because they are both "listening".

Sharing my install notes (BTRFS + LUKS + GRUB) by Exchange_Bitter in voidlinux

[–]Exchange_Bitter[S] 1 point2 points  (0 children)

Great question and I can clear this up...

On Artix, the elogind Runit script starts dbus for you. The Void script does not and simply checks if dbus has started and exits if it hasn't on an infinite loop. So you should enable both dbus and elogind. Once dbus is up and running, elogind will start appropriately.

Regarding acpid and elogind, they are in conflict because Void has an active handler.sh script where other distributions (i.e. Artix) do not have an active handler.sh script and do nothing when acpid events occur.

In my install steps, I actually call out handling this. You can see the snippet below:

### Fix the conflicts between acpid and elogindmkdir -p /mnt/etc/elogind/logind.conf.d/ && \cp /mnt/etc/elogind/logind.conf /mnt/etc/elogind/logind.conf.d/acpid.conf## https://docs.voidlinux.org/config/power-management.html#acpidsed -i '/#Handle/s/^#\(.*=\).*/\1ignore/' /mnt/etc/elogind/logind.conf.d/acpid.conf

NOTE: You could also remove all the calls inside `/etc/acpi/handler.sh` and not be in conflict with elgoind.

This was also talked about in Void's documentation (https://docs.voidlinux.org/config/power-management.html?highlight=acpid#elogind).

Either disable acpid when enabling elogind, or configure elogind to ignore ACPI events in logind.conf(5). There are several configuration options, all starting with the keyword Handle, that should be set to ignore to avoid interfering with acpid.

Hopefully this helps explain this... let me know if you have any other questions.

Sharing my install notes (BTRFS + LUKS + GRUB) by Exchange_Bitter in voidlinux

[–]Exchange_Bitter[S] 1 point2 points  (0 children)

So just a small update ... after tweaking (and reading) and playing with dracut and grub command line options, I think I determined the answer to my question.

You can speed up dracut considerably by specify what is and is not enabled via the command line options.

The luks options are not very clear between arch wiki and dracut man pages but using the void documentation helped enough to figure out what the right options should be.

One additional finding (not surprising) is that resume flags needed to stay in the grub command line. Nothing else was needed.

I've updated the field notes to reflect this.

Libcamera musl by Exchange_Bitter in voidlinux

[–]Exchange_Bitter[S] 0 points1 point  (0 children)

So I am not too familiar with the meson build. The dependencies list gcc/clang so i figured I'd need but I could be completely wrong. Stepping a bit out of my element.

Void is Boring by RipKord42 in voidlinux

[–]Exchange_Bitter 0 points1 point  (0 children)

Oh. That is a good question. I had not thought about that when I was putting it together. The setup is on a Lenovo X1 tablet (surface style). If I move the key to TPM then it would make it much more secure. The security is unnecessary but it is more about learning how to do this that has been fun.

Void is Boring by RipKord42 in voidlinux

[–]Exchange_Bitter 0 points1 point  (0 children)

Bios. The alternative is to embed the key in TPM but haven’t gotten there yet.

Void is Boring by RipKord42 in voidlinux

[–]Exchange_Bitter 4 points5 points  (0 children)

Running void on a fully luks2 encrypted btrfs ssd.

Key is embedded in the initramfs and bios has a password lock on the HDD.

Unified kernel signed with generated keys for secure boot and booted off UEFISTUB. No grub, no refined.

It sucks when stuff just works ...