minimal slackware install desktop

tdsf · 02-14-2017, 10:35 PM

Hello, buddies!

I want install a minimal Slackware to a desktop.

I have a dvd with the full instalation but i want to try a minimal install.

Because.. see.. Im just using Abiword and Gnumeric and Firefox and dvd... once in a while i'll need to compile Slackbuilds.

So, maybe theres a lot of things that i dont use in my instalation.

I dont want to be a developer, i dont want make a server. Im just a regular guy that uses a laptop for normal routines.

I thinking: the A, AP, K, L, N, X and XAP packages maybe are just enought to me. But i have to compile the SlackBuilds. What program in the D series its required to compile the SlackBuilds? Can i just install the respective program that compile the SlackBuilds and do not install the rest of the things?

What do you suggests?

Thank you so much for your time!!!!!

orbea · 02-14-2017, 10:42 PM

If you really want to you can safely skip kde/, kdei and xfce/. You should probably not skip anything else though and note that this means no you will not be able to compile anything that requires kde or xfce which some slackbuilds at SBo will require.

You should certainly not skip d/, it includes gcc, llvm and other important packages required for compiling software.

Slackware is not really the right distro for minimal installs unless you really know what you are doing, additionally there is 0 reason to do so unless you want to learn how it all works.

Didier Spaier · 02-15-2017, 01:13 AM

Welcome tdsf.

This question has already received countless answers over the years, so please use the search feature of this forum (minimal install could be a good search argument) to find them. http://docs.slackware.com/ is also a good source of information.

PS maybe Salix, based on Slackware but intended for desktop users will better fit your needs. It can make and install packages from SlackBuilds and also provides gnumeric and abiword packages. In simple cases its spi command can handle both SlackBuilds and pre-compiled packages.

SCerovec · 02-15-2017, 02:38 PM

AFAIK: TL;DR
minimal install able to continue later from LAN/internet:

series: a/ap/n/l

therefrom one is in position to login as root and run slackpkg to install further series or packages.

NOTE: no official dependencies resolution is provided for the "vanilla" Slackware - OEM recommends full install only,

hitest · 02-17-2017, 09:26 AM

Quote:

Originally Posted by SCerovec

NOTE: no official dependencies resolution is provided for the "vanilla" Slackware - OEM recommends full install only,

Yes. A full install of Slackware works out of the box with all dependencies met. If you pare down your install and something doesn't work it is expected that you will trouble shoot your own set-up. We prefer to offer technical support for full installations of Slackware.

onebuck · 02-17-2017, 09:44 AM

Hi,

Welcome to LQ & Slackware!

Quote:

Originally Posted by tdsf

Hello, buddies!

I want install a minimal Slackware to a desktop.

I have a dvd with the full instalation but i want to try a minimal install.

Because.. see.. Im just using Abiword and Gnumeric and Firefox and dvd... once in a while i'll need to compile Slackbuilds.

So, maybe theres a lot of things that i dont use in my instalation.

I dont want to be a developer, i dont want make a server. Im just a regular guy that uses a laptop for normal routines.

I thinking: the A, AP, K, L, N, X and XAP packages maybe are just enought to me. But i have to compile the SlackBuilds. What program in the D series its required to compile the SlackBuilds? Can i just install the respective program that compile the SlackBuilds and do not install the rest of the things?

What do you suggests?

Thank you so much for your time!!!!!

As other members have stated that a full install is your best bet not to have future issues.

If you really wish to do a minimum install then these links may be of some help;

Quote:

-- Minimal System Install:
Minimal System <- SlackWiki method as to what packages you should install to have a base system.
HOWTO make your own custom Slackware install disk <- Samac's LQ technique, some cautions but good. 'Here is a method of cutting your Slackware to fit you by using Alien_Bob's mirror-slackware-current.sh script.'
mini ISO image <- 'CDROM to boot, and install packages from an NFS server or local hard disk'

Any issue with your minimum install must be handled by you. Most experienced Slackware users will not advise on a personal minimum install. I for one would not since it will be hard to diagnose the system. Disk space is cheap per GB so no real reason not to do a full install to get a working system.

You could look at a Live Slackware to fill your system needs;

Quote:

Slackware64®_Live

Updated ISOs for Slackware Live Edition <- 'New ISO images for Slackware Live Edition based on the liveslak 1.0.1 scripts and using Slackware-current dated “Fri May 27 23:08:17 UTC 2016”. This version of Slackware-current has several significant changes and fixes, compared to the snapshot I used for the liveslak-1.0.0 based ISO images.' + 'Be sure to read Eric's blog to get information related to new ISO available and blog entry updates that are very helpful' + Latest SlackwareLive ISO
Slackware Live Edition Beta Blog <- 'Please read the Alien Blog for all information for Slackware Live' + 'By releasing a first public Beta of the Slackware Live Edition.' + ' Slackware Live Edition is a version of Slackware-current (64-bit only for now) that can be run from a DVD or a USB stick. It is an ISO image meant to be a showcase of what Slackware is about. You get the default install, no customization, but with all the power.' + 'Get the ISO here; http://bear.alienbase.nl/mirrors/slackware-live/ or rsync://bear.alienbase.nl/mirrors/slackware-live/ + 'The “rsync” command has a “–bwlimit” parameter which lets you limit the download bandwidth.'
Slackware Live Edition Beta2 Blog <- 'Please read the Alien Blog for all information for Slackware Live' + 'What is Slackware Live Edition? If you’re new here: Slackware Live Edition is a “live OS” meaning it does not have to be installed to a harddrive and can run straight off a CDROM or DVD medium, or off a USB stick. Slackware Live Edition is meant to showcase the development of Slackware. Therefore it will boot slackware-current and no other OS. + 'ISO Primary location: http://bear.alienbase.nl/mirrors/slackware-live/ (rsync URI: rsync://bear.alienbase.nl/mirrors/slackware-live/)'
Slackware Live Documentation
Slackware Live Edition Documentation <- 'is a valued site for Liveslak information/documentation'

