1. Support for Kernel 2.6.20 added;
2. Fixed compilation problems on Red Hat line of products;
3. Fixed "sys_ipc" parameter passing;
4. Replaced "svr4_getdents" with "sys_getdents" in "sco/sysent.c".
Alex,
No change from iBCS-3.1 when executing an SCO Unix application. As was the case with the previous version, the database server process silently dies. Yet, the application runs just fine in single user mode. I will send you the execution trace.
-Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
works brilliantly on Zenwalk linux (linux-2.6.20.3) with:
acucobol242 for sco osr 5.x.x
micro focus cobol for unix (sco osr 5.x.x)
Have no idea how to get socksys ready for testing...
Good work!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2007-03-20
Logged In: YES
user_id=1714746
Originator: NO
I have previously used implementations of Linux-ABI that are compiled into the kernel, and the applications I use require the following commands to be run for them to work:
echo 0x4100003 > /proc/sys/abi/defhandler_libcso || echo "Couldn't set default A BI handler - is /proc mounted?"
echo 0x4100003 > /proc/sys/abi/defhandler_lcall7 || echo "Couldn't set default A BI handler - is /proc mounted?"
Any idea how I can do the above using this patch? There is no /proc/sys/abi which I assume because this patch does not compile into the kernel like previous ones.
Regards,
Brad
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Brad,
Original iBCS2 package did not provide dynamic personality flag handling - neither does iBCS3 (at the moment).
To resolve your problem try this:
1) Run "utils/elf_mark -5 PathToYourBinaries";
2) If "1)" does not help replace "PER_SVR4" and "PER_OSR5" strings in "lcall/lcall.c" with "PER_OSR5 | MMAP_PAGE_ZERO";
3) If "2)" does not help - wait for iBCS-3.3.
Regards,
Alex.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Robert,
Thanks for the Execution Traces provided. The problem you described appears since release 2.6.18 with introduction of VDSO. For "OpenSuse 10.2" insert "current->mm->context.vdso = VDSO_PRELINK;" above "out_free_file:" label into "coff/binfmt-coff.c".
Proper fix (applicable to all other kernel versions) will appear in iBCS-3.3.
Regards,
Alex.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi "brente",
In order "to get socksys ready for testing" in "udev" environment do this:
......
mknod /lib/udev/devices/socksys c 30 0
chmod 666 /lib/udev/devices/socksys
init 6
......
Regards,
Alex.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Alex, what i meant was; I have no network-aware application to test with :-) (back then)
I can also report success with acucobol runtime v 6.1.0, and YES! network works!
i also tried an evaluation copy of Acucorp's acuconnect server and other clients found it...
(Now, there _are_ linux versions of these newer releases, i know, but our licence is for the OpenServer version)
I have dynamic /dev so i put
mknod /dev/socksys c 30 0
ln -s /dev/null /dev/X0R
mknod /dev/spx c 30 1
in rc.local
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have any troubles on Debian stable etch 4.0. Compiles OK, without any warnings, but when I run ./abi_ldr:
insmod: error inserting './lcall/abi_lcall.ko': -1 Operation not permitted
insmod: error inserting './coff/binfmt_coff.ko': -1 Unknown symbol in module
insmod: error inserting './xout/binfmt_xout.ko': -1 Unknown symbol in module
insmod: error inserting './svr4/abi_svr4.ko': -1 Unknown symbol in module
insmod: error inserting './cxenix/abi_cxenix.ko': -1 Unknown symbol in module
insmod: error inserting './sco/abi_sco.ko': -1 Unknown symbol in module
insmod: error inserting './ibcs/abi_ibcs.ko': -1 Unknown symbol in module
insmod: error inserting './isc/abi_isc.ko': -1 Unknown symbol in module
insmod: error inserting './solaris/abi_solaris.ko': -1 Unknown symbol in module
insmod: error inserting './uw7/abi_uw7.ko': -1 Unknown symbol in module
insmod: error inserting './wyse/abi_wyse.ko': -1 Unknown symbol in module
The same happens with version 3.3
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
iBCS-3.2
Logged In: YES
user_id=1111689
Originator: NO
Alex,
No change from iBCS-3.1 when executing an SCO Unix application. As was the case with the previous version, the database server process silently dies. Yet, the application runs just fine in single user mode. I will send you the execution trace.
-Robert
Logged In: YES
user_id=1739492
Originator: NO
On FedoraCore 6 with kernell 2.6.20.1 some old COBOL stuff ported
from AT&T UNIX works nice.
Thanks.
Logged In: YES
user_id=1004345
Originator: NO
works brilliantly on Zenwalk linux (linux-2.6.20.3) with:
acucobol242 for sco osr 5.x.x
micro focus cobol for unix (sco osr 5.x.x)
Have no idea how to get socksys ready for testing...
Good work!
Logged In: YES
user_id=1714746
Originator: NO
I have previously used implementations of Linux-ABI that are compiled into the kernel, and the applications I use require the following commands to be run for them to work:
echo 0x4100003 > /proc/sys/abi/defhandler_libcso || echo "Couldn't set default A BI handler - is /proc mounted?"
echo 0x4100003 > /proc/sys/abi/defhandler_lcall7 || echo "Couldn't set default A BI handler - is /proc mounted?"
Any idea how I can do the above using this patch? There is no /proc/sys/abi which I assume because this patch does not compile into the kernel like previous ones.
Regards,
Brad
Logged In: YES
user_id=1641112
Originator: YES
Hi Brad,
Original iBCS2 package did not provide dynamic personality flag handling - neither does iBCS3 (at the moment).
To resolve your problem try this:
1) Run "utils/elf_mark -5 PathToYourBinaries";
2) If "1)" does not help replace "PER_SVR4" and "PER_OSR5" strings in "lcall/lcall.c" with "PER_OSR5 | MMAP_PAGE_ZERO";
3) If "2)" does not help - wait for iBCS-3.3.
Regards,
Alex.
Logged In: YES
user_id=1641112
Originator: YES
Hi Robert,
Thanks for the Execution Traces provided. The problem you described appears since release 2.6.18 with introduction of VDSO. For "OpenSuse 10.2" insert "current->mm->context.vdso = VDSO_PRELINK;" above "out_free_file:" label into "coff/binfmt-coff.c".
Proper fix (applicable to all other kernel versions) will appear in iBCS-3.3.
Regards,
Alex.
Logged In: YES
user_id=1641112
Originator: YES
Hi "brente",
In order "to get socksys ready for testing" in "udev" environment do this:
......
mknod /lib/udev/devices/socksys c 30 0
chmod 666 /lib/udev/devices/socksys
init 6
......
Regards,
Alex.
Logged In: YES
user_id=1004345
Originator: NO
Alex, what i meant was; I have no network-aware application to test with :-) (back then)
I can also report success with acucobol runtime v 6.1.0, and YES! network works!
i also tried an evaluation copy of Acucorp's acuconnect server and other clients found it...
(Now, there _are_ linux versions of these newer releases, i know, but our licence is for the OpenServer version)
I have dynamic /dev so i put
mknod /dev/socksys c 30 0
ln -s /dev/null /dev/X0R
mknod /dev/spx c 30 1
in rc.local
Logged In: NO
i have a problem compiling it on debian etch:
when i call make i get the error /lib/modules/2.6.18-4-686/build not such file or directory
i create the directory build (/lib/modules/2.6.18-4-686 exists) and now if i call make as root i receive the following error:
pServer:~/ibcs# make
make -C /lib/modules/2.6.18-4-686/build M=/root/ibcs modules
make[1]: Entering directory `/lib/modules/2.6.18-4-686/build'
make[1]: *** No rule to make target `modules'. Stop.
make[1]: Leaving directory `/lib/modules/2.6.18-4-686/build'
make: *** [all] Error 2
someone can help me to understand this error?
Logged In: NO
Install the kernel-source
Logged In: YES
user_id=1138037
Originator: NO
I am running into similar issues with compiling on kubuntu.
Is there a "howto" for this new iBCS 3.x? I'd really appreciate one.
Logged In: YES
user_id=1641112
Originator: YES
For "Debian Etch" run:
apt-get install linux-headers-2.6.18-4-686
For "Ubuntu Edgy Eft" run:
apt-get install linux-headers-2.6.17-10-generic
Logged In: NO
I have any troubles on Debian stable etch 4.0. Compiles OK, without any warnings, but when I run ./abi_ldr:
insmod: error inserting './lcall/abi_lcall.ko': -1 Operation not permitted
insmod: error inserting './coff/binfmt_coff.ko': -1 Unknown symbol in module
insmod: error inserting './xout/binfmt_xout.ko': -1 Unknown symbol in module
insmod: error inserting './svr4/abi_svr4.ko': -1 Unknown symbol in module
insmod: error inserting './cxenix/abi_cxenix.ko': -1 Unknown symbol in module
insmod: error inserting './sco/abi_sco.ko': -1 Unknown symbol in module
insmod: error inserting './ibcs/abi_ibcs.ko': -1 Unknown symbol in module
insmod: error inserting './isc/abi_isc.ko': -1 Unknown symbol in module
insmod: error inserting './solaris/abi_solaris.ko': -1 Unknown symbol in module
insmod: error inserting './uw7/abi_uw7.ko': -1 Unknown symbol in module
insmod: error inserting './wyse/abi_wyse.ko': -1 Unknown symbol in module
The same happens with version 3.3