From f57f53c0189b96a426ab033b19a8a808d3e1b269 Mon Sep 17 00:00:00 2001 From: Sergey Cherevko Date: Thu, 19 Dec 2024 21:34:38 +0300 Subject: [PATCH 08/15] Replace Fedora references and update translations --- data/liveinst/gnome/fedora-welcome.js | 6 +++--- .../gnome/org.fedoraproject.welcome-screen.desktop | 3 ++- docs/intro.rst | 4 ++-- docs/iscsi.rst | 8 ++++---- 4 files changed, 11 insertions(+), 10 deletions(-) diff --git a/data/liveinst/gnome/fedora-welcome.js b/data/liveinst/gnome/fedora-welcome.js index fc42e5d..61e11ff 100755 --- a/data/liveinst/gnome/fedora-welcome.js +++ b/data/liveinst/gnome/fedora-welcome.js @@ -46,7 +46,7 @@ class WelcomeWindow extends Adw.ApplicationWindow { } constructor(application) { - const title = _('Welcome to Fedora!'); + const title = _('Welcome to MSVSphere!'); super({ application, title, @@ -58,7 +58,7 @@ class WelcomeWindow extends Adw.ApplicationWindow { const statusPage = new Adw.StatusPage({ title, iconName: 'fedora-logo-icon', - description: _('This live media can be used to install Fedora or as a temporary system. Installation can be started at any time using the install icon in Activities.'), + description: _('This live media can be used to install MSVSphere or as a temporary system. Installation can be started at any time using the install icon in Activities.'), }); this.content.set_child(statusPage); @@ -71,7 +71,7 @@ class WelcomeWindow extends Adw.ApplicationWindow { statusPage.set_child(buttonBox); const installButton = new Gtk.Button({ - label: _('Install Fedora…'), + label: _('Install MSVSphere…'), actionName: 'window.install-fedora', }); installButton.add_css_class('pill'); diff --git a/data/liveinst/gnome/org.fedoraproject.welcome-screen.desktop b/data/liveinst/gnome/org.fedoraproject.welcome-screen.desktop index c3551b1..60ab503 100644 --- a/data/liveinst/gnome/org.fedoraproject.welcome-screen.desktop +++ b/data/liveinst/gnome/org.fedoraproject.welcome-screen.desktop @@ -1,5 +1,6 @@ [Desktop Entry] -Name=Welcome to Fedora +Name=Welcome to MSVSphere +Name[ru]=Добро пожаловать в МСВСфера Icon=fedora-logo-icon Exec=/usr/share/anaconda/gnome/fedora-welcome Terminal=false diff --git a/docs/intro.rst b/docs/intro.rst index 3c62e77..d4b7f53 100644 --- a/docs/intro.rst +++ b/docs/intro.rst @@ -1,8 +1,8 @@ Introduction to Anaconda ======================== -Anaconda is the installation program used by Fedora, Red Hat Enterprise Linux -and some other distributions. +Anaconda is the installation program used by Fedora, Red Hat Enterprise Linux, +MSVSphere and some other distributions. During installation, a target computer's hardware is identified and configured and the appropriate file systems for the system's architecture are created. diff --git a/docs/iscsi.rst b/docs/iscsi.rst index 847078d..1f1d377 100644 --- a/docs/iscsi.rst +++ b/docs/iscsi.rst @@ -16,8 +16,8 @@ The terminology: - 'initiator', the client in the iscsi connection. The computer we are running Anaconda on is typically an initiator. - 'target', the storage device behind the Network. This is where the data is - physically stored and read from. You can turn any Fedora/RHEL machine to a - target (or several) via scsi-target-utils. + physically stored and read from. You can turn any Fedora/RHEL/MSVSphere machine + to a target (or several) via scsi-target-utils. - 'HBA' or Host Bus Adapter. A device (PCI card typically) you connect to a computer. It acts as a NIC and if you configure it properly it transparently connects to the target when started and all you can see is a block device on @@ -25,7 +25,7 @@ The terminology: - 'software initiator' is what you end up with if you emulate most of what HBA is doing and just use a regular NIC for the iscsi communication. The modern Linux kernel has a software initiator. To use it, you need the Open-ISCSI software - stack [1, 2] installed. It is known as iscsi-initiator-utils in Fedora/RHEL. + stack [1, 2] installed. It is known as iscsi-initiator-utils in Fedora/RHEL/MSVSphere. - 'partial offload card'. Similar to HBA but needs some support from kernel and iscsi-initiator-utils. The least pleasant to work with, particularly because there is no standardized amount of the manual setting that needs to be done @@ -139,7 +139,7 @@ If for some reason the DeviceTree fails at recognizing iscsi devices as such, The booting problems are either due to incorrectly generated dracut boot arguments or they are simply dracut bugs. -Note that many of the iscsi adapters are installed in different Red Hat machines +Note that many of the iscsi adapters are installed in different MSVSphere machines and so the issues can often be reproduced and debugged. -- 2.43.5