clearlinux/clear-linux-documentation
2
0
Fork 0
mirror of https://github.com/clearlinux/clear-linux-documentation.git synced 2026-08-21 06:36:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

Initial commit for .po file reconcile

Browse Source 
- remove locale de
- re org zh_CN content to match .rst structure/org

Signed-off-by: Kristal Dale <kristal.dale@intel.com>
This commit is contained in:
Kristal Dale
2019-08-09 09:19:34 -07:00
parent 21f2cd5e6f
commit 22f164cb4d
249 changed files with 859 additions and 37539 deletions
Download Patch File Download Diff File Expand all files Collapse all files
locale/de/LC_MESSAGES/FAQ/faq.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/concepts/autospec-about.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/concepts/autospec-about.po
-223
View File
@@ -1,223 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-12 12:18-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../concepts/autospec-about.rst:4
msgid "Autospec"
msgstr ""
#: ../../concepts/autospec-about.rst:6
msgid ""
"``autospec`` is a tool to assist in the automated creation and "
"maintenance of RPM packaging in |CL-ATTR|. Where a standard RPM build "
"process using ``rpmbuild`` requires a tarball and .spec file to start, "
"``autospec`` requires only a tarball and package name to start."
msgstr ""
"``autospec`` ist ein Werkzeug zur automatisierten Erstellung und Pflege von RPM-Verpackungen in |CL-ATTR| zu unterstützen. Ein Standard-RPM Build-Prozess"
"unter Verwendung von ``rpmbuild`` erfordert einen Tarball und .spec Datei zu "
"begginen. Vergleichsweise, ``autospec`` erfordert nur einen Tarball und "
"Paketnamen um zu starten."
#: ../../concepts/autospec-about.rst:12
msgid "How autospec works"
msgstr "Wie autospec functioniert"
#: ../../concepts/autospec-about.rst:14
msgid ""
"``autospec`` attempts to infer the requirements of the .spec file by "
"analyzing the source code and :file:`Makefile` information. It will "
"continuously run updated builds based on new information discovered from "
"build failures until it has a complete and valid .spec file. Although not"
" required, you can influence the behavior of ``autospec`` by providing "
":ref:`control files <control-files>`."
msgstr ""
#: ../../concepts/autospec-about.rst:20
msgid "The basic process is described in the following steps:"
msgstr ""
#: ../../concepts/autospec-about.rst:22
msgid ""
"The :command:`make autospec` command generates a .spec based on analysis "
"of code and control files, if present."
msgstr ""
#: ../../concepts/autospec-about.rst:25
msgid "``autospec`` creates a ``build root`` with ``mock`` config."
msgstr ""
#: ../../concepts/autospec-about.rst:27
msgid "``autospec`` attempts to build an RPM from the generated .spec."
msgstr ""
#: ../../concepts/autospec-about.rst:29
msgid "``autospec`` detects any missed declarations in the .spec."
msgstr ""
#: ../../concepts/autospec-about.rst:31
msgid ""
"If build errors occur, ``autospec`` will scan the build log to try and "
"detect the root cause."
msgstr ""
#: ../../concepts/autospec-about.rst:34
msgid ""
"If ``autospec`` detects the root cause and knows how to continue, it will"
" restart the build automatically at step 1 with updated build "
"instructions."
msgstr ""
#: ../../concepts/autospec-about.rst:37
msgid ""
"Otherwise, ``autospec`` will stop the build for user inspection and "
"editing of control files to resolve the errors. The user resumes the "
"process at step 1 after errors are resolved."
msgstr ""
#: ../../concepts/autospec-about.rst:40
msgid ""
"Following these steps, ``autospec`` continues to rebuild the package, "
"based on new information discovered from build failures, until it has a "
"valid .spec. If no build errors occur, RPM packages are successfully "
"built."
msgstr ""
#: ../../concepts/autospec-about.rst:47
msgid "Control files"
msgstr ""
#: ../../concepts/autospec-about.rst:49
msgid ""
"It is possible to influence the behavior of ``autospec`` by providing "
"control files. These files may be used to alter the default behavior of "
"the configure routine, to blacklist build dependencies, etc. Control "
"files must be located in the same directory as the resulting .spec."
msgstr ""
#: ../../concepts/autospec-about.rst:54
msgid "Table 1 shows control files used to control dependencies, for example."
msgstr ""
#: ../../concepts/autospec-about.rst:56
msgid "**Table 1. Control files to control dependencies**"
msgstr ""
#: ../../concepts/autospec-about.rst:60
msgid "Filename"
msgstr ""
#: ../../concepts/autospec-about.rst:61
msgid "Description"
msgstr ""
#: ../../concepts/autospec-about.rst:62
msgid "buildreq_add"
msgstr ""
#: ../../concepts/autospec-about.rst:63
msgid ""
"Each line in the file provides the name of a package to add as a build "
"dependency to the .spec."
msgstr ""
#: ../../concepts/autospec-about.rst:65
msgid "buildreq_ban"
msgstr ""
#: ../../concepts/autospec-about.rst:66
msgid ""
"Each line in the file is a build dependency that under no circumstance "
"should be automatically added to the build dependencies. This is useful "
"to block automatic configuration routines adding undesired functionality,"
" or to omit any automatically discovered dependencies during tarball "
"scanning."
msgstr ""
#: ../../concepts/autospec-about.rst:71
msgid "pkgconfig_add"
msgstr ""
#: ../../concepts/autospec-about.rst:72
msgid ""
"Each line in the file is assumed to be a pkgconfig() build dependency. "
"Add the pkg-config names here, as ``autospec`` will automatically "
"transform the names into their ``pkgconfig($name)`` style when generating"
" the .spec."
msgstr ""
#: ../../concepts/autospec-about.rst:76
msgid "pkgconfig_ban"
msgstr ""
#: ../../concepts/autospec-about.rst:77
msgid ""
"Each line in this file is a pkgconfig() build dependency that should not "
"be added automatically to the build, much the same as `` buildreq_ban``. "
"As with ``pkgconfig_add``, these names are automatically transformed by "
"``autospec`` into their correct ``pkgconfig($name))`` style."
msgstr ""
#: ../../concepts/autospec-about.rst:82
msgid "requires_add"
msgstr ""
#: ../../concepts/autospec-about.rst:83
msgid ""
"Each line in the file provides the name of a package to add as a runtime "
"dependency to the .spec."
msgstr ""
#: ../../concepts/autospec-about.rst:85
msgid "requires_ban"
msgstr ""
#: ../../concepts/autospec-about.rst:86
msgid ""
"Each line in the file is a runtime dependency that under no circumstance "
"should be automatically added to the runtime dependencies. This is useful"
" to block automatic configuration routines adding undesired "
"functionality, or to omit any automatically discovered dependencies "
"during tarball scanning."
msgstr ""
#: ../../concepts/autospec-about.rst:92
msgid ""
"Further control of the build can be achieved through the use of the "
"``options.conf`` file. If this file does not exist, it is created by "
"``autospec`` with default values. If certain deprecated configuration "
"files exists ``autospec`` will use the value indicated by those files and"
" remove them."
msgstr ""
#: ../../concepts/autospec-about.rst:98
msgid "For a comprehensive list of control files, view the `autospec readme`_."
msgstr ""
#: ../../concepts/autospec-about.rst:101
msgid "Related topics"
msgstr ""
#: ../../concepts/autospec-about.rst:103
msgid ":ref:`autospec`"
msgstr ""
#: ../../concepts/autospec-about.rst:104
msgid ":ref:`mixer`"
msgstr ""
locale/de/LC_MESSAGES/concepts/bundles-about.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/concepts/mixer-about.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/concepts/mixer-about.po
-115
View File
@@ -1,115 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-12 12:18-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../concepts/mixer-about.rst:4
msgid "Mixer"
msgstr ""
#: ../../concepts/mixer-about.rst:6
msgid ""
"|CL-ATTR| is a powerful, modular, and customizable OS. Upstream |CL| "
"offers many images to support different environments and use-cases. "
"There are hundreds of bundles that will meet most, if not all, of your OS"
" and software needs."
msgstr ""
#: ../../concepts/mixer-about.rst:11
msgid ""
"However, if you need additional customization or content, |CL| provides "
"the mixer tool. Depending on your needs, the mixer tool allows you to:"
msgstr ""
#: ../../concepts/mixer-about.rst:15
msgid ":ref:`create-mix` to create a distinct derivative of the |CL| that"
msgstr ""
#: ../../concepts/mixer-about.rst:15
msgid "contains your custom software."
msgstr ""
#: ../../concepts/mixer-about.rst:20
msgid "Create a mix"
msgstr ""
#: ../../concepts/mixer-about.rst:22
msgid "When creating a mix, you can"
msgstr ""
#: ../../concepts/mixer-about.rst:24
msgid "Use any existing upstream bundles with no modification."
msgstr ""
#: ../../concepts/mixer-about.rst:25
msgid "Redefine what goes into existing bundles."
msgstr ""
#: ../../concepts/mixer-about.rst:26
msgid "Create completely new, custom bundles with your own custom packages."
msgstr ""
#: ../../concepts/mixer-about.rst:28
msgid ""
"With mixer you are not required to incorporate every upstream release "
"into your mix. You decide which upstream versions to update your "
"derivative to, as illustrated in Figure 1."
msgstr ""
#: ../../concepts/mixer-about.rst:36
msgid ""
"Figure 1: With a custom mix, you add your custom bundle and decide which "
"upstream versions to update your mix to, on your own release cycle."
msgstr ""
#: ../../concepts/mixer-about.rst:39
msgid ""
"Creating your own mix forks away from the |CL| upstream and requires that"
" you act as your own OSV. There is a greater level of responsibility, "
"requiring more infrastructure and processes to adopt. However, with this "
"approach, you have a higher degree of control and customization of your "
"custom |CL|."
msgstr ""
#: ../../concepts/mixer-about.rst:45
msgid "Related topics"
msgstr ""
#: ../../concepts/mixer-about.rst:47
msgid ""
"|CL| provides flexibility in how you customize your OS. Learn more about "
"mixer and related topics to decide which customization approach is best "
"for you."
msgstr ""
#: ../../concepts/mixer-about.rst:51
msgid ":ref:`mixer`"
msgstr ""
#: ../../concepts/mixer-about.rst:52
msgid ":ref:`bundles-about`"
msgstr ""
#: ../../concepts/mixer-about.rst:53
msgid ":ref:`swupd-about`"
msgstr ""
#: ../../concepts/mixer-about.rst:54
msgid ":ref:`deploy-at-scale`"
msgstr ""
locale/de/LC_MESSAGES/concepts/restart.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/concepts/restart.po
-301
View File
@@ -1,301 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-12 12:18-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../concepts/restart.rst:4
msgid "Restart system services after an OS update"
msgstr ""
#: ../../concepts/restart.rst:6
msgid ""
"The software life cycle describes how software is created, developed, and"
" deployed, and includes how to replace or update software. A good OS "
"provides tools for the entire software life cycle. These tools must "
"include ways to remove software components properly when replaced with "
"something else."
msgstr ""
#: ../../concepts/restart.rst:12
msgid ""
"Most of the work on software update code in |CL| was focused on adding "
"new software to the system. We recommended that users reboot their system"
" once in a while, but we did not provide any tools to restart services "
"easily, until now."
msgstr ""
#: ../../concepts/restart.rst:18
msgid "User challenges"
msgstr ""
#: ../../concepts/restart.rst:20
msgid ""
"It is difficult to determine which services to restart. You can either "
"evaluate each system and reboot manually, or figure out which services to"
" restart based on documentation like the |CL| release notes. Since "
"neither option solves the issue completely, the |CL| team created a "
"solution."
msgstr ""
#: ../../concepts/restart.rst:25
msgid ""
"Over the years, several OSes approached the problem and created partial "
"solutions such as the following:"
msgstr ""
#: ../../concepts/restart.rst:28
msgid "Automatically restart services during an upgrade."
msgstr ""
#: ../../concepts/restart.rst:29
msgid "Evaluate services using these steps:"
msgstr ""
#: ../../concepts/restart.rst:31
msgid "Mark updates requiring a reboot, such as kernel updates."
msgstr ""
#: ../../concepts/restart.rst:32
msgid "Inform the user of those updates."
msgstr ""
#: ../../concepts/restart.rst:33
msgid "Ask the user to restart the OS."
msgstr ""
#: ../../concepts/restart.rst:35
msgid ""
"Both solutions are acceptable for many OSes. However, |CL| updates "
"software automatically and users do not see notices from the updater "
"unless they review the journal. |CL| requires a completely different "
"solution, with the following requirements:"
msgstr ""
#: ../../concepts/restart.rst:40
msgid ""
"Eliminate the guesswork about what to restart and under what "
"circumstances."
msgstr ""
#: ../../concepts/restart.rst:41
msgid ""
"Cannot restart everything. Many service daemons do not support an "
"automatic background restart."
msgstr ""
#: ../../concepts/restart.rst:43
msgid "Fit into the |CL| architectural perspective: be small, quick, and lean."
msgstr ""
#: ../../concepts/restart.rst:46
msgid "clr-service-restart functionality"
msgstr ""
#: ../../concepts/restart.rst:48
msgid "Typical reasons to restart a service daemon include:"
msgstr ""
#: ../../concepts/restart.rst:50
msgid "A new version replaces the executable file itself."
msgstr ""
#: ../../concepts/restart.rst:51
msgid "A new version replaces a library component used by a service daemon."
msgstr ""
#: ../../concepts/restart.rst:53
msgid ""
"Our method restarts daemons when it is really needed, especially in the "
"case of security updates. The tool restarts daemons by reading various "
"files in the :file:`procfs` filesystem provided by the kernel."
msgstr ""
#: ../../concepts/restart.rst:57
msgid ""
"The second part of the problem is to determine whether or not running "
"processes are part of a system service. The tool focuses on system "
"services because most system services are background tasks with no direct"
" user interaction. Fortunately, :command:`systemd` provides a simple way "
"to:"
msgstr ""
#: ../../concepts/restart.rst:62
msgid "Determine which active tasks are within the system domain."
msgstr ""
#: ../../concepts/restart.rst:63
msgid "Determine which tasks map to which service."
msgstr ""
#: ../../concepts/restart.rst:65
msgid ""
"We combined both solutions into a low-overhead tool that shows which "
"system daemons require a restart, as shown below:"
msgstr ""
#: ../../concepts/restart.rst:68
msgid "Figure 1: Invoke :command:`clr-service-restart`."
msgstr ""
#: ../../concepts/restart.rst:83
msgid ""
":command:`clr-service-restart` implements a whitelist to identify which "
"daemons can be restarted. The system administrator can customize the "
"default |CL| OS whitelist using *allow* or *disallow* options for "
"restarting system services. When a software update occurs, :command:`clr-"
"service-restart` consults the whitelist to see if a service daemon is "
"allowed to be restarted or not. See the options section for details."
msgstr ""
#: ../../concepts/restart.rst:93
msgid "Options for clr-service-restart"
msgstr ""
#: ../../concepts/restart.rst:95
msgid ""
"The *allow* option identifies a daemon to restart after an OS software "
"update. The :command:`clr-service-restart` daemon creates a symlink in "
":file:`/etc/clr-service-restart` as a record. The example below tells "
":command:`clr-service-restart` to restart the *tallow* daemon after an OS"
" software update."
msgstr ""
#: ../../concepts/restart.rst:105
msgid ""
"The *disallow* option tells :command:`clr-service-restart` not to restart"
" the specified daemon even if the OS defaults permit the daemon to be "
"restarted. The :command:`clr-service-restart` daemon creates a symlink in"
" :file:`/etc/clr-service-restart` that points to :file:`/dev/null` as a "
"record. The example below tells :command:`clr-service-restart` not to "
"restart the *rngd* daemon after an OS software update."
msgstr ""
#: ../../concepts/restart.rst:116
msgid ""
"The *default* option makes :command:`clr-service-restart` revert back to "
"the OS defaults and delete any symlink in :file:`/etc/clr-service-"
"restart`. The example below tells :command:`clr-service-restart` to "
"restart *rngd* automatically again, because *rngd* is whitelisted for "
"automatic service restarts by default in |CL|."
msgstr ""
#: ../../concepts/restart.rst:128
msgid "Monitor options for clr-service-restart"
msgstr ""
#: ../../concepts/restart.rst:130
msgid ""
":command:`clr-service-restart` works in the background and is invoked "
"with :command:`swupd` automatically. Review the journal output to verify "
"that services are restarted after an OS software update."
msgstr ""
#: ../../concepts/restart.rst:134
msgid ""
"To monitor :command:`clr-service-restart`, use one or both options "
"described below."
msgstr ""
#: ../../concepts/restart.rst:139
msgid ""
"This option makes :command:`clr-service-restart` perform no restarts. "
"Instead it displays the services that could potentially be restarted. "
"When used, :command:`clr-service-restart` outputs a list of messages "
"showing:"
msgstr ""
#: ../../concepts/restart.rst:144
msgid "Which service needs a restart."
msgstr ""
#: ../../concepts/restart.rst:145
msgid "What unit it is."
msgstr ""
#: ../../concepts/restart.rst:146
msgid "Why it needs a restart."
msgstr ""
#: ../../concepts/restart.rst:147
msgid "Which command is required to restart the unit."
msgstr ""
#: ../../concepts/restart.rst:151
msgid ""
"This option makes :command:`clr-service-restart` consider all system "
"services, not only the ones that are whitelisted. Because the default "
"whitelist in |CL| is relatively short, you can use this option to restart"
" all impacted services when you log in on the system."
msgstr ""
#: ../../concepts/restart.rst:156
msgid ""
"If you pass both options (:option:`-a` and :option:`-n`), :command:`clr-"
"service-restart` displays a complete list of system services that require"
" a restart. Use both options to verify that all desired daemons are "
"restarted."
msgstr ""
#: ../../concepts/restart.rst:163
msgid "Telemetry"
msgstr ""
#: ../../concepts/restart.rst:165
msgid ""
":command:`clr-service-restart` may cause problems such as a short service"
" outage when a daemon is being restarted, or if a daemon fails to "
"properly restart. To minimize issues, :command:`clr-service-restart` "
"creates a telemetry record and sends it to the optional |CL| telemetry "
"service if both conditions below are met:"
msgstr ""
#: ../../concepts/restart.rst:171
msgid "If a unit fails to automatically restart after an OS update."
msgstr ""
#: ../../concepts/restart.rst:172
msgid ""
"If that unit resides in the system location "
":file:`/usr/lib/systemd/system`."
msgstr ""
#: ../../concepts/restart.rst:175
msgid ""
"If you do not install the |CL| telemetrics bundle, the data is discarded."
" If you install the telemetrics bundle and you opt to send telemetry, "
"then the system unit name is sent to the |CL| telemetry service. We "
"evaluate the report and update the whitelist to remove services that are "
"not safe to restart."
msgstr ""
#: ../../concepts/restart.rst:182
msgid "Conclusion"
msgstr ""
#: ../../concepts/restart.rst:184
msgid ""
"The |CL| team enjoys coming up with simple and efficient solutions to "
"make your work easier. We made a github project of :command:`clr-service-"
"restart` and we invite you to look at the code, share your thoughts, and "
"work with us on improving the project. You can find the project at:"
msgstr ""
#: ../../concepts/restart.rst:189
msgid "https://github.com/clearlinux/clr-service-restart"
msgstr ""
locale/de/LC_MESSAGES/concepts/security.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/concepts/security.po
-249
View File
@@ -1,249 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-12 12:18-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../concepts/security.rst:4
msgid "OS Security"
msgstr ""
#: ../../concepts/security.rst:6
msgid ""
"|CL-ATTR| aims to make systemic and layered security-conscious decisions "
"that are both performant and practical. This security philosophy is "
"rooted within the project's codebase and operating culture."
msgstr ""
#: ../../concepts/security.rst:17
msgid "Security in Updates"
msgstr ""
#: ../../concepts/security.rst:19
msgid ""
"The |CL| team believes in the benefits of software security through open "
"sourcing, incremental updates, and rapidly resolving known security "
"advisories."
msgstr ""
#: ../../concepts/security.rst:26
msgid "The latest Linux* codebase"
msgstr ""
#: ../../concepts/security.rst:28
msgid ""
"|CL| uses the newest version of the Linux kernel which allows the "
"operating system to leverage the latest features from the upstream Linux "
"kernel, including security fixes."
msgstr ""
#: ../../concepts/security.rst:36
msgid "Automated Effective Updating"
msgstr ""
#: ../../concepts/security.rst:38
msgid "|CL| is incrementally updated multiple times per day."
msgstr ""
#: ../../concepts/security.rst:40
msgid ""
"This `rolling release model`_ allows |CL| to consume the latest security "
"fixes of software packages as soon as they become available. There is no "
"waiting for major or minor releases on |CL|."
msgstr ""
#: ../../concepts/security.rst:44
msgid ""
"An update is not effective if it is just simply downloaded onto a system."
" It needs to be obtained *AND* ensured that the new patched copy is being"
" used; not an older copy loaded into memory. |CL| will let you know when "
"a service needs to be rebooted or do it for your automatically after a "
"software update, if desired."
msgstr ""
#: ../../concepts/security.rst:51
msgid ""
"In |CL| updates are delivered automatically, efficiently, and "
"effectively. For more information see `documentation about Software "
"Updates`_ in |CL|."
msgstr ""
#: ../../concepts/security.rst:60
msgid "Automated CVE Scanning and Remediation"
msgstr ""
#: ../../concepts/security.rst:62
msgid ""
"The sheer number of software packages and security vulnerabilities is "
"growing exponentially. Repositories of Common Vulnerabilities and "
"Exposures (CVEs) and their fixes, if known, are published by :abbr:`NIST`"
" in a National Vulnerability Database \\ |NVD|\\ and at \\ |MITRE|\\ ."
msgstr ""
#: ../../concepts/security.rst:68
msgid ""
"|CL| employs a proactive and measured approach to addressing known and "
"fixable :abbr:`CVEs (Common Vulnerabilities and Exposures)`. Packages are"
" automatically scanned against :abbr:`CVEs (Common Vulnerabilities and "
"Exposures)` daily, and security patches are deployed as soon as they are "
"available."
msgstr ""
#: ../../concepts/security.rst:74
msgid ""
"These combined practices minimize the amount of time |CL| systems are "
"exposed to unnecessary security risk."
msgstr ""
#: ../../concepts/security.rst:82
msgid "Security in Software"
msgstr ""
#: ../../concepts/security.rst:86
msgid "Minimized attack surface"
msgstr ""
#: ../../concepts/security.rst:88
msgid ""
"|CL| removes legacy, unneeded, or redundant standards and components as "
"much as possible to enable the use of best known security standards. "
"Below are some examples:"
msgstr ""
#: ../../concepts/security.rst:92
msgid ""
"`RC4`, `SSLv3`, `3DES`, and `SHA-1` ciphers which have had known "
"vulnerabilities, have been explicitly disabled within many |CL| packages "
"to avoid their accidental usage."
msgstr ""
#: ../../concepts/security.rst:96
msgid ""
"Services and subsystems which expose sensitive system information have "
"been removed such as the `finger` and `tcpwrappers`."
msgstr ""
#: ../../concepts/security.rst:99
msgid "`SFTP` has been disabled by default due to security considerations."
msgstr ""
#: ../../concepts/security.rst:104
msgid "Verified trust"
msgstr ""
#: ../../concepts/security.rst:106
msgid ""
"|CL| encourages the use of secure practices such as encryption and "
"digital signature verification throughout the system and discourages "
"blind trust. Below are some examples:"
msgstr ""
#: ../../concepts/security.rst:110
msgid ""
"All update operations from swupd are transparently encrypted and checked "
"against the |CL| maintainers' public key for authenticity. More "
"information can be found in this blog post: `blog post about swupd "
"security`_"
msgstr ""
#: ../../concepts/security.rst:115
msgid ""
"Before being built, packages available from |CL| verify checksums and "
"signatures provided by third party project codebases and maintainers."
msgstr ""
#: ../../concepts/security.rst:118
msgid ""
"|CL| features a unified certificate store, `clrtrust`_ which comes ready "
"to work with well-known Certificate Authorities out of the box. "
"`clrtrust`_ also offers an easy to use command line interface for "
"managing system-wide chains of trust, instead of ignoring foreign "
"certificates."
msgstr ""
#: ../../concepts/security.rst:129
msgid "Compiled with secure options"
msgstr ""
#: ../../concepts/security.rst:131
msgid ""
"While |CL| packages are optimized for performance on Intel® architecture,"
" security conscious kernel and compiler options are sensibly taken "
"advantage of. Below are some examples:"
msgstr ""
#: ../../concepts/security.rst:136
msgid ""
"Kernels shipped with |CL| are signed and disallow the usage of custom "
"kernel modules to maintain verifiable system integrity."
msgstr ""
#: ../../concepts/security.rst:139
msgid ""
"`Address space layout randomization (ASLR)`_ and `Kernel address space "
"layout randomization (KASLR)`_ are kernel features which defend against "
"certain memory based attacks. More information can be found in a `blog "
"post about PIE executables`_ ."
msgstr ""
#: ../../concepts/security.rst:150
msgid "Security in System Design"
msgstr ""
#: ../../concepts/security.rst:152
msgid ""
"Simple, yet effective, techniques are used throughout the |CL| system "
"design to defend against common attack vectors and enable good security "
"hygiene. Below are some examples:"
msgstr ""
#: ../../concepts/security.rst:157
msgid ""
"Full disk encryption using `Linux Unified Key Setup`_ (LUKS) is "
"available during installation."
msgstr ""
#: ../../concepts/security.rst:160
msgid ""
"|CL| uses the PAM cracklib module to harden user login and password "
"security resulting in:"
msgstr ""
#: ../../concepts/security.rst:163
msgid ""
"No default username or root password set out of the box with |CL|, you "
"will be asked to set your own password immediately."
msgstr ""
#: ../../concepts/security.rst:166
msgid ""
"Simple password schemes, which are known to be easily compromised, cannot"
" be set in |CL|."
msgstr ""
#: ../../concepts/security.rst:169
msgid ""
"A password blacklist, to avoid system passwords being set to passwords "
"which have been compromised in the past."
msgstr ""
#: ../../concepts/security.rst:172
msgid ""
"`Tallow`_, a lightweight service which monitors and blocks suspicious SSH"
" login patterns, is installed with the :command:`openssh-server` bundle."
msgstr ""
locale/de/LC_MESSAGES/concepts/stateless.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/concepts/stateless.po
-202
View File
@@ -1,202 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-12 12:18-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../concepts/stateless.rst:4
msgid "Stateless"
msgstr ""
#: ../../concepts/stateless.rst:6
msgid ""
"In most operating systems, files can become intermingled with user and "
"system data and configurations."
msgstr ""
#: ../../concepts/stateless.rst:14
msgid ""
"Figure 1: Without stateless, user and system files become mixed on the "
"filesystem over time."
msgstr ""
#: ../../concepts/stateless.rst:16
msgid ""
"|CL-ATTR| has a stateless design philosophy of which the goal is to "
"provide an :abbr:`OS (operating system)` that functions without excessive"
" user configuration or customization. Stateless in this context does "
"*not* mean ephemeral or non-persistent."
msgstr ""
#: ../../concepts/stateless.rst:26
msgid "File-level separation"
msgstr ""
#: ../../concepts/stateless.rst:28
msgid ""
"To accomplish a stateless design the Linux Filesystem Hierarchy is "
"separated between user-owned areas and |CL|-owned areas."
msgstr ""
#: ../../concepts/stateless.rst:36
msgid ""
"Figure 2: With stateless, user and system files are separated on the "
"filesystem."
msgstr ""
#: ../../concepts/stateless.rst:39
msgid "System areas"
msgstr ""
#: ../../concepts/stateless.rst:40
msgid ""
"File under the :file:`/usr` directory are managed by |CL| as system "
"files. Files written under the :file:`/usr` directory by users can get "
"removed through system updates with :ref:`swupd <swupd-about>`.This "
"operating assumption allows |CL| to verify and maintain integrity of "
"system files."
msgstr ""
#: ../../concepts/stateless.rst:46
msgid "User areas"
msgstr ""
#: ../../concepts/stateless.rst:47
msgid ""
"Files under the :file:`/etc/`, :file:`/home`, and :file:`/var` "
"directories are owned and managed by the user. A freshly installed |CL| "
"system will only have a minimal set of files in the :file:`/etc/` "
"directory and software installed by |CL| does not write to :file:`/etc`. "
"This operating assumption allows |CL| users to clearly identify the "
"configuration that makes their system unique."
msgstr ""
#: ../../concepts/stateless.rst:55
msgid "Software Configuration"
msgstr ""
#: ../../concepts/stateless.rst:57
msgid ""
"With stateless separation, default software configurations are read in "
"order from predefined source code, |CL| provided defaults, and user-"
"provided configuration."
msgstr ""
#: ../../concepts/stateless.rst:62
msgid "Default configurations"
msgstr ""
#: ../../concepts/stateless.rst:64
msgid ""
"Software in |CL| provides default configuration values so that it is "
"immediately functional, whenever it is appropriate to do so."
msgstr ""
#: ../../concepts/stateless.rst:67
msgid ""
"|CL| distributed software packages may be directly modified to include "
"default configuration values or default configuration files may be "
"provided by |CL| under :file:`/usr/share/defaults`. These files can be "
"referenced as templates for customization."
msgstr ""
#: ../../concepts/stateless.rst:72
msgid ""
"For example, the default configuration that Apache uses when installed "
"can be found at :file:`/usr/share/defaults/httpd/httpd.conf` directory."
msgstr ""
#: ../../concepts/stateless.rst:77
msgid "Overriding configurations"
msgstr ""
#: ../../concepts/stateless.rst:79
msgid ""
"If a configuration needs to be changed, the appropriate file should be "
"modified by the user under :file:`/etc/`. If the configuration file does "
"not already exist, it can be created in the appropriate location."
msgstr ""
#: ../../concepts/stateless.rst:83
msgid ""
"User defined configuration files should contain the minimal set of "
"desired changes and rely on default configuration for the rest."
msgstr ""
#: ../../concepts/stateless.rst:86
msgid "For example, a customized Apache configuration can be used instead by:"
msgstr ""
#: ../../concepts/stateless.rst:88
msgid "Create the destination directory for the configuration:"
msgstr ""
#: ../../concepts/stateless.rst:94
msgid "Copy the default configuration as a reference template:"
msgstr ""
#: ../../concepts/stateless.rst:100
msgid "Make any desired modifications to the configurations:"
msgstr ""
#: ../../concepts/stateless.rst:106
msgid "Reload the service or reboot the system to pickup any changes:"
msgstr ""
#: ../../concepts/stateless.rst:113
msgid ""
"This pattern can be used to modify the configurations of other programs "
"too. The `stateless man page`_ has application-specific examples."
msgstr ""
#: ../../concepts/stateless.rst:118
msgid "System reset"
msgstr ""
#: ../../concepts/stateless.rst:120
msgid ""
"Once advantage of the stateless design is that the system defaults can be"
" easily restored by simply deleting everything under :file:`/etc/` and "
":file:`/var`."
msgstr ""
#: ../../concepts/stateless.rst:124
msgid ""
"Running the commands below effectively performs a system reset as if it "
"was just installed:"
msgstr ""
#: ../../concepts/stateless.rst:132
msgid ""
"In other Linux distributions, this can be a catastrophic action that "
"renders a system unable to boot."
msgstr ""
#: ../../concepts/stateless.rst:136
msgid "Additional information"
msgstr ""
#: ../../concepts/stateless.rst:138
msgid "`stateless man page`_"
msgstr ""
#: ../../concepts/stateless.rst:140
msgid ""
"`Where is /etc/fstab in Clear Linux? <https://clearlinux.org/news-blogs"
"/where-etcfstab-clear-linux>`_"
msgstr ""
locale/de/LC_MESSAGES/concepts/swupd-about.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/concepts/swupd-about.po
-193
View File
@@ -1,193 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-12 12:18-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../concepts/swupd-about.rst:4
msgid "swupd: software updater"
msgstr ""
#: ../../concepts/swupd-about.rst:6
msgid ""
":command:`swupd` is an operating system software manager and update "
"program that operates at a file-level to enable verifiable integrity and "
"update efficiency."
msgstr ""
#: ../../concepts/swupd-about.rst:10
msgid "Visit the `swupd man page`_ for more details."
msgstr ""
#: ../../concepts/swupd-about.rst:13
msgid "Versioning"
msgstr ""
#: ../../concepts/swupd-about.rst:15
msgid ""
"Using package managers to keep track of software version compatibility or"
" compare multiple systems on many Linux distributions can be cumbersome."
msgstr ""
#: ../../concepts/swupd-about.rst:17
msgid ""
"With |CL| :command:`swupd`, versioning happens at the individual file-"
"level. This means |CL| generates an entirely new OS version with any set "
"of software changes to the system (including software downgrades or "
"removals). This rolling release versioning model is similar to "
":command:`git` internal version tracking, where any of the individual "
"file commits are tracked and move the pointer forward when changed."
msgstr ""
#: ../../concepts/swupd-about.rst:23
msgid ""
"While administrators can pick and choose which `bundles`_ a system has "
"installed, a single |CL| version number strictly represents one "
"combination of all software versions that can be installed onto a system "
"of that |CL| version. This method of whole OS versioning offers unique "
"advantages. Namely, system administrators can quickly compare multiple "
"|CL| systems that share the same version for important software and "
"security fixes."
msgstr ""
#: ../../concepts/swupd-about.rst:31
msgid "Updating"
msgstr ""
#: ../../concepts/swupd-about.rst:33
msgid ""
"|CL| promotes regular and automated updating of software to ensure "
"integration of new enhancements and security fixes. Refer to "
":ref:`security` documentation for more information."
msgstr ""
#: ../../concepts/swupd-about.rst:37
msgid "Learn how to update your system using :ref:`swupd <swupd-guide>`."
msgstr ""
#: ../../concepts/swupd-about.rst:40
msgid "Update efficiency"
msgstr ""
#: ../../concepts/swupd-about.rst:42
msgid ""
"Because :command:`swupd` operates at the individual file-level instead of"
" a package-level, |CL| updates are small and fast."
msgstr ""
#: ../../concepts/swupd-about.rst:45
msgid ""
"On many Linux\\* distributions, updates to a particular software package "
"require the whole software package to be downloaded and replaced --even "
"for one line of code."
msgstr ""
#: ../../concepts/swupd-about.rst:49
msgid ""
"In |CL|, updates are generated using the :ref:`mixer <mixer-about>` tool."
" Mixer calculates the difference between two |CL| versions and makes "
"available *binary deltas*, which contain only the changed portion of "
"files. This *binary delta technology* [1]_ means :command:`swupd` on |CL|"
" systems only needs to download and apply a small fraction of a package "
"in order to receive an update."
msgstr ""
#: ../../concepts/swupd-about.rst:55
msgid ""
"The :ref:`mixer <mixer-about>` tool additionally computes updates files "
"in multiple compression formats, allowing :command:`swupd` to utilize the"
" most efficiently compressed format for a |CL| system to minimize the "
"cost to update."
msgstr ""
#: ../../concepts/swupd-about.rst:61
msgid "Update integrity"
msgstr ""
#: ../../concepts/swupd-about.rst:63
msgid ""
"This is the basis of the :command:`swupd diagnose` subcommand, which "
"allows a |CL| system to check for any discrepancies to system files. As "
"necessary, :command:`swupd repair` provides a useful way for software "
"developers to remediate these discrepancies and return to a known "
"filesystem state."
msgstr ""
#: ../../concepts/swupd-about.rst:67
msgid "Bundles"
msgstr ""
#: ../../concepts/swupd-about.rst:69
msgid ""
"|CL-ATTR| approaches software management differently than many other "
"Linux-based operating systems."
msgstr ""
#: ../../concepts/swupd-about.rst:72
msgid ""
"Instead of deploying granular software packages, |CL| uses the concept of"
" bundles with pre-associated software. Each bundle encapsulates a "
"particular use-case, which is enabled by composing all the required "
"upstream open-source projects and packages into one logical unit."
msgstr ""
#: ../../concepts/swupd-about.rst:77
msgid "This bundle-based approach offers some unique advantages:"
msgstr ""
#: ../../concepts/swupd-about.rst:79
msgid ""
"Bundles provide a particular functionality, or stack, which include all "
"associated runtime dependencies."
msgstr ""
#: ../../concepts/swupd-about.rst:82
msgid ""
"Software package dependencies are resolved on the server, so file-level "
"conflicts do not occur on the target system after an update."
msgstr ""
#: ../../concepts/swupd-about.rst:85
msgid "All combinations of bundles are able to co-exist on a |CL| system."
msgstr ""
#: ../../concepts/swupd-about.rst:87
msgid "For more information on bundles, visit:"
msgstr ""
#: ../../concepts/swupd-about.rst:89
msgid ":ref:`bundles`"
msgstr ""
#: ../../concepts/swupd-about.rst:90
msgid ":ref:`bundles-about`"
msgstr ""
#: ../../concepts/swupd-about.rst:91
msgid ":ref:`bundle-commands`"
msgstr ""
#: ../../concepts/swupd-about.rst:92
msgid ":ref:`compatible-kernels`"
msgstr ""
#: ../../concepts/swupd-about.rst:94
msgid ""
"The software update technology for |CL-ATTR| was first presented at the "
"Linux Plumbers conference in 2012."
msgstr ""
locale/de/LC_MESSAGES/concepts/telemetry-about.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/concepts/telemetry-about.po
-176
View File
@@ -1,176 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-12 12:18-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../concepts/telemetry-about.rst:4
msgid "Telemetrics"
msgstr ""
#: ../../concepts/telemetry-about.rst:6
msgid ""
"One of the key features of |CL-ATTR| is telemetry, which is used to "
"monitor system health. Telemetry enables developers to observe and "
"proactively address issues before end users are impacted."
msgstr ""
#: ../../concepts/telemetry-about.rst:10
msgid "*Telemetrics* is a combination word made from:"
msgstr ""
#: ../../concepts/telemetry-about.rst:12
msgid "*Telemetry* which is sensing and reporting data."
msgstr ""
#: ../../concepts/telemetry-about.rst:13
msgid ""
"*Analytics* which is using visualization and statistical inferencing to "
"make sense of the reported data."
msgstr ""
#: ../../concepts/telemetry-about.rst:16
msgid ""
"|CL| telemetry reports system-level debug/crash information using "
"specialized probes. The probes monitor system tasks such as :abbr:`swupd "
"(software updater)`, kernel oops, machine error checks, and BIOS error "
"report table for unhandled hardware failures. Telemetry enables real-time"
" issue reporting to allow system developers to quickly focus on an issue "
"and monitor corrective actions."
msgstr ""
#: ../../concepts/telemetry-about.rst:22
msgid ""
"|CL| telemetry is fully customizable and can be used during software "
"development for debugging purposes. You can use **libtelemetry** in your "
"code to create custom telemetry records. You can also use **telem-record-"
"gen** in script files or call it from another program."
msgstr ""
#: ../../concepts/telemetry-about.rst:29
msgid ""
"The |CL| telemetry client is disabled by default until you decide to "
"enable it. Telemetry is an **opt-in** solution and can be easily enabled"
" or disabled."
msgstr ""
#: ../../concepts/telemetry-about.rst:32
msgid "Architecture"
msgstr ""
#: ../../concepts/telemetry-about.rst:34
msgid ""
"|CL| telemetry has two fundamental components, which are shown in figure "
"1:"
msgstr ""
#: ../../concepts/telemetry-about.rst:36
msgid ""
"Client: generates and delivers records to the backend server via the "
"network."
msgstr ""
#: ../../concepts/telemetry-about.rst:37
msgid ""
"Backend: captures records sent from the client and displays the "
"cumulative content through a specialized interface."
msgstr ""
#: ../../concepts/telemetry-about.rst:42
msgid ""
"If you want to capture your own records for analysis, you must set up "
"your own backend server."
msgstr ""
#: ../../concepts/telemetry-about.rst:49
msgid "Figure 1: Clear Linux Telemetry Architecture."
msgstr ""
#: ../../concepts/telemetry-about.rst:51
msgid ""
"The telemetry client provides the front end of a complete telemetrics "
"solution and includes the following components:"
msgstr ""
#: ../../concepts/telemetry-about.rst:54
msgid ""
"**telemprobd**, a daemon that prepares the telemetry records and spools "
"them on disk prior to delivery"
msgstr ""
#: ../../concepts/telemetry-about.rst:55
msgid ""
"**telempostd**, a daemon that sends the records to the telemetry backend "
"server or leaves them on disk until deleting after the record expires."
msgstr ""
#: ../../concepts/telemetry-about.rst:57
msgid "**probes**, that collect specific types of data from the operating system."
msgstr ""
#: ../../concepts/telemetry-about.rst:58
msgid ""
"**libtelemetry**, that telemetrics probes use to create telemetrics "
"records and send them to the telemprobd daemon for further processing."
msgstr ""
#: ../../concepts/telemetry-about.rst:62
msgid ""
"The telemetry backend provides the server-side component of a complete "
"telemetrics solution and consists of:"
msgstr ""
#: ../../concepts/telemetry-about.rst:65
msgid "Nginx web server."
msgstr ""
#: ../../concepts/telemetry-about.rst:66
msgid "Two Flask apps:"
msgstr ""
#: ../../concepts/telemetry-about.rst:68
msgid ""
"Collector, an ingestion web app for records received from telemetrics-"
"client probes."
msgstr ""
#: ../../concepts/telemetry-about.rst:69
msgid ""
"TelemetryUI, a web app that exposes several views to visualize the "
"telemetry data and also provides a REST API to perform queries."
msgstr ""
#: ../../concepts/telemetry-about.rst:72
msgid "PostgreSQL as the underlying database server."
msgstr ""
#: ../../concepts/telemetry-about.rst:74
msgid ""
"The default telemetry backend server reports back to the |CL| development"
" team and is not viewable outside the Intel firewall. If you want to "
"collect your own records, then you must set up your own telemetry backend"
" server."
msgstr ""
#: ../../concepts/telemetry-about.rst:79
msgid "Next steps"
msgstr ""
#: ../../concepts/telemetry-about.rst:81
msgid "To put this concept into practice, refer to :ref:`telem-guide`."
msgstr ""
locale/de/LC_MESSAGES/disclaimers.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/disclaimers.po
-32
View File
@@ -1,32 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-12 12:18-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../disclaimers.rst:7
msgid "Disclaimer"
msgstr ""
#: ../../disclaimers.rst:9
msgid ""
"This documentation is a work in progress and is being provided for "
"informative purposes only. Because it is a work in progress, there are "
"parts that are either missing or will be revised as code development "
"continues."
msgstr ""
locale/de/LC_MESSAGES/documentation_license.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/documentation_license.po
-20
View File
@@ -1,20 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-12 12:18-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
locale/de/LC_MESSAGES/get-started/bare-metal-install-desktop/bare-metal-install-desktop.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/get-started/bare-metal-install-desktop/bare-metal-install-desktop.po
-1013
View File
File diff suppressed because it is too large Load Diff
locale/de/LC_MESSAGES/get-started/bare-metal-install-server/bare-metal-install-server.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/get-started/bare-metal-install-server/bare-metal-install-server.po
-1312
View File
File diff suppressed because it is too large Load Diff
locale/de/LC_MESSAGES/get-started/bootable-usb/bootable-usb.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/get-started/bootable-usb/bootable-usb.po
-239
View File
@@ -1,239 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-17 11:17-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../get-started/bootable-usb/bootable-usb.rst:4
msgid "Create a bootable USB drive"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:6
msgid ""
"Follow the instructions applicable to your system to create a bootable "
"|CL-ATTR| USB drive:"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:9
msgid ":ref:`bootable-usb-linux`"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:10
msgid ":ref:`bootable-usb-mac`"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:11
msgid ":ref:`bootable-usb-windows`"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:14
msgid "Prerequisites"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:16
msgid "Use an **8GB** or larger USB drive."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:17
msgid ""
"Download the |CL| live boot image or interactive installer image from the"
" `Downloads`_ page."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:23
msgid "Create a bootable USB drive on Linux\\*"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:25
#: ../../get-started/bootable-usb/bootable-usb.rst:108
#: ../../get-started/bootable-usb/bootable-usb.rst:167
msgid "Make sure you have have completed all `Prerequisites`_."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:27
msgid ""
"Before burning the image onto your USB drive, :ref:`verify and decompress"
" your image <verify-linux>`."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:31
#: ../../get-started/bootable-usb/bootable-usb.rst:114
#: ../../get-started/bootable-usb/bootable-usb.rst:173
msgid "Burn the |CL| image onto a USB drive"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:35
#: ../../get-started/bootable-usb/bootable-usb.rst:118
#: ../../get-started/bootable-usb/bootable-usb.rst:177
msgid "|CAUTION-BACKUP-USB|"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:37
msgid "Open a terminal emulator and get root privilege."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:43
#: ../../get-started/bootable-usb/bootable-usb.rst:122
msgid "Go to the directory with the decompressed image."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:45
msgid "Plug in the USB drive."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:47
msgid ""
"Identify the USB drive using the :command:`lsblk` command. This shows all"
" drives attached to the system, including the primary hard disk. In the "
"example output below, there are 4 drives (`/dev/sda`, `/dev/sdb`, "
"`/dev/sdc`, and `/dev/sdd`) attached, where `/dev/sda` is primary drive. "
"The remaining are three USB drives. The output also shows the mounted "
"partitions (under the `MOUNTPOINT` column) for each drive."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:59
msgid "Example output:"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:82
msgid ""
"You must unmount a USB drive before burning an image onto it. Note that "
"some Linux distros automatically mount a USB drive when it is plugged in."
" Unmount a USB drive with the :command:`umount` command followed by the "
"device identifier/partition. For example:"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:92
msgid ""
"Burn the image onto the USB drive. The example below burns an "
"uncompressed image onto `<your USB device>`:"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:101
msgid "|CAUTION-UNMOUNT-USB-PARTITIONS|"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:106
msgid "Create a bootable USB drive on macOS\\*"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:110
msgid ""
"Before burning the image onto your USB drive, :ref:`verify and decompress"
" your image <verify-mac>`."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:120
msgid "Launch the Terminal app."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:124
msgid "Plug in a USB drive and get its identifier:"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:130
msgid "This will list available disks and their partitions, as shown in Figure 1."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:136
msgid "Figure 1: macOS - Get USB drive identifier"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:138
msgid "Unmount the USB drive identified in the previous step. For example:"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:144
msgid ""
"Burn the image onto the drive using the :command:`dd` command. The "
"example below burns an uncompressed image onto `<your USB device>`:"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:151
msgid ""
"To speed up the imaging process, add an ‘r’ in front of the disk "
"identifier. For example `/dev/rdisk2`."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:154
msgid "Press :kbd:`<CTL>-T` to check imaging progress."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:156
msgid "Eject the USB drive."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:165
msgid "Create a bootable USB drive on Windows\\*"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:169
msgid ""
"Before burning the image onto your USB drive, :ref:`verify and decompress"
" your image <verify-windows>`."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:179
msgid ""
"Download the `Rufus`_ utility to burn the image onto a USB drive. We use "
"Rufus 3.5 here. **Only use the latest version of Rufus**."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:182
msgid "Plug in the USB drive and open Rufus."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:184
msgid "Under `Boot selection`, click the :guilabel:`SELECT` button."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:186
msgid "Find and select the previously extracted |CL| image file."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:188
msgid "Click the :guilabel:`START` button. See Figure 2."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:194
msgid "Figure 2: Rufus utility"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:196
msgid ""
"When the dialogue appears, select :guilabel:`Write in ISO image mode "
"(Recommended)`. See Figure 3."
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:203
msgid "Figure 3: ISOHybrid image detected"
msgstr ""
#: ../../get-started/bootable-usb/bootable-usb.rst:205
msgid "Select the Windows taskbar menu for USB and select eject."
msgstr ""
#~ msgid ""
#~ "Instructions to create a |CL-ATTR| "
#~ "USB drive vary depending on your "
#~ "operating system. Follow the instructions "
#~ "applicable to your system:"
#~ msgstr ""
#~ msgid "`Download`_ the |CL| live boot image or interactive installer image."
#~ msgstr ""
locale/de/LC_MESSAGES/get-started/compatibility-check.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/get-started/compatibility-check.po
-106
View File
@@ -1,106 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-17 11:17-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../get-started/compatibility-check.rst:4
msgid "Check processor and EFI firmware compatibility"
msgstr ""
#: ../../get-started/compatibility-check.rst:6
msgid ""
"Before installing |CL-ATTR|, check your host system's processor and EFI "
"firmware compatibility. To check compatibilty, choose one of the "
"following paths:"
msgstr ""
#: ../../get-started/compatibility-check.rst:9
msgid ""
"From a system with a Linux\\* OS installed, follow the instructions to "
":ref:`check-compatibility-steps`."
msgstr ""
#: ../../get-started/compatibility-check.rst:11
msgid ""
"From a non-Linux OS, first :ref:`bare-metal-install-desktop` and then "
"follow the instructions to :ref:`check-compatibility-steps`."
msgstr ""
#: ../../get-started/compatibility-check.rst:15
msgid ""
"This does not check other system components (for example: storage and "
"graphics) for compatibility with |CL|."
msgstr ""
#: ../../get-started/compatibility-check.rst:21
msgid "Check compatibility"
msgstr ""
#: ../../get-started/compatibility-check.rst:23
msgid "Download the `clear-linux-check-config.sh`_ file."
msgstr ""
#: ../../get-started/compatibility-check.rst:25
msgid "If a browser is not available, use:"
msgstr ""
#: ../../get-started/compatibility-check.rst:31
msgid "Make the script executable."
msgstr ""
#: ../../get-started/compatibility-check.rst:37
msgid "Run the script."
msgstr ""
#: ../../get-started/compatibility-check.rst:39
msgid ""
"Check to see if the host's processor and EFI firmware is capable of "
"running |CL|."
msgstr ""
#: ../../get-started/compatibility-check.rst:46
msgid "Check to see if the host is capable of running |CL| in a container."
msgstr ""
#: ../../get-started/compatibility-check.rst:52
msgid ""
"The script prints a list of test results similar to the output below. All"
" items should return a `SUCCESS` status. This example indicates the "
"host's processor and EFI firmware support running |CL|."
msgstr ""
#~ msgid ""
#~ "On a system that is currently "
#~ "running a Linux\\* operating system, "
#~ "follow the instructions below to "
#~ "determine if your system's processor and"
#~ " EFI firmware is capable of running"
#~ " |CL-ATTR|. Otherwise, :ref:`bare-metal-"
#~ "install-desktop` and then perform the"
#~ " steps below."
#~ msgstr ""
#~ msgid ""
#~ "The script will print a list of"
#~ " test results similar to the output"
#~ " below. All items should return a "
#~ "`SUCCESS` status. This example indicates "
#~ "the host's processor and EFI firmware"
#~ " support running |CL|."
#~ msgstr ""
locale/de/LC_MESSAGES/get-started/get-started.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/get-started/get-started.po
-76
View File
@@ -1,76 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-17 11:17-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../get-started/get-started.rst:4
msgid "Get started"
msgstr ""
#: ../../get-started/get-started.rst:6
msgid ""
"The Get Started section guides you through the requirements and "
"installation of |CL-ATTR|. Follow these step-by-step intructions to get "
"started with |CL|, fast."
msgstr ""
#: ../../get-started/get-started.rst:10
msgid "Pre-install"
msgstr ""
#: ../../get-started/get-started.rst:12
msgid "There are a couple of things to take care of before you install."
msgstr ""
#: ../../get-started/get-started.rst:14
msgid ":ref:`system-requirements`"
msgstr ""
#: ../../get-started/get-started.rst:15
msgid ":ref:`compatibility-check`"
msgstr ""
#: ../../get-started/get-started.rst:16
msgid ":ref:`bootable-usb`"
msgstr ""
#: ../../get-started/get-started.rst:18
msgid "When installing |CL-ATTR| in a VM, consider which kernel to use."
msgstr ""
#: ../../get-started/get-started.rst:20
msgid ":ref:`Compatible VM kernels <vm-kernels>`"
msgstr ""
#: ../../get-started/get-started.rst:30
msgid "Install"
msgstr ""
#: ../../get-started/get-started.rst:42
msgid "Install in a virtual machine"
msgstr ""
#~ msgid ""
#~ "The Get Started section will get "
#~ "you up and running fast with "
#~ "|CL-ATTR|. Use these step-by-step "
#~ "instructions to guide you through the"
#~ " installing |CL| from a live desktop"
#~ " or to a virtual machine."
#~ msgstr ""
locale/de/LC_MESSAGES/get-started/install-configfile.po
-226
View File
@@ -1,226 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-17 11:17-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../get-started/install-configfile.rst:4
msgid "Install using clr-installer and a configuration file"
msgstr ""
#: ../../get-started/install-configfile.rst:6
msgid ""
"This page explains how to install |CL-ATTR| using the clr-installer tool "
"with a configuration file. The configuration file (:file:`clr-"
"installer.yaml`) can be reused to duplicate the same installation "
"configuration on additional machines."
msgstr ""
#: ../../get-started/install-configfile.rst:16
msgid "Prerequisites"
msgstr ""
#: ../../get-started/install-configfile.rst:18
msgid "Ensure that your target system supports the installation:"
msgstr ""
#: ../../get-started/install-configfile.rst:20
msgid ":ref:`system-requirements`"
msgstr ""
#: ../../get-started/install-configfile.rst:21
msgid ":ref:`compatibility-check`"
msgstr ""
#: ../../get-started/install-configfile.rst:24
msgid "Process"
msgstr ""
#: ../../get-started/install-configfile.rst:26
msgid ""
"This guide describes two methods for using a configuration file with the "
"clr-installer tool. You can use either method to achieve the same goal. "
"Choose the method that works best for your setup."
msgstr ""
#: ../../get-started/install-configfile.rst:30
msgid "If you are installing |CL| for the first time, we recommend Example 1."
msgstr ""
#: ../../get-started/install-configfile.rst:32
msgid "To clone an existing |CL| setup on another system, we recommend Example 2."
msgstr ""
#: ../../get-started/install-configfile.rst:35
msgid "Example 1"
msgstr ""
#: ../../get-started/install-configfile.rst:37
msgid ""
"This method uses a configuration file template to perform a new "
"installation."
msgstr ""
#: ../../get-started/install-configfile.rst:39
#: ../../get-started/install-configfile.rst:146
msgid "Perform the following steps:"
msgstr ""
#: ../../get-started/install-configfile.rst:41
#: ../../get-started/install-configfile.rst:163
msgid "Go to `Downloads`_ and download the latest Clear Linux OS Server image."
msgstr ""
#: ../../get-started/install-configfile.rst:43
#: ../../get-started/install-configfile.rst:165
msgid ""
"For example: "
"https://download.clearlinux.org/releases/30010/clear/clear-30010-live-"
"server.iso.xz"
msgstr ""
#: ../../get-started/install-configfile.rst:46
#: ../../get-started/install-configfile.rst:168
msgid "Follow the instructions to :ref:`bootable-usb` based on your OS."
msgstr ""
#: ../../get-started/install-configfile.rst:48
#: ../../get-started/install-configfile.rst:170
msgid "Boot up the USB thumb drive."
msgstr ""
#: ../../get-started/install-configfile.rst:49
#: ../../get-started/install-configfile.rst:171
msgid "Select :guilabel:`Clear Linux OS` from the menu."
msgstr ""
#: ../../get-started/install-configfile.rst:50
#: ../../get-started/install-configfile.rst:172
msgid "In the console window, log in as root and set a password."
msgstr ""
#: ../../get-started/install-configfile.rst:51
#: ../../get-started/install-configfile.rst:173
msgid ""
"Verify you have a network connection to the Internet and configure proxy "
"settings if you're working behind a firewall."
msgstr ""
#: ../../get-started/install-configfile.rst:53
msgid "Download a :file:`live-server.yaml` template."
msgstr ""
#: ../../get-started/install-configfile.rst:55
msgid "For example:"
msgstr ""
#: ../../get-started/install-configfile.rst:61
msgid "Edit the template and change the settings as needed."
msgstr ""
#: ../../get-started/install-configfile.rst:63
msgid "Commonly-changed settings include:"
msgstr ""
#: ../../get-started/install-configfile.rst:67
msgid ""
"Under *block-devices*, set “file: \"/dev/sda\"” or enter your preferred "
"device."
msgstr ""
#: ../../get-started/install-configfile.rst:68
msgid ""
"Under *targetMedia*, set the third partition size to “0” to use the "
"entire disk space."
msgstr ""
#: ../../get-started/install-configfile.rst:69
msgid "Under *bundles*, add additional bundles as needed."
msgstr ""
#: ../../get-started/install-configfile.rst:70
msgid ""
"Delete the *post-install* section unless you have post-installation "
"scripts."
msgstr ""
#: ../../get-started/install-configfile.rst:71
msgid ""
"Under *Version*, set a version number. To use the latest version, set to "
"“0”."
msgstr ""
#: ../../get-started/install-configfile.rst:73
msgid ""
"Commonly-changed settings are shown in lines 15, 34, 37, and 51 below. "
"See `Installer YAML Syntax`_ for more details."
msgstr ""
#: ../../get-started/install-configfile.rst:134
#: ../../get-started/install-configfile.rst:177
msgid "Start the installation with the command:"
msgstr ""
#: ../../get-started/install-configfile.rst:141
msgid "Example 2"
msgstr ""
#: ../../get-started/install-configfile.rst:143
msgid ""
"This method uses a saved configuration file from a previous installation,"
" which you can use to easily duplicate the installation on additional "
"machines."
msgstr ""
#: ../../get-started/install-configfile.rst:148
msgid ""
"Open a console window on a system where |CL| was installed to retrieve a "
"copy of the configuration file."
msgstr ""
#: ../../get-started/install-configfile.rst:151
msgid "In the console window, log in as root and enter your password."
msgstr ""
#: ../../get-started/install-configfile.rst:153
msgid ""
"Change directory to :file:`/root` and copy the :file:`clr-installer.yaml`"
" file to a USB thumb drive."
msgstr ""
#: ../../get-started/install-configfile.rst:161
msgid "Start the installation on the target with the following steps:"
msgstr ""
#: ../../get-started/install-configfile.rst:175
msgid ""
"Plug in and mount the USB thumb drive containing the retrieved :file"
":`clr-installer.yaml` configuration file."
msgstr ""
#: ../../get-started/install-configfile.rst:184
msgid "References"
msgstr ""
#: ../../get-started/install-configfile.rst:186
msgid "`Clear Linux Installer`_"
msgstr ""
#: ../../get-started/install-configfile.rst:187
msgid "`Installer YAML Syntax`_"
msgstr ""
locale/de/LC_MESSAGES/get-started/virtual-machine-install/gce.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/get-started/virtual-machine-install/gce.po
-448
View File
@@ -1,448 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-17 11:17-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../get-started/virtual-machine-install/gce.rst:4
msgid "Launch |CL-ATTR| Compute Engine on Google Cloud Platform\\*"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:6
msgid ""
"This page explains the steps to create a virtual machine instance of |CL-"
"ATTR| on `Google Cloud Platform`_ (:abbr:`GCP (Google Cloud Platform)`)."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:14
msgid "Prerequisites"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:16
msgid "Set up a Google account and a GCP billing account."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:18
msgid ""
"Generate and install a user SSH key in the Linux PCs that will connect to"
" the VMs in GCP."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:22
msgid "Setup |CL| VM on GCP"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:24
msgid ""
"Sign in to your Google\\* account on the `Google Cloud Console "
"<https://console.cloud.google.com/>`_:"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:31
msgid "Figure 1: Google sign in screen"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:33
msgid ""
"Google Cloud Platform uses **Projects** to manage resources. Select or "
"create a new project for hosting the |CL| VM."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:38
msgid ""
"Refer to the `Quickstart Using a Linux VM "
"<https://cloud.google.com/compute/docs/quickstart-linux>`_ guide to learn"
" about the process of creating VM instances on GCP."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:42
msgid ""
"Navigate to the latest |CL| `release folder "
"<https://download.clearlinux.org/releases/current/clear/>`_ to view the "
"currently released :abbr:`GCE (Google Compute Engine\\*)` image, and "
"download the :file:`clear-<release number>-gce.tar.gz` image archive."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:48
msgid ""
"You don't need to uncompress the image archive, the intact file will be "
"uploaded to the Google Cloud Storage later."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:51
msgid ""
"Create a *Storage Bucket* for hosting the |CL| image source archive "
"downloaded in the previous step:"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:54
#: ../../get-started/virtual-machine-install/gce.rst:112
#: ../../get-started/virtual-machine-install/gce.rst:158
msgid "Click the :guilabel:`Navigation menu` icon on the upper left screen menu."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:56
msgid ""
"Select the :menuselection:`Storage` item from the side bar on the left. "
"You will be sent to the Storage Browser tool or the Cloud Storage "
"overview page."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:63
msgid "Figure 2: Browse Google Cloud Storage"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:66
msgid ""
"You may need to create a billing account and link to this project before "
"you create a bucket."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:73
msgid "Figure 3: Cloud Storage Browser tool"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:75
msgid ""
"Click the :guilabel:`CREATE BUCKET` button to enter the bucket creation "
"tool. The bucket name must be unique because buckets in the Cloud Storage"
" share a single global namespace."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:79
msgid ""
"Leave the remaining options set to the defaults, and click the "
":guilabel:`Create` button at the bottom to create a *Bucket*."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:86
msgid "Figure 4: Set bucket name"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:88
msgid ""
"Once the bucket is created, click the :guilabel:`Upload files` button on "
"the Bucket details page to upload the |CL| GCE image archive to the named"
" bucket:"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:96
msgid "Figure 5: Cloud Storage bucket"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:102
msgid "Figure 6: Uploading the image source archive file"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:108
msgid "Figure 7: Importing complete"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:110
msgid "Browse the Compute Engine Image library page:"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:114
msgid ""
"Select the :menuselection:`Compute Engine --> Images` from the side bar "
"on the left."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:121
msgid "Figure 8: Image library"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:123
msgid ""
"On the Compute Engine Image library page, click the :guilabel:`[+] CREATE"
" IMAGE` menu item to create a custom image:"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:130
msgid "Figure 9: Create image"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:132
msgid ""
"In the VM image creation page, change the image source type to *Cloud "
"Storage file*."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:135
msgid "Under :guilabel:`Source`, select :guilabel:`Browse`."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:137
msgid ""
"Locate the :file:`clear-<release number>-gce.tar.gz` file, and click "
":guilabel:`Select`."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:144
msgid "Figure 10: Create image using imported object"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:146
msgid ""
"Accept all default options, and click the :guilabel:`Create` button at "
"the bottom to import the Clear Linux GCE image to the image library."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:153
msgid "Figure 11: Image is created"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:155
msgid ""
"After the |CL| image is imported, you can launch a VM instance running "
"|CL|:"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:160
msgid ""
"Select :menuselection:`Compute Engine --> VM Instances` from the side bar"
" on the left."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:167
msgid "Figure 12: VM instances catalog"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:169
msgid ""
"If no VM instance was created in this project, you will be prompted to "
"create one."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:172
msgid ""
"Alternatively, click the :guilabel:`CREATE INSTANCE` button on the VM "
"instances page to create a VM instance."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:179
msgid "Figure 13: VM creation"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:185
msgid "Figure 14: VM instances list"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:187
msgid ""
"Under :guilabel:`Region`, choose a region based on the `Best practices "
"for Compute Engine regions selection`_."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:190
msgid "Under :guilabel:`Boot disk`, click the :guilabel:`Change` button."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:196
msgid "Figure 15: Use custom image"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:198
msgid ""
"Select the :menuselection:`Custom images` tab for using Clear Linux OS "
"GCE image."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:204
msgid "Figure 16: Select Clear Linux boot disk to create a VM instance"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:206
msgid ""
"Scroll down to the bottom of the VM instance creation page, expand the "
":guilabel:`Management, security, disks, networking, sole tenancy` group."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:214
msgid "Figure 17: Set up SSH keys"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:217
msgid ""
"|CL| does not allow SSH login with a root account by default. As a "
"result, you must configure the VM instance with your SSH public key, so "
"that you are able to access it remotely."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:221
msgid "Refer to :ref:`security` for more details."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:223
msgid ""
"Click the :menuselection:`Security` tab, copy and paste your SSH public "
"key:"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:229
msgid "Figure 18: Set SSH key for remote login"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:233
msgid ""
"The username is assigned from characters preceding ``@`` in the email "
"address, included in the SSH key. The dot symbol \".\" is not allowed, "
"because it is an invalid character while creating user accounts in |CL|."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:238
msgid "Click the :guilabel:`Create` button to create the |CL| VM."
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:240
msgid "The Clear Linux VM instance is created and assigned a public IP address:"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:246
msgid "Figure 19: Clear Linux VM instance is created and started"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:248
msgid ""
"You can now SSH login to the VM using the IP address obtained in the "
"previous step, and the username associated with the SSH public key:"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:255
msgid "Figure 20: SSH login to Clear Linux VM"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:258
msgid "Related topics"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:260
msgid ":ref:`azure`"
msgstr ""
#: ../../get-started/virtual-machine-install/gce.rst:261
msgid ":ref:`aws-web`"
msgstr ""
#~ msgid ""
#~ "This tutorial walks you through the "
#~ "steps to create a virtual machine "
#~ "instance of |CL-ATTR| on `Google "
#~ "Cloud Platform`_ (:abbr:`GCP (Google Cloud "
#~ "Platform)`)."
#~ msgstr ""
#~ msgid "Process"
#~ msgstr ""
#~ msgid "Click the *Navigation menu* icon on the upper left screen menu."
#~ msgstr ""
#~ msgid ""
#~ "Select the *Storage* item from the "
#~ "side bar on the left. You will "
#~ "be sent to the Storage Browser "
#~ "tool or the Cloud Storage overview "
#~ "page."
#~ msgstr ""
#~ msgid ""
#~ "Click the ``CREATE BUCKET`` button to"
#~ " enter the bucket creation tool. The"
#~ " bucket name must be unique because"
#~ " buckets in the Cloud Storage share"
#~ " a single global namespace."
#~ msgstr ""
#~ msgid ""
#~ "Leave the remaining options set to "
#~ "the defaults, and select the ``Create``"
#~ " button at the bottom to create "
#~ "a *Bucket*."
#~ msgstr ""
#~ msgid ""
#~ "Once the bucket is created, click "
#~ "the ``Upload files`` button on the "
#~ "Bucket details page to upload the "
#~ "|CL| GCE image archive to the "
#~ "named bucket:"
#~ msgstr ""
#~ msgid "Hover your mouse over the *Compute Engine* menu and select *Images*."
#~ msgstr ""
#~ msgid ""
#~ "On the Compute Engine Image library "
#~ "page, click the ``[+] CREATE IMAGE`` "
#~ "menu item to create a custom "
#~ "image:"
#~ msgstr ""
#~ msgid "Under :guilabel:`Cloud Storage file`, select :guilabel:`Browse`."
#~ msgstr ""
#~ msgid ""
#~ "Accept all default options, and click"
#~ " the ``Create`` button at the bottom"
#~ " to import the Clear Linux GCE "
#~ "image to the image library."
#~ msgstr ""
#~ msgid ""
#~ "Hover your mouse over the *Compute "
#~ "Engine* menu group and select the "
#~ "*VM instances* item."
#~ msgstr ""
#~ msgid ""
#~ "Alternatively, click the ``CREATE INSTANCE``"
#~ " button on the VM instances page "
#~ "to create a VM instance."
#~ msgstr ""
#~ msgid ""
#~ "In :guilabel:`Region`, choose a region "
#~ "based on the `Best practices for "
#~ "Compute Engine regions selection`_."
#~ msgstr ""
#~ msgid "Under *Boot disk*, click the ``Change`` button."
#~ msgstr ""
#~ msgid "Select the *Custom images* tab for using Clear Linux OS GCE image."
#~ msgstr ""
#~ msgid ""
#~ "Scroll down to the bottom of the"
#~ " VM instance creation page, expand "
#~ "the *Management, security, disks, networking,"
#~ " sole tenancy* group."
#~ msgstr ""
#~ msgid "Click the *Security* tab, copy and paste your SSH public key:"
#~ msgstr ""
#~ msgid "Click the ``Create`` button to create the |CL| VM."
#~ msgstr ""
#~ msgid ""
#~ "The following tutorials describe a "
#~ "similar process and may be useful "
#~ "references:"
#~ msgstr ""
locale/de/LC_MESSAGES/get-started/virtual-machine-install/hyper-v.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/get-started/virtual-machine-install/hyper-v.po
-158
View File
@@ -1,158 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-17 11:17-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../get-started/virtual-machine-install/hyper-v.rst:4
msgid "Use Hyper-V\\*"
msgstr ""
#: ../../get-started/virtual-machine-install/hyper-v.rst:6
msgid ""
"This page explains how to run |CL-ATTR| inside a `Windows Server "
"Virtualization`_\\* or **Hyper-V** environment."
msgstr ""
#: ../../get-started/virtual-machine-install/hyper-v.rst:14
msgid "Prerequisites"
msgstr ""
#: ../../get-started/virtual-machine-install/hyper-v.rst:16
msgid "Enable `Intel® Virtualization Technology`_ (Intel® VT)"
msgstr ""
#: ../../get-started/virtual-machine-install/hyper-v.rst:18
msgid ""
"Enable `Intel® Virtualization Technology for Directed I/O`_ (Intel® VT-d)"
" in your BIOS/UEFI firmware configuration."
msgstr ""
#: ../../get-started/virtual-machine-install/hyper-v.rst:22
msgid "Enable Hyper-V"
msgstr ""
#: ../../get-started/virtual-machine-install/hyper-v.rst:24
msgid ""
"Please refer to `Install Hyper-V on Windows 10`_ to enable and configure "
"*Hyper-V* on your machine."
msgstr ""
#: ../../get-started/virtual-machine-install/hyper-v.rst:28
msgid "Create a virtual network"
msgstr ""
#: ../../get-started/virtual-machine-install/hyper-v.rst:30
msgid ""
"Once *Hyper-V* has been enabled on your Windows system you will need to "
"create a virtual network in the **Hyper-V Manager**. Refer to the "
"`Create a virtual network`_ documentation to create and configure a "
"virtual network."
msgstr ""
#: ../../get-started/virtual-machine-install/hyper-v.rst:36
msgid "Create a virtual machine"
msgstr ""
#: ../../get-started/virtual-machine-install/hyper-v.rst:38
msgid ""
"Download and decompress the latest hyperv disk image :file:`clear-XXXXX-"
"hyperv.img.gz`, where XXXXX is the latest available version of |CL| from "
"our `Downloads`_ page."
msgstr ""
#: ../../get-started/virtual-machine-install/hyper-v.rst:42
msgid "Create a virtual machine using the **Hyper-V Manager**:"
msgstr ""
#: ../../get-started/virtual-machine-install/hyper-v.rst:44
msgid "Choose **Generation 2** when prompted to *specify VM generation*."
msgstr ""
#: ../../get-started/virtual-machine-install/hyper-v.rst:45
msgid ""
"Choose **Use an existing virtual hard disk** and browse to find the :file"
":`clear-XXXX-hyperv.vhdx` file."
msgstr ""
#: ../../get-started/virtual-machine-install/hyper-v.rst:47
msgid ""
"When finished, open VM settings, select Firmware Section and in Secure "
"Boot config, **uncheck** Enable Secure Boot."
msgstr ""
#: ../../get-started/virtual-machine-install/hyper-v.rst:50
msgid "Currently, |CL| does not boot with `secure boot` enabled."
msgstr ""
#: ../../get-started/virtual-machine-install/hyper-v.rst:53
msgid "Connect to your new VM and start it. You should see a prompt:"
msgstr ""
#: ../../get-started/virtual-machine-install/hyper-v.rst:59
msgid "Set a root user password."
msgstr ""
#: ../../get-started/virtual-machine-install/hyper-v.rst:61
msgid "Your virtual machine running |CL| is ready!"
msgstr ""
#~ msgid ""
#~ "This section explains how to run "
#~ "|CL-ATTR| inside a `Windows Server "
#~ "Virtualization`_\\* or **Hyper-V** environment."
#~ msgstr ""
#~ msgid ""
#~ "Please ensure you have enabled `Intel®"
#~ " Virtualization Technology "
#~ "<http://www.intel.com/content/www/us/en/virtualization"
#~ "/virtualization-technology/intel-virtualization-"
#~ "technology.html>`_ (Intel® VT) and `Intel® "
#~ "Virtualization Technology for Directed I/O "
#~ "<https://software.intel.com/en-us/articles/intel-"
#~ "virtualization-technology-for-directed-io-"
#~ "vt-d-enhancing-intel-platforms-for-"
#~ "efficient-virtualization-of-io-devices>`_ "
#~ "(Intel® VT-d) in your BIOS/UEFI firmware"
#~ " configuration."
#~ msgstr ""
#~ msgid ""
#~ "Please refer to the `Microsoft "
#~ "documentation`_ to enable and configure "
#~ "*Hyper-V* on your machine."
#~ msgstr ""
#~ msgid ""
#~ "Once *Hyper-V* has been enabled on "
#~ "your Windows system you will need "
#~ "to create a virtual network in the"
#~ " **Hyper-V Manager**. Refer to the "
#~ "`Create a Virtual Network documentation`_ "
#~ "to create and configure a virtual "
#~ "network."
#~ msgstr ""
#~ msgid ""
#~ "Download and decompress the latest "
#~ "hyperv disk image :file:`clear-XXXXX-"
#~ "hyperv.img.gz`, where XXXXX is the "
#~ "latest available version of |CL| from"
#~ " our `downloads`_ section."
#~ msgstr ""
locale/de/LC_MESSAGES/get-started/virtual-machine-install/kvm.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/get-started/virtual-machine-install/kvm.po
-261
View File
@@ -1,261 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-17 11:17-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../get-started/virtual-machine-install/kvm.rst:4
msgid "Run |CL-ATTR| as a KVM guest OS"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:6
msgid ""
"This page explains how to run |CL-ATTR| in a virtualized environment "
"using :abbr:`KVM (Kernel-based Virtual Machine)`."
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:14
msgid "Install QEMU-KVM"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:16
msgid ""
"Enable the `Intel® Virtualization Technology`_ (Intel® VT) and the "
"`Intel® Virtualization Technology for Directed I/O`_ (Intel® VT-d) in the"
" host machine’s BIOS."
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:20
msgid "Log in and open a terminal emulator."
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:22
msgid "Install `QEMU*-KVM` on the host machine. Below are some example distros."
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:24
msgid "On |CL|:"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:30
#: ../../get-started/virtual-machine-install/kvm.rst:159
msgid "On Ubuntu\\* 18.04 LTS Desktop:"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:36
#: ../../get-started/virtual-machine-install/kvm.rst:165
msgid "On Mint\\* 19.1 “Cinnamon” Desktop:"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:42
#: ../../get-started/virtual-machine-install/kvm.rst:171
msgid "On Fedora\\* 30 Workstation:"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:49
msgid "Download and launch the virtual machine"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:51
msgid ""
"Download the latest pre-built |CL| KVM image file from the `image "
"<https://cdn.download.clearlinux.org/image/>`_ directory. Look for "
"``clear-<version>-kvm.img.xz``. You can also use this command:"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:59
msgid "Uncompress the downloaded image:"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:65
msgid ""
"Download the 3 OVMF files (`OVMF.fd`, `OVMF_CODE.fd`, `OVMF_VARS.fd`) "
"that provides UEFI support for virtual machines."
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:76
msgid ""
"The default OVMF files from |CL| may not work for some distro version(s)."
" You may get an `ASSERT` in the `debug.log` file when starting the VM. If"
" that is the case, use the distro-specific-OVMF files instead. For "
"example, the |CL| OVMF files work for Ubuntu 18.04 LTS, but not for "
"Ubuntu 19.04 LTS. Installing and using the OVMF files for Ubuntu 19.04 "
"LTS resolved the `ASSERT` issue."
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:82
msgid ""
"Download the `start_qemu.sh`_ script from the `image "
"<https://cdn.download.clearlinux.org/image/>`_ directory. This script "
"will launch the |CL| VM and provide console interaction within the same "
"terminal emulator window."
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:91
msgid "Make the script executable:"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:97
msgid "Start the |CL| KVM virtual machine:"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:103
msgid "Log in as ``root`` user and set a new password."
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:106
msgid "SSH access into the virtual machine"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:108
msgid ""
"To interact with the |CL| VM through SSH instead of the console it was "
"launched from, follow these steps."
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:111
msgid "Configure SSH in the |CL| VM to allow root login:"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:119
msgid "Enable and start SSH server in the |CL| VM:"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:126
#: ../../get-started/virtual-machine-install/kvm.rst:215
msgid ""
"Determine the IP address of the host on which you will launch the VM. "
"Substitute <ip-addr-of-kvm-host> in the next step with this information."
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:133
msgid "SSH into the |CL| VM using the default port of `10022`:"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:140
msgid "Optional: Add the GNOME Display Manager (GDM)"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:142
msgid ""
"To add :abbr:`GDM (GNOME Display Manager)` to the |CL| VM, follow these "
"steps:"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:144
msgid "Shutdown the active |CL| VM."
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:150
msgid ""
"Install the Spice viewer on the local host or remote system. Below are "
"some example distros."
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:153
msgid "On Clear Linux:"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:177
msgid ""
"Modify the :file:`start_qemu.sh` script to increase memory (`-m`), add "
"graphics driver (`-vga`), and add Spice (`-spice`, `-usb`, and `-device`)"
" support."
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:198
msgid ""
"Due to changes in the :file:`start_qemu.sh` script from the previous "
"step, using the same OVMF files will result in the VM not booting "
"properly and you end up in the the UEFI shell. The easiest way to avoid "
"this is to delete the OVMF files and restore the originals before "
"relaunching the VM."
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:203
msgid "Increase the size of the VM by 10GB to accommodate the GDM installation:"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:209
msgid "Relaunch the |CL| VM:"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:222
msgid ""
"From the local host or remote system, open a new terminal emulator window"
" and connect into the |CL| VM using the Spice viewer:"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:229
msgid "Log in as `root` user into the |CL| VM."
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:231
msgid ""
"Follow these steps from :ref:`increase-virtual-disk-size` to resize the "
"partition of the virtual disk of the VM."
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:233
msgid "Add GDM to the |CL| VM:"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:239
msgid "Reboot the |CL| VM to start GDM:"
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:245
msgid "Go through the GDM out-of-box experience (OOBE)."
msgstr ""
#: ../../get-started/virtual-machine-install/kvm.rst:247
msgid ""
"The default aspect ratio of the GDM GUI for the |CL| VM is 4:3. To change"
" it, use GDM's `Devices > Displays` setting tool (located at the top-"
"right corner)."
msgstr ""
#~ msgid ""
#~ "This guide explains how to run "
#~ "|CL-ATTR| in a virtualized environment "
#~ "using :abbr:`KVM (Kernel-based Virtual "
#~ "Machine)`."
#~ msgstr ""
#~ msgid ""
#~ "Enable the `Intel® Virtualization Technology`_"
#~ " (Intel® VT) and the `Intel®Virtualization"
#~ " Technology for Directed I/O`_ (Intel® "
#~ "VT-d) in the host machine’s BIOS."
#~ msgstr ""
#~ msgid ""
#~ "Download the `QEMU-KVM launcher`_ script"
#~ " from the `image "
#~ "<https://cdn.download.clearlinux.org/image/>`_ directory. "
#~ "This script will launch the |CL| "
#~ "VM and provide console interaction "
#~ "within the same terminal emulator "
#~ "window."
#~ msgstr ""
#~ msgid ""
#~ "Follow these steps to `resize the "
#~ "partition`_ of the virtual disk of "
#~ "the VM."
#~ msgstr ""
locale/de/LC_MESSAGES/get-started/virtual-machine-install/virtualbox-cl-installer.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/get-started/virtual-machine-install/virtualbox-cl-installer.po
-703
View File
@@ -1,703 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-17 11:17-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:4
msgid "Install a |CL-ATTR| VM in VirtualBox\\*"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:6
msgid ""
"This page explains how to create a virtual machine on the `VirtualBox`_ "
"hypervisor with |CL-ATTR| as the guest operating system. These "
"instructions support the |CL| live-server installer to create the |CL| "
"virtual machine (VM)."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:15
msgid "Prerequisites"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:17
msgid ""
"Enable virtualization, such as `Intel® Virtualization Technology`_ "
"(Intel® VT), on the host system from EFI/BIOS."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:20
msgid ""
"Download and install |VB| **version 6.0 or greater** from `VirtualBox`_ "
"using the `VirtualBox Installation Instructions`_ for your platform."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:25
msgid "Download and extract the |CL| installer ISO"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:27
msgid ""
"Download the :file:`clear-<VERSION>-live-server.iso.xz` of |CL| on the "
"`Downloads`_ page."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:30
msgid ""
"Validate the integrity of the downloaded image by checking the file hash "
"and signatures. Refer to :ref:`validate-signatures` for detailed steps."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:33
msgid "Decompress the downloaded image."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:35
msgid ""
"On Windows you can use `7zip`_ to extract the file by right-clicking the "
"file to *Extract Here* (in the same directory)"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:42
msgid "Figure 1: 7zip extract here command"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:44
msgid "On Linux :"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:50
msgid "Delete the originally downloaded compressed file."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:53
msgid "Create a new |VB| virtual machine"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:55
msgid ""
"A new :abbr:`VM (Virtual Machine)` needs to be created in |VBM| where "
"|CL| will be installed. General instructions for creating a virtual "
"machine and details about using different settings are available in the "
"VirtualBox manual section `Creating Your First Virtual Machine`_."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:59
msgid "Launch the |VBM| from your host system."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:61
msgid "Click the :guilabel:`New` button to create a new VM."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:63
msgid "Choose :guilabel:`Expert mode`."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:65
msgid ""
"On the :guilabel:`Create Virtual Machine` screen, enter the following "
"settings:"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:67
msgid "**Name**: Choose name (e.g. ClearLinuxOS-VM)."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:68
msgid "**Type**: Linux"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:69
msgid "**Version**: **Linux 2.6 / 3.x / 4.x (64-bit)**"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:70
msgid "**Hard disk**: `Create a virtual hard disk now`"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:71
msgid "**Memory size default**: 2048 MB (Adjust appropriately.)"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:74
msgid ""
"Later, if you want to change the amount of RAM allocated, power down your"
" VM. Return to :file:`Settings > System` and change :guilabel:`Base "
"Memory` to the desired size."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:81
msgid "Figure 2: Create Virtual Machine"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:83
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:98
msgid "Click :guilabel:`Create`."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:85
msgid "On the :guilabel:`Create Virtual Hard Disk` screen, select:"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:87
msgid "**File location**"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:88
msgid "**File size**: **32.00 GB**. Adjust size to your needs."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:89
msgid "**Hard disk file type**: `VDI (VirtualBox Disk Image)`"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:90
msgid "**Storage on physical hard disk**:`Dynamically allocated`"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:96
msgid "Figure 3: Create Virtual Hard Disk"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:100
msgid "A new virtual machine will be created and appear in the |VBM|."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:102
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:218
msgid "Click :guilabel:`Settings` to configure the |CL| VM."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:104
msgid "In the left-hand menu, navigate to the :menuselection:`System` menu."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:106
msgid ""
"On the :guilabel:`Motherboard` tab, select the :guilabel:`Chipset` menu, "
"and then select :menuselection:`ICH9`. See Figure 4."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:111
msgid ""
"You can select which chipset will be presented to the virtual machine. "
"Consult the `VM VirtualBox User Manual`_ for more details."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:114
msgid "In :guilabel:`Enabled Features`, check these boxes:"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:116
msgid "**Enable I/O APIC**"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:117
msgid "**Enable EFI (special OSes only)**"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:123
msgid "Figure 4: Settings > System"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:127
msgid ""
"By default, only 1 virtual CPU is allocated to the new VM. Consider "
"increasing the number of virtual processors allocated to the virtual "
"machine under Settings > System > Processor for increased performance."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:132
msgid "Click :guilabel:`OK`."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:135
msgid "Install |CL| on the |VB| VM"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:137
msgid "|CL| is ready to be installed."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:140
msgid "Mount the installation ISO"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:142
msgid ""
"The |CL| installer ISO needs to be mounted as a virtual CD-ROM on the VM "
"before powering the VM on."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:145
msgid ""
"From the *ClearLinux-OS* :guilabel:`Settings` menu at left, select "
":guilabel:`Storage`."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:148
msgid ""
"From :guilabel:`Storage Devices`, middle column, click the blue disk "
"labeled :guilabel:`Empty`."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:151
msgid ""
"From the :guilabel:`Attributes` menu, click the blue CD disk next to the "
":guilabel:`Optical Drive` drop down menu and click :guilabel:`Choose "
"Virtual Optical Disk File...`"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:159
msgid "Figure 5: Choose Virtual Optical Disk Drive"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:161
msgid ""
"Where there appears :guilabel:`Please choose a virtual optical disk "
"file`, select the ISO file and click *Open*."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:168
msgid "Figure 6: Mounting an ISO"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:170
msgid "Click :guilabel:`OK` to exit and return to the main |VBM|."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:173
msgid "Install |CL| with live-server installer"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:175
msgid ""
"In the |VBM|, select virtual machine you created and click "
":guilabel:`Start`."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:181
msgid "Figure 7: Start the installer"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:185
msgid ""
"To release the mouse cursor from the VM console window, press the right "
":kbd:`Ctrl` key on the keyboard."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:188
msgid ""
"When :guilabel:`Clear Linux Installer` in boot manager appears, select "
":kbd:`Enter`. Do not install the bundle `desktop-autostart`."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:191
msgid ""
"Follow the steps in :ref:`bare-metal-install-server` to install |CL| onto"
" the VM virtual disk. Note:"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:194
msgid ""
"In :guilabel:`Configure Installation Media`, navigate top VBOX HARDDISK, "
"and then select :guilabel:`Confirm`."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:197
msgid ""
"In :menuselection:`Advanced options --> Manage User`, create an "
"administrative user."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:200
msgid "Do not install the bundle `desktop-autostart`."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:202
msgid "When |CL| installation is complete, click :guilabel:`Exit`."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:204
msgid "At the prompt, enter:"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:211
msgid "Unmount the ISO"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:213
msgid ""
"The |CL| installer ISO needs to be unmounted to allow the VM to boot from"
" the virtual hard disk."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:216
msgid "Return to the |VBM|."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:220
msgid ""
"From the VM :guilabel:`Settings` window, navigate to the "
":guilabel:`Storage` pane in the left menu."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:223
msgid ""
"From the middle :guilabel:`Storage Devices` column, click the blue CD "
"disk labeled :guilabel:`clear-<VERSION>-live-server.iso` under the "
":guilabel:`Controller: IDE`."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:227
msgid ""
"From the :guilabel:`Attributes` column at right, in :guilabel:`Optical "
"Drive`, select the blue CD icon beside and click :guilabel:`Remove Disk "
"from Virtual Drive`."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:235
msgid "Figure 8: Remove Disk from Virtual Drive"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:237
msgid ""
"Click :guilabel:`OK` to exit the :guilabel:`VM Settings` menu and return "
"to the main |VBM|."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:241
msgid "Install |VB| Linux Guest Additions"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:243
msgid ""
"|CL| provides Linux Guest Additions drivers for full compatibility using "
"an install script in the **kernel-lts** (Long Term Support) bundle by "
"|CL|."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:246
msgid "From the |VBM| select the |CL| VM, and select :guilabel:`Start`."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:248
msgid "In the VM Console, log in as the administrative user previously created."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:251
msgid ""
"A message may appear: \"A kernel update is available: you may wish to "
"reboot the system.\""
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:254
msgid "To update the kernel, enter:"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:260
msgid "At initial login, enter the administrative user's password and continue."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:262
msgid ""
"Validate the installed kernel is **kernel-lts** by checking the output of"
" the :command:`uname -r` command. It should end in **.lts** or "
"**.lts2018**."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:270
msgid ""
"If the running kernel is not **lts**: install the LTS kernel manually, "
"update the bootloader, and check again:"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:280
msgid ""
"Remove any kernel bundles that do not end in *-lts* or *kernel-install* "
"to simplify and avoid conflicts:"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:288
msgid ""
"In the VM Console top menu, click :guilabel:`Devices`, and select "
":guilabel:`Insert Guest Additions CD image...` to mount the |VB| driver "
"installation to the |CL| VM."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:296
msgid "Figure 9: Insert Guest Additions CD image"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:298
msgid ""
"If a dialogue appears, \"VBx_GAs_6.0.8... Would you like to run it?\", "
"select :guilabel:`Cancel`."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:301
msgid "Instead, we provide a script to patch and install |VB| drivers on |CL|."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:303
msgid "Open a Terminal and enter the script:"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:311
msgid ""
"Successful installation shows: \"Guest Additions installation complete\"."
" If drivers are already installed, don't re-install them."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:314
msgid "Shut down the system. Select :menuselection:`Machine --> ACPI Shutdown`."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:320
msgid "Figure 10: Powering off a VirtualBox VM"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:322
msgid "Select :guilabel:`Settings`, :guilabel:`Display`."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:324
msgid ""
"In :guilabel:`Graphics Controller`, select :guilabel:`VBoxSVGA` to adjust"
" screen size dynamically."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:331
msgid "Figure 11: VirtualBox hardware acceleration error"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:333
msgid "In the |VBM|, select :guilabel:`Start`."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:335
msgid "In the VM console, login and verify the |VB| drivers are loaded:"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:341
msgid ""
"You should see drivers loaded with names beginning with **vbox**: (e.g., "
"vboxvideo, vboxguest)."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:344
msgid "Add `desktop-autostart` for a full desktop experience."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:350
msgid "Reboot the VM and log in with the administrative user."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:356
msgid "The |CL| VM running on |VB| is ready to develop and explore."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:359
msgid "Troubleshooting"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:361
msgid ""
"**Problem:** On a Microsoft\\* Windows\\* OS, |VB| encounters an error "
"when trying to start a VM indicating *VT-X/AMD-v hardware acceleration is"
" not available on your system.*"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:369
msgid "Figure 12: VirtualBox hardware acceleration error"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:371
msgid ""
"**Solution:** First, double check the `Prerequisites`_ section to make "
"sure *Hardware accelerated virtualization* extensions have been enabled "
"in the host system's EFI/BIOS."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:375
msgid ""
"*Hardware accelerated virtualization*, may get disabled for |VB| when "
"another hypervisor, such as *Hyper-V* is enabled."
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:378
msgid ""
"To disable *Hyper-V* execute this command in an **Administrator: Command "
"Prompt or Powershell**, and reboot the system:"
msgstr ""
#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:385
msgid ""
"To enable Hyper-V again, execute this command in an **Administrator: "
"Command Prompt or Powershell**, and reboot the system:"
msgstr ""
#~ msgid ""
#~ "Oracle\\* VirtualBox\\* is a type 2 "
#~ "hypervisor. This document explains how "
#~ "to create a virtual machine on the"
#~ " `VirtualBox hypervisor`_ with |CL-ATTR|"
#~ " as the guest operating system. These"
#~ " instructions support use of the |CL|"
#~ " live-server installer to create |CL|"
#~ " virtual machine (VM)."
#~ msgstr ""
#~ msgid "Before continuing, assure you have:"
#~ msgstr ""
#~ msgid ""
#~ "Enabled virtualization, such as Intel® "
#~ "`Virtualization Technology`_ (Intel® VT), on"
#~ " the host system from EFI/BIOS."
#~ msgstr ""
#~ msgid ""
#~ "Downloaded and installed |VB| **version "
#~ "6.0 or greater** from the `official "
#~ "VirtualBox website`_ per the `appropriate "
#~ "instructions`_ for your platform."
#~ msgstr ""
#~ msgid ""
#~ "Download the :file:`clear-<VERSION>-live-"
#~ "server.iso.xz` of |CL| on the `downloads"
#~ " page`_."
#~ msgstr ""
#~ msgid ""
#~ "Validate the integrity of the downloaded"
#~ " image by checking the file hash "
#~ "and signatures. Refer :ref:`validate-"
#~ "signatures` for detailed steps."
#~ msgstr ""
#~ msgid ""
#~ "A new :abbr:`VM (Virtual Machine)` needs"
#~ " to be created in |VBM| where "
#~ "|CL| will be installed. General "
#~ "instructions for creating a virtual "
#~ "machine and details about using "
#~ "different settings are available on the"
#~ " `VirtualBox manual section on Creating "
#~ "a VM`_."
#~ msgstr ""
#~ msgid "Click the *New* button to create a new VM."
#~ msgstr ""
#~ msgid "In :guilabel:`Create Virtual Machine`, enter the following settings:"
#~ msgstr ""
#~ msgid "Select :guilabel:`Create`."
#~ msgstr ""
#~ msgid "In :guilabel:`Create Virtual Hard Disk`, select:"
#~ msgstr ""
#~ msgid "Click *Create*."
#~ msgstr ""
#~ msgid "Click *Settings* to configure the |CL| VM."
#~ msgstr ""
#~ msgid "In the left-hand menu, navigate to the :guilabel:`System` menu."
#~ msgstr ""
#~ msgid ""
#~ "In the :guilabel:`Motherboard` tab, select "
#~ "the `Chipset` pulldown menu, and then"
#~ " select :guilabel:`ICH9`. See Figure 4."
#~ msgstr ""
#~ msgid "Select :guilabel:`OK`."
#~ msgstr ""
#~ msgid ""
#~ "From the *ClearLinux-OS* :guilabel:`Settings`"
#~ " at left, select :guilabel:`Storage`."
#~ msgstr ""
#~ msgid ""
#~ "From :guilabel:`Storage Devices`, middle "
#~ "column, click the blue disk labeled "
#~ "*Empty*."
#~ msgstr ""
#~ msgid ""
#~ "From the :guilabel:`Attributes` menu, click"
#~ " the blue CD disk next to the"
#~ " *Optical Drive* drop down menu and"
#~ " click *Choose Virtual Optical Disk "
#~ "File...*"
#~ msgstr ""
#~ msgid "Select :guilabel:`OK` to exit and return to the main |VBM|."
#~ msgstr ""
#~ msgid "In the |VBM|, select virtual machine you created and click *Start*."
#~ msgstr ""
#~ msgid ""
#~ "In :guilabel:`Advanced options` > "
#~ ":guilabel:`Manage User`, create an "
#~ "administrative user."
#~ msgstr ""
#~ msgid "When |CL| installation is complete, select :guilabel:`Exit`."
#~ msgstr ""
#~ msgid ""
#~ "From the *VM - Settings* window, "
#~ "navigate to the *Storage* pane from "
#~ "the left-hand side."
#~ msgstr ""
#~ msgid ""
#~ "From the middle *Storage Devices* "
#~ "column, click the blue CD disk "
#~ "labeled *clear-<VERSION>-live-server.iso* under "
#~ "the *Controller: IDE* from."
#~ msgstr ""
#~ msgid ""
#~ "From the *Attributes* column at right,"
#~ " in *Optical Drive*, select the blue"
#~ " CD icon beside and click *Remove "
#~ "Disk from Virtual Drive*."
#~ msgstr ""
#~ msgid "Click *OK* to exit the *VM Settings* menu and return to the main |VBM|."
#~ msgstr ""
#~ msgid ""
#~ "In the VM Console top menu, click"
#~ " *Devices*, and select *Insert Guest "
#~ "Additions CD image...* to mount the "
#~ "|VB| driver installation to the |CL| "
#~ "VM."
#~ msgstr ""
#~ msgid "Shut down the system. Select :guilabel:`Machine>ACPI Shutdown`."
#~ msgstr ""
locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmw-player-preconf.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmw-player-preconf.po
-672
View File
@@ -1,672 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:4
msgid ""
"Run pre-configured |CL-ATTR| image as a VMware\\* Workstation Player "
"guest OS"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:6
msgid ""
"This page explains how to deploy a pre-configured |CL| VMware image on "
"`VMware Workstation 14 Player`_."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:14
msgid "Overview"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:16
msgid ""
"VMware Workstation 14 Player is a type 2 hypervisor. It runs on top of "
"another operating system such as Windows\\* or Linux\\*. With VMware "
"ESXi, you can create, configure, manage, and run |CL-ATTR| :abbr:`VMs "
"(Virtual Machines)` on your local system."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:23
msgid ""
"Screenshots in this document show VMware Workstation 14 Player for "
"Windows. Menus and prompts in the Linux version have minor wording "
"differences."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:27
msgid "Install the VMware Workstation Player hypervisor"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:29
msgid ""
"Enable :abbr:`Intel® VT (Intel® Virtualization Technology)` and "
":abbr:`Intel® VT-d (Intel® Virtualization Technology for Directed I/O)` "
"in your system's BIOS."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:33
msgid ""
"`VMware Workstation 14 Player`_ is available for Windows and Linux. "
"Download your preferred version."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:36
msgid ""
"Depending on which OS you're running, install it by following one of "
"these instructions:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:39
msgid "On supported Linux distros:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:41
msgid "Enable a GUI desktop."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:43
msgid "Start a terminal emulator."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:45
msgid ""
"Start the installer by issuing the command below and following the guided"
" steps."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:52
msgid "On Windows:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:54
msgid "Start the installer."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:55
msgid "Follow the setup wizard."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:57
msgid "For additional help, see the `VMware Workstation Player Documentation`_."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:60
msgid "Download the latest |CL| VMware image"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:62
msgid ""
"Get the latest |CL| VMware image from the `image`_ repository. Look for "
":file:`clear-[version number]-vmware.vmdk.xz`. You can also use this "
"command:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:70
msgid ""
"Visit :ref:`image-types` for additional information about all available "
"|CL| images."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:4
msgid "Verify the integrity of the |CL| image"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:6
msgid ""
"Before you use a downloaded |CL| image, verify its integrity. This action"
" eliminates the small chance of a corrupted image due to download issues."
" To support verification, each released |CL| image has a corresponding "
"SHA512 checksum file designated with the suffix `-SHA512SUMS`."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:11
msgid "Download the corresponding SHA512 checksum file of your |CL| `image`_."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:12
msgid "Start Command Prompt."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:13
msgid "Go to the directory with the downloaded image and checksum files."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:14
msgid "Get the SHA512 checksum of the image with the command:"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:20
msgid ""
"Manually compare the output with the original checksum value shown in the"
" downloaded checksum file and make sure they match."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:24
msgid "Decompress the |CL| image"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:26
msgid ""
"Released |CL| images are compressed with either GNU zip (*.gz*) or XZ "
"(*.xz*). The compression type depends on the target platform or "
"environment. To decompress the image, follow these steps:"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:30
msgid "Download and install `7-Zip`_."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:31
msgid "Go to the directory with the downloaded image and right-click it."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:32
msgid ""
"From the pop-up menu, select :guilabel:`7-Zip` and select "
":guilabel:`Extract Here` as shown in Figure 1."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:39
msgid "Figure 1: Windows 7-Zip extract file."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:44
msgid "Image types"
msgstr ""
#: ../../reference/image-types.rst:3
msgid ""
"Table 1 lists the currently available images that are platform "
"independent. Table 2 lists the currently available images that are "
"platform specific."
msgstr ""
#: ../../reference/image-types.rst:6
msgid "Table 1: Types of platform-independent |CL| images"
msgstr ""
#: ../../reference/image-types.rst:10 ../../reference/image-types.rst:23
msgid "Image Type"
msgstr ""
#: ../../reference/image-types.rst:11 ../../reference/image-types.rst:24
msgid "Description"
msgstr ""
#: ../../reference/image-types.rst:13
msgid "live-desktop.img or live-desktop.iso"
msgstr ""
#: ../../reference/image-types.rst:14
msgid "Image for booting to GNOME\\* desktop to preview or install the OS."
msgstr ""
#: ../../reference/image-types.rst:16
msgid "live-server.img or live-server.iso"
msgstr ""
#: ../../reference/image-types.rst:17
msgid "Image for booting to server command prompt to preview or install the OS."
msgstr ""
#: ../../reference/image-types.rst:19
msgid "Table 2: Types of platform-specific |CL| images"
msgstr ""
#: ../../reference/image-types.rst:26
msgid "aws.img"
msgstr ""
#: ../../reference/image-types.rst:27
msgid "Image suitable for use with Amazon\\* AWS\\*."
msgstr ""
#: ../../reference/image-types.rst:29
msgid "azure.vhd"
msgstr ""
#: ../../reference/image-types.rst:30
msgid "Virtual Hard Disk for use on Microsoft\\* Azure\\* cloud platform."
msgstr ""
#: ../../reference/image-types.rst:32
msgid "azure-docker.vhd"
msgstr ""
#: ../../reference/image-types.rst:33
msgid ""
"Virtual Hard Disk for use on Microsoft Azure cloud platform with "
"Docker\\* pre-installed."
msgstr ""
#: ../../reference/image-types.rst:35
msgid "azure-machine-learning.vhd"
msgstr ""
#: ../../reference/image-types.rst:36
msgid ""
"Virtual Hard Disk for use on Microsoft Azure cloud platform with the "
"`machine-learning-basic` bundle installed."
msgstr ""
#: ../../reference/image-types.rst:38
msgid "cloudguest.img"
msgstr ""
#: ../../reference/image-types.rst:39
msgid ""
"Image with generic cloud guest virtual machine (VM) requirements "
"installed."
msgstr ""
#: ../../reference/image-types.rst:41
msgid "gce.tar"
msgstr ""
#: ../../reference/image-types.rst:42
msgid "Image with the Google Compute Engine (GCE) specific kernel."
msgstr ""
#: ../../reference/image-types.rst:44
msgid "hyperv.vhdx"
msgstr ""
#: ../../reference/image-types.rst:45
msgid ""
"Virtual Hard Disk for use with Microsoft Hyper-V\\* hypervisor. Includes "
"`optimized kernel`_ for Hyper-V."
msgstr ""
#: ../../reference/image-types.rst:47
msgid "kvm.img"
msgstr ""
#: ../../reference/image-types.rst:48
msgid ""
"Image for booting in a simple VM with start_qemu.sh. Includes `optimized "
"kernel`_ for KVM."
msgstr ""
#: ../../reference/image-types.rst:51
msgid "kvm-legacy.img"
msgstr ""
#: ../../reference/image-types.rst:52
msgid ""
"Image for booting in a simple VM using legacy BIOS, if using "
"start_qemu.sh make sure to remove -bios parameter."
msgstr ""
#: ../../reference/image-types.rst:54
msgid "pxe.tar"
msgstr ""
#: ../../reference/image-types.rst:55
msgid "Image suitable for use with PXE server."
msgstr ""
#: ../../reference/image-types.rst:57
msgid "vmware.vmdk"
msgstr ""
#: ../../reference/image-types.rst:58
msgid ""
"Virtual Machine Disk for VMware\\* platforms inclduing Player, "
"Workstation, and ESXi."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:75
msgid "We also provide instructions for other operating systems:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:77
msgid ":ref:`download-verify-decompress-linux`"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:80
msgid "Create and configure a new VM"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:82
msgid "Start the `VMware Workstation Player` app."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:83
msgid ""
"On the home screen, click :guilabel:`Create a New Virtual Machine`. See "
"figure 1."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:90
msgid "Figure 1: VMware Workstation 14 Player - Create a new virtual machine"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:92
msgid ""
"On the :guilabel:`Welcome to the New Virtual Machine Wizard` screen, "
"select the :guilabel:`I will install the operating system later` option. "
"See figure 2."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:100
msgid ""
"Figure 2: VMware Workstation 14 Player - Select install operating system "
"later."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:103
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:119
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:130
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:229
msgid "Click the :guilabel:`Next` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:105
msgid ""
"On the :guilabel:`Select a Guest Operating System` screen, set the "
":guilabel:`Guest operating system` setting to :guilabel:`Linux`. See "
"figure 3."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:113
msgid ""
"Figure 3: VMware Workstation 14 Player - Select guest operating system "
"type"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:116
msgid ""
"Set :guilabel:`Version` setting to :guilabel:`Other Linux 3.x or later "
"kernel 64-bit`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:121
msgid ""
"On the :guilabel:`Name the Virtual Machine` screen, give your new VM a "
"name. See figure 4."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:128
msgid "Figure 4: VMware Workstation 14 Player - Name virtual machine"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:132
msgid ""
"On the :guilabel:`Specify Disk Capacity` screen, click the "
":guilabel:`Next` button. Keep the default disk settings unchanged. When "
"we attach the pre-configured |CL| VMware image, we will remove the "
"default virtual disk and replace it with the pre-configured one. See "
"figure 5."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:142
msgid "Figure 5: VMware Workstation 14 Player - Set disk capacity"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:144
msgid ""
"On the :guilabel:`Ready to Create Virtual Machine` screen, click the "
":guilabel:`Customize Hardware...` button. See figure 6."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:151
msgid "Figure 6: VMware Workstation 14 Player - Customize hardware"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:153
msgid ""
"Under the :guilabel:`Device` list, select :guilabel:`Processors`. See "
"figure 7."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:160
msgid "Figure 7: VMware Workstation 14 Player - Set virtualization engine option"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:163
msgid ""
"Under the :guilabel:`Virtualization engine` section, check "
":guilabel:`Virtualize Intel VT-x/EPT or AMD-V/RVI`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:166
msgid ""
"To disconnect the virtual CD/DVD (IDE) since it is not needed, under the "
":guilabel:`Device` list, select :guilabel:`New CD/DVD (IDE)`. See figure "
"8."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:173
msgid "Figure 8: VMware Workstation 14 Player - Disconnect CD/DVD (IDE)"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:175
msgid ""
"Under the :guilabel:`Device status` section, uncheck :guilabel:`Connect "
"at power on`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:178
msgid "Click the :guilabel:`Close` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:180
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:257
msgid "Click the :guilabel:`Finish` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:183
msgid "Attach the pre-configured |CL| VMware image"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:185
msgid ""
"Move the downloaded and decompressed pre-configured |CL| VMware image "
"file :file:`clear-[version number]-basic.vmdk` to the directory where "
"your newly-created VM resides."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:191
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:276
msgid "Depending on the OS, you can typically find the VMware VM files under:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:193
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:278
msgid "On Linux distros: :file:`/home/username/vmware`"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:194
msgid "On Windows: :file:`C:\\Users\\username\\Documents\\Virtual Machines`"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:196
msgid ""
"On the :guilabel:`VMware Workstation Player` home screen, select your "
"newly-created VM. See figure 9."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:203
msgid "Figure 9: VMware Workstation 14 Player - Edit virtual machine settings"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:205
msgid "Click :guilabel:`Edit virtual machine settings`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:207
msgid ""
"To remove the default hard disk, under the :guilabel:`Device` list, "
"select :guilabel:`Hard Disk (SCSI)`. See figure 10."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:214
msgid "Figure 10: VMware Workstation 14 Player - Remove hard drive"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:216
msgid "Click the :guilabel:`Remove` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:218
msgid ""
"To add a new hard disk and attach the pre-configured |CL| VMware image, "
"click the :guilabel:`Add...` button. See Figure 11."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:225
msgid "Figure 11: VMware Workstation 14 Player - Add new hard drive"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:227
msgid ""
"Under the :guilabel:`Hardware types` section, select :guilabel:`Hard "
"Disk`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:231
msgid "Select your preferred :guilabel:`Virtual disk type`. See figure 12."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:237
msgid "Figure 12: VMware Workstation 14 Player - Select virtual disk type"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:239
msgid "Select the :guilabel:`Use an existing virtual disk` option. See figure 13."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:245
msgid "Figure 13: VMware Workstation 14 Player - Use existing virtual disk"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:247
msgid ""
"Click the :guilabel:`Browse` button and select the pre-configured |CL| "
"VMware image file. See figure 14."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:254
msgid ""
"Figure 14: VMware Workstation 14 Player - Select ready-made VMware |CL| "
"image file"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:261
msgid ""
"When asked to convert the existing virtual disk to a newer format, "
"selecting either option works."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:265
msgid "Enable UEFI boot support"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:267
msgid ""
"|CL| needs UEFI support to boot.To enable it, add the following line to "
"the end of your VM's :file:`.vmx` file:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:279
msgid ""
"On Windows: :file:`C:\\\\Users\\\\username\\\\Documents\\\\Virtual "
"Machines`"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:282
msgid "Power on the VM"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:284
msgid "After configuring the settings above, power on your |CL| virtual machine."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:286
msgid ""
"On the :guilabel:`VMware Workstation Player` home screen, select your VM."
" See figure 15."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:293
msgid "Figure 15: VMware Workstation 14 Player - Power on virtual machine"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:295
msgid "Click :guilabel:`Play virtual machine`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:298
msgid "Related topics"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:300
msgid "For other guides on using the VMWare Player and ESXi, see:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:302
msgid ":ref:`vmw-player`"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:303
msgid ":ref:`vmware-esxi-install-cl`"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:304
msgid ":ref:`vmware-esxi-preconfigured-cl-image`"
msgstr ""
#~ msgid ""
#~ "`VMware Workstation 14 Player`_ is a "
#~ "type 2 hypervisor. It runs on top"
#~ " of another operating system such as"
#~ " Windows\\* or Linux\\*. With VMware "
#~ "ESXi, you can create, configure, manage,"
#~ " and run |CL-ATTR| :abbr:`VMs "
#~ "(Virtual Machines)` on your local "
#~ "system."
#~ msgstr ""
#~ msgid ""
#~ "This section shows how to deploy a"
#~ " pre-configured |CL| VMware image on"
#~ " VMware Workstation 14 Player."
#~ msgstr ""
#~ msgid "In this tutorial, we perform the following steps:"
#~ msgstr ""
#~ msgid ""
#~ "The screenshots on this document show"
#~ " the Windows version of the VMware"
#~ " Workstation 14 Player. The menus and"
#~ " prompts are similar to those in "
#~ "the Linux version save some minor "
#~ "wording differences."
#~ msgstr ""
#~ msgid "For additional help, see the `VMware Workstation Player guide`_."
#~ msgstr ""
#~ msgid "Download the corresponding SHA512 checksum file of your |CL| image."
#~ msgstr ""
#~ msgid ":ref:`download-verify-decompress-mac`"
#~ msgstr ""
locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmw-player.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmw-player.po
-656
View File
@@ -1,656 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../get-started/virtual-machine-install/vmw-player.rst:4
msgid "Install |CL-ATTR| as a VMware\\* Workstation Player guest OS"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:6
msgid ""
"This page explains how to create a new VM and install |CL| on it with the"
" VMware Workstation Player hypervisor."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:14
msgid "Overview"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:16
msgid ""
"`VMware Workstation Player`_ is a type 2 hypervisor. It runs on top of "
"Windows\\* or Linux\\* operating systems. With VMware ESXi, you can "
"create, configure, manage, and run |CL-ATTR| :abbr:`VMs (Virtual "
"Machines)` on your local system."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:21
msgid ""
"VMware offers a type 1 hypervisor called `VMware ESXi`_ designed for the "
"cloud environment. For information on how to install |CL| as guest OS on "
"it, see :ref:`vmware-esxi-install-cl`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:27
msgid ""
"The screenshots on this document show the Windows version of the VMware "
"Workstation 15 Player. The menus and prompts are similar to those in "
"other versions and for the Linux OS save some minor wording differences."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:31
msgid ""
"If you prefer to use a pre-configured |CL| VMware image instead, see our "
":ref:`vmw-player-preconf` guide."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:35
msgid "Install the VMware Workstation Player hypervisor"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:37
msgid ""
"Enable :abbr:`Intel® VT (Intel® Virtualization Technology)` and "
":abbr:`Intel® VT-d (Intel® Virtualization Technology for Directed I/O)` "
"in your system's BIOS."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:41
msgid ""
"`VMware Workstation Player`_ is available for Windows and Linux. Download"
" your preferred version."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:46
msgid ""
"By default, selecting download means you receive the latest version of "
"this application. Commands may differ based on the version."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:49
msgid ""
"Install VMware Workstation Player following the instructions appropriate "
"for your system's OS:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:52
msgid "On supported Linux distros:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:54
msgid "Enable a GUI desktop."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:55
msgid "Start a terminal emulator."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:56
msgid ""
"Start the installer by issuing the command below and follow the guided "
"steps."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:63
msgid "On Windows:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:65
msgid "Start the installer."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:66
msgid "Follow the setup wizard."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:68
msgid "For additional help, see the `VMware Workstation Player Documentation`_."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:71
msgid "Download the latest |CL| installer"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:73
msgid "Get the latest installer with |CL| OS Desktop from the `downloads`_ page."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:75
msgid ""
"Visit :ref:`image-types` for additional information about all available "
"|CL| images."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:77
msgid ""
"We also provide instructions for downloading and verifying a Clear Linux "
"ISO. For more information, refer to :ref:`download-verify-decompress`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:81
msgid "Create and configure a new VM"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:83
msgid "Start the `VMware Workstation Player` app."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:85
msgid ""
"On the home screen, click :guilabel:`Create a New Virtual Machine`. See "
"Figure 1."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:92
msgid "Figure 1: VMware Workstation Player - Create a new virtual machine"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:95
msgid ""
"On the :guilabel:`Welcome to the New Virtual Machine Wizard` screen, "
"select the :guilabel:`Installer disc image file (iso)` option. See Figure"
" 2."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:103
msgid "Figure 2: VMware Workstation Player - Select |CL| installer ISO"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:105
msgid ""
"Click the :guilabel:`Browse` button and select the decompressed |CL| "
"installer ISO."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:108
#: ../../get-started/virtual-machine-install/vmw-player.rst:124
#: ../../get-started/virtual-machine-install/vmw-player.rst:135
#: ../../get-started/virtual-machine-install/vmw-player.rst:151
msgid "Click the :guilabel:`Next` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:110
msgid ""
"On the :guilabel:`Select a Guest Operating System`, set the "
":guilabel:`Guest operating system` setting to :guilabel:`Linux`. See "
"Figure 3."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:118
msgid "Figure 3: VMware Workstation Player - Select guest operating system type"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:121
msgid ""
"Set the :guilabel:`Version` setting to :guilabel:`Other Linux 4.x or "
"later kernel 64-bit`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:126
msgid ""
"On the :guilabel:`Name the Virtual Machine` screen, name the new VM. See "
"Figure 4."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:133
msgid "Figure 4: VMware Workstation Player - Name virtual machine"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:137
msgid ""
"On the :guilabel:`Specify Disk Capacity` screen, set the VM's maximum "
"disk size. See Figure 5."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:144
msgid "Figure 5: VMware Workstation Player - Set disk capacity"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:148
msgid ""
"For optimal performance with the |CL| Desktop image, we recommend 32GB of"
" drive space. See :ref:`system-requirements` for more details."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:153
msgid ""
"On the :guilabel:`Ready to Create Virtual Machine` screen, click the "
":guilabel:`Customize Hardware...` button. See Figure 6."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:160
msgid "Figure 6: VMware Workstation Player - Customize hardware"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:162
msgid "Select :guilabel:`Memory` and set the size to 2GB. See Figure 7."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:168
msgid "Figure 7: VMware Workstation Player - Set memory size"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:171
msgid ""
"The |CL| installer ISO needs a minimum of 2GB of RAM. After completing "
"installation, |CL| can run on as little as 128MB of RAM. Thus, you can "
"reduce the memory size if needed. See :ref:`system-requirements` for more"
" details."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:176
msgid ""
"Under the :guilabel:`Device` list, select :guilabel:`Processors`. See "
"Figure 8."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:183
msgid "Figure 8: VMware Workstation Player - Set virtualization engine option"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:186
msgid ""
"Under the :guilabel:`Virtualization engine` section, check "
":guilabel:`Virtualize Intel VT-x/EPT or AMD-V/RVI`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:189
msgid "Click the :guilabel:`Close` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:191
msgid "Click the :guilabel:`Finish` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:194
msgid "Install |CL| into the new VM"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:196
msgid ""
"Select the newly-created VM and click the :guilabel:`Play virtual "
"machine` button. See Figure 9."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:203
msgid "Figure 9: VMware Workstation Player - Power on virtual machine"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:205
msgid ""
"Follow the :ref:`install-on-target-start` guide to complete the "
"installation of |CL|."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:208
msgid ""
"After the installation completes, reboot the VM. This reboot restarts the"
" |CL| installer."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:212
msgid "Detach the |CL| installer ISO from the VM"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:214
msgid ""
"To enable the mouse pointer so you access VMware Workstation Player's "
"menus, press :kbd:`<CTRL>` + :kbd:`<ALT>` on the keyboard."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:217
msgid ""
"To disconnect the CD/DVD to stop it from booting the |CL| installer ISO "
"again, click the :guilabel:`Player` menu. See Figure 10."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:224
msgid "Figure 10: VMware Workstation Player - Edit CD/DVD settings"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:226
msgid "Go to :menuselection:`Removable Devices-->CD/DVD (IDE)-->Disconnect`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:228
msgid "Click the :guilabel:`OK` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:231
msgid "Enable UEFI boot support"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:233
msgid "|CL| needs UEFI support to boot. To enable UEFI:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:235
msgid "Power off the VM. click the :guilabel:`Player` menu. See Figure 11."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:241
msgid "Figure 11: VMware Workstation Player - Power off virtual machine"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:243
msgid "Go to :guilabel:`Power` and select :guilabel:`Shut Down Guest`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:245
msgid "Add the following line to the end of your VM's :file:`.vmx` file:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:253
msgid "Depending on the OS, you can typically find the VMware VM files under:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:255
msgid "On Linux distros: :file:`/home/username/vmware`"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:256
msgid ""
"On Windows: :file:`C:\\\\Users\\\\username\\\\Documents\\\\Virtual "
"Machines`"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:259
msgid ""
"After configuring the settings above, power on your |CL| virtual machine."
" On the :guilabel:`VMware Workstation Player` home screen, select your "
"VM. See Figure 9."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:263
msgid "Click :guilabel:`Play virtual machine`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:265
msgid ""
"Install Open VM Tools. You may want to install the `open-vm-tools` in "
"your virtual machine. The Open Virtual Machine Tools (open-vm-tools) are "
"the open source implementation of VMware Tools for Linux guest operating "
"systems. In |CL| you can use the following to install the bundle in your "
"VM"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:275
msgid ""
"More information is available on the `VMWare Tools Product "
"Documentation`_ site."
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:278
msgid "Related topics"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:280
msgid "For other guides on using the VMWare Player and ESXi, see:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:282
msgid ":ref:`vmw-player-preconf`"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:283
msgid ":ref:`vmware-esxi-install-cl`"
msgstr ""
#: ../../get-started/virtual-machine-install/vmw-player.rst:284
msgid ":ref:`vmware-esxi-preconfigured-cl-image`"
msgstr ""
#~ msgid ""
#~ "This section shows how to create a"
#~ " new VM and install |CL| into "
#~ "it with the VMware Workstation 14 "
#~ "Player hypervisor. Installing |CL| into "
#~ "a new VM provides you flexibility "
#~ "when configuring the VM. You can "
#~ "configure the VM's size, number of "
#~ "partitions, installed bundles, etc."
#~ msgstr ""
#~ msgid "In this tutorial, we perform the following steps:"
#~ msgstr ""
#~ msgid ""
#~ "The screenshots on this document show"
#~ " the Windows version of the VMware"
#~ " Workstation 14 Player. The menus and"
#~ " prompts are similar to those in "
#~ "the Linux version save some minor "
#~ "wording differences."
#~ msgstr ""
#~ msgid "For additional help, see the `VMware Workstation Player guide`_."
#~ msgstr ""
#~ msgid ""
#~ "This page explains how to create a"
#~ " new VM and install |CL| on it"
#~ " with the VMware Workstation 14 "
#~ "Player hypervisor."
#~ msgstr ""
#~ msgid ""
#~ "`VMware Workstation 14 Player`_ is a "
#~ "type 2 hypervisor. It runs on top"
#~ " of another operating system such as"
#~ " Windows\\* or Linux\\*. With VMware "
#~ "ESXi, you can create, configure, manage,"
#~ " and run |CL-ATTR| :abbr:`VMs "
#~ "(Virtual Machines)` on your local "
#~ "system."
#~ msgstr ""
#~ msgid ""
#~ "Installing |CL| into a new VM "
#~ "provides you flexibility when configuring "
#~ "the VM. You can configure the VM's"
#~ " size, number of partitions, installed "
#~ "bundles, etc."
#~ msgstr ""
#~ msgid ""
#~ "Screenshots in this document show VMware"
#~ " Workstation 14 Player for Windows. "
#~ "Menus and prompts in the Linux "
#~ "version have minor wording differences."
#~ msgstr ""
#~ msgid ""
#~ "`VMware Workstation 14 Player`_ is "
#~ "available for Windows and Linux. "
#~ "Download your preferred version."
#~ msgstr ""
#~ msgid ""
#~ "Install VMware Workstation 14 Player "
#~ "following the instructions appropriate for "
#~ "your system's OS:"
#~ msgstr ""
#~ msgid "Download the latest |CL| installer ISO"
#~ msgstr ""
#~ msgid ""
#~ "Get the latest |CL| installer ISO "
#~ "image from the `image`_ repository. Look"
#~ " for :file:`clear-[version number]-installer.iso.xz`."
#~ msgstr ""
#~ msgid "Verify the integrity of the |CL| image"
#~ msgstr ""
#~ msgid ""
#~ "Before you use a downloaded |CL| "
#~ "image, verify its integrity. This action"
#~ " eliminates the small chance of a "
#~ "corrupted image due to download issues."
#~ " To support verification, each released "
#~ "|CL| image has a corresponding SHA512"
#~ " checksum file designated with the "
#~ "suffix `-SHA512SUMS`."
#~ msgstr ""
#~ msgid "Download the corresponding SHA512 checksum file of your |CL| image."
#~ msgstr ""
#~ msgid "Start Command Prompt."
#~ msgstr ""
#~ msgid "Go to the directory with the downloaded image and checksum files."
#~ msgstr ""
#~ msgid "Get the SHA512 checksum of the image with the command:"
#~ msgstr ""
#~ msgid ""
#~ "Manually compare the output with the "
#~ "original checksum value shown in the "
#~ "downloaded checksum file and make sure"
#~ " they match."
#~ msgstr ""
#~ msgid "Decompress the |CL| image"
#~ msgstr ""
#~ msgid ""
#~ "Released |CL| images are compressed with"
#~ " either GNU zip (*.gz*) or XZ "
#~ "(*.xz*). The compression type depends on"
#~ " the target platform or environment. "
#~ "To decompress the image, follow these"
#~ " steps:"
#~ msgstr ""
#~ msgid "Download and install `7-Zip`_."
#~ msgstr ""
#~ msgid "Go to the directory with the downloaded image and right-click it."
#~ msgstr ""
#~ msgid ""
#~ "From the pop-up menu, select "
#~ ":guilabel:`7-Zip` and select :guilabel:`Extract "
#~ "Here` as shown in Figure 1."
#~ msgstr ""
#~ msgid "Figure 1: Windows 7-Zip extract file."
#~ msgstr ""
#~ msgid "We also provide instructions for other operating systems:"
#~ msgstr ""
#~ msgid ":ref:`download-verify-decompress-linux`"
#~ msgstr ""
#~ msgid ":ref:`download-verify-decompress-mac`"
#~ msgstr ""
#~ msgid "Figure 1: VMware Workstation 14 Player - Create a new virtual machine"
#~ msgstr ""
#~ msgid "Figure 2: VMware Workstation 14 Player - Select |CL| installer ISO"
#~ msgstr ""
#~ msgid ""
#~ "Figure 3: VMware Workstation 14 Player"
#~ " - Select guest operating system type"
#~ msgstr ""
#~ msgid ""
#~ "Set the :guilabel:`Version` setting to "
#~ ":guilabel:`Other Linux 3.x or later "
#~ "kernel 64-bit`."
#~ msgstr ""
#~ msgid "Figure 4: VMware Workstation 14 Player - Name virtual machine"
#~ msgstr ""
#~ msgid "Figure 5: VMware Workstation 14 Player - Set disk capacity"
#~ msgstr ""
#~ msgid ""
#~ "A minimal |CL| installation can exist"
#~ " on 600MB of drive space. See "
#~ ":ref:`system-requirements` for more details."
#~ msgstr ""
#~ msgid "Figure 6: VMware Workstation 14 Player - Customize hardware"
#~ msgstr ""
#~ msgid "Figure 7: VMware Workstation 14 Player - Set memory size"
#~ msgstr ""
#~ msgid ""
#~ "Figure 8: VMware Workstation 14 Player"
#~ " - Set virtualization engine option"
#~ msgstr ""
#~ msgid "Figure 9: VMware Workstation 14 Player - Power on virtual machine"
#~ msgstr ""
#~ msgid "Figure 10: VMware Workstation 14 Player - Edit CD/DVD settings"
#~ msgstr ""
#~ msgid "Go to :menuselection:`Removable Devices-->CD/DVD (IDE)-->Settings`."
#~ msgstr ""
#~ msgid ""
#~ "On the :guilabel:`Device status` section, "
#~ "uncheck the :guilabel:`Connected` and the "
#~ ":guilabel:`Connect at power on` settings. "
#~ "See Figure 11."
#~ msgstr ""
#~ msgid "Figure 11: VMware Workstation 14 Player - Disconnect CD/DVD"
#~ msgstr ""
#~ msgid "To power off the VM, click the :guilabel:`Player` menu. See Figure 12."
#~ msgstr ""
#~ msgid "Figure 12: VMware Workstation 14 Player - Power off virtual machine"
#~ msgstr ""
#~ msgid ""
#~ "|CL| needs UEFI support to boot. "
#~ "To enable UEFI, add the following "
#~ "line to the end of your VM's "
#~ ":file:`.vmx` file:"
#~ msgstr ""
#~ msgid "Power on the VM"
#~ msgstr ""
#~ msgid ""
#~ "After configuring the settings above, "
#~ "power on your |CL| virtual machine."
#~ msgstr ""
#~ msgid ""
#~ "On the :guilabel:`VMware Workstation Player`"
#~ " home screen, select your VM. See "
#~ "Figure 13."
#~ msgstr ""
#~ msgid "Figure 13: VMware Workstation 14 Player - Power on virtual machine"
#~ msgstr ""
locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-install-cl.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-install-cl.po
-519
View File
@@ -1,519 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:4
msgid "Install |CL-ATTR| as a VMware\\* ESXi guest OS"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:6
msgid ""
"This page explains how to create a new :abbr:`VM (Virtual Machine)` and "
"manually install |CL-ATTR| on the new VM with VMware ESXi 6.5."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:14
msgid "Overview"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:16
msgid ""
"`VMware ESXi`_ is a type 1 bare-metal hypervisor that runs directly on "
"top of server hardware. With VMware ESXi, you can create, configure, "
"manage, and run |CL| virtual machines in the cloud."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:20
msgid ""
"Manually installing |CL| on a new VM gives additional configuration "
"flexibility during installation. For example: alternate disk sizes, "
"number of partitions, pre-installed bundles, etc."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:24
msgid ""
"If you prefer to use a preconfigured |CL| VMware image instead, refer to "
":ref:`vmware-esxi-preconfigured-cl-image`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:29
msgid ""
"VMware also offers a type 2 hypervisor designed for the desktop "
"environment, called `VMware Workstation Player`_. Refer to :ref:`vmw-"
"player-preconf` or :ref:`vmw-player` for more information."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:33
msgid "Visit :ref:`image-types` to learn more about all available images."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:36
msgid "Download the latest |CL| installer ISO"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:38
msgid ""
"Get the latest |CL| installer ISO image from the `image`_ repository. "
"Look for :file:`clear-[version number]-installer.iso.xz`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:41
msgid ""
"We also provide instructions for downloading and verifying a Clear Linux "
"ISO. For more information, refer to :ref:`download-verify-decompress`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:45
msgid "Upload the |CL| installer ISO to the VMware server"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:47
msgid ""
"Connect to the VMware server and log into an account with sufficient "
"permission to create and manage VMs."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:49
msgid ""
"Under the :guilabel:`Navigator` window, select :guilabel:`Storage`. See "
"Figure 1."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:51
msgid ""
"Under the :guilabel:`Datastores` tab, click the :guilabel:`Datastore "
"browser` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:58
msgid "Figure 1: VMware ESXi - Navigator > Storage"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:60
msgid ""
"Click the :guilabel:`Create directory` button and name the directory "
"`ISOs`. See Figure 2."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:67
msgid "Figure 2: VMware ESXi - Datastore > Create directory"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:69
msgid ""
"Select the newly-created directory and click the :guilabel:`Upload` "
"button. See Figure 3."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:76
msgid "Figure 3: VMware ESXi - Datastore > Upload ISO"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:78
msgid ""
"Select the decompressed |CL| installer ISO file :file:`clear-[version "
"number]-installer.iso` and upload it."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:82
msgid "Create and configure a new VM"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:84
msgid ""
"In this section, you will create a new VM, configure its basic parameters"
" such as drive size, number of CPUs, memory size, and then attach the "
"|CL| installer ISO."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:87
msgid ""
"Under the :guilabel:`Navigator` window, select :guilabel:`Virtual "
"Machines`. See Figure 4."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:89
msgid "In the right window, click the :guilabel:`Create / Register VM` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:95
msgid "Figure 4: VMware ESXi - Navigator > Virtual Machines"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:97
msgid "On the :guilabel:`Select creation type` step:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:99
msgid "Select the :guilabel:`Create a new virtual machine` option. See Figure 5."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:101
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:115
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:126
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:179
msgid "Click the :guilabel:`Next` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:107
msgid "Figure 5: VMware ESXi - Create a new virtual machine"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:109
msgid "On the :guilabel:`Select a name and guest OS` step:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:111
msgid "Give the new VM a name in the :guilabel:`Name` field. See Figure 6."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:112
msgid ""
"Set the :guilabel:`Compatability` option to :guilabel:`ESXi 6.5 virtual "
"machine`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:113
msgid "Set the :guilabel:`Guest OS family` option to :guilabel:`Linux`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:114
msgid ""
"Set the :guilabel:`Guest OS version` option to :guilabel:`Other 3.x or "
"later Linux (64-bit)`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:121
msgid "Figure 6: VMware ESXi - Give a name and select guest OS type"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:123
msgid "On the :guilabel:`Select storage` step:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:125
msgid "Accept the default option."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:128
msgid "On the :guilabel:`Customize settings` step:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:130
msgid "Click the :guilabel:`Virtual Hardware` button. See Figure 7."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:131
msgid ""
"Expand the :guilabel:`CPU` setting and enable :guilabel:`Hardware "
"virtualization` by checking :guilabel:`Expose hardware assisted "
"virtualization to the guest OS`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:138
msgid "Figure 7: VMware ESXi - Enable hardware virtualization"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:140
msgid "Set :guilabel:`Memory` size to 2048MB (2GB). See Figure 8."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:146
msgid "Figure 8: VMware ESXi - Set memory size"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:150
msgid ""
"The |CL| installer ISO needs a minimum of 2GB of RAM to work properly. "
"You can reduce the memory size after the installation completes if you "
"want, because a minimum |CL| installation can function on as little as "
"128MB of RAM. See :ref:`system-requirements` for more details."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:155
msgid "Set :guilabel:`Hard disk 1` to the desired capacity. See Figure 9."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:161
msgid "Figure 9: VMware ESXi - Set hard disk size"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:165
msgid ""
"A minimum |CL| installation can exist on 600MB of drive space. See :ref"
":`system-requirements` for more details."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:168
msgid ""
"Attach the |CL| installer ISO. For the :guilabel:`CD/DVD Drive 1` "
"setting, click the drop-down list to the right of it and select the "
":guilabel:`Datastore ISO file` option. Then select the |CL| installer "
"ISO :file:`clear-[version number]-installer.iso` that you previously "
"uploaded to the VMware server. See Figure 10."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:177
msgid "Figure 10: VMware ESXi - Set CD/DVD to boot installer ISO"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:180
msgid "Click the :guilabel:`Finish` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:183
msgid "Install |CL| into the new VM"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:185
msgid "Power on the VM."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:187
msgid ""
"Under the :guilabel:`Navigator` window, select :guilabel:`Virtual "
"Machines`. See Figure 11."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:189
msgid "In the right window, select the newly-created VM."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:190
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:270
msgid "Click the :guilabel:`Power on` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:191
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:271
msgid ""
"Click on the icon representing the VM to bring it into view and maximize "
"its window."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:198
msgid "Figure 11: VMware ESXi - Navigator > Virtual Machines > Power on VM"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:200
msgid ""
"Follow the :ref:`install-on-target-start` guide to complete the "
"installation of |CL|."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:202
msgid ""
"After the installation is complete, follow the |CL| instruction to reboot"
" it. This will restart the installer again."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:206
msgid "Reconfigure the VM's settings to boot the newly-installed |CL|"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:208
msgid ""
"After |CL| has been installed using the installer ISO, it must be "
"detached so it will not run again. Also, in order to boot the newly-"
"installed |CL|, you must enable UEFI support."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:212
msgid "Power off the VM."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:214
msgid ""
"Click the :guilabel:`Actions` button - located on the top-right corner of"
" the VM's windows - and go to the :guilabel:`Power` setting and select "
"the :guilabel:`Power off` option. See Figure 12."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:222
msgid "Figure 12: VMware ESXi - Actions > Power off"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:224
msgid "Edit the VM settings."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:226
msgid ""
"Click the :guilabel:`Actions` button again and select :guilabel:`Edit "
"settings`. See Figure 13."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:233
msgid "Figure 13: VMware ESXi - Actions > Edit settings"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:235
msgid ""
"Disconnect the CD/DVD to stop it from booting the |CL| installer ISO "
"again."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:237
msgid "Click the :guilabel:`Virtual Hardware` button. See Figure 14."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:238
msgid ""
"For the :guilabel:`CD/DVD Drive 1` setting, uncheck the "
":guilabel:`Connect` checkbox."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:245
msgid "Figure 14: VMware ESXi - Disconnect the CD/DVD drive"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:247
msgid "|CL| needs UEFI support in order to boot. Enable it."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:249
msgid "Click the :guilabel:`VM Options` button. See Figure 15."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:250
msgid "Expand the :guilabel:`Boot Options` setting."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:251
msgid ""
"For the :guilabel:`Firmware` setting, click the drop-down list to the "
"right of it and select the :guilabel:`EFI` option."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:258
msgid "Figure 15: VMware ESXi - Set boot firmware to EFI"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:260
msgid "Click the :guilabel:`Save` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:263
msgid "Power on the VM and boot |CL|"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:265
msgid "After configuring the settings above, power on the VM."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:267
msgid ""
"Under the :guilabel:`Navigator` window, select :guilabel:`Virtual "
"Machines`. See Figure 16."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:269
msgid "In the right window, select the VM."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:278
msgid "Figure 16: VMware ESXi - Navigator > Virtual Machines > Power on VM"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:281
msgid "Related topics"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:283
msgid ":ref:`vmware-esxi-preconfigured-cl-image`"
msgstr ""
#~ msgid ""
#~ "`VMware ESXi`_ is a type 1 "
#~ "bare-metal hypervisor which runs directly"
#~ " on top of server hardware. With "
#~ "VMware ESXi, you can create, configure,"
#~ " manage, and run |CL-ATTR| virtual"
#~ " machines in the cloud."
#~ msgstr ""
#~ msgid ""
#~ "This section shows you how to "
#~ "create a new :abbr:`VM (Virtual "
#~ "Machine)` and manually install |CL| into"
#~ " it with VMware ESXi 6.5."
#~ msgstr ""
#~ msgid ""
#~ "Manually installing |CL| into a new "
#~ "VM provides you some additional "
#~ "configuration flexibility during installation. "
#~ "For example: alternate disk sizes, "
#~ "number of partitions, pre-installed "
#~ "bundles, etc."
#~ msgstr ""
#~ msgid ""
#~ "If you would prefer to use a "
#~ "preconfigured |CL| VMware image instead, "
#~ "see :ref:`vmware-esxi-preconfigured-cl-"
#~ "image`."
#~ msgstr ""
#~ msgid ""
#~ "VMware also offers a type 2 "
#~ "hypervisor called `VMware Workstation Player`_"
#~ " which is designed for the desktop"
#~ " environment."
#~ msgstr ""
#~ msgid "See :ref:`vmw-player-preconf` or see :ref:`vmw-player`"
#~ msgstr ""
#~ msgid "Install steps:"
#~ msgstr ""
#~ msgid "Decompress the |CL| image"
#~ msgstr ""
#~ msgid ""
#~ "Released |CL| images are compressed with"
#~ " either GNU zip (*.gz*) or XZ "
#~ "(*.xz*). The compression type depends on"
#~ " the target platform or environment. "
#~ "To decompress the image, follow these"
#~ " steps:"
#~ msgstr ""
#~ msgid "Start a terminal emulator."
#~ msgstr ""
#~ msgid "Go to the directory with the downloaded image."
#~ msgstr ""
#~ msgid "To decompress an XZ image, enter:"
#~ msgstr ""
#~ msgid "To decompress a GZ image, enter:"
#~ msgstr ""
#~ msgid "For alternative instructions on other operating systems, see:"
#~ msgstr ""
#~ msgid ":ref:`download-verify-decompress-mac`"
#~ msgstr ""
#~ msgid ":ref:`download-verify-decompress-windows`"
#~ msgstr ""
locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.po
-520
View File
@@ -1,520 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:4
msgid "Run preconfigured |CL-ATTR| image as a VMware\\* ESXi guest OS"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:6
msgid ""
"This page explains how to deploy a preconfigured |CL| VMware :abbr:`VM "
"(Virtual Machine)` image on a VMware ESXi 6.5 host."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:14
msgid "Overview"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:16
msgid ""
"`VMware ESXi`_ is a type 1 bare-metal hypervisor which runs directly on "
"top of server hardware. With VMware ESXi, you can create, configure, "
"manage, and run |CL-ATTR| virtual machines at scale."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:20
msgid ""
"We provide a preconfigured |CL| VMware image that can be run on a VMware "
"ESXi 6.5 host."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:23
msgid ""
"If manuall installation is preferred, refer to :ref:`vmware-esxi-install-"
"cl`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:27
msgid ""
"VMware also offers a type 2 hypervisor designed for the desktop "
"environment, called `VMware Workstation Player`_. Refer to :ref:`vmw-"
"player-preconf` or :ref:`vmw-player` for more information."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:32
msgid "Download the latest |CL| VMware image"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:34
msgid ""
"Get the latest |CL| VMware prebuilt image from the `image`_ repository. "
"Look for :file:`clear-[version number]-vmware.vmdk.xz`. You can also use "
"this command:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:42
msgid ""
"Visit :ref:`image-types` for additional information about all available "
"|CL| images."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:44
msgid ""
"We also provide instructions for downloading and verifying a Clear Linux "
"ISO. For more information, refer to :ref:`download-verify-decompress`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:48
msgid "Upload the |CL| image to the VMware server"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:50
msgid ""
"Once the |CL| VMware prebuilt image has been downloaded and decompressed "
"on your local system, it must be uploaded to a datastore on the VMware "
"ESXi server."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:54
msgid ""
"The steps in this section can also be referenced from the VMware "
"documentation `Using Datastore File Browser in the VMware Host Client`_."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:57
msgid ""
"Connect to the VMware ESXi server and login to an account with sufficient"
" permission to create and manage VMs."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:60
msgid ""
"Under the :guilabel:`Navigator` window on the left side, select "
":guilabel:`Storage`. See Figure 1"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:64
msgid ""
"Under the :guilabel:`Datastores` tab, click the :guilabel:`Datastore "
"browser` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:71
msgid "Figure 1: VMware ESXi - Navigator > Storage"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:73
msgid ""
"Click the :guilabel:`Create directory` button and name the directory "
"`Clear Linux VM`. See Figure 2."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:80
msgid "Figure 2: VMware ESXi - Datastore > Create directory"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:82
msgid ""
"Select the newly-created directory and click the :guilabel:`Upload` "
"button. See Figure 3."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:89
msgid "Figure 3: VMware ESXi - Datastore > Upload VMware image"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:91
msgid ""
"Select the decompressed |CL| VMware image file :file:`clear-[version "
"number]-vmware.vmdk` and upload it."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:95
msgid "Convert the |CL| image to an ESXi-supported format"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:97
msgid ""
"Once the |CL| VMware prebuilt image has been uploaded to the VMware ESXi "
"datastore, it must be converted to a format for usable with VMware's ESXi"
" hypervisor."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:101
msgid ""
"The steps in this section can also be referenced from the VMware "
"documentation on `Cloning and converting virtual machine disks with "
"vmkfstools`_"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:103
msgid ""
"SSH into the `vSphere Management Assistant`_ appliance that is managing "
"the ESXi host or connect to the vSphere hosting using the `vSphere CLI`_."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:108
msgid ""
"If there is no :abbr:`vMA (vSphere Management Assistant)` appliance or "
":abbr:`vCLI (vSphere CLI)` configured and available, you can temporarily "
"enable SSH directly on the ESXi host by following the steps described in "
"`Enable the Secure Shell (SSH) in the VMware Host Client`_ ."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:112
msgid ""
"As a security best practice, remember to disable SSH access after "
"following the steps in this section."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:115
msgid ""
"Locate the uploaded image, which is typically found in "
":file:`/vmfs/volumes/datastore1`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:118
msgid ""
"Use the :command:`vmkfstools` command to perform the conversion, as shown"
" below:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:125
msgid "Two files should result from this:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:127
msgid ":file:`clear-[version number]-esxi-flat.vmdk`"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:128
msgid ":file:`clear-[version number]-esxi.vmdk`"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:130
msgid ""
"The :file:`clear-[version number]-esxi.vmdk` file will be used in the "
"next section when you create a new VM."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:134
msgid "Create and configure a new VM"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:136
msgid ""
"In this section, you will create a new VM, configure its basic parameters"
" such as number of CPUs, memory size, and then attach the converted |CL| "
"VMware image. Also, in order to boot |CL|, you must enable UEFI support."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:140
msgid ""
"Under the :guilabel:`Navigator` window, select :guilabel:`Virtual "
"Machines`. See Figure 4."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:143
msgid "In the right window, click the :guilabel:`Create / Register VM` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:149
msgid "Figure 4: VMware ESXi - Navigator > Virtual Machines"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:151
msgid "On the :guilabel:`Select creation type` step:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:153
msgid "Select the :guilabel:`Create a new virtual machine` option. See Figure 5."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:156
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:173
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:184
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:255
msgid "Click the :guilabel:`Next` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:162
msgid "Figure 5: VMware ESXi - Create a new virtual machine"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:164
msgid "On the :guilabel:`Select a name and guest OS` step:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:166
msgid "Give the new VM a name in the :guilabel:`Name` field. See Figure 6."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:168
msgid ""
"Set the :guilabel:`Compatability` option to :guilabel:`ESXi 6.5 virtual "
"machine`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:170
msgid "Set the :guilabel:`Guest OS family` option to :guilabel:`Linux`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:171
msgid ""
"Set the :guilabel:`Guest OS version` option to :guilabel:`Other 3.x or "
"later Linux (64-bit)`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:179
msgid "Figure 6: VMware ESXi - Give a name and select guest OS type"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:181
msgid "On the :guilabel:`Select storage` step:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:183
msgid "Accept the default option."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:186
msgid "On the :guilabel:`Customize settings` step:"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:188
msgid "Click the :guilabel:`Virtual Hardware` button. See Figure 7."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:189
msgid ""
"Expand the :guilabel:`CPU` setting and enable :guilabel:`Hardware "
"virtualization` by checking :guilabel:`Expose hardware assisted "
"virtualization to the guest OS`."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:197
msgid "Figure 7: VMware ESXi - Enable hardware virtualization"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:199
msgid ""
"Remove the default :guilabel:`Hard drive 1` setting by clicking the `X` "
"icon on the right side. See Figure 8."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:206
msgid "Figure 8: VMware ESXi - Remove hard drive"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:208
msgid ""
"Since a preconfigured image will be used, the :guilabel:`CD/DVD Drive 1` "
"setting will not be needed. Disable it by unchecking the "
":guilabel:`Connect` checkbox. See Figure 9."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:216
msgid "Figure 9: VMware ESXi - Disconnect the CD/DVD drive"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:218
msgid ""
"Attach the :file:`clear-[version number]-esxi.vmdk` file that was "
"converted from the preconfigured |CL| VMware image."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:221
msgid ""
"Click the :guilabel:`Add hard disk` button and select the "
":guilabel:`Existing hard drive` option. See Figure 10."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:228
msgid "Figure 10: VMware ESXi - Add an existing hard drive"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:230
msgid ""
"Select the converted :file:`clear-[version number]-esxi.vmdk` file. Do "
"not use the original unconverted :file:`clear-[version "
"number]-vmware.vmdk` file. See Figure 11."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:238
msgid ""
"Figure 11: VMware ESXi - Select the converted :file:`clear-[version "
"number]-esxi.vmdk` file"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:241
msgid "|CL| needs UEFI support in order to boot. Enable UEFI boot support."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:243
msgid "Click the :guilabel:`VM Options` button. See Figure 12."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:244
msgid "Expand the :guilabel:`Boot Options` setting."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:245
msgid ""
"For the :guilabel:`Firmware` setting, click the drop-down list to the "
"right of it and select the :guilabel:`EFI` option."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:252
msgid "Figure 12: VMware ESXi - Set boot firmware to EFI"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:254
msgid "Click the :guilabel:`Save` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:256
msgid "Click the :guilabel:`Finish` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:259
msgid "Power on the VM and boot |CL|"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:261
msgid "After configuring the settings above, power on the VM."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:263
msgid ""
"Under the :guilabel:`Navigator` window, select :guilabel:`Virtual "
"Machines`. See Figure 13."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:265
msgid "In the right window, select the newly-created VM."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:266
msgid "Click the :guilabel:`Power on` button."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:267
msgid ""
"Click on the icon representing the VM to bring it into view and maximize "
"its window."
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:274
msgid "Figure 13: VMware ESXi - Navigator > Virtual Machines > Power on VM"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:277
msgid "Related topics"
msgstr ""
#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:279
msgid ":ref:`vmware-esxi-install-cl`"
msgstr ""
#~ msgid ""
#~ "This section shows you how to "
#~ "deploy a preconfigured |CL| VMware "
#~ ":abbr:`VM (Virtual Machine)` image on a"
#~ " VMware ESXi 6.5 host."
#~ msgstr ""
#~ msgid ""
#~ "If you would prefer to perform a"
#~ " manual installation of |CL| into a"
#~ " new VMware ESXi :abbr:`VM (Virtual "
#~ "Machine)` instead, see :ref:`vmware-esxi-"
#~ "install-cl`."
#~ msgstr ""
#~ msgid ""
#~ "VMware also offers a type 2 "
#~ "hypervisor called `VMware Workstation Player`"
#~ " which is designed for the desktop"
#~ " environment."
#~ msgstr ""
#~ msgid "See :ref:`vmw-player-preconf` or see :ref:`vmw-player`."
#~ msgstr ""
#~ msgid "Install steps:"
#~ msgstr ""
#~ msgid ""
#~ "The steps in this section can also"
#~ " be referenced from the `VMware "
#~ "documentation on Using the Datastore "
#~ "File Browser`_"
#~ msgstr ""
#~ msgid ""
#~ "The steps in this section can also"
#~ " be referenced from the `VMware "
#~ "documentation on Cloning and converting "
#~ "virtual machine disks with vmkfstools`_"
#~ msgstr ""
#~ msgid ""
#~ "If there is no :abbr:`vMA (vSphere "
#~ "Management Assistant)` appliance or "
#~ ":abbr:`vCLI (vSphere CLI)` configured and "
#~ "available, you can temporarily enable "
#~ "SSH directly on the ESXi host by"
#~ " referencing the `VMware documentation on"
#~ " Enable the Secure Shell (SSH)`_ ."
#~ msgstr ""
#~ msgid "Decompress the |CL| image"
#~ msgstr ""
#~ msgid ""
#~ "Released |CL| images are compressed with"
#~ " either GNU zip (*.gz*) or XZ "
#~ "(*.xz*). The compression type depends on"
#~ " the target platform or environment. "
#~ "To decompress the image, follow these"
#~ " steps:"
#~ msgstr ""
#~ msgid "Start a terminal emulator."
#~ msgstr ""
#~ msgid "Go to the directory with the downloaded image."
#~ msgstr ""
#~ msgid "To decompress an XZ image, enter:"
#~ msgstr ""
#~ msgid "To decompress a GZ image, enter:"
#~ msgstr ""
#~ msgid "For alternative instructions on other operating systems, see:"
#~ msgstr ""
#~ msgid ":ref:`download-verify-decompress-mac`"
#~ msgstr ""
#~ msgid ":ref:`download-verify-decompress-windows`"
#~ msgstr ""
locale/de/LC_MESSAGES/guides/deploy-at-scale.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/deploy-at-scale.po
-602
View File
@@ -1,602 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/deploy-at-scale.rst:4
msgid "Deploy at Scale"
msgstr ""
#: ../../guides/deploy-at-scale.rst:6
msgid ""
"This guide describes deployment considerations and strategies when "
"deploying |CL-ATTR| at scale in your environment."
msgstr ""
#: ../../guides/deploy-at-scale.rst:14
msgid "Overview"
msgstr ""
#: ../../guides/deploy-at-scale.rst:16
msgid ""
"In this guide the term *endpoint* refers to a system targeted for |CL| "
"installation, whether that is a datacenter system or unit deployed in "
"field."
msgstr ""
#: ../../guides/deploy-at-scale.rst:21
msgid ""
"This guide is not a replacement or blueprint for designing your own IT "
"operating environment."
msgstr ""
#: ../../guides/deploy-at-scale.rst:24
msgid ""
"Implementation details for a scale deployment are beyond the scope of "
"this guide."
msgstr ""
#: ../../guides/deploy-at-scale.rst:27
msgid ""
"Your |CL| deployment should complement your existing environment and "
"available tools. It is assumed core IT dependencies of your environment, "
"such as your network, are healthy and scaled to suit the deployment."
msgstr ""
#: ../../guides/deploy-at-scale.rst:32
msgid "Pick a usage and update strategy"
msgstr ""
#: ../../guides/deploy-at-scale.rst:34
msgid ""
"Different business scenarios call for different deployment methodologies."
" |CL| offers the flexibility to continue consuming the upstream |CL| "
"distribution or the option to fork away from the |CL| distribution and "
"act as your own :abbr:`OSV (Operating System Vendor)`."
msgstr ""
#: ../../guides/deploy-at-scale.rst:39
msgid "Below is an overview of some considerations."
msgstr ""
#: ../../guides/deploy-at-scale.rst:42
msgid "Create your own Linux distribution (mix)"
msgstr ""
#: ../../guides/deploy-at-scale.rst:44
msgid ""
"This approach forks away from the |CL| upstream and has you act as your "
"own :abbr:`OSV (Operating System Vendor)` by leveraging the :ref:`mixer` "
"process to create customized images based on |CL|. This is a level of "
"responsibility that requires having more infrastructure and processes to "
"adopt. In return, this approach *offers you a high degree of control and "
"customization*. Consider:"
msgstr ""
#: ../../guides/deploy-at-scale.rst:50
msgid ""
"Development systems that generate bundles and updates should have "
"sufficient performance for the task and be separate from the swupd update"
" webservers that serve update content to production machines."
msgstr ""
#: ../../guides/deploy-at-scale.rst:54
msgid ""
"swupd update webservers that serve update content to production machines "
"should be appropriately scaled. Specific implementation details for a "
"scalable, resilient web server are beyond the scope of this document."
msgstr ""
#: ../../guides/deploy-at-scale.rst:58
msgid "(See :ref:`mixer` for more information about update servers.)"
msgstr ""
#: ../../guides/deploy-at-scale.rst:61
msgid "Adopt an agile methodology"
msgstr ""
#: ../../guides/deploy-at-scale.rst:63
msgid ""
"The cloud, and other scaled deployments, are all about flexibility and "
"speed. It only makes sense that any |CL| deployment strategy should "
"follow suit."
msgstr ""
#: ../../guides/deploy-at-scale.rst:66
msgid ""
"Manually rebuilding your own bundles or mix for every release is not "
"sustainable at a large scale. A |CL| deployment pipeline should be agile "
"enough to validate and produce new versions with speed. Whether or not "
"those updates actually make their way to your production can be separate "
"business decision. However this *ability to frequently roll new versions*"
" of software to your endpoints is an important prerequisite."
msgstr ""
#: ../../guides/deploy-at-scale.rst:73
msgid ""
"You own the validation and lifecycle of the OS and should treat it like "
"any other software development lifecycle. Below are some pointers:"
msgstr ""
#: ../../guides/deploy-at-scale.rst:76
msgid ""
"Thoroughly understand the custom software packages that you will need to "
"integrate with |CL| and maintain along with their dependencies."
msgstr ""
#: ../../guides/deploy-at-scale.rst:79
msgid ""
"Setup a path to production for building |CL| based images. At minimum "
"this should include:"
msgstr ""
#: ../../guides/deploy-at-scale.rst:82
msgid ""
"A development clr-on-clr environment to test building packages and "
"bundles for |CL| systems."
msgstr ""
#: ../../guides/deploy-at-scale.rst:85
msgid "A pre-production environment to deploy |CL| versions to before production"
msgstr ""
#: ../../guides/deploy-at-scale.rst:88
msgid ""
"Employ a continuous integration and continuous deployment (CI/CD) "
"philosophy in order to:"
msgstr ""
#: ../../guides/deploy-at-scale.rst:91
msgid ""
"Automatically pull custom packages as they are updated from their "
"upstream projects or vendors."
msgstr ""
#: ../../guides/deploy-at-scale.rst:94
msgid ""
"Generate |CL| bundles and potentially bootable images with your "
"customizations, if any."
msgstr ""
#: ../../guides/deploy-at-scale.rst:97
msgid ""
"Measure against metrics and indicators which are relevant to your "
"business (e.g. performance, power, etc) from release to release."
msgstr ""
#: ../../guides/deploy-at-scale.rst:100
msgid ""
"Integrate with your organization's governance processes, such as change "
"control."
msgstr ""
#: ../../guides/deploy-at-scale.rst:104
msgid "Versioning infrastructure"
msgstr ""
#: ../../guides/deploy-at-scale.rst:106
msgid ""
"|CL| version numbers are very important as they apply to the whole "
"infrastructure stack from OS components to libraries and applications."
msgstr ""
#: ../../guides/deploy-at-scale.rst:109
msgid ""
"Good record keeping is important, so you should keep a detailed registry "
"and history of previously deployed versions and their contents."
msgstr ""
#: ../../guides/deploy-at-scale.rst:112
msgid ""
"With a glance at the |CL| version numbers deployed, you should be able to"
" tell if your Clear systems are patched against a particular security "
"vulnerability or incorporate a critical new feature."
msgstr ""
#: ../../guides/deploy-at-scale.rst:117
msgid "Pick an image distribution strategy"
msgstr ""
#: ../../guides/deploy-at-scale.rst:119
msgid ""
"Once you have decided on a usage and update strategy, you should "
"understand *how* |CL| will be deployed to your endpoints. In a large "
"scale deployment, interactive installers should be avoided in favor of "
"automated installations or prebuilt images."
msgstr ""
#: ../../guides/deploy-at-scale.rst:124
msgid ""
"There are many well-known ways to install an operating system at scale. "
"Each have their own benefits, and one may lend itself easier in your "
"environment depending on the resources available to you."
msgstr ""
#: ../../guides/deploy-at-scale.rst:128
msgid "See the available :ref:`image-types`."
msgstr ""
#: ../../guides/deploy-at-scale.rst:130
msgid "Below are some common ways to install |CL| to systems at scale:"
msgstr ""
#: ../../guides/deploy-at-scale.rst:133
msgid "Bare metal"
msgstr ""
#: ../../guides/deploy-at-scale.rst:135
msgid ""
"Preboot Execution Environments (PXE) or other out-of-band booting options"
" are one way to distribute |CL| to physical bare metal systems on a LAN."
msgstr ""
#: ../../guides/deploy-at-scale.rst:138
msgid ""
"This option works well if your customizations are fairly small in size "
"and infrastructure can be stateless."
msgstr ""
#: ../../guides/deploy-at-scale.rst:141
msgid ""
"The |CL| `Downloads`_ page offers a live image that can be deployed as a "
"PXE boot server if one doesn't already exist in your environment. Also "
"see documentation on how to :ref:`bare-metal-install-server`."
msgstr ""
#: ../../guides/deploy-at-scale.rst:146
msgid "Cloud instances or virtual machines"
msgstr ""
#: ../../guides/deploy-at-scale.rst:148
msgid ""
"Image templates in the form of cloneable disks are an effective way to "
"distribute |CL| for virtual machine environments, whether on-premises or "
"hosted by a Cloud Solution Provider (CSP)."
msgstr ""
#: ../../guides/deploy-at-scale.rst:152
msgid ""
"When used in concert with cloud VM migration features, this can be a good"
" option for allowing your applications a degree of high availability and "
"workload mobility; VMs can be restarted on a cluster of hypervisor host "
"or moved between datacenters transparently."
msgstr ""
#: ../../guides/deploy-at-scale.rst:157
msgid ""
"The |CL| `Downloads`_ page offers example prebuilt VM images and is "
"readily available on popular CSPs. Also see documentation on how to :ref"
":`virtual-machine-install`."
msgstr ""
#: ../../guides/deploy-at-scale.rst:162
msgid "Containers"
msgstr ""
#: ../../guides/deploy-at-scale.rst:164
msgid ""
"Containerization platforms allow images to be pulled from a repository "
"and deployed repeatedly as isolated containers."
msgstr ""
#: ../../guides/deploy-at-scale.rst:167
msgid ""
"Containers with a |CL| image can be a good option to blueprint and ship "
"your application, including all its dependencies, as an artifact while "
"allowing you or your customers to dynamically orchestrate and scale "
"applications."
msgstr ""
#: ../../guides/deploy-at-scale.rst:172
msgid ""
"|CL| is capable of running a Docker host, has a container image which can"
" be pulled from DockerHub, or can be built as a customized container. For"
" more information visit the `Containers`_ page."
msgstr ""
#: ../../guides/deploy-at-scale.rst:177
msgid "Considerations with stateless systems"
msgstr ""
#: ../../guides/deploy-at-scale.rst:179
msgid ""
"An important |CL| concept is statelessness and partitioning of system "
"data from user data. This concept can change the way you think about an "
"at scale deployment."
msgstr ""
#: ../../guides/deploy-at-scale.rst:184
msgid "Backup strategy"
msgstr ""
#: ../../guides/deploy-at-scale.rst:186
msgid ""
"A |CL| system and its infrastructure should be considered a commodity and"
" be easily reproducible. Avoid focusing on backing up the operating "
"system itself or default values."
msgstr ""
#: ../../guides/deploy-at-scale.rst:190
msgid ""
"Instead, focus on backing up what's important and unique - the "
"application and data. In other words, only focus on backing up critical "
"areas like :file:`/home`, :file:`/etc`, and :file:`/var`."
msgstr ""
#: ../../guides/deploy-at-scale.rst:195
msgid "Meaningful logging & telemetry"
msgstr ""
#: ../../guides/deploy-at-scale.rst:197
msgid ""
"Offload logging and telemetry from endpoints to external servers, so it "
"is persistent and can be accessed on another server when an issue occurs."
msgstr ""
#: ../../guides/deploy-at-scale.rst:200
msgid ""
"Remote syslogging in |CL| is available through the `systemd-journal-"
"remote.service`_"
msgstr ""
#: ../../guides/deploy-at-scale.rst:203
msgid ""
"|CL| offers a :ref:`telem-guide`, which can be a powerful tool for a "
"large deployment to quickly crowdsource issues of interest. Take "
"advantage of this feature with careful consideration of the target "
"audience and the kind of data that would be valuable, and expose events "
"appropriately."
msgstr ""
#: ../../guides/deploy-at-scale.rst:209
msgid ""
"Like any web server, the telemetry server should be appropriately scaled "
"and resilient. Specific implementation details for a scalable, resilient "
"web server are beyond the scope of this document."
msgstr ""
#: ../../guides/deploy-at-scale.rst:214
msgid "Orchestration and configuration management"
msgstr ""
#: ../../guides/deploy-at-scale.rst:216
msgid ""
"In cloud environments, where systems can be ephemeral, being able to "
"configure and maintain generic instances is valuable."
msgstr ""
#: ../../guides/deploy-at-scale.rst:219
msgid ""
"|CL| offers an efficient cloud-init style solution, `micro-config-"
"drive`_, through the *os-cloudguest* bundles which allow you to configure"
" many Day 1 tasks such as setting hostname, creating users, or placing "
"SSH keys in an automated way at boot. For more information on automating "
"configuration during deployment of |CL| endpoints see the :ref:`bulk-"
"provision` guide."
msgstr ""
#: ../../guides/deploy-at-scale.rst:226
msgid ""
"A configuration management tool is useful for maintaining consistent "
"system and application-level configuration. Ansible\\* is offered through"
" the *sysadmin-hostmgmt* bundle as a configuration management and "
"automation tool."
msgstr ""
#: ../../guides/deploy-at-scale.rst:232
msgid "Cloud-native applications"
msgstr ""
#: ../../guides/deploy-at-scale.rst:234
msgid ""
"An Infrastructure OS can design for good behavior, but it is ultimately "
"up to applications to make agile design choices. Applications deployed on"
" |CL| should aim to be host-aware but not depend on any specific host to "
"run. References should be relative and dynamic when possible."
msgstr ""
#: ../../guides/deploy-at-scale.rst:239
msgid ""
"The application architecture should incorporate an appropriate tolerance "
"for infrastructure outages. Don't just keep stateless design as a noted "
"feature. Continuously test its use; Automate its use by redeploying |CL| "
"and application on new hosts. This naturally minimizes configuration "
"drift, challenges your monitoring systems, and business continuity plans."
msgstr ""
#~ msgid ""
#~ "Development systems which are generating "
#~ "bundles and updates should be "
#~ "sufficiently performant for the task and"
#~ " separate from the swupd update "
#~ "webservers which are serving update "
#~ "content to production machines."
#~ msgstr ""
#~ msgid ""
#~ "swupd update webservers which are "
#~ "serving update content to production "
#~ "machines (see `mixer process`_ for more"
#~ " information) should be appropriately "
#~ "scaled."
#~ msgstr ""
#~ msgid ""
#~ "|CL| offers a `native telemetry "
#~ "solution`_ which can be a powerful "
#~ "tool for a large deployment to "
#~ "quickly crowdsource issues of interest. "
#~ "Take advantage of this feature with "
#~ "careful consideration of the target "
#~ "audience and the kind of data that"
#~ " would be valuable, and expose events"
#~ " appropriately."
#~ msgstr ""
#~ msgid ""
#~ "Once you are comfortable with |CL-"
#~ "ATTR| :ref:`concepts <concepts>`, your next"
#~ " step as a system administrator is"
#~ " to understand how to deploy |CL| "
#~ "at scale in your environment."
#~ msgstr ""
#~ msgid ""
#~ "In this document the term *endpoint* "
#~ "refers to a system targeted for "
#~ "|CL| installation, whether that is a "
#~ "datacenter system or unit deployed in"
#~ " field."
#~ msgstr ""
#~ msgid ""
#~ "This is not a replacement or "
#~ "blueprint for designing your own IT "
#~ "operating environment."
#~ msgstr ""
#~ msgid ""
#~ "Your |CL| deployment should complement "
#~ "the existing environment and available "
#~ "tools. It is assumed foundational core"
#~ " IT dependencies of your environment, "
#~ "such as your network, are healthy "
#~ "and scaled to suit the deployment."
#~ msgstr ""
#~ msgid "Pick a |CL| usage and update strategy"
#~ msgstr ""
#~ msgid ""
#~ "This approach forks away from the "
#~ "|CL| upstream and has you act as"
#~ " your own :abbr:`OSV (Operating System "
#~ "Vendor)` by leveraging the `mixer "
#~ "process`_ to create customized images "
#~ "based on |CL|. This is a level "
#~ "of responsibility that requires having "
#~ "more infrastructure and processes to "
#~ "adopt. In return, this approach *offers"
#~ " you a high degree of control "
#~ "and customization*."
#~ msgstr ""
#~ msgid ""
#~ "Development systems that generate bundles "
#~ "and updates should have sufficient "
#~ "performance for the task and separate"
#~ " from the swupd update webservers "
#~ "that serve update content to production"
#~ " machines."
#~ msgstr ""
#~ msgid ""
#~ "swupd update webservers that serve "
#~ "update content to production machines "
#~ "(see `mixer process`_ for more "
#~ "information) should be appropriately scaled."
#~ msgstr ""
#~ msgid ""
#~ "Your swupd update server is just "
#~ "like any other web application. |WEB-"
#~ "SERVER-SCALE|"
#~ msgstr ""
#~ msgid "Versioning Infrastructure"
#~ msgstr ""
#~ msgid "Baremetal"
#~ msgstr ""
#~ msgid ""
#~ "Preboot Execution Environments (PXE) or "
#~ "other out-of-band booting options "
#~ "are one way to distribute |CL| to"
#~ " physical baremetal systems on a LAN."
#~ msgstr ""
#~ msgid ""
#~ "The |CL| `downloads page`_ offers a "
#~ "live image that can be deployed as"
#~ " a PXE boot server if one "
#~ "doesn't already exist in your "
#~ "environment. Also see documentation on "
#~ "how to :ref:`bare-metal-install-server`."
#~ msgstr ""
#~ msgid "Cloud Instances or Virtual Machines"
#~ msgstr ""
#~ msgid ""
#~ "The |CL| `downloads page`_ offers "
#~ "example prebuilt VM images and is "
#~ "readily available on popular CSPs. Also"
#~ " see documentation on how to :ref"
#~ ":`virtual-machine-install`."
#~ msgstr ""
#~ msgid ""
#~ "|CL| is capable of running a "
#~ "Docker host, has a container image "
#~ "which can be pulled from DockerHub, "
#~ "or can be built as a customized"
#~ " container. For more information visit "
#~ "the `containers page`_."
#~ msgstr ""
#~ msgid ""
#~ "Instead, focus on backing up what's "
#~ "important and unique - the application"
#~ " and data. In other words, only "
#~ "focus on backing up critical areas "
#~ "like `/home`, `/etc`, and `/var`."
#~ msgstr ""
#~ msgid "Meaningful Logging & Telemetry"
#~ msgstr ""
#~ msgid ""
#~ "Remote syslogging in |CL| is available"
#~ " through the `systemd journal-remote "
#~ "service`_"
#~ msgstr ""
#~ msgid ""
#~ "Your telemetry server is just like "
#~ "any other web application. |WEB-"
#~ "SERVER-SCALE|"
#~ msgstr ""
#~ msgid "Orchestration and Configuration Management"
#~ msgstr ""
#~ msgid ""
#~ "|CL| offers an efficient cloud-init "
#~ "style solution, `micro-config-drive`_, "
#~ "through the *os-cloudguest* bundles "
#~ "which allow you to configure many "
#~ "Day 1 tasks such as setting "
#~ "hostname, creating users, or placing SSH"
#~ " keys in an automated way at "
#~ "boot. For more information on automating"
#~ " configuration during deployment of |CL|"
#~ " endpoints see the `documentation on "
#~ "bulk provisioning`_ ."
#~ msgstr ""
locale/de/LC_MESSAGES/guides/guides.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/guides.po
-48
View File
@@ -1,48 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/guides.rst:4
msgid "Guides"
msgstr ""
#: ../../guides/guides.rst:6
msgid "The following guides provide step-by-step instructions on using |CL|."
msgstr ""
#: ../../guides/guides.rst:10
msgid "As of 22 May 2019 :file:`mixin` is no longer supported."
msgstr ""
#: ../../guides/guides.rst:13
msgid "Maintenance"
msgstr ""
#: ../../guides/guides.rst:23
msgid "Network"
msgstr ""
#: ../../guides/guides.rst:32
msgid "Kernel"
msgstr ""
#: ../../guides/guides.rst:41
msgid "Stacks"
msgstr ""
locale/de/LC_MESSAGES/guides/kernel/kernel-development.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/kernel/kernel-development.po
-641
View File
@@ -1,641 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/kernel/kernel-development.rst:4
msgid "Kernel development"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:6
msgid ""
"This guide shows how to obtain and compile a Linux\\* kernel source using"
" |CL-ATTR| development tooling."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:15
msgid "Overview"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:17
msgid ""
"The :ref:`compatible-kernels` available in |CL| aim to be performant and "
"practical. In some cases, it may be necessary to modify the kernel to "
"suit your specific needs or test new kernel code as a developer."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:21
msgid ""
"`Source RPMs (SRPMS)`_ are also available for all |CL| kernels, and can "
"be used for development instead."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:25
msgid "Request changes be included with the |CL| kernel"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:27
msgid ""
"If the kernel modification you need is already open source and likely to "
"be useful to others, consider submitting a request to include it in the "
"|CL| kernels.If your change request is accepted, you do not need to "
"maintain your own modified kernel."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:32
msgid ""
"Make enhancement requests to the |CL| `Distribution Project`_ on "
"GitHub\\*."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:35
msgid "Set up kernel development environment"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:37
msgid ""
"In some cases, it may be necessary to modify the kernel to suit your "
"specific needs or to test new kernel code."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:40
msgid "You can build and install a custom kernel; however you must:"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:42
msgid "Disable Secure Boot"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:43
msgid "Maintain any updates to the kernel going forward"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:45
msgid ""
"To create a custom kernel, start with the |CL| development environment. "
"Then make changes to the kernel, build it, and install it."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:50
msgid "Install the |CL| development tooling framework"
msgstr ""
#: ../../tooling/autospec.rst:3
msgid ""
"Setup of the workspace and tooling used for building source in |CL| is "
"mostly automated for you with a setup script. It uses tools from the "
":command:`os-clr-on-clr` bundle."
msgstr ""
#: ../../tooling/autospec.rst:7
msgid ""
"The setup script creates a workspace in the :file:`clearlinux` folder, "
"with the subfolders :file:`Makefile`, :file:`packages`, and "
":file:`projects`. The :file:`projects` folder contains the main tools "
"used for making packages in |CL| :file:`autospec` and :file:`common`."
msgstr ""
#: ../../tooling/autospec.rst:12
msgid "Follow these steps to setup the workspace and tooling for building source:"
msgstr ""
#: ../../tooling/autospec.rst:14
msgid "Install the :command:`os-clr-on-clr` bundle:"
msgstr ""
#: ../../tooling/autospec.rst:20
msgid "Download the :file:`user-setup.sh` script:"
msgstr ""
#: ../../tooling/autospec.rst:26
msgid "Make :file:`user-setup.sh` executable:"
msgstr ""
#: ../../tooling/autospec.rst:32
msgid "Run the script as an unprivileged user:"
msgstr ""
#: ../../tooling/autospec.rst:38
msgid ""
"After the script completes, log out and log in again to complete the "
"setup process."
msgstr ""
#: ../../tooling/autospec.rst:41
msgid "Set your Git user email and username for the repos on your system:"
msgstr ""
#: ../../tooling/autospec.rst:48
msgid "This global setting is used by |CL| tools that make use of Git."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:57
msgid "Clone the kernel package"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:59
msgid ""
"Clone the existing kernel package repository from |CL| as a starting "
"point."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:61
msgid ""
"Clone the Linux kernel package from |CL|. Using the :command:`make "
"clone_<PACKAGENAME>` command in the :file:`clearlinux/` directory clones "
"the package from the `clearlinux-pkgs`_ repo on GitHub."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:71
msgid "Navigate into the cloned package directory."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:78
msgid ""
"The \"linux\" package is the kernel that comes with |CL| in the :command"
":`kernel-native` bundle. Alternatively, you can use a different kernel "
"variant as the base for modification. For a list of kernel package names "
"which you can clone instead, see the `clearlinux-pkgs`_ repo on GitHub."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:85
msgid ""
"The latest version of the |CL| kernel package is pulled as a starting "
"point. An older version can pulled by switching to different git tag by "
"using :command:`git checkout tag/<TAG_NAME>`."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:90
msgid "Change the kernel version"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:92
msgid ""
"|CL| tends to use the latest kernel available from `kernel.org`_, the "
"Linux upstream. The kernel version that will be built can be changed in "
"the RPM SPEC file. While most packages in Clear Linux are typically "
"packaged using :ref:`autospec-about`, the kernel is not. This means "
"control files provided by autospec are not available and changes must be "
"made manually."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:98
#: ../../guides/kernel/kernel-development.rst:294
msgid "Open the Linux kernel package RPM SPEC file in an editor."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:104
msgid ""
"Modify the Version, Release, and Source0 URL entries at the top of the "
"file to change the version of Linux kernel that will be compiled."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:107
msgid ""
"A list of current and available kernel release can be found on "
"`kernel.org`_."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:126
msgid ""
"Consider changing the Name from *linux* in the RPM spec file to easily "
"identify a modified kernel."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:129
msgid ""
"Consider changing the ktarget from *native* in the RPM spec file to "
"easily identify a modified kernel."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:132
msgid "Commit and save the changes to the file."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:137
msgid "Pull a copy of the Linux kernel source code"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:139
msgid "Obtain a local copy of the source code to make modifications against."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:141
msgid ""
"Run make sources to pull the kernel source code specified in the RPM SPEC"
" file. In the example, it downloads the :file:`linux-4.20.8.tar.xz` file."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:149
msgid ""
"Extract the kernel source code archive. This will create a working copy "
"of the Linux source that you can modify."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:156
msgid ""
"Navigate to the extracted directory. In this example, it has been "
"extracted into a :file:`linux-4.20.8` directory."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:165
msgid "Customize the Linux kernel source"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:167
msgid ""
"After the kernel sources have been obtained, customizations to the kernel"
" configuration or source code can be made for inclusion with the kernel "
"build. These customizations are optional."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:172
msgid "Modify kernel configuration"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:174
msgid ""
"The kernel source has many configuration options available to pick "
"support for different hardware and software features."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:177
msgid ""
"These configuration values must be provided in the :file:`.config` file "
"at compile time. You will need to make modifications to the "
":file:`.config` file, and include it in the kernel package."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:182
#: ../../guides/kernel/kernel-development.rst:238
msgid ""
"Make sure you have followed the steps to :ref:`pull-copy-kernel-source` "
"and are in the kernel source working directory."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:186
msgid ""
"If you have an existing :file:`.config` file from an old kernel, copy it "
"into the working directory as :file:`.config` for comparison. Otherwise, "
"use the |CL| kernel configuration file as template"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:195
msgid ""
"Make any desired changes to the :file:`.config` using a kernel "
"configuration tool. Below are some popular options:"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:198
msgid ""
":command:`$EDITOR .config` - the .config file can be directly edited for "
"simple changes with names that are already known."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:201
msgid ""
":command:`make config` - a text-based tool that asks questions one-by-one"
" to decide configuration options."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:204
msgid ""
":command:`make menuconfig` - a terminal user interface that provides "
"menus to decide configuration options."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:207
msgid ""
":command:`make xconfig` - a graphical user interface that provides tree "
"views to decide configuration options."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:211
msgid ""
"More configuration tools can be found by looking at the make help: "
":command:`make help | grep config`"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:214
msgid "Commit and save the changes to the :file:`.config` file."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:216
msgid ""
"Copy the :file:`.config` file from the kernel source directory into the "
"kernel package directory as :file:`config` for inclusion in the build."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:224
msgid "Modify kernel source code"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:226
msgid ""
"Changes to kernel code are applied with patch files. Patch files are "
"formatted git commits that can be applied to the main source code."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:229
msgid ""
"You will need to obtain a copy of the source code, make modifications, "
"generate patch file(s), and add them to the RPM SPEC file for inclusion "
"during the kernel build."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:233
msgid ""
"If you have a large number of patches or a more complex workflow, "
"consider using a patch management tool in addition to Git such as "
"`Quilt`_."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:242
msgid ""
"Initialize the kernel source directory as a new git repo and create a "
"commit with all the existing source files to begin tracking changes."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:252
msgid ""
"Apply patches provided by the |CL| kernel package to the kernel source in"
" the working directory."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:260
msgid "Make any of your desired code changes to the Linux source code files."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:263
msgid "Track and commit your changes to the local git repo."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:271
msgid ""
"Generate a patch file based on your git commits. <n> represents the "
"number of local commits to create patch file. See the `git-format-patch`_"
" documentation for detailed information on using :command:`git format-"
"patch`"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:280
msgid ""
"Copy the patch files from the patches directory in the linux source tree "
"to the RPM build directory."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:288
msgid "Navigate back to the RPM build directory."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:300
msgid ""
"Locate the section of the SPEC file that contains existing patch variable"
" definitions and append your patch file name. Ensure the patch number "
"does not collide with an existing patch. In this example, the patch file "
"is called :file:`2001-my-patch-for-driver-A.patch`"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:323
msgid ""
"Locate the section of the SPEC file further down that contains patch "
"application and append your patch file number used in the step above. In "
"this example, patch2001 is added."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:342
msgid "Commit and save the changes to the RPM SPEC file."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:345
msgid "Modify kernel boot parameters"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:346
msgid ""
"The kernel boot options are passed from the bootloader to the kernel with"
" command-line parameters."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:349
msgid ""
"While temporary changes can be made to kernel parameters on a running "
"system or on a during boot, you can also modify the default parameters "
"that are persistent and distributed with a customized kernel."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:354
msgid "Open the kernel :file:`cmdline` file in an editor."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:361
msgid ""
"Make any desired change to the kernel parameters. For example, you can "
"remove the :command:`quiet` parameter to see more verbose output of "
"kernel log messages during the boot process."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:365
msgid "Commit and save the changes to the :file:`cmdline` file."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:367
msgid ""
"See the `kernel parameters`_ documentation for a list of available "
"parameters."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:371
msgid "Build and install the kernel"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:372
msgid ""
"After changes have been made to the kernel source and RPM SPEC file, the "
"kernel is ready to be compiled and packaged into an RPM."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:375
msgid ""
"The |CL| development tooling makes use of :command:`mock` environments to"
" isolate building of packages in a sanitized workspace."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:378
msgid ""
"Start the compilation process by issuing the :command:`make build` "
"command. This process is typically resource intensive and will take a "
"while."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:386
msgid ""
"The mock plugin `ccache`_ can be enabled to help speed up any future "
"rebuilds of the kernel package by caching compiler outputs and reusing "
"them."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:391
msgid ""
"The result will be multiple :file:`.rpm` files in the :file:`rpms` "
"directory as output."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:398
msgid ""
"The kernel RPM will be named "
":file:`linux<NAME>-<VERSION>-<RELEASE>.x86_64.rpm`"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:402
msgid ""
"The kernel RPM file can be input to the :ref:`mixer` to create a custom "
"bundle and mix of |CL|."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:405
msgid ""
"Alternatively, the kernel RPM bundle can be installed manually on a local"
" machine for testing. This approach works well for individual development"
" or testing. For a more scalable and customizable approach, consider "
"using the :ref:`mixer` to provide a custom kernel with updates."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:410
msgid ""
"Install the kernel onto the local system by extracting the RPM with the "
":command:`rpm2cpio` command."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:418
msgid "Update the |CL| boot manager using :command:`clr-boot-manager` and reboot."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:428
msgid "After a reboot, verify the customized kernel is running."
msgstr ""
#: ../../guides/kernel/kernel-development.rst:435
msgid "Related topics"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:437
msgid ":ref:`kernel-modules`"
msgstr ""
#: ../../guides/kernel/kernel-development.rst:438
msgid ":ref:`mixer`"
msgstr ""
#~ msgid ""
#~ "This document shows how to obtain "
#~ "and compile a Linux* kernel source "
#~ "using |CL-ATTR| development tooling."
#~ msgstr ""
#~ msgid ""
#~ "The `kernels available`_ in |CL| aim"
#~ " to be performant and practical. In"
#~ " some cases, it may be necessary "
#~ "to modify the kernel to suit your"
#~ " specific needs or test new kernel"
#~ " code as a developer."
#~ msgstr ""
#~ msgid ""
#~ "Source RPM files (SRPM) are also "
#~ "available for all |CL| kernels, and "
#~ "can be used for development instead. "
#~ "Select this link to view the "
#~ "latest `source RPM files`_."
#~ msgstr ""
#~ msgid "Make enhancement requests to the |CL| `distribution on GitHub`_ ."
#~ msgstr ""
#~ msgid ""
#~ "Clone the Linux kernel package from "
#~ "|CL|. Using the :command:`make "
#~ "clone_<PACKAGENAME>` command in the "
#~ ":file:`clearlinux/` directory clones the "
#~ "package from the `clearlinux-pkgs "
#~ "GitHub`_."
#~ msgstr ""
#~ msgid ""
#~ "The \"linux\" package is the kernel "
#~ "that comes with |CL| in the "
#~ "`kernel-native` bundle. Alternatively, you "
#~ "can use a different kernel variant "
#~ "as the base for modification. For "
#~ "a list of kernel package names "
#~ "which you can clone instead, see "
#~ "the `clearlinux-pkgs GitHub`_."
#~ msgstr ""
#~ msgid ""
#~ "Generate a patch file based on "
#~ "your git commits. <n> represents the "
#~ "number of local commits to create "
#~ "patch file. See the `git-format-"
#~ "patch Documentation`_ for detailed information"
#~ " on using :command:`git format-patch`"
#~ msgstr ""
#~ msgid ""
#~ "See the `Kernel parameters documentation`_ "
#~ "for a list of available parameters."
#~ msgstr ""
#~ msgid ""
#~ "The `ccache plugin for mock`_ can "
#~ "be enabled to help speed up any"
#~ " future rebuilds of the kernel "
#~ "package by caching compiler outputs and"
#~ " reusing them."
#~ msgstr ""
#~ msgid ""
#~ "This guide shows how to obtain and"
#~ " compile a Linux* kernel source using"
#~ " |CL-ATTR| development tooling."
#~ msgstr ""
#~ msgid ""
#~ "Make enhancement requests to the |CL|"
#~ " `Distribution Project`_ on GitHub."
#~ msgstr ""
#~ msgid ""
#~ "The \"linux\" package is the kernel "
#~ "that comes with |CL| in the "
#~ "`kernel-native` bundle. Alternatively, you "
#~ "can use a different kernel variant "
#~ "as the base for modification. For "
#~ "a list of kernel package names "
#~ "which you can clone instead, see "
#~ "the `clearlinux-pkgs`_ repo on GitHub."
#~ msgstr ""
#~ msgid ""
#~ "Make sure you have followed the "
#~ "steps to `Pull a copy of the "
#~ "Linux kernel source code`_ and are "
#~ "in the kernel source working directory."
#~ msgstr ""
locale/de/LC_MESSAGES/guides/kernel/kernel-modules-dkms.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/kernel/kernel-modules-dkms.po
-565
View File
@@ -1,565 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/kernel/kernel-modules-dkms.rst:4
msgid "Add kernel modules with DKMS"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:6
msgid ""
"This guide describes how to add kernel modules with :abbr:`DKMS (Dynamic "
"Kernel Module System)`."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:14
msgid "Overview"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:16
msgid ""
"Certain kernel modules are enabled by default in |CL-ATTR|. To use "
"additional kernel modules that are not part of the Linux source tree, you"
" may need to build out-of-tree kernel modules. Use this guide to add "
"kernel modules with :abbr:`DKMS (Dynamic Kernel Module System)` or refer "
"to :ref:`kernel-modules`."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:22
msgid "Description"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:24
msgid ""
"Kernel modules are additional pieces of software capable of being "
"inserted into the Linux kernel to add functionality, such as a hardware "
"driver. Kernel modules may already be part of the Linux source tree (in-"
"tree) or may come from an external source, such as directly from a vendor"
" (out-of-tree)."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:29
msgid ""
":abbr:`DKMS (Dynamic Kernel Module System)` is a framework that "
"facilitates the building and installation of kernel modules. DKMS allows "
"|CL| to provide hooks that automatically rebuild modules against new "
"kernel versions."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:4
msgid "Kernel module availability"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:6
msgid ""
"|CL| comes with many upstream kernel modules available for use. Using an "
"existing module is significantly easier to maintain and retains signature"
" verification of the |CL| kernel. For more information on |CL| security "
"practices, see the :ref:`security` page."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:11
msgid ""
"Before continuing, check if the kernel module you're looking for is "
"already available in |CL| or submit a request to add the module."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:16
msgid "Check if the module is already available"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:19
msgid ""
"You can search for kernel module file names, which end with the "
":file:`.ko` file extension, using the :command:`swupd search` command, as"
" shown in the following example. See :ref:`swupd-guide` for more "
"information."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:29
msgid "Submit a request to add the module"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:31
msgid ""
"If the kernel module you need is already open source (for example, in the"
" Linux upstream) and likely to be useful to others, consider submitting a"
" request to add or enable it in the |CL| kernel."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:35
msgid "Make enhancement requests to the |CL| 'Distribution Project'_ on GitHub."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:38
msgid "Install DKMS"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:42
msgid ""
"The :command:`kernel-native-dkms` bundle provides the :command:`dkms` "
"program and Linux kernel headers, which are required for compiling kernel"
" modules."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:45
msgid "The :command:`kernel-native-dkms` bundle also:"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:47
msgid ""
"Adds a `systemd` update trigger (:file:`/usr/lib/systemd/system/dkms-new-"
"kernel.service`) to automatically run DKMS to rebuild modules after a "
"kernel upgrade occurs with :ref:`swupd update <swupd-guide>`."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:52
msgid ""
"Disables kernel module signature verification by appending a kernel "
"command-line parameter (:command:`module.sig_unenforce`) from the "
":file:`/usr/share/kernel/cmdline.d/clr-ignore-mod-sig.conf` file."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:56
msgid ""
"Adds a notification to the Message of the Day (MOTD) indicating kernel "
"module signature verification is disabled."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:61
msgid ""
"We recommend that you always review the :command:`swupd update` output to"
" make sure kernel modules were successfully rebuilt against the new "
"kernel. This is especially important for systems where a successful boot "
"relies on a kernel module."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:66
msgid ""
"Install the :command:`kernel-native-dkms` or :command:`kernel-lts-dkms` "
"bundle:"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:69
msgid ""
"Determine which kernel variant is running on |CL|. Only the *native* and "
"*lts* kernels are enabled to build and load out-of-tree kernel modules "
"with DKMS."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:78
msgid "Ensure *.native* or *.lts* is in the kernel name."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:80
msgid ""
"Install the DKMS bundle corresponding to the installed kernel. Use "
":command:`kernel-native-dkms` for the native kernel or :command:`kernel-"
"lts-dkms` for the lts kernel."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:88
msgid "or"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:95
msgid "Update the |CL| bootloader and reboot."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:105
msgid "Build, install, and load an out-of-tree module"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:107
msgid ""
"Follow the steps in this section if you are an individual user or "
"testing, and you need an out-of-tree kernel module that is not available "
"through |CL|. For a more scalable and customizable approach, we recommend"
" using :ref:`mixer` to provide a custom kernel and updates."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:113
msgid "Prerequisites"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:115
msgid "Before you begin, you must:"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:117
msgid ""
"Disable Secure Boot in UEFI/BIOS. The loading of new out-of-tree modules "
"modifies the signatures that Secure Boot relies on for trust."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:120
msgid ""
"Obtain a kernel module package in the form of source code or pre-compiled"
" binaries."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:124
msgid "Obtain kernel module source"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:126
msgid ""
"A required :file:`dkms.conf` file inside of the kernel module's source "
"code directory informs DKMS how the kernel module should be compiled."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:129
msgid "Kernel modules may come packaged as:"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:131
msgid "Source code without a :file:`dkms.conf` file"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:132
msgid "Source code with a premade :file:`dkms.conf` file"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:133
msgid ""
"Source code with a premade :file:`dkms.conf` file and precompiled module "
"binaries"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:135
msgid "Precompiled module binaries only (without source code)"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:137
msgid ""
"Of the package types listed above, only precompiled kernel module "
"binaries will not work, because |CL| requires kernel modules to be built "
"against the same kernel source tree before they can be loaded. If you are"
" only able to obtain source code without a :file:`dkms.conf` file, you "
"must manually create a :file:`dkms.conf` file, described later in this "
"document."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:143
msgid "Download the kernel module's source code."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:145
msgid ""
"Review the available download options. Some kernel modules provide "
"separate archives that are specifically enabled for DKMS support."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:148
msgid ""
"Review the README documentation, because it often provides required "
"information to build the module with DKMS support."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:159
msgid "Build kernel module with an existing dkms.conf"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:161
msgid ""
"If the kernel module maintainer packaged the source archive with the "
":command:`dkms mktarball` command, the entire archive can be passed to "
"the :command:`dkms ldtarball` which completes many steps for you."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:165
msgid ""
"The archive contains the required :file:`dkms.conf` file, and may contain"
" a :file:`dkms_source_tree` directory and a :file:`dkms_binaries_only` "
"directory."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:169
msgid ""
"Run the :command:`dkms ldtarball` command against the kernel module "
"archive."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:177
msgid ""
":command:`dkms ldtarball` places the kernel module source under "
":file:`/usr/src/<MODULE-NAME>-<MODULE-VERSION>/`, builds it if necessary,"
" and adds the module into the DKMS tree."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:182
msgid ""
"Verify the kernel module is detected by checking the output of the "
":command:`dkms status` command."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:190
msgid "Install the kernel module."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:197
msgid "Build kernel module without an existing dkms.conf"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:199
msgid ""
"If the kernel module source does not contain a :file:`dkms.conf` file or "
"the :command:`dkms ldtarball` command encounters errors, you must "
"manually create the file."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:203
msgid ""
"Review the kernel module README documentation for guidance on what needs "
"to be in the :file:`dkms.conf` file, including special variables that may"
" be required to build successfully."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:207
msgid "Here are some additional resources that can be used for reference:"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:209
msgid ""
"DKMS manual page (:command:`man dkms`) shows detailed syntax in the "
"DKMS.CONF section."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:212
msgid ""
"Ubuntu community wiki entry for the `Kernel DKMS Package`_ shows an "
"example where a single package contains multiple modules."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:215
msgid "Sample `dkms.conf`_ file in the GitHub\\* repository for the DKMS project."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:219
msgid ""
":command:`AUTOINSTALL=yes` must be set in the dkms.conf for the module to"
" be automatically recompiled with |CL| updates."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:222
msgid "The instructions below show a generic example:"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:224
msgid ""
"Create or modify the :file:`dkms.conf` file inside of the extracted "
"source code directory."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:240
msgid ""
"This example identifies a kernel module named *custom_module* with "
"version *1.0*."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:243
msgid "Copy the kernel module source code into the :file:`/usr/src/` directory."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:252
msgid ""
"*<PACKAGE_NAME>* and *<PACKAGE_VERSION>* must match the entries in the "
":file:`dkms.conf` file."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:255
msgid "Add the kernel module to the DKMS tree so that it is tracked by DKMS."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:261
msgid ""
"Build the kernel module using DKMS. If the build encounters errors, you "
"may need to edit the :file:`dkms.conf` file."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:268
msgid "Install the kernel module using DKMS."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:275
msgid "Load kernel module"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:277
msgid ""
"By default, DKMS installs modules \"in-tree\" under :file:`/lib/modules` "
"so the :command:`modprobe` command can be used to load them."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:280
msgid "Load the installed module with the :command:`modprobe` command."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:286
msgid "Validate the kernel module is loaded."
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:293
msgid "Examples"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:4
msgid "Optional: Specify module options and aliases"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:6
msgid "Use the :command:`modprobe` command to load a module and set options."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:8
msgid ""
":command:`modprobe` may add or remove more than one module due to module "
"interdependencies. You can specify which options to use with individual "
"modules, by using configuration files under the :file:`/etc/modprobe.d` "
"directory."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:16
msgid ""
"All files underneath the :file:`/etc/modprobe.d` directory that end with "
"the :file:`.conf` extension specify module options to use when loading. "
"You can use :file:`.conf` files to create convenient aliases for modules "
"or to override the normal loading behavior altogether for those with "
"special requirements."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:21
msgid "Learn more about :command:`modprobe` on the modprobe.d manual page:"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:28
msgid "Optional: Configure kernel modules to load at boot"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:30
msgid ""
"Use the :file:`/etc/modules-load.d` configuration directory to specify "
"kernel modules to load automatically at boot."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:37
msgid ""
"All files underneath the :file:`/etc/modules-load.d` directory that end "
"with the :file:`.conf` extension contain a list of module names of "
"aliases (one per line) to load at boot."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:41
msgid "Learn more about module loading in the modules-load.d manual page:"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:300
msgid "Related topics"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:302
msgid "`Dynamic Kernel Module System (DKMS)`_"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:304
msgid ""
"`Dell Linux Engineering Dynamic Kernel Module Support: From Theory to "
"Practice "
"<https://www.kernel.org/doc/ols/2004/ols2004v1-pages-187-202.pdf>`_"
msgstr ""
#: ../../guides/kernel/kernel-modules-dkms.rst:306
msgid ""
"`Linux Journal: Exploring Dynamic Kernel Module Support "
"<https://www.linuxjournal.com/article/6896>`_"
msgstr ""
#~ msgid "Make enhancement requests to the |CL| distribution `on GitHub`_."
#~ msgstr ""
#~ msgid ""
#~ "Follow the steps in this section "
#~ "if you are an individual user or"
#~ " testing, and you need an out-"
#~ "of-tree kernel module that is not "
#~ "available through |CL|. For a more "
#~ "scalable and customizable approach, we "
#~ "recommend using the `mixer tool`_ to "
#~ "provide a custom kernel and updates."
#~ msgstr ""
#~ msgid ""
#~ "`Ubuntu community wiki`_ shows an "
#~ "example where a single package contains"
#~ " multiple modules."
#~ msgstr ""
#~ msgid ""
#~ "`Sample dkms.conf file`_ in the "
#~ "GitHub\\* repository for the DKMS "
#~ "project."
#~ msgstr ""
#~ msgid ""
#~ "`Dynamic Kernel Module System (DKMS) "
#~ "project on GitHub <https://github.com/dell/dkms>`_"
#~ msgstr ""
#~ msgid ""
#~ "Make enhancement requests to the |CL|"
#~ " `Distribution Project "
#~ "<https://github.com/clearlinux/distribution>`_ on GitHub."
#~ msgstr ""
#~ msgid ""
#~ "The *kernel-native-dkms* bundle provides"
#~ " the :command:`dkms` program and Linux "
#~ "kernel headers, which are required for"
#~ " compiling kernel modules."
#~ msgstr ""
#~ msgid "The *kernel-native-dkms* bundle also:"
#~ msgstr ""
#~ msgid ""
#~ "Adds a systemd update trigger "
#~ "(:file:`/usr/lib/systemd/system/dkms-new-kernel.service`)"
#~ " to automatically run DKMS to rebuild"
#~ " modules after a kernel upgrade "
#~ "occurs with :ref:`swupd update <swupd-"
#~ "guide>`."
#~ msgstr ""
#~ msgid ""
#~ "Follow the steps in this section "
#~ "if you are an individual user or"
#~ " testing, and you need an out-"
#~ "of-tree kernel module that is not "
#~ "available through |CL|. For a more "
#~ "scalable and customizable approach, we "
#~ "recommend using the :ref:`mixer` tool to"
#~ " provide a custom kernel and updates."
#~ msgstr ""
#~ msgid ""
#~ "Obtain a kernel module package in "
#~ "the form of source code and/or "
#~ "precompiled binaries."
#~ msgstr ""
locale/de/LC_MESSAGES/guides/kernel/kernel-modules.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/kernel/kernel-modules.po
-301
View File
@@ -1,301 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/kernel/kernel-modules.rst:4
msgid "Add kernel modules manually"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:6
msgid "This guide describes how to add kernel modules manually."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:13
msgid "Overview"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:15
msgid ""
"Certain kernel modules are enabled by default in |CL-ATTR|. To use "
"additional kernel modules that are not part of the Linux source tree, you"
" may need to build out-of-tree kernel modules. Use this guide to add "
"kernel modules manually, or refer to :ref:`kernel-modules-dkms`."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:21
msgid "Description"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:23
msgid ""
"Kernel modules are additional pieces of software capable of being "
"inserted into the Linux kernel to add functionality, such as a hardware "
"driver. Kernel modules may already be part of the Linux source tree (in-"
"tree) or may come from an external source, such as directly from a vendor"
" (out-of-tree)."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:32
msgid "Kernel module availability"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:34
msgid ""
"|CL| comes with many upstream kernel modules available for use. Using an "
"existing module is significantly easier to maintain and retains signature"
" verification of the |CL| kernel. For more information on |CL| security "
"practices, see the :ref:`security` page."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:39
msgid ""
"Before continuing, check if the kernel module you're looking for is "
"already available in |CL| or submit a request to add the module."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:44
msgid "Check if the module is already available"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:47
msgid ""
"You can search for kernel module file names, which end with the "
":file:`.ko` file extension, using the :command:`swupd search` command, as"
" shown in the following example. See :ref:`swupd-guide` for more "
"information."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:57
msgid "Submit a request to add the module"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:59
msgid ""
"If the kernel module you need is already open source (for example, in the"
" Linux upstream) and likely to be useful to others, consider submitting a"
" request to add or enable it in the |CL| kernel."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:63
msgid "Make enhancement requests to the |CL| 'Distribution Project'_ on GitHub."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:69
msgid "Build, install, and load an out-of-tree module"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:71
msgid ""
"Follow the steps in this section if you are an individual user or "
"testing, and you need an out-of-tree kernel module that is not available "
"through |CL|. For a more scalable and customizable approach, we recommend"
" using the :ref:`mixer` to provide a custom kernel and updates."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:78
msgid "Prerequisites"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:80
msgid "Before you begin, you must:"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:82
msgid "Disable Secure Boot."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:83
msgid "Disable kernel module integrity checking."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:84
msgid "Have a kernel module package in the form of source code."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:85
msgid "Rebuild the module against new versions of the Linux kernel."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:89
msgid ""
"Any time the kernel is upgraded on your Clear Linux system, you must "
"rebuild your out-of-tree modules."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:94
msgid "Build and install kernel module"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:96
msgid ""
"Determine which kernel variant is running on |CL|. In the example below, "
"the *native* kernel is in use."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:104
msgid ""
"Install the kernel dev bundle corresponding to the installed kernel. The "
"kernel dev bundle contains the kernel headers, which are required for "
"compiling kernel modules. For example:"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:108
msgid ":command:`linux-dev` for developing against the native kernel."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:109
msgid ":command:`linux-lts-dev` for developing against the LTS kernel."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:115
msgid ""
"Follow instructions from the kernel module source code to compile the "
"kernel module. For example:"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:128
msgid "Load kernel module"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:130
msgid ""
"Disable Secure Boot in your system's UEFI settings, if you have enabled "
"it. The loading of new out-of-tree modules modifies the signatures that "
"Secure Boot relies on for trust."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:134
msgid ""
"Disable signature checking for the kernel by modifying the kernel boot "
"parameters and reboot the system."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:137
msgid ""
"All kernel modules from |CL| have been signed to enforce kernel security."
" However, out-of-tree modules break this chain of trust so this mechanism"
" needs to be disabled."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:146
msgid ""
"Update the boot manager and reboot the system to implement the changed "
"kernel parameters."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:156
msgid ""
"If successful, the :command:`clr-boot-manager update` command does not "
"return any console output."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:159
msgid ""
"After rebooting, manually load out-of-tree modules using the "
":command:`insmod` command."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:167
msgid "Examples"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:172
msgid "Optional: Specify module options and aliases"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:174
msgid "Use the :command:`modprobe` command to load a module and set options."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:176
msgid ""
":command:`modprobe` may add or remove more than one module due to module "
"interdependencies. You can specify which options to use with individual "
"modules, by using configuration files under the :file:`/etc/modprobe.d` "
"directory."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:184
msgid ""
"All files underneath the :file:`/etc/modprobe.d` directory that end with "
"the :file:`.conf` extension specify module options to use when loading. "
"You can use :file:`.conf` files to create convenient aliases for modules "
"or to override the normal loading behavior altogether for those with "
"special requirements."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:189
msgid "Learn more about :command:`modprobe` on the modprobe.d manual page:"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:196
msgid "Optional: Configure kernel modules to load at boot"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:198
msgid ""
"Use the :file:`/etc/modules-load.d` configuration directory to specify "
"kernel modules to load automatically at boot."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:205
msgid ""
"All files underneath the :file:`/etc/modules-load.d` directory that end "
"with the :file:`.conf` extension contain a list of module names of "
"aliases (one per line) to load at boot."
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:209
msgid "Learn more about module loading in the modules-load.d manual page:"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:219
msgid "Related topic"
msgstr ""
#: ../../guides/kernel/kernel-modules.rst:221
msgid ":ref:`kernel-modules-dkms`"
msgstr ""
#~ msgid "Make enhancement requests to the |CL| distribution `on GitHub`_."
#~ msgstr ""
#~ msgid ""
#~ "Follow the steps in this section "
#~ "if you are an individual user or"
#~ " testing, and you need an out-"
#~ "of-tree kernel module that is not "
#~ "available through |CL|. For a more "
#~ "scalable and customizable approach, we "
#~ "recommend using the `mixer tool`_ to "
#~ "provide a custom kernel and updates."
#~ msgstr ""
#~ msgid ""
#~ "Make enhancement requests to the |CL|"
#~ " `Distribution Project "
#~ "<https://github.com/clearlinux/distribution>`_ on GitHub."
#~ msgstr ""
#~ msgid "`linux-dev` for developing against the native kernel."
#~ msgstr ""
#~ msgid "`linux-lts-dev` for developing against the LTS kernel."
#~ msgstr ""
locale/de/LC_MESSAGES/guides/maintenance/architect-lifecycle.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/maintenance/architect-lifecycle.po
-207
View File
@@ -1,207 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/maintenance/architect-lifecycle.rst:4
msgid "Architect the life-cycle of |CL-ATTR|"
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:6
msgid ""
"This guide describes the basic, recommended infrastructure and workflow "
"for maintaining a |CL-ATTR| derivative."
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:14
msgid "Prerequisites"
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:16
msgid ""
"A repository with software RPM artifacts and a CI/CD system with a |CL| "
"machine for building `mixes`"
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:19
msgid "Experience using :ref:`mixer <mixer>` to create a |CL|-based distro"
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:21
msgid ""
"Experience using :ref:`swupd <swupd-guide>` for maintaining the |CL| "
"build environment"
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:24
msgid "Familiarity with |CL| architecture and reuse of its content in releases"
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:27
msgid "Description"
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:29
msgid "Maintaining a |CL| derivative requires:"
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:31
msgid "Monitoring upstream |CL| for new releases"
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:32
msgid "Building software packages and staging"
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:33
msgid "Employing CI/CD automation for building releases"
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:34
msgid "Integrating Quality Assurance for testing and validation"
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:36
msgid ""
"Coordinated infrastructure is deployed to automate the life-cycle of your"
" |CL| derivative. We divide deployment of this infrastucture in two "
"parts: *Content Workflow*; and *Release Workflow*, shown in Figure 1."
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:44
msgid "Figure 1: Architect the life-cycle"
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:47
msgid "Content Workflow"
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:49
msgid ""
"The Content Workflow (Figure 1) orchestrates the processes used to manage"
" the creation of content for the distribution. This includes everything "
"from detecting a new release in a custom software repository to "
"generating RPM package files. The RPM files serve as intermediary "
"artifacts that track software dependencies and provide file-level data "
"consumed in a Release Workflow. The `Watcher Pipeline`_ checks |CL| and "
"a content provider, such as Koji, to determine if a new release is "
"necessary."
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:58
msgid "Release Workflow"
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:60
msgid ""
"The Release Workflow (Figure 1) gathers the content of the RPMs and "
"ensures it can be consumed by :ref:`mixer <mixer>`. A content web server "
"hosts the |CL| derivative, to which targets connect for updating their "
"OSes. As an integral part of this toolchain, the `Release Pipeline`_ "
"enables these derivatives to incorporate |CL| content into their own "
"custom content. The Watcher Pipeline triggers the Release Pipeline to "
"create new releases."
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:69
msgid "Implementation"
msgstr ""
#: ../../guides/maintenance/architect-lifecycle.rst:71
msgid ""
"The |CL| Distro Factory manages the Release Workflow. For detailed "
"information about Distro Factory deployment, refer to the `clr-distro-"
"factory`_ GitHub\\* repo."
msgstr ""
#~ msgid ""
#~ "Distro factory implements the *Release "
#~ "workflow*. To get started on a "
#~ "full implementation, visit |CL| `Distro "
#~ "factory documentation`_."
#~ msgstr ""
#~ msgid ""
#~ "This guide provides DevOps with a "
#~ "model to architect the life-cycle "
#~ "of a |CL| derivative that integrates "
#~ "custom software and content using "
#~ "distinct workflows."
#~ msgstr ""
#~ msgid "This guide provides the foundation of the recommended infrastructure."
#~ msgstr ""
#~ msgid ""
#~ "Coordinated infrastructure is deployed to "
#~ "automate the life-cycle of your "
#~ "|CL| derivative. We divide deployment of"
#~ " this infrastucture in two parts: "
#~ "*Content Workflow*; and *Release Workflow*,"
#~ " shown in Figure 1. Distro Factory"
#~ " manages the *Release Workflow* while "
#~ "capturing the requirements for maintaining "
#~ "a long-term release cadence."
#~ msgstr ""
#~ msgid "Content workflow"
#~ msgstr ""
#~ msgid ""
#~ "The *Content Workflow* (Figure 1) "
#~ "orchestrates the processes used to "
#~ "manage the creation of content for "
#~ "the distribution. This includes everything "
#~ "from detecting a new release in a"
#~ " custom software repository to generating"
#~ " RPM package files. The RPM files "
#~ "serve as intermediary artifacts that "
#~ "track software dependencies and provide "
#~ "file-level data consumed in a "
#~ "*Release Workflow*. The `Watcher Pipeline`_"
#~ " checks |CL| and a content provider,"
#~ " such as Koji, to determine if "
#~ "a new release is necessary."
#~ msgstr ""
#~ msgid "Release workflow"
#~ msgstr ""
#~ msgid ""
#~ "The *Release Workflow* (Figure 1) "
#~ "gathers the content of the RPMs "
#~ "and ensures it can be consumed by"
#~ " :ref:`mixer <mixer>`. A content web "
#~ "server hosts the |CL| derivative, to "
#~ "which targets connect for updating their"
#~ " OSes. As an integral part of "
#~ "this toolchain, the *Release Pipeline* "
#~ "enables these derivatives to incorporate "
#~ "|CL| content into their own custom "
#~ "content. The *Watcher Pipeline* triggers "
#~ "the `Release Pipeline`_ to create new"
#~ " releases."
#~ msgstr ""
#~ msgid ""
#~ "Distro factory implements the *Release "
#~ "workflow*. To get started on a "
#~ "full implementation, visit |CL| `Distro "
#~ "Factory`_ documentation."
#~ msgstr ""
locale/de/LC_MESSAGES/guides/maintenance/assign-static-ip.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/maintenance/assign-static-ip.po
-318
View File
@@ -1,318 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/maintenance/assign-static-ip.rst:4
msgid "Assign a static IP address"
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:7
msgid ""
"This guide explains how to assign a static IP address. This may be "
"helpful in scenarios such as a network with no DHCP server."
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:15
msgid "Identify which program is managing the interface"
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:17
msgid ""
"New installations of |CL-ATTR| use NetworkManager as the default network "
"interface manager for all network connections."
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:22
msgid ""
"The cloud |CL| images continue to use `systemd-networkd` to manage "
"network connections."
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:25
msgid ""
"In earlier |CL| versions, `systemd-network` was used to manage Ethernet "
"interfaces and NetworkManager was used for wireless interfaces."
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:29
msgid ""
"Before defining a configuration for assigning a static IP address, verify"
" which program is managing the network interface."
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:32
msgid ""
"Check the output of :command:`nmcli device` to see if NetworkManager is "
"managing the device."
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:39
msgid ""
"If the STATE column for the device shows *connected* or *disconnected*, "
"the network configuration is being managed by NetworkManager, then use "
"the instructions for :ref:`using NetworkManager <nm-static-ip>`."
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:43
msgid ""
"If the STATE column for the device shows *unmanaged*, then check if the "
"device is being managed by systemd-networkd."
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:47
msgid ""
"Check the output of :command:`networkctl list` to see if `systemd-"
"networkd` is managing the device."
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:54
msgid ""
"If the SETUP column for the device shows *configured*, the network "
"configuration is being managed by `systemd-networkd`, then use the "
"instructions for :ref:`using systemd-networkd <networkd-static-ip>`."
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:62
msgid "Using NetworkManager"
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:64
msgid ""
"Network connections managed by NetworkManager are stored as files with "
"the :file:`.nmconnection` file extension in the "
":file:`/etc/NetworkManager/system-connections/` directory."
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:68
msgid ""
"A few tools exists to aid to manipulate network connections managed by "
"NetworkManager:"
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:71
msgid "nmcli - a command-line tool"
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:73
msgid ""
"nmtui - a text user interface that provides a pseudo graphical menu in "
"the terminal"
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:76
msgid "nm-connection-editor - a graphical user interface"
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:78
msgid ""
"The method below uses the command line tool nmcli to modify network "
"connection."
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:82
msgid "Identify the existing connection name:"
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:88
msgid "Sample output:"
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:95
msgid ""
"If a connection does not exist, create it with the :command:`nmcli "
"connection add` command."
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:99
msgid ""
"Modify the connection to use a static IP address. Replace the variables "
"in brackets with the appropriate values. Replace *[CONNECTION_NAME]* with"
" the NAME from the command above."
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:112
msgid ""
"See the `nmcli developer page "
"<https://developer.gnome.org/NetworkManager/stable/nmcli.html>`_ for more"
" configuration options. For advanced configurations, the "
":file:`/etc/NetworkManager/system-connections/*.nmconnection`. can be "
"edited directly."
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:118
msgid "Restart the NetworkManager server to reload the DNS servers:"
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:125
#: ../../guides/maintenance/assign-static-ip.rst:179
msgid "Verify your static IP address details have been set:"
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:136
msgid "Using systemd-networkd"
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:138
msgid ""
"Network connections managed by systemd-networkd are stored as files with "
"the :file:`.network` file extension the :file:`/etc/systemd/network/` "
"directory."
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:141
msgid ""
"Files to manipulate network connections managed by systemd-networkd must "
"be created manually."
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:144
msgid ""
"Create the :file:`/etc/systemd/network` directory if it does not already "
"exist:"
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:150
msgid ""
"Create a :file:`.network` file and add the following content. Replace the"
" variables in brackets with the appropriate values. Replace "
"*[INTERFACE_NAME]* with LINK from the output of the :command:`networkctl "
"list` command that was run previously."
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:168
msgid ""
"See the `systemd-network man page "
"<https://www.freedesktop.org/software/systemd/man/systemd.network.html>`_"
" for more configuration options."
msgstr ""
#: ../../guides/maintenance/assign-static-ip.rst:172
msgid "Restart the `systemd-networkd` service:"
msgstr ""
#~ msgid ""
#~ "By default, your |CL-ATTR| system "
#~ "automatically gets an IP address from"
#~ " your network via DHCP. If you "
#~ "do not have a DHCP server on "
#~ "your network or simply want to use"
#~ " a static IP address, follow the "
#~ "steps in this guide."
#~ msgstr ""
#~ msgid ""
#~ "New installations of |CL| use "
#~ "NetworkManager as the default network "
#~ "interface manager for all network "
#~ "connections."
#~ msgstr ""
#~ msgid ""
#~ "The *cloud* |CL| images continue to "
#~ "use systemd-networkd to manage network"
#~ " connections."
#~ msgstr ""
#~ msgid ""
#~ "In earlier |CL| versions, systemd-"
#~ "network was used to manage Ethernet "
#~ "interfaces and NetworkManager was used "
#~ "for wireless interfaces."
#~ msgstr ""
#~ msgid ""
#~ "Before defining a configuration for "
#~ "assigning a static IP address, you "
#~ "should verify which program is managing"
#~ " the network interface."
#~ msgstr ""
#~ msgid ""
#~ "If the STATE column for the device"
#~ " shows *connected* or *disconnected*, the"
#~ " network configuration is being managed "
#~ "by NetworkManager and the instructions "
#~ "for :ref:`using NetworkManager <nm-static-"
#~ "ip>` should be used."
#~ msgstr ""
#~ msgid ""
#~ "If the STATE column for the device"
#~ " shows *unmanaged*, check to see if"
#~ " the device is being managed by "
#~ "systemd-networkd"
#~ msgstr ""
#~ msgid ""
#~ "Check the output of :command:`networkctl "
#~ "list` to see if systemd-networkd "
#~ "is managing the device."
#~ msgstr ""
#~ msgid ""
#~ "If the SETUP column for the device"
#~ " shows *configured*, the network "
#~ "configuration is being managed by "
#~ "systemd-networkd and the instructions for"
#~ " :ref:`using systemd-networkd <networkd-"
#~ "static-ip>` should be used."
#~ msgstr ""
#~ msgid ""
#~ "The method below uses the command "
#~ "line tool *nmcli* to modify network "
#~ "connection."
#~ msgstr ""
#~ msgid "The output will look like this:"
#~ msgstr ""
#~ msgid ""
#~ "If a connection does not exist, it"
#~ " will need to be created with "
#~ ":command:`nmcli connection add`."
#~ msgstr ""
#~ msgid ""
#~ "Modify the connection to use a "
#~ "static IP address. Replace the variables"
#~ " in brackets with the appropriate "
#~ "values. *[CONNECTION_NAME]* should be replaced"
#~ " with the NAME from the command "
#~ "above."
#~ msgstr ""
#~ msgid ""
#~ "Create the :file:`/etc/systemd/network` directory"
#~ " if it doesn't exist already:"
#~ msgstr ""
#~ msgid ""
#~ "Create a :file:`.network` file and add"
#~ " the following content. Replace the "
#~ "variables in brackets with the "
#~ "appropriate values. *[INTERFACE_NAME]* should "
#~ "be replaced with LINK from the "
#~ "output of :command:`networkctl list` ran "
#~ "previously."
#~ msgstr ""
#~ msgid "Restart the systemd-networkd service:"
#~ msgstr ""
locale/de/LC_MESSAGES/guides/maintenance/bulk-provision.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/maintenance/bulk-provision.po
-354
View File
@@ -1,354 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/maintenance/bulk-provision.rst:4
msgid "Bulk provision"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:6
msgid ""
"This guide explains how to perform a bulk provision of |CL-ATTR| using a "
"combination of the |CL| installer, Ister, and :abbr:`ICIS (Ister Cloud "
"Init Service)`."
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:15
msgid "Overview"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:17
msgid "To configure a bulk provision:"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:19
msgid "Define Ister configuration files to customize the installation process"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:20
msgid "Define cloud-init\\* files to customize the installation instance"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:21
msgid ""
"Host the configuration files in ICIS to allow Ister to use them during "
"the installation"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:24
msgid ""
"Figure 1 depicts the flow of information between a PXE server and a PXE "
"client that needs to be set up to perform a bulk provision."
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:30
msgid "Figure 1: Bulk provision information flow"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:33
msgid "Prerequisites"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:35
msgid ""
"Before performing a bulk provision, verify you have a PXE server capable "
"of performing network boots of |CL|. Please refer to our :ref:`guide on "
"how to perform an iPXE boot<ipxe-install>` using :abbr:`NAT (network "
"address translation)` for details."
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:40
msgid ""
"Because a bulk provision relies on a reboot, ensure the following "
"preparations have been made:"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:43
msgid "No existing disks are bootable."
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:44
msgid ""
"The network boot option must come immediately after the disk boot option "
"on any computer performing the installation."
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:48
msgid "Configuration"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:50
msgid ""
"Install ICIS by following the getting started guide on the `ICIS`_ "
"GitHub\\* repository."
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:53
msgid ""
"Create an Ister installation file and save it to the :file:`static/ister`"
" directory within the web hosting directory for ICIS. The installation "
"file is a JSON block and provides Ister with the steps it needs to "
"perform an installation. The file outlines what partitions, file systems,"
" and mount points Ister should set up. Lastly, the file outlines which "
"bundles to install. See our :ref:`bundles` document for the list of "
"available bundles. The following example shows the contents of an Ister "
"installation file:"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:92
msgid ""
"Every Ister installation file hosted on ICIS must contain the the "
"`IsterCloudInitSvc` parameter as well as the :command:`os-cloudguest` "
"bundle. These entries allow Ister to customize an instance of of an "
"install."
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:97
msgid ""
"Create an Ister configuration file to define the location of the Ister "
"installation file. Save it to the :file:`static/ister` directory within "
"the web hosting directory of ICIS. The following example shows an Ister "
"configuration file:"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:106
msgid ""
"Modify the iPXE boot script by adding a kernel parameter to the command "
"line for booting the network image. Add the kernel parameter `isterconf` "
"with the location of the Ister configuration file hosted on ICIS as the "
"kernel parameter value. The following example shows an iPXE boot script "
"with the `isterconf` parameter:"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:121
msgid ""
"After the network image of |CL| boots, Ister inspects the parameters used"
" during boot in :file:`/proc/cmdline` to find the location of the Ister "
"configuration file."
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:125
msgid ""
"Write a cloud-init document to customize the instance of the installation"
" according to your requirements. The `cloud-init`_ documentation provides"
" a guide on how to write a cloud-init document. The guide covers the "
"customization options provided by cloud-init after an installation."
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:130
msgid ""
"Save the cloud-init document to the :file:`static/roles` directory within"
" the web hosting directory for ICIS with the name of a role you would "
"like to create. For example, a role may be \"database\", \"web\", or "
"\"ciao\"."
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:134
msgid ""
"After creating the roles, also known as cloud-init files, assign roles to"
" MAC addresses of PXE clients. To do so, modify the :file:`config.txt` "
"file in the :file:`static` directory within the web hosting directory of "
"ICIS. The following example shows an example assignment:"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:144
msgid ""
"If MAC addresses of PXE clients are not listed within the "
":file:`config.txt` file, a default role for those MAC address may be "
"defined as follows:"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:153
msgid "Verify the following URLs are accessible on your local network:"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:155
msgid "http://192.168.1.1:60000/icis/static/ister/ister.conf"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:156
msgid "http://192.168.1.1:60000/icis/static/ister/ister.json"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:157
msgid "http://192.168.1.1:60000/icis/get_config/<MAC address>"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:158
msgid "http://192.168.1.1:60000/icis/get_role/<role>"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:159
msgid "http://192.168.1.1:60000/ipxe/ipxe_boot_script.txt"
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:161
msgid "Power on the PXE client and watch it boot and install |CL|."
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:163
msgid "Power-cycle the PXE client and watch it customize the |CL| installation."
msgstr ""
#: ../../guides/maintenance/bulk-provision.rst:165
msgid ""
"**Congratulations!** You have successfully performed a bulk provision of "
"|CL|."
msgstr ""
#~ msgid ""
#~ "Install **ICIS** by following the "
#~ "getting started guide on the `ICIS "
#~ "GitHub repository`_."
#~ msgstr ""
#~ msgid ""
#~ "Write a cloud-init document to "
#~ "customize the instance of the "
#~ "installation according to your requirements."
#~ " The `cloud-init Read the Docs`_ "
#~ "provides a guide on how to write"
#~ " a cloud-init document. The guide "
#~ "covers the customization options provided "
#~ "by cloud-init after an installation."
#~ msgstr ""
#~ msgid ""
#~ "The |CL-ATTR| can be automatically "
#~ "provisioned in bulk using a combination"
#~ " of the |CL| installer, **Ister**, "
#~ "and :abbr:`ICIS (Ister Cloud Init "
#~ "Service)`. This guide covers how to "
#~ "perform a bulk provision of |CL| "
#~ "using **Ister** and **ICIS**."
#~ msgstr ""
#~ msgid ""
#~ "To configure a bulk provision, Ister "
#~ "configuration files and cloud-init files"
#~ " must be defined. Hosting the "
#~ "configuration files in **ICIS** allows "
#~ "**Ister** to use them during the "
#~ "installation. The Ister configuration files"
#~ " allow us to customize the "
#~ "installation process. The cloud-init\\* "
#~ "files allow us to customize the "
#~ "instance of the installation."
#~ msgstr ""
#~ msgid ""
#~ "Install **ICIS** by following the "
#~ "getting started guide on the `ICIS`_ "
#~ "GitHub repository."
#~ msgstr ""
#~ msgid ""
#~ "Create an Ister installation file and"
#~ " save it to the :file:`static/ister` "
#~ "directory within the web hosting "
#~ "directory for **ICIS**. The installation "
#~ "file is a JSON block and provides"
#~ " **Ister** with the steps it needs"
#~ " to perform an installation. The file"
#~ " outlines what partitions, file systems,"
#~ " and mount points **Ister** should "
#~ "set up. Lastly, the file outlines "
#~ "which bundles to install. See our "
#~ ":ref:`bundles` document for the list of"
#~ " available bundles. The following example"
#~ " shows the contents of an Ister "
#~ "installation file:"
#~ msgstr ""
#~ msgid ""
#~ "Every Ister installation file hosted on"
#~ " **ICIS** must contain the the "
#~ "``IsterCloudInitSvc`` parameter as well as "
#~ "the ``os-cloudguest`` bundle. These "
#~ "entries allow **Ister** to customize an"
#~ " instance of of an install."
#~ msgstr ""
#~ msgid ""
#~ "Create an Ister configuration file to"
#~ " define the location of the Ister "
#~ "installation file. Save it to the "
#~ ":file:`static/ister` directory within the web"
#~ " hosting directory of **ICIS**. The "
#~ "following example shows an Ister "
#~ "configuration file:"
#~ msgstr ""
#~ msgid ""
#~ "Modify the iPXE boot script by "
#~ "adding a kernel parameter to the "
#~ "command line for booting the network "
#~ "image. Add the kernel parameter "
#~ "``isterconf`` with the location of the"
#~ " Ister configuration file hosted on "
#~ "**ICIS** as the kernel parameter value."
#~ " The following example shows an iPXE"
#~ " boot script with the ``isterconf`` "
#~ "parameter:"
#~ msgstr ""
#~ msgid ""
#~ "After the network image of |CL| "
#~ "boots, **Ister** inspects the parameters "
#~ "used during boot in :file:`/proc/cmdline` "
#~ "to find the location of the Ister"
#~ " configuration file."
#~ msgstr ""
#~ msgid ""
#~ "Save the cloud-init document to "
#~ "the :file:`static/roles` directory within the"
#~ " web hosting directory for **ICIS** "
#~ "with the name of a role you "
#~ "would like to create. For example, "
#~ "a role may be \"database\", \"web\", "
#~ "or \"ciao\"."
#~ msgstr ""
#~ msgid ""
#~ "After creating the roles, also known "
#~ "as cloud-init files, assign roles "
#~ "to MAC addresses of PXE clients. "
#~ "To do so, modify the :file:`config.txt`"
#~ " file in the ``static`` directory "
#~ "within the web hosting directory of "
#~ "**ICIS**. The following example shows "
#~ "one such assignment:"
#~ msgstr ""
#~ msgid "``http://192.168.1.1:60000/icis/static/ister/ister.conf``"
#~ msgstr ""
#~ msgid "``http://192.168.1.1:60000/icis/static/ister/ister.json``"
#~ msgstr ""
#~ msgid "``http://192.168.1.1:60000/icis/get_config/<MAC address>``"
#~ msgstr ""
#~ msgid "``http://192.168.1.1:60000/icis/get_role/<role>``"
#~ msgstr ""
#~ msgid "``http://192.168.1.1:60000/ipxe/ipxe_boot_script.txt``"
#~ msgstr ""
locale/de/LC_MESSAGES/guides/maintenance/cpu-performance.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/maintenance/cpu-performance.po
-315
View File
@@ -1,315 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/maintenance/cpu-performance.rst:4
msgid "CPU Power and Performance"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:6
msgid "This guide explains the CPU power and performance mechanisms in |CL-ATTR|."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:13
msgid "Overview"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:15
msgid ""
"Modern x86 :abbr:`CPUs (central processing units)` employ a number of "
"features and technologies to balance performance, energy, and thermal "
"efficiencies."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:18
msgid ""
"By default, |CL| prioritizes maximum CPU performance with the philosophy "
"that the faster the program finishes execution, the faster the CPU can "
"return to a low energy idle state. It is important to understand and "
"evaluate all of these technologies when troubleshooting or considering "
"changing the defaults."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:28
msgid "CPU power saving mechanisms"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:30
msgid ""
"C-states and P-states are both CPU power saving mechanisms that are "
"entered under different operating conditions. The tradeoff is a slightly "
"longer time to exit these states when the CPU is needed once again."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:37
msgid "C-states (idle states)"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:39
msgid ""
"C-states are hardware sleep states that are entered when it is determined"
" that the CPU is idle and not executing instructions."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:42
msgid ""
"C-states aim to reduce power utilization by increasingly reducing clock "
"frequency, voltages, and features in each state."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:45
msgid ""
"Although C-states can typically be limited or disabled in a system's UEFI"
" or BIOS configuration, these settings are overridden when the "
"`intel_idle driver`_ is in use."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:49
msgid "To view the current cpuidle driver run this command in a terminal:"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:55
msgid ""
"For troubleshooting, C-states can be limited with a kernel command line "
"boot parameter by adding :command:`processor.max_cstate=N "
"intel_idle.max_cstate=N` or completely disabled with "
":command:`idle=poll`."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:61
msgid ""
":command:`processor.max_cstate=0` is changed to "
":command:`processor.max_cstate=1` by the kernel to be a valid value."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:64
msgid ""
":command:`intel_idle.max_cstate=0` disables the Intel Idle driver, not "
"set it to C-state 0."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:70
msgid "P-states (performance states)"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:72
msgid ""
"P-states, also known as *Intel SpeedStep® technology* on Intel processors"
" or *Cool'n'Quiet* on AMD processors, are states entered while the CPU is"
" active and executing instructions."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:76
msgid ""
"P-states aim to reduce power utilization by adjusting CPU clock frequency"
" and voltages based on CPU demand."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:79
msgid ""
"P-states can typically be limited or disabled in a system's firmware "
"(UEFI/BIOS)."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:82
msgid "Turbo boost"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:84
msgid ""
"`Intel® Turbo Boost Technology`_, found on some modern Intel CPUs, allows"
" core(s) on a processor to temporarily operate at a higher than rated CPU"
" clock frequency to accommodate demanding workloads if the CPU is under "
"defined power and thermal thresholds."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:89
msgid ""
"Turbo boost is an extension of P-states. As such, changing or limiting "
"C-states or P-states impact the ability of a process to enter Turbo "
"boost."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:92
msgid ""
"Turbo boost can be disabled in a system's UEFI or BIOS. Turbo boost can "
"also be disabled within |CL| with the command:"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:100
msgid "Linux CPU clock frequency scaling"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:102
msgid ""
"The CPUFreq subsystem in Linux allows the OS to control :ref:`C-states <c"
"-states-section>` and :ref:`P-states <P-states-section>` via CPU drivers "
"and governors that provide algorithms that define how and when to enter "
"these states."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:108
msgid "Scaling driver"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:110
msgid ""
"Linux uses the `Intel P-state driver`_, :command:`intel_pstate`, for "
"modern Intel processors from the Sandy Bridge generation or newer. Other "
"processors may default to the :command:`acpi-cpufreq*` driver which reads"
" values from the systems UEFI or BIOS."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:115
msgid ""
"To view the current CPU frequency scaling driver run this command in a "
"terminal:"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:122
msgid "Scaling governor"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:124
msgid ""
"|CL| sets the CPU governor to *performance* which calls for the CPU to "
"operate at maximum clock frequency. In other words, P-state P0. While "
"this may sound wasteful at first, it is important to remember that power "
"utilization does not increase significantly simply because of a locked "
"clock frequency without a workload."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:130
msgid ""
"To view the current CPU frequency scaling governor run this command in a "
"terminal:"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:136
msgid "To change the CPU frequency scaling governor:"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:138
msgid "Disable |CL| enforcement of certain power and performance settings:"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:144
msgid ""
"Change the governor. In the example below, the governor is set to "
"*performance*:"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:151
msgid ""
"The list of all governors can be found in the Linux kernel documentation "
"on `CPUFreq Governors`_."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:156
msgid ""
"The intel_pstate driver only supports *performance* and *powersave* "
"governors."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:159
msgid "Thermal management"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:161
msgid ""
"`thermald`_ is a Linux thermal management daemon used to prevent the "
"overheating of platforms. When temperature thresholds are exceeded, "
"thermald forces a C-state by inserting CPU sleep cycles and adjusts "
"available cooling methods. This can be especially desirable for laptops."
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:166
msgid ""
"By default, thermald is disabled in |CL| and starts automatically if "
"battery power is detected. thermald can be manually enabled using the "
"systemd service by running the command:"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:175
msgid "For more information, see the thermald man page:"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:181
msgid ""
"`ThermalMonitor`_ is a GUI application that can visually graph and log "
"temperatures from thermald. To use ThermalMonitor, add the :command"
":`desktop-apps-extras` bundle and add your user account to the power "
"group:"
msgstr ""
#: ../../guides/maintenance/cpu-performance.rst:194
msgid ""
"After adding a new group, you must log out and log back in for the new "
"group to take effect."
msgstr ""
#~ msgid ""
#~ "The list of all governors can be"
#~ " found in the `Linux kernel "
#~ "documentation on CPUFreq Governors`_."
#~ msgstr ""
#~ msgid ""
#~ "P-states, also known as *SpeedStep* on"
#~ " Intel processors or *Cool'n'Quiet* on "
#~ "AMD processors, are states entered while"
#~ " the CPU is active and executing "
#~ "instructions."
#~ msgstr ""
#~ msgid ""
#~ "`Turbo Boost technology`_, found on some"
#~ " modern Intel CPUs, allows core(s) on"
#~ " a processor to temporarily operate "
#~ "at a higher than rated CPU clock"
#~ " frequency to accommodate demanding "
#~ "workloads if the CPU is under "
#~ "defined power and thermal thresholds."
#~ msgstr ""
#~ msgid ""
#~ "Linux uses the `Intel P-state driver`_,"
#~ " *intel_pstate*, for modern Intel "
#~ "processors from the Sandy Bridge "
#~ "generation or newer. Other processors "
#~ "may default to the *acpi-cpufreq* "
#~ "driver which reads values from the "
#~ "systems UEFI or BIOS."
#~ msgstr ""
#~ msgid ""
#~ "`ThermalMonitor`_ is a GUI application "
#~ "that can visually graph and log "
#~ "temperatures from thermald. To use "
#~ "ThermalMonitor, add the desktop-apps-"
#~ "extras bundle and add your user "
#~ "account to the power group:"
#~ msgstr ""
#~ msgid ""
#~ "After adding a new group you must"
#~ " log out and log back in for"
#~ " the new group to take affect."
#~ msgstr ""
locale/de/LC_MESSAGES/guides/maintenance/developer-workstation.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/maintenance/developer-workstation.po
-286
View File
@@ -1,286 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/maintenance/developer-workstation.rst:4
msgid "Developer Workstation"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:6
msgid ""
"This guide helps you find the minimum set of bundles needed to start your"
" |CL-ATTR| development project."
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:9
msgid ""
"Before continuing, review the :ref:`swupd <swupd-guide>` guide to learn "
"more about the swupd tool and how |CL| simplifies software versioning "
"compared to other Linux\\* distributions."
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:18
msgid "Workstation Setup"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:20
msgid ""
"After installing the minimum set of bundles required to get started, you "
"can add more bundles relevant to your specific use case."
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:23
msgid ""
"To run any process required for |CL| development, you can add the large "
"bundle :ref:`*os-clr-on-clr* <enable-user-space>`. However, given how "
"many packages this bundle contains, you may want to deploy a leaner OS "
"with only bundles relevant to your project."
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:28
msgid ""
"Use Table 1, *Developer Profiles*, to identify the *minimum required "
"bundles* to get started developing based on your role or project. While "
"your role may not neatly fit in one of these categories, consider Table 1"
" as a starting point."
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:33
msgid "**Table 1. Developer Profiles**"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:37
msgid "|CL| Bundle"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:38
msgid "*Internet of Things (IoT)*"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:39
msgid "*System Administrator*"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:40
msgid "*Client/Cloud/Web Developer*"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:42
msgid ":command:`editors`"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:43
#: ../../guides/maintenance/developer-workstation.rst:44
#: ../../guides/maintenance/developer-workstation.rst:45
#: ../../guides/maintenance/developer-workstation.rst:48
#: ../../guides/maintenance/developer-workstation.rst:49
#: ../../guides/maintenance/developer-workstation.rst:50
#: ../../guides/maintenance/developer-workstation.rst:53
#: ../../guides/maintenance/developer-workstation.rst:54
#: ../../guides/maintenance/developer-workstation.rst:55
#: ../../guides/maintenance/developer-workstation.rst:59
#: ../../guides/maintenance/developer-workstation.rst:60
#: ../../guides/maintenance/developer-workstation.rst:64
#: ../../guides/maintenance/developer-workstation.rst:65
#: ../../guides/maintenance/developer-workstation.rst:69
#: ../../guides/maintenance/developer-workstation.rst:70
#: ../../guides/maintenance/developer-workstation.rst:73
#: ../../guides/maintenance/developer-workstation.rst:74
#: ../../guides/maintenance/developer-workstation.rst:75
#: ../../guides/maintenance/developer-workstation.rst:80
msgid "✓"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:47
msgid ":command:`network-basic`"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:52
msgid ":command:`openssh-server`"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:57
msgid ":command:`webserver-basic`"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:62
msgid ":command:`application-server`"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:67
msgid ":command:`database-basic`"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:72
msgid ":command:`desktop-autostart`"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:77
msgid ":command:`dev-utils`"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:83
msgid "swupd search"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:85
msgid ""
"We recommend learning about :ref:`swupd <swupd-guide>`, to learn the "
"commands to search for and add bundles relevant to your project."
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:88
msgid ""
"The guide provides an :ref:`example <swupd-guide-example-install-bundle>`"
" that shows you how to:"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:91
msgid "Use swupd to search for bundles"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:92
msgid "Use swupd to add bundles"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:95
msgid "Core Concepts"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:97
msgid ""
"We recommend that you understand these core concepts in |CL| *before* "
"developing your project."
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:100
msgid ":ref:`Software update <swupd-guide>`"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:101
msgid ":ref:`Mixer <mixer>`"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:102
msgid ":ref:`Autospec <autospec>`"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:105
msgid "Other resources for developers"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:107
msgid "`Developer Tooling Framework`_ for |CL|"
msgstr ""
#: ../../guides/maintenance/developer-workstation.rst:108
msgid "`Bundle Definition Files`_"
msgstr ""
#~ msgid "`Bundle definition files`_"
#~ msgstr ""
#~ msgid ""
#~ "*Developer Workstation* helps you find "
#~ "the :ref:`bundles-about` you need to "
#~ "start your |CL-ATTR| development "
#~ "project."
#~ msgstr ""
#~ msgid ""
#~ "Before continuing, we recommend that you"
#~ " learn how to use :ref:`swupd "
#~ "<swupd-guide>`. Visit our :ref:`swupd-"
#~ "about` page to understand how |CL| "
#~ "simplifies software versioning compared to "
#~ "other Linux\\* distributions."
#~ msgstr ""
#~ msgid ""
#~ "This guide helps you understand the "
#~ "minimum bundles required to get started."
#~ " After installing them, you can add"
#~ " more bundles relevant to your use"
#~ " case. To run any process required"
#~ " for |CL| development, you can add"
#~ " the large bundle :ref:`*os-clr-"
#~ "on-clr* <enable-user-space>`. However, "
#~ "given how many packages this bundle "
#~ "contains, you may want instead to "
#~ "deploy a leaner OS with only those"
#~ " bundles relevant to your project. "
#~ "Developer Workstation responds to this "
#~ "need."
#~ msgstr ""
#~ msgid ""
#~ "Use Table 1, *Developer Profiles*, to"
#~ " identify the *minimum required bundles*"
#~ " to get started developing based on"
#~ " your role or project. While your "
#~ "role may not neatly fit in one "
#~ "of these categories, consider using "
#~ "Table 1 as a starting point."
#~ msgstr ""
#~ msgid "`editors`"
#~ msgstr ""
#~ msgid "`network-basic`"
#~ msgstr ""
#~ msgid "`openssh-server`"
#~ msgstr ""
#~ msgid "`webserver-basic`"
#~ msgstr ""
#~ msgid "`application-server`"
#~ msgstr ""
#~ msgid "`database-basic`"
#~ msgstr ""
#~ msgid "`desktop-autostart`"
#~ msgstr ""
#~ msgid "`dev-utils`"
#~ msgstr ""
#~ msgid "`swupd` search"
#~ msgstr ""
#~ msgid "Use `swupd` to search for bundles"
#~ msgstr ""
#~ msgid "Use `swupd` to add bundles"
#~ msgstr ""
#~ msgid ":ref:`Bundles <bundles-about>`"
#~ msgstr ""
#~ msgid ":ref:`Software update <swupd-about>`"
#~ msgstr ""
#~ msgid ":ref:`Mixer <mixer-about>`"
#~ msgstr ""
#~ msgid ":ref:`Autospec <autospec-about>`"
#~ msgstr ""
locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-linux.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-linux.po
-282
View File
@@ -1,282 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-12 12:18-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/maintenance/download-verify-decompress-linux.rst:4
msgid "Download, verify, and decompress a |CL-ATTR| image on Linux"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-linux.rst:6
msgid ""
"This guide describes the types of |CL| images available, where to "
"download them, how to verify the integrity of an image, and how to "
"decompress it."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-linux.rst:9
msgid "Instructions for other operating systems are available:"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-linux.rst:11
msgid ":ref:`download-verify-decompress-mac`"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-linux.rst:12
msgid ":ref:`download-verify-decompress-windows`"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-linux.rst:15
msgid "Image types"
msgstr ""
#: ../../reference/image-types.rst:3
msgid ""
"|CL-ATTR| offers many types of `images`_ for different platforms and "
"environments."
msgstr ""
#: ../../reference/image-types.rst:7
msgid "The naming convention of a |CL| image filename is:"
msgstr ""
#: ../../reference/image-types.rst:13
msgid "The *[version number]* field specifies the version number."
msgstr ""
#: ../../reference/image-types.rst:15
msgid ""
"The *[image type]* field specifies the type of image and its "
"corresponding file format."
msgstr ""
#: ../../reference/image-types.rst:18
msgid ""
"The *[compression type]* field specifies the compression type. Two types "
"of compressions are used: GNU\\* zip (*.gz*) and XZ (*.xz*)."
msgstr ""
#: ../../reference/image-types.rst:23
msgid ""
"Table 1 lists the currently available images that are platform "
"independent. Table 2 lists the currently available images that are "
"platform specific."
msgstr ""
#: ../../reference/image-types.rst:26
msgid "Table 1: Types of platform-independent |CL| images"
msgstr ""
#: ../../reference/image-types.rst:30 ../../reference/image-types.rst:43
msgid "Image Type"
msgstr ""
#: ../../reference/image-types.rst:31 ../../reference/image-types.rst:44
msgid "Description"
msgstr ""
#: ../../reference/image-types.rst:33
msgid "live-desktop.img or live-desktop.iso"
msgstr ""
#: ../../reference/image-types.rst:34
msgid "Image for booting to GNOME\\* desktop to preview or install the OS."
msgstr ""
#: ../../reference/image-types.rst:36
msgid "live-server.img or live-server.iso"
msgstr ""
#: ../../reference/image-types.rst:37
msgid "Image for booting to server command prompt to preview or install the OS."
msgstr ""
#: ../../reference/image-types.rst:39
msgid "Table 2: Types of platform-specific |CL| images"
msgstr ""
#: ../../reference/image-types.rst:46
msgid "aws.img"
msgstr ""
#: ../../reference/image-types.rst:47
msgid "Image suitable for use with Amazon\\* AWS\\*."
msgstr ""
#: ../../reference/image-types.rst:49
msgid "azure.vhd"
msgstr ""
#: ../../reference/image-types.rst:50
msgid "Virtual Hard Disk for use on Microsoft\\* Azure\\* cloud platform."
msgstr ""
#: ../../reference/image-types.rst:52
msgid "azure-docker.vhd"
msgstr ""
#: ../../reference/image-types.rst:53
msgid ""
"Virtual Hard Disk for use on Microsoft Azure cloud platform with "
"Docker\\* pre-installed."
msgstr ""
#: ../../reference/image-types.rst:55
msgid "azure-machine-learning.vhd"
msgstr ""
#: ../../reference/image-types.rst:56
msgid ""
"Virtual Hard Disk for use on Microsoft Azure cloud platform with the "
"`machine-learning-basic` bundle installed."
msgstr ""
#: ../../reference/image-types.rst:58
msgid "cloudguest.img"
msgstr ""
#: ../../reference/image-types.rst:59
msgid ""
"Image with generic cloud guest virtual machine (VM) requirements "
"installed."
msgstr ""
#: ../../reference/image-types.rst:61
msgid "gce.tar"
msgstr ""
#: ../../reference/image-types.rst:62
msgid "Image with the Google Compute Engine (GCE) specific kernel."
msgstr ""
#: ../../reference/image-types.rst:64
msgid "hyperv.vhdx"
msgstr ""
#: ../../reference/image-types.rst:65
msgid ""
"Virtual Hard Disk for use with Microsoft Hyper-V\\* hypervisor. Includes "
"`optimized kernel`_ for Hyper-V."
msgstr ""
#: ../../reference/image-types.rst:67
msgid "kvm.img"
msgstr ""
#: ../../reference/image-types.rst:68
msgid ""
"Image for booting in a simple VM with start_qemu.sh. Includes `optimized "
"kernel`_ for KVM."
msgstr ""
#: ../../reference/image-types.rst:71
msgid "kvm-legacy.img"
msgstr ""
#: ../../reference/image-types.rst:72
msgid ""
"Image for booting in a simple VM using legacy BIOS, if using "
"start_qemu.sh make sure to remove -bios parameter."
msgstr ""
#: ../../reference/image-types.rst:74
msgid "pxe.tar"
msgstr ""
#: ../../reference/image-types.rst:75
msgid "Image suitable for use with PXE server."
msgstr ""
#: ../../reference/image-types.rst:77
msgid "vmware.vmdk"
msgstr ""
#: ../../reference/image-types.rst:78
msgid ""
"Virtual Machine Disk for VMware\\* platforms inclduing Player, "
"Workstation, and ESXi."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-linux.rst:23
msgid "Verify the integrity of the |CL| image"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-linux.rst:25
msgid ""
"Before you use a downloaded |CL| image, verify its integrity. This action"
" eliminates the small chance of a corrupted image due to download issues."
" To support verification, each released |CL| image has a corresponding "
"SHA512 checksum file designated with the suffix `-SHA512SUMS`."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-linux.rst:30
msgid "Download the corresponding SHA512 checksum file of your |CL| image."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-linux.rst:31
#: ../../guides/maintenance/download-verify-decompress-linux.rst:57
msgid "Start a terminal emulator."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-linux.rst:32
msgid "Go to the directory with the downloaded image and checksum files."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-linux.rst:33
msgid ""
"Verify the integrity of the image and compare it to its original checksum"
" with the command:"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-linux.rst:40
msgid ""
"If the checksum of the downloaded image is different than the original "
"checksum, a warning is displayed with a message indicating the computed "
"checksum does **not** match. Otherwise, the name of the image is printed "
"on the screen followed by `OK`."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-linux.rst:45
msgid ""
"For a more in-depth discussion of image verification including checking "
"the certificate see :ref:`image-content-validation`."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-linux.rst:51
msgid "Decompress the |CL| image"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-linux.rst:53
msgid ""
"Released |CL| images are compressed with either GNU zip (*.gz*) or XZ "
"(*.xz*). The compression type depends on the target platform or "
"environment. To decompress the image, follow these steps:"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-linux.rst:58
msgid "Go to the directory with the downloaded image."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-linux.rst:60
msgid "To decompress an XZ image, enter:"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-linux.rst:66
msgid "To decompress a GZ image, enter:"
msgstr ""
locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-mac.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-mac.po
-273
View File
@@ -1,273 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-12 12:18-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/maintenance/download-verify-decompress-mac.rst:4
msgid "Download, verify, and decompress a |CL-ATTR| image on macOS\\*"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-mac.rst:6
msgid ""
"This guide describes the types of |CL| images available, where to "
"download them, how to verify the integrity of an image, and how to "
"decompress it."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-mac.rst:9
msgid "Instructions for other operating systems are available:"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-mac.rst:11
msgid ":ref:`download-verify-decompress-linux`"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-mac.rst:12
msgid ":ref:`download-verify-decompress-windows`"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-mac.rst:15
msgid "Image types"
msgstr ""
#: ../../reference/image-types.rst:3
msgid ""
"|CL-ATTR| offers many types of `images`_ for different platforms and "
"environments."
msgstr ""
#: ../../reference/image-types.rst:7
msgid "The naming convention of a |CL| image filename is:"
msgstr ""
#: ../../reference/image-types.rst:13
msgid "The *[version number]* field specifies the version number."
msgstr ""
#: ../../reference/image-types.rst:15
msgid ""
"The *[image type]* field specifies the type of image and its "
"corresponding file format."
msgstr ""
#: ../../reference/image-types.rst:18
msgid ""
"The *[compression type]* field specifies the compression type. Two types "
"of compressions are used: GNU\\* zip (*.gz*) and XZ (*.xz*)."
msgstr ""
#: ../../reference/image-types.rst:23
msgid ""
"Table 1 lists the currently available images that are platform "
"independent. Table 2 lists the currently available images that are "
"platform specific."
msgstr ""
#: ../../reference/image-types.rst:26
msgid "Table 1: Types of platform-independent |CL| images"
msgstr ""
#: ../../reference/image-types.rst:30 ../../reference/image-types.rst:43
msgid "Image Type"
msgstr ""
#: ../../reference/image-types.rst:31 ../../reference/image-types.rst:44
msgid "Description"
msgstr ""
#: ../../reference/image-types.rst:33
msgid "live-desktop.img or live-desktop.iso"
msgstr ""
#: ../../reference/image-types.rst:34
msgid "Image for booting to GNOME\\* desktop to preview or install the OS."
msgstr ""
#: ../../reference/image-types.rst:36
msgid "live-server.img or live-server.iso"
msgstr ""
#: ../../reference/image-types.rst:37
msgid "Image for booting to server command prompt to preview or install the OS."
msgstr ""
#: ../../reference/image-types.rst:39
msgid "Table 2: Types of platform-specific |CL| images"
msgstr ""
#: ../../reference/image-types.rst:46
msgid "aws.img"
msgstr ""
#: ../../reference/image-types.rst:47
msgid "Image suitable for use with Amazon\\* AWS\\*."
msgstr ""
#: ../../reference/image-types.rst:49
msgid "azure.vhd"
msgstr ""
#: ../../reference/image-types.rst:50
msgid "Virtual Hard Disk for use on Microsoft\\* Azure\\* cloud platform."
msgstr ""
#: ../../reference/image-types.rst:52
msgid "azure-docker.vhd"
msgstr ""
#: ../../reference/image-types.rst:53
msgid ""
"Virtual Hard Disk for use on Microsoft Azure cloud platform with "
"Docker\\* pre-installed."
msgstr ""
#: ../../reference/image-types.rst:55
msgid "azure-machine-learning.vhd"
msgstr ""
#: ../../reference/image-types.rst:56
msgid ""
"Virtual Hard Disk for use on Microsoft Azure cloud platform with the "
"`machine-learning-basic` bundle installed."
msgstr ""
#: ../../reference/image-types.rst:58
msgid "cloudguest.img"
msgstr ""
#: ../../reference/image-types.rst:59
msgid ""
"Image with generic cloud guest virtual machine (VM) requirements "
"installed."
msgstr ""
#: ../../reference/image-types.rst:61
msgid "gce.tar"
msgstr ""
#: ../../reference/image-types.rst:62
msgid "Image with the Google Compute Engine (GCE) specific kernel."
msgstr ""
#: ../../reference/image-types.rst:64
msgid "hyperv.vhdx"
msgstr ""
#: ../../reference/image-types.rst:65
msgid ""
"Virtual Hard Disk for use with Microsoft Hyper-V\\* hypervisor. Includes "
"`optimized kernel`_ for Hyper-V."
msgstr ""
#: ../../reference/image-types.rst:67
msgid "kvm.img"
msgstr ""
#: ../../reference/image-types.rst:68
msgid ""
"Image for booting in a simple VM with start_qemu.sh. Includes `optimized "
"kernel`_ for KVM."
msgstr ""
#: ../../reference/image-types.rst:71
msgid "kvm-legacy.img"
msgstr ""
#: ../../reference/image-types.rst:72
msgid ""
"Image for booting in a simple VM using legacy BIOS, if using "
"start_qemu.sh make sure to remove -bios parameter."
msgstr ""
#: ../../reference/image-types.rst:74
msgid "pxe.tar"
msgstr ""
#: ../../reference/image-types.rst:75
msgid "Image suitable for use with PXE server."
msgstr ""
#: ../../reference/image-types.rst:77
msgid "vmware.vmdk"
msgstr ""
#: ../../reference/image-types.rst:78
msgid ""
"Virtual Machine Disk for VMware\\* platforms inclduing Player, "
"Workstation, and ESXi."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-mac.rst:23
msgid "Verify the integrity of the |CL| image"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-mac.rst:25
msgid ""
"Before you use a downloaded |CL| image, verify its integrity. This action"
" eliminates the small chance of a corrupted image due to download issues."
" To support verification, each released |CL| image has a corresponding "
"SHA512 checksum file designated with the suffix `-SHA512SUMS`."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-mac.rst:30
msgid "Download the corresponding SHA512 checksum file of your |CL| image."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-mac.rst:31
#: ../../guides/maintenance/download-verify-decompress-mac.rst:51
msgid "Start the Terminal app."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-mac.rst:32
msgid "Go to the directory with the downloaded image and checksum files."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-mac.rst:33
msgid ""
"Verify the integrity of the image and compare it to its original checksum"
" with the command:"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-mac.rst:40
msgid ""
"If the checksum of the downloaded image is different than the original "
"checksum, the differences will be displayed. Otherwise, an empty output "
"indicates a match and your downloaded image is good."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-mac.rst:45
msgid "Decompress the |CL| image"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-mac.rst:47
msgid ""
"We compress all released |CL| images by default with either GNU zip "
"(`.gz`) or xz (`.xz`). The compression type we use depends on the target "
"platform or environment. To decompress the image, follow these steps:"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-mac.rst:52
msgid "Go to the directory with the downloaded image."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-mac.rst:53
msgid ""
"Use the :command:`gunzip` command to decompress either compression type. "
"For example:"
msgstr ""
locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-windows.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-windows.po
-277
View File
@@ -1,277 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-12 12:18-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/maintenance/download-verify-decompress-windows.rst:4
msgid "Download, verify, and decompress a |CL-ATTR| image on Windows\\*"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-windows.rst:6
msgid ""
"This guide describes the types of |CL-ATTR| images available, where to "
"download them, how to verify the integrity of an image, and how to "
"decompress it."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-windows.rst:9
msgid "Instructions for other operating systems are available:"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-windows.rst:11
msgid ":ref:`download-verify-decompress-linux`"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-windows.rst:12
msgid ":ref:`download-verify-decompress-mac`"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-windows.rst:15
msgid "Image types"
msgstr ""
#: ../../reference/image-types.rst:3
msgid ""
"|CL-ATTR| offers many types of `images`_ for different platforms and "
"environments."
msgstr ""
#: ../../reference/image-types.rst:7
msgid "The naming convention of a |CL| image filename is:"
msgstr ""
#: ../../reference/image-types.rst:13
msgid "The *[version number]* field specifies the version number."
msgstr ""
#: ../../reference/image-types.rst:15
msgid ""
"The *[image type]* field specifies the type of image and its "
"corresponding file format."
msgstr ""
#: ../../reference/image-types.rst:18
msgid ""
"The *[compression type]* field specifies the compression type. Two types "
"of compressions are used: GNU\\* zip (*.gz*) and XZ (*.xz*)."
msgstr ""
#: ../../reference/image-types.rst:23
msgid ""
"Table 1 lists the currently available images that are platform "
"independent. Table 2 lists the currently available images that are "
"platform specific."
msgstr ""
#: ../../reference/image-types.rst:26
msgid "Table 1: Types of platform-independent |CL| images"
msgstr ""
#: ../../reference/image-types.rst:30 ../../reference/image-types.rst:43
msgid "Image Type"
msgstr ""
#: ../../reference/image-types.rst:31 ../../reference/image-types.rst:44
msgid "Description"
msgstr ""
#: ../../reference/image-types.rst:33
msgid "live-desktop.img or live-desktop.iso"
msgstr ""
#: ../../reference/image-types.rst:34
msgid "Image for booting to GNOME\\* desktop to preview or install the OS."
msgstr ""
#: ../../reference/image-types.rst:36
msgid "live-server.img or live-server.iso"
msgstr ""
#: ../../reference/image-types.rst:37
msgid "Image for booting to server command prompt to preview or install the OS."
msgstr ""
#: ../../reference/image-types.rst:39
msgid "Table 2: Types of platform-specific |CL| images"
msgstr ""
#: ../../reference/image-types.rst:46
msgid "aws.img"
msgstr ""
#: ../../reference/image-types.rst:47
msgid "Image suitable for use with Amazon\\* AWS\\*."
msgstr ""
#: ../../reference/image-types.rst:49
msgid "azure.vhd"
msgstr ""
#: ../../reference/image-types.rst:50
msgid "Virtual Hard Disk for use on Microsoft\\* Azure\\* cloud platform."
msgstr ""
#: ../../reference/image-types.rst:52
msgid "azure-docker.vhd"
msgstr ""
#: ../../reference/image-types.rst:53
msgid ""
"Virtual Hard Disk for use on Microsoft Azure cloud platform with "
"Docker\\* pre-installed."
msgstr ""
#: ../../reference/image-types.rst:55
msgid "azure-machine-learning.vhd"
msgstr ""
#: ../../reference/image-types.rst:56
msgid ""
"Virtual Hard Disk for use on Microsoft Azure cloud platform with the "
"`machine-learning-basic` bundle installed."
msgstr ""
#: ../../reference/image-types.rst:58
msgid "cloudguest.img"
msgstr ""
#: ../../reference/image-types.rst:59
msgid ""
"Image with generic cloud guest virtual machine (VM) requirements "
"installed."
msgstr ""
#: ../../reference/image-types.rst:61
msgid "gce.tar"
msgstr ""
#: ../../reference/image-types.rst:62
msgid "Image with the Google Compute Engine (GCE) specific kernel."
msgstr ""
#: ../../reference/image-types.rst:64
msgid "hyperv.vhdx"
msgstr ""
#: ../../reference/image-types.rst:65
msgid ""
"Virtual Hard Disk for use with Microsoft Hyper-V\\* hypervisor. Includes "
"`optimized kernel`_ for Hyper-V."
msgstr ""
#: ../../reference/image-types.rst:67
msgid "kvm.img"
msgstr ""
#: ../../reference/image-types.rst:68
msgid ""
"Image for booting in a simple VM with start_qemu.sh. Includes `optimized "
"kernel`_ for KVM."
msgstr ""
#: ../../reference/image-types.rst:71
msgid "kvm-legacy.img"
msgstr ""
#: ../../reference/image-types.rst:72
msgid ""
"Image for booting in a simple VM using legacy BIOS, if using "
"start_qemu.sh make sure to remove -bios parameter."
msgstr ""
#: ../../reference/image-types.rst:74
msgid "pxe.tar"
msgstr ""
#: ../../reference/image-types.rst:75
msgid "Image suitable for use with PXE server."
msgstr ""
#: ../../reference/image-types.rst:77
msgid "vmware.vmdk"
msgstr ""
#: ../../reference/image-types.rst:78
msgid ""
"Virtual Machine Disk for VMware\\* platforms inclduing Player, "
"Workstation, and ESXi."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-windows.rst:23
msgid "Verify the integrity of the |CL| image"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-windows.rst:25
msgid ""
"Before you use a downloaded |CL| image, verify its integrity. This action"
" eliminates the small chance of a corrupted image due to download issues."
" To support verification, each released |CL| image has a corresponding "
"SHA512 checksum file designated with the suffix `-SHA512SUMS`."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-windows.rst:30
msgid "Download the corresponding SHA512 checksum file of your |CL| image."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-windows.rst:31
msgid "Start Command Prompt."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-windows.rst:32
msgid "Go to the directory with the downloaded image and checksum files."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-windows.rst:33
msgid "Get the SHA512 checksum of the image with the command:"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-windows.rst:39
msgid ""
"Manually compare the output with the original checksum value shown in the"
" downloaded checksum file and make sure they match."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-windows.rst:43
msgid "Decompress the |CL| image"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-windows.rst:45
msgid ""
"Released |CL| images are compressed with either GNU zip (*.gz*) or XZ "
"(*.xz*). The compression type depends on the target platform or "
"environment. To decompress the image, follow these steps:"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-windows.rst:49
msgid "Download and install `7-Zip`_."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-windows.rst:50
msgid "Go to the directory with the downloaded image and right-click it."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-windows.rst:51
msgid ""
"From the pop-up menu, select :guilabel:`7-Zip` and select "
":guilabel:`Extract Here` as shown in Figure 1."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress-windows.rst:58
msgid "Figure 1: Windows 7-Zip extract file."
msgstr ""
locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress.po
-349
View File
@@ -1,349 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/maintenance/download-verify-decompress.rst:4
msgid "Download, verify, and decompress a |CL-ATTR| image"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:6
msgid ""
"This guide describes the available types of |CL| images, where to "
"download them, how to verify their integrity, and how to decompress them."
" Follow the steps for your OS."
msgstr ""
#: ../../reference/image-types.rst:3
msgid ""
"|CL-ATTR| offers many types of `images`_ for different platforms and "
"environments."
msgstr ""
#: ../../reference/image-types.rst:7
msgid "The naming convention of a |CL| image filename is:"
msgstr ""
#: ../../reference/image-types.rst:13
msgid "The *[version number]* field specifies the version number."
msgstr ""
#: ../../reference/image-types.rst:15
msgid ""
"The *[image type]* field specifies the type of image and its "
"corresponding file format."
msgstr ""
#: ../../reference/image-types.rst:18
msgid ""
"The *[compression type]* field specifies the compression type. Two types "
"of compressions are used: GNU\\* zip (*.gz*) and XZ (*.xz*)."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:22
msgid "Linux OS steps"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:27
#: ../../guides/maintenance/download-verify-decompress.rst:86
#: ../../guides/maintenance/download-verify-decompress.rst:131
msgid "Verify the integrity of the |CL| image"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:29
#: ../../guides/maintenance/download-verify-decompress.rst:88
#: ../../guides/maintenance/download-verify-decompress.rst:133
msgid ""
"Before you use a downloaded |CL| image, verify its integrity. This action"
" eliminates the small chance of a corrupted image due to download issues."
" To support verification, each released |CL| image has a corresponding "
"SHA512 checksum file designated with the suffix `-SHA512SUMS`."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:34
#: ../../guides/maintenance/download-verify-decompress.rst:93
#: ../../guides/maintenance/download-verify-decompress.rst:138
msgid "Download the corresponding SHA512 checksum file of your |CL| `image`_."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:35
#: ../../guides/maintenance/download-verify-decompress.rst:61
#: ../../guides/maintenance/download-verify-decompress.rst:94
#: ../../guides/maintenance/download-verify-decompress.rst:114
msgid "Open a Terminal."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:36
#: ../../guides/maintenance/download-verify-decompress.rst:95
#: ../../guides/maintenance/download-verify-decompress.rst:140
msgid "Go to the directory with the downloaded image and checksum files."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:37
#: ../../guides/maintenance/download-verify-decompress.rst:96
msgid ""
"Verify the integrity of the image and compare it to its original checksum"
" with the command:"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:44
msgid ""
"If the checksum of the downloaded image is different than the original "
"checksum, a warning is displayed with a message indicating the computed "
"checksum does **not** match. Otherwise, the name of the image is printed "
"on the screen followed by `OK`."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:49
msgid ""
"For a more in-depth discussion of image verification including checking "
"the certificate see :ref:`image-content-validation`."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:55
#: ../../guides/maintenance/download-verify-decompress.rst:108
#: ../../guides/maintenance/download-verify-decompress.rst:151
msgid "Decompress the |CL| image"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:57
#: ../../guides/maintenance/download-verify-decompress.rst:153
msgid ""
"Released |CL| images are compressed with either GNU zip (*.gz*) or XZ "
"(*.xz*). The compression type depends on the target platform or "
"environment. To decompress the image, follow these steps:"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:62
#: ../../guides/maintenance/download-verify-decompress.rst:115
msgid "Go to the directory with the downloaded image."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:64
msgid "To decompress an XZ image, enter:"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:70
msgid "To decompress a GZ image, enter:"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:81
msgid "macOS\\* steps"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:103
msgid ""
"If the checksum of the downloaded image is different than the original "
"checksum, the differences will be displayed. Otherwise, an empty output "
"indicates a match and your downloaded image is good."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:110
msgid ""
"We compress all released |CL| images by default with either GNU zip "
"(`.gz`) or xz (`.xz`). The compression type we use depends on the target "
"platform or environment. To decompress the image, follow these steps:"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:116
msgid ""
"Use the :command:`gunzip` command to decompress either compression type. "
"For example:"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:126
msgid "Windows\\* OS steps"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:139
msgid "Start Command Prompt."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:141
msgid "Get the SHA512 checksum of the image with the command:"
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:147
msgid ""
"Manually compare the output with the original checksum value shown in the"
" downloaded checksum file and make sure they match."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:157
msgid "Download and install `7-Zip`_."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:158
msgid "Go to the directory with the downloaded image and right-click it."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:159
msgid ""
"From the pop-up menu, select :guilabel:`7-Zip` and select "
":guilabel:`Extract Here` as shown in Figure 1."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:166
msgid "Figure 1: Windows 7-Zip extract file."
msgstr ""
#: ../../guides/maintenance/download-verify-decompress.rst:171
msgid "Image types"
msgstr ""
#: ../../reference/image-types.rst:3
msgid ""
"Table 1 lists the currently available images that are platform "
"independent. Table 2 lists the currently available images that are "
"platform specific."
msgstr ""
#: ../../reference/image-types.rst:6
msgid "Table 1: Types of platform-independent |CL| images"
msgstr ""
#: ../../reference/image-types.rst:10 ../../reference/image-types.rst:23
msgid "Image Type"
msgstr ""
#: ../../reference/image-types.rst:11 ../../reference/image-types.rst:24
msgid "Description"
msgstr ""
#: ../../reference/image-types.rst:13
msgid "live-desktop.img or live-desktop.iso"
msgstr ""
#: ../../reference/image-types.rst:14
msgid "Image for booting to GNOME\\* desktop to preview or install the OS."
msgstr ""
#: ../../reference/image-types.rst:16
msgid "live-server.img or live-server.iso"
msgstr ""
#: ../../reference/image-types.rst:17
msgid "Image for booting to server command prompt to preview or install the OS."
msgstr ""
#: ../../reference/image-types.rst:19
msgid "Table 2: Types of platform-specific |CL| images"
msgstr ""
#: ../../reference/image-types.rst:26
msgid "aws.img"
msgstr ""
#: ../../reference/image-types.rst:27
msgid "Image suitable for use with Amazon\\* AWS\\*."
msgstr ""
#: ../../reference/image-types.rst:29
msgid "azure.vhd"
msgstr ""
#: ../../reference/image-types.rst:30
msgid "Virtual Hard Disk for use on Microsoft\\* Azure\\* cloud platform."
msgstr ""
#: ../../reference/image-types.rst:32
msgid "azure-docker.vhd"
msgstr ""
#: ../../reference/image-types.rst:33
msgid ""
"Virtual Hard Disk for use on Microsoft Azure cloud platform with "
"Docker\\* pre-installed."
msgstr ""
#: ../../reference/image-types.rst:35
msgid "azure-machine-learning.vhd"
msgstr ""
#: ../../reference/image-types.rst:36
msgid ""
"Virtual Hard Disk for use on Microsoft Azure cloud platform with the "
"`machine-learning-basic` bundle installed."
msgstr ""
#: ../../reference/image-types.rst:38
msgid "cloudguest.img"
msgstr ""
#: ../../reference/image-types.rst:39
msgid ""
"Image with generic cloud guest virtual machine (VM) requirements "
"installed."
msgstr ""
#: ../../reference/image-types.rst:41
msgid "gce.tar"
msgstr ""
#: ../../reference/image-types.rst:42
msgid "Image with the Google Compute Engine (GCE) specific kernel."
msgstr ""
#: ../../reference/image-types.rst:44
msgid "hyperv.vhdx"
msgstr ""
#: ../../reference/image-types.rst:45
msgid ""
"Virtual Hard Disk for use with Microsoft Hyper-V\\* hypervisor. Includes "
"`optimized kernel`_ for Hyper-V."
msgstr ""
#: ../../reference/image-types.rst:47
msgid "kvm.img"
msgstr ""
#: ../../reference/image-types.rst:48
msgid ""
"Image for booting in a simple VM with start_qemu.sh. Includes `optimized "
"kernel`_ for KVM."
msgstr ""
#: ../../reference/image-types.rst:51
msgid "kvm-legacy.img"
msgstr ""
#: ../../reference/image-types.rst:52
msgid ""
"Image for booting in a simple VM using legacy BIOS, if using "
"start_qemu.sh make sure to remove -bios parameter."
msgstr ""
#: ../../reference/image-types.rst:54
msgid "pxe.tar"
msgstr ""
#: ../../reference/image-types.rst:55
msgid "Image suitable for use with PXE server."
msgstr ""
#: ../../reference/image-types.rst:57
msgid "vmware.vmdk"
msgstr ""
#: ../../reference/image-types.rst:58
msgid ""
"Virtual Machine Disk for VMware\\* platforms inclduing Player, "
"Workstation, and ESXi."
msgstr ""
locale/de/LC_MESSAGES/guides/maintenance/enable-user-space.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/maintenance/enable-user-space.po
-223
View File
@@ -1,223 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/maintenance/enable-user-space.rst:4
msgid "Create and enable a new user space"
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:6
msgid ""
"This guide provides steps to complete the following basic setup tasks for"
" a newly installed |CL-ATTR| system:"
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:14
msgid "Create a new user"
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:16
msgid ""
"To create a new user and set a password for that user, enter the "
"following commands as a root user:"
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:24
msgid ""
"Replace the <userid> with the name of the user account you want to create"
" including the password for that user. The :command:`passwd` command "
"prompts you to enter a new password. Retype the new password for the new "
"user account just created."
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:30
msgid "Add the new user to the *wheel* group"
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:32
msgid ""
"Before logging off as root and logging into your new user account, enable"
" the :command:`sudo` command for your new <userid>."
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:35
msgid ""
"To be able to execute all applications with root privileges, add the "
"<userid> to the `wheel group`_."
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:38
msgid "Add <userid> to the wheel group:"
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:44
msgid "Log out of root and into the new <userid>."
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:46
msgid "To log off as root, enter :command:`exit`."
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:48
msgid "Enter the new <userid> and the password created earlier."
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:50
msgid "You will now be in the home directory of <userid>."
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:53
msgid "Install and update the OS software to its current version"
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:55
msgid ""
"The |CL| software utility :ref:`swupd <swupd-guide>` allows you to "
"perform system updates while reaping the benefits of upstream "
"development."
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:58
msgid "To update your newly installed OS, run:"
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:65
msgid "Add a bundle"
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:67
msgid ""
"Software applications are installed as bundles using the command "
":command:`swupd bundle-add`. Experienced Linux users might compare swupd "
"to running :command:`apt-get` or :command:`yum install` for package "
"management. However |CL| manages packages at the level of bundles, which "
"are integrated stacks of packages."
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:73
msgid ""
"For example, the :command:`sysadmin-basic` bundle installs the majority "
"of applications useful to a system administrator. To install it, enter:"
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:80
msgid ""
"View a full list of bundles and packages installed with the `sysadmin-"
"basic`_ bundle. You can also view all `bundles`_ for |CL|, active or "
"deprecated."
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:83
msgid ""
"Expand your knowledge of :command:`swupd` and check out our developer "
"resources:"
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:85
msgid ":ref:`swupd-guide`"
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:86
msgid ":ref:`developer-workstation`"
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:89
msgid "Next steps"
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:91
msgid "Check out our guides and tutorials."
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:93
msgid ":ref:`guides`"
msgstr ""
#: ../../guides/maintenance/enable-user-space.rst:94
msgid ":ref:`tutorials`"
msgstr ""
#~ msgid ""
#~ "View a full list of bundles and"
#~ " packages installed with the `sysadmin-"
#~ "basic`_ bundle. You can also view "
#~ "`all bundles`_ for |CL|, active or "
#~ "deprecated."
#~ msgstr ""
#~ msgid ""
#~ "This section provides steps to complete"
#~ " the following basic setup tasks for"
#~ " a newly installed |CL-ATTR| system:"
#~ msgstr ""
#~ msgid ""
#~ "To create a new user and set "
#~ "a password for that user, enter "
#~ "the following commands as a `root` "
#~ "user:"
#~ msgstr ""
#~ msgid "Add the new user to the `wheel` group"
#~ msgstr ""
#~ msgid ""
#~ "Before logging off as root and "
#~ "logging into your new user account, "
#~ "enable the :command:`sudo` command for "
#~ "your new `<userid>`."
#~ msgstr ""
#~ msgid ""
#~ "To be able to execute all "
#~ "applications with root privileges, add "
#~ "the `<userid>` to the `wheel group`_."
#~ msgstr ""
#~ msgid "Add `<userid>` to the `wheel` group:"
#~ msgstr ""
#~ msgid "Log out of root and into the new `<userid>`."
#~ msgstr ""
#~ msgid "Enter the new `<userid>` and the password created earlier."
#~ msgstr ""
#~ msgid "You will now be in the home directory of `<userid>`."
#~ msgstr ""
#~ msgid ""
#~ "Software applications are installed as "
#~ "bundles using the command :command:`swupd "
#~ "bundle-add`. Experienced Linux* users "
#~ "might compare `swupd` to running "
#~ ":command:`apt-get` or :command:`yum install`"
#~ " for package management. Yet |CL| "
#~ "manages packages at the level of "
#~ "bundles, which are integrated stacks of"
#~ " packages."
#~ msgstr ""
#~ msgid ""
#~ "For example, the `sysadmin-basic` bundle"
#~ " installs the majority of applications "
#~ "useful to a system administrator. To "
#~ "install it, enter:"
#~ msgstr ""
locale/de/LC_MESSAGES/guides/maintenance/fix-broken-install.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/maintenance/fix-broken-install.po
-205
View File
@@ -1,205 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/maintenance/fix-broken-install.rst:4
msgid "Fix a broken installation"
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:6
msgid ""
"This guide explains how to fix a broken installation of |CL-ATTR| using a"
" live desktop image on a USB."
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:14
msgid "Overview"
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:16
msgid ""
"This guide assumes you have installed |CL| on a target system, but the OS"
" does not boot or function properly."
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:19
msgid ""
"The process described in this guide can only verify and fix files that "
":ref:`swupd<swupd-guide>` owns in :file:`/usr`. Files outside of this "
"path, such as :file:`/home/`, :file:`/etc`, :file:`/var`, etc., cannot be"
" repaired by this process."
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:25
msgid "Prerequisites"
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:27
msgid ""
"Download and install the live desktop image on a USB. See :ref:`bare-"
"metal-install-desktop` for install instructions."
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:31
msgid "Boot a live desktop image to fix target system"
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:33
msgid "Boot the |CL| live desktop image."
msgstr ""
#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:4
msgid "Install from live image"
msgstr ""
#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:6
msgid ""
"After you download and burn the live desktop image on a USB drive, follow"
" these steps."
msgstr ""
#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:9
msgid "Insert the USB drive into an available USB slot."
msgstr ""
#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:11
msgid "Power on the system."
msgstr ""
#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:13
msgid ""
"Open the system BIOS setup menu by pressing the :kbd:`F2` key. Your BIOS "
"setup menu entry point may vary."
msgstr ""
#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:16
msgid ""
"In the setup menu, enable the UEFI boot and set the USB drive as the "
"first option in the device boot order."
msgstr ""
#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:19
msgid "Save these settings, e.g. :kbd:`F10`, and exit."
msgstr ""
#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:21
msgid "Reboot the target system."
msgstr ""
#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:23
msgid "Select :guilabel:`Clear Linux OS` in the boot menu, shown in Figure 1."
msgstr ""
#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:29
msgid "Figure 1: Clear Linux OS in boot menu"
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:40
msgid "Mount root partition, verify, and fix"
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:42
msgid "Open a Terminal window."
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:44
msgid "Ensure the system is connected to the network."
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:46
msgid "Mount the system’s root partition."
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:48
msgid "To find the root partition, run:"
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:54
msgid "We'll use :file:`/dev/sda3/` as the root partition example."
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:56
msgid "Next, mount the partition to the :file:`/mnt` folder."
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:62
msgid ""
"Verify that you mounted the correct root partition by checking for some "
"files commonly found on |CL| systems."
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:70
msgid "Next, run swupd to fix any issues on the target system."
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:76
msgid ":ref:`Learn more about how swupd works <swupd-guide>`."
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:78
msgid "After the process is complete, unmount the root partition:"
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:84
msgid ""
"Reboot the system, remove the live desktop USB drive, and boot into the "
"repaired system."
msgstr ""
#: ../../guides/maintenance/fix-broken-install.rst:91
msgid "**Congratulations!** You successfully restored |CL|."
msgstr ""
#~ msgid "Fix a broken installation of |CL-ATTR|"
#~ msgstr ""
#~ msgid ""
#~ "This guide explains how to fix a"
#~ " broken installation of |CL| using a"
#~ " live desktop image on a USB. "
#~ "It's assumed you already installed |CL|"
#~ " on a target system, but your "
#~ "operating system does not boot or "
#~ "function properly."
#~ msgstr ""
#~ msgid ""
#~ "This process can only verify and "
#~ "fix files that :ref:`swupd<swupd-guide>` "
#~ "owns in :file:`/usr`. Files outside of"
#~ " this path, such as /home/, /etc, "
#~ "/var, etc., cannot be repaired by "
#~ "this process."
#~ msgstr ""
#~ msgid ""
#~ ":ref:`Download and install the live "
#~ "desktop image on a USB <bare-"
#~ "metal-install-desktop>`"
#~ msgstr ""
#~ msgid "Assure the system is connected to the network."
#~ msgstr ""
#~ msgid "We'll use `/dev/sda3/` as the root partition example."
#~ msgstr ""
#~ msgid "Next, mount the partition to the `/mnt` folder."
#~ msgstr ""
locale/de/LC_MESSAGES/guides/maintenance/hostname.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/maintenance/hostname.po
-126
View File
@@ -1,126 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/maintenance/hostname.rst:4
msgid "Modify hostname"
msgstr ""
#: ../../guides/maintenance/hostname.rst:6
msgid ""
"This guide describes how to modify and view the hostname of your |CL-"
"ATTR| system."
msgstr ""
#: ../../guides/maintenance/hostname.rst:14
msgid "Overview"
msgstr ""
#: ../../guides/maintenance/hostname.rst:16
msgid ""
"By default, |CL| installations have a machine generated name, which is a "
"long string of letters and numbers. The generated name is fine for "
"computers but is not human-friendly. Administrators and users will often "
"want to rename their machines with a name that is easier to remember, "
"type, and search for. Renaming a machine also makes it easier to "
"identify, by including meaningful data in the name. The following "
"examples show human-friendly machine names:"
msgstr ""
#: ../../guides/maintenance/hostname.rst:24
msgid "*regression-test*"
msgstr ""
#: ../../guides/maintenance/hostname.rst:25
msgid "*sally-test-box1*"
msgstr ""
#: ../../guides/maintenance/hostname.rst:26
msgid "*az-bldg2-lab*"
msgstr ""
#: ../../guides/maintenance/hostname.rst:29
msgid "Set your hostname"
msgstr ""
#: ../../guides/maintenance/hostname.rst:31
msgid ""
"|CL| uses the :command:`hostnamectl` command to display and modify the "
"machine name. :command:`hostnamectl` is part of the :command:`os-core` "
"bundle, which provides a basic Linux\\* user space and utilities."
msgstr ""
#: ../../guides/maintenance/hostname.rst:35
msgid ""
"This example sets the hostname to *telemetry-test-2-h15*, to identify a "
"|CL| telemetry test machine on the second floor at grid location H15. "
"Make sure to reboot after setting a new hostname."
msgstr ""
#: ../../guides/maintenance/hostname.rst:46
msgid ""
"There are three types of hostname: *static*, *transient*, and *pretty*. "
"The most common is the static hostname. Static hostnames must be between "
"two and 63 characters long, must start and end with a letter or number, "
"and may contain letters (case-insensitive), numbers, dashes, or dots."
msgstr ""
#: ../../guides/maintenance/hostname.rst:51
msgid ""
"If the static hostname exists, it is used to generate the transient "
"hostname, which is maintained by the kernel. The transient hostname can "
"be changed by DHCP or mDNS at runtime."
msgstr ""
#: ../../guides/maintenance/hostname.rst:55
msgid ""
"The pretty hostname is a free-form UTF8 name used for presentation to the"
" user."
msgstr ""
#: ../../guides/maintenance/hostname.rst:58
msgid "View your hostname"
msgstr ""
#: ../../guides/maintenance/hostname.rst:60
msgid "View your current hostname using the following command:"
msgstr ""
#: ../../guides/maintenance/hostname.rst:66
msgid "You should see output similar to:"
msgstr ""
#: ../../guides/maintenance/hostname.rst:81
msgid ""
"**Congratulations!** You successfully modified the hostname of your |CL| "
"system."
msgstr ""
#~ msgid "Modify hostname on |CL-ATTR|"
#~ msgstr ""
#~ msgid ""
#~ "|CL| uses the :command:`hostnamectl` command"
#~ " to display and modify the machine"
#~ " name. :command:`hostnamectl` is part of"
#~ " the **os-core** bundle, which "
#~ "provides a basic Linux\\* user space "
#~ "and utilities."
#~ msgstr ""
locale/de/LC_MESSAGES/guides/maintenance/increase-virtual-disk-size.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/maintenance/increase-virtual-disk-size.po
-317
View File
@@ -1,317 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/maintenance/increase-virtual-disk-size.rst:4
msgid "Increase virtual disk size of an image"
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:6
msgid ""
"This guide describes how to increase the disk size of your prebuilt |CL-"
"ATTR| image if you need more capacity."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:14
msgid "Determine the partition order and sizes of the prebuilt image"
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:16
msgid ""
"|CL| prebuilt images come in different sizes, ranging from 300 MB to 20 "
"GB."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:19
msgid ""
"There are two methods to find the order and sizes of partitions virtual "
"disk of your prebuilt |CL| image."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:22
msgid ""
"In both examples, the prebuilt Hyper-V image has a disk size of 8.5 GB "
"with :file:`/dev/sda3` being the partition for the root filesystem (/)"
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:26
msgid "Checking :command:`lsblk` on the VM"
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:28
msgid ""
"The first method is to boot up your :abbr:`VM (Virtual Machine)` and "
"execute the :command:`lsblk` command as shown below:"
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:35
msgid "An example output of the :command:`lsblk` command:"
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:45
msgid "An example of this can also be seen in Figure 1."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:48
msgid "Checking :file:`config.json` used to build the image"
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:50
msgid ""
"The second method to determine partition to check the :file:`config.json`"
" file used to create prebuilt image, located in the `releases`_ "
"repository. For example, to find the size of the Hyper-V\\* image version"
" number 20450, follow these steps:"
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:55
msgid "Go to the `releases`_ repository."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:56
msgid "Drill down into the `20450 > clear > config > image` directory."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:57
msgid "Open the :file:`hyperv-config.json` file."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:58
msgid "Locate the `PartitionLayout` key."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:60
msgid ""
"The example shows 512 MB for the EFI partition, 32 MB for the swap "
"partition, and 8 GB for the root partition."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:80
msgid "Increase virtual disk size"
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:81
msgid ""
"Once you have determined the disk and partition to be increased, you are "
"ready to perform the actual increase of the disk, partition, and "
"filesystem."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:85
msgid "Power off VM and increase virtual disk size"
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:87
msgid ""
"To increase the virtual disk size for a prebuilt image, perform the steps"
" below:"
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:90
msgid "Shut down your VM if it is running."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:91
msgid ""
"Use the process defined by your hypervisor or cloud provider to increase"
" the virtual disk size of your |CL| VM."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:93
msgid "Power up the VM."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:97
msgid "Resize the partition of the virtual disk"
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:99
msgid "Log in to an account with root privileges."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:100
msgid "Open a terminal emulator."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:101
msgid ""
"Add the :command:`storage-utils` bundle to install the :command:`parted` "
"and :command:`resize2fs` tools."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:108
msgid "Launch the `parted` tool."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:114
msgid "In the `parted` tool, perform these steps:"
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:116
msgid "Press :command:`p` to print the partitions table."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:117
msgid "If the warning message below is displayed, enter :command:`Fix`."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:127
msgid ""
"Enter :command:`resizepart [partition number]` where *[partition number]*"
" is the partition number of the partition to modify."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:129
msgid "Enter :command:`yes` when prompted."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:130
msgid "Enter the new End size."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:134
msgid ""
"If you want a partition to take up the remaining disk space, then enter "
"the total size of the disk. When you print the partitions table with the "
":command:`p` command, the total disk size is shown after the "
":guilabel:`Disk` label."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:139
msgid "An example of this can be seen in Figure 1."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:141
msgid ""
"Enter :command:`q` to exit `parted` when you are finished resizing the "
"image."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:144
msgid ""
"Figure 1 depicts the described steps to resize the partition of the "
"virtual disk from 8.5GB to 20GB."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:150
msgid "Figure 1: Increase root partition size."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:153
msgid "Resize the filesystem"
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:155
msgid ""
"Enter :command:`sudo resize2fs -p /dev/[modified partition name]` where "
"*[modified partition name]* is the partition that was changed in the "
"`parted` tool."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:159
msgid "Run the :command:`df -h` to verify that the filesystem size has increased."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:162
msgid ""
"Figure 2 depicts the described steps to resize the partition of the "
"virtual disk from 8.5GB to 20GB."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:169
msgid "Figure 2: Increase root filesystem size after partition has been expanded."
msgstr ""
#: ../../guides/maintenance/increase-virtual-disk-size.rst:171
msgid ""
"**Congratulations!** You have resized the disk, partition, and "
"filesystem. At this point, the increase in disk capacity is usable."
msgstr ""
#~ msgid "Increase virtual disk size of a |CL-ATTR| image"
#~ msgstr ""
#~ msgid ""
#~ "|CL-ATTR| prebuilt images come in "
#~ "different sizes, ranging from 300 MB "
#~ "to 20 GB. This guide describes how"
#~ " to increase the size of your "
#~ "prebuilt |CL| image if you need "
#~ "more capacity."
#~ msgstr ""
#~ msgid "This guide will cover:"
#~ msgstr ""
#~ msgid ""
#~ "In both examples, the prebuilt Hyper-V"
#~ " image has a disk size of 8.5"
#~ " GB with / dev/sda3 being the "
#~ "partition for the root filesystem (/)"
#~ msgstr ""
#~ msgid "Power off VM and increase virtual disk size:"
#~ msgstr ""
#~ msgid ""
#~ "Use the process defined by your "
#~ "hypervisor or cloud provider to increase"
#~ " the virtual disk size of your "
#~ "|CL| VM."
#~ msgstr ""
#~ msgid "Resize the partition of the virtual disk:"
#~ msgstr ""
#~ msgid ""
#~ "Add the |CL| `storage-utils` bundle "
#~ "to install the :command:`parted` and "
#~ ":command:`resize2fs` tools."
#~ msgstr ""
#~ msgid "Enter the new `End` size."
#~ msgstr ""
#~ msgid ""
#~ "If you want a partition to take"
#~ " up the remaining disk space, then"
#~ " enter the total size of the "
#~ "disk. When you print the partitions "
#~ "table with the :command:`p` command, the"
#~ " total disk size is shown after "
#~ "the `Disk` label."
#~ msgstr ""
#~ msgid "Resize the filesytem"
#~ msgstr ""
#~ msgid ""
#~ "Enter :command:`sudo resize2fs -p "
#~ "/dev/[modified partition name]` where "
#~ "*[modified partition name]* is the "
#~ "partition that was changed in `parted`."
#~ msgstr ""
#~ msgid ""
#~ "Congratulations! You have resized the "
#~ "disk, partition, and filesystem. At this"
#~ " point, the increase in disk capacity"
#~ " is usable."
#~ msgstr ""
locale/de/LC_MESSAGES/guides/maintenance/query-upstream.po
-168
View File
@@ -1,168 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/maintenance/query-upstream.rst:4
msgid "Query package info from upstream repository"
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:6
msgid ""
"This guide describes how to query package information from the |CL| "
"upstream repositories. This guide is intended for developers and advanced"
" users."
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:15
msgid "Overview"
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:17
msgid ""
"In |CL-ATTR|, the :ref:`swupd<swupd-guide>` tool manages software "
"dependencies and installs bundles instead of packages. Although a bundle "
"is a collection of one or more packages, |CL| does not work with packages"
" on the client side. However, on the upstream/factory side, |CL| does "
"work with packages using a process called *mixing*."
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:23
msgid ""
"Currently, :command:`swupd` does not report which packages are installed,"
" provide package version information, or return other package details. "
"This guide describes a method for retrieving package information from the"
" |CL| upstream repositories using :abbr:`DNF(Dandified Yum)` commands."
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:29
msgid "Prerequisites"
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:31
msgid ""
"This guide assumes you have installed |CL| on your host system. For "
"detailed instructions on installing |CL| on a bare metal system, visit "
"the :ref:`bare metal installation guide <bare-metal-install-desktop>`."
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:35
msgid ""
"Before you install any new packages, update |CL| with the following "
"command:"
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:42
msgid "Configure DNF"
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:44
msgid "Install the DNF bundle with the command:"
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:50
msgid "Create a :file:`dnf.conf` file with the commands:"
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:58
msgid ""
"Edit the :file:`/etc/dnf/dnf.conf` file and set the **baseurl** variable "
"for binary and source RPMs as shown in lines 3 and 9 in the following "
"example."
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:78
msgid "Initialize the RPM database with the command:"
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:86
msgid "DNF command usage examples"
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:93
msgid "List all binary and source RPMs in the current release"
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:95
#: ../../guides/maintenance/query-upstream.rst:129
#: ../../guides/maintenance/query-upstream.rst:150
#: ../../guides/maintenance/query-upstream.rst:173
#: ../../guides/maintenance/query-upstream.rst:196
#: ../../guides/maintenance/query-upstream.rst:215
msgid "Command:"
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:101
#: ../../guides/maintenance/query-upstream.rst:135
#: ../../guides/maintenance/query-upstream.rst:156
#: ../../guides/maintenance/query-upstream.rst:179
#: ../../guides/maintenance/query-upstream.rst:202
#: ../../guides/maintenance/query-upstream.rst:221
msgid "Sample output:"
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:125
msgid "Show version information for a package in current release"
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:127
msgid "This example queries version information for the zstd package."
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:145
msgid "Show version information for a package in a specific release"
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:147
msgid ""
"This example queries version information for the zstd package in release "
"21000."
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:168
msgid ""
"Show only version and release information for a package in a specific "
"release"
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:170
msgid ""
"This example queries version and release information for the zstd package"
" in release 15000."
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:191
msgid "Show the binary package for a specified binary file"
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:193
msgid ""
"This example returns the binary package that contains the "
":file:`/usr/bin/zip` binary file."
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:210
msgid "Show the source package for a specified binary file"
msgstr ""
#: ../../guides/maintenance/query-upstream.rst:212
msgid ""
"This example returns the source package that contains the "
":file:`/usr/bin/zip` binary file."
msgstr ""
locale/de/LC_MESSAGES/guides/maintenance/restart.po
-237
View File
@@ -1,237 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/maintenance/restart.rst:4
msgid "Restart system services after an OS update"
msgstr ""
#: ../../guides/maintenance/restart.rst:6
msgid "This guide describes how to use the :command:`clr-service-restart` tool."
msgstr ""
#: ../../guides/maintenance/restart.rst:13
msgid "Overview"
msgstr ""
#: ../../guides/maintenance/restart.rst:15
msgid ""
"|CL-ATTR| includes a :command:`clr-service-restart` tool that shows which"
" system daemons require a restart."
msgstr ""
#: ../../guides/maintenance/restart.rst:18
msgid ""
":command:`clr-service-restart` reads various files in the :file:`procfs` "
"filesystem provided by the kernel and relies on :command:`systemd` to "
"determine which services to restart."
msgstr ""
#: ../../guides/maintenance/restart.rst:24
msgid "How it works"
msgstr ""
#: ../../guides/maintenance/restart.rst:26
msgid ""
":command:`clr-service-restart` implements a whitelist to identify which "
"daemons can be restarted. As a system administrator, you can customize "
"the default |CL| OS whitelist using :command:`allow` or "
":command:`disallow` options for restarting system services. When a "
"software update occurs, :command:`clr-service-restart` consults the "
"whitelist to see if a service daemon is allowed to be restarted or not."
msgstr ""
#: ../../guides/maintenance/restart.rst:35
msgid "Basic options"
msgstr ""
#: ../../guides/maintenance/restart.rst:37
msgid ""
":command:`clr-service-restart` has three basic options: :command:`allow`,"
" :command:`disallow`, and :command:`default`."
msgstr ""
#: ../../guides/maintenance/restart.rst:41
msgid "allow"
msgstr ""
#: ../../guides/maintenance/restart.rst:43
msgid ""
"The :command:`allow` option identifies a daemon to restart after an OS "
"software update. The :command:`clr-service-restart` daemon creates a "
"symlink in :file:`/etc/clr-service-restart` as a record. The example "
"below tells :command:`clr-service-restart` to restart the *tallow* daemon"
" after an OS software update."
msgstr ""
#: ../../guides/maintenance/restart.rst:54
msgid "disallow"
msgstr ""
#: ../../guides/maintenance/restart.rst:56
msgid ""
"The :command:`disallow` option tells :command:`clr-service-restart` not "
"to restart the specified daemon even if the OS defaults permit the daemon"
" to be restarted. The :command:`clr-service-restart` daemon creates a "
"symlink in :file:`/etc/clr-service-restart` that points to "
":file:`/dev/null` as a record. The example below tells :command:`clr-"
"service-restart` not to restart the *rngd* daemon after an OS software "
"update."
msgstr ""
#: ../../guides/maintenance/restart.rst:68
msgid "default"
msgstr ""
#: ../../guides/maintenance/restart.rst:70
msgid ""
"The :command:`default` option makes :command:`clr-service-restart` revert"
" back to the OS defaults and delete any symlink in :file:`/etc/clr-"
"service-restart`. The example below tells :command:`clr-service-restart`"
" to restart *rngd* automatically again, because *rngd* is whitelisted for"
" automatic service restarts by default in |CL|."
msgstr ""
#: ../../guides/maintenance/restart.rst:81
msgid "Monitor options"
msgstr ""
#: ../../guides/maintenance/restart.rst:83
msgid ""
":command:`clr-service-restart` works in the background and is invoked "
"with :command:`swupd` automatically. Review the journal output to verify "
"that services are restarted after an OS software update."
msgstr ""
#: ../../guides/maintenance/restart.rst:87
msgid ""
"If you pass both options (:command:`-a` and :command:`-n`) described "
"below, :command:`clr-service-restart` displays a complete list of system "
"services that require a restart. Use both options to verify that all "
"desired daemons are restarted."
msgstr ""
#: ../../guides/maintenance/restart.rst:94
msgid "-n option"
msgstr ""
#: ../../guides/maintenance/restart.rst:96
msgid ""
"The :command:`-n` option makes :command:`clr-service-restart` perform no "
"restarts. Instead it displays the services that could potentially be "
"restarted. When used, :command:`clr-service-restart` outputs a list of "
"messages showing:"
msgstr ""
#: ../../guides/maintenance/restart.rst:100
msgid "Which service needs a restart."
msgstr ""
#: ../../guides/maintenance/restart.rst:101
msgid "What unit it is."
msgstr ""
#: ../../guides/maintenance/restart.rst:102
msgid "Why it needs a restart."
msgstr ""
#: ../../guides/maintenance/restart.rst:103
msgid "Which command is required to restart the unit."
msgstr ""
#: ../../guides/maintenance/restart.rst:106
msgid "-a option"
msgstr ""
#: ../../guides/maintenance/restart.rst:108
msgid ""
"The :command:`-a` option makes :command:`clr-service-restart` consider "
"all system services, not only the ones that are whitelisted. Because the "
"default whitelist in |CL| is relatively short, you can use this option to"
" restart all impacted services when you log in on the system."
msgstr ""
#: ../../guides/maintenance/restart.rst:114
msgid "Example"
msgstr ""
#: ../../guides/maintenance/restart.rst:116
msgid ""
"In the example below, :command:`clr-service-restart` is invoked with both"
" the :command:`-a` and :command:`-n` options, which displays a complete "
"list of system services that require a restart."
msgstr ""
#: ../../guides/maintenance/restart.rst:120
msgid "Command:"
msgstr ""
#: ../../guides/maintenance/restart.rst:126
msgid "Sample output:"
msgstr ""
#: ../../guides/maintenance/restart.rst:138
msgid "Telemetry"
msgstr ""
#: ../../guides/maintenance/restart.rst:140
msgid ""
":command:`clr-service-restart` may cause problems such as a short service"
" outage when a daemon is being restarted, or if a daemon fails to "
"properly restart. To minimize issues, :command:`clr-service-restart` "
"creates a telemetry record and sends it to the optional |CL| telemetry "
"service if both conditions below are met:"
msgstr ""
#: ../../guides/maintenance/restart.rst:146
msgid "If a unit fails to automatically restart after an OS update."
msgstr ""
#: ../../guides/maintenance/restart.rst:147
msgid ""
"If that unit resides in the system location "
":file:`/usr/lib/systemd/system`."
msgstr ""
#: ../../guides/maintenance/restart.rst:149
msgid ""
"If you do not install the |CL| telemetrics bundle, the data is discarded."
" If you install the telemetrics bundle and you opt to send telemetry, "
"then the system unit name is sent to the |CL| telemetry service. We "
"evaluate the report and update the whitelist to remove services that are "
"not safe to restart."
msgstr ""
#: ../../guides/maintenance/restart.rst:157
msgid "Conclusion"
msgstr ""
#: ../../guides/maintenance/restart.rst:159
msgid ""
"The |CL| team enjoys coming up with simple and efficient solutions to "
"make your work easier. We made a GitHub\\* project of :command:`clr-"
"service-restart` and we invite you to look at the code, share your "
"thoughts, and work with us on improving the project. You can find the "
"project at:"
msgstr ""
#: ../../guides/maintenance/restart.rst:164
msgid "https://github.com/clearlinux/clr-service-restart"
msgstr ""
locale/de/LC_MESSAGES/guides/maintenance/time.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/maintenance/time.po
-94
View File
@@ -1,94 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/maintenance/time.rst:4
msgid "Set the time"
msgstr ""
#: ../../guides/maintenance/time.rst:6
msgid ""
"This guide describes how to reset the time in your |CL-ATTR| system when "
"the default :abbr:`NTP (Network Time Protocol)` servers cannot be "
"reached."
msgstr ""
#: ../../guides/maintenance/time.rst:9
msgid "|CL| uses the `systemd-timesyncd.service` daemon to synchronize time."
msgstr ""
#: ../../guides/maintenance/time.rst:12
msgid "Install the :command:`sysadmin-basic` bundle."
msgstr ""
#: ../../guides/maintenance/time.rst:18
msgid "Set your time zone. This example uses Los Angeles."
msgstr ""
#: ../../guides/maintenance/time.rst:26
msgid ""
"To see a list of time zones, use the command: :command:`timedatectl list-"
"timezones | grep <locale>`"
msgstr ""
#: ../../guides/maintenance/time.rst:29
msgid "Create a :file:`/etc/systemd/` directory."
msgstr ""
#: ../../guides/maintenance/time.rst:35
msgid ""
"Create a new file named :file:`/etc/systemd/timesyncd.conf` and enter the"
" following text."
msgstr ""
#: ../../guides/maintenance/time.rst:44
msgid "Enable the `systemd-timesyncd` service."
msgstr ""
#: ../../guides/maintenance/time.rst:52
msgid ""
"To check the service status, use the :command:`timedatectl status` "
"command."
msgstr ""
#: ../../guides/maintenance/time.rst:54
msgid ""
"To restart the `timesyncd` daemon, enter :command:`systemctl restart "
"systemd-timesyncd` into your terminal emulator."
msgstr ""
#: ../../guides/maintenance/time.rst:57
msgid "**Congratulations!** You successfully set up the time in your |CL| system."
msgstr ""
#~ msgid ""
#~ "|CL-ATTR| uses the `systemd-"
#~ "timesyncd.service` daemon to synchronize time."
#~ msgstr ""
#~ msgid ""
#~ "This guide describes how to reset "
#~ "the time in your |CL| system when"
#~ " the default :abbr:`NTP (Network Time "
#~ "Protocol)` servers cannot be reached."
#~ msgstr ""
#~ msgid "Install the `sysadmin-basic` bundle."
#~ msgstr ""
locale/de/LC_MESSAGES/guides/maintenance/validate-signatures.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/maintenance/validate-signatures.po
-240
View File
@@ -1,240 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/maintenance/validate-signatures.rst:4
msgid "Validate signatures"
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:7
msgid "This guide describes how to validate the contents of a |CL-ATTR| image."
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:14
msgid "Overview"
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:16
msgid ""
"Validating the contents of an image is a manual process and is the same "
"process that :ref:`swupd-guide` performs internally."
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:19
msgid ""
"|CL| offers a way to validate the content of an image or an update. All "
"validation of content works by creating and signing a hash. A valid "
"signature creates a chain of trust. A broken chain of trust, seen as an "
"invalid signature, means the content is not valid."
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:28
msgid "Image content validation"
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:30
msgid ""
"In the steps below, we used the installer image of the latest release of "
"|CL|. You may use any image of |CL| you choose."
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:33
msgid ""
"Download the image, the signature of the SHA512 sum of the image, and the"
" |CL| certificate used for signing the SHA512 sum."
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:45
msgid "Generate the SHA256 sum of the |CL| certificate."
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:51
msgid ""
"Ensure the generated SHA256 sum of the |CL| certificate matches the "
"following SHA256 sum to verify the integrity of the certificate."
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:58
msgid "Generate the SHA512 sum of the image and save it to a file."
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:64
msgid ""
"Ensure the signature of the SHA512 sum of the image was created using the"
" |CL| certificate. This confirms that the image is trusted and has not "
"been modified."
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:74
#: ../../guides/maintenance/validate-signatures.rst:125
msgid ""
"The :command:`-purpose any` option is required when using OpenSSL 1.1. If"
" you use an earlier version of OpenSSL, omit this option to perform "
"signature validation. The :command:`openssl version` command may be used"
" to determine the version of OpenSSL in use."
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:79
msgid ""
"The output should contain \"Verification successful\". If the output "
"contains \"bad_signature\" anywhere, then the image is not trustworthy."
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:83
msgid "Update content validation"
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:85
msgid ""
"**swupd** validates all update content automatically before applying the "
"update content. The process swupd follows internally is illustrated here "
"with manual steps using the latest |CL| release. There is no need to "
"perform these steps manually when performing a :command:`swupd update`."
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:90
msgid ""
"Download the :abbr:`MoM (top-level manifest)`, the signature of the MoM, "
"and the Swupd certificate used for signing the signature of the MoM."
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:102
msgid "Generate the SHA256 sum of the swupd certificate."
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:108
msgid ""
"Confirm that the generated SHA256 sum of the swupd certificate matches "
"the SHA256 sum shown below to verify the integrity of the certificate."
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:115
msgid ""
"Confirm that the signature of the MoM was created using the Swupd "
"certificate. This signature validates the update content is trustworthy "
"and has not been modified."
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:132
msgid ""
"The SHA512 sum of the MoM is not generated and then signed. Instead, the "
"MoM is signed directly because it is small in size compared to an image "
"of |CL|."
msgstr ""
#: ../../guides/maintenance/validate-signatures.rst:136
msgid ""
"The output should contain \"Verification successful\". If the output "
"contains \"bad_signature\" anywhere, then the MoM cannot be trusted. "
"Because the MoM contains a list of hashes for bundle manifests, if the "
"MoM cannot be trusted, then the bundle content cannot be trusted."
msgstr ""
#~ msgid ""
#~ "|CL-ATTR| offers a way to validate"
#~ " the content of an image or an"
#~ " update. All validation of content "
#~ "works by creating and signing a "
#~ "hash. A valid signature creates a "
#~ "chain of trust. A broken chain of"
#~ " trust, seen as an invalid signature,"
#~ " means the content is not valid."
#~ msgstr ""
#~ msgid ""
#~ "This guide covers how to validate "
#~ "the contents of an image, which is"
#~ " a manual process and is the "
#~ "same process ``swupd`` performs internally "
#~ "to validate an update."
#~ msgstr ""
#~ msgid ""
#~ "For the outlined steps, the installer"
#~ " image of the latest release of "
#~ "|CL| is used for illustrative purposes."
#~ " You may use any image of |CL|"
#~ " you choose."
#~ msgstr ""
#~ msgid ""
#~ "Ensure the signature of the SHA512 "
#~ "sum of the image was created using"
#~ " the |CL| certificate. This validates "
#~ "the image is trusted and it has"
#~ " not been modified."
#~ msgstr ""
#~ msgid ""
#~ "The `-purpose any` option is required"
#~ " when using OpenSSL 1.1. If using"
#~ " an earlier version of OpenSSL, omit"
#~ " this option to perform signature "
#~ "validation. The `openssl version` command "
#~ "may be used to determine the "
#~ "version of OpenSSL in use."
#~ msgstr ""
#~ msgid ""
#~ "The output should contain ``Verification "
#~ "successful``. If the output contains "
#~ "``bad_signature`` anywhere, then the image "
#~ "is not trustworthy."
#~ msgstr ""
#~ msgid ""
#~ "``swupd`` validates all update content "
#~ "automatically before applying the update "
#~ "content. The process ``swupd`` follows "
#~ "internally is illustrated here with "
#~ "manual steps using the latest |CL| "
#~ "release. There is no need to "
#~ "perform these steps manually when "
#~ "performing a ``swupd update``."
#~ msgstr ""
#~ msgid "Generate the SHA256 sum of the Swupd certificate."
#~ msgstr ""
#~ msgid ""
#~ "Ensure the generated SHA256 sum of "
#~ "the Swupd certificate matches following "
#~ "SHA256 sum to verify the integrity "
#~ "of the certificate."
#~ msgstr ""
#~ msgid ""
#~ "Ensure the signature of the MoM "
#~ "was created using the Swupd certificate."
#~ " This signature validates the update "
#~ "content is trustworthy and has not "
#~ "been modified."
#~ msgstr ""
#~ msgid ""
#~ "The output should contain ``Verification "
#~ "successful``. If the output contains "
#~ "``bad_signature`` anywhere, then the MoM "
#~ "cannot be trusted. Because the MoM "
#~ "contains a list of hashes for "
#~ "bundle manifests, if the MoM cannot "
#~ "be trusted, then the bundle content "
#~ "cannot be trusted."
#~ msgstr ""
locale/de/LC_MESSAGES/guides/network/custom-clear-container.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/network/custom-clear-container.po
-216
View File
@@ -1,216 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/network/custom-clear-container.rst:4
msgid "Build a custom |CL-ATTR| based Docker container image"
msgstr ""
#: ../../guides/network/custom-clear-container.rst:6
msgid ""
"This guide contains the steps to build a custom container image. The "
"official base |CL-ATTR| container image is published on Docker\\* Hub and"
" is updated on a regular basis."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:15
msgid "Prerequisites"
msgstr ""
#: ../../guides/network/custom-clear-container.rst:17
msgid ""
"You must perform these steps on a |CL| system because the :abbr:`swupd "
"(software updater)` is used to manage bundles in the container."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:20
msgid ""
"You must install the :file:`containers-basic` bundle on the |CL| system "
"or Docker will not work."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:22
msgid "You have a basic understanding of Docker."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:25
msgid "Build the base container image"
msgstr ""
#: ../../guides/network/custom-clear-container.rst:27
msgid "Log in and get root privileges."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:33
msgid "Verify Docker is installed and running."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:39
msgid "If Docker is installed and running, the output is similar to this example:"
msgstr ""
#: ../../guides/network/custom-clear-container.rst:82
msgid "If Docker is not installed, enter the commands:"
msgstr ""
#: ../../guides/network/custom-clear-container.rst:89
msgid "Use :command:`os-install` to download and install the bundles."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:96
msgid "The swupd example uses the following flags:"
msgstr ""
#: ../../guides/network/custom-clear-container.rst:98
msgid ":command:`os-install` tells swupd to download and install."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:99
msgid ":command:`-V / --version` specifies the version of the |CL| bundles."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:100
msgid ":command:`--url` specifies the URL of the bundles repository."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:101
msgid ""
":command:`--statedir` specifies the state directory where downloaded "
"bundles and any state information are stored."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:103
msgid ""
":command:`--no-boot-update` tells swupd to skip updating boot files "
"because boot files are not required for a container."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:106
msgid ""
"For more information on swupd flags, enter the :command:`swupd os-install"
" -h` command."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:109
#: ../../guides/network/custom-clear-container.rst:172
#: ../../guides/network/custom-clear-container.rst:199
#: ../../guides/network/custom-clear-container.rst:233
#: ../../guides/network/custom-clear-container.rst:295
msgid "Example output:"
msgstr ""
#: ../../guides/network/custom-clear-container.rst:146
msgid "The WARNING message is expected and can be ignored."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:148
msgid "Create a tarball and compress it."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:155
msgid "Create the Dockerfile to build the image."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:166
msgid "Build the |CL| container image."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:193
msgid "List the newly created |CL| container image."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:206
msgid "Launch the built |CL| container."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:213
msgid "Manage bundles in a container"
msgstr ""
#: ../../guides/network/custom-clear-container.rst:215
msgid ""
"You can add and remove bundles from a |CL| container using the "
":command:`RUN swupd` command in the Dockerfile."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:219
msgid "Add a bundle"
msgstr ""
#: ../../guides/network/custom-clear-container.rst:221
msgid ""
"This example Dockerfile adds the :file:`pxe-server` bundle to an existing"
" |CL| Docker image:"
msgstr ""
#: ../../guides/network/custom-clear-container.rst:277
msgid ""
"The WARNING message can be ignored because systemd does not run inside a "
"container."
msgstr ""
#: ../../guides/network/custom-clear-container.rst:281
msgid "Remove a bundle"
msgstr ""
#: ../../guides/network/custom-clear-container.rst:283
msgid ""
"This example Dockerfile removes the :file:`pxe-server` bundle from an "
"existing |CL| Docker image:"
msgstr ""
#~ msgid ""
#~ "The official base |CL-ATTR| container"
#~ " image is published on Docker\\* Hub"
#~ " and is updated on a regular "
#~ "basis. This guide contains the steps "
#~ "to build a custom container image."
#~ msgstr ""
#~ msgid "Use `os-install` to download and install the bundles."
#~ msgstr ""
#~ msgid "The `swupd` example uses the following flags:"
#~ msgstr ""
#~ msgid ":command:`os-install` tells `swupd` to download and install."
#~ msgstr ""
#~ msgid ""
#~ ":command:`--no-boot-update` tells `swupd` "
#~ "to skip updating boot files because "
#~ "boot files are not required for a"
#~ " container."
#~ msgstr ""
#~ msgid ""
#~ "For more information on `swupd` flags,"
#~ " enter the :command:`swupd os-install "
#~ "-h` command."
#~ msgstr ""
#~ msgid "The `WARNING` message is expected and can be ignored."
#~ msgstr ""
#~ msgid ""
#~ "The `WARNING` message can be ignored "
#~ "because systemd does not run inside "
#~ "a container."
#~ msgstr ""
locale/de/LC_MESSAGES/guides/network/dpdk.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/network/dpdk.po
-437
View File
@@ -1,437 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/network/dpdk.rst:4
msgid "Use DPDK to send packets between platforms"
msgstr ""
#: ../../guides/network/dpdk.rst:6
msgid "This guide describes how to send packets between two platforms."
msgstr ""
#: ../../guides/network/dpdk.rst:13
msgid "Overview"
msgstr ""
#: ../../guides/network/dpdk.rst:15
msgid ""
"Figure 1 shows how to send packets between two platforms in a simple "
"configuration. The example uses the :abbr:`Data Plane Development Kit "
"(DPDK)`, which is a set of libraries, drivers, sample applications, and "
"tools for fast packet processing."
msgstr ""
#: ../../guides/network/dpdk.rst:24
msgid "Figure 1: Environment for l3fwd DPDK application"
msgstr ""
#: ../../guides/network/dpdk.rst:26
msgid "This example uses the following DPDK components:"
msgstr ""
#: ../../guides/network/dpdk.rst:28
msgid "pktgen: Traffic generator. See `pktgen`_ documentation for details."
msgstr ""
#: ../../guides/network/dpdk.rst:29
msgid ""
"l3fwd: Layer 3 forwarding example application. See `l3fwd`_ documentation"
" for details."
msgstr ""
#: ../../guides/network/dpdk.rst:33
msgid "Prerequisites"
msgstr ""
#: ../../guides/network/dpdk.rst:35
msgid "Two platforms using |CL-ATTR| release `13330`_ or higher."
msgstr ""
#: ../../guides/network/dpdk.rst:36
msgid "Both images must include the :command:`kernel-native` bundle."
msgstr ""
#: ../../guides/network/dpdk.rst:37
msgid "Install the :command:`network-basic-dev` bundle with the command:"
msgstr ""
#: ../../guides/network/dpdk.rst:43
msgid ""
"Each platform must have at least one :abbr:`NIC (Network Interface "
"Card)`. Check the `DPDK project`_ for the list of supported `dpdk.org "
"NICs`_."
msgstr ""
#: ../../guides/network/dpdk.rst:46
msgid "Two network cables."
msgstr ""
#: ../../guides/network/dpdk.rst:49
msgid "Install dpdk and build l3fwd example (Platform B)"
msgstr ""
#: ../../guides/network/dpdk.rst:51
msgid "Change to the :file:`l3fwd` example directory."
msgstr ""
#: ../../guides/network/dpdk.rst:57
msgid "Assign :envvar:`RTE_SDK` variable to the makefiles path."
msgstr ""
#: ../../guides/network/dpdk.rst:63
msgid ""
"Assign :envvar:`RTE_TARGET` variable to the location of the gcc\\* config"
" file."
msgstr ""
#: ../../guides/network/dpdk.rst:70
msgid ""
"Build the `l3fwd` application and add the configuration header to the "
":makevar:`CFLAGS` variable."
msgstr ""
#: ../../guides/network/dpdk.rst:79
msgid "Build pktgen (Platform A)"
msgstr ""
#: ../../guides/network/dpdk.rst:81
msgid "Download the `pktgen tar package`_ v3.1.2 or newer."
msgstr ""
#: ../../guides/network/dpdk.rst:83
msgid "Decompress packages and move to uncompressed source directory."
msgstr ""
#: ../../guides/network/dpdk.rst:85
msgid "Assign :envvar:`RTE_SDK` variable to the path where makefiles are located."
msgstr ""
#: ../../guides/network/dpdk.rst:91
msgid "Assign :envvar:`RTE_TARGET` to the location of the gcc config file."
msgstr ""
#: ../../guides/network/dpdk.rst:97
msgid ""
"Build the `pktgen` project and set the "
":makevar:`CONFIG_RTE_BUILD_SHARED_LIB` variable to \"n\"."
msgstr ""
#: ../../guides/network/dpdk.rst:105
msgid "Bind NICs to DPDK kernel drivers (Platforms A and B)"
msgstr ""
#: ../../guides/network/dpdk.rst:107
msgid ""
"The `l3fwd` application uses two NICs. The DPDK includes tools for "
"binding NICs to DPDK modules to run DPDK applications."
msgstr ""
#: ../../guides/network/dpdk.rst:110
msgid "Load the DPDK I/O kernel module."
msgstr ""
#: ../../guides/network/dpdk.rst:116
msgid ""
"Check the NIC status to determine which network cards are not busy. When "
"another application is using them, the status shows \"Active\", and those"
" NICs cannot be bound."
msgstr ""
#: ../../guides/network/dpdk.rst:124
msgid ""
"Bind two available NICs. The general syntax for binding is: :command"
":`dpdk-devbind --bind=vfio-pci <device-entry>`. A working example is "
"shown below:"
msgstr ""
#: ../../guides/network/dpdk.rst:132
msgid ""
"Check the NIC status to verify that the NICs are bound correctly. If "
"successful, `drv` displays the value `igb_uio`, which confirms that the "
"NICs are using the DPDK modules."
msgstr ""
#: ../../guides/network/dpdk.rst:138
msgid "Set hugepages (Platforms A and B)"
msgstr ""
#: ../../guides/network/dpdk.rst:140
msgid ""
"|CL| supports `hugepages` for the large memory pool allocation used for "
"packet buffers."
msgstr ""
#: ../../guides/network/dpdk.rst:143
msgid "Set the number of hugepages."
msgstr ""
#: ../../guides/network/dpdk.rst:149
msgid "Allocate pages on NUMA machines."
msgstr ""
#: ../../guides/network/dpdk.rst:156
msgid "Make memory available for DPDK."
msgstr ""
#: ../../guides/network/dpdk.rst:162
msgid ""
"For more information, refer to the `DPDK guide`_ System Requirements "
"section."
msgstr ""
#: ../../guides/network/dpdk.rst:167
msgid "Set up the physical environment (Platforms A and B)"
msgstr ""
#: ../../guides/network/dpdk.rst:169
msgid ""
"Connect the NICs on Platform A to the NICs on Platform B using the "
"network cables as shown in figure 2."
msgstr ""
#: ../../guides/network/dpdk.rst:174
msgid "Figure 2: Physical network environment"
msgstr ""
#: ../../guides/network/dpdk.rst:178
msgid "Run l3fwd application (Platform B)"
msgstr ""
#: ../../guides/network/dpdk.rst:180
msgid ""
"The `l3fwd` application is one of the DPDK examples available when you "
"install the :file:`dpdk-dev` bundle. `l3fwd` forwards packets from one "
"NIC to another. For details, refer to the `l3fwd`_ documentation."
msgstr ""
#: ../../guides/network/dpdk.rst:184
msgid "Open the l3fwd example directory."
msgstr ""
#: ../../guides/network/dpdk.rst:190
msgid "**This step is very important.**"
msgstr ""
#: ../../guides/network/dpdk.rst:192
msgid "DPDK needs poll mode drivers to operate."
msgstr ""
#: ../../guides/network/dpdk.rst:193
msgid "Poll mode drivers are shared objects in :file:`/usr/lib64`."
msgstr ""
#: ../../guides/network/dpdk.rst:194
msgid "See the full list of supported NICs at `dpdk.org NICs`_."
msgstr ""
#: ../../guides/network/dpdk.rst:195
msgid ""
"You must know which kernel module each NIC is using and choose a poll "
"mode driver that corresponds to your NICs."
msgstr ""
#: ../../guides/network/dpdk.rst:198
msgid ""
"NIC binding and `pktgen` configuration depends upon network use cases and"
" available system resources. Use the :command:`-d` flag to set the poll "
"mode driver."
msgstr ""
#: ../../guides/network/dpdk.rst:202
msgid ""
"The following example assumes that the NICs use the `e1000` network "
"driver and the `e1000` poll mode driver. The :file:`librte_pmd_e1000.so` "
"is located in :file:`/usr/lib64` in |CL|."
msgstr ""
#: ../../guides/network/dpdk.rst:210
msgid ""
"The `l3fwd` application shows port initialization details at startup. "
"After port 0 initialization completes, `l3fwd` shows a MAC address and "
"information for port 1."
msgstr ""
#: ../../guides/network/dpdk.rst:214
msgid "Save the MAC address for configuring the `pktgen` project."
msgstr ""
#: ../../guides/network/dpdk.rst:217
msgid "Run pktgen application (Platform A)"
msgstr ""
#: ../../guides/network/dpdk.rst:219
msgid "`pktgen` is a network traffic generator included in the DPDK."
msgstr ""
#: ../../guides/network/dpdk.rst:221
msgid ""
"`pktgen` configuration depends upon the network setup and the available "
"system resources. The following example shows a basic configuration."
msgstr ""
#: ../../guides/network/dpdk.rst:229
msgid "Enable active colorful output (optional)."
msgstr ""
#: ../../guides/network/dpdk.rst:235
msgid ""
"Use the MAC addresses shown by the `l3fwd` application during "
"initialization. The command to set the MAC addresses in `pktgen` has the "
"format:"
msgstr ""
#: ../../guides/network/dpdk.rst:242 ../../guides/network/dpdk.rst:301
#: ../../guides/network/dpdk.rst:319
msgid "Here is a working example:"
msgstr ""
#: ../../guides/network/dpdk.rst:249
msgid "Send packets."
msgstr ""
#: ../../guides/network/dpdk.rst:255
msgid "For more details, see the `pktgen`_ documentation."
msgstr ""
#: ../../guides/network/dpdk.rst:258
msgid "Appendix A: Use pass-through for virtual machines"
msgstr ""
#: ../../guides/network/dpdk.rst:260
msgid ""
"This section explains how to set up a virtual environment where virtual "
"machines control the NICs on the host."
msgstr ""
#: ../../guides/network/dpdk.rst:263
msgid "Create a new directory and move to it."
msgstr ""
#: ../../guides/network/dpdk.rst:265
msgid ""
"Download or create a :file:`start_qemu.sh` script for running a kvm "
"virtual machine:"
msgstr ""
#: ../../guides/network/dpdk.rst:272
msgid "Download a bare-metal image of |CL| and rename it as :file:`clear.img`."
msgstr ""
#: ../../guides/network/dpdk.rst:274
msgid "Look for an Ethernet\\* device entry that contains vendor and device ID:"
msgstr ""
#: ../../guides/network/dpdk.rst:280
msgid "An example output:"
msgstr ""
#: ../../guides/network/dpdk.rst:286
msgid ""
"where `03:00.0` is the device entry and `8086:1521` is the `vendor:device"
" ID`. Record this information, because you need it to unbind the NICs "
"from a host."
msgstr ""
#: ../../guides/network/dpdk.rst:291
msgid ""
"Unbind the NICs from the host to do pass-through with virtual machines. "
"|CL| supports this action. The commands take the format:"
msgstr ""
#: ../../guides/network/dpdk.rst:310
msgid ""
"Assign the unbound NICs to the KVM virtual machine (guest). Modify the "
":file:`start_qemu.sh` script in `qemu-system-x86_64` arguments, and add "
"the lines with the host's NICs information in the format:"
msgstr ""
#: ../../guides/network/dpdk.rst:326
msgid ""
"Add more NUMA machines to the virtual machine by adding lines to the "
"Makefile boot target in the format:"
msgstr ""
#: ../../guides/network/dpdk.rst:333
msgid ""
"Here is a working example for a virtual machine with 4096 memory and four"
" CPUs:"
msgstr ""
#: ../../guides/network/dpdk.rst:341
msgid "Each NUMA machine must use the same quantity of memory."
msgstr ""
#: ../../guides/network/dpdk.rst:343
msgid "Run the :file:`start_qemu.sh` script."
msgstr ""
#~ msgid ""
#~ "This document describes how to send "
#~ "packets between two platforms in the "
#~ "simple configuration shown in :ref:`Figure "
#~ "1 <f1>`. The example uses the "
#~ ":abbr:`Data Plane Development Kit (DPDK)`, "
#~ "which is a set of libraries, "
#~ "drivers, sample applications, and tools "
#~ "for fast packet processing."
#~ msgstr ""
#~ msgid "pktgen: Traffic generator. See `pktgen documentation`_ for details."
#~ msgstr ""
#~ msgid ""
#~ "l3fwd: Layer 3 forwarding example "
#~ "application. See `l3fwd documentation`_ for"
#~ " details."
#~ msgstr ""
#~ msgid "Both images must include the :file:`kernel-native bundle`."
#~ msgstr ""
#~ msgid "Install the :file:`network-basic-dev` bundle with the command:"
#~ msgstr ""
#~ msgid ""
#~ "Check the NIC status to determine "
#~ "which network cards are not busy. "
#~ "When another application is using them,"
#~ " the status shows `Active`, and those"
#~ " NICs cannot be bound."
#~ msgstr ""
#~ msgid ""
#~ "Connect the NICs on Platform A to"
#~ " the NICs on Platform B using "
#~ "the network cables as shown in "
#~ ":ref:`Figure 2<f2>`."
#~ msgstr ""
#~ msgid ""
#~ "The `l3fwd` application is one of "
#~ "the DPDK examples available when you "
#~ "install the :file:`dpdk-dev` bundle. "
#~ "`l3fwd` forwards packets from one NIC"
#~ " to another. For details, refer to"
#~ " the `l3fwd documentation`_."
#~ msgstr ""
#~ msgid "For more details, see the `pktgen documentation`_."
#~ msgstr ""
locale/de/LC_MESSAGES/guides/network/ipxe-install.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/network/ipxe-install.po
-405
View File
@@ -1,405 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/network/ipxe-install.rst:4
msgid "Install over the network with iPXE"
msgstr ""
#: ../../guides/network/ipxe-install.rst:6
msgid ""
"This guide describes how to install |CL-ATTR| using :abbr:`PXE (Pre-boot "
"Execution Environment)` over the network."
msgstr ""
#: ../../guides/network/ipxe-install.rst:14
msgid "Overview"
msgstr ""
#: ../../guides/network/ipxe-install.rst:16
msgid ""
"PXE is an industry standard that describes client-server interaction with"
" network-boot software and uses the DHCP and TFTP protocols. This guide "
"shows one method of using the PXE environment to install |CL|."
msgstr ""
#: ../../guides/network/ipxe-install.rst:20
msgid ""
"The PXE extension called `iPXE`_ adds support for additional protocols "
"such as HTTP, :abbr:`iSCSI (Internet Small Computer Systems Interface)`, "
":abbr:`AoE (ATA over Ethernet\\*)`, and :abbr:`FCoE (Fiber Channel over "
"Ethernet\\*)`. iPXE enables network booting on computers with no built-in"
" PXE support."
msgstr ""
#: ../../guides/network/ipxe-install.rst:25
msgid ""
"To install |CL| through iPXE, you must create a PXE client. Figure 1 "
"depicts the flow of information between a PXE server and a PXE client."
msgstr ""
#: ../../guides/network/ipxe-install.rst:31
msgid "Figure 1: PXE information flow."
msgstr ""
#: ../../guides/network/ipxe-install.rst:35
msgid ""
"The |CL| image that boots through the PXE process automatically erases "
"all data and partitions on the PXE client system and creates 3 new "
"partitions to install onto."
msgstr ""
#: ../../guides/network/ipxe-install.rst:40
msgid "Prerequisites"
msgstr ""
#: ../../guides/network/ipxe-install.rst:42
msgid "Before booting with iPXE, make the following preparations."
msgstr ""
#: ../../guides/network/ipxe-install.rst:44
msgid ""
"Connect the PXE server and PXE clients to a switch on a private network, "
"as shown in figure 2."
msgstr ""
#: ../../guides/network/ipxe-install.rst:50
msgid "Figure 2: Network topology."
msgstr ""
#: ../../guides/network/ipxe-install.rst:52
msgid ""
"Your PXE client must have a boot order where the network boot option is "
"prioritized before the disk boot option."
msgstr ""
#: ../../guides/network/ipxe-install.rst:55
msgid "Your PXE server must have:"
msgstr ""
#: ../../guides/network/ipxe-install.rst:57
msgid "Ethernet/LAN boot option."
msgstr ""
#: ../../guides/network/ipxe-install.rst:58
msgid "At least two network adapters."
msgstr ""
#: ../../guides/network/ipxe-install.rst:59
msgid "Connection to a public network."
msgstr ""
#: ../../guides/network/ipxe-install.rst:60
msgid "Secure boot option disabled."
msgstr ""
#: ../../guides/network/ipxe-install.rst:64
msgid ""
"You must disable the secure boot option in the BIOS because the UEFI "
"binaries used to boot |CL| are not signed."
msgstr ""
#: ../../guides/network/ipxe-install.rst:69
msgid "Configuration"
msgstr ""
#: ../../guides/network/ipxe-install.rst:71
msgid ""
"To set up |CL| using iPXE automatically, use the :file:`configure-"
"ipxe.sh` script included with :abbr:`ICIS (Ister Cloud Init Service)`. "
"For additional instructions on the script, refer to the guide on the "
"`ister-cloud-init-svc`_ GitHub\\* repository."
msgstr ""
#: ../../guides/network/ipxe-install.rst:76
msgid "To set up |CL| manually, perform the steps below."
msgstr ""
#: ../../guides/network/ipxe-install.rst:78
msgid "Define the variables used for iPXE boot configuration."
msgstr ""
#: ../../guides/network/ipxe-install.rst:94
msgid "Log in and get root privilege."
msgstr ""
#: ../../guides/network/ipxe-install.rst:100
msgid ""
"Add the :command:`pxe-server` bundle to your |CL| system. The bundle "
"contains all files needed to run a PXE server."
msgstr ""
#: ../../guides/network/ipxe-install.rst:107
msgid ""
"Download the latest network-bootable release of |CL| and extract the "
"files."
msgstr ""
#: ../../guides/network/ipxe-install.rst:121
msgid ""
"Ensure that the initial ramdisk file is named :file:`initrd` and the "
"kernel file is named :file:`linux`, which is a symbolic link to the "
"actual kernel file."
msgstr ""
#: ../../guides/network/ipxe-install.rst:125
msgid ""
"Create an iPXE boot script with the following contents. During an iPXE "
"boot, the iPXE boot script directs the PXE client to download the files "
"to boot and install |CL|. Use the names previously given to the initial "
"ramdisk and kernel files."
msgstr ""
#: ../../guides/network/ipxe-install.rst:141
msgid ""
"The :command:`pxe-server` bundle contains a lightweight web-server known "
"as nginx. Create a configuration file for nginx to serve |CL| to PXE "
"clients with the following contents:"
msgstr ""
#: ../../guides/network/ipxe-install.rst:163
msgid ""
"Create a separate nginx configuration file to serve network-bootable "
"images on a non-standard port number. This action saves existing nginx "
"configurations."
msgstr ""
#: ../../guides/network/ipxe-install.rst:167
msgid "Start nginx and enable the startup on boot option."
msgstr ""
#: ../../guides/network/ipxe-install.rst:174
msgid ""
"The :command:`pxe-server` bundle contains a lightweight DNS server which "
"conflicts with the DNS stub listener provided in `systemd-resolved`. "
"Disable the DNS stub listener and temporarily stop `systemd-resolved`."
msgstr ""
#: ../../guides/network/ipxe-install.rst:188
msgid ""
"Assign a static IP address to the network adapter for the private network"
" and restart `systemd-networkd` with the following commands:"
msgstr ""
#: ../../guides/network/ipxe-install.rst:204
msgid ""
"Configure :abbr:`NAT (Network Address Translation)` to route traffic from"
" the private network to the public network. This action makes the PXE "
"server act as a router. To make these changes persistent during reboots, "
"save the changes to the firewall with the following commands:"
msgstr ""
#: ../../guides/network/ipxe-install.rst:220
msgid ""
"The firewall masks packets to make them appear as coming from the PXE "
"server and hides PXE clients from the public network."
msgstr ""
#: ../../guides/network/ipxe-install.rst:223
msgid ""
"Configure the kernel to forward network packets to different interfaces. "
"Otherwise, NAT will not work."
msgstr ""
#: ../../guides/network/ipxe-install.rst:232
msgid ""
"The :command:`pxe-server` bundle contains iPXE firmware images that allow"
" computers without an iPXE implementation to perform an iPXE boot. Create"
" a TFTP hosting directory and populate the directory with the iPXE "
"firmware images with the following commands:"
msgstr ""
#: ../../guides/network/ipxe-install.rst:242
msgid ""
"The :command:`pxe-server` bundle contains a lightweight TFTP, DNS, and "
"DHCP server known as `dnsmasq`. Create a configuration file for `dnsmasq`"
" to listen on a dedicated IP address for those functions. PXE clients on "
"the private network will use this IP address."
msgstr ""
#: ../../guides/network/ipxe-install.rst:253
msgid ""
"Add the options to serve iPXE firmware images to PXE clients over TFTP to"
" the `dnsmasq` configuration file."
msgstr ""
#: ../../guides/network/ipxe-install.rst:263
msgid ""
"Add the options to host a DHCP server for PXE clients to the "
":file:`dnsmasq` configuration file."
msgstr ""
#: ../../guides/network/ipxe-install.rst:285
msgid "The configuration provides the following important functions:"
msgstr ""
#: ../../guides/network/ipxe-install.rst:287
msgid ""
"Directs PXE clients without an iPXE implementation to the TFTP server to "
"acquire architecture-specific iPXE firmware images that allow them to "
"perform an iPXE boot."
msgstr ""
#: ../../guides/network/ipxe-install.rst:290
msgid ""
"Activates only on the network adapter that has an IP address on the "
"defined subnet."
msgstr ""
#: ../../guides/network/ipxe-install.rst:292
msgid "Directs PXE clients to the DNS server."
msgstr ""
#: ../../guides/network/ipxe-install.rst:293
msgid "Directs PXE clients to the PXE server for routing via NAT."
msgstr ""
#: ../../guides/network/ipxe-install.rst:294
msgid ""
"Divides the private network into two pools of IP addresses. One pool is "
"for network boot and one pool is used after boot. Each pool has their own"
" lease times."
msgstr ""
#: ../../guides/network/ipxe-install.rst:298
msgid ""
"Create a file for `dnsmasq` to record the IP addresses it provides to PXE"
" clients."
msgstr ""
#: ../../guides/network/ipxe-install.rst:306
msgid "Start `dnsmasq` and enable startup on boot."
msgstr ""
#: ../../guides/network/ipxe-install.rst:313
msgid "Start `systemd-resolved`."
msgstr ""
#: ../../guides/network/ipxe-install.rst:321
msgid ""
"`systemd-resolved` dynamically updates the list of DNS servers for the "
"private network if you use the `dnsmasq` DNS server. The setup creates a "
"pass-through DNS server that relies on the DNS servers listed in "
":file:`/etc/resolv.conf`."
msgstr ""
#: ../../guides/network/ipxe-install.rst:326
msgid "Power on the PXE client and watch the client boot and install |CL|."
msgstr ""
#: ../../guides/network/ipxe-install.rst:328
msgid ""
"After booting, |CL| automatically partitions the hard drive, installs "
"itself, updates to the latest version, and reboots."
msgstr ""
#: ../../guides/network/ipxe-install.rst:332
msgid ""
"**Congratulations!** You have successfully installed and configured a PXE"
" server that enables PXE clients to boot and install |CL| over the "
"network."
msgstr ""
#~ msgid "Install |CL-ATTR| over the network with iPXE"
#~ msgstr ""
#~ msgid ""
#~ "This guide describes how to install "
#~ "|CL-ATTR| using :abbr:`PXE (Pre-boot "
#~ "Execution Environment)`."
#~ msgstr ""
#~ msgid ""
#~ "Connect the PXE server and PXE "
#~ "clients to a switch on a private"
#~ " network, as shown in Figure 2."
#~ msgstr ""
#~ msgid ""
#~ "To set up |CL| using iPXE "
#~ "automatically, use the :file:`configure-"
#~ "ipxe.sh` script included with :abbr:`ICIS "
#~ "(Ister Cloud Init Service)`. For "
#~ "additional instructions on the script, "
#~ "refer to the guide on the `ICIS"
#~ " GitHub repository`_."
#~ msgstr ""
#~ msgid ""
#~ "Add the `pxe-server` bundle to "
#~ "your |CL| system. The bundle contains"
#~ " all files needed to run a PXE"
#~ " server."
#~ msgstr ""
#~ msgid ""
#~ "The `pxe-server` bundle contains a "
#~ "lightweight web-server known as `nginx`."
#~ " Create a configuration file for "
#~ "`nginx` to serve |CL| to PXE "
#~ "clients with the following contents:"
#~ msgstr ""
#~ msgid ""
#~ "Create a separate `nginx` configuration "
#~ "file to serve network-bootable images"
#~ " on a non-standard port number. "
#~ "This action saves existing `nginx` "
#~ "configurations."
#~ msgstr ""
#~ msgid "Start `nginx` and enable the startup on boot option."
#~ msgstr ""
#~ msgid ""
#~ "The `pxe-server` bundle contains a "
#~ "lightweight DNS server which conflicts "
#~ "with the DNS stub listener provided "
#~ "in `systemd-resolved`. Disable the DNS"
#~ " stub listener and temporarily stop "
#~ "`systemd-resolved`."
#~ msgstr ""
#~ msgid ""
#~ "The `pxe-server` bundle contains iPXE"
#~ " firmware images that allow computers "
#~ "without an iPXE implementation to "
#~ "perform an iPXE boot. Create a "
#~ "TFTP hosting directory and populate the"
#~ " directory with the iPXE firmware "
#~ "images with the following commands:"
#~ msgstr ""
#~ msgid ""
#~ "The `pxe-server` bundle contains a "
#~ "lightweight TFTP, DNS, and DHCP server"
#~ " known as `dnsmasq`. Create a "
#~ "configuration file for `dnsmasq` to "
#~ "listen on a dedicated IP address "
#~ "for those functions. PXE clients on "
#~ "the private network will use this "
#~ "IP address."
#~ msgstr ""
#~ msgid ""
#~ "Add the options to host a DHCP "
#~ "server for PXE clients to the "
#~ "`dnsmasq` configuration file."
#~ msgstr ""
locale/de/LC_MESSAGES/guides/network/network-bonding.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/network/network-bonding.po
-200
View File
@@ -1,200 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/network/network-bonding.rst:4
msgid "Combine multiple interfaces with network bonding"
msgstr ""
#: ../../guides/network/network-bonding.rst:6
msgid ""
"This guide describes how to configure systemd to use the "
":command:`bonding` driver."
msgstr ""
#: ../../guides/network/network-bonding.rst:9
msgid ""
"Network bonding combines multiple network interfaces into a single "
"logical interface to provide redundancy and bandwidth aggregation."
msgstr ""
#: ../../guides/network/network-bonding.rst:12
msgid "|CL-ATTR| includes the Linux `Bonding driver`_ and `Team driver`_ ."
msgstr ""
#: ../../guides/network/network-bonding.rst:14
msgid "The example demonstrates how to:"
msgstr ""
#: ../../guides/network/network-bonding.rst:16
msgid "Bond all four ports of a quad-port NIC in 802.3ad mode."
msgstr ""
#: ../../guides/network/network-bonding.rst:18
msgid "Enable jumbo frames to optimize large data transfers on the local network."
msgstr ""
#: ../../guides/network/network-bonding.rst:20
msgid ""
"Your NICs and network switch must support 802.3ad mode and jumbo frames. "
"The example explains how to configure your NICs for both features. Your "
"switch may require additional configuration. See your switch "
"documentation for details."
msgstr ""
#: ../../guides/network/network-bonding.rst:26
msgid "You must run all commands in this guide as root."
msgstr ""
#: ../../guides/network/network-bonding.rst:28
msgid "Log in and get root privileges."
msgstr ""
#: ../../guides/network/network-bonding.rst:34
msgid "Create the :file:`/etc/systemd/network` directory."
msgstr ""
#: ../../guides/network/network-bonding.rst:40
msgid ""
"The :file:`/etc/systemd/network` directory contains configuration files "
"and network settings for the virtual device and its underlying physical "
"interfaces."
msgstr ""
#: ../../guides/network/network-bonding.rst:44
msgid ""
"Configure systemd to create a virtual network device called `bond1`. Use "
"a text editor to create a file named :file:`30-bond1.netdev`."
msgstr ""
#: ../../guides/network/network-bonding.rst:59
msgid ""
"Refer to the `systemd.netdev`_ manpage for :file:`30-bond1.netdev` file "
"syntax. This example is based on Example 9 on the manpage. Modify the "
"example for your configuration."
msgstr ""
#: ../../guides/network/network-bonding.rst:63
msgid ""
"Configure the slave interfaces. Create a text file named "
":file:`30-bond1-enp1s0.network`. Assign the slave interfaces to the "
"virtual `bond1` device and use the syntax shown in `systemd.network`_."
msgstr ""
#: ../../guides/network/network-bonding.rst:78
msgid ""
"The example bonds all four ports of a quad-port NIC as a slave of "
"`bond1`. The example uses a wildcard match because the NIC names are in "
"the range `enp1s0f0-enp1s0f3`. If your NIC names are not wildcard-"
"compatible, create a separate :file:`.network` file for each NIC."
msgstr ""
#: ../../guides/network/network-bonding.rst:83
msgid ""
"For best results, do not assign addresses or DHCP support to the "
"individual NICs."
msgstr ""
#: ../../guides/network/network-bonding.rst:86
msgid ""
"The `MTUBytes` setting enables jumbo frames of up to 9000 bytes. Your "
"switch may require additional configuration to support this setting."
msgstr ""
#: ../../guides/network/network-bonding.rst:89
msgid "Configure the bonded interface in a file named :file:`30-bond1.network`."
msgstr ""
#: ../../guides/network/network-bonding.rst:103
msgid "`bond1` is a virtual interface with no physical link status."
msgstr ""
#: ../../guides/network/network-bonding.rst:105
msgid ""
"`BindCarrier` indicates that the `bond1` link status is determined by the"
" status of the listed slave devices."
msgstr ""
#: ../../guides/network/network-bonding.rst:108
msgid ""
"`Address` contains an IP address that you assign to the logical "
"interface. DHCP bonded interfaces are complex and outside the scope of "
"this example."
msgstr ""
#: ../../guides/network/network-bonding.rst:111
msgid ""
"`MTUBytes` must be set to 9000 on all slave interfaces and on the bonded "
"interface for successful jumbo frames operation. If `MTUBytes` is not the"
" same on all interfaces, then the lowest value is used."
msgstr ""
#: ../../guides/network/network-bonding.rst:115
msgid "Apply the new network configuration with the command:"
msgstr ""
#: ../../guides/network/network-bonding.rst:121
msgid ""
"The `MTUBytes` settings do not take effect until you reboot or manually "
"apply the settings with a utility such as ifconfig."
msgstr ""
#~ msgid ""
#~ "|CL-ATTR| includes Linux bonding_ and"
#~ " team_ drivers. This guide describes "
#~ "how to configure systemd to use "
#~ "the `bonding` driver."
#~ msgstr ""
#~ msgid "Bond all four ports of a quad-port NIC in `802.3ad` mode."
#~ msgstr ""
#~ msgid ""
#~ "Your NICs and network switch must "
#~ "support `802.3ad` mode and jumbo frames."
#~ " The example explains how to "
#~ "configure your NICs for both features."
#~ " Your switch may require additional "
#~ "configuration. See your switch documentation"
#~ " for details."
#~ msgstr ""
#~ msgid ""
#~ "Refer to the systemd.netdev_ manpage for"
#~ " :file:`30-bond1.netdev` file syntax. This "
#~ "example is based on Example 9 on"
#~ " the manpage. Modify the example for"
#~ " your configuration."
#~ msgstr ""
#~ msgid ""
#~ "Configure the slave interfaces. Create a"
#~ " text file named :file:`30-bond1-enp1s0.network`."
#~ " Assign the slave interfaces to the"
#~ " virtual `bond1` device and use the"
#~ " syntax shown in systemd.network_."
#~ msgstr ""
#~ msgid ""
#~ "The `MTUBytes` settings do not take "
#~ "effect until you reboot or manually "
#~ "apply the settings with a utility "
#~ "such as `ifconfig`."
#~ msgstr ""
locale/de/LC_MESSAGES/guides/network/vnc.mo
BIN
View File
Binary file not shown.
locale/de/LC_MESSAGES/guides/network/vnc.po
-1148
View File
File diff suppressed because it is too large Load Diff
locale/de/LC_MESSAGES/guides/stacks/dars.po
-151
View File
@@ -1,151 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/stacks/dars.rst:4
msgid "Data Analytics Reference Stack"
msgstr ""
#: ../../guides/stacks/dars.rst:6
msgid ""
"This guide explains how to use the :abbr:`DARS (Data Analytics Reference "
"Stack)`, and to optionally build your own DARS container image."
msgstr ""
#: ../../guides/stacks/dars.rst:9
msgid ""
"Any system that supports Docker\\* containers can be used with DARS. This"
" steps in this guide use |CL-ATTR| as the host system."
msgstr ""
#: ../../guides/stacks/dars.rst:17
msgid "The Data Analytics Reference Stack release"
msgstr ""
#: ../../guides/stacks/dars.rst:19
msgid ""
"The Data Analytics Reference Stack (DARS) provides developers and "
"enterprises a straightforward, highly optimized software stack for "
"storing and processing large amounts of data. More detail is available "
"on the `DARS architecture and performance benchmarks`_."
msgstr ""
#: ../../guides/stacks/dars.rst:23
msgid ""
"The Data Analytics Reference Stack provides two pre-built Docker images, "
"available on `Docker Hub`_:"
msgstr ""
#: ../../guides/stacks/dars.rst:26
msgid "A |CL|-derived `DARS with OpenBlas`_ stack optimized for `OpenBLAS`_"
msgstr ""
#: ../../guides/stacks/dars.rst:27
msgid "A |CL|-derived `DARS with Intel® MKL`_ stack optimized for `MKL`_"
msgstr ""
#: ../../guides/stacks/dars.rst:29
msgid ""
"We recommend you view the latest component versions for each image in the"
" :file:`README` found in the `Data Analytics Reference Stack`_ GitHub\\* "
"repository. Because |CL| is a rolling distribution, the package version "
"numbers in the |CL|-based containers may not be the latest released by "
"|CL|."
msgstr ""
#: ../../guides/stacks/dars.rst:36
msgid ""
"The Data Analytics Reference Stack is a collective work, and each piece "
"of software within the work has its own license. Please see the `DARS "
"Terms of Use`_ for more details about licensing and usage of the Data "
"Analytics Reference Stack."
msgstr ""
#: ../../guides/stacks/dars.rst:42
msgid "Using the Docker images"
msgstr ""
#: ../../guides/stacks/dars.rst:44
msgid ""
"To immediately start using the latest stable DARS images, pull an image "
"directly from `Docker Hub`_. This example uses the `DARS with Intel® "
"MKL`_ Docker image."
msgstr ""
#: ../../guides/stacks/dars.rst:48
msgid "Once you have downloaded the image, you can run it with"
msgstr ""
#: ../../guides/stacks/dars.rst:54
msgid ""
"This will launch the image and drop you into a bash shell inside the "
"container. You will see output similar to the following:"
msgstr ""
#: ../../guides/stacks/dars.rst:75
msgid ""
"The :command:`--ulimit nofile` parameter is currently required in order "
"to increase the number of open files opened at certain point by the spark"
" engine."
msgstr ""
#: ../../guides/stacks/dars.rst:80
msgid "Building DARS images"
msgstr ""
#: ../../guides/stacks/dars.rst:82
msgid ""
"If you choose to build your own DARS container images, you can customize "
"them as needed. Use the provided Dockerfile as a baseline."
msgstr ""
#: ../../guides/stacks/dars.rst:85
msgid ""
"To construct images with |CL|, start with a |CL| development platform "
"that has the :command:`containers-basic-dev` bundle installed. Learn more"
" about bundles and installing them by using :ref:`swupd-guide`."
msgstr ""
#: ../../guides/stacks/dars.rst:89
msgid "Clone the `Data Analytics Reference Stack`_ GitHub\\* repository."
msgstr ""
#: ../../guides/stacks/dars.rst:95
msgid ""
"Inside the DARS directory, run :command:`make` to build OpenBLAS and MKL "
"images."
msgstr ""
#: ../../guides/stacks/dars.rst:101
msgid ""
"Run :command:`make baseline` to build the baseline CentOS image. "
"Depending on the system, it may take a while to finish building."
msgstr ""
#: ../../guides/stacks/dars.rst:108
msgid "Once completed, check the resulting images with :command:`Docker`"
msgstr ""
#: ../../guides/stacks/dars.rst:114
msgid ""
"You can use any of the resulting images to launch fully functional "
"containers. If you need to customize the containers, you can edit the "
"provided :file:`Dockerfile`."
msgstr ""
locale/de/LC_MESSAGES/guides/stacks/dlrs/dlrs.po
-616
View File
@@ -1,616 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2019, many
# This file is distributed under the same license as the Clear Linux*
# Project Docs package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Clear Linux* Project Docs latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-22 12:54-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../../guides/stacks/dlrs/dlrs.rst:4
msgid "Deep Learning Reference Stack"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:6
msgid ""
"This guide describes how to run benchmarking workloads for TensorFlow\\*,"
" PyTorch\\*, and Kubeflow in |CL-ATTR| using the Deep Learning Reference "
"Stack."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:14
msgid "Overview"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:16
msgid ""
"We created the Deep Learning Reference Stack to help AI developers "
"deliver the best experience on Intel® Architecture. This stack reduces "
"complexity common with deep learning software components, provides "
"flexibility for customized solutions, and enables you to quickly "
"prototype and deploy Deep Learning workloads. Use this guide to run "
"benchmarking workloads on your solution."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:23
msgid "The Deep Learning Reference Stack is available in the following versions:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:25
msgid ""
"`Intel MKL-DNN-VNNI`_, which is optimized using Intel® Math Kernel "
"Library for Deep Neural Networks (Intel® MKL-DNN) primitives and "
"introduces support for Intel® AVX-512 Vector Neural Network Instructions "
"(VNNI)."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:28
msgid ""
"`Intel MKL-DNN`_, which includes the TensorFlow framework optimized using"
" Intel® Math Kernel Library for Deep Neural Networks (Intel® MKL-DNN) "
"primitives."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:31
msgid "`Eigen`_, which includes `TensorFlow`_ optimized for Intel® architecture."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:32
msgid "`PyTorch with OpenBLAS`_, which includes PyTorch with OpenBlas."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:33
msgid ""
"`PyTorch with Intel MKL-DNN`_, which includes PyTorch optimized using "
"Intel® Math Kernel Library (Intel® MKL) and Intel MKL-DNN."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:38
msgid ""
"To take advantage of the Intel® AVX-512 and VNNI functionality with the "
"Deep Learning Reference Stack, you must use the following hardware:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:41
msgid "Intel® AVX-512 images require an Intel® Xeon® Scalable Platform"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:42
msgid "VNNI requires a 2nd generation Intel® Xeon® Scalable Platform"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:45
msgid "Stack features"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:47
msgid "`DLRS V3.0`_ release announcement."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:48
msgid "Deep Learning Reference Stack v2.0 including current `PyTorch benchmark`_."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:50
msgid ""
"Deep Learning Reference Stack v1.0 including current `TensorFlow "
"benchmark`_ results."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:52
msgid ""
"`DLRS Release notes`_ on Github\\* for the latest release of Deep "
"Learning Reference Stack."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:57
msgid ""
"The Deep Learning Reference Stack is a collective work, and each piece of"
" software within the work has its own license. Please see the `DLRS "
"Terms of Use`_ for more details about licensing and usage of the Deep "
"Learning Reference Stack."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:62
msgid "Prerequisites"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:64
msgid ":ref:`Install <bare-metal-install-desktop>` |CL| on your host system"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:65
msgid ":command:`containers-basic` bundle"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:66
msgid ":command:`cloud-native-basic` bundle"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:68
msgid ""
"In |CL|, :command:`containers-basic` includes Docker\\*, which is "
"required for TensorFlow and PyTorch benchmarking. Use the "
":command:`swupd` utility to check if :command:`containers-basic` and "
":command:`cloud-native-basic` are present:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:77
msgid ""
"To install the :command:`containers-basic` or :command:`cloud-native-"
"basic` bundles, enter:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:84
msgid ""
"Docker is not started upon installation of the :command:`containers-"
"basic` bundle. To start Docker, enter:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:91
msgid ""
"To ensure that Kubernetes is correctly installed and configured, follow "
"the instructions in :ref:`kubernetes`."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:95
msgid "Version compatibility"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:97
msgid "We validated these steps against the following software package versions:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:99
msgid "|CL| 26240 (Minimum supported version)"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:100
msgid "Docker 18.06.1"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:101
msgid "Kubernetes 1.11.3"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:102
msgid "Go 1.11.12"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:107
msgid ""
"The Deep Learning Reference Stack was developed to provide the best user "
"experience when executed on a |CL| host. However, as the stack runs in a"
" container environment, you should be able to complete the following "
"sections of this guide on other Linux* distributions, provided they "
"comply with the Docker*, Kubernetes* and Go* package versions listed "
"above. Look for your distribution documentation on how to update packages"
" and manage Docker services."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:112
msgid "TensorFlow single and multi-node benchmarks"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:114
msgid ""
"This section describes running the `TensorFlow Benchmarks`_ in single "
"node. For multi-node testing, replicate these steps for each node. These "
"steps provide a template to run other benchmarks, provided that they can "
"invoke TensorFlow."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:121
msgid ""
"Performance test results for the Deep Learning Reference Stack and for "
"this guide were obtained using `runc` as the runtime."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:124
msgid ""
"Download either the `Eigen`_ or the `Intel MKL-DNN`_ Docker image from "
"`Docker Hub`_."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:127 ../../guides/stacks/dlrs/dlrs.rst:169
msgid "Run the image with Docker:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:136 ../../guides/stacks/dlrs/dlrs.rst:177
msgid ""
"Launching the Docker image with the :command:`-i` argument starts "
"interactive mode within the container. Enter the following commands in "
"the running container."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:140
msgid "Clone the benchmark repository in the container:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:146 ../../guides/stacks/dlrs/dlrs.rst:187
msgid "Execute the benchmark script:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:154
msgid ""
"You can replace the model with one of your choice supported by the "
"TensorFlow benchmarks."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:157
msgid ""
"If you are using an FP32 based model, it can be converted to an int8 "
"model using `Intel® quantization tools`_."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:161
msgid "PyTorch single and multi-node benchmarks"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:163
msgid ""
"This section describes running the `PyTorch benchmarks`_ for Caffe2 in "
"single node."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:166
msgid ""
"Download either the `PyTorch with OpenBLAS`_ or the `PyTorch with Intel "
"MKL-DNN`_ Docker image from `Docker Hub`_."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:181
msgid "Clone the benchmark repository:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:197
msgid "Kubeflow multi-node benchmarks"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:199
msgid ""
"The benchmark workload runs in a Kubernetes cluster. The guide uses "
"`Kubeflow`_ for the Machine Learning workload deployment on three nodes."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:204
msgid ""
"If you choose the Intel® MKL-DNN or Intel® MKL-DNN-VNNI image, your "
"platform must support the Intel® AVX-512 instruction set. Otherwise, an "
"*illegal instruction* error may appear, and you won’t be able to complete"
" this guide."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:210
msgid "Kubernetes setup"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:212
msgid ""
"Follow the instructions in the :ref:`kubernetes` tutorial to get set up "
"on |CL|. The Kubernetes community also has instructions for creating a "
"cluster, described in `Creating a single control-plane cluster with "
"kubeadm`_."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:217
msgid "Kubernetes networking"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:219
msgid ""
"We used `flannel`_ as the network provider for these tests. If you prefer"
" a different network layer, refer to the Kubernetes network documentation"
" described in `Creating a single control-plane cluster with kubeadm`_ for"
" setup."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:224
msgid "Kubectl"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:226
msgid ""
"You can use kubectl to run commands against your Kubernetes cluster. "
"Refer to the `Overview of kubectl`_ for details on syntax and operations."
" Once you have a working cluster on Kubernetes, use the following YAML "
"script to start a pod with a simple shell script, and keep the pod open."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:231
msgid "Copy this example.yaml script to your system:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:248
msgid "Execute the script with kubectl:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:254
msgid ""
"This script opens a single pod. More robust solutions would create a "
"deployment or inject a python script or larger shell script into the "
"container."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:258
msgid "Images"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:260
msgid ""
"You must add `launcher.py`_ to the Docker image to include the Deep "
"Learning Reference Stack and put the benchmarks repo in the correct "
"location. Note that this guide uses Kubeflow v0.4.0, and cannot guarantee"
" results if you use a different version."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:264
msgid "From the Docker image, run the following:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:273
msgid "Your entry point becomes: :file:`/opt/launcher.py`."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:275
msgid "This builds an image that can be consumed directly by TFJob from Kubeflow."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:278
msgid "ksonnet\\*"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:280
msgid ""
"Kubeflow uses ksonnet\\* to manage deployments, so you must install it "
"before setting up Kubeflow."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:283
msgid ""
"ksonnet was added to the :command:`cloud-native-basic` bundle in |CL| "
"version 27550. If you are using an older |CL| version (not recommended), "
"you must manually install ksonnet as described below."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:287
msgid "On |CL|, follow these steps:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:298
msgid ""
"After the ksonnet installation is complete, ensure that binary `ks` is "
"accessible across the environment."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:302
msgid "Kubeflow"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:304
msgid ""
"Once you have Kubernetes running on your nodes, set up `Kubeflow`_ by "
"following these instructions from the `Getting Started with Kubeflow`_ "
"guide."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:322
msgid "Next, deploy the primary package for our purposes: tf-job-operator."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:332
msgid ""
"This creates the CustomResourceDefinition (CRD) endpoint to launch a "
"TFJob."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:335
msgid "Run a TFJob"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:337
msgid "Get the ksonnet registries for deploying TFJobs from `dlrs-tfjob`_."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:339
msgid "Install the TFJob components as follows:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:347
msgid "Export the image name to use for the deployment:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:355
msgid "Replace <docker_name> with the image name you specified in previous steps."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:357
msgid ""
"Generate Kubernetes manifests for the workloads and apply them using "
"these commands:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:367
msgid "This replicates and deploys three test setups in your Kubernetes cluster."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:370
msgid "Results of running this guide"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:372
msgid ""
"You must parse the logs of the Kubernetes pod to retrieve performance "
"data. The pods will still exist post-completion and will be in "
"‘Completed’ state. You can get the logs from any of the pods to inspect "
"the benchmark results. More information about Kubernetes logging is "
"available in the Kubernetes `Logging Architecture`_ documentation."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:379
msgid "Use Jupyter Notebook"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:381
msgid ""
"This example uses the `PyTorch with OpenBLAS`_ container image. After it "
"is downloaded, run the Docker image with :command:`-p` to specify the "
"shared port between the container and the host. This example uses port "
"8888."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:389
msgid ""
"After you start the container, launch the Jupyter Notebook. This command "
"is executed inside the container image."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:396
msgid ""
"After the notebook has loaded, you will see output similar to the "
"following:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:404
msgid ""
"From your host system, or any system that can access the host's IP "
"address, start a web browser with the following. If you are not running "
"the browser on the host system, replace :command:`127.0.0.1` with the IP "
"address of the host."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:412
msgid "Your browser displays the following:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:418
msgid "Figure 1: :guilabel:`Jupyter Notebook`"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:421
msgid ""
"To create a new notebook, click :guilabel:`New` and select "
":guilabel:`Python 3`."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:427
msgid "Figure 2: Create a new notebook"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:429
msgid "A new, blank notebook is displayed, with a cell ready for input."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:436
msgid ""
"To verify that PyTorch is working, copy the following snippet into the "
"blank cell, and run the cell."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:450
msgid "When you run the cell, your output will look something like this:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:456
msgid ""
"You can continue working in this notebook, or you can download existing "
"notebooks to take advantage of the Deep Learning Reference Stack's "
"optimized deep learning frameworks. Refer to `Jupyter Notebook`_ for "
"details."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:461
msgid "Uninstallation"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:463
msgid ""
"To uninstall the Deep Learning Reference Stack, you can choose to stop "
"the container so that it is not using system resources, or you can stop "
"the container and delete it to free storage space."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:467
msgid "To stop the container, execute the following from your host system:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:469
msgid "Find the container's ID"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:475
msgid "This will result in output similar to the following:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:482
msgid ""
"You can then use the ID or container name to stop the container. This "
"example uses the name \"oss\":"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:490
msgid "Verify that the container is not running"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:497
msgid "To delete the container from your system you need to know the Image ID:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:503
msgid "This command results in output similar to the following:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:511
msgid "To remove an image use the image ID:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:527
msgid ""
"Note that you can execute the :command:`docker rmi` command using only "
"the first few characters of the image ID, provided they are unique on the"
" system."
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:529
msgid "Once you have removed the image, you can verify it has been deleted with:"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:537
msgid "Related topics"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:539
msgid "`DLRS V3.0`_ release announcement"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:540
msgid "`TensorFlow Benchmarks`_"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:541
msgid "`PyTorch benchmarks`_"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:542
msgid "`Kubeflow`_"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:543
msgid ":ref:`kubernetes` tutorial"
msgstr ""
#: ../../guides/stacks/dlrs/dlrs.rst:544
msgid "`Jupyter Notebook`_"
msgstr ""

Some files were not shown because too many files have changed in this diff Show More