The what should be updated in -current thread

Originally Posted by rworkman Thank you for such a wonderfully helpful suggestion and followup comment.

You seemed to miss that it was tongue-in-cheek and just a joke...so did the seven suckups who 'favored' your reply to it.

Hi,

What do you expect with a comment like that? This is the Slackware forum and your post was not warranted. Suck-ups??? Just users that found alignment/agreement with robby's post.

I just considered the source!

Originally Posted by ReaperX7 Speaking of updates, I've been wondering if we should begin looking into adding Wayland and any needed support libraries for it like libinput, libxkbcommon, as well as have projects rebuilt and linked to Wayland, officially integrated into Slackware. I know this is an odd mentioning, but because some projects are now utilizing Wayland based rendering protocols, maybe it could be looked into, as well as enabling support in projects like KDE and such to use Wayland protocols, and maybe even see about using a heavily Slackwareified Weston in some way, though I think this may require a few extra packages, or at least a minimal shared object library if necessary for anything missing.

None of the DEs in Slackware currently fully support Wayland. KDE is not there yet and the other DEs and WMs just don't support it at all. Having Wayland would at the moment only be interesting for Slackel (Enlightenment fully supports Wayland, AFAIK) and Dlackware for their Gnome desktop. Regarding Weston, parts of it depend on a specific software that is better not mentioned here and would also better go with Dlackware because of that.
Also, keep in mind that Wayland is sadly still not supported by the proprietary AMD and Nvidia drivers.

Weedle tiny patch for mkinitrd- if you give it kernel options in -m, it says "/sbin/mkinitrd: line 295: [: too many arguments"

--- a/mkinitrd      2013-06-11 11:33:38.000000000 +1000
+++ b/mkinitrd  2015-04-12 07:49:20.339919146 +1000
@@ -292,7 +292,7 @@
 # Parse for the use config file option first or else the other command
 # line options can not override /etc/mkinitrd.conf. 
 for opt in "$@"; do
-  if [ $opt = "-F" ]; then
+  if [ "$opt" = "-F" ]; then
       if [ -e /etc/mkinitrd.conf ]; then
         . /etc/mkinitrd.conf || badconf_file
       else

Originally Posted by TobiSGD None of the DEs in Slackware currently fully support Wayland. KDE is not there yet and the other DEs and WMs just don't support it at all. Having Wayland would at the moment only be interesting for Slackel (Enlightenment fully supports Wayland, AFAIK) and Dlackware for their Gnome desktop. Regarding Weston, parts of it depend on a specific software that is better not mentioned here and would also better go with Dlackware because of that. Also, keep in mind that Wayland is sadly still not supported by the proprietary AMD and Nvidia drivers.

Wayland requires EGL support which was added recently to the Nvidia OEM drivers. AMD... let's just not even bother with that abomination. We all know the free driver is far better at times than the AMD one. If, and when, they ever add it, well that's on them.

I'm only suggesting it due to KDE5/Plasma anyway, but only if it's added, but there is the argument of being prepared beforehand to thoroughly test things and make sure they're working. Yes, there has been no mentioning of other DEs or WMs supporting it, yet, outside the mainstays, but a few like i3 are doing spinoffs. Technically, KDE is there, but in KDE4 the offering was rudimentary at best while KDE5/Plasma takes more advantage of it. I would say if 14.2 does incorporate KDE5/Plasma, then yes, offer it, but equally, offer a way to select with or without Wayland at the time you launch KDE5.

Yes, Weston is more suited to Dlackware, but it still can be built to some extent or another. The only hard requirements it has is libinput (I have a SBo for that I need to upload to my repo) and libxkbcommon which is already in SBo. Yes, it's less than useful, but it can be good for testing and evaluation purposes.

Originally Posted by ReaperX7 Wayland requires EGL support which was added recently to the Nvidia OEM drivers. AMD... let's just not even bother with that abomination. We all know the free driver is far better at times than the AMD one. If, and when, they ever add it, well that's on them. I'm only suggesting it due to KDE5/Plasma anyway, but only if it's added, but there is the argument of being prepared beforehand to thoroughly test things and make sure they're working. Yes, there has been no mentioning of other DEs or WMs supporting it, yet, outside the mainstays, but a few like i3 are doing spinoffs. Technically, KDE is there, but in KDE4 the offering was rudimentary at best while KDE5/Plasma takes more advantage of it. I would say if 14.2 does incorporate KDE5/Plasma, then yes, offer it, but equally, offer a way to select with or without Wayland at the time you launch KDE5.

