Tuxedo
2018-09-27 16:24:12 UTC
Hello,
In short, my recent Slackware current installation, after setting up LVM,
encryption etc., I had a package selection included the following:
[*] Base Linux System
[*] Various applications that do not need X
[*] Program Development, (c, C++, Lisp, Perl, etc.)
[*] GNU Emacs
[*] FAQ lists, HOWTO documentation
[*] Linux kernel source
[*] KDE QT and the K Desktop Environment for X
[*] KDEI International Language Support for KDE
[*] System Libraries (some needed by both KDE and GNOME)
[*] Networking (TCP/IP, UUCP, Mail, News)
[*] TeX typesetting softare
[*] TCL Tcl/Tk scropt languages
[*] X Windows System
[*] X Appications
[*] XFCE The Xfce Desktop Envirobment for X
[*] Games
I also added a selection of various startup services:
rc.bind
rc.cups
rc.dnsmasq
rc.fuse
rc.http
rc.ip_forward
rc.ntpd
rc.inetd
rc.ip_forward
rc.messagebus
rc.ntpd
rc.rpc
rc.postfix
rc.rpc NFS daemons
rc.snmpd
rc.syslog
rc.sshd
... thereafter did the custom kernel with the mkinitrd_command_generator.sh
and manual LILO configuration. The image used when loading Linux is:
image = /boot/vmlinuz-generic-4.14.67
As far as I understand, 'slackpkg clean-all' will not change this setup?
It's suggested to uncomment kernel images in /etc/slackpkg/blacklist when
upgrading packages. Is this also relevant when doing the 'clean-all'?
#kernel-generic
#kernel-generic-smp
#kernel-huge
#kernel-huge-smp
#kernel-modules
#kernel-modules-smp
#kernel-source
After initial installation, I had added some packages which were simple to
install via sbo but there's no need to reinstall, so they can be temporarily
blacklisted:
sbopkg-0.38.1-noarch-1_wsr.tgz
perl-CGI-4.40-x86_64-1_SBo
perl-Image-Size-3.300-x86_64-1_SBo
perl-Sub-Uplevel-0.25-x86_64-1_SBo
perl-Test-Deep-1.127-x86_64-1_SBo
perl-Test-NoWarnings-1.04-x86_64-1_SBo
perl-html-parser-3.71-x86_64-1_SBo
perl-html-tagset-3.20-x86_64-1_SBo
perl-test-warn-0.36-x86_64-1_SBo
imagemagick-6.9.10_3-x86_64-1
From this point I've been trying but failing to get QMapShack working and in
the same process installing countless libraries by a mix of sbopkg, slpkg
and installpkg, so whatever conflicts those actions may have caused, their
resulting package installations can best be removed.
I uncomment some nearby mirror in /etc/slackpkg/mirrors
#----------------------------------------------------------------
# Slackware64-current
#----------------------------------------------------------------
# GERMANY (DE)
http://ftp.gwdg.de/pub/linux/slackware/slackware64-current/
I don't have an alternative booting method except the initial manual LILO
configuration, so I hope clean-all isn't going to change the original setup
in some default way that could get me locked out of the system. If so, how
do I prevent this from happening?
Are there other considerations that should be taken into account
before running 'slackpkg clean-all'?
Many thanks for any suggestions.
Tuxedo
In short, my recent Slackware current installation, after setting up LVM,
encryption etc., I had a package selection included the following:
[*] Base Linux System
[*] Various applications that do not need X
[*] Program Development, (c, C++, Lisp, Perl, etc.)
[*] GNU Emacs
[*] FAQ lists, HOWTO documentation
[*] Linux kernel source
[*] KDE QT and the K Desktop Environment for X
[*] KDEI International Language Support for KDE
[*] System Libraries (some needed by both KDE and GNOME)
[*] Networking (TCP/IP, UUCP, Mail, News)
[*] TeX typesetting softare
[*] TCL Tcl/Tk scropt languages
[*] X Windows System
[*] X Appications
[*] XFCE The Xfce Desktop Envirobment for X
[*] Games
I also added a selection of various startup services:
rc.bind
rc.cups
rc.dnsmasq
rc.fuse
rc.http
rc.ip_forward
rc.ntpd
rc.inetd
rc.ip_forward
rc.messagebus
rc.ntpd
rc.rpc
rc.postfix
rc.rpc NFS daemons
rc.snmpd
rc.syslog
rc.sshd
... thereafter did the custom kernel with the mkinitrd_command_generator.sh
and manual LILO configuration. The image used when loading Linux is:
image = /boot/vmlinuz-generic-4.14.67
As far as I understand, 'slackpkg clean-all' will not change this setup?
It's suggested to uncomment kernel images in /etc/slackpkg/blacklist when
upgrading packages. Is this also relevant when doing the 'clean-all'?
#kernel-generic
#kernel-generic-smp
#kernel-huge
#kernel-huge-smp
#kernel-modules
#kernel-modules-smp
#kernel-source
After initial installation, I had added some packages which were simple to
install via sbo but there's no need to reinstall, so they can be temporarily
blacklisted:
sbopkg-0.38.1-noarch-1_wsr.tgz
perl-CGI-4.40-x86_64-1_SBo
perl-Image-Size-3.300-x86_64-1_SBo
perl-Sub-Uplevel-0.25-x86_64-1_SBo
perl-Test-Deep-1.127-x86_64-1_SBo
perl-Test-NoWarnings-1.04-x86_64-1_SBo
perl-html-parser-3.71-x86_64-1_SBo
perl-html-tagset-3.20-x86_64-1_SBo
perl-test-warn-0.36-x86_64-1_SBo
imagemagick-6.9.10_3-x86_64-1
From this point I've been trying but failing to get QMapShack working and in
the same process installing countless libraries by a mix of sbopkg, slpkg
and installpkg, so whatever conflicts those actions may have caused, their
resulting package installations can best be removed.
I uncomment some nearby mirror in /etc/slackpkg/mirrors
#----------------------------------------------------------------
# Slackware64-current
#----------------------------------------------------------------
# GERMANY (DE)
http://ftp.gwdg.de/pub/linux/slackware/slackware64-current/
I don't have an alternative booting method except the initial manual LILO
configuration, so I hope clean-all isn't going to change the original setup
in some default way that could get me locked out of the system. If so, how
do I prevent this from happening?
Are there other considerations that should be taken into account
before running 'slackpkg clean-all'?
Many thanks for any suggestions.
Tuxedo