Is there manual how to remove unnecessary stuff from 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.
The way you continually belittle and berate people is growing old.
LuckyCyborg is not a native English speaker and to make matters worse, he lives in a culture that is famous for "sounding offensive" when translated somewhat directly into English.
But that does not mean that he is a malevolent person. On the contrary, as far as I know him, he did a lot for Slackware and Slackers without having any personal interest.
So please be kind to be easier with the labels. If you don't like the way he talks, just don't answer him.
Distribution: Slackware64 {15.0,-current}, FreeBSD, stuff on QEMU
Posts: 451
Rep:
Quote:
Originally Posted by youni
I am not figuring out how to count how heavy my slackware is?
Here's a script I worked out for that. Give it a package search term for one package, a series name for a series or "BASE" to get the total size of all installed packages from the base system.
Last edited by pghvlaans; 03-18-2023 at 09:59 PM.
Reason: clarity
I do not believe I wrote that LuckyCyborg is malevolent and even commented that he is skilled and knowledgeable. The Slackware change logs note his technical contributions. I apologize if I insinuated otherwise.
There is the old adage about only getting one chance to provide a first impression. New comers to the Slackware forum seek help rather than snarky replies. People do not like having their intelligence and motives challenged. Especially when many new comers are not native English speakers. Helping and patience creates a positive impression. Answer the person's question rather than judging or jumping a soap box.
Slackware is not exactly a favored distro these days. Positive first impressions and actually helping people might improve that status.
Treating people with dignity and respect is not a difficult skill to learn, regardless of what culture a person lives. I have been online for a very long time and am well aware of language challenges. More than a few of LuckyCyborg's posts have nothing to do with cultural differences.
Here's a script I worked out for that. Give it a package search term for one package, a series name for a series or "BASE" to get the total size of all installed packages from the base system.
it counts packages size, but there are libs and some other files.
Code:
root@slack:~# ./howbig.sh BASE
BASE SYSTEM:
9.34 GiB
root@slack:~# du -sh /usr
12G /usr
The quick and easy way is to reinstall all Slackware packages, a full install is the recommended way to install Slackware.
Quote:
Originally Posted by youni
How to check xfce4 dependencies?
As you have already noticed, Slackware packages does not contain any dependency information. Removing some packages might break things so you will need to know what you are doing when removing packages. You will need to be comfortable using tools like ldd to see which dynamic libraries binaries are using. You will also need to be comfortable reading different log files and using tools like strace.
It might also be worth noting that removing some of the original Slackware packages might not only break other original Slackware packages. When installing software from third party providers like slackbuilds.org it is assumed that you have a full install of Slackware.
You will need to consider if the disk space saved by removing packages is worth the time you will need to spend tracing down why things go wrong.
An installation with some packages removed will be a non-standard installation. It will also make it harder for you to get help at forums like this when you report something like "Application Y does not seem to work" and only get replies like "works fine here".
Many years ago, at my first installation of Slackware, during the installation process I carefully selected the packages I would need. Among those packages that I didn't select was a package named groff intended for formatting text. As I would not be working with text formatting but programming my choice was easy to not install that package. It then turned out that I got a system where I couldn't read any man-pages. Since then I have always made full Slackware installations.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,061
Rep:
It's all about your needs and preferences.
As others have pointed out already, removing stuff from a full install might lead to nasty surprises due to slackware's lack of dependency management. But there are a few huge packages (or groups of packages) that in my experience can be removed without disastrous dependency issues:
Petri Kaukasoina has already mentioned kernel-source (1.3 GB installed). Some programs are dependent on rust for compiling, but if you don't need it, rust takes up almost 1 GB. Texlive is another space consumer (>400 MB). And of course everything KDE related. There are a few packages in the xap section that can be removed without creating serious issues, e.g. Firefox, Thunderbird, Seamonkey, Gimp.
Even so, a 20 GB partition is on the small side. If you do compiling, you might sometimes need a few GB of /tmp files with the risk of running out of space.
Replacing your HDD/SSD or adding another with more space might be the best option if you really want to keep four or more OSs running.
Here's a script I worked out for that. Give it a package search term for one package, a series name for a series or "BASE" to get the total size of all installed packages from the base system.
FYI I added LC_NUMERIC=C on top of the script, to avoid warning at line 21
Mine is fat
Code:
BASE SYSTEM:
19.76 GiB
Last edited by marav; 03-19-2023 at 10:02 AM.
Reason: typo
A clean install of Slackware 15.0 doesn't take up a lot of space, probably 10-20 GB on your SSD. Select XFCE during the installation process. It is a benefit to have the KDE applications, such as K3B and okular.
Last edited by hitest; 03-19-2023 at 10:26 AM.
Reason: Typo
My Slackware-15 root partition contains 13G with 7.2G in /usr. Yes, it took me quite a bit of work to get there but, as a retired person, I have plenty of time to get things just the way I like them. Slackware-14 took up only 12G, but there are quite a lot more dependencies in -15.
I don't know though if it can be done by working down from a full install. I tried that once with Ubuntu, which does have dependency checking, and it was a disaster. I found it easier to work upwards from zero with -14.2, then copied that setup to -15.0 and added whatever was needed to make everything work.
Install a/ ap/ d/ l/ n/ x/ xap/ xfce/ subtract out seamonkey and thunderbird, if they are useless to you (maybe you only use webmail client for email and are happy with it). Add k/ if you need to compile drivers that require it (famously and commonly nvidia, but there are others) or want to tweak your kernel config. Add f/ if you will be offline and want extra help pages offline. Mostly this should work. Notably you will have no office suite, but could easily add libreoffice from alienbob to get that back. There are many other nice to have apps in kde, but many people use none of them.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.