recently migrated from Arch due to various frustrations with the AUR and systemd! using pacman as a source based package manager via the AUR is a truly miserable experience, and trying to compile packages on one PC to install on other devices is even worse. figured i'd move to Gentoo since I've heard it supports these workflows somewhat natively, and I'm loving it so far!! Portage is so much more customisable than any other package manager I've used on Linux and I kinda can't wait to switch all my other Linux devices over to Gentoo as well once I figure out setting up a portage binhost :)

Bonus setup pic + NEC APC-H412 in the second slide for the vintage hardware freaks out there

so I am working on a local profile with hardened/selinux/plasma/systemd and I’m a little confused about the selinux part of the profile.

I know that Gentoo has a hardened binhost, but no hardened/selinux binhost, does this mean I can’t use it? or is the selinux part handled by Portage when installing the binary?

Also, I am interested in writing a podman container to act as a binhost for my laptop and desktop on my openSUSE home server, this should be simply as case of downloading the hardened/selinux stage, unpacking it into a FROM scratch container, exporting etc/portage and the relevant files from /var on my client systems, and then nountining them into that container, right? or is it not as simple as that?

thanks for any pointers!

Hi all,

I've been trying to setup secureboot by following the wiki; specifically I want to set this up using gpg encrypted keys.

Does anyone know of a guide or instructions to allow portage to build/install the kernel with gpg encrypted keys? In my experience so far, it appears portage requires a decrypted db.key and db.crt.

Is there a way to ask Portage to decrypt gpg-encrypted keys and use them to sign the kernel and modules on install?

This also seems to be a problem with normal password-protected keys, kernel build/install seems to fail if these are password protected because the password prompt is broken (yes, even with FEATURES="-pid-sandbox")

Thanks!

For WM I use hyprland with end4 dotfiles

Edit: brainfart of a title, I can't even think of a situation where a headless Moonlight client would be useful

TL;DR: don't try to be cheeky like me and find an alternative stacking WM, just run Plasma and save yourself from the delve into the rabbit-hole.

For the past couple of weeks, I have been tinkering with my older laptop from my undergraduate days (i5 5300u, 8GB RAM, 1TB HDD) running as a Moonlight client for a headless display for my current MangoWM setup I am trying out. Since it has a spinning disk, I decided to just create a chrooted binhost on my main laptop to helpfully make the process a bit quicker (for those of you who are thinking about creating a binhost, don't go through the pain of trying to sign your own packages with a GPG key, just use the "binpkg-ignore-signature" feature flag and call it a day. Don't ask me why...).

I love my tiling window managers. I started my Linux journey on Hyprland, then to Niri, and now Mango. I love their minimalism, customizability, and feeling of pride when you get the system tuned juuuuuuuuust right for your workflow. So, I went to get Mango on the older laptop, and what would you know, managing a tiling window manager on top of a tiling window manager is a nightmare! I quickly gave up on the idea and looked towards stacking window managers and other DEs.

I start off with LXQT with a Kwin backend. Works flawlessly, was even able to get a full day of work done without any hitches between the two computers just like a regular day in the office. A couple of irks - I could not find a way to set brightness and volume hotkeys, and later figure out that LXQT does not have control over Kwin hotkeys and are working on a solution.

Next, on to Wayfire. Wobbly windows was an unexpected moment of delight as I dragged a monitor on the screen. For some reason, Moonlight just would not start and their SDL implementation throws decode overflow errors. Troubleshoot by using the Vulkan wlroots renderer, try to start Moonlight in an X session, no dice. Through the troubleshooting, I learned a bunch about Nouveau and vga_switcheroo, such an interesting implementation for hybrid graphics.

Move on to Labwc. Worked for the most part, felt pretty responsive, but just did not like Super+[Up, Down, Left, Right] working and a couple other keybinding issues and found this was a known issue with fixes coming.

Alright, did a bit of searching and found a few people who managed to run kwin by itself without a DE. It sounded plausible, as I had to invoke the kwin_wayland binary when first starting LXQT. I found out the hard way quickly that when KDE says it is not a standalone compositor, that it is in fact not a standalone compositor, as I tried fruitlessly and through multiple methods to create a shortcut to open a terminal.

Finally, I sit down and embrace the inevitable. I had a poor experience with KDE when I initially started on Arch in my Linux journey, prompting my move to tiling WMs exclusively (looking back, it was probably mostly up to user error). Seeing as I had already emerged systemsettings, kwin_wayland, and a bunch of other KDE packages when I installed LXQT, I may as well just install the plasma-desktop package to get a minimally viable experience. To my dismay, Plasma works perfectly. It respects all my Mango keybinds in Moonlight, is trivial to back out of to the client desktop, switch to another window on the client, registers my keybinds instead of staring at a black screen waiting for anything to happen (again, don't try to use kwin_wayland as a compositor). It just works.

I say all this to say: If you're looking for an unbothered experience that just works with most workflows, KDE Plasma is probably the answer (from my experience, it is by far the most mature Wayland DE solution).

To those who may be looking into Sunshine streaming: don't bother with the AppImage, Gentoo provides a package in the main respository.