Requests for -current (14.2-->15.0)

chrisretusn · 03-06-2021, 08:29 PM

Quote:

Originally Posted by camerabambai

Why the /etc/slackpkg/mirrors on current has a 14.2 mirror as default?

Code:

# USE MIRRORS.SLACKWARE.COM (DO NOT USE FTP - ONLY HTTP FINDS A NEARBY MIRROR)
https://mirrors.slackware.com/slackw...ckware64-14.2/
#

If you decide to start using -current then you should know you will have to change it. My guess for the reason, is 14.2 is the stable release version thus mirror points to 14.2 because that is the default for the stable release version of Slackware. As it sits right now, if you have slackware-14.2 installed you will hose your system up since the "default" is set to slackware64=14.2 unless you change the mirror.

That said, I don't believe there should be a default mirror set in /etc/slackpkg/mirrors. I think /etc/slackpkg/mirrors should not have a default at all. Let the use pick a mirror as it was in the past.

My

rworkman · 03-06-2021, 10:44 PM

Quote:

Originally Posted by chrisretusn

If you decide to start using -current then you should know you will have to change it. My guess for the reason, is 14.2 is the stable release version thus mirror points to 14.2 because that is the default for the stable release version of Slackware. As it sits right now, if you have slackware-14.2 installed you will hose your system up since the "default" is set to slackware64=14.2 unless you change the mirror.

That said, I don't believe there should be a default mirror set in /etc/slackpkg/mirrors. I think /etc/slackpkg/mirrors should not have a default at all. Let the use pick a mirror as it was in the past.

My

You will get your money's worth in the 15.0.1 release :-)

Code:

commit 5c9d02046732b6b5970b6a209e32daaad44f6f55
Author: Robby Workman <rworkman@slackware.com>
Date:   Tue Mar 2 20:21:21 2021 -0600

    Update mirror files (14.2 -> 15.0)
    
    This also comments out the default mirror.

pghvlaans · 03-07-2021, 12:09 AM

It looks as though sudo might be compiling without PAM support for 64-bit systems. This code in the SlackBuild:

Code:

# Choose correct options depending on whether PAM is installed:
if [ -L /lib${LIBDIRSUFFIX}/libpam.so.? ]; then
  PAM_OPTIONS="--enable-pam-session --with-pam=yes"
  unset SHADOW_OPTIONS
else
  unset PAM_OPTIONS
  SHADOW_OPTIONS="--disable-pam-session --with-pam=no"
fi

looks for /lib/libpam.so.? on x86_64 because LIBDIRSUFFIX is not set. The PAM libraries are in /lib64, so the options --disable-pam-session and --with-pam=no were passed to .configure when I did the build. Using the patch below resulted in the PAM options being passed instead.

Patch:

Code:

--- sudo.SlackBuild     2021-03-07 14:17:22.894280178 +0900
+++ sudo.SlackBuild     2021-03-07 14:35:35.479313521 +0900
@@ -54,12 +54,16 @@

 if [ "$ARCH" = "i386" ]; then
   SLKCFLAGS="-O2 -march=i386 -mcpu=i686"
+  LIBDIRSUFFIX=""
 elif [ "$ARCH" = "i586" ]; then
   SLKCFLAGS="-O2 -march=i586 -mtune=i686"
+  LIBDIRSUFFIX=""
 elif [ "$ARCH" = "s390" ]; then
   SLKCFLAGS="-O2"
+  LIBDIRSUFFIX=""
 elif [ "$ARCH" = "x86_64" ]; then
   SLKCFLAGS="-O2 -fPIC"
+  LIBDIRSUFFIX="64"
 fi

 cd $TMP

