![](https://seccdn.libravatar.org/avatar/696255f62c3cefe5d517f913058b70bc.jpg?s=120&d=mm&r=g)
On Friday 02 September 2005 21:54, Greg Wallace wrote:
Well, I've been trying to move toward 9.3 in a step by step fashion, starting from 8.1. <snip>
Hi Greg, Why are you doing this in stages? I have a dedicated /home partition, so when I go from one version to the next, I just move ("mv") my user directory, /home/carl, to /home/.carl (hidden) and do a clean install. The installation creates a new, "clean" user directory for me. Then I symlink across to the important stuff, like my mail, so I'm up and running in the new desktop very quickly. I then use all the tools installed with the new system to migrate/rebuild/recreate the stuff that takes a little time and isn't as straightforward. I highly recommend this approach over layering later versions on top of earlier versions. In most cases, when you're installing the later version, it does wholesale replacements anyway. As far as the specific problems you're having, AFAIK, the boot loader module is intelligent enough to create a workable solution. If it can't, it'll tell you what is wrong. Select the option to re-read the partitioning scheme and "start from scratch." Then, "force" it to save everything, not just the "changed files" at the same time it installs the boot loader. That's probably the fastest fix for the boot problem. If that system isn't being used as a gateway or firewall or server supporting other clients, you should leave IP forwarding off. Also, put some real name servers and a real domain in those fields. In my case, the name servers provided by our ISP (Verizon) are 4.2.2.1 and 4.2.2.2. The search domain is dsl.verizon.net ... that should get you back on-line. regards, - Carl a) You shouldn't have a need for more than a 1GB swap partition