Recommendations on upgrading from 504 to 505
Ken Wolff
upgrade, a fresh install) and I'd like to get opinions/recommendations
concerning ona few items from anyone willing to give them.
We're currently running VisionFS 1.2 on 504. Will 1.2 work under 505?
Which version should I use? I recall that with 504 there were two VisionFS
products, one worked, one did not. Do these same problems exist with the
505 distribution?
In regards to PPP, how many folks prefer the PPP implementation that comes
with 505 as opposed to the MST PPP product? Pros and Cons for each? We
currently are not using MST PPP. We have a dial up PPP connection to our
ISP that is up all the time. We do not provide any PPP dialin capabilities
(not to say we will not in the future).
I have the current rs505a supplement as well as all oss patches available
on the SCO FTP site. I've run a few installs on a test machine without any
problems. We use BackupEdge and have recovery disks ready in the event we
have to drop back to 504. I also have JP's 'savefiles' script (been using
this for quite a few upgrades - thanks JP). I ran a test upgrade on the
production machine a few months back with no BIG problems, but some of the
hardware on this machine is unique to this machine.
For example, we have a 3Com 3C59x network card in the production machine (I
can't remember the exact model without pulling the side panel). Has anyone
run into any problems with the 3Com drivers under 505?
We also have a ADAC RAID controller (from ALR). I know there are not many
of these out there running SCO, but has anyone installed 505 with an ADAC
controller and had any problems?
Are there any other "gotcha's" out there I need to be aware of?
Thanks!
------------------------------------------------------
Ken Wolff
MAXIMUS
Child Support Collection Center
http://www.maxinc.com
Phone: 616-957-4949 Ext: 111
Toll Free: 800-722-2338
FAX: 616-957-1614
------------------------------------------------------
Jean-Pierre Radley
|
| I also have JP's 'savefiles' script (been using
| this for quite a few upgrades - thanks JP).
You're welcome. But please get the latest version of savefiles from
ftp.jpr.com.
The script makes us of BackupEDGE's h flag:
h Restore the data in addition to the symbolic link. If this flag is set
and symbolic link is restored, AND if the symbolic link point to a real
file which is stored later on the archive, the real file is also
restored.
It literally means what it says; but in earlier versions of "savefiles",
I had included a few directories; the contents of those directories
didn't get saved if the directory itself was a symlink. /usr/spool/cron,
for example.
--
Jean-Pierre Radley <j...@jpr.com> XC/XT Custodian Sysop, CompuServe SCOForum
Ken Wolff
Tom Parsons
| We will be upgrading from OSR504 to 505 over Memorial Day weekend (not an
| upgrade, a fresh install) and I'd like to get opinions/recommendations
| concerning ona few items from anyone willing to give them.
That you can definitely get here <g>
| We're currently running VisionFS 1.2 on 504. Will 1.2 work under 505?
| Which version should I use? I recall that with 504 there were two VisionFS
| products, one worked, one did not. Do these same problems exist with the
| 505 distribution?
Yes. Any one of the three.
The only problem with VisionFS and 5.0.4 was that 2 different distributions
of VisionFS were included in the media kit and many didn't read the
documentation and tried to install the version that could not be licensed.
If you don't mind the considerable aggravation of maintaining 2 password
files and don't intend to print any document greater than 2872 characters
to a printer attached to a Win95 machine, then 3.0 is by far, the best
route to follow. Rumors are there will be a fix for the printing problem
but I suspect the dual passwords files will do disappear. The alternative
to dual password files is to wait until they fix the umask problem that
only occurs if you are not using encrypted passwords.
| In regards to PPP, how many folks prefer the PPP implementation that comes
| with 505 as opposed to the MST PPP product? Pros and Cons for each? We
| currently are not using MST PPP. We have a dial up PPP connection to our
| ISP that is up all the time. We do not provide any PPP dialin capabilities
| (not to say we will not in the future).
You paid your money, take your choice.
| I have the current rs505a supplement as well as all oss patches available
| on the SCO FTP site. I've run a few installs on a test machine without any
| problems. We use BackupEdge and have recovery disks ready in the event we
| have to drop back to 504. I also have JP's 'savefiles' script (been using
| this for quite a few upgrades - thanks JP). I ran a test upgrade on the
| production machine a few months back with no BIG problems, but some of the
| hardware on this machine is unique to this machine.
Why did you expect to have problems with the install?
| For example, we have a 3Com 3C59x network card in the production machine (I
| can't remember the exact model without pulling the side panel). Has anyone
| run into any problems with the 3Com drivers under 505?
No.
| We also have a ADAC RAID controller (from ALR). I know there are not many
| of these out there running SCO, but has anyone installed 505 with an ADAC
| controller and had any problems?
Never used one.
| Are there any other "gotcha's" out there I need to be aware of?
Install the distribution, rs505a, oss497b and oss600a in that order and
before you start configuring the installation.
--
==========================================================================
Tom Parsons t...@tegan.com Sysop, SCOForum-CompuServe
==========================================================================
Roger Cornelius
>
>Ken Wolff averred (on Sun, May 23, 1999 at 06:20:28PM +0000):
>|
>| this for quite a few upgrades - thanks JP).
>
>ftp.jpr.com.
>
>The script makes us of BackupEDGE's h flag:
>
> h Restore the data in addition to the symbolic link. If this flag is set
> and symbolic link is restored, AND if the symbolic link point to a real
> file which is stored later on the archive, the real file is also
> restored.
>
>It literally means what it says; but in earlier versions of "savefiles",
>I had included a few directories; the contents of those directories
>didn't get saved if the directory itself was a symlink. /usr/spool/cron,
>for example.
Here's a script I've been meaning to post for a long time. I use it
along with your savefiles script to help restore the state of my system
after an upgrade or restore. Depending on the options used, it produces
a list of symlinks on the root fs which point to objects on non-root
filesystems, a list of symlinks on non-root filesystems which point to
the root fs, or both. It will optionally produce the list in a form
suitable for execution by the shell.
Any comments or suggestions are welcome.
---- cut here ----
:
# @(#) findln: print list of symlinks pointing to/from root filesystem
# @(#) Assumes all filesystems are currently mounted
# @(#) Requires Gnu find
# @(#) 08/25/97 r...@tenzing.org
# The following can be useful in building a script to reconnect symlinks
# after an OS upgrade, etc..
# findln -nr | sed 's/^\(.*\) -> \(.*\)/ln -s \2 \1/'
# or
# findln -lnr
arg0=`basename $0`
# location of gnu find
FIND=/u/gnu/bin/find
if expr "`id`" : ".*(root) *" >/dev/null
then
: ok
else
echo "Must be root" >&2
exit 2
fi
usage() {
echo "Usage: $arg0 [-l] [-n] [-r]
where:
-n print symlinks on non-root filesystems pointing to root filesystem
-r print symlinks on root filesystem pointing to non-root filesystems
-l print in format suitable for execution by /bin/sh" >&2
exit 1
}
# find symlinks on root filesystem which point to non-root filesystems
do_root_fs() {
echo "\n#\n# symlinks on root filesystem\n#"
# create -lname command list for gnu find
pat=
for fs in $mountlist
do
case $fs in
/|/stand) # skip root and stand filesystems
;;
*) pat="$pat ${pat:+-o} -lname '${fs}/*'";;
esac
done
sh -c "$FIND / -mount \( $pat \) -printf '$printf_fmt'"
}
# find symlinks on non-root filesystems which point to / or /stand filesystems
do_nonroot_fs() {
echo "\n#\n# symlinks on non-root filesystems\n#"
# create -lname command list for gnu find
# don't match any symlink whose contents don't begin with '/'
pat="! -lname '[!/]*'"
for fs in $mountlist
do
case $fs in
/|/stand)
;;
*) pat="$pat ${pat:+-a} ! -lname '${fs}/*'";;
esac
done
# for each fs, search for symlinks to / or /stand
for fs in $mountlist
do
# skip root and stand filesystems
case $fs in /|/stand) continue ;; esac
sh -c "$FIND $fs -mount -type l \( $pat \) -printf '$printf_fmt'"
done
}
# default printf format
printf_fmt="%p -> %l\n"
do_root=false do_nonroot=false
while getopts lnr opt
do
case $opt in
l) printf_fmt="ln -s %l %p\n";;
n) do_nonroot=:;;
r) do_root=:;;
*) usage;;
esac
done
# skip /dev/cd* and /dev/hd[0-9]d (cdrom drives and dos partitions)
mountlist="`/etc/mount | sed '/\/dev\/cd/d; /\dev\/hd[0-9]d/d; s/ .*//'`"
$do_root && do_root_fs
$do_nonroot && do_nonroot_fs
---- cut here ----
--
Roger Cornelius r...@tenzing.org
Ken Wolff
>Ken Wolff enscribed:
>| I have the current rs505a supplement as well as all oss patches available
>| on the SCO FTP site. I've run a few installs on a test machine without any
>| problems. We use BackupEdge and have recovery disks ready in the event we
>| have to drop back to 504. I also have JP's 'savefiles' script (been using
>| this for quite a few upgrades - thanks JP). I ran a test upgrade on the
>| production machine a few months back with no BIG problems, but some of the
>| hardware on this machine is unique to this machine.
>
>Why did you expect to have problems with the install?
>
I expected problems with the ALR ADAC drivers. I had drivers for 502 and
ALR stated they would work fine with 504. They didn't. Once I got the 504
drivers from ALR, the controller worked fine. This time, I once again
called ALR (now Gateway) to see if the 504 drivers worked with 505, they
said yes. I didn't trust them. But they did work.
========================================================
Ken Wolff
MAXIMUS, Inc.
http://www.maxinc.com
Phone: 616-957-4949 ext. 111
FAX: 616-957-1614
========================================================