Browse Prior Art Database

Method for Software Installation and Apply Once Update from a Single Image

IP.com Disclosure Number: IPCOM000116835D
Original Publication Date: 1995-Nov-01
Included in the Prior Art Database: 2005-Mar-31
Document File: 2 page(s) / 104K

Publishing Venue

IBM

Related People

McBrearty, GF: AUTHOR

Abstract

Disclosed is a proposal for how installation images could be created and how they would be applied to individual machines. The disclosed proposes that the state of a fileset be taken into account when applying a fileset from an installation image. If a given fileset does not exist on a machine then the apply path will be that of a new installation, likewise if a given fileset does exist on a machine then the apply path will be that of an update.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Method for Software Installation and Apply Once Update from a Single
Image

      Disclosed is a proposal for how installation images could be
created and how they would be applied to individual machines.  The
disclosed proposes that the state of a fileset be taken into account
when applying a fileset from an installation image.  If a given
fileset does not exist on a machine then the apply path will be that
of a new installation, likewise if a given fileset does exist on a
machine then the apply path will be that of an update.

      This proposal calls for the packaging of install images and the
installation process to consider the state of the machine when
processing an install image.

      An install image is a conglomeration of files within some type
of Backup Format File (BFF).  Within a BFF are system files to be
extracted, configuration files that contain information about what
changes must be made to the running system, and apply only files that
are used during the apply and are then removed.  Installs and updates
work on a collection of related files known as a subsystem or fileset
and they are normally cumulative in nature, that is they contain all
changes to a subsystem or fileset since the last base line was
established.

      The packaging of install images will include information that
indicates the image can be used for both installation or updating the
fileset, and information that indicates what level the system files
or configuration changes where first introduced.  The apply process
will look at the information contained in the install image and
compare it to the current level of the machine.  From the comparison
of the machine's level and the information in the image the install
process can determine what subset of apply files and configuration
changes need to be performed, rather than over writing all the files
in the fileset.  If there are no versions of the fileset currently
applied then the fileset would apply all files from the fileset.

      When an install image is packaged two files would be added to
the the control files that ship with the image.  These files would
contain information about each requested apply and configuration
change since the initial level of this fileset.  These two files
would control what filesystem files are applied and control the
configuration changes needed for the running machine.  These files
could be in apply list format with a token identifying the level that
the last modification for a file or configuration change was
introduced.  The first file would control what files are restored on
to the system and the second would control the configuration changes
needed on the system.

      The first file will contain two tokens on a line identifying
the configuration change, and a second token indicating a level.  The
config token would be the first column, and the level token the
second column.  The config token would identify the configuration
cha...