On 10/2/09 7:05 PM, Bernard Li wrote:
Hi Joe:
On Fri, Oct 2, 2009 at 6:53 AM, Joe Koenig<[email protected]> wrote:
Yeah, that was the first thing I tried. When renaming the file didn't
work, I threw the -S option in, which gave the same result. If this file
was corrupted somehow, would I have gotten as far in the process as I
did, or would it just have not run at all? And, yes, I'm working with a
copy of the file, just in case.
Okay this is pretty strange.
So can you take a look at the initrd.img from
/usr/share/systemimager/boot/i386/standard/ (replace i386 with x86_64
if your server is x86_64) and compare that with the initrd.img that
you were working on. Are they the same?
Oh and one more thing. Can you post the output of:
rpm -qa | grep systemimager
Thanks,
Bernard
They are quite different actually. Would that indicate I used UYOK
without realizing? I basically followed the quick how-to on the wiki.
Here's an ls -l of them (copies of them, that is)
-rw-r--r-- 1 root root 58791424 Sep 15 10:36 initrd.img
-rw-r--r-- 1 root root 8122399 Oct 5 16:08 initrd-standard.img
The standard one is the one in
/usr/share/systemimager/boot/x86_64/standard. I should also note that
the 'standard' one unzips just fine, whereas the other continues to tell
me it is not in gzip format.
As far as the rpm query:
systemimager-x86_64boot-standard-4.0.2-1
systemimager-server-4.0.2-1
systemimager-common-4.0.2-1
systemimager-x86_64initrd_template-4.0.2-1
systemimager-i386boot-standard-4.0.2-1
Thanks,
Joe
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
