On Wed, 2007-12-12 at 16:12 +1300, Clint Dilks wrote: > Gregory P. Ennis wrote: > > On Wed, 2007-12-12 at 15:47 +1300, Clint Dilks wrote: > > > >> Gregory P. Ennis wrote: > >> > >>> On Tue, 2007-12-11 at 15:32 -0800, Liam Kirsher wrote: > >>> > >>> > >>>> Does eula stand for End User Licensing Agreement, perhaps? Just a guess. > >>>> If it's a script why don't you just look in it (the calling script) and > >>>> see what it's doing? > >>>> Also, maybe the eula binary exists (did you look for it?) but is not > >>>> executable, which should be easy to fix. > >>>> > >>>> Gregory P. Ennis wrote: > >>>> > >>>> > >>>>> All.... > >>>>> > >>>>> I am trying to install vsifax on a 64 bit Centos 5.1 system. The Esker > >>>>> staff have been helpful but no cigar. > >>>>> > >>>>> At first they thought the problem might be related to a 64 bit machine > >>>>> so I tried to install vsifax on a 32 bit Centos 5.1 machine and received > >>>>> the same error. > >>>>> > >>>>> One of their installation scripts is trying to execute a binary called > >>>>> eula which fails. > >>>>> > >>>>> ./eula: cannot execute binary file > >>>>> > >>>>> The tech support of vsifax advised me they had one other customer use > >>>>> Centos 4.5 and succeeded in a vsifax installation. > >>>>> > >>>>> I was hoping whoever had the other vsifax installation might be > >>>>> listening to this list and could give me a hand. > >>>>> > >>>>> Thanks much!!! > >>>>> > >>>>> Greg Ennis > >>>>> > >>>>> _______________________________________________ > >>>>> > >>>>> > >>> The vsifax documentation does not declare what the file is, but their > >>> installation scripts try to execute the 'eula' file and and fails. In > >>> looking at the contents of the file it is not a simple script, but looks > >>> like a binary executable file. I tried to execute the file manually and > >>> received the same error : > >>> > >>> [root at MailIn install]# ./eula > >>> -bash: ./eula: cannot execute binary file > >>> > >>> The file is executable : > >>> -rwxr-xr-x 1 227 105 374644 Apr 19 2007 eula > >>> > >>> The file is not a script, The beginning of the file is : > >>> ^Aß^@^DF'<90>V^@^DGz^@^@^Oe^@H^P^B^A^K^@^A^@^BÅø^@^@f<98>^@^@^@^D > >>> ^@ià^P^@^A( ^@^G ^@j > >>> ´^@^B^@^A^@^B^@^B^@^D^@^C^@^E^@^C1L^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@.text^@^@^@^P^@^A(^P^@^A(^@^BÅø^@^@^A(^@^C<94>Ä^@^@^@^@ î^@^@^@^@^@ .data^@^@^@ ^@^G ^@^G ^@^@f<98>^@^BÇ ^@^Cø^P^@^@^@^@^Gñ^@^@^@^@^@@.bss^@^@^@^@ ^@m¸ ^@m¸^@^@^@^D^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@<80>.loader^@^@^@^@^@^@^@^@^@^@^@g^K^@^C-¸^@^@^@^@^@^@^@^@^@^@^@^@^@^@^P^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@<82>"^@$|n^[x|<8f>#x|°+x|^^ø^@<91>Â^@^@<91>â^@^D<82>1^@^@<81>B^@(9 ^@^@e)^D^C-^Q^@^@<91>*^@^@@<82>^@^PH^@^@<91>`^@^@^@H^@^@^T<83>â^@0H^@^A<81><80>A^@^T|n^[xA<8a>^@^\<80>^Q^@^@<90>A^@^T| ^C¦<80>Q^@^DN<80>^D!<80>A^@^T<80>â^@89^@^@^@}Ãsx}ä{x~^E<83>x<91>^G^@^@H^@^Ai`^@^@^@<80>â^@^\,^G^@^@A<82>^@^H<80>b^@ H^B^T<81><80>A^@^T|<81>^H^H^@^@^@^@^@^L @^@^@^@^@^@^@^@¬^@^G__start^@^@^@<80>b^@^H|^H^B¦,^C^@^@<94>!ÿÀ<90>^A^@HA<82>^@À<81>c^@^@<90>A^@^T}h^C¦<81>c^@^H<80>C^@^DN<80>^@!<80>A^@^T<80>b^@^L,^C^@^@A<82>^@^\<80>^C^@^@<81>c^@^H|^H^C¦<80>C^@^DN<80>^@!<80>A^@^T<80>b^@^P,^C^@^@A<82>^@^\<80>^C^@^@<81>c^@^H|^H^C¦<80>C^@^DN<80>^@!<80>A^@^T<80>b^@^T,^C^@^@A<82>^@^\<80>^C^@^@<81>c^@^H|^H^C¦<80>C^@^DN<80>^@!<80>A^@^T<80>b^@^X,^C^@^@A<82>^@^\<80>^C^@^@<81>c^@^H|^H^C¦<80>C^@^DN<80>^@!<80>A^@^T<81><81>^@H8!^@@}<88>^C¦N<80>^@ 8!^@@N<80>^@ ^@^@^@^@^@^@ A<80>^@^@^@^@^@^@Ü^@^N__threads_init<80>^@^@,<81><82>^@4<90>A^@^T > >>> > >>> > >>> Thanks for your help!! > >>> > >>> Greg > >>> _______________________________________________ > >>> CentOS mailing list > >>> CentOS at centos.org > >>> http://lists.centos.org/mailman/listinfo/centos > >>> > >>> > >>> > >> Hi, > >> What information is returned when you type file eula ? > >> > >> > >> > > > > typing in ./eula returns > > -bash: ./eula: cannot execute binary file > > > > I have also tested some of their binary executable files and get the > > results. I looks like to me that they complied the files for a system > > different than EL5 Linux. > > > > _______________________________________________ > > CentOS mailing list > > CentOS at centos.org > > http://lists.centos.org/mailman/listinfo/centos > > > > > Hi, if you type file <file to test> it should give you information eg on > one of my systems if I type > > file /usr/bin/pstree > > /usr/bin/pstree: ELF 32-bit LSB executable, Intel 80386, version 1 > (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), stripped > > Clint, Sorry... did . not understand your grammar thanks for the clarification Here is the result. eula: executable (RISC System/6000 V3.1) or obj module not stripped Looks like to me that they gave me the wrong binaries. Do you agree? Greg