Hi Jing,
sorry for the late reply, I've been on vacation for few days.. ;-)
Your results are great! I'll include your changes in the trunk and I
hope the next release will work better on ppc64.
Anyway, I've a question regarding the libs in boel_binaries, since the
libs conflict look quite strange... the libs in the initrd should be
always a subset of the libs included in boel_binaries. In both cases the
script mklibs is used to copy & strip the libraries into the initrd as
the boel_binaries tarball.
The only difference is that with boel_binaries the list with the
directories of the libraries to be copied has more elements...
The doubt (and the only difference from the generation of the libs in
initrd) is that libnss* could be overwritten by mklibs.
So, could you try to apply the following patch and see if it can resolve
the lib problem?
Index: make.d/boel_binaries.inc
===================================================================
--- make.d/boel_binaries.inc (revision 3794)
+++ make.d/boel_binaries.inc (working copy)
@@ -132,6 +132,9 @@
test ! -d /lib64 || TGTLIBDIR=lib64 ; \
cd $(BOEL_BINARIES_DIR) \
&& $(PYTHON) $(TOPDIR)/initrd_source/mklibs -L
$(SRC_DIR)/$(PARTED_DIR)/libparted/.libs:$(DISCOVER_DIR)/lib/.libs:$(SRC_DIR)/$(DEVMAPPER_DIR)/lib/ioctl:$(SRC_DIR)/$(E2FSPROGS_DIR)/lib:/lib64:/usr/lib64:/usr/kerberos/lib64:/lib:/usr/lib:/usr/kerberos/lib:/lib/tls:`find
/lib/tls /usr/lib/tls /lib64/tls /usr/lib64/tls -type d 2>/dev/null | tr '\n'
:` -v -d $$TGTLIBDIR bin/* sbin/* $(INITRD_BUILD_DIR)/*bin/*
$(INITRD_BUILD_DIR)/usr/*bin/*
+
+ [ -d /lib64 ] && cp -a /lib64/libnss* $(BOEL_BINARIES_DIR)/lib64 || true
+
#
# Include other files required by openssh that apparently aren't
# picked up by mklibs for some reason. -BEF-
Many thanks,
-Andrea
PS I don't remember if I already asked this question, but can I add you
in the CREDITS file? I think your tests with ppc64 have been very
precious for systemimager. The entry would look like this (is it ok?):
Index: CREDITS
===================================================================
--- CREDITS (revision 3794)
+++ CREDITS (working copy)
@@ -143,6 +143,10 @@
E: [EMAIL PROTECTED]
D: PPC Porting related stuff
+N: Jing Sun
+E: [EMAIL PROTECTED]
+D: fixes and improvements on PPC64 support
+
N: Denise Walters
E: [EMAIL PROTECTED]
D: Put the documentation into a much more professional format
Jing CDL Sun wrote:
> Hi, Andrea:
>
> I have resolved this problem manually, based on the PREP partition; I
> changed the file "img1.master"(it is my autoinstallscript).
> Before run systemconfigurator command (in line 572), I have added a code
> line to copy the yaboot file to /a/boot/ so that the
> Systemconfigurator can find the correct yaboot file and write it to the
> PREP partition. Such as:
>
> 570 [ -z $DEVICE ] && DEVICE=eth0
> 571 cp -f /a/usr/lib/yaboot/yaboot /a/boot/yaboot # added
> 572 chroot /a/ systemconfigurator
> --excludesto=/etc/systemimager/systemconfig.local.exclude --configsi
> --stdin << EOL || shellout
>
> After these two modifications mentioned in my mails, we can use SIS to
> install RHEL4QU4 on ppc64 platform :)
> But I think there should be some formal methods to fix them, for
> example, for the error above I think the correct code change may be
> Done in the file /usr/lib/systemconfig/Boot/YaBoot.pm(it is located in
> the systemconfurator rpm package) line 81 ~ 89.
> Because the yaboot file location is written to /boot/yaboot, but the
> right yaboot file is put in /a/usr/lib/yaboot/yaboot.
> Since it needs to change the SIS code, so, Andrea, if you just have some
> free time, could you help to merge those code changes to SIS?
> That will be very helpful, thank you. :)
>
> I have also listed other fixes of sis on ppc64 here for your reference:
> 1. /etc/systemimager/autoinstallscript.conf will be modified to create
> the PREP and swap partition (see my mail below). Such as:
> <part num="1" size="7.813" p_type="primary" p_name="-" flags="PREP" />
> <part num="5" size="*" p_type="logical" p_name="-" flags="swap" />
> <fsinfo line="80" real_dev="none" mp="swap" fs="swap" options="defaults"
> dump="0" pass="0" format="no" />
>
> 2. zImage is too big to transfer.(use --my-modules option with
> si_prepareclient)
>
> 3. boel_binaries.tar.gz has a lib conflict with initrd.img, these libs are:
>
> libc.so.6
> libresolv.so.2
> libm.so.6
> libdl.so.2
> libncurses.so.5
>
> (So far I have to remove these libs from the boel_binaries.tar.gz manully)
>
> 4. Some code change may be needed for
> /usr/lib/systemconfig/Boot/YaBoot.pm.(see this mail)
>
> I guess the #1,#3,#4 can be merged into the SIS code, so that other
> people who will also used SIS on ppc64 platform will not encounter them,
> It is a nice thing :). And it also can make the SIS more robust. Could
> you help us? Thank you.
>
>
> *To Andrea: so many thanks for you and you have helped me a lot.*
>
>
>
>
>
>
>
>
> 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 Jing CDL Sun/China/IBMJing CDL Sun/China/IBM
>
>
> *Jing CDL Sun/China/IBM*
>
> 2006-11-01 17:45
>
>
>
> To
>
> Jing CDL Sun/China/[EMAIL PROTECTED]
>
> cc
>
> [EMAIL PROTECTED], sisuite-devel@lists.sourceforge.net,
> [EMAIL PROTECTED]
>
> Subject
>
> Re: [Sisuite-devel] CLAIM Failed when getting zImage on ppc64Jing CDL
> Sun
> <Notes:///482571B8003D5139/38D46BF5E8F08834852564B500129B2C/F620C3882D46FC9448257218003B2661>
>
>
>
> Hi,
>
> I found the partion was not correct in the target node, because
> /dev/sda1 is not a PPC PReP Boot.
> so I changed the /etc/systemimager/autoinstallscript.conf file like this:
>
> <part num="1" size="7.813" p_type="primary" p_name="-" flags="PREP" />
> <part num="2" size="125.508" p_type="primary" p_name="-" flags="-" />
> <part num="3" size="33549.807" p_type="primary" p_name="-" flags="-" />
> <part num="4" size="*" p_type="extended" p_name="-" flags="-" />
> <part num="5" size="*" p_type="logical" p_name="-" flags="swap" />
>
> then the systemconfigurator can create the partion correctly, "fdisk -l"
> on the target node is:
>
> /scripts/pre-install # fdisk -l
> ioctl32(fdisk:10525): Unknown cmd fd(5) cmd(40081272){00} arg(ffffe778)
> on /dev/sda
>
> Disk /dev/sda: 36.4 GB, 36401479680 bytes
> 128 heads, 32 sectors/track, 17357 cylinders
> Units = cylinders of 4096 * 512 = 2097152 bytes
>
> Device Boot Start End Blocks Id System
> /dev/sda1 1 4 8001 41 PPC PReP Boot
> Partition 1 does not end on cylinder boundary.(I do not know this is why)
> /dev/sda2 4 64 122164 83 Linux
> Partition 2 does not end on cylinder boundary.
> /dev/sda3 64 16062 32763483+ 83 Linux
> Partition 3 does not end on cylinder boundary.
> /dev/sda4 16062 17358 2654640 5 Extended
> Partition 4 does not end on cylinder boundary.
> /dev/sda5 16062 17358 2654639+ 82 Linux swap
>
> by this, I only can create this boot partion, but I still can not
> resolve the problem of "no Yaboot",
> could you give me any suggestions? thank you very much.
>
> ps: I think the "systemconfigurator" may be helpful to this problem, for
> there is some pm files about "Boot" and "Yaboot",
> but I did not find any materials about this component except the man
> page, and I do not know which is the right interface or option.
>
>
-------------------------------------------------------------------------
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
