Question about Slackware flexibility
 

I'm more of a linux newbie than anything, but I have been playing with it off and on for years. I've used Slackware before, but it's been awhile Ver 10.1 was the latest at the time I think. I've also played with some other distro's, mainly Gentoo which *seems* more flexible. But I would like to stick with go with Slackware. Basically, I want to be able to install everything from what amounts to just a small kernel, bash and a few network apps; all the way to a full blown server with a netbook, a laptop and desktop in between. I know I can do a server with Slack, I also know I can do a desktop and laptop. But when it comes to netbook and smaller I'm a little concerned that I won't be able to get a "small" enough install.

Is there a way to trim it down some so that I don't need a big huge kernel and a lot of storage space? I would basically like to get a very, very basic install. Kernel, Bash, Slackware specific stuff add maybe 5 or 10 network apps and that is it.

Yes you can do small installs with Slackware.
Choose only A, AP, L & N from the package series and you'll have a working system - without X, without kernel sources, without compilers etc.
You can even trim it down more, leaving out individual packages, but that is called Expert mode for a reason ;)

Can I just add kernel sources and compilers to that list? I would check it out myself, but my internet connection is only about 7K a second and frequently cuts out. So it takes a LONG time to download an ISO. It took me 36 hours to get the Vector Linux light ISO, and it's only about 300 megs. So it is taking some time.

Sure you can. For me a minimal install includes the kernel sources (K) and development (D) series as well :)

actually browsing the package thing on the slackware site. I remembered the package system after you mentioned it. Looking through it there was a good bit of stuff I wouldn't need for some applications. How hard is it to cleanly remove some packages after it's installed. I really don't want to try an expert install. That is a lot of clicking.

You'll find a list of all installed packages in /var/log/packages.

Removing a single package is as simple as typing:
If something stops working, you can download the single package and do an 'installpkg'.

Slackware really is flexible! :cool:

Thanks! Here's an idea, how about I RTFM about Slacks package system LOL. The only package system I really know anything about is Portage. Hopefully there isn't much of a learning curve.

P.S. I really like the portage/ports package set up. FreeBSD and Gentoo are really nice IMO. Gentoo just takes forever and I know FreeBSD doesn't support all my hardware.

No problem, we're here to help.
After understanding the basics of the package tools of Slackware, take a look at SlackPkg.

In the stable version (12.1) it's in the /extra directory.
Pat recently decided to include it in the base system of Slackware starting with the next version (it already is in -current).

Warning / Disclaimer: Slackware -current is for testing purposes only. Do not install on production machines / equipment with important information etc. Things are bound to stop working. It is for people who want to help testing new versions and for the adventurous ;)

In addition to installpkg, upgradepkg, and removepkg you can install/remove packages by using pkgtool.

# pkgtool

http://www.slackbook.org/html/packag...utilities.html

If you create your own tagfiles for installation you can easily trim it down, but be careful not to remove things from the a, ap and l folders unless you know what you are doing. Else chances are high that you end up with a mess. This way is similar to the expert install, but you can take more time to consider what to remove and include - and you can use the tag files over and over again with each Slackware install since the tag files don't include version numbers but only package names (only minor changes are needed if a package is thrown out or added by Patrick Volkerding)

From the same source hitest quoted: http://www.slackbook.org/html/packag...-tagfiles.html