Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Nope. This is a generic warning. If you install a boot loader and something goes wrong, you may not be able to boot other systems already installed on the hard disk (if any). I'd not be worried so much, anyway.
So why not do a full install if you've got 500 GB free?
Having a large space doesn't mean that I should fill it up by the things which I don't want. The only reason I wanted to use Arch instead of Slack was that everything which you wanted, had to configured in the system yourself, so there was no question of having the unwanted things.
You could choose the selective option during installation. Choose each package you want. http://www.slackbook.org/html/instal...p.html#AEN1062
I always do a full install, because though I might not be interested in using or learning about some particular bit of software (say, Apache, or just about every major programming language) now, I may be in the not too distant future. A full installation of Slack gives you a versatile system, out of the box, no need for apt-getting or yumming masses of packages.
and messed up every thing because the packages are not grouped, individual libraries and config files have to be selected which can be done only if one knows what he is doing so the links colocix has provided I hope will solve my problems
Originally Posted by SilverBack
Another way to do this would be to install all and then gradually uninstall that you did not want.
Thats what I used to do in OpenSuse all this while and many times it resulted in broken packages and sometimes I even had to do system reinstall!
It was for such reasons that I decided to follow Patrick's advice and install everything (except KDE). I understand and respect your desire to have a minimal system with only the packages you need but balancing the costs (most of which you are discovering first hand!) against the actual benefits, Patrick's advice made sense. The only thing I don't like now is the bandwidth wasted upgrading packages I don't use.
Even if it was easy to install only the required packages, I found that unnecessary time was wasted when I wanted to install another package and did not have the prerequisites.
Anisha has yet not taken a print out of the minimal packages required to be installed (the paper needs to be kept in front of the eyes during installation) nor she has completely understood Slax-Dude's howto