SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When I got my new laptop, I decided to try out a couple of different distros. So, I partitioned my hard drive accordingly, and installed Ubuntu on the first partition. I then installed Slack on my second root partition (I had separate /home partitions for each distro). Ubuntu was lovely and easy to use, but it wasn't the same as Slackware, and I've since been using Slack as my primary OS again. I'd rather not have to format my entire disk and start again as it's getting to the stage where my Slack install is getting very highly configured.
The problem I have is that Ubuntu is managing the booting of the computer with Grub. I want to move Slack back to the first partition of the disk, and remove Ubuntu altogether. This will presumably mean I lose Grub. Is my plan of action correct:
Boot to a LiveCD.
Make an image of my Slack installation.
Remove the partitions on my disk.
Make the parition layout for one distro only (plus Windows XP).
Restore the Slackware image.
Boot to the Slackware installation CD and install lilo.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,637
Rep:
Your steps look right to me.
You might consider cloning your Slackware installation (for example using rsync) to the first partition, so you would not need the image. Depending on your exact partition layout and how/if you want to change your partition layout this could be difficult or impossible with your home partition though.
If you want to keep grub you can do that. There is a grub package in /extra.
I'm not really too bothered which boot loader I have, so long as it works!
At the moment I have a setup like this: (hope this works!)
Code:
Primary Extended
|---------||--------------------------------------------------------------|
|---------||----|------------|---------------|--------------|-------------|
Windows Swap Ubuntu root Ubuntu home Slack root Slack home
(hda1) (hda5) (hda6) (hda7) (hda8) (hda9)
What I'd like it to just have three partitions for Linux: hda5, hda6 and hda7, with 6 and 7 being root and home respectively.
As it stands, I can just move everything in my /home partition onto my external USB disk as either an image or a tarball or something (how would I preserve the permissions?) and then restore it when I've finished moving the root partition.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,637
Rep:
I used rsync to make a copy of my slackware installation before.
I mounted the partition where the copy should be created as /mnt/slack-A-root and /mnt/slack-A-home, then executed (no guarantee, please take a look at other rsync examples or the man page before doing it):
The trailing slash at the source's path is important!
If I were in your situation I would first copy Ubuntu's /boot folder (at least the grub folder), and modify the menu.lst and copy it back after rsync. Then I would change the rsync-copy's fstab file (if you have absolute /dev-points there and do not mount by label or uuid).
Ah, I see. The problem I have with using rsync to backup to my external disk (which is what I would do) is that it's formatted using fat32, and therefore doesn't keep the original permissions. I suppose I could make an image of /home, and then mount that to some temporary mount point using -o loop after I've sorted out the parition scheme, and simply copy the contents of that image back into my new /home.
I could also just install the grub package now, and then copy the contents from the ubuntu /boot into the slack /boot.
You may also just copy whole installation to required partition and then resize.
boot from Live/Rescue CD
by fdisk create partition 6 in place of 6 and 7
create new filesystem on part. 6 (ext3)
mount partitions 8,9 and new 6
copy contents of 8 and 9 to 6 (by cp -a f.E.)
update lilo or grub with new partition 6
u(n)mount part. 6, erase part. 8 and 9
resize part. 6 and then create part. 7 of the remaining space and move /home to it
Take it as an excersize how to do it without backups, but forget it when there are some important data for you. In addition it's usefull for filesystems with unchallanged resizing capability.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,637
Rep:
Anyways it would be a good idea to make the backup (with tar or whatever) to your external hard disk, no matter how you will solve your problem. This should make your head ache a little less
Well, I want to resize my root partition, and leave all the rest of the drive as /home (it's a 40GB hard drive, and currently I only have a 5GB root partition and a 10GB /home partition for slack (the rest is ubuntu and windows).
This is what I think I'll do:
Make an image of slack root and slack home.
Wipe the drive of all the linux paritions.
Restore the image of my slack installation.
Resize the root partition using a liveCD.
Boot into the installation CD and install lilo.
Finally make a new home and restore that from an image too.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.