Carlo Scarfoglio <scarfoglio(a)arpacoop.it> writes:
The update system has problems when there is a
separate /boot partition.
I was forced to create one when I installed an alpha because I use an
LVM setup. But all the Betas botched the update by creating a new /boot
directory on / (root). I had to copy the installed files (kernel,
initrd, etc) to the /boot partition by hand. Not difficult, but for a
newbie a real nightmare. Consider that the system boots from the /boot
partition with the *not* updated* kernel, which will not find its modules.
In general the update process sees just one /, all other mount points
could you file a bugreport for this and attach the YaST log files that
show that it did not work?
The beta1 finally seems to give the option to add
for mount points, but it fails because it prepends /mnt to the directory
set by the user. In my case, /dev/sdc1 is the /boot partition and that's
what I inserted, but when I pressed OK, a popup complained that there
was no /mnt/boot partition.
Additionally, it is strongly needed to add the option to select on what
disk grub will be installed, both to the install and update system.
I, for an example, have two disks on this PC. The old one with openSuSE
10.2, and a new one for 10.3. I select in the BIOS which disk to boot
from. When I installed and each time I update from DVD, I had to
disconnect the old disk cable, because the kernel sees it as the first
disk and will install grub there.
Thanks for the otherwise excellent distro. It might reach the heights of
SuSE 10.0, the best ever.
thanks for your testing,
Andreas Jaeger, Director Platform/openSUSE, aj(a)suse.de
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126