Update userguide and welcome pages.
This is the first userguide export on the Postgres-based translation tool (previously it used MySQL), so please double-check it extra carefully. (I spotted a few minor problems in the export and fixed the relevant bugs already.)
This commit is contained in:
waddlesplash
@@ -87,7 +87,7 @@ After you have established that it's a unique bug, make your information as accu
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (x86_gcc2, x86_64). 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>
|
||||
@@ -95,17 +95,17 @@ After you have established that it's a unique bug, make your information as accu
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Application bugs</a></h2>
|
||||
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
|
||||
<p>When an application crashed, you can either save a report or write a core file (both saved to the Desktop) that you can attach to a bugreport, or you can evoke the <a href="../../userguide/ca/applications/debugger.html">Debugger</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Server bugs</a></h2>
|
||||
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
|
||||
<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 the Debugger will be started in text-mode, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and Debugger 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.<br />
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> and then press the power button once to try shutting cleanly down.</p>
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> or <span class="cli">write-core</span> for a core file, and then press the power button once to try shutting cleanly down. If the power button doesn't work, there are also the commands <span class="cli">shutdown</span> and <span class="cli">reboot</span>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Kernel bugs</a></h2>
|
||||
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<p>Kernel bugs are usually the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<ul>
|
||||
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
|
||||
<li><p>The system reboots spontaneously.</p></li>
|
||||
@@ -117,13 +117,13 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>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> (<span class="key">SysReq</span> being the <span class="key">Print</span> key, normally).<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, with USB keyboards it depends on the type of USB controller (UHCI/EHCI). Generally, the keyboard should be plugged into the port directly, not via any hubs. In some circumstances, the keyboard only works if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
|
||||
<tr><td><span class="cli">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace. If the system entered KDL on its own 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 class="onelinetop"><span class="cli">co</span> (aka <span class="cli">continue</span>)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
|
||||
</table>
|
||||
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
@@ -132,7 +132,7 @@ 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 />
|
||||
<p><b>This is the preferred method for extracting 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 />
|
||||
@@ -141,7 +141,7 @@ In the boot loader's <span class="menu">Debug menu</span> you should find the en
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">On screen debug output</a></h3>
|
||||
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog</span> option doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../userguide/ca/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
@@ -152,13 +152,13 @@ One or more pages of text will display on the screen, only the last few lines ne
|
||||
<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>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, see <a href="#syslog">Syslog</a> above, 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 colspan="3">- On screen debug output (a safe mode boot time option, see <a href="#onscreen">above</a>).</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>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 "<tt>output.txt</tt>" that you can attach to your bug report or email.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">What's next?</a></h2>
|
||||
|
||||
@@ -12,8 +12,8 @@
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <[email protected]>
|
||||
* Translators:
|
||||
* Matthias
|
||||
* Humdinger
|
||||
* Matthias
|
||||
* taos
|
||||
*
|
||||
-->
|
||||
@@ -89,7 +89,7 @@ Nach dieser Überprüfung sollte man so genau wie möglich den Fehler beschreibe
|
||||
<ul>
|
||||
<li><p>Der Fehler sollte mit einer aktuellen Version von Haiku reproduzierbar sein. Zum Testen gibt es installierbare <a href="http://download.haiku-os.org">Nightly Images</a>.</p></li>
|
||||
<li><p>Wie wurde Haiku verwendet (auf echter Hardware oder virtualisiert unter VMWare, QEMU oder ähnlichem)?</p></li>
|
||||
<li><p>Welche Haiku-Versionsnummer wurde verwendet? Die Version ist unter <span class="menu">Über Haiku...</span> im Deskbar Menü zu finden. Wie genau Haiku kompiliert wurde (gcc2, gcc4, gcc2hybrid, gcc4hybrid), ist ebenfalls von Interesse. Die runterladbaren Images sind entsprechend benannt; Leute, die sich ihr Haiku selber zusammenbauen, sollten wissen wie sie das gemacht haben.</p></li>
|
||||
<li><p>Welche Haiku-Versionsnummer wurde verwendet? Die Version ist unter <span class="menu">Über Haiku...</span> im Deskbar Menü zu finden. Wie genau Haiku kompiliert wurde (x86_gcc2, x86_64), ist ebenfalls von Interesse. Die runterladbaren Images sind entsprechend benannt; Leute, die sich ihr Haiku selber zusammenbauen, sollten wissen wie sie das gemacht haben.</p></li>
|
||||
<li><p>Der Fehler sollte so präzise wie möglich beschrieben werden. Welches Verhalten wurde erwartet und was wurde statt dessen beobachtet?</p></li>
|
||||
<li><p>Wann tritt der Fehler auf? Nur mit einer Schritt-für-Schritt Anleitung können die Entwickler den Bug nachstellen und beheben.</p></li>
|
||||
<li><p>An den Fehlerbericht sollten so viele Informationen wie möglich angehängt werden. Handelt es sich um einen Bug in der grafischen Oberfläche oder einer der Anwendungen, ist ein Bildschirmfoto mittels der <span class="key">DRUCK</span> Taste hilfreich.</p></li>
|
||||
@@ -97,13 +97,13 @@ Nach dieser Überprüfung sollte man so genau wie möglich den Fehler beschreibe
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Bugs in Anwendungen</a></h2>
|
||||
<p>Stürzt eine Anwendung ab, sollte man den Debugger aus dem erscheinenden Hinweisfenster aufrufen. Dadurch wird ein Terminal mit gdb (dem GNU Debugger) geöffnet. Gibt man dort <span class="cli">bt</span> ein, wird ein sogenannter "backtrace" erstellt, der komplett (auch mit dem Teil bevor <span class="cli">bt</span> eingegeben wurde) mit an die Fehlermeldung angehängt werden sollte.</p>
|
||||
<p>Stürzt eine Anwendung ab, kann man entweder einen 'Bericht' speichern oder eine 'Core-Datei' schreiben (beides erscheint auf dem Desktop), die man dann an einen Bugreport hängen kann oder man ruft den Debugger auf. Siehe dazu das Kapitel <a href="../../userguide/de/applications/debugger.html">Debugger</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Bugs in Servern</a></h2>
|
||||
<p>Stürzen lebenswichtige Server wie der App Server, der Registrar oder der Input Server ab, bekommt man nicht den gewöhnlichen Crash-Hinweis zu sehen. Stattdessen wird der gesamte Bildschirm weiß und der gdb wird gestartet, der seine Ausgabe direkt auf den Bildschirm schreibt. Unter Umständen kann man immer noch die Maus bewegen, die daraufhin das Weiß und die gdb Ausgabe übermalt. Noch laufende Anwendungen, wie ProcessController oder die Uhr in der Deskbar, tun das vielleicht auch noch.<br />
|
||||
<p>Stürzen lebenswichtige Server wie der App Server, der Registrar oder der Input Server ab, bekommt man nicht den gewöhnlichen Crash-Hinweis zu sehen. Stattdessen wird der gesamte Bildschirm weiß und der Debugger wird im Textmodus gestartet, der seine Ausgabe direkt auf den Bildschirm schreibt. Unter Umständen kann man immer noch die Maus bewegen, die daraufhin das Weiß und die Debugger Ausgabe übermalt. Noch laufende Anwendungen, wie ProcessController oder die Uhr in der Deskbar, tun das vielleicht auch noch.<br />
|
||||
Außer dass alles etwas unansehnlicher und unbequemer ist, gilt eigentlich das gleiche wie für Bugs in Anwendungen. Am wichtigsten ist das sichern eines "backtrace" mittels <span class="cli">bt</span>. Weil man den Text ja nicht mehr irgendwohin kopieren kann, müsste man die Ausgabe per Kamera festhalten.<br />
|
||||
Je nachdem was genau abgestürzt ist, kann man auch probieren mit dem Befehl <span class="cli">save-report</span> einen Crash-Report auf dem Desktop zu speichern. Danach sollte man einmal auf den Powerknopf drücken, um zu versuchen den Rechner sauber herunterzufahren.</p>
|
||||
Je nachdem was genau abgestürzt ist, kann man auch probieren mit dem Befehl <span class="cli">save-report</span> einen 'Crash-Bericht' oder per <span class="cli">write-core</span> eine 'Core-Datei' auf dem Desktop zu speichern. Danach sollte man einmal auf den Powerknopf drücken, um zu versuchen den Rechner sauber herunterzufahren. Funktioneirt ther Powerknopf nicht, gibt es noch die Befehle <span class="cli">shutdown</span> und <span class="cli">reboot</span> zum Ausschalten bzw. für einen Neustart.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Bugs im Kernel</a></h2>
|
||||
@@ -119,11 +119,11 @@ Je nachdem was genau abgestürzt ist, kann man auch probieren mit dem Befehl <sp
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>Stürzt das System nicht von selbst ins KDL, kann man das auch absichtlich mit der Tastenkombination <span class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span> erreichen.<br />
|
||||
Im KDL kann es passieren, dass die Tastatur nicht mehr funktioniert. PS/2 Tastaturen gehen immer, USB Tastaturen an UHCI Controllern nur wenn man vorher schonmal per Tastenkombination das KDL betreten hat. USB OHCI wird zur Zeit noch gar nicht unterstützt.</p>
|
||||
<p>Stürzt das System nicht von selbst ins KDL, kann man das auch absichtlich mit der Tastenkombination <span class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span> erreichen (<span class="key">SysReq</span> ist normalerweise die <span class="key">Druck</span> Taste).<br />
|
||||
Im KDL kann es passieren, dass die Tastatur nicht mehr funktioniert. PS/2 Tastaturen gehen immer, bei USB Tastaturen kommt es auf die Art des USB Controllers an (UHCI/EHCI). Generell sollte die Tastatur direkt an einem Port hängen, nicht über einen Hub. Ein bestimmten Fällen kann es sein, dass die Tastatur nur funktioniert wenn man vorher schonmal per Tastenkombination das KDL betreten hat. USB OHCI wird zur Zeit noch gar nicht unterstützt.</p>
|
||||
<p>Das KDL ist eine Art Konsole. Es lassen sich Befehle eingeben, die Informationen über das System ausgeben. Folgende Befehle sind von besonderen Interesse:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (auch "sc")</td><td> </td><td>Zeigt einen "backtrace" (oder auch "stack crawl") wo genau der Fehler aufgetreten ist. Ist das System von selbst ins KDL gefallen, sollte man diesen Befehl unbedingt ausführen.</td></tr>
|
||||
<tr><td><span class="cli">bt</span> (auch <span class="cli">sc</span>)</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>
|
||||
@@ -155,10 +155,10 @@ Auf dem Bildschirm werden einige Seiten Text ausgegeben, von denen aber nur die
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>Eine detaillierte Auflistung aller vorhandener Hardware inklusive "vendor id" und "pci id"; ähnlich den Befehlen <span class="cli">lshw</span> und <span class="cli">lspci</span> unter Linux.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Bei Fehlern im Zusammenhang mit USB, ähnlich dem Befehlt <span class="cli">lsusb</span> unter Linux.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Die zentrale Log-Datei von Haiku. Mit dem Befehl <span class="cli">open</span> kann das Log im Texteditor auf eine sinnvolle Länge gekürzt werden.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Die zentrale Log-Datei von Haiku, siehe <a href="#syslog">Syslog</a> weiter oben, entspricht der Debug Bildschirmausgabe. Mit dem Befehl <span class="cli">open</span> kann das Log im Texteditor auf eine sinnvolle Länge gekürzt werden.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Eine Auflistung aller verwendeten Treiber.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Nur im <i>Kernel Debugging Land</i> (siehe weiter oben). Es zeigt eine Liste aller verwendeter "Interrupts". Wenn sich mehrere Geräte zuviele von ihnen teilen, ist das schlecht.</td></tr>
|
||||
<tr><td colspan="3">- "On screen debug output" (die Bootloader Debug Option zur Ausgabe auf dem Bildschirm).</td></tr>
|
||||
<tr><td colspan="3">- "On screen debug output" (die Bootloader Debug Option zur Ausgabe auf dem Bildschirm, siehe <a href="#onscreen">weiter oben</a>).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>Die ersten vier dieser Befehle sind im Terminal einzugeben. Mit dem Zusatz "<span class="cli"> > output.txt</span>" an den Befehl wird dessen Ausgabe in die Datei "output.txt" gespeichert, die dann an den Fehlerbericht angehängt werden kann.</p>
|
||||
|
||||
@@ -86,7 +86,7 @@ After you have established that it's a unique bug, make your information as accu
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (x86_gcc2, x86_64). 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>
|
||||
@@ -94,17 +94,17 @@ After you have established that it's a unique bug, make your information as accu
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Application bugs</a></h2>
|
||||
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
|
||||
<p>When an application crashed, you can either save a report or write a core file (both saved to the Desktop) that you can attach to a bugreport, or you can evoke the <a href="../../userguide/en/applications/debugger.html">Debugger</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Server bugs</a></h2>
|
||||
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
|
||||
<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 the Debugger will be started in text-mode, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and Debugger 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.<br />
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> and then press the power button once to try shutting cleanly down.</p>
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> or <span class="cli">write-core</span> for a core file, and then press the power button once to try shutting cleanly down. If the power button doesn't work, there are also the commands <span class="cli">shutdown</span> and <span class="cli">reboot</span>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Kernel bugs</a></h2>
|
||||
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<p>Kernel bugs are usually the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<ul>
|
||||
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
|
||||
<li><p>The system reboots spontaneously.</p></li>
|
||||
@@ -116,13 +116,13 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>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> (<span class="key">SysReq</span> being the <span class="key">Print</span> key, normally).<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, with USB keyboards it depends on the type of USB controller (UHCI/EHCI). Generally, the keyboard should be plugged into the port directly, not via any hubs. In some circumstances, the keyboard only works if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
|
||||
<tr><td><span class="cli">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace. If the system entered KDL on its own 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 class="onelinetop"><span class="cli">co</span> (aka <span class="cli">continue</span>)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
|
||||
</table>
|
||||
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
@@ -131,7 +131,7 @@ 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 />
|
||||
<p><b>This is the preferred method for extracting 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 />
|
||||
@@ -140,7 +140,7 @@ In the boot loader's <span class="menu">Debug menu</span> you should find the en
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">On screen debug output</a></h3>
|
||||
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog</span> option doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../userguide/en/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
@@ -151,13 +151,13 @@ One or more pages of text will display on the screen, only the last few lines ne
|
||||
<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>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, see <a href="#syslog">Syslog</a> above, 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 colspan="3">- On screen debug output (a safe mode boot time option, see <a href="#onscreen">above</a>).</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>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 "<tt>output.txt</tt>" that you can attach to your bug report or email.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">What's next?</a></h2>
|
||||
|
||||
@@ -12,8 +12,8 @@
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <[email protected]>
|
||||
* Translators:
|
||||
* miguel~1.mx
|
||||
* kervas
|
||||
* miguel~1.mx
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -90,7 +90,7 @@ Tras haber establecido que es un fallo nuevo, haga que su información sea lo m
|
||||
<ul>
|
||||
<li><p>Intente reproducir su problema en la revisión actual de Haiku. Hay imagenes pre-construidas para fines de prueba <a href="http://download.haiku-os.org">disponibles</a> en línea.</p></li>
|
||||
<li><p>Incluya información básica tal como dónde está probando a Haiku (sobre hardware real, en VMWare, en QEMU, etc.).</p></li>
|
||||
<li><p>Mencione cuál revisión está corriendo. Puede encontrar esta información en <span class="menu">Acerca de Haiku…</span> del menú del Deskbar. También mencione cual versión de Haiku está poniendo a prueba (gcc2, gcc4, gcc2hybrid, gcc4hybrid). Las imagenes descargables tienen su nombre de esa forma, para una imagen auto-construida deberá saber cómo la construyó.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (x86_gcc2, x86_64). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describa el problema que esté experimentando. Intente ser tan preciso como pueda: describa el comportamiento actual, y el comportamiento esperado.</p></li>
|
||||
<li><p>Describa qué pasos necesita realizar para exponer el fallo. Esto ayudará a los desarrolladores a reproducir el fallo.</p></li>
|
||||
<li><p>Adjunte tanta información como tenga. Si es un fallo de interfaz de usuario, o un fallo en una de las aplicaciones, intente hacer una captura de pantalla presionando la tecla <span class="key">Impr pant</span>.</p></li>
|
||||
@@ -98,17 +98,17 @@ Tras haber establecido que es un fallo nuevo, haga que su información sea lo m
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Fallos de programas</a></h2>
|
||||
<p>Cuando falla una aplicación, debería invocar el depurador desde la alerta que aparece. Esto abrirá una ventana de Terminal con gdb (el depurador GNU) ejecutandose en ella. Al ingresar <span class="cli">bt</span>, creará un "backtrace", del cual debe copiar su contenido completo (incluyendo la parte antes que ingresara la orden <span class="cli">bt</span>) y adjuntarlo al reporte de fallo.</p>
|
||||
<p>When an application crashed, you can either save a report or write a core file (both saved to the Desktop) that you can attach to a bugreport, or you can evoke the <a href="../../userguide/es/applications/debugger.html">Debugger</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Fallos 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 />
|
||||
<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 the Debugger will be started in text-mode, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and Debugger 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.<br />
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> and then press the power button once to try shutting cleanly down.</p>
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> or <span class="cli">write-core</span> for a core file, and then press the power button once to try shutting cleanly down. If the power button doesn't work, there are also the commands <span class="cli">shutdown</span> and <span class="cli">reboot</span>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Fallos de núcleo (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>Kernel bugs are usually the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<ul>
|
||||
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
|
||||
<li><p>The system reboots spontaneously.</p></li>
|
||||
@@ -120,11 +120,11 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Zona de depuración del núcleo - KDL</a></h3>
|
||||
<p>Si el sistema no ha entrado al KDL por sí sólo, puede ingresar deliberadamente invocando la combinación de teclas <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (siendo <span class="key">SysReq</span> (PetSis) el mismo botón que <span class="key">Impr pant</span> en la mayoría de los teclados).<br />
|
||||
Tome nota que en el KDL su teclado podría dejar de funcionar. Los teclados PS/2 siempre lo hacen, los teclados USB conectados via controladores UHCI lo hacen solo si ha ingresado al KDL a través del método abreviado al menos una vez anteriormente. Actualmente no se soporta OHCI USB.</p>
|
||||
<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> (<span class="key">SysReq</span> being the <span class="key">Print</span> key, normally).<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, with USB keyboards it depends on the type of USB controller (UHCI/EHCI). Generally, the keyboard should be plugged into the port directly, not via any hubs. In some circumstances, the keyboard only works if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>El KDL mismo es un tipo de intérprete de comandos. Uno puede ejecutar ordenes que despliegan información sobre el sistema. Los siguientes comandos pueden ser de interés:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (también conocido como sc)</td><td> </td><td>muestra el "backtrace", detallando dónde exactamente sucedió el fallo. Si el sistema entró en el KDL por sí sólo, ingrese ese.</td></tr>
|
||||
<tr><td><span class="cli">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>muestra el "backtrace", detallando dónde exactamente sucedió el fallo. Si el sistema entró en el KDL por sí sólo, ingrese ese.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>mostrará el uso de interruptores manejados y no manejados de hardware.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (lo mismo que continue)</td><td> </td><td>saldrá del depurador del kernel y continuará la operación del sistema, si es posible.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reinicia el sistema inmediatamente. Perderá toda la información no guardada y tal vez alguna que haya guardado, pero que todavía no se ha escrito en el disco.</td></tr>
|
||||
@@ -135,7 +135,7 @@ Tome nota que en el KDL su teclado podría dejar de funcionar. Los teclados PS/2
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Historial de Eventos de Sistema</a></h3>
|
||||
<p><b>This is the preferred method for gaining information from a non-booting system.</b><br />
|
||||
<p><b>This is the preferred method for extracting 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 />
|
||||
@@ -144,7 +144,7 @@ In the boot loader's <span class="menu">Debug menu</span> you should find the en
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">Salida de depuración en pantalla</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 />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog</span> option doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../userguide/es/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
@@ -155,10 +155,10 @@ One or more pages of text will display on the screen, only the last few lines ne
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>un listado detallado de su hardware, incluyendo las IDs de fabricante y dispositivo PCI, similar a los comandos de Linux <span class="cli">lshw</span> y <span class="cli">lspci</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>asumiendo que el conflicto se relacione con USB, esto es similar a <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>el historial primario de sucesos de sistema utilizado por Haiku, parecido a la pantalla de depuración durante el arranque. Con el comando <span class="cli">open</span> se puede acortar la parte relevante de los sucesos de sistema en un editor de textos.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, see <a href="#syslog">Syslog</a> above, 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>muestra una lista de todos los controladores utilizados.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>sólo disponible en la <i>Zona de depuración del núcleo (kernel)</i> (vea abajo). Muestra el uso de interruptores. No deberían haber muchos que esten compartidos por diferentes dispositivos.</td></tr>
|
||||
<tr><td colspan="3">Salida de depuración a pantalla (una opción de modo a prueba de fallas en el momento de arranque)</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option, see <a href="#onscreen">above</a>).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>Las primeras cuatro ordenes se pueden ingresar en la Terminal. Agregue un <span class="cli"> > output.txt</span> tras una orden, y será canalizada a un archivo de texto llamado "output.txt" que puede adjuntar al reporte de fallos o correo electrónico.</p>
|
||||
|
||||
@@ -12,8 +12,8 @@
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <[email protected]>
|
||||
* Translators:
|
||||
* Karvjorm
|
||||
* Humdinger
|
||||
* Jorma Karvonen
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -25,7 +25,7 @@
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
<div><span>Käyttäjäopas</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
@@ -65,10 +65,10 @@
|
||||
<a href="#app">Sovellusviat</a><br />
|
||||
<a href="#server">Palvelinviat</a><br />
|
||||
<a href="#kernel">Käyttöjärjestelmäydinviat</a><br />
|
||||
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
|
||||
<a href="#kdl">Käyttöjärjestelmäytimen vianjäljitysalue - KDL</a><br />
|
||||
<a href="#syslog">Järjestelmäloki</a><br />
|
||||
<a href="#onscreen">Vikajäljitystulostus näytölle</a><br />
|
||||
<a href="#hardware">Laitteisto-/Ajuriviat</a><br />
|
||||
<a href="#hardware">Laitteisto-/ajuriviat</a><br />
|
||||
<a href="#next">Mitä seuraavaksi?</a></td></tr>
|
||||
</table>
|
||||
|
||||
@@ -80,7 +80,7 @@
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Trac-tiilin saaminen</a></h2>
|
||||
<p>Jos luot vikalipun, sinulla on oltava tili <a href="http://dev.haiku-os.org/register" title="Registröidy Haikun vikajäljittäjään">Haikun vikajäljittäjässä</a>.<br />
|
||||
Luotaessa uutta tiliä muista <b>tarjota sähköpostiosoitteesi</b>, koska se on välttämätön lipun muokkausoikeusien saamiseksi. Tarkista varmuuden vuoksi <b>roskapostikansiosi</b> pian jälkeenpäin, koska kaikki tärkeät vahvistussähköpostiviestit usein päättyvät sinne.</p>
|
||||
Luotaessa uutta tiliä muista <b>tarjota sähköpostiosoitteesi</b>, koska se on välttämätön lipun muokkausoikeuksien saamiseksi. Tarkista varmuuden vuoksi <b>roskapostikansiosi</b> pian jälkeenpäin, koska kaikki tärkeät vahvistussähköpostiviestit usein päättyvät sinne.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Vikailmoituksen luominen</a></h2>
|
||||
@@ -89,7 +89,7 @@ Varmista sen jälkeen kun olet esitellyt ainutlaatuisen vian, että tietosi ovat
|
||||
<ul>
|
||||
<li><p>Yritä toistaa havaitsemasi vika nykyisessä Haikun korjausversiossa. Esirakennetut tiedostovedokset testaustarkoituksiin löytyvät <a href="http://haiku-files.org/">täältä</a>.</p></li>
|
||||
<li><p>Sisällytä mukaan perustietoa siitä, kuinka testaat Haikua (todellisessa tietokoneessa, VMWare-ympäristössä, QEMU-emulaattorissa, jne.).</p></li>
|
||||
<li><p>Mainitse, mitä korjausversiota käytät. Löydät tämän tiedon Työpöytäpalkin valikosta <span class="menu">Haikusta...</span>. Mainitse myös, että minkälaisella rakennusjärjestelmällä (gcc2, gcc4, gcc2hybrid, gcc4hybrid) testaamasi järjestelmä on rakennettu. Ladattavat tiedostovedokset on nimetty niiden mukaan. Itse rakennetuissa tiedostovedoksissa tiedät itse, kuinka se on rakennettu.</p></li>
|
||||
<li><p>Mainitse, mitä korjausversiota käytät. Löydät tämän tiedon Työpöytäpalkin valikosta <span class="menu">Haikusta...</span>. Mainitse myös, että minkälaisella rakennusjärjestelmällä (x86_gcc2, x86_64) testaamasi järjestelmä on rakennettu. Ladattavat tiedostovedokset on nimetty niiden mukaan. Itse rakennetuissa tiedostovedoksissa tiedät itse, kuinka se on rakennettu.</p></li>
|
||||
<li><p>Kuvaile kokemasi pulma. Yritä olla niin tarkka kuin voit: kuvaile todellinen käyttäytyminen, ja se käyttäytyminen, jota odotit.</p></li>
|
||||
<li><p>Kuvaile, mitä vaiheita pitää suorittaa vian paljastumiseksi. Tämä auttaa kehittäjiä toistamaan vian.</p></li>
|
||||
<li><p>Liitä mukaan niin paljon tietoja, kuin sinulla on. Jos kyseessä on graafisen käyttöliittymän vika, tai vika yhdessä sovelluksessa, yritä tehdä näytönkaappaus painamalla <span class="key">PRINT SCREEN</span>-näppäintä.</p></li>
|
||||
@@ -97,13 +97,13 @@ Varmista sen jälkeen kun olet esitellyt ainutlaatuisen vian, että tietosi ovat
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Sovellusviat</a></h2>
|
||||
<p>Kun sovellus kaatuu, sinun pitäisi kutsua vikajäljitintä hälytysikkunasta, joka ponnahtaa näkyviin. Tämä avaa Pääteikkunan gdb-ohjelmalla (GNU-vikajäljitin), joka käynnistyy. Kirjoittamalla <span class="cli">bt</span>, luot "paluujäljen". jonka sinun pitäisi kopioida kokonaisuudessaan (mukaan lukien se osa, joka tuli näkyviin, ennen kuin kirjoitit <span class="cli">bt</span>-komennon) ja liittää se vikalippuun.</p>
|
||||
<p>Kun sovellus kaatuu, voit joko tallentaa ilmoituksen tai kirjoittaa ydintiedoston (molemmat tallentuvat Työpöydälle), jonka voit liittää vikailmoitukseen, tai voit kutsua <a href="../../userguide/fi/applications/debugger.html">Vianjäljittäjän</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Palvelinviat</a></h2>
|
||||
<p>Kun elintärkeät palvelimet, kuten app-, registrar- tai input-palvelin kaatuvat, et näe tavallista kaatumishälytystä. Sen sijaan koko näyttö muuttuu valkoiseksi ja gdb-istunto käynnistyy ja sen tuloste ilmaantuu näytölle. Todennäköisesti pystyt yhä liikuttamaan hiiren kohdistinta, mikä ylikirjoittaa valkoisen ja gdb-tulosteen näytöllä. Yhä vielä toimivat sovellukset (kuten Prosessivalvonta tai Työpöytäpalkin kello) saattavat myös kirjoittaa vikajäljittimen tulosteen päälle näytölle.<br />
|
||||
<p>Kun elintärkeät palvelimet, kuten app-, registrar- tai input-palvelin kaatuvat, et näe tavallista kaatumishälytystä. Sen sijaan koko näyttö muuttuu valkoiseksi ja gdb-istunto käynnistyy tekstitilassa ja vianjäljittimen tuloste ilmaantuu suoraan näytölle. Todennäköisesti pystyt yhä liikuttamaan hiiren kohdistinta, mikä ylikirjoittaa valkoisen ja gdb-tulosteen näytöllä. Yhä vielä toimivat sovellukset (kuten Prosessivalvonta tai Työpöytäpalkin kello) saattavat myös kirjoittaa vikajäljittimen tulosteen päälle näytölle.<br />
|
||||
Paitsi että kaikki on rumempaa ja epämukavampaa, sama koskee myös sovellusvikoja. Tärkeintä on hankkia paluujälki (<span class="cli">bt</span>-komento). Sinun on ehkä otettava valokuva näytöstä digitaalikameralla, koska et voi kopioida tekstiä mihinkään.<br />
|
||||
Riippuen siitä mikä kaatui voit yrittää tallentaa kaatumisilmoituksen Työpöydälle <span class="cli">save-report</span>-komentorivisovelluksella ja painaa virtapainiketta kerran, mikä sulkee järjestelmän puhtaasti.</p>
|
||||
Riippuen siitä mikä kaatui voit yrittää tallentaa kaatumisilmoituksen Työpöydälle <span class="cli">save-report</span>-komentorivisovelluksella tai ydintiedoston <span class="cli">write-core</span>-komentorivisovelluksella ja painaa virtapainiketta kerran, mikä yrittää sulkea järjestelmän siististi. Jos virtapainike ei toimi, niin on myös olemassa <span class="cli">shutdown</span>- ja <span class="cli">reboot</span>-komentorivisovellukset.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Käyttöjärjestelmäydinviat</a></h2>
|
||||
@@ -111,21 +111,21 @@ Riippuen siitä mikä kaatui voit yrittää tallentaa kaatumisilmoituksen Työp
|
||||
<ul>
|
||||
<li><p>Järjestelmä siirtyy Käyttöjärjestelmän vianjäljitysmaahan (KDL) omasta tahdostaan. Näytön ylempi osa muuttuu valkoiseksi ja sille tulostetaan useita rivejä tekstiä. Toinen rivi sanoo "<i>Welcome to Kernel Debugging Land...</i>". Sen yläpuolella oleva rivi kertoo välittömän syyn siirtymisestä KDL:ään.</p></li>
|
||||
<li><p>Järjestelmä alkulatautuu itsestään.</p></li>
|
||||
<li><p>Järjestelmä jäätyy täysin. Et voi siirtää hiiren osoitinta ja mikään sovellus ei enää toimi. Tärkeä testi siinä tilanteessa on, että pystytkö siirtymään KDL:ään pikanäppäimellä <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> mikä on <span class="key">PRINT</span> useimmissa näppäimistöissä). Odota vähintään minuutti nähdeksesi, että tapahtuuko jotain.</p></li>
|
||||
<li><p>Järjestelmä jäätyy täysin. Et voi siirtää hiiren osoitinta ja mikään sovellus ei enää toimi. Tärkeä testi siinä tilanteessa on, että pystytkö siirtymään KDL:ään pikanäppäimellä <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> on sama kuin <span class="key">PRINT</span> useimmissa näppäimistöissä). Odota vähintään minuutti nähdeksesi, että tapahtuuko jotain.</p></li>
|
||||
<li><p>Järjestelmä ei alkulataa oikein. Se voi alkulatautua itsestään tai pysähtyä jossain vaiheessa (esimerkiksi jonkun alkaulatausnäytön kuvakkeen kohdalla). Yritä jälkimmäisessä tapauksessa myös <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>Koko järjestelmä tai joku laitteiston osa ei toimi kunnolla. Esimerkiksi se voisi olla hyvin hidas, tapahtuu virheitä, tai jokin ei toimi ollenkaan. Jos jokin laite ei toimi ollenkaan, ensimmäinen ilmeinen tarkistus on, että tukeeko Haiku sitä ylimalkaan tällä hetkellä (esim.: kysy sähköpostituslistalta tai foorumilta).</p></li>
|
||||
</ul>
|
||||
<p>Huomaa että vaikka ainoastaan viimeinen kohta tuntuu viittaavan laittoistovikaan, kaikki muutkin oireet voivat johtua myös viasta laitteistoajurissa. Jos sinulla on epäilyjä, että mikä laitteiston osa tai vastaava ajuri aiheuttaa pulmia, tarkista, että eroaako tilanne, jos poistat tai otat pois käytöstä laitteen tai ajurin. Esimerkiksi jos epäilet Wifi-verkkoa, saatat huomata, että BIOS-asetuksissa voidaan ottaa se pois käytöstä. Tai jos ei, niin voisit merkata vastuullisen Wifi-ajurin mustalle listalle Haiku-asennuksestasi (katso <a href="../../userguide/fi/bootloader.html">Käynnistyslataaja</a>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Käyttöjärjestelmäytimen viajäljitysalue - KDL</a></h3>
|
||||
<p>Jos järjestelmä ei ole siirtynyt KDL-tilaan itsestään, voit tehdä sen tarkoituksellisesti pikanäppäimillä <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Huomaa, että KDL-tilassa näppäimistösi ei ehkä toimi. PS/2-näppäimistöt toimivat aina, UCHI-ohjaimen kautta yhdistetyt USB-näppäimistöt toimivat vain jos jos KDL-tilaan on siirrytty näppäimistön avulla vähintään kerran. USB OHCI ei tällä hetkellä tueta.</p>
|
||||
<a id="kdl" name="kdl">Käyttöjärjestelmäytimen vianjäljitysalue - KDL</a></h3>
|
||||
<p>Jos järjestelmä ei ole siirtynyt KDL-tilaan itsestään, voit tehdä sen tarkoituksellisesti pikanäppäimillä <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span>-näppäin on normaalisti <span class="key">Print</span>-näppäin).<br />
|
||||
Huomaa, että KDL-tilassa näppäimistösi ei ehkä toimi. PS/2-näppäimistöt toimivat aina, USB-näppäimistöjen kohdalla se riippuu USB-ohjaimen (UCHI/ECHI) tyypistä. Yleensä näppäimistöt olisi liitettävä suoraan porttiin, ei minkään keskittimen (hub) kautta. Joissakin tilanteissa näppäimistöt toimivat vain jos KDL-tilaan on siirrytty pikanäppäinten avulla vähintään kerran. USB OHCI-näppäimistöä ei tällä hetkellä tueta.</p>
|
||||
<p>KDL itse on erään tyyppinen komentotulkki. Käyttäjä voi suorittaa komentoja, jotka tulostavat tietoja järjestelmästä. Seuraavat komennot saattavat olla kiinnostavia:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (eli sc)</td><td> </td><td>Tulostaa paluujäljen. Jos järjestelmä siirtyy KDL-tilaan omasta tahdostaan, kirjoita aina tämä komento.</td></tr>
|
||||
<tr><td><span class="cli">bt</span> (eli <span class="cli">sc</span>)</td><td> </td><td>Tulostaa paluujäljen. Jos järjestelmä siirtyy KDL-tilaan omasta tahdostaan, kirjoita aina tämä komento.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Näyttää käsitellyt ja käsittelemättömät laitteistokeskeytykset.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (eli jatka)</td><td> </td><td>Jättää järjestelmävianjäljittimen ja jatkaa normaalia järjestelmän toimintaa, jos se on mahdollista.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (eli <span class="cli">continue</span>)</td><td> </td><td>Jättää järjestelmävianjäljittimen ja jatkaa normaalia järjestelmän toimintaa, jos se on mahdollista.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Alkulataa järjestelmän välittömästi. Menetät kaiken tallentamattomat tiedot ja vieläpä nuo, jotka on tallennettu, mutta joita ei ole vielä kirjoitettu levylle.</td></tr>
|
||||
</table>
|
||||
<p>Katso lisätietoja artikkelista <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Tervetuloa vikajäljitysalueelle</a>.</p>
|
||||
@@ -148,16 +148,16 @@ Valitse lopuksi <span class="menu">Paluu päävalikkoon</span> ja sitten <span c
|
||||
Yksi tai useampia tekstisivuja näytetään näytölle, vain muutama harva viimeinen rivi on liitettävä vikailmoituslippuun. Tässä on lisätietoja <a href="../../userguide/fi/bootloader.html">Alkulataaja</a>sta.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Laitteisto/ajuriviat</a></h2>
|
||||
<a id="hardware" name="hardware">Laitteisto-/ajuriviat</a></h2>
|
||||
<p>Kun ollaan tekemisissä laitteisto- tai ajurivikojen kanssa, sinun pitäisi liittää seuraavia tietoja tekstitiedostona:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>Yksityiskohtainen luettelo laitteistostasi, mukaanlukien valmistaja- ja pci-tunnisteet, samanlainen kuin Linuxin <span class="cli">lshw</span> ja <span class="cli">lspci</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Otaksutaan sen olevan USB:hen liittyvä pulma, sama kuin <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Haikun ensisijainen järjestelmäloki, sukua alkulatauksen aikaiselle vianjäljitykselle. Komennolla <span class="cli">open</span> voit poimia olennaisen osan järjestelmälokista testieditorissa.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Haikun käyttämään ensisijaiseen järjestelmälokiin tutustumiseksi katso yllä <a href="#syslog">Syslog</a>, joka on kuin vianjäljitys näytölle käynnistyksen aikana. Komennolla <span class="cli">open</span> voit poimia olennaisen osan järjestelmälokista testieditorissa.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Luettelee kaikki käytetyt ajurit.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Käytettävissä vain <i>Käyttöjärjestelmäytimen vianjäljitysalueella</i> (katso yllä). Näyttää keskeytysten käytön. Eri laitteiden kesken jaettuja keskeytyksiä ei pitäisi olla montaa.</td></tr>
|
||||
<tr><td colspan="3">- Vianjäljitystulostus näytölle (alkulatausvalitsin turvatilassa).</td></tr>
|
||||
<tr><td colspan="3">- Vianjäljitystulostuksessa näytölle (turvatilan käynnistysvalitsin, katso <a href="#onscreen">yllä</a>).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>Neljä ensimmäistä komentoa kirjoitetaan Pääteikkunassa. Lisää <span class="cli"> > output.txt</span> komennon jälkeen ja se putkitetaan tekstitiedostoon, jonka nimi on "output.txt", jonka voit liittää vikailmoitukseesi tai sähköpostiviestiisi.</p>
|
||||
|
||||
@@ -12,10 +12,10 @@
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <[email protected]>
|
||||
* Translators:
|
||||
* Loïc
|
||||
* Vincent Duvert
|
||||
* roptat
|
||||
* Humdinger
|
||||
* Loïc
|
||||
* roptat
|
||||
* Vincent Duvert
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -78,7 +78,7 @@
|
||||
<h1>Signaler les bogues</h1>
|
||||
|
||||
<p>Comme il est impossible pour nos développeurs de tester toutes les combinaisons de matériel, ni tous les cas de figure pouvant interagir avec le système d'exploitation, nous comptons sur les utilisateurs pour nous dire si les choses fonctionnent pour eux. puisque Haiku est encore tout jeune, il est très probable que vous rencontriez des bogues. Nous vous remercions de bien vouloir prendre le temps de nous les signaler. Ensemble, nous pourrons, petit à petit, améliorer Haiku.</p>
|
||||
<p>Afin que le suivi de nos bogues reste efficace, il est essentiel de respecter l'<a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">étiquette de suivi des bogues</a>.</p>
|
||||
<p>Afin que le suivi de nos bogues reste efficace, il est essentiel de respecter l’<a href="https://dev.haiku-os.org/wiki/BugTrackerEtiquette">étiquette de suivi des bogues</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Obtenir un compte Trac</a></h2>
|
||||
@@ -92,25 +92,23 @@ Après vous être assuré que votre bogue est unique, obtenez des informations p
|
||||
<ul>
|
||||
<li><p>Essayez de reproduire votre problème avec la version actuelle d'Haiku. Des <a href="http://haiku-files.org/">images préfabriqués</a> sont disponible à cet usage.</p></li>
|
||||
<li><p>Indiquez comment vous testez Haiku (sur machine réelle, dans VMware, dans Qemu…)</p></li>
|
||||
<li><p>Indiquez quelle révision vous utilisez. Vous pouvez trouver cette information dans le menu « <i>About Haiku…</i> » de la Deskbar.
|
||||
N'oubliez pas de mentionner le type de construction dont est issu le système que vous testez (gcc2, gcc4, gcc2hybrid, gcc4hybrid).
|
||||
<li><p>Indiquez quelle révision vous utilisez. Vous pouvez trouver cette information dans le menu <span class="menu">À propos de Haiku...</span> de la Deskbar.
|
||||
N'oubliez pas de mentionner le type de construction dont est issu le système que vous testez (x86_gcc2, x86_64).
|
||||
Les images téléchargeables sont nommés en conséquence. Si vous avez construit l'image vous-même, vous devriez savoir comment vous l'avez compilé.</p></li>
|
||||
<li><p>Décrivez le problème que vous rencontrez. soyez aussi précis que possible : décrivez le comportement réel, et celui que vous attendiez.</p></li>
|
||||
<li><p>Décrivez les actions que vous avez effectuées avant de faire ressortir le bogue. Cela permettra aux développeurs de le reproduire.</p></li>
|
||||
<li><p>Attachez au rapport le plus d’informations possibles. Si le bogue concerne l’interface graphique ou une application, essayez de faire une capture d’écran à l'aide de la la touche <span class="key">IMPR ÉCRAN</span>.</p></li>
|
||||
<li><p>Attachez au rapport le plus d’informations possibles. Si le bogue concerne l’interface graphique ou une application, essayez de faire une capture d’écran à l'aide de la la touche <span class="key">Impr Écran</span>.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Bogues logiciels</a></h2>
|
||||
<p>Lorsqu'une application se plante, vous devez appeler le débogueur depuis le message d'alerte qui s'affiche.
|
||||
Une fenêtre de Terminal devrait s'ouvrir avec gdb (le débogueur GNU) lancé à l'intérieur.
|
||||
En saisissant <span class="cli">bt</span>, vous obtiendrez ainsi une trace de la « pile d'appel » (<i>backtrace</i>) que vous devez joindre en intégralité (y compris la partie précédant l'appel à la commande <span class="cli">bt</span>) à votre rapport de bogue.</p>
|
||||
<p>Lorsqu'une application plante, vous pouvez soit enregistrer un rapport, soit écrire un fichier de base (les deux seront sauvegardés sur le Bureau) afin de les joindre à un rapport de bug. Vous pouvez aussi invoquer le <a href="../../userguide/fr/applications/debugger.html">Debugger</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Bogues dans les serveurs</a></h2>
|
||||
<p>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.<br />
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> and then press the power button once to try shutting cleanly down.</p>
|
||||
<p>Lorsque les serveurs vitaux comme le serveur d'application, de registre ou d'entrées plantent, vous ne verrez pas l'alerte de crash habituelle. À la place, l'écran sera nettoyé à blanc et une session gdb sera lancée, qui affichera directement ses restitutions à l'écran. Il se pourrait que vous soyez toujours à même de déplacer la souris, qui dessinera alors par dessus l'écran blanc de gdb. Les applications encore en cours (comme ProcessController ou l'horloge dans la barre de Bureau) pourrait également continuer à se dessiner au dessus de la sortie du débogueur à l'écran.<br />
|
||||
Bien que tout soit plus laid et peu commode, les même fondamentaux que pour déboguer les applications s'appliquent. Le plus important est de fournir une trace de la pile d'appel à l'aide de la commande <span class="cli">bt</span> (backtrace). Comme vous ne serez pas en mesure de copier le texte, Vous devrez peut-être prendre une photo de l'écran avec un appareil photo numérique<br />
|
||||
En fonction de ce qui s'est planté, vous pouvez essayer d'enregistrer un rapport d'accident sur le Bureau avec <span class="cli">save-report</span> ou <span class="cli">write-core</span> pour un fichier image, puis appuyez une fois sur le bouton marche/arrêt pour essayer d'arrêter proprement le système. Si le bouton d'alimentation ne fonctionne pas, il y a aussi les commandes <span class="cli">shutdown</span> et <span class="cli">reboot</span>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Bogues du noyau</a></h2>
|
||||
@@ -119,8 +117,8 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
|
||||
<li><p>Le système entre en mode débogage du noyau (KDL) de lui même. La partie supérieure de l'écran est mise à blanc et plusieurs lignes de texte sont affichées.
|
||||
La seconde ligne dit « <i>Welcome to Kernel Debugging Land…</i> ». Celle au-dessus, précise la raison qui a déclenchée la session de débogage du noyau (KDL).</p></li>
|
||||
<li><p>Le système redémarre spontanément.</p></li>
|
||||
<li><p>Le système se bloque complètement. Vous ne pouvez pas déplacer la souris et plus aucune application ne dessine quoi que se soit. Dans cette situation, un bon test consiste à essayer d'accéder au KDL via le raccourci <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> étant la touche <span class="key">Impr</span> sur la plus part des claviers). Attendez au moins une minute, pour voir si quelque chose se passe.</p></li>
|
||||
<li><p>Le système ne démarre pas correctement. Il peut redémarrer spontanément ou s'arrêter à un moment donné (par exemple au niveau d'une icône de l'écran de démarrage). Dans ce dernier cas vous pouvez essayer aussi <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>Le système se bloque complètement. Vous ne pouvez pas déplacer la souris et plus aucune application ne dessine quoi que se soit. Dans cette situation, un bon test consiste à essayer d'accéder au KDL via le raccourci <span class="key">Alt</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> étant la touche <span class="key">Impr Écran</span> sur la plus part des claviers). Attendez au moins une minute, pour voir si quelque chose se passe.</p></li>
|
||||
<li><p>Le système ne démarre pas correctement. Il peut redémarrer spontanément ou s'arrêter à un moment donné (par exemple au niveau d'une icône de l'écran de démarrage). Dans ce dernier cas vous pouvez essayer aussi <span class="key">Alt</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>L'ensemble du système ou un élément matériel ne se comporte pas correctement. Par exemple, il pourrait être très lent, des erreurs pourraient se produisent, ou quelque chose pourrait ne pas fonctionner du tous. Si un périphérique ne fonctionne pas du tout, la première vérification évidente à faire, est de se renseigner pour savoir si il est déjà supporté par Haiku (par exemple, en posant la question sur une liste de diffusion ou un forum).</p></li>
|
||||
</ul>
|
||||
<p>Notez que si seul le dernier point semble indiquer une relation avec le matériel, tous les autres symptômes pourraient aussi être causés par un bogue dans un pilote.
|
||||
@@ -129,12 +127,12 @@ Par exemple, si vous soupçonnez le Wifi, votre BIOS a peut-être une option pou
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Le mode débogage noyau - KDL</a></h3>
|
||||
<p>Si le système n'entre pas de lui même en mode déboguage du noyau (KDL) vous pouvez le faire volontairement en invoquant le raccourci clavier <span class="key">ALT</span> <span class="key">Syst</span> <span class="key">D</span> Attention : l'ordre des touches compte (<span class="key">SYST</span> correspond à <span class="key">Impr Écran</span> sur la plupart des claviers).
|
||||
Notez bien que votre clavier pourrait ne pas fonctionner en mode déboguage du noyau. Alors que les claviers PS/2
|
||||
ne posent pas de problème, les claviers USB connecté à un controleur UHCI ne fonctionne que si vous être entré au moins une fois en mode débogage à l'aide du raccourci clavier. Pour le moment l'USB OHCI n'est pas supporté.</p>
|
||||
<p>Si le système n’entre pas de lui même en mode débogage du noyau (KDL) vous pouvez l’invoquer à l'aide du raccourci clavier <span class="key">At</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> correspond à <span class="key">Impr Écran</span> sur la plupart des claviers) Attention : l'ordre des touches compte<br />
|
||||
Notez bien que votre clavier pourrait ne pas fonctionner en mode débogage du noyau. Si les claviers PS/2 ne posent pas de problème, pour les claviers USB cela dépend du type de contrôleur USB (UHCI/EHCI).
|
||||
En règle générale, le clavier doit être branché directement sur le port, et non par l'intermédiaire d'un concentrateur. Dans certains cas, le clavier ne fonctionne que si l'on a invoqué le mode débogage du noyau une première fois via le raccourci clavier. Pour le moment l'USB OHCI n'est pas supporté.</p>
|
||||
<p>KDL est, par lui-même, une sorte d'interpréteur de commande. On peut exécuter des instructions pour afficher des informations sur le système. Les commandes suivantes pourraient vous intéresser :</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (alias sc)</td><td> </td><td>Affiche une trace de débogage (backtrace), Faites systematiquement cette commande quand le système entre dans le débogueur de lui même.</td></tr>
|
||||
<tr><td><span class="cli">bt</span> (alias <span class="cli">sc</span>)</td><td> </td><td>Affiche une trace de débogage (backtrace), Faites systematiquement cette commande quand le système entre dans le débogueur de lui même.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Affichera les interruptions matérielles qui sont gérées, ainsi que celles qui sont ignorées.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (alias continue)</td><td> </td><td>Quitte le débogueur pour reprendre, si possible, les opérations normales du système.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Redémarre le système immédiatement. Vous perdrez toutes les données non enregistrées, ainsi que celles qui ont été enregistrés, mais qui n'ont pas encore été écrites sur le disque.</td></tr>
|
||||
@@ -145,8 +143,8 @@ 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/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><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 abrégé) contient des informations précieuses sur ce qui s'est passé dans votre système, y compris les productions des sessions KDL. L'attacher au ticket « kernel » dans l'outil de suivi de bogues (Trac) est généralement une bonne pratique.
|
||||
Le journal est consigné dans le fichier <span class="path">/boot/system/var/log/syslog</span>. Puisque l'écriture d'un fichier requiert un système qui fonctionne, les entrées les plus récentes 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>
|
||||
@@ -165,11 +163,12 @@ Une ou plusieurs pages de texte seront affiché à l'écran, Seules les quelques
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>Fait une liste détaillée de votre matériel, en y incluant les identifiants des périphériques PCI et de leurs fabriquants, à la manière de <span class="cli">lshw</span> ou <span class="cli">lspci</span> dans GNU/Linux.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Fait comme <span class="cli">lsusb</span> en supposant que c'est un problème lié à l'USB.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Le journal système principal utilisé par Haiku, semblable à celui de l'écran de débogage pendant le démarrage. Avec la commande <span class="cli">open</span>, vous pouvez modifier ce journal dans un éditeur de texte pour n'en conserver que la partie la plus pertinente.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Le journal système principal utilisé par Haiku (voir <a href="#syslog">Le journal système</a> ci-dessus)
|
||||
est similaire à l'écran de débogage pendant le démarrage. Avec la commande <span class="cli">open</span>, vous pouvez modifier ce journal dans un éditeur de texte pour n'en conserver que la partie la plus pertinente.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Liste tous les drivers utilisés.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Seulement disponible dans le <i>mode débogage du noyau</i> (voir ci-dessous). Montre l'utilisation des interruptions.
|
||||
Il ne devrait pas y avoir trop d'interruptions partagées par plusieurs périphériques.</td></tr>
|
||||
<tr><td colspan="3">- Les sorties écran du débogueur (une option de mode sans échec du démarrage).</td></tr>
|
||||
<tr><td colspan="3">- Les sorties écran du débogueur (une option de démarrage en mode sans échec, voir <a href="#onscreen">ci-dessus</a>).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>Les 4 premières commandes sont à exécuter dans le Terminal. Si vous ajoutez <span class="cli"> > sortie.txt</span> après une commande, sa sortie sera redirigée dans un fichier texte nommé « sortie.txt » que vous pourrez attachez à votre rapport de bogue ou e-mail.</p>
|
||||
|
||||
@@ -90,7 +90,7 @@ Miután megbizonyosodtál róla, hogy a hiba egyedi, akkor azt a lehető legpont
|
||||
<ul>
|
||||
<li><p>Próbáld meg a hibát a legújabb verzión is előidézni. Előre elkészített képfájlok is a <a href="http://download.haiku-os.org">rendelkezésre állnak</a>.</p></li>
|
||||
<li><p>Add meg az alapvető információkat arra vonatkozóan, hogy miként használtad a Haiku-t (például valós gépen vagy emulátoron (VMWare, QEMU), stb.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (x86_gcc2, x86_64). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Írd le a tapasztalt problémát. Próbáld meg olyan pontosan, ahogy tudod: mi és hogyan viselkedett, és mire számítottál.</p></li>
|
||||
<li><p>Írd le, hogy milyen lépések szükségesek ahhoz, hogy a hibát meg tudjuk ismételni. Ez a lépés segít a fejlesztőknek.</p></li>
|
||||
<li><p>Mellékelj annyi információt, amennyit csak tudsz. Ha ez a grafikus felület, vagy egy program hibája, akkor készíts egy képernyőképet a <span class="key">PRINT</span> billentyű lenyomásával.</p></li>
|
||||
@@ -98,13 +98,13 @@ Miután megbizonyosodtál róla, hogy a hiba egyedi, akkor azt a lehető legpont
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Program hibák</a></h2>
|
||||
<p>Ha egy program meghibásodott, akkor a hibakereső a megjelenített üzenetből is előhívható. Ekkor megnyílik egy Terminál ablak a gdb-t (GNU hibakereső) futtatva. A <span class="cli">bt</span>-t kiadva létrehozhatunk egy "visszakövetést", aminek az eredményét a jelentéshez kell mellékelni (azt is, amit a <span class="cli">bt</span> előtt kaptál).</p>
|
||||
<p>When an application crashed, you can either save a report or write a core file (both saved to the Desktop) that you can attach to a bugreport, or you can evoke the <a href="../../userguide/hu/applications/debugger.html">Debugger</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Kiszolgáló/szolgáltatás hibák</a></h2>
|
||||
<p>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 />
|
||||
<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 the Debugger will be started in text-mode, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and Debugger 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.<br />
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> and then press the power button once to try shutting cleanly down.</p>
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> or <span class="cli">write-core</span> for a core file, and then press the power button once to try shutting cleanly down. If the power button doesn't work, there are also the commands <span class="cli">shutdown</span> and <span class="cli">reboot</span>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Kernel hibák</a></h2>
|
||||
@@ -120,11 +120,11 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL (Kernel Hibakereső Felület)</a></h3>
|
||||
<p>Ha a rendszer nem lép be automatikusan a KDL-be, akkor a <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> kombinációval manuálisan is beléphetsz oda.<br />
|
||||
Ne feledd, megeshet, hogy a billentyűzeted nem fog működni a KDL-ben. A PS/2 billentyűzet biztosan, az USB csak akkor, ha UHCI vezérlőre van csatlakoztatva. USB OHCI jelenleg nem használható.</p>
|
||||
<p>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> (<span class="key">SysReq</span> being the <span class="key">Print</span> key, normally).<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, with USB keyboards it depends on the type of USB controller (UHCI/EHCI). Generally, the keyboard should be plugged into the port directly, not via any hubs. In some circumstances, the keyboard only works if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>A KDL egyfajta shell. Itt néhány parancsot is használhatunk. Az alábbi parancsok érdekesek lehetnek:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (sc)</td><td> </td><td>A hiba visszakövetése. Ha egy hiba miatt kerülsz a KDL-be, akkor ezt alapból kiadja az.</td></tr>
|
||||
<tr><td><span class="cli">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>A hiba visszakövetése. Ha egy hiba miatt kerülsz a KDL-be, akkor ezt alapból kiadja az.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>A kezelt és nem kezelt eszköz-megszakítások megjelenítése.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (continue)</td><td> </td><td>Ha lehetséges, akkor kilép a hibakeresőből, és folytatja a normális működést.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Azonnal újraindítja a rendszert. Minden nem mentett adatot elveszítesz. Azokat is, amit bár elmentettél, de még nem lett a lemezre írva.</td></tr>
|
||||
@@ -143,10 +143,10 @@ A rendszertöltő <span class="menu">Debug menu</span>-ben (hibakereső menü) a
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">Hibakeresés a képernyőn</a></h3>
|
||||
<p><b>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/hu/bootloader.html">Boot Loader</a>.</p>
|
||||
<p><b>A képernyőn történő hibakeresés csak egy megadott hiba esetében hasznos, és időigényes. Ne használd, ha nem szükséges.</b><br />
|
||||
Ez akkor fontos, ha a Haiku nem tud elindulni és a <span class="menu">hibakereső naplózás</span> valamiért nem működik. Mielőtt a Haiku logó megjelenik, tartsd lenyomva a <span class="key">SHIFT</span>-et a rendszertöltőbe való belépéshez. Válasszd a <span class="menu">Select safe mode options</span> (hibakereső opciók) menüt, majd azon belül az <span class="menu">[ ] Enable on screen debug output</span> (képernyőn történő hibakeresés engedélyezése) opciót. (Megjegyzés: több opció is haszálható betöltéskor. Ha a Haiku indításakor egy vagy több opciót is használsz, akkor azokat is említsd meg.)<br />
|
||||
Végül válaszd a <span class="menu">Return to main menu</span> (visszatérés a főmenübe), majd a <span class="menu">Continue booting</span> (betöltés folytatása) menüpontot.<br />
|
||||
Egy vagy több oldalnyi szöveg is megjelenik majd a képernyőn, amiből csak az utolsó néhány sort szükséges a jelentéshez csatolni. További információk a <a href="../../userguide/hu/bootloader.html">Rendszertöltő</a> fejezetben.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Eszköz/vezérlő hibák</a></h2>
|
||||
@@ -155,10 +155,10 @@ One or more pages of text will display on the screen, only the last few lines ne
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>Részletes lista az eszközökről/összetevőkről a pci és a gyártó azonosítójával együtt. Hasonló a Linux <span class="cli">lshw</span> és <span class="cli">lspci</span> parancsához.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>USB-vel kapcsolatos hiba esetén. Hasonló a <span class="cli">lsusb</span>-hez.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Az elsődleges napló, amit a Haiku használ, amibe az indításkori üzenetek is bekerülnek. Az <span class="cli">open</span> használatával a naplóból egy adott részt is kimásolhatunk, mert az egy szövegszerksztőben nyílik meg.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, see <a href="#syslog">Syslog</a> above, 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>Az összes használt eszközvezérlő.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Csak a <i>Kernel Debugging Land</i>-ben haszálatos (lásd fejjebb). A megszakítások használatát jeleníti meg. Elvileg nem lehet túl sok amit megosztva használnak az eszközök.</td></tr>
|
||||
<tr><td colspan="3">- Hibakeresés a képernyőn (indításkori biztonsági opció).</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option, see <a href="#onscreen">above</a>).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>Az elős 4 parancsot a Terminálban kell kiadni. Kiegészítve a <span class="cli"> > output.txt</span> paraméterrel, a parancsok kimenete nem a képernyőre, hanem egy "output.txt" (kimenet) nevű fájlba kerül, amit a jelentéshez csatolhatunk vagy levélhez mellékelhetünk.</p>
|
||||
|
||||
@@ -87,7 +87,7 @@ After you have established that it's a unique bug, make your information as accu
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (x86_gcc2, x86_64). 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>
|
||||
@@ -95,17 +95,17 @@ After you have established that it's a unique bug, make your information as accu
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Application bugs</a></h2>
|
||||
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
|
||||
<p>When an application crashed, you can either save a report or write a core file (both saved to the Desktop) that you can attach to a bugreport, or you can evoke the <a href="../../userguide/it/applications/debugger.html">Debugger</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Server bugs</a></h2>
|
||||
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
|
||||
<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 the Debugger will be started in text-mode, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and Debugger 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.<br />
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> and then press the power button once to try shutting cleanly down.</p>
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> or <span class="cli">write-core</span> for a core file, and then press the power button once to try shutting cleanly down. If the power button doesn't work, there are also the commands <span class="cli">shutdown</span> and <span class="cli">reboot</span>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Kernel bugs</a></h2>
|
||||
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<p>Kernel bugs are usually the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<ul>
|
||||
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
|
||||
<li><p>The system reboots spontaneously.</p></li>
|
||||
@@ -117,13 +117,13 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>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> (<span class="key">SysReq</span> being the <span class="key">Print</span> key, normally).<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, with USB keyboards it depends on the type of USB controller (UHCI/EHCI). Generally, the keyboard should be plugged into the port directly, not via any hubs. In some circumstances, the keyboard only works if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
|
||||
<tr><td><span class="cli">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace. If the system entered KDL on its own 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 class="onelinetop"><span class="cli">co</span> (aka <span class="cli">continue</span>)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
|
||||
</table>
|
||||
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
@@ -132,7 +132,7 @@ 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 />
|
||||
<p><b>This is the preferred method for extracting 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 />
|
||||
@@ -141,7 +141,7 @@ In the boot loader's <span class="menu">Debug menu</span> you should find the en
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">On screen debug output</a></h3>
|
||||
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog</span> option doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../userguide/it/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
@@ -152,13 +152,13 @@ One or more pages of text will display on the screen, only the last few lines ne
|
||||
<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>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, see <a href="#syslog">Syslog</a> above, 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 colspan="3">- On screen debug output (a safe mode boot time option, see <a href="#onscreen">above</a>).</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>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 "<tt>output.txt</tt>" that you can attach to your bug report or email.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">What's next?</a></h2>
|
||||
|
||||
@@ -12,9 +12,9 @@
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <[email protected]>
|
||||
* Translators:
|
||||
* Shota Fukumori
|
||||
* log-1
|
||||
* mt
|
||||
* Shota Fukumori
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -60,7 +60,7 @@
|
||||
<div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>目次</td></tr>
|
||||
<tr class="heading"><td>インデックス</td></tr>
|
||||
<tr class="index"><td><a href="#account">Trac アカウントを取得する</a><br />
|
||||
<a href="#report">バグレポートの作成</a><br />
|
||||
<a href="#app">アプリケーションのバグ</a><br />
|
||||
@@ -68,29 +68,29 @@
|
||||
<a href="#kernel">カーネルのバグ</a><br />
|
||||
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
|
||||
<a href="#syslog">Syslog</a><br />
|
||||
<a href="#onscreen">スクリーン上でのデバッグ</a><br />
|
||||
<a href="#hardware">Hardware/Driver bugs</a><br />
|
||||
<a href="#next">そして次は</a></td></tr>
|
||||
<a href="#onscreen">画面上でのデバッグ</a><br />
|
||||
<a href="#hardware">ハードウェアとドライバーのバグ</a><br />
|
||||
<a href="#next">次はどうする</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>バグの報告</h1>
|
||||
|
||||
<p>開発者はすべてのハードウェア構成でテストをできません。また、オペレーティングシステムとのあらゆる関わり方をテストすることもできません。そのため私たちは、動作報告をユーザーに頼っています。そして Haiku はまだ幼いプロジェクトのため、バグに遭遇する可能性が高いです。私たちはあなたがバグ報告に時間を割いてくれることに対して感謝します。共に私たちは Haiku を少しづつ改善していくことができます。</p>
|
||||
<p>開発者はすべてのハードウェア構成でテストをできません。また、オペレーティングシステムとのあらゆる関わり方をテストすることもできません。そのため私たちは、動作報告をユーザーに頼っています。そして Haiku はまだ幼いプロジェクトのため、バグに遭遇する可能性が高いです。私たちはあなたがバグ報告に時間を割いてくれることに対して感謝します。共に私たちは Haiku を少しずつ改善していくことができます。</p>
|
||||
<p>私たちのバグトラッカーを有効に保つため、<a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">バグトラッカーでのエチケット</a>を絶対に守ってください。</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Trac アカウントを取得する</a></h2>
|
||||
<p>チケットを登録するには、<a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku バグトラッカー</a>でアカウントを取得する必要があります。<br />
|
||||
アカウントを作るときは、チケットの更新通知メールを受信するために<b>自分のメールアドレスを登録すること</b>が必要です。さまざまな確認のためのメールが届くため、アカウントを作成した後は、こまめに<b>迷惑メールフォルダ</b>をチェックするようにしてください。というのも、重要な確認メールがしばしば迷惑メールに分類されてしまうからです。</p>
|
||||
アカウントを作るときは、チケットの更新通知メールを受信するために<b>自分のメールアドレスを登録すること</b>が必要です。さまざまな確認のためのメールが届くため、アカウントを作成した後は、こまめに<b>迷惑メールフォルダ</b>をチェックしてください。というのも、重要な確認メールがしばしば迷惑メールに分類されてしまうからです。</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">バグレポートの作成</a></h2>
|
||||
<p>バグを報告する前に、すでに報告されていないか<a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">確認を</a>するようにしてください。<a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">検索機能</a>が有用です。<br />
|
||||
<p>バグを報告する前に、すでに報告されていないか<a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">確認</a>してください。<a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">検索機能</a>が有用です。<br />
|
||||
報告されていないことを確認したら、以下の情報をできる限り多く提供してください。</p>
|
||||
<ul>
|
||||
<li><p>その問題が最新バージョンの Haiku でも再現するかを確認してみてください。テスト用のビルド済イメージが<a href="http://download.haiku-os.org">利用可能です</a>。</p></li>
|
||||
<li><p>その問題が最新バージョンの Haiku でも再現するかを確認してください。テスト用のビルド済イメージが<a href="http://download.haiku-os.org">利用可能です</a>。</p></li>
|
||||
<li><p>テストした環境の情報 (物理的なハードウェア、QEMU、VMware など)</p></li>
|
||||
<li><p>動かしているリビジョン番号について言及してください。この情報は、Deskbar メニューの<span class="menu">Haiku について (About Haiku...)</span> から得られます。同様にテストしているHaiku のビルドの種類 (gcc2, gcc4, gcc2hybrid, gcc4hybrid) についても触れてください。ダウンロードイメージはビルドの種類に従って命名されています。自分でビルドしたイメージについては、どのようにビルドしたか知っておく必要があります。</p></li>
|
||||
<li><p>動かしているリビジョン番号について言及してください。この情報は、Deskbar メニューの <span class="menu">Haiku について (About Haiku...)</span> から得られます。同様にテストしている Haiku のビルドの種類 (x86_gcc2, x86_64) についても触れてください。ダウンロードイメージはビルドの種類に従って命名されています。自分でビルドしたイメージについては、どのようにビルドしたか知っておく必要があります。</p></li>
|
||||
<li><p>できる限り正しく、実際に起きた挙動を説明し、その後自分が予測した挙動と、現在の挙動の問題を説明する</p></li>
|
||||
<li><p>再現する手順や準備。これは開発者が再現するために必要です。</p></li>
|
||||
<li><p>その他の情報。GUI 周りのバグやアプリケーションのバグならば、<span class="key">PRINT</span> キーを押してスクリーンショットを取得してください。</p></li>
|
||||
@@ -98,40 +98,40 @@
|
||||
|
||||
<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>アプリケーションがクラッシュしたときは、レポートを保存するかコアファイルを書き込むかができ (どちらもデスクトップ上に保存されます)。それらはバグレポートに添付できます。または、<a href="../../userguide/jp/applications/debugger.html">デバッガー</a>を起動します。</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">サーバーのバグ</a></h2>
|
||||
<p>App server、registrar、input server のような重要なサーバーがクラッシュしたときはよくあるクラッシュアラートを見ることは無いでしょう。その代わりに、スクリーン全体が白で塗りつぶされ、gdb のセッションがスタートします。出力はスクリーンに直接出力されます。たぶん、マウスはまだ動かせでも gdb の出力を上書きするでしょう。アプリケーションも動いたままで、(たとえば、プロセスコントローラーや デスクバーの時計のように) それも gdb の出力を上書きします。<br />
|
||||
さらに、アプリケーションのバグに比べ、すべては見にくく便利ではありません。アプリケーションのバグのようにはいかないでしょう。もっとも重要なバックトレースの取得 (<span class="cli">bt</span> コマンド) も、どこでもテキストのコピーができないのでデジタルカメラ等を用いて写真を撮影しないとならないでしょう。<br />
|
||||
実際にクラッシュしているものに応じて、デスクトップに <span class="cli">save-report</span> を使ってクラッシュレポートを保存してみてもよいです。それから電源ボタンを一度押して、手際よくシャットダウンしてみることもできます。</p>
|
||||
<p>App server、registrar、input server のような重要なサーバーがクラッシュしたときはよくあるクラッシュアラートを見ることは無いでしょう。その代わりに、画面全体が白で塗りつぶされ、デバッガーがテキストモードで開始します。出力はスクリーンに直接出力されます。たぶん、マウスはまだ動かせでも デバッガーの出力を上書きするでしょう。アプリケーションも動いたままで、(たとえば、プロセスコントローラーや デスクバーの時計のように) それもデバッガーの画面上への出力を上書きします。<br />
|
||||
すべては見にくく便利でないことを除けば、基本的にアプリケーションのバグと同様なものが適用できます。もっとも重要なバックトレースの取得 (<span class="cli">bt</span> コマンド) も、どこでもテキストのコピーができないのでデジタルカメラ等を用いて写真を撮影しないとならないでしょう。<br />
|
||||
実際にクラッシュしているものに応じて、デスクトップに <span class="cli">save-report</span> を使ってクラッシュレポートを保存するか、<span class="cli">write-core</span> で core file を保存してみてもよいです。それから電源ボタンを一度押して、手際よくシャットダウンしてみることもできます。電源ボタンが動作しない場合は、<span class="cli">shutdown</span> および <span class="cli">reboot</span> コマンドがあります。</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">カーネルのバグ</a></h2>
|
||||
<p>カーネルのバグのデバッグはもっとも難しいでしょう。カーネルやドライバーのバグにはこのようなさまざまな症状があります:</p>
|
||||
<p>カーネルのバグは、もっとも重い努力を伴うバグであり、一方それと同時に、デバッグはもっとも困難なものでしょう。以下のようなさまざまな種類の症状は、そのほとんどがカーネルやドライバーのバグを示しています:</p>
|
||||
<ul>
|
||||
<li><p>システムは kernel debugging land (KDL) に入ります。画面上部はクリアされいくつかの KDL に入る原因となった理由を含むと思われる文字列が出力されます。次に、"<i>Welcome to Kernel Debugging Land...</i>" と出力されます。その上に、KDL に入った直接の理由が表示されます。</p></li>
|
||||
<li><p>システムは自然に再起動します。</p></li>
|
||||
<li><p>システムは自発的に再起動します。</p></li>
|
||||
<li><p>システムは完全にフリーズします。マウスを動かすこともできず、アプリケーションも停止します。<span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (だいたいのキーボードで、<span class="key">SysReq</span> は <span class="key">PRINT</span> と同じキーです) を押して、KDL に入れます。</p></li>
|
||||
<li><p>システムは正常に起動しません。起動中に再起動するか、起動中にどこかで止まるか (たとえば、ブートスクリーンでのいくつかのアイコンで) のどちらかかもしれません。後者の場合でも、<span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> を押してみてください。</p></li>
|
||||
<li><p>システム全体または一部のハードウェアで正常な動作をしない。たとえば、動作がすごく遅い、エラーが発生する、完全に動作しない、などです。一部のハードウェアが動作しないならば、まず Haiku がそれをサポートするかどうかを確認してください (メーリングリストやフォーラムで聞いてみるなど)</p></li>
|
||||
<li><p>システム全体または一部のハードウェアで正常な動作をしない。たとえば、動作がすごく遅い、エラーが発生する、完全に動作しない、などです。一部のハードウェアが動作しないならば、まず Haiku がそれをサポートするかどうかを確認してください (メーリングリストやフォーラムで聞いてみるなど)。</p></li>
|
||||
</ul>
|
||||
<p>最後のポイントだけは、ハードウェアに関係あることを示すように思えますが、すべての他の症状も同様に、ハードウェアのドライバーのバグが原因で発生することがありえることに注意してください。もしドライバーやハードウェアに疑いを持っているならば、そのハードウェアを取り外すか、無効化をしてどのように変わるかを確認してください。たとえば、Wifi が問題だと疑っているならば BIOS の設定を参照して Wifi を無効化できます。設定がない場合は、問題の原因である Wifi ドライバーを Haiku のインストールからブラックリストに入れる (<a href="../../../userguide/en/bootloader.html">ブートローダー</a>を参照ください) ことができます。</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 キーボードは、一度キーボードショートカット経由で KDL に入った場合のみ動作するでしょう。現時点では、USB OHCI はサポートされていません。</p>
|
||||
<p>システムが KDL に自動で入らなかった場合、<span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (通常、<span class="key">SysReq</span> は、<span class="key">Print</span> キーです) を押して意図的に入ることができます。<br />
|
||||
ここで注意することは、KDL ではキーボードが動作しないかもしれないことです。PS/2 キーボードは常に動作します。USB キーボードは、USB コントローラーのタイプ (UHCI/EHCI) 次第です。通常、キーボードはハフを介さず、直接 USB ポートに接続されるべきです。少なくとも一度は、キーボードショートカット経由で KDL に入った場合、状況次第でキーボードのみ動作するでしょう。現時点では、USB OHCI はサポートされていません。</p>
|
||||
<p>KDL 自体はシェルの一種です。システム情報を出力するコマンドを実行できますす。次のコマンドが役に立つでしょう:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (もしくは sc)</td><td> </td><td>バックトレースを出力する。システムが自ら KDL に入った場合、これを必ず実行します。</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>処理される / 処理されないハードウェア割り込みを表示します。</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (もしくは continue)</td><td> </td><td>カーネルデバッガーを離れ、可能ならばシステムの実行に戻ります。</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>システムをすぐに再起動します。まだ保存されていないすべてのデータ、保存はしていてもまだディスクに書き込まれていないデータは失われます。</td></tr>
|
||||
<tr><td><span class="cli">bt</span> (別名 <span class="cli">sc</span>)</td><td> </td><td>バックトレースを出力する。システムが自ら KDL に入った場合、これを必ず実行する。</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>処理される / 処理されないハードウェア割り込みを表示。</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (または continue)</td><td> </td><td>カーネルデバッガーを離れ、可能ならばシステムの実行に戻る。</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>システムをすぐに再起動する。まだ保存されていないすべてのデータ、保存はしていてもまだディスクに書き込まれていないデータは失われる。</td></tr>
|
||||
</table>
|
||||
<p>詳細は <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Kernel Debugging Land へようこそ</a>も参照してください。</p>
|
||||
<p>KDL はシリアルポートと syslog にも出力します (もしあるならば。シリアルケーブルをもう一つのコンピューターに接続し、出力を受け取れます)。KDL を終了できない場合 syslog には出力されませんが、ブートローダーのデバッグ用オプションがそれを可能にするでしょう (下記も参照ください)。</p>
|
||||
<p>KDL の出力から QR コードを生成できます。QR コードは、スマートフォンなどを使ってテキストに変換できます。この機能を使って KDL のデータを取り出すことについては、次のブログ投稿、<a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> を参照してください。</p>
|
||||
<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>
|
||||
@@ -142,26 +142,26 @@ syslog (system log の略称) はシステムに発生した有益な情報を
|
||||
ブートローダーメニューにある <span class="menu">Debug menu</span> の中には <span class="menu">Display syslog from previous session</span> と <span class="menu">Save syslog from previous session</span> があります。前者は syslog をスクリーンに表示し、後者はディスクに保存します。現時点では FAT32 フォーマットのみサポートされていることに注意してください。USB メモリを使用する場合は、後から接続しても認識しないので 1 度再起動し、再度ブートローダーメニューに入る必要があります。注意: 誤ってほかのオペレーションシステムを実行しないようにしてください。syslog を失ってしまいます。</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">スクリーン上でのデバッグ</a></h3>
|
||||
<p><b>スクリーン上のデバッグ出力は極めて特定の問題とすでにわかっている (タイミング) 問題について役立つでしょう。必要でないなら使用しないでください。</b><br />
|
||||
<a id="onscreen" name="onscreen">画面上でのデバッグ</a></h3>
|
||||
<p><b>画面上のデバッグ出力は極めて特定の問題にのみ役立ち、(タイミングの) 問題を持つことがわかっています。必要でないなら使用しないでください。</b><br />
|
||||
これは Haiku がユーザーのマシンでうまく起動せず、なおかつ何らかの理由で <span class="menu">Debug syslog option</span> もうまく動作しないときに使います。Haiku の起動ロゴが現れる前に、<span class="key">SHIFT</span> を押したままにしてブートローダーメニューに入り、<span class="menu">Select safe mode options</span> を選びます。下の方に <span class="menu">[ ] Enable on screen debug output</span> がリストにあります (注意: ほかのオプションも Haiku のブートを試みる際に有効にできます。Haiku がひとつ以上のオプションを有効にした時のみ起動する場合は、必ずどのオプションかを挙げるようにしてください)。<br />
|
||||
最後に、<span class="menu">Return to main menu</span> を選択し、それから <span class="menu">Continue booting</span> を選択します。<br />
|
||||
1 ページ以上のテキストがスクリーンに表示されますが、最後の数行のみがチケットに添付する必要がある物でしょう。詳細は、<a href="../../userguide/jp/bootloader.html">ブートローダー</a>を参照ください。</p>
|
||||
1 ページ以上のテキストが画面に表示されますが、最後の数行のみがチケットに添付する必要がある物でしょう。詳細は、<a href="../../userguide/jp/bootloader.html">ブートローダー</a>を参照ください。</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">ハードウェアとドライバーのバグ</a></h2>
|
||||
<p>もしハードウェアやドライバーのバグに関連したバグを扱うならば、以下の情報を添付する必要があります:</p>
|
||||
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>ベンダーと PCI id を含む詳細なハードウェアのリストを出力します。linux の <span class="cli">lshw</span> と <span class="cli">lspci</span> に似ています。</td></tr>
|
||||
<tr><td>- <span class="cli">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">open /var/log/syslog</span></td><td> </td><td>Haiku で使用するシステムのメインログ、上の <a href="#syslog">Syslog</a> を参照ください。ブート中の画面上デバッグと似ています。<span class="cli">open</span> コマンドを用いることで、syslog の関連する部分をテキストエディターに切り出せます。</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">- 画面上へのデバッグ出力 (ブート時のセーフモードオプション<a href="#onscreen">上</a>を参照)</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>
|
||||
|
||||
@@ -11,11 +11,13 @@
|
||||
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <[email protected]>
|
||||
* Translators:
|
||||
* Kacper Kasper
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Reporting bugs</title>
|
||||
<title>Zgłaszanie błędów</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
@@ -54,118 +56,115 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Tłumaczenie tej strony jest niekompletne. Nieukończone części wyświetlane są w języku angielskim.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Spis treści</td></tr>
|
||||
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
|
||||
<a href="#report">Creating a bug report</a><br />
|
||||
<a href="#app">Application bugs</a><br />
|
||||
<a href="#server">Server bugs</a><br />
|
||||
<a href="#kernel">Kernel bugs</a><br />
|
||||
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
|
||||
<tr class="index"><td><a href="#account">Zakładanie konta Trac</a><br />
|
||||
<a href="#report">Otwieranie zgłoszenia</a><br />
|
||||
<a href="#app">Błędy w aplikacjach</a><br />
|
||||
<a href="#server">Błędy w serwerach</a><br />
|
||||
<a href="#kernel">Błędy w jądrze</a><br />
|
||||
<a href="#kdl">Tryb krokowy jądra (KDL)</a><br />
|
||||
<a href="#syslog">Syslog</a><br />
|
||||
<a href="#onscreen">On screen debug output</a><br />
|
||||
<a href="#hardware">Hardware/Driver bugs</a><br />
|
||||
<a href="#next">What's next?</a></td></tr>
|
||||
<a href="#onscreen">Wypis dziennika na ekran</a><br />
|
||||
<a href="#hardware">Błędy sprzętowe/w sterownikach</a><br />
|
||||
<a href="#next">Co dalej?</a></td></tr>
|
||||
</table>
|
||||
|
||||
<h1>Reporting bugs</h1>
|
||||
<h1>Zgłaszanie błędów</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>Nasi deweloperzy nie są w stanie przetestować każdej możliwej kombinacji sprzętu ani każdego możliwego sposobu interakcji z systemem. Z tego powodu polegamy na użytkownikach, licząc na to, że dadzą nam znać jak Haiku działa na ich komputerach. Ponieważ Haiku jest projektem dość młodym, istnieje duże prawdopodobieństwo, że natkniesz się na błędy. Dziękujemy za czas poświęcony na ich zgłoszenie. Razem możemy ulepszyć Haiku, krok po kroku.</p>
|
||||
<p>Aby ułatwić na śledzenie problemów ważne jest przestrzeganie <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Etykiety systemu śledzenia błędów</a> (ang.).</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="account" name="accout">Getting a Trac account</a></h2>
|
||||
<p>To file a ticket, you need to have an account at <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku's Bugtracker</a>.<br />
|
||||
When creating a new account, be certain to <b>provide your email address</b> as it is necessary to obtain basic ticket modification privileges. Be sure to <b>check your spam folder</b> shortly afterwards, as the all important verification mail often ends up there.</p>
|
||||
<a id="account" name="accout">Zakładanie konta Trac</a></h2>
|
||||
<p>Aby zgłosić problem, potrzebujesz konta w <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">systemie śledzenia błędów Haiku</a>.<br />
|
||||
Zakładając konto koniecznie <b>podaj swój adres e-mail</b> ponieważ jest on niezbędny do otrzymania podstawowych uprawinień modyfikacji zgłoszeń. Nie zapomnij <b>sprawdzić katalogu ze spamem</b> maile weryfikacyjne zwykle tam trafiają.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="report" name="report">Creating a bug report</a></h2>
|
||||
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">search</a> function for this.<br />
|
||||
After you have established that it's a unique bug, make your information as accurate as possible:</p>
|
||||
<a id="report" name="report">Otwieranie zgłoszenia</a></h2>
|
||||
<p>Przed otworzeniem zgłoszenia <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">upewnij się</a>, że podobne jeszcze nie istnieje. Możesz do tego użyć funkcji <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">Szukaj</a>.<br />
|
||||
Kiedy już ustaliłeś, że Twój problem nie został wcześniej zgłoszony, ustal informacje najdokładniej jak potrafisz:</p>
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
|
||||
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
|
||||
<li><p>Spróbuj spowodować problem na najnowszej wersji Haiku. Gotowe obrazy do testów <a href="http://download.haiku-os.org">dostępne</a> są w sieci.</p></li>
|
||||
<li><p>Załącz podstawowe informacje, takie jak na czym testujesz Haiku (na sprzęcie, w VMWare, w QEMU, itp.).</p></li>
|
||||
<li><p>Napisz jakiej wersji używasz. Znajdziesz tę informację w oknie <span class="menu">O Haiku...</span> dostępnym z menu Deskbara. Istotna jest także architektura systemu (x86_gcc2, x86_64). Obrazy pobrane z sieci mają odpowiednie nazwy, w przypadku systemu zbudowanego samodzielnie powinieneś wiedzieć jakiej jest architektury.</p></li>
|
||||
<li><p>Opisz problem najdokładniej jak możesz: zawrzyj nie tylko opis zachowania obserwowanego, ale też zachowania oczekiwanego.</p></li>
|
||||
<li><p>Opisz krok po kroku jak wywołać opisane zachowanie. To pomoże deweloperom szybciej naprawić błąd.</p></li>
|
||||
<li><p>Załącz jak najwięcej informacji. Jeśli to problem z interfejsem graficznym lub błąd w aplikacji, wykonaj zrzut ekranu klawiszem <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">Application bugs</a></h2>
|
||||
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
|
||||
<a id="app" name="app">Błędy w aplikacjach</a></h2>
|
||||
<p>Kiedy aplikacja ulegnie awarii, możesz włączyć <a href="../../userguide/pl/applications/debugger.html">Debugger</a>, zapisać raport lub zrzut pamięci (oba na pulpicie). Pliki dołącz do zgłoszenia.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Server bugs</a></h2>
|
||||
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
|
||||
Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (<span class="cli">bt</span> command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.<br />
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> and then press the power button once to try shutting cleanly down.</p>
|
||||
<a id="server" name="server">Błędy w serwerach</a></h2>
|
||||
<p>Gdy krytyczne dla systemu serwery takie jak app server, registrar lub input server ulegają awarii, nie zobaczysz zwyczajnego okna z błędem, jak w przypadku aplikacji. Zamiast tego cały ekran zostanie wyczyszczony na biało i zostanie wystartowana tekstowa sesja Debuggera, której rezultaty pojawią się na ekranie. Prawdopodobnie nadal będziesz mieć możliwość poruszania kursorem, który nadpisze fragmenty ekranu. Wciąż działające aplikacji (takie jak ProcessController lub zegar w Deskbarze) również mogą się tak zachowywać.<br />
|
||||
Poza tym, że wszystko będzie brzydsze i mniej wygodne, obowiązują te same zasady co w przypadku błędów w aplikacjach. Co najważniejsze, uzyskaj stos wywołań (komenda <span class="cli">bt</span>). Może być konieczne zrobienie zdjęcia ekranu, ze względu na brak możliwości skopiowania tekstu.<br />
|
||||
W zależności od tego, co dokładnie uległo awarii, możesz spróbować zapisać raport lub zrzut pamięci na pulpicie komendami (odpowiednio) <span class="cli">save-report</span> i <span class="cli">write-core</span>, a następnie wcisnąć krótko przycisk zasilania jeden raz, aby wyłączyć komputer. Jeżeli przycisk zasilania nie działa, dostępne są również komendy <span class="cli">shutdown</span> i <span class="cli">reboot</span>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Kernel bugs</a></h2>
|
||||
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<a id="kernel" name="kernel">Błędy w jądrze</a></h2>
|
||||
<p>Błędy w jądrze zazwyczaj sprawiają najwięcej problemów, będąc jednocześnie najtrudniejszymi do zbadania. Są różne objawy wskazujące na błąd w jądrze lub sterowniku:</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>System z własnej woli wchodzi do trybu badania jądra (KDL). Górna część ekranu zostaje wyczyszczona białym kolorem i wypisane zostaje kilka linii tekstu. Druga linia to „<i>Welcome to Kernel Debugging Land...</i>”, ponad nią znajduje się bezpośredni powód wejścia do tego trybu.</p></li>
|
||||
<li><p>System spontanicznie się restartuje.</p></li>
|
||||
<li><p>System kompletnie się zawiesza. Nie można ruszyć kursorem oraz żadna aplikacja nie przerysowuje ekranu. Ważnym testem w tej sytuacji jest próba wejścia do KDL skrótem <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> to <span class="key">PRINT</span> na większości klawiatur). Poczekaj na efekt przynajmniej minutę.</p></li>
|
||||
<li><p>System nie startuje poprawnie. Może uruchamiać się ponownie lub zatrzymywać w którymś momencie (np. na którejś z ikon na ekranie rozruchowym). W drugim przypadku również spróbuj skrótu <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
|
||||
<li><p>Cały system lub któreś z urządzeń nie zachowuje się poprawnie. Na przykład może być bardzo powolne, powodować błędy lub w ogóle nie działać. Jeśli urządzenie nie działa, pierwszą rzeczą do sprawdzenia jest, czy Haiku ten sprzęt obsługuje (np. pytając na liście mailingowej lub forum).</p></li>
|
||||
</ul>
|
||||
<p>Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could blacklist the responsible Wifi driver from your Haiku installation (see <a href="../../userguide/pl/bootloader.html">Boot Loader</a>).</p>
|
||||
<p>Mimo że tylko ostatni symptom wskazuje na powiązanie ze sprzętem, wszystkie pozostałe objawy też mogą być spowodowane błędem w sterowniku. Jeżeli podejrzewasz jakieś konkretne urządzenie lub sterownik o powodowanie problemów, sprawdź czy wyłączenie/usunięcie ich robi różnicę. Dla przykładu, podejrzewając WiFi poszukaj w BIOS-ie opcji wyłączenia łączności bezprzewodowej. Możesz również wyłączyć ładowanie odpowiedniego sterownika (zobacz rozdział <a href="../../userguide/pl/bootloader.html">Boot Loader</a>).</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
|
||||
<a id="kdl" name="kdl">Tryb krokowy jądra (Kernel Debugging Land, KDL)</a></h3>
|
||||
<p>Jeżeli system nie wszedł do KDL, możesz to zrobić samodzielnie skrótem klawiszowym <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> to zazwyczaj <span class="key">Print</span>).<br />
|
||||
Weź pod uwagę, że w KDL klawiatura może nie działać. Klawiatury PS/2 działają zawsze, klawiatury USB podłączone do kontrolera UHCI działają tylko, gdy KDL został wywołany z klawiatury przynajmniej raz. USB OHCI nie jest obecnie obsługiwane.</p>
|
||||
<p>Sam KDL jest rodzajem powłoki. Można w nim wywoływać komendy zwracające informacje o stanie systemu. Poniższe są szczególnie przydatne:</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> (lub <span class="cli">sc</span>)</td><td> </td><td>Wypisuje stos wywołań. Zawsze wywołaj tę komendę, jeśli KDL pojawił się samoczynnie.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Wypisuje obsłużone i nieobsłużone przerwania sprzętowe.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (lub continue)</td><td> </td><td>Opuszcza tryb badania jądra i wznawia normalną pracę systemu, o ile jest to możliwe.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Natychmiast restartuje system. Powoduje utratę niezapisanych danych oraz tych zapisanych, ale nie zrzuconych jeszcze na dysk.</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>Więcej informacji w artykule <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a> (ang.).</p>
|
||||
<p>Wyjście KDL jest kopiowane na port szeregowy (jeśli komputer jest wyposażony w taki port, a ponadto masz odpowiedni kabel i drugi komputer, możesz je przechwycić korzystając z terminala) oraz do dziennika systemu. To ostatnie nie będzie możliwe, jeżeli nie możesz wyjść z KDL. Istnieje opcja boot loadera pozwalająca przechwycić informacje z KDL mimo tego (patrz niżej).</p>
|
||||
<p>Możesz wygenerować kody QR z wynikiem KDL, które mogą być potem odczytane na smartfonie lub podobnym urządzeniu. Zobacz wpis <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> (ang.) na blogu, aby dowiedzieć się jak korzystać z tej możliwości.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Syslog</a></h3>
|
||||
<p><b>This is the preferred method for gaining information from a non-booting system.</b><br />
|
||||
The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file <span class="path">/boot/system/var/log/syslog</span>. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).</p>
|
||||
<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog persistent. If the option <span class="menu">Save syslog from previous session during boot</span> is activated in the boot loader options (as it is by default), you'll find the syslog of your last session as <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
If you're not able to boot to get to the previous_syslog, you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
|
||||
In the boot loader's <span class="menu">Debug menu</span> you should find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. Note: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
<p><b>Jest to preferowana metoda wyciągnięcia informacji z niestartującego systemu.</b><br />
|
||||
Syslog (skrót od ang. <i>system log</i>, dziennik systemu) zawiera wartościowe informacje dotyczące tego, co działo się z systemem, włączając w to sesje KDL. Dobrą praktyką jest dołączanie tego pliku do zgłoszeń dotyczących jądra. Syslog jest zapisywany do pliku <span class="path">/boot/system/var/log/syslog</span>. Ponieważ zapisywanie do pliku wymaga działającego systemu, najświeższe informacje mogą się w nim nie znaleźć, jeżeli wystąpi problem z jądrem (w szczególności przy losowych restartach lub sesjach KDL, z których nie można wyjść).</p>
|
||||
<p>Opcja <span class="menu">Enable debug syslog</span> w menu bootloadera <span class="menu">Debug menu</span> sprawia, że syslog jest zrzucany bezpośrednio do pliku. Jeżeli opcja <span class="menu">Save syslog from previous session during boot</span> jest aktywowana (a domyślnie jest), syslog z poprzedniej sesji znajdziesz w pliku <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
W przypadku niestartującego systemu, aby dostać się do poprzedniego syslogu wciśnij klawisz <span class="key">SHIFT</span> podczas rozruchu.<br />
|
||||
W <span class="menu">Debug menu</span> bootloadera znajdziesz pozycje <span class="menu">Display syslog from previous session</span> oraz <span class="menu">Save syslog from previous session</span>. Pierwsza z nich wyświetla syslog na ekranie, druga pozwala zapisać dziennik do pliku. Obecnie tylko partycje FAT32 są obsługiwane. Jeśli chcesz użyć dysku USB, ale został podłączony za późno i przez to nierozpoznany, uruchom komputer ponownie i jeszcze raz wejdź do menu. Uwaga: przypadkowe uruchomienie systemu spowoduje utratę danych z dziennika.</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">On screen debug output</a></h3>
|
||||
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../userguide/pl/bootloader.html">Boot Loader</a>.</p>
|
||||
<a id="onscreen" name="onscreen">Wypis dziennika na ekran</a></h3>
|
||||
<p><b>Ta opcja jest przydatna do badania tylko ściśle określonych przypadków i wiadomo, że są z nią problemy. Nie używaj jej, o ile nie musisz.</b><br />
|
||||
Poniższe informacje mają zastosowanie tylko jeśli Haiku nie uruchamia się i opcja <span class="menu">Debug syslog</span> z jakiejś przyczyny nie działa. Podczas rozruchu, zanim pojawi się logo Haiku, przytrzymaj <span class="key">SHIFT</span>, aby otworzyć menu bootloadera. Wybierz <span class="menu">Select safe mode options</span>. Na dole pojawi się opcja <span class="menu">[ ] Enable on screen debug output</span>. (Uwaga: inne opcje także mogą być zaznaczone. Jeśli Haiku uruchamia się tylko z określonymi kombinacjami, opisz je w zgłoszeniu).<br />
|
||||
Na koniec wybierz <span class="menu">Return to main menu</span>, a następnie <span class="menu">Continue booting</span>.<br />
|
||||
Kilka stron tekstu zostanie wyświetlone na ekranie, ale tylko kilka ostatnich linii powinno być dołączone do zgłoszenia. Więcej informacji o rozruchu systemu jest w rozdziale <a href="../../userguide/pl/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">Hardware/Driver bugs</a></h2>
|
||||
<p>When dealing with a hardware/driver related bug, you should attach the following information as text files:</p>
|
||||
<a id="hardware" name="hardware">Błędy sprzętowe/w sterownikach</a></h2>
|
||||
<p>Mając do czynienia z błędem dotyczącym sprzętu lub sterownika, do zgłoszenia powinny być załączone jako pliki wyniki następujących komend:</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>Szczegółowa lista sprzętu, zawierająca identyfikatory producentów i modeli, odpowiednik linuksowych <span class="cli">lshw</span> i <span class="cli">lspci</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>W przypadku problemów z USB, odpowiednik <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Dziennik systemu opisany <a href="#syslog">wyżej</a>. Komendą <span class="cli">open</span> możesz przyciąć dziennik w edytorze tekstu.</td></tr>
|
||||
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Sporządza listę wszystkich używanych sterowników.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Dostępna tylko w <i>Trybie krokowym jądra (KDL)</i> (patrz wyżej). Wyświetla przerwania. Nie powinno być zbyt wielu współdzielonych przez różne urządzenia.</td></tr>
|
||||
<tr><td colspan="3">- Wypis dziennika na ekran (opcja ustawiana podczas rozruchu, zobacz <a href="#onscreen">wyżej</a>).</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>Pierwsze cztery komendy należy wpisać w aplikacji Terminal. Dodając <span class="cli"> > output.txt</span> po komendzie, można przekierować jej wynik z ekranu do pliku o nazwie „output.txt”, który później łatwo załączyć do zgłoszenia lub maila.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">What's next?</a></h2>
|
||||
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
|
||||
non-descriptive comments.</p>
|
||||
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
|
||||
as 'fixed'.</p>
|
||||
<a id="next" name="next">Co dalej?</a></h2>
|
||||
<p>Po zgłoszeniu błędu, jeden z deweloperów rzuci na niego okiem i spróbuje go sklasyfikować. Pamiętaj, wszyscy jesteśmy wolontariuszami, czasami zgłoszenie może pozostać przez jakiś czas bez odpowiedzi. Dołączanie nowych informacji zazwyczaj sprawia, że błąd zostanie naprawiony szybciej, ale nie należy „podbijać” zgłoszenia nieistotnymi komentarzami.</p>
|
||||
<p>Pamiętaj też, że zgłoszenie błędu to nie jest jednorazowy wysiłek. Po otwarciu zgłoszenia stajesz się częścią procesu jego rozwiązywania. W jego trakcie deweloperzy mogą mieć pytania. Zostań w kontakcie, aby móc na nie odpowiedzieć. Możesz uznać swoje zaangażowanie za „zakończone” dopiero gdy zgłoszenie zostanie oznaczone jako „rozwiązane”.</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@@ -12,9 +12,9 @@
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <[email protected]>
|
||||
* Translators:
|
||||
* tiagoms
|
||||
* Adriano Duarte
|
||||
* Humdinger
|
||||
* Adriano Duarte
|
||||
* tiagoms
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -91,7 +91,7 @@ Após constatar que é um erro original, torne sua informação a mais acurada p
|
||||
<ul>
|
||||
<li><p>Tente reproduzir o problema na versão atual do Haiku. Imagens pré-compiladas para o propósito de testes estão <a href="http://haiku-files.org/">disponíveis</a>.</p></li>
|
||||
<li><p>Inclua informação básica sobre como está testando o Haiku (em equipamento real, no VMWare, no QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (x86_gcc2, x86_64). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Descreva o problema que está experimentando. Tente ser o mais acurado possível: descreva o comportamento atual e o comportamento que deseja.</p></li>
|
||||
<li><p>Descreva que passos precisa realizar a fim de expor o erro. Isto ajudará os desenvolvedores a reproduzir o erro.</p></li>
|
||||
<li><p>Anexe toda a informação que tiver. Se é um erro de interface gráfica, ou um erro em um dos aplicativos, tente obter uma imagem da tela pressionando a tecla <span class="key">PRINT</span>.</p></li>
|
||||
@@ -99,13 +99,13 @@ Após constatar que é um erro original, torne sua informação a mais acurada p
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Erros de Aplicativo</a></h2>
|
||||
<p>Quando um aplicativo trava, deve-se executar o depurador a partir do alerta que aparece na tela. Isto abrirá uma janela do Terminal com o gdb (o depurador GNU) rodando nele. Executando <span class="cli">bt</span>, cria-se um "rastro" que deverá ser copiado inteiramente (incluindo a parte antes de executar o comando <span class="cli">bt</span>) e anexado ao tíquete.</p>
|
||||
<p>When an application crashed, you can either save a report or write a core file (both saved to the Desktop) that you can attach to a bugreport, or you can evoke the <a href="../../userguide/pt_BR/applications/debugger.html">Debugger</a>.</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 />
|
||||
<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 the Debugger will be started in text-mode, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and Debugger 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.<br />
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> and then press the power button once to try shutting cleanly down.</p>
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> or <span class="cli">write-core</span> for a core file, and then press the power button once to try shutting cleanly down. If the power button doesn't work, there are also the commands <span class="cli">shutdown</span> and <span class="cli">reboot</span>.</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>
|
||||
@@ -121,11 +121,11 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Terra da Depuração do Kernel - KDL</a></h3>
|
||||
<p>Se o sistema não entrar no KDL por si mesmo, pode-se fazê-lo intencionalmente invocando através do atalho de teclado <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Observe que no KDL seu teclado pode não funcionar. Teclados PS/2 sempre funcionam, teclados USB conectados via controladores UHCI apenas se alguém entrou no KDL via atalho de teclado ao menos uma vez. USB OHCI não é suportado no momento.</p>
|
||||
<p>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> (<span class="key">SysReq</span> being the <span class="key">Print</span> key, normally).<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, with USB keyboards it depends on the type of USB controller (UHCI/EHCI). Generally, the keyboard should be plugged into the port directly, not via any hubs. In some circumstances, the keyboard only works if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>O KDL propriamente é uma espécie de shell. Alguém pode executar comandos que exibem informação sobre o sistema. Os seguintes comandos podem ser de interesse:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (conhecido como sc)</td><td> </td><td>Exibe um rastro. Se o sistema entrar no KDL por sua própria vontade, sempre o execute.</td></tr>
|
||||
<tr><td><span class="cli">bt</span> (aka <span class="cli">sc</span>)</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>
|
||||
@@ -136,8 +136,8 @@ Observe que no KDL seu teclado pode não funcionar. Teclados PS/2 sempre funcion
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="syslog" name="syslog">Relatório de sistema</a></h3>
|
||||
<p><b>This is the preferred method for gaining information from a non-booting system.</b><br />
|
||||
The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file <span class="path">/boot/system/var/log/syslog</span>. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).</p>
|
||||
<p><b>Este é o método preferido para obter informação de um sistema que não inicializa.</b><br />
|
||||
O relatório do sistema contém informação valiosa sobre o que aconteceu no seu sistema, incluindo a saída das sessões da KDL. É geralmente uma boa ideia anexá-lo ao tíquete do Trac relacionado ao kernel. O relatório do sistema é gravado no arquivo <span class="path">/boot/common/var/log/syslog</span>. Uma vez que gravar um arquivo requer um sistema funcional, a saída mais recente deve não ter sido feita ao relatório de sistema quando um problema de kernel ocorre (particularmente em reinicializações espontâneas ou sessões descontinuadas da KDL).</p>
|
||||
<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog persistent. If the option <span class="menu">Save syslog from previous session during boot</span> is activated in the boot loader options (as it is by default), you'll find the syslog of your last session as <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
If you're not able to boot to get to the previous_syslog, you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
|
||||
In the boot loader's <span class="menu">Debug menu</span> you should find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. Note: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
@@ -156,10 +156,10 @@ Uma ou mais páginas de texto serão exibidas na tela, apenas as últimas poucas
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>Uma lista detalhada do seu dispositivo, incluindo fornecedor e id's pci, similar ao <span class="cli">lshw</span> e <span class="cli">lspci</span> do Linux.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Supondo que seja um problema relacionado a USB, é similar ao <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>O relatório primário de sistema utilizado pelo Haiku, parecido com a depuração na tela durante a inicialização. Com o comando <span class="cli">open</span> pode-se cortar a parte relevante do relatório de sistema em um editor de texto.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, see <a href="#syslog">Syslog</a> above, 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>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>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option, see <a href="#onscreen">above</a>).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>Os primeiros quatro comandos são executados no Terminal. Adicione um <span class="cli"> > output.txt</span> após um comando e ele será direcionado para um arquivo de texto chamado "output.txt" que pode ser anexado a seu relatório de erro ou mensagem de correio eletrônico.</p>
|
||||
|
||||
@@ -87,7 +87,7 @@ After you have established that it's a unique bug, make your information as accu
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (x86_gcc2, x86_64). 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>
|
||||
@@ -95,17 +95,17 @@ After you have established that it's a unique bug, make your information as accu
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Application bugs</a></h2>
|
||||
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
|
||||
<p>When an application crashed, you can either save a report or write a core file (both saved to the Desktop) that you can attach to a bugreport, or you can evoke the <a href="../../userguide/pt_PT/applications/debugger.html">Debugger</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Server bugs</a></h2>
|
||||
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
|
||||
<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 the Debugger will be started in text-mode, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and Debugger 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.<br />
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> and then press the power button once to try shutting cleanly down.</p>
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> or <span class="cli">write-core</span> for a core file, and then press the power button once to try shutting cleanly down. If the power button doesn't work, there are also the commands <span class="cli">shutdown</span> and <span class="cli">reboot</span>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Kernel bugs</a></h2>
|
||||
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<p>Kernel bugs are usually the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<ul>
|
||||
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
|
||||
<li><p>The system reboots spontaneously.</p></li>
|
||||
@@ -117,13 +117,13 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>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> (<span class="key">SysReq</span> being the <span class="key">Print</span> key, normally).<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, with USB keyboards it depends on the type of USB controller (UHCI/EHCI). Generally, the keyboard should be plugged into the port directly, not via any hubs. In some circumstances, the keyboard only works if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
|
||||
<tr><td><span class="cli">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace. If the system entered KDL on its own 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 class="onelinetop"><span class="cli">co</span> (aka <span class="cli">continue</span>)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
|
||||
</table>
|
||||
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
@@ -132,7 +132,7 @@ 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 />
|
||||
<p><b>This is the preferred method for extracting 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 />
|
||||
@@ -141,7 +141,7 @@ In the boot loader's <span class="menu">Debug menu</span> you should find the en
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">On screen debug output</a></h3>
|
||||
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog</span> option doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../userguide/pt_PT/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
@@ -152,13 +152,13 @@ One or more pages of text will display on the screen, only the last few lines ne
|
||||
<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>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, see <a href="#syslog">Syslog</a> above, 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 colspan="3">- On screen debug output (a safe mode boot time option, see <a href="#onscreen">above</a>).</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>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 "<tt>output.txt</tt>" that you can attach to your bug report or email.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">What's next?</a></h2>
|
||||
|
||||
@@ -89,7 +89,7 @@ After you have established that it's a unique bug, make your information as accu
|
||||
<ul>
|
||||
<li><p>Încercați să replicați problema pe o revizie curentă a Haiku. Imaginile pre-compilate în scopul testării sunt <a href="http://download.haiku-os.org">disponibile</a> online.</p></li>
|
||||
<li><p>Includeți informații de bază, cum ar fi modul în care testați Haiku (pe hardware real, pe VMWare, pe QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (x86_gcc2, x86_64). 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>
|
||||
@@ -97,17 +97,17 @@ After you have established that it's a unique bug, make your information as accu
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Defecțiuni de aplicație</a></h2>
|
||||
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
|
||||
<p>When an application crashed, you can either save a report or write a core file (both saved to the Desktop) that you can attach to a bugreport, or you can evoke the <a href="../../userguide/ro/applications/debugger.html">Debugger</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Defecțiuni de server</a></h2>
|
||||
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
|
||||
<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 the Debugger will be started in text-mode, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and Debugger 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.<br />
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> and then press the power button once to try shutting cleanly down.</p>
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> or <span class="cli">write-core</span> for a core file, and then press the power button once to try shutting cleanly down. If the power button doesn't work, there are also the commands <span class="cli">shutdown</span> and <span class="cli">reboot</span>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Defecțiuni de kernel</a></h2>
|
||||
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<p>Kernel bugs are usually the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<ul>
|
||||
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
|
||||
<li><p>Sistemul repornește spontan.</p></li>
|
||||
@@ -119,11 +119,11 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>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> (<span class="key">SysReq</span> being the <span class="key">Print</span> key, normally).<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, with USB keyboards it depends on the type of USB controller (UHCI/EHCI). Generally, the keyboard should be plugged into the port directly, not via any hubs. In some circumstances, the keyboard only works if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>KDL în sine este un fel de shell. Se pot executa comenzi care tipăresc informații despre sistem. Următoarele comenzi pot fi de interes:</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">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace. If the system entered KDL on its own 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>
|
||||
@@ -134,7 +134,7 @@ 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 />
|
||||
<p><b>This is the preferred method for extracting 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 />
|
||||
@@ -143,7 +143,7 @@ In the boot loader's <span class="menu">Debug menu</span> you should find the en
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">Rezultatul depanării pe ecran</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 />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog</span> option doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../userguide/ro/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
@@ -154,13 +154,13 @@ One or more pages of text will display on the screen, only the last few lines ne
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>O listare detaliată de hardware, care include vânzătorul și id-uri pci, similar cu <span class="cli">lshw</span> și <span class="cli">lspci</span> din Linux.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Se presupune că este o problemă legată de USB, similar cu <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>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, see <a href="#syslog">Syslog</a> above, 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>Listează toate driverele utilizate.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Disponibil doar în <i>Kernel Debugging Land</i> (vedeți mai sus). Afișează utilizarea interrupt. Nu ar trebui să fie prea multe care sunt partajate de dispozitive diferite.</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option).</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option, see <a href="#onscreen">above</a>).</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>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 "<tt>output.txt</tt>" that you can attach to your bug report or email.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">Ce urmează?</a></h2>
|
||||
|
||||
@@ -12,10 +12,10 @@
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* Michael Smirnov
|
||||
* Sergei Reznikov
|
||||
* Rodastahm Islamov
|
||||
* Humdinger
|
||||
* Michael Smirnov
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -92,7 +92,7 @@
|
||||
<ul>
|
||||
<li><p>Попытайтесь воспроизвести вашу проблему на текущей ревизии Haiku. Готовые образы для тестирования доступны <a href="http://haiku-files.org/">здесь</a>.</p></li>
|
||||
<li><p>Включите информацию о том как вы тестируете Haiku (на реальном компьютере, в эмуляторе VMWare, QEMU, и т. д.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (x86_gcc2, x86_64). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Опишите проблему, с которой вы столкнулись, попытайтесь описать её наиболее точно: как именно она проявилась, и как правильно должен бы был действовать проблемный объект при её отсутствии.</p></li>
|
||||
<li><p>Расскажите какие шаги нужно выполнить для её возникновения, что поможет разработчикам воспроизвести эту ошибку.</p></li>
|
||||
<li><p>Прикрепите всю имеющуюся информацию. Если это ошибка графического интерфейса или баг в каком-либо приложении, то попытайтесь сделать скриншот клавишей <span class="key">Print Screen</span> key.</p></li>
|
||||
@@ -100,13 +100,13 @@
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Ошибки приложений</a></h2>
|
||||
<p>Когда приложение аварийно завершилось, вы должны запустить отладчик из окна сообщения о падении программы. Откроется окно Терминала с запущенным gdb (the GNU debugger). Введя в окне терминала <span class="cli">bt</span>, вы создадите "трассировку", которую необходимо полностью скопировать (включая текст, который уже был до ввода команды <span class="cli">bt</span>) и прикрепить ее в ваш багрепорт.</p>
|
||||
<p>When an application crashed, you can either save a report or write a core file (both saved to the Desktop) that you can attach to a bugreport, or you can evoke the <a href="../../userguide/ru/applications/debugger.html">Debugger</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Ошибки серверов</a></h2>
|
||||
<p>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 />
|
||||
<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 the Debugger will be started in text-mode, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and Debugger 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.<br />
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> and then press the power button once to try shutting cleanly down.</p>
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> or <span class="cli">write-core</span> for a core file, and then press the power button once to try shutting cleanly down. If the power button doesn't work, there are also the commands <span class="cli">shutdown</span> and <span class="cli">reboot</span>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Ошибки ядра</a></h2>
|
||||
@@ -123,11 +123,11 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Царство отладки ядра - KDL</a>
|
||||
</h3>
|
||||
<p>Когда какой-либо системный низкоуровневый компонент вызывает фатальную ошибку, то вы, с большой долей вероятности, окажетесь в отладчике ядра. Также он может быть вызван намеренно при нажатии на клавиши <span class="key">ALT</span>+<span class="key">SysReq</span>+<span class="key">D</span> (клавиша <span class="key">SysReq</span> называется <span class="key">PrintScreen</span> на большинстве клавиатур).
|
||||
Учтите, что ваша клавиатура может не работать в KD. PS/2 клавиатуры работают всегда, USB клавиатуры, подключенные через UHCI контроллер работают, только если вы входили в KDL через клавиатурное сочетание хотя бы раз. USB OHCI не поддерживаются в данный момент.</p>
|
||||
<p>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> (<span class="key">SysReq</span> being the <span class="key">Print</span> key, normally).<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, with USB keyboards it depends on the type of USB controller (UHCI/EHCI). Generally, the keyboard should be plugged into the port directly, not via any hubs. In some circumstances, the keyboard only works if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>Сам по себе KDL является некой оболочкой. Вы можете выполнять команды, которые выводят информацию о системе. Следующие команды могут быть интересны:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (синоним sc)</td><td> </td><td><span class="cli">bt</span> - покажет трассировку, уточняющую где именно произошла ошибка.
|
||||
<tr><td><span class="cli">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td><span class="cli">bt</span> - покажет трассировку, уточняющую где именно произошла ошибка.
|
||||
Если система вошла в KDL самопроизвольно, всегда используйте эту команду.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td><span class="cli">int</span> - отобразит обработанные и необработанные прерывания.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (синоним continue)</td><td> </td><td>выведет систему из отладчика ядра продолжит нормальную работу Haiku, если это возможно.</td></tr>
|
||||
@@ -139,7 +139,7 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
|
||||
|
||||
<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 />
|
||||
<p><b>This is the preferred method for extracting 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 />
|
||||
@@ -159,10 +159,10 @@ In the boot loader's <span class="menu">Debug menu</span> you should find the en
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td><span class="cli">listdev</span> - подробный список оборудования, включающий ID производителей и отдельных устройств, схожа с командами Linux <span class="cli">lshw</span> и <span class="cli">lspci</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td><span class="cli">listusb -v</span> - используйте при ошибке, связанной с USB, аналогична команде <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td><span class="cli">open /var/log/syslog</span> - основной системный лог, используемый Haiku. С командой <span class="cli">open</span> можно вырезать нужную часть лога в текстовом редакторе.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, see <a href="#syslog">Syslog</a> above, 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><span class="cli">listimage | grep drivers/</span> - список всех загруженных драйверов.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td><span class="cli">ints</span> - доступна только в режиме <i>Царства отладки ядра (Kernel Debugging Land - KDL)</i> (см. выше). Отображает используемые прерывания. Не должно быть слишком много устройств, использующих одно прерывание.</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (опция загрузочного меню).</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option, see <a href="#onscreen">above</a>).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>Все эти команды вводятся в терминале, если не указано иное. Если добавить <span class="cli"> > output.txt</span> после команды, то результат её работы сохранится в текстовый файл "output.txt", который можно прикрепить к своему сообщению об ошибке или отправить по электронной почте.</p>
|
||||
|
||||
@@ -90,7 +90,7 @@ Potom, ako ste sa uistili, že chyba je jedinečná, uveďte čo najpresnejšie
|
||||
<ul>
|
||||
<li><p>Pokúste sa reprodukovať problém v aktuálnej revízii Haiku. Sú pripravené <a href="http://haiku-files.org/">obrazy na testovacie účely</a>.</p></li>
|
||||
<li><p>iveďte základné infomrácie o tom ako testujete Haiku (na skutočnom hardvéri, vo VMWare, v QEMU atď.).</p></li>
|
||||
<li><p>Uveďte, ktorú revíziu používate. Túto informáciu nájdete v dialógu <span class="menu">O Haiku...</span> z menu Panela. Tiež uvete, aký druh Haiku testujete (gcc2, gcc4, gcc2hybrid, gcc4hybrid). Obrazy na stiahnutie sú podľa toho pomenované; pri obraze, ktorý ste zostavili sami by ste mali vedieť ako ste ho zostavili.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (x86_gcc2, x86_64). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Popíšte váš problém. Skúste byč čo najpresnejší: popíšte správanie, ktoré ste očakávali a správanie, ktoré ste dostali.</p></li>
|
||||
<li><p>Popíšte kroky, ktoré je potrebné vykonať na vyvolanie chyby. To pomôže vývojárom chybu reprodukovať.</p></li>
|
||||
<li><p>Priložte všetky informácie,ktoré máte k dispozícii. Ak je to chyba používateľského rozhrania alebo chyba v niektorej z aplikácií, skúste urobiť snímku obrazovky stlačením klávesu <span class="key">Print Screen</span>.</p></li>
|
||||
@@ -98,13 +98,13 @@ Potom, ako ste sa uistili, že chyba je jedinečná, uveďte čo najpresnejšie
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Chyby aplikácií</a></h2>
|
||||
<p>Keď aplikácia havaruje, mali by ste vyvolať ladiaci nástroj z upozornenia, ktoré vyskočí. To otvorí okno Terminálu, v ktorom beží gdb (GNU debugger). Zadaním <span class="cli">bt</span> vytvoríte „backtrace“, ktorý by ste mali kompletne skopírovať (vrátane časti zorbazenej než ste zadali príkaz <span class="cli">bt</span>) a priložiť ho k hláseniu.</p>
|
||||
<p>When an application crashed, you can either save a report or write a core file (both saved to the Desktop) that you can attach to a bugreport, or you can evoke the <a href="../../userguide/sk/applications/debugger.html">Debugger</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Chyby serverov</a></h2>
|
||||
<p>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 />
|
||||
<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 the Debugger will be started in text-mode, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and Debugger 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.<br />
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> and then press the power button once to try shutting cleanly down.</p>
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> or <span class="cli">write-core</span> for a core file, and then press the power button once to try shutting cleanly down. If the power button doesn't work, there are also the commands <span class="cli">shutdown</span> and <span class="cli">reboot</span>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Chyby jadra</a></h2>
|
||||
@@ -120,11 +120,11 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>Ak systém sám nevstúpil do KDL, môžete ho úmyselne vyvolať klávesovou skratkou <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Pamätajte, že v KDL vaša klávesnica nemusí fungovať. Klávesnice PS/2 fungujú vždy, klávesnice USB pripojené prostredníctvom ovládačov UHCI fungujú iba ak už aspoň raz ste vstúpili do KDL použitím klávesovej skratky. USB OHCI momentálne nie je podporované.</p>
|
||||
<p>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> (<span class="key">SysReq</span> being the <span class="key">Print</span> key, normally).<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, with USB keyboards it depends on the type of USB controller (UHCI/EHCI). Generally, the keyboard should be plugged into the port directly, not via any hubs. In some circumstances, the keyboard only works if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>Samotné KDL je istým druhom shellu. Môžete vykonávať príkazy, ktoré vypisujú informácie o systéme. Nasledovné príkazy môžu byť zaujímavé:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (resp. sc)</td><td> </td><td>Vypíše backtrace. Ak systém svojvoľne vstúpil do KDL, vždy ho spustite.</td></tr>
|
||||
<tr><td><span class="cli">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>Vypíše backtrace. Ak systém svojvoľne vstúpil do KDL, vždy ho spustite.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>Zobrazí ošetrené a neošetrené hardvérové prerušenia.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (resp. continue)</td><td> </td><td>Opustí ladenie jadra a pokračuje v normálnej prevádzke systému ak je to možné.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Okamžite reštartuje systém. Stratíte všetky neuložené dáta a aj tie, ktoré už boli uložené, ale zatiaľ neboli zapísané na disk.</td></tr>
|
||||
@@ -144,7 +144,7 @@ V <span class="menu">menu Ladenie</span> zavádzača by ste mali nájsť položk
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">Výstup ladenia na obrazovku</a></h3>
|
||||
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog</span> option doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../userguide/sk/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
@@ -155,10 +155,10 @@ One or more pages of text will display on the screen, only the last few lines ne
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>Podrobný výpis vášho hardvéru vrátane dodávateľa a PCI ID, podobný ako <span class="cli">lshw</span> a <span class="cli">lspci</span> v Linuxe.</td></tr>
|
||||
<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Za predpokladu, že sa problém týka USB, je podobný ako <span class="cli">lsusb</span>.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Primárny protokol systému, ktorý Haiku používa, podobný ladeniu na obrazovku počas štartu systému. Príkazom <span class="cli">open</span> môžete vystrihnúť relevantnú časť syslogu v textovom editore.</td></tr>
|
||||
<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, see <a href="#syslog">Syslog</a> above, 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>Vypíše všetky použité ovládače.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Dostupné iba v rámci <i>(KDL) Kernel Debugging Land</i> (pozri vyššie). Zobrazuje použitie prerušení. Nemalo by sa vyskytovať mnoho takých, ktoré používajú viaceré zariadenia.</td></tr>
|
||||
<tr><td colspan="3">- Ladiaci výstup na obrazovke (voľba Bezpečný režim počas štartu systému).</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option, see <a href="#onscreen">above</a>).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>Prvé štyri príkazy sú zadané do Terminálu. Keď za príkaz pridáte <span class="cli"> > output.txt</span>, výstup sa zapíše do textového súboru s názvom „output.txt“, ktorý môžete priložiť k vášmu hláseniu chyby alebo emailu.</p>
|
||||
|
||||
@@ -89,7 +89,7 @@ After you have established that it's a unique bug, make your information as accu
|
||||
<ul>
|
||||
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are <a href="http://download.haiku-os.org">available</a> online.</p></li>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (x86_gcc2, x86_64). 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>
|
||||
@@ -97,17 +97,17 @@ After you have established that it's a unique bug, make your information as accu
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">Programbuggar</a></h2>
|
||||
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
|
||||
<p>When an application crashed, you can either save a report or write a core file (both saved to the Desktop) that you can attach to a bugreport, or you can evoke the <a href="../../userguide/sv_SE/applications/debugger.html">Debugger</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Serverbuggar</a></h2>
|
||||
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
|
||||
<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 the Debugger will be started in text-mode, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and Debugger 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.<br />
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> and then press the power button once to try shutting cleanly down.</p>
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> or <span class="cli">write-core</span> for a core file, and then press the power button once to try shutting cleanly down. If the power button doesn't work, there are also the commands <span class="cli">shutdown</span> and <span class="cli">reboot</span>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Buggar i kärnan</a></h2>
|
||||
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<p>Kernel bugs are usually the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
|
||||
<ul>
|
||||
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
|
||||
<li><p>The system reboots spontaneously.</p></li>
|
||||
@@ -119,13 +119,13 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
|
||||
<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>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> (<span class="key">SysReq</span> being the <span class="key">Print</span> key, normally).<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, with USB keyboards it depends on the type of USB controller (UHCI/EHCI). Generally, the keyboard should be plugged into the port directly, not via any hubs. In some circumstances, the keyboard only works if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
|
||||
<tr><td><span class="cli">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace. If the system entered KDL on its own 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 class="onelinetop"><span class="cli">co</span> (aka <span class="cli">continue</span>)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
|
||||
</table>
|
||||
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
|
||||
@@ -134,7 +134,7 @@ 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 />
|
||||
<p><b>This is the preferred method for extracting 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 />
|
||||
@@ -143,7 +143,7 @@ In the boot loader's <span class="menu">Debug menu</span> you should find the en
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">On screen debug output</a></h3>
|
||||
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog</span> option doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
|
||||
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
|
||||
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../userguide/sv_SE/bootloader.html">Boot Loader</a>.</p>
|
||||
|
||||
@@ -154,13 +154,13 @@ One or more pages of text will display on the screen, only the last few lines ne
|
||||
<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>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, see <a href="#syslog">Syslog</a> above, 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 colspan="3">- On screen debug output (a safe mode boot time option, see <a href="#onscreen">above</a>).</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>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 "<tt>output.txt</tt>" that you can attach to your bug report or email.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="next" name="next">Vad händer sen?</a></h2>
|
||||
|
||||
@@ -56,6 +56,7 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">Переклад даної сторінки ще неповний. Допоки це так, незавершені частини користайте у англійському варіанті. </div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Зміст</td></tr>
|
||||
@@ -88,7 +89,7 @@
|
||||
<ul>
|
||||
<li><p>Спробуйте відтворити проблему на поточній версії Haiku. Передналаштовані образи для цілей тестування <a href="http://download.haiku-os.org">доступні</a> в інтернеті.</p></li>
|
||||
<li><p>Повідомте основну інформацію про те як Ви тестуєте Haiku (на реальному залізі, у VMWare, у QEMU і тд).</p></li>
|
||||
<li><p>Уточніть з якою версією Ви працюєте. Інформацію про це можна знайти у пункті меню Deskbar'а <span class="menu">Про Haiku... (About Haiku...)</span>. Також вкажіть вид збірки Haiku (gcc2, gcc4, gcc2hybrid, gcc4hybrid), яка тестується. Стягнуті з мережі образи відповідно проіменовані, у випадку самостійного збирання Ви повинні знати що збирали.</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (x86_gcc2, x86_64). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>Опишіть проблему яка Вас спіткала. Постарайтесь бути якомога точнішим: опишіть реальну поведінку та ту яку Ви очікуєте.</p></li>
|
||||
<li><p>Опишіть які кроки необхідно виконати для того, щоб натрапити на помилку. Це допоможе розробникам відтворити її.</p></li>
|
||||
<li><p>Вкладіть всю інформацію яка у Вас є. Якщо це помилка графічного інтерфейсу або помилка одного з додатків спробуйте при можливості зробити знімок екрану натиснувши клавішу <span class="key">PRINT</span>.</p></li>
|
||||
@@ -96,14 +97,13 @@
|
||||
|
||||
<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>When an application crashed, you can either save a report or write a core file (both saved to the Desktop) that you can attach to a bugreport, or you can evoke the <a href="../../userguide/uk/applications/debugger.html">Debugger</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">Помилки у серверах</a></h2>
|
||||
<p>Коли зазнають краху життєво важливі сервери такі як: app server, registrar або input server Ви не побачите звичного попередження про аварію. Замість нього екран очиститься стане білим та стартує сесія відладчика gdb, його вихід з'явиться безпосередньо на екрані. Можливо Ви надалі зможете рухати курсором мишки який затиратиме на екрані біле тло та рядки виводу відладчика. Працюючі додатки (такі як, наприклад, ProcessController або годинник в Deskbar) також можуть малювати поверх виведення відладчика на екрані.<br />
|
||||
До того ж, все буде виглядати так само незграбно та жахливо як і при помилках додатків. Найважливіше тепер отримати зворотнє трасування (командою <span class="cli">bt</span>). Ви можете зробити знімок екрану цифровою камерою, бо текст gdb скоріше всього скопіювати не вдасться.<br />
|
||||
В залежності від того що зазнало краху можна спробувати зберегти звіт про помилку на робочому столі ввівши команду <span class="cli">save-report</span>, а після цього натиснути кнопку живлення один раз щоб спробувати акуратно завершити роботу.</p>
|
||||
<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 the Debugger will be started in text-mode, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and Debugger 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.<br />
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> or <span class="cli">write-core</span> for a core file, and then press the power button once to try shutting cleanly down. If the power button doesn't work, there are also the commands <span class="cli">shutdown</span> and <span class="cli">reboot</span>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">Помилки у ядрі</a></h2>
|
||||
@@ -119,11 +119,11 @@
|
||||
|
||||
<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 клавіатури працюватимуть завжди, USB клавіатури підключені до контролерів UHCI спрацюють для входу у KDL тільки один раз. Клавіатури USB OHCI на даний момент у цьому режимі не працюють.</p>
|
||||
<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> (<span class="key">SysReq</span> being the <span class="key">Print</span> key, normally).<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, with USB keyboards it depends on the type of USB controller (UHCI/EHCI). Generally, the keyboard should be plugged into the port directly, not via any hubs. In some circumstances, the keyboard only works if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>Сама KDL є свого роду оболонкою. Можна виконувати команди, які надають інформацію про систему. Можуть бути цікавими наступні команди :</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>виводити зворотнє трасування. Якщо система потрапила у KDL за власним бажанням завжди набирайте цю команду.</td></tr>
|
||||
<tr><td><span class="cli">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>виводити зворотнє трасування. Якщо система потрапила у KDL за власним бажанням завжди набирайте цю команду.</td></tr>
|
||||
<tr><td><span class="cli">ints</span></td><td> </td><td>показати оброблені та необроблені переривання апаратного забезпечення.</td></tr>
|
||||
<tr><td class="onelinetop"><span class="cli">co</span> (aka continue)</td><td> </td><td>залишити територію відладки ядра та продовжити при можливості роботу системи.</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>негайно перезавантажує систему. Будуть втрачені всі незбережені дані і навіть ті, які були збережені, але ще не були записані назад на диск.</td></tr>
|
||||
@@ -154,10 +154,10 @@
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td>- <span class="cli">listdev</span></td><td> </td><td>детальний список Вашого апаратного забезпечення, включаючи визначники vendor id та 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, аналогічно <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">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, see <a href="#syslog">Syslog</a> above, 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>перелічує всі драйвери які використовуються.</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>Доступне тільки зсередини <i>Території відладки ядра (Kernel Debugging Land)</i> (дивись вище). Показує використання переривань. Не повинно бути занадто багато таких, які спільно використовують різні пристрої.</td></tr>
|
||||
<tr><td colspan="3">- Екранний вивід відладки (On screen debug output) (опція безпечного режиму під час завантаження).</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option, see <a href="#onscreen">above</a>).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>Перші чотири команди вводяться в Терміналі. Додайте <span class="cli"> > output.txt</span> після команди, і це конвеєрує вивід в текстовий файл з ім'ям "output.txt", який ви можете прикріпити до зголошення про помилку або до електронного листа.</p>
|
||||
|
||||
@@ -11,8 +11,8 @@
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Paco Rivière
|
||||
* Humdinger
|
||||
* Paco Rivière
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -24,7 +24,7 @@
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
<div><span>Manual d'usuari</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
@@ -56,7 +56,7 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
<div class="box-info">La traducció d'aquesta pàgina encara no està acabada. Fins que ho sigui, algunes part correspondrà a la versió anglesa.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Índex</td></tr>
|
||||
@@ -73,16 +73,16 @@
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Benvingut al Haiku!</a></h2>
|
||||
<p>Thank you very much for checking out Haiku! This is our fourth public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a hrf="https://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
<p>Thanks for checking out Haiku! This is our fifth public release. We hope to attract new developers to our project and give users a chance to check out Haiku. While this first <i>beta release</i> includes all major features planned for the final Haiku release, it still has many bugs and a few rough edges that need further polishing. However, we think that this release is quite usable and hope it lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a href="https://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Atenció amb els Errors de programació</a></h2>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.</div>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being a beta release, there are bound to be some left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using beta versions as a production system. Your data could be altered, mangled or downright destroyed. Keep up-to-date backups!</div>
|
||||
|
||||
<p>One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<p>One of the main reasons for releasing a beta version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="https://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
|
||||
<li><a href="ca/bugreports.html">Tips for a helpful bug report</a></li>
|
||||
@@ -133,13 +133,13 @@ Deviations from the BeOS API and Haiku specific additions are collected in the H
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Com contactar</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="https://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to be established to keep communication effective. Please respect our <a href="https://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<ul>
|
||||
<li><a href="https://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
|
||||
<li><a href="https://www.haiku-os.org/forum" class="printurl">Forums</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/ml" class="printurl">Overview of all mailing lists</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
@@ -11,8 +11,8 @@
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Matthias
|
||||
* Humdinger
|
||||
* Matthias
|
||||
* taos
|
||||
*
|
||||
-->
|
||||
@@ -25,7 +25,7 @@
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
<div><span>User Guide</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
@@ -73,16 +73,16 @@
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Willkommen zu Haiku!</a></h2>
|
||||
<p>Danke, für das Interesse an Haiku! Wir hoffen, dass wir durch die vierte öffentliche Version neue Entwickler für unser Projekt begeistern können und Anwendern die Möglichkeit geben, Haiku kennenzulernen. Natürlich ist diese <i>Alpha Version</i> noch nicht vollständig oder gar fehlerfrei, und sie erfüllt auch noch nicht die Ziele, die wir uns selbst gesteckt haben. Sie zeigt jedoch warum wir uns in diesem Projekt so engagieren und es ermöglicht anderen, das große Potential von Haiku zu erkunden.</p>
|
||||
<p>Danke, für das Interesse an Haiku! Wir hoffen, dass wir durch diese fünfte offizielle Version neue Entwickler für unser Projekt begeistern können und Anwendern die Möglichkeit geben, Haiku kennenzulernen. Während diese <i>Beta Version</i> schon alle größeren Features zeigt, die für die Endversion geplant sind, enthält sie auch noch einige Fehler und ist an einigen Stellen noch verbesserungsfähig. Haiku ist jedoch schon sehr gut benutzbar und ermöglicht allen das große Potential von Haiku zu erkunden. </p>
|
||||
<p>Auf der Projektseite <a hrf="https://www.haiku-os.org">Haiku-os.org</a> finden sich immer die neuesten Ankündigungen und Entwicklungen.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Achtung, Bugs!</a></h2>
|
||||
<p>Wir haben uns sehr bemüht eventuell schwerwiegende Fehler zu beseitigen. Da es sich aber trotz allem um eine Alpha-Version handelt, kann man davon ausgehen, dass noch genügend unentdeckte Fehler vorhanden sind.</p>
|
||||
<div class="box-warning">Diese Alpha-Version sollte nicht für wirklich kritische Aufgaben verwendet werden! Obwohl unwahrscheinlich, kann Datenverlust nicht ausgeschlossen werden!</div>
|
||||
<p>Wir haben uns sehr bemüht eventuell schwerwiegende Fehler zu beseitigen. Da es sich aber trotz allem um eine Beta-Version handelt, kann man davon ausgehen, dass auch noch einige unentdeckte Fehler vorhanden sind.</p>
|
||||
<div class="box-warning">Diese Beta-Version sollte nicht für wirklich kritische Aufgaben verwendet werden. Obwohl unwahrscheinlich, kann Datenverlust nicht ausgeschlossen werden. Regelmäßige Backups sind angeraten!</div>
|
||||
|
||||
<p>Einer der Hauptgründe für diese Alpha-Version ist, das System möglichst vielen Leuten zum Testen anbieten zu können. Nur so ist es möglich, alle Fehler zu finden und Verbesserungsvorschläge zu erhalten. Deshalb sollte nicht gezögert werden, Fehler auch im Bug Tracker zu melden (nachdem man dessen Suchfunktion benutzt hat, um Doppeleinträge zu vermeiden).</p>
|
||||
<p>Einer der Hauptgründe für diese Beta-Version ist, das System möglichst vielen Leuten zum Testen anbieten zu können. Nur so ist es möglich, alle Fehler zu finden und Verbesserungsvorschläge zu erhalten. Deshalb sollte nicht gezögert werden, Fehler dem Bug Tracker zu melden (nachdem man dessen Suchfunktion benutzt hat, um Doppeleinträge zu vermeiden).</p>
|
||||
<ul>
|
||||
<li><a href="https://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
|
||||
<li><a href="de/bugreports.html">Tipps für einen sinnvollen Fehler-Report</a></li>
|
||||
@@ -137,9 +137,9 @@ Abweichungen von der BeOS API und Haiku-spezifische Erweiterungen werden im Haik
|
||||
<ul>
|
||||
<li><a href="https://www.haiku-os.org/community/irc" class="printurl">IRC Kanäle</a></li>
|
||||
<li><a href="https://www.haiku-os.org/forum" class="printurl">Foren</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Mailingliste für allgemeine Haiku Themen</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Mailingliste für Programmierer von Haiku selbst</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailingliste für Programmierer von Software für Haiku</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku" class="printurl">Mailingliste für allgemeine Haiku Themen</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-development" class="printurl">Mailingliste für Programmierer von Haiku selbst</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailingliste für Programmierer von Software für Haiku</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/ml" class="printurl">Alle Mailinglisten</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
@@ -69,16 +69,16 @@
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Welcome to Haiku!</a></h2>
|
||||
<p>Thank you very much for checking out Haiku! This is our fourth public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a hrf="https://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
<p>Thanks for checking out Haiku! This is our fifth public release. We hope to attract new developers to our project and give users a chance to check out Haiku. While this first <i>beta release</i> includes all major features planned for the final Haiku release, it still has many bugs and a few rough edges that need further polishing. However, we think that this release is quite usable and hope it lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a href="https://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Beware of Bugs</a></h2>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.</div>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being a beta release, there are bound to be some left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using beta versions as a production system. Your data could be altered, mangled or downright destroyed. Keep up-to-date backups!</div>
|
||||
|
||||
<p>One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<p>One of the main reasons for releasing a beta version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="https://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
|
||||
<li><a href="en/bugreports.html">Tips for a helpful bug report</a></li>
|
||||
@@ -129,13 +129,13 @@ Deviations from the BeOS API and Haiku specific additions are collected in the H
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Getting in contact</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="https://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to be established to keep communication effective. Please respect our <a href="https://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<ul>
|
||||
<li><a href="https://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
|
||||
<li><a href="https://www.haiku-os.org/forum" class="printurl">Forums</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/ml" class="printurl">Overview of all mailing lists</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
@@ -11,10 +11,10 @@
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Oscar Carballal
|
||||
* miguel~1.mx
|
||||
* Humdinger
|
||||
* kervas
|
||||
* miguel~1.mx
|
||||
* Oscar Carballal
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -26,7 +26,7 @@
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
<div><span>Guía del usuario</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
@@ -58,7 +58,7 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
<div class="box-info">La traducción de esta página no está completa aún. Hasta que esté, las partes sin traducir se muestran en el inglés original.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Contenido</td></tr>
|
||||
@@ -75,16 +75,16 @@
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">¡Bienvenido a Haiku!</a></h2>
|
||||
<p>Gracias por probar Haiku. Este es nuestro cuarto lanzamiento público. Esperamos atraer nuevos desarrolladores a nuestro proyecto y darle a los futuros usuarios una oportunidad para probar Haiku. Estamos conscientes de que esta <i>versión alpha</i> no cumple del todo los objetivos que nos hemos propuesto y no ofrece todas las características ni la experiencia de usuario bien formulada que fueron planificadas para la versión R1 final. No obstante, esperamos que esta versión le permita descubrir el gran potencial de Haiku, y que comparta nuestro entusiasmo.</p>
|
||||
<p>Thanks for checking out Haiku! This is our fifth public release. We hope to attract new developers to our project and give users a chance to check out Haiku. While this first <i>beta release</i> includes all major features planned for the final Haiku release, it still has many bugs and a few rough edges that need further polishing. However, we think that this release is quite usable and hope it lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visite el sitio web de nuestro proyecto <a hrf="https://www.haiku-os.org">Haiku-os.org</a> para ver los últimos anuncios y noticias.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Cuidado con los fallos</a></h2>
|
||||
<p>Hemos trabajado muy duro para arreglar todos los fallos más críticos, sin embargo, ya que es una versión alpha, es muy probable que haya muchos por descubrir.</p>
|
||||
<div class="box-warning">No se recomienda el uso de versiones alfa en sistemas de producción. Su información bien podría alterarse, estropearse o destruirse.</div>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being a beta release, there are bound to be some left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using beta versions as a production system. Your data could be altered, mangled or downright destroyed. Keep up-to-date backups!</div>
|
||||
|
||||
<p>Una de las razones principales para liberar una versión alpha es atraer a mucha gente para probar el sistema y descubrir fallos o darnos sugerencias para futuras mejoras. Por favor, archive los fallos y mejoras en nuestro bug tracker después de utilizar su sistema de búsqueda para evitar duplicados.</p>
|
||||
<p>One of the main reasons for releasing a beta version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="https://dev.haiku-os.org/wiki" class="printurl">Rastreador de fallos de Haiku</a></li>
|
||||
<li><a href="es/bugreports.html">Consejos para un buen informe de error</a></li>
|
||||
@@ -140,9 +140,9 @@ Las divergencias del API de BeOS y adiciones específicas a Haiku se recopilan e
|
||||
<ul>
|
||||
<li><a href="https://www.haiku-os.org/community/irc" class="printurl">Canales IRC</a></li>
|
||||
<li><a href="https://www.haiku-os.org/forum" class="printurl">Foros</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Lista de correo general</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Lista de correo de desarrollo de Haiku</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Lista de correo para programadores de aplicaciones de terceros</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/ml" class="printurl">Panorama de todas las listas de correo</a>.</li>
|
||||
</ul>
|
||||
|
||||
|
||||
@@ -11,8 +11,8 @@
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Karvjorm
|
||||
* Humdinger
|
||||
* Jorma Karvonen
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -24,7 +24,7 @@
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
<div><span>Käyttäjäopas</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
@@ -56,7 +56,7 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
<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>
|
||||
@@ -72,16 +72,16 @@
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Tervetuloa Haikuun!</a></h2>
|
||||
<p>Kiitoksia oikein paljon, että latasit Haiku-käyttöjärjestelmän! Tämä on neljäs julkinen julkaisumme. Toivomme houkuttelevamme uusia kehittäjiä hankkeeseemme ja antavamme tuleville käyttäjillä mahdollisuuden tutustua Haikuun. Tiedämme, että tämä <i>alfa-julkaisu</i> ei vielä täytä niitä odotuksia, jotka olemme asettaneet itsellemme ja se ei tarjoa kaikkia ominaisuuksia ja lopullisen R1-version täysiä käyttäjäkokemuksia. Toivomme kuitenkin, että tämä julkaisu antaa sinulle mahdollisuuden löytää Haikun suuren potentiaalin ja että jaat meidän innostuksemme.</p>
|
||||
<p>Thanks for checking out Haiku! This is our fifth public release. We hope to attract new developers to our project and give users a chance to check out Haiku. While this first <i>beta release</i> includes all major features planned for the final Haiku release, it still has many bugs and a few rough edges that need further polishing. However, we think that this release is quite usable and hope it lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Vieraile projektimme kotisivulla <a hrf="https://www.haiku-os.org">Haiku-os.org</a> saadaksesi viimeisimmät uutiset ja tiedonannot.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Varo ohjelmistovikoja</a></h2>
|
||||
<p>Olemme työskennelleet kovasti korjataksemme potentiaalisesti kriittiset viat, mutta kuitenkin tämä on ohjelmiston alfa-julkaisu, ja siinä on jäljellä runsaasti löytämättömiä vikoja</p>
|
||||
<div class="box-warning">Emme suosittele käyttämään alfa-versioita tuotantojärjestelmänä. Tietosi voivat aivan hyvin muuttua, vääristyä tai suorastaan tuhoutua.</div>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being a beta release, there are bound to be some left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using beta versions as a production system. Your data could be altered, mangled or downright destroyed. Keep up-to-date backups!</div>
|
||||
|
||||
<p>Yksi pääsyy alfa-versioiden julkaisemiseen on houkutella lisää ihmisiä järjestelmän testaamiseen ja vikojen havaitsemiseen tai tarjota ehdotuksia tulevista laajennuksista. Ilmoita vioista ja laajennuksista vikaseuraajajärjestelmässämme sen jälkeen kun olet käyttänyt sen etsintätoimintoa kaksoiskappaleilmoitusten estämiseksi.</p>
|
||||
<p>One of the main reasons for releasing a beta version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="https://dev.haiku-os.org/wiki" class="printurl">Haiku-vikaseuraaja</a></li>
|
||||
<li><a href="fi/bugreports.html">Vihjeitä hyödyllisiä vikailmoituksia varten</a></li>
|
||||
@@ -106,8 +106,8 @@ Binaari- ja lähdekoodiyhteensopivuuden vuoksi monia BeOS-sovelluksia voidaan su
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="update" name="update">Haikun päivittäminen</a></h2>
|
||||
<p>Updating Haiku as well as third party packages is done with the application <a href="../userguide/fi/applications/softwareupdater.html">SoftwareUpdater</a>. When it's finished, reboot.<br />
|
||||
For more details, see the guide <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Updating your system</a> on our website.</p>
|
||||
<p>Haikun kuten myös kolmansien osapuolten pakkausten päivittäminen tehdään sovelluksella <a href="../userguide/fi/applications/softwareupdater.html">Ohjelmistopäivittäjä</a>. Kun päivitys on valmis, käynnistä järjestelmä uudelleen.<br />
|
||||
Lisätietoja varten katso ohje <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system”">Järjestelmäsi päivittäminen</a> webbisivustollamme.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
@@ -136,9 +136,9 @@ Poikkeavuudet BeOS API:sta ja Haiku-kohtaiset lisäykset on kerätty Haiku-kirja
|
||||
<ul>
|
||||
<li><a href="https://www.haiku-os.org/community/irc" class="printurl">IRC-kanavat</a></li>
|
||||
<li><a href="https://www.haiku-os.org/forum" class="printurl">Foorumit</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Yleinen sähköpostilista</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Haikua itseä koskeva kehityssähköpostilista</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Kolmannen osapuolen sovellusohjelmoijien sähköpostilista</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku" class="printurl">Yleinen sähköpostilista</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-development" class="printurl">Haikua itseä koskeva kehityssähköpostilista</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Kolmannen osapuolen sovellusohjelmoijien sähköpostilista</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/ml" class="printurl">Kaikkien sähköpostilistojen yleiskatsaus</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
@@ -11,9 +11,9 @@
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Vincent Duvert
|
||||
* Loïc
|
||||
* Humdinger
|
||||
* Loïc
|
||||
* Vincent Duvert
|
||||
* Wabouz
|
||||
*
|
||||
-->
|
||||
@@ -26,7 +26,7 @@
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
<div><span>Guide de l’utilisateur</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
@@ -58,7 +58,6 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
@@ -75,18 +74,18 @@
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Bienvenue sur Haiku !</a></h2>
|
||||
<p>Merci beaucoup d’essayer Haiku ! Voici notre quatrième version publique. Nous espérons encourager de nouveaux développeurs à nous rejoindre et donner aux futurs utilisateurs la possibilité d’essayer Haiku. Nous sommes conscients que cette <i>version alpha</i> ne remplit pas tous les objectifs que nous nous sommes fixés et ne fournit pas toutes les fonctionnalités et l’expérience utilisateur attendues pour la version R1 finale. Néanmoins, nous espérons que cette version (même inachevée) vous permettra de découvrir le potentiel de Haiku et de partager notre enthousiasme.</p>
|
||||
<p>Visit our project's website <a hrf="https://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
<p>Merci beaucoup d’essayer Haiku ! Voici notre cinquième version publique. Nous espérons encourager de nouveaux développeurs à nous rejoindre et faire connaître Haiku à de nombreux utilisateurs. Bien que cette <i>version beta</i> comprenne toutes les fonctions majeures prévues pour la version finale, elle contient encore beaucoup de bugs et pas mal de choses ont besoin d'être peaufinées. Néanmoins, nous estimons que cette version est suffisamment utilisable pour vous permettre de découvrir tout le potentiel d’Haiku, et vous espérons que vous partagerez notre enthousiasme.</p>
|
||||
<p>Visitez le site de notre projet <a hrf="http://www.haiku-os.org">Haiku-os.org</a> pour rester informé des dernières évolutions.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Attention aux bogues</a></h2>
|
||||
<p>Nous avons travaillé dur pour résoudre les bogues critiques du système. Néanmoins, Haiku n'étant qu'au stade d'une version alpha, beaucoup n'ont pas encore été découverts.</p>
|
||||
<div class="box-warning">Nous déconseillons l'utilisation des versions Alpha en tant que système pour travailler sur des fichiers/projets/travaux personnels. Les données que vous manipulez pourraient être altérées, corrompues ou tout simplement détruites.</div>
|
||||
<p>Nous avons travaillé dur pour résoudre les bogues critiques du système. Néanmoins, Haiku n'étant qu'au stade d'une version bêta, il y en a sûrement d'autres qui n'ont pas encore été découverts.</p>
|
||||
<div class="box-warning">Nous déconseillons l'utilisation des versions bêta en tant que système de production. Les données que vous manipulez pourraient être altérées, corrompues ou tout simplement détruites. Tenez vos sauvegardes à jour !</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>
|
||||
<p>L’un des principal objectif pour sortie une version bêta, est d’attirer plus de personnes à tester le système, à découvrir des bugs ou à proposer des améliorations futures. Nous vous remercions de bien vouloir soumettre les bugs et les propositions d’améliorations dans notre outil de suivi des bugs, non sans avoir, au préalable, utilisé la fonction de recherche pour éviter les doublons.</p>
|
||||
<ul>
|
||||
<li><a href="https://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
|
||||
<li><a href="https://dev.haiku-os.org/wiki" class="printurl">Traqueur de bogues d’Haiku</a> (en anglais)</li>
|
||||
<li><a href="fr/bugreports.html">Astuces pour un rapport de bogue utile</a></li>
|
||||
</ul>
|
||||
|
||||
@@ -96,53 +95,55 @@
|
||||
<p>Les premières versions de Haiku auront une apparence et des fonctionnalités proches de celles de BeOS R5, le système d'exploitation qu'il tente de ré-implémenter. Si vous ne l'avez jamais essayé, jetez un œil à ces liens :</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/fr/contents.html">Guide utilisateur d'Haiku</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/" class="printurl">List of BeOS/Haiku websites</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/" class="printurl">Liste des sites web consacrés à BeOS/Haiku</a> (en anglais)</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">Installer plus de logiciels</a></h2>
|
||||
<p>La plupart des logiciels disponible peuvent être téléchargés et installés avec l'application HaikuDepot qui est fournie avec Haiku.<br /> Du fait de sa la compatibilité des binaires et des sources, la plupart des applications BeOS tournent sur Haiku. Beaucoup d'entre elles ont été ré-empaquetées pour Haiku ou tournent parfaitement, même sans modification. Vous trouverez plus d'informations sur l'installation de nouveaux programmes dans le guide de l'utilisateur, au chapitre <a href="../userguide/fr/applications.html">Applications</a>.</p>
|
||||
<p>There are several community-based software collections. See the <a href="https://www.haiku-os.org/community/software">Software Sites</a> page on our website.</p>
|
||||
<p>Il existe plusieurs collections de logiciels proposés par la communauté. Veuillez consulter la page des <a href="https://www.haiku-os.org/community/software">Sites de Logiciels</a> sur notre site Web.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="update" name="update">Updating Haiku</a></h2>
|
||||
<p>Updating Haiku as well as third party packages is done with the application <a href="../userguide/fr/applications/softwareupdater.html">SoftwareUpdater</a>. When it's finished, reboot.<br />
|
||||
For more details, see the guide <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Updating your system</a> on our website.</p>
|
||||
<a id="update" name="update">Mettre à jour Haiku</a></h2>
|
||||
<p>La mise à jour d’Haiku ainsi que des paquets tiers se fait à travers l’application <a href="../userguide/fr/applications/softwareupdater.html">SoftwareUpdater</a>. Quand la mise à jour est fini, redémarrez.<br />
|
||||
Pour plus de détails, consultez le guide de <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Mise à jour de votre système</a> sur notre site Web.</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>
|
||||
<p>Haiku gère les réseaux sans fil cryptés en WPA/WPA2 ou WEP et bien sûr les réseaux ouverts non chiffrés. En raison de plusieurs politiques d'octroi de licences de différents fabricants de matériels, une étape manuelle peut-être nécessaire pour installer le firmware. Vous trouverez plus d'informations sur le matériel pris en charge, l'installation du firmware et comment adhérer à un réseau sans fil dans le Guide de l'utilisateur de Haiku <a href="../userguide/fr/workshop-wlan.html">Atelier : Réseaux sans-fils</a>.</p>
|
||||
<p>Haiku gère les réseaux sans fil cryptés en WPA/WPA2 ou WEP et bien sûr les réseaux ouverts non chiffrés. En raison de plusieurs politiques d'octroi de licences de différents fabricants de matériels, une étape manuelle peut-être nécessaire pour installer le firmware. Vous trouverez plus d'informations sur le matériel pris en charge, l'installation du firmware et comment adhérer à un réseau sans fil dans le Guide de l’utilisateur de Haiku <a href="../userguide/fr/workshop-wlan.html">Atelier : Réseaux sans-fils</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="api" name="api">Apprendre à connaître l'API</a></h2>
|
||||
<p>Comme Haiku est une ré-implémentation, l'API est encore la même que celle de BeOS R5 (avec quelques ajouts).
|
||||
Par conséquent, la documentation du BeBook est toujours valable. Nous remercions ACCESS, qui détient les droits de propriété de l'ancien Be Inc, de nous autoriser à fournir une copie du BeBook.<br />
|
||||
<p>Comme Haiku est une ré-implémentation, l’API est encore la même que celle de BeOS R5 (avec quelques ajouts).
|
||||
Par conséquent, la documentation du BeBook est toujours valable. Nous remercions ACCESS, qui détient les droits de propriété de l’ancien Be Inc, de nous autoriser à fournir une copie du BeBook.<br />
|
||||
Les écarts par rapport à l'API BeOS et les ajouts spécifiques à Haiku sont collectés dans le livre Haiku.</p>
|
||||
|
||||
<p>Quelques ressources sont susceptibles de vous aider à commencer :</p>
|
||||
<ul>
|
||||
<li><a href="https://www.haiku-os.org/development/faq" class="printurl">Development FAQ</a></li>
|
||||
<li><a href="https://www.haiku-os.org/development/faq" class="printurl">FAQ Développement</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">Explorer le code source</a></li>
|
||||
<li><a href="https://www.haiku-os.org/legacy-docs/bebook/" class="printurl">The Be Book</a></li>
|
||||
<li><a href="https://www.haiku-os.org/docs/api/" class="printurl">The Haiku Book</a></li>
|
||||
<li><a href="https://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be Newsletter Archive</a></li>
|
||||
<li><a href="https://www.haiku-os.org/legacy-docs/bebook/" class="printurl">Le BeBook</a></li>
|
||||
<li><a href="https://www.haiku-os.org/docs/api" class="printurl">Le Haiku Book</a></li>
|
||||
<li><a href="https://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">L’archive BeNewsletter</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Rester en contact</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="https://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<p>Entrez en contact avec les autres développeurs et utilisateurs, participez aux discussions sur IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> pour le webchat), dans nos forums ou les listes de diffusion.
|
||||
Quand beaucoup de gens différents se rencontrent, des règles doivent êtres établies pour maintenir une communication efficace. Veuillez respecter
|
||||
<a href="http://www.haiku-os.org/community/ml/etiquette">l’étiquette de notre liste de diffusion</a>.</p>
|
||||
<ul>
|
||||
<li><a href="https://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/irc" class="printurl">Canaux IRC</a></li>
|
||||
<li><a href="https://www.haiku-os.org/forum" class="printurl">Forums</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Liste de diffusion générale</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Liste de diffusion concernant le dévelopment de Haiku, lui même</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Liste de diffusion concernant les développeurs d'applications tiers</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/ml" class="printurl">Overview of all mailing lists</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku" class="printurl">Liste de diffusion générale</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-development" class="printurl">Liste de diffusion concernant le développement d’Haiku, lui même</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Liste de diffusion concernant les développeurs d’applications tiers</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/ml" class="printurl">Panorama de toutes les listes de diffusions</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -24,7 +24,7 @@
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
<div><span>Használati útmutató</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
@@ -56,7 +56,7 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
<div class="box-info">Az oldal fordítása még folyamatban van. Amíg tart a fordítás, addig a lefordítatlan részek angolul jelennek meg.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
@@ -73,16 +73,16 @@
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Üdvözöl a Haiku!</a></h2>
|
||||
<p>Köszönjük, hogy kipróbálod a Haiku legújabb hivatalos kiadását. Reméljük, hogy találunk újabb fejlesztőket és felhasználókat, akik tesztelik a szoftvert. Tisztában vagyunk azzal, hogy ez csak egy <i>alfa-verziójú</i> kiadás, ami nem teljesen életképes és nem tartalmaz minden, az R1-es verzióban várható programot és funkciót. Mindazonáltal reméljük, hogy ez a kiadás lehetőséget nyújt a Haiku megismeréséhez, és megmutatja a benne rejlő lehetőségeket.</p>
|
||||
<p>Visit our project's website <a hrf="https://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
<p>Thanks for checking out Haiku! This is our fifth public release. We hope to attract new developers to our project and give users a chance to check out Haiku. While this first <i>beta release</i> includes all major features planned for the final Haiku release, it still has many bugs and a few rough edges that need further polishing. However, we think that this release is quite usable and hope it lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Kérjük látogass el a project oldalára (<a hrf="http://www.haiku-os.org">Haiku-os.org</a>) a legfrissebb hírek és információk miatt.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Előfordulhatnak hibák</a></h2>
|
||||
<p>Keményen dolgozunk azon, hogy minden lehetséges hibát felderítsünk, és kijavítsunk. Alfa-állapotú szoftver révén több felderítetlen hiba is adódhat.</p>
|
||||
<div class="box-warning">Nem ajánljuk, hogy produktívan használj egy alfa-állapotú szoftvert. Komoly adatveszteséggel járhat.</div>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being a beta release, there are bound to be some left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using beta versions as a production system. Your data could be altered, mangled or downright destroyed. Keep up-to-date backups!</div>
|
||||
|
||||
<p>Azért adunk ki alfa-állapotú szoftvert, hogy minél többen teszteljék, és minél több hibára derüljön fény, illetve hogy javaslatokat kapjunk a további fejlesztéshez. Kérjük, hogy mielőtt jelentesz egy hibát, előtte próbálj rákeresni, hátha már valaki jelentette azt.</p>
|
||||
<p>One of the main reasons for releasing a beta version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="https://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
|
||||
<li><a href="hu/bugreports.html">Tippek a hibák jelentéséhez</a></li>
|
||||
@@ -134,13 +134,13 @@ A Haiku könyv a Be köny átirata a Haiku-specifikus információkkal.</p>
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Kapcsolat</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="https://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<p>Kapcsolatba léphetsz más fejlesztőkkel és felhasználókkal IRC csatornán keresztül (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a>), a fórumunkon illetve a levelezőlistáinkon. Ha sok különböző ember összejön, akkor különféle szabályokat be kell vezetni. Kérjük, olvasd el a <a href="http://www.haiku-os.org/community/ml/etiquette">levelezőlista-illemtan</a>t.</p>
|
||||
<ul>
|
||||
<li><a href="https://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
|
||||
<li><a href="https://www.haiku-os.org/forum" class="printurl">Forums</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Elsődleges levelezőlista</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Fejlesztői levelezőlista</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Külső fejlesztői lista</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/ml" class="printurl">Overview of all mailing lists</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
@@ -11,8 +11,8 @@
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* MichaelPeppers
|
||||
* Humdinger
|
||||
* MichaelPeppers
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -24,7 +24,7 @@
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
<div><span>Guida dell'utente</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
@@ -56,7 +56,7 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
<div class="box-info">La traduzione di questa pagina non è stata completata. Per questo motivo le parti non tradotte sono visibili in inglese.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
@@ -73,16 +73,16 @@
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Benvenuto in Haiku!</a></h2>
|
||||
<p>Thank you very much for checking out Haiku! This is our fourth public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a hrf="https://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
<p>Thanks for checking out Haiku! This is our fifth public release. We hope to attract new developers to our project and give users a chance to check out Haiku. While this first <i>beta release</i> includes all major features planned for the final Haiku release, it still has many bugs and a few rough edges that need further polishing. However, we think that this release is quite usable and hope it lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a href="https://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="indice" /></a>
|
||||
<a id="bugreport" name="bugreport">Attento ai bug</a></h2>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
|
||||
<div class="box-warning">Scoraggiamo l'uso di versioni alpha come sistemi di produzione. I tuoi dati potrebbero venire alterati, danneggiati o essere addirittura cancellati.</div>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being a beta release, there are bound to be some left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using beta versions as a production system. Your data could be altered, mangled or downright destroyed. Keep up-to-date backups!</div>
|
||||
|
||||
<p>Una delle principali ragioni per rilasciare una versione alpha è di attrarre più persone per testare il sistema e scoprire bug o per consigliare miglioramenti. Ti preghiamo di segnalarci bug e miglioramenti nel nostro bug tracker dopo aver usato il suo motore di ricerca interno per evitare duplicati.</p>
|
||||
<p>One of the main reasons for releasing a beta version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="https://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
|
||||
<li><a href="it/bugreports.html">Consigli per segnalare i bug in modo utile</a></li>
|
||||
@@ -133,13 +133,13 @@ Deviations from the BeOS API and Haiku specific additions are collected in the H
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="indice" /></a>
|
||||
<a id="contact" name="contact">Entrare in contatto</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="https://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<p>Entra in contatto con altri sviluppatori e utenti e partecipa alle discussioni in chat, nei nostri forum o mailing list. Quando molte persone diverse si incontrano, si devono stabilire regole per fare in modo che la comunicazione sia fruttifera, ti preghiamo quindi di rispettare la nostra <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<ul>
|
||||
<li><a href="https://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
|
||||
<li><a href="https://www.haiku-os.org/forum" class="printurl">Forums</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Mailing list di discussione generale</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Mailing list per gli sviluppatori concernente Haiku stesso</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list per i programmatori di applicazioni di terze parti</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/ml" class="printurl">Overview of all mailing lists</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
@@ -11,10 +11,10 @@
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* iwaim
|
||||
* Shota Fukumori
|
||||
* mt
|
||||
* Humdinger
|
||||
* iwaim
|
||||
* mt
|
||||
* Shota Fukumori
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -26,7 +26,7 @@
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
<div><span>ユーザーガイド</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
@@ -60,7 +60,7 @@
|
||||
<div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>目次</td></tr>
|
||||
<tr class="heading"><td>インデックス</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">Haiku へようこそ!</a><br />
|
||||
<a href="#bugreport">バグに注意</a><br />
|
||||
@@ -74,16 +74,16 @@
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Haiku へようこそ！</a></h2>
|
||||
<p>Haiku を選んでくれてとてもうれしいよ！これは私たちの 4 番目の公式リリースです。私たちは新しい開発者をプロジェクトに迎え入れて、将来のユーザーに Haiku を選択してもらう機会を与えたいと考えています。この<i>アルファ版</i>が私たちが設定した目標を完全に満たしているものではなく、すべての機能を提供しているわけではないと理解しています。また、幅広いエンドユーザー・エクスペリエンスによって最終的な R1 バージョンの計画を立てました。しかしながら、あなたがこのリリースで Haiku の素晴らしいポテンシャルに気づき、私たちの興奮を共有してくれることを願っています。</p>
|
||||
<p>Haiku を選んでくれてとてもうれしいよ! これは私たちの 5 番目の公式リリースです。私たちは新しい開発者をプロジェクトに迎え入れて、ユーザーに Haiku を選択してもらう機会を与えたいと考えています。この最初の<i>ベータ版</i>は、Haiku の最終リリースに計画された機能をすべて含んでいますが、まだ多くのバグがあり、さらに洗練する必要のある荒削りな部分があります。しかし、私たちはこのリリースがかなり使い物になると考えており、あなたがこのリリースで Haiku の素晴らしいポテンシャルに気づき、私たちの興奮を共有してくれることを願っています。</p>
|
||||
<p>プロジェクトのウェブサイト、<a hrf="https://www.haiku-os.org">Haiku-os.org</a> にアクセスして、最新のニュースとお知らせを入手してください。</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">バグに注意</a></h2>
|
||||
<p>私たち開発チームはできるだけ潜在的に重大なバグを修正することに努めています。しかし、これはアルファ版であるため、まだ見つかっていないたくさんのバグが残っているかもしれません。</p>
|
||||
<div class="box-warning">アルファ版をプロダクションシステムとして使うことは勧めません。あなたのデータが壊れたり、めちゃくちゃになったり、完全に破壊されたりする可能性がとても高いです。</div>
|
||||
<p>私たち開発チームはできるだけ潜在的に重大なバグを修正することに努めています。しかし、これはベータ版であるため、まだ見つかっていないたくさんのバグが残っているかもしれません。</p>
|
||||
<div class="box-warning">ベータ版をプロダクションシステムとして使うことは勧めません。あなたのデータが壊れたり、めちゃくちゃになったり、完全に破壊されたりする可能性がとても高いです。常にバックアップを取って下さい!</div>
|
||||
|
||||
<p>私たちがアルファ版をリリースした理由の一つに、もっとたくさんの人に Haiku を触ってもらい、システムのテストとバグの発見など、Haiku の向上を目指すというのがあります。バグを見つけた場合、バグトラッカーで検索してまだ報告されていなければ (重複を防ぐために) 報告していただけると助かります。</p>
|
||||
<p>私たちがベータ版をリリースした主な理由の一つは、もっとたくさんの人を呼び込んで、システムのテスト、バグの発見、または、将来の機能向上のための提案をしていただくことです。バグと機能向上は、重複防止のためバグトラッカーで検索してから報告ください。</p>
|
||||
<ul>
|
||||
<li><a href="https://dev.haiku-os.org/wiki" class="printurl">Haiku バグトラッカー</a></li>
|
||||
<li><a href="jp/bugreports.html">役立つバグレポートのためのヒント</a></li>
|
||||
@@ -101,7 +101,7 @@
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">ソフトウェアを追加する</a></h2>
|
||||
<p>ほとんどの利用可能なソフトウェアは、Haiku に付属のアプリケーション、HaikuDepot でダウンロードおよびインストールできます。<br />ほとんどの BeOS 向けアプリケーションは Haiku でもバイナリとソースコードの互換性から動作すると思われます。その多くは Haiku 用に再パッケージされているか、修正なしに動作します。新しいアプリケーションのインストールに関する追加の情報はユーザーガイドの<a href="../userguide/jp/applications.html">アプリケーション</a>の章に見つかります。</p>
|
||||
<p>ほとんどの利用可能なソフトウェアは、Haiku に付属のアプリケーション、HaikuDepot でダウンロードおよびインストールできます。<br />ほとんどの BeOS 向けアプリケーションはバイナリとソースコードの互換性から Haiku でも動作すると思われます。その多くは Haiku 用に再パッケージされているか、修正なしに動作します。新しいアプリケーションのインストールに関する追加の情報はユーザーガイドの<a href="../userguide/jp/applications.html">アプリケーション</a>の章に見つかります。</p>
|
||||
<p>コミュニティベースのソフトウェアコレクションがいくつかあります。ウェブサイトの<a href="https://www.haiku-os.org/community/software">ソフトウェアサイト (Software Sites)</a> ページを参照ください。</p>
|
||||
|
||||
<h2>
|
||||
@@ -118,7 +118,7 @@
|
||||
<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,13 +132,13 @@
|
||||
<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="https://www.haiku-os.org/community/ml/etiquette">メーリングリストでのエチケット</a>に準拠して行動をするようにお願いします。</p>
|
||||
<p>IRC (webchat 上の <a href="http://webchat.freenode.net/?channels=haiku">#haiku</a>) や私たちのフォーラムまたはメーリングリストでほかの開発者やユーザーと連絡を取り、議論に参加できます。たくさんの人々が一緒に活動を場合、ルールにしっかりと準拠して行動をする必要があります。<a href="https://www.haiku-os.org/community/ml/etiquette">メーリングリストでのエチケット</a>に準拠して行動するようにお願いします。</p>
|
||||
<ul>
|
||||
<li><a href="https://www.haiku-os.org/community/irc" class="printurl">IRC チャンネル</a></li>
|
||||
<li><a href="https://www.haiku-os.org/forum" class="printurl">フォーラム</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Haiku 自体の開発のためのメーリングリスト</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">サードパーティソフトウェア開発者のためのメーリングリスト</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-development" class="printurl">Haiku 自体の開発のためのメーリングリスト</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">サードパーティソフトウェア開発者のためのメーリングリスト</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/ml" class="printurl">メーリングリストの概要</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
@@ -23,7 +23,7 @@
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
<div><span>Podręcznik użytkownika</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
@@ -55,91 +55,91 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
<div class="box-info">Tłumaczenie tej strony jest niekompletne. Nieukończone części wyświetlane są w języku angielskim.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Spis treści</td></tr>
|
||||
<tr class="index"><td>
|
||||
<a href="#welcome">Welcome to Haiku!</a><br />
|
||||
<a href="#bugreport">Beware of Bugs</a><br />
|
||||
<a href="#system">Getting to know the system</a><br />
|
||||
<a href="#software">Installing new software</a><br />
|
||||
<a href="#wifi">Wifi in Haiku</a><br />
|
||||
<a href="#api">Getting to know the API</a><br />
|
||||
<a href="#contact">Getting in contact</a>
|
||||
<a href="#welcome">Witamy w Haiku!</a><br />
|
||||
<a href="#bugreport">Strzeż się błędów</a><br />
|
||||
<a href="#system">Poznawanie systemu</a><br />
|
||||
<a href="#software">Instalowanie oprogramowania</a><br />
|
||||
<a href="#wifi">WiFi w Haiku</a><br />
|
||||
<a href="#api">Poznawanie API</a><br />
|
||||
<a href="#contact">Kontakt</a>
|
||||
</td></tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Witamy w Haiku!</a></h2>
|
||||
<p>Thank you very much for checking out Haiku! This is our fourth public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a hrf="https://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
<p>Thanks for checking out Haiku! This is our fifth public release. We hope to attract new developers to our project and give users a chance to check out Haiku. While this first <i>beta release</i> includes all major features planned for the final Haiku release, it still has many bugs and a few rough edges that need further polishing. However, we think that this release is quite usable and hope it lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Odwiedź stronę naszego projektu <a href="https://www.haiku-os.org">haiku-os.org</a> po najświeższe informacje oraz ogłoszenia.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Strzeż się błędów</a></h2>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
|
||||
<div class="box-warning">Odradzamy używania wersji alpha na codzień. Twoje dane mogą zostać zmienione, zniekształcone lub po prostu zniszczone.</div>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being a beta release, there are bound to be some left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using beta versions as a production system. Your data could be altered, mangled or downright destroyed. Keep up-to-date backups!</div>
|
||||
|
||||
<p>One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<p>One of the main reasons for releasing a beta version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="https://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
|
||||
<li><a href="pl/bugreports.html">Tips for a helpful bug report</a></li>
|
||||
<li><a href="https://dev.haiku-os.org/wiki" class="printurl">System śledzenia błędów Haiku</a></li>
|
||||
<li><a href="pl/bugreports.html">Poradnik wypełniania użytecznego zgłoszenia</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="system" name="system">Getting to know the system</a></h2>
|
||||
<p>The first release(s) of Haiku will be very much like the BeOS R5, the operating system it is reimplementing. If you never experienced it, have a look at these links:</p>
|
||||
<a id="system" name="system">Poznawanie systemu</a></h2>
|
||||
<p>Pierwsze wydanie Haiku będzie bardzo podobne do BeOS-a R5, systemu który w założeniu reimplementuje. Jeśli nigdy nie miałeś z nim styczności, zerknij na poniższe strony:</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/pl/contents.html">Podręcznik użytkownika Haiku</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/" class="printurl">List of BeOS/Haiku websites</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/" class="printurl">Lista stron o BeOS/Haiku</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="software">Instalowanie oprogramowania</a></h2>
|
||||
<p>Most of the available software can be downloaded and installed with the application HaikuDepot that comes with Haiku.<br />
|
||||
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/pl/applications.html">Applications</a>.</p>
|
||||
<p>There are several community-based software collections. See the <a href="https://www.haiku-os.org/community/software">Software Sites</a> page on our website.</p>
|
||||
<p>Większość dostępnego oprogramowania można pobrać i zainstalować za pomocą aplikacji HaikuDepot, dostarczanej razem z Haiku.<br />
|
||||
Z powodu kompatybilności binarnej oraz na poziomie kodu źródłowego, większość aplikacji BeOS działa na Haiku. Wiele z nich zostało przepakowanych dla Haiku, część pozostała w niezmienionej formie. Więcej informacji o instalowaniu nowych programów znajdziesz w podręczniku użytkownika, w rozdziale <a href="../userguide/pl/applications.html">Aplikacje</a>.</p>
|
||||
<p>Istnieje kilka zbiorów oprogramowania utrzymywanych przez społeczność. Zobacz <a href="https://www.haiku-os.org/community/software">Software Sites</a> na naszej stronie.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="update" name="update">Updating Haiku</a></h2>
|
||||
<p>Updating Haiku as well as third party packages is done with the application <a href="../userguide/pl/applications/softwareupdater.html">SoftwareUpdater</a>. When it's finished, reboot.<br />
|
||||
For more details, see the guide <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Updating your system</a> on our website.</p>
|
||||
<a id="update" name="update">Aktualizowanie Haiku</a></h2>
|
||||
<p>Aktualizacje zarówno Haiku, jak i pakietów niedostarczanych z systemem, są dokonywane przez aplikację <a href="../userguide/pl/applications/softwareupdater.html">SoftwareUpdater</a>. Kiedy skończy swoje działanie, uruchom komputer ponownie.<br />
|
||||
Po więcej szczegółów zajrzyj do poradnika <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Updating your system</a> na naszej stronie.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="software" name="wifi">WiFi w Haiku</a></h2>
|
||||
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/pl/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
|
||||
<p>Haiku wspiera sieci bezprzewodowe szyfrowane WPA/WPA2 i WEP oraz oczywiście, otwarte, nieszyfrowanie połączenia. Ze względu na różne polityki licencyjne różnych dostawców sprzętu, może być konieczna ręczna instalacja oprogramowania niezbędnego do działania. Więcej informacji o wspieranych urządzeniach, instalacji firmware’u oraz o tym jak połączyć się z siecią bezprzewodową znajdziesz w <a href="../userguide/pl/workshop-wlan.html">Warsztacie dotyczącym sieci bezprzewodowych</a> w naszym podręczniku.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="api" name="api">Poznawanie API</a></h2>
|
||||
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
|
||||
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
|
||||
<p>Haiku, będąc reimplementacją, ma takie samo API jak BeOS R5 (z kilkoma dodatkami), zatem dokumentacja dostępna w Księdze Be nadal jest wartościowym źródłem informacji. Dzięki uprzejmości firmy ACCESS, która jest właścicielem praw do zasobów byłego Be Inc., możemy udostępniać kopie Księgi Be.<br />
|
||||
Odstępstwa od API BeOS-a oraz rozszerzenia specyficzne dla Haiku zebrane zostały w Księdze Haiku.</p>
|
||||
|
||||
<p>There are some resources that should help you getting started:</p>
|
||||
<p>Poniżej znajduje się kilka źródeł, które ułatwią Ci start:</p>
|
||||
<ul>
|
||||
<li><a href="https://www.haiku-os.org/development/faq" class="printurl">Development FAQ</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">Source Browser</a></li>
|
||||
<li><a href="https://www.haiku-os.org/legacy-docs/bebook/" class="printurl">The Be Book</a></li>
|
||||
<li><a href="https://www.haiku-os.org/docs/api/" class="printurl">The Haiku Book</a></li>
|
||||
<li><a href="https://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be Newsletter Archive</a></li>
|
||||
<li><a href="https://www.haiku-os.org/development/faq" class="printurl">FAQ dla deweloperów</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">Przeglądarka kodu źródłowego</a></li>
|
||||
<li><a href="https://www.haiku-os.org/legacy-docs/bebook/" class="printurl">Księga Be</a></li>
|
||||
<li><a href="https://www.haiku-os.org/docs/api/" class="printurl">Księga Haiku</a></li>
|
||||
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Archiwum biuletynów Be</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Getting in contact</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="https://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<a id="contact" name="contact">Kontakt</a></h2>
|
||||
<p>Możesz skontaktować się z pozostałymi użytkownikami i deweloperami, dołączając do dyskusji na IRC (kanał <a href="http://webchat.freenode.net/?channels=haiku">#haiku</a>), na naszym forum lub listach mailingowych. Gdy wiele osób zbiera się w jednym miejscu, muszą zostać wprowadzone pewne zasady, aby komunikacja przebiegała sprawnie. Przestrzegaj proszę naszej <a href="https://www.haiku-os.org/community/ml/etiquette">Etykiety list mailingowych</a>.</p>
|
||||
<ul>
|
||||
<li><a href="https://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
|
||||
<li><a href="https://www.haiku-os.org/forum" class="printurl">Forums</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/ml" class="printurl">Overview of all mailing lists</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/irc" class="printurl">Kanały IRC</a></li>
|
||||
<li><a href="https://www.haiku-os.org/forum" class="printurl">Forum</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku" class="printurl">Główna lista mailingowa</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-development" class="printurl">Lista mailingowa dla deweloperów Haiku</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Lista mailingowa dla deweloperów aplikacji</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/ml" class="printurl">Przegląd wszystkich list mailingowych</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -11,9 +11,9 @@
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* tiagoms
|
||||
* Adriano Duarte
|
||||
* Humdinger
|
||||
* Adriano Duarte
|
||||
* tiagoms
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -25,7 +25,7 @@
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
<div><span>Guia do Usuário</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
@@ -57,7 +57,7 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
<div class="box-info">A tradução desta página ainda não está completa. Até lá, partes incompletas mostrarão o original em inglês.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Índice</td></tr>
|
||||
@@ -73,16 +73,16 @@
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Bem-vindo ao Haiku!</a></h2>
|
||||
<p>Muito obrigado por seu interesse no Haiku! Este é o nosso quarto lançamento ao público. Esperamos atrair novos desenvolvedores para o projeto e dar aos futuros usuários uma oportunidade de experimentar o sistema. Nós entendemos que este <i>lançamento alpha</i> ainda não atende completamente os objetivos que definimos e que não oferece todas as funcionalidades e suavidade de utilização para usuário-final planejadas para a versão R1 final. Contudo, esperamos que este lançamento lhe permita descobrir o grande potencial do Haiku e que você possa compartilhar de nosso entusiasmo.</p>
|
||||
<p>Visit our project's website <a hrf="https://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
<p>Thanks for checking out Haiku! This is our fifth public release. We hope to attract new developers to our project and give users a chance to check out Haiku. While this first <i>beta release</i> includes all major features planned for the final Haiku release, it still has many bugs and a few rough edges that need further polishing. However, we think that this release is quite usable and hope it lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visite o site de nosso projeto <a hrf="http://www.haiku-os.org">Haiku-os.org</a> para saber das últimas notícias e comunicados.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Cuidado com os bugs</a></h2>
|
||||
<p>Estivemos trabalhando duro para corrigir bugs potencialmente críticos, entretanto, por ser uma versão alfa, há margem para a existência de muitos ainda não descobertos.</p>
|
||||
<div class="box-warning">Desencorajamos usar versões alfa como sistemas de produção. Seus dados podem ser seriamente alterados, corrompidos ou completamente destruídos.</div>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being a beta release, there are bound to be some left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using beta versions as a production system. Your data could be altered, mangled or downright destroyed. Keep up-to-date backups!</div>
|
||||
|
||||
<p>Uma das principais razões para lançar uma versão alfa é atrair mais pessoas para testar o sistema e descobrir falhas ou oferecer sugestões para futuras melhorias. Por favor relate erros e melhorias no nosso rastreador de erros somente após usar nossa ferramenta de pesquisa, para evitar duplicidade.</p>
|
||||
<p>One of the main reasons for releasing a beta version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="https://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
|
||||
<li><a href="pt_BR/bugreports.html">Dicas para um relatório de erros proveitoso</a></li>
|
||||
@@ -133,13 +133,13 @@ Diferenças da API do BeOS e adicionais específicos do Haiku são coletados no
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Entrando em contato</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="https://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<p>Entre em contato com outros desenvolvedores e usuários e junte-se às discussões no IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> no webchat), em nossos fóruns ou nas listas de correio. Quando muitas pessoas diferentes se juntam, regras devem ser estabelecidas para manter a comunicação efetiva. Por favor, respeite nossa <a href="http://www.haiku-os.org/community/ml/etiquette">Etiqueta na Lista de Discussão</a>.</p>
|
||||
<ul>
|
||||
<li><a href="https://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
|
||||
<li><a href="https://www.haiku-os.org/forum" class="printurl">Forums</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Lista de discussão geral</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Lista de discussão de desenvolvimento referente ao próprio Haiku</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Lista de discussão dos programadores de aplicativos de terceiros</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/ml" class="printurl">Overview of all mailing lists</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
@@ -70,16 +70,16 @@
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Welcome to Haiku!</a></h2>
|
||||
<p>Thank you very much for checking out Haiku! This is our fourth public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a hrf="https://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
<p>Thanks for checking out Haiku! This is our fifth public release. We hope to attract new developers to our project and give users a chance to check out Haiku. While this first <i>beta release</i> includes all major features planned for the final Haiku release, it still has many bugs and a few rough edges that need further polishing. However, we think that this release is quite usable and hope it lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a href="https://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Beware of Bugs</a></h2>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.</div>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being a beta release, there are bound to be some left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using beta versions as a production system. Your data could be altered, mangled or downright destroyed. Keep up-to-date backups!</div>
|
||||
|
||||
<p>One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<p>One of the main reasons for releasing a beta version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="https://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
|
||||
<li><a href="pt_PT/bugreports.html">Tips for a helpful bug report</a></li>
|
||||
@@ -130,13 +130,13 @@ Deviations from the BeOS API and Haiku specific additions are collected in the H
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Getting in contact</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="https://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to be established to keep communication effective. Please respect our <a href="https://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<ul>
|
||||
<li><a href="https://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
|
||||
<li><a href="https://www.haiku-os.org/forum" class="printurl">Forums</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/ml" class="printurl">Overview of all mailing lists</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
<div><span>Ghid de utilizare</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
@@ -56,7 +56,7 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
<div class="box-info">Traducerea acestei pagini nu este completă încă. Până când va fi, părțile incomplete utilizează originalul în limba engleză.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
@@ -73,16 +73,16 @@
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Bine ați venit la Haiku!</a></h2>
|
||||
<p>Mulțumim mult că încercați Haiku! Aceasta este a patra versiune publică. Sperăm să atragem dezvoltatori noi către proiectul nostru și să oferim utilizatorilor viitori o șansă să încerce Haiku. Ne dăm seama că această <i>versiune alpha</i> nu se ridică încă la așteptările pe care le-am stabilit pentru noi și nu oferă toate caracteristicile și experiența bine alcătuită pentru un utilizator plănuită pentru versiunea finală R1. Totuși, sperăm că această versiune vă permite să descoperiți potențialul ridicat al Haiku și că sunteți la fel de entuziasmați ca și noi.</p>
|
||||
<p>Thanks for checking out Haiku! This is our fifth public release. We hope to attract new developers to our project and give users a chance to check out Haiku. While this first <i>beta release</i> includes all major features planned for the final Haiku release, it still has many bugs and a few rough edges that need further polishing. However, we think that this release is quite usable and hope it lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Vizitați pagina web a proiectului nostru <a hrf="https://www.haiku-os.org">Haiku-os.org</a> pentru cele mai recente știri și anunțuri.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Aveți grijă la defecțiuni</a></h2>
|
||||
<p>Lucrăm din greu să rezolvăm defecțiunile potențial grave, deși, fiind o versiune alpha, este foarte posibil să fie destule care încă nu au fost descoperite.</p>
|
||||
<div class="box-warning">Descurajăm utilizarea versiunilor alpha drept sistem de producție. Este foarte posibil ca datele să fie alterate, deformate sau chiar distruse.</div>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being a beta release, there are bound to be some left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using beta versions as a production system. Your data could be altered, mangled or downright destroyed. Keep up-to-date backups!</div>
|
||||
|
||||
<p>Unul din motivele principale pentru lansarea unei versiuni alpha este să atragem mai multe persoane care să testeze sistemul și să descopere defecțiuni sau să ofere sugestii pentru îmbunătățiri viitoare. Trimiteți defecțiunile și îmbunătățirile la monitorul nostru de defecțiuni după ce ați utilizat funcția acestuia de căutare pentru a evita duplicate.</p>
|
||||
<p>One of the main reasons for releasing a beta version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Monitor defecțiuni Haiku</a></li>
|
||||
<li><a href="ro/bugreports.html">Sfaturi pentru un raport de defecțiune util</a></li>
|
||||
@@ -137,9 +137,9 @@ Deviațiile de la API BeOs și adaosurile specifice Haiku sunt colecționate în
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">Canale IRC</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">Forumuri</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Liste de discuții generale</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Listă de discuții pentru dezvoltare cu privire la Haiku în sine</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Listă de discuții pentru programatorii de aplicație 3rd party</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Prezentare generală a tuturor listelor de discuții</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
@@ -11,10 +11,10 @@
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Michael Smirnov
|
||||
* Rodastahm Islamov
|
||||
* Sergei Reznikov
|
||||
* Rodastahm Islamov
|
||||
* Humdinger
|
||||
* Michael Smirnov
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -26,7 +26,7 @@
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
<div><span>Руководство пользователя</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
@@ -58,7 +58,7 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
<div class="box-info">Перевод этой страницы еще не завершен. Пока это не произойдет, незавершенные части будут на английском.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Содержание</td></tr>
|
||||
@@ -75,16 +75,16 @@
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Добро пожаловать в Haiku!</a></h2>
|
||||
<p>Thank you very much for checking out Haiku! This is our fourth public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a hrf="https://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
<p>Thanks for checking out Haiku! This is our fifth public release. We hope to attract new developers to our project and give users a chance to check out Haiku. While this first <i>beta release</i> includes all major features planned for the final Haiku release, it still has many bugs and a few rough edges that need further polishing. However, we think that this release is quite usable and hope it lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Посетите сайт нашего проекта <a hrf="http://www.haiku-os.org">Haiku-os.org</a> чтобы узнать последние новости и объявления.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Остерегайтесь ошибок!</a></h2>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
|
||||
<div class="box-warning">Мы не рекомендуем использовать альфа-версии в качестве основной операционной системы. В ваши данные с большой вероятностью могут быть внесены нежелательные изменения, они могут быть искажены или даже уничтожены.</div>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being a beta release, there are bound to be some left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using beta versions as a production system. Your data could be altered, mangled or downright destroyed. Keep up-to-date backups!</div>
|
||||
|
||||
<p>Одной из главных причин для выпуска альфа-версии явиляется желание привлечь больше пользователей для тестирования и обнаружения ошибок, а также получения от них предложений по дальнейшему улучшению Haiku. Пожалуйста, оставляйте отчёты о найденных багах и предложения по улучшению в нашей системе отслеживания ошибок (bug tracker), но только после использования поиска, чтобы избежать дубликатов.</p>
|
||||
<p>One of the main reasons for releasing a beta version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="https://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
|
||||
<li><a href="ru/bugreports.html">Советы по сообщениям об ошибках</a></li>
|
||||
@@ -135,13 +135,13 @@ For more details, see the guide <a href="https://www.haiku-os.org/guides/daily-t
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Желаете пообщаться?</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="https://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<p>Вы можете связаться с разработчиками и другими пользователями, присоединившись к обсуждению на IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> в вебчате), каналах, нашем форуме или в списках рассылки. Когда множество людей обсуждают что-то вместе, то необходимо соблюдать некоторые правила для сохранения эффективности общения. Пожалуйста, придерживайтесь <a href="http://www.haiku-os.org/community/ml/etiquette">Этикета списков рассылки</a>.</p>
|
||||
<ul>
|
||||
<li><a href="https://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
|
||||
<li><a href="https://www.haiku-os.org/forum" class="printurl">Forums</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Основной список рассылки</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Список рассылки непосредственных разработчиков Haiku</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Список рассылки для разработчиков сторонних приложений</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/ml" class="printurl">Overview of all mailing lists</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
<div><span>Používateľská príručka</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
@@ -56,7 +56,7 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
<div class="box-info">Preklad tejto stránky zatiaľ nie je dokončený. Dovtedy sa nedokončené časti zobrazia v anglickom origináli.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Obsah</td></tr>
|
||||
@@ -72,18 +72,18 @@
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Víta vás Haiku!</a></h2>
|
||||
<p>Ďakujeme vám, že ste vyskúšali Haiku! Toto je naše štvrté verejné vydanie. Dúfame, že náš projekt zaujme nových vývojárov a dá budúcim používateľom šancu vyskúšať Haiku. Uvedomujeme si, že toto <i>alfa vydanie</i> zatiaľ celkom nedosahuje cieľov, ktoré sme si stanovili a neponúka všetky možnosti a bezproblémový používateľský zážitok, ktorý je plánovaný pre finálne vydanie R1. Dúfame však, že vám toto vydanie Haiku umožní objaviť veľký potenciál Haiku a že zdieľate naše nadšenie.</p>
|
||||
<p>Visit our project's website <a hrf="https://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
<p>Thanks for checking out Haiku! This is our fifth public release. We hope to attract new developers to our project and give users a chance to check out Haiku. While this first <i>beta release</i> includes all major features planned for the final Haiku release, it still has many bugs and a few rough edges that need further polishing. However, we think that this release is quite usable and hope it lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Posledné novinky a oznámenia nájdete na webovej stránke projeku <a hrf="http://www.haiku-os.org">Haiku-os.org</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Pozor na chyby</a></h2>
|
||||
<p>Usilovne sme odstraňovali a stále pracujeme na odstraňovaní všetkých závažných chýb, ale pretože toto je alfa vydanie, určite je v ňom ešte mnoho neodhalených chýb.</p>
|
||||
<div class="box-warning">Neodporúčame používať alfa verzie ako produkčný systém. Vaše dáta sa môžu zmeniť, poškodiť alebo úplne zničiť.</div>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being a beta release, there are bound to be some left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using beta versions as a production system. Your data could be altered, mangled or downright destroyed. Keep up-to-date backups!</div>
|
||||
|
||||
<p>Jedným z hlavných dôvodov vydania alfa verzie je prilákanie ďalších ľudí, aby otestovali systém a odhalili chyby alebo vyjadrili svoje návrhy ďalších vylepšení. Prosím, posielajte chyby a vylepšenia do nášho systému na sledovanie chýb potom, ako použijete jeho vyhľadávacie funkcie, aby sme predišli duplicitám.</p>
|
||||
<p>One of the main reasons for releasing a beta version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="https://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
|
||||
<li><a href="https://dev.haiku-os.org/wiki" class="printurl">Systém sledovania chýb Haiku</a></li>
|
||||
<li><a href="sk/bugreports.html">Tipy na užitočné hlásenie o chybe</a></li>
|
||||
</ul>
|
||||
|
||||
@@ -93,7 +93,7 @@
|
||||
<p>Prvé vydanie či vydania Haiku budú veľmi podobné ako BeOS R5, operačný systém, ktorý sa snaží reimplementovať. Ak ho nikdy nezažili, pozrite sa na tieto odkazy:</p>
|
||||
<ul>
|
||||
<li><a href="../userguide/sk/contents.html">Používateľská príručka Haiku</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/" class="printurl">List of BeOS/Haiku websites</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/" class="printurl">Zoznam webov o BeOS/Haiku</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
@@ -101,13 +101,13 @@
|
||||
<a id="software" name="software">Inštalovanie ďalšieho softvéru</a></h2>
|
||||
<p>Väčšinu dostupného softvéru je možné stiahnuť a nainštalovať pomocou aplikácie HaikuDepot, ktorá sa dodáva spolu s Haiku.<br />
|
||||
Vďaka tomu, že Haiku je kompatibilné s BeOS na binárnej úrovni aj na úrovni zdrojového kódu, mnohé aplikácie pre BeOS bežia na Haiku. Pre mnohé z nich boli vytvorené balíky pre Haiku alebo jednoducho bežia nezmenené. Ďalšie informácie o inštalovaní nových programov nájdete v Používateľskej príručke v kapitole <a href="../userguide/sk/applications.html">Aplikácie</a>.</p>
|
||||
<p>There are several community-based software collections. See the <a href="https://www.haiku-os.org/community/software">Software Sites</a> page on our website.</p>
|
||||
<p>Existuje niekoľko kolekcií softvéru, ktoré spravuje komunita. Nájdete ich na našej webovej stránke <a href="https://www.haiku-os.org/community/software">Stránky so softvérom</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="update" name="update">Updating Haiku</a></h2>
|
||||
<p>Updating Haiku as well as third party packages is done with the application <a href="../userguide/sk/applications/softwareupdater.html">SoftwareUpdater</a>. When it's finished, reboot.<br />
|
||||
For more details, see the guide <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Updating your system</a> on our website.</p>
|
||||
<a id="update" name="update">Aktualizácia Haiku</a></h2>
|
||||
<p>Aktualizácia Haiku a balíkov od tretích strán sa robí pomocou aplikácie <a href="../userguide/sk/applications/softwareupdater.html">Aktualizácia softvéru</a>. Po jej dokončení reštartujte systém.<br />
|
||||
Ďalšie podrobnosti nájdete v návode <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Aktualizácia vášho systému</a> na našej webovej stránke.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
@@ -122,24 +122,24 @@ Odchýlky od API BeOSu a rozšírenia špecifické pre Haiku sú zdokumentované
|
||||
|
||||
<p>Existujú zdroje, ktoré vám pomôžu začať:</p>
|
||||
<ul>
|
||||
<li><a href="https://www.haiku-os.org/development/faq" class="printurl">Development FAQ</a></li>
|
||||
<li><a href="https://www.haiku-os.org/development/faq" class="printurl">Často kladené otázky - vývoj</a></li>
|
||||
<li><a href="http://cgit.haiku-os.org/" class="printurl">Prehliadač zdrojového kódu</a></li>
|
||||
<li><a href="https://www.haiku-os.org/legacy-docs/bebook/" class="printurl">The Be Book</a></li>
|
||||
<li><a href="https://www.haiku-os.org/docs/api/" class="printurl">The Haiku Book</a></li>
|
||||
<li><a href="https://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be Newsletter Archive</a></li>
|
||||
<li><a href="https://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Archív newsletterov Be</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Kontaktujte nás</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="https://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<p>Kontaktujte ostatných vývojárov a používateľov a pridajte sa do diskusií na IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> na webčete), v našich fórach alebo poštových konferenciách. Keď sa zhromaždí veľa rôznych ľudí, musia sa stanoviť pravidlá, aby komunikácia zostala efektívna. Prosím, rešpektujte <a href="http://www.haiku-os.org/community/ml/etiquette">Etiketu našej konferencie</a>.</p>
|
||||
<ul>
|
||||
<li><a href="https://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
|
||||
<li><a href="https://www.haiku-os.org/forum" class="printurl">Forums</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Všeobecná poštová konferencia</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Poštová konferencia o vývoji samotného Haiku</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Poštová konferencia o vývoji aplikácií tretích strán</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/ml" class="printurl">Overview of all mailing lists</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/irc" class="printurl">Kanály IRC</a></li>
|
||||
<li><a href="https://www.haiku-os.org/forum" class="printurl">Fóra</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku" class="printurl">Všeobecná poštová konferencia</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-development" class="printurl">Poštová konferencia o vývoji samotného Haiku</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Poštová konferencia o vývoji aplikácií tretích strán</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/ml" class="printurl">Prehľad všetkých poštových konferencií</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -24,7 +24,7 @@
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
<div><span>Användarhandbok</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
@@ -56,7 +56,7 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
<div class="box-info">Översättningen av denna sida är inte komplett. Delar av innehållet kommer därför att visas på engelska.</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Index</td></tr>
|
||||
@@ -73,16 +73,16 @@
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Välkommen till Haiku!</a></h2>
|
||||
<p>Thank you very much for checking out Haiku! This is our fourth public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a hrf="https://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
<p>Thanks for checking out Haiku! This is our fifth public release. We hope to attract new developers to our project and give users a chance to check out Haiku. While this first <i>beta release</i> includes all major features planned for the final Haiku release, it still has many bugs and a few rough edges that need further polishing. However, we think that this release is quite usable and hope it lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Visit our project's website <a href="https://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Varning för buggar</a></h2>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
|
||||
<div class="box-warning">Vi rekommenderar inte att använda alfa versioner i ett produktionssystem. Din data kan mycket väl ändras, eller helt enkelt förstöras.</div>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being a beta release, there are bound to be some left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using beta versions as a production system. Your data could be altered, mangled or downright destroyed. Keep up-to-date backups!</div>
|
||||
|
||||
<p>En av huvudanledningarna till varför vi ger ut en alfa-version är för att locka fler att testa systemet, upptäcka buggar eller förse oss med förslag för framtida förbättringar. Vänligen registrera buggar och förbättringar i vårt projekthanteringssystem efter att ha använt dess sökfunktion, för att på så sätt undvika att dubletter skapas.</p>
|
||||
<p>One of the main reasons for releasing a beta version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="https://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
|
||||
<li><a href="sv_SE/bugreports.html">Tips för hjälpsam buggrapportering</a></li>
|
||||
@@ -133,13 +133,13 @@ Deviations from the BeOS API and Haiku specific additions are collected in the H
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="contact" name="contact">Kom i kontakt med oss</a></h2>
|
||||
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="https://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
|
||||
<p>Kom i kontakt med andra utvecklare och användare och delta i diskussionerna på IRC, i våra forum eller på e-postlistorna. När många olika människor samlas krävs regler för att hålla kommunikationen effektiv. Vänligen respektera vår <a href="http://www.haiku-os.org/community/ml/etiquette">etikett för e-postlistor</a>.</p>
|
||||
<ul>
|
||||
<li><a href="https://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
|
||||
<li><a href="https://www.haiku-os.org/forum" class="printurl">Forums</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Allmän e-postlista</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">E-postlista för utveckling av Haiku</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">E-postlista för utveckling av tredjeparts programvara</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/ml" class="printurl">Overview of all mailing lists</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
@@ -11,8 +11,8 @@
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* totish
|
||||
* Humdinger
|
||||
* totish
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -24,7 +24,7 @@
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
<div><span>Настанова користувачеві</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
@@ -56,7 +56,7 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
<div class="box-info">Переклад даної сторінки ще неповний. Допоки це так, незавершені частини користайте у англійському варіанті. </div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>Зміст</td></tr>
|
||||
@@ -74,16 +74,16 @@
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">Вітаємо в Haiku!</a></h2>
|
||||
<p>Дякуємо за інтерес, який Ви проявляєте до Haiku! Це наш четвертий публічний реліз, ми маємо надію привернути увагу нових розробників і дати можливість майбутнім користувачам побачити Haiku в дії. Зрозуміло, що цей <i>альфа реліз</i> далеко не повністю відповідає цілям, які поставлені і не надає всіх функцій, які ми збирались надати кінцевому користувачеві, запланувавши їх для фінальної версії R1. Однак, ми маємо надію, що він дозволить Вам помітити значний потенціал Haiku і Ви знайдете хвильку для її вивчення.</p>
|
||||
<p>Thanks for checking out Haiku! This is our fifth public release. We hope to attract new developers to our project and give users a chance to check out Haiku. While this first <i>beta release</i> includes all major features planned for the final Haiku release, it still has many bugs and a few rough edges that need further polishing. However, we think that this release is quite usable and hope it lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>Відвідайте вебсайт нашого проекту <a hrf="https://www.haiku-os.org">Haiku-os.org</a> для ознайомлення з останніми новинами та оголошеннями.</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">Остерігайтесь помилок</a></h2>
|
||||
<p>Ми провели значну роботу по виявленню і усуненню помилок ("багів"), однак це лише альфа-реліз і в ньому можлива присутність деякої кількості невиявлених помилок.</p>
|
||||
<div class="box-warning">Ми не рекомендуємо використовувати альфа версій у якості основної опереаційної системи. У Ваші дані з великою ймовірністю можуть бути внесені небажані зміни, вони можуть бути спотворені або навіть знищені.</div>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being a beta release, there are bound to be some left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using beta versions as a production system. Your data could be altered, mangled or downright destroyed. Keep up-to-date backups!</div>
|
||||
|
||||
<p>Одна з основних причин випуску альфа-версії є бажання привернути більше користувачів для тестування і виявлення помилок, а також отримання від них пропозицій для подальшого покращення Haiku. Прохання залишати звіти про найдені помилки і пропозиції з покращення ОС в нашій системі відслідкування помилок (bug tracker), але тільки після попереднього пошуку, для уникнення появи дублікатів.</p>
|
||||
<p>One of the main reasons for releasing a beta version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Система відслідковування помилок у Haiku (Bug Tracker)</a></li>
|
||||
<li><a href="uk/bugreports.html">Поради по повідомленнях про помилки</a></li>
|
||||
@@ -138,9 +138,9 @@ For more details, see the guide <a href="https://www.haiku-os.org/guides/daily-t
|
||||
<ul>
|
||||
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC канали</a></li>
|
||||
<li><a href="http://www.haiku-os.org/forum" class="printurl">Форуми</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Основний список розсилки</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Список розсилки безпосередніх розробників Haiku</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Список розсилки для розробників сторонніх додатків</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Огляд усіх списків розсилки</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
@@ -11,9 +11,9 @@
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Stephan Aßmus <superstippi@gmx.de>
|
||||
* Translators:
|
||||
* Pengphei Han
|
||||
* Humdinger
|
||||
* dgy18787
|
||||
* Humdinger
|
||||
* Pengphei Han
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -25,7 +25,7 @@
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
<div><span>用户指南</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
@@ -57,7 +57,7 @@
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
<div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</div>
|
||||
|
||||
<table class="index" id="index" summary="index">
|
||||
<tr class="heading"><td>索引</td></tr>
|
||||
@@ -74,16 +74,16 @@
|
||||
|
||||
<h2>
|
||||
<a id="welcome" name="welcome">欢迎使用Haiku！</a></h2>
|
||||
<p>非常感谢试用 Haiku 操作系统！这是我们发布的第四个公开版本，希望能吸引新开发者加入开发，并让未来的 Haiku 用户有机会了解 Haiku 的开发情况。我们深知，现在这个<i>Alpha 预览版本</i>还不能完整达到我们的既定目标，也不能提供 R1 正式版中的所有特性及全面的用户体验。但即便如此，我们还是期望这个版本能够让您对 Haiku 的惊人潜力略窥一二，分享我们的喜悦。</p>
|
||||
<p>Thanks for checking out Haiku! This is our fifth public release. We hope to attract new developers to our project and give users a chance to check out Haiku. While this first <i>beta release</i> includes all major features planned for the final Haiku release, it still has many bugs and a few rough edges that need further polishing. However, we think that this release is quite usable and hope it lets you discover Haiku's great potential and that you share our excitement.</p>
|
||||
<p>要了解最新新闻和公告，请访问我们的网站： <a hrf="https://www.haiku-os.org">Haiku-os.org</a> 。</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="bugreport" name="bugreport">当心软件错误</a></h2>
|
||||
<p>我们一直在努力修复软件中所有可能出现的严重缺陷，但是，作为预览版本，当中一定会有许多未知问题。</p>
|
||||
<div class="box-warning">我们不建议您将预览版本作为日常工作系统，在这种情况下，您的数据可能遭到改变，损坏甚至完全破坏。</div>
|
||||
<p>We have been working hard to fix potentially critical bugs, however, being a beta release, there are bound to be some left undiscovered.</p>
|
||||
<div class="box-warning">We discourage using beta versions as a production system. Your data could be altered, mangled or downright destroyed. Keep up-to-date backups!</div>
|
||||
|
||||
<p>发布该预览版本的主要原因之一，是为了吸引更多的用户来测试系统、发现错误，提供未来改进建议。在使用我们的错误跟踪系统提交错误或改进建议之前，请使用查询功能以避免重复提交。</p>
|
||||
<p>One of the main reasons for releasing a beta version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
|
||||
<ul>
|
||||
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku 错误跟踪系统</a></li>
|
||||
<li><a href="zh_CN/bugreports.html">如何提交有价值的错误报告</a></li>
|
||||
@@ -107,8 +107,8 @@
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="update" name="update">升级 Haiku 系统</a></h2>
|
||||
<p>Updating Haiku as well as third party packages is done with the application <a href="../userguide/zh_CN/applications/softwareupdater.html">SoftwareUpdater</a>. When it's finished, reboot.<br />
|
||||
For more details, see the guide <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Updating your system</a> on our website.</p>
|
||||
<p>Haiku 系统以及第三方的包升级都可以通过应用 <a href="../userguide/zh_CN/applications/softwareupdater.html">软件更新器</a> 完成。在完成后，重启系统。 <br />
|
||||
更多信息，查看我们网站上的指南 <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Updating your system</a> 。</p>
|
||||
|
||||
<h2>
|
||||
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
@@ -137,9 +137,9 @@ BeOS API 与 Haiku 之间的不同之处，可见于 Haiku Book。</p>
|
||||
<ul>
|
||||
<li><a href="https://www.haiku-os.org/community/irc" class="printurl">IRC 聊天频道</a></li>
|
||||
<li><a href="https://www.haiku-os.org/forum" class="printurl">相关论坛</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku" class="printurl">通用邮件列表</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">开发邮件列表（只关注 Haiku 项目）</a></li>
|
||||
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">开发邮件列表（第三方程序）</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
|
||||
<li><a href="https://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
|
||||
<li><a href="https://www.haiku-os.org/community/ml" class="printurl">所有邮件列表概览</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
@@ -12,8 +12,8 @@
|
||||
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* Pengphei Han
|
||||
* dgy18787
|
||||
* Pengphei Han
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -92,7 +92,7 @@
|
||||
<ul>
|
||||
<li><p>尝试在当前版本的Haiku系统中重现您的问题。 有许多用于测试的预编译镜像都是<a href="http://haiku-files.org/">可用的</a>。</p></li>
|
||||
<li><p>包括基本的信息，例如以何种方式测试 Haiku（利用真实的硬件，VMware，还是 QEMU）。</p></li>
|
||||
<li><p>注意您所运行的系统版本。您可以在桌面栏菜单的 <span class="menu">关于 Haiku...</span> 找到该信息。<br /> 同时您还需要注意您所测试的 Haiku 的构建类型（gcc2，gcc4，gcc2hybird，gcc4hybird）。 可下载的镜像都会给出相应的命名，对于自主构建的镜像，您需要了解自己的构建方法。</p></li>
|
||||
<li><p>Mention which revision you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (x86_gcc2, x86_64). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
|
||||
<li><p>描述您所遇到的问题。尽量把问题讲得精确和明白：详细的描述系统的行为反馈，和您期望的反馈。</p></li>
|
||||
<li><p>描述出现该错误所需要的操作步骤。这将会有助于开发者重现该错误，并对其进行修复和完善。</p></li>
|
||||
<li><p>附带你所掌握的尽可能多的信息。如果是一个GUI错误，或者其中的程序错误，尽量使用 <span class="key">PRINT</span> 键来截取当时的屏幕图像。</p></li>
|
||||
@@ -100,14 +100,13 @@
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="app" name="app">程序错误</a></h2>
|
||||
<p>如果程序发生崩溃，您需要从弹出的警告窗口中启动调试程序。它将会打开一个运行gdb（GNUdebugger）的终端窗口。输入 <span class="cli">bt</span>，您将会创建一个有关调试信息的“回溯”，然后您需要把它完整的复制出来（包括您输入 <span class="cli">bt</span> 命令之前终端中显示的内容），附加到错误报告中。</p>
|
||||
<p>When an application crashed, you can either save a report or write a core file (both saved to the Desktop) that you can attach to a bugreport, or you can evoke the <a href="../../userguide/zh_CN/applications/debugger.html">Debugger</a>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="server" name="server">服务错误</a></h2>
|
||||
<p>当 app server，registrar server 或者 input server 等重要组件崩溃时，您将无法看到通常的崩溃警告。相反的，整个屏幕将会呈现白色，并且启动一个 gdb 会话，相关的输出信息直接在屏幕中进行显示。您可能还可以继续移动鼠标，这将会覆盖掉屏幕中的白色区域和 gdb 输出信息。仍在运行的程序 (例如，进程控制器或者桌面栏的时钟) 可能也会覆盖屏幕中的调试信息。
|
||||
<br />
|
||||
除却所有显示的丑陋和操作的不便，它与软件出错基本一样。 最重要的是获取一个有关错误的回溯（使用 <span class="cli">bt</span> 命令）。您可能还需要使用数码相机记录下相关的屏幕显示，因为这种情况下，您无法拷贝相关的文本，<br />
|
||||
根据不同的崩溃问题，您可以尝试通过 <span class="cli">save-report</span> 指令在桌面保存崩溃报告，然后按下电源键尝试重启。</p>
|
||||
<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 the Debugger will be started in text-mode, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and Debugger 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.<br />
|
||||
Depending on what exactly crashed, you can try to save a crash report on the Desktop with <span class="cli">save-report</span> or <span class="cli">write-core</span> for a core file, and then press the power button once to try shutting cleanly down. If the power button doesn't work, there are also the commands <span class="cli">shutdown</span> and <span class="cli">reboot</span>.</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kernel" name="kernel">内核错误</a></h2>
|
||||
@@ -123,11 +122,11 @@
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="kdl" name="kdl">内核调试 - KDL</a></h3>
|
||||
<p>如果系统没有自动的进入内核调试状态，您也可以有意识的使用 <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> 快捷键手动进入。<br />
|
||||
需要注意的是，在内核调试状态，您的键盘可能会无法工作。PS/2 键盘通常都能够正常工作；对于 UHCI 控制器连接的 USB 键盘，您至少需要使用快捷键进入内核调试状态一次，它才可用。但是对于 USB OCHI，目前还未实现支持。</p>
|
||||
<p>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> (<span class="key">SysReq</span> being the <span class="key">Print</span> key, normally).<br />
|
||||
Note that in KDL your keyboard may not work. PS/2 keyboards always do, with USB keyboards it depends on the type of USB controller (UHCI/EHCI). Generally, the keyboard should be plugged into the port directly, not via any hubs. In some circumstances, the keyboard only works if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
|
||||
<p>KDL 本身是 shell 中的一类。它可以执行命令，打印系统信息。下面是一些感兴趣的命令：</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>打印回溯信息。如果系统自主进入内核调试状态，通常需要输入该命令。</td></tr>
|
||||
<tr><td><span class="cli">bt</span> (aka <span class="cli">sc</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> (aka continue)</td><td> </td><td>离开内核调试状态；如果可能的话，继续正常的系统操作。</td></tr>
|
||||
<tr><td><span class="cli">reboot</span></td><td> </td><td>立即重启系统。您将会丢失所有未保存的数据，甚至包括那些已经保存，但是还未写入硬盘的数据。</td></tr>
|
||||
@@ -141,16 +140,16 @@
|
||||
<p><b>这是从无法引导的系统中获取信息的首选方法。</b>
|
||||
<br />
|
||||
系统日志（syslog，system log 的缩写）中包含了关于系统问题的有用信息，包括 KDL 会话的输出信息 。通常将它附带到有关内核问题的报告中是个不错的主意。系统日志将会写入文件 <span class="path">/boot/system/var/log/syslog</span>。由于写入文件需要系统处于运行状态，因此当内核出现问题时（尤其是，系统自动重启，或者无法持续 KDL 会话），最新的输出信息可能无法写入日志文件。</p>
|
||||
<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog persistent. If the option <span class="menu">Save syslog from previous session during boot</span> is activated in the boot loader options (as it is by default), you'll find the syslog of your last session as <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
|
||||
If you're not able to boot to get to the previous_syslog, you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
|
||||
In the boot loader's <span class="menu">Debug menu</span> you should find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. Note: Don't accidentally boot any operating system or the data will be lost.</p>
|
||||
<p>引导程序的 <span class="menu">Debug menu</span> 中的<span class="menu">Enable debug syslog</span> 选项可以使系统日志持久存在。如果启用了引导菜单中的 <span class="menu">Save syslog from previous session during boot</span> 选项（默认情况下启用），您可以在 <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> 两个入口。前者将系统日志显示于屏幕，后者允许您将其保存到硬盘。需要注意的是，目前只有 FAT32 卷支持保存该文件。如果您使用 USB 磁盘，但是插入晚了，可能它将不被识别；您可以重置机器，然后再次进入引导程序菜单。但是还要注意：不要无故的启动任何操作系统，否则数据将会丢失。</p>
|
||||
|
||||
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="onscreen" name="onscreen">屏幕调试</a></h3>
|
||||
<p><b>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/zh_CN/bootloader.html">Boot Loader</a>.</p>
|
||||
<p><b>屏幕调试输出仅对调试特殊问题有用，而且自身也有（定时）问题。若非必须，不要使用它。</b><br />
|
||||
只有当 Haiku 引导机器失败，而且 <span class="menu">Debug syslog option</span> 出于某些原因无法使用，它才具有重要意义。 在Haiku的引导徽标出现之前，按下 <span class="key">SHIFT</span> 进入引导程序菜单。 选择 <span class="menu">Select safe mode options</span>。 在接近屏幕底部，<span class="menu">[ ] Enable on screen debug output</span> 将会列出。（注意：如果尝试启动Haiku，您可以启用另一个选项。如果 Haiku 只有在启用多个选项时才可以启动，您在错误报告中一定要给出这些选项。）<br />
|
||||
最后，选择 <span class="menu">Return to main menu</span> 和 <span class="menu">Continue booting</span>。<br />
|
||||
在屏幕上将会显示一页或者多页文本，只有最后几行才需要附带到您的错误报告。更多信息，参阅 <a href="../../userguide/zh_CN/bootloader.html">引导程序</a>。</p>
|
||||
|
||||
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="hardware" name="hardware">硬件错误</a></h2>
|
||||
@@ -159,10 +158,10 @@ One or more pages of text will display on the screen, only the last few lines ne
|
||||
<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">open /var/log/syslog</span></td><td> </td><td>The primary system log used by Haiku, see <a href="#syslog">Syslog</a> above, 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> 列出所有使用的驱动。</td></tr>
|
||||
<tr><td>- <span class="cli">ints</span></td><td> </td><td>只在 <i>内核调试状态</i> 可用（参阅下文）。它用显示中断使用情况。不可能有许多由不同硬件共享的中断。</td></tr>
|
||||
<tr><td colspan="3">- 屏幕调试输出（引导时间选项的安全模式）。</td></tr>
|
||||
<tr><td colspan="3">- On screen debug output (a safe mode boot time option, see <a href="#onscreen">above</a>).</td></tr>
|
||||
</table>
|
||||
|
||||
<p>前四个命令需要在终端中进行输入。在命令后添加 <span class="cli"> > output.txt</span> ，然后输出的信息将会重定向到“output.txt”文本文件，您可以将其附带到您的错误报告或者邮件。</p>
|
||||
|
||||
Reference in New Issue
Block a user