Requests for current-next (15.0-->15.1)

Lockywolf · 07-19-2026, 11:39 PM

The page about the Slackbook on the official website still references "The Slackware Store", which has been deprecated.

http://www.slackware.com/book/

Also, on the "links" page:

http://www.slackware.com/links/

Freshmeat.net is not with us any more, so probably worth removing.

Linux.com is not run by VA Linux anymore, but is run by Linux Foundation, might be still useful.

teoberi · Yesterday, 02:13 AM

Sun Jul 19 21:53:17 UTC 2026
...
n/dovecot-2.4.4-x86_64-1.txz: Upgraded.
Note that the configuration for this is now completely different.
...
Finally here we go!

Options modified from the default in the configuration files are moved to dovecot.conf after first checking whether they have not been changed in name or syntax.
https://doc.dovecot.org/main/install....3-to-2.4.html

henca · Yesterday, 05:43 AM

Quote:

Originally Posted by Lockywolf

Freshmeat.net is not with us any more, so probably worth removing.

Or replaced with a link to https://freshcode.club/ which basically has taken over the role of good old freshmeat.

regards Henrik

chrisretusn · Yesterday, 09:51 AM

15.0 installer when Selecting source media, Install from NFS presents the DHCP Configuration choice Yes or No. The -current installer does not offer DHCP Configuration and starts with Assign IP Address. Would like to see the option added back in to -current to use DHCP Yes or No. Thanks.

jtsn · Yesterday, 10:07 AM

Quote:

Originally Posted by chrisretusn

15.0 installer when Selecting source media, Install from NFS presents the DHCP Configuration choice Yes or No. The -current installer does not offer DHCP Configuration and starts with Assign IP Address. Would like to see the option added back in to -current to use DHCP Yes or No. Thanks.

Adding to that I'd like to suggest adding NetworkManager together with a full wireless network stack to the installer. NM can be controlled through nmcli from the busybox shell and set up a variety of connections, most of them automatically (like DHCP over Ethernet). Getting connected to a wireless network can be as easy as typing

Code:

nmcli wifi connect SSID password PSK

Afterwards adding a few dialogs to the installer calling nmcli is piece of cake, or just call nmtui.

gmgf · Yesterday, 11:42 PM

two bugfix releases for Frameworks 6.28:

syntax-highlighting & kimageformats 6.28.1

https://mail.kde.org/pipermail/relea...ly/013939.html

Lockywolf · Today, 08:47 AM

Why do we have rc.mcelog in /etc/rc.d? Nothing starts it, and nothing seems to ever did for the past 5 years.

Perhaps move it to /usr/doc/mcelog-*/ ?

onebuck · Today, 10:00 AM

Hi,

Quote:

Originally Posted by Lockywolf

Why do we have rc.mcelog in /etc/rc.d? Nothing starts it, and nothing seems to ever did for the past 5 years.

Perhaps move it to /usr/doc/mcelog-*/ ?

I believe that 'rc.mcelog' can be start/restart/stop to be used for Log of CPU hardware errors(Machine Check Exceptions) which also decodes cryptic CPU errors into a human readable messages. Many times can log memory corrections, cache along with CPU and potential thermal errors.

All errors are logged into /var/log/mcelog. Root must start this daemon to log information since Slackware doesn't start it. This daemon is useful if you want early warning of potential developing hardware problems like failing RAM, over heating and even power-related machine check events. Even problems with a Motherboard problems may help with future errors made aware of need for diagnosis.

You can configure using /etc/mcelog/mcelog.conf

marav · Today, 04:15 PM

Firefox 153.0

https://www.firefox.com/en-US/firefo.../releasenotes/

Thunderbird 153.0

https://www.thunderbird.net/en-US/th.../releasenotes/

peake · Today, 04:31 PM

Quote:

Originally Posted by Lockywolf

Why do we have rc.mcelog in /etc/rc.d? Nothing starts it, and nothing seems to ever did for the past 5 years.

Perhaps move it to /usr/doc/mcelog-*/ ?

how bout this? (warning: untested)

Code:

--- source/a/sysvinit-scripts/scripts/rc.M      2026-07-17 17:20:06.506963465 -0400
+++ source/a/sysvinit-scripts/scripts/rc.M      2026-07-21 17:28:55.050074400 -0400
@@ -96,6 +96,11 @@ if [ -x /etc/rc.d/rc.syslog ]; then
   /etc/rc.d/rc.syslog start
 fi
 
+# Start the Machine Check Event (MCE) logger.
+if [ -x /etc/rc.d/rc.mcelog ]; then
+  /etc/rc.d/rc.mcelog start
+fi
+
 # Start the PC/SC-lite smart card daemon:
 if [ -x /etc/rc.d/rc.pcscd ]; then
   /etc/rc.d/rc.pcscd start

Lockywolf · Today, 06:03 PM

Quote:

Originally Posted by peake

how bout this? (warning: untested)

Code:

--- source/a/sysvinit-scripts/scripts/rc.M      2026-07-17 17:20:06.506963465 -0400
+++ source/a/sysvinit-scripts/scripts/rc.M      2026-07-21 17:28:55.050074400 -0400
@@ -96,6 +96,11 @@ if [ -x /etc/rc.d/rc.syslog ]; then
   /etc/rc.d/rc.syslog start
 fi
 
+# Start the Machine Check Event (MCE) logger.
+if [ -x /etc/rc.d/rc.mcelog ]; then
+  /etc/rc.d/rc.mcelog start
+fi
+
 # Start the PC/SC-lite smart card daemon:
 if [ -x /etc/rc.d/rc.pcscd ]; then
   /etc/rc.d/rc.pcscd start

I'm fine both ways. Either move it away from rc.d as being unused, or add it to a system rc script so that it's started.

But having a script hanging around with no goal is strange.