Re: Migrating app from 3.2v4.2 to OpenServer 5.0.7?
From: Bela Lubkin (belal_at_sco.com)
Date: 05/13/03
- Next message: Bela Lubkin: "Re: server panic sco openserver 5.0.5"
- Previous message: Bela Lubkin: "Re: Alarm Call when using 'wall'"
- In reply to: Brian Lavender: "Migrating app from 3.2v4.2 to OpenServer 5.0.7?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 12 May 2003 20:57:35 -0400
[reposting article that didn't make it through the mail->news gateway]
Brian Lavender wrote:
> I have an orthodontics application running on 3.2v4.2 This is somewhat
> similar to another post, but a different approach.
>
> Should I:
>
> 1. Try to build another 3.2v4.2 box
> 2 Convert the app to 5.0.7
> 3. Run it under Linux-ABI
>
> I am thinking that there might be issues that could cause this to be
> somewhat difficult. Here's what I have. This is an old (still useful)
> terminal based application along with some dumb terminals and some
> logins through the TCP/IP network.
>
> The OrthoTrac system uses user ID's 200 through 240. It also has these
> users in the group called group which has a gid of 50. Are these
> uid/gid's reserved on the new version of Openserver?
They're still available.
> The app talks directly to the printer through the parallel port, and
> it looks like the app has /dev/slp1 hard coded into it in various
> areas. It also communicates with two serial based printers. The
> application talks directly to the device with its own drivers. Is
> /dev/slp1 still the device name of the printer on parallel port one?
> Am I going to have to tweak 5.0.7 to allow this direct device access?
> In fact, it seems wierd that this is the device name on 3.2v4.2,
> unless I got misinterpreted something somewhere.
Seems weird to me, too. SCO Unix never supplied a device named
/dev/slp1. The three "standard" parallel port addresses correspond to
devices /dev/lp0, lp1, lp2. /dev/slp1 might be linked from one of those
devices -- what are its major/minor numbers? Or, when you said "with
its own drivers" maybe you really did mean its own kernel device
drivers. In which case -- kernel device drivers should be compatible
from SCO Unix 3.2v4.2 to OpenServer 5.0.7.
> The app looks as if it forks, or calls another process that wants to
> write to the /dev/tty. In fact, the .profile for the ortho user
> executes a command that adds write privilege to all the /dev/tty*. Is
> /dev/tty* still the name of the pseudo terms in 5.0.7. I have had some
> problems with Linux's /dev/pts/* pseudo terminals.
OpenServer tty devices are still /dev/tty*. Largely for this exact sort
of reason -- apps exist which expect it so.
> I am almost thinking that maybe I ought to build/obtain a box that is
> running 3.2v4.2 and use it as a failover. The app is working fine.
> It's just that there is no other server available if this one fails.
>
> I am most familiar with Linux, so I have been working with the
> application on Redhat 8 using ABI. THe cobol runtime seems to run
> well, but there seems to be problems with the way the software is
> accessing the hardware. I haven't seen any segfaults, but I can't seem
> to get strace to follow child processes, so it's hard to see where
> the app fails under Linux.
I'm not qualified to help you with that...
3.2v4.2 might be difficult to install on current hardware. I'm not
really sure. You could probably find old/used/low spec hardware that
might work. On the other hand, bringing the app up on OSR507 shouldn't
be too bad, and will let you use much more easily obtained hardware.
>Bela<
- Next message: Bela Lubkin: "Re: server panic sco openserver 5.0.5"
- Previous message: Bela Lubkin: "Re: Alarm Call when using 'wall'"
- In reply to: Brian Lavender: "Migrating app from 3.2v4.2 to OpenServer 5.0.7?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
