LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-15-2016, 10:21 AM   #1
bifferos
Member
 
Registered: Jul 2009
Posts: 331

Rep: Reputation: 119Reputation: 119
A minimal Slackware install (Slack64 14.2)


I've seen a few references on the 'net about how to get a minimal install, but wanted to investigate for myself. I'm recording the results here in case they are useful to someone. Please let's not start a long thread about what constitutes a useful install set. A useful Linux system could consist of Kernel + My application as init, after all!

Using VirtualBox[1] I selected only the 'A' series disks, then snapshot the machine at the package selection menu, then started repetitively choosing different a-series packages and seeing what happened. The one conclusion I reached is that 'REQUIRED' is not always helpful. There are packages that are most definitely not required, and some not labelled as such which are. Anyhow, on to my findings. Here is the list of required packages for 14.2 (64-bit), and my notes about why.

aaa_base aaa_elflibs bash bin coreutils I didn't do much experimentation with these, I figured that'd be just silly.

devs You get a boot without device files, but it's handy to have the directories because stuff tries to mount filesystems on subdirs of /dev.

e2fsprogs Needed to avoid fsck error and drop to single-user every time you boot, but you could hack the init scripts to avoid needing this.

etc Didn't try to remove it

eudev Got a boot without it, I put it back in though :-)

glibc-solibs Required only if you want to set a password during install.

grep Referenced in rc.M et al, will boot without it with reduced functionality.

kernel-huge With a minimal system the non-huge kernel gave a panic on boot, which may be down to initrd requirements. The menu system help eluded to this. I stuck with huge.

kernel-modules kmod I actually needed modules so didn't try to remove them.

lilo My favourite bootloader, but you don't need it for Grub of course.

pkgtools sed tar xz Needed if you want to install packages after boot, instead of installing them during setup.

shadow I assume this is also needed for the passwd program.

syslinux Required if you're creating a USB boot stick only. Leaving it out results in an error message during install about missing mbr.bin but it can be safely ignored if not creating boot stick.

sysvinit sysvinit-scripts You'll need this if you want to go multi-user but can technically boot without it.

util-linux Didn't try to remove it.

So that's all. A lot less than I thought to get a reasonably clean boot. I may follow-up with the packages needed for other basic operations, e.g. kernel compilation if there is interest.

regards,
Biff.

[1] It's possible (but unlikely) real machines give different results.


Followup #1, add basic network access:

n/net-tools If you need to set an IP address statically.

n/dhcpcd If you need to set an IP address dynamically.

n/iputils For 'ping' utility :-)

n/openssl a/openssl-solibs Needed for openssl, e.g. scp

Last edited by bifferos; 12-16-2016 at 04:28 AM.
 
Old 12-15-2016, 06:11 PM   #2
atelszewski
Member
 
Registered: Aug 2007
Distribution: Slackware
Posts: 890

Rep: Reputation: Disabled
Hi,

Quote:
Originally Posted by bifferos View Post
syslinux Required if you're using lilo. Can possibly avoid if using Grub
Is it really so?

I think all of the three: lilo, syslinux and grub can work on their own, without any dependency.

--
Best regards,
Andrzej Telszewski
 
Old 12-16-2016, 03:33 AM   #3
bifferos
Member
 
Registered: Jul 2009
Posts: 331

Original Poster
Rep: Reputation: 119Reputation: 119
Quote:
Originally Posted by atelszewski View Post
Hi,


Is it really so?

I think all of the three: lilo, syslinux and grub can work on their own, without any dependency.

--
Best regards,
Andrzej Telszewski
My bad. You only need syslinux if creating a USB boot stick, and creating a boot stick comes just before the lilo install. Further, you get an error message about missing mbr.bin due to syslinux not present *before* you get a chance to say whether you want the USB boot stick in the first place. That could be considered a bug.

Click image for larger version

Name:	mbr.png
Views:	50
Size:	2.1 KB
ID:	23780

Once you add the syslinux package you get the correct Create/Skip prompt.

I updated the list above accordingly. If you're happy with an ugly install experience you can still leave syslinux out, everything seems to work, as you say, but I still left it in my list above for cosmetic reasons.

Last edited by bifferos; 12-16-2016 at 03:57 AM.
 
Old 12-16-2016, 03:02 PM   #4
atelszewski
Member
 
Registered: Aug 2007
Distribution: Slackware
Posts: 890

Rep: Reputation: Disabled
Hi,

