Path: nntp.gmd.de!news.rwth-aachen.de!news.rhrz.uni-bonn.de!
news.uni-stuttgart.de!news.belwue.de!delos.stgt.sub.org!delos.stgt.sub.org!
news.maz.net!news.ppp.de!xlink.net!howland.reston.ans.net!gatech!udel!
news.mathworks.com!news.duke.edu!godot.cc.duq.edu!nntp.club.cc.cmu.edu!
lobo.westmoreland.cc.pa.us!jackal.westmoreland.cc.pa.us!falensmj
From: falen...@jackal.westmoreland.cc.pa.us (Matt Falenski)
Newsgroups: comp.os.linux.development
Subject: Sco??
Date: 4 Mar 1995 06:18:41 GMT
Organization: Westmoreland County Community College
Lines: 15
Message-ID: <3j90o1$k6t@lobo.westmoreland.cc.pa.us>
NNTP-Posting-Host: jackal.westmoreland.cc.pa.us
X-Newsreader: TIN [version 1.2 PL2]
Could anyone provide me with the cost of SCO? Is it lots & lots or reasonable?
Any reason to run it over Linux? or Vice versa???
Thanks!
Matt
--
----------------------------------------------------------------------------
Matt Falenski Westmoreland County Community College Data Center WS
It's a perfect day for dreams come true, for thinking big, and doing
anything you want to do.
----------------------------------------------------------------------------
Path: nntp.gmd.de!news.rwth-aachen.de!news.rhrz.uni-bonn.de!
RRZ.Uni-Koeln.DE!uni-duisburg.de!zib-berlin.de!news.mathworks.com!
uhog.mit.edu!news.mtholyoke.edu!jbotz
From: jb...@mtholyoke.edu (Jurgen Botz)
Newsgroups: comp.os.linux.development
Subject: Re: Sco??
Date: 5 Mar 1995 21:04:23 GMT
Organization: Mount Holyoke College, MA, USA
Lines: 23
Message-ID: <3jd90n$sal@mudraker.mtholyoke.edu>
References: <3j90o1$k6t@lobo.westmoreland.cc.pa.us>
NNTP-Posting-Host: orixa.mtholyoke.edu
In article <3j90o1$...@lobo.westmoreland.cc.pa.us>,
Matt Falenski <falen...@jackal.westmoreland.cc.pa.us> wrote:
>Could anyone provide me with the cost of SCO? Is it lots & lots or reasonable?
Lots and lots, and C compiler and NFS and such are all options for
lot sand lots more.
>Any reason to run it over Linux?
No.
>or Vice versa???
Yes!
8-)
Seriously, Linux is vastly superior to SCO.. SCO is (or at least until
recently was) still based on SVR3 which is nearly a decade old. The
only reason anyone would want to run SCO is because they feel safer if
they shell out some real bucks for their OS... kinda like having a
rabbit's foot on your keychain or something... ;-)
Path: bga.com!news.sprintlink.net!EU.net!news.eunet.fi!ksv!jarmo
From: ja...@ksv.ksvltd.fi (Jarmo Raiha)
Newsgroups: comp.os.linux.development
Subject: Re: Sco??
Date: 11 Mar 95 18:28:39 GMT
Organization: KSV Instruments ltd. (Finland)
Lines: 24
Message-ID: <jarmo.794946519@ksv>
References: <3j90o1$k6t@lobo.westmoreland.cc.pa.us>
<3jd90n$sal@mudraker.mtholyoke.edu>
NNTP-Posting-Host: ksvltd.fi
jb...@mtholyoke.edu (Jurgen Botz) writes:
>In article <3j90o1$...@lobo.westmoreland.cc.pa.us>,
>Matt Falenski <falen...@jackal.westmoreland.cc.pa.us> wrote:
>>Could anyone provide me with the cost of SCO? Is it lots & lots or reasonable?
>Lots and lots, and C compiler and NFS and such are all options for
>lot sand lots more.
Yes.
>>Any reason to run it over Linux?
>No.
Yes. It has msdos cross compiler. Still a better platform to do
msdos compiles than msdos itself.
I have to maintain our msdos software and that is the only thing
why I keep SCO still hanging around. Althoug moved into a junk 386sx.
If just linux could run SCO devsys I could junk the rest of SCO
finally and forever. Alternatively , if dosemu could run MSDOS compilers
transparently inside linux , it would put an end to our SCO too.
>Seriously, Linux is vastly superior to SCO.. SCO is (or at least until
Yes.
Jarmo
Path: bga.com!news.sprintlink.net!howland.reston.ans.net!newsjunkie.ans.net!
newstf01.news.aol.com!newsbf02.news.aol.com!not-for-mail
From: dyf...@aol.com (DyfetT)
Newsgroups: comp.os.linux.development
Subject: Re: Sco??
Date: 11 Mar 1995 14:39:15 -0500
Organization: America Online, Inc. (1-800-827-6364)
Lines: 14
Sender: r...@newsbf02.news.aol.com
Message-ID: <3jsu93$7ep@newsbf02.news.aol.com>
References: <jarmo.794946519@ksv>
Reply-To: dyf...@aol.com (DyfetT)
NNTP-Posting-Host: newsbf02.mail.aol.com
>Yes. It has msdos cross compiler. Still a better platform to do
msdos compiles than msdos itself.
>I have to maintain our msdos software and that is the only thing
>why I keep SCO still hanging around. Althoug moved into a junk 386sx.
>If just linux could run SCO devsys I could junk the rest of SCO
>finally and forever. Alternatively , if dosemu could run MSDOS compilers
>transparently inside linux , it would put an end to our SCO too.
Strange, I have similar needs for having SCO around. I am hoping the SCO
dev tools (command line compilers/linker/etc) could run under iBCS
emulation so that, with a little clever file system mapping, and perhaps a
script file or two, I could once and for all scrap that 300 meg millstone
from my other system. In fact, that was originally going to be my weekend
project before '95 became available on my favorite ftp site :).
Newsgroups: comp.os.linux.development
Path: bga.com!news.sprintlink.net!pipex!uunet!in1.uu.net!virtech!aib.com!
not-for-mail
From: e...@aib.com (Eric Youngdale)
Subject: Re: Sco??
Message-ID: <3jv532$4oa@andante.aib.com>
Lines: 34
Sender: n...@aib.com (Usenet/NetNews Administrator)
Nntp-Posting-Host: andante.aib.com
Organization: AIB Software Inc
References: <jarmo.794946519@ksv> <3jsu93$7ep@newsbf02.news.aol.com>
Date: Sun, 12 Mar 1995 15:47:46 GMT
In article <3jsu93$...@newsbf02.news.aol.com>, DyfetT <dyf...@aol.com> wrote:
>>Yes. It has msdos cross compiler. Still a better platform to do
>msdos compiles than msdos itself.
>>I have to maintain our msdos software and that is the only thing
>>why I keep SCO still hanging around. Althoug moved into a junk 386sx.
>>If just linux could run SCO devsys I could junk the rest of SCO
>>finally and forever. Alternatively , if dosemu could run MSDOS compilers
>>transparently inside linux , it would put an end to our SCO too.
>
>Strange, I have similar needs for having SCO around. I am hoping the SCO
>dev tools (command line compilers/linker/etc) could run under iBCS
>emulation so that, with a little clever file system mapping, and perhaps a
>script file or two, I could once and for all scrap that 300 meg millstone
>from my other system. In fact, that was originally going to be my weekend
>project before '95 became available on my favorite ftp site :).
I am told that one of the commercially available SCO applications
(someone from the company that did this can stand up and take credit,
if they want), is using SCO development tools under Linux to develop
their SCO application. It is an X based application, and yes, they had
a spare license so they were not breaking any rules by doing this. As
I recall, they had a /sco directory tree under which they did a chroot
so as to be able to transparently build their application.
As a general rule, things like compilers, linkers, etc, do not
really tax the iBCS2 stuff very heavily. For the most part, all they
do is file open/close/read/write/seek/stat, which we have been able
to handle quite easily.
-Eric
--
"The woods are lovely, dark and deep. But I have promises to keep,
And lines to code before I sleep, And lines to code before I sleep."
Newsgroups: comp.os.linux.development
From: ja...@purplet.demon.co.uk (Mike Jagdis)
Path: bga.com!news.sprintlink.net!uunet!in1.uu.net!pipex!
peernews.demon.co.uk!purplet!jaggy
Subject: Re: Sco??
Organization: FidoNet node 2:252/305 - The Purple Tentacle, Reading
X-Posting-Host: purplet.demon.co.uk
Date: Tue, 14 Mar 1995 20:04:00 +0000
Message-ID: <826.2F6617A6@purplet.demon.co.uk>
Sender: use...@demon.co.uk
Lines: 25
* In message <3jsu93$...@newsbf02.news.aol.com>, DyfetT said:
DD> Strange, I have similar needs for having SCO around. I am
DD> hoping the SCO
DD> dev tools (command line compilers/linker/etc) could run
DD> under iBCS
DD> emulation so that, with a little clever file system mapping,
DD> and perhaps a
DD> script file or two, I could once and for all scrap that 300
DD> meg millstone from my other system.
Check out the VSYS bits in the iBCS release archive. It creates "virtual"
systems by NFS mounting the target system's filesystems (but you could just
copy them into place for a more permanent set up). You can then run commands
under the virtual system. For instance "/OS/bin/sco -ksh" chroots in to my
virtual SCO system and runs a login shell so I can use it as if I were
actually there. "/OS/bin/sco cc -o prog prog.c" compiles a program using the
SCO development system.
I've done real work (building Informix 4GL (compiled) applications) like
this - it used to be a good way of finding problems in iBCS but now it just
works :-( (or :-) depending on your pointof view!).
Mike