WEP Verschlüsselung ist durch das Kommandozeilen-Programm setwep verfügbar. Es ist ein Provisorium, um sich in ein nicht oder per WEP verschlüsseltes Netzwerk einzuklinken. setwep funktioniert mit 64- und 128-bit WEP und unterstützt Passwörter als Text und Hex-Werte (siehe WEP Info weiter unten).
-
Der Gebrauch ist: setwep Geräte_Pfad [ssid] [key]. Nachfolgend einige Beispiele.
-
In diesen Beispielen gehen wir von einer Netzwerkkarte "/dev/net/iprowifi3945/0" und einem Funknetzwerk mit dem Namen "haikuwifi" aus.
+
Der Gebrauch ist: setwep Geräte_Pfad [ssid] [key].
+
In nachfolgenden Beispielen gehen wir von einer Netzwerkkarte "/dev/net/iprowifi3945/0" und einem Funknetzwerk mit dem Namen "haikuwifi" aus.
Beispiel 1: Verbindung mit einer 64-bit WEP Verschlüsselung und einem Hex-Passwort
WEP encryption is available through a command-line application setwep. It is a temporary means for joining an unencrypted or WEP encrypted wifi network. setwep works with 64- and 128-bit WEP and supports both text keys as well as hex digit keys (see WEP notes below)
+
WEP encryption is available through a command-line application setwep. It is a temporary means for joining an unencrypted or WEP encrypted wifi network. setwep works with 64- and 128-bit WEP and supports both text keys as well as hex digit keys (see WEP notes below).
-
The usage is: setwep device_path [ssid] [key]. Below are some examples.
-
In this example, let us assume your wifi network card is "/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".
+
The usage is: setwep device_path [ssid] [key]
+
Below are two examples. Let us assume your wifi network card is "/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".
Example 1: Connect with 64-bit WEP encryption using a hex digit key
To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you'll need to run
-
~> install-wifi-firmwares.sh
+
To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you need to run
+
install-wifi-firmwares.sh
The Intel ipw2100 and ipw22xx 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.
People building their own Haiku image can modify their build/jam/UserBuildConfig accordingly. Details for that and general updates on the wifi topic are found at the online version of this document.
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.
-This includes:
+
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.
+Esto incluye a:
-
aironetwifi supporting at least
-Cisco Aironet 350 Series
-Aironet PCI4500
-Aironet PCI4800
+
aironetwifi soportando al menos:
+Aironet PCI4500 y
+Aironet PCI4800.
-
atheroswifi supporting almost every chipset outthere (though no AR9285 chips)
WEP encryption is available through a command-line application setwep. It is a temporary means for joining an unencrypted or WEP encrypted wifi network. setwep works with 64- and 128-bit WEP and supports both text keys as well as hex digit keys (see WEP notes below)
-
-
The usage is: setwep device_path [ssid] [key]. Below are some examples.
-
In this example, let us assume your wifi network card is "/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".
-
Example 1: Connect with 64-bit WEP encryption using a hex digit key
Está disponible la encripción WEP mediante una aplicación de comando de línea setwep. Es una manera temporal para unirse a una red Wifi sin encriptar o con encripción WEP. setwep trabaja con WEP 64- y 128-bit y soporta tanto claves de texto
+WEP como claves de dígito hexadecimal (vea las (see notas WEP debajo).
+
La forma de uso es: setwep device_path [ssid] [key]
+
Debajo hay dos ejemplos. Asumamos que la tarjeta Wifi en su sistema está en "/dev/net/iprowifi3945/0" y la red inalámbrica se llama "haikuwifi".
+
Ejemplo 1: Conectarse con encripción WEP 64-bit usando una clave de dígitos hexadecimales
Ejemplo 2: Conectarse a una red inalámbrica sin encripción
setwep /dev/net/iprowifi3945/0 haikuwifi
-
-
To find out what your device_path is, have a look in Preferences -> Network.
-
To make your wifi device connect to a given SSID at each boot, add the setwep command to your home/config/boot/UserBootscript.
+
Para averiguar qué device_path tiene su dispositivo, dé un vistazo en Preferencias -> Red
+
Para hacer que su dispositivo Wifi se conecte a un SSID dado en cada inicio del sistema, agregue el comando setwep command a su home/config/boot/UserBootscript
At the moment there is no WPA encryption available in Haiku. However, there is some preliminary and unfinished code for implementing WPA available. Some tasks for improving this is to plug it into the wpa_supplicant build process and then fixing compile & runtime issues.
Al momento no hay encripción WPA disponible en Haiku. Sin embargo hay algo de código preliminar y sin terminar pra implementar WPA disponible. Algunas tareas para mejorar esto es conectarse en el build del proceso del wpa_supplicant build y luego arreglar los problemas de compilación y los problemas en tiempo de ejecución.
To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you'll need to run
-
~> install-wifi-firmwares.sh
-
-
The Intel ipw2100 and ipw22xx 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.
-
People building their own Haiku image can modify their build/jam/UserBuildConfig accordingly. Details for that and general updates on the wifi topic are found at the online version of this document.
-
If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a shell script, which will create a zip file for you to extract to Haiku's /boot. After that you'll have all files needed by install-wifi-firmwares.sh.
+
Para instalar el firmware para las Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx y Marvell 88W8335, se necesita correr
+
install-wifi-firmwares.sh
+
Las tarjetas Intel ipw2100 y ipw22xx se instalarán sin conexión a Internet, pues los términos de la licencia permiten a Haiku distribuir los archivos de firmware originales. No obstante, requieren cierto acuerdo por el usuario final previo a la instalación. Las tarjetas Broadcom 43xx y Marvell 88W8335 requerirán una conexión a Internet activa, pues los archivos que contienen los respectivos firmwares no pueden redistribuirse con Haiku.
+
La gente que hace su propio build de la imagen de Haiku puede modificar su build/jam/UserBuildConfig en conformidad. Los detalles para ello y actualizaciones generales del tema de Wifi se encuentran en la versión en línea de este documento.
+
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 script de shell, el cual creará un archivo zip para que se extraiga en la carpeta /boot de Haiku. Después de ello tendrá todos los archivos necesarios por install-wifi-firmwares.sh.
@@ -54,12 +57,12 @@
Lors de la création d’un nouveau compte, pensez à indiquer votre adresse e-mail afin d’obtenir les privilèges basiques de gestions des tickets. N’oubliez pas de Vérifier votre dossier de pourriel après, car les e-mails de vérifications s’y retrouvent souvent.
Créer un rapport de bogue
-
Avant de rapporter un bogue, veuillez vérifierqu’il n’est pas déjà répertorié. Vous pouvez aussi utiliser la fonction de recherche pour cela.
-Après vous être assurer que votre bogue est unique, obtenez des informations précises sur votre environnement :
+
Avant de rapporter un bogue, veuillez vérifier qu’il n’est pas déjà répertorié. Vous pouvez aussi utiliser la fonction de recherche pour cela.
+Après vous être assuré que votre bogue est unique, obtenez des informations précises sur votre environnement :
Indiquez comment vous testez Haiku (sur machine réelle, dans VMware, dans Qemu…)
Indiquez quelle révision SVN de Haiku vous utilisez. Vous pouvez trouver des informations à ce sujet dans le menu « About This System… » de la Deskbar.
-
Décrire le problème que vous rencontrez. Essayez d'être aussi précis que possible : décrivez le comportement réel, et celui que vous attendiez.
+
Décrivez le problème que vous rencontrez. soyez aussi précis que possible : décrivez le comportement réel, et celui que vous attendiez.
Décrivez les actions que vous avez effectuées avant de faire ressortir le bogue. Cela permettra aux développeurs de le reproduire.
Attachez au rapport le plus d’informations possibles. Si le bogue concerne l’interface graphique ou une application, essayez de faire une capture d’écran (la touche IMPR ÉCRAN créera une image PNG dans le dossier /boot/home/).
@@ -90,7 +93,7 @@ Il ne devrait pas y avoir trop d'interruptions partagées par plusieurs périph
Et après ?
Une fois le bogue rapporté, un développeur le consultera et essayera de le cataloguer. Retenez que tous les développeurs sont des volontaires; un long délai avant réponse peut s’écouler après le rapport de bogue. L’ajout de nouvelles informations une fois celles-ci disponibles peut généralement permettre à un bogue d’être analysé plus rapidement. Néanmoins, n’essayez pas de « faire remonter » un bogue en ajoutant des commentaires non pertinents.
-
N’oubliez pas, le rapport d’un bogue ne se limite pas à sa soumission. Une fois cette tâche faite, vous ferez partie du processus de développement de Haiku. Les développeurs pourront vous poser des question pour essayer de résoudre votre bogue. Merci de rester disponible pour y répondre. Considérez votre travail « terminé » quand le bogue sera marqué comme étant « corrigé ».
+
N’oubliez pas, le rapport d’un bogue ne se limite pas à sa soumission. Une fois cette tâche faite, vous ferez partie du processus de développement de Haiku. Les développeurs pourront vous poser des question pour essayer de résoudre votre bogue. Merci de rester disponible pour y répondre. Vous pourrez considérer votre travail « terminé » quand le bogue sera marqué comme étant « corrigé ».
diff --git a/welcome/fr/wifi.html b/welcome/fr/wifi.html
index abf91fc3..e44485ca 100644
--- a/welcome/fr/wifi.html
+++ b/welcome/fr/wifi.html
@@ -10,6 +10,9 @@
* Authors:
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
* Humdinger
+ * Translators:
+ * Loïc
+ * Vincent Duvert
*
-->
@@ -21,7 +24,7 @@
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.
-This includes:
-
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.
+Cela inclut :
-
aironetwifi supporting at least
+
Le module aironetwifi, qui supporte au minimum les cartes :
Cisco Aironet 350 Series
Aironet PCI4500
Aironet PCI4800
-
atheroswifi supporting almost every chipset outthere (though no AR9285 chips)
Le module atheroswifi, qui supporte la plupart des puces Atheros (à l'exception de la puce AR9285)
+
Le module broadcom43xx qui supporte les cartes :
+BCM4301
+BCM4306
+BCM4307
+BCM4309
+BCM4311
+BCM4312
+BCM4318
+
Le module iprowifi2100 qui supporte les puces Intel Pro Wifi 2100
+
Module iprowifi2200 qui supporte les cartes :
2200BG
2225BG
2915ABG
-
iprowifi3945 supporting the 3945 chips
-
iprowifi4965 supporting the 4965 chips
-
marvell88w8335 supporting
+
Module iprowifi3945 qui supporte les puces 3945 d’Intel
+
Module iprowifi4965 qui supporte les puces 4965 d’Intel
+
Module marvell88w8335 qui supporte les cartes :
Marvell Libertas 88W8310
Marvell Libertas 88W8335
-
marvell88w8363 supporting the 88W8363 chips
-
ralinkwifi supporting
+
Module marvell88w8363 qui supporte les puces Marvell 88W8363
+
Le module ralinkwifi qui supporte les cartes :
RT2560
RT2561S
RT2561
RT2661
-
wavelanwifi supporting at least
+
Le module wavelanwifi qui supporte au moins les cartes suivantes :
3Com Airconnect
GLPRISM2 WaveLAN
Intersil Prism3
@@ -95,38 +105,39 @@ Addtron AWA-100 PCI
WEP encryption is available through a command-line application setwep. It is a temporary means for joining an unencrypted or WEP encrypted wifi network. setwep works with 64- and 128-bit WEP and supports both text keys as well as hex digit keys (see WEP notes below)
-
-
The usage is: setwep device_path [ssid] [key]. Below are some examples.
-
In this example, let us assume your wifi network card is "/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".
-
Example 1: Connect with 64-bit WEP encryption using a hex digit key
Le protocole de sécurité WEP est disponible au travers de l'application en ligne de commande setwep.
+Il s’agit une solution temporaire pour accéder à un réseau Wifi non protégé ou en codage WEP. setwep
+supporte les clés WEP 64 et 128 bits, indiquées sous forme hexadécimale ou texte. (voir les remarques concernant le WEP ci-dessous).
+
L'usage est le suivant : setwep chemin_de_périphérique [ssid] [clé] ([ssid] est le nom du réseau à rejoindre)
+
Voici deux exemples pour lesquels nous supposerons que votre carte réseau wifi est «/dev/net/iprowifi3945/0» et que le réseau sans fil est nommé «haikuwifi».
+
Exemple 1 : Se connecter avec un cryptage WEP 64 bits et une clé numérique hexadécimale
Pour connaître le chemin_du_périphérique, regardez dans les préférences réseau (Preferences -> Network)
+
Pour connecter votre adaptateur Wifi à un réseau de SSID donné à chaque démarrage, ajoutez la commande setwep a votre script home/config/boot/UserBootscript
64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex digits
-
128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex digits
-
hexadecimal digits = characters 0-9 and A through F (prepended with '0x')
+
Le WEP « 64 bits » utilise une clé de 40 bits, c’est à dire 5 caractères alphanumériques ou 10 chiffres hexadécimaux.
+
Le WEP « 128 bits » utilise une clé de 104 bits, c’est à dire 13 caractères alphanumériques ou 26 chiffres hexadécimaux.
+
Un chiffre hexadécimal est un chiffre de 0 à 9 ou une lettre de 0 à F. Un nombre hexadécimal doit être précédé de « 0x » lorsqu’il est utilisé dans setwep.
At the moment there is no WPA encryption available in Haiku. However, there is some preliminary and unfinished code for implementing WPA available. Some tasks for improving this is to plug it into the wpa_supplicant build process and then fixing compile & runtime issues.
Pour le moment, le codage WPA n'est pas disponible dans Haiku. Cependant, il existe une ébauche de code pour la mise en œuvre de cette sécurité.
+Il reste notamment à intégrer le processus de construction du gestionnaire wpa_supplicant et à corriger des problèmes de compilation et d’exécution.
To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you'll need to run
-
~> install-wifi-firmwares.sh
+
Pour installer le micro-logiciel des cartes Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx et Marvell 88W8335 vous devez exécuter la commande
+
install-wifi-firmwares.sh
-
The Intel ipw2100 and ipw22xx 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.
-
People building their own Haiku image can modify their build/jam/UserBuildConfig accordingly. Details for that and general updates on the wifi topic are found at the online version of this document.
-
If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a shell script, which will create a zip file for you to extract to Haiku's /boot. After that you'll have all files needed by install-wifi-firmwares.sh.
+
Les pilotes Intel ipw2100 et ipw22xx 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.
+
Si vous compilez vous-même Haiku, vous pouvez modifier votre fichier build/jam/UserBuildConfig afin de pouvoir utiliser cet outil. Vous pourrez trouver plus de détails sur le Wifi dans Haiku sur la version en ligne de ce document (en anglais).
+
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 script de commande, qui crée un fichier zip à extraire dans le dossier /boot de Haiku. Après cela, vous aurez tous les fichiers nécessaires pour install-wifi-firmwares.sh.
diff --git a/welcome/images/flags/it.png b/welcome/images/flags/it.png
new file mode 100644
index 00000000..e288f40b
Binary files /dev/null and b/welcome/images/flags/it.png differ
diff --git a/welcome/images/flags/jp.png b/welcome/images/flags/jp.png
new file mode 100644
index 00000000..aaf58327
Binary files /dev/null and b/welcome/images/flags/jp.png differ
diff --git a/welcome/images/flags/sv_SE.png b/welcome/images/flags/sv_SE.png
new file mode 100644
index 00000000..126a2503
Binary files /dev/null and b/welcome/images/flags/sv_SE.png differ
diff --git a/welcome/it/bugreports.html b/welcome/it/bugreports.html
new file mode 100644
index 00000000..c3055927
--- /dev/null
+++ b/welcome/it/bugreports.html
@@ -0,0 +1,106 @@
+
+
+
+
+
+
+
+ Reporting bugs
+
+
+
+
+
The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
+
+
Reporting bugs
+
+
Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.
+
To keep our bugtracker effective, it's essential to abide by the Bug Tracker Etiquette.
+
+
Getting a Trac account
+
To file a ticket, you need to have an account at Haiku's Bugtracker.
+When creating a new account, be certain to provide your email address as it is necessary to obtain basic ticket modification privileges. Be sure to check your spam folder shortly afterwards, as the all important verification mail often ends up there.
+
+
Creating a bug report
+
Before reporting a bug, please make sure that it does not yet exist. You can also use the search function for this.
+After you have established that it's a unique bug, make your information as accurate as possible:
+
+
Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).
+
Mention which revision from SVN you are running. You can find this information in 'About This System...' from the Deskbar menu.
+
Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.
+
Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.
+
Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot (the PRINT key saves a PNG in /boot/home/).
+
+
+
Software Bugs
+
When an application crashed, you should invoke the debugger from the alert that pops up. Entering bt into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.
+
+
Hardware Bugs
+
When dealing with a hardware/driver related bug, you should attach the following information:
+
+
listdev - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' lshw and lspci.
+
listusb -v - assuming its a USB related issue, similar to lsusb.
+
open /var/log/syslog - the primary system log used by Haiku, akin to on screen debugging during boot. With the open command you can crop down the relevant part of the syslog in a text editor.
+
listimage | grep drivers/ - lists all used drivers.
+
ints - only available within Kernel Debugging Land (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.
+
+
You enter these commands into Terminal. Add a > output.txt after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.
+
+
Kernel Debugging Land - KDL
+
When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with ALTSysReqD (SysReq being PRINT on most keyboards).
+
+
co - will exit KDL and continue normal system operation, if possible.
+
int - will show interrupt usage (as described above).
+
bt - shows a backtrace, detailing where exactly the crash happened.
+
+
+
What's next?
+
After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
+non-descriptive comments.
+
Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
+as 'fixed'.
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.
+This includes:
+
+
+
aironetwifi supporting at least
+Cisco Aironet 350 Series
+Aironet PCI4500
+Aironet PCI4800
+
+
atheroswifi supporting almost every chipset outthere (though no AR9285 chips)
WEP encryption is available through a command-line application setwep. It is a temporary means for joining an unencrypted or WEP encrypted wifi network. setwep works with 64- and 128-bit WEP and supports both text keys as well as hex digit keys (see WEP notes below).
+
+
The usage is: setwep device_path [ssid] [key]
+
Below are two examples. Let us assume your wifi network card is "/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".
+
Example 1: Connect with 64-bit WEP encryption using a hex digit key
At the moment there is no WPA encryption available in Haiku. However, there is some preliminary and unfinished code for implementing WPA available. Some tasks for improving this is to plug it into the wpa_supplicant build process and then fixing compile & runtime issues.
To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you need to run
+
install-wifi-firmwares.sh
+
+
The Intel ipw2100 and ipw22xx 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.
+
People building their own Haiku image can modify their build/jam/UserBuildConfig accordingly. Details for that and general updates on the wifi topic are found at the online version of this document.
+
If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a shell script, which will create a zip file for you to extract to Haiku's /boot. After that you'll have all files needed by install-wifi-firmwares.sh.
The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
+
+
Reporting bugs
+
+
Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.
+
To keep our bugtracker effective, it's essential to abide by the Bug Tracker Etiquette.
+
+
Getting a Trac account
+
To file a ticket, you need to have an account at Haiku's Bugtracker.
+When creating a new account, be certain to provide your email address as it is necessary to obtain basic ticket modification privileges. Be sure to check your spam folder shortly afterwards, as the all important verification mail often ends up there.
+
+
Creating a bug report
+
Before reporting a bug, please make sure that it does not yet exist. You can also use the search function for this.
+After you have established that it's a unique bug, make your information as accurate as possible:
+
+
Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).
+
Mention which revision from SVN you are running. You can find this information in 'About This System...' from the Deskbar menu.
+
Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.
+
Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.
+
Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot (the PRINT key saves a PNG in /boot/home/).
+
+
+
Software Bugs
+
When an application crashed, you should invoke the debugger from the alert that pops up. Entering bt into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.
+
+
Hardware Bugs
+
When dealing with a hardware/driver related bug, you should attach the following information:
+
+
listdev - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' lshw and lspci.
+
listusb -v - assuming its a USB related issue, similar to lsusb.
+
open /var/log/syslog - the primary system log used by Haiku, akin to on screen debugging during boot. With the open command you can crop down the relevant part of the syslog in a text editor.
+
listimage | grep drivers/ - lists all used drivers.
+
ints - only available within Kernel Debugging Land (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.
+
+
You enter these commands into Terminal. Add a > output.txt after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.
+
+
Kernel Debugging Land - KDL
+
When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with ALTSysReqD (SysReq being PRINT on most keyboards).
+
+
co - will exit KDL and continue normal system operation, if possible.
+
int - will show interrupt usage (as described above).
+
bt - shows a backtrace, detailing where exactly the crash happened.
+
+
+
What's next?
+
After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
+non-descriptive comments.
+
Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
+as 'fixed'.
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.
+This includes:
+
+
+
aironetwifi supporting at least
+Cisco Aironet 350 Series
+Aironet PCI4500
+Aironet PCI4800
+
+
atheroswifi supporting almost every chipset outthere (though no AR9285 chips)
WEP encryption is available through a command-line application setwep. It is a temporary means for joining an unencrypted or WEP encrypted wifi network. setwep works with 64- and 128-bit WEP and supports both text keys as well as hex digit keys (see WEP notes below).
+
+
The usage is: setwep device_path [ssid] [key]
+
Below are two examples. Let us assume your wifi network card is "/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".
+
Example 1: Connect with 64-bit WEP encryption using a hex digit key
At the moment there is no WPA encryption available in Haiku. However, there is some preliminary and unfinished code for implementing WPA available. Some tasks for improving this is to plug it into the wpa_supplicant build process and then fixing compile & runtime issues.
To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you need to run
+
install-wifi-firmwares.sh
+
+
The Intel ipw2100 and ipw22xx 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.
+
People building their own Haiku image can modify their build/jam/UserBuildConfig accordingly. Details for that and general updates on the wifi topic are found at the online version of this document.
+
If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a shell script, which will create a zip file for you to extract to Haiku's /boot. After that you'll have all files needed by install-wifi-firmwares.sh.
Когда приложение аварийно завершилось, вы должны использовать автоматически открывающийся отладчик. Введя в окне терминала с дебагером bt, вы создаёте "трассировку", которую необходимо скопировать в ваш багрепорт.
Аппаратные ошибки
-
Если вы столкнулись с ошибкой работы аппаратных средств и/или их драйвера, то вы должны приложить следующую информацию:
+
Если вы столкнулись с ошибкой работы оборудования и/или драйвера, то вы должны приложить следующую информацию:
listdev - подробный список оборудования, включающий ID поставщиков и отдельных устройств, схожа с командами Linux lshw и lspci.
listusb -v - при ошибке, связанной с USB, аналогична команде lsusb.
-
open /var/log/syslog - основной системный лог используемый Haiku, сродни выводимой на экран отладочной информации при загрузке в соответствующем режиме. С командой open можно вырезать нужную часть лога в текстовом редакторе.
+
open /var/log/syslog - основной системный лог, используемый Haiku, сродни выводимой на экран отладочной информации при загрузке в соответствующем режиме. С командой open можно вырезать нужную часть лога в текстовом редакторе.
listimage | grep drivers/ - список всех задействованных драйверов.
ints - доступна только в режиме Царства отладки ядра (Kernel Debugging Land - KDL) (см. ниже), отображает используемые прерывания. Не должно быть слишком много устройств, использующих одно прерывание.
@@ -86,8 +90,8 @@
Что дальше?
-
После того как багрепорт отправлен, разработчик рассмотрит вашу ошибку и попытаться классифицировать ее. Помните, что мы все добровольцы, и иногда багрепорт может оставаться без ответа некоторое время. Добавление новой информации об ошибке помогает исправить её быстрее, но не пытайтесь увеличить её значимость, добавляя не относящиеся к делу комментарии.
-
Помните, что отправка багрепорта, на который вы потратили некоторое время - это ещё полдела, и желательно чтобы вы следили за его состоянием. Только в этом случае вы внесёте ощутимую часть в процесс развития Haiku. У разработчиков могут возникнуть вопросы, относящиеся к багу во время его исправления, пожалуйста, не игнорируйте их, постаравшись как можно подробней ответить. Считайте свое участие законченным, только когда ошибка пиобритёт статус "исправлено (fixed)".
+
После того как багрепорт отправлен, разработчик рассмотрит вашу ошибку и попытаться классифицировать ее. Помните, что мы все добровольцы, и иногда багрепорт может оставаться без ответа некоторое время. Добавление новой информации к этой ошибке помогает исправить её быстрее, но не пытайтесь увеличить её значимость, добавляя не относящиеся к делу комментарии.
+
Помните, что отправка багрепорта, на который вы потратили некоторое время - это ещё полдела, и желательно чтобы вы следили за его состоянием. Только в этом случае вы внесёте ощутимую часть в процесс развития Haiku. У разработчиков могут возникнуть вопросы, относящиеся к багу во время его исправления, пожалуйста, не игнорируйте их, постаравшись как можно подробней ответить. Считайте свое участие законченным, только когда ошибка приобретёт статус "исправлено (fixed)".
diff --git a/welcome/ru/wifi.html b/welcome/ru/wifi.html
index 4bf3c7cd..7be60693 100644
--- a/welcome/ru/wifi.html
+++ b/welcome/ru/wifi.html
@@ -10,18 +10,20 @@
* Authors:
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
* Humdinger
+ * Translators:
+ * Diver
*
-->
- Wifi
+ Беспроводная сеть Wifi
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.
-This includes:
+Поддерживаемое оборудование:
+
Должны работать все wlan драйвера, поддерживаемые FreeBSD 8.
+Не поддерживаются все PCMCIA, CardBus, ExpressCard, USB и ISA карты. Поддерживаются только PCI, miniPCI, PCI-Express, miniPci-Express и PCI-X.
+
-
aironetwifi supporting at least
+
aironetwifi поддерживает как минимум:
Cisco Aironet 350 Series
Aironet PCI4500
Aironet PCI4800
-
atheroswifi supporting almost every chipset outthere (though no AR9285 chips)
-
broadcom43xx supporting
+
atheroswifi поддерживает почти все существующие чипсеты (кроме чипов AR9285)
+
broadcom43xx поддерживает:
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318
WEP encryption is available through a command-line application setwep. It is a temporary means for joining an unencrypted or WEP encrypted wifi network. setwep works with 64- and 128-bit WEP and supports both text keys as well as hex digit keys (see WEP notes below)
+WEP шифрование
+
WEP шифрование доступно через консольное приложение setwep. Это временный способ для подключения к незащищенным сетям или к сетям, использующим WEP шифрование. Приложение setwep работает с 64- и 128-битным WEP шифрованием и поддерживает как текстовые ключи, так и шестнадцатеричные ключи (смотрите примечание про WEP ниже).
-
The usage is: setwep device_path [ssid] [key]. Below are some examples.
-
In this example, let us assume your wifi network card is "/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".
-
Example 1: Connect with 64-bit WEP encryption using a hex digit key
+
Использование: setwep device_path [ssid] [key]
+
Ниже приведены два примера. Допустим, Ваша wifi сетевая карта это "/dev/net/iprowifi3945/0", а беспроводная сеть называется "haikuwifi".
+
Пример 1: Подключение с 64-битным WEP шифрованием, используя шестнадцатеричный ключ
Example 2: Connect to an unencrypted wireless network
+
Пример 2: Подключение к незашифрованной беспроводной сети
setwep /dev/net/iprowifi3945/0 haikuwifi
-
To find out what your device_path is, have a look in Preferences -> Network.
-
To make your wifi device connect to a given SSID at each boot, add the setwep command to your home/config/boot/UserBootscript.
+
Чтобы узнать какой у Вас device_path is, посмотрите в Preferences -> Network
+
Если вы хотите, чтобы Ваше wifi устройство подключалось к данной SSID после каждой загрузке, добавьте команду setwep в Ваш home/config/boot/UserBootscript
At the moment there is no WPA encryption available in Haiku. However, there is some preliminary and unfinished code for implementing WPA available. Some tasks for improving this is to plug it into the wpa_supplicant build process and then fixing compile & runtime issues.
В настоящий момент WPA шифрование не поддерживается в Haiku. Однако существует экспериментальный незавершенный код, реализующий поддержку WPA. Этот код потребуется внедрить в процесс сборки wpa_supplicant, а затем ликвидировать ошибки при компиляции и возможные проблемы при работе.
To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you'll need to run
+
Для установки микропрограмм для Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx и Marvell 88W8335 нужно запустить:
~> install-wifi-firmwares.sh
-
The Intel ipw2100 and ipw22xx 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.
-
People building their own Haiku image can modify their build/jam/UserBuildConfig accordingly. Details for that and general updates on the wifi topic are found at the online version of this document.
-
If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a shell script, which will create a zip file for you to extract to Haiku's /boot. After that you'll have all files needed by install-wifi-firmwares.sh.
+
Intel ipw2100 и ipw22xx установятся без Интернет-соединения, так как лицензионные условия позволяют Haiku распространять архивы с микропрограммой (firmware). Однако они требуют ознакомления конечного пользователя с условиями лицензии перед их установкой. Broadcom 43xx и Marvell 88W8335 требуют работающего Интернет-соединения, так как файлы, содержащие их микропрограммы (firmwares), не могут распространяться с Haiku.
+
Те, кто самостоятельно собирают собственные образы Haiku, могут соответственным образом изменить свой build/jam/UserBuildConfig. Описание этого процесса, а также обновление информации по поддержке wifi можно найти в онлайн-версии этого документа.
+
Если вы скачали микропрограмму (firmware), но не имеете работающего Интернет-соединения в Haiku, то онлайн-версия предлагает скрипт, который создаст для Вас zip файл, который нужно будет извлечь в директорию /boot. После этого у Вас будут все файлы, необходимые для запуска install-wifi-firmwares.sh.
The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
+
+
Reporting bugs
+
+
Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.
+
To keep our bugtracker effective, it's essential to abide by the Bug Tracker Etiquette.
+
+
Getting a Trac account
+
To file a ticket, you need to have an account at Haiku's Bugtracker.
+When creating a new account, be certain to provide your email address as it is necessary to obtain basic ticket modification privileges. Be sure to check your spam folder shortly afterwards, as the all important verification mail often ends up there.
+
+
Creating a bug report
+
Before reporting a bug, please make sure that it does not yet exist. You can also use the search function for this.
+After you have established that it's a unique bug, make your information as accurate as possible:
+
+
Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).
+
Mention which revision from SVN you are running. You can find this information in 'About This System...' from the Deskbar menu.
+
Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.
+
Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.
+
Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot (the PRINT key saves a PNG in /boot/home/).
+
+
+
Software Bugs
+
When an application crashed, you should invoke the debugger from the alert that pops up. Entering bt into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.
+
+
Hardware Bugs
+
When dealing with a hardware/driver related bug, you should attach the following information:
+
+
listdev - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' lshw and lspci.
+
listusb -v - assuming its a USB related issue, similar to lsusb.
+
open /var/log/syslog - the primary system log used by Haiku, akin to on screen debugging during boot. With the open command you can crop down the relevant part of the syslog in a text editor.
+
listimage | grep drivers/ - lists all used drivers.
+
ints - only available within Kernel Debugging Land (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.
+
+
You enter these commands into Terminal. Add a > output.txt after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.
+
+
Kernel Debugging Land - KDL
+
When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with ALTSysReqD (SysReq being PRINT on most keyboards).
+
+
co - will exit KDL and continue normal system operation, if possible.
+
int - will show interrupt usage (as described above).
+
bt - shows a backtrace, detailing where exactly the crash happened.
+
+
+
What's next?
+
After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
+non-descriptive comments.
+
Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
+as 'fixed'.
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.
+This includes:
+
+
+
aironetwifi supporting at least
+Cisco Aironet 350 Series
+Aironet PCI4500
+Aironet PCI4800
+
+
atheroswifi supporting almost every chipset outthere (though no AR9285 chips)
WEP encryption is available through a command-line application setwep. It is a temporary means for joining an unencrypted or WEP encrypted wifi network. setwep works with 64- and 128-bit WEP and supports both text keys as well as hex digit keys (see WEP notes below).
+
+
The usage is: setwep device_path [ssid] [key]
+
Below are two examples. Let us assume your wifi network card is "/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".
+
Example 1: Connect with 64-bit WEP encryption using a hex digit key
At the moment there is no WPA encryption available in Haiku. However, there is some preliminary and unfinished code for implementing WPA available. Some tasks for improving this is to plug it into the wpa_supplicant build process and then fixing compile & runtime issues.
To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you need to run
+
install-wifi-firmwares.sh
+
+
The Intel ipw2100 and ipw22xx 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.
+
People building their own Haiku image can modify their build/jam/UserBuildConfig accordingly. Details for that and general updates on the wifi topic are found at the online version of this document.
+
If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a shell script, which will create a zip file for you to extract to Haiku's /boot. After that you'll have all files needed by install-wifi-firmwares.sh.
WEP encryption is available through a command-line application setwep. It is a temporary means for joining an unencrypted or WEP encrypted wifi network. setwep works with 64- and 128-bit WEP and supports both text keys as well as hex digit keys (see WEP notes below)
+
WEP encryption is available through a command-line application setwep. It is a temporary means for joining an unencrypted or WEP encrypted wifi network. setwep works with 64- and 128-bit WEP and supports both text keys as well as hex digit keys (see WEP notes below).
-
The usage is: setwep device_path [ssid] [key]. Below are some examples.
-
In this example, let us assume your wifi network card is "/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".
+
The usage is: setwep device_path [ssid] [key]
+
Below are two examples. Let us assume your wifi network card is "/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".
Example 1: Connect with 64-bit WEP encryption using a hex digit key
To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you'll need to run
-
~> install-wifi-firmwares.sh
+
To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you need to run
+
install-wifi-firmwares.sh
The Intel ipw2100 and ipw22xx 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.
People building their own Haiku image can modify their build/jam/UserBuildConfig accordingly. Details for that and general updates on the wifi topic are found at the online version of this document.
So weit es geht, sind alle schwerwiegendere Fehler beseitigt. Da es sich aber trotz alle dem um eine Alpha-Version handelt, muss man davon ausgehen, dass noch Fehler vorhanden sind, die noch nicht entdeckt wurden.
-
Vom Verwenden dieser Alpha-Version in einer systemkritischen Umgebung wird dringend abgeraten! Obwohl es unwahrscheinlich ist, kann ein Datenverlust nicht ausgeschlossen werden!
Alle schwerwiegenden Fehler sind, soweit bekannt, beseitigt. Da es sich aber trotz alle dem um eine Alpha-Version handelt, muss man davon ausgehen, dass es noch Fehler gibt, die noch nicht entdeckt wurden.
+
Diese Alpha-Version sollte nicht für wirklich kritische Aufgabe verwendet werden! Obwohl es unwahrscheinlich ist, kann Datenverlust nicht ausgeschlossen werden!
-
Einer der Hauptgründe, diese Alpha-Version zu veröffentlichen war, das System einer Vielzahl von Menschen zum Testen anbieten zu können. Nur so ist es möglich, alle Fehler zu finden und Verbesserungsvorschläge zu erhalten. Deshalb sollte nicht gezögert werden, Fehler auch zu melden!
+
Einer der Hauptgründe für diese Alpha-Version ist, das System möglichst vielen Leuten zum Testen anbieten zu können. Nur so ist es möglich, alle Fehler zu finden und Verbesserungsvorschläge zu erhalten. Deshalb sollte nicht gezögert werden, Fehler auch zu im Bug Tracker zu melden (nachdem man dessen Suchfunktion benutzt hat, um Doppeleinträge zu vermeiden).
Da Haiku darauf abzielt ein würdiger Nachfolger des BeOS R5 zu werden, ist eine Erfahrung mit diesem System natürlich hilfreich. Darüber hinaus sei auf diese Punkte verwiesen:
+
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:
Da Haiku eine Reimplemention des BeOS R5 ist, sind die API die gleichen (mit einigen Erweiterungen). Deshalb ist die Dokumentation im Be Book immernoch eine hilfreiche Quelle. Dankenswerter weise hat die Firma ACCESS, die alle Rechte von Be Inc. übernommen hat, einer Veröffentlichung des Be Book zugestimmt.
+
Da Haiku eine Reimplemention des BeOS R5 ist, sind die API die gleichen (mit einigen Erweiterungen). Deshalb ist die Dokumentation im Be Book immernoch eine hilfreiche Quelle. Dankenswerterweise hat die Firma ACCESS, die alle Rechte von Be Inc. übernommen hat, einer Veröffentlichung des Be Book zugestimmt.
Diese Informationen sollten einen guten Einstieg in die Materie vermitteln:
@@ -106,7 +109,7 @@ Dazu benutzt man einen Befehl im Terminal: installoptionalpackage -h er
Um sich mit anderen Entwickler und Anwender auszutauschen muss man nur an den Diskussionen im IRC, unseren Foren oder Mailinglisten teilnehmen. Wie üblich, wenn sich mehrere Menschen unterhalten, sollte eine gewisse Etikette eingehalten werden.
+
Um sich mit anderen Entwickler und Anwendern auszutauschen, muss man nur an den Diskussionen im IRC, unseren Foren oder Mailinglisten teilnehmen. Wie üblich, wenn sich mehrere Menschen unterhalten, sollte eine gewisse Etikette eingehalten werden.
We have been working hard to fix all possible to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.
+
We have been working hard to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.
We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.
One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.
@@ -85,7 +88,7 @@ You'll have to run a command in Terminal: installoptionalpackage -h exp
Wifi does work to some extend. At the moment you can only log into unprotected or WEP encrypted wireless networks. Due to several different licensing policies of different vendors, a manual installation process for the firmware may be required. A list of working devices and instructions for installation can be found in our Wifi page (also online).
+
Wifi does work to some extent. At the moment you can only connect to unencrypted or WEP encrypted wireless networks. Due to several different licensing policies of different vendors, a manual installation process for the firmware may be required. A list of working devices and instructions for installation can be found on our Wifi page (also online).
Hemos trabajado muy duro para arreglar todos los fallos posibles, aún así, siendo una versión alpha, es muy probable que haya muchos por descubrir.
-
No se recomienda el uso de versiones alfa como sistemas de producción. Su información podría alterarse, estropearse o destruirse en algún momento.
+
No se recomienda el uso de versiones alfa como sistemas de producción. Su información bien podría alterarse, estropearse o destruirse en algún momento.
Una de las razones principales para liberar una versión alpha es atraer a mucha gente para probar el sistema y descubrir fallos o darnos sugerencias para futuras mejoras. Por favor, archive los fallos y mejoras en nuestro bug tracker después de utilizar su sistema de búsqueda para evitar duplicados.
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:
Because of our binary and source compatibility, many BeOS applications run on Haiku (you may have to install the optional package "beoscompatibility" for some programs, see below). After downloading a package, simply unzip it (double clicking opens Expander) to /boot/apps/ and start the application from there.
Debido a nuestra compatibilidad de código binario y código fuente, muchas aplicaciones de BeOS funcionan en Haiku (tal vez tenga que instalar el paquete "beoscompatibility" para algunos programas, vea debajo). Tras descargar un paquete, tan sólo debe descomprimirlo (dando doble clic se abre Expander) con destino a /boot/apps/ y se inicia la aplicación desde ahí).
Repositorios de software populares son:
@@ -88,12 +91,12 @@ Al correrse el siguiente comando en una Terminal: installoptionalpackage -h<
Wifi does work to some extend. At the moment you can only log into unprotected or WEP encrypted wireless networks. Due to several different licensing policies of different vendors, a manual installation process for the firmware may be required. A list of working devices and instructions for installation can be found in our Wifi page (also online).
La red inalámbrica (Wifi) trabaja hasta cierto punto. Al momento se puede conectar a redes inalámbricas con encripción WEP. Debido a políticas de licencias diferentes de fabricantes diferengtes, se puede requerir un proceso de instalación manual del firmware. Una lista de dispositivos funcionando e instrucciones para instalación se pueden encontrar en nuestra página Wifi (también disponible en línea).
Como Haiku es una reimplementación, la API es la misma que para BeOS R5 (con algunos añadidos). Por lo tanto, la documentación existente en el BeBook es todavía un recurso válido. Gracias a ACCESS, quien tiene los derechos de la antigua Be Inc., se nos permite distribuir una copia del BeBook.
Existen algunos recursos que le pueden ayudar a comenzar:
Merci beaucoup d’essayer Haiku ! Voici notre seconde version publique. Nous espérons encourager de nouveaux développeurs à nous rejoindre et donner aux futurs utilisateurs la possibilité d’essayer Haiku. Nous sommes conscients que cette version alpha ne remplit pas touts les objectifs que nous nous sommes fixés et ne fournit pas toutes les fonctionnalités et l’expérience utilisateur attendues pour la version R1 finale. Néanmoins, nous espérons que cette version (même inachevée) vous permettra de découvrir le potentiel de Haiku et de partager notre enthousiasme.
+
Merci beaucoup d’essayer Haiku ! Voici notre seconde version publique. Nous espérons encourager de nouveaux développeurs à nous rejoindre et donner aux futurs utilisateurs la possibilité d’essayer Haiku. Nous sommes conscients que cette version alpha ne remplit pas tous les objectifs que nous nous sommes fixés et ne fournit pas toutes les fonctionnalités et l’expérience utilisateur attendues pour la version R1 finale. Néanmoins, nous espérons que cette version (même inachevée) vous permettra de découvrir le potentiel de Haiku et de partager notre enthousiasme.
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 :
Because of our binary and source compatibility, many BeOS applications run on Haiku (you may have to install the optional package "beoscompatibility" for some programs, see below). After downloading a package, simply unzip it (double clicking opens Expander) to /boot/apps/ and start the application from there.
+
Grâce à notre compatibilité binaire et source avec BeOS, de nombreuses applications écrites pour ce système fonctionne sous Haiku. Après avoir téléchargé un paquet, décompressez le (un double-clic lancera Expander) dans /boot/apps/ et démarrez l'application depuis de ce dossier.
-
Des sites populaires référencent les logiciels disponibles.
+
Voici quelques sites populaires référençant un certain nombre de logiciels :
Wifi does work to some extend. At the moment you can only log into unprotected or WEP encrypted wireless networks. Due to several different licensing policies of different vendors, a manual installation process for the firmware may be required. A list of working devices and instructions for installation can be found in our Wifi page (also online).
Le Wifi ne fonctionne que partiellement. Pour le moment vous ne pouvez vous connecter qu'à des réseaux sans fils non-sécurisés ou à ceux cryptés en WEP. En raison des politiques de licence de certains fournisseurs, il peut être nécessaire d'installer manuellement le micro-logiciel de votre adaptateur réseau. Une liste des périphériques et leurs instructions d'installation peuvent être trouvées sur notre page Wifi (ou en ligne).
Thank you very much for checking out Haiku! This is our second public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this alpha release does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.
We have been working hard to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.
+
We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.
+
+
One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.
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:
Because of our binary and source compatibility, many BeOS applications run on Haiku (you may have to install the optional package "beoscompatibility" for some programs, see below). After downloading a package, simply unzip it (double clicking opens Expander) to /boot/apps/ and start the application from there.
HaikuPorts - maintains patches for ported software
+
OsDrawer - hosts native BeOS and Haiku open source software projects
+
+
+
There are also so-called Optional Packages, which are used by Haiku's build system. It is not intended for end users to manually extract and install them. Instead, a utility script is provided, installoptionalpackage. This script is meant to bridge the gap while Haiku's package management is still under construction. It will allow you to install most of the available Optional Packages.
+You'll have to run a command in Terminal: installoptionalpackage -h explains its usage.
Wifi does work to some extent. At the moment you can only connect to unencrypted or WEP encrypted wireless networks. Due to several different licensing policies of different vendors, a manual installation process for the firmware may be required. A list of working devices and instructions for installation can be found on our Wifi page (also online).
Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.
+
+
There are additional resources that should help you getting started:
Get in contact with other developers and users and join the discussions on IRC, in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our Mailing List Etiquette.
Thank you very much for checking out Haiku! This is our second public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this alpha release does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.
We have been working hard to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.
+
We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.
+
+
One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.
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:
Because of our binary and source compatibility, many BeOS applications run on Haiku (you may have to install the optional package "beoscompatibility" for some programs, see below). After downloading a package, simply unzip it (double clicking opens Expander) to /boot/apps/ and start the application from there.
HaikuPorts - maintains patches for ported software
+
OsDrawer - hosts native BeOS and Haiku open source software projects
+
+
+
There are also so-called Optional Packages, which are used by Haiku's build system. It is not intended for end users to manually extract and install them. Instead, a utility script is provided, installoptionalpackage. This script is meant to bridge the gap while Haiku's package management is still under construction. It will allow you to install most of the available Optional Packages.
+You'll have to run a command in Terminal: installoptionalpackage -h explains its usage.
Wifi does work to some extent. At the moment you can only connect to unencrypted or WEP encrypted wireless networks. Due to several different licensing policies of different vendors, a manual installation process for the firmware may be required. A list of working devices and instructions for installation can be found on our Wifi page (also online).
Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.
+
+
There are additional resources that should help you getting started:
Get in contact with other developers and users and join the discussions on IRC, in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our Mailing List Etiquette.
Большое спасибо за проявленный интерес к Haiku! Это наш второй публичный релиз, мы надеемся привлечь новых разработчиков к нашему проекту и дать будущим пользователям шанс увидеть Haiku в деле. Понятно, что этот альфа-релиз далеко не полностью соответствует намеченным нами целям, и не предоставляет все функции, которые мы собирались дать конечному пользователю, запланировав их для финальной версии R1. Однако, мы надеемся, что этот релиз позволит Вам заметить большой потенциал Haiku, и Вы найдёте немного времени для её изучения.
+
Большое спасибо за проявленный интерес к Haiku! Это наш второй публичный релиз, мы надеемся привлечь новых разработчиков к нашему проекту и дать будущим пользователям шанс увидеть Haiku в деле. Понятно, что этот альфа-релиз далеко не полностью соответствует намеченным нами целям, и не предоставляет все функции, которые мы собирались дать конечному пользователю, запланировав их для финальной версии R1. Однако мы надеемся, что этот релиз позволит Вам заметить большой потенциал Haiku, и вы найдёте немного времени для её изучения.
Мы провели тяжёлую работу по выявлению и устранению ошибок ("багов"), однако это только альфа-релиз и в нём обязательно присутствуют немало скрытых ошибок.
-
Мы не рекомендуем использовать альфа-версии в качестве основной операционной системы. В Ваши данные с большой вероятностью могут быть внесены нежелательные изменения, они могут исказиться или даже могут быть уничтожены.
Мы провели тяжёлую работу по выявлению и устранению ошибок ("багов"), однако это только альфа-релиз и в нём обязательно присутствует немало скрытых ошибок.
+
Мы не рекомендуем использовать альфа-версии в качестве основной операционной системы. В ваши данные с большой вероятностью могут быть внесены нежелательные изменения, они могут быть искажены или даже уничтожены.
Одной из главных причин для выпуска альфа-версии явиляется желание привлечь больше пользователей для тестирования и обнаружения ошибок, а также получения от них предложений по дальнейшему улучшению Haiku. Пожалуйста, оставляйте отчёты о найденных багах и предложения по улучшению в нашей системе отслеживания ошибок (bug tracker), но только после использования поиска, чтобы избежать дубликатов.
Первые релизы Haiku будут похожи по функционалу и вешнему виду на BeOS R5, которую она и призвана повторить. Если Вы никогда не пользовались этой операционной системой, то рекомендуется воспользоваться следующими ссылками:
+
Первые релизы Haiku будут похожи по функционалу и вешнему виду на BeOS R5, которую она и призвана повторить. Если вы никогда не пользовались этой операционной системой, то рекомендуется воспользоваться следующими ссылками:
Because of our binary and source compatibility, many BeOS applications run on Haiku (you may have to install the optional package "beoscompatibility" for some programs, see below). After downloading a package, simply unzip it (double clicking opens Expander) to /boot/apps/ and start the application from there.
+
Так как Haiku бинарно и на уровне исходных кодов совместима с BeOS, то многие BeOS-приложения работают и в ней (для некоторых программ возможно потребуется установить пакет "beoscompatibility"). Загрузив архив с программой, просто распакуйте его (достаточно двойного клика для открытия архива в Expander) в /boot/apps/, и оттуда же запускайте это приложение.
Популярные каталоги программ:
-
Haikuware сайт с программами, ориентированными на Haiku.
-
BeBits самый популярный каталог программ для BeOS (в последнее время и для Haiku).
+
Haikuware - сайт с программами, ориентированными на Haiku.
+
BeBits - самый популярный каталог программ для BeOS (в последнее время и для Haiku).
HaikuPorts - библиотеки, необходимые для портирования приложений.
OsDrawer - хранилище для разрабатываемых приложений с открытым исходным кодом для BeOS и Haiku.
Wifi does work to some extend. At the moment you can only log into unprotected or WEP encrypted wireless networks. Due to several different licensing policies of different vendors, a manual installation process for the firmware may be required. A list of working devices and instructions for installation can be found in our Wifi page (also online).
Wifi поддерживается частично. В настоящий момент возможно подключение к незащищенным сетям или к сетям, защищенным WEP шифрованием. Из-за разных лицензионных политик разных производителей возможно потребуется ручная установка микропрогаммы (firmware). Список работающих устройств и инструкции по установке можно посмотреть на нашей странице Wifi (а также в Интернете).
Thank you very much for checking out Haiku! This is our second public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this alpha release does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.
We have been working hard to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.
+
We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.
+
+
One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.
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:
Because of our binary and source compatibility, many BeOS applications run on Haiku (you may have to install the optional package "beoscompatibility" for some programs, see below). After downloading a package, simply unzip it (double clicking opens Expander) to /boot/apps/ and start the application from there.
HaikuPorts - maintains patches for ported software
+
OsDrawer - hosts native BeOS and Haiku open source software projects
+
+
+
There are also so-called Optional Packages, which are used by Haiku's build system. It is not intended for end users to manually extract and install them. Instead, a utility script is provided, installoptionalpackage. This script is meant to bridge the gap while Haiku's package management is still under construction. It will allow you to install most of the available Optional Packages.
+You'll have to run a command in Terminal: installoptionalpackage -h explains its usage.
Wifi does work to some extent. At the moment you can only connect to unencrypted or WEP encrypted wireless networks. Due to several different licensing policies of different vendors, a manual installation process for the firmware may be required. A list of working devices and instructions for installation can be found on our Wifi page (also online).
Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.
+
+
There are additional resources that should help you getting started:
Get in contact with other developers and users and join the discussions on IRC, in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our Mailing List Etiquette.
We have been working hard to fix all possible to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.
+
We have been working hard to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.
We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.
One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.
@@ -87,7 +91,7 @@ You'll have to run a command in Terminal: installoptionalpackage -h exp
Wifi does work to some extend. At the moment you can only log into unprotected or WEP encrypted wireless networks. Due to several different licensing policies of different vendors, a manual installation process for the firmware may be required. A list of working devices and instructions for installation can be found in our Wifi page (also online).
+
Wifi does work to some extent. At the moment you can only connect to unencrypted or WEP encrypted wireless networks. Due to several different licensing policies of different vendors, a manual installation process for the firmware may be required. A list of working devices and instructions for installation can be found on our Wifi page (also online).
Deutsch
Français
Italiano
Русский
Español
Svensk
日本語
Українська
English
-Expected supported hardware
Deutsch
Français
Italiano
Русский
Español
Svensk
日本語
Українська
English