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.
Just got a quick question in regards to cloning my slackware 14.1 install from a HDD to SSD
I've got a 64gb SSD as i've replaced the boot drive in my main (windows 7, don't hurt me!) machine with a larger one, so I'm wanting to put the 64gb in my HP Microserver as its boot/program drive. When i installed slackware in the first instance, i wasn't paying attention to the installer, as it's a little server i've got a few drives in there. I thought it was installing to the 250gb drive that i was using for it's boot/program drive with Arch, which is SDA, but it actually installed it on a 250gb partition on another drive, which is SDC1.
I'm thinking it would be best to connect up the SSD, use dd to clone the boot/program partition to it. It's about 15gb at the moment, so i'm not sure if i can use dd to clone it as i'm not sure if dd will try and clone the entire 250gb, or just what is used. I've had a search but i can't seem to see a better solution, really.
Also, once i've cloned it, can i just edit the /etc/fstab and lilo.conf to point it to SDA, after i've used cfdisk to mark it as bootable? i've not used UUID or anything like that for the drive names, so i'm hoping i can just edit the relevant files, rerun lilo to confirm the changes and i'd be all set, but again, not sure.
I've also got the /home directory currently on the boot/program drive. What i want to do once i've cloned the install is to have the /home directory on the partition i've just cloned from. If i boot up without doing this, and it works, can i reformat the partition, copy over the files from the current /home directory onto the partition, edit /etc/fstab to mount the /home directory on the partition and reboot, would that be enough to sort this, or am i missing anything out?
Last edited by Condemn; 02-14-2014 at 06:52 AM.
Reason: made it clearer (hopefully!) as to what i'm asking
I have just changed my main drive again the way i usually go is to install the new drive boot from the install cd or live usb/cd if i have one around, if the drive i am copying from is full i just use dd onto the new drive then adjust the partion to match the new disk. If there is a lot i free space i mount the new and old drive and use rsync to copy files across remembering to exclude dev mount media etc. Then I remove the old drive (if replacing) or just make sure its connected to the correct controller, reboot to the install disc/live cd/usb mount the new disk chroot edit fstab and lilo run mkintrid run lilo and reboot.
To move the home directory that is almost everything you have to make sure you the old home directory is gone otherwise it will still take up space but you wont be able to see it, i have made that mistake in the past and it took me quite a while to work out how i had run out of space.