Mailinglist Archive: opensuse-bugs (13468 mails)
| < Previous | Next > |
[Bug 334475] New: kiwi: allow specification of pre-built boot image in config.xml
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Wed, 17 Oct 2007 02:40:10 -0600 (MDT)
- Message-id: <bug-334475-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=334475
Summary: kiwi: allow specification of pre-built boot image in
config.xml
Product: openSUSE.org
Version: unspecified
Platform: Other
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: P5 - None
Component: System Imaging
AssignedTo: ms@xxxxxxxxxx
ReportedBy: ms@xxxxxxxxxx
QAContact: adrian@xxxxxxxxxx
Found By: ---
So I talked to Marcus for a while about how to do the branding
automatically and it is indeed a bit more complicated than we'd thought.
Basically, when Kiwi builds an image, it actually builds TWO images: the
system image, and the boot image (also known as initrd).
The bootsplash branding needs to be dropped into the _boot_ image.
Right now we have no way of configuring the boot image. So Marcus is
going to modify Kiwi to give us a way of specifying a pre-built boot
image at the kiwi commandline and/or in the config.xml (Marcus, I think
it might be more useful in the commandline).
Then, we'll have to add a new step to our kiwi-runner process: first,
build the boot image with the embedded branding, THEN, build the whole
system image, passing it the pre-built boot image.
To make boot image building fast, we'll have to use a base tree there.
While Marcus is doing that, we can perfect the script that does the
generation. What we should do is create a new gfxboot theme and drop it
into /usr/share/gfxboot/themes/@image.shortname. Then, during image
build, we run 'make prep' in that directory and do the other required
actions (I'm not sure what they are).
So, it's a little more complicated than we thought, but do-able. If
making a custom operating system weren't complicated, people wouldn't
need an image builder!
--
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.
Summary: kiwi: allow specification of pre-built boot image in
config.xml
Product: openSUSE.org
Version: unspecified
Platform: Other
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: P5 - None
Component: System Imaging
AssignedTo: ms@xxxxxxxxxx
ReportedBy: ms@xxxxxxxxxx
QAContact: adrian@xxxxxxxxxx
Found By: ---
So I talked to Marcus for a while about how to do the branding
automatically and it is indeed a bit more complicated than we'd thought.
Basically, when Kiwi builds an image, it actually builds TWO images: the
system image, and the boot image (also known as initrd).
The bootsplash branding needs to be dropped into the _boot_ image.
Right now we have no way of configuring the boot image. So Marcus is
going to modify Kiwi to give us a way of specifying a pre-built boot
image at the kiwi commandline and/or in the config.xml (Marcus, I think
it might be more useful in the commandline).
Then, we'll have to add a new step to our kiwi-runner process: first,
build the boot image with the embedded branding, THEN, build the whole
system image, passing it the pre-built boot image.
To make boot image building fast, we'll have to use a base tree there.
While Marcus is doing that, we can perfect the script that does the
generation. What we should do is create a new gfxboot theme and drop it
into /usr/share/gfxboot/themes/@image.shortname. Then, during image
build, we run 'make prep' in that directory and do the other required
actions (I'm not sure what they are).
So, it's a little more complicated than we thought, but do-able. If
making a custom operating system weren't complicated, people wouldn't
need an image builder!
--
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.
| < Previous | Next > |