Quote:
Originally Posted by bifferos View Post
If you're happy with an ugly install experience you can still leave syslinux out
The solution might be not to use setup at all.
Have a look here.

--
Best regards,
Andrzej Telszewski
 
1 members found this post helpful.
Old 12-16-2016, 05:54 PM   #5
atelszewski
Member
 
Registered: Aug 2007
Distribution: Slackware
Posts: 890

Rep: Reputation: Disabled
Hi,

I hope I don't hijack your thread ;-)

Just an amazing note.
If you want firewall, you need iptables.
iptables requires (among others) libpcap.
libpcap requires (among others) dbus.

That was quite a surprise when I was playing the way you play now.
On the good side, it seems that the dbus daemon does not have to run for iptables to work.

BTW, I encourage you play with sbbdep.
You'll be able to find deps more easily.

--
Best regards,
Andrzej Telszewski
 
Old 12-19-2016, 04:07 AM   #6
bifferos
Member
 
Registered: Jul 2009
Posts: 331

Original Poster
Rep: Reputation: 119Reputation: 119
Quote:
Originally Posted by atelszewski View Post
If you want firewall, you need iptables.
iptables requires (among others) libpcap.
libpcap requires (among others) dbus.
Yes, I will be figuring out that dependency set and will update my post with the full list for iptables, as I have a future requirement for that.

Thanks for the tip about sbbdep.
 
Old 03-05-2020, 03:09 AM   #7
bifferos
Member
 
Registered: Jul 2009
Posts: 331

