Hi DongInn, when you get a shellout on the PS3: try unpacking the tarball manually. Try putting it to the PS3 by transporting it with a memory stick. When untarring, check the errors: do they look like the tarball is corrupt? Can you unpack the tarball on the master node (PS3)?
My feelings go towards some 32 vs. 64 bit mismatch of the tar binary, though I'd expect the two should be compatible. Anyway, one of the tars comes from busybox, the other one from a distro (YDL), and the tar which has built boel_binaries might come from another distro (?)... Regards, Erich On Monday 03 December 2007 18:16, DongInn Kim wrote: > Hi, > > I have tried to test systemimager-4.0.1.svn4354.kexecfix+rsync3pre6.bli on > YDL5-PPC64 (PS3) and I got a little different error this time. > But it does not look so good. > --------------<error log on the client node>-------------- > > Monitoring initialized. > > start_syslogd > > get_boel_binaries_tarball > rsync -av 129.79.246.46::boot/ppc64-ps3/standard/boel_binaries.tar.gz > /tmp/boel_binaries > receiving file list ... done > boel_binaries.tar.gz > > sent 136 bytes received 18220901 bytes 12147358.00 bytes/sec > total size is 18218548 speedup is 1.00 > tar: Unknown typeflag: 0x4c > tar: Unrecognised file type > Killing off running processes. > > write_variables > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > This is the SystemImager autoinstall system > > --------------<error log on the client node>-------------- > > If anyone can figure out this problem, that would be really appreciated. > > Regards, > > - DongInn > > > Bernard Li wrote: > > Done. > > > > BTW, the latest SystemImager snapshot from branch-4.0.x is now available > > here: > > > > http://therealms.org/oss/systemimager/snapshots/ > > > > Cheers, > > > > Bernard > > > > On 12/2/07, Andrea Righi <[EMAIL PROTECTED]> wrote: > >> Bernard Li wrote: > >>> Hi Andrea: > >>> > >>> On 12/2/07, Andrea Righi <[EMAIL PROTECTED]> wrote: > >>> > >>>> don't use the current SI trunk, it needs more testing and debugging > >>>> activities, > >>>> because a lot of core-packages have been updated. > >>>> > >>>> The next SI stable release will be based on the 4.0.x branch: > >>>> http://svn.systemimager.org/listing.php?repname=systemimager&path=%2Fbranches%2F4.0.x%2F&rev=0&sc=0 > >>>> > >>>> So, better to use this branch for a while... > >>> I see -- should I backport both my recent fixes to trunk to branch-4.0.x? > >>> > >>> http://www.systemimager.org:8000/trac.systemimager.org/changeset/4353 > >>> http://www.systemimager.org:8000/trac.systemimager.org/changeset/4354 > >>> > >> Sounds good. Do it please. > >> > >> -Andrea > >> ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ sisuite-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
