On Tue, 7 Mar 2006, Gabriel wrote:
HI, I WOULD LIKE TO KNOW IF RMCOBOL RUNS IN FREEBSD, THANKS.
GABRIEL
DON'T KNOW ABOUT ANY RMCOBOL, BUT THERE EXISTS open-cobol AND tinycobol
UNDER /usr/ports/lang.
PS - NO NEED TO SHOUT, BUT I TRY TO ANSWER IN
On Tuesday, 7 March 2006 at 18:47:25 -0500, Chris Hill wrote:
On Tue, 7 Mar 2006, Gabriel wrote:
HI, I WOULD LIKE TO KNOW IF RMCOBOL RUNS IN FREEBSD, THANKS.
GABRIEL
DON'T KNOW ABOUT ANY RMCOBOL, BUT THERE EXISTS open-cobol AND tinycobol
UNDER
On Tue, Mar 07, 2006 at 06:47:25PM -0500, Chris Hill wrote:
On Tue, 7 Mar 2006, Gabriel wrote:
HI, I WOULD LIKE TO KNOW IF RMCOBOL RUNS IN FREEBSD, THANKS.
GABRIEL
DON'T KNOW ABOUT ANY RMCOBOL, BUT THERE EXISTS open-cobol AND tinycobol
UNDER
From: Kris Kennaway [EMAIL PROTECTED]
Give the poor guy a break; he's a COBOL programmer, so he's used to
thinking and typing in all-caps :-)
And just think, both COBOL and AOL end in OL. I wonder if there is a
relationship?
Exit stage left FAST--{O,o}
On Tuesday 07 March 2006 15:56, Gabriel wrote:
HI, I WOULD LIKE TO KNOW IF RMCOBOL RUNS IN FREEBSD, THANKS.
HI, I WOULD LIKE TO KNOW IF YOU COULD POSSIBLY TURN OFF YOUR CAPS LOCK KEY. IT
MAKES IT SEEM LIKE YOU ARE SCREAMING AND NO ONE WANTS TO ANSWER A QUESTION
FOR SOMEONE WHO RANTS AND RAVES.
On Tue, Mar 07, 2006 at 04:33:05PM -0800, jdow wrote:
From: Kris Kennaway [EMAIL PROTECTED]
Give the poor guy a break; he's a COBOL programmer, so he's used to
thinking and typing in all-caps :-)
And just think, both COBOL and AOL end in OL. I wonder if there is a
relationship?
LOL? Or
I have used this in the past.
It's Cobol script for building web sites that r/w to flat files
and mysql database.
Works much Like php in the way it interfaces with native html code.
Their website is built using it as a demo of how fast it runs.
Can download version with mysql for testing.
On 3/7/06, Bob Hall [EMAIL PROTECTED] wrote:
...
I couldn't figure out how to fit ALGOL in there. Ain't life a PISTOL?
After that, I need a Tylenol...
--
Noel Jones
___
freebsd-questions@freebsd.org mailing list
Noel Jones wrote:
On 3/7/06, Bob Hall [EMAIL PROTECTED] wrote:
...
I couldn't figure out how to fit ALGOL in there. Ain't life a PISTOL?
After that, I need a Tylenol...
--
Noel Jones
... because the whole thing sounded like folderol. ;-)
Nonetheless, I'm not sure if I have
Dan Nelson writes:
In the last episode (Feb 04), Walter C. Pelissero said:
A side note. What is the impact of this IPC_64 flag on the FreeBSD
code? Can we ignore it, or does it mean that the Linux emulator is
outdated regarding this new flag?
Linux IPC_64 support was added to the
Dan Nelson writes:
In the last episode (Feb 04), Walter C. Pelissero said:
A side note. What is the impact of this IPC_64 flag on the FreeBSD
code? Can we ignore it, or does it mean that the Linux emulator is
outdated regarding this new flag?
Linux IPC_64 support was added to the
I tried linux_kdump (from ports) and things seem to clarify a bit.
I concentrated on acushare, which is the daemon that supervises
inter-process locking (locking on file access) and licence
verification. Whereas acushare seems to start properly, an attempt to
kill it through the recommended
In the last episode (Feb 03), Walter C. Pelissero said:
I tried linux_kdump (from ports) and things seem to clarify a bit.
I concentrated on acushare, which is the daemon that supervises
inter-process locking (locking on file access) and licence
verification. Whereas acushare seems to start
Dan Nelson writes:
If you do have sysvmsg loaded, you may have to start adding printfs in
linux_msgctl() to trace which call is failing and why.
Thanks. With your hints I made an interesting discovery that allowed
me to improve the situation dramatically.
In Linux's /usr/include/linux/ipc.h
In the last episode (Feb 04), Walter C. Pelissero said:
A side note. What is the impact of this IPC_64 flag on the FreeBSD
code? Can we ignore it, or does it mean that the Linux emulator is
outdated regarding this new flag?
Linux IPC_64 support was added to the 5.x tree over a year ago but
I realised that the ktrace log was rubbish; most of the syscalls names
were not properly mapped.
I tried to track down the exact spot were the Linux executable gets
the SEGV signal, running strace on a Debian system and comparing the
values passed to the system calls. Here is an extract:
Jerry McAllister writes:
[apparently the first message didn't get through; this is a repost]
Your previous post got through.
Probably the presumed answer is that no-one who saw it has
tried this or feels competent to respond.
Sorry for the duplicate. It wasn't the lack of answer but
[apparently the first message didn't get through; this is a repost]
Your previous post got through.
Probably the presumed answer is that no-one who saw it has
tried this or feels competent to respond.
You might some response if you could find a way to break the
problem down a little more and
18 matches
Mail list logo
