diff options
authorChristos.K <freedomrfox@gmail.com>2017-06-24 18:37:19 +0300
committerChristos.K <freedomrfox@gmail.com>2017-06-24 18:37:19 +0300
commitc96554a5f41f680e73e62a2ea62dc6af4c35a9de (patch)
parentUpdated the help menu (diff)
Updated gse 1
1 files changed, 13 insertions, 4 deletions
diff --git a/docs/documentations/gse.1 b/docs/documentations/gse.1
index 139ea98..eb70fba 100644
--- a/docs/documentations/gse.1
+++ b/docs/documentations/gse.1
@@ -29,7 +29,7 @@ prompt, then -sn should be used.
Warning: This option uses force on every action and ignores any workdone. For more safe approach, see enforce.
+\fB\-\-lawful-good\fR \fI[="Hook Points"]
This option instructs gse to automatically say no to a completed part. For example, if there has been
already a successful system build and one wishes to reconfigure all parts but one, say apply new changes,
then he could simply start gse with --lawful-good=apply-new. This command can be used multiple times,
@@ -42,7 +42,7 @@ To make gse passive for everything, simply do: gse --lawful-good=all. This optio
the work done and sign it.
+\fB\-\-enforce\fR \fI[="Hook Points"]\fR
See --lawful-good, for examples. The only difference is that this option instructs gse to use force on the
target part instead of being passive. Note that --enforce=all, implies --force-new.
@@ -53,7 +53,7 @@ all the configuration files, flags and their arguments for a given build. This s
and always will reproduce the same output, given no unexpected issues pupup during the process.
+\fB\-\-time-warp\fR \fI[=N]\fR
Time warp enables time states. If this and only this option is passed on gse, then gse will search for the inidcated
state, export it and initiate the process.
@@ -81,7 +81,7 @@ go controller free, hence no stateless.
This option enables/disables the gse interactive mode. By default it's on.
-\fB\-\-base\fR \fB\-b\fR
+\fB\-\-base\fR \fB\-b\fR \fI[=catalyst/precomp]\fR
This option instructs gse about the method that should be used for the fundations of the system to be built.
Currently there are 2 options which gse supports. The one is 'catalyst', while the other is 'precomp'. The
catalyst opton will initiate the functions for creating a stage3 tarball, reading the spec files. The precomp
@@ -186,6 +186,15 @@ If other states existed prior to this, then 1 is not true. To see the related ma
To build a minimal system ( see --build-minimal for informations ): gse --base=catalyst --build-minimal.
+To build the controller, run: gse --controller. Without a =[moddir], gse will look in the default modules locations.
+For a custom location, run: gse --controller=[moddir].
+If you have a kernel already built and you wish to use that image instead of building a new one, start gse with:
+gse --base=catalyst --kernel=[path/to/kernel].
+Same holds for initramfs, gse --base=catalyst --initramfs=[path/to/image]
man 5 gse