Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
i have a linux system here (arch linux) which I'm happy with. it has one harddisk of 120gb. I recently added two new 120gb drives thinking I would like to set up a mirror RAID on these two identical disks, make new partitions (/var, /tmp, /home, /boot, / and swap) and move all my files currently on the original disk to the new RAID, and then make the RAID bootable and remove the original disk.
the original disk is not the same model as the newer disks, which is why I would like to remove it and use it for some other purpose.
can anyone tell me what partitions to make and how big they should be? should the swap partition also be in the mirror raid? it seems weird to me to mirror the swap partition ...
after making the partitions I would like to move all the files over to the new RAID. how can I do this safely without forgetting anything in the process?
and how do I make my RAID bootable and succesfully reboot?
the machine is going to be a small business mail(imap) / web / groupware server (mysql, php etc), up to 10 users
I would partition like so:
The rest Home (I'm assuming your users get home directories and accounts on the server)
It doesn't really matter if the swap is on the RAID or not.. RAID doesn't just keep working when a whole drive breaks, it fixes errors when one disk gets bad sectors, etc. Because of this, it might make your system ever so slightly more reliable to have the swap on the RAID array.
I would boot off a bootable linux cd (gentoo livecd, knoppix, etc) to move the files. cp -pR will preserve file ownership information and copy recursively in a smart way. I like to copy one partition (mount point / filesystem, really) at a time, so cp -Rpx is good for me. Just read the manpage for cp and it will tell you everything you need to know.
Once you have your files all coppied over the way you want them onto the destination drive, chroot to it ("man chroot" for more info).
From there you can update your bootloader config file (/etc/lilo.conf or /boot/grub/grub.conf, etc) and install it (grub, lilo).
The man pages should tell you all you need to know for reinstalling the bootloader (man lilo, man lilo.conf, man grub, etc)
Yeah, -a is short for -dpPR. I think that may be better, though, I have had problems with -d in the past.
Perhaps just cp -pPRx would be the best.
-P Do not follow any symbolic links, neither those that occur in
the parameter list nor those encountered during the recursive
copy. Just copy them as symbolic link.
-R Copy directories recursively, and do the right thing when
objects other than ordinary files or directories are encoun-
tered. (Thus, the copy of a FIFO or special file is a FIFO or
-p Preserve the original files' owner, group, permissions (includ-
ing the setuid and setgid bits), time of last modification and
time of last access. In case duplication of owner or group
fails, the setuid and setgid bits are cleared. (Note that
afterwards source and copy may well have different times of
last access, since the copy operation is an access to the
Skip subdirectories that are on different filesystems from the
one that the copy started on.
-d Copy symbolic links as symbolic links rather than copying the
files that they point to, and preserve hard links between
source files in the copies.