[SOLVED] How to create an Slackware ISO "up-to-date"?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Right now I have two installations of Slackware, the first one is Slackware 14.2 and the second one is Slackware 14+current. Both of them are "up to date".
My internet is very slow so it really takes a while installing updates after a fresh installation, specially upgrading to Slackware 14+current (it takes me 8 hours upgrading from the initial Slackware 14.2 ISO to Slackware14+current).
I think it will easier for me if I just have an ISO with, say, the Slackware 14.2 packages "up-to-date" ready. That way I don't have to update packages after a fresh installation. Same goes for Slackware14+current, I think.
How can I do so? I've never created ISO medias before, by the way.
Also I thought of another possibility. Maybe if I just save the packages that I've already downloaded to update the initial packages I can apply those updates to other installations, that way I can get rid of downloading the packages, still I have to apply the updates though. If there's a way to create an ISO with the updated packages I can avoid the two steps. Either way will be useful, at least it'll shorten the time I'll spend installing Slackware.
Last edited by slac; 08-09-2019 at 08:29 PM.
Reason: "it takes me" instead of "it takes"
Another option is to have install media (mini-iso without packages is ok too) and package tree somewhere (stick, hdd, local network) and select this tree on SOURCE step of setup.
For the 2nd task you can mirror slackware 14.2 tree, replace packages (and .asc, .txt) in slackware*/* with the new versions from patches/packages/ and build fresh ISO with empty /patches as described in /isolinux/README.TXT.
Slackware 14.2 added rust package since release. You can simple place rust package files in /patches/packages/ and install them manually after setup or place them in slackware/d/ and fix tagfile and maketag, maketag.ez scripts.
So you have an iso of slackware mount the ISO and then copy to a folder name that folder slackware-14.2 or slackware64-14.2
Code:
rsync -r -a -v --delete --progress --stats rsync://mirrors.kernel.org/slackware/slackware-14.2 .
or
Code:
rsync -r -a -v --delete --progress --stats rsync://mirrors.kernel.org/slackware/slackware64-14.2 .
or
Code:
rsync -r -a -v --delete --progress --stats rsync://mirrors.kernel.org/slackware/slackware-current .
or
Code:
rsync -r -a -v --delete --progress --stats rsync://mirrors.kernel.org/slackware/slackware64-current .
Or do like I do
Code:
mkdir -p /home/ftp/pub/Linux/Slackware
Then copy ISO contents to /home/ftp/pub/Linux/Slackware/slacware-14.2
The script I use will keep that updated. you just need to edit your /etc/slackpkg/mirrors like this.
Code:
# Local Directory
#----------------------------------------------------------------
# file://path/to/some/directory/
file://home/ftp/pub/Linux/Slackware/slackware-14.2/
#----------------------------------------------------------------
How to correctly exclude packages in ISO Slackware creation?
If I have already downloaded the Slackware64 14.2 tree (https://slackware.uk/slackware/slackware64-14.2/) to my computer and I want to leave out some packages in order to a create a custom ISO, what is the recommended approach to do so?
Let's say I want to create an ISO without the KDE (v4) packages (example).
I have this directory from where the ISO is created (https://slackware.uk/slackware/slack...2/slackware64/) and the KDE packages are in kde/kdei directories. Because I don't want those packages I can delete them in order to no longer have them inside the ISO I'll create, right?
Now, I haven't checked myself if you need to JUST edit the file: /slackware64-14.2/isolinux/setpkg to remove the kde and kdei installation options in the setup menu (when you are installing Slackware), but if I remove these lines:
Code:
"KDE" "The K Desktop Environment for X" on "The KDE series contains the K Desktop Environment for X." \
"KDEI" "International language support for KDE" off "The KDEI series provides support for languages other than US English in KDE." \
... then the setup won't show up those options when installing slackware from its setup, will they?
After doing that... I no longer have to install patches of KDE/KDEI but I think they still will show up when doing:
Code:
slackpkg install-new
slackpkg upgrade-all
What could be a convenient approach to avoid that? I mean... even if those patches for kde/kdei appear they can't be installed/applied since there aren't such packages installed in the system, but is it a correct option to just blacklist the packages in the file /etc/slackpkg/blacklist?
Also, should I delete the lines referring to those packages in the files (?), /slackware64-14.2/slackware64/FILE_LIST and /slackware64-14.2/slackware64/PACKAGES, ie:
I don't think that last thing should be done at all since when you do a rsync to the local tree, new files_list and packages files are downloaded/sync'd (I think(?)), so would it be better to just blacklist, is it true?
Last edited by slac; 08-14-2019 at 04:00 AM.
Reason: spell checking
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.