sbw@naucse.UUCP (Steve Wampler) (10/25/89)
I just got the 3.51 OS for my 3B1 (thanks guys, for making it
affordable). Of course, I'd like to bring it up, but there
are some nagging questions:
(1) The installation guide claims that the 3.5 development
set will not work with the 3.51 foundation set. True?
If it is true, then my 3.51 is going to sit on a shelf
until the development set can be gotten cheaply. If
it's only partially true, what part?
(2) I've got a fair amount of odds and ends out there
(pty and other lddrvs, patched iv, etc.) that seem
like they will be affected in going from 3.5 to 3.51.
Is there an easy way to handle this? Should I plan
on rebuilding all these things from source (gaaak -
I have gcc 1.36 - please let that pass through without
rebuilding!) I'd like to automate the process of
restoring those things I've added, any suggestions?
(3) I'm getting sick just thinking about all the floppies
that I'm going to need to back up the disk(s). Will
the following approach work:
I have a 2nd drive that still has around 30MB free on
it (two partitions: /usr/local and /usr/net). Rather
than back everything to floppy, can I copy a bunch
of stuff onto the 2nd disk? (Heck, I bet if I compress
as I go, I get get *everything* over there.) Ok,
I know I can do the copy, but will I be able to get
to it once the 3.51 foundation set is in place (i.e.
will I have to teach the system (via the enhanced
diagnotic disk) about the 2nd drive all over again -
can I avoid reformatting the 2nd drive if I do?)
Will just saving the iv description file in /usr/lib/iv
be sufficient? I'm assuming that I can 'hide' the
2nd drive from 3.51 easily enough during installation,
unless I have to run the diagnostic disk again...
(4) Since the stuff I want to save is spread all over
the place (for example, the improved 'rc' from ICUS
is in /etc) is there an easy way to restore those
things selectively (see question 2 above)?
Thanks for any help you folks can give!
--
Steve Wampler
{....!arizona!naucse!sbw}jcm@mtunb.ATT.COM (was-John McMillan) (10/26/89)
In article <1763@naucse.UUCP> sbw@naucse.UUCP (Steve Wampler) writes: : > (1) The installation guide claims that the 3.5 development > set will not work with the 3.51 foundation set. True? There _IS_ a serious problem, but NO ONE can recall what it is! (I never heard of it until now.) Some folks remember that they'd heard reports of trouble, while others say they they ran with that combination with no problems. (Great help... sorry.) Since 3.5 object codes work on a 3.51 system, the incompatibility would seem to lie in: a) replacing a 3.51 file with an older version while re-loading the 3.5 Dev.System -- thus crashing 3.51 codes -- OR b) building an object code using some file from 3.51 that is incompatible with the 3.5 pre-cursor -- thus creating un-runnable new object codes. The only file _I_ know that is common to both the OS set and the development set is "/bin/ld". Consider waiting for a clarification from someone: I'll ask around here tomorrow. : > (2) I've got a fair amount of odds and ends out there > (pty and other lddrvs, patched iv, etc.) that seem > like they will be affected in going from 3.5 to 3.51. : We're still loading drivers developed on 3.0. Expect fewer problems than you currently encounter. (Yes, it is POSSIBLE you have written something peculiar enough to require 3.5 -- but very unlikely.) > (3) I'm getting sick just thinking about all the floppies > that I'm going to need to back up the disk(s). Will > the following approach work: : The only problem I'd intuit is a need to alter your new (3.51) /etc files to mount your additional File Systems. (You may have the MOUNT information in a form that will survive the upgrade w/o ANY changes.) > (4) Since the stuff I want to save is spread all over > the place (for example, the improved 'rc' from ICUS > is in /etc) is there an easy way to restore those > things selectively (see question 2 above)? There are so many ways you can make up a long list. The challenge has always been to KEEP TRACK of the files you want to replace, not to replace them. You shouldn't have any problem accessing your 2nd disk File Systems (after you've mounted them) following the upgrade, so just make sure the files you want ARE THERE. jc mcmillan -- att!mtunb!jcm -- speaking for self... not THEM
lenny@icus.islp.ny.us (Lenny Tropiano) (10/26/89)
In article <1763@naucse.UUCP> sbw@naucse.UUCP (Steve Wampler) writes: |>I just got the 3.51 OS for my 3B1 (thanks guys, for making it |>affordable). Of course, I'd like to bring it up, but there |>are some nagging questions: .. You're welcome :-) |> |> (1) The installation guide claims that the 3.5 development |> set will not work with the 3.51 foundation set. True? ... Do you believe everything you read? :-) No, there were limited changed to the 3.51 dev set, just a few bug fixes here and there. Nothing is stopping you from installing the 3.5 dev set under 3.51 OS. AT&T just wanted the $$$ from new OS's and new dev sets :-) |> (2) I've got a fair amount of odds and ends out there |> (pty and other lddrvs, patched iv, etc.) that seem |> like they will be affected in going from 3.5 to 3.51. ... They should all work, without having to recompile them. Software was downward compatible... |> I'd like to automate the process of restoring those things |> I've added, any suggestions? ... The installation of 3.51 (to upgrade from 3.5) allows you to keep things like that intact on the hard disk. All your user installed programs will remain. Just modified programs will be installed on top of it. |> I have a 2nd drive that still has around 30MB free on |> it (two partitions: /usr/local and /usr/net). Rather |> than back everything to floppy, can I copy a bunch ... Sure, that's as good of a backup as any. Probably even more reliable than floppies :-) I do suggest a backup, it does aid in restoring things that will inevitably be overwritten with the installation of 3.51. |> to it once the 3.51 foundation set is in place (i.e. |> will I have to teach the system (via the enhanced |> diagnotic disk) about the 2nd drive all over again - ... No, 3.51, like 3.5 has all the hidden hooks for the 2nd drive. There is no need to format the 2nd drive again. |> (4) Since the stuff I want to save is spread all over |> the place (for example, the improved 'rc' from ICUS |> is in /etc) is there an easy way to restore those |> things selectively (see question 2 above)? |> ... Well I think most of the system profiles, passwd files, etc... are saved in a /u/SAVE3.5 and /u/CONV3.5. If you look on the floppy filesystem disk for 3.51, you will take notice of these references in /mnt/etc/profile (on the floppy). The file in /mnt/etc/convert/SPECIAL contains the files that are saved/converted, etc... I'd suggest making a backup, nevertheless... also you should be able to ascertain the files that changed since the installation by doing a: # find / -newer /etc/.installdate -print | xargs ls -ld Good luck! -Lenny -- | Lenny Tropiano ICUS Software Systems [w] +1 (516) 589-7930 | | lenny@icus.islp.ny.us Telex; 154232428 ICUS [h] +1 (516) 968-8576 | | {ames,pacbell,decuac,hombre,sbcs,attctc}!icus!lenny attmail!icus!lenny | +------- ICUS Software Systems -- PO Box 1; Islip Terrace, NY 11752 -------+
baur@venice.SEDD.TRW.COM (Steven L. Baur) (10/26/89)
From article <1684@mtunb.ATT.COM>, by jcm@mtunb.ATT.COM (was-John McMillan):
: In article <1763@naucse.UUCP> sbw@naucse.UUCP (Steve Wampler) writes:
:> (1) The installation guide claims that the 3.5 development
:> set will not work with the 3.51 foundation set. True?
: There _IS_ a serious problem, but NO ONE can recall
: what it is! (I never heard of it until now.)
How about incompatibility between the shared libraries?
I have never used 3.5 (only 3.51) but from my experience with dynamically
linked libraries on the SUN, version can be a problem.
--
steve baur@venice.SEDD.TRW.COM