Requests for -current (14.2-->15.0)

upnort · 02-27-2021, 11:48 AM

Quote:

If you use sddm to login, the log file is located in ~/.local/share/sddm/xorg-session.log

Yes, but doesn't help users who launch X through startx.

upnort · 02-27-2021, 04:22 PM

Pat,

Cosmetic only.

Proposed rc.S stdout information messages.

Code:

--- rc.S
+++ rc.S.new
@@ -3,11 +3,15 @@
 # /etc/rc.d/rc.S:  System initialization script.
 #
 # Mostly written by:  Patrick J. Volkerding, <volkerdi@slackware.com>
-#
+
+# Tell the viewers what's going to happen.
+echo
+echo "Initializing."
 
 PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin
 
 # Try to mount /proc:
+echo "Mounting proc filesystem."
 /sbin/mount -v proc /proc -n -t proc 2> /dev/null
 
 # Mount sysfs next, if the kernel supports it:
@@ -176,6 +180,7 @@
 fi
 
 # Enable swapping:
+echo "Enabling swap partition."
 /sbin/swapon -a 2> /dev/null
 
 # Set the tick and frequency for the system clock.
@@ -319,6 +324,7 @@
 # Configure ISA Plug-and-Play devices:
 if [ -r /etc/isapnp.conf ]; then
   if [ -x /sbin/isapnp ]; then
+    echo "Configuring ISA Plug-and-Play devices."
     /sbin/isapnp /etc/isapnp.conf
   fi
 fi
@@ -354,7 +360,7 @@
   fi
 fi
 
-# Mount non-root file systems in fstab, but not NFS or SMB 
+# Mount non-root file systems in fstab, but not NFS or SMB
 # because TCP/IP is not yet configured, and not proc or sysfs
 # because those have already been mounted.  Also check that
 # devpts is not already mounted before attempting to mount

upnort · 02-27-2021, 04:28 PM

Pat,

Cosmetic only. Proposed rc.font patch:

Code:

--- rc.font
+++ rc.font.new
@@ -3,4 +3,5 @@
 # This selects your default screen font from among the ones in
 # /usr/share/kbd/consolefonts.
 #
+echo "Setting the console font:"
 setfont -v

USUARIONUEVO · 02-27-2021, 06:56 PM

pair libclc with same version of llvm.

Ressy · 02-27-2021, 07:44 PM

Quote:

Originally Posted by ponce

if it can help you decide I'm managing web services httpd and mariadb based on up-2-date minimal installs of slackware64-current at the moment with no issues (I'm actually doing it since 4 years), just some carefully reading the ChangeLog and managing eventual new dependencies when upgrading.
I agree it's not for everybody, but you surely are aware of that if you choose to use in production the development version of a distribution.

that's probably because of the php gd extension, but X libs actually show in the ldd output

It was GD actually yes, and my comments on that elsewhere still stand.

I am aware of risks of using current.

This is why I have now just one 64bit in production and the 32bit dev box
We need to run proprietary code on select machines, since slackware stable 14.2 is 5 years old, it does not build on it, not built on it for over a year due to too many antique libraries, so I moved 2 of those machines to centos, now running on RHEL since we can get free licences, all other serves remain slackware 14.2 at this stage

so I setup our dev box with current, as its an unused 32bit box last year, it was great, no hassles - apart from the niggly server stuff Pat incorrectly builds against X, like php/gd, and I think APR had a hissy as well, and the libusb issues which I understand are still ongoing with re-inserted devices but that one AFAIK, is a global issue, not just slackwares.

Tolerating those minor things that can be overcome, I was liking -current as very stable - until Jan 22 updates when it all went to hell, so you can appreciate if its kaput on my dev box, the single 64bit production box - which remains stable, stays un-updated, I think Jan 18 was its last update, and it stays that way until the dev box shows no more problems or such critical exploits or issues force us to migrate it to RHEL too.

I take note that the issues seem not to affect your 64bit, this is promising, although as Didier showed, the rsync bug did affect 64bit afterall, and as mariadb's Jira shows, the mariadb issue also affects others, but thats why we have dev boxes so we dont crash our entire production network, and we cant keep just waiting forever for it to be taken seriously by those who matter, who show they actually take very little notice of people they do not know.

