You must create a JumpStart directory on a diskette if a system is not connected to a network, because the system won't have access to a profile server. However, as expected, the system must have a diskette drive.
When you use a diskette for custom JumpStart installations, the essential custom JumpStart files (for example, the rules file, rules.ok file, and profiles) must reside in the root directory (JumpStart directory) on the diskette. The diskette that contains a JumpStart directory is called a profile diskette. The custom JumpStart files on the diskette should be owned by root and have permissions equal to 755.
The diskette requirements for the profile diskette are different for x86 based systems and SPARC based systems, so there is a different procedure to create a profile diskette for each platform.
Follow this procedure to create a profile diskette for x86 based systems, which involves:
Making a copy of the Configuration Assistant diskette (the copied boot diskette has a PCFS file system)
Copying sample custom JumpStart installation files into the diskette's root directory (JumpStart directory)
This procedure assumes that the system is running Volume Management. For detailed information about managing CDs without Volume Management, see the System Administration Guide.
Log in as root on an x86 or SPARC based system that has a diskette drive.
Insert the Configuration Assistant diskette into the diskette drive.
Make sure Volume Management knows about the diskette.
# volcheck |
Copy the Configuration Assistant diskette image to the system's hard disk.
# dd if=/vol/dev/aliases/floppy0 of=boot_image |
boot_image |
Is the file name where the Configuration Assistant diskette image is copied. You can specify an absolute path name. |
For example, the following command would copy the boot diskette to the boot_save file.
dd if=/vol/dev/aliases/floppy0 of=boot_save |
Manually eject the Configuration Assistant diskette.
Find a blank diskette (or a diskette that can be overwritten) that you can use for a profile diskette and insert it into the diskette drive.
Any previous information on the diskette will be overwritten when you make it into a profile diskette.
Make sure Volume Management knows about the diskette.
# volcheck |
This step will overwrite any data on the diskette.
# fdformat -d -U |
Copy the Configuration Assistant diskette image from the system's hard disk to the formatted diskette.
# dd if=boot_image of=/vol/dev/aliases/floppy0 |
The boot_image variable should be the same as in Step 4.
Eject the diskette.
# eject floppy |
Insert the copied boot diskette back into the diskette drive.
Make sure Volume Management knows about the diskette.
# volcheck |
Determine your next step based on where the Solaris CD is located.
You only need to perform the rest of the steps if you want to copy example custom JumpStart files from the Solaris CD. You are already done creating the profile diskette.
Change directory to the Misc directory on the Solaris CD image.
# cd Solaris_2.6/Misc |
Copy the example custom JumpStart files into the root directory (JumpStart directory) of the profile diskette.
# cp -r jumpstart_sample/* /floppy/floppy0/. |
The files you just copied are only example custom JumpStart files. You must update the files for your own site.
File names on PCFS file systems can be only 11 characters long (an 8-character file name and a 3-character extension). When copying JumpStart installation files to a diskette for x86 systems, be aware that the file transfer may truncate file names.
When using a profile diskette, all the custom JumpStart installation files must be in the root directory of the diskette.
You have completed creating a profile diskette. Now you can update the rules file and create profiles on the profile diskette to perform custom JumpStart installations. To continue, go to "Creating the rules File".
Follow this procedure to create a profile diskette for SPARC based systems, which involves:
Formatting a diskette (if needed).
Creating a UFS file system on the diskette (if needed).
Copying sample custom JumpStart installation files into the diskette's root directory (JumpStart directory).
This procedure assumes that the system is running Volume Management. If you are not using Volume Management to manage diskettes and CDs, refer to the System Administration Guide for detailed information about managing removable media without Volume Management.
Log in as root on a SPARC based system that has a diskette drive and a CD-ROM drive.
Find a blank diskette (or a diskette that can be overwritten) that you can use for a profile diskette and insert it into the diskette drive.
Any previous information on the diskette will be overwritten when you make it into a profile diskette.
Make sure Volume Management knows about the diskette.
# volcheck |
If the diskette already has a UFS file system on it, go to Step 10.
To find out if the diskette has a UFS file system on it, check the /etc/mnttab file for an entry similar to this:
/floppy/unnamed_floppy ufs |
This step will overwrite any data on the disk.
# fdformat -U |
Create a UFS file system on the diskette.
# newfs /vol/dev/aliases/floppy0 |
Eject the diskette.
# eject floppy |
Insert the formatted diskette back into the diskette drive.
Make sure Volume Management knows about the diskette.
# volcheck |
Determine your next step based on where the Solaris CD is located.
You only need to perform the rest of the steps if you want to copy example custom JumpStart files from the Solaris CD. You are already done creating the profile diskette.
If You Want to Use The ... |
Then ... |
|
---|---|---|
Solaris CD in the local CD-ROM drive |
|
|
Solaris CD image on the local disk |
Change the directory to the Solaris CD image on the local disk. For example:
|
Change directory to the Misc directory on the Solaris CD image.
# cd Solaris_2.6/Misc |
Copy the example custom JumpStart installation files into the root directory (JumpStart directory) of the profile diskette.
# cp -r jumpstart_sample/* /floppy/floppy0/. |
The files you just copied are only example custom JumpStart files. You must update the files for your own site.
When using a profile diskette, all the custom JumpStart installation files must be in the root directory of the diskette.
You have completed creating a profile diskette. Now you can update the rules file and create profiles on the profile diskette to perform custom JumpStart installations. To continue, go to "Creating the rules File".