Welcome to Linux Forums! With a comprehensive Linux Forum, information on various types of Linux software and many Linux Reviews articles, we have all the knowledge you need a click away, or accessible via our knowledgeable members.
Write an article for LinuxForums Today! Win Great Prizes!
I want to upgrade my Debian from lenny (stable) to squeeze (testing), I would like some advice.
It is rather important that I don't end up with a non-functioning installation, even if its just for a short time, because it's my work computer and my boss wouldn't take a Debian upgrade as an excuse for not having a computer. He prefers Windows anyway, and that's the only OS the ICT department supports.
I would like to dual boot between lenny and squeeze, so that I can always fall back to lenny if squeeze didn't work out for some reason. I would keep my /home and share it between the two.
I would do the following:
Boot my system with a Linux live CD.
Make an image of my root partition with partimage as backup.
Resize the root partition to make space for the root partition of squeeze.
Create the root partition, format it as ext3, and copy everything from the lenny root fs to the new squeeze root fs, OR
Use the image created in step 2 in stead.
Edit the /boot/grub/menu.lst to make an entry for the new (soon-to-be-upgraded-to-squeeze) Debian.
Reboot. Since I now should have to identical lennies, I can choose which I will use for the upgrade.
In lenny perform the upgrade to squeeze. I have yet to find out how to exactly do that.
Is this to much work for a little safety?
An additional advantage is that once squeeze is running fine, I have an additional partition I can use for other OS's at some later time, like Debian 64 bit.
Is it wise to share my /home between lenny and squeeze? Or should a duplicate that too?
What do you think of my strategy in general?
__________________ OS's I use: Debian Lenny, Windows XP, Windows Vista
that is definitely a cautious approach. Why don't you just back everything up to a remote server and then upgrade, if it foobars you can just rollback? That would be the easiest IMO and there is very little actual downtime involved if you use something like this: Virtualize a Server with Minimal Downtime
that article is for going P2V but the concept is the same and it works like a champ.
if you are wanting to be able to boot off both, I can't comment on sharing the home dir since I have never done it.
Open Source Security Myths Dispelled Dispel the five major myths surrounding Open Source Security and gain the tools necessary to make a truly informed decision for your IT organization subscribe
InformationWeek InformationWeek is the only newsweekly you'll need to stay on top of the latest developments in information technology. subscribe