Fair enough. I am surprised about a possible spinoff for i3, since I use it myself and the last news I got is that the developer is not interested in a Wayland port for now. I know about i3way, but that sits idle without a single line of code since 2013. Is there another project?

Yes, Weston is more suited to Dlackware, but it still can be built to some extent or another. The only hard requirements it has is libinput (I have a SBo for that I need to upload to my repo) and libxkbcommon which is already in SBo. Yes, it's less than useful, but it can be good for testing and evaluation purposes.

I thought that weston-launch needs systemd to work, but after re-reading the Weston website it seems that I am wrong and that it can run without it, so that point of my previous post can be dismissed, thanks for the correction.

At one time early on it was recommended to have launchd for weston-launch, but it never materialized as a hard dependency. PAM is a recommended dependency also, but again, not a hard requirement.

I do know libinput is required for Weston (I submitted an SBo pack yesterday for it), as well as Wayland and a few other minor tools, but that's it.

Yeah, i3way has been dead. So far Xfce hasn't said a word on Wayland either, but still if it can be used, and it benefits, might be worth a tinker or two.

libcdio-0.93 (0.83 is 4 years old and iirc several programs using it didn't work or even segfaulted, I guess no one is using it anyways)
cryptsetup-1.6.7

Also, I'd like to see man replaced by man-db, somehow I couldn't get man and apropos working properly for a long time. Furthermore slocate to mlocate, slocate segfaulted for me some times, don't know if it's better in other ways (updating is quicker though).

But please don't request it

Traditionally Slackware only includes LTS kernels and only has a config file in /testing for mainline kernels.

mcelog gets the briefest of mentions in this thread.

Over the last few weeks I've been tracking down an error that I've been seeing in /var/log/messages which states

Apr 12 15:22:36 office kernel: [23270.195393] mce: [Hardware Error]: Machine check events logged
Apr 12 17:27:08 office kernel: [30748.900053] mce: [Hardware Error]: Machine check events logged
Apr 12 21:14:32 office kernel: [44405.280808] mce: [Hardware Error]: Machine check events logged
Apr 12 21:18:23 office kernel: [44636.598253] mce: [Hardware Error]: Machine check events logged
Apr 12 21:18:25 office kernel: [44638.014714] mce: [Hardware Error]: Machine check events logged
Apr 12 21:34:26 office kernel: [45600.007987] mce: [Hardware Error]: Machine check events logged
Apr 12 21:39:14 office kernel: [45888.285268] mce: [Hardware Error]: Machine check events logged
Apr 12 21:46:24 office kernel: [46319.083602] mce: [Hardware Error]: Machine check events logged
Apr 12 21:49:31 office kernel: [46506.314965] mce: [Hardware Error]: Machine check events logged

See discussion in
http://www.linuxquestions.org/questi...em-4175535727/

Decoding with the outdated mcelog tool in Slackware 14.1 gives this -

HARDWARE ERROR. This is *NOT* a software problem!
Please contact your hardware vendor
MCE 0
CPU 1 BANK 0 
TIME 1425459338 Wed Mar  4 08:55:38 2015
MCG status:
MCi status:
Error enabled
MCA: Unknown Error 5
STATUS 90000040000f0005 MCGSTATUS 0
MCGCAP c09 APICID 2 SOCKETID 0 
CPUID Vendor Intel Family 6 Model 60

whereas with the latest version of mcelog gives this

Hardware event. This is not a software error.
MCE 0
CPU 2 BANK 0 
TIME 1428909602 Mon Apr 13 08:20:02 2015
MCG status:
MCi status:
Corrected error
Error enabled
MCA: Internal parity error
STATUS 90000040000f0005 MCGSTATUS 0
MCGCAP c09 APICID 4 SOCKETID 0 
CPUID Vendor Intel Family 6 Model 60

The output from the latest mcelog tool is a bit less scary than the output delivered by the outdated version of mcelog that's currently in 14.1.

Alex

Originally Posted by Didier Spaier please don't request it

:doh : ()

Originally Posted by Didier Spaier But please don't request it

No, i rather see Linux 3.20 in slackware

libvorbis - 1.3.5

gnuplot 5.0 is out (-current has 4.6.3), and it contains some nice new features: http://gnuplot.sourceforge.net/ReleaseNotes_5_0.html

edit: didn't realise you wanted a freeze on upgrade suggestions: this one's not particularly important, so it can wait