Discussion:
[Sisuite-devel] [ systemimager-Bugs-1190929 ] si_mkautoinstallcd does not work with custom kernel file
SourceForge.net
2007-04-17 17:15:49 UTC
Permalink
Bugs item #1190929, was opened at 2005-04-27 06:37
Message generated for change (Comment added) made by u4imcwdm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100259&aid=1190929&group_id=259

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: systemimager-server
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: si_mkautoinstallcd does not work with custom kernel file

Initial Comment:
There are problems creating a boot cd with custom
kernel and initrd files. Below is the output of the
si_mkautoinstallcd, and the files used are attached.

The version used is 3.4.0-2 for Debian, installed with
apt-get.

# si_mkautoinstallcd --kernel
/var/lib/systemimager/images/gclient/boot/vmlinuz-2.6.8-2-686
--initrd
/var/lib/systemimager/images/gclient/boot/initrd.img-2.6.8-2-686
--out-file bootcd.iso

Creating temporary working directory...
2880+0 records in
2880+0 records out
2949120 bytes transferred in 0.053779 seconds (54837661
bytes/sec)
Creating DOS filesystem on temporary image...
mkdosfs 2.11 (12 Mar 2005)
Using "syslinux" to make CD image bootable...
Mounting temporary image in loopback mode...
Filesystem 1K-blocks Used Available Use%
Mounted on
/tmp/systemimager.autoinstallcd.temp.dir/boot/siboot.img
2863 2860 3 100%
/tmp/systemimager.autoinstallcd.temp.dir/mnt
Couldn't copy
/var/lib/systemimager/images/gclient/boot/initrd.img-2.6.8-2-686
to /tmp/systemimager.autoinstallcd.temp.dir/mnt!
#


----------------------------------------------------------------------

Comment By: wdmac2658 (u4imcwdm)
Date: 2007-04-17 12:15

Message:
Logged In: YES
user_id=1771783
Originator: NO

this is a autoinstall cd, why should the 1.44 size limit matter?

----------------------------------------------------------------------

Comment By: Jerry DeLapp (jerrygd)
Date: 2005-04-27 08:11

Message:
Logged In: YES
user_id=512778

This is not a bug.

Your custom kernel and initrd are too big to fit. The total size of both
must be less than 2880 blocks, and your kernel alone is 2680 blocks.

You need to restructure your kernel and initrd to insure that together
they total less than 1.44MB (2880 blocks).

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100259&aid=1190929&group_id=259
Loading...