Original Poster
Rep: Reputation: 119Reputation: 119
I revisited this ancient thread last night, because I wanted to check the situation with -current. Unbelievably my 14.2 package list still applies, except I needed to add hostname, to avoid an error during boot (but it doesn't stop the boot). I don't know if I just overlooked that from the last investigation.

I'm truly awestruck by how consistent the Slackware team have kept this.

I will need to update the network section a little, I'll post more on that later.

Last edited by bifferos; 03-05-2020 at 03:13 AM.
 
1 members found this post helpful.
Old 03-05-2020, 03:14 PM   #8
dalacor
Member
 
Registered: Feb 2019
Distribution: Slackware
Posts: 73

Rep: Reputation: Disabled
I came across your thread. This interests me as I would like to prune the other directories to only install what I need to actually run Slackware and the core software. I have already done some pruning on my own system.

Currently, I only install the following:

A (everything in this)
AP (only cgmanager, slackpkg and vim) as I use Vim, you need Slackpkg to update Slackware and for some reason I needed cgmanager, but probably when I prune the A directory, I won't need it anymore
D (everything in this)
L (everything in this)
N (everything in this)

I don't install any of the other directories.

What I use Slackware for is running E2guardian (a web filtering program) so I need make, make install etc. I need openssl for certificates and Openvpn and E2guardian, I need ssh for remote access and I install Openvpn to create the vpn. I also need Iptables etc.

If you are planning on creating a Slackware system that you can use without a gui environment, the above should be really all that you need. But I am wanting to prune the A, D, L and N directories as there is a lot of stuff I just don't need running there like wireless network manager and Rust etc. It would reduce the amount of time to install, download and update Slackware if I am installing far fewer packages.

I will try and see if I can get the system working using your A list as a suggestion, to prune the system even further.

By the way you need glibc-solibs for other things as well - this is a critical package! If you update Slackware using slackpkg and you don't update glibc-solibs first before updating the packages, you will have problems.

https://docs.slackware.com/howtos:sl...:systemupgrade

Good job on the A: series. It has inspired me to work on the N series soon.
 
1 members found this post helpful.
Old 03-05-2020, 06:24 PM   #9
bifferos
Member
 
Registered: Jul 2009
Posts: 331

Original Poster
Rep: Reputation: 119Reputation: 119
If you would like a more sensible minimal install then you can check out the skip files from vagaslack:

https://github.com/bifferos/vagaslack/tree/master/tags

These package set description files work in a kind-of cascade where you have top-level files detailing the packages to be removed from the install, and then sub-directory files supplementing these lists with additional files to be removed for specific Slackware versions. When you download an ISO it will have a name like

slackware64-<version>-install-dvd.iso

The create_iso.py script looks at the version, then decomposes the ISO, chooses an appropriate set of .skp files, and using this code:

https://github.com/bifferos/vagaslac...ate_iso.py#L66

Creates appropriate tagfiles.

I prefer to deal in lists of packages I'm removing (rather than installing), so a new release of -current doesn't break the system I'm creating. Note that my default install is a little heavy-weight there because it includes kernel sources required for installation of VirtualBox guest additions :-(.

cheers,
Biff.
 
Old 03-06-2020, 06:12 AM   #10
a.out
Member
 
Registered: Feb 2019
Location: Luxembourg
Distribution: Slackware on server, Bunsenlabs on desktop
Posts: 30

Rep: Reputation: Disabled
Quote:
Originally Posted by atelszewski View Post
Hi,
Just an amazing note.
If you want firewall, you need iptables.
iptables requires (among others) libpcap.
libpcap requires (among others) dbus.
Yes, this was discussed here:

https://www.linuxquestions.org/quest...ml#post5961625
 
Old 03-06-2020, 07:07 AM   #11
ehartman
Senior Member
 
Registered: Jul 2007
Location: Delft, The Netherlands
Distribution: Slackware
Posts: 1,585

Rep: Reputation: 818Reputation: 818Reputation: 818Reputation: 818Reputation: 818Reputation: 818Reputation: 818
Quote:
Originally Posted by bifferos View Post
I needed to add hostname, to avoid an error during boot (but it doesn't stop the boot). I don't know if I just overlooked that from the last investigation.
The 'hostname' package is a reasonable new addition, so wasn't there yet in 14.2
From -current's ChangeLog
Quote:
Fri Nov 17 00:56:25 UTC 2017
a/hostname-3.18-<arch>-1.txz: Added.
This is the latest version of the hostname utility, broken out into a new package to get rid of duplication between util-linux and net-tools.
 
1 members found this post helpful.
Old 03-06-2020, 07:39 AM   #12
deNiro
Member
 
Registered: Jun 2003
Location: Belgium
Distribution: Salix 14.2 and Slackware-current
Posts: 168

Rep: Reputation: Disabled
A while ago I was experimenting a bit with minimal install of slackware 14.2. And used the post from @nobodino as a start. here is that post. The txt file splits it up nicely.

That list worked great, though it is really minimalistic, so it requires some time to figure out the stuff you need on top of that if you want to install/compile certain software later.

Here is what is included in that text file, created by @nobodino :


bare system: 23 packages
-----------
-rw-r--r-- 1 root root 2095 juil. 31 11:07 aaa_base-14.2-i586-5
-rw-r--r-- 1 root root 2689 juil. 31 11:07 aaa_elflibs-15.0-i586-2
-rw-r--r-- 1 root root 13765 juil. 31 11:08 aaa_terminfo-6.1_20180616-i586-1
-rw-r--r-- 1 root root 7389 juil. 31 11:08 bash-4.4.023-i586-1
-rw-r--r-- 1 root root 9095 juil. 31 11:08 coreutils-8.30-i586-1
-rw-r--r-- 1 root root 143762 oct. 29 2017 devs-2.3.1-noarch-25
-rw-r--r-- 1 root root 5261 juil. 31 11:08 e2fsprogs-1.44.3-i586-1
-rw-r--r-- 1 root root 1004 juil. 31 11:08 etc-15.0-i586-7
-rw-r--r-- 1 root root 3551 juil. 31 11:08 eudev-3.2.5-i586-4
-rw-r--r-- 1 root root 7953 juil. 31 11:07 glibc-solibs-2.27-i586-4
-rw-r--r-- 1 root root 5039 mai 7 10:26 grep-3.1-i586-2
-rw-r--r-- 1 root root 1060 juil. 31 11:08 kernel-huge-smp-4.14.59_smp-i686-1
-rw-r--r-- 1 root root 303280 juil. 31 11:08 kernel-modules-smp-4.14.59_smp-i686-1
-rw-r--r-- 1 root root 3454 mai 7 10:26 kmod-25-i586-2
-rw-r--r-- 1 root root 5116 juil. 31 11:07 pkgtools-15.0-noarch-21
-rw-r--r-- 1 root root 5981 juil. 31 11:09 procps-ng-3.3.15-i586-2
-rw-r--r-- 1 root root 4604 mai 7 10:25 sed-4.5-i586-2
-rw-r--r-- 1 root root 18937 juil. 31 11:09 shadow-4.2.1-i586-5
-rw-r--r-- 1 root root 1587 juil. 31 11:09 sysvinit-2.90-i586-1
-rw-r--r-- 1 root root 925 juil. 31 11:09 sysvinit-scripts-2.1-noarch-14
-rw-r--r-- 1 root root 4690 mai 7 10:27 tar-1.30-i586-2
-rw-r--r-- 1 root root 15728 juil. 31 11:09 util-linux-2.32.1-i586-1
-rw-r--r-- 1 root root 3068 mai 7 10:27 xz-5.2.4-i586-1

to upgrade packages manually: 1 package
--------------------
-rw-r--r-- 1 root root 4948 mai 7 10:26 findutils-4.4.2-i586-2

to access internet dynamicaly with a text browser: 9 packages
--------------------
-rw-r--r-- 1 root root 1581 juil. 31 11:08 dhcpcd-7.0.7-i586-1
-rw-r--r-- 1 root root 4441 juil. 31 11:08 gnupg-1.4.23-i586-1
-rw-r--r-- 1 root root 5831 juil. 31 11:08 iproute2-4.17.0-i586-1
-rw-r--r-- 1 root root 1154 mai 7 10:26 iputils-s20140519-i586-2
-rw-r--r-- 1 root root 8618 juin 3 14:42 lynx-2.8.9dev.19-i586-1
-rw-r--r-- 1 root root 1389 mai 7 10:27 ncftp-3.2.6-i586-2
-rw-r--r-- 1 root root 1525 mai 7 10:27 net-tools-20170208_479bb4a-i586-21
-rw-r--r-- 1 root root 1309 juin 3 14:42 network-scripts-15.0-noarch-8
-rw-r--r-- 1 root root 1293 mai 20 16:46 openssl-solibs-1.1.0h-i586-2

---------------------
dhcpcd -t 10 eth0
ifconfig eth0
ping free.fr
lynx http://ftp.osuosl.org/pub/slackware/slackware-current
or
ncftp ftp://ftp.osuosl.org/pub/slackware/slackware-current
---------------------

bare-x11 system: 55 packages
----------------
-rw-r--r-- 1 root root 6024 juil. 31 11:08 blackbox-0.73-i586-1
-rw-r--r-- 1 root root 4305 mai 7 10:25 dbus-1.12.8-i586-1
-rw-r--r-- 1 root root 2460 juil. 31 11:08 dejavu-fonts-ttf-2.37-noarch-4
-rw-r--r-- 1 root root 1001 mai 7 10:26 font-alias-1.0.3-noarch-2
-rw-r--r-- 1 root root 10002 mai 7 10:26 fontconfig-2.12.6-i586-2
-rw-r--r-- 1 root root 15231 juil. 31 11:08 font-misc-misc-1.1.2-noarch-3
-rw-r--r-- 1 root root 4089 mai 7 10:26 freetype-2.9-i586-2
-rw-r--r-- 1 root root 7322 juil. 31 11:08 harfbuzz-1.8.4-i586-1
-rw-r--r-- 1 root root 2818 mai 11 08:41 libdrm-2.4.92-i586-1
-rw-r--r-- 1 root root 1148 mai 7 10:26 libevdev-1.5.9-i586-2
-rw-r--r-- 1 root root 928 mai 7 10:26 libfontenc-1.1.3-i586-2
-rw-r--r-- 1 root root 1227 juil. 31 11:08 libgcrypt-1.8.3-i586-1
-rw-r--r-- 1 root root 3805 juil. 31 11:08 libgpg-error-1.32-i586-1
-rw-r--r-- 1 root root 1282 mai 7 10:26 libICE-1.0.9-i586-3
-rw-r--r-- 1 root root 1001 mai 7 10:26 libmnl-1.0.4-i586-3
-rw-r--r-- 1 root root 958 mai 7 10:26 libpciaccess-0.14-i586-2
-rw-r--r-- 1 root root 1092 mai 7 10:26 libSM-1.2.2-i586-3
-rw-r--r-- 1 root root 2735 mai 7 10:30 libunwind-1.2.1-i586-3
-rw-r--r-- 1 root root 49772 mai 7 10:26 libX11-1.6.5-i586-2
-rw-r--r-- 1 root root 1315 mai 7 10:26 libXau-1.0.8-i586-3
-rw-r--r-- 1 root root 4738 mai 7 10:26 libXaw-1.0.13-i586-2
-rw-r--r-- 1 root root 118615 mai 7 10:27 libxcb-1.13-i586-2
-rw-r--r-- 1 root root 1021 mai 7 10:26 libXdamage-1.1.4-i586-3
-rw-r--r-- 1 root root 1046 mai 7 10:26 libXdmcp-1.1.2-i586-3
-rw-r--r-- 1 root root 4359 mai 7 10:26 libXext-1.3.3-i586-3
-rw-r--r-- 1 root root 1013 mai 7 10:26 libXfixes-5.0.3-i586-2
-rw-r--r-- 1 root root 1180 mai 7 10:26 libXfont2-2.0.3-i586-2
-rw-r--r-- 1 root root 962 mai 7 10:26 libXft-2.3.2-i586-4
-rw-r--r-- 1 root root 1232 juil. 31 11:08 libXinerama-1.1.4-i586-1
-rw-r--r-- 1 root root 1143 mai 7 10:27 libxkbfile-1.0.9-i586-2
-rw-r--r-- 1 root root 1758 mai 7 10:26 libXmu-1.1.2-i586-3
-rw-r--r-- 1 root root 1000 mai 7 10:26 libXpm-3.5.12-i586-2
-rw-r--r-- 1 root root 1052 mai 7 10:26 libXrender-0.9.10-i586-2
-rw-r--r-- 1 root root 910 mai 7 10:27 libxshmfence-1.3-i586-2
-rw-r--r-- 1 root root 11840 mai 7 10:26 libXt-1.1.5-i586-2
-rw-r--r-- 1 root root 1941 mai 7 10:26 libXxf86vm-1.1.4-i586-3
-rw-r--r-- 1 root root 6051 juil. 31 11:09 mesa-18.1.5-i586-1
-rw-r--r-- 1 root root 894 mai 7 10:27 mkfontdir-1.0.7-noarch-2
-rw-r--r-- 1 root root 756 mai 7 10:27 mkfontscale-1.1.3-i586-2
-rw-r--r-- 1 root root 1159 mai 7 10:27 mtdev-1.1.5-i586-2
-rw-r--r-- 1 root root 2978 mai 7 10:27 nettle-3.4-i586-2
-rw-r--r-- 1 root root 918 mai 7 10:27 pixman-0.34.0-i586-2
-rw-r--r-- 1 root root 803 mai 7 10:27 setxkbmap-1.3.1-i586-2
-rw-r--r-- 1 root root 852 mai 7 10:27 utempter-1.1.6-i586-3
-rw-r--r-- 1 root root 1065 mai 7 10:27 x11-skel-7.7-i586-4
-rw-r--r-- 1 root root 660 mai 7 10:27 xauth-1.0.10-i586-2
-rw-r--r-- 1 root root 1306 juin 3 14:42 xf86-input-evdev-2.10.6-i586-1
-rw-r--r-- 1 root root 1127 mai 13 15:11 xf86-input-keyboard-1.9.0-i586-3
-rw-r--r-- 1 root root 1069 mai 13 15:11 xf86-video-vesa-2.4.0-i586-3
-rw-r--r-- 1 root root 859 mai 7 10:27 xinit-1.4.0-i586-2
-rw-r--r-- 1 root root 812 juil. 31 11:09 xkbcomp-1.4.2-i586-1
-rw-r--r-- 1 root root 736 mai 7 10:27 xkbevd-1.1.4-i586-2
-rw-r--r-- 1 root root 14415 mai 7 10:27 xkeyboard-config-2.22-noarch-2
-rw-r--r-- 1 root root 7701 juil. 31 11:09 xorg-server-1.20.0-i586-3
-rw-r--r-- 1 root root 2197 mai 7 10:27 xterm-333-i586-1


to upgrade/install packages via slackpkg: 8 packages + 1 package (mc) to edit /etc/slackpkg.conf
--------------------------------
-rw-r--r-- 1 root root 1325 mai 13 15:11 bzip2-1.0.6-i586-3
-rw-r--r-- 1 root root 6623 mai 7 10:26 dialog-1.3_20170509-i586-2
-rw-r--r-- 1 root root 5130 mai 7 10:26 gawk-4.2.1-i586-2
-rw-r--r-- 1 root root 2969 juin 3 14:42 libunistring-0.9.10-i586-1
-rw-r--r-- 1 root root 14679 juil. 31 11:08 mc-4.8.21-i586-1
-rw-r--r-- 1 root root 61539 juil. 31 11:09 ncurses-6.1_20180616-i586-1
-rw-r--r-- 1 root root 3548 juil. 31 11:07 slackpkg-2.83.0-noarch-3
-rw-r--r-- 1 root root 4685 mai 11 08:41 wget-1.19.5-i586-1
-rw-r--r-- 1 root root 1108 mai 7 10:27 which-2.21-i586-2

to access man-pages : 5 packages
-------------------------------
-rw-r--r-- 1 root root 25147 mai 7 10:26 groff-1.22.3-i586-3
-rw-r--r-- 1 root root 1201 mai 7 10:26 gzip-1.9-i586-2
-rw-r--r-- 1 root root 895 mai 7 10:26 less-530-i586-3
-rw-r--r-- 1 root root 5027 nov. 11 2017 man-1.6g-i586-3
-rw-r--r-- 1 root root 70933 mai 7 10:27 man-pages-4.16-noarch-1

-------------------------------

to edit files: 2 packages (1 vi like, 1 emacs like)
-------------------------------
-rw-r--r-- 1 root root 4598 mai 7 10:26 elvis-2.2_0-i586-4
-rw-r--r-- 1 root root 7197 mai 7 10:26 jed-0.99_19-i586-3
-------------------------------

Last edited by deNiro; 03-06-2020 at 07:44 AM.
 
1 members found this post helpful.
Old 03-06-2020, 11:44 AM   #13
ehartman
Senior Member
 
Registered: Jul 2007
Location: Delft, The Netherlands
Distribution: Slackware
Posts: 1,585

Rep: Reputation: 818Reputation: 818Reputation: 818Reputation: 818Reputation: 818Reputation: 818Reputation: 818
Quote:
Originally Posted by dalacor View Post
A (everything in this)
You never need "everything" in the A series, for instance, you normally should install either kernel-huge or kernel-generic (and in 32-bit: either the smp or the non-smp version of those). Note that kernel-generic does need kernel-modules too, the huge kernel often does not.
Packages like btrfs-tools, dosfstools, e2fsprogs, f2fs-tools, jfsutils, ntfs-3g, reiserfsprogs and xfsprogs are only needed when you have (or expect to need) that kind of file system in your installation.
And, of course, floppy nowadays mostly isn't needed as most modern systems do not that kind of drive anymore. Further lhasa, unarj and zoo are for file archivers that you normally don't see anymore.
 
2 members found this post helpful.
Old 03-06-2020, 04:55 PM   #14
slac-in-the-box
Member
 
Registered: Mar 2010
Location: oregon
Distribution: slackware64-current
Posts: 367

Rep: Reputation: 162Reputation: 162
I started using /etc/slackpkg/blacklist to do just that, blacklist every unneeded package. Made keeping current on servers with customized minimal installs a breeze.
 
Old 03-07-2020, 07:31 AM   #15
dalacor
Member
 
Registered: Feb 2019
Distribution: Slackware
Posts: 73

Rep: Reputation: Disabled
Quote:
Originally Posted by ehartman View Post
You never need "everything" in the A series, for instance, you normally should install either kernel-huge or kernel-generic (and in 32-bit: either the smp or the non-smp version of those). Note that kernel-generic does need kernel-modules too, the huge kernel often does not.
Packages like btrfs-tools, dosfstools, e2fsprogs, f2fs-tools, jfsutils, ntfs-3g, reiserfsprogs and xfsprogs are only needed when you have (or expect to need) that kind of file system in your installation.
And, of course, floppy nowadays mostly isn't needed as most modern systems do not that kind of drive anymore. Further lhasa, unarj and zoo are for file archivers that you normally don't see anymore.
Yes I am aware that you don't need everything in the A series. But I didn't have time to test the system to see exactly what I needed to run both Slackware and the programs I install. I excluded most of the series like X and XAP as it's obvious that I don't need KDE, X Windows etc to run Slackware without a gui. With AP, I knew that Slackware would run without AP and it was only a case of selecting whatever programs I actually wanted to use.

A, L and N however are very different series in that if you don't install certain packages, Slackware either won't run or you won't be able to to basic things like disk check and other basic command functions.

I will try this weekend to see if I can get Slackware working without most of the A series as indicated in this guide and have a look at the N series next. I think the L series I might just install everything otherwise I will spend forever troubleshooting why something doesn't work like slackpg upgrade to use a good example. I think there are too many dependencies on the L series so that the system is usable, not just boots.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
How to install minimal Slackware... gor0 Slackware - Installation 35 09-10-2014 04:17 PM
Minimal Slackware 13 Install ljones0 Slackware - Installation 2 12-02-2009 03:16 AM
Slackware Minimal Install (?) toxic.influx Slackware 6 10-13-2006 08:34 AM
Slackware Minimal Install Dr. Psy Slackware 7 05-31-2005 08:13 PM
Minimal Slackware 8.1 Install Demon Linux - Software 4 03-11-2003 11:36 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:06 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration