LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Requests for -current (14.2-->15.0) (https://www.linuxquestions.org/questions/slackware-14/requests-for-current-14-2-15-0-a-4175620463/)

ljb643 03-19-2021 08:16 PM

Quote:

Originally Posted by volkerdi (Post 6232117)
Reinstall the krb5 package. Probably aaa_libraries was installed after it and clobbered the library versions in the krb5 package (which unfortunately do not properly increment a minor library version with new releases).

To clarify: You can also get this error if you never installed the krb5 package in the first place. (I know, we are supposed to install everything, which is why I haven't mentioned this before.)

Prior releases of Samba, and everything else I use, worked just fine without the krb5 package installed. They either didn't need it at all or they used the one in aaa_libraries. When Samba was upgraded, suddenly the version in aaa_libraries wasn't good enough for it, and you need the version in the krb5 package.

So the solution is: install (or reinstall) the krb5 package.

ZhaoLin1457 03-19-2021 10:04 PM

Quote:

Originally Posted by ljb643 (Post 6232254)
To clarify: You can also get this error if you never installed the krb5 package in the first place. (I know, we are supposed to install everything, which is why I haven't mentioned this before.)

Prior releases of Samba, and everything else I use, worked just fine without the krb5 package installed. They either didn't need it at all or they used the one in aaa_libraries. When Samba was upgraded, suddenly the version in aaa_libraries wasn't good enough for it, and you need the version in the krb5 package.

So the solution is: install (or reinstall) the krb5 package.

I do not think that Kerberos or LinuxPAM are (or could be considered) optional packages on Slackware-current, because they are part of the system authentication.

tux_dude 03-19-2021 10:35 PM

Quote:

Originally Posted by richarson (Post 6231308)
I don't know if it's sufficient but have you tried installing AlienBOB's packages? Or is it really necessary to recompile plasma-nm after installing those packages?

Code:

$ slackpkg search openconnect

Looking for openconnect in package list. Please wait... DONE

The list below shows all packages with name matching "openconnect".

[ Status      ] [ Repository ] [ Package                                        ]
  uninstalled    alienbob      NetworkManager-openconnect-1.2.4-x86_64-2alien
  uninstalled    alienbob      openconnect-7.08-x86_64-4alien               

You can search specific files using "slackpkg file-search file".

Sorry I can't test this as I don't have/know an openconnect VPN to try.

I am not using slackpkg+, but to get KDE connection setting to work with openconnect support is required in plasma-nm. I am currently running AlienBOB's last release from ktown
Code:

plasma5-nm-5.19.4-x86_64-1alien
.

atelszewski 03-20-2021 05:05 AM

mkinitrd.conf enhacement
 
Hi,

how about /etc/mkinitrd.conf pointing to the installed modules rather than to the ones of the running kernel? Something in the lines of:
Code:

KERNEL_VERSION="$(ls -1 /var/lib/pkgtools/packages/kernel-modules-*-*-* | tail -n1 | rev | cut -f3 -d- | rev)"
That would cover the more common situation.

--
Best regards,
Andrzej Telszewski

Didier Spaier 03-20-2021 05:16 AM

GNOME 40 around the corner
 
In case someone wonder, this is not a request to include the GNOME desktop in Slackware (I don't like it anyway). However several packages in Slackware are built from sources available in https://download.gnome.org/sources/, and they can be sorted by date of last update descending: https://download.gnome.org/sources/?C=M&O=D

So it will be easy enough to find which ones to update after the official release of GNOME 40.

marco70 03-20-2021 05:37 AM

Please add WPA3 support to the wpa_supplicant package.

dot.config:

Code:

# WPA3-Personal (SAE)
CONFIG_SAE=y

# WPA3-Enterprise (SuiteB-192)
CONFIG_SUITEB=y
CONFIG_SUITEB192=y


pisti 03-20-2021 07:22 AM

as the maildir format gets increasingly used even locally for mail storage, one may think about including a maildir patch in the alpine email client as described here :

http://alpine.x10host.com/alpine/info/maildir.html

the maildir patch :

http://alpine.x10host.com/alpine/pat...ildir.patch.gz

thank you !

Thom1b 03-20-2021 09:33 AM

Quote:

Originally Posted by atelszewski (Post 6232329)
how about /etc/mkinitrd.conf pointing to the installed modules rather than to the ones of the running kernel? Something in the lines of:
Code:

KERNEL_VERSION="$(ls -1 /var/lib/pkgtools/packages/kernel-modules-*-*-* | tail -n1 | rev | cut -f3 -d- | rev)"
That would cover the more common situation.

Good idea. I prefer this code:
Code:

KERNEL_VERSION="$(readlink /boot/vmlinuz | cut -d- -f3-)"

GazL 03-20-2021 09:45 AM

re: mkinitrd suggestions above.

You're both making assumptions about the filename of the vmlinuz image. I'd prefer it left as is, but if you must do this then maybe
ls -1t /lib/modules/ | head -n1

correction:
atelszewski wasn't, as on second look he is using the package file name, but even there he's assuming that the user is using that package. I don't.

allend 03-20-2021 10:32 AM

I have always considered /etc/mkinitrd.conf to be a convenience best left for the individual to configure.

I do not care about defaults as I do not use it, but the choice of how to set the kernel version apart from the running kernel will depend on individual use cases.

Chuck56 03-20-2021 11:07 AM

Quote:

Originally Posted by allend (Post 6232404)
I have always considered /etc/mkinitrd.conf to be a convenience best left for the individual to configure...

I modify /etc/mkinitrd.conf OUTPUT_IMAGE & KERNEL_VERSION lines as follows:
Code:

#OUTPUT_IMAGE="/boot/initrd.gz"
OUTPUT_IMAGE="/boot/initrd-$2.gz"
#KERNEL_VERSION="$(uname -r)"
KERNEL_VERSION="$2"

As root, I call /sbin/mkinitrd as follows:
Code:

mkinitrd -F 5.11.7
One of the other customization(s) is the MODULE_LIST="ext4" at a minimum. This is also how autoslackpkg is designed to build the initrd.

GazL 03-20-2021 11:31 AM

Quote:

Originally Posted by Chuck56 (Post 6232413)
I modify /etc/mkinitrd.conf OUTPUT_IMAGE & KERNEL_VERSION lines as follows:
Code:

#OUTPUT_IMAGE="/boot/initrd.gz"
OUTPUT_IMAGE="/boot/initrd-$2.gz"
#KERNEL_VERSION="$(uname -r)"
KERNEL_VERSION="$2"

As root, I call /sbin/mkinitrd as follows:
Code:

mkinitrd -F 5.11.7

mkinitrd already has the -k option for that.

Chuck56 03-20-2021 11:46 AM

Quote:

Originally Posted by GazL (Post 6232420)
mkinitrd already has the -k option for that.

Learned something new! Fewer modifications to the conf file is mo' betta! :)

saxa 03-20-2021 12:20 PM

Quote:

Originally Posted by Didier Spaier (Post 6232333)
In case someone wonder, this is not a request to include the GNOME desktop in Slackware (I don't like it anyway). However several packages in Slackware are built from sources available in https://download.gnome.org/sources/, and they can be sorted by date of last update descending: https://download.gnome.org/sources/?C=M&O=D

So it will be easy enough to find which ones to update after the official release of GNOME 40.

I posted some of them which are already on the server. Would be nice to have those updated to the latest since we are still in Alpha phase afaik.

saxa 03-20-2021 12:21 PM

PS: Just looked at the changelog and I see we have pygobject 3.40 already, so hope is the last to die :)


All times are GMT -5. The time now is 10:25 PM.