shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

290
active users

#slackware

5 posts4 participants0 posts today

Icu4c appears to have been updated in #slackware today while I’ve been working. I’ll get rebuilds out in some hours for the effected #kde6 packages. Did KDE ever drop the next gear beta? That was supposed to be today as well. Ah well, we’ll get it all soon enough.

So I'm in this Linux-centric Discord server, and everyone pokes fun at me for using Slackware, jokingly saying I'm super old and whatnot. I play into it and share a couple of memes playing into the joke. Here's those memes. All us old-ass Slackware users can have a good laugh at this :)

Question to #pkgsrc people in the context of #slackware #linux usage. I have bootstrapped pkgsrc with ˋbootstrap --prefer-pkgsrc yes --prefer-native openssl`. Everything compiles and works well so far.

Trying to build thunar, I get unsolvable error with a dependency. So I added "samba gvfs" to the prefer-native variable in my mk.conf.

But the build process still tries to compile samba4 and gvfs packages. What am I doing wrong?

In the adventures of Bob's "Perfect" #Slackware install, I've been struggling to get Secure Boot working on my #Thinkpad x280.

Something seems to be preventing me from loading a custom Platform Key, while none appears loaded, and everything seems 'right' -- #SecureBoot is in Custom / Setup mode.

The unfortunate thing is ... using Secure Boot and signing kernel images and efi executables is not a common practice, and the documentation seems lacking explanations for people with my particular issue; method 1 of using `efi-updatevar` returns an error "Cannot write to PK, wrong filesystem permissions", method 2 -- updating from the #UEFI 'bios' -- is not an option on an x280, and method 3, using KeyTool.efi returns the error "Failed to update variable: (26) Security Violation".

I am wondering if there are some further setup settings that need to be adjusted to allow this operation, if perhaps my pk.auth file is incorrect in some way, if my machine was, from the factory, unable to allow custom Platform Keys, or if someone has modified it since then.

Rabbit holes are a pain in the dick, and now I'm in a position where I'm kinda 'forced' to learn a bit more about the mechanics of Secure Boot, under the hood.

Anyone got some good tips for where to start solving this puzzle?

I have been referencing:

- wiki.gentoo.org/wiki/User:Saka
- wiki.linuxquestions.org/wiki/H

wiki.gentoo.orgUser:Sakaki/Sakaki's EFI Install Guide/Configuring Secure Boot under OpenRC - Gentoo wiki