forked from artix/66-scripts
obarun
2 years ago
1 changed files with 0 additions and 69 deletions
@ -1,69 +0,0 @@
|
||||
<!DOCTYPE html> |
||||
<html> |
||||
<head> |
||||
<meta charset="utf-8" /> |
||||
<meta name="viewport" content="width=device-width,initial-scale=1" /> |
||||
<title>The 66 Suite: boot@-66serv</title> |
||||
<meta name="author" content="Eric Vidal <eric@obarun.org>" /> |
||||
</head> |
||||
<body> |
||||
|
||||
<h1 id="boot@%20service">boot@ service</h1> |
||||
|
||||
<p>The boot@ instantiated service is a portable set of service to boot a machine in conjunction with the 66 API.</p> |
||||
|
||||
<h2 id="How%20to%20enable">How to enable</h2> |
||||
|
||||
<p>Like any other instantiated service to enable it you need to specify the target of the service. The target can be a random name.</p> |
||||
|
||||
<p>Such this service is a specific service to handle the boot sequence of a machine, its usually enabled on a tree build especially for it and contains only this service.</p> |
||||
|
||||
<p>For example:</p> |
||||
|
||||
<pre><code># 66-tree -n boot |
||||
# 66-enable -t boot boot@system |
||||
</code></pre> |
||||
|
||||
<p>The name of the tree need to match the name set at your <code>TREE=</code> <em>key=value</em> pair define into the <code>/etc/66/init.conf</code> file.</p> |
||||
|
||||
<p>Do not marks this tree enabled with the <code>66-tree -E</code> option. The <a href="https://web.obarun.org/software/66/66-tree.html">66-init</a> will take care for you about this special tree and starts it automatically.</p> |
||||
|
||||
<p>Refer to the <a href="https://web.obarun.org/software/66/66-tree.html">66-tree</a> and <a href="https://web.obarun.org/software/66/66-tree.html">66-enable</a> for further information about these tools.</p> |
||||
|
||||
<h2 id="How%20to%20configure%20it">How to configure it</h2> |
||||
|
||||
<p>This service is declared as a <code>module</code> service and comes with its own configuration file. |
||||
The configuration file can be seen easily using the <a href="https://web.obarun.org/software/66/66-env.html">66-env</a> tool with:</p> |
||||
|
||||
<pre><code># 66-env boot@system |
||||
</code></pre> |
||||
|
||||
<p>When you're done editing this file, you need to enable again the service to apply your changes:</p> |
||||
|
||||
<pre><code># 66-enable -t boot -F boot@system |
||||
</code></pre> |
||||
|
||||
<h2 id="Configuration%20file%20key=value%20pair%20explanation">Configuration file key=value pair explanation</h2> |
||||
|
||||
<p>Two differents kind of variable is used:</p> |
||||
|
||||
<ul> |
||||
<li><p>boolean: accepts as valid value the term <code>yes</code> or <code>no</code> and nothing else.</p></li> |
||||
<li><p>string: depends of the variable and defines in the following documentation.</p></li> |
||||
</ul> |
||||
|
||||
<hr/> |
||||
|
||||
<ul> |
||||
<li><strong>HOSTNAME</strong> : |
||||
|
||||
<ul> |
||||
<li>type: string</li> |
||||
<li>valid value: |
||||
Anything you want</li> |
||||
<li>description: |
||||
Tells at the kernel the hostname to use and set the /etc/hostname file with the value passed.</li> |
||||
</ul></li> |
||||
</ul> |
||||
</body> |
||||
</html> |
||||
Loading…
Reference in new issue