If you are just starting with SCO, or just need to learn enough to get the system transferred to Linux or whatever, there are a number of basic things you need to know (if you are just starting with Unix, see New to Unix) See Getting near to the end? also.
.MUCH OF THE MATERIAL AT THIS SITE IS RELATED TO SCO OSR5, Linux and Mac OSX. SOME of what you'll find here is useful if you are running Unixware, Solaris, or whatever, but if your specific OS is not specifically mentioned, take whatever you read as being POSSIBLY WRONG FOR YOU (note that there is plenty of general Unix, Linux and Mac OS X stuff here too).
Caldera bought the Unix side of SCO in 2001. There have been problems with links that point to SCO web pages. Many have been corrected, but if you have trouble, http://www.caldera.com/company/scofind.html may help.
In August 2002, Caldera has renamed itself "The SCO Group" and some of the old www.sco.com links work again.
Some of the information below is outdated. SCO web site links are often broken or not working. SCO itself may be heading for financial problems. See Getting near the end?
Also see SCO FAQ
Some things commonly used on SCO that you might not know about (read the man pages):
Many people ask about things like "which" or command history, etc. Those are features of SHELLS, not operating systems.
Unlike Linux distributions, SCO currently doesn't provide any way that you can download the OS: see http://shop.caldera.com/caldera/offers/ to get an inexpensive CD.
Recently, "free SCO" has been discontinued. We hope that will change and that a free or low cost version will be available again.
You can buy a 60 day evaluation version for $99.00.
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:
Dirk Hart, a regular contributor to the SCO newsgroups, offers this further advice:
How to ask a well formed question in comp.unix.sco.misc
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 formed question.
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 shell prompt.
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 especially useful.
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://www.sco.com/ta should be the first place
you check for any problem. Also, do you have all the mandatory patches
and supplements your OS needs? If you don't know, see Current Patches or SCO's FTP Site and get them.
Another good idea is to use the power search page at Dejanews:
groups.google.com
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 times before.
For even more advice on asking questions, see Eric Raymond's "How To Ask Questions The Smart Way"
There are several SCO related FAQS The most comprehensive for troubleshooting is My FAQ.
I also suggest the Search Engine for my pages.
Nothing that will ever stop anything from working; it's just a nag.
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.caldera.com/support/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.
Also see How To Ask Questions The Smart Way
The latest version of Openserver is OpenServer 6.0.0, Unixware is 7.1.4. To find out what your version is, try:
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 install, etc.
Unixware was briefly renamed Open Unix 8- Jonathan Shilling says:
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.
Some people have an odd attitude toward these because sometimes patches cause more problems than you have now. But it's reallysilly to hesitate about an important patch that has been out for months or years. If it had defects, someone has already found themby now, so it's very unlikely to cause problems. So if you are running an earlier version of your OS and don't have the recommended patches, you are just being foolish. You are probably being foolish even if the patch was just posted yesterday.
Check ftp://ftp.sco.com/README.OSR5.Supplements for Open Server patch recommendations and ftp://ftp.sco.com/README.UW7.Supplements for recent releases of Unixware. Unfortunately there's nothing equivalent for the earlier releases (there are patches, just no comprehensive place to find out what you need). The http://www.caldera.com/support/ page is also a good starting point for general SCO support related issues.
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 ' '
The latest video card and network drivers can be found at ftp://ftp.sco.com/pub/drivers/. Check to see if your card is listed here.
Year 2000 information is tracked on this page.
For specific packages within SCO OS's, see Jeff Liebermans's Version Guide
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 "Enterprise".
The Host versions CAN do ppp.
(When adding a pci Network card to SCO OSR5, the card should just "pop up" with netconfig - you shouldn't get a whole list of cards to choose from. If it does not, you probably do not have the right driver and should visit ftp://ftp.sco.com/pub/drivers/ to get it. Also use "hw -r pci" to see what is actually installed.)
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. Download it from ftp://ftp.caldera.com/TLS/tls096.zip. See http://aplawrence.com/cgi-bin/ta.pl?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.
There are a number of SCO related FTP and Web sites.
The most comprehensive list of ftp sites was originally produced by Bela Lubkin and is now maintained by Andrew Smallshaw. See Andrew Smallshaw's FTP List . One of the largest sources for compiled SCO binaries is Celestial Systems.
Jeff Liebermann's SCO Page has a lot of very useful technical tips. I have a large number of introductory articles at my Unix Articles pages.
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.caldera.com/support/docs/.
On-Line Man 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.
You can get printed documentation at extra charge. Amonra Insight has a nice Q-File SCO OSR5 Quick Reference Guide.
Finally, you will want to know about http://ftp.caldera.com/ta, which is a trouble-shooting search engine covering all SCO products.
Jeff Liebermann's SCO Page puts a lot of these tools and other links together on one convenient page.
See Links for other SCO resources, and of course if you are not already aware of the Articles here, you'll find those to be an excellent introduction to many topics.
Skunkware (http://www.caldera.com/skunkware/) 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:
MANPATH=scohelp:/usr/man:/usr/local/man
Sometimes Skunkware packages have dependencies: see Library Cross Reference
There are some good books you might consider: for OSR5 I'd recommend Sco Companion by Jim Mohr: /Books/companion.html and for Unixware, Gene Henriksen's /Books/uw7sysadm.html).
I have a small list of other SCO Specific Books.
See Magazines
See Consultant List.
Of course, I also am a SCO and Linux consultant. See Rates and Services.
SCO maintains security information at
| SCO's Security Pages |
| SCO Security Tools |
| SCO's SSE ftp site |
| SCO's Security Enhancements |
You'll find other security related information at my Security articles
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.
SCO provides a NAT and IPFILTER tool: see IPFILTER
This is built in to current release and is available as TLS711 for older versions.
Because, by default, SCO systems set interrupt to the DELETE key, not CTRL-C.If you find that unbearable, you can easily change it; for example,
stty intr ^C
will change your interrupt on Bourne or Korn shells. In this example, you
actually type CTRL-C; if you are in vi adding it to your .profile, type
CTRL-V and then CTRL-C
© June 1999, June 2000, February 2001 Anthony Lawrence. All rights reserved.
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
/newtosco.html copyright Tony Lawrence All Rights Reserved
| Views for this page | ||||
|---|---|---|---|---|
| Today | This Week | This Month | This Year | Overall |
| 38 | 124 | 547 | 10,614 | 113,108 |
Tue May 3 12:10:55 2005 about the interrupt anonymous
pls how can I return to the prompt ( login: ) on a tty at my server
if a client turn his terminal or his pc off.
I tried at /etc/gettydefs the variable HUPCL but without any result
/>
thanks for response
Tue May 3 15:40:23 2005 TonyLawrence
You need to use the modem control device.
Add your comments