https://bugzilla.novell.com/show_bug.cgi?id=392054
User agruen@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=392054#c13
Andreas Gruenbacher changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aosthof@novell.com
Status|RESOLVED |REOPENED
Resolution|FIXED |
--- Comment #13 from Andreas Gruenbacher 2008-05-22 03:31:35 MST ---
Comment 11: I see -- that's ugly. I think it will be safest to reintroduce the
/.buildenv check for now, at least until we have fully analyzed the situation.
That way we won't end up in a worse mess than what we have right now at least.
Comment 5: What are the reasons why the filesystem into which the packages are
installed (apparently) has an /etc/fstab? Is a fake fstab required by other
packages? Otherwise, would it make sense to ensure that no /etc/fstab exists
while the image is being created? This would also stop the kernel %post from
creating an initrd / trying to update the boot loader.
Another problem with skipping the bootloader configuration in the kernel %post
is that the kernel %post is supposed to create the bootloader entries (and YaST
won't otherwise do it for the kernel).
So on the one hand in some cases you want to skip creating the initrd because
an initrd isn't needed, and on the other hand, you want to still invoke
perl-Bootloader. This makes me wonder whether we shouldn't move the initrd
creation into perl-Bootloader (which knows the kind of system, and knows
whether an initrd make sense), and let the kernel %post invoke perl-Bootloader
unconditionally.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.