OT: High End SCO System for Filepro

[John Esak]

> John Esak propounded (on Thu, Nov 10, 2005 at 03:52:38PM -0500):
> | We wanted to the very same thing. Our 6.0 SCO system and new server are
> | right there. We've x'ferred the data (but I mean just simple
> ftp the data,
> | you don't need to use filePro xfer... unless it *is* your way
> of moving the
> | files...)
>
> You used ftp to tramsfer the /appl/hierarchy?  Wouldn't it have been
> simpler to use rdist, let alone rsync if you had it?  At the very least,
> you would have preserved original permissions.
>
I don't believe I mentioned anything about the /appl hierarchy... but I did
use ftp to move the entire /appl/f* group of files.  All of which are
quickly put back to the proper permissions by running the fp perms script.

I know what rdist and rsyn are and how to use them. They were just not
called for in this 15 minute operation. I have no need to eer sync the data.
Once again  will do it when we move everything over for real. We are
actually going to take a different approach to these servers, since we
really don't want to buy a 2nd 64 or 128 user filePro, not even runtime. We
will close down the other server eventually and do something else with it.
Perhaps, a very fast and extremely useful 2003 server?  Might even buy a
filePro system for that, I have a 5 user ODBC at present, but it would
probably have to go up a little if do put anything useful on this box. But,
just for people being able to RDP to their own machines from home... this is
a really good use of this old box for us.


> | Anyway, we are waiting on a driver for a muli-modem board... but I'm
> | actually glad we have just been testing so far... since the
> SYSTEM problem
> | Ken mentioned a while back is there ever-looming as a huge
> hangup. (SYSTEM
> | calls to the shell are calling .../*95*/something/shell  instead of just
> | plain /bin/sh... and if you *need* regular /bin/sh, you are getting a
> | kornish shell... which may/will break your scripts.)

> What constructions are you using in Bourne scripts that break under
> Korn?
>
I have no idea... maybe none, maybe some, maybe just one crucial place that
will break when I'm not available. Can't trust such a huge thing *until* we
actually put #!/bin/sh at the head of the must-be thousands of local scripts
I've managed to gather since about 1984. Or, I would/will be much happier to
just buy/upgrade to the 6.0 version of filePro which _replaces_ the system
call that messes up with one that works as expected. Going to have to
upgrade anyway, we'll probably just wait until 6.0 filePro comes out.

> If the shell scripts start with #!/bin/sh, do OSR5 filePro binaries
> *still* run them using /u95/bin/sh instead of /bin/sh?

> --
> JP

No, I assume that would fix the problem (created by the ridiculous IMH) way
SCO just changed things without warning... all part of the relatively
"bait-and-switch" tactic of calling their new product OpenServer 6.0 instead
of Unixware 9.0 or whatever it would have been.

John