installupdate man page on Tru64

Man page or keyword search:  
man Server   12896 pages
apropos Keyword Search (all sections)
Output format
Tru64 logo
[printable version]

installupdate(8)					      installupdate(8)

NAME
       installupdate - Invokes the Update Installation procedure

SYNOPSIS
       /sbin/installupdate [-nogui] [-u] {ris_server:}

       /sbin/installupdate [-nogui] [-u] {[cdrom_device] [cdrom_mount_point]}

OPTIONS
       On  systems  with  graphics  capability,	 this option invokes the text-
       based, menu driven user interface rather than the graphical user inter‐
       face.  Invokes an unattended Update Installation. Unattended means that
       barring any problems during the Update Installation (such as file  type
       conflicts,  insufficient	 disk  space,  and blocking layered products),
       there is no user interaction required. This option builds a kernel with
       all  kernel  components and does not provide the opportunity to archive
       obsolete files before the Update Installation process deletes them.

	      If the analysis phase of the update  discovers  file  type  con‐
	      flicts,  insufficient  disk space, or blocking layered products,
	      the update process stops and prompts you to correct the  problem
	      or problems before the update resumes.

DESCRIPTION
       An  Update Installation updates the  base operating system software and
       the worldwide language support (WLS) software to the next released ver‐
       sion  of	 the operating system on a single system. The Update Installa‐
       tion preserves user files, data files,  print  and  network  configura‐
       tions,  user accounts, and any other system setup and customization you
       may have done.

       Cluster software is updated by a process called a rolling  upgrade.  An
       Update  Installation  is	 one  of  several  stages in a cluster rolling
       upgrade.	 The cluster rolling upgrade process is documented in the Tru‐
       Cluster Server Cluster Installation manual and in clu_upgrade(8).

       An  Update  Installation	 does not update layered products, but you can
       still perform an Update Installation if your system is  installed  with
       layered	products.  Some layered products operate properly with the new
       version of the operating system and others must be reinstalled  with  a
       version	that  is compatible with the new version of the operating sys‐
       tem. You are notified accordingly. You can delete these products during
       the  Update Installation process and then reinstall them on the updated
       system.

       There are two distribution methods for an Update Installation: From the
       operating  system  CD-ROM  (from a mount point or CD-ROM device) Over a
       network connection to a Remote Installation Services (RIS) server  that
       is serving the most recent version of the operating system

       The Update Installation is performed from single-user mode. You must be
       superuser or the user root to bring a system down to single-user	 mode.
       Do not boot to single-user mode to perform an Update Installation.

       Whether you are using CD-ROM or RIS, the Update Installation process is
       started by entering the /sbin/installupdate command  from  the  command
       line.

       The functions performed during the Update Installation process include:
       Detecting and deleting obsolete system files, files  that  were	previ‐
       ously  shipped  with  the older version of the operating system but are
       not in the new release. You have the option to archive these files to a
       file  name  of  your  choice  before  they are removed from the system.
       Checking for file types that you have changed since the last version of
       the  operating  system.	Certain file type conflicts prevent the Update
       Installation from continuing, and  you  must  resolve  these  conflicts
       before you can restart the Update. This feature preserves the integrity
       of the new operating system about to be installed.  Checking  for  ade‐
       quate free disk space to ensure the Update Installation has enough room
       for temporary processing and there is enough disk  space	 for  the  new
       software subsets that were introduced in the new version of the operat‐
       ing system.  Checking for installed layered products that  may  not  be
       compatible with the new version of the operating system. The product or
       products may need to be reinstalled later.  Saving unprotected  custom‐
       ized  files  to	files  with extensions to preserve customizations that
       were made to unprotected system files.  These files are not expected to
       be  modified  and are not merge protected from the Update Installation,
       therefore they are saved with the extension.  Performing merges of pro‐
       tected  system  files.  These are files that are shipped as part of the
       operating system that are expected to be customized (for	 example,  the
       /etc/hosts  file).  These  files	 are merge protected, which means that
       user customizations are preserved and newly introduced functionality is
       merged  into  the  already customized file.  Using the setld command to
       load new software subsets.  Subsets previously installed are updated as
       well  as any new mandatory subsets that were introduced in the new ver‐
       sion of the operating system. Base operating system subsets and	World‐
       wide  Language  Support	(WLS)  subsets are updated.  Building a custom
       kernel and rebooting the system with that kernel.  Executing  user-sup‐
       plied  update_preinstall	 and  update_postload files, if they exist, to
       perform customizations on the updated system.

       An Update Installation completes in 45  to  120	minutes.  Actual  time
       varies depending on your processor type, the number of software subsets
       that have to be updated, network traffic, and the speed of  the	CD-ROM
       device. You need to respond to prompts only during the initial analysis
       phase of the Update Installation.

       Postinstallation tasks may include manually merging file customizations
       into  those  files  that were not done automatically and rebuilding the
       kernel with layered product kernel components. It is  recommended  that
       you   review   the   Update  Installation  log  files  located  in  the
       /var/adm/smlogs directory when the Update Installation is complete.

EXAMPLES
       The following examples assume you have performed	 all  required	prein‐
       stallation  tasks,  have	 shut down the system to single user mode, and
       have   mounted	the   local   file   systems   with   the   <filename>
       /sbin/bcheckrc</filename> command.  See the Installation Guide for more
       information about these steps.

       To start an unattended Update Installation  from	 a  CD-ROM  device:  #
       /sbin/installupdate -u /dev/disk/cdrom0c

       To  start the Update Installation using the text-based interface from a
       CD-ROM  device  that  is	 mounted  on   the   /mnt   mount   point:   #
       /sbin/installupdate -nogui /mnt

       To  start  the  Update  Installation from a RIS server named server1: #
       /sbin/installupdate server1:

FILES
       Contains a log of the output that was displayed to  the	screen	during
       the  Update Installation.  Contains a list of the files that were saved
       to a extension.	Contains a list of the files  that  were  saved	 to  a
       extension.   Contains  a list of the protected system files that failed
       to automatically merge during the Update Installation.

SEE ALSO
       Commands: clu_upgrade(8),  doconfig(8),	fitset(8),  ris(8),  setld(8),
       updadmin(8)

       Installation Guide

       Installation Guide -- Advanced Topics

       Update Installation Quick Reference Card

       Sharing Software on a Local Area Network

       TruCluster Server Cluster Installation

							      installupdate(8)
[top]
                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 
More information is available in HTML format for server Tru64

List of man pages available for Tru64

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net