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.
Yes, they have compiled PAM into the packages (and I am grateful for it! having plans to use vbatt's work), but this does not lessen the maintenance burden and does not address the misconfiguration risk.
By asking PV+friends to maintain more distro complexity, we are essentially telling them to neglect other packages and/or take longer between releases. IMO that is not fair to the majority of Slackware's users, who have no need for PAM and would be exposed to unnecessary risk.
It's ultimately not up to us, of course .. we'll see what BDFL decides.
vbatts' server is down and has been for a while, so I had a go at updating the PAM stuff for -current back in July and am currently halfway maintaining it. I just pushed some rebuilds and upgrades to sync it with the present -current tree. There is no warranty, neither express nor implied. :-)
Require freetype >= 2.8.1
2.8.0 had a bad bug with loading 'avar' table. Let's update requirement and cleanup
fifteen years of ifdefs!
I also have problems with (I guess, based on many hours research I've done) freetype - problems on my t420 (Intel i915), XFCE, fonts are too blurry everywhere. Hope that freetype upgrade will solve that.
Last edited by ajevremovic; 11-19-2017 at 04:00 AM.
In rc.dovecot, "killall" is used to shutdown dovecot. But the command "doveadm stop" is a proper way to shut it down (like "postfix stop" for postfix).
Maybe dovecot-pigeonhole can be added to manage sieve scripts ?
/sbin/mount -a -t nfs # This may be our /usr runtime!
Code:
# Start the system logger if it is not already running (maybe because /usr
# is on a network partition).
if [ -x /etc/rc.d/rc.syslog -a -d /var/log -a ! -r /var/run/syslogd.pid ]; then
. /etc/rc.d/rc.syslog start
fi
And some scripts in /etc/rc.d/rc.inet2 are still sourced.
In rc.dovecot, "killall" is used to shutdown dovecot. But the command "doveadm stop" is a proper way to shut it down (like "postfix stop" for postfix).
Here is the rc.dovecot I suggest, using "doveadm stop" and "doveadm reload" :
Thank you very much!
And thank you for all the updates, I love to have postfix and dovecot added to Slackware!
Does anyone know what the motivation behind this is?
Because, not only is Postfix added, but Sendmail is about to be kicked out of Slackware. Is it, because Postfix plays more nicely together with Dovecot? Or has there been any trouble, e.g. unfixed vulnerabilities, with Sendmail recently (which I am not aware of).
Just curious, because I remember the time, when other distros made that move, but Slackware stuck with Sendmail despite its bad reputation for being difficult to administer and patch, and being plagued by a never-ending stream of security vulnerabilities.
So, does anyone know why the switch is made, now? (And please, don't turn this into an MTA flamewar --- I am really just interested what triggered that move right now).
I also have problems with (I guess, based on many hours research I've done) freetype - problems on my t420 (Intel i915), XFCE, fonts are too blurry everywhere. Hope that freetype upgrade will solve that.
Yes, they are blurry. No, Freetype won't "solve" that, because that's how their newest interpreter works :-/
Meanwhile, you can uncomment this line in /etc/profile.d/freetype.sh :
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.