NetNews Usenet Archive 1992 #16/NN_1992_16.iso/spool/comp/sys/3b1/2936

Internet Message Format | 1992-07-23 | 3.6 KB

Path: sparky!uunet!spool.mu.edu!introl.introl.com!booth!roger
From: [e-mail] (Roger Abrahams)
Newsgroups: comp.sys.3b1
Subject: Re: What's in Development Set?
Message-ID: <[e-mail]>
Date: 24 Jul 92 03:54:22 GMT
Article-I.D.: booth.BrvK6o.BJF
References: <[e-mail]> <[e-mail]>
Organization: Private System
Lines: 68

In article <[e-mail]> [e-mail] (Don Nichols (DoN.)) writes:
<In article <[e-mail]> [e-mail] (Bob Hruska) writes:
<>
<>I have two different machines that I know little about.  For one, I
<>have the complete Foundation 3.51m set on floppy.  The other has
<>only the hard drive, but it contains the entire set of software
<>(foundation, development, text formatting)
<>
<>I would like to install the development set (along with foundation
<>3.51m) onto the other machine. My question is, what are all the
<>files in the foundation set I need to move?
<
<    More than any sane man would want to list. :-)
<
<    Probably the best way to do this is to make a full backup of the
<system which has the development set on floppies (have *lots* of
<pre-formatted floppies - you should probably modify the descriptor file in
</usr/lib/iv to make a 42-track floppy with 10 sectors/track so as to
<maximize the ammount which fits on each floppy.
<
<    Once you have the backup made, you can extract it on the other
<system.  This presupposes that there is little other than the foundation and
<development sets on the first box.  The backup software will *not* back up
<the foundation set - you should have a full set of diskettes with the
<foundation set for restoring the machine in case of a crash.  This I
<normally consider to be a big negative of the behavior of the backup
<software, but in this case, it works to your advantage, since you don't waste
<time copying what is already on the other system.
<
<    Good luck
<        DoN.
<
<--
<Donald Nichols (DoN.)     | Voice (Days): [phone] (Eves): [phone]
<D&D Data                  |  Email: <[e-mail]>
<I said it - no one else   |         <[e-mail]>
<    --- Black Holes are where God is dividing by zero ---

Well it has been some time since I had the "junk" files on my system which
appear in the "/usr/installed" directory, but as I remember, there was
a "Files" listing for (at least) the foundation set. This was found as
"/usr/installed/FND/Files".

These "listings" can be used as input to cpio to backup the required sets.
Note that the "listing" is relative, that is all the files are in the
form of "./dir/file", so that you need to be in "/" (root directory) to
actually find them.  So "cd /" and do:

    cat /usr/install/FND/Files |cpio -ocB >/dev/rfp021

Of course you can also copy it and edit the copy to remove the
leading ".".

The Development set files can be had by simply making a copy of the
associated uninstall script found in the "/usr/installed" directory
and editing it.  You might want to read the notes at the front and
add some files that are listed as not normally backed up.  The actual
file names are different on every system, depending on the order
installed as well as the date, but they fall in to the catagory of
having a long numeric string followed by ".un".

There is also a listing of the files contained in each set in the
manuals, but it would be pretty time consuming to type it in, and
these are probably prone to error if some files were added/removed
between the time the manuals were printed and the software was
sent out.

                    - booth![e-mail]