Update userguide
This commit is contained in:
autonielx
@@ -109,7 +109,7 @@ Besides everything being more ugly and inconvenient, basically the same applies
|
||||
<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 remove the responsible Wifi driver from your Haiku installation (in <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
|
||||
<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>
|
||||
@@ -129,9 +129,10 @@ Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keybo
|
||||
<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/common/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 somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So 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 now 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. But again: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
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>
|
||||
|
||||
@@ -111,7 +111,7 @@ Außer dass alles etwas unansehnlicher und unbequemer ist, gilt eigentlich das g
|
||||
<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 aus dem System entfernen (in <span class="path"><acronym title="/boot/system/add-ons/kernel/drivers/bin">/boot/System/add-ons/kernel/drivers/bin</acronym></span>).</p>
|
||||
<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>
|
||||
@@ -119,7 +119,7 @@ Außer dass alles etwas unansehnlicher und unbequemer ist, gilt eigentlich das g
|
||||
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" 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">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>
|
||||
@@ -131,9 +131,11 @@ Im KDL kann es passieren, dass die Tastatur nicht mehr funktioniert. PS/2 Tastat
|
||||
<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"><acronym title="/boot/common/var/log/syslog">/boot/Allgemein/var/log/syslog</acronym></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 etwas langlebiger. Das ist standardmäßig aktiviert. "Etwas langlebiger" bedeutet, dass es einen Reset überlebt und direkt danach noch im Bootloader verfübar ist. Bootet man allerdings ein Betriebssystem (zumindest bei Haiku, wahrscheinlich aber bei allen), werden diese Informationen zerstört. Man muss beim Neustart also unbedingt das Bootloader Menü mittels gedrückter <span class="key">SHIFT</span> Taste aufrufen.<br />
|
||||
Dort sollte man im <span class="menu">Debug menu</span> jetzt 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>
|
||||
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>
|
||||
|
||||
@@ -108,7 +108,7 @@ Besides everything being more ugly and inconvenient, basically the same applies
|
||||
<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 remove the responsible Wifi driver from your Haiku installation (in <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
|
||||
<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>
|
||||
@@ -128,9 +128,10 @@ Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keybo
|
||||
<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/common/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 somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So 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 now 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. But again: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
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>
|
||||
|
||||
@@ -111,7 +111,7 @@ Besides everything being more ugly and inconvenient, basically the same applies
|
||||
<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 remove the responsible Wifi driver from your Haiku installation (in <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
|
||||
<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>
|
||||
@@ -131,9 +131,10 @@ Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keybo
|
||||
<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/common/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 somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So 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 now 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. But again: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
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>
|
||||
|
||||
@@ -53,6 +53,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>
|
||||
@@ -110,7 +111,7 @@ Paitsi että kaikki on rumempaa ja epämukavampaa, sama koskee myös sovellusvik
|
||||
<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 poistaa vastuullisen Wifi-ajurin Haiku-asennuksestasi (kansiossa <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
|
||||
<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">Käyttöjärjestelmäytimen viajäljitysalue - KDL</a></h3>
|
||||
@@ -129,10 +130,11 @@ Huomaa, että KDL-tilassa näppäimistösi ei ehkä toimi. PS/2-näppäimistöt
|
||||
|
||||
<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-alkuladattavasta 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/common/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> alkulataajan <span class="menu">Vianjäljitys</span>-valikossa tekee syslog-järjestelmälokista jossain määrin pysyvän muistissa. Valitsin on oletuksena käytössä. "Jossain määrin pysyvä" tarkoittaa, että se selviää järjestelmän nollauksesta ja on edelleen saatavilla kun siirryt alkulatausvalikkoon heti sen jälkeen. Järjestelmän alkulataus (Haiku ehdottomasti, muut todennäköisesti) tuhoavat kuitenkin tiedon. Joten sinun on siirryttävä alkulatausvalikkoon pitämällä alkulatauksen aikana alhaalla <span class="key">VAIHTO</span>-näppäintä.<br />
|
||||
Alkulataajan <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 tiedostontallentamisessa. 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 alkulatausvalikkoon. Mutta taas: Älä vahingossa alkulataa mitään käyttöjärjestelmää tai tiedot katoavat.</p>
|
||||
<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">Vikajäljitystulostus näytölle</a></h3>
|
||||
|
||||
@@ -14,6 +14,7 @@
|
||||
* Translators:
|
||||
* Loïc
|
||||
* Vincent Duvert
|
||||
* roptat
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -54,6 +55,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>
|
||||
@@ -120,7 +122,7 @@ La seconde ligne dit « <i>Welcome to Kernel Debugging Land…</i> ». Celle a
|
||||
</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 (dans <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
|
||||
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>
|
||||
@@ -141,9 +143,10 @@ ne posent pas de problème, les claviers USB connecté à un controleur UHCI ne
|
||||
<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/common/var/log/syslog</span>.Puisque l'écriture d'un fichier requiert un système qui fonctionne, les écritures les plus récente faites dans le journal ne peuvent pas être présentes quand un problème se produit dans le noyau (en particulier lors d'un redémarrage spontané ou d'une sessions KDL non recouvrable).</p>
|
||||
<p>L'option <span class="menu">Enable debug syslog</span> dans le menu <span class="menu">Debug menu</span> du chargeur de démarrage rend le journal légèrement persistant en mémoire. Cette option est activée par défaut. « légèrement persistant » signifie qu'il résistera à une réinitialisation et qu'il sera encore accessible quand vous entrerez dans le menu du chargeur de démarrage juste après. Noter qu'amorcer un système d'exploitation (Haiku sans aucun doute, et probablement les autres) détruit cette information. Alors vous devez rentrer dans le menu du chargeur de démarrage en maintenant la touche <span class="key">MAJ</span> enfoncée pendant le redémarrage.<br />
|
||||
Dans le menu du chargeur de démarrage <span class="menu">Debug menu</span>, vous devriez maintenant trouver les entrés <span class="menu">Display syslog from previous session</span> et <span class="menu">Save syslog from previous session</span>. La première, affiche le journal de la session précédente à écran. La dernière vous permet de l'enregistrer dans un fichier sur disque. Notez que pour le moment seuls les volumes FAT32 sont pris en charge pour l'enregistrement du fichier. Si vous souhaitez utiliser une clé USB, mais que vous l'avez branchée trop tard de sorte qu'elle n'a pas été prise en compte, vous pouvez réinitialiser la machine et entrer à nouveau dans le menu du chargeur de démarrage. Mais encore une fois : Ne démarrer aucun système d'exploitation accidentellement ou les données seront perdues.</p>
|
||||
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>
|
||||
|
||||
@@ -110,7 +110,7 @@ Attól, hogy kicsit kényelmetlen, minden épp úgy működik, mint a programhib
|
||||
<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. Plldá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 töröld a rendszerből (a <span class="path">/boot/system/add-ons/kernel/drivers/bin</span> mappából).</p>
|
||||
<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>
|
||||
@@ -130,9 +130,10 @@ Ne feledd, megeshet, hogy a billentyűzeted nem fog működni a KDL-ben. A PS/2
|
||||
<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/common/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">Select debug options</span> (hibakereső opciók) menüjében, akkor a rendszer a naplót megőrzi a memóriában. Alap esetben ez az opció engedélyezve van. A napló megőrzése annyit jelent, hogy a rendszer újraindításkor továbbra is elérhető marad a rendszertöltő menübe való belépéskor. Egy operációs rendszer betöltése (a Haiku biztosan, a többi pedig valószínűleg) törli ezt az információt. Tehát, be kell lépni indításkor a menübe a <span class="key">SHIFT</span> lenyomása közben.<br />
|
||||
A rendszertöltő menü <span class="menu">Select output options</span> (hibakereső opciók) menüjében most megjelenik további opció két is: <span class="menu">Display syslog from previous session</span> (a legutóbbi napló megjelenítése) és a <span class="menu">Save syslog from previous session</span> (a legutóbbi napló menté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>
|
||||
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>
|
||||
|
||||
@@ -109,7 +109,7 @@ Besides everything being more ugly and inconvenient, basically the same applies
|
||||
<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 remove the responsible Wifi driver from your Haiku installation (in <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
|
||||
<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>
|
||||
@@ -129,9 +129,10 @@ Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keybo
|
||||
<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/common/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 somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So 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 now 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. But again: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
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>
|
||||
|
||||
@@ -73,7 +73,7 @@
|
||||
<h1>バグの報告</h1>
|
||||
|
||||
<p>開発者はあらゆるハードウェア構成でテストすることは不可能です。さまざまな要因がオペレーティングシステムに影響を与えるため、私たちはユーザーの動作の報告などの情報に頼っています。そして Haiku はまだ幼いプロジェクトのため、バグに遭遇する可能性が高いです。私たちはバグを報告してくれるのを待っています。少しずつ Haiku を改善してもっと良いものにしていきませんか?</p>
|
||||
<p>私たちのバグトラッカーに有効に保つため、<a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">バグトラッカーにおけるエチケット</a>を絶対に守ってください。</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>
|
||||
@@ -86,16 +86,16 @@
|
||||
報告されていないことを確認したら、以下の情報を可能な限り多く提供してください。</p>
|
||||
<ul>
|
||||
<li><p>そのバグが最新バージョンでも再現するかを確認してみてください。最新バージョンのイメージは<a href="http://haiku-files.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>テストした環境の情報 (物理的なハードウェア、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>可能な限り正しく、実際に起きた挙動を説明し、その後自分が予測した挙動と、現在の挙動の問題を説明する</p></li>
|
||||
<li><p>再現する手順や準備。これは開発者が再現するために必要です。</p></li>
|
||||
<li><p>その他の情報。GUI 周りのバグやアプリケーションのバグならば、<span class="key">PRINT</span> キーを押下しスクリーンショットを取得してください。</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>
|
||||
<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>
|
||||
@@ -109,32 +109,33 @@
|
||||
<li><p>システムは kernel debugging land (KDL) に入ります。画面上部はクリアされいくつかの 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> と同じキーです) を押して、KDL に入れます。</p></li>
|
||||
<li><p>システムは正常に起動しません。起動中に再起動するか、起動中にどこかで止まるかのどちらかだと思います。(たとえば、ブートスクリーンでのいくつかのアイコンで) このケースでも <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</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 のインストール作業で取り除く (<span class="path">/boot/system/add-ons/kernel/drivers/bin</span> の中にあります) 等といったことです。</p>
|
||||
<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 キーボードは動作するでしょう。キーボードはショートカットでの起動で利用した一つに限られます。USB OHCI は現時点ではサポートされていません。</p>
|
||||
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><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 はシリアルポートと 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/common/var/log/syslog</span> に記録されます。ファイルの書き込みには動作しているシステムが必要であり、直近の出力が書き込まれず、カーネルの問題が起きた瞬間を記録していないかもしれません (おもに突然のリブートや続行不能な KDL のセッションで)。</p>
|
||||
<p>ブートローダーの <span class="menu">Debug menu</span> にある <span class="menu">Enable debug syslog</span> オプションは syslog を記録します。デフォルトでこのオプションは有効で、リブートがかかってもブートローダーメニューから直接アクセスできるようにします。オペレーティングシステム (Haiku 含めあらゆるシステム) を起動すると 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>
|
||||
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>
|
||||
@@ -148,15 +149,15 @@ syslog (system log の略称) はシステムに発生した事象の情報、KD
|
||||
<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>- <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>
|
||||
<tr><td colspan="3">- スクリーン上へのデバッグ出力 (ブート時のセーフモードオプション)</td></tr>
|
||||
</table>
|
||||
|
||||
<p>最初の 4 つのコマンドはターミナルに入力する。 <span class="cli"> > output.txt</span> をコマンドの最後に追加することで、"output.txt" というテキストファイルにターミナルの代わりに出力されるようになる。つまり、それをバグレポートやメールに添付することができるようになる。</p>
|
||||
<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>
|
||||
|
||||
@@ -63,107 +63,106 @@
|
||||
<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">País da Depuração do Kernel - KDL</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 Hardware/Driver</a><br />
|
||||
<a href="#next">Qual é o próximo?</a></td></tr>
|
||||
<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>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>
|
||||
<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>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>
|
||||
<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>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>
|
||||
<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://haiku-files.org/">available</a>.</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>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>
|
||||
<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>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>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>
|
||||
<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>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>
|
||||
<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>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>
|
||||
<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>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>
|
||||
<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 remove the responsible Wifi driver from your Haiku installation (in <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
|
||||
<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">País da Depuração do Kernel - 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>
|
||||
<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> (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>
|
||||
<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>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>
|
||||
<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/common/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 somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So 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 now 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. But again: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
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>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_BR/bootloader.html">Boot Loader</a>.</p>
|
||||
<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 Hardware/Driver</a></h2>
|
||||
<p>When dealing with a hardware/driver related bug, you should attach the following information as text files:</p>
|
||||
<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>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>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>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>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">Qual é o próximo?</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>
|
||||
<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>
|
||||
|
||||
@@ -109,7 +109,7 @@ Besides everything being more ugly and inconvenient, basically the same applies
|
||||
<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 remove the responsible Wifi driver from your Haiku installation (in <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
|
||||
<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>
|
||||
@@ -129,9 +129,10 @@ Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keybo
|
||||
<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/common/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 somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So 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 now 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. But again: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
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>
|
||||
|
||||
@@ -113,7 +113,7 @@
|
||||
<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 драйвер (из папки <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
|
||||
<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>
|
||||
@@ -135,9 +135,10 @@
|
||||
<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/common/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 somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So 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 now 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. But again: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
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>
|
||||
|
||||
@@ -111,7 +111,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>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 (v <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
|
||||
<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>
|
||||
@@ -131,9 +131,10 @@ Pamätajte, že v KDL vaša klávesnica nemusí fungovať. Klávesnice PS/2 fung
|
||||
<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/common/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 somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So 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 now 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. But again: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
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">Výstup ladenia na obrazovku</a></h3>
|
||||
|
||||
@@ -111,7 +111,7 @@ Besides everything being more ugly and inconvenient, basically the same applies
|
||||
<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 remove the responsible Wifi driver from your Haiku installation (in <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
|
||||
<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>
|
||||
@@ -131,9 +131,10 @@ Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keybo
|
||||
<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/common/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 somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So 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 now 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. But again: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
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>
|
||||
|
||||
@@ -109,7 +109,7 @@ Besides everything being more ugly and inconvenient, basically the same applies
|
||||
<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 remove the responsible Wifi driver from your Haiku installation (in <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
|
||||
<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>
|
||||
@@ -129,9 +129,10 @@ Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keybo
|
||||
<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/common/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 somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So 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 now 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. But again: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
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>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -12,6 +12,7 @@
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Paco Rivière
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -96,19 +97,17 @@
|
||||
<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>Because of our binary and source compatibility, many BeOS applications run on Haiku (you may have to install the optional package "beoscompatibility" for some programs, see below). After downloading a package, simply unzip it (double clicking opens <span class="app">Expander</span>) to <span class="path">/boot/apps/</span> and start the application from there.</p>
|
||||
<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>Popular software repositories are:</p>
|
||||
<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://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - maintains patches for ported software</li>
|
||||
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> - hosts native BeOS and Haiku open source software projects</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>
|
||||
|
||||
<p>There are also so-called Optional Packages, which are used by Haiku's build system. It is not intended for end users to manually extract and install them. Instead, a utility script is provided, <tt>installoptionalpackage</tt>. This script is meant to bridge the gap while Haiku's package management is still under construction. It will allow you to install most of the available Optional Packages.<br />
|
||||
You'll have to run a command in Terminal: <tt>installoptionalpackage -h</tt> explains its usage.</p>
|
||||
|
||||
<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>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -97,19 +97,17 @@
|
||||
<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>Da Haiku sowohl binärkompatibel als auch code-kompatibel mit dem BeOS ist, laufen viele BeOS-Anwendungen auch direkt in Haiku (für manche Programme muss das Optional Package "beoscompatibility" installiert werden, siehe unten). Nach dem Herunterladen eines Programm-Pakets muss es lediglich nach <span class="path"><acronym title="/boot/apps/">/boot/Anwendungen</acronym></span> entpackt (ein Doppelklick öffnet den <span class="app"><acronym title="Expander">Entpacker</acronym></span>) und von dort gestartet werden.</p>
|
||||
<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>Große Software-Verzeichnisse sind:</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://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - hier werden Erweiterungen für portiere Software bereitgehalten.</li>
|
||||
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> - Open Source Programme, die speziell für das BeOS oder Haiku geschrieben wurden.</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>
|
||||
|
||||
<p>Daneben existieren auch sogenannte "Optional Packages", die beim Erzeugen von Haiku Images zum Einsatz kommen. Sie sind nicht dazu bestimmt vom Benutzer manuell entpackt und installiert zu werden. Dafür gibt es aber das kleine Skript <tt>installoptionalpackage</tt>. Es dient als Lückenfüller solange noch an Haikus Paketmanagement gearbeitet wird. Mit ihm lassen sich viele der vorhandenen Optional Packages installieren.<br />
|
||||
Dazu benutzt man einen Befehl im Terminal: <tt>installoptionalpackage -h</tt> erklärt die verschiedenen Optionen.</p>
|
||||
|
||||
<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>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -93,19 +93,17 @@
|
||||
<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>Because of our binary and source compatibility, many BeOS applications run on Haiku (you may have to install the optional package "beoscompatibility" for some programs, see below). After downloading a package, simply unzip it (double clicking opens <span class="app">Expander</span>) to <span class="path">/boot/apps/</span> and start the application from there.</p>
|
||||
<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>Popular software repositories are:</p>
|
||||
<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://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - maintains patches for ported software</li>
|
||||
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> - hosts native BeOS and Haiku open source software projects</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>
|
||||
|
||||
<p>There are also so-called Optional Packages, which are used by Haiku's build system. It is not intended for end users to manually extract and install them. Instead, a utility script is provided, <tt>installoptionalpackage</tt>. This script is meant to bridge the gap while Haiku's package management is still under construction. It will allow you to install most of the available Optional Packages.<br />
|
||||
You'll have to run a command in Terminal: <tt>installoptionalpackage -h</tt> explains its usage.</p>
|
||||
|
||||
<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>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -13,6 +13,7 @@
|
||||
* Translators:
|
||||
* Oscar Carballal
|
||||
* miguel~1.mx
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -97,19 +98,17 @@
|
||||
<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>Debido a nuestra compatibilidad de código binario y código fuente, muchas aplicaciones de BeOS funcionan en Haiku (tal vez tenga que instalar el paquete "beoscompatibility" para algunos programas, vea debajo). Tras descargar un paquete, tan sólo debe descomprimirlo (dando doble clic se abre <span class="app">Expander</span>) con destino a <span class="path">/boot/apps/</span> y se inicia la aplicación desde ahí).</p>
|
||||
<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>Repositorios de software populares son:</p>
|
||||
<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://ports.haiku-files.org/" class="printurl">HaikuPorts</a> mantiene actualizaciones y parches para las aplicaciones portadas.</li>
|
||||
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> hospeda los proyectos de software de código libre para BeOS y Haiku.</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>
|
||||
|
||||
<p>También están los así llamados Paquetes opcionales, los cuales se utilizan por el sistema de construcción de Haiku. No se persigue que los usuarios finales los extraigan e instalen manualmente. En su lugar, un script de utilidades se proporciona, <tt>installoptionalpackage</tt>. La intención de este script es de llenar el vacío mientras el mantenimiento de paquetes de Haiku esté todavía en construcción. Este script permite instalar la mayoría de los Paquetes opcionales disponibles.<br />
|
||||
Al correrse el siguiente comando en una Terminal: <tt>installoptionalpackage -h</tt> se explica su uso.</p>
|
||||
|
||||
<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>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -12,6 +12,7 @@
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Karvjorm
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -52,6 +53,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>
|
||||
@@ -94,18 +96,17 @@
|
||||
<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>Binaari- ja lähdekoodiyhteensopivuuden vuoksi monia BeOS-sovelluksia voidaan suorittaa Haikussa (sinun on ehkä asennettava valinnainen paketti ”beoscompatibility” joitakin ohjelmia varten, katso alla). Yksinkertaisesti pura pakkaus latauksen jälkeen (hiiren kaksoisnapsautus avaa <span class="app">Laajentaja</span>n) kansioon <span class="path">/boot/apps/</span> ja käynnistä sovellus sieltä.</p>
|
||||
<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/fi/applications.html">Applications</a>.</p>
|
||||
|
||||
<p>Suosittuja ohjelmistovarastoja ovat:</p>
|
||||
<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://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - ylläpitää siirretyn ohjelmiston korjauksia</li>
|
||||
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> - ylläpitää aitoja BeOS- ja Haiku open source -ohjelmistohankkeita</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>
|
||||
|
||||
<p>Haikun rakentamisjärjestelmässä käytetään myös niin sanottuja valinnaisia pakkauksia. Ei ole tarkoitus, että loppukäyttäjät manuaalisesti purkavat ja asentavat pakkaukset. Sen sijaan tarkoitusta varten on apuohjelmaskripti <tt>installoptionalpackage</tt>. Tämän skriptin tarkoitus on täyttää aukko, joka johtuu siitä, että Haikun pakettihallinta on vielä suunnitteilla. Skripti sallii sinun asentaa useimmat saatavilla olevat valinnaiset pakkaukset.<br />Sinun on suoritettava komento Pääteikkunassa: <tt>installoptionalpackage -h</tt> selittää sen käytön.</p>
|
||||
|
||||
<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>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -14,6 +14,7 @@
|
||||
* Vincent Duvert
|
||||
* Loïc
|
||||
* Humdinger
|
||||
* Wabouz
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -77,7 +78,7 @@
|
||||
<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 sur un système en production. Les données que vous manipulez pourraient être altérées, corrompues ou tout simplement détruites.</div>
|
||||
<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>
|
||||
@@ -97,22 +98,16 @@
|
||||
<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>Grâce à notre compatibilité binaire et source avec BeOS, de nombreuses applications écrites pour ce système fonctionne sous Haiku. Après avoir téléchargé un paquet, décompressez le (un double-clic lancera <span class="app">Expander</span>) dans <span class="path">/boot/apps/</span> et démarrez l'application depuis de ce dossier.</p>
|
||||
<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 :</p>
|
||||
<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://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - maintient les correctifs pour les logiciels portés</li>
|
||||
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> - héberge des projets de logiciels open source natifs pour BeOS et Haiku</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>
|
||||
|
||||
<p>Il y a aussi les paquets dits optionnels, qui sont utilisés par le système de compilation d'Haiku. Les utilisateurs finaux ne sont pas sensés les extraire manuellement pour les installer. Toutefois, un script utilitaire est fourni : <tt>installoptionalpackage</tt>.
|
||||
Ce script est destiné à combler les lacunes du gestionnaire de paquets en cours de construction.
|
||||
Il vous permettra d'installer la plus part des paquets optionnels disponibles.<br />
|
||||
Vous devrez saisir une ligne de commande dans le Terminal :
|
||||
<tt>installoptionalpackage -h</tt> explique son utilisation.</p>
|
||||
|
||||
<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>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -12,6 +12,7 @@
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Dancsó Róbert
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -95,19 +96,18 @@
|
||||
<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 bináris kompatibilitás miatt sok BeOS-ra íródott program futtatható Haiku-n (néhány programhoz szükséges lehet a "beoscompatibility" csomag telepítése). A csomag letöltése után egyszerűen csak ki kell csomagolni azt (a csomagon történő dupla kattintással megnyílik a <span class="app">Kicsomagoló</span>) a <span class="path">/boot/apps/</span> mappába, majd onnan elindítani.</p>
|
||||
<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>Népszerű oldalak:</p>
|
||||
<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://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - portolt programok és frissítéseik</li>
|
||||
<li><a href="http://dev.osdrawer.net/" class="printurl">OsDrawer</a> - a BeOS és a Haiku nyílt forrású programjainak otthona</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>
|
||||
|
||||
<p>Ezen kívül vannak különféle kiegészítő csomagok, melyek automatizált telepítéséhez a Haiku egy szkriptet biztosít: <tt>installoptionalpackage</tt>. Ez a szkript csak egy ideiglenes megoldás addig, amíg a Haiku csomagkezelője el nem készül. Ezzel lehetőséged van az összes elérhető kiegészítő csomag telepítésére.<br />
|
||||
Ha segítségre van szükséged, akkor a Terminálban add ki a következő parancsot: <tt>installoptionalpackage -h</tt>.</p>
|
||||
|
||||
<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>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -12,6 +12,7 @@
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* MichaelPeppers
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -96,19 +97,17 @@
|
||||
<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>Grazie alla compatibilità, sia a livello di binari, sia a livello di codice, molte applicazioni per BeOS funzionano in Haiku (potresti aver bisogno di installare il pacchetto opzionale "beoscompatibility" per alcuni programmi, vedi sotto). Dopo aver scaricato un pacchetto, basta estrarlo (un doppio click su di esso fa aprire l'<span class="app">Expander</span>) in <span class="path">/boot/apps/</span> e far partire l'applicazione da lì.</p>
|
||||
<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>I siti più utili per cercare applicazioni per Haiku sono:</p>
|
||||
<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://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - si occupa delle patch per le applicazioni non-native</li>
|
||||
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> - ospita progetti di applicazioni open source native per BeOS e Haiku</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>
|
||||
|
||||
<p>Ci sono anche i cosiddetti Pacchetti Opzionali, che sono usati dal build system di Haiku. Non è nostra intenzione far estrarre e installare questi pacchetti manualmente all'utente finale, perciò, è stato incluso uno script, <tt>installoptionalpackage</tt>. Lo script è pensato per coprire questo gap mentre si sta lavorando su come gestire i pacchetti in Haiku. Questo script ti permetterà di installare la maggior parte dei Pacchetti Opzionali disponibili.<br />
|
||||
Dovrai far partire il comando nel terminale; <tt>installoptionalpackage -h</tt> spiega il suo utilizzo.</p>
|
||||
|
||||
<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>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -14,6 +14,7 @@
|
||||
* iwaim
|
||||
* Shota Fukumori
|
||||
* mt
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -71,7 +72,7 @@
|
||||
<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>
|
||||
<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>
|
||||
@@ -97,28 +98,25 @@
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">ソフトウェアを追加する</a></h2>
|
||||
<p>だいたいの BeOS 向けアプリケーションは Haiku でもバイナリとソースコードの互換性から動くと思われます (ただし、オプションの "beoscompatibility" パッケージのインストールが必要です)。パッケージをダウンロードし、<span class="path">/boot/apps/</span> に unzip (ダブルクリックで、<span class="app">ファイル解凍</span>が開きます) することでアプリケーションを起動できます。</p>
|
||||
<p>ほとんどの利用可能なソフトウェアは、Haiku に付属のアプリケーション、HaikuDepot でダウンロードおよびインストールできます。<br />ほとんどの BeOS 向けアプリケーションは Haiku でもバイナリとソースコードの互換性から動作すると思われます。その多くは Haiku 用に再パッケージされているか、修正なしに動作します。新しいアプリケーションのインストールに関する追加の情報はユーザーガイドの<a href="../userguide/jp/applications.html">アプリケーション</a>の章に見つかります。</p>
|
||||
|
||||
<p>有名なソフトウェアのレポジトリの一覧:</p>
|
||||
<p>HaikuDepot の使用以外の、有名なソフトウェアレポジトリの一覧:</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://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - 移植されたソフトウェアやパッチのメンテナンスを行っています</li>
|
||||
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> - ネイティブ BeOS と Haiku のソフトウェアを提供しています</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>
|
||||
|
||||
<p>Haiku のビルドシステムで使われているオプショナルパッケージというものがあります。これはユーザーが手動で展開・インストールを行うために用意はされていません。そのかわり、<tt>installoptionalpackage</tt> というユーティリティスクリプトが用意されています。このスクリプトは未完成の Haiku のパッケージ管理システムの穴を埋めるためのもので、たくさんのオプショナルパッケージのインストールを容易にするために用意されています。<br />
|
||||
以下のコマンドをターミナルで実行することで使い方を知ることができます: <tt>installoptionalpackage -h</tt></p>
|
||||
|
||||
<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>
|
||||
<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>Haiku は再実装のため、API は BeOS R5 とまだ同じです (少しの追加があります)。そのため、Be Book にあるドキュメントはまだ有用な情報です。かつての Be Inc. の所有物の権利を持つ ACCESS に感謝します。私たちは Be Book のコピーを提供することを許可されました。<br />BeOS API から離れたところ、および Haiku 固有の追加事項は Haiku Book に集められています。</p>
|
||||
|
||||
<p>以下は、読者が始めるのに手助けになると思われる追加のドキュメントです。</p>
|
||||
<ul>
|
||||
@@ -132,7 +130,7 @@
|
||||
<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>
|
||||
<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>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -13,6 +13,7 @@
|
||||
* Translators:
|
||||
* tiagoms
|
||||
* Adriano Duarte
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -95,19 +96,17 @@
|
||||
<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>Por causa da sua compatibilidade de código e binária, muitos aplicativos BeOS executam no Haiku (deve-se instalar o pacote opcional "beoscompatibility" para alguns programas, veja abaixo). Após baixar um pacote, simplesmente descompacte-o (duplo clique abre o <span class="app">Expansor</span>) para a pasta <span class="path">/boot/apps/</span> e inicie o aplicativo de lá.</p>
|
||||
<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>Repositórios populares de software para o Haiku são:</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://www.haikuware.com" class="printurl">Haikuware</a></li>
|
||||
<li><a href="http://www.bebits.com" class="printurl">BeBits</a></li>
|
||||
<li><a href="http://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - mantém patches para software portado</li>
|
||||
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> - abriga projetos de sotftware BeOS e Haiku, de código aberto, nativos.</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>
|
||||
|
||||
<p>Existem também os chamados Pacotes Opcionais, os quais são usados pelo sistema de desenvolvimento do Haiku. Estes não são direcionados para usuários finais extraí-los e instalá-los manualmente. Ao invés disso, é fornecido um script utilitário, <tt>installoptionalpackage</tt>. Este script é um paliativo enquanto o gerenciador de pacotes do Haiku está em construção. Ele permitirá instalar a maioria dos Pacotes Opcionais disponíveis.<br />
|
||||
Executar no Terminal o comando: <tt>installoptionalpackage -h</tt> esclarece o seu uso.</p>
|
||||
|
||||
<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>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -94,19 +94,17 @@
|
||||
<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>Because of our binary and source compatibility, many BeOS applications run on Haiku (you may have to install the optional package "beoscompatibility" for some programs, see below). After downloading a package, simply unzip it (double clicking opens <span class="app">Expander</span>) to <span class="path">/boot/apps/</span> and start the application from there.</p>
|
||||
<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>Popular software repositories are:</p>
|
||||
<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://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - maintains patches for ported software</li>
|
||||
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> - hosts native BeOS and Haiku open source software projects</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>
|
||||
|
||||
<p>There are also so-called Optional Packages, which are used by Haiku's build system. It is not intended for end users to manually extract and install them. Instead, a utility script is provided, <tt>installoptionalpackage</tt>. This script is meant to bridge the gap while Haiku's package management is still under construction. It will allow you to install most of the available Optional Packages.<br />
|
||||
You'll have to run a command in Terminal: <tt>installoptionalpackage -h</tt> explains its usage.</p>
|
||||
|
||||
<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>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -99,20 +99,17 @@
|
||||
<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 бинарно и на уровне исходных кодов совместима с BeOS, то многие BeOS-приложения работают и в ней (для некоторых программ возможно потребуется установить пакет "beoscompatibility"). Загрузив архив с программой, просто распакуйте его (достаточно двойного клика для открытия архива в <span class="app">Expander</span>) в <span class="path">/boot/apps/</span>, и оттуда же запускайте это приложение.</p>
|
||||
<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>Популярные каталоги программ:</p>
|
||||
<p>Besides using HaikuDepot, popular software repositories are:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haikuware.com" class="printurl">Haikuware</a> - сайт с программами, ориентированными на Haiku.</li>
|
||||
<li><a href="http://www.bebits.com" class="printurl">BeBits</a> - самый популярный каталог программ для BeOS (в последнее время и для Haiku).</li>
|
||||
<li><a href="http://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - библиотеки, необходимые для портирования приложений.</li>
|
||||
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> - хранилище для разрабатываемых приложений с открытым исходным кодом для BeOS и Haiku.</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>
|
||||
|
||||
<p>Также существуют так называемые дополнительные пакеты (Optional Packages), которые используются при сборке Haiku. Они не предназначены для скачивания и установки конечными пользователями, однако имеется сервисный скрипт, <tt>installoptionalpackage</tt>, которым можно воспользоваться пока менеджер пакетов для Haiku находится в разработке. Он позволит вам установить большинство доступных дополнительных пакетов.<br />
|
||||
Для этого нужно выполнить команду в терминале:
|
||||
<tt>installoptionalpackage -h</tt> описывает как им пользоваться.</p>
|
||||
|
||||
<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>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -12,6 +12,7 @@
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* helix84
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -95,18 +96,17 @@
|
||||
<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ď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 (je možné, že budete musieř nainštalovať voliteľný balík „beoscompatibility“). Niektoré programy nájdete nižšie. Po stiahnutí balíka ho jednoducho rozbaľte (dvojité kliknutie otvorí <span class="app">Rozbaľovač</span>) do <span class="path">/boot/apps/</span> a odtiaľ aplikáciu spustite.</p>
|
||||
<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/sk/applications.html">Applications</a>.</p>
|
||||
|
||||
<p>Populárne zdroje softvéru sú:</p>
|
||||
<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://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - spravuje záplaty portovaného softvéru</li>
|
||||
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> - hosťuje natívne open source projekty pre BeOS a Haiku</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>
|
||||
|
||||
<p>Tiež existujú tzv. Voliteľné balíky, ktoré používa zostavovací systém Haiku. Nie sú určené na to, aby ich koncoví používatelia ručne rozbaľovali a inštalovali. Namiesto toho poskytujeme pomocný skript <tt>installoptionalpackage</tt>. Tento skript má pomôcť preklenúť obdobie, kým správu balíkov Haiku zatiaľ len tvoríme. Umožní vám nainštalovať väčšinu dostupných Voliteľných balíkov.<br /> Budete musieť spustiť nasledovný príkaz v Termináli, ktorý vysvetľuje jeho použitie: <tt>installoptionalpackage -h</tt></p>
|
||||
|
||||
<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>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -12,6 +12,7 @@
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* deejam
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -96,18 +97,17 @@
|
||||
<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>På grund av vår binära källkods-kompatibilitet fungerar många BeOS-program i Haiku (du kan behöva installera det valfria paketet "beoscompatibility" för vissa program, se nedan). Efter nedladdning av ett paket, packa upp det (dubbelklicka för att öppna <span class="app">Expanderaren</span>) till <span class="path">/boot/apps/</span> och starta programmet därifrån.</p>
|
||||
<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>Populära programvarutjänster är:</p>
|
||||
<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://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - tillhandahåller och underhåller uppdateringar för portad mjukvara</li>
|
||||
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> - tillhandahåller öppen-källkodsmjukvara för BeOS och Haiku</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>
|
||||
|
||||
<p>Det finns även valfria paket, som används av Haiku's byggsystem. Det är inte meningen att användare själva skall packa upp och installera dessa. I stället finns ett hjälpskript, <tt>installoptionalpackage</tt>. Detta skript är till för att underlätta pakethanteringen under tiden som Haiku's pakethanteringssystem är under utveckling. Det erbjuder dig att installera dom flesta av dom tillgängliga valfria paketen.<br />Du behöver köra ett kommando i Terminalen: <tt>installoptionalpackage -h</tt> förklarar hur den används.</p>
|
||||
|
||||
<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>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -12,6 +12,7 @@
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* totish
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -96,19 +97,17 @@
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">Встановлення додаткових програм</a></h2>
|
||||
<p>Так як ОС бінарно і на рівні коду сумісна з BeOS, багато з додатків працюють у Haiku (для деяких програм доведеться встановити пакет "beoscompatibility" , дивись нижче). Після закачки просто розпакуйте його (подвійним кліком для відкриття архіву в <span class="app">Expander</span>) в<span class="path">/boot/apps/</span> і запускайте додаток.</p>
|
||||
<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>Популярні сховища програм:</p>
|
||||
<p>Besides using HaikuDepot, popular software repositories are:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.haikuware.com" class="printurl">Haikuware</a> - сайт з додатками, що орієнтовані на Haiku</li>
|
||||
<li><a href="http://www.bebits.com" class="printurl">BeBits</a> - найпопулярніший каталог програм для BeOS ( останнім часом і для Haiku).</li>
|
||||
<li><a href="http://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - бібліотеки, що необхідні для портування додатків.</li>
|
||||
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> - сховище для додатків з відкритим кодом підBeOS і Haiku, що знаходяться на стадії розробки.</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>
|
||||
|
||||
<p>Також існують так звані додаткові пакети (Optional Packages), що використовуються при побудові Haiku. Вони не призначені для скачування і встановлення кінцевим користувачем, однак є сервісний скрипт <tt>installoptionalpackage</tt>, котрим можна скористатись поки менеджер пакетів знаходиться в стані розробки. Він дозволить встановити більшість додаткових пакетів.<br />
|
||||
Досить у терміналі набрати команду: <tt>installoptionalpackage -h</tt> , що описує як ним зкористатись.</p>
|
||||
|
||||
<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>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2012, Haiku. All rights reserved.
|
||||
* Copyright 2008-2013, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -12,6 +12,7 @@
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Pengphei Han
|
||||
* Humdinger
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -52,6 +53,7 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>索引</td></tr>
|
||||
@@ -95,19 +97,17 @@
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">安装更多的程序</a></h2>
|
||||
<p>由于二进制库和源代码的兼容性，许多BeOS程序可以在Haiku系统中运行。（您可能需要为某些程序安装“beoscompatibility”附加软件包，详情见下文）。 下载软件包之后，将其解压（双击打开 <span class="app">档案管理器</span>）到 <span class="path">/boot/apps/</span> ，然后从这里启动程序。</p>
|
||||
<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/zh_CN/applications.html">Applications</a>.</p>
|
||||
|
||||
<p>非常有名的软件仓库有：</p>
|
||||
<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://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - 包含了移植程序的补丁</li>
|
||||
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> - 主持原生的BeOS和Haiku开源程序项目</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>
|
||||
|
||||
<p>还有一些所谓的附加软件包，它们主要用于Haiku的构建系统，终端用户并不需要对它们进行解压和安装。相应的，系统提供了一个工具脚本 <tt>installoptionalpackage</tt> 来安装附加软件包。由于Haiku的包管理软件仍在开发之中，该脚本主要起到一个暂时的过渡作用。它允许您安装大部分可用的附加软件包。<br />
|
||||
您可以在终端中输入命令： <tt>installoptionalpackage -h</tt> 来查看它的用法。</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="wifi">Haiku 无线网络</a></h2>
|
||||
|
||||
@@ -54,6 +54,7 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>索引</td></tr>
|
||||
@@ -114,7 +115,7 @@
|
||||
<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中删除相关的无线网络驱动（位于 <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>）。</p>
|
||||
<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>
|
||||
@@ -133,11 +134,11 @@
|
||||
|
||||
<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/common/var/log/syslog</span>。由于写入文件需要系统处于运行状态，因此当内核出现问题时（尤其是，系统自动重启，或者无法持续KDL会话），最新的输出信息可能无法写入日志文件。</p>
|
||||
<p>引导程序的<span class="menu">Debug menu</span> 中的<span class="menu">Enable debug syslog</span> 选项可以使系统日志在内存中稍微持久的存在。默认情况下，它是启用的。 “稍微持久” 意味着，它可以在一次机器重置之后仍然存在，在之后直接进入引导程序菜单时仍然可以访问。尽管如此，引导一个操作系统将会（Haiku 肯定会，其他的可能会）损坏该信息。 所以您需要在引导时按下 <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> 两个入口。前者将系统日志显示于屏幕，后者允许您将其保存到硬盘。需要注意的是，目前只有FAT32卷支持保存该文件。如果您使用USB磁盘，但是插入晚了，可能它将不被识别；您可以重置机器，然后再次进入引导程序菜单。但是还要注意：不要无意的启动任何操作系统，否则数据将会丢失。</p>
|
||||
<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>
|
||||
|
||||
Reference in New Issue
Block a user