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.
+
The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
Screenshot
@@ -75,26 +76,18 @@ Tomar una captura de pantalla desde la Terminal
There's a special screenshot application to be used from Terminal or a script. screenshot --help shows the familiar options as parameters:
-
~> screenshot --help
+
~> Screenshot --help
-screenshot [OPTIONS] [FILE] Creates a bitmap of the current screen
+Screenshot [OPTION]... Creates a bitmap of the current screen
-FILE is the optional output path / filename used in silent mode. An exisiting
-file with the same name will be overwritten without warning. If FILE is not
-given the screenshot will be saved to a file with the default filename in the
-user's home directory.
-
-OPTIONS
+OPTION
+ -o, --options Show options window first
-m, --mouse-pointer Include the mouse pointer
-b, --border Include the window border
-w, --window Capture the active window instead of the entire screen
- -d, --delay=seconds Take screenshot after the specified delay [in seconds]
- -s, --silent Saves the screenshot without showing the application
- window
- -f, --format=image Give the image format you like to save as
- [bmp], [gif], [jpg], [png], [ppm], [tga], [tif]
- -c, --clipboard Copies the screenshot to the system clipboard without
- showing the application window
+ -d, --delay=seconds Take screenshot after specified delay [in seconds]
+ -s, --silent Saves the screenshot without showing the app window
+ overrides --options, saves to home folder as png
Note: OPTION -b, --border takes only effect when used with -w, --window
Nella pima tab, Colori, puoi cambiare i colori di diverse parti dell'interfaccia utente. Il colore accetta anche drag&drop da altri programmi, permettendo di prendere colori da, per esempio, WonderBrush, Icon-O-Matic o dal pannello di Backgrounds.
+
Nella prima tab, Colori, puoi cambiare i colori di diverse parti dell'interfaccia utente. Il colore accetta anche drag&drop da altri programmi, permettendo di prendere colori da, per esempio, WonderBrush, Icon-O-Matic o dal pannello di Backgrounds.
The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
CDPlayer
Deskbarメニュー:
Applications
場所:
/boot/system/apps/CDPlayer
-
設定ファイル:
~/cd/* - Stores details to all identified CDs
+
設定ファイル:
~/cd/* - 認識されたすべてのCDの詳細情報が保存されています
-
Usage is pretty much what you'd expect from looking at the control buttons.
-Activate the Repeat button to the left of Shuffle to loop the complete CD.
-
If you need more control like playlists, try MediaPlayer instead.
The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
CharacterMap
@@ -56,10 +57,10 @@
設定ファイル:
~/config/settings/CharacterMap settings
-
CharacterMap will show you the UTF-8 code of every character a font supports.
+
CharacterMapは、そのフォントがサポートしている各文字のUTF-8コードを表示します。
-
To the left you have the standardized blocks, together with a handy filter function. Optionally, you can choose to also Show Private Blocks from the View menu. The right shows the actual characters in these blocks, using the font specified in the Font menu. Below that you can change the font size. And below that, the values of the character currently under the mouse pointer is displayed in hex, decimal and UTF-8 notation.
-
You can drag&drop a character directly from the character map into a text editor, or right-click on one to either Copy Character (ALTC) or Copy As Escaped Byte String (SHIFTALTC). Resulting in, e.g. either € or \xe2\x82\xac.
文字コード・マップからテキスト・エディタに対して文字を直接ドラッグ・アンド・ドロップすることができます。他の機能として、文字を右クリックしてCopy Character (ALTC)を選択することも、Copy As Escaped Byte String (SHIFTALTC)を選択することもできます。例えば、前者の場合は€という文字が、後者の場合は\xe2\x82\xacという文字列がコピーされます。
The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
-
Commandline applications
+
コマンドライン・アプリケーション
-
Location:
/boot/system/bin /boot/common/bin ~/config/bin
+
場所:
/boot/system/bin /boot/common/bin ~/config/bin
-
All commandline applications shipped with Haiku are in either /boot/system/bin or /boot/common/bin. Your own or additionally installed commandline apps should go in ~/config/bin. All these locations are part of the PATH variable and are therefore automatically found.
-The following isn't an exhaustive list of all Haiku-specific CLI apps, it serves just to highlight a few of the most useful to give you a taste. Feel encouraged to explore what's in the bin/ folders on your own a bit. Executing an app with the parameter --help shows the usage of the command and all its various options.
These commands are used to display, read out, add and remove attributes of files. Remember that these meta data are currently only available on BFS formatted volumes. Moving files onto other file systems will strip all attributes!
-All these commands are described in topic Attributes in Terminal.
With these commands you list, make, reindex and remove attributes to BFS' index. Every volume has it's own index, remember that when copying files from one volume to another.
-These commands are described in topic Index.
alert conjures up the typical alert window with a pre-defined icon, explanatory text and up to three buttons. It will return the title of the pressed button and an exit status (starting with 0). For example, this is made of the line:
alert --idea "FantasticApp(tm) installed successfully!
Would you like a link to it?" "On Desktop" "In Deskbar" "No thanks"
filepanel
-
filepanel displays a load or save file panel and lets the user choose a file or location. As a return value you'll get the chosen file or folder's path. There are several parameters available, for example to set a starting directory, a window title, a default name when saving or restrictions to the allowed types of files. This is an example of
filepanel -s -t "Save your logfile" -d ~/config/settings -n Fantastic.log
waitfor
-
waitfor is a nice way to wait for a particular application or thread to be started or to have ended.
+
waitforはアプリケーションやスレッドの開始および終了を待つのにピッタリの方法です。
query
-
query is the commandline version of the Find panel. In fact, a quick way to generate the search term is to build a query in the Find panel, switch to by formula, add double quotes (") in front and back and paste the whole string after your query command in Terminal or your script.
checkfs is an important tool to check for errors in your file system. Simply add the volume or device name and it'll run through every file and correct inconsistencies where possible.
open is a very handy little tool. With it you open any file with its preferred application, or start a specific application by its signature without the need to know its exact path. It also works with URLs and even with the "virtual" directories . for the current directory and .. for the parent, opening the folder in Tracker.
desklink can install an icon for any file, folder, query or application in the Deskbar tray. It also offers the option to provide a context menu when right-clicking an icon to execute special actions. As an example, try this to add Screenshot with various options (the "\" in the first line is just for the line break in Terminal):
To the left under the preview, you set the filename that'll be suffixed with an increasing number for every picture taken. Beneath that you decide on the file format and the rate the pictures are taken.
-
To the right you choose either FTP or sFTP (if SSH is available) and enter the needed data to save the images on a server.
The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
-
Boot Loader
+
ブートローダー
-
Haiku's Boot Loader can help when you experience hardware related problems or want to choose which Haiku installation to start, if you have more than one (maybe on an installation CD or USB stick).
-It's also handy after you installed a software component that acts up and prevents you from booting the system to remove it again. The Disable user add-ons option that's mentioned below, will start Haiku without loading user installed components, e.g. a driver.
-
To enter the Boot Loader options, you have to press and keep holding the SHIFT key before the beginning of Haiku's boot process. If there's a boot manager installed, you can start holding SHIFT before invoking the boot entry for Haiku. If Haiku is the only operating system on the machine, you can begin holding the key while still seeing boot messages from the BIOS.
+
ハードウェア周りに問題が生じた場合や、Haikuを2つ以上インストールしていて(おそらくインストールCD上あるいはUSBメモリ上のHaiku)、そのいずれかを選択したい場合にHaikuのブートローダーは役立ちます。
+また、あるソフトウェア・コンポーネントをインストールしたもののそれが正しく動作せず、システムの起動を妨げてしまうような状況で、そのコンポーネントを再度削除するのにもHaikuのブートローダーは役立ちます。後で述べるように、Disable user add-onsオプションを有効にすると、ドライバーといったユーザーがインストールしたコンポーネントを読み込まずにHaikuが起動します。
There are several options to try in case of hardware related trouble. When moving the selection bar to an option, a short explanation appears at the bottom of the screen.
+
- Safe mode - Disable user add-ons - Disable IDE DMA
@@ -72,31 +73,31 @@ It's also handy after you installed a software component that acts up and preven
- Disable ACPI
Select debug options
-
Here you'll find several options that help with debugging or getting details for a bug report. Again, a short explanation for each option is displayed at the bottom.
+
Перевод этой страницы еще не завершен. Пока это не произойдет, незавершенные части будут на английском.
+
The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
Screenshot
Расположение в Deskbar:
Приложения (Applications)
-
Расположение в Tracker:
/boot/system/apps/Screenshot
-/bin/screenshot
+
Расположение в Tracker:
/boot/system/apps/Screenshot
Настройки хранятся по адресу:
~/config/settings/screenshot
-
Screenshots are taken by either starting the Screenshot application or by pressing the PRINT key,
+
Помимо получения обычных скриншотов через клавишу Print Screen, которая помещает изображение текущего экрана в PNG формате в папку /boot/home, это приложение содержит и ряд других полезных настроек.
-
In the Screenshot panel you can toggle between taking the whole screen or just the active window and decide if the window border and mouse pointer should be included. You can also enter a delay before a screenshot is taken.
+
Помимо очевидных опций - захвата всего экрана (Capture entire screen), либо только активного окна (Capture active window), включая его грани (Include window border) и курсор мыши (Include mouse pointer), также имеется возможность ввести задержку перед снятием скриншота. Эта задержка будет задействована, только если вы снимаете новый скриншот, нажимая кнопку Take Screenshot.
Below that you set the name, format and location for the screenshot that will be used when you click Save. Instead of saving the file to disk you can also decide to Copy to clipboard to be able to paste the shot directly into another application, or take a New screenshot.
All settings are remembered the next time you take a screenshot, enabling these convenient keyboard shortcuts:
@@ -72,31 +72,22 @@
Снятие скриншота из Terminal
-
There's a special screenshot application to be used from Terminal or a script.
-screenshot --help shows the familiar options as parameters:
+
Приложение Screenshot также можно использовать из Terminal или через скрипт.
+Screenshot --help выведет справку о доступных параметрах:
-
~> screenshot --help
+
~> Screenshot --help
-screenshot [OPTIONS] [FILE] Creates a bitmap of the current screen
+Screenshot [OPTION]... Создает изображение текущего экрана.
-FILE is the optional output path / filename used in silent mode. An exisiting
-file with the same name will be overwritten without warning. If FILE is not
-given the screenshot will be saved to a file with the default filename in the
-user's home directory.
+Опция:
+ -o, --options При запуске сразу откроется окно параметров
+ -m, --mouse-pointer Включает в снимок курсор мыши
+ -b, --border Включает в снимок грани окна
+ -w, --window Делает снимок только активного окна, а не всего экрана
+ -d, --delay=seconds Делает скриншот с указанной задержкой [в секундах]
+ -s, --silent Сохраняет скриншот, игнорируя настройки, выставленные в окне параметров и сохраняет его в домашнюю папку в PNG формате.
-OPTIONS
- -m, --mouse-pointer Include the mouse pointer
- -b, --border Include the window border
- -w, --window Capture the active window instead of the entire screen
- -d, --delay=seconds Take screenshot after the specified delay [in seconds]
- -s, --silent Saves the screenshot without showing the application
- window
- -f, --format=image Give the image format you like to save as
- [bmp], [gif], [jpg], [png], [ppm], [tga], [tif]
- -c, --clipboard Copies the screenshot to the system clipboard without
- showing the application window
-
-Note: OPTION -b, --border takes only effect when used with -w, --window
+Примечание: Опция -b, --border сработает только совместно с опцией -w, --window
Contrary to the BeOS, Haiku uses vector icons instead of bitmap icons. A special Haiku Vector Icon Format (HVIF) was developed that is highly optimized for small file sizes and fast rendering. That's why our icons are for the most part much smaller than either a bitmap or the widely used SVG format. Also, unlike BeOS' bitmap icons, Haiku isn't limited to an 8bit palette (256 colors).
-Take this icon of the Terminal, for example:
Note that the BeOS used two versions of an icon, one 16x16 and one 32x32, to achieve good visuals in List and Icon View mode.
-
This trick isn't needed with vector icons. Besides only taking up a few hundred bytes in a file, vector icons also scale much better than bitmaps. (Note: BeOS offered only a 16x16 and 32x32 display.)
The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
文本搜索
@@ -63,23 +62,22 @@
-
You enter a search string in the text box on top and hit RETURN or click Search to start. If Show lines is checked, the hits are automatically expanded to show the lines of the file containing the search string.
Only a few words on some of the otherwise self-explaining menu items:
+
对于其他的菜单项，在下面将会给出相应的解释：
File 菜单
-
New window
ALTN
Opens a new window where you can enter another string and search through the same files/folders.
-
-
Set target...
ALTF
Lets you choose a new set of files and folders to search through.
+
New window
ALTN
打开新窗口，您可以输入其他的字符，然后在相同的文件/文件夹中进行搜索。
+
Set target...
ALTF
让你选择新的目标文件和文件夹进行搜索。
Action 菜单
-
Trim selection
ALTT
Removes all entries from the list that are not currently selected.
-
Open selection
ALTO
Opens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found.
-
Open files in Tracker
ALTK
Opens the location of the currently selected files in Tracker.
This is useful when working in a "unixy" environment, where often administrative files are hidden inside ".folders/". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku.
-
Escape search text
TextSearch uses the command line tool grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions.
-
Text files only
TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.
Haiku provides a system that retrieves e-mail regularly via a Mail Service (also known as mail_daemon) and saves each mail as a single text file. It parses the mail and fills its attributes with all necessary header information, like from, to, subject and its unread status. Now it can be queried by you or any application. This system also makes switching e-mail clients easy as all the data and your configuration stays the same.
-The configuration is done in the E-Mail preference panel.
首先， declare the Account Type which is either Receive Mail Only, Send Mail Only, or the most usual type, Send and Receive Mail. Then you set how you get your mail, via POP3 or IMAP.
-
Now you enter your E-mail Address, Login Name and Password, give an Account Name under which it will be known under Haiku and your Real Name.
-
If your account is from a major e-mail provider, Haiku already knows all technical details like server IP addresses and the following information is already filled in automatically. If that is not the case, just follow this guide and fill in the details to your e-mail account accordingly.
+
首先，声明账户类型：Receive Mail Only ，Send Mail Only ，或常用的 Send and Receive Mail。然后您需要设置如何接收邮件，POP3 或 IMAP。
Click on Incoming under your account's name to set up how e-mails are received.
+
点击您的账户名下的 Incoming 设置如何进行邮件的接收。
-
From the pop-up menu you choose the protocol used by your provider. IMAP and POP3 are supported.
+
从弹出菜单中，选择您的提供商所使用的协议。目前支持的协议有 IMAP 和 POP3 。
Next is the Mail Server address for incoming mails. If your provider needs you to log into a specific port, you add that to the address, separated by a colon. For example, pop.your-provider.org:1400.
Then you enter your login information, Username and Password, and if necessary change the Login Type from the default Plain Text to APOP for authentication.
If you use POP3 and retrieve mails of this account from different computers, you may want to activate the option to Leave mail on server and only Remove mail from server when deleted locally.
The generated text file can then be opened in a text editor. Make sure to use a fixed font in that editor or you'll never grok that file...
-At the beginning of that file, you'll find a legend of a stylized keyboard with the hex value corresponding to each key. Below that are the actual assignments of every value. You can do all the customizing that's also available from the Keymap preference panel, and then some. If you happen to have some special keys on your keyboard, you may be able to activate them. That is, use them as ordinary keys or like an option or control key. You won't be able to, for example, have your multimedia keys de/increase the volume or start some application. For this you can use e.g. SpicyKeys.
The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
触摸板
@@ -65,19 +64,22 @@
通过拖动触摸板上显示的红色的水平或者垂直区域， 您可以进行滚动区域的设置（slightly reddish against the grey general touch area）。如果您在触摸板的该区域上下移动手指，它将会上下移动对应窗口中的滚动条。
-
To the right are sliders to set the general scroll acceleration and the vertical and horizontal scrolling speed.
-The acceleration setting decides how much quicker a list scrolls by if you swish over the scroll area very fast. The scrolling speeds control the general speed when using the scroll area in a "normal" way.
-
Below the touchpad graphic are checkboxes to enable "Two finger scrolling" for vertical and horizontal scrolling. Move two fingers in parallel vertically or horizontally to move the scrollbars of a window. At least for me, it works best if with one finger from the left and one from the right hand.
-If you feel comfortable using this feature, you can dispense with setting scroll areas and instead use the whole pad for normal navigation.
-
At the bottom is another slider to set the tap click sensitivity. If your taps keep getting ignored, increase the sensitivity. If the system registers clicks all the time, while all you want is to move the mouse pointer, try decreasing it.
Here is a tip that's not related to the Touchpad preferences, but fits the general topic:
-Did you know that you can do a drag and drop just by using the touchpad, i.e. not using the buttons? Just do a double click without lifting the finger after the second click. The picked up icon will stick to the mouse pointer and you can drag it around by moving your finger. Lifting your finger will drop the icon.
-
If your finger reaches a border of the touchpad while dragging an icon, but the mouse pointer hasn't yet reached the screen edge, how can you keep on dragging your icon? As soon as you lift your finger, the icon would be dropped.
-Depending on your hardware, there's a nifty feature: just leave your finger without lifting at the touchpad edge. The mouse pointer will keep on moving on auto-pilot.
A query is a file search based on file attributes and can be performed within Tracker or in Terminal. Queries are saved in /boot/home/queries/ and by default last seven days before being purged. Note, these aren't static result lists of your search, but are the query formulas which trigger a new search whenever you open them.
-Even better, you don't have to double-click to re-do a query. You can drill down a saved query just like any folder by right-clicking on it and navigating through the submenus.
You start a query by invoking the Find... menu either from the Deskbar menu or any Tracker window or the Desktop (which is actually a fullscreen Tracker window). The shortcut is ALTF. You're presented with the Find window:
The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
Signaler les bogues
@@ -68,7 +67,7 @@
Signaler les bogues
Comme il est impossible pour nos développeurs de tester toutes les combinaisons de matériel, ni tous les cas de figure pouvant interagir avec le système d'exploitation, nous comptons sur les utilisateurs pour nous dire si les choses fonctionnent pour eux. puisque Haiku est encore tout jeune, il est très probable que vous rencontriez des bogues. Nous vous remercions de bien vouloir prendre le temps de nous les signaler. Ensemble, nous pourrons, petit à petit, améliorer Haiku.
When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.
-Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (bt 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.
+
Lorsque les serveurs vitaux comme le serveur d'application, de registre ou d'entré plantent, vous ne verrez pas l'alerte de crash habituelle. à la place, l'écran sera nettoyé de blanc et une session gdb sera lancée, qui affichera directement ses restitutions à l'écran.
+Il se pourrait que vous soyez toujours à même de déplacer la souris, qui dessinera alors par dessus l'écran blanc de gdb. Les demandes encore en cours (comme ProcessController ou l'horloge dans la barre de Bureau) pourrait également dessiner au dessus de la sortie du débogueur à l'écran.
+Bien que tout soit plus laid et peu commode, les même fondamentaux que pour déboguer les applications s'appliquent.
+Le plus important est de fournir une trace de la pile d'appel à l'aide de la commande bt (backtrace). Mais comme vous ne serez pas en mesure de copier le texte, vous aurez besoin de prendre une photo de l'écran avec un appareil photo numérique.
Les bogues du noyau sont habituellement ceux qui ont les effets les plus graves, tout en étant les plus difficiles à déboguer. Il existe différents types de symptômes, qui révèlent généralement un problème du noyau ou d'un pilote :
-
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 "Welcome to Kernel Debugging Land...", the one above it states the immediate reason for entering KDL.
+
Le système entre en mode débogage du noyau (KDL) de lui même. La partie supérieure de l'écran est mise à blanc et plusieurs lignes de texte sont affichées.
+La seconde ligne dit « Welcome to Kernel Debugging Land… ». Celle au-dessus, précise la raison qui a déclenchée la session de débogage du noyau (KDL).
Le système redémarre spontanément.
-
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 ALTSysReqD (SysReq being PRINT on most keyboards). Wait at least a minute to see, if anything happens.
+
Le système se bloque complètement. Vous ne pouvez pas déplacer la souris et plus aucune application ne dessine quoi que se soit. Dans cette situation, un bon test consiste à essayer d'accéder au KDL via le raccourci ALTSysReqD (SysReq étant la touche Impr sur la plus part des claviers). Attendez au moins une minute, pour voir si quelque chose se passe.
Le système ne démarre pas correctement. Il peut redémarrer spontanément ou s'arrêter à un moment donné (par exemple au niveau d'une icône de l'écran de démarrage). Dans ce dernier cas vous pouvez essayer aussi ALTSysReqD.
-
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).
+
L'ensemble du système ou un élément matériel ne se comporte pas correctement. Par exemple, il pourrait être très lent, des erreurs pourraient se produisent, ou quelque chose pourrait ne pas fonctionner du tous. Si un périphérique ne fonctionne pas du tout, la première vérification évidente à faire, est de se renseigner pour savoir si il est déjà supporté par Haiku (par exemple, en posant la question sur une liste de diffusion ou un forum).
-
Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could remove the responsible Wifi driver from your Haiku installation (in /boot/system/add-ons/kernel/drivers/bin).
+
Notez que si seul le dernier point semble indiquer une relation avec le matériel, tous les autres symptômes pourraient aussi être causés par un bogue dans un pilote.
+Si vous soupçonnez un matériel ou son pilote d'être responsable du problème, vérifiez si la suppression ou la désactivation du matériel ou du pilote change quelque chose.
+Par exemple, si vous soupçonnez le Wifi, votre BIOS a peut-être une option pour le désactiver. Sinon, vous pouvez supprimer le pilote Wifi installé dans Haiku (dans /boot/system/add-ons/kernel/drivers/bin).
@@ -126,21 +130,21 @@ ne posent pas de problème, les claviers USB connecté à un controleur UHCI ne
reboot
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.
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).
+
La sortie KDL est écrite vers le port série ( si vous en avez un, un câble approprié, et un deuxième ordinateur pour vous connecter, vous pourrez capturer la sortie via un programme de terminal) et le journal système. Nottez que si vous ne pouvez pas sortir du mode de débogage du noyau, le journal ne sera pas écrit dans le fichier. Cependant, Il existe une option dans le menu de démarrage qui permet tout de même sa capture (voir ci-dessous).
This is the preferred method for gaining information from a non-booting system.
-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 /boot/common/var/log/syslog. 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).
-
The option Enable debug syslog in the boot loader's Debug menu makes the syslog somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So you have to enter the boot loader menu by holding down SHIFT while booting.
-In the boot loader's Debug menu you should now find the entries Display syslog from previous session and Save syslog from previous session. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. But again: Don't accidentally boot any operating system or the data will be lost.
+
C'est la méthode privilégiée pour obtenir des informations d'un système qui ne démarre pas. Le journal système ( « syslog » en abgégé) contient des informations précieuses sur ce qui s'est passé dans votre système, y compris les productions des sessions KDL. L'attacher au ticket « kernel » dans l'outil de suivi de bogues (Trac) est généralement une bonne pratique.
+Le journal est consigné dans le fichier /boot/common/var/log/syslog.Puisque l'écriture d'un fichier requiert un système qui fonctionne, les écritures les plus récente faites dans le journal ne peuvent pas être présentes quand un problème se produit dans le noyau (en particulier lors d'un redémarrage spontané ou d'une sessions KDL non recouvrable).
+
L'option Enable debug syslog dans le menu Debug menu du chargeur de démarrage rend le journal légèrement persistant en mémoire. Cette option est activée par défaut. « légèrement persistant » signifie qu'il résistera à une réinitialisation et qu'il sera encore accessible quand vous entrerez dans le menu du chargeur de démarrage juste après. Noter qu'amorcer un système d'exploitation (Haiku sans aucun doute, et probablement les autres) détruit cette information. Alors vous devez rentrer dans le menu du chargeur de démarrage en maintenant la touche MAJ enfoncée pendant le redémarrage.
+Dans le menu du chargeur de démarrage Debug menu, vous devriez maintenant trouver les entrés Display syslog from previous session et Save syslog from previous session. La première, affiche le journal de la session précédente à écran. La dernière vous permet de l'enregistrer dans un fichier sur disque. Notez que pour le moment seuls les volumes FAT32 sont pris en charge pour l'enregistrement du fichier. Si vous souhaitez utiliser une clé USB, mais que vous l'avez branchée trop tard de sorte qu'elle n'a pas été prise en compte, vous pouvez réinitialiser la machine et entrer à nouveau dans le menu du chargeur de démarrage. Mais encore une fois : Ne démarrer aucun système d'exploitation accidentellement ou les données seront perdues.
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.
-This is only relevant when Haiku fails to boot on your machine and the Debug syslog option doesn't work for some reason. Before the Haiku boot logo appears, hold SHIFT to enter the boot loader menu. Select Select safe mode options. Near the bottom, [ ] Enable on screen debug output 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.)
-Finally select Return to main menu and then Continue booting.
-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 Boot Loader.
+
La sortie écran du débogueur n'est utile que pour déboguer certains problèmes bien spécifiques, et est connu pour avoir des problèmes (timing). Ne l'utilisez que si vous en avez vraiment besoin.
+Ce n'est pertinent que si Haiku n'arrive pas à démarrer sur votre machine et que le Debug syslog option ne fonctionne pas pour quelque raison que ce soit. Pour accéder au menu du chargeur de démarrage, maintenez la touche MAJ enfoncée avant que le logo de Haiku n'apparaisse. Choisissez Select safe mode options. Selectionnez [ ] Enable on screen debug output que vous verrez en bas. (Notez que les autres options peuvent êtres activées pour tenter de démarrer Haiku. Si Haiku ne démarre que lorsque certaines options sont activées, n'oubliez pas de mentionner lesquelles )
+Enfin choisissez Return to main menu puis Continue booting.
+Une ou plusieurs pages de texte seront affiché à l'écran, Seules les quelques dernières lignes ont besoin de figurer dans votre rapport de bogue. Vous trouvez plus d'information dans le sujet consacré au Chargeur de démarrage.
Чтобы создать новый багрепорт, у вас должен быть заведён аккаунт в багтрекере Haiku.
Создавая новый аккаунт обязательно введите адрес электронной почты, так как на него будут приходить все сведения, связанные с изменением багрепорта. Убедитесь, что приходящие с багтрекера письма не помечаются как спам, так как это вполне возможно.
Прежде чем сообщать об ошибке, пожалуйста, убедитесь, что аналогичного багрепорта ещё не существует. Для этого также можно воспользоваться функцией поиска.
После того как вы установили, что подобных багрепортов не имеется, то оформите вашу информацию как можно точнее:
Mention which revision from SVN you are running. You can find this information in About Haiku... from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.
-
描述您所遇到的问题。尽量把问题讲得精确和明白：描述详细的系统行为反馈，和您期望的反馈。
-
描述暴露该错误所需要的操作步骤。这将会有助于开发者重现该错误，并对其进行修复和完善。
-
Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the PRINT key.
When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering bt, you create a "backtrace" that you should copy in its entirety (including the part before you entered the bt command) and attach it to the ticket.
When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.
-Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (bt 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.
Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:
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 "Welcome to Kernel Debugging Land...", the one above it states the immediate reason for entering KDL.
-
The system reboots spontaneously.
-
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 ALTSysReqD (SysReq being PRINT on most keyboards). Wait at least a minute to see, if anything happens.
-
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 ALTSysReqD.
-
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).
+
系统自动进入了内核调试状态（KDL），屏幕上方显示为白色，并且打印出几行文本。文本第二行显示为“Welcome to Kernel Debugging Land...”，而第一行则声明了进入内核调试状态的实时原因。
Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could remove the responsible Wifi driver from your Haiku installation (in /boot/system/add-ons/kernel/drivers/bin).
If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut ALTSysReqD.
-Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.
-
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:
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).
This is the preferred method for gaining information from a non-booting system.
-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 /boot/common/var/log/syslog. 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).
-
The option Enable debug syslog in the boot loader's Debug menu makes the syslog somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So you have to enter the boot loader menu by holding down SHIFT while booting.
-In the boot loader's Debug menu you should now find the entries Display syslog from previous session and Save syslog from previous session. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. But again: Don't accidentally boot any operating system or the data will be lost.
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.
-This is only relevant when Haiku fails to boot on your machine and the Debug syslog option doesn't work for some reason. Before the Haiku boot logo appears, hold SHIFT to enter the boot loader menu. Select Select safe mode options. Near the bottom, [ ] Enable on screen debug output 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.)
-Finally select Return to main menu and then Continue booting.
-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 Boot Loader.
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 above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.
-
- On screen debug output (a safe mode boot time option).
Haiku的主要系统日志，类似于引导过程中的屏幕调试信息。您可以使用 open 命令在文本编辑器中获取到系统日志中相关的部分。
+
- listimage | grep drivers/
列出所有使用的驱动。
+
- ints
只在 内核调试状态 可用（参阅下文）。它用显示中断使用情况。不可能有许多由不同硬件共享的中断。
+
- 屏幕调试输出（引导时间选项的安全模式）。
-
The first four commands are entered 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.
English
Screenshot
Appearance (Apparenza)
-
CDPlayer
-
CharacterMap
-
Commandline applications
CodyCam
-
WebPositive
-
Locale
Touchpad
TextSearch
English
放大镜
-
-
-
键盘映射
Tracker