Initial import of the user guide translations from http://userguide.haikuzone.net. Thanks to Vincent for providing all the necessary tools and to all translators for their work so far!

git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@35067 a95241bf-73f2-0310-859d-f6bbb57e9c96
This commit is contained in:
Joachim Seemer
2010-01-14 07:00:47 +00:00
parent bcc2c157a1
commit ee7dedc859
1233 changed files with 58973 additions and 4098 deletions
+50 -43
View File
@@ -1,6 +1,5 @@
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"../../html-dtd/xhtml1-strict.dtd">
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "../../html-dtd/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<!--
@@ -20,45 +19,55 @@
</head>
<body>
<div class="logo">
<img src="./images/logo.png" alt="logo" class="noprint" id="logo" name="logo" />
</div>
<div class="topnav">
<p>
«&#160;&#160;<a href="preferences.html">Preferences</a>
&#160;&#160;::&#160;&#160;
<a href="contents.html" class="uplink">Contents</a>
<!-- &#160;&#160;::&#160;&#160;
<a href="filesystem-layout.html">Filesystem layout</a>&#160;&#160;»
--> </p>
<div id="banner">
<div><span>User guide</span></div>
</div>
<div class="content">
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../../images/flags/gb.png" alt="" /> English</li>
<li><a href="../fr/bash-scripting.html"><img src="../../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="../de/bash-scripting.html"><img src="../../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="../it/bash-scripting.html"><img src="../../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="../ru/bash-scripting.html"><img src="../../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="../es/bash-scripting.html"><img src="../../images/flags/es.png" alt="" />Español</a></li>
<li><a href="../sv_SE/bash-scripting.html"><img src="../../images/flags/sv_SE.png" alt="" />Svensk</a></li>
<li><a href="../jp/bash-scripting.html"><img src="../../images/flags/jp.png" alt="" />日本語</a></li>
</ul>
<span>
«  <a href="preferences.html">Preferences</a> 
::  <a href="contents.html" class="uplink">Contents</a> 
<!-- ::  <a href="filesystem-layout.html">Filesystem layout</a>  » -->
</span></div>
</div>
<div class="title">Bash and Scripting</div>
<div id="content">
<div>
<h1>Bash and Scripting</h1>
<p>"Scripting" is the technique of automating procedures by stringing together commands and saving it all as text files, so called "scripts". Every time you run such a script, the commands are processed one after the other just like they would if you entered them into the <a href="applications/terminal.html">Terminal</a> by hand.<br />
Scripts can range from simply executing a few commands in a specific order to sophisticated pieces of code that solve complex tasks.</p>
<h1>
<a href="#logo"><img src="../images/up.png" align="right" alt="index" border="0" class="noprint" /></a>
<a id="bash" name="bash">The Bash</a></h1>
<h2>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="bash" name="bash">The Bash</a></h2>
<p>Since scripts rely naturally a lot on the shell they are interpreted by, you should first familiarize yourself with the BASH that's used by Haiku. There are many resources online as it's a widely used shell. One nice document is Johan Jansson's <a href="http://www.beforever.com/bashtut.htm" class="printurl">Introduction to bash - a tutorial for bash under BeOS</a>.</p>
<h1>
<a href="#logo"><img src="../images/up.png" align="right" alt="index" border="0" class="noprint" /></a>
<a id="scripting-bible" name="scripting-bible">The Scripting Bible</a></h1>
<h2>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="scripting-bible" name="scripting-bible">The Scripting Bible</a></h2>
<p>After you've learned a few basics about working in the shell, it's time to slowly ease yourself into the world of scripting. Again, you'll find loads of tutorials and reference material online as well as in bookstores. A very nice introduction that's practically tailor-made for Haiku is the online available <a href="http://www.birdhouse.org/beos/bible/bos/ch_scripting1.html" class="printurl">Scripting Chapter</a> (<a href="http://www.birdhouse.org/beos/bible/bos/BeOS.scripting.PDF">PDF, 900kb</a>) of Scot Hacker's BeOS Bible.</p>
<h1>
<a href="#logo"><img src="../images/up.png" align="right" alt="index" border="0" class="noprint" /></a><a id="user-scripts" name="user-scripts">Scripts in Haiku</a></h1>
<h2>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a><a id="user-scripts" name="user-scripts">Scripts in Haiku</a></h2>
<p>In Haiku, the system makes of course also use of scripting. Booting and shutting down are typical scripting procedures. These defined sequences can be augmented by the user with certain user scripts.<br />
If they don't exist already, you'll have to create the needed files yourself. Otherwise simply add your commands where in the process you want them to be executed.</p>
<h2>
<a href="#logo"><img src="../images/up.png" align="right" alt="index" border="0" class="noprint" /></a>
<a id="userbootscript" name="userbootscript">The UserBootscript</a></h2>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="userbootscript" name="userbootscript">The UserBootscript</a></h3>
<p><span class="path">/boot/home/config/boot/UserBootscript</span> will be executed after the system has finished its boot process. For example, you could launch a number of programs that would then be automatically started on every boot up:</p>
<pre># Start LaunchBox
/boot/system/apps/LaunchBox &amp;
@@ -69,27 +78,25 @@ If they don't exist already, you'll have to create the needed files yourself. Ot
<p>A simple alternative to the above for launching applications at boot up is to put links to them in the <span class="path">/boot/home/config/boot/launch</span> directory. This can be done simply by right-clicking on the application you wish to have started automatically, going to <span class="menu">Create Link</span> and then <a href="tracker.html#navigating">navigating</a> to the above directory.</p>
<h2>
<a href="#logo"><img src="../images/up.png" align="right" alt="index" border="0" class="noprint" /></a>
<a id="usershutdownscript" name="usershutdownscript">The UserShutdownScript</a></h2>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="usershutdownscript" name="usershutdownscript">The UserShutdownScript</a></h3>
<p><span class="path">/boot/home/config/boot/UserShutdownScript</span> will be executed as the first step in the shutdown process. If the script returns a non-zero exit status, the shutdown is aborted.</p>
<h2>
<a href="#logo"><img src="../images/up.png" align="right" alt="index" border="0" class="noprint" /></a>
<a id="usershutdownfinishscript" name="usershutdownfinishscript">The UserShutdownFinishScript</a></h2>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="usershutdownfinishscript" name="usershutdownfinishscript">The UserShutdownFinishScript</a></h3>
<p><span class="path">/boot/home/config/boot/UserShutdownFinishScript</span> is executed as the last step in the shutdown process. Note, that most parts of the system have terminated by the time this script is executed.</p>
</div>
</div>
<div class="bottomnav">
<p>
«&#160;&#160;<a href="preferences.html">Preferences</a>
&#160;&#160;::&#160;&#160;
<a href="contents.html" class="uplink">Contents</a>
<!-- &#160;&#160;::&#160;&#160;
<a href="filesystem-layout.html">Filesystem layout</a>&#160;&#160;»
--> </p>
<div class="nav">
<div class="inner"><span>
«  <a href="preferences.html">Preferences</a> 
::  <a href="contents.html" class="uplink">Contents</a> 
<!-- ::  <a href="filesystem-layout.html">Filesystem layout</a>  » -->
</span></div>
</div>
</body>