Patch-ID# 100904-03
Keywords: auto-install, filesys, pfinstall, disk
Synopsis: SunOS 5.1: filesys keywords don't work on systems with single disk 
Date: Aug/23/93

Solaris 2.1
 
SunOS release: 5.1
 
Topic: auto-install fails because filesys keywords don't work on systems 
       with a single disk
 
BugId's fixed with this patch: 1109781, 1126588

Relevant Architectures ('arch -k' values if kernel specific): all

Patches which may conflict with this patch: 

Obsoleted by: 

Files included with this patch: pfinstall, begin

Problem Description: 

	Bug 1109781 - filesys keywords don't work on systems with a single disk

	This is a bug in auto-install which causes auto-install to fail if
	the filesys keyword is used in the profile that drives the system
	installation and the system has only one disk.  Without the filesys
	keyword, there is no way to control filesystem sizes.

	Bug 1126588 - Jump Start installation fail with 100904-01 (J-Solaris2.1)

	This bug prevented localization packages from being explicitly
	included or excluded in auto-install profiles.

These are both bugs in the pfinstall program, a binary which exists only on 
the Solaris 2.1 installation CD-ROM.  Because the bug exists in a program that 
is on read-only media, special procedures must be used to enable the fixed
version of pfinstall.

This patch contains two files in addition to this README; a fixed version
of pfinstall and a sample "begin" script that may be used in the auto-install
rules file. The version of pfinstall included with this patch will
support the explicit inclusion and exclusion of specific localization
packages as described in the Solaris 2.1 documentation.


Patch Installation Instructions:

There are two ways to work around this bug.

First, if the user has copied the Solaris 2.1 CD onto a disk (using the
procedures documented in the "System Installation and Configuration Guide",
chapter 10, section "Optionally Copying the CD-ROM to Disk"), then the broken
version of pfinstall can be replaced directly on the image by the new version.

1) uncompress the new version of pfinstall
2) cd <cd-image>/export/exec/sparc.Solaris_2.1/sbin
3) cp <new pfinstall> .

Second, if the user is installing directly from the CD (either locally or
off of a server that has mounted the CD), then use the attached begin script
to force auto-install to use the fixed version of pfinstall.

1) uncompress the new version of pfinstall

2) Place the new version of pfinstall in the auto-install configuration
   directory.  This is the directory that contains the auto-install rules
   and profile files.

3) For each rule, the attached begin script must be used.  If the the rule
   already has a begin script, the contents of the patch begin script must be
   placed at the end of local begin script. Note that the names of the local
   begin scripts (if any) will vary and the begin script included with this
   patch will ne to be renamed accordingly.

4) Re-run the check program to enable the updated rules file with the new
   begin scripts.