Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!swrinde!emory!hubcap!ncrcae!ofc!hl.rogers
From: hl.rogers@ofc.Columbia.NCR.COM (HL Rogers)
Newsgroups: comp.sys.ncr
Subject: Re: media portability issues
Message-ID: <602@ofc.Columbia.NCR.COM>
Date: 28 Sep 90 12:38:05 GMT
References: <1990Sep27.005958.4483@pilikia.pegasus.com>
Reply-To: hl.rogers@ncrcae.Columbia.NCR.COM (HL Rogers)
Organization: NCR E&M Columbia, Columbia, SC
Lines: 26

In article <1990Sep27.005958.4483@pilikia.pegasus.com> art@pilikia.pegasus.com (Art Neilson) writes:
<
<I have some in-house developed software I'd like to distribute across
<our Tower sites.  We have XP's, 400's, 600's, 650's, 500's and 700's.
<They run various OS versions 1.xx, 2.xx and 3.xx.  What are the portability
<concerns across these platforms ?  Some things which come to mind are
<media type, I suppose 45MB cartridges are readable across all boxes.
<What backup utility is most portable ? cpio, tar or dd ?  As for coding,
<is there a cpp define telling me which Tower release the machine is on ?
<What other things should I worry about ?
<-- 
<Arthur W. Neilson III		| ARPA: art@pilikia.pegasus.com
<Bank of Hawaii Tech Support	| UUCP: uunet!ucsd!nosc!pegasus!pilikia!art

Chapter 7 of the Release Definition for the 32/700 operating system
contains a fairly comprehensive treatment of software migration across
4 generations of the NCR TOWER (68000, 68010, 68020, 68030).  Chapter 5
provides a treatment of media migration.  This material is on-line in 
directory /etc/RELDEF.  Release definitions for all the TOWER operating
systems have similar sections to help with migration.

Good luck!
-- 
HL Rogers    (hl.rogers@ncrcae.Columbia.NCR.COM)
Me?  Speak for my company??  HA!
"Call 202/653-1800 for a good time!" - John Matrow, 1989