Home > Articles > Programming > Java

WebStart Flash

  • Print
  • + Share This
Like this article? We recommend

Using Flash in an Example

This section details a complete example of a Flash installation. The major steps of this procedure are these:

  1. Identify the master machine and create the Flash archive.

  2. Add the installation client (if necessary) on the JumpStart server and edit the appropriate sysidcfg, profile, and rules files.

  3. Initiate the installation on the client.

Creating the Flash Archive

We create the Flash archive on www01, an Ultra Enterprise_ 220R server acting as a Web server, and then make it available to the JumpStart server, server01, by the ftp command.

www01# pwd
/var/tmp
www01# uname -a
SunOS www01 5.8 Generic_108528-07 sun4u sparc SUNW,Ultra-60
www01# flarcreate -n "Solaris 8 web server image" \
> -a "j.s.howard@Sun.COM" \
> -R / \
> -x /var/tmp \
> /var/tmp/S8-webserver.archive
Determining which filesystems will be included in the archive...
Determining the size of the archive...
The archive will be approximately 699.92MB.
Creating the archive...
Archive creation complete.
www01# ftp server01
Connected to server01.EE_Lab.Sun.COM.
220 server01 FTP server (SunOS 5.8) ready.
Name (server01:root): blueprints
331 Password required for blueprints.
Password:
230 User blueprints logged in.
ftp> cd /jumpstart/FlashArchives
250 CWD command successful.
ftp> bin
200 Type set to I.
ftp> put S8-webserver.archive
200 PORT command successful.
150 Binary data connection for S8-webserver.archive (10.1.1.8,34653).
226 Transfer complete.
local: S8-webserver.archive remote: S8-webserver.archive
733880662 bytes sent in 67 seconds (10738.38 Kbytes/s)
ftp> quit
221 Goodbye.

Adding the Installation Client

We add the installation client, www26 (a Netra_ t1 105 server) in this example, as an installation client on the JumpStart server, server01 (www26 has already been added to the /etc/ethers and /etc/hosts files).

server01# cd /jumpstart/OS/Solaris_8_2001-04/Solaris_8/Tools
server01# ./add_install_client \
> -p server01:/jumpstart/Sysidcfg/Solaris_8 \
> -c server01:/jumpstart \
> www26 sun4u
updating /etc/bootparams

The profile used for this example, S8-webserver-Flash.profile, is similar to profiles presented in previous chapters. However, with Flash, only the following profile keywords are valid:

  • install_type

  • partitioning, and only the keyword values of explicit or existing must be used

  • filesys, and the keyword value of auto must not be used

  • fdisk (valid for Intel Architecture only)

The following profile specifies that Flash is used as the installation type, flash_install. Additionally, the profile instructs that the Flash archive is accessed through NFS, from the location specified by the archive_location keyword.

install_type  flash_install
archive_location nfs://10.1.1.8/jumpstart/FlashArchives/S8-webserver.archive
partitioning  explicit
#
# 4GB / and 1GB swap on a 18GB disk
#
filesys     rootdisk.s0   free      /
filesys     rootdisk.s1   1:449      swap

NOTE

Since name_service=NONE is specified in the following sysidcfg file, an IP address is used for the archive_location in the profile.

The rules entry used for this example is as follows:

model SUNW,UltraSPARC-IIi-cEngine \
    - \
    Profiles/S8-webserver-Flash.profile \
    Finish/EE_Lab-Flash.fin

The sysidcfg file used is as follows:

system_locale=en_US
timezone=US/Pacific
network_interface=primary {netmask=255.255.255.0
            protocol_ipv6=no}
terminal=vt100
security_policy=NONE
root_password=QH311oG13nnTU
name_service=NONE
timeserver=localhost

NOTE

A root password is specified in the sysidcfg file. This specification overrides the root password contained within the Flash archive in /etc/shadow.

After we have created or edited the preceding files, we verify the rules file, being certain to use the check script from the Solaris 8 OE 4/01 (Update 4) CD-ROM.

server01# cd /jumpstart
server01# ./check
Validating rules...
Validating profile Profiles/S8-webserver-Flash.profile...
The custom JumpStart configuration is ok.

The finish script used for this installation is:

#!/bin/sh
# EE_Lab-Flash.fin
# Finish script for default EE_Lab setup, JumpStart Flash

#
# clean up after flash archive install
#
for i in /a/var/adm/messages* /a/var/adm/utmpx \
     /a/var/adm/wtmpx /a/var/adm/lastlog
do
  cp /dev/null ${i}
