At this time, the primary SCO related newsgroups are:
All of these are available as mailing lists if you do not have
access to News. See SCO
Administrative FAQ for more information.
Please- when posting, ALWAYS include version numbers and patches
you have applied. If it is at all relevant, include at least rough
harware info- like "32 mb ram, Scsi hard drive, Pentium 266", for
example. Don't ever paraphrase error messages- post the EXACT error
messages (see Messages). It's
never a bad idea to describe:
What your OS and version is:
Redhat Linux 7.1
Hardware info if applicable to your question
What you were trying to accomplish
Want to add default route
Want to change user's password
What you did
Logged in as root, typed "mkdev lp"
Ran "route add.."
What you expected to happen
I expected the route to be there when I rebooted
I expected the printer to work from Netscape
What actually happened
There's no route after reboot
Only root can print
Dirk Hart, a regular contributor to the SCO newsgroups, offers
this further advice:
How to ask a well formed question in
You may have noticed some people posting
questions on comp.unix.sco.misc are treated with disdain, even
abusively. This is invariably because the poster asked a poorly
All of the knowledgeable people replying to
messages spend their own time doing so, after having worked that
day and after having accreted years of knowledge and experience. In
spite of the rants directed at specific posters, the people in this
newsgroup are indeed helping others through goodwill.
When you post a question you are encouraged to
respect the knowledge, experience and goodwill of others in the
group by posting a well formed question.
The well formed question includes as much
relevant information as you can gather.
By all means state your SCO UNIX version. The
newsgroup comp.unix.sco.misc covers several different SCO operating
systems. If you aren't sure, you can find out using uname -X at a
Apropos of that:
Age of SCO products
3.2v4.2 1993 Jan-Mar
5.0.0 1995 May/June
5.0.4 1997 May/June
5.0.5 1998 May/June
5.0.6 2000 August
5.0.7 2003 February
6.0 2005 June
Tell the group what hardware you have, especially
if this is a hardware-related problem. If you're unsure, use
hwconfig -h at a shell prompt.
If the hardware configuration recently changed by
all means mention it.
Include the unedited error output including the
command used to generate this output. What you may not think is
relevant may be crucial to helping you. There is often summary
information at the beginning or ending of output which is
When you ask a question in the group you should
expect your replies in the group. Do not ask for help by email and
do not email those who give you help unless you have been
specifically asked to do so.
Don't forget that http://wdb1.sco.com/kb/showta should be the first place
you check for any problem. Also, do you have all the mandatory
patches and supplements your OS needs?
Another good idea is to use the power search page at
Put "comp.unix.sco.*" into the "Forum" box, and then search for
what you need. This can be very useful, and may save you from
asking a question that has been asked (and answered) hundreds of
Nothing that will ever stop anything from working; it's just a
To get rid of it, run "scoadmin" and fire up the Software
Manager. Note the "SCO System id" at the bottom of the screen.
Armed with that and your serial numbers, go to http://www.sco.com/%20support/registration,
answer a few questions, and return to the Software Manager with a
registration key for each serial number you have. Register the
products, and you won't see that nag message again.
The latest version of Openserver is 3.2v5.0.6 and Unixware is
7.1.3. To find out what your version is, try:
uname -X (most SCO versions)
uname -a (very old Xenix versions)
uname version (Unixware 7 and up only)
Don't be concerned by things like "5.0.6j" that you might see in
"custom". Also don't get confused by things like "RS506a (Release
Supplement 5.0.6a) " Your version is what uname -X says it is. Any
trailing letters are meaningless as far as deciding what patches to
Note how all the various departments at SCO, work harmoniously
together to produce an unworkable conglomeration. However, this is
considerably better than if any one department were in control. For
example, if marketting gained an upper hand, the product and possibly
the company would derive it's name from something something generated
by the allegedly pronounceable password generator and end in a
vowel. If engineering were in control, the company name would be
an acronym of other acronyms, and the version number would look
like an SNMP OID. Were support in control, it would probably be
something like "Unix, 05/01/2000 edition". While the current name
and numbers are a bit awkward, they are significantly better than
the potential alternatives.
Unixware was briefly renamed Open Unix 8- Jonathan Shilling
uname returns "OpenUNIX". For compatibility purposes you can get it to
return "UnixWare" by doing
$ SCOMPAT=5:7.1.2:UnixWare uname -s
It's back to Unixware now with 7.1.3.
There are almost always patches or
supplements that should be installed. Often these fix serious
problems and really are required for a stable system. Don't ignore
these. Check http://sco.com/support/download.html.
You can find out what patches are currently installed on your
system by running "custom" or Scoadmin->Software Manager. A way
to list them at the command line for modern releases (with minimal
information) is :
customquery listpatches | grep ' '
An important point about SCO that often astonishes people is
that the older (3.2v4.2) releases were often sold without
networking support- no TCP/IP. The newer 3.2v5.x versions can also
be purchased that way- it's called "Host"; the network version is
Transferring Disk Images from Windows
If you have downloaded patches, etc. to a Windows machine and
you have a network connection, of course you can just ftp the files
over. If you do not, you need to do it by floppy, and you will
immediately realize that most of the patches are disk images: they
are 1.44 MB and will not fit on a DOS floppy. There is a utility
(RAWRITE) that will solve this problem for you. It's SCO install CD's starting with 5.0.5 - it's called floppycp.exe there (you can access the SCO CD from Windows or any other OS).
See TA 105004
for more information.
Also see my Data Transfer
article for more general advice on transferring data.
The overall tool is "scoadmin". This runs in both character and
X screens. Many of the sub-tools it calls can be easily invoked
from the command line or found in the System Administration folder
in the gui.
You have graphical documention (not just man pages) included
with modern releases. On traditional SCO and Openserver releases,
this is the life ring icon on your desktop. On Unixware, it is
found in the launch bar at the bottom of the screen. All of this is
available on the web at http://www.sco.com/%20support/docs/.
Pages are also available on the web. Note that the presentation
of this page is not good, but if you skip to the bottom, you'll
find a place to just type in the command you are looking for
without having to guess which section it belongs in.
is a large collection of shareware and open source software. It is
not always the latest versions, but both source and binaries are
included, so it's often a good starting point. This is where you
can get Perl, Expect, Less, etc.
More recent releases include the Skunkware CD in the
distribution, so if you upgrade, you will get this. Recently SCO
has renamed Skunkware as OLSS, which stands for Open License
Something Source or something equally silly.
Of course you get man pages for all these things, but they may
not work until you do two things:
Install the GNU text processing tools from Skunkware
Modify /etc/default/man so that the MANPATH reads:
SCO includes Visionfs in
all modern versions up to 5.0.5, or you can get Samba from Skunkware.
Either of these let you put the SCO machine into the windows
Network Neighborhood, including the SCO printers. You can print to
Windows shared printers from Unix (see Visionfs Printing) and can even mount
Windows shared directories.