How to use /patches at setup time with Slackware64-15.0 stable

iri · 04-26-2022, 10:23 AM

Hello,

Just downloaded Slackware64-15.0 and installed it, but all the updated packages from /patches were not install at "setup time".

Is there a simple way to use these updated packages (including kernel) at setup time? Rather than update/use slackpkg manually after install?

Thanks!

lazardo · 04-26-2022, 12:41 PM

Code:

# cd patches/packages && upgradpkg *.txz

Gerard Lally · 04-26-2022, 12:48 PM

Quote:

Originally Posted by lazardo

Code:

# cd patches/packages && upgradepkg *.txz

Typo

iri · 04-26-2022, 12:58 PM

But this will work when booting from USB, before running setup?

oily · 04-26-2022, 04:15 PM

FWIW, with 14.2 I've replaced package files in the slackware/* directories with the relevant updated files from patches before installation and it's worked fine. I suppose 15.0 is likely to work similarly.

iri · 04-27-2022, 12:25 PM

I was thinking the same thing, was not sure if it will work though, but then you have to delete the old packages that you're replacing, of course you could create a little script, but I thought maybe this is already a "built-in" feature in the Slackware installer/setup.

ozanbaba · 04-27-2022, 11:32 PM

Let's say your install medium mounted on /media/cdrom and your install point is /mnt. You can check them with mount command.
you can do something like this:

Code:

cd /media/cdrom/patches/packages
ROOT=/mnt upgradepkg *.t?z

you should able to do this after the installation and before the reboot. Of course, if patches has any new kernel, you need to update your initrd and lilo (for other boot systems, you need to check their documentation)

fredmyra · 11-07-2022, 01:52 PM

ozanbaba wrote:

Quote:

Let's say your install medium mounted on /media/cdrom and your install point is /mnt. You can check them with mount command.
you can do something like this:

Code:

cd /media/cdrom/patches/packages
ROOT=/mnt upgradepkg *.t?z

you should able to do this after the installation and before the reboot.

I am sorry for my own ignorance but I am stuck here and need help.

I am installing Slackware64-15.0 on an old laptop, have just exited setup, after its conclusion. While searching for tips on keeping my original kernel when getting a new kernel I ended in this thread and would like to follow the above instructions, but I am wondering if I must follow by installing those

Code:

*.t?z

packages .

The reason for this question is that my memory tells me that the only time I did anything with "t?z" (or perhaps "t*z" ???) I had to follow up by installing the packages.

I know my memory is not that good any longer though.

EDIT: In retrospect I suspect now that may have been kernel related packages that I first downloaded, but I still mistrust my memory.

elcore · 11-07-2022, 02:04 PM

Quote:

Originally Posted by fredmyra

The reason for this question is that my memory tells me that the only time I did anything with "t?z" (or perhaps "t*z" ???) I had to follow up by installing the packages.

Don't quote me on that, but from experience:
* = whatever, wildcard, joker card
? = unknown character
So when you do upgradepkg *.t?z you're doing an upgrade of all/whatever packages in the directory.
And since the extension is t?z, it means they could end with either txz or tgz, it's there to avoid upgrading *.txt.

If you already have packages with the same name installed, then "upgradepkg --reinstall *.t?z" is used to replace them.

henca · 11-07-2022, 02:12 PM

Quote:

Originally Posted by fredmyra

The reason for this question is that my memory tells me that the only time I did anything with "t?z" (or perhaps "t*z" ???) I had to follow up by installing the packages.

The t?z like t*z are both different wildcars matching Slackware package names like tgz and txz. The only difference is that t*z also matches longer words like teraherz .

Quote:

Originally Posted by fredmyra

EDIT: In retrospect I suspect now that may have been kernel related packages that I first downloaded, but I still mistrust my memory.

Well, there is a tricky thing with kernel patch packages. Upgrading or installing such a package also requires a reconfiguration of the boot method of choice. This means that the bootloader needs to be told to use the new kernel and if an initrd is used it has to be updated.

For that reason, it might not be best to upgrade kernel patch packages at the end of the installation, after the boot loader has been configured.

regards Henrik

fredmyra · 11-07-2022, 02:43 PM

I booted from an usb pendrive. Want to install to /dev/sda6. Shell says:

Code:

root@slackware:/#mount
/dev/initramfs on /proc type tmpfs (rw)
proc on /sys type sysfs (rw)
sysfs on /proc type tmpfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sda6 on /mnt type exct4 (rw)
/dev on /mnt/dev type none (rw,bind)
/proc on /mnt/proc type none (rw,bind)
/sys on /mnt/sys type none (rw,bind)
/proc on /mnt/proc type none (rw,bind)
/sys on /mnt/sys type none (rw,bind)
/dev on /mnt/dev type none (rw,bind)
root@slackware:/#lsblk
NAME    MAJ:MIN  RM    SIZE   RO  TYPE MOUNTPOINT
sda       8:0     0  465.8G    0  disk 
|-sda1    8:1     0    512M    0  part
|-sda2    8:2     0    513M    0  part
|-sda3    8:3     0      1k    0  part
|-sda5    8:5     0   34,6G    0  part
|-sda6    8:6     0   35.2G    0  part /mnt
|-sda7    8:7     0  275,7G    0  part
|-sda8    8:8     0     16G    0  part [SWAP]
sdb       8:16    1   14.3G    0  disk
|-sdb1    8:17    1    3.5G    0  part 
`-sdb2    8:18    1    1.4M    0  part
sr0      11:0     1   1024M    0  rom

Where can I understand my usb pendrive is mounted ?
Is there anything strange about the last 6 lines in the output of cmd mount ?

keefaz · 11-07-2022, 02:51 PM

use dmesg command for finding out usb key

LuckyCyborg · 11-07-2022, 02:55 PM

From what I know, the official Slackware 15.0 ISO has no packages into /patches directory, because it is not refreshed when patches are later released.

So, if OP wants /patches they could be found only with slackpkg or by manually mirroring the Slackware 15.0 tree and generating a custom ISO.

OR, I miss something?

Daedra · 11-07-2022, 03:27 PM

I don't think this can be done in an official capacity since there is no patches directory on the ISO. Easiest way if you didn't want to use slackpkg is you could write a script with this code and it would take care of the patches.

Code:

#!/bin/bash
mkdir /tmp/patches
cd /tmp/patches
wget -r -np -nd -l1 --accept=*.t?z https://slackware.osuosl.org/slackware64-15.0/patches/packages/
upgradepkg *.t?z

LuckyCyborg · 11-07-2022, 03:29 PM

Quote:

Originally Posted by Daedra

I don't think this can be done in an official capacity since there is no patches directory on the ISO. Easiest way if you didn't want to use slackpkg is you could write a script with this code and it would take care of the patches.

Code:

#!/bin/bash
mkdir /tmp/patches
cd /tmp/patches
wget -r -np -nd -l1 --accept=*.t?z https://slackware.osuosl.org/slackware64-15.0/patches/packages/
upgradepkg *.t?z

And what you do with the kernels, which are in their own subdirectory?