(Sorry in advance if I'm off-base about this.)

Andypoo · 03-07-2021, 10:22 AM

Just leaving this here..

efivar-20191015_ca85d51-x86_64-3 still contains the regression that prevents installation on eMMC. Please run fetch-efivar.sh to pull a new version.

Details:
https://www.linuxquestions.org/quest...ml#post6127519

Thanks!

richarson · 03-07-2021, 12:04 PM

Quote:

Originally Posted by chrisretusn

If you decide to start using -current then you should know you will have to change it. My guess for the reason, is 14.2 is the stable release version thus mirror points to 14.2 because that is the default for the stable release version of Slackware. As it sits right now, if you have slackware-14.2 installed you will hose your system up since the "default" is set to slackware64=14.2 unless you change the mirror.

But if you're already running -current why would mirrors file revert to 14.2? I think that was the question.
For 14.2 of course mirrors should point to a 14.2 mirror by default (if at all, se below).

Quote:

Originally Posted by chrisretusn

That said, I don't believe there should be a default mirror set in /etc/slackpkg/mirrors. I think /etc/slackpkg/mirrors should not have a default at all. Let the use pick a mirror as it was in the past.

My

I respectfully disagree, especially since "MIRRORS.SLACKWARE.COM [...] FINDS A NEARBY MIRROR" which seems like a nice thing to do by default.
It'd be different if it pointed to say, a US mirror.

But of course that's just IMHO.

Cheers!

USUARIONUEVO · 03-07-2021, 01:08 PM

Quote:

Originally Posted by Andypoo

Just leaving this here..

efivar-20191015_ca85d51-x86_64-3 still contains the regression that prevents installation on eMMC. Please run fetch-efivar.sh to pull a new version.

Details:
https://www.linuxquestions.org/quest...ml#post6127519

Thanks!

I intersting on this fix , cause some portable devices have a emmc drive.

LuckyCyborg · 03-07-2021, 01:25 PM

Quote:

Originally Posted by USUARIONUEVO

I intersting on this fix , cause some portable devices have a emmc drive.

Let me fix for you.

Quote:

Originally Posted by USUARIONUEVO

I'm interested on this fix , because tons of portable devices have an eMMC drive.

And not only. All those Chinese mini-PCs or development boards sporting an x86 CPU, also they have as main storage an eMMC chip.

Let's hope that the eMMC support would not be the next "missing feature" like was on Slackware 14.2 the support for NVMe drives...

Didier Spaier · 03-07-2021, 01:53 PM

Quote:

Originally Posted by LuckyCyborg

All those Chinese mini-PCs or development boards sporting an x86 CPU, also they have as main storage an eMMC chip.

Which is just an SD card soldered to the main board, so when it will die the mini PC will be dead as well. Indeed that minimize the costs for the manufacturer. Thanks, but no, thanks, I prefer an SSD. No worry, they are ready to sell you an external SSD in addition...

LuckyCyborg · 03-07-2021, 02:15 PM

Quote:

Originally Posted by Didier Spaier

Which is just an SD card soldered to the main board, so when it will die the mini PC will be dead as well. Indeed that minimize the costs for the manufacturer. Thanks, but no, thanks, I prefer an SSD. No worry, they are ready to sell you an external SSD in addition...

Excuse me, but I do not understand well your point.

You requested to NOT support the eMMC drives because they are of lesser quality compared with SSDs, and Slackware will kill them?

Please note that I do not talked about the eMMCs qualities and performances, BUT rather about they being supported by Slackware as main system drive.

IF you have some particular information that Slackware -current is an eMMC killer, please be kind to disclose it because this is a really huge issue!

If you do this, you will save many people computers, as they can chose to install something else which does not broke their devices.

For example Ubuntu or even Windows 10 - I heard many people that they works well on their eMMC based devices for really long time.

mats_b_tegner · 03-07-2021, 03:11 PM

Mutt 2.0.6 was released on March 6, 2021. This is a bug-fix release, with some cleanup and small fixes.
ftp://ftp.mutt.org/pub/mutt/mutt-2.0.6.tar.gz

Didier Spaier · 03-07-2021, 04:13 PM

Quote:

Originally Posted by LuckyCyborg

You requested to NOT support the eMMC drives because they are of lesser quality compared with SSDs, and Slackware will kill them?

Not at all. They are supported in Slint, and given a fitting file system in 'auto' mode:

Code:

choosefilesystems() {
    echo "filesystems" >>$INSTALL/log
    DRIVENAME=$(cat $INSTALL/drivename)
    echo ext4 > $INSTALL/fstype
    if printf "$DRIVENAME"|grep -q mmc; then
        echo f2fs > $INSTALL/fstype
    fi
    FSTYPE=$(cat $INSTALL/fstype)
}

I was just expressing a personal choice, sorry for the off topic

metalforever · 03-07-2021, 10:18 PM

I'm sorry, I really cant figure out this issue and I need help.

1. vanilla full install of the 15.0 alpha w/ newest nvidia driver for 2070 super and KDE

Every time i exit X, such as to restart the computer or to control-alt-backspace into the terminal I get a black screen and the monitor says no signal (kde works fine) and I have to hard reset my computer because its still running.

elcore · 03-08-2021, 02:10 AM

Quote:

Originally Posted by metalforever

I'm sorry, I really cant figure out this issue and I need help.

1. vanilla full install of the 15.0 alpha w/ newest nvidia driver for 2070 super and KDE

Every time i exit X, such as to restart the computer or to control-alt-backspace into the terminal I get a black screen and the monitor says no signal (kde works fine) and I have to hard reset my computer because its still running.

Same problem here, with drivers version 340.x it was possible to switch to another (vesafb?) driver and back, while there was only a warning in the log.
Drivers above 390.x do not support this at all, no warning and no signal. I think starting the kernel with 'nomodeset' is now a requirement for some cards.
Anyway this problem is specific to binary driver, nouveau which is the default driver in Slackware does not yet have such limitations.

Petri Kaukasoina · 03-08-2021, 04:55 AM

sysklogd v2.2.2

metalforever · 03-08-2021, 07:34 AM

Quote:

Originally Posted by elcore

Same problem here, with drivers version 340.x it was possible to switch to another (vesafb?) driver and back, while there was only a warning in the log.
Drivers above 390.x do not support this at all, no warning and no signal. I think starting the kernel with 'nomodeset' is now a requirement for some cards.
Anyway this problem is specific to binary driver, nouveau which is the default driver in Slackware does not yet have such limitations.

How did you fix it? I can't run the open source drivers for this card.