Upgrade from Beta-1 or Beta-2 to Beta-3 left 2 machines in non-bootable
On the other two installer installed kernel-2.2.16-8, but did not create
/boot/initrd-2.2.16-8.img and also did not update /etc/lilo.conf for
Which caused kernel panic after reboot, had to reboot with Emergency
kernel and update bootsect maanually.
On one machine with nVidia GeForce DDR (Generic) XFree86 does core dump.
Not very impressed with Beta-3!!!
This defect is considered MUST-FIX for Winston Beta-5
*** Bug 13545 has been marked as a duplicate of this bug. ***
This defect is considered MUST-FIX for Winston Release-Candidate #1
(especially since it wasn't fixed for beta-5)
OK, so we've tried several ways to reproduce this (in good faith). I agree that
betas 1-3 were not so good... but how does an upgrade from 6.2 to beta-5, or
even an upgrade from beta-3 to beta-5 work? I'm reluctant to close this defect
because I don't want something important to slip through the cracks, but I don't
want to hold up the release candidate for a corner-case defect related to
hackware (let's face it, beta-3 was NOT a good build).
Are you comfortable with me resolving this as WORKS4ME? We've done literally
hundreds of upgrades to Pinstripe with no discernable results similar to what
It is Ok to close this case.
But please note on a DELL 2400 server upgrade from RH 6.1 to Pinstripe
did mess up. See my posting at the list. I had to do a fresh install without
formating disk, to get the system back in order.
I'm marking this defect as resolved; please submit another defect report against
the upgrade issue with the Dell 2400 (6.1->Pinstripe) and we'll see what we can