diff --git a/locale/de/LC_MESSAGES/FAQ/faq.mo b/locale/de/LC_MESSAGES/FAQ/faq.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/FAQ/faq.mo differ diff --git a/locale/de/LC_MESSAGES/FAQ/faq.po b/locale/de/LC_MESSAGES/FAQ/faq.po new file mode 100644 index 00000000..4ad15c47 --- /dev/null +++ b/locale/de/LC_MESSAGES/FAQ/faq.po @@ -0,0 +1,275 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../FAQ/faq.rst:4 +msgid "FAQ" +msgstr "" + +#: ../../FAQ/faq.rst:6 +msgid "" +"Below is a list of commonly asked questions with answers sourced from the" +" |CL-ATTR| team and `Clear Linux community forums`_." +msgstr "" + +#: ../../FAQ/faq.rst:14 +msgid "General" +msgstr "" + +#: ../../FAQ/faq.rst:17 +msgid "Why did you make another distro?" +msgstr "" + +#: ../../FAQ/faq.rst:19 +msgid "" +"The |CL| team felt that performance was left on the table with Linux " +"software. |CL| takes a holistic approach to improving performance across " +"the stack. We also wanted to take more modern approaches with OS updates " +"and tooling." +msgstr "" + +#: ../../FAQ/faq.rst:26 +msgid "Can other distros copy |CL| improvements?" +msgstr "" + +#: ../../FAQ/faq.rst:28 +msgid "Yes, we absolutely love open source reuse and upstreaming improvements." +msgstr "" + +#: ../../FAQ/faq.rst:33 +msgid "How often do you update?" +msgstr "" + +#: ../../FAQ/faq.rst:35 +msgid "" +"The |CL| team puts out multiple releases a week, often releasing 2 or " +"more times a day. This rolling release approach allows |CL| to remain " +"agile to upstream changes and security patches." +msgstr "" + +#: ../../FAQ/faq.rst:42 +msgid "Is telemetry required?" +msgstr "" + +#: ../../FAQ/faq.rst:44 +msgid "" +"The telemetry solution provided by |CL| is entirely optional and " +"customizable. It is disabled by default. If you do choose to enable " +"telemetry, the data helps the |CL| team proactively identify and resolve " +"bugs. See the :ref:`telemetry ` page for more " +"information." +msgstr "" + +#: ../../FAQ/faq.rst:52 +msgid "What is the default firewall?" +msgstr "" + +#: ../../FAQ/faq.rst:54 +msgid "" +"|CL| packages :command:`iptables` as a bundle, however, there are no " +"default firewall rules. All network traffic is allowed by default." +msgstr "" + +#: ../../FAQ/faq.rst:60 +msgid "Where are the files that I usually see under /etc like fstab?" +msgstr "" + +#: ../../FAQ/faq.rst:62 +msgid "" +"|CL| has a stateless design that maintains a separation between system " +"files and user files. Default values are stored under " +":file:`/usr/share/defaults/`. Files under :file:`/etc/` are not created " +"unless you create one." +msgstr "" + +#: ../../FAQ/faq.rst:66 +msgid "" +"A blog post explaining how this is accomplished with :file:`/etc/fstab/` " +"specifically is available here: https://clearlinux.org/news-blogs/where-" +"etcfstab-clear-linux" +msgstr "" + +#: ../../FAQ/faq.rst:73 +msgid "Software packages" +msgstr "" + +#: ../../FAQ/faq.rst:76 +msgid "How is software installed and updated?" +msgstr "" + +#: ../../FAQ/faq.rst:78 +msgid "" +"|CL| provides software in the form of :ref:`bundles ` and " +"updates software with :ref:`swupd `." +msgstr "" + +#: ../../FAQ/faq.rst:81 +msgid "" +":ref:`FlatPak\\* ` is an application virtualization solution " +"that allows more software to be available to |CL| users by augmenting the" +" software |CL| packages natively with software available through FlatPak." +msgstr "" + +#: ../../FAQ/faq.rst:85 +msgid "" +"Our goal is to have software packaged natively and made available through" +" bundles whenever possible." +msgstr "" + +#: ../../FAQ/faq.rst:91 +msgid "Does |CL| use RPMs like other distros?" +msgstr "" + +#: ../../FAQ/faq.rst:93 +msgid "" +"|CL| provides software in the form of :ref:`bundles `. The" +" RPM format is used as an intermediary step for packaging and determining" +" software dependencies at OS build time." +msgstr "" + +#: ../../FAQ/faq.rst:97 +msgid "" +"Individual RPMs can sometimes be manually installed on a |CL| system with" +" the right tools, but that is not the intended use case." +msgstr "" + +#: ../../FAQ/faq.rst:103 +msgid "Can I install a software package from another OS on |CL|?" +msgstr "" + +#: ../../FAQ/faq.rst:105 +msgid "" +"Software that is packaged in other formats for other Linux distributions " +"is not guaranteed to work on |CL| and may be impacted by |CL| updates." +msgstr "" + +#: ../../FAQ/faq.rst:108 +msgid "" +"If the software you're seeking is open source, please submit a request to" +" add it to |CL|. Submit requests on GitHub\\* here: " +"https://github.com/clearlinux/distribution/issues" +msgstr "" + +#: ../../FAQ/faq.rst:115 +msgid "Software availability" +msgstr "" + +#: ../../FAQ/faq.rst:118 +msgid "What software is available on |CL|?" +msgstr "" + +#: ../../FAQ/faq.rst:120 +msgid "" +"Available software can be found in the `Software Store`_, through the " +"GNOME\\* Software application on the desktop, or by using :ref:`swupd " +"search `." +msgstr "" + +#: ../../FAQ/faq.rst:126 +msgid "Is Google\\* Chrome\\* available?" +msgstr "" + +#: ../../FAQ/faq.rst:128 +msgid "" +"The Google Chrome web browser is not distributed as a bundle in |CL| due " +"to copyright and licensing complexities." +msgstr "" + +#: ../../FAQ/faq.rst:131 +msgid "" +"A discussion on manually installing and maintaining Google Chrome can be " +"found on GitHub: https://github.com/clearlinux/distribution/issues/422" +msgstr "" + +#: ../../FAQ/faq.rst:137 +msgid "Is FFmpeg available?" +msgstr "" + +#: ../../FAQ/faq.rst:139 +msgid "" +"`FFmpeg`_ is a multimedia software suite, which is commonly used for " +"various media encoding/decoding, streaming, and playback." +msgstr "" + +#: ../../FAQ/faq.rst:142 +msgid "" +"|CL| does not distribute FFmpeg due to well-known licensing and legal " +"complexities (See https://www.ffmpeg.org/legal.html and " +"http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html)." +msgstr "" + +#: ../../FAQ/faq.rst:146 +msgid "" +"Read more in the |CL| repository, including discussion of an alternative " +"hardware-based solution: " +"https://github.com/clearlinux/distribution/issues/429." +msgstr "" + +#: ../../FAQ/faq.rst:150 +msgid "" +"While |CL| cannot distribute FFmpeg, a manual solution to build and " +"install FFmpeg under :file:`/usr/local` has been shared on the community " +"forums: https://community.clearlinux.org/t/how-to-h264-etc-support-for-" +"firefox-including-ffmpeg-install." +msgstr "" + +#: ../../FAQ/faq.rst:157 +msgid "Is ZFS\\* available?" +msgstr "" + +#: ../../FAQ/faq.rst:159 +msgid "" +"ZFS is not available with |CL| because of copyright and licensing " +"complexities. BTRFS is an alternative filesystem that is available in " +"|CL| natively." +msgstr "" + +#: ../../FAQ/faq.rst:163 +msgid "" +"A user on GitHub notes that the ZFS kernel module can be compiled, built," +" and installed manually: " +"https://github.com/clearlinux/distribution/issues/631" +msgstr "" + +#: ../../FAQ/faq.rst:169 +msgid "Can you add a driver that I need?" +msgstr "" + +#: ../../FAQ/faq.rst:171 +msgid "" +"If a kernel module is available as part of the Linux kernel source tree " +"but not enabled in the |CL| kernels, in many cases the |CL| team will " +"enable it upon request. Submit requests on GitHub here: " +"https://github.com/clearlinux/distribution/issues" +msgstr "" + +#: ../../FAQ/faq.rst:176 +msgid "" +"The |CL| team does not typically add out-of-tree kernel modules as a " +"matter of practice because of the maintenance overhead. If the driver was" +" unable to be merged upstream, there is a good chance we may be unable to" +" merge it for similar reasons." +msgstr "" + +#: ../../FAQ/faq.rst:181 +msgid "" +"Kernel modules can be individually built and installed on |CL|. See the " +":ref:`kernel modules ` page for more information." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/concepts/autospec-about.mo b/locale/de/LC_MESSAGES/concepts/autospec-about.mo new file mode 100644 index 00000000..f911f469 Binary files /dev/null and b/locale/de/LC_MESSAGES/concepts/autospec-about.mo differ diff --git a/locale/de/LC_MESSAGES/concepts/autospec-about.po b/locale/de/LC_MESSAGES/concepts/autospec-about.po new file mode 100644 index 00000000..88dbf688 --- /dev/null +++ b/locale/de/LC_MESSAGES/concepts/autospec-about.po @@ -0,0 +1,223 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 `." +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 "" + diff --git a/locale/de/LC_MESSAGES/concepts/bundles-about.mo b/locale/de/LC_MESSAGES/concepts/bundles-about.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/concepts/bundles-about.mo differ diff --git a/locale/de/LC_MESSAGES/concepts/bundles-about.po b/locale/de/LC_MESSAGES/concepts/bundles-about.po new file mode 100644 index 00000000..48be697c --- /dev/null +++ b/locale/de/LC_MESSAGES/concepts/bundles-about.po @@ -0,0 +1,71 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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/bundles-about.rst:4 +msgid "Bundles" +msgstr "" + +#: ../../concepts/bundles-about.rst:6 +msgid "" +"Linux-based operating systems contain the code of several hundred, if not" +" thousands, of open source projects. To make this manageable, " +"distributions use a concept called \"packages\" to configure and compile " +"the source code of these projects into binaries." +msgstr "" + +#: ../../concepts/bundles-about.rst:11 +msgid "" +"Many distributions then split the content of these compiled packages into" +" so-called sub-packages, which are the granularity at which these " +"distributions deploy their software. With those kinds of distributions, " +"system administrators can then install and update sub-packages " +"individually or as a set, using tools such as \"yum\" and \"apt-get.\"" +msgstr "" + +#: ../../concepts/bundles-about.rst:17 +msgid "" +"The |CL-ATTR| takes a slightly different approach. While we also use the " +"concept of packages to manage compiling source code into binaries, we do " +"not use the package concept to deploy software. Instead, we provide " +"software \"bundles\" that are installed and managed using :ref:`swupd" +"`. Each bundle contains as many or as few open source " +"projects needed to provide a complete functionality." +msgstr "" + +#: ../../concepts/bundles-about.rst:24 +msgid "Next steps" +msgstr "" + +#: ../../concepts/bundles-about.rst:26 +msgid "To put this concept into practice, see the following resources:" +msgstr "" + +#: ../../concepts/bundles-about.rst:28 +msgid ":ref:`bundles`" +msgstr "" + +#: ../../concepts/bundles-about.rst:29 +msgid ":ref:`bundle-commands`" +msgstr "" + +#: ../../concepts/bundles-about.rst:30 +msgid ":ref:`compatible-kernels`" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/concepts/mixer-about.mo b/locale/de/LC_MESSAGES/concepts/mixer-about.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/concepts/mixer-about.mo differ diff --git a/locale/de/LC_MESSAGES/concepts/mixer-about.po b/locale/de/LC_MESSAGES/concepts/mixer-about.po new file mode 100644 index 00000000..58d238c7 --- /dev/null +++ b/locale/de/LC_MESSAGES/concepts/mixer-about.po @@ -0,0 +1,115 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" + diff --git a/locale/de/LC_MESSAGES/concepts/restart.mo b/locale/de/LC_MESSAGES/concepts/restart.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/concepts/restart.mo differ diff --git a/locale/de/LC_MESSAGES/concepts/restart.po b/locale/de/LC_MESSAGES/concepts/restart.po new file mode 100644 index 00000000..afb3649d --- /dev/null +++ b/locale/de/LC_MESSAGES/concepts/restart.po @@ -0,0 +1,301 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" + diff --git a/locale/de/LC_MESSAGES/concepts/security.mo b/locale/de/LC_MESSAGES/concepts/security.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/concepts/security.mo differ diff --git a/locale/de/LC_MESSAGES/concepts/security.po b/locale/de/LC_MESSAGES/concepts/security.po new file mode 100644 index 00000000..87326a37 --- /dev/null +++ b/locale/de/LC_MESSAGES/concepts/security.po @@ -0,0 +1,249 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" + diff --git a/locale/de/LC_MESSAGES/concepts/stateless.mo b/locale/de/LC_MESSAGES/concepts/stateless.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/concepts/stateless.mo differ diff --git a/locale/de/LC_MESSAGES/concepts/stateless.po b/locale/de/LC_MESSAGES/concepts/stateless.po new file mode 100644 index 00000000..976be398 --- /dev/null +++ b/locale/de/LC_MESSAGES/concepts/stateless.po @@ -0,0 +1,202 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 `.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? `_" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/concepts/swupd-about.mo b/locale/de/LC_MESSAGES/concepts/swupd-about.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/concepts/swupd-about.mo differ diff --git a/locale/de/LC_MESSAGES/concepts/swupd-about.po b/locale/de/LC_MESSAGES/concepts/swupd-about.po new file mode 100644 index 00000000..0624a47a --- /dev/null +++ b/locale/de/LC_MESSAGES/concepts/swupd-about.po @@ -0,0 +1,193 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 `." +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 ` 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 ` 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 "" + diff --git a/locale/de/LC_MESSAGES/concepts/telemetry-about.mo b/locale/de/LC_MESSAGES/concepts/telemetry-about.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/concepts/telemetry-about.mo differ diff --git a/locale/de/LC_MESSAGES/concepts/telemetry-about.po b/locale/de/LC_MESSAGES/concepts/telemetry-about.po new file mode 100644 index 00000000..f5ba1195 --- /dev/null +++ b/locale/de/LC_MESSAGES/concepts/telemetry-about.po @@ -0,0 +1,176 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" + diff --git a/locale/de/LC_MESSAGES/disclaimers.mo b/locale/de/LC_MESSAGES/disclaimers.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/disclaimers.mo differ diff --git a/locale/de/LC_MESSAGES/disclaimers.po b/locale/de/LC_MESSAGES/disclaimers.po new file mode 100644 index 00000000..46d60de2 --- /dev/null +++ b/locale/de/LC_MESSAGES/disclaimers.po @@ -0,0 +1,32 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" + diff --git a/locale/de/LC_MESSAGES/documentation_license.mo b/locale/de/LC_MESSAGES/documentation_license.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/documentation_license.mo differ diff --git a/locale/de/LC_MESSAGES/documentation_license.po b/locale/de/LC_MESSAGES/documentation_license.po new file mode 100644 index 00000000..cfdc38ce --- /dev/null +++ b/locale/de/LC_MESSAGES/documentation_license.po @@ -0,0 +1,20 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + diff --git a/locale/de/LC_MESSAGES/get-started/bare-metal-install-desktop/bare-metal-install-desktop.mo b/locale/de/LC_MESSAGES/get-started/bare-metal-install-desktop/bare-metal-install-desktop.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/get-started/bare-metal-install-desktop/bare-metal-install-desktop.mo differ diff --git a/locale/de/LC_MESSAGES/get-started/bare-metal-install-desktop/bare-metal-install-desktop.po b/locale/de/LC_MESSAGES/get-started/bare-metal-install-desktop/bare-metal-install-desktop.po new file mode 100644 index 00000000..41244d23 --- /dev/null +++ b/locale/de/LC_MESSAGES/get-started/bare-metal-install-desktop/bare-metal-install-desktop.po @@ -0,0 +1,745 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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/bare-metal-install-desktop/bare-metal-install-desktop.rst:4 +msgid "Install |CL-ATTR| from the live desktop" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:6 +msgid "" +"The live desktop allows you to boot |CL-ATTR| in a GNOME desktop without " +"modifying the host system, offering the chance to explore developing on " +"|CL|. Better yet, launch the |CL| installer to install on your target " +"system." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:15 +msgid "System requirements" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:17 +msgid "Assure that your target system supports the installation:" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:19 +msgid ":ref:`system-requirements`" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:20 +msgid ":ref:`compatibility-check`" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:23 +msgid "Preliminary steps" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:25 +msgid "`Visit our Downloads page`_." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:27 +msgid "Download the file :file:`clear--live-desktop.iso`" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:31 +msgid " is the latest |CL| auto-numbered release." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:33 +msgid "Follow your OS instructions to create a bootable USB drive." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:35 +msgid ":ref:`bootable-usb`" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:40 +msgid "Install from live image" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:42 +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:45 +msgid "Insert the USB drive into an available USB slot." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:47 +msgid "Power on the system." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:49 +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:52 +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:55 +msgid "Save these settings, e.g. :kbd:`F10`, and exit." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:57 +msgid "Reboot the target system." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:59 +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:65 +msgid "Figure 1: Clear Linux OS in boot menu" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:70 +msgid "Confirm network connection" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:72 +msgid "" +"Confirm there is a network connection before launching the installer. " +"Choose a method: `Wired Connection`, or `WiFi Connected`. This guide " +"shows an example of a **Wired Connection**." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:76 +msgid "" +"In the upper right of the top menu bar, select the square icon to view " +"Network settings, shown in Figure 2." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:79 +msgid "Select :guilabel:`Wired Connected` and then :guilabel:`Wired Settings`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:85 +msgid "Figure 2: Software icon, Network settings" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:87 +msgid "" +"View the :guilabel:`Wired` menu to assure that you're target system and " +"installer are connected to a network." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:90 +msgid "Optional: Configure Proxy settings." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:92 +msgid "To view :guilabel:`Network Proxy`, select its :guilabel:`Gear` icon." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:94 +msgid "Select from `Automatic`, `Manual` or `Disabled` as desired." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:96 +msgid "Close the dialogue box." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:98 +msgid "Select the :guilabel:`Gear` icon to view Network settings." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:100 +msgid "" +"If desired, select :guilabel:`Connect automatically`. Select other " +"options as desired." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:103 +msgid "Select :guilabel:`Apply` button to confirm change to settings." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:106 +msgid "Software" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:108 +msgid "" +"Optional: Explore |CL| bundles and other software available. Double-click" +" the :guilabel:`Software` icon from the Activities menu, shown in Figure " +"2." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:112 +msgid "" +"`Sofware` application is *only intended for exploring* available bundles," +" applications, and images. Do not attempt to install them." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:115 +msgid "Assure there is a network connection before launching `Software`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:118 +msgid "Launch the |CL| installer" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:120 +msgid "" +"After the live desktop image boots, find the |CL| icon in the " +":guilabel:`Activities` menu at left, shown in Figure 3." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:123 +msgid "Click the icon, :guilabel:`Install Clear Linux OS`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:129 +msgid "Figure 3: Install Clear Linux OS icon" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:131 +msgid "The installer is launched, as shown in Figure 4." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:137 +msgid "Figure 4: |CL| OS Desktop Installer" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:139 +msgid "" +"In :guilabel:`Select Language`, select a language from the options, or " +"type your preferred language in the search bar." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:142 +msgid "Select :guilabel:`Next`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:148 +msgid "Minimum installation requirements" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:150 +msgid "" +"To fulfill minimum installation requirements, complete the `Required " +"options`_. We also recommend completing `Advanced options`_." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:155 +msgid "" +"The :kbd:`Install` button is only highlighted **after** you complete " +"`Required options`_." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:158 +msgid "Checkmarks indicate a selection has been made." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:160 +msgid "" +"An Internet connection is required. You may want to launch a browser " +"prior to installation to verify your Internet connection." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:164 +msgid "|CL| Desktop Installer" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:166 +msgid "" +"The |CL| Desktop Installer Main Menu appears as shown in Figure 5. To " +"meet the minimum requirements, enter values in all submenus for the " +":guilabel:`Required options`. After you complete them, your selections " +"appear below submenus and a checkmark appears at right." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:175 +msgid "Figure 5: Clear Linux OS Desktop Installer - Main Menu" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:178 +msgid "Navigation" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:180 +msgid "Use the :kbd:`mouse` to navigate or select options." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:182 +msgid "" +"Use :kbd:`Tab` key to navigate between :guilabel:`Required options` and " +":guilabel:`Advanced options`" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:185 +msgid "Use :kbd:`Up` or :kbd:`Down` arrow keys to navigate submenu list." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:187 +msgid "Select :kbd:`Confirm`, or :kbd:`Cancel` in submenus." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:190 +msgid "Required options" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:193 +msgid "Select Time Zone" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:195 +msgid "" +"From the Main Menu, select :guilabel:`Select Time Zone`. `UTC` is " +"selected by default." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:198 +msgid "" +"In :guilabel:`Select Time Zone`, navigate to the desired time zone. Or " +"start typing the region and then city. (.e.g., " +":file:`America/Los_Angeles`)." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:202 +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:218 +msgid "Select :guilabel:`Confirm`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:208 +msgid "Figure 6: Select System Time Zone" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:211 +msgid "Select Keyboard" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:213 +msgid "From the Main Menu, select :guilabel:`Select Keyboard`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:215 +msgid "" +"Navigate to your desired keyboard layout. We select \"us\" for the United" +" States." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:224 +msgid "Figure 7: Select Keyboard menu" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:227 +msgid "Select Installation Media" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:229 +msgid "From the Main Menu, select :guilabel:`Select Installation Media`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:231 +msgid "" +"Choose an installation method: `Safe Installation`_ or `Destructive " +"Installation`_." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:238 +msgid "Figure 8: Select Installation Media" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:241 +msgid "Safe Installation" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:242 +msgid "" +"Use this method to safely install |CL| on media with available space, or " +"alongside existing partitions, and accept the `Default partition " +"schema`_. If enough free space exists, safe installation is allowed." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:248 +msgid "" +"|CL| allows installation alongside another OS. Typically, when you boot " +"your system, you can press an `F key` to view and select a bootable " +"device or partition during the BIOS POST stage. Some BIOSes present the " +"|CL| partition, and you can select and boot it. However, other BIOSes may" +" only show the primary partition, in which case you will not be able boot" +" |CL|. Be aware of this possible limitation." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:257 +msgid "Destructive Installation" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:259 +msgid "" +"Use this method to destroy the contents of the target device, install " +"|CL| on it, and accept the `Default partition schema`_." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:262 +msgid "Disk encryption" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:264 +msgid "" +"For greater security, disk encryption is supported using LUKS. Encryption" +" is optional." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:267 +msgid "" +"To encrypt the root partition, select :guilabel:`Enable Encryption`, as " +"shown in Figure 9." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:274 +msgid "Figure 9: Enable Encryption" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:276 +msgid "When :guilabel:`Encryption Passphrase` appears, enter a passphrase." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:282 +msgid "Figure 10: Encryption Passphrase" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:286 +msgid "Minimum length is 8 characters. Maximum length is 94 characters." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:288 +msgid "Enter the same passphrase in the second field." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:290 +msgid "Select :guilabel:`Confirm` in the dialogue box." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:294 +msgid ":guilabel:`Confirm` is only highlighted if passphrases match." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:296 +msgid "Select :guilabel:`Confirm` in submenu." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:299 +msgid "Manage User" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:301 +msgid "In Required Options, select :guilabel:`Manage User`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:303 +msgid "In :guilabel:`User Name`, enter a user name." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:309 +msgid "Figure 11: Manage User" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:311 +msgid "" +"In :guilabel:`Login`, create a login name. It must start with a letter " +"and can use numbers, hyphens, and underscores. Maximum length is 31 " +"characters." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:315 +msgid "" +"In :guilabel:`Password`, enter a password. Minimum length is 8 " +"characters. Maximum length is 255 characters." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:318 +msgid "In :guilabel:`Confirm`, enter the same password." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:322 +msgid "" +":guilabel:`Administrator` rights are selected by default. For security " +"purposes, the default user must be assigned as an Administrator." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:326 +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:394 +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:427 +msgid "Select :kbd:`Confirm`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:330 +msgid "Select :guilabel:`Cancel` to return to the Main Menu." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:333 +msgid "Modify User" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:335 +msgid "In Manager User, select :guilabel:`Manage User`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:337 +msgid "Modify user details as desired." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:339 +msgid "Select :guilabel:`Confirm` to save the changes you made." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:343 +msgid "" +"Optional: Select :guilabel:`Cancel` to return to the Main Menu to revert " +"changes." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:346 +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:404 +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:429 +msgid "Optional: Skip to `Finish installation`_." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:349 +msgid "Telemetry" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:351 +msgid "" +"Choose whether to participate in `telemetry`. :ref:`telem-guide` is a " +"|CL| feature that reports failures and crashes to the |CL| development " +"team for improvements. For more information, see :ref:`telemetry-about`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:355 +msgid "From :guilabel:`Required Options`, select :guilabel:`Telemetry`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:357 +msgid "Select :kbd:`Yes`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:363 +msgid "Figure 12: Enable Telemetry" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:365 +msgid "If you don't wish to participate, select :kbd:`No`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:368 +msgid "Advanced options" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:370 +msgid "" +"After you complete the `Required options`_, we recommend completing " +":guilabel:`Advanced options`--though they're not required. Doing so " +"customizes your development environment, so you're ready to go " +"immediately after reboot." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:375 +msgid "`Bundle Selection`_" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:377 +msgid "`Assign Hostname`_" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:379 +msgid "As for bundles, you can always add more later with :ref:`swupd-guide`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:382 +msgid "Bundle Selection" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:384 +msgid "On the Advanced menu, select :guilabel:`Bundle Selection`" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:386 +msgid "Select your desired bundles." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:392 +msgid "Figure 13: Bundle Selection" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:396 +msgid "View the bundles that you selected." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:402 +msgid "Figure 14: Bundle Selections - Advanced Options" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:407 +msgid "Assign Hostname" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:409 +msgid "In Advanced Options, select :guilabel:`Assign Hostname`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:411 +msgid "In :guilabel:`Hostname`, enter the hostname only (excluding the domain)." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:417 +msgid "Figure 15: Assign Hostname" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:421 +msgid "" +"Hostname does not allow empty spaces. Hostname must start with an " +"alphanumeric character but may also contain hyphens. Maximum length of 63" +" characters." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:425 +msgid "Navigate to :kbd:`Confirm` until highlighted." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:432 +msgid "Finish installation" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:434 +msgid "" +"When you are satisfied with your installation configuration, select " +":guilabel:`Install`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:441 +msgid "Figure 16: Finish installation" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:447 +msgid "" +"If you do not enter a selection for all :guilabel:`Required Options`, the" +" :guilabel:`Install` button remains greyed out, as shown in Figure 17. " +"Return to `Required Options`_ and make selections." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:456 +msgid "Figure 17: Required Options - Incomplete" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:458 +msgid "After installation is complete, select :guilabel:`Exit`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:460 +msgid "Shut down the target system." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:462 +msgid "Remove the USB or any installation media." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:464 +msgid "Power on your system." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:468 +msgid "" +"Allow time for the graphical login to appear. A login prompt shows the " +"administrative user that you created." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:470 +msgid "Log in as the adminstrative user." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:472 +msgid "Congratulations. You successfully installed |CL|." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:475 +msgid "Default partition schema" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:477 +msgid "" +"Table 1 shows the defult partition schema with the exception of root, " +"which varies." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:480 +msgid "**Table 1. Disk Partition Setup**" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:484 +msgid "FileSystem" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:485 +msgid "Mount Point" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:486 +msgid "Minimum size" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:487 +msgid "``VFAT``" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:488 +msgid "/boot" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:489 +msgid "150M" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:490 +msgid "``swap``" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:492 +msgid "256MB" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:493 +msgid "``root``" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:494 +msgid "/" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:495 +msgid "*Size depends upon use case/desired bundles.*" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:498 +msgid "Next steps" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:500 +msgid ":ref:`guides`" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/get-started/bare-metal-install-server/bare-metal-install-server.mo b/locale/de/LC_MESSAGES/get-started/bare-metal-install-server/bare-metal-install-server.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/get-started/bare-metal-install-server/bare-metal-install-server.mo differ diff --git a/locale/de/LC_MESSAGES/get-started/bare-metal-install-server/bare-metal-install-server.po b/locale/de/LC_MESSAGES/get-started/bare-metal-install-server/bare-metal-install-server.po new file mode 100644 index 00000000..65d7c961 --- /dev/null +++ b/locale/de/LC_MESSAGES/get-started/bare-metal-install-server/bare-metal-install-server.po @@ -0,0 +1,1237 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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/bare-metal-install-server/bare-metal-install-server.rst:4 +msgid "Install |CL-ATTR| on bare metal with live server" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:6 +msgid "" +"These instructions guide you through installing |CL-ATTR| on bare metal " +"from a bootable USB drive using a live server image." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:13 +msgid "System requirements" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:15 +msgid "Assure that your target system supports the installation:" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:17 +msgid ":ref:`system-requirements`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:18 +msgid ":ref:`compatibility-check`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:21 +msgid "Download the latest |CL| live server image" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:23 +msgid "" +"Get the latest |CL| installer image from the `downloads page`_. Look for " +"the :file:`clear-[version number]-live-server.iso` file." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:26 +msgid "Follow your OS instructions to create a bootable USB drive." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:28 +msgid ":ref:`bootable-usb`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:30 +msgid "After downloading the image, verify and decompress the file per your OS." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:33 +msgid "Install |CL| on your target system" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:35 +msgid "" +"Ensure that your system is configured to boot UEFI. The installation " +"method described below requires a wired Internet connection with DHCP." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:40 +msgid "" +"Alternatively, you can install |CL| over a wireless connection by first " +"using `nmtui`. Follow the `nmtui` instructions shown in Figure 2." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:43 +msgid "Follow these steps to install |CL| on the target system:" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:45 +msgid "Insert the USB drive into an available USB slot." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:47 +msgid "Power on the system." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:49 +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-server/bare-metal-install-server.rst:53 +msgid "" +"|CL| supports UEFI boot. Some hardware may list UEFI and non-UEFI USB " +"boot entries. In this case, you should select the `UEFI` boot option." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:57 +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-server/bare-metal-install-server.rst:60 +msgid "Save these settings and exit." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:62 +msgid "Reboot the target system." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:64 +msgid "This action launches the |CL| installer boot menu, shown in figure 1." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:70 +msgid "Figure 1: Clear Linux OS Installer boot menu" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:72 +msgid "With :guilabel:`Clear Linux OS` highlighted, select :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:75 +msgid "Launch the |CL| Installer" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:77 +msgid "At the :guilabel:`login` prompt, enter :command:`root`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:79 +msgid "" +"Follow the onscreen instructions, shown in Figure 2, and enter a " +"temporary password." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:86 +msgid "Figure 2: root login" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:88 +msgid "" +"At the :guilabel:`root` prompt, enter :command:`clr-installer` and press " +":kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:95 +msgid "Figure 3: clr-installer command" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:98 +msgid "Minimum installation requirements" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:100 +msgid "" +"To fulfill minimum installation requirements, complete the `Required " +"options`_. While not required, we encourage you to apply the `Recommended" +" options`_. `Advanced options`_ are optional." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:106 +msgid "" +"The :kbd:`Install` button is **only highlighted after** you complete " +"`Required options`_." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:110 +msgid "Main Menu" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:111 +msgid "The |CL| Installer Main Menu appears as shown in Figure 4." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:117 +msgid "Figure 4: Clear Linux OS Installer" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:119 +msgid "" +"The |CL| Installer Main Menu has two tabs: :guilabel:`[R] Required " +"options` and :guilabel:`[A] Advanced options`. Navigate between tabs " +"using the arrow these shortcut keys:" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:123 +msgid ":kbd:`Shift+A` for :guilabel:`[A] Advanced options`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:124 +msgid ":kbd:`Shift+R` for :guilabel:`[R] Required options`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:126 +msgid "" +"To meet the minimum requirements, enter your choices in the " +":guilabel:`Required options`. After confirmation, your selections appear " +"beside the :guilabel:`>>` chevron, below the menu options." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:131 +msgid "Navigation" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:133 +msgid "Select :kbd:`Tab` or :kbd:`Up/Down` arrows to highlight your choice." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:135 +msgid "Select :kbd:`Enter` or :kbd:`Spacebar` to confirm your choice." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:137 +msgid "Select :kbd:`Cancel` or :kbd:`Esc` to cancel your choice." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:140 +msgid "Required options" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:143 +msgid "Choose Timezone" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:145 +msgid "" +"From the Main Menu, navigate to :guilabel:`Choose Timezone`. `UTC` is the" +" default." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:148 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:168 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:185 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:677 +msgid "Select :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:150 +msgid "" +"In :guilabel:`Select System Timezone`, use :kbd:`Up/Down` arrows navigate" +" to the desired timezone." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:155 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:172 +msgid "Press :kbd:`Enter` to confirm." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:161 +msgid "Figure 5: Select System Timezone" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:164 +msgid "Choose Language" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:166 +msgid "From the Main Menu, navigate to :guilabel:`Choose Language`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:170 +msgid "In :guilabel:`Select System Language`, navigate to your desired language." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:178 +msgid "Figure 6: Select System Language" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:181 +msgid "Configure the Keyboard" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:183 +msgid "From the Main Menu, select :guilabel:`Configure the Keyboard`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:187 +msgid "In :guilabel:`Select Keyboard`, navigate to the desired option." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:189 +msgid "Select :kbd:`Enter` to :kbd:`Confirm`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:191 +msgid "" +"Optional: In :guilabel:`Test keyboard`, type text to assure that the keys" +" map to your keyboard." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:198 +msgid "Figure 7: Select Keyboard menu" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:201 +msgid "Configure Installation Media" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:203 +msgid "From the Main Menu, select :guilabel:`Configure Installation Media`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:205 +msgid "" +"Choose an installation method: * `Safe Installation`_ * `Destructive " +"Installation`_ * `Advanced Configuration`_" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:215 +msgid "Figure 8: Select Installation Media" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:217 +msgid "Select :guilabel:`Rescan Media` to show available installation targets." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:222 +msgid "Safe Installation" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:224 +msgid "" +"Use this method to safely install |CL| on media with available space, or " +"alongside existing partitions, and accept the `Default partition " +"schema`_. If enough free space exists, safe installation is allowed. See " +"also `Troubleshooting`_ below." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:230 +msgid "Destructive Installation" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:232 +msgid "" +"Use this method to destroy the contents of the target device, install " +"|CL| on it, and accept the `Default partition schema`_." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:237 +msgid "" +"From the :guilabel:`Select Installation Media` menu, select " +":guilabel:`Enable Encryption` to encrypt the root filesystem for either " +"option above. See also `Disk encryption`_ for more information." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:242 +msgid "Advanced Configuration" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:244 +msgid "" +"Use this method to manually configure partitions. These must meet " +"`Default partition schema`_. You may also choose `Disk encryption`_ " +"during configuration of each partition." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:250 +msgid "" +"`Advanced Configuration` is available in the installer versions 1.2.0 and" +" above." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:253 +msgid "" +"From :guilabel:`Select Installation Media`, shown in Figure 8 above, " +"select :guilabel:`Advanced Configuration`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:256 +msgid "" +"In :guilabel:`Advanced Configuration`, navigate to :file:`/dev/sda` and " +"then press :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:263 +msgid "Figure 9: Advanced configuration menu" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:265 +msgid "Choose a partition method:" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:267 +msgid "" +":guilabel:`Auto Partition` Select this option to accept the `Default " +"partition schema`_." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:270 +msgid "Navigate to and press :guilabel:`Confirm`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:272 +msgid "Continue with installation configuration. Jump to `Telemetry`_." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:274 +msgid "`Manual Partition`_ Continue below." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:277 +msgid "Manual Partition" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:279 +msgid "We provide a simple example below." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:281 +msgid "" +"Navigate to the unallocated media (e.g.,`/dev/sda`) until highlighted, as" +" shown in Figure 9." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:284 +msgid "Press :guilabel:`Enter` to edit the partition." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:286 +msgid "The :guilabel:`Partition Setup` menu appears, shown in Figure 10." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:290 +msgid "" +"After adding the first partition, select :guilabel:`Free Space` to add " +"another partition." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:293 +msgid "root partition" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:295 +msgid "" +"We configure the `root` partition as shown in Figure 10. Configuration of" +" the `root` partition varies." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:302 +msgid "Figure 10: root partition" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:304 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:317 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:331 +msgid "Navigate to :guilabel:`Add` and press :guilabel:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:307 +msgid "boot partition" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:309 +msgid "We configure the `boot` partition as shown in Figure 11." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:315 +msgid "Figure 11: boot partition" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:320 +msgid "swap partition" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:322 +msgid "" +"In the :guilabel:`File System` pulldown menu, select `swap`, and enter a " +"label. We enter the minimum required size (e.g., 256M)." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:329 +msgid "Figure 12: swap partition" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:333 +msgid "" +"Next, navigate to :guilabel:`Confirm` and press :guilabel:`Enter`, shown " +"in Figure 13." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:336 +msgid "Manual partitioning is complete." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:342 +msgid "Figure 13: Final configuration of disk partitions" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:344 +msgid "You may skip to the `Telemetry`_ section below." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:347 +msgid "Disk encryption" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:349 +msgid "" +"For greater security, disk encryption is supported using LUKS for the any" +" partition except `/boot` on |CL|. To encrypt the root partition, see the" +" example below. Encryption is optional." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:354 +msgid "Encryption Passphrase" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:356 +msgid "" +"|CL| uses a single passphrase for encrypted partitions. Additional keys " +"may be configured post-installation using the ``cryptsetup`` tool." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:359 +msgid "" +"Optional: Select :guilabel:`[X] Encrypt` to encrypt the root partition, " +"as shown in Figure 14." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:366 +msgid "Figure 14: Encrypt partition" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:368 +msgid "The :guilabel:`Encryption Passphrase` dialogue appears." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:372 +msgid "Minimum length is 8 characters. Maximum length is 94 characters." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:378 +msgid "Figure 15: Encryption Passphrase" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:380 +msgid "Enter the same passphrase in the first and second field." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:382 +msgid "Navigate to :guilabel:`Confirm` and press :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:386 +msgid ":guilabel:`Confirm` is only highlighted if passphrases match." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:389 +msgid "Telemetry" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:391 +msgid "" +":ref:`telem-guide` is a |CL| feature that reports failures and crashes to" +" the |CL| development team for improvements. For more detailed " +"information, visit our :ref:`telemetry-about` page." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:395 +msgid "Select your desired option on whether to participate in `telemetry`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:397 +msgid "" +"In the Main Menu, navigate to :guilabel:`Telemetry` and select " +":kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:400 +msgid "Select :kbd:`Tab` to highlight your choice." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:402 +msgid "Select :kbd:`Enter` to confirm." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:408 +msgid "Figure 16: Enable Telemetry" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:411 +msgid "Recommended options" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:413 +msgid "" +"After you complete the `Required options`_, we highly recommend " +"completing these selected `Advanced options`_ at minimum:" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:416 +msgid "`Manage User`_ Assign a new user with administrative rights" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:417 +msgid "`Assign Hostname`_ Simplify your development environment" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:420 +msgid "Skip to finish installation" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:422 +msgid "" +"After selecting values for all :guilabel:`Required options`, you may skip" +" to `Finish installation`_." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:425 +msgid "" +"Otherwise, continue below. In the Main Menu, select :guilabel:`Advanced " +"options` for additional configuration." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:429 +msgid "Advanced options" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:432 +msgid "Configure Network Interfaces" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:434 +msgid "" +"By default, |CL| is configured to automatically detect the host network " +"interface using DHCP. However, if you want to use a static IP address or " +"if you do not have a DHCP server on your network, follow these " +"instructions to manually configure the network interface. Otherwise, " +"default network interface settings are automatically applied." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:442 +msgid "If DHCP is available, no user selection may be required." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:444 +msgid "" +"Navigate to :guilabel:`Configure Network Interfaces` and select " +":kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:447 +msgid "Navigate to the network :guilabel:`interface` you wish to change." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:449 +msgid "" +"When the desired :guilabel:`interface` is highlighted, select " +":guilabel:`Enter` to edit." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:452 +msgid "Multiple network interfaces may appear." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:458 +msgid "Figure 17: Configure Network Interfaces" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:460 +msgid "Notice :guilabel:`Automatic / dhcp` is selected by default (at bottom)." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:462 +msgid "" +"Optional: Navigate to the checkbox :guilabel:`Automatic / dhcp` and " +"select :kbd:`Spacebar` to deselect." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:469 +msgid "Figure 18: Network interface configuration" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:471 +msgid "" +"Navigate to the appropriate fields and assign the desired network " +"configuration." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:474 +msgid "To save settings, navigate to :guilabel:`Confirm` and select :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:479 +msgid "" +"To revert to previous settings, navigate to the :guilabel:`Cancel` and " +"select :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:482 +msgid "" +"Upon confirming network configuration, the :guilabel:`Testing Networking`" +" dialogue appears. Assure the result shows success. If a failure occurs, " +"your changes will not be saved." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:486 +msgid "" +"Upon confirmation, you are returned to :guilabel:`Network interface` " +"settings." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:489 +msgid "Navigate to and select :guilabel:`Main Menu`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:491 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:519 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:540 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:564 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:664 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:694 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:714 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:733 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:758 +msgid "Optional: Skip to `Finish installation`_." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:494 +msgid "Proxy" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:496 +msgid "" +"|CL| automatically attempts to detect proxy settings, as described in " +"`Autoproxy`_. If you need to manually assign proxy settings, follow this " +"instruction." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:500 +msgid "" +"From the Advanced options menu, navigate to :guilabel:`Proxy`, and select" +" :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:503 +msgid "Navigate to the field :guilabel:`HTTPS Proxy`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:509 +msgid "Figure 19: Configure the network proxy" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:511 +msgid "" +"Enter the desired proxy address and port using conventional syntax, such " +"as: \\http://address:port." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:514 +msgid "Navigate to :guilabel:`Confirm` and select :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:516 +msgid "" +"To revert to previous settings, navigate to :guilabel:`Cancel` and select" +" :guilabel:`Cancel`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:522 +msgid "Test Network Settings" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:524 +msgid "" +"To manually assure network connectivity before installing |CL|, select " +":guilabel:`Test Network Settings` and select :guilabel:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:527 +msgid "A progress bar appears as shown in Figure 20." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:533 +msgid "Figure 20: Testing Networking dialogue" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:537 +msgid "" +"Any changes made to network settings are automatically tested during " +"configuration." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:543 +msgid "Bundle Selection" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:545 +msgid "On the Advanced menu, select :guilabel:`Bundle Selection`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:547 +msgid "Navigate to the desired bundle using :kbd:`Tab` or :kbd:`Up/Down` arrows." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:549 +msgid "Select :kbd:`Spacebar` to select the checkbox for each desired bundle." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:555 +msgid "Figure 21: Bundle Selection" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:557 +msgid "" +"Optional: To start developing with |CL|, we recommend adding :file:`os-" +"clr-on-clr`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:560 +msgid "Navigate to and select :kbd:`Confirm`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:562 +msgid "You are returned to the :guilabel:`Advanced options` menu." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:567 +msgid "Manage User" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:570 +msgid "Add New User" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:572 +msgid "In Advanced Options, select :guilabel:`Manage User`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:574 +msgid "Select :guilabel:`Add New User` as shown in Figure 22." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:580 +msgid "Figure 22: Add New User" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:582 +msgid "Optional: Enter a :guilabel:`User Name`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:592 +msgid "Figure 23: User Name" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:594 +msgid "Enter a :guilabel:`Login`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:598 +msgid "" +"The User Login must be alphanumeric and can include hyphens and " +"underscores. Maximum length is 31 characters." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:600 +msgid "Enter a :guilabel:`Password`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:606 +msgid "In :guilabel:`Confirm`, enter the same password." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:608 +msgid "" +"Optional: Navigate to the :guilabel:`Administrative` checkbox and select " +":kbd:`Spacebar` to assign administrative rights to the user." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:613 +msgid "Selecting this option enables sudo privileges for the user." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:615 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:692 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:725 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:756 +msgid "Select :kbd:`Confirm`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:619 +msgid "If desired, select :guilabel:`Reset` to reset the form." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:621 +msgid "In :guilabel:`Manage User`, navigate to :guilabel:`Confirm`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:623 +msgid "With :guilabel:`Confirm` highlighted, select :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:626 +msgid "Modify / Delete User" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:628 +msgid "" +"In :guilabel:`Manage User`, navigate to the user you wish to modify until" +" highlighted, as shown in Figure 24." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:631 +msgid "Select :kbd:`Enter` to modify the user." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:637 +msgid "Figure 24: Modify User" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:639 +msgid "Modify user details as desired." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:641 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:660 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:754 +msgid "Navigate to :kbd:`Confirm` until highlighted." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:645 +msgid "Optional: Select :guilabel:`Reset` to rest the form." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:647 +msgid "Select :guilabel:`Confirm` to save the changes you made." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:649 +msgid "" +"Optional: In :guilabel:`Modify User`, to delete the user, navigate to the" +" :guilabel:`Delete` button and select :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:656 +msgid "Figure 25: Delete User" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:658 +msgid "You are returned to :guilabel:`Manage User`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:662 +msgid "Select :guilabel:`Enter` to complete :guilabel:`Manage User` options." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:667 +msgid "Kernel Command Line" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:669 +msgid "" +"For advanced users, |CL| provides the ability to add or remove kernel " +"arguments. If you want to append a new argument, enter the argument here." +" This argument will be used every time you install or update a new " +"kernel." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:674 +msgid "" +"In Advanced Options, select :guilabel:`Tab` to highlight " +":guilabel:`Kernel Command Line`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:683 +msgid "Figure 26: kernel command line" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:685 +msgid "Choose from the following options." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:687 +msgid "To add arguments, enter the argument in :guilabel:`Add Extra Arguments`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:689 +msgid "To remove an argument, enter the argument in :guilabel:`Remove Arguments`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:697 +msgid "Kernel Selection" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:699 +msgid "" +"Select a kernel option. By default, the latest kernel release is " +"selected. Native kernel is shown in Figure 27." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:702 +msgid "To select a different kernel, navigate to it using :guilabel:`Tab`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:708 +msgid "Figure 27: Kernel selection" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:710 +msgid "Select :kbd:`Spacebar` to select the desired option." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:712 +msgid "Navigate to :kbd:`Confirm` and select :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:717 +msgid "Swupd Mirror" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:719 +msgid "If you have your own custom mirror of |CL|, you can add its URL." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:721 +msgid "In Advanced Options, select :guilabel:`Swupd Mirror`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:723 +msgid "To add a local swupd mirror, enter a valid URL in :guilabel:`Mirror URL:`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:731 +msgid "Figure 28: Swupd Mirror" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:736 +msgid "Assign Hostname" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:738 +msgid "In Advanced Options, select :guilabel:`Assign Hostname`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:740 +msgid "In :guilabel:`Hostname`, enter the hostname only (excluding the domain)." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:744 +msgid "" +"Hostname does not allow empty spaces. Hostname must start with an " +"alphanumeric character but may also contain hyphens. Maximum length of 63" +" characters." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:752 +msgid "Figure 29: Assign Hostname" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:761 +msgid "Automatic OS Updates" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:763 +msgid "" +"Automatical OS updates are enabled by default. In the rare case that you " +"need to disable automatic software updates, follow the onscreen " +"instructions, shown in Figure 30." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:767 +msgid "In Advanced Options, select :guilabel:`Automatic OS Updates`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:769 +msgid "Select the desired option." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:775 +msgid "Figure 30: Automatic OS Updates" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:777 +msgid "You are returned to the :guilabel:`Main Menu`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:780 +msgid "Save Configuration Settings" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:782 +msgid "In Advanced Options, select :guilabel:`Save Configuration Settings`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:784 +msgid "" +"A dialogue box shows the installation configuration was saved to :file" +":`clr-installer.yaml`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:791 +msgid "Figure 31: Automatic OS Updates" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:793 +msgid "" +"Use the :file:`clr-installer.yaml` file to install |CL|, with the same " +"configuration, on multiple targets." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:797 +msgid "Finish installation" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:799 +msgid "" +"When you are satisfied with your installation configuration, navigate to " +":guilabel:`Install` and select :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:806 +msgid "Figure 32: Select Install" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:808 +msgid "Select :guilabel:`reboot`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:812 +msgid "" +"If you do not assign an administrative user, upon rebooting, enter `root`" +" and set the root password immediately." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:815 +msgid "When the system reboots, remove any installation media present." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:818 +msgid "Default partition schema" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:820 +msgid "" +"To add partitions manually, see `Advanced configuration`_ below, and " +"create partitions per requirements in Table 1." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:823 +msgid "**Table 1. Disk Partition Setup**" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:827 +msgid "FileSystem" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:828 +msgid "Mount Point" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:829 +msgid "Minimum size" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:830 +msgid "``VFAT``" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:831 +msgid "/boot" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:832 +msgid "150M" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:833 +msgid "``swap``" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:835 +msgid "256MB" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:836 +msgid "``root``" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:837 +msgid "/" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:838 +msgid "*Size depends upon use case/desired bundles.*" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:841 +msgid "Troubleshooting" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:844 +msgid "For Configure Installation Media" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:846 +msgid "" +"If a warning message appears that no media or space is available after " +"entering :guilabel:`Configure Installation Media`:" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:849 +msgid "Verify that target media has enough free space." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:851 +msgid "Confirm the USB is properly connected to and mounted on target media." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:853 +msgid "Review the size of existing partitions on the target media:" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:855 +msgid "Linux\\* OS: :command:`lsblk -a`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:856 +msgid "Windows\\* OS: :command:`diskpart`, then :command:`list disk`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:857 +msgid "macOS\\* platform: :command:`diskutil list`" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/get-started/bootable-usb/bootable-usb.mo b/locale/de/LC_MESSAGES/get-started/bootable-usb/bootable-usb.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/get-started/bootable-usb/bootable-usb.mo differ diff --git a/locale/de/LC_MESSAGES/get-started/bootable-usb/bootable-usb.po b/locale/de/LC_MESSAGES/get-started/bootable-usb/bootable-usb.po new file mode 100644 index 00000000..89e4ecf7 --- /dev/null +++ b/locale/de/LC_MESSAGES/get-started/bootable-usb/bootable-usb.po @@ -0,0 +1,227 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"Instructions to create a |CL-ATTR| USB drive vary depending on your " +"operating system. Follow the instructions applicable to your system:" +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." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:22 +msgid "Create a bootable USB drive on Linux\\*" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:24 +#: ../../get-started/bootable-usb/bootable-usb.rst:107 +#: ../../get-started/bootable-usb/bootable-usb.rst:166 +msgid "Make sure you have have completed all `Prerequisites`_." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:26 +msgid "" +"Before burning the image onto your USB drive, :ref:`verify and decompress" +" your image `." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:30 +#: ../../get-started/bootable-usb/bootable-usb.rst:113 +#: ../../get-started/bootable-usb/bootable-usb.rst:172 +msgid "Burn the |CL| image onto a USB drive" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:34 +#: ../../get-started/bootable-usb/bootable-usb.rst:117 +#: ../../get-started/bootable-usb/bootable-usb.rst:176 +msgid "|CAUTION-BACKUP-USB|" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:36 +msgid "Open a terminal emulator and get root privilege." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:42 +#: ../../get-started/bootable-usb/bootable-usb.rst:121 +msgid "Go to the directory with the decompressed image." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:44 +msgid "Plug in the USB drive." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:46 +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:58 +msgid "Example output:" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:81 +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:91 +msgid "" +"Burn the image onto the USB drive. The example below burns an " +"uncompressed image onto ``:" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:100 +msgid "|CAUTION-UNMOUNT-USB-PARTITIONS|" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:105 +msgid "Create a bootable USB drive on macOS\\*" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:109 +msgid "" +"Before burning the image onto your USB drive, :ref:`verify and decompress" +" your image `." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:119 +msgid "Launch the Terminal app." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:123 +msgid "Plug in a USB drive and get its identifier:" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:129 +msgid "This will list available disks and their partitions, as shown in Figure 1." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:135 +msgid "Figure 1: macOS - Get USB drive identifier" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:137 +msgid "Unmount the USB drive identified in the previous step. For example:" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:143 +msgid "" +"Burn the image onto the drive using the :command:`dd` command. The " +"example below burns an uncompressed image onto ``:" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:150 +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:153 +msgid "Press :kbd:`-T` to check imaging progress." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:155 +msgid "Eject the USB drive." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:164 +msgid "Create a bootable USB drive on Windows\\*" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:168 +msgid "" +"Before burning the image onto your USB drive, :ref:`verify and decompress" +" your image `." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:178 +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:181 +msgid "Plug in the USB drive and open Rufus." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:183 +msgid "Under `Boot selection`, click the :guilabel:`SELECT` button." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:185 +msgid "Find and select the previously extracted |CL| image file." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:187 +msgid "Click the :guilabel:`START` button. See Figure 2." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:193 +msgid "Figure 2: Rufus utility" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:195 +msgid "" +"When the dialogue appears, select :guilabel:`Write in ISO image mode " +"(Recommended)`. See Figure 3." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:202 +msgid "Figure 3: ISOHybrid image detected" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:204 +msgid "Select the Windows taskbar menu for USB and select eject." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/get-started/compatibility-check.mo b/locale/de/LC_MESSAGES/get-started/compatibility-check.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/get-started/compatibility-check.mo differ diff --git a/locale/de/LC_MESSAGES/get-started/compatibility-check.po b/locale/de/LC_MESSAGES/get-started/compatibility-check.po new file mode 100644 index 00000000..726ea234 --- /dev/null +++ b/locale/de/LC_MESSAGES/get-started/compatibility-check.po @@ -0,0 +1,71 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"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 "" + +#: ../../get-started/compatibility-check.rst:13 +msgid "" +"This does not check other system components (for example: storage and " +"graphics) for compatibility with |CL|." +msgstr "" + +#: ../../get-started/compatibility-check.rst:16 +msgid "Download the `clear-linux-check-config.sh`_ file." +msgstr "" + +#: ../../get-started/compatibility-check.rst:18 +msgid "If a browser is not available, use:" +msgstr "" + +#: ../../get-started/compatibility-check.rst:24 +msgid "Make the script executable." +msgstr "" + +#: ../../get-started/compatibility-check.rst:30 +msgid "Run the script." +msgstr "" + +#: ../../get-started/compatibility-check.rst:32 +msgid "" +"Check to see if the host's processor and EFI firmware is capable of " +"running |CL|." +msgstr "" + +#: ../../get-started/compatibility-check.rst:39 +msgid "Check to see if the host is capable of running |CL| in a container." +msgstr "" + +#: ../../get-started/compatibility-check.rst:45 +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 "" + diff --git a/locale/de/LC_MESSAGES/get-started/get-started.mo b/locale/de/LC_MESSAGES/get-started/get-started.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/get-started/get-started.mo differ diff --git a/locale/de/LC_MESSAGES/get-started/get-started.po b/locale/de/LC_MESSAGES/get-started/get-started.po new file mode 100644 index 00000000..dbe2f3f9 --- /dev/null +++ b/locale/de/LC_MESSAGES/get-started/get-started.po @@ -0,0 +1,67 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 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 "" + +#: ../../get-started/get-started.rst:11 +msgid "Pre-install" +msgstr "" + +#: ../../get-started/get-started.rst:13 +msgid "There are a couple of things to take care of before you install." +msgstr "" + +#: ../../get-started/get-started.rst:15 +msgid ":ref:`system-requirements`" +msgstr "" + +#: ../../get-started/get-started.rst:16 +msgid ":ref:`compatibility-check`" +msgstr "" + +#: ../../get-started/get-started.rst:17 +msgid ":ref:`bootable-usb`" +msgstr "" + +#: ../../get-started/get-started.rst:19 +msgid "When installing |CL-ATTR| in a VM, consider which kernel to use." +msgstr "" + +#: ../../get-started/get-started.rst:21 +msgid ":ref:`Compatible VM kernels `" +msgstr "" + +#: ../../get-started/get-started.rst:31 +msgid "Install" +msgstr "" + +#: ../../get-started/get-started.rst:42 +msgid "Install in a virtual machine" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/get-started/virtual-machine-install/gce.mo b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/gce.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/gce.mo differ diff --git a/locale/de/LC_MESSAGES/get-started/virtual-machine-install/gce.po b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/gce.po new file mode 100644 index 00000000..9ba7ad3d --- /dev/null +++ b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/gce.po @@ -0,0 +1,340 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 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 "" + +#: ../../get-started/virtual-machine-install/gce.rst:13 +msgid "Prerequisites" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:15 +msgid "Set up a Google account and a GCP billing account." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:17 +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 "Process" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:24 +msgid "" +"Sign in to your Google\\* account on the `Google Cloud Console " +"`_:" +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 " +"`_ 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 " +"`_ to view the " +"currently released :abbr:`GCE (Google Compute Engine\\*)` image, and " +"download the :file:`clear--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:157 +msgid "Click the *Navigation menu* icon on the upper left screen menu." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:56 +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 "" + +#: ../../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 ``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 select the " +"``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 ``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 "Hover your mouse over the *Compute Engine* menu and select *Images*." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:120 +msgid "Figure 8: Image library" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:122 +msgid "" +"On the Compute Engine Image library page, click the ``[+] CREATE IMAGE`` " +"menu item to create a custom image:" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:129 +msgid "Figure 9: Create image" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:131 +msgid "" +"In the VM image creation page, change the image source type to *Cloud " +"Storage file*." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:134 +msgid "Under :guilabel:`Cloud Storage file`, select :guilabel:`Browse`." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:136 +msgid "" +"Locate the :file:`clear--gce.tar.gz` file, and click " +":guilabel:`Select`." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:143 +msgid "Figure 10: Create image using imported object" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:145 +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 "" + +#: ../../get-started/virtual-machine-install/gce.rst:152 +msgid "Figure 11: Image is created" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:154 +msgid "" +"After the |CL| image is imported, you can launch a VM instance running " +"|CL|:" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:159 +msgid "" +"Hover your mouse over the *Compute Engine* menu group and select the *VM " +"instances* item." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:166 +msgid "Figure 12: VM instances catalog" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:168 +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:171 +msgid "" +"Alternatively, click the ``CREATE INSTANCE`` button on the VM instances " +"page to create a VM instance." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:178 +msgid "Figure 13: VM creation" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:184 +msgid "Figure 14: VM instances list" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:186 +msgid "" +"In :guilabel:`Region`, choose a region based on the `Best practices for " +"Compute Engine regions selection`_." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:189 +msgid "Under *Boot disk*, click the ``Change`` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:195 +msgid "Figure 15: Use custom image" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:197 +msgid "Select the *Custom images* tab for using Clear Linux OS GCE image." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:203 +msgid "Figure 16: Select Clear Linux boot disk to create a VM instance" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:205 +msgid "" +"Scroll down to the bottom of the VM instance creation page, expand the " +"*Management, security, disks, networking, sole tenancy* group." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:212 +msgid "Figure 17: Set up SSH keys" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:215 +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:219 +msgid "Refer to :ref:`security` for more details." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:221 +msgid "Click the *Security* tab, copy and paste your SSH public key:" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:227 +msgid "Figure 18: Set SSH key for remote login" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:231 +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:236 +msgid "Click the ``Create`` button to create the |CL| VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:238 +msgid "The Clear Linux VM instance is created and assigned a public IP address:" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:244 +msgid "Figure 19: Clear Linux VM instance is created and started" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:246 +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:253 +msgid "Figure 20: SSH login to Clear Linux VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:256 +msgid "Related topics" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:258 +msgid "" +"The following tutorials describe a similar process and may be useful " +"references:" +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 "" + diff --git a/locale/de/LC_MESSAGES/get-started/virtual-machine-install/hyper-v.mo b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/hyper-v.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/hyper-v.mo differ diff --git a/locale/de/LC_MESSAGES/get-started/virtual-machine-install/hyper-v.po b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/hyper-v.po new file mode 100644 index 00000000..c728a732 --- /dev/null +++ b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/hyper-v.po @@ -0,0 +1,111 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 section explains how to run |CL-ATTR| inside a `Windows Server " +"Virtualization`_\\* or **Hyper-V** environment." +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:9 +msgid "" +"Please ensure you have enabled `Intel® Virtualization Technology " +"`_ (Intel® VT) and " +"`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:16 +msgid "Enable Hyper-V" +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:18 +msgid "" +"Please refer to the `Microsoft documentation`_ to enable and configure " +"*Hyper-V* on your machine." +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:22 +msgid "Create a virtual network" +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:24 +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:30 +msgid "Create a virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:32 +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 "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:36 +msgid "Create a virtual machine using the **Hyper-V Manager**:" +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:38 +msgid "Choose **Generation 2** when prompted to *specify VM generation*." +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:39 +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:41 +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:44 +msgid "Currently, |CL| does not boot with `secure boot` enabled." +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:47 +msgid "Connect to your new VM and start it. You should see a prompt:" +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:53 +msgid "Set a root user password." +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:55 +msgid "Your virtual machine running |CL| is ready!" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/get-started/virtual-machine-install/kvm.mo b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/kvm.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/kvm.mo differ diff --git a/locale/de/LC_MESSAGES/get-started/virtual-machine-install/kvm.po b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/kvm.po new file mode 100644 index 00000000..d2c26b05 --- /dev/null +++ b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/kvm.po @@ -0,0 +1,231 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 guide 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:10 +msgid "Install QEMU-KVM" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:12 +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:16 +msgid "Log in and open a terminal emulator." +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:18 +msgid "Install `QEMU*-KVM` on the host machine. Below are some example distros." +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:20 +msgid "On |CL|:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:26 +#: ../../get-started/virtual-machine-install/kvm.rst:155 +msgid "On Ubuntu\\* 18.04 LTS Desktop:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:32 +#: ../../get-started/virtual-machine-install/kvm.rst:161 +msgid "On Mint\\* 19.1 “Cinnamon” Desktop:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:38 +#: ../../get-started/virtual-machine-install/kvm.rst:167 +msgid "On Fedora\\* 30 Workstation:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:45 +msgid "Download and launch the virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:47 +msgid "" +"Download the latest pre-built |CL| KVM image file from the `image " +"`_ directory. Look for " +"``clear--kvm.img.xz``. You can also use this command:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:55 +msgid "Uncompress the downloaded image:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:61 +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:72 +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:78 +msgid "" +"Download the `QEMU-KVM launcher`_ script from the `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:87 +msgid "Make the script executable:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:93 +msgid "Start the |CL| KVM virtual machine:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:99 +msgid "Log in as ``root`` user and set a new password." +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:102 +msgid "SSH access into the virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:104 +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:107 +msgid "Configure SSH in the |CL| VM to allow root login:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:115 +msgid "Enable and start SSH server in the |CL| VM:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:122 +#: ../../get-started/virtual-machine-install/kvm.rst:211 +msgid "" +"Determine the IP address of the host on which you will launch the VM. " +"Substitute in the next step with this information." +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:129 +msgid "SSH into the |CL| VM using the default port of `10022`:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:136 +msgid "Optional: Add the GNOME Display Manager (GDM)" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:138 +msgid "" +"To add :abbr:`GDM (GNOME Display Manager)` to the |CL| VM, follow these " +"steps:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:140 +msgid "Shutdown the active |CL| VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:146 +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:149 +msgid "On Clear Linux:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:173 +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:194 +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:199 +msgid "Increase the size of the VM by 10GB to accommodate the GDM installation:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:205 +msgid "Relaunch the |CL| VM:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:218 +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:225 +msgid "Log in as `root` user into the |CL| VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:227 +msgid "" +"Follow these steps to `resize the partition`_ of the virtual disk of the " +"VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:229 +msgid "Add GDM to the |CL| VM:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:235 +msgid "Reboot the |CL| VM to start GDM:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:241 +msgid "Go through the GDM out-of-box experience (OOBE)." +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:243 +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 "" + diff --git a/locale/de/LC_MESSAGES/get-started/virtual-machine-install/virtualbox-cl-installer.mo b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/virtualbox-cl-installer.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/virtualbox-cl-installer.mo differ diff --git a/locale/de/LC_MESSAGES/get-started/virtual-machine-install/virtualbox-cl-installer.po b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/virtualbox-cl-installer.po new file mode 100644 index 00000000..99f1c39d --- /dev/null +++ b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/virtualbox-cl-installer.po @@ -0,0 +1,554 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"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 "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:15 +msgid "Prerequisites" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:17 +msgid "Before continuing, assure you have:" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:19 +msgid "" +"Enabled 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:23 +msgid "" +"Downloaded and installed |VB| **version 6.0 or greater** from the " +"`official VirtualBox website`_ per the `appropriate instructions`_ for " +"your platform." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:28 +msgid "Download and extract the |CL| installer ISO" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:30 +msgid "" +"Download the :file:`clear--live-server.iso.xz` of |CL| on the " +"`downloads page`_." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:33 +msgid "" +"Validate the integrity of the downloaded image by checking the file hash " +"and signatures. Refer :ref:`validate-signatures` for detailed steps." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:36 +msgid "Decompress the downloaded image." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:38 +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:45 +msgid "Figure 1: 7zip extract here command" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:47 +msgid "On Linux :" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:53 +msgid "Delete the originally downloaded compressed file." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:56 +msgid "Create a new |VB| virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:58 +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 "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:63 +msgid "Launch the |VBM| from your host system." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:65 +msgid "Click the *New* button to create a new VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:67 +msgid "Choose :guilabel:`Expert mode`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:69 +msgid "In :guilabel:`Create Virtual Machine`, enter the following settings:" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:71 +msgid "**Name**: Choose name (e.g. ClearLinuxOS-VM)." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:72 +msgid "**Type**: Linux" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:73 +msgid "**Version**: **Linux 2.6 / 3.x / 4.x (64-bit)**" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:74 +msgid "**Hard disk**: `Create a virtual hard disk now`" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:75 +msgid "**Memory size default**: 2048 MB (Adjust appropriately.)" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:78 +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:85 +msgid "Figure 2: Create Virtual Machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:87 +msgid "Select :guilabel:`Create`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:89 +msgid "In :guilabel:`Create Virtual Hard Disk`, select:" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:91 +msgid "**File location**" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:92 +msgid "**File size**: **32.00 GB**. Adjust size to your needs." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:93 +msgid "**Hard disk file type**: `VDI (VirtualBox Disk Image)`" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:94 +msgid "**Storage on physical hard disk**:`Dynamically allocated`" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:100 +msgid "Figure 3: Create Virtual Hard Disk" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:102 +msgid "Click *Create*." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:104 +msgid "A new virtual machine will be created and appear in the |VBM|." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:106 +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:222 +msgid "Click *Settings* to configure the |CL| VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:108 +msgid "In the left-hand menu, navigate to the :guilabel:`System` menu." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:110 +msgid "" +"In the :guilabel:`Motherboard` tab, select the `Chipset` pulldown menu, " +"and then select :guilabel:`ICH9`. See Figure 4." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:115 +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:118 +msgid "In :guilabel:`Enabled Features`, check these boxes:" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:120 +msgid "**Enable I/O APIC**" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:121 +msgid "**Enable EFI (special OSes only)**" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:127 +msgid "Figure 4: Settings > System" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:131 +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:136 +msgid "Select :guilabel:`OK`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:139 +msgid "Install |CL| on the |VB| VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:141 +msgid "|CL| is ready to be installed." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:144 +msgid "Mount the installation ISO" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:146 +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:149 +msgid "" +"From the *ClearLinux-OS* :guilabel:`Settings` at left, select " +":guilabel:`Storage`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:152 +msgid "" +"From :guilabel:`Storage Devices`, middle column, click the blue disk " +"labeled *Empty*." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:155 +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 "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:163 +msgid "Figure 5: Choose Virtual Optical Disk Drive" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:165 +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:172 +msgid "Figure 6: Mounting an ISO" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:174 +msgid "Select :guilabel:`OK` to exit and return to the main |VBM|." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:177 +msgid "Install |CL| with live-server installer" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:179 +msgid "In the |VBM|, select virtual machine you created and click *Start*." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:185 +msgid "Figure 7: Start the installer" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:189 +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:192 +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:195 +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:198 +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:201 +msgid "" +"In :guilabel:`Advanced options` > :guilabel:`Manage User`, create an " +"administrative user." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:204 +msgid "Do not install the bundle `desktop-autostart`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:206 +msgid "When |CL| installation is complete, select :guilabel:`Exit`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:208 +msgid "At the prompt, enter:" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:215 +msgid "Unmount the ISO" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:217 +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:220 +msgid "Return to the |VBM|." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:224 +msgid "" +"From the *VM - Settings* window, navigate to the *Storage* pane from the " +"left-hand side." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:227 +msgid "" +"From the middle *Storage Devices* column, click the blue CD disk labeled " +"*clear--live-server.iso* under the *Controller: IDE* from." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:230 +msgid "" +"From the *Attributes* column at right, in *Optical Drive*, select the " +"blue CD icon beside and click *Remove Disk from Virtual Drive*." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:237 +msgid "Figure 8: Remove Disk from Virtual Drive" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:239 +msgid "Click *OK* to exit the *VM Settings* menu and return to the main |VBM|." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:243 +msgid "Install |VB| Linux Guest Additions" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:245 +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:248 +msgid "From the |VBM| select the |CL| VM, and select :guilabel:`Start`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:250 +msgid "In the VM Console, log in as the administrative user previously created." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:253 +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:256 +msgid "To update the kernel, enter:" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:262 +msgid "At initial login, enter the administrative user's password and continue." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:264 +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:272 +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:282 +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:290 +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 "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:297 +msgid "Figure 9: Insert Guest Additions CD image" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:299 +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:302 +msgid "Instead, we provide a script to patch and install |VB| drivers on |CL|." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:304 +msgid "Open a Terminal and enter the script:" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:312 +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:315 +msgid "Shut down the system. Select :guilabel:`Machine>ACPI Shutdown`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:321 +msgid "Figure 10: Powering off a VirtualBox VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:323 +msgid "Select :guilabel:`Settings`, :guilabel:`Display`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:325 +msgid "" +"In :guilabel:`Graphics Controller`, select :guilabel:`VBoxSVGA` to adjust" +" screen size dynamically." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:332 +msgid "Figure 11: VirtualBox hardware acceleration error" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:334 +msgid "In the |VBM|, select :guilabel:`Start`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:336 +msgid "In the VM console, login and verify the |VB| drivers are loaded:" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:342 +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:345 +msgid "Add `desktop-autostart` for a full desktop experience." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:351 +msgid "Reboot the VM and log in with the administrative user." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:357 +msgid "The |CL| VM running on |VB| is ready to develop and explore." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:360 +msgid "Troubleshooting" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:362 +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:370 +msgid "Figure 12: VirtualBox hardware acceleration error" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:372 +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:376 +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:379 +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:386 +msgid "" +"To enable Hyper-V again, execute this command in an **Administrator: " +"Command Prompt or Powershell**, and reboot the system:" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmw-player-preconf.mo b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmw-player-preconf.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmw-player-preconf.mo differ diff --git a/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmw-player-preconf.po b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmw-player-preconf.po new file mode 100644 index 00000000..9637b3b8 --- /dev/null +++ b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmw-player-preconf.po @@ -0,0 +1,493 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"`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:11 +msgid "" +"This section shows 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 "In this tutorial, we perform the following steps:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:21 +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 "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:26 +msgid "Install the VMware Workstation Player hypervisor" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:28 +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:32 +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:35 +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:38 +msgid "On supported Linux distros:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:40 +msgid "Enable a GUI desktop." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:42 +msgid "Start a terminal emulator." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:44 +msgid "" +"Start the installer by issuing the command below and following the guided" +" steps." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:51 +msgid "On Windows:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:53 +msgid "Start the installer." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:54 +msgid "Follow the setup wizard." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:56 +msgid "For additional help, see the `VMware Workstation Player guide`_." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:59 +msgid "Download the latest |CL| VMware image" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:61 +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:69 +msgid "" +"Visit :ref:`image-types` for additional information about all available " +"|CL| images." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:4 +msgid "Verify the integrity of the |CL| image" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.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-windows.rst:11 +msgid "Download the corresponding SHA512 checksum file of your |CL| image." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:12 +msgid "Start Command Prompt." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:13 +msgid "Go to the directory with the downloaded image and checksum files." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:14 +msgid "Get the SHA512 checksum of the image with the command:" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.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-windows.rst:24 +msgid "Decompress the |CL| image" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.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-windows.rst:30 +msgid "Download and install `7-Zip`_." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:31 +msgid "Go to the directory with the downloaded image and right-click it." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.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-windows.rst:39 +msgid "Figure 1: Windows 7-Zip extract file." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:74 +msgid "We also provide instructions for other operating systems:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:76 +msgid ":ref:`download-verify-decompress-linux`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:77 +msgid ":ref:`download-verify-decompress-mac`" +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 "" + diff --git a/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmw-player.mo b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmw-player.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmw-player.mo differ diff --git a/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmw-player.po b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmw-player.po new file mode 100644 index 00000000..4ec155fc --- /dev/null +++ b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmw-player.po @@ -0,0 +1,492 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"`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.rst:11 +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 "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:16 +msgid "In this tutorial, we perform the following steps:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:21 +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:24 +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:30 +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 "" + +#: ../../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 14 Player`_ is available for Windows and Linux. " +"Download your preferred version." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:44 +msgid "" +"Install VMware Workstation 14 Player following the instructions " +"appropriate for your system's OS:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:47 +msgid "On supported Linux distros:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:49 +msgid "Enable a GUI desktop." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:50 +msgid "Start a terminal emulator." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:51 +msgid "" +"Start the installer by issuing the command below and follow the guided " +"steps." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:58 +msgid "On Windows:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:60 +msgid "Start the installer." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:61 +msgid "Follow the setup wizard." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:63 +msgid "For additional help, see the `VMware Workstation Player guide`_." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:66 +msgid "Download the latest |CL| installer ISO" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:68 +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/vmw-player.rst:71 +msgid "" +"Visit :ref:`image-types` for additional information about all available " +"|CL| images." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:4 +msgid "Verify the integrity of the |CL| image" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.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-windows.rst:11 +msgid "Download the corresponding SHA512 checksum file of your |CL| image." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:12 +msgid "Start Command Prompt." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:13 +msgid "Go to the directory with the downloaded image and checksum files." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:14 +msgid "Get the SHA512 checksum of the image with the command:" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.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-windows.rst:24 +msgid "Decompress the |CL| image" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.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-windows.rst:30 +msgid "Download and install `7-Zip`_." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:31 +msgid "Go to the directory with the downloaded image and right-click it." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.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-windows.rst:39 +msgid "Figure 1: Windows 7-Zip extract file." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:76 +msgid "We also provide instructions for other operating systems:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:78 +msgid ":ref:`download-verify-decompress-linux`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:79 +msgid ":ref:`download-verify-decompress-mac`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:82 +msgid "Create and configure a new VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:84 +msgid "Start the `VMware Workstation Player` app." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:86 +msgid "" +"On the home screen, click :guilabel:`Create a New Virtual Machine`. See " +"Figure 1." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:93 +msgid "Figure 1: VMware Workstation 14 Player - Create a new virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:96 +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:104 +msgid "Figure 2: VMware Workstation 14 Player - Select |CL| installer ISO" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:106 +msgid "" +"Click the :guilabel:`Browse` button and select the decompressed |CL| " +"installer ISO." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:109 +#: ../../get-started/virtual-machine-install/vmw-player.rst:125 +#: ../../get-started/virtual-machine-install/vmw-player.rst:136 +#: ../../get-started/virtual-machine-install/vmw-player.rst:151 +msgid "Click the :guilabel:`Next` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:111 +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:119 +msgid "" +"Figure 3: VMware Workstation 14 Player - Select guest operating system " +"type" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:122 +msgid "" +"Set the :guilabel:`Version` setting to :guilabel:`Other Linux 3.x or " +"later kernel 64-bit`." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:127 +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:134 +msgid "Figure 4: VMware Workstation 14 Player - Name virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:138 +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:145 +msgid "Figure 5: VMware Workstation 14 Player - Set disk capacity" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:148 +msgid "" +"A minimal |CL| installation can exist on 600MB 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 14 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 14 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 14 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 14 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:`` + :kbd:`` 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 14 Player - Edit CD/DVD settings" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:226 +msgid "Go to :menuselection:`Removable Devices-->CD/DVD (IDE)-->Settings`." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:228 +msgid "" +"On the :guilabel:`Device status` section, uncheck the " +":guilabel:`Connected` and the :guilabel:`Connect at power on` settings. " +"See Figure 11." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:236 +msgid "Figure 11: VMware Workstation 14 Player - Disconnect CD/DVD" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:238 +msgid "Click the :guilabel:`OK` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:240 +msgid "To power off the VM, click the :guilabel:`Player` menu. See Figure 12." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:246 +msgid "Figure 12: VMware Workstation 14 Player - Power off virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:248 +msgid "Go to :guilabel:`Power` and select :guilabel:`Shut Down Guest`." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:251 +msgid "Enable UEFI boot support" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:253 +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 "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:262 +msgid "Depending on the OS, you can typically find the VMware VM files under:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:264 +msgid "On Linux distros: :file:`/home/username/vmware`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:265 +msgid "" +"On Windows: :file:`C:\\\\Users\\\\username\\\\Documents\\\\Virtual " +"Machines`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:268 +msgid "Power on the VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:270 +msgid "After configuring the settings above, power on your |CL| virtual machine." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:272 +msgid "" +"On the :guilabel:`VMware Workstation Player` home screen, select your VM." +" See Figure 13." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:279 +msgid "Figure 13: VMware Workstation 14 Player - Power on virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:281 +msgid "Click :guilabel:`Play virtual machine`." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:284 +msgid "Related topics" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:286 +msgid "For other guides on using the VMWare Player and ESXi, see:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:288 +msgid ":ref:`vmw-player-preconf`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:289 +msgid ":ref:`vmware-esxi-install-cl`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:290 +msgid ":ref:`vmware-esxi-preconfigured-cl-image`" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-install-cl.mo b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-install-cl.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-install-cl.mo differ diff --git a/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-install-cl.po b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-install-cl.po new file mode 100644 index 00000000..f1ea673b --- /dev/null +++ b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-install-cl.po @@ -0,0 +1,477 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"`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 "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:10 +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 "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:13 +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 "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:17 +msgid "" +"If you would prefer to use a preconfigured |CL| VMware image instead, see" +" :ref:`vmware-esxi-preconfigured-cl-image`." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:22 +msgid "" +"VMware also offers a type 2 hypervisor called `VMware Workstation " +"Player`_ which is designed for the desktop environment." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:25 +msgid "See :ref:`vmw-player-preconf` or see :ref:`vmw-player`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:27 +msgid "Visit :ref:`image-types` to learn more about all available images." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:29 +msgid "Install steps:" +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 "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:4 +msgid "Decompress the |CL| image" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:6 +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:10 +msgid "Start a terminal emulator." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:11 +msgid "Go to the directory with the downloaded image." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:13 +msgid "To decompress an XZ image, enter:" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:19 +msgid "To decompress a GZ image, enter:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:45 +msgid "For alternative instructions on other operating systems, see:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:47 +msgid ":ref:`download-verify-decompress-mac`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:48 +msgid ":ref:`download-verify-decompress-windows`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:51 +msgid "Upload the |CL| installer ISO to the VMware server" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:53 +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:55 +msgid "" +"Under the :guilabel:`Navigator` window, select :guilabel:`Storage`. See " +"Figure 1." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:57 +msgid "" +"Under the :guilabel:`Datastores` tab, click the :guilabel:`Datastore " +"browser` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:64 +msgid "Figure 1: VMware ESXi - Navigator > Storage" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:66 +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:73 +msgid "Figure 2: VMware ESXi - Datastore > Create directory" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:75 +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:82 +msgid "Figure 3: VMware ESXi - Datastore > Upload ISO" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:84 +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:88 +msgid "Create and configure a new VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:90 +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:93 +msgid "" +"Under the :guilabel:`Navigator` window, select :guilabel:`Virtual " +"Machines`. See Figure 4." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:95 +msgid "In the right window, click the :guilabel:`Create / Register VM` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:101 +msgid "Figure 4: VMware ESXi - Navigator > Virtual Machines" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:103 +msgid "On the :guilabel:`Select creation type` step:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:105 +msgid "Select the :guilabel:`Create a new virtual machine` option. See Figure 5." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:107 +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:121 +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:132 +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:185 +msgid "Click the :guilabel:`Next` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:113 +msgid "Figure 5: VMware ESXi - Create a new virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:115 +msgid "On the :guilabel:`Select a name and guest OS` step:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:117 +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:118 +msgid "" +"Set the :guilabel:`Compatability` option to :guilabel:`ESXi 6.5 virtual " +"machine`." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:119 +msgid "Set the :guilabel:`Guest OS family` option to :guilabel:`Linux`." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:120 +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:127 +msgid "Figure 6: VMware ESXi - Give a name and select guest OS type" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:129 +msgid "On the :guilabel:`Select storage` step:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:131 +msgid "Accept the default option." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:134 +msgid "On the :guilabel:`Customize settings` step:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:136 +msgid "Click the :guilabel:`Virtual Hardware` button. See Figure 7." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:137 +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:144 +msgid "Figure 7: VMware ESXi - Enable hardware virtualization" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:146 +msgid "Set :guilabel:`Memory` size to 2048MB (2GB). See Figure 8." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:152 +msgid "Figure 8: VMware ESXi - Set memory size" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:156 +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:161 +msgid "Set :guilabel:`Hard disk 1` to the desired capacity. See Figure 9." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:167 +msgid "Figure 9: VMware ESXi - Set hard disk size" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:171 +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:174 +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:183 +msgid "Figure 10: VMware ESXi - Set CD/DVD to boot installer ISO" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:186 +msgid "Click the :guilabel:`Finish` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:189 +msgid "Install |CL| into the new VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:191 +msgid "Power on the VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:193 +msgid "" +"Under the :guilabel:`Navigator` window, select :guilabel:`Virtual " +"Machines`. See Figure 11." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:195 +msgid "In the right window, select the newly-created VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:196 +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:276 +msgid "Click the :guilabel:`Power on` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:197 +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:277 +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:204 +msgid "Figure 11: VMware ESXi - Navigator > Virtual Machines > Power on VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:206 +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:208 +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:212 +msgid "Reconfigure the VM's settings to boot the newly-installed |CL|" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:214 +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:218 +msgid "Power off the VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:220 +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:228 +msgid "Figure 12: VMware ESXi - Actions > Power off" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:230 +msgid "Edit the VM settings." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:232 +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:239 +msgid "Figure 13: VMware ESXi - Actions > Edit settings" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:241 +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:243 +msgid "Click the :guilabel:`Virtual Hardware` button. See Figure 14." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:244 +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:251 +msgid "Figure 14: VMware ESXi - Disconnect the CD/DVD drive" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:253 +msgid "|CL| needs UEFI support in order to boot. Enable it." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:255 +msgid "Click the :guilabel:`VM Options` button. See Figure 15." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:256 +msgid "Expand the :guilabel:`Boot Options` setting." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:257 +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:264 +msgid "Figure 15: VMware ESXi - Set boot firmware to EFI" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:266 +msgid "Click the :guilabel:`Save` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:269 +msgid "Power on the VM and boot |CL|" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:271 +msgid "After configuring the settings above, power on the VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:273 +msgid "" +"Under the :guilabel:`Navigator` window, select :guilabel:`Virtual " +"Machines`. See Figure 16." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:275 +msgid "In the right window, select the VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:284 +msgid "Figure 16: VMware ESXi - Navigator > Virtual Machines > Power on VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:287 +msgid "Related topics" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:289 +msgid ":ref:`vmware-esxi-preconfigured-cl-image`" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.mo b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.mo differ diff --git a/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.po b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.po new file mode 100644 index 00000000..1b58619a --- /dev/null +++ b/locale/de/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.po @@ -0,0 +1,466 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"`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:10 +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 "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:13 +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 "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:19 +msgid "" +"VMware also offers a type 2 hypervisor called `VMware Workstation Player`" +" which is designed for the desktop environment." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:22 +msgid "See :ref:`vmw-player-preconf` or see :ref:`vmw-player`." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:25 +msgid "Install steps:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:31 +msgid "Download the latest |CL| VMware image" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:33 +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:41 +msgid "" +"Visit :ref:`image-types` for additional information about all available " +"|CL| images." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:4 +msgid "Decompress the |CL| image" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:6 +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:10 +msgid "Start a terminal emulator." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:11 +msgid "Go to the directory with the downloaded image." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:13 +msgid "To decompress an XZ image, enter:" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:19 +msgid "To decompress a GZ image, enter:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:47 +msgid "For alternative instructions on other operating systems, see:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:49 +msgid ":ref:`download-verify-decompress-mac`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:50 +msgid ":ref:`download-verify-decompress-windows`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:53 +msgid "Upload the |CL| image to the VMware server" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:55 +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:59 +msgid "" +"The steps in this section can also be referenced from the `VMware " +"documentation on Using the Datastore File Browser`_" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:61 +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:64 +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:68 +msgid "" +"Under the :guilabel:`Datastores` tab, click the :guilabel:`Datastore " +"browser` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:75 +msgid "Figure 1: VMware ESXi - Navigator > Storage" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:77 +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:84 +msgid "Figure 2: VMware ESXi - Datastore > Create directory" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:86 +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:93 +msgid "Figure 3: VMware ESXi - Datastore > Upload VMware image" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:95 +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:99 +msgid "Convert the |CL| image to an ESXi-supported format" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:101 +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:105 +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:107 +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:112 +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 "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:116 +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:119 +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:122 +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:129 +msgid "Two files should result from this:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:131 +msgid ":file:`clear-[version number]-esxi-flat.vmdk`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:132 +msgid ":file:`clear-[version number]-esxi.vmdk`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:134 +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:138 +msgid "Create and configure a new VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:140 +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:144 +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:147 +msgid "In the right window, click the :guilabel:`Create / Register VM` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:153 +msgid "Figure 4: VMware ESXi - Navigator > Virtual Machines" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:155 +msgid "On the :guilabel:`Select creation type` step:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:157 +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:160 +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:177 +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:188 +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:259 +msgid "Click the :guilabel:`Next` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:166 +msgid "Figure 5: VMware ESXi - Create a new virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:168 +msgid "On the :guilabel:`Select a name and guest OS` step:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:170 +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:172 +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:174 +msgid "Set the :guilabel:`Guest OS family` option to :guilabel:`Linux`." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:175 +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:183 +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:185 +msgid "On the :guilabel:`Select storage` step:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:187 +msgid "Accept the default option." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:190 +msgid "On the :guilabel:`Customize settings` step:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:192 +msgid "Click the :guilabel:`Virtual Hardware` button. See Figure 7." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:193 +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:201 +msgid "Figure 7: VMware ESXi - Enable hardware virtualization" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:203 +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:210 +msgid "Figure 8: VMware ESXi - Remove hard drive" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:212 +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:220 +msgid "Figure 9: VMware ESXi - Disconnect the CD/DVD drive" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:222 +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:225 +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:232 +msgid "Figure 10: VMware ESXi - Add an existing hard drive" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:234 +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:242 +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:245 +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:247 +msgid "Click the :guilabel:`VM Options` button. See Figure 12." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:248 +msgid "Expand the :guilabel:`Boot Options` setting." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:249 +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:256 +msgid "Figure 12: VMware ESXi - Set boot firmware to EFI" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:258 +msgid "Click the :guilabel:`Save` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:260 +msgid "Click the :guilabel:`Finish` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:263 +msgid "Power on the VM and boot |CL|" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:265 +msgid "After configuring the settings above, power on the VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:267 +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:269 +msgid "In the right window, select the newly-created VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:270 +msgid "Click the :guilabel:`Power on` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.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-preconfigured-cl-image.rst:278 +msgid "Figure 13: VMware ESXi - Navigator > Virtual Machines > Power on VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:281 +msgid "Related topics" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:283 +msgid ":ref:`vmware-esxi-install-cl`" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/deploy-at-scale.mo b/locale/de/LC_MESSAGES/guides/deploy-at-scale.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/deploy-at-scale.mo differ diff --git a/locale/de/LC_MESSAGES/guides/deploy-at-scale.po b/locale/de/LC_MESSAGES/guides/deploy-at-scale.po new file mode 100644 index 00000000..60cb19e3 --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/deploy-at-scale.po @@ -0,0 +1,414 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"Once you are comfortable with |CL-ATTR| :ref:`concepts `, your " +"next step as a system administrator is to understand how to deploy |CL| " +"at scale in your environment." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:10 +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 "" + +#: ../../guides/deploy-at-scale.rst:16 +msgid "" +"This is not a replacement or blueprint for designing your own IT " +"operating environment." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:19 +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 "" + +#: ../../guides/deploy-at-scale.rst:28 +msgid "Pick a |CL| usage and update strategy" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:30 +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:35 +msgid "Below is an overview of some considerations." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:38 +msgid "Create your own Linux distribution (mix)" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:40 +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 "" + +#: ../../guides/deploy-at-scale.rst:46 +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 "" + +#: ../../guides/deploy-at-scale.rst:50 +msgid "" +"swupd update webservers which are serving update content to production " +"machines (see `mixer process`_ for more information) should be " +"appropriately scaled." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:54 +msgid "" +"Your swupd update server is just like any other web application. |WEB-" +"SERVER-SCALE|" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:58 +msgid "Adopt an agile methodology" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:59 +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:62 +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:69 +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:72 +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:75 +msgid "" +"Setup a path to production for building |CL| based images. At minimum " +"this should include:" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:78 +msgid "" +"A development clr-on-clr environment to test building packages and " +"bundles for |CL| systems." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:81 +msgid "A pre-production environment to deploy |CL| versions to before production" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:84 +msgid "" +"Employ a continuous integration and continuous deployment (CI/CD) " +"philosophy in order to:" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:87 +msgid "" +"Automatically pull custom packages as they are updated from their " +"upstream projects or vendors." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:90 +msgid "" +"Generate |CL| bundles and potentially bootable images with your " +"customizations, if any." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:93 +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:96 +msgid "" +"Integrate with your organization's governance processes, such as change " +"control." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:100 +msgid "Versioning Infrastructure" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:102 +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:106 +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:109 +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:114 +msgid "Pick an image distribution strategy" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:116 +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:121 +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:125 +msgid "See the available :ref:`image-types`." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:127 +msgid "Below are some common ways to install |CL| to systems at scale:" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:130 +msgid "Baremetal" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:132 +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 "" + +#: ../../guides/deploy-at-scale.rst:136 +msgid "" +"This option works well if your customizations are fairly small in size " +"and infrastructure can be stateless." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:139 +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:144 +msgid "Cloud Instances or Virtual Machines" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:146 +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:150 +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:155 +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:160 +msgid "Containers" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:162 +msgid "" +"Containerization platforms allow images to be pulled from a repository " +"and deployed repeatedly as isolated containers." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:165 +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:170 +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:175 +msgid "Considerations with stateless systems" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:176 +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:181 +msgid "Backup strategy" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:183 +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:187 +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 "" + +#: ../../guides/deploy-at-scale.rst:192 +msgid "Meaningful Logging & Telemetry" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:194 +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:197 +msgid "" +"Remote syslogging in |CL| is available through the `systemd journal-" +"remote service`_" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:200 +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 "" + +#: ../../guides/deploy-at-scale.rst:206 +msgid "" +"Your telemetry server is just like any other web application. |WEB-" +"SERVER-SCALE|" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:210 +msgid "Orchestration and Configuration Management" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:212 +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:215 +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 "" + +#: ../../guides/deploy-at-scale.rst:222 +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:228 +msgid "Cloud-native applications" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:230 +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:235 +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 "" + diff --git a/locale/de/LC_MESSAGES/guides/guides.mo b/locale/de/LC_MESSAGES/guides/guides.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/guides.mo differ diff --git a/locale/de/LC_MESSAGES/guides/guides.po b/locale/de/LC_MESSAGES/guides/guides.po new file mode 100644 index 00000000..b6b78e41 --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/guides.po @@ -0,0 +1,44 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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:33 +msgid "Kernel" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/kernel/kernel-development.mo b/locale/de/LC_MESSAGES/guides/kernel/kernel-development.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/kernel/kernel-development.mo differ diff --git a/locale/de/LC_MESSAGES/guides/kernel/kernel-development.po b/locale/de/LC_MESSAGES/guides/kernel/kernel-development.po new file mode 100644 index 00000000..898885d0 --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/kernel/kernel-development.po @@ -0,0 +1,539 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 document shows how to obtain and compile a Linux* kernel source " +"using |CL-ATTR| development tooling." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:9 +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 "" + +#: ../../guides/kernel/kernel-development.rst:18 +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 "" + +#: ../../guides/kernel/kernel-development.rst:22 +msgid "Request changes be included with the |CL| kernel" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:24 +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:28 +msgid "Make enhancement requests to the |CL| `distribution on GitHub`_ ." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:31 +msgid "Set up kernel development environment" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:33 +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:36 +msgid "You can build and install a custom kernel; however you must:" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:38 +msgid "Disable Secure Boot" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:39 +msgid "Maintain any updates to the kernel going forward" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:41 +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:46 +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:53 +msgid "Clone the kernel package" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:54 +msgid "" +"Clone the existing kernel package repository from |CL| as a starting " +"point." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:56 +msgid "" +"Clone the Linux kernel package from |CL|. Using the :command:`make " +"clone_` command in the :file:`clearlinux/` directory clones " +"the package from the `clearlinux-pkgs GitHub`_." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:66 +msgid "Navigate into the cloned package directory." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:73 +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 "" + +#: ../../guides/kernel/kernel-development.rst:80 +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/`." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:84 +msgid "Change the kernel version" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:86 +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:92 +#: ../../guides/kernel/kernel-development.rst:285 +msgid "Open the Linux kernel package RPM SPEC file in an editor." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:98 +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:101 +msgid "" +"A list of current and available kernel release can be found on " +"`kernel.org`_." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:120 +msgid "" +"Consider changing the Name from *linux* in the RPM spec file to easily " +"identify a modified kernel." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:122 +msgid "" +"Consider changing the ktarget from *native* in the RPM spec file to " +"easily identify a modified kernel." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:124 +msgid "Commit and save the changes to the file." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:127 +msgid "Pull a copy of the Linux kernel source code" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:129 +msgid "Obtain a local copy of the source code to make modifications against." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:131 +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:139 +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:146 +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:155 +msgid "Customize the Linux kernel source" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:157 +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:162 +msgid "Modify kernel configuration" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:164 +msgid "" +"The kernel source has many configuration options available to pick " +"support for different hardware and software features." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:166 +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:171 +#: ../../guides/kernel/kernel-development.rst:228 +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 "" + +#: ../../guides/kernel/kernel-development.rst:176 +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:185 +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:188 +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:191 +msgid "" +":command:`make config` - a text-based tool that asks questions one-by-one" +" to decide configuration options." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:194 +msgid "" +":command:`make menuconfig` - a terminal user interface that provides " +"menus to decide configuration options." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:197 +msgid "" +":command:`make xconfig` - a graphical user interface that provides tree " +"views to decide configuration options." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:201 +msgid "" +"More configuration tools can be found by looking at the make help: " +":command:`make help | grep config`" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:204 +msgid "Commit and save the changes to the :file:`.config` file." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:206 +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:214 +msgid "Modify kernel source code" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:216 +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:219 +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:223 +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:233 +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:243 +msgid "" +"Apply patches provided by the |CL| kernel package to the kernel source in" +" the working directory." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:251 +msgid "Make any of your desired code changes to the Linux source code files." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:254 +msgid "Track and commit your changes to the local git repo." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:262 +msgid "" +"Generate a patch file based on your git commits. 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:271 +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:279 +msgid "Navigate back to the RPM build directory." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:291 +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:314 +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:333 +msgid "Commit and save the changes to the RPM SPEC file." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:336 +msgid "Modify kernel boot parameters" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:337 +msgid "" +"The kernel boot options are passed from the bootloader to the kernel with" +" command-line parameters." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:340 +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:345 +msgid "Open the kernel :file:`cmdline` file in an editor." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:352 +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:356 +msgid "Commit and save the changes to the :file:`cmdline` file." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:358 +msgid "" +"See the `Kernel parameters documentation`_ for a list of available " +"parameters." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:362 +msgid "Build and install the kernel" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:363 +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:366 +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:369 +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:377 +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 "" + +#: ../../guides/kernel/kernel-development.rst:380 +msgid "" +"The result will be multiple :file:`.rpm` files in the :file:`rpms` " +"directory as output." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:387 +msgid "" +"The kernel RPM will be named " +":file:`linux--.x86_64.rpm`" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:391 +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:394 +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:399 +msgid "" +"Install the kernel onto the local system by extracting the RPM with the " +":command:`rpm2cpio` command." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:407 +msgid "Update the |CL| boot manager using :command:`clr-boot-manager` and reboot." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:417 +msgid "After a reboot, verify the customized kernel is running." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:424 +msgid "Related topics" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:426 +msgid ":ref:`kernel-modules`" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:427 +msgid ":ref:`mixer`" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/kernel/kernel-modules-dkms.mo b/locale/de/LC_MESSAGES/guides/kernel/kernel-modules-dkms.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/kernel/kernel-modules-dkms.mo differ diff --git a/locale/de/LC_MESSAGES/guides/kernel/kernel-modules-dkms.po b/locale/de/LC_MESSAGES/guides/kernel/kernel-modules-dkms.po new file mode 100644 index 00000000..4344ce30 --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/kernel/kernel-modules-dkms.po @@ -0,0 +1,483 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"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:18 +msgid "Description" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:20 +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:25 +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 `on GitHub`_." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:39 +msgid "Install DKMS" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:43 +msgid "" +"The *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:46 +msgid "The *kernel-native-dkms* bundle also:" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:48 +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 `." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:53 +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:57 +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:62 +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:68 +msgid "" +"Install the :command:`kernel-native-dkms` or :command:`kernel-lts-dkms` " +"bundle:" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:71 +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:80 +msgid "Ensure *.native* or *.lts* is in the kernel name." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:82 +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:90 +msgid "or" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:97 +msgid "Update the |CL| bootloader and reboot." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:108 +msgid "Build, install, and load an out-of-tree module" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:110 +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 "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:117 +msgid "Prerequisites" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:119 +msgid "Before you begin, you must:" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:121 +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:124 +msgid "" +"Obtain a kernel module package in the form of source code and/or " +"precompiled binaries." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:130 +msgid "Obtain kernel module source" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:132 +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:135 +msgid "Kernel modules may come packaged as:" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:137 +msgid "Source code without a :file:`dkms.conf` file" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:138 +msgid "Source code with a premade :file:`dkms.conf` file" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:139 +msgid "" +"Source code with a premade :file:`dkms.conf` file and precompiled module " +"binaries" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:141 +msgid "Precompiled module binaries only (without source code)" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:143 +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:149 +msgid "Download the kernel module's source code." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:151 +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:154 +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:166 +msgid "Build kernel module with an existing dkms.conf" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:168 +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:172 +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:177 +msgid "" +"Run the :command:`dkms ldtarball` command against the kernel module " +"archive." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:184 +msgid "" +":command:`dkms ldtarball` places the kernel module source under " +":file:`/usr/src/-/`, builds it if necessary," +" and adds the module into the DKMS tree." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:189 +msgid "" +"Verify the kernel module is detected by checking the output of the " +":command:`dkms status` command." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:197 +msgid "Install the kernel module." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:206 +msgid "Build kernel module without an existing dkms.conf" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:208 +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:212 +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:216 +msgid "Here are some additional resources that can be used for reference:" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:218 +msgid "" +"DKMS manual page (:command:`man dkms`) shows detailed syntax in the " +"DKMS.CONF section." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:221 +msgid "" +"`Ubuntu community wiki`_ shows an example where a single package contains" +" multiple modules." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:224 +msgid "`Sample dkms.conf file`_ in the GitHub\\* repository for the DKMS project." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:228 +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:231 +msgid "The instructions below show a generic example:" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:233 +msgid "" +"Create or modify the :file:`dkms.conf` file inside of the extracted " +"source code directory." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:249 +msgid "" +"This example identifies a kernel module named *custom_module* with " +"version *1.0*." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:252 +msgid "Copy the kernel module source code into the :file:`/usr/src/` directory." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:261 +msgid "" +"** and ** must match the entries in the " +":file:`dkms.conf` file." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:265 +msgid "Add the kernel module to the DKMS tree so that it is tracked by DKMS." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:271 +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:278 +msgid "Install the kernel module using DKMS." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:287 +msgid "Load kernel module" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:289 +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:292 +msgid "Load the installed module with the :command:`modprobe` command." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:298 +msgid "Validate the kernel module is loaded." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:306 +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:316 +msgid "Related topics" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:318 +msgid "" +"`Dynamic Kernel Module System (DKMS) project on GitHub " +"`_" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:320 +msgid "" +"`Dell Linux Engineering Dynamic Kernel Module Support: From Theory to " +"Practice " +"`_" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:322 +msgid "" +"`Linux Journal: Exploring Dynamic Kernel Module Support " +"`_" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/kernel/kernel-modules.mo b/locale/de/LC_MESSAGES/guides/kernel/kernel-modules.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/kernel/kernel-modules.mo differ diff --git a/locale/de/LC_MESSAGES/guides/kernel/kernel-modules.po b/locale/de/LC_MESSAGES/guides/kernel/kernel-modules.po new file mode 100644 index 00000000..a6dadc38 --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/kernel/kernel-modules.po @@ -0,0 +1,267 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"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:17 +msgid "Description" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:19 +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:28 +msgid "Kernel module availability" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:30 +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:35 +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:40 +msgid "Check if the module is already available" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:43 +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:53 +msgid "Submit a request to add the module" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:55 +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:59 +msgid "Make enhancement requests to the |CL| distribution `on GitHub`_." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:65 +msgid "Build, install, and load an out-of-tree module" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:67 +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 "" + +#: ../../guides/kernel/kernel-modules.rst:74 +msgid "Prerequisites" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:76 +msgid "Before you begin, you must:" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:78 +msgid "Disable Secure Boot." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:79 +msgid "Disable kernel module integrity checking." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:80 +msgid "Have a kernel module package in the form of source code." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:81 +msgid "Rebuild the module against new versions of the Linux kernel." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:85 +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:90 +msgid "Build and install kernel module" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:92 +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:100 +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:104 +msgid "`linux-dev` for developing against the native kernel." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:105 +msgid "`linux-lts-dev` for developing against the LTS kernel." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:111 +msgid "" +"Follow instructions from the kernel module source code to compile the " +"kernel module. For example:" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:124 +msgid "Load kernel module" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:126 +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:130 +msgid "" +"Disable signature checking for the kernel by modifying the kernel boot " +"parameters and reboot the system." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:133 +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:142 +msgid "" +"Update the boot manager and reboot the system to implement the changed " +"kernel parameters." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:152 +msgid "" +"If successful, the :command:`clr-boot-manager update` command does not " +"return any console output." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:155 +msgid "" +"After rebooting, manually load out-of-tree modules using the " +":command:`insmod` command." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:163 +msgid "Examples" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:168 +msgid "Optional: Specify module options and aliases" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:170 +msgid "Use the :command:`modprobe` command to load a module and set options." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:172 +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:180 +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:185 +msgid "Learn more about :command:`modprobe` on the modprobe.d manual page:" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:192 +msgid "Optional: Configure kernel modules to load at boot" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:194 +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:201 +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:205 +msgid "Learn more about module loading in the modules-load.d manual page:" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:215 +msgid "Related topic" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:217 +msgid ":ref:`kernel-modules-dkms`" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/maintenance/architect-lifecycle.mo b/locale/de/LC_MESSAGES/guides/maintenance/architect-lifecycle.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/maintenance/architect-lifecycle.mo differ diff --git a/locale/de/LC_MESSAGES/guides/maintenance/architect-lifecycle.po b/locale/de/LC_MESSAGES/guides/maintenance/architect-lifecycle.po new file mode 100644 index 00000000..df13bcac --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/maintenance/architect-lifecycle.po @@ -0,0 +1,137 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 provides DevOps with a model to architect the life-cycle of a " +"|CL| derivative that integrates custom software and content using " +"distinct workflows." +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:10 +msgid "Maintaining a |CL| derivative requires:" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:12 +msgid "Monitoring upstream |CL| for new releases" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:13 +msgid "Building software packages and staging" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:14 +msgid "Employing CI/CD automation for building releases" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:15 +msgid "Integrating Quality Assurance for testing and validation" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:17 +msgid "This guide provides the foundation of the recommended infrastructure." +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:24 +msgid "Prerequisites" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:26 +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:29 +msgid "Experience using :ref:`mixer ` to create a |CL|-based distro" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:31 +msgid "" +"Experience using :ref:`swupd ` for maintaining the |CL| " +"build environment" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:34 +msgid "Familiarity with |CL| architecture and reuse of its content in releases" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:37 +msgid "Description" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:39 +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 "" + +#: ../../guides/maintenance/architect-lifecycle.rst:48 +msgid "Figure 1: Architect the life-cycle" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:51 +msgid "Content workflow" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:53 +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:57 +msgid "Release workflow" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:59 +msgid "" +"The *Release Workflow* (Figure 1) gathers the content of the RPMs and " +"ensures it can be consumed by :ref:`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:68 +msgid "Implementation" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:70 +msgid "" +"Distro factory implements the *Release workflow*. To get started on a " +"full implementation, visit |CL| `Distro factory documentation`_." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/maintenance/assign-static-ip.mo b/locale/de/LC_MESSAGES/guides/maintenance/assign-static-ip.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/maintenance/assign-static-ip.mo differ diff --git a/locale/de/LC_MESSAGES/guides/maintenance/assign-static-ip.po b/locale/de/LC_MESSAGES/guides/maintenance/assign-static-ip.po new file mode 100644 index 00000000..e8a36566 --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/maintenance/assign-static-ip.po @@ -0,0 +1,211 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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:6 +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 "" + +#: ../../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| 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, you " +"should 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 and the " +"instructions for :ref:`using NetworkManager ` should be " +"used." +msgstr "" + +#: ../../guides/maintenance/assign-static-ip.rst:43 +msgid "" +"If the STATE column for the device shows *unmanaged*, check to see 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 and the instructions " +"for :ref:`using systemd-networkd ` should be used." +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 "The output will look like this:" +msgstr "" + +#: ../../guides/maintenance/assign-static-ip.rst:95 +msgid "" +"If a connection does not exist, it will need to be created with " +":command:`nmcli connection add`." +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. *[CONNECTION_NAME]* should be " +"replaced with the NAME from the command above." +msgstr "" + +#: ../../guides/maintenance/assign-static-ip.rst:112 +msgid "" +"See the `nmcli developer page " +"`_ 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 doesn't exist " +"already:" +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. *[INTERFACE_NAME]* " +"should be replaced with LINK from the output of :command:`networkctl " +"list` ran previously." +msgstr "" + +#: ../../guides/maintenance/assign-static-ip.rst:168 +msgid "" +"See the `systemd-network man page " +"`_" +" for more configuration options." +msgstr "" + +#: ../../guides/maintenance/assign-static-ip.rst:172 +msgid "Restart the systemd-networkd service:" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/maintenance/bulk-provision.mo b/locale/de/LC_MESSAGES/guides/maintenance/bulk-provision.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/maintenance/bulk-provision.mo differ diff --git a/locale/de/LC_MESSAGES/guides/maintenance/bulk-provision.po b/locale/de/LC_MESSAGES/guides/maintenance/bulk-provision.po new file mode 100644 index 00000000..47c5eae9 --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/maintenance/bulk-provision.po @@ -0,0 +1,201 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"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 "" + +#: ../../guides/maintenance/bulk-provision.rst:11 +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 "" + +#: ../../guides/maintenance/bulk-provision.rst:17 +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:23 +msgid "Figure 1: Bulk provision information flow" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:26 +msgid "Prerequisites" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:28 +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` using :abbr:`NAT (network " +"address translation)` for details." +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:33 +msgid "" +"Because a bulk provision relies on a reboot, ensure the following " +"preparations have been made:" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:36 +msgid "No existing disks are bootable." +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:37 +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:41 +msgid "Configuration" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:43 +msgid "" +"Install **ICIS** by following the getting started guide on the `ICIS " +"GitHub repository`_." +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:46 +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:85 +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 "" + +#: ../../guides/maintenance/bulk-provision.rst:90 +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:99 +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:114 +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:118 +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 "" + +#: ../../guides/maintenance/bulk-provision.rst:123 +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:127 +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 "" + +#: ../../guides/maintenance/bulk-provision.rst:137 +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:146 +msgid "Verify the following URLs are accessible on your local network:" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:148 +msgid "``http://192.168.1.1:60000/icis/static/ister/ister.conf``" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:149 +msgid "``http://192.168.1.1:60000/icis/static/ister/ister.json``" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:150 +msgid "``http://192.168.1.1:60000/icis/get_config/``" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:151 +msgid "``http://192.168.1.1:60000/icis/get_role/``" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:152 +msgid "``http://192.168.1.1:60000/ipxe/ipxe_boot_script.txt``" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:154 +msgid "Power on the PXE client and watch it boot and install |CL|." +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:156 +msgid "Power-cycle the PXE client and watch it customize the |CL| installation." +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:158 +msgid "" +"**Congratulations!** You have successfully performed a bulk provision of " +"|CL|." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/maintenance/cpu-performance.mo b/locale/de/LC_MESSAGES/guides/maintenance/cpu-performance.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/maintenance/cpu-performance.mo differ diff --git a/locale/de/LC_MESSAGES/guides/maintenance/cpu-performance.po b/locale/de/LC_MESSAGES/guides/maintenance/cpu-performance.po new file mode 100644 index 00000000..8f73d394 --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/maintenance/cpu-performance.po @@ -0,0 +1,257 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"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:9 +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:18 +msgid "CPU power saving mechanisms" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:20 +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:27 +msgid "C-states (idle states)" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:29 +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:32 +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:35 +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:39 +msgid "To view the current cpuidle driver run this command in a terminal:" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:45 +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:51 +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:53 +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:59 +msgid "P-states (performance states)" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:61 +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 "" + +#: ../../guides/maintenance/cpu-performance.rst:65 +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:68 +msgid "" +"P-states can typically be limited or disabled in a system's firmware " +"(UEFI/BIOS)." +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:71 +msgid "Turbo boost" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:73 +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 "" + +#: ../../guides/maintenance/cpu-performance.rst:78 +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:81 +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:89 +msgid "Linux CPU clock frequency scaling" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:91 +msgid "" +"The CPUFreq subsystem in Linux allows the OS to control :ref:`C-states ` and :ref:`P-states ` via CPU drivers " +"and governors that provide algorithms that define how and when to enter " +"these states." +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:97 +msgid "Scaling driver" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:99 +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 "" + +#: ../../guides/maintenance/cpu-performance.rst:104 +msgid "" +"To view the current CPU frequency scaling driver run this command in a " +"terminal:" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:111 +msgid "Scaling governor" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:113 +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:119 +msgid "" +"To view the current CPU frequency scaling governor run this command in a " +"terminal:" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:125 +msgid "To change the CPU frequency scaling governor:" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:127 +msgid "Disable |CL| enforcement of certain power and performance settings:" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:133 +msgid "" +"Change the governor. In the example below, the governor is set to " +"*performance*:" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:140 +msgid "" +"The list of all governors can be found in the `Linux kernel documentation" +" on CPUFreq Governors`_." +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:145 +msgid "" +"The intel_pstate driver only supports *performance* and *powersave* " +"governors." +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:148 +msgid "Thermal management" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:150 +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:155 +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:164 +msgid "For more information, see the thermald man page:" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:170 +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 "" + +#: ../../guides/maintenance/cpu-performance.rst:182 +msgid "" +"After adding a new group you must log out and log back in for the new " +"group to take affect." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/maintenance/developer-workstation.mo b/locale/de/LC_MESSAGES/guides/maintenance/developer-workstation.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/maintenance/developer-workstation.mo differ diff --git a/locale/de/LC_MESSAGES/guides/maintenance/developer-workstation.po b/locale/de/LC_MESSAGES/guides/maintenance/developer-workstation.po new file mode 100644 index 00000000..283c668f --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/maintenance/developer-workstation.po @@ -0,0 +1,196 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"*Developer Workstation* helps you find the :ref:`bundles-about` you need " +"to start your |CL-ATTR| development project." +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:9 +msgid "" +"Before continuing, we recommend that you learn how to use :ref:`swupd " +"`. Visit our :ref:`swupd-about` page to understand how |CL| " +"simplifies software versioning compared to other Linux\\* distributions." +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:15 +msgid "Workstation Setup" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:17 +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* `. 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 "" + +#: ../../guides/maintenance/developer-workstation.rst:25 +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 "" + +#: ../../guides/maintenance/developer-workstation.rst:29 +msgid "**Table 1. Developer Profiles**" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:33 +msgid "|CL| Bundle" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:34 +msgid "*Internet of Things (IoT)*" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:35 +msgid "*System Administrator*" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:36 +msgid "*Client/Cloud/Web Developer*" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:38 +msgid "`editors`" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:39 +#: ../../guides/maintenance/developer-workstation.rst:40 +#: ../../guides/maintenance/developer-workstation.rst:41 +#: ../../guides/maintenance/developer-workstation.rst:44 +#: ../../guides/maintenance/developer-workstation.rst:45 +#: ../../guides/maintenance/developer-workstation.rst:46 +#: ../../guides/maintenance/developer-workstation.rst:49 +#: ../../guides/maintenance/developer-workstation.rst:50 +#: ../../guides/maintenance/developer-workstation.rst:51 +#: ../../guides/maintenance/developer-workstation.rst:55 +#: ../../guides/maintenance/developer-workstation.rst:56 +#: ../../guides/maintenance/developer-workstation.rst:60 +#: ../../guides/maintenance/developer-workstation.rst:61 +#: ../../guides/maintenance/developer-workstation.rst:65 +#: ../../guides/maintenance/developer-workstation.rst:66 +#: ../../guides/maintenance/developer-workstation.rst:69 +#: ../../guides/maintenance/developer-workstation.rst:70 +#: ../../guides/maintenance/developer-workstation.rst:71 +#: ../../guides/maintenance/developer-workstation.rst:76 +msgid "✓" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:43 +msgid "`network-basic`" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:48 +msgid "`openssh-server`" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:53 +msgid "`webserver-basic`" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:58 +msgid "`application-server`" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:63 +msgid "`database-basic`" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:68 +msgid "`desktop-autostart`" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:73 +msgid "`dev-utils`" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:79 +msgid "`swupd` search" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:81 +msgid "" +"We recommend learning about :ref:`swupd `, to learn the " +"commands to search for and add bundles relevant to your project." +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:84 +msgid "" +"The guide provides an :ref:`example `" +" that shows you how to:" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:87 +msgid "Use `swupd` to search for bundles" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:88 +msgid "Use `swupd` to add bundles" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:91 +msgid "Core Concepts" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:93 +msgid "" +"We recommend that you understand these core concepts in |CL| *before* " +"developing your project." +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:96 +msgid ":ref:`Bundles `" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:97 +msgid ":ref:`Software update `" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:98 +msgid ":ref:`Mixer `" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:99 +msgid ":ref:`Autospec `" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:102 +msgid "Other resources for developers" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:104 +msgid "`Developer Tooling Framework`_ for |CL|" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:105 +msgid "`Bundle definition files`_" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-linux.mo b/locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-linux.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-linux.mo differ diff --git a/locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-linux.po b/locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-linux.po new file mode 100644 index 00000000..2bd2ccf6 --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-linux.po @@ -0,0 +1,282 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" + diff --git a/locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-mac.mo b/locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-mac.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-mac.mo differ diff --git a/locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-mac.po b/locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-mac.po new file mode 100644 index 00000000..5e08c128 --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-mac.po @@ -0,0 +1,273 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" + diff --git a/locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-windows.mo b/locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-windows.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-windows.mo differ diff --git a/locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-windows.po b/locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-windows.po new file mode 100644 index 00000000..928bbb5d --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/maintenance/download-verify-decompress-windows.po @@ -0,0 +1,277 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" + diff --git a/locale/de/LC_MESSAGES/guides/maintenance/enable-user-space.mo b/locale/de/LC_MESSAGES/guides/maintenance/enable-user-space.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/maintenance/enable-user-space.mo differ diff --git a/locale/de/LC_MESSAGES/guides/maintenance/enable-user-space.po b/locale/de/LC_MESSAGES/guides/maintenance/enable-user-space.po new file mode 100644 index 00000000..6c14ed97 --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/maintenance/enable-user-space.po @@ -0,0 +1,155 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 section 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 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 ``." +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:35 +msgid "" +"To be able to execute all applications with root privileges, add the " +"`` to the `wheel group`_." +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:38 +msgid "Add `` to the `wheel` group:" +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:44 +msgid "Log out of root and into the new ``." +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 `` and the password created earlier." +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:50 +msgid "You will now be in the home directory of ``." +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 ` allows you to " +"perform system updates while reaping the benefits of upstream " +"development." +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:57 +msgid "To update your newly installed OS, run:" +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:64 +msgid "Add a bundle" +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:66 +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 "" + +#: ../../guides/maintenance/enable-user-space.rst:72 +msgid "" +"For example, the `sysadmin-basic` bundle installs the majority of " +"applications useful to a system administrator. To install it, enter:" +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:78 +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:80 +msgid "" +"Expand your knowledge of :command:`swupd` and check out our developer " +"resources:" +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:82 +msgid ":ref:`swupd-guide`" +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:83 +msgid ":ref:`developer-workstation`" +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:86 +msgid "Next steps" +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:88 +msgid "Check out our guides and tutorials." +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:90 +msgid ":ref:`guides`" +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:91 +msgid ":ref:`tutorials`" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/maintenance/fix-broken-install.mo b/locale/de/LC_MESSAGES/guides/maintenance/fix-broken-install.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/maintenance/fix-broken-install.mo differ diff --git a/locale/de/LC_MESSAGES/guides/maintenance/fix-broken-install.po b/locale/de/LC_MESSAGES/guides/maintenance/fix-broken-install.po new file mode 100644 index 00000000..befb7e98 --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/maintenance/fix-broken-install.po @@ -0,0 +1,159 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 of |CL-ATTR|" +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:6 +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 "" + +#: ../../guides/maintenance/fix-broken-install.rst:10 +msgid "" +"This process can only verify and fix files that :ref:`swupd`" +" owns in :file:`/usr`. Files outside of this path, such as /home/, /etc, " +"/var, etc., cannot be repaired by this process." +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:15 +msgid "Prerequisites" +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:17 +msgid "" +":ref:`Download and install the live desktop image on a USB `" +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:20 +msgid "Boot a live desktop image to fix target system" +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:22 +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:29 +msgid "Mount root partition, verify, and fix" +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:31 +msgid "Open a Terminal window." +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:33 +msgid "Assure the system is connected to the network." +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:35 +msgid "Mount the system’s root partition." +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:37 +msgid "To find the root partition, run:" +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:43 +msgid "We'll use `/dev/sda3/` as the root partition example." +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:45 +msgid "Next, mount the partition to the `/mnt` folder." +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:51 +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:59 +msgid "Next, run swupd to fix any issues on the target system." +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:65 +msgid ":ref:`Learn more about how swupd works `." +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:67 +msgid "After the process is complete, unmount the root partition:" +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:73 +msgid "" +"Reboot the system, remove the live desktop USB drive, and boot into the " +"repaired system." +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:80 +msgid "**Congratulations!** You successfully restored |CL|." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/maintenance/hostname.mo b/locale/de/LC_MESSAGES/guides/maintenance/hostname.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/maintenance/hostname.mo differ diff --git a/locale/de/LC_MESSAGES/guides/maintenance/hostname.po b/locale/de/LC_MESSAGES/guides/maintenance/hostname.po new file mode 100644 index 00000000..49c9c89b --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/maintenance/hostname.po @@ -0,0 +1,110 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 on |CL-ATTR|" +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:9 +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:17 +msgid "*regression-test*" +msgstr "" + +#: ../../guides/maintenance/hostname.rst:18 +msgid "*sally-test-box1*" +msgstr "" + +#: ../../guides/maintenance/hostname.rst:19 +msgid "*az-bldg2-lab*" +msgstr "" + +#: ../../guides/maintenance/hostname.rst:22 +msgid "Set your hostname" +msgstr "" + +#: ../../guides/maintenance/hostname.rst:24 +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 "" + +#: ../../guides/maintenance/hostname.rst:28 +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:39 +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:44 +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:48 +msgid "" +"The pretty hostname is a free-form UTF8 name used for presentation to the" +" user." +msgstr "" + +#: ../../guides/maintenance/hostname.rst:51 +msgid "View your hostname" +msgstr "" + +#: ../../guides/maintenance/hostname.rst:53 +msgid "View your current hostname using the following command:" +msgstr "" + +#: ../../guides/maintenance/hostname.rst:59 +msgid "You should see output similar to:" +msgstr "" + +#: ../../guides/maintenance/hostname.rst:74 +msgid "" +"**Congratulations!** You successfully modified the hostname of your |CL| " +"system." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/maintenance/increase-virtual-disk-size.mo b/locale/de/LC_MESSAGES/guides/maintenance/increase-virtual-disk-size.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/maintenance/increase-virtual-disk-size.mo differ diff --git a/locale/de/LC_MESSAGES/guides/maintenance/increase-virtual-disk-size.po b/locale/de/LC_MESSAGES/guides/maintenance/increase-virtual-disk-size.po new file mode 100644 index 00000000..b2dfd8ac --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/maintenance/increase-virtual-disk-size.po @@ -0,0 +1,245 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 a |CL-ATTR| image" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:6 +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 "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:10 +msgid "This guide will cover:" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:13 +msgid "Determine the partition order and sizes of the prebuilt image" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:15 +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:18 +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 "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:22 +msgid "Checking :command:`lsblk` on the VM" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:24 +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:31 +msgid "An example output of the :command:`lsblk` command:" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:41 +msgid "An example of this can also be seen in Figure 1." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:44 +msgid "Checking :file:`config.json` used to build the image" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:46 +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:51 +msgid "Go to the `releases`_ repository." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:52 +msgid "Drill down into the `20450 > clear > config > image` directory." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:53 +msgid "Open the :file:`hyperv-config.json` file." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:54 +msgid "Locate the `PartitionLayout` key." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:56 +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:76 +msgid "Increase virtual disk size" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:77 +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:81 +msgid "Power off VM and increase virtual disk size:" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:83 +msgid "" +"To increase the virtual disk size for a prebuilt image, perform the steps" +" below:" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:86 +msgid "Shut down your VM if it is running." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:87 +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:90 +msgid "Power up the VM." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:94 +msgid "Resize the partition of the virtual disk:" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:96 +msgid "Log in to an account with root privileges." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:97 +msgid "Open a terminal emulator." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:98 +msgid "" +"Add the |CL| `storage-utils` bundle to install the :command:`parted` and " +":command:`resize2fs` tools." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:105 +msgid "Launch the `parted` tool." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:111 +msgid "In the `parted` tool, perform these steps:" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:113 +msgid "Press :command:`p` to print the partitions table." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:114 +msgid "If the warning message below is displayed, enter :command:`Fix`." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:124 +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:126 +msgid "Enter :command:`yes` when prompted." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:127 +msgid "Enter the new `End` size." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:131 +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 "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:136 +msgid "An example of this can be seen in Figure 1." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:138 +msgid "" +"Enter :command:`q` to exit `parted` when you are finished resizing the " +"image." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:141 +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:147 +msgid "Figure 1: Increase root partition size." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:150 +msgid "Resize the filesytem" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:152 +msgid "" +"Enter :command:`sudo resize2fs -p /dev/[modified partition name]` where " +"*[modified partition name]* is the partition that was changed in " +"`parted`." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:155 +msgid "Run the :command:`df -h` to verify that the filesystem size has increased." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:158 +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:164 +msgid "Figure 2: Increase root filesystem size after partition has been expanded." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:166 +msgid "" +"Congratulations! You have resized the disk, partition, and filesystem. At" +" this point, the increase in disk capacity is usable." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/maintenance/time.mo b/locale/de/LC_MESSAGES/guides/maintenance/time.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/maintenance/time.mo differ diff --git a/locale/de/LC_MESSAGES/guides/maintenance/time.po b/locale/de/LC_MESSAGES/guides/maintenance/time.po new file mode 100644 index 00000000..48c75bf6 --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/maintenance/time.po @@ -0,0 +1,78 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "|CL-ATTR| uses the `systemd-timesyncd.service` daemon to synchronize time." +msgstr "" + +#: ../../guides/maintenance/time.rst:8 +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 "" + +#: ../../guides/maintenance/time.rst:11 +msgid "Install the `sysadmin-basic` bundle." +msgstr "" + +#: ../../guides/maintenance/time.rst:17 +msgid "Set your time zone. This example uses Los Angeles." +msgstr "" + +#: ../../guides/maintenance/time.rst:25 +msgid "" +"To see a list of time zones, use the command: :command:`timedatectl list-" +"timezones | grep `" +msgstr "" + +#: ../../guides/maintenance/time.rst:28 +msgid "Create a :file:`/etc/systemd/` directory." +msgstr "" + +#: ../../guides/maintenance/time.rst:34 +msgid "" +"Create a new file named :file:`/etc/systemd/timesyncd.conf` and enter the" +" following text." +msgstr "" + +#: ../../guides/maintenance/time.rst:43 +msgid "Enable the `systemd-timesyncd` service." +msgstr "" + +#: ../../guides/maintenance/time.rst:51 +msgid "" +"To check the service status, use the :command:`timedatectl status` " +"command." +msgstr "" + +#: ../../guides/maintenance/time.rst:53 +msgid "" +"To restart the `timesyncd` daemon, enter :command:`systemctl restart " +"systemd-timesyncd` into your terminal emulator." +msgstr "" + +#: ../../guides/maintenance/time.rst:56 +msgid "**Congratulations!** You successfully set up the time in your |CL| system." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/maintenance/validate-signatures.mo b/locale/de/LC_MESSAGES/guides/maintenance/validate-signatures.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/maintenance/validate-signatures.mo differ diff --git a/locale/de/LC_MESSAGES/guides/maintenance/validate-signatures.po b/locale/de/LC_MESSAGES/guides/maintenance/validate-signatures.po new file mode 100644 index 00000000..82f9392d --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/maintenance/validate-signatures.po @@ -0,0 +1,142 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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:6 +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 "" + +#: ../../guides/maintenance/validate-signatures.rst:11 +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 "" + +#: ../../guides/maintenance/validate-signatures.rst:18 +msgid "Image content validation" +msgstr "" + +#: ../../guides/maintenance/validate-signatures.rst:20 +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 "" + +#: ../../guides/maintenance/validate-signatures.rst:23 +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:35 +msgid "Generate the SHA256 sum of the |CL| certificate." +msgstr "" + +#: ../../guides/maintenance/validate-signatures.rst:41 +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:48 +msgid "Generate the SHA512 sum of the image and save it to a file." +msgstr "" + +#: ../../guides/maintenance/validate-signatures.rst:54 +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 "" + +#: ../../guides/maintenance/validate-signatures.rst:64 +#: ../../guides/maintenance/validate-signatures.rst:115 +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 "" + +#: ../../guides/maintenance/validate-signatures.rst:69 +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:73 +msgid "Update content validation" +msgstr "" + +#: ../../guides/maintenance/validate-signatures.rst:75 +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 "" + +#: ../../guides/maintenance/validate-signatures.rst:80 +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:92 +msgid "Generate the SHA256 sum of the Swupd certificate." +msgstr "" + +#: ../../guides/maintenance/validate-signatures.rst:98 +msgid "" +"Ensure the generated SHA256 sum of the Swupd certificate matches " +"following SHA256 sum to verify the integrity of the certificate." +msgstr "" + +#: ../../guides/maintenance/validate-signatures.rst:105 +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 "" + +#: ../../guides/maintenance/validate-signatures.rst:122 +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:126 +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 "" + diff --git a/locale/de/LC_MESSAGES/guides/network/custom-clear-container.mo b/locale/de/LC_MESSAGES/guides/network/custom-clear-container.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/network/custom-clear-container.mo differ diff --git a/locale/de/LC_MESSAGES/guides/network/custom-clear-container.po b/locale/de/LC_MESSAGES/guides/network/custom-clear-container.po new file mode 100644 index 00000000..446b005f --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/network/custom-clear-container.po @@ -0,0 +1,177 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"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 "" + +#: ../../guides/network/custom-clear-container.rst:11 +msgid "Prerequisites" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:13 +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:16 +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:18 +msgid "You have a basic understanding of Docker." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:21 +msgid "Build the base container image" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:23 +msgid "Log in and get root privileges." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:29 +msgid "Verify Docker is installed and running." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:35 +msgid "If Docker is installed and running, the output is similar to this example:" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:78 +msgid "If Docker is not installed, enter the commands:" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:85 +msgid "Use `os-install` to download and install the bundles." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:92 +msgid "The `swupd` example uses the following flags:" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:94 +msgid ":command:`os-install` tells `swupd` to download and install." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:95 +msgid ":command:`-V / --version` specifies the version of the |CL| bundles." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:96 +msgid ":command:`--url` specifies the URL of the bundles repository." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:97 +msgid "" +":command:`--statedir` specifies the state directory where downloaded " +"bundles and any state information are stored." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:99 +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:102 +msgid "" +"For more information on `swupd` flags, enter the :command:`swupd os-" +"install -h` command." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:104 +#: ../../guides/network/custom-clear-container.rst:167 +#: ../../guides/network/custom-clear-container.rst:194 +#: ../../guides/network/custom-clear-container.rst:228 +#: ../../guides/network/custom-clear-container.rst:290 +msgid "Example output:" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:141 +msgid "The `WARNING` message is expected and can be ignored." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:143 +msgid "Create a tarball and compress it." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:150 +msgid "Create the Dockerfile to build the image." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:161 +msgid "Build the |CL| container image." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:188 +msgid "List the newly created |CL| container image." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:201 +msgid "Launch the built |CL| container." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:208 +msgid "Manage bundles in a container" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:210 +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:214 +msgid "Add a bundle" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:216 +msgid "" +"This example Dockerfile adds the :file:`pxe-server` bundle to an existing" +" |CL| Docker image:" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:272 +msgid "" +"The `WARNING` message can be ignored because systemd does not run inside " +"a container." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:276 +msgid "Remove a bundle" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:278 +msgid "" +"This example Dockerfile removes the :file:`pxe-server` bundle from an " +"existing |CL| Docker image:" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/network/dpdk.mo b/locale/de/LC_MESSAGES/guides/network/dpdk.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/network/dpdk.mo differ diff --git a/locale/de/LC_MESSAGES/guides/network/dpdk.po b/locale/de/LC_MESSAGES/guides/network/dpdk.po new file mode 100644 index 00000000..86dac763 --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/network/dpdk.po @@ -0,0 +1,376 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 document describes how to send packets between two platforms in the " +"simple configuration shown in :ref:`Figure 1 `. 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:17 +msgid "Figure 1: Environment for l3fwd DPDK application" +msgstr "" + +#: ../../guides/network/dpdk.rst:19 +msgid "This example uses the following DPDK components:" +msgstr "" + +#: ../../guides/network/dpdk.rst:21 +msgid "pktgen: Traffic generator. See `pktgen documentation`_ for details." +msgstr "" + +#: ../../guides/network/dpdk.rst:22 +msgid "" +"l3fwd: Layer 3 forwarding example application. See `l3fwd documentation`_" +" for details." +msgstr "" + +#: ../../guides/network/dpdk.rst:26 +msgid "Prerequisites" +msgstr "" + +#: ../../guides/network/dpdk.rst:28 +msgid "Two platforms using |CL-ATTR| release `13330`_ or higher." +msgstr "" + +#: ../../guides/network/dpdk.rst:29 +msgid "Both images must include the :file:`kernel-native bundle`." +msgstr "" + +#: ../../guides/network/dpdk.rst:30 +msgid "Install the :file:`network-basic-dev` bundle with the command:" +msgstr "" + +#: ../../guides/network/dpdk.rst:36 +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:39 +msgid "Two network cables." +msgstr "" + +#: ../../guides/network/dpdk.rst:42 +msgid "Install dpdk and build l3fwd example (Platform B)" +msgstr "" + +#: ../../guides/network/dpdk.rst:44 +msgid "Change to the :file:`l3fwd` example directory." +msgstr "" + +#: ../../guides/network/dpdk.rst:50 +msgid "Assign :envvar:`RTE_SDK` variable to the makefiles path." +msgstr "" + +#: ../../guides/network/dpdk.rst:56 +msgid "" +"Assign :envvar:`RTE_TARGET` variable to the location of the gcc\\* config" +" file." +msgstr "" + +#: ../../guides/network/dpdk.rst:63 +msgid "" +"Build the `l3fwd` application and add the configuration header to the " +":makevar:`CFLAGS` variable." +msgstr "" + +#: ../../guides/network/dpdk.rst:72 +msgid "Build pktgen (Platform A)" +msgstr "" + +#: ../../guides/network/dpdk.rst:74 +msgid "Download the `pktgen tar package`_ v3.1.2 or newer." +msgstr "" + +#: ../../guides/network/dpdk.rst:76 +msgid "Decompress packages and move to uncompressed source directory." +msgstr "" + +#: ../../guides/network/dpdk.rst:78 +msgid "Assign :envvar:`RTE_SDK` variable to the path where makefiles are located." +msgstr "" + +#: ../../guides/network/dpdk.rst:84 +msgid "Assign :envvar:`RTE_TARGET` to the location of the gcc config file." +msgstr "" + +#: ../../guides/network/dpdk.rst:90 +msgid "" +"Build the `pktgen` project and set the " +":makevar:`CONFIG_RTE_BUILD_SHARED_LIB` variable to \"n\"." +msgstr "" + +#: ../../guides/network/dpdk.rst:98 +msgid "Bind NICs to DPDK kernel drivers (Platforms A and B)" +msgstr "" + +#: ../../guides/network/dpdk.rst:100 +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:103 +msgid "Load the DPDK I/O kernel module." +msgstr "" + +#: ../../guides/network/dpdk.rst:109 +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:117 +msgid "" +"Bind two available NICs. The general syntax for binding is: :command" +":`dpdk-devbind --bind=vfio-pci `. A working example is " +"shown below:" +msgstr "" + +#: ../../guides/network/dpdk.rst:125 +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:131 +msgid "Set hugepages (Platforms A and B)" +msgstr "" + +#: ../../guides/network/dpdk.rst:133 +msgid "" +"|CL| supports `hugepages` for the large memory pool allocation used for " +"packet buffers." +msgstr "" + +#: ../../guides/network/dpdk.rst:136 +msgid "Set the number of hugepages." +msgstr "" + +#: ../../guides/network/dpdk.rst:142 +msgid "Allocate pages on NUMA machines." +msgstr "" + +#: ../../guides/network/dpdk.rst:149 +msgid "Make memory available for DPDK." +msgstr "" + +#: ../../guides/network/dpdk.rst:155 +msgid "" +"For more information, refer to the `DPDK guide`_ System Requirements " +"section." +msgstr "" + +#: ../../guides/network/dpdk.rst:160 +msgid "Set up the physical environment (Platforms A and B)" +msgstr "" + +#: ../../guides/network/dpdk.rst:162 +msgid "" +"Connect the NICs on Platform A to the NICs on Platform B using the " +"network cables as shown in :ref:`Figure 2`." +msgstr "" + +#: ../../guides/network/dpdk.rst:169 +msgid "Figure 2: Physical network environment" +msgstr "" + +#: ../../guides/network/dpdk.rst:173 +msgid "Run l3fwd application (Platform B)" +msgstr "" + +#: ../../guides/network/dpdk.rst:175 +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:179 +msgid "Open the l3fwd example directory." +msgstr "" + +#: ../../guides/network/dpdk.rst:185 +msgid "**This step is very important.**" +msgstr "" + +#: ../../guides/network/dpdk.rst:187 +msgid "DPDK needs poll mode drivers to operate." +msgstr "" + +#: ../../guides/network/dpdk.rst:188 +msgid "Poll mode drivers are shared objects in :file:`/usr/lib64`." +msgstr "" + +#: ../../guides/network/dpdk.rst:189 +msgid "See the full list of supported NICs at `dpdk.org NICs`_." +msgstr "" + +#: ../../guides/network/dpdk.rst:190 +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:193 +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:197 +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:205 +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:209 +msgid "Save the MAC address for configuring the `pktgen` project." +msgstr "" + +#: ../../guides/network/dpdk.rst:212 +msgid "Run pktgen application (Platform A)" +msgstr "" + +#: ../../guides/network/dpdk.rst:214 +msgid "`pktgen` is a network traffic generator included in the DPDK." +msgstr "" + +#: ../../guides/network/dpdk.rst:216 +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:224 +msgid "Enable active colorful output (optional)." +msgstr "" + +#: ../../guides/network/dpdk.rst:230 +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:237 ../../guides/network/dpdk.rst:296 +#: ../../guides/network/dpdk.rst:314 +msgid "Here is a working example:" +msgstr "" + +#: ../../guides/network/dpdk.rst:244 +msgid "Send packets." +msgstr "" + +#: ../../guides/network/dpdk.rst:250 +msgid "For more details, see the `pktgen documentation`_." +msgstr "" + +#: ../../guides/network/dpdk.rst:253 +msgid "Appendix A: Use pass-through for virtual machines" +msgstr "" + +#: ../../guides/network/dpdk.rst:255 +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:258 +msgid "Create a new directory and move to it." +msgstr "" + +#: ../../guides/network/dpdk.rst:260 +msgid "" +"Download or create a :file:`start_qemu.sh` script for running a kvm " +"virtual machine:" +msgstr "" + +#: ../../guides/network/dpdk.rst:267 +msgid "Download a bare-metal image of |CL| and rename it as :file:`clear.img`." +msgstr "" + +#: ../../guides/network/dpdk.rst:269 +msgid "Look for an Ethernet\\* device entry that contains vendor and device ID:" +msgstr "" + +#: ../../guides/network/dpdk.rst:275 +msgid "An example output:" +msgstr "" + +#: ../../guides/network/dpdk.rst:281 +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:286 +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:305 +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:321 +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:328 +msgid "" +"Here is a working example for a virtual machine with 4096 memory and four" +" CPUs:" +msgstr "" + +#: ../../guides/network/dpdk.rst:336 +msgid "Each NUMA machine must use the same quantity of memory." +msgstr "" + +#: ../../guides/network/dpdk.rst:338 +msgid "Run the :file:`start_qemu.sh` script." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/network/ipxe-install.mo b/locale/de/LC_MESSAGES/guides/network/ipxe-install.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/network/ipxe-install.mo differ diff --git a/locale/de/LC_MESSAGES/guides/network/ipxe-install.po b/locale/de/LC_MESSAGES/guides/network/ipxe-install.po new file mode 100644 index 00000000..36ed2863 --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/network/ipxe-install.po @@ -0,0 +1,314 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 |CL-ATTR| 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)`." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:9 +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:13 +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:18 +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:24 +msgid "Figure 1: PXE information flow." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:28 +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:33 +msgid "Prerequisites" +msgstr "" + +#: ../../guides/network/ipxe-install.rst:35 +msgid "Before booting with iPXE, make the following preparations." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:37 +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:43 +msgid "Figure 2: Network topology." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:45 +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:48 +msgid "Your PXE server must have:" +msgstr "" + +#: ../../guides/network/ipxe-install.rst:50 +msgid "Ethernet/LAN boot option." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:51 +msgid "At least two network adapters." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:52 +msgid "Connection to a public network." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:53 +msgid "Secure boot option disabled." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:57 +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:62 +msgid "Configuration" +msgstr "" + +#: ../../guides/network/ipxe-install.rst:64 +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 "" + +#: ../../guides/network/ipxe-install.rst:68 +msgid "To set up |CL| manually, perform the steps below." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:70 +msgid "Define the variables used for iPXE boot configuration." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:86 +msgid "Log in and get root privilege." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:92 +msgid "" +"Add the `pxe-server` bundle to your |CL| system. The bundle contains all " +"files needed to run a PXE server." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:99 +msgid "" +"Download the latest network-bootable release of |CL| and extract the " +"files." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:113 +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:117 +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:133 +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 "" + +#: ../../guides/network/ipxe-install.rst:155 +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:159 +msgid "Start `nginx` and enable the startup on boot option." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:166 +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 "" + +#: ../../guides/network/ipxe-install.rst:180 +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:196 +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:212 +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:215 +msgid "" +"Configure the kernel to forward network packets to different interfaces. " +"Otherwise, NAT will not work." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:224 +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 "" + +#: ../../guides/network/ipxe-install.rst:234 +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 "" + +#: ../../guides/network/ipxe-install.rst:245 +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:255 +msgid "" +"Add the options to host a DHCP server for PXE clients to the `dnsmasq` " +"configuration file." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:277 +msgid "The configuration provides the following important functions:" +msgstr "" + +#: ../../guides/network/ipxe-install.rst:279 +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:282 +msgid "" +"Activates only on the network adapter that has an IP address on the " +"defined subnet." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:284 +msgid "Directs PXE clients to the DNS server." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:285 +msgid "Directs PXE clients to the PXE server for routing via NAT." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:286 +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:290 +msgid "" +"Create a file for `dnsmasq` to record the IP addresses it provides to PXE" +" clients." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:298 +msgid "Start `dnsmasq` and enable startup on boot." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:305 +msgid "Start `systemd-resolved`." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:313 +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:318 +msgid "Power on the PXE client and watch the client boot and install |CL|." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:320 +msgid "" +"After booting, |CL| automatically partitions the hard drive, installs " +"itself, updates to the latest version, and reboots." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:324 +msgid "" +"**Congratulations!** You have successfully installed and configured a PXE" +" server that enables PXE clients to boot and install |CL| over the " +"network." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/network/network-bonding.mo b/locale/de/LC_MESSAGES/guides/network/network-bonding.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/network/network-bonding.mo differ diff --git a/locale/de/LC_MESSAGES/guides/network/network-bonding.po b/locale/de/LC_MESSAGES/guides/network/network-bonding.po new file mode 100644 index 00000000..df3f9cc1 --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/network/network-bonding.po @@ -0,0 +1,153 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"Network bonding combines multiple network interfaces into a single " +"logical interface to provide redundancy and bandwidth aggregation." +msgstr "" + +#: ../../guides/network/network-bonding.rst:9 +msgid "" +"|CL-ATTR| includes Linux bonding_ and team_ drivers. This guide describes" +" how to configure systemd to use the `bonding` driver." +msgstr "" + +#: ../../guides/network/network-bonding.rst:12 +msgid "The example demonstrates how to:" +msgstr "" + +#: ../../guides/network/network-bonding.rst:14 +msgid "Bond all four ports of a quad-port NIC in `802.3ad` mode." +msgstr "" + +#: ../../guides/network/network-bonding.rst:16 +msgid "Enable jumbo frames to optimize large data transfers on the local network." +msgstr "" + +#: ../../guides/network/network-bonding.rst:18 +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:24 +msgid "You must run all commands in this guide as root." +msgstr "" + +#: ../../guides/network/network-bonding.rst:26 +msgid "Log in and get root privileges." +msgstr "" + +#: ../../guides/network/network-bonding.rst:32 +msgid "Create the :file:`/etc/systemd/network` directory." +msgstr "" + +#: ../../guides/network/network-bonding.rst:38 +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:42 +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:57 +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:61 +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:76 +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:81 +msgid "" +"For best results, do not assign addresses or DHCP support to the " +"individual NICs." +msgstr "" + +#: ../../guides/network/network-bonding.rst:84 +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:87 +msgid "Configure the bonded interface in a file named :file:`30-bond1.network`." +msgstr "" + +#: ../../guides/network/network-bonding.rst:101 +msgid "`bond1` is a virtual interface with no physical link status." +msgstr "" + +#: ../../guides/network/network-bonding.rst:103 +msgid "" +"`BindCarrier` indicates that the `bond1` link status is determined by the" +" status of the listed slave devices." +msgstr "" + +#: ../../guides/network/network-bonding.rst:106 +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:109 +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:113 +msgid "Apply the new network configuration with the command:" +msgstr "" + +#: ../../guides/network/network-bonding.rst:119 +msgid "" +"The `MTUBytes` settings do not take effect until you reboot or manually " +"apply the settings with a utility such as `ifconfig`." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/network/vnc.mo b/locale/de/LC_MESSAGES/guides/network/vnc.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/network/vnc.mo differ diff --git a/locale/de/LC_MESSAGES/guides/network/vnc.po b/locale/de/LC_MESSAGES/guides/network/vnc.po new file mode 100644 index 00000000..0cf56ed8 --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/network/vnc.po @@ -0,0 +1,921 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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/vnc.rst:4 +msgid "Remote-desktop to a |CL-ATTR| host using VNC" +msgstr "" + +#: ../../guides/network/vnc.rst:6 +msgid "" +":abbr:`VNC (Virtual Network Computing)` is a client-server GUI-based tool" +" that allows you to connect via remote-desktop to your |CL-ATTR| host." +msgstr "" + +#: ../../guides/network/vnc.rst:9 +msgid "This guide shows you how to:" +msgstr "" + +#: ../../guides/network/vnc.rst:11 +msgid "Install the VNC server and misc. components on your |CL| host." +msgstr "" + +#: ../../guides/network/vnc.rst:12 +msgid "Configure a VNC-server-start method on your |CL| host." +msgstr "" + +#: ../../guides/network/vnc.rst:13 +msgid "Install a VNC viewer app and an SSH client on your client system." +msgstr "" + +#: ../../guides/network/vnc.rst:14 +msgid "Establish a VNC connection to your |CL| host." +msgstr "" + +#: ../../guides/network/vnc.rst:15 +msgid "Terminate a VNC connection to your |CL| host." +msgstr "" + +#: ../../guides/network/vnc.rst:16 +msgid "Encrypt VNC traffic through an SSH tunnel." +msgstr "" + +#: ../../guides/network/vnc.rst:19 +msgid "Install the VNC server and misc. components on your host" +msgstr "" + +#: ../../guides/network/vnc.rst:21 +msgid "To configure VNC to work on your |CL| host, install these bundles:" +msgstr "" + +#: ../../guides/network/vnc.rst:23 +msgid "" +"`desktop-autostart`: Installs :abbr:`GDM (Gnome Desktop Manager)`, sets " +"it to start automatically on boot, and installs TigerVNC Viewer." +msgstr "" + +#: ../../guides/network/vnc.rst:25 +msgid "`vnc-server`: Installs the TigerVNC server." +msgstr "" + +#: ../../guides/network/vnc.rst:27 +msgid "Follow these steps:" +msgstr "" + +#: ../../guides/network/vnc.rst:29 +msgid "Log into your |CL| host and get root privileges." +msgstr "" + +#: ../../guides/network/vnc.rst:35 +msgid "Install the |CL| bundles." +msgstr "" + +#: ../../guides/network/vnc.rst:41 +msgid "Reboot your |CL| host." +msgstr "" + +#: ../../guides/network/vnc.rst:44 +msgid "Configure a VNC-server-start method on your host" +msgstr "" + +#: ../../guides/network/vnc.rst:46 +msgid "" +"There are three methods you can use to configure and start the VNC server" +" on your |CL| host:" +msgstr "" + +#: ../../guides/network/vnc.rst:49 +msgid "Table 1: VNC-server-start Configuration Methods" +msgstr "" + +#: ../../guides/network/vnc.rst:53 +msgid "Attribute" +msgstr "" + +#: ../../guides/network/vnc.rst:54 +msgid "`Method 1`: Manually start a VNC session" +msgstr "" + +#: ../../guides/network/vnc.rst:55 +msgid "`Method 2`: Automatically start a VNC session via a systemd service script" +msgstr "" + +#: ../../guides/network/vnc.rst:56 +msgid "`Method 3`: Create multi-user logins with authentication through GDM" +msgstr "" + +#: ../../guides/network/vnc.rst:57 +msgid "Description" +msgstr "" + +#: ../../guides/network/vnc.rst:58 +msgid "" +"This is the traditional method where you SSH into the |CL| host, manually" +" start a VNC session to get a display ID, and connect to it by supplying " +"the display ID." +msgstr "" + +#: ../../guides/network/vnc.rst:61 +msgid "" +"The system administrator sets up a systemd service script for you with a " +"pre-assigned display ID. You make a VNC connection and supply your pre-" +"assigned display ID." +msgstr "" + +#: ../../guides/network/vnc.rst:64 +msgid "" +"The system adminstrator configures GDM to accept connection requests. " +"When you make a VNC connection to the |CL| host, you see the GDM login " +"screen and authenticate as if you are local." +msgstr "" + +#: ../../guides/network/vnc.rst:67 +msgid "Who configures VNC settings?" +msgstr "" + +#: ../../guides/network/vnc.rst:68 ../../guides/network/vnc.rst:72 +#: ../../guides/network/vnc.rst:76 ../../guides/network/vnc.rst:77 +msgid "You" +msgstr "" + +#: ../../guides/network/vnc.rst:69 ../../guides/network/vnc.rst:70 +msgid "System adminstrator" +msgstr "" + +#: ../../guides/network/vnc.rst:71 +msgid "Who starts VNC session?" +msgstr "" + +#: ../../guides/network/vnc.rst:73 ../../guides/network/vnc.rst:74 +msgid "Set to start automatically on boot by system administrator" +msgstr "" + +#: ../../guides/network/vnc.rst:75 +msgid "Who ends VNC sesssion?" +msgstr "" + +#: ../../guides/network/vnc.rst:78 +msgid "System administrator can disable VNC service altogether" +msgstr "" + +#: ../../guides/network/vnc.rst:79 +msgid "Requires VNC password to authenticate?" +msgstr "" + +#: ../../guides/network/vnc.rst:80 ../../guides/network/vnc.rst:81 +msgid "Yes" +msgstr "" + +#: ../../guides/network/vnc.rst:82 +msgid "No. Use |CL| account username and password through GDM" +msgstr "" + +#: ../../guides/network/vnc.rst:85 +msgid "" +"Although all three methods can coexist on the same |CL| host, we " +"recommend you pick a method that suits your needs." +msgstr "" + +#: ../../guides/network/vnc.rst:88 +msgid "" +"For simplicity, the rest of this guide refers to these methods as `Method" +" 1`, `Method 2`, and `Method 3`." +msgstr "" + +#: ../../guides/network/vnc.rst:92 +msgid "Method 1: Manually start a VNC session" +msgstr "" + +#: ../../guides/network/vnc.rst:94 +msgid "" +"You (and each user) must perform these steps to initialize your VNC " +"settings." +msgstr "" + +#: ../../guides/network/vnc.rst:96 +msgid "Log in." +msgstr "" + +#: ../../guides/network/vnc.rst:97 ../../guides/network/vnc.rst:557 +msgid "Open a terminal emulator." +msgstr "" + +#: ../../guides/network/vnc.rst:98 +msgid "" +"Start VNC with the :command:`vncserver` command. Since this is your " +"first time starting VNC, it adds default configuration files and asks you" +" to set a VNC password." +msgstr "" + +#: ../../guides/network/vnc.rst:106 ../../guides/network/vnc.rst:431 +msgid "Example output:" +msgstr "" + +#: ../../guides/network/vnc.rst:126 +msgid "" +"Upon completion, you can find the default configuration files and the " +"password file hidden in the `.vnc` directory in your home directory." +msgstr "" + +#: ../../guides/network/vnc.rst:129 +msgid "" +"Also, a VNC session starts and shows a unique display ID, which is the " +"number following the hostname and the colon `:`. In the above example, " +"the display ID is 2. In a later step, you will supply the display ID to " +"your VNC viewer app for connection." +msgstr "" + +#: ../../guides/network/vnc.rst:133 +msgid "" +"Kill the active VNC session for the time being with the " +":command:`vncserver -kill :[display ID]` command. Substitute [display " +"ID] with your active VNC session display ID. For example:" +msgstr "" + +#: ../../guides/network/vnc.rst:143 +msgid "" +"If you do not recall the active session display ID, use the " +":command:`vncserver -list` command to find it." +msgstr "" + +#: ../../guides/network/vnc.rst:146 +msgid "Optional configurations:" +msgstr "" + +#: ../../guides/network/vnc.rst:148 +msgid "" +"To customize settings such as screen size, security type, etc., modify " +"the :file:`$HOME/.vnc/config` file." +msgstr "" + +#: ../../guides/network/vnc.rst:150 +msgid "" +"To customize the applications to run at startup, modify the " +":file:`$HOME/.vnc/xstartup` file." +msgstr "" + +#: ../../guides/network/vnc.rst:154 +msgid "Method 2: Automatically start a VNC session via a systemd service script" +msgstr "" + +#: ../../guides/network/vnc.rst:156 +msgid "" +"To configure VNC for this method, you must have root privileges. You " +"will set up a systemd service file for all intended VNC users with their " +"own preassigned unique display ID." +msgstr "" + +#: ../../guides/network/vnc.rst:160 ../../guides/network/vnc.rst:244 +msgid "Log in and get root privileges." +msgstr "" + +#: ../../guides/network/vnc.rst:166 +msgid "" +"Make sure the user accounts already exist. Use the following command to " +"list all users." +msgstr "" + +#: ../../guides/network/vnc.rst:174 ../../guides/network/vnc.rst:250 +msgid "Create the path :file:`/etc/systemd/system`." +msgstr "" + +#: ../../guides/network/vnc.rst:180 +msgid "" +"Create a systemd service script file :file:`vncserver@:[X].service`, " +"where [X] is the display ID, for each user in :file:`/etc/systemd/system`" +" Each user must be assigned a unique display ID. Be sure the correct " +"username is entered in the `User` field. The example below shows user " +"`vnc-user-b` who is assigned the display ID `5`." +msgstr "" + +#: ../../guides/network/vnc.rst:208 +msgid "" +"Have each user log into their account and set a VNC password with the " +":command:`vncpasswd` command before proceeding to the next step." +msgstr "" + +#: ../../guides/network/vnc.rst:211 +msgid "" +"Start the VNC service script and set it to start automatically on boot " +"for each user. Replace the [X] with the display ID." +msgstr "" + +#: ../../guides/network/vnc.rst:220 +msgid "After starting the services, verify they are running." +msgstr "" + +#: ../../guides/network/vnc.rst:226 +msgid "" +"The example below shows 2 VNC sessions that were successfully started for" +" users `vnc-user-b` with display ID 5 and `vnc-user-c` with display ID 6." +msgstr "" + +#: ../../guides/network/vnc.rst:238 +msgid "Method 3: Multi-user logins with authentication through GDM" +msgstr "" + +#: ../../guides/network/vnc.rst:240 +msgid "" +"For this method, VNC is configured as a systemd service that listens on " +"port 5900 and GDM is configured to accept access requests from VNC. When " +"you make a VNC connection to your |CL| host, you are presented with the " +"GDM login screen and you authenticate as if you are local. You must have" +" root privileges to perform this configuration." +msgstr "" + +#: ../../guides/network/vnc.rst:256 +msgid "Create a systemd socket file :file:`xvnc.socket` and add the following:" +msgstr "" + +#: ../../guides/network/vnc.rst:274 +msgid "Create a systemd service file :file:`xvnc@.service` and add the following:" +msgstr "" + +#: ../../guides/network/vnc.rst:291 +msgid "Create the path :file:`/etc/gdm`." +msgstr "" + +#: ../../guides/network/vnc.rst:298 +msgid "Create a GDM :file:`custom.conf` file and add the following:" +msgstr "" + +#: ../../guides/network/vnc.rst:310 +msgid "Start the VNC socket script and set it to start automatically on boot." +msgstr "" + +#: ../../guides/network/vnc.rst:318 +msgid "After starting the socket, verify it is running." +msgstr "" + +#: ../../guides/network/vnc.rst:324 +msgid "The example below shows the xvnc.socket is running." +msgstr "" + +#: ../../guides/network/vnc.rst:333 +msgid "See the `vncserver` Man page for additional information." +msgstr "" + +#: ../../guides/network/vnc.rst:336 +msgid "Install a VNC viewer app and an SSH client on your client system" +msgstr "" + +#: ../../guides/network/vnc.rst:338 +msgid "" +"You need a VNC viewer app on your client system to connect to your |CL| " +"host. An SSH client is only needed if you chose to use `Method 1` or you " +"plan to encrypt your VNC traffic, which is discussed later in this guide." +msgstr "" + +#: ../../guides/network/vnc.rst:342 +msgid "Perform the steps below to add these apps to your client system." +msgstr "" + +#: ../../guides/network/vnc.rst:345 +msgid "Install a VNC viewer app" +msgstr "" + +#: ../../guides/network/vnc.rst:347 +msgid "On |CL|:" +msgstr "" + +#: ../../guides/network/vnc.rst:353 +msgid "On Ubuntu, Mint:" +msgstr "" + +#: ../../guides/network/vnc.rst:359 +msgid "On Fedora:" +msgstr "" + +#: ../../guides/network/vnc.rst:365 ../../guides/network/vnc.rst:407 +msgid "On Windows:" +msgstr "" + +#: ../../guides/network/vnc.rst:367 +msgid "Install `RealVNC for Windows`_" +msgstr "" + +#: ../../guides/network/vnc.rst:369 +msgid "On macOS:" +msgstr "" + +#: ../../guides/network/vnc.rst:371 +msgid "Install `RealVNC for macOS`_" +msgstr "" + +#: ../../guides/network/vnc.rst:374 +msgid "Install an SSH client" +msgstr "" + +#: ../../guides/network/vnc.rst:376 +msgid "" +"On most Linux distros (|CL|, Ubuntu, Mint, Fedora, etc.) and macOS, SSH " +"is built-in so you don't need to install it." +msgstr "" + +#: ../../guides/network/vnc.rst:378 +msgid "On Windows, you can install `Putty`_." +msgstr "" + +#: ../../guides/network/vnc.rst:381 +msgid "Establish a VNC connection to your host" +msgstr "" + +#: ../../guides/network/vnc.rst:383 +msgid "" +"Depending on the VNC-server-configuration method chosen, use the " +"appropriate VNC connection:" +msgstr "" + +#: ../../guides/network/vnc.rst:385 +msgid "" +"If you chose `Method 1`, you must take a few extra steps by using SSH to " +"connect to your |CL| host and then manually launching VNC." +msgstr "" + +#: ../../guides/network/vnc.rst:388 +msgid "" +"If you chose `Method 2`, get your preassigned VNC display ID from your " +"system administrator first and then proceed to the :ref:`connect-to-vnc-" +"session` section below." +msgstr "" + +#: ../../guides/network/vnc.rst:392 +msgid "" +"If you chose `Method 3`, proceed to the :ref:`connect-to-vnc-session` " +"below." +msgstr "" + +#: ../../guides/network/vnc.rst:397 +msgid "SSH into your host and launch VNC" +msgstr "" + +#: ../../guides/network/vnc.rst:399 +msgid "SSH into your |CL| host" +msgstr "" + +#: ../../guides/network/vnc.rst:401 +msgid "On Linux distros and macOS:" +msgstr "" + +#: ../../guides/network/vnc.rst:409 ../../guides/network/vnc.rst:724 +msgid "Launch Putty." +msgstr "" + +#: ../../guides/network/vnc.rst:410 ../../guides/network/vnc.rst:727 +msgid "" +"Under the :guilabel:`Category` section, select :guilabel:`Session`. See " +"Figure 1." +msgstr "" + +#: ../../guides/network/vnc.rst:412 ../../guides/network/vnc.rst:729 +msgid "" +"Enter the IP address of your |CL| host in the :guilabel:`Host Name (or IP" +" address)` field." +msgstr "" + +#: ../../guides/network/vnc.rst:414 ../../guides/network/vnc.rst:731 +msgid "Set the :guilabel:`Connection type` option to :guilabel:`SSH`." +msgstr "" + +#: ../../guides/network/vnc.rst:415 ../../guides/network/vnc.rst:753 +msgid "Click the :guilabel:`Open` button." +msgstr "" + +#: ../../guides/network/vnc.rst:421 +msgid "Figure 1: Putty - configure SSH session settings" +msgstr "" + +#: ../../guides/network/vnc.rst:423 +msgid "Log in with your |CL| username and password. Do not use your VNC password." +msgstr "" + +#: ../../guides/network/vnc.rst:425 +msgid "Start a VNC session." +msgstr "" + +#: ../../guides/network/vnc.rst:442 +msgid "" +"Take note of the generated display ID because you will input it into the " +"VNC viewer app to establish the connection. The above example shows the " +"display ID is 3." +msgstr "" + +#: ../../guides/network/vnc.rst:448 +msgid "" +"VNC automatically picks a unique display ID unless you specify one. To " +"specify a display ID, enter a unique number that is not already in use " +"after the colon. For example:" +msgstr "" + +#: ../../guides/network/vnc.rst:456 +msgid "" +"You can now end the SSH connection by logging out. This does not " +"terminate your active VNC session." +msgstr "" + +#: ../../guides/network/vnc.rst:462 +msgid "Connect to your VNC session" +msgstr "" + +#: ../../guides/network/vnc.rst:464 +msgid "" +"For `Method 1` and `Method 2`, you must connect to a specific active " +"session or display ID using one of two options:" +msgstr "" + +#: ../../guides/network/vnc.rst:467 +msgid "" +"Use a fully-qualified VNC port number, which consists of the default VNC " +"server port (5900) plus the display ID" +msgstr "" + +#: ../../guides/network/vnc.rst:469 +msgid "Use the display ID" +msgstr "" + +#: ../../guides/network/vnc.rst:471 +msgid "" +"For example, if the display ID is 3, it can be specified as `5903` or " +"just as `3`. For `Method 3`, VNC does not expect a display ID. Use " +"`5900`. For simplicity, the instructions below use the fully-qualified " +"VNC port number." +msgstr "" + +#: ../../guides/network/vnc.rst:475 ../../guides/network/vnc.rst:762 +msgid "**On Linux distros:**" +msgstr "" + +#: ../../guides/network/vnc.rst:477 +msgid "Open a terminal emulator and enter:" +msgstr "" + +#: ../../guides/network/vnc.rst:483 ../../guides/network/vnc.rst:512 +msgid "Enter your credentials." +msgstr "" + +#: ../../guides/network/vnc.rst:485 ../../guides/network/vnc.rst:514 +msgid "" +"For `Method 1` and `Method 2`, enter your VNC password. No username is " +"required." +msgstr "" + +#: ../../guides/network/vnc.rst:487 ../../guides/network/vnc.rst:516 +msgid "For `Method 3`, enter your |CL| account username and password through GDM." +msgstr "" + +#: ../../guides/network/vnc.rst:492 ../../guides/network/vnc.rst:521 +msgid "" +"With `Method 3`, you cannot remotely log into your |CL| host through VNC " +"if you are logged in locally and vice versa." +msgstr "" + +#: ../../guides/network/vnc.rst:495 +msgid "**On Windows and macOS using `RealVNC` app:**" +msgstr "" + +#: ../../guides/network/vnc.rst:497 +msgid "Start the RealVNC viewer app. See Figure 2." +msgstr "" + +#: ../../guides/network/vnc.rst:498 +msgid "" +"Enter the IP address of the |CL| host and the fully-qualified VNC port " +"number." +msgstr "" + +#: ../../guides/network/vnc.rst:501 +msgid "" +"The following screenshot shows connecting to |CL| host 192.168.25.54 with" +" a fully-qualified VNC port number 5902." +msgstr "" + +#: ../../guides/network/vnc.rst:508 +msgid "Figure 2: RealVNC Viewer" +msgstr "" + +#: ../../guides/network/vnc.rst:510 +msgid "Press the :kbd:`Enter` key." +msgstr "" + +#: ../../guides/network/vnc.rst:525 +msgid "`Optional: Configure RealVNC Image Quality`" +msgstr "" + +#: ../../guides/network/vnc.rst:527 +msgid "" +"To increase the RealVNC viewer image quality, manually change the " +"`ColorLevel` value. Follow these steps:" +msgstr "" + +#: ../../guides/network/vnc.rst:529 +msgid "" +"Right-click a connection node and select :guilabel:`Properties...`. See " +"Figure 3." +msgstr "" + +#: ../../guides/network/vnc.rst:536 +msgid "Figure 3: RealVNC Viewer - change connection node properties" +msgstr "" + +#: ../../guides/network/vnc.rst:538 +msgid "Select the :guilabel:`Expert` tab. See Figure 4." +msgstr "" + +#: ../../guides/network/vnc.rst:540 +msgid "" +"Select the :guilabel:`ColorLevel` setting and change it to your preferred" +" setting." +msgstr "" + +#: ../../guides/network/vnc.rst:547 +msgid "Figure 4: RealVNC Viewer - change :guilabel:`ColorLevel`" +msgstr "" + +#: ../../guides/network/vnc.rst:550 +msgid "Terminate a VNC connection to your host" +msgstr "" + +#: ../../guides/network/vnc.rst:552 +msgid "" +"For `Method 1` and `Method 2`, once started, a VNC session remains active" +" on your |CL| host even if you close your VNC viewer app. If you want to " +"truly terminate an active VNC session, follow these steps:" +msgstr "" + +#: ../../guides/network/vnc.rst:556 +msgid "SSH into your |CL| host." +msgstr "" + +#: ../../guides/network/vnc.rst:558 +msgid "" +"Find the active VNC session display ID with the command " +":command:`vncserver -list`." +msgstr "" + +#: ../../guides/network/vnc.rst:565 +msgid "" +"Terminate it with the :command:`vncserver -kill` command followed by a " +"colon and the display ID." +msgstr "" + +#: ../../guides/network/vnc.rst:572 +msgid "" +"For `Method 3`, only the system administrator can stop and disable the " +"VNC service by using these commands:" +msgstr "" + +#: ../../guides/network/vnc.rst:582 +msgid "Encrypt VNC traffic through an SSH tunnel" +msgstr "" + +#: ../../guides/network/vnc.rst:584 +msgid "" +"By default, VNC traffic is not encrypted. Figure 6 shows an example " +"warning from RealVNC Viewer." +msgstr "" + +#: ../../guides/network/vnc.rst:591 +msgid "Figure 6: RealVNC Viewer - Connection not encrypted warning" +msgstr "" + +#: ../../guides/network/vnc.rst:593 +msgid "" +"To add security, VNC traffic can be routed through an SSH tunnel. This is" +" accomplished by following these steps:" +msgstr "" + +#: ../../guides/network/vnc.rst:595 +msgid "" +"Configure the VNC server to only accept connection from localhost by " +"adding the `-localhost` option." +msgstr "" + +#: ../../guides/network/vnc.rst:597 +msgid "" +"Set up an SSH tunnel between your client system and your |CL| host. Your " +"client system will forward traffic from the localhost (the client) " +"destined for a specified fully-qualified VNC port number (on the client) " +"to your |CL| host with the same port number." +msgstr "" + +#: ../../guides/network/vnc.rst:601 +msgid "" +"The VNC viewer app on your client system will now connect to localhost, " +"instead of the IP address of your |CL| host." +msgstr "" + +#: ../../guides/network/vnc.rst:605 +msgid "Configure VNC to only accept connection from localhost" +msgstr "" + +#: ../../guides/network/vnc.rst:607 +msgid "For `Method 1`:" +msgstr "" + +#: ../../guides/network/vnc.rst:609 +msgid "" +"Edit the :file:`config` file located in :file:`$HOME/.vnc` and uncomment " +"the `# localhost` line. It should look like this:" +msgstr "" + +#: ../../guides/network/vnc.rst:625 +msgid "If an active session exists, kill it, and then restart it." +msgstr "" + +#: ../../guides/network/vnc.rst:627 +msgid "For `Method 2`:" +msgstr "" + +#: ../../guides/network/vnc.rst:629 +msgid "" +"Edit the systemd service script :file:`vncserver@:[X].service` located in" +" :file:`/etc/systemd/system` and add `-localhost` to the `ExecStart` " +"line. The example below uses vncserver@:5.service:" +msgstr "" + +#: ../../guides/network/vnc.rst:651 +msgid "Restart the service script:" +msgstr "" + +#: ../../guides/network/vnc.rst:658 +msgid "For `Method 3`:" +msgstr "" + +#: ../../guides/network/vnc.rst:660 +msgid "No change is needed to the :file:`xvnc@service` script." +msgstr "" + +#: ../../guides/network/vnc.rst:662 +msgid "" +"After you have restarted your VNC session, you can verify that it only " +"accepts connections from localhost by using the :command:`netstat` " +"command like this:" +msgstr "" + +#: ../../guides/network/vnc.rst:672 +msgid "Add the |CL| `network-basic` bundle to get the :command:`netstat` command." +msgstr "" + +#: ../../guides/network/vnc.rst:675 +msgid "" +"Figure 7 shows two VNC sessions (5901 and 5905) accepting connections " +"from any host as specified by the `0.0.0.0`'s. This is before the " +"`-localhost` option was used." +msgstr "" + +#: ../../guides/network/vnc.rst:682 +msgid "Figure 7: VNC sessions (5901 and 5905) accepting connections from any host" +msgstr "" + +#: ../../guides/network/vnc.rst:684 +msgid "" +"Figure 8 shows two VNC sessions (5901 and 5905) only accepting " +"connections from localhost as specified by `127.0.0.1`'s. This is after " +"the `-localhost` option was used." +msgstr "" + +#: ../../guides/network/vnc.rst:690 +msgid "" +"Figure 8: VNC sessions (5901 and 5905) only accepting connections from " +"localhost" +msgstr "" + +#: ../../guides/network/vnc.rst:693 +msgid "Set up an SSH tunnel from your client system to your |CL| host" +msgstr "" + +#: ../../guides/network/vnc.rst:695 +msgid "**On Linux distros and macOS:**" +msgstr "" + +#: ../../guides/network/vnc.rst:697 ../../guides/network/vnc.rst:764 +msgid "Open terminal emulator and enter:" +msgstr "" + +#: ../../guides/network/vnc.rst:704 ../../guides/network/vnc.rst:754 +msgid "Enter your |CL| account password (not your VNC password)." +msgstr "" + +#: ../../guides/network/vnc.rst:708 +msgid "" +"`-L` specifies that [client port number] on the localhost (on the client " +"side) is forwarded to [fully-qualified VNC port number] (on the server " +"side)." +msgstr "" + +#: ../../guides/network/vnc.rst:711 +msgid "" +"Replace `[client port number]` with an available client port number (for " +"example: 1234). For simplicity, you can make the `[client port number]` " +"the same as the `[fully-qualified VNC port number]`." +msgstr "" + +#: ../../guides/network/vnc.rst:714 +msgid "" +"Replace `[fully-qualified VNC port number]` with 5900 (default VNC port) " +"plus the display ID. For example, if the display ID is 2, the fully-" +"qualified VNC port number is is 5902." +msgstr "" + +#: ../../guides/network/vnc.rst:717 +msgid "`-N` tells SSH to only forward ports and not execute a remote command." +msgstr "" + +#: ../../guides/network/vnc.rst:719 +msgid "`-f` tells SSH to go into the background before command execution." +msgstr "" + +#: ../../guides/network/vnc.rst:720 +msgid "`-l` specifies the username to log in as." +msgstr "" + +#: ../../guides/network/vnc.rst:722 +msgid "**On Windows:**" +msgstr "" + +#: ../../guides/network/vnc.rst:725 +msgid "Specify the |CL| VNC host to connect to." +msgstr "" + +#: ../../guides/network/vnc.rst:733 +msgid "Configure the SSH tunnel. See Figure 9 for an example." +msgstr "" + +#: ../../guides/network/vnc.rst:735 +msgid "" +"Under the :guilabel:`Category` section, go to :guilabel:`Connection` > " +":guilabel:`SSH` > :guilabel:`Tunnels`." +msgstr "" + +#: ../../guides/network/vnc.rst:738 +msgid "" +"In the :guilabel:`Source port` field, enter an available client port " +"number (for example: 1234). For simplicity, you can make the `Source " +"port` the same as the fully-qualified VNC port number." +msgstr "" + +#: ../../guides/network/vnc.rst:742 +msgid "" +"In the :guilabel:`Destination` field, enter `localhost:` plus the fully-" +"qualified VNC port number." +msgstr "" + +#: ../../guides/network/vnc.rst:745 +msgid "Click the :guilabel:`Add` button." +msgstr "" + +#: ../../guides/network/vnc.rst:751 +msgid "Figure 9: Putty - configure SSH tunnel" +msgstr "" + +#: ../../guides/network/vnc.rst:757 +msgid "Connect to a VNC session through an SSH tunnel" +msgstr "" + +#: ../../guides/network/vnc.rst:759 +msgid "" +"After you have set up an SSH tunnel, follow these instructions to connect" +" to your VNC session." +msgstr "" + +#: ../../guides/network/vnc.rst:770 +msgid "**On Windows and macOS using `RealVNC`:**" +msgstr "" + +#: ../../guides/network/vnc.rst:772 +msgid "Start the RealVNC viewer app." +msgstr "" + +#: ../../guides/network/vnc.rst:773 +msgid "" +"Enter `localhost` and the fully-qualified VNC port number. See Figure 10" +" for an example." +msgstr "" + +#: ../../guides/network/vnc.rst:780 +msgid "Figure 10: RealVNC viewer app connecting to `localhost:1234`" +msgstr "" + +#: ../../guides/network/vnc.rst:784 +msgid "" +"RealVNC will still warn that the connection is not encrypted even though " +"its traffic is going through the SSH tunnel. You can ignore this " +"warning." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/guides/telemetrics/telem-guide.mo b/locale/de/LC_MESSAGES/guides/telemetrics/telem-guide.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/guides/telemetrics/telem-guide.mo differ diff --git a/locale/de/LC_MESSAGES/guides/telemetrics/telem-guide.po b/locale/de/LC_MESSAGES/guides/telemetrics/telem-guide.po new file mode 100644 index 00000000..a6d6ec5e --- /dev/null +++ b/locale/de/LC_MESSAGES/guides/telemetrics/telem-guide.po @@ -0,0 +1,942 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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/telemetrics/telem-guide.rst:4 +msgid "Telemetrics" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:6 +msgid "" +"Telemetrics in |CL-ATTR| is a client and server solution used to collect " +"data from running |CL| systems to help quickly identify and fix bugs in " +"the OS. Both client and server are customizable, and an API is available" +" on the client side for instrumenting your code for debug and analysis." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:10 +msgid "" +"Telemetry in |CL| is **opt-in**. The telemetry client is **not** active " +"and sends **no** data until you explicitly enable it." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:14 +msgid "" +"The telemetry functionality adheres to `Intel privacy policies`_ " +"regarding the collection and use of :abbr:`PII (Personally Identifiable " +"Information)` and is open source. Specifically, no intentionally " +"identifiable information about the user or system owner is collected." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:23 +msgid "Description" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:25 +msgid "" +"Telemetry, one of the key features of |CL|, enables developers to observe" +" and proactively address issues in the OS before end users are impacted." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:27 +msgid "Telemetrics is a combination word made from:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:29 +msgid "Telemetry, which is sensing and reporting data." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:30 +msgid "" +"Analytics, which is using visualization and statistical inferencing to " +"make sense of the reported data." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:32 +msgid "" +"|CL| telemetry reports system-level debug/crash information using " +"specialized probes. The probes monitor system tasks such as swupd, kernel" +" oops, machine error checks, and the 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 "" + +#: ../../guides/telemetrics/telem-guide.rst:34 +msgid "" +"|CL| telemetry is fully customizable and can be used during software " +"development for debugging purposes. You can use the libtelemetry library" +" in your code to create custom telemetry records. You can also use the " +"telem-record-gen utility in script files for light touch record creation " +"where instrumenting code files doesn't make sense." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:36 +msgid "" +"The |CL| telemetrics solution is an **opt-in** choice on the client side." +" By default, the telemetry client is disabled until you choose to enable" +" it. Enabling the client is covered in this guide." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:39 +msgid "Architecture" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:41 +msgid "" +"|CL| telemetry has two fundamental components, which are shown in figure " +"1:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:43 +msgid "" +"Client: generates and delivers records to the backend server via the " +"network" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:45 +msgid "" +"Backend: receives records sent from the client and displays the " +"cumulative content through a specialized web interface." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:50 +msgid "Figure 1: :guilabel:`|CL| Telemetry Architecture`" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:52 +msgid "" +"The telemetry client provides the front end of the telemetrics solution " +"and includes the following components:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:54 +msgid "" +"telemprobd, a daemon that receives and prepares telemetry records from " +"probes and spools them to disk." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:55 +msgid "" +"telempostd, a daemon that manages spooled telemetry records and delivers " +"these records according to configurable settings." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:56 +msgid "probes, that collect specific types of data from the operating system." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:57 +msgid "libtelemetry, the API that telemetrics probes use to create records." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:59 +msgid "" +"The telemetry backend provides the server-side component of the " +"telemetrics solution and consists of:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:61 +msgid "Nginx web server." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:62 +msgid "" +"Two Flask apps: * Collector, an ingestion web app for records received " +"from client probes. * TelemetryUI, a web app that exposes different views" +" to visualize the telemetry data." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:65 +msgid "PostgreSQL as the underlying database server." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:69 +msgid "" +"The default telemetry backend server is hosted by the Intel |CL| " +"development team and is not viewable outside the Intel firewall. To " +"collect your own records, you must set up your own telemetry backend " +"server." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:74 +msgid "How To Use" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:76 +msgid "" +"From a workflow perspective, the |CL| telemetrics system is " +"straightforward. On the client side, the main decisions after " +"installation and enabling telemetry concern what to do with the record " +"data generated by the probes. You can send the data to the default or a " +"custom backend server, keep the data local to the system, or both. The " +"backend server has a more complex setup, but once it's running, it is " +"simple to use and configure." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:78 +msgid "" +"This section walks through some of the possible scenarios for configuring" +" the |CL| telemetrics system, and suggests which make sense according to " +"your needs." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:81 +msgid "Scenarios" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:82 +msgid "Enable telemetry" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:84 +msgid "" +"Before probes can generate records, the telemetry client daemons must be " +"enabled. You can configure the client before enabling by creating a " +"custom :file:`telemetrics.conf` file that you place in the " +":file:`/etc/telemetrics` directory. If you choose to use the default " +"settings, records will be sent to the telemetrics backend server managed " +"by the |CL| development team at Intel." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:86 +msgid "Save record data locally" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:88 +msgid "" +"You can configure the telemetry client to save records locally. This is " +"convenient when you want instant feedback during a development cycle, or " +"to track system issues if you believe there is a machine specific " +"problem. The client can be set to not send records at all, or to both " +"keep the records locally and send to the backend server." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:90 +msgid "Set up a server to collect data" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:92 +msgid "" +"Whether you are managing a network of |CL| systems or you don't want to " +"send records to the default telemetry server, you can set up a backend " +"server to collect your records. The backend server can be installed on " +"any Linux system and will give you the same dashboard as the default " +"server." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:95 +#: ../../guides/telemetrics/telem-guide.rst:362 +msgid "Instrument your code with the libtelemetry API" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:97 +msgid "" +"The ``telemetrics`` bundle includes the libtelemetry C library, which " +"exposes an API used by the telemprobd and telempostd daemons. You can use" +" these in your applications as well. The API documentation is found in " +"the :file:`telemetry.h` file in `Telemetrics client`_ repository." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:101 +msgid "Examples" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:108 +msgid "Enable or Disable Telemetry" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:110 +msgid "Enabling during installation" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:112 +msgid "" +"During the initial installation of |CL|, you are requested to join the " +"stability enhancement program and allow |CL| to collect anonymous reports" +" to improve system stability. If you choose not to join this program, " +"then the telemetry software bundle is not added to your system. Choosing " +"to join will automatically enable telemetry on your system after " +"installation is commplete." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:114 +msgid "Enabling after install" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:116 +msgid "To start telemetry on your system, run the following command:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:122 +msgid "" +"This enables and starts the :command:`telemprobd` and " +":command:`telempostd` daemons. Your system will begin to send telemetry " +"data to the server defined in the file " +":file:`/etc/telemetrics/telemetrics.conf`. If this file does not exist, " +"the :command:`telemprobd` and :command:`telempostd` daemons will use the " +"file :file:`/usr/share/defaults/telemetrics/telemetrics.conf`." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:124 +msgid "Disabling after install" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:126 +msgid "To disable both of the telemetry daemons, run the following command:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:132 +msgid "Opt in to telemetry" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:134 +msgid "" +"To opt-in to the telemetry services, simply enter the opt-in command and " +"start the service:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:140 +msgid "" +"This removes the :file:`/etc/telemetrics/opt-out` file, if it exists, and" +" starts the telemetry services." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:144 +msgid "" +"To opt-in but not immediately start telemetry services, you will need to " +"run the command :command:`sudo telemctl stop` after the :command:`opt-in`" +" command is entered. Once you are ready to start the service, enter the " +"command :command:`sudo telemctl start`." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:146 +msgid "Opt out of telemetry" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:148 +msgid "" +"To stop sending telemetrics data from your system, opt out of the " +"telemetry service:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:154 +msgid "" +"This creates the file :file:`/etc/telemetrics/opt-out` and stops the " +"telemetry services." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:158 +msgid "Saving Data Locally" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:160 +msgid "" +"This example requires |CL| to be installed, and telemetry to be enabled " +"on the system." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:162 +msgid "" +"To change how records are managed, we will be copying the default " +":file:`/usr/share/defaults/telemetrics/telemetrics.conf` file to " +":file:`/etc/telemetrics/telemetrics.conf` and editing it. The changes in" +" the :file:`/etc/telemetrics/telemetrics.conf` file will override the " +"defaults in the :file:`/usr/share/defaults/telemetrics/telemetrics.conf` " +"file. You may need ``root`` permissions to create and edit files in " +":file:`/etc`. For each example, and for any time you make changes to the " +"configuration file, you will need to restart the client daemons to pick " +"up the changes:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:169 +msgid "" +"The :command:`telemctl journal` command gives you access to features and " +"options of the telemetry journal to assist with system analytics and " +"debug. :command:`telemctl journal` has a number of options to help filter" +" records. Use :command:`-h` or :command:`--help` to view usage options." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:172 +msgid "Keep local copy and send records to backend server" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:174 +msgid "" +"To keep a local copy of the telemetry record and also send it on to the " +"backend server, we will need to change the " +":guilabel:`record_retention_enabled` configuration key value to " +":guilabel:`true`." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:177 +msgid "Keep all records -- don't send to backend server" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:179 +msgid "" +"To keep records on the system without sending them to a backend server, " +"set the :guilabel:`record_server_delivery_enabled` key value to " +":guilabel:`false`. Note that you will also need to ensure the " +":guilabel:`record_retention_enabled` configuration key value is set to " +":guilabel:`true` or the system will not keep local copies." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:181 +msgid "Keep and send records to custom server" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:183 +msgid "" +"This assumes you have set up a custom server according to the next " +"example." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:185 +msgid "" +"The server is identified by the :guilabel:`server` setting, and by " +"default records will be sent to the |CL| server " +":guilabel:`server=https://clr.telemetry.intel.com/v2/collector`. To " +"change this, you can use an IP address or fully qualified domain name." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:190 +msgid "Set up a backend server to collect telemetry records" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:192 +msgid "" +"For this example, start with a clean installation of |CL| on a new system" +" using the :ref:`bare-metal-install-server` getting started guide and:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:195 +msgid "" +"Join the :guilabel:`Stability Enhancement Program` to install and enable " +"the telemetrics components." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:197 +msgid "Select the manual installation method with the following settings:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:199 +msgid "Set the hostname to :guilabel:`clr-telem-server`," +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:200 +msgid "" +"Create an administrative user named :guilabel:`clear` and add this user " +"to sudoers" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:203 +msgid "" +"Log in with your administrative user, from your :file:`$HOME` directory, " +"run :command:`git` to clone the :guilabel:`telemetrics-backend` " +"repository into the :file:`$HOME/telemetrics-backend` directory:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:211 +msgid "" +"You may need to set up the :envvar:`https_proxy` environment variable if " +"you have issues reaching github.com." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:213 +msgid "" +"Change your current working directory to :file:`telemetrics-" +"backend/scripts`." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:214 +msgid "" +"We will install the telemetrics backend with the :file:`deploy.sh` script" +" file. We will set the following options and leave the remainder as " +"default:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:216 +msgid "*-a install* to perform an install" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:217 +msgid "*-d clr* to install to a |CL| distro" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:218 +msgid "*-H localhost* to set the domain to localhost" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:221 +msgid "" +"The :file:`deploy.sh` shell script has minimal error checking and makes " +"several changes to your system. Be sure that the options you define on " +"the cmdline are correct before proceeding." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:224 +msgid "" +"Run the shell script from the :file:`$HOME/telemetrics-backend/scripts` " +"directory:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:232 +msgid "" +"The script will start and list all the defined options and prompt you for" +" the :guilabel:`PostgreSQL` database password" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:245 +msgid "" +"For the :guilabel:`DB password:`, press the :kbd:`Enter` key to accept " +"the default password `postgres`." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:249 +msgid "" +"The :file:`deploy.sh` script uses :command:`sudo` to run commands and you" +" may be prompted to enter your user password at any time while the script" +" is executing. If this occurs, enter your user password to execute the " +":command:`sudo` command." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:252 +msgid "" +"Once all the server components have been installed you are prompted to " +"enter the :guilabel:`PostgreSQL` database password to change it as " +"illustrated below:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:261 +msgid "" +"Enter `postgres` for the current value of the password and then enter a " +"new password, retype it to verify the new password and the " +":guilabel:`PostgreSQL` database password will be updated." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:263 +msgid "" +"Once the installation is complete you can use your web browser to view " +"the new server by opening the browser on the system and typing in " +"``localhost`` in the address bar. You should see a web page similar to " +"the one shown in figure 1:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:268 +msgid "Figure 1: :guilabel:`Telemetry UI`" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:273 +msgid "Create records with telem-record-gen" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:275 +msgid "" +"The telemetrics bundle provides a record generator tool called ``telem-" +"record-gen``. This tool can be used to create records from shell scripts " +"or the command line when writing a probe in C is not desirable. Records " +"are sent to the backend server, and can also be echoed to stdout." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:277 +msgid "There are three ways to supply the payload to the record." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:279 +msgid "On the command line, use the :command:`-p ` option:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:305 +msgid "" +"Specify a file that contains the payload with the option :command:`-P " +"path/to/file`." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:331 +msgid "" +"If the :command:`-p` or :command:`-P` options are absent, the tool reads " +"from stdin so you can use it in a :file:`heredoc` in scripts." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:365 +msgid "Prerequisites" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:366 +msgid "" +"Confirm that the telemetrics header file is located on the system at " +":file:`usr/include/telemetry.h` The `latest version`_ of the file can " +"also be found on github for reference, but installing the `telemetry` " +"bundle will install the header file that matches your |CL| version." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:368 +msgid "Includes and variables" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:370 +msgid "" +"You will need to include the following headers in your code to use the " +"API:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:381 +msgid "" +"Use the following code to create the variables we need to hold the data " +"for the record we will be creating:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:396 +msgid "Severity:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst +msgid "Type: uint32_t" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst +msgid "" +"Value: Severity field value. Accepted values are in the range 1-4, with " +"1 being the lowest severity, and 4 being the highest severity. Values " +"provided outside of this range are clamped to 1 or 4. [low, med, high, " +"crit]" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:400 +msgid "Payload_version:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst +msgid "" +"Value: Payload format version. The only supported value right now is 1, " +"which indicates that the payload is a freely-formatted (unstructured) " +"string. Values greater than 1 are reserved for future use." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:404 +msgid "Classification:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst +msgid "Type: char array" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst +msgid "" +"Value: It should have the form, DOMAIN/PROBENAME/REST: DOMAIN is the " +"reverse domain to use as a namespace for the probe (e.g. org.clearlinux);" +" PROBENAME is the name of the probe; and REST is an arbitrary value that " +"the probe should use to classify the record. The maximum length for the " +"classification string is 122 bytes. Each sub-category may be no longer " +"than 40 bytes long. Two / delimiters are required." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:408 +msgid "Tm_handle:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst +msgid "Type: Telem_ref struct pointer" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst +msgid "" +"Value: Struct pointer declared by the caller, The struct is initialized " +"if the function returns success." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:414 +msgid "Payload:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst +msgid "Type: char pointer" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst +msgid "Value: The payload to set" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:416 +msgid "For this example, we'll set the payload to “hello” by using ``asprintf()``" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:426 +msgid "" +"The functions ``asprintf()`` and ``vasprintf()`` are analogs of " +"``sprintf(3)`` and ``vsprintf(3)``, except that they allocate a string" +" large enough to hold the output including the terminating null byte " +"('\\0'), and return a pointer to it via the first argument. This pointer" +" should be passed to ``free(3)`` to release the allocated storage when it" +" is no longer needed." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:428 +msgid "Create the new telemetry record" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:430 +msgid "" +"The function ``tm_create_record()`` initializes a telemetry record and " +"sets the severity and classification of that record, as well as the " +"payload version number. The memory needed to store the telemetry record " +"is allocated and should be freed with ``tm_free_record()`` when no longer" +" needed." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:440 +msgid "Set the payload field of a telemetrics record" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:442 +msgid "" +"The function ``tm_set_payload()`` attaches the provided telemetry record " +"data to the telemetry record. The current maximum payload size is 8192b." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:453 +msgid "" +"The ``free()`` function frees the memory space pointed to by ptr, which " +"must have been returned by a previous call to ``malloc()``, ``calloc()``," +" or ``realloc()``. Otherwise, or if ``free(ptr)`` has already been " +"called before, undefined behavior occurs. If ptr is NULL, no operation " +"is performed." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:455 +msgid "Send a record to the telemetrics daemon" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:457 +msgid "" +"The function ``tm_send_record()`` delivers the record to the local " +"``telemprobd(1)`` service. Since the telemetry record was allocated by " +"the program it should be freed with ``tm_free_record()`` when it is no " +"longer needed." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:476 +msgid "Full sample application with compiling flags" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:478 +msgid "Create a new file test.c add the following code." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:533 +msgid "Compile with the gcc compiler, using this command:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:540 +msgid "Test to ensure the program is working:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:549 +msgid "" +"A full example of the `heartbeat probe`_ in C is documented in the source" +" code." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:552 +msgid "Reference" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:559 +msgid "The Telemetry API" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:561 +msgid "" +"Installing the ``telemetrics`` bundle includes the libtelemetry C " +"library, which exposes an API used by the telemprobd and telempostd " +"daemons. You can use these in your applications as well. The API " +"documentation is found in the :file:`telemetry.h` file in `Telemetrics " +"client`_ repository." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:564 +msgid "Client Configuration" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:566 +msgid "" +"The telemetry client will look for the configuration file located at " +":file:`/etc/telemetrics/telemetrics.conf` and use it if it exists. If the" +" file does not exist, the client will use the default configuration " +"located at :file:`/usr/share/defaults telemetrics/telemetrics.conf`. To " +"modify or customize the configuration, copy the file from " +":file:`/usr/share/defaults/telemetrics` to :file:`/etc/telemetrics` and " +"edit it." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:569 +msgid "Configuration Options" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:570 +msgid "The client uses the following configuration options from the config file:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:572 +msgid "" +"**server**: This specifies the web server to which telempostd sends the " +"telemetry records." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:573 +msgid "" +"**socket_path**: This specifies the path of the unix domain socket that " +"the telemprobd listens on for connections from the probes." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:574 +msgid "" +"**spool_dir**: This configuration option is related to spooling. If the " +"daemon is not able to send the telemetry records to the backend server " +"due to reasons such as the network availability, then it stores the " +"records in a spool directory. This option specifies that path of the " +"spool directory. This directory should be owned by the same user as the " +"daemon." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:575 +msgid "" +"**record_expiry**: This is the time in minutes after which the records in" +" the spool directory are deleted by the daemon." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:576 +msgid "" +"**spool_process_time**: This specifies the time interval in seconds that " +"the daemon waits for before checking the spool directory for records. The" +" daemon picks up the records in the order of modification date and tries " +"to send the record to the server. It sends a maximum of 10 records at a " +"time. If it was able to send a record successfully, it deletes the record" +" from the spool. If the daemon finds a record older than the " +"\"record_expiry\" time, then it deletes that record. The daemon looks at " +"a maximum of 20 records in a single spool run loop." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:577 +msgid "" +"**rate_limit_enabled**: This determines whether rate-limiting is enabled " +"or disabled. When enabled, there is a threshold on both records sent " +"within a window of time, and record bytes sent within a window a time." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:578 +msgid "" +"**record_burst_limit**: This is the maximum amount of records allowed to " +"be passed by the daemon within the record_window_length of time. If set " +"to -1, the rate-limiting for record bursts is disabled." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:579 +msgid "" +"**record_window_length**: The time in minutes (0-59) that establishes the" +" window length for the record_burst_limit. EX: if " +"record_burst_window=1000 and record_window_length=15, then no more than " +"1000 records can be passed within any given fifteen minute window." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:580 +msgid "" +"**byte_burst_limit**: This is the maximum amount of bytes that can be " +"passed by the daemon within the byte_window_length of time. If set to -1," +" the rate-limiting for byte bursts is disabled." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:582 +msgid "" +"**byte_window_length**: This is the time, in minutes (0-59), that " +"establishes the window length for the byte_burst_limit." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:583 +msgid "" +"**rate_limit_strategy**: This is the strategy chosen once the rate-" +"limiting threshold has been reached. Currently the options are 'drop' or " +"'spool', with spool being the default. If spool is chosen, records will " +"be spooled and sent at a later time." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:584 +msgid "" +"**record_retention_enabled**: When this key is enabled (true) the daemon " +"saves a copy of the payload on disk from all valid records. To avoid the " +"excessive use of disk space only the latest 100 records are kept. The " +"default value for this configuration key is false." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:585 +msgid "" +"**record_server_delivery_enabled**: This key controls the delivery of " +"records to server; when enabled (default value), the record will be " +"posted to the address in the configuration file. If this configuration " +"key is disabled (false), records will not be spooled or posted to " +"backend. This configuration key can be used in combination with " +"record_retention_enabled to keep copies of telemetry records locally " +"only." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:589 +msgid "" +"Configuration options may change as the telemetry client evolves. Please " +"use the comments in the file itself as the most accurate reference for " +"configuration." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:595 +msgid "Client Run-time Options" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:596 +msgid "" +"The |CL| telemetry client provides an admin tool called " +":guilabel:`telemctl` for managing the telemetry services and probes. The " +"tool is located in :file:`/usr/bin`. Running it with no argument results " +"in the following:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:615 +msgid "start/stop/restart" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:617 +msgid "" +"The commands to start, stop and restart the telemetry services manage all" +" required services and probes on the system. There is no need to " +"separately start/stop/restart the two client daemons **telemprobd** and " +"**telempostd**. The **restart** command option will call **telemctl " +"stop** followed by **telemctl start** ." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:620 +msgid "is-active" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:622 +msgid "" +"The `is-active` option reports whether the two client daemons are active." +" This is useful to verify that the **opt-in** and **opt-out** options " +"have taken effect, or to ensure that telemetry is functioning on the " +"system. Note that both daemons are verified." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/index.mo b/locale/de/LC_MESSAGES/index.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/index.mo differ diff --git a/locale/de/LC_MESSAGES/index.po b/locale/de/LC_MESSAGES/index.po new file mode 100644 index 00000000..700ac6a4 --- /dev/null +++ b/locale/de/LC_MESSAGES/index.po @@ -0,0 +1,94 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../index.rst:4 +msgid "|CL-PRJ|" +msgstr "" + +#: ../../index.rst:6 +msgid "" +"Welcome to the |CL-ATTR| documentation pages, the source for |CL| " +"documentation." +msgstr "" + +#: ../../index.rst:12 +msgid "Our documentation is divided into the following sections:" +msgstr "" + +#: ../../index.rst:15 +msgid ":ref:`get-started`" +msgstr "" + +#: ../../includes/get-started.txt:1 +msgid "" +"If you are new to |CL|, get started fast with tutorials for installing " +"|CL| on bare metal, in a virtual environment, or as a live image on a USB" +" stick." +msgstr "" + +#: ../../index.rst:19 +msgid ":ref:`tooling`" +msgstr "" + +#: ../../index.rst:18 +msgid "" +"Clear Linux is a little different from other distros. Here are some " +"important tools and concept for managing your install." +msgstr "" + +#: ../../index.rst:24 +msgid ":ref:`guides`" +msgstr "" + +#: ../../index.rst:22 +msgid "" +"Guides show how to complete common tasks that help you leverage |CL| " +"native features effectively. From basic system configuration to advanced " +"management of a cloud installation, there is a guide for you." +msgstr "" + +#: ../../index.rst:28 +msgid ":ref:`tutorials`" +msgstr "" + +#: ../../index.rst:27 +msgid "" +"|CL| tutorials provide step-by-step instructions on how |CL| features can" +" be used and extended, frequently with third-party tools." +msgstr "" + +#: ../../index.rst:32 +msgid ":ref:`reference`" +msgstr "" + +#: ../../index.rst:31 +msgid "" +"Find the detailed information you need to enable your configuration or " +"task in our |CL| reference section." +msgstr "" + +#: ../../index.rst:35 +msgid ":ref:`faq`" +msgstr "" + +#: ../../index.rst:35 +msgid "Refer to our FAQ section to read commonly asked questions and answers." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/reference/bundle-commands.mo b/locale/de/LC_MESSAGES/reference/bundle-commands.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/reference/bundle-commands.mo differ diff --git a/locale/de/LC_MESSAGES/reference/bundle-commands.po b/locale/de/LC_MESSAGES/reference/bundle-commands.po new file mode 100644 index 00000000..4691ea79 --- /dev/null +++ b/locale/de/LC_MESSAGES/reference/bundle-commands.po @@ -0,0 +1,58 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/bundle-commands.rst:4 +msgid "Useful bundle commands" +msgstr "" + +#: ../../reference/bundle-commands.rst:6 +msgid "To see a list of currently installed bundles, enter:" +msgstr "" + +#: ../../reference/bundle-commands.rst:12 +msgid "To see the list of all available bundles, enter:" +msgstr "" + +#: ../../reference/bundle-commands.rst:18 +msgid "" +"Alternatively, you can view our :ref:`available bundles ` " +"webpage." +msgstr "" + +#: ../../reference/bundle-commands.rst:21 +msgid "To search for bundles and their contents, enter:" +msgstr "" + +#: ../../reference/bundle-commands.rst:27 +msgid "To add a bundle, enter:" +msgstr "" + +#: ../../reference/bundle-commands.rst:34 +msgid "Additional information" +msgstr "" + +#: ../../reference/bundle-commands.rst:36 +msgid "For additional :command:`swupd` commands, enter:" +msgstr "" + +#: ../../reference/bundle-commands.rst:42 +msgid "To reference the :command:`swupd` man page, enter:" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/reference/bundles/bundles.mo b/locale/de/LC_MESSAGES/reference/bundles/bundles.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/reference/bundles/bundles.mo differ diff --git a/locale/de/LC_MESSAGES/reference/bundles/bundles.po b/locale/de/LC_MESSAGES/reference/bundles/bundles.po new file mode 100644 index 00000000..44329562 --- /dev/null +++ b/locale/de/LC_MESSAGES/reference/bundles/bundles.po @@ -0,0 +1,41 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/bundles/bundles.rst:4 +msgid "Available bundles" +msgstr "" + +#: ../../reference/bundles/bundles.rst:6 +msgid "" +"This document provides a current list of available bundles. View the " +"`clr-bundles repo`_ on GitHub\\*, or select the bundle :file:`Name` for " +"more details." +msgstr "" + +#: ../../reference/bundles/bundles.rst:9 +msgid "" +"To learn more about how |CL-ATTR| uses bundles for software deployment, " +"visit :ref:`bundles-about`." +msgstr "" + +#: ../../reference/bundles/bundles.rst:13 +msgid "Bundle list" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/reference/bundles/openssh-server.mo b/locale/de/LC_MESSAGES/reference/bundles/openssh-server.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/reference/bundles/openssh-server.mo differ diff --git a/locale/de/LC_MESSAGES/reference/bundles/openssh-server.po b/locale/de/LC_MESSAGES/reference/bundles/openssh-server.po new file mode 100644 index 00000000..d0cefde9 --- /dev/null +++ b/locale/de/LC_MESSAGES/reference/bundles/openssh-server.po @@ -0,0 +1,181 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/bundles/openssh-server.rst:4 +msgid "openssh-server" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:6 +msgid "" +"The **openssh-server** bundle provides the OpenSSH\\* package needed to " +"enable an SSH service in |CL-ATTR|. Remote users require an SSH service " +"to be able to use an encrypted login shell." +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:10 +msgid "" +"|CL| enables the `sshd.socket` unit, which will listen on port 22 by " +"default and start the OpenSSH service as required. The first time OpenSSH" +" starts, it generates the server SSH keys needed for the service." +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:15 +msgid "Prerequisites" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:17 +msgid "Assure the bundle :file:`openssh-server` is installed." +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:19 +msgid "To check it it's on your host, enter:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:25 +msgid "To add it, enter:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:32 +msgid "Change default port" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:34 +msgid "" +"Perform the following steps to change the default listening port for the " +"OpenSSH service:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:37 +msgid "Open the sshd.socket file:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:43 +msgid "" +"Add the `[Socket]` section and `ListenStream` option to the sshd.socket " +"file as shown below. The first `ListenStream` entry removes the |CL| " +"default listen port value. The second `ListenStream` entry sets the new " +"default listen port value. In this example, we set the new default port " +"to 4200:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:56 +msgid "" +"Make sure to include a new line after the last line of text in the " +"sshd.socket file." +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:58 +msgid "Verify your changes:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:64 +msgid "You should see the following output:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:72 +msgid "Reload the systemd daemon configurations:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:78 +msgid "Restart the sshd.socket unit:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:84 +msgid "Confirm the the sshd.socket unit is listening on your new port:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:92 +msgid "Output should show :guilabel:`Active:` as `active(listening)`." +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:95 +msgid "Enable SFTP" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:97 +msgid "" +"|CL| *disables* the :abbr:`SFTP (SSH File Transfer Protocol)` subsystem " +"by default due to security considerations. To enable the SFTP subsystem, " +"perform the following configuration of the :abbr:`SSHD (SSH Daemon)` " +"service file:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:101 +msgid "Create a systemd drop-in directory for the SSHD service:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:107 +msgid "" +"Create the following file: " +":file:`/etc/systemd/system/sshd@.service.d/sftp.conf`" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:110 +msgid "Add the OPTIONS environment variable to the sftp.conf file." +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:117 +msgid "Reload systemd configuration:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:123 +msgid "Congratulations! The SFTP subsystem is enabled." +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:126 +msgid "Enable root login" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:128 +msgid "To enable root login via SSH, perform the following steps:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:130 +#: ../../reference/bundles/openssh-server.rst:153 +msgid "Create a *ssh* directory in :file:`/etc`, if it does not already exist." +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:136 +#: ../../reference/bundles/openssh-server.rst:159 +msgid "" +"Create the following file, if it does not already exist: " +":file:`/etc/ssh/sshd_config`" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:139 +msgid "Set the configuration variable in /etc/ssh/sshd_config" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:146 +msgid "Enable X11-forwarding" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:148 +msgid "" +"X11 forwarding allows you to securely run graphical applications (i.e., X" +" clients) over the ssh conection. This will alow for remote gui apps " +"without the need for full VNC/remotedesktop. To enable X11-forwarding via" +" SSH, perform the following steps:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:162 +msgid "Set the configuration variables." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/reference/collaboration/collaboration.mo b/locale/de/LC_MESSAGES/reference/collaboration/collaboration.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/reference/collaboration/collaboration.mo differ diff --git a/locale/de/LC_MESSAGES/reference/collaboration/collaboration.po b/locale/de/LC_MESSAGES/reference/collaboration/collaboration.po new file mode 100644 index 00000000..c3b1a476 --- /dev/null +++ b/locale/de/LC_MESSAGES/reference/collaboration/collaboration.po @@ -0,0 +1,161 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/collaboration/collaboration.rst:4 +msgid "Documentation guidelines" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:6 +msgid "" +"See a missing topic in the documentation? Find an existing document that " +"could be improved? Help us out by contributing! If you haven't " +"contributed before, take a moment to review our `Contribution " +"guidelines`_." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:10 +msgid "" +"Do you have questions about the documentation that were not answered by " +"these guidelines? Send your question to the `mailing list`_." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:14 +msgid "Contribution guidelines" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:16 +msgid "" +"The |CL| documentation is hosted in GitHub and is written using " +"reStructuredText. Use our guidelines and best practices to write " +"consistent, readable documentation." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:27 +msgid "How to contribute" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:29 +msgid "There are multiple ways to contribute and help improve our documentation:" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:31 +msgid "" +"**Make a suggestion**: Have a documentation suggestion but no time to " +"write it yourself? Send your suggestion to the `mailing list`_." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:33 +msgid "" +"**Log an issue**: If you find a problem in our documentation (such as " +"typos or out-of-date information), log an issue in the `documentation " +"repository`_." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:35 +msgid "" +"**Contribute directly via GitHub**: Whether you've found a typo, have " +"better instructions or examples, or have a new page to add, submit your " +"improvement or addition as a pull request on the `documentation " +"repository`_." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:38 +msgid "" +"**Test documentation**: Step through our instructional guides and " +"tutorials to verify the instructions. Log or correct any out-of-date " +"information." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:41 +msgid "All contributions must follow our `code of conduct`_." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:44 +msgid "Contribute via GitHub" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:46 +msgid "" +"Our documentation is hosted in GitHub and we follow the standard `GitHub " +"flow`_:" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:48 +msgid "Clone the `documentation repository`_." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:50 +msgid "Create your own fork of the repository." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:52 +msgid "Create a branch for your contribution." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:54 +msgid "Add your commits." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:56 +msgid "Open a pull request." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:58 +msgid "Discuss, review, and update your contributions." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:60 +msgid "" +"Once the maintainer approves, your contribution is merged and published " +"as part of the documentation." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:66 +msgid "References" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:68 +msgid "" +"We use the following references to guide the grammar, style, and " +"formatting of our documentation:" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:71 +msgid "`Microsoft Writing Style Guide`_" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:72 +msgid "`Merriam-Webster Dictionary`_" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:73 +msgid "" +"The Chicago Manual of Style (15th edition), The University of Chicago " +"Press" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:74 +msgid "Microsoft Press Computer Dictionary, Microsoft Press" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:75 +msgid "Read Me First!, Oracle Technical Publications" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/reference/collaboration/structure-formatting.mo b/locale/de/LC_MESSAGES/reference/collaboration/structure-formatting.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/reference/collaboration/structure-formatting.mo differ diff --git a/locale/de/LC_MESSAGES/reference/collaboration/structure-formatting.po b/locale/de/LC_MESSAGES/reference/collaboration/structure-formatting.po new file mode 100644 index 00000000..5f0d340e --- /dev/null +++ b/locale/de/LC_MESSAGES/reference/collaboration/structure-formatting.po @@ -0,0 +1,890 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/collaboration/structure-formatting.rst:4 +msgid "Structure and formatting" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:6 +msgid "" +"Content should be organized to support scanning. Consistent organization," +" formatting, and writing style helps readers quickly find what they need " +"and to understand the content more effectively. This document describes " +"our organization and formatting guidelines." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:11 +msgid "" +"Refer to :ref:`writing-guide` to learn how we keep our documents clear " +"and concise." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:18 +msgid "Markup" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:20 +msgid "" +"Our documentation is written in the reStructuredText markup language, " +"using Sphinx roles and directives. We use Sphinx to generate the final " +"documentation. You can read more about reStructuredText and Sphinx on " +"their respective websites:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:25 +msgid "`Sphinx documentation`_" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:26 +msgid "`reStructuredText Primer`_" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:28 +msgid "" +"You can view the content directly in the .rst markup files, or generate " +"the HTML content by installing and building the documentation locally. To" +" run the documentation locally, follow the instructions found in the " +"`documentation repository`_ README." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:34 +msgid "New pages" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:36 +msgid "" +"There are a few additional steps to consider when adding a new page to " +"the documentation. First, identify where your new page should be located " +"within the existing `Documentation organization`_. Second, make sure the " +"new page is picked up in the Sphinx build and easily linkable from other " +"content." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:41 +msgid "" +"Each page must be included in a `Sphinx toctree`_ in order to be included" +" in the documentation content tree. Typically, pages are added to the " +"section landing page toctree." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:45 +msgid "For example, the :ref:`collaboration` page toctree looks like:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:55 +msgid "" +"Additionally, each page must include a uniquely named reST label directly" +" before the page title, to enable the `Sphinx ref role`_ for linking to a" +" page." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:58 +msgid "" +"For example, this page \"Structure and formating\" has the label ``.. " +"_structure-formatting``:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:68 +msgid "" +"This page can then be referenced from other pages in the documentation " +"using the `:ref:` role:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:76 +msgid "Documentation organization" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:78 +msgid "The documentation is organized into five general sections:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:80 +msgid "" +"**Concepts**: Introduction and overview of |CL| specific concepts or " +"features." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:82 +msgid "**Get started**: Information about getting started with |CL|." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:83 +msgid "**Guides**: Detailed information and instruction on using |CL| features." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:84 +msgid "" +"**Tutorials**: Step-by-step instruction for using |CL| in specific use " +"cases." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:85 +msgid "**Reference**: Supplementary and reference information for |CL|." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:88 +msgid "Page structure" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:90 +msgid "Each page in the documentation should follow the basic format of:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:92 +msgid "Overview: 1-2 sentences describing what this page shows and why it matters" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:93 +msgid "" +"Prerequisites: Describe any pre-work necessary to the content (if " +"appropriate)" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:94 +msgid "Content" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:95 +msgid "Next steps: List links to next steps (if appropriate)" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:96 +msgid "Related topics: List links to related content (if appropriate)" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:99 +msgid "Headings" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:101 +msgid "" +"Use headings to section and organize your content for better readability " +"and clarity." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:104 +msgid "All files must have a top level heading, which is the title for the page." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:105 +msgid "" +"Up to three additional levels of headings are allowed under the title " +"heading." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:106 +msgid "" +"Each heading should be followed by at least one paragraph of content. " +"Avoid two or more consecutive headings." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:109 +msgid "" +"Refer to the :ref:`writing-guide` for tips on using headings to create " +":ref:`scannable content `." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:112 +msgid "To mark up headings in the .rst file:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:114 +msgid "Use hash-tags to underline the file's main title:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:121 +msgid "Use asterisks to underline the file's first level headings:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:128 +msgid "Use equal signs to underline the file's second level of headings:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:135 +msgid "Use dashes to underline the file's third level of headings:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:143 +msgid "In-page navigation" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:145 +msgid "" +"If a page has three or more sections, provide quick links to each " +"section. Place the quick links after the overview section." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:148 +msgid "Use the standard `reST contents directive`_ with depth: 1 for quick links." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:151 +msgid "Inline text formatting" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:153 +msgid "" +"We use the `Microsoft Writing Style Guide`_ as our starting point for " +"text formatting. We apply the formatting using reST and Sphinx markup." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:156 +msgid "Use our quick reference for the most commonly used inline text elements:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:159 +msgid "**Element**" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:159 +msgid "**Convention**" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:159 +msgid "**reST/Sphinx**" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:161 +msgid "Acronyms" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:161 +msgid "" +"Define acronym when first used. After first use and definition, use the " +"acronym only." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:161 +msgid "Use the ``:abbr:`` role, in the following format:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:164 +msgid "``:abbr:`Acronym (Def)```" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:166 +msgid "Bundle names" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:166 +#: ../../reference/collaboration/structure-formatting.rst:174 +#: ../../reference/collaboration/structure-formatting.rst:176 +msgid "Bold" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:166 +#: ../../reference/collaboration/structure-formatting.rst:174 +#: ../../reference/collaboration/structure-formatting.rst:176 +msgid "Use the ``:command:`` role." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:168 +msgid "Callouts" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:168 +msgid "Use ``.. note::``" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:170 +msgid "Code/command examples" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:170 +msgid "" +"Monospace, visually distinct from rest of text. Use an indented call-out " +"box." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:170 +msgid "Use ``.. code-block::`` with the correct language setting." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:174 +msgid "Commands" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:176 +msgid "Command flags" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:178 +msgid "Console output" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:178 +msgid "" +"Monospace, visual distinction from rest of text. Use an indented call-out" +" box." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:178 +msgid "Use ``.. code-block::`` with console as the language setting." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:182 +msgid "Emphasis" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:182 +msgid "Italic" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:182 +msgid "``*strong*``" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:184 +msgid "Environment variables" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:184 +msgid "Use the case format of the environment variable." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:184 +msgid "Use ``:envvar:``" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:187 +msgid "Example commands with optional or replaceable parts" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:187 +msgid "Use angle brackets for swapping in the specific name, e.g. ." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:191 +msgid "Use square brackets for optional parts, e.g. [--build]." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:195 +msgid "Example URLs (not linked)" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:195 +msgid "Plain text" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:197 +msgid "File extensions" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:197 +msgid "Lowercase" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:199 +msgid "File names, directories, paths" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:199 +msgid "Title style capitalization" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:199 +msgid "Use the ``:file:`` role." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:201 +msgid "GUI labels" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:201 +msgid "Use ``:guilabel:``" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:203 +msgid "Inline comments" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:203 +msgid "Use ``..``" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:205 +msgid "Keystrokes" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:205 +msgid "Use ``:kbd:``" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:207 +msgid "Local navigation" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:207 +msgid "``.. contents:: :local:`` with a depth of 1" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:210 +msgid "Menu selection" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:210 +msgid "Use ``:menuselection:``" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:212 +msgid "New terms" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:212 +msgid "Italic for first use, normal for all subsequent uses." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:215 +msgid "If it is used outside of the source of definition, link the term." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:212 +msgid "``*term*``" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:218 +msgid "Product name" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:218 +msgid "Follow correct trademark and attribution guidelines." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:221 +msgid "Tool names" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:221 +msgid "Correctly capitalized, no quotes, bold, or italics as the basic rule." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:224 +msgid "" +"If the tool name is the command, like most Linux tools, treat it like a " +"command." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:228 +msgid "" +"If the tool name is lowercase and used at the start of a sentence, use " +"bold." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:234 +msgid "White space and line length" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:236 +msgid "" +"Limit line length to 78 characters. The GitHub web interface forces this " +"limitation for readability." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:239 +msgid "Remove trailing whitespace from your documents." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:242 +msgid "Code blocks and examples" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:244 +msgid "" +"When providing example code or commands use the `Sphinx code-block " +"directive`_. Select the appropriate syntax highlighting for the example " +"command or code." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:247 +msgid "For example, if showing console output, use console highlighting:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:253 +msgid "Sphinx provides other ways of `marking up example code`_ if needed." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:256 +msgid "Lists and instructions" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:258 +msgid "" +"Use a numbered list when the order or priority of the items is important," +" such as step-by-step instructions." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:261 +msgid "Use a bulleted list when the order of the items is not important." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:263 +msgid "" +"For both list types, keep all items in the list parallel. See " +":ref:`parallelism`." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:266 +msgid "Use standard `reST list markup`_." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:269 +msgid "Numbered lists" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:271 +msgid "" +"Numbered lists are most frequently used for procedures. Use numbered " +"lists to show sequence for the items. Follow our guidelines for numbered " +"lists:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:274 +msgid "Make sure the list is sequential and not just a collection of items." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:275 +msgid "" +"Introduce a numbered list with a sentence. End the setup text with a " +"colon. Example: \"To configure the unit, perform the following steps:\"" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:277 +#: ../../reference/collaboration/structure-formatting.rst:299 +msgid "Each item in the list should be parallel." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:278 +msgid "" +"Treat numbered list items as full sentences with correct ending " +"punctuation." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:280 +msgid "" +"You may interrupt numbered lists with other content, if relevant, e.g. " +"explanatory text, commands, or code." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:282 +msgid "Second-level steps are acceptable; avoid third-level steps." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:283 +msgid "" +"Avoid single-step procedures; the minimum number of steps in a procedure " +"is two." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:285 +msgid "" +"Do not create numbered lists that emulate flowcharts. The reader should " +"be able to execute the list of steps from first to last without branching" +" or looping." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:288 +msgid "" +"Avoid over-using numbered lists, except in procedural documents such as " +"tutorials and step-by-step guides." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:292 +msgid "Bulleted lists" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:294 +msgid "" +"Use bulleted lists to reduce wordiness and paragraph density, especially " +"when a sequence is not required. Here are some guidelines for bulleted " +"lists:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:297 +msgid "" +"Introduce a bulleted list with a sentence. End the setup text with a " +"colon. Example: \"To repair the unit, you will need the following " +"items:\"" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:300 +msgid "Avoid interrupting bulleted lists with other paragraph styles." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:301 +msgid "Second-level bullets are acceptable; avoid third-level bullets." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:303 +msgid "" +"Use the correct ending punctuation for sentence style bullet lists. For " +"example:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:305 +msgid "**Use this:**" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:315 +msgid "**Not this:**" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:327 +msgid "Instructions" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:329 +msgid "" +"When presenting instructions, such as in a tutorial, present them in a " +"numbered list according to these guidelines:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:332 +msgid "Each step (list item) should describe one action." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:334 +msgid "" +"If the same steps are repeated, refer to the earlier steps rather than " +"repeating them." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:337 +msgid "" +"When a step includes a command or code block as an example, put the " +"command or code block after the step that includes them." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:340 +msgid "" +"Use supporting images where appropriate. If the series of steps is " +"supported by one figure, refer to the figure in the introductory text." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:343 +msgid "For example: \"See Figure 15 and do the following:\"" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:345 +msgid "" +"When a series of steps is supported by two or more figures, refer to the " +"specific figure in the relevant step and show the figure immediately " +"after the reference. **Do not write**: \"See figures 15 through 22 and do" +" the following:\"" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:351 +msgid "Notices" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:353 +msgid "" +"We use four special types of notices: notes, cautions, warnings, and " +"dangers. Here are some specific rules and tips regarding use of these " +"notices:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:356 +msgid "" +"Do not use a notice directly after a heading. Notices must follow a " +"variant of body text." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:358 +msgid "Do not include more than one notice in a single notice block." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:359 +msgid "Avoid back-to-back notices." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:360 +msgid "" +"If back-to-back notices are not avoidable, make sure each distinct notice" +" in the notice block is clearly defined." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:363 +msgid "Use the standard `reST admonition directive`_." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:366 +msgid "Notes, cautions, and warnings" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:368 +msgid "" +"Use notes sparingly. Avoid having more than one note per section. If you " +"exceed this number consistently, consider rewriting the notes as main " +"body text." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:371 +msgid "" +"Use cautions and warnings to alert readers of potential problems or " +"pitfalls. Use conditional phrases in cautions and warnings, such as \"If " +"you do X, then Y will occur.\"" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:375 +msgid "These are examples of typical notices and the conditions for their usage:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:378 +msgid "" +"Notes are extra bits of information that supplement the main content. " +"Notes should be relatively short." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:382 +msgid "" +"Cautions are low-level hazard messages that alert the user of possible " +"equipment, product, and software damage, including loss of data." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:386 +msgid "Warnings are mid-level hazards that are likely to cause product damage." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:389 +msgid "Links" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:391 +msgid "Use the standard `reST markup for links`_." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:393 +msgid "" +"To add a cross-reference to another documentation page, use the `:ref:` " +"role:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:399 +msgid "" +"To add an external link, we use named references that refer to a defined " +"link/label at the bottom of the page." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:402 +msgid "" +"For example, an external link is defined at the bottom of the page like " +"this:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:408 +msgid "The defined link is then used in the content like this:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:415 +msgid "Images" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:417 +msgid "" +"Use images or figures to convey information that may be difficult to " +"explain using words alone. Well-planned graphics reduce the amount of " +"text required to explain a topic or example." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:421 +msgid "" +"Follow these guidelines when using graphics in support of your " +"documentation:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:423 +msgid "" +"Keep it simple. Use images that serve a specific purpose in your " +"document, and contain only the information the reader needs." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:426 +msgid "" +"Avoid graphics that will need frequent updating. Don't include " +"information in a graphic that might change with each release, such as " +"product versions." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:429 +msgid "" +"Use either PNG or JPEG bitmap files for screenshots and SVG files for " +"vector graphics." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:432 +msgid "" +"Place the image immediately after the text it helps clarify, or as close " +"as possible." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:435 +msgid "" +"Use the `Sphinx figure directive`_ to insert images and figures into the " +"document. Include both alt text, a figure name, and caption." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:438 +msgid "For example:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:447 +msgid "" +"Include at least one direct reference to an image from the main text, " +"using the figure number. For example:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:450 +msgid "**Use this:** ::" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:454 +msgid "**Not this:** ::" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:458 +msgid "Images should follow these naming and location conventions:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:460 +msgid "" +"Save the image files in a :file:`figures` folder at the same level as the" +" file that will reference the image." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:462 +msgid "Name image files according to the following rules:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:464 +msgid "Use only lower case letters." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:465 +msgid "Separate multiple words in filenames using dashes." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:466 +msgid "" +"Name images using the filename of the file they appear on and add a " +"number to indicate their place in the file. For example, the third figure" +" added to the :file:`welcome.rst` file must be named " +":file:`welcome-3.png`." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/reference/collaboration/writing-guide.mo b/locale/de/LC_MESSAGES/reference/collaboration/writing-guide.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/reference/collaboration/writing-guide.mo differ diff --git a/locale/de/LC_MESSAGES/reference/collaboration/writing-guide.po b/locale/de/LC_MESSAGES/reference/collaboration/writing-guide.po new file mode 100644 index 00000000..9167d289 --- /dev/null +++ b/locale/de/LC_MESSAGES/reference/collaboration/writing-guide.po @@ -0,0 +1,689 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/collaboration/writing-guide.rst:4 +msgid "Writing guide" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:6 +msgid "" +"We want our documentation to be easy to read and understand. This " +"document describes guidelines for writing documentation that is clear, " +"concise, confident, and courteous." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:10 +msgid "" +"Refer to :ref:`structure-formatting` for details on organizing content " +"and how we use reStructuredText and Sphinx." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:17 +msgid "Use simple English" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:19 +msgid "" +"Write using simple English: Be brief and communicate only the information" +" that is needed. Be friendly and informative. Emphasize clarity and avoid" +" unecessary complicated or technical terms. Make the content accessible " +"to non-native speakers." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:25 +msgid "Be brief" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:27 +msgid "" +"Use short sentences and paragraphs. Stick to the principle of one main " +"idea per sentence, plus one additional point if needed. Each paragraph " +"should address one main idea. Remember the basic structure of a " +"paragraph: Introduction, body, and conclusion." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:33 +msgid "Be friendly" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:35 +msgid "" +"We write for our peers and want to be familiar. Take a personal tone as " +"if you were speaking directly to the reader. Use \"you\" to address the " +"reader and \"we\" to refer to our view. Be professional, respectful, and " +"cooperative." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:39 +msgid "" +"Assume your audience has the same level of technical understanding and " +"expertise as you did when you first started collaborating. Do not talk " +"down to our readers, but also do not assume they know everything about " +"the subject. Offer brief explanations or summaries of common knowledge if" +" a significant portion of readers might benefit." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:46 +msgid "Use simple words" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:48 +msgid "" +"Use simple words to increase reader comprehension and reduce ambiguity. " +"Follow our tips for making good word choices:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:51 +msgid "" +"**Avoid jargon**: Write for your audience, using everyday language where " +"possible, and technical terms where appropriate. Avoid clichés, idioms, " +"and metaphors." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:54 +msgid "" +"**Be consistent**: Use one term for each concept or action and use it " +"consistently." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:56 +msgid "" +"**Avoid \"fancy\" words and phrases**: If there is a simpler word or " +"phrase, use it." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:59 +#: ../../reference/collaboration/writing-guide.rst:151 +#: ../../reference/collaboration/writing-guide.rst:202 +#: ../../reference/collaboration/writing-guide.rst:213 +#: ../../reference/collaboration/writing-guide.rst:258 +#: ../../reference/collaboration/writing-guide.rst:368 +msgid "For example:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:62 +msgid "Use this" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:62 +msgid "Not this" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:64 +msgid "start, begin" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:64 +msgid "commence" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:65 +msgid "so" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:65 +msgid "consequently" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:66 +msgid "more than" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:66 +msgid "in excess of" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:67 +msgid "if" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:67 +msgid "in the event of" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:68 +msgid "before" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:68 +msgid "prior to" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:69 +msgid "if you want" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:69 +msgid "should one wish" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:70 +msgid "use" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:70 +msgid "utilize" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:71 +msgid "example" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:71 +msgid "instance" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:75 +msgid "Avoid overuse of product name" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:77 +msgid "" +"Use product names only when necessary. Typically, you can rewrite " +"sentences to remove the product name with no change in meaning, which " +"keeps the content concise and scannable." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:81 +msgid "Avoid using the product name in page titles and headings." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:86 +msgid "Make content scannable" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:88 +msgid "" +"Organize your content to make it scannable for the reader, which helps " +"them find what they need quickly, and to understand the information more " +"efficiently." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:91 +msgid "" +"**Put the most important content first.** Make sure your introduction " +"clearly communicates what the reader can find on the page. Present the " +"point of the document first, and organize supporting information towards " +"the end of the page." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:95 +msgid "" +"**Write scannable headings.** Expect readers of documentation to skim and" +" scan the content, and to leave if they dont find what they need quickly." +" Good headings add organization to your content and help the reader to " +"find and understand content more effectively. Follow our guidelines for " +"writing effective `Headings`_." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:100 +msgid "" +"**Write great link text.** Great link text tells the reader what they can" +" expect when they click on a link. It also helps make the page more " +"scannable. Follow our guidelines for writing `Link text`_." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:105 +msgid "Headings" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:107 +msgid "Use these guidelines to write effective headings:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:109 +msgid "" +"**Be concise and descriptive.** Use only the words necessary to describe " +"the section." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:111 +msgid "" +"**Use sentence case.** Capitalize only the first word and proper nouns in" +" a heading." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:113 +msgid "" +"**Avoid punctuation.** Unless your heading is a question, don't use " +"sentence punctuation in headings." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:115 +msgid "" +"**Use parallel structure.** Headings at the same level should use the " +"same grammatical pattern. This provides structure to the document and " +"helps users find information more easily. See :ref:`parallelism`." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:118 +msgid "" +"**Use strong verbs.** Strong, active verbs get to the point. Avoid -ing " +"verbs, such as *Running*, *Testing*, etc." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:121 +msgid "For example, two headings at the same level:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:123 +#: ../../reference/collaboration/writing-guide.rst:153 +#: ../../reference/collaboration/writing-guide.rst:173 +#: ../../reference/collaboration/writing-guide.rst:189 +#: ../../reference/collaboration/writing-guide.rst:215 +#: ../../reference/collaboration/writing-guide.rst:225 +#: ../../reference/collaboration/writing-guide.rst:239 +#: ../../reference/collaboration/writing-guide.rst:260 +#: ../../reference/collaboration/writing-guide.rst:270 +#: ../../reference/collaboration/writing-guide.rst:285 +#: ../../reference/collaboration/writing-guide.rst:401 +msgid "**Use this:** ::" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:129 +#: ../../reference/collaboration/writing-guide.rst:157 +#: ../../reference/collaboration/writing-guide.rst:177 +#: ../../reference/collaboration/writing-guide.rst:193 +#: ../../reference/collaboration/writing-guide.rst:219 +#: ../../reference/collaboration/writing-guide.rst:229 +#: ../../reference/collaboration/writing-guide.rst:243 +#: ../../reference/collaboration/writing-guide.rst:264 +#: ../../reference/collaboration/writing-guide.rst:274 +#: ../../reference/collaboration/writing-guide.rst:289 +#: ../../reference/collaboration/writing-guide.rst:405 +msgid "**Not this:** ::" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:136 +msgid "Link text" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:138 +msgid "All links in content should follow these guidelines:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:140 +msgid "" +"**Write descriptive link text**: Link text should describe where the link" +" goes, without having to read the surrounding text." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:142 +msgid "" +"**Keep link text concise**: Use only the words needed to accurately " +"describe the destination." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:144 +msgid "" +"**Use unique link text**: Each link on a page should be unique. If users " +"see the same link text twice on a page, they'll assume it goes to the " +"same place." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:146 +msgid "" +"**Start link text with keywords**: Frontload the link text with the most " +"important words to help users scan the text." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:148 +msgid "" +"**Avoid generic text**: Don't use generic, uninformative link text such " +"as \"click here\" or \"read more\"." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:162 +msgid "Use strong verbs" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:164 +msgid "" +"Passive verbs make writing stuffy and formal. Use strong verbs to get to " +"the point and avoid unnecessary words and phrases." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:168 +msgid "Use imperatives" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:170 +msgid "" +"Commands, also called imperatives, are the fastest and most direct way of" +" giving someone instructions. For example:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:182 +msgid "Use present tense" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:184 +msgid "" +"Use simple present tense instead of future tense for most text. Search " +"for the words \"will\" or \"shall\" to find future tense instances. " +"Future tense is acceptable for conditional statements, such as in a " +"caution or a warning. For example:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:198 +msgid "Avoid nominalizations" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:200 +msgid "Avoid nominalizations, which are nouns formed from verbs." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:205 +msgid "Verb" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:205 +msgid "Nominalization" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:207 +msgid "complete" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:207 +msgid "completion" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:208 +msgid "provide" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:208 +msgid "provision" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:209 +msgid "fail" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:209 +msgid "failure" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:210 +msgid "install" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:210 +msgid "installation" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:223 +#: ../../reference/collaboration/writing-guide.rst:268 +msgid "Or:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:234 +msgid "Avoid words ending in -ing" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:236 +msgid "" +"Avoid using words ending in -ing unless they are part of a technical " +"name. For example:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:248 +msgid "Use the active voice" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:250 +msgid "" +"Use active voice whenever possible to show who or what is performing an " +"action." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:253 +msgid "" +"Active voice follows standard English word order: SUBJECT–VERB–OBJECT " +"(where the OBJECT is optional)." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:255 +msgid "" +"Passive voice reverses the order and weakens the verb: OBJECT–be VERB–by " +"SUBJECT (where the OBJECT is optional)." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:279 +msgid "Avoid long noun phrases" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:281 +msgid "" +"Noun phrases (a noun and other words that describe or modify it) can be " +"difficult to understand. Try to limit the number of modifiers in a noun " +"phrase to two. For example:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:296 +msgid "Parallelism" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:298 +msgid "" +"Parallelism refers to the practice of using similar patterns of grammar, " +"and sometimes length, to coordinate words, phrases, and clauses." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:301 +msgid "" +"Use parallel construction in lists. The table below shows some unparallel" +" structures and how they can be made parallel with a little rewording." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:305 +msgid "Parallel (do)" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:305 +msgid "Unparallel (don't)" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:307 +msgid "Mount the panel." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:308 +msgid "Install the battery." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:309 +msgid "Wire the keypad." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:308 +msgid "Battery installation." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:309 +msgid "Wiring the keypad." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:311 +msgid "" +"I like practicing my accordion, reading sci-fi, and eating peanut butter " +"and pickle sandwiches." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:311 +msgid "" +"I like practicing my accordion, reading sci-fi, and to eat peanut butter " +"and pickle sandwiches." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:316 +msgid "For breakfast he likes coffee and bacon." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:316 +msgid "For breakfast he likes coffee and to fry bacon." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:319 +msgid "Apples or bananas are a good snack." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:319 +msgid "Apples or a banana are a good snack." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:324 +msgid "Grammar and punctuation" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:326 +msgid "" +"This section covers common grammatical topics relevant to our " +"documentation. For detailed explanations of correct grammar and " +"punctuation, use one of our :ref:`preferred references `." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:331 +msgid "Capitalization" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:333 +msgid "" +"The capitalization style for all documentation is sentence case. Words " +"should only be capitalized when they are proper nouns or refer to " +"trademarked product names." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:338 +msgid "" +"Do not capitalize a word to indicate it is more important than other " +"words. Never change the case of variable, function or file names - always" +" keep the original case." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:343 +msgid "Menu capitalization" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:345 +msgid "" +"When referring to software menu items by name, use the same " +"capitalization as seen in the actual menu." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:348 +msgid "A few other tips when referring to menu items:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:350 +msgid "" +"Reference the specific menu item using \"Select :menuselection:`File --> " +"New`.\"" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:352 +msgid "" +"Put the option to be selected last. \"Select :menuselection:`View --> " +"Side Bar --> Hide Side Bar`\"" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:355 +msgid "" +"Do not include more than 3 navigation steps in a menu selection. If more " +"than three steps are needed, divide the steps using ``:guilabel:`` or " +"``:menuselection:``." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:359 +msgid "" +"For example: \"Go to :guilabel:`File` and select :menuselection:`Print " +"--> Print Preview --> Set Up`.\"" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:363 +msgid "Software version capitalization" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:365 +msgid "" +"When listing software or hardware version numbers, the word “version” or " +"letter \"v\" are lowercase. The v is closed with the number (no period)." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:370 +msgid "Widget Pro version 5.0" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:371 +msgid "Widget Master v2.1.12" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:374 +msgid "Contractions" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:376 +msgid "" +"Avoid using contractions, such as it's, they're, and you're, because they" +" may be unclear to non-native English-speaking audiences." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:380 +msgid "Quotation marks" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:382 +msgid "Follow these guidelines for quotation marks:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:384 +msgid "Restrict use of quotation marks to terms as terms." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:385 +msgid "Do not use quotation marks for emphasis; use *italics* for emphasis." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:386 +msgid "Avoid using single-quote marks." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:389 +msgid "Commas and colons" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:391 +msgid "" +"This section addresses common use of commas, semicolons, and colons in " +"our documentation. Refer to one of our :ref:`preferred references " +"` for further details." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:396 +msgid "Use the serial comma" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:398 +msgid "" +"When writing a series of items, use the serial comma before the final " +"*and* and *or* to avoid confusion and ambiguity. For example:" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/reference/compatible-hardware.mo b/locale/de/LC_MESSAGES/reference/compatible-hardware.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/reference/compatible-hardware.mo differ diff --git a/locale/de/LC_MESSAGES/reference/compatible-hardware.po b/locale/de/LC_MESSAGES/reference/compatible-hardware.po new file mode 100644 index 00000000..77baec94 --- /dev/null +++ b/locale/de/LC_MESSAGES/reference/compatible-hardware.po @@ -0,0 +1,262 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/compatible-hardware.rst:4 +msgid "Compatible Hardware" +msgstr "" + +#: ../../reference/compatible-hardware.rst:6 +msgid "" +"This document describes hardware that has been tested and confirmed as " +"compatible with |CL-ATTR|. This list is not comprehensive and will " +"continue to grow." +msgstr "" + +#: ../../reference/compatible-hardware.rst:10 +msgid "**Table 1. Compatible Hardware**" +msgstr "" + +#: ../../reference/compatible-hardware.rst:14 +msgid "Processor SKU" +msgstr "" + +#: ../../reference/compatible-hardware.rst:15 +msgid "Platform" +msgstr "" + +#: ../../reference/compatible-hardware.rst:17 +#: ../../reference/compatible-hardware.rst:98 +#: ../../reference/compatible-hardware.rst:110 +msgid "Intel® Core™ i5-6260U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:20 +msgid "Intel® Core™ i5-6560U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:21 +msgid "Dell XPS\\* 13 9350" +msgstr "" + +#: ../../reference/compatible-hardware.rst:23 +#: ../../reference/compatible-hardware.rst:92 +msgid "Intel® Celeron® J3455" +msgstr "" + +#: ../../reference/compatible-hardware.rst:24 +msgid "NUC6CAYS" +msgstr "" + +#: ../../reference/compatible-hardware.rst:26 +#: ../../reference/compatible-hardware.rst:65 +msgid "Intel® Core™ i5-4250U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:29 +#: ../../reference/compatible-hardware.rst:101 +#: ../../reference/compatible-hardware.rst:107 +msgid "Intel® Core™ i7-5557U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:32 +msgid "Intel® Core™ i9-7900X" +msgstr "" + +#: ../../reference/compatible-hardware.rst:33 +msgid "Gigabyte\\* X299" +msgstr "" + +#: ../../reference/compatible-hardware.rst:35 +msgid "Intel® Core™ i3-4130" +msgstr "" + +#: ../../reference/compatible-hardware.rst:36 +msgid "Lenovo Thinkserver\\* TS140" +msgstr "" + +#: ../../reference/compatible-hardware.rst:38 +msgid "Intel® Core™ i7-7567U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:39 +msgid "NUC7i7BNH" +msgstr "" + +#: ../../reference/compatible-hardware.rst:41 +msgid "Intel® Core™ i7-8809G" +msgstr "" + +#: ../../reference/compatible-hardware.rst:42 +msgid "NUC8i7HVK" +msgstr "" + +#: ../../reference/compatible-hardware.rst:44 +msgid "Intel® Core™ i5-7260U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:45 +msgid "NUC7i5BNH" +msgstr "" + +#: ../../reference/compatible-hardware.rst:47 +msgid "Intel® Core™ i7-8650U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:48 +msgid "NUC7i7DNKE" +msgstr "" + +#: ../../reference/compatible-hardware.rst:50 +msgid "Intel® Core™ i5-7300U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:51 +msgid "NUC7i5DNHE" +msgstr "" + +#: ../../reference/compatible-hardware.rst:53 +msgid "Intel® Xeon® Gold 6138" +msgstr "" + +#: ../../reference/compatible-hardware.rst:56 +msgid "Intel® Xeon® E5-2699A v4" +msgstr "" + +#: ../../reference/compatible-hardware.rst:57 +msgid "Dell PowerEdge\\* R630" +msgstr "" + +#: ../../reference/compatible-hardware.rst:59 +msgid "Intel® Xeon® E5-2620 v3" +msgstr "" + +#: ../../reference/compatible-hardware.rst:62 +msgid "Intel® Core™ i5-6600" +msgstr "" + +#: ../../reference/compatible-hardware.rst:63 +msgid "Gigabyte\\* Z170X-UD5" +msgstr "" + +#: ../../reference/compatible-hardware.rst:66 +msgid "D54250WYK" +msgstr "" + +#: ../../reference/compatible-hardware.rst:68 +msgid "Intel® Xeon® E5-2699 v3" +msgstr "" + +#: ../../reference/compatible-hardware.rst:69 +msgid "S2600WT2" +msgstr "" + +#: ../../reference/compatible-hardware.rst:71 +msgid "Intel® Atom™ J3455" +msgstr "" + +#: ../../reference/compatible-hardware.rst:72 +#: ../../reference/compatible-hardware.rst:93 +msgid "NUC6CAYB" +msgstr "" + +#: ../../reference/compatible-hardware.rst:74 +msgid "Intel® Xeon® Bronze 3104" +msgstr "" + +#: ../../reference/compatible-hardware.rst:75 +msgid "0W23H8" +msgstr "" + +#: ../../reference/compatible-hardware.rst:77 +msgid "Intel® Atom™ C2750" +msgstr "" + +#: ../../reference/compatible-hardware.rst:78 +msgid "SuperMicro\\* A1SAi" +msgstr "" + +#: ../../reference/compatible-hardware.rst:80 +msgid "Intel® Atom™ E3825" +msgstr "" + +#: ../../reference/compatible-hardware.rst:81 +msgid "CircuitCo MinnowBoard MAX\\*" +msgstr "" + +#: ../../reference/compatible-hardware.rst:83 +msgid "Intel® Core™ i7-8700" +msgstr "" + +#: ../../reference/compatible-hardware.rst:84 +msgid "Gigabyte\\* H370 WIFI" +msgstr "" + +#: ../../reference/compatible-hardware.rst:86 +msgid "Intel® Core™ i7-3667U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:87 +msgid "Lenovo ThinkPad\\* X1 Carbon laptop" +msgstr "" + +#: ../../reference/compatible-hardware.rst:89 +msgid "Intel® Core™ i5-4210U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:90 +msgid "Dell XPS\\* 13 laptop" +msgstr "" + +#: ../../reference/compatible-hardware.rst:95 +msgid "Intel® Core™ i7-4790" +msgstr "" + +#: ../../reference/compatible-hardware.rst:96 +msgid "Gigabyte\\* desktop" +msgstr "" + +#: ../../reference/compatible-hardware.rst:99 +msgid "NUC6I6SYH" +msgstr "" + +#: ../../reference/compatible-hardware.rst:102 +msgid "NUC5I7RYH" +msgstr "" + +#: ../../reference/compatible-hardware.rst:104 +msgid "Intel® Core™ i7-4700MQ" +msgstr "" + +#: ../../reference/compatible-hardware.rst:105 +msgid "Lenovo ThinkPad\\* T540p" +msgstr "" + +#: ../../reference/compatible-hardware.rst:108 +msgid "NUC5I7RYB" +msgstr "" + +#: ../../reference/compatible-hardware.rst:111 +msgid "NUC6I5SYH" +msgstr "" + +#: ../../reference/compatible-hardware.rst:113 +msgid "\\* Other names and brands may be claimed as the property of others." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/reference/how-to-clear-overview.mo b/locale/de/LC_MESSAGES/reference/how-to-clear-overview.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/reference/how-to-clear-overview.mo differ diff --git a/locale/de/LC_MESSAGES/reference/how-to-clear-overview.po b/locale/de/LC_MESSAGES/reference/how-to-clear-overview.po new file mode 100644 index 00000000..f6cbfb7f --- /dev/null +++ b/locale/de/LC_MESSAGES/reference/how-to-clear-overview.po @@ -0,0 +1,94 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/how-to-clear-overview.rst:4 +msgid "How to Clear training overview" +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:6 +msgid "" +"The existing Linux\\* ecosystem can be challenging to users because of " +"long intervals between :abbr:`OS (operating system)` updates, which leads" +" to large update downloads. Users can also be frustrated when managing " +"complicated component dependencies. |CL-ATTR| solves these problems by:" +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:11 +msgid "Allowing you to update frequently, even multiple times per day" +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:12 +msgid "Preventing you from combining incompatible components" +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:14 +msgid "" +"The |CL| team delivers technology advances with the |CL| OS and its " +"tooling, concepts, and content. The team has created training materials " +"as a GitHub\\* project to get you up and running quickly." +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:18 +msgid "" +"The training provides complete details on the methods used to create " +"updates and how to deploy the updates to targets. The following items " +"provide an overview of these |CL| mechanisms:" +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:22 +msgid "" +"Update server: an https-enabled web server where the content files are " +"served as static content. |CL| periodically queries the data on the " +"update server and determines whether updates are available. The update " +"content files provide the data and metadata to perform the required " +"actions." +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:27 +msgid "" +"Software delivery mechanism: :abbr:`swupd (software updater)` queries " +"metadata from the update server and calculates what to do and which " +"content to use." +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:31 +msgid "" +"Tools: `mixer-tools` software suite generates the update server content " +"using |CL| official software update content, local bundle definitions, " +"and local RPM files." +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:34 +msgid "" +"The training helps you create a customized OS that is based on |CL|. The " +"training content is self-contained and hosted on GitHub. You need a clean" +" |CL| installation and a functional network connection to complete the " +"training. For convenience, the project includes the training files you " +"need for the exercises." +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:40 +msgid "" +"We appreciate your feedback and comments, especially in the form of Pull " +"Requests. Please visit the `how-to-clear project`_ page to access the " +"training materials, open a ticket, or clone/branch the training and help " +"us improve |CL|." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/reference/image-types.mo b/locale/de/LC_MESSAGES/reference/image-types.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/reference/image-types.mo differ diff --git a/locale/de/LC_MESSAGES/reference/image-types.po b/locale/de/LC_MESSAGES/reference/image-types.po new file mode 100644 index 00000000..1a68069c --- /dev/null +++ b/locale/de/LC_MESSAGES/reference/image-types.po @@ -0,0 +1,191 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/image-types.rst:4 +msgid "|CL-ATTR| image types" +msgstr "" + +#: ../../reference/image-types.rst:8 +msgid "" +"|CL-ATTR| offers many types of `images`_ for different platforms and " +"environments." +msgstr "" + +#: ../../reference/image-types.rst:12 +msgid "The naming convention of a |CL| image filename is:" +msgstr "" + +#: ../../reference/image-types.rst:18 +msgid "The *[version number]* field specifies the version number." +msgstr "" + +#: ../../reference/image-types.rst:20 +msgid "" +"The *[image type]* field specifies the type of image and its " +"corresponding file format." +msgstr "" + +#: ../../reference/image-types.rst:23 +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:28 +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:31 +msgid "Table 1: Types of platform-independent |CL| images" +msgstr "" + +#: ../../reference/image-types.rst:35 ../../reference/image-types.rst:48 +msgid "Image Type" +msgstr "" + +#: ../../reference/image-types.rst:36 ../../reference/image-types.rst:49 +msgid "Description" +msgstr "" + +#: ../../reference/image-types.rst:38 +msgid "live-desktop.img or live-desktop.iso" +msgstr "" + +#: ../../reference/image-types.rst:39 +msgid "Image for booting to GNOME\\* desktop to preview or install the OS." +msgstr "" + +#: ../../reference/image-types.rst:41 +msgid "live-server.img or live-server.iso" +msgstr "" + +#: ../../reference/image-types.rst:42 +msgid "Image for booting to server command prompt to preview or install the OS." +msgstr "" + +#: ../../reference/image-types.rst:44 +msgid "Table 2: Types of platform-specific |CL| images" +msgstr "" + +#: ../../reference/image-types.rst:51 +msgid "aws.img" +msgstr "" + +#: ../../reference/image-types.rst:52 +msgid "Image suitable for use with Amazon\\* AWS\\*." +msgstr "" + +#: ../../reference/image-types.rst:54 +msgid "azure.vhd" +msgstr "" + +#: ../../reference/image-types.rst:55 +msgid "Virtual Hard Disk for use on Microsoft\\* Azure\\* cloud platform." +msgstr "" + +#: ../../reference/image-types.rst:57 +msgid "azure-docker.vhd" +msgstr "" + +#: ../../reference/image-types.rst:58 +msgid "" +"Virtual Hard Disk for use on Microsoft Azure cloud platform with " +"Docker\\* pre-installed." +msgstr "" + +#: ../../reference/image-types.rst:60 +msgid "azure-machine-learning.vhd" +msgstr "" + +#: ../../reference/image-types.rst:61 +msgid "" +"Virtual Hard Disk for use on Microsoft Azure cloud platform with the " +"`machine-learning-basic` bundle installed." +msgstr "" + +#: ../../reference/image-types.rst:63 +msgid "cloudguest.img" +msgstr "" + +#: ../../reference/image-types.rst:64 +msgid "" +"Image with generic cloud guest virtual machine (VM) requirements " +"installed." +msgstr "" + +#: ../../reference/image-types.rst:66 +msgid "gce.tar" +msgstr "" + +#: ../../reference/image-types.rst:67 +msgid "Image with the Google Compute Engine (GCE) specific kernel." +msgstr "" + +#: ../../reference/image-types.rst:69 +msgid "hyperv.vhdx" +msgstr "" + +#: ../../reference/image-types.rst:70 +msgid "" +"Virtual Hard Disk for use with Microsoft Hyper-V\\* hypervisor. Includes " +"`optimized kernel`_ for Hyper-V." +msgstr "" + +#: ../../reference/image-types.rst:72 +msgid "kvm.img" +msgstr "" + +#: ../../reference/image-types.rst:73 +msgid "" +"Image for booting in a simple VM with start_qemu.sh. Includes `optimized " +"kernel`_ for KVM." +msgstr "" + +#: ../../reference/image-types.rst:76 +msgid "kvm-legacy.img" +msgstr "" + +#: ../../reference/image-types.rst:77 +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:79 +msgid "pxe.tar" +msgstr "" + +#: ../../reference/image-types.rst:80 +msgid "Image suitable for use with PXE server." +msgstr "" + +#: ../../reference/image-types.rst:82 +msgid "vmware.vmdk" +msgstr "" + +#: ../../reference/image-types.rst:83 +msgid "" +"Virtual Machine Disk for VMware\\* platforms inclduing Player, " +"Workstation, and ESXi." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/reference/reference.mo b/locale/de/LC_MESSAGES/reference/reference.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/reference/reference.mo differ diff --git a/locale/de/LC_MESSAGES/reference/reference.po b/locale/de/LC_MESSAGES/reference/reference.po new file mode 100644 index 00000000..f2de2b3a --- /dev/null +++ b/locale/de/LC_MESSAGES/reference/reference.po @@ -0,0 +1,34 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/reference.rst:4 +msgid "Reference" +msgstr "" + +#: ../../reference/reference.rst:6 +msgid "" +"This section provides additional information on the |CL| project and " +"features." +msgstr "" + +#: ../../reference/reference.rst:24 +msgid "Clear Linux concepts" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/reference/system-requirements.mo b/locale/de/LC_MESSAGES/reference/system-requirements.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/reference/system-requirements.mo differ diff --git a/locale/de/LC_MESSAGES/reference/system-requirements.po b/locale/de/LC_MESSAGES/reference/system-requirements.po new file mode 100644 index 00000000..9df1c30e --- /dev/null +++ b/locale/de/LC_MESSAGES/reference/system-requirements.po @@ -0,0 +1,124 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/system-requirements.rst:4 +msgid "Recommended minimum system requirements" +msgstr "" + +#: ../../reference/system-requirements.rst:6 +msgid "" +"|CL-ATTR| can run on very minimal hardware. For example, it can run on a " +"system with a single core CPU, 128MB of memory, and 600MB of disk space." +msgstr "" + +#: ../../reference/system-requirements.rst:9 +msgid "" +"Different use cases and applications will require different " +"configurations. For general |CL| use, in addition to a supported " +"processor, the recommended minimum requirements include:" +msgstr "" + +#: ../../reference/system-requirements.rst:13 +msgid "Processors:" +msgstr "" + +#: ../../reference/system-requirements.rst:15 +msgid "" +"|CL-ATTR| can run on any Intel® 64bit processors which support UEFI\\* " +"and SSE\\* v4.1 streaming SIMD\\* instructions." +msgstr "" + +#: ../../reference/system-requirements.rst:18 +msgid "The following processor families have been verified to run |CL|:" +msgstr "" + +#: ../../reference/system-requirements.rst:20 +msgid "2nd Generation, or later, Intel® Core™ processor family." +msgstr "" + +#: ../../reference/system-requirements.rst:21 +msgid "Intel® Xeon® Processor E3" +msgstr "" + +#: ../../reference/system-requirements.rst:22 +msgid "Intel® Xeon® Processor E5" +msgstr "" + +#: ../../reference/system-requirements.rst:23 +msgid "Intel® Xeon® Processor E7" +msgstr "" + +#: ../../reference/system-requirements.rst:24 +msgid "" +"Intel® Atom™ processor C2000 product family for servers -- Q3 2013 " +"version or later." +msgstr "" + +#: ../../reference/system-requirements.rst:26 +msgid "Intel® Atom™ processor E3800 series -- Q4 2013 version or later." +msgstr "" + +#: ../../reference/system-requirements.rst:28 +msgid "" +"To help determine if a processor is supported, you can run a " +":ref:`compatibility check` or go to " +"http://ark.intel.com and check for these features:" +msgstr "" + +#: ../../reference/system-requirements.rst:32 +msgid "Instruction Set = 64-bit" +msgstr "" + +#: ../../reference/system-requirements.rst:33 +msgid "Instruction Set Extensions = SSSE3" +msgstr "" + +#: ../../reference/system-requirements.rst:34 +msgid "Instruction Set Extensions = SSE 4.1" +msgstr "" + +#: ../../reference/system-requirements.rst:35 +msgid "Instruction Set Extensions = SSE 4.2" +msgstr "" + +#: ../../reference/system-requirements.rst:36 +msgid "Instruction Set Extensions = AES" +msgstr "" + +#: ../../reference/system-requirements.rst:37 +msgid "Instruction Set Extensions = PCLMUL" +msgstr "" + +#: ../../reference/system-requirements.rst:39 +msgid "Memory: 4GB RAM" +msgstr "" + +#: ../../reference/system-requirements.rst:41 +msgid "Hard Disk: 20GB HDD" +msgstr "" + +#: ../../reference/system-requirements.rst:43 +msgid "Network: Active Internet connection" +msgstr "" + +#: ../../reference/system-requirements.rst:45 +msgid "Graphics: Intel HD Graphics (required if running a GUI desktop)" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tooling/autoproxy.mo b/locale/de/LC_MESSAGES/tooling/autoproxy.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tooling/autoproxy.mo differ diff --git a/locale/de/LC_MESSAGES/tooling/autoproxy.po b/locale/de/LC_MESSAGES/tooling/autoproxy.po new file mode 100644 index 00000000..298045a3 --- /dev/null +++ b/locale/de/LC_MESSAGES/tooling/autoproxy.po @@ -0,0 +1,162 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tooling/autoproxy.rst:4 +msgid "Autoproxy" +msgstr "" + +#: ../../tooling/autoproxy.rst:6 +msgid "" +"Autoproxy is provided to enable |CL-ATTR| to work smoothly behind a " +"corporate proxy." +msgstr "" + +#: ../../tooling/autoproxy.rst:14 +msgid "Description" +msgstr "" + +#: ../../tooling/autoproxy.rst:16 +msgid "" +"Autoproxy tries to detect a Proxy Auto-Config (PAC) script and use it to " +"automatically resolve the proxy needed for a given connection. With " +"Autoproxy, you can use |CL| inside any proxy environment without having " +"to manually configure the proxies." +msgstr "" + +#: ../../tooling/autoproxy.rst:21 +msgid "" +"Corporate and private networks can be very complex, needing to restrict " +"and control network connections for security reasons. The typical side " +"effects are limited or blocked connectivity, and require manual " +"configuration of proxies to perform the most mundane tasks, such as " +"cloning a repo or checking for updates. With |CL|, all of the work is " +"done behind the scenes to effortlessly use your network and have " +"connections “just work”." +msgstr "" + +#: ../../tooling/autoproxy.rst:28 +msgid "" +"This feature removes severe complications with network connectivity due " +"to proxy issues. You can automate tasks, such as unit testing, without " +"worrying about the proxy not being set, and you can remove unset proxies " +"from the equation when dealing with network unavailability across " +"systems." +msgstr "" + +#: ../../tooling/autoproxy.rst:34 +msgid "How it works" +msgstr "" + +#: ../../tooling/autoproxy.rst:36 +msgid "" +"We designed Autoproxy around tools provided by most Linux\\* " +"distributions with a few minor additions and modifications. We leveraged " +"the DHCP and network information obtained from systemd and created a PAC-" +"discovery daemon. The daemon uses the information to resolve a URL for a " +"PAC file. The daemon then passes the URL into PACrunner\\*. PACrunner " +"downloads the PAC file and uses the newly implemented Duktape\\* engine " +"to parse it." +msgstr "" + +#: ../../tooling/autoproxy.rst:47 +msgid "Figure 1: Autoproxy Flow" +msgstr "" + +#: ../../tooling/autoproxy.rst:49 +msgid "" +"From that point on, any cURL\\* or network requests query PACrunner for " +"the correct proxy to use. We modified the cURL library to communicate " +"with PACrunner over DBus. However, cURL will ignore PACrunner and run " +"normally if no PAC file is loaded or if you manually set any proxies. " +"Thus, your environment settings are respected and no time is wasted " +"trying to resolve a proxy. All these steps happen in the background with " +"no user interaction." +msgstr "" + +#: ../../tooling/autoproxy.rst:57 +msgid "Troubleshooting" +msgstr "" + +#: ../../tooling/autoproxy.rst:59 +msgid "" +"Autoproxy allows |CL| to operate seamlessly behind a proxy because " +":ref:`swupd ` and other |CL| tools are implemented on top of" +" libcurl. Tools that do not use libcurl, like git, must be configured " +"independently." +msgstr "" + +#: ../../tooling/autoproxy.rst:64 +msgid "" +"If you are familiar with PAC files and WPAD, you can use " +":command:`pacdiscovery` and :command:`FindProxyForURL` to troubleshoot " +"problems with autproxy." +msgstr "" + +#: ../../tooling/autoproxy.rst:70 +msgid "Learn more about WPAD, PAC files, and PAC functions at `findproxyforurl`_." +msgstr "" + +#: ../../tooling/autoproxy.rst:74 +msgid "Run :command:`pacdiscovery` with no arguments to indicate" +msgstr "" + +#: ../../tooling/autoproxy.rst:76 +msgid "if there is a problem resolving the :command:`WPAD` host name resolution:" +msgstr "" + +#: ../../tooling/autoproxy.rst:87 +msgid "or if the :command:`pacrunner` service is disabled (masked)." +msgstr "" + +#: ../../tooling/autoproxy.rst:98 +msgid "Unmask the :command:`pacrunner` service by running:" +msgstr "" + +#: ../../tooling/autoproxy.rst:104 +msgid "" +":command:`FindProxyForURL` with :command:`busctl` can also indicate if " +"the :command:`pacrunner.service` is masked." +msgstr "" + +#: ../../tooling/autoproxy.rst:117 +msgid "" +":command:`FindProxyForURL` returns the URL and port of the proxy server " +"when an external URL and host are provided as arguments." +msgstr "" + +#: ../../tooling/autoproxy.rst:129 +msgid "" +"If a proxy server is not avialable, or if :command:`pacrunner` is running" +" without a PAC file, :command:`FindProxyForURL` will return \"DIRECT\"." +msgstr "" + +#: ../../tooling/autoproxy.rst:141 +msgid "" +"Once :command:`pacdiscovery` is able to look up :command:`WPAD`, restart " +"the :command:`pacrunner` service:" +msgstr "" + +#: ../../tooling/autoproxy.rst:151 +msgid "" +"A \"domain\" or \"search\" entry in :file:`/etc/resolv.conf` is required " +"for short name lookups to resolve. The :file:`resolv.conf` man page has " +"additional details." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tooling/autospec.mo b/locale/de/LC_MESSAGES/tooling/autospec.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tooling/autospec.mo differ diff --git a/locale/de/LC_MESSAGES/tooling/autospec.po b/locale/de/LC_MESSAGES/tooling/autospec.po new file mode 100644 index 00000000..32e603ea --- /dev/null +++ b/locale/de/LC_MESSAGES/tooling/autospec.po @@ -0,0 +1,576 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tooling/autospec.rst:4 +msgid "autospec" +msgstr "" + +#: ../../tooling/autospec.rst:6 +msgid "" +"**autospec** is a tool used to assist with the automated creation and " +"maintenance of RPM packaging in |CL-ATTR|. Where a standard :abbr:`RPM " +"(RPM Package Manager)` build process using :command:`rpmbuild` requires a" +" tarball and :file:`.spec` file to start, autospec requires only a " +"tarball and package name to start." +msgstr "" + +#: ../../tooling/autospec.rst:16 +msgid "Description" +msgstr "" + +#: ../../tooling/autospec.rst:18 +msgid "" +"The autospec tool attempts to infer the requirements of the :file:`.spec`" +" file by analyzing the source code and :file:`Makefile` information. It " +"continuously runs updated builds based on new information discovered from" +" build failures until it has a complete and valid :file:`.spec` file. If " +"needed, you can influence the behavior of autospec and customize the " +"build by providing optional `control files`_ to the autospec tool." +msgstr "" + +#: ../../tooling/autospec.rst:25 +msgid "" +"autospec uses **mock** as a sandbox to run the builds. Visit the `mock " +"wiki`_ for additional information on using mock." +msgstr "" + +#: ../../tooling/autospec.rst:28 +msgid "" +"For a general understanding of how an RPM works, visit the `rpm website`_" +" or the `RPM Packaging Guide`_ ." +msgstr "" + +#: ../../tooling/autospec.rst:32 +msgid "How it works" +msgstr "" + +#: ../../tooling/autospec.rst:34 +msgid "Learn the autospec tool set up and process." +msgstr "" + +#: ../../tooling/autospec.rst:41 +msgid "Prerequisites" +msgstr "" + +#: ../../tooling/autospec.rst:43 +msgid "" +"The setup for building source in |CL| must be completed before using the " +"autospec tool." +msgstr "" + +#: ../../tooling/autospec.rst:46 +msgid "" +"Refer to `Setup environment to build source`_ for instructions on " +"completing the setup." +msgstr "" + +#: ../../tooling/autospec.rst:50 +msgid "Create an RPM" +msgstr "" + +#: ../../tooling/autospec.rst:52 +msgid "The basic autospec process is described in the following steps:" +msgstr "" + +#: ../../tooling/autospec.rst:54 +msgid "" +"The :command:`make autospec` command generates a :file:`.spec` file based" +" on the analysis of code and existing control files." +msgstr "" + +#: ../../tooling/autospec.rst:57 +msgid "" +"Any control files should be located in the same directory as the " +"resulting :file:`.spec` file." +msgstr "" + +#: ../../tooling/autospec.rst:60 +msgid "View the `autospec README`_ for more information on `control files`_." +msgstr "" + +#: ../../tooling/autospec.rst:62 +msgid "autospec creates a build root with mock config." +msgstr "" + +#: ../../tooling/autospec.rst:64 +msgid "autospec attempts to build an RPM from the generated :file:`.spec`." +msgstr "" + +#: ../../tooling/autospec.rst:66 +msgid "autospec detects any missed declarations in the :file:`.spec`." +msgstr "" + +#: ../../tooling/autospec.rst:68 +msgid "" +"If build errors occur, autospec scans the build log to try to detect the " +"root cause." +msgstr "" + +#: ../../tooling/autospec.rst:71 +msgid "" +"If autospec detects the root cause and knows how to continue, it restarts" +" the build automatically at step 1 with updated build instructions." +msgstr "" + +#: ../../tooling/autospec.rst:74 +msgid "" +"Otherwise, autospec stops the build for user inspection to resolve the " +"errors. Respond to the build process output by fixing source code issues " +"and/or editing control files to resolve issues, which may include " +"dependencies or exclusions. See `autospec README`_ for more information " +"on control files." +msgstr "" + +#: ../../tooling/autospec.rst:80 +msgid "The user resumes the process at step 1 after errors are resolved." +msgstr "" + +#: ../../tooling/autospec.rst:82 +msgid "" +"If a binary dependency doesn't exist in |CL|, you must build it before " +"running autospec again." +msgstr "" + +#: ../../tooling/autospec.rst:85 +msgid "" +"Following these steps, autospec continues to rebuild the package, based " +"on new information discovered from build failures, until it has a valid " +":file:`.spec`. If no build errors occur, RPM packages are successfully " +"built." +msgstr "" + +#: ../../tooling/autospec.rst:90 +msgid "Examples" +msgstr "" + +#: ../../tooling/autospec.rst:92 +msgid "Complete `Setup environment to build source`_ before using these examples." +msgstr "" + +#: ../../tooling/autospec.rst:99 +msgid "Example 1: Build RPM with an existing spec file" +msgstr "" + +#: ../../tooling/autospec.rst:101 +msgid "" +"This example shows how to build a RPM from a pre-packaged upstream " +"package with an existing spec file. The example uses the ``dmidecode`` " +"package." +msgstr "" + +#: ../../tooling/autospec.rst:104 ../../tooling/autospec.rst:160 +msgid "Navigate to the autospec workspace and clone the ``dmidecode`` package:" +msgstr "" + +#: ../../tooling/autospec.rst:113 +msgid "You can clone all package repos at once using the following command:" +msgstr "" + +#: ../../tooling/autospec.rst:119 ../../tooling/autospec.rst:216 +msgid "The optional NUM is the number of threads to use." +msgstr "" + +#: ../../tooling/autospec.rst:121 +msgid "" +"For a list of available packages, view the " +":file:`~/clearlinux/projects/common/packages` file." +msgstr "" + +#: ../../tooling/autospec.rst:124 +msgid "Navigate to the local copy of the ``dmidecode`` package and build it:" +msgstr "" + +#: ../../tooling/autospec.rst:131 +msgid "" +"The resulting RPMs are in :file:`./rpms`. Build logs and additional RPMs " +"are in :file:`./results`." +msgstr "" + +#: ../../tooling/autospec.rst:135 +msgid "Example 2: Build a new RPM" +msgstr "" + +#: ../../tooling/autospec.rst:137 +msgid "" +"This example shows how to build a new RPM with no spec file. The example " +"will create a simple helloclear RPM." +msgstr "" + +#: ../../tooling/autospec.rst:140 +msgid "" +"Navigate to the autospec workspace and build the helloclear RPM. The " +":file:`Makefile` provides a :command:`make autospecnew` that can " +"automatically generate an RPM package using the autospec tool. You must " +"pass the URL to the source tarball and the NAME of the RPM you wish to " +"create:" +msgstr "" + +#: ../../tooling/autospec.rst:150 +msgid "" +"The resulting RPMs are in :file:`./packages/helloclear/rpms`. Build logs " +"and additional RPMs are in :file:`./packages/helloclear/results`." +msgstr "" + +#: ../../tooling/autospec.rst:154 +msgid "Example 3: Generate a new spec file with a pre-defined package" +msgstr "" + +#: ../../tooling/autospec.rst:156 +msgid "" +"This example shows how to modify an existing package to create a custom " +"RPM. In this example you will make a simple change to the ``dmidecode`` " +"package and rebuild the package." +msgstr "" + +#: ../../tooling/autospec.rst:167 +msgid "Navigate into the *dmidecode* directory:" +msgstr "" + +#: ../../tooling/autospec.rst:173 +msgid "Open the :file:`excludes` file with an editor and add these lines:" +msgstr "" + +#: ../../tooling/autospec.rst:186 +msgid "" +"These files aren't needed by dmidecode, so we can remove them without any" +" issues." +msgstr "" + +#: ../../tooling/autospec.rst:189 +msgid "" +"In the :file:`dmidecode` directory, build the modified ``dmidecode`` " +"package:" +msgstr "" + +#: ../../tooling/autospec.rst:195 +msgid "The resulting RPMs are in :file:`./rpms`. Logs are in :file:`./results`." +msgstr "" + +#: ../../tooling/autospec.rst:198 +msgid "Example 4: Provide control files to autospec" +msgstr "" + +#: ../../tooling/autospec.rst:200 +msgid "" +"This example shows how to modify control files to correct build failures " +"that autospec is unable to resolve. In this example, you will add a " +"missing license and dependencies so autospec can complete a successful " +"build." +msgstr "" + +#: ../../tooling/autospec.rst:204 +msgid "Navigate to the autospec workspace:" +msgstr "" + +#: ../../tooling/autospec.rst:210 +msgid "If you have not already, clone all upstream package repos:" +msgstr "" + +#: ../../tooling/autospec.rst:220 +msgid "" +"In a later step of this example, we will search the cloned package repos " +"for a missing dependency." +msgstr "" + +#: ../../tooling/autospec.rst:223 +msgid "Build the opae-sdk RPM:" +msgstr "" + +#: ../../tooling/autospec.rst:229 +msgid "This results in an error for a missing license file:" +msgstr "" + +#: ../../tooling/autospec.rst:235 +msgid "Navigate to the package with build failures:" +msgstr "" + +#: ../../tooling/autospec.rst:241 +msgid "" +"Add one or more valid license identifiers from the `SPDX License List " +"`_. In the example below, two different " +"licenses are appropriate based on the opae-sdk project licensing:" +msgstr "" + +#: ../../tooling/autospec.rst:250 +msgid "Run autospec again:" +msgstr "" + +#: ../../tooling/autospec.rst:256 +msgid "This results in a generic error:" +msgstr "" + +#: ../../tooling/autospec.rst:262 +msgid "Open the build log to view the error details:" +msgstr "" + +#: ../../tooling/autospec.rst:268 +msgid "" +"The build log contains details for the specific failures. In this " +"instance, there are missing dependencies:" +msgstr "" + +#: ../../tooling/autospec.rst:281 +msgid "" +"Search the spec files of upstream |CL| packages to see if the json-c " +"library is available. In this case, it does exist and we'll add the " +"json-c 'dev' package into the buildreq_add:" +msgstr "" + +#: ../../tooling/autospec.rst:292 +msgid "" +"This search step works only if the user cloned all of the upstream " +"package repos. In this example, upstream package repos were cloned in a " +"previous step." +msgstr "" + +#: ../../tooling/autospec.rst:296 +msgid "" +"Search the spec files of upstream |CL| packages to see if the libuuid " +"library is available. In this case, it exists in the util-linux package, " +"so we'll add util-linux-dev package into the buildreq_add:" +msgstr "" + +#: ../../tooling/autospec.rst:305 +msgid "" +"Run autospec again and find the successfully-generated RPMs in the " +":file:`rpms` directory:" +msgstr "" + +#: ../../tooling/autospec.rst:314 +msgid "" +"If you need a dependency that does not exist in the |CL| repo, you must " +"first build it manually (see `Example 2: Build a new RPM`_), then add the" +" repo so that autospec knows the package exists. For example:" +msgstr "" + +#: ../../tooling/autospec.rst:324 +msgid "" +"You only need to add the dependency to the :file:`buildreq_add` control " +"file if autospec is not able to automatically find the correct dependency" +" on its own." +msgstr "" + +#: ../../tooling/autospec.rst:329 +msgid "Test packaged software" +msgstr "" + +#: ../../tooling/autospec.rst:331 +msgid "" +"After software has been packaged with autospec, the resulting RPMs can be" +" tested for functionality before being integrated and deployed into a " +"|CL| image with the :ref:`Mixer tool `." +msgstr "" + +#: ../../tooling/autospec.rst:335 +msgid "" +"The |CL| development tooling offers two ways to quickly test autospec " +"generated RPMs." +msgstr "" + +#: ../../tooling/autospec.rst:339 +msgid "" +"The methods outlined below should only be used for temporary testing on " +"development systems." +msgstr "" + +#: ../../tooling/autospec.rst:344 +msgid "Test in a |CL| virtual machine" +msgstr "" + +#: ../../tooling/autospec.rst:346 +msgid "" +"The |CL| development tooling includes a method to install RPMs into a " +"|CL| virtual machine running on the KVM hypervisor. Using a :abbr:`VM " +"(Virtual Machine)` allows testing in a completely isolated environment." +msgstr "" + +#: ../../tooling/autospec.rst:350 +msgid "To test an autospec-created package inside a VM:" +msgstr "" + +#: ../../tooling/autospec.rst:352 +msgid "" +"Download the |CL| KVM image into the :file:`~/clearlinux` directory as " +":file:`clear.img`. The location and name :file:`clear.img.xz` is " +"important for the tooling to work:" +msgstr "" + +#: ../../tooling/autospec.rst:361 +msgid "Extract the downloaded |CL| KVM image:" +msgstr "" + +#: ../../tooling/autospec.rst:367 +msgid "" +"Copy the QEMU start script and virtual firmware needed for KVM into the " +":file:`~/clearlinux` directory:" +msgstr "" + +#: ../../tooling/autospec.rst:375 +msgid "" +"Run :command:`make install` from the package's autospec directory. The " +":command:`make install` command mounts the downloaded |CL| KVM image and " +"installs the autospec-created RPM into it:" +msgstr "" + +#: ../../tooling/autospec.rst:384 +msgid "" +"The code that makes this possible can be viewed by searching for the " +"*install:* target in the `Makefile.common file on GitHub`_." +msgstr "" + +#: ../../tooling/autospec.rst:387 +msgid "Return to the :file:`~/clearlinux` directory and start the |CL| VM:" +msgstr "" + +#: ../../tooling/autospec.rst:394 +msgid "" +"A new |CL| VM will launch in the console. Log into the VM as *root* and " +"set a new pasword for the VM." +msgstr "" + +#: ../../tooling/autospec.rst:397 +msgid "" +"Check that the software is installed in the |CL| VM as expected and " +"perform any relevant tests." +msgstr "" + +#: ../../tooling/autospec.rst:400 +msgid "" +"After testing has been completed, the |CL| VM can be powered off and " +"deleted:" +msgstr "" + +#: ../../tooling/autospec.rst:410 +msgid "Test directly on a development machine" +msgstr "" + +#: ../../tooling/autospec.rst:412 +msgid "" +"The |CL| development tooling also includes a method to extract autospec-" +"created RPMs locally onto a |CL| development system for testing. " +"Extracting an RPM directly onto a system offers quicker testing; however" +" conflicts may occur and responsibility to remove the software after " +"testing is up to the developer." +msgstr "" + +#: ../../tooling/autospec.rst:418 +msgid "" +"To test an autospec created package directly on the |CL| development " +"system:" +msgstr "" + +#: ../../tooling/autospec.rst:420 +msgid "" +"Run :command:`make install-local` from the package's autospec directory. " +"The :command:`make install-local` command extracts the RPM directly onto " +"the filesystem of the running |CL| system:" +msgstr "" + +#: ../../tooling/autospec.rst:429 +msgid "" +"The code that makes this possible can be viewed by searching for the " +"*install-local:* target in the `Makefile.common file on GitHub`_." +msgstr "" + +#: ../../tooling/autospec.rst:432 +msgid "" +"Check that the software is installed as expected and perform any relevant" +" tests." +msgstr "" + +#: ../../tooling/autospec.rst:435 +msgid "" +"After testing has been completed, the software and any related files must" +" be identified and deleted. The :command:`swupd repair --picky` command " +"can help restore the state of the :file:`/usr` directory (see :ref:`swupd" +" `) however any other files must be cleaned up manually." +msgstr "" + +#: ../../tooling/autospec.rst:443 +msgid "References" +msgstr "" + +#: ../../tooling/autospec.rst:445 +msgid "" +"Reference the `autospec README`_ for details regarding `autospec` " +"commands and options." +msgstr "" + +#: ../../tooling/autospec.rst:448 +msgid "Setup environment to build source" +msgstr "" + +#: ../../tooling/autospec.rst:452 +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:456 +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:461 +msgid "Follow these steps to setup the workspace and tooling for building source:" +msgstr "" + +#: ../../tooling/autospec.rst:463 +msgid "Install the :command:`os-clr-on-clr` bundle:" +msgstr "" + +#: ../../tooling/autospec.rst:469 +msgid "Download the :file:`user-setup.sh` script:" +msgstr "" + +#: ../../tooling/autospec.rst:475 +msgid "Make :file:`user-setup.sh` executable:" +msgstr "" + +#: ../../tooling/autospec.rst:481 +msgid "Run the script as an unprivileged user:" +msgstr "" + +#: ../../tooling/autospec.rst:487 +msgid "" +"After the script completes, log out and log in again to complete the " +"setup process." +msgstr "" + +#: ../../tooling/autospec.rst:490 +msgid "Set your Git user email and username for the repos on your system:" +msgstr "" + +#: ../../tooling/autospec.rst:497 +msgid "This global setting is used by |CL| tools that make use of Git." +msgstr "" + +#: ../../tooling/autospec.rst:502 +msgid "Related topics" +msgstr "" + +#: ../../tooling/autospec.rst:504 +msgid ":ref:`Mixer tool `" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tooling/compatible-kernels.mo b/locale/de/LC_MESSAGES/tooling/compatible-kernels.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tooling/compatible-kernels.mo differ diff --git a/locale/de/LC_MESSAGES/tooling/compatible-kernels.po b/locale/de/LC_MESSAGES/tooling/compatible-kernels.po new file mode 100644 index 00000000..5fc6f59b --- /dev/null +++ b/locale/de/LC_MESSAGES/tooling/compatible-kernels.po @@ -0,0 +1,135 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tooling/compatible-kernels.rst:4 +msgid "Kernels" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:6 +msgid "" +"The |CL-ATTR| provides the following Linux kernels with a respective " +"bundle. This document describes the specific use cases these `bundles`_ " +"serve and provides links to their source code." +msgstr "" + +#: ../../tooling/compatible-kernels.rst:11 +msgid "Bare metal only" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:17 +msgid "Kernel native" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:14 +msgid "" +"The *kernel-native* bundle focuses on the bare metal platforms. It is " +"optimized for fast booting and performs best on the Intel® architectures " +"described on the :ref:`supported hardware list`. The" +" optimization patches are found in our `Linux`_ GitHub\\* repo." +msgstr "" + +#: ../../tooling/compatible-kernels.rst:24 +msgid "Kernel Container" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:20 +msgid "" +"The *kernel-container* bundle contains the kernel used by the Intel® " +"Clear Containers project. This kernel is optimized for fast booting and " +"performs best on |CC| running on the Intel® architectures described on " +"the :ref:`supported hardware list`. The optimization" +" patches are found in our `Linux-Container`_ GitHub repo." +msgstr "" + +#: ../../tooling/compatible-kernels.rst:29 +msgid "Also compatible with VMs" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:39 +msgid "Kernel LTS" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:32 +msgid "" +"The *kernel-lts* bundle focuses on the bare metal platforms but uses the " +"latest :abbr:`LTS (Long Term Support)` Linux kernel. It is optimized for " +"fast booting and performs best on the Intel® architectures described on " +"the :ref:`supported hardware list`. Additionally, " +"this kernel includes the VirtualBox\\* kernel modules, see our " +":ref:`instructions on using Virtualbox` for more" +" information. The optimization patches are found in our `Linux-LTS`_ " +"GitHub repo." +msgstr "" + +#: ../../tooling/compatible-kernels.rst:42 +msgid "VM only" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:54 +msgid "Kernel KVM" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:45 +msgid "" +"The *kernel-kvm* bundle focuses on the Linux :abbr:`KVM (Kernel-based " +"Virtual Machine)`. It is optimized for fast booting and performs best on " +"Virtual Machines running on the Intel® architectures described on the " +":ref:`supported hardware list`. Use this kernel when" +" running |CL| as the guest OS on top of *qemu/kvm*. Use this kernel with " +"**cloud orchestrators** using *qemu/kvm* internally as their " +"**hypervisor** . This kernel can be used as a standalone |CL| VM, see our" +" :ref:`instructions on using KVM` for more information. The " +"optimization patches are found in our `Linux-KVM`_ GitHub repo." +msgstr "" + +#: ../../tooling/compatible-kernels.rst:65 +msgid "Kernel Hyper-V\\*" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:57 +msgid "" +"The *kernel-hyperv* bundle focuses on running Linux on Microsoft\\* " +"Hyper-V. It is optimized for fast booting and performs best on Virtual " +"Machines running on the Intel® architectures described on the " +":ref:`supported hardware list`. Use this kernel when" +" running |CL| as the guest OS of **Cloud Instances** in projects such as " +"Microsoft `Azure`_\\*. This kernel can be used in a standalone |CL| VM, " +"see our :ref:`instructions on using Hyper-V` for more " +"information. The optimization patches are found in our `Linux-HyperV`_ " +"GitHub repo." +msgstr "" + +#: ../../tooling/compatible-kernels.rst:78 +msgid "Kernel Hyper-V LTS" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:68 +msgid "" +"The *kernel-hyperv-lts* bundle focuses on running Linux on Microsoft " +"Hyper-V but uses the latest :abbr:`LTS (Long Term Support)` Linux kernel." +" It is optimized for fast booting and performs best on Virtual Machines " +"running on the Intel® architectures described on the :ref:`supported " +"hardware list`. Use this kernel when running |CL| as" +" the guest OS of **Cloud Instances** in projects such as Microsoft " +"`Azure`_. This kernel can be used in a standalone |CL| VM, see our " +":ref:`instructions on using Hyper-V` for more information. The " +"optimization patches are found in our `Linux-HyperV-LTS`_ GitHub repo." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tooling/debug.mo b/locale/de/LC_MESSAGES/tooling/debug.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tooling/debug.mo differ diff --git a/locale/de/LC_MESSAGES/tooling/debug.po b/locale/de/LC_MESSAGES/tooling/debug.po new file mode 100644 index 00000000..3d55a821 --- /dev/null +++ b/locale/de/LC_MESSAGES/tooling/debug.po @@ -0,0 +1,131 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tooling/debug.rst:4 +msgid "Debug System" +msgstr "" + +#: ../../tooling/debug.rst:6 +msgid "" +"|CL-ATTR| introduces a novel approach to system software debugging using " +"*clr-debug-info*. On the client side, the |CL| debug system obtains any " +"necessary debug information on-the-fly over a network during a debugging " +"session. On the server side, the system curates and compresses debug " +"information into small pieces for efficient downloading." +msgstr "" + +#: ../../tooling/debug.rst:12 +msgid "" +"For developers, this avoids the interruption during debugging that " +"usually happens when debug information is missing. This can be especially" +" useful on systems where storage is limited." +msgstr "" + +#: ../../tooling/debug.rst:22 +msgid "Background" +msgstr "" + +#: ../../tooling/debug.rst:24 +msgid "" +"Software that is compiled and packaged for general usage in an operating " +"system typically only contains components that are used to execute the " +"program, such as binaries and libraries. Extra developer data, such as " +"the actual source code and symbol information, are separated and excluded" +" for efficiency." +msgstr "" + +#: ../../tooling/debug.rst:30 +msgid "" +"The debug information helps relate binary code to human readable source " +"code lines and variables. Most of the time, this auxiliary information is" +" not needed; however without it, debugging a program results in limited " +"visibility." +msgstr "" + +#: ../../tooling/debug.rst:37 +msgid "Usage" +msgstr "" + +#: ../../tooling/debug.rst:39 +msgid "" +"The clr-debug-info system is integrated into |CL| and seamlessly engages " +"once installed." +msgstr "" + +#: ../../tooling/debug.rst:42 +msgid "Install the *dev-utils* bundle." +msgstr "" + +#: ../../tooling/debug.rst:50 +msgid "" +"The *telemetrics* and *performance-tools* bundles also include clr-debug-" +"info." +msgstr "" + +#: ../../tooling/debug.rst:54 +msgid "" +"Start a debugging session against a program using a debugger, such as " +"GDB. For example, to debug *gnome-control-center* execute the following " +"command:" +msgstr "" + +#: ../../tooling/debug.rst:62 +msgid "" +"As you step through the program and debug information is needed, the " +"clr_debug_daemon obtains it in the background." +msgstr "" + +#: ../../tooling/debug.rst:67 +msgid "Implementation" +msgstr "" + +#: ../../tooling/debug.rst:69 +msgid "" +"The implementation of the |CL| debug system is open source and available " +"on GitHub at: https://github.com/clearlinux/clr-debug-info/" +msgstr "" + +#: ../../tooling/debug.rst:76 +msgid "Figure 1: The communication flow of the |CL| debug system" +msgstr "" + +#: ../../tooling/debug.rst:78 +msgid "" +"The |CL| debug system implements a :abbr:`FUSE (filesystem in userspace)`" +" filesystem mounted at :file:`/usr/lib/debug` and :file:`/usr/src/debug`." +" The FUSE filesystem starts automatically. You can verify its status by " +"executing :command:`systemctl status clr_debug_fuse.service`." +msgstr "" + +#: ../../tooling/debug.rst:83 +msgid "" +"The *clr_debug_daemon* is responsible for fetching the appropriate " +"package debug content from the server and making it available for any " +"debugging programs that need it. It is socket activated whenever a " +"request to the local FUSE filesystem occurs. You can verify its status " +"with :command:`systemctl status clr_debug_daemon.service`." +msgstr "" + +#: ../../tooling/debug.rst:90 +msgid "" +"|CL| hosts debuginfo content packaged for consumption by |CL| debug " +"clients at https://download.clearlinux.org/debuginfo/" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tooling/ister.mo b/locale/de/LC_MESSAGES/tooling/ister.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tooling/ister.mo differ diff --git a/locale/de/LC_MESSAGES/tooling/ister.po b/locale/de/LC_MESSAGES/tooling/ister.po new file mode 100644 index 00000000..9eb9249f --- /dev/null +++ b/locale/de/LC_MESSAGES/tooling/ister.po @@ -0,0 +1,166 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tooling/ister.rst:4 +msgid "ister.py image builder" +msgstr "" + +#: ../../tooling/ister.rst:6 +msgid "" +"The `ister.py tool`_ is a template-based installer used by |CL-ATTR| to " +"produce images for each release. The same ister tool is available for use" +" in |CL| to create custom images based on an upstream image." +msgstr "" + +#: ../../tooling/ister.rst:15 +msgid "Description" +msgstr "" + +#: ../../tooling/ister.rst:17 +msgid "" +"|CL| is a rolling release and produces an average of 10 releases per week" +" using the ister tool. With each release we produce multiple :ref:`image " +"types for different environments ` and use cases such as " +"installers, Hyper-V, KVM, or VMWare." +msgstr "" + +#: ../../tooling/ister.rst:22 +msgid "" +"Each image has a JSON configuration file that is used by ister to " +"generate the image. These JSON configuration files describe the image " +"type, partitions, version, and bundles that will be preinstalled by " +"default with the image. For each image type we produce, the corresponding" +" JSON configuration file for the image also is published." +msgstr "" + +#: ../../tooling/ister.rst:28 +msgid "" +"The :ref:`mixer` tool also uses ister to build images for your " +"custom mix. Like upstream images, a JSON configuration file is defined " +"for the image, which ister uses to generate the image. Refer to the " +":ref:`mixer` guide for instructions on using ister to build an " +"image for a custom mix." +msgstr "" + +#: ../../tooling/ister.rst:34 +msgid "Examples" +msgstr "" + +#: ../../tooling/ister.rst:37 +msgid "Recreate an upstream image" +msgstr "" + +#: ../../tooling/ister.rst:39 +msgid "" +"The published configuration files for upstream images may be used to " +"recreate an image. Here are some examples:" +msgstr "" + +#: ../../tooling/ister.rst:42 +msgid "" +"Use an older version of |CL| and the image is no longer available (only " +"after March 2017)." +msgstr "" + +#: ../../tooling/ister.rst:44 +msgid "Customize the partitions of an image." +msgstr "" + +#: ../../tooling/ister.rst:45 +msgid "Customize the bundles preinstalled in an image." +msgstr "" + +#: ../../tooling/ister.rst:46 +msgid "Run your own post installation script." +msgstr "" + +#: ../../tooling/ister.rst:49 +msgid "" +"Follow these steps to recreate an upstream image based on the image's " +"JSON configuration file:" +msgstr "" + +#: ../../tooling/ister.rst:52 +msgid "" +"Install the :command:`os-installer` bundle. Refer to `Install a bundle`_ " +"for more details." +msgstr "" + +#: ../../tooling/ister.rst:55 +msgid "Download the `ister.py tool`_ and grant it sudo privileges." +msgstr "" + +#: ../../tooling/ister.rst:57 +msgid "Download the JSON configuration file for the desired image:" +msgstr "" + +#: ../../tooling/ister.rst:59 +msgid "`Configuration files for the current release`_" +msgstr "" + +#: ../../tooling/ister.rst:60 +msgid "`Previous releases`_ (only after March 2017)" +msgstr "" + +#: ../../tooling/ister.rst:62 +msgid "" +"For a previous release, navigate to `Previous releases`_, select the " +"version you want, and find the JSON configuration file under " +":file:`/clear/config/image`. For example: " +"``https://cdn.download.clearlinux.org/releases/15700/clear/config/image/``" +msgstr "" + +#: ../../tooling/ister.rst:67 +msgid "Download the “PostNonChroot” script (if applicable)." +msgstr "" + +#: ../../tooling/ister.rst:69 +msgid "" +"The JSON configuration file for the image may have an accompanying " +"“PostNonChroot” script that is executed at the end of the image creation " +"process. If it does, download the script and make it executable." +msgstr "" + +#: ../../tooling/ister.rst:73 +msgid "Edit the JSON configuration file as needed." +msgstr "" + +#: ../../tooling/ister.rst:75 +msgid "" +"If your configuration file has an accompanying \"PostNonChroot\" script, " +"change the default path of the script to match your path." +msgstr "" + +#: ../../tooling/ister.rst:78 +msgid "Generate the new image with the following command:" +msgstr "" + +#: ../../tooling/ister.rst:85 +msgid "Related topics" +msgstr "" + +#: ../../tooling/ister.rst:87 +msgid ":ref:`mixer`" +msgstr "" + +#: ../../tooling/ister.rst:88 +msgid ":ref:`bulk-provision`" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tooling/mixer.mo b/locale/de/LC_MESSAGES/tooling/mixer.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tooling/mixer.mo differ diff --git a/locale/de/LC_MESSAGES/tooling/mixer.po b/locale/de/LC_MESSAGES/tooling/mixer.po new file mode 100644 index 00000000..94079929 --- /dev/null +++ b/locale/de/LC_MESSAGES/tooling/mixer.po @@ -0,0 +1,1074 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tooling/mixer.rst:4 +msgid "mixer" +msgstr "" + +#: ../../tooling/mixer.rst:6 +msgid "" +"**mixer** is the tool used by the |CL-ATTR| team to generate official " +"update content and releases. The update content generated by mixer is " +"then consumed by swupd on a downstream client. The same mixer tool is " +"available as part of |CL| to create your own customized update content " +"and releases." +msgstr "" + +#: ../../tooling/mixer.rst:16 +msgid "Description" +msgstr "" + +#: ../../tooling/mixer.rst:18 +msgid "mixer uses the following sources as inputs to generate update content:" +msgstr "" + +#: ../../tooling/mixer.rst:20 +msgid "Upstream |CL| bundles with their corresponding RPM packages" +msgstr "" + +#: ../../tooling/mixer.rst:21 +msgid "Locally-defined bundles with their corresponding local RPM packages" +msgstr "" + +#: ../../tooling/mixer.rst:22 +msgid "Locally-defined bundles with upstream RPM packages" +msgstr "" + +#: ../../tooling/mixer.rst:24 +msgid "" +"Using the mixer tool, you select which set of content from these sources " +"will be part of your update. You can select content from each of these " +"sources to make a unique combination of functionality for your custom " +"update content, known as a **mix**." +msgstr "" + +#: ../../tooling/mixer.rst:29 +msgid "" +"The update content that mixer generates consists of various pieces of OS " +"content, update metadata, as well as a complete image. The OS content " +"includes all files in an update, as well as zero- and delta-packs for " +"improved update performance. The update metadata, stored as manifests, " +"describes all of the bundle information for the update. Update content " +"produced by mixer is then published to a web server and consumed by " +"clients via swupd. Refer to :ref:`swupd ` for additional " +"information regarding updates and update content." +msgstr "" + +#: ../../tooling/mixer.rst:39 +msgid "How it works" +msgstr "" + +#: ../../tooling/mixer.rst:41 +msgid "Learn the mixer tool set up and workflow." +msgstr "" + +#: ../../tooling/mixer.rst:48 +msgid "Prerequisites" +msgstr "" + +#: ../../tooling/mixer.rst:50 +msgid ":command:`mixer` bundle" +msgstr "" + +#: ../../tooling/mixer.rst:52 +msgid "" +"Add the mixer tool with the :command:`mixer` bundle. Refer to `Install a " +"bundle`_ for more details." +msgstr "" + +#: ../../tooling/mixer.rst:55 +msgid "Docker\\* container" +msgstr "" + +#: ../../tooling/mixer.rst:57 +msgid "" +"mixer by default runs all build commands in a Docker container to ensure " +"the correct tool versions are used. This also allows custom mixes to " +"automatically perform downstream format bumps when the upstream releases " +"a format bump. See `Format version`_ for additional information regarding" +" format bumps." +msgstr "" + +#: ../../tooling/mixer.rst:63 +msgid "Refer to `Configure and enable Docker`_ for instruction." +msgstr "" + +#: ../../tooling/mixer.rst:65 +msgid "Docker proxy (optional)" +msgstr "" + +#: ../../tooling/mixer.rst:67 +msgid "" +"If you use a proxy server, you must set your proxy environment variables " +"and create a proxy configuration file for the Docker daemon and " +"container." +msgstr "" + +#: ../../tooling/mixer.rst:70 +msgid "" +"Consult your IT department for the correct values if you are behind a " +"corporate proxy." +msgstr "" + +#: ../../tooling/mixer.rst:73 +msgid "Refer to `Configure Docker proxy info`_ for instruction." +msgstr "" + +#: ../../tooling/mixer.rst:75 +msgid "Location to host the update content and images" +msgstr "" + +#: ../../tooling/mixer.rst:77 +msgid "" +"In order for swupd to make use of your mix, the update content for your " +"mix must be hosted on a web server. Your mix will be configured with an " +"update location URL, which swupd will use to pull down updates." +msgstr "" + +#: ../../tooling/mixer.rst:81 +msgid "" +"Refer to `Set up a nginx web server for mixer`_ for an simple example of " +"setting up an update location." +msgstr "" + +#: ../../tooling/mixer.rst:85 +msgid "Mix setup" +msgstr "" + +#: ../../tooling/mixer.rst:87 +msgid "" +"Follow these steps to create and initialize the mixer workspace. Complete" +" the setup before you create a mix." +msgstr "" + +#: ../../tooling/mixer.rst:90 +msgid "Create workspace." +msgstr "" + +#: ../../tooling/mixer.rst:92 +msgid "" +"The mixer tool uses a simple workspace to contain all input and output in" +" a basic directory structure. The workspace is simply an empty folder " +"from which you execute the mixer commands. Each mix uses its own separate" +" workspace." +msgstr "" + +#: ../../tooling/mixer.rst:97 +msgid "Initialize the workspace and mix." +msgstr "" + +#: ../../tooling/mixer.rst:99 +msgid "" +"Before you create a mix, you must explicitly initialize the mixer " +"workspace. During initialization, the mixer workspace is configured and " +"the base for your mix is defined. By default, your mix is based on the " +"latest upstream version and starts with the minimum set of bundles. Your " +"first custom mix version number starts at 10. Alternatively, you can " +"select other versions or bundle sets from which to start." +msgstr "" + +#: ../../tooling/mixer.rst:106 +msgid "" +"Initialization creates the directory structure within the workspace and " +"adds the :file:`builder.conf` file, which is used to configure the mixer " +"tool." +msgstr "" + +#: ../../tooling/mixer.rst:109 +msgid "" +"View the `mixer.init man page`_ for more information on mixer " +"initialization." +msgstr "" + +#: ../../tooling/mixer.rst:112 +msgid "View the list of `suitable versions`_ from which to mix." +msgstr "" + +#: ../../tooling/mixer.rst:114 +msgid "Edit builder.conf." +msgstr "" + +#: ../../tooling/mixer.rst:116 +msgid "" +":file:`builder.conf` tells the mixer tool how to configure the mix. For " +"example, it allows you to configure where mixer output is located and " +"where swupd update content will be located." +msgstr "" + +#: ../../tooling/mixer.rst:120 +msgid "" +"At minimum, set the URL of your update server so your custom OS knows " +"where to get update content." +msgstr "" + +#: ../../tooling/mixer.rst:123 +msgid "Refer to the `builder.conf`_ section for more information." +msgstr "" + +#: ../../tooling/mixer.rst:126 +msgid "Create a mix" +msgstr "" + +#: ../../tooling/mixer.rst:128 +msgid "A mix is created with the following steps:" +msgstr "" + +#: ../../tooling/mixer.rst:130 +msgid "Add custom RPMs and set up local repo (optional)." +msgstr "" + +#: ../../tooling/mixer.rst:132 +msgid "" +"If you are adding custom RPMs to your mix, you must add the RPMs to your " +"mix workspace and set up a corresponding local repository." +msgstr "" + +#: ../../tooling/mixer.rst:135 +msgid "" +"Go to the :ref:`autospec` guide to learn to build RPMs from " +"scratch. If the RPMs are not built on |CL|, make sure your configuration " +"and toolchain builds them correctly for |CL|. Otherwise there is no " +"guarantee they will be compatible." +msgstr "" + +#: ../../tooling/mixer.rst:140 +msgid "" +"Refer to the :ref:`autospec` guide for more information on using autospec" +" to build RPMs." +msgstr "" + +#: ../../tooling/mixer.rst:143 +msgid "Update and build bundles." +msgstr "" + +#: ../../tooling/mixer.rst:145 +msgid "" +"Add, edit, or remove bundles that will be part of your content and build " +"them. mixer automatically updates the :file:`mixbundles` file when you " +"update the bundles in your mix." +msgstr "" + +#: ../../tooling/mixer.rst:149 +msgid "" +"View the `mixer.bundle man page`_ for more information on configuring " +"bundles in a mix." +msgstr "" + +#: ../../tooling/mixer.rst:152 +msgid "View the `mixer.build man page`_ for more information on building bundles." +msgstr "" + +#: ../../tooling/mixer.rst:154 +msgid "" +"View the `Bundles`_ section for more information on how mixer manages " +"bundles." +msgstr "" + +#: ../../tooling/mixer.rst:157 +msgid "Create the update content." +msgstr "" + +#: ../../tooling/mixer.rst:159 +msgid "" +"mixer creates update content with this step. Zero-packs are created " +"automatically, and delta-packs can be optionally created at the same time" +" (for all builds after version 0)." +msgstr "" + +#: ../../tooling/mixer.rst:163 +msgid "" +"A zero-pack is the full set of content needed to go from mix version 0 " +"(nothing) to the mix version for which you just built content." +msgstr "" + +#: ../../tooling/mixer.rst:166 +msgid "" +"A delta-pack provides the content *delta* between a `PAST_VERSION` to a " +"`MIX_VERSION` that allows the transition from one mix version to another." +msgstr "" + +#: ../../tooling/mixer.rst:169 +msgid "View :ref:`swupd-guide` for more information on update content." +msgstr "" + +#: ../../tooling/mixer.rst:171 +msgid "Create image." +msgstr "" + +#: ../../tooling/mixer.rst:173 +msgid "" +"mixer creates a bootable image from your updated content using the " +":ref:`ister` tool. In this step you can specify which bundles you want " +"*preinstalled* in the image. Users can later install other bundles " +"available in your mix." +msgstr "" + +#: ../../tooling/mixer.rst:178 +msgid "Make update available." +msgstr "" + +#: ../../tooling/mixer.rst:180 +msgid "Deploy update content and images to your update server." +msgstr "" + +#: ../../tooling/mixer.rst:182 +msgid "" +"View the `Example 3: Deploy updates to target`_ for a simple deployment " +"scenario." +msgstr "" + +#: ../../tooling/mixer.rst:186 +msgid "Maintain or modify mix" +msgstr "" + +#: ../../tooling/mixer.rst:188 +msgid "" +"Update or modify your content to a new version by following the steps to " +"create a mix. Increment the mix version number for the next mix." +msgstr "" + +#: ../../tooling/mixer.rst:192 +msgid "Examples" +msgstr "" + +#: ../../tooling/mixer.rst:194 +msgid "" +"The following examples are designed to work together and in order. The " +"examples use:" +msgstr "" + +#: ../../tooling/mixer.rst:197 +msgid "A stock installation of |CL|." +msgstr "" + +#: ../../tooling/mixer.rst:198 +msgid "A web server that comes with |CL| to host the content updates." +msgstr "" + +#: ../../tooling/mixer.rst:199 +msgid "" +"A simple VM that updates against the locally produced content created in " +"Example 2." +msgstr "" + +#: ../../tooling/mixer.rst:202 +msgid "Complete all `Prerequisites`_ before using these examples." +msgstr "" + +#: ../../tooling/mixer.rst:205 +msgid "Example 1: Mix set up" +msgstr "" + +#: ../../tooling/mixer.rst:207 +msgid "" +"This example shows the basic steps for the first-time setup of mixer for " +"a new mix." +msgstr "" + +#: ../../tooling/mixer.rst:210 +msgid "Create an empty directory to use as a workspace for mixer:" +msgstr "" + +#: ../../tooling/mixer.rst:216 +msgid "" +"In your mixer workspace, generate an initial mix based on the latest " +"upstream |CL| version, with minimum bundles. In the initialization " +"output, be aware that your initial mix version is set to 10 and that the " +"minimum bundles have been added." +msgstr "" + +#: ../../tooling/mixer.rst:226 +msgid "" +"Edit :file:`builder.conf` to set the value of CONTENTURL and VERSIONURL " +"to the IP address of the nginx\\* server you set up in the prerequisite " +"`Set up a nginx web server for mixer`_. For example:" +msgstr "" + +#: ../../tooling/mixer.rst:238 +msgid "Example 2: Create a simple mix" +msgstr "" + +#: ../../tooling/mixer.rst:240 +msgid "" +"This example shows how to create a simple custom mix using upstream " +"content. We'll create an image for a QEMU virtual machine that we can use" +" later to test our mix." +msgstr "" + +#: ../../tooling/mixer.rst:244 +msgid "" +"We can use the default bundles that were added during initialization, but" +" these include the :command:`native-kernel` bundle that is intended to be" +" used on a bare metal system instead of a VM. So we will modify the " +"default bundle set to get a smaller kernel image, which will also be " +"faster to load." +msgstr "" + +#: ../../tooling/mixer.rst:249 +msgid "Update bundles in mix:" +msgstr "" + +#: ../../tooling/mixer.rst:256 +msgid "Build bundles:" +msgstr "" + +#: ../../tooling/mixer.rst:262 +msgid "" +"Look in ~/mixer/update/image//full for the full chroot after" +" the :command:`build` command completes." +msgstr "" + +#: ../../tooling/mixer.rst:265 +msgid "" +"Build update content. Browse to your \\http://localhost site and you'll " +"see the web page is now up, but with no update content. Build the update " +"content:" +msgstr "" + +#: ../../tooling/mixer.rst:272 +msgid "" +"Refresh your \\http://localhost site and now you can see the update " +"content for mix version 10." +msgstr "" + +#: ../../tooling/mixer.rst:275 ../../tooling/mixer.rst:339 +msgid "" +"Look in ~/mixer/update/www/ to see the update content in " +"your workspace." +msgstr "" + +#: ../../tooling/mixer.rst:278 +msgid "" +"Configure image. Edit the ister configuration file for your image to " +"include all of the bundles you want preinstalled in the image. If this is" +" the first time creating an image, first get a copy of the :file" +":`release-image-config.json` template file:" +msgstr "" + +#: ../../tooling/mixer.rst:287 +msgid "" +"For this example, edit :file:`release-image-config.json` so that the root" +" partition size is \"5G\" and replace the \"kernel-native\" bundle with " +"\"kernel-kvm\"." +msgstr "" + +#: ../../tooling/mixer.rst:307 +msgid "Build the image." +msgstr "" + +#: ../../tooling/mixer.rst:313 +msgid "" +"The output from this step will be :file:`release.img`, which is a live " +"image." +msgstr "" + +#: ../../tooling/mixer.rst:315 +msgid "" +"Make the next mix. Create a new version of your mix, for the live image " +"to update to. Increment your mix version by 10:" +msgstr "" + +#: ../../tooling/mixer.rst:322 +msgid "Repeat steps 1-3 to add the upstream :command:`curl` bundle to the mix:" +msgstr "" + +#: ../../tooling/mixer.rst:330 +msgid "Build optional delta-packs, which helps reduce client update time:" +msgstr "" + +#: ../../tooling/mixer.rst:336 +msgid "" +"Refresh your \\http://localhost site to see the update content for mix " +"version 20." +msgstr "" + +#: ../../tooling/mixer.rst:343 +msgid "Example 3: Deploy updates to target" +msgstr "" + +#: ../../tooling/mixer.rst:345 +msgid "" +"The image created in Example 2 is directly bootable in QEMU. In this " +"example, we'll boot the image from Example 2 to verify it, and update the" +" image from mix version 10 (from which the image was built), to mix " +"version 20." +msgstr "" + +#: ../../tooling/mixer.rst:349 +msgid "Set up the QEMU environment." +msgstr "" + +#: ../../tooling/mixer.rst:351 +msgid "Install the :command:`kvm-host` bundle to your |CL|:" +msgstr "" + +#: ../../tooling/mixer.rst:357 +msgid "" +"Get the virtual EFI firmware, download the image launch script, and make " +"it executable:" +msgstr "" + +#: ../../tooling/mixer.rst:366 +msgid "Start your VM image (created in Example 2):" +msgstr "" + +#: ../../tooling/mixer.rst:372 +msgid "Log in as root and set a password" +msgstr "" + +#: ../../tooling/mixer.rst:374 +msgid "Try out your mix." +msgstr "" + +#: ../../tooling/mixer.rst:376 +msgid "Take a look at the default bundles installed in your mix:" +msgstr "" + +#: ../../tooling/mixer.rst:386 +msgid "" +"You cannot see the curl bundle that you added in Example 2 because your " +"mix is still on version 10." +msgstr "" + +#: ../../tooling/mixer.rst:389 +msgid "" +"Check for updates. You should see that version 20 is available. Use swupd" +" to update your mix:" +msgstr "" + +#: ../../tooling/mixer.rst:398 +msgid "" +"Now your mix should be at version 20 and curl is now available. Try using" +" curl. This will fail because curl is not yet installed:" +msgstr "" + +#: ../../tooling/mixer.rst:406 +msgid "" +"Add the new bundle from your update server to your VM. Retry curl. It " +"works!" +msgstr "" + +#: ../../tooling/mixer.rst:413 +msgid "Shutdown your VM:" +msgstr "" + +#: ../../tooling/mixer.rst:424 +msgid "References" +msgstr "" + +#: ../../tooling/mixer.rst:426 +msgid "" +"Reference the `mixer man page`_ for details regarding mixer commands and " +"options." +msgstr "" + +#: ../../tooling/mixer.rst:435 +msgid "builder.conf" +msgstr "" + +#: ../../tooling/mixer.rst:437 +msgid "" +"mixer initialization creates a :file:`builder.conf` that stores the basic" +" configuration for the mixer tool. The items of primary interest are " +"CONTENTURL and VERSIONURL, which will be used by systems updating against" +" your custom content." +msgstr "" + +#: ../../tooling/mixer.rst:470 +msgid "" +"Additional explanation of variables in :file:`builder.conf` is provided " +"in Table 1." +msgstr "" + +#: ../../tooling/mixer.rst:474 +msgid "**Variable**" +msgstr "" + +#: ../../tooling/mixer.rst:474 +msgid "**Explanation**" +msgstr "" + +#: ../../tooling/mixer.rst:476 +msgid "`CERT`" +msgstr "" + +#: ../../tooling/mixer.rst:476 +msgid "" +"Sets the path where mixer stores the certificate file used to sign " +"content for verification. mixer automatically generates the certificate " +"if you do not provide the path to an existing one, and signs the " +":file:`Manifest.MoM` file to provide security for the updated content you" +" create." +msgstr "" + +#: ../../tooling/mixer.rst:483 +msgid "" +"chroot-builder uses the certificate file to sign the root " +":file:`Manifest.MoM` file to provide security for content verification." +msgstr "" + +#: ../../tooling/mixer.rst:487 +msgid "" +"swupd uses this certificate to verify the :file:`Manifest.MoM` file's " +"signature." +msgstr "" + +#: ../../tooling/mixer.rst:490 +msgid "" +"For now, we strongly recommend that you do not modify this variable, as " +"swupd expects a certificate with a very specific configuration to sign " +"and verify properly." +msgstr "" + +#: ../../tooling/mixer.rst:495 +msgid "`CONTENTURL` and `VERSIONURL`" +msgstr "" + +#: ../../tooling/mixer.rst:495 +msgid "" +"Set these variables to the IP address of the web server hosting the " +"update content." +msgstr "" + +#: ../../tooling/mixer.rst:498 +msgid "" +"VERSIONURL is the IP address where the swupd client looks to determine if" +" a new version is available." +msgstr "" + +#: ../../tooling/mixer.rst:501 +msgid "CONTENTURL is the location from which swupd pulls content updates." +msgstr "" + +#: ../../tooling/mixer.rst:504 +msgid "" +"If the web server is on the same machine as the SERVER_STATE_DIR " +"directory, you can create a symlink to the directory in your web server's" +" document root to easily host the content." +msgstr "" + +#: ../../tooling/mixer.rst:509 +msgid "These URLs are embedded in the images created by mixer." +msgstr "" + +#: ../../tooling/mixer.rst:511 +msgid "`DOCKER_IMAGE_PATH`" +msgstr "" + +#: ../../tooling/mixer.rst:511 +msgid "" +"Sets the base name of the docker image that mixer pulls down to run " +"builds in the proper container." +msgstr "" + +#: ../../tooling/mixer.rst:514 +msgid "`LOCAL_BUNDLE_DIR`" +msgstr "" + +#: ../../tooling/mixer.rst:514 +msgid "" +"Sets the path where mixer stores the local bundle definition files. The " +"bundle definition files include any new, original bundles you create, " +"along with any edited versions of upstream bundles." +msgstr "" + +#: ../../tooling/mixer.rst:519 +msgid "`SERVER_STATE_DIR`" +msgstr "" + +#: ../../tooling/mixer.rst:519 +msgid "" +"Sets the path to which mixer outputs content. By default, mixer " +"automatically sets the path." +msgstr "" + +#: ../../tooling/mixer.rst:522 +msgid "`VERSIONS_PATH`" +msgstr "" + +#: ../../tooling/mixer.rst:522 +msgid "" +"Sets the path for the mix version and upstream version's two state files:" +" :file:`mixversion` and :file:`upstreamversion`. mixer creates both files" +" for you when you set up the workspace." +msgstr "" + +#: ../../tooling/mixer.rst:527 +msgid "`YUM_CONF`" +msgstr "" + +#: ../../tooling/mixer.rst:527 +msgid "" +"Sets the path where mixer automatically generates the :file:`.yum-" +"mix.conf` file." +msgstr "" + +#: ../../tooling/mixer.rst:530 +msgid "" +"The yum configuration file points the chroot-builder to where the RPMs " +"are stored." +msgstr "" + +#: ../../tooling/mixer.rst:533 +msgid "**Table 1**: *Variables in builder.conf*" +msgstr "" + +#: ../../tooling/mixer.rst:537 +msgid "Format version" +msgstr "" + +#: ../../tooling/mixer.rst:539 +msgid "" +"Compatible versions of an OS are tracked with an OS *compatibility " +"epoch*. Versions of an OS within an epoch are fully compatible and can " +"update to any other version within that epoch. The compatibility epoch is" +" set as the `Format` variable in the :file:`mixer.state` file. Variables " +"in the :file:`mixer.state` are used by mixer between executions and " +"should not be manually changed." +msgstr "" + +#: ../../tooling/mixer.rst:545 +msgid "" +"If `Format` increments to a new epoch (a \"format bump\"), the OS has " +"changed in such a way that updating from build M in format X to build N " +"in format Y will not work. Generally, this scenario occurs when the " +"software updater or the software has a change such that it is no longer " +"compatible with the previous update scheme, or when a package is removed " +"from the update stream and the update must ensure the files associated " +"with that package are removed from the system." +msgstr "" + +#: ../../tooling/mixer.rst:552 +msgid "" +"Using a format increment, we make sure pre- and co-requisite changes flow" +" out with proper ordering. The updated client will only update to the " +"latest release in its respective format version, unless overridden by " +"command line flags. In this way, we can guarantee that all clients update" +" to the final version in their given format." +msgstr "" + +#: ../../tooling/mixer.rst:558 +msgid "" +"The given format *must* contain all the changes needed to understand the " +"content built in the next format. Only after reaching the final release " +"in the old format can a client continue to update to releases in the new " +"format." +msgstr "" + +#: ../../tooling/mixer.rst:562 +msgid "" +"The format version is incremented only when a compatibility breakage is " +"introduced. Normal updates, such as updating a software package, do not " +"require a format increment." +msgstr "" + +#: ../../tooling/mixer.rst:569 +msgid "Bundles" +msgstr "" + +#: ../../tooling/mixer.rst:571 +msgid "" +"mixer stores information about the bundles included in a mix in a flat " +"file called :file:`mixbundles`, which is located in the path set by the " +"VERSIONS_PATH variable in :file:`builder.conf`. :file:`mixbundles` is " +"automatically created when the mix is initiated. mixer will refresh the " +"file each time you change the bundles in the mix." +msgstr "" + +#: ../../tooling/mixer.rst:577 +msgid "" +"Bundles can include other bundles. Nested bundles can themselves include " +"other bundles. If you see an unexpected bundle in your mix, it is likely " +"a nested bundle in one of the bundles you explicitly added." +msgstr "" + +#: ../../tooling/mixer.rst:581 +msgid "" +"A bundle will fill into one of two categories: upstream or local. " +"Upstream bundles are those provided by |CL|. Local bundles are either " +"modified upstream bundles or new local bundles." +msgstr "" + +#: ../../tooling/mixer.rst:586 +msgid "Upstream bundles" +msgstr "" + +#: ../../tooling/mixer.rst:588 +msgid "" +"mixer automatically downloads and caches upstream bundle definition " +"files. These definition files are stored in the upstream-bundles " +"directory in the workspace. Do not modify the files in this directory. " +"This directory is simply a mirror for mixer to use. mixer will " +"automatically delete the contents of this directory before repopulating " +"it on-the-fly if a new version must be downloaded." +msgstr "" + +#: ../../tooling/mixer.rst:594 +msgid "" +"The mixer tool automatically caches the bundles for the |CL| version " +"configured in the :file:`upstreamversion` file. mixer also cleans up old " +"versions once they are no longer needed." +msgstr "" + +#: ../../tooling/mixer.rst:599 +msgid "Local bundles" +msgstr "" + +#: ../../tooling/mixer.rst:601 +msgid "" +"Local bundles are bundles that you create, or are edited versions of " +"upstream bundles. Local bundle definition files are stored in the local-" +"bundles directory in the workspace. The LOCAL_BUNDLE_DIR variable sets " +"the path of this directory in the :file:`builder.conf` file." +msgstr "" + +#: ../../tooling/mixer.rst:606 +msgid "" +"*mixer always checks for local bundles first and the upstream bundles " +"second.* So bundles in the local-bundles directory will always take " +"precedence over any upstream bundles that have the same name. This " +"precedence enables you to copy upstream bundles locally, and edit into a " +"local variation." +msgstr "" + +#: ../../tooling/mixer.rst:612 +msgid "Bundle configuration" +msgstr "" + +#: ../../tooling/mixer.rst:614 +msgid "" +"mixer provides commands to configure the bundles for a mix, such as to " +"add a bundle to a mix, to create a new bundle for a mix, or to remove a " +"bundle from a mix. View the `mixer.bundle man page`_ for a full list of " +"commands and more information on configuring bundles in a mix." +msgstr "" + +#: ../../tooling/mixer.rst:619 +msgid "" +"Editing an existing local bundle is as simple as opening the bundle " +"definition file in your favorite editor, making the desired edits, and " +"saving your changes." +msgstr "" + +#: ../../tooling/mixer.rst:624 +msgid "" +"Removing bundles from a mix: By default, removing a bundle will only " +"remove the bundle from the mix. The local bundle definition file will " +"still remain. To completely remove a bundle, including its local bundle " +"definition file, use the :command:`--local` flag." +msgstr "" + +#: ../../tooling/mixer.rst:629 +msgid "" +"If you remove the bundle definition file for a local, edited version of " +"an upstream bundle in a mix, the mix reverts to reference the original " +"upstream version of the bundle." +msgstr "" + +#: ../../tooling/mixer.rst:636 +msgid "Configure and enable Docker" +msgstr "" + +#: ../../tooling/mixer.rst:638 +msgid "" +"Use these steps to enable Docker for the mixer tool. Make sure to " +"`Configure Docker proxy info`_ first if needed." +msgstr "" + +#: ../../tooling/mixer.rst:641 +msgid "Start the Docker daemon:" +msgstr "" + +#: ../../tooling/mixer.rst:649 +msgid "Add user to the docker group" +msgstr "" + +#: ../../tooling/mixer.rst:656 +msgid "Pull Docker container manually (optional)" +msgstr "" + +#: ../../tooling/mixer.rst:658 +msgid "" +"By default, mixer automatically pulls a Docker container for mixing if " +"one does not already exist. If you need to troubleshoot the mixer " +"container, it may be useful to manually pull a mixer Docker container." +msgstr "" + +#: ../../tooling/mixer.rst:662 +msgid "" +"Versions of the mixer Docker container are available under the tags for " +"the `clearlinux/mixer repo " +"`_ on Docker Hub. Each " +"version of the mixer Docker container is named after the associated |CL| " +"upstream format version. Refer to `Format version`_ for additional " +"information on upstream format versions." +msgstr "" + +#: ../../tooling/mixer.rst:668 +msgid "Use the following steps to manually pull a mixer Docker container:" +msgstr "" + +#: ../../tooling/mixer.rst:670 +msgid "" +"Find the version of the container you need by viewing the tags for the " +"`clearlinux/mixer repo " +"`_ on Docker Hub." +msgstr "" + +#: ../../tooling/mixer.rst:674 +msgid "Pull the latest container version:" +msgstr "" + +#: ../../tooling/mixer.rst:680 +msgid "View local docker images:" +msgstr "" + +#: ../../tooling/mixer.rst:689 +msgid "Configure Docker proxy info" +msgstr "" + +#: ../../tooling/mixer.rst:691 +msgid "If needed, use these steps to configure the Docker proxy information." +msgstr "" + +#: ../../tooling/mixer.rst:693 +msgid "Create the Docker daemon proxy config directory:" +msgstr "" + +#: ../../tooling/mixer.rst:699 +msgid "" +"Create :file:`/etc/systemd/system/docker.service.d/http-proxy.conf` and " +"add the following using your own proxy values:" +msgstr "" + +#: ../../tooling/mixer.rst:708 +msgid "Reload the Docker daemon:" +msgstr "" + +#: ../../tooling/mixer.rst:714 +msgid "" +"Configure the Docker container proxies, to pass proxy settings to " +"containers:" +msgstr "" + +#: ../../tooling/mixer.rst:717 +msgid "Create a directory for your container config:" +msgstr "" + +#: ../../tooling/mixer.rst:723 +msgid "" +"Create the config file :file:`~/.docker/config.json` and add the " +"following entries, using your own proxy values:" +msgstr "" + +#: ../../tooling/mixer.rst:739 +msgid "Set ownership and permission on the docker config directory:" +msgstr "" + +#: ../../tooling/mixer.rst:746 +msgid "" +"Configure proxies to allow mixer to access upstream content from behind a" +" firewall." +msgstr "" + +#: ../../tooling/mixer.rst:749 +msgid "" +"Open your :file:`$HOME/.bashrc` file and add proxy and port values for " +"the following:" +msgstr "" + +#: ../../tooling/mixer.rst:760 +msgid "Log out and log back in for the proxies to take effect." +msgstr "" + +#: ../../tooling/mixer.rst:765 +msgid "Set up a nginx web server for mixer" +msgstr "" + +#: ../../tooling/mixer.rst:767 +msgid "" +"A web server is needed to host your update content. In this example, we " +"use the nginx web server, which comes with |CL|." +msgstr "" + +#: ../../tooling/mixer.rst:770 +msgid "Set up a nginx web server for mixer with the following steps:" +msgstr "" + +#: ../../tooling/mixer.rst:772 +msgid "Install the :command:`nginx` bundle:" +msgstr "" + +#: ../../tooling/mixer.rst:778 +msgid "Make the directory where mixer updates will reside:" +msgstr "" + +#: ../../tooling/mixer.rst:784 +msgid "" +"Create a symbolic link between your workspace updates and the updates on " +"the local nginx web server. In this example, `$HOME/mixer` is the " +"workspace for the mix." +msgstr "" + +#: ../../tooling/mixer.rst:792 +msgid "Set up ``nginx`` configuration:" +msgstr "" + +#: ../../tooling/mixer.rst:798 +msgid "Copy the default example configuration file:" +msgstr "" + +#: ../../tooling/mixer.rst:804 +msgid "" +"Configure the mixer update server. Create and add the following server " +"configuration content to :file:`/etc/nginx/conf.d/mixer.conf` (sudo " +"required):" +msgstr "" + +#: ../../tooling/mixer.rst:817 +msgid "Restart the daemon, enable nginx on boot, and start the service." +msgstr "" + +#: ../../tooling/mixer.rst:827 +msgid "" +"Verify the web server is running at \\http://localhost. At this point you" +" should no longer see a \"404 Not Found\" message." +msgstr "" + +#: ../../tooling/mixer.rst:831 +msgid "Related topics" +msgstr "" + +#: ../../tooling/mixer.rst:833 +msgid ":ref:`About mixer `" +msgstr "" + +#: ../../tooling/mixer.rst:834 +msgid ":ref:`autospec-about`" +msgstr "" + +#: ../../tooling/mixer.rst:835 +msgid ":ref:`bundles-about`" +msgstr "" + +#: ../../tooling/mixer.rst:836 +msgid ":ref:`swupd-about`" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tooling/swupd-guide.mo b/locale/de/LC_MESSAGES/tooling/swupd-guide.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tooling/swupd-guide.mo differ diff --git a/locale/de/LC_MESSAGES/tooling/swupd-guide.po b/locale/de/LC_MESSAGES/tooling/swupd-guide.po new file mode 100644 index 00000000..61a3c847 --- /dev/null +++ b/locale/de/LC_MESSAGES/tooling/swupd-guide.po @@ -0,0 +1,446 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tooling/swupd-guide.rst:4 +msgid "swupd" +msgstr "" + +#: ../../tooling/swupd-guide.rst:6 +msgid "" +":command:`swupd` links a |CL-ATTR| installation with upstream updates and" +" software." +msgstr "" + +#: ../../tooling/swupd-guide.rst:14 +msgid "Description" +msgstr "" + +#: ../../tooling/swupd-guide.rst:16 +msgid ":command:`swupd` has two main functions:" +msgstr "" + +#: ../../tooling/swupd-guide.rst:18 +msgid "" +"Manage software and replace APT or YUM, by installing bundles rather than" +" packages." +msgstr "" + +#: ../../tooling/swupd-guide.rst:20 +msgid "Check for system updates and install them." +msgstr "" + +#: ../../tooling/swupd-guide.rst:22 +msgid "" +":command:`swupd` manages overlapping dependencies behind the scenes, " +"ensuring that all software is compatible across the system. It can be " +"used to verify the OS, clean cached files, and fix issues." +msgstr "" + +#: ../../tooling/swupd-guide.rst:26 +msgid "" +":ref:`Bundles ` contain everything needed to deliver a software " +"capability. They are the smallest granularity component that is managed " +"by |CL|. A bundle comes with all of its dependencies rather than " +"downloading a cascade of package dependencies when installing a piece of " +"software." +msgstr "" + +#: ../../tooling/swupd-guide.rst:33 +msgid "Versioning" +msgstr "" + +#: ../../tooling/swupd-guide.rst:35 +msgid "" +"Using package managers to monitor software version compatibility or " +"compare multiple systems on many Linux distributions can be cumbersome." +msgstr "" + +#: ../../tooling/swupd-guide.rst:38 +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 "" + +#: ../../tooling/swupd-guide.rst:45 +msgid "" +"A number that represents the **current** release of the OS describes the " +"versions of all the software on the OS. Each build is composed of a " +"specific set of bundles made from a particular version of packages. On a " +"daily basis, this matters to system administrators who need to determine " +"which of their systems do not have the latest security fixes, or which " +"combinations of software have been tested. Every release of the same " +"number is guaranteed to contain the same versions of software, so there's" +" no ambiguity between two systems running the same version of |CL|." +msgstr "" + +#: ../../tooling/swupd-guide.rst:55 +msgid "Updating" +msgstr "" + +#: ../../tooling/swupd-guide.rst:57 +msgid "" +"|CL| enforces regular updating of the OS by default and automatically " +"checks for updates against a version server. The content server provides " +"the file and metadata content for all versions and can be the same as the" +" version server. The content url server provides metadata in the form of " +"*manifests*, which list and describe file contents, symlinks, and " +"directories. Additionally, the actual content is provided to clients in " +"the form of archive files." +msgstr "" + +#: ../../tooling/swupd-guide.rst:65 +msgid "" +"Software updates with |CL| are also efficient. Unlike package-based " +"distributions, :command:`swupd` only updates files that have changed, " +"rather than entire packages. For example, it is quite common for an OS " +"security patch to be as small as 15 KB. Using binary deltas, |CL| is able" +" to apply only what is needed." +msgstr "" + +#: ../../tooling/swupd-guide.rst:71 +msgid "" +"For details on how to generate update content for |CL|, see the " +":ref:`mixer ` tool." +msgstr "" + +#: ../../tooling/swupd-guide.rst:75 +msgid "How it works" +msgstr "" + +#: ../../tooling/swupd-guide.rst:78 +msgid "Prerequisites" +msgstr "" + +#: ../../tooling/swupd-guide.rst:80 +msgid "The device is on a well-connected network." +msgstr "" + +#: ../../tooling/swupd-guide.rst:81 +msgid "" +"The device is able to connect to an update server. The default server is:" +" http://update.clearlinux.org" +msgstr "" + +#: ../../tooling/swupd-guide.rst:85 +msgid "Updates" +msgstr "" + +#: ../../tooling/swupd-guide.rst:87 +msgid "" +"|CL| updates are automatic by default, but can be set to occur only on " +"demand. :command:`swupd` makes sure that regular updates are simple and " +"secure. It can also check the validity of currently installed files and " +"software, and can correct any problems." +msgstr "" + +#: ../../tooling/swupd-guide.rst:93 +msgid "Manifests" +msgstr "" + +#: ../../tooling/swupd-guide.rst:95 +msgid "" +"The |CL| software update content consists of data and metadata. The data " +"is the files that end up in the OS. The metadata contains relevant " +"information to properly provision the data to the OS file system, as well" +" as update the system and add or remove additional content to the OS." +msgstr "" + +#: ../../tooling/swupd-guide.rst:100 +msgid "" +"The manifests are mostly long lists of hashes that describe content. Each" +" bundle gets its own manifest file. There is a master manifest file that " +"describes all manifests to tie it all together." +msgstr "" + +#: ../../tooling/swupd-guide.rst:105 +msgid "Fullfiles, packs, and delta packs" +msgstr "" + +#: ../../tooling/swupd-guide.rst:107 +msgid "" +"To speed up updates and optimize content delivery, update data " +"provisioned to a system is obtained by one of the following methods:" +msgstr "" + +#: ../../tooling/swupd-guide.rst:110 +msgid "" +"*Fullfiles* are always generated for every file in every release. This " +"allows any |CL| to obtain the exact copy of the content for each version " +"directly. This is used if the OS verification needs to replace a single " +"file, for instance." +msgstr "" + +#: ../../tooling/swupd-guide.rst:115 +msgid "" +"*Packs* are available for some releases. They combine many files to speed" +" up the creation of installation media and large updates." +msgstr "" + +#: ../../tooling/swupd-guide.rst:118 +msgid "" +"*Delta packs* are an optimized version of packs that only contain updates" +" (binary diffs). They cannot be used without having the original file " +"content." +msgstr "" + +#: ../../tooling/swupd-guide.rst:122 +msgid "Bundle search" +msgstr "" + +#: ../../tooling/swupd-guide.rst:124 +msgid "" +":command:`swupd` searches download manifest data for bundles that match " +"the term. Enter only one term, or hyphenated term, per search. Use the " +"command :command:`man swupd` to learn more." +msgstr "" + +#: ../../tooling/swupd-guide.rst:128 +msgid "" +"Only the base bundle is returned. Bundles can contain other bundles via " +"includes. For more details, see `Bundle Definition Files`_ and its " +"subdirectory bundles." +msgstr "" + +#: ../../tooling/swupd-guide.rst:132 +msgid "" +"Bundles that are already installed are marked **(installed)** in search " +"results." +msgstr "" + +#: ../../tooling/swupd-guide.rst:135 +msgid "Optionally, you can review our `bundles`_ on GitHub\\*." +msgstr "" + +#: ../../tooling/swupd-guide.rst:138 +msgid "Examples" +msgstr "" + +#: ../../tooling/swupd-guide.rst:141 +msgid "Example 1: Disable and enable automatic updates" +msgstr "" + +#: ../../tooling/swupd-guide.rst:143 +msgid "" +"|CL| updates are automatic by default, but can be set to occur only on " +"demand." +msgstr "" + +#: ../../tooling/swupd-guide.rst:146 +msgid "Verify your current auto-update setting." +msgstr "" + +#: ../../tooling/swupd-guide.rst:156 +msgid "Disable automatic updates." +msgstr "" + +#: ../../tooling/swupd-guide.rst:170 +msgid "Check manually for updates." +msgstr "" + +#: ../../tooling/swupd-guide.rst:176 +msgid "Install an update after identifying one that you need." +msgstr "" + +#: ../../tooling/swupd-guide.rst:182 +msgid "Re-enable automatic installs." +msgstr "" + +#: ../../tooling/swupd-guide.rst:191 +msgid "Example 2: Find and install Kata Containers\\*" +msgstr "" + +#: ../../tooling/swupd-guide.rst:193 +msgid "" +"Kata Containers is a popular container implementation. Unlike other " +"container implementations, each Kata Container has its own kernel " +"instance and runs on its own :abbr:`VM (Virtual Machine)` for improved " +"security." +msgstr "" + +#: ../../tooling/swupd-guide.rst:198 +msgid "" +"|CL| makes it very easy to install, since you only need to add `one " +"bundle`_ to use `Kata Containers`_: `containers-virt`, despite a number " +"of dependencies. Also, check out our tutorial: :ref:`kata`." +msgstr "" + +#: ../../tooling/swupd-guide.rst:202 +msgid "Find the correct bundle." +msgstr "" + +#: ../../tooling/swupd-guide.rst:204 +msgid "" +"To return all possible matches for the search string, enter " +":command:`swupd search`, followed by 'kata':" +msgstr "" + +#: ../../tooling/swupd-guide.rst:211 +msgid "The output should be similar to:" +msgstr "" + +#: ../../tooling/swupd-guide.rst:229 +msgid "" +"If your search does not produce results with a specific term, shorten the" +" search term. For example, use *kube* instead of *kubernetes*." +msgstr "" + +#: ../../tooling/swupd-guide.rst:232 +msgid "Add the bundle." +msgstr "" + +#: ../../tooling/swupd-guide.rst:240 +msgid "To add multiple bundles, add a space followed by the bundle name." +msgstr "" + +#: ../../tooling/swupd-guide.rst:242 +msgid "The output of a successful installation should be similar to:" +msgstr "" + +#: ../../tooling/swupd-guide.rst:261 +msgid "Example 3: Verify and correct system file mismatch" +msgstr "" + +#: ../../tooling/swupd-guide.rst:263 +msgid "" +":command:`swupd` can determine whether system directories and files have " +"been added to, overwritten, removed, or modified (e.g., permissions)." +msgstr "" + +#: ../../tooling/swupd-guide.rst:270 +msgid "" +"All directories that are watched by :command:`swupd` are verified " +"according to the manifest data. Hash mismatches are flagged as follows:" +msgstr "" + +#: ../../tooling/swupd-guide.rst:287 +msgid "" +"In this case, Python\\* packages that were installed on top of the " +"default install were flagged as mismatched. :command:`swupd` can be " +"directed to ignore or fix issues based on command line options." +msgstr "" + +#: ../../tooling/swupd-guide.rst:291 +msgid "" +":command:`swupd` can correct any issues it detects. Additional directives" +" can be added including a white list of directories to be ignored." +msgstr "" + +#: ../../tooling/swupd-guide.rst:294 +msgid "" +"The following command repairs issues, removes unknown items, and ignores " +"files or directories matching :file:`/usr/lib/python`:" +msgstr "" + +#: ../../tooling/swupd-guide.rst:302 +msgid "Quick reference" +msgstr "" + +#: ../../tooling/swupd-guide.rst:305 +msgid "swupd info" +msgstr "" + +#: ../../tooling/swupd-guide.rst:305 +msgid "Returns the currently installed version and update servers." +msgstr "" + +#: ../../tooling/swupd-guide.rst:309 +msgid "swupd update " +msgstr "" + +#: ../../tooling/swupd-guide.rst:308 +msgid "" +"Updates to a specific version or updates to latest version if no " +"arguments are used." +msgstr "" + +#: ../../tooling/swupd-guide.rst:312 +msgid "swupd bundle-list [--all]" +msgstr "" + +#: ../../tooling/swupd-guide.rst:312 +msgid "Lists installed bundles." +msgstr "" + +#: ../../tooling/swupd-guide.rst:315 +msgid "swupd bundle-add [-b] " +msgstr "" + +#: ../../tooling/swupd-guide.rst:315 +msgid "Finds a bundle that contains your search term." +msgstr "" + +#: ../../tooling/swupd-guide.rst:318 +msgid "swupd bundle-add " +msgstr "" + +#: ../../tooling/swupd-guide.rst:318 +msgid "Adds a bundle." +msgstr "" + +#: ../../tooling/swupd-guide.rst:321 +msgid "swupd bundle-remove " +msgstr "" + +#: ../../tooling/swupd-guide.rst:321 +msgid "Removes a bundle." +msgstr "" + +#: ../../tooling/swupd-guide.rst:324 +msgid "swupd --help" +msgstr "" + +#: ../../tooling/swupd-guide.rst:324 +msgid "Lists additional :command:`swupd` commands." +msgstr "" + +#: ../../tooling/swupd-guide.rst:327 +msgid "man swupd" +msgstr "" + +#: ../../tooling/swupd-guide.rst:327 +msgid "Opens the :command:`swupd` man page." +msgstr "" + +#: ../../tooling/swupd-guide.rst:329 +msgid "" +"Refer to :command:`swupd` `source documentation`_ on GitHub for more " +"details." +msgstr "" + +#: ../../tooling/swupd-guide.rst:332 +msgid "Related topics" +msgstr "" + +#: ../../tooling/swupd-guide.rst:334 +msgid ":ref:`autospec`" +msgstr "" + +#: ../../tooling/swupd-guide.rst:335 +msgid ":ref:`mixer`" +msgstr "" + +#: ../../tooling/swupd-guide.rst:336 +msgid ":ref:`bundles`" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tooling/tooling.mo b/locale/de/LC_MESSAGES/tooling/tooling.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tooling/tooling.mo differ diff --git a/locale/de/LC_MESSAGES/tooling/tooling.po b/locale/de/LC_MESSAGES/tooling/tooling.po new file mode 100644 index 00000000..4f4cac73 --- /dev/null +++ b/locale/de/LC_MESSAGES/tooling/tooling.po @@ -0,0 +1,30 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tooling/tooling.rst:4 +msgid "Tooling" +msgstr "" + +#: ../../tooling/tooling.rst:6 +msgid "" +"Clear Linux is a little different from other distros. Here are some " +"important tools and concepts for managing your install." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/aws-web/aws-web.mo b/locale/de/LC_MESSAGES/tutorials/aws-web/aws-web.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/aws-web/aws-web.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/aws-web/aws-web.po b/locale/de/LC_MESSAGES/tutorials/aws-web/aws-web.po new file mode 100644 index 00000000..a4cc924e --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/aws-web/aws-web.po @@ -0,0 +1,379 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/aws-web/aws-web.rst:4 +msgid "Create and launch |CL-ATTR| from Amazon Web Services" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:6 +msgid "" +"This tutorial walks you through creating and launching a |CL| :abbr:`AMI " +"(Amazon Machine Image)` instance from the :abbr:`AWS (Amazon Web " +"Services)` console and complete the following tasks:" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:10 +msgid "Locate and select the |CL| OS Basic AMI in the AWS Marketplace." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:11 +msgid "" +"Create a new public and private key pair to allow you to connect to your " +"|CL| instance securely." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:13 +msgid "Launch the new |CL| instance and connect to it." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:14 +msgid "Update your instance of |CL| using the :command:`swupd` command." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:15 +msgid "Stop the |CL| instance." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:18 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:20 +msgid "This tutorial assumes the following statements are true:" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:22 +msgid "" +"You are using a linux-based system to access AWS and can run " +":command:`SSH` to access the remote |CL| AWS image." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:24 +msgid "" +"Your browser puts downloaded files in the :file:`$HOME/Downloads` " +"directory." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:26 +msgid "" +"You have already set up an AWS user account and logged into the AWS " +"console." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:30 +msgid "" +"This tutorial uses a |CL| AMI t2.micro instance that is eligible for the " +"AWS free tier. To learn more about AWS and setting up an account, visit " +"the AWS website at http://aws.amazon.com." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:35 +msgid "Locate, select, and launch the |CL| Basic AMI" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:37 +msgid "" +"Start from your main AWS services console menu in your browser and select" +" the :guilabel:`EC2` text as shown in figure 1:" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:44 +msgid "Figure 1: :guilabel:`AWS Console`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:46 +msgid "This selection brings up your :guilabel:`EC2 Dashboard` menu." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:48 +msgid "" +"To create a new |CL| instance from the :guilabel:`EC2 Dashboard` menu, " +"select the :guilabel:`Launch Instance` button as shown in figure 2:" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:55 +msgid "Figure 2: :guilabel:`EC2 Dashboard`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:57 +msgid "" +"This selection takes you to the :guilabel:`Step 1: Choose an Amazon " +"Machine Image (AMI)` menu." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:60 +msgid "" +"To find the :guilabel:`Clear Linux OS Basic` AMI in the :guilabel:`Step " +"1: Choose an Amazon Machine Image (AMI)` menu, do the following:" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:64 +msgid "" +"In the lefthand navigation window, select the :guilabel:`AWS Marketplace`" +" menu item to bring up the search bar to :guilabel:`Search AWS " +"Marketplace Products`." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:68 +msgid "" +"In the search bar, type \"clear linux os\" and hit the :kbd:`Enter` key " +"to search for and locate the :guilabel:`Clear Linux OS Basic` AMI." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:71 +msgid "" +"Select the :guilabel:`Clear Linux OS Basic` AMI by clicking on the " +":guilabel:`Select` button as shown in figure 3:" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:78 +msgid "Figure 3: :guilabel:`Step 1: Choose AMI`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:80 +msgid "" +"A pop-up dialog box appears showing you more information about the " +":guilabel:`Clear Linux OS Basic` AMI along with the pricing details for " +"running |CL| on different platform configurations as shown in figure 4. " +"Select the :guilabel:`Continue` button." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:89 +msgid "Figure 4: :guilabel:`Clear Linux OS Basic`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:91 +msgid "The :guilabel:`Choose Instance Type` menu appears as shown in figure 5." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:97 +msgid "Figure 5: :guilabel:`Choose an Instance Type`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:99 +msgid "" +"Select the :guilabel:`t2.micro` type by clicking the box on the left side" +" of the instance and then select the :guilabel:`Review and Launch` button" +" to move to the :guilabel:`Step 7: Review the Instance Launch` menu." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:105 +msgid "" +"You can configure the instance details, add additional storage, add tags," +" and configure the security group before selecting the :guilabel:`Review " +"and Launch` button if you want to further customize this |CL| instance." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:110 +msgid "" +"The :guilabel:`Step 7: Review the Instance Launch` menu, shown in figure " +"6, allows you to :guilabel:`Cancel` the process, return to the " +":guilabel:`Previous` screen to change the configuration or " +":guilabel:`Launch` the instance defined." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:119 +msgid "Figure 6: :guilabel:`Step 7: Review the Instance Launch`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:121 +msgid "" +"Select the :guilabel:`Launch` button. A dialog box appears, as shown in " +"figure 7, asking you to :guilabel:`Select an existing key pair or create " +"a new pair`." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:129 +msgid "Figure 7: :guilabel:`Select an existing key pair or create a new pair`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:131 +msgid "Select the :guilabel:`Create a new key pair` option." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:133 +msgid "For the :guilabel:`Key pair name` field, enter `AWSClearTestKey`." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:135 +msgid "" +"Select the :guilabel:`Download Key Pair` button to download the " +":file:`AWSClearTestKey.pem` to your browser's defined :file:`Downloads` " +"directory." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:139 +msgid "" +"When the file finishes downloading, select the :guilabel:`Launch " +"Instances` button to proceed to the :guilabel:`Launch Status` menu shown " +"in figure 8." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:147 +msgid "Figure 8: :guilabel:`Launch Status`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:149 +msgid "" +"Once the :guilabel:`Launch Status` page changes to what is shown in " +"figure 9, select the :guilabel:`View Instances` button to view your " +":guilabel:`Instances` dashboard." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:157 +msgid "Figure 9: :guilabel:`View Instance`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:160 +msgid "Connect to your Clear Linux OS Basic instance" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:162 +msgid "" +"Your :guilabel:`Instances` Dashboard is shown in figure 10 with the new " +"|CL| OS basic instance already selected and in the running state. If " +"there are other instances available, they are also listed but not " +"selected." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:170 +msgid "Figure 10: :guilabel:`Instance Dashboard`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:172 +msgid "" +"To connect to your running instance, click the :guilabel:`Connect` button" +" located at the top of your dashboard. AWS brings up the pop-up dialog " +"box shown in figure 11 describing how to connect to your running " +"instance." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:182 +msgid "Figure 11: :guilabel:`Connect to Your Instance`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:184 +msgid "" +"Open a terminal on your system. You should be in your :file:`$HOME` " +"directory." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:187 +msgid "" +"Copy the previously downloaded keyfile from the :file:`Downloads` " +"directory to the current directory." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:194 +msgid "" +"Change the attributes of the :file:`AWSClearTestKey.pem` using the " +":command:`chmod` command as instructed in the dialog box shown in figure " +"11." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:202 +msgid "" +"Copy the text highlighted in the :guilabel:`Example:` section that is " +"shown in :ref:`figure 11`. Paste the copied text into " +"your terminal, change the text before the `@` sign to the username " +"`clear`, and press the :kbd:`Enter` key to execute the command." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:211 +msgid "" +"A message appears on the terminal stating the authenticity of the host " +"can't be established and prompts you with the message:" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:220 +msgid "" +"Type `yes` and hit the :kbd:`Enter` key. Another warning is printed to " +"the terminal and you are now at the command prompt of your new |CL| " +"instance." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:229 +msgid "Update the |CL| instance" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:231 +msgid "" +"Run the :command:`sudo swupd update` command to update the operating " +"system as shown in figure 12:" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:238 +msgid "Figure 12: :guilabel:`sudo swupd update`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:240 +msgid "In this example we updated from version 18940 to 19100." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:243 +msgid "Stop the |CL| instance" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:245 +msgid "" +"When you are finished using your AWS |CL| instance you need to stop it " +"using the :guilabel:`Instances` dashboard to stop accruing charges. " +"Complete the following steps from the :guilabel:`Instances` dashboard to " +"stop your AWS |CL| instance from running." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:250 +msgid "Select the :guilabel:`Actions` button to bring up a pull-down menu." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:252 +msgid "Select the :guilabel:`Instance State` menu item to expand the options." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:254 +msgid "Select :guilabel:`Stop` menu item to shut down the running instance." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:256 +msgid "Figure 13 illustrates these steps." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:262 +msgid "Figure 13: :guilabel:`Stop Instance`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:264 +msgid "" +"A pop-up dialog box appears warning you that any ephemeral storage of " +"your instance will be lost. Select the :guilabel:`Yes, Stop` button to " +"stop your |CL| instance." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:272 +msgid "Figure 14: :guilabel:`Stop Instances`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:274 +msgid "" +"Congratulations! You are up and running with |CL| on AWS. To see what you" +" can do with your |CL| instance, visit our :ref:`tutorials ` " +"section for examples on using your |CL| system." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/azure.mo b/locale/de/LC_MESSAGES/tutorials/azure.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/azure.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/azure.po b/locale/de/LC_MESSAGES/tutorials/azure.po new file mode 100644 index 00000000..75be9084 --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/azure.po @@ -0,0 +1,445 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/azure.rst:4 +msgid "Run |CL-ATTR| using Microsoft Azure CLI 2.0" +msgstr "" + +#: ../../tutorials/azure.rst:6 +msgid "" +"|CL-ATTR| is available for you to use in the Microsoft* Azure* " +"marketplace and is offered with three different images, also known as a " +":abbr:`SKU (Stock Keeping Unit)`." +msgstr "" + +#: ../../tutorials/azure.rst:10 +msgid "" +"|CL| Basic - This SKU consists of a bare-bones system which can be used " +"as a starting point for those wanting to explore and build out a system " +"with additional software bundles of their choosing." +msgstr "" + +#: ../../tutorials/azure.rst:14 +msgid "" +"|CL| Containers - This SKU comes with the containers-basic software " +"bundle already installed." +msgstr "" + +#: ../../tutorials/azure.rst:17 +msgid "" +"|CL| Machine-learning - This SKU comes pre-loaded with popular open " +"source tools for developing machine learning applications." +msgstr "" + +#: ../../tutorials/azure.rst:20 +msgid "" +"You can access these images directly from your MS Azure dashboard through" +" the `Azure portal`_ or by using the MS Azure :abbr:`CLI (Command Line " +"Interface)` 2.0. If you do not already have an account set up with MS " +"Azure, you can sign up for a `MS Azure free account`_ to access the |CL| " +":abbr:`VM(Virtual Machine)` images." +msgstr "" + +#: ../../tutorials/azure.rst:26 +msgid "" +"The Azure CLI offers the ability to create and manage resources in MS " +"Azure from the command line. In this tutorial you learn to:" +msgstr "" + +#: ../../tutorials/azure.rst:29 +msgid "Install the latest MS Azure CLI on your |CL| machine." +msgstr "" + +#: ../../tutorials/azure.rst:31 +msgid "Log into MS Azure using the CLI 2.0 interface." +msgstr "" + +#: ../../tutorials/azure.rst:33 +msgid "Create a MS Azure resource group." +msgstr "" + +#: ../../tutorials/azure.rst:35 +msgid "Locate the |CL| images." +msgstr "" + +#: ../../tutorials/azure.rst:37 +msgid "Create and log into the |CL| virtual machine." +msgstr "" + +#: ../../tutorials/azure.rst:39 +msgid "Stop and deallocate the |CL| VM and resources." +msgstr "" + +#: ../../tutorials/azure.rst:41 +msgid "" +"To use the MS Azure CLI 2.0 on your |CL| system, your system must have " +"the following packages installed:" +msgstr "" + +#: ../../tutorials/azure.rst:44 +msgid "Python 2.7 or later" +msgstr "" + +#: ../../tutorials/azure.rst:46 +msgid "libffi" +msgstr "" + +#: ../../tutorials/azure.rst:48 +msgid "OpenSSL 1.0.2" +msgstr "" + +#: ../../tutorials/azure.rst:50 +msgid "" +"You can check to see what versions you have installed on your system by " +"running the individual commands as follows:" +msgstr "" + +#: ../../tutorials/azure.rst:78 +msgid "" +"If you do not have these packages installed on your |CL| system, install " +"the sysadmin-basic software bundle using the :command:`swupd` command:" +msgstr "" + +#: ../../tutorials/azure.rst:87 +msgid "" +"These instructions are for installing the MS Azure CLI 2.0 tools on a " +"|CL| system. If you are installing the CLI on another platform, follow " +"the instructions in the `MS Azure Install Azure CLI tutorial`_ for your " +"specific operating system." +msgstr "" + +#: ../../tutorials/azure.rst:93 +msgid "Install MS Azure CLI 2.0 on |CL|" +msgstr "" + +#: ../../tutorials/azure.rst:95 +msgid "" +"To install the MS Azure CLI 2.0 on |CL|, use the :command:`curl` command " +"as follows:" +msgstr "" + +#: ../../tutorials/azure.rst:102 +msgid "" +"If you get an error message from :command:`curl` related to the -L " +"parameter or an error message is generated that includes the text " +"\"Object Moved\", use the full URL instead of the aka.ms redirect " +"address:" +msgstr "" + +#: ../../tutorials/azure.rst:110 +msgid "" +"The installation script begins and prompts you several times during " +"execution for information." +msgstr "" + +#: ../../tutorials/azure.rst:115 +msgid "" +"The console output from the script displays your username instead of the " +"**[user]** variable shown on this tutorial." +msgstr "" + +#: ../../tutorials/azure.rst:122 +msgid "" +"Press the :kbd:`Enter` key to accept the default or you can chose another" +" directory to install the MS Azure CLI 2.0 tools into." +msgstr "" + +#: ../../tutorials/azure.rst:129 +msgid "" +"Press the :kbd:`Enter` key to accept the default or you can chose another" +" directory to install the :command:`az` executable in." +msgstr "" + +#: ../../tutorials/azure.rst:132 +msgid "" +"The installation downloads and builds all required tools and when " +"complete prompts you with:" +msgstr "" + +#: ../../tutorials/azure.rst:139 +msgid "Type :kbd:`Y` and press the :kbd:`Enter` key to allow this modification." +msgstr "" + +#: ../../tutorials/azure.rst:145 +msgid "" +"Press the :kbd:`Enter` key to accept the default or enter the pathname to" +" your :file:`.bashrc` file. The installation completes with the final " +"output shown below:" +msgstr "" + +#: ../../tutorials/azure.rst:160 +msgid "" +"The installation program finishes and you must restart your shell for the" +" changes to take effect. When the installation is successful, run the " +"following command to restart your shell." +msgstr "" + +#: ../../tutorials/azure.rst:168 +msgid "" +"With the MS Azure CLI 2.0 executable successfully built and installed, " +"run the :command:`az` command." +msgstr "" + +#: ../../tutorials/azure.rst:175 +msgid "The output from the :command:`az` command is shown below:" +msgstr "" + +#: ../../tutorials/azure.rst:254 +msgid "Log into your Microsoft Azure account" +msgstr "" + +#: ../../tutorials/azure.rst:256 +msgid "" +"With the :command:`az` command properly installed and functional, login " +"to your MS Azure account using the :command:`az login` command shown " +"below:" +msgstr "" + +#: ../../tutorials/azure.rst:263 +msgid "The output from this command is:" +msgstr "" + +#: ../../tutorials/azure.rst:269 +msgid "" +"Open your browser and enter the page `https://aka.ms/devicelogin` as " +"shown in figure 1:" +msgstr "" + +#: ../../tutorials/azure.rst:276 +msgid "Figure 1: :guilabel:`Microsoft Device Login`" +msgstr "" + +#: ../../tutorials/azure.rst:278 +msgid "" +"Enter the code `BQ9MG442B` to authenticate your device as shown in figure" +" 2. The code `BQ9MG442B` is a random authentication code generated for " +"each session login and will be different each time you log into MS Azure " +"using the :command:`az login` command." +msgstr "" + +#: ../../tutorials/azure.rst:287 +msgid "Figure 2: :guilabel:`Microsoft Device Login - Azure CLI`" +msgstr "" + +#: ../../tutorials/azure.rst:289 +msgid "" +"Once you enter the authentication code, the website changes to a screen " +"to enter your existing Microsoft Azure credentials." +msgstr "" + +#: ../../tutorials/azure.rst:292 +msgid "" +"Log in with your existing MS Azure account credentials. Once complete, " +"the browser screen changes again as shown in figure 3. The screen shows " +"you have signed into the Microsoft Cross-platform Command Line Interface " +"application on your device and you can close the window." +msgstr "" + +#: ../../tutorials/azure.rst:301 +msgid "Figure 3: :guilabel:`Microsoft Azure Cross-platform CLI`" +msgstr "" + +#: ../../tutorials/azure.rst:303 +msgid "" +"The MS Azure CLI 2.0 interface is now active using your existing MS Azure" +" account credentials." +msgstr "" + +#: ../../tutorials/azure.rst:307 +msgid "Create a MS Azure resource group" +msgstr "" + +#: ../../tutorials/azure.rst:309 +msgid "" +"To learn more about MS Azure resource groups, visit the `Azure Resource " +"Manager overview`_ for an overview and detailed description of resources " +"within MS Azure." +msgstr "" + +#: ../../tutorials/azure.rst:313 +msgid "" +"To create our new resource group, run the :command:`az group create ...` " +"command shown below to create a resource group named `ClearResourceGroup`" +" using the `-n` parameter and locate it in the `westus` region using the " +"`-l` parameter." +msgstr "" + +#: ../../tutorials/azure.rst:322 +msgid "" +"When the command has completed, the output from this command is similar " +"to the following:" +msgstr "" + +#: ../../tutorials/azure.rst:339 +msgid "Create and log into the |CL| virtual machine" +msgstr "" + +#: ../../tutorials/azure.rst:341 +msgid "For this tutorial, we are using the |CL| Basic SKU for our VM." +msgstr "" + +#: ../../tutorials/azure.rst:343 +msgid "" +"To locate the available |CL| Basic VM SKU images in the MS Azure " +"marketplace, run the :command:`az vm image ...` command:" +msgstr "" + +#: ../../tutorials/azure.rst:350 +msgid "" +"This command may take some time to finish. The output lists all available" +" |CL| Basic images available in the Microsoft Azure marketplace as shown " +"below:" +msgstr "" + +#: ../../tutorials/azure.rst:370 +msgid "" +"The output list shows current offerings. New versions are added to the MS" +" Azure marketplace all the time. To reference the latest version of an " +"image, you can use the version label `latest` when specifying an image." +msgstr "" + +#: ../../tutorials/azure.rst:374 +msgid "" +"The information shown in the `Urn` column lists the " +"`Publisher:Offer:Sku:Version` for each image available and this is the " +"information we want to create the |CL| Basic VM. Since we are creating a " +"|CL| Basic VM, highlight the `clear-linux-project:clear-linux-os:basic:` " +"string and copy it to your clipboard. Use the label `latest` instead of " +"referencing a specific version." +msgstr "" + +#: ../../tutorials/azure.rst:381 +msgid "" +"Create the new |CL| Basic VM. Run the :command:`az vm create ...` command" +" using the URN `:clear-linux-project:clear-linux-os:basic:latest` that we" +" copied to the clipboard on the previous step." +msgstr "" + +#: ../../tutorials/azure.rst:391 +msgid "" +"If you have already defined your public/private SSH key pair and they are" +" stored in your :file:`$HOME/.ssh` directory, you do not need to include " +"the *--generate-ssh-keys* option." +msgstr "" + +#: ../../tutorials/azure.rst:395 +msgid "" +"Your output from this command will look similar to this output, where " +"[user] is your user name:" +msgstr "" + +#: ../../tutorials/azure.rst:416 +msgid "Take note of the public IP address from the output." +msgstr "" + +#: ../../tutorials/azure.rst:418 +msgid "" +"Login into the new |CL| Basic VM, run the :command:`ssh` command with the" +" public IP address obtained from the previous step as shown:" +msgstr "" + +#: ../../tutorials/azure.rst:425 +msgid "" +"You may see the following message about the authenticity of the host. If " +"this appears, type `yes` to proceed connecting to your new |CL| VM." +msgstr "" + +#: ../../tutorials/azure.rst:437 +msgid "" +"You are now logged into your new |CL| VM as [user], where [user] is your " +"user name. To check which software bundles are included with this VM " +"image, run the :command:`sudo swupd bundle-list` command inside the VM:" +msgstr "" + +#: ../../tutorials/azure.rst:445 +msgid "The output shown should be similar to:" +msgstr "" + +#: ../../tutorials/azure.rst:467 +msgid "" +"When you are finished using your new |CL| VM, type :command:`exit` to " +"close the :command:`SSH` terminal and logout." +msgstr "" + +#: ../../tutorials/azure.rst:471 +msgid "Stop and deallocate the |CL| VM and resources" +msgstr "" + +#: ../../tutorials/azure.rst:473 +msgid "" +"When you finish using your new |CL| instance, you must stop the VM and " +"deallocate the resources in your resource group. If you only stop a VM, " +"the OS image shuts down but the resources associated with it in your " +"resource group remain allocated and incurring charges. For instance, if " +"you stop and then later start the VM using the :command:`az vm start...` " +"without deallocating the resources, the IP address is retained and you " +"can access the VM using that same IP address. To release the resources " +"associated with the VM and stop incurring charges for them, you must " +"deallocate the resources as well." +msgstr "" + +#: ../../tutorials/azure.rst:482 +msgid "" +"At the command prompt, enter the :command:`az vm stop...` command as " +"follows:" +msgstr "" + +#: ../../tutorials/azure.rst:489 +msgid "This will stop the VM and then output text similar to:" +msgstr "" + +#: ../../tutorials/azure.rst:501 +msgid "" +"Once the VM stops, deallocate the VM resources to stop incurring charges " +"for the |CL| instance. Enter the following command:" +msgstr "" + +#: ../../tutorials/azure.rst:508 +msgid "**Congratulations!**" +msgstr "" + +#: ../../tutorials/azure.rst:510 +msgid "" +"You are up and running with |CL| on MS Azure using the Azure CLI 2.0 " +"command line tools." +msgstr "" + +#: ../../tutorials/azure.rst:514 +msgid "Next steps" +msgstr "" + +#: ../../tutorials/azure.rst:516 +msgid "" +"To see use cases you can fulfill with your |CL| instance, visit our " +":ref:`tutorials ` section." +msgstr "" + +#: ../../tutorials/azure.rst:519 +msgid "" +"For additional information visit the |CL| `Azure Partner Mini Case " +"Study`_ and the `Azure Partner Datasheet`_." +msgstr "" + +#: ../../tutorials/azure.rst:522 +msgid "" +"To learn more about the MS Azure CLI 2.0 tool and options that are " +"available, visit the `MS Azure documentation and tutorials`_ website." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/dars.mo b/locale/de/LC_MESSAGES/tutorials/dars.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/dars.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/dars.po b/locale/de/LC_MESSAGES/tutorials/dars.po new file mode 100644 index 00000000..a4f30456 --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/dars.po @@ -0,0 +1,128 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/dars.rst:4 +msgid "Data Analytics Reference Stack" +msgstr "" + +#: ../../tutorials/dars.rst:6 +msgid "" +"This tutorial shows you how to use the Data Analytics Reference Stack " +"(DARS), and to optionally build your own images with the baseline " +"Dockerfiles provided in the `DARS repository`_. Our assumption is that " +"|CL-ATTR| is the host. However, any system that supports Docker\\* " +"containers can be used to follow these steps." +msgstr "" + +#: ../../tutorials/dars.rst:17 +msgid "The Data Analytics Reference Stack release" +msgstr "" + +#: ../../tutorials/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 "" + +#: ../../tutorials/dars.rst:21 +msgid "" +"The Data Analytics Reference Stack provides two pre-built Docker images, " +"available on `Docker Hub`_:" +msgstr "" + +#: ../../tutorials/dars.rst:23 +msgid "A |CL|-derived `DARS with OpenBlas`_ stack optimized for `OpenBLAS`_" +msgstr "" + +#: ../../tutorials/dars.rst:24 +msgid "A |CL|-derived `DARS with MKL`_ stack optimized for `MKL`_" +msgstr "" + +#: ../../tutorials/dars.rst:26 +msgid "" +"We recommend you view the latest component versions for each image in the" +" :file:`README` found in the `DARS 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 "" + +#: ../../tutorials/dars.rst:34 +msgid "Using the Docker Images" +msgstr "" + +#: ../../tutorials/dars.rst:36 +msgid "" +"To immediately start using the latest stable DARS images, pull directly " +"from `Docker Hub`_. For this tutorial we'll use the `Dars with MKL`_ " +"version of the stack." +msgstr "" + +#: ../../tutorials/dars.rst:39 +msgid "Once you have downloaded the image, you can run it with" +msgstr "" + +#: ../../tutorials/dars.rst:45 +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 "" + +#: ../../tutorials/dars.rst:66 +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 "" + +#: ../../tutorials/dars.rst:71 +msgid "Building DARS Images" +msgstr "" + +#: ../../tutorials/dars.rst:73 +msgid "" +"If you choose to build your own DARS container images, you can customize " +"them as needed. Use the provided Dockerfile as a baseline. 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 "" + +#: ../../tutorials/dars.rst:79 +msgid "First, clone the `DARS repository`_ from GitHub." +msgstr "" + +#: ../../tutorials/dars.rst:85 +msgid "" +"Then, inside the DARS directory, run :command:`make` to build OpenBLAS " +"and MKL images, and run :command:`make baseline` to build the baseline " +"CentOS image. Depending on the system, it may take a while to finish " +"building. Once completed, check the resulting images with " +":command:`Docker`" +msgstr "" + +#: ../../tutorials/dars.rst:94 +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 "" + diff --git a/locale/de/LC_MESSAGES/tutorials/dlrs/dlrs.mo b/locale/de/LC_MESSAGES/tutorials/dlrs/dlrs.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/dlrs/dlrs.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/dlrs/dlrs.po b/locale/de/LC_MESSAGES/tutorials/dlrs/dlrs.po new file mode 100644 index 00000000..936cb860 --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/dlrs/dlrs.po @@ -0,0 +1,615 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/dlrs/dlrs.rst:4 +msgid "Deep Learning Reference Stack" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:6 +msgid "" +"This tutorial describes how to run benchmarking workloads for " +"TensorFlow\\*, PyTorch\\*, and Kubeflow in |CL-ATTR| using the Deep " +"Learning Reference Stack." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:14 +msgid "Overview" +msgstr "" + +#: ../../tutorials/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 tutorial to run " +"benchmarking workloads on your solution." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:22 +msgid "The Deep Learning Reference Stack is available in the following versions:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:24 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:27 +msgid "" +"`Intel MKL-DNN`_, which includes the TensorFlow framework optimized using" +" Intel® Math Kernel Library for Deep Neural Networks (Intel® MKL-DNN) " +"primitives." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:30 +msgid "`Eigen`_, which includes `TensorFlow`_ optimized for Intel® architecture." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:31 +msgid "`PyTorch with OpenBLAS`_, which includes PyTorch with OpenBlas." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:32 +msgid "" +"`PyTorch with Intel MKL-DNN`_, which includes PyTorch optimized using " +"Intel® Math Kernel Library (Intel® MKL) and Intel MKL-DNN." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:37 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:40 +msgid "Intel® AVX-512 images require an Intel® Xeon® Scalable Platform" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:41 +msgid "VNNI requires a 2nd generation Intel® Xeon® Scalable Platform" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:44 +msgid "Stack features" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:46 +msgid "Deep Learning Reference Stack `V3.0 release announcement`_." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:47 +msgid "" +"Deep Learning Reference Stack v2.0 including current `PyTorch benchmark " +"results`_." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:49 +msgid "" +"Deep Learning Reference Stack v1.0 including current `TensorFlow " +"benchmark results`_." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:51 +msgid "" +"`Release notes on Github\\*`_ for the latest release of Deep Learning " +"Reference Stack." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:56 +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 `terms of " +"use`_ for more details about licensing and usage of the Deep Learning " +"Reference Stack." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:61 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:63 +msgid ":ref:`Install ` |CL| on your host system" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:64 +msgid ":command:`containers-basic` bundle" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:65 +msgid ":command:`cloud-native-basic` bundle" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:67 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:76 +msgid "" +"To install the :command:`containers-basic` or :command:`cloud-native-" +"basic` bundles, enter:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:83 +msgid "" +"Docker is not started upon installation of the :command:`containers-" +"basic` bundle. To start Docker, enter:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:90 +msgid "" +"To ensure that Kubernetes is correctly installed and configured, follow " +"the instructions in :ref:`kubernetes`." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:94 +msgid "Version compatibility" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:96 +msgid "We validated these steps against the following software package versions:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:98 +msgid "|CL| 26240 (Minimum supported version)" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:99 +msgid "Docker 18.06.1" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:100 +msgid "Kubernetes 1.11.3" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:101 +msgid "Go 1.11.12" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:106 +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 tutorial 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 "" + +#: ../../tutorials/dlrs/dlrs.rst:109 +msgid "TensorFlow single and multi-node benchmarks" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:111 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:118 +msgid "" +"Performance test results for the Deep Learning Reference Stack and for " +"this tutorial were obtained using `runc` as the runtime." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:122 +msgid "" +"Download either the `Eigen`_ or the `Intel MKL-DNN`_ Docker image from " +"`Docker Hub`_." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:125 ../../tutorials/dlrs/dlrs.rst:167 +msgid "Run the image with Docker:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:134 ../../tutorials/dlrs/dlrs.rst:175 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:138 +msgid "Clone the benchmark repository in the container:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:144 ../../tutorials/dlrs/dlrs.rst:185 +msgid "Execute the benchmark script:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:152 +msgid "" +"You can replace the model with one of your choice supported by the " +"TensorFlow benchmarks." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:155 +msgid "" +"If you are using an FP32 based model, it can be converted to an int8 " +"model using `Intel® quantization tools`_." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:159 +msgid "PyTorch single and multi-node benchmarks" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:161 +msgid "" +"This section describes running the `PyTorch benchmarks`_ for Caffe2 in " +"single node." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:164 +msgid "" +"Download either the `PyTorch with OpenBLAS`_ or the `PyTorch with Intel " +"MKL-DNN`_ Docker image from `Docker Hub`_." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:179 +msgid "Clone the benchmark repository:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:195 +msgid "Kubeflow multi-node benchmarks" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:197 +msgid "" +"The benchmark workload runs in a Kubernetes cluster. The tutorial uses " +"`Kubeflow`_ for the Machine Learning workload deployment on three nodes." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:202 +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 tutorial." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:206 +msgid "Kubernetes setup" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:208 +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`_." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:213 +msgid "Kubernetes networking" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:215 +msgid "" +"We used `flannel`_ as the network provider for these tests. If you prefer" +" a different network layer, refer to the Kubernetes `networking " +"documentation`_ for setup." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:220 +msgid "Kubectl" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:222 +msgid "" +"You can use kubectl to run commands against your Kubernetes cluster. " +"Refer to the `kubectl overview`_ 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 "" + +#: ../../tutorials/dlrs/dlrs.rst:227 +msgid "Copy this example.yaml script to your system:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:244 +msgid "Execute the script with kubectl:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:250 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:254 +msgid "Images" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:256 +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 tutorial uses Kubeflow v0.4.0, and cannot " +"guarantee results if you use a different version." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:260 +msgid "From the Docker image, run the following:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:269 +msgid "Your entry point becomes: :file:`/opt/launcher.py`." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:271 +msgid "This builds an image that can be consumed directly by TFJob from Kubeflow." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:274 +msgid "ksonnet\\*" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:276 +msgid "" +"Kubeflow uses ksonnet\\* to manage deployments, so you must install it " +"before setting up Kubeflow." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:279 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:283 +msgid "On |CL|, follow these steps:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:294 +msgid "" +"After the ksonnet installation is complete, ensure that binary `ks` is " +"accessible across the environment." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:298 +msgid "Kubeflow" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:300 +msgid "" +"Once you have Kubernetes running on your nodes, set up `Kubeflow`_ by " +"following these instructions from the `quick start guide`_." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:318 +msgid "Next, deploy the primary package for our purposes: tf-job-operator." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:328 +msgid "" +"This creates the CustomResourceDefinition (CRD) endpoint to launch a " +"TFJob." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:331 +msgid "Run a TFJob" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:333 +msgid "Select this link for the `ksonnet registries for deploying TFJobs`_." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:335 +msgid "Install the TFJob components as follows:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:343 +msgid "Export the image name to use for the deployment:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:351 +msgid "Replace with the image name you specified in previous steps." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:353 +msgid "" +"Generate Kubernetes manifests for the workloads and apply them using " +"these commands:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:363 +msgid "This replicates and deploys three test setups in your Kubernetes cluster." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:366 +msgid "Results of running this tutorial" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:368 +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 from the Kubernetes community." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:375 +msgid "Use Jupyter Notebook" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:377 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:385 +msgid "" +"After you start the container, launch the Jupyter Notebook. This command " +"is executed inside the container image." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:392 +msgid "" +"After the notebook has loaded, you will see output similar to the " +"following:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:400 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:408 +msgid "Your browser displays the following:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:414 +msgid "Figure 1: :guilabel:`Jupyter Notebook`" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:417 +msgid "" +"To create a new notebook, click :guilabel:`New` and select " +":guilabel:`Python 3`." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:423 +msgid "Figure 2: Create a new notebook" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:425 +msgid "A new, blank notebook is displayed, with a cell ready for input." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:432 +msgid "" +"To verify that PyTorch is working, copy the following snippet into the " +"blank cell, and run the cell." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:446 +msgid "When you run the cell, your output will look something like this:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:452 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:457 +msgid "Uninstallation" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:459 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:461 +msgid "To stop the container, execute the following from your host system:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:463 +msgid "Find the container's ID" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:469 +msgid "This will result in output similar to the following:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:476 +msgid "" +"You can then use the ID or container name to stop the container. This " +"example uses the name \"oss\":" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:483 +msgid "Verify that the container is not running" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:490 +msgid "To delete the container from your system you need to know the Image ID:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:496 +msgid "This command results in output similar to the following:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:504 +msgid "To remove an image use the image ID:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:520 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:522 +msgid "Once you have removed the image, you can verify it has been deleted with:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:530 +msgid "Related topics" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:532 +msgid "Deep Learning Reference Stack `V3.0 release announcement`_" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:533 +msgid "`TensorFlow benchmarks`_" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:534 +msgid "`PyTorch benchmarks`_" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:535 +msgid "`Kubeflow`_" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:536 +msgid ":ref:`kubernetes` tutorial" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:537 +msgid "`Jupyter Notebook`_" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/docker/docker.mo b/locale/de/LC_MESSAGES/tutorials/docker/docker.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/docker/docker.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/docker/docker.po b/locale/de/LC_MESSAGES/tutorials/docker/docker.po new file mode 100644 index 00000000..dcd04626 --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/docker/docker.po @@ -0,0 +1,297 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/docker/docker.rst:4 +msgid "Run Docker\\* on |CL-ATTR|" +msgstr "" + +#: ../../tutorials/docker/docker.rst:6 +msgid "" +"|CL-ATTR| supports multiple containerization platforms, including a " +"Docker\\* solution. |CL| has many `unique features`_ including a minimal " +"default installation, which makes it compelling to use as a host for " +"container workloads, management, and orchestration." +msgstr "" + +#: ../../tutorials/docker/docker.rst:11 +msgid "This tutorial covers:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:18 +msgid "" +"This tutorial focuses on the installaton of the Docker ecosystem. If you " +"want to use |CL| as a Docker container image, refer to the official |CL| " +"container image `published on Docker* Hub " +"`_ and our guide to :ref:`custom-" +"clear-container`." +msgstr "" + +#: ../../tutorials/docker/docker.rst:25 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/docker/docker.rst:27 +msgid "" +"This tutorial assumes you have installed |CL| on your host system. For " +"detailed instructions on installing |CL| on a bare metal system, follow " +"the :ref:`bare metal installation instructions`." +msgstr "" + +#: ../../tutorials/docker/docker.rst:31 +msgid "" +"Before you install any new packages, update |CL| with the following " +"command:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:37 +msgid "Additionally, you should have:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:39 +msgid "A basic understanding of Linux and Docker." +msgstr "" + +#: ../../tutorials/docker/docker.rst:41 +msgid "" +"|CL| environment that has transparent network access to the Internet. If " +"you are behind a HTTP proxy server, in a corporate setting for example, " +"please refer to the `Docker proxy instructions`_ ." +msgstr "" + +#: ../../tutorials/docker/docker.rst:46 +msgid "Install the containers-basic bundle" +msgstr "" + +#: ../../tutorials/docker/docker.rst:48 +msgid "" +"Software in |CL| is offered in the form of `bundles`_ to provide a " +"complete function. The *containers-basic* provides all the required " +"software packages to run Docker images as containers." +msgstr "" + +#: ../../tutorials/docker/docker.rst:52 +msgid "" +"First, install the *containers-basic* bundle by running this " +":command:`swupd` command:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:59 +msgid "Start the Docker daemon through systemd manager by running this command:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:65 +msgid "" +"If you want Docker to start automatically on boot, enable the systemd " +"service by running this command:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:72 +msgid "" +"Finally, verify :command:`docker` has been installed by running this " +"command and checking the version output for both *client* and *server*:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:79 +msgid "" +"Congratulations! At this point, you have a working installation of Docker" +" on |CL|. You are ready to start using container images on your system." +msgstr "" + +#: ../../tutorials/docker/docker.rst:83 +msgid "Integration with Kata Containers (optional)" +msgstr "" + +#: ../../tutorials/docker/docker.rst:85 +msgid "" +"`Kata Containers`_, is an open source project aiming to increase security" +" of containers by using a hardware-backed virtual machine container " +"runtime rather than software namespace containers that are provided by " +"the standard Docker *runc* runtime." +msgstr "" + +#: ../../tutorials/docker/docker.rst:90 +msgid "" +"|CL| provides easy integration of the *kata-runtime* with Docker. More " +"information on installing and using the *kata-runtime* may be found at " +":ref:`kata`." +msgstr "" + +#: ../../tutorials/docker/docker.rst:96 +msgid "" +"The proceeding sections of this tutorial are standard to Docker setup and" +" configuration. If you are familiar with Docker basics, you do not need " +"to continue reading. The following sections are provided here for sake of" +" completeness." +msgstr "" + +#: ../../tutorials/docker/docker.rst:104 +msgid "Additional Docker configuration" +msgstr "" + +#: ../../tutorials/docker/docker.rst:106 +msgid "" +"Perform additional Docker daemon configuration via a configuration file " +"typically located at :file:`/etc/docker/daemon.json`. |CL| features a " +"`stateless system`_ so the configuration file :file:`daemon.json` does " +"*NOT* exist by default." +msgstr "" + +#: ../../tutorials/docker/docker.rst:111 +msgid "Create the :file:`daemon.json` by running this command:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:119 +msgid "" +"Refer to the `Docker documentation on daemon configuration`_ for the full" +" list of available configuration options and examples." +msgstr "" + +#: ../../tutorials/docker/docker.rst:122 +msgid "" +"For production systems, we follow Docker's recommendation to use the " +"`OverlayFS storage driver`_ `overlay2`, shown below:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:133 +msgid "" +"A testing version is found in `Docker Device Mapper storage driver`_. If " +"using this storage driver, a warning message may appear: \"usage of " +"loopback devices is strongly discouraged for production use\"." +msgstr "" + +#: ../../tutorials/docker/docker.rst:137 +msgid "Save and close :file:`daemon.json`." +msgstr "" + +#: ../../tutorials/docker/docker.rst:139 +msgid "" +"Once you've made any required changes, be sure to restart the Docker " +"daemon through systemd manager by running this command:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:147 +msgid "Pulling and running an image from Docker Hub" +msgstr "" + +#: ../../tutorials/docker/docker.rst:149 +msgid "" +"`Docker Hub`_ is a publically available container image repository which " +"comes preconfigured with Docker. In the example below we will pull and " +"run an the official Docker image for nginx, an open source reverse proxy " +"server." +msgstr "" + +#: ../../tutorials/docker/docker.rst:153 +msgid "" +"First, pull a container image from Docker Hub using the :command:`docker " +"pull` command. Download the latest nginx Docker container image by " +"running this command:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:161 +msgid "" +"Create and launch a new container using the :command:`docker run` " +"command. Launch a nginx container by running this command:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:170 +msgid "" +"Below is an explanation of switches used in the command above. For " +"detailed :command:`docker run` switches and syntax, refer to the `Docker " +"Documentation`_ ." +msgstr "" + +#: ../../tutorials/docker/docker.rst:174 +msgid "" +"The *--name* switch lets you provide a friendly name to target the " +"container for future operations" +msgstr "" + +#: ../../tutorials/docker/docker.rst:177 +msgid "The *-d* switch launches the container in the background" +msgstr "" + +#: ../../tutorials/docker/docker.rst:179 +msgid "" +"The *-p* switch allows the container's HTTP port (80) to be accessible " +"from the |CL| host on port 8080" +msgstr "" + +#: ../../tutorials/docker/docker.rst:182 +msgid "" +"You can access the Welcome to Nginx! splash page running in the container" +" by browsing to \\http://127.0.0.1:8080 or by running this " +":command:`curl` command from your |CL| machine:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:190 +msgid "" +"Finally, stop and delete the nginx container by running the " +":command:`docker stop` and :command:`docker rm` commands." +msgstr "" + +#: ../../tutorials/docker/docker.rst:198 +msgid "" +"Congratulations! At this point, you have successfully pulled a nginx " +"container image from `Docker Hub`_ and have run an example container." +msgstr "" + +#: ../../tutorials/docker/docker.rst:202 +msgid "Creating a Docker swarm cluster" +msgstr "" + +#: ../../tutorials/docker/docker.rst:204 +msgid "Clusters of Docker hosts are referred to as *swarms*." +msgstr "" + +#: ../../tutorials/docker/docker.rst:206 +msgid "" +"The process in this tutorial can be repeated to install Docker on " +"multiple |CL| hosts with the intent to form a Docker swarm cluster." +msgstr "" + +#: ../../tutorials/docker/docker.rst:209 +msgid "" +"The `Docker documentation on swarm key concepts`_ and `Docker " +"documentation on creating a swarm`_ can be referenced for further " +"instructions on setting up a swarm." +msgstr "" + +#: ../../tutorials/docker/docker.rst:214 +msgid "Related topics" +msgstr "" + +#: ../../tutorials/docker/docker.rst:216 +msgid "`Docker Home`_" +msgstr "" + +#: ../../tutorials/docker/docker.rst:217 +msgid "`Docker Documentation`_" +msgstr "" + +#: ../../tutorials/docker/docker.rst:218 +msgid "`Docker Hub`_" +msgstr "" + +#: ../../tutorials/docker/docker.rst:219 +msgid "`Kata Containers`_" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/flatpak/flatpak.mo b/locale/de/LC_MESSAGES/tutorials/flatpak/flatpak.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/flatpak/flatpak.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/flatpak/flatpak.po b/locale/de/LC_MESSAGES/tutorials/flatpak/flatpak.po new file mode 100644 index 00000000..e4b094b6 --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/flatpak/flatpak.po @@ -0,0 +1,117 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/flatpak/flatpak.rst:4 +msgid "Use Flatpak\\* to install applications on |CL-ATTR|" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:6 +msgid "" +"This tutorial provides all the required steps to install Flatpak as well " +"as downloading, installing, and running LibreOffice\\* on |CL-ATTR|." +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:9 +msgid "" +"Please visit the `Flatpak website`_ for more information about Flatpak " +"and how to use it. You can also `download it here`_." +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:13 +msgid "Before you begin" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:15 +msgid "" +"This tutorial assumes you have installed |CL| on your host system. For " +"detailed instructions on installing |CL| on a bare metal system, visit " +"our :ref:`bare metal installation guide `." +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:20 +msgid "Install Flatpak on your host system" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:22 +msgid "" +"Flatpak is included as part of the bundle `desktop`. To install the " +"application, log in to your user account and enter the following command:" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:30 +msgid "Install and run the LibreOffice Flatpak image" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:32 +msgid "" +"Application developers have the option to bundle their applications using" +" Flatpak to allow the installation of a single distribution of their " +"application on different distributions of Linux, including |CL|. Flatpak " +"provides a `list of applications`_ available through Flathub." +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:37 +msgid "|CL| enables the Flathub repository by default." +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:41 +msgid "Installing using gnome software" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:43 +msgid "" +"All you need to do is to launch `gnome software`, search for the " +"LibreOffice app, and click the install button." +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:49 +msgid "Figure 1: Installing LibreOffice using gnome-software" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:54 +msgid "Installing using the command line" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:56 +msgid "" +"Open the `gnome-terminal` and type the following command to install the " +"LibreOffice app." +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:79 +msgid "Launch LibreOffice" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:80 +msgid "" +"A new set of icons will appear in your Gnome applications list titled " +":guilabel:`LibreOffice.` To execute the application, highlight the " +"application and click on the :guilabel:`LibreOffice` icon. LibreOffice " +"will start normally." +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:87 +msgid "Figure 2: Select :guilabel:`LibreOffice` app" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:90 +msgid "Using the command line" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/fmv.mo b/locale/de/LC_MESSAGES/tutorials/fmv.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/fmv.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/fmv.po b/locale/de/LC_MESSAGES/tutorials/fmv.po new file mode 100644 index 00000000..63e9c1a6 --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/fmv.po @@ -0,0 +1,180 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/fmv.rst:4 +msgid "Use the function multi-version patch generator" +msgstr "" + +#: ../../tutorials/fmv.rst:6 +msgid "" +"CPU architectures often gain interesting new instructions as they evolve " +"but application developers find it difficult to take advantage of those " +"instructions. The reluctance to lose backward-compatibility is one of the" +" main roadblocks slowing developers from using advancements in newer " +"computing architectures. :abbr:`FMV (Function Multi-Versioning)`, which " +"first appeared in `GCC`_ 4.8, is a way to have multiple implementations " +"of a function, each using a different architecture specialized " +"instruction-set extensions. GCC 6 introduces changes to FMV to make it " +"even easier to bring architecture- based optimizations to the application" +" code." +msgstr "" + +#: ../../tutorials/fmv.rst:16 +msgid "" +"In this tutorial we will use FMV on general code and on :abbr:`FFT (Fast " +"Fourier Transform)` library code. Upon completing the tutorial, you will " +"be able to use this technology on your code and use the libraries to " +"deploy architecture-based optimizations to your application code." +msgstr "" + +#: ../../tutorials/fmv.rst:22 +msgid "Install and configure a |CL| host on bare metal" +msgstr "" + +#: ../../tutorials/fmv.rst:23 +msgid "" +"First, follow our guide to :ref:`bare-metal-install-desktop`. Once the " +"bare metal installation and initial configuration are complete, add the " +"`desktop-dev` bundle to the system. `desktop-dev`: contains the necessary" +" development tools like GCC and Perl\\*." +msgstr "" + +#: ../../tutorials/fmv.rst:28 +msgid "" +"To install the bundles, run the following command in the :file:`$HOME` " +"directory:" +msgstr "" + +#: ../../tutorials/fmv.rst:36 +msgid "Detect loop vectorization candidates" +msgstr "" + +#: ../../tutorials/fmv.rst:38 +msgid "" +"Now, we need to detect the loop vectorization candidates to be cloned for" +" multiple platforms with FMV. As an example, we will use the following " +"simple C code:" +msgstr "" + +#: ../../tutorials/fmv.rst:67 +msgid "" +"Save the example code as :file:`example.c` in the current directory and " +"build with the following flags:" +msgstr "" + +#: ../../tutorials/fmv.rst:74 +msgid "The build generates the following output:" +msgstr "" + +#: ../../tutorials/fmv.rst:81 +msgid "The output shows that line 11 is a good candidate for vectorization:" +msgstr "" + +#: ../../tutorials/fmv.rst:89 +msgid "Generate the FMV patch" +msgstr "" + +#: ../../tutorials/fmv.rst:91 +msgid "" +"To generate the FMV patch with the `make-fmv-patch`_ project, we must " +"clone the project and generate a log file with the loop vectorized " +"information:" +msgstr "" + +#: ../../tutorials/fmv.rst:100 +msgid "To generate the patch files, execute:" +msgstr "" + +#: ../../tutorials/fmv.rst:106 +msgid "" +"The :file:`make-fmv-patch.pl` script takes two arguments: `` " +"and ``. Replace `` and `` with the " +"proper values and execute:" +msgstr "" + +#: ../../tutorials/fmv.rst:114 +msgid "The command generates the following :file:`example.c.patch` patch:" +msgstr "" + +#: ../../tutorials/fmv.rst:129 +msgid "" +"We recommend you use the :file:`make-fmv-patch` script to add the " +"attribute generating the target clones on the function `foo`. Thus, we " +"can have the following code:" +msgstr "" + +#: ../../tutorials/fmv.rst:158 +msgid "" +"Changing the value of the `$avx2` variable, we can change the target " +"clones when adding the patches or in the :file:`make-fmv-patch.pl` " +"script:" +msgstr "" + +#: ../../tutorials/fmv.rst:165 +msgid "" +"Compile the code again with FMV and add the option to analyze the " +"`objdump` log:" +msgstr "" + +#: ../../tutorials/fmv.rst:173 +msgid "You can see the multiple clones of the `foo` function:" +msgstr "" + +#: ../../tutorials/fmv.rst:181 +msgid "" +"The cloned functions use AVX2 registers and vectorized instructions. To " +"verify, enter the following commands:" +msgstr "" + +#: ../../tutorials/fmv.rst:190 +msgid "FTT project example" +msgstr "" + +#: ../../tutorials/fmv.rst:192 +msgid "" +"To follow the same approach with a package like FFT, we must use the " +"`-fopt-info-vec` flag to get a build log file similar to:" +msgstr "" + +#: ../../tutorials/fmv.rst:210 +msgid "" +"For example, the :file:`fftw-3.3.6-pl2/tools/fftw-wisdom.c.patch` file " +"generates the following patches:" +msgstr "" + +#: ../../tutorials/fmv.rst:262 +msgid "" +"With these patches, we can select where to apply the FMV technology " +"making bringing architecture-based optimizations to application code even" +" easier." +msgstr "" + +#: ../../tutorials/fmv.rst:265 +msgid "**Congratulations!**" +msgstr "" + +#: ../../tutorials/fmv.rst:267 +msgid "" +"You have successfully installed an FMV development environment on |CL|. " +"Furthermore, you used cutting edge compiler technology to improve the " +"performance of your application based on Intel Architecture technology " +"and profiling of the specific execution of your application." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/greengrass.mo b/locale/de/LC_MESSAGES/tutorials/greengrass.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/greengrass.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/greengrass.po b/locale/de/LC_MESSAGES/tutorials/greengrass.po new file mode 100644 index 00000000..d73f9c53 --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/greengrass.po @@ -0,0 +1,658 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/greengrass.rst:4 +msgid "Enable AWS Greengrass\\* and OpenVINO™ toolkit" +msgstr "" + +#: ../../tutorials/greengrass.rst:6 +msgid "" +"Hardware accelerated Function-as-a-Service (FaaS) enables cloud " +"developers to deploy inference functionalities [1] on Intel® IoT edge " +"devices with accelerators (CPU, Integrated GPU, Intel® FPGA, and Intel® " +"Movidius™ technology). These functions provide a great developer " +"experience and seamless migration of visual analytics from cloud to edge " +"in a secure manner using a containerized environment. Hardware-" +"accelerated FaaS provides the best-in-class performance by accessing " +"optimized deep learning libraries on Intel® IoT edge devices with " +"accelerators." +msgstr "" + +#: ../../tutorials/greengrass.rst:15 +msgid "This tutorial demonstrates how to:" +msgstr "" + +#: ../../tutorials/greengrass.rst:17 +msgid "Set up the Intel® edge device with |CL-ATTR|" +msgstr "" + +#: ../../tutorials/greengrass.rst:18 +msgid "" +"Install the OpenVINO™ toolkit and Amazon Web Services\\* (AWS\\*) " +"Greengrass\\* software stacks" +msgstr "" + +#: ../../tutorials/greengrass.rst:20 +msgid "" +"Use AWS Greengrass\\* and AWS Lambda\\* to deploy the FaaS samples from " +"the cloud" +msgstr "" + +#: ../../tutorials/greengrass.rst:22 +msgid "Refer to the following topics:" +msgstr "" + +#: ../../tutorials/greengrass.rst:29 +msgid "Supported platforms" +msgstr "" + +#: ../../tutorials/greengrass.rst:31 +msgid "Operating System: |CL| latest release" +msgstr "" + +#: ../../tutorials/greengrass.rst:32 +msgid "" +"Hardware: Intel® core platforms (This tutorial supports inference " +"on CPU only.)" +msgstr "" + +#: ../../tutorials/greengrass.rst:35 +msgid "Sample description" +msgstr "" + +#: ../../tutorials/greengrass.rst:37 +msgid "" +"The AWS Greengrass samples are located at `Edge-Analytics-FaaS`_. This " +"tutorial uses the 1.0 version of the source code." +msgstr "" + +#: ../../tutorials/greengrass.rst:40 +msgid "|CL| provides the following AWS Greengrass samples:" +msgstr "" + +#: ../../tutorials/greengrass.rst:42 +msgid "`greengrass_classification_sample.py`_" +msgstr "" + +#: ../../tutorials/greengrass.rst:44 +msgid "" +"This AWS Greengrass sample classifies a video stream using classification" +" networks such as AlexNet and GoogLeNet and publishes top-10 results on " +"AWS\\* IoT Cloud every second." +msgstr "" + +#: ../../tutorials/greengrass.rst:48 +msgid "`greengrass_object_detection_sample_ssd.py`_" +msgstr "" + +#: ../../tutorials/greengrass.rst:50 +msgid "" +"This AWS Greengrass sample detects objects in a video stream and " +"classifies them using single-shot multi-box detection (SSD) networks such" +" as SSD Squeezenet, SSD Mobilenet, and SSD300. This sample publishes " +"detection outputs such as class label, class confidence, and bounding box" +" coordinates on AWS IoT Cloud every second." +msgstr "" + +#: ../../tutorials/greengrass.rst:58 +msgid "Install the OS on the edge device" +msgstr "" + +#: ../../tutorials/greengrass.rst:60 +msgid "" +"Start with a clean installation of |CL| on a new system, using the :ref" +":`bare-metal-install-desktop`, found in :ref:`get-started`." +msgstr "" + +#: ../../tutorials/greengrass.rst:64 +msgid "Create user accounts" +msgstr "" + +#: ../../tutorials/greengrass.rst:66 +msgid "" +"After |CL| is installed, create two user accounts. Create an " +"administrative user in |CL| and create a user account for the Greengrass " +"services to use ( see Greengrass user below)." +msgstr "" + +#: ../../tutorials/greengrass.rst:70 +msgid "" +"Create a new user and set a password for that user. Enter the following " +"commands as ``root``:" +msgstr "" + +#: ../../tutorials/greengrass.rst:78 +msgid "" +"Next, enable the :command:`sudo` command for your new ````. Add " +"```` to the *wheel* group:" +msgstr "" + +#: ../../tutorials/greengrass.rst:85 +msgid "Create a :file:`/etc/fstab` file." +msgstr "" + +#: ../../tutorials/greengrass.rst:93 +msgid "" +"By default, |CL| does not create an :file:`/etc/fstab` file. You must " +"create this file before the Greengrass service runs." +msgstr "" + +#: ../../tutorials/greengrass.rst:97 +msgid "Add required bundles" +msgstr "" + +#: ../../tutorials/greengrass.rst:99 +msgid "" +"Use the :command:`swupd` software updater utility to add the prerequisite" +" bundles for the OpenVINO software stack:" +msgstr "" + +#: ../../tutorials/greengrass.rst:108 +msgid "Learn more about how to :ref:`swupd-guide`." +msgstr "" + +#: ../../tutorials/greengrass.rst:110 +msgid "" +"The :command:`computer-vision-basic` bundle installs the OpenVINO™ " +"toolkit, and the sample models optimized for Intel® edge platforms." +msgstr "" + +#: ../../tutorials/greengrass.rst:114 +msgid "Convert deep learning models" +msgstr "" + +#: ../../tutorials/greengrass.rst:117 +msgid "Locate sample models" +msgstr "" + +#: ../../tutorials/greengrass.rst:119 +msgid "" +"There are two types of provided models that can be used in conjunction " +"with AWS Greengrass for this tutorial: classification or object " +"detection." +msgstr "" + +#: ../../tutorials/greengrass.rst:122 +msgid "" +"To complete this tutorial using an image classification model, download " +"the BVLC AlexNet model files `bvlc_alexnet.caffemodel`_ and " +"`deploy.prototxt`_ to the default model_location at " +":file:`/usr/share/openvino/models`. Any custom pre-trained classification" +" models can be used with the classification sample." +msgstr "" + +#: ../../tutorials/greengrass.rst:128 +msgid "" +"For object detection, the sample models optimized for Intel® edge " +"platforms are included with the computer-vision-basic bundle installation" +" at :file:`/usr/share/openvino/models`. These models are provided as an " +"example; however, you may also use a custom SSD model with the Greengrass" +" object detection sample." +msgstr "" + +#: ../../tutorials/greengrass.rst:134 +msgid "Run model optimizer" +msgstr "" + +#: ../../tutorials/greengrass.rst:136 +msgid "" +"Follow these instructions for `converting deep learning models to " +"Intermediate Representation using Model Optimizer`_. To optimize either " +"of the sample models described above, run one of the following commands." +msgstr "" + +#: ../../tutorials/greengrass.rst:138 +msgid "For classification using BVLC AlexNet model:" +msgstr "" + +#: ../../tutorials/greengrass.rst:147 +msgid "For object detection using SqueezeNetSSD-5Class model:" +msgstr "" + +#: ../../tutorials/greengrass.rst:156 +msgid "In these examples:" +msgstr "" + +#: ../../tutorials/greengrass.rst:158 +msgid "```` is :file:`/usr/share/openvino/models`." +msgstr "" + +#: ../../tutorials/greengrass.rst:160 +msgid "```` is FP32 or FP16, depending on target device." +msgstr "" + +#: ../../tutorials/greengrass.rst:162 +msgid "" +"```` is the directory where the Intermediate Representation " +"(IR) is stored. IR contains .xml format corresponding to the network " +"structure and .bin format corresponding to weights. This .xml file should" +" be passed to :command:``." +msgstr "" + +#: ../../tutorials/greengrass.rst:167 +msgid "" +"In the BVLC AlexNet model, the prototxt defines the input shape with " +"batch size 10 by default. In order to use any other batch size, the " +"entire input shape must be provided as an argument to the model " +"optimizer. For example, to use batch size 1, you must provide: " +"``--input_shape [1,3,227,227]``" +msgstr "" + +#: ../../tutorials/greengrass.rst:175 +msgid "Configure AWS Greengrass group" +msgstr "" + +#: ../../tutorials/greengrass.rst:177 +msgid "" +"For each Intel® edge platform, you must create a new AWS Greengrass group" +" and install AWS Greengrass core software to establish the connection " +"between cloud and edge." +msgstr "" + +#: ../../tutorials/greengrass.rst:181 +msgid "" +"To create an AWS Greengrass group, follow the instructions in `Configure " +"AWS IoT Greengrass on AWS IoT`_." +msgstr "" + +#: ../../tutorials/greengrass.rst:184 +msgid "" +"To install and configure AWS Greengrass core on edge platform, follow the" +" instructions in `Start AWS Greengrass on the Core Device`_. In step " +"8(b), download the x86_64 Ubuntu\\* configuration of the AWS Greengrass " +"core software." +msgstr "" + +#: ../../tutorials/greengrass.rst:191 +msgid "" +"You do not need to run the :file:`cgroupfs-mount.sh` script in step #6 of" +" Module 1 of the `AWS Greengrass developer guide`_ because this is " +"enabled already in |CL|." +msgstr "" + +#: ../../tutorials/greengrass.rst:195 +msgid "" +"Be sure to download both the security resources and the AWS Greengrass " +"core software." +msgstr "" + +#: ../../tutorials/greengrass.rst:200 +msgid "Security certificates are linked to your AWS account." +msgstr "" + +#: ../../tutorials/greengrass.rst:204 +msgid "Create and package Lambda function" +msgstr "" + +#: ../../tutorials/greengrass.rst:206 +msgid "" +"Complete steps 1-4 of the AWS Greengrass tutorial at `Create and Package " +"a Lambda Function`_." +msgstr "" + +#: ../../tutorials/greengrass.rst:210 +msgid "" +"This creates the tarball needed to create the AWS Greengrass environment " +"on the edge device." +msgstr "" + +#: ../../tutorials/greengrass.rst:214 +msgid "" +"In step 5, replace :file:`greengrassHelloWorld.py` with the " +"classification or object detection Greengrass sample from `Edge-" +"Analytics-Faas`_:" +msgstr "" + +#: ../../tutorials/greengrass.rst:217 +msgid "Classification: `greengrass_classification_sample.py`_" +msgstr "" + +#: ../../tutorials/greengrass.rst:219 +msgid "Object Detection: `greengrass_object_detection_sample_ssd.py`_" +msgstr "" + +#: ../../tutorials/greengrass.rst:221 +msgid "" +"Zip the selected Greengrass sample with the extracted Greengrass SDK " +"folders from the previous step into " +":file:`greengrass_sample_python_lambda.zip`." +msgstr "" + +#: ../../tutorials/greengrass.rst:224 +msgid "The zip should contain:" +msgstr "" + +#: ../../tutorials/greengrass.rst:226 +msgid "greengrasssdk" +msgstr "" + +#: ../../tutorials/greengrass.rst:228 +msgid "greengrass classification or object detection sample" +msgstr "" + +#: ../../tutorials/greengrass.rst:230 +msgid "For example:" +msgstr "" + +#: ../../tutorials/greengrass.rst:237 +msgid "" +"Return to the AWS documentation section called `Create and Package a " +"Lambda Function`_ and complete the procedure." +msgstr "" + +#: ../../tutorials/greengrass.rst:242 +msgid "" +"In step 9(a) of the AWS documentation, while uploading the zip file, make" +" sure to name the handler to one of the following, depending on the AWS " +"Greengrass sample you are using:" +msgstr "" + +#: ../../tutorials/greengrass.rst:246 +msgid "greengrass_object_detection_sample_ssd.function_handler" +msgstr "" + +#: ../../tutorials/greengrass.rst:247 +msgid "greengrass_classification_sample.function_handler" +msgstr "" + +#: ../../tutorials/greengrass.rst:251 +msgid "Configure Lambda function" +msgstr "" + +#: ../../tutorials/greengrass.rst:253 +msgid "" +"After creating the Greengrass group and the Lambda function, start " +"configuring the Lambda function for AWS Greengrass." +msgstr "" + +#: ../../tutorials/greengrass.rst:256 +msgid "" +"Follow steps 1-8 in `Configure the Lambda Function for AWS IoT " +"Greengrass`_ in the AWS documentation." +msgstr "" + +#: ../../tutorials/greengrass.rst:259 +msgid "" +"In addition to the details mentioned in step 8, change the Memory limit " +"to 2048 MB to accommodate large input video streams." +msgstr "" + +#: ../../tutorials/greengrass.rst:262 +msgid "" +"Add the following environment variables as key-value pairs when editing " +"the Lambda configuration and click on update:" +msgstr "" + +#: ../../tutorials/greengrass.rst:265 +msgid "**Table 1. Environment variables: Lambda configuration**" +msgstr "" + +#: ../../tutorials/greengrass.rst:269 +msgid "Key" +msgstr "" + +#: ../../tutorials/greengrass.rst:270 +msgid "Value" +msgstr "" + +#: ../../tutorials/greengrass.rst:271 +msgid "PARAM_MODEL_XML" +msgstr "" + +#: ../../tutorials/greengrass.rst:272 +msgid "" +"/, where is user specified and contains " +"IR.xml, the Intermediate Representation file from Intel® Model Optimizer." +" For this tutorial, should be set to " +"'/usr/share/openvino/models' or one of its subdirectories." +msgstr "" + +#: ../../tutorials/greengrass.rst:276 +msgid "PARAM_INPUT_SOURCE" +msgstr "" + +#: ../../tutorials/greengrass.rst:277 +msgid "/input.webm to be specified by user. Holds both input and" +msgstr "" + +#: ../../tutorials/greengrass.rst:278 +msgid "output data. For webcam, set PARAM_INPUT_SOURCE to ‘/dev/video0’" +msgstr "" + +#: ../../tutorials/greengrass.rst:279 +msgid "PARAM_DEVICE" +msgstr "" + +#: ../../tutorials/greengrass.rst:280 +msgid "\"CPU\"" +msgstr "" + +#: ../../tutorials/greengrass.rst:281 +msgid "PARAM_CPU_EXTENSION_PATH" +msgstr "" + +#: ../../tutorials/greengrass.rst:282 +msgid "/usr/lib64/libcpu_extension.so" +msgstr "" + +#: ../../tutorials/greengrass.rst:283 +msgid "PARAM_OUTPUT_DIRECTORY" +msgstr "" + +#: ../../tutorials/greengrass.rst:284 +msgid " to be specified by user. Holds both input and output data" +msgstr "" + +#: ../../tutorials/greengrass.rst:286 +msgid "PARAM_NUM_TOP_RESULTS" +msgstr "" + +#: ../../tutorials/greengrass.rst:287 +msgid "" +"User specified for classification sample. (e.g. 1 for top-1 result, 5 for" +" top-5 results)" +msgstr "" + +#: ../../tutorials/greengrass.rst:290 +msgid "" +"Add subscription to subscribe, or publish messages from AWS Greengrass " +"Lambda function by completing the procedure in `Configure the Lambda " +"Function for AWS IoT Greengrass`_." +msgstr "" + +#: ../../tutorials/greengrass.rst:295 +msgid "" +"The optional topic filter field is the topic mentioned inside the Lambda " +"function. In this tutorial, sample topics include the following: " +":command:`openvino/ssd` or :command:`openvino/classification`" +msgstr "" + +#: ../../tutorials/greengrass.rst:300 +msgid "Add local resources" +msgstr "" + +#: ../../tutorials/greengrass.rst:302 +msgid "" +"Refer to the AWS documentation for details about `local resources and " +"access privileges`_." +msgstr "" + +#: ../../tutorials/greengrass.rst:304 +msgid "The following table describes the local resources needed for the CPU:" +msgstr "" + +#: ../../tutorials/greengrass.rst:306 +msgid "**Local resources**" +msgstr "" + +#: ../../tutorials/greengrass.rst:310 +msgid "Name" +msgstr "" + +#: ../../tutorials/greengrass.rst:311 +msgid "Resource type" +msgstr "" + +#: ../../tutorials/greengrass.rst:312 +msgid "Local path" +msgstr "" + +#: ../../tutorials/greengrass.rst:313 +msgid "Access" +msgstr "" + +#: ../../tutorials/greengrass.rst:315 +msgid "ModelDir" +msgstr "" + +#: ../../tutorials/greengrass.rst:316 ../../tutorials/greengrass.rst:326 +msgid "Volume" +msgstr "" + +#: ../../tutorials/greengrass.rst:317 +msgid " to be specified by user" +msgstr "" + +#: ../../tutorials/greengrass.rst:318 ../../tutorials/greengrass.rst:323 +msgid "Read-Only" +msgstr "" + +#: ../../tutorials/greengrass.rst:320 +msgid "Webcam" +msgstr "" + +#: ../../tutorials/greengrass.rst:321 +msgid "Device" +msgstr "" + +#: ../../tutorials/greengrass.rst:322 +msgid "/dev/video0" +msgstr "" + +#: ../../tutorials/greengrass.rst:325 +msgid "DataDir" +msgstr "" + +#: ../../tutorials/greengrass.rst:327 +msgid " to be specified by user. Holds both input and output data." +msgstr "" + +#: ../../tutorials/greengrass.rst:329 +msgid "Read and Write" +msgstr "" + +#: ../../tutorials/greengrass.rst:332 +msgid "Deploy Lambda function" +msgstr "" + +#: ../../tutorials/greengrass.rst:334 +msgid "" +"Refer to the AWS documentation for instructions on how to `deploy the " +"lambda function to AWS Greengrass core device`_. Select *Deployments* on " +"the group page and follow the instructions." +msgstr "" + +#: ../../tutorials/greengrass.rst:339 +msgid "Output consumption" +msgstr "" + +#: ../../tutorials/greengrass.rst:341 +msgid "" +"There are four options available for output consumption. These options " +"are used to report, stream, upload, or store inference output at an " +"interval defined by the variable :command:`reporting_interval` in the AWS" +" Greengrass samples." +msgstr "" + +#: ../../tutorials/greengrass.rst:345 +msgid "IoT cloud output:" +msgstr "" + +#: ../../tutorials/greengrass.rst:347 +msgid "" +"This option is enabled by default in the AWS Greengrass samples using the" +" :command:`enable_iot_cloud_output` variable. You can use it to verify " +"the lambda running on the edge device. It enables publishing messages to " +"IoT cloud using the subscription topic specified in the lambda. (For " +"example, topics may include :command:`openvino/classification` for " +"classification and :command:`openvino/ssd` for object detection samples.)" +" For classification, top-1 result with class label are published to IoT " +"cloud. For SSD object detection, detection results such as bounding box " +"coordinates of objects, class label, and class confidence are published." +msgstr "" + +#: ../../tutorials/greengrass.rst:357 +msgid "Follow the instructions here to `view the output on IoT cloud`_." +msgstr "" + +#: ../../tutorials/greengrass.rst:359 +msgid "Kinesis streaming:" +msgstr "" + +#: ../../tutorials/greengrass.rst:361 +msgid "" +"This option enables inference output to be streamed from the edge device " +"to cloud using Kinesis [3] streams when :command:`enable_kinesis_output` " +"is set to True. The edge devices act as data producers and continually " +"push processed data to the cloud. You must set up and specify Kinesis " +"stream name, Kinesis shard, and AWS region in the AWS Greengrass samples." +msgstr "" + +#: ../../tutorials/greengrass.rst:368 +msgid "Cloud storage using AWS S3 bucket:" +msgstr "" + +#: ../../tutorials/greengrass.rst:370 +msgid "" +"When the :command:`enable_s3_jpeg_output` variable is set to True, it " +"enables uploading and storing processed frames (in jpeg format) in an AWS" +" S3 bucket. You must set up and specify the S3 bucket name in the AWS " +"Greengrass samples to store the JPEG images. The images are named using " +"the timestamp and uploaded to S3." +msgstr "" + +#: ../../tutorials/greengrass.rst:376 +msgid "Local storage:" +msgstr "" + +#: ../../tutorials/greengrass.rst:378 +msgid "" +"When the :command:`enable_s3_jpeg_output` variable is set to True, it " +"enables storing processed frames (in jpeg format) on the edge device. The" +" images are named using the timestamp and stored in a directory specified" +" by :command:`PARAM_OUTPUT_DIRECTORY`." +msgstr "" + +#: ../../tutorials/greengrass.rst:384 +msgid "References" +msgstr "" + +#: ../../tutorials/greengrass.rst:386 +msgid "AWS Greengrass: https://aws.amazon.com/greengrass/" +msgstr "" + +#: ../../tutorials/greengrass.rst:387 +msgid "AWS Lambda: https://aws.amazon.com/lambda/" +msgstr "" + +#: ../../tutorials/greengrass.rst:388 +msgid "AWS Kinesis: https://aws.amazon.com/kinesis/" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/hadoop.mo b/locale/de/LC_MESSAGES/tutorials/hadoop.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/hadoop.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/hadoop.po b/locale/de/LC_MESSAGES/tutorials/hadoop.po new file mode 100644 index 00000000..bb1ad7ee --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/hadoop.po @@ -0,0 +1,231 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/hadoop.rst:4 +msgid "Set up a single node cluster with Hadoop\\*" +msgstr "" + +#: ../../tutorials/hadoop.rst:6 +msgid "" +"This tutorial walks you through the process of installing, configuring, " +"and running Apache\\* Hadoop on |CL-ATTR|. The Apache Hadoop software " +"library is a framework for distributed processing of large data sets " +"across clusters of computers using simple programming models. It is " +"designed to scale up from single servers to thousands of machines, with " +"each machine offering local computation and storage." +msgstr "" + +#: ../../tutorials/hadoop.rst:14 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/hadoop.rst:16 +msgid "" +"Before following this tutorial, you should follow the :ref:`bare-metal-" +"install-desktop` to ensure you have installed |CL|." +msgstr "" + +#: ../../tutorials/hadoop.rst:19 +msgid "" +"Before you install any new packages, update |CL| with the following " +"command:" +msgstr "" + +#: ../../tutorials/hadoop.rst:25 +msgid "" +"For the purposes of this tutorial, we will install Hadoop in a single " +"machine running both the master and slave daemons." +msgstr "" + +#: ../../tutorials/hadoop.rst:29 +msgid "Install Apache Hadoop" +msgstr "" + +#: ../../tutorials/hadoop.rst:31 +msgid "" +"Apache Hadoop is included in the `big-data-basic` bundle. To install the " +"framework, enter the following command:" +msgstr "" + +#: ../../tutorials/hadoop.rst:39 +msgid "Configure Apache Hadoop" +msgstr "" + +#: ../../tutorials/hadoop.rst:41 +msgid "To create the configuration directory, enter the following command:" +msgstr "" + +#: ../../tutorials/hadoop.rst:47 +msgid "" +"Copy the defaults from :file:`/usr/share/defaults/hadoop` to " +":file:`/etc/hadoop` with the following command:" +msgstr "" + +#: ../../tutorials/hadoop.rst:54 +msgid "" +"Since |CL| is a stateless system, you should never modify the files under" +" the :file:`/usr/share/defaults` directory. The software updater will " +"overwrite those files." +msgstr "" + +#: ../../tutorials/hadoop.rst:58 +msgid "" +"Once all the configuration files are in :file:`/etc/hadoop`, we must edit" +" them to fit our needs. The `NameNode` server is the master server. It " +"manages the namespace of the files system and regulates the clients' " +"access to files. The first file we edit, :file:`/etc/hadoop/core-" +"site.xml`, informs the Hadoop daemon where `NameNode` is running." +msgstr "" + +#: ../../tutorials/hadoop.rst:64 +msgid "" +"In this tutorial, our `NameNode` runs in our `localhost`. Follow these " +"steps to set it up correctly:" +msgstr "" + +#: ../../tutorials/hadoop.rst:67 +msgid "" +"Open the :file:`/etc/hadoop/core-site.xml` file using the editor of your " +"choice and modify the file as follows:" +msgstr "" + +#: ../../tutorials/hadoop.rst:81 +msgid "" +"Edit the :file:`/etc/hadoop/hdfs-site.xml` file. This file configures the" +" :abbr:`HDFS (Hadoop Distributed File System)` daemons. This " +"configuration includes the list of permitted and excluded data nodes and " +"the size of said blocks. In this example, we are setting the number of " +"block replication to 1 from the default of 3 as follows:" +msgstr "" + +#: ../../tutorials/hadoop.rst:103 +msgid "" +"Edit the :file:`/etc/hadoop/mapred-site.xml` file. This file configures " +"all daemons related to `MapReduce`: `JobTracker` and `TaskTrackers`. With" +" `MapReduce`, Hadoop can process big amounts of data in multiple systems." +" In our example, we set :abbr:`YARN (Yet Another Resource Manager)` as " +"our runtime framework for executing `MapReduce` jobs as follows:" +msgstr "" + +#: ../../tutorials/hadoop.rst:121 +msgid "" +"Edit the :file:`/etc/hadoop/yarn-site.xml` file. This file configures all" +" daemons related to `YARN`: `ResourceManager` and `NodeManager`. In our " +"example, we implement the `mapreduce_shuffle` service, which is the " +"default as follows:" +msgstr "" + +#: ../../tutorials/hadoop.rst:142 +msgid "Configure your SSH key" +msgstr "" + +#: ../../tutorials/hadoop.rst:144 +msgid "Create a SSH key. If you already have one, skip this step." +msgstr "" + +#: ../../tutorials/hadoop.rst:151 +msgid "Copy the key to your authorized keys." +msgstr "" + +#: ../../tutorials/hadoop.rst:157 +msgid "" +"Log into the localhost. If no password prompt appears, you are ready to " +"run the Hadoop daemons." +msgstr "" + +#: ../../tutorials/hadoop.rst:165 +msgid "Run the Hadoop daemons" +msgstr "" + +#: ../../tutorials/hadoop.rst:167 +msgid "" +"With all the configuration files properly edited, we are ready to start " +"the daemons." +msgstr "" + +#: ../../tutorials/hadoop.rst:170 +msgid "" +"When we format the `NameNode` server, it formats the meta-data related to" +" data nodes. Thus, all the information on the data nodes is lost and the " +"nodes can be reused for new data." +msgstr "" + +#: ../../tutorials/hadoop.rst:174 +msgid "Format the `NameNode` server with the following command:" +msgstr "" + +#: ../../tutorials/hadoop.rst:180 +msgid "Start the DFS in `NameNode` and `DataNodes` with the following command:" +msgstr "" + +#: ../../tutorials/hadoop.rst:186 ../../tutorials/hadoop.rst:211 +msgid "The console output should be similar to:" +msgstr "" + +#: ../../tutorials/hadoop.rst:196 +msgid "Enter `yes` to continue." +msgstr "" + +#: ../../tutorials/hadoop.rst:198 +msgid "" +"Start the `YARN` daemons `ResourceManager` and `NodeManager` with the " +"following command:" +msgstr "" + +#: ../../tutorials/hadoop.rst:205 +msgid "Ensure everything is running as expected with the following command:" +msgstr "" + +#: ../../tutorials/hadoop.rst:223 +msgid "Run the MapReduce wordcount example" +msgstr "" + +#: ../../tutorials/hadoop.rst:225 +msgid "Create the input directory." +msgstr "" + +#: ../../tutorials/hadoop.rst:231 +msgid "Copy a file from the local file system to the HDFS." +msgstr "" + +#: ../../tutorials/hadoop.rst:237 +msgid "Run the `wordcount` example." +msgstr "" + +#: ../../tutorials/hadoop.rst:243 +msgid "" +"Read output file \"part-r-00000\". This file contains the number of times" +" each word appears in the file." +msgstr "" + +#: ../../tutorials/hadoop.rst:250 +msgid "**Congratulations!**" +msgstr "" + +#: ../../tutorials/hadoop.rst:252 +msgid "" +"You successfully installed and setup a single node Hadoop cluster. " +"Additionally, you ran a simple wordcount example." +msgstr "" + +#: ../../tutorials/hadoop.rst:255 +msgid "Your single node Hadoop cluster is up and running!" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/kata.mo b/locale/de/LC_MESSAGES/tutorials/kata.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/kata.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/kata.po b/locale/de/LC_MESSAGES/tutorials/kata.po new file mode 100644 index 00000000..faaa3d83 --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/kata.po @@ -0,0 +1,143 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/kata.rst:4 +msgid "Install Kata Containers\\*" +msgstr "" + +#: ../../tutorials/kata.rst:6 +msgid "" +"This tutorial describes how to install, configure, and run `Kata " +"Containers`_ on |CL-ATTR|. Kata Containers is an open source project " +"developing a lightweight implementation of :abbr:`VMs (Virtual Machines)`" +" that offer the speed of containers and the security of VMs." +msgstr "" + +#: ../../tutorials/kata.rst:12 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/kata.rst:14 +msgid "" +"This tutorial assumes you have installed |CL| on your host system. For " +"detailed instructions on installing |CL| on a bare metal system, follow " +"the :ref:`bare metal installation tutorial`." +msgstr "" + +#: ../../tutorials/kata.rst:18 +msgid "" +"If you have Clear Containers installed on your |CL| system, then follow " +"the :ref:`migrate Clear Containers to Kata Containers " +"tutorial`." +msgstr "" + +#: ../../tutorials/kata.rst:21 +msgid "" +"Before you install any new packages, update |CL| with the following " +"command:" +msgstr "" + +#: ../../tutorials/kata.rst:28 +msgid "Install Kata Containers" +msgstr "" + +#: ../../tutorials/kata.rst:30 +msgid "" +"Kata Containers is included in the :file:`containers-virt` bundle. To " +"install the framework, enter the following command:" +msgstr "" + +#: ../../tutorials/kata.rst:37 +msgid "Restart the Docker\\* and Kata Containers systemd services." +msgstr "" + +#: ../../tutorials/kata.rst:45 +msgid "Run Kata Containers" +msgstr "" + +#: ../../tutorials/kata.rst:53 +msgid "" +"If you use a proxy server and your proxy environment variables are " +"already set, run the following commands as a shell script to configure " +"Docker:" +msgstr "" + +#: ../../tutorials/kata.rst:70 +msgid "**Congratulations!**" +msgstr "" + +#: ../../tutorials/kata.rst:72 +msgid "You've successfully installed and set up Kata Containers on |CL|." +msgstr "" + +#: ../../tutorials/kata.rst:75 +msgid "More information about Docker" +msgstr "" + +#: ../../tutorials/kata.rst:77 +msgid "" +"Docker on |CL| provides a :file:`docker.service` file to start the Docker" +" daemon. The daemon will use runc or kata-runtime depending on the " +"environment:" +msgstr "" + +#: ../../tutorials/kata.rst:81 +msgid "" +"If you are running |CL| on bare metal or on a VM with Nested " +"Virtualization activated, Docker uses kata-runtime as the default " +"runtime." +msgstr "" + +#: ../../tutorials/kata.rst:84 +msgid "" +"If you are running |CL| on a VM without Nested Virtualization, Docker " +"uses runc as the default runtime." +msgstr "" + +#: ../../tutorials/kata.rst:87 +msgid "" +"You do not need to manually configure the runtime for Docker, because it " +"automatically uses the runtime supported by the system." +msgstr "" + +#: ../../tutorials/kata.rst:91 +msgid "Troubleshooting" +msgstr "" + +#: ../../tutorials/kata.rst:93 +msgid "" +"To change the Docker storage driver, see :ref:`additional-docker-" +"configuration`." +msgstr "" + +#: ../../tutorials/kata.rst:96 +msgid "" +"For some |CL| versions before 27000, you may need to manually configure " +"Docker\\* to use Kata Containers by default." +msgstr "" + +#: ../../tutorials/kata.rst:99 +msgid "To do so, enter:" +msgstr "" + +#: ../../tutorials/kata.rst:109 +msgid "To check the version of |CL| on your system, enter:" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/kata_migration.mo b/locale/de/LC_MESSAGES/tutorials/kata_migration.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/kata_migration.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/kata_migration.po b/locale/de/LC_MESSAGES/tutorials/kata_migration.po new file mode 100644 index 00000000..32c6f182 --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/kata_migration.po @@ -0,0 +1,104 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/kata_migration.rst:4 +msgid "Migrate Clear Containers to Kata Containers\\*" +msgstr "" + +#: ../../tutorials/kata_migration.rst:6 +msgid "" +"`Clear Containers`_ and `Kata Containers`_ can co-exist in the same " +"system. Both can be installed through the :file:`containers-virt bundle`." +" However, we recommend that you migrate to Kata Containers because Clear " +"Containers is no longer maintained_ and will soon be deprecated on |CL-" +"ATTR|." +msgstr "" + +#: ../../tutorials/kata_migration.rst:11 +msgid "This guide describes how to migrate to Kata Containers and assumes that:" +msgstr "" + +#: ../../tutorials/kata_migration.rst:13 +msgid "Clear Containers is on a Docker\\* system." +msgstr "" + +#: ../../tutorials/kata_migration.rst:14 +msgid "Kata Containers is installed. See :ref:`kata`." +msgstr "" + +#: ../../tutorials/kata_migration.rst:18 +msgid "Stop Clear Containers instances" +msgstr "" + +#: ../../tutorials/kata_migration.rst:20 +msgid "As an unprivileged user, stop all running instances of Clear Containers:" +msgstr "" + +#: ../../tutorials/kata_migration.rst:28 +msgid "Manually migrate customized configuration files" +msgstr "" + +#: ../../tutorials/kata_migration.rst:30 +msgid "" +"If you have made changes to your `Clear Containers configuration`_, " +"review those changes and decide whether to manually apply those changes " +"to your `Kata Containers configuration`_." +msgstr "" + +#: ../../tutorials/kata_migration.rst:34 +msgid "Make any required changes before continuing this process." +msgstr "" + +#: ../../tutorials/kata_migration.rst:38 +msgid "You do not need to manually remove any Clear Containers packages." +msgstr "" + +#: ../../tutorials/kata_migration.rst:42 +msgid "Enable Kata Containers as default" +msgstr "" + +#: ../../tutorials/kata_migration.rst:44 +msgid "Configure Docker to use the Kata Containers runtime by default." +msgstr "" + +#: ../../tutorials/kata_migration.rst:54 +msgid "Restart the Docker systemd services." +msgstr "" + +#: ../../tutorials/kata_migration.rst:61 +msgid "Verify Docker is using Kata Containers." +msgstr "" + +#: ../../tutorials/kata_migration.rst:69 +msgid "Run Kata Containers" +msgstr "" + +#: ../../tutorials/kata_migration.rst:71 +msgid "Use the following command:" +msgstr "" + +#: ../../tutorials/kata_migration.rst:77 +msgid "**Congratulations!**" +msgstr "" + +#: ../../tutorials/kata_migration.rst:79 +msgid "You've successfully migrated from Clear Containers to Kata Containers." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/kubernetes/kubernetes-bp.mo b/locale/de/LC_MESSAGES/tutorials/kubernetes/kubernetes-bp.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/kubernetes/kubernetes-bp.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/kubernetes/kubernetes-bp.po b/locale/de/LC_MESSAGES/tutorials/kubernetes/kubernetes-bp.po new file mode 100644 index 00000000..2dc71062 --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/kubernetes/kubernetes-bp.po @@ -0,0 +1,138 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:4 +msgid "Kubernetes Best Practices on |CL|" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:7 +msgid "Use swupd to update clusters" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:9 +msgid "" +"This tutorial shows you how to manage your Kubernetes cluster while using" +" :command:`swupd` to update |CL-ATTR|." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:12 +msgid "" +"In our tutorial :ref:`kubernetes`, we explain how to set up a Kubernetes " +"cluster on |CL| using `kubeadm`. `Kubeadm documentation`_ often builds on" +" the assumption that the distribution uses a traditional package manager " +"(e.g., RPM/DEB)." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:17 +msgid "" +"In contrast, |CL| uses `swupd` to update the OS, which in this case " +"updates all of the kubernetes node and client binaries simultaneously, as" +" part of the `cloud-native-basic` bundle (e.g., kubectl, kubeadm, " +"kubelet). Running :command:`sudo swupd update` requires special care to " +"ensure the OS incorporates the latest Kubernetes upgrades." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:23 +msgid "" +"This document describes best practices to manage cluster upgrades with " +"`kubeadm` on a |CL|-based cluster." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:27 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:29 +msgid "Assure that you:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:31 +msgid "Completed :ref:`kubernetes`" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:32 +msgid "Installed the bundle `cloud-native-basic`" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:36 +msgid "" +"Other Linux\\* distros shown in Kubernetes upgrade documentation reflect " +"`apt-get update`, `apt-mark hold kubeadm`, and similar commands; however," +" such commands **are not valid** on |CL|." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:40 +msgid "Update the control plane" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:42 +msgid "Read kubernetes documentation `before you begin`_." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:44 +msgid "On your master node, run the command:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:52 +msgid "" +"If the minor version of Kubernetes changes, |CL| shows a message-of-the-" +"day, or `motd`. When the `motd` appears, you **must postpone** a kubelet " +"restart on master and nodes until the control plane is properly updated. " +":command:`swupd update` does not restart services automatically unless " +"explicitly configured to do so." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:54 +msgid "Now follow these instructions in kubernetes documentation." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:56 +msgid "`Upgrade control plane`_" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:57 +msgid "`Drain control plane node`_" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:58 +#: ../../tutorials/kubernetes/kubernetes-bp.rst:73 +msgid "`Restart Kubelet and undrain node`_" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:61 +msgid "Update worker nodes" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:63 +msgid "On each worker node, run the command:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:69 +msgid "Now follow these instructions in kubernetes documentation:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:71 +msgid "`Drain node`_" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:72 +msgid "`Update kubelet configuration`_" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/kubernetes/kubernetes.mo b/locale/de/LC_MESSAGES/tutorials/kubernetes/kubernetes.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/kubernetes/kubernetes.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/kubernetes/kubernetes.po b/locale/de/LC_MESSAGES/tutorials/kubernetes/kubernetes.po new file mode 100644 index 00000000..38e23ec4 --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/kubernetes/kubernetes.po @@ -0,0 +1,448 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/kubernetes/kubernetes.rst:4 +msgid "Run Kubernetes\\*" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:6 +msgid "" +"This tutorial describes how to install, configure, and run the " +"`Kubernetes container orchestration system`_ on |CL-ATTR| using CRI+O and" +" kata-runtime." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:10 +msgid "" +"Kubernetes\\* is an open source system for automating deployment, " +"scaling, and management of containerized applications. It groups " +"containers that make up an application into logical units for easy " +"management and discovery." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:14 +msgid "" +"Kata Containers\\* kata-runtime adheres to :abbr:`OCI (Open Container " +"Initiative*)` guidelines and work seamlessly with Kubernetes. `Kata " +"Containers`_ provide strong isolation for untrusted workloads or multi-" +"tenant scenarios. Kata Containers can be allocated on a per-pod basis so " +"you can mix and match both on the same host to suit your needs." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:25 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:27 +msgid "" +"This tutorial assumes you have already installed |CL|. For detailed " +"instructions on installing |CL| on a bare metal system, follow the " +":ref:`bare metal installation tutorial`. " +"Learn about the benefits of having an up-to-date system for cloud " +"orchestration on the :ref:`swupd-about` page." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:33 +msgid "" +"Before you install any new packages, update |CL| with the following " +"command:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:40 +msgid "Install Kubernetes and CRI runtimes" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:42 +msgid "" +"Kubernetes, a set of supported :abbr:`CRI (Container Runtime Interface)` " +"runtimes, and networking plugins, are included in the `cloud-native-" +"basic`_ bundle." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:46 +msgid "To install this framework, enter the following command:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:54 +msgid "For more on networking plugins, see `Install pod network add-on`_." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:57 +msgid "Configure Kubernetes" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:59 +msgid "" +"This tutorial uses the basic default Kubernetes configuration for " +"simplicity. You must define your Kubernetes configuration according to " +"your specific deployment and your security needs." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:63 +msgid "Enable IP forwarding to avoid kubeadm `preflight check`_ errors:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:65 +msgid "" +"Create (or edit if it exists) the file :file:`/etc/sysctl.d/60-k8s.conf` " +"and include the following line:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:72 +msgid "Apply the change:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:78 +msgid "Enable the kubelet service:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:84 +msgid "Disable swap using one of the following methods, either:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:86 +msgid "Temporarily:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:94 +msgid "Swap will be enabled at next reboot, causing failures in your cluster." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:97 +msgid "or:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:99 +msgid "Permanently:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:101 +msgid "Mask the swap partition:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:110 +msgid "" +"On systems with limited resources, some performance degradation may be " +"observed while swap is disabled." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:113 +msgid "Switch to root to modify the `hosts` file:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:119 +msgid "" +"Create (or edit if it exists) the hosts file that Kubernetes will read to" +" locate the master's host:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:126 +msgid "Exit root:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:133 +msgid "Configure and run Kubernetes" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:135 +msgid "" +"This section describes how to configure and run Kubernetes with CRI-O and" +" kata-runtime." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:138 +msgid "Configure and run CRI-O + kata-runtime" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:140 +msgid "Enable the CRI-O service:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:146 +msgid "Enter the commands:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:153 +msgid "" +"Initialize the master control plane with the command below and follow the" +" displayed instructions to set up `kubectl`:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:159 +msgid "Register kata-runtime as a RuntimeClass handler:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:178 +msgid "Install pod network add-on" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:180 +msgid "" +"You must choose and install a `pod network add-on`_ to allow your pods to" +" communicate. Check whether or not your add-on requires special flags " +"when you initialize the master control plane." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:184 +msgid "**Notes about flannel add-on**" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:186 +msgid "" +"If you choose the `flannel` add-on, then you must add the following to " +"the `kubeadm init` command:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:193 +msgid "" +"Furthermore, if you are using CRI-O and `flannel` and you want to use " +"Kata Containers, edit the :file:`/etc/crio/crio.conf` file to add:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:202 +msgid "Use your cluster" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:204 +msgid "" +"Once your master control plane is successfully initialized, instructions " +"on how to use your cluster and its *IP*, *token*, and *hash* values are " +"displayed. It is important that you record the cluster values because " +"they are needed when joining worker nodes to the cluster. Some values " +"have a valid period. The values are presented in a format similar to:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:214 +msgid "**Congratulations!**" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:216 +msgid "" +"You've successfully installed and set up Kubernetes in |CL| using CRI-O " +"and kata-runtime. You are now ready to follow on-screen instructions to " +"deploy a pod network to the cluster and join worker nodes with the " +"displayed token and IP information." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:222 +msgid "Related topics" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:224 +msgid "Read the Kubernetes documentation to learn more about:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:226 +msgid "`Understanding basic Kubernetes architecture`_" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:228 +msgid "`Deploying an application to your cluster`_" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:230 +msgid "Installing a `pod network add-on`_" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:232 +msgid "`Joining your nodes`_" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:235 +msgid "Cloud native setup automation (optional)" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:237 +msgid "" +"Clone the `cloud-native-setup`_ repository on your system and follow the " +"instructions. This repository includes helper scripts to automate " +"configuration." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:240 +msgid "Package configuration customization (optional)" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:242 +msgid "" +"|CL| is a stateless system that looks for user-defined package " +"configuration files in the :file:`/etc/` directory to be " +"used as default. If user-defined files are not found, |CL| uses the " +"distribution-provided configuration files for each package." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:247 +msgid "" +"If you customize any of the default package configuration files, you " +"**must** store the customized files in the :file:`/etc/` directory. If " +"you edit any of the distribution-provided default files, your changes " +"will be lost in the next system update." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:252 +msgid "" +"For example, to customize CRI-O configuration in your system, run the " +"following commands:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:261 +msgid "Learn more about `Stateless`_ in |CL| and view the |CL| `documentation`_." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:264 +msgid "Proxy configuration (optional)" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:266 +msgid "" +"If you use a proxy server, you must set your proxy environment variables " +"and create an appropriate proxy configuration file for both CRI-O " +"services. Consult your IT department if you are behind a corporate proxy " +"for the appropriate values. Ensure that your local IP is **explicitly " +"included** in the environment variable *NO_PROXY*. (Setting *localhost* " +"is not enough.)" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:271 +msgid "" +"If you have already set your proxy environment variables, run the " +"following commands as a shell script to configure all of these services " +"in one step:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:289 +msgid "Next steps" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:291 +msgid ":ref:`kubernetes-bp`" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:295 +msgid "Troubleshooting" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:297 +msgid " not found in message." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:299 +msgid "" +"Your DNS server may not be appropriately configured. Try adding an entry " +"to the :file:`/etc/hosts` file with your host's IP and Name." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:302 +msgid "For example: 100.200.50.20 myhost" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:304 +msgid "" +"Use the commands :command:`hostname` and :command:`hostname -I` to " +"retrieve them." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:306 +msgid "Images cannot be pulled." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:308 +msgid "" +"You may be behind a proxy server. Try configuring your proxy settings, " +"using the environment variables *HTTP_PROXY*, *HTTPS_PROXY*, and " +"*NO_PROXY* as required in your environment." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:312 +msgid "Connection refused error." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:314 +msgid "" +"If you are behind a proxy server, you may need to add the master's IP to " +"the environment variable *NO_PROXY*." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:317 +msgid "Connection timed-out or Access Refused errors." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:319 +msgid "" +"You must ensure that the appropriate proxy settings are available from " +"the same terminal where you will initialize the control plane. To verify " +"the proxy settings that Kubernetes will actually use, run the commands:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:329 +msgid "" +"If the displayed proxy values are different from your assigned values, " +"the cluster initialization will fail. Contact your IT support team to " +"learn how to set the proxy variables permanently, and how to make them " +"available for all the types of access that you will use, such as remote " +"SSH access." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:334 +msgid "" +"If the result of the above commands is blank, you may need to add a " +"``profile`` to the :file:`/etc` directory. To do so, follow these steps." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:337 +msgid "Create a `profile` in :file:`/etc`" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:343 +msgid "" +"With a preferred editor, open `profile`, and enter your proxy settings. " +"Example shown below." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:355 +msgid " can be obtained by running :command:`ifconfig`." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:357 +msgid "Save and exit the `profile`." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:359 +msgid "Run:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:365 +msgid "To ensure your system isn't running previous session variables, run:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:371 +msgid "Continue below while passing `-E` in the command as shown." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:373 +msgid "Missing environment variables." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:375 +msgid "" +"If you are behind a proxy server, pass environment variables by adding " +"*-E* to the command that initializes the master control plane." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/machine-learning/machine-learning.mo b/locale/de/LC_MESSAGES/tutorials/machine-learning/machine-learning.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/machine-learning/machine-learning.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/machine-learning/machine-learning.po b/locale/de/LC_MESSAGES/tutorials/machine-learning/machine-learning.po new file mode 100644 index 00000000..b82bc2cd --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/machine-learning/machine-learning.po @@ -0,0 +1,314 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/machine-learning/machine-learning.rst:4 +msgid "TensorFlow\\* machine learning on |CL-ATTR|" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:6 +msgid "" +"This tutorial will demonstrate the installation and execusion of a " +"TensorFlow\\* machine learning example on |CL-ATTR|. It uses a Jupyter\\*" +" Notebook and MNIST data for handwriting recognition." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:10 +msgid "" +"The initial steps will have you set up a Jupyter kernel and run a " +"Notebook on a bare-metal |CL| system." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:14 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:16 +msgid "" +"This tutorial assumes you have installed |CL| on your host system. For " +"detailed instructions on installing |CL| on a bare metal system, follow " +"the :ref:`bare metal installation tutorial`." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:20 +msgid "" +"Before you install any new packages, update |CL| with the following " +"command:" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:26 +msgid "Once your system is updated, add the following bundles to your system:" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:28 +msgid "`machine-learning-web-ui`: This bundle contains the Jupyter application." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:30 +msgid "" +"`machine-learning-basic`: This bundle contains TensorFlow and other " +"useful tools." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:33 +msgid "" +"To install the bundles, run the following commands in your :file:`$HOME` " +"directory:" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:43 +msgid "Set up a Jupyter notebook" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:45 +msgid "" +"With all required packages and libraries installed, set up the file " +"structure for the Jupyter Notebook." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:48 +msgid "" +"In the :file:`$HOME` directory, create a directory for the Jupyter " +"Notebooks named :file:`Notebooks`." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:55 +msgid "Within :file:`Notebooks`, create a directory named :file:`Handwriting`." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:61 +msgid "Change to the new directory." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:67 +msgid "" +"Copy the :file:`MNIST_example.ipynb` file into the :file:`Handwriting` " +"directory." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:71 +msgid "" +"After installing the `machine-learning basic` bundle, you can find the " +"example code under :file:`/usr/share/doc/tensorflow/MNIST_example.ipynb`." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:76 +msgid "" +"The example code downloads and decompresses the MNIST data directly into " +"the :file:`./mnist` directory. Alternatively, download the four files " +"directly from the Yann LeCun’s `MNIST Database website`_ and save them " +"into a :file:`mnist` directory within the :file:`Handwriting` directory." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:81 +msgid "The files needed are:" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:83 +msgid "`train-images-idx3-ubyte.gz`_: Training set images (9912422 bytes)" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:85 +msgid "`train-labels-idx1-ubyte.gz`_: Training set labels (28881 bytes)" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:87 +msgid "`t10k-images-idx3-ubyte.gz`_: Test set images (1648877 bytes)" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:89 +msgid "`t10k-labels-idx1-ubyte.gz`_: Test set labels (4542 bytes)" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:92 +msgid "Run the Jupyter machine learning example code" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:94 +msgid "" +"With |CL|, Jupyter, and TensorFlow installed and configured, we can run " +"the example code." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:97 +msgid "" +"Go to the :file:`($HOME)/Notebooks` directory and start Jupyter with the " +"following commands:" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:106 +msgid "" +"The Jupyter server starts and opens a web browser showing the Jupyter " +"file manager with a list of files in the current directory, see figure 1." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:112 +msgid "Figure 1: The Jupyter file manager shows the list of available files." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:114 +msgid "" +"Click on the :file:`Handwriting` directory. The " +":file:`MNIST_example.ipynb` file created earlier should be listed there, " +"see figure 2." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:120 +msgid "Figure 2: The example file within the Jupyter file manager." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:122 +msgid "" +"To run the hand writing example, click on the :file:`MNIST_example.ipynb`" +" file to load the notebook, see figure 3." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:128 +msgid "" +"Figure 3: The loaded MNIST_example notebook within the Jupyter file " +"manager." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:131 +msgid "" +"Click the |run-cell| button to execute the code in the current cell and " +"move to the next." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:134 +msgid "" +"Select the :guilabel:`In [2]` cell and click the |run-cell| button to " +"load the MNIST data. The successful output is shown on figure 4." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:140 +msgid "Figure 4: Output after successfully importing the MNIST data." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:143 +msgid "" +"After the MNIST data was successfully downloaded and extracted into the " +":file:`mnist` directory within the :file:`($HOME)/Notebooks/Handwriting` " +"directory, four .gz files are present and the four data sets were " +"created: `trainX`, `trainY`, `testX` and `testY`." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:148 +msgid "" +"To inspect the imported data, the function in :guilabel:`In [3]` first " +"instructs Jupyter to reshape the data into an array of 28 x 28 images and" +" to plot the area in a 28 x 28 grid. Click the |run-cell| button twice to" +" show the first two digits in the `trainX` dataset, see figure 5." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:156 +msgid "" +"Figure 5: A function reshapes the data and displays the first two digits " +"in the `trainX` dataset." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:159 +msgid "" +"The :guilabel:`In [4]` cell defines the neural network. It provides the " +"inputs, defines the hidden layers, runs the training model, and sets up " +"the output layer, see figure 6. Click the |run-cell| button four times to" +" perform these operations." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:167 +msgid "Figure 6: Defining, building and training the neural network model." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:169 +msgid "" +"To test the accuracy of the prediction the system makes, select the " +":guilabel:`In [8]` cell and click the |run-cell| button. In this example," +" the number 6 was predicted with a 99% accuracy, see figure 7." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:176 +msgid "" +"Figure 7: The system predicts a number providing the accuracy of the " +"prediction." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:181 +msgid "" +"To retest the accuracy of a random data point's prediction, run the cell " +":guilabel:`In [8]` again. It will take another random data point and " +"predict its value." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:185 +msgid "" +"To check the accuracy for the whole dataset, select the :guilabel:`In " +"[10]` cell and click the |run-cell| button. Our example's accuracy is " +"calculated as 97.17%, see figure 8." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:192 +msgid "Figure 8: The system's accuracy for the entire data set." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:194 +msgid "" +"For more in-depth information on the model used and the mathematics it " +"entails, visit the TensorFlow tutorials `TensorFlow MNIST beginners " +"demo`_ and `TensorFlow MNIST pros demo`_." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:198 +msgid "**Congratulations!**" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:200 +msgid "" +"You have successfully installed a Jupyter kernel on |CL|. In addition, " +"you trained a neural network to successfully predict the values contained" +" in a data set of hand-written number images." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:205 +msgid "Related topics" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:207 +msgid "`MNIST Database website`_" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:208 +msgid "`TensorFlow MNIST beginners demo`_" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:209 +msgid "`TensorFlow MNIST pros demo`_" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:210 +msgid "`Jupyter main website`_" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:211 +msgid "`Jupyter documentation`_" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:212 +msgid "`MNIST at Wikipedia`_" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/nvidia.mo b/locale/de/LC_MESSAGES/tutorials/nvidia.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/nvidia.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/nvidia.po b/locale/de/LC_MESSAGES/tutorials/nvidia.po new file mode 100644 index 00000000..8f20bc16 --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/nvidia.po @@ -0,0 +1,420 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/nvidia.rst:4 +msgid "Install NVIDIA\\* Drivers" +msgstr "" + +#: ../../tutorials/nvidia.rst:6 +msgid "" +"NVIDIA manufactures graphics processing units (GPU), also known as " +"graphics cards." +msgstr "" + +#: ../../tutorials/nvidia.rst:9 +msgid "" +"NVIDIA devices on Linux\\* have two popular device driver options: the " +"opensource drivers from the `nouveau project`_ or the proprietary drivers" +" published by NVIDIA. The nouveau drivers are built into the |CL-ATTR| " +"kernel and are loaded automatically at system boot if a compatible card " +"is detected." +msgstr "" + +#: ../../tutorials/nvidia.rst:15 +msgid "" +"These instructions show how to use the proprietary NVIDIA drivers, which " +"require a manual installation." +msgstr "" + +#: ../../tutorials/nvidia.rst:20 +msgid "" +"Software installed outside of :ref:`swupd ` is not updated " +"with |CL| updates and must be updated and maintained manually." +msgstr "" + +#: ../../tutorials/nvidia.rst:23 +msgid "" +"For example, the file :file:`/usr/lib/libGL.so` conflicts between the one" +" provided by the mesa package in |CL| and the one NVIDIA provides. If a " +"|CL| update overwrites these files, a reinstallation of the NVIDIA driver" +" might be required." +msgstr "" + +#: ../../tutorials/nvidia.rst:36 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/nvidia.rst:38 +msgid "A |CL| system with a desktop installed" +msgstr "" + +#: ../../tutorials/nvidia.rst:39 +msgid "An NVIDIA device installed" +msgstr "" + +#: ../../tutorials/nvidia.rst:43 +msgid "Install DKMS" +msgstr "" + +#: ../../tutorials/nvidia.rst:45 +msgid "" +"The :ref:`Dynamic Kernel Module System (DKMS) ` " +"allows the NVIDIA kernel modules to be automatically integrated when " +"kernel updates occur in |CL|." +msgstr "" + +#: ../../tutorials/nvidia.rst:49 +msgid "Install the appropriate DKMS bundle using the instructions below:" +msgstr "" + +#: ../../tutorials/nvidia.rst:52 +msgid "" +"The Long Term Support (LTS) kernel variant is more likely to remain " +"compatible between updates with NVIDIA drivers." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:3 +msgid "" +"The *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:6 +msgid "The *kernel-native-dkms* bundle also:" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:8 +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 `." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:13 +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:17 +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:22 +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:28 +msgid "" +"Install the :command:`kernel-native-dkms` or :command:`kernel-lts-dkms` " +"bundle:" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:31 +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:40 +msgid "Ensure *.native* or *.lts* is in the kernel name." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:42 +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:50 +msgid "or" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:57 +msgid "Update the |CL| bootloader and reboot." +msgstr "" + +#: ../../tutorials/nvidia.rst:62 +msgid "Download and install the NVIDIA Drivers" +msgstr "" + +#: ../../tutorials/nvidia.rst:66 +msgid "Download the NVIDIA Drivers for Linux" +msgstr "" + +#: ../../tutorials/nvidia.rst:68 +msgid "Identify the model of NVIDIA GPU that is installed." +msgstr "" + +#: ../../tutorials/nvidia.rst:75 +msgid "" +"Go to the `NVIDIA Driver Downloads website`_ . Search for and download " +"the appropriate driver based on the model of NVIDIA GPU you have with " +"*Linux 64-bit* selected as the Operating System ." +msgstr "" + +#: ../../tutorials/nvidia.rst:80 +msgid "" +"Open a terminal and navigate to where the :file:`NVIDIA-" +"Linux-x86_64-.run` file was saved. In this example, it was saved" +" in the Downloads folder." +msgstr "" + +#: ../../tutorials/nvidia.rst:88 +msgid "Make the :file:`NVIDIA-Linux-x86_64-.run` file executable." +msgstr "" + +#: ../../tutorials/nvidia.rst:96 +msgid "Disable the nouveau Driver" +msgstr "" + +#: ../../tutorials/nvidia.rst:98 +msgid "" +"The proprietary NVIDIA driver is incompatible with the nouveau driver and" +" must be disabled before installation can continue." +msgstr "" + +#: ../../tutorials/nvidia.rst:101 +msgid "" +"Disable the nouveau driver by creating a blacklist file under " +":file:`/etc/modprobe.d` and reboot." +msgstr "" + +#: ../../tutorials/nvidia.rst:111 +msgid "" +"Reboot the system and log back in. It is normal for the graphical " +"environment not to start without the NVIDIA driver loaded." +msgstr "" + +#: ../../tutorials/nvidia.rst:118 +msgid "Configure Alternative Software Paths" +msgstr "" + +#: ../../tutorials/nvidia.rst:120 +msgid "" +"The NVIDIA installer will be directed to install files under " +":file:`/opt/nvidia` as much as possible to keep its contents isolated " +"from the rest of the |CL| system files under :file:`/usr`. The dynamic " +"linker and X server must be configured to use the content under " +":file:`/opt/nvidia`." +msgstr "" + +#: ../../tutorials/nvidia.rst:127 +msgid "" +"Configure the dynamic linker to look for and to cache shared libraries " +"under :file:`/opt/nvidia/lib` and :file:`/opt/nvidia/lib32` in addition " +"to the default paths." +msgstr "" + +#: ../../tutorials/nvidia.rst:138 +msgid "Reload the dynamic linker run-time bindings and library cache." +msgstr "" + +#: ../../tutorials/nvidia.rst:144 +msgid "" +"Create a Xorg configuration file to search for modules under " +":file:`/opt/nvidia` in addition to the default path." +msgstr "" + +#: ../../tutorials/nvidia.rst:160 +msgid "Install the NVIDIA Drivers" +msgstr "" + +#: ../../tutorials/nvidia.rst:163 +msgid "" +"A terminal not running on */dev/tty1* is useful to view uninterrupted " +"installation progress. Switch to a secondary virtual terminal by pushing " +":command:`CTRL + ALT + F2` or remotely login over SSH." +msgstr "" + +#: ../../tutorials/nvidia.rst:168 +msgid "Navigate into the directory where the NVIDIA installer was downloaded." +msgstr "" + +#: ../../tutorials/nvidia.rst:175 +msgid "Run the installer with the advanced options below." +msgstr "" + +#: ../../tutorials/nvidia.rst:199 +msgid "" +"The graphical interface may automatically start after the NVIDIA driver " +"is loaded. Return to the working terminal and log back in if necessary." +msgstr "" + +#: ../../tutorials/nvidia.rst:203 +msgid "Confirm that the NVIDIA kernel modules are loaded." +msgstr "" + +#: ../../tutorials/nvidia.rst:210 +msgid "" +"Run a |CL| system verification to restore files that the NVIDIA installer" +" likely deleted." +msgstr "" + +#: ../../tutorials/nvidia.rst:219 +msgid "" +"The NVIDIA software places some files under the :file:`/usr` subdirectory" +" which are not managed by |CL| and conflict with the |CL| stateless " +"design." +msgstr "" + +#: ../../tutorials/nvidia.rst:222 +msgid "" +"Although a limited version of :command:`swupd repair` is run above, other" +" uses of the :command:`swupd repair` command should be avoided with the " +"proprietary NVIDIA drivers installed." +msgstr "" + +#: ../../tutorials/nvidia.rst:228 +msgid "Updating the NVIDIA Drivers" +msgstr "" + +#: ../../tutorials/nvidia.rst:230 +msgid "" +"The proprietary NVIDIA drivers are installed manually outside of " +":ref:`swupd ` and must be updated manually when needed." +msgstr "" + +#: ../../tutorials/nvidia.rst:233 +msgid "" +"Updating the NVIDIA drivers follows the same steps as initial " +"installation, however the desktop environment must first be stopped so " +"that the drivers are not in use." +msgstr "" + +#: ../../tutorials/nvidia.rst:237 +msgid "" +"Follow the steps in the `Download the NVIDIA Drivers for Linux`_ section " +"to get the latest NVIDIA drivers." +msgstr "" + +#: ../../tutorials/nvidia.rst:240 +msgid "" +"Temporarily set the default boot target to the *multi-user*, which is a " +"non-graphical runtime." +msgstr "" + +#: ../../tutorials/nvidia.rst:248 +msgid "" +"Reboot the system and log back in. It is normal for the graphical " +"environment not to start." +msgstr "" + +#: ../../tutorials/nvidia.rst:251 +msgid "" +"Follow the steps in the `Install the NVIDIA Drivers`_ section to update " +"the NVIDIA drivers. This installation will overwrite the previous NVIDIA " +"drivers and files." +msgstr "" + +#: ../../tutorials/nvidia.rst:255 +msgid "Set the default boot target back to the *graphical* target." +msgstr "" + +#: ../../tutorials/nvidia.rst:262 +msgid "Reboot the system and log back in." +msgstr "" + +#: ../../tutorials/nvidia.rst:264 +msgid "" +"Trigger a flatpak update which will download the runtime corresponding " +"with the new NVIDIA drivers for the flatpak apps that require it." +msgstr "" + +#: ../../tutorials/nvidia.rst:273 +msgid "Uninstalling the NVIDIA Drivers" +msgstr "" + +#: ../../tutorials/nvidia.rst:275 +msgid "" +"The NVIDIA drivers and associated software can be uninstalled and nouveau" +" driver restored with the instructions in this section." +msgstr "" + +#: ../../tutorials/nvidia.rst:278 +msgid "Remove the :file:`modprobe.d` file that prevents nouveau from loading." +msgstr "" + +#: ../../tutorials/nvidia.rst:285 +msgid "Remove the :file:`xorg.conf.d` file that adds a search path for X modules." +msgstr "" + +#: ../../tutorials/nvidia.rst:291 +msgid "Run the :command:`sudo /opt/nvidia/bin/nvidia-uninstall`" +msgstr "" + +#: ../../tutorials/nvidia.rst:293 +msgid "Follow the prompts on the screen and reboot the system." +msgstr "" + +#: ../../tutorials/nvidia.rst:297 +msgid "Debugging Installation of NVIDIA Drivers" +msgstr "" + +#: ../../tutorials/nvidia.rst:299 +msgid "" +"The NVIDIA driver places installer and uninstaller logs under " +":file:`/var/log/nvidia-install` and :file:`/var/log/nvidia-uninstall`." +msgstr "" + +#: ../../tutorials/nvidia.rst:302 +msgid "" +":file:`NVIDIA-Linux-x86_64-.run --advanced-options` shows many " +"parameters to control installation behavior." +msgstr "" + +#: ../../tutorials/nvidia.rst:305 +msgid "" +":file:`NVIDIA-Linux-x86_64-.run --extract-only` extracts " +"installation files into a directory named :file:`NVIDIA-" +"Linux-x86_64-`." +msgstr "" + +#: ../../tutorials/nvidia.rst:312 +msgid "Additional resources" +msgstr "" + +#: ../../tutorials/nvidia.rst:314 +msgid "" +"`Why aren't the NVIDIA Linux drivers open source? " +"`_" +msgstr "" + +#: ../../tutorials/nvidia.rst:316 +msgid "" +"`Where can I get support for NVIDIA Linux drivers? " +"`_" +msgstr "" + +#: ../../tutorials/nvidia.rst:318 +msgid "" +"`NVIDIA Accelerated Linux Graphics Driver Installation Guides " +"`_" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/redis.mo b/locale/de/LC_MESSAGES/tutorials/redis.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/redis.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/redis.po b/locale/de/LC_MESSAGES/tutorials/redis.po new file mode 100644 index 00000000..5199c5b1 --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/redis.po @@ -0,0 +1,183 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/redis.rst:4 +msgid "Run Redis on |CL-ATTR|" +msgstr "" + +#: ../../tutorials/redis.rst:6 +msgid "" +"Redis is an in-memory key:value store designed for quick lookups, " +"accessible over the network. In this tutorial, you'll install redis and " +"launch a redis-server on |CL|, plus learn a few basic redis commands. We " +"also invite you to pull our `Clear Linux Redis instance`_ on dockerhub\\*" +" for application or infrastructure development." +msgstr "" + +#: ../../tutorials/redis.rst:12 +msgid "" +"While the `redis data structure store`_ can serve as a NoSQL database for" +" a Web application, it's also easy to integrate in an existing stack. For" +" example, you could use the Redis caching layer for real-time responses " +"on a leaderboard in a gaming app. Redis offers many client libraries with" +" language-specific bindings for Python, Perl, Ruby, and more." +msgstr "" + +#: ../../tutorials/redis.rst:19 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/redis.rst:20 +msgid "Install the `redis-native` bundle in |CL|" +msgstr "" + +#: ../../tutorials/redis.rst:21 +msgid "Install the `containers-basic` bundle in |CL| (only required in Example 2)" +msgstr "" + +#: ../../tutorials/redis.rst:24 +msgid "Install the redis bundle" +msgstr "" + +#: ../../tutorials/redis.rst:26 +msgid "In |CL|, find redis in the `redis-native` bundle." +msgstr "" + +#: ../../tutorials/redis.rst:28 +msgid "Open a Terminal and login as an administrative user." +msgstr "" + +#: ../../tutorials/redis.rst:30 +msgid "Add :file:`redis-native`." +msgstr "" + +#: ../../tutorials/redis.rst:38 +msgid "If the bundle already exists, no action is required." +msgstr "" + +#: ../../tutorials/redis.rst:41 +msgid "Start the redis-server" +msgstr "" + +#: ../../tutorials/redis.rst:43 +msgid "" +"A `systemd` service unit is available to control the redis server. By " +"default, redis runs on port 6379." +msgstr "" + +#: ../../tutorials/redis.rst:46 +msgid "Start the service." +msgstr "" + +#: ../../tutorials/redis.rst:54 +msgid "To stop redis run :command:`systemctl stop redis`." +msgstr "" + +#: ../../tutorials/redis.rst:56 +msgid "Assure the service is running." +msgstr "" + +#: ../../tutorials/redis.rst:62 +msgid "Verify the redis-server sends a reply." +msgstr "" + +#: ../../tutorials/redis.rst:70 +msgid "Expected output: `PONG`." +msgstr "" + +#: ../../tutorials/redis.rst:72 +msgid "" +"Optional: If you wish to apply advanced configuration, copy the " +"`redis.conf` into /etc/ directory." +msgstr "" + +#: ../../tutorials/redis.rst:79 +msgid "The redis-server is now ready to use on |CL|. Try some examples below." +msgstr "" + +#: ../../tutorials/redis.rst:82 +msgid "Example 1: Use the redis-cli and try commands" +msgstr "" + +#: ../../tutorials/redis.rst:84 +msgid "" +"One advantage of redis over other NoSQL databases is that developers can " +"easily access data structures like lists, sets, sorted sets, strings, and" +" hashes using collection operations commands similar to those found in " +"many programming languages. These exercises are inspired by `try redis " +"io`_." +msgstr "" + +#: ../../tutorials/redis.rst:89 +msgid "After your `redis-server` is running, try some basic commands." +msgstr "" + +#: ../../tutorials/redis.rst:91 +msgid "Enter the `redis-cli`. It provides syntax suggestions as you type." +msgstr "" + +#: ../../tutorials/redis.rst:97 +msgid "SET key to hold string value. In the set create connections and increment." +msgstr "" + +#: ../../tutorials/redis.rst:108 +msgid "If the key does not exist or hold a key value, `nil` is returned." +msgstr "" + +#: ../../tutorials/redis.rst:126 +msgid "Create a `friends` list and insert new values at the end of the list." +msgstr "" + +#: ../../tutorials/redis.rst:140 +msgid "Modify `friends` list, using a common slice method with a 0-index." +msgstr "" + +#: ../../tutorials/redis.rst:162 +msgid "" +"Consider using a hash, a very useful data type, which maps string fields " +"and string values, offering multiple lookup methods." +msgstr "" + +#: ../../tutorials/redis.rst:165 +msgid "Enter many user key:values with `HMSET`. Then try `HGET` and `HGETALL`." +msgstr "" + +#: ../../tutorials/redis.rst:185 +msgid "Example 2: Run the |CL| redis docker image" +msgstr "" + +#: ../../tutorials/redis.rst:187 +msgid "" +"We also provide a `Clear Linux Redis instance`_, which is updated " +"continuously and maintained by |CL| development." +msgstr "" + +#: ../../tutorials/redis.rst:203 +msgid "Next Steps" +msgstr "" + +#: ../../tutorials/redis.rst:205 +msgid "Follow the `redis quickstart tutorial`_ to expand potential uses." +msgstr "" + +#: ../../tutorials/redis.rst:207 +msgid "Learn to :ref:`docker`." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/smb/smb-desktop.mo b/locale/de/LC_MESSAGES/tutorials/smb/smb-desktop.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/smb/smb-desktop.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/smb/smb-desktop.po b/locale/de/LC_MESSAGES/tutorials/smb/smb-desktop.po new file mode 100644 index 00000000..179f5bdf --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/smb/smb-desktop.po @@ -0,0 +1,110 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/smb/smb-desktop.rst:4 +msgid "Connect to Windows\\* shared location from |CL-ATTR| desktop" +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:6 +msgid "" +"This tutorial explains how to access an existing shared drive on " +"Windows\\* via Server Message Block (SMB) / Common Internet File System " +"(CIFS) from the |CL| GNOME desktop. CIFS filesystem is generally used to" +" access shared storage locations, or share files." +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:12 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:14 +msgid "You have already `set up a shared location on Windows`_" +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:17 +msgid "Connect to Windows shared location with Nautilus" +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:19 +msgid "From the desktop, select :guilabel:`Files` from the application menu." +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:23 +msgid "GNOME Files is also known as `Nautilus`." +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:25 +msgid "In :guilabel:`Files`, select :guilabel:`Other Locations`." +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:31 +msgid "Figure 1: Files, Other Locations" +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:33 +msgid "" +"In the lower taskbar, beside :guilabel:`Connect to Server`, enter the " +"file-sharing address using the Windows sharing schema:" +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:44 +msgid "Figure 2: Connect to Server" +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:46 +msgid "" +"Optional: If there are issues with DNS, you can use an IP address in " +"place of the `servername` above. You must still specify the share." +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:49 +msgid "" +"Optional: On the Windows machine, in a CLI, retrieve the IP address by " +"entering the command:" +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:58 +msgid "If using the IP address, assure that it is accessible and secure." +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:60 +msgid "Select :guilabel:`Connect`." +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:62 +msgid "The server will request authentication, as shown in Figure 3." +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:68 +msgid "Figure 3: Authentication" +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:70 +msgid "" +"Log in with the same Windows system credentials for which you granted " +"access to the share." +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:73 +msgid "" +"Select the appropriate checkbox to save your credentials. Consider " +"carefully the security risks as a result of your selection." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/smb/smb.mo b/locale/de/LC_MESSAGES/tutorials/smb/smb.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/smb/smb.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/smb/smb.po b/locale/de/LC_MESSAGES/tutorials/smb/smb.po new file mode 100644 index 00000000..3c148d6c --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/smb/smb.po @@ -0,0 +1,152 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/smb/smb.rst:4 +msgid "Enable simple file sharing with a Windows\\* machine using Samba\\*" +msgstr "" + +#: ../../tutorials/smb/smb.rst:6 +msgid "" +"This tutorial describes how to enable simple file sharing from a system " +"running |CL-ATTR| to a Windows machine using Samba. For more advanced " +"sharing, refer to the `Samba guide`_." +msgstr "" + +#: ../../tutorials/smb/smb.rst:11 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/smb/smb.rst:13 +msgid "" +"This tutorial assumes you have installed |CL| on your host system. For " +"detailed instructions, follow the steps in :ref:`bare-metal-install-" +"desktop`." +msgstr "" + +#: ../../tutorials/smb/smb.rst:16 +msgid "" +"Before you install any new packages, update |CL| with the following " +"command:" +msgstr "" + +#: ../../tutorials/smb/smb.rst:24 +msgid "Set up file sharing" +msgstr "" + +#: ../../tutorials/smb/smb.rst:26 +msgid "Log in and get root privileges." +msgstr "" + +#: ../../tutorials/smb/smb.rst:32 +msgid "Add the storage-utils bundle, which includes the Samba binaries." +msgstr "" + +#: ../../tutorials/smb/smb.rst:40 +msgid "The os-clr-on-clr bundle also includes the Samba binaries." +msgstr "" + +#: ../../tutorials/smb/smb.rst:42 +msgid "" +"Create a configuration file called :file:`/etc/samba/smb.conf`. In this " +"example, `[Downloads]` enables a folder share with a specific user. " +"`[Documents]` enables a folder share with any user. The example assumes " +"that a user account `clearlinuxuser` already exists." +msgstr "" + +#: ../../tutorials/smb/smb.rst:47 +msgid "" +"If `valid users` is not specified, then anyone with a user account on the" +" machine and with their Samba password already set can access the folder." +" However, the account is only able to access files and folders for which " +"they have appropriate permissions." +msgstr "" + +#: ../../tutorials/smb/smb.rst:52 +msgid "" +"Use :command:`chown` or :command:`chmod` to change either the owner of " +"the file or the permissions to allow other users to access the file." +msgstr "" + +#: ../../tutorials/smb/smb.rst:72 +msgid "Enable the Samba daemon to start every time." +msgstr "" + +#: ../../tutorials/smb/smb.rst:79 +msgid "" +"Use :command:`smbpasswd` to add the initial password for the user account" +" to access the share. Be aware that Samba maintains its own list of " +"passwords for user accounts. The Samba password list can be different " +"than the password used to log in." +msgstr "" + +#: ../../tutorials/smb/smb.rst:88 +msgid "" +"Setup is complete and a Windows machine on the same network can access " +"the shares. Windows uses the format :file:`\\\\\\\\[server IP or " +"hostname]\\\\folder` to access shares. Access the shares directly with " +"Windows Explorer or by mapping a network drive." +msgstr "" + +#: ../../tutorials/smb/smb.rst:93 +msgid "" +"Use the IP address of the |CL| machine for an easy access method. If the " +"|CL| machine is behind an Active Directory domain controller or a DNS " +"server, use the hostname of the |CL| machine. For other ways to access " +"shares using a hostname instead of an IP address, see `Chapter 7 of the " +"Samba guide`_." +msgstr "" + +#: ../../tutorials/smb/smb.rst:100 +msgid "Map |CL| drive in Windows" +msgstr "" + +#: ../../tutorials/smb/smb.rst:102 +msgid "" +"Open Windows Explorer and click on the left sidebar on :guilabel:`This " +"PC` to change the options available at the top." +msgstr "" + +#: ../../tutorials/smb/smb.rst:105 +msgid "" +"Click the :guilabel:`Map Network Drive` icon and enter the path in the " +"format: :file:`\\\\\\\\[server IP or hostname]\\\\[shared folder]`" +msgstr "" + +#: ../../tutorials/smb/smb.rst:108 +msgid "" +"Check the box :guilabel:`Connect using different credentials`. Enter the " +"Samba user `clearlinuxuser` and the password created with " +":command:`smbpasswd`. See Figure 1 for details." +msgstr "" + +#: ../../tutorials/smb/smb.rst:116 +msgid "Figure 1: Map a network drive in Windows Explorer." +msgstr "" + +#: ../../tutorials/smb/smb.rst:118 +msgid "" +"When complete, Windows Explorer displays the share drive as shown in " +"Figure 2." +msgstr "" + +#: ../../tutorials/smb/smb.rst:124 +msgid "Figure 2: View a share drive in Windows Explorer." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/spark.mo b/locale/de/LC_MESSAGES/tutorials/spark.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/spark.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/spark.po b/locale/de/LC_MESSAGES/tutorials/spark.po new file mode 100644 index 00000000..a73c55c1 --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/spark.po @@ -0,0 +1,176 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/spark.rst:4 +msgid "Set up a standalone cluster system using Apache\\* Spark\\*" +msgstr "" + +#: ../../tutorials/spark.rst:6 +msgid "" +"This tutorial describes how to install, configure, and run Apache Spark " +"on |CL-ATTR|. Apache Spark is a fast general-purpose cluster computing " +"system with the following features:" +msgstr "" + +#: ../../tutorials/spark.rst:10 +msgid "Provides high-level APIs in Java\\*, Scala\\*, Python\\*, and R\\*." +msgstr "" + +#: ../../tutorials/spark.rst:11 +msgid "Includes an optimized engine that supports general execution graphs." +msgstr "" + +#: ../../tutorials/spark.rst:12 +msgid "" +"Supports high-level tools including Spark SQL, MLlib, GraphX, and Spark " +"Streaming." +msgstr "" + +#: ../../tutorials/spark.rst:15 +msgid "" +"In this tutorial, you will install Spark on a single machine running the " +"master daemon and a worker daemon." +msgstr "" + +#: ../../tutorials/spark.rst:19 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/spark.rst:21 +msgid "" +"This tutorial 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 `." +msgstr "" + +#: ../../tutorials/spark.rst:25 +msgid "" +"Before you install any new packages, update |CL| with the following " +"command:" +msgstr "" + +#: ../../tutorials/spark.rst:32 +msgid "Install Apache Spark" +msgstr "" + +#: ../../tutorials/spark.rst:34 +msgid "" +"Apache Spark is included in the :file:`big-data-basic` bundle. To install" +" the framework, enter:" +msgstr "" + +#: ../../tutorials/spark.rst:42 +msgid "Configure Apache Spark" +msgstr "" + +#: ../../tutorials/spark.rst:44 +msgid "Create the configuration directory with the command:" +msgstr "" + +#: ../../tutorials/spark.rst:50 +msgid "" +"Copy the default templates from :file:`/usr/share/defaults/spark` to " +":file:`/etc/spark` with the command:" +msgstr "" + +#: ../../tutorials/spark.rst:57 +msgid "" +"Since |CL| is a stateless system, you should never modify the files under" +" the :file:`/usr/share/defaults` directory. The software updater " +"overwrites those files." +msgstr "" + +#: ../../tutorials/spark.rst:62 +msgid "Copy the template files below to create custom configuration files:" +msgstr "" + +#: ../../tutorials/spark.rst:70 +msgid "" +"Edit the :file:`/etc/spark/spark-env.sh` file and add the " +":envvar:`SPARK_MASTER_HOST` variable. Replace the example address below " +"with your localhost IP address. View your IP address using the " +":command:`hostname -I` command." +msgstr "" + +#: ../../tutorials/spark.rst:79 +msgid "" +"This optional step enables the master's web user interface to view " +"information needed later in this tutorial." +msgstr "" + +#: ../../tutorials/spark.rst:82 +msgid "" +"Edit the :file:`/etc/spark/spark-defaults.conf` file and update the " +"`spark.master` variable with the `SPARK_MASTER_HOST` address and port " +"`7077`." +msgstr "" + +#: ../../tutorials/spark.rst:90 +msgid "Start the master server and a worker daemon" +msgstr "" + +#: ../../tutorials/spark.rst:92 +msgid "Start the master server using:" +msgstr "" + +#: ../../tutorials/spark.rst:98 +msgid "" +"Start one worker daemon and connect it to the master using the " +"`spark.master` variable defined earlier:" +msgstr "" + +#: ../../tutorials/spark.rst:105 +msgid "" +"Open an internet browser and view the worker daemon information using the" +" master's IP address and port `8080`:" +msgstr "" + +#: ../../tutorials/spark.rst:113 +msgid "Run the Spark wordcount example" +msgstr "" + +#: ../../tutorials/spark.rst:115 +msgid "" +"Run the wordcount example using a file on your local host and output the " +"results to a new file with the following command:" +msgstr "" + +#: ../../tutorials/spark.rst:122 +msgid "" +"Open an internet browser and view the application information using the " +"master's IP address and port `8080`:" +msgstr "" + +#: ../../tutorials/spark.rst:129 +msgid "" +"View the results of the wordcount application in the " +":file:`~/Documents/results` file." +msgstr "" + +#: ../../tutorials/spark.rst:131 +msgid "**Congratulations!**" +msgstr "" + +#: ../../tutorials/spark.rst:133 +msgid "" +"You successfully installed and set up a standalone Apache Spark cluster. " +"Additionally, you ran a simple wordcount example." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/tutorial-proxy.mo b/locale/de/LC_MESSAGES/tutorials/tutorial-proxy.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/tutorial-proxy.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/tutorial-proxy.po b/locale/de/LC_MESSAGES/tutorials/tutorial-proxy.po new file mode 100644 index 00000000..4dfdc240 --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/tutorial-proxy.po @@ -0,0 +1,121 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/tutorial-proxy.rst:4 +msgid "Setting up proxy" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:6 +msgid "" +"This tutorial shows you how to configure your system for use behind an " +"outbound proxy to access the Internet." +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:9 +msgid "" +"|CL| :ref:`tooling` applications already benefit from the " +":ref:`autoproxy` feature." +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:17 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:19 +msgid "" +"This tutorial 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 `." +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:24 +msgid "Shells and programs in a desktop session" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:27 +msgid "Terminal" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:29 +msgid "Add the following to your ~/.bashrc:" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:45 +msgid "wget" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:47 +msgid "Run this command to enable downloading from websites from the terminal:" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:59 +msgid "System service (Docker)" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:61 +msgid "" +"For Docker (and other services that use systemd), you can follow these " +"steps to configure and check proxy settings:" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:65 +msgid "Be sure to use :command:`sudo`, as you will need elevated permissions." +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:67 +msgid "" +"Create :file:`/etc/systemd/system/docker.service.d` directory to host " +"configuration information for the Docker service." +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:70 +msgid "" +"Create :file:`/etc/systemd/system/docker.service.d/http-proxy.conf` and " +"add:" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:78 +msgid "Load the changes and restart the service:" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:85 +msgid "Verify that changes have loaded:" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:97 +msgid "" +"This process enables the ability to successfully run ``docker pull``. " +"Containers themselves must be configured independently." +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:101 +msgid "git over ssh" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:103 +msgid "Add the following to your :file:`~/.ssh/config`:" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:114 +msgid "" +"Though netcat is included with Clear Linux, it is not the BSD version, " +"which is the one usually used to enable git over ssh." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/tutorials.mo b/locale/de/LC_MESSAGES/tutorials/tutorials.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/tutorials.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/tutorials.po b/locale/de/LC_MESSAGES/tutorials/tutorials.po new file mode 100644 index 00000000..d31563df --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/tutorials.po @@ -0,0 +1,28 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/tutorials.rst:4 +msgid "Tutorials" +msgstr "" + +#: ../../tutorials/tutorials.rst:6 +msgid "Explore our tutorials to discover what you can do with |CL|!" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/wordpress/web-server-install.mo b/locale/de/LC_MESSAGES/tutorials/wordpress/web-server-install.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/wordpress/web-server-install.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/wordpress/web-server-install.po b/locale/de/LC_MESSAGES/tutorials/wordpress/web-server-install.po new file mode 100644 index 00000000..3987c146 --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/wordpress/web-server-install.po @@ -0,0 +1,547 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/wordpress/web-server-install.rst:4 +msgid "Set up a LAMP web server on |CL-ATTR|" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:6 +msgid "" +"This tutorial provides instructions on how to set up a :abbr:`LAMP " +"(Linux, Apache, MySQL, PHP)` web server on |CL-ATTR| and how to use " +"phpMyAdmin\\* to manage an associated database. Note that this tutorial " +"installs MariaDB\\*, which is a drop-in replacement for MySQL\\*." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:11 +msgid "" +"In order to create a web server using |CL| as the host OS, your host " +"system must be running |CL|. This tutorial assumes you have installed " +"|CL| on your host system. For detailed instructions on installing |CL| on" +" a bare metal system, visit :ref:`bare-metal-install-desktop`." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:16 +msgid "This tutorial covers:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:22 +msgid "Install Apache" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:24 +msgid "" +"Apache is an open source HTTP web server application that can run on " +"several operating systems, including |CL|. Go to the `Apache HTTP Server " +"Project`_ for more information." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:29 +msgid "Install the web-server-basic bundle" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:31 +msgid "" +"The **web-server-basic** bundle contains the packages needed to install " +"the Apache software bundle on |CL|." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:36 +msgid "" +"Before you install new packages, update the |CL| with the following " +"console command:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:43 +msgid "To install the bundle, enter the following command:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:50 +msgid "To start the Apache service, enter the following commands:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:57 +msgid "" +"To verify that the Apache server application is running, open a web " +"browser and navigate to: \\http://localhost." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:60 +msgid "" +"If the service is running, a confirmation message will appear, similar to" +" the message shown in figure 1." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:67 +msgid "`Figure 1: Confirmation that the Apache service is running.`" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:71 +msgid "" +"The :file:`index.html` file is located in the :file:`/var/www/html` " +"directory of your host system. You will copy this file into a new " +"location after you modify the configuration in the next step." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:76 +msgid "Change the default configuration and data directory" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:78 +msgid "" +"|CL| is designed to be a `stateless`_ operating system which means that " +"you must create an optional configuration file to override the default " +"values. The default location of the Apache configuration file, " +":file:`httpd.conf`, is located in the :file:`/usr/share/defaults/httpd` " +"directory. |CL| can override this directory as part of the stateless " +"paradigm. This default :file:`.conf` file includes the following " +"directives that allow for additional locations of configuration " +"definitions:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:94 +msgid "" +"In this section you will define your own httpd.conf file to override the " +"default values, and define a custom DocumentRoot for your web server." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:97 +msgid "Create the directory structure for :file:`/etc/httpd/conf.d`." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:103 +msgid "" +"Create and open the :file:`httpd.conf` file in your new " +":file:`/etc/httpd/conf.d` directory." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:110 +msgid "" +"Add the ``DocumentRoot`` variable to :file:`httpd.conf`. Copy the content" +" listed below into the new :file:`/etc/httpd/conf.d/httpd.conf` file." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:128 +msgid "" +"Create a new ``DocumentRoot`` directory structure and copy the " +":file:`index.html` file from :file:`/var/www/html` directory to " +":file:`/var/www/tutorial`." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:138 +msgid "" +"To ensure a successful setup, edit the new :file:`index.html` file with " +"an obvious change." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:145 +msgid "For example, we changed the default message" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:147 +msgid "\"It works!\"" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:149 +msgid "to" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:151 +msgid "\"It works from its new location!\"" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:153 +#: ../../tutorials/wordpress/web-server-install.rst:171 +msgid "Stop and then restart ``httpd.service``." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:160 +msgid "" +"Go to \\http://localhost to view the new screen. You should see your " +"updated default message from step 5." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:163 +msgid "" +"Change the configuration back to the default :file:`/var/www/html` " +"location. To do this, edit the :file:`/etc/httpd/conf.d/httpd.conf` file " +"again and replace any instance of /var/www/tutorial with /var/www/html." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:178 +msgid "" +"Go to \\http://localhost and verify that you can see the default screen " +"again." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:181 +msgid "Optionally, remove the /var/www/tutorial directory you previously created." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:189 +msgid "Install PHP" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:191 +msgid "" +"An Apache installation allows you to display static web pages. Enabling " +"PHP allows you to generate and display dynamic web pages. To add this " +"functionality to your web server, install PHP on your system." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:195 +msgid "To get the php components, enter the following command:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:201 +msgid "To enable PHP, enter the following commands:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:209 +msgid "After restarting the Apache service, test your PHP installation." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:211 +msgid "" +"Create and open a file named :file:`phpinfo.php` in the " +":file:`/var/www/html/` directory using a text editor." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:218 +msgid "Add the following line to the file:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:224 +msgid "Go to \\http://localhost/phpinfo.php." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:226 +msgid "Verify that the PHP information screen appears, similar to figure 2:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:232 +msgid "`Figure 2: The PHP information screen.`" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:234 +msgid "" +"If the PHP information screen is displayed, you have successfully " +"installed the PHP components and are now ready to add your database " +"application to complete your LAMP server implementation." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:239 +msgid "Install MariaDB" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:241 +msgid "" +"Install MariaDB to store content. MariaDB is a drop-in replacement for " +"MySQL and is available in the database-basic |CL| bundle." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:244 +msgid "To install the database-basic bundle, enter the following command:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:250 +msgid "To start MariaDB after it is installed, enter the following commands:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:257 +msgid "To check the status of MariaDB, enter the following command:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:263 +msgid "Press :kbd:`Ctrl` + :kbd:`c` or :kbd:`q` to exit." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:266 +msgid "Security hardening" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:268 +msgid "" +"With the MariaDB service running, we can perform some basic security " +"hardening." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:271 +msgid "To add a basic layer of security, enter the following command:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:277 +msgid "Respond to the questions that appear in the script below." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:281 +msgid "Our suggested responses follow each question." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:287 +msgid "" +"In order to secure MariaDB, we need the current password for the root " +"user. For a newly installed MariaDB without a set root password, the " +"password is blank. Thus, press enter to continue." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:299 +msgid "" +"Set the root password to prevent unauthorized MariaDB root user logins. " +"To set a root password, type 'y'." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:306 +msgid "Type the desired password for the root user." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:312 +msgid "Re-type the desired password for the root user." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:322 +msgid "" +"By default, a MariaDB installation includes an anonymous user that allows" +" anyone to log in to MariaDB without a user account. This anonymous user " +"is intended only for testing and for a smoother installation. To remove " +"the anonymous user and make your database more secure, type 'y'." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:332 +msgid "" +"Normally, root should only be allowed to connect from the 'localhost'. " +"This ensures that someone cannot guess the root password from the " +"network. To block any remote root login, type 'y'." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:341 +msgid "" +"By default, MariaDB includes a database named 'test' which anyone can " +"access. This database is also intended only for testing and should be " +"removed. To remove the test database, type 'y'." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:353 +msgid "" +"Reloading the privilege tables ensures all changes made so far take " +"effect immediately. To reload the privilege tables, type 'y'." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:362 +msgid "" +"All done! If you've completed all of the above steps, your MariaDB " +"installation should now be secure." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:365 +msgid "Thanks for using MariaDB!" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:367 +msgid "" +"The MariaDB installation is complete, and we can now install phpMyAdmin " +"to manage the databases." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:371 +msgid "Install phpMyAdmin" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:373 +msgid "" +"The web-based tool phpMyAdmin is a straightforward way to manage MySQL or" +" MariaDB databases. Visit the `phpMyAdmin`_ website for the complete " +"discussion regarding phpMyAdmin, its documentation, the latest downloads," +" and other useful information." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:378 +msgid "In this tutorial, we use the latest English version of phpMyAdmin." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:380 +msgid "" +"Download the :file:`phpMyAdmin--english.tar.gz` file to your " +":file:`~/Downloads` directory. Here, refers to the current " +"version available at https://www.phpmyadmin.net/downloads." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:386 +msgid "This example downloads and uses version 4.6.4." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:388 +msgid "" +"Once the file has been successfully downloaded and verified, decompress " +"the file and directories into the Apache web server document root " +"directory. Use the following commands:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:397 +msgid "" +"To keep things simple, rename the newly created " +":file:`phpMyAdmin-4.6.4-english` directory to :file:`phpMyAdmin` with the" +" following command:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:406 +msgid "Use phpMyAdmin to manage a database" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:408 +msgid "" +"You can use the phpMyAdmin web-based tool to manage your databases. " +"Follow the steps below for setting up a database called \"WordPress\"." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:411 +msgid "" +"Verify that a successful installation of all LAMP server components by " +"going to \\http://localhost/phpMyAdmin. See figure 3." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:414 +msgid "" +"Log in with your root userid and the password you set up when you ran the" +" :ref:`mysql_secure_installation command `. Enter your " +"credentials and select :guilabel:`Go` to log in:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:422 +msgid "`Figure 3: The phpMyAdmin login page.`" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:424 +msgid "" +"Verify a successful login by confirming that the main phpMyAdmin page " +"displays, as shown in figure 4:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:431 +msgid "`Figure 4: The phpMyAdmin dashboard.`" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:433 +msgid "" +"Set up a database by selecting the :guilabel:`Databases` tab, as shown in" +" figure 5." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:436 +msgid "" +"Enter `WordPress` in the text field below the :guilabel:`Create database`" +" label." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:439 +msgid "" +"Select the :guilabel:`utf8_unicode_ci` option from the " +":guilabel:`Collation` drop-down menu beside the text field." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:442 +msgid "Click :guilabel:`Create`." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:448 +msgid "`Figure 5: The Databases tab.`" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:450 +msgid "" +"Set up user permissions by selecting the :guilabel:`WordPress` database " +"located in the left panel. See figure 6." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:453 +msgid "Select the :guilabel:`Privileges` tab. Figure 6 shows its contents." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:459 +msgid "`Figure 6: The Privileges tab.`" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:461 +msgid "" +"Click :guilabel:`Add user account` located at the bottom of the " +":guilabel:`Privileges` tab. The `Add user account` page appears, as shown" +" in figure 7." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:469 +msgid "`Figure 7: The User accounts tab.`" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:471 +msgid "" +"Enter the following information in the corresponding fields that appear " +"in figure 7 above:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:474 +msgid "User name: wordpressuser" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:476 +msgid "Password: wp-example" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:478 +msgid "Re-type: wp-example" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:480 +msgid "" +"In the `Database for user account` section, select :guilabel:`Grant all " +"privileges on database “WordPress”.`" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:483 +msgid "At the bottom of the page, click :guilabel:`Go`." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:485 +msgid "If successful, you should see the screen shown in figure 8:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:491 +msgid "`Figure 8: The user wordpressuser is successfully added.`" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:493 +msgid "**Congratulations!**" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:495 +msgid "" +"You have now created a fully functional LAMP server along with a " +"WordPress\\*-ready database using |CL|." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:499 +msgid "Next steps" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:501 +msgid "" +"Next, add the WordPress components needed to host a WordPress website " +"with :ref:`wp-install`." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/wordpress/wordpress.mo b/locale/de/LC_MESSAGES/tutorials/wordpress/wordpress.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/wordpress/wordpress.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/wordpress/wordpress.po b/locale/de/LC_MESSAGES/tutorials/wordpress/wordpress.po new file mode 100644 index 00000000..78f37045 --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/wordpress/wordpress.po @@ -0,0 +1,51 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/wordpress/wordpress.rst:4 +msgid "WordPress\\* on |CL-ATTR|" +msgstr "" + +#: ../../tutorials/wordpress/wordpress.rst:6 +msgid "" +"This tutorial describes how to setup a web server to host a WordPress\\* " +"site on a |CL-ATTR| system. The tutorial is split into two sections:" +msgstr "" + +#: ../../tutorials/wordpress/wordpress.rst:9 +msgid ":ref:`web-server-install`" +msgstr "" + +#: ../../tutorials/wordpress/wordpress.rst:11 +msgid ":ref:`wp-install`" +msgstr "" + +#: ../../tutorials/wordpress/wordpress.rst:13 +msgid "" +"If you already have a |CL| based :abbr:`LAMP (Linux, Apache, MySQL, PHP)`" +" web server, you can skip ahead to the second section of this tutorial." +msgstr "" + +#: ../../tutorials/wordpress/wordpress.rst:18 +msgid "" +"This tutorial is for development and testing purposes only. Additional " +"steps are required to secure production systems. Those steps are beyond " +"the scope of this tutorial." +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/wordpress/wp-install.mo b/locale/de/LC_MESSAGES/tutorials/wordpress/wp-install.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/wordpress/wp-install.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/wordpress/wp-install.po b/locale/de/LC_MESSAGES/tutorials/wordpress/wp-install.po new file mode 100644 index 00000000..243b1128 --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/wordpress/wp-install.po @@ -0,0 +1,293 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/wordpress/wp-install.rst:4 +msgid "Set up WordPress\\* on a LAMP web server" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:6 +msgid "" +"This tutorial shows you how to install the WordPress\\* components on " +"your |CL| :abbr:`LAMP (Linux, Apache, MySQL, PHP)` server. At the end of " +":ref:`web-server-install`, you created a WordPress-ready database using " +"phpMyAdmin\\* and MariaDB\\*. Now that the LAMP server is up and running," +" you can add the WordPress components needed to host a WordPress website " +"on your system." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:13 +msgid "Before you begin" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:15 +msgid "" +"This tutorial assumes that you have successfully completed :ref:`bare-" +"metal-install-desktop` and you have :ref:`web-server-install`." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:19 +msgid "Create a WordPress server" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:21 +msgid "" +"WordPress can be installed in a variety of ways. These instructions are " +"written for users who have followed our instructions for installing " +"phpMyAdmin when they :ref:`set up a LAMP web server `. Note that all steps in this tutorial have been tested using a " +"NUC6i5SYH Intel® NUC. Visit the `NUC6i5SYH product page`_ for detailed " +"information." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:27 +msgid "" +"Numerous online articles are available to help you name your website and " +"acquire the necessary certificates. Those tasks are beyond the scope of " +"this tutorial." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:30 +msgid "" +"You can take several actions to harden your website from attacks. The " +"security of your website and the data it contains are complex and ever-" +"evolving tasks. Prioritize security if you plan to expose your website to" +" the outside world. This tutorial does not address security measures that" +" you can take to harden your site but we strongly encourage you to take " +"action." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:38 +msgid "" +"Throughout this tutorial, we reference your website name as " +"." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:42 +msgid "Download WordPress and manage directories" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:44 +msgid "" +"For this tutorial, you will create a WordPress blog that can be accessed " +"at: \\http:///blog." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:47 +msgid "" +"To accomplish this setup, you must add WordPress components to the " +":file:`/var/www/html/blog` directory." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:50 +msgid "Follow these steps:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:53 +msgid "Navigate to the top level of the website’s root directory:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:59 +msgid "Download the latest version of WordPress:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:65 +msgid "Extract all files and directories from the downloaded file:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:71 +msgid "Rename the top-level WordPress directory to “blog”:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:77 +msgid "Remove the downloaded tar file:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:84 +msgid "Set up WordPress with web-based GUI" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:86 +msgid "" +"Recall that you created a database and user when you installed phpMyAdmin" +" when you set up a |CL| based :ref:`web server `. " +"Next, you must connect WordPress to the database and install WordPress." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:90 +msgid "" +"To continue with the setup, go to: \\http:///blog/wp-" +"admin/install.php. The WordPress language option screen appears, as shown" +" in figure 1." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:93 +msgid "Select :guilabel:`English` and click :guilabel:`Continue`." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:99 +msgid "`Figure 1: WordPress language selection screen.`" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:102 +msgid "" +"The WordPress installation continues until the Welcome screen appears, as" +" shown in figure 2:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:109 +msgid "`Figure 2: WordPress Welcome screen.`" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:111 +msgid "Click :guilabel:`Let’s go!`." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:113 +msgid "" +"Enter database connection specifics in the screen that appears, as shown " +"in figure 3 below." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:116 +msgid "Database name: WordPress" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:117 +msgid "Database username: wordpressuser" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:118 +msgid "" +"Database password: wp-example (asterisks will not appear in the text " +"box)" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:119 +msgid "Database host: localhost" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:120 +msgid "Table prefix: wp\\_" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:126 +msgid "" +"`Figure 3: Information necessary for WordPress to connect to the " +"database.`" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:128 +msgid "Click :guilabel:`Submit` to complete the setup." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:130 +msgid "" +"Figure 4 shows the confirmation screen that verifies a successful setup. " +"WordPress is connected to the MariaDB database." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:137 +msgid "`Figure 4: Successful WordPress connection.`" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:139 +msgid "" +"Click :guilabel:`Run the install`. The installer runs until WordPress is " +"fully installed on your system." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:143 +msgid "Complete successful login" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:145 +msgid "" +"Once the installation is complete, you can name your blog and create a " +"WordPress username and password. See figure 5." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:152 +msgid "`Figure 5: WordPress site information screen.`" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:155 +msgid "Enter all required information." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:156 +msgid "Click :guilabel:`Install WordPress`." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:157 +msgid "" +"Verify that the initial login screen appears once the installation is " +"complete. See figure 6:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:163 +msgid "`Figure 6: The WordPress login screen.`" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:165 +msgid "Enter your WordPress username and password." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:166 +msgid "Check :guilabel:`Remember me` to save your credentials." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:167 +msgid "Click :guilabel:`Log in`." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:169 +msgid "Figure 7 shows the WordPress dashboard after a successful login:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:175 +msgid "`Figure 7: The WordPress dashboard.`" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:177 +msgid "You are ready to go!" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:179 +msgid "" +"To check out your blog as it is seen by the outside world, enter: " +"\\http:///blog on your browser. Figure 8 shows the result:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:186 +msgid "`Figure 8: Your WordPress blog.`" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:188 +msgid "**Congratulations, your WordPress blog is up and running!**" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:190 +msgid "You have successfully installed WordPress on a host system." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:192 +msgid "Add new entries to your blog and share them with the world using |CL|!" +msgstr "" + diff --git a/locale/de/LC_MESSAGES/tutorials/yubikey-u2f.mo b/locale/de/LC_MESSAGES/tutorials/yubikey-u2f.mo new file mode 100644 index 00000000..785d7c82 Binary files /dev/null and b/locale/de/LC_MESSAGES/tutorials/yubikey-u2f.mo differ diff --git a/locale/de/LC_MESSAGES/tutorials/yubikey-u2f.po b/locale/de/LC_MESSAGES/tutorials/yubikey-u2f.po new file mode 100644 index 00000000..5f511f39 --- /dev/null +++ b/locale/de/LC_MESSAGES/tutorials/yubikey-u2f.po @@ -0,0 +1,159 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/yubikey-u2f.rst:4 +msgid "Enable YubiKey U2F Support" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:6 +msgid "" +"YubiKey\\* is a USB security token manufactured by `Yubico`_. Depending " +"on the model, a YubiKey can support different authentication protocols " +"including: One-Time Password (OTP), Smart card, FIDO2, and Universal 2nd " +"Factor (U2F)." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:10 +msgid "" +"These instructions will go over configuring a YubiKey for U2F " +"authentication through a web browser on a |CL-ATTR| system." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:13 +msgid "" +"A list of `websites accepting U2F authentication with the YubiKey`_ is " +"available on the Yubico website. See the Yubico website to learn more " +"about the Yubikey: https://www.yubico.com/getstarted/meet-the-yubikey/" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:26 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:28 +msgid "This tutorial assumes you have:" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:30 +msgid "|CL| installed and running." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:32 +msgid "Mozilla Firefox installed on |CL|." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:34 +msgid "A YubiKey." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:39 +msgid "Enable Linux udev rules for YubiKey" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:41 +msgid "" +":command:`udev` is the Linux device manager which handles events when USB" +" devices are added and removed. Custom rules needs to be created to " +"properly identify the YubiKey and provide applications access." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:45 +msgid "" +"These instructions are derived from: `Yubico support article Using Your " +"U2F YubiKey with Linux " +"`_" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:50 +msgid "Create the udev rules folder under :file:`/etc`" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:57 +msgid "Download the u2f rules from the Yubico GitHub:" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:64 +msgid "" +"Move the downloaded :file:`70-u2f.rules` file into the :file:`/etc/udev` " +"folder" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:72 +msgid "" +"The udev rules should automatically be reloaded. However, they can be " +"manually reloaded or reboot the system:" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:80 +msgid "Plugin and validate the YubiKey appears as a USB device:" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:89 +msgid "Enable U2F in Mozilla Firefox" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:91 +msgid "" +"Firefox comes with U2F web authentication support disabled by default. " +"U2F needs to be enabled in the advanced settings." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:94 +msgid "" +"These instructions are derived from: `Yubico support article Enabling U2F" +" support in Mozilla Firefox " +"`_" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:99 +msgid "Launch Mozilla Firefox" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:101 +msgid "" +"In the URL bar, type :command:`about:config` to access the advanced " +"settings." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:108 +msgid "Click the *I accept the risk!* button to continue to the advanced settings" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:110 +msgid "" +"Search for the :command:`security.webauth.u2f` and double-click it so " +"*Value* becomes **true**." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:114 +msgid "" +"Your YubiKey is now usable on |CL| with Mozilla Firefox with websites " +"that support U2F authentication." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:119 +msgid "Related topics" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:121 +msgid "|CL| :ref:`security`" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/FAQ/faq.po b/locale/zh_CN/LC_MESSAGES/FAQ/faq.po new file mode 100644 index 00000000..4ad15c47 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/FAQ/faq.po @@ -0,0 +1,275 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../FAQ/faq.rst:4 +msgid "FAQ" +msgstr "" + +#: ../../FAQ/faq.rst:6 +msgid "" +"Below is a list of commonly asked questions with answers sourced from the" +" |CL-ATTR| team and `Clear Linux community forums`_." +msgstr "" + +#: ../../FAQ/faq.rst:14 +msgid "General" +msgstr "" + +#: ../../FAQ/faq.rst:17 +msgid "Why did you make another distro?" +msgstr "" + +#: ../../FAQ/faq.rst:19 +msgid "" +"The |CL| team felt that performance was left on the table with Linux " +"software. |CL| takes a holistic approach to improving performance across " +"the stack. We also wanted to take more modern approaches with OS updates " +"and tooling." +msgstr "" + +#: ../../FAQ/faq.rst:26 +msgid "Can other distros copy |CL| improvements?" +msgstr "" + +#: ../../FAQ/faq.rst:28 +msgid "Yes, we absolutely love open source reuse and upstreaming improvements." +msgstr "" + +#: ../../FAQ/faq.rst:33 +msgid "How often do you update?" +msgstr "" + +#: ../../FAQ/faq.rst:35 +msgid "" +"The |CL| team puts out multiple releases a week, often releasing 2 or " +"more times a day. This rolling release approach allows |CL| to remain " +"agile to upstream changes and security patches." +msgstr "" + +#: ../../FAQ/faq.rst:42 +msgid "Is telemetry required?" +msgstr "" + +#: ../../FAQ/faq.rst:44 +msgid "" +"The telemetry solution provided by |CL| is entirely optional and " +"customizable. It is disabled by default. If you do choose to enable " +"telemetry, the data helps the |CL| team proactively identify and resolve " +"bugs. See the :ref:`telemetry ` page for more " +"information." +msgstr "" + +#: ../../FAQ/faq.rst:52 +msgid "What is the default firewall?" +msgstr "" + +#: ../../FAQ/faq.rst:54 +msgid "" +"|CL| packages :command:`iptables` as a bundle, however, there are no " +"default firewall rules. All network traffic is allowed by default." +msgstr "" + +#: ../../FAQ/faq.rst:60 +msgid "Where are the files that I usually see under /etc like fstab?" +msgstr "" + +#: ../../FAQ/faq.rst:62 +msgid "" +"|CL| has a stateless design that maintains a separation between system " +"files and user files. Default values are stored under " +":file:`/usr/share/defaults/`. Files under :file:`/etc/` are not created " +"unless you create one." +msgstr "" + +#: ../../FAQ/faq.rst:66 +msgid "" +"A blog post explaining how this is accomplished with :file:`/etc/fstab/` " +"specifically is available here: https://clearlinux.org/news-blogs/where-" +"etcfstab-clear-linux" +msgstr "" + +#: ../../FAQ/faq.rst:73 +msgid "Software packages" +msgstr "" + +#: ../../FAQ/faq.rst:76 +msgid "How is software installed and updated?" +msgstr "" + +#: ../../FAQ/faq.rst:78 +msgid "" +"|CL| provides software in the form of :ref:`bundles ` and " +"updates software with :ref:`swupd `." +msgstr "" + +#: ../../FAQ/faq.rst:81 +msgid "" +":ref:`FlatPak\\* ` is an application virtualization solution " +"that allows more software to be available to |CL| users by augmenting the" +" software |CL| packages natively with software available through FlatPak." +msgstr "" + +#: ../../FAQ/faq.rst:85 +msgid "" +"Our goal is to have software packaged natively and made available through" +" bundles whenever possible." +msgstr "" + +#: ../../FAQ/faq.rst:91 +msgid "Does |CL| use RPMs like other distros?" +msgstr "" + +#: ../../FAQ/faq.rst:93 +msgid "" +"|CL| provides software in the form of :ref:`bundles `. The" +" RPM format is used as an intermediary step for packaging and determining" +" software dependencies at OS build time." +msgstr "" + +#: ../../FAQ/faq.rst:97 +msgid "" +"Individual RPMs can sometimes be manually installed on a |CL| system with" +" the right tools, but that is not the intended use case." +msgstr "" + +#: ../../FAQ/faq.rst:103 +msgid "Can I install a software package from another OS on |CL|?" +msgstr "" + +#: ../../FAQ/faq.rst:105 +msgid "" +"Software that is packaged in other formats for other Linux distributions " +"is not guaranteed to work on |CL| and may be impacted by |CL| updates." +msgstr "" + +#: ../../FAQ/faq.rst:108 +msgid "" +"If the software you're seeking is open source, please submit a request to" +" add it to |CL|. Submit requests on GitHub\\* here: " +"https://github.com/clearlinux/distribution/issues" +msgstr "" + +#: ../../FAQ/faq.rst:115 +msgid "Software availability" +msgstr "" + +#: ../../FAQ/faq.rst:118 +msgid "What software is available on |CL|?" +msgstr "" + +#: ../../FAQ/faq.rst:120 +msgid "" +"Available software can be found in the `Software Store`_, through the " +"GNOME\\* Software application on the desktop, or by using :ref:`swupd " +"search `." +msgstr "" + +#: ../../FAQ/faq.rst:126 +msgid "Is Google\\* Chrome\\* available?" +msgstr "" + +#: ../../FAQ/faq.rst:128 +msgid "" +"The Google Chrome web browser is not distributed as a bundle in |CL| due " +"to copyright and licensing complexities." +msgstr "" + +#: ../../FAQ/faq.rst:131 +msgid "" +"A discussion on manually installing and maintaining Google Chrome can be " +"found on GitHub: https://github.com/clearlinux/distribution/issues/422" +msgstr "" + +#: ../../FAQ/faq.rst:137 +msgid "Is FFmpeg available?" +msgstr "" + +#: ../../FAQ/faq.rst:139 +msgid "" +"`FFmpeg`_ is a multimedia software suite, which is commonly used for " +"various media encoding/decoding, streaming, and playback." +msgstr "" + +#: ../../FAQ/faq.rst:142 +msgid "" +"|CL| does not distribute FFmpeg due to well-known licensing and legal " +"complexities (See https://www.ffmpeg.org/legal.html and " +"http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html)." +msgstr "" + +#: ../../FAQ/faq.rst:146 +msgid "" +"Read more in the |CL| repository, including discussion of an alternative " +"hardware-based solution: " +"https://github.com/clearlinux/distribution/issues/429." +msgstr "" + +#: ../../FAQ/faq.rst:150 +msgid "" +"While |CL| cannot distribute FFmpeg, a manual solution to build and " +"install FFmpeg under :file:`/usr/local` has been shared on the community " +"forums: https://community.clearlinux.org/t/how-to-h264-etc-support-for-" +"firefox-including-ffmpeg-install." +msgstr "" + +#: ../../FAQ/faq.rst:157 +msgid "Is ZFS\\* available?" +msgstr "" + +#: ../../FAQ/faq.rst:159 +msgid "" +"ZFS is not available with |CL| because of copyright and licensing " +"complexities. BTRFS is an alternative filesystem that is available in " +"|CL| natively." +msgstr "" + +#: ../../FAQ/faq.rst:163 +msgid "" +"A user on GitHub notes that the ZFS kernel module can be compiled, built," +" and installed manually: " +"https://github.com/clearlinux/distribution/issues/631" +msgstr "" + +#: ../../FAQ/faq.rst:169 +msgid "Can you add a driver that I need?" +msgstr "" + +#: ../../FAQ/faq.rst:171 +msgid "" +"If a kernel module is available as part of the Linux kernel source tree " +"but not enabled in the |CL| kernels, in many cases the |CL| team will " +"enable it upon request. Submit requests on GitHub here: " +"https://github.com/clearlinux/distribution/issues" +msgstr "" + +#: ../../FAQ/faq.rst:176 +msgid "" +"The |CL| team does not typically add out-of-tree kernel modules as a " +"matter of practice because of the maintenance overhead. If the driver was" +" unable to be merged upstream, there is a good chance we may be unable to" +" merge it for similar reasons." +msgstr "" + +#: ../../FAQ/faq.rst:181 +msgid "" +"Kernel modules can be individually built and installed on |CL|. See the " +":ref:`kernel modules ` page for more information." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/concepts/autospec-about.po b/locale/zh_CN/LC_MESSAGES/concepts/autospec-about.po new file mode 100644 index 00000000..21a344d0 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/concepts/autospec-about.po @@ -0,0 +1,219 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" + +#: ../../concepts/autospec-about.rst:12 +msgid "How autospec works" +msgstr "" + +#: ../../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 `." +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 "" + diff --git a/locale/zh_CN/LC_MESSAGES/concepts/bundles-about.po b/locale/zh_CN/LC_MESSAGES/concepts/bundles-about.po new file mode 100644 index 00000000..48be697c --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/concepts/bundles-about.po @@ -0,0 +1,71 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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/bundles-about.rst:4 +msgid "Bundles" +msgstr "" + +#: ../../concepts/bundles-about.rst:6 +msgid "" +"Linux-based operating systems contain the code of several hundred, if not" +" thousands, of open source projects. To make this manageable, " +"distributions use a concept called \"packages\" to configure and compile " +"the source code of these projects into binaries." +msgstr "" + +#: ../../concepts/bundles-about.rst:11 +msgid "" +"Many distributions then split the content of these compiled packages into" +" so-called sub-packages, which are the granularity at which these " +"distributions deploy their software. With those kinds of distributions, " +"system administrators can then install and update sub-packages " +"individually or as a set, using tools such as \"yum\" and \"apt-get.\"" +msgstr "" + +#: ../../concepts/bundles-about.rst:17 +msgid "" +"The |CL-ATTR| takes a slightly different approach. While we also use the " +"concept of packages to manage compiling source code into binaries, we do " +"not use the package concept to deploy software. Instead, we provide " +"software \"bundles\" that are installed and managed using :ref:`swupd" +"`. Each bundle contains as many or as few open source " +"projects needed to provide a complete functionality." +msgstr "" + +#: ../../concepts/bundles-about.rst:24 +msgid "Next steps" +msgstr "" + +#: ../../concepts/bundles-about.rst:26 +msgid "To put this concept into practice, see the following resources:" +msgstr "" + +#: ../../concepts/bundles-about.rst:28 +msgid ":ref:`bundles`" +msgstr "" + +#: ../../concepts/bundles-about.rst:29 +msgid ":ref:`bundle-commands`" +msgstr "" + +#: ../../concepts/bundles-about.rst:30 +msgid ":ref:`compatible-kernels`" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/concepts/mixer-about.po b/locale/zh_CN/LC_MESSAGES/concepts/mixer-about.po new file mode 100644 index 00000000..58d238c7 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/concepts/mixer-about.po @@ -0,0 +1,115 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" + diff --git a/locale/zh_CN/LC_MESSAGES/concepts/restart.po b/locale/zh_CN/LC_MESSAGES/concepts/restart.po new file mode 100644 index 00000000..afb3649d --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/concepts/restart.po @@ -0,0 +1,301 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" + diff --git a/locale/zh_CN/LC_MESSAGES/concepts/security.po b/locale/zh_CN/LC_MESSAGES/concepts/security.po new file mode 100644 index 00000000..87326a37 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/concepts/security.po @@ -0,0 +1,249 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" + diff --git a/locale/zh_CN/LC_MESSAGES/concepts/stateless.po b/locale/zh_CN/LC_MESSAGES/concepts/stateless.po new file mode 100644 index 00000000..976be398 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/concepts/stateless.po @@ -0,0 +1,202 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 `.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? `_" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/concepts/swupd-about.po b/locale/zh_CN/LC_MESSAGES/concepts/swupd-about.po new file mode 100644 index 00000000..0624a47a --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/concepts/swupd-about.po @@ -0,0 +1,193 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 `." +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 ` 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 ` 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 "" + diff --git a/locale/zh_CN/LC_MESSAGES/concepts/telemetry-about.po b/locale/zh_CN/LC_MESSAGES/concepts/telemetry-about.po new file mode 100644 index 00000000..f5ba1195 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/concepts/telemetry-about.po @@ -0,0 +1,176 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" + diff --git a/locale/zh_CN/LC_MESSAGES/disclaimers.po b/locale/zh_CN/LC_MESSAGES/disclaimers.po new file mode 100644 index 00000000..46d60de2 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/disclaimers.po @@ -0,0 +1,32 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" + diff --git a/locale/zh_CN/LC_MESSAGES/documentation_license.po b/locale/zh_CN/LC_MESSAGES/documentation_license.po new file mode 100644 index 00000000..cfdc38ce --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/documentation_license.po @@ -0,0 +1,20 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + diff --git a/locale/zh_CN/LC_MESSAGES/get-started/bare-metal-install-desktop/bare-metal-install-desktop.po b/locale/zh_CN/LC_MESSAGES/get-started/bare-metal-install-desktop/bare-metal-install-desktop.po new file mode 100644 index 00000000..41244d23 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/get-started/bare-metal-install-desktop/bare-metal-install-desktop.po @@ -0,0 +1,745 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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/bare-metal-install-desktop/bare-metal-install-desktop.rst:4 +msgid "Install |CL-ATTR| from the live desktop" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:6 +msgid "" +"The live desktop allows you to boot |CL-ATTR| in a GNOME desktop without " +"modifying the host system, offering the chance to explore developing on " +"|CL|. Better yet, launch the |CL| installer to install on your target " +"system." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:15 +msgid "System requirements" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:17 +msgid "Assure that your target system supports the installation:" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:19 +msgid ":ref:`system-requirements`" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:20 +msgid ":ref:`compatibility-check`" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:23 +msgid "Preliminary steps" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:25 +msgid "`Visit our Downloads page`_." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:27 +msgid "Download the file :file:`clear--live-desktop.iso`" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:31 +msgid " is the latest |CL| auto-numbered release." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:33 +msgid "Follow your OS instructions to create a bootable USB drive." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:35 +msgid ":ref:`bootable-usb`" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:40 +msgid "Install from live image" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:42 +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:45 +msgid "Insert the USB drive into an available USB slot." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:47 +msgid "Power on the system." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:49 +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:52 +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:55 +msgid "Save these settings, e.g. :kbd:`F10`, and exit." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:57 +msgid "Reboot the target system." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:59 +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:65 +msgid "Figure 1: Clear Linux OS in boot menu" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:70 +msgid "Confirm network connection" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:72 +msgid "" +"Confirm there is a network connection before launching the installer. " +"Choose a method: `Wired Connection`, or `WiFi Connected`. This guide " +"shows an example of a **Wired Connection**." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:76 +msgid "" +"In the upper right of the top menu bar, select the square icon to view " +"Network settings, shown in Figure 2." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:79 +msgid "Select :guilabel:`Wired Connected` and then :guilabel:`Wired Settings`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:85 +msgid "Figure 2: Software icon, Network settings" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:87 +msgid "" +"View the :guilabel:`Wired` menu to assure that you're target system and " +"installer are connected to a network." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:90 +msgid "Optional: Configure Proxy settings." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:92 +msgid "To view :guilabel:`Network Proxy`, select its :guilabel:`Gear` icon." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:94 +msgid "Select from `Automatic`, `Manual` or `Disabled` as desired." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:96 +msgid "Close the dialogue box." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:98 +msgid "Select the :guilabel:`Gear` icon to view Network settings." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:100 +msgid "" +"If desired, select :guilabel:`Connect automatically`. Select other " +"options as desired." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:103 +msgid "Select :guilabel:`Apply` button to confirm change to settings." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:106 +msgid "Software" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:108 +msgid "" +"Optional: Explore |CL| bundles and other software available. Double-click" +" the :guilabel:`Software` icon from the Activities menu, shown in Figure " +"2." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:112 +msgid "" +"`Sofware` application is *only intended for exploring* available bundles," +" applications, and images. Do not attempt to install them." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:115 +msgid "Assure there is a network connection before launching `Software`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:118 +msgid "Launch the |CL| installer" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:120 +msgid "" +"After the live desktop image boots, find the |CL| icon in the " +":guilabel:`Activities` menu at left, shown in Figure 3." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:123 +msgid "Click the icon, :guilabel:`Install Clear Linux OS`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:129 +msgid "Figure 3: Install Clear Linux OS icon" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:131 +msgid "The installer is launched, as shown in Figure 4." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:137 +msgid "Figure 4: |CL| OS Desktop Installer" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:139 +msgid "" +"In :guilabel:`Select Language`, select a language from the options, or " +"type your preferred language in the search bar." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:142 +msgid "Select :guilabel:`Next`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:148 +msgid "Minimum installation requirements" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:150 +msgid "" +"To fulfill minimum installation requirements, complete the `Required " +"options`_. We also recommend completing `Advanced options`_." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:155 +msgid "" +"The :kbd:`Install` button is only highlighted **after** you complete " +"`Required options`_." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:158 +msgid "Checkmarks indicate a selection has been made." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:160 +msgid "" +"An Internet connection is required. You may want to launch a browser " +"prior to installation to verify your Internet connection." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:164 +msgid "|CL| Desktop Installer" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:166 +msgid "" +"The |CL| Desktop Installer Main Menu appears as shown in Figure 5. To " +"meet the minimum requirements, enter values in all submenus for the " +":guilabel:`Required options`. After you complete them, your selections " +"appear below submenus and a checkmark appears at right." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:175 +msgid "Figure 5: Clear Linux OS Desktop Installer - Main Menu" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:178 +msgid "Navigation" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:180 +msgid "Use the :kbd:`mouse` to navigate or select options." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:182 +msgid "" +"Use :kbd:`Tab` key to navigate between :guilabel:`Required options` and " +":guilabel:`Advanced options`" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:185 +msgid "Use :kbd:`Up` or :kbd:`Down` arrow keys to navigate submenu list." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:187 +msgid "Select :kbd:`Confirm`, or :kbd:`Cancel` in submenus." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:190 +msgid "Required options" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:193 +msgid "Select Time Zone" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:195 +msgid "" +"From the Main Menu, select :guilabel:`Select Time Zone`. `UTC` is " +"selected by default." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:198 +msgid "" +"In :guilabel:`Select Time Zone`, navigate to the desired time zone. Or " +"start typing the region and then city. (.e.g., " +":file:`America/Los_Angeles`)." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:202 +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:218 +msgid "Select :guilabel:`Confirm`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:208 +msgid "Figure 6: Select System Time Zone" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:211 +msgid "Select Keyboard" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:213 +msgid "From the Main Menu, select :guilabel:`Select Keyboard`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:215 +msgid "" +"Navigate to your desired keyboard layout. We select \"us\" for the United" +" States." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:224 +msgid "Figure 7: Select Keyboard menu" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:227 +msgid "Select Installation Media" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:229 +msgid "From the Main Menu, select :guilabel:`Select Installation Media`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:231 +msgid "" +"Choose an installation method: `Safe Installation`_ or `Destructive " +"Installation`_." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:238 +msgid "Figure 8: Select Installation Media" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:241 +msgid "Safe Installation" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:242 +msgid "" +"Use this method to safely install |CL| on media with available space, or " +"alongside existing partitions, and accept the `Default partition " +"schema`_. If enough free space exists, safe installation is allowed." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:248 +msgid "" +"|CL| allows installation alongside another OS. Typically, when you boot " +"your system, you can press an `F key` to view and select a bootable " +"device or partition during the BIOS POST stage. Some BIOSes present the " +"|CL| partition, and you can select and boot it. However, other BIOSes may" +" only show the primary partition, in which case you will not be able boot" +" |CL|. Be aware of this possible limitation." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:257 +msgid "Destructive Installation" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:259 +msgid "" +"Use this method to destroy the contents of the target device, install " +"|CL| on it, and accept the `Default partition schema`_." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:262 +msgid "Disk encryption" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:264 +msgid "" +"For greater security, disk encryption is supported using LUKS. Encryption" +" is optional." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:267 +msgid "" +"To encrypt the root partition, select :guilabel:`Enable Encryption`, as " +"shown in Figure 9." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:274 +msgid "Figure 9: Enable Encryption" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:276 +msgid "When :guilabel:`Encryption Passphrase` appears, enter a passphrase." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:282 +msgid "Figure 10: Encryption Passphrase" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:286 +msgid "Minimum length is 8 characters. Maximum length is 94 characters." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:288 +msgid "Enter the same passphrase in the second field." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:290 +msgid "Select :guilabel:`Confirm` in the dialogue box." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:294 +msgid ":guilabel:`Confirm` is only highlighted if passphrases match." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:296 +msgid "Select :guilabel:`Confirm` in submenu." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:299 +msgid "Manage User" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:301 +msgid "In Required Options, select :guilabel:`Manage User`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:303 +msgid "In :guilabel:`User Name`, enter a user name." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:309 +msgid "Figure 11: Manage User" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:311 +msgid "" +"In :guilabel:`Login`, create a login name. It must start with a letter " +"and can use numbers, hyphens, and underscores. Maximum length is 31 " +"characters." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:315 +msgid "" +"In :guilabel:`Password`, enter a password. Minimum length is 8 " +"characters. Maximum length is 255 characters." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:318 +msgid "In :guilabel:`Confirm`, enter the same password." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:322 +msgid "" +":guilabel:`Administrator` rights are selected by default. For security " +"purposes, the default user must be assigned as an Administrator." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:326 +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:394 +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:427 +msgid "Select :kbd:`Confirm`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:330 +msgid "Select :guilabel:`Cancel` to return to the Main Menu." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:333 +msgid "Modify User" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:335 +msgid "In Manager User, select :guilabel:`Manage User`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:337 +msgid "Modify user details as desired." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:339 +msgid "Select :guilabel:`Confirm` to save the changes you made." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:343 +msgid "" +"Optional: Select :guilabel:`Cancel` to return to the Main Menu to revert " +"changes." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:346 +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:404 +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:429 +msgid "Optional: Skip to `Finish installation`_." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:349 +msgid "Telemetry" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:351 +msgid "" +"Choose whether to participate in `telemetry`. :ref:`telem-guide` is a " +"|CL| feature that reports failures and crashes to the |CL| development " +"team for improvements. For more information, see :ref:`telemetry-about`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:355 +msgid "From :guilabel:`Required Options`, select :guilabel:`Telemetry`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:357 +msgid "Select :kbd:`Yes`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:363 +msgid "Figure 12: Enable Telemetry" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:365 +msgid "If you don't wish to participate, select :kbd:`No`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:368 +msgid "Advanced options" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:370 +msgid "" +"After you complete the `Required options`_, we recommend completing " +":guilabel:`Advanced options`--though they're not required. Doing so " +"customizes your development environment, so you're ready to go " +"immediately after reboot." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:375 +msgid "`Bundle Selection`_" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:377 +msgid "`Assign Hostname`_" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:379 +msgid "As for bundles, you can always add more later with :ref:`swupd-guide`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:382 +msgid "Bundle Selection" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:384 +msgid "On the Advanced menu, select :guilabel:`Bundle Selection`" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:386 +msgid "Select your desired bundles." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:392 +msgid "Figure 13: Bundle Selection" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:396 +msgid "View the bundles that you selected." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:402 +msgid "Figure 14: Bundle Selections - Advanced Options" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:407 +msgid "Assign Hostname" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:409 +msgid "In Advanced Options, select :guilabel:`Assign Hostname`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:411 +msgid "In :guilabel:`Hostname`, enter the hostname only (excluding the domain)." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:417 +msgid "Figure 15: Assign Hostname" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:421 +msgid "" +"Hostname does not allow empty spaces. Hostname must start with an " +"alphanumeric character but may also contain hyphens. Maximum length of 63" +" characters." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:425 +msgid "Navigate to :kbd:`Confirm` until highlighted." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:432 +msgid "Finish installation" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:434 +msgid "" +"When you are satisfied with your installation configuration, select " +":guilabel:`Install`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:441 +msgid "Figure 16: Finish installation" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:447 +msgid "" +"If you do not enter a selection for all :guilabel:`Required Options`, the" +" :guilabel:`Install` button remains greyed out, as shown in Figure 17. " +"Return to `Required Options`_ and make selections." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:456 +msgid "Figure 17: Required Options - Incomplete" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:458 +msgid "After installation is complete, select :guilabel:`Exit`." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:460 +msgid "Shut down the target system." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:462 +msgid "Remove the USB or any installation media." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:464 +msgid "Power on your system." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:468 +msgid "" +"Allow time for the graphical login to appear. A login prompt shows the " +"administrative user that you created." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:470 +msgid "Log in as the adminstrative user." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:472 +msgid "Congratulations. You successfully installed |CL|." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:475 +msgid "Default partition schema" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:477 +msgid "" +"Table 1 shows the defult partition schema with the exception of root, " +"which varies." +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:480 +msgid "**Table 1. Disk Partition Setup**" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:484 +msgid "FileSystem" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:485 +msgid "Mount Point" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:486 +msgid "Minimum size" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:487 +msgid "``VFAT``" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:488 +msgid "/boot" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:489 +msgid "150M" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:490 +msgid "``swap``" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:492 +msgid "256MB" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:493 +msgid "``root``" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:494 +msgid "/" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:495 +msgid "*Size depends upon use case/desired bundles.*" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:498 +msgid "Next steps" +msgstr "" + +#: ../../get-started/bare-metal-install-desktop/bare-metal-install-desktop.rst:500 +msgid ":ref:`guides`" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/get-started/bare-metal-install-server/bare-metal-install-server.po b/locale/zh_CN/LC_MESSAGES/get-started/bare-metal-install-server/bare-metal-install-server.po new file mode 100644 index 00000000..65d7c961 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/get-started/bare-metal-install-server/bare-metal-install-server.po @@ -0,0 +1,1237 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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/bare-metal-install-server/bare-metal-install-server.rst:4 +msgid "Install |CL-ATTR| on bare metal with live server" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:6 +msgid "" +"These instructions guide you through installing |CL-ATTR| on bare metal " +"from a bootable USB drive using a live server image." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:13 +msgid "System requirements" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:15 +msgid "Assure that your target system supports the installation:" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:17 +msgid ":ref:`system-requirements`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:18 +msgid ":ref:`compatibility-check`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:21 +msgid "Download the latest |CL| live server image" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:23 +msgid "" +"Get the latest |CL| installer image from the `downloads page`_. Look for " +"the :file:`clear-[version number]-live-server.iso` file." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:26 +msgid "Follow your OS instructions to create a bootable USB drive." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:28 +msgid ":ref:`bootable-usb`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:30 +msgid "After downloading the image, verify and decompress the file per your OS." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:33 +msgid "Install |CL| on your target system" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:35 +msgid "" +"Ensure that your system is configured to boot UEFI. The installation " +"method described below requires a wired Internet connection with DHCP." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:40 +msgid "" +"Alternatively, you can install |CL| over a wireless connection by first " +"using `nmtui`. Follow the `nmtui` instructions shown in Figure 2." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:43 +msgid "Follow these steps to install |CL| on the target system:" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:45 +msgid "Insert the USB drive into an available USB slot." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:47 +msgid "Power on the system." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:49 +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-server/bare-metal-install-server.rst:53 +msgid "" +"|CL| supports UEFI boot. Some hardware may list UEFI and non-UEFI USB " +"boot entries. In this case, you should select the `UEFI` boot option." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:57 +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-server/bare-metal-install-server.rst:60 +msgid "Save these settings and exit." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:62 +msgid "Reboot the target system." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:64 +msgid "This action launches the |CL| installer boot menu, shown in figure 1." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:70 +msgid "Figure 1: Clear Linux OS Installer boot menu" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:72 +msgid "With :guilabel:`Clear Linux OS` highlighted, select :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:75 +msgid "Launch the |CL| Installer" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:77 +msgid "At the :guilabel:`login` prompt, enter :command:`root`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:79 +msgid "" +"Follow the onscreen instructions, shown in Figure 2, and enter a " +"temporary password." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:86 +msgid "Figure 2: root login" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:88 +msgid "" +"At the :guilabel:`root` prompt, enter :command:`clr-installer` and press " +":kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:95 +msgid "Figure 3: clr-installer command" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:98 +msgid "Minimum installation requirements" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:100 +msgid "" +"To fulfill minimum installation requirements, complete the `Required " +"options`_. While not required, we encourage you to apply the `Recommended" +" options`_. `Advanced options`_ are optional." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:106 +msgid "" +"The :kbd:`Install` button is **only highlighted after** you complete " +"`Required options`_." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:110 +msgid "Main Menu" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:111 +msgid "The |CL| Installer Main Menu appears as shown in Figure 4." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:117 +msgid "Figure 4: Clear Linux OS Installer" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:119 +msgid "" +"The |CL| Installer Main Menu has two tabs: :guilabel:`[R] Required " +"options` and :guilabel:`[A] Advanced options`. Navigate between tabs " +"using the arrow these shortcut keys:" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:123 +msgid ":kbd:`Shift+A` for :guilabel:`[A] Advanced options`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:124 +msgid ":kbd:`Shift+R` for :guilabel:`[R] Required options`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:126 +msgid "" +"To meet the minimum requirements, enter your choices in the " +":guilabel:`Required options`. After confirmation, your selections appear " +"beside the :guilabel:`>>` chevron, below the menu options." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:131 +msgid "Navigation" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:133 +msgid "Select :kbd:`Tab` or :kbd:`Up/Down` arrows to highlight your choice." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:135 +msgid "Select :kbd:`Enter` or :kbd:`Spacebar` to confirm your choice." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:137 +msgid "Select :kbd:`Cancel` or :kbd:`Esc` to cancel your choice." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:140 +msgid "Required options" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:143 +msgid "Choose Timezone" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:145 +msgid "" +"From the Main Menu, navigate to :guilabel:`Choose Timezone`. `UTC` is the" +" default." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:148 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:168 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:185 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:677 +msgid "Select :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:150 +msgid "" +"In :guilabel:`Select System Timezone`, use :kbd:`Up/Down` arrows navigate" +" to the desired timezone." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:155 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:172 +msgid "Press :kbd:`Enter` to confirm." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:161 +msgid "Figure 5: Select System Timezone" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:164 +msgid "Choose Language" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:166 +msgid "From the Main Menu, navigate to :guilabel:`Choose Language`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:170 +msgid "In :guilabel:`Select System Language`, navigate to your desired language." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:178 +msgid "Figure 6: Select System Language" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:181 +msgid "Configure the Keyboard" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:183 +msgid "From the Main Menu, select :guilabel:`Configure the Keyboard`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:187 +msgid "In :guilabel:`Select Keyboard`, navigate to the desired option." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:189 +msgid "Select :kbd:`Enter` to :kbd:`Confirm`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:191 +msgid "" +"Optional: In :guilabel:`Test keyboard`, type text to assure that the keys" +" map to your keyboard." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:198 +msgid "Figure 7: Select Keyboard menu" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:201 +msgid "Configure Installation Media" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:203 +msgid "From the Main Menu, select :guilabel:`Configure Installation Media`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:205 +msgid "" +"Choose an installation method: * `Safe Installation`_ * `Destructive " +"Installation`_ * `Advanced Configuration`_" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:215 +msgid "Figure 8: Select Installation Media" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:217 +msgid "Select :guilabel:`Rescan Media` to show available installation targets." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:222 +msgid "Safe Installation" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:224 +msgid "" +"Use this method to safely install |CL| on media with available space, or " +"alongside existing partitions, and accept the `Default partition " +"schema`_. If enough free space exists, safe installation is allowed. See " +"also `Troubleshooting`_ below." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:230 +msgid "Destructive Installation" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:232 +msgid "" +"Use this method to destroy the contents of the target device, install " +"|CL| on it, and accept the `Default partition schema`_." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:237 +msgid "" +"From the :guilabel:`Select Installation Media` menu, select " +":guilabel:`Enable Encryption` to encrypt the root filesystem for either " +"option above. See also `Disk encryption`_ for more information." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:242 +msgid "Advanced Configuration" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:244 +msgid "" +"Use this method to manually configure partitions. These must meet " +"`Default partition schema`_. You may also choose `Disk encryption`_ " +"during configuration of each partition." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:250 +msgid "" +"`Advanced Configuration` is available in the installer versions 1.2.0 and" +" above." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:253 +msgid "" +"From :guilabel:`Select Installation Media`, shown in Figure 8 above, " +"select :guilabel:`Advanced Configuration`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:256 +msgid "" +"In :guilabel:`Advanced Configuration`, navigate to :file:`/dev/sda` and " +"then press :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:263 +msgid "Figure 9: Advanced configuration menu" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:265 +msgid "Choose a partition method:" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:267 +msgid "" +":guilabel:`Auto Partition` Select this option to accept the `Default " +"partition schema`_." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:270 +msgid "Navigate to and press :guilabel:`Confirm`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:272 +msgid "Continue with installation configuration. Jump to `Telemetry`_." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:274 +msgid "`Manual Partition`_ Continue below." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:277 +msgid "Manual Partition" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:279 +msgid "We provide a simple example below." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:281 +msgid "" +"Navigate to the unallocated media (e.g.,`/dev/sda`) until highlighted, as" +" shown in Figure 9." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:284 +msgid "Press :guilabel:`Enter` to edit the partition." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:286 +msgid "The :guilabel:`Partition Setup` menu appears, shown in Figure 10." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:290 +msgid "" +"After adding the first partition, select :guilabel:`Free Space` to add " +"another partition." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:293 +msgid "root partition" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:295 +msgid "" +"We configure the `root` partition as shown in Figure 10. Configuration of" +" the `root` partition varies." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:302 +msgid "Figure 10: root partition" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:304 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:317 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:331 +msgid "Navigate to :guilabel:`Add` and press :guilabel:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:307 +msgid "boot partition" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:309 +msgid "We configure the `boot` partition as shown in Figure 11." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:315 +msgid "Figure 11: boot partition" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:320 +msgid "swap partition" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:322 +msgid "" +"In the :guilabel:`File System` pulldown menu, select `swap`, and enter a " +"label. We enter the minimum required size (e.g., 256M)." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:329 +msgid "Figure 12: swap partition" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:333 +msgid "" +"Next, navigate to :guilabel:`Confirm` and press :guilabel:`Enter`, shown " +"in Figure 13." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:336 +msgid "Manual partitioning is complete." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:342 +msgid "Figure 13: Final configuration of disk partitions" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:344 +msgid "You may skip to the `Telemetry`_ section below." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:347 +msgid "Disk encryption" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:349 +msgid "" +"For greater security, disk encryption is supported using LUKS for the any" +" partition except `/boot` on |CL|. To encrypt the root partition, see the" +" example below. Encryption is optional." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:354 +msgid "Encryption Passphrase" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:356 +msgid "" +"|CL| uses a single passphrase for encrypted partitions. Additional keys " +"may be configured post-installation using the ``cryptsetup`` tool." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:359 +msgid "" +"Optional: Select :guilabel:`[X] Encrypt` to encrypt the root partition, " +"as shown in Figure 14." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:366 +msgid "Figure 14: Encrypt partition" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:368 +msgid "The :guilabel:`Encryption Passphrase` dialogue appears." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:372 +msgid "Minimum length is 8 characters. Maximum length is 94 characters." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:378 +msgid "Figure 15: Encryption Passphrase" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:380 +msgid "Enter the same passphrase in the first and second field." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:382 +msgid "Navigate to :guilabel:`Confirm` and press :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:386 +msgid ":guilabel:`Confirm` is only highlighted if passphrases match." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:389 +msgid "Telemetry" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:391 +msgid "" +":ref:`telem-guide` is a |CL| feature that reports failures and crashes to" +" the |CL| development team for improvements. For more detailed " +"information, visit our :ref:`telemetry-about` page." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:395 +msgid "Select your desired option on whether to participate in `telemetry`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:397 +msgid "" +"In the Main Menu, navigate to :guilabel:`Telemetry` and select " +":kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:400 +msgid "Select :kbd:`Tab` to highlight your choice." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:402 +msgid "Select :kbd:`Enter` to confirm." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:408 +msgid "Figure 16: Enable Telemetry" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:411 +msgid "Recommended options" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:413 +msgid "" +"After you complete the `Required options`_, we highly recommend " +"completing these selected `Advanced options`_ at minimum:" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:416 +msgid "`Manage User`_ Assign a new user with administrative rights" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:417 +msgid "`Assign Hostname`_ Simplify your development environment" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:420 +msgid "Skip to finish installation" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:422 +msgid "" +"After selecting values for all :guilabel:`Required options`, you may skip" +" to `Finish installation`_." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:425 +msgid "" +"Otherwise, continue below. In the Main Menu, select :guilabel:`Advanced " +"options` for additional configuration." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:429 +msgid "Advanced options" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:432 +msgid "Configure Network Interfaces" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:434 +msgid "" +"By default, |CL| is configured to automatically detect the host network " +"interface using DHCP. However, if you want to use a static IP address or " +"if you do not have a DHCP server on your network, follow these " +"instructions to manually configure the network interface. Otherwise, " +"default network interface settings are automatically applied." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:442 +msgid "If DHCP is available, no user selection may be required." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:444 +msgid "" +"Navigate to :guilabel:`Configure Network Interfaces` and select " +":kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:447 +msgid "Navigate to the network :guilabel:`interface` you wish to change." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:449 +msgid "" +"When the desired :guilabel:`interface` is highlighted, select " +":guilabel:`Enter` to edit." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:452 +msgid "Multiple network interfaces may appear." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:458 +msgid "Figure 17: Configure Network Interfaces" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:460 +msgid "Notice :guilabel:`Automatic / dhcp` is selected by default (at bottom)." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:462 +msgid "" +"Optional: Navigate to the checkbox :guilabel:`Automatic / dhcp` and " +"select :kbd:`Spacebar` to deselect." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:469 +msgid "Figure 18: Network interface configuration" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:471 +msgid "" +"Navigate to the appropriate fields and assign the desired network " +"configuration." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:474 +msgid "To save settings, navigate to :guilabel:`Confirm` and select :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:479 +msgid "" +"To revert to previous settings, navigate to the :guilabel:`Cancel` and " +"select :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:482 +msgid "" +"Upon confirming network configuration, the :guilabel:`Testing Networking`" +" dialogue appears. Assure the result shows success. If a failure occurs, " +"your changes will not be saved." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:486 +msgid "" +"Upon confirmation, you are returned to :guilabel:`Network interface` " +"settings." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:489 +msgid "Navigate to and select :guilabel:`Main Menu`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:491 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:519 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:540 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:564 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:664 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:694 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:714 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:733 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:758 +msgid "Optional: Skip to `Finish installation`_." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:494 +msgid "Proxy" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:496 +msgid "" +"|CL| automatically attempts to detect proxy settings, as described in " +"`Autoproxy`_. If you need to manually assign proxy settings, follow this " +"instruction." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:500 +msgid "" +"From the Advanced options menu, navigate to :guilabel:`Proxy`, and select" +" :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:503 +msgid "Navigate to the field :guilabel:`HTTPS Proxy`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:509 +msgid "Figure 19: Configure the network proxy" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:511 +msgid "" +"Enter the desired proxy address and port using conventional syntax, such " +"as: \\http://address:port." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:514 +msgid "Navigate to :guilabel:`Confirm` and select :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:516 +msgid "" +"To revert to previous settings, navigate to :guilabel:`Cancel` and select" +" :guilabel:`Cancel`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:522 +msgid "Test Network Settings" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:524 +msgid "" +"To manually assure network connectivity before installing |CL|, select " +":guilabel:`Test Network Settings` and select :guilabel:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:527 +msgid "A progress bar appears as shown in Figure 20." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:533 +msgid "Figure 20: Testing Networking dialogue" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:537 +msgid "" +"Any changes made to network settings are automatically tested during " +"configuration." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:543 +msgid "Bundle Selection" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:545 +msgid "On the Advanced menu, select :guilabel:`Bundle Selection`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:547 +msgid "Navigate to the desired bundle using :kbd:`Tab` or :kbd:`Up/Down` arrows." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:549 +msgid "Select :kbd:`Spacebar` to select the checkbox for each desired bundle." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:555 +msgid "Figure 21: Bundle Selection" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:557 +msgid "" +"Optional: To start developing with |CL|, we recommend adding :file:`os-" +"clr-on-clr`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:560 +msgid "Navigate to and select :kbd:`Confirm`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:562 +msgid "You are returned to the :guilabel:`Advanced options` menu." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:567 +msgid "Manage User" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:570 +msgid "Add New User" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:572 +msgid "In Advanced Options, select :guilabel:`Manage User`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:574 +msgid "Select :guilabel:`Add New User` as shown in Figure 22." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:580 +msgid "Figure 22: Add New User" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:582 +msgid "Optional: Enter a :guilabel:`User Name`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:592 +msgid "Figure 23: User Name" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:594 +msgid "Enter a :guilabel:`Login`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:598 +msgid "" +"The User Login must be alphanumeric and can include hyphens and " +"underscores. Maximum length is 31 characters." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:600 +msgid "Enter a :guilabel:`Password`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:606 +msgid "In :guilabel:`Confirm`, enter the same password." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:608 +msgid "" +"Optional: Navigate to the :guilabel:`Administrative` checkbox and select " +":kbd:`Spacebar` to assign administrative rights to the user." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:613 +msgid "Selecting this option enables sudo privileges for the user." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:615 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:692 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:725 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:756 +msgid "Select :kbd:`Confirm`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:619 +msgid "If desired, select :guilabel:`Reset` to reset the form." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:621 +msgid "In :guilabel:`Manage User`, navigate to :guilabel:`Confirm`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:623 +msgid "With :guilabel:`Confirm` highlighted, select :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:626 +msgid "Modify / Delete User" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:628 +msgid "" +"In :guilabel:`Manage User`, navigate to the user you wish to modify until" +" highlighted, as shown in Figure 24." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:631 +msgid "Select :kbd:`Enter` to modify the user." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:637 +msgid "Figure 24: Modify User" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:639 +msgid "Modify user details as desired." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:641 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:660 +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:754 +msgid "Navigate to :kbd:`Confirm` until highlighted." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:645 +msgid "Optional: Select :guilabel:`Reset` to rest the form." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:647 +msgid "Select :guilabel:`Confirm` to save the changes you made." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:649 +msgid "" +"Optional: In :guilabel:`Modify User`, to delete the user, navigate to the" +" :guilabel:`Delete` button and select :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:656 +msgid "Figure 25: Delete User" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:658 +msgid "You are returned to :guilabel:`Manage User`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:662 +msgid "Select :guilabel:`Enter` to complete :guilabel:`Manage User` options." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:667 +msgid "Kernel Command Line" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:669 +msgid "" +"For advanced users, |CL| provides the ability to add or remove kernel " +"arguments. If you want to append a new argument, enter the argument here." +" This argument will be used every time you install or update a new " +"kernel." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:674 +msgid "" +"In Advanced Options, select :guilabel:`Tab` to highlight " +":guilabel:`Kernel Command Line`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:683 +msgid "Figure 26: kernel command line" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:685 +msgid "Choose from the following options." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:687 +msgid "To add arguments, enter the argument in :guilabel:`Add Extra Arguments`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:689 +msgid "To remove an argument, enter the argument in :guilabel:`Remove Arguments`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:697 +msgid "Kernel Selection" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:699 +msgid "" +"Select a kernel option. By default, the latest kernel release is " +"selected. Native kernel is shown in Figure 27." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:702 +msgid "To select a different kernel, navigate to it using :guilabel:`Tab`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:708 +msgid "Figure 27: Kernel selection" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:710 +msgid "Select :kbd:`Spacebar` to select the desired option." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:712 +msgid "Navigate to :kbd:`Confirm` and select :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:717 +msgid "Swupd Mirror" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:719 +msgid "If you have your own custom mirror of |CL|, you can add its URL." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:721 +msgid "In Advanced Options, select :guilabel:`Swupd Mirror`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:723 +msgid "To add a local swupd mirror, enter a valid URL in :guilabel:`Mirror URL:`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:731 +msgid "Figure 28: Swupd Mirror" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:736 +msgid "Assign Hostname" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:738 +msgid "In Advanced Options, select :guilabel:`Assign Hostname`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:740 +msgid "In :guilabel:`Hostname`, enter the hostname only (excluding the domain)." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:744 +msgid "" +"Hostname does not allow empty spaces. Hostname must start with an " +"alphanumeric character but may also contain hyphens. Maximum length of 63" +" characters." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:752 +msgid "Figure 29: Assign Hostname" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:761 +msgid "Automatic OS Updates" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:763 +msgid "" +"Automatical OS updates are enabled by default. In the rare case that you " +"need to disable automatic software updates, follow the onscreen " +"instructions, shown in Figure 30." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:767 +msgid "In Advanced Options, select :guilabel:`Automatic OS Updates`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:769 +msgid "Select the desired option." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:775 +msgid "Figure 30: Automatic OS Updates" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:777 +msgid "You are returned to the :guilabel:`Main Menu`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:780 +msgid "Save Configuration Settings" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:782 +msgid "In Advanced Options, select :guilabel:`Save Configuration Settings`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:784 +msgid "" +"A dialogue box shows the installation configuration was saved to :file" +":`clr-installer.yaml`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:791 +msgid "Figure 31: Automatic OS Updates" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:793 +msgid "" +"Use the :file:`clr-installer.yaml` file to install |CL|, with the same " +"configuration, on multiple targets." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:797 +msgid "Finish installation" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:799 +msgid "" +"When you are satisfied with your installation configuration, navigate to " +":guilabel:`Install` and select :kbd:`Enter`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:806 +msgid "Figure 32: Select Install" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:808 +msgid "Select :guilabel:`reboot`." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:812 +msgid "" +"If you do not assign an administrative user, upon rebooting, enter `root`" +" and set the root password immediately." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:815 +msgid "When the system reboots, remove any installation media present." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:818 +msgid "Default partition schema" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:820 +msgid "" +"To add partitions manually, see `Advanced configuration`_ below, and " +"create partitions per requirements in Table 1." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:823 +msgid "**Table 1. Disk Partition Setup**" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:827 +msgid "FileSystem" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:828 +msgid "Mount Point" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:829 +msgid "Minimum size" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:830 +msgid "``VFAT``" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:831 +msgid "/boot" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:832 +msgid "150M" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:833 +msgid "``swap``" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:835 +msgid "256MB" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:836 +msgid "``root``" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:837 +msgid "/" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:838 +msgid "*Size depends upon use case/desired bundles.*" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:841 +msgid "Troubleshooting" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:844 +msgid "For Configure Installation Media" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:846 +msgid "" +"If a warning message appears that no media or space is available after " +"entering :guilabel:`Configure Installation Media`:" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:849 +msgid "Verify that target media has enough free space." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:851 +msgid "Confirm the USB is properly connected to and mounted on target media." +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:853 +msgid "Review the size of existing partitions on the target media:" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:855 +msgid "Linux\\* OS: :command:`lsblk -a`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:856 +msgid "Windows\\* OS: :command:`diskpart`, then :command:`list disk`" +msgstr "" + +#: ../../get-started/bare-metal-install-server/bare-metal-install-server.rst:857 +msgid "macOS\\* platform: :command:`diskutil list`" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/get-started/bootable-usb/bootable-usb.po b/locale/zh_CN/LC_MESSAGES/get-started/bootable-usb/bootable-usb.po new file mode 100644 index 00000000..89e4ecf7 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/get-started/bootable-usb/bootable-usb.po @@ -0,0 +1,227 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"Instructions to create a |CL-ATTR| USB drive vary depending on your " +"operating system. Follow the instructions applicable to your system:" +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." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:22 +msgid "Create a bootable USB drive on Linux\\*" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:24 +#: ../../get-started/bootable-usb/bootable-usb.rst:107 +#: ../../get-started/bootable-usb/bootable-usb.rst:166 +msgid "Make sure you have have completed all `Prerequisites`_." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:26 +msgid "" +"Before burning the image onto your USB drive, :ref:`verify and decompress" +" your image `." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:30 +#: ../../get-started/bootable-usb/bootable-usb.rst:113 +#: ../../get-started/bootable-usb/bootable-usb.rst:172 +msgid "Burn the |CL| image onto a USB drive" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:34 +#: ../../get-started/bootable-usb/bootable-usb.rst:117 +#: ../../get-started/bootable-usb/bootable-usb.rst:176 +msgid "|CAUTION-BACKUP-USB|" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:36 +msgid "Open a terminal emulator and get root privilege." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:42 +#: ../../get-started/bootable-usb/bootable-usb.rst:121 +msgid "Go to the directory with the decompressed image." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:44 +msgid "Plug in the USB drive." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:46 +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:58 +msgid "Example output:" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:81 +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:91 +msgid "" +"Burn the image onto the USB drive. The example below burns an " +"uncompressed image onto ``:" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:100 +msgid "|CAUTION-UNMOUNT-USB-PARTITIONS|" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:105 +msgid "Create a bootable USB drive on macOS\\*" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:109 +msgid "" +"Before burning the image onto your USB drive, :ref:`verify and decompress" +" your image `." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:119 +msgid "Launch the Terminal app." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:123 +msgid "Plug in a USB drive and get its identifier:" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:129 +msgid "This will list available disks and their partitions, as shown in Figure 1." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:135 +msgid "Figure 1: macOS - Get USB drive identifier" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:137 +msgid "Unmount the USB drive identified in the previous step. For example:" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:143 +msgid "" +"Burn the image onto the drive using the :command:`dd` command. The " +"example below burns an uncompressed image onto ``:" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:150 +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:153 +msgid "Press :kbd:`-T` to check imaging progress." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:155 +msgid "Eject the USB drive." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:164 +msgid "Create a bootable USB drive on Windows\\*" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:168 +msgid "" +"Before burning the image onto your USB drive, :ref:`verify and decompress" +" your image `." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:178 +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:181 +msgid "Plug in the USB drive and open Rufus." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:183 +msgid "Under `Boot selection`, click the :guilabel:`SELECT` button." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:185 +msgid "Find and select the previously extracted |CL| image file." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:187 +msgid "Click the :guilabel:`START` button. See Figure 2." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:193 +msgid "Figure 2: Rufus utility" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:195 +msgid "" +"When the dialogue appears, select :guilabel:`Write in ISO image mode " +"(Recommended)`. See Figure 3." +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:202 +msgid "Figure 3: ISOHybrid image detected" +msgstr "" + +#: ../../get-started/bootable-usb/bootable-usb.rst:204 +msgid "Select the Windows taskbar menu for USB and select eject." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/get-started/compatibility-check.po b/locale/zh_CN/LC_MESSAGES/get-started/compatibility-check.po new file mode 100644 index 00000000..726ea234 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/get-started/compatibility-check.po @@ -0,0 +1,71 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"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 "" + +#: ../../get-started/compatibility-check.rst:13 +msgid "" +"This does not check other system components (for example: storage and " +"graphics) for compatibility with |CL|." +msgstr "" + +#: ../../get-started/compatibility-check.rst:16 +msgid "Download the `clear-linux-check-config.sh`_ file." +msgstr "" + +#: ../../get-started/compatibility-check.rst:18 +msgid "If a browser is not available, use:" +msgstr "" + +#: ../../get-started/compatibility-check.rst:24 +msgid "Make the script executable." +msgstr "" + +#: ../../get-started/compatibility-check.rst:30 +msgid "Run the script." +msgstr "" + +#: ../../get-started/compatibility-check.rst:32 +msgid "" +"Check to see if the host's processor and EFI firmware is capable of " +"running |CL|." +msgstr "" + +#: ../../get-started/compatibility-check.rst:39 +msgid "Check to see if the host is capable of running |CL| in a container." +msgstr "" + +#: ../../get-started/compatibility-check.rst:45 +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 "" + diff --git a/locale/zh_CN/LC_MESSAGES/get-started/get-started.po b/locale/zh_CN/LC_MESSAGES/get-started/get-started.po new file mode 100644 index 00000000..dbe2f3f9 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/get-started/get-started.po @@ -0,0 +1,67 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 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 "" + +#: ../../get-started/get-started.rst:11 +msgid "Pre-install" +msgstr "" + +#: ../../get-started/get-started.rst:13 +msgid "There are a couple of things to take care of before you install." +msgstr "" + +#: ../../get-started/get-started.rst:15 +msgid ":ref:`system-requirements`" +msgstr "" + +#: ../../get-started/get-started.rst:16 +msgid ":ref:`compatibility-check`" +msgstr "" + +#: ../../get-started/get-started.rst:17 +msgid ":ref:`bootable-usb`" +msgstr "" + +#: ../../get-started/get-started.rst:19 +msgid "When installing |CL-ATTR| in a VM, consider which kernel to use." +msgstr "" + +#: ../../get-started/get-started.rst:21 +msgid ":ref:`Compatible VM kernels `" +msgstr "" + +#: ../../get-started/get-started.rst:31 +msgid "Install" +msgstr "" + +#: ../../get-started/get-started.rst:42 +msgid "Install in a virtual machine" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/gce.po b/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/gce.po new file mode 100644 index 00000000..9ba7ad3d --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/gce.po @@ -0,0 +1,340 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 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 "" + +#: ../../get-started/virtual-machine-install/gce.rst:13 +msgid "Prerequisites" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:15 +msgid "Set up a Google account and a GCP billing account." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:17 +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 "Process" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:24 +msgid "" +"Sign in to your Google\\* account on the `Google Cloud Console " +"`_:" +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 " +"`_ 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 " +"`_ to view the " +"currently released :abbr:`GCE (Google Compute Engine\\*)` image, and " +"download the :file:`clear--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:157 +msgid "Click the *Navigation menu* icon on the upper left screen menu." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:56 +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 "" + +#: ../../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 ``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 select the " +"``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 ``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 "Hover your mouse over the *Compute Engine* menu and select *Images*." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:120 +msgid "Figure 8: Image library" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:122 +msgid "" +"On the Compute Engine Image library page, click the ``[+] CREATE IMAGE`` " +"menu item to create a custom image:" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:129 +msgid "Figure 9: Create image" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:131 +msgid "" +"In the VM image creation page, change the image source type to *Cloud " +"Storage file*." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:134 +msgid "Under :guilabel:`Cloud Storage file`, select :guilabel:`Browse`." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:136 +msgid "" +"Locate the :file:`clear--gce.tar.gz` file, and click " +":guilabel:`Select`." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:143 +msgid "Figure 10: Create image using imported object" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:145 +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 "" + +#: ../../get-started/virtual-machine-install/gce.rst:152 +msgid "Figure 11: Image is created" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:154 +msgid "" +"After the |CL| image is imported, you can launch a VM instance running " +"|CL|:" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:159 +msgid "" +"Hover your mouse over the *Compute Engine* menu group and select the *VM " +"instances* item." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:166 +msgid "Figure 12: VM instances catalog" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:168 +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:171 +msgid "" +"Alternatively, click the ``CREATE INSTANCE`` button on the VM instances " +"page to create a VM instance." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:178 +msgid "Figure 13: VM creation" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:184 +msgid "Figure 14: VM instances list" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:186 +msgid "" +"In :guilabel:`Region`, choose a region based on the `Best practices for " +"Compute Engine regions selection`_." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:189 +msgid "Under *Boot disk*, click the ``Change`` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:195 +msgid "Figure 15: Use custom image" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:197 +msgid "Select the *Custom images* tab for using Clear Linux OS GCE image." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:203 +msgid "Figure 16: Select Clear Linux boot disk to create a VM instance" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:205 +msgid "" +"Scroll down to the bottom of the VM instance creation page, expand the " +"*Management, security, disks, networking, sole tenancy* group." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:212 +msgid "Figure 17: Set up SSH keys" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:215 +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:219 +msgid "Refer to :ref:`security` for more details." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:221 +msgid "Click the *Security* tab, copy and paste your SSH public key:" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:227 +msgid "Figure 18: Set SSH key for remote login" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:231 +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:236 +msgid "Click the ``Create`` button to create the |CL| VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:238 +msgid "The Clear Linux VM instance is created and assigned a public IP address:" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:244 +msgid "Figure 19: Clear Linux VM instance is created and started" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:246 +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:253 +msgid "Figure 20: SSH login to Clear Linux VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:256 +msgid "Related topics" +msgstr "" + +#: ../../get-started/virtual-machine-install/gce.rst:258 +msgid "" +"The following tutorials describe a similar process and may be useful " +"references:" +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 "" + diff --git a/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/hyper-v.po b/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/hyper-v.po new file mode 100644 index 00000000..c728a732 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/hyper-v.po @@ -0,0 +1,111 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 section explains how to run |CL-ATTR| inside a `Windows Server " +"Virtualization`_\\* or **Hyper-V** environment." +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:9 +msgid "" +"Please ensure you have enabled `Intel® Virtualization Technology " +"`_ (Intel® VT) and " +"`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:16 +msgid "Enable Hyper-V" +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:18 +msgid "" +"Please refer to the `Microsoft documentation`_ to enable and configure " +"*Hyper-V* on your machine." +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:22 +msgid "Create a virtual network" +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:24 +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:30 +msgid "Create a virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:32 +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 "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:36 +msgid "Create a virtual machine using the **Hyper-V Manager**:" +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:38 +msgid "Choose **Generation 2** when prompted to *specify VM generation*." +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:39 +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:41 +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:44 +msgid "Currently, |CL| does not boot with `secure boot` enabled." +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:47 +msgid "Connect to your new VM and start it. You should see a prompt:" +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:53 +msgid "Set a root user password." +msgstr "" + +#: ../../get-started/virtual-machine-install/hyper-v.rst:55 +msgid "Your virtual machine running |CL| is ready!" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/kvm.po b/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/kvm.po new file mode 100644 index 00000000..d2c26b05 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/kvm.po @@ -0,0 +1,231 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 guide 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:10 +msgid "Install QEMU-KVM" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:12 +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:16 +msgid "Log in and open a terminal emulator." +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:18 +msgid "Install `QEMU*-KVM` on the host machine. Below are some example distros." +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:20 +msgid "On |CL|:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:26 +#: ../../get-started/virtual-machine-install/kvm.rst:155 +msgid "On Ubuntu\\* 18.04 LTS Desktop:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:32 +#: ../../get-started/virtual-machine-install/kvm.rst:161 +msgid "On Mint\\* 19.1 “Cinnamon” Desktop:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:38 +#: ../../get-started/virtual-machine-install/kvm.rst:167 +msgid "On Fedora\\* 30 Workstation:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:45 +msgid "Download and launch the virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:47 +msgid "" +"Download the latest pre-built |CL| KVM image file from the `image " +"`_ directory. Look for " +"``clear--kvm.img.xz``. You can also use this command:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:55 +msgid "Uncompress the downloaded image:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:61 +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:72 +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:78 +msgid "" +"Download the `QEMU-KVM launcher`_ script from the `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:87 +msgid "Make the script executable:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:93 +msgid "Start the |CL| KVM virtual machine:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:99 +msgid "Log in as ``root`` user and set a new password." +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:102 +msgid "SSH access into the virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:104 +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:107 +msgid "Configure SSH in the |CL| VM to allow root login:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:115 +msgid "Enable and start SSH server in the |CL| VM:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:122 +#: ../../get-started/virtual-machine-install/kvm.rst:211 +msgid "" +"Determine the IP address of the host on which you will launch the VM. " +"Substitute in the next step with this information." +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:129 +msgid "SSH into the |CL| VM using the default port of `10022`:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:136 +msgid "Optional: Add the GNOME Display Manager (GDM)" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:138 +msgid "" +"To add :abbr:`GDM (GNOME Display Manager)` to the |CL| VM, follow these " +"steps:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:140 +msgid "Shutdown the active |CL| VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:146 +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:149 +msgid "On Clear Linux:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:173 +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:194 +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:199 +msgid "Increase the size of the VM by 10GB to accommodate the GDM installation:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:205 +msgid "Relaunch the |CL| VM:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:218 +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:225 +msgid "Log in as `root` user into the |CL| VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:227 +msgid "" +"Follow these steps to `resize the partition`_ of the virtual disk of the " +"VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:229 +msgid "Add GDM to the |CL| VM:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:235 +msgid "Reboot the |CL| VM to start GDM:" +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:241 +msgid "Go through the GDM out-of-box experience (OOBE)." +msgstr "" + +#: ../../get-started/virtual-machine-install/kvm.rst:243 +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 "" + diff --git a/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/virtualbox-cl-installer.po b/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/virtualbox-cl-installer.po new file mode 100644 index 00000000..99f1c39d --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/virtualbox-cl-installer.po @@ -0,0 +1,554 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"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 "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:15 +msgid "Prerequisites" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:17 +msgid "Before continuing, assure you have:" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:19 +msgid "" +"Enabled 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:23 +msgid "" +"Downloaded and installed |VB| **version 6.0 or greater** from the " +"`official VirtualBox website`_ per the `appropriate instructions`_ for " +"your platform." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:28 +msgid "Download and extract the |CL| installer ISO" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:30 +msgid "" +"Download the :file:`clear--live-server.iso.xz` of |CL| on the " +"`downloads page`_." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:33 +msgid "" +"Validate the integrity of the downloaded image by checking the file hash " +"and signatures. Refer :ref:`validate-signatures` for detailed steps." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:36 +msgid "Decompress the downloaded image." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:38 +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:45 +msgid "Figure 1: 7zip extract here command" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:47 +msgid "On Linux :" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:53 +msgid "Delete the originally downloaded compressed file." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:56 +msgid "Create a new |VB| virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:58 +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 "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:63 +msgid "Launch the |VBM| from your host system." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:65 +msgid "Click the *New* button to create a new VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:67 +msgid "Choose :guilabel:`Expert mode`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:69 +msgid "In :guilabel:`Create Virtual Machine`, enter the following settings:" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:71 +msgid "**Name**: Choose name (e.g. ClearLinuxOS-VM)." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:72 +msgid "**Type**: Linux" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:73 +msgid "**Version**: **Linux 2.6 / 3.x / 4.x (64-bit)**" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:74 +msgid "**Hard disk**: `Create a virtual hard disk now`" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:75 +msgid "**Memory size default**: 2048 MB (Adjust appropriately.)" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:78 +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:85 +msgid "Figure 2: Create Virtual Machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:87 +msgid "Select :guilabel:`Create`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:89 +msgid "In :guilabel:`Create Virtual Hard Disk`, select:" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:91 +msgid "**File location**" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:92 +msgid "**File size**: **32.00 GB**. Adjust size to your needs." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:93 +msgid "**Hard disk file type**: `VDI (VirtualBox Disk Image)`" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:94 +msgid "**Storage on physical hard disk**:`Dynamically allocated`" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:100 +msgid "Figure 3: Create Virtual Hard Disk" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:102 +msgid "Click *Create*." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:104 +msgid "A new virtual machine will be created and appear in the |VBM|." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:106 +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:222 +msgid "Click *Settings* to configure the |CL| VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:108 +msgid "In the left-hand menu, navigate to the :guilabel:`System` menu." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:110 +msgid "" +"In the :guilabel:`Motherboard` tab, select the `Chipset` pulldown menu, " +"and then select :guilabel:`ICH9`. See Figure 4." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:115 +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:118 +msgid "In :guilabel:`Enabled Features`, check these boxes:" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:120 +msgid "**Enable I/O APIC**" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:121 +msgid "**Enable EFI (special OSes only)**" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:127 +msgid "Figure 4: Settings > System" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:131 +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:136 +msgid "Select :guilabel:`OK`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:139 +msgid "Install |CL| on the |VB| VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:141 +msgid "|CL| is ready to be installed." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:144 +msgid "Mount the installation ISO" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:146 +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:149 +msgid "" +"From the *ClearLinux-OS* :guilabel:`Settings` at left, select " +":guilabel:`Storage`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:152 +msgid "" +"From :guilabel:`Storage Devices`, middle column, click the blue disk " +"labeled *Empty*." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:155 +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 "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:163 +msgid "Figure 5: Choose Virtual Optical Disk Drive" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:165 +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:172 +msgid "Figure 6: Mounting an ISO" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:174 +msgid "Select :guilabel:`OK` to exit and return to the main |VBM|." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:177 +msgid "Install |CL| with live-server installer" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:179 +msgid "In the |VBM|, select virtual machine you created and click *Start*." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:185 +msgid "Figure 7: Start the installer" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:189 +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:192 +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:195 +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:198 +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:201 +msgid "" +"In :guilabel:`Advanced options` > :guilabel:`Manage User`, create an " +"administrative user." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:204 +msgid "Do not install the bundle `desktop-autostart`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:206 +msgid "When |CL| installation is complete, select :guilabel:`Exit`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:208 +msgid "At the prompt, enter:" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:215 +msgid "Unmount the ISO" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:217 +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:220 +msgid "Return to the |VBM|." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:224 +msgid "" +"From the *VM - Settings* window, navigate to the *Storage* pane from the " +"left-hand side." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:227 +msgid "" +"From the middle *Storage Devices* column, click the blue CD disk labeled " +"*clear--live-server.iso* under the *Controller: IDE* from." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:230 +msgid "" +"From the *Attributes* column at right, in *Optical Drive*, select the " +"blue CD icon beside and click *Remove Disk from Virtual Drive*." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:237 +msgid "Figure 8: Remove Disk from Virtual Drive" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:239 +msgid "Click *OK* to exit the *VM Settings* menu and return to the main |VBM|." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:243 +msgid "Install |VB| Linux Guest Additions" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:245 +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:248 +msgid "From the |VBM| select the |CL| VM, and select :guilabel:`Start`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:250 +msgid "In the VM Console, log in as the administrative user previously created." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:253 +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:256 +msgid "To update the kernel, enter:" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:262 +msgid "At initial login, enter the administrative user's password and continue." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:264 +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:272 +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:282 +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:290 +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 "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:297 +msgid "Figure 9: Insert Guest Additions CD image" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:299 +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:302 +msgid "Instead, we provide a script to patch and install |VB| drivers on |CL|." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:304 +msgid "Open a Terminal and enter the script:" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:312 +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:315 +msgid "Shut down the system. Select :guilabel:`Machine>ACPI Shutdown`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:321 +msgid "Figure 10: Powering off a VirtualBox VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:323 +msgid "Select :guilabel:`Settings`, :guilabel:`Display`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:325 +msgid "" +"In :guilabel:`Graphics Controller`, select :guilabel:`VBoxSVGA` to adjust" +" screen size dynamically." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:332 +msgid "Figure 11: VirtualBox hardware acceleration error" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:334 +msgid "In the |VBM|, select :guilabel:`Start`." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:336 +msgid "In the VM console, login and verify the |VB| drivers are loaded:" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:342 +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:345 +msgid "Add `desktop-autostart` for a full desktop experience." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:351 +msgid "Reboot the VM and log in with the administrative user." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:357 +msgid "The |CL| VM running on |VB| is ready to develop and explore." +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:360 +msgid "Troubleshooting" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:362 +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:370 +msgid "Figure 12: VirtualBox hardware acceleration error" +msgstr "" + +#: ../../get-started/virtual-machine-install/virtualbox-cl-installer.rst:372 +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:376 +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:379 +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:386 +msgid "" +"To enable Hyper-V again, execute this command in an **Administrator: " +"Command Prompt or Powershell**, and reboot the system:" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/vmw-player-preconf.po b/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/vmw-player-preconf.po new file mode 100644 index 00000000..9637b3b8 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/vmw-player-preconf.po @@ -0,0 +1,493 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"`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:11 +msgid "" +"This section shows 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 "In this tutorial, we perform the following steps:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:21 +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 "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:26 +msgid "Install the VMware Workstation Player hypervisor" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:28 +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:32 +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:35 +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:38 +msgid "On supported Linux distros:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:40 +msgid "Enable a GUI desktop." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:42 +msgid "Start a terminal emulator." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:44 +msgid "" +"Start the installer by issuing the command below and following the guided" +" steps." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:51 +msgid "On Windows:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:53 +msgid "Start the installer." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:54 +msgid "Follow the setup wizard." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:56 +msgid "For additional help, see the `VMware Workstation Player guide`_." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:59 +msgid "Download the latest |CL| VMware image" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:61 +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:69 +msgid "" +"Visit :ref:`image-types` for additional information about all available " +"|CL| images." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:4 +msgid "Verify the integrity of the |CL| image" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.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-windows.rst:11 +msgid "Download the corresponding SHA512 checksum file of your |CL| image." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:12 +msgid "Start Command Prompt." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:13 +msgid "Go to the directory with the downloaded image and checksum files." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:14 +msgid "Get the SHA512 checksum of the image with the command:" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.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-windows.rst:24 +msgid "Decompress the |CL| image" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.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-windows.rst:30 +msgid "Download and install `7-Zip`_." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:31 +msgid "Go to the directory with the downloaded image and right-click it." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.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-windows.rst:39 +msgid "Figure 1: Windows 7-Zip extract file." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:74 +msgid "We also provide instructions for other operating systems:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:76 +msgid ":ref:`download-verify-decompress-linux`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player-preconf.rst:77 +msgid ":ref:`download-verify-decompress-mac`" +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 "" + diff --git a/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/vmw-player.po b/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/vmw-player.po new file mode 100644 index 00000000..4ec155fc --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/vmw-player.po @@ -0,0 +1,492 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"`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.rst:11 +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 "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:16 +msgid "In this tutorial, we perform the following steps:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:21 +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:24 +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:30 +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 "" + +#: ../../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 14 Player`_ is available for Windows and Linux. " +"Download your preferred version." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:44 +msgid "" +"Install VMware Workstation 14 Player following the instructions " +"appropriate for your system's OS:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:47 +msgid "On supported Linux distros:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:49 +msgid "Enable a GUI desktop." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:50 +msgid "Start a terminal emulator." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:51 +msgid "" +"Start the installer by issuing the command below and follow the guided " +"steps." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:58 +msgid "On Windows:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:60 +msgid "Start the installer." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:61 +msgid "Follow the setup wizard." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:63 +msgid "For additional help, see the `VMware Workstation Player guide`_." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:66 +msgid "Download the latest |CL| installer ISO" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:68 +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/vmw-player.rst:71 +msgid "" +"Visit :ref:`image-types` for additional information about all available " +"|CL| images." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:4 +msgid "Verify the integrity of the |CL| image" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.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-windows.rst:11 +msgid "Download the corresponding SHA512 checksum file of your |CL| image." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:12 +msgid "Start Command Prompt." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:13 +msgid "Go to the directory with the downloaded image and checksum files." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:14 +msgid "Get the SHA512 checksum of the image with the command:" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.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-windows.rst:24 +msgid "Decompress the |CL| image" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.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-windows.rst:30 +msgid "Download and install `7-Zip`_." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.rst:31 +msgid "Go to the directory with the downloaded image and right-click it." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-windows.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-windows.rst:39 +msgid "Figure 1: Windows 7-Zip extract file." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:76 +msgid "We also provide instructions for other operating systems:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:78 +msgid ":ref:`download-verify-decompress-linux`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:79 +msgid ":ref:`download-verify-decompress-mac`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:82 +msgid "Create and configure a new VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:84 +msgid "Start the `VMware Workstation Player` app." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:86 +msgid "" +"On the home screen, click :guilabel:`Create a New Virtual Machine`. See " +"Figure 1." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:93 +msgid "Figure 1: VMware Workstation 14 Player - Create a new virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:96 +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:104 +msgid "Figure 2: VMware Workstation 14 Player - Select |CL| installer ISO" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:106 +msgid "" +"Click the :guilabel:`Browse` button and select the decompressed |CL| " +"installer ISO." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:109 +#: ../../get-started/virtual-machine-install/vmw-player.rst:125 +#: ../../get-started/virtual-machine-install/vmw-player.rst:136 +#: ../../get-started/virtual-machine-install/vmw-player.rst:151 +msgid "Click the :guilabel:`Next` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:111 +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:119 +msgid "" +"Figure 3: VMware Workstation 14 Player - Select guest operating system " +"type" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:122 +msgid "" +"Set the :guilabel:`Version` setting to :guilabel:`Other Linux 3.x or " +"later kernel 64-bit`." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:127 +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:134 +msgid "Figure 4: VMware Workstation 14 Player - Name virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:138 +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:145 +msgid "Figure 5: VMware Workstation 14 Player - Set disk capacity" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:148 +msgid "" +"A minimal |CL| installation can exist on 600MB 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 14 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 14 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 14 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 14 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:`` + :kbd:`` 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 14 Player - Edit CD/DVD settings" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:226 +msgid "Go to :menuselection:`Removable Devices-->CD/DVD (IDE)-->Settings`." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:228 +msgid "" +"On the :guilabel:`Device status` section, uncheck the " +":guilabel:`Connected` and the :guilabel:`Connect at power on` settings. " +"See Figure 11." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:236 +msgid "Figure 11: VMware Workstation 14 Player - Disconnect CD/DVD" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:238 +msgid "Click the :guilabel:`OK` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:240 +msgid "To power off the VM, click the :guilabel:`Player` menu. See Figure 12." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:246 +msgid "Figure 12: VMware Workstation 14 Player - Power off virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:248 +msgid "Go to :guilabel:`Power` and select :guilabel:`Shut Down Guest`." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:251 +msgid "Enable UEFI boot support" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:253 +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 "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:262 +msgid "Depending on the OS, you can typically find the VMware VM files under:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:264 +msgid "On Linux distros: :file:`/home/username/vmware`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:265 +msgid "" +"On Windows: :file:`C:\\\\Users\\\\username\\\\Documents\\\\Virtual " +"Machines`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:268 +msgid "Power on the VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:270 +msgid "After configuring the settings above, power on your |CL| virtual machine." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:272 +msgid "" +"On the :guilabel:`VMware Workstation Player` home screen, select your VM." +" See Figure 13." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:279 +msgid "Figure 13: VMware Workstation 14 Player - Power on virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:281 +msgid "Click :guilabel:`Play virtual machine`." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:284 +msgid "Related topics" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:286 +msgid "For other guides on using the VMWare Player and ESXi, see:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:288 +msgid ":ref:`vmw-player-preconf`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:289 +msgid ":ref:`vmware-esxi-install-cl`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmw-player.rst:290 +msgid ":ref:`vmware-esxi-preconfigured-cl-image`" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-install-cl.po b/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-install-cl.po new file mode 100644 index 00000000..f1ea673b --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-install-cl.po @@ -0,0 +1,477 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"`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 "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:10 +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 "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:13 +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 "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:17 +msgid "" +"If you would prefer to use a preconfigured |CL| VMware image instead, see" +" :ref:`vmware-esxi-preconfigured-cl-image`." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:22 +msgid "" +"VMware also offers a type 2 hypervisor called `VMware Workstation " +"Player`_ which is designed for the desktop environment." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:25 +msgid "See :ref:`vmw-player-preconf` or see :ref:`vmw-player`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:27 +msgid "Visit :ref:`image-types` to learn more about all available images." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:29 +msgid "Install steps:" +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 "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:4 +msgid "Decompress the |CL| image" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:6 +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:10 +msgid "Start a terminal emulator." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:11 +msgid "Go to the directory with the downloaded image." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:13 +msgid "To decompress an XZ image, enter:" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:19 +msgid "To decompress a GZ image, enter:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:45 +msgid "For alternative instructions on other operating systems, see:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:47 +msgid ":ref:`download-verify-decompress-mac`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:48 +msgid ":ref:`download-verify-decompress-windows`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:51 +msgid "Upload the |CL| installer ISO to the VMware server" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:53 +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:55 +msgid "" +"Under the :guilabel:`Navigator` window, select :guilabel:`Storage`. See " +"Figure 1." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:57 +msgid "" +"Under the :guilabel:`Datastores` tab, click the :guilabel:`Datastore " +"browser` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:64 +msgid "Figure 1: VMware ESXi - Navigator > Storage" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:66 +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:73 +msgid "Figure 2: VMware ESXi - Datastore > Create directory" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:75 +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:82 +msgid "Figure 3: VMware ESXi - Datastore > Upload ISO" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:84 +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:88 +msgid "Create and configure a new VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:90 +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:93 +msgid "" +"Under the :guilabel:`Navigator` window, select :guilabel:`Virtual " +"Machines`. See Figure 4." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:95 +msgid "In the right window, click the :guilabel:`Create / Register VM` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:101 +msgid "Figure 4: VMware ESXi - Navigator > Virtual Machines" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:103 +msgid "On the :guilabel:`Select creation type` step:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:105 +msgid "Select the :guilabel:`Create a new virtual machine` option. See Figure 5." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:107 +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:121 +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:132 +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:185 +msgid "Click the :guilabel:`Next` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:113 +msgid "Figure 5: VMware ESXi - Create a new virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:115 +msgid "On the :guilabel:`Select a name and guest OS` step:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:117 +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:118 +msgid "" +"Set the :guilabel:`Compatability` option to :guilabel:`ESXi 6.5 virtual " +"machine`." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:119 +msgid "Set the :guilabel:`Guest OS family` option to :guilabel:`Linux`." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:120 +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:127 +msgid "Figure 6: VMware ESXi - Give a name and select guest OS type" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:129 +msgid "On the :guilabel:`Select storage` step:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:131 +msgid "Accept the default option." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:134 +msgid "On the :guilabel:`Customize settings` step:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:136 +msgid "Click the :guilabel:`Virtual Hardware` button. See Figure 7." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:137 +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:144 +msgid "Figure 7: VMware ESXi - Enable hardware virtualization" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:146 +msgid "Set :guilabel:`Memory` size to 2048MB (2GB). See Figure 8." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:152 +msgid "Figure 8: VMware ESXi - Set memory size" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:156 +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:161 +msgid "Set :guilabel:`Hard disk 1` to the desired capacity. See Figure 9." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:167 +msgid "Figure 9: VMware ESXi - Set hard disk size" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:171 +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:174 +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:183 +msgid "Figure 10: VMware ESXi - Set CD/DVD to boot installer ISO" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:186 +msgid "Click the :guilabel:`Finish` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:189 +msgid "Install |CL| into the new VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:191 +msgid "Power on the VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:193 +msgid "" +"Under the :guilabel:`Navigator` window, select :guilabel:`Virtual " +"Machines`. See Figure 11." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:195 +msgid "In the right window, select the newly-created VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:196 +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:276 +msgid "Click the :guilabel:`Power on` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:197 +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:277 +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:204 +msgid "Figure 11: VMware ESXi - Navigator > Virtual Machines > Power on VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:206 +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:208 +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:212 +msgid "Reconfigure the VM's settings to boot the newly-installed |CL|" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:214 +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:218 +msgid "Power off the VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:220 +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:228 +msgid "Figure 12: VMware ESXi - Actions > Power off" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:230 +msgid "Edit the VM settings." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:232 +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:239 +msgid "Figure 13: VMware ESXi - Actions > Edit settings" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:241 +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:243 +msgid "Click the :guilabel:`Virtual Hardware` button. See Figure 14." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:244 +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:251 +msgid "Figure 14: VMware ESXi - Disconnect the CD/DVD drive" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:253 +msgid "|CL| needs UEFI support in order to boot. Enable it." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:255 +msgid "Click the :guilabel:`VM Options` button. See Figure 15." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:256 +msgid "Expand the :guilabel:`Boot Options` setting." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:257 +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:264 +msgid "Figure 15: VMware ESXi - Set boot firmware to EFI" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:266 +msgid "Click the :guilabel:`Save` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:269 +msgid "Power on the VM and boot |CL|" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:271 +msgid "After configuring the settings above, power on the VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:273 +msgid "" +"Under the :guilabel:`Navigator` window, select :guilabel:`Virtual " +"Machines`. See Figure 16." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:275 +msgid "In the right window, select the VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:284 +msgid "Figure 16: VMware ESXi - Navigator > Virtual Machines > Power on VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:287 +msgid "Related topics" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-install-cl.rst:289 +msgid ":ref:`vmware-esxi-preconfigured-cl-image`" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.po b/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.po new file mode 100644 index 00000000..1b58619a --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.po @@ -0,0 +1,466 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"`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:10 +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 "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:13 +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 "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:19 +msgid "" +"VMware also offers a type 2 hypervisor called `VMware Workstation Player`" +" which is designed for the desktop environment." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:22 +msgid "See :ref:`vmw-player-preconf` or see :ref:`vmw-player`." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:25 +msgid "Install steps:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:31 +msgid "Download the latest |CL| VMware image" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:33 +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:41 +msgid "" +"Visit :ref:`image-types` for additional information about all available " +"|CL| images." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:4 +msgid "Decompress the |CL| image" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:6 +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:10 +msgid "Start a terminal emulator." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:11 +msgid "Go to the directory with the downloaded image." +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:13 +msgid "To decompress an XZ image, enter:" +msgstr "" + +#: ../../guides/maintenance/download-verify-decompress-linux.rst:19 +msgid "To decompress a GZ image, enter:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:47 +msgid "For alternative instructions on other operating systems, see:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:49 +msgid ":ref:`download-verify-decompress-mac`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:50 +msgid ":ref:`download-verify-decompress-windows`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:53 +msgid "Upload the |CL| image to the VMware server" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:55 +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:59 +msgid "" +"The steps in this section can also be referenced from the `VMware " +"documentation on Using the Datastore File Browser`_" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:61 +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:64 +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:68 +msgid "" +"Under the :guilabel:`Datastores` tab, click the :guilabel:`Datastore " +"browser` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:75 +msgid "Figure 1: VMware ESXi - Navigator > Storage" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:77 +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:84 +msgid "Figure 2: VMware ESXi - Datastore > Create directory" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:86 +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:93 +msgid "Figure 3: VMware ESXi - Datastore > Upload VMware image" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:95 +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:99 +msgid "Convert the |CL| image to an ESXi-supported format" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:101 +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:105 +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:107 +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:112 +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 "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:116 +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:119 +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:122 +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:129 +msgid "Two files should result from this:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:131 +msgid ":file:`clear-[version number]-esxi-flat.vmdk`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:132 +msgid ":file:`clear-[version number]-esxi.vmdk`" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:134 +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:138 +msgid "Create and configure a new VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:140 +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:144 +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:147 +msgid "In the right window, click the :guilabel:`Create / Register VM` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:153 +msgid "Figure 4: VMware ESXi - Navigator > Virtual Machines" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:155 +msgid "On the :guilabel:`Select creation type` step:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:157 +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:160 +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:177 +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:188 +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:259 +msgid "Click the :guilabel:`Next` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:166 +msgid "Figure 5: VMware ESXi - Create a new virtual machine" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:168 +msgid "On the :guilabel:`Select a name and guest OS` step:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:170 +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:172 +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:174 +msgid "Set the :guilabel:`Guest OS family` option to :guilabel:`Linux`." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:175 +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:183 +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:185 +msgid "On the :guilabel:`Select storage` step:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:187 +msgid "Accept the default option." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:190 +msgid "On the :guilabel:`Customize settings` step:" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:192 +msgid "Click the :guilabel:`Virtual Hardware` button. See Figure 7." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:193 +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:201 +msgid "Figure 7: VMware ESXi - Enable hardware virtualization" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:203 +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:210 +msgid "Figure 8: VMware ESXi - Remove hard drive" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:212 +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:220 +msgid "Figure 9: VMware ESXi - Disconnect the CD/DVD drive" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:222 +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:225 +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:232 +msgid "Figure 10: VMware ESXi - Add an existing hard drive" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:234 +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:242 +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:245 +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:247 +msgid "Click the :guilabel:`VM Options` button. See Figure 12." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:248 +msgid "Expand the :guilabel:`Boot Options` setting." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:249 +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:256 +msgid "Figure 12: VMware ESXi - Set boot firmware to EFI" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:258 +msgid "Click the :guilabel:`Save` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:260 +msgid "Click the :guilabel:`Finish` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:263 +msgid "Power on the VM and boot |CL|" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:265 +msgid "After configuring the settings above, power on the VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:267 +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:269 +msgid "In the right window, select the newly-created VM." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:270 +msgid "Click the :guilabel:`Power on` button." +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.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-preconfigured-cl-image.rst:278 +msgid "Figure 13: VMware ESXi - Navigator > Virtual Machines > Power on VM" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:281 +msgid "Related topics" +msgstr "" + +#: ../../get-started/virtual-machine-install/vmware-esxi-preconfigured-cl-image.rst:283 +msgid ":ref:`vmware-esxi-install-cl`" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/deploy-at-scale.po b/locale/zh_CN/LC_MESSAGES/guides/deploy-at-scale.po new file mode 100644 index 00000000..60cb19e3 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/deploy-at-scale.po @@ -0,0 +1,414 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"Once you are comfortable with |CL-ATTR| :ref:`concepts `, your " +"next step as a system administrator is to understand how to deploy |CL| " +"at scale in your environment." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:10 +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 "" + +#: ../../guides/deploy-at-scale.rst:16 +msgid "" +"This is not a replacement or blueprint for designing your own IT " +"operating environment." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:19 +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 "" + +#: ../../guides/deploy-at-scale.rst:28 +msgid "Pick a |CL| usage and update strategy" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:30 +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:35 +msgid "Below is an overview of some considerations." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:38 +msgid "Create your own Linux distribution (mix)" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:40 +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 "" + +#: ../../guides/deploy-at-scale.rst:46 +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 "" + +#: ../../guides/deploy-at-scale.rst:50 +msgid "" +"swupd update webservers which are serving update content to production " +"machines (see `mixer process`_ for more information) should be " +"appropriately scaled." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:54 +msgid "" +"Your swupd update server is just like any other web application. |WEB-" +"SERVER-SCALE|" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:58 +msgid "Adopt an agile methodology" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:59 +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:62 +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:69 +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:72 +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:75 +msgid "" +"Setup a path to production for building |CL| based images. At minimum " +"this should include:" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:78 +msgid "" +"A development clr-on-clr environment to test building packages and " +"bundles for |CL| systems." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:81 +msgid "A pre-production environment to deploy |CL| versions to before production" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:84 +msgid "" +"Employ a continuous integration and continuous deployment (CI/CD) " +"philosophy in order to:" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:87 +msgid "" +"Automatically pull custom packages as they are updated from their " +"upstream projects or vendors." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:90 +msgid "" +"Generate |CL| bundles and potentially bootable images with your " +"customizations, if any." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:93 +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:96 +msgid "" +"Integrate with your organization's governance processes, such as change " +"control." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:100 +msgid "Versioning Infrastructure" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:102 +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:106 +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:109 +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:114 +msgid "Pick an image distribution strategy" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:116 +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:121 +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:125 +msgid "See the available :ref:`image-types`." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:127 +msgid "Below are some common ways to install |CL| to systems at scale:" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:130 +msgid "Baremetal" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:132 +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 "" + +#: ../../guides/deploy-at-scale.rst:136 +msgid "" +"This option works well if your customizations are fairly small in size " +"and infrastructure can be stateless." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:139 +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:144 +msgid "Cloud Instances or Virtual Machines" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:146 +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:150 +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:155 +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:160 +msgid "Containers" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:162 +msgid "" +"Containerization platforms allow images to be pulled from a repository " +"and deployed repeatedly as isolated containers." +msgstr "" + +#: ../../guides/deploy-at-scale.rst:165 +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:170 +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:175 +msgid "Considerations with stateless systems" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:176 +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:181 +msgid "Backup strategy" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:183 +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:187 +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 "" + +#: ../../guides/deploy-at-scale.rst:192 +msgid "Meaningful Logging & Telemetry" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:194 +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:197 +msgid "" +"Remote syslogging in |CL| is available through the `systemd journal-" +"remote service`_" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:200 +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 "" + +#: ../../guides/deploy-at-scale.rst:206 +msgid "" +"Your telemetry server is just like any other web application. |WEB-" +"SERVER-SCALE|" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:210 +msgid "Orchestration and Configuration Management" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:212 +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:215 +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 "" + +#: ../../guides/deploy-at-scale.rst:222 +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:228 +msgid "Cloud-native applications" +msgstr "" + +#: ../../guides/deploy-at-scale.rst:230 +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:235 +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 "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/guides.po b/locale/zh_CN/LC_MESSAGES/guides/guides.po new file mode 100644 index 00000000..b6b78e41 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/guides.po @@ -0,0 +1,44 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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:33 +msgid "Kernel" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/kernel/kernel-development.po b/locale/zh_CN/LC_MESSAGES/guides/kernel/kernel-development.po new file mode 100644 index 00000000..898885d0 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/kernel/kernel-development.po @@ -0,0 +1,539 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 document shows how to obtain and compile a Linux* kernel source " +"using |CL-ATTR| development tooling." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:9 +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 "" + +#: ../../guides/kernel/kernel-development.rst:18 +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 "" + +#: ../../guides/kernel/kernel-development.rst:22 +msgid "Request changes be included with the |CL| kernel" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:24 +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:28 +msgid "Make enhancement requests to the |CL| `distribution on GitHub`_ ." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:31 +msgid "Set up kernel development environment" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:33 +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:36 +msgid "You can build and install a custom kernel; however you must:" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:38 +msgid "Disable Secure Boot" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:39 +msgid "Maintain any updates to the kernel going forward" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:41 +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:46 +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:53 +msgid "Clone the kernel package" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:54 +msgid "" +"Clone the existing kernel package repository from |CL| as a starting " +"point." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:56 +msgid "" +"Clone the Linux kernel package from |CL|. Using the :command:`make " +"clone_` command in the :file:`clearlinux/` directory clones " +"the package from the `clearlinux-pkgs GitHub`_." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:66 +msgid "Navigate into the cloned package directory." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:73 +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 "" + +#: ../../guides/kernel/kernel-development.rst:80 +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/`." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:84 +msgid "Change the kernel version" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:86 +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:92 +#: ../../guides/kernel/kernel-development.rst:285 +msgid "Open the Linux kernel package RPM SPEC file in an editor." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:98 +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:101 +msgid "" +"A list of current and available kernel release can be found on " +"`kernel.org`_." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:120 +msgid "" +"Consider changing the Name from *linux* in the RPM spec file to easily " +"identify a modified kernel." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:122 +msgid "" +"Consider changing the ktarget from *native* in the RPM spec file to " +"easily identify a modified kernel." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:124 +msgid "Commit and save the changes to the file." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:127 +msgid "Pull a copy of the Linux kernel source code" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:129 +msgid "Obtain a local copy of the source code to make modifications against." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:131 +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:139 +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:146 +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:155 +msgid "Customize the Linux kernel source" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:157 +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:162 +msgid "Modify kernel configuration" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:164 +msgid "" +"The kernel source has many configuration options available to pick " +"support for different hardware and software features." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:166 +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:171 +#: ../../guides/kernel/kernel-development.rst:228 +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 "" + +#: ../../guides/kernel/kernel-development.rst:176 +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:185 +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:188 +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:191 +msgid "" +":command:`make config` - a text-based tool that asks questions one-by-one" +" to decide configuration options." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:194 +msgid "" +":command:`make menuconfig` - a terminal user interface that provides " +"menus to decide configuration options." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:197 +msgid "" +":command:`make xconfig` - a graphical user interface that provides tree " +"views to decide configuration options." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:201 +msgid "" +"More configuration tools can be found by looking at the make help: " +":command:`make help | grep config`" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:204 +msgid "Commit and save the changes to the :file:`.config` file." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:206 +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:214 +msgid "Modify kernel source code" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:216 +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:219 +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:223 +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:233 +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:243 +msgid "" +"Apply patches provided by the |CL| kernel package to the kernel source in" +" the working directory." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:251 +msgid "Make any of your desired code changes to the Linux source code files." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:254 +msgid "Track and commit your changes to the local git repo." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:262 +msgid "" +"Generate a patch file based on your git commits. 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:271 +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:279 +msgid "Navigate back to the RPM build directory." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:291 +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:314 +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:333 +msgid "Commit and save the changes to the RPM SPEC file." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:336 +msgid "Modify kernel boot parameters" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:337 +msgid "" +"The kernel boot options are passed from the bootloader to the kernel with" +" command-line parameters." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:340 +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:345 +msgid "Open the kernel :file:`cmdline` file in an editor." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:352 +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:356 +msgid "Commit and save the changes to the :file:`cmdline` file." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:358 +msgid "" +"See the `Kernel parameters documentation`_ for a list of available " +"parameters." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:362 +msgid "Build and install the kernel" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:363 +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:366 +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:369 +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:377 +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 "" + +#: ../../guides/kernel/kernel-development.rst:380 +msgid "" +"The result will be multiple :file:`.rpm` files in the :file:`rpms` " +"directory as output." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:387 +msgid "" +"The kernel RPM will be named " +":file:`linux--.x86_64.rpm`" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:391 +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:394 +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:399 +msgid "" +"Install the kernel onto the local system by extracting the RPM with the " +":command:`rpm2cpio` command." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:407 +msgid "Update the |CL| boot manager using :command:`clr-boot-manager` and reboot." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:417 +msgid "After a reboot, verify the customized kernel is running." +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:424 +msgid "Related topics" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:426 +msgid ":ref:`kernel-modules`" +msgstr "" + +#: ../../guides/kernel/kernel-development.rst:427 +msgid ":ref:`mixer`" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/kernel/kernel-modules-dkms.po b/locale/zh_CN/LC_MESSAGES/guides/kernel/kernel-modules-dkms.po new file mode 100644 index 00000000..4344ce30 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/kernel/kernel-modules-dkms.po @@ -0,0 +1,483 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"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:18 +msgid "Description" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:20 +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:25 +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 `on GitHub`_." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:39 +msgid "Install DKMS" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:43 +msgid "" +"The *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:46 +msgid "The *kernel-native-dkms* bundle also:" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:48 +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 `." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:53 +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:57 +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:62 +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:68 +msgid "" +"Install the :command:`kernel-native-dkms` or :command:`kernel-lts-dkms` " +"bundle:" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:71 +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:80 +msgid "Ensure *.native* or *.lts* is in the kernel name." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:82 +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:90 +msgid "or" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:97 +msgid "Update the |CL| bootloader and reboot." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:108 +msgid "Build, install, and load an out-of-tree module" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:110 +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 "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:117 +msgid "Prerequisites" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:119 +msgid "Before you begin, you must:" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:121 +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:124 +msgid "" +"Obtain a kernel module package in the form of source code and/or " +"precompiled binaries." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:130 +msgid "Obtain kernel module source" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:132 +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:135 +msgid "Kernel modules may come packaged as:" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:137 +msgid "Source code without a :file:`dkms.conf` file" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:138 +msgid "Source code with a premade :file:`dkms.conf` file" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:139 +msgid "" +"Source code with a premade :file:`dkms.conf` file and precompiled module " +"binaries" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:141 +msgid "Precompiled module binaries only (without source code)" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:143 +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:149 +msgid "Download the kernel module's source code." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:151 +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:154 +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:166 +msgid "Build kernel module with an existing dkms.conf" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:168 +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:172 +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:177 +msgid "" +"Run the :command:`dkms ldtarball` command against the kernel module " +"archive." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:184 +msgid "" +":command:`dkms ldtarball` places the kernel module source under " +":file:`/usr/src/-/`, builds it if necessary," +" and adds the module into the DKMS tree." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:189 +msgid "" +"Verify the kernel module is detected by checking the output of the " +":command:`dkms status` command." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:197 +msgid "Install the kernel module." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:206 +msgid "Build kernel module without an existing dkms.conf" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:208 +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:212 +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:216 +msgid "Here are some additional resources that can be used for reference:" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:218 +msgid "" +"DKMS manual page (:command:`man dkms`) shows detailed syntax in the " +"DKMS.CONF section." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:221 +msgid "" +"`Ubuntu community wiki`_ shows an example where a single package contains" +" multiple modules." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:224 +msgid "`Sample dkms.conf file`_ in the GitHub\\* repository for the DKMS project." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:228 +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:231 +msgid "The instructions below show a generic example:" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:233 +msgid "" +"Create or modify the :file:`dkms.conf` file inside of the extracted " +"source code directory." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:249 +msgid "" +"This example identifies a kernel module named *custom_module* with " +"version *1.0*." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:252 +msgid "Copy the kernel module source code into the :file:`/usr/src/` directory." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:261 +msgid "" +"** and ** must match the entries in the " +":file:`dkms.conf` file." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:265 +msgid "Add the kernel module to the DKMS tree so that it is tracked by DKMS." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:271 +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:278 +msgid "Install the kernel module using DKMS." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:287 +msgid "Load kernel module" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:289 +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:292 +msgid "Load the installed module with the :command:`modprobe` command." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:298 +msgid "Validate the kernel module is loaded." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:306 +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:316 +msgid "Related topics" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:318 +msgid "" +"`Dynamic Kernel Module System (DKMS) project on GitHub " +"`_" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:320 +msgid "" +"`Dell Linux Engineering Dynamic Kernel Module Support: From Theory to " +"Practice " +"`_" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:322 +msgid "" +"`Linux Journal: Exploring Dynamic Kernel Module Support " +"`_" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/kernel/kernel-modules.po b/locale/zh_CN/LC_MESSAGES/guides/kernel/kernel-modules.po new file mode 100644 index 00000000..a6dadc38 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/kernel/kernel-modules.po @@ -0,0 +1,267 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"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:17 +msgid "Description" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:19 +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:28 +msgid "Kernel module availability" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:30 +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:35 +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:40 +msgid "Check if the module is already available" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:43 +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:53 +msgid "Submit a request to add the module" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:55 +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:59 +msgid "Make enhancement requests to the |CL| distribution `on GitHub`_." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:65 +msgid "Build, install, and load an out-of-tree module" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:67 +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 "" + +#: ../../guides/kernel/kernel-modules.rst:74 +msgid "Prerequisites" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:76 +msgid "Before you begin, you must:" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:78 +msgid "Disable Secure Boot." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:79 +msgid "Disable kernel module integrity checking." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:80 +msgid "Have a kernel module package in the form of source code." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:81 +msgid "Rebuild the module against new versions of the Linux kernel." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:85 +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:90 +msgid "Build and install kernel module" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:92 +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:100 +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:104 +msgid "`linux-dev` for developing against the native kernel." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:105 +msgid "`linux-lts-dev` for developing against the LTS kernel." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:111 +msgid "" +"Follow instructions from the kernel module source code to compile the " +"kernel module. For example:" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:124 +msgid "Load kernel module" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:126 +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:130 +msgid "" +"Disable signature checking for the kernel by modifying the kernel boot " +"parameters and reboot the system." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:133 +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:142 +msgid "" +"Update the boot manager and reboot the system to implement the changed " +"kernel parameters." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:152 +msgid "" +"If successful, the :command:`clr-boot-manager update` command does not " +"return any console output." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:155 +msgid "" +"After rebooting, manually load out-of-tree modules using the " +":command:`insmod` command." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:163 +msgid "Examples" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:168 +msgid "Optional: Specify module options and aliases" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:170 +msgid "Use the :command:`modprobe` command to load a module and set options." +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:172 +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:180 +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:185 +msgid "Learn more about :command:`modprobe` on the modprobe.d manual page:" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:192 +msgid "Optional: Configure kernel modules to load at boot" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:194 +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:201 +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:205 +msgid "Learn more about module loading in the modules-load.d manual page:" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:215 +msgid "Related topic" +msgstr "" + +#: ../../guides/kernel/kernel-modules.rst:217 +msgid ":ref:`kernel-modules-dkms`" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/maintenance/architect-lifecycle.po b/locale/zh_CN/LC_MESSAGES/guides/maintenance/architect-lifecycle.po new file mode 100644 index 00000000..df13bcac --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/maintenance/architect-lifecycle.po @@ -0,0 +1,137 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 provides DevOps with a model to architect the life-cycle of a " +"|CL| derivative that integrates custom software and content using " +"distinct workflows." +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:10 +msgid "Maintaining a |CL| derivative requires:" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:12 +msgid "Monitoring upstream |CL| for new releases" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:13 +msgid "Building software packages and staging" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:14 +msgid "Employing CI/CD automation for building releases" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:15 +msgid "Integrating Quality Assurance for testing and validation" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:17 +msgid "This guide provides the foundation of the recommended infrastructure." +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:24 +msgid "Prerequisites" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:26 +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:29 +msgid "Experience using :ref:`mixer ` to create a |CL|-based distro" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:31 +msgid "" +"Experience using :ref:`swupd ` for maintaining the |CL| " +"build environment" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:34 +msgid "Familiarity with |CL| architecture and reuse of its content in releases" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:37 +msgid "Description" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:39 +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 "" + +#: ../../guides/maintenance/architect-lifecycle.rst:48 +msgid "Figure 1: Architect the life-cycle" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:51 +msgid "Content workflow" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:53 +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:57 +msgid "Release workflow" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:59 +msgid "" +"The *Release Workflow* (Figure 1) gathers the content of the RPMs and " +"ensures it can be consumed by :ref:`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:68 +msgid "Implementation" +msgstr "" + +#: ../../guides/maintenance/architect-lifecycle.rst:70 +msgid "" +"Distro factory implements the *Release workflow*. To get started on a " +"full implementation, visit |CL| `Distro factory documentation`_." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/maintenance/assign-static-ip.po b/locale/zh_CN/LC_MESSAGES/guides/maintenance/assign-static-ip.po new file mode 100644 index 00000000..e8a36566 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/maintenance/assign-static-ip.po @@ -0,0 +1,211 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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:6 +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 "" + +#: ../../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| 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, you " +"should 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 and the " +"instructions for :ref:`using NetworkManager ` should be " +"used." +msgstr "" + +#: ../../guides/maintenance/assign-static-ip.rst:43 +msgid "" +"If the STATE column for the device shows *unmanaged*, check to see 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 and the instructions " +"for :ref:`using systemd-networkd ` should be used." +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 "The output will look like this:" +msgstr "" + +#: ../../guides/maintenance/assign-static-ip.rst:95 +msgid "" +"If a connection does not exist, it will need to be created with " +":command:`nmcli connection add`." +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. *[CONNECTION_NAME]* should be " +"replaced with the NAME from the command above." +msgstr "" + +#: ../../guides/maintenance/assign-static-ip.rst:112 +msgid "" +"See the `nmcli developer page " +"`_ 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 doesn't exist " +"already:" +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. *[INTERFACE_NAME]* " +"should be replaced with LINK from the output of :command:`networkctl " +"list` ran previously." +msgstr "" + +#: ../../guides/maintenance/assign-static-ip.rst:168 +msgid "" +"See the `systemd-network man page " +"`_" +" for more configuration options." +msgstr "" + +#: ../../guides/maintenance/assign-static-ip.rst:172 +msgid "Restart the systemd-networkd service:" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/maintenance/bulk-provision.po b/locale/zh_CN/LC_MESSAGES/guides/maintenance/bulk-provision.po new file mode 100644 index 00000000..47c5eae9 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/maintenance/bulk-provision.po @@ -0,0 +1,201 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"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 "" + +#: ../../guides/maintenance/bulk-provision.rst:11 +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 "" + +#: ../../guides/maintenance/bulk-provision.rst:17 +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:23 +msgid "Figure 1: Bulk provision information flow" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:26 +msgid "Prerequisites" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:28 +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` using :abbr:`NAT (network " +"address translation)` for details." +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:33 +msgid "" +"Because a bulk provision relies on a reboot, ensure the following " +"preparations have been made:" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:36 +msgid "No existing disks are bootable." +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:37 +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:41 +msgid "Configuration" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:43 +msgid "" +"Install **ICIS** by following the getting started guide on the `ICIS " +"GitHub repository`_." +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:46 +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:85 +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 "" + +#: ../../guides/maintenance/bulk-provision.rst:90 +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:99 +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:114 +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:118 +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 "" + +#: ../../guides/maintenance/bulk-provision.rst:123 +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:127 +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 "" + +#: ../../guides/maintenance/bulk-provision.rst:137 +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:146 +msgid "Verify the following URLs are accessible on your local network:" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:148 +msgid "``http://192.168.1.1:60000/icis/static/ister/ister.conf``" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:149 +msgid "``http://192.168.1.1:60000/icis/static/ister/ister.json``" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:150 +msgid "``http://192.168.1.1:60000/icis/get_config/``" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:151 +msgid "``http://192.168.1.1:60000/icis/get_role/``" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:152 +msgid "``http://192.168.1.1:60000/ipxe/ipxe_boot_script.txt``" +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:154 +msgid "Power on the PXE client and watch it boot and install |CL|." +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:156 +msgid "Power-cycle the PXE client and watch it customize the |CL| installation." +msgstr "" + +#: ../../guides/maintenance/bulk-provision.rst:158 +msgid "" +"**Congratulations!** You have successfully performed a bulk provision of " +"|CL|." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/maintenance/cpu-performance.po b/locale/zh_CN/LC_MESSAGES/guides/maintenance/cpu-performance.po new file mode 100644 index 00000000..8f73d394 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/maintenance/cpu-performance.po @@ -0,0 +1,257 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"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:9 +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:18 +msgid "CPU power saving mechanisms" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:20 +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:27 +msgid "C-states (idle states)" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:29 +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:32 +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:35 +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:39 +msgid "To view the current cpuidle driver run this command in a terminal:" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:45 +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:51 +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:53 +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:59 +msgid "P-states (performance states)" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:61 +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 "" + +#: ../../guides/maintenance/cpu-performance.rst:65 +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:68 +msgid "" +"P-states can typically be limited or disabled in a system's firmware " +"(UEFI/BIOS)." +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:71 +msgid "Turbo boost" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:73 +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 "" + +#: ../../guides/maintenance/cpu-performance.rst:78 +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:81 +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:89 +msgid "Linux CPU clock frequency scaling" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:91 +msgid "" +"The CPUFreq subsystem in Linux allows the OS to control :ref:`C-states ` and :ref:`P-states ` via CPU drivers " +"and governors that provide algorithms that define how and when to enter " +"these states." +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:97 +msgid "Scaling driver" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:99 +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 "" + +#: ../../guides/maintenance/cpu-performance.rst:104 +msgid "" +"To view the current CPU frequency scaling driver run this command in a " +"terminal:" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:111 +msgid "Scaling governor" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:113 +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:119 +msgid "" +"To view the current CPU frequency scaling governor run this command in a " +"terminal:" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:125 +msgid "To change the CPU frequency scaling governor:" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:127 +msgid "Disable |CL| enforcement of certain power and performance settings:" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:133 +msgid "" +"Change the governor. In the example below, the governor is set to " +"*performance*:" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:140 +msgid "" +"The list of all governors can be found in the `Linux kernel documentation" +" on CPUFreq Governors`_." +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:145 +msgid "" +"The intel_pstate driver only supports *performance* and *powersave* " +"governors." +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:148 +msgid "Thermal management" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:150 +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:155 +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:164 +msgid "For more information, see the thermald man page:" +msgstr "" + +#: ../../guides/maintenance/cpu-performance.rst:170 +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 "" + +#: ../../guides/maintenance/cpu-performance.rst:182 +msgid "" +"After adding a new group you must log out and log back in for the new " +"group to take affect." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/maintenance/developer-workstation.po b/locale/zh_CN/LC_MESSAGES/guides/maintenance/developer-workstation.po new file mode 100644 index 00000000..283c668f --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/maintenance/developer-workstation.po @@ -0,0 +1,196 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"*Developer Workstation* helps you find the :ref:`bundles-about` you need " +"to start your |CL-ATTR| development project." +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:9 +msgid "" +"Before continuing, we recommend that you learn how to use :ref:`swupd " +"`. Visit our :ref:`swupd-about` page to understand how |CL| " +"simplifies software versioning compared to other Linux\\* distributions." +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:15 +msgid "Workstation Setup" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:17 +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* `. 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 "" + +#: ../../guides/maintenance/developer-workstation.rst:25 +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 "" + +#: ../../guides/maintenance/developer-workstation.rst:29 +msgid "**Table 1. Developer Profiles**" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:33 +msgid "|CL| Bundle" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:34 +msgid "*Internet of Things (IoT)*" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:35 +msgid "*System Administrator*" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:36 +msgid "*Client/Cloud/Web Developer*" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:38 +msgid "`editors`" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:39 +#: ../../guides/maintenance/developer-workstation.rst:40 +#: ../../guides/maintenance/developer-workstation.rst:41 +#: ../../guides/maintenance/developer-workstation.rst:44 +#: ../../guides/maintenance/developer-workstation.rst:45 +#: ../../guides/maintenance/developer-workstation.rst:46 +#: ../../guides/maintenance/developer-workstation.rst:49 +#: ../../guides/maintenance/developer-workstation.rst:50 +#: ../../guides/maintenance/developer-workstation.rst:51 +#: ../../guides/maintenance/developer-workstation.rst:55 +#: ../../guides/maintenance/developer-workstation.rst:56 +#: ../../guides/maintenance/developer-workstation.rst:60 +#: ../../guides/maintenance/developer-workstation.rst:61 +#: ../../guides/maintenance/developer-workstation.rst:65 +#: ../../guides/maintenance/developer-workstation.rst:66 +#: ../../guides/maintenance/developer-workstation.rst:69 +#: ../../guides/maintenance/developer-workstation.rst:70 +#: ../../guides/maintenance/developer-workstation.rst:71 +#: ../../guides/maintenance/developer-workstation.rst:76 +msgid "✓" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:43 +msgid "`network-basic`" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:48 +msgid "`openssh-server`" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:53 +msgid "`webserver-basic`" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:58 +msgid "`application-server`" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:63 +msgid "`database-basic`" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:68 +msgid "`desktop-autostart`" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:73 +msgid "`dev-utils`" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:79 +msgid "`swupd` search" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:81 +msgid "" +"We recommend learning about :ref:`swupd `, to learn the " +"commands to search for and add bundles relevant to your project." +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:84 +msgid "" +"The guide provides an :ref:`example `" +" that shows you how to:" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:87 +msgid "Use `swupd` to search for bundles" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:88 +msgid "Use `swupd` to add bundles" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:91 +msgid "Core Concepts" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:93 +msgid "" +"We recommend that you understand these core concepts in |CL| *before* " +"developing your project." +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:96 +msgid ":ref:`Bundles `" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:97 +msgid ":ref:`Software update `" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:98 +msgid ":ref:`Mixer `" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:99 +msgid ":ref:`Autospec `" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:102 +msgid "Other resources for developers" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:104 +msgid "`Developer Tooling Framework`_ for |CL|" +msgstr "" + +#: ../../guides/maintenance/developer-workstation.rst:105 +msgid "`Bundle definition files`_" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/maintenance/download-verify-decompress-linux.po b/locale/zh_CN/LC_MESSAGES/guides/maintenance/download-verify-decompress-linux.po new file mode 100644 index 00000000..2bd2ccf6 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/maintenance/download-verify-decompress-linux.po @@ -0,0 +1,282 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/maintenance/download-verify-decompress-mac.po b/locale/zh_CN/LC_MESSAGES/guides/maintenance/download-verify-decompress-mac.po new file mode 100644 index 00000000..5e08c128 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/maintenance/download-verify-decompress-mac.po @@ -0,0 +1,273 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/maintenance/download-verify-decompress-windows.po b/locale/zh_CN/LC_MESSAGES/guides/maintenance/download-verify-decompress-windows.po new file mode 100644 index 00000000..928bbb5d --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/maintenance/download-verify-decompress-windows.po @@ -0,0 +1,277 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/maintenance/enable-user-space.po b/locale/zh_CN/LC_MESSAGES/guides/maintenance/enable-user-space.po new file mode 100644 index 00000000..6c14ed97 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/maintenance/enable-user-space.po @@ -0,0 +1,155 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 section 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 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 ``." +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:35 +msgid "" +"To be able to execute all applications with root privileges, add the " +"`` to the `wheel group`_." +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:38 +msgid "Add `` to the `wheel` group:" +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:44 +msgid "Log out of root and into the new ``." +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 `` and the password created earlier." +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:50 +msgid "You will now be in the home directory of ``." +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 ` allows you to " +"perform system updates while reaping the benefits of upstream " +"development." +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:57 +msgid "To update your newly installed OS, run:" +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:64 +msgid "Add a bundle" +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:66 +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 "" + +#: ../../guides/maintenance/enable-user-space.rst:72 +msgid "" +"For example, the `sysadmin-basic` bundle installs the majority of " +"applications useful to a system administrator. To install it, enter:" +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:78 +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:80 +msgid "" +"Expand your knowledge of :command:`swupd` and check out our developer " +"resources:" +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:82 +msgid ":ref:`swupd-guide`" +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:83 +msgid ":ref:`developer-workstation`" +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:86 +msgid "Next steps" +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:88 +msgid "Check out our guides and tutorials." +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:90 +msgid ":ref:`guides`" +msgstr "" + +#: ../../guides/maintenance/enable-user-space.rst:91 +msgid ":ref:`tutorials`" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/maintenance/fix-broken-install.po b/locale/zh_CN/LC_MESSAGES/guides/maintenance/fix-broken-install.po new file mode 100644 index 00000000..befb7e98 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/maintenance/fix-broken-install.po @@ -0,0 +1,159 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 of |CL-ATTR|" +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:6 +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 "" + +#: ../../guides/maintenance/fix-broken-install.rst:10 +msgid "" +"This process can only verify and fix files that :ref:`swupd`" +" owns in :file:`/usr`. Files outside of this path, such as /home/, /etc, " +"/var, etc., cannot be repaired by this process." +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:15 +msgid "Prerequisites" +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:17 +msgid "" +":ref:`Download and install the live desktop image on a USB `" +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:20 +msgid "Boot a live desktop image to fix target system" +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:22 +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:29 +msgid "Mount root partition, verify, and fix" +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:31 +msgid "Open a Terminal window." +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:33 +msgid "Assure the system is connected to the network." +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:35 +msgid "Mount the system’s root partition." +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:37 +msgid "To find the root partition, run:" +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:43 +msgid "We'll use `/dev/sda3/` as the root partition example." +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:45 +msgid "Next, mount the partition to the `/mnt` folder." +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:51 +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:59 +msgid "Next, run swupd to fix any issues on the target system." +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:65 +msgid ":ref:`Learn more about how swupd works `." +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:67 +msgid "After the process is complete, unmount the root partition:" +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:73 +msgid "" +"Reboot the system, remove the live desktop USB drive, and boot into the " +"repaired system." +msgstr "" + +#: ../../guides/maintenance/fix-broken-install.rst:80 +msgid "**Congratulations!** You successfully restored |CL|." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/maintenance/hostname.po b/locale/zh_CN/LC_MESSAGES/guides/maintenance/hostname.po new file mode 100644 index 00000000..49c9c89b --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/maintenance/hostname.po @@ -0,0 +1,110 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 on |CL-ATTR|" +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:9 +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:17 +msgid "*regression-test*" +msgstr "" + +#: ../../guides/maintenance/hostname.rst:18 +msgid "*sally-test-box1*" +msgstr "" + +#: ../../guides/maintenance/hostname.rst:19 +msgid "*az-bldg2-lab*" +msgstr "" + +#: ../../guides/maintenance/hostname.rst:22 +msgid "Set your hostname" +msgstr "" + +#: ../../guides/maintenance/hostname.rst:24 +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 "" + +#: ../../guides/maintenance/hostname.rst:28 +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:39 +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:44 +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:48 +msgid "" +"The pretty hostname is a free-form UTF8 name used for presentation to the" +" user." +msgstr "" + +#: ../../guides/maintenance/hostname.rst:51 +msgid "View your hostname" +msgstr "" + +#: ../../guides/maintenance/hostname.rst:53 +msgid "View your current hostname using the following command:" +msgstr "" + +#: ../../guides/maintenance/hostname.rst:59 +msgid "You should see output similar to:" +msgstr "" + +#: ../../guides/maintenance/hostname.rst:74 +msgid "" +"**Congratulations!** You successfully modified the hostname of your |CL| " +"system." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/maintenance/increase-virtual-disk-size.po b/locale/zh_CN/LC_MESSAGES/guides/maintenance/increase-virtual-disk-size.po new file mode 100644 index 00000000..b2dfd8ac --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/maintenance/increase-virtual-disk-size.po @@ -0,0 +1,245 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 a |CL-ATTR| image" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:6 +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 "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:10 +msgid "This guide will cover:" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:13 +msgid "Determine the partition order and sizes of the prebuilt image" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:15 +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:18 +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 "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:22 +msgid "Checking :command:`lsblk` on the VM" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:24 +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:31 +msgid "An example output of the :command:`lsblk` command:" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:41 +msgid "An example of this can also be seen in Figure 1." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:44 +msgid "Checking :file:`config.json` used to build the image" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:46 +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:51 +msgid "Go to the `releases`_ repository." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:52 +msgid "Drill down into the `20450 > clear > config > image` directory." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:53 +msgid "Open the :file:`hyperv-config.json` file." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:54 +msgid "Locate the `PartitionLayout` key." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:56 +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:76 +msgid "Increase virtual disk size" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:77 +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:81 +msgid "Power off VM and increase virtual disk size:" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:83 +msgid "" +"To increase the virtual disk size for a prebuilt image, perform the steps" +" below:" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:86 +msgid "Shut down your VM if it is running." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:87 +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:90 +msgid "Power up the VM." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:94 +msgid "Resize the partition of the virtual disk:" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:96 +msgid "Log in to an account with root privileges." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:97 +msgid "Open a terminal emulator." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:98 +msgid "" +"Add the |CL| `storage-utils` bundle to install the :command:`parted` and " +":command:`resize2fs` tools." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:105 +msgid "Launch the `parted` tool." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:111 +msgid "In the `parted` tool, perform these steps:" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:113 +msgid "Press :command:`p` to print the partitions table." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:114 +msgid "If the warning message below is displayed, enter :command:`Fix`." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:124 +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:126 +msgid "Enter :command:`yes` when prompted." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:127 +msgid "Enter the new `End` size." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:131 +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 "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:136 +msgid "An example of this can be seen in Figure 1." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:138 +msgid "" +"Enter :command:`q` to exit `parted` when you are finished resizing the " +"image." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:141 +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:147 +msgid "Figure 1: Increase root partition size." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:150 +msgid "Resize the filesytem" +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:152 +msgid "" +"Enter :command:`sudo resize2fs -p /dev/[modified partition name]` where " +"*[modified partition name]* is the partition that was changed in " +"`parted`." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:155 +msgid "Run the :command:`df -h` to verify that the filesystem size has increased." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:158 +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:164 +msgid "Figure 2: Increase root filesystem size after partition has been expanded." +msgstr "" + +#: ../../guides/maintenance/increase-virtual-disk-size.rst:166 +msgid "" +"Congratulations! You have resized the disk, partition, and filesystem. At" +" this point, the increase in disk capacity is usable." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/maintenance/time.po b/locale/zh_CN/LC_MESSAGES/guides/maintenance/time.po new file mode 100644 index 00000000..48c75bf6 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/maintenance/time.po @@ -0,0 +1,78 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "|CL-ATTR| uses the `systemd-timesyncd.service` daemon to synchronize time." +msgstr "" + +#: ../../guides/maintenance/time.rst:8 +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 "" + +#: ../../guides/maintenance/time.rst:11 +msgid "Install the `sysadmin-basic` bundle." +msgstr "" + +#: ../../guides/maintenance/time.rst:17 +msgid "Set your time zone. This example uses Los Angeles." +msgstr "" + +#: ../../guides/maintenance/time.rst:25 +msgid "" +"To see a list of time zones, use the command: :command:`timedatectl list-" +"timezones | grep `" +msgstr "" + +#: ../../guides/maintenance/time.rst:28 +msgid "Create a :file:`/etc/systemd/` directory." +msgstr "" + +#: ../../guides/maintenance/time.rst:34 +msgid "" +"Create a new file named :file:`/etc/systemd/timesyncd.conf` and enter the" +" following text." +msgstr "" + +#: ../../guides/maintenance/time.rst:43 +msgid "Enable the `systemd-timesyncd` service." +msgstr "" + +#: ../../guides/maintenance/time.rst:51 +msgid "" +"To check the service status, use the :command:`timedatectl status` " +"command." +msgstr "" + +#: ../../guides/maintenance/time.rst:53 +msgid "" +"To restart the `timesyncd` daemon, enter :command:`systemctl restart " +"systemd-timesyncd` into your terminal emulator." +msgstr "" + +#: ../../guides/maintenance/time.rst:56 +msgid "**Congratulations!** You successfully set up the time in your |CL| system." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/maintenance/validate-signatures.po b/locale/zh_CN/LC_MESSAGES/guides/maintenance/validate-signatures.po new file mode 100644 index 00000000..82f9392d --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/maintenance/validate-signatures.po @@ -0,0 +1,142 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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:6 +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 "" + +#: ../../guides/maintenance/validate-signatures.rst:11 +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 "" + +#: ../../guides/maintenance/validate-signatures.rst:18 +msgid "Image content validation" +msgstr "" + +#: ../../guides/maintenance/validate-signatures.rst:20 +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 "" + +#: ../../guides/maintenance/validate-signatures.rst:23 +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:35 +msgid "Generate the SHA256 sum of the |CL| certificate." +msgstr "" + +#: ../../guides/maintenance/validate-signatures.rst:41 +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:48 +msgid "Generate the SHA512 sum of the image and save it to a file." +msgstr "" + +#: ../../guides/maintenance/validate-signatures.rst:54 +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 "" + +#: ../../guides/maintenance/validate-signatures.rst:64 +#: ../../guides/maintenance/validate-signatures.rst:115 +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 "" + +#: ../../guides/maintenance/validate-signatures.rst:69 +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:73 +msgid "Update content validation" +msgstr "" + +#: ../../guides/maintenance/validate-signatures.rst:75 +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 "" + +#: ../../guides/maintenance/validate-signatures.rst:80 +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:92 +msgid "Generate the SHA256 sum of the Swupd certificate." +msgstr "" + +#: ../../guides/maintenance/validate-signatures.rst:98 +msgid "" +"Ensure the generated SHA256 sum of the Swupd certificate matches " +"following SHA256 sum to verify the integrity of the certificate." +msgstr "" + +#: ../../guides/maintenance/validate-signatures.rst:105 +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 "" + +#: ../../guides/maintenance/validate-signatures.rst:122 +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:126 +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 "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/network/custom-clear-container.po b/locale/zh_CN/LC_MESSAGES/guides/network/custom-clear-container.po new file mode 100644 index 00000000..446b005f --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/network/custom-clear-container.po @@ -0,0 +1,177 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"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 "" + +#: ../../guides/network/custom-clear-container.rst:11 +msgid "Prerequisites" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:13 +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:16 +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:18 +msgid "You have a basic understanding of Docker." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:21 +msgid "Build the base container image" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:23 +msgid "Log in and get root privileges." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:29 +msgid "Verify Docker is installed and running." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:35 +msgid "If Docker is installed and running, the output is similar to this example:" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:78 +msgid "If Docker is not installed, enter the commands:" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:85 +msgid "Use `os-install` to download and install the bundles." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:92 +msgid "The `swupd` example uses the following flags:" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:94 +msgid ":command:`os-install` tells `swupd` to download and install." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:95 +msgid ":command:`-V / --version` specifies the version of the |CL| bundles." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:96 +msgid ":command:`--url` specifies the URL of the bundles repository." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:97 +msgid "" +":command:`--statedir` specifies the state directory where downloaded " +"bundles and any state information are stored." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:99 +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:102 +msgid "" +"For more information on `swupd` flags, enter the :command:`swupd os-" +"install -h` command." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:104 +#: ../../guides/network/custom-clear-container.rst:167 +#: ../../guides/network/custom-clear-container.rst:194 +#: ../../guides/network/custom-clear-container.rst:228 +#: ../../guides/network/custom-clear-container.rst:290 +msgid "Example output:" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:141 +msgid "The `WARNING` message is expected and can be ignored." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:143 +msgid "Create a tarball and compress it." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:150 +msgid "Create the Dockerfile to build the image." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:161 +msgid "Build the |CL| container image." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:188 +msgid "List the newly created |CL| container image." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:201 +msgid "Launch the built |CL| container." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:208 +msgid "Manage bundles in a container" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:210 +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:214 +msgid "Add a bundle" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:216 +msgid "" +"This example Dockerfile adds the :file:`pxe-server` bundle to an existing" +" |CL| Docker image:" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:272 +msgid "" +"The `WARNING` message can be ignored because systemd does not run inside " +"a container." +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:276 +msgid "Remove a bundle" +msgstr "" + +#: ../../guides/network/custom-clear-container.rst:278 +msgid "" +"This example Dockerfile removes the :file:`pxe-server` bundle from an " +"existing |CL| Docker image:" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/network/dpdk.po b/locale/zh_CN/LC_MESSAGES/guides/network/dpdk.po new file mode 100644 index 00000000..86dac763 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/network/dpdk.po @@ -0,0 +1,376 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 document describes how to send packets between two platforms in the " +"simple configuration shown in :ref:`Figure 1 `. 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:17 +msgid "Figure 1: Environment for l3fwd DPDK application" +msgstr "" + +#: ../../guides/network/dpdk.rst:19 +msgid "This example uses the following DPDK components:" +msgstr "" + +#: ../../guides/network/dpdk.rst:21 +msgid "pktgen: Traffic generator. See `pktgen documentation`_ for details." +msgstr "" + +#: ../../guides/network/dpdk.rst:22 +msgid "" +"l3fwd: Layer 3 forwarding example application. See `l3fwd documentation`_" +" for details." +msgstr "" + +#: ../../guides/network/dpdk.rst:26 +msgid "Prerequisites" +msgstr "" + +#: ../../guides/network/dpdk.rst:28 +msgid "Two platforms using |CL-ATTR| release `13330`_ or higher." +msgstr "" + +#: ../../guides/network/dpdk.rst:29 +msgid "Both images must include the :file:`kernel-native bundle`." +msgstr "" + +#: ../../guides/network/dpdk.rst:30 +msgid "Install the :file:`network-basic-dev` bundle with the command:" +msgstr "" + +#: ../../guides/network/dpdk.rst:36 +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:39 +msgid "Two network cables." +msgstr "" + +#: ../../guides/network/dpdk.rst:42 +msgid "Install dpdk and build l3fwd example (Platform B)" +msgstr "" + +#: ../../guides/network/dpdk.rst:44 +msgid "Change to the :file:`l3fwd` example directory." +msgstr "" + +#: ../../guides/network/dpdk.rst:50 +msgid "Assign :envvar:`RTE_SDK` variable to the makefiles path." +msgstr "" + +#: ../../guides/network/dpdk.rst:56 +msgid "" +"Assign :envvar:`RTE_TARGET` variable to the location of the gcc\\* config" +" file." +msgstr "" + +#: ../../guides/network/dpdk.rst:63 +msgid "" +"Build the `l3fwd` application and add the configuration header to the " +":makevar:`CFLAGS` variable." +msgstr "" + +#: ../../guides/network/dpdk.rst:72 +msgid "Build pktgen (Platform A)" +msgstr "" + +#: ../../guides/network/dpdk.rst:74 +msgid "Download the `pktgen tar package`_ v3.1.2 or newer." +msgstr "" + +#: ../../guides/network/dpdk.rst:76 +msgid "Decompress packages and move to uncompressed source directory." +msgstr "" + +#: ../../guides/network/dpdk.rst:78 +msgid "Assign :envvar:`RTE_SDK` variable to the path where makefiles are located." +msgstr "" + +#: ../../guides/network/dpdk.rst:84 +msgid "Assign :envvar:`RTE_TARGET` to the location of the gcc config file." +msgstr "" + +#: ../../guides/network/dpdk.rst:90 +msgid "" +"Build the `pktgen` project and set the " +":makevar:`CONFIG_RTE_BUILD_SHARED_LIB` variable to \"n\"." +msgstr "" + +#: ../../guides/network/dpdk.rst:98 +msgid "Bind NICs to DPDK kernel drivers (Platforms A and B)" +msgstr "" + +#: ../../guides/network/dpdk.rst:100 +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:103 +msgid "Load the DPDK I/O kernel module." +msgstr "" + +#: ../../guides/network/dpdk.rst:109 +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:117 +msgid "" +"Bind two available NICs. The general syntax for binding is: :command" +":`dpdk-devbind --bind=vfio-pci `. A working example is " +"shown below:" +msgstr "" + +#: ../../guides/network/dpdk.rst:125 +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:131 +msgid "Set hugepages (Platforms A and B)" +msgstr "" + +#: ../../guides/network/dpdk.rst:133 +msgid "" +"|CL| supports `hugepages` for the large memory pool allocation used for " +"packet buffers." +msgstr "" + +#: ../../guides/network/dpdk.rst:136 +msgid "Set the number of hugepages." +msgstr "" + +#: ../../guides/network/dpdk.rst:142 +msgid "Allocate pages on NUMA machines." +msgstr "" + +#: ../../guides/network/dpdk.rst:149 +msgid "Make memory available for DPDK." +msgstr "" + +#: ../../guides/network/dpdk.rst:155 +msgid "" +"For more information, refer to the `DPDK guide`_ System Requirements " +"section." +msgstr "" + +#: ../../guides/network/dpdk.rst:160 +msgid "Set up the physical environment (Platforms A and B)" +msgstr "" + +#: ../../guides/network/dpdk.rst:162 +msgid "" +"Connect the NICs on Platform A to the NICs on Platform B using the " +"network cables as shown in :ref:`Figure 2`." +msgstr "" + +#: ../../guides/network/dpdk.rst:169 +msgid "Figure 2: Physical network environment" +msgstr "" + +#: ../../guides/network/dpdk.rst:173 +msgid "Run l3fwd application (Platform B)" +msgstr "" + +#: ../../guides/network/dpdk.rst:175 +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:179 +msgid "Open the l3fwd example directory." +msgstr "" + +#: ../../guides/network/dpdk.rst:185 +msgid "**This step is very important.**" +msgstr "" + +#: ../../guides/network/dpdk.rst:187 +msgid "DPDK needs poll mode drivers to operate." +msgstr "" + +#: ../../guides/network/dpdk.rst:188 +msgid "Poll mode drivers are shared objects in :file:`/usr/lib64`." +msgstr "" + +#: ../../guides/network/dpdk.rst:189 +msgid "See the full list of supported NICs at `dpdk.org NICs`_." +msgstr "" + +#: ../../guides/network/dpdk.rst:190 +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:193 +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:197 +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:205 +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:209 +msgid "Save the MAC address for configuring the `pktgen` project." +msgstr "" + +#: ../../guides/network/dpdk.rst:212 +msgid "Run pktgen application (Platform A)" +msgstr "" + +#: ../../guides/network/dpdk.rst:214 +msgid "`pktgen` is a network traffic generator included in the DPDK." +msgstr "" + +#: ../../guides/network/dpdk.rst:216 +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:224 +msgid "Enable active colorful output (optional)." +msgstr "" + +#: ../../guides/network/dpdk.rst:230 +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:237 ../../guides/network/dpdk.rst:296 +#: ../../guides/network/dpdk.rst:314 +msgid "Here is a working example:" +msgstr "" + +#: ../../guides/network/dpdk.rst:244 +msgid "Send packets." +msgstr "" + +#: ../../guides/network/dpdk.rst:250 +msgid "For more details, see the `pktgen documentation`_." +msgstr "" + +#: ../../guides/network/dpdk.rst:253 +msgid "Appendix A: Use pass-through for virtual machines" +msgstr "" + +#: ../../guides/network/dpdk.rst:255 +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:258 +msgid "Create a new directory and move to it." +msgstr "" + +#: ../../guides/network/dpdk.rst:260 +msgid "" +"Download or create a :file:`start_qemu.sh` script for running a kvm " +"virtual machine:" +msgstr "" + +#: ../../guides/network/dpdk.rst:267 +msgid "Download a bare-metal image of |CL| and rename it as :file:`clear.img`." +msgstr "" + +#: ../../guides/network/dpdk.rst:269 +msgid "Look for an Ethernet\\* device entry that contains vendor and device ID:" +msgstr "" + +#: ../../guides/network/dpdk.rst:275 +msgid "An example output:" +msgstr "" + +#: ../../guides/network/dpdk.rst:281 +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:286 +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:305 +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:321 +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:328 +msgid "" +"Here is a working example for a virtual machine with 4096 memory and four" +" CPUs:" +msgstr "" + +#: ../../guides/network/dpdk.rst:336 +msgid "Each NUMA machine must use the same quantity of memory." +msgstr "" + +#: ../../guides/network/dpdk.rst:338 +msgid "Run the :file:`start_qemu.sh` script." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/network/ipxe-install.po b/locale/zh_CN/LC_MESSAGES/guides/network/ipxe-install.po new file mode 100644 index 00000000..36ed2863 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/network/ipxe-install.po @@ -0,0 +1,314 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 |CL-ATTR| 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)`." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:9 +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:13 +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:18 +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:24 +msgid "Figure 1: PXE information flow." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:28 +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:33 +msgid "Prerequisites" +msgstr "" + +#: ../../guides/network/ipxe-install.rst:35 +msgid "Before booting with iPXE, make the following preparations." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:37 +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:43 +msgid "Figure 2: Network topology." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:45 +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:48 +msgid "Your PXE server must have:" +msgstr "" + +#: ../../guides/network/ipxe-install.rst:50 +msgid "Ethernet/LAN boot option." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:51 +msgid "At least two network adapters." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:52 +msgid "Connection to a public network." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:53 +msgid "Secure boot option disabled." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:57 +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:62 +msgid "Configuration" +msgstr "" + +#: ../../guides/network/ipxe-install.rst:64 +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 "" + +#: ../../guides/network/ipxe-install.rst:68 +msgid "To set up |CL| manually, perform the steps below." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:70 +msgid "Define the variables used for iPXE boot configuration." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:86 +msgid "Log in and get root privilege." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:92 +msgid "" +"Add the `pxe-server` bundle to your |CL| system. The bundle contains all " +"files needed to run a PXE server." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:99 +msgid "" +"Download the latest network-bootable release of |CL| and extract the " +"files." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:113 +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:117 +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:133 +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 "" + +#: ../../guides/network/ipxe-install.rst:155 +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:159 +msgid "Start `nginx` and enable the startup on boot option." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:166 +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 "" + +#: ../../guides/network/ipxe-install.rst:180 +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:196 +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:212 +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:215 +msgid "" +"Configure the kernel to forward network packets to different interfaces. " +"Otherwise, NAT will not work." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:224 +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 "" + +#: ../../guides/network/ipxe-install.rst:234 +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 "" + +#: ../../guides/network/ipxe-install.rst:245 +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:255 +msgid "" +"Add the options to host a DHCP server for PXE clients to the `dnsmasq` " +"configuration file." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:277 +msgid "The configuration provides the following important functions:" +msgstr "" + +#: ../../guides/network/ipxe-install.rst:279 +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:282 +msgid "" +"Activates only on the network adapter that has an IP address on the " +"defined subnet." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:284 +msgid "Directs PXE clients to the DNS server." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:285 +msgid "Directs PXE clients to the PXE server for routing via NAT." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:286 +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:290 +msgid "" +"Create a file for `dnsmasq` to record the IP addresses it provides to PXE" +" clients." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:298 +msgid "Start `dnsmasq` and enable startup on boot." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:305 +msgid "Start `systemd-resolved`." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:313 +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:318 +msgid "Power on the PXE client and watch the client boot and install |CL|." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:320 +msgid "" +"After booting, |CL| automatically partitions the hard drive, installs " +"itself, updates to the latest version, and reboots." +msgstr "" + +#: ../../guides/network/ipxe-install.rst:324 +msgid "" +"**Congratulations!** You have successfully installed and configured a PXE" +" server that enables PXE clients to boot and install |CL| over the " +"network." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/network/network-bonding.po b/locale/zh_CN/LC_MESSAGES/guides/network/network-bonding.po new file mode 100644 index 00000000..df3f9cc1 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/network/network-bonding.po @@ -0,0 +1,153 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 "" +"Network bonding combines multiple network interfaces into a single " +"logical interface to provide redundancy and bandwidth aggregation." +msgstr "" + +#: ../../guides/network/network-bonding.rst:9 +msgid "" +"|CL-ATTR| includes Linux bonding_ and team_ drivers. This guide describes" +" how to configure systemd to use the `bonding` driver." +msgstr "" + +#: ../../guides/network/network-bonding.rst:12 +msgid "The example demonstrates how to:" +msgstr "" + +#: ../../guides/network/network-bonding.rst:14 +msgid "Bond all four ports of a quad-port NIC in `802.3ad` mode." +msgstr "" + +#: ../../guides/network/network-bonding.rst:16 +msgid "Enable jumbo frames to optimize large data transfers on the local network." +msgstr "" + +#: ../../guides/network/network-bonding.rst:18 +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:24 +msgid "You must run all commands in this guide as root." +msgstr "" + +#: ../../guides/network/network-bonding.rst:26 +msgid "Log in and get root privileges." +msgstr "" + +#: ../../guides/network/network-bonding.rst:32 +msgid "Create the :file:`/etc/systemd/network` directory." +msgstr "" + +#: ../../guides/network/network-bonding.rst:38 +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:42 +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:57 +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:61 +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:76 +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:81 +msgid "" +"For best results, do not assign addresses or DHCP support to the " +"individual NICs." +msgstr "" + +#: ../../guides/network/network-bonding.rst:84 +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:87 +msgid "Configure the bonded interface in a file named :file:`30-bond1.network`." +msgstr "" + +#: ../../guides/network/network-bonding.rst:101 +msgid "`bond1` is a virtual interface with no physical link status." +msgstr "" + +#: ../../guides/network/network-bonding.rst:103 +msgid "" +"`BindCarrier` indicates that the `bond1` link status is determined by the" +" status of the listed slave devices." +msgstr "" + +#: ../../guides/network/network-bonding.rst:106 +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:109 +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:113 +msgid "Apply the new network configuration with the command:" +msgstr "" + +#: ../../guides/network/network-bonding.rst:119 +msgid "" +"The `MTUBytes` settings do not take effect until you reboot or manually " +"apply the settings with a utility such as `ifconfig`." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/network/vnc.po b/locale/zh_CN/LC_MESSAGES/guides/network/vnc.po new file mode 100644 index 00000000..0cf56ed8 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/network/vnc.po @@ -0,0 +1,921 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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/vnc.rst:4 +msgid "Remote-desktop to a |CL-ATTR| host using VNC" +msgstr "" + +#: ../../guides/network/vnc.rst:6 +msgid "" +":abbr:`VNC (Virtual Network Computing)` is a client-server GUI-based tool" +" that allows you to connect via remote-desktop to your |CL-ATTR| host." +msgstr "" + +#: ../../guides/network/vnc.rst:9 +msgid "This guide shows you how to:" +msgstr "" + +#: ../../guides/network/vnc.rst:11 +msgid "Install the VNC server and misc. components on your |CL| host." +msgstr "" + +#: ../../guides/network/vnc.rst:12 +msgid "Configure a VNC-server-start method on your |CL| host." +msgstr "" + +#: ../../guides/network/vnc.rst:13 +msgid "Install a VNC viewer app and an SSH client on your client system." +msgstr "" + +#: ../../guides/network/vnc.rst:14 +msgid "Establish a VNC connection to your |CL| host." +msgstr "" + +#: ../../guides/network/vnc.rst:15 +msgid "Terminate a VNC connection to your |CL| host." +msgstr "" + +#: ../../guides/network/vnc.rst:16 +msgid "Encrypt VNC traffic through an SSH tunnel." +msgstr "" + +#: ../../guides/network/vnc.rst:19 +msgid "Install the VNC server and misc. components on your host" +msgstr "" + +#: ../../guides/network/vnc.rst:21 +msgid "To configure VNC to work on your |CL| host, install these bundles:" +msgstr "" + +#: ../../guides/network/vnc.rst:23 +msgid "" +"`desktop-autostart`: Installs :abbr:`GDM (Gnome Desktop Manager)`, sets " +"it to start automatically on boot, and installs TigerVNC Viewer." +msgstr "" + +#: ../../guides/network/vnc.rst:25 +msgid "`vnc-server`: Installs the TigerVNC server." +msgstr "" + +#: ../../guides/network/vnc.rst:27 +msgid "Follow these steps:" +msgstr "" + +#: ../../guides/network/vnc.rst:29 +msgid "Log into your |CL| host and get root privileges." +msgstr "" + +#: ../../guides/network/vnc.rst:35 +msgid "Install the |CL| bundles." +msgstr "" + +#: ../../guides/network/vnc.rst:41 +msgid "Reboot your |CL| host." +msgstr "" + +#: ../../guides/network/vnc.rst:44 +msgid "Configure a VNC-server-start method on your host" +msgstr "" + +#: ../../guides/network/vnc.rst:46 +msgid "" +"There are three methods you can use to configure and start the VNC server" +" on your |CL| host:" +msgstr "" + +#: ../../guides/network/vnc.rst:49 +msgid "Table 1: VNC-server-start Configuration Methods" +msgstr "" + +#: ../../guides/network/vnc.rst:53 +msgid "Attribute" +msgstr "" + +#: ../../guides/network/vnc.rst:54 +msgid "`Method 1`: Manually start a VNC session" +msgstr "" + +#: ../../guides/network/vnc.rst:55 +msgid "`Method 2`: Automatically start a VNC session via a systemd service script" +msgstr "" + +#: ../../guides/network/vnc.rst:56 +msgid "`Method 3`: Create multi-user logins with authentication through GDM" +msgstr "" + +#: ../../guides/network/vnc.rst:57 +msgid "Description" +msgstr "" + +#: ../../guides/network/vnc.rst:58 +msgid "" +"This is the traditional method where you SSH into the |CL| host, manually" +" start a VNC session to get a display ID, and connect to it by supplying " +"the display ID." +msgstr "" + +#: ../../guides/network/vnc.rst:61 +msgid "" +"The system administrator sets up a systemd service script for you with a " +"pre-assigned display ID. You make a VNC connection and supply your pre-" +"assigned display ID." +msgstr "" + +#: ../../guides/network/vnc.rst:64 +msgid "" +"The system adminstrator configures GDM to accept connection requests. " +"When you make a VNC connection to the |CL| host, you see the GDM login " +"screen and authenticate as if you are local." +msgstr "" + +#: ../../guides/network/vnc.rst:67 +msgid "Who configures VNC settings?" +msgstr "" + +#: ../../guides/network/vnc.rst:68 ../../guides/network/vnc.rst:72 +#: ../../guides/network/vnc.rst:76 ../../guides/network/vnc.rst:77 +msgid "You" +msgstr "" + +#: ../../guides/network/vnc.rst:69 ../../guides/network/vnc.rst:70 +msgid "System adminstrator" +msgstr "" + +#: ../../guides/network/vnc.rst:71 +msgid "Who starts VNC session?" +msgstr "" + +#: ../../guides/network/vnc.rst:73 ../../guides/network/vnc.rst:74 +msgid "Set to start automatically on boot by system administrator" +msgstr "" + +#: ../../guides/network/vnc.rst:75 +msgid "Who ends VNC sesssion?" +msgstr "" + +#: ../../guides/network/vnc.rst:78 +msgid "System administrator can disable VNC service altogether" +msgstr "" + +#: ../../guides/network/vnc.rst:79 +msgid "Requires VNC password to authenticate?" +msgstr "" + +#: ../../guides/network/vnc.rst:80 ../../guides/network/vnc.rst:81 +msgid "Yes" +msgstr "" + +#: ../../guides/network/vnc.rst:82 +msgid "No. Use |CL| account username and password through GDM" +msgstr "" + +#: ../../guides/network/vnc.rst:85 +msgid "" +"Although all three methods can coexist on the same |CL| host, we " +"recommend you pick a method that suits your needs." +msgstr "" + +#: ../../guides/network/vnc.rst:88 +msgid "" +"For simplicity, the rest of this guide refers to these methods as `Method" +" 1`, `Method 2`, and `Method 3`." +msgstr "" + +#: ../../guides/network/vnc.rst:92 +msgid "Method 1: Manually start a VNC session" +msgstr "" + +#: ../../guides/network/vnc.rst:94 +msgid "" +"You (and each user) must perform these steps to initialize your VNC " +"settings." +msgstr "" + +#: ../../guides/network/vnc.rst:96 +msgid "Log in." +msgstr "" + +#: ../../guides/network/vnc.rst:97 ../../guides/network/vnc.rst:557 +msgid "Open a terminal emulator." +msgstr "" + +#: ../../guides/network/vnc.rst:98 +msgid "" +"Start VNC with the :command:`vncserver` command. Since this is your " +"first time starting VNC, it adds default configuration files and asks you" +" to set a VNC password." +msgstr "" + +#: ../../guides/network/vnc.rst:106 ../../guides/network/vnc.rst:431 +msgid "Example output:" +msgstr "" + +#: ../../guides/network/vnc.rst:126 +msgid "" +"Upon completion, you can find the default configuration files and the " +"password file hidden in the `.vnc` directory in your home directory." +msgstr "" + +#: ../../guides/network/vnc.rst:129 +msgid "" +"Also, a VNC session starts and shows a unique display ID, which is the " +"number following the hostname and the colon `:`. In the above example, " +"the display ID is 2. In a later step, you will supply the display ID to " +"your VNC viewer app for connection." +msgstr "" + +#: ../../guides/network/vnc.rst:133 +msgid "" +"Kill the active VNC session for the time being with the " +":command:`vncserver -kill :[display ID]` command. Substitute [display " +"ID] with your active VNC session display ID. For example:" +msgstr "" + +#: ../../guides/network/vnc.rst:143 +msgid "" +"If you do not recall the active session display ID, use the " +":command:`vncserver -list` command to find it." +msgstr "" + +#: ../../guides/network/vnc.rst:146 +msgid "Optional configurations:" +msgstr "" + +#: ../../guides/network/vnc.rst:148 +msgid "" +"To customize settings such as screen size, security type, etc., modify " +"the :file:`$HOME/.vnc/config` file." +msgstr "" + +#: ../../guides/network/vnc.rst:150 +msgid "" +"To customize the applications to run at startup, modify the " +":file:`$HOME/.vnc/xstartup` file." +msgstr "" + +#: ../../guides/network/vnc.rst:154 +msgid "Method 2: Automatically start a VNC session via a systemd service script" +msgstr "" + +#: ../../guides/network/vnc.rst:156 +msgid "" +"To configure VNC for this method, you must have root privileges. You " +"will set up a systemd service file for all intended VNC users with their " +"own preassigned unique display ID." +msgstr "" + +#: ../../guides/network/vnc.rst:160 ../../guides/network/vnc.rst:244 +msgid "Log in and get root privileges." +msgstr "" + +#: ../../guides/network/vnc.rst:166 +msgid "" +"Make sure the user accounts already exist. Use the following command to " +"list all users." +msgstr "" + +#: ../../guides/network/vnc.rst:174 ../../guides/network/vnc.rst:250 +msgid "Create the path :file:`/etc/systemd/system`." +msgstr "" + +#: ../../guides/network/vnc.rst:180 +msgid "" +"Create a systemd service script file :file:`vncserver@:[X].service`, " +"where [X] is the display ID, for each user in :file:`/etc/systemd/system`" +" Each user must be assigned a unique display ID. Be sure the correct " +"username is entered in the `User` field. The example below shows user " +"`vnc-user-b` who is assigned the display ID `5`." +msgstr "" + +#: ../../guides/network/vnc.rst:208 +msgid "" +"Have each user log into their account and set a VNC password with the " +":command:`vncpasswd` command before proceeding to the next step." +msgstr "" + +#: ../../guides/network/vnc.rst:211 +msgid "" +"Start the VNC service script and set it to start automatically on boot " +"for each user. Replace the [X] with the display ID." +msgstr "" + +#: ../../guides/network/vnc.rst:220 +msgid "After starting the services, verify they are running." +msgstr "" + +#: ../../guides/network/vnc.rst:226 +msgid "" +"The example below shows 2 VNC sessions that were successfully started for" +" users `vnc-user-b` with display ID 5 and `vnc-user-c` with display ID 6." +msgstr "" + +#: ../../guides/network/vnc.rst:238 +msgid "Method 3: Multi-user logins with authentication through GDM" +msgstr "" + +#: ../../guides/network/vnc.rst:240 +msgid "" +"For this method, VNC is configured as a systemd service that listens on " +"port 5900 and GDM is configured to accept access requests from VNC. When " +"you make a VNC connection to your |CL| host, you are presented with the " +"GDM login screen and you authenticate as if you are local. You must have" +" root privileges to perform this configuration." +msgstr "" + +#: ../../guides/network/vnc.rst:256 +msgid "Create a systemd socket file :file:`xvnc.socket` and add the following:" +msgstr "" + +#: ../../guides/network/vnc.rst:274 +msgid "Create a systemd service file :file:`xvnc@.service` and add the following:" +msgstr "" + +#: ../../guides/network/vnc.rst:291 +msgid "Create the path :file:`/etc/gdm`." +msgstr "" + +#: ../../guides/network/vnc.rst:298 +msgid "Create a GDM :file:`custom.conf` file and add the following:" +msgstr "" + +#: ../../guides/network/vnc.rst:310 +msgid "Start the VNC socket script and set it to start automatically on boot." +msgstr "" + +#: ../../guides/network/vnc.rst:318 +msgid "After starting the socket, verify it is running." +msgstr "" + +#: ../../guides/network/vnc.rst:324 +msgid "The example below shows the xvnc.socket is running." +msgstr "" + +#: ../../guides/network/vnc.rst:333 +msgid "See the `vncserver` Man page for additional information." +msgstr "" + +#: ../../guides/network/vnc.rst:336 +msgid "Install a VNC viewer app and an SSH client on your client system" +msgstr "" + +#: ../../guides/network/vnc.rst:338 +msgid "" +"You need a VNC viewer app on your client system to connect to your |CL| " +"host. An SSH client is only needed if you chose to use `Method 1` or you " +"plan to encrypt your VNC traffic, which is discussed later in this guide." +msgstr "" + +#: ../../guides/network/vnc.rst:342 +msgid "Perform the steps below to add these apps to your client system." +msgstr "" + +#: ../../guides/network/vnc.rst:345 +msgid "Install a VNC viewer app" +msgstr "" + +#: ../../guides/network/vnc.rst:347 +msgid "On |CL|:" +msgstr "" + +#: ../../guides/network/vnc.rst:353 +msgid "On Ubuntu, Mint:" +msgstr "" + +#: ../../guides/network/vnc.rst:359 +msgid "On Fedora:" +msgstr "" + +#: ../../guides/network/vnc.rst:365 ../../guides/network/vnc.rst:407 +msgid "On Windows:" +msgstr "" + +#: ../../guides/network/vnc.rst:367 +msgid "Install `RealVNC for Windows`_" +msgstr "" + +#: ../../guides/network/vnc.rst:369 +msgid "On macOS:" +msgstr "" + +#: ../../guides/network/vnc.rst:371 +msgid "Install `RealVNC for macOS`_" +msgstr "" + +#: ../../guides/network/vnc.rst:374 +msgid "Install an SSH client" +msgstr "" + +#: ../../guides/network/vnc.rst:376 +msgid "" +"On most Linux distros (|CL|, Ubuntu, Mint, Fedora, etc.) and macOS, SSH " +"is built-in so you don't need to install it." +msgstr "" + +#: ../../guides/network/vnc.rst:378 +msgid "On Windows, you can install `Putty`_." +msgstr "" + +#: ../../guides/network/vnc.rst:381 +msgid "Establish a VNC connection to your host" +msgstr "" + +#: ../../guides/network/vnc.rst:383 +msgid "" +"Depending on the VNC-server-configuration method chosen, use the " +"appropriate VNC connection:" +msgstr "" + +#: ../../guides/network/vnc.rst:385 +msgid "" +"If you chose `Method 1`, you must take a few extra steps by using SSH to " +"connect to your |CL| host and then manually launching VNC." +msgstr "" + +#: ../../guides/network/vnc.rst:388 +msgid "" +"If you chose `Method 2`, get your preassigned VNC display ID from your " +"system administrator first and then proceed to the :ref:`connect-to-vnc-" +"session` section below." +msgstr "" + +#: ../../guides/network/vnc.rst:392 +msgid "" +"If you chose `Method 3`, proceed to the :ref:`connect-to-vnc-session` " +"below." +msgstr "" + +#: ../../guides/network/vnc.rst:397 +msgid "SSH into your host and launch VNC" +msgstr "" + +#: ../../guides/network/vnc.rst:399 +msgid "SSH into your |CL| host" +msgstr "" + +#: ../../guides/network/vnc.rst:401 +msgid "On Linux distros and macOS:" +msgstr "" + +#: ../../guides/network/vnc.rst:409 ../../guides/network/vnc.rst:724 +msgid "Launch Putty." +msgstr "" + +#: ../../guides/network/vnc.rst:410 ../../guides/network/vnc.rst:727 +msgid "" +"Under the :guilabel:`Category` section, select :guilabel:`Session`. See " +"Figure 1." +msgstr "" + +#: ../../guides/network/vnc.rst:412 ../../guides/network/vnc.rst:729 +msgid "" +"Enter the IP address of your |CL| host in the :guilabel:`Host Name (or IP" +" address)` field." +msgstr "" + +#: ../../guides/network/vnc.rst:414 ../../guides/network/vnc.rst:731 +msgid "Set the :guilabel:`Connection type` option to :guilabel:`SSH`." +msgstr "" + +#: ../../guides/network/vnc.rst:415 ../../guides/network/vnc.rst:753 +msgid "Click the :guilabel:`Open` button." +msgstr "" + +#: ../../guides/network/vnc.rst:421 +msgid "Figure 1: Putty - configure SSH session settings" +msgstr "" + +#: ../../guides/network/vnc.rst:423 +msgid "Log in with your |CL| username and password. Do not use your VNC password." +msgstr "" + +#: ../../guides/network/vnc.rst:425 +msgid "Start a VNC session." +msgstr "" + +#: ../../guides/network/vnc.rst:442 +msgid "" +"Take note of the generated display ID because you will input it into the " +"VNC viewer app to establish the connection. The above example shows the " +"display ID is 3." +msgstr "" + +#: ../../guides/network/vnc.rst:448 +msgid "" +"VNC automatically picks a unique display ID unless you specify one. To " +"specify a display ID, enter a unique number that is not already in use " +"after the colon. For example:" +msgstr "" + +#: ../../guides/network/vnc.rst:456 +msgid "" +"You can now end the SSH connection by logging out. This does not " +"terminate your active VNC session." +msgstr "" + +#: ../../guides/network/vnc.rst:462 +msgid "Connect to your VNC session" +msgstr "" + +#: ../../guides/network/vnc.rst:464 +msgid "" +"For `Method 1` and `Method 2`, you must connect to a specific active " +"session or display ID using one of two options:" +msgstr "" + +#: ../../guides/network/vnc.rst:467 +msgid "" +"Use a fully-qualified VNC port number, which consists of the default VNC " +"server port (5900) plus the display ID" +msgstr "" + +#: ../../guides/network/vnc.rst:469 +msgid "Use the display ID" +msgstr "" + +#: ../../guides/network/vnc.rst:471 +msgid "" +"For example, if the display ID is 3, it can be specified as `5903` or " +"just as `3`. For `Method 3`, VNC does not expect a display ID. Use " +"`5900`. For simplicity, the instructions below use the fully-qualified " +"VNC port number." +msgstr "" + +#: ../../guides/network/vnc.rst:475 ../../guides/network/vnc.rst:762 +msgid "**On Linux distros:**" +msgstr "" + +#: ../../guides/network/vnc.rst:477 +msgid "Open a terminal emulator and enter:" +msgstr "" + +#: ../../guides/network/vnc.rst:483 ../../guides/network/vnc.rst:512 +msgid "Enter your credentials." +msgstr "" + +#: ../../guides/network/vnc.rst:485 ../../guides/network/vnc.rst:514 +msgid "" +"For `Method 1` and `Method 2`, enter your VNC password. No username is " +"required." +msgstr "" + +#: ../../guides/network/vnc.rst:487 ../../guides/network/vnc.rst:516 +msgid "For `Method 3`, enter your |CL| account username and password through GDM." +msgstr "" + +#: ../../guides/network/vnc.rst:492 ../../guides/network/vnc.rst:521 +msgid "" +"With `Method 3`, you cannot remotely log into your |CL| host through VNC " +"if you are logged in locally and vice versa." +msgstr "" + +#: ../../guides/network/vnc.rst:495 +msgid "**On Windows and macOS using `RealVNC` app:**" +msgstr "" + +#: ../../guides/network/vnc.rst:497 +msgid "Start the RealVNC viewer app. See Figure 2." +msgstr "" + +#: ../../guides/network/vnc.rst:498 +msgid "" +"Enter the IP address of the |CL| host and the fully-qualified VNC port " +"number." +msgstr "" + +#: ../../guides/network/vnc.rst:501 +msgid "" +"The following screenshot shows connecting to |CL| host 192.168.25.54 with" +" a fully-qualified VNC port number 5902." +msgstr "" + +#: ../../guides/network/vnc.rst:508 +msgid "Figure 2: RealVNC Viewer" +msgstr "" + +#: ../../guides/network/vnc.rst:510 +msgid "Press the :kbd:`Enter` key." +msgstr "" + +#: ../../guides/network/vnc.rst:525 +msgid "`Optional: Configure RealVNC Image Quality`" +msgstr "" + +#: ../../guides/network/vnc.rst:527 +msgid "" +"To increase the RealVNC viewer image quality, manually change the " +"`ColorLevel` value. Follow these steps:" +msgstr "" + +#: ../../guides/network/vnc.rst:529 +msgid "" +"Right-click a connection node and select :guilabel:`Properties...`. See " +"Figure 3." +msgstr "" + +#: ../../guides/network/vnc.rst:536 +msgid "Figure 3: RealVNC Viewer - change connection node properties" +msgstr "" + +#: ../../guides/network/vnc.rst:538 +msgid "Select the :guilabel:`Expert` tab. See Figure 4." +msgstr "" + +#: ../../guides/network/vnc.rst:540 +msgid "" +"Select the :guilabel:`ColorLevel` setting and change it to your preferred" +" setting." +msgstr "" + +#: ../../guides/network/vnc.rst:547 +msgid "Figure 4: RealVNC Viewer - change :guilabel:`ColorLevel`" +msgstr "" + +#: ../../guides/network/vnc.rst:550 +msgid "Terminate a VNC connection to your host" +msgstr "" + +#: ../../guides/network/vnc.rst:552 +msgid "" +"For `Method 1` and `Method 2`, once started, a VNC session remains active" +" on your |CL| host even if you close your VNC viewer app. If you want to " +"truly terminate an active VNC session, follow these steps:" +msgstr "" + +#: ../../guides/network/vnc.rst:556 +msgid "SSH into your |CL| host." +msgstr "" + +#: ../../guides/network/vnc.rst:558 +msgid "" +"Find the active VNC session display ID with the command " +":command:`vncserver -list`." +msgstr "" + +#: ../../guides/network/vnc.rst:565 +msgid "" +"Terminate it with the :command:`vncserver -kill` command followed by a " +"colon and the display ID." +msgstr "" + +#: ../../guides/network/vnc.rst:572 +msgid "" +"For `Method 3`, only the system administrator can stop and disable the " +"VNC service by using these commands:" +msgstr "" + +#: ../../guides/network/vnc.rst:582 +msgid "Encrypt VNC traffic through an SSH tunnel" +msgstr "" + +#: ../../guides/network/vnc.rst:584 +msgid "" +"By default, VNC traffic is not encrypted. Figure 6 shows an example " +"warning from RealVNC Viewer." +msgstr "" + +#: ../../guides/network/vnc.rst:591 +msgid "Figure 6: RealVNC Viewer - Connection not encrypted warning" +msgstr "" + +#: ../../guides/network/vnc.rst:593 +msgid "" +"To add security, VNC traffic can be routed through an SSH tunnel. This is" +" accomplished by following these steps:" +msgstr "" + +#: ../../guides/network/vnc.rst:595 +msgid "" +"Configure the VNC server to only accept connection from localhost by " +"adding the `-localhost` option." +msgstr "" + +#: ../../guides/network/vnc.rst:597 +msgid "" +"Set up an SSH tunnel between your client system and your |CL| host. Your " +"client system will forward traffic from the localhost (the client) " +"destined for a specified fully-qualified VNC port number (on the client) " +"to your |CL| host with the same port number." +msgstr "" + +#: ../../guides/network/vnc.rst:601 +msgid "" +"The VNC viewer app on your client system will now connect to localhost, " +"instead of the IP address of your |CL| host." +msgstr "" + +#: ../../guides/network/vnc.rst:605 +msgid "Configure VNC to only accept connection from localhost" +msgstr "" + +#: ../../guides/network/vnc.rst:607 +msgid "For `Method 1`:" +msgstr "" + +#: ../../guides/network/vnc.rst:609 +msgid "" +"Edit the :file:`config` file located in :file:`$HOME/.vnc` and uncomment " +"the `# localhost` line. It should look like this:" +msgstr "" + +#: ../../guides/network/vnc.rst:625 +msgid "If an active session exists, kill it, and then restart it." +msgstr "" + +#: ../../guides/network/vnc.rst:627 +msgid "For `Method 2`:" +msgstr "" + +#: ../../guides/network/vnc.rst:629 +msgid "" +"Edit the systemd service script :file:`vncserver@:[X].service` located in" +" :file:`/etc/systemd/system` and add `-localhost` to the `ExecStart` " +"line. The example below uses vncserver@:5.service:" +msgstr "" + +#: ../../guides/network/vnc.rst:651 +msgid "Restart the service script:" +msgstr "" + +#: ../../guides/network/vnc.rst:658 +msgid "For `Method 3`:" +msgstr "" + +#: ../../guides/network/vnc.rst:660 +msgid "No change is needed to the :file:`xvnc@service` script." +msgstr "" + +#: ../../guides/network/vnc.rst:662 +msgid "" +"After you have restarted your VNC session, you can verify that it only " +"accepts connections from localhost by using the :command:`netstat` " +"command like this:" +msgstr "" + +#: ../../guides/network/vnc.rst:672 +msgid "Add the |CL| `network-basic` bundle to get the :command:`netstat` command." +msgstr "" + +#: ../../guides/network/vnc.rst:675 +msgid "" +"Figure 7 shows two VNC sessions (5901 and 5905) accepting connections " +"from any host as specified by the `0.0.0.0`'s. This is before the " +"`-localhost` option was used." +msgstr "" + +#: ../../guides/network/vnc.rst:682 +msgid "Figure 7: VNC sessions (5901 and 5905) accepting connections from any host" +msgstr "" + +#: ../../guides/network/vnc.rst:684 +msgid "" +"Figure 8 shows two VNC sessions (5901 and 5905) only accepting " +"connections from localhost as specified by `127.0.0.1`'s. This is after " +"the `-localhost` option was used." +msgstr "" + +#: ../../guides/network/vnc.rst:690 +msgid "" +"Figure 8: VNC sessions (5901 and 5905) only accepting connections from " +"localhost" +msgstr "" + +#: ../../guides/network/vnc.rst:693 +msgid "Set up an SSH tunnel from your client system to your |CL| host" +msgstr "" + +#: ../../guides/network/vnc.rst:695 +msgid "**On Linux distros and macOS:**" +msgstr "" + +#: ../../guides/network/vnc.rst:697 ../../guides/network/vnc.rst:764 +msgid "Open terminal emulator and enter:" +msgstr "" + +#: ../../guides/network/vnc.rst:704 ../../guides/network/vnc.rst:754 +msgid "Enter your |CL| account password (not your VNC password)." +msgstr "" + +#: ../../guides/network/vnc.rst:708 +msgid "" +"`-L` specifies that [client port number] on the localhost (on the client " +"side) is forwarded to [fully-qualified VNC port number] (on the server " +"side)." +msgstr "" + +#: ../../guides/network/vnc.rst:711 +msgid "" +"Replace `[client port number]` with an available client port number (for " +"example: 1234). For simplicity, you can make the `[client port number]` " +"the same as the `[fully-qualified VNC port number]`." +msgstr "" + +#: ../../guides/network/vnc.rst:714 +msgid "" +"Replace `[fully-qualified VNC port number]` with 5900 (default VNC port) " +"plus the display ID. For example, if the display ID is 2, the fully-" +"qualified VNC port number is is 5902." +msgstr "" + +#: ../../guides/network/vnc.rst:717 +msgid "`-N` tells SSH to only forward ports and not execute a remote command." +msgstr "" + +#: ../../guides/network/vnc.rst:719 +msgid "`-f` tells SSH to go into the background before command execution." +msgstr "" + +#: ../../guides/network/vnc.rst:720 +msgid "`-l` specifies the username to log in as." +msgstr "" + +#: ../../guides/network/vnc.rst:722 +msgid "**On Windows:**" +msgstr "" + +#: ../../guides/network/vnc.rst:725 +msgid "Specify the |CL| VNC host to connect to." +msgstr "" + +#: ../../guides/network/vnc.rst:733 +msgid "Configure the SSH tunnel. See Figure 9 for an example." +msgstr "" + +#: ../../guides/network/vnc.rst:735 +msgid "" +"Under the :guilabel:`Category` section, go to :guilabel:`Connection` > " +":guilabel:`SSH` > :guilabel:`Tunnels`." +msgstr "" + +#: ../../guides/network/vnc.rst:738 +msgid "" +"In the :guilabel:`Source port` field, enter an available client port " +"number (for example: 1234). For simplicity, you can make the `Source " +"port` the same as the fully-qualified VNC port number." +msgstr "" + +#: ../../guides/network/vnc.rst:742 +msgid "" +"In the :guilabel:`Destination` field, enter `localhost:` plus the fully-" +"qualified VNC port number." +msgstr "" + +#: ../../guides/network/vnc.rst:745 +msgid "Click the :guilabel:`Add` button." +msgstr "" + +#: ../../guides/network/vnc.rst:751 +msgid "Figure 9: Putty - configure SSH tunnel" +msgstr "" + +#: ../../guides/network/vnc.rst:757 +msgid "Connect to a VNC session through an SSH tunnel" +msgstr "" + +#: ../../guides/network/vnc.rst:759 +msgid "" +"After you have set up an SSH tunnel, follow these instructions to connect" +" to your VNC session." +msgstr "" + +#: ../../guides/network/vnc.rst:770 +msgid "**On Windows and macOS using `RealVNC`:**" +msgstr "" + +#: ../../guides/network/vnc.rst:772 +msgid "Start the RealVNC viewer app." +msgstr "" + +#: ../../guides/network/vnc.rst:773 +msgid "" +"Enter `localhost` and the fully-qualified VNC port number. See Figure 10" +" for an example." +msgstr "" + +#: ../../guides/network/vnc.rst:780 +msgid "Figure 10: RealVNC viewer app connecting to `localhost:1234`" +msgstr "" + +#: ../../guides/network/vnc.rst:784 +msgid "" +"RealVNC will still warn that the connection is not encrypted even though " +"its traffic is going through the SSH tunnel. You can ignore this " +"warning." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/guides/telemetrics/telem-guide.po b/locale/zh_CN/LC_MESSAGES/guides/telemetrics/telem-guide.po new file mode 100644 index 00000000..a6d6ec5e --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/guides/telemetrics/telem-guide.po @@ -0,0 +1,942 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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/telemetrics/telem-guide.rst:4 +msgid "Telemetrics" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:6 +msgid "" +"Telemetrics in |CL-ATTR| is a client and server solution used to collect " +"data from running |CL| systems to help quickly identify and fix bugs in " +"the OS. Both client and server are customizable, and an API is available" +" on the client side for instrumenting your code for debug and analysis." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:10 +msgid "" +"Telemetry in |CL| is **opt-in**. The telemetry client is **not** active " +"and sends **no** data until you explicitly enable it." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:14 +msgid "" +"The telemetry functionality adheres to `Intel privacy policies`_ " +"regarding the collection and use of :abbr:`PII (Personally Identifiable " +"Information)` and is open source. Specifically, no intentionally " +"identifiable information about the user or system owner is collected." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:23 +msgid "Description" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:25 +msgid "" +"Telemetry, one of the key features of |CL|, enables developers to observe" +" and proactively address issues in the OS before end users are impacted." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:27 +msgid "Telemetrics is a combination word made from:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:29 +msgid "Telemetry, which is sensing and reporting data." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:30 +msgid "" +"Analytics, which is using visualization and statistical inferencing to " +"make sense of the reported data." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:32 +msgid "" +"|CL| telemetry reports system-level debug/crash information using " +"specialized probes. The probes monitor system tasks such as swupd, kernel" +" oops, machine error checks, and the 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 "" + +#: ../../guides/telemetrics/telem-guide.rst:34 +msgid "" +"|CL| telemetry is fully customizable and can be used during software " +"development for debugging purposes. You can use the libtelemetry library" +" in your code to create custom telemetry records. You can also use the " +"telem-record-gen utility in script files for light touch record creation " +"where instrumenting code files doesn't make sense." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:36 +msgid "" +"The |CL| telemetrics solution is an **opt-in** choice on the client side." +" By default, the telemetry client is disabled until you choose to enable" +" it. Enabling the client is covered in this guide." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:39 +msgid "Architecture" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:41 +msgid "" +"|CL| telemetry has two fundamental components, which are shown in figure " +"1:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:43 +msgid "" +"Client: generates and delivers records to the backend server via the " +"network" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:45 +msgid "" +"Backend: receives records sent from the client and displays the " +"cumulative content through a specialized web interface." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:50 +msgid "Figure 1: :guilabel:`|CL| Telemetry Architecture`" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:52 +msgid "" +"The telemetry client provides the front end of the telemetrics solution " +"and includes the following components:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:54 +msgid "" +"telemprobd, a daemon that receives and prepares telemetry records from " +"probes and spools them to disk." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:55 +msgid "" +"telempostd, a daemon that manages spooled telemetry records and delivers " +"these records according to configurable settings." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:56 +msgid "probes, that collect specific types of data from the operating system." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:57 +msgid "libtelemetry, the API that telemetrics probes use to create records." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:59 +msgid "" +"The telemetry backend provides the server-side component of the " +"telemetrics solution and consists of:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:61 +msgid "Nginx web server." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:62 +msgid "" +"Two Flask apps: * Collector, an ingestion web app for records received " +"from client probes. * TelemetryUI, a web app that exposes different views" +" to visualize the telemetry data." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:65 +msgid "PostgreSQL as the underlying database server." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:69 +msgid "" +"The default telemetry backend server is hosted by the Intel |CL| " +"development team and is not viewable outside the Intel firewall. To " +"collect your own records, you must set up your own telemetry backend " +"server." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:74 +msgid "How To Use" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:76 +msgid "" +"From a workflow perspective, the |CL| telemetrics system is " +"straightforward. On the client side, the main decisions after " +"installation and enabling telemetry concern what to do with the record " +"data generated by the probes. You can send the data to the default or a " +"custom backend server, keep the data local to the system, or both. The " +"backend server has a more complex setup, but once it's running, it is " +"simple to use and configure." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:78 +msgid "" +"This section walks through some of the possible scenarios for configuring" +" the |CL| telemetrics system, and suggests which make sense according to " +"your needs." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:81 +msgid "Scenarios" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:82 +msgid "Enable telemetry" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:84 +msgid "" +"Before probes can generate records, the telemetry client daemons must be " +"enabled. You can configure the client before enabling by creating a " +"custom :file:`telemetrics.conf` file that you place in the " +":file:`/etc/telemetrics` directory. If you choose to use the default " +"settings, records will be sent to the telemetrics backend server managed " +"by the |CL| development team at Intel." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:86 +msgid "Save record data locally" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:88 +msgid "" +"You can configure the telemetry client to save records locally. This is " +"convenient when you want instant feedback during a development cycle, or " +"to track system issues if you believe there is a machine specific " +"problem. The client can be set to not send records at all, or to both " +"keep the records locally and send to the backend server." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:90 +msgid "Set up a server to collect data" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:92 +msgid "" +"Whether you are managing a network of |CL| systems or you don't want to " +"send records to the default telemetry server, you can set up a backend " +"server to collect your records. The backend server can be installed on " +"any Linux system and will give you the same dashboard as the default " +"server." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:95 +#: ../../guides/telemetrics/telem-guide.rst:362 +msgid "Instrument your code with the libtelemetry API" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:97 +msgid "" +"The ``telemetrics`` bundle includes the libtelemetry C library, which " +"exposes an API used by the telemprobd and telempostd daemons. You can use" +" these in your applications as well. The API documentation is found in " +"the :file:`telemetry.h` file in `Telemetrics client`_ repository." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:101 +msgid "Examples" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:108 +msgid "Enable or Disable Telemetry" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:110 +msgid "Enabling during installation" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:112 +msgid "" +"During the initial installation of |CL|, you are requested to join the " +"stability enhancement program and allow |CL| to collect anonymous reports" +" to improve system stability. If you choose not to join this program, " +"then the telemetry software bundle is not added to your system. Choosing " +"to join will automatically enable telemetry on your system after " +"installation is commplete." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:114 +msgid "Enabling after install" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:116 +msgid "To start telemetry on your system, run the following command:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:122 +msgid "" +"This enables and starts the :command:`telemprobd` and " +":command:`telempostd` daemons. Your system will begin to send telemetry " +"data to the server defined in the file " +":file:`/etc/telemetrics/telemetrics.conf`. If this file does not exist, " +"the :command:`telemprobd` and :command:`telempostd` daemons will use the " +"file :file:`/usr/share/defaults/telemetrics/telemetrics.conf`." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:124 +msgid "Disabling after install" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:126 +msgid "To disable both of the telemetry daemons, run the following command:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:132 +msgid "Opt in to telemetry" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:134 +msgid "" +"To opt-in to the telemetry services, simply enter the opt-in command and " +"start the service:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:140 +msgid "" +"This removes the :file:`/etc/telemetrics/opt-out` file, if it exists, and" +" starts the telemetry services." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:144 +msgid "" +"To opt-in but not immediately start telemetry services, you will need to " +"run the command :command:`sudo telemctl stop` after the :command:`opt-in`" +" command is entered. Once you are ready to start the service, enter the " +"command :command:`sudo telemctl start`." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:146 +msgid "Opt out of telemetry" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:148 +msgid "" +"To stop sending telemetrics data from your system, opt out of the " +"telemetry service:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:154 +msgid "" +"This creates the file :file:`/etc/telemetrics/opt-out` and stops the " +"telemetry services." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:158 +msgid "Saving Data Locally" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:160 +msgid "" +"This example requires |CL| to be installed, and telemetry to be enabled " +"on the system." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:162 +msgid "" +"To change how records are managed, we will be copying the default " +":file:`/usr/share/defaults/telemetrics/telemetrics.conf` file to " +":file:`/etc/telemetrics/telemetrics.conf` and editing it. The changes in" +" the :file:`/etc/telemetrics/telemetrics.conf` file will override the " +"defaults in the :file:`/usr/share/defaults/telemetrics/telemetrics.conf` " +"file. You may need ``root`` permissions to create and edit files in " +":file:`/etc`. For each example, and for any time you make changes to the " +"configuration file, you will need to restart the client daemons to pick " +"up the changes:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:169 +msgid "" +"The :command:`telemctl journal` command gives you access to features and " +"options of the telemetry journal to assist with system analytics and " +"debug. :command:`telemctl journal` has a number of options to help filter" +" records. Use :command:`-h` or :command:`--help` to view usage options." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:172 +msgid "Keep local copy and send records to backend server" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:174 +msgid "" +"To keep a local copy of the telemetry record and also send it on to the " +"backend server, we will need to change the " +":guilabel:`record_retention_enabled` configuration key value to " +":guilabel:`true`." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:177 +msgid "Keep all records -- don't send to backend server" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:179 +msgid "" +"To keep records on the system without sending them to a backend server, " +"set the :guilabel:`record_server_delivery_enabled` key value to " +":guilabel:`false`. Note that you will also need to ensure the " +":guilabel:`record_retention_enabled` configuration key value is set to " +":guilabel:`true` or the system will not keep local copies." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:181 +msgid "Keep and send records to custom server" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:183 +msgid "" +"This assumes you have set up a custom server according to the next " +"example." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:185 +msgid "" +"The server is identified by the :guilabel:`server` setting, and by " +"default records will be sent to the |CL| server " +":guilabel:`server=https://clr.telemetry.intel.com/v2/collector`. To " +"change this, you can use an IP address or fully qualified domain name." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:190 +msgid "Set up a backend server to collect telemetry records" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:192 +msgid "" +"For this example, start with a clean installation of |CL| on a new system" +" using the :ref:`bare-metal-install-server` getting started guide and:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:195 +msgid "" +"Join the :guilabel:`Stability Enhancement Program` to install and enable " +"the telemetrics components." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:197 +msgid "Select the manual installation method with the following settings:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:199 +msgid "Set the hostname to :guilabel:`clr-telem-server`," +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:200 +msgid "" +"Create an administrative user named :guilabel:`clear` and add this user " +"to sudoers" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:203 +msgid "" +"Log in with your administrative user, from your :file:`$HOME` directory, " +"run :command:`git` to clone the :guilabel:`telemetrics-backend` " +"repository into the :file:`$HOME/telemetrics-backend` directory:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:211 +msgid "" +"You may need to set up the :envvar:`https_proxy` environment variable if " +"you have issues reaching github.com." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:213 +msgid "" +"Change your current working directory to :file:`telemetrics-" +"backend/scripts`." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:214 +msgid "" +"We will install the telemetrics backend with the :file:`deploy.sh` script" +" file. We will set the following options and leave the remainder as " +"default:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:216 +msgid "*-a install* to perform an install" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:217 +msgid "*-d clr* to install to a |CL| distro" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:218 +msgid "*-H localhost* to set the domain to localhost" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:221 +msgid "" +"The :file:`deploy.sh` shell script has minimal error checking and makes " +"several changes to your system. Be sure that the options you define on " +"the cmdline are correct before proceeding." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:224 +msgid "" +"Run the shell script from the :file:`$HOME/telemetrics-backend/scripts` " +"directory:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:232 +msgid "" +"The script will start and list all the defined options and prompt you for" +" the :guilabel:`PostgreSQL` database password" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:245 +msgid "" +"For the :guilabel:`DB password:`, press the :kbd:`Enter` key to accept " +"the default password `postgres`." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:249 +msgid "" +"The :file:`deploy.sh` script uses :command:`sudo` to run commands and you" +" may be prompted to enter your user password at any time while the script" +" is executing. If this occurs, enter your user password to execute the " +":command:`sudo` command." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:252 +msgid "" +"Once all the server components have been installed you are prompted to " +"enter the :guilabel:`PostgreSQL` database password to change it as " +"illustrated below:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:261 +msgid "" +"Enter `postgres` for the current value of the password and then enter a " +"new password, retype it to verify the new password and the " +":guilabel:`PostgreSQL` database password will be updated." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:263 +msgid "" +"Once the installation is complete you can use your web browser to view " +"the new server by opening the browser on the system and typing in " +"``localhost`` in the address bar. You should see a web page similar to " +"the one shown in figure 1:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:268 +msgid "Figure 1: :guilabel:`Telemetry UI`" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:273 +msgid "Create records with telem-record-gen" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:275 +msgid "" +"The telemetrics bundle provides a record generator tool called ``telem-" +"record-gen``. This tool can be used to create records from shell scripts " +"or the command line when writing a probe in C is not desirable. Records " +"are sent to the backend server, and can also be echoed to stdout." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:277 +msgid "There are three ways to supply the payload to the record." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:279 +msgid "On the command line, use the :command:`-p ` option:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:305 +msgid "" +"Specify a file that contains the payload with the option :command:`-P " +"path/to/file`." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:331 +msgid "" +"If the :command:`-p` or :command:`-P` options are absent, the tool reads " +"from stdin so you can use it in a :file:`heredoc` in scripts." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:365 +msgid "Prerequisites" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:366 +msgid "" +"Confirm that the telemetrics header file is located on the system at " +":file:`usr/include/telemetry.h` The `latest version`_ of the file can " +"also be found on github for reference, but installing the `telemetry` " +"bundle will install the header file that matches your |CL| version." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:368 +msgid "Includes and variables" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:370 +msgid "" +"You will need to include the following headers in your code to use the " +"API:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:381 +msgid "" +"Use the following code to create the variables we need to hold the data " +"for the record we will be creating:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:396 +msgid "Severity:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst +msgid "Type: uint32_t" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst +msgid "" +"Value: Severity field value. Accepted values are in the range 1-4, with " +"1 being the lowest severity, and 4 being the highest severity. Values " +"provided outside of this range are clamped to 1 or 4. [low, med, high, " +"crit]" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:400 +msgid "Payload_version:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst +msgid "" +"Value: Payload format version. The only supported value right now is 1, " +"which indicates that the payload is a freely-formatted (unstructured) " +"string. Values greater than 1 are reserved for future use." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:404 +msgid "Classification:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst +msgid "Type: char array" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst +msgid "" +"Value: It should have the form, DOMAIN/PROBENAME/REST: DOMAIN is the " +"reverse domain to use as a namespace for the probe (e.g. org.clearlinux);" +" PROBENAME is the name of the probe; and REST is an arbitrary value that " +"the probe should use to classify the record. The maximum length for the " +"classification string is 122 bytes. Each sub-category may be no longer " +"than 40 bytes long. Two / delimiters are required." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:408 +msgid "Tm_handle:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst +msgid "Type: Telem_ref struct pointer" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst +msgid "" +"Value: Struct pointer declared by the caller, The struct is initialized " +"if the function returns success." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:414 +msgid "Payload:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst +msgid "Type: char pointer" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst +msgid "Value: The payload to set" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:416 +msgid "For this example, we'll set the payload to “hello” by using ``asprintf()``" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:426 +msgid "" +"The functions ``asprintf()`` and ``vasprintf()`` are analogs of " +"``sprintf(3)`` and ``vsprintf(3)``, except that they allocate a string" +" large enough to hold the output including the terminating null byte " +"('\\0'), and return a pointer to it via the first argument. This pointer" +" should be passed to ``free(3)`` to release the allocated storage when it" +" is no longer needed." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:428 +msgid "Create the new telemetry record" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:430 +msgid "" +"The function ``tm_create_record()`` initializes a telemetry record and " +"sets the severity and classification of that record, as well as the " +"payload version number. The memory needed to store the telemetry record " +"is allocated and should be freed with ``tm_free_record()`` when no longer" +" needed." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:440 +msgid "Set the payload field of a telemetrics record" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:442 +msgid "" +"The function ``tm_set_payload()`` attaches the provided telemetry record " +"data to the telemetry record. The current maximum payload size is 8192b." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:453 +msgid "" +"The ``free()`` function frees the memory space pointed to by ptr, which " +"must have been returned by a previous call to ``malloc()``, ``calloc()``," +" or ``realloc()``. Otherwise, or if ``free(ptr)`` has already been " +"called before, undefined behavior occurs. If ptr is NULL, no operation " +"is performed." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:455 +msgid "Send a record to the telemetrics daemon" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:457 +msgid "" +"The function ``tm_send_record()`` delivers the record to the local " +"``telemprobd(1)`` service. Since the telemetry record was allocated by " +"the program it should be freed with ``tm_free_record()`` when it is no " +"longer needed." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:476 +msgid "Full sample application with compiling flags" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:478 +msgid "Create a new file test.c add the following code." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:533 +msgid "Compile with the gcc compiler, using this command:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:540 +msgid "Test to ensure the program is working:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:549 +msgid "" +"A full example of the `heartbeat probe`_ in C is documented in the source" +" code." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:552 +msgid "Reference" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:559 +msgid "The Telemetry API" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:561 +msgid "" +"Installing the ``telemetrics`` bundle includes the libtelemetry C " +"library, which exposes an API used by the telemprobd and telempostd " +"daemons. You can use these in your applications as well. The API " +"documentation is found in the :file:`telemetry.h` file in `Telemetrics " +"client`_ repository." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:564 +msgid "Client Configuration" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:566 +msgid "" +"The telemetry client will look for the configuration file located at " +":file:`/etc/telemetrics/telemetrics.conf` and use it if it exists. If the" +" file does not exist, the client will use the default configuration " +"located at :file:`/usr/share/defaults telemetrics/telemetrics.conf`. To " +"modify or customize the configuration, copy the file from " +":file:`/usr/share/defaults/telemetrics` to :file:`/etc/telemetrics` and " +"edit it." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:569 +msgid "Configuration Options" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:570 +msgid "The client uses the following configuration options from the config file:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:572 +msgid "" +"**server**: This specifies the web server to which telempostd sends the " +"telemetry records." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:573 +msgid "" +"**socket_path**: This specifies the path of the unix domain socket that " +"the telemprobd listens on for connections from the probes." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:574 +msgid "" +"**spool_dir**: This configuration option is related to spooling. If the " +"daemon is not able to send the telemetry records to the backend server " +"due to reasons such as the network availability, then it stores the " +"records in a spool directory. This option specifies that path of the " +"spool directory. This directory should be owned by the same user as the " +"daemon." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:575 +msgid "" +"**record_expiry**: This is the time in minutes after which the records in" +" the spool directory are deleted by the daemon." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:576 +msgid "" +"**spool_process_time**: This specifies the time interval in seconds that " +"the daemon waits for before checking the spool directory for records. The" +" daemon picks up the records in the order of modification date and tries " +"to send the record to the server. It sends a maximum of 10 records at a " +"time. If it was able to send a record successfully, it deletes the record" +" from the spool. If the daemon finds a record older than the " +"\"record_expiry\" time, then it deletes that record. The daemon looks at " +"a maximum of 20 records in a single spool run loop." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:577 +msgid "" +"**rate_limit_enabled**: This determines whether rate-limiting is enabled " +"or disabled. When enabled, there is a threshold on both records sent " +"within a window of time, and record bytes sent within a window a time." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:578 +msgid "" +"**record_burst_limit**: This is the maximum amount of records allowed to " +"be passed by the daemon within the record_window_length of time. If set " +"to -1, the rate-limiting for record bursts is disabled." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:579 +msgid "" +"**record_window_length**: The time in minutes (0-59) that establishes the" +" window length for the record_burst_limit. EX: if " +"record_burst_window=1000 and record_window_length=15, then no more than " +"1000 records can be passed within any given fifteen minute window." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:580 +msgid "" +"**byte_burst_limit**: This is the maximum amount of bytes that can be " +"passed by the daemon within the byte_window_length of time. If set to -1," +" the rate-limiting for byte bursts is disabled." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:582 +msgid "" +"**byte_window_length**: This is the time, in minutes (0-59), that " +"establishes the window length for the byte_burst_limit." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:583 +msgid "" +"**rate_limit_strategy**: This is the strategy chosen once the rate-" +"limiting threshold has been reached. Currently the options are 'drop' or " +"'spool', with spool being the default. If spool is chosen, records will " +"be spooled and sent at a later time." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:584 +msgid "" +"**record_retention_enabled**: When this key is enabled (true) the daemon " +"saves a copy of the payload on disk from all valid records. To avoid the " +"excessive use of disk space only the latest 100 records are kept. The " +"default value for this configuration key is false." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:585 +msgid "" +"**record_server_delivery_enabled**: This key controls the delivery of " +"records to server; when enabled (default value), the record will be " +"posted to the address in the configuration file. If this configuration " +"key is disabled (false), records will not be spooled or posted to " +"backend. This configuration key can be used in combination with " +"record_retention_enabled to keep copies of telemetry records locally " +"only." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:589 +msgid "" +"Configuration options may change as the telemetry client evolves. Please " +"use the comments in the file itself as the most accurate reference for " +"configuration." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:595 +msgid "Client Run-time Options" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:596 +msgid "" +"The |CL| telemetry client provides an admin tool called " +":guilabel:`telemctl` for managing the telemetry services and probes. The " +"tool is located in :file:`/usr/bin`. Running it with no argument results " +"in the following:" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:615 +msgid "start/stop/restart" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:617 +msgid "" +"The commands to start, stop and restart the telemetry services manage all" +" required services and probes on the system. There is no need to " +"separately start/stop/restart the two client daemons **telemprobd** and " +"**telempostd**. The **restart** command option will call **telemctl " +"stop** followed by **telemctl start** ." +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:620 +msgid "is-active" +msgstr "" + +#: ../../guides/telemetrics/telem-guide.rst:622 +msgid "" +"The `is-active` option reports whether the two client daemons are active." +" This is useful to verify that the **opt-in** and **opt-out** options " +"have taken effect, or to ensure that telemetry is functioning on the " +"system. Note that both daemons are verified." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/index.po b/locale/zh_CN/LC_MESSAGES/index.po new file mode 100644 index 00000000..700ac6a4 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/index.po @@ -0,0 +1,94 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../index.rst:4 +msgid "|CL-PRJ|" +msgstr "" + +#: ../../index.rst:6 +msgid "" +"Welcome to the |CL-ATTR| documentation pages, the source for |CL| " +"documentation." +msgstr "" + +#: ../../index.rst:12 +msgid "Our documentation is divided into the following sections:" +msgstr "" + +#: ../../index.rst:15 +msgid ":ref:`get-started`" +msgstr "" + +#: ../../includes/get-started.txt:1 +msgid "" +"If you are new to |CL|, get started fast with tutorials for installing " +"|CL| on bare metal, in a virtual environment, or as a live image on a USB" +" stick." +msgstr "" + +#: ../../index.rst:19 +msgid ":ref:`tooling`" +msgstr "" + +#: ../../index.rst:18 +msgid "" +"Clear Linux is a little different from other distros. Here are some " +"important tools and concept for managing your install." +msgstr "" + +#: ../../index.rst:24 +msgid ":ref:`guides`" +msgstr "" + +#: ../../index.rst:22 +msgid "" +"Guides show how to complete common tasks that help you leverage |CL| " +"native features effectively. From basic system configuration to advanced " +"management of a cloud installation, there is a guide for you." +msgstr "" + +#: ../../index.rst:28 +msgid ":ref:`tutorials`" +msgstr "" + +#: ../../index.rst:27 +msgid "" +"|CL| tutorials provide step-by-step instructions on how |CL| features can" +" be used and extended, frequently with third-party tools." +msgstr "" + +#: ../../index.rst:32 +msgid ":ref:`reference`" +msgstr "" + +#: ../../index.rst:31 +msgid "" +"Find the detailed information you need to enable your configuration or " +"task in our |CL| reference section." +msgstr "" + +#: ../../index.rst:35 +msgid ":ref:`faq`" +msgstr "" + +#: ../../index.rst:35 +msgid "Refer to our FAQ section to read commonly asked questions and answers." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/reference/bundle-commands.po b/locale/zh_CN/LC_MESSAGES/reference/bundle-commands.po new file mode 100644 index 00000000..4691ea79 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/reference/bundle-commands.po @@ -0,0 +1,58 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/bundle-commands.rst:4 +msgid "Useful bundle commands" +msgstr "" + +#: ../../reference/bundle-commands.rst:6 +msgid "To see a list of currently installed bundles, enter:" +msgstr "" + +#: ../../reference/bundle-commands.rst:12 +msgid "To see the list of all available bundles, enter:" +msgstr "" + +#: ../../reference/bundle-commands.rst:18 +msgid "" +"Alternatively, you can view our :ref:`available bundles ` " +"webpage." +msgstr "" + +#: ../../reference/bundle-commands.rst:21 +msgid "To search for bundles and their contents, enter:" +msgstr "" + +#: ../../reference/bundle-commands.rst:27 +msgid "To add a bundle, enter:" +msgstr "" + +#: ../../reference/bundle-commands.rst:34 +msgid "Additional information" +msgstr "" + +#: ../../reference/bundle-commands.rst:36 +msgid "For additional :command:`swupd` commands, enter:" +msgstr "" + +#: ../../reference/bundle-commands.rst:42 +msgid "To reference the :command:`swupd` man page, enter:" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/reference/bundles/bundles.po b/locale/zh_CN/LC_MESSAGES/reference/bundles/bundles.po new file mode 100644 index 00000000..44329562 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/reference/bundles/bundles.po @@ -0,0 +1,41 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/bundles/bundles.rst:4 +msgid "Available bundles" +msgstr "" + +#: ../../reference/bundles/bundles.rst:6 +msgid "" +"This document provides a current list of available bundles. View the " +"`clr-bundles repo`_ on GitHub\\*, or select the bundle :file:`Name` for " +"more details." +msgstr "" + +#: ../../reference/bundles/bundles.rst:9 +msgid "" +"To learn more about how |CL-ATTR| uses bundles for software deployment, " +"visit :ref:`bundles-about`." +msgstr "" + +#: ../../reference/bundles/bundles.rst:13 +msgid "Bundle list" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/reference/bundles/openssh-server.po b/locale/zh_CN/LC_MESSAGES/reference/bundles/openssh-server.po new file mode 100644 index 00000000..d0cefde9 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/reference/bundles/openssh-server.po @@ -0,0 +1,181 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/bundles/openssh-server.rst:4 +msgid "openssh-server" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:6 +msgid "" +"The **openssh-server** bundle provides the OpenSSH\\* package needed to " +"enable an SSH service in |CL-ATTR|. Remote users require an SSH service " +"to be able to use an encrypted login shell." +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:10 +msgid "" +"|CL| enables the `sshd.socket` unit, which will listen on port 22 by " +"default and start the OpenSSH service as required. The first time OpenSSH" +" starts, it generates the server SSH keys needed for the service." +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:15 +msgid "Prerequisites" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:17 +msgid "Assure the bundle :file:`openssh-server` is installed." +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:19 +msgid "To check it it's on your host, enter:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:25 +msgid "To add it, enter:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:32 +msgid "Change default port" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:34 +msgid "" +"Perform the following steps to change the default listening port for the " +"OpenSSH service:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:37 +msgid "Open the sshd.socket file:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:43 +msgid "" +"Add the `[Socket]` section and `ListenStream` option to the sshd.socket " +"file as shown below. The first `ListenStream` entry removes the |CL| " +"default listen port value. The second `ListenStream` entry sets the new " +"default listen port value. In this example, we set the new default port " +"to 4200:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:56 +msgid "" +"Make sure to include a new line after the last line of text in the " +"sshd.socket file." +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:58 +msgid "Verify your changes:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:64 +msgid "You should see the following output:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:72 +msgid "Reload the systemd daemon configurations:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:78 +msgid "Restart the sshd.socket unit:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:84 +msgid "Confirm the the sshd.socket unit is listening on your new port:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:92 +msgid "Output should show :guilabel:`Active:` as `active(listening)`." +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:95 +msgid "Enable SFTP" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:97 +msgid "" +"|CL| *disables* the :abbr:`SFTP (SSH File Transfer Protocol)` subsystem " +"by default due to security considerations. To enable the SFTP subsystem, " +"perform the following configuration of the :abbr:`SSHD (SSH Daemon)` " +"service file:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:101 +msgid "Create a systemd drop-in directory for the SSHD service:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:107 +msgid "" +"Create the following file: " +":file:`/etc/systemd/system/sshd@.service.d/sftp.conf`" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:110 +msgid "Add the OPTIONS environment variable to the sftp.conf file." +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:117 +msgid "Reload systemd configuration:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:123 +msgid "Congratulations! The SFTP subsystem is enabled." +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:126 +msgid "Enable root login" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:128 +msgid "To enable root login via SSH, perform the following steps:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:130 +#: ../../reference/bundles/openssh-server.rst:153 +msgid "Create a *ssh* directory in :file:`/etc`, if it does not already exist." +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:136 +#: ../../reference/bundles/openssh-server.rst:159 +msgid "" +"Create the following file, if it does not already exist: " +":file:`/etc/ssh/sshd_config`" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:139 +msgid "Set the configuration variable in /etc/ssh/sshd_config" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:146 +msgid "Enable X11-forwarding" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:148 +msgid "" +"X11 forwarding allows you to securely run graphical applications (i.e., X" +" clients) over the ssh conection. This will alow for remote gui apps " +"without the need for full VNC/remotedesktop. To enable X11-forwarding via" +" SSH, perform the following steps:" +msgstr "" + +#: ../../reference/bundles/openssh-server.rst:162 +msgid "Set the configuration variables." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/reference/collaboration/collaboration.po b/locale/zh_CN/LC_MESSAGES/reference/collaboration/collaboration.po new file mode 100644 index 00000000..c3b1a476 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/reference/collaboration/collaboration.po @@ -0,0 +1,161 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/collaboration/collaboration.rst:4 +msgid "Documentation guidelines" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:6 +msgid "" +"See a missing topic in the documentation? Find an existing document that " +"could be improved? Help us out by contributing! If you haven't " +"contributed before, take a moment to review our `Contribution " +"guidelines`_." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:10 +msgid "" +"Do you have questions about the documentation that were not answered by " +"these guidelines? Send your question to the `mailing list`_." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:14 +msgid "Contribution guidelines" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:16 +msgid "" +"The |CL| documentation is hosted in GitHub and is written using " +"reStructuredText. Use our guidelines and best practices to write " +"consistent, readable documentation." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:27 +msgid "How to contribute" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:29 +msgid "There are multiple ways to contribute and help improve our documentation:" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:31 +msgid "" +"**Make a suggestion**: Have a documentation suggestion but no time to " +"write it yourself? Send your suggestion to the `mailing list`_." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:33 +msgid "" +"**Log an issue**: If you find a problem in our documentation (such as " +"typos or out-of-date information), log an issue in the `documentation " +"repository`_." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:35 +msgid "" +"**Contribute directly via GitHub**: Whether you've found a typo, have " +"better instructions or examples, or have a new page to add, submit your " +"improvement or addition as a pull request on the `documentation " +"repository`_." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:38 +msgid "" +"**Test documentation**: Step through our instructional guides and " +"tutorials to verify the instructions. Log or correct any out-of-date " +"information." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:41 +msgid "All contributions must follow our `code of conduct`_." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:44 +msgid "Contribute via GitHub" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:46 +msgid "" +"Our documentation is hosted in GitHub and we follow the standard `GitHub " +"flow`_:" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:48 +msgid "Clone the `documentation repository`_." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:50 +msgid "Create your own fork of the repository." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:52 +msgid "Create a branch for your contribution." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:54 +msgid "Add your commits." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:56 +msgid "Open a pull request." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:58 +msgid "Discuss, review, and update your contributions." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:60 +msgid "" +"Once the maintainer approves, your contribution is merged and published " +"as part of the documentation." +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:66 +msgid "References" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:68 +msgid "" +"We use the following references to guide the grammar, style, and " +"formatting of our documentation:" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:71 +msgid "`Microsoft Writing Style Guide`_" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:72 +msgid "`Merriam-Webster Dictionary`_" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:73 +msgid "" +"The Chicago Manual of Style (15th edition), The University of Chicago " +"Press" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:74 +msgid "Microsoft Press Computer Dictionary, Microsoft Press" +msgstr "" + +#: ../../reference/collaboration/collaboration.rst:75 +msgid "Read Me First!, Oracle Technical Publications" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/reference/collaboration/structure-formatting.po b/locale/zh_CN/LC_MESSAGES/reference/collaboration/structure-formatting.po new file mode 100644 index 00000000..5f0d340e --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/reference/collaboration/structure-formatting.po @@ -0,0 +1,890 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/collaboration/structure-formatting.rst:4 +msgid "Structure and formatting" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:6 +msgid "" +"Content should be organized to support scanning. Consistent organization," +" formatting, and writing style helps readers quickly find what they need " +"and to understand the content more effectively. This document describes " +"our organization and formatting guidelines." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:11 +msgid "" +"Refer to :ref:`writing-guide` to learn how we keep our documents clear " +"and concise." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:18 +msgid "Markup" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:20 +msgid "" +"Our documentation is written in the reStructuredText markup language, " +"using Sphinx roles and directives. We use Sphinx to generate the final " +"documentation. You can read more about reStructuredText and Sphinx on " +"their respective websites:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:25 +msgid "`Sphinx documentation`_" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:26 +msgid "`reStructuredText Primer`_" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:28 +msgid "" +"You can view the content directly in the .rst markup files, or generate " +"the HTML content by installing and building the documentation locally. To" +" run the documentation locally, follow the instructions found in the " +"`documentation repository`_ README." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:34 +msgid "New pages" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:36 +msgid "" +"There are a few additional steps to consider when adding a new page to " +"the documentation. First, identify where your new page should be located " +"within the existing `Documentation organization`_. Second, make sure the " +"new page is picked up in the Sphinx build and easily linkable from other " +"content." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:41 +msgid "" +"Each page must be included in a `Sphinx toctree`_ in order to be included" +" in the documentation content tree. Typically, pages are added to the " +"section landing page toctree." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:45 +msgid "For example, the :ref:`collaboration` page toctree looks like:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:55 +msgid "" +"Additionally, each page must include a uniquely named reST label directly" +" before the page title, to enable the `Sphinx ref role`_ for linking to a" +" page." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:58 +msgid "" +"For example, this page \"Structure and formating\" has the label ``.. " +"_structure-formatting``:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:68 +msgid "" +"This page can then be referenced from other pages in the documentation " +"using the `:ref:` role:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:76 +msgid "Documentation organization" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:78 +msgid "The documentation is organized into five general sections:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:80 +msgid "" +"**Concepts**: Introduction and overview of |CL| specific concepts or " +"features." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:82 +msgid "**Get started**: Information about getting started with |CL|." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:83 +msgid "**Guides**: Detailed information and instruction on using |CL| features." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:84 +msgid "" +"**Tutorials**: Step-by-step instruction for using |CL| in specific use " +"cases." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:85 +msgid "**Reference**: Supplementary and reference information for |CL|." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:88 +msgid "Page structure" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:90 +msgid "Each page in the documentation should follow the basic format of:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:92 +msgid "Overview: 1-2 sentences describing what this page shows and why it matters" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:93 +msgid "" +"Prerequisites: Describe any pre-work necessary to the content (if " +"appropriate)" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:94 +msgid "Content" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:95 +msgid "Next steps: List links to next steps (if appropriate)" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:96 +msgid "Related topics: List links to related content (if appropriate)" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:99 +msgid "Headings" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:101 +msgid "" +"Use headings to section and organize your content for better readability " +"and clarity." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:104 +msgid "All files must have a top level heading, which is the title for the page." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:105 +msgid "" +"Up to three additional levels of headings are allowed under the title " +"heading." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:106 +msgid "" +"Each heading should be followed by at least one paragraph of content. " +"Avoid two or more consecutive headings." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:109 +msgid "" +"Refer to the :ref:`writing-guide` for tips on using headings to create " +":ref:`scannable content `." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:112 +msgid "To mark up headings in the .rst file:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:114 +msgid "Use hash-tags to underline the file's main title:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:121 +msgid "Use asterisks to underline the file's first level headings:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:128 +msgid "Use equal signs to underline the file's second level of headings:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:135 +msgid "Use dashes to underline the file's third level of headings:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:143 +msgid "In-page navigation" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:145 +msgid "" +"If a page has three or more sections, provide quick links to each " +"section. Place the quick links after the overview section." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:148 +msgid "Use the standard `reST contents directive`_ with depth: 1 for quick links." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:151 +msgid "Inline text formatting" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:153 +msgid "" +"We use the `Microsoft Writing Style Guide`_ as our starting point for " +"text formatting. We apply the formatting using reST and Sphinx markup." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:156 +msgid "Use our quick reference for the most commonly used inline text elements:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:159 +msgid "**Element**" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:159 +msgid "**Convention**" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:159 +msgid "**reST/Sphinx**" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:161 +msgid "Acronyms" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:161 +msgid "" +"Define acronym when first used. After first use and definition, use the " +"acronym only." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:161 +msgid "Use the ``:abbr:`` role, in the following format:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:164 +msgid "``:abbr:`Acronym (Def)```" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:166 +msgid "Bundle names" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:166 +#: ../../reference/collaboration/structure-formatting.rst:174 +#: ../../reference/collaboration/structure-formatting.rst:176 +msgid "Bold" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:166 +#: ../../reference/collaboration/structure-formatting.rst:174 +#: ../../reference/collaboration/structure-formatting.rst:176 +msgid "Use the ``:command:`` role." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:168 +msgid "Callouts" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:168 +msgid "Use ``.. note::``" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:170 +msgid "Code/command examples" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:170 +msgid "" +"Monospace, visually distinct from rest of text. Use an indented call-out " +"box." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:170 +msgid "Use ``.. code-block::`` with the correct language setting." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:174 +msgid "Commands" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:176 +msgid "Command flags" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:178 +msgid "Console output" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:178 +msgid "" +"Monospace, visual distinction from rest of text. Use an indented call-out" +" box." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:178 +msgid "Use ``.. code-block::`` with console as the language setting." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:182 +msgid "Emphasis" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:182 +msgid "Italic" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:182 +msgid "``*strong*``" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:184 +msgid "Environment variables" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:184 +msgid "Use the case format of the environment variable." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:184 +msgid "Use ``:envvar:``" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:187 +msgid "Example commands with optional or replaceable parts" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:187 +msgid "Use angle brackets for swapping in the specific name, e.g. ." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:191 +msgid "Use square brackets for optional parts, e.g. [--build]." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:195 +msgid "Example URLs (not linked)" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:195 +msgid "Plain text" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:197 +msgid "File extensions" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:197 +msgid "Lowercase" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:199 +msgid "File names, directories, paths" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:199 +msgid "Title style capitalization" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:199 +msgid "Use the ``:file:`` role." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:201 +msgid "GUI labels" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:201 +msgid "Use ``:guilabel:``" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:203 +msgid "Inline comments" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:203 +msgid "Use ``..``" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:205 +msgid "Keystrokes" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:205 +msgid "Use ``:kbd:``" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:207 +msgid "Local navigation" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:207 +msgid "``.. contents:: :local:`` with a depth of 1" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:210 +msgid "Menu selection" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:210 +msgid "Use ``:menuselection:``" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:212 +msgid "New terms" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:212 +msgid "Italic for first use, normal for all subsequent uses." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:215 +msgid "If it is used outside of the source of definition, link the term." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:212 +msgid "``*term*``" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:218 +msgid "Product name" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:218 +msgid "Follow correct trademark and attribution guidelines." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:221 +msgid "Tool names" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:221 +msgid "Correctly capitalized, no quotes, bold, or italics as the basic rule." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:224 +msgid "" +"If the tool name is the command, like most Linux tools, treat it like a " +"command." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:228 +msgid "" +"If the tool name is lowercase and used at the start of a sentence, use " +"bold." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:234 +msgid "White space and line length" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:236 +msgid "" +"Limit line length to 78 characters. The GitHub web interface forces this " +"limitation for readability." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:239 +msgid "Remove trailing whitespace from your documents." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:242 +msgid "Code blocks and examples" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:244 +msgid "" +"When providing example code or commands use the `Sphinx code-block " +"directive`_. Select the appropriate syntax highlighting for the example " +"command or code." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:247 +msgid "For example, if showing console output, use console highlighting:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:253 +msgid "Sphinx provides other ways of `marking up example code`_ if needed." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:256 +msgid "Lists and instructions" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:258 +msgid "" +"Use a numbered list when the order or priority of the items is important," +" such as step-by-step instructions." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:261 +msgid "Use a bulleted list when the order of the items is not important." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:263 +msgid "" +"For both list types, keep all items in the list parallel. See " +":ref:`parallelism`." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:266 +msgid "Use standard `reST list markup`_." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:269 +msgid "Numbered lists" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:271 +msgid "" +"Numbered lists are most frequently used for procedures. Use numbered " +"lists to show sequence for the items. Follow our guidelines for numbered " +"lists:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:274 +msgid "Make sure the list is sequential and not just a collection of items." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:275 +msgid "" +"Introduce a numbered list with a sentence. End the setup text with a " +"colon. Example: \"To configure the unit, perform the following steps:\"" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:277 +#: ../../reference/collaboration/structure-formatting.rst:299 +msgid "Each item in the list should be parallel." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:278 +msgid "" +"Treat numbered list items as full sentences with correct ending " +"punctuation." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:280 +msgid "" +"You may interrupt numbered lists with other content, if relevant, e.g. " +"explanatory text, commands, or code." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:282 +msgid "Second-level steps are acceptable; avoid third-level steps." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:283 +msgid "" +"Avoid single-step procedures; the minimum number of steps in a procedure " +"is two." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:285 +msgid "" +"Do not create numbered lists that emulate flowcharts. The reader should " +"be able to execute the list of steps from first to last without branching" +" or looping." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:288 +msgid "" +"Avoid over-using numbered lists, except in procedural documents such as " +"tutorials and step-by-step guides." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:292 +msgid "Bulleted lists" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:294 +msgid "" +"Use bulleted lists to reduce wordiness and paragraph density, especially " +"when a sequence is not required. Here are some guidelines for bulleted " +"lists:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:297 +msgid "" +"Introduce a bulleted list with a sentence. End the setup text with a " +"colon. Example: \"To repair the unit, you will need the following " +"items:\"" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:300 +msgid "Avoid interrupting bulleted lists with other paragraph styles." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:301 +msgid "Second-level bullets are acceptable; avoid third-level bullets." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:303 +msgid "" +"Use the correct ending punctuation for sentence style bullet lists. For " +"example:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:305 +msgid "**Use this:**" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:315 +msgid "**Not this:**" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:327 +msgid "Instructions" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:329 +msgid "" +"When presenting instructions, such as in a tutorial, present them in a " +"numbered list according to these guidelines:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:332 +msgid "Each step (list item) should describe one action." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:334 +msgid "" +"If the same steps are repeated, refer to the earlier steps rather than " +"repeating them." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:337 +msgid "" +"When a step includes a command or code block as an example, put the " +"command or code block after the step that includes them." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:340 +msgid "" +"Use supporting images where appropriate. If the series of steps is " +"supported by one figure, refer to the figure in the introductory text." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:343 +msgid "For example: \"See Figure 15 and do the following:\"" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:345 +msgid "" +"When a series of steps is supported by two or more figures, refer to the " +"specific figure in the relevant step and show the figure immediately " +"after the reference. **Do not write**: \"See figures 15 through 22 and do" +" the following:\"" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:351 +msgid "Notices" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:353 +msgid "" +"We use four special types of notices: notes, cautions, warnings, and " +"dangers. Here are some specific rules and tips regarding use of these " +"notices:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:356 +msgid "" +"Do not use a notice directly after a heading. Notices must follow a " +"variant of body text." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:358 +msgid "Do not include more than one notice in a single notice block." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:359 +msgid "Avoid back-to-back notices." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:360 +msgid "" +"If back-to-back notices are not avoidable, make sure each distinct notice" +" in the notice block is clearly defined." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:363 +msgid "Use the standard `reST admonition directive`_." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:366 +msgid "Notes, cautions, and warnings" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:368 +msgid "" +"Use notes sparingly. Avoid having more than one note per section. If you " +"exceed this number consistently, consider rewriting the notes as main " +"body text." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:371 +msgid "" +"Use cautions and warnings to alert readers of potential problems or " +"pitfalls. Use conditional phrases in cautions and warnings, such as \"If " +"you do X, then Y will occur.\"" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:375 +msgid "These are examples of typical notices and the conditions for their usage:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:378 +msgid "" +"Notes are extra bits of information that supplement the main content. " +"Notes should be relatively short." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:382 +msgid "" +"Cautions are low-level hazard messages that alert the user of possible " +"equipment, product, and software damage, including loss of data." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:386 +msgid "Warnings are mid-level hazards that are likely to cause product damage." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:389 +msgid "Links" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:391 +msgid "Use the standard `reST markup for links`_." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:393 +msgid "" +"To add a cross-reference to another documentation page, use the `:ref:` " +"role:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:399 +msgid "" +"To add an external link, we use named references that refer to a defined " +"link/label at the bottom of the page." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:402 +msgid "" +"For example, an external link is defined at the bottom of the page like " +"this:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:408 +msgid "The defined link is then used in the content like this:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:415 +msgid "Images" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:417 +msgid "" +"Use images or figures to convey information that may be difficult to " +"explain using words alone. Well-planned graphics reduce the amount of " +"text required to explain a topic or example." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:421 +msgid "" +"Follow these guidelines when using graphics in support of your " +"documentation:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:423 +msgid "" +"Keep it simple. Use images that serve a specific purpose in your " +"document, and contain only the information the reader needs." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:426 +msgid "" +"Avoid graphics that will need frequent updating. Don't include " +"information in a graphic that might change with each release, such as " +"product versions." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:429 +msgid "" +"Use either PNG or JPEG bitmap files for screenshots and SVG files for " +"vector graphics." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:432 +msgid "" +"Place the image immediately after the text it helps clarify, or as close " +"as possible." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:435 +msgid "" +"Use the `Sphinx figure directive`_ to insert images and figures into the " +"document. Include both alt text, a figure name, and caption." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:438 +msgid "For example:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:447 +msgid "" +"Include at least one direct reference to an image from the main text, " +"using the figure number. For example:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:450 +msgid "**Use this:** ::" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:454 +msgid "**Not this:** ::" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:458 +msgid "Images should follow these naming and location conventions:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:460 +msgid "" +"Save the image files in a :file:`figures` folder at the same level as the" +" file that will reference the image." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:462 +msgid "Name image files according to the following rules:" +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:464 +msgid "Use only lower case letters." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:465 +msgid "Separate multiple words in filenames using dashes." +msgstr "" + +#: ../../reference/collaboration/structure-formatting.rst:466 +msgid "" +"Name images using the filename of the file they appear on and add a " +"number to indicate their place in the file. For example, the third figure" +" added to the :file:`welcome.rst` file must be named " +":file:`welcome-3.png`." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/reference/collaboration/writing-guide.po b/locale/zh_CN/LC_MESSAGES/reference/collaboration/writing-guide.po new file mode 100644 index 00000000..9167d289 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/reference/collaboration/writing-guide.po @@ -0,0 +1,689 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/collaboration/writing-guide.rst:4 +msgid "Writing guide" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:6 +msgid "" +"We want our documentation to be easy to read and understand. This " +"document describes guidelines for writing documentation that is clear, " +"concise, confident, and courteous." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:10 +msgid "" +"Refer to :ref:`structure-formatting` for details on organizing content " +"and how we use reStructuredText and Sphinx." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:17 +msgid "Use simple English" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:19 +msgid "" +"Write using simple English: Be brief and communicate only the information" +" that is needed. Be friendly and informative. Emphasize clarity and avoid" +" unecessary complicated or technical terms. Make the content accessible " +"to non-native speakers." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:25 +msgid "Be brief" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:27 +msgid "" +"Use short sentences and paragraphs. Stick to the principle of one main " +"idea per sentence, plus one additional point if needed. Each paragraph " +"should address one main idea. Remember the basic structure of a " +"paragraph: Introduction, body, and conclusion." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:33 +msgid "Be friendly" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:35 +msgid "" +"We write for our peers and want to be familiar. Take a personal tone as " +"if you were speaking directly to the reader. Use \"you\" to address the " +"reader and \"we\" to refer to our view. Be professional, respectful, and " +"cooperative." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:39 +msgid "" +"Assume your audience has the same level of technical understanding and " +"expertise as you did when you first started collaborating. Do not talk " +"down to our readers, but also do not assume they know everything about " +"the subject. Offer brief explanations or summaries of common knowledge if" +" a significant portion of readers might benefit." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:46 +msgid "Use simple words" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:48 +msgid "" +"Use simple words to increase reader comprehension and reduce ambiguity. " +"Follow our tips for making good word choices:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:51 +msgid "" +"**Avoid jargon**: Write for your audience, using everyday language where " +"possible, and technical terms where appropriate. Avoid clichés, idioms, " +"and metaphors." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:54 +msgid "" +"**Be consistent**: Use one term for each concept or action and use it " +"consistently." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:56 +msgid "" +"**Avoid \"fancy\" words and phrases**: If there is a simpler word or " +"phrase, use it." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:59 +#: ../../reference/collaboration/writing-guide.rst:151 +#: ../../reference/collaboration/writing-guide.rst:202 +#: ../../reference/collaboration/writing-guide.rst:213 +#: ../../reference/collaboration/writing-guide.rst:258 +#: ../../reference/collaboration/writing-guide.rst:368 +msgid "For example:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:62 +msgid "Use this" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:62 +msgid "Not this" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:64 +msgid "start, begin" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:64 +msgid "commence" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:65 +msgid "so" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:65 +msgid "consequently" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:66 +msgid "more than" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:66 +msgid "in excess of" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:67 +msgid "if" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:67 +msgid "in the event of" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:68 +msgid "before" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:68 +msgid "prior to" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:69 +msgid "if you want" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:69 +msgid "should one wish" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:70 +msgid "use" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:70 +msgid "utilize" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:71 +msgid "example" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:71 +msgid "instance" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:75 +msgid "Avoid overuse of product name" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:77 +msgid "" +"Use product names only when necessary. Typically, you can rewrite " +"sentences to remove the product name with no change in meaning, which " +"keeps the content concise and scannable." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:81 +msgid "Avoid using the product name in page titles and headings." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:86 +msgid "Make content scannable" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:88 +msgid "" +"Organize your content to make it scannable for the reader, which helps " +"them find what they need quickly, and to understand the information more " +"efficiently." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:91 +msgid "" +"**Put the most important content first.** Make sure your introduction " +"clearly communicates what the reader can find on the page. Present the " +"point of the document first, and organize supporting information towards " +"the end of the page." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:95 +msgid "" +"**Write scannable headings.** Expect readers of documentation to skim and" +" scan the content, and to leave if they dont find what they need quickly." +" Good headings add organization to your content and help the reader to " +"find and understand content more effectively. Follow our guidelines for " +"writing effective `Headings`_." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:100 +msgid "" +"**Write great link text.** Great link text tells the reader what they can" +" expect when they click on a link. It also helps make the page more " +"scannable. Follow our guidelines for writing `Link text`_." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:105 +msgid "Headings" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:107 +msgid "Use these guidelines to write effective headings:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:109 +msgid "" +"**Be concise and descriptive.** Use only the words necessary to describe " +"the section." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:111 +msgid "" +"**Use sentence case.** Capitalize only the first word and proper nouns in" +" a heading." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:113 +msgid "" +"**Avoid punctuation.** Unless your heading is a question, don't use " +"sentence punctuation in headings." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:115 +msgid "" +"**Use parallel structure.** Headings at the same level should use the " +"same grammatical pattern. This provides structure to the document and " +"helps users find information more easily. See :ref:`parallelism`." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:118 +msgid "" +"**Use strong verbs.** Strong, active verbs get to the point. Avoid -ing " +"verbs, such as *Running*, *Testing*, etc." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:121 +msgid "For example, two headings at the same level:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:123 +#: ../../reference/collaboration/writing-guide.rst:153 +#: ../../reference/collaboration/writing-guide.rst:173 +#: ../../reference/collaboration/writing-guide.rst:189 +#: ../../reference/collaboration/writing-guide.rst:215 +#: ../../reference/collaboration/writing-guide.rst:225 +#: ../../reference/collaboration/writing-guide.rst:239 +#: ../../reference/collaboration/writing-guide.rst:260 +#: ../../reference/collaboration/writing-guide.rst:270 +#: ../../reference/collaboration/writing-guide.rst:285 +#: ../../reference/collaboration/writing-guide.rst:401 +msgid "**Use this:** ::" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:129 +#: ../../reference/collaboration/writing-guide.rst:157 +#: ../../reference/collaboration/writing-guide.rst:177 +#: ../../reference/collaboration/writing-guide.rst:193 +#: ../../reference/collaboration/writing-guide.rst:219 +#: ../../reference/collaboration/writing-guide.rst:229 +#: ../../reference/collaboration/writing-guide.rst:243 +#: ../../reference/collaboration/writing-guide.rst:264 +#: ../../reference/collaboration/writing-guide.rst:274 +#: ../../reference/collaboration/writing-guide.rst:289 +#: ../../reference/collaboration/writing-guide.rst:405 +msgid "**Not this:** ::" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:136 +msgid "Link text" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:138 +msgid "All links in content should follow these guidelines:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:140 +msgid "" +"**Write descriptive link text**: Link text should describe where the link" +" goes, without having to read the surrounding text." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:142 +msgid "" +"**Keep link text concise**: Use only the words needed to accurately " +"describe the destination." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:144 +msgid "" +"**Use unique link text**: Each link on a page should be unique. If users " +"see the same link text twice on a page, they'll assume it goes to the " +"same place." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:146 +msgid "" +"**Start link text with keywords**: Frontload the link text with the most " +"important words to help users scan the text." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:148 +msgid "" +"**Avoid generic text**: Don't use generic, uninformative link text such " +"as \"click here\" or \"read more\"." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:162 +msgid "Use strong verbs" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:164 +msgid "" +"Passive verbs make writing stuffy and formal. Use strong verbs to get to " +"the point and avoid unnecessary words and phrases." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:168 +msgid "Use imperatives" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:170 +msgid "" +"Commands, also called imperatives, are the fastest and most direct way of" +" giving someone instructions. For example:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:182 +msgid "Use present tense" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:184 +msgid "" +"Use simple present tense instead of future tense for most text. Search " +"for the words \"will\" or \"shall\" to find future tense instances. " +"Future tense is acceptable for conditional statements, such as in a " +"caution or a warning. For example:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:198 +msgid "Avoid nominalizations" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:200 +msgid "Avoid nominalizations, which are nouns formed from verbs." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:205 +msgid "Verb" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:205 +msgid "Nominalization" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:207 +msgid "complete" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:207 +msgid "completion" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:208 +msgid "provide" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:208 +msgid "provision" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:209 +msgid "fail" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:209 +msgid "failure" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:210 +msgid "install" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:210 +msgid "installation" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:223 +#: ../../reference/collaboration/writing-guide.rst:268 +msgid "Or:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:234 +msgid "Avoid words ending in -ing" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:236 +msgid "" +"Avoid using words ending in -ing unless they are part of a technical " +"name. For example:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:248 +msgid "Use the active voice" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:250 +msgid "" +"Use active voice whenever possible to show who or what is performing an " +"action." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:253 +msgid "" +"Active voice follows standard English word order: SUBJECT–VERB–OBJECT " +"(where the OBJECT is optional)." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:255 +msgid "" +"Passive voice reverses the order and weakens the verb: OBJECT–be VERB–by " +"SUBJECT (where the OBJECT is optional)." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:279 +msgid "Avoid long noun phrases" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:281 +msgid "" +"Noun phrases (a noun and other words that describe or modify it) can be " +"difficult to understand. Try to limit the number of modifiers in a noun " +"phrase to two. For example:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:296 +msgid "Parallelism" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:298 +msgid "" +"Parallelism refers to the practice of using similar patterns of grammar, " +"and sometimes length, to coordinate words, phrases, and clauses." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:301 +msgid "" +"Use parallel construction in lists. The table below shows some unparallel" +" structures and how they can be made parallel with a little rewording." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:305 +msgid "Parallel (do)" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:305 +msgid "Unparallel (don't)" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:307 +msgid "Mount the panel." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:308 +msgid "Install the battery." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:309 +msgid "Wire the keypad." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:308 +msgid "Battery installation." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:309 +msgid "Wiring the keypad." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:311 +msgid "" +"I like practicing my accordion, reading sci-fi, and eating peanut butter " +"and pickle sandwiches." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:311 +msgid "" +"I like practicing my accordion, reading sci-fi, and to eat peanut butter " +"and pickle sandwiches." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:316 +msgid "For breakfast he likes coffee and bacon." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:316 +msgid "For breakfast he likes coffee and to fry bacon." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:319 +msgid "Apples or bananas are a good snack." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:319 +msgid "Apples or a banana are a good snack." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:324 +msgid "Grammar and punctuation" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:326 +msgid "" +"This section covers common grammatical topics relevant to our " +"documentation. For detailed explanations of correct grammar and " +"punctuation, use one of our :ref:`preferred references `." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:331 +msgid "Capitalization" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:333 +msgid "" +"The capitalization style for all documentation is sentence case. Words " +"should only be capitalized when they are proper nouns or refer to " +"trademarked product names." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:338 +msgid "" +"Do not capitalize a word to indicate it is more important than other " +"words. Never change the case of variable, function or file names - always" +" keep the original case." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:343 +msgid "Menu capitalization" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:345 +msgid "" +"When referring to software menu items by name, use the same " +"capitalization as seen in the actual menu." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:348 +msgid "A few other tips when referring to menu items:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:350 +msgid "" +"Reference the specific menu item using \"Select :menuselection:`File --> " +"New`.\"" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:352 +msgid "" +"Put the option to be selected last. \"Select :menuselection:`View --> " +"Side Bar --> Hide Side Bar`\"" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:355 +msgid "" +"Do not include more than 3 navigation steps in a menu selection. If more " +"than three steps are needed, divide the steps using ``:guilabel:`` or " +"``:menuselection:``." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:359 +msgid "" +"For example: \"Go to :guilabel:`File` and select :menuselection:`Print " +"--> Print Preview --> Set Up`.\"" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:363 +msgid "Software version capitalization" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:365 +msgid "" +"When listing software or hardware version numbers, the word “version” or " +"letter \"v\" are lowercase. The v is closed with the number (no period)." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:370 +msgid "Widget Pro version 5.0" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:371 +msgid "Widget Master v2.1.12" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:374 +msgid "Contractions" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:376 +msgid "" +"Avoid using contractions, such as it's, they're, and you're, because they" +" may be unclear to non-native English-speaking audiences." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:380 +msgid "Quotation marks" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:382 +msgid "Follow these guidelines for quotation marks:" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:384 +msgid "Restrict use of quotation marks to terms as terms." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:385 +msgid "Do not use quotation marks for emphasis; use *italics* for emphasis." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:386 +msgid "Avoid using single-quote marks." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:389 +msgid "Commas and colons" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:391 +msgid "" +"This section addresses common use of commas, semicolons, and colons in " +"our documentation. Refer to one of our :ref:`preferred references " +"` for further details." +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:396 +msgid "Use the serial comma" +msgstr "" + +#: ../../reference/collaboration/writing-guide.rst:398 +msgid "" +"When writing a series of items, use the serial comma before the final " +"*and* and *or* to avoid confusion and ambiguity. For example:" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/reference/compatible-hardware.po b/locale/zh_CN/LC_MESSAGES/reference/compatible-hardware.po new file mode 100644 index 00000000..77baec94 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/reference/compatible-hardware.po @@ -0,0 +1,262 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/compatible-hardware.rst:4 +msgid "Compatible Hardware" +msgstr "" + +#: ../../reference/compatible-hardware.rst:6 +msgid "" +"This document describes hardware that has been tested and confirmed as " +"compatible with |CL-ATTR|. This list is not comprehensive and will " +"continue to grow." +msgstr "" + +#: ../../reference/compatible-hardware.rst:10 +msgid "**Table 1. Compatible Hardware**" +msgstr "" + +#: ../../reference/compatible-hardware.rst:14 +msgid "Processor SKU" +msgstr "" + +#: ../../reference/compatible-hardware.rst:15 +msgid "Platform" +msgstr "" + +#: ../../reference/compatible-hardware.rst:17 +#: ../../reference/compatible-hardware.rst:98 +#: ../../reference/compatible-hardware.rst:110 +msgid "Intel® Core™ i5-6260U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:20 +msgid "Intel® Core™ i5-6560U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:21 +msgid "Dell XPS\\* 13 9350" +msgstr "" + +#: ../../reference/compatible-hardware.rst:23 +#: ../../reference/compatible-hardware.rst:92 +msgid "Intel® Celeron® J3455" +msgstr "" + +#: ../../reference/compatible-hardware.rst:24 +msgid "NUC6CAYS" +msgstr "" + +#: ../../reference/compatible-hardware.rst:26 +#: ../../reference/compatible-hardware.rst:65 +msgid "Intel® Core™ i5-4250U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:29 +#: ../../reference/compatible-hardware.rst:101 +#: ../../reference/compatible-hardware.rst:107 +msgid "Intel® Core™ i7-5557U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:32 +msgid "Intel® Core™ i9-7900X" +msgstr "" + +#: ../../reference/compatible-hardware.rst:33 +msgid "Gigabyte\\* X299" +msgstr "" + +#: ../../reference/compatible-hardware.rst:35 +msgid "Intel® Core™ i3-4130" +msgstr "" + +#: ../../reference/compatible-hardware.rst:36 +msgid "Lenovo Thinkserver\\* TS140" +msgstr "" + +#: ../../reference/compatible-hardware.rst:38 +msgid "Intel® Core™ i7-7567U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:39 +msgid "NUC7i7BNH" +msgstr "" + +#: ../../reference/compatible-hardware.rst:41 +msgid "Intel® Core™ i7-8809G" +msgstr "" + +#: ../../reference/compatible-hardware.rst:42 +msgid "NUC8i7HVK" +msgstr "" + +#: ../../reference/compatible-hardware.rst:44 +msgid "Intel® Core™ i5-7260U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:45 +msgid "NUC7i5BNH" +msgstr "" + +#: ../../reference/compatible-hardware.rst:47 +msgid "Intel® Core™ i7-8650U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:48 +msgid "NUC7i7DNKE" +msgstr "" + +#: ../../reference/compatible-hardware.rst:50 +msgid "Intel® Core™ i5-7300U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:51 +msgid "NUC7i5DNHE" +msgstr "" + +#: ../../reference/compatible-hardware.rst:53 +msgid "Intel® Xeon® Gold 6138" +msgstr "" + +#: ../../reference/compatible-hardware.rst:56 +msgid "Intel® Xeon® E5-2699A v4" +msgstr "" + +#: ../../reference/compatible-hardware.rst:57 +msgid "Dell PowerEdge\\* R630" +msgstr "" + +#: ../../reference/compatible-hardware.rst:59 +msgid "Intel® Xeon® E5-2620 v3" +msgstr "" + +#: ../../reference/compatible-hardware.rst:62 +msgid "Intel® Core™ i5-6600" +msgstr "" + +#: ../../reference/compatible-hardware.rst:63 +msgid "Gigabyte\\* Z170X-UD5" +msgstr "" + +#: ../../reference/compatible-hardware.rst:66 +msgid "D54250WYK" +msgstr "" + +#: ../../reference/compatible-hardware.rst:68 +msgid "Intel® Xeon® E5-2699 v3" +msgstr "" + +#: ../../reference/compatible-hardware.rst:69 +msgid "S2600WT2" +msgstr "" + +#: ../../reference/compatible-hardware.rst:71 +msgid "Intel® Atom™ J3455" +msgstr "" + +#: ../../reference/compatible-hardware.rst:72 +#: ../../reference/compatible-hardware.rst:93 +msgid "NUC6CAYB" +msgstr "" + +#: ../../reference/compatible-hardware.rst:74 +msgid "Intel® Xeon® Bronze 3104" +msgstr "" + +#: ../../reference/compatible-hardware.rst:75 +msgid "0W23H8" +msgstr "" + +#: ../../reference/compatible-hardware.rst:77 +msgid "Intel® Atom™ C2750" +msgstr "" + +#: ../../reference/compatible-hardware.rst:78 +msgid "SuperMicro\\* A1SAi" +msgstr "" + +#: ../../reference/compatible-hardware.rst:80 +msgid "Intel® Atom™ E3825" +msgstr "" + +#: ../../reference/compatible-hardware.rst:81 +msgid "CircuitCo MinnowBoard MAX\\*" +msgstr "" + +#: ../../reference/compatible-hardware.rst:83 +msgid "Intel® Core™ i7-8700" +msgstr "" + +#: ../../reference/compatible-hardware.rst:84 +msgid "Gigabyte\\* H370 WIFI" +msgstr "" + +#: ../../reference/compatible-hardware.rst:86 +msgid "Intel® Core™ i7-3667U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:87 +msgid "Lenovo ThinkPad\\* X1 Carbon laptop" +msgstr "" + +#: ../../reference/compatible-hardware.rst:89 +msgid "Intel® Core™ i5-4210U" +msgstr "" + +#: ../../reference/compatible-hardware.rst:90 +msgid "Dell XPS\\* 13 laptop" +msgstr "" + +#: ../../reference/compatible-hardware.rst:95 +msgid "Intel® Core™ i7-4790" +msgstr "" + +#: ../../reference/compatible-hardware.rst:96 +msgid "Gigabyte\\* desktop" +msgstr "" + +#: ../../reference/compatible-hardware.rst:99 +msgid "NUC6I6SYH" +msgstr "" + +#: ../../reference/compatible-hardware.rst:102 +msgid "NUC5I7RYH" +msgstr "" + +#: ../../reference/compatible-hardware.rst:104 +msgid "Intel® Core™ i7-4700MQ" +msgstr "" + +#: ../../reference/compatible-hardware.rst:105 +msgid "Lenovo ThinkPad\\* T540p" +msgstr "" + +#: ../../reference/compatible-hardware.rst:108 +msgid "NUC5I7RYB" +msgstr "" + +#: ../../reference/compatible-hardware.rst:111 +msgid "NUC6I5SYH" +msgstr "" + +#: ../../reference/compatible-hardware.rst:113 +msgid "\\* Other names and brands may be claimed as the property of others." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/reference/how-to-clear-overview.po b/locale/zh_CN/LC_MESSAGES/reference/how-to-clear-overview.po new file mode 100644 index 00000000..f6cbfb7f --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/reference/how-to-clear-overview.po @@ -0,0 +1,94 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/how-to-clear-overview.rst:4 +msgid "How to Clear training overview" +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:6 +msgid "" +"The existing Linux\\* ecosystem can be challenging to users because of " +"long intervals between :abbr:`OS (operating system)` updates, which leads" +" to large update downloads. Users can also be frustrated when managing " +"complicated component dependencies. |CL-ATTR| solves these problems by:" +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:11 +msgid "Allowing you to update frequently, even multiple times per day" +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:12 +msgid "Preventing you from combining incompatible components" +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:14 +msgid "" +"The |CL| team delivers technology advances with the |CL| OS and its " +"tooling, concepts, and content. The team has created training materials " +"as a GitHub\\* project to get you up and running quickly." +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:18 +msgid "" +"The training provides complete details on the methods used to create " +"updates and how to deploy the updates to targets. The following items " +"provide an overview of these |CL| mechanisms:" +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:22 +msgid "" +"Update server: an https-enabled web server where the content files are " +"served as static content. |CL| periodically queries the data on the " +"update server and determines whether updates are available. The update " +"content files provide the data and metadata to perform the required " +"actions." +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:27 +msgid "" +"Software delivery mechanism: :abbr:`swupd (software updater)` queries " +"metadata from the update server and calculates what to do and which " +"content to use." +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:31 +msgid "" +"Tools: `mixer-tools` software suite generates the update server content " +"using |CL| official software update content, local bundle definitions, " +"and local RPM files." +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:34 +msgid "" +"The training helps you create a customized OS that is based on |CL|. The " +"training content is self-contained and hosted on GitHub. You need a clean" +" |CL| installation and a functional network connection to complete the " +"training. For convenience, the project includes the training files you " +"need for the exercises." +msgstr "" + +#: ../../reference/how-to-clear-overview.rst:40 +msgid "" +"We appreciate your feedback and comments, especially in the form of Pull " +"Requests. Please visit the `how-to-clear project`_ page to access the " +"training materials, open a ticket, or clone/branch the training and help " +"us improve |CL|." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/reference/image-types.po b/locale/zh_CN/LC_MESSAGES/reference/image-types.po new file mode 100644 index 00000000..1a68069c --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/reference/image-types.po @@ -0,0 +1,191 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/image-types.rst:4 +msgid "|CL-ATTR| image types" +msgstr "" + +#: ../../reference/image-types.rst:8 +msgid "" +"|CL-ATTR| offers many types of `images`_ for different platforms and " +"environments." +msgstr "" + +#: ../../reference/image-types.rst:12 +msgid "The naming convention of a |CL| image filename is:" +msgstr "" + +#: ../../reference/image-types.rst:18 +msgid "The *[version number]* field specifies the version number." +msgstr "" + +#: ../../reference/image-types.rst:20 +msgid "" +"The *[image type]* field specifies the type of image and its " +"corresponding file format." +msgstr "" + +#: ../../reference/image-types.rst:23 +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:28 +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:31 +msgid "Table 1: Types of platform-independent |CL| images" +msgstr "" + +#: ../../reference/image-types.rst:35 ../../reference/image-types.rst:48 +msgid "Image Type" +msgstr "" + +#: ../../reference/image-types.rst:36 ../../reference/image-types.rst:49 +msgid "Description" +msgstr "" + +#: ../../reference/image-types.rst:38 +msgid "live-desktop.img or live-desktop.iso" +msgstr "" + +#: ../../reference/image-types.rst:39 +msgid "Image for booting to GNOME\\* desktop to preview or install the OS." +msgstr "" + +#: ../../reference/image-types.rst:41 +msgid "live-server.img or live-server.iso" +msgstr "" + +#: ../../reference/image-types.rst:42 +msgid "Image for booting to server command prompt to preview or install the OS." +msgstr "" + +#: ../../reference/image-types.rst:44 +msgid "Table 2: Types of platform-specific |CL| images" +msgstr "" + +#: ../../reference/image-types.rst:51 +msgid "aws.img" +msgstr "" + +#: ../../reference/image-types.rst:52 +msgid "Image suitable for use with Amazon\\* AWS\\*." +msgstr "" + +#: ../../reference/image-types.rst:54 +msgid "azure.vhd" +msgstr "" + +#: ../../reference/image-types.rst:55 +msgid "Virtual Hard Disk for use on Microsoft\\* Azure\\* cloud platform." +msgstr "" + +#: ../../reference/image-types.rst:57 +msgid "azure-docker.vhd" +msgstr "" + +#: ../../reference/image-types.rst:58 +msgid "" +"Virtual Hard Disk for use on Microsoft Azure cloud platform with " +"Docker\\* pre-installed." +msgstr "" + +#: ../../reference/image-types.rst:60 +msgid "azure-machine-learning.vhd" +msgstr "" + +#: ../../reference/image-types.rst:61 +msgid "" +"Virtual Hard Disk for use on Microsoft Azure cloud platform with the " +"`machine-learning-basic` bundle installed." +msgstr "" + +#: ../../reference/image-types.rst:63 +msgid "cloudguest.img" +msgstr "" + +#: ../../reference/image-types.rst:64 +msgid "" +"Image with generic cloud guest virtual machine (VM) requirements " +"installed." +msgstr "" + +#: ../../reference/image-types.rst:66 +msgid "gce.tar" +msgstr "" + +#: ../../reference/image-types.rst:67 +msgid "Image with the Google Compute Engine (GCE) specific kernel." +msgstr "" + +#: ../../reference/image-types.rst:69 +msgid "hyperv.vhdx" +msgstr "" + +#: ../../reference/image-types.rst:70 +msgid "" +"Virtual Hard Disk for use with Microsoft Hyper-V\\* hypervisor. Includes " +"`optimized kernel`_ for Hyper-V." +msgstr "" + +#: ../../reference/image-types.rst:72 +msgid "kvm.img" +msgstr "" + +#: ../../reference/image-types.rst:73 +msgid "" +"Image for booting in a simple VM with start_qemu.sh. Includes `optimized " +"kernel`_ for KVM." +msgstr "" + +#: ../../reference/image-types.rst:76 +msgid "kvm-legacy.img" +msgstr "" + +#: ../../reference/image-types.rst:77 +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:79 +msgid "pxe.tar" +msgstr "" + +#: ../../reference/image-types.rst:80 +msgid "Image suitable for use with PXE server." +msgstr "" + +#: ../../reference/image-types.rst:82 +msgid "vmware.vmdk" +msgstr "" + +#: ../../reference/image-types.rst:83 +msgid "" +"Virtual Machine Disk for VMware\\* platforms inclduing Player, " +"Workstation, and ESXi." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/reference/reference.po b/locale/zh_CN/LC_MESSAGES/reference/reference.po new file mode 100644 index 00000000..f2de2b3a --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/reference/reference.po @@ -0,0 +1,34 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/reference.rst:4 +msgid "Reference" +msgstr "" + +#: ../../reference/reference.rst:6 +msgid "" +"This section provides additional information on the |CL| project and " +"features." +msgstr "" + +#: ../../reference/reference.rst:24 +msgid "Clear Linux concepts" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/reference/system-requirements.po b/locale/zh_CN/LC_MESSAGES/reference/system-requirements.po new file mode 100644 index 00000000..9df1c30e --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/reference/system-requirements.po @@ -0,0 +1,124 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../reference/system-requirements.rst:4 +msgid "Recommended minimum system requirements" +msgstr "" + +#: ../../reference/system-requirements.rst:6 +msgid "" +"|CL-ATTR| can run on very minimal hardware. For example, it can run on a " +"system with a single core CPU, 128MB of memory, and 600MB of disk space." +msgstr "" + +#: ../../reference/system-requirements.rst:9 +msgid "" +"Different use cases and applications will require different " +"configurations. For general |CL| use, in addition to a supported " +"processor, the recommended minimum requirements include:" +msgstr "" + +#: ../../reference/system-requirements.rst:13 +msgid "Processors:" +msgstr "" + +#: ../../reference/system-requirements.rst:15 +msgid "" +"|CL-ATTR| can run on any Intel® 64bit processors which support UEFI\\* " +"and SSE\\* v4.1 streaming SIMD\\* instructions." +msgstr "" + +#: ../../reference/system-requirements.rst:18 +msgid "The following processor families have been verified to run |CL|:" +msgstr "" + +#: ../../reference/system-requirements.rst:20 +msgid "2nd Generation, or later, Intel® Core™ processor family." +msgstr "" + +#: ../../reference/system-requirements.rst:21 +msgid "Intel® Xeon® Processor E3" +msgstr "" + +#: ../../reference/system-requirements.rst:22 +msgid "Intel® Xeon® Processor E5" +msgstr "" + +#: ../../reference/system-requirements.rst:23 +msgid "Intel® Xeon® Processor E7" +msgstr "" + +#: ../../reference/system-requirements.rst:24 +msgid "" +"Intel® Atom™ processor C2000 product family for servers -- Q3 2013 " +"version or later." +msgstr "" + +#: ../../reference/system-requirements.rst:26 +msgid "Intel® Atom™ processor E3800 series -- Q4 2013 version or later." +msgstr "" + +#: ../../reference/system-requirements.rst:28 +msgid "" +"To help determine if a processor is supported, you can run a " +":ref:`compatibility check` or go to " +"http://ark.intel.com and check for these features:" +msgstr "" + +#: ../../reference/system-requirements.rst:32 +msgid "Instruction Set = 64-bit" +msgstr "" + +#: ../../reference/system-requirements.rst:33 +msgid "Instruction Set Extensions = SSSE3" +msgstr "" + +#: ../../reference/system-requirements.rst:34 +msgid "Instruction Set Extensions = SSE 4.1" +msgstr "" + +#: ../../reference/system-requirements.rst:35 +msgid "Instruction Set Extensions = SSE 4.2" +msgstr "" + +#: ../../reference/system-requirements.rst:36 +msgid "Instruction Set Extensions = AES" +msgstr "" + +#: ../../reference/system-requirements.rst:37 +msgid "Instruction Set Extensions = PCLMUL" +msgstr "" + +#: ../../reference/system-requirements.rst:39 +msgid "Memory: 4GB RAM" +msgstr "" + +#: ../../reference/system-requirements.rst:41 +msgid "Hard Disk: 20GB HDD" +msgstr "" + +#: ../../reference/system-requirements.rst:43 +msgid "Network: Active Internet connection" +msgstr "" + +#: ../../reference/system-requirements.rst:45 +msgid "Graphics: Intel HD Graphics (required if running a GUI desktop)" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tooling/autoproxy.po b/locale/zh_CN/LC_MESSAGES/tooling/autoproxy.po new file mode 100644 index 00000000..298045a3 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tooling/autoproxy.po @@ -0,0 +1,162 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tooling/autoproxy.rst:4 +msgid "Autoproxy" +msgstr "" + +#: ../../tooling/autoproxy.rst:6 +msgid "" +"Autoproxy is provided to enable |CL-ATTR| to work smoothly behind a " +"corporate proxy." +msgstr "" + +#: ../../tooling/autoproxy.rst:14 +msgid "Description" +msgstr "" + +#: ../../tooling/autoproxy.rst:16 +msgid "" +"Autoproxy tries to detect a Proxy Auto-Config (PAC) script and use it to " +"automatically resolve the proxy needed for a given connection. With " +"Autoproxy, you can use |CL| inside any proxy environment without having " +"to manually configure the proxies." +msgstr "" + +#: ../../tooling/autoproxy.rst:21 +msgid "" +"Corporate and private networks can be very complex, needing to restrict " +"and control network connections for security reasons. The typical side " +"effects are limited or blocked connectivity, and require manual " +"configuration of proxies to perform the most mundane tasks, such as " +"cloning a repo or checking for updates. With |CL|, all of the work is " +"done behind the scenes to effortlessly use your network and have " +"connections “just work”." +msgstr "" + +#: ../../tooling/autoproxy.rst:28 +msgid "" +"This feature removes severe complications with network connectivity due " +"to proxy issues. You can automate tasks, such as unit testing, without " +"worrying about the proxy not being set, and you can remove unset proxies " +"from the equation when dealing with network unavailability across " +"systems." +msgstr "" + +#: ../../tooling/autoproxy.rst:34 +msgid "How it works" +msgstr "" + +#: ../../tooling/autoproxy.rst:36 +msgid "" +"We designed Autoproxy around tools provided by most Linux\\* " +"distributions with a few minor additions and modifications. We leveraged " +"the DHCP and network information obtained from systemd and created a PAC-" +"discovery daemon. The daemon uses the information to resolve a URL for a " +"PAC file. The daemon then passes the URL into PACrunner\\*. PACrunner " +"downloads the PAC file and uses the newly implemented Duktape\\* engine " +"to parse it." +msgstr "" + +#: ../../tooling/autoproxy.rst:47 +msgid "Figure 1: Autoproxy Flow" +msgstr "" + +#: ../../tooling/autoproxy.rst:49 +msgid "" +"From that point on, any cURL\\* or network requests query PACrunner for " +"the correct proxy to use. We modified the cURL library to communicate " +"with PACrunner over DBus. However, cURL will ignore PACrunner and run " +"normally if no PAC file is loaded or if you manually set any proxies. " +"Thus, your environment settings are respected and no time is wasted " +"trying to resolve a proxy. All these steps happen in the background with " +"no user interaction." +msgstr "" + +#: ../../tooling/autoproxy.rst:57 +msgid "Troubleshooting" +msgstr "" + +#: ../../tooling/autoproxy.rst:59 +msgid "" +"Autoproxy allows |CL| to operate seamlessly behind a proxy because " +":ref:`swupd ` and other |CL| tools are implemented on top of" +" libcurl. Tools that do not use libcurl, like git, must be configured " +"independently." +msgstr "" + +#: ../../tooling/autoproxy.rst:64 +msgid "" +"If you are familiar with PAC files and WPAD, you can use " +":command:`pacdiscovery` and :command:`FindProxyForURL` to troubleshoot " +"problems with autproxy." +msgstr "" + +#: ../../tooling/autoproxy.rst:70 +msgid "Learn more about WPAD, PAC files, and PAC functions at `findproxyforurl`_." +msgstr "" + +#: ../../tooling/autoproxy.rst:74 +msgid "Run :command:`pacdiscovery` with no arguments to indicate" +msgstr "" + +#: ../../tooling/autoproxy.rst:76 +msgid "if there is a problem resolving the :command:`WPAD` host name resolution:" +msgstr "" + +#: ../../tooling/autoproxy.rst:87 +msgid "or if the :command:`pacrunner` service is disabled (masked)." +msgstr "" + +#: ../../tooling/autoproxy.rst:98 +msgid "Unmask the :command:`pacrunner` service by running:" +msgstr "" + +#: ../../tooling/autoproxy.rst:104 +msgid "" +":command:`FindProxyForURL` with :command:`busctl` can also indicate if " +"the :command:`pacrunner.service` is masked." +msgstr "" + +#: ../../tooling/autoproxy.rst:117 +msgid "" +":command:`FindProxyForURL` returns the URL and port of the proxy server " +"when an external URL and host are provided as arguments." +msgstr "" + +#: ../../tooling/autoproxy.rst:129 +msgid "" +"If a proxy server is not avialable, or if :command:`pacrunner` is running" +" without a PAC file, :command:`FindProxyForURL` will return \"DIRECT\"." +msgstr "" + +#: ../../tooling/autoproxy.rst:141 +msgid "" +"Once :command:`pacdiscovery` is able to look up :command:`WPAD`, restart " +"the :command:`pacrunner` service:" +msgstr "" + +#: ../../tooling/autoproxy.rst:151 +msgid "" +"A \"domain\" or \"search\" entry in :file:`/etc/resolv.conf` is required " +"for short name lookups to resolve. The :file:`resolv.conf` man page has " +"additional details." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tooling/autospec.po b/locale/zh_CN/LC_MESSAGES/tooling/autospec.po new file mode 100644 index 00000000..32e603ea --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tooling/autospec.po @@ -0,0 +1,576 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tooling/autospec.rst:4 +msgid "autospec" +msgstr "" + +#: ../../tooling/autospec.rst:6 +msgid "" +"**autospec** is a tool used to assist with the automated creation and " +"maintenance of RPM packaging in |CL-ATTR|. Where a standard :abbr:`RPM " +"(RPM Package Manager)` build process using :command:`rpmbuild` requires a" +" tarball and :file:`.spec` file to start, autospec requires only a " +"tarball and package name to start." +msgstr "" + +#: ../../tooling/autospec.rst:16 +msgid "Description" +msgstr "" + +#: ../../tooling/autospec.rst:18 +msgid "" +"The autospec tool attempts to infer the requirements of the :file:`.spec`" +" file by analyzing the source code and :file:`Makefile` information. It " +"continuously runs updated builds based on new information discovered from" +" build failures until it has a complete and valid :file:`.spec` file. If " +"needed, you can influence the behavior of autospec and customize the " +"build by providing optional `control files`_ to the autospec tool." +msgstr "" + +#: ../../tooling/autospec.rst:25 +msgid "" +"autospec uses **mock** as a sandbox to run the builds. Visit the `mock " +"wiki`_ for additional information on using mock." +msgstr "" + +#: ../../tooling/autospec.rst:28 +msgid "" +"For a general understanding of how an RPM works, visit the `rpm website`_" +" or the `RPM Packaging Guide`_ ." +msgstr "" + +#: ../../tooling/autospec.rst:32 +msgid "How it works" +msgstr "" + +#: ../../tooling/autospec.rst:34 +msgid "Learn the autospec tool set up and process." +msgstr "" + +#: ../../tooling/autospec.rst:41 +msgid "Prerequisites" +msgstr "" + +#: ../../tooling/autospec.rst:43 +msgid "" +"The setup for building source in |CL| must be completed before using the " +"autospec tool." +msgstr "" + +#: ../../tooling/autospec.rst:46 +msgid "" +"Refer to `Setup environment to build source`_ for instructions on " +"completing the setup." +msgstr "" + +#: ../../tooling/autospec.rst:50 +msgid "Create an RPM" +msgstr "" + +#: ../../tooling/autospec.rst:52 +msgid "The basic autospec process is described in the following steps:" +msgstr "" + +#: ../../tooling/autospec.rst:54 +msgid "" +"The :command:`make autospec` command generates a :file:`.spec` file based" +" on the analysis of code and existing control files." +msgstr "" + +#: ../../tooling/autospec.rst:57 +msgid "" +"Any control files should be located in the same directory as the " +"resulting :file:`.spec` file." +msgstr "" + +#: ../../tooling/autospec.rst:60 +msgid "View the `autospec README`_ for more information on `control files`_." +msgstr "" + +#: ../../tooling/autospec.rst:62 +msgid "autospec creates a build root with mock config." +msgstr "" + +#: ../../tooling/autospec.rst:64 +msgid "autospec attempts to build an RPM from the generated :file:`.spec`." +msgstr "" + +#: ../../tooling/autospec.rst:66 +msgid "autospec detects any missed declarations in the :file:`.spec`." +msgstr "" + +#: ../../tooling/autospec.rst:68 +msgid "" +"If build errors occur, autospec scans the build log to try to detect the " +"root cause." +msgstr "" + +#: ../../tooling/autospec.rst:71 +msgid "" +"If autospec detects the root cause and knows how to continue, it restarts" +" the build automatically at step 1 with updated build instructions." +msgstr "" + +#: ../../tooling/autospec.rst:74 +msgid "" +"Otherwise, autospec stops the build for user inspection to resolve the " +"errors. Respond to the build process output by fixing source code issues " +"and/or editing control files to resolve issues, which may include " +"dependencies or exclusions. See `autospec README`_ for more information " +"on control files." +msgstr "" + +#: ../../tooling/autospec.rst:80 +msgid "The user resumes the process at step 1 after errors are resolved." +msgstr "" + +#: ../../tooling/autospec.rst:82 +msgid "" +"If a binary dependency doesn't exist in |CL|, you must build it before " +"running autospec again." +msgstr "" + +#: ../../tooling/autospec.rst:85 +msgid "" +"Following these steps, autospec continues to rebuild the package, based " +"on new information discovered from build failures, until it has a valid " +":file:`.spec`. If no build errors occur, RPM packages are successfully " +"built." +msgstr "" + +#: ../../tooling/autospec.rst:90 +msgid "Examples" +msgstr "" + +#: ../../tooling/autospec.rst:92 +msgid "Complete `Setup environment to build source`_ before using these examples." +msgstr "" + +#: ../../tooling/autospec.rst:99 +msgid "Example 1: Build RPM with an existing spec file" +msgstr "" + +#: ../../tooling/autospec.rst:101 +msgid "" +"This example shows how to build a RPM from a pre-packaged upstream " +"package with an existing spec file. The example uses the ``dmidecode`` " +"package." +msgstr "" + +#: ../../tooling/autospec.rst:104 ../../tooling/autospec.rst:160 +msgid "Navigate to the autospec workspace and clone the ``dmidecode`` package:" +msgstr "" + +#: ../../tooling/autospec.rst:113 +msgid "You can clone all package repos at once using the following command:" +msgstr "" + +#: ../../tooling/autospec.rst:119 ../../tooling/autospec.rst:216 +msgid "The optional NUM is the number of threads to use." +msgstr "" + +#: ../../tooling/autospec.rst:121 +msgid "" +"For a list of available packages, view the " +":file:`~/clearlinux/projects/common/packages` file." +msgstr "" + +#: ../../tooling/autospec.rst:124 +msgid "Navigate to the local copy of the ``dmidecode`` package and build it:" +msgstr "" + +#: ../../tooling/autospec.rst:131 +msgid "" +"The resulting RPMs are in :file:`./rpms`. Build logs and additional RPMs " +"are in :file:`./results`." +msgstr "" + +#: ../../tooling/autospec.rst:135 +msgid "Example 2: Build a new RPM" +msgstr "" + +#: ../../tooling/autospec.rst:137 +msgid "" +"This example shows how to build a new RPM with no spec file. The example " +"will create a simple helloclear RPM." +msgstr "" + +#: ../../tooling/autospec.rst:140 +msgid "" +"Navigate to the autospec workspace and build the helloclear RPM. The " +":file:`Makefile` provides a :command:`make autospecnew` that can " +"automatically generate an RPM package using the autospec tool. You must " +"pass the URL to the source tarball and the NAME of the RPM you wish to " +"create:" +msgstr "" + +#: ../../tooling/autospec.rst:150 +msgid "" +"The resulting RPMs are in :file:`./packages/helloclear/rpms`. Build logs " +"and additional RPMs are in :file:`./packages/helloclear/results`." +msgstr "" + +#: ../../tooling/autospec.rst:154 +msgid "Example 3: Generate a new spec file with a pre-defined package" +msgstr "" + +#: ../../tooling/autospec.rst:156 +msgid "" +"This example shows how to modify an existing package to create a custom " +"RPM. In this example you will make a simple change to the ``dmidecode`` " +"package and rebuild the package." +msgstr "" + +#: ../../tooling/autospec.rst:167 +msgid "Navigate into the *dmidecode* directory:" +msgstr "" + +#: ../../tooling/autospec.rst:173 +msgid "Open the :file:`excludes` file with an editor and add these lines:" +msgstr "" + +#: ../../tooling/autospec.rst:186 +msgid "" +"These files aren't needed by dmidecode, so we can remove them without any" +" issues." +msgstr "" + +#: ../../tooling/autospec.rst:189 +msgid "" +"In the :file:`dmidecode` directory, build the modified ``dmidecode`` " +"package:" +msgstr "" + +#: ../../tooling/autospec.rst:195 +msgid "The resulting RPMs are in :file:`./rpms`. Logs are in :file:`./results`." +msgstr "" + +#: ../../tooling/autospec.rst:198 +msgid "Example 4: Provide control files to autospec" +msgstr "" + +#: ../../tooling/autospec.rst:200 +msgid "" +"This example shows how to modify control files to correct build failures " +"that autospec is unable to resolve. In this example, you will add a " +"missing license and dependencies so autospec can complete a successful " +"build." +msgstr "" + +#: ../../tooling/autospec.rst:204 +msgid "Navigate to the autospec workspace:" +msgstr "" + +#: ../../tooling/autospec.rst:210 +msgid "If you have not already, clone all upstream package repos:" +msgstr "" + +#: ../../tooling/autospec.rst:220 +msgid "" +"In a later step of this example, we will search the cloned package repos " +"for a missing dependency." +msgstr "" + +#: ../../tooling/autospec.rst:223 +msgid "Build the opae-sdk RPM:" +msgstr "" + +#: ../../tooling/autospec.rst:229 +msgid "This results in an error for a missing license file:" +msgstr "" + +#: ../../tooling/autospec.rst:235 +msgid "Navigate to the package with build failures:" +msgstr "" + +#: ../../tooling/autospec.rst:241 +msgid "" +"Add one or more valid license identifiers from the `SPDX License List " +"`_. In the example below, two different " +"licenses are appropriate based on the opae-sdk project licensing:" +msgstr "" + +#: ../../tooling/autospec.rst:250 +msgid "Run autospec again:" +msgstr "" + +#: ../../tooling/autospec.rst:256 +msgid "This results in a generic error:" +msgstr "" + +#: ../../tooling/autospec.rst:262 +msgid "Open the build log to view the error details:" +msgstr "" + +#: ../../tooling/autospec.rst:268 +msgid "" +"The build log contains details for the specific failures. In this " +"instance, there are missing dependencies:" +msgstr "" + +#: ../../tooling/autospec.rst:281 +msgid "" +"Search the spec files of upstream |CL| packages to see if the json-c " +"library is available. In this case, it does exist and we'll add the " +"json-c 'dev' package into the buildreq_add:" +msgstr "" + +#: ../../tooling/autospec.rst:292 +msgid "" +"This search step works only if the user cloned all of the upstream " +"package repos. In this example, upstream package repos were cloned in a " +"previous step." +msgstr "" + +#: ../../tooling/autospec.rst:296 +msgid "" +"Search the spec files of upstream |CL| packages to see if the libuuid " +"library is available. In this case, it exists in the util-linux package, " +"so we'll add util-linux-dev package into the buildreq_add:" +msgstr "" + +#: ../../tooling/autospec.rst:305 +msgid "" +"Run autospec again and find the successfully-generated RPMs in the " +":file:`rpms` directory:" +msgstr "" + +#: ../../tooling/autospec.rst:314 +msgid "" +"If you need a dependency that does not exist in the |CL| repo, you must " +"first build it manually (see `Example 2: Build a new RPM`_), then add the" +" repo so that autospec knows the package exists. For example:" +msgstr "" + +#: ../../tooling/autospec.rst:324 +msgid "" +"You only need to add the dependency to the :file:`buildreq_add` control " +"file if autospec is not able to automatically find the correct dependency" +" on its own." +msgstr "" + +#: ../../tooling/autospec.rst:329 +msgid "Test packaged software" +msgstr "" + +#: ../../tooling/autospec.rst:331 +msgid "" +"After software has been packaged with autospec, the resulting RPMs can be" +" tested for functionality before being integrated and deployed into a " +"|CL| image with the :ref:`Mixer tool `." +msgstr "" + +#: ../../tooling/autospec.rst:335 +msgid "" +"The |CL| development tooling offers two ways to quickly test autospec " +"generated RPMs." +msgstr "" + +#: ../../tooling/autospec.rst:339 +msgid "" +"The methods outlined below should only be used for temporary testing on " +"development systems." +msgstr "" + +#: ../../tooling/autospec.rst:344 +msgid "Test in a |CL| virtual machine" +msgstr "" + +#: ../../tooling/autospec.rst:346 +msgid "" +"The |CL| development tooling includes a method to install RPMs into a " +"|CL| virtual machine running on the KVM hypervisor. Using a :abbr:`VM " +"(Virtual Machine)` allows testing in a completely isolated environment." +msgstr "" + +#: ../../tooling/autospec.rst:350 +msgid "To test an autospec-created package inside a VM:" +msgstr "" + +#: ../../tooling/autospec.rst:352 +msgid "" +"Download the |CL| KVM image into the :file:`~/clearlinux` directory as " +":file:`clear.img`. The location and name :file:`clear.img.xz` is " +"important for the tooling to work:" +msgstr "" + +#: ../../tooling/autospec.rst:361 +msgid "Extract the downloaded |CL| KVM image:" +msgstr "" + +#: ../../tooling/autospec.rst:367 +msgid "" +"Copy the QEMU start script and virtual firmware needed for KVM into the " +":file:`~/clearlinux` directory:" +msgstr "" + +#: ../../tooling/autospec.rst:375 +msgid "" +"Run :command:`make install` from the package's autospec directory. The " +":command:`make install` command mounts the downloaded |CL| KVM image and " +"installs the autospec-created RPM into it:" +msgstr "" + +#: ../../tooling/autospec.rst:384 +msgid "" +"The code that makes this possible can be viewed by searching for the " +"*install:* target in the `Makefile.common file on GitHub`_." +msgstr "" + +#: ../../tooling/autospec.rst:387 +msgid "Return to the :file:`~/clearlinux` directory and start the |CL| VM:" +msgstr "" + +#: ../../tooling/autospec.rst:394 +msgid "" +"A new |CL| VM will launch in the console. Log into the VM as *root* and " +"set a new pasword for the VM." +msgstr "" + +#: ../../tooling/autospec.rst:397 +msgid "" +"Check that the software is installed in the |CL| VM as expected and " +"perform any relevant tests." +msgstr "" + +#: ../../tooling/autospec.rst:400 +msgid "" +"After testing has been completed, the |CL| VM can be powered off and " +"deleted:" +msgstr "" + +#: ../../tooling/autospec.rst:410 +msgid "Test directly on a development machine" +msgstr "" + +#: ../../tooling/autospec.rst:412 +msgid "" +"The |CL| development tooling also includes a method to extract autospec-" +"created RPMs locally onto a |CL| development system for testing. " +"Extracting an RPM directly onto a system offers quicker testing; however" +" conflicts may occur and responsibility to remove the software after " +"testing is up to the developer." +msgstr "" + +#: ../../tooling/autospec.rst:418 +msgid "" +"To test an autospec created package directly on the |CL| development " +"system:" +msgstr "" + +#: ../../tooling/autospec.rst:420 +msgid "" +"Run :command:`make install-local` from the package's autospec directory. " +"The :command:`make install-local` command extracts the RPM directly onto " +"the filesystem of the running |CL| system:" +msgstr "" + +#: ../../tooling/autospec.rst:429 +msgid "" +"The code that makes this possible can be viewed by searching for the " +"*install-local:* target in the `Makefile.common file on GitHub`_." +msgstr "" + +#: ../../tooling/autospec.rst:432 +msgid "" +"Check that the software is installed as expected and perform any relevant" +" tests." +msgstr "" + +#: ../../tooling/autospec.rst:435 +msgid "" +"After testing has been completed, the software and any related files must" +" be identified and deleted. The :command:`swupd repair --picky` command " +"can help restore the state of the :file:`/usr` directory (see :ref:`swupd" +" `) however any other files must be cleaned up manually." +msgstr "" + +#: ../../tooling/autospec.rst:443 +msgid "References" +msgstr "" + +#: ../../tooling/autospec.rst:445 +msgid "" +"Reference the `autospec README`_ for details regarding `autospec` " +"commands and options." +msgstr "" + +#: ../../tooling/autospec.rst:448 +msgid "Setup environment to build source" +msgstr "" + +#: ../../tooling/autospec.rst:452 +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:456 +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:461 +msgid "Follow these steps to setup the workspace and tooling for building source:" +msgstr "" + +#: ../../tooling/autospec.rst:463 +msgid "Install the :command:`os-clr-on-clr` bundle:" +msgstr "" + +#: ../../tooling/autospec.rst:469 +msgid "Download the :file:`user-setup.sh` script:" +msgstr "" + +#: ../../tooling/autospec.rst:475 +msgid "Make :file:`user-setup.sh` executable:" +msgstr "" + +#: ../../tooling/autospec.rst:481 +msgid "Run the script as an unprivileged user:" +msgstr "" + +#: ../../tooling/autospec.rst:487 +msgid "" +"After the script completes, log out and log in again to complete the " +"setup process." +msgstr "" + +#: ../../tooling/autospec.rst:490 +msgid "Set your Git user email and username for the repos on your system:" +msgstr "" + +#: ../../tooling/autospec.rst:497 +msgid "This global setting is used by |CL| tools that make use of Git." +msgstr "" + +#: ../../tooling/autospec.rst:502 +msgid "Related topics" +msgstr "" + +#: ../../tooling/autospec.rst:504 +msgid ":ref:`Mixer tool `" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tooling/compatible-kernels.po b/locale/zh_CN/LC_MESSAGES/tooling/compatible-kernels.po new file mode 100644 index 00000000..5fc6f59b --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tooling/compatible-kernels.po @@ -0,0 +1,135 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tooling/compatible-kernels.rst:4 +msgid "Kernels" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:6 +msgid "" +"The |CL-ATTR| provides the following Linux kernels with a respective " +"bundle. This document describes the specific use cases these `bundles`_ " +"serve and provides links to their source code." +msgstr "" + +#: ../../tooling/compatible-kernels.rst:11 +msgid "Bare metal only" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:17 +msgid "Kernel native" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:14 +msgid "" +"The *kernel-native* bundle focuses on the bare metal platforms. It is " +"optimized for fast booting and performs best on the Intel® architectures " +"described on the :ref:`supported hardware list`. The" +" optimization patches are found in our `Linux`_ GitHub\\* repo." +msgstr "" + +#: ../../tooling/compatible-kernels.rst:24 +msgid "Kernel Container" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:20 +msgid "" +"The *kernel-container* bundle contains the kernel used by the Intel® " +"Clear Containers project. This kernel is optimized for fast booting and " +"performs best on |CC| running on the Intel® architectures described on " +"the :ref:`supported hardware list`. The optimization" +" patches are found in our `Linux-Container`_ GitHub repo." +msgstr "" + +#: ../../tooling/compatible-kernels.rst:29 +msgid "Also compatible with VMs" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:39 +msgid "Kernel LTS" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:32 +msgid "" +"The *kernel-lts* bundle focuses on the bare metal platforms but uses the " +"latest :abbr:`LTS (Long Term Support)` Linux kernel. It is optimized for " +"fast booting and performs best on the Intel® architectures described on " +"the :ref:`supported hardware list`. Additionally, " +"this kernel includes the VirtualBox\\* kernel modules, see our " +":ref:`instructions on using Virtualbox` for more" +" information. The optimization patches are found in our `Linux-LTS`_ " +"GitHub repo." +msgstr "" + +#: ../../tooling/compatible-kernels.rst:42 +msgid "VM only" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:54 +msgid "Kernel KVM" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:45 +msgid "" +"The *kernel-kvm* bundle focuses on the Linux :abbr:`KVM (Kernel-based " +"Virtual Machine)`. It is optimized for fast booting and performs best on " +"Virtual Machines running on the Intel® architectures described on the " +":ref:`supported hardware list`. Use this kernel when" +" running |CL| as the guest OS on top of *qemu/kvm*. Use this kernel with " +"**cloud orchestrators** using *qemu/kvm* internally as their " +"**hypervisor** . This kernel can be used as a standalone |CL| VM, see our" +" :ref:`instructions on using KVM` for more information. The " +"optimization patches are found in our `Linux-KVM`_ GitHub repo." +msgstr "" + +#: ../../tooling/compatible-kernels.rst:65 +msgid "Kernel Hyper-V\\*" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:57 +msgid "" +"The *kernel-hyperv* bundle focuses on running Linux on Microsoft\\* " +"Hyper-V. It is optimized for fast booting and performs best on Virtual " +"Machines running on the Intel® architectures described on the " +":ref:`supported hardware list`. Use this kernel when" +" running |CL| as the guest OS of **Cloud Instances** in projects such as " +"Microsoft `Azure`_\\*. This kernel can be used in a standalone |CL| VM, " +"see our :ref:`instructions on using Hyper-V` for more " +"information. The optimization patches are found in our `Linux-HyperV`_ " +"GitHub repo." +msgstr "" + +#: ../../tooling/compatible-kernels.rst:78 +msgid "Kernel Hyper-V LTS" +msgstr "" + +#: ../../tooling/compatible-kernels.rst:68 +msgid "" +"The *kernel-hyperv-lts* bundle focuses on running Linux on Microsoft " +"Hyper-V but uses the latest :abbr:`LTS (Long Term Support)` Linux kernel." +" It is optimized for fast booting and performs best on Virtual Machines " +"running on the Intel® architectures described on the :ref:`supported " +"hardware list`. Use this kernel when running |CL| as" +" the guest OS of **Cloud Instances** in projects such as Microsoft " +"`Azure`_. This kernel can be used in a standalone |CL| VM, see our " +":ref:`instructions on using Hyper-V` for more information. The " +"optimization patches are found in our `Linux-HyperV-LTS`_ GitHub repo." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tooling/debug.po b/locale/zh_CN/LC_MESSAGES/tooling/debug.po new file mode 100644 index 00000000..3d55a821 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tooling/debug.po @@ -0,0 +1,131 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tooling/debug.rst:4 +msgid "Debug System" +msgstr "" + +#: ../../tooling/debug.rst:6 +msgid "" +"|CL-ATTR| introduces a novel approach to system software debugging using " +"*clr-debug-info*. On the client side, the |CL| debug system obtains any " +"necessary debug information on-the-fly over a network during a debugging " +"session. On the server side, the system curates and compresses debug " +"information into small pieces for efficient downloading." +msgstr "" + +#: ../../tooling/debug.rst:12 +msgid "" +"For developers, this avoids the interruption during debugging that " +"usually happens when debug information is missing. This can be especially" +" useful on systems where storage is limited." +msgstr "" + +#: ../../tooling/debug.rst:22 +msgid "Background" +msgstr "" + +#: ../../tooling/debug.rst:24 +msgid "" +"Software that is compiled and packaged for general usage in an operating " +"system typically only contains components that are used to execute the " +"program, such as binaries and libraries. Extra developer data, such as " +"the actual source code and symbol information, are separated and excluded" +" for efficiency." +msgstr "" + +#: ../../tooling/debug.rst:30 +msgid "" +"The debug information helps relate binary code to human readable source " +"code lines and variables. Most of the time, this auxiliary information is" +" not needed; however without it, debugging a program results in limited " +"visibility." +msgstr "" + +#: ../../tooling/debug.rst:37 +msgid "Usage" +msgstr "" + +#: ../../tooling/debug.rst:39 +msgid "" +"The clr-debug-info system is integrated into |CL| and seamlessly engages " +"once installed." +msgstr "" + +#: ../../tooling/debug.rst:42 +msgid "Install the *dev-utils* bundle." +msgstr "" + +#: ../../tooling/debug.rst:50 +msgid "" +"The *telemetrics* and *performance-tools* bundles also include clr-debug-" +"info." +msgstr "" + +#: ../../tooling/debug.rst:54 +msgid "" +"Start a debugging session against a program using a debugger, such as " +"GDB. For example, to debug *gnome-control-center* execute the following " +"command:" +msgstr "" + +#: ../../tooling/debug.rst:62 +msgid "" +"As you step through the program and debug information is needed, the " +"clr_debug_daemon obtains it in the background." +msgstr "" + +#: ../../tooling/debug.rst:67 +msgid "Implementation" +msgstr "" + +#: ../../tooling/debug.rst:69 +msgid "" +"The implementation of the |CL| debug system is open source and available " +"on GitHub at: https://github.com/clearlinux/clr-debug-info/" +msgstr "" + +#: ../../tooling/debug.rst:76 +msgid "Figure 1: The communication flow of the |CL| debug system" +msgstr "" + +#: ../../tooling/debug.rst:78 +msgid "" +"The |CL| debug system implements a :abbr:`FUSE (filesystem in userspace)`" +" filesystem mounted at :file:`/usr/lib/debug` and :file:`/usr/src/debug`." +" The FUSE filesystem starts automatically. You can verify its status by " +"executing :command:`systemctl status clr_debug_fuse.service`." +msgstr "" + +#: ../../tooling/debug.rst:83 +msgid "" +"The *clr_debug_daemon* is responsible for fetching the appropriate " +"package debug content from the server and making it available for any " +"debugging programs that need it. It is socket activated whenever a " +"request to the local FUSE filesystem occurs. You can verify its status " +"with :command:`systemctl status clr_debug_daemon.service`." +msgstr "" + +#: ../../tooling/debug.rst:90 +msgid "" +"|CL| hosts debuginfo content packaged for consumption by |CL| debug " +"clients at https://download.clearlinux.org/debuginfo/" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tooling/ister.po b/locale/zh_CN/LC_MESSAGES/tooling/ister.po new file mode 100644 index 00000000..9eb9249f --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tooling/ister.po @@ -0,0 +1,166 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tooling/ister.rst:4 +msgid "ister.py image builder" +msgstr "" + +#: ../../tooling/ister.rst:6 +msgid "" +"The `ister.py tool`_ is a template-based installer used by |CL-ATTR| to " +"produce images for each release. The same ister tool is available for use" +" in |CL| to create custom images based on an upstream image." +msgstr "" + +#: ../../tooling/ister.rst:15 +msgid "Description" +msgstr "" + +#: ../../tooling/ister.rst:17 +msgid "" +"|CL| is a rolling release and produces an average of 10 releases per week" +" using the ister tool. With each release we produce multiple :ref:`image " +"types for different environments ` and use cases such as " +"installers, Hyper-V, KVM, or VMWare." +msgstr "" + +#: ../../tooling/ister.rst:22 +msgid "" +"Each image has a JSON configuration file that is used by ister to " +"generate the image. These JSON configuration files describe the image " +"type, partitions, version, and bundles that will be preinstalled by " +"default with the image. For each image type we produce, the corresponding" +" JSON configuration file for the image also is published." +msgstr "" + +#: ../../tooling/ister.rst:28 +msgid "" +"The :ref:`mixer` tool also uses ister to build images for your " +"custom mix. Like upstream images, a JSON configuration file is defined " +"for the image, which ister uses to generate the image. Refer to the " +":ref:`mixer` guide for instructions on using ister to build an " +"image for a custom mix." +msgstr "" + +#: ../../tooling/ister.rst:34 +msgid "Examples" +msgstr "" + +#: ../../tooling/ister.rst:37 +msgid "Recreate an upstream image" +msgstr "" + +#: ../../tooling/ister.rst:39 +msgid "" +"The published configuration files for upstream images may be used to " +"recreate an image. Here are some examples:" +msgstr "" + +#: ../../tooling/ister.rst:42 +msgid "" +"Use an older version of |CL| and the image is no longer available (only " +"after March 2017)." +msgstr "" + +#: ../../tooling/ister.rst:44 +msgid "Customize the partitions of an image." +msgstr "" + +#: ../../tooling/ister.rst:45 +msgid "Customize the bundles preinstalled in an image." +msgstr "" + +#: ../../tooling/ister.rst:46 +msgid "Run your own post installation script." +msgstr "" + +#: ../../tooling/ister.rst:49 +msgid "" +"Follow these steps to recreate an upstream image based on the image's " +"JSON configuration file:" +msgstr "" + +#: ../../tooling/ister.rst:52 +msgid "" +"Install the :command:`os-installer` bundle. Refer to `Install a bundle`_ " +"for more details." +msgstr "" + +#: ../../tooling/ister.rst:55 +msgid "Download the `ister.py tool`_ and grant it sudo privileges." +msgstr "" + +#: ../../tooling/ister.rst:57 +msgid "Download the JSON configuration file for the desired image:" +msgstr "" + +#: ../../tooling/ister.rst:59 +msgid "`Configuration files for the current release`_" +msgstr "" + +#: ../../tooling/ister.rst:60 +msgid "`Previous releases`_ (only after March 2017)" +msgstr "" + +#: ../../tooling/ister.rst:62 +msgid "" +"For a previous release, navigate to `Previous releases`_, select the " +"version you want, and find the JSON configuration file under " +":file:`/clear/config/image`. For example: " +"``https://cdn.download.clearlinux.org/releases/15700/clear/config/image/``" +msgstr "" + +#: ../../tooling/ister.rst:67 +msgid "Download the “PostNonChroot” script (if applicable)." +msgstr "" + +#: ../../tooling/ister.rst:69 +msgid "" +"The JSON configuration file for the image may have an accompanying " +"“PostNonChroot” script that is executed at the end of the image creation " +"process. If it does, download the script and make it executable." +msgstr "" + +#: ../../tooling/ister.rst:73 +msgid "Edit the JSON configuration file as needed." +msgstr "" + +#: ../../tooling/ister.rst:75 +msgid "" +"If your configuration file has an accompanying \"PostNonChroot\" script, " +"change the default path of the script to match your path." +msgstr "" + +#: ../../tooling/ister.rst:78 +msgid "Generate the new image with the following command:" +msgstr "" + +#: ../../tooling/ister.rst:85 +msgid "Related topics" +msgstr "" + +#: ../../tooling/ister.rst:87 +msgid ":ref:`mixer`" +msgstr "" + +#: ../../tooling/ister.rst:88 +msgid ":ref:`bulk-provision`" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tooling/mixer.po b/locale/zh_CN/LC_MESSAGES/tooling/mixer.po new file mode 100644 index 00000000..94079929 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tooling/mixer.po @@ -0,0 +1,1074 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tooling/mixer.rst:4 +msgid "mixer" +msgstr "" + +#: ../../tooling/mixer.rst:6 +msgid "" +"**mixer** is the tool used by the |CL-ATTR| team to generate official " +"update content and releases. The update content generated by mixer is " +"then consumed by swupd on a downstream client. The same mixer tool is " +"available as part of |CL| to create your own customized update content " +"and releases." +msgstr "" + +#: ../../tooling/mixer.rst:16 +msgid "Description" +msgstr "" + +#: ../../tooling/mixer.rst:18 +msgid "mixer uses the following sources as inputs to generate update content:" +msgstr "" + +#: ../../tooling/mixer.rst:20 +msgid "Upstream |CL| bundles with their corresponding RPM packages" +msgstr "" + +#: ../../tooling/mixer.rst:21 +msgid "Locally-defined bundles with their corresponding local RPM packages" +msgstr "" + +#: ../../tooling/mixer.rst:22 +msgid "Locally-defined bundles with upstream RPM packages" +msgstr "" + +#: ../../tooling/mixer.rst:24 +msgid "" +"Using the mixer tool, you select which set of content from these sources " +"will be part of your update. You can select content from each of these " +"sources to make a unique combination of functionality for your custom " +"update content, known as a **mix**." +msgstr "" + +#: ../../tooling/mixer.rst:29 +msgid "" +"The update content that mixer generates consists of various pieces of OS " +"content, update metadata, as well as a complete image. The OS content " +"includes all files in an update, as well as zero- and delta-packs for " +"improved update performance. The update metadata, stored as manifests, " +"describes all of the bundle information for the update. Update content " +"produced by mixer is then published to a web server and consumed by " +"clients via swupd. Refer to :ref:`swupd ` for additional " +"information regarding updates and update content." +msgstr "" + +#: ../../tooling/mixer.rst:39 +msgid "How it works" +msgstr "" + +#: ../../tooling/mixer.rst:41 +msgid "Learn the mixer tool set up and workflow." +msgstr "" + +#: ../../tooling/mixer.rst:48 +msgid "Prerequisites" +msgstr "" + +#: ../../tooling/mixer.rst:50 +msgid ":command:`mixer` bundle" +msgstr "" + +#: ../../tooling/mixer.rst:52 +msgid "" +"Add the mixer tool with the :command:`mixer` bundle. Refer to `Install a " +"bundle`_ for more details." +msgstr "" + +#: ../../tooling/mixer.rst:55 +msgid "Docker\\* container" +msgstr "" + +#: ../../tooling/mixer.rst:57 +msgid "" +"mixer by default runs all build commands in a Docker container to ensure " +"the correct tool versions are used. This also allows custom mixes to " +"automatically perform downstream format bumps when the upstream releases " +"a format bump. See `Format version`_ for additional information regarding" +" format bumps." +msgstr "" + +#: ../../tooling/mixer.rst:63 +msgid "Refer to `Configure and enable Docker`_ for instruction." +msgstr "" + +#: ../../tooling/mixer.rst:65 +msgid "Docker proxy (optional)" +msgstr "" + +#: ../../tooling/mixer.rst:67 +msgid "" +"If you use a proxy server, you must set your proxy environment variables " +"and create a proxy configuration file for the Docker daemon and " +"container." +msgstr "" + +#: ../../tooling/mixer.rst:70 +msgid "" +"Consult your IT department for the correct values if you are behind a " +"corporate proxy." +msgstr "" + +#: ../../tooling/mixer.rst:73 +msgid "Refer to `Configure Docker proxy info`_ for instruction." +msgstr "" + +#: ../../tooling/mixer.rst:75 +msgid "Location to host the update content and images" +msgstr "" + +#: ../../tooling/mixer.rst:77 +msgid "" +"In order for swupd to make use of your mix, the update content for your " +"mix must be hosted on a web server. Your mix will be configured with an " +"update location URL, which swupd will use to pull down updates." +msgstr "" + +#: ../../tooling/mixer.rst:81 +msgid "" +"Refer to `Set up a nginx web server for mixer`_ for an simple example of " +"setting up an update location." +msgstr "" + +#: ../../tooling/mixer.rst:85 +msgid "Mix setup" +msgstr "" + +#: ../../tooling/mixer.rst:87 +msgid "" +"Follow these steps to create and initialize the mixer workspace. Complete" +" the setup before you create a mix." +msgstr "" + +#: ../../tooling/mixer.rst:90 +msgid "Create workspace." +msgstr "" + +#: ../../tooling/mixer.rst:92 +msgid "" +"The mixer tool uses a simple workspace to contain all input and output in" +" a basic directory structure. The workspace is simply an empty folder " +"from which you execute the mixer commands. Each mix uses its own separate" +" workspace." +msgstr "" + +#: ../../tooling/mixer.rst:97 +msgid "Initialize the workspace and mix." +msgstr "" + +#: ../../tooling/mixer.rst:99 +msgid "" +"Before you create a mix, you must explicitly initialize the mixer " +"workspace. During initialization, the mixer workspace is configured and " +"the base for your mix is defined. By default, your mix is based on the " +"latest upstream version and starts with the minimum set of bundles. Your " +"first custom mix version number starts at 10. Alternatively, you can " +"select other versions or bundle sets from which to start." +msgstr "" + +#: ../../tooling/mixer.rst:106 +msgid "" +"Initialization creates the directory structure within the workspace and " +"adds the :file:`builder.conf` file, which is used to configure the mixer " +"tool." +msgstr "" + +#: ../../tooling/mixer.rst:109 +msgid "" +"View the `mixer.init man page`_ for more information on mixer " +"initialization." +msgstr "" + +#: ../../tooling/mixer.rst:112 +msgid "View the list of `suitable versions`_ from which to mix." +msgstr "" + +#: ../../tooling/mixer.rst:114 +msgid "Edit builder.conf." +msgstr "" + +#: ../../tooling/mixer.rst:116 +msgid "" +":file:`builder.conf` tells the mixer tool how to configure the mix. For " +"example, it allows you to configure where mixer output is located and " +"where swupd update content will be located." +msgstr "" + +#: ../../tooling/mixer.rst:120 +msgid "" +"At minimum, set the URL of your update server so your custom OS knows " +"where to get update content." +msgstr "" + +#: ../../tooling/mixer.rst:123 +msgid "Refer to the `builder.conf`_ section for more information." +msgstr "" + +#: ../../tooling/mixer.rst:126 +msgid "Create a mix" +msgstr "" + +#: ../../tooling/mixer.rst:128 +msgid "A mix is created with the following steps:" +msgstr "" + +#: ../../tooling/mixer.rst:130 +msgid "Add custom RPMs and set up local repo (optional)." +msgstr "" + +#: ../../tooling/mixer.rst:132 +msgid "" +"If you are adding custom RPMs to your mix, you must add the RPMs to your " +"mix workspace and set up a corresponding local repository." +msgstr "" + +#: ../../tooling/mixer.rst:135 +msgid "" +"Go to the :ref:`autospec` guide to learn to build RPMs from " +"scratch. If the RPMs are not built on |CL|, make sure your configuration " +"and toolchain builds them correctly for |CL|. Otherwise there is no " +"guarantee they will be compatible." +msgstr "" + +#: ../../tooling/mixer.rst:140 +msgid "" +"Refer to the :ref:`autospec` guide for more information on using autospec" +" to build RPMs." +msgstr "" + +#: ../../tooling/mixer.rst:143 +msgid "Update and build bundles." +msgstr "" + +#: ../../tooling/mixer.rst:145 +msgid "" +"Add, edit, or remove bundles that will be part of your content and build " +"them. mixer automatically updates the :file:`mixbundles` file when you " +"update the bundles in your mix." +msgstr "" + +#: ../../tooling/mixer.rst:149 +msgid "" +"View the `mixer.bundle man page`_ for more information on configuring " +"bundles in a mix." +msgstr "" + +#: ../../tooling/mixer.rst:152 +msgid "View the `mixer.build man page`_ for more information on building bundles." +msgstr "" + +#: ../../tooling/mixer.rst:154 +msgid "" +"View the `Bundles`_ section for more information on how mixer manages " +"bundles." +msgstr "" + +#: ../../tooling/mixer.rst:157 +msgid "Create the update content." +msgstr "" + +#: ../../tooling/mixer.rst:159 +msgid "" +"mixer creates update content with this step. Zero-packs are created " +"automatically, and delta-packs can be optionally created at the same time" +" (for all builds after version 0)." +msgstr "" + +#: ../../tooling/mixer.rst:163 +msgid "" +"A zero-pack is the full set of content needed to go from mix version 0 " +"(nothing) to the mix version for which you just built content." +msgstr "" + +#: ../../tooling/mixer.rst:166 +msgid "" +"A delta-pack provides the content *delta* between a `PAST_VERSION` to a " +"`MIX_VERSION` that allows the transition from one mix version to another." +msgstr "" + +#: ../../tooling/mixer.rst:169 +msgid "View :ref:`swupd-guide` for more information on update content." +msgstr "" + +#: ../../tooling/mixer.rst:171 +msgid "Create image." +msgstr "" + +#: ../../tooling/mixer.rst:173 +msgid "" +"mixer creates a bootable image from your updated content using the " +":ref:`ister` tool. In this step you can specify which bundles you want " +"*preinstalled* in the image. Users can later install other bundles " +"available in your mix." +msgstr "" + +#: ../../tooling/mixer.rst:178 +msgid "Make update available." +msgstr "" + +#: ../../tooling/mixer.rst:180 +msgid "Deploy update content and images to your update server." +msgstr "" + +#: ../../tooling/mixer.rst:182 +msgid "" +"View the `Example 3: Deploy updates to target`_ for a simple deployment " +"scenario." +msgstr "" + +#: ../../tooling/mixer.rst:186 +msgid "Maintain or modify mix" +msgstr "" + +#: ../../tooling/mixer.rst:188 +msgid "" +"Update or modify your content to a new version by following the steps to " +"create a mix. Increment the mix version number for the next mix." +msgstr "" + +#: ../../tooling/mixer.rst:192 +msgid "Examples" +msgstr "" + +#: ../../tooling/mixer.rst:194 +msgid "" +"The following examples are designed to work together and in order. The " +"examples use:" +msgstr "" + +#: ../../tooling/mixer.rst:197 +msgid "A stock installation of |CL|." +msgstr "" + +#: ../../tooling/mixer.rst:198 +msgid "A web server that comes with |CL| to host the content updates." +msgstr "" + +#: ../../tooling/mixer.rst:199 +msgid "" +"A simple VM that updates against the locally produced content created in " +"Example 2." +msgstr "" + +#: ../../tooling/mixer.rst:202 +msgid "Complete all `Prerequisites`_ before using these examples." +msgstr "" + +#: ../../tooling/mixer.rst:205 +msgid "Example 1: Mix set up" +msgstr "" + +#: ../../tooling/mixer.rst:207 +msgid "" +"This example shows the basic steps for the first-time setup of mixer for " +"a new mix." +msgstr "" + +#: ../../tooling/mixer.rst:210 +msgid "Create an empty directory to use as a workspace for mixer:" +msgstr "" + +#: ../../tooling/mixer.rst:216 +msgid "" +"In your mixer workspace, generate an initial mix based on the latest " +"upstream |CL| version, with minimum bundles. In the initialization " +"output, be aware that your initial mix version is set to 10 and that the " +"minimum bundles have been added." +msgstr "" + +#: ../../tooling/mixer.rst:226 +msgid "" +"Edit :file:`builder.conf` to set the value of CONTENTURL and VERSIONURL " +"to the IP address of the nginx\\* server you set up in the prerequisite " +"`Set up a nginx web server for mixer`_. For example:" +msgstr "" + +#: ../../tooling/mixer.rst:238 +msgid "Example 2: Create a simple mix" +msgstr "" + +#: ../../tooling/mixer.rst:240 +msgid "" +"This example shows how to create a simple custom mix using upstream " +"content. We'll create an image for a QEMU virtual machine that we can use" +" later to test our mix." +msgstr "" + +#: ../../tooling/mixer.rst:244 +msgid "" +"We can use the default bundles that were added during initialization, but" +" these include the :command:`native-kernel` bundle that is intended to be" +" used on a bare metal system instead of a VM. So we will modify the " +"default bundle set to get a smaller kernel image, which will also be " +"faster to load." +msgstr "" + +#: ../../tooling/mixer.rst:249 +msgid "Update bundles in mix:" +msgstr "" + +#: ../../tooling/mixer.rst:256 +msgid "Build bundles:" +msgstr "" + +#: ../../tooling/mixer.rst:262 +msgid "" +"Look in ~/mixer/update/image//full for the full chroot after" +" the :command:`build` command completes." +msgstr "" + +#: ../../tooling/mixer.rst:265 +msgid "" +"Build update content. Browse to your \\http://localhost site and you'll " +"see the web page is now up, but with no update content. Build the update " +"content:" +msgstr "" + +#: ../../tooling/mixer.rst:272 +msgid "" +"Refresh your \\http://localhost site and now you can see the update " +"content for mix version 10." +msgstr "" + +#: ../../tooling/mixer.rst:275 ../../tooling/mixer.rst:339 +msgid "" +"Look in ~/mixer/update/www/ to see the update content in " +"your workspace." +msgstr "" + +#: ../../tooling/mixer.rst:278 +msgid "" +"Configure image. Edit the ister configuration file for your image to " +"include all of the bundles you want preinstalled in the image. If this is" +" the first time creating an image, first get a copy of the :file" +":`release-image-config.json` template file:" +msgstr "" + +#: ../../tooling/mixer.rst:287 +msgid "" +"For this example, edit :file:`release-image-config.json` so that the root" +" partition size is \"5G\" and replace the \"kernel-native\" bundle with " +"\"kernel-kvm\"." +msgstr "" + +#: ../../tooling/mixer.rst:307 +msgid "Build the image." +msgstr "" + +#: ../../tooling/mixer.rst:313 +msgid "" +"The output from this step will be :file:`release.img`, which is a live " +"image." +msgstr "" + +#: ../../tooling/mixer.rst:315 +msgid "" +"Make the next mix. Create a new version of your mix, for the live image " +"to update to. Increment your mix version by 10:" +msgstr "" + +#: ../../tooling/mixer.rst:322 +msgid "Repeat steps 1-3 to add the upstream :command:`curl` bundle to the mix:" +msgstr "" + +#: ../../tooling/mixer.rst:330 +msgid "Build optional delta-packs, which helps reduce client update time:" +msgstr "" + +#: ../../tooling/mixer.rst:336 +msgid "" +"Refresh your \\http://localhost site to see the update content for mix " +"version 20." +msgstr "" + +#: ../../tooling/mixer.rst:343 +msgid "Example 3: Deploy updates to target" +msgstr "" + +#: ../../tooling/mixer.rst:345 +msgid "" +"The image created in Example 2 is directly bootable in QEMU. In this " +"example, we'll boot the image from Example 2 to verify it, and update the" +" image from mix version 10 (from which the image was built), to mix " +"version 20." +msgstr "" + +#: ../../tooling/mixer.rst:349 +msgid "Set up the QEMU environment." +msgstr "" + +#: ../../tooling/mixer.rst:351 +msgid "Install the :command:`kvm-host` bundle to your |CL|:" +msgstr "" + +#: ../../tooling/mixer.rst:357 +msgid "" +"Get the virtual EFI firmware, download the image launch script, and make " +"it executable:" +msgstr "" + +#: ../../tooling/mixer.rst:366 +msgid "Start your VM image (created in Example 2):" +msgstr "" + +#: ../../tooling/mixer.rst:372 +msgid "Log in as root and set a password" +msgstr "" + +#: ../../tooling/mixer.rst:374 +msgid "Try out your mix." +msgstr "" + +#: ../../tooling/mixer.rst:376 +msgid "Take a look at the default bundles installed in your mix:" +msgstr "" + +#: ../../tooling/mixer.rst:386 +msgid "" +"You cannot see the curl bundle that you added in Example 2 because your " +"mix is still on version 10." +msgstr "" + +#: ../../tooling/mixer.rst:389 +msgid "" +"Check for updates. You should see that version 20 is available. Use swupd" +" to update your mix:" +msgstr "" + +#: ../../tooling/mixer.rst:398 +msgid "" +"Now your mix should be at version 20 and curl is now available. Try using" +" curl. This will fail because curl is not yet installed:" +msgstr "" + +#: ../../tooling/mixer.rst:406 +msgid "" +"Add the new bundle from your update server to your VM. Retry curl. It " +"works!" +msgstr "" + +#: ../../tooling/mixer.rst:413 +msgid "Shutdown your VM:" +msgstr "" + +#: ../../tooling/mixer.rst:424 +msgid "References" +msgstr "" + +#: ../../tooling/mixer.rst:426 +msgid "" +"Reference the `mixer man page`_ for details regarding mixer commands and " +"options." +msgstr "" + +#: ../../tooling/mixer.rst:435 +msgid "builder.conf" +msgstr "" + +#: ../../tooling/mixer.rst:437 +msgid "" +"mixer initialization creates a :file:`builder.conf` that stores the basic" +" configuration for the mixer tool. The items of primary interest are " +"CONTENTURL and VERSIONURL, which will be used by systems updating against" +" your custom content." +msgstr "" + +#: ../../tooling/mixer.rst:470 +msgid "" +"Additional explanation of variables in :file:`builder.conf` is provided " +"in Table 1." +msgstr "" + +#: ../../tooling/mixer.rst:474 +msgid "**Variable**" +msgstr "" + +#: ../../tooling/mixer.rst:474 +msgid "**Explanation**" +msgstr "" + +#: ../../tooling/mixer.rst:476 +msgid "`CERT`" +msgstr "" + +#: ../../tooling/mixer.rst:476 +msgid "" +"Sets the path where mixer stores the certificate file used to sign " +"content for verification. mixer automatically generates the certificate " +"if you do not provide the path to an existing one, and signs the " +":file:`Manifest.MoM` file to provide security for the updated content you" +" create." +msgstr "" + +#: ../../tooling/mixer.rst:483 +msgid "" +"chroot-builder uses the certificate file to sign the root " +":file:`Manifest.MoM` file to provide security for content verification." +msgstr "" + +#: ../../tooling/mixer.rst:487 +msgid "" +"swupd uses this certificate to verify the :file:`Manifest.MoM` file's " +"signature." +msgstr "" + +#: ../../tooling/mixer.rst:490 +msgid "" +"For now, we strongly recommend that you do not modify this variable, as " +"swupd expects a certificate with a very specific configuration to sign " +"and verify properly." +msgstr "" + +#: ../../tooling/mixer.rst:495 +msgid "`CONTENTURL` and `VERSIONURL`" +msgstr "" + +#: ../../tooling/mixer.rst:495 +msgid "" +"Set these variables to the IP address of the web server hosting the " +"update content." +msgstr "" + +#: ../../tooling/mixer.rst:498 +msgid "" +"VERSIONURL is the IP address where the swupd client looks to determine if" +" a new version is available." +msgstr "" + +#: ../../tooling/mixer.rst:501 +msgid "CONTENTURL is the location from which swupd pulls content updates." +msgstr "" + +#: ../../tooling/mixer.rst:504 +msgid "" +"If the web server is on the same machine as the SERVER_STATE_DIR " +"directory, you can create a symlink to the directory in your web server's" +" document root to easily host the content." +msgstr "" + +#: ../../tooling/mixer.rst:509 +msgid "These URLs are embedded in the images created by mixer." +msgstr "" + +#: ../../tooling/mixer.rst:511 +msgid "`DOCKER_IMAGE_PATH`" +msgstr "" + +#: ../../tooling/mixer.rst:511 +msgid "" +"Sets the base name of the docker image that mixer pulls down to run " +"builds in the proper container." +msgstr "" + +#: ../../tooling/mixer.rst:514 +msgid "`LOCAL_BUNDLE_DIR`" +msgstr "" + +#: ../../tooling/mixer.rst:514 +msgid "" +"Sets the path where mixer stores the local bundle definition files. The " +"bundle definition files include any new, original bundles you create, " +"along with any edited versions of upstream bundles." +msgstr "" + +#: ../../tooling/mixer.rst:519 +msgid "`SERVER_STATE_DIR`" +msgstr "" + +#: ../../tooling/mixer.rst:519 +msgid "" +"Sets the path to which mixer outputs content. By default, mixer " +"automatically sets the path." +msgstr "" + +#: ../../tooling/mixer.rst:522 +msgid "`VERSIONS_PATH`" +msgstr "" + +#: ../../tooling/mixer.rst:522 +msgid "" +"Sets the path for the mix version and upstream version's two state files:" +" :file:`mixversion` and :file:`upstreamversion`. mixer creates both files" +" for you when you set up the workspace." +msgstr "" + +#: ../../tooling/mixer.rst:527 +msgid "`YUM_CONF`" +msgstr "" + +#: ../../tooling/mixer.rst:527 +msgid "" +"Sets the path where mixer automatically generates the :file:`.yum-" +"mix.conf` file." +msgstr "" + +#: ../../tooling/mixer.rst:530 +msgid "" +"The yum configuration file points the chroot-builder to where the RPMs " +"are stored." +msgstr "" + +#: ../../tooling/mixer.rst:533 +msgid "**Table 1**: *Variables in builder.conf*" +msgstr "" + +#: ../../tooling/mixer.rst:537 +msgid "Format version" +msgstr "" + +#: ../../tooling/mixer.rst:539 +msgid "" +"Compatible versions of an OS are tracked with an OS *compatibility " +"epoch*. Versions of an OS within an epoch are fully compatible and can " +"update to any other version within that epoch. The compatibility epoch is" +" set as the `Format` variable in the :file:`mixer.state` file. Variables " +"in the :file:`mixer.state` are used by mixer between executions and " +"should not be manually changed." +msgstr "" + +#: ../../tooling/mixer.rst:545 +msgid "" +"If `Format` increments to a new epoch (a \"format bump\"), the OS has " +"changed in such a way that updating from build M in format X to build N " +"in format Y will not work. Generally, this scenario occurs when the " +"software updater or the software has a change such that it is no longer " +"compatible with the previous update scheme, or when a package is removed " +"from the update stream and the update must ensure the files associated " +"with that package are removed from the system." +msgstr "" + +#: ../../tooling/mixer.rst:552 +msgid "" +"Using a format increment, we make sure pre- and co-requisite changes flow" +" out with proper ordering. The updated client will only update to the " +"latest release in its respective format version, unless overridden by " +"command line flags. In this way, we can guarantee that all clients update" +" to the final version in their given format." +msgstr "" + +#: ../../tooling/mixer.rst:558 +msgid "" +"The given format *must* contain all the changes needed to understand the " +"content built in the next format. Only after reaching the final release " +"in the old format can a client continue to update to releases in the new " +"format." +msgstr "" + +#: ../../tooling/mixer.rst:562 +msgid "" +"The format version is incremented only when a compatibility breakage is " +"introduced. Normal updates, such as updating a software package, do not " +"require a format increment." +msgstr "" + +#: ../../tooling/mixer.rst:569 +msgid "Bundles" +msgstr "" + +#: ../../tooling/mixer.rst:571 +msgid "" +"mixer stores information about the bundles included in a mix in a flat " +"file called :file:`mixbundles`, which is located in the path set by the " +"VERSIONS_PATH variable in :file:`builder.conf`. :file:`mixbundles` is " +"automatically created when the mix is initiated. mixer will refresh the " +"file each time you change the bundles in the mix." +msgstr "" + +#: ../../tooling/mixer.rst:577 +msgid "" +"Bundles can include other bundles. Nested bundles can themselves include " +"other bundles. If you see an unexpected bundle in your mix, it is likely " +"a nested bundle in one of the bundles you explicitly added." +msgstr "" + +#: ../../tooling/mixer.rst:581 +msgid "" +"A bundle will fill into one of two categories: upstream or local. " +"Upstream bundles are those provided by |CL|. Local bundles are either " +"modified upstream bundles or new local bundles." +msgstr "" + +#: ../../tooling/mixer.rst:586 +msgid "Upstream bundles" +msgstr "" + +#: ../../tooling/mixer.rst:588 +msgid "" +"mixer automatically downloads and caches upstream bundle definition " +"files. These definition files are stored in the upstream-bundles " +"directory in the workspace. Do not modify the files in this directory. " +"This directory is simply a mirror for mixer to use. mixer will " +"automatically delete the contents of this directory before repopulating " +"it on-the-fly if a new version must be downloaded." +msgstr "" + +#: ../../tooling/mixer.rst:594 +msgid "" +"The mixer tool automatically caches the bundles for the |CL| version " +"configured in the :file:`upstreamversion` file. mixer also cleans up old " +"versions once they are no longer needed." +msgstr "" + +#: ../../tooling/mixer.rst:599 +msgid "Local bundles" +msgstr "" + +#: ../../tooling/mixer.rst:601 +msgid "" +"Local bundles are bundles that you create, or are edited versions of " +"upstream bundles. Local bundle definition files are stored in the local-" +"bundles directory in the workspace. The LOCAL_BUNDLE_DIR variable sets " +"the path of this directory in the :file:`builder.conf` file." +msgstr "" + +#: ../../tooling/mixer.rst:606 +msgid "" +"*mixer always checks for local bundles first and the upstream bundles " +"second.* So bundles in the local-bundles directory will always take " +"precedence over any upstream bundles that have the same name. This " +"precedence enables you to copy upstream bundles locally, and edit into a " +"local variation." +msgstr "" + +#: ../../tooling/mixer.rst:612 +msgid "Bundle configuration" +msgstr "" + +#: ../../tooling/mixer.rst:614 +msgid "" +"mixer provides commands to configure the bundles for a mix, such as to " +"add a bundle to a mix, to create a new bundle for a mix, or to remove a " +"bundle from a mix. View the `mixer.bundle man page`_ for a full list of " +"commands and more information on configuring bundles in a mix." +msgstr "" + +#: ../../tooling/mixer.rst:619 +msgid "" +"Editing an existing local bundle is as simple as opening the bundle " +"definition file in your favorite editor, making the desired edits, and " +"saving your changes." +msgstr "" + +#: ../../tooling/mixer.rst:624 +msgid "" +"Removing bundles from a mix: By default, removing a bundle will only " +"remove the bundle from the mix. The local bundle definition file will " +"still remain. To completely remove a bundle, including its local bundle " +"definition file, use the :command:`--local` flag." +msgstr "" + +#: ../../tooling/mixer.rst:629 +msgid "" +"If you remove the bundle definition file for a local, edited version of " +"an upstream bundle in a mix, the mix reverts to reference the original " +"upstream version of the bundle." +msgstr "" + +#: ../../tooling/mixer.rst:636 +msgid "Configure and enable Docker" +msgstr "" + +#: ../../tooling/mixer.rst:638 +msgid "" +"Use these steps to enable Docker for the mixer tool. Make sure to " +"`Configure Docker proxy info`_ first if needed." +msgstr "" + +#: ../../tooling/mixer.rst:641 +msgid "Start the Docker daemon:" +msgstr "" + +#: ../../tooling/mixer.rst:649 +msgid "Add user to the docker group" +msgstr "" + +#: ../../tooling/mixer.rst:656 +msgid "Pull Docker container manually (optional)" +msgstr "" + +#: ../../tooling/mixer.rst:658 +msgid "" +"By default, mixer automatically pulls a Docker container for mixing if " +"one does not already exist. If you need to troubleshoot the mixer " +"container, it may be useful to manually pull a mixer Docker container." +msgstr "" + +#: ../../tooling/mixer.rst:662 +msgid "" +"Versions of the mixer Docker container are available under the tags for " +"the `clearlinux/mixer repo " +"`_ on Docker Hub. Each " +"version of the mixer Docker container is named after the associated |CL| " +"upstream format version. Refer to `Format version`_ for additional " +"information on upstream format versions." +msgstr "" + +#: ../../tooling/mixer.rst:668 +msgid "Use the following steps to manually pull a mixer Docker container:" +msgstr "" + +#: ../../tooling/mixer.rst:670 +msgid "" +"Find the version of the container you need by viewing the tags for the " +"`clearlinux/mixer repo " +"`_ on Docker Hub." +msgstr "" + +#: ../../tooling/mixer.rst:674 +msgid "Pull the latest container version:" +msgstr "" + +#: ../../tooling/mixer.rst:680 +msgid "View local docker images:" +msgstr "" + +#: ../../tooling/mixer.rst:689 +msgid "Configure Docker proxy info" +msgstr "" + +#: ../../tooling/mixer.rst:691 +msgid "If needed, use these steps to configure the Docker proxy information." +msgstr "" + +#: ../../tooling/mixer.rst:693 +msgid "Create the Docker daemon proxy config directory:" +msgstr "" + +#: ../../tooling/mixer.rst:699 +msgid "" +"Create :file:`/etc/systemd/system/docker.service.d/http-proxy.conf` and " +"add the following using your own proxy values:" +msgstr "" + +#: ../../tooling/mixer.rst:708 +msgid "Reload the Docker daemon:" +msgstr "" + +#: ../../tooling/mixer.rst:714 +msgid "" +"Configure the Docker container proxies, to pass proxy settings to " +"containers:" +msgstr "" + +#: ../../tooling/mixer.rst:717 +msgid "Create a directory for your container config:" +msgstr "" + +#: ../../tooling/mixer.rst:723 +msgid "" +"Create the config file :file:`~/.docker/config.json` and add the " +"following entries, using your own proxy values:" +msgstr "" + +#: ../../tooling/mixer.rst:739 +msgid "Set ownership and permission on the docker config directory:" +msgstr "" + +#: ../../tooling/mixer.rst:746 +msgid "" +"Configure proxies to allow mixer to access upstream content from behind a" +" firewall." +msgstr "" + +#: ../../tooling/mixer.rst:749 +msgid "" +"Open your :file:`$HOME/.bashrc` file and add proxy and port values for " +"the following:" +msgstr "" + +#: ../../tooling/mixer.rst:760 +msgid "Log out and log back in for the proxies to take effect." +msgstr "" + +#: ../../tooling/mixer.rst:765 +msgid "Set up a nginx web server for mixer" +msgstr "" + +#: ../../tooling/mixer.rst:767 +msgid "" +"A web server is needed to host your update content. In this example, we " +"use the nginx web server, which comes with |CL|." +msgstr "" + +#: ../../tooling/mixer.rst:770 +msgid "Set up a nginx web server for mixer with the following steps:" +msgstr "" + +#: ../../tooling/mixer.rst:772 +msgid "Install the :command:`nginx` bundle:" +msgstr "" + +#: ../../tooling/mixer.rst:778 +msgid "Make the directory where mixer updates will reside:" +msgstr "" + +#: ../../tooling/mixer.rst:784 +msgid "" +"Create a symbolic link between your workspace updates and the updates on " +"the local nginx web server. In this example, `$HOME/mixer` is the " +"workspace for the mix." +msgstr "" + +#: ../../tooling/mixer.rst:792 +msgid "Set up ``nginx`` configuration:" +msgstr "" + +#: ../../tooling/mixer.rst:798 +msgid "Copy the default example configuration file:" +msgstr "" + +#: ../../tooling/mixer.rst:804 +msgid "" +"Configure the mixer update server. Create and add the following server " +"configuration content to :file:`/etc/nginx/conf.d/mixer.conf` (sudo " +"required):" +msgstr "" + +#: ../../tooling/mixer.rst:817 +msgid "Restart the daemon, enable nginx on boot, and start the service." +msgstr "" + +#: ../../tooling/mixer.rst:827 +msgid "" +"Verify the web server is running at \\http://localhost. At this point you" +" should no longer see a \"404 Not Found\" message." +msgstr "" + +#: ../../tooling/mixer.rst:831 +msgid "Related topics" +msgstr "" + +#: ../../tooling/mixer.rst:833 +msgid ":ref:`About mixer `" +msgstr "" + +#: ../../tooling/mixer.rst:834 +msgid ":ref:`autospec-about`" +msgstr "" + +#: ../../tooling/mixer.rst:835 +msgid ":ref:`bundles-about`" +msgstr "" + +#: ../../tooling/mixer.rst:836 +msgid ":ref:`swupd-about`" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tooling/swupd-guide.po b/locale/zh_CN/LC_MESSAGES/tooling/swupd-guide.po new file mode 100644 index 00000000..61a3c847 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tooling/swupd-guide.po @@ -0,0 +1,446 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tooling/swupd-guide.rst:4 +msgid "swupd" +msgstr "" + +#: ../../tooling/swupd-guide.rst:6 +msgid "" +":command:`swupd` links a |CL-ATTR| installation with upstream updates and" +" software." +msgstr "" + +#: ../../tooling/swupd-guide.rst:14 +msgid "Description" +msgstr "" + +#: ../../tooling/swupd-guide.rst:16 +msgid ":command:`swupd` has two main functions:" +msgstr "" + +#: ../../tooling/swupd-guide.rst:18 +msgid "" +"Manage software and replace APT or YUM, by installing bundles rather than" +" packages." +msgstr "" + +#: ../../tooling/swupd-guide.rst:20 +msgid "Check for system updates and install them." +msgstr "" + +#: ../../tooling/swupd-guide.rst:22 +msgid "" +":command:`swupd` manages overlapping dependencies behind the scenes, " +"ensuring that all software is compatible across the system. It can be " +"used to verify the OS, clean cached files, and fix issues." +msgstr "" + +#: ../../tooling/swupd-guide.rst:26 +msgid "" +":ref:`Bundles ` contain everything needed to deliver a software " +"capability. They are the smallest granularity component that is managed " +"by |CL|. A bundle comes with all of its dependencies rather than " +"downloading a cascade of package dependencies when installing a piece of " +"software." +msgstr "" + +#: ../../tooling/swupd-guide.rst:33 +msgid "Versioning" +msgstr "" + +#: ../../tooling/swupd-guide.rst:35 +msgid "" +"Using package managers to monitor software version compatibility or " +"compare multiple systems on many Linux distributions can be cumbersome." +msgstr "" + +#: ../../tooling/swupd-guide.rst:38 +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 "" + +#: ../../tooling/swupd-guide.rst:45 +msgid "" +"A number that represents the **current** release of the OS describes the " +"versions of all the software on the OS. Each build is composed of a " +"specific set of bundles made from a particular version of packages. On a " +"daily basis, this matters to system administrators who need to determine " +"which of their systems do not have the latest security fixes, or which " +"combinations of software have been tested. Every release of the same " +"number is guaranteed to contain the same versions of software, so there's" +" no ambiguity between two systems running the same version of |CL|." +msgstr "" + +#: ../../tooling/swupd-guide.rst:55 +msgid "Updating" +msgstr "" + +#: ../../tooling/swupd-guide.rst:57 +msgid "" +"|CL| enforces regular updating of the OS by default and automatically " +"checks for updates against a version server. The content server provides " +"the file and metadata content for all versions and can be the same as the" +" version server. The content url server provides metadata in the form of " +"*manifests*, which list and describe file contents, symlinks, and " +"directories. Additionally, the actual content is provided to clients in " +"the form of archive files." +msgstr "" + +#: ../../tooling/swupd-guide.rst:65 +msgid "" +"Software updates with |CL| are also efficient. Unlike package-based " +"distributions, :command:`swupd` only updates files that have changed, " +"rather than entire packages. For example, it is quite common for an OS " +"security patch to be as small as 15 KB. Using binary deltas, |CL| is able" +" to apply only what is needed." +msgstr "" + +#: ../../tooling/swupd-guide.rst:71 +msgid "" +"For details on how to generate update content for |CL|, see the " +":ref:`mixer ` tool." +msgstr "" + +#: ../../tooling/swupd-guide.rst:75 +msgid "How it works" +msgstr "" + +#: ../../tooling/swupd-guide.rst:78 +msgid "Prerequisites" +msgstr "" + +#: ../../tooling/swupd-guide.rst:80 +msgid "The device is on a well-connected network." +msgstr "" + +#: ../../tooling/swupd-guide.rst:81 +msgid "" +"The device is able to connect to an update server. The default server is:" +" http://update.clearlinux.org" +msgstr "" + +#: ../../tooling/swupd-guide.rst:85 +msgid "Updates" +msgstr "" + +#: ../../tooling/swupd-guide.rst:87 +msgid "" +"|CL| updates are automatic by default, but can be set to occur only on " +"demand. :command:`swupd` makes sure that regular updates are simple and " +"secure. It can also check the validity of currently installed files and " +"software, and can correct any problems." +msgstr "" + +#: ../../tooling/swupd-guide.rst:93 +msgid "Manifests" +msgstr "" + +#: ../../tooling/swupd-guide.rst:95 +msgid "" +"The |CL| software update content consists of data and metadata. The data " +"is the files that end up in the OS. The metadata contains relevant " +"information to properly provision the data to the OS file system, as well" +" as update the system and add or remove additional content to the OS." +msgstr "" + +#: ../../tooling/swupd-guide.rst:100 +msgid "" +"The manifests are mostly long lists of hashes that describe content. Each" +" bundle gets its own manifest file. There is a master manifest file that " +"describes all manifests to tie it all together." +msgstr "" + +#: ../../tooling/swupd-guide.rst:105 +msgid "Fullfiles, packs, and delta packs" +msgstr "" + +#: ../../tooling/swupd-guide.rst:107 +msgid "" +"To speed up updates and optimize content delivery, update data " +"provisioned to a system is obtained by one of the following methods:" +msgstr "" + +#: ../../tooling/swupd-guide.rst:110 +msgid "" +"*Fullfiles* are always generated for every file in every release. This " +"allows any |CL| to obtain the exact copy of the content for each version " +"directly. This is used if the OS verification needs to replace a single " +"file, for instance." +msgstr "" + +#: ../../tooling/swupd-guide.rst:115 +msgid "" +"*Packs* are available for some releases. They combine many files to speed" +" up the creation of installation media and large updates." +msgstr "" + +#: ../../tooling/swupd-guide.rst:118 +msgid "" +"*Delta packs* are an optimized version of packs that only contain updates" +" (binary diffs). They cannot be used without having the original file " +"content." +msgstr "" + +#: ../../tooling/swupd-guide.rst:122 +msgid "Bundle search" +msgstr "" + +#: ../../tooling/swupd-guide.rst:124 +msgid "" +":command:`swupd` searches download manifest data for bundles that match " +"the term. Enter only one term, or hyphenated term, per search. Use the " +"command :command:`man swupd` to learn more." +msgstr "" + +#: ../../tooling/swupd-guide.rst:128 +msgid "" +"Only the base bundle is returned. Bundles can contain other bundles via " +"includes. For more details, see `Bundle Definition Files`_ and its " +"subdirectory bundles." +msgstr "" + +#: ../../tooling/swupd-guide.rst:132 +msgid "" +"Bundles that are already installed are marked **(installed)** in search " +"results." +msgstr "" + +#: ../../tooling/swupd-guide.rst:135 +msgid "Optionally, you can review our `bundles`_ on GitHub\\*." +msgstr "" + +#: ../../tooling/swupd-guide.rst:138 +msgid "Examples" +msgstr "" + +#: ../../tooling/swupd-guide.rst:141 +msgid "Example 1: Disable and enable automatic updates" +msgstr "" + +#: ../../tooling/swupd-guide.rst:143 +msgid "" +"|CL| updates are automatic by default, but can be set to occur only on " +"demand." +msgstr "" + +#: ../../tooling/swupd-guide.rst:146 +msgid "Verify your current auto-update setting." +msgstr "" + +#: ../../tooling/swupd-guide.rst:156 +msgid "Disable automatic updates." +msgstr "" + +#: ../../tooling/swupd-guide.rst:170 +msgid "Check manually for updates." +msgstr "" + +#: ../../tooling/swupd-guide.rst:176 +msgid "Install an update after identifying one that you need." +msgstr "" + +#: ../../tooling/swupd-guide.rst:182 +msgid "Re-enable automatic installs." +msgstr "" + +#: ../../tooling/swupd-guide.rst:191 +msgid "Example 2: Find and install Kata Containers\\*" +msgstr "" + +#: ../../tooling/swupd-guide.rst:193 +msgid "" +"Kata Containers is a popular container implementation. Unlike other " +"container implementations, each Kata Container has its own kernel " +"instance and runs on its own :abbr:`VM (Virtual Machine)` for improved " +"security." +msgstr "" + +#: ../../tooling/swupd-guide.rst:198 +msgid "" +"|CL| makes it very easy to install, since you only need to add `one " +"bundle`_ to use `Kata Containers`_: `containers-virt`, despite a number " +"of dependencies. Also, check out our tutorial: :ref:`kata`." +msgstr "" + +#: ../../tooling/swupd-guide.rst:202 +msgid "Find the correct bundle." +msgstr "" + +#: ../../tooling/swupd-guide.rst:204 +msgid "" +"To return all possible matches for the search string, enter " +":command:`swupd search`, followed by 'kata':" +msgstr "" + +#: ../../tooling/swupd-guide.rst:211 +msgid "The output should be similar to:" +msgstr "" + +#: ../../tooling/swupd-guide.rst:229 +msgid "" +"If your search does not produce results with a specific term, shorten the" +" search term. For example, use *kube* instead of *kubernetes*." +msgstr "" + +#: ../../tooling/swupd-guide.rst:232 +msgid "Add the bundle." +msgstr "" + +#: ../../tooling/swupd-guide.rst:240 +msgid "To add multiple bundles, add a space followed by the bundle name." +msgstr "" + +#: ../../tooling/swupd-guide.rst:242 +msgid "The output of a successful installation should be similar to:" +msgstr "" + +#: ../../tooling/swupd-guide.rst:261 +msgid "Example 3: Verify and correct system file mismatch" +msgstr "" + +#: ../../tooling/swupd-guide.rst:263 +msgid "" +":command:`swupd` can determine whether system directories and files have " +"been added to, overwritten, removed, or modified (e.g., permissions)." +msgstr "" + +#: ../../tooling/swupd-guide.rst:270 +msgid "" +"All directories that are watched by :command:`swupd` are verified " +"according to the manifest data. Hash mismatches are flagged as follows:" +msgstr "" + +#: ../../tooling/swupd-guide.rst:287 +msgid "" +"In this case, Python\\* packages that were installed on top of the " +"default install were flagged as mismatched. :command:`swupd` can be " +"directed to ignore or fix issues based on command line options." +msgstr "" + +#: ../../tooling/swupd-guide.rst:291 +msgid "" +":command:`swupd` can correct any issues it detects. Additional directives" +" can be added including a white list of directories to be ignored." +msgstr "" + +#: ../../tooling/swupd-guide.rst:294 +msgid "" +"The following command repairs issues, removes unknown items, and ignores " +"files or directories matching :file:`/usr/lib/python`:" +msgstr "" + +#: ../../tooling/swupd-guide.rst:302 +msgid "Quick reference" +msgstr "" + +#: ../../tooling/swupd-guide.rst:305 +msgid "swupd info" +msgstr "" + +#: ../../tooling/swupd-guide.rst:305 +msgid "Returns the currently installed version and update servers." +msgstr "" + +#: ../../tooling/swupd-guide.rst:309 +msgid "swupd update " +msgstr "" + +#: ../../tooling/swupd-guide.rst:308 +msgid "" +"Updates to a specific version or updates to latest version if no " +"arguments are used." +msgstr "" + +#: ../../tooling/swupd-guide.rst:312 +msgid "swupd bundle-list [--all]" +msgstr "" + +#: ../../tooling/swupd-guide.rst:312 +msgid "Lists installed bundles." +msgstr "" + +#: ../../tooling/swupd-guide.rst:315 +msgid "swupd bundle-add [-b] " +msgstr "" + +#: ../../tooling/swupd-guide.rst:315 +msgid "Finds a bundle that contains your search term." +msgstr "" + +#: ../../tooling/swupd-guide.rst:318 +msgid "swupd bundle-add " +msgstr "" + +#: ../../tooling/swupd-guide.rst:318 +msgid "Adds a bundle." +msgstr "" + +#: ../../tooling/swupd-guide.rst:321 +msgid "swupd bundle-remove " +msgstr "" + +#: ../../tooling/swupd-guide.rst:321 +msgid "Removes a bundle." +msgstr "" + +#: ../../tooling/swupd-guide.rst:324 +msgid "swupd --help" +msgstr "" + +#: ../../tooling/swupd-guide.rst:324 +msgid "Lists additional :command:`swupd` commands." +msgstr "" + +#: ../../tooling/swupd-guide.rst:327 +msgid "man swupd" +msgstr "" + +#: ../../tooling/swupd-guide.rst:327 +msgid "Opens the :command:`swupd` man page." +msgstr "" + +#: ../../tooling/swupd-guide.rst:329 +msgid "" +"Refer to :command:`swupd` `source documentation`_ on GitHub for more " +"details." +msgstr "" + +#: ../../tooling/swupd-guide.rst:332 +msgid "Related topics" +msgstr "" + +#: ../../tooling/swupd-guide.rst:334 +msgid ":ref:`autospec`" +msgstr "" + +#: ../../tooling/swupd-guide.rst:335 +msgid ":ref:`mixer`" +msgstr "" + +#: ../../tooling/swupd-guide.rst:336 +msgid ":ref:`bundles`" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tooling/tooling.po b/locale/zh_CN/LC_MESSAGES/tooling/tooling.po new file mode 100644 index 00000000..4f4cac73 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tooling/tooling.po @@ -0,0 +1,30 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tooling/tooling.rst:4 +msgid "Tooling" +msgstr "" + +#: ../../tooling/tooling.rst:6 +msgid "" +"Clear Linux is a little different from other distros. Here are some " +"important tools and concepts for managing your install." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/aws-web/aws-web.po b/locale/zh_CN/LC_MESSAGES/tutorials/aws-web/aws-web.po new file mode 100644 index 00000000..a4cc924e --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/aws-web/aws-web.po @@ -0,0 +1,379 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/aws-web/aws-web.rst:4 +msgid "Create and launch |CL-ATTR| from Amazon Web Services" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:6 +msgid "" +"This tutorial walks you through creating and launching a |CL| :abbr:`AMI " +"(Amazon Machine Image)` instance from the :abbr:`AWS (Amazon Web " +"Services)` console and complete the following tasks:" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:10 +msgid "Locate and select the |CL| OS Basic AMI in the AWS Marketplace." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:11 +msgid "" +"Create a new public and private key pair to allow you to connect to your " +"|CL| instance securely." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:13 +msgid "Launch the new |CL| instance and connect to it." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:14 +msgid "Update your instance of |CL| using the :command:`swupd` command." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:15 +msgid "Stop the |CL| instance." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:18 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:20 +msgid "This tutorial assumes the following statements are true:" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:22 +msgid "" +"You are using a linux-based system to access AWS and can run " +":command:`SSH` to access the remote |CL| AWS image." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:24 +msgid "" +"Your browser puts downloaded files in the :file:`$HOME/Downloads` " +"directory." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:26 +msgid "" +"You have already set up an AWS user account and logged into the AWS " +"console." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:30 +msgid "" +"This tutorial uses a |CL| AMI t2.micro instance that is eligible for the " +"AWS free tier. To learn more about AWS and setting up an account, visit " +"the AWS website at http://aws.amazon.com." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:35 +msgid "Locate, select, and launch the |CL| Basic AMI" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:37 +msgid "" +"Start from your main AWS services console menu in your browser and select" +" the :guilabel:`EC2` text as shown in figure 1:" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:44 +msgid "Figure 1: :guilabel:`AWS Console`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:46 +msgid "This selection brings up your :guilabel:`EC2 Dashboard` menu." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:48 +msgid "" +"To create a new |CL| instance from the :guilabel:`EC2 Dashboard` menu, " +"select the :guilabel:`Launch Instance` button as shown in figure 2:" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:55 +msgid "Figure 2: :guilabel:`EC2 Dashboard`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:57 +msgid "" +"This selection takes you to the :guilabel:`Step 1: Choose an Amazon " +"Machine Image (AMI)` menu." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:60 +msgid "" +"To find the :guilabel:`Clear Linux OS Basic` AMI in the :guilabel:`Step " +"1: Choose an Amazon Machine Image (AMI)` menu, do the following:" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:64 +msgid "" +"In the lefthand navigation window, select the :guilabel:`AWS Marketplace`" +" menu item to bring up the search bar to :guilabel:`Search AWS " +"Marketplace Products`." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:68 +msgid "" +"In the search bar, type \"clear linux os\" and hit the :kbd:`Enter` key " +"to search for and locate the :guilabel:`Clear Linux OS Basic` AMI." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:71 +msgid "" +"Select the :guilabel:`Clear Linux OS Basic` AMI by clicking on the " +":guilabel:`Select` button as shown in figure 3:" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:78 +msgid "Figure 3: :guilabel:`Step 1: Choose AMI`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:80 +msgid "" +"A pop-up dialog box appears showing you more information about the " +":guilabel:`Clear Linux OS Basic` AMI along with the pricing details for " +"running |CL| on different platform configurations as shown in figure 4. " +"Select the :guilabel:`Continue` button." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:89 +msgid "Figure 4: :guilabel:`Clear Linux OS Basic`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:91 +msgid "The :guilabel:`Choose Instance Type` menu appears as shown in figure 5." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:97 +msgid "Figure 5: :guilabel:`Choose an Instance Type`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:99 +msgid "" +"Select the :guilabel:`t2.micro` type by clicking the box on the left side" +" of the instance and then select the :guilabel:`Review and Launch` button" +" to move to the :guilabel:`Step 7: Review the Instance Launch` menu." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:105 +msgid "" +"You can configure the instance details, add additional storage, add tags," +" and configure the security group before selecting the :guilabel:`Review " +"and Launch` button if you want to further customize this |CL| instance." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:110 +msgid "" +"The :guilabel:`Step 7: Review the Instance Launch` menu, shown in figure " +"6, allows you to :guilabel:`Cancel` the process, return to the " +":guilabel:`Previous` screen to change the configuration or " +":guilabel:`Launch` the instance defined." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:119 +msgid "Figure 6: :guilabel:`Step 7: Review the Instance Launch`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:121 +msgid "" +"Select the :guilabel:`Launch` button. A dialog box appears, as shown in " +"figure 7, asking you to :guilabel:`Select an existing key pair or create " +"a new pair`." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:129 +msgid "Figure 7: :guilabel:`Select an existing key pair or create a new pair`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:131 +msgid "Select the :guilabel:`Create a new key pair` option." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:133 +msgid "For the :guilabel:`Key pair name` field, enter `AWSClearTestKey`." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:135 +msgid "" +"Select the :guilabel:`Download Key Pair` button to download the " +":file:`AWSClearTestKey.pem` to your browser's defined :file:`Downloads` " +"directory." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:139 +msgid "" +"When the file finishes downloading, select the :guilabel:`Launch " +"Instances` button to proceed to the :guilabel:`Launch Status` menu shown " +"in figure 8." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:147 +msgid "Figure 8: :guilabel:`Launch Status`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:149 +msgid "" +"Once the :guilabel:`Launch Status` page changes to what is shown in " +"figure 9, select the :guilabel:`View Instances` button to view your " +":guilabel:`Instances` dashboard." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:157 +msgid "Figure 9: :guilabel:`View Instance`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:160 +msgid "Connect to your Clear Linux OS Basic instance" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:162 +msgid "" +"Your :guilabel:`Instances` Dashboard is shown in figure 10 with the new " +"|CL| OS basic instance already selected and in the running state. If " +"there are other instances available, they are also listed but not " +"selected." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:170 +msgid "Figure 10: :guilabel:`Instance Dashboard`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:172 +msgid "" +"To connect to your running instance, click the :guilabel:`Connect` button" +" located at the top of your dashboard. AWS brings up the pop-up dialog " +"box shown in figure 11 describing how to connect to your running " +"instance." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:182 +msgid "Figure 11: :guilabel:`Connect to Your Instance`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:184 +msgid "" +"Open a terminal on your system. You should be in your :file:`$HOME` " +"directory." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:187 +msgid "" +"Copy the previously downloaded keyfile from the :file:`Downloads` " +"directory to the current directory." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:194 +msgid "" +"Change the attributes of the :file:`AWSClearTestKey.pem` using the " +":command:`chmod` command as instructed in the dialog box shown in figure " +"11." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:202 +msgid "" +"Copy the text highlighted in the :guilabel:`Example:` section that is " +"shown in :ref:`figure 11`. Paste the copied text into " +"your terminal, change the text before the `@` sign to the username " +"`clear`, and press the :kbd:`Enter` key to execute the command." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:211 +msgid "" +"A message appears on the terminal stating the authenticity of the host " +"can't be established and prompts you with the message:" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:220 +msgid "" +"Type `yes` and hit the :kbd:`Enter` key. Another warning is printed to " +"the terminal and you are now at the command prompt of your new |CL| " +"instance." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:229 +msgid "Update the |CL| instance" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:231 +msgid "" +"Run the :command:`sudo swupd update` command to update the operating " +"system as shown in figure 12:" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:238 +msgid "Figure 12: :guilabel:`sudo swupd update`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:240 +msgid "In this example we updated from version 18940 to 19100." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:243 +msgid "Stop the |CL| instance" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:245 +msgid "" +"When you are finished using your AWS |CL| instance you need to stop it " +"using the :guilabel:`Instances` dashboard to stop accruing charges. " +"Complete the following steps from the :guilabel:`Instances` dashboard to " +"stop your AWS |CL| instance from running." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:250 +msgid "Select the :guilabel:`Actions` button to bring up a pull-down menu." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:252 +msgid "Select the :guilabel:`Instance State` menu item to expand the options." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:254 +msgid "Select :guilabel:`Stop` menu item to shut down the running instance." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:256 +msgid "Figure 13 illustrates these steps." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:262 +msgid "Figure 13: :guilabel:`Stop Instance`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:264 +msgid "" +"A pop-up dialog box appears warning you that any ephemeral storage of " +"your instance will be lost. Select the :guilabel:`Yes, Stop` button to " +"stop your |CL| instance." +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:272 +msgid "Figure 14: :guilabel:`Stop Instances`" +msgstr "" + +#: ../../tutorials/aws-web/aws-web.rst:274 +msgid "" +"Congratulations! You are up and running with |CL| on AWS. To see what you" +" can do with your |CL| instance, visit our :ref:`tutorials ` " +"section for examples on using your |CL| system." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/azure.po b/locale/zh_CN/LC_MESSAGES/tutorials/azure.po new file mode 100644 index 00000000..75be9084 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/azure.po @@ -0,0 +1,445 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/azure.rst:4 +msgid "Run |CL-ATTR| using Microsoft Azure CLI 2.0" +msgstr "" + +#: ../../tutorials/azure.rst:6 +msgid "" +"|CL-ATTR| is available for you to use in the Microsoft* Azure* " +"marketplace and is offered with three different images, also known as a " +":abbr:`SKU (Stock Keeping Unit)`." +msgstr "" + +#: ../../tutorials/azure.rst:10 +msgid "" +"|CL| Basic - This SKU consists of a bare-bones system which can be used " +"as a starting point for those wanting to explore and build out a system " +"with additional software bundles of their choosing." +msgstr "" + +#: ../../tutorials/azure.rst:14 +msgid "" +"|CL| Containers - This SKU comes with the containers-basic software " +"bundle already installed." +msgstr "" + +#: ../../tutorials/azure.rst:17 +msgid "" +"|CL| Machine-learning - This SKU comes pre-loaded with popular open " +"source tools for developing machine learning applications." +msgstr "" + +#: ../../tutorials/azure.rst:20 +msgid "" +"You can access these images directly from your MS Azure dashboard through" +" the `Azure portal`_ or by using the MS Azure :abbr:`CLI (Command Line " +"Interface)` 2.0. If you do not already have an account set up with MS " +"Azure, you can sign up for a `MS Azure free account`_ to access the |CL| " +":abbr:`VM(Virtual Machine)` images." +msgstr "" + +#: ../../tutorials/azure.rst:26 +msgid "" +"The Azure CLI offers the ability to create and manage resources in MS " +"Azure from the command line. In this tutorial you learn to:" +msgstr "" + +#: ../../tutorials/azure.rst:29 +msgid "Install the latest MS Azure CLI on your |CL| machine." +msgstr "" + +#: ../../tutorials/azure.rst:31 +msgid "Log into MS Azure using the CLI 2.0 interface." +msgstr "" + +#: ../../tutorials/azure.rst:33 +msgid "Create a MS Azure resource group." +msgstr "" + +#: ../../tutorials/azure.rst:35 +msgid "Locate the |CL| images." +msgstr "" + +#: ../../tutorials/azure.rst:37 +msgid "Create and log into the |CL| virtual machine." +msgstr "" + +#: ../../tutorials/azure.rst:39 +msgid "Stop and deallocate the |CL| VM and resources." +msgstr "" + +#: ../../tutorials/azure.rst:41 +msgid "" +"To use the MS Azure CLI 2.0 on your |CL| system, your system must have " +"the following packages installed:" +msgstr "" + +#: ../../tutorials/azure.rst:44 +msgid "Python 2.7 or later" +msgstr "" + +#: ../../tutorials/azure.rst:46 +msgid "libffi" +msgstr "" + +#: ../../tutorials/azure.rst:48 +msgid "OpenSSL 1.0.2" +msgstr "" + +#: ../../tutorials/azure.rst:50 +msgid "" +"You can check to see what versions you have installed on your system by " +"running the individual commands as follows:" +msgstr "" + +#: ../../tutorials/azure.rst:78 +msgid "" +"If you do not have these packages installed on your |CL| system, install " +"the sysadmin-basic software bundle using the :command:`swupd` command:" +msgstr "" + +#: ../../tutorials/azure.rst:87 +msgid "" +"These instructions are for installing the MS Azure CLI 2.0 tools on a " +"|CL| system. If you are installing the CLI on another platform, follow " +"the instructions in the `MS Azure Install Azure CLI tutorial`_ for your " +"specific operating system." +msgstr "" + +#: ../../tutorials/azure.rst:93 +msgid "Install MS Azure CLI 2.0 on |CL|" +msgstr "" + +#: ../../tutorials/azure.rst:95 +msgid "" +"To install the MS Azure CLI 2.0 on |CL|, use the :command:`curl` command " +"as follows:" +msgstr "" + +#: ../../tutorials/azure.rst:102 +msgid "" +"If you get an error message from :command:`curl` related to the -L " +"parameter or an error message is generated that includes the text " +"\"Object Moved\", use the full URL instead of the aka.ms redirect " +"address:" +msgstr "" + +#: ../../tutorials/azure.rst:110 +msgid "" +"The installation script begins and prompts you several times during " +"execution for information." +msgstr "" + +#: ../../tutorials/azure.rst:115 +msgid "" +"The console output from the script displays your username instead of the " +"**[user]** variable shown on this tutorial." +msgstr "" + +#: ../../tutorials/azure.rst:122 +msgid "" +"Press the :kbd:`Enter` key to accept the default or you can chose another" +" directory to install the MS Azure CLI 2.0 tools into." +msgstr "" + +#: ../../tutorials/azure.rst:129 +msgid "" +"Press the :kbd:`Enter` key to accept the default or you can chose another" +" directory to install the :command:`az` executable in." +msgstr "" + +#: ../../tutorials/azure.rst:132 +msgid "" +"The installation downloads and builds all required tools and when " +"complete prompts you with:" +msgstr "" + +#: ../../tutorials/azure.rst:139 +msgid "Type :kbd:`Y` and press the :kbd:`Enter` key to allow this modification." +msgstr "" + +#: ../../tutorials/azure.rst:145 +msgid "" +"Press the :kbd:`Enter` key to accept the default or enter the pathname to" +" your :file:`.bashrc` file. The installation completes with the final " +"output shown below:" +msgstr "" + +#: ../../tutorials/azure.rst:160 +msgid "" +"The installation program finishes and you must restart your shell for the" +" changes to take effect. When the installation is successful, run the " +"following command to restart your shell." +msgstr "" + +#: ../../tutorials/azure.rst:168 +msgid "" +"With the MS Azure CLI 2.0 executable successfully built and installed, " +"run the :command:`az` command." +msgstr "" + +#: ../../tutorials/azure.rst:175 +msgid "The output from the :command:`az` command is shown below:" +msgstr "" + +#: ../../tutorials/azure.rst:254 +msgid "Log into your Microsoft Azure account" +msgstr "" + +#: ../../tutorials/azure.rst:256 +msgid "" +"With the :command:`az` command properly installed and functional, login " +"to your MS Azure account using the :command:`az login` command shown " +"below:" +msgstr "" + +#: ../../tutorials/azure.rst:263 +msgid "The output from this command is:" +msgstr "" + +#: ../../tutorials/azure.rst:269 +msgid "" +"Open your browser and enter the page `https://aka.ms/devicelogin` as " +"shown in figure 1:" +msgstr "" + +#: ../../tutorials/azure.rst:276 +msgid "Figure 1: :guilabel:`Microsoft Device Login`" +msgstr "" + +#: ../../tutorials/azure.rst:278 +msgid "" +"Enter the code `BQ9MG442B` to authenticate your device as shown in figure" +" 2. The code `BQ9MG442B` is a random authentication code generated for " +"each session login and will be different each time you log into MS Azure " +"using the :command:`az login` command." +msgstr "" + +#: ../../tutorials/azure.rst:287 +msgid "Figure 2: :guilabel:`Microsoft Device Login - Azure CLI`" +msgstr "" + +#: ../../tutorials/azure.rst:289 +msgid "" +"Once you enter the authentication code, the website changes to a screen " +"to enter your existing Microsoft Azure credentials." +msgstr "" + +#: ../../tutorials/azure.rst:292 +msgid "" +"Log in with your existing MS Azure account credentials. Once complete, " +"the browser screen changes again as shown in figure 3. The screen shows " +"you have signed into the Microsoft Cross-platform Command Line Interface " +"application on your device and you can close the window." +msgstr "" + +#: ../../tutorials/azure.rst:301 +msgid "Figure 3: :guilabel:`Microsoft Azure Cross-platform CLI`" +msgstr "" + +#: ../../tutorials/azure.rst:303 +msgid "" +"The MS Azure CLI 2.0 interface is now active using your existing MS Azure" +" account credentials." +msgstr "" + +#: ../../tutorials/azure.rst:307 +msgid "Create a MS Azure resource group" +msgstr "" + +#: ../../tutorials/azure.rst:309 +msgid "" +"To learn more about MS Azure resource groups, visit the `Azure Resource " +"Manager overview`_ for an overview and detailed description of resources " +"within MS Azure." +msgstr "" + +#: ../../tutorials/azure.rst:313 +msgid "" +"To create our new resource group, run the :command:`az group create ...` " +"command shown below to create a resource group named `ClearResourceGroup`" +" using the `-n` parameter and locate it in the `westus` region using the " +"`-l` parameter." +msgstr "" + +#: ../../tutorials/azure.rst:322 +msgid "" +"When the command has completed, the output from this command is similar " +"to the following:" +msgstr "" + +#: ../../tutorials/azure.rst:339 +msgid "Create and log into the |CL| virtual machine" +msgstr "" + +#: ../../tutorials/azure.rst:341 +msgid "For this tutorial, we are using the |CL| Basic SKU for our VM." +msgstr "" + +#: ../../tutorials/azure.rst:343 +msgid "" +"To locate the available |CL| Basic VM SKU images in the MS Azure " +"marketplace, run the :command:`az vm image ...` command:" +msgstr "" + +#: ../../tutorials/azure.rst:350 +msgid "" +"This command may take some time to finish. The output lists all available" +" |CL| Basic images available in the Microsoft Azure marketplace as shown " +"below:" +msgstr "" + +#: ../../tutorials/azure.rst:370 +msgid "" +"The output list shows current offerings. New versions are added to the MS" +" Azure marketplace all the time. To reference the latest version of an " +"image, you can use the version label `latest` when specifying an image." +msgstr "" + +#: ../../tutorials/azure.rst:374 +msgid "" +"The information shown in the `Urn` column lists the " +"`Publisher:Offer:Sku:Version` for each image available and this is the " +"information we want to create the |CL| Basic VM. Since we are creating a " +"|CL| Basic VM, highlight the `clear-linux-project:clear-linux-os:basic:` " +"string and copy it to your clipboard. Use the label `latest` instead of " +"referencing a specific version." +msgstr "" + +#: ../../tutorials/azure.rst:381 +msgid "" +"Create the new |CL| Basic VM. Run the :command:`az vm create ...` command" +" using the URN `:clear-linux-project:clear-linux-os:basic:latest` that we" +" copied to the clipboard on the previous step." +msgstr "" + +#: ../../tutorials/azure.rst:391 +msgid "" +"If you have already defined your public/private SSH key pair and they are" +" stored in your :file:`$HOME/.ssh` directory, you do not need to include " +"the *--generate-ssh-keys* option." +msgstr "" + +#: ../../tutorials/azure.rst:395 +msgid "" +"Your output from this command will look similar to this output, where " +"[user] is your user name:" +msgstr "" + +#: ../../tutorials/azure.rst:416 +msgid "Take note of the public IP address from the output." +msgstr "" + +#: ../../tutorials/azure.rst:418 +msgid "" +"Login into the new |CL| Basic VM, run the :command:`ssh` command with the" +" public IP address obtained from the previous step as shown:" +msgstr "" + +#: ../../tutorials/azure.rst:425 +msgid "" +"You may see the following message about the authenticity of the host. If " +"this appears, type `yes` to proceed connecting to your new |CL| VM." +msgstr "" + +#: ../../tutorials/azure.rst:437 +msgid "" +"You are now logged into your new |CL| VM as [user], where [user] is your " +"user name. To check which software bundles are included with this VM " +"image, run the :command:`sudo swupd bundle-list` command inside the VM:" +msgstr "" + +#: ../../tutorials/azure.rst:445 +msgid "The output shown should be similar to:" +msgstr "" + +#: ../../tutorials/azure.rst:467 +msgid "" +"When you are finished using your new |CL| VM, type :command:`exit` to " +"close the :command:`SSH` terminal and logout." +msgstr "" + +#: ../../tutorials/azure.rst:471 +msgid "Stop and deallocate the |CL| VM and resources" +msgstr "" + +#: ../../tutorials/azure.rst:473 +msgid "" +"When you finish using your new |CL| instance, you must stop the VM and " +"deallocate the resources in your resource group. If you only stop a VM, " +"the OS image shuts down but the resources associated with it in your " +"resource group remain allocated and incurring charges. For instance, if " +"you stop and then later start the VM using the :command:`az vm start...` " +"without deallocating the resources, the IP address is retained and you " +"can access the VM using that same IP address. To release the resources " +"associated with the VM and stop incurring charges for them, you must " +"deallocate the resources as well." +msgstr "" + +#: ../../tutorials/azure.rst:482 +msgid "" +"At the command prompt, enter the :command:`az vm stop...` command as " +"follows:" +msgstr "" + +#: ../../tutorials/azure.rst:489 +msgid "This will stop the VM and then output text similar to:" +msgstr "" + +#: ../../tutorials/azure.rst:501 +msgid "" +"Once the VM stops, deallocate the VM resources to stop incurring charges " +"for the |CL| instance. Enter the following command:" +msgstr "" + +#: ../../tutorials/azure.rst:508 +msgid "**Congratulations!**" +msgstr "" + +#: ../../tutorials/azure.rst:510 +msgid "" +"You are up and running with |CL| on MS Azure using the Azure CLI 2.0 " +"command line tools." +msgstr "" + +#: ../../tutorials/azure.rst:514 +msgid "Next steps" +msgstr "" + +#: ../../tutorials/azure.rst:516 +msgid "" +"To see use cases you can fulfill with your |CL| instance, visit our " +":ref:`tutorials ` section." +msgstr "" + +#: ../../tutorials/azure.rst:519 +msgid "" +"For additional information visit the |CL| `Azure Partner Mini Case " +"Study`_ and the `Azure Partner Datasheet`_." +msgstr "" + +#: ../../tutorials/azure.rst:522 +msgid "" +"To learn more about the MS Azure CLI 2.0 tool and options that are " +"available, visit the `MS Azure documentation and tutorials`_ website." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/dars.po b/locale/zh_CN/LC_MESSAGES/tutorials/dars.po new file mode 100644 index 00000000..a4f30456 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/dars.po @@ -0,0 +1,128 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/dars.rst:4 +msgid "Data Analytics Reference Stack" +msgstr "" + +#: ../../tutorials/dars.rst:6 +msgid "" +"This tutorial shows you how to use the Data Analytics Reference Stack " +"(DARS), and to optionally build your own images with the baseline " +"Dockerfiles provided in the `DARS repository`_. Our assumption is that " +"|CL-ATTR| is the host. However, any system that supports Docker\\* " +"containers can be used to follow these steps." +msgstr "" + +#: ../../tutorials/dars.rst:17 +msgid "The Data Analytics Reference Stack release" +msgstr "" + +#: ../../tutorials/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 "" + +#: ../../tutorials/dars.rst:21 +msgid "" +"The Data Analytics Reference Stack provides two pre-built Docker images, " +"available on `Docker Hub`_:" +msgstr "" + +#: ../../tutorials/dars.rst:23 +msgid "A |CL|-derived `DARS with OpenBlas`_ stack optimized for `OpenBLAS`_" +msgstr "" + +#: ../../tutorials/dars.rst:24 +msgid "A |CL|-derived `DARS with MKL`_ stack optimized for `MKL`_" +msgstr "" + +#: ../../tutorials/dars.rst:26 +msgid "" +"We recommend you view the latest component versions for each image in the" +" :file:`README` found in the `DARS 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 "" + +#: ../../tutorials/dars.rst:34 +msgid "Using the Docker Images" +msgstr "" + +#: ../../tutorials/dars.rst:36 +msgid "" +"To immediately start using the latest stable DARS images, pull directly " +"from `Docker Hub`_. For this tutorial we'll use the `Dars with MKL`_ " +"version of the stack." +msgstr "" + +#: ../../tutorials/dars.rst:39 +msgid "Once you have downloaded the image, you can run it with" +msgstr "" + +#: ../../tutorials/dars.rst:45 +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 "" + +#: ../../tutorials/dars.rst:66 +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 "" + +#: ../../tutorials/dars.rst:71 +msgid "Building DARS Images" +msgstr "" + +#: ../../tutorials/dars.rst:73 +msgid "" +"If you choose to build your own DARS container images, you can customize " +"them as needed. Use the provided Dockerfile as a baseline. 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 "" + +#: ../../tutorials/dars.rst:79 +msgid "First, clone the `DARS repository`_ from GitHub." +msgstr "" + +#: ../../tutorials/dars.rst:85 +msgid "" +"Then, inside the DARS directory, run :command:`make` to build OpenBLAS " +"and MKL images, and run :command:`make baseline` to build the baseline " +"CentOS image. Depending on the system, it may take a while to finish " +"building. Once completed, check the resulting images with " +":command:`Docker`" +msgstr "" + +#: ../../tutorials/dars.rst:94 +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 "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/dlrs/dlrs.po b/locale/zh_CN/LC_MESSAGES/tutorials/dlrs/dlrs.po new file mode 100644 index 00000000..936cb860 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/dlrs/dlrs.po @@ -0,0 +1,615 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/dlrs/dlrs.rst:4 +msgid "Deep Learning Reference Stack" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:6 +msgid "" +"This tutorial describes how to run benchmarking workloads for " +"TensorFlow\\*, PyTorch\\*, and Kubeflow in |CL-ATTR| using the Deep " +"Learning Reference Stack." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:14 +msgid "Overview" +msgstr "" + +#: ../../tutorials/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 tutorial to run " +"benchmarking workloads on your solution." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:22 +msgid "The Deep Learning Reference Stack is available in the following versions:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:24 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:27 +msgid "" +"`Intel MKL-DNN`_, which includes the TensorFlow framework optimized using" +" Intel® Math Kernel Library for Deep Neural Networks (Intel® MKL-DNN) " +"primitives." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:30 +msgid "`Eigen`_, which includes `TensorFlow`_ optimized for Intel® architecture." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:31 +msgid "`PyTorch with OpenBLAS`_, which includes PyTorch with OpenBlas." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:32 +msgid "" +"`PyTorch with Intel MKL-DNN`_, which includes PyTorch optimized using " +"Intel® Math Kernel Library (Intel® MKL) and Intel MKL-DNN." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:37 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:40 +msgid "Intel® AVX-512 images require an Intel® Xeon® Scalable Platform" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:41 +msgid "VNNI requires a 2nd generation Intel® Xeon® Scalable Platform" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:44 +msgid "Stack features" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:46 +msgid "Deep Learning Reference Stack `V3.0 release announcement`_." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:47 +msgid "" +"Deep Learning Reference Stack v2.0 including current `PyTorch benchmark " +"results`_." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:49 +msgid "" +"Deep Learning Reference Stack v1.0 including current `TensorFlow " +"benchmark results`_." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:51 +msgid "" +"`Release notes on Github\\*`_ for the latest release of Deep Learning " +"Reference Stack." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:56 +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 `terms of " +"use`_ for more details about licensing and usage of the Deep Learning " +"Reference Stack." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:61 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:63 +msgid ":ref:`Install ` |CL| on your host system" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:64 +msgid ":command:`containers-basic` bundle" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:65 +msgid ":command:`cloud-native-basic` bundle" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:67 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:76 +msgid "" +"To install the :command:`containers-basic` or :command:`cloud-native-" +"basic` bundles, enter:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:83 +msgid "" +"Docker is not started upon installation of the :command:`containers-" +"basic` bundle. To start Docker, enter:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:90 +msgid "" +"To ensure that Kubernetes is correctly installed and configured, follow " +"the instructions in :ref:`kubernetes`." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:94 +msgid "Version compatibility" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:96 +msgid "We validated these steps against the following software package versions:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:98 +msgid "|CL| 26240 (Minimum supported version)" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:99 +msgid "Docker 18.06.1" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:100 +msgid "Kubernetes 1.11.3" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:101 +msgid "Go 1.11.12" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:106 +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 tutorial 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 "" + +#: ../../tutorials/dlrs/dlrs.rst:109 +msgid "TensorFlow single and multi-node benchmarks" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:111 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:118 +msgid "" +"Performance test results for the Deep Learning Reference Stack and for " +"this tutorial were obtained using `runc` as the runtime." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:122 +msgid "" +"Download either the `Eigen`_ or the `Intel MKL-DNN`_ Docker image from " +"`Docker Hub`_." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:125 ../../tutorials/dlrs/dlrs.rst:167 +msgid "Run the image with Docker:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:134 ../../tutorials/dlrs/dlrs.rst:175 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:138 +msgid "Clone the benchmark repository in the container:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:144 ../../tutorials/dlrs/dlrs.rst:185 +msgid "Execute the benchmark script:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:152 +msgid "" +"You can replace the model with one of your choice supported by the " +"TensorFlow benchmarks." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:155 +msgid "" +"If you are using an FP32 based model, it can be converted to an int8 " +"model using `Intel® quantization tools`_." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:159 +msgid "PyTorch single and multi-node benchmarks" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:161 +msgid "" +"This section describes running the `PyTorch benchmarks`_ for Caffe2 in " +"single node." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:164 +msgid "" +"Download either the `PyTorch with OpenBLAS`_ or the `PyTorch with Intel " +"MKL-DNN`_ Docker image from `Docker Hub`_." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:179 +msgid "Clone the benchmark repository:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:195 +msgid "Kubeflow multi-node benchmarks" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:197 +msgid "" +"The benchmark workload runs in a Kubernetes cluster. The tutorial uses " +"`Kubeflow`_ for the Machine Learning workload deployment on three nodes." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:202 +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 tutorial." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:206 +msgid "Kubernetes setup" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:208 +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`_." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:213 +msgid "Kubernetes networking" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:215 +msgid "" +"We used `flannel`_ as the network provider for these tests. If you prefer" +" a different network layer, refer to the Kubernetes `networking " +"documentation`_ for setup." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:220 +msgid "Kubectl" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:222 +msgid "" +"You can use kubectl to run commands against your Kubernetes cluster. " +"Refer to the `kubectl overview`_ 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 "" + +#: ../../tutorials/dlrs/dlrs.rst:227 +msgid "Copy this example.yaml script to your system:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:244 +msgid "Execute the script with kubectl:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:250 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:254 +msgid "Images" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:256 +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 tutorial uses Kubeflow v0.4.0, and cannot " +"guarantee results if you use a different version." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:260 +msgid "From the Docker image, run the following:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:269 +msgid "Your entry point becomes: :file:`/opt/launcher.py`." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:271 +msgid "This builds an image that can be consumed directly by TFJob from Kubeflow." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:274 +msgid "ksonnet\\*" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:276 +msgid "" +"Kubeflow uses ksonnet\\* to manage deployments, so you must install it " +"before setting up Kubeflow." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:279 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:283 +msgid "On |CL|, follow these steps:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:294 +msgid "" +"After the ksonnet installation is complete, ensure that binary `ks` is " +"accessible across the environment." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:298 +msgid "Kubeflow" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:300 +msgid "" +"Once you have Kubernetes running on your nodes, set up `Kubeflow`_ by " +"following these instructions from the `quick start guide`_." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:318 +msgid "Next, deploy the primary package for our purposes: tf-job-operator." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:328 +msgid "" +"This creates the CustomResourceDefinition (CRD) endpoint to launch a " +"TFJob." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:331 +msgid "Run a TFJob" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:333 +msgid "Select this link for the `ksonnet registries for deploying TFJobs`_." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:335 +msgid "Install the TFJob components as follows:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:343 +msgid "Export the image name to use for the deployment:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:351 +msgid "Replace with the image name you specified in previous steps." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:353 +msgid "" +"Generate Kubernetes manifests for the workloads and apply them using " +"these commands:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:363 +msgid "This replicates and deploys three test setups in your Kubernetes cluster." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:366 +msgid "Results of running this tutorial" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:368 +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 from the Kubernetes community." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:375 +msgid "Use Jupyter Notebook" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:377 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:385 +msgid "" +"After you start the container, launch the Jupyter Notebook. This command " +"is executed inside the container image." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:392 +msgid "" +"After the notebook has loaded, you will see output similar to the " +"following:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:400 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:408 +msgid "Your browser displays the following:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:414 +msgid "Figure 1: :guilabel:`Jupyter Notebook`" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:417 +msgid "" +"To create a new notebook, click :guilabel:`New` and select " +":guilabel:`Python 3`." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:423 +msgid "Figure 2: Create a new notebook" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:425 +msgid "A new, blank notebook is displayed, with a cell ready for input." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:432 +msgid "" +"To verify that PyTorch is working, copy the following snippet into the " +"blank cell, and run the cell." +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:446 +msgid "When you run the cell, your output will look something like this:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:452 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:457 +msgid "Uninstallation" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:459 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:461 +msgid "To stop the container, execute the following from your host system:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:463 +msgid "Find the container's ID" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:469 +msgid "This will result in output similar to the following:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:476 +msgid "" +"You can then use the ID or container name to stop the container. This " +"example uses the name \"oss\":" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:483 +msgid "Verify that the container is not running" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:490 +msgid "To delete the container from your system you need to know the Image ID:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:496 +msgid "This command results in output similar to the following:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:504 +msgid "To remove an image use the image ID:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:520 +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 "" + +#: ../../tutorials/dlrs/dlrs.rst:522 +msgid "Once you have removed the image, you can verify it has been deleted with:" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:530 +msgid "Related topics" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:532 +msgid "Deep Learning Reference Stack `V3.0 release announcement`_" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:533 +msgid "`TensorFlow benchmarks`_" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:534 +msgid "`PyTorch benchmarks`_" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:535 +msgid "`Kubeflow`_" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:536 +msgid ":ref:`kubernetes` tutorial" +msgstr "" + +#: ../../tutorials/dlrs/dlrs.rst:537 +msgid "`Jupyter Notebook`_" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/docker/docker.po b/locale/zh_CN/LC_MESSAGES/tutorials/docker/docker.po new file mode 100644 index 00000000..dcd04626 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/docker/docker.po @@ -0,0 +1,297 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/docker/docker.rst:4 +msgid "Run Docker\\* on |CL-ATTR|" +msgstr "" + +#: ../../tutorials/docker/docker.rst:6 +msgid "" +"|CL-ATTR| supports multiple containerization platforms, including a " +"Docker\\* solution. |CL| has many `unique features`_ including a minimal " +"default installation, which makes it compelling to use as a host for " +"container workloads, management, and orchestration." +msgstr "" + +#: ../../tutorials/docker/docker.rst:11 +msgid "This tutorial covers:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:18 +msgid "" +"This tutorial focuses on the installaton of the Docker ecosystem. If you " +"want to use |CL| as a Docker container image, refer to the official |CL| " +"container image `published on Docker* Hub " +"`_ and our guide to :ref:`custom-" +"clear-container`." +msgstr "" + +#: ../../tutorials/docker/docker.rst:25 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/docker/docker.rst:27 +msgid "" +"This tutorial assumes you have installed |CL| on your host system. For " +"detailed instructions on installing |CL| on a bare metal system, follow " +"the :ref:`bare metal installation instructions`." +msgstr "" + +#: ../../tutorials/docker/docker.rst:31 +msgid "" +"Before you install any new packages, update |CL| with the following " +"command:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:37 +msgid "Additionally, you should have:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:39 +msgid "A basic understanding of Linux and Docker." +msgstr "" + +#: ../../tutorials/docker/docker.rst:41 +msgid "" +"|CL| environment that has transparent network access to the Internet. If " +"you are behind a HTTP proxy server, in a corporate setting for example, " +"please refer to the `Docker proxy instructions`_ ." +msgstr "" + +#: ../../tutorials/docker/docker.rst:46 +msgid "Install the containers-basic bundle" +msgstr "" + +#: ../../tutorials/docker/docker.rst:48 +msgid "" +"Software in |CL| is offered in the form of `bundles`_ to provide a " +"complete function. The *containers-basic* provides all the required " +"software packages to run Docker images as containers." +msgstr "" + +#: ../../tutorials/docker/docker.rst:52 +msgid "" +"First, install the *containers-basic* bundle by running this " +":command:`swupd` command:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:59 +msgid "Start the Docker daemon through systemd manager by running this command:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:65 +msgid "" +"If you want Docker to start automatically on boot, enable the systemd " +"service by running this command:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:72 +msgid "" +"Finally, verify :command:`docker` has been installed by running this " +"command and checking the version output for both *client* and *server*:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:79 +msgid "" +"Congratulations! At this point, you have a working installation of Docker" +" on |CL|. You are ready to start using container images on your system." +msgstr "" + +#: ../../tutorials/docker/docker.rst:83 +msgid "Integration with Kata Containers (optional)" +msgstr "" + +#: ../../tutorials/docker/docker.rst:85 +msgid "" +"`Kata Containers`_, is an open source project aiming to increase security" +" of containers by using a hardware-backed virtual machine container " +"runtime rather than software namespace containers that are provided by " +"the standard Docker *runc* runtime." +msgstr "" + +#: ../../tutorials/docker/docker.rst:90 +msgid "" +"|CL| provides easy integration of the *kata-runtime* with Docker. More " +"information on installing and using the *kata-runtime* may be found at " +":ref:`kata`." +msgstr "" + +#: ../../tutorials/docker/docker.rst:96 +msgid "" +"The proceeding sections of this tutorial are standard to Docker setup and" +" configuration. If you are familiar with Docker basics, you do not need " +"to continue reading. The following sections are provided here for sake of" +" completeness." +msgstr "" + +#: ../../tutorials/docker/docker.rst:104 +msgid "Additional Docker configuration" +msgstr "" + +#: ../../tutorials/docker/docker.rst:106 +msgid "" +"Perform additional Docker daemon configuration via a configuration file " +"typically located at :file:`/etc/docker/daemon.json`. |CL| features a " +"`stateless system`_ so the configuration file :file:`daemon.json` does " +"*NOT* exist by default." +msgstr "" + +#: ../../tutorials/docker/docker.rst:111 +msgid "Create the :file:`daemon.json` by running this command:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:119 +msgid "" +"Refer to the `Docker documentation on daemon configuration`_ for the full" +" list of available configuration options and examples." +msgstr "" + +#: ../../tutorials/docker/docker.rst:122 +msgid "" +"For production systems, we follow Docker's recommendation to use the " +"`OverlayFS storage driver`_ `overlay2`, shown below:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:133 +msgid "" +"A testing version is found in `Docker Device Mapper storage driver`_. If " +"using this storage driver, a warning message may appear: \"usage of " +"loopback devices is strongly discouraged for production use\"." +msgstr "" + +#: ../../tutorials/docker/docker.rst:137 +msgid "Save and close :file:`daemon.json`." +msgstr "" + +#: ../../tutorials/docker/docker.rst:139 +msgid "" +"Once you've made any required changes, be sure to restart the Docker " +"daemon through systemd manager by running this command:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:147 +msgid "Pulling and running an image from Docker Hub" +msgstr "" + +#: ../../tutorials/docker/docker.rst:149 +msgid "" +"`Docker Hub`_ is a publically available container image repository which " +"comes preconfigured with Docker. In the example below we will pull and " +"run an the official Docker image for nginx, an open source reverse proxy " +"server." +msgstr "" + +#: ../../tutorials/docker/docker.rst:153 +msgid "" +"First, pull a container image from Docker Hub using the :command:`docker " +"pull` command. Download the latest nginx Docker container image by " +"running this command:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:161 +msgid "" +"Create and launch a new container using the :command:`docker run` " +"command. Launch a nginx container by running this command:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:170 +msgid "" +"Below is an explanation of switches used in the command above. For " +"detailed :command:`docker run` switches and syntax, refer to the `Docker " +"Documentation`_ ." +msgstr "" + +#: ../../tutorials/docker/docker.rst:174 +msgid "" +"The *--name* switch lets you provide a friendly name to target the " +"container for future operations" +msgstr "" + +#: ../../tutorials/docker/docker.rst:177 +msgid "The *-d* switch launches the container in the background" +msgstr "" + +#: ../../tutorials/docker/docker.rst:179 +msgid "" +"The *-p* switch allows the container's HTTP port (80) to be accessible " +"from the |CL| host on port 8080" +msgstr "" + +#: ../../tutorials/docker/docker.rst:182 +msgid "" +"You can access the Welcome to Nginx! splash page running in the container" +" by browsing to \\http://127.0.0.1:8080 or by running this " +":command:`curl` command from your |CL| machine:" +msgstr "" + +#: ../../tutorials/docker/docker.rst:190 +msgid "" +"Finally, stop and delete the nginx container by running the " +":command:`docker stop` and :command:`docker rm` commands." +msgstr "" + +#: ../../tutorials/docker/docker.rst:198 +msgid "" +"Congratulations! At this point, you have successfully pulled a nginx " +"container image from `Docker Hub`_ and have run an example container." +msgstr "" + +#: ../../tutorials/docker/docker.rst:202 +msgid "Creating a Docker swarm cluster" +msgstr "" + +#: ../../tutorials/docker/docker.rst:204 +msgid "Clusters of Docker hosts are referred to as *swarms*." +msgstr "" + +#: ../../tutorials/docker/docker.rst:206 +msgid "" +"The process in this tutorial can be repeated to install Docker on " +"multiple |CL| hosts with the intent to form a Docker swarm cluster." +msgstr "" + +#: ../../tutorials/docker/docker.rst:209 +msgid "" +"The `Docker documentation on swarm key concepts`_ and `Docker " +"documentation on creating a swarm`_ can be referenced for further " +"instructions on setting up a swarm." +msgstr "" + +#: ../../tutorials/docker/docker.rst:214 +msgid "Related topics" +msgstr "" + +#: ../../tutorials/docker/docker.rst:216 +msgid "`Docker Home`_" +msgstr "" + +#: ../../tutorials/docker/docker.rst:217 +msgid "`Docker Documentation`_" +msgstr "" + +#: ../../tutorials/docker/docker.rst:218 +msgid "`Docker Hub`_" +msgstr "" + +#: ../../tutorials/docker/docker.rst:219 +msgid "`Kata Containers`_" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/flatpak/flatpak.po b/locale/zh_CN/LC_MESSAGES/tutorials/flatpak/flatpak.po new file mode 100644 index 00000000..e4b094b6 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/flatpak/flatpak.po @@ -0,0 +1,117 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/flatpak/flatpak.rst:4 +msgid "Use Flatpak\\* to install applications on |CL-ATTR|" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:6 +msgid "" +"This tutorial provides all the required steps to install Flatpak as well " +"as downloading, installing, and running LibreOffice\\* on |CL-ATTR|." +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:9 +msgid "" +"Please visit the `Flatpak website`_ for more information about Flatpak " +"and how to use it. You can also `download it here`_." +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:13 +msgid "Before you begin" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:15 +msgid "" +"This tutorial assumes you have installed |CL| on your host system. For " +"detailed instructions on installing |CL| on a bare metal system, visit " +"our :ref:`bare metal installation guide `." +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:20 +msgid "Install Flatpak on your host system" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:22 +msgid "" +"Flatpak is included as part of the bundle `desktop`. To install the " +"application, log in to your user account and enter the following command:" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:30 +msgid "Install and run the LibreOffice Flatpak image" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:32 +msgid "" +"Application developers have the option to bundle their applications using" +" Flatpak to allow the installation of a single distribution of their " +"application on different distributions of Linux, including |CL|. Flatpak " +"provides a `list of applications`_ available through Flathub." +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:37 +msgid "|CL| enables the Flathub repository by default." +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:41 +msgid "Installing using gnome software" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:43 +msgid "" +"All you need to do is to launch `gnome software`, search for the " +"LibreOffice app, and click the install button." +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:49 +msgid "Figure 1: Installing LibreOffice using gnome-software" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:54 +msgid "Installing using the command line" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:56 +msgid "" +"Open the `gnome-terminal` and type the following command to install the " +"LibreOffice app." +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:79 +msgid "Launch LibreOffice" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:80 +msgid "" +"A new set of icons will appear in your Gnome applications list titled " +":guilabel:`LibreOffice.` To execute the application, highlight the " +"application and click on the :guilabel:`LibreOffice` icon. LibreOffice " +"will start normally." +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:87 +msgid "Figure 2: Select :guilabel:`LibreOffice` app" +msgstr "" + +#: ../../tutorials/flatpak/flatpak.rst:90 +msgid "Using the command line" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/fmv.po b/locale/zh_CN/LC_MESSAGES/tutorials/fmv.po new file mode 100644 index 00000000..63e9c1a6 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/fmv.po @@ -0,0 +1,180 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/fmv.rst:4 +msgid "Use the function multi-version patch generator" +msgstr "" + +#: ../../tutorials/fmv.rst:6 +msgid "" +"CPU architectures often gain interesting new instructions as they evolve " +"but application developers find it difficult to take advantage of those " +"instructions. The reluctance to lose backward-compatibility is one of the" +" main roadblocks slowing developers from using advancements in newer " +"computing architectures. :abbr:`FMV (Function Multi-Versioning)`, which " +"first appeared in `GCC`_ 4.8, is a way to have multiple implementations " +"of a function, each using a different architecture specialized " +"instruction-set extensions. GCC 6 introduces changes to FMV to make it " +"even easier to bring architecture- based optimizations to the application" +" code." +msgstr "" + +#: ../../tutorials/fmv.rst:16 +msgid "" +"In this tutorial we will use FMV on general code and on :abbr:`FFT (Fast " +"Fourier Transform)` library code. Upon completing the tutorial, you will " +"be able to use this technology on your code and use the libraries to " +"deploy architecture-based optimizations to your application code." +msgstr "" + +#: ../../tutorials/fmv.rst:22 +msgid "Install and configure a |CL| host on bare metal" +msgstr "" + +#: ../../tutorials/fmv.rst:23 +msgid "" +"First, follow our guide to :ref:`bare-metal-install-desktop`. Once the " +"bare metal installation and initial configuration are complete, add the " +"`desktop-dev` bundle to the system. `desktop-dev`: contains the necessary" +" development tools like GCC and Perl\\*." +msgstr "" + +#: ../../tutorials/fmv.rst:28 +msgid "" +"To install the bundles, run the following command in the :file:`$HOME` " +"directory:" +msgstr "" + +#: ../../tutorials/fmv.rst:36 +msgid "Detect loop vectorization candidates" +msgstr "" + +#: ../../tutorials/fmv.rst:38 +msgid "" +"Now, we need to detect the loop vectorization candidates to be cloned for" +" multiple platforms with FMV. As an example, we will use the following " +"simple C code:" +msgstr "" + +#: ../../tutorials/fmv.rst:67 +msgid "" +"Save the example code as :file:`example.c` in the current directory and " +"build with the following flags:" +msgstr "" + +#: ../../tutorials/fmv.rst:74 +msgid "The build generates the following output:" +msgstr "" + +#: ../../tutorials/fmv.rst:81 +msgid "The output shows that line 11 is a good candidate for vectorization:" +msgstr "" + +#: ../../tutorials/fmv.rst:89 +msgid "Generate the FMV patch" +msgstr "" + +#: ../../tutorials/fmv.rst:91 +msgid "" +"To generate the FMV patch with the `make-fmv-patch`_ project, we must " +"clone the project and generate a log file with the loop vectorized " +"information:" +msgstr "" + +#: ../../tutorials/fmv.rst:100 +msgid "To generate the patch files, execute:" +msgstr "" + +#: ../../tutorials/fmv.rst:106 +msgid "" +"The :file:`make-fmv-patch.pl` script takes two arguments: `` " +"and ``. Replace `` and `` with the " +"proper values and execute:" +msgstr "" + +#: ../../tutorials/fmv.rst:114 +msgid "The command generates the following :file:`example.c.patch` patch:" +msgstr "" + +#: ../../tutorials/fmv.rst:129 +msgid "" +"We recommend you use the :file:`make-fmv-patch` script to add the " +"attribute generating the target clones on the function `foo`. Thus, we " +"can have the following code:" +msgstr "" + +#: ../../tutorials/fmv.rst:158 +msgid "" +"Changing the value of the `$avx2` variable, we can change the target " +"clones when adding the patches or in the :file:`make-fmv-patch.pl` " +"script:" +msgstr "" + +#: ../../tutorials/fmv.rst:165 +msgid "" +"Compile the code again with FMV and add the option to analyze the " +"`objdump` log:" +msgstr "" + +#: ../../tutorials/fmv.rst:173 +msgid "You can see the multiple clones of the `foo` function:" +msgstr "" + +#: ../../tutorials/fmv.rst:181 +msgid "" +"The cloned functions use AVX2 registers and vectorized instructions. To " +"verify, enter the following commands:" +msgstr "" + +#: ../../tutorials/fmv.rst:190 +msgid "FTT project example" +msgstr "" + +#: ../../tutorials/fmv.rst:192 +msgid "" +"To follow the same approach with a package like FFT, we must use the " +"`-fopt-info-vec` flag to get a build log file similar to:" +msgstr "" + +#: ../../tutorials/fmv.rst:210 +msgid "" +"For example, the :file:`fftw-3.3.6-pl2/tools/fftw-wisdom.c.patch` file " +"generates the following patches:" +msgstr "" + +#: ../../tutorials/fmv.rst:262 +msgid "" +"With these patches, we can select where to apply the FMV technology " +"making bringing architecture-based optimizations to application code even" +" easier." +msgstr "" + +#: ../../tutorials/fmv.rst:265 +msgid "**Congratulations!**" +msgstr "" + +#: ../../tutorials/fmv.rst:267 +msgid "" +"You have successfully installed an FMV development environment on |CL|. " +"Furthermore, you used cutting edge compiler technology to improve the " +"performance of your application based on Intel Architecture technology " +"and profiling of the specific execution of your application." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/greengrass.po b/locale/zh_CN/LC_MESSAGES/tutorials/greengrass.po new file mode 100644 index 00000000..d73f9c53 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/greengrass.po @@ -0,0 +1,658 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/greengrass.rst:4 +msgid "Enable AWS Greengrass\\* and OpenVINO™ toolkit" +msgstr "" + +#: ../../tutorials/greengrass.rst:6 +msgid "" +"Hardware accelerated Function-as-a-Service (FaaS) enables cloud " +"developers to deploy inference functionalities [1] on Intel® IoT edge " +"devices with accelerators (CPU, Integrated GPU, Intel® FPGA, and Intel® " +"Movidius™ technology). These functions provide a great developer " +"experience and seamless migration of visual analytics from cloud to edge " +"in a secure manner using a containerized environment. Hardware-" +"accelerated FaaS provides the best-in-class performance by accessing " +"optimized deep learning libraries on Intel® IoT edge devices with " +"accelerators." +msgstr "" + +#: ../../tutorials/greengrass.rst:15 +msgid "This tutorial demonstrates how to:" +msgstr "" + +#: ../../tutorials/greengrass.rst:17 +msgid "Set up the Intel® edge device with |CL-ATTR|" +msgstr "" + +#: ../../tutorials/greengrass.rst:18 +msgid "" +"Install the OpenVINO™ toolkit and Amazon Web Services\\* (AWS\\*) " +"Greengrass\\* software stacks" +msgstr "" + +#: ../../tutorials/greengrass.rst:20 +msgid "" +"Use AWS Greengrass\\* and AWS Lambda\\* to deploy the FaaS samples from " +"the cloud" +msgstr "" + +#: ../../tutorials/greengrass.rst:22 +msgid "Refer to the following topics:" +msgstr "" + +#: ../../tutorials/greengrass.rst:29 +msgid "Supported platforms" +msgstr "" + +#: ../../tutorials/greengrass.rst:31 +msgid "Operating System: |CL| latest release" +msgstr "" + +#: ../../tutorials/greengrass.rst:32 +msgid "" +"Hardware: Intel® core platforms (This tutorial supports inference " +"on CPU only.)" +msgstr "" + +#: ../../tutorials/greengrass.rst:35 +msgid "Sample description" +msgstr "" + +#: ../../tutorials/greengrass.rst:37 +msgid "" +"The AWS Greengrass samples are located at `Edge-Analytics-FaaS`_. This " +"tutorial uses the 1.0 version of the source code." +msgstr "" + +#: ../../tutorials/greengrass.rst:40 +msgid "|CL| provides the following AWS Greengrass samples:" +msgstr "" + +#: ../../tutorials/greengrass.rst:42 +msgid "`greengrass_classification_sample.py`_" +msgstr "" + +#: ../../tutorials/greengrass.rst:44 +msgid "" +"This AWS Greengrass sample classifies a video stream using classification" +" networks such as AlexNet and GoogLeNet and publishes top-10 results on " +"AWS\\* IoT Cloud every second." +msgstr "" + +#: ../../tutorials/greengrass.rst:48 +msgid "`greengrass_object_detection_sample_ssd.py`_" +msgstr "" + +#: ../../tutorials/greengrass.rst:50 +msgid "" +"This AWS Greengrass sample detects objects in a video stream and " +"classifies them using single-shot multi-box detection (SSD) networks such" +" as SSD Squeezenet, SSD Mobilenet, and SSD300. This sample publishes " +"detection outputs such as class label, class confidence, and bounding box" +" coordinates on AWS IoT Cloud every second." +msgstr "" + +#: ../../tutorials/greengrass.rst:58 +msgid "Install the OS on the edge device" +msgstr "" + +#: ../../tutorials/greengrass.rst:60 +msgid "" +"Start with a clean installation of |CL| on a new system, using the :ref" +":`bare-metal-install-desktop`, found in :ref:`get-started`." +msgstr "" + +#: ../../tutorials/greengrass.rst:64 +msgid "Create user accounts" +msgstr "" + +#: ../../tutorials/greengrass.rst:66 +msgid "" +"After |CL| is installed, create two user accounts. Create an " +"administrative user in |CL| and create a user account for the Greengrass " +"services to use ( see Greengrass user below)." +msgstr "" + +#: ../../tutorials/greengrass.rst:70 +msgid "" +"Create a new user and set a password for that user. Enter the following " +"commands as ``root``:" +msgstr "" + +#: ../../tutorials/greengrass.rst:78 +msgid "" +"Next, enable the :command:`sudo` command for your new ````. Add " +"```` to the *wheel* group:" +msgstr "" + +#: ../../tutorials/greengrass.rst:85 +msgid "Create a :file:`/etc/fstab` file." +msgstr "" + +#: ../../tutorials/greengrass.rst:93 +msgid "" +"By default, |CL| does not create an :file:`/etc/fstab` file. You must " +"create this file before the Greengrass service runs." +msgstr "" + +#: ../../tutorials/greengrass.rst:97 +msgid "Add required bundles" +msgstr "" + +#: ../../tutorials/greengrass.rst:99 +msgid "" +"Use the :command:`swupd` software updater utility to add the prerequisite" +" bundles for the OpenVINO software stack:" +msgstr "" + +#: ../../tutorials/greengrass.rst:108 +msgid "Learn more about how to :ref:`swupd-guide`." +msgstr "" + +#: ../../tutorials/greengrass.rst:110 +msgid "" +"The :command:`computer-vision-basic` bundle installs the OpenVINO™ " +"toolkit, and the sample models optimized for Intel® edge platforms." +msgstr "" + +#: ../../tutorials/greengrass.rst:114 +msgid "Convert deep learning models" +msgstr "" + +#: ../../tutorials/greengrass.rst:117 +msgid "Locate sample models" +msgstr "" + +#: ../../tutorials/greengrass.rst:119 +msgid "" +"There are two types of provided models that can be used in conjunction " +"with AWS Greengrass for this tutorial: classification or object " +"detection." +msgstr "" + +#: ../../tutorials/greengrass.rst:122 +msgid "" +"To complete this tutorial using an image classification model, download " +"the BVLC AlexNet model files `bvlc_alexnet.caffemodel`_ and " +"`deploy.prototxt`_ to the default model_location at " +":file:`/usr/share/openvino/models`. Any custom pre-trained classification" +" models can be used with the classification sample." +msgstr "" + +#: ../../tutorials/greengrass.rst:128 +msgid "" +"For object detection, the sample models optimized for Intel® edge " +"platforms are included with the computer-vision-basic bundle installation" +" at :file:`/usr/share/openvino/models`. These models are provided as an " +"example; however, you may also use a custom SSD model with the Greengrass" +" object detection sample." +msgstr "" + +#: ../../tutorials/greengrass.rst:134 +msgid "Run model optimizer" +msgstr "" + +#: ../../tutorials/greengrass.rst:136 +msgid "" +"Follow these instructions for `converting deep learning models to " +"Intermediate Representation using Model Optimizer`_. To optimize either " +"of the sample models described above, run one of the following commands." +msgstr "" + +#: ../../tutorials/greengrass.rst:138 +msgid "For classification using BVLC AlexNet model:" +msgstr "" + +#: ../../tutorials/greengrass.rst:147 +msgid "For object detection using SqueezeNetSSD-5Class model:" +msgstr "" + +#: ../../tutorials/greengrass.rst:156 +msgid "In these examples:" +msgstr "" + +#: ../../tutorials/greengrass.rst:158 +msgid "```` is :file:`/usr/share/openvino/models`." +msgstr "" + +#: ../../tutorials/greengrass.rst:160 +msgid "```` is FP32 or FP16, depending on target device." +msgstr "" + +#: ../../tutorials/greengrass.rst:162 +msgid "" +"```` is the directory where the Intermediate Representation " +"(IR) is stored. IR contains .xml format corresponding to the network " +"structure and .bin format corresponding to weights. This .xml file should" +" be passed to :command:``." +msgstr "" + +#: ../../tutorials/greengrass.rst:167 +msgid "" +"In the BVLC AlexNet model, the prototxt defines the input shape with " +"batch size 10 by default. In order to use any other batch size, the " +"entire input shape must be provided as an argument to the model " +"optimizer. For example, to use batch size 1, you must provide: " +"``--input_shape [1,3,227,227]``" +msgstr "" + +#: ../../tutorials/greengrass.rst:175 +msgid "Configure AWS Greengrass group" +msgstr "" + +#: ../../tutorials/greengrass.rst:177 +msgid "" +"For each Intel® edge platform, you must create a new AWS Greengrass group" +" and install AWS Greengrass core software to establish the connection " +"between cloud and edge." +msgstr "" + +#: ../../tutorials/greengrass.rst:181 +msgid "" +"To create an AWS Greengrass group, follow the instructions in `Configure " +"AWS IoT Greengrass on AWS IoT`_." +msgstr "" + +#: ../../tutorials/greengrass.rst:184 +msgid "" +"To install and configure AWS Greengrass core on edge platform, follow the" +" instructions in `Start AWS Greengrass on the Core Device`_. In step " +"8(b), download the x86_64 Ubuntu\\* configuration of the AWS Greengrass " +"core software." +msgstr "" + +#: ../../tutorials/greengrass.rst:191 +msgid "" +"You do not need to run the :file:`cgroupfs-mount.sh` script in step #6 of" +" Module 1 of the `AWS Greengrass developer guide`_ because this is " +"enabled already in |CL|." +msgstr "" + +#: ../../tutorials/greengrass.rst:195 +msgid "" +"Be sure to download both the security resources and the AWS Greengrass " +"core software." +msgstr "" + +#: ../../tutorials/greengrass.rst:200 +msgid "Security certificates are linked to your AWS account." +msgstr "" + +#: ../../tutorials/greengrass.rst:204 +msgid "Create and package Lambda function" +msgstr "" + +#: ../../tutorials/greengrass.rst:206 +msgid "" +"Complete steps 1-4 of the AWS Greengrass tutorial at `Create and Package " +"a Lambda Function`_." +msgstr "" + +#: ../../tutorials/greengrass.rst:210 +msgid "" +"This creates the tarball needed to create the AWS Greengrass environment " +"on the edge device." +msgstr "" + +#: ../../tutorials/greengrass.rst:214 +msgid "" +"In step 5, replace :file:`greengrassHelloWorld.py` with the " +"classification or object detection Greengrass sample from `Edge-" +"Analytics-Faas`_:" +msgstr "" + +#: ../../tutorials/greengrass.rst:217 +msgid "Classification: `greengrass_classification_sample.py`_" +msgstr "" + +#: ../../tutorials/greengrass.rst:219 +msgid "Object Detection: `greengrass_object_detection_sample_ssd.py`_" +msgstr "" + +#: ../../tutorials/greengrass.rst:221 +msgid "" +"Zip the selected Greengrass sample with the extracted Greengrass SDK " +"folders from the previous step into " +":file:`greengrass_sample_python_lambda.zip`." +msgstr "" + +#: ../../tutorials/greengrass.rst:224 +msgid "The zip should contain:" +msgstr "" + +#: ../../tutorials/greengrass.rst:226 +msgid "greengrasssdk" +msgstr "" + +#: ../../tutorials/greengrass.rst:228 +msgid "greengrass classification or object detection sample" +msgstr "" + +#: ../../tutorials/greengrass.rst:230 +msgid "For example:" +msgstr "" + +#: ../../tutorials/greengrass.rst:237 +msgid "" +"Return to the AWS documentation section called `Create and Package a " +"Lambda Function`_ and complete the procedure." +msgstr "" + +#: ../../tutorials/greengrass.rst:242 +msgid "" +"In step 9(a) of the AWS documentation, while uploading the zip file, make" +" sure to name the handler to one of the following, depending on the AWS " +"Greengrass sample you are using:" +msgstr "" + +#: ../../tutorials/greengrass.rst:246 +msgid "greengrass_object_detection_sample_ssd.function_handler" +msgstr "" + +#: ../../tutorials/greengrass.rst:247 +msgid "greengrass_classification_sample.function_handler" +msgstr "" + +#: ../../tutorials/greengrass.rst:251 +msgid "Configure Lambda function" +msgstr "" + +#: ../../tutorials/greengrass.rst:253 +msgid "" +"After creating the Greengrass group and the Lambda function, start " +"configuring the Lambda function for AWS Greengrass." +msgstr "" + +#: ../../tutorials/greengrass.rst:256 +msgid "" +"Follow steps 1-8 in `Configure the Lambda Function for AWS IoT " +"Greengrass`_ in the AWS documentation." +msgstr "" + +#: ../../tutorials/greengrass.rst:259 +msgid "" +"In addition to the details mentioned in step 8, change the Memory limit " +"to 2048 MB to accommodate large input video streams." +msgstr "" + +#: ../../tutorials/greengrass.rst:262 +msgid "" +"Add the following environment variables as key-value pairs when editing " +"the Lambda configuration and click on update:" +msgstr "" + +#: ../../tutorials/greengrass.rst:265 +msgid "**Table 1. Environment variables: Lambda configuration**" +msgstr "" + +#: ../../tutorials/greengrass.rst:269 +msgid "Key" +msgstr "" + +#: ../../tutorials/greengrass.rst:270 +msgid "Value" +msgstr "" + +#: ../../tutorials/greengrass.rst:271 +msgid "PARAM_MODEL_XML" +msgstr "" + +#: ../../tutorials/greengrass.rst:272 +msgid "" +"/, where is user specified and contains " +"IR.xml, the Intermediate Representation file from Intel® Model Optimizer." +" For this tutorial, should be set to " +"'/usr/share/openvino/models' or one of its subdirectories." +msgstr "" + +#: ../../tutorials/greengrass.rst:276 +msgid "PARAM_INPUT_SOURCE" +msgstr "" + +#: ../../tutorials/greengrass.rst:277 +msgid "/input.webm to be specified by user. Holds both input and" +msgstr "" + +#: ../../tutorials/greengrass.rst:278 +msgid "output data. For webcam, set PARAM_INPUT_SOURCE to ‘/dev/video0’" +msgstr "" + +#: ../../tutorials/greengrass.rst:279 +msgid "PARAM_DEVICE" +msgstr "" + +#: ../../tutorials/greengrass.rst:280 +msgid "\"CPU\"" +msgstr "" + +#: ../../tutorials/greengrass.rst:281 +msgid "PARAM_CPU_EXTENSION_PATH" +msgstr "" + +#: ../../tutorials/greengrass.rst:282 +msgid "/usr/lib64/libcpu_extension.so" +msgstr "" + +#: ../../tutorials/greengrass.rst:283 +msgid "PARAM_OUTPUT_DIRECTORY" +msgstr "" + +#: ../../tutorials/greengrass.rst:284 +msgid " to be specified by user. Holds both input and output data" +msgstr "" + +#: ../../tutorials/greengrass.rst:286 +msgid "PARAM_NUM_TOP_RESULTS" +msgstr "" + +#: ../../tutorials/greengrass.rst:287 +msgid "" +"User specified for classification sample. (e.g. 1 for top-1 result, 5 for" +" top-5 results)" +msgstr "" + +#: ../../tutorials/greengrass.rst:290 +msgid "" +"Add subscription to subscribe, or publish messages from AWS Greengrass " +"Lambda function by completing the procedure in `Configure the Lambda " +"Function for AWS IoT Greengrass`_." +msgstr "" + +#: ../../tutorials/greengrass.rst:295 +msgid "" +"The optional topic filter field is the topic mentioned inside the Lambda " +"function. In this tutorial, sample topics include the following: " +":command:`openvino/ssd` or :command:`openvino/classification`" +msgstr "" + +#: ../../tutorials/greengrass.rst:300 +msgid "Add local resources" +msgstr "" + +#: ../../tutorials/greengrass.rst:302 +msgid "" +"Refer to the AWS documentation for details about `local resources and " +"access privileges`_." +msgstr "" + +#: ../../tutorials/greengrass.rst:304 +msgid "The following table describes the local resources needed for the CPU:" +msgstr "" + +#: ../../tutorials/greengrass.rst:306 +msgid "**Local resources**" +msgstr "" + +#: ../../tutorials/greengrass.rst:310 +msgid "Name" +msgstr "" + +#: ../../tutorials/greengrass.rst:311 +msgid "Resource type" +msgstr "" + +#: ../../tutorials/greengrass.rst:312 +msgid "Local path" +msgstr "" + +#: ../../tutorials/greengrass.rst:313 +msgid "Access" +msgstr "" + +#: ../../tutorials/greengrass.rst:315 +msgid "ModelDir" +msgstr "" + +#: ../../tutorials/greengrass.rst:316 ../../tutorials/greengrass.rst:326 +msgid "Volume" +msgstr "" + +#: ../../tutorials/greengrass.rst:317 +msgid " to be specified by user" +msgstr "" + +#: ../../tutorials/greengrass.rst:318 ../../tutorials/greengrass.rst:323 +msgid "Read-Only" +msgstr "" + +#: ../../tutorials/greengrass.rst:320 +msgid "Webcam" +msgstr "" + +#: ../../tutorials/greengrass.rst:321 +msgid "Device" +msgstr "" + +#: ../../tutorials/greengrass.rst:322 +msgid "/dev/video0" +msgstr "" + +#: ../../tutorials/greengrass.rst:325 +msgid "DataDir" +msgstr "" + +#: ../../tutorials/greengrass.rst:327 +msgid " to be specified by user. Holds both input and output data." +msgstr "" + +#: ../../tutorials/greengrass.rst:329 +msgid "Read and Write" +msgstr "" + +#: ../../tutorials/greengrass.rst:332 +msgid "Deploy Lambda function" +msgstr "" + +#: ../../tutorials/greengrass.rst:334 +msgid "" +"Refer to the AWS documentation for instructions on how to `deploy the " +"lambda function to AWS Greengrass core device`_. Select *Deployments* on " +"the group page and follow the instructions." +msgstr "" + +#: ../../tutorials/greengrass.rst:339 +msgid "Output consumption" +msgstr "" + +#: ../../tutorials/greengrass.rst:341 +msgid "" +"There are four options available for output consumption. These options " +"are used to report, stream, upload, or store inference output at an " +"interval defined by the variable :command:`reporting_interval` in the AWS" +" Greengrass samples." +msgstr "" + +#: ../../tutorials/greengrass.rst:345 +msgid "IoT cloud output:" +msgstr "" + +#: ../../tutorials/greengrass.rst:347 +msgid "" +"This option is enabled by default in the AWS Greengrass samples using the" +" :command:`enable_iot_cloud_output` variable. You can use it to verify " +"the lambda running on the edge device. It enables publishing messages to " +"IoT cloud using the subscription topic specified in the lambda. (For " +"example, topics may include :command:`openvino/classification` for " +"classification and :command:`openvino/ssd` for object detection samples.)" +" For classification, top-1 result with class label are published to IoT " +"cloud. For SSD object detection, detection results such as bounding box " +"coordinates of objects, class label, and class confidence are published." +msgstr "" + +#: ../../tutorials/greengrass.rst:357 +msgid "Follow the instructions here to `view the output on IoT cloud`_." +msgstr "" + +#: ../../tutorials/greengrass.rst:359 +msgid "Kinesis streaming:" +msgstr "" + +#: ../../tutorials/greengrass.rst:361 +msgid "" +"This option enables inference output to be streamed from the edge device " +"to cloud using Kinesis [3] streams when :command:`enable_kinesis_output` " +"is set to True. The edge devices act as data producers and continually " +"push processed data to the cloud. You must set up and specify Kinesis " +"stream name, Kinesis shard, and AWS region in the AWS Greengrass samples." +msgstr "" + +#: ../../tutorials/greengrass.rst:368 +msgid "Cloud storage using AWS S3 bucket:" +msgstr "" + +#: ../../tutorials/greengrass.rst:370 +msgid "" +"When the :command:`enable_s3_jpeg_output` variable is set to True, it " +"enables uploading and storing processed frames (in jpeg format) in an AWS" +" S3 bucket. You must set up and specify the S3 bucket name in the AWS " +"Greengrass samples to store the JPEG images. The images are named using " +"the timestamp and uploaded to S3." +msgstr "" + +#: ../../tutorials/greengrass.rst:376 +msgid "Local storage:" +msgstr "" + +#: ../../tutorials/greengrass.rst:378 +msgid "" +"When the :command:`enable_s3_jpeg_output` variable is set to True, it " +"enables storing processed frames (in jpeg format) on the edge device. The" +" images are named using the timestamp and stored in a directory specified" +" by :command:`PARAM_OUTPUT_DIRECTORY`." +msgstr "" + +#: ../../tutorials/greengrass.rst:384 +msgid "References" +msgstr "" + +#: ../../tutorials/greengrass.rst:386 +msgid "AWS Greengrass: https://aws.amazon.com/greengrass/" +msgstr "" + +#: ../../tutorials/greengrass.rst:387 +msgid "AWS Lambda: https://aws.amazon.com/lambda/" +msgstr "" + +#: ../../tutorials/greengrass.rst:388 +msgid "AWS Kinesis: https://aws.amazon.com/kinesis/" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/hadoop.po b/locale/zh_CN/LC_MESSAGES/tutorials/hadoop.po new file mode 100644 index 00000000..bb1ad7ee --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/hadoop.po @@ -0,0 +1,231 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/hadoop.rst:4 +msgid "Set up a single node cluster with Hadoop\\*" +msgstr "" + +#: ../../tutorials/hadoop.rst:6 +msgid "" +"This tutorial walks you through the process of installing, configuring, " +"and running Apache\\* Hadoop on |CL-ATTR|. The Apache Hadoop software " +"library is a framework for distributed processing of large data sets " +"across clusters of computers using simple programming models. It is " +"designed to scale up from single servers to thousands of machines, with " +"each machine offering local computation and storage." +msgstr "" + +#: ../../tutorials/hadoop.rst:14 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/hadoop.rst:16 +msgid "" +"Before following this tutorial, you should follow the :ref:`bare-metal-" +"install-desktop` to ensure you have installed |CL|." +msgstr "" + +#: ../../tutorials/hadoop.rst:19 +msgid "" +"Before you install any new packages, update |CL| with the following " +"command:" +msgstr "" + +#: ../../tutorials/hadoop.rst:25 +msgid "" +"For the purposes of this tutorial, we will install Hadoop in a single " +"machine running both the master and slave daemons." +msgstr "" + +#: ../../tutorials/hadoop.rst:29 +msgid "Install Apache Hadoop" +msgstr "" + +#: ../../tutorials/hadoop.rst:31 +msgid "" +"Apache Hadoop is included in the `big-data-basic` bundle. To install the " +"framework, enter the following command:" +msgstr "" + +#: ../../tutorials/hadoop.rst:39 +msgid "Configure Apache Hadoop" +msgstr "" + +#: ../../tutorials/hadoop.rst:41 +msgid "To create the configuration directory, enter the following command:" +msgstr "" + +#: ../../tutorials/hadoop.rst:47 +msgid "" +"Copy the defaults from :file:`/usr/share/defaults/hadoop` to " +":file:`/etc/hadoop` with the following command:" +msgstr "" + +#: ../../tutorials/hadoop.rst:54 +msgid "" +"Since |CL| is a stateless system, you should never modify the files under" +" the :file:`/usr/share/defaults` directory. The software updater will " +"overwrite those files." +msgstr "" + +#: ../../tutorials/hadoop.rst:58 +msgid "" +"Once all the configuration files are in :file:`/etc/hadoop`, we must edit" +" them to fit our needs. The `NameNode` server is the master server. It " +"manages the namespace of the files system and regulates the clients' " +"access to files. The first file we edit, :file:`/etc/hadoop/core-" +"site.xml`, informs the Hadoop daemon where `NameNode` is running." +msgstr "" + +#: ../../tutorials/hadoop.rst:64 +msgid "" +"In this tutorial, our `NameNode` runs in our `localhost`. Follow these " +"steps to set it up correctly:" +msgstr "" + +#: ../../tutorials/hadoop.rst:67 +msgid "" +"Open the :file:`/etc/hadoop/core-site.xml` file using the editor of your " +"choice and modify the file as follows:" +msgstr "" + +#: ../../tutorials/hadoop.rst:81 +msgid "" +"Edit the :file:`/etc/hadoop/hdfs-site.xml` file. This file configures the" +" :abbr:`HDFS (Hadoop Distributed File System)` daemons. This " +"configuration includes the list of permitted and excluded data nodes and " +"the size of said blocks. In this example, we are setting the number of " +"block replication to 1 from the default of 3 as follows:" +msgstr "" + +#: ../../tutorials/hadoop.rst:103 +msgid "" +"Edit the :file:`/etc/hadoop/mapred-site.xml` file. This file configures " +"all daemons related to `MapReduce`: `JobTracker` and `TaskTrackers`. With" +" `MapReduce`, Hadoop can process big amounts of data in multiple systems." +" In our example, we set :abbr:`YARN (Yet Another Resource Manager)` as " +"our runtime framework for executing `MapReduce` jobs as follows:" +msgstr "" + +#: ../../tutorials/hadoop.rst:121 +msgid "" +"Edit the :file:`/etc/hadoop/yarn-site.xml` file. This file configures all" +" daemons related to `YARN`: `ResourceManager` and `NodeManager`. In our " +"example, we implement the `mapreduce_shuffle` service, which is the " +"default as follows:" +msgstr "" + +#: ../../tutorials/hadoop.rst:142 +msgid "Configure your SSH key" +msgstr "" + +#: ../../tutorials/hadoop.rst:144 +msgid "Create a SSH key. If you already have one, skip this step." +msgstr "" + +#: ../../tutorials/hadoop.rst:151 +msgid "Copy the key to your authorized keys." +msgstr "" + +#: ../../tutorials/hadoop.rst:157 +msgid "" +"Log into the localhost. If no password prompt appears, you are ready to " +"run the Hadoop daemons." +msgstr "" + +#: ../../tutorials/hadoop.rst:165 +msgid "Run the Hadoop daemons" +msgstr "" + +#: ../../tutorials/hadoop.rst:167 +msgid "" +"With all the configuration files properly edited, we are ready to start " +"the daemons." +msgstr "" + +#: ../../tutorials/hadoop.rst:170 +msgid "" +"When we format the `NameNode` server, it formats the meta-data related to" +" data nodes. Thus, all the information on the data nodes is lost and the " +"nodes can be reused for new data." +msgstr "" + +#: ../../tutorials/hadoop.rst:174 +msgid "Format the `NameNode` server with the following command:" +msgstr "" + +#: ../../tutorials/hadoop.rst:180 +msgid "Start the DFS in `NameNode` and `DataNodes` with the following command:" +msgstr "" + +#: ../../tutorials/hadoop.rst:186 ../../tutorials/hadoop.rst:211 +msgid "The console output should be similar to:" +msgstr "" + +#: ../../tutorials/hadoop.rst:196 +msgid "Enter `yes` to continue." +msgstr "" + +#: ../../tutorials/hadoop.rst:198 +msgid "" +"Start the `YARN` daemons `ResourceManager` and `NodeManager` with the " +"following command:" +msgstr "" + +#: ../../tutorials/hadoop.rst:205 +msgid "Ensure everything is running as expected with the following command:" +msgstr "" + +#: ../../tutorials/hadoop.rst:223 +msgid "Run the MapReduce wordcount example" +msgstr "" + +#: ../../tutorials/hadoop.rst:225 +msgid "Create the input directory." +msgstr "" + +#: ../../tutorials/hadoop.rst:231 +msgid "Copy a file from the local file system to the HDFS." +msgstr "" + +#: ../../tutorials/hadoop.rst:237 +msgid "Run the `wordcount` example." +msgstr "" + +#: ../../tutorials/hadoop.rst:243 +msgid "" +"Read output file \"part-r-00000\". This file contains the number of times" +" each word appears in the file." +msgstr "" + +#: ../../tutorials/hadoop.rst:250 +msgid "**Congratulations!**" +msgstr "" + +#: ../../tutorials/hadoop.rst:252 +msgid "" +"You successfully installed and setup a single node Hadoop cluster. " +"Additionally, you ran a simple wordcount example." +msgstr "" + +#: ../../tutorials/hadoop.rst:255 +msgid "Your single node Hadoop cluster is up and running!" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/kata.po b/locale/zh_CN/LC_MESSAGES/tutorials/kata.po new file mode 100644 index 00000000..faaa3d83 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/kata.po @@ -0,0 +1,143 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/kata.rst:4 +msgid "Install Kata Containers\\*" +msgstr "" + +#: ../../tutorials/kata.rst:6 +msgid "" +"This tutorial describes how to install, configure, and run `Kata " +"Containers`_ on |CL-ATTR|. Kata Containers is an open source project " +"developing a lightweight implementation of :abbr:`VMs (Virtual Machines)`" +" that offer the speed of containers and the security of VMs." +msgstr "" + +#: ../../tutorials/kata.rst:12 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/kata.rst:14 +msgid "" +"This tutorial assumes you have installed |CL| on your host system. For " +"detailed instructions on installing |CL| on a bare metal system, follow " +"the :ref:`bare metal installation tutorial`." +msgstr "" + +#: ../../tutorials/kata.rst:18 +msgid "" +"If you have Clear Containers installed on your |CL| system, then follow " +"the :ref:`migrate Clear Containers to Kata Containers " +"tutorial`." +msgstr "" + +#: ../../tutorials/kata.rst:21 +msgid "" +"Before you install any new packages, update |CL| with the following " +"command:" +msgstr "" + +#: ../../tutorials/kata.rst:28 +msgid "Install Kata Containers" +msgstr "" + +#: ../../tutorials/kata.rst:30 +msgid "" +"Kata Containers is included in the :file:`containers-virt` bundle. To " +"install the framework, enter the following command:" +msgstr "" + +#: ../../tutorials/kata.rst:37 +msgid "Restart the Docker\\* and Kata Containers systemd services." +msgstr "" + +#: ../../tutorials/kata.rst:45 +msgid "Run Kata Containers" +msgstr "" + +#: ../../tutorials/kata.rst:53 +msgid "" +"If you use a proxy server and your proxy environment variables are " +"already set, run the following commands as a shell script to configure " +"Docker:" +msgstr "" + +#: ../../tutorials/kata.rst:70 +msgid "**Congratulations!**" +msgstr "" + +#: ../../tutorials/kata.rst:72 +msgid "You've successfully installed and set up Kata Containers on |CL|." +msgstr "" + +#: ../../tutorials/kata.rst:75 +msgid "More information about Docker" +msgstr "" + +#: ../../tutorials/kata.rst:77 +msgid "" +"Docker on |CL| provides a :file:`docker.service` file to start the Docker" +" daemon. The daemon will use runc or kata-runtime depending on the " +"environment:" +msgstr "" + +#: ../../tutorials/kata.rst:81 +msgid "" +"If you are running |CL| on bare metal or on a VM with Nested " +"Virtualization activated, Docker uses kata-runtime as the default " +"runtime." +msgstr "" + +#: ../../tutorials/kata.rst:84 +msgid "" +"If you are running |CL| on a VM without Nested Virtualization, Docker " +"uses runc as the default runtime." +msgstr "" + +#: ../../tutorials/kata.rst:87 +msgid "" +"You do not need to manually configure the runtime for Docker, because it " +"automatically uses the runtime supported by the system." +msgstr "" + +#: ../../tutorials/kata.rst:91 +msgid "Troubleshooting" +msgstr "" + +#: ../../tutorials/kata.rst:93 +msgid "" +"To change the Docker storage driver, see :ref:`additional-docker-" +"configuration`." +msgstr "" + +#: ../../tutorials/kata.rst:96 +msgid "" +"For some |CL| versions before 27000, you may need to manually configure " +"Docker\\* to use Kata Containers by default." +msgstr "" + +#: ../../tutorials/kata.rst:99 +msgid "To do so, enter:" +msgstr "" + +#: ../../tutorials/kata.rst:109 +msgid "To check the version of |CL| on your system, enter:" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/kata_migration.po b/locale/zh_CN/LC_MESSAGES/tutorials/kata_migration.po new file mode 100644 index 00000000..32c6f182 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/kata_migration.po @@ -0,0 +1,104 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/kata_migration.rst:4 +msgid "Migrate Clear Containers to Kata Containers\\*" +msgstr "" + +#: ../../tutorials/kata_migration.rst:6 +msgid "" +"`Clear Containers`_ and `Kata Containers`_ can co-exist in the same " +"system. Both can be installed through the :file:`containers-virt bundle`." +" However, we recommend that you migrate to Kata Containers because Clear " +"Containers is no longer maintained_ and will soon be deprecated on |CL-" +"ATTR|." +msgstr "" + +#: ../../tutorials/kata_migration.rst:11 +msgid "This guide describes how to migrate to Kata Containers and assumes that:" +msgstr "" + +#: ../../tutorials/kata_migration.rst:13 +msgid "Clear Containers is on a Docker\\* system." +msgstr "" + +#: ../../tutorials/kata_migration.rst:14 +msgid "Kata Containers is installed. See :ref:`kata`." +msgstr "" + +#: ../../tutorials/kata_migration.rst:18 +msgid "Stop Clear Containers instances" +msgstr "" + +#: ../../tutorials/kata_migration.rst:20 +msgid "As an unprivileged user, stop all running instances of Clear Containers:" +msgstr "" + +#: ../../tutorials/kata_migration.rst:28 +msgid "Manually migrate customized configuration files" +msgstr "" + +#: ../../tutorials/kata_migration.rst:30 +msgid "" +"If you have made changes to your `Clear Containers configuration`_, " +"review those changes and decide whether to manually apply those changes " +"to your `Kata Containers configuration`_." +msgstr "" + +#: ../../tutorials/kata_migration.rst:34 +msgid "Make any required changes before continuing this process." +msgstr "" + +#: ../../tutorials/kata_migration.rst:38 +msgid "You do not need to manually remove any Clear Containers packages." +msgstr "" + +#: ../../tutorials/kata_migration.rst:42 +msgid "Enable Kata Containers as default" +msgstr "" + +#: ../../tutorials/kata_migration.rst:44 +msgid "Configure Docker to use the Kata Containers runtime by default." +msgstr "" + +#: ../../tutorials/kata_migration.rst:54 +msgid "Restart the Docker systemd services." +msgstr "" + +#: ../../tutorials/kata_migration.rst:61 +msgid "Verify Docker is using Kata Containers." +msgstr "" + +#: ../../tutorials/kata_migration.rst:69 +msgid "Run Kata Containers" +msgstr "" + +#: ../../tutorials/kata_migration.rst:71 +msgid "Use the following command:" +msgstr "" + +#: ../../tutorials/kata_migration.rst:77 +msgid "**Congratulations!**" +msgstr "" + +#: ../../tutorials/kata_migration.rst:79 +msgid "You've successfully migrated from Clear Containers to Kata Containers." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/kubernetes/kubernetes-bp.po b/locale/zh_CN/LC_MESSAGES/tutorials/kubernetes/kubernetes-bp.po new file mode 100644 index 00000000..2dc71062 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/kubernetes/kubernetes-bp.po @@ -0,0 +1,138 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:4 +msgid "Kubernetes Best Practices on |CL|" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:7 +msgid "Use swupd to update clusters" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:9 +msgid "" +"This tutorial shows you how to manage your Kubernetes cluster while using" +" :command:`swupd` to update |CL-ATTR|." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:12 +msgid "" +"In our tutorial :ref:`kubernetes`, we explain how to set up a Kubernetes " +"cluster on |CL| using `kubeadm`. `Kubeadm documentation`_ often builds on" +" the assumption that the distribution uses a traditional package manager " +"(e.g., RPM/DEB)." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:17 +msgid "" +"In contrast, |CL| uses `swupd` to update the OS, which in this case " +"updates all of the kubernetes node and client binaries simultaneously, as" +" part of the `cloud-native-basic` bundle (e.g., kubectl, kubeadm, " +"kubelet). Running :command:`sudo swupd update` requires special care to " +"ensure the OS incorporates the latest Kubernetes upgrades." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:23 +msgid "" +"This document describes best practices to manage cluster upgrades with " +"`kubeadm` on a |CL|-based cluster." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:27 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:29 +msgid "Assure that you:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:31 +msgid "Completed :ref:`kubernetes`" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:32 +msgid "Installed the bundle `cloud-native-basic`" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:36 +msgid "" +"Other Linux\\* distros shown in Kubernetes upgrade documentation reflect " +"`apt-get update`, `apt-mark hold kubeadm`, and similar commands; however," +" such commands **are not valid** on |CL|." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:40 +msgid "Update the control plane" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:42 +msgid "Read kubernetes documentation `before you begin`_." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:44 +msgid "On your master node, run the command:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:52 +msgid "" +"If the minor version of Kubernetes changes, |CL| shows a message-of-the-" +"day, or `motd`. When the `motd` appears, you **must postpone** a kubelet " +"restart on master and nodes until the control plane is properly updated. " +":command:`swupd update` does not restart services automatically unless " +"explicitly configured to do so." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:54 +msgid "Now follow these instructions in kubernetes documentation." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:56 +msgid "`Upgrade control plane`_" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:57 +msgid "`Drain control plane node`_" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:58 +#: ../../tutorials/kubernetes/kubernetes-bp.rst:73 +msgid "`Restart Kubelet and undrain node`_" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:61 +msgid "Update worker nodes" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:63 +msgid "On each worker node, run the command:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:69 +msgid "Now follow these instructions in kubernetes documentation:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:71 +msgid "`Drain node`_" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes-bp.rst:72 +msgid "`Update kubelet configuration`_" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/kubernetes/kubernetes.po b/locale/zh_CN/LC_MESSAGES/tutorials/kubernetes/kubernetes.po new file mode 100644 index 00000000..38e23ec4 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/kubernetes/kubernetes.po @@ -0,0 +1,448 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/kubernetes/kubernetes.rst:4 +msgid "Run Kubernetes\\*" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:6 +msgid "" +"This tutorial describes how to install, configure, and run the " +"`Kubernetes container orchestration system`_ on |CL-ATTR| using CRI+O and" +" kata-runtime." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:10 +msgid "" +"Kubernetes\\* is an open source system for automating deployment, " +"scaling, and management of containerized applications. It groups " +"containers that make up an application into logical units for easy " +"management and discovery." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:14 +msgid "" +"Kata Containers\\* kata-runtime adheres to :abbr:`OCI (Open Container " +"Initiative*)` guidelines and work seamlessly with Kubernetes. `Kata " +"Containers`_ provide strong isolation for untrusted workloads or multi-" +"tenant scenarios. Kata Containers can be allocated on a per-pod basis so " +"you can mix and match both on the same host to suit your needs." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:25 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:27 +msgid "" +"This tutorial assumes you have already installed |CL|. For detailed " +"instructions on installing |CL| on a bare metal system, follow the " +":ref:`bare metal installation tutorial`. " +"Learn about the benefits of having an up-to-date system for cloud " +"orchestration on the :ref:`swupd-about` page." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:33 +msgid "" +"Before you install any new packages, update |CL| with the following " +"command:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:40 +msgid "Install Kubernetes and CRI runtimes" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:42 +msgid "" +"Kubernetes, a set of supported :abbr:`CRI (Container Runtime Interface)` " +"runtimes, and networking plugins, are included in the `cloud-native-" +"basic`_ bundle." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:46 +msgid "To install this framework, enter the following command:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:54 +msgid "For more on networking plugins, see `Install pod network add-on`_." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:57 +msgid "Configure Kubernetes" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:59 +msgid "" +"This tutorial uses the basic default Kubernetes configuration for " +"simplicity. You must define your Kubernetes configuration according to " +"your specific deployment and your security needs." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:63 +msgid "Enable IP forwarding to avoid kubeadm `preflight check`_ errors:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:65 +msgid "" +"Create (or edit if it exists) the file :file:`/etc/sysctl.d/60-k8s.conf` " +"and include the following line:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:72 +msgid "Apply the change:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:78 +msgid "Enable the kubelet service:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:84 +msgid "Disable swap using one of the following methods, either:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:86 +msgid "Temporarily:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:94 +msgid "Swap will be enabled at next reboot, causing failures in your cluster." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:97 +msgid "or:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:99 +msgid "Permanently:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:101 +msgid "Mask the swap partition:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:110 +msgid "" +"On systems with limited resources, some performance degradation may be " +"observed while swap is disabled." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:113 +msgid "Switch to root to modify the `hosts` file:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:119 +msgid "" +"Create (or edit if it exists) the hosts file that Kubernetes will read to" +" locate the master's host:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:126 +msgid "Exit root:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:133 +msgid "Configure and run Kubernetes" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:135 +msgid "" +"This section describes how to configure and run Kubernetes with CRI-O and" +" kata-runtime." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:138 +msgid "Configure and run CRI-O + kata-runtime" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:140 +msgid "Enable the CRI-O service:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:146 +msgid "Enter the commands:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:153 +msgid "" +"Initialize the master control plane with the command below and follow the" +" displayed instructions to set up `kubectl`:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:159 +msgid "Register kata-runtime as a RuntimeClass handler:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:178 +msgid "Install pod network add-on" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:180 +msgid "" +"You must choose and install a `pod network add-on`_ to allow your pods to" +" communicate. Check whether or not your add-on requires special flags " +"when you initialize the master control plane." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:184 +msgid "**Notes about flannel add-on**" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:186 +msgid "" +"If you choose the `flannel` add-on, then you must add the following to " +"the `kubeadm init` command:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:193 +msgid "" +"Furthermore, if you are using CRI-O and `flannel` and you want to use " +"Kata Containers, edit the :file:`/etc/crio/crio.conf` file to add:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:202 +msgid "Use your cluster" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:204 +msgid "" +"Once your master control plane is successfully initialized, instructions " +"on how to use your cluster and its *IP*, *token*, and *hash* values are " +"displayed. It is important that you record the cluster values because " +"they are needed when joining worker nodes to the cluster. Some values " +"have a valid period. The values are presented in a format similar to:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:214 +msgid "**Congratulations!**" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:216 +msgid "" +"You've successfully installed and set up Kubernetes in |CL| using CRI-O " +"and kata-runtime. You are now ready to follow on-screen instructions to " +"deploy a pod network to the cluster and join worker nodes with the " +"displayed token and IP information." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:222 +msgid "Related topics" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:224 +msgid "Read the Kubernetes documentation to learn more about:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:226 +msgid "`Understanding basic Kubernetes architecture`_" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:228 +msgid "`Deploying an application to your cluster`_" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:230 +msgid "Installing a `pod network add-on`_" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:232 +msgid "`Joining your nodes`_" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:235 +msgid "Cloud native setup automation (optional)" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:237 +msgid "" +"Clone the `cloud-native-setup`_ repository on your system and follow the " +"instructions. This repository includes helper scripts to automate " +"configuration." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:240 +msgid "Package configuration customization (optional)" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:242 +msgid "" +"|CL| is a stateless system that looks for user-defined package " +"configuration files in the :file:`/etc/` directory to be " +"used as default. If user-defined files are not found, |CL| uses the " +"distribution-provided configuration files for each package." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:247 +msgid "" +"If you customize any of the default package configuration files, you " +"**must** store the customized files in the :file:`/etc/` directory. If " +"you edit any of the distribution-provided default files, your changes " +"will be lost in the next system update." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:252 +msgid "" +"For example, to customize CRI-O configuration in your system, run the " +"following commands:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:261 +msgid "Learn more about `Stateless`_ in |CL| and view the |CL| `documentation`_." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:264 +msgid "Proxy configuration (optional)" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:266 +msgid "" +"If you use a proxy server, you must set your proxy environment variables " +"and create an appropriate proxy configuration file for both CRI-O " +"services. Consult your IT department if you are behind a corporate proxy " +"for the appropriate values. Ensure that your local IP is **explicitly " +"included** in the environment variable *NO_PROXY*. (Setting *localhost* " +"is not enough.)" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:271 +msgid "" +"If you have already set your proxy environment variables, run the " +"following commands as a shell script to configure all of these services " +"in one step:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:289 +msgid "Next steps" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:291 +msgid ":ref:`kubernetes-bp`" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:295 +msgid "Troubleshooting" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:297 +msgid " not found in message." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:299 +msgid "" +"Your DNS server may not be appropriately configured. Try adding an entry " +"to the :file:`/etc/hosts` file with your host's IP and Name." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:302 +msgid "For example: 100.200.50.20 myhost" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:304 +msgid "" +"Use the commands :command:`hostname` and :command:`hostname -I` to " +"retrieve them." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:306 +msgid "Images cannot be pulled." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:308 +msgid "" +"You may be behind a proxy server. Try configuring your proxy settings, " +"using the environment variables *HTTP_PROXY*, *HTTPS_PROXY*, and " +"*NO_PROXY* as required in your environment." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:312 +msgid "Connection refused error." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:314 +msgid "" +"If you are behind a proxy server, you may need to add the master's IP to " +"the environment variable *NO_PROXY*." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:317 +msgid "Connection timed-out or Access Refused errors." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:319 +msgid "" +"You must ensure that the appropriate proxy settings are available from " +"the same terminal where you will initialize the control plane. To verify " +"the proxy settings that Kubernetes will actually use, run the commands:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:329 +msgid "" +"If the displayed proxy values are different from your assigned values, " +"the cluster initialization will fail. Contact your IT support team to " +"learn how to set the proxy variables permanently, and how to make them " +"available for all the types of access that you will use, such as remote " +"SSH access." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:334 +msgid "" +"If the result of the above commands is blank, you may need to add a " +"``profile`` to the :file:`/etc` directory. To do so, follow these steps." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:337 +msgid "Create a `profile` in :file:`/etc`" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:343 +msgid "" +"With a preferred editor, open `profile`, and enter your proxy settings. " +"Example shown below." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:355 +msgid " can be obtained by running :command:`ifconfig`." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:357 +msgid "Save and exit the `profile`." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:359 +msgid "Run:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:365 +msgid "To ensure your system isn't running previous session variables, run:" +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:371 +msgid "Continue below while passing `-E` in the command as shown." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:373 +msgid "Missing environment variables." +msgstr "" + +#: ../../tutorials/kubernetes/kubernetes.rst:375 +msgid "" +"If you are behind a proxy server, pass environment variables by adding " +"*-E* to the command that initializes the master control plane." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/machine-learning/machine-learning.po b/locale/zh_CN/LC_MESSAGES/tutorials/machine-learning/machine-learning.po new file mode 100644 index 00000000..b82bc2cd --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/machine-learning/machine-learning.po @@ -0,0 +1,314 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/machine-learning/machine-learning.rst:4 +msgid "TensorFlow\\* machine learning on |CL-ATTR|" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:6 +msgid "" +"This tutorial will demonstrate the installation and execusion of a " +"TensorFlow\\* machine learning example on |CL-ATTR|. It uses a Jupyter\\*" +" Notebook and MNIST data for handwriting recognition." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:10 +msgid "" +"The initial steps will have you set up a Jupyter kernel and run a " +"Notebook on a bare-metal |CL| system." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:14 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:16 +msgid "" +"This tutorial assumes you have installed |CL| on your host system. For " +"detailed instructions on installing |CL| on a bare metal system, follow " +"the :ref:`bare metal installation tutorial`." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:20 +msgid "" +"Before you install any new packages, update |CL| with the following " +"command:" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:26 +msgid "Once your system is updated, add the following bundles to your system:" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:28 +msgid "`machine-learning-web-ui`: This bundle contains the Jupyter application." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:30 +msgid "" +"`machine-learning-basic`: This bundle contains TensorFlow and other " +"useful tools." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:33 +msgid "" +"To install the bundles, run the following commands in your :file:`$HOME` " +"directory:" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:43 +msgid "Set up a Jupyter notebook" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:45 +msgid "" +"With all required packages and libraries installed, set up the file " +"structure for the Jupyter Notebook." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:48 +msgid "" +"In the :file:`$HOME` directory, create a directory for the Jupyter " +"Notebooks named :file:`Notebooks`." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:55 +msgid "Within :file:`Notebooks`, create a directory named :file:`Handwriting`." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:61 +msgid "Change to the new directory." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:67 +msgid "" +"Copy the :file:`MNIST_example.ipynb` file into the :file:`Handwriting` " +"directory." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:71 +msgid "" +"After installing the `machine-learning basic` bundle, you can find the " +"example code under :file:`/usr/share/doc/tensorflow/MNIST_example.ipynb`." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:76 +msgid "" +"The example code downloads and decompresses the MNIST data directly into " +"the :file:`./mnist` directory. Alternatively, download the four files " +"directly from the Yann LeCun’s `MNIST Database website`_ and save them " +"into a :file:`mnist` directory within the :file:`Handwriting` directory." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:81 +msgid "The files needed are:" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:83 +msgid "`train-images-idx3-ubyte.gz`_: Training set images (9912422 bytes)" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:85 +msgid "`train-labels-idx1-ubyte.gz`_: Training set labels (28881 bytes)" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:87 +msgid "`t10k-images-idx3-ubyte.gz`_: Test set images (1648877 bytes)" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:89 +msgid "`t10k-labels-idx1-ubyte.gz`_: Test set labels (4542 bytes)" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:92 +msgid "Run the Jupyter machine learning example code" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:94 +msgid "" +"With |CL|, Jupyter, and TensorFlow installed and configured, we can run " +"the example code." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:97 +msgid "" +"Go to the :file:`($HOME)/Notebooks` directory and start Jupyter with the " +"following commands:" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:106 +msgid "" +"The Jupyter server starts and opens a web browser showing the Jupyter " +"file manager with a list of files in the current directory, see figure 1." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:112 +msgid "Figure 1: The Jupyter file manager shows the list of available files." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:114 +msgid "" +"Click on the :file:`Handwriting` directory. The " +":file:`MNIST_example.ipynb` file created earlier should be listed there, " +"see figure 2." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:120 +msgid "Figure 2: The example file within the Jupyter file manager." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:122 +msgid "" +"To run the hand writing example, click on the :file:`MNIST_example.ipynb`" +" file to load the notebook, see figure 3." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:128 +msgid "" +"Figure 3: The loaded MNIST_example notebook within the Jupyter file " +"manager." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:131 +msgid "" +"Click the |run-cell| button to execute the code in the current cell and " +"move to the next." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:134 +msgid "" +"Select the :guilabel:`In [2]` cell and click the |run-cell| button to " +"load the MNIST data. The successful output is shown on figure 4." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:140 +msgid "Figure 4: Output after successfully importing the MNIST data." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:143 +msgid "" +"After the MNIST data was successfully downloaded and extracted into the " +":file:`mnist` directory within the :file:`($HOME)/Notebooks/Handwriting` " +"directory, four .gz files are present and the four data sets were " +"created: `trainX`, `trainY`, `testX` and `testY`." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:148 +msgid "" +"To inspect the imported data, the function in :guilabel:`In [3]` first " +"instructs Jupyter to reshape the data into an array of 28 x 28 images and" +" to plot the area in a 28 x 28 grid. Click the |run-cell| button twice to" +" show the first two digits in the `trainX` dataset, see figure 5." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:156 +msgid "" +"Figure 5: A function reshapes the data and displays the first two digits " +"in the `trainX` dataset." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:159 +msgid "" +"The :guilabel:`In [4]` cell defines the neural network. It provides the " +"inputs, defines the hidden layers, runs the training model, and sets up " +"the output layer, see figure 6. Click the |run-cell| button four times to" +" perform these operations." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:167 +msgid "Figure 6: Defining, building and training the neural network model." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:169 +msgid "" +"To test the accuracy of the prediction the system makes, select the " +":guilabel:`In [8]` cell and click the |run-cell| button. In this example," +" the number 6 was predicted with a 99% accuracy, see figure 7." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:176 +msgid "" +"Figure 7: The system predicts a number providing the accuracy of the " +"prediction." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:181 +msgid "" +"To retest the accuracy of a random data point's prediction, run the cell " +":guilabel:`In [8]` again. It will take another random data point and " +"predict its value." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:185 +msgid "" +"To check the accuracy for the whole dataset, select the :guilabel:`In " +"[10]` cell and click the |run-cell| button. Our example's accuracy is " +"calculated as 97.17%, see figure 8." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:192 +msgid "Figure 8: The system's accuracy for the entire data set." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:194 +msgid "" +"For more in-depth information on the model used and the mathematics it " +"entails, visit the TensorFlow tutorials `TensorFlow MNIST beginners " +"demo`_ and `TensorFlow MNIST pros demo`_." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:198 +msgid "**Congratulations!**" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:200 +msgid "" +"You have successfully installed a Jupyter kernel on |CL|. In addition, " +"you trained a neural network to successfully predict the values contained" +" in a data set of hand-written number images." +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:205 +msgid "Related topics" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:207 +msgid "`MNIST Database website`_" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:208 +msgid "`TensorFlow MNIST beginners demo`_" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:209 +msgid "`TensorFlow MNIST pros demo`_" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:210 +msgid "`Jupyter main website`_" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:211 +msgid "`Jupyter documentation`_" +msgstr "" + +#: ../../tutorials/machine-learning/machine-learning.rst:212 +msgid "`MNIST at Wikipedia`_" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/nvidia.po b/locale/zh_CN/LC_MESSAGES/tutorials/nvidia.po new file mode 100644 index 00000000..8f20bc16 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/nvidia.po @@ -0,0 +1,420 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/nvidia.rst:4 +msgid "Install NVIDIA\\* Drivers" +msgstr "" + +#: ../../tutorials/nvidia.rst:6 +msgid "" +"NVIDIA manufactures graphics processing units (GPU), also known as " +"graphics cards." +msgstr "" + +#: ../../tutorials/nvidia.rst:9 +msgid "" +"NVIDIA devices on Linux\\* have two popular device driver options: the " +"opensource drivers from the `nouveau project`_ or the proprietary drivers" +" published by NVIDIA. The nouveau drivers are built into the |CL-ATTR| " +"kernel and are loaded automatically at system boot if a compatible card " +"is detected." +msgstr "" + +#: ../../tutorials/nvidia.rst:15 +msgid "" +"These instructions show how to use the proprietary NVIDIA drivers, which " +"require a manual installation." +msgstr "" + +#: ../../tutorials/nvidia.rst:20 +msgid "" +"Software installed outside of :ref:`swupd ` is not updated " +"with |CL| updates and must be updated and maintained manually." +msgstr "" + +#: ../../tutorials/nvidia.rst:23 +msgid "" +"For example, the file :file:`/usr/lib/libGL.so` conflicts between the one" +" provided by the mesa package in |CL| and the one NVIDIA provides. If a " +"|CL| update overwrites these files, a reinstallation of the NVIDIA driver" +" might be required." +msgstr "" + +#: ../../tutorials/nvidia.rst:36 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/nvidia.rst:38 +msgid "A |CL| system with a desktop installed" +msgstr "" + +#: ../../tutorials/nvidia.rst:39 +msgid "An NVIDIA device installed" +msgstr "" + +#: ../../tutorials/nvidia.rst:43 +msgid "Install DKMS" +msgstr "" + +#: ../../tutorials/nvidia.rst:45 +msgid "" +"The :ref:`Dynamic Kernel Module System (DKMS) ` " +"allows the NVIDIA kernel modules to be automatically integrated when " +"kernel updates occur in |CL|." +msgstr "" + +#: ../../tutorials/nvidia.rst:49 +msgid "Install the appropriate DKMS bundle using the instructions below:" +msgstr "" + +#: ../../tutorials/nvidia.rst:52 +msgid "" +"The Long Term Support (LTS) kernel variant is more likely to remain " +"compatible between updates with NVIDIA drivers." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:3 +msgid "" +"The *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:6 +msgid "The *kernel-native-dkms* bundle also:" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:8 +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 `." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:13 +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:17 +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:22 +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:28 +msgid "" +"Install the :command:`kernel-native-dkms` or :command:`kernel-lts-dkms` " +"bundle:" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:31 +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:40 +msgid "Ensure *.native* or *.lts* is in the kernel name." +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:42 +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:50 +msgid "or" +msgstr "" + +#: ../../guides/kernel/kernel-modules-dkms.rst:57 +msgid "Update the |CL| bootloader and reboot." +msgstr "" + +#: ../../tutorials/nvidia.rst:62 +msgid "Download and install the NVIDIA Drivers" +msgstr "" + +#: ../../tutorials/nvidia.rst:66 +msgid "Download the NVIDIA Drivers for Linux" +msgstr "" + +#: ../../tutorials/nvidia.rst:68 +msgid "Identify the model of NVIDIA GPU that is installed." +msgstr "" + +#: ../../tutorials/nvidia.rst:75 +msgid "" +"Go to the `NVIDIA Driver Downloads website`_ . Search for and download " +"the appropriate driver based on the model of NVIDIA GPU you have with " +"*Linux 64-bit* selected as the Operating System ." +msgstr "" + +#: ../../tutorials/nvidia.rst:80 +msgid "" +"Open a terminal and navigate to where the :file:`NVIDIA-" +"Linux-x86_64-.run` file was saved. In this example, it was saved" +" in the Downloads folder." +msgstr "" + +#: ../../tutorials/nvidia.rst:88 +msgid "Make the :file:`NVIDIA-Linux-x86_64-.run` file executable." +msgstr "" + +#: ../../tutorials/nvidia.rst:96 +msgid "Disable the nouveau Driver" +msgstr "" + +#: ../../tutorials/nvidia.rst:98 +msgid "" +"The proprietary NVIDIA driver is incompatible with the nouveau driver and" +" must be disabled before installation can continue." +msgstr "" + +#: ../../tutorials/nvidia.rst:101 +msgid "" +"Disable the nouveau driver by creating a blacklist file under " +":file:`/etc/modprobe.d` and reboot." +msgstr "" + +#: ../../tutorials/nvidia.rst:111 +msgid "" +"Reboot the system and log back in. It is normal for the graphical " +"environment not to start without the NVIDIA driver loaded." +msgstr "" + +#: ../../tutorials/nvidia.rst:118 +msgid "Configure Alternative Software Paths" +msgstr "" + +#: ../../tutorials/nvidia.rst:120 +msgid "" +"The NVIDIA installer will be directed to install files under " +":file:`/opt/nvidia` as much as possible to keep its contents isolated " +"from the rest of the |CL| system files under :file:`/usr`. The dynamic " +"linker and X server must be configured to use the content under " +":file:`/opt/nvidia`." +msgstr "" + +#: ../../tutorials/nvidia.rst:127 +msgid "" +"Configure the dynamic linker to look for and to cache shared libraries " +"under :file:`/opt/nvidia/lib` and :file:`/opt/nvidia/lib32` in addition " +"to the default paths." +msgstr "" + +#: ../../tutorials/nvidia.rst:138 +msgid "Reload the dynamic linker run-time bindings and library cache." +msgstr "" + +#: ../../tutorials/nvidia.rst:144 +msgid "" +"Create a Xorg configuration file to search for modules under " +":file:`/opt/nvidia` in addition to the default path." +msgstr "" + +#: ../../tutorials/nvidia.rst:160 +msgid "Install the NVIDIA Drivers" +msgstr "" + +#: ../../tutorials/nvidia.rst:163 +msgid "" +"A terminal not running on */dev/tty1* is useful to view uninterrupted " +"installation progress. Switch to a secondary virtual terminal by pushing " +":command:`CTRL + ALT + F2` or remotely login over SSH." +msgstr "" + +#: ../../tutorials/nvidia.rst:168 +msgid "Navigate into the directory where the NVIDIA installer was downloaded." +msgstr "" + +#: ../../tutorials/nvidia.rst:175 +msgid "Run the installer with the advanced options below." +msgstr "" + +#: ../../tutorials/nvidia.rst:199 +msgid "" +"The graphical interface may automatically start after the NVIDIA driver " +"is loaded. Return to the working terminal and log back in if necessary." +msgstr "" + +#: ../../tutorials/nvidia.rst:203 +msgid "Confirm that the NVIDIA kernel modules are loaded." +msgstr "" + +#: ../../tutorials/nvidia.rst:210 +msgid "" +"Run a |CL| system verification to restore files that the NVIDIA installer" +" likely deleted." +msgstr "" + +#: ../../tutorials/nvidia.rst:219 +msgid "" +"The NVIDIA software places some files under the :file:`/usr` subdirectory" +" which are not managed by |CL| and conflict with the |CL| stateless " +"design." +msgstr "" + +#: ../../tutorials/nvidia.rst:222 +msgid "" +"Although a limited version of :command:`swupd repair` is run above, other" +" uses of the :command:`swupd repair` command should be avoided with the " +"proprietary NVIDIA drivers installed." +msgstr "" + +#: ../../tutorials/nvidia.rst:228 +msgid "Updating the NVIDIA Drivers" +msgstr "" + +#: ../../tutorials/nvidia.rst:230 +msgid "" +"The proprietary NVIDIA drivers are installed manually outside of " +":ref:`swupd ` and must be updated manually when needed." +msgstr "" + +#: ../../tutorials/nvidia.rst:233 +msgid "" +"Updating the NVIDIA drivers follows the same steps as initial " +"installation, however the desktop environment must first be stopped so " +"that the drivers are not in use." +msgstr "" + +#: ../../tutorials/nvidia.rst:237 +msgid "" +"Follow the steps in the `Download the NVIDIA Drivers for Linux`_ section " +"to get the latest NVIDIA drivers." +msgstr "" + +#: ../../tutorials/nvidia.rst:240 +msgid "" +"Temporarily set the default boot target to the *multi-user*, which is a " +"non-graphical runtime." +msgstr "" + +#: ../../tutorials/nvidia.rst:248 +msgid "" +"Reboot the system and log back in. It is normal for the graphical " +"environment not to start." +msgstr "" + +#: ../../tutorials/nvidia.rst:251 +msgid "" +"Follow the steps in the `Install the NVIDIA Drivers`_ section to update " +"the NVIDIA drivers. This installation will overwrite the previous NVIDIA " +"drivers and files." +msgstr "" + +#: ../../tutorials/nvidia.rst:255 +msgid "Set the default boot target back to the *graphical* target." +msgstr "" + +#: ../../tutorials/nvidia.rst:262 +msgid "Reboot the system and log back in." +msgstr "" + +#: ../../tutorials/nvidia.rst:264 +msgid "" +"Trigger a flatpak update which will download the runtime corresponding " +"with the new NVIDIA drivers for the flatpak apps that require it." +msgstr "" + +#: ../../tutorials/nvidia.rst:273 +msgid "Uninstalling the NVIDIA Drivers" +msgstr "" + +#: ../../tutorials/nvidia.rst:275 +msgid "" +"The NVIDIA drivers and associated software can be uninstalled and nouveau" +" driver restored with the instructions in this section." +msgstr "" + +#: ../../tutorials/nvidia.rst:278 +msgid "Remove the :file:`modprobe.d` file that prevents nouveau from loading." +msgstr "" + +#: ../../tutorials/nvidia.rst:285 +msgid "Remove the :file:`xorg.conf.d` file that adds a search path for X modules." +msgstr "" + +#: ../../tutorials/nvidia.rst:291 +msgid "Run the :command:`sudo /opt/nvidia/bin/nvidia-uninstall`" +msgstr "" + +#: ../../tutorials/nvidia.rst:293 +msgid "Follow the prompts on the screen and reboot the system." +msgstr "" + +#: ../../tutorials/nvidia.rst:297 +msgid "Debugging Installation of NVIDIA Drivers" +msgstr "" + +#: ../../tutorials/nvidia.rst:299 +msgid "" +"The NVIDIA driver places installer and uninstaller logs under " +":file:`/var/log/nvidia-install` and :file:`/var/log/nvidia-uninstall`." +msgstr "" + +#: ../../tutorials/nvidia.rst:302 +msgid "" +":file:`NVIDIA-Linux-x86_64-.run --advanced-options` shows many " +"parameters to control installation behavior." +msgstr "" + +#: ../../tutorials/nvidia.rst:305 +msgid "" +":file:`NVIDIA-Linux-x86_64-.run --extract-only` extracts " +"installation files into a directory named :file:`NVIDIA-" +"Linux-x86_64-`." +msgstr "" + +#: ../../tutorials/nvidia.rst:312 +msgid "Additional resources" +msgstr "" + +#: ../../tutorials/nvidia.rst:314 +msgid "" +"`Why aren't the NVIDIA Linux drivers open source? " +"`_" +msgstr "" + +#: ../../tutorials/nvidia.rst:316 +msgid "" +"`Where can I get support for NVIDIA Linux drivers? " +"`_" +msgstr "" + +#: ../../tutorials/nvidia.rst:318 +msgid "" +"`NVIDIA Accelerated Linux Graphics Driver Installation Guides " +"`_" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/redis.po b/locale/zh_CN/LC_MESSAGES/tutorials/redis.po new file mode 100644 index 00000000..5199c5b1 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/redis.po @@ -0,0 +1,183 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/redis.rst:4 +msgid "Run Redis on |CL-ATTR|" +msgstr "" + +#: ../../tutorials/redis.rst:6 +msgid "" +"Redis is an in-memory key:value store designed for quick lookups, " +"accessible over the network. In this tutorial, you'll install redis and " +"launch a redis-server on |CL|, plus learn a few basic redis commands. We " +"also invite you to pull our `Clear Linux Redis instance`_ on dockerhub\\*" +" for application or infrastructure development." +msgstr "" + +#: ../../tutorials/redis.rst:12 +msgid "" +"While the `redis data structure store`_ can serve as a NoSQL database for" +" a Web application, it's also easy to integrate in an existing stack. For" +" example, you could use the Redis caching layer for real-time responses " +"on a leaderboard in a gaming app. Redis offers many client libraries with" +" language-specific bindings for Python, Perl, Ruby, and more." +msgstr "" + +#: ../../tutorials/redis.rst:19 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/redis.rst:20 +msgid "Install the `redis-native` bundle in |CL|" +msgstr "" + +#: ../../tutorials/redis.rst:21 +msgid "Install the `containers-basic` bundle in |CL| (only required in Example 2)" +msgstr "" + +#: ../../tutorials/redis.rst:24 +msgid "Install the redis bundle" +msgstr "" + +#: ../../tutorials/redis.rst:26 +msgid "In |CL|, find redis in the `redis-native` bundle." +msgstr "" + +#: ../../tutorials/redis.rst:28 +msgid "Open a Terminal and login as an administrative user." +msgstr "" + +#: ../../tutorials/redis.rst:30 +msgid "Add :file:`redis-native`." +msgstr "" + +#: ../../tutorials/redis.rst:38 +msgid "If the bundle already exists, no action is required." +msgstr "" + +#: ../../tutorials/redis.rst:41 +msgid "Start the redis-server" +msgstr "" + +#: ../../tutorials/redis.rst:43 +msgid "" +"A `systemd` service unit is available to control the redis server. By " +"default, redis runs on port 6379." +msgstr "" + +#: ../../tutorials/redis.rst:46 +msgid "Start the service." +msgstr "" + +#: ../../tutorials/redis.rst:54 +msgid "To stop redis run :command:`systemctl stop redis`." +msgstr "" + +#: ../../tutorials/redis.rst:56 +msgid "Assure the service is running." +msgstr "" + +#: ../../tutorials/redis.rst:62 +msgid "Verify the redis-server sends a reply." +msgstr "" + +#: ../../tutorials/redis.rst:70 +msgid "Expected output: `PONG`." +msgstr "" + +#: ../../tutorials/redis.rst:72 +msgid "" +"Optional: If you wish to apply advanced configuration, copy the " +"`redis.conf` into /etc/ directory." +msgstr "" + +#: ../../tutorials/redis.rst:79 +msgid "The redis-server is now ready to use on |CL|. Try some examples below." +msgstr "" + +#: ../../tutorials/redis.rst:82 +msgid "Example 1: Use the redis-cli and try commands" +msgstr "" + +#: ../../tutorials/redis.rst:84 +msgid "" +"One advantage of redis over other NoSQL databases is that developers can " +"easily access data structures like lists, sets, sorted sets, strings, and" +" hashes using collection operations commands similar to those found in " +"many programming languages. These exercises are inspired by `try redis " +"io`_." +msgstr "" + +#: ../../tutorials/redis.rst:89 +msgid "After your `redis-server` is running, try some basic commands." +msgstr "" + +#: ../../tutorials/redis.rst:91 +msgid "Enter the `redis-cli`. It provides syntax suggestions as you type." +msgstr "" + +#: ../../tutorials/redis.rst:97 +msgid "SET key to hold string value. In the set create connections and increment." +msgstr "" + +#: ../../tutorials/redis.rst:108 +msgid "If the key does not exist or hold a key value, `nil` is returned." +msgstr "" + +#: ../../tutorials/redis.rst:126 +msgid "Create a `friends` list and insert new values at the end of the list." +msgstr "" + +#: ../../tutorials/redis.rst:140 +msgid "Modify `friends` list, using a common slice method with a 0-index." +msgstr "" + +#: ../../tutorials/redis.rst:162 +msgid "" +"Consider using a hash, a very useful data type, which maps string fields " +"and string values, offering multiple lookup methods." +msgstr "" + +#: ../../tutorials/redis.rst:165 +msgid "Enter many user key:values with `HMSET`. Then try `HGET` and `HGETALL`." +msgstr "" + +#: ../../tutorials/redis.rst:185 +msgid "Example 2: Run the |CL| redis docker image" +msgstr "" + +#: ../../tutorials/redis.rst:187 +msgid "" +"We also provide a `Clear Linux Redis instance`_, which is updated " +"continuously and maintained by |CL| development." +msgstr "" + +#: ../../tutorials/redis.rst:203 +msgid "Next Steps" +msgstr "" + +#: ../../tutorials/redis.rst:205 +msgid "Follow the `redis quickstart tutorial`_ to expand potential uses." +msgstr "" + +#: ../../tutorials/redis.rst:207 +msgid "Learn to :ref:`docker`." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/smb/smb-desktop.po b/locale/zh_CN/LC_MESSAGES/tutorials/smb/smb-desktop.po new file mode 100644 index 00000000..179f5bdf --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/smb/smb-desktop.po @@ -0,0 +1,110 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/smb/smb-desktop.rst:4 +msgid "Connect to Windows\\* shared location from |CL-ATTR| desktop" +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:6 +msgid "" +"This tutorial explains how to access an existing shared drive on " +"Windows\\* via Server Message Block (SMB) / Common Internet File System " +"(CIFS) from the |CL| GNOME desktop. CIFS filesystem is generally used to" +" access shared storage locations, or share files." +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:12 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:14 +msgid "You have already `set up a shared location on Windows`_" +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:17 +msgid "Connect to Windows shared location with Nautilus" +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:19 +msgid "From the desktop, select :guilabel:`Files` from the application menu." +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:23 +msgid "GNOME Files is also known as `Nautilus`." +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:25 +msgid "In :guilabel:`Files`, select :guilabel:`Other Locations`." +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:31 +msgid "Figure 1: Files, Other Locations" +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:33 +msgid "" +"In the lower taskbar, beside :guilabel:`Connect to Server`, enter the " +"file-sharing address using the Windows sharing schema:" +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:44 +msgid "Figure 2: Connect to Server" +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:46 +msgid "" +"Optional: If there are issues with DNS, you can use an IP address in " +"place of the `servername` above. You must still specify the share." +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:49 +msgid "" +"Optional: On the Windows machine, in a CLI, retrieve the IP address by " +"entering the command:" +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:58 +msgid "If using the IP address, assure that it is accessible and secure." +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:60 +msgid "Select :guilabel:`Connect`." +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:62 +msgid "The server will request authentication, as shown in Figure 3." +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:68 +msgid "Figure 3: Authentication" +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:70 +msgid "" +"Log in with the same Windows system credentials for which you granted " +"access to the share." +msgstr "" + +#: ../../tutorials/smb/smb-desktop.rst:73 +msgid "" +"Select the appropriate checkbox to save your credentials. Consider " +"carefully the security risks as a result of your selection." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/smb/smb.po b/locale/zh_CN/LC_MESSAGES/tutorials/smb/smb.po new file mode 100644 index 00000000..3c148d6c --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/smb/smb.po @@ -0,0 +1,152 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/smb/smb.rst:4 +msgid "Enable simple file sharing with a Windows\\* machine using Samba\\*" +msgstr "" + +#: ../../tutorials/smb/smb.rst:6 +msgid "" +"This tutorial describes how to enable simple file sharing from a system " +"running |CL-ATTR| to a Windows machine using Samba. For more advanced " +"sharing, refer to the `Samba guide`_." +msgstr "" + +#: ../../tutorials/smb/smb.rst:11 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/smb/smb.rst:13 +msgid "" +"This tutorial assumes you have installed |CL| on your host system. For " +"detailed instructions, follow the steps in :ref:`bare-metal-install-" +"desktop`." +msgstr "" + +#: ../../tutorials/smb/smb.rst:16 +msgid "" +"Before you install any new packages, update |CL| with the following " +"command:" +msgstr "" + +#: ../../tutorials/smb/smb.rst:24 +msgid "Set up file sharing" +msgstr "" + +#: ../../tutorials/smb/smb.rst:26 +msgid "Log in and get root privileges." +msgstr "" + +#: ../../tutorials/smb/smb.rst:32 +msgid "Add the storage-utils bundle, which includes the Samba binaries." +msgstr "" + +#: ../../tutorials/smb/smb.rst:40 +msgid "The os-clr-on-clr bundle also includes the Samba binaries." +msgstr "" + +#: ../../tutorials/smb/smb.rst:42 +msgid "" +"Create a configuration file called :file:`/etc/samba/smb.conf`. In this " +"example, `[Downloads]` enables a folder share with a specific user. " +"`[Documents]` enables a folder share with any user. The example assumes " +"that a user account `clearlinuxuser` already exists." +msgstr "" + +#: ../../tutorials/smb/smb.rst:47 +msgid "" +"If `valid users` is not specified, then anyone with a user account on the" +" machine and with their Samba password already set can access the folder." +" However, the account is only able to access files and folders for which " +"they have appropriate permissions." +msgstr "" + +#: ../../tutorials/smb/smb.rst:52 +msgid "" +"Use :command:`chown` or :command:`chmod` to change either the owner of " +"the file or the permissions to allow other users to access the file." +msgstr "" + +#: ../../tutorials/smb/smb.rst:72 +msgid "Enable the Samba daemon to start every time." +msgstr "" + +#: ../../tutorials/smb/smb.rst:79 +msgid "" +"Use :command:`smbpasswd` to add the initial password for the user account" +" to access the share. Be aware that Samba maintains its own list of " +"passwords for user accounts. The Samba password list can be different " +"than the password used to log in." +msgstr "" + +#: ../../tutorials/smb/smb.rst:88 +msgid "" +"Setup is complete and a Windows machine on the same network can access " +"the shares. Windows uses the format :file:`\\\\\\\\[server IP or " +"hostname]\\\\folder` to access shares. Access the shares directly with " +"Windows Explorer or by mapping a network drive." +msgstr "" + +#: ../../tutorials/smb/smb.rst:93 +msgid "" +"Use the IP address of the |CL| machine for an easy access method. If the " +"|CL| machine is behind an Active Directory domain controller or a DNS " +"server, use the hostname of the |CL| machine. For other ways to access " +"shares using a hostname instead of an IP address, see `Chapter 7 of the " +"Samba guide`_." +msgstr "" + +#: ../../tutorials/smb/smb.rst:100 +msgid "Map |CL| drive in Windows" +msgstr "" + +#: ../../tutorials/smb/smb.rst:102 +msgid "" +"Open Windows Explorer and click on the left sidebar on :guilabel:`This " +"PC` to change the options available at the top." +msgstr "" + +#: ../../tutorials/smb/smb.rst:105 +msgid "" +"Click the :guilabel:`Map Network Drive` icon and enter the path in the " +"format: :file:`\\\\\\\\[server IP or hostname]\\\\[shared folder]`" +msgstr "" + +#: ../../tutorials/smb/smb.rst:108 +msgid "" +"Check the box :guilabel:`Connect using different credentials`. Enter the " +"Samba user `clearlinuxuser` and the password created with " +":command:`smbpasswd`. See Figure 1 for details." +msgstr "" + +#: ../../tutorials/smb/smb.rst:116 +msgid "Figure 1: Map a network drive in Windows Explorer." +msgstr "" + +#: ../../tutorials/smb/smb.rst:118 +msgid "" +"When complete, Windows Explorer displays the share drive as shown in " +"Figure 2." +msgstr "" + +#: ../../tutorials/smb/smb.rst:124 +msgid "Figure 2: View a share drive in Windows Explorer." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/spark.po b/locale/zh_CN/LC_MESSAGES/tutorials/spark.po new file mode 100644 index 00000000..a73c55c1 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/spark.po @@ -0,0 +1,176 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/spark.rst:4 +msgid "Set up a standalone cluster system using Apache\\* Spark\\*" +msgstr "" + +#: ../../tutorials/spark.rst:6 +msgid "" +"This tutorial describes how to install, configure, and run Apache Spark " +"on |CL-ATTR|. Apache Spark is a fast general-purpose cluster computing " +"system with the following features:" +msgstr "" + +#: ../../tutorials/spark.rst:10 +msgid "Provides high-level APIs in Java\\*, Scala\\*, Python\\*, and R\\*." +msgstr "" + +#: ../../tutorials/spark.rst:11 +msgid "Includes an optimized engine that supports general execution graphs." +msgstr "" + +#: ../../tutorials/spark.rst:12 +msgid "" +"Supports high-level tools including Spark SQL, MLlib, GraphX, and Spark " +"Streaming." +msgstr "" + +#: ../../tutorials/spark.rst:15 +msgid "" +"In this tutorial, you will install Spark on a single machine running the " +"master daemon and a worker daemon." +msgstr "" + +#: ../../tutorials/spark.rst:19 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/spark.rst:21 +msgid "" +"This tutorial 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 `." +msgstr "" + +#: ../../tutorials/spark.rst:25 +msgid "" +"Before you install any new packages, update |CL| with the following " +"command:" +msgstr "" + +#: ../../tutorials/spark.rst:32 +msgid "Install Apache Spark" +msgstr "" + +#: ../../tutorials/spark.rst:34 +msgid "" +"Apache Spark is included in the :file:`big-data-basic` bundle. To install" +" the framework, enter:" +msgstr "" + +#: ../../tutorials/spark.rst:42 +msgid "Configure Apache Spark" +msgstr "" + +#: ../../tutorials/spark.rst:44 +msgid "Create the configuration directory with the command:" +msgstr "" + +#: ../../tutorials/spark.rst:50 +msgid "" +"Copy the default templates from :file:`/usr/share/defaults/spark` to " +":file:`/etc/spark` with the command:" +msgstr "" + +#: ../../tutorials/spark.rst:57 +msgid "" +"Since |CL| is a stateless system, you should never modify the files under" +" the :file:`/usr/share/defaults` directory. The software updater " +"overwrites those files." +msgstr "" + +#: ../../tutorials/spark.rst:62 +msgid "Copy the template files below to create custom configuration files:" +msgstr "" + +#: ../../tutorials/spark.rst:70 +msgid "" +"Edit the :file:`/etc/spark/spark-env.sh` file and add the " +":envvar:`SPARK_MASTER_HOST` variable. Replace the example address below " +"with your localhost IP address. View your IP address using the " +":command:`hostname -I` command." +msgstr "" + +#: ../../tutorials/spark.rst:79 +msgid "" +"This optional step enables the master's web user interface to view " +"information needed later in this tutorial." +msgstr "" + +#: ../../tutorials/spark.rst:82 +msgid "" +"Edit the :file:`/etc/spark/spark-defaults.conf` file and update the " +"`spark.master` variable with the `SPARK_MASTER_HOST` address and port " +"`7077`." +msgstr "" + +#: ../../tutorials/spark.rst:90 +msgid "Start the master server and a worker daemon" +msgstr "" + +#: ../../tutorials/spark.rst:92 +msgid "Start the master server using:" +msgstr "" + +#: ../../tutorials/spark.rst:98 +msgid "" +"Start one worker daemon and connect it to the master using the " +"`spark.master` variable defined earlier:" +msgstr "" + +#: ../../tutorials/spark.rst:105 +msgid "" +"Open an internet browser and view the worker daemon information using the" +" master's IP address and port `8080`:" +msgstr "" + +#: ../../tutorials/spark.rst:113 +msgid "Run the Spark wordcount example" +msgstr "" + +#: ../../tutorials/spark.rst:115 +msgid "" +"Run the wordcount example using a file on your local host and output the " +"results to a new file with the following command:" +msgstr "" + +#: ../../tutorials/spark.rst:122 +msgid "" +"Open an internet browser and view the application information using the " +"master's IP address and port `8080`:" +msgstr "" + +#: ../../tutorials/spark.rst:129 +msgid "" +"View the results of the wordcount application in the " +":file:`~/Documents/results` file." +msgstr "" + +#: ../../tutorials/spark.rst:131 +msgid "**Congratulations!**" +msgstr "" + +#: ../../tutorials/spark.rst:133 +msgid "" +"You successfully installed and set up a standalone Apache Spark cluster. " +"Additionally, you ran a simple wordcount example." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/tutorial-proxy.po b/locale/zh_CN/LC_MESSAGES/tutorials/tutorial-proxy.po new file mode 100644 index 00000000..4dfdc240 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/tutorial-proxy.po @@ -0,0 +1,121 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/tutorial-proxy.rst:4 +msgid "Setting up proxy" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:6 +msgid "" +"This tutorial shows you how to configure your system for use behind an " +"outbound proxy to access the Internet." +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:9 +msgid "" +"|CL| :ref:`tooling` applications already benefit from the " +":ref:`autoproxy` feature." +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:17 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:19 +msgid "" +"This tutorial 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 `." +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:24 +msgid "Shells and programs in a desktop session" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:27 +msgid "Terminal" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:29 +msgid "Add the following to your ~/.bashrc:" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:45 +msgid "wget" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:47 +msgid "Run this command to enable downloading from websites from the terminal:" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:59 +msgid "System service (Docker)" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:61 +msgid "" +"For Docker (and other services that use systemd), you can follow these " +"steps to configure and check proxy settings:" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:65 +msgid "Be sure to use :command:`sudo`, as you will need elevated permissions." +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:67 +msgid "" +"Create :file:`/etc/systemd/system/docker.service.d` directory to host " +"configuration information for the Docker service." +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:70 +msgid "" +"Create :file:`/etc/systemd/system/docker.service.d/http-proxy.conf` and " +"add:" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:78 +msgid "Load the changes and restart the service:" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:85 +msgid "Verify that changes have loaded:" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:97 +msgid "" +"This process enables the ability to successfully run ``docker pull``. " +"Containers themselves must be configured independently." +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:101 +msgid "git over ssh" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:103 +msgid "Add the following to your :file:`~/.ssh/config`:" +msgstr "" + +#: ../../tutorials/tutorial-proxy.rst:114 +msgid "" +"Though netcat is included with Clear Linux, it is not the BSD version, " +"which is the one usually used to enable git over ssh." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/tutorials.po b/locale/zh_CN/LC_MESSAGES/tutorials/tutorials.po new file mode 100644 index 00000000..d31563df --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/tutorials.po @@ -0,0 +1,28 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/tutorials.rst:4 +msgid "Tutorials" +msgstr "" + +#: ../../tutorials/tutorials.rst:6 +msgid "Explore our tutorials to discover what you can do with |CL|!" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/wordpress/web-server-install.po b/locale/zh_CN/LC_MESSAGES/tutorials/wordpress/web-server-install.po new file mode 100644 index 00000000..3987c146 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/wordpress/web-server-install.po @@ -0,0 +1,547 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/wordpress/web-server-install.rst:4 +msgid "Set up a LAMP web server on |CL-ATTR|" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:6 +msgid "" +"This tutorial provides instructions on how to set up a :abbr:`LAMP " +"(Linux, Apache, MySQL, PHP)` web server on |CL-ATTR| and how to use " +"phpMyAdmin\\* to manage an associated database. Note that this tutorial " +"installs MariaDB\\*, which is a drop-in replacement for MySQL\\*." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:11 +msgid "" +"In order to create a web server using |CL| as the host OS, your host " +"system must be running |CL|. This tutorial assumes you have installed " +"|CL| on your host system. For detailed instructions on installing |CL| on" +" a bare metal system, visit :ref:`bare-metal-install-desktop`." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:16 +msgid "This tutorial covers:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:22 +msgid "Install Apache" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:24 +msgid "" +"Apache is an open source HTTP web server application that can run on " +"several operating systems, including |CL|. Go to the `Apache HTTP Server " +"Project`_ for more information." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:29 +msgid "Install the web-server-basic bundle" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:31 +msgid "" +"The **web-server-basic** bundle contains the packages needed to install " +"the Apache software bundle on |CL|." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:36 +msgid "" +"Before you install new packages, update the |CL| with the following " +"console command:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:43 +msgid "To install the bundle, enter the following command:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:50 +msgid "To start the Apache service, enter the following commands:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:57 +msgid "" +"To verify that the Apache server application is running, open a web " +"browser and navigate to: \\http://localhost." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:60 +msgid "" +"If the service is running, a confirmation message will appear, similar to" +" the message shown in figure 1." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:67 +msgid "`Figure 1: Confirmation that the Apache service is running.`" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:71 +msgid "" +"The :file:`index.html` file is located in the :file:`/var/www/html` " +"directory of your host system. You will copy this file into a new " +"location after you modify the configuration in the next step." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:76 +msgid "Change the default configuration and data directory" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:78 +msgid "" +"|CL| is designed to be a `stateless`_ operating system which means that " +"you must create an optional configuration file to override the default " +"values. The default location of the Apache configuration file, " +":file:`httpd.conf`, is located in the :file:`/usr/share/defaults/httpd` " +"directory. |CL| can override this directory as part of the stateless " +"paradigm. This default :file:`.conf` file includes the following " +"directives that allow for additional locations of configuration " +"definitions:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:94 +msgid "" +"In this section you will define your own httpd.conf file to override the " +"default values, and define a custom DocumentRoot for your web server." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:97 +msgid "Create the directory structure for :file:`/etc/httpd/conf.d`." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:103 +msgid "" +"Create and open the :file:`httpd.conf` file in your new " +":file:`/etc/httpd/conf.d` directory." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:110 +msgid "" +"Add the ``DocumentRoot`` variable to :file:`httpd.conf`. Copy the content" +" listed below into the new :file:`/etc/httpd/conf.d/httpd.conf` file." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:128 +msgid "" +"Create a new ``DocumentRoot`` directory structure and copy the " +":file:`index.html` file from :file:`/var/www/html` directory to " +":file:`/var/www/tutorial`." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:138 +msgid "" +"To ensure a successful setup, edit the new :file:`index.html` file with " +"an obvious change." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:145 +msgid "For example, we changed the default message" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:147 +msgid "\"It works!\"" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:149 +msgid "to" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:151 +msgid "\"It works from its new location!\"" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:153 +#: ../../tutorials/wordpress/web-server-install.rst:171 +msgid "Stop and then restart ``httpd.service``." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:160 +msgid "" +"Go to \\http://localhost to view the new screen. You should see your " +"updated default message from step 5." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:163 +msgid "" +"Change the configuration back to the default :file:`/var/www/html` " +"location. To do this, edit the :file:`/etc/httpd/conf.d/httpd.conf` file " +"again and replace any instance of /var/www/tutorial with /var/www/html." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:178 +msgid "" +"Go to \\http://localhost and verify that you can see the default screen " +"again." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:181 +msgid "Optionally, remove the /var/www/tutorial directory you previously created." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:189 +msgid "Install PHP" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:191 +msgid "" +"An Apache installation allows you to display static web pages. Enabling " +"PHP allows you to generate and display dynamic web pages. To add this " +"functionality to your web server, install PHP on your system." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:195 +msgid "To get the php components, enter the following command:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:201 +msgid "To enable PHP, enter the following commands:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:209 +msgid "After restarting the Apache service, test your PHP installation." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:211 +msgid "" +"Create and open a file named :file:`phpinfo.php` in the " +":file:`/var/www/html/` directory using a text editor." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:218 +msgid "Add the following line to the file:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:224 +msgid "Go to \\http://localhost/phpinfo.php." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:226 +msgid "Verify that the PHP information screen appears, similar to figure 2:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:232 +msgid "`Figure 2: The PHP information screen.`" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:234 +msgid "" +"If the PHP information screen is displayed, you have successfully " +"installed the PHP components and are now ready to add your database " +"application to complete your LAMP server implementation." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:239 +msgid "Install MariaDB" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:241 +msgid "" +"Install MariaDB to store content. MariaDB is a drop-in replacement for " +"MySQL and is available in the database-basic |CL| bundle." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:244 +msgid "To install the database-basic bundle, enter the following command:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:250 +msgid "To start MariaDB after it is installed, enter the following commands:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:257 +msgid "To check the status of MariaDB, enter the following command:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:263 +msgid "Press :kbd:`Ctrl` + :kbd:`c` or :kbd:`q` to exit." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:266 +msgid "Security hardening" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:268 +msgid "" +"With the MariaDB service running, we can perform some basic security " +"hardening." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:271 +msgid "To add a basic layer of security, enter the following command:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:277 +msgid "Respond to the questions that appear in the script below." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:281 +msgid "Our suggested responses follow each question." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:287 +msgid "" +"In order to secure MariaDB, we need the current password for the root " +"user. For a newly installed MariaDB without a set root password, the " +"password is blank. Thus, press enter to continue." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:299 +msgid "" +"Set the root password to prevent unauthorized MariaDB root user logins. " +"To set a root password, type 'y'." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:306 +msgid "Type the desired password for the root user." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:312 +msgid "Re-type the desired password for the root user." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:322 +msgid "" +"By default, a MariaDB installation includes an anonymous user that allows" +" anyone to log in to MariaDB without a user account. This anonymous user " +"is intended only for testing and for a smoother installation. To remove " +"the anonymous user and make your database more secure, type 'y'." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:332 +msgid "" +"Normally, root should only be allowed to connect from the 'localhost'. " +"This ensures that someone cannot guess the root password from the " +"network. To block any remote root login, type 'y'." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:341 +msgid "" +"By default, MariaDB includes a database named 'test' which anyone can " +"access. This database is also intended only for testing and should be " +"removed. To remove the test database, type 'y'." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:353 +msgid "" +"Reloading the privilege tables ensures all changes made so far take " +"effect immediately. To reload the privilege tables, type 'y'." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:362 +msgid "" +"All done! If you've completed all of the above steps, your MariaDB " +"installation should now be secure." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:365 +msgid "Thanks for using MariaDB!" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:367 +msgid "" +"The MariaDB installation is complete, and we can now install phpMyAdmin " +"to manage the databases." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:371 +msgid "Install phpMyAdmin" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:373 +msgid "" +"The web-based tool phpMyAdmin is a straightforward way to manage MySQL or" +" MariaDB databases. Visit the `phpMyAdmin`_ website for the complete " +"discussion regarding phpMyAdmin, its documentation, the latest downloads," +" and other useful information." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:378 +msgid "In this tutorial, we use the latest English version of phpMyAdmin." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:380 +msgid "" +"Download the :file:`phpMyAdmin--english.tar.gz` file to your " +":file:`~/Downloads` directory. Here, refers to the current " +"version available at https://www.phpmyadmin.net/downloads." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:386 +msgid "This example downloads and uses version 4.6.4." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:388 +msgid "" +"Once the file has been successfully downloaded and verified, decompress " +"the file and directories into the Apache web server document root " +"directory. Use the following commands:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:397 +msgid "" +"To keep things simple, rename the newly created " +":file:`phpMyAdmin-4.6.4-english` directory to :file:`phpMyAdmin` with the" +" following command:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:406 +msgid "Use phpMyAdmin to manage a database" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:408 +msgid "" +"You can use the phpMyAdmin web-based tool to manage your databases. " +"Follow the steps below for setting up a database called \"WordPress\"." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:411 +msgid "" +"Verify that a successful installation of all LAMP server components by " +"going to \\http://localhost/phpMyAdmin. See figure 3." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:414 +msgid "" +"Log in with your root userid and the password you set up when you ran the" +" :ref:`mysql_secure_installation command `. Enter your " +"credentials and select :guilabel:`Go` to log in:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:422 +msgid "`Figure 3: The phpMyAdmin login page.`" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:424 +msgid "" +"Verify a successful login by confirming that the main phpMyAdmin page " +"displays, as shown in figure 4:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:431 +msgid "`Figure 4: The phpMyAdmin dashboard.`" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:433 +msgid "" +"Set up a database by selecting the :guilabel:`Databases` tab, as shown in" +" figure 5." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:436 +msgid "" +"Enter `WordPress` in the text field below the :guilabel:`Create database`" +" label." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:439 +msgid "" +"Select the :guilabel:`utf8_unicode_ci` option from the " +":guilabel:`Collation` drop-down menu beside the text field." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:442 +msgid "Click :guilabel:`Create`." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:448 +msgid "`Figure 5: The Databases tab.`" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:450 +msgid "" +"Set up user permissions by selecting the :guilabel:`WordPress` database " +"located in the left panel. See figure 6." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:453 +msgid "Select the :guilabel:`Privileges` tab. Figure 6 shows its contents." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:459 +msgid "`Figure 6: The Privileges tab.`" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:461 +msgid "" +"Click :guilabel:`Add user account` located at the bottom of the " +":guilabel:`Privileges` tab. The `Add user account` page appears, as shown" +" in figure 7." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:469 +msgid "`Figure 7: The User accounts tab.`" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:471 +msgid "" +"Enter the following information in the corresponding fields that appear " +"in figure 7 above:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:474 +msgid "User name: wordpressuser" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:476 +msgid "Password: wp-example" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:478 +msgid "Re-type: wp-example" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:480 +msgid "" +"In the `Database for user account` section, select :guilabel:`Grant all " +"privileges on database “WordPress”.`" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:483 +msgid "At the bottom of the page, click :guilabel:`Go`." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:485 +msgid "If successful, you should see the screen shown in figure 8:" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:491 +msgid "`Figure 8: The user wordpressuser is successfully added.`" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:493 +msgid "**Congratulations!**" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:495 +msgid "" +"You have now created a fully functional LAMP server along with a " +"WordPress\\*-ready database using |CL|." +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:499 +msgid "Next steps" +msgstr "" + +#: ../../tutorials/wordpress/web-server-install.rst:501 +msgid "" +"Next, add the WordPress components needed to host a WordPress website " +"with :ref:`wp-install`." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/wordpress/wordpress.po b/locale/zh_CN/LC_MESSAGES/tutorials/wordpress/wordpress.po new file mode 100644 index 00000000..78f37045 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/wordpress/wordpress.po @@ -0,0 +1,51 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/wordpress/wordpress.rst:4 +msgid "WordPress\\* on |CL-ATTR|" +msgstr "" + +#: ../../tutorials/wordpress/wordpress.rst:6 +msgid "" +"This tutorial describes how to setup a web server to host a WordPress\\* " +"site on a |CL-ATTR| system. The tutorial is split into two sections:" +msgstr "" + +#: ../../tutorials/wordpress/wordpress.rst:9 +msgid ":ref:`web-server-install`" +msgstr "" + +#: ../../tutorials/wordpress/wordpress.rst:11 +msgid ":ref:`wp-install`" +msgstr "" + +#: ../../tutorials/wordpress/wordpress.rst:13 +msgid "" +"If you already have a |CL| based :abbr:`LAMP (Linux, Apache, MySQL, PHP)`" +" web server, you can skip ahead to the second section of this tutorial." +msgstr "" + +#: ../../tutorials/wordpress/wordpress.rst:18 +msgid "" +"This tutorial is for development and testing purposes only. Additional " +"steps are required to secure production systems. Those steps are beyond " +"the scope of this tutorial." +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/wordpress/wp-install.po b/locale/zh_CN/LC_MESSAGES/tutorials/wordpress/wp-install.po new file mode 100644 index 00000000..243b1128 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/wordpress/wp-install.po @@ -0,0 +1,293 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/wordpress/wp-install.rst:4 +msgid "Set up WordPress\\* on a LAMP web server" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:6 +msgid "" +"This tutorial shows you how to install the WordPress\\* components on " +"your |CL| :abbr:`LAMP (Linux, Apache, MySQL, PHP)` server. At the end of " +":ref:`web-server-install`, you created a WordPress-ready database using " +"phpMyAdmin\\* and MariaDB\\*. Now that the LAMP server is up and running," +" you can add the WordPress components needed to host a WordPress website " +"on your system." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:13 +msgid "Before you begin" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:15 +msgid "" +"This tutorial assumes that you have successfully completed :ref:`bare-" +"metal-install-desktop` and you have :ref:`web-server-install`." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:19 +msgid "Create a WordPress server" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:21 +msgid "" +"WordPress can be installed in a variety of ways. These instructions are " +"written for users who have followed our instructions for installing " +"phpMyAdmin when they :ref:`set up a LAMP web server `. Note that all steps in this tutorial have been tested using a " +"NUC6i5SYH Intel® NUC. Visit the `NUC6i5SYH product page`_ for detailed " +"information." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:27 +msgid "" +"Numerous online articles are available to help you name your website and " +"acquire the necessary certificates. Those tasks are beyond the scope of " +"this tutorial." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:30 +msgid "" +"You can take several actions to harden your website from attacks. The " +"security of your website and the data it contains are complex and ever-" +"evolving tasks. Prioritize security if you plan to expose your website to" +" the outside world. This tutorial does not address security measures that" +" you can take to harden your site but we strongly encourage you to take " +"action." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:38 +msgid "" +"Throughout this tutorial, we reference your website name as " +"." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:42 +msgid "Download WordPress and manage directories" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:44 +msgid "" +"For this tutorial, you will create a WordPress blog that can be accessed " +"at: \\http:///blog." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:47 +msgid "" +"To accomplish this setup, you must add WordPress components to the " +":file:`/var/www/html/blog` directory." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:50 +msgid "Follow these steps:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:53 +msgid "Navigate to the top level of the website’s root directory:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:59 +msgid "Download the latest version of WordPress:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:65 +msgid "Extract all files and directories from the downloaded file:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:71 +msgid "Rename the top-level WordPress directory to “blog”:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:77 +msgid "Remove the downloaded tar file:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:84 +msgid "Set up WordPress with web-based GUI" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:86 +msgid "" +"Recall that you created a database and user when you installed phpMyAdmin" +" when you set up a |CL| based :ref:`web server `. " +"Next, you must connect WordPress to the database and install WordPress." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:90 +msgid "" +"To continue with the setup, go to: \\http:///blog/wp-" +"admin/install.php. The WordPress language option screen appears, as shown" +" in figure 1." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:93 +msgid "Select :guilabel:`English` and click :guilabel:`Continue`." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:99 +msgid "`Figure 1: WordPress language selection screen.`" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:102 +msgid "" +"The WordPress installation continues until the Welcome screen appears, as" +" shown in figure 2:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:109 +msgid "`Figure 2: WordPress Welcome screen.`" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:111 +msgid "Click :guilabel:`Let’s go!`." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:113 +msgid "" +"Enter database connection specifics in the screen that appears, as shown " +"in figure 3 below." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:116 +msgid "Database name: WordPress" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:117 +msgid "Database username: wordpressuser" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:118 +msgid "" +"Database password: wp-example (asterisks will not appear in the text " +"box)" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:119 +msgid "Database host: localhost" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:120 +msgid "Table prefix: wp\\_" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:126 +msgid "" +"`Figure 3: Information necessary for WordPress to connect to the " +"database.`" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:128 +msgid "Click :guilabel:`Submit` to complete the setup." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:130 +msgid "" +"Figure 4 shows the confirmation screen that verifies a successful setup. " +"WordPress is connected to the MariaDB database." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:137 +msgid "`Figure 4: Successful WordPress connection.`" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:139 +msgid "" +"Click :guilabel:`Run the install`. The installer runs until WordPress is " +"fully installed on your system." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:143 +msgid "Complete successful login" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:145 +msgid "" +"Once the installation is complete, you can name your blog and create a " +"WordPress username and password. See figure 5." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:152 +msgid "`Figure 5: WordPress site information screen.`" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:155 +msgid "Enter all required information." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:156 +msgid "Click :guilabel:`Install WordPress`." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:157 +msgid "" +"Verify that the initial login screen appears once the installation is " +"complete. See figure 6:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:163 +msgid "`Figure 6: The WordPress login screen.`" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:165 +msgid "Enter your WordPress username and password." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:166 +msgid "Check :guilabel:`Remember me` to save your credentials." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:167 +msgid "Click :guilabel:`Log in`." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:169 +msgid "Figure 7 shows the WordPress dashboard after a successful login:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:175 +msgid "`Figure 7: The WordPress dashboard.`" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:177 +msgid "You are ready to go!" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:179 +msgid "" +"To check out your blog as it is seen by the outside world, enter: " +"\\http:///blog on your browser. Figure 8 shows the result:" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:186 +msgid "`Figure 8: Your WordPress blog.`" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:188 +msgid "**Congratulations, your WordPress blog is up and running!**" +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:190 +msgid "You have successfully installed WordPress on a host system." +msgstr "" + +#: ../../tutorials/wordpress/wp-install.rst:192 +msgid "Add new entries to your blog and share them with the world using |CL|!" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/yubikey-u2f.po b/locale/zh_CN/LC_MESSAGES/tutorials/yubikey-u2f.po new file mode 100644 index 00000000..5f511f39 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/yubikey-u2f.po @@ -0,0 +1,159 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019, many +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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" + +#: ../../tutorials/yubikey-u2f.rst:4 +msgid "Enable YubiKey U2F Support" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:6 +msgid "" +"YubiKey\\* is a USB security token manufactured by `Yubico`_. Depending " +"on the model, a YubiKey can support different authentication protocols " +"including: One-Time Password (OTP), Smart card, FIDO2, and Universal 2nd " +"Factor (U2F)." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:10 +msgid "" +"These instructions will go over configuring a YubiKey for U2F " +"authentication through a web browser on a |CL-ATTR| system." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:13 +msgid "" +"A list of `websites accepting U2F authentication with the YubiKey`_ is " +"available on the Yubico website. See the Yubico website to learn more " +"about the Yubikey: https://www.yubico.com/getstarted/meet-the-yubikey/" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:26 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:28 +msgid "This tutorial assumes you have:" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:30 +msgid "|CL| installed and running." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:32 +msgid "Mozilla Firefox installed on |CL|." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:34 +msgid "A YubiKey." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:39 +msgid "Enable Linux udev rules for YubiKey" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:41 +msgid "" +":command:`udev` is the Linux device manager which handles events when USB" +" devices are added and removed. Custom rules needs to be created to " +"properly identify the YubiKey and provide applications access." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:45 +msgid "" +"These instructions are derived from: `Yubico support article Using Your " +"U2F YubiKey with Linux " +"`_" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:50 +msgid "Create the udev rules folder under :file:`/etc`" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:57 +msgid "Download the u2f rules from the Yubico GitHub:" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:64 +msgid "" +"Move the downloaded :file:`70-u2f.rules` file into the :file:`/etc/udev` " +"folder" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:72 +msgid "" +"The udev rules should automatically be reloaded. However, they can be " +"manually reloaded or reboot the system:" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:80 +msgid "Plugin and validate the YubiKey appears as a USB device:" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:89 +msgid "Enable U2F in Mozilla Firefox" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:91 +msgid "" +"Firefox comes with U2F web authentication support disabled by default. " +"U2F needs to be enabled in the advanced settings." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:94 +msgid "" +"These instructions are derived from: `Yubico support article Enabling U2F" +" support in Mozilla Firefox " +"`_" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:99 +msgid "Launch Mozilla Firefox" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:101 +msgid "" +"In the URL bar, type :command:`about:config` to access the advanced " +"settings." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:108 +msgid "Click the *I accept the risk!* button to continue to the advanced settings" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:110 +msgid "" +"Search for the :command:`security.webauth.u2f` and double-click it so " +"*Value* becomes **true**." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:114 +msgid "" +"Your YubiKey is now usable on |CL| with Mozilla Firefox with websites " +"that support U2F authentication." +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:119 +msgid "Related topics" +msgstr "" + +#: ../../tutorials/yubikey-u2f.rst:121 +msgid "|CL| :ref:`security`" +msgstr "" + diff --git a/source/conf.py b/source/conf.py index 7c651f8a..716011c5 100644 --- a/source/conf.py +++ b/source/conf.py @@ -326,3 +326,8 @@ html_add_permalinks = "" #suppresses warnings for options that aren't referenced #suppress_warnings = ["ref.option"] + +# -- Options for Localization using sphinx-intl --------------------------- + +locale_dirs = ['../locale/'] # path for lang-specific po files. +gettext_compact = False # optional. \ No newline at end of file