Update userguide translations, leavengood as nielx
This commit is contained in:
autonielx
@@ -43,6 +43,7 @@
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -83,9 +84,9 @@ When creating a new account, be certain to <b>provide your email address</b> as
|
||||
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">search</a> function for this.<br />
|
||||
After you have established that it's a unique bug, make your information as accurate as possible:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a>.</p></li>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision from <acronym title="Subversion, the source code management system we use">SVN</acronym> you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
|
||||
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
|
||||
@@ -47,6 +47,7 @@
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -56,7 +57,6 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Solange die Übersetzung dieser Seite noch nicht ganz fertig ist, erscheint für die noch fehlenden Teile die englische Version.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
@@ -86,9 +86,9 @@
|
||||
<p>Bevor man einen Fehler meldet, sollte man sich <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">sicher sein</a>, dass das nicht schon geschehen ist. Hierzu kann auch die <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">Suchfunktion</a> verwendet werden.<br />
|
||||
Nach dieser Überprüfung sollte man so genau wie möglich den Fehler beschreiben:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a>.</p></li>
|
||||
<li><p>Der Fehler sollte mit einer aktuellen Version von Haiku reproduzierbar sein. Zum Testen gibt es installierbare <a href="http://download.haiku-os.org">Nightly Images</a>.</p></li>
|
||||
<li><p>Wie wurde Haiku verwendet (auf echter Hardware oder virtualisiert unter VMWare, QEMU oder ähnlichem)?</p></li>
|
||||
<li><p>Welche Versionsnummer aus dem <acronym title="Subversion, unser Source Code Management System">SVN</acronym> wurde verwendet? Die Version ist auch unter <span class="menu">Über Haiku...</span> im Deskbar Menü zu finden. Wie genau Haiku kompiliert wurde (gcc2, gcc4, gcc2hybrid, gcc4hybrid), ist ebenfalls von Interesse. Die runterladbaren Images sind entsprechend benannt; Leute, die sich ihr Haiku selber zusammenbauen, sollten wissen wie sie das gemacht haben.</p></li>
|
||||
<li><p>Welche Haiku-Versionsnummer wurde verwendet? Die Version ist unter <span class="menu">Über Haiku...</span> im Deskbar Menü zu finden. Wie genau Haiku kompiliert wurde (gcc2, gcc4, gcc2hybrid, gcc4hybrid), ist ebenfalls von Interesse. Die runterladbaren Images sind entsprechend benannt; Leute, die sich ihr Haiku selber zusammenbauen, sollten wissen wie sie das gemacht haben.</p></li>
|
||||
<li><p>Der Fehler sollte so präzise wie möglich beschrieben werden. Welches Verhalten wurde erwartet und was wurde statt dessen beobachtet?</p></li>
|
||||
<li><p>Wann tritt der Fehler auf? Nur mit einer Schritt-für-Schritt Anleitung können die Entwickler den Bug nachstellen und beheben.</p></li>
|
||||
<li><p>An den Fehlerbericht sollten so viele Informationen wie möglich angehängt werden. Handelt es sich um einen Bug in der grafischen Oberfläche oder einer der Anwendungen, ist ein Bildschirmfoto mittels der <span class="key">DRUCK</span> Taste hilfreich.</p></li>
|
||||
|
||||
@@ -44,6 +44,7 @@
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_en.html" class="uplink">Welcome</a>
|
||||
@@ -82,9 +83,9 @@ When creating a new account, be certain to <b>provide your email address</b> as
|
||||
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">search</a> function for this.<br />
|
||||
After you have established that it's a unique bug, make your information as accurate as possible:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a>.</p></li>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision from <acronym title="Subversion, the source code management system we use">SVN</acronym> you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
|
||||
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
|
||||
@@ -45,6 +45,7 @@
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -85,9 +86,9 @@ Cuando se cree una cuenta nueva, asegurese de <b>proporcionar su correo electró
|
||||
<p>Antes de reportar un fallo, por favor <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">asegúrese</a> que aún no exista. Puede también usar la función de <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">búsqueda</a> para esto.<br />
|
||||
Tras haber establecido que es un fallo nuevo, haga su información tan puntual como sea posible:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a>.</p></li>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Incluya información básica tal como dónde está probando a Haiku (sobre hardware real, en VMWare, en QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision from <acronym title="Subversion, the source code management system we use">SVN</acronym> you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describa el problema que esté experimentando. Intente ser tan preciso como pueda: describa el comportamiento actual, y el comportamiento esperado.</p></li>
|
||||
<li><p>Describa qué pasos necesita realizar para exponer el fallo. Esto ayudará a los desarrolladores a reproducir el fallo.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
|
||||
@@ -45,6 +45,7 @@
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -85,9 +86,9 @@ Luotaessa uutta tiliä muista <b>tarjota sähköpostiosoitteesi</b>, koska se on
|
||||
<p><a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">Varmista</a> ennen vian ilmoittamista, että vastaavaa vikailmoitusta ei ole jo olemassa. Voit käyttää myös <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">etsi</a>-toimintoa tähän.<br />
|
||||
Varmista sen jälkeen kun olet esitellyt ainutlaatuisen vian, että tietosi ovat niin tarkkoja kuin mahdollista:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a>.</p></li>
|
||||
<li><p>Yritä toistaa havaitsemasi vika nykyisessä Haikun korjausversiossa. Esirakennetut tiedostovedokset testaustarkoituksiin löytyvät <a href="http://haiku-files.org/">täältä</a>.</p></li>
|
||||
<li><p>Sisällytä mukaan perustietoa siitä, kuinka testaat Haikua (todellisessa tietokoneessa, VMWare-ympäristössä, QEMU-emulaattorissa, jne.).</p></li>
|
||||
<li><p>Mainitse, mitä <acronym title="Subversion, käyttämämme lähdekoodin versionhallintajärjestelmä">SVN</acronym>-korjausversiota käytät. Löydät tämän tiedon Työpöytäpalkin valikosta <span class="menu">Haikusta...</span>. Mainitse myös, että minkälaisella rakennusjärjestelmällä (gcc2, gcc4, gcc2hybrid, gcc4hybrid) testaamasi järjestelmä on rakennettu. Ladattavat tiedostovedokset on nimetty niiden mukaan. Itse rakennetuissa tiedostovedoksissa tiedät itse, kuinka se on rakennettu.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Kuvaile kokemasi pulma. Yritä olla niin tarkka kuin voit: kuvaile todellinen käyttäytyminen, ja se käyttäytyminen, jota odotit.</p></li>
|
||||
<li><p>Kuvaile, mitä vaiheita pitää suorittaa vian paljastumiseksi. Tämä auttaa kehittäjiä toistamaan vian.</p></li>
|
||||
<li><p>Liitä mukaan niin paljon tietoja, kuin sinulla on. Jos kyseessä on graafisen käyttöliittymän vika, tai vika yhdessä sovelluksessa, yritä tehdä näytönkaappaus painamalla <span class="key">PRINT SCREEN</span>-näppäintä.</p></li>
|
||||
|
||||
@@ -47,6 +47,7 @@
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -87,10 +88,10 @@ Lors de la création d’un nouveau compte, pensez à <b>indiquer votre adresse
|
||||
<p>Avant de rapporter un bogue, veuillez <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">vérifier</a> qu’il n’est pas déjà répertorié. Vous pouvez aussi utiliser la <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">fonction de recherche</a> pour cela.<br />
|
||||
Après vous être assuré que votre bogue est unique, obtenez des informations précises sur votre environnement :</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a>.</p></li>
|
||||
<li><p>Essayez de reproduire votre problème avec la version actuelle d'Haiku. Des <a href="http://haiku-files.org/">images préfabriqués</a> sont disponible à cet usage.</p></li>
|
||||
<li><p>Indiquez comment vous testez Haiku (sur machine réelle, dans VMware, dans Qemu…)</p></li>
|
||||
<li><p>Indiquez quelle révision <acronym title="Subversion, le système de gestion de code source que nous utilisons">SVN</acronym> de Haiku vous utilisez. Vous pouvez trouver cette information dans le menu « <i>About This System…</i> » de la Deskbar.
|
||||
N'oubliez pas de mentionner de quel type de construction est issu le système Haiku que vous testez (gcc2, gcc4, gcc2hybrid, gcc4hybrid).
|
||||
<li><p>Indiquez quelle révision vous utilisez. Vous pouvez trouver cette information dans le menu « <i>About Haiku…</i> » de la Deskbar.
|
||||
N'oubliez pas de mentionner le type de construction dont est issu le système que vous testez (gcc2, gcc4, gcc2hybrid, gcc4hybrid).
|
||||
Les images téléchargeables sont nommés en conséquence. Si vous avez construit l'image vous-même, vous devriez savoir comment vous l'avez compilé.</p></li>
|
||||
<li><p>Décrivez le problème que vous rencontrez. soyez aussi précis que possible : décrivez le comportement réel, et celui que vous attendiez.</p></li>
|
||||
<li><p>Décrivez les actions que vous avez effectuées avant de faire ressortir le bogue. Cela permettra aux développeurs de le reproduire.</p></li>
|
||||
|
||||
@@ -45,6 +45,7 @@
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -85,9 +86,9 @@
|
||||
<p>Mielőtt jelentesz egy hibát, előtte <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">győződj meg</a>, hogy még nem létezik róla jelentés. Szintén használható a <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">kereső</a> is.<br />
|
||||
Miután megbizonyosodtál róla, hogy a hiba egyedi, akkor azt a lehető legpontosabban, legrészletesebben le kell írni:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a>.</p></li>
|
||||
<li><p>Próbáld meg a hibát a legújabb verzión is előidézni. Előre elkészített képfájlok is a <a href="http://download.haiku-os.org">rendelkezésre állnak</a>.</p></li>
|
||||
<li><p>Add meg az alapvető információkat arra vonatkozóan, hogy miként használtad a Haiku-t (például valós gépen vagy emulátoron (VMWare, QEMU), stb.).</p></li>
|
||||
<li><p>Említsd meg, melyik <acronym title="Subversion, az általunk használt forráskód-kezelő">SVN</acronym> verziót használod. Ezt az információt megtalálod a <span class="menu">Haiku névjegyé</span>n az Asztalsávon. Szintén szükséges a Haiku típusának (gcc2, gcc4, gcc2hybrid, gcc4hybrid) megadása. Ez a letöltött képfájl nevéből is kiderülthet, mert tartalmazzák azt.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Írd le a tapasztalt problémát. Próbáld meg olyan pontosan, ahogy tudod: mi és hogyan viselkedett, és mire számítottál.</p></li>
|
||||
<li><p>Írd le, hogy milyen lépések szükségesek ahhoz, hogy a hibát meg tudjuk ismételni. Ez a lépés segít a fejlesztőknek.</p></li>
|
||||
<li><p>Mellékelj annyi információt, amennyit csak tudsz. Ha ez a grafikus felület, vagy egy program hibája, akkor készíts egy képernyőképet a <span class="key">PRINT</span> billentyű lenyomásával.</p></li>
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 110 B After Width: | Height: | Size: 98 B |
Binary file not shown.
|
After Width: | Height: | Size: 120 B |
@@ -43,6 +43,7 @@
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -83,9 +84,9 @@ When creating a new account, be certain to <b>provide your email address</b> as
|
||||
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">search</a> function for this.<br />
|
||||
After you have established that it's a unique bug, make your information as accurate as possible:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a>.</p></li>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision from <acronym title="Subversion, the source code management system we use">SVN</acronym> you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
|
||||
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
|
||||
@@ -47,6 +47,7 @@
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -88,7 +89,7 @@
|
||||
<ul>
|
||||
<li><p>その問題が最新バージョンの Haiku でも再現するかを確認してみてください。テスト用のビルド済イメージが<a href="http://download.haiku-os.org">利用可能です</a>。</p></li>
|
||||
<li><p>テストした環境の情報 (物理的なハードウェア、QEMU、VMware など)</p></li>
|
||||
<li><p><acronym title="Git, the source code management system we use">GIT</acronym> でのリビジョン番号。リビジョン番号はデスクバーメニューの <span class="menu">Haiku について...</span> から見つけられます。また、Haiku をビルドした環境も必要かもしれません。(gcc2、gcc4、gcc2hybrid、gcc4hybrid) ダウンロードしたイメージの場合イメージ名を書いてください。自分でビルドした場合、何でビルドしたのかを知っておく必要があります。</p></li>
|
||||
<li><p>動かしているリビジョン番号について言及してください。この情報は、Deskbar メニューの<span class="menu">Haiku について (About Haiku...)</span> から得られます。同様にテストしているHaiku のビルドの種類 (gcc2, gcc4, gcc2hybrid, gcc4hybrid) についても触れてください。ダウンロードイメージはビルドの種類に従って命名されています。自分でビルドしたイメージについては、どのようにビルドしたか知っておく必要があります。</p></li>
|
||||
<li><p>できる限り正しく、実際に起きた挙動を説明し、その後自分が予測した挙動と、現在の挙動の問題を説明する</p></li>
|
||||
<li><p>再現する手順や準備。これは開発者が再現するために必要です。</p></li>
|
||||
<li><p>その他の情報。GUI 周りのバグやアプリケーションのバグならば、<span class="key">PRINT</span> キーを押してスクリーンショットを取得してください。</p></li>
|
||||
|
||||
@@ -43,6 +43,7 @@
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -83,9 +84,9 @@ When creating a new account, be certain to <b>provide your email address</b> as
|
||||
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">search</a> function for this.<br />
|
||||
After you have established that it's a unique bug, make your information as accurate as possible:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a>.</p></li>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision from <acronym title="Subversion, the source code management system we use">SVN</acronym> you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
|
||||
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
|
||||
@@ -46,6 +46,7 @@
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -86,9 +87,9 @@ Ao criar uma nova conta, certifique-se de <b>informar seu endereço de correio e
|
||||
<p>Antes de reportar um erro, por favor <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">certifique-se</a> de que ele ainda não existe. Pode-se também utilizar a função de <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">pesquisa</a> para isso.<br />
|
||||
Após constatar que é um erro original, torne sua informação a mais acurada possível:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a>.</p></li>
|
||||
<li><p>Tente reproduzir o problema na versão atual do Haiku. Imagens pré-compiladas para o propósito de testes estão <a href="http://haiku-files.org/">disponíveis</a>.</p></li>
|
||||
<li><p>Inclua informação básica sobre como está testando o Haiku (em equipamento real, no VMWare, no QEMU, etc.).</p></li>
|
||||
<li><p>Mencione qual revisão do <acronym title="Subversion, the source code management system we use">SVN</acronym> você está rodando. Esta informação pode ser encontrada em <span class="menu">Sobre o Haiku...</span> a partir do menu do Deskbar. Também mencione que tipo de compilação do Haiku está testando (gcc2, gcc4, gcc2hybrid, gcc4hybrid). As imagens baixáveis são nomeadas de acordo, para uma imagem compilada por você mesmo, deverá informar como o fez.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Descreva o problema que está experimentando. Tente ser o mais acurado possível: descreva o comportamento atual e o comportamento que deseja.</p></li>
|
||||
<li><p>Descreva que passos precisa realizar a fim de expor o erro. Isto ajudará os desenvolvedores a reproduzir o erro.</p></li>
|
||||
<li><p>Anexe toda a informação que tiver. Se é um erro de interface gráfica, ou um erro em um dos aplicativos, tente obter uma imagem da tela pressionando a tecla <span class="key">PRINT</span>.</p></li>
|
||||
|
||||
@@ -43,6 +43,7 @@
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -83,9 +84,9 @@ When creating a new account, be certain to <b>provide your email address</b> as
|
||||
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">search</a> function for this.<br />
|
||||
After you have established that it's a unique bug, make your information as accurate as possible:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a>.</p></li>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision from <acronym title="Subversion, the source code management system we use">SVN</acronym> you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
|
||||
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
|
||||
@@ -0,0 +1,180 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <[email protected]>
|
||||
* Translators:
|
||||
* Emrys
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Raportare defecțiuni</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Ghid de utilizare</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/ro.png" alt="" /> Română</li>
|
||||
<li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_ro.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Traducerea acestei pagini nu este completă încă. Până când va fi, părțile incomplete utilizează originalul în limba engleză.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
|
||||
<a href="#report">Creating a bug report</a><br />
|
||||
<a href="#app">Application bugs</a><br />
|
||||
<a href="#server">Server bugs</a><br />
|
||||
<a href="#kernel">Kernel bugs</a><br />
|
||||
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
|
||||
<a href="#syslog">Syslog</a><br />
|
||||
<a href="#onscreen">On screen debug output</a><br />
|
||||
<a href="#hardware">Hardware/Driver bugs</a><br />
|
||||
<a href="#next">What's next?</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>Raportare defecțiuni</h1>
|
||||
|
||||
<p>Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.</p>
|
||||
<p>To keep our bugtracker effective, it's essential to abide by the <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Bug Tracker Etiquette</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Obținerea unui cont Trac</a></h2>
|
||||
<p>To file a ticket, you need to have an account at <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku's Bugtracker</a>.<br />
|
||||
When creating a new account, be certain to <b>provide your email address</b> as it is necessary to obtain basic ticket modification privileges. Be sure to <b>check your spam folder</b> shortly afterwards, as the all important verification mail often ends up there.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Crearea unui raport de defecțiune</a></h2>
|
||||
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">search</a> function for this.<br />
|
||||
After you have established that it's a unique bug, make your information as accurate as possible:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
|
||||
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Defecțiuni de aplicație</a></h2>
|
||||
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Defecțiuni de server</a></h2>
|
||||
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
|
||||
Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (<span class="cli">bt</span> command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Defecțiuni de kernel</a></h2>
|
||||
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<ul>
|
||||
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
|
||||
<li><p>The system reboots spontaneously.</p></li>
|
||||
<li><p>The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards). Wait at least a minute to see, if anything happens.</p></li>
|
||||
<li><p>The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).</p></li>
|
||||
</ul>
|
||||
<p>Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could blacklist the responsible Wifi driver from your Haiku installation (see <a href="../../../userguide/en/bootloader.html">Boot Loader</a>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Shows the handled and unhandled hardware interrupts.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (aka continue)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
|
||||
</table>
|
||||
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
|
||||
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Syslog</a></h3>
|
||||
<p><b>This is the preferred method for gaining information from a non-booting system.</b><br />
|
||||
The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file <span class="path">/boot/system/var/log/syslog</span>. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).</p>
|
||||
<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog persistent. If the option <span class="menu">Save syslog from previous session during boot</span> is activated in the boot loader options (as it is by default), you'll find the syslog of your last session as <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
If you're not able to boot to get to the previous_syslog, you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
|
||||
In the boot loader's <span class="menu">Debug menu</span> you should find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. Note: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">On screen debug output</a></h3>
|
||||
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../../userguide/ro/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Hardware/Driver bugs</a></h2>
|
||||
<p>When dealing with a hardware/driver related bug, you should attach the following information as text files:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>A detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Lists all used drivers.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Only available within <i>Kernel Debugging Land</i> (see above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>The first four commands are entered into Terminal. Add a <span class="cli"> > output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">Ce urmează?</a></h2>
|
||||
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
|
||||
non-descriptive comments.</p>
|
||||
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
|
||||
as 'fixed'.</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_ro.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -47,6 +47,7 @@
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -87,9 +88,9 @@
|
||||
<p>Прежде чем сообщать об ошибке, пожалуйста, <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Eтекст,+который+вы+ищите&order=priority">убедитесь</a>, что аналогичного багрепорта ещё не существует. Для этого также можно воспользоваться функцией <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">поиска</a>.<br />
|
||||
После того как вы установили, что подобных багрепортов не имеется, то оформите вашу информацию как можно точнее:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a>.</p></li>
|
||||
<li><p>Попытайтесь воспроизвести вашу проблему на текущей ревизии Haiku. Готовые образы для тестирования доступны <a href="http://haiku-files.org/">здесь</a>.</p></li>
|
||||
<li><p>Включите информацию о том как вы тестируете Haiku (на реальном компьютере, в эмуляторе VMWare, QEMU, и т. д.).</p></li>
|
||||
<li><p>Укажите какую <acronym title="Subversion - система управления версиями, которую мы используем">SVN</acronym> ревизию Haiku вы используете. Эту информацию можно найти в окне программы <span class="menu">О системе Haiku...</span> , которая доступна в меню Deskbar-а. Также укажите какой тип сборки Haiku вы тестируете (gcc2, gcc4, gcc2hybrid, gcc4hybrid). Образы для скачивания названы подобным образом, а если вы собрали систему сами, то вы знаете как вы ее собрали.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Опишите проблему, с которой вы столкнулись, попытайтесь описать её наиболее точно: как именно она проявилась, и как правильно должен бы был действовать проблемный объект при её отсутствии.</p></li>
|
||||
<li><p>Расскажите какие шаги нужно выполнить для её возникновения, что поможет разработчикам воспроизвести эту ошибку.</p></li>
|
||||
<li><p>Прикрепите всю имеющуюся информацию. Если это ошибка графического интерфейса или баг в каком-либо приложении, то попытайтесь сделать скриншот клавишей <span class="key">Print Screen</span> key.</p></li>
|
||||
|
||||
@@ -45,6 +45,7 @@
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -85,9 +86,9 @@ Pri vytváraní účtu určite poskytnite <b>vašu emailovú adresu</b>, pretož
|
||||
<p>Pred nahlásením chyby sa prosím <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">uisitite</a>, že už nebola nahlásená. Tiež na to môžete použiť funkciu <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">hľadanie</a>.<br />
|
||||
Potom, ako ste sa uistili, že chyba je jedinečná, uveďte čo najpresnejšie vaše informácie:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a>.</p></li>
|
||||
<li><p>Pokúste sa reprodukovať problém v aktuálnej revízii Haiku. Sú pripravené <a href="http://haiku-files.org/">obrazy na testovacie účely</a>.</p></li>
|
||||
<li><p>iveďte základné infomrácie o tom ako testujete Haiku (na skutočnom hardvéri, vo VMWare, v QEMU atď.).</p></li>
|
||||
<li><p>Uveďte, ktorú revíziu zo <acronym title="Subversion, nástroj na správu zdrojového kódu, ktorý používame">SVN</acronym> používate. Túto informáciu nájdete v dialógu <span class="menu">O Haiku...</span> z menu Panela. Tiež uvete, aký druh Haiku testujete (gcc2, gcc4, gcc2hybrid, gcc4hybrid). Obsazy na stiahnutie sú podľa toho pomenované; pri obraze, ktorý ste zostavili sami by ste mali vedieť ako ste ho zostavili.</p></li>
|
||||
<li><p>Uveďte, ktorú revíziu používate. Túto informáciu nájdete v dialógu <span class="menu">O Haiku...</span> z menu Panela. Tiež uvete, aký druh Haiku testujete (gcc2, gcc4, gcc2hybrid, gcc4hybrid). Obrazy na stiahnutie sú podľa toho pomenované; pri obraze, ktorý ste zostavili sami by ste mali vedieť ako ste ho zostavili.</p></li>
|
||||
<li><p>Popíšte váš problém. Skúste byč čo najpresnejší: popíšte správanie, ktoré ste očakávali a správanie, ktoré ste dostali.</p></li>
|
||||
<li><p>Popíšte kroky, ktoré je potrebné vykonať na vyvolanie chyby. To pomôže vývojárom chybu reprodukovať.</p></li>
|
||||
<li><p>Priložte všetky informácie,ktoré máte k dispozícii. Ak je to chyba používateľského rozhrania alebo chyba v niektorej z aplikácií, skúste urobiť snímku obrazovky stlačením klávesu <span class="key">Print Screen</span>.</p></li>
|
||||
@@ -112,7 +113,7 @@ Okrem toho, že je všetko škaredšie a nepohodlné platí prakticky to isté a
|
||||
<li><p>Systém nenaštartuje korektne. Môže spontánne naštartovať alebo v niektorom bode zastaviť (napr. na niektorej ikone štartovacej obrazovky). V druhom prípade tiež skúste <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>Celý systém alebo niektorá časť hardvéru sa nespráva korektne. Napríklad môže byť veľmi pomalý, vyskytnú sa chyby alebo niečo vôbec nefunguje. Ak nejaký hardvér vôbec nefunguje, prvá vec, ktorú treba skontrolovať je, či ho momentálne Haiku vôbec podporuje (napr. spýtať sa v poštovej konferencii alebo na fóre).</p></li>
|
||||
</ul>
|
||||
<p>Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could blacklist the responsible Wifi driver from your Haiku installation (see <a href="../../../userguide/en/bootloader.html">Boot Loader</a>).</p>
|
||||
<p>Pamätajte, že hoci iba posledný bod indikuje súvislosť s hardvérom, všetky ostatné symptómy môžu byť spôsobené aj chybou v ovládači hardvéru. Ak máte podozrenie, ktorá časť hardvéru alebo zodpovedajúci ovládač môže súvisieť s problémom, skontrolujte, či odstránenie alebo vypnutie hardvéru či ovládača pomôže. Napríklad ak podozrievate Wi-Fi, možno zistíte, že váš BIOS umožňuje ju vypnúť. Alebo ak nie, môžete odstrániť príslušný ovládač Wi-Fi z vašej inštalácie Haiku (pozri <a href="../../../userguide/en/bootloader.html">Zavádzač systému</a>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
@@ -127,15 +128,15 @@ Pamätajte, že v KDL vaša klávesnica nemusí fungovať. Klávesnice PS/2 fung
|
||||
</table>
|
||||
<p>Ďalšie informácie nájdete v článku <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
<p>Výstup KDL sa zapisuje na sériový port (ak ho máte a ak máte príslušný kábel na pripojenie druhého počítača, môžete prostredníctvom neho zachytiť výstup pomocou terminálového programu) a do syslogu. Ak nemôžete opustiť KDL, nezapíše však sa do súboru syslog. Existuje voľba zavádzača systému, ktorá vám umožňuje zachytiť ho napriek tomu (pozri nižšie).</p>
|
||||
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
|
||||
<p>Môžete vygenerovať QR kódy z výstupu KDL, ktoré je možné previesť na text pomocou smartfónu alebo podobných zariadení. V príspevku na blogu <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> nájdete informácie o tom, ako získať dáta z KDL pomocou tejto funkcie.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Syslog</a></h3>
|
||||
<p><b>This is the preferred method for gaining information from a non-booting system.</b><br />
|
||||
The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file <span class="path">/boot/system/var/log/syslog</span>. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).</p>
|
||||
<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog persistent. If the option <span class="menu">Save syslog from previous session during boot</span> is activated in the boot loader options (as it is by default), you'll find the syslog of your last session as <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
If you're not able to boot to get to the previous_syslog, you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
|
||||
In the boot loader's <span class="menu">Debug menu</span> you should find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. Note: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
<p><b>Toto je preferovaný spôsob ako získať informácie zo systému, ktorý nejde naštartovať.</b><br />
|
||||
Syslog (skratka system log) obsahuje cenné informácie o tom, čo sa na vašom systéme stalo vrátane výstupu ladenia KDL. Zvyčajne je dobrý nápad pripojiť ho k súvisiacemu hláseniu v systéme Trac. Syslog sa zapisuje do súboru <span class="path">/boot/system/var/log/syslog</span>. Pretože zapisovanie do súbory vyžaduje, aby bol systém funkčný, je možné, že posledný výstup po výskyte problému s jadrom sa do syslogu už nedostal (obzvlášť pri samovoľných reštartoch alebo reláciách KDL, v ktorých nemožno pokračovať).</p>
|
||||
<p>Voľba <span class="menu">Zapnúť ladiaci syslog</span> v <span class="menu">menu Ladenie</span> zavádzača systému zabezpečí, že syslog bude trvalo uložený. Ak je v nastaveniach zavádzača systému zapnutá voľba <span class="menu">Uložiť syslog z predchádzajúcej relácie pri štarte</span> (predvolene je zapnutá), nájdete syslog vašej poslednej relácie v súbore <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
Ak sa vám nedarí spustiť systém, aby ste sa dostali k poslednému syslogu (previous_syslog), musíte vstúpiť do menu zavádzača podržaním klávesu <span class="key">SHIFT</span> počas štartu systému.<br />
|
||||
V <span class="menu">menu Ladenie</span> zavádzača by ste mali nájsť položky <span class="menu">Zobraziť syslog z predošlej relácie</span> a <span class="menu">Uložiť syslogz predošlej relácie</span>. Prvá z nich zobrazí syslog na obrazovke, druhá z nich vám umožní uložiť ho ako súbor na disk. Pamätajte, že momentálne sú na ukladanie súboru podporované iba zväzky so súborovým systémom FAT32. Ak chcete použiť disk USB, ale zapojili ste ho príliš neskoro a nebol zatiaľ rozpoznaný, môžete reštartovať počítač a znovu vstúpiť do menu zavádzača. Pozn.: Vyhnite sa automatickému spusteniu akéhokoľvek operačného systému, inak sa dáta posledného syslogu môžu stratiť.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">Výstup ladenia na obrazovku</a></h3>
|
||||
@@ -146,18 +147,18 @@ One or more pages of text will display on the screen, only the last few lines ne
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Chyby hardvéru/ovládačov</a></h2>
|
||||
<p>When dealing with a hardware/driver related bug, you should attach the following information as text files:</p>
|
||||
<p>Ak sa potýkate s chybou súvisiacou s hardvérom alebo ovládačom, mali by ste k hláseniu priložiť nasledovné informácie vo forme textových súborov:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>A detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Lists all used drivers.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Only available within <i>Kernel Debugging Land</i> (see above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option).</td></tr>
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>Podrobný výpis vášho hardvéru vrátane dodávateľa a PCI ID, podobný ako <span class="cli">lshw</span> a <span class="cli">lspci</span> v Linuxe.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Za predpokladu, že sa problém týka USB, je podobný ako <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Primárny protokol systému, ktorý Haiku používa, podobný ladeniu na obrazovku počas štartu systému. Príkazom <span class="cli">open</span> môžete vystrihnúť relevantnú časť syslogu v textovom editore.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Vypíše všetky použité ovládače.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Dostupné iba v rámci <i>(KDL) Kernel Debugging Land</i> (pozri vyššie). Zobrazuje použitie prerušení. Nemalo by sa vyskytovať mnoho takých, ktoré používajú viaceré zariadenia.</td></tr>
|
||||
<tr><td colspan="3">- Ladiaci výstup na obrazovke (voľba Bezpečný režim počas štartu systému).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>The first four commands are entered into Terminal. Add a <span class="cli"> > output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
|
||||
<p>Prvé štyri príkazy sú zadané do Terminálu. Keď za príkaz pridáte <span class="cli"> > output.txt</span>, výstup sa zapíše do textového súboru s názvom „output.txt“, ktorý môžete priložiť k vášmu hláseniu chyby alebo emailu.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">Čo ďalej?</a></h2>
|
||||
|
||||
@@ -45,6 +45,7 @@
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -85,9 +86,9 @@ When creating a new account, be certain to <b>provide your email address</b> as
|
||||
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">search</a> function for this.<br />
|
||||
After you have established that it's a unique bug, make your information as accurate as possible:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a>.</p></li>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision from <acronym title="Subversion, the source code management system we use">SVN</acronym> you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
|
||||
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
|
||||
@@ -43,6 +43,7 @@
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -83,9 +84,9 @@ When creating a new account, be certain to <b>provide your email address</b> as
|
||||
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">search</a> function for this.<br />
|
||||
After you have established that it's a unique bug, make your information as accurate as possible:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a>.</p></li>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision from <acronym title="Subversion, the source code management system we use">SVN</acronym> you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
|
||||
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
|
||||
@@ -0,0 +1,405 @@
|
||||
/*
|
||||
* Copyright 2008-2009, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* François Revol <[email protected]>
|
||||
* Stephan Aßmus <[email protected]>
|
||||
* Braden Ewing <[email protected]>
|
||||
* Humdinger <[email protected]>
|
||||
* Vincent Duvert <[email protected]>
|
||||
*/
|
||||
|
||||
html {
|
||||
margin: 0;
|
||||
padding: 0;
|
||||
background: #FFF;
|
||||
}
|
||||
|
||||
body {
|
||||
color: #333333;
|
||||
line-height: 1.5;
|
||||
margin: 0;
|
||||
padding: 0;
|
||||
font-family: "DejaVu Sans", Arial, Helvetica, sans-serif;
|
||||
}
|
||||
|
||||
/* link colors and text decoration */
|
||||
|
||||
a:link {
|
||||
font-weight: bold;
|
||||
text-decoration: none;
|
||||
color: #dc3c01;
|
||||
}
|
||||
a:visited {
|
||||
font-weight: bold;
|
||||
text-decoration: none;
|
||||
color: #892601;
|
||||
}
|
||||
a:hover, a:active {
|
||||
text-decoration: underline;
|
||||
color: #ff4500;
|
||||
}
|
||||
|
||||
/* Some headers act as anchors, don't give them a hover effect */
|
||||
|
||||
h2 a:hover, a:active {
|
||||
text-decoration: none;
|
||||
color: #0c3762;
|
||||
}
|
||||
h3 a:hover, a:active {
|
||||
text-decoration: none;
|
||||
color: #0c3762;
|
||||
}
|
||||
h4 a:hover, a:active {
|
||||
text-decoration: none;
|
||||
color: #0c3762;
|
||||
}
|
||||
h5 a:hover, a:active {
|
||||
text-decoration: none;
|
||||
color: #0c3762;
|
||||
}
|
||||
|
||||
/* heading and navigation */
|
||||
|
||||
#banner {
|
||||
position: relative;
|
||||
left: 0;
|
||||
top: 0;
|
||||
height: 84px;
|
||||
min-width: 59em;
|
||||
background: #eeeeee;
|
||||
}
|
||||
|
||||
#banner div {
|
||||
background: transparent url(images/logo.png) no-repeat scroll 10px 0;
|
||||
min-width: 59em;
|
||||
max-width: 70em;
|
||||
height: 100%;
|
||||
margin: 0 auto;
|
||||
}
|
||||
|
||||
#banner span {
|
||||
position: relative;
|
||||
top: 51px;
|
||||
left: 272px;
|
||||
color: #333333;
|
||||
text-transform: uppercase;
|
||||
letter-spacing: 3px;
|
||||
font-family: Myriad Pro,Myriad Web Pro Regular,Lucida Grande,Geneva,Trebuchet MS,sans-serif;
|
||||
font-weight: normal;
|
||||
font-size: 16px;
|
||||
}
|
||||
|
||||
div.nav {
|
||||
position: relative;
|
||||
min-width: 59em;
|
||||
left: 0;
|
||||
top: 0;
|
||||
background: #e0e0e0;
|
||||
padding: 0;
|
||||
}
|
||||
|
||||
div.nav div.inner {
|
||||
min-width: 59em;
|
||||
max-width: 70em;
|
||||
height: 100%;
|
||||
margin: 0 auto;
|
||||
text-align: right;
|
||||
padding: 0;
|
||||
}
|
||||
|
||||
div.nav div.inner span {
|
||||
margin-right: 40px;
|
||||
font-size: 0.8em;
|
||||
}
|
||||
|
||||
div.nav div.inner span a.uplink {
|
||||
font-weight: normal;
|
||||
}
|
||||
|
||||
/* Language selection menu */
|
||||
|
||||
ul.lang-menu {
|
||||
display: block;
|
||||
text-align: left;
|
||||
list-style-type: none;
|
||||
font-size: 0.8em;
|
||||
position: absolute;
|
||||
margin: 0;
|
||||
}
|
||||
|
||||
ul.lang-menu img {
|
||||
border: 0;
|
||||
padding-right: 5px;
|
||||
}
|
||||
|
||||
ul.lang-menu li {
|
||||
margin-left: 10px;
|
||||
padding: 2px 5px 2px 5px;
|
||||
background: #e0e0e0;
|
||||
display: none;
|
||||
}
|
||||
|
||||
ul.lang-menu:hover li {
|
||||
display: block;
|
||||
}
|
||||
|
||||
ul.lang-menu li:hover {
|
||||
background-color: #efefef;
|
||||
}
|
||||
|
||||
ul.lang-menu li.now {
|
||||
padding: 5px 5px 0 5px;
|
||||
display: block;
|
||||
background-color: inherit;
|
||||
}
|
||||
|
||||
ul.lang-menu li a {
|
||||
color: black;
|
||||
text-decoration: none;
|
||||
font-weight: normal;
|
||||
}
|
||||
|
||||
/* main content */
|
||||
#content {
|
||||
min-width: 59em;
|
||||
max-width: 70em;
|
||||
margin: 0 auto;
|
||||
}
|
||||
|
||||
#content div {
|
||||
margin-top: 30px;
|
||||
margin-left: 40px;
|
||||
margin-right: 40px;
|
||||
margin-bottom: 50px;
|
||||
font-size: 0.9em;
|
||||
}
|
||||
|
||||
/* contents box */
|
||||
|
||||
table.index {
|
||||
margin: 0px 0px 30px 30px;
|
||||
padding: 1px;
|
||||
border-width: 1px;
|
||||
border-style: dotted;
|
||||
border-color: #e0e0e0;
|
||||
float:right;
|
||||
}
|
||||
table.index tr.heading {
|
||||
background-color: #e0e0e0;
|
||||
text-align: center;
|
||||
font-weight: bold;
|
||||
font-size: 1.1em;
|
||||
}
|
||||
table.index tr.index {
|
||||
background-color: #eeeeee;
|
||||
}
|
||||
table.index td {
|
||||
padding: 5px 20px;
|
||||
}
|
||||
|
||||
table.index a:link, table.index a:visited {
|
||||
font-weight: normal;
|
||||
text-decoration: none;
|
||||
color: #dc3c01;
|
||||
}
|
||||
table.index a:hover, table.index a:active {
|
||||
text-decoration: underline;
|
||||
color: #ff4500;
|
||||
}
|
||||
|
||||
|
||||
/* Haiku User Guide styles and layout */
|
||||
|
||||
/* Rounded corner boxes */
|
||||
/* Common declarations */
|
||||
.box-info, .box-stop, .box-warning {
|
||||
-webkit-border-radius: 10px;
|
||||
-khtml-border-radius: 10px;
|
||||
-moz-border-radius: 10px;
|
||||
border-radius: 10px;
|
||||
border-style: dotted;
|
||||
border-width: thin;
|
||||
border-color: #dcdcdc;
|
||||
padding: 10px 15px 10px 80px;
|
||||
margin-bottom: 15px;
|
||||
margin-top: 15px;
|
||||
min-height: 42px;
|
||||
}
|
||||
.box-info {
|
||||
background: #e4ffde url(images/alert_info_32.png) 15px 15px no-repeat;
|
||||
}
|
||||
.box-warning {
|
||||
background: #fffbc6 url(images/alert_warning_32.png) 15px 15px no-repeat;
|
||||
}
|
||||
.box-stop {
|
||||
background: #ffeae6 url(images/alert_stop_32.png) 15px 15px no-repeat;
|
||||
}
|
||||
|
||||
/* More layout and styles */
|
||||
h1 {
|
||||
font-size: 1.3em;
|
||||
font-weight: bold;
|
||||
color: #0c3762;
|
||||
border-bottom: dotted thin #e0e0e0;
|
||||
margin-bottom: 25px;
|
||||
}
|
||||
h2 {
|
||||
font-size: 1.3em;
|
||||
font-weight: normal;
|
||||
color: #0c3762;
|
||||
border-bottom: dotted thin #e0e0e0;
|
||||
margin-top: 35px;
|
||||
}
|
||||
h3 {
|
||||
font-size: 1.2em;
|
||||
font-weight: normal;
|
||||
color: #0c3762;
|
||||
border-bottom: dotted thin #e0e0e0;
|
||||
margin-top: 30px;
|
||||
}
|
||||
h4 {
|
||||
font-size: 1.1em;
|
||||
font-weight: normal;
|
||||
color: #0c3762;
|
||||
margin-top: 30px;
|
||||
}
|
||||
h5 {
|
||||
font-size: 1.0em;
|
||||
font-weight: normal;
|
||||
color: #0c3762;
|
||||
margin-top: 30px;
|
||||
}
|
||||
p {
|
||||
text-align: justify;
|
||||
}
|
||||
ol {
|
||||
padding-left: 20px;
|
||||
}
|
||||
ul {
|
||||
padding-left: 14px;
|
||||
}
|
||||
li {
|
||||
line-height: 1.3;
|
||||
}
|
||||
td {
|
||||
vertical-align: top;
|
||||
}
|
||||
td.onelinetop {
|
||||
vertical-align: top;
|
||||
white-space: nowrap;
|
||||
}
|
||||
tt {
|
||||
background-color: #e2e2e2;
|
||||
font-size: 1.0em;
|
||||
font-family: monospace;
|
||||
}
|
||||
pre {
|
||||
border-color: #0c3762;
|
||||
border-style: dotted;
|
||||
border-width: thin;
|
||||
margin: 0em;
|
||||
padding: 1.5em;
|
||||
background-color: #f0f0f0;
|
||||
}
|
||||
pre.terminal { /* Terminal output*/
|
||||
border-color: #ffb11f;
|
||||
border-style: dotted;
|
||||
border-width: thin;
|
||||
margin: 0em;
|
||||
padding: 1.5em;
|
||||
background-color: #3a3a3a;
|
||||
color: #ffb11f;
|
||||
}
|
||||
.menu { /* Menu */
|
||||
font-size: 1.0em;
|
||||
font-family: serif;
|
||||
font-style: italic;
|
||||
color: #24225e;
|
||||
}
|
||||
.button { /* Button */
|
||||
font-size: 1.0em;
|
||||
font-family: serif;
|
||||
font-style: italic;
|
||||
color: #33583c;
|
||||
}
|
||||
.app { /* GUI Application name */
|
||||
font-size: 1.0em;
|
||||
font-family: serif;
|
||||
font-style: italic;
|
||||
color: #5e1c1c;
|
||||
}
|
||||
.cli { /* Shell command or file */
|
||||
background-color: #e8e8e8;
|
||||
font-size: 0.9em;
|
||||
font-family: monospace;
|
||||
}
|
||||
.path { /* File path */
|
||||
background-color: #e8e8e8;
|
||||
font-size: 0.9em;
|
||||
font-family: monospace;
|
||||
}
|
||||
.key { /* Shortcut (separate with */
|
||||
-webkit-border-radius: 3px;
|
||||
-khtml-border-radius: 3px;
|
||||
-moz-border-radius: 3px;
|
||||
border-radius: 3px;
|
||||
border-color: #c7c7c7;
|
||||
border-style: solid;
|
||||
border-width: 1px;
|
||||
padding: 0px 2px 0px 2px;
|
||||
background-color: #e8e8e8;
|
||||
font-family: serif;
|
||||
font-variant: small-caps;
|
||||
font-size: 0.8em;
|
||||
}
|
||||
|
||||
/* printer only pretty stuff */
|
||||
@media /*screen,*/print {
|
||||
/* suggest page orientation */
|
||||
@page { size: portrait; }
|
||||
.noprint {
|
||||
display: none;
|
||||
}
|
||||
/* hide header and nav bar */
|
||||
#banner {
|
||||
display:none;
|
||||
}
|
||||
|
||||
div.nav {
|
||||
display:none;
|
||||
}
|
||||
|
||||
/* some links we want to print the url along with (CSS2) */
|
||||
a.printurl:after {
|
||||
content: " <" attr(href) ">";
|
||||
font-weight: normal;
|
||||
font-size: small;
|
||||
}
|
||||
/* override for those we really don't want to print */
|
||||
a.noprinturl:after {
|
||||
content: "";
|
||||
}
|
||||
/* for acronyms we want their definitions inlined at print time */
|
||||
acronym[title]:after {
|
||||
font-size: small;
|
||||
content: " (" attr(title) ")";
|
||||
font-style: italic;
|
||||
}
|
||||
/* and not have mozilla dotted underline */
|
||||
acronym {
|
||||
border: none;
|
||||
}
|
||||
pre.terminal { /* Terminal output black on white*/
|
||||
background-color: #ffffff;
|
||||
color: #000000;
|
||||
}
|
||||
#content {
|
||||
margin: 0px;
|
||||
padding: 0px;
|
||||
}
|
||||
html {
|
||||
background: #FFF;
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,178 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <[email protected]>
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Reporting bugs</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Manual d'usuari</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/ca.png" alt="" /> Català</li>
|
||||
<li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_ca.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">La traducció d'aquesta pàgina encara no està acabada. Fins que ho sigui, algunes part correspondrà a la versió anglesa.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Índex</td></tr>
|
||||
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
|
||||
<a href="#report">Creating a bug report</a><br />
|
||||
<a href="#app">Application bugs</a><br />
|
||||
<a href="#server">Server bugs</a><br />
|
||||
<a href="#kernel">Kernel bugs</a><br />
|
||||
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
|
||||
<a href="#syslog">Syslog</a><br />
|
||||
<a href="#onscreen">On screen debug output</a><br />
|
||||
<a href="#hardware">Hardware/Driver bugs</a><br />
|
||||
<a href="#next">What's next?</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>Reporting bugs</h1>
|
||||
|
||||
<p>Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.</p>
|
||||
<p>To keep our bugtracker effective, it's essential to abide by the <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Bug Tracker Etiquette</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Getting a Trac account</a></h2>
|
||||
<p>To file a ticket, you need to have an account at <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku's Bugtracker</a>.<br />
|
||||
When creating a new account, be certain to <b>provide your email address</b> as it is necessary to obtain basic ticket modification privileges. Be sure to <b>check your spam folder</b> shortly afterwards, as the all important verification mail often ends up there.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Creating a bug report</a></h2>
|
||||
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">search</a> function for this.<br />
|
||||
After you have established that it's a unique bug, make your information as accurate as possible:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
|
||||
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Application bugs</a></h2>
|
||||
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Server bugs</a></h2>
|
||||
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
|
||||
Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (<span class="cli">bt</span> command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Kernel bugs</a></h2>
|
||||
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<ul>
|
||||
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
|
||||
<li><p>The system reboots spontaneously.</p></li>
|
||||
<li><p>The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards). Wait at least a minute to see, if anything happens.</p></li>
|
||||
<li><p>The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).</p></li>
|
||||
</ul>
|
||||
<p>Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could blacklist the responsible Wifi driver from your Haiku installation (see <a href="../../../userguide/en/bootloader.html">Boot Loader</a>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Shows the handled and unhandled hardware interrupts.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (aka continue)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
|
||||
</table>
|
||||
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
|
||||
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Syslog</a></h3>
|
||||
<p><b>This is the preferred method for gaining information from a non-booting system.</b><br />
|
||||
The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file <span class="path">/boot/system/var/log/syslog</span>. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).</p>
|
||||
<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog persistent. If the option <span class="menu">Save syslog from previous session during boot</span> is activated in the boot loader options (as it is by default), you'll find the syslog of your last session as <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
If you're not able to boot to get to the previous_syslog, you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
|
||||
In the boot loader's <span class="menu">Debug menu</span> you should find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. Note: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">On screen debug output</a></h3>
|
||||
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../../userguide/ca/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Hardware/Driver bugs</a></h2>
|
||||
<p>When dealing with a hardware/driver related bug, you should attach the following information as text files:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>A detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Lists all used drivers.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Only available within <i>Kernel Debugging Land</i> (see above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>The first four commands are entered into Terminal. Add a <span class="cli"> > output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">What's next?</a></h2>
|
||||
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
|
||||
non-descriptive comments.</p>
|
||||
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
|
||||
as 'fixed'.</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_ca.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,179 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* Matthias
|
||||
* Humdinger
|
||||
* taos
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Bugs melden</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User Guide</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/de.png" alt="" /> Deutsch</li>
|
||||
<li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_de.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td><a href="#account">Zugang zu Trac</a><br />
|
||||
<a href="#report">Bugreport erstellen</a><br />
|
||||
<a href="#app">Bugs in Anwendungen</a><br />
|
||||
<a href="#server">Bugs in Servern</a><br />
|
||||
<a href="#kernel">Bugs im Kernel</a><br />
|
||||
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
|
||||
<a href="#syslog">Syslog</a><br />
|
||||
<a href="#onscreen">Debug Ausgabe auf dem Bildschirm</a><br />
|
||||
<a href="#hardware">Bugs von Hardware/Treiber</a><br />
|
||||
<a href="#next">Bug gemeldet, und dann?</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>Bugs melden</h1>
|
||||
|
||||
<p>Da es für die Haiku-Entwickler unmöglich ist, jede denkbare Hardware-Kombination oder jede mögliche Anwendungsweise eines Programms zu testen, ist es eine große Hilfe, wenn Fehler gemeldet werden. Da Haiku noch recht jung ist, sind Bugs nicht Ungewöhnliches. Nur mit Hilfe der Anwender können wir Haiku gemeinsam Stück für Stück perfektionieren.</p>
|
||||
<p>Damit unser "Bugtracker" - also die Liste aller gefundenen Fehler - effektiv funktioniert, ist eine grundlegende <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Bug Tracker Etiquette</a> zu wahren.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Zugang zu Trac</a></h2>
|
||||
<p>Um ein Fehler-Ticket aufzugeben, muss man registrierter Benutzer beim <a href="http://dev.haiku-os.org/register" title="Registerierung bei Haikus Bugtracker">Bugtracker</a> sein.<br /> Um sich anzumelden ist eine <b>gültige E-Mail Adresse</b> notwendig. Sollte nach dem Anmelden keine Bestätigungsmail ankommen, sollte man mal seinen <b>Spam-Ordner</b> überprüfen.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Bugreport erstellen</a></h2>
|
||||
<p>Bevor man einen Fehler meldet, sollte man sich <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">sicher sein</a>, dass das nicht schon geschehen ist. Hierzu kann auch die <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">Suchfunktion</a> verwendet werden.<br />
|
||||
Nach dieser Überprüfung sollte man so genau wie möglich den Fehler beschreiben:</p>
|
||||
<ul>
|
||||
<li><p>Der Fehler sollte mit einer aktuellen Version von Haiku reproduzierbar sein. Zum Testen gibt es installierbare <a href="http://download.haiku-os.org">Nightly Images</a>.</p></li>
|
||||
<li><p>Wie wurde Haiku verwendet (auf echter Hardware oder virtualisiert unter VMWare, QEMU oder ähnlichem)?</p></li>
|
||||
<li><p>Welche Haiku-Versionsnummer wurde verwendet? Die Version ist unter <span class="menu">Über Haiku...</span> im Deskbar Menü zu finden. Wie genau Haiku kompiliert wurde (gcc2, gcc4, gcc2hybrid, gcc4hybrid), ist ebenfalls von Interesse. Die runterladbaren Images sind entsprechend benannt; Leute, die sich ihr Haiku selber zusammenbauen, sollten wissen wie sie das gemacht haben.</p></li>
|
||||
<li><p>Der Fehler sollte so präzise wie möglich beschrieben werden. Welches Verhalten wurde erwartet und was wurde statt dessen beobachtet?</p></li>
|
||||
<li><p>Wann tritt der Fehler auf? Nur mit einer Schritt-für-Schritt Anleitung können die Entwickler den Bug nachstellen und beheben.</p></li>
|
||||
<li><p>An den Fehlerbericht sollten so viele Informationen wie möglich angehängt werden. Handelt es sich um einen Bug in der grafischen Oberfläche oder einer der Anwendungen, ist ein Bildschirmfoto mittels der <span class="key">DRUCK</span> Taste hilfreich.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Bugs in Anwendungen</a></h2>
|
||||
<p>Stürzt eine Anwendung ab, sollte man den Debugger aus dem erscheinenden Hinweisfenster aufrufen. Dadurch wird ein Terminal mit gdb (dem GNU Debugger) geöffnet. Gibt man dort <span class="cli">bt</span> ein, wird ein sogenannter "backtrace" erstellt, der komplett (auch mit dem Teil bevor <span class="cli">bt</span> eingegeben wurde) mit an die Fehlermeldung angehängt werden sollte.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Bugs in Servern</a></h2>
|
||||
<p>Stürzen lebenswichtige Server wie der App Server, der Registrar oder der Input Server ab, bekommt man nicht den gewöhnlichen Crash-Hinweis zu sehen. Stattdessen wird der gesamte Bildschirm weiß und der gdb wird gestartet, der seine Ausgabe direkt auf den Bildschirm schreibt. Unter Umständen kann man immer noch die Maus bewegen, die daraufhin das Weiß und die gdb Ausgabe übermalt. Noch laufende Anwendungen, wie ProcessController oder die Uhr in der Deskbar, tun das vielleicht auch noch.<br />
|
||||
Außer dass alles etwas unansehnlicher und unbequemer ist, gilt eigentlich das gleiche wie für Bugs in Anwendungen. Am wichtigsten ist das sichern eines "backtrace" mittels <span class="cli">bt</span>. Weil man den Text ja nicht mehr irgendwohin kopieren kann, müsste man die Ausgabe per Kamera festhalten.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Bugs im Kernel</a></h2>
|
||||
<p>Fehler im Kernel haben normalerweise die schwersten Auswirkungen und sind zugleich am schwierigsten zu debuggen. Es gibt unterschiedliche Symptome, die auf ein Problem von Kernel oder Treiber hindeuten:</p>
|
||||
<ul>
|
||||
<li><p>Das System betritt selbständig das Kernel Debugging Land (KDL) . Der obere Teil des Bildschirms wird weiß und einige Zeilen Text erscheinen. Die zweite Zeile verkündet "<i>Welcome to Kernel Debugging Land...</i>", die darüber beschreibt den unmittelbaren Grund für die Reise ins KDL.</p></li>
|
||||
<li><p>Das System führt einen spontanen Neustart aus.</p></li>
|
||||
<li><p>Das System friert komplett ein. Die Maus lässt sich nicht mehr bewegen und Anwendungen aktualisieren ihre Oberfläche nicht mehr. Ein wichtiger Test in so einer Situation ist, ob man das KDL noch mit der Tastenkombination <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> ist dabei meist die <span class="key">DRUCK</span> Taste) erreichen kann. Man sollte zumindest eine Minute warten, ob sich was tut.</p></li>
|
||||
<li><p>Das System fährt nicht mehr richtig hoch. Unter Umständen führt es spontan einen Neustart durch oder bleibt an einer Stelle stecken, vielleicht bei einem bestimmten Symbol des Boot Bildschirms. In letzterem Falle sollte man auch mal ein <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> versuchen.</p></li>
|
||||
<li><p>Das ganze System oder eine bestimmte Hardwarekomponente funktioniert nicht richtig. Es könnte beispielsweise nur sehr langsam laufen, Fehler könnten auftreten oder etwas funktioniert überhaupt nicht. Verweigert eine Hardwarekomponente die Arbeit komplett, sollte man natürlich erst mal checken, ob Haiku sie momentan überhaupt treibermäßig unterstützt, indem man zum Beispiel auf der Mainlingliste oder im Forum nachfragt.</p></li>
|
||||
</ul>
|
||||
<p>Während nur der letzte Punkt explizit auf eine Hardware-Ursache eingeht, können auch alle anderen Symptome auf Fehler in einem Hardware Treiber hindeuten. Hat man einen Verdacht welche Hardware oder entsprechender Treiber mit dem Problem zu tun haben könnte, sollte man prüfen ob das Entfernen oder Deaktivieren von Hardware oder Treiber Abhilfe schafft. Wenn man das Problem beispielsweise beim WLAN vermutet, könnte diese Funktion vielleicht im BIOS ausgeschaltet werden. Wenn nicht, kann man auch den entsprechenden Treiber auf eine "Schwarze Liste" setzen und so im System deaktivieren (siehe <a href="../../../userguide/de/bootloader.html">Boot Loader</a>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>Stürzt das System nicht von selbst ins KDL, kann man das auch absichtlich mit der Tastenkombination <span class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span> erreichen.<br />
|
||||
Im KDL kann es passieren, dass die Tastatur nicht mehr funktioniert. PS/2 Tastaturen gehen immer, USB Tastaturen an UHCI Controllern nur wenn man vorher schonmal per Tastenkombination das KDL betreten hat. USB OHCI wird zur Zeit noch gar nicht unterstützt.</p>
|
||||
<p>Das KDL ist eine Art Konsole. Es lassen sich Befehle eingeben, die Informationen über das System ausgeben. Folgende Befehle sind von besonderen Interesse:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (auch "sc")</td><td> </td><td>Zeigt einen "backtrace" (oder auch "stack crawl") wo genau der Fehler aufgetreten ist. Ist das System von selbst ins KDL gefallen, sollte man diesen Befehl unbedingt ausführen.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Zeigt die unbenutzten und verwendeten Interrupts.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (auch "continue")</td><td> </td><td>Verlässt den Kernel Debugger und das System läuft - soweit möglich - normal weiter.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Führt einen unmittelbaren Neustart durch. Alle ungespeicherten Daten gehen verloren und selbst was man gespeichert hat, aber noch nicht auf die Platte geschrieben wurde, ist weg.</td></tr>
|
||||
</table>
|
||||
<p>Weitere Infos gibt es im Artikel <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a> (Englisch).</p>
|
||||
<p>Die Ausgaben im KDL werden zum seriellen Port geschickt (falls man einen hat und ein entsprechendes Nullmodemkabel samt zweiten Rechner, kann man die Ausgaben in einem Terminalprogramm aufnehmen). Außerdem werden sie ins Syslog geschrieben. Wenn man das KDL allerdings nicht verlassen kann, wird auch nichts ins Syslog geschrieben. Es gibt aber eine Bootloader Debug Option, die das trotzdem möglich macht (siehe weiter unten).</p>
|
||||
<p>Von Ausgaben im KDL lassen sich auch QR-Codes erzeugen, die dann mit einem Smartphone oder ähnlichem zu Text konvertiert werden können. Der Blogpost <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> (Englisch) erklärt wie man mit diesem Feature Daten aus dem Kernel Debugging Land herausbekommt.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Syslog</a></h3>
|
||||
<p><b>Dies ist die beste Methode Informationen über ein nicht-bootendes System zu gewinnen.</b><br />
|
||||
Das Syslog (kurz für System Log) enthält wertvolle Infos was im System abläuft, einschließlich der Ausgaben einer KDL Sitzung. Man sollte es immer an einen Trac Ticket hängen wenn es etwas mit dem Kernel zu tun haben könnte. Das Syslog befindet sich in der Datei <span class="path">/boot/common/var/log/syslog</span>. Um in eine Datei schreiben zu können, braucht man ein funktionierendes System. Tritt ein Problem im Kernel auf (insbesondere bei spontanen Neustarts und nicht-fortsetzbaren KDL Sitzungen), kann es daher passieren dass es die letzten Ausgaben nicht mehr ins Syslog schaffen.</p>
|
||||
<p>Durch die Option <span class="menu">Enable debug syslog</span> im <span class="menu">Debug menu</span> des Bootloaders wird das Syslog im Speicher gehalten.
|
||||
Ist die Einstellung <span class="menu">Save syslog from previous session during boot</span> in den Bootloader Optionen aktiviert (wie es standardmäßig der Fall ist), findet man das Syslog der letzten Sitzung unter <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
Gelingt das Booten nicht, um an das previous_syslog zu kommen, muss man beim Neustart das Bootloader Menü mittels gedrückter <span class="key">SHIFT</span> Taste aufrufen.<br />
|
||||
Dort sollte man im <span class="menu">Debug menu</span> die Einträge <span class="menu">Display syslog from previous session</span> und <span class="menu">Save syslog from previous session</span> sehen. Ersterer zeigt das Syslog direkt auf dem Bildschirm an, mit letzterem lässt es sich speichern. Momentan geht das nur auf FAT32 formatierten Medien. Möchte man dafür einen USB-Stick benutzen, den man allerdings erst zu spät reingesteckt hat und der deswegen nicht erkannt wurde, kann man den Rechner nochmals resetten und das Bootloader Menü erneut aufrufen. Es gilt aber immer noch: Bootet man ausversehen ein Betriebssystem, sind die Syslog Daten weg.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">Debug Ausgabe auf den Bildschirm</a></h3>
|
||||
<p><b>Die Ausgabe auf dem Bildschirm ist nur bei ganz bestimmten Situationen sinnvoll und hat bekanntermaßen Timing-Probleme. Es sollte also wirklich nur im Notfall benutzt werden.</b><br />
|
||||
Das ist zum Beispiel der Fall wenn Haiku nicht ganz hochfährt und Bootloader's <span class="menu">Debug syslog option</span> irgendwie nicht funktioniert. Noch bevor das Haiku Bootlogo erscheint, die <span class="key">SHIFT</span> Taste gedrückt halten, um das Bootloader Menü aufzurufen. Von hier in das Menü <span class="menu">Select safe mode options</span> wechseln und dort weiter unten <span class="menu">[ ] Enable on screen debug output</span> aktivieren. (Die anderen Optionen kann man auch mal probieren, um zu versuchen Haiku erfolgreich zu booten. Wenn Haiku nur mit einer oder mehreren aktivierten Optionen hochfahren kann, sollte man natürlich erwähnen welche das sind.)<br />
|
||||
Abschließend geht man auf <span class="menu">Return to main menu</span> und dann <span class="menu">Continue booting</span>.<br />
|
||||
Auf dem Bildschirm werden einige Seiten Text ausgegeben, von denen aber nur die letzten paar für einen Bugreport interessant sind. Der Userguide hat noch weitere Infos zum <a href="../../../userguide/de/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Bugs von Hardware/Treiber</a></h2>
|
||||
<p>Wenn ein Fehler gemeldet wird, der Hardware oder Treiber betrifft, sollten folgende Informationen als Textdateien an den Fehlerbericht angehängt werden:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>Eine detaillierte Auflistung aller vorhandener Hardware inklusive "vendor id" und "pci id"; ähnlich den Befehlen <span class="cli">lshw</span> und <span class="cli">lspci</span> unter Linux.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Bei Fehlern im Zusammenhang mit USB, ähnlich dem Befehlt <span class="cli">lsusb</span> unter Linux.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Die zentrale Log-Datei von Haiku. Mit dem Befehl <span class="cli">open</span> kann das Log im Texteditor auf eine sinnvolle Länge gekürzt werden.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Eine Auflistung aller verwendeten Treiber.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Nur im <i>Kernel Debugging Land</i> (siehe weiter oben). Es zeigt eine Liste aller verwendeter "Interrupts". Wenn sich mehrere Geräte zuviele von ihnen teilen, ist das schlecht.</td></tr>
|
||||
<tr><td colspan="3">- "On screen debug output" (die Bootloader Debug Option zur Ausgabe auf dem Bildschirm).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>Die ersten vier dieser Befehle sind im Terminal einzugeben. Mit dem Zusatz "<span class="cli"> > output.txt</span>" an den Befehl wird dessen Ausgabe in die Datei "output.txt" gespeichert, die dann an den Fehlerbericht angehängt werden kann.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">Bug gemeldet, und dann?</a></h2>
|
||||
<p>Nachdem ein Fehler gemeldet wurde, wird sich ein Entwickler ihm annehmen und bewerten. Da es sich bei allen Entwicklern um Freiwillige handelt, die in ihrer Freizeit programmieren, kann es durchaus etwas dauern, bis man eine Rückmeldung erhält. Je mehr Informationen man einer Fehlermeldung beifügt oder nachreicht, um so leichter ist es für den Programmierer, diesen zu beheben.</p>
|
||||
<p>Wenn man einen Fehler gemeldet hat ist es damit nicht abgeschlossen, eigentlich ist es erst der Anfang und man wird Teil des Entwicklungs-Prozesses von Haiku. Es ist durchaus möglich und eigentlich auch zu erwarten, dass sich ein Entwickler meldet, um näheres zu den Umständen des Fehler-Reports zu erfahren. Hier gilt wieder: je mehr man dem Entwickler helfen kann, um so leichter tut er sich mit der Fehlerbehebung. Erst wenn der Fehler als 'fixed' - also behoben - markiert ist, kann man sich zurücklehnen, mit dem guten Gefühl etwas beigetragen zu haben.</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_de.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,155 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2010-2011, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* Humdinger
|
||||
* taos
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta http-equiv="Content-Style-Type" content="text/css" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>WLAN</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User Guide</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/de.png" alt="" /> Deutsch</li>
|
||||
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
|
||||
<span>
|
||||
<a href="../welcome_de.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
|
||||
<h2>WLAN in Haiku</h2>
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="hardware" rel="nofollow" id="hardware">Wahrscheinlich unterstützte Hardware</a></h3>
|
||||
<p>Alle FreeBSD 8 WLAN Treiber sollten funktionieren. Jedoch keine PCMCIA, CardBus, ExpressCard, USB oder ISA basierte Karten. Unterstützt wird nur PCI, miniPCI, PCI-Express, miniPci-Express und PCI-X.<br />
|
||||
Darunter:</p>
|
||||
<ul>
|
||||
<li><p><i>aironetwifi</i> unterstützt zumindest<br />
|
||||
Cisco Aironet 350 Serie<br />
|
||||
Aironet PCI4500<br />
|
||||
Aironet PCI4800<br />
|
||||
</p></li>
|
||||
<li><p><i>atheroswifi</i> unterstützt fast alle Chipsets (allerdings keine AR9285 Chips)</p></li>
|
||||
<li><p><i>broadcom43xx</i> unterstützt<br />
|
||||
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 und BCM4318</p>
|
||||
</li>
|
||||
<li><p><i>ipw2100</i> unterstützt Intel Pro Wireless 2100 Chips</p></li>
|
||||
<li><p><i>iprowifi2200</i> unterstützt Intel Pro Wireless<br />
|
||||
2200BG<br />
|
||||
2225BG<br />
|
||||
2915ABG</p>
|
||||
</li>
|
||||
<li><p><i>iprowifi3945</i> unterstützt Intel Pro Wireless Chips 3945</p></li>
|
||||
<li><p><i>iprowifi4965</i> unterstützt Intel Pro Wireless 4965 Chips</p></li>
|
||||
<li><p><i>marvell88w8335</i> unterstützt<br />
|
||||
Marvell Libertas 88W8310<br />
|
||||
Marvell Libertas 88W8335</p></li>
|
||||
<li><p><i>marvell88w8363</i> unterstützt 88W8363 Chips</p></li>
|
||||
<li><p><i>ralinkwifi</i> unterstützt<br />
|
||||
RT2560<br />
|
||||
RT2561S<br />
|
||||
RT2561<br />
|
||||
RT2661</p>
|
||||
</li>
|
||||
<li><p>ralink2860 unterstützt Ralink RT2860</p></li>
|
||||
<li><p><i>wavelanwifi</i> unterstützt zumindest<br />
|
||||
3Com Airconnect<br />
|
||||
GLPRISM2 WaveLAN<br />
|
||||
Intersil Prism3<br />
|
||||
Intersil Prism2.5<br />
|
||||
Linksys WDT11<br />
|
||||
Netgear MA301<br />
|
||||
PRISM2STA WaveLAN<br />
|
||||
Siemens SpeedStream<br />
|
||||
SMC 2602W<br />
|
||||
Us Robotics 2415<br />
|
||||
Addtron AWA-100 PCI</p></li>
|
||||
</ul>
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="connect" rel="nofollow" id="connect">Verbindung zum Funknetzwerk</a></h3>
|
||||
<p>Neben unverschlüsselten Netzwerken unterstützt Haiku auch mittels <a href="#wep-notes" rel="nofollow">WEP Schlüssel</a> verschlüsselte Netze. WEP ist allerdings eine bereits veraltete Verschlüsselungsmethode, also nicht wirklich sicher.</p>
|
||||
<p>Vom Terminal aus lassen sich mit dem Befehl <span class="cli">ifconfig</span> vorhandene Funknetze auflisten und mit einem Verbindung aufnehmen ("join") oder wieder trennen ("leave"):</p>
|
||||
<pre class="terminal">ifconfig [Wifi_Geräte_Pfad] [list|join|leave] (Schlüssel)</pre>
|
||||
<p>Der <tt>Wifi_Geräte_Pfad</tt> wird in den <span class="app">Netzwerk</span> Einstellungen angezeigt oder mit dem Befehl <span class="cli">ifconfig -a</span> im Terminal.</p>
|
||||
<p>Nachfolgend einige Beispiele wie mit einem Funknetzwerk namens <i>wifitopia</i> eine Verbindung hergestellt wird. Als Netzwerkkarte wird <tt>/dev/net/iprowifi3945/0</tt> angenommen.</p>
|
||||
<h4>Alle Funknetzwerke auflisten:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
|
||||
<h4>Verbindung mit einem unverschlüsselten Funknetzwerk:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
|
||||
<h4>Verbindung mit einem <a href="#wep-notes">WEP verschlüsselten </a> Funknetzwerk: (ASCII Passwort)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia DasPasswort</pre>
|
||||
<h4>Verbindung mit einem <a href="#wep-notes">WEP verschlüsselten </a> Funknetzwerk: (64 Bit Hex-Passwort)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
|
||||
<h4>Verbindung zum Funknetzwerk trennen:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="auto-connect" rel="nofollow" id="auto-connect">Automatische Verbindung zu einem Funknetzwerk</a></h3>
|
||||
<p>Nach dem Hochfahren kann man sich auch automatisch mit einem durch seine SSID benannten Netzwerk verbinden. Dazu müssen Funknetzwerke und die entsprechenden Passwörter in der Datei <tt><acronym title="/boot/common/settings/network/wireless_networks">/boot/Allgemein/settings/network/wireless_networks</acronym></tt> in folgendem Format abgelegt werden:</p>
|
||||
<pre>network wifitopia {
|
||||
password DasPasswort
|
||||
}</pre>
|
||||
<p>Legt man diese Konfigurationsdatei nicht an, verbindet sich das System automatisch mit dem ersten unverschlüsselten Netzwerk, das es findet.</p>
|
||||
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP Info</strong></a></p>
|
||||
<ul>
|
||||
<li>64-bit WEP benutzt ein 40-bit Passwort, das sind 5 Buchstaben oder 10 Hex-Werte</li>
|
||||
<li>128-bit WEP benutzt ein 104-bit Passwort, das sind 13 Buchstaben oder 26 Hex-Werte</li>
|
||||
<li>Hex-Werte sind die Zahlen 0-9 und Buchstaben A bis F (in <tt>ifconfig</tt> mit einem vorangestellten '0x')</li>
|
||||
</ul>
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="wpa" rel="nofollow" id="wpa">WPA Verschlüsselung</a></h3>
|
||||
<p>Momentan gibt es noch keine WPA Verschlüsselung unter Haiku. <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">Ein großer Schritt</a> in diese Richtung wurde allerdings bereits unternommen.</p>
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
|
||||
<p>Um die Firmware für Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx & Marvell 88W8335 zu installieren, startet man</p>
|
||||
<pre class="terminal">~> install-wifi-firmwares.sh
|
||||
</pre>
|
||||
<p>Die Intel ipw2100 und iprowifi22xx benötigen zur Installation keine Internetverbindung, da es die Lizenzbestimmungen erlauben, die Original-Firmware gleich mitzuliefern. Sie verlangen jedoch eine Zustimmung des Benutzers vor ihrer Installtion. Für Broadcom 43xx & Marvell 88W8335 ist hingegen eine funktionierende Internetverbindung nötig, da die entsprechenden Dateien mit der Firmware Haiku nicht beiliegen dürfen.</p>
|
||||
<p>Leute, die ihr eigenes Haiku Image bauen, können ihre <span class="cli">build/jam/UserBuildConfig</span> entsprechend anpassen. Details dazu und eventuelle Updates zum WLAN-Thema finden sich in der <a href="">Online-Version dieses Dokuments</a> (Englisch).</p>
|
||||
<p>Wer die Firmware runterladen muss, aber unter Haiku keine Internetverbindung hat, kann das in diesem Online Dokument angebotene <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">Shell Skript</a> benutzen. Damit werden alle nötigen Dateien heruntergeladen und in ein Zip gepackt, das man unter Haiku in <tt>/boot</tt> entpacken kann. Dann stehen alle Dateien zur Verfügung, die von install-wifi-firmwares.sh benötigt werden.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_de.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,177 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Reporting bugs</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
</div>
|
||||
|
||||
<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/bugreports.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_en.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
|
||||
<a href="#report">Creating a bug report</a><br />
|
||||
<a href="#app">Application bugs</a><br />
|
||||
<a href="#server">Server bugs</a><br />
|
||||
<a href="#kernel">Kernel bugs</a><br />
|
||||
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
|
||||
<a href="#syslog">Syslog</a><br />
|
||||
<a href="#onscreen">On screen debug output</a><br />
|
||||
<a href="#hardware">Hardware/Driver bugs</a><br />
|
||||
<a href="#next">What's next?</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>Reporting bugs</h1>
|
||||
|
||||
<p>Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.</p>
|
||||
<p>To keep our bugtracker effective, it's essential to abide by the <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Bug Tracker Etiquette</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Getting a Trac account</a></h2>
|
||||
<p>To file a ticket, you need to have an account at <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku's Bugtracker</a>.<br />
|
||||
When creating a new account, be certain to <b>provide your email address</b> as it is necessary to obtain basic ticket modification privileges. Be sure to <b>check your spam folder</b> shortly afterwards, as the all important verification mail often ends up there.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Creating a bug report</a></h2>
|
||||
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">search</a> function for this.<br />
|
||||
After you have established that it's a unique bug, make your information as accurate as possible:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
|
||||
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Application bugs</a></h2>
|
||||
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Server bugs</a></h2>
|
||||
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
|
||||
Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (<span class="cli">bt</span> command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Kernel bugs</a></h2>
|
||||
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<ul>
|
||||
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
|
||||
<li><p>The system reboots spontaneously.</p></li>
|
||||
<li><p>The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards). Wait at least a minute to see, if anything happens.</p></li>
|
||||
<li><p>The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).</p></li>
|
||||
</ul>
|
||||
<p>Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could blacklist the responsible Wifi driver from your Haiku installation (see <a href="../../../userguide/en/bootloader.html">Boot Loader</a>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Shows the handled and unhandled hardware interrupts.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (aka continue)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
|
||||
</table>
|
||||
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
|
||||
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Syslog</a></h3>
|
||||
<p><b>This is the preferred method for gaining information from a non-booting system.</b><br />
|
||||
The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file <span class="path">/boot/system/var/log/syslog</span>. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).</p>
|
||||
<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog persistent. If the option <span class="menu">Save syslog from previous session during boot</span> is activated in the boot loader options (as it is by default), you'll find the syslog of your last session as <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
If you're not able to boot to get to the previous_syslog, you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
|
||||
In the boot loader's <span class="menu">Debug menu</span> you should find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. Note: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">On screen debug output</a></h3>
|
||||
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../../userguide/en/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Hardware/Driver bugs</a></h2>
|
||||
<p>When dealing with a hardware/driver related bug, you should attach the following information as text files:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>A detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Lists all used drivers.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Only available within <i>Kernel Debugging Land</i> (see above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>The first four commands are entered into Terminal. Add a <span class="cli"> > output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">What's next?</a></h2>
|
||||
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
|
||||
non-descriptive comments.</p>
|
||||
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
|
||||
as 'fixed'.</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_en.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,158 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2010-2011, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta http-equiv="Content-Style-Type" content="text/css" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Wifi</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
</div>
|
||||
|
||||
<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/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
</ul>
|
||||
|
||||
<span>
|
||||
<a href="../welcome_en.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
|
||||
<h2>Wifi in Haiku</h2>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="hardware" rel="nofollow" id="hardware">Expected supported hardware</a></h3>
|
||||
<p>All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, PCI-Express, miniPci-Express and PCI-X are supposed to work.<br />
|
||||
This includes:
|
||||
</p>
|
||||
<ul>
|
||||
<li><p><i>aironetwifi</i> supporting at least<br />
|
||||
Cisco Aironet 350 Series<br />
|
||||
Aironet PCI4500<br />
|
||||
Aironet PCI4800<br />
|
||||
</p></li>
|
||||
<li><p><i>atheroswifi</i> supporting almost every chipset outthere (though no AR9285 chips)</p></li>
|
||||
<li><p><i>broadcom43xx</i> supporting<br />
|
||||
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318
|
||||
</p></li>
|
||||
<li><p><i>ipw2100</i> supporting Intel Pro Wireless 2100 chips</p></li>
|
||||
<li><p><i>iprowifi2200</i> supporting Intel Pro Wireless<br />
|
||||
2200BG<br />
|
||||
2225BG<br />
|
||||
2915ABG
|
||||
</p></li>
|
||||
<li><p><i>iprowifi3945</i> supporting Intel Pro Wireless 3945 chips</p></li>
|
||||
<li><p><i>iprowifi4965</i> supporting Intel Pro Wireless 4965 chips</p></li>
|
||||
<li><p><i>marvell88w8335</i> supporting<br />
|
||||
Marvell Libertas 88W8310<br />
|
||||
Marvell Libertas 88W8335
|
||||
</p></li>
|
||||
<li><p><i>marvell88w8363</i> supporting the 88W8363 chips</p></li>
|
||||
<li><p><i>ralinkwifi</i> supporting<br />
|
||||
RT2560<br />
|
||||
RT2561S<br />
|
||||
RT2561<br />
|
||||
RT2661
|
||||
</p></li>
|
||||
<li><p>ralink2860 supporting Ralink RT2860</p></li>
|
||||
<li><p><i>wavelanwifi</i> supporting at least<br />
|
||||
3Com Airconnect<br />
|
||||
GLPRISM2 WaveLAN<br />
|
||||
Intersil Prism3<br />
|
||||
Intersil Prism2.5<br />
|
||||
Linksys WDT11<br />
|
||||
Netgear MA301<br />
|
||||
PRISM2STA WaveLAN<br />
|
||||
Siemens SpeedStream<br />
|
||||
SMC 2602W<br />
|
||||
Us Robotics 2415<br />
|
||||
Addtron AWA-100 PCI
|
||||
</p></li>
|
||||
</ul>
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="connect" rel="nofollow" id="connect">Connecting to a wireless network</a></h3>
|
||||
<p>Besides of course unencrypted networks, Haiku has preliminary support for accessing wireless networks via <a href="#wep-notes" rel="nofollow">WEP encryption keys</a>. WEP is an early encryption method, although not the most secure.</p>
|
||||
<p>You can list available networks, join and leave them with the command <span class="cli">ifconfig</span> from Terminal:</p>
|
||||
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
|
||||
<p>You can find your <tt>wifi_device_path</tt> in the <span class="app">Network</span> preferences applet, or by executing <span class="cli">ifconfig -a</span>.</p>
|
||||
<p>Below are a few examples of connecting to a wireless network named <i>wifitopia</i>. For these examples we are assuming your wifi network card is <tt>/dev/net/iprowifi3945/0</tt>.</p>
|
||||
<h4>Listing wireless networks:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
|
||||
<h4>Joining unsecured wireless network:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
|
||||
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (ascii password)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
|
||||
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (64-bit hex password)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
|
||||
<h4>Leaving a wireless network:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="auto-connect" rel="nofollow" id="auto-connect">Automatically connecting to a wireless network</a></h3>
|
||||
<p>To make your system connect to a given SSID at each boot automatically, you can specify your wireless networks and passwords in <tt>/boot/common/settings/network/wireless_networks</tt> with the following format:</p>
|
||||
<pre>network wifitopia {
|
||||
password mypassword
|
||||
}</pre>
|
||||
<p>If you don't create this configuration file, the system will connect to the first unencrypted network it finds.</p>
|
||||
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP notes</strong></a></p>
|
||||
<ul>
|
||||
<li>64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex digits</li>
|
||||
<li>128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex digits</li>
|
||||
<li>hexadecimal digits = characters 0-9 and A through F (prepended with "0x" in <tt>ifconfig</tt>)</li>
|
||||
</ul>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="wpa" rel="nofollow" id="wpa">WPA encryption</a></h3>
|
||||
<p><p>At the moment there is no WPA encryption available in Haiku, though there have been <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">some efforts</a> bringing it significantly closer.</p></p>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
|
||||
<p>To install the firmware for Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you need to run</p>
|
||||
<pre class="terminal">install-wifi-firmwares.sh
|
||||
</pre>
|
||||
<p>The Intel ipw2100 and iprowifi22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.</p>
|
||||
<p>People building their own Haiku image can modify their <span class="cli">build/jam/UserBuildConfig</span> accordingly. Details for that and general updates on the wifi topic are found at the <a href="http://www.haiku-os.org/guides/wifi">online version of this document</a>.</p>
|
||||
<p>If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">shell script</a>, which will create a zip file for you to extract to Haiku's <tt>/boot</tt>. After that you'll have all files needed by install-wifi-firmwares.sh.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_en.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,178 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* miguel~1.mx
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Reportar fallos</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Guía del usuario</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/es.png" alt="" /> Español</li>
|
||||
<li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_es.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">La traducción de esta página no está completa aún. Hasta que esté, las partes sin terminar vienen en su inglés original.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
|
||||
<a href="#report">Creating a bug report</a><br />
|
||||
<a href="#app">Application bugs</a><br />
|
||||
<a href="#server">Server bugs</a><br />
|
||||
<a href="#kernel">Kernel bugs</a><br />
|
||||
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
|
||||
<a href="#syslog">Syslog</a><br />
|
||||
<a href="#onscreen">On screen debug output</a><br />
|
||||
<a href="#hardware">Hardware/Driver bugs</a><br />
|
||||
<a href="#next">What's next?</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>Reportar fallos</h1>
|
||||
|
||||
<p>Ya que nuestros desarrolladores no pueden verificar todas las combinaciones de hardware, ni todas las posibles maneras de interactuar con el sistema operativo, confiamos que los usuarios nos den retroalimentación sobre cómo funcionan las cosas de su lado. Dado que Haiku todavía es muy joven, muy probablemente encontrará fallos. Le agradecemos por tomarse el tiempo para reportarlos. Juntos podemos mejorar a Haiku, bit a bit.</p>
|
||||
<p>Para mantener nuestro rastreador de fallos efectivo, es esencial supeditarse a la <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Etiqueta del rastreador de fallos</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Getting a Trac account</a></h2>
|
||||
<p>Para llenar un reporte, necesita tener una cuenta en <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">el Rastreador de fallos de Haiku</a>.<br />
|
||||
Cuando se cree una cuenta nueva, asegurese de <b>proporcionar su correo electrónico</b> pues es necesario obtener privilegios de modificación básica del reporte. Asegúrese de <b>comprobar su carpeta de correo no deseado (spam)</b> brevemente después, ya que a menudo toda verificación de correo importante termina allí.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Creating a bug report</a></h2>
|
||||
<p>Antes de reportar un fallo, por favor <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">asegúrese</a> que aún no exista. Puede también usar la función de <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">búsqueda</a> para esto.<br />
|
||||
Tras haber establecido que es un fallo nuevo, haga su información tan puntual como sea posible:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Incluya información básica tal como dónde está probando a Haiku (sobre hardware real, en VMWare, en QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describa el problema que esté experimentando. Intente ser tan preciso como pueda: describa el comportamiento actual, y el comportamiento esperado.</p></li>
|
||||
<li><p>Describa qué pasos necesita realizar para exponer el fallo. Esto ayudará a los desarrolladores a reproducir el fallo.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Application bugs</a></h2>
|
||||
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Server bugs</a></h2>
|
||||
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
|
||||
Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (<span class="cli">bt</span> command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Kernel bugs</a></h2>
|
||||
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<ul>
|
||||
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
|
||||
<li><p>The system reboots spontaneously.</p></li>
|
||||
<li><p>The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards). Wait at least a minute to see, if anything happens.</p></li>
|
||||
<li><p>The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).</p></li>
|
||||
</ul>
|
||||
<p>Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could blacklist the responsible Wifi driver from your Haiku installation (see <a href="../../../userguide/en/bootloader.html">Boot Loader</a>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Shows the handled and unhandled hardware interrupts.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (aka continue)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
|
||||
</table>
|
||||
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
|
||||
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Syslog</a></h3>
|
||||
<p><b>This is the preferred method for gaining information from a non-booting system.</b><br />
|
||||
The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file <span class="path">/boot/system/var/log/syslog</span>. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).</p>
|
||||
<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog persistent. If the option <span class="menu">Save syslog from previous session during boot</span> is activated in the boot loader options (as it is by default), you'll find the syslog of your last session as <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
If you're not able to boot to get to the previous_syslog, you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
|
||||
In the boot loader's <span class="menu">Debug menu</span> you should find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. Note: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">On screen debug output</a></h3>
|
||||
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../../userguide/es/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Hardware/Driver bugs</a></h2>
|
||||
<p>When dealing with a hardware/driver related bug, you should attach the following information as text files:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>A detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Lists all used drivers.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Only available within <i>Kernel Debugging Land</i> (see above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>The first four commands are entered into Terminal. Add a <span class="cli"> > output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">What's next?</a></h2>
|
||||
<p>Después que un fallo se ha reportado, un desarrollador verá el reporte e intentará clasificarlo. Recuerde, todos somos voluntarios, y por ello, algunas veces un fallo pudiera estar sin responderse por un tiempo. Agregar nueva información cuando esté disponible usualmente ayuda a que se escoja un fallo más rápidamente, pero no intente 'levantar' el fallo agregando comentarios no descriptivos.</p>
|
||||
<p>Recuerde, reportar un fallo no es algo en lo que tome un poquito de tiempo y sea todo. Si se reporta un fallo, se vuelve parte del proceso de desarrollo de Haiku. Los desarrolladores podrían llegar con preguntas mientras intentan arreglar el fallo reportado. Por favor, permanezca atento para responderlas. Considere su participación 'terminada' cuando el fallo se marque como 'arreglado'.</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_es.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,157 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2010-2011, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* miguel~1.mx
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta http-equiv="Content-Style-Type" content="text/css" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Wifi</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Guía del usuario</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/es.png" alt="" /> Español</li>
|
||||
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
|
||||
<span>
|
||||
<a href="../welcome_es.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">La traducción de esta página no está completa aún. Hasta que esté, las partes sin terminar vienen en su inglés original.</div>
|
||||
|
||||
<h2>Wifi en Haiku</h2>
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="hardware" rel="nofollow" id="hardware">Hardware que se espera funcione</a></h3>
|
||||
<p>Todos los controladores wlan de FreeBSD 8 deberían trabajar. Cualquier tarjeta basada PCMCIA, CardBus, ExpressCard, USB o ISA no funcionará. Únicamente las PCI, miniPCI, PCI-Express, miniPci-Express and PCI-X se espera que trabajen.<br />
|
||||
Esto incluye a:
|
||||
</p>
|
||||
<ul>
|
||||
<li><p><i>aironetwifi</i> soportando al menos:<br />
|
||||
Aironet PCI4500 y<br />
|
||||
Aironet PCI4800.<br />
|
||||
</p></li>
|
||||
<li><p><i>atheroswifi</i> soportando casi todos los chipsets de afuera (aunque no los chips AR9285).</p></li>
|
||||
<li><p><i>broadcom43xx</i> soportando<br />
|
||||
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 y BCM4318.
|
||||
</p></li>
|
||||
<li><p><i>ipw2100</i> supporting Intel Pro Wireless 2100 chips</p></li>
|
||||
<li><p><i>iprowifi2200</i> supporting Intel Pro Wireless<br />
|
||||
2200BG<br />
|
||||
2225BG<br />
|
||||
2915ABG
|
||||
</p></li>
|
||||
<li><p><i>iprowifi3945</i> supporting Intel Pro Wireless 3945 chips</p></li>
|
||||
<li><p><i>iprowifi4965</i> supporting Intel Pro Wireless 4965 chips</p></li>
|
||||
<li><p><i>marvell88w8335</i> soportando:<br />
|
||||
Marvell Libertas 88W8310 y<br />
|
||||
Marvell Libertas 88W8335.
|
||||
</p></li>
|
||||
<li><p><i>marvell88w8363</i> soportando los chips 88W8363.</p></li>
|
||||
<li><p><i>ralinkwifi</i> soportando:<br />
|
||||
RT2560,<br />
|
||||
RT2561S,<br />
|
||||
RT2561 y <br />
|
||||
RT2661.
|
||||
</p></li>
|
||||
<li><p>ralink2860 supporting Ralink RT2860</p></li>
|
||||
<li><p><i>wavelanwifi</i> soportando al menos:<br />
|
||||
3Com Airconnect,<br />
|
||||
GLPRISM2 WaveLAN,<br />
|
||||
Intersil Prism3,<br />
|
||||
Intersil Prism2.5,<br />
|
||||
Linksys WDT11,<br />
|
||||
Netgear MA301,<br />
|
||||
PRISM2STA WaveLAN,<br />
|
||||
Siemens SpeedStream,<br />
|
||||
SMC 2602W,<br />
|
||||
Us Robotics 2415 y<br />
|
||||
Addtron AWA-100 PCI.
|
||||
</p></li>
|
||||
</ul>
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="connect" rel="nofollow" id="connect">Connecting to a wireless network</a></h3>
|
||||
<p>Besides of course unencrypted networks, Haiku has preliminary support for accessing wireless networks via <a href="#wep-notes" rel="nofollow">WEP encryption keys</a>. WEP is an early encryption method, although not the most secure.</p>
|
||||
<p>You can list available networks, join and leave them with the command <span class="cli">ifconfig</span> from Terminal:</p>
|
||||
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
|
||||
<p>You can find your <tt>wifi_device_path</tt> in the <span class="app">Network</span> preferences applet, or by executing <span class="cli">ifconfig -a</span>.</p>
|
||||
<p>Below are a few examples of connecting to a wireless network named <i>wifitopia</i>. For these examples we are assuming your wifi network card is <tt>/dev/net/iprowifi3945/0</tt>.</p>
|
||||
<h4>Listing wireless networks:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
|
||||
<h4>Joining unsecured wireless network:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
|
||||
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (ascii password)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
|
||||
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (64-bit hex password)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
|
||||
<h4>Leaving a wireless network:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="auto-connect" rel="nofollow" id="auto-connect">Automatically connecting to a wireless network</a></h3>
|
||||
<p>To make your system connect to a given SSID at each boot automatically, you can specify your wireless networks and passwords in <tt>/boot/common/settings/network/wireless_networks</tt> with the following format:</p>
|
||||
<pre>network wifitopia {
|
||||
password mypassword
|
||||
}</pre>
|
||||
<p>If you don't create this configuration file, the system will connect to the first unencrypted network it finds.</p>
|
||||
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>Notas WEP</strong></a></p>
|
||||
<ul>
|
||||
<li>El WEP de 64-bit usa una clave de 40-bit, lo cual significa 5 caracteres de texto o 10 dígitos hexadecimales.</li>
|
||||
<li>El WEP de 128-bit usa una clave de 104-bit, lo cual significa 13 caracteres de texto o 16 dígitos hexadecimales.</li>
|
||||
<li>hexadecimal digits = characters 0-9 and A through F (prepended with "0x" in <tt>ifconfig</tt>)</li>
|
||||
</ul>
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="wpa" rel="nofollow" id="wpa">Encripción WPA</a></h3>
|
||||
<p><p>At the moment there is no WPA encryption available in Haiku, though there have been <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">some efforts</a> bringing it significantly closer.</p></p>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
|
||||
<p>To install the firmware for Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you need to run</p>
|
||||
<pre class="terminal">install-wifi-firmwares.sh</pre>
|
||||
<p>The Intel ipw2100 and iprowifi22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.</p>
|
||||
<p>La gente que hace su propio build de la imagen de Haiku puede modificar su <span class="cli">build/jam/UserBuildConfig</span> en conformidad. Los detalles para ello y actualizaciones generales del tema de Wifi se encuentran en la <a href="http://www.haiku-os.org/guides/wifi">versión en línea de este documento</a>.</p>
|
||||
<p>Si tiene que descargar el firmware, pero no tiene una conexión a Internet funcionando bajo Haiku, la versión en línea de este documento ofrece un <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">script de shell</a>, el cual creará un archivo zip para que se extraiga en la carpeta <tt>/boot</tt> de Haiku. Después de ello tendrá todos los archivos necesarios por install-wifi-firmwares.sh.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_es.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,178 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* Karvjorm
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Vikojen ilmoittaminen</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Käyttäjäopas</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/fi.png" alt="" /> Suomi</li>
|
||||
<li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_fi.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Tämän sivun kotoistaminen ei ole vielä täydellinen. Siihen asti keskeneräiset osat käyttävät englanninkielistä alkuperäistekstiä.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Hakemisto</td></tr>
|
||||
<tr class="index"><td><a href="#account">Trac-tilin saaminen</a><br />
|
||||
<a href="#report">Vikailmoituksen luominen</a><br />
|
||||
<a href="#app">Sovellusviat</a><br />
|
||||
<a href="#server">Palvelinviat</a><br />
|
||||
<a href="#kernel">Käyttöjärjestelmäydinviat</a><br />
|
||||
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
|
||||
<a href="#syslog">Järjestelmäloki</a><br />
|
||||
<a href="#onscreen">Vikajäljitystulostus näytölle</a><br />
|
||||
<a href="#hardware">Laitteisto-/Ajuriviat</a><br />
|
||||
<a href="#next">Mitä seuraavaksi?</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>Vikojen ilmoittaminen</h1>
|
||||
|
||||
<p>Koska kehittäjämme eivät pysty testaamaan jokaista laitteistoyhdistelmää, eikä jokaista erilaista käyttöjärjestelmän vuorovaikutusta, luotamme käyttäjien antavan meille palautetta siitä, kuinka asiat toimivat heidän laitteissaan. Koska Haiku on aika nuori, on hyvin todennäköistä, että käyttäjä kohtaa vikoja. Kiitämme siitä ajasta, jota käytät niistä ilmoittamiseen. Yhdessä voimme parantaa Haikua pala palalta.</p>
|
||||
<p>Vianjäljityksen pitämiseksi tehokkaana on olennaista noudattaa <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Vianjäljitysetikettiä</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Trac-tiilin saaminen</a></h2>
|
||||
<p>Jos luot vikalipun, sinulla on oltava tili <a href="http://dev.haiku-os.org/register" title="Registröidy Haikun vikajäljittäjään">Haikun vikajäljittäjässä</a>.<br />
|
||||
Luotaessa uutta tiliä muista <b>tarjota sähköpostiosoitteesi</b>, koska se on välttämätön lipun muokkausoikeusien saamiseksi. Tarkista varmuuden vuoksi <b>roskapostikansiosi</b> pian jälkeenpäin, koska kaikki tärkeät vahvistussähköpostiviestit usein päättyvät sinne.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Vikailmoituksen luominen</a></h2>
|
||||
<p><a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">Varmista</a> ennen vian ilmoittamista, että vastaavaa vikailmoitusta ei ole jo olemassa. Voit käyttää myös <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">etsi</a>-toimintoa tähän.<br />
|
||||
Varmista sen jälkeen kun olet esitellyt ainutlaatuisen vian, että tietosi ovat niin tarkkoja kuin mahdollista:</p>
|
||||
<ul>
|
||||
<li><p>Yritä toistaa havaitsemasi vika nykyisessä Haikun korjausversiossa. Esirakennetut tiedostovedokset testaustarkoituksiin löytyvät <a href="http://haiku-files.org/">täältä</a>.</p></li>
|
||||
<li><p>Sisällytä mukaan perustietoa siitä, kuinka testaat Haikua (todellisessa tietokoneessa, VMWare-ympäristössä, QEMU-emulaattorissa, jne.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Kuvaile kokemasi pulma. Yritä olla niin tarkka kuin voit: kuvaile todellinen käyttäytyminen, ja se käyttäytyminen, jota odotit.</p></li>
|
||||
<li><p>Kuvaile, mitä vaiheita pitää suorittaa vian paljastumiseksi. Tämä auttaa kehittäjiä toistamaan vian.</p></li>
|
||||
<li><p>Liitä mukaan niin paljon tietoja, kuin sinulla on. Jos kyseessä on graafisen käyttöliittymän vika, tai vika yhdessä sovelluksessa, yritä tehdä näytönkaappaus painamalla <span class="key">PRINT SCREEN</span>-näppäintä.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Sovellusviat</a></h2>
|
||||
<p>Kun sovellus kaatuu, sinun pitäisi kutsua vikajäljitintä hälytysikkunasta, joka ponnahtaa näkyviin. Tämä avaa Pääteikkunan gdb-ohjelmalla (GNU-vikajäljitin), joka käynnistyy. Kirjoittamalla <span class="cli">bt</span>, luot "paluujäljen". jonka sinun pitäisi kopioida kokonaisuudessaan (mukaan lukien se osa, joka tuli näkyviin, ennen kuin kirjoitit <span class="cli">bt</span>-komennon) ja liittää se vikalippuun.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Palvelinviat</a></h2>
|
||||
<p>Kun elintärkeät palvelimet, kuten app-, registrar- tai input-palvelin kaatuvat, et näe tavallista kaatumishälytystä. Sen sijaan koko näyttö muuttuu valkoiseksi tja gdb-istunto käynnistyy ja sen tuloste ilmaantuu näytölle. Todennäköisesti pystyt yhä liikuttamaan hiiren kohdistinta, mikä ylikirjoittaa valkoisen ja gdb-tulosteen näytöllä. Yhä vielä toimivat sovellukset (kuten Prosessivalvonta tai Työpöytäpalkin kello) saattavat myös kirjoittaa vikajäljitin tulosteen päälle näytölle.<br />
|
||||
Paitsi että kaikki on rumempaa ja epämukavampaa, sama koskee myös sovellusvikoja. Tärkeintä on hankkia paluujälki (<span class="cli">bt</span>-komento). Sinun on ehkä otettava valokuva näytöstä digitaalikameralla, koska et voi kopioida tekstiä mihinkään.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Käyttöjärjestelmäydinviat</a></h2>
|
||||
<p>Käyttöjärjestelmäydinviat ovat tavallisesti vaikutuksiltaan vakavimmat ja samanaikaisesti niiden vikajäljittäminen on vaikeinta. Käyttöjärjestelmäytimeen tai ajuriin osoittavat selvimmin seuraavat oireet:</p>
|
||||
<ul>
|
||||
<li><p>Järjestelmä siirtyy Käyttöjärjestelmän vianjäljitysmaahan (KDL) omasta tahdostaan. Näytön ylempi osa muuttuu valkoiseksi ja sille tulostetaan useita rivejä tekstiä. Toinen rivi sanoo "<i>Welcome to Kernel Debugging Land...</i>". Sen yläpuolella oleva rivi kertoo välittömän syyn siirtymisestä KDL:ään.</p></li>
|
||||
<li><p>Järjestelmä alkulatautuu itsestään.</p></li>
|
||||
<li><p>Järjestelmä jäätyy täysin. Et voi siirtää hiiren osoitinta ja mikään sovellus ei enää toimi. Tärkeä testi siinä tilanteessa on, että pystytkö siirtymään KDL:ään pikanäppäimellä <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> mikä on <span class="key">PRINT</span> useimmissa näppäimistöissä). Odota vähintään minuutti nähdeksesi, että tapahtuuko jotain.</p></li>
|
||||
<li><p>Järjestelmä ei alkulataa oikein. Se voi alkulatautua itsestään tai pysähtyä jossain vaiheessa (esimerkiksi jonkun alkaulatausnäytön kuvakkeen kohdalla). Yritä jälkimmäisessä tapauksessa myös <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>Koko järjestelmä tai joku laitteiston osa ei toimi kunnolla. Esimerkiksi se voisi olla hyvin hidas, tapahtuu virheitä, tai jokin ei toimi ollenkaan. Jos jokin laite ei toimi ollenkaan, ensimmäinen ilmeinen tarkistus on, että tukeeko Haiku sitä ylimalkaan tällä hetkellä (esim.: kysy sähköpostituslistalta tai foorumilta).</p></li>
|
||||
</ul>
|
||||
<p>Huomaa että vaikka ainoastaan viimeinen kohta tuntuu viittaavan laittoistovikaan, kaikki muutkin oireet voivat johtua myös viasta laitteistoajurissa. Jos sinulla on epäilyjä, että mikä laitteiston osa tai vastaava ajuri aiheuttaa pulmia, tarkista, että eroaako tilanne, jos poistat tai otat pois käytöstä laitteen tai ajurin. Esimerkiksi jos epäilet Wifi-verkkoa, saatat huomata, että BIOS-asetuksissa voidaan ottaa se pois käytöstä. Tai jos ei, niin voisit merkata vastuullisen Wifi-ajurin mustalle listalle Haiku-asennuksestasi (katso <a href="../../../userguide/en/bootloader.html">Käynnistyslataaja</a>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Käyttöjärjestelmäytimen viajäljitysalue - KDL</a></h3>
|
||||
<p>Jos järjestelmä ei ole siirtynyt KDL-tilaan itsestään, voit tehdä sen tarkoituksellisesti pikanäppäimillä <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Huomaa, että KDL-tilassa näppäimistösi ei ehkä toimi. PS/2-näppäimistöt toimivat aina, UCHI-ohjaimen kautta yhdistetyt USB-näppäimistöt toimivat vain jos jos KDL-tilaan on siirrytty näppäimistön avulla vähintään kerran. USB OHCI ei tällä hetkellä tueta.</p>
|
||||
<p>KDL itse on erään tyyppinen komentotulkki. Käyttäjä voi suorittaa komentoja, jotka tulostavat tietoja järjestelmästä. Seuraavat komennot saattavat olla kiinnostavia:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (eli sc)</td><td> </td><td>Tulostaa paluujäljen. Jos järjestelmä siirtyy KDL-tilaan omasta tahdostaan, kirjoita aina tämä komento.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Näyttää käsitellyt ja käsittelemättömät laitteistokeskeytykset.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (eli jatka)</td><td> </td><td>Jättää järjestelmävianjäljittimen ja jatkaa normaalia järjestelmän toimintaa, jos se on mahdollista.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Alkulataa järjestelmän välittömästi. Menetät kaiken tallentamattomat tiedot ja vieläpä nuo, jotka on tallennettu, mutta joita ei ole vielä kirjoitettu levylle.</td></tr>
|
||||
</table>
|
||||
<p>Katso lisätietoja artikkelista <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Tervetuloa vikajäljitysalueelle</a>.</p>
|
||||
<p>KDL-tuloste kirjoitetaan sarjaporttiin (jos sinulla on sellainen, vastaavaan kaapeliin ja toiseen tietokoneeseen, voit kaapata tulosteen siellä pääteikkunan kautta) ja syslog-järjestelmälokiin. Jos et voi poistua KDL:stä, sitä ei kuitenkaan voida kirjoittaa järjestelmälokiin. Alkulatausvianjäljitysvalitsin mahdollistaa sen tallentamisen kaikesta huolimatta (katso alla).</p>
|
||||
<p>Voit tuottaa QR-koodeja KDL-tulosteesta, joka voidaan muuntaa tekstiksi käyttäen älypuhelimia ja vastaavia laitteita. Katso blogikirjoitusta <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR-koodaa KDL-tulosteesi</a> siitä kuinka saat ulos tietoja KDL:sta käyttäen tätä ominaisuutta.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Järjestelmäloki</a></h3>
|
||||
<p><b>Tämä on ensijainen menetelmä tietojen keräämiseksi ei-käynnistettävästä järjestelmästä.</b><br />
|
||||
Syslog-järjestelmäloki (syslog on lyhenne englanninkielisestä lokinimestä system log) sisältää arvokkaita tietoja siitä, mitä järjestelmässäsi tapahtui, mukaanlukien KDL-istunnot. On tavallisesti hyvä ajatus liittää se käyttöjärjestelmäydinaiheiseen Trac-lippuun. Järjestelmäloki kirjoitetaan tiedostoon <span class="path">/boot/system/var/log/syslog</span>. Koska kirjoittaminen tiedostoon vaatii toimivan järjestelmän, kaikkein viimeisin tulostustapahtuma ei ehkä ehdi järjestelmälokiin ennen käyttöjärjestelmäytimen pulman ilmaantumista (erityisesti spontaaneissa järjestelmän uudelleenkäynnistymisissä ja KDL-istunnoissa, joita ei voi jatkaa).</p>
|
||||
<p>Valitsin <span class="menu">Ota käyttöön vianjäljitysjärjestelmäloki</span> käynnistyslataajan <span class="menu">Vianjäljitys</span>-valikossa tekee syslog-järjestelmälokista jossain määrin pysyvän muistissa. Jos valitsin <span class="menu">Tallenna järjestelmäloki edellisestä istunnosta käynnistymisen aikana</span> on aktivoitu käynnistyslataajavalitsimissa (kuten se on oletuksena), löydät viimeisimmän istunnon järjestelmälokin tiedostosta <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
Jos et kykene hakemaan previous_syslog-tiedostoa, voit siirtyä käynnistyslataajaan pitämällä alhaalla näppäintä <span class="key">VAIHTO</span> käynnistyksen aikana.<br />
|
||||
Käynnistyslataajan <span class="menu">Vianjäljitys</span>-valikossa sinun pitäisi nyt löytää rivit <span class="menu">Näytä järjestelmäloki edellisestä istunnosta</span> ja <span class="menu">Tallenna järjestelmäloki edellisestä istunnosta</span>. Edellinen näyttää järjestelmälokin näytöllä, jälkimmäinen sallii sinun tallentaa sen tiedostona levylle. Huomaa, että tällä hetkellä vain FAT32-taltioita tuetaan tiedoston tallentamisessa. Jos haluat käyttää USB-tikkua, mutta olet liittänyt sen järjestelmään niin myöhään, että sitä ei ole vielä tunnistettu, voit nollata koneen ja siirtyä uudelleen käynnistysvalikkoon. Mutta taas: Älä vahingossa käynnistä mitään käyttöjärjestelmää tai tiedot katoavat.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">Vikajäljitystulostus näytölle</a></h3>
|
||||
<p><b>Vianjäljitystulostus näytölle on hyödyllinen vain hyvin erikoisten kohteiden vianjäljityksessä ja siinä tiedetään olevan (ajoitus) pulmia.</b><br />
|
||||
Se on ajankohtainen vain kun Haikun alkulataus epäonnistuu ja valikkovalinta <span class="menu">Vikajäljitä järjestelmäloki</span> ei jostain syystä toimi. Pidä ennen Haikun alkulatauslogon ilmaantumistta alhaalla <span class="key">VAIHTO</span>-näppäintä päästäksesi alkulatausvalikkoon. Valitse <span class="menu">Valitse turvatila</span>-valitsimet. Lähellä alareunaa luetelleaan <span class="menu">[ ] Ota käyttöön vikajäljitystulostus näytölle</span>. (Huomaa: Toiset valitsime voivat olla käytössä yrityksenä alkuladata Haiku. Jos Haiku alkulatautuu vain kun yksi tai useampi valitsin on käytössä, varmista, että mainitset ne).<br />
|
||||
Valitse lopuksi <span class="menu">Paluu päävalikkoon</span> ja sitten <span class="menu">Jatka alkulatausta</span>.<br />
|
||||
Yksi tai useampia tekstisivuja näytetään näytölle, vain muutama harva viimeinen rivi on liitettävä vikailmoituslippuun. Tässä on lisätietoja <a href="../../../userguide/fi/bootloader.html">Alkulataaja</a>sta.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Laitteisto/ajuriviat</a></h2>
|
||||
<p>Kun ollaan tekemisissä laitteisto- tai ajurivikojen kanssa, sinun pitäisi liittää seuraavia tietoja tekstitiedostona:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>Yksityiskohtainen luettelo laitteistostasi, mukaanlukien valmistaja- ja pci-tunnisteet, samanlainen kuin Linuxin <span class="cli">lshw</span> ja <span class="cli">lspci</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Otaksutaan sen olevan USB:hen liittyvä pulma, sama kuin <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Haikun ensisijainen järjestelmäloki, sukua alkulatauksen aikaiselle vianjäljitykselle. Komennolla <span class="cli">open</span> voit poimia olennaisen osan järjestelmälokista testieditorissa.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Luettelee kaikki käytetyt ajurit.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Käytettävissä vain <i>Käyttöjärjestelmäytimen vianjäljitysalueella</i> (katso yllä). Näyttää keskeytysten käytön. Eri laitteiden kesken jaettuja keskeytyksiä ei pitäisi olla montaa.</td></tr>
|
||||
<tr><td colspan="3">- Vianjäljitystulostus näytölle (alkulatausvalitsin turvatilassa).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>Neljä ensimmäistä komentoa kirjoitetaan Pääteikkunassa. Lisää <span class="cli"> > output.txt</span> komennon jälkeen ja se putkitetaan tekstitiedostoon, jonka nimi on "output.txt", jonka voit liittää vikailmoitukseesi tai sähköpostiviestiisi.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">Mitä seuraavaksi?</a></h2>
|
||||
<p>Vikailmoituksen tekemisen jälkeen kehittäjä tutkii vikaa ja yrittää luokitella sen. Muista, että olemme kaikki vapaaehtoisia ja sellaisena joskus vikailmoitus voi olla vastaamattomana jonkin aikaa. Lisätietojen lisääminen silloin kun sellaista ilmenee, auttaa tavallisesti vian poimimista käsiteltäväksi nopeammin, mutta älä yritä 'töniä' vikaa lisäämällä ei-kuvaavia kommentteja.</p>
|
||||
<p>Muista, että vika ei ole jotain, johon käytät pikkuisen aikaa ja sitten kaikki on tehty. Jos ilmoitat viasta, olet osa Haikun kehitysprosessia. Kehittäjät saattavat esittää kysymyksiä yrittäessään korjata vikaa. Pysyttele tavoitettavissa vastataksesi kysymyksiin. Katso osanottamisesi -tehdyksi' kun vika on merkitty 'fixed'.</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_fi.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,159 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2010-2011, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta http-equiv="Content-Style-Type" content="text/css" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Wifi</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/fi.png" alt="" /> Suomi</li>
|
||||
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
|
||||
<span>
|
||||
<a href="../welcome_fi.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
|
||||
<h2>Wifi in Haiku</h2>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="hardware" rel="nofollow" id="hardware">Expected supported hardware</a></h3>
|
||||
<p>All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, PCI-Express, miniPci-Express and PCI-X are supposed to work.<br />
|
||||
This includes:
|
||||
</p>
|
||||
<ul>
|
||||
<li><p><i>aironetwifi</i> supporting at least<br />
|
||||
Cisco Aironet 350 Series<br />
|
||||
Aironet PCI4500<br />
|
||||
Aironet PCI4800<br />
|
||||
</p></li>
|
||||
<li><p><i>atheroswifi</i> supporting almost every chipset outthere (though no AR9285 chips)</p></li>
|
||||
<li><p><i>broadcom43xx</i> supporting<br />
|
||||
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318
|
||||
</p></li>
|
||||
<li><p><i>ipw2100</i> supporting Intel Pro Wireless 2100 chips</p></li>
|
||||
<li><p><i>iprowifi2200</i> supporting Intel Pro Wireless<br />
|
||||
2200BG<br />
|
||||
2225BG<br />
|
||||
2915ABG
|
||||
</p></li>
|
||||
<li><p><i>iprowifi3945</i> supporting Intel Pro Wireless 3945 chips</p></li>
|
||||
<li><p><i>iprowifi4965</i> supporting Intel Pro Wireless 4965 chips</p></li>
|
||||
<li><p><i>marvell88w8335</i> supporting<br />
|
||||
Marvell Libertas 88W8310<br />
|
||||
Marvell Libertas 88W8335
|
||||
</p></li>
|
||||
<li><p><i>marvell88w8363</i> supporting the 88W8363 chips</p></li>
|
||||
<li><p><i>ralinkwifi</i> supporting<br />
|
||||
RT2560<br />
|
||||
RT2561S<br />
|
||||
RT2561<br />
|
||||
RT2661
|
||||
</p></li>
|
||||
<li><p>ralink2860 supporting Ralink RT2860</p></li>
|
||||
<li><p><i>wavelanwifi</i> supporting at least<br />
|
||||
3Com Airconnect<br />
|
||||
GLPRISM2 WaveLAN<br />
|
||||
Intersil Prism3<br />
|
||||
Intersil Prism2.5<br />
|
||||
Linksys WDT11<br />
|
||||
Netgear MA301<br />
|
||||
PRISM2STA WaveLAN<br />
|
||||
Siemens SpeedStream<br />
|
||||
SMC 2602W<br />
|
||||
Us Robotics 2415<br />
|
||||
Addtron AWA-100 PCI
|
||||
</p></li>
|
||||
</ul>
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="connect" rel="nofollow" id="connect">Connecting to a wireless network</a></h3>
|
||||
<p>Besides of course unencrypted networks, Haiku has preliminary support for accessing wireless networks via <a href="#wep-notes" rel="nofollow">WEP encryption keys</a>. WEP is an early encryption method, although not the most secure.</p>
|
||||
<p>You can list available networks, join and leave them with the command <span class="cli">ifconfig</span> from Terminal:</p>
|
||||
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
|
||||
<p>You can find your <tt>wifi_device_path</tt> in the <span class="app">Network</span> preferences applet, or by executing <span class="cli">ifconfig -a</span>.</p>
|
||||
<p>Below are a few examples of connecting to a wireless network named <i>wifitopia</i>. For these examples we are assuming your wifi network card is <tt>/dev/net/iprowifi3945/0</tt>.</p>
|
||||
<h4>Listing wireless networks:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
|
||||
<h4>Joining unsecured wireless network:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
|
||||
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (ascii password)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
|
||||
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (64-bit hex password)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
|
||||
<h4>Leaving a wireless network:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="auto-connect" rel="nofollow" id="auto-connect">Automatically connecting to a wireless network</a></h3>
|
||||
<p>To make your system connect to a given SSID at each boot automatically, you can specify your wireless networks and passwords in <tt>/boot/common/settings/network/wireless_networks</tt> with the following format:</p>
|
||||
<pre>network wifitopia {
|
||||
password mypassword
|
||||
}</pre>
|
||||
<p>If you don't create this configuration file, the system will connect to the first unencrypted network it finds.</p>
|
||||
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP notes</strong></a></p>
|
||||
<ul>
|
||||
<li>64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex digits</li>
|
||||
<li>128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex digits</li>
|
||||
<li>hexadecimal digits = characters 0-9 and A through F (prepended with "0x" in <tt>ifconfig</tt>)</li>
|
||||
</ul>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="wpa" rel="nofollow" id="wpa">WPA encryption</a></h3>
|
||||
<p><p>At the moment there is no WPA encryption available in Haiku, though there have been <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">some efforts</a> bringing it significantly closer.</p></p>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
|
||||
<p>To install the firmware for Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you need to run</p>
|
||||
<pre class="terminal">install-wifi-firmwares.sh
|
||||
</pre>
|
||||
<p>The Intel ipw2100 and iprowifi22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.</p>
|
||||
<p>People building their own Haiku image can modify their <span class="cli">build/jam/UserBuildConfig</span> accordingly. Details for that and general updates on the wifi topic are found at the <a href="http://www.haiku-os.org/guides/wifi">online version of this document</a>.</p>
|
||||
<p>If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">shell script</a>, which will create a zip file for you to extract to Haiku's <tt>/boot</tt>. After that you'll have all files needed by install-wifi-firmwares.sh.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_fi.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,191 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* Loïc
|
||||
* Vincent Duvert
|
||||
* roptat
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Signaler les bogues</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Guide de l’utilisateur</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/fr.png" alt="" /> Français</li>
|
||||
<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_fr.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Cette page n'est pas encore entièrement traduite. Les parties non encore traduites seront en anglais.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td><a href="#account">Obtenir un compte Trac</a><br />
|
||||
<a href="#report">Créer un rapport de bogue</a><br />
|
||||
<a href="#app">Bogues logiciels</a><br />
|
||||
<a href="#server">Bogues dans les Serveurs</a><br />
|
||||
<a href="#kernel">Bogues du noyau</a><br />
|
||||
<a href="#kdl">Le mode débogage noyau - KDL</a><br />
|
||||
<a href="#syslog">Le journal système</a><br />
|
||||
<a href="#onscreen">Les sorties écran du débogueur</a><br />
|
||||
<a href="#hardware">Bogues liés au matériel ou aux pilotes</a><br />
|
||||
<a href="#next">Et après ?</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>Signaler les bogues</h1>
|
||||
|
||||
<p>Comme il est impossible pour nos développeurs de tester toutes les combinaisons de matériel, ni tous les cas de figure pouvant interagir avec le système d'exploitation, nous comptons sur les utilisateurs pour nous dire si les choses fonctionnent pour eux. puisque Haiku est encore tout jeune, il est très probable que vous rencontriez des bogues. Nous vous remercions de bien vouloir prendre le temps de nous les signaler. Ensemble, nous pourrons, petit à petit, améliorer Haiku.</p>
|
||||
<p>Afin que le suivi de nos bogues reste efficace, il est essentiel de respecter l'<a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">étiquette de suivi des bogues</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Obtenir un compte Trac</a></h2>
|
||||
<p>Pour remplir un rapport (ticket), vous aurez besoin d’un compte utilisateur sur le <a href="http://dev.haiku-os.org/register" title="Traqueur de bogues de Haiku">Traqueur de bogues de Haiku</a>.<br />
|
||||
Lors de la création d’un nouveau compte, pensez à <b>indiquer votre adresse e-mail</b> afin d’obtenir les privilèges basiques de gestions des tickets. N’oubliez pas de <b>Vérifier votre dossier de pourriel</b> après, car les e-mails de vérifications s’y retrouvent souvent.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Créer un rapport de bogue</a></h2>
|
||||
<p>Avant de rapporter un bogue, veuillez <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">vérifier</a> qu’il n’est pas déjà répertorié. Vous pouvez aussi utiliser la <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">fonction de recherche</a> pour cela.<br />
|
||||
Après vous être assuré que votre bogue est unique, obtenez des informations précises sur votre environnement :</p>
|
||||
<ul>
|
||||
<li><p>Essayez de reproduire votre problème avec la version actuelle d'Haiku. Des <a href="http://haiku-files.org/">images préfabriqués</a> sont disponible à cet usage.</p></li>
|
||||
<li><p>Indiquez comment vous testez Haiku (sur machine réelle, dans VMware, dans Qemu…)</p></li>
|
||||
<li><p>Indiquez quelle révision vous utilisez. Vous pouvez trouver cette information dans le menu « <i>About Haiku…</i> » de la Deskbar.
|
||||
N'oubliez pas de mentionner le type de construction dont est issu le système que vous testez (gcc2, gcc4, gcc2hybrid, gcc4hybrid).
|
||||
Les images téléchargeables sont nommés en conséquence. Si vous avez construit l'image vous-même, vous devriez savoir comment vous l'avez compilé.</p></li>
|
||||
<li><p>Décrivez le problème que vous rencontrez. soyez aussi précis que possible : décrivez le comportement réel, et celui que vous attendiez.</p></li>
|
||||
<li><p>Décrivez les actions que vous avez effectuées avant de faire ressortir le bogue. Cela permettra aux développeurs de le reproduire.</p></li>
|
||||
<li><p>Attachez au rapport le plus d’informations possibles. Si le bogue concerne l’interface graphique ou une application, essayez de faire une capture d’écran à l'aide de la la touche <span class="key">IMPR ÉCRAN</span>.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Bogues logiciels</a></h2>
|
||||
<p>Lorsqu'une application se plante, vous devez appeler le débogueur depuis le message d'alerte qui s'affiche.
|
||||
Une fenêtre de Terminal devrait s'ouvrir avec gdb (le débogueur GNU) lancé à l'intérieur.
|
||||
En saisissant <span class="cli">bt</span>, vous obtiendrez ainsi une trace de la « pile d'appel » (<i>backtrace</i>) que vous devez joindre en intégralité (y compris la partie précédant l'appel à la commande <span class="cli">bt</span>) à votre rapport de bogue.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Bogues dans les serveurs</a></h2>
|
||||
<p>Lorsque les serveurs vitaux comme le serveur d'application, de registre ou d'entré plantent, vous ne verrez pas l'alerte de crash habituelle. à la place, l'écran sera nettoyé de blanc et une session gdb sera lancée, qui affichera directement ses restitutions à l'écran.
|
||||
Il se pourrait que vous soyez toujours à même de déplacer la souris, qui dessinera alors par dessus l'écran blanc de gdb. Les demandes encore en cours (comme ProcessController ou l'horloge dans la barre de Bureau) pourrait également dessiner au dessus de la sortie du débogueur à l'écran.<br />
|
||||
Bien que tout soit plus laid et peu commode, les même fondamentaux que pour déboguer les applications s'appliquent.
|
||||
Le plus important est de fournir une trace de la pile d'appel à l'aide de la commande <span class="cli">bt</span> (backtrace). Mais comme vous ne serez pas en mesure de copier le texte, vous aurez besoin de prendre une photo de l'écran avec un appareil photo numérique.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Bogues du noyau</a></h2>
|
||||
<p>Les bogues du noyau sont habituellement ceux qui ont les effets les plus graves, tout en étant les plus difficiles à déboguer. Il existe différents types de symptômes, qui révèlent généralement un problème du noyau ou d'un pilote :</p>
|
||||
<ul>
|
||||
<li><p>Le système entre en mode débogage du noyau (KDL) de lui même. La partie supérieure de l'écran est mise à blanc et plusieurs lignes de texte sont affichées.
|
||||
La seconde ligne dit « <i>Welcome to Kernel Debugging Land…</i> ». Celle au-dessus, précise la raison qui a déclenchée la session de débogage du noyau (KDL).</p></li>
|
||||
<li><p>Le système redémarre spontanément.</p></li>
|
||||
<li><p>Le système se bloque complètement. Vous ne pouvez pas déplacer la souris et plus aucune application ne dessine quoi que se soit. Dans cette situation, un bon test consiste à essayer d'accéder au KDL via le raccourci <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> étant la touche <span class="key">Impr</span> sur la plus part des claviers). Attendez au moins une minute, pour voir si quelque chose se passe.</p></li>
|
||||
<li><p>Le système ne démarre pas correctement. Il peut redémarrer spontanément ou s'arrêter à un moment donné (par exemple au niveau d'une icône de l'écran de démarrage). Dans ce dernier cas vous pouvez essayer aussi <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>L'ensemble du système ou un élément matériel ne se comporte pas correctement. Par exemple, il pourrait être très lent, des erreurs pourraient se produisent, ou quelque chose pourrait ne pas fonctionner du tous. Si un périphérique ne fonctionne pas du tout, la première vérification évidente à faire, est de se renseigner pour savoir si il est déjà supporté par Haiku (par exemple, en posant la question sur une liste de diffusion ou un forum).</p></li>
|
||||
</ul>
|
||||
<p>Notez que si seul le dernier point semble indiquer une relation avec le matériel, tous les autres symptômes pourraient aussi être causés par un bogue dans un pilote.
|
||||
Si vous soupçonnez un matériel ou son pilote d'être responsable du problème, vérifiez si la suppression ou la désactivation du matériel ou du pilote change quelque chose.
|
||||
Par exemple, si vous soupçonnez le Wifi, votre BIOS a peut-être une option pour le désactiver. Sinon, vous pouvez supprimer le pilote Wifi installé dans Haiku (voir <a href="../../../userguide/en/bootloader.html">Chargeur de démarrage</a>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Le mode débogage noyau - KDL</a></h3>
|
||||
<p>Si le système n'entre pas de lui même en mode déboguage du noyau (KDL) vous pouvez le faire volontairement en invoquant le raccourci clavier <span class="key">ALT</span> <span class="key">Syst</span> <span class="key">D</span> Attention : l'ordre des touches compte (<span class="key">SYST</span> correspond à <span class="key">Impr Écran</span> sur la plupart des claviers).
|
||||
Notez bien que votre clavier pourrait ne pas fonctionner en mode déboguage du noyau. Alors que les claviers PS/2
|
||||
ne posent pas de problème, les claviers USB connecté à un controleur UHCI ne fonctionne que si vous être entré au moins une fois en mode débogage à l'aide du raccourci clavier. Pour le moment l'USB OHCI n'est pas supporté.</p>
|
||||
<p>KDL est, par lui-même, une sorte d'interpréteur de commande. On peut exécuter des instructions pour afficher des informations sur le système. Les commandes suivantes pourraient vous intéresser :</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (alias sc)</td><td> </td><td>Affiche une trace de débogage (backtrace), Faites systematiquement cette commande quand le système entre dans le débogueur de lui même.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Affichera les interruptions matérielles qui sont gérées, ainsi que celles qui sont ignorées.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (alias continue)</td><td> </td><td>Quitte le débogueur pour reprendre, si possible, les opérations normales du système.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Redémarre le système immédiatement. Vous perdrez toutes les données non enregistrées, ainsi que celles qui ont été enregistrés, mais qui n'ont pas encore été écrites sur le disque.</td></tr>
|
||||
</table>
|
||||
<p>Pour plus d'information, consultez l'article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
<p>La sortie KDL est écrite vers le port série ( si vous en avez un, un câble approprié, et un deuxième ordinateur pour vous connecter, vous pourrez capturer la sortie via un programme de terminal) et le journal système. Nottez que si vous ne pouvez pas sortir du mode de débogage du noyau, le journal ne sera pas écrit dans le fichier. Cependant, Il existe une option dans le menu de démarrage qui permet tout de même sa capture (voir ci-dessous). </p>
|
||||
<p>Vous pouvez générer des codes QR à partir des sorties du KDL, ce qui vous permet de récupérer le texte en photographiant l'écran avec un un smartphones ou un appareil similaires. Consultez le blog <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> pour obtenir les informations sur l'utilisation de cette fonctionnalité dans le KDL.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Le journal système</a></h3>
|
||||
<p><b>C'est la méthode privilégiée pour obtenir des informations d'un système qui ne démarre pas.</b><br />Le journal système ( « syslog » en abgégé) contient des informations précieuses sur ce qui s'est passé dans votre système, y compris les productions des sessions KDL. L'attacher au ticket « kernel » dans l'outil de suivi de bogues (Trac) est généralement une bonne pratique.
|
||||
Le journal est consigné dans le fichier <span class="path">/boot/system/var/log/syslog</span>.Puisque l'écriture d'un fichier requiert un système qui fonctionne, les entrées les plus récente faites dans le journal peuvent ne pas être présentes quand un problème se produit dans le noyau (en particulier lors d'un redémarrage spontané ou d'une session KDL non recouvrable).</p>
|
||||
<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog persistent. If the option <span class="menu">Save syslog from previous session during boot</span> is activated in the boot loader options (as it is by default), you'll find the syslog of your last session as <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
If you're not able to boot to get to the previous_syslog, you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
|
||||
In the boot loader's <span class="menu">Debug menu</span> you should find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. Note: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">Les sorties écran du débogueur</a></h3>
|
||||
<p><b>La sortie écran du débogueur n'est utile que pour déboguer certains problèmes bien spécifiques, et est connu pour avoir des problèmes (timing). Ne l'utilisez que si vous en avez vraiment besoin.</b><br />
|
||||
Ce n'est pertinent que si Haiku n'arrive pas à démarrer sur votre machine et que le <span class="menu">Debug syslog option</span> ne fonctionne pas pour quelque raison que ce soit. Pour accéder au menu du chargeur de démarrage, maintenez la touche <span class="key">MAJ</span> enfoncée avant que le logo de Haiku n'apparaisse. Choisissez <span class="menu">Select safe mode options</span>. Selectionnez <span class="menu">[ ] Enable on screen debug output</span> que vous verrez en bas. (Notez que les autres options peuvent êtres activées pour tenter de démarrer Haiku. Si Haiku ne démarre que lorsque certaines options sont activées, n'oubliez pas de mentionner lesquelles )<br />
|
||||
Enfin choisissez <span class="menu">Return to main menu</span> puis <span class="menu">Continue booting</span>.<br />
|
||||
Une ou plusieurs pages de texte seront affiché à l'écran, Seules les quelques dernières lignes ont besoin de figurer dans votre rapport de bogue. Vous trouvez plus d'information dans le sujet consacré au <a href="../../../userguide/fr/bootloader.html">Chargeur de démarrage</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Bogues liés au matériel ou aux pilotes</a></h2>
|
||||
<p>Lorsque le bogue concerne un matériel ou son pilote, veuillez attacher au rapport, un fichier texte contenant les renseignements suivants :</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>Fait une liste détaillée de votre matériel, en y incluant les identifiants des périphériques PCI et de leurs fabriquants, à la manière de <span class="cli">lshw</span> ou <span class="cli">lspci</span> dans GNU/Linux.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Fait comme <span class="cli">lsusb</span> en supposant que c'est un problème lié à l'USB.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Le journal système principal utilisé par Haiku, semblable à celui de l'écran de débogage pendant le démarrage. Avec la commande <span class="cli">open</span>, vous pouvez modifier ce journal dans un éditeur de texte pour n'en conserver que la partie la plus pertinente.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Liste tous les drivers utilisés.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Seulement disponible dans le <i>mode débogage du noyau</i> (voir ci-dessous). Montre l'utilisation des interruptions.
|
||||
Il ne devrait pas y avoir trop d'interruptions partagées par plusieurs périphériques.</td></tr>
|
||||
<tr><td colspan="3">- Les sorties écran du débogueur (une option de mode sans échec du démarrage).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>Les 4 premières commandes sont à exécuter dans le Terminal. Si vous ajoutez <span class="cli"> > sortie.txt</span> après une commande, sa sortie sera redirigée dans un fichier texte nommé « sortie.txt » que vous pourrez attachez à votre rapport de bogue ou e-mail.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">Et après ?</a></h2>
|
||||
<p>Une fois le bogue rapporté, un développeur le consultera et essayera de le cataloguer. Retenez que tous les développeurs sont des volontaires; un long délai avant réponse peut s’écouler après le rapport de bogue. L’ajout de nouvelles informations une fois celles-ci disponibles peut généralement permettre à un bogue d’être analysé plus rapidement. Néanmoins, n’essayez pas de « faire remonter » un bogue en ajoutant des commentaires non pertinents.</p>
|
||||
<p>N’oubliez pas, le rapport d’un bogue ne se limite pas à sa soumission. Une fois cette tâche faite, vous ferez partie du processus de développement de Haiku. Les développeurs pourront vous poser des question pour essayer de résoudre votre bogue. Merci de rester disponible pour y répondre. Vous pourrez considérer votre travail « terminé » quand le bogue sera marqué comme étant « corrigé ».</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_fr.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,165 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2010-2011, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* Loïc
|
||||
* Vincent Duvert
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta http-equiv="Content-Style-Type" content="text/css" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Wifi</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Guide de l’utilisateur</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/fr.png" alt="" /> Français</li>
|
||||
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
|
||||
<span>
|
||||
<a href="../welcome_fr.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
|
||||
<h2>Le Wifi dans Haiku</h2>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="hardware" rel="nofollow" id="hardware">Matériel théoriquement supporté</a></h3>
|
||||
<p>Tous les pilotes de réseau sans fil de FreeBSD 8 devraient fonctionner. En revanche, les périphériques PCMCIA, CardBus, ExpressCard, USB, ou ISA ne sont pas supportés. Seules les cartes PCI, MiniPCI, PCI-Express, minipci-Express et PCI-X sont censées fonctionner.<br />
|
||||
Cela inclut :</p>
|
||||
<ul>
|
||||
<li><p>Le module <i>aironetwifi</i>, qui supporte au minimum les cartes :<br />
|
||||
Cisco Aironet 350 Series<br />
|
||||
Aironet PCI4500<br />
|
||||
Aironet PCI4800<br />
|
||||
</p></li>
|
||||
<li><p>Le module <i>atheroswifi</i>, qui supporte la plupart des puces Atheros (à l'exception de la puce AR9285)</p></li>
|
||||
<li><p>Le module <i>broadcom43xx</i> qui supporte les cartes :<br />
|
||||
BCM4301<br />
|
||||
BCM4306<br />
|
||||
BCM4307<br />
|
||||
BCM4309<br />
|
||||
BCM4311<br />
|
||||
BCM4312<br />
|
||||
BCM4318</p></li>
|
||||
<li><p>Le module <i>ipw2100</i> qui supporte les puces Wifi Intel Pro 2100</p></li>
|
||||
<li><p>Le module <i>iprowifi2200</i> qui supporte les cartes Wifi Intel Pro :<br />
|
||||
2200BG<br />
|
||||
2225BG<br />
|
||||
2915ABG
|
||||
</p></li>
|
||||
<li><p>Le module <i>iprowifi3945</i> qui supporte les puces Wifi Intel Pro 3945</p></li>
|
||||
<li><p>Le module <i>iprowifi4965</i> qui supporte les puces Wifi Intel Pro 4965</p></li>
|
||||
<li><p>Le module <i>marvell88w8335</i> qui supporte les cartes :<br />
|
||||
Marvell Libertas 88W8310<br />
|
||||
Marvell Libertas 88W8335
|
||||
</p></li>
|
||||
<li><p>Le module <i>marvell88w8363</i> qui supporte les puces Marvell 88W8363</p></li>
|
||||
<li><p>Le module <i>ralinkwifi</i> qui supporte les cartes :<br />
|
||||
RT2560<br />
|
||||
RT2561S<br />
|
||||
RT2561<br />
|
||||
RT2661
|
||||
</p></li>
|
||||
<li><p>Le module <i>ralink2860</i> qui supporte les puces Ralink RT2860</p></li>
|
||||
<li><p>Le module <i>wavelanwifi</i> qui supporte au moins les cartes suivantes :<br />
|
||||
3Com Airconnect<br />
|
||||
GLPRISM2 WaveLAN<br />
|
||||
Intersil Prism3<br />
|
||||
Intersil Prism2.5<br />
|
||||
Linksys WDT11<br />
|
||||
Netgear MA301<br />
|
||||
PRISM2STA WaveLAN<br />
|
||||
Siemens SpeedStream<br />
|
||||
SMC 2602W<br />
|
||||
Us Robotics 2415<br />
|
||||
Addtron AWA-100 PCI
|
||||
</p></li>
|
||||
</ul>
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="connect" rel="nofollow" id="connect">Connexion à un réseau Wifi</a></h3>
|
||||
<p>Outre les réseaux non-cryptés, un début de sécurité Wifi est disponible dans Haiku grâce aux <a href="#wep-notes" rel="nofollow">clés de cryptage WEP</a>.
|
||||
WEP est une méthode de cryptage rudimentaire peu sûre.</p>
|
||||
<p>Vous pouvez lister les réseaux disponibles, les joindre oules quitter à l'aide de la commande <span class="cli">ifconfig</span> depuis le Terminal :</p>
|
||||
<pre class="terminal">ifconfig [Chemin_du_ périphérique_Wifi] [list|join|leave] (clé)</pre>
|
||||
<p>Vous pouvez trouver votre <tt>Chemin_du_ périphérique_Wifi</tt> dans l'appliquette des préférences Réseau (<span class="app">Network</span>), ou en exécutant <span class="cli">ifconfig -a</span>.</p>
|
||||
<p>Voici quelques exemples de connexions à un réseau sans fil nommé <i>wifitopia</i>. Pour ces exemples, nous supposeront que votre carte réseau wifi est <tt>/dev/net/iprowifi3945/0</tt>.</p>
|
||||
<h4>Lister les réseaux Wifi :</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
|
||||
<h4>Joindre un réseau Wifi non sécurisé :</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
|
||||
<h4>Joindre un réseau Wifi <a href="#wep-notes">sécurisé en WEP </a> : (mot de passe ascii)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia MonMotDePasse</pre>
|
||||
<h4>Joindre un réseau Wifi <a href="#wep-notes">sécurisé en WEP </a> : (mot de passe hexadécimal 64-bit)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
|
||||
<h4>Quitter un réseau Wifi non :</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="auto-connect" rel="nofollow" id="auto-connect">Connexion automatique à un réseau Wifi</a></h3>
|
||||
<p>Pour que votre système se connecte automatiquement à un SSID donné à chaque démarrage, vous pouvez spécifier vos réseaux sans fil et leurs mots de passe dans <tt>/boot/common/settings/network/wireless_networks</tt> en utilisant le format suivant :</p>
|
||||
<pre>network wifitopia {
|
||||
password MonMotDePasse
|
||||
}</pre>
|
||||
<p>Si vous ne créez pas ce fichier de configuration, le système se connectera au premier réseau non crypté qu'il trouvera.</p>
|
||||
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>Remarques concernant le WEP</strong></a></p>
|
||||
<ul>
|
||||
<li>Le WEP « 64 bits » utilise une clé de 40 bits, c’est à dire 5 caractères alphanumériques ou 10 chiffres hexadécimaux.</li>
|
||||
<li>Le WEP « 128 bits » utilise une clé de 104 bits, c’est à dire 13 caractères alphanumériques ou 26 chiffres hexadécimaux.</li>
|
||||
<li>Un chiffre hexadécimal est un chiffre de 0 à 9 ou une lettre de A à F. Un nombre hexadécimal doit être précédé de « 0x » lorsqu’il est utilisé dans <tt>ifconfig</tt>.</li>
|
||||
</ul>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="wpa" rel="nofollow" id="wpa">Le cryptage WPA</a></h3>
|
||||
<p><p>Le cryptage WPA n'est pas encore disponible dans Haiku. Cependant, il existe une <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">ébauche</a> pour apporter cette nouvelle fonction.</p></p>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
|
||||
<p>Pour installer le micro-logiciel des cartes Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx & Marvell 88W8335, vous devez exécuter la commande</p>
|
||||
<pre class="terminal">install-wifi-firmwares.sh
|
||||
</pre>
|
||||
<p>Les pilotes Intel ipw2100 et iprowifi22xx pourront être installés sans qu’une connexion Internet soit présente, car la distribution, dans Haiku, des fichiers contenant les micro-logiciels originaux est autorisée par leur licence. En revanche, vous devrez accepter les termes de cette licence avant l’installation. Les pilotes Broadcom 43xx et Marvell 88W8335 nécessiteront une connexion Internet pour s’installer, car les fichiers contenant leurs micro-logiciels respectifs ne peuvent être redistribués avec Haiku.</p>
|
||||
<p>Si vous compilez vous-même Haiku, vous pouvez modifier votre fichier <span class="cli">build/jam/UserBuildConfig</span> afin de pouvoir utiliser cet outil. Vous pourrez trouver plus de détails sur le Wifi dans Haiku sur la <a href="http://www.haiku-os.org/guides/wifi">version en ligne de ce document</a> (en anglais).</p>
|
||||
<p>Si il vous faut télécharger le micro-logiciel mais que vous n'avez pas de connexion internet qui fonctionne sous Haiku, la version en ligne vous propose aussi un <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">script de commande</a>, qui crée un fichier zip à extraire dans le dossier <tt>/boot</tt> de Haiku. Après cela, vous aurez tous les fichiers nécessaires pour install-wifi-firmwares.sh.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_fr.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,179 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* Dancsó Róbert
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Hibák jelentése</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Használati útmutató</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/hu.png" alt="" /> Magyar</li>
|
||||
<li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_hu.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Az oldal fordítása még folyamatban van. Amíg tart a fordítás, addig a lefordítatlan részek angolul jelennek meg.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td><a href="#account">Trac azonosító létrehozása</a><br />
|
||||
<a href="#report">Hibajelentés készítése</a><br />
|
||||
<a href="#app">Program hibák</a><br />
|
||||
<a href="#server">Kiszolgáló/szolgáltatás hibák</a><br />
|
||||
<a href="#kernel">Kernel hibák</a><br />
|
||||
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
|
||||
<a href="#syslog">Rendszer napló</a><br />
|
||||
<a href="#onscreen">Hibakeresés a képernyőn</a><br />
|
||||
<a href="#hardware">Eszköz/vezérlő hibák</a><br />
|
||||
<a href="#next">Hogyan tovább?</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>Hibák jelentése</h1>
|
||||
|
||||
<p>Mivel a fejlesztők nem tudnak minden konfigurációt, az operációs rendszerben minden eshetőséget kipróbálni, ezért a felhasználók visszajelzésére támaszkodunk, arra, hogy náluk hogyan működnek a dolgok, milyen kimenetet kapnak. Mivel a Haiku még fiatal, ezért nagy valószínűséggel találkozol majd valamilyen hibával. Megköszönjük, ha fordítasz időt a feltárt hibák jelzésére. Együtt képesek leszünk a Haiku hiáinak javítására.</p>
|
||||
<p>A hibakeresőnél vedd figyelembe a <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Bug Tracker Etiquette</a>-ben leírtakat.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Trac azonosító létrehozása</a></h2>
|
||||
<p>Egy probléma jelentéséhez szükség van egy <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku Hibakövető</a> azonosítóra.<br />
|
||||
Új felhasználó létrehozáskor szükséges egy <b>e-mail cím megadása</b>. Ha regsiztráció után nem érkezik meg az ellenőrző/visszaigazoló levél, akkor ellenőrizni kell a <b>kéretlen levelek mappáját</b>, mert gyakran oda kerül.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Hibajelentés készítése</a></h2>
|
||||
<p>Mielőtt jelentesz egy hibát, előtte <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">győződj meg</a>, hogy még nem létezik róla jelentés. Szintén használható a <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">kereső</a> is.<br />
|
||||
Miután megbizonyosodtál róla, hogy a hiba egyedi, akkor azt a lehető legpontosabban, legrészletesebben le kell írni:</p>
|
||||
<ul>
|
||||
<li><p>Próbáld meg a hibát a legújabb verzión is előidézni. Előre elkészített képfájlok is a <a href="http://download.haiku-os.org">rendelkezésre állnak</a>.</p></li>
|
||||
<li><p>Add meg az alapvető információkat arra vonatkozóan, hogy miként használtad a Haiku-t (például valós gépen vagy emulátoron (VMWare, QEMU), stb.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Írd le a tapasztalt problémát. Próbáld meg olyan pontosan, ahogy tudod: mi és hogyan viselkedett, és mire számítottál.</p></li>
|
||||
<li><p>Írd le, hogy milyen lépések szükségesek ahhoz, hogy a hibát meg tudjuk ismételni. Ez a lépés segít a fejlesztőknek.</p></li>
|
||||
<li><p>Mellékelj annyi információt, amennyit csak tudsz. Ha ez a grafikus felület, vagy egy program hibája, akkor készíts egy képernyőképet a <span class="key">PRINT</span> billentyű lenyomásával.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Program hibák</a></h2>
|
||||
<p>Ha egy program meghibásodott, akkor a hibakereső a megjelenített üzenetből is előhívható. Ekkor megnyílik egy Terminál ablak a gdb-t (GNU hibakereső) futtatva. A <span class="cli">bt</span>-t kiadva létrehozhatunk egy "visszakövetést", aminek az eredményét a jelentéshez kell mellékelni (azt is, amit a <span class="cli">bt</span> előtt kaptál).</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Kiszolgáló/szolgáltatás hibák</a></h2>
|
||||
<p>Amikor egy létfontosságú szolgáltatás, mint például az alkalmazás szolgáltatás (app_server), a registrar vagy a bemeneti eszköz szolgáltatás (input_server) hibásodik meg, akkor nem valószínű, hogy a szokásos üzenetet kapod majd. Ehelyett a teljes képernyő egy Terminálhoz hasonló képernyőre változik, ahol a hibakereső folyamat elindul, és az üzenetek ott jelennek meg. Lehetséges, hogy az egér mozgatható, ekkor azonban az egér-kurzor törli a fehér képernyőn lévő információt. A programok továbbra is futnak (például a Folyamatkezelő vagy az óra az Ásztalsávon), amik szintén törölhetik a fehér képernyőt.<br />
|
||||
Attól, hogy kicsit kényelmetlen, minden épp úgy működik, mint a programhibák esetében. A legfontosabb a hiba visszakövetése (<span class="cli">bt</span> parancs). Erről a képernyőről készíthetsz egy képet is egy digitális fényképezőgéppel, itt ugyanis nem használható a kijelölés és másolás.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Kernel hibák</a></h2>
|
||||
<p>A kernel hibák a legsúlyosabbak, és ugyanakkor a legnehezebb felderíteni is azokat. Különféle eshetőségek lehetnek, melyek leginkább a kernelel vagy egy vezérlőprogramal kapcsolatos:</p>
|
||||
<ul>
|
||||
<li><p>A rendszer saját magától belép a kernel hibakereső felületére (KDL). A képernyő felső része törlődik, fehér hátteret kap és néhány sornyi szöveg is megjelenik. A második sor a "<i>Welcome to Kernel Debugging Land...</i>" (üdvözöllek a kernel hibakeresőben), az e feletti sor pedig a hibakeresőbe való belépés okát adja meg.</p></li>
|
||||
<li><p>A rendszer spontán újraindul.</p></li>
|
||||
<li><p>A rendszer teljesen használhatatlan ("lefagy"). Nem tudod mozgatni az egeret, és a képernyőt sem frissíti semmi. Fontos megpróbálni, hogy be tudunk-e lépni a KDL-be az <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (a <span class="key">SysReq</span> az a <span class="key">PRINT</span> sok billentyűzeten) kombinációval. Várj körülbelül egy percet, hogy történik-e valami.</p></li>
|
||||
<li><p>A rendszer nem megfelelően indul. Néha újraindul vagy megáll egy adott ponton (például egy indító képernyő egyik ikonjának felvillanásakor). Később ismét megpróbálható a <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> kombináció.</p></li>
|
||||
<li><p>A teljes rendszer, vagy bizonyos eszközök nem működnek megfelelően. Például nagyon lelassul vagy valami egyártalán nem működik. Ha egy eszköz nem működik, akkor elsőként azt kell kideríteni, hogy egyártalán támogatott eszközről van-e szó (például levelező listán vagy fórumon ajánlott megkérdezni).</p></li>
|
||||
</ul>
|
||||
<p>Ne feledd, hogy csak az utolsó pont utal eszköz hibára, azonban más problémát is okozhat egy eszközvezérlő hibája. Ha gyanítod, hogy a hibát egy adott vezérlő okozza, akkor ellenőrizd le, hogy mi változik, ha az eszközt vagy a vezérlőt eltávolítod vagy letiltod. Például, ha a Wifi-re gyanakszol, akkor próbáld meg kideríteni, hogy a BIOS-ban letiltható-e. Ha nem, akkor a gyanús vezérlőt feketelistára rakhatod (további információk a <a href="../../../userguide/en/bootloader.html">Rendszertöltő</a> fejezetben).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL (Kernel Hibakereső Felület)</a></h3>
|
||||
<p>Ha a rendszer nem lép be automatikusan a KDL-be, akkor a <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> kombinációval manuálisan is beléphetsz oda.<br />
|
||||
Ne feledd, megeshet, hogy a billentyűzeted nem fog működni a KDL-ben. A PS/2 billentyűzet biztosan, az USB csak akkor, ha UHCI vezérlőre van csatlakoztatva. USB OHCI jelenleg nem használható.</p>
|
||||
<p>A KDL egyfajta shell. Itt néhány parancsot is használhatunk. Az alábbi parancsok érdekesek lehetnek:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (sc)</td><td> </td><td>A hiba visszakövetése. Ha egy hiba miatt kerülsz a KDL-be, akkor ezt alapból kiadja az.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>A kezelt és nem kezelt eszköz-megszakítások megjelenítése.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (continue)</td><td> </td><td>Ha lehetséges, akkor kilép a hibakeresőből, és folytatja a normális működést.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Azonnal újraindítja a rendszert. Minden nem mentett adatot elveszítesz. Azokat is, amit bár elmentettél, de még nem lett a lemezre írva.</td></tr>
|
||||
</table>
|
||||
<p>További információk a <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a> oldalon.</p>
|
||||
<p>A KDL kimenete a soros porta is kiküldésre kerül (márha rendelkezünk vele). Egy kábelel egy másik számítógéphez kötve a terminálból egy program segítségével megkaphatjuk a kimenetet illetve a naplót. Ha nem tudunk kilépni a KDL-ből, akkor a napló sem kerül mentésre. Ekkor egy opció is a rendelkezésünkre áll betöltéskor (további információk alább).</p>
|
||||
<p>QR-kód létrehozására is lehetőségünk van a KDL-ből, amit felhasználhatunk például okos telefonnal. További információk a <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> oldalán.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Rendszer napló</a></h3>
|
||||
<p><b>Ez az előnyben részesített módszer egy nem indítható rendszer információinak összegyűjtésére.</b><br />
|
||||
A syslog (a rendszer napló rövid neve) értékes információkat tartalmaz arról, hogy mi történt a rendszerben beleértve a KDL kimenetét is. Általában jó ötlet és hasznos is a jelentéshez csatolása. A naplót a <span class="path">/boot/system/var/log/syslog</span> fájl tartalmazza. Mivel a fájl írásához működő rendszerre van szükség, ezért megeshet, hogy a legújabb üzenetek nem kerülnek bele a naplóba, főként, ha kernel probléma adódik (például ha a KDL nem válaszol, nem használható).</p>
|
||||
<p>Ha az <span class="menu">Enable debug syslog</span> (hibakereső naplózás engedélyezése) engedélyezve van a rendszertöltő <span class="menu">Debug menu</span>-ben (hibakereső menü), akkor a rendszer a naplót megőrzi. Ha a <span class="menu">Save syslog from previous session during boot</span> (az előző munkamenet naplójának mentése betöltés közben) engedélyezve van a rendszertöltő opciói között (ez az eredet beállítás), a legutóbbi rendszertötés naplója a <span class="path">/boot/system/var/log/previous_syslog</span> útvonalon található.<br />
|
||||
Ha a rendszer képtelen az indulás és így nem férünk hozzá az előző naplóhoz (previous_syslog), akkor be kell lépni indításkor a menübe a <span class="key">SHIFT</span> lenyomva tartásával.<br />
|
||||
A rendszertöltő <span class="menu">Debug menu</span>-ben (hibakereső menü) az alábbi két opciót láthatjuk: <span class="menu">Display syslog from previous session</span> (előző munkamenet naplójának megjelenítése) és a <span class="menu">Save syslog from previous session</span> (előző munkamenet naplójának elmentése). Az előbbi a naplót a képernyőn jeleníti meg, az utóbbi pedig elmenti azt a lemezre. Ne feledd, hogy jelenleg csak a FAT32-es fájlrendszerű lemezek használhatóak mentésre. Ha USB lemezre akarod menteni és elfelejtetted azt időben csatlakoztatni, akkor csatlakoztasd, majd nyugodtan indítsd újra a gépet, és próbáld meg akkor menteni a naplót. De ismételten: véletlenül se indíts egy operációs rendszert amíg el nem mented a naplót, mert különben elvész az.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">Hibakeresés a képernyőn</a></h3>
|
||||
<p><b>A képernyőn történő hibakeresés csak egy megadott hiba esetében hasznos, és időigényes. Ne használd, ha nem szükséges.</b><br />
|
||||
Ez akkor fontos, ha a Haiku nem tud elindulni és a <span class="menu">hibakereső naplózás</span> valamiért nem működik. Mielőtt a Haiku logó megjelenik, tartsd lenyomva a <span class="key">SHIFT</span>-et a rendszertöltőbe való belépéshez. Válasszd a <span class="menu">Select safe mode options</span> (hibakereső opciók) menüt, majd azon belül az <span class="menu">[ ] Enable on screen debug output</span> (képernyőn történő hibakeresés engedélyezése) opciót. (Megjegyzés: több opció is haszálható betöltéskor. Ha a Haiku indításakor egy vagy több opciót is használsz, akkor azokat is említsd meg.)<br />
|
||||
Végül válaszd a <span class="menu">Return to main menu</span> (visszatérés a főmenübe), majd a <span class="menu">Continue booting</span> (betöltés folytatása) menüpontot.<br />
|
||||
Egy vagy több oldalnyi szöveg is megjelenik majd a képernyőn, amiből csak az utolsó néhány sort szükséges a jelentéshez csatolni. További információk a <a href="../../userguide/hu/bootloader.html">Rendszertöltő</a> fejezetben.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Eszköz/vezérlő hibák</a></h2>
|
||||
<p>Ha eszközhibával/vezérlővel van dolgunk, akkor az alábbi információkat is ajánlott csatolni szöveges fájlként:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>Részletes lista az eszközökről/összetevőkről a pci és a gyártó azonosítójával együtt. Hasonló a Linux <span class="cli">lshw</span> és <span class="cli">lspci</span> parancsához.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>USB-vel kapcsolatos hiba esetén. Hasonló a <span class="cli">lsusb</span>-hez.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Az elsődleges napló, amit a Haiku használ, amibe az indításkori üzenetek is bekerülnek. Az <span class="cli">open</span> használatával a naplóból egy adott részt is kimásolhatunk, mert az egy szövegszerksztőben nyílik meg.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Az összes használt eszközvezérlő.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Csak a <i>Kernel Debugging Land</i>-ben haszálatos (lásd fejjebb). A megszakítások használatát jeleníti meg. Elvileg nem lehet túl sok amit megosztva használnak az eszközök.</td></tr>
|
||||
<tr><td colspan="3">- Hibakeresés a képernyőn (indításkori biztonsági opció).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>Az elős 4 parancsot a Terminálban kell kiadni. Kiegészítve a <span class="cli"> > output.txt</span> paraméterrel, a parancsok kimenete nem a képernyőre, hanem egy "output.txt" (kimenet) nevű fájlba kerül, amit a jelentéshez csatolhatunk vagy levélhez mellékelhetünk.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">Hogyan tovább?</a></h2>
|
||||
<p>Miután jeleztél egy hibát, egy fejlesztő megnézi azt, és osztályozza. Ne feledd, hogy minden fejlesztő önkéntes, így néha egy jelentés megválaszolatlan marad egy ideig.
|
||||
Ha új információk is rendelkezésre állnak, akkor azt is a jelentéshez ajánlott csatolni, így a probléma megoldása felgyorsulhat.</p>
|
||||
<p>Ne feledd azt sem, hogy a hiba jelentése nem csak annyiból ál, hogy jelented, és kész. Mikor jelentesz egy hibát, akkor Te is a Haiku fejlesztésének részévé válasz. A fejlesztők is tehetnek fel kérdéseket miközben próbálják kijavítani a hibát. Kérünk, hogy a válaszaiddal segítsd a munkánkat. Ha egy jelentés 'kész', akkor az 'fixed' (javított) jelölést kap.</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_hu.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 1.1 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 1.0 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 1.0 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 98 B |
Binary file not shown.
|
After Width: | Height: | Size: 124 B |
Binary file not shown.
|
After Width: | Height: | Size: 110 B |
Binary file not shown.
|
After Width: | Height: | Size: 121 B |
Binary file not shown.
|
After Width: | Height: | Size: 120 B |
Binary file not shown.
|
After Width: | Height: | Size: 378 B |
Binary file not shown.
|
After Width: | Height: | Size: 124 B |
Binary file not shown.
|
After Width: | Height: | Size: 120 B |
Binary file not shown.
|
After Width: | Height: | Size: 145 B |
Binary file not shown.
|
After Width: | Height: | Size: 111 B |
Binary file not shown.
|
After Width: | Height: | Size: 337 B |
Binary file not shown.
|
After Width: | Height: | Size: 264 B |
Binary file not shown.
|
After Width: | Height: | Size: 120 B |
Binary file not shown.
|
After Width: | Height: | Size: 126 B |
Binary file not shown.
|
After Width: | Height: | Size: 229 B |
Binary file not shown.
|
After Width: | Height: | Size: 121 B |
Binary file not shown.
|
After Width: | Height: | Size: 115 B |
Binary file not shown.
|
After Width: | Height: | Size: 212 B |
Binary file not shown.
|
After Width: | Height: | Size: 11 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 367 B |
@@ -0,0 +1,178 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Reporting bugs</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Guida dell'utente</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/it.png" alt="" /> Italiano</li>
|
||||
<li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_it.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">La traduzione di questa pagina non è stata completata. Per questo motivo le parti non tradotte sono visibili in inglese.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
|
||||
<a href="#report">Creating a bug report</a><br />
|
||||
<a href="#app">Application bugs</a><br />
|
||||
<a href="#server">Server bugs</a><br />
|
||||
<a href="#kernel">Kernel bugs</a><br />
|
||||
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
|
||||
<a href="#syslog">Syslog</a><br />
|
||||
<a href="#onscreen">On screen debug output</a><br />
|
||||
<a href="#hardware">Hardware/Driver bugs</a><br />
|
||||
<a href="#next">What's next?</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>Reporting bugs</h1>
|
||||
|
||||
<p>Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.</p>
|
||||
<p>To keep our bugtracker effective, it's essential to abide by the <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Bug Tracker Etiquette</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Getting a Trac account</a></h2>
|
||||
<p>To file a ticket, you need to have an account at <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku's Bugtracker</a>.<br />
|
||||
When creating a new account, be certain to <b>provide your email address</b> as it is necessary to obtain basic ticket modification privileges. Be sure to <b>check your spam folder</b> shortly afterwards, as the all important verification mail often ends up there.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Creating a bug report</a></h2>
|
||||
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">search</a> function for this.<br />
|
||||
After you have established that it's a unique bug, make your information as accurate as possible:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
|
||||
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Application bugs</a></h2>
|
||||
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Server bugs</a></h2>
|
||||
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
|
||||
Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (<span class="cli">bt</span> command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Kernel bugs</a></h2>
|
||||
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<ul>
|
||||
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
|
||||
<li><p>The system reboots spontaneously.</p></li>
|
||||
<li><p>The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards). Wait at least a minute to see, if anything happens.</p></li>
|
||||
<li><p>The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).</p></li>
|
||||
</ul>
|
||||
<p>Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could blacklist the responsible Wifi driver from your Haiku installation (see <a href="../../../userguide/en/bootloader.html">Boot Loader</a>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Shows the handled and unhandled hardware interrupts.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (aka continue)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
|
||||
</table>
|
||||
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
|
||||
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Syslog</a></h3>
|
||||
<p><b>This is the preferred method for gaining information from a non-booting system.</b><br />
|
||||
The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file <span class="path">/boot/system/var/log/syslog</span>. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).</p>
|
||||
<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog persistent. If the option <span class="menu">Save syslog from previous session during boot</span> is activated in the boot loader options (as it is by default), you'll find the syslog of your last session as <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
If you're not able to boot to get to the previous_syslog, you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
|
||||
In the boot loader's <span class="menu">Debug menu</span> you should find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. Note: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">On screen debug output</a></h3>
|
||||
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../../userguide/it/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Hardware/Driver bugs</a></h2>
|
||||
<p>When dealing with a hardware/driver related bug, you should attach the following information as text files:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>A detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Lists all used drivers.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Only available within <i>Kernel Debugging Land</i> (see above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>The first four commands are entered into Terminal. Add a <span class="cli"> > output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">What's next?</a></h2>
|
||||
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
|
||||
non-descriptive comments.</p>
|
||||
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
|
||||
as 'fixed'.</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_it.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,161 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2010-2011, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* MichaelPeppers
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta http-equiv="Content-Style-Type" content="text/css" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Wifi</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Guida dell'utente</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/it.png" alt="" /> Italiano</li>
|
||||
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
|
||||
<span>
|
||||
<a href="../welcome_it.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">La traduzione di questa pagina non è stata completata. Per questo motivo le parti non tradotte sono visibili in inglese.</div>
|
||||
|
||||
<h2>Il Wifi in Haiku</h2>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="indice" /></a>
|
||||
<a name="hardware" rel="nofollow" id="hardware">Hardware che dovrebbe essere supportato</a></h3>
|
||||
<p>Tutti i driver wlan forniti da FreeBSD 8 dovrebbero funzionare. Qualunque scheda basata su PCMCIA, CardBus, ExpressCard, USB o ISA non funzionerà. Solo PCI, miniPCI, PCI-Express, miniPci-Express e PCI-X sono probabilmente funzionanti.<br />
|
||||
I driver disponibili includono:
|
||||
</p>
|
||||
<ul>
|
||||
<li><p><i>aironetwifi</i>, supporta almeno<br />
|
||||
La serie Cisco Aironet 350<br />
|
||||
Aironet PCI4500<br />
|
||||
Aironet PCI4800<br />
|
||||
</p></li>
|
||||
<li><p><i>atheroswifi</i>, supporta quasi tutti i chipset Atheros in commercio (ma non i chip AR9285)</p></li>
|
||||
<li><p><i>broadcom43xx</i>, supporta i chipset<br />
|
||||
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 e BCM4318
|
||||
</p></li>
|
||||
<li><p><i>iprowifi2100</i>, supporta i chip Intel Pro Wireless 2100</p></li>
|
||||
<li><p><i>iprowifi2200</i>, supporta i chip Intel Pro Wireless<br />
|
||||
2200BG<br />
|
||||
2225BG<br />
|
||||
2915ABG
|
||||
</p></li>
|
||||
<li><p><i>iprowifi3945</i>, supporta i chip Intel Pro Wireless 3945</p></li>
|
||||
<li><p><i>iprowifi4965</i>, supporta i chip Intel Pro Wireless 4965</p></li>
|
||||
<li><p><i>marvell88w8335</i>, supporta<br />
|
||||
Marvell Libertas 88W8310<br />
|
||||
Marvell Libertas 88W8335
|
||||
</p></li>
|
||||
<li><p><i>marvell88w8363</i>, supporta i chip 88W8363</p></li>
|
||||
<li><p><i>ralinkwifi</i>, supporta<br />
|
||||
RT2560<br />
|
||||
RT2561S<br />
|
||||
RT2561<br />
|
||||
RT2661
|
||||
</p></li>
|
||||
<li><p>ralink2860, supporta i chip Ralink RT2860</p></li>
|
||||
<li><p><i>wavelanwifi</i>, supporta almeno<br />
|
||||
3Com Airconnect<br />
|
||||
GLPRISM2 WaveLAN<br />
|
||||
Intersil Prism3<br />
|
||||
Intersil Prism2.5<br />
|
||||
Linksys WDT11<br />
|
||||
Netgear MA301<br />
|
||||
PRISM2STA WaveLAN<br />
|
||||
Siemens SpeedStream<br />
|
||||
SMC 2602W<br />
|
||||
Us Robotics 2415<br />
|
||||
Addtron AWA-100 PCI
|
||||
</p></li>
|
||||
</ul>
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="connect" rel="nofollow" id="connect">Connettersi a un network wireless</a></h3>
|
||||
<p>Besides of course unencrypted networks, Haiku has preliminary support for accessing wireless networks via <a href="#wep-notes" rel="nofollow">WEP encryption keys</a>. WEP is an early encryption method, although not the most secure.</p>
|
||||
<p>You can list available networks, join and leave them with the command <span class="cli">ifconfig</span> from Terminal:</p>
|
||||
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
|
||||
<p>You can find your <tt>wifi_device_path</tt> in the <span class="app">Network</span> preferences applet, or by executing <span class="cli">ifconfig -a</span>.</p>
|
||||
<p>Below are a few examples of connecting to a wireless network named <i>wifitopia</i>. For these examples we are assuming your wifi network card is <tt>/dev/net/iprowifi3945/0</tt>.</p>
|
||||
<h4>Mostrare una lista dei network wireless:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
|
||||
<h4>Joining unsecured wireless network:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
|
||||
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (ascii password)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
|
||||
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (64-bit hex password)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
|
||||
<h4>Leaving a wireless network:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="auto-connect" rel="nofollow" id="auto-connect">Connettersi automaticamente a un network wireless</a></h3>
|
||||
<p>To make your system connect to a given SSID at each boot automatically, you can specify your wireless networks and passwords in <tt>/boot/common/settings/network/wireless_networks</tt> with the following format:</p>
|
||||
<pre>network wifitopia {
|
||||
password mypassword
|
||||
}</pre>
|
||||
<p>If you don't create this configuration file, the system will connect to the first unencrypted network it finds.</p>
|
||||
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>Note sul WEP</strong></a></p>
|
||||
<ul>
|
||||
<li>64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex digits</li>
|
||||
<li>128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex digits</li>
|
||||
<li>hexadecimal digits = characters 0-9 and A through F (prepended with "0x" in <tt>ifconfig</tt>)</li>
|
||||
</ul>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="wpa" rel="nofollow" id="wpa">WPA encryption</a></h3>
|
||||
<p><p>At the moment there is no WPA encryption available in Haiku, though there have been <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">some efforts</a> bringing it significantly closer.</p></p>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="indice" /></a>
|
||||
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
|
||||
<p>Per installare il firmware per le schede ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx & Marvell 88W8335, dovete far partire lo script</p>
|
||||
<pre class="terminal">install-wifi-firmwares.sh
|
||||
</pre>
|
||||
<p>The Intel ipw2100 and iprowifi22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.</p>
|
||||
<p>People building their own Haiku image can modify their <span class="cli">build/jam/UserBuildConfig</span> accordingly. Details for that and general updates on the wifi topic are found at the <a href="http://www.haiku-os.org/guides/wifi">online version of this document</a>.</p>
|
||||
<p>If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">shell script</a>, which will create a zip file for you to extract to Haiku's <tt>/boot</tt>. After that you'll have all files needed by install-wifi-firmwares.sh.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_it.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,179 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* Shota Fukumori
|
||||
* log-1
|
||||
* mt
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>バグの報告</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>ユーザーガイド</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/jp.png" alt="" /> 日本語</li>
|
||||
<li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_jp.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>目次</td></tr>
|
||||
<tr class="index"><td><a href="#account">Trac アカウントを取得する</a><br />
|
||||
<a href="#report">バグレポートの作成</a><br />
|
||||
<a href="#app">アプリケーションのバグ</a><br />
|
||||
<a href="#server">サーバーのバグ</a><br />
|
||||
<a href="#kernel">カーネルのバグ</a><br />
|
||||
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
|
||||
<a href="#syslog">Syslog</a><br />
|
||||
<a href="#onscreen">スクリーン上でのデバッグ</a><br />
|
||||
<a href="#hardware">Hardware/Driver bugs</a><br />
|
||||
<a href="#next">そして次は</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>バグの報告</h1>
|
||||
|
||||
<p>開発者はすべてのハードウェア構成でテストを行えませんし、オペレーティングシステムとのあらゆる関わり方をテストすることもできないので、ユーザーの動作報告などの情報に頼っています。そして Haiku はまだ幼いプロジェクトのため、バグに遭遇する可能性が高いです。私たちはバグを報告してくれるのを待っています。少しずつ Haiku を改善してもっと良いものにしていきませんか?</p>
|
||||
<p>私たちのバグトラッカーを有効に保つため、<a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">バグトラッカーでのエチケット</a>を絶対に守ってください。</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Trac アカウントを取得する</a></h2>
|
||||
<p>チケットを登録するには、<a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku バグトラッカー</a>でアカウントを取得する必要があります。<br />
|
||||
アカウントを作るときは、チケットの更新通知メールを受信するために<b>自分のメールアドレスを登録すること</b>が必要です。さまざまな確認のためのメールが届くため、アカウントを作成した後は、こまめに<b>迷惑メールフォルダ</b>をチェックするようにしてください。というのも、重要な確認メールがしばしば迷惑メールに分類されてしまうからです。</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">バグレポートの作成</a></h2>
|
||||
<p>バグを報告する前に、すでに報告されていないか<a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">確認を</a>するようにしてください。<a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">検索機能</a>が有用です。<br />
|
||||
報告されていないことを確認したら、以下の情報をできる限り多く提供してください。</p>
|
||||
<ul>
|
||||
<li><p>その問題が最新バージョンの Haiku でも再現するかを確認してみてください。テスト用のビルド済イメージが<a href="http://download.haiku-os.org">利用可能です</a>。</p></li>
|
||||
<li><p>テストした環境の情報 (物理的なハードウェア、QEMU、VMware など)</p></li>
|
||||
<li><p>動かしているリビジョン番号について言及してください。この情報は、Deskbar メニューの<span class="menu">Haiku について (About Haiku...)</span> から得られます。同様にテストしているHaiku のビルドの種類 (gcc2, gcc4, gcc2hybrid, gcc4hybrid) についても触れてください。ダウンロードイメージはビルドの種類に従って命名されています。自分でビルドしたイメージについては、どのようにビルドしたか知っておく必要があります。</p></li>
|
||||
<li><p>できる限り正しく、実際に起きた挙動を説明し、その後自分が予測した挙動と、現在の挙動の問題を説明する</p></li>
|
||||
<li><p>再現する手順や準備。これは開発者が再現するために必要です。</p></li>
|
||||
<li><p>その他の情報。GUI 周りのバグやアプリケーションのバグならば、<span class="key">PRINT</span> キーを押してスクリーンショットを取得してください。</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">アプリケーションのバグ</a></h2>
|
||||
<p>アプリケーションがクラッシュしたときは、ポップアップしたダイアログからデバッガーを起動すべきです。そうすれば gdb (GNU デバッガー) がターミナル画面の上で起動します。<span class="cli">bt</span> と入力すると "バックトレース" が出力されるので、それをそのままコピーし (<span class="cli">bt</span> と入力する前も含める) 、そのままチケットに添付してください。</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">サーバーのバグ</a></h2>
|
||||
<p>App server、registrar、input server のような重要なサーバーがクラッシュしたときはよくあるクラッシュアラートを見ることは無いでしょう。スクリーン全体が白で塗りつぶされ、gdb のセッションがスタートします。出力はスクリーンに直接出力されます。たぶん、マウスはまだ動かせでも gdb の出力を上書きするでしょう。アプリケーションも動いたままで、(たとえば、プロセスコントローラーや デスクバーの時計のように) それも gdb の出力を上書きします。<br />
|
||||
さらに、アプリケーションのバグに比べ、すべては見にくく便利ではありません。アプリケーションのバグのようにはいかないでしょう。バックトレースの取得 (<span class="cli">bt</span> コマンド) も、テキストのコピーができないためデジタルカメラ等を用いて写真を撮影しないとならないでしょう。</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">カーネルのバグ</a></h2>
|
||||
<p>カーネルのバグのデバッグはもっとも難しいでしょう。カーネルやドライバーのバグにはこのようなさまざまな症状があります:</p>
|
||||
<ul>
|
||||
<li><p>システムは kernel debugging land (KDL) に入ります。画面上部はクリアされいくつかの KDL に入る原因となった理由を含むと思われる文字列が出力されます。次に、"<i>Welcome to Kernel Debugging Land...</i>" と出力されます。その上に、KDL に入った直接の理由が表示されます。</p></li>
|
||||
<li><p>システムは自然に再起動します。</p></li>
|
||||
<li><p>システムは完全にフリーズします。マウスを動かすこともできず、アプリケーションも停止します。<span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (だいたいのキーボードで、<span class="key">SysReq</span> は <span class="key">PRINT</span> と同じキーです) を押して、KDL に入れます。</p></li>
|
||||
<li><p>システムは正常に起動しません。起動中に再起動するか、起動中にどこかで止まるか (たとえば、ブートスクリーンでのいくつかのアイコンで) のどちらかかもしれません。後者の場合でも、<span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> を押してみてください。</p></li>
|
||||
<li><p>システム全体または一部のハードウェアで正常な動作をしない。たとえば、動作がすごく遅い、エラーが発生する、完全に動作しない、などです。一部のハードウェアが動作しないならば、まず Haiku がそれをサポートするかどうかを確認してください (メーリングリストやフォーラムで聞いてみるなど)</p></li>
|
||||
</ul>
|
||||
<p>最後のポイントだけは、ハードウェアに関係あることを示すように思えますが、すべての他の症状も同様に、ハードウェアのドライバーのバグが原因で発生することがありえることに注意してください。もしドライバーやハードウェアに疑いを持っているならば、そのハードウェアを取り外すか、無効化をしてどのように変わるかを確認してください。たとえば、Wifi が問題だと疑っているならば BIOS の設定を参照して Wifi を無効化できます。設定がない場合は、問題の原因である Wifi ドライバーを Haiku のインストールからブラックリストに入れる (<a href="../../../userguide/en/bootloader.html">ブートローダー</a>を参照ください) ことができます。</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>システムが KDL に自動で入らなかった場合、<span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> を押して手動で入れます。<br />
|
||||
KDL ではキーボードが動作しないかもしれません。PS/2 キーボードは常に動作します。UHCI コントローラーに接続された USB キーボードは、一度キーボードショートカット経由で KDL に入った場合のみ動作するでしょう。現時点では、USB OHCI はサポートされていません。</p>
|
||||
<p>KDL 自体はシェルの一種です。システム情報を出力するコマンドを実行できますす。次のコマンドが役に立つでしょう:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (もしくは sc)</td><td> </td><td>バックトレースを出力する。システムが自ら KDL に入った場合、これを必ず実行します。</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>処理される / 処理されないハードウェア割り込みを表示します。</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (もしくは continue)</td><td> </td><td>カーネルデバッガーを離れ、可能ならばシステムの実行に戻ります。</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>システムをすぐに再起動します。まだ保存されていないすべてのデータ、保存はしていてもまだディスクに書き込まれていないデータは失われます。</td></tr>
|
||||
</table>
|
||||
<p>詳細は <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Kernel Debugging Land へようこそ</a>も参照してください。</p>
|
||||
<p>KDL はシリアルポートと syslog にも出力します (もしあるならば。シリアルケーブルをもう一つのコンピューターに接続し、出力を受け取れます)。KDL を終了できない場合 syslog には出力されませんが、ブートローダーのデバッグ用オプションがそれを可能にするでしょう (下記も参照ください)。</p>
|
||||
<p>KDL の出力から QR コードを生成できます。QR コードは、スマートフォンなどを使ってテキストに変換できます。この機能を使って KDL のデータを取り出すことについては、次のブログ投稿、<a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> を参照してください。</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Syslog</a></h3>
|
||||
<p><b>これは起動しないシステムから情報を取得するためのものです。</b><br />
|
||||
syslog (system log の略称) はシステムに発生した有益な情報を含んでいます。それは、KDL セッションの出力を含んでいます。それをカーネル関連の Trac チケットに添付することは良いことです。syslog は <span class="path">/boot/system/var/log/syslog</span> に記録されます。ファイルの書き込みには動作しているシステムが必要であり、直近の出力が書き込まれず、カーネルの問題が起きた瞬間を記録していないかもしれません (おもに突然のリブートや続行不能な KDL のセッションで)。</p>
|
||||
<p>ブートローダーの <span class="menu">Debug menu</span> にある <span class="menu">Enable debug syslog</span> オプションは syslog を記録します。<span class="menu">Save syslog from previous session during boot</span> オプションがブートローダーオプションで有効な場合 (実際デフォルトです)、最新のセッションの syslog は、<span class="path">/boot/system/var/log/previous_syslog</span> に見つかるでしょう。<br />
|
||||
ブートしても、previous_syslog が得られない場合は、起動するときに <span class="key">SHIFT</span> を押したままにしてブートローダーメニューに入る必要があります。<br />
|
||||
ブートローダーメニューにある <span class="menu">Debug menu</span> の中には <span class="menu">Display syslog from previous session</span> と <span class="menu">Save syslog from previous session</span> があります。前者は syslog をスクリーンに表示し、後者はディスクに保存します。現時点では FAT32 フォーマットのみサポートされていることに注意してください。USB メモリを使用する場合は、後から接続しても認識しないので 1 度再起動し、再度ブートローダーメニューに入る必要があります。注意: 誤ってほかのオペレーションシステムを実行しないようにしてください。syslog を失ってしまいます。</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">スクリーン上でのデバッグ</a></h3>
|
||||
<p><b>スクリーン上のデバッグ出力は特定の問題とすでにわかっている問題について役立つでしょう。必要でないなら使用しないでください。</b><br />
|
||||
これは Haiku がうまく起動せず、なおかつ <span class="menu">Debug syslog option</span> もうまく動作しないときに使います。Haiku の起動ロゴが現れる前に、<span class="key">SHIFT</span> を押したままにしてブートローダーメニューに入り、<span class="menu">Select safe mode options</span> を選びます。下の方にある <span class="menu">[ ] Enable on screen debug output</span> を有効にします (ノート: ほかのオプションも Haiku のブートを試みるときに有効になります。Haiku がどのオプションでのみ起動するかを確認してください)。<br />
|
||||
最後に、<span class="menu">Return to main menu</span> を選択し <span class="menu">Continue booting</span> を選択します。<br />
|
||||
1 ページ以上のテキストがスクリーンに表示されます。最後の数行がチケットに添付する必要がある物でしょう。詳細は、<a href="../../../userguide/jp/bootloader.html">ブートローダー</a>を参照のこと。</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">ハードウェアとドライバーのバグ</a></h2>
|
||||
<p>もしハードウェアやドライバーのバグに関連したバグを扱うならば、以下の情報を添付する必要があります:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>ベンダーと PCI id を含む詳細なハードウェアのリストを出力します。linux の <span class="cli">lshw</span> と <span class="cli">lspci</span> に似ています。</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>USB 関連のバグを取り扱うときに使用します。Linux の <span class="cli">lsusb</span> に似ています。</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Haiku システムのメインログ。ブート中のスクリーン上デバッグと似ています。<span class="cli">open</span> コマンドを用いることで、必要な部分をテキストエディターに切り出せます。</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>使用されているドライバーのリストを出力する。</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td><i>Kernel Debugging Land</i> (上記を参照) でのみ有効。割り込みの使用状況を表示します。同じ割り込みが複数のデバイスで共有されるのは好ましくありません。</td></tr>
|
||||
<tr><td colspan="3">- スクリーン上へのデバッグ出力 (ブート時のセーフモードオプション)</td></tr>
|
||||
</table>
|
||||
|
||||
<p>最初の 4 つのコマンドはターミナルに入力できます。<span class="cli"> > output.txt</span> をコマンドの最後に追加することで、"output.txt" というテキストファイルに出力されるようになります。つまり、それをバグレポートやメールに添付できるようになります。</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">そして次は</a></h2>
|
||||
<p>バグをレポートした後は、開発者があなたの報告を見て修正を試みるでしょう。しかし忘れないでいてもらいたいのは、私たちはボランティアであるので、しばらくの間報告が放置されることもあります。情報を追加することで早くバグを修正できるようになります。しかし、説明的でないコメントを追加することはしないでください。</p>
|
||||
<p>バグのレポートはあなたの時間を無駄に消費するわけではありません。バグの報告をしたあなたは一つの Haiku の開発プロセスにあります。開発者はバグを修正するために質問をすることがあります。それを無視せず、質問には答えるようにしてください。あなたの参加は、バグが 'fixed' となるまで終わりません。</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_jp.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,161 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2010-2011, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* Shota Fukumori
|
||||
* log-1
|
||||
* mt
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta http-equiv="Content-Style-Type" content="text/css" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Wifi</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>ユーザーガイド</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/jp.png" alt="" /> 日本語</li>
|
||||
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
|
||||
<span>
|
||||
<a href="../welcome_jp.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
|
||||
<h2>Haiku での Wifi</h2>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="hardware" rel="nofollow" id="hardware">サポートされているハードウェア</a></h3>
|
||||
<p>全ての FreeBSD 8 wlan ドライバーは動作すると思われます。ただし, PCMCIA, CardBus, ExpressCard, USB, ISA ベースのカードは動作しません。 PCI, miniPCI, PCI-Express, miniPCI-Express, PCI-X は動作すると思われます。<br />
|
||||
以下のようなデバイスとドライバーをサポートします:</p>
|
||||
<ul>
|
||||
<li><p><i>aironetwifi</i> は少なくとも以下をサポートします<br />
|
||||
Cisco Aironet 350 Series<br />
|
||||
Aironet PCI4500<br />
|
||||
Aironet PCI4800<br />
|
||||
</p></li>
|
||||
<li><p><i>atheroswifi</i> はそのチップを使うデバイスをサポートするでしょう (ただし AR9285 チップを除く)</p></li>
|
||||
<li><p><i>broadcom43xx</i> は以下をサポートします<br />
|
||||
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312, BCM4318
|
||||
</p></li>
|
||||
<li><p><i>iprowifi2100</i> は Intel Pro Wireless 2100 チップをサポートします</p></li>
|
||||
<li><p><i>iprowifi2200</i> は以下の Intel Pro Wireless をサポートします<br />
|
||||
2200BG<br />
|
||||
2225BG<br />
|
||||
2915ABG
|
||||
</p></li>
|
||||
<li><p><i>iprowifi3945</i> は Intel Pro Wireless 3945 チップをサポートします</p></li>
|
||||
<li><p><i>iprowifi4965</i> は Intel Pro Wireless 4965 チップをサポートします</p></li>
|
||||
<li><p><i>marvell88w8335</i> は以下をサポートします<br />
|
||||
Marvell Libertas 88W8310<br />
|
||||
Marvell Libertas 88W8335
|
||||
</p></li>
|
||||
<li><p><i>marvell88w8363</i> は 88W8363 チップをサポートします</p></li>
|
||||
<li><p><i>ralinkwifi</i> は以下をサポートします<br />
|
||||
RT2560<br />
|
||||
RT2561S<br />
|
||||
RT2561<br />
|
||||
RT2661
|
||||
</p></li>
|
||||
<li><p>ralink2860 は Ralink RT2860 をサポートします。</p></li>
|
||||
<li><p><i>wavelanwifi</i> は少なくとも以下をサポートします<br />
|
||||
3Com Airconnect<br />
|
||||
GLPRISM2 WaveLAN<br />
|
||||
Intersil Prism3<br />
|
||||
Intersil Prism2.5<br />
|
||||
Linksys WDT11<br />
|
||||
Netgear MA301<br />
|
||||
PRISM2STA WaveLAN<br />
|
||||
Siemens SpeedStream<br />
|
||||
SMC 2602W<br />
|
||||
Us Robotics 2415<br />
|
||||
Addtron AWA-100 PCI
|
||||
</p></li>
|
||||
</ul>
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="connect" rel="nofollow" id="connect">ワイヤレスネットワークへの接続</a></h3>
|
||||
<p>Haiku は、暗号化されていないネットワークに加えて、<a href="#wep-notes" rel="nofollow">WEP 暗号化キー</a>を用いたネットワークアクセスの予備的なサポートがあります。 WEP は初期の暗号化メソッドで、もっともセキュアということではありません。</p>
|
||||
<p>ターミナルからコマンド <span class="cli">ifconfig</span> を使って、利用可能なネットワークの一覧、ネットワーク接続、そしてネットワーク接続を閉じることができます。:</p>
|
||||
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
|
||||
<p><tt>wifi_device_path</tt> は、<span class="app">ネットワーク</span> プリファレンスアプレット、または <span class="cli">ifconfig -a</span> を実行することで見つけられます。</p>
|
||||
<p>以下は、<i>wifitopia</i> と名付けたワイヤレスネットワークへの接続の例です。これらの例では、wifi ネットワークカードを <tt>/dev/net/iprowifi3945/0</tt> と仮定しています。</p>
|
||||
<h4>ワイヤレスネットワークの一覧:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
|
||||
<h4>暗号化されていないワイヤレスネットワークへの接続:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
|
||||
<h4><a href="#wep-notes">WEP 暗号化された</a>ワイヤレスネットワークへの接続: (ascii パスワード)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
|
||||
<h4><a href="#wep-notes">WEP 暗号化された</a> ワイヤレスネットワークへの接続: (64-bit 16 進数パスワード)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
|
||||
<h4>ワイヤレスネットワーク接続を閉じる:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="auto-connect" rel="nofollow" id="auto-connect">自動的にワイヤレスネットワークに接続する</a></h3>
|
||||
<p>起動毎にシステムを特定の SSID に自動的に接続させるために、<tt>/boot/common/settings/network/wireless_networks</tt> に次のフォーマットでワイヤレスネットワークとパスワードを記入してもよいです。</p>
|
||||
<pre>network wifitopia {
|
||||
password mypassword
|
||||
}</pre>
|
||||
<p>この設定を作成していない場合、システムは最初に見つけた暗号化されていないネットワークに接続しようとするでしょう。</p>
|
||||
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP ノート</strong></a></p>
|
||||
<ul>
|
||||
<li>64-bit WEP 暗号 は 40-bit のキーを使用します。 すなわち 13 文字の文字列か、26 桁の 16 進法キーです。</li>
|
||||
<li>128-bit WEP 暗号 は 104-bit のキーを使用します。 すなわち 13 文字の文字列か、26 桁の 16 進法キーです。</li>
|
||||
<li>16 進法キー = 0 から 9、A から F で構成された文字列 (<tt>ifconfig</tt> では "0x" を頭につける)</li>
|
||||
</ul>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="wpa" rel="nofollow" id="wpa">WPA 暗号化</a></h3>
|
||||
<p><p>今現在、Haiku では WPA 暗号を利用することができません。しかし、<a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">いくつかの努力</a>によりかなり近づいています。</p></p>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
|
||||
<p>Intel ipw2100、Intel iprowifi2200/2225/2915、Broadcom 43xx & Marvell 88W8335 のためのファームウェアをインストールするには、以下を実行する必要があります。</p>
|
||||
<pre class="terminal">install-wifi-firmwares.sh
|
||||
</pre>
|
||||
<p>Haiku にオリジナルのファームウェアアーカイブを配布することをライセンス条項が許可しているため、 Intel ipw2011、iprowifi22xx はエンドユーザー承認があればインターネット接続無しでインストールできます。しかし、 Broadcom 43xx と Marvell 88W8335 は、Haiku と共に個別のファームウェアを配布できないため、アクティブなインターネット接続が必要です。</p>
|
||||
<p>自分で Haiku イメージ をビルドしている方は、上述に従い、 <span class="cli">build/jam/UserBuildConfig</span> を編集することができます。 編集についての詳細と wifi の話題に関するとさまざまなアップデートは<a href="http://www.haiku-os.org/guides/wifi">このドキュメントのオンライン版</a>を参照してください。</p>
|
||||
<p>もし、ファームウェアをダウンロードする必要があるが、Haiku 環境にインターネット接続が無い場合は、Haiku の <tt>/boot</tt> に展開するための zip ファイルを作成する<a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">シェルスクリプト</a>がオンライン版にあります。</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_jp.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,178 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Reporting bugs</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Podręcznik użytkownika</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/pl.png" alt="" /> Polski</li>
|
||||
<li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_pl.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Tłumaczenie tej strony jest niekompletne. Nieukończone części wyświetlane są w języku angielskim.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Spis treści</td></tr>
|
||||
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
|
||||
<a href="#report">Creating a bug report</a><br />
|
||||
<a href="#app">Application bugs</a><br />
|
||||
<a href="#server">Server bugs</a><br />
|
||||
<a href="#kernel">Kernel bugs</a><br />
|
||||
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
|
||||
<a href="#syslog">Syslog</a><br />
|
||||
<a href="#onscreen">On screen debug output</a><br />
|
||||
<a href="#hardware">Hardware/Driver bugs</a><br />
|
||||
<a href="#next">What's next?</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>Reporting bugs</h1>
|
||||
|
||||
<p>Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.</p>
|
||||
<p>To keep our bugtracker effective, it's essential to abide by the <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Bug Tracker Etiquette</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Getting a Trac account</a></h2>
|
||||
<p>To file a ticket, you need to have an account at <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku's Bugtracker</a>.<br />
|
||||
When creating a new account, be certain to <b>provide your email address</b> as it is necessary to obtain basic ticket modification privileges. Be sure to <b>check your spam folder</b> shortly afterwards, as the all important verification mail often ends up there.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Creating a bug report</a></h2>
|
||||
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">search</a> function for this.<br />
|
||||
After you have established that it's a unique bug, make your information as accurate as possible:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
|
||||
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Application bugs</a></h2>
|
||||
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Server bugs</a></h2>
|
||||
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
|
||||
Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (<span class="cli">bt</span> command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Kernel bugs</a></h2>
|
||||
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<ul>
|
||||
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
|
||||
<li><p>The system reboots spontaneously.</p></li>
|
||||
<li><p>The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards). Wait at least a minute to see, if anything happens.</p></li>
|
||||
<li><p>The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).</p></li>
|
||||
</ul>
|
||||
<p>Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could blacklist the responsible Wifi driver from your Haiku installation (see <a href="../../../userguide/en/bootloader.html">Boot Loader</a>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Shows the handled and unhandled hardware interrupts.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (aka continue)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
|
||||
</table>
|
||||
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
|
||||
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Syslog</a></h3>
|
||||
<p><b>This is the preferred method for gaining information from a non-booting system.</b><br />
|
||||
The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file <span class="path">/boot/system/var/log/syslog</span>. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).</p>
|
||||
<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog persistent. If the option <span class="menu">Save syslog from previous session during boot</span> is activated in the boot loader options (as it is by default), you'll find the syslog of your last session as <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
If you're not able to boot to get to the previous_syslog, you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
|
||||
In the boot loader's <span class="menu">Debug menu</span> you should find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. Note: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">On screen debug output</a></h3>
|
||||
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../../userguide/pl/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Hardware/Driver bugs</a></h2>
|
||||
<p>When dealing with a hardware/driver related bug, you should attach the following information as text files:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>A detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Lists all used drivers.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Only available within <i>Kernel Debugging Land</i> (see above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>The first four commands are entered into Terminal. Add a <span class="cli"> > output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">What's next?</a></h2>
|
||||
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
|
||||
non-descriptive comments.</p>
|
||||
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
|
||||
as 'fixed'.</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_pl.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,179 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* tiagoms
|
||||
* Adriano Duarte
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Reportando erros</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Guia do Usuário</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/pt_BR.png" alt="" /> Português (Brazil)</li>
|
||||
<li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_pt_BR.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">A tradução desta página ainda não está completa. Até lá, partes incompletas mostrarão o original em inglês.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Índice</td></tr>
|
||||
<tr class="index"><td><a href="#account">Obtendo uma conta do Trac</a><br />
|
||||
<a href="#report">Criando um relatório de erro</a><br />
|
||||
<a href="#app">Erros de aplicativo</a><br />
|
||||
<a href="#server">Erros de servidor</a><br />
|
||||
<a href="#kernel">Erros de Kernel</a><br />
|
||||
<a href="#kdl">Terra da Depuração do Kernel - KDL</a><br />
|
||||
<a href="#syslog">Relatório de Sistema</a><br />
|
||||
<a href="#onscreen">Saída de depuração na tela</a><br />
|
||||
<a href="#hardware">Erros de Dispositivo/Driver</a><br />
|
||||
<a href="#next">O que vem a seguir?</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>Reportando erros</h1>
|
||||
|
||||
<p>Uma vez que nossos desenvolvedores não são capazes de testar todas as combinações de hardware nem todas as diferentes formas de interação com o sistema operacional, nós contamos com os usuários para dar-nos algum retorno sobre como as coisas funcionam em seu equipamento. Uma vez que o Haiku é ainda um tanto jovem, é muito provável que irá encontrar erros. Agradecemos por dispor de tempo para reportá-los. Juntos melhoraremos o Haiku, bit a bit.</p>
|
||||
<p>Para manter nosso rastreador de erros eficaz, é essencial obedecer à <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Etiqueta do Rastreador de Erros</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Obtendo uma conta do Trac</a></h2>
|
||||
<p>Para arquivar um tíquete, é necessária uma conta no <a href="http://dev.haiku-os.org/register" title="Registro no Rastreador de Erros do Haiku">Rastreador de Erros do Haiku</a>.<br />
|
||||
Ao criar uma nova conta, certifique-se de <b>informar seu endereço de correio eletrônico</b>, necessário para obter privilégios básicos para modificação do tíquete. Assegure-se de <b>verificar sua pasta de correspondência indesejada</b> logo depois, afinal toda verificação de correios importantes costuma acabar aí.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Criando um relatório de erro</a></h2>
|
||||
<p>Antes de reportar um erro, por favor <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">certifique-se</a> de que ele ainda não existe. Pode-se também utilizar a função de <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">pesquisa</a> para isso.<br />
|
||||
Após constatar que é um erro original, torne sua informação a mais acurada possível:</p>
|
||||
<ul>
|
||||
<li><p>Tente reproduzir o problema na versão atual do Haiku. Imagens pré-compiladas para o propósito de testes estão <a href="http://haiku-files.org/">disponíveis</a>.</p></li>
|
||||
<li><p>Inclua informação básica sobre como está testando o Haiku (em equipamento real, no VMWare, no QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Descreva o problema que está experimentando. Tente ser o mais acurado possível: descreva o comportamento atual e o comportamento que deseja.</p></li>
|
||||
<li><p>Descreva que passos precisa realizar a fim de expor o erro. Isto ajudará os desenvolvedores a reproduzir o erro.</p></li>
|
||||
<li><p>Anexe toda a informação que tiver. Se é um erro de interface gráfica, ou um erro em um dos aplicativos, tente obter uma imagem da tela pressionando a tecla <span class="key">PRINT</span>.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Erros de Aplicativo</a></h2>
|
||||
<p>Quando um aplicativo trava, deve-se executar o depurador a partir do alerta que aparece na tela. Isto abrirá uma janela do Terminal com o gdb (o depurador GNU) rodando nele. Executando <span class="cli">bt</span>, cria-se um "rastro" que deverá ser copiado inteiramente (incluindo a parte antes de executar o comando <span class="cli">bt</span>) e anexado ao tíquete.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Erros de servidor</a></h2>
|
||||
<p>Quando servidores vitais como o servidor de aplicativo, o registrador ou o servidor de entrada travar, não se verá o alerta de travamento usual. Ao invés disso, toda a tela ficará em branco e uma sessão do gdb será iniciada, sua saída aparecendo diretamente na tela. Provavelmente você ainda será capaz de mover o mouse, o que irá sobrescrever o branco e a saída do gdb na tela. Aplicativos ainda em execução (como o Controlador de Processos ou o relógio na Deskbar) podem também aparecer sobre a saída do depurador na tela.<br />
|
||||
Apesar de tudo ser mais feio e inconveniente, basicamente se aplica o mesmo que aos erros de aplicativos. O mais importante é obter um "rastro" (comando <span class="cli">bt</span>). Pode-se precisar obter uma imagem da tela com uma câmera digital, uma vez que, de qualquer maneira, não será capaz de copiar o texto.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Erros do Kernel</a></h2>
|
||||
<p>Erros de Kernel são sempre os únicos com os efeitos mais graves e ao mesmo tempo os mais difíceis de depurar. Existem diferentes tipos de sintomas, os quais mais provavelmente apontam um problema de kernel ou de driver:</p>
|
||||
<ul>
|
||||
<li><p>O sistema aciona a Terra da Depuração do Kernel (KDL) por si mesmo. A parte superior da tela torna-se branca e várias linhas de texto são mostradas. A segunda linha diz "<i>Bem vindo a Terra da Depuração do Kernel...</i>", a linha acima dela afirma a razão imediata para entrar na KDL.</p></li>
|
||||
<li><p>O sistema reinicia espontaneamente.</p></li>
|
||||
<li><p>O sistema congela completamente. Não se pode mover o mouse e nenhum aplicativo faz nada mais. Um importante teste naquela situação é, se ainda puder entrar na KDL pelo atalho <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> sendo <span class="key">PRINT</span> na maioria dos teclados). Aguarde ao menos um minuto para ver se algo acontece.</p></li>
|
||||
<li><p>O sistema não inicializa corretamente. Ele pode reiniciar espontaneamente ou pára em algum ponto (por exemplo, em algum ícone da tela de inicialização). No último caso tente também <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>O sistema inteiro ou alguma parte do equipamento não se comporta corretamente. Por exemplo, ele pode ficar muito lento, ocorrerem erros ou algo não funcionar absolutamente, a primeira verificação óbvia é se o Haiku já o suporta completamente (por exemplo, perguntando em uma lista de discussão ou num fórum).</p></li>
|
||||
</ul>
|
||||
<p>Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could blacklist the responsible Wifi driver from your Haiku installation (see <a href="../../../userguide/en/bootloader.html">Boot Loader</a>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Terra da Depuração do Kernel - KDL</a></h3>
|
||||
<p>Se o sistema não entrar no KDL por si mesmo, pode-se fazê-lo intencionalmente invocando através do atalho de teclado <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Observe que no KDL seu teclado pode não funcionar. Teclados PS/2 sempre funcionam, teclados USB conectados via controladores UHCI apenas se alguém entrou no KDL via atalho de teclado ao menos uma vez. USB OHCI não é suportado no momento.</p>
|
||||
<p>O KDL propriamente é uma espécie de shell. Alguém pode executar comandos que exibem informação sobre o sistema. Os seguintes comandos podem ser de interesse:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (conhecido como sc)</td><td> </td><td>Exibe um rastro. Se o sistema entrar no KDL por sua própria vontade, sempre o execute.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Mostra as interrupções de dispositivos tratadas e não tratadas.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (conhecido como continue)</td><td> </td><td>Sai do depurador do kernel e continua a operação normal do sistema, se for possível.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reinicia o sistema imediatamente. Perder-se-á todos os dados não salvos e até mesmo aqueles que tenham sido salvos, mas que não tenham sido gravados no disco.</td></tr>
|
||||
</table>
|
||||
<p>Para mais informações, veja o artigo <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Bem vindo à Terra da Depuração do Kernel</a>.</p>
|
||||
<p>A saída do KDL é enviada para uma porta serial (caso tenha um, um cabo respectivo e um segundo computador conectado a ele, pode-se capturar a saída lá através de um programa de terminal) e para o relatório do sistema. Entretanto, se não puder sair do KDL ela não será escrita no arquivo de relatório do sistema. Todavia, existe uma opção de depuração do carregador da inicialização que permite capturá-la (veja abaixo).</p>
|
||||
<p>Pode-se gerar códigos QR a partir da saída do KDL que pode então ser convertido para texto utilizando smartphones ou dispositivos similares. Veja a postagem de blog <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR codifica sua saída do KDL</a> sobre como obter saída de dados do KDL utilizando aquela funcionalidade.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Relatório de sistema</a></h3>
|
||||
<p><b>This is the preferred method for gaining information from a non-booting system.</b><br />
|
||||
The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file <span class="path">/boot/system/var/log/syslog</span>. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).</p>
|
||||
<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog persistent. If the option <span class="menu">Save syslog from previous session during boot</span> is activated in the boot loader options (as it is by default), you'll find the syslog of your last session as <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
If you're not able to boot to get to the previous_syslog, you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
|
||||
In the boot loader's <span class="menu">Debug menu</span> you should find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. Note: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">Saída de depuração na tela</a></h3>
|
||||
<p><b>A saída em tela é útil apenas para depurar problemas muito específicos e é conhecido por ter problemas (de tempo). Não a utilize, se não precisar.</b><br />
|
||||
Isto é relevante apenas quando o Haiku falha ao inicializar na sua máquina e a <span class="menu">Opção de relatório de sistema do depurador</span> não funciona por alguma razão. Antes da logo de inicialização do Haiku aparecer, pressione <span class="key">SHIFT</span> para entrar no menu do carregador de inicialização. Selecione <span class="menu">Selecionar opções de modo seguro</span>. Próximo do fim, <span class="menu">[ ] Habilitar saída de depuração na tela</span> será listada. (Observação: As outras opções podem ser habilitadas numa tentativa de inicializar o Haiku. Se o Haiku inicializar apenas quando uma ou mais opções forem ativadas, assegure-se de mencionar quais são.)<br />
|
||||
Finalmente selecione <span class="menu">Voltar para o menu principal</span> e então <span class="menu">Continuar a inicialização</span>.<br />
|
||||
Uma ou mais páginas de texto serão exibidas na tela, apenas as últimas poucas linhas precisam ser incluídas no seu tíquete. Há mais informações em <a href="../../../userguide/pt_BR/bootloader.html">Carregador de Inicialização</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Erros de Dispositivo/Driver</a></h2>
|
||||
<p>Enquanto estiver lidando com um erro relativo a dispositivo/driver, deve-se anexar as seguintes informações como arquivos de texto:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>Uma lista detalhada do seu dispositivo, incluindo fornecedor e id's pci, similar ao <span class="cli">lshw</span> e <span class="cli">lspci</span> do Linux.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Supondo que seja um problema relacionado a USB, é similar ao <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>O relatório primário de sistema utilizado pelo Haiku, parecido com a depuração na tela durante a inicialização. Com o comando <span class="cli">open</span> pode-se cortar a parte relevante do relatório de sistema em um editor de texto.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Lista todos os drivers utilizados.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Apenas disponível na <i>Terra da Deupração do Kernel</i> (ver acima). Exibe a utilização das interrupções. There shouldn't be too many that are shared by different devices.</td></tr>
|
||||
<tr><td colspan="3">- Saída de depuração na tela (Uma opção de modo de segurança em tempo de inicialização).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>Os primeiros quatro comandos são executados no Terminal. Adicione um <span class="cli"> > output.txt</span> após um comando e ele será direcionado para um arquivo de texto chamado "output.txt" que pode ser anexado a seu relatório de erro ou mensagem de correio eletrônico.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">O que vem a seguir?</a></h2>
|
||||
<p>Após o erro ter sido reportado, um desenvolvedor irá dar uma olhada e tentar classificá-lo. Lembre-se, nós somos voluntários e, como tais, algumas vezes um relatório de erro pode ficar sem resposta por um tempo. Adicionar informação nova quando disponível geralmente ajuda a selecionar o problema mais rapidamente, mas não tente 'incrementar' o erro adicionando comentários não descritivos.</p>
|
||||
<p>Lembre-se, reportar um erro não é algo a que se dispensa um pouco de tempo e então está resolvido. Se reportou um erro, então você é parte do processo de desenvolvimento do Haiku. Desenvolvedores podem aparecer com perguntas enquanto eles estão tentando consertar o erro. Por favor esteja disponível para respondê-los. Considere sua participação 'terminada' quando o erro estiver marcado como 'corrigido'.</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_pt_BR.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,178 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Reporting bugs</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/pt_PT.png" alt="" /> Português</li>
|
||||
<li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_pt_PT.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
|
||||
<a href="#report">Creating a bug report</a><br />
|
||||
<a href="#app">Application bugs</a><br />
|
||||
<a href="#server">Server bugs</a><br />
|
||||
<a href="#kernel">Kernel bugs</a><br />
|
||||
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
|
||||
<a href="#syslog">Syslog</a><br />
|
||||
<a href="#onscreen">On screen debug output</a><br />
|
||||
<a href="#hardware">Hardware/Driver bugs</a><br />
|
||||
<a href="#next">What's next?</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>Reporting bugs</h1>
|
||||
|
||||
<p>Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.</p>
|
||||
<p>To keep our bugtracker effective, it's essential to abide by the <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Bug Tracker Etiquette</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Getting a Trac account</a></h2>
|
||||
<p>To file a ticket, you need to have an account at <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku's Bugtracker</a>.<br />
|
||||
When creating a new account, be certain to <b>provide your email address</b> as it is necessary to obtain basic ticket modification privileges. Be sure to <b>check your spam folder</b> shortly afterwards, as the all important verification mail often ends up there.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Creating a bug report</a></h2>
|
||||
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">search</a> function for this.<br />
|
||||
After you have established that it's a unique bug, make your information as accurate as possible:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
|
||||
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Application bugs</a></h2>
|
||||
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Server bugs</a></h2>
|
||||
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
|
||||
Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (<span class="cli">bt</span> command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Kernel bugs</a></h2>
|
||||
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<ul>
|
||||
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
|
||||
<li><p>The system reboots spontaneously.</p></li>
|
||||
<li><p>The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards). Wait at least a minute to see, if anything happens.</p></li>
|
||||
<li><p>The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).</p></li>
|
||||
</ul>
|
||||
<p>Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could blacklist the responsible Wifi driver from your Haiku installation (see <a href="../../../userguide/en/bootloader.html">Boot Loader</a>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Shows the handled and unhandled hardware interrupts.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (aka continue)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
|
||||
</table>
|
||||
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
|
||||
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Syslog</a></h3>
|
||||
<p><b>This is the preferred method for gaining information from a non-booting system.</b><br />
|
||||
The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file <span class="path">/boot/system/var/log/syslog</span>. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).</p>
|
||||
<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog persistent. If the option <span class="menu">Save syslog from previous session during boot</span> is activated in the boot loader options (as it is by default), you'll find the syslog of your last session as <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
If you're not able to boot to get to the previous_syslog, you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
|
||||
In the boot loader's <span class="menu">Debug menu</span> you should find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. Note: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">On screen debug output</a></h3>
|
||||
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../../userguide/pt_PT/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Hardware/Driver bugs</a></h2>
|
||||
<p>When dealing with a hardware/driver related bug, you should attach the following information as text files:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>A detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Lists all used drivers.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Only available within <i>Kernel Debugging Land</i> (see above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>The first four commands are entered into Terminal. Add a <span class="cli"> > output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">What's next?</a></h2>
|
||||
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
|
||||
non-descriptive comments.</p>
|
||||
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
|
||||
as 'fixed'.</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_pt_PT.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,159 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2010-2011, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta http-equiv="Content-Style-Type" content="text/css" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Wifi</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/pt_PT.png" alt="" /> Português</li>
|
||||
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
|
||||
<span>
|
||||
<a href="../welcome_pt_PT.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
|
||||
<h2>Wifi in Haiku</h2>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="hardware" rel="nofollow" id="hardware">Expected supported hardware</a></h3>
|
||||
<p>All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, PCI-Express, miniPci-Express and PCI-X are supposed to work.<br />
|
||||
This includes:
|
||||
</p>
|
||||
<ul>
|
||||
<li><p><i>aironetwifi</i> supporting at least<br />
|
||||
Cisco Aironet 350 Series<br />
|
||||
Aironet PCI4500<br />
|
||||
Aironet PCI4800<br />
|
||||
</p></li>
|
||||
<li><p><i>atheroswifi</i> supporting almost every chipset outthere (though no AR9285 chips)</p></li>
|
||||
<li><p><i>broadcom43xx</i> supporting<br />
|
||||
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318
|
||||
</p></li>
|
||||
<li><p><i>ipw2100</i> supporting Intel Pro Wireless 2100 chips</p></li>
|
||||
<li><p><i>iprowifi2200</i> supporting Intel Pro Wireless<br />
|
||||
2200BG<br />
|
||||
2225BG<br />
|
||||
2915ABG
|
||||
</p></li>
|
||||
<li><p><i>iprowifi3945</i> supporting Intel Pro Wireless 3945 chips</p></li>
|
||||
<li><p><i>iprowifi4965</i> supporting Intel Pro Wireless 4965 chips</p></li>
|
||||
<li><p><i>marvell88w8335</i> supporting<br />
|
||||
Marvell Libertas 88W8310<br />
|
||||
Marvell Libertas 88W8335
|
||||
</p></li>
|
||||
<li><p><i>marvell88w8363</i> supporting the 88W8363 chips</p></li>
|
||||
<li><p><i>ralinkwifi</i> supporting<br />
|
||||
RT2560<br />
|
||||
RT2561S<br />
|
||||
RT2561<br />
|
||||
RT2661
|
||||
</p></li>
|
||||
<li><p>ralink2860 supporting Ralink RT2860</p></li>
|
||||
<li><p><i>wavelanwifi</i> supporting at least<br />
|
||||
3Com Airconnect<br />
|
||||
GLPRISM2 WaveLAN<br />
|
||||
Intersil Prism3<br />
|
||||
Intersil Prism2.5<br />
|
||||
Linksys WDT11<br />
|
||||
Netgear MA301<br />
|
||||
PRISM2STA WaveLAN<br />
|
||||
Siemens SpeedStream<br />
|
||||
SMC 2602W<br />
|
||||
Us Robotics 2415<br />
|
||||
Addtron AWA-100 PCI
|
||||
</p></li>
|
||||
</ul>
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="connect" rel="nofollow" id="connect">Connecting to a wireless network</a></h3>
|
||||
<p>Besides of course unencrypted networks, Haiku has preliminary support for accessing wireless networks via <a href="#wep-notes" rel="nofollow">WEP encryption keys</a>. WEP is an early encryption method, although not the most secure.</p>
|
||||
<p>You can list available networks, join and leave them with the command <span class="cli">ifconfig</span> from Terminal:</p>
|
||||
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
|
||||
<p>You can find your <tt>wifi_device_path</tt> in the <span class="app">Network</span> preferences applet, or by executing <span class="cli">ifconfig -a</span>.</p>
|
||||
<p>Below are a few examples of connecting to a wireless network named <i>wifitopia</i>. For these examples we are assuming your wifi network card is <tt>/dev/net/iprowifi3945/0</tt>.</p>
|
||||
<h4>Listing wireless networks:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
|
||||
<h4>Joining unsecured wireless network:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
|
||||
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (ascii password)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
|
||||
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (64-bit hex password)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
|
||||
<h4>Leaving a wireless network:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="auto-connect" rel="nofollow" id="auto-connect">Automatically connecting to a wireless network</a></h3>
|
||||
<p>To make your system connect to a given SSID at each boot automatically, you can specify your wireless networks and passwords in <tt>/boot/common/settings/network/wireless_networks</tt> with the following format:</p>
|
||||
<pre>network wifitopia {
|
||||
password mypassword
|
||||
}</pre>
|
||||
<p>If you don't create this configuration file, the system will connect to the first unencrypted network it finds.</p>
|
||||
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP notes</strong></a></p>
|
||||
<ul>
|
||||
<li>64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex digits</li>
|
||||
<li>128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex digits</li>
|
||||
<li>hexadecimal digits = characters 0-9 and A through F (prepended with "0x" in <tt>ifconfig</tt>)</li>
|
||||
</ul>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="wpa" rel="nofollow" id="wpa">WPA encryption</a></h3>
|
||||
<p><p>At the moment there is no WPA encryption available in Haiku, though there have been <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">some efforts</a> bringing it significantly closer.</p></p>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
|
||||
<p>To install the firmware for Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you need to run</p>
|
||||
<pre class="terminal">install-wifi-firmwares.sh
|
||||
</pre>
|
||||
<p>The Intel ipw2100 and iprowifi22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.</p>
|
||||
<p>People building their own Haiku image can modify their <span class="cli">build/jam/UserBuildConfig</span> accordingly. Details for that and general updates on the wifi topic are found at the <a href="http://www.haiku-os.org/guides/wifi">online version of this document</a>.</p>
|
||||
<p>If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">shell script</a>, which will create a zip file for you to extract to Haiku's <tt>/boot</tt>. After that you'll have all files needed by install-wifi-firmwares.sh.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_pt_PT.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,180 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* Emrys
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Raportare defecțiuni</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Ghid de utilizare</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/ro.png" alt="" /> Română</li>
|
||||
<li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_ro.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Traducerea acestei pagini nu este completă încă. Până când va fi, părțile incomplete utilizează originalul în limba engleză.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
|
||||
<a href="#report">Creating a bug report</a><br />
|
||||
<a href="#app">Application bugs</a><br />
|
||||
<a href="#server">Server bugs</a><br />
|
||||
<a href="#kernel">Kernel bugs</a><br />
|
||||
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
|
||||
<a href="#syslog">Syslog</a><br />
|
||||
<a href="#onscreen">On screen debug output</a><br />
|
||||
<a href="#hardware">Hardware/Driver bugs</a><br />
|
||||
<a href="#next">What's next?</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>Raportare defecțiuni</h1>
|
||||
|
||||
<p>Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.</p>
|
||||
<p>To keep our bugtracker effective, it's essential to abide by the <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Bug Tracker Etiquette</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Obținerea unui cont Trac</a></h2>
|
||||
<p>To file a ticket, you need to have an account at <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku's Bugtracker</a>.<br />
|
||||
When creating a new account, be certain to <b>provide your email address</b> as it is necessary to obtain basic ticket modification privileges. Be sure to <b>check your spam folder</b> shortly afterwards, as the all important verification mail often ends up there.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Crearea unui raport de defecțiune</a></h2>
|
||||
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">search</a> function for this.<br />
|
||||
After you have established that it's a unique bug, make your information as accurate as possible:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
|
||||
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Defecțiuni de aplicație</a></h2>
|
||||
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Defecțiuni de server</a></h2>
|
||||
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
|
||||
Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (<span class="cli">bt</span> command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Defecțiuni de kernel</a></h2>
|
||||
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<ul>
|
||||
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
|
||||
<li><p>The system reboots spontaneously.</p></li>
|
||||
<li><p>The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards). Wait at least a minute to see, if anything happens.</p></li>
|
||||
<li><p>The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).</p></li>
|
||||
</ul>
|
||||
<p>Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could blacklist the responsible Wifi driver from your Haiku installation (see <a href="../../../userguide/en/bootloader.html">Boot Loader</a>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Shows the handled and unhandled hardware interrupts.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (aka continue)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
|
||||
</table>
|
||||
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
|
||||
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Syslog</a></h3>
|
||||
<p><b>This is the preferred method for gaining information from a non-booting system.</b><br />
|
||||
The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file <span class="path">/boot/system/var/log/syslog</span>. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).</p>
|
||||
<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog persistent. If the option <span class="menu">Save syslog from previous session during boot</span> is activated in the boot loader options (as it is by default), you'll find the syslog of your last session as <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
If you're not able to boot to get to the previous_syslog, you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
|
||||
In the boot loader's <span class="menu">Debug menu</span> you should find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. Note: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">On screen debug output</a></h3>
|
||||
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../../userguide/ro/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Hardware/Driver bugs</a></h2>
|
||||
<p>When dealing with a hardware/driver related bug, you should attach the following information as text files:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>A detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Lists all used drivers.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Only available within <i>Kernel Debugging Land</i> (see above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>The first four commands are entered into Terminal. Add a <span class="cli"> > output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">Ce urmează?</a></h2>
|
||||
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
|
||||
non-descriptive comments.</p>
|
||||
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
|
||||
as 'fixed'.</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_ro.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,182 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* Michael Smirnov
|
||||
* Diver
|
||||
* Rodastahm Islamov
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Отчёт об ошибках (багах)</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Руководство пользователя</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/ru.png" alt="" /> Русский</li>
|
||||
<li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_ru.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Перевод этой страницы еще не завершен. Пока это не произойдет, незавершенные части будут на английском.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Содержание</td></tr>
|
||||
<tr class="index"><td><a href="#account">Получение аккаунта в Trac</a><br />
|
||||
<a href="#report">Создание отчёта об ошибке</a><br />
|
||||
<a href="#app">Ошибки приложений</a><br />
|
||||
<a href="#server">Ошибки серверов</a><br />
|
||||
<a href="#kernel">Ошибки ядра</a><br />
|
||||
<a href="#kdl">Царство отладки ядра - KDL</a><br />
|
||||
<a href="#syslog">Системный журнал</a><br />
|
||||
<a href="#onscreen">Вывод отладочной информации на экран</a><br />
|
||||
<a href="#hardware">Аппаратные ошибки/Ошибки в драйверах</a><br />
|
||||
<a href="#next">Что дальше?</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>Отчёт об ошибках (багах)</h1>
|
||||
|
||||
<p>Так как наши разработчики не в состоянии проверить все комбинации компьютерных комплектующих и программных средств при их работе в Haiku, то мы полагаемся на пользователей, надеясь, что вы сообщите нам об обнаруженных ошибках, которых, ввиду молодости Haiku, может быть немало. Мы будем благодарны вам за потраченное на составление отчёта время, только вместе мы сможем сделать Haiku лучше.</p>
|
||||
<p>Для продуктивной работы c системой отслеживания ошибок (багтрекером) важно соблюдать принятый в нём <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">этикет</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Получение аккаунта в Trac</a></h2>
|
||||
<p>Чтобы создать новый багрепорт, у вас должен быть заведён аккаунт в <a href="http://dev.haiku-os.org/register" title="Регистрация в багтрекере Haiku">багтрекере Haiku</a>.<br />
|
||||
Создавая новый аккаунт <b>обязательно введите адрес электронной почты</b>, так как на него будут приходить все сведения, связанные с изменением багрепорта. Убедитесь, что приходящие с багтрекера письма <b>не помечаются как спам,</b> так как это вполне возможно.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Создание отчёта об ошибке</a></h2>
|
||||
<p>Прежде чем сообщать об ошибке, пожалуйста, <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Eтекст,+который+вы+ищите&order=priority">убедитесь</a>, что аналогичного багрепорта ещё не существует. Для этого также можно воспользоваться функцией <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">поиска</a>.<br />
|
||||
После того как вы установили, что подобных багрепортов не имеется, то оформите вашу информацию как можно точнее:</p>
|
||||
<ul>
|
||||
<li><p>Попытайтесь воспроизвести вашу проблему на текущей ревизии Haiku. Готовые образы для тестирования доступны <a href="http://haiku-files.org/">здесь</a>.</p></li>
|
||||
<li><p>Включите информацию о том как вы тестируете Haiku (на реальном компьютере, в эмуляторе VMWare, QEMU, и т. д.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Опишите проблему, с которой вы столкнулись, попытайтесь описать её наиболее точно: как именно она проявилась, и как правильно должен бы был действовать проблемный объект при её отсутствии.</p></li>
|
||||
<li><p>Расскажите какие шаги нужно выполнить для её возникновения, что поможет разработчикам воспроизвести эту ошибку.</p></li>
|
||||
<li><p>Прикрепите всю имеющуюся информацию. Если это ошибка графического интерфейса или баг в каком-либо приложении, то попытайтесь сделать скриншот клавишей <span class="key">Print Screen</span> key.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Ошибки приложений</a></h2>
|
||||
<p>Когда приложение аварийно завершилось, вы должны запустить отладчик из окна сообщения о падении программы. Откроется окно Терминала с запущенным gdb (the GNU debugger). Введя в окне терминала <span class="cli">bt</span>, вы создадите "трассировку", которую необходимо полностью скопировать (включая текст, который уже был до ввода команды <span class="cli">bt</span>) и прикрепить ее в ваш багрепорт.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Ошибки серверов</a></h2>
|
||||
<p>Когда жизненно важный сервер, такой как app server, registrar или input server падает, вы не увидите обычное сообщение о падении приложения. Вместо этого весь экран станет белым и запустится gdb сессия, ее вывод будет попадать напрямую на экран. Скорее всего вы все еще сможете двигать курсором, что приведет к перезаписи участков белого экрана с выводом. Все еще работающие приложения (например Контроллер процессов или часы в Deskbar) могут также прорисовываться сквозь вывод отладчика на экран.<br />
|
||||
Кроме того, что все более выглядит более страшно и неудобно, применимо все то же самое, что и в случае ошибок приложений. Самое важное в данном случае - это выполнение трассировки коммандой (<span class="cli">bt</span>). Скорее всего вам понадобится сфотографировать экран, так как будет невозможно куда либо скопировать текст трассировки.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Ошибки ядра</a></h2>
|
||||
<p>Ошибки ядра обычно вызывают наиболее серьезные последствия и в тоже время их сложнее отлаживать. Существуют различные типы симптомов, которые скорее всего указывают на ошибку в ядре или на проблему с каким-либо драйвером:</p>
|
||||
<ul>
|
||||
<li><p>Система входит в царство отладки ядра (KDL) по собственному желанию. Верхняя часть экрана станет белой и появятся несколько строчек текста. Во второй стоке будет написано "<i>Welcome to Kernel Debugging Land...</i>", выше этой строки будет указана непосредственная причина входа в KDL.</p></li>
|
||||
<li><p>Система спонтанно перезагружается.</p></li>
|
||||
<li><p>Система полностью зависает. Курсор не двигается и ни одно приложение не выводит и не прорисовывает ничего на экран. Важный тестом в данном случае является проверка, пожете ли вы все еще войти в KDL через комбинацию клавиш <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (эквивалентом <span class="key">SysReq</span> является <span class="key">PrintScreen</span> на большинстве клавиатур). Подождите несколько минут и посмотрите, произойдет ли что-нибудь.</p></li>
|
||||
<li><p>Система не загружается корректно. Она может спонтанно перезагружаться на каком-то моменте или зависать (например на каком-то значке экрана загрузки). В случае зависания попробуйте нажать <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>Система или какое-то устройство не работает нормально. Например если она работает очень медленно, появляются ошибки, или что-то вообще не работает. Если какое-то устройство вообще не работает первое что нужно проверить это поддерживает ли его Haiku в данный момент (например спросить в списке рассылки или на форуме).</p></li>
|
||||
</ul>
|
||||
<p>Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could blacklist the responsible Wifi driver from your Haiku installation (see <a href="../../../userguide/en/bootloader.html">Boot Loader</a>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Царство отладки ядра - KDL</a>
|
||||
</h3>
|
||||
<p>Когда какой-либо системный низкоуровневый компонент вызывает фатальную ошибку, то вы, с большой долей вероятности, окажетесь в отладчике ядра. Также он может быть вызван намеренно при нажатии на клавиши <span class="key">ALT</span>+<span class="key">SysReq</span>+<span class="key">D</span> (клавиша <span class="key">SysReq</span> называется <span class="key">PrintScreen</span> на большинстве клавиатур).
|
||||
Учтите, что ваша клавиатура может не работать в KD. PS/2 клавиатуры работают всегда, USB клавиатуры, подключенные через UHCI контроллер работают, только если вы входили в KDL через клавиатурное сочетание хотя бы раз. USB OHCI не поддерживаются в данный момент.</p>
|
||||
<p>Сам по себе KDL является некой оболочкой. Вы можете выполнять команды, которые выводят информацию о системе. Следующие команды могут быть интересны:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (синоним sc)</td><td> </td><td><span class="cli">bt</span> - покажет трассировку, уточняющую где именно произошла ошибка.
|
||||
Если система вошла в KDL самопроизвольно, всегда используйте эту команду.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td><span class="cli">int</span> - отобразит обработанные и необработанные прерывания.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (синоним continue)</td><td> </td><td>выведет систему из отладчика ядра продолжит нормальную работу Haiku, если это возможно.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Немедленно перезагрузит систему. Вы потеряете все несохраненные данные и те, что были сохранены, но еще не успели записаться из памяти обратно на диск.</td></tr>
|
||||
</table>
|
||||
<p>Для более подробной информации смотрите статью <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Добро пожаловать в Царство Отладки Ядра</a>.</p>
|
||||
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
|
||||
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Системный журнал</a></h3>
|
||||
<p><b>This is the preferred method for gaining information from a non-booting system.</b><br />
|
||||
The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file <span class="path">/boot/system/var/log/syslog</span>. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).</p>
|
||||
<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog persistent. If the option <span class="menu">Save syslog from previous session during boot</span> is activated in the boot loader options (as it is by default), you'll find the syslog of your last session as <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
If you're not able to boot to get to the previous_syslog, you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
|
||||
In the boot loader's <span class="menu">Debug menu</span> you should find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. Note: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">Вывод отладочной информации на экран</a></h3>
|
||||
<p><b>Функция вывода отладочной информации на экран полезна для отладки только специфичных проблем, она также имеет известные проблемы с таймингами. Используйте ее только если это очень необходимо.</b><br />
|
||||
Ее использование имеет смысл только когда Haiku не загружается на вашем компьютереи функция <span class="menu">Debug syslog option</span> по какой-то причине не работает. Перед появлением загрузочного экрана зажмите <span class="key">SHIFT</span> для входа в меню загрузчика. Выберите <span class="menu">Select safe mode options</span>. Почти в самом низу будет опция, <span class="menu">[ ] Enable on screen debug output</span>. (Имейте в виду, что можно включить остальные опции, чтобы Haiku загрузилась. Если Haiku будет загружаться только при включении одной или более опций, не забудьте указать какие именно.)<br />
|
||||
И наконец выбарите <span class="menu">Return to main menu</span>, а затем then <span class="menu">Continue booting</span>.<br />
|
||||
Одна страница текста или более появятся на экране, только последние несколько строк нужно включать в ваш багрепорт. Дополнительная информация имеется в статье <a href="../../../userguide/ru/bootloader.html">Загрузчик</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Аппаратные ошибки/Ошибки в драйверах</a></h2>
|
||||
<p>Если вы столкнулись с ошибкой работы оборудования и/или драйвера, то вы должны приложить к вашему багрепорту следующую информацию в виде текстовых файло:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td><span class="cli">listdev</span> - подробный список оборудования, включающий ID производителей и отдельных устройств, схожа с командами Linux <span class="cli">lshw</span> и <span class="cli">lspci</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td><span class="cli">listusb -v</span> - используйте при ошибке, связанной с USB, аналогична команде <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td><span class="cli">open /var/log/syslog</span> - основной системный лог, используемый Haiku. С командой <span class="cli">open</span> можно вырезать нужную часть лога в текстовом редакторе.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td><span class="cli">listimage | grep drivers/</span> - список всех загруженных драйверов.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td><span class="cli">ints</span> - доступна только в режиме <i>Царства отладки ядра (Kernel Debugging Land - KDL)</i> (см. выше). Отображает используемые прерывания. Не должно быть слишком много устройств, использующих одно прерывание.</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (опция загрузочного меню).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>Все эти команды вводятся в терминале, если не указано иное. Если добавить <span class="cli"> > output.txt</span> после команды, то результат её работы сохранится в текстовый файл "output.txt", который можно прикрепить к своему сообщению об ошибке или отправить по электронной почте.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">Что дальше?</a></h2>
|
||||
<p>После того как багрепорт отправлен, разработчик рассмотрит вашу ошибку и попытаться классифицировать ее. Помните, что мы все добровольцы, и иногда багрепорт может оставаться без ответа некоторое время. Добавление новой информации к этой ошибке помогает исправить её быстрее, но не пытайтесь увеличить её значимость, добавляя не относящиеся к делу комментарии.</p>
|
||||
<p>Помните, что отправка багрепорта, на который вы потратили некоторое время - это ещё полдела, и желательно чтобы вы следили за его состоянием. Только в этом случае вы внесёте ощутимую часть в процесс развития Haiku. У разработчиков могут возникнуть вопросы, относящиеся к багу во время его исправления, пожалуйста, не игнорируйте их, постаравшись как можно подробней ответить. Считайте свое участие законченным, только когда ошибка приобретёт статус "исправлено (fixed)".</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_ru.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,162 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2010-2011, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* Diver
|
||||
* Rodastahm Islamov
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta http-equiv="Content-Style-Type" content="text/css" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Беспроводная сеть Wifi</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Руководство пользователя</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/ru.png" alt="" /> Русский</li>
|
||||
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
|
||||
<span>
|
||||
<a href="../welcome_ru.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
|
||||
<h2>Беспроводная сеть Wifi в Haiku</h2>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="hardware" rel="nofollow" id="hardware">Поддерживаемое оборудование:</a></h3>
|
||||
<p>Должны работать все wlan драйвера, поддерживаемые FreeBSD 8. <br />
|
||||
Не поддерживаются все PCMCIA, CardBus, ExpressCard, USB и ISA карты. <br />Поддерживаются только PCI, miniPCI, PCI-Express, miniPci-Express и PCI-X.<br />
|
||||
|
||||
</p>
|
||||
<ul>
|
||||
<li><p><i>aironetwifi</i> поддерживает как минимум:<br />
|
||||
Cisco Aironet 350 Series<br />
|
||||
Aironet PCI4500<br />
|
||||
Aironet PCI4800<br />
|
||||
</p></li>
|
||||
<li><p><i>atheroswifi</i> поддерживает почти все существующие чипсеты (кроме чипов AR9285)</p></li>
|
||||
<li><p><i>broadcom43xx</i> поддерживает:<br />
|
||||
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318
|
||||
</p></li>
|
||||
<li><p><i>iprowifi2100</i> поддерживает Intel Pro Wireless 2100 чипы</p></li>
|
||||
<li><p><i>iprowifi2200</i> поддерживает следующие Intel Pro Wireless чипы:<br />
|
||||
2200BG<br />
|
||||
2225BG<br />
|
||||
2915ABG
|
||||
</p></li>
|
||||
<li><p><i>iprowifi3945</i> поддерживает Intel Pro Wireless 3945 чипы</p></li>
|
||||
<li><p><i>iprowifi4965</i> поддерживает Intel Pro Wireless 4965 чипы</p></li>
|
||||
<li><p><i>marvell88w8335</i> поддерживает:<br />
|
||||
Marvell Libertas 88W8310<br />
|
||||
Marvell Libertas 88W8335
|
||||
</p></li>
|
||||
<li><p><i>marvell88w8363</i> поддерживает 88W8363 чипсет</p></li>
|
||||
<li><p><i>ralinkwifi</i> поддерживает:<br />
|
||||
RT2560<br />
|
||||
RT2561S<br />
|
||||
RT2561<br />
|
||||
RT2661
|
||||
</p></li>
|
||||
<li><p>ralink2860 поддерживает Ralink RT2860 чипы</p></li>
|
||||
<li><p><i>wavelanwifi</i> поддерживает как минимум:<br />
|
||||
3Com Airconnect<br />
|
||||
GLPRISM2 WaveLAN<br />
|
||||
Intersil Prism3<br />
|
||||
Intersil Prism2.5<br />
|
||||
Linksys WDT11<br />
|
||||
Netgear MA301<br />
|
||||
PRISM2STA WaveLAN<br />
|
||||
Siemens SpeedStream<br />
|
||||
SMC 2602W<br />
|
||||
Us Robotics 2415<br />
|
||||
Addtron AWA-100 PCI
|
||||
</p></li>
|
||||
</ul>
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="connect" rel="nofollow" id="connect">Подключение к беспроводной сети</a></h3>
|
||||
<p>Помимо открытых беспроводных сетей Haiku поддерживает беспроводные сети с <a href="#wep-notes" rel="nofollow">WEP-шифрованием</a>. WEP является одним из первых методов шифрования для беспроводных сетей, поэтому считается устаревшим т.к. взламывается за пару минут.</p>
|
||||
<p>Вы можете получить список доступных сетей, подключиться либо отключиться от сети при помощи команды <span class="cli">ifconfig</span>, используя Терминал:</p>
|
||||
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
|
||||
<p>Найти ваш <tt>wifi_device_path</tt> вы можете в окне настроек <span class="app">Сети (Network)</span>, либо выполнив в Терминале команду <span class="cli">ifconfig -a</span>.</p>
|
||||
<p>Ниже приведены примеры подключения к сети с названием <i>wifitopia</i>, в которых предполагается, что вашей беспроводной картой является <tt>/dev/net/iprowifi3945/0</tt>.</p>
|
||||
<h4>Список беспроводных сетей:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
|
||||
<h4>Подключение к открытой беспроводной сети:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
|
||||
<h4>Подключение к беспроводной сети с <a href="#wep-notes">WEP-шифрованием</a>: (ascii-пароль)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
|
||||
<h4>Подключение к беспроводной сети с <a href="#wep-notes">WEP-шифрованием</a>: (64-битный hex-пароль)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
|
||||
<h4>Отключение от беспроводной сети:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="auto-connect" rel="nofollow" id="auto-connect">Автоматическое подключение к беспроводной сети</a></h3>
|
||||
<p>Для того, чтобы система после загрузки подключалась к определённой беспроводной сети, следует создать файл по следующему адресу:<tt>/boot/common/settings/network/wireless_networks</tt>, который имеет формат:</p>
|
||||
<pre>network wifitopia {
|
||||
password mypassword
|
||||
}</pre>
|
||||
<p>Если вы не создадите этот файл, то система будет подключаться к первой попавшейся открытой сети.</p>
|
||||
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>Примечания про WEP</strong></a></p>
|
||||
<ul>
|
||||
<li>64-битное WEP использует 40-битный ключ, что эквивалентно 5 буквам или 10 цифрам</li>
|
||||
<li>128-битное WEP использует 104-битный ключ, что эквивалентно 13 буквам или 26 цифрам</li>
|
||||
<li>шестнадцатеричная система = цифры 0-9 и буквы от A до F (начинающиеся с "0x" в <tt>ifconfig</tt>)</li>
|
||||
</ul>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="wpa" rel="nofollow" id="wpa">WPA шифрование</a></h3>
|
||||
<p><p>В настоящий момент WPA шифрование не поддерживается в Haiku. Однако сделана <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">попытка</a> добавить поддержку WPA.</p></p>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="install_script" rel="nofollow" id="install_script">Сценарий для установки микропрограмм (firmwares).</a></h3>
|
||||
<p>Для установки микропрограмм для Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx и Marvell 88W8335 нужно запустить:</p>
|
||||
<pre class="terminal">~> install-wifi-firmwares.sh
|
||||
</pre>
|
||||
<p>Intel ipw2100 и iprowifi22xx установятся без Интернет-соединения, так как лицензионные условия позволяют Haiku распространять архивы с микропрограммой (firmware). Однако они требуют ознакомления конечного пользователя с условиями лицензии перед их установкой. Broadcom 43xx и Marvell 88W8335 требуют работающего Интернет-соединения, так как файлы, содержащие их микропрограммы (firmwares), не могут распространяться с Haiku.</p>
|
||||
<p>Те, кто самостоятельно собирают собственные образы Haiku, могут соответственным образом изменить свой <span class="cli">build/jam/UserBuildConfig</span>. Описание этого процесса, а также обновление информации по поддержке wifi можно найти в <a href="http://www.haiku-os.org/guides/wifi">онлайн-версии</a> этого документа.</p>
|
||||
<p>Если вы скачали микропрограмму (firmware), но не имеете работающего Интернет-соединения в Haiku, то онлайн-версия предлагает <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">скрипт</a>, который создаст для Вас zip файл, который нужно будет извлечь в директорию <tt>/boot</tt>. После этого у Вас будут все файлы, необходимые для запуска install-wifi-firmwares.sh.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_ru.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,180 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* helix84
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Nahlasovanie chýb</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Používateľská príručka</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/sk.png" alt="" /> Slovenčina</li>
|
||||
<li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_sk.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Preklad tejto stránky zatiaľ nie je dokončený. Dovtedy sa nedokončené časti zobrazia v anglickom origináli.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Obsah</td></tr>
|
||||
<tr class="index"><td><a href="#account">Získanie účtu v Trac</a><br />
|
||||
<a href="#report">Vytvorenie hlásenia o chybe</a><br />
|
||||
<a href="#app">Chyby aplikácií</a><br />
|
||||
<a href="#server">Chyby serverov</a><br />
|
||||
<a href="#kernel">Chyby jadra</a><br />
|
||||
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
|
||||
<a href="#syslog">Syslog</a><br />
|
||||
<a href="#onscreen">Výstup ladenia na obrazovku</a><br />
|
||||
<a href="#hardware">Chyby hardvéru/ovládačov</a><br />
|
||||
<a href="#next">Čo ďalej?</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>Nahlasovanie chýb</h1>
|
||||
|
||||
<p>Keďže je nemožné, aby naši vývojári otestovali každú kombináciu hardvéru či každý možný spôsob interakcie s operačným systémom, spoliehame sa na našich používateľov, aby nám poslali spätnú väzbu ako veci fungujú u nich. Keďže Haiku je stále relatívne mladé, je veľmi pravdepodobné, že narazíte na chyby. ďakujeme vám za čas, ktorý venujete ich nahláseniu. Spolu môžeme Haiku vylepšovať, trochu po troche.</p>
|
||||
<p>Aby bol náš nástroj na sledovanie chýb fungoval efektívne, je nevyhnutné dodržiavať <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Etiketu nástroja na sledovanie chýb</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Získanie účtu v Trac</a></h2>
|
||||
<p>Aby ste mohli založiť hlásenie, musíte mať účet v <a href="http://dev.haiku-os.org/register" title="Registrácia v nástroji na sledovanie chýb Haiku">Nástroji na sledovanie chýb Haiku</a>.<br />
|
||||
Pri vytváraní účtu určite poskytnite <b>vašu emailovú adresu</b>, pretože je potrebné získať základné oprávnenia na zmenu hlásení. Určite sa krátko potom <b>pozrite aj do spamového priečinka</b>, pretože dôležité overovacie emaily tam často skončia.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Vytvorenie hlásenia o chybe</a></h2>
|
||||
<p>Pred nahlásením chyby sa prosím <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">uisitite</a>, že už nebola nahlásená. Tiež na to môžete použiť funkciu <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">hľadanie</a>.<br />
|
||||
Potom, ako ste sa uistili, že chyba je jedinečná, uveďte čo najpresnejšie vaše informácie:</p>
|
||||
<ul>
|
||||
<li><p>Pokúste sa reprodukovať problém v aktuálnej revízii Haiku. Sú pripravené <a href="http://haiku-files.org/">obrazy na testovacie účely</a>.</p></li>
|
||||
<li><p>iveďte základné infomrácie o tom ako testujete Haiku (na skutočnom hardvéri, vo VMWare, v QEMU atď.).</p></li>
|
||||
<li><p>Uveďte, ktorú revíziu používate. Túto informáciu nájdete v dialógu <span class="menu">O Haiku...</span> z menu Panela. Tiež uvete, aký druh Haiku testujete (gcc2, gcc4, gcc2hybrid, gcc4hybrid). Obrazy na stiahnutie sú podľa toho pomenované; pri obraze, ktorý ste zostavili sami by ste mali vedieť ako ste ho zostavili.</p></li>
|
||||
<li><p>Popíšte váš problém. Skúste byč čo najpresnejší: popíšte správanie, ktoré ste očakávali a správanie, ktoré ste dostali.</p></li>
|
||||
<li><p>Popíšte kroky, ktoré je potrebné vykonať na vyvolanie chyby. To pomôže vývojárom chybu reprodukovať.</p></li>
|
||||
<li><p>Priložte všetky informácie,ktoré máte k dispozícii. Ak je to chyba používateľského rozhrania alebo chyba v niektorej z aplikácií, skúste urobiť snímku obrazovky stlačením klávesu <span class="key">Print Screen</span>.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Chyby aplikácií</a></h2>
|
||||
<p>Keď aplikácia havaruje, mali by ste vyvolať ladiaci nástroj z upozornenia, ktoré vyskočí. To otvorí okno Terminálu, v ktorom beží gdb (GNU debugger). Zadaním <span class="cli">bt</span> vytvoríte „backtrace“, ktorý by ste mali kompletne skopírovať (vrátane časti zorbazenej než ste zadali príkaz <span class="cli">bt</span>) a priložiť ho k hláseniu.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Chyby serverov</a></h2>
|
||||
<p>Ak havarujú dôležité servery ako aplikačný server, registrátor alebo server vstupu, neuvidíte zvyčajné upozornenie na haváriu. Namiesto toho sa celá obrazovka zmaže na bielu farbu, spustí sa relácia gdb a jej výstup sa objaví priamo na obrazovke. Pravdepodobne budete môcť pohybovať myšou, čo prepíše bielu farbu a výstup gdb na obrazovke. Aplikácie, ktoré ešte bežia (ako ProcessController alebo hodiny v Paneli) tiež možno prekreslia časť ladiaceho výstupu na obrazovke.<br />
|
||||
Okrem toho, že je všetko škaredšie a nepohodlné platí prakticky to isté ako pri chybách aplikácií. Predovšetkým získajte backtrace (príkaz <span class="cli">bt</span>). Možno budete musieť odfotiť obrazovku digitálnym fotoaparátom, pretože nebudete môcť text nikam skopírovať.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Chyby jadra</a></h2>
|
||||
<p>Chyby jadra sú zvyčajne tie, ktoré majú najzávažnejší vplyv a zároveň sa najťažšie ladia. Existujú rôzne druhy symptómov, ktoré pravdepodobne naznačujú problém s jadrom alebo ovládačom:</p>
|
||||
<ul>
|
||||
<li><p>Systém svojvoľne vstúpi KDL (kernel debugging land). Horná časť obrazovky sa vyčistí do biela a vypíše sa na ňu niekoľko riadkov textu. Druhý riadok bude obsahovať „<i>Welcome to Kernel Debugging Land...</i>“ a ten nad ním bude obsahovať okamžitý dôvod, prečo bolo vyvolané KDL.</p></li>
|
||||
<li><p>Systém sa spontánne reštartuje.</p></li>
|
||||
<li><p>Systém kompletne zamrzne. Nemôžete hýbať myšou a žiadna aplikácia nič nevykresľuje. Dôležitý test v tejto situácii je, či ešte môžete vyvolať KDL klávesovou skratkou <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> je na väčšine klávesníc <span class="key">PRINT</span>). Počkajte aspoň minútu, aby ste uvideli, či sa niečo stane.</p></li>
|
||||
<li><p>Systém nenaštartuje korektne. Môže spontánne naštartovať alebo v niektorom bode zastaviť (napr. na niektorej ikone štartovacej obrazovky). V druhom prípade tiež skúste <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>Celý systém alebo niektorá časť hardvéru sa nespráva korektne. Napríklad môže byť veľmi pomalý, vyskytnú sa chyby alebo niečo vôbec nefunguje. Ak nejaký hardvér vôbec nefunguje, prvá vec, ktorú treba skontrolovať je, či ho momentálne Haiku vôbec podporuje (napr. spýtať sa v poštovej konferencii alebo na fóre).</p></li>
|
||||
</ul>
|
||||
<p>Pamätajte, že hoci iba posledný bod indikuje súvislosť s hardvérom, všetky ostatné symptómy môžu byť spôsobené aj chybou v ovládači hardvéru. Ak máte podozrenie, ktorá časť hardvéru alebo zodpovedajúci ovládač môže súvisieť s problémom, skontrolujte, či odstránenie alebo vypnutie hardvéru či ovládača pomôže. Napríklad ak podozrievate Wi-Fi, možno zistíte, že váš BIOS umožňuje ju vypnúť. Alebo ak nie, môžete odstrániť príslušný ovládač Wi-Fi z vašej inštalácie Haiku (pozri <a href="../../../userguide/en/bootloader.html">Zavádzač systému</a>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>Ak systém sám nevstúpil do KDL, môžete ho úmyselne vyvolať klávesovou skratkou <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Pamätajte, že v KDL vaša klávesnica nemusí fungovať. Klávesnice PS/2 fungujú vždy, klávesnice USB pripojené prostredníctvom ovládačov UHCI fungujú iba ak už aspoň raz ste vstúpili do KDL použitím klávesovej skratky. USB OHCI momentálne nie je podporované.</p>
|
||||
<p>Samotné KDL je istým druhom shellu. Môžete vykonávať príkazy, ktoré vypisujú informácie o systéme. Nasledovné príkazy môžu byť zaujímavé:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (resp. sc)</td><td> </td><td>Vypíše backtrace. Ak systém svojvoľne vstúpil do KDL, vždy ho spustite.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Zobrazí ošetrené a neošetrené hardvérové prerušenia.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (resp. continue)</td><td> </td><td>Opustí ladenie jadra a pokračuje v normálnej prevádzke systému ak je to možné.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Okamžite reštartuje systém. Stratíte všetky neuložené dáta a aj tie, ktoré už boli uložené, ale zatiaľ neboli zapísané na disk.</td></tr>
|
||||
</table>
|
||||
<p>Ďalšie informácie nájdete v článku <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
<p>Výstup KDL sa zapisuje na sériový port (ak ho máte a ak máte príslušný kábel na pripojenie druhého počítača, môžete prostredníctvom neho zachytiť výstup pomocou terminálového programu) a do syslogu. Ak nemôžete opustiť KDL, nezapíše však sa do súboru syslog. Existuje voľba zavádzača systému, ktorá vám umožňuje zachytiť ho napriek tomu (pozri nižšie).</p>
|
||||
<p>Môžete vygenerovať QR kódy z výstupu KDL, ktoré je možné previesť na text pomocou smartfónu alebo podobných zariadení. V príspevku na blogu <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> nájdete informácie o tom, ako získať dáta z KDL pomocou tejto funkcie.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Syslog</a></h3>
|
||||
<p><b>Toto je preferovaný spôsob ako získať informácie zo systému, ktorý nejde naštartovať.</b><br />
|
||||
Syslog (skratka system log) obsahuje cenné informácie o tom, čo sa na vašom systéme stalo vrátane výstupu ladenia KDL. Zvyčajne je dobrý nápad pripojiť ho k súvisiacemu hláseniu v systéme Trac. Syslog sa zapisuje do súboru <span class="path">/boot/system/var/log/syslog</span>. Pretože zapisovanie do súbory vyžaduje, aby bol systém funkčný, je možné, že posledný výstup po výskyte problému s jadrom sa do syslogu už nedostal (obzvlášť pri samovoľných reštartoch alebo reláciách KDL, v ktorých nemožno pokračovať).</p>
|
||||
<p>Voľba <span class="menu">Zapnúť ladiaci syslog</span> v <span class="menu">menu Ladenie</span> zavádzača systému zabezpečí, že syslog bude trvalo uložený. Ak je v nastaveniach zavádzača systému zapnutá voľba <span class="menu">Uložiť syslog z predchádzajúcej relácie pri štarte</span> (predvolene je zapnutá), nájdete syslog vašej poslednej relácie v súbore <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
Ak sa vám nedarí spustiť systém, aby ste sa dostali k poslednému syslogu (previous_syslog), musíte vstúpiť do menu zavádzača podržaním klávesu <span class="key">SHIFT</span> počas štartu systému.<br />
|
||||
V <span class="menu">menu Ladenie</span> zavádzača by ste mali nájsť položky <span class="menu">Zobraziť syslog z predošlej relácie</span> a <span class="menu">Uložiť syslogz predošlej relácie</span>. Prvá z nich zobrazí syslog na obrazovke, druhá z nich vám umožní uložiť ho ako súbor na disk. Pamätajte, že momentálne sú na ukladanie súboru podporované iba zväzky so súborovým systémom FAT32. Ak chcete použiť disk USB, ale zapojili ste ho príliš neskoro a nebol zatiaľ rozpoznaný, môžete reštartovať počítač a znovu vstúpiť do menu zavádzača. Pozn.: Vyhnite sa automatickému spusteniu akéhokoľvek operačného systému, inak sa dáta posledného syslogu môžu stratiť.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">Výstup ladenia na obrazovku</a></h3>
|
||||
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../../userguide/sk/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Chyby hardvéru/ovládačov</a></h2>
|
||||
<p>Ak sa potýkate s chybou súvisiacou s hardvérom alebo ovládačom, mali by ste k hláseniu priložiť nasledovné informácie vo forme textových súborov:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>Podrobný výpis vášho hardvéru vrátane dodávateľa a PCI ID, podobný ako <span class="cli">lshw</span> a <span class="cli">lspci</span> v Linuxe.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Za predpokladu, že sa problém týka USB, je podobný ako <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Primárny protokol systému, ktorý Haiku používa, podobný ladeniu na obrazovku počas štartu systému. Príkazom <span class="cli">open</span> môžete vystrihnúť relevantnú časť syslogu v textovom editore.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Vypíše všetky použité ovládače.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Dostupné iba v rámci <i>(KDL) Kernel Debugging Land</i> (pozri vyššie). Zobrazuje použitie prerušení. Nemalo by sa vyskytovať mnoho takých, ktoré používajú viaceré zariadenia.</td></tr>
|
||||
<tr><td colspan="3">- Ladiaci výstup na obrazovke (voľba Bezpečný režim počas štartu systému).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>Prvé štyri príkazy sú zadané do Terminálu. Keď za príkaz pridáte <span class="cli"> > output.txt</span>, výstup sa zapíše do textového súboru s názvom „output.txt“, ktorý môžete priložiť k vášmu hláseniu chyby alebo emailu.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">Čo ďalej?</a></h2>
|
||||
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
|
||||
non-descriptive comments.</p>
|
||||
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
|
||||
as 'fixed'.</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_sk.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,161 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2010-2011, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* helix84
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta http-equiv="Content-Style-Type" content="text/css" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Wi-Fi</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Používateľská príručka</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/sk.png" alt="" /> Slovenčina</li>
|
||||
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
|
||||
<span>
|
||||
<a href="../welcome_sk.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Preklad tejto stránky zatiaľ nie je dokončený. Dovtedy sa nedokončené časti zobrazia v anglickom origináli.</div>
|
||||
|
||||
<h2>Wi-Fi v Haiku</h2>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="hardware" rel="nofollow" id="hardware">Expected supported hardware</a></h3>
|
||||
<p>All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, PCI-Express, miniPci-Express and PCI-X are supposed to work.<br />
|
||||
This includes:
|
||||
</p>
|
||||
<ul>
|
||||
<li><p><i>aironetwifi</i> supporting at least<br />
|
||||
Cisco Aironet 350 Series<br />
|
||||
Aironet PCI4500<br />
|
||||
Aironet PCI4800<br />
|
||||
</p></li>
|
||||
<li><p><i>atheroswifi</i> supporting almost every chipset outthere (though no AR9285 chips)</p></li>
|
||||
<li><p><i>broadcom43xx</i> supporting<br />
|
||||
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318
|
||||
</p></li>
|
||||
<li><p><i>ipw2100</i> supporting Intel Pro Wireless 2100 chips</p></li>
|
||||
<li><p><i>iprowifi2200</i> supporting Intel Pro Wireless<br />
|
||||
2200BG<br />
|
||||
2225BG<br />
|
||||
2915ABG
|
||||
</p></li>
|
||||
<li><p><i>iprowifi3945</i> supporting Intel Pro Wireless 3945 chips</p></li>
|
||||
<li><p><i>iprowifi4965</i> supporting Intel Pro Wireless 4965 chips</p></li>
|
||||
<li><p><i>marvell88w8335</i> supporting<br />
|
||||
Marvell Libertas 88W8310<br />
|
||||
Marvell Libertas 88W8335
|
||||
</p></li>
|
||||
<li><p><i>marvell88w8363</i> supporting the 88W8363 chips</p></li>
|
||||
<li><p><i>ralinkwifi</i> supporting<br />
|
||||
RT2560<br />
|
||||
RT2561S<br />
|
||||
RT2561<br />
|
||||
RT2661
|
||||
</p></li>
|
||||
<li><p>ralink2860 supporting Ralink RT2860</p></li>
|
||||
<li><p><i>wavelanwifi</i> supporting at least<br />
|
||||
3Com Airconnect<br />
|
||||
GLPRISM2 WaveLAN<br />
|
||||
Intersil Prism3<br />
|
||||
Intersil Prism2.5<br />
|
||||
Linksys WDT11<br />
|
||||
Netgear MA301<br />
|
||||
PRISM2STA WaveLAN<br />
|
||||
Siemens SpeedStream<br />
|
||||
SMC 2602W<br />
|
||||
Us Robotics 2415<br />
|
||||
Addtron AWA-100 PCI
|
||||
</p></li>
|
||||
</ul>
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="connect" rel="nofollow" id="connect">Connecting to a wireless network</a></h3>
|
||||
<p>Besides of course unencrypted networks, Haiku has preliminary support for accessing wireless networks via <a href="#wep-notes" rel="nofollow">WEP encryption keys</a>. WEP is an early encryption method, although not the most secure.</p>
|
||||
<p>You can list available networks, join and leave them with the command <span class="cli">ifconfig</span> from Terminal:</p>
|
||||
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
|
||||
<p>You can find your <tt>wifi_device_path</tt> in the <span class="app">Network</span> preferences applet, or by executing <span class="cli">ifconfig -a</span>.</p>
|
||||
<p>Below are a few examples of connecting to a wireless network named <i>wifitopia</i>. For these examples we are assuming your wifi network card is <tt>/dev/net/iprowifi3945/0</tt>.</p>
|
||||
<h4>Listing wireless networks:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
|
||||
<h4>Joining unsecured wireless network:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
|
||||
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (ascii password)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
|
||||
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (64-bit hex password)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
|
||||
<h4>Leaving a wireless network:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="auto-connect" rel="nofollow" id="auto-connect">Automatically connecting to a wireless network</a></h3>
|
||||
<p>To make your system connect to a given SSID at each boot automatically, you can specify your wireless networks and passwords in <tt>/boot/common/settings/network/wireless_networks</tt> with the following format:</p>
|
||||
<pre>network wifitopia {
|
||||
password mypassword
|
||||
}</pre>
|
||||
<p>If you don't create this configuration file, the system will connect to the first unencrypted network it finds.</p>
|
||||
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP notes</strong></a></p>
|
||||
<ul>
|
||||
<li>64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex digits</li>
|
||||
<li>128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex digits</li>
|
||||
<li>hexadecimal digits = characters 0-9 and A through F (prepended with "0x" in <tt>ifconfig</tt>)</li>
|
||||
</ul>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="wpa" rel="nofollow" id="wpa">Šifrovanie WPA</a></h3>
|
||||
<p><p>At the moment there is no WPA encryption available in Haiku, though there have been <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">some efforts</a> bringing it significantly closer.</p></p>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
|
||||
<p>To install the firmware for Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you need to run</p>
|
||||
<pre class="terminal">install-wifi-firmwares.sh
|
||||
</pre>
|
||||
<p>The Intel ipw2100 and iprowifi22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.</p>
|
||||
<p>People building their own Haiku image can modify their <span class="cli">build/jam/UserBuildConfig</span> accordingly. Details for that and general updates on the wifi topic are found at the <a href="http://www.haiku-os.org/guides/wifi">online version of this document</a>.</p>
|
||||
<p>If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">shell script</a>, which will create a zip file for you to extract to Haiku's <tt>/boot</tt>. After that you'll have all files needed by install-wifi-firmwares.sh.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_sk.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,180 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* deejam
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Buggrapportering</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Användarhandbok</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/sv_SE.png" alt="" /> Svenska</li>
|
||||
<li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_sv_SE.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Översättningen av denna sida är inte komplett. Delar av innehållet kommer därför att visas på engelska.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
|
||||
<a href="#report">Creating a bug report</a><br />
|
||||
<a href="#app">Application bugs</a><br />
|
||||
<a href="#server">Server bugs</a><br />
|
||||
<a href="#kernel">Kernel bugs</a><br />
|
||||
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
|
||||
<a href="#syslog">Syslog</a><br />
|
||||
<a href="#onscreen">On screen debug output</a><br />
|
||||
<a href="#hardware">Hardware/Driver bugs</a><br />
|
||||
<a href="#next">What's next?</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>Buggrapportering</h1>
|
||||
|
||||
<p>Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.</p>
|
||||
<p>För att behålla vårt bugghanteringssystem effektivt är det viktigt att följa vår <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">etikett för buggrapportering</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Skapa ett Trac-konto</a></h2>
|
||||
<p>To file a ticket, you need to have an account at <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku's Bugtracker</a>.<br />
|
||||
When creating a new account, be certain to <b>provide your email address</b> as it is necessary to obtain basic ticket modification privileges. Be sure to <b>check your spam folder</b> shortly afterwards, as the all important verification mail often ends up there.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Skapa en buggrapport</a></h2>
|
||||
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">search</a> function for this.<br />
|
||||
After you have established that it's a unique bug, make your information as accurate as possible:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
|
||||
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Programbuggar</a></h2>
|
||||
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Serverbuggar</a></h2>
|
||||
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
|
||||
Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (<span class="cli">bt</span> command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Buggar i kärnan</a></h2>
|
||||
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<ul>
|
||||
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
|
||||
<li><p>The system reboots spontaneously.</p></li>
|
||||
<li><p>The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards). Wait at least a minute to see, if anything happens.</p></li>
|
||||
<li><p>The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).</p></li>
|
||||
</ul>
|
||||
<p>Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could blacklist the responsible Wifi driver from your Haiku installation (see <a href="../../../userguide/en/bootloader.html">Boot Loader</a>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Shows the handled and unhandled hardware interrupts.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (aka continue)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
|
||||
</table>
|
||||
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
|
||||
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Systemloggen</a></h3>
|
||||
<p><b>This is the preferred method for gaining information from a non-booting system.</b><br />
|
||||
The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file <span class="path">/boot/system/var/log/syslog</span>. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).</p>
|
||||
<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog persistent. If the option <span class="menu">Save syslog from previous session during boot</span> is activated in the boot loader options (as it is by default), you'll find the syslog of your last session as <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
If you're not able to boot to get to the previous_syslog, you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
|
||||
In the boot loader's <span class="menu">Debug menu</span> you should find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. Note: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">On screen debug output</a></h3>
|
||||
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../../userguide/sv_SE/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Hårdvara/drivrutinsbuggar</a></h2>
|
||||
<p>When dealing with a hardware/driver related bug, you should attach the following information as text files:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>A detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Lists all used drivers.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Only available within <i>Kernel Debugging Land</i> (see above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>The first four commands are entered into Terminal. Add a <span class="cli"> > output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">Vad händer sen?</a></h2>
|
||||
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
|
||||
non-descriptive comments.</p>
|
||||
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
|
||||
as 'fixed'.</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_sv_SE.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,158 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2010-2011, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* deejam
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta http-equiv="Content-Style-Type" content="text/css" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Wifi</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Användarhandbok</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/sv_SE.png" alt="" /> Svenska</li>
|
||||
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
|
||||
<span>
|
||||
<a href="../welcome_sv_SE.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
|
||||
<h2>Wifi i Haiku</h2>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="hardware" rel="nofollow" id="hardware">Hårdvara som förväntas fungera</a></h3>
|
||||
<p>Haiku har inbyggt stöd för alla trådlösa enheter som finns i FreeBSD 8. PCMCIA, CardBus, ExpressCard, USB eller ISA-baserade kort stöds inte. Endast PCI, miniPCI, PCI-Express, miniPCI-Express och PCI-X skall fungera.<br />Detta inkluderar:</p>
|
||||
<ul>
|
||||
<li><p><i>aironetwifi</i> stöder åtminstone<br />
|
||||
Cisco Aironet 350 Series<br />
|
||||
Aironet PCI4500<br />
|
||||
Aironet PCI4800<br />
|
||||
</p></li>
|
||||
<li><p><i>atheroswifi</i> stöder nästan alla tillgängliga chipset (dock inte AR9285)</p></li>
|
||||
<li><p><i>broadcom43xx</i> stöder<br />
|
||||
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 och BCM4318
|
||||
</p></li>
|
||||
<li><p><i>ipw2100</i> stöder Intel Pro Wireless 2100</p></li>
|
||||
<li><p><i>iprowifi2200</i> stöder Intel Pro Wireless<br />
|
||||
2200BG<br />
|
||||
2225BG<br />
|
||||
2915ABG
|
||||
</p></li>
|
||||
<li><p><i>iprowifi3945</i> stöder Intel Pro Wireless 3945</p></li>
|
||||
<li><p><i>iprowifi4965</i> stöder Intel Pro Wireless 4965</p></li>
|
||||
<li><p><i>marvell88w8335</i> stöder<br />
|
||||
Marvell Libertas 88W8310<br />
|
||||
Marvell Libertas 88W8335
|
||||
</p></li>
|
||||
<li><p><i>marvell88w8363</i> stöder 88W8363</p></li>
|
||||
<li><p><i>ralinkwifi</i> stöder<br />
|
||||
RT2560<br />
|
||||
RT2561S<br />
|
||||
RT2561<br />
|
||||
RT2661
|
||||
</p></li>
|
||||
<li><p>ralink2860 stöder Ralink RT2860</p></li>
|
||||
<li><p><i>wavelanwifi</i> stöder åtminstone<br />
|
||||
3Com Airconnect<br />
|
||||
GLPRISM2 WaveLAN<br />
|
||||
Intersil Prism3<br />
|
||||
Intersil Prism2.5<br />
|
||||
Linksys WDT11<br />
|
||||
Netgear MA301<br />
|
||||
PRISM2STA WaveLAN<br />
|
||||
Siemens SpeedStream<br />
|
||||
SMC 2602W<br />
|
||||
Us Robotics 2415<br />
|
||||
Addtron AWA-100 PCI
|
||||
</p></li>
|
||||
</ul>
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="connect" rel="nofollow" id="connect">Ansluta till trådlösa nätverk</a></h3>
|
||||
<p>Haiku har - utöver okrypterade nätverk - preliminärt stöd för att ansluta till trådlösa nätverk med <a href="#wep-notes" rel="nofollow">WEP kryptering</a>. WEP är en tidig krypteringsmetod och därmed inte den säkraste.</p>
|
||||
<p>Du kan se tillgängliga nätverk, ansluta och koppla ner med kommandot <span class="cli">ifconfig</span> via Terminalen:</p>
|
||||
<pre class="terminal">ifconfig [sökväg_till_wifi_enhet] [list|join|leave] (nyckel)</pre>
|
||||
<p>Du kan se din <tt>sökväg_till_wifi_enhet</tt> i inställningar för <span class="app">Nätverk</span>, eller genom att köra <span class="cli">ifconfig -a</span>.</p>
|
||||
<p>Nedan finns några exempel för hur man ansluter till ett trådlöst nätverk med namnet <i>wifitopia</i>. För dessa exempel antar vi att ditt trådlösa nätverkskort är <tt>/dev/net/iprowifi3945/0</tt>.</p>
|
||||
<h4>Lista trådlösa nätverk:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
|
||||
<h4>Ansluta till ett okrypterat trådlöst nätverk:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
|
||||
<h4>Ansluta till ett <a href="#wep-notes">WEP krypterat</a> trådlöst nätverk: (med ett ascii lösenord)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mitt_lösenord</pre>
|
||||
<h4>Ansluta till ett <a href="#wep-notes">WEP krypterat</a> trådlöst nätverk: (64-bitars hexadecimalt lösenord)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
|
||||
<h4>Koppla ifrån ett trådlöst nätverk:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="auto-connect" rel="nofollow" id="auto-connect">Ansluta automatiskt till ett trådlöst nätverk</a></h3>
|
||||
<p>För att ansluta till ett nätverk vid varje uppstart kan du specifiera namnet på ditt trådlösa nätverk och lösenord i <tt>/boot/common/settings/network/wireless_networks</tt> med följande format:</p>
|
||||
<pre>network wifitopia {
|
||||
password mitt_lösenord
|
||||
}</pre>
|
||||
<p>Om du inte skapar denna konfigurationsfil så kommer Haiku att ansluta till det första okrypterade nätverket som hittas.</p>
|
||||
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP kommentarer</strong></a></p>
|
||||
<ul>
|
||||
<li>64-bitars WEP använder en 40-bitars nyckel, vilket betyder 5 bokstäver eller 10 hexadecimala siffror.</li>
|
||||
<li>128-bitars WEP använder en 104-bitars nyckel, vilket betyder 13 bokstäver eller 26 hexadecimala siffror.</li>
|
||||
<li>hexadecimala siffror = siffrorna 0-9 samt A till och med F (med "0x" i början)</li>
|
||||
</ul>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="wpa" rel="nofollow" id="wpa">WPA kryptering</a></h3>
|
||||
<p><p>För tillfället finns inte WPA kryptering tillgängligt i Haiku, även om det det har gjorts <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">ansträngningar</a> som har fört det allt närmare.</p></p>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="install_script" rel="nofollow" id="install_script">Skriptet install-wifi-firmwares.sh</a></h3>
|
||||
<p>För att installera mikroprogramvaran för Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx och Marvell 88W8335 behöver du köra skriptet:</p>
|
||||
<pre class="terminal">install-wifi-firmwares.sh
|
||||
</pre>
|
||||
<p>Intel ipw2100 och iprowifi22xx kan installeras utan en internetanslutning eftersom licensvilkoren tillåter Haiku att distribuera mikroprogramvaran. Dock krävs det att användaren godkänner licensvilkoren innan installationen. För Broadcom 43xx och Marvell 88W8335 krävs en internetanslutning eftersom respektive mikroprogramvara inte får distribueras med Haiku.</p>
|
||||
<p>Personer som bygger egna Haiku avbilder kan modifiera deras <span class="cli">build/jam/UserBuildConfig</span> därefter. Detaljer för detta och generella uppdateringar i ämnet wifi finns på <a href="http://www.haiku-os.org/guides/wifi">detta dokument på internet</a>.</p>
|
||||
<p>Om du behöver ladda ner mikroprogramvaran men saknar en fungerande internetanslutning i Haku så erbjuder internetversionen ett <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">skalskript</a> som hämtar de filer som behövs och sparar det i en komprimerad fil. FIlen skall packas upp till Haiku's <tt>/boot</tt> katalog. Efter det kommer du att ha alla filer som du behöver för att använda install-wifi-firmwares.sh skriptet.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_sv_SE.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,178 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Reporting bugs</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/uk.png" alt="" /> Українська</li>
|
||||
<li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_uk.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
|
||||
<a href="#report">Creating a bug report</a><br />
|
||||
<a href="#app">Application bugs</a><br />
|
||||
<a href="#server">Server bugs</a><br />
|
||||
<a href="#kernel">Kernel bugs</a><br />
|
||||
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
|
||||
<a href="#syslog">Syslog</a><br />
|
||||
<a href="#onscreen">On screen debug output</a><br />
|
||||
<a href="#hardware">Hardware/Driver bugs</a><br />
|
||||
<a href="#next">What's next?</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>Reporting bugs</h1>
|
||||
|
||||
<p>Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.</p>
|
||||
<p>To keep our bugtracker effective, it's essential to abide by the <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Bug Tracker Etiquette</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Getting a Trac account</a></h2>
|
||||
<p>To file a ticket, you need to have an account at <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku's Bugtracker</a>.<br />
|
||||
When creating a new account, be certain to <b>provide your email address</b> as it is necessary to obtain basic ticket modification privileges. Be sure to <b>check your spam folder</b> shortly afterwards, as the all important verification mail often ends up there.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Creating a bug report</a></h2>
|
||||
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">search</a> function for this.<br />
|
||||
After you have established that it's a unique bug, make your information as accurate as possible:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
|
||||
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Application bugs</a></h2>
|
||||
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Server bugs</a></h2>
|
||||
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
|
||||
Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (<span class="cli">bt</span> command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Kernel bugs</a></h2>
|
||||
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<ul>
|
||||
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
|
||||
<li><p>The system reboots spontaneously.</p></li>
|
||||
<li><p>The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards). Wait at least a minute to see, if anything happens.</p></li>
|
||||
<li><p>The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).</p></li>
|
||||
</ul>
|
||||
<p>Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could blacklist the responsible Wifi driver from your Haiku installation (see <a href="../../../userguide/en/bootloader.html">Boot Loader</a>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Shows the handled and unhandled hardware interrupts.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (aka continue)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
|
||||
</table>
|
||||
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
|
||||
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Syslog</a></h3>
|
||||
<p><b>This is the preferred method for gaining information from a non-booting system.</b><br />
|
||||
The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file <span class="path">/boot/system/var/log/syslog</span>. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).</p>
|
||||
<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog persistent. If the option <span class="menu">Save syslog from previous session during boot</span> is activated in the boot loader options (as it is by default), you'll find the syslog of your last session as <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
If you're not able to boot to get to the previous_syslog, you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
|
||||
In the boot loader's <span class="menu">Debug menu</span> you should find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. Note: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">On screen debug output</a></h3>
|
||||
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../../userguide/uk/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Hardware/Driver bugs</a></h2>
|
||||
<p>When dealing with a hardware/driver related bug, you should attach the following information as text files:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>A detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Lists all used drivers.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Only available within <i>Kernel Debugging Land</i> (see above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>The first four commands are entered into Terminal. Add a <span class="cli"> > output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">What's next?</a></h2>
|
||||
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
|
||||
non-descriptive comments.</p>
|
||||
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
|
||||
as 'fixed'.</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_uk.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,159 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2010-2011, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta http-equiv="Content-Style-Type" content="text/css" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Wifi</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/uk.png" alt="" /> Українська</li>
|
||||
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
|
||||
<span>
|
||||
<a href="../welcome_uk.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
|
||||
<h2>Wifi in Haiku</h2>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="hardware" rel="nofollow" id="hardware">Expected supported hardware</a></h3>
|
||||
<p>All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, PCI-Express, miniPci-Express and PCI-X are supposed to work.<br />
|
||||
This includes:
|
||||
</p>
|
||||
<ul>
|
||||
<li><p><i>aironetwifi</i> supporting at least<br />
|
||||
Cisco Aironet 350 Series<br />
|
||||
Aironet PCI4500<br />
|
||||
Aironet PCI4800<br />
|
||||
</p></li>
|
||||
<li><p><i>atheroswifi</i> supporting almost every chipset outthere (though no AR9285 chips)</p></li>
|
||||
<li><p><i>broadcom43xx</i> supporting<br />
|
||||
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318
|
||||
</p></li>
|
||||
<li><p><i>ipw2100</i> supporting Intel Pro Wireless 2100 chips</p></li>
|
||||
<li><p><i>iprowifi2200</i> supporting Intel Pro Wireless<br />
|
||||
2200BG<br />
|
||||
2225BG<br />
|
||||
2915ABG
|
||||
</p></li>
|
||||
<li><p><i>iprowifi3945</i> supporting Intel Pro Wireless 3945 chips</p></li>
|
||||
<li><p><i>iprowifi4965</i> supporting Intel Pro Wireless 4965 chips</p></li>
|
||||
<li><p><i>marvell88w8335</i> supporting<br />
|
||||
Marvell Libertas 88W8310<br />
|
||||
Marvell Libertas 88W8335
|
||||
</p></li>
|
||||
<li><p><i>marvell88w8363</i> supporting the 88W8363 chips</p></li>
|
||||
<li><p><i>ralinkwifi</i> supporting<br />
|
||||
RT2560<br />
|
||||
RT2561S<br />
|
||||
RT2561<br />
|
||||
RT2661
|
||||
</p></li>
|
||||
<li><p>ralink2860 supporting Ralink RT2860</p></li>
|
||||
<li><p><i>wavelanwifi</i> supporting at least<br />
|
||||
3Com Airconnect<br />
|
||||
GLPRISM2 WaveLAN<br />
|
||||
Intersil Prism3<br />
|
||||
Intersil Prism2.5<br />
|
||||
Linksys WDT11<br />
|
||||
Netgear MA301<br />
|
||||
PRISM2STA WaveLAN<br />
|
||||
Siemens SpeedStream<br />
|
||||
SMC 2602W<br />
|
||||
Us Robotics 2415<br />
|
||||
Addtron AWA-100 PCI
|
||||
</p></li>
|
||||
</ul>
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="connect" rel="nofollow" id="connect">Connecting to a wireless network</a></h3>
|
||||
<p>Besides of course unencrypted networks, Haiku has preliminary support for accessing wireless networks via <a href="#wep-notes" rel="nofollow">WEP encryption keys</a>. WEP is an early encryption method, although not the most secure.</p>
|
||||
<p>You can list available networks, join and leave them with the command <span class="cli">ifconfig</span> from Terminal:</p>
|
||||
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
|
||||
<p>You can find your <tt>wifi_device_path</tt> in the <span class="app">Network</span> preferences applet, or by executing <span class="cli">ifconfig -a</span>.</p>
|
||||
<p>Below are a few examples of connecting to a wireless network named <i>wifitopia</i>. For these examples we are assuming your wifi network card is <tt>/dev/net/iprowifi3945/0</tt>.</p>
|
||||
<h4>Listing wireless networks:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
|
||||
<h4>Joining unsecured wireless network:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
|
||||
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (ascii password)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
|
||||
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (64-bit hex password)</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
|
||||
<h4>Leaving a wireless network:</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="auto-connect" rel="nofollow" id="auto-connect">Automatically connecting to a wireless network</a></h3>
|
||||
<p>To make your system connect to a given SSID at each boot automatically, you can specify your wireless networks and passwords in <tt>/boot/common/settings/network/wireless_networks</tt> with the following format:</p>
|
||||
<pre>network wifitopia {
|
||||
password mypassword
|
||||
}</pre>
|
||||
<p>If you don't create this configuration file, the system will connect to the first unencrypted network it finds.</p>
|
||||
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP notes</strong></a></p>
|
||||
<ul>
|
||||
<li>64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex digits</li>
|
||||
<li>128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex digits</li>
|
||||
<li>hexadecimal digits = characters 0-9 and A through F (prepended with "0x" in <tt>ifconfig</tt>)</li>
|
||||
</ul>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="wpa" rel="nofollow" id="wpa">WPA encryption</a></h3>
|
||||
<p><p>At the moment there is no WPA encryption available in Haiku, though there have been <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">some efforts</a> bringing it significantly closer.</p></p>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
|
||||
<p>To install the firmware for Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you need to run</p>
|
||||
<pre class="terminal">install-wifi-firmwares.sh
|
||||
</pre>
|
||||
<p>The Intel ipw2100 and iprowifi22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.</p>
|
||||
<p>People building their own Haiku image can modify their <span class="cli">build/jam/UserBuildConfig</span> accordingly. Details for that and general updates on the wifi topic are found at the <a href="http://www.haiku-os.org/guides/wifi">online version of this document</a>.</p>
|
||||
<p>If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">shell script</a>, which will create a zip file for you to extract to Haiku's <tt>/boot</tt>. After that you'll have all files needed by install-wifi-firmwares.sh.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_uk.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,157 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Paco Rivière
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Benvingut al Haiku!</title>
|
||||
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Manual d'usuari</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="images/flags/ca.png" alt="" /> Català</li>
|
||||
<li><a href="welcome_fr.html"><img src="images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="welcome_de.html"><img src="images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="welcome_it.html"><img src="images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="welcome_ru.html"><img src="images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="welcome_es.html"><img src="images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="welcome_sv_SE.html"><img src="images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="welcome_hu.html"><img src="images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">La traducció d'aquesta pàgina encara no està acabada. Fins que ho sigui, algunes part correspondrà a la versió anglesa.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Índex</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">Welcome to Haiku!</a><br />
|
||||
<a href="#bugreport">Beware of Bugs</a><br />
|
||||
<a href="#system">Getting to know the system</a><br />
|
||||
<a href="#software">Installing new software</a><br />
|
||||
<a href="#wifi">Wifi in Haiku</a><br />
|
||||
<a href="#api">Getting to know the API</a><br />
|
||||
<a href="#contact">Getting in contact</a>
|
||||
</td></tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Benvingut al Haiku!</a></h2>
|
||||
<p>Thank you very much for checking out Haiku! This is our fourth public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a hrf="http://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Atenció amb els Errors de programació</a></h2>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.</div>
|
||||
|
||||
<p>One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
|
||||
<li><a href="ca/bugreports.html">Tips for a helpful bug report</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="system" name="system">Conegueu el sistema</a></h2>
|
||||
<p>The first release(s) of Haiku will be very much like the BeOS R5, the operating system it is reimplementing. If you never experienced it, have a look at these links:</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/ca/contents.html">Haiku User Guide</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/" class="printurl">List of BeOS/Haiku websites</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">Instal·leu més programari</a></h2>
|
||||
<p>Most of the available software can be downloaded and installed with the application HaikuDepot that comes with Haiku.<br />
|
||||
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/ca/applications.html">Applications</a>.</p>
|
||||
|
||||
<p>Besides using HaikuDepot, popular software repositories are:</p>
|
||||
<ul>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - maintains patches for ported software</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - hosts native BeOS and Haiku open source software projects in a github</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="wifi">El wifi al Haiku</a></h2>
|
||||
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/ca/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="api" name="api">Coneixeu l'API</a></h2>
|
||||
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
|
||||
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
|
||||
|
||||
<p>There are some resources that should help you getting started:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Development FAQ</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">Source Browser</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">The Be Book</a></li>
|
||||
<li><a href="http://api.haiku-os.org" class="printurl">The Haiku Book</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be Newsletter Archive</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Com contactar</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">Forums</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Overview of all mailing lists</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,157 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Matthias
|
||||
* Humdinger
|
||||
* taos
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Willkommen zu Haiku!</title>
|
||||
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User Guide</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="images/flags/de.png" alt="" /> Deutsch</li>
|
||||
<li><a href="welcome_fr.html"><img src="images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="welcome_it.html"><img src="images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="welcome_ru.html"><img src="images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="welcome_es.html"><img src="images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="welcome_sv_SE.html"><img src="images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="welcome_hu.html"><img src="images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">Willkommen zu Haiku!</a><br />
|
||||
<a href="#bugreport">Achtung, Bugs!</a><br />
|
||||
<a href="#system">Das System kennenlernen</a><br />
|
||||
<a href="#software">Software installieren</a><br />
|
||||
<a href="#wifi">WLAN in Haiku</a><br />
|
||||
<a href="#api">Die API kennenlernen</a><br />
|
||||
<a href="#contact">Kontakte knüpfen</a>
|
||||
</td></tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Willkommen zu Haiku!</a></h2>
|
||||
<p>Danke, für das Interesse an Haiku! Wir hoffen, dass wir durch die vierte öffentliche Version neue Entwickler für unser Projekt begeistern können und Anwendern die Möglichkeit geben, Haiku kennenzulernen. Natürlich ist diese <i>Alpha Version</i> noch nicht vollständig oder gar fehlerfrei, und sie erfüllt auch noch nicht die Ziele, die wir uns selbst gesteckt haben. Sie zeigt jedoch warum wir uns in diesem Projekt so engagieren und es ermöglicht anderen, das große Potential von Haiku zu erkunden.</p>
|
||||
<p>Auf der Projektseite <a hrf="http://www.haiku-os.org">Haiku-os.org</a> finden sich immer die neuesten Ankündigungen und Entwicklungen.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Achtung, Bugs!</a></h2>
|
||||
<p>Wir haben uns sehr bemüht eventuell schwerwiegende Fehler zu beseitigen. Da es sich aber trotz allem um eine Alpha-Version handelt, kann man davon ausgehen, dass noch genügend unentdeckte Fehler vorhanden sind.</p>
|
||||
<div class="box-warning">Diese Alpha-Version sollte nicht für wirklich kritische Aufgabe verwendet werden! Obwohl unwahrscheinlich, kann Datenverlust nicht ausgeschlossen werden!</div>
|
||||
|
||||
<p>Einer der Hauptgründe für diese Alpha-Version ist, das System möglichst vielen Leuten zum Testen anbieten zu können. Nur so ist es möglich, alle Fehler zu finden und Verbesserungsvorschläge zu erhalten. Deshalb sollte nicht gezögert werden, Fehler auch im Bug Tracker zu melden (nachdem man dessen Suchfunktion benutzt hat, um Doppeleinträge zu vermeiden).</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
|
||||
<li><a href="de/bugreports.html">Tipps für einen sinnvollen Fehler-Report</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="system" name="system">Das System kennenlernen</a></h2>
|
||||
<p>Zumindest zu Beginn wird sich Haiku sehr eng an sein Vorbild BeOS R5 halten. Insbesondere wer mit diesem Betriebssystem keine Erfahrungen sammeln durfte, seien diese Links empfohlen:</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/de/contents.html">Haiku User Guide</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/" class="printurl">BeOS/Haiku Webseiten</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">Software installieren</a></h2>
|
||||
<p>Ein Großteil der vorhandenen Software kann mit der mit Haiku kommenden HaikuDepot Anwendung heruntergeladen und installiert werden.<br />
|
||||
Da Haiku sowohl binärkompatibel als auch code-kompatibel mit BeOS ist, laufen viele BeOS-Anwendungen auch direkt in Haiku. Die meisten von ihnen wurden für Haiku passend neu gepackt oder funktionieren auch ohne Änderungen. Weitere Informationen zur Installation neuer Anwendungen finden sich im Kapitel <a href="../userguide/de/applications.html">Anwendungen</a> im Haiku User Guide.</p>
|
||||
|
||||
<p>Neben HaikuDepot existieren auch noch andere Software-Archive:</p>
|
||||
<ul>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - hier werden Patche für portierte Software gepflegt</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - ein GitHub für opensource Programme, die speziell für BeOS oder Haiku geschrieben wurden.</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="wifi">WLAN in Haiku</a></h2>
|
||||
<p>Haiku unterstützt neben unverschlüsselten Funknetzwerken auch mittels WPA/WPA2 und WEP gesicherte Verbindungen. Wegen verschiedener Lizenzbedingungen der unterschiedlichen Hardware-Hersteller, ist gegebenenfalls eine manuelle Installation von Firmware nötig. Mehr Information zu unterstützter Hardware, Installieren von Firmware und wie man eine WLAN-Verbindung herstellt, finden sich im <a href="../userguide/de/workshop-wlan.html">Workshop: Funknetzwerke nutzen</a> des Haiku User Guides.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="api" name="api">Die API kennenlernen</a></h2>
|
||||
<p>Da Haiku eine Reimplementierung des BeOS R5 ist, sind die API die gleichen (mit einigen Erweiterungen). Deshalb ist die Dokumentation im Be Book immer noch eine hilfreiche Quelle. Dankenswerterweise hat die Firma ACCESS, die alle Rechte von Be Inc. übernommen hat, einer Veröffentlichung des Be Book zugestimmt.<br />
|
||||
Abweichungen von der BeOS API und Haiku-spezifische Erweiterungen werden im Haiku Book gesammelt.</p>
|
||||
|
||||
<p>Diese Informationen sollten einen guten Einstieg in die Materie vermitteln:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Entwickler FAQ</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">Sourcecode-Browser</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">Be Book</a></li>
|
||||
<li><a href="http://api.haiku-os.org" class="printurl">Haiku Book</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be Newsletter Archiv</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Kontakte knüpfen</a></h2>
|
||||
<p>Um sich mit anderen Entwicklern und Anwendern auszutauschen, kann man an Diskussionen im IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a>), in den Foren oder auf Mailinglisten teilnehmen. Wie üblich, wenn sich mehrere Menschen unterhalten, sollte eine gewisse <a href="http://www.haiku-os.org/community/ml/etiquette">Etikette</a> eingehalten werden.</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC Kanäle</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">Foren</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Mailingliste für allgemeine Haiku Themen</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Mailingliste für Programmierer von Haiku selbst</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailingliste für Programmierer von Software für Haiku</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Alle Mailinglisten</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,153 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Welcome to Haiku!</title>
|
||||
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
</div>
|
||||
|
||||
<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="welcome_fr.html"><img src="images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="welcome_de.html"><img src="images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="welcome_it.html"><img src="images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="welcome_ru.html"><img src="images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="welcome_es.html"><img src="images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="welcome_sv_SE.html"><img src="images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="welcome_hu.html"><img src="images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">Welcome to Haiku!</a><br />
|
||||
<a href="#bugreport">Beware of Bugs</a><br />
|
||||
<a href="#system">Getting to know the system</a><br />
|
||||
<a href="#software">Installing new software</a><br />
|
||||
<a href="#wifi">Wifi in Haiku</a><br />
|
||||
<a href="#api">Getting to know the API</a><br />
|
||||
<a href="#contact">Getting in contact</a>
|
||||
</td></tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Welcome to Haiku!</a></h2>
|
||||
<p>Thank you very much for checking out Haiku! This is our fourth public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a hrf="http://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Beware of Bugs</a></h2>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.</div>
|
||||
|
||||
<p>One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
|
||||
<li><a href="en/bugreports.html">Tips for a helpful bug report</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="system" name="system">Getting to know the system</a></h2>
|
||||
<p>The first release(s) of Haiku will be very much like the BeOS R5, the operating system it is reimplementing. If you never experienced it, have a look at these links:</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/en/contents.html">Haiku User Guide</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/" class="printurl">List of BeOS/Haiku websites</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">Installing more software</a></h2>
|
||||
<p>Most of the available software can be downloaded and installed with the application HaikuDepot that comes with Haiku.<br />
|
||||
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/en/applications.html">Applications</a>.</p>
|
||||
|
||||
<p>Besides using HaikuDepot, popular software repositories are:</p>
|
||||
<ul>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - maintains patches for ported software</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - hosts native BeOS and Haiku open source software projects in a github</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="wifi">Wifi in Haiku</a></h2>
|
||||
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/en/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="api" name="api">Getting to know the API</a></h2>
|
||||
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
|
||||
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
|
||||
|
||||
<p>There are some resources that should help you getting started:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Development FAQ</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">Source Browser</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">The Be Book</a></li>
|
||||
<li><a href="http://api.haiku-os.org" class="printurl">The Haiku Book</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be Newsletter Archive</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Getting in contact</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">Forums</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Overview of all mailing lists</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,158 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Oscar Carballal
|
||||
* miguel~1.mx
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>¡Bienvenido a Haiku!</title>
|
||||
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Guía del usuario</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="images/flags/es.png" alt="" /> Español</li>
|
||||
<li><a href="welcome_fr.html"><img src="images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="welcome_de.html"><img src="images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="welcome_it.html"><img src="images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="welcome_ru.html"><img src="images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="welcome_sv_SE.html"><img src="images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="welcome_hu.html"><img src="images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">La traducción de esta página no está completa aún. Hasta que esté, las partes sin terminar vienen en su inglés original.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">Welcome to Haiku!</a><br />
|
||||
<a href="#bugreport">Beware of Bugs</a><br />
|
||||
<a href="#system">Getting to know the system</a><br />
|
||||
<a href="#software">Installing new software</a><br />
|
||||
<a href="#wifi">Wifi in Haiku</a><br />
|
||||
<a href="#api">Getting to know the API</a><br />
|
||||
<a href="#contact">Getting in contact</a>
|
||||
</td></tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">¡Bienvenido a Haiku!</a></h2>
|
||||
<p>Thank you very much for checking out Haiku! This is our fourth public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a hrf="http://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Cuidado con los fallos</a></h2>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
|
||||
<div class="box-warning">No se recomienda el uso de versiones alfa como sistemas de producción. Su información bien podría alterarse, estropearse o destruirse en algún momento.</div>
|
||||
|
||||
<p>Una de las razones principales para liberar una versión alpha es atraer a mucha gente para probar el sistema y descubrir fallos o darnos sugerencias para futuras mejoras. Por favor, archive los fallos y mejoras en nuestro bug tracker después de utilizar su sistema de búsqueda para evitar duplicados.</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Rastreador de fallos de Haiku</a></li>
|
||||
<li><a href="es/bugreports.html">Consejos para un buen informe de error</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="system" name="system">Habituándose al sistema</a></h2>
|
||||
<p>Las primeras versiones de Haiku serán muy similares a BeOS R5, el sistema operativo que está recreando. Si nunca lo ha probado, puede mirar estos enlaces:</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/es/contents.html">Guía de usuario de Haiku</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/" class="printurl">Lista de sitios web acerca de BeOS/Haiku</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">Instalar más software</a></h2>
|
||||
<p>Most of the available software can be downloaded and installed with the application HaikuDepot that comes with Haiku.<br />
|
||||
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/es/applications.html">Applications</a>.</p>
|
||||
|
||||
<p>Besides using HaikuDepot, popular software repositories are:</p>
|
||||
<ul>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - maintains patches for ported software</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - hosts native BeOS and Haiku open source software projects in a github</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="wifi">Wifi en Haiku</a></h2>
|
||||
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/es/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="api" name="api">Habituándose a la API</a></h2>
|
||||
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
|
||||
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
|
||||
|
||||
<p>There are some resources that should help you getting started:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">FAQ (preguntas frecuentes) de desarrollo</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">Navegador de código fuente</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">El BeBook (Descripción de la API de Be)</a></li>
|
||||
<li><a href="http://api.haiku-os.org" class="printurl">The Haiku Book</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">El archivo de la revista BeNewsletter</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Ponerse en contacto</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">Canales IRC</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">Foros</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Lista de correo general</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Lista de correo de desarrollo de Haiku</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Lista de correo para programadores de aplicaciones de terceros</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Panorama de todas las listas de correo</a>.</li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,156 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Karvjorm
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Tervetuloa Haikuun!</title>
|
||||
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Käyttäjäopas</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="images/flags/fi.png" alt="" /> Suomi</li>
|
||||
<li><a href="welcome_fr.html"><img src="images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="welcome_de.html"><img src="images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="welcome_it.html"><img src="images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="welcome_ru.html"><img src="images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="welcome_es.html"><img src="images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="welcome_sv_SE.html"><img src="images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="welcome_hu.html"><img src="images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Tämän sivun kotoistaminen ei ole vielä täydellinen. Siihen asti keskeneräiset osat käyttävät englanninkielistä alkuperäistekstiä.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Hakemisto</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">Tervetuloa Haikuun!</a><br />
|
||||
<a href="#bugreport">Varo ohjelmistovikoja</a><br />
|
||||
<a href="#system">Järjestelmään tutustuminen</a><br />
|
||||
<a href="#software">Lisäohjelmistojen asentaminen</a><br />
|
||||
<a href="#wifi">Wifi-verkot Haikussa</a><br />
|
||||
<a href="#api">Tutustuminen sovellusohjelmointirajapintaan</a><br />
|
||||
<a href="#contact">Yhteydenotot</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Tervetuloa Haikuun!</a></h2>
|
||||
<p>Kiitoksia oikein paljon, että latasit Haiku-käyttöjärjestelmän! Tämä on neljäs julkinen julkaisumme. Toivomme houkuttelevamme uusia kehittäjiä hankkeeseemme ja antavamme tuleville käyttäjillä mahdollisuuden tutustua Haikuun. Tiedämme, että tämä <i>alfa-julkaisu</i> ei vielä täytä niitä odotuksia, jotka olemme asettaneet itsellemme ja se ei tarjoa kaikkia ominaisuuksia ja lopullisen R1-version täysiä käyttäjäkokemuksia. Toivomme kuitenkin, että tämä julkaisu antaa sinulle mahdollisuuden löytää Haikun suuren potentiaalin ja että jaat meidän innostuksemme.</p>
|
||||
<p>Vieraile projektimme kotisivulla <a hrf="http://www.haiku-os.org">Haiku-os.org</a> saadaksesi viimeisimmät uutiset ja tiedonannot.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Varo ohjelmistovikoja</a></h2>
|
||||
<p>Olemme työskennelleet kovasti korjataksemme potentiaalisesti kriittiset viat, mutta kuitenkin tämä on ohjelmiston alfa-julkaisu, ja siinä on jäljellä runsaasti löytämättömiä vikoja</p>
|
||||
<div class="box-warning">Emme suosittele käyttämään alfa-versioita tuotantojärjestelmänä. Tietosi voivat aivan hyvin muuttua, vääristyä tai suorastaan tuhoutua.</div>
|
||||
|
||||
<p>Yksi pääsyy alfa-versioiden julkaisemiseen on houkutella lisää ihmisiä järjestelmän testaamiseen ja vikojen havaitsemiseen tai tarjota ehdotuksia tulevista laajennuksista. Ilmoita vioista ja laajennuksista vikaseuraajajärjestelmässämme sen jälkeen kun olet käyttänyt sen etsintätoimintoa kaksoiskappaleilmoitusten estämiseksi.</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku-vikaseuraaja</a></li>
|
||||
<li><a href="fi/bugreports.html">Vihjeitä hyödyllisiä vikailmoituksia varten</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="system" name="system">Järjestelmään tutustuminen</a></h2>
|
||||
<p>Haikun ensimmäiset julkaisut ovat paljolti kuin BeOS R5, käyttöjärjestelmän uudelleentoteutus. Jos et ole koskaan kokenut sitä, vilkaise näitä linkkejä:</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/fi/contents.html">Haiku-käyttäjäopas</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/" class="printurl">BeOS/Haiku -webbisivustojen luettelo</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">Lisäohjelmistojen asentaminen</a></h2>
|
||||
<p>Useimmat saatavilla olevat ohjelmistot voidaan ladata ja asentaa HaikuDepot-sovelluksella, joka tulee Haikun mukana.<br />
|
||||
Binaari- ja lähdekoodiyhteensopivuuden vuoksi monia BeOS-sovelluksia voidaan suorittaa Haikussa. Monet niistä on pakattu uudelleen Haikua varten tai ne suoritetaan yhä muokkaamattomina. Löydät lisätietoja uusien ohjelmien asentamisesta käyttöoppaan kappaleesta <a href="../userguide/fi/applications.html">Sovellukset</a>.</p>
|
||||
|
||||
<p>HaikuDepot:in lisäksi suosittuja ohjelmistovarastoja ovat:</p>
|
||||
<ul>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - ylläpitää siirretyn ohjelmiston korjauksia</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - ylläpitää aitoja BeOS- ja Haiku open source -ohjelmistohankkeita githubissa</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="wifi">Wifi-verkot Haikussa</a></h2>
|
||||
<p>Haiku tukee langattomia verkkoja, jotka on WPA-/WPA2- tai WEP-salattuja ja tietysti avoimia, salaamattomia yhteyksiä. Eri toimittajien useista erilaisista lisenssointikäytännöistä johtuen käyttäjiltä vaaditaan mikro-ohjelmistokoodin manuaalista asentamista. Löydät lisätietoja tuetuista laitteista, mikro-ohjelmistoasennuksista ja kuinka liitytään langattomaan verkkoon Haikun Käyttäjäopasteesta <a href="../userguide/fi/workshop-wlan.html">Työpaja: Langaton verkko</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="api" name="api">Tutustuminen sovellusohjelmointirajapintaan</a></h2>
|
||||
<p>Koska Haiku on uudelleentoteutus, sovellusohjelmointirajapinta (API) on yhä sama kuin BeOS R5 (joillakin lisäyksillä). Siksi dokumentaation Be-kirjassa on yhä kelvollinen resurssi. Kiitos ACCESS-yhtiön, joka omistaa entisen Be Inc. -yhtiön immateriaalioikeudet, meidän on lupa tarjota Be-kirjan kopio.<br />
|
||||
Poikkeavuudet BeOS API:sta ja Haiku-kohtaiset lisäykset on kerätty Haiku-kirjaan.</p>
|
||||
|
||||
<p>Joitakin lisäresursseja, joiden pitäisi auttaa aloittamisessa:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Kehitys-UKK</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">Lähdekoodiselain</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">Be-kirja</a></li>
|
||||
<li><a href="http://api.haiku-os.org" class="printurl">Haiku-kirja</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be-uutiskirjearkisto</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Yhteydenotot</a></h2>
|
||||
<p>Hakeudu yhteyteen muiden kehittäjien ja käyttäjien kanssa ja liity keskusteluihin IRC-kanavalla (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a>), foorumeillamme tai sähköpostilistoilla. Kun monet eri ihmiset tulevat yhteen, on perustettu sääntöjä viestinnän pitämiseksi tehokkaana. Kunnioita meidän <a href="http://www.haiku-os.org/community/ml/etiquette">Sähköpostilistaetiketti</a>ämme.</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC-kanavat</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">Foorumit</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Yleinen sähköpostilista</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Haikua itseä koskeva kehityssähköpostilista</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Kolmannen osapuolen sovellusohjelmoijien sähköpostilista</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Kaikkien sähköpostilistojen yleiskatsaus</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,161 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Vincent Duvert
|
||||
* Loïc
|
||||
* Humdinger
|
||||
* Wabouz
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Bienvenue sur Haiku !</title>
|
||||
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Guide de l’utilisateur</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="images/flags/fr.png" alt="" /> Français</li>
|
||||
<li><a href="welcome_de.html"><img src="images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="welcome_it.html"><img src="images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="welcome_ru.html"><img src="images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="welcome_es.html"><img src="images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="welcome_sv_SE.html"><img src="images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="welcome_hu.html"><img src="images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Cette page n'est pas encore entièrement traduite. Les parties non encore traduites seront en anglais.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">Bienvenue sur Haiku !</a><br />
|
||||
<a href="#bugreport">Attention aux bogues</a><br />
|
||||
<a href="#system">Comment se familiariser avec le système</a><br />
|
||||
<a href="#software">Installer plus de logiciels</a><br />
|
||||
<a href="#wifi">Le wifi dans Haiku</a><br />
|
||||
<a href="#api">Apprendre à connaître l'API</a><br />
|
||||
<a href="#contact">Rester en contact</a>
|
||||
</td></tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Bienvenue sur Haiku !</a></h2>
|
||||
<p>Merci beaucoup d’essayer Haiku ! Voici notre quatrième version publique. Nous espérons encourager de nouveaux développeurs à nous rejoindre et donner aux futurs utilisateurs la possibilité d’essayer Haiku. Nous sommes conscients que cette <i>version alpha</i> ne remplit pas tous les objectifs que nous nous sommes fixés et ne fournit pas toutes les fonctionnalités et l’expérience utilisateur attendues pour la version R1 finale. Néanmoins, nous espérons que cette version (même inachevée) vous permettra de découvrir le potentiel de Haiku et de partager notre enthousiasme.</p>
|
||||
<p>Visitez le site de notre projet <a hrf="http://www.haiku-os.org">Haiku-os.org</a> pour rester informé des dernières évolutions.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Attention aux bogues</a></h2>
|
||||
<p>Nous avons travaillé dur pour résoudre les bogues critiques du système. Néanmoins, Haiku n'étant qu'au stade d'une version alpha, beaucoup n'ont pas encore été découverts.</p>
|
||||
<div class="box-warning">Nous déconseillons l'utilisation des versions Alpha en tant que système pour travailler sur des fichiers/projets/travaux personnels. Les données que vous manipulez pourraient être altérées, corrompues ou tout simplement détruites.</div>
|
||||
|
||||
<p>La sortie d'une version alpha a pour objectif de faire découvrir et tester le système par d'avantage de personnes, afin de trouver les bogues présents et d'obtenir des suggestions d'améliorations futures. Veuillez rapporter d'éventuels bogues et suggestions sur notre traqueur de bogues après avoir utilisé sa fonction de recherche pour éviter les doublons.</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Traqueur de bogues de Haiku</a> (en anglais)</li>
|
||||
<li><a href="fr/bugreports.html">Astuces pour un rapport de bogue utile</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="system" name="system">Comment se familiariser avec le système</a></h2>
|
||||
<p>Les premières versions de Haiku auront une apparence et des fonctionnalités proches de celles de BeOS R5, le système d'exploitation qu'il tente de ré-implémenter. Si vous ne l'avez jamais essayé, jetez un œil à ces liens :</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/fr/contents.html">Guide utilisateur d'Haiku</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/" class="printurl">Liste de sites web consacrés à BeOS/Haiku</a> (en anglais)</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">Installer plus de logiciels</a></h2>
|
||||
<p>La plupart des logiciels disponible peuvent être téléchargés et installés avec l'application HaikuDepot qui est fournie avec Haiku.<br /> Du fait de sa la compatibilité des binaires et des sources, la plupart des applications BeOS tournent sur Haiku. Beaucoup d'entre elles ont été ré-empaquetées pour Haiku ou tournent parfaitement, même sans modification. Vous trouverez plus d'informations sur l'installation de nouveaux programmes dans le guide de l'utilisateur, au chapitre <a href="../userguide/fr/applications.html">Applications</a>.</p>
|
||||
|
||||
<p>Voici quelques sites populaires référençant un certain nombre de logiciels populaires :</p>
|
||||
<ul>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - maintient les correctifs pour les logiciels supportés.</li>
|
||||
<li><a href="http://dev.osdrawer.net/" class="printurl">OsDrawer</a> - héberge des projets de logiciels open source natifs pour BeOS et Haiku</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="wifi">Le wifi dans Haiku</a></h2>
|
||||
<p>Haiku gère les réseaux sans fil cryptés en WPA/WPA2 ou WEP et bien sûr les réseaux ouverts non chiffrés. En raison de plusieurs politiques d'octroi de licences de différents fabricants de matériels, une étape manuelle peut-être nécessaire pour installer le firmware. Vous trouverez plus d'informations sur le matériel pris en charge, l'installation du firmware et comment adhérer à un réseau sans fil dans le Guide de l'utilisateur de Haiku <a href="../userguide/fr/workshop-wlan.html">Atelier : Réseaux sans-fils</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="api" name="api">Apprendre à connaître l'API</a></h2>
|
||||
<p>Comme Haiku est une ré-implémentation, l'API est encore la même que celle de BeOS R5 (avec quelques ajouts).
|
||||
Par conséquent, la documentation du BeBook est toujours valable. Nous remercions ACCESS, qui détient les droits de propriété de l'ancien Be Inc, de nous autoriser à fournir une copie du BeBook.<br />
|
||||
Les écarts par rapport à l'API BeOS et les ajouts spécifiques à Haiku sont collectés dans le livre Haiku.</p>
|
||||
|
||||
<p>Quelques ressources sont susceptibles de vous aider à commencer :</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">FAQ Développement</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">Explorer le code source</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">Le BeBook</a></li>
|
||||
<li><a href="http://api.haiku-os.org" class="printurl">Le Haiku Book</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">L'archive BeNewsletter</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Rester en contact</a></h2>
|
||||
<p>Entrez en contact avec les autres développeurs et utilisateurs, participez aux discussions sur IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> pour le webchat), dans nos forums ou les listes de diffusion.
|
||||
Quand beaucoup de gens différents se rencontrent, des règles doivent êtres établies pour maintenir une communication efficace. Veuillez respecter
|
||||
<a href="http://www.haiku-os.org/community/ml/etiquette">l'étiquette de notre liste de diffusion</a>.</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">Canaux IRC</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">Forums</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Liste de diffusion générale</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Liste de diffusion concernant le dévelopment de Haiku, lui même</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Liste de diffusion concernant les développeurs d'applications tiers</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl"> Panorama de toutes les listes de diffusions</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,157 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Dancsó Róbert
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Üdvözöl a Haiku!</title>
|
||||
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Használati útmutató</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="images/flags/hu.png" alt="" /> Magyar</li>
|
||||
<li><a href="welcome_fr.html"><img src="images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="welcome_de.html"><img src="images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="welcome_it.html"><img src="images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="welcome_ru.html"><img src="images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="welcome_es.html"><img src="images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="welcome_sv_SE.html"><img src="images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">Üdvözöl a Haiku!</a><br />
|
||||
<a href="#bugreport">Előfordulhatnak hibák</a><br />
|
||||
<a href="#system">A rendszer megismerése</a><br />
|
||||
<a href="#software">Új programok telepítése</a><br />
|
||||
<a href="#wifi">Wifi Haiku alatt</a><br />
|
||||
<a href="#api">A felület megismerése</a><br />
|
||||
<a href="#contact">Kapcsolat</a>
|
||||
</td></tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Üdvözöl a Haiku!</a></h2>
|
||||
<p>Köszönjük, hogy kipróbálod a Haiku legújabb hivatalos kiadását. Reméljük, hogy találunk újabb fejlesztőket és felhasználókat, akik tesztelik a szoftvert. Tisztában vagyunk azzal, hogy ez csak egy <i>alfa-verziójú</i> kiadás, ami nem teljesen életképes és nem tartalmaz minden, az R1-es verzióban várható programot és funkciót. Mindazonáltal reméljük, hogy ez a kiadás lehetőséget nyújt a Haiku megismeréséhez, és megmutatja a benne rejlő lehetőségeket.</p>
|
||||
<p>Kérjük látogass el a project oldalára (<a hrf="http://www.haiku-os.org">Haiku-os.org</a>) a legfrissebb hírek és információk miatt.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Előfordulhatnak hibák</a></h2>
|
||||
<p>Keményen dolgozunk azon, hogy minden lehetséges hibát felderítsünk, és kijavítsunk. Alfa-állapotú szoftver révén több felderítetlen hiba is adódhat.</p>
|
||||
<div class="box-warning">Nem ajánljuk, hogy produktívan használj egy alfa-állapotú szoftvert. Komoly adatveszteséggel járhat.</div>
|
||||
|
||||
<p>Azért adunk ki alfa-állapotú szoftvert, hogy minél többen teszteljék, és minél több hibára derüljön fény, illetve hogy javaslatokat kapjunk a további fejlesztéshez. Kérjük, hogy mielőtt jelentesz egy hibát, előtte próbálj rákeresni, hátha már valaki jelentette azt.</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku hibajelentő</a></li>
|
||||
<li><a href="hu/bugreports.html">Tippek a hibák jelentéséhez</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="system" name="system">A rendszer megismerése</a></h2>
|
||||
<p>A Haiku sok tekintetben hasonlít a BeOS R5-ös verziójára, ezért tekinthetjük a modern reinkarnációjának is. Ha eddig még nem találkoztál a rendszerrel, akkor ajánlom figyelmedbe a következő oldalakat:</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/hu/contents.html">Haiku felhasználói útmutató</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/" class="printurl">BeOS/Haiku oldalak</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">Új programok telepítése</a></h2>
|
||||
<p>A legtöbb program elérhető a Raktár-ból, mely a Haiku részét képezi.
|
||||
A bináris kompatibilitás miatt sok BeOS-ra készült program futtatható Haiku-n. Közülük több is újra lett csomagolva a Haiku-nak megfelelően vagy eredeti formájában is használható.
|
||||
További információk a <a href="../userguide/hu/applications.html">Programok</a> fejezetben.</p>
|
||||
|
||||
<p>A Raktáron kívül az alábbi népszerű oldalakon is találunk programokat:</p>
|
||||
<ul>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a> - PulkoMandy szoftverei</li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a> - Guest One raktár</li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org/" class="printurl">HaikuPorts</a> - portolt programok és frissítéseik</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - a BeOS és a Haiku nyílt forrású programjainak otthona</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="wifi">Wifi Haiku alatt</a></h2>
|
||||
<p>A Haiku jelenleg a WPA/WPA2 és a WEP kódolású, és természetesen a kódolatlan hálózatokat támogatja. További információt találsz a támogatott eszközökről, konfigurálásról illetve csatlakozási módokról a felhasználó útmutatóban: <a href="../userguide/hu/workshop-wlan.html">Műhely: vezeték nélküli hálózat</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="api" name="api">A felület megismerése</a></h2>
|
||||
<p>Mivel a Haiku a BeOS R5 reinkarnációja, a felhasználói felület nagyon hasonló, éppen ezért a Be könyv még mindig használható. Ezért köszönettel tartozunk az ACCESS cégnek, aki jelenleg az egykori Be Inc. jogainak a birtokosa.<br />
|
||||
A Haiku könyv a Be köny átirata a Haiku-specifikus információkkal.</p>
|
||||
|
||||
<p>Néhány hasznos oldal, ahol érdemes elindulni:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Fejlesztői GYIK</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">A forráskód böngészése</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">A Be könyv</a></li>
|
||||
<li><a href="http://api.haiku-os.org" class="printurl">A Haiku könyv</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">A Be hírlevelek archívuma</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Kapcsolat</a></h2>
|
||||
<p>Kapcsolatba léphetsz más fejlesztőkkel és felhasználókkal IRC csatornán keresztül (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a>), a fórumunkon illetve a levelezőlistáinkon. Ha sok különböző ember összejön, akkor különféle szabályokat be kell vezetni. Kérjük, olvasd el a <a href="http://www.haiku-os.org/community/ml/etiquette">levelezőlista-illemtan</a>t.</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC csatornák</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">Fórumok</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Elsődleges levelezőlista</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Fejlesztői levelezőlista</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Külső fejlesztői lista</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Az összes levelezőlista egy helyen</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,157 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* MichaelPeppers
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Benvenuto in Haiku!</title>
|
||||
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Guida dell'utente</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="images/flags/it.png" alt="" /> Italiano</li>
|
||||
<li><a href="welcome_fr.html"><img src="images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="welcome_de.html"><img src="images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="welcome_ru.html"><img src="images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="welcome_es.html"><img src="images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="welcome_sv_SE.html"><img src="images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="welcome_hu.html"><img src="images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">La traduzione di questa pagina non è stata completata. Per questo motivo le parti non tradotte sono visibili in inglese.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">Welcome to Haiku!</a><br />
|
||||
<a href="#bugreport">Beware of Bugs</a><br />
|
||||
<a href="#system">Getting to know the system</a><br />
|
||||
<a href="#software">Installing new software</a><br />
|
||||
<a href="#wifi">Wifi in Haiku</a><br />
|
||||
<a href="#api">Getting to know the API</a><br />
|
||||
<a href="#contact">Getting in contact</a>
|
||||
</td></tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Benvenuto in Haiku!</a></h2>
|
||||
<p>Thank you very much for checking out Haiku! This is our fourth public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a hrf="http://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="indice" /></a>
|
||||
<a id="bugreport" name="bugreport">Attento ai bug</a></h2>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
|
||||
<div class="box-warning">Scoraggiamo l'uso di versioni alpha come sistemi di produzione. I tuoi dati potrebbero venire alterati, danneggiati o essere addirittura cancellati.</div>
|
||||
|
||||
<p>Una delle principali ragioni per rilasciare una versione alpha è di attrarre più persone per testare il sistema e scoprire bug o per consigliare miglioramenti. Ti preghiamo di segnalarci bug e miglioramenti nel nostro bug tracker dopo aver usato il suo motore di ricerca interno per evitare duplicati.</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">il bug tracker di Haiku</a></li>
|
||||
<li><a href="it/bugreports.html">Consigli per segnalare i bug in modo utile</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="indice" /></a>
|
||||
<a id="system" name="system">Per conoscere il sistema</a></h2>
|
||||
<p>Le prime release di Haiku saranno molto simili al BeOS R5, il sistema operativo che sta re-implementando. Se non l'hai mai provato, dai un'occhiata a questi link:</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/it/contents.html">Guida dell'utente Haiku</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/" class="printurl">Lista di siti riguardanti BeOS e Haiku</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="indice" /></a>
|
||||
<a id="software" name="software">Installare altre applicazioni</a></h2>
|
||||
<p>Most of the available software can be downloaded and installed with the application HaikuDepot that comes with Haiku.<br />
|
||||
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/it/applications.html">Applications</a>.</p>
|
||||
|
||||
<p>Besides using HaikuDepot, popular software repositories are:</p>
|
||||
<ul>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - maintains patches for ported software</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - hosts native BeOS and Haiku open source software projects in a github</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="indice" /></a>
|
||||
<a id="software" name="wifi">Il Wifi in Haiku</a></h2>
|
||||
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/it/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="indice" /></a>
|
||||
<a id="api" name="api">Per conoscere l'API</a></h2>
|
||||
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
|
||||
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
|
||||
|
||||
<p>There are some resources that should help you getting started:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">FAQ degli sviluppatori</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">Browser del codice sorgente</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">Il Be Book</a></li>
|
||||
<li><a href="http://api.haiku-os.org" class="printurl">The Haiku Book</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Achivio delle newsletter della Be Inc.</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="indice" /></a>
|
||||
<a id="contact" name="contact">Entrare in contatto</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">Canali di chat</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">I forum</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Mailing list di discussione generale</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Mailing list per gli sviluppatori concernente Haiku stesso</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list per i programmatori di applicazioni di terze parti</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Lista delle varie mailing list</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,156 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* iwaim
|
||||
* Shota Fukumori
|
||||
* mt
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Haiku へようこそ！</title>
|
||||
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>ユーザーガイド</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="images/flags/jp.png" alt="" /> 日本語</li>
|
||||
<li><a href="welcome_fr.html"><img src="images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="welcome_de.html"><img src="images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="welcome_it.html"><img src="images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="welcome_ru.html"><img src="images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="welcome_es.html"><img src="images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="welcome_sv_SE.html"><img src="images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="welcome_hu.html"><img src="images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>目次</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">Haiku へようこそ!</a><br />
|
||||
<a href="#bugreport">バグに注意</a><br />
|
||||
<a href="#system">システムを把握する</a><br />
|
||||
<a href="#software">ソフトウェアを追加する</a><br />
|
||||
<a href="#wifi">Haiku での Wifi</a><br />
|
||||
<a href="#api">API を理解する</a><br />
|
||||
<a href="#contact">連絡を取り合う</a>
|
||||
</td></tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Haiku へようこそ！</a></h2>
|
||||
<p>Haiku を選んでくれてとてもうれしいよ！これは私たちの 4 番目の公式リリースです。私たちは新しい開発者をプロジェクトに迎え入れて、将来のユーザーに Haiku を選択してもらう機会を与えたいと考えています。この<i>アルファ版</i>が私たちが設定した目標を完全に満たしているものではなく、すべての機能を提供しているわけではないと理解しています。また、幅広いエンドユーザー・エクスペリエンスによって最終的な R1 バージョンの計画を立てました。しかしながら、あなたがこのリリースで Haiku の素晴らしいポテンシャルに気づき、私たちの興奮を共有してくれることを願っています。</p>
|
||||
<p>最新のニュースとお知らせは、私たちのプロジェクトのウェブサイト、<a hrf="http://www.haiku-os.org">Haiku-os.org</a> にアクセスしてください。</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">バグに注意</a></h2>
|
||||
<p>私たち開発チームはできるだけ潜在的に重大なバグを修正することに努めています。しかし、これはアルファ版であるため、まだ見つかっていないたくさんのバグが残っているかもしれません。</p>
|
||||
<div class="box-warning">私たちはアルファ版を実際の場面で使うことを望んではいません。あなたのデータは壊れたり、めちゃくちゃになったり、完全に破壊されたりするかもしれません。</div>
|
||||
|
||||
<p>私たちがアルファ版をリリースした理由の一つに、もっとたくさんの人に Haiku を触ってもらい、システムのテストとバグの発見など、Haiku の向上を目指すというのがあります。バグを見つけた場合、バグトラッカーで検索してまだ報告されていなければ (重複を防ぐために) 報告していただけると助かります。</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku バグトラッカー</a></li>
|
||||
<li><a href="jp/bugreports.html">良いバグレポートをするためのヒント</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="system" name="system">システムを把握する</a></h2>
|
||||
<p>最初の Haiku のリリースは BeOS R5 の再実装のようになる予定ですが、まだ体験していないならこれらも見ると良いでしょう:</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/jp/contents.html">Haiku ユーザーガイド</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/" class="printurl">BeOS および Haiku 関連ウェブサイト一覧</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">ソフトウェアを追加する</a></h2>
|
||||
<p>ほとんどの利用可能なソフトウェアは、Haiku に付属のアプリケーション、HaikuDepot でダウンロードおよびインストールできます。<br />ほとんどの BeOS 向けアプリケーションは Haiku でもバイナリとソースコードの互換性から動作すると思われます。その多くは Haiku 用に再パッケージされているか、修正なしに動作します。新しいアプリケーションのインストールに関する追加の情報はユーザーガイドの<a href="../userguide/jp/applications.html">アプリケーション</a>の章に見つかります。</p>
|
||||
|
||||
<p>HaikuDepot 以外の有名なソフトウェアレポジトリの一覧:</p>
|
||||
<ul>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - Haiku に移植されたソフトウェアのパッチをメンテナンスしています。</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - ネイティブ BeOS と Haiku のオープンソースソフトウェアプロジェクトを github でホストしています。</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="wifi">Haiku での Wifi</a></h2>
|
||||
<p>Haiku は、WPA / WPA2 または WEP で暗号化されているワイヤレスネットワークと、当然、オープンで暗号化されていないワイヤレスネットワークをサポートしています。異なるハードウェアベンダーの様々なライセンスポリシーのため、ファームウェアインストールプロセスのマニュアルが必要となるでしょう。サポートされたハードウェア、ファームウェアのインストール、そしてワイヤレスネットワークへの接続方法についての詳しい情報は、ユーザーガイドの<a href="../userguide/jp/workshop-wlan.html">ワークショップ: ワイヤレスネットワーク</a>で見つかるでしょう。</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="api" name="api">API を理解する</a></h2>
|
||||
<p>Haiku は再実装のため、API は BeOS R5 とまだ同じです (少しの追加があります)。そのため、Be Book にあるドキュメントはまだ有用な情報です。かつての Be Inc. の所有物の権利を持つ ACCESS に感謝します。私たちは Be Book のコピーを提供することを許可されました。<br />BeOS API から離れたところ、および Haiku 固有の追加事項は Haiku Book に集められています。</p>
|
||||
|
||||
<p>以下は、始める際に手助けになるいくつかのドキュメントです。</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">開発 FAQ</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">ソースブラウザー</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">Be Book</a></li>
|
||||
<li><a href="http://api.haiku-os.org" class="printurl">The Haiku Book</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be ニュースレター アーカイブ</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">連絡を取り合う</a></h2>
|
||||
<p>IRC (webchat 上の <a href="http://webchat.freenode.net/?channels=haiku">#haiku</a>) や私たちのフォーラム、メーリングリストでほかの開発者やユーザーと連絡や議論ができます。たくさんの人々が一緒に活動をするには、ルールにしっかりと準拠して行動をする必要があります。<a href="http://www.haiku-os.org/community/ml/etiquette">メーリングリストでのルール</a>に準拠して行動をするようにお願いします。</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC チャンネル</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">フォーラム</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Haiku 自体の開発のためのメーリングリスト</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">サードパーティソフトウェア開発者のためのメーリングリスト</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">その他のメーリングリスト</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,156 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Kacper Kasper
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Witamy w Haiku!</title>
|
||||
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Podręcznik użytkownika</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="images/flags/pl.png" alt="" /> Polski</li>
|
||||
<li><a href="welcome_fr.html"><img src="images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="welcome_de.html"><img src="images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="welcome_it.html"><img src="images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="welcome_ru.html"><img src="images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="welcome_es.html"><img src="images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="welcome_sv_SE.html"><img src="images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="welcome_hu.html"><img src="images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Tłumaczenie tej strony jest niekompletne. Nieukończone części wyświetlane są w języku angielskim.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Spis treści</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">Welcome to Haiku!</a><br />
|
||||
<a href="#bugreport">Beware of Bugs</a><br />
|
||||
<a href="#system">Getting to know the system</a><br />
|
||||
<a href="#software">Installing new software</a><br />
|
||||
<a href="#wifi">Wifi in Haiku</a><br />
|
||||
<a href="#api">Getting to know the API</a><br />
|
||||
<a href="#contact">Getting in contact</a>
|
||||
</td></tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Witamy w Haiku!</a></h2>
|
||||
<p>Thank you very much for checking out Haiku! This is our fourth public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a hrf="http://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Strzeż się błędów</a></h2>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
|
||||
<div class="box-warning">Odradzamy używania wersji alpha na codzień. Twoje dane mogą zostać zmienione, zniekształcone lub po prostu zniszczone.</div>
|
||||
|
||||
<p>One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
|
||||
<li><a href="pl/bugreports.html">Tips for a helpful bug report</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="system" name="system">Getting to know the system</a></h2>
|
||||
<p>The first release(s) of Haiku will be very much like the BeOS R5, the operating system it is reimplementing. If you never experienced it, have a look at these links:</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/pl/contents.html">Podręcznik użytkownika Haiku</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/" class="printurl">List of BeOS/Haiku websites</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">Instalowanie oprogramowania</a></h2>
|
||||
<p>Most of the available software can be downloaded and installed with the application HaikuDepot that comes with Haiku.<br />
|
||||
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/pl/applications.html">Applications</a>.</p>
|
||||
|
||||
<p>Besides using HaikuDepot, popular software repositories are:</p>
|
||||
<ul>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - maintains patches for ported software</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - hosts native BeOS and Haiku open source software projects in a github</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="wifi">WiFi w Haiku</a></h2>
|
||||
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/pl/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="api" name="api">Poznawanie API</a></h2>
|
||||
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
|
||||
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
|
||||
|
||||
<p>There are some resources that should help you getting started:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Development FAQ</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">Source Browser</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">The Be Book</a></li>
|
||||
<li><a href="http://api.haiku-os.org" class="printurl">The Haiku Book</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Archiwum biuletynów Be</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Getting in contact</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">Kanały IRC</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">Forums</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Overview of all mailing lists</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,157 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* tiagoms
|
||||
* Adriano Duarte
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Bem-vindo ao Haiku!</title>
|
||||
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Guia do Usuário</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="images/flags/pt_BR.png" alt="" /> Português (Brazil)</li>
|
||||
<li><a href="welcome_fr.html"><img src="images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="welcome_de.html"><img src="images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="welcome_it.html"><img src="images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="welcome_ru.html"><img src="images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="welcome_es.html"><img src="images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="welcome_sv_SE.html"><img src="images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="welcome_hu.html"><img src="images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">A tradução desta página ainda não está completa. Até lá, partes incompletas mostrarão o original em inglês.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Índice</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">Bem-vindo ao Haiku!</a><br />
|
||||
<a href="#bugreport">Cuidado com os bugs</a><br />
|
||||
<a href="#system">Conhecendo o sistema</a><br />
|
||||
<a href="#software">Instalando mais software</a><br />
|
||||
<a href="#wifi">Wifi no Haiku</a><br />
|
||||
<a href="#api">Conhecendo a API</a><br />
|
||||
<a href="#contact">Entrando em contato</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Bem-vindo ao Haiku!</a></h2>
|
||||
<p>Muito obrigado por seu interesse no Haiku! Este é o nosso quarto lançamento ao público. Esperamos atrair novos desenvolvedores para o projeto e dar aos futuros usuários uma oportunidade de experimentar o sistema. Nós entendemos que este <i>lançamento alpha</i> ainda não atende completamente os objetivos que definimos e que não oferece todas as funcionalidades e suavidade de utilização para usuário-final planejadas para a versão R1 final. Contudo, esperamos que este lançamento lhe permita descobrir o grande potencial do Haiku e que você possa compartilhar de nosso entusiasmo.</p>
|
||||
<p>Visite o site de nosso projeto <a hrf="http://www.haiku-os.org">Haiku-os.org</a> para saber das últimas notícias e comunicados.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Cuidado com os bugs</a></h2>
|
||||
<p>Estivemos trabalhando duro para corrigir bugs potencialmente críticos, entretanto, por ser uma versão alfa, há margem para a existência de muitos ainda não descobertos.</p>
|
||||
<div class="box-warning">Desencorajamos usar versões alfa como sistemas de produção. Seus dados podem ser seriamente alterados, corrompidos ou completamente destruídos.</div>
|
||||
|
||||
<p>Uma das principais razões para lançar uma versão alfa é atrair mais pessoas para testar o sistema e descobrir falhas ou oferecer sugestões para futuras melhorias. Por favor relate erros e melhorias no nosso rastreador de erros somente após usar nossa ferramenta de pesquisa, para evitar duplicidade.</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Rastreador de Erros do Haiku</a></li>
|
||||
<li><a href="pt_BR/bugreports.html">Dicas para um relatório de erros proveitoso</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="system" name="system">Conhecendo o sistema</a></h2>
|
||||
<p>A primeira versão do Haiku será muito mais como o BeOS R5, o sistema operacional que está sendo reimplementado. Se você nunca o experimentou, dê uma olhada nestes vínculos:</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/pt_BR/contents.html">Guia do Usuário Haiku</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/" class="printurl">Lista de sítios BeOS/Haiku</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">Instalando mais software</a></h2>
|
||||
<p>A maioria do software disponível pode ser baixado e instalado com o aplicativo Depósito Haiku, que vem com o Haiku.<br />
|
||||
Por causa da sua compatibilidade de código e binária, muitos aplicativos BeOS executam no Haiku. Muitos deles foram reempacotados para o Haiku ou ainda executam sem modificações. Você encontrará mais informações sobre instalar novos programas no capítulo <a href="../userguide/pt_BR/applications.html">Aplicativos</a> do guia do usuário.</p>
|
||||
|
||||
<p>Além de usar o Depósito Haiku, repositórios populares de software para o Haiku são:</p>
|
||||
<ul>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org/" class="printurl">HaikuPorts</a> - mantém patches para software portado</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">OsDrawer</a> - abriga projetos de sotftware BeOS e Haiku, de código aberto, nativos, em um GitHub.</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="wifi">Wifi no Haiku</a></h2>
|
||||
<p>Haiku suporta redes sem fio encriptados por WPA/WPA2 ou WEP e, naturalmente, abertas ou não encriptadas. Devido a várias políticas de licenciamento dos diferentes fabricantes de hardware, um processo de instalação manual de firmware pode ser necessário. Maiores informações sobre hardware suportado, instalação de firmware e como acessar uma rede sem fio no Guia do Usuário Haiku <a href="../userguide/{pt_BR}/workshop-wlan.html">Oficina: Redes sem fio</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="api" name="api">Conhecendo a API</a></h2>
|
||||
<p>Uma vez que o Haiku é uma reimplementação, a API é ainda a mesma do BeOS R5 (com alguns adicionais). Portanto, a documentação contida no Be Book é ainda um recurso válido. Agradecemos à ACCESS, que detém os direitos de propriedade da Be Inc., por nos permitir disponibilizar uma cópia do Be Book.<br />
|
||||
Diferenças da API do BeOS e adicionais específicos do Haiku são coletados no Haiku Book.</p>
|
||||
|
||||
<p>Existem alguns recursos que devem lhe ajudar a começar:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">FAQ de Desenvolvimento</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">Navegador de Código</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">O Be Book</a></li>
|
||||
<li><a href="http://api.haiku-os.org" class="printurl">O Haiku Book</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Arquivo de Boletins da Be</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Entrando em contato</a></h2>
|
||||
<p>Entre em contato com outros desenvolvedores e usuários e junte-se às discussões no IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> no webchat), em nossos fóruns ou nas listas de correio. Quando muitas pessoas diferentes se juntam, regras devem ser estabelecidas para manter a comunicação efetiva. Por favor, respeite nossa <a href="http://www.haiku-os.org/community/ml/etiquette">Etiqueta na Lista de Discussão</a>.</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">Canais de IRC</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">Fóruns</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Lista de discussão geral</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Lista de discussão de desenvolvimento referente ao próprio Haiku</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Lista de discussão dos programadores de aplicativos de terceiros</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Visão global de todas as listas de discussão</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,154 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Welcome to Haiku!</title>
|
||||
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="images/flags/pt_PT.png" alt="" /> Português</li>
|
||||
<li><a href="welcome_fr.html"><img src="images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="welcome_de.html"><img src="images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="welcome_it.html"><img src="images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="welcome_ru.html"><img src="images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="welcome_es.html"><img src="images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="welcome_sv_SE.html"><img src="images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="welcome_hu.html"><img src="images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">Welcome to Haiku!</a><br />
|
||||
<a href="#bugreport">Beware of Bugs</a><br />
|
||||
<a href="#system">Getting to know the system</a><br />
|
||||
<a href="#software">Installing new software</a><br />
|
||||
<a href="#wifi">Wifi in Haiku</a><br />
|
||||
<a href="#api">Getting to know the API</a><br />
|
||||
<a href="#contact">Getting in contact</a>
|
||||
</td></tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Welcome to Haiku!</a></h2>
|
||||
<p>Thank you very much for checking out Haiku! This is our fourth public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a hrf="http://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Beware of Bugs</a></h2>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.</div>
|
||||
|
||||
<p>One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
|
||||
<li><a href="pt_PT/bugreports.html">Tips for a helpful bug report</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="system" name="system">Getting to know the system</a></h2>
|
||||
<p>The first release(s) of Haiku will be very much like the BeOS R5, the operating system it is reimplementing. If you never experienced it, have a look at these links:</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/pt_PT/contents.html">Haiku User Guide</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/" class="printurl">List of BeOS/Haiku websites</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">Installing more software</a></h2>
|
||||
<p>Most of the available software can be downloaded and installed with the application HaikuDepot that comes with Haiku.<br />
|
||||
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/pt_PT/applications.html">Applications</a>.</p>
|
||||
|
||||
<p>Besides using HaikuDepot, popular software repositories are:</p>
|
||||
<ul>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - maintains patches for ported software</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - hosts native BeOS and Haiku open source software projects in a github</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="wifi">Wifi in Haiku</a></h2>
|
||||
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/pt_PT/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="api" name="api">Getting to know the API</a></h2>
|
||||
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
|
||||
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
|
||||
|
||||
<p>There are some resources that should help you getting started:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Development FAQ</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">Source Browser</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">The Be Book</a></li>
|
||||
<li><a href="http://api.haiku-os.org" class="printurl">The Haiku Book</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be Newsletter Archive</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Getting in contact</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">Forums</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Overview of all mailing lists</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,156 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Emrys
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Bine ați venit la Haiku!</title>
|
||||
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Ghid de utilizare</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="images/flags/ro.png" alt="" /> Română</li>
|
||||
<li><a href="welcome_fr.html"><img src="images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="welcome_de.html"><img src="images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="welcome_it.html"><img src="images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="welcome_ru.html"><img src="images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="welcome_es.html"><img src="images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="welcome_sv_SE.html"><img src="images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="welcome_hu.html"><img src="images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Traducerea acestei pagini nu este completă încă. Până când va fi, părțile incomplete utilizează originalul în limba engleză.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">Welcome to Haiku!</a><br />
|
||||
<a href="#bugreport">Beware of Bugs</a><br />
|
||||
<a href="#system">Getting to know the system</a><br />
|
||||
<a href="#software">Installing new software</a><br />
|
||||
<a href="#wifi">Wifi in Haiku</a><br />
|
||||
<a href="#api">Getting to know the API</a><br />
|
||||
<a href="#contact">Getting in contact</a>
|
||||
</td></tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Bine ați venit la Haiku!</a></h2>
|
||||
<p>Thank you very much for checking out Haiku! This is our fourth public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Vizitați site-ul web al proiectului nostru <a hrf="http://www.haiku-os.org">Haiku-os.org</a> pentru ultimile știri și anunțuri.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Aveți grijă la defecțiuni</a></h2>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
|
||||
<div class="box-warning">Descurajăm utilizarea versiunilor alpha drept sistem de producție. Este foarte posibil ca datele să devină alterate, deformate sau chiar distruse.</div>
|
||||
|
||||
<p>One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Monitor defecțiuni Haiku</a></li>
|
||||
<li><a href="ro/bugreports.html">Sfaturi pentru un raport de defecțiune util</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="system" name="system">Cunoașterea sistemului</a></h2>
|
||||
<p>The first release(s) of Haiku will be very much like the BeOS R5, the operating system it is reimplementing. If you never experienced it, have a look at these links:</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/ro/contents.html">Ghid Utilizare Haiku</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/" class="printurl">Listă site-uri BeOS/Haiku</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">Instalare de software</a></h2>
|
||||
<p>Most of the available software can be downloaded and installed with the application HaikuDepot that comes with Haiku.<br />
|
||||
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/ro/applications.html">Applications</a>.</p>
|
||||
|
||||
<p>Pe lângă utilizarea HaikuDepot, software popular pentru depozite sunt:</p>
|
||||
<ul>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">Arhiva de software BeOS a lui PulkoMandy</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Depozitul Haiku al lui Guest One</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Software Fat Elk</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - menține patches pentru software portat</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - găzduiește proiecte software open source native BeOS și Haiku într-un github</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="wifi">Wifi în Haiku</a></h2>
|
||||
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/ro/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="api" name="api">Cunoașterea API</a></h2>
|
||||
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
|
||||
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
|
||||
|
||||
<p>Există câteva resurse care ar trebui să vă ajute să începeți:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">FAQ Dezvoltare</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">Navigator de sursă</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">Cartea Be</a></li>
|
||||
<li><a href="http://api.haiku-os.org" class="printurl">Cartea Haiku</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Arhiva buletinului informativ Be</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Intrare în contact</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">Canale IRC</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">Forumuri</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Liste de discuții generale</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Listă de discuții pentru dezvoltare cu privire la Haiku în sine</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Listă de discuții pentru programatorii de aplicație 3rd party</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Prezentare generală a tuturor listelor de discuții</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,159 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Michael Smirnov
|
||||
* Rodastahm Islamov
|
||||
* Diver
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Добро пожаловать в Haiku!</title>
|
||||
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Руководство пользователя</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="images/flags/ru.png" alt="" /> Русский</li>
|
||||
<li><a href="welcome_fr.html"><img src="images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="welcome_de.html"><img src="images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="welcome_it.html"><img src="images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="welcome_es.html"><img src="images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="welcome_sv_SE.html"><img src="images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="welcome_hu.html"><img src="images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Перевод этой страницы еще не завершен. Пока это не произойдет, незавершенные части будут на английском.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Содержание</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">Добро пожаловать в Haiku!</a><br />
|
||||
<a href="#bugreport">Остерегайтесь ошибок!</a><br />
|
||||
<a href="#system">Знакомство с системой</a><br />
|
||||
<a href="#software">Установка дополнительных программ</a><br />
|
||||
<a href="#wifi">Wifi в Haiku</a><br />
|
||||
<a href="#api">Знакомство с API</a><br />
|
||||
<a href="#contact">Желаете пообщаться?</a>
|
||||
</td></tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Добро пожаловать в Haiku!</a></h2>
|
||||
<p>Thank you very much for checking out Haiku! This is our fourth public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Посетите сайт нашего проекта <a hrf="http://www.haiku-os.org">Haiku-os.org</a> чтобы узнать последние новости и объявления.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Остерегайтесь ошибок!</a></h2>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
|
||||
<div class="box-warning">Мы не рекомендуем использовать альфа-версии в качестве основной операционной системы. В ваши данные с большой вероятностью могут быть внесены нежелательные изменения, они могут быть искажены или даже уничтожены.</div>
|
||||
|
||||
<p>Одной из главных причин для выпуска альфа-версии явиляется желание привлечь больше пользователей для тестирования и обнаружения ошибок, а также получения от них предложений по дальнейшему улучшению Haiku. Пожалуйста, оставляйте отчёты о найденных багах и предложения по улучшению в нашей системе отслеживания ошибок (bug tracker), но только после использования поиска, чтобы избежать дубликатов.</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Система отслеживания ошибок в Haiku (Bug Tracker)</a></li>
|
||||
<li><a href="ru/bugreports.html">Советы по сообщениям об ошибках</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="system" name="system">Знакомство с системой</a></h2>
|
||||
<p>Первые релизы Haiku будут похожи по функционалу и вешнему виду на BeOS R5, которую она и призвана повторить. Если вы никогда не пользовались этой операционной системой, то рекомендуется воспользоваться следующими ссылками:</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/ru/contents.html">Руководство пользователя Haiku</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/" class="printurl">Список сайтов о BeOS/Haiku</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">Установка дополнительных программ</a></h2>
|
||||
<p>Most of the available software can be downloaded and installed with the application HaikuDepot that comes with Haiku.<br />
|
||||
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/ru/applications.html">Applications</a>.</p>
|
||||
|
||||
<p>Besides using HaikuDepot, popular software repositories are:</p>
|
||||
<ul>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - maintains patches for ported software</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - hosts native BeOS and Haiku open source software projects in a github</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="wifi">Wifi в Haiku</a></h2>
|
||||
<p>Haiku поддерживает беспроводные сети, зашифрованные с помощью WPA/WPA2 или WEP и конечно открытые, нешифрованные соединеня. Из-за разных лицензионных политик разных производителей возможно потребуется ручная установка микропрогаммы (firmware). Список работающих устройств и инструкции по установке и подключению к беспроводным сетям можно посмотреть на странице пользовательской документации Haiku <a href="../userguide/ru/workshop-wlan.html">Семинар: Беспроводные сети</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="api" name="api">Знакомство с интерфейсом программирования приложений (API)</a></h2>
|
||||
<p>Так как Haiku повторяет BeOS R5, то и всё, что касается API у них схоже (с некоторыми исключениями), потому документация в BeBook всё ещё актуальна. Благодаря компании ACCESS, которой принадлежат права на интеллектуальную собственность Be Inc., нам позволено распространять BeBook.
|
||||
Изменения в BeOS API и Haiku специфические дополнения собраны в Книге Haiku.</p>
|
||||
|
||||
<p>Существуют и другие ресурсы, которые должны помочь Вам начать изучение:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">ЧАВО разработчика</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">Браузер исходного кода </a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">BeBook</a></li>
|
||||
<li><a href="http://api.haiku-os.org" class="printurl">Книга Haiku</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Архив Be Newsletter</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Желаете пообщаться?</a></h2>
|
||||
<p>Вы можете связаться с разработчиками и другими пользователями, присоединившись к обсуждению на IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> в вебчате), каналах, нашем форуме или в списках рассылки. Когда множество людей обсуждают что-то вместе, то необходимо соблюдать некоторые правила для сохранения эффективности общения. Пожалуйста, придерживайтесь <a href="http://www.haiku-os.org/community/ml/etiquette">Этикета списков рассылки</a>.</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC каналы</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">Форумы</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Основной список рассылки</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Список рассылки непосредственных разработчиков Haiku</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Список рассылки для разработчиков сторонних приложений</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Обзор всех списков рассылки</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,155 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* helix84
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Víta vás Haiku!</title>
|
||||
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Používateľská príručka</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="images/flags/sk.png" alt="" /> Slovenčina</li>
|
||||
<li><a href="welcome_fr.html"><img src="images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="welcome_de.html"><img src="images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="welcome_it.html"><img src="images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="welcome_ru.html"><img src="images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="welcome_es.html"><img src="images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="welcome_sv_SE.html"><img src="images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="welcome_hu.html"><img src="images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Obsah</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">Víta vás Haiku!</a><br />
|
||||
<a href="#bugreport">Pozor na chyby</a><br />
|
||||
<a href="#system">Spoznávanie systému</a><br />
|
||||
<a href="#software">Inštalovanie ďalšieho softvéru</a><br />
|
||||
<a href="#wifi">Wifi v Haiku</a><br />
|
||||
<a href="#api">Spoznávanie API</a><br />
|
||||
<a href="#contact">Kontaktujte nás</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Víta vás Haiku!</a></h2>
|
||||
<p>Ďakujeme vám, že ste vyskúšali Haiku! Toto je naše štvrté verejné vydanie. Dúfame, že náš projekt zaujme nových vývojárov a dá budúcim používateľom šancu vyskúšať Haiku. Uvedomujeme si, že toto <i>alfa vydanie</i> zatiaľ celkom nedosahuje cieľov, ktoré sme si stanovili a neponúka všetky možnosti a bezproblémový používateľský zážitok, ktorý je plánovaný pre finálne vydanie R1. Dúfame však, že vám toto vydanie Haiku umožní objaviť veľký potenciál Haiku a že zdieľate naše nadšenie.</p>
|
||||
<p>Posledné novinky a oznámenia nájdete na webovej stránke projeku <a hrf="http://www.haiku-os.org">Haiku-os.org</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Pozor na chyby</a></h2>
|
||||
<p>Usilovne sme odstraňovali a stále pracujeme na odstraňovaní všetkých závažných chýb, ale pretože toto je alfa vydanie, určite je v ňom ešte mnoho neodhalených chýb.</p>
|
||||
<div class="box-warning">Neodporúčame používať alfa verzie ako produkčný systém. Vaše dáta sa môžu zmeniť, poškodiť alebo úplne zničiť.</div>
|
||||
|
||||
<p>Jedným z hlavných dôvodov vydania alfa verzie je prilákanie ďalších ľudí, aby otestovali systém a odhalili chyby alebo vyjadrili svoje návrhy ďalších vylepšení. Prosím, posielajte chyby a vylepšenia do nášho systému na sledovanie chýb potom, ako použijete jeho vyhľadávacie funkcie, aby sme predišli duplicitám.</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Systém sledovania chýb Haiku</a></li>
|
||||
<li><a href="sk/bugreports.html">Tipy na užitočné hlásenie o chybe</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="system" name="system">Spoznávanie systému</a></h2>
|
||||
<p>Prvé vydanie či vydania Haiku budú veľmi podobné ako BeOS R5, operačný systém, ktorý sa snaží reimplementovať. Ak ho nikdy nezažili, pozrite sa na tieto odkazy:</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/sk/contents.html">Používateľská príručka Haiku</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/" class="printurl">Zoznam webov o BeOS/Haiku</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">Inštalovanie ďalšieho softvéru</a></h2>
|
||||
<p>Väčšinu dostupného softvéru je možné stiahnuť a nainštalovať pomocou aplikácie HaikuDepot, ktorá sa dodáva spolu s Haiku.<br />
|
||||
Vďaka tomu, že Haiku je kompatibilné s BeOS na binárnej úrovni aj na úrovni zdrojového kódu, mnohé aplikácie pre BeOS bežia na Haiku. Pre mnohé z nich boli vytvorené balíky pre Haiku alebo jednoducho bežia nezmenené. Ďalšie informácie o inštalovaní nových programov nájdete v Používateľskej príručke v kapitole <a href="../userguide/sk/applications.html">Aplikácie</a>.</p>
|
||||
|
||||
<p>Ďalšie populárne zdroje softvéru okrem HaikuDepot sú:</p>
|
||||
<ul>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy-ho archív BeOS softvéru</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Repozitár Haiku od Guest One</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - spravuje záplaty portovaného softvéru</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - na GitHube hosťuje natívne open source projekty pre BeOS a Haiku</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="wifi">Wi-Fi v Haiku</a></h2>
|
||||
<p>Haiku podporuje siete Wi-Fi, ktoré sú šifrované pomocou WPA/WPA2 alebo WEP a samozrejme otvorené, nešifrované spojenia. Z dôvodu niekoľkých odlišných licenčných politík rôznych dodávateľov hardvéru, možno budete musieť firmvér nainštalovať ručne. Zoznam fungujúcich zariadení a inštalačné inštrukcie k firmvéru a dokumentáciu o pripájaní k bezdrôtovým sieťam nájdete v Príručke Haiku <a href="../userguide/sk/workshop-wlan.html">Workshop: Bezdrôtové siete</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="api" name="api">Spoznávanie API</a></h2>
|
||||
<p>Keďže Haiku je reimplementácia, API je stále rovnaké ako mal BeOS R5 (s istými rozšíreniami). Preto dokumentácia v Be Book je stále platný zdroj. Vďaka ACCESS, ktorý vlastní práva k bývalému majetku spoločnosti Be Inc., máme povolenie poskytovať kópiu Be Book.<br />
|
||||
Odchýlky od API BeOSu a rozšírenia špecifické pre Haiku sú zdokumentované v Haiku Book.</p>
|
||||
|
||||
<p>Existujú zdroje, ktoré vám pomôžu začať:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Často kladené otázky - vývoj</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">Prehliadač zdrojového kódu</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">The Be Book</a></li>
|
||||
<li><a href="http://api.haiku-os.org" class="printurl">The Haiku Book</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Archív newsletterov Be</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Kontaktujte nás</a></h2>
|
||||
<p>Kontaktujte ostatných vývojárov a používateľov a pridajte sa do diskusií na IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> na webčete), v našich fórach alebo poštových konferenciách. Keď sa zhromaždí veľa rôznych ľudí, musia sa stanoviť pravidlá, aby komunikácia zostala efektívna. Prosím, rešpektujte <a href="http://www.haiku-os.org/community/ml/etiquette">Etiketu našej konferencie</a>.</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">Kanály IRC</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">Fóra</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Všeobecná poštová konferencia</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Poštová konferencia o vývoji samotného Haiku</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Poštová konferencia o vývoji aplikácií tretích strán</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Prehľad všetkých poštových konferencií</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,157 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* deejam
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Välkommen till Haiku!</title>
|
||||
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>Användarhandbok</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="images/flags/sv_SE.png" alt="" /> Svenska</li>
|
||||
<li><a href="welcome_fr.html"><img src="images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="welcome_de.html"><img src="images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="welcome_it.html"><img src="images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="welcome_ru.html"><img src="images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="welcome_es.html"><img src="images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="welcome_hu.html"><img src="images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Översättningen av denna sida är inte komplett. Delar av innehållet kommer därför att visas på engelska.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">Welcome to Haiku!</a><br />
|
||||
<a href="#bugreport">Beware of Bugs</a><br />
|
||||
<a href="#system">Getting to know the system</a><br />
|
||||
<a href="#software">Installing new software</a><br />
|
||||
<a href="#wifi">Wifi in Haiku</a><br />
|
||||
<a href="#api">Getting to know the API</a><br />
|
||||
<a href="#contact">Getting in contact</a>
|
||||
</td></tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Välkommen till Haiku!</a></h2>
|
||||
<p>Thank you very much for checking out Haiku! This is our fourth public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a hrf="http://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Varning för buggar</a></h2>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
|
||||
<div class="box-warning">Vi rekommenderar inte att använda alfa versioner i ett produktionssystem. Din data kan mycket väl ändras, eller helt enkelt förstöras.</div>
|
||||
|
||||
<p>En av huvudanledningarna till varför vi ger ut en alfa-version är för att locka fler att testa systemet, upptäcka buggar eller förse oss med förslag för framtida förbättringar. Vänligen registrera buggar och förbättringar i vårt projekthanteringssystem efter att ha använt dess sökfunktion, för att på så sätt undvika att dubletter skapas.</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku's projekthanteringssystem</a></li>
|
||||
<li><a href="sv_SE/bugreports.html">Tips för hjälpsam buggrapportering</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="system" name="system">Lär känna Haiku</a></h2>
|
||||
<p>Dom första utgåvorna av Haiku kommer att vara väldigt lik BeOS R5, operativsystemet som vi omimplementerar. Om du aldrig har upplevt det, ta då en titt på följande länkar:</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/sv_SE/contents.html">Haiku's Användarhandbok</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/" class="printurl">Lista över BeOS/Haiku hemsidor</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">Installera ytterligare programvara</a></h2>
|
||||
<p>Most of the available software can be downloaded and installed with the application HaikuDepot that comes with Haiku.<br />
|
||||
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/sv_SE/applications.html">Applications</a>.</p>
|
||||
|
||||
<p>Besides using HaikuDepot, popular software repositories are:</p>
|
||||
<ul>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - maintains patches for ported software</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - hosts native BeOS and Haiku open source software projects in a github</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="wifi">Wifi i Haiku</a></h2>
|
||||
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/sv_SE/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="api" name="api">Lär känna Haiku's API</a></h2>
|
||||
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
|
||||
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
|
||||
|
||||
<p>There are some resources that should help you getting started:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Utvecklings FAQ</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">Källkodsläsare</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">The Be Book</a></li>
|
||||
<li><a href="http://api.haiku-os.org" class="printurl">The Haiku Book</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be's nyhetsbrevsarkiv</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Kom i kontakt med oss</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC kanaler</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">Forum</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Allmän e-postlista</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">E-postlista för utveckling av Haiku</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">E-postlista för utveckling av tredjeparts programvara</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Översikt över alla e-postlistor</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,157 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* totish
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Вітаємо в Haiku!</title>
|
||||
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="images/flags/uk.png" alt="" /> Українська</li>
|
||||
<li><a href="welcome_fr.html"><img src="images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="welcome_de.html"><img src="images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="welcome_it.html"><img src="images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="welcome_ru.html"><img src="images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="welcome_es.html"><img src="images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="welcome_sv_SE.html"><img src="images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
|
||||
<li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="welcome_hu.html"><img src="images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">Welcome to Haiku!</a><br />
|
||||
<a href="#bugreport">Beware of Bugs</a><br />
|
||||
<a href="#system">Getting to know the system</a><br />
|
||||
<a href="#software">Installing new software</a><br />
|
||||
<a href="#wifi">Wifi in Haiku</a><br />
|
||||
<a href="#api">Getting to know the API</a><br />
|
||||
<a href="#contact">Getting in contact</a>
|
||||
</td></tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Вітаємо в Haiku!</a></h2>
|
||||
<p>Thank you very much for checking out Haiku! This is our fourth public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a hrf="http://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Остерігайтесь помилок</a></h2>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
|
||||
<div class="box-warning">Ми не рекомендуємо використовувати альфа версій у якості основної опереаційної системи. У Ваші дані з великою ймовірністю можуть бути внесені небажані зміни, вони можуть бути спотворені або навіть знищені.</div>
|
||||
|
||||
<p>Одна з основних причин випуску альфа-версії є бажання привернути більше користувачів для тестування і виявлення помилок, а також отримання від них пропозицій для подальшого покращення Haiku. Прохання залишати звіти про найдені помилки і пропозиції з покращення ОС в нашій системі відслідкування помилок (bug tracker) , але тільки після попереднього пошуку, для уникнення появи дублікатів.</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Система відслідковування помилок у Haiku (Bug Tracker)</a></li>
|
||||
<li><a href="uk/bugreports.html">Поради по повідомленнях про помилки</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="system" name="system">Знайомство з системою</a></h2>
|
||||
<p>Перші релізи Haiku будуть схожі по функціоналу і зовнішньому вигляду на BeOS R5, яку ми і намагалися відтворити. Якщо Ви ніколи нею не користувались варта скористатись такими посиланнями:</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/uk/contents.html"> Настанова користувача Haiku</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/" class="printurl">Список сайтів про BeOS/Haiku</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">Встановлення додаткових програм</a></h2>
|
||||
<p>Most of the available software can be downloaded and installed with the application HaikuDepot that comes with Haiku.<br />
|
||||
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/uk/applications.html">Applications</a>.</p>
|
||||
|
||||
<p>Besides using HaikuDepot, popular software repositories are:</p>
|
||||
<ul>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - maintains patches for ported software</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - hosts native BeOS and Haiku open source software projects in a github</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="wifi">Wifi в Haiku</a></h2>
|
||||
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/uk/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="api" name="api">Знайомство з інтерфейсом програмування додатків (API)</a></h2>
|
||||
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
|
||||
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
|
||||
|
||||
<p>There are some resources that should help you getting started:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">FAQ для розробників</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">Source Браузер вихідного коду</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl"> Be Book</a></li>
|
||||
<li><a href="http://api.haiku-os.org" class="printurl">The Haiku Book</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Архів Be Newsletter</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Бажаєте спілкування</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC канали</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">Форуми</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Основний список розсилки</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Список розсилки безпосередніх розробників Haiku</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Список розсилки для розробників сторонніх додатків</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Огляд усіх списків розсилки</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,155 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Pengphei Han
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>欢迎使用Haiku！</title>
|
||||
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>用户指南</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</li>
|
||||
<li><a href="welcome_fr.html"><img src="images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="welcome_de.html"><img src="images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="welcome_it.html"><img src="images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="welcome_ru.html"><img src="images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="welcome_es.html"><img src="images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="welcome_sv_SE.html"><img src="images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="welcome_hu.html"><img src="images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>索引</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">欢迎使用 Haiku！</a><br />
|
||||
<a href="#bugreport">警惕程序错误</a><br />
|
||||
<a href="#system">了解 Haiku 系统</a><br />
|
||||
<a href="#software">安装新软件</a><br />
|
||||
<a href="#wifi">Haiku 无线网络</a><br />
|
||||
<a href="#api">了解 Haiku 的API</a><br />
|
||||
<a href="#contact">联系我们</a>
|
||||
</td></tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">欢迎使用Haiku！</a></h2>
|
||||
<p>非常感谢您对Haiku的试用和测试！这是我们公开发布的第四个版本，我们希望能够吸引更多的开发者参与我们的项目，也希望能够为将来的用户提供测试 Haiku 的机会。我们也注意到本<i>试用版本</i> 还远远没有达到既定的目标，没有提供为最终的 R1 版本计划的所有特性和全面用户体验。然而，我们希望这一版本可以让您发现 Haiku 的巨大潜力，让您分享我们的喜悦。</p>
|
||||
<p>最新新闻和公告请访问我们的网站 <a hrf="http://www.haiku-os.org">Haiku-os.org</a> 。</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">警惕错误</a></h2>
|
||||
<p>我们已经尽力去修复所有发现了的错误。然而作为测试版本，它可能还有许多未发现的错误。</p>
|
||||
<div class="box-warning">我们不鼓励您使用测试版本作为生产用系统。因为您的数据可能会被改变，损坏或者完全销毁。</div>
|
||||
|
||||
<p>发布该测试版本的主要原因之一是为了吸引更多的用户来测试系统，发现错误，提供未来发展的建议。在您使用我们的错误跟踪系统提交错误或者发展建议之前，请使用它的查询功能来避免重复的提交相同的内容。</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku错误跟踪系统</a></li>
|
||||
<li><a href="zh_CN/bugreports.html">错误报告的提示</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="system" name="system">了解Haiku操作系统</a></h2>
|
||||
<p>Haiku的第一个系列的版本将会非常类似于BeOS R5，是BeOS R5系统的重建系统。如果您从未尝试过该系统，您可以参阅以下链接：</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/zh_CN/contents.html">Haiku用户指南</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/" class="printurl"> BeOS/Haiku 网站清单</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">安装更多的程序</a></h2>
|
||||
<p>很多程序都可以通过 Haiku 内置的 HaikuDepot 程序进行下载和安装。由于二进制库和源代码的兼容性，许多 BeOS 程序可以在 Haiku 系统中运行。它们中的大多数已经为 Haiku 进行了重新的打包或者仍未做修改。您可以在用户指南的 <a href="../userguide/zh_CN/applications.html">应用程序</a> 一节中找到更多有关安装新程序的相关信息。</p>
|
||||
|
||||
<p>除了 Haiku 软件仓库，其他非常有名的软件仓库有：</p>
|
||||
<ul>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - 包含了移植程序的补丁</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - 在 Github 中保留了原生的 BeOS 和 Haiku 开源程序项目</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="wifi">Haiku 无线网络</a></h2>
|
||||
<p>Haiku目前支持WPA/WPA2 和 WEP 加密的无线网络，当然也包括开放的和未加密的网络。由于不同提供商的各种不同的授权政策，对于一些固件，可能需要手动的安装。您可以在我们 Haiku 用户指南的<a href="../userguide/zh_CN/workshop-wlan.html">操作练习：无线网络</a>页面上找到更多有关硬件支持，固件安装以及如何进行无线网络连接的详细信息。</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="api" name="api">了解Haiku的API</a></h2>
|
||||
<p>由于 Haiku 是 BeOS 系统的重新实现，它的 API 仍然和 BeOS R5 的相同（增添了一些特性）。所以 Be Book 中的文档仍然是非常有用的资源。非常感谢前 BeOS 公司财产的拥有者 - ACCESS，我们才可以提供 Be Book 的副本供大家参考。BeOS API 与 Haiku 之间的不同之处可以参考 Haiku Book。</p>
|
||||
|
||||
<p>下面的资源对您的入门会有很多帮助：</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">开发FAQ</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">源码浏览</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">Be Book</a></li>
|
||||
<li><a href="http://api.haiku-os.org" class="printurl">Haiku Book</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be 通讯存档</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">联系我们</a></h2>
|
||||
<p>通过参加 IRC（<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> 聊天室），论坛，邮件列表中的讨论来同其他的开发者和用户保持联系。由于许多不同人员的参与，我们需要制定一些规则使交流变得方便有效。请遵守我们的 <a href="http://www.haiku-os.org/community/ml/etiquette"> 邮件列表规范</a>。</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC聊天频道</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">相关论坛</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">通用邮件列表</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">开发邮件列表（只关注 Haiku 项目）</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">开发邮件列表（第三方程序）</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">所有邮件列表概览</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,183 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* Pengphei Han
|
||||
* dgy18787
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>报告错误</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>用户指南</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</li>
|
||||
<li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../hu/bugreports.html"><img src="../images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="../pt_BR/bugreports.html"><img src="../images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="../ca/bugreports.html"><img src="../images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="../pl/bugreports.html"><img src="../images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="../ro/bugreports.html"><img src="../images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_zh_CN.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>索引</td></tr>
|
||||
<tr class="index"><td><a href="#account">获取Trac账户</a><br />
|
||||
<a href="#report">创建错误报告</a><br />
|
||||
<a href="#app">软件错误</a><br />
|
||||
<a href="#server">服务错误</a><br />
|
||||
<a href="#kernel">内核错误</a><br />
|
||||
<a href="#kdl">内核调试- KDL</a><br />
|
||||
<a href="#syslog">系统日志</a><br />
|
||||
<a href="#onscreen">屏幕调试</a><br />
|
||||
<a href="#hardware">硬件错误</a><br />
|
||||
<a href="#next">下一步？</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>报告错误</h1>
|
||||
|
||||
<p>由于我们的开发人员不可能测试每种硬件组合和每种不同的系统交互方式，所以我们依赖于用户，通过用户来给予我们Haiku的运行情况。由于Haiku还很年轻，您在使用时很有可能会遇到错误。我们非常感谢您能够分出时间来提交这些错误报告。我们可以共同一步一步的提高Haiku的性能。</p>
|
||||
<p>为了确保我们的错误跟踪系统的有效性，遵守共同的<a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">错误报告规范</a>是很有必要的。</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">获取Trac账户</a></h2>
|
||||
<p>为了提交任务单，您需要在<a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku 的错误跟踪系统</a>中注册一个账户。
|
||||
<br />
|
||||
新建账户时，您需要<b>提供自己的电子邮箱</b> ，否则您将不具备基本的任务单修改权限。完成之后，您必须要保证<b>检查您的垃圾邮箱</b>，因为所有重要的验证邮件可能都会被发送到那里。</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">创建错误报告</a></h2>
|
||||
<p>在报告一个错误之前，请您<a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">确保</a>该错误报告之前不存在。你可以使用<a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">查找</a>功能来查找其是否存在。
|
||||
<br />
|
||||
在确定它是一个独特的错误之后，您需要尽可能的找出有关的详细信息：</p>
|
||||
<ul>
|
||||
<li><p>尝试在当前版本的Haiku系统中重现您的问题。 有许多用于测试的预编译镜像都是<a href="http://haiku-files.org/">可用的</a>。</p></li>
|
||||
<li><p>包括基本的信息，例如以何种方式测试 Haiku（利用真实的硬件，VMware，还是 QEMU）。</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>描述您所遇到的问题。尽量把问题讲得精确和明白：详细的描述系统的行为反馈，和您期望的反馈。</p></li>
|
||||
<li><p>描述出现该错误所需要的操作步骤。这将会有助于开发者重现该错误，并对其进行修复和完善。</p></li>
|
||||
<li><p>附带你所掌握的尽可能多的信息。如果是一个GUI错误，或者其中的程序错误，尽量使用 <span class="key">PRINT</span> 键来截取当时的屏幕图像。</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">程序错误</a></h2>
|
||||
<p>如果程序发生崩溃，您需要从弹出的警告窗口中启动调试程序。它将会打开一个运行gdb（GNUdebugger）的终端窗口。输入 <span class="cli">bt</span>，您将会创建一个有关调试信息的“回溯”，然后您需要把它完整的复制出来（包括您输入 <span class="cli">bt</span> 命令之前终端中显示的内容），附加到错误报告中。</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">服务错误</a></h2>
|
||||
<p>当 app server，registrar server 或者 input server 等重要组件崩溃时，您将无法看到通常的崩溃警告。相反的，整个屏幕将会呈现白色，并且启动一个 gdb 会话，相关的输出信息直接在屏幕中进行显示。您可能还可以继续移动鼠标，这将会覆盖掉屏幕中的白色区域和 gdb 输出信息。仍在运行的程序 (例如，进程控制器或者桌面栏的时钟) 可能也会覆盖屏幕中的调试信息。
|
||||
<br />
|
||||
除却所有显示的丑陋和操作的不便，它与软件出错基本一样。 最重要的是获取一个有关错误的回溯（使用 <span class="cli">bt</span> 命令）。如果不能够拷贝相关的文本，您可能还需要使用数码相机记录下相关的屏幕显示。</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">内核错误</a></h2>
|
||||
<p>内核错误通常都是危害效果最大的错误，同时也是最难调试的错误。下面几种情形，通常都可能是内核或者驱动问题：</p>
|
||||
<ul>
|
||||
<li><p>系统自动进入了内核调试状态（KDL），屏幕上方显示为白色，并且打印出几行文本。文本第二行显示为“<i>Welcome to Kernel Debugging Land...</i>”，而第一行则声明了进入内核调试状态的实时原因。</p></li>
|
||||
<li><p>系统自动重新启动。</p></li>
|
||||
<li><p>系统完全冻结。您无法移动鼠标，并且屏幕中无任何程序显示。在此情况下，重要的是测试能否使用快捷键 <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> 进入内核调试状态（在多数键盘上，<span class="key">SysReq</span> 是 <span class="key">PRINT</span> 键）。然后等待至少一分钟，查看系统反应状态。</p></li>
|
||||
<li><p>系统无法实现正确引导。它可能自动重启，或停止在某个步骤（例如，某个启动图标）。对于后一种情况，可以尝试使用快捷键 <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>。</p></li>
|
||||
<li><p>整个系统或者部分硬件无法正确运行。例如，系统运行缓慢，出现错误，或者完全无法运行。如果某个硬件完全无法工作，首要的是检查Haiku目前是否支持该硬件（例如，在邮件列表或论坛中进行询问）。</p></li>
|
||||
</ul>
|
||||
<p>需要注意的是，只有最后这种情况与硬件相关，而所有其他的问题也可能由硬件驱动中的错误引起。如果您对引起该问题的硬件或相关的驱动有所疑问，您可以检查删除/禁用该硬件或驱动是否会产生影响。例如，如果您怀疑无线网络有问题，您会发现 BIOS 中有可禁用它的选项。如果其中没有该选项，您可以从安装的 Haiku 中删除相关的无线网络驱动（参见 <a href="../../../userguide/en/bootloader.html">引导程序</a>）。</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">内核调试 - KDL</a></h3>
|
||||
<p>如果系统没有自动的进入内核调试状态，您也可以有意识的使用 <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> 快捷键手动进入。<br />
|
||||
需要注意的是，在内核调试状态，您的键盘可能会无法工作。PS/2 键盘通常都能够正常工作；对于 UHCI 控制器连接的 USB 键盘，您至少需要使用快捷键进入内核调试状态一次，它才可用。但是对于 USB OCHI，目前还未实现支持。</p>
|
||||
<p>KDL 本身是 shell 中的一类。它可以执行命令，打印系统信息。下面是一些感兴趣的命令：</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>打印回溯信息。如果系统自主进入内核调试状态，通常需要输入该命令。</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>显示已处理和未处理的硬件中断。</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (aka continue)</td><td> </td><td>离开内核调试状态；如果可能的话，继续正常的系统操作。</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>立即重启系统。您将会丢失所有未保存的数据，甚至包括那些已经保存，但是还未写入硬盘的数据。</td></tr>
|
||||
</table>
|
||||
<p>获取更多信息，请参阅 <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">欢迎使用内核调试工具</a>。</p>
|
||||
<p>KDL输出信息将会写入到串行端口（如果您拥有另一台与之相连接的计算机，您可以通过中断程序重定向输出信息）和系统日志。如果您无法离开KDL，它将无法写入系统日志文件。尽管如此，还有一个系统引导调试选项，允许您捕获系统信息（参阅下文）。</p>
|
||||
<p>您可以从KDL输出中生成 QR 代码，而它们可以通过智能手机或相似设备转换为文本内容。有关如何使用该功能从 KDL 获取数据，详情参考 <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> 。</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">系统日志</a></h3>
|
||||
<p><b>这是从无法引导的系统中获取信息的首选方法。</b>
|
||||
<br />
|
||||
系统日志（syslog，system log 的缩写）中包含了关于系统问题的有用信息，包括 KDL 会话的输出信息 。通常将它附带到有关内核问题的报告中是个不错的主意。系统日志将会写入文件 <span class="path">/boot/system/var/log/syslog</span>。由于写入文件需要系统处于运行状态，因此当内核出现问题时（尤其是，系统自动重启，或者无法持续 KDL 会话），最新的输出信息可能无法写入日志文件。</p>
|
||||
<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog persistent. If the option <span class="menu">Save syslog from previous session during boot</span> is activated in the boot loader options (as it is by default), you'll find the syslog of your last session as <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
If you're not able to boot to get to the previous_syslog, you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
|
||||
In the boot loader's <span class="menu">Debug menu</span> you should find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. Note: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">屏幕调试</a></h3>
|
||||
<p><b>屏幕调试输出仅对调试特殊问题有用，而且自身也有（定时）问题。若非必须，不要使用它。</b><br />
|
||||
只有当Haiku引导机器失败，而且 <span class="menu">Debug syslog option</span> 出于某些原因无法使用，它才具有重要意义。 在Haiku的引导徽标出现之前，按下 <span class="key">SHIFT</span> 进入引导程序菜单。 选择 <span class="menu">Select safe mode options</span>。 在接近屏幕底部，<span class="menu">[ ] Enable on screen debug output</span> 将会列出。（注意：如果尝试启动Haiku，您可以启用另一个选项。如果Haiku只有在启用多个选项时才可以启动，您在错误报告中一定要给出这些选项。）<br />
|
||||
最后，选择 <span class="menu">Return to main menu</span> 和 <span class="menu">Continue booting</span>。<br />
|
||||
在屏幕上将会显示一页或者多页文本，只有最后几行才需要附带到您的错误报告。更多信息，参阅 <a href="../../../userguide/zh_CN/bootloader.html">引导程序</a>。</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">硬件错误</a></h2>
|
||||
<p>在处理有关硬件/驱动的问题时，您需要在报告中附带下面的信息：</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td> 给出所有硬件的详细列表，包括提供商和 PCI ID；类似于Linux下的 <span class="cli">lshw</span> 和 <span class="cli">lspci</span> 。</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>假如是有关 USB 的问题，它类似于Linux下的 <span class="cli">lsusb</span>。</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Haiku的主要系统日志，类似于引导过程中的屏幕调试信息。您可以使用 <span class="cli">open</span> 命令在文本编辑器中获取到系统日志中相关的部分。</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td> 列出所有使用的驱动。</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>只在 <i>内核调试状态</i> 可用（参阅下文）。它用显示中断使用情况。不可能有许多由不同硬件共享的中断。</td></tr>
|
||||
<tr><td colspan="3">- 屏幕调试输出（引导时间选项的安全模式）。</td></tr>
|
||||
</table>
|
||||
|
||||
<p>前四个命令需要在终端中进行输入。在命令后添加 <span class="cli"> > output.txt</span> ，然后输出的信息将会重定向到“output.txt”文本文件，您可以将其附带到您的错误报告或者邮件。</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">下一步</a></h2>
|
||||
<p>在您提交错误报告之后，开发人员将会检查您的错误，然后尝试进行修复。但是需要注意的是，我们所有的人员都是志愿者，有时候一个错误报告可能会很长时间没有人来进行回复。如果可以的话，添加新的信息将会有助于早点修复错误，但是请不要添加非描述性的评论来将“炒热”该错误。</p>
|
||||
<p>切记，提交错误报告不是花很少时间写个报告，然后就结束了。如果您提交了一个错误，然后您就是Haiku开发过程中的一员。开发人员在解决您的错误过程中可能会遇到问题，因此请你一定要始终关注该错误，然后回答相关的问题。如果该问题没有“fixed”，你的任务就没有“done”。</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_zh_CN.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,164 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2010-2011, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* Pengphei Han
|
||||
* dgy18787
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta http-equiv="Content-Style-Type" content="text/css" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>无线网络</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>用户指南</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</li>
|
||||
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
|
||||
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
|
||||
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
|
||||
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
|
||||
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
|
||||
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
|
||||
<span>
|
||||
<a href="../welcome_zh_CN.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
|
||||
<h2>Haiku中的无线网络</h2>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="hardware" rel="nofollow" id="hardware">预期的硬件支持</a></h3>
|
||||
<p>FreeBSD 8的所有无线驱动都应该可以工作。但是任何的PCMCIA，CardBus，ExpressCard，USB或者基于ISA的网卡将无法工作。只有PCI，miniPCI，PCI-Express，miniPci-Express 和 PCI-X 才应该可以工作。<br />
|
||||
包括以下：
|
||||
</p>
|
||||
<ul>
|
||||
<li><p><i>aironetwifi</i> 至少支持：<br />
|
||||
Cisco Aironet 350 Series<br />
|
||||
Aironet PCI4500<br />
|
||||
Aironet PCI4800<br />
|
||||
</p></li>
|
||||
<li><p><i>atheroswifi</i>支持几乎所有的芯片集(但是除了 AR9285 芯片)</p></li>
|
||||
<li><p><i>broadcom43xx</i> 支持：<br />
|
||||
BCM4301，BCM4306，BCM4307，BCM4309，BCM4311，BCM4312和 BCM4318
|
||||
</p></li>
|
||||
<li><p><i>iprowifi2100</i> 支持英特尔专业无线 2100 芯片</p></li>
|
||||
<li><p><i>iprowifi2200</i> 支持英特尔无线卡：<br />
|
||||
2200BG<br />
|
||||
2225BG<br />
|
||||
2915ABG
|
||||
</p></li>
|
||||
<li><p><i>iprowifi3945</i> 支持英特尔 3945 专业无线芯片</p></li>
|
||||
<li><p><i>iprowifi4965</i>支持英特尔 4965 专业无线芯片</p></li>
|
||||
<li><p><i>marvell88w8335</i> 支持：
|
||||
<br />
|
||||
Marvell Libertas 88W8310<br />
|
||||
Marvell Libertas 88W8335
|
||||
</p></li>
|
||||
<li><p><i>marvell88w8363</i> 支持 88W8363 芯片</p></li>
|
||||
<li><p><i>ralinkwifi</i> 支持：
|
||||
<br />
|
||||
RT2560<br />
|
||||
RT2561S<br />
|
||||
RT2561<br />
|
||||
RT2661
|
||||
</p></li>
|
||||
<li><p>ralink2860 支持 Ralink RT2860</p></li>
|
||||
<li><p><i>wavelanwifi</i> 目前支持：
|
||||
<br />
|
||||
3Com Airconnect<br />
|
||||
GLPRISM2 WaveLAN<br />
|
||||
Intersil Prism3<br />
|
||||
Intersil Prism2.5<br />
|
||||
Linksys WDT11<br />
|
||||
Netgear MA301<br />
|
||||
PRISM2STA WaveLAN<br />
|
||||
Siemens SpeedStream<br />
|
||||
SMC 2602W<br />
|
||||
Us Robotics 2415<br />
|
||||
Addtron AWA-100 PCI
|
||||
</p></li>
|
||||
</ul>
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="connect" rel="nofollow" id="connect">连接到无线网络</a></h3>
|
||||
<p>除了未加密网络，Haiku 还初步支持通过<a href="#wep-notes" rel="nofollow">WEP 密钥</a> 访问无线网络。WEP 是早期的加密方法，尽管不是最安全的。</p>
|
||||
<p>你可以通过在终端中输入 <span class="cli">ifconfig</span> 列出可用网络，并且加入或者断开连接。</p>
|
||||
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
|
||||
<p>您可以在 <span class="app">Network</span> 首选项或通过 <span class="cli">ifconfig -a</span> 命令找到你的 <tt>wifi_device_path</tt>。</p>
|
||||
<p>下述是一些连接到 <i>wifitopia</i> 无线网络的示例。在这些示例中，我们假定您的无线网卡为 <tt>/dev/net/iprowifi3945/0</tt>。</p>
|
||||
<h4>列出无线网络：</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
|
||||
<h4>加入不安全的无线网络：</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
|
||||
<h4>加入 <a href="#wep-notes">WEP 加密</a> 无线网络：（ascii 密码）</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
|
||||
<h4>加入 <a href="#wep-notes">WEP 加密</a> 无线网络：（64位十六进制密码）</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
|
||||
<h4>断开无线网络：</h4>
|
||||
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="auto-connect" rel="nofollow" id="auto-connect">自动连接无线网络</a></h3>
|
||||
<p>为了使系统在每次启动时自动连接到一个给定 SSID 的网络，您可以按照下述格式在<tt>/boot/common/settings/network/wireless_networks</tt> 中指定无线网络和密码：</p>
|
||||
<pre>network wifitopia {
|
||||
password mypassword
|
||||
}</pre>
|
||||
<p>如果您并未创建该配置文件，系统将会自动连接到其发现的首个未加密网络。</p>
|
||||
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP 备注</strong></a></p>
|
||||
<ul>
|
||||
<li>64位的WEP使用了40位的密钥，也就是5个文本字符或者10个十六进制数字。</li>
|
||||
<li>128位的WEP是引用了104位密钥，也就是13个文本字符或者26个十六进制数字。</li>
|
||||
<li>十六进制位数字 = 0-9 和 A-F 十六个字符（在 <tt>ifconfig</tt> 中都带有前缀 "0x"）。</li>
|
||||
</ul>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="wpa" rel="nofollow" id="wpa">WPA加密</a></h3>
|
||||
<p><p>现在，Haiku 中还未有可用的 WPA 加密，尽管有一些 <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">成果</a> 已经带来了深远的影响。</p></p>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
|
||||
<p>为了安装用于 Intel ipw2100，Intel ipw2200/2225/2915，Broadcom 43xx 和 Marvell 88W8335 等的固件，您需要运行</p>
|
||||
<pre class="terminal">install-wifi-firmwares.sh
|
||||
</pre>
|
||||
<p>Intel ipw2100 和 ipw22xx 无需网络连接也可以进行安装，这是因为它们的许可条款允许 Haiku 发行原始的固件档案。但是在安装之前，它们确实需要用户的确认。Broadcom 43xx 和 Marvell 88W8335 需要活动的网络连接，这是因为包含固件的文件不能够随着 Haiku 一同发布。</p>
|
||||
<p>构建自己的Haiku镜像的人们可以在 <span class="cli">build/jam/UserBuildConfig</span> 中进行相应的改动。更多详细信息和关于无线网络的主题更新可以参阅 <a href="http://www.haiku-os.org/guides/wifi">有关的在线文档</a>。</p>
|
||||
<p>如果您确实需要下载该固件，而且在 Haiku 下也没有可用的网络连接，在线文档提供了一个<a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">shell 脚本</a>，它将会为你创建用于解压到 Haiku 的 <tt>/boot</tt> 文件夹下的Zip文件。之后，您就具有了所有 install-wifi-firmwares.sh 所需要的所有文件。</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_zh_CN.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -45,6 +45,7 @@
|
||||
<li><a href="welcome_hu.html"><img src="images/flags/hu.png" alt="" />Magyar</a></li>
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -103,8 +104,9 @@ Because of our binary and source compatibility, most BeOS applications run on Ha
|
||||
|
||||
<p>Besides using HaikuDepot, popular software repositories are:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haikuware.com" class="printurl">Haikuware</a></li>
|
||||
<li><a href="http://www.bebits.com" class="printurl">BeBits</a></li>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - maintains patches for ported software</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - hosts native BeOS and Haiku open source software projects in a github</li>
|
||||
</ul>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -46,6 +46,7 @@
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -99,12 +100,13 @@
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">Software installieren</a></h2>
|
||||
<p>Ein Großteil der vorhandenen Software kann mit der mit Haiku kommenden HaikuDepot Anwendung heruntergeladen und installiert werden.<br />
|
||||
Da Haiku sowohl binärkompatibel als auch code-kompatibel mit BeOS ist, laufen viele BeOS-Anwendungen auch direkt in Haiku. Die meisten von ihnen wurden für Haiku passend neu gepackt oder funktionieren auch ohne Änderungen. Weitere Informationen zur Installation neuer Anwendungen finden sich im Kapitel <a href="../userguide/de/applications.html">Anwendungen</a> im Haiku User Guide..</p>
|
||||
Da Haiku sowohl binärkompatibel als auch code-kompatibel mit BeOS ist, laufen viele BeOS-Anwendungen auch direkt in Haiku. Die meisten von ihnen wurden für Haiku passend neu gepackt oder funktionieren auch ohne Änderungen. Weitere Informationen zur Installation neuer Anwendungen finden sich im Kapitel <a href="../userguide/de/applications.html">Anwendungen</a> im Haiku User Guide.</p>
|
||||
|
||||
<p>Neben HaikuDepot existieren auch noch andere Software-Archive:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haikuware.com" class="printurl">Haikuware</a></li>
|
||||
<li><a href="http://www.bebits.com" class="printurl">BeBits</a></li>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - hier werden Patche für portierte Software gepflegt</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - ein GitHub für opensource Programme, die speziell für BeOS oder Haiku geschrieben wurden.</li>
|
||||
</ul>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -43,6 +43,7 @@
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
|
||||
@@ -99,8 +100,9 @@ Because of our binary and source compatibility, most BeOS applications run on Ha
|
||||
|
||||
<p>Besides using HaikuDepot, popular software repositories are:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haikuware.com" class="printurl">Haikuware</a></li>
|
||||
<li><a href="http://www.bebits.com" class="printurl">BeBits</a></li>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - maintains patches for ported software</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - hosts native BeOS and Haiku open source software projects in a github</li>
|
||||
</ul>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -46,6 +46,7 @@
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -104,8 +105,9 @@ Because of our binary and source compatibility, most BeOS applications run on Ha
|
||||
|
||||
<p>Besides using HaikuDepot, popular software repositories are:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haikuware.com" class="printurl">Haikuware</a></li>
|
||||
<li><a href="http://www.bebits.com" class="printurl">BeBits</a></li>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - maintains patches for ported software</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - hosts native BeOS and Haiku open source software projects in a github</li>
|
||||
</ul>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -45,6 +45,7 @@
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -54,6 +55,7 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Tämän sivun kotoistaminen ei ole vielä täydellinen. Siihen asti keskeneräiset osat käyttävät englanninkielistä alkuperäistekstiä.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Hakemisto</td></tr>
|
||||
@@ -101,8 +103,9 @@ Binaari- ja lähdekoodiyhteensopivuuden vuoksi monia BeOS-sovelluksia voidaan su
|
||||
|
||||
<p>HaikuDepot:in lisäksi suosittuja ohjelmistovarastoja ovat:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haikuware.com" class="printurl">Haikuware</a></li>
|
||||
<li><a href="http://www.bebits.com" class="printurl">BeBits</a></li>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - ylläpitää siirretyn ohjelmiston korjauksia</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - ylläpitää aitoja BeOS- ja Haiku open source -ohjelmistohankkeita githubissa</li>
|
||||
</ul>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -47,6 +47,7 @@
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -56,6 +57,7 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Cette page n'est pas encore entièrement traduite. Les parties non encore traduites seront en anglais.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
@@ -103,8 +105,9 @@
|
||||
|
||||
<p>Voici quelques sites populaires référençant un certain nombre de logiciels populaires :</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haikuware.com" class="printurl">Haikuware</a></li>
|
||||
<li><a href="http://www.bebits.com" class="printurl">BeBits</a></li>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - maintient les correctifs pour les logiciels supportés.</li>
|
||||
<li><a href="http://dev.osdrawer.net/" class="printurl">OsDrawer</a> - héberge des projets de logiciels open source natifs pour BeOS et Haiku</li>
|
||||
</ul>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -45,6 +45,7 @@
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -103,8 +104,9 @@ További információk a <a href="../userguide/hu/applications.html">Programok</
|
||||
|
||||
<p>A Raktáron kívül az alábbi népszerű oldalakon is találunk programokat:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haikuware.com" class="printurl">Haikuware</a></li>
|
||||
<li><a href="http://www.bebits.com" class="printurl">BeBits</a></li>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a> - PulkoMandy szoftverei</li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a> - Guest One raktár</li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org/" class="printurl">HaikuPorts</a> - portolt programok és frissítéseik</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - a BeOS és a Haiku nyílt forrású programjainak otthona</li>
|
||||
</ul>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -45,6 +45,7 @@
|
||||
<li><a href="welcome_pt_BR.html"><img src="images/flags/pt_BR.png" alt="" />Português (Brazil)</a></li>
|
||||
<li><a href="welcome_ca.html"><img src="images/flags/ca.png" alt="" />Català</a></li>
|
||||
<li><a href="welcome_pl.html"><img src="images/flags/pl.png" alt="" />Polski</a></li>
|
||||
<li><a href="welcome_ro.html"><img src="images/flags/ro.png" alt="" />Română</a></li>
|
||||
<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
@@ -103,8 +104,9 @@ Because of our binary and source compatibility, most BeOS applications run on Ha
|
||||
|
||||
<p>Besides using HaikuDepot, popular software repositories are:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haikuware.com" class="printurl">Haikuware</a></li>
|
||||
<li><a href="http://www.bebits.com" class="printurl">BeBits</a></li>
|
||||
<li><a href="http://pulkomandy.tk/~beosarchive/about.html" class="printurl">PulkoMandy's BeOS software archive</a></li>
|
||||
<li><a href="http://haiku.uwolke.ru/" class="printurl">Guest One's Haiku repository</a></li>
|
||||
<li><a href="http://fatelk.com/repo" class="printurl">Fat Elk Software</a></li>
|
||||
<li><a href="http://haikuports.org" class="printurl">HaikuPorts</a> - maintains patches for ported software</li>
|
||||
<li><a href="https://github.com/HaikuArchives" class="printurl">HaikuArchives</a> - hosts native BeOS and Haiku open source software projects in a github</li>
|
||||
</ul>
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user