Darth Vader,
I installed Linux Mint 18.? on my father-in-law's computer a couple of years ago with Plasma/KDE 5 (I don't know the specific version). That computer has a poor graphic card (an Intel onboard one) and it's still running fine. I don't know if desktop effects are on or off.
Anyway, IMHO this is an indication that Plasma 5 is ready for inclusion in any linux distribution, not only in Slackware :)

Off-topic:
Some years ago I was an enthusiast of desktop effects (good times those of Beryl :D ). But now I rarely use them...

Yeah, we know that Plasma5 works with Intel on-board videos, even myself I had a such success story.

BUT until version 5.13.1 it performed lamentably with trivial/budget/desktop AMD/ATI video cards, and about the NVIDIA side, well... I guess you have to bet on Nouveau or in the raw power of your NVIDIA beast to crunch the pixels. The lack of support of NVIDIA or AMD blobs I consider a total show stepper because we are not The Church of Stallman here.

BTW, without 3D support, the Plasma5 performs ridiculous slow. Tested myself.

/bin/login seems to have lost its SUIDness somewhere down the line.

Quoting an old debian bug report, where someone suggested removing SUID:
/bin/login is suid root for several good reasons. For one, it allows daemons that use it to run as non-root.

Also, though admittedly not particularly common these days, it used to be possible to invoke it from a login shell with "exec /bin/login" to login as a different user (as documented in the man-page). This no longer works without the SUID bit, as I just discovered.

I don't know whether this was an intentional change in slackware, and I can certainly understand wanting to keep the number of suid executables down to a minimum, but this is a user visible change in behavior (at least for old-school users like me who are in the habit of using uncommon stuff like this from time to time), so I thought it worth raising the question.

It's been setuid free since at least Slackware 8.1.

Just out of curiosity, how old?

It was changed at least 16 years ago (I don't keep pre-8.1 handy so perhaps longer ago). At this point, I'd say it's unlikely that you'll convince me to make it setuid root as shipped. I'll also note that the SlackBuild does not remove setuid from /bin/login, so this was done upstream, and shadow's upstream is Debian. So whatever their reason for keeping setuid in their reply to an old bug report, eventually they decided to remove it.

The debian bug report was somewhere in the region of 2008, so pretty ancient. It was one of the few hits I got when I googled bin/login SUID (trying to determine whether it was a upstream change or not.)

I'm sure I'd been successfully running /bin/login on the command line recently and I'm a one distro sorta guy so I'm not mixing up my distros or anything like that. If you say it's been like this since 8.1 I'll take your word for it. I'll have to assume that I'm either: mis-remembering running it as root; I'd fixed it locally and forgotten about it; or my mind is just going!

Thanks for the reply, and sorry for the noise.

I request Tig for inclusion. It is a ncurses interface to git. I find it good for a high level view and detailed views, and for searching within files or for files. All dependacies are met with a full install of Slackware, they are the basic libs of any real Linux: iconv, readline, git.

The homepage is here: https://www.tecmint.com/tig-a-comman...-repositories/

python-3.6.6
https://www.python.org/ftp/python/3....n-3.6.6.tar.xz

or

python-3.7.0
https://www.python.org/ftp/python/3....n-3.7.0.tar.xz

Any reason it would fit better in the main tree than SBo? Not that I disagree, just I am not very familiar with tig. :)

http://slackbuilds.org/repository/14.2/development/tig/

apmd still ships /usr/lib64/libapm.la despite the recent mass rebuild.

Err disregard, didn't see it moved to pasture/.

I thought I looked in SBo for it and didn' t see it. My bad, I have no argument for it to be in main if in SBo.

I suggest the addition of two files (slackware.sh and slackware.csh) to /etc/profile.d/ to contain Slackware specific aliases.
As an example, (following the recent change in -current to the use of /var/lib/pkgtools/packages for storing the package database), an alias 'lspkg' for listing installed packages could be defined.
slackware.sh
slackware.csh
A bash user could add this to their profile by adding '. /etc/profile.d/slackware.sh' to their ~/.bashrc.

I love the idea of lspkg! Even if this isn't added to Slackware itself, I think it will become an addition on mine.

if you like such a thing maybe a /usr/bin/lspkg bash script that is actually a wrapper for ls, so that you can pass options to it, could be better
EDIT: please ignore the noise: obviously you can pass options to the alias too.

A long time ago, CTWaley (a.k.a., thegeekster), posted some handy scripts for Slackware: lspkg, pkginfo, and whichpkg.

Mesa 18.1.3
Source: https://mesa.freedesktop.org/archive/mesa-18.1.3.tar.xz
Release notes: https://lists.freedesktop.org/archiv...ne/198970.html