Since booting kernel 5.15.18 and 5.15.19 on current, I get the following in /var/log/dmesg:

...
[ 14.738261] udevd[1293]: specified group 'kvm' unknown
[ 15.179665] udevd[1300]: starting eudev-3.2.11
...

Doesn't seem to be an issue. It has a history with systemd from some quick googling. Just reporting.

Jeff.

The word "kvm" makes me think about QEMU with hardware acceleration within the host kernel, which happens to be named KVM.

So, permit me to doubt that it's something about systemd, but it's rather about KVM/QEMU .

http://www.linux-kvm.org/page/Main_Page

Let's do not see Mr. Poettering's shadow at every street corner... ;)

I assume that one of the files in /etc/udev/rules.d/ or /usr/lib/udev/rules.d/ has "kvm" in it. Did you install qemu or libvirt but forgot to create the "kvm" group which is needed?

Is there any reason the syslinux package hasn't been upgraded to 6.0.3? It is currently at 4.0.7 and doesn't support EFI (EFI only supported from 6.0.0)

Maybe because, at a moment, we have to stop with Paleolithic bootloaders ... (even if they work)

edit: and, there are, at least 2 pages of patches since 6.0.3
https://repo.or.cz/syslinux.git/shor...e41aed067?pg=1

Syslinux wasn't updated because 6.0 is buggy, or at least that was the case a year ago:

https://www.linuxquestions.org/quest...ml#post6236546

I disagree with Didier about syslinux being dead -- old software that still works isn't "dead", it's "mature".

I agree with him, though, that until 6.0's bugs get fixed, we're better off sticking with 4.0.7.

syslinux-6.03 is buggy. I built my own syslinux and used syslinux-6.04-pre1 and it seems to support EFI and not suck.

Dovecot v2.3.18

Hi, tigervnc is not working properly, it shows the remote desktop but it doesn't accept any inputs, I think it needs to be rebuild against the current xorg version.

sorry for the noise :D

... so maybe there has to be a future CVE to make a newer dovecot happen in 15.0, but who knows.

Ya.. I recompiled the dovecot slackbuild on that version... theres a lot of fixes for fts among other things :( Hopefully(?!) a CVE will come out to update the version

Ehm
Scuse me... last request for me here...
Isn't it time to mark this thread as solved ?

And closed.

No need to be sticky, then.

This thread could be closed. We could start a new one and call it "Requests for -current 15.0 >"!

Or we could close.
Let a little rest to our BDFL.
Let a little time to the rest of the team and SBo folks to go stable.

And when we'll begin to enjoy the stability of the whole ecosystem, just go current again.

I also think this thread should now be marked [solved] closed, and unstuck.

Then, where I should put my request for Plasma 5.24 ? :D

Hmm

Because LuckyCyborg is LuckyCyborg, I think he wants plasma 5.24 in Slackware 15.0 :D

Side note:
And thank you by the way LC, you are undoubtedly part of those who pushed for plasma 5.23

Just one more thing to do. This forum is https://www.linuxquestions.org/questions/slackware-14. Should not we change it to slackware-15?

This is not a release number, but an LQ forum ID

https://github.com/ValveSoftware/ste...ent-1030509625

Sounds like glibc 2.34 is going to be an issue for some electron and chromium things for a bit until they get patched...

This sounds like it merits its own thread.

Thank you for your kind explanation. Yes, Slackware forum ID 14.2 will be the same when Slackware 16.0 is current.

Again, just like Monsieur Marav said, the number 14 from name of our subforum: "slackware-14" means the 14th row in a database table of this site, just like "centos-111" means the 111th row in the same database table. It has nothing to do with Slackware 14.2

This "ID 14" was from beginning, when was created this subforum, and probably the Slackware was probably on release 9.1 and will be 'till this site (and/or this subforum) will exists, no matter which release will have Slackware in the future.

building DVD builds but ha errors and ommits stuff

rive current: -outdev 'stdio:/tmp/slackware-dvd.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 154g free
xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rules
Added to ISO image: directory '/'='/var/ftp/pub/slackware-15.0'
xorriso : UPDATE : 5680 files added in 1 seconds
xorriso : UPDATE : 5680 files added in 1 seconds
xorriso : NOTE : Copying to System Area: 432 bytes from file '/usr/share/syslinux/isohdpfx.bin'
libisofs: WARNING : Cannot add /extra/java to Joliet tree. Symlinks can only be added to a Rock Ridge tree.
libisofs: WARNING : Cannot add /extra/source/alpine to Joliet tree. Symlinks can only be added to a Rock Ridge tree.
libisofs: WARNING : Cannot add /isolinux/sbootmgr/RAWRITE13.EXE to Joliet tree. Symlinks can only be added to a Rock Ridge tree.
libisofs: WARNING : Cannot add /slackware/PACKAGES.TXT to Joliet tree. Symlinks can only be added to a Rock Ridge tree.
libisofs: WARNING : Cannot add /usb-and-pxe-installers/etherboot/RAWRITE13.EXE to Joliet tree. Symlinks can only be added to a Rock Ridge tree.
libisofs: NOTE : Automatically adjusted MBR geometry to 1022/234/32


I reverted to using ol faithful mkisofs (which i prefer anyway) and no problems, so something got lot in trying to change to xorro

You failed to share your commandline. The xorriso program adds Rock Ridge by default, so perhaps you added ' -rockridge "off" ' ?

The suggested command in Pat's README throws those warnings. I noticed them too.

I don't think they're anything to worry about. Joliet just doesn't support symlinks is all, and that's fine as the rock-ridge extension will handle all the UNIXy stuff and joliet is for Microsoft OSes.

I'm not sure what the problem with the 'SlackDVD' volid is supposed to be. Should it be upper-case only to be conformant or something? Anyway, it doesn't seem to do any harm.

According to the ECMA-119 standard, § 8.4.6 the characters in the Volume Identifier (BP 41 to 72) shall be d-characters. The § 7.4.1 lists these characters and ECMA-6 identify them as digits 0 to 9, upper case letters A to Z and "low line" (aka underscore or "_").

Thanks Didier, I tried to search for ecma-119 but all I found were sites trying to sell me a copy. :(

https://www.ecma-international.org/p...ards/ecma-119/
Note that this is the same content as in ISO-9660, but ECMA standards are free to download.

Please mark this thread finally as solved and close it. I can't sleep well until then! :D

Take Guarana - no sleep :D

Yeah, I would like this thread terminated, and two new threads: "requests for 15.0 patches", and "requests for -current 15.0 -> 15.1".

An update to util-linux 2.37.4 would be nice :)

Why not just stop responding to it and let it die to obscurity?

1. It's a sticky thread.
2. There are no threads to replace it.

1. No more
2. https://www.linuxquestions.org/quest...-a-4175706801/

You haven't been paying attention :D

It lost its sticky status probably last week and a replacement thread was stickied.

Lock it when at 666 pages? :foot:

After six years we hurry nowhere any more :foot:

EDIT: WOOPS

sorry ...