dmb@morgoth.UUCP (David M. Brown) (12/22/87)
I'm helping a friend evaluate proposals for a financial system for his
small sales and marketing company. One proposed system included the
Real World (TM) software package running under the Cobol Runtime
System and Xenix on a Unisys 500/12.
I have read most of the spex on the other stuff, but am curious about
Xenix. Some questions:
1. How complete a subset of Unix is Xenix? I'm thinking of
utilities and system management software. He can probably do without
awk, sed, etc. But, for example, how easy are the dump and restore?
2. Are all the standard signals supported? In particular,
can you really stop and start jobs just like real Unix? Is it a true
multi-user system or some sort of approximation?
3. What size of swap space partition would you recommend?
How big is the kernel? What kind of performance drop is experienced
under various configurations of RAM and other resources? What is the
most necessary resource (other than more RAM) to increase performance?
4. What else should I know?
I expect the answers to some of these questions are machine-dependent.
If so, please assume the machine is an IBM-AT compatible with an 80286
(is that redundant?).
Any help at all would be greatly appreciated. Thank you.
David Brown
{harvard | ll-xn | mirror}!adelie!morgoth!dmb
ICF Technology, Robinson Plaza II, Suite 200, Pittsburgh, PA 15205
(412) 788-9200
WE CHALLENGE our traditions
BECAUSE we believe
TRUTH without questioning
IS FALSEwnp@killer.UUCP (Wolf Paul) (12/29/87)
In article <461@morgoth.UUCP> dmb@morgoth.UUCP writes: > ... > 2. Are all the standard signals supported? In particular, >can you really stop and start jobs just like real Unix? Is it a true >multi-user system or some sort of approximation? > Well, the BSD v. ATT controversy rears its head again. Stopping and starting jobs is a feature of Berkeley UNIX and not supported on most AT&T versions (I heard that SV.3 ksh supports it, but nothing prior to that). As far as I understand, Xenix supports all STANDARD signals, but "STOP" is not a standard signal, and no, Xenix does not support it. But it is true mult-tasking, multi-user, and you can put jobs in the background by starting them with '&' on the commandline. Wolf Paul ihnp4!killer!dcs!wnp
csch@coma.UUCP (Clemens Schrimpe) (12/31/87)
In article <2604@killer.UUCP> wnp@killer.UUCP (Wolf Paul) writes: >Well, the BSD v. ATT controversy rears its head again. Stopping and starting >jobs is a feature of Berkeley UNIX and not supported on most AT&T versions >(I heard that SV.3 ksh supports it, but nothing prior to that). Right! - but SCO Xenix (we're running 2.2.1) supports so called "shell-layers", which is some mixture of a special line-discipline and pseudo-ttys. (I've seen them on other SYS V installations also, so I think it's not a special SCO-feature) They allow you to handle up to eight processes, each of which can be stopped, continued, killed, "put in background" and so far. I'd like BSD-like stop-and-go features more than this, but it's more than NOTHING :-) happy new yearishness ]:-} Clemens UUCP: csch@tmpmbx = {unido|pyramid}!tmpmbx!csch BITNET: CSCH@DB0TUI6 TELEX: 186672 net d TELETEX: 17186672=net d PHONE: +49-30-332 40 15 BTX: 0303325016-0003
mike@gen1.UUCP (Mike CLARKSON) (01/01/88)
In article <2604@killer.UUCP> wnp@killer.UUCP (Wolf Paul) writes: > >Well, the BSD v. ATT controversy rears its head again. Stopping and starting >jobs is a feature of Berkeley UNIX and not supported on most AT&T versions >(I heard that SV.3 ksh supports it, but nothing prior to that). > I hate to jump into anything that would touch off a round of Bsd vs. SysV flames, but... I've been born and raised on Bsd for a number of years, and only recently have been using SysV (SCO Xenix 2.2). Although SysV doesn't have Berkeley job control, it does have something very nice called shell layers. Actually, it's so nice that at this point I'm having trouble deciding which one I like better. Shell layers allow you to run multiple concurrent jobs, switching back and forth, having them block on output or just have them all output to the screen. Needless to say, the interrupt character to get the shell layer monitor's attention is ^Z. Note that this is under SysV.2 not 3, and I find it to be a very good way of managing concurrent interactive processes. Bsd types who haven't used shell layers should look at the Xenix man pages for shl and give them a try. Mike Clarkson York University, utgpu!yunexus!carr!mike
fyl@ssc.UUCP (Phil Hughes) (01/07/88)
In article <323@gen1.UUCP>, mike@gen1.UUCP (Mike CLARKSON) writes: > flames, but... I've been born and raised on Bsd for a number of years, and > only recently have been using SysV (SCO Xenix 2.2). Although SysV doesn't > have Berkeley job control, it does have something very nice called shell > layers. I have played with shell layers but what I want is the equivalent of the multiple terminals you can get at the console. Is there a way to get shl started automatically when I log in? -- Phil Hughes, SSC, Inc. P.O. Box 55549, Seattle, WA 98155 (206)FOR-UNIX uw-beaver!tikal!ssc!fyl or uunet!pilchuck!ssc!fyl or attmail!ssc!fyl