Thomas Backlund <[EMAIL PROTECTED]> writes:
<(not a top-post answer> please sent splitted bug reports, one item
per mail so that threads do not badly get
mixed for different bugs (idem for bugzilla)
> Synced Cooker as of 20030826, 10:00 UTC,
> and executed gendistrib...
> Install-mode: expert, using network.img
> Locale: fi, UTF8
>
> nforce2 system, 1GB RAM...
>
> most buttons for advanced / extra options shows the wrong caption
> when install is started with "linux expert"...
> - ex. a button shows "advanced" even if the advanced mode is already
> active. pushing it one will get you to standard mode with the caption
> "advanced" on the button. Pressing it again will put you in advanced
> mode again, but this time with the right caption ("standard") on the
> button...
i fixed this one last week. changelog extract:
>============================================================================>
> 2003-08-22 14:59 Thierry Vignaud <[EMAIL PROTECTED]> >
> >
> * interactive/gtk.pm: (ask_fromW) split $set_advanced into >
> $set_advanced and $set_advanced_raw to fix drakconnect "failling" >
> to detect network interfaces in standalone mode when in expert >
> mode >
>============================================================================>
> packages selection:
> - enterprise kernel was not selected, even if I had 1GB of ram...
> - kde locales was not selected according to selected locales at the
> beginning...
pixel ?
> summary screen:
> - I chose network, but then decided to not change anyhing,
> but there was no "cancel" button... so I tried to leave everything
> unselected and pressed next -> installer hanged itself there :(
> I waited for 10 minutes before changing to console and did
> reboot...
poulpy ?
> New user wizard:
> - this window IMHO need some kind of frame to separate it better from
> the background when you choose / have chosen a kde theme...
warly ?
> And last a _BAD BUG_ that I noticed now....
> - since I also installed the 2.6 kernel from contribs,
> this happend in /boot: (symlinks)
> vmlinuz -> vmlinuz-2.6.0-0.test4.1mdk
> initrd.img -> initrd-2.6.0-0.test4.1mdk.img
>
> And the original up kernel got installed as:
> (wich ofcouse is working)
> image=/boot/vmlinuz-2.4.22-0.8mdk
> ...
> initrd=/boot/initrd-2.4.22-0.8mdk.img
>
>
> BUT ...
> since the installer adds nonfb and failsafe according to
> vmlinuz/initrd.img we will have people that will boot into
> 2.6test kernel when they try to fix a problem with failsafe mode :(
>
> So the question is ...
> Is it possible for the installer and/or installkernel to _not_ modify
> symlinks in /boot unless the kernel is in main ?
>
> one way is of course to add -L to /sbin/installkernel in
> %post scripts for contrib kernels....
pixel ?
