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.
Depends on how much you install and how much RAM you have and what your usage is going to be. Maybe 3 gigs would do for root, depending. /home is up to you - very little room needed for config files and however much space you personally want. Rule of thumb for swap is twice your physical RAM but it's a dumb rule these days. With only 7.5 gigs, might just make 256MB but it would vary.
-- Whoops. Good link. I strongly recommend the separate /home, though - that link just makes it sound like a 'sorta' good idea. And I did the symlink thing to home for awhile but it felt funny so I made them separate again for 9.1.
A seperate /home partition is great . Your mail and settings and much more is stored in your hpme dir and will be restored if you decide to get another version of Slack.
My Slack 9.1 install with some sources is about 3.5 gigabytes. I would suggest a 4 gigabytes filesystem for / (root) if you are planning to install KDE or Gnome and X. If you're planning a machine without X you could save 1 gigabyte. The rest is for /home and swap ( 2 times amount of internal memory maximum 512 MB swap) .
I have another question which is very important to me.
I have 6 partitions on my hard disk now. Let's label them: C, D, E, F, G, H.
C, D, E, F reserved for Windows XP for some reason, I have to keep it. G has RedHat 9 installed. I don't want to use it any more. However, I won't remove it untill I set up my Slackware.
Now I want to install Slackware on H partition. When I install Slackware, how can I know I install it exactly on this H partition. That is I may partition this H partition to several partition for swap, root, boot, home etc. I don't want ot make this mistake such as install Slackware to D or E partition, that will lead to lose important data.
Slack will ask you where you want stuff*. If C is hda1, etc., then H would hda7 (assuming D2/E3/logical 4/F5/G6/H7) and any slicing you did would just extend it from there - hda8, etc. Is RH on hda6? Then Slack would be hda7+. Anyway - the output of fdisk -l (particularly in conjunction with /etc/fstab) should give you a good idea of what's going on.
*by that, I mean the installer will present you with a menu listing of partitions - it IDs Windows partitions and swap spaces and pretty much ignores Windows and asks if you'd like to initialize the swap - and asks where you'd like to put root and then asks you define any further partitions and mountpoints for them. So, basically, if you know the layout of your disk, you can't go wrong - Slack won't do anything without your say so.
-- Yet another edit. I've never had anything go wrong like that but, still, it's a very good idea to back up your data before something like this. That way it's impossible to 'lose' data no matter what you do - at worst you temporarily misplace it.
I'm not an expert, but from what I understand you should set the swap depending on the load you expect. For example, I have 768 MB ram on my system and a 500 MB swap. Now if you were running a server with a heavy load you may want to follow the double your RAM rule. For most desktop users though, 500 MB is enough. Generally the only time you use the swap at all is if you have enough stuff running where you use all of your physical ram. Personally, I've never had linux dip into my swap with my current system configuration.