The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not push the repository.
Zen

Translation

English type: delimited block =
In general, there is no reason to leave the default graphical installation environment unless you need to diagnose an installation problem.
0/1390 · 139

This translation is currently locked.

English Japanese Actions
Installing Using Anaconda
 
This chapter provides step-by-step instructions for installing {PRODUCT} using the [application]*Anaconda* installer. The bulk of this chapter describes installation using the graphical user interface. A text mode is also available for systems with no graphical display, but this mode is limited in certain aspects (for example, custom partitioning is not possible in text mode).
この章ではステップ・バイ・ステップで [application]*Anaconda* の使用による {PRODUCT} インストールのためのインストラクションを提供します。この章の大体はグラフィカル・モードを使ったインストール方法で説明しています。グラフィカル表示を使わずともテキストモードでも利要可能ですが、テキストモードではいくつかの側面が制約されます（例えば、カスタム・パーティショニングはテキストモードでは不可能）。
If your system does not have the ability to use the graphical mode, you can:
もしお使いのシステムにグラフィカルモードを使える性能が無いなら、下記が出来ます:
Use Kickstart to automate the installation as described in xref:advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart]
 
Perform the graphical installation remotely by connecting to the installation system from another computer with a graphical display using the _VNC_ (Virtual Network Computing) protocol - see xref:advanced/VNC_Installations.adoc#chap-vnc-installations[Installing Using VNC]
 
Introduction to Anaconda
 
The {PRODUCT} installer, [application]*Anaconda*, is different from most other operating system installation programs due to its parallel nature. Most installers follow a fixed path: you must choose your language first, then you configure network, then installation type, then partitioning, etc. There is usually only one way to proceed at any given time.
他のオペレーティングシステムのインストーラーと比べて、 {PRODUCT} インストーラー [application]*Anaconda* の独特な点は、その並列性です。大半のインストーラーは固定の経路を追います: 最初に言語を選択しなければならず、それからネットワークを設定し、そのあとインストール形式を選択し、それからパーティショニング、など。通常、手順は一個だけです。
In [application]*Anaconda* you are only required to select your language and locale first, and then you are presented with a central screen, where you can configure most aspects of the installation in any order you like. This does not apply to all parts of the installation process, however - for example, when installing from a network location, you must configure the network before you can select which packages to install.
[application]*Anaconda* では最初に言語とロケールを選択すれば、あとは中央画面にいるだけで、お好きな順序でインストールの設定をできます。ただし、インストールプロセスの全てがそうではないです。例えば、ネットワークからインストールするなら、パッケージのインストールを選択する前に、ネットワークの設定をしなければなりません。
Some screens will be automatically configured depending on your hardware and the type of media you used to start the installation. You can still change the detected settings in any screen. Screens which have not been automatically configured, and therefore require your attention before you begin the installation, are marked by an exclamation mark. You can not start the actual installation process before you finish configuring these settings.
 
Additional differences appear in certain screens; notably the custom partitioning process is very different from other Linux distributions. These differences are described in each screen's subsection.
 
Consoles and Logging During the Installation
 
The following sections describe how to access logs and an interactive shell during the installation. This is useful when troubleshooting problems, but should not be necessary in most cases.
 
Accessing Consoles
 
The {PRODUCT} installer uses the [application]*tmux* terminal multiplexer to display and control several windows you can use in addition to the main interface. Each of these windows serves a different purpose - they display several different logs, which can be used to troubleshoot any issues during the installation, and one of the windows provides an interactive shell prompt with `root` privileges, unless this prompt was specifically disabled using a boot option or a Kickstart command.
 
In general, there is no reason to leave the default graphical installation environment unless you need to diagnose an installation problem.
 
The terminal multiplexer is running in virtual console 1. To switch from the actual installation environment to [application]*tmux*, press kbd:[Ctrl + Alt + F1]. To go back to the main installation interface which runs in virtual console 6, press kbd:[Ctrl + Alt + F6].
 
If you choose text mode installation, you will start in virtual console 1 ([application]*tmux*), and switching to console 6 will open a shell prompt instead of a graphical interface.
 
The console running [application]*tmux* has 5 available windows; their contents are described in the table below, along with keyboard shortcuts used to access them. Note that the keyboard shortcuts are two-part: first press kbd:[Ctrl + b], then release both keys, and press the number key for the window you want to use.
 
