Network & Academic Computing Services Departamental Computing Support Autoinstall Autoinstall is used by DCS to install/upgrade the operating system. Autoinstall repartitions the hard drive (if there is any local data, it will be lost) and then installs the Operating System. At the end, it runs a script called after. after mounts our systems and runs many scripts (sometimes called each scripts) to configure your system as we know it. Thus it is essential for the local person to communicate to DCS any changes that are made to the system locally. run-after runs the same scripts as after. It is used to apply incremental changes. run-after can be executed at any time, where as after is executed after an OS install. Why use autoinstall? The components of autoinstall. What to do before autoinstalling a machine. How to initiate an autoinstall process: Sun Solaris SunOS 4.1.x SGI Irix 6.5.20 Overlay Procedure Irix 6.5.22 Overlay Procedure Irix 6.5.27 Overlay Procedure Irix6.5 Irix6.2 (w/CD) / ( w/o CD ) Irix6.3+6.4 Irix 5.X HP/Compaq/Digital Tru64 UNIX 5.x Digital UNIX Linux Red Hat 7.3 Red Hat Enterprise Linux The hokey install. It has been tested on Solaris, Red Hat and Tru64 UNIX. A related procedure: using hokey install for a quick host swap . How to remove an autoinstalled machine from support. How the autoinstall scripts can be tailored to accomodate the specifics of a particular machine's usage. Multi-stage installs How to reautoinstall a previously autoinstalled machine. How to autoinstall a previously non-autoinstalled machine. Issues to be aware of when administering an autoinstalled machine. FTP the autoinstall package. Some assembly is required. Please recommand any modifications to this document that will provide clarification of our instructions. Please do not hesitate to contact DCS with any questions concerning autoinstall. the previous autoinstall page dcs@uci.edu Network & Academic Computing Services > Support > SysAdmin Updated: October 2, 2003 University of California, Irvine