Ressy · 02-27-2021, 07:56 PM

Quote:

Originally Posted by Didier Spaier

.

I guess tadgy ran an rsync update, his rsync has been down 4 days now

bassmadrigal · 02-27-2021, 08:56 PM

Quote:

Originally Posted by Ressy

apart from the niggly server stuff Pat incorrectly builds against X, like php/gd

Who are you to say it's built incorrectly? This is Pat's distro and he builds it how he wants. Some may want the functionality provided by building gd against X, while others may not.

If you don't like it, rebuild php to suit your needs, add the required X libraries, or switch OSes.

In the case of gd, a very simple rerunning of the gd.SlackBuild will build your program without any dependencies on X (assuming X isn't installed). Pat is simply using the defaults of that ./configure, which is if it detects X, it adds support for xpm files (if I remember correctly, as another user ran into similar issues and complained Pat was doing things wrong).

I can even give you the exact commands to fix this problem. Feel free to copy/paste and solve your problem.

Code:

wget -r -nH --no-parent --reject="index.htm*" --cut-dirs=4 https://mirror.slackbuilds.org/slackware/slackware64-current/source/l/gd/
cd gd
su -c "sh gd.SlackBuild"
su -c "upgradepkg --reinstall /tmp/gd-2.3.1-x86_64-2.txz

Now, if you want to actually be helpful rather than complain about how Pat has built his distro, you could maybe give some reasons on why gd should be built without X dependencies. It's a pretty simple flag for Pat to add to the SlackBuild to prevent it from being picked up. If you can convince him the potential benefits outweigh the potential costs, then you might not need to worry about recompiling that specific package.

Ressy · 02-27-2021, 09:19 PM

Quote:

Originally Posted by bassmadrigal

Who are you to say it's built incorrectly? This is Pat's distro and he builds it how he wants. Some may want the functionality provided by building gd against X, while others may not.

If you don't like it, rebuild php to suit your needs, add the required X libraries, or switch OSes.

In the case of gd, a very simple rerunning of the gd.SlackBuild will build your program without any dependencies on X (assuming X isn't installed). Pat is simply using the defaults of that ./configure, which is if it detects X, it adds support for xpm files (if I remember correctly, as another user ran into similar issues and complained Pat was doing things wrong).

I can even give you the exact commands to fix this problem. Feel free to copy/paste and solve your problem.

Code:

wget -r -nH --no-parent --reject="index.htm*" --cut-dirs=4 https://mirror.slackbuilds.org/slackware/slackware64-current/source/l/gd/
cd gd
su -c "sh gd.SlackBuild"
su -c "upgradepkg --reinstall /tmp/gd-2.3.1-x86_64-2.txz

Now, if you want to actually be helpful rather than complain about how Pat has built his distro, you could maybe give some reasons on why gd should be built without X dependencies. It's a pretty simple flag for Pat to add to the SlackBuild to prevent it from being picked up. If you can convince him the potential benefits outweigh the potential costs, then you might not need to worry about recompiling that specific package.

I dont answer to trolls, and you've shown you like to start [removed] around here, I have been running networks and isps since the early 90's I know how to obtain and build source you F'n tool. Now dont waste my time again. because I wont respond, I have better things to do on a Sunday arvo

perrin4869 · 02-27-2021, 10:09 PM

Pat,

Wrote about it in more detail here: https://www.linuxquestions.org/quest...es-4175688858/
mkinitrd_command_generator needs to be patched to correctly detect RAID devices

Code:

--- mkinitrd_command_generator.sh       2021-02-28 13:05:32.831726334 +0900
+++ mkinitrd_command_generator.sh.new   2021-02-28 13:06:23.577723912 +0900
@@ -307,6 +307,14 @@
       USING_RAID=1
       break
     fi
+
+    # Additional check in case $BASEDEV is a partition of /dev/$MD
+    for BLK in $(sfdisk -ld /dev/$MD | grep ^/dev | cut -d" " -f1); do
+      if [ "$BASEDEV" = "$BLK" ]; then
+        USING_RAID=1
+        break
+      fi
+    done
   done
 }

bassmadrigal · 02-28-2021, 12:32 AM

Quote:

Originally Posted by Ressy

I dont answer to trolls, and you've shown you like to start [removed] around here

I call people on stupidity. You say Pat is building it wrong and when I call you on it, you say I'm starting stuff and a troll?

Quote:

Originally Posted by Ressy

I have been running networks and isps since the early 90's I know how to obtain and build source you F'n tool.

It was intended as tongue-in-cheek. You seem to miss the obvious on how Pat builds Slackware, so I wanted to make sure you didn't miss the obvious on how to rebuild the software in Slackware

You say know how to obtain and build source, yet you complain that Pat doesn't build Slackware to your specific standards? And me calling on that makes me a tool? Sure...

I get it... you're big person who's been around a long time. I have no idea how long you've been using Slackware, but you seem to fail to realize that Pat builds things with everything installed. If you rerun the build script without X installed, your problem goes away (it's not a problem for people who follow the recommendation of a full install). If you choose to run Slackware without a full install, you'll potentially run into issues since the only automatic dependency resolution in Slackware is "install everything and all dependencies will be met".

