SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
postfix seems not supporting mariadb. Is this normal?
If I compile it using the 14.2 SBo, mariadb is supported. I don't know what's the difference between the SBo and the official current SB.I'm checking.
postfix seems not supporting mariadb. Is this normal?
If I compile it using the 14.2 SBo, mariadb is supported. I don't know what's the difference between the SBo and the official current SB.I'm checking.
Found, I compile postfix with this little modification:
I had to modify my postfix-files file and add dynamicmaps.cf to my old conf. Everything works now with official package.
Sorry for the noise. Can be useful for people using postfix with mysql/ldap/sqlite.
Doesn't seem to be an issue. It has a history with systemd from some quick googling. Just reporting.
Jeff.
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)
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)
Originally Posted by ialexand
Syslinux is very old version. Why not to upgrade it to 6.03?
Originally Posted by Didier Spaier
Because 6.03 is buggy and syslinux is dead. Unless Patrick wants to carry all Debian' downstream patches that never did and never will make their way upstream, for the years to come. Which I very much doubt.
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.
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.