On Sun, 11 Nov 2007, Rajko M. wrote:- >On Sunday 11 November 2007 11:25:59 am David Bolt wrote: > >> >it was unable to update the grub boot menu on /boot >> >> Again, I didn't have a problem here. This could have been because, >> during the installation I edited /etc/fstab and /boot/grub/device.map to >> correct the device names, or the editing may have been unnecessary. I >> don't know either way. > >Hi David, > >One of things about not supported old versions is that fstab and boot loader >update are dropped out for such versions.
Maybe so. In theory, it should work since there's no real difference between menu.lst, device.map and fstab between 9.3, 10.0 and 10.2. It's only with 10.3 do the device mapping change and again, in theory, this should be handled as if the upgrade was from 10.2. I edited /etc/fstab and /boot/menu/device.map because the installer wanted to mount the /boot partition and a couple of Windows partitions. I don't know why it wanted the Windows partitions, but it referred to them as hdb1 and hdb5 when they should have been sdb1 and sdb5. My guess, after reading Carlos' reply, and then looking at the Most Annoying Bugs page, is that the confusion over the device names was related to bug #330705. While it mentions a separate /var causing problems, I think having the mixed PATA and SATA configuration confused the upgrade code and so needed the manual assistance to sort it out. >It may succeed, but there is no >workarounds for differences. I think that the procedure detailed here: <URL:http://en.opensuse.org/How_To_Upgrade_System_with_Separate_/var_Partition> should work. I'll have to try that method out the next time I have a huge version jump to perform. Regards, David Bolt -- Team Acorn: http://www.distributed.net/ OGR-P2 @ ~100Mnodes RC5-72 @ ~15Mkeys | SUSE 10.1 32bit | openSUSE 10.2 32bit | openSUSE 10.3 32bit SUSE 10.0 64bit | SUSE 10.1 64bit | openSUSE 10.2 64bit | RISC OS 3.11 | RISC OS 3.6 | TOS 4.02 | openSUSE 10.3 PPC -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
