The following line in the finish script copIEs a file to the newly installed file system hierarchy on the client:
cp /tmp/install_config/
The profile file is a text file that defines how the Solaris OS is installed on a client.
Multiple profile files can be created. Several clients can use the same profile file, or each client can have its own profile file. The following shows the creation of two profile files:
# cd /export/config
# vi profile1
# install_type MUST be first
install_type initial_install
# start with the minimal required number of packages
clusterSUNWCXall
clusterSUNWCapache delete
clusterSUNWCpcmcdelete
clusterSUNWCpcmcx delete
clusterSUNWCthaidelete
clusterSUNWClp delete
clusterSUNWCnisdelete
clusterSUNWCpppdelete
# format the entire disk for Solaris
fdiskallsolaris all
# define how the disk is partitioned
partitioning explicit
filesysrootdisk.s0 6144 /
filesysrootdisk.s1 1024 swap
filesysrootdisk.s7 free /state/partition1
# install systems as standalone
system_type standalone
# specify patches to install
patch 119281-06 nfs 172.16.64.194:/export/patches
# specify packages to install
package SPROcc add nfs 172.16.64.194:/export/packages
:wq
# vi profile2
# install_type MUST be first
install_type initial_install
# start with the minimal required number of packages
clusterSUNWCXall
clusterSUNWCapache delete
clusterSUNWCpcmcdelete
clusterSUNWCpcmcx delete
clusterSUNWCthaidelete
clusterSUNWClp delete
clusterSUNWCnisdelete
clusterSUNWCpppdelete
# format the entire disk for Solaris
fdiskallsolaris all
# define how the disk is partitioned
partitioning explicit
filesysrootdisk.s0 6144 /
filesysrootdisk.s1 4096 swap
filesysrootdisk.s7 free /state/partition1
# install systems as standalone
system_type standalone
# specify patches to install
patch 119281-06 nfs 172.16.64.194:/export/patches
# specify packages to install
package SPROcc add nfs 172.16.64.194:/export/packages
:wqg. Create the check script:
The check script is used to validate that the rules and profile files are correctly set up. First copy the check script to the local Directory, that is, /export/config, as shown:
# cd /export/config
# cp /export/install/Solaris_10/Misc/jumpstart_sample/check .h. Run the check script:
# ./check
Validating rules...
Validating profile profile1...
Validating profile profile2...
The custom JumpStart configuration is ok.If no errors are found, the rules.ok file is created. This file is the same as the rules file but with its comments and blank lines removed. The check script adds the following comment to the end of the rules.ok file:
# version=2 checksum=3. Share the Installation and Configuration DirectorIEs
a. Modify dfstab to share the JumpStart directories.
b. Edit the /etc/dfs/dfstab file:
# vi /etc/dfs/dfstab
#Place share(1M) commands here for automatic execution
#on entering init state 3.
#
#Issue the command 'svCADm enable network/nfs/server' to
#run the NFS daemon processes and the share commands, after
#adding the very first entry to this file.
#
#share [-F fstype] [ -o options] [-d ""]
#[resource]
#for example,
#share -F nfs -o rw=engineering -d "home dirs" /export/home2
share -F nfs -o ro,anon=0 /export/install
share -F nfs -o ro,anon=0 /export/config
推荐阅读
- 超能战联娜雅菲技能使用方法
- 使用Yassp工具包安装安全的Solaris系统
- 使用PPT制作出动态文字具体操作流程
- 棉花脱叶剂使用方法
- 方舟生存进化遥控板如何使用
- 使用PPT制作出动态表白文字具体操作方法
- 荣耀20i中隐藏视频的简单使用方法
- Photoshop中使用内容感知工具去除图片多余物体具体操作步骤
- 6230i一周使用报告
- 便池的污垢怎么能快速清除
