https://bugzilla.novell.com/show_bug.cgi?id=846068 https://bugzilla.novell.com/show_bug.cgi?id=846068#c3 Marcus Schaefer <ms@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #3 from Marcus Schaefer <ms@suse.com> 2013-10-21 10:33:43 UTC --- Ok I added the custom profile to the boot images and tested it with a bootincluded kernel-desktop. On build you get information like: Oct-21 11:58:35 <1> : Boot including package(s) [bootstrap]: Oct-21 11:58:35 <1> : --> kernel-desktop .. Oct-21 11:58:35 <1> : Updating Type section Oct-21 11:58:35 <1> : --> bootkernel: custom Hope that's ok. here is the commit commit eb33c9ed6de3bfae7edb4b646f56daa6a66e0150 Author: Marcus Schäfer <ms@suse.de> Date: Mon Oct 21 11:45:51 2013 +0200 - added custom bootkernel profile (bnc #846068) * with the bootkernel="custom" profile one can prevent the installation of a kernel in the kiwi boot image (initrd) This makes sense if a non profiled kernel or a specific version of a kernel is used as part of the system image XML description. Examples: <type ... bootkernel="custom"/> ==> version pinned kernel: <package name="kernel-default-3.7.10-1.16.1" bootinclude="true"/> ==> non profiled/custom kernel: <package name="kernel-bob" bootinclude="true"/> If the custom bootkernel attribute is used it's required to mark the kernel in the system image XML with bootinclude="true" If this is not done the initrd will not have a kernel/modules which is in most cases unwanted -- 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.