LFScript Switches - Revision history

Marcel at 14:02, 14 June 2014

2014-06-14T14:02:50Z

← Older revision		Revision as of 14:02, 14 June 2014
Line 1:		Line 1:
			[[Category:Documentation]]
	LFScript is a command line application. You must provide LFScript with one or more ''switches'' to control what LFScript will build. Some switches (also called 'options') require additional arguments.		LFScript is a command line application. You must provide LFScript with one or more ''switches'' to control what LFScript will build. Some switches (also called 'options') require additional arguments.

Marcel: /* -i */ Add mountpoint requirement.

2012-02-09T15:24:53Z

-i: Add mountpoint requirement.

← Older revision		Revision as of 15:24, 9 February 2012
Line 86:		Line 86:

	=== -i <directory> ===		=== -i <directory> ===
	Tells LFScript to install to the defined directory.		Tells LFScript to install to the defined directory. The directory must be a ''mountpoint''.

	=== -I <overhead_directory> ===		=== -I <overhead_directory> ===

Marcel: /* -k */

2012-01-31T21:08:40Z

-k

← Older revision		Revision as of 21:08, 31 January 2012
Line 26:		Line 26:

	=== -k <kernel_configuration> ===		=== -k <kernel_configuration> ===
	Uses the specified Linux configuration file when building the kernel. If this option has not been set, LFScript will run <code>make defconfig</code> on the kernel, producing a default kernel configuration which probably lacks drivers and other support for your system. See [[~~Configuring a kernel~~]] for more information on how to create this configuration file.		Uses the specified Linux configuration file when building the kernel. If this option has not been set, LFScript will run <code>make defconfig</code> on the kernel, producing a default kernel configuration which probably lacks drivers and other support for your system. See [[Kernel configuration]] for more information on how to create this configuration file.

	Scripts named "kernel", or have the keyword "kernel" in their <code>TAGS</code> variable (see [[Script layout]]) will receive the configuration file.		Scripts named "kernel", or have the keyword "kernel" in their <code>TAGS</code> variable (see [[Script layout]]) will receive the configuration file.

Marcel at 20:43, 30 January 2012

2012-01-30T20:43:04Z

@@ Line 11: / Line 11: @@
 ./lfscript -Bx "nano which"    # Right</pre>
-Every switch should be used only once per session, and not every switch will allow the use of others.
+Every switch should be used only once per session, and not every switch will allow the use of others. However, with the right options set, it is possible to build and install your entire system in a single session.
 == Building the base system ==
@@ Line 42: / Line 42: @@
 === -x "<package1> [package2] [pa..." ===
 Builds the selected additional packages when the base system has been completed. Unlike with the base system, which defines the software it uses in [[buildbase.lfs]], LFScript will automatically resolve dependencies for the selected packages and build them too.
@@ Line 76: / Line 75: @@
 === Examples ===
 <pre>./lfscript -Bu                              # Resumes building your base system
 ./lfscript -BU kernel -k myconfig.config    # Rebuilds your Linux kernel, and any missing base system packages
 ./lfscript -Bux nano                        # Builds the 'nano' editor, and any missing base system packages</pre>

Marcel at 20:16, 30 January 2012

2012-01-30T20:16:30Z

@@ Line 13: / Line 13: @@
 Every switch should be used only once per session, and not every switch will allow the use of others.
-== Selecting the base system ==
+== Building the base system ==
 Every time you use LFScript, you must specify a base system at least. Even if you've already build it and only want to extend or install your system, you must '''always''' specify which base system to use.
@@ Line 34: / Line 34: @@
 === Examples ===
 <pre>./lfscript -B                            # Builds an LFS system
-./lfscript -b lfs-9193                   # Builds LFS SVN revision 9193 (if scripts for it exist)
+./lfscript -b lfs-9713                   # Builds LFS SVN revision 9713 (if scripts for it exist)
 ./lfscript -Bk fsos/3.2.1-i486.config    # Builds an LFS system and uses an fsOS kernel configuration file</pre>

Marcel at 19:27, 30 January 2012

2012-01-30T19:27:40Z

← Older revision		Revision as of 19:27, 30 January 2012
Line 8:		Line 8:
	If you want to give a switch multiple arguments you must enclose them in quote marks.		If you want to give a switch multiple arguments you must enclose them in quote marks.

	<pre>./lfscript -Bx nano which # WRONG!		<pre>./lfscript -Bx nano which # WRONG!
	./lfscript -Bx "nano which" # Right</pre>		./lfscript -Bx "nano which" # Right</pre>

	Every switch should be used only once per session, and not every switch will allow the use of others.		Every switch should be used only once per session, and not every switch will allow the use of others.
Line 17:		Line 17:
	Every time you use LFScript, you must specify a base system at least. Even if you've already build it and only want to extend or install your system, you must '''always''' specify which base system to use.		Every time you use LFScript, you must specify a base system at least. Even if you've already build it and only want to extend or install your system, you must '''always''' specify which base system to use.

	=== -B ~~("find~~ the base system for ~~me") ===~~		=== -B ===
	Normally, LFScript is distributed with scripts for a single base system ~~in which case~~ you can ~~just~~		This will automatically select the base system for you, if only one is available.

			Normally, LFScript is distributed with scripts for a single base system, making this option the easiest to use of the two 'b' options.

			=== -b <basesystem> ===
			With this option you can specify which base system to build.

			=== -k <kernel_configuration> ===
			Uses the specified Linux configuration file when building the kernel. If this option has not been set, LFScript will run <code>make defconfig</code> on the kernel, producing a default kernel configuration which probably lacks drivers and other support for your system. See [[Configuring a kernel]] for more information on how to create this configuration file.

			Scripts named "kernel", or have the keyword "kernel" in their <code>TAGS</code> variable (see [[Script layout]]) will receive the configuration file.

			LFScript has sample kernel configurations (used by the [[fsOS]] Live CD) in the "fsos" folder.

			=== Examples ===
			<pre>./lfscript -B # Builds an LFS system
			./lfscript -b lfs-9193 # Builds LFS SVN revision 9193 (if scripts for it exist)
			./lfscript -Bk fsos/3.2.1-i486.config # Builds an LFS system and uses an fsOS kernel configuration file</pre>

Marcel: Created page with "LFScript is a command line application. You must provide LFScript with one or more ''switches'' to control what LFScript will build. Some switches (also called 'options') requ..."

2012-01-30T19:05:59Z

Created page with "LFScript is a command line application. You must provide LFScript with one or more ''switches'' to control what LFScript will build. Some switches (also called 'options') requ..."

New page

LFScript is a command line application. You must provide LFScript with one or more ''switches'' to control what LFScript will build. Some switches (also called 'options') require additional arguments.

If you want to give several options without arguments, you can collapse them. The following two commands produce identical results:

<pre>./lfscript -B -u -x nano -k myconfig.config
./lfscript -Bux nano -k myconfig.config</pre>

If you want to give a switch multiple arguments you must enclose them in quote marks.

<pre>./lfscript -Bx nano which # WRONG!
./lfscript -Bx "nano which" # Right</pre>

Every switch should be used only once per session, and not every switch will allow the use of others.

== Selecting the base system ==

Every time you use LFScript, you must specify a base system at least. Even if you've already build it and only want to extend or install your system, you must '''always''' specify which base system to use.

=== -B ("find the base system for me") ===
Normally, LFScript is distributed with scripts for a single base system in which case you can just