Hi, Andrea:
I am sorry the replay is late for I am on training for the last whole week.
I have used the option --my-modules with si_prepareclient, the initrd it built is smaller than before,
But the zImage is 10164532 bytes; it is still a little bigger. Is there anything in the initrd that we can delete?
So the zIamge can be smaller.
As an experiment, I have just removed the directory /lib/bittorrents so that the initrd is smaller, hehe,
And rebuilt the initrd and zImage, then the zImage is 8188876 bytes, and the cloned node can get the zImage correctly.
But I still have a question that is why the zImage must be small; I mean it should be less than 8M just by my experiments,
Or a CLAIM FAILED error will be encountered, is it a configuration problem of open firmware?
As you supposed, I am using the UYOK feature.
The full path of libc.so.6 in my build machine is /lib64; I have done the test,
And found maybe the libc.so.6 was covered by boel_binaries, so I removed the libc.so.6 from boel_binaries.tar.gz to workaround it.
After that, another error is encountered:
get_arch
Partitioning /dev/sda...
Old partition table for /dev/sda:
/scripts/js21n03.sh: /scripts/js21n03.sh: 173: parted: not found
dd if=/dev/zero of=/dev/sda bs=512 count=1 || shellout
1+0 records in
1+0 records out
blockdev --rereadpt /dev/sda
/scripts/js21n03.sh: /scripts/js21n03.sh: 181: blockdev: not found
It seems that there are not the command parted and blockdev in it, but I found them in the boel_binaries.tar.gz,
So I think it maybe a path problem, because actually we can find the command /boel/parted and /boel/blockdev,
And I also do compare with i386 arch, the commands are in the same directory for i386, but it can work well on i386 :(
I am totally confused. On ppc64, I have tried to find this "path", but I failed, Andrea, could you help me? Thank you.
PS:
The method to generate a zImage from kernel and initrd.img is below:
[EMAIL PROTECTED] ~]# mkzimage
Usage: /usr/bin/mkzimage <vmlinuz>|no <config>|no <sysmap>|no <initrd>|no <zImage.stub> <output>
See "man mkzimage" for more details.
For example (this is my usage):
[EMAIL PROTECTED] img1]# ll
Total 37272
-rw-r--r-- 1 tftpd tftpd 8284197 Nov 9 04:53 initrd.img
-rw-r--r-- 1 tftpd tftpd 6308538 Nov 9 05:39 initrd.img.my
-rw-r--r-- 1 tftpd tftpd 5228952 Nov 9 04:53 kernel
-rwxr-xr-x 1 tftpd tftpd 8188876 Nov 9 05:42 ks4-QU4-ppc64-zImage.initrd_172.20.3.35
-rwxr-xr-x 1 tftpd tftpd 10164532 Nov 9 05:17 ks4-QU4-ppc64-zImage.initrd_172.20.3.35.org
-rw-r--r-- 1 tftpd tftpd 34407 Nov 9 05:17 zImage.stub-2.6.9-42.EL
[EMAIL PROTECTED] img1]#
[EMAIL PROTECTED] img1]#
[EMAIL PROTECTED] img1]# mkzimage
Usage: /usr/bin/mkzimage <vmlinuz>|no <config>|no <sysmap>|no <initrd>|no <zImage.stub> <output>
[EMAIL PROTECTED] img1]# mkzimage kernel no no initrd.img.my zImage.stub-2.6.9-42.EL ks4-QU4-ppc64-zImage.initrd_172.20.3.35
Note: the intrd.img should not be too large; even we use the option --my-modules with si_prepareclient :)
Best Regards,
-----------------------------
Sun jing(孙靖)
IBM China Software Development Laboratory
Tel: (86-10) 82782244 ext.3625 E-mail: [EMAIL PROTECTED]
Address:8/F, Power Creative Building,No. 1, East Road, ShangDi, Beijing 100085, P.R.China.
![Inactive hide details for Andrea Righi <[EMAIL PROTECTED]>](gifXo6qF7zUVJ.gif){kind=small}
Andrea Righi <[EMAIL PROTECTED]>
2006-10-21 01:23
|
|
Jing CDL Sun wrote:
> I tried to fix the problem I mentioned below. and I found the zImage
> that I used mkzimage to build is too big, it is almost 18M.
> so I tried to reduce the size of zImage. I do the work below:
> 1. It seems that SIS have copied all modules into the initrd, but only
> the ones in file INSMOD_COMMAND are useful, so I deleted
> the others except the ones in INSMOD_COMMAND.
> (then I make the new initrd and the new zImage, but it still seems a
> little bigger.)
I suppose you're using UYOK feature
(http://wiki.systemimager.org/index.php/UYOK) and not the standard
kernel+initrd.img (that should be in
/usr/share/systemimager/boot/ppc64/standard/ on your image server).
Anyway to reduce the size of the initrd try to use the option
--my-modules with si_prepareclient, instead of manually remove modules.
> but, during installation, there is a confusing error:
>
> /tart_syslogd/
>
> /get_boel_binaries_tarball/
> /rsync -av 172.20.3.35::boot/ppc64/standard/boel_binaries.tar.gz
> /tmp/boel_binaries/
> /receiving file list ... done/
> /boel_binaries.tar.gz/
>
> /sent 121 bytes received 5476461 bytes 10953164.00 bytes/sec/
> /total size is 5475666 speedup is 1.00/
> /echo: error while loading shared libraries: libc.so.6: cannot open
> shared object file: No such file or directory/
> /[: error while loading shared libraries: libc.so.6: cannot open shared
> object file: No such file or directory/
> /echo: error while loading shared libraries: libc.so.6: cannot open
> shared object file: No such file or directory/
> /[: error while loading shared libraries: libc.so.6: cannot open shared
> object file: No such file or directory/
> /echo: error while loading shared libraries: libc.so.6: cannot open
> shared object file: No such file or directory/
> /[: error while loading shared libraries: libc.so.6: cannot open shared
> object file: No such file or directory/
> /echo: error while loading shared libraries: libc.so.6: cannot open
> shared object file: No such file or directory
> /
> I have checked the new initrd ,and actually there is /libc.so.6/ in it,
> i do not know why?
>
>
>
>
It seems that after untarring boel_binaries the libraries got corrupted.
Maybe because boel_binaries overwrite some libs used by busybox, and
maybe because during boel_binaries build we didn't include a needed
library path to the mklibs script...
Do you know the full path of libc.so.6 in your build machine (that I
suppose it a ppc64)?
I'm sorry, but, as I said, I've not a ppc64 machine to do those tests,
so it's a bit difficult for me to debug the problems... anyway your
tests are really precious and I'd really like to have a stable support
for ppc* architectures, so many thanks for the tests...
Regarding the split of kernel+initrd.img in the clients, honestly I've
no idea how to put them togheter to generate the zImage... if you know
the exact commands I can add a piece of code in si_prepareclient to do
that automatically.
Regards,
-Andrea
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ sisuite-devel mailing list sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
