i2p/haiku-beta6
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update userguide translations

Browse Source 
Also purge old documents
This commit is contained in:
Autocommitter
2018-10-20 16:28:58 -04:00
committed by waddlesplash
parent 4fd69b6cc2
commit 7852aa0525
323 changed files with 2291 additions and 7101 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/welcome/ca/bugreports.html
+1 -1
View File
@@ -121,7 +121,7 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
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 <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">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace (aka stack crawl). If the system entered KDL on its on volition, a back trace is normally printed automatically. Enter the command if that didn't happen or part of it is obscured (e.g. when the stack trace is so long that it wrapped around) and your only way of providing the information to developers is by taking a picture of the screen.</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 <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>
docs/welcome/de/bugreports.html
+1 -1
View File
@@ -123,7 +123,7 @@ Je nachdem was genau abgestürzt ist, kann man auch probieren mit dem Befehl <sp
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 <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">bt</span> (auch <span class="cli">sc</span>)</td><td> </td><td>Zeigt einen "backtrace" (oder auch "stackcrawl") wo genau der Fehler aufgetreten ist. Ist das System von selbst ins KDL gefallen, wird so ein backtrace automatisch ausgegeben. Der Befehl ist einzugeben wenn das nicht geschehen oder ein Teil nicht zu sehen ist (beispielsweise bei sehr langen Ausgaben, bei denen das Ende der Ausgabe am Ende der Seite den Anfang überschreibt), und die einzige Möglichkeit die Information an die Entwickler zu senden ein Foto ist.</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>
docs/welcome/de/wifi.html
-155
View File
@@ -1,155 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!--
*
* Copyright 2010-2011, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
* Humdinger <[email protected]>
* Translators:
* Humdinger
* taos
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="robots" content="all" />
<title>WLAN</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>User Guide</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/de.png" alt="" /> Deutsch</li>
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
<a href="../welcome_de.html" class="uplink">Welcome</a>
</span></div>
</div>
<div id="content">
<div>
<h2>WLAN in Haiku</h2>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="hardware" rel="nofollow" id="hardware">Wahrscheinlich unterstützte Hardware</a></h3>
<p>Alle FreeBSD 8 WLAN Treiber sollten funktionieren. Jedoch keine PCMCIA, CardBus, ExpressCard, USB oder ISA basierte Karten. Unterstützt wird nur PCI, miniPCI, PCI-Express, miniPci-Express und PCI-X.<br />
Darunter:</p>
<ul>
<li><p><i>aironetwifi</i> unterstützt zumindest<br />
Cisco Aironet 350 Serie<br />
Aironet PCI4500<br />
Aironet PCI4800<br />
</p></li>
<li><p><i>atheroswifi</i> unterstützt fast alle Chipsets (allerdings keine AR9285 Chips)</p></li>
<li><p><i>broadcom43xx</i> unterstützt<br />
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 und BCM4318</p>
</li>
<li><p><i>ipw2100</i> unterstützt Intel Pro Wireless 2100 Chips</p></li>
<li><p><i>iprowifi2200</i> unterstützt Intel Pro Wireless<br />
2200BG<br />
2225BG<br />
2915ABG</p>
</li>
<li><p><i>iprowifi3945</i> unterstützt Intel Pro Wireless Chips 3945</p></li>
<li><p><i>iprowifi4965</i> unterstützt Intel Pro Wireless 4965 Chips</p></li>
<li><p><i>marvell88w8335</i> unterstützt<br />
Marvell Libertas 88W8310<br />
Marvell Libertas 88W8335</p></li>
<li><p><i>marvell88w8363</i> unterstützt 88W8363 Chips</p></li>
<li><p><i>ralinkwifi</i> unterstützt<br />
RT2560<br />
RT2561S<br />
RT2561<br />
RT2661</p>
</li>
<li><p>ralink2860 unterstützt Ralink RT2860</p></li>
<li><p><i>wavelanwifi</i> unterstützt zumindest<br />
3Com Airconnect<br />
GLPRISM2 WaveLAN<br />
Intersil Prism3<br />
Intersil Prism2.5<br />
Linksys WDT11<br />
Netgear MA301<br />
PRISM2STA WaveLAN<br />
Siemens SpeedStream<br />
SMC 2602W<br />
Us Robotics 2415<br />
Addtron AWA-100 PCI</p></li>
</ul>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="connect" rel="nofollow" id="connect">Verbindung zum Funknetzwerk</a></h3>
<p>Neben unverschlüsselten Netzwerken unterstützt Haiku auch mittels <a href="#wep-notes" rel="nofollow">WEP Schlüssel</a> verschlüsselte Netze. WEP ist allerdings eine bereits veraltete Verschlüsselungsmethode, also nicht wirklich sicher.</p>
<p>Vom Terminal aus lassen sich mit dem Befehl <span class="cli">ifconfig</span> vorhandene Funknetze auflisten und mit einem Verbindung aufnehmen ("join") oder wieder trennen ("leave"):</p>
<pre class="terminal">ifconfig [Wifi_Geräte_Pfad] [list|join|leave] (Schlüssel)</pre>
<p>Der <tt>Wifi_Geräte_Pfad</tt> wird in den <span class="app">Netzwerk</span> Einstellungen angezeigt oder mit dem Befehl <span class="cli">ifconfig -a</span> im Terminal.</p>
<p>Nachfolgend einige Beispiele wie mit einem Funknetzwerk namens <i>wifitopia</i> eine Verbindung hergestellt wird. Als Netzwerkkarte wird <tt>/dev/net/iprowifi3945/0</tt> angenommen.</p>
<h4>Alle Funknetzwerke auflisten:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
<h4>Verbindung mit einem unverschlüsselten Funknetzwerk:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
<h4>Verbindung mit einem <a href="#wep-notes">WEP verschlüsselten </a> Funknetzwerk: (ASCII Passwort)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia DasPasswort</pre>
<h4>Verbindung mit einem <a href="#wep-notes">WEP verschlüsselten </a> Funknetzwerk: (64 Bit Hex-Passwort)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
<h4>Verbindung zum Funknetzwerk trennen:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="auto-connect" rel="nofollow" id="auto-connect">Automatische Verbindung zu einem Funknetzwerk</a></h3>
<p>Nach dem Hochfahren kann man sich auch automatisch mit einem durch seine SSID benannten Netzwerk verbinden. Dazu müssen Funknetzwerke und die entsprechenden Passwörter in der Datei <tt><acronym title="/boot/common/settings/network/wireless_networks">/boot/Allgemein/settings/network/wireless_networks</acronym></tt> in folgendem Format abgelegt werden:</p>
<pre>network wifitopia {
   password DasPasswort
}</pre>
<p>Legt man diese Konfigurationsdatei nicht an, verbindet sich das System automatisch mit dem ersten unverschlüsselten Netzwerk, das es findet.</p>
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP Info</strong></a></p>
<ul>
<li>64-bit WEP benutzt ein 40-bit Passwort, das sind 5 Buchstaben oder 10 Hex-Werte</li>
<li>128-bit WEP benutzt ein 104-bit Passwort, das sind 13 Buchstaben oder 26 Hex-Werte</li>
<li>Hex-Werte sind die Zahlen 0-9 und Buchstaben A bis F (in <tt>ifconfig</tt> mit einem vorangestellten '0x')</li>
</ul>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="wpa" rel="nofollow" id="wpa">WPA Verschlüsselung</a></h3>
<p>Momentan gibt es noch keine WPA Verschlüsselung unter Haiku. <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">Ein großer Schritt</a> in diese Richtung wurde allerdings bereits unternommen.</p>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
<p>Um die Firmware für Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx &amp; Marvell 88W8335 zu installieren, startet man</p>
<pre class="terminal">~&gt; install-wifi-firmwares.sh
</pre>
<p>Die Intel ipw2100 und iprowifi22xx benötigen zur Installation keine Internetverbindung, da es die Lizenzbestimmungen erlauben, die Original-Firmware gleich mitzuliefern. Sie verlangen jedoch eine Zustimmung des Benutzers vor ihrer Installtion. Für Broadcom 43xx &amp; Marvell 88W8335 ist hingegen eine funktionierende Internetverbindung nötig, da die entsprechenden Dateien mit der Firmware Haiku nicht beiliegen dürfen.</p>
<p>Leute, die ihr eigenes Haiku Image bauen, können ihre <span class="cli">build/jam/UserBuildConfig</span> entsprechend anpassen. Details dazu und eventuelle Updates zum WLAN-Thema finden sich in der <a href="">Online-Version dieses Dokuments</a> (Englisch).</p>
<p>Wer die Firmware runterladen muss, aber unter Haiku keine Internetverbindung hat, kann das in diesem Online Dokument angebotene <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">Shell Skript</a> benutzen. Damit werden alle nötigen Dateien heruntergeladen und in ein Zip gepackt, das man unter Haiku in <tt>/boot</tt> entpacken kann. Dann stehen alle Dateien zur Verfügung, die von install-wifi-firmwares.sh benötigt werden.</p>
</div>
</div>
<div class="nav">
<div class="inner"><span>
<a href="../welcome_de.html" class="uplink">Welcome</a>
</span></div>
</div>
</body>
</html>
docs/welcome/en/bugreports.html
+1 -1
View File
@@ -120,7 +120,7 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
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 <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">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace (aka stack crawl). If the system entered KDL on its on volition, a back trace is normally printed automatically. Enter the command if that didn't happen or part of it is obscured (e.g. when the stack trace is so long that it wrapped around) and your only way of providing the information to developers is by taking a picture of the screen.</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 <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>
docs/welcome/en/wifi.html
-158
View File
@@ -1,158 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!--
*
* Copyright 2010-2011, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
* Humdinger <[email protected]>
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="robots" content="all" />
<title>Wifi</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>User guide</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/gb.png" alt="" /> English</li>
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
</ul>
<span>
<a href="../welcome_en.html" class="uplink">Welcome</a>
</span></div>
</div>
<div id="content">
<div>
<h2>Wifi in Haiku</h2>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="hardware" rel="nofollow" id="hardware">Expected supported hardware</a></h3>
<p>All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, PCI-Express, miniPci-Express and PCI-X are supposed to work.<br />
This includes:
</p>
<ul>
<li><p><i>aironetwifi</i> supporting at least<br />
Cisco Aironet 350 Series<br />
Aironet PCI4500<br />
Aironet PCI4800<br />
</p></li>
<li><p><i>atheroswifi</i> supporting almost every chipset outthere (though no AR9285 chips)</p></li>
<li><p><i>broadcom43xx</i> supporting<br />
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318
</p></li>
<li><p><i>ipw2100</i> supporting Intel Pro Wireless 2100 chips</p></li>
<li><p><i>iprowifi2200</i> supporting Intel Pro Wireless<br />
2200BG<br />
2225BG<br />
2915ABG
</p></li>
<li><p><i>iprowifi3945</i> supporting Intel Pro Wireless 3945 chips</p></li>
<li><p><i>iprowifi4965</i> supporting Intel Pro Wireless 4965 chips</p></li>
<li><p><i>marvell88w8335</i> supporting<br />
Marvell Libertas 88W8310<br />
Marvell Libertas 88W8335
</p></li>
<li><p><i>marvell88w8363</i> supporting the 88W8363 chips</p></li>
<li><p><i>ralinkwifi</i> supporting<br />
RT2560<br />
RT2561S<br />
RT2561<br />
RT2661
</p></li>
<li><p>ralink2860 supporting Ralink RT2860</p></li>
<li><p><i>wavelanwifi</i> supporting at least<br />
3Com Airconnect<br />
GLPRISM2 WaveLAN<br />
Intersil Prism3<br />
Intersil Prism2.5<br />
Linksys WDT11<br />
Netgear MA301<br />
PRISM2STA WaveLAN<br />
Siemens SpeedStream<br />
SMC 2602W<br />
Us Robotics 2415<br />
Addtron AWA-100 PCI
</p></li>
</ul>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="connect" rel="nofollow" id="connect">Connecting to a wireless network</a></h3>
<p>Besides of course unencrypted networks, Haiku has preliminary support for accessing wireless networks via <a href="#wep-notes" rel="nofollow">WEP encryption keys</a>. WEP is an early encryption method, although not the most secure.</p>
<p>You can list available networks, join and leave them with the command <span class="cli">ifconfig</span> from Terminal:</p>
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
<p>You can find your <tt>wifi_device_path</tt> in the <span class="app">Network</span> preferences applet, or by executing <span class="cli">ifconfig -a</span>.</p>
<p>Below are a few examples of connecting to a wireless network named <i>wifitopia</i>. For these examples we are assuming your wifi network card is <tt>/dev/net/iprowifi3945/0</tt>.</p>
<h4>Listing wireless networks:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
<h4>Joining unsecured wireless network:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (ascii password)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (64-bit hex password)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
<h4>Leaving a wireless network:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="auto-connect" rel="nofollow" id="auto-connect">Automatically connecting to a wireless network</a></h3>
<p>To make your system connect to a given SSID at each boot automatically, you can specify your wireless networks and passwords in <tt>/boot/common/settings/network/wireless_networks</tt> with the following format:</p>
<pre>network wifitopia {
   password mypassword
}</pre>
<p>If you don't create this configuration file, the system will connect to the first unencrypted network it finds.</p>
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP notes</strong></a></p>
<ul>
<li>64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex digits</li>
<li>128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex digits</li>
<li>hexadecimal digits = characters 0-9 and A through F (prepended with "0x" in <tt>ifconfig</tt>)</li>
</ul>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="wpa" rel="nofollow" id="wpa">WPA encryption</a></h3>
<p><p>At the moment there is no WPA encryption available in Haiku, though there have been <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">some efforts</a> bringing it significantly closer.</p></p>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
<p>To install the firmware for Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx &amp; Marvell 88W8335, you need to run</p>
<pre class="terminal">install-wifi-firmwares.sh
</pre>
<p>The Intel ipw2100 and iprowifi22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.</p>
<p>People building their own Haiku image can modify their <span class="cli">build/jam/UserBuildConfig</span> accordingly. Details for that and general updates on the wifi topic are found at the <a href="http://www.haiku-os.org/guides/wifi">online version of this document</a>.</p>
<p>If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">shell script</a>, which will create a zip file for you to extract to Haiku's <tt>/boot</tt>. After that you'll have all files needed by install-wifi-firmwares.sh.</p>
</div>
</div>
<div class="nav">
<div class="inner"><span>
<a href="../welcome_en.html" class="uplink">Welcome</a>
</span></div>
</div>
</body>
</html>
docs/welcome/es/bugreports.html
+36 -37
View File
@@ -18,7 +18,7 @@
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta name="robots" content="all" />
<title>Reportar fallos</title>
<title>Como Reportar fallos</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
@@ -57,25 +57,24 @@
<div id="content">
<div>
<div class="box-info">La traducción de esta página no está completa aún. Hasta que esté, las partes sin traducir se muestran en el inglés original.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Contenido</td></tr>
<tr class="index"><td><a href="#account">Obtener una cuenta de Trac</a><br />
<a href="#report">Crear un reporte de fallo</a><br />
<a href="#report">Creación de un reporte de fallo</a><br />
<a href="#app">Fallos de programas</a><br />
<a href="#server">Fallos de servidores</a><br />
<a href="#kernel">Fallos de núcleo</a><br />
<a href="#kdl">Zona de depuración de núcleo (KDL - Kernel Debugging Land)</a><br />
<a href="#syslog">Historial de Eventos de Sistema</a><br />
<a href="#syslog">Registro de Eventos de Sistema</a><br />
<a href="#onscreen">Salida de depuración en pantalla</a><br />
<a href="#hardware">Fallos de hardware/controladores</a><br />
<a href="#next">¿Qué sigue?</a></td></tr>
</table>
<h1>Reportar fallos</h1>
<h1>Como Reportar fallos</h1>
<p>Ya que nuestros desarrolladores no pueden verificar todas las combinaciones de hardware, ni todas las posibles maneras de interactuar con el sistema operativo, confiamos que los usuarios nos den retroalimentación sobre cómo funcionan las cosas de su lado. Dado que Haiku todavía es muy joven, muy probablemente encontrará fallos. Le agradecemos por tomarse el tiempo para reportarlos. Juntos podemos mejorar a Haiku, bit a bit.</p>
<p>Debido a que nuestros desarrolladores no pueden verificar todas las combinaciones de hardware, ni todas las posibles maneras de interactuar con el sistema operativo, estamos contando con que los usuarios nos den retroalimentación sobre cómo funcionan las cosas de su lado. Dado que Haiku todavía es muy joven, es probable que vaya a encontrar fallos. Le agradecemos por tomarse el tiempo para reportar estos fallos. Juntos podemos mejorar a Haiku, poco a poco.</p>
<p>Para mantener nuestro rastreador de fallos efectivo, es esencial supeditarse a la <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Etiqueta del rastreador de fallos</a>.</p>
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
@@ -84,13 +83,13 @@
Cuando se cree una cuenta nueva, asegurese de <b>proporcionar su correo electrónico</b> pues es necesario obtener privilegios de modificación básica del reporte. Asegúrese de <b>comprobar su carpeta de correo no deseado (spam)</b> brevemente después, ya que a menudo toda verificación de correo importante termina allí.</p>
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="report" name="report">Crear un reporte de fallo</a></h2>
<a id="report" name="report">Creación de un reporte de fallo</a></h2>
<p>Antes de reportar un fallo, por favor <a href="http://dev.haiku-os.org/query?status=new&amp;status=assigned&amp;status=reopened&amp;status=closed&amp;summary=%7Etext+you+want+to+search+for&amp;order=priority">asegúrese</a> que aún no exista un reporte. Puede también usar la función de <a href="http://dev.haiku-os.org/search?q=&amp;noquickjump=1&amp;ticket=on">búsqueda</a> para esto.<br />
Tras haber establecido que es un fallo nuevo, haga que su información sea lo más precisa posible:</p>
<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>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>Mencione cuál revisión está ejecutando. 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 (x86_gcc2, x86_64). Las imagenes descargables se encuentran nombradas acorde, y en caso de una imagen auto-construida deberá saber cómo la construyó.</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,55 +97,55 @@ 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>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>
<p>Cuando una aplicación deja de responder, puede guardar un informe o archivo de volcado de memoria (core file), ambos guardados en el Escritorio, y puede adjuntar estos archivos a un informe de fallos, o puede invocar el <a href="../../userguide/es/applications/debugger.html">Depurador</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 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>
<p>Cuando dejan de responder servidores vitales como el app server, el registrar o el input server, no verá la alerta de cuelgue normal. En lugar de ella, la pantalla completa se pondrá en blanco y el Depurador será iniciado en modalidad de sólo texto, y su información de salida aparecerá directamente en la pantalla. Probablemente pueda seguir moviendo el ratón, que sobreescribirá el blanco y la salida del Depurador en pantalla. Aplicaciones que se sigan ejecutando, como ProcessController o el reloj en la Barra de Escritorio, también podrían dibujar encima de la salida de depurador en la pantalla.<br />
Más allá que todo se muestre de manera más desagradable e incómoda, basicamente lo mismo aplica para fallos en aplicaciones. Es muy importante que procure obtener un rastreo de pila (back trace) con la orden <span class="cli">bt</span>. Puede que sea necesario que tome una foto de la pantalla con una cámara digital, ya que no podrá copiar el texto en ningún lado.<br />
Dependiendo de que fue lo que dejó de responder, puede intentar guardar un informe de cuelgue en el Escritorio con la orden <span class="cli">save-report</span> o <span class="cli">write-core</span> para un archivo de volcado, y luego presionar el botón de encendido una vez para intentar apagar el sistema de forma limpia. Si no funciona el botón de encendido, también están las ordenes <span class="cli">shutdown</span> (apagar) y <span class="cli">reboot</span> (reiniciar).</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 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>
<p>Los fallos de núcleo a menudo son los de efectos más severos mientras que a la vez son los más dificiles de depurar. Hay diferentes tipos de síntomas, que muy probablemente apuntan a un problema de controlador o de núcleo:</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>El sistema entra al KDL (Zona de depuración de Núcleo) por sí sólo. La parte superior de la pantalla se despeja en blanco y varias líneas se muestran en ella. La segunda línea dice "<i>Bienvenido a la Zona de Depuración del Núclo...</i>" (Welcome to Kernel Debugging Land...), y la que está arriba declara la razón por la que se ingresó al KDL.</p></li>
<li><p>El sistema se reinicia de forma espontánea</p></li>
<li><p>El sistema deja de responder por completo. No puede mover el ratón y ninguna aplicación dibuja nada ya. Una prueba importante en esta situación es, si acaso todavía puede ingresar al KDL a través de la combinación de teclas <span class="key">ALT</span> <span class="key">PetSis</span>(SysReq) <span class="key">D</span> siendo <span class="key">PetSis</span>( <span class="key">Impr Pant</span> en la mayoría de los teclados). Espere al menos un minuto para ver si sucede algo.</p></li>
<li><p>El sistema no arranca correctamente. Puede reiniciarse espontaneamente o dejar de funcionar en algún punto (por ejemplo, en algún ícono de la pantalla de arranque). En el segundo caso también intente <span class="key">ALT</span> <span class="key">PetSis</span>(SysReq) <span class="key">D</span>.</p></li>
<li><p>El sistema completo o alguna pieza de hardware no se comportan correctamente. Por ejemplo, puede estar muy lento, ocurren errores, o algo no funciona en absoluto. Si algún hardware no funciona para nada, la primera verificación obvia es revisar si Haiku lo soporta actualmente (por ejemplo, preguntar en una lista de correos o en un foro).</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/es/bootloader.html">Boot Loader</a>).</p>
<p>Tome nota que aún cuando parece que sólo el último inciso parece indicar que es algo relacionado con hardware, todos los otros síntomas podrían ser provocados por una falla en un controlador de hardware también. Si tiene la sospecha que una pieza de hardware o su controlador correspondiente pueda que tenga que ver con el problema, revise si retirando/desactivando el hardware o el controlador hacen alguna diferencia. Por ejemplo, si sospecha sobre el Wifi podría encontrar que su BIOS tenga una opción para desactivarlo. O si no, podría añadir el controlador de Wifi responsable a la lista negra de su instalación de Haiku (vea <a href="../../userguide/es/bootloader.html">Cargador de arranque</a>).</p>
<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>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>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, con los teclados USB depende del tipo de controlador (UHCI/EHCI). Generalmente, el teclado debería estar conectado al puerto directamente, no a través de un hub. En algunas circunstancias, el teclado sólo funciona si uno ha ingresado al KDL por el método abreviado de teclado al menos una vez anteriormente. Actualmente no se soporta USB OHCI.</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> (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">bt</span> (también conocido como <span class="cli">sc</span>)</td><td> </td><td>muestra el "backtrace", o rastreo de pila. Si el sistema entró en el KDL por si solo, un rastreo de pila normalmente se muestra de forma automática. Ingrese la orden si eso no sucedió así o parte de ella está cubierta (por ejemplo, si el rastreo de pila es tan largo que dio la vuelta), y su única forma de proveer la información a los desarrolladores es tomando una foto de la pantalla.</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>
</table>
<p>Para más información, vea el artículo <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Bienvenido a la Zona de Depuración del Kernel <i>(en inglés)</i></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>La salida de KDL se escribe al puerto serial (si tiene uno, el cable respectivo, y un segundo ordenador para conectarlo, puede capturar la salida allá via un programa de terminal) y al registro del sistema (syslog). Pero si no puede salir del KDL, no será escrito en el archivo de registro de sistema. Hay una opción de depuración del cargador de arranque que permite capturarlo, no obstante (vea abajo).</p>
<p>Es posible generar códigos QR desde la salida de KDL que luego pueden ser convertidos a texo usando teléfonos inteligentes o aparatos similares. Vea la entrada del blog <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">Codifique su salida KDL en QR</a> (en inglés) sobre cómo extraer datos del KDL usando esa característica.</p>
<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 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 />
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>
<a id="syslog" name="syslog">Registro de Eventos de Sistema</a></h3>
<p><b>Este es el método predilecto para extraer información de un sistema que no arranca.</b><br />
El Registro de Eventos de Sistema (o syslog, por su nombre corto en inglés) contiene información valiosa sobre lo que ha sucedido con su sistema, incluyendo la salida de las sesiones KDL. Normalmente es buena idea adjuntarlo al ticket de Trac relacionado con el núcleo. El syslog es escrito al archivo <span class="path">/boot/system/var/log/syslog</span>. Debido a que escribir a un archivo requiere un sistema funcional, la salida más reciente puede no haber logrado llegar al syslog cuando ocurre un problema en el núcleo (particularmente en reinicios espontáneos o sesiones KDL incontinuables).</p>
<p>La opción <span class="menu">Activar syslog de depuración</span> (Enable debug syslog) en el <span class="menu">menú de Depuración</span> del cargador de arranque vuelve el syslog persistente. Si la opción <span class="menu">Guarde sus syslog de una sesión anterior durante el arranque</span> (Save syslog from previous session during boot) ha sido activada en las opciones del cargador de arranque (como lo está de forma predeterminada), encontrará el syslog de su última sesión en <span class="path">/boot/system/var/log/previous_syslog</span>.<br />
Si no puede arrancar para llegar al previous_syslog, tendrá que ingresar al menú del cargador de arranque manteniendo presionada la tecla <span class="key">Mayús</span> (SHIFT) mientras arranca.<br />
En el <span class="menu">menú de Depuración</span> del cargador de arranque, debería encontrar las entradas <span class="menu">Mostrar syslog de sesión previa</span> (Display syslog from previous session) y <span class="menu">Guardar syslog de sesión previa</span> (Save syslog from previous session). La primera muestra el syslog en pantalla, y la segunda le permite guardarlo en un archivo en disco. Note que en este momento solamente se soportan volumenes FAT32 para guardar el archivo. Si quiere usar una unidad USB, pero la insertó muy tarde de manera que todavía no se ha reconocido, puede reinicar la máquina y reingresar en el menú de cargador de arranque. Nota: No arranque ningún sistema operativo accidentalmente o los datos se perderán.</p>
<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</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>
<p><b>La salida de depuración en pantalla es útil solamente para depurar problemas muy específicos y es conocido que tiene problemas de tiempos. No lo use, si no debe hacerlo.</b><br />
Esto sólo es relevante cuando Haiku no arranca en su máquina y la opción de <span class="menu">Depuración de syslog</span> (Debug syslog) no funciona por alguna razón. Antes que aparezca el logo de arranque de Haiku, mantenga presionada la tecla <span class="key">Mayús</span> (SHIFT) para entrar en el menú del cargador de arranque. Seleccione <span class="menu">Seleccionar opciones de arranque en modo seguro</span> (Select safe mode options). Cerca de la parte inferior, aparecerá en la lista <span class="menu">[ ] Activar salida de depuración a pantalla</span> (Enable on screen debug output). (Nota: Las otras opciones podrían ser activadas en un intento de lograr que Haiku pueda arrancar. Si Haiku solo arranca cuando una o más opciones están activadas, asegúrese de mencionar cuales son.)<br />
Finalmente seleccione <span class="menu">Regresar a menú principal</span> (Return to main menu) y luego <span class="menu">Continuar con el arranque</span> (Continue booting).<br />
Una o más páginas de texto se mostrarán en la pantalla, solamente las últimas líneas deben incluirse en su ticket. Hay más información en el <a href="../../userguide/es/bootloader.html">Cargador de arranque</a>.</p>
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="hardware" name="hardware">Fallos de hardware/controladores</a></h2>
@@ -155,17 +154,17 @@ 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>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>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>vea <a href="#syslog">Registro de sistema</a> arriba, parecido al depurador en pantalla cuando se arranca. Con la orden <span class="cli">open</span> puede acortar a la parte relevante del registro de sistema en un editor de texto.</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">- On screen debug output (a safe mode boot time option, see <a href="#onscreen">above</a>).</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, vea <a href="#onscreen">arriba</a>)</td></tr>
</table>
<p>Las primeras cuatro ordenes se pueden ingresar en la Terminal. Agregue un <span class="cli"> &gt; 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>
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="next" name="next">¿Qué sigue?</a></h2>
<p>Después que un fallo se ha reportado, un desarrollador verá el reporte e intentará clasificarlo. Recuerde, todos somos voluntarios, y por ello, algunas veces un fallo pudiera estar sin responderse por un tiempo. Agregar nueva información cuando esté disponible usualmente ayuda a que se escoja un fallo más rápidamente, pero no intente 'levantar' el fallo agregando comentarios no descriptivos.</p>
<p>Luego que se ha reportado un fallo, un desarrollador verá el reporte e intentará clasificarlo. Recuerde, todos somos voluntarios, y por ello, algunas veces un fallo pudiera estar sin responderse por un tiempo. El agregar nueva información cuando esté disponible normalmente ayuda a que se seleccione un fallo más rápidamente, pero no intente 'empujar' el fallo arriba en la lista agregando comentarios no descriptivos.</p>
<p>Recuerde, reportar un fallo no es algo en lo que tome un poquito de tiempo y sea todo. Si se reporta un fallo, se vuelve parte del proceso de desarrollo de Haiku. Los desarrolladores podrían llegar con preguntas mientras intentan arreglar el fallo reportado. Por favor, permanezca atento para responderlas. Considere su participación 'terminada' cuando el fallo se marque como 'arreglado'.</p>
</div>
docs/welcome/es/wifi.html
-157
View File
@@ -1,157 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!--
*
* Copyright 2010-2011, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
* Humdinger <[email protected]>
* Translators:
* miguel~1.mx
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="robots" content="all" />
<title>Wifi</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>Guía del usuario</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/es.png" alt="" /> Español</li>
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
<a href="../welcome_es.html" class="uplink">Welcome</a>
</span></div>
</div>
<div id="content">
<div>
<div class="box-info">La traducción de esta página no está completa aún. Hasta que esté, las partes sin terminar vienen en su inglés original.</div>
<h2>Wifi en Haiku</h2>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="hardware" rel="nofollow" id="hardware">Hardware que se espera funcione</a></h3>
<p>Todos los controladores wlan de FreeBSD 8 deberían trabajar. Cualquier tarjeta basada PCMCIA, CardBus, ExpressCard, USB o ISA no funcionará. Únicamente las PCI, miniPCI, PCI-Express, miniPci-Express and PCI-X se espera que trabajen.<br />
Esto incluye a:
</p>
<ul>
<li><p><i>aironetwifi</i> soportando al menos:<br />
Aironet PCI4500 y<br />
Aironet PCI4800.<br />
</p></li>
<li><p><i>atheroswifi</i> soportando casi todos los chipsets de afuera (aunque no los chips AR9285).</p></li>
<li><p><i>broadcom43xx</i> soportando<br />
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 y BCM4318.
</p></li>
<li><p><i>ipw2100</i> supporting Intel Pro Wireless 2100 chips</p></li>
<li><p><i>iprowifi2200</i> supporting Intel Pro Wireless<br />
2200BG<br />
2225BG<br />
2915ABG
</p></li>
<li><p><i>iprowifi3945</i> supporting Intel Pro Wireless 3945 chips</p></li>
<li><p><i>iprowifi4965</i> supporting Intel Pro Wireless 4965 chips</p></li>
<li><p><i>marvell88w8335</i> soportando:<br />
Marvell Libertas 88W8310 y<br />
Marvell Libertas 88W8335.
</p></li>
<li><p><i>marvell88w8363</i> soportando los chips 88W8363.</p></li>
<li><p><i>ralinkwifi</i> soportando:<br />
RT2560,<br />
RT2561S,<br />
RT2561 y <br />
RT2661.
</p></li>
<li><p>ralink2860 supporting Ralink RT2860</p></li>
<li><p><i>wavelanwifi</i> soportando al menos:<br />
3Com Airconnect,<br />
GLPRISM2 WaveLAN,<br />
Intersil Prism3,<br />
Intersil Prism2.5,<br />
Linksys WDT11,<br />
Netgear MA301,<br />
PRISM2STA WaveLAN,<br />
Siemens SpeedStream,<br />
SMC 2602W,<br />
Us Robotics 2415 y<br />
Addtron AWA-100 PCI.
</p></li>
</ul>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="connect" rel="nofollow" id="connect">Connecting to a wireless network</a></h3>
<p>Besides of course unencrypted networks, Haiku has preliminary support for accessing wireless networks via <a href="#wep-notes" rel="nofollow">WEP encryption keys</a>. WEP is an early encryption method, although not the most secure.</p>
<p>You can list available networks, join and leave them with the command <span class="cli">ifconfig</span> from Terminal:</p>
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
<p>You can find your <tt>wifi_device_path</tt> in the <span class="app">Network</span> preferences applet, or by executing <span class="cli">ifconfig -a</span>.</p>
<p>Below are a few examples of connecting to a wireless network named <i>wifitopia</i>. For these examples we are assuming your wifi network card is <tt>/dev/net/iprowifi3945/0</tt>.</p>
<h4>Listing wireless networks:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
<h4>Joining unsecured wireless network:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (ascii password)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (64-bit hex password)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
<h4>Leaving a wireless network:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="auto-connect" rel="nofollow" id="auto-connect">Automatically connecting to a wireless network</a></h3>
<p>To make your system connect to a given SSID at each boot automatically, you can specify your wireless networks and passwords in <tt>/boot/common/settings/network/wireless_networks</tt> with the following format:</p>
<pre>network wifitopia {
   password mypassword
}</pre>
<p>If you don't create this configuration file, the system will connect to the first unencrypted network it finds.</p>
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>Notas WEP</strong></a></p>
<ul>
<li>El WEP de 64-bit usa una clave de 40-bit, lo cual significa 5 caracteres de texto o 10 dígitos hexadecimales.</li>
<li>El WEP de 128-bit usa una clave de 104-bit, lo cual significa 13 caracteres de texto o 16 dígitos hexadecimales.</li>
<li>hexadecimal digits = characters 0-9 and A through F (prepended with "0x" in <tt>ifconfig</tt>)</li>
</ul>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="wpa" rel="nofollow" id="wpa">Encripción WPA</a></h3>
<p><p>At the moment there is no WPA encryption available in Haiku, though there have been <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">some efforts</a> bringing it significantly closer.</p></p>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
<p>To install the firmware for Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx &amp; Marvell 88W8335, you need to run</p>
<pre class="terminal">install-wifi-firmwares.sh</pre>
<p>The Intel ipw2100 and iprowifi22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.</p>
<p>La gente que hace su propio build de la imagen de Haiku puede modificar su <span class="cli">build/jam/UserBuildConfig</span> en conformidad. Los detalles para ello y actualizaciones generales del tema de Wifi se encuentran en la <a href="http://www.haiku-os.org/guides/wifi">versión en línea de este documento</a>.</p>
<p>Si tiene que descargar el firmware, pero no tiene una conexión a Internet funcionando bajo Haiku, la versión en línea de este documento ofrece un <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">script de shell</a>, el cual creará un archivo zip para que se extraiga en la carpeta <tt>/boot</tt> de Haiku. Después de ello tendrá todos los archivos necesarios por install-wifi-firmwares.sh.</p>
</div>
</div>
<div class="nav">
<div class="inner"><span>
<a href="../welcome_es.html" class="uplink">Welcome</a>
</span></div>
</div>
</body>
</html>
docs/welcome/fi/bugreports.html
+2 -1
View File
@@ -57,6 +57,7 @@
<div id="content">
<div>
<div class="box-info">Tämän sivun kotoistaminen ei ole vielä täydellinen. Siihen asti keskeneräiset osat käyttävät englanninkielistä alkuperäistekstiä.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Hakemisto</td></tr>
@@ -123,7 +124,7 @@ Riippuen siitä mikä kaatui voit yrittää tallentaa kaatumisilmoituksen Työp
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 <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">bt</span> (eli <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace (aka stack crawl). If the system entered KDL on its on volition, a back trace is normally printed automatically. Enter the command if that didn't happen or part of it is obscured (e.g. when the stack trace is so long that it wrapped around) and your only way of providing the information to developers is by taking a picture of the screen.</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 <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>
docs/welcome/fi/wifi.html
-159
View File
@@ -1,159 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!--
*
* Copyright 2010-2011, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
* Humdinger <[email protected]>
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="robots" content="all" />
<title>Wifi</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>User guide</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/fi.png" alt="" /> Suomi</li>
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
<a href="../welcome_fi.html" class="uplink">Welcome</a>
</span></div>
</div>
<div id="content">
<div>
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
<h2>Wifi in Haiku</h2>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="hardware" rel="nofollow" id="hardware">Expected supported hardware</a></h3>
<p>All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, PCI-Express, miniPci-Express and PCI-X are supposed to work.<br />
This includes:
</p>
<ul>
<li><p><i>aironetwifi</i> supporting at least<br />
Cisco Aironet 350 Series<br />
Aironet PCI4500<br />
Aironet PCI4800<br />
</p></li>
<li><p><i>atheroswifi</i> supporting almost every chipset outthere (though no AR9285 chips)</p></li>
<li><p><i>broadcom43xx</i> supporting<br />
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318
</p></li>
<li><p><i>ipw2100</i> supporting Intel Pro Wireless 2100 chips</p></li>
<li><p><i>iprowifi2200</i> supporting Intel Pro Wireless<br />
2200BG<br />
2225BG<br />
2915ABG
</p></li>
<li><p><i>iprowifi3945</i> supporting Intel Pro Wireless 3945 chips</p></li>
<li><p><i>iprowifi4965</i> supporting Intel Pro Wireless 4965 chips</p></li>
<li><p><i>marvell88w8335</i> supporting<br />
Marvell Libertas 88W8310<br />
Marvell Libertas 88W8335
</p></li>
<li><p><i>marvell88w8363</i> supporting the 88W8363 chips</p></li>
<li><p><i>ralinkwifi</i> supporting<br />
RT2560<br />
RT2561S<br />
RT2561<br />
RT2661
</p></li>
<li><p>ralink2860 supporting Ralink RT2860</p></li>
<li><p><i>wavelanwifi</i> supporting at least<br />
3Com Airconnect<br />
GLPRISM2 WaveLAN<br />
Intersil Prism3<br />
Intersil Prism2.5<br />
Linksys WDT11<br />
Netgear MA301<br />
PRISM2STA WaveLAN<br />
Siemens SpeedStream<br />
SMC 2602W<br />
Us Robotics 2415<br />
Addtron AWA-100 PCI
</p></li>
</ul>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="connect" rel="nofollow" id="connect">Connecting to a wireless network</a></h3>
<p>Besides of course unencrypted networks, Haiku has preliminary support for accessing wireless networks via <a href="#wep-notes" rel="nofollow">WEP encryption keys</a>. WEP is an early encryption method, although not the most secure.</p>
<p>You can list available networks, join and leave them with the command <span class="cli">ifconfig</span> from Terminal:</p>
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
<p>You can find your <tt>wifi_device_path</tt> in the <span class="app">Network</span> preferences applet, or by executing <span class="cli">ifconfig -a</span>.</p>
<p>Below are a few examples of connecting to a wireless network named <i>wifitopia</i>. For these examples we are assuming your wifi network card is <tt>/dev/net/iprowifi3945/0</tt>.</p>
<h4>Listing wireless networks:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
<h4>Joining unsecured wireless network:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (ascii password)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (64-bit hex password)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
<h4>Leaving a wireless network:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="auto-connect" rel="nofollow" id="auto-connect">Automatically connecting to a wireless network</a></h3>
<p>To make your system connect to a given SSID at each boot automatically, you can specify your wireless networks and passwords in <tt>/boot/common/settings/network/wireless_networks</tt> with the following format:</p>
<pre>network wifitopia {
   password mypassword
}</pre>
<p>If you don't create this configuration file, the system will connect to the first unencrypted network it finds.</p>
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP notes</strong></a></p>
<ul>
<li>64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex digits</li>
<li>128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex digits</li>
<li>hexadecimal digits = characters 0-9 and A through F (prepended with "0x" in <tt>ifconfig</tt>)</li>
</ul>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="wpa" rel="nofollow" id="wpa">WPA encryption</a></h3>
<p><p>At the moment there is no WPA encryption available in Haiku, though there have been <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">some efforts</a> bringing it significantly closer.</p></p>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
<p>To install the firmware for Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx &amp; Marvell 88W8335, you need to run</p>
<pre class="terminal">install-wifi-firmwares.sh
</pre>
<p>The Intel ipw2100 and iprowifi22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.</p>
<p>People building their own Haiku image can modify their <span class="cli">build/jam/UserBuildConfig</span> accordingly. Details for that and general updates on the wifi topic are found at the <a href="http://www.haiku-os.org/guides/wifi">online version of this document</a>.</p>
<p>If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">shell script</a>, which will create a zip file for you to extract to Haiku's <tt>/boot</tt>. After that you'll have all files needed by install-wifi-firmwares.sh.</p>
</div>
</div>
<div class="nav">
<div class="inner"><span>
<a href="../welcome_fi.html" class="uplink">Welcome</a>
</span></div>
</div>
</body>
</html>
docs/welcome/fr/bugreports.html
+1 -1
View File
@@ -132,7 +132,7 @@ Notez bien que votre clavier pourrait ne pas fonctionner en mode débogage du no
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 <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">bt</span> (alias <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace (aka stack crawl). If the system entered KDL on its on volition, a back trace is normally printed automatically. Enter the command if that didn't happen or part of it is obscured (e.g. when the stack trace is so long that it wrapped around) and your only way of providing the information to developers is by taking a picture of the screen.</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>
docs/welcome/fr/wifi.html
-165
View File
@@ -1,165 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!--
*
* Copyright 2010-2011, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
* Humdinger <[email protected]>
* Translators:
* Loïc
* Vincent Duvert
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="robots" content="all" />
<title>Wifi</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>Guide de l’utilisateur</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/fr.png" alt="" /> Français</li>
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
<a href="../welcome_fr.html" class="uplink">Welcome</a>
</span></div>
</div>
<div id="content">
<div>
<h2>Le Wifi dans Haiku</h2>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="hardware" rel="nofollow" id="hardware">Matériel théoriquement supporté</a></h3>
<p>Tous les pilotes de réseau sans fil de FreeBSD 8 devraient fonctionner. En revanche, les périphériques PCMCIA, CardBus, ExpressCard, USB, ou ISA ne sont pas supportés. Seules les cartes PCI, MiniPCI, PCI-Express, minipci-Express et PCI-X sont censées fonctionner.<br />
Cela inclut :</p>
<ul>
<li><p>Le module <i>aironetwifi</i>, qui supporte au minimum les cartes :<br />
Cisco Aironet 350 Series<br />
Aironet PCI4500<br />
Aironet PCI4800<br />
</p></li>
<li><p>Le module <i>atheroswifi</i>, qui supporte la plupart des puces Atheros (à l'exception de la puce AR9285)</p></li>
<li><p>Le module <i>broadcom43xx</i> qui supporte les cartes :<br />
BCM4301<br />
BCM4306<br />
BCM4307<br />
BCM4309<br />
BCM4311<br />
BCM4312<br />
BCM4318</p></li>
<li><p>Le module <i>ipw2100</i> qui supporte les puces Wifi Intel Pro 2100</p></li>
<li><p>Le module <i>iprowifi2200</i> qui supporte les cartes Wifi Intel Pro :<br />
2200BG<br />
2225BG<br />
2915ABG
</p></li>
<li><p>Le module <i>iprowifi3945</i> qui supporte les puces Wifi Intel Pro 3945</p></li>
<li><p>Le module <i>iprowifi4965</i> qui supporte les puces Wifi Intel Pro 4965</p></li>
<li><p>Le module <i>marvell88w8335</i> qui supporte les cartes :<br />
Marvell Libertas 88W8310<br />
Marvell Libertas 88W8335
</p></li>
<li><p>Le module <i>marvell88w8363</i> qui supporte les puces Marvell 88W8363</p></li>
<li><p>Le module <i>ralinkwifi</i> qui supporte les cartes :<br />
RT2560<br />
RT2561S<br />
RT2561<br />
RT2661
</p></li>
<li><p>Le module <i>ralink2860</i> qui supporte les puces Ralink RT2860</p></li>
<li><p>Le module <i>wavelanwifi</i> qui supporte au moins les cartes suivantes :<br />
3Com Airconnect<br />
GLPRISM2 WaveLAN<br />
Intersil Prism3<br />
Intersil Prism2.5<br />
Linksys WDT11<br />
Netgear MA301<br />
PRISM2STA WaveLAN<br />
Siemens SpeedStream<br />
SMC 2602W<br />
Us Robotics 2415<br />
Addtron AWA-100 PCI
</p></li>
</ul>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="connect" rel="nofollow" id="connect">Connexion à un réseau Wifi</a></h3>
<p>Outre les réseaux non-cryptés, un début de sécurité Wifi est disponible dans Haiku grâce aux <a href="#wep-notes" rel="nofollow">clés de cryptage WEP</a>.
WEP est une méthode de cryptage rudimentaire peu sûre.</p>
<p>Vous pouvez lister les réseaux disponibles, les joindre oules quitter à l'aide de la commande <span class="cli">ifconfig</span> depuis le Terminal :</p>
<pre class="terminal">ifconfig [Chemin_du_ périphérique_Wifi] [list|join|leave] (clé)</pre>
<p>Vous pouvez trouver votre <tt>Chemin_du_ périphérique_Wifi</tt> dans l'appliquette des préférences Réseau (<span class="app">Network</span>), ou en exécutant <span class="cli">ifconfig -a</span>.</p>
<p>Voici quelques exemples de connexions à un réseau sans fil nommé <i>wifitopia</i>. Pour ces exemples, nous supposeront que votre carte réseau wifi est <tt>/dev/net/iprowifi3945/0</tt>.</p>
<h4>Lister les réseaux Wifi :</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
<h4>Joindre un réseau Wifi non sécurisé :</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
<h4>Joindre un réseau Wifi <a href="#wep-notes">sécurisé en WEP </a> : (mot de passe ascii)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia MonMotDePasse</pre>
<h4>Joindre un réseau Wifi <a href="#wep-notes">sécurisé en WEP </a> : (mot de passe hexadécimal 64-bit)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
<h4>Quitter un réseau Wifi non :</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="auto-connect" rel="nofollow" id="auto-connect">Connexion automatique à un réseau Wifi</a></h3>
<p>Pour que votre système se connecte automatiquement à un SSID donné à chaque démarrage, vous pouvez spécifier vos réseaux sans fil et leurs mots de passe dans <tt>/boot/common/settings/network/wireless_networks</tt> en utilisant le format suivant :</p>
<pre>network wifitopia {
   password MonMotDePasse
}</pre>
<p>Si vous ne créez pas ce fichier de configuration, le système se connectera au premier réseau non crypté qu'il trouvera.</p>
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>Remarques concernant le WEP</strong></a></p>
<ul>
<li>Le WEP « 64 bits » utilise une clé de 40 bits, c’est à dire 5 caractères alphanumériques ou 10 chiffres hexadécimaux.</li>
<li>Le WEP « 128 bits » utilise une clé de 104 bits, c’est à dire 13 caractères alphanumériques ou 26 chiffres hexadécimaux.</li>
<li>Un chiffre hexadécimal est un chiffre de 0 à 9 ou une lettre de A à F. Un nombre hexadécimal doit être précédé de « 0x » lorsqu’il est utilisé dans <tt>ifconfig</tt>.</li>
</ul>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="wpa" rel="nofollow" id="wpa">Le cryptage WPA</a></h3>
<p><p>Le cryptage WPA n'est pas encore disponible dans Haiku. Cependant, il existe une <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">ébauche</a> pour apporter cette nouvelle fonction.</p></p>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
<p>Pour installer le micro-logiciel des cartes Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx &amp; Marvell 88W8335, vous devez exécuter la commande</p>
<pre class="terminal">install-wifi-firmwares.sh
</pre>
<p>Les pilotes Intel ipw2100 et iprowifi22xx pourront être installés sans qu’une connexion Internet soit présente, car la distribution, dans Haiku, des fichiers contenant les micro-logiciels originaux est autorisée par leur licence. En revanche, vous devrez accepter les termes de cette licence avant l’installation. Les pilotes Broadcom 43xx et Marvell 88W8335 nécessiteront une connexion Internet pour s’installer, car les fichiers contenant leurs micro-logiciels respectifs ne peuvent être redistribués avec Haiku.</p>
<p>Si vous compilez vous-même Haiku, vous pouvez modifier votre fichier <span class="cli">build/jam/UserBuildConfig</span> afin de pouvoir utiliser cet outil. Vous pourrez trouver plus de détails sur le Wifi dans Haiku sur la <a href="http://www.haiku-os.org/guides/wifi">version en ligne de ce document</a> (en anglais).</p>
<p>Si il vous faut télécharger le micro-logiciel mais que vous n'avez pas de connexion internet qui fonctionne sous Haiku, la version en ligne vous propose aussi un <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">script de commande</a>, qui crée un fichier zip à extraire dans le dossier <tt>/boot</tt> de Haiku. Après cela, vous aurez tous les fichiers nécessaires pour install-wifi-firmwares.sh.</p>
</div>
</div>
<div class="nav">
<div class="inner"><span>
<a href="../welcome_fr.html" class="uplink">Welcome</a>
</span></div>
</div>
</body>
</html>
docs/welcome/hu/bugreports.html
+1 -1
View File
@@ -124,7 +124,7 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
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> (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">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace (aka stack crawl). If the system entered KDL on its on volition, a back trace is normally printed automatically. Enter the command if that didn't happen or part of it is obscured (e.g. when the stack trace is so long that it wrapped around) and your only way of providing the information to developers is by taking a picture of the screen.</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>
docs/welcome/it/bugreports.html
+1 -1
View File
@@ -121,7 +121,7 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
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 <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">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace (aka stack crawl). If the system entered KDL on its on volition, a back trace is normally printed automatically. Enter the command if that didn't happen or part of it is obscured (e.g. when the stack trace is so long that it wrapped around) and your only way of providing the information to developers is by taking a picture of the screen.</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 <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>
docs/welcome/it/wifi.html
-161
View File
@@ -1,161 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!--
*
* Copyright 2010-2011, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
* Humdinger <[email protected]>
* Translators:
* MichaelPeppers
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="robots" content="all" />
<title>Wifi</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>Guida dell'utente</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/it.png" alt="" /> Italiano</li>
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
<a href="../welcome_it.html" class="uplink">Welcome</a>
</span></div>
</div>
<div id="content">
<div>
<div class="box-info">La traduzione di questa pagina non è stata completata. Per questo motivo le parti non tradotte sono visibili in inglese.</div>
<h2>Il Wifi in Haiku</h2>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="indice" /></a>
<a name="hardware" rel="nofollow" id="hardware">Hardware che dovrebbe essere supportato</a></h3>
<p>Tutti i driver wlan forniti da FreeBSD 8 dovrebbero funzionare. Qualunque scheda basata su PCMCIA, CardBus, ExpressCard, USB o ISA non funzionerà. Solo PCI, miniPCI, PCI-Express, miniPci-Express e PCI-X sono probabilmente funzionanti.<br />
I driver disponibili includono:
</p>
<ul>
<li><p><i>aironetwifi</i>, supporta almeno<br />
La serie Cisco Aironet 350<br />
Aironet PCI4500<br />
Aironet PCI4800<br />
</p></li>
<li><p><i>atheroswifi</i>, supporta quasi tutti i chipset Atheros in commercio (ma non i chip AR9285)</p></li>
<li><p><i>broadcom43xx</i>, supporta i chipset<br />
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 e BCM4318
</p></li>
<li><p><i>iprowifi2100</i>, supporta i chip Intel Pro Wireless 2100</p></li>
<li><p><i>iprowifi2200</i>, supporta i chip Intel Pro Wireless<br />
2200BG<br />
2225BG<br />
2915ABG
</p></li>
<li><p><i>iprowifi3945</i>, supporta i chip Intel Pro Wireless 3945</p></li>
<li><p><i>iprowifi4965</i>, supporta i chip Intel Pro Wireless 4965</p></li>
<li><p><i>marvell88w8335</i>, supporta<br />
Marvell Libertas 88W8310<br />
Marvell Libertas 88W8335
</p></li>
<li><p><i>marvell88w8363</i>, supporta i chip 88W8363</p></li>
<li><p><i>ralinkwifi</i>, supporta<br />
RT2560<br />
RT2561S<br />
RT2561<br />
RT2661
</p></li>
<li><p>ralink2860, supporta i chip Ralink RT2860</p></li>
<li><p><i>wavelanwifi</i>, supporta almeno<br />
3Com Airconnect<br />
GLPRISM2 WaveLAN<br />
Intersil Prism3<br />
Intersil Prism2.5<br />
Linksys WDT11<br />
Netgear MA301<br />
PRISM2STA WaveLAN<br />
Siemens SpeedStream<br />
SMC 2602W<br />
Us Robotics 2415<br />
Addtron AWA-100 PCI
</p></li>
</ul>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="connect" rel="nofollow" id="connect">Connettersi a un network wireless</a></h3>
<p>Besides of course unencrypted networks, Haiku has preliminary support for accessing wireless networks via <a href="#wep-notes" rel="nofollow">WEP encryption keys</a>. WEP is an early encryption method, although not the most secure.</p>
<p>You can list available networks, join and leave them with the command <span class="cli">ifconfig</span> from Terminal:</p>
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
<p>You can find your <tt>wifi_device_path</tt> in the <span class="app">Network</span> preferences applet, or by executing <span class="cli">ifconfig -a</span>.</p>
<p>Below are a few examples of connecting to a wireless network named <i>wifitopia</i>. For these examples we are assuming your wifi network card is <tt>/dev/net/iprowifi3945/0</tt>.</p>
<h4>Mostrare una lista dei network wireless:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
<h4>Joining unsecured wireless network:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (ascii password)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (64-bit hex password)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
<h4>Leaving a wireless network:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="auto-connect" rel="nofollow" id="auto-connect">Connettersi automaticamente a un network wireless</a></h3>
<p>To make your system connect to a given SSID at each boot automatically, you can specify your wireless networks and passwords in <tt>/boot/common/settings/network/wireless_networks</tt> with the following format:</p>
<pre>network wifitopia {
   password mypassword
}</pre>
<p>If you don't create this configuration file, the system will connect to the first unencrypted network it finds.</p>
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>Note sul WEP</strong></a></p>
<ul>
<li>64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex digits</li>
<li>128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex digits</li>
<li>hexadecimal digits = characters 0-9 and A through F (prepended with "0x" in <tt>ifconfig</tt>)</li>
</ul>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="wpa" rel="nofollow" id="wpa">WPA encryption</a></h3>
<p><p>At the moment there is no WPA encryption available in Haiku, though there have been <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">some efforts</a> bringing it significantly closer.</p></p>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="indice" /></a>
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
<p>Per installare il firmware per le schede ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx &amp; Marvell 88W8335, dovete far partire lo script</p>
<pre class="terminal">install-wifi-firmwares.sh
</pre>
<p>The Intel ipw2100 and iprowifi22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.</p>
<p>People building their own Haiku image can modify their <span class="cli">build/jam/UserBuildConfig</span> accordingly. Details for that and general updates on the wifi topic are found at the <a href="http://www.haiku-os.org/guides/wifi">online version of this document</a>.</p>
<p>If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">shell script</a>, which will create a zip file for you to extract to Haiku's <tt>/boot</tt>. After that you'll have all files needed by install-wifi-firmwares.sh.</p>
</div>
</div>
<div class="nav">
<div class="inner"><span>
<a href="../welcome_it.html" class="uplink">Welcome</a>
</span></div>
</div>
</body>
</html>
docs/welcome/jp/bugreports.html
+1 -1
View File
@@ -124,7 +124,7 @@
ここで注意することは、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> (別名 <span class="cli">sc</span>)</td><td> </td><td>バックトレースを出力する。システムが自ら KDL に入った場合、これを必ず実行する。</td></tr>
<tr><td><span class="cli">bt</span> (別名 <span class="cli">sc</span>)</td><td> </td><td>バックトレース (別名 stack crawl) を出力する。システムが自ら 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>
docs/welcome/jp/wifi.html
-161
View File
@@ -1,161 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!--
*
* Copyright 2010-2011, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
* Humdinger <humdingerb@gmail.com>
* Translators:
* Shota Fukumori
* log-1
* mt
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="robots" content="all" />
<title>Wifi</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>ユーザーガイド</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/jp.png" alt="" /> 日本語</li>
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
<a href="../welcome_jp.html" class="uplink">Welcome</a>
</span></div>
</div>
<div id="content">
<div>
<h2>Haiku での Wifi</h2>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="hardware" rel="nofollow" id="hardware">サポートされているハードウェア</a></h3>
<p>全ての FreeBSD 8 wlan ドライバーは動作すると思われます。ただし, PCMCIA, CardBus, ExpressCard, USB, ISA ベースのカードは動作しません。 PCI, miniPCI, PCI-Express, miniPCI-Express, PCI-X は動作すると思われます。<br />
以下のようなデバイスとドライバーをサポートします:</p>
<ul>
<li><p><i>aironetwifi</i> は少なくとも以下をサポートします<br />
Cisco Aironet 350 Series<br />
Aironet PCI4500<br />
Aironet PCI4800<br />
</p></li>
<li><p><i>atheroswifi</i> はそのチップを使うデバイスをサポートするでしょう (ただし AR9285 チップを除く)</p></li>
<li><p><i>broadcom43xx</i> は以下をサポートします<br />
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312, BCM4318
</p></li>
<li><p><i>iprowifi2100</i> は Intel Pro Wireless 2100 チップをサポートします</p></li>
<li><p><i>iprowifi2200</i> は以下の Intel Pro Wireless をサポートします<br />
2200BG<br />
2225BG<br />
2915ABG
</p></li>
<li><p><i>iprowifi3945</i> は Intel Pro Wireless 3945 チップをサポートします</p></li>
<li><p><i>iprowifi4965</i> は Intel Pro Wireless 4965 チップをサポートします</p></li>
<li><p><i>marvell88w8335</i> は以下をサポートします<br />
Marvell Libertas 88W8310<br />
Marvell Libertas 88W8335
</p></li>
<li><p><i>marvell88w8363</i> は 88W8363 チップをサポートします</p></li>
<li><p><i>ralinkwifi</i> は以下をサポートします<br />
RT2560<br />
RT2561S<br />
RT2561<br />
RT2661
</p></li>
<li><p>ralink2860 は Ralink RT2860 をサポートします。</p></li>
<li><p><i>wavelanwifi</i> は少なくとも以下をサポートします<br />
3Com Airconnect<br />
GLPRISM2 WaveLAN<br />
Intersil Prism3<br />
Intersil Prism2.5<br />
Linksys WDT11<br />
Netgear MA301<br />
PRISM2STA WaveLAN<br />
Siemens SpeedStream<br />
SMC 2602W<br />
Us Robotics 2415<br />
Addtron AWA-100 PCI
</p></li>
</ul>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="connect" rel="nofollow" id="connect">ワイヤレスネットワークへの接続</a></h3>
<p>Haiku は、暗号化されていないネットワークに加えて、<a href="#wep-notes" rel="nofollow">WEP 暗号化キー</a>を用いたネットワークアクセスの予備的なサポートがあります。 WEP は初期の暗号化メソッドで、もっともセキュアということではありません。</p>
<p>ターミナルからコマンド <span class="cli">ifconfig</span> を使って、利用可能なネットワークの一覧、ネットワーク接続、そしてネットワーク接続を閉じることができます。:</p>
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
<p><tt>wifi_device_path</tt> は、<span class="app">ネットワーク</span> プリファレンスアプレット、または <span class="cli">ifconfig -a</span> を実行することで見つけられます。</p>
<p>以下は、<i>wifitopia</i> と名付けたワイヤレスネットワークへの接続の例です。これらの例では、wifi ネットワークカードを <tt>/dev/net/iprowifi3945/0</tt> と仮定しています。</p>
<h4>ワイヤレスネットワークの一覧:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
<h4>暗号化されていないワイヤレスネットワークへの接続:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
<h4><a href="#wep-notes">WEP 暗号化された</a>ワイヤレスネットワークへの接続: (ascii パスワード)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
<h4><a href="#wep-notes">WEP 暗号化された</a> ワイヤレスネットワークへの接続: (64-bit 16 進数パスワード)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
<h4>ワイヤレスネットワーク接続を閉じる:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="auto-connect" rel="nofollow" id="auto-connect">自動的にワイヤレスネットワークに接続する</a></h3>
<p>起動毎にシステムを特定の SSID に自動的に接続させるために、<tt>/boot/common/settings/network/wireless_networks</tt> に次のフォーマットでワイヤレスネットワークとパスワードを記入してもよいです。</p>
<pre>network wifitopia {
   password mypassword
}</pre>
<p>この設定を作成していない場合、システムは最初に見つけた暗号化されていないネットワークに接続しようとするでしょう。</p>
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP ノート</strong></a></p>
<ul>
<li>64-bit WEP 暗号 は 40-bit のキーを使用します。 すなわち 13 文字の文字列か、26 桁の 16 進法キーです。</li>
<li>128-bit WEP 暗号 は 104-bit のキーを使用します。 すなわち 13 文字の文字列か、26 桁の 16 進法キーです。</li>
<li>16 進法キー = 0 から 9、A から F で構成された文字列 (<tt>ifconfig</tt> では "0x" を頭につける)</li>
</ul>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="wpa" rel="nofollow" id="wpa">WPA 暗号化</a></h3>
<p><p>今現在、Haiku では WPA 暗号を利用することができません。しかし、<a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">いくつかの努力</a>によりかなり近づいています。</p></p>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
<p>Intel ipw2100、Intel iprowifi2200/2225/2915、Broadcom 43xx &amp; Marvell 88W8335 のためのファームウェアをインストールするには、以下を実行する必要があります。</p>
<pre class="terminal">install-wifi-firmwares.sh
</pre>
<p>Haiku にオリジナルのファームウェアアーカイブを配布することをライセンス条項が許可しているため、 Intel ipw2011、iprowifi22xx はエンドユーザー承認があればインターネット接続無しでインストールできます。しかし、 Broadcom 43xx と Marvell 88W8335 は、Haiku と共に個別のファームウェアを配布できないため、アクティブなインターネット接続が必要です。</p>
<p>自分で Haiku イメージ をビルドしている方は、上述に従い、 <span class="cli">build/jam/UserBuildConfig</span> を編集することができます。 編集についての詳細と wifi の話題に関するとさまざまなアップデートは<a href="http://www.haiku-os.org/guides/wifi">このドキュメントのオンライン版</a>を参照してください。</p>
<p>もし、ファームウェアをダウンロードする必要があるが、Haiku 環境にインターネット接続が無い場合は、Haiku の <tt>/boot</tt> に展開するための zip ファイルを作成する<a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">シェルスクリプト</a>がオンライン版にあります。</p>
</div>
</div>
<div class="nav">
<div class="inner"><span>
<a href="../welcome_jp.html" class="uplink">Welcome</a>
</span></div>
</div>
</body>
</html>
docs/welcome/pl/bugreports.html
+2 -1
View File
@@ -56,6 +56,7 @@
<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>
@@ -122,7 +123,7 @@ W zależności od tego, co dokładnie uległo awarii, możesz spróbować zapisa
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> (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">bt</span> (lub <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace (aka stack crawl). If the system entered KDL on its on volition, a back trace is normally printed automatically. Enter the command if that didn't happen or part of it is obscured (e.g. when the stack trace is so long that it wrapped around) and your only way of providing the information to developers is by taking a picture of the screen.</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>
docs/welcome/pt_BR/bugreports.html
+1 -1
View File
@@ -125,7 +125,7 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
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> (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">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace (aka stack crawl). If the system entered KDL on its on volition, a back trace is normally printed automatically. Enter the command if that didn't happen or part of it is obscured (e.g. when the stack trace is so long that it wrapped around) and your only way of providing the information to developers is by taking a picture of the screen.</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>
docs/welcome/pt_PT/bugreports.html
+1 -1
View File
@@ -121,7 +121,7 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
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 <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">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace (aka stack crawl). If the system entered KDL on its on volition, a back trace is normally printed automatically. Enter the command if that didn't happen or part of it is obscured (e.g. when the stack trace is so long that it wrapped around) and your only way of providing the information to developers is by taking a picture of the screen.</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 <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>
docs/welcome/pt_PT/wifi.html
-159
View File
@@ -1,159 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!--
*
* Copyright 2010-2011, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
* Humdinger <humdingerb@gmail.com>
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="robots" content="all" />
<title>Wifi</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>User guide</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/pt_PT.png" alt="" /> Português</li>
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
<a href="../welcome_pt_PT.html" class="uplink">Welcome</a>
</span></div>
</div>
<div id="content">
<div>
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
<h2>Wifi in Haiku</h2>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="hardware" rel="nofollow" id="hardware">Expected supported hardware</a></h3>
<p>All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, PCI-Express, miniPci-Express and PCI-X are supposed to work.<br />
This includes:
</p>
<ul>
<li><p><i>aironetwifi</i> supporting at least<br />
Cisco Aironet 350 Series<br />
Aironet PCI4500<br />
Aironet PCI4800<br />
</p></li>
<li><p><i>atheroswifi</i> supporting almost every chipset outthere (though no AR9285 chips)</p></li>
<li><p><i>broadcom43xx</i> supporting<br />
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318
</p></li>
<li><p><i>ipw2100</i> supporting Intel Pro Wireless 2100 chips</p></li>
<li><p><i>iprowifi2200</i> supporting Intel Pro Wireless<br />
2200BG<br />
2225BG<br />
2915ABG
</p></li>
<li><p><i>iprowifi3945</i> supporting Intel Pro Wireless 3945 chips</p></li>
<li><p><i>iprowifi4965</i> supporting Intel Pro Wireless 4965 chips</p></li>
<li><p><i>marvell88w8335</i> supporting<br />
Marvell Libertas 88W8310<br />
Marvell Libertas 88W8335
</p></li>
<li><p><i>marvell88w8363</i> supporting the 88W8363 chips</p></li>
<li><p><i>ralinkwifi</i> supporting<br />
RT2560<br />
RT2561S<br />
RT2561<br />
RT2661
</p></li>
<li><p>ralink2860 supporting Ralink RT2860</p></li>
<li><p><i>wavelanwifi</i> supporting at least<br />
3Com Airconnect<br />
GLPRISM2 WaveLAN<br />
Intersil Prism3<br />
Intersil Prism2.5<br />
Linksys WDT11<br />
Netgear MA301<br />
PRISM2STA WaveLAN<br />
Siemens SpeedStream<br />
SMC 2602W<br />
Us Robotics 2415<br />
Addtron AWA-100 PCI
</p></li>
</ul>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="connect" rel="nofollow" id="connect">Connecting to a wireless network</a></h3>
<p>Besides of course unencrypted networks, Haiku has preliminary support for accessing wireless networks via <a href="#wep-notes" rel="nofollow">WEP encryption keys</a>. WEP is an early encryption method, although not the most secure.</p>
<p>You can list available networks, join and leave them with the command <span class="cli">ifconfig</span> from Terminal:</p>
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
<p>You can find your <tt>wifi_device_path</tt> in the <span class="app">Network</span> preferences applet, or by executing <span class="cli">ifconfig -a</span>.</p>
<p>Below are a few examples of connecting to a wireless network named <i>wifitopia</i>. For these examples we are assuming your wifi network card is <tt>/dev/net/iprowifi3945/0</tt>.</p>
<h4>Listing wireless networks:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
<h4>Joining unsecured wireless network:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (ascii password)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (64-bit hex password)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
<h4>Leaving a wireless network:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="auto-connect" rel="nofollow" id="auto-connect">Automatically connecting to a wireless network</a></h3>
<p>To make your system connect to a given SSID at each boot automatically, you can specify your wireless networks and passwords in <tt>/boot/common/settings/network/wireless_networks</tt> with the following format:</p>
<pre>network wifitopia {
   password mypassword
}</pre>
<p>If you don't create this configuration file, the system will connect to the first unencrypted network it finds.</p>
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP notes</strong></a></p>
<ul>
<li>64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex digits</li>
<li>128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex digits</li>
<li>hexadecimal digits = characters 0-9 and A through F (prepended with "0x" in <tt>ifconfig</tt>)</li>
</ul>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="wpa" rel="nofollow" id="wpa">WPA encryption</a></h3>
<p><p>At the moment there is no WPA encryption available in Haiku, though there have been <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">some efforts</a> bringing it significantly closer.</p></p>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
<p>To install the firmware for Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx &amp; Marvell 88W8335, you need to run</p>
<pre class="terminal">install-wifi-firmwares.sh
</pre>
<p>The Intel ipw2100 and iprowifi22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.</p>
<p>People building their own Haiku image can modify their <span class="cli">build/jam/UserBuildConfig</span> accordingly. Details for that and general updates on the wifi topic are found at the <a href="http://www.haiku-os.org/guides/wifi">online version of this document</a>.</p>
<p>If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">shell script</a>, which will create a zip file for you to extract to Haiku's <tt>/boot</tt>. After that you'll have all files needed by install-wifi-firmwares.sh.</p>
</div>
</div>
<div class="nav">
<div class="inner"><span>
<a href="../welcome_pt_PT.html" class="uplink">Welcome</a>
</span></div>
</div>
</body>
</html>
docs/welcome/ro/bugreports.html
+1 -1
View File
@@ -123,7 +123,7 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
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 <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">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace (aka stack crawl). If the system entered KDL on its on volition, a back trace is normally printed automatically. Enter the command if that didn't happen or part of it is obscured (e.g. when the stack trace is so long that it wrapped around) and your only way of providing the information to developers is by taking a picture of the screen.</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>
docs/welcome/ru/bugreports.html
+1 -2
View File
@@ -127,8 +127,7 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
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 <span class="cli">sc</span>)</td><td> </td><td><span class="cli">bt</span> - покажет трассировку, уточняющую где именно произошла ошибка.
Если система вошла в KDL самопроизвольно, всегда используйте эту команду.</td></tr>
<tr><td><span class="cli">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace (aka stack crawl). If the system entered KDL on its on volition, a back trace is normally printed automatically. Enter the command if that didn't happen or part of it is obscured (e.g. when the stack trace is so long that it wrapped around) and your only way of providing the information to developers is by taking a picture of the screen.</td></tr>
<tr><td><span class="cli">ints</span></td><td> </td><td><span class="cli">int</span> - отобразит обработанные и необработанные прерывания.</td></tr>
<tr><td class="onelinetop"><span class="cli">co</span> (синоним continue)</td><td> </td><td>выведет систему из отладчика ядра продолжит нормальную работу Haiku, если это возможно.</td></tr>
<tr><td><span class="cli">reboot</span></td><td> </td><td>Немедленно перезагрузит систему. Вы потеряете все несохраненные данные и те, что были сохранены, но еще не успели записаться из памяти обратно на диск.</td></tr>
docs/welcome/ru/wifi.html
-162
View File
@@ -1,162 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!--
*
* Copyright 2010-2011, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
* Humdinger <humdingerb@gmail.com>
* Translators:
* Diver
* Rodastahm Islamov
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="robots" content="all" />
<title>Беспроводная сеть Wifi</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>Руководство пользователя</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/ru.png" alt="" /> Русский</li>
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
<a href="../welcome_ru.html" class="uplink">Welcome</a>
</span></div>
</div>
<div id="content">
<div>
<h2>Беспроводная сеть Wifi в Haiku</h2>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="hardware" rel="nofollow" id="hardware">Поддерживаемое оборудование:</a></h3>
<p>Должны работать все wlan драйвера, поддерживаемые FreeBSD 8. <br />
Не поддерживаются все PCMCIA, CardBus, ExpressCard, USB и ISA карты. <br />Поддерживаются только PCI, miniPCI, PCI-Express, miniPci-Express и PCI-X.<br />
</p>
<ul>
<li><p><i>aironetwifi</i> поддерживает как минимум:<br />
Cisco Aironet 350 Series<br />
Aironet PCI4500<br />
Aironet PCI4800<br />
</p></li>
<li><p><i>atheroswifi</i> поддерживает почти все существующие чипсеты (кроме чипов AR9285)</p></li>
<li><p><i>broadcom43xx</i> поддерживает:<br />
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318
</p></li>
<li><p><i>iprowifi2100</i> поддерживает Intel Pro Wireless 2100 чипы</p></li>
<li><p><i>iprowifi2200</i> поддерживает следующие Intel Pro Wireless чипы:<br />
2200BG<br />
2225BG<br />
2915ABG
</p></li>
<li><p><i>iprowifi3945</i> поддерживает Intel Pro Wireless 3945 чипы</p></li>
<li><p><i>iprowifi4965</i> поддерживает Intel Pro Wireless 4965 чипы</p></li>
<li><p><i>marvell88w8335</i> поддерживает:<br />
Marvell Libertas 88W8310<br />
Marvell Libertas 88W8335
</p></li>
<li><p><i>marvell88w8363</i> поддерживает 88W8363 чипсет</p></li>
<li><p><i>ralinkwifi</i> поддерживает:<br />
RT2560<br />
RT2561S<br />
RT2561<br />
RT2661
</p></li>
<li><p>ralink2860 поддерживает Ralink RT2860 чипы</p></li>
<li><p><i>wavelanwifi</i> поддерживает как минимум:<br />
3Com Airconnect<br />
GLPRISM2 WaveLAN<br />
Intersil Prism3<br />
Intersil Prism2.5<br />
Linksys WDT11<br />
Netgear MA301<br />
PRISM2STA WaveLAN<br />
Siemens SpeedStream<br />
SMC 2602W<br />
Us Robotics 2415<br />
Addtron AWA-100 PCI
</p></li>
</ul>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="connect" rel="nofollow" id="connect">Подключение к беспроводной сети</a></h3>
<p>Помимо открытых беспроводных сетей Haiku поддерживает беспроводные сети с <a href="#wep-notes" rel="nofollow">WEP-шифрованием</a>. WEP является одним из первых методов шифрования для беспроводных сетей, поэтому считается устаревшим т.к. взламывается за пару минут.</p>
<p>Вы можете получить список доступных сетей, подключиться либо отключиться от сети при помощи команды <span class="cli">ifconfig</span>, используя Терминал:</p>
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
<p>Найти ваш <tt>wifi_device_path</tt> вы можете в окне настроек <span class="app">Сети (Network)</span>, либо выполнив в Терминале команду <span class="cli">ifconfig -a</span>.</p>
<p>Ниже приведены примеры подключения к сети с названием <i>wifitopia</i>, в которых предполагается, что вашей беспроводной картой является <tt>/dev/net/iprowifi3945/0</tt>.</p>
<h4>Список беспроводных сетей:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
<h4>Подключение к открытой беспроводной сети:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
<h4>Подключение к беспроводной сети с <a href="#wep-notes">WEP-шифрованием</a>: (ascii-пароль)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
<h4>Подключение к беспроводной сети с <a href="#wep-notes">WEP-шифрованием</a>: (64-битный hex-пароль)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
<h4>Отключение от беспроводной сети:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="auto-connect" rel="nofollow" id="auto-connect">Автоматическое подключение к беспроводной сети</a></h3>
<p>Для того, чтобы система после загрузки подключалась к определённой беспроводной сети, следует создать файл по следующему адресу:<tt>/boot/common/settings/network/wireless_networks</tt>, который имеет формат:</p>
<pre>network wifitopia {
   password mypassword
}</pre>
<p>Если вы не создадите этот файл, то система будет подключаться к первой попавшейся открытой сети.</p>
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>Примечания про WEP</strong></a></p>
<ul>
<li>64-битное WEP использует 40-битный ключ, что эквивалентно 5 буквам или 10 цифрам</li>
<li>128-битное WEP использует 104-битный ключ, что эквивалентно 13 буквам или 26 цифрам</li>
<li>шестнадцатеричная система = цифры 0-9 и буквы от A до F (начинающиеся с "0x" в <tt>ifconfig</tt>)</li>
</ul>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="wpa" rel="nofollow" id="wpa">WPA шифрование</a></h3>
<p><p>В настоящий момент WPA шифрование не поддерживается в Haiku. Однако сделана <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">попытка</a> добавить поддержку WPA.</p></p>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="install_script" rel="nofollow" id="install_script">Сценарий для установки микропрограмм (firmwares).</a></h3>
<p>Для установки микропрограмм для Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx и Marvell 88W8335 нужно запустить:</p>
<pre class="terminal">~&gt; install-wifi-firmwares.sh
</pre>
<p>Intel ipw2100 и iprowifi22xx установятся без Интернет-соединения, так как лицензионные условия позволяют Haiku распространять архивы с микропрограммой (firmware). Однако они требуют ознакомления конечного пользователя с условиями лицензии перед их установкой. Broadcom 43xx и Marvell 88W8335 требуют работающего Интернет-соединения, так как файлы, содержащие их микропрограммы (firmwares), не могут распространяться с Haiku.</p>
<p>Те, кто самостоятельно собирают собственные образы Haiku, могут соответственным образом изменить свой <span class="cli">build/jam/UserBuildConfig</span>. Описание этого процесса, а также обновление информации по поддержке wifi можно найти в <a href="http://www.haiku-os.org/guides/wifi">онлайн-версии</a> этого документа.</p>
<p>Если вы скачали микропрограмму (firmware), но не имеете работающего Интернет-соединения в Haiku, то онлайн-версия предлагает <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">скрипт</a>, который создаст для Вас zip файл, который нужно будет извлечь в директорию <tt>/boot</tt>. После этого у Вас будут все файлы, необходимые для запуска install-wifi-firmwares.sh.</p>
</div>
</div>
<div class="nav">
<div class="inner"><span>
<a href="../welcome_ru.html" class="uplink">Welcome</a>
</span></div>
</div>
</body>
</html>
docs/welcome/sk/bugreports.html
+1 -1
View File
@@ -124,7 +124,7 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
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> (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">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace (aka stack crawl). If the system entered KDL on its on volition, a back trace is normally printed automatically. Enter the command if that didn't happen or part of it is obscured (e.g. when the stack trace is so long that it wrapped around) and your only way of providing the information to developers is by taking a picture of the screen.</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>
docs/welcome/sk/wifi.html
-161
View File
@@ -1,161 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!--
*
* Copyright 2010-2011, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
* Humdinger <humdingerb@gmail.com>
* Translators:
* helix84
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="robots" content="all" />
<title>Wi-Fi</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>Používateľská príručka</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/sk.png" alt="" /> Slovenčina</li>
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
<a href="../welcome_sk.html" class="uplink">Welcome</a>
</span></div>
</div>
<div id="content">
<div>
<div class="box-info">Preklad tejto stránky zatiaľ nie je dokončený. Dovtedy sa nedokončené časti zobrazia v anglickom origináli.</div>
<h2>Wi-Fi v Haiku</h2>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="hardware" rel="nofollow" id="hardware">Expected supported hardware</a></h3>
<p>All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, PCI-Express, miniPci-Express and PCI-X are supposed to work.<br />
This includes:
</p>
<ul>
<li><p><i>aironetwifi</i> supporting at least<br />
Cisco Aironet 350 Series<br />
Aironet PCI4500<br />
Aironet PCI4800<br />
</p></li>
<li><p><i>atheroswifi</i> supporting almost every chipset outthere (though no AR9285 chips)</p></li>
<li><p><i>broadcom43xx</i> supporting<br />
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318
</p></li>
<li><p><i>ipw2100</i> supporting Intel Pro Wireless 2100 chips</p></li>
<li><p><i>iprowifi2200</i> supporting Intel Pro Wireless<br />
2200BG<br />
2225BG<br />
2915ABG
</p></li>
<li><p><i>iprowifi3945</i> supporting Intel Pro Wireless 3945 chips</p></li>
<li><p><i>iprowifi4965</i> supporting Intel Pro Wireless 4965 chips</p></li>
<li><p><i>marvell88w8335</i> supporting<br />
Marvell Libertas 88W8310<br />
Marvell Libertas 88W8335
</p></li>
<li><p><i>marvell88w8363</i> supporting the 88W8363 chips</p></li>
<li><p><i>ralinkwifi</i> supporting<br />
RT2560<br />
RT2561S<br />
RT2561<br />
RT2661
</p></li>
<li><p>ralink2860 supporting Ralink RT2860</p></li>
<li><p><i>wavelanwifi</i> supporting at least<br />
3Com Airconnect<br />
GLPRISM2 WaveLAN<br />
Intersil Prism3<br />
Intersil Prism2.5<br />
Linksys WDT11<br />
Netgear MA301<br />
PRISM2STA WaveLAN<br />
Siemens SpeedStream<br />
SMC 2602W<br />
Us Robotics 2415<br />
Addtron AWA-100 PCI
</p></li>
</ul>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="connect" rel="nofollow" id="connect">Connecting to a wireless network</a></h3>
<p>Besides of course unencrypted networks, Haiku has preliminary support for accessing wireless networks via <a href="#wep-notes" rel="nofollow">WEP encryption keys</a>. WEP is an early encryption method, although not the most secure.</p>
<p>You can list available networks, join and leave them with the command <span class="cli">ifconfig</span> from Terminal:</p>
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
<p>You can find your <tt>wifi_device_path</tt> in the <span class="app">Network</span> preferences applet, or by executing <span class="cli">ifconfig -a</span>.</p>
<p>Below are a few examples of connecting to a wireless network named <i>wifitopia</i>. For these examples we are assuming your wifi network card is <tt>/dev/net/iprowifi3945/0</tt>.</p>
<h4>Listing wireless networks:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
<h4>Joining unsecured wireless network:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (ascii password)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (64-bit hex password)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
<h4>Leaving a wireless network:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="auto-connect" rel="nofollow" id="auto-connect">Automatically connecting to a wireless network</a></h3>
<p>To make your system connect to a given SSID at each boot automatically, you can specify your wireless networks and passwords in <tt>/boot/common/settings/network/wireless_networks</tt> with the following format:</p>
<pre>network wifitopia {
   password mypassword
}</pre>
<p>If you don't create this configuration file, the system will connect to the first unencrypted network it finds.</p>
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP notes</strong></a></p>
<ul>
<li>64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex digits</li>
<li>128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex digits</li>
<li>hexadecimal digits = characters 0-9 and A through F (prepended with "0x" in <tt>ifconfig</tt>)</li>
</ul>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="wpa" rel="nofollow" id="wpa">Šifrovanie WPA</a></h3>
<p><p>At the moment there is no WPA encryption available in Haiku, though there have been <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">some efforts</a> bringing it significantly closer.</p></p>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
<p>To install the firmware for Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx &amp; Marvell 88W8335, you need to run</p>
<pre class="terminal">install-wifi-firmwares.sh
</pre>
<p>The Intel ipw2100 and iprowifi22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.</p>
<p>People building their own Haiku image can modify their <span class="cli">build/jam/UserBuildConfig</span> accordingly. Details for that and general updates on the wifi topic are found at the <a href="http://www.haiku-os.org/guides/wifi">online version of this document</a>.</p>
<p>If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">shell script</a>, which will create a zip file for you to extract to Haiku's <tt>/boot</tt>. After that you'll have all files needed by install-wifi-firmwares.sh.</p>
</div>
</div>
<div class="nav">
<div class="inner"><span>
<a href="../welcome_sk.html" class="uplink">Welcome</a>
</span></div>
</div>
</body>
</html>
docs/welcome/sv_SE/bugreports.html
+1 -1
View File
@@ -123,7 +123,7 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
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 <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">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace (aka stack crawl). If the system entered KDL on its on volition, a back trace is normally printed automatically. Enter the command if that didn't happen or part of it is obscured (e.g. when the stack trace is so long that it wrapped around) and your only way of providing the information to developers is by taking a picture of the screen.</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 <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>
docs/welcome/sv_SE/wifi.html
-158
View File
@@ -1,158 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!--
*
* Copyright 2010-2011, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
* Humdinger <humdingerb@gmail.com>
* Translators:
* deejam
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="robots" content="all" />
<title>Wifi</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>Användarhandbok</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/sv_SE.png" alt="" /> Svenska</li>
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
<a href="../welcome_sv_SE.html" class="uplink">Welcome</a>
</span></div>
</div>
<div id="content">
<div>
<h2>Wifi i Haiku</h2>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="hardware" rel="nofollow" id="hardware">Hårdvara som förväntas fungera</a></h3>
<p>Haiku har inbyggt stöd för alla trådlösa enheter som finns i FreeBSD 8. PCMCIA, CardBus, ExpressCard, USB eller ISA-baserade kort stöds inte. Endast PCI, miniPCI, PCI-Express, miniPCI-Express och PCI-X skall fungera.<br />Detta inkluderar:</p>
<ul>
<li><p><i>aironetwifi</i> stöder åtminstone<br />
Cisco Aironet 350 Series<br />
Aironet PCI4500<br />
Aironet PCI4800<br />
</p></li>
<li><p><i>atheroswifi</i> stöder nästan alla tillgängliga chipset (dock inte AR9285)</p></li>
<li><p><i>broadcom43xx</i> stöder<br />
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 och BCM4318
</p></li>
<li><p><i>ipw2100</i> stöder Intel Pro Wireless 2100</p></li>
<li><p><i>iprowifi2200</i> stöder Intel Pro Wireless<br />
2200BG<br />
2225BG<br />
2915ABG
</p></li>
<li><p><i>iprowifi3945</i> stöder Intel Pro Wireless 3945</p></li>
<li><p><i>iprowifi4965</i> stöder Intel Pro Wireless 4965</p></li>
<li><p><i>marvell88w8335</i> stöder<br />
Marvell Libertas 88W8310<br />
Marvell Libertas 88W8335
</p></li>
<li><p><i>marvell88w8363</i> stöder 88W8363</p></li>
<li><p><i>ralinkwifi</i> stöder<br />
RT2560<br />
RT2561S<br />
RT2561<br />
RT2661
</p></li>
<li><p>ralink2860 stöder Ralink RT2860</p></li>
<li><p><i>wavelanwifi</i> stöder åtminstone<br />
3Com Airconnect<br />
GLPRISM2 WaveLAN<br />
Intersil Prism3<br />
Intersil Prism2.5<br />
Linksys WDT11<br />
Netgear MA301<br />
PRISM2STA WaveLAN<br />
Siemens SpeedStream<br />
SMC 2602W<br />
Us Robotics 2415<br />
Addtron AWA-100 PCI
</p></li>
</ul>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="connect" rel="nofollow" id="connect">Ansluta till trådlösa nätverk</a></h3>
<p>Haiku har - utöver okrypterade nätverk - preliminärt stöd för att ansluta till trådlösa nätverk med <a href="#wep-notes" rel="nofollow">WEP kryptering</a>. WEP är en tidig krypteringsmetod och därmed inte den säkraste.</p>
<p>Du kan se tillgängliga nätverk, ansluta och koppla ner med kommandot <span class="cli">ifconfig</span> via Terminalen:</p>
<pre class="terminal">ifconfig [sökväg_till_wifi_enhet] [list|join|leave] (nyckel)</pre>
<p>Du kan se din <tt>sökväg_till_wifi_enhet</tt> i inställningar för <span class="app">Nätverk</span>, eller genom att köra <span class="cli">ifconfig -a</span>.</p>
<p>Nedan finns några exempel för hur man ansluter till ett trådlöst nätverk med namnet <i>wifitopia</i>. För dessa exempel antar vi att ditt trådlösa nätverkskort är <tt>/dev/net/iprowifi3945/0</tt>.</p>
<h4>Lista trådlösa nätverk:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
<h4>Ansluta till ett okrypterat trådlöst nätverk:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
<h4>Ansluta till ett <a href="#wep-notes">WEP krypterat</a> trådlöst nätverk: (med ett ascii lösenord)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mitt_lösenord</pre>
<h4>Ansluta till ett <a href="#wep-notes">WEP krypterat</a> trådlöst nätverk: (64-bitars hexadecimalt lösenord)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
<h4>Koppla ifrån ett trådlöst nätverk:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="auto-connect" rel="nofollow" id="auto-connect">Ansluta automatiskt till ett trådlöst nätverk</a></h3>
<p>För att ansluta till ett nätverk vid varje uppstart kan du specifiera namnet på ditt trådlösa nätverk och lösenord i <tt>/boot/common/settings/network/wireless_networks</tt> med följande format:</p>
<pre>network wifitopia {
   password mitt_lösenord
}</pre>
<p>Om du inte skapar denna konfigurationsfil så kommer Haiku att ansluta till det första okrypterade nätverket som hittas.</p>
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP kommentarer</strong></a></p>
<ul>
<li>64-bitars WEP använder en 40-bitars nyckel, vilket betyder 5 bokstäver eller 10 hexadecimala siffror.</li>
<li>128-bitars WEP använder en 104-bitars nyckel, vilket betyder 13 bokstäver eller 26 hexadecimala siffror.</li>
<li>hexadecimala siffror = siffrorna 0-9 samt A till och med F (med "0x" i början)</li>
</ul>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="wpa" rel="nofollow" id="wpa">WPA kryptering</a></h3>
<p><p>För tillfället finns inte WPA kryptering tillgängligt i Haiku, även om det det har gjorts <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">ansträngningar</a> som har fört det allt närmare.</p></p>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="install_script" rel="nofollow" id="install_script">Skriptet install-wifi-firmwares.sh</a></h3>
<p>För att installera mikroprogramvaran för Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx och Marvell 88W8335 behöver du köra skriptet:</p>
<pre class="terminal">install-wifi-firmwares.sh
</pre>
<p>Intel ipw2100 och iprowifi22xx kan installeras utan en internetanslutning eftersom licensvilkoren tillåter Haiku att distribuera mikroprogramvaran. Dock krävs det att användaren godkänner licensvilkoren innan installationen. För Broadcom 43xx och Marvell 88W8335 krävs en internetanslutning eftersom respektive mikroprogramvara inte får distribueras med Haiku.</p>
<p>Personer som bygger egna Haiku avbilder kan modifiera deras <span class="cli">build/jam/UserBuildConfig</span> därefter. Detaljer för detta och generella uppdateringar i ämnet wifi finns på <a href="http://www.haiku-os.org/guides/wifi">detta dokument på internet</a>.</p>
<p>Om du behöver ladda ner mikroprogramvaran men saknar en fungerande internetanslutning i Haku så erbjuder internetversionen ett <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">skalskript</a> som hämtar de filer som behövs och sparar det i en komprimerad fil. FIlen skall packas upp till Haiku's <tt>/boot</tt> katalog. Efter det kommer du att ha alla filer som du behöver för att använda install-wifi-firmwares.sh skriptet.</p>
</div>
</div>
<div class="nav">
<div class="inner"><span>
<a href="../welcome_sv_SE.html" class="uplink">Welcome</a>
</span></div>
</div>
</body>
</html>
docs/welcome/uk/bugreports.html
+1 -1
View File
@@ -123,7 +123,7 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
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 <span class="cli">sc</span>)</td><td> </td><td>виводити зворотнє трасування. Якщо система потрапила у KDL за власним бажанням завжди набирайте цю команду.</td></tr>
<tr><td><span class="cli">bt</span> (aka <span class="cli">sc</span>)</td><td> </td><td>Prints a back trace (aka stack crawl). If the system entered KDL on its on volition, a back trace is normally printed automatically. Enter the command if that didn't happen or part of it is obscured (e.g. when the stack trace is so long that it wrapped around) and your only way of providing the information to developers is by taking a picture of the screen.</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>
docs/welcome/uk/wifi.html
-159
View File
@@ -1,159 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!--
*
* Copyright 2010-2011, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
* Humdinger <humdingerb@gmail.com>
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="robots" content="all" />
<title>Wifi</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>User guide</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/uk.png" alt="" /> Українська</li>
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
<a href="../welcome_uk.html" class="uplink">Welcome</a>
</span></div>
</div>
<div id="content">
<div>
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
<h2>Wifi in Haiku</h2>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="hardware" rel="nofollow" id="hardware">Expected supported hardware</a></h3>
<p>All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, PCI-Express, miniPci-Express and PCI-X are supposed to work.<br />
This includes:
</p>
<ul>
<li><p><i>aironetwifi</i> supporting at least<br />
Cisco Aironet 350 Series<br />
Aironet PCI4500<br />
Aironet PCI4800<br />
</p></li>
<li><p><i>atheroswifi</i> supporting almost every chipset outthere (though no AR9285 chips)</p></li>
<li><p><i>broadcom43xx</i> supporting<br />
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318
</p></li>
<li><p><i>ipw2100</i> supporting Intel Pro Wireless 2100 chips</p></li>
<li><p><i>iprowifi2200</i> supporting Intel Pro Wireless<br />
2200BG<br />
2225BG<br />
2915ABG
</p></li>
<li><p><i>iprowifi3945</i> supporting Intel Pro Wireless 3945 chips</p></li>
<li><p><i>iprowifi4965</i> supporting Intel Pro Wireless 4965 chips</p></li>
<li><p><i>marvell88w8335</i> supporting<br />
Marvell Libertas 88W8310<br />
Marvell Libertas 88W8335
</p></li>
<li><p><i>marvell88w8363</i> supporting the 88W8363 chips</p></li>
<li><p><i>ralinkwifi</i> supporting<br />
RT2560<br />
RT2561S<br />
RT2561<br />
RT2661
</p></li>
<li><p>ralink2860 supporting Ralink RT2860</p></li>
<li><p><i>wavelanwifi</i> supporting at least<br />
3Com Airconnect<br />
GLPRISM2 WaveLAN<br />
Intersil Prism3<br />
Intersil Prism2.5<br />
Linksys WDT11<br />
Netgear MA301<br />
PRISM2STA WaveLAN<br />
Siemens SpeedStream<br />
SMC 2602W<br />
Us Robotics 2415<br />
Addtron AWA-100 PCI
</p></li>
</ul>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="connect" rel="nofollow" id="connect">Connecting to a wireless network</a></h3>
<p>Besides of course unencrypted networks, Haiku has preliminary support for accessing wireless networks via <a href="#wep-notes" rel="nofollow">WEP encryption keys</a>. WEP is an early encryption method, although not the most secure.</p>
<p>You can list available networks, join and leave them with the command <span class="cli">ifconfig</span> from Terminal:</p>
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
<p>You can find your <tt>wifi_device_path</tt> in the <span class="app">Network</span> preferences applet, or by executing <span class="cli">ifconfig -a</span>.</p>
<p>Below are a few examples of connecting to a wireless network named <i>wifitopia</i>. For these examples we are assuming your wifi network card is <tt>/dev/net/iprowifi3945/0</tt>.</p>
<h4>Listing wireless networks:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
<h4>Joining unsecured wireless network:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (ascii password)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (64-bit hex password)</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
<h4>Leaving a wireless network:</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="auto-connect" rel="nofollow" id="auto-connect">Automatically connecting to a wireless network</a></h3>
<p>To make your system connect to a given SSID at each boot automatically, you can specify your wireless networks and passwords in <tt>/boot/common/settings/network/wireless_networks</tt> with the following format:</p>
<pre>network wifitopia {
   password mypassword
}</pre>
<p>If you don't create this configuration file, the system will connect to the first unencrypted network it finds.</p>
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP notes</strong></a></p>
<ul>
<li>64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex digits</li>
<li>128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex digits</li>
<li>hexadecimal digits = characters 0-9 and A through F (prepended with "0x" in <tt>ifconfig</tt>)</li>
</ul>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="wpa" rel="nofollow" id="wpa">WPA encryption</a></h3>
<p><p>At the moment there is no WPA encryption available in Haiku, though there have been <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">some efforts</a> bringing it significantly closer.</p></p>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
<p>To install the firmware for Intel ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx &amp; Marvell 88W8335, you need to run</p>
<pre class="terminal">install-wifi-firmwares.sh
</pre>
<p>The Intel ipw2100 and iprowifi22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.</p>
<p>People building their own Haiku image can modify their <span class="cli">build/jam/UserBuildConfig</span> accordingly. Details for that and general updates on the wifi topic are found at the <a href="http://www.haiku-os.org/guides/wifi">online version of this document</a>.</p>
<p>If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">shell script</a>, which will create a zip file for you to extract to Haiku's <tt>/boot</tt>. After that you'll have all files needed by install-wifi-firmwares.sh.</p>
</div>
</div>
<div class="nav">
<div class="inner"><span>
<a href="../welcome_uk.html" class="uplink">Welcome</a>
</span></div>
</div>
</body>
</html>
docs/welcome/welcome_ca.html
+3 -3
View File
@@ -94,13 +94,13 @@
<p>The first release(s) of Haiku will be very much like the BeOS R5, the operating system it is reimplementing. If you never experienced it, have a look at these links:</p>
<ul>
<li><a href="../userguide/ca/contents.html">Haiku User Guide</a></li>
<li><a href="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">Get help and support and become a part of the community</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Instal·leu més programari</a></h2>
<p>Most of the available software can be downloaded and installed with the application HaikuDepot that comes with Haiku.<br />
<p>Most of the available software can be downloaded and installed with the application <a href="../userguide/ca/applications/haikudepot.html">HaikuDepot</a> that comes with Haiku.<br />
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/ca/applications.html">Applications</a>.</p>
<p>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>
@@ -108,7 +108,7 @@ Because of our binary and source compatibility, most BeOS applications run on Ha
<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/ca/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>
For more details, see the guide <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Updating and downgrading your system</a> on our website.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
docs/welcome/welcome_de.html
+3 -3
View File
@@ -94,13 +94,13 @@
<p>Zumindest zu Beginn wird sich Haiku sehr eng an sein Vorbild BeOS R5 halten. Insbesondere wer mit diesem Betriebssystem keine Erfahrungen sammeln durfte, seien diese Links empfohlen:</p>
<ul>
<li><a href="../userguide/de/contents.html">Haiku User Guide</a></li>
<li><a href="https://www.haiku-os.org/community/" class="printurl">BeOS/Haiku Webseiten</a></li>
<li><a href="https://www.haiku-os.org/community/" class="printurl">Finde Hilfe und werde Teil der Haiku Gemeinschaft</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Software installieren</a></h2>
<p>Ein Großteil der vorhandenen Software kann mit der mit Haiku kommenden HaikuDepot Anwendung heruntergeladen und installiert werden.<br />
<p>Ein Großteil der vorhandenen Software kann mit der mit Haiku kommenden <a href="../userguide/de/applications/haikudepot.html">HaikuDepot</a> Anwendung heruntergeladen und installiert werden.<br />
Da Haiku sowohl binärkompatibel als auch code-kompatibel mit BeOS ist, laufen viele BeOS-Anwendungen auch direkt in Haiku. Die meisten von ihnen wurden für Haiku passend neu gepackt oder funktionieren auch ohne Änderungen. Weitere Informationen zur Installation neuer Anwendungen finden sich im Kapitel <a href="../userguide/de/applications.html">Anwendungen</a> im Haiku User Guide.</p>
<p>Es existieren einige von Haiku Enthusiasten gepflegte Software Sammlungen, siehe die Liste <a href="https://www.haiku-os.org/community/software">Software Sites</a> auf der Webseite.</p>
@@ -108,7 +108,7 @@ Da Haiku sowohl binärkompatibel als auch code-kompatibel mit BeOS ist, laufen v
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="update" name="update">Haiku aktualisieren</a></h2>
<p>Haiku wird genau wie alle Pakete mit der Anwendung <a href="../userguide/de/applications/softwareupdater.html">SoftwareUpdater</a> aktualisiert. Nach Abschluss des Aktualisierungsvorgangs, Haiku neu starten.<br />
Für weitere Details, siehe <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Updating your system</a> (Englisch) auf der Webseite.</p>
Für weitere Details, siehe <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Updating and downgrading your system</a> (Englisch) auf der Webseite.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
docs/welcome/welcome_en.html
+3 -3
View File
@@ -90,13 +90,13 @@
<p>The first release(s) of Haiku will be very much like the BeOS R5, the operating system it is reimplementing. If you never experienced it, have a look at these links:</p>
<ul>
<li><a href="../userguide/en/contents.html">Haiku User Guide</a></li>
<li><a href="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">Get help and support and become a part of the community</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Installing more software</a></h2>
<p>Most of the available software can be downloaded and installed with the application HaikuDepot that comes with Haiku.<br />
<p>Most of the available software can be downloaded and installed with the application <a href="../userguide/en/applications/haikudepot.html">HaikuDepot</a> that comes with Haiku.<br />
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/en/applications.html">Applications</a>.</p>
<p>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>
@@ -104,7 +104,7 @@ Because of our binary and source compatibility, most BeOS applications run on Ha
<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/en/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>
For more details, see the guide <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Updating and downgrading your system</a> on our website.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
docs/welcome/welcome_es.html
+13 -14
View File
@@ -58,7 +58,6 @@
<div id="content">
<div>
<div class="box-info">La traducción de esta página no está completa aún. Hasta que esté, las partes sin 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 +74,16 @@
<h2>
<a id="welcome" name="welcome">¡Bienvenido a Haiku!</a></h2>
<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>¡Gracias por poner Haiku a prueba! Este es nuestra quinta entrega al público. Esperamos atraer nuevos desarrolladores a este proyecto y darle a los usuarios una oportunidad para probar Haiku. Aún cuando esta primera <i>versión beta</i> incluye todas las principales características planeadas para la versión final de Haiku, todavía existen muchos fallos y algunas asperezas que hay que limar. No obstante, consideramos que esta entrega es muy funcional, y esperamos que le permita descubrir el gran potencial de Haiku, y que pueda compartir nuestro entusiasmo.</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>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>Hemos trabajado muy duro para resolver todas los fallas más críticas, sin embargo, ya que es una versión beta, es muy probable que existan algunas por descubrir.</p>
<div class="box-warning">No recomendamos el uso de versiones beta en sistemas de producción. Sus datos podrían resultar alterados, estropeados o incluso destruidos. ¡Conserve copias de respaldo al día!</div>
<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>
<p>Una de las razones principales para liberar una versión beta es atraer más gente para poner a prueba el sistema y descubrir fallos o darnos sugerencias para futuras mejoras. Por favor, envíe informes de fallos y mejoras en nuestro bug tracker, luego de utilizar su sistema de búsqueda, para evitar duplicados.</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>
@@ -96,21 +95,21 @@
<p>Las primeras versiones de Haiku serán muy similares a BeOS R5, el sistema operativo que está recreando. Si nunca lo ha probado, puede mirar estos enlaces:</p>
<ul>
<li><a href="../userguide/es/contents.html">Guía de usuario de Haiku</a></li>
<li><a href="https://www.haiku-os.org/community/" class="printurl">Lista de sitios web acerca de BeOS/Haiku</a></li>
<li><a href="https://www.haiku-os.org/community/" class="printurl">Reciba ayuda y soporte y vuélvase parte de la comunidad</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Instalar más software</a></h2>
<p>La mayoría del software disponible se puede descargar e instalar con la aplicación HaikuDepot que viene con Haiku.<br />
Debido a nuestra compatibilidad de código fuente y binario, muchas aplicaciones de BeOS funcionan en Haiku. Muchas de ellas han sido re-empaquetadas para Haiku o todavía corren sin necesidad de modificarse. Puede encontrar más información sobre cómo instalar nuevos programas en el capítulo de la Guía de Usuario en <a href="../userguide/es/applications.html">Aplicaciones</a>.</p>
<p>La mayoría del software disponible se puede descargar e instalar con la aplicación <a href="../userguide/es/applications/haikudepot.html">HaikuDepot</a> que viene con Haiku.<br />
Debido a nuestra compatibilidad de código fuente y binario, muchas aplicaciones de BeOS funcionan bien en Haiku. Muchas de ellas han sido re-empaquetadas para Haiku o todavía corren sin necesidad de ser modificadas. Puede encontrar más información sobre cómo instalar nuevos programas en el capítulo <a href="../userguide/es/applications.html">Aplicaciones</a>, en la Guía de Usuario.</p>
<p>Existen varias colecciones de software basados en la comunidad. Vea la página <a href="https://www.haiku-os.org/community/software">Sitios de Software (en inglés)</a> en nuestro sitio.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="update" name="update">Actualizar Haiku</a></h2>
<p>Updating Haiku as well as third party packages is done with the application <a href="../userguide/es/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">Actualización de Haiku</a></h2>
<p>Haiku y los paquetes de terceros se actualizan con la aplicacion <a href="../userguide/es/applications/softwareupdater.html">SoftwareUpdater</a>. Cuando la actualización esté completa, reinicie.<br />
Para más detalles, vea la guía <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Actualizar su sistema</a> en nuestro sitio.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
@@ -140,9 +139,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="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.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.haiku-os.org/community/ml" class="printurl">Panorama de todas las listas de correo</a>.</li>
</ul>
docs/welcome/welcome_fi.html
+5 -5
View File
@@ -93,21 +93,21 @@
<p>Haikun ensimmäiset julkaisut ovat paljolti kuin BeOS R5, käyttöjärjestelmän uudelleentoteutus. Jos et ole koskaan kokenut sitä, vilkaise näitä linkkejä:</p>
<ul>
<li><a href="../userguide/fi/contents.html">Haiku-käyttäjäopas</a></li>
<li><a href="https://www.haiku-os.org/community/" class="printurl">BeOS/Haiku -webbisivustojen luettelo</a></li>
<li><a href="https://www.haiku-os.org/community/" class="printurl">Get help and support and become a part of the community</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Lisäohjelmistojen asentaminen</a></h2>
<p>Useimmat saatavilla olevat ohjelmistot voidaan ladata ja asentaa HaikuDepot-sovelluksella, joka tulee Haikun mukana.<br />
Binaari- ja lähdekoodiyhteensopivuuden vuoksi monia BeOS-sovelluksia voidaan suorittaa Haikussa. Monet niistä on pakattu uudelleen Haikua varten tai ne suoritetaan yhä muokkaamattomina. Löydät lisätietoja uusien ohjelmien asentamisesta käyttöoppaan kappaleesta <a href="../userguide/fi/applications.html">Sovellukset</a>.</p>
<p>Most of the available software can be downloaded and installed with the application <a href="../userguide/fi/applications/haikudepot.html">HaikuDepot</a> that comes with Haiku.<br />
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/fi/applications.html">Applications</a>.</p>
<p>On olemassa useita yhteisöpohjaisia ohjelmistokokoelmia. Katso <a href="https://www.haiku-os.org/community/software">Ohjelmistosivustot</a>-sivua webbisivustollamme.</p>
<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>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>
<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 and downgrading your system</a> on our website.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
docs/welcome/welcome_fr.html
+6 -4
View File
@@ -58,6 +58,7 @@
<div id="content">
<div>
<div class="box-info">Cette page n'est pas encore entièrement traduite. Les parties non encore traduites seront en anglais.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Index</td></tr>
@@ -95,20 +96,21 @@
<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">Liste des sites web consacrés à BeOS/Haiku</a> (en anglais)</li>
<li><a href="https://www.haiku-os.org/community/" class="printurl">Get help and support and become a part of the community</a></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>Most of the available software can be downloaded and installed with the application <a href="../userguide/fr/applications/haikudepot.html">HaikuDepot</a> 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/fr/applications.html">Applications</a>.</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">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>
<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 and downgrading your system</a> on our website.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
docs/welcome/welcome_hu.html
+4 -5
View File
@@ -94,22 +94,21 @@
<p>A Haiku sok tekintetben hasonlít a BeOS R5-ös verziójára, ezért tekinthetjük a modern reinkarnációjának is. Ha eddig még nem találkoztál a rendszerrel, akkor ajánlom figyelmedbe a következő oldalakat:</p>
<ul>
<li><a href="../userguide/hu/contents.html">Haiku felhasználói útmutató</a></li>
<li><a href="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">Get help and support and become a part of the community</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Új programok telepítése</a></h2>
<p>A legtöbb program elérhető a Raktár-ból, mely a Haiku részét képezi.
A bináris kompatibilitás miatt sok BeOS-ra készült program futtatható Haiku-n. Közülük több is újra lett csomagolva a Haiku-nak megfelelően vagy eredeti formájában is használható.
További információk a <a href="../userguide/hu/applications.html">Programok</a> fejezetben.</p>
<p>Most of the available software can be downloaded and installed with the application <a href="../userguide/hu/applications/haikudepot.html">HaikuDepot</a> 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/hu/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>
<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/hu/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>
For more details, see the guide <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Updating and downgrading your system</a> on our website.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
docs/welcome/welcome_it.html
+3 -3
View File
@@ -94,13 +94,13 @@
<p>Le prime release di Haiku saranno molto simili al BeOS R5, il sistema operativo che sta re-implementando. Se non l'hai mai provato, dai un'occhiata a questi link:</p>
<ul>
<li><a href="../userguide/it/contents.html">Guida dell'utente Haiku</a></li>
<li><a href="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">Get help and support and become a part of the community</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="indice" /></a>
<a id="software" name="software">Installare altre applicazioni</a></h2>
<p>Most of the available software can be downloaded and installed with the application HaikuDepot that comes with Haiku.<br />
<p>Most of the available software can be downloaded and installed with the application <a href="../userguide/it/applications/haikudepot.html">HaikuDepot</a> that comes with Haiku.<br />
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/it/applications.html">Applications</a>.</p>
<p>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>
@@ -108,7 +108,7 @@ Because of our binary and source compatibility, most BeOS applications run on Ha
<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/it/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>
For more details, see the guide <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Updating and downgrading your system</a> on our website.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="indice" /></a>
docs/welcome/welcome_jp.html
+3 -3
View File
@@ -95,20 +95,20 @@
<p>最初の Haiku のリリースは BeOS R5 の再実装のようになる予定ですが、まだ体験していないならこれらも見ると良いでしょう:</p>
<ul>
<li><a href="../userguide/jp/contents.html">Haiku ユーザーガイド</a></li>
<li><a href="https://www.haiku-os.org/community/" class="printurl">BeOS および Haiku 関連ウェブサイト一覧</a></li>
<li><a href="https://www.haiku-os.org/community/" class="printurl">ヘルプとサポート、そしてコミュニティーの一員になるには</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">ソフトウェアを追加する</a></h2>
<p>ほとんどの利用可能なソフトウェアは、Haiku に付属のアプリケーション、HaikuDepot でダウンロードおよびインストールできます。<br />ほとんどの BeOS 向けアプリケーションはバイナリとソースコードの互換性から Haiku でも動作すると思われます。その多くは Haiku 用に再パッケージされているか、修正なしに動作します。新しいアプリケーションのインストールに関する追加の情報はユーザーガイドの<a href="../userguide/jp/applications.html">アプリケーション</a>の章に見つかります。</p>
<p>ほとんどの利用可能なソフトウェアは、Haiku に付属のアプリケーション、<a href="../userguide/jp/applications/haikudepot.html">HaikuDepot</a> でダウンロードおよびインストールできます。<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>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="update" name="update">Haiku をアップデートする</a></h2>
<p>Haiku の更新は、サードパーティパッケージのアップデートと同様に、<a href="../userguide/jp/applications/softwareupdater.html">ソフトウェアの更新 (SoftwareUpdater)</a> アプリケーションで行います。アップデート終了後、再起動します。<br />
更に詳しくは、ウェブサイトのガイド、<a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">システムをアップデートする</a> を参照ください。</p>
更に詳しくは、ウェブサイトのガイド、<a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">システムのアップデートとダウングレード</a> を参照ください。</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
docs/welcome/welcome_pl.html
+5 -5
View File
@@ -93,21 +93,21 @@
<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">Lista stron o BeOS/Haiku</a></li>
<li><a href="https://www.haiku-os.org/community/" class="printurl">Get help and support and become a part of the community</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>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>Most of the available software can be downloaded and installed with the application <a href="../userguide/pl/applications/haikudepot.html">HaikuDepot</a> 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>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">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>
<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 and downgrading your system</a> on our website.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
docs/welcome/welcome_pt_BR.html
+4 -4
View File
@@ -94,21 +94,21 @@
<p>A primeira versão do Haiku será muito mais como o BeOS R5, o sistema operacional que está sendo reimplementado. Se você nunca o experimentou, dê uma olhada nestes vínculos:</p>
<ul>
<li><a href="../userguide/pt_BR/contents.html">Guia do Usuário Haiku</a></li>
<li><a href="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">Get help and support and become a part of the community</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Instalando mais software</a></h2>
<p>A maioria do software disponível pode ser baixado e instalado com o aplicativo Depósito Haiku, que vem com o Haiku.<br />
Por causa da sua compatibilidade de código e binária, muitos aplicativos BeOS executam no Haiku. Muitos deles foram reempacotados para o Haiku ou ainda executam sem modificações. Você encontrará mais informações sobre instalar novos programas no capítulo <a href="../userguide/pt_BR/applications.html">Aplicativos</a> do guia do usuário.</p>
<p>Most of the available software can be downloaded and installed with the application <a href="../userguide/pt_BR/applications/haikudepot.html">HaikuDepot</a> that comes with Haiku.<br />
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/pt_BR/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>
<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/pt_BR/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>
For more details, see the guide <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Updating and downgrading your system</a> on our website.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
docs/welcome/welcome_pt_PT.html
+3 -3
View File
@@ -91,13 +91,13 @@
<p>The first release(s) of Haiku will be very much like the BeOS R5, the operating system it is reimplementing. If you never experienced it, have a look at these links:</p>
<ul>
<li><a href="../userguide/pt_PT/contents.html">Haiku User Guide</a></li>
<li><a href="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">Get help and support and become a part of the community</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Installing more software</a></h2>
<p>Most of the available software can be downloaded and installed with the application HaikuDepot that comes with Haiku.<br />
<p>Most of the available software can be downloaded and installed with the application <a href="../userguide/pt_PT/applications/haikudepot.html">HaikuDepot</a> that comes with Haiku.<br />
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/pt_PT/applications.html">Applications</a>.</p>
<p>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>
@@ -105,7 +105,7 @@ Because of our binary and source compatibility, most BeOS applications run on Ha
<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/pt_PT/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>
For more details, see the guide <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Updating and downgrading your system</a> on our website.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
docs/welcome/welcome_ro.html
+4 -4
View File
@@ -94,21 +94,21 @@
<p>Prima versiune(i) ale Haiku vor fi foarte asemănătoare cu BeOS R5, sistemul de operare pe care îl reimplementează. Dacă nu l-ați experimentat niciodată, uitați-vă la aceste resurse:</p>
<ul>
<li><a href="../userguide/ro/contents.html">Ghid de utilizare Haiku</a></li>
<li><a href="http://www.haiku-os.org/community/" class="printurl">Listă site-uri BeOS/Haiku</a></li>
<li><a href="https://www.haiku-os.org/community/" class="printurl">Get help and support and become a part of the community</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Instalarea de software nou</a></h2>
<p>Majoritatea aplicațiilor software disponibile pot fi descărcate și instalate cu aplicația HaikuDepot care vine cu Haiku.<br />
Datorită compatibilității binarului și sursei, majoritatea aplicațiilor BeOS rulează pe Haiku. Multe dintre ele au fost reîmpachetate pentru Haiku și încă rulează nemodificate. Veți găsi mai multe informații pentru instalarea de programe noi în capitolul ghidului de utilizator despre <a href="../userguide/ro/applications.html">Applications</a>.</p>
<p>Most of the available software can be downloaded and installed with the application <a href="../userguide/ro/applications/haikudepot.html">HaikuDepot</a> that comes with Haiku.<br />
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/ro/applications.html">Applications</a>.</p>
<p>Există mai multe colecții de software create de comunitate. Vedeți <a href="https://www.haiku-os.org/community/software">Site-uri Software </a> pe pagina noastră web.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="update" name="update">Actualizarea Haiku</a></h2>
<p>Updating Haiku as well as third party packages is done with the application <a href="../userguide/ro/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>
For more details, see the guide <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Updating and downgrading your system</a> on our website.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
docs/welcome/welcome_ru.html
+3 -3
View File
@@ -96,13 +96,13 @@
<p>Первые релизы Haiku будут похожи по функционалу и вешнему виду на BeOS R5, которую она и призвана повторить. Если вы никогда не пользовались этой операционной системой, то рекомендуется воспользоваться следующими ссылками:</p>
<ul>
<li><a href="../userguide/ru/contents.html">Руководство пользователя 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">Get help and support and become a part of the community</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Установка дополнительных программ</a></h2>
<p>Most of the available software can be downloaded and installed with the application HaikuDepot that comes with Haiku.<br />
<p>Most of the available software can be downloaded and installed with the application <a href="../userguide/ru/applications/haikudepot.html">HaikuDepot</a> that comes with Haiku.<br />
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/ru/applications.html">Applications</a>.</p>
<p>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>
@@ -110,7 +110,7 @@ Because of our binary and source compatibility, most BeOS applications run on Ha
<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/ru/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>
For more details, see the guide <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Updating and downgrading your system</a> on our website.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
docs/welcome/welcome_sk.html
+5 -5
View File
@@ -93,21 +93,21 @@
<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">Zoznam webov o BeOS/Haiku</a></li>
<li><a href="https://www.haiku-os.org/community/" class="printurl">Get help and support and become a part of the community</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Inštalovanie ďalšieho softvéru</a></h2>
<p>Väčšinu dostupného softvéru je možné stiahnuť a nainštalovať pomocou aplikácie HaikuDepot, ktorá sa dodáva spolu s Haiku.<br />
Vďaka tomu, že Haiku je kompatibilné s BeOS na binárnej úrovni aj na úrovni zdrojového kódu, mnohé aplikácie pre BeOS bežia na Haiku. Pre mnohé z nich boli vytvorené balíky pre Haiku alebo jednoducho bežia nezmenené. Ďalšie informácie o inštalovaní nových programov nájdete v Používateľskej príručke v kapitole <a href="../userguide/sk/applications.html">Aplikácie</a>.</p>
<p>Most of the available software can be downloaded and installed with the application <a href="../userguide/sk/applications/haikudepot.html">HaikuDepot</a> that comes with Haiku.<br />
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/sk/applications.html">Applications</a>.</p>
<p>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">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>
<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 and downgrading your system</a> on our website.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
docs/welcome/welcome_sv_SE.html
+3 -3
View File
@@ -94,13 +94,13 @@
<p>Dom första utgåvorna av Haiku kommer att vara väldigt lik BeOS R5, operativsystemet som vi omimplementerar. Om du aldrig har upplevt det, ta då en titt på följande länkar:</p>
<ul>
<li><a href="../userguide/sv_SE/contents.html">Haiku's Användarhandbok</a></li>
<li><a href="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">Get help and support and become a part of the community</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Installera ytterligare programvara</a></h2>
<p>Most of the available software can be downloaded and installed with the application HaikuDepot that comes with Haiku.<br />
<p>Most of the available software can be downloaded and installed with the application <a href="../userguide/sv_SE/applications/haikudepot.html">HaikuDepot</a> that comes with Haiku.<br />
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/sv_SE/applications.html">Applications</a>.</p>
<p>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>
@@ -108,7 +108,7 @@ Because of our binary and source compatibility, most BeOS applications run on Ha
<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/sv_SE/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>
For more details, see the guide <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Updating and downgrading your system</a> on our website.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
docs/welcome/welcome_uk.html
+4 -4
View File
@@ -95,21 +95,21 @@
<p>Перші релізи Haiku будуть схожі по функціоналу і зовнішньому вигляду на BeOS R5, яку ми і намагалися відтворити. Якщо Ви ніколи нею не користувались варто скористатись такими посиланнями:</p>
<ul>
<li><a href="../userguide/uk/contents.html"> Настанова користувачеві Haiku</a></li>
<li><a href="http://www.haiku-os.org/community/" class="printurl">Список BeOS/Haiku вебсайтів</a></li>
<li><a href="https://www.haiku-os.org/community/" class="printurl">Get help and support and become a part of the community</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Встановлення додаткових програм</a></h2>
<p>Велика частина доступного програмного забезпечення може бути завантажена та встановлена додатком Сховище Haiku (HaikuDepot), який іде разом з Haiku.<br />
Завдяки бінарній та кодовій сумісності, більшість програм BeOS працюватиме на Haiku. Багато з них або були перепаковані під Haiku або надалі працюють без змін. Ви знайдете більш детальну інформацію про встановлення нових програм у розділі Настанови користувачеві <a href="../userguide/uk/applications.html"> Додатки</a>.</p>
<p>Most of the available software can be downloaded and installed with the application <a href="../userguide/uk/applications/haikudepot.html">HaikuDepot</a> that comes with Haiku.<br />
Because of our binary and source compatibility, most BeOS applications run on Haiku. Many of those have been re-packaged for Haiku or still run unmodified. You'll find more information on installing new programs in the user guide's chapter on <a href="../userguide/uk/applications.html">Applications</a>.</p>
<p>Існує декілька колекцій програмного забезпечення створених товариством. Дивись сторінку <a href="https://www.haiku-os.org/community/software">Сайти програмного забезпечення (Software Sites)</a> на нашому вебсайті.</p>
<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/uk/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>
For more details, see the guide <a href="https://www.haiku-os.org/guides/daily-tasks/updating-system">Updating and downgrading your system</a> on our website.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
docs/welcome/welcome_zh_CN.html
+11 -11
View File
@@ -57,7 +57,6 @@
<div id="content">
<div>
<div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>索引</td></tr>
@@ -74,16 +73,16 @@
<h2>
<a id="welcome" name="welcome">欢迎使用Haiku！</a></h2>
<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>非常感谢试用 Haiku 操作系统！这是我们发布的第五个公开版本，我们希望能吸引新开发者加入我们的项目，并让未来的 Haiku 用户有机会了解 Haiku 的开发情况。我们深知，现在这个<i>beta 版本</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>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>我们一直在努力修复软件中所有可能出现的严重缺陷，但是，作为 beta 版本，当中一定会有许多未知问题。</p>
<div class="box-warning">我们不建议您将 beta 版本作为生产系统，在这种情况下，您的数据可能遭到改变，损坏甚至完全破坏。清及时进行备份。</div>
<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>
<p>发布该 beta 版本的主要原因之一，是为了吸引更多的用户来测试系统、发现问题，提供建议用于未来改进。在使用我们的错误跟踪系统提交错误或改进建议之前，请使用查询功能以避免重复提交。</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>
@@ -95,20 +94,21 @@
<p>Haiku 第一个系列的版本将会非常类似于BeOS R5，也就是 Haiku 要复刻的操作系统。如果您从未尝试过该系统，可参阅以下链接：</p>
<ul>
<li><a href="../userguide/zh_CN/contents.html">Haiku 用户指南</a></li>
<li><a href="http://www.haiku-os.org/community/" class="printurl"> BeOS/Haiku 相关网站清单</a></li>
<li><a href="https://www.haiku-os.org/community/" class="printurl"> 获取帮助支持和加入社区</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">安装更多程序</a></h2>
<p>大多数程序都可以通过 Haiku 内置的 HaikuDepot 程序进行下载安装。<br />由于二进制库和源代码的兼容性，大部分 BeOS 程序都可以在 Haiku 系统上运行其中，许多软件已经为 Haiku 进行了重新的打包，或可以在没有变动的情况下运行。您可以在用户指南的 <a href="../userguide/zh_CN/applications.html">应用程序</a> 一节中找到更多有关安装新程序的相关信息。</p>
<p>大多数程序都可以通过 Haiku 内置的 <a href="../userguide/zh_CN/applications/haikudepot.html">HaikuDepot</a> 程序进行下载安装。<br />
由于二进制库和源代码的兼容性，大部分 BeOS 程序都可以在 Haiku 系统上运行，其中许多软件已经为 Haiku 进行了重新的打包，或可以在没有变动的情况下运行。您可以在用户指南的 <a href="../userguide/zh_CN/applications.html">应用程序</a> 一节中找到更多有关安装新程序的相关信息。</p>
<p>一些社区维护的软件网站也可以提供软件下载。参见本站的<a href="https://www.haiku-os.org/community/software">软件网站</a>页面以进行了解。</p>
<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>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>
更多信息，查看官网指南 <a href="https://www.haiku-os.org/guides/daily-tasks/updating-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="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.freelists.org/list/haiku" 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>
docs/welcome/zh_CN/bugreports.html
+3 -3
View File
@@ -126,7 +126,7 @@ Depending on what exactly crashed, you can try to save a crash report on the Des
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 <span class="cli">sc</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> (aka continue)</td><td> </td><td>离开内核调试状态；如果可能的话，继续正常的系统操作。</td></tr>
<tr><td><span class="cli">reboot</span></td><td> </td><td>立即重启系统。您将会丢失所有未保存的数据，甚至包括那些已经保存，但是还未写入硬盘的数据。</td></tr>
@@ -158,10 +158,10 @@ Note that in KDL your keyboard may not work. PS/2 keyboards always do, with USB
<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>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>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Haiku的主要系统日志，查看上述 <a href="#syslog">Syslog</a>，类似于引导过程中的屏幕调试信息。您可以使用 <span class="cli">open</span> 命令在文本编辑器中获取到系统日志中相关的部分。</td></tr>
<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td> 列出所有使用的驱动。</td></tr>
<tr><td>- <span class="cli">ints</span></td><td> </td><td>只在 <i>内核调试状态</i> 可用（参阅下文）。它用显示中断使用情况。不可能有许多由不同硬件共享的中断。</td></tr>
<tr><td colspan="3">- On screen debug output (a safe mode boot time option, see <a href="#onscreen">above</a>).</td></tr>
<tr><td colspan="3">- 屏幕调试输出（一种安全模式引导时间选项，查看 <a href="#onscreen">上述</a>）。</td></tr>
</table>
<p>前四个命令需要在终端中进行输入。在命令后添加 <span class="cli"> &gt; output.txt</span> ，然后输出的信息将会重定向到“output.txt”文本文件，您可以将其附带到您的错误报告或者邮件。</p>
docs/welcome/zh_CN/wifi.html
-164
View File
@@ -1,164 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!--
*
* Copyright 2010-2011, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
* Humdinger <humdingerb@gmail.com>
* Translators:
* Pengphei Han
* dgy18787
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="robots" content="all" />
<title>无线网络</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>用户指南</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/zh_CN.png" alt="" />  中文 ［中文］</li>
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</a></li>
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
<a href="../welcome_zh_CN.html" class="uplink">Welcome</a>
</span></div>
</div>
<div id="content">
<div>
<h2>Haiku中的无线网络</h2>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="hardware" rel="nofollow" id="hardware">预期的硬件支持</a></h3>
<p>FreeBSD 8的所有无线驱动都应该可以工作。但是任何的PCMCIA，CardBus，ExpressCard，USB或者基于ISA的网卡将无法工作。只有PCI，miniPCI，PCI-Express，miniPci-Express 和 PCI-X 才应该可以工作。<br />
包括以下：
</p>
<ul>
<li><p><i>aironetwifi</i> 至少支持：<br />
Cisco Aironet 350 Series<br />
Aironet PCI4500<br />
Aironet PCI4800<br />
</p></li>
<li><p><i>atheroswifi</i>支持几乎所有的芯片集(但是除了 AR9285 芯片)</p></li>
<li><p><i>broadcom43xx</i> 支持：<br />
BCM4301，BCM4306，BCM4307，BCM4309，BCM4311，BCM4312和 BCM4318
</p></li>
<li><p><i>iprowifi2100</i> 支持英特尔专业无线 2100 芯片</p></li>
<li><p><i>iprowifi2200</i> 支持英特尔无线卡：<br />
2200BG<br />
2225BG<br />
2915ABG
</p></li>
<li><p><i>iprowifi3945</i> 支持英特尔 3945 专业无线芯片</p></li>
<li><p><i>iprowifi4965</i>支持英特尔 4965 专业无线芯片</p></li>
<li><p><i>marvell88w8335</i> 支持：
<br />
Marvell Libertas 88W8310<br />
Marvell Libertas 88W8335
</p></li>
<li><p><i>marvell88w8363</i> 支持 88W8363 芯片</p></li>
<li><p><i>ralinkwifi</i> 支持：
<br />
RT2560<br />
RT2561S<br />
RT2561<br />
RT2661
</p></li>
<li><p>ralink2860 支持 Ralink RT2860</p></li>
<li><p><i>wavelanwifi</i> 目前支持：
<br />
3Com Airconnect<br />
GLPRISM2 WaveLAN<br />
Intersil Prism3<br />
Intersil Prism2.5<br />
Linksys WDT11<br />
Netgear MA301<br />
PRISM2STA WaveLAN<br />
Siemens SpeedStream<br />
SMC 2602W<br />
Us Robotics 2415<br />
Addtron AWA-100 PCI
</p></li>
</ul>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="connect" rel="nofollow" id="connect">连接到无线网络</a></h3>
<p>除了未加密网络，Haiku 还初步支持通过<a href="#wep-notes" rel="nofollow">WEP 密钥</a> 访问无线网络。WEP 是早期的加密方法，尽管不是最安全的。</p>
<p>你可以通过在终端中输入 <span class="cli">ifconfig</span> 列出可用网络，并且加入或者断开连接。</p>
<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
<p>您可以在 <span class="app">Network</span> 首选项或通过 <span class="cli">ifconfig -a</span> 命令找到你的 <tt>wifi_device_path</tt>。</p>
<p>下述是一些连接到 <i>wifitopia</i> 无线网络的示例。在这些示例中，我们假定您的无线网卡为 <tt>/dev/net/iprowifi3945/0</tt>。</p>
<h4>列出无线网络：</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
<h4>加入不安全的无线网络：</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
<h4>加入 <a href="#wep-notes">WEP 加密</a> 无线网络：（ascii 密码）</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
<h4>加入 <a href="#wep-notes">WEP 加密</a> 无线网络：（64位十六进制密码）</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
<h4>断开无线网络：</h4>
<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="auto-connect" rel="nofollow" id="auto-connect">自动连接无线网络</a></h3>
<p>为了使系统在每次启动时自动连接到一个给定 SSID 的网络，您可以按照下述格式在<tt>/boot/common/settings/network/wireless_networks</tt> 中指定无线网络和密码：</p>
<pre>network wifitopia {
   password mypassword
}</pre>
<p>如果您并未创建该配置文件，系统将会自动连接到其发现的首个未加密网络。</p>
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP 备注</strong></a></p>
<ul>
<li>64位的WEP使用了40位的密钥，也就是5个文本字符或者10个十六进制数字。</li>
<li>128位的WEP是引用了104位密钥，也就是13个文本字符或者26个十六进制数字。</li>
<li>十六进制位数字 = 0-9 和 A-F 十六个字符（在 <tt>ifconfig</tt> 中都带有前缀 "0x"）。</li>
</ul>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="wpa" rel="nofollow" id="wpa">WPA加密</a></h3>
<p><p>现在，Haiku 中还未有可用的 WPA 加密，尽管有一些 <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">成果</a> 已经带来了深远的影响。</p></p>
<h3>
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
<p>为了安装用于 Intel ipw2100，Intel ipw2200/2225/2915，Broadcom 43xx 和 Marvell 88W8335 等的固件，您需要运行</p>
<pre class="terminal">install-wifi-firmwares.sh
</pre>
<p>Intel ipw2100 和 ipw22xx 无需网络连接也可以进行安装，这是因为它们的许可条款允许 Haiku 发行原始的固件档案。但是在安装之前，它们确实需要用户的确认。Broadcom 43xx 和 Marvell 88W8335 需要活动的网络连接，这是因为包含固件的文件不能够随着 Haiku 一同发布。</p>
<p>构建自己的Haiku镜像的人们可以在 <span class="cli">build/jam/UserBuildConfig</span> 中进行相应的改动。更多详细信息和关于无线网络的主题更新可以参阅 <a href="http://www.haiku-os.org/guides/wifi">有关的在线文档</a>。</p>
<p>如果您确实需要下载该固件，而且在 Haiku 下也没有可用的网络连接，在线文档提供了一个<a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">shell 脚本</a>，它将会为你创建用于解压到 Haiku 的 <tt>/boot</tt> 文件夹下的Zip文件。之后，您就具有了所有 install-wifi-firmwares.sh 所需要的所有文件。</p>
</div>
</div>
<div class="nav">
<div class="inner"><span>
<a href="../welcome_zh_CN.html" class="uplink">Welcome</a>
</span></div>
</div>
</body>
</html>