Hope this helps.
Have fun & enjoy!

Alien Bob · 02-17-2017, 10:22 AM

Gary, please change "taper" to "bear" in your documentation.

kikinovak · 02-17-2017, 01:34 PM

I wrote that "Minimal System" article on Slackwiki back in 2007. It is completely outdated information. Please don't use it.

SCerovec · 02-18-2017, 04:49 PM

@kikinovak,
You wrote an excellent, but quite specific article - it was bound to be obsoleted by the intention.
As Slackware evolved, some packages changed...

My approach, had a more generic goal:

Quote:

Geta system able to boot itself and easy pick up install further packages

There are quite few packages needed for that (the install initrd is one example), but I wanted an obsoleting-proof recipe

so I repeat (with hints this time)

series [hint]
a [absolute basic system]
ap [holds slackpkg et co.]
n [needed for any ssh and networking]
l [some libs might be missing for ap series and some ncurses programs]

therefrom, one can ssh or login and continue series installation, or what ever:

Code:

# slackpkg install d

For instance.

chris.willing · 02-18-2017, 05:57 PM

Another view of packages needed for a minimal system is in /usr/share/lxc/templates/lxc-slackware - packages required for a running container are listed at around line 224. It should be an OK basis for a normal (non container) system too. The list includes slackpkg so that, following the minimal install, other packages for particular requirements (e.g. desktop) can be easily added.

chris

onebuck · 02-19-2017, 06:11 AM

Hi,

Quote:

Originally Posted by Alien Bob

Gary, please change "taper" to "bear" in your documentation.

Done! Sorry for the oversight.

SCerovec · 02-19-2017, 07:40 AM

Quote:

Originally Posted by chris.willing

Another view of packages needed for a minimal system is in /usr/share/lxc/templates/lxc-slackware - packages required for a running container are listed at around line 224. It should be an OK basis for a normal (non container) system too. The list includes slackpkg so that, following the minimal install, other packages for particular requirements (e.g. desktop) can be easily added.

chris

on 14.2 that list reads:

Code:

# thanks to Vincent Batts for this list of packages
# (that I modified a little :P)
# http://connie.slackware.com/~vbatts/minimal/
cat <<EOF > $CONF/templates/minimal-lxc.template
aaa_base
aaa_elflibs
aaa_terminfo
bash
bin
bzip2
coreutils
dcron
dhcpcd
dialog
diffutils
e2fsprogs
elvis
etc
eudev
findutils
gawk
glibc-solibs
gnupg
grep
gzip
iputils
logrotate
mpfr
net-tools
network-scripts
ncurses
openssh
openssl-solibs
pkgtools
procps-ng
sed
shadow
sharutils
slackpkg
sysklogd
sysvinit
sysvinit-functions
sysvinit-scripts
tar
util-linux
wget
which
xz
EOF

just for reference.

Didier Spaier · 02-21-2017, 08:24 AM

Quote:

Originally Posted by chris.willing

Another view of packages needed for a minimal system is in /usr/share/lxc/templates/lxc-slackware - packages required for a running container are listed at around line 224. It should be an OK basis for a normal (non container) system too. The list includes slackpkg so that, following the minimal install, other packages for particular requirements (e.g. desktop) can be easily added.

I have played with that, thanks Chris!

But maybe you could add kmod, to make eudev happy

Other than that, still trying to find a way to simplify setting up unprivileged containers, albeit slowly because I do not have Internet in my country house now.

montagdude · 02-21-2017, 08:41 AM

If you really want to trim down your Slackware installation, one of the best tools I've found is sbbdep. It can be a long and tedious process depending on how much you want to remove (with few real benefits, I might add), but it does a good job. One problem, though, is that it can't detect interpreted language runtime dependencies -- at least as far as I know -- because these are only referenced in the source code itself. So you may encounter, for example, "ImportError"s in Python programs.

Personally, I don't care that much about having a lot of things installed that I don't need, but I do prefer not to have the application menu cluttered with such things. I wrote a script that scans the .desktop files on your system and makes a list of the packages that they are contained in. You can save this to a file, remove anything from the list that you wish to keep, and then remove the rest easily by running removepkg in a loop through the packages listed in the file. If anyone is interested in that script, I can post it later tonight. (Warning: requires the user to know what they're doing so as not to remove anything important!)

chris.willing · 02-21-2017, 03:44 PM

Quote:

Originally Posted by Didier Spaier

But maybe you could add kmod, to make eudev happy

Yes, that would be important for a bare metal installation (what this thread is about), whereas a container installation uses the kernel/modules of the host machine (so kmod not needed).

chris