ssmtp is not maintained.

msmtp would be a better candidate.

An option in the installer to only install a minimal set of packages.

In my opinion pkgtools are great! And please no GUI config tools that no one needs!

How much space does a full install take up? I've never bothered to check.

About 7.2 GB, I think???

This. I always go straight for openjdk over the main one.

Installing Series A and L (and maybe N) should do the trick. Slackware up to 11.0 provided Zipslack, an installation that fits into 100 MB.

Yeah, about 8G, but... you don't have a lot of room to install any additional software you might need and, over time, you'll hit the limit switches. That's a full install. I've got one client machine that's 10G root and it's getting real close to full (about 1.5G left in a 10G root). Now, when you really think about it 1.5G is a heckuva lot of space if you don't go nuts with SlackBuilds.org, but it's pretty tight over time and use.

My running systems, with 15G roots, are at about 60% with a little over 5G left and I've been migrating them to 20G root just to have elbow room. Running systems are kind of like a fart in an elevator, rapidly expanding to fill all available space. In these days of terabyte disk drives, who really gives a hoot about 10G or so here and there? Just remember, off you can take, on you can't put. I have separate partitions for /opt, /usr/local, /var/lib/mysql and other space eaters, the root is only the distribution software, nothing additional if I can help it (SlackBuilds.org insists on installing in the root tree instead of /usr/local or /opt, drives me nuts).

If you only do a full install of Slackware, you can get away with 10G -- just don't install much of anything else.

Whatever I feel like installing. I prefer the tabula rasa gooey. Why should I bother the systems developers with adding stuff I don't want or need. Some of the student employees in the computer science program use TWM as their X window manager. Problem with widget dependencies is widget toolkits get deprecated, fall by the wayside when the developer graduates or moves to another company and nobody is around to maintain it. The freeway is littered with such toolkits. Those using them just accept that everything works as advertised, and consider them static, won't change, which itself is a good thing if there are no security flaws, off-by-one errors (ones-complement vs twos complement arithmetic in loop counters), remote possibility of writing past the end of an allocated structure, and all. I've read graduate theses where an unanticipated congruence of unlikely events leads to catastrophic failure. In the eighties on PLATO, whenever we thought a lesson was ready for prime time, we'd get all of the authors we could muster to try and break it. Students could reply with an essay that could get graded correct if the parser found key words in specific sequences. But I digress. What do I want to see on the slackware desktop in the future? Nothing. If I want more than a root console, I'll install something minimal, maybe some xfce utilities, libreoffice, geany, gvim, emacs, tex,... There will never be a consensus in such groupware. Let the end user install what they want. Chances are they'll install only the tools they need to get the job done, nothing more.

I don't know if this is relevant, but the Dalai Lama said there should be six million different religions because each person experiences things differently. Walk into a grocery store and observe the fruit and vegetable displays. Not likely to find two people that choose identical combinations. Some people love limburger cheese; me, I can't stay in the same room with someone eating it. Point is, don't try to outguess end users. Provide a basic system and utilities, then leave the rest to the end user. That's why I love SlackBuilds. One person uses their computer as an audio production workstation; another for entertainment; another as a video production workstation; graphics design; producing peer-reviewed journal articles (I know a scientist who uses Slackware with only bash, LaTEX and emacs with supporting libraries, who composes articles in ascii, goes back and adds TEX commands, sends the result on a 5.25" floppy to the front office where the article gets uploaded and sent to a journal, since TEX produces camera-ready pages.)

1 members found this post helpful.

Kate Beckinsale joining me for dinner at a favorite eatery would be better.
In all seriousness though I am happy with Slackware as it is. GUI tools? No thank you.

Yeah, only a few years ago 6G was sufficient for my root partitions. Now I am fixed at 20G.

Just remember: when an elevator is full of people and a person farts, only one person knows for sure who farted. When the elevator has two people and one farts, everybody knows who farted.

I've only ever had a simple / and swap. And now I've lost interest in distrohopping/dual-booting, the whole hard drive is devoted to Slackware. Hard drives, rather, since that applies to my desktop, laptop, and netbook.

I do like to maintain a separate /home partition. I am dual booting less and less. I have one Slackware64/OpenBSD dual boot that I maintain.

Even while I am not dual booting I keep /home on a different partition

Well, there are alot of things in A, L and N, that I do not need. I know how to make a minimal system (using Slackware since version 7), it just is very time consuming! A full install is nice if you install Slackware the first time and want to play around a little bit. But if I want to use it as my main system, I hate having software installed that I don't need.

The problem, Roman, is that everyone has different needs, thus his or her own definition of a minimum system. Of course if you want to "clone" your own system you can use customized tagfiles.