done
mkdir /a/var/tmp
chown root:sys /a/var/tmp
chmod 1777 /a/var/tmp

NOTE

The /var/tmp directory needs to be created by the finish script because it was excluded when the archive was created with the flarcreate command.

The boot net - install command is then issued on the installation client.

ok boot net - install
Resetting ... 

screen not found.
keyboard not found.
Keyboard not present. Using ttya for input and output.

Netra t1 (UltraSPARC-IIi 360MHz), No Keyboard
OpenBoot 3.10.24 ME, 512 MB memory installed, Serial #11699811.
Ethernet address 8:0:20:b2:86:63, Host ID: 80b28663.

Executing last command: boot net - install              
Boot device: /pci@1f,0/pci@1,1/network@1,1 File and args: - install
SunOS Release 5.8 Version Generic_108528-07 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
whoami: no domain name
Configuring /dev and /devices
Using RPC Bootparams for network configuration information.
Configured interface hme0
Using sysid configuration file 10.1.1.8:/jumpstart/Sysidcfg/Solaris_8/sysidcfg
The system is coming up. Please wait.
Starting remote procedure call (RPC) services: sysidns done.
Starting Solaris installation program...
Searching for JumpStart directory...
Using rules.ok from 10.1.1.8:/jumpstart.
Checking rules.ok file...
Using profile: Profiles/S8-webserver-Flash.profile
Using finish script: Finish/EE_Lab.fin
Executing JumpStart preinstall phase...
Searching for SolStart directory...
Checking rules.ok file...
Using begin script: install_begin
Using finish script: patch_finish
Executing SolStart preinstall phase...
Executing begin script "install_begin"...
Begin script install_begin execution completed.

Processing default locales
	- Specifying default locale (en_US)

Processing profile
	- Opening Flash archive

	- Validating Flash archive

	- Selecting all disks
	- Configuring boot device
	- Using disk (c0t0d0) for "rootdisk"
	- Configuring / (c0t0d0s0)
	- Configuring swap (c0t0d0s1)

Verifying space allocation
	NOTE: 1 archives did not include size information

Preparing system for Flash install

Configuring disk (c0t0d0)
	- Creating Solaris disk label (VTOC)

Creating and checking UFS filesystems
	- Creating / (c0t0d0s0)

Beginning Flash archive extraction

Extracting archive: Solaris 8 workgroup server image
	Extracted  0.00 MB ( 0% of 699.88 MB archive)
	Extracted  1.00 MB ( 0% of 699.88 MB archive)
	Extracted  2.00 MB ( 0% of 699.88 MB archive)
.
.
output deleted for brevity
.
.
	Extracted 698.00 MB ( 99% of 699.88 MB archive)
	Extracted 699.00 MB ( 99% of 699.88 MB archive)
	Extracted 699.88 MB (100% of 699.88 MB archive)
	Extraction complete

Customizing system files
	- Mount points table (/etc/vfstab)
	- Network host addresses (/etc/hosts)

Cleaning devices

Customizing system devices
	- Physical devices (/devices)
	- Logical devices (/dev)

Installing boot information
	- Installing boot blocks (c0t0d0s0)

Installation log location
	- /a/var/sadm/system/logs/install_log (before reboot)
	- /var/sadm/system/logs/install_log (after reboot)

Flash installation complete
Executing JumpStart postinstall phase...
Executing finish script "Finish/EE_Lab-Flash.fin"...


Finish script Finish/EE_Lab-Flash.fin execution completed.

The begin script log 'begin.log'
is located in /var/sadm/system/logs after reboot.

The finish script log 'finish.log'
is located in /var/sadm/system/logs after reboot.

Just as with a "classic" JumpStart software installation, after the Flash installation completes, the specified finish script executes. If we had specified a begin script, it would have executed before the installation began. The Flash mechanism does not change the JumpStart framework, but Flash does change the manner in which the Solaris OE (and software) is installed. Flash does not do an individual installation of each software package, as suninstall does. The Flash mechanism simply writes the archive on the disk and then customizes the on-disk image to the hardware it was just installed on.

Also, keep in mind that the Flash archive is literally a snapshot of an installed system. If the archive was created on a system that has been in production or use, there may be additional clean-up that the finish scripts need to perform. Temporary files such as those found in /var/tmp and log files such as /var/adm/messages, /var/adm/utmpx, and /var/adm/wtmpx should be removed or zeroed out (as appropriate) after a Flash installation from an archive created on a production system. In this example, these files were zeroed out by the finish script.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020