If Pat doesn't have a good reason to override the ./configure autodetection, he won't. Maybe you should provide a reason beyond "it depends on something I don't have installed" and he might consider it.

Quote:

Originally Posted by Ressy

Now dont waste my time again. because I wont respond, I have better things to do on a Sunday arvo

You wasted everyone's time writing a post that included Pat is building software incorrectly since he doesn't follow your exacting specifications. You gave no reason on why Pat should remove support for xpm (other than "I don't want to install this dependency"). In fact, you didn't even request Pat to change it, just said he built it wrong. Sure seems like you have better things to do...

Feel free to respond or don't. I don't really care. (You can wait until Monday if you do really have better things to do on a Sunday.)

Didier Spaier · 02-28-2021, 02:13 AM

Quote:

Originally Posted by Ressy

I guess tadgy ran an rsync update, his rsync has been down 4 days now

Recently rsync was not down but the server was off line, for reasons clearly explained in this post then elaborated in this other post by Tadgy and that have nothing to do with rsync. Further you linked (with an arrow) to a post of mine unrelated to rsync, which is very confusing. Additionally slackware.uk is up and running since at least 18h00 UTC yesterday as I could then upload files there and the rsync issue had been solved by Tadgy several days before, reverting to the previous package built for Slackware-current.

franzen · 02-28-2021, 02:55 AM

The changelog mentions for hplip:

Quote:

Drop HAL support (LOL!)

Just noticed that the package etc-15.0 still supports hal

Code:

/etc/group:haldaemon:x:82:
/etc/passwd:haldaemon:x:82:82:User for HAL:/var/run/hald:/bin/false
/etc/shadow:haldaemon:*:9797:0:::::

gmgf · 02-28-2021, 04:49 AM

kernel-86_64

Pat, please , make the 'kernel' with the option 'CONFIG_IOMMU_DEFAULT_PASSTHROUGH=y

without this option actived many am3+ card have a conflict under usb1, usb2, and usb3 ports, without UEFI actived in bios.

kernel x86_64 openSUSE use this option, and this work fine here.

i have tested this,here, on your .config, no problem, and the usb ports are no longer in conflict .

camerabambai · 02-28-2021, 06:06 AM

Is a bad idea to add those lines in /etc/request.key.conf? On many distro are default, useful for mount cifs+kerberos.

Code:

create  cifs.spnego    *        *               /usr/sbin/cifs.upcall %k
create  dns_resolver   *        *               /usr/sbin/cifs.upcall %k

mats_b_tegner · 02-28-2021, 09:31 AM

Quote:

Originally Posted by USUARIONUEVO

pair libclc with same version of llvm.

libclc 11.1.0 seems to build fine on -current using LLVM/Clang 11.1.0. Just grab the

Code:

libclc.SlackBuild, etc.

from https://mirrors.slackware.com/slackw...urce/l/libclc/
I did get a fair number of compiler warnings but no errors.