To complete the Custom JumpStart installation the profiles, rules, and rules.ok files you have customized for JumpStart must be added to jumpstart_dir_path. Check that all interactive prompts can be answered.
As root, at label admin_low
,
launch a terminal and change to the JumpStart directory.
If the jumpstart_dir_path is on a diskette, you must allocate the device first. See "How to Create a JumpStart Directory on a Diskette" for the procedure.
# cd jumpstart_dir_path |
If you are using a working directory rather than the jumpstart_dir_path to create custom JumpStart files, copy them to jumpstart_dir_path.
All of your profiles, the rules file, the rules.ok file, and the finish script (finish.sh) should be copied to jumpstart_dir_path.
For example, the following commands copy the contents of the working directory /export/tmp. All custom JumpStart profiles have followed a convention of using "profile" as the last part of the file name.
# cd /export/tmp # cp finish.sh *profile* rules rules.ok jumpstart_dir_path |
Check file permissions.
File or Directory |
Owner |
Permissions |
Label |
---|---|---|---|
jumpstart_dir_path |
root |
755 |
admin_low[admin_low] |
profiles |
root |
644 |
admin_low[admin_low] |
rules, rules.ok |
root |
644 |
admin_low[admin_low] |
finish.sh |
root |
755 |
admin_low[admin_low] |
As root, at label admin_low
,
deallocate the diskette drive if the jumpstart_dir_path
is on a diskette.
Result: The custom JumpStart files are available to the installation program.
A custom JumpStart installation prompts you interactively if the installation program cannot get information that it requires.
Did you complete the following procedures?
To read about the optional features available for custom JumpStart installations, see Chapter 9, Using Optional Custom JumpStart Features.
To install a workstation using custom JumpStart, use the appropriate booting procedure in Chapter 3, Installing a Workstation.