You can also use kbd:[Ctrl + b] kbd:[n] and kbd:[Ctrl + b] kbd:[p] to switch to the next or previous [application]*tmux* window, respectively.
 
Available tmux Windows
 
|Shortcut|Contents
|kbd:[Ctrl + b] kbd:[1]|Main installation program window. Contains text-based prompts (during text mode installation or if you use VNC direct mode), and also some debugging information.
|kbd:[Ctrl + b] kbd:[2]|Interactive shell prompt with `root` privileges.
|kbd:[Ctrl + b] kbd:[3]|Installation log; displays messages stored in `/tmp/anaconda.log`.
|kbd:[Ctrl + b] kbd:[4]|Storage log; displays messages related storage devices from kernel and system services, stored in `/tmp/storage.log`.
|kbd:[Ctrl + b] kbd:[5]|Program log; displays messages from other system utilities, stored in `/tmp/program.log`.
 
In addition to displaying diagnostic information in [application]*tmux* windows, [application]*Anaconda* also generates several log files, which can be transferred from the installation system. These log files are described in xref:install/Troubleshooting.adoc#sect-troubleshooting-log-files[Log Files Generated During the Installation], and directions for transferring them from the installation system are available in xref:install/Troubleshooting.adoc#sect-troubleshooting-transferring-logs[Transferring Log Files from the Installation System].
 
Saving Screenshots
 
You can press kbd:[Shift + Print Screen] at any time during the graphical installation to capture the current screen. These screenshots are saved to `/tmp/anaconda-screenshots`.
 
Additionally, you can use the [command]#autostep --autoscreenshot# command in a Kickstart file to capture and save each step of the installation automatically. See xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-autostep[autostep (optional) - Go Through Every Screen] for details.
 
Installing in Text Mode
 
Text mode installation offers an interactive, non-graphical interface for installing {PRODUCT}. This may be useful on systems with no graphical capabilities; however, you should always consider the available alternatives before starting a text-based installation. Text mode is limited in the amount of choices you can make during the installation.
 
To start a text mode installation, boot the installation with the [option]#inst.text# boot option used either at the boot command line in the boot menu, or in your PXE server configuration. See xref:install/Booting_the_Installation.adoc#chap-booting-the-installation[Booting the Installation] for information about booting and using boot options.
 
There are two alternatives to text mode which can both be used even if the installation system does not have a graphical display. You can either connect to the installation system using VNC and perform an interactive graphical installation remotely (see xref:advanced/VNC_Installations.adoc#chap-vnc-installations[Installing Using VNC]), or you can create a Kickstart file to perform the installation automatically (see xref:advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart]).
 
Text Mode Installation
 
User avatar anonymous

Suggestion added

一般に、インストールの問題を診断する必要でもない限り、グラフィカル・インストールから離れる必要はないです。

Suggested change:

一般に、インストールの問題を診断する必要でもない限り、グラフィカル・インストールから離れる必要はないです。
2 years ago

Loading…

User avatar None

Suggestion added
In general, there is no reason to leave the default graphical installation environment unless you need to diagnose an installation problem.
一般に、インストールの問題を診断する必要でもない限り、グラフィカル・インストールから離れる必要はないです。
2 years ago
User avatar sujiniku

Translation changed
In general, there is no reason to leave the default graphical installation environment unless you need to diagnose an installation problem.
一般に、インストールの問題を診断する必要でもない限り、グラフィカル・インストールから離れる必要はないです。
2 years ago
User avatar sujiniku

Translation added
In general, there is no reason to leave the default graphical installation environment unless you need to diagnose an installation problem.
一般に、インストールの問題を診断する必要でもない限り、グラフィカル・インストールから離れる必要はないです。
2 years ago
Browse all string changes

Things to check

Suggestions

There is 1 suggestion for this string.

View

Has been translated

Previous translation was "一般に、インストールの問題を診断する必要でもない限り、グラフィカル・インストールから離れる必要はないです。".

Fix string

Reset

Glossary

English Japanese
No related strings found in the glossary.

7944494 String information

Source string description
type: delimited block =
Source string location
./pages/install/Installing_Using_Anaconda.adoc:41
String age
3 years ago
Last updated
a year ago
Source string age
3 years ago
Translation file
po/ja/f34/pages/install/Installing_Using_Anaconda.po, string 15