We use SCO 6's built-in functions to create a bootable CD and tape image.
Create Emergency CD
o identify and configure CD (as root)
cdrecord –scanbus
vi /etc/default/cdrecord - change ide to the cd drive
o Read/Write media must be formatted. Skip this step unless the CD is R/W
- cdrecord...
Unfortunately, it's probably because I've tried everything else... I just hate that error: C compiler cannot create executables. Kinda makes you wonder what you'd download a C compiler for if it couldn't compile executables!?!?
Building working gcc's for AIX4.# and SCO5.0.# was/is an adventure...
I just tried this today on a fresh (albeit ancient) SCO 5.0.4 install (VMWare server using http://aplawrence.com/OSR5/vmware_504.html) and rsync is working.
ftp ftp2.sco.com
cd /pub/skunkware/osr5/vols
Download and install:
autoconf-2.12-VOLS.tar
automake-1.4-VOLS.tar
gcc-98q2-VOLS.tar...
If those time stamps are the times that your logging in then you definitely have a problem with the license manager. I remember having problems with node-locked licenses and such on 5.0.5 but it was a long time ago. The comment at the end of this post rings a bell...
Remove /var/spool/lpd/lp_savin if it exists.
Remove 2 entries for lp_savin from /etc/printcap.
/usr/lib/lpshut
ps -ef | grep lpd (and/or lp) and kill the processes
/usr/lib/lpd
/usr/lib/lpsched
lpstat -p (to make sure it's gone)
It looks like there's a duplicate SCO license on the network...
Recreate or remove the lp_savin remote print queue
We've treated any problems with SCO "databases" with
authck -av
cd /etc/auth/system
mv ttys /tmp/ttys.bad
touch /etc/auth/system/ttys
chown auth:auth /etc/auth/system/ttys...
Booting Unix daily? That's just wrong...
The syntax is definitely correct. Try
0 4 * * 1-5 /etc/reboot
if it does the same thing then it's probably something in the server BIOS that is preventing it from coming back up.
SCO 5.0.7 and 6.0.0
cddev=`cdrecord -scanbus | grep CD-ROM | awk '{print $1}'`
cdrecord dev=$cddev -eject 2> /dev/null 1>&2
Non-writable drives will produce a warning message that can be ignored.
We had a problem when the Cisco PIX devices became more widespread. They don't like packets that come in "out of order" and caused the remote PC's connection to freeze. Our solution was to change the TCP/IP Send and Receive packet window to 32K, change the keepidle to 5 minutes instead of two...
Depends on the dumb terminal
Early Wyse Shift Setup
Later Wyse Shift Select
ADDS CTRL (or Shift) Scroll-Lock
IBM3151 CTRL Setup
Try right and/or left Shifts and CTRL keys.
We do this all the time using rcp. Create a user on each server who has access to the source and destination directories. Give it the same password on each server. Add each server to the other server's /etc/hosts.equiv. Create an rcp script and call it manually or from cron.
rcp -rp...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.