On Thu, Jan 08, 2004 at 04:47:50PM -0500, Mark Seger wrote:
> Ahh, somehow I missed --config-file switch the first time I read the man
> page. The one thing I'm still a little hazy on though is the notion of
> multiple master scripts, which is essentially where I'd like to go with
> this. I didn't see any switches that control the name of the script
> that is created.
ah - the --script option that never got added to the manpage, that
explains your confusion. I'm committing the following patch.
Index: mkautoinstallscript.content.sgml
===================================================================
RCS file: /cvsroot/systemimager/systemimager/doc/man/mkautoinstallscript.content.sgml,v
retrieving revision 1.7
diff -u -p -u -r1.7 mkautoinstallscript.content.sgml
--- mkautoinstallscript.content.sgml 15 Sep 2003 14:55:12 -0000 1.7
+++ mkautoinstallscript.content.sgml 9 Jan 2004 16:24:41 -0000
@@ -32,6 +32,7 @@
<arg><option>--quiet</option></arg>
<arg><option>--no-listing</option></arg>
<arg><option>--image <replaceable>IMAGENAME</replaceable></option></arg>
+ <arg><option>--script <replaceable>SCRIPTNAME</replaceable></option></arg>
<arg><option>--force <replaceable>[YES|NO]</replaceable></option></arg>
<arg><option>--config-file <replaceable>FILE</replaceable></option></arg>
<arg><option>--ip-assignment <replaceable>METHOD</replaceable></option></arg>
@@ -91,6 +92,19 @@
Where IMAGENAME is the name of the image for which you want to
create a new autoinstall script.
</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--script <replaceable>SCRIPTNAME</replaceable></option></term>
+ <listitem>
+ <para>
+ Where SCRIPTNAME is the base name to use for the resultant
+ autoinstall script. If not specified, SCRIPTNAME defaults to
+ IMAGENAME. This is most often used when you want to have multiple
+ autoinstallscripts for a single image; i.e. when you have clients
+ with different partitioning and/or filesystem schemes that use
+ the same image (same file set).
+ </para>
</listitem>
</varlistentry>
<varlistentry>
> It sounds like I could always rename the current
> master script and then create a new one, but I don't see how two scripts
> can be created, both of which point to the same image. without some
> manual horsing around. I'm certainly not opposed to diddling filenames,
> but if there's an easier way to do it I'm all for that.
>
> -mark
>
>
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Sisuite-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
