Bugs item #1426566, was opened at 2006-02-07 12:39
Message generated for change (Comment added) made by bernardli
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100259&aid=1426566&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: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Patrick Dowler (pdowler)
Assigned to: Nobody/Anonymous (nobody)
Summary: mkbootpackage makes huge initrd
Initial Comment:
Tried to use mkbootpackage on FC4, as follows:
si_mkbootpackage
--kernel /boot/vmlinuz-2.6.11-1.1369_FC4
--new-flavor xpc64
Minor problem: got warning about untested xfs
filesystem and it did not create anything. The
xfs module is not loaded, but the test in
build_loopfile seems to chose it anyway. I
commented out the check and then it "worked",
i.e. si_mkbootpackage said:
Finished! Your new boot package lives in:
/usr/share/systemimager/boot/i386/xpc64
> ls -l /usr/share/systemimager/boot/i386/xpc64
16805761 Feb 7 11:11 boel_binaries.tar.gz
5283546 Feb 7 11:11 initrd.img
1639539 Feb 7 11:11 kernel
The initrd is 5MB compressed so I cannot make a
bootable CD image (si_mkautoinstallcd fails when
trying to copy it) because of the 2880 size limit.
I gunziped and mounted the image (ext2 filesystem)
and it looks basically the same as the original; the
only thing I can think of is that the binaries
in /bin and /sbin maybe are copies rather than
hard-links (rsync command I found in the script uses
-aHS though, so that seems unlikely)
rsync version: rsync-2.6.4-3
kernel: 2.6.11-1.1369_FC4
SI: systemimager-client-3.4.1-1
systemimager-i386boot-standard-3.4.1-1
systemimager-common-3.4.1-1
systemimager-server-3.4.1-1
----------------------------------------------------------------------
>Comment By: Bernard Li (bernardli)
Date: 2006-02-07 13:48
Message:
Logged In: YES
user_id=879102
Can you try the following development version of SystemImager:
http://www.bcgsc.ca/downloads/oscar/systemimager/
Also, use si_prepareclient instead of si_mkbootpackage - run
it with --norsync and it won't mess up your settings, the
resulting bootpackage should be useable.
The UYOK code in si_prepareclient is more up-to-date than
si_mkbootpackage. si_mkbootpackage is the correct tool to
be used, but it needs to be fixed first so use
si_prepareclient for now...
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100259&aid=1426566&group_id=259
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Sisuite-devel mailing list
Sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
