Bug 179640

Summary:	YaST / Bootloader / Propose New Configuration -> bad result
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Tim Fechtner <timmi>
Component:	YaST2	Assignee:	Olaf Dabrunz <odabrunz>
Status:	RESOLVED FIXED	QA Contact:	Stanislav Visnovsky <visnov>
Severity:	Normal
Priority:	P3 - Medium	CC:	stefan.fent, suse-beta
Version:	Final
Target Milestone:	---
Hardware:	All
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	snapshot1.png - Screenshot of the YaST proposel log.tar.bz2 - the hole /var/log as tar.bz2 archive boot.tar.bz2 - /boot as tar.bz2 archive excluding initrd-2.6.16.13-4-default /boot/initrd-2.6.16.13-4-default

Description Tim Fechtner 2006-05-29 13:47:19 UTC

YaST / Bootloader / Propose New Configuration gives a bad result.

I've done the following.

- Starting YaST Control Center
- Starting System / Bootlaoder
- Choosing Other / Propose New Configuration

The result is quiet interesting (see snapshot1.png).
- The name of the first entry is empty.
- The name of the 4. entry is "Failsafe --", and not "Failsafe"
- The 5. entry is another kernel. For what is it usefull?

Comment 1 Tim Fechtner 2006-05-29 13:48:20 UTC

Created attachment 85559 [details]
snapshot1.png - Screenshot of the YaST proposel

Comment 2 Tim Fechtner 2006-05-29 13:51:48 UTC

Created attachment 85560 [details]
log.tar.bz2 - the hole /var/log as tar.bz2 archive

Comment 3 Tim Fechtner 2006-05-29 13:58:28 UTC

Created attachment 85565 [details]
boot.tar.bz2 - /boot as tar.bz2 archive excluding initrd-2.6.16.13-4-default

Comment 4 Tim Fechtner 2006-05-29 14:00:52 UTC

Created attachment 85567 [details]
/boot/initrd-2.6.16.13-4-default

Comment 5 Stefan Fent 2006-10-16 09:28:57 UTC

Those are two different things:
Apparently print-product.ycp seems not to do the right thing
Can you please add the result of 'yast2 print-product'?
Do you have all updates installed? I can't reproduce here

The second part, the last line comes from the bootloader configuration
not following links, so you get one entry for /boot/vmlinuz, which is a link to the real kernel image, and one for the real kernel-image.
There is not much we can do about this.

Comment 6 Tim Fechtner 2006-10-16 18:38:23 UTC

>> Those are two different things:
>> Apparently print-product.ycp seems not to do the right thing
>> Can you please add the result of 'yast2 print-product'?

SUSE Linux 10.1

>> Do you have all updates installed? I can't reproduce here

Now, having all updates, I also can't reproduce it no longer.

>> The second part, the last line comes from the bootloader configuration
>> not following links, so you get one entry for /boot/vmlinuz, which is
>> a link to the real kernel image, and one for the real kernel-image.
>> There is not much we can do about this.

As the first part seems to be solved, and the second part won't be fixed, this bug can be closed. Setting resolution to "fixed".