Patch-ID# 101122-07
Keywords: pkginstall package  pkgadd pkgtrans sun4d sysmem
Synopsis: SunOS 5.2: fixes for the packaging utilities
Date: Dec/10/93

Solaris Release: 2.2

SunOS release: 5.2

Unbundled Product:

Unbundled Release:

Topic: SunOS 5.2: fixes for the packaging utilities, symbolic link removal

   NOTE: It is recommended that this patch be installed if other patches
         will also be applied since installpatch and backoutpatch use
         package utilities for installing or removing patch packages.

BugId's fixed with this patch: 1131708 1126855 1129521 1136784 1138068 1129208 1127771 1143144 1145943 1141621 

Changes incorporated in this version: 

Relevant Architectures: sparc

Patches accumulated and obsoleted by this patch: 101050-01

Patches which conflict with this patch:

Patches required with this patch:

Obsoleted by:

Files included with this patch:

usr/sadm/sysadm/bin/mkdtab
usr/bin/pkginfo
usr/bin/pkgmk
usr/bin/pkgparam
usr/bin/pkgproto
usr/bin/pkgtrans
usr/lib/libadm.a
usr/lib/libadm.so
usr/lib/libadm.so.1
usr/lib/libpkg.a
usr/sadm/install/bin/pkginstall
usr/sadm/install/bin/pkgname
usr/sadm/install/bin/pkgremove
usr/sbin/installf
usr/sbin/pkgadd
usr/sbin/pkgask
usr/sbin/pkgchk
usr/sbin/pkgmv
usr/sbin/pkgrm
usr/sbin/removef
/usr/sbin/prtconf

Problem Description:

This patch is being reissued to remove a symbolic link in the
SUNWcsu patch package

(from 101122-06)

1141621 pkgadd does not automatically eject the floppy


During multiple volume pkgmk, pkgadd and pkgtrans, the user is not given a
direct method whereby the floppy disk may be ejected.


(from 101122-05)

1145943 pkgtrans of more than 14 packages sometimes causes a core dump


A mathematical error in the pkgtrans code causes a core dump
if system memory is fragmented enough and there are more
than 14 or so packages to be transfered.


(from 101122-04)

1143144 pkgtrans reports incorrerctly that not enough space is available


The problem lies in the way on493 calculates file system size.
It is easily confused by remote file systems and sometimes
pkgtrans will fail to locate all the space available on the target
system. The fix involves multiple modifications over many files.
It is repaired in on1093. The accompanying jumbo patch brings
s493 packaging code up to the s1093 level as regards all features.


(from 101122-03)


The packaging utility 'pkgtrans' limited command lines as well as numerous internal buffers for command construction to 512 bytes. If pkgtrans was called upon to transfer a large number of packages by providing a list of packages on the command line or by use of the keyword 'all', these buffers would overflow leading to failure of the transfer.

If the utility were used with an Exabyte tape drive and the list of packages was longer than about 14, the data written to the tape would have a blocking factor incompatible with the facility used to read the tape.


(from 101122-02)

When more than one instance of a package exists on a system, (e.g.: a
server providing services to multiple architectures) the various
instances are distinguished from one another by appending a "dot serial
number" to the name of the package. For example, the first time the
Core Architecture is loaded on a machine, it is called SUNWkvm. If this
machine were providing a core architecture to two other types of
machines the other two packages would be "pkgadd'd" as SUNWkvm.2 and
SUNWkvm.3. If an entirely different package is added which requires
that the core architecture for a particular machine be present, the
packaging code should test each instance to see if one of them is the
required architecture and version established by the producers of the
new package. Currently, the packaging code will only test the prime
installation (e.g.: SUNWkvm), it will not even look at the other
instances. This patch fixes that problem and allows the packaging code
to correctly test dependencies by testing every instance of th


(from 101122-01)


When installing a package containing entities (files, directories,
devices, ...) which conflict with entities already installed on the
system, the operatior is given the option of installing the conflicting
files or leaving the original files in place. If the operator chooses
to leave the original files in place, the pkgadd utility will fail to
fill in all the blanks in the entry to be stored in the contents file.
This uninitialized entry, once detected, causes the utility to fail
and produce a core file.


(from 101050-01)

        Applications that use the sysmem() library routine in libadm will 
        hang on machines with exactly 2G of physical memory installed.


Patch Installation Instructions:
--------------------------------
Generic 'installpatch' and 'backoutpatch' scripts are provided
within each patch package with instructions appended to this section.
Other specific or unique installation instructions may also be
necessary and should be described below.

Special Install Instructions:
-----------------------------

none.