SlackwareThis Forum is for the discussion of Slackware Linux.
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.
the thing is... i need an OS to download the packages.
for example, lets say i download the X and KDE package groups and install them,,,, but i dont have the 'a' package ? surely KDE and X will depend on 'a' ? what happens then ? am i left with an un-usable system, forced to re-installed fedora ?
or will the install floppy have my network card drivers ? and download missing dependency's via FTP ?
Well..it would be best to download the iso's and burn them, then walk through the install. This way you wouldn't miss any packages. A full Slackware install is muchless 'bloated' then a minimal Redhat install. Once you have Slack up and running, you can always just removepkg what you don't want/need .
that's the mirror list.
Selecting package by package isn't that hard if you read their descriptions, also guessing what packages names means is not hard ie: A = apps, XA = X apss, X = X server, WM, etc D = devel, etc.
Read the guides that are sticky on this forum, also the subforum Slackware - Installation, i think that will give you some introduction to Slack.
qwigibow - you may find this page of the Slackware book to be helpful in defining the different sets of packages. Although I always do a full install, my understanding (which could be wrong) is that each series is independent, and if you choose to not install a particular series, that will not cause dependency issues elsewhere. In other words, they're modular and self-contained. The "A" series is mandatory; I believe the others are optional (although if you only installed A then your system would be very bare bones)
It isn't necessary for you to remove your existing OS in order to install Slack, but naturally you do need at least some available disk space into which it would be installed.
As for obtaining Slack 10, given its popularity and the fact that it was just released the other day, it's to be expected that there will be a huge crush of people who are all trying to get it immediately. In about a week or two hopefully the crowds will have subsided, and downloading the ISO's could be done without difficulty. My recommendation would be to download the ISO's, however, I suppose it would be possible to load the individual series that you wanted first to your hard drive, then kick off the installation process using the boot and 2 root floppies. At the point where you need to select the source media, you'd pick the hard drive option rather than the CD. I haven't tried that myself, but it is an option.
In any event, good luck with the project. I think that you will find Slack to be an excellent distro -- J.W.
There is a tool called "swaret" that resolves any dependencies on your system. it's a bit similar to apt-get. You can also use some redhat 9 and Fedora Core rpms on a Slack system by converting them to Slack packages using rpm2tgz. www.linuxpackages.net is a good site for getting Slackware packages and understanding how the Slack packaging system works.
as a fellow convert from fedora/redhat, i feel compelled to try to point you the way i went. not sure if you have gotten the iso's and installed yet, but here is a fast mirror that i found, and here is a nice link for installation instructions that are step by step with screenshots. not that the install process is really difficult, but it was nice to have along.