386 SVR3.0 to SVR3.1 conversion...

Mitchell Lerner mitchell at cadovax.UUCP
Sat Sep 10 07:23:17 AEST 1988


Problem: Converting a non-AT386 box from SVR3.0 to SVR3.1 using a
	 source update tape from AT&T.

Background information:

We are in the process of updating to SVR3.1, using a source update
tape from AT&T.  Our current SVR3.0 is a 386 port done for us by ISC.
The current policy of AT&T is to sell the 386 SVR3.1 source WITHOUT
either SUPPORT or DOCUMENTATION.  In the --> 3B2 <-- document "Unix
System V Release 3.1 Source Code Provision Release notes (select code:
305-566)", there is an "Appendix #B: Update List" and an "Appendix C:
Remove List" of files affected by the 3.1 update.  The names of these
3B2 files slightly resemble the files provided with the AT&T 386 SVR3.1
update tape.  However, the differences between this SVR3.1 3B2 document,
and the 386 AT&T SVR3.1 release tape, are major enough to make the above
mentioned document useless.

The new AT&T 386 SVR3.1 kernel makefiles are customized for AT&T's AT386
product, and no longer support any Multibus machines.  The list of
modified files and the list of deleted files, can only be derived
indirectly by examining the makefiles to determine which files are used
and which are not used.

The device "config" file in the i386/master.d/xxx/ directories has been
changed to "sdev" and "mdev" files.  The "mdev" files are one liners
from the pre-master.d "/etc/master" file, and the "sdev" are one liners
from the pre-master.d "config" file.  It seems that someone tried to go
back to the SIMPLE and EASY pre-master.d days - and almost made it!
These "mdev" and "sdev" files are processed by the new configuration
program "idconfig" - but unfortunately "idconfig" and other utilities are
customized for the AT386.

Our Solution: Struggle with it, think warm thoughts of AT&T, and use
	      modified versions of the old makefiles.

Questions:
    Who else has had similar experiences?

    Why was the system generation procedure changed from the simple
    two file (/etc/master and configuration) and library scheme,
    to the multiple file (master.d/xxx/*) and explicit link (stub.c)?

-- 
Mitchell Lerner -- UUCP:  {ucbvax,ihnp4,decvax}!trwrb!cadovax!mitchell
	Don't speak to him of your heartache, for he is speaking.
	He feels the touch of an ants foot.  If a stone moves under the 
	water he knows it.



More information about the Comp.unix.questions mailing list