> "Reset the Root Password on the Client" > "To reset the root password after a JumpStart > installation, use the > root_password keyword in a sysidcfg(4) file." > > I might recommend to use different word instead of > 'reset', > perhaps 'configure', since I think 'reset' evokes > impression > of setting to default/initial value instead of > customized one.
Changed to configure > *************************************** > > "For Automated Installer, reset the root password and > define new users ..." > -> > "For Automated Installer, configure the root password > and define new > user ..." changed > Current System Configuration manifest supports only > one user account. > > *************************************** > > "Rules Keywords and Criteria Manifest Directives" > > It seems that the table does not capture AI criteria > correctly, > in particular, AI currently supports: > > arch - reflects output of `uname -m`, e.g. sun4u > cpu - reflects output of `uname -p`, e.g. sparc > platform - reflects output of `uname -i`, e.g. i86pc > > Based on this, following AI criteria are equivalent > to jumpstart rules > keywords: > > jumpstart AI criteria > ......................... > arch cpu > karch arch > model platform I have searched the source of the AI guide and I do not find any instance of "cpu". Can you point me to some more information on this or a sample manifest that shows it? > *************************************** > > "Profile Keywords and AI Manifest Directives" > > In entry 'boot_device c0t0d0s0 update' following > piece of AI manifest is listed as equivalent: > > <ai_target_device> > <target_device_name>c0t0d0s0</target_device_name> > </ai_target_device> > > However, <target_device_name> accepts only disk name, > not slice name. We can perhaps use following AI > manifest > as an replacement: > > <ai_target_device> > <target_device_name> > c0t0d0 > device_name> > <target_device_install_slice_number> > 0 > device_install_slice_number> > </ai_target_device> Fixed > * Also, 'update' portion of 'boot_device' jumpstart > keyword is only > applicable for Sparc. For x86, 'preserve' has > always to be used, since > there is no way to change the boot device for x86. > Thus, the behavior > is the same for both jumpstart as well as AI. When I search the AI guide, I do not find any instance of "preserve" except with regard to VTOC slices. Can you explain further? > * 'usedisk' jumpstart keyword can only contain ctd > device name. Since > AI provides much more in that area, I would > recommend to mention this. Changed this > For more information about what <ai_target_device> > allows, please see > http://hub.opensolaris.org/bin/view/Project+caiman/Hea > ds+upFlag+day+for+bugs+5451%2C7057%2C7058 Added this link here: http://wikis.sun.com/display/OpenSolarisInfo/Which+Target+Will+AI+Install under "How to Specify Install Targets" > *************************************** > > "Converting a Profile File to an AI Manifest" > > In SC manifest, I might recommend to add > configuration of 'hostname': > > ... > <propval name="hostname" type="astring" > value="opensolaris"/> > .. Added > *************************************** > > "Sample JumpStart Rules File" > > In jumpstart rules file, I believe it should be: > > arch i86pc > -> > arch i386 > > or > > arch i86pc > -> > karch i86pc Changed to this latter > Criteria part in the first AI manifest: > > <ai_criteria name="ARCH"> > <value>Sparc</value> > criteria> > > -> > > <ai_criteria name="cpu"> > <value>Sparc</value> > criteria> Please see previous comment about "cpu" -- This message posted from opensolaris.org _______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
