Introducing StripSlack, a minimal configuration of Slackware
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Introducing StripSlack, a minimal configuration of Slackware
Hi,
I've recently built a LiveCD based on Slackware, which actually works quite well, except for the fact that there is way too much bloat included. So I started to give a sane minimal configuration for Slackware some thought.
Vincent Batts has a page about a minimal Slackware configuration, and the french Slackware users site sports an outdated article on the subject. I fired up a VM, bookmarked the LFS and BLFS documentation and then spent a few rainy afternoons reading and experimenting.
I'd say this is a usable beta. Everything is working fine, there don't seem to be any showstoppers, though there are still some rough edges and some missing things.
In the past, the need for a "basic" Slackware installation has repeatedly been voiced in this forum. I hope my little project can answer these requests.
Test it and feel free to report your findings and suggestions, so we can work on making it perfect.
Just one comment: it might be worth making clearer what exactly is included in your stripslack as I don't think you include a desktop seeing your tagfiles and this might not be everyones understanding of a minimal enterprise desktop, so better to be clearer about this on your webpage. In particular as determining which packages need to be installed to get a minimal XFCE + some specific applications isn't obvious.
I for example do this by using Salix's dependency repository with a bash-script to generate a specific tagfile for a XFCE desktop with only the applications I use, which works well enough for me.
Just one comment: it might be worth making clearer what exactly is included in your stripslack as I don't think you include a desktop seeing your tagfiles and this might not be everyones understanding of a minimal enterprise desktop, so better to be clearer about this on your webpage. In particular as determining which packages need to be installed to get a minimal XFCE + some specific applications isn't obvious.
At the moment this is only useful for someone who wants a minimal console-system. Desktop users definitely don't want to use this.
That being said, I have an idea that's slowly growing at the back of my head. Something similar to 'yum groupinstall <package_group>' on RHEL/CentOS or 'tasksel --install <package_group>' on Debian, only for Slackware. This will take some time, though, since my skills to do that aren't sufficient for the moment. But I'm working on it.
Just one comment: it might be worth making clearer what exactly is included in your stripslack as I don't think you include a desktop seeing your tagfiles and this might not be everyones understanding of a minimal enterprise desktop, so better to be clearer about this on your webpage.
I didn't understand at first that you were referring to the h1 page title. I just changed it to avoid any further confusion.
That being said, I have an idea that's slowly growing at the back of my head. Something similar to 'yum groupinstall <package_group>' on RHEL/CentOS or 'tasksel --install <package_group>' on Debian, only for Slackware. This will take some time, though, since my skills to do that aren't sufficient for the moment. But I'm working on it.
Not sure what you aiming for, but generating the appropriate packages to install for a given minimal desktop system is not difficult to do using the salix dependency tree.
What I typically do is start with a similar file as you have as your stripslack.sh then add the package-names of things I know I want to add and run this through a simple script that fills in the missing packages using Salix's hard work. This gives me a complete list of packages to install on that system. With that list I can generate the tagfile using gust.
Initially I thought it would be hard to add packages, but in reality I find slackpkg sufficient to deal with the things I need to add. As a result I never extended the quick and dirty script for step 1 although in reality it would be no more than taking a diff between the list of installed and to_install packages.
That's why I wrote a detailed document about the subject and linked to it in my initial post. Please take at least one minute to read it before starting to speculate.
Minimal system
--------------
When two users are talking about a "minimal system", chances are they don't
refer to the same thing. Embedded Linux systems will consist in barely more
than a kernel, a C library, a shell and a very reduced set of tools. On the
other side of the scale, installing the "Base System" package group on a
RHEL/CentOS system will leave you with several hundred packages and a complete
collection of shells and text editors as well as a full set of administration
tools.
A task-oriented approach will help us in finding the right balance between
these two extremes. Here's a few things we want to be able to do with our
minimal installation of Slackware:
* Boot in multi-user console mode
* Use the Bash shell
* Edit text files using Vim
* Display man and info pages
* Manage disks and filesystems
* Build an initrd
* Manage users
* Connect to a network
* Install and upgrade packages through a network
* Work remotely using SSH
* Work with the Git revision control system
* Compile applications
* Browse the Web using a text-mode browser
StripSlack simply aims to provide all these functionalities while leaving out
all the stuff that's not strictly needed.
Got it running OK in VirtualBox. Thanks, Niki.
It's been on my ToDo list for ages: setting up a minimal Slack in VBox, but I'm afflicted with chronic laziness.
BTW you don't need any X libs. Groff is used only by man and it works fine w/o X. And I am not sure why you need the netkit stuff. You have to add portmap and eventually inetd to make use of it. Telnet and tftp-hpa make me wonder too.
That's why I wrote a detailed document about the subject and linked to it in my initial post. Please take at least one minute to read it before starting to speculate.
For clarity: I referred to the "idea" that was "growing" in your head, not what you now posted, hence the quote above. Bottomline, please be careful in misreading replies...
Just for clarity: what you currently have is in itself very useful for many already, which is why I thanked you for this effort!
For clarity: I referred to the "idea" that was "growing" in your head, not what you now posted, hence the quote above. Bottomline, please be careful in misreading replies...
Just for clarity: what you currently have is in itself very useful for many already, which is why I thanked you for this effort!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.