Hi there, well after i "SOLVE" the question on this post -> https://www.linuxquestions.org/quest...ml#post6459595

For had a minimal installation of Slackware working with Networking.

I am thinking, on make tutorials for make some Servers like :

* DNS ( Named or DNSMasq ) [Internal / External]
* PROXY ( Squid )
* EMAIL ( Zimbra )
* NTP
* DHCP
* OCS Inventory
* VOIp ( Asterisk or another )

each individual servers, i prefer separated servers, because i agree with "make just one thing but make it fine"

Well, the idea of this post i make tutorials for use a minimal working with networking Slackware installation. because on internet i can't find post like that, are ever "Ubuntu, Debian, Fedora, CentOS" and basically any distro using "SystemD"

Hi Inukaze,

Such an effort should be welcomed. Because English does not seem to be your native language, some native English speakers might help to review the tutorials.

Likely somebody will suggest posting the tutorials to the Slackware Documentation Project.

Perhaps the tutorials should start with some kind of zealous minimum install. For example, here.

The different server types listed need networking packages. That does not mean every package in the /n series needs to be installed, but some /n packages are needed. As Pat has shared through the years, the package series naming does not imply a strict dependency or hierarchy for installing packages. The package series names originate from the floppy disk days, with some basic idea that /n packages are networking related, /d packages are development related, etc.

The "fun" part is debating which packages should be installed to support each server type. Perhaps the tutorials might list minimum packages for each server type and then list optional "nice to have" packages.

Perhaps worth mentioning is scripting. Installing packages for scripting support (perl, python, php, etc.) is appealing because scripting usually makes administration easier. Admins tend to like scheduling tools such as at and cron. Such packages are not needed to satisfy a strict definition of "minimal," but makes life more palatable. And most admins likely will scream if SSH is not installed.

The idea of a minimal Slackware installation has been discussed many times in this forum and elsewhere. As discussed in your previous thread, there are many package dependencies because Slackware is designed from the bottom up to be a full operating system -- whether the user is a basic web surfer, developer, network admin, whatever. (One ring to bring them all and in the darkness bind them?) One way or another there will be some broken dependencies unless packages are recompiled. I share this not to discourage but only to offer the usual caveat emptor warning.

If you feel energetic then perhaps mention broken dependencies introduced by limited package selections.

Outside short term testing environments such as virtual machines (VMs), I do not recall ever running a full Slackware environment. I started hacking Slackware from the very first install I performed, including rc.d scripts. Even now my sole Slackware Current VM is not a full system nor are my daily 15.0 systems. I have some specialty Slackware VMs that are not even close to being full installs. In the specialty VMs there are some broken dependencies but they do not affect the VMs. For example, those systems are intended to be headless. I have no need for any X packages and some binaries such as /usr/bin/dbus-launch or /usr/bin/grub-mkfont show missing dependencies, but I do not need or use those binaries within the VMs.

The popular advice to perform a full install probably is sane for new Slackware users, if for no other reason than to reduce forum chatter and support. Us old farts who have been using computers for several decades tend to shrug off such advice because some of us old farts have been installing computer operating systems since the early MS-DOS days, long before preinstalled systems became the norm. As others continually mention, Slackware is designed as a full operating system but unlike other distros seems more flexible toward hacking and customizing. Also pleasing is Pat seems to have a honey badger attitude about what users might want to do with their computers -- he provides a full operating system and users are free to hack and tinker as they please.

Well written tutorials are always helpful for those who want to explore. Sounds as though you have sufficient computer experience to hack Slackware as you wish and need.

I hope this helps. Have fun!

2 members found this post helpful.

Hi there, thanks for the warning, and yes, the english is not my native language, i am from venezuela, my native language is spanish.
Well on my "Minimal Selection" i test each package one by one to see which package can solve some broken dependency, that take me too much time, because i am start to do that on Slackware(64) 14.2, but the lastest test i do on Slackware(64) 15.0 and for the core + base system works exactly equal. when you start to put things of X / X.org some deps are diferents.

I don't have trouble with test each package one by one to determinate the minimal packages for get a real web server working like expected. i just really don't want extend the absurd dependency on systemd. On my job, every day we have electrical fails with lights, and all server is very common shutdown and when try to boot again, just hang on a absurd message of systemd like "The Job [1/???] cannot be unfinished" or "Press Control+D to boot normally" but when you try, the unique thing you got is a restart.

Too many times, the message never specify something like "Fileystem not clean" or "Incoherent Filesystem please check with fsck" and this is very common on distro with systemd if just 1 bit is wrong. on Slackware, you need a real incoherent filesystem to get a message like that, on the lastest 8 years using Slackware(64) 14.2 on Domestic usage, i have see that message just 5 times, caused by abructal cut of electricity on my building, the rest is one bit is wrong slackware knows that and just continue normally

Another thing i really hate of systemd, is if all mountable extra devices on the /etc/fstab file are not present, the distro never boot, slackware if not found a extra device, just ignore and continue the loading normally

and for things like that i really want to make servers using Slackware.