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.
Well, grep is used on the init and network scripts, so I cant do with out it.
bzip2 and diffutils are needed for slackpkg.
findutils I'm unsure... haven't found any major scripts with "find" or "xargs" in them.
The rest of them I'll remove (one by one) and see if it brakes stuff
If kernel-modules is not needed it would be great since it's a 15Mb (compressed!) package!
I'll keep you guys posted
Thanks for the tips
Click here to see the post LQ members have rated as the most helpful post in this thread.
find is optional during startup -if present, it is used when looking for updated kernel modules. 155MB is still about 100MB too much -but your filesystem block size may be affecting the size too.
Good list, the differences between 12.2 and 13.0 are quite small, my list allows you to compile and use sbopkg, and yours allows you only to use slackware packages, but that is cool because you would then be able to download the extra packages you need.
You have added four packages, iputils, openssh, sysvinit-functions and xz. I can see the definite need for xv, the probable need for sysvinit-functions, but you might be able to remove the other two, though this is just a guess as I haven't tried it.
You should be able to remove slackpkg as that only allows you to update your system and you can to that manually with wget.
I would add a boot loader or you will not be able to access your system on a fresh install, lilo ?
You have added four packages, iputils, openssh, sysvinit-functions and xz. I can see the definite need for xv, the probable need for sysvinit-functions, but you might be able to remove the other two, though this is just a guess as I haven't tried it.
I need iputils to have network (tools like ifconfig are in that package).
I also need to login remotely to add some packages or change some .conf files if needed, so openssh must be there as well.
Quote:
Originally Posted by samac
You should be able to remove slackpkg as that only allows you to update your system and you can to that manually with wget.
Indeed I can, but since it's only 180Kb (uncompressed) and I love the simplicity of "slackpkg update" + "slackpkg install d" to get me a compiling machine like yours, I'll let it stay
I'll use wget for non-standard stuff like sbopkg
Quote:
Originally Posted by samac
I would add a boot loader or you will not be able to access your system on a fresh install, lilo ?
samac
I usually install the bootloader (I prefer grub) during the installation process and not as a package on the newly created machine.
I mean: if I install 10 slackware systems into the same HD, they don't need all to have grub installed.
Like the slackware installer, I'll leave the bootloader as optional, as it may not be desirable to install it.
My goal is to build a sort of slackware-template that once installed could be easily expanded in to a full slackware installation or a custom slackware installation like a dedicated mysql server or a web server.
Whatever the final system may become, it would start with the same template.
gnashley: in fear of being called a noob, I ask. What do I do / where do I read to find out what that does at startup? or what happens
I was asking myself this same question a few years ago and came across this page : Slackware : The boot process.. Not sure how up to date this will be now (Version 10 is mentioned, but I still look at it now and again to remind myself of what is going on with my various boxes (all now on Slack 12.1 or 12.2) at boot time. I find it nice and short and to the point.
I get chroot cannot execute /usr/bin/passwd: no such file or directory. what packages includes that? I have etc,etc,sed,shadow
I cant figure out what package I forget to install.
This is under the install when I'm prompted to setup root password
Remove aaa_elflibs to save a little space. It will also make your list more accurate -you may be running some programs which depend on libs which are included in aaa_elflibs but don't have the regular package for them installed. What I mean is this: aaa_elflibs contains duplicate single libraries which are each contained in some other package. if you really want to know which packages are essential for your purposes, removing aaa_elflibs will help you find that out, and it will eliminate other libs in there which you do not need.
I have a little tools here: http://distro.ibiblio.org/pub/linux/...3-noarch-1.tgz
which will save you some space by removing unwanted language files. Even if you have not installed glibc-i18n, most packages install their own language files.
Another trick you can use, which Patrick used to do when building the zipslack distro, is to remove all header files under /usr/include and also all static libraries under /usr/lib
Of course, this removes files while not removing them from the package database, so later removing/upgrading the packages will show error messages.
You'll also find there is lots of 'cruft' under /usr/doc...
The localepurge script above will remove several hundred MBs from a full install!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.