Zen

Translation

English (itstool) path: sect2/para
openSUSE minimizes the risk by not writing more than the bare minimum required to boot the OS. The minimum means telling the UEFI firmware about the location of the openSUSE boot loader. Upstream Linux kernel features that use the UEFI storage area for storing boot and crash information (<literal>pstore</literal>) have been disabled by default. Nevertheless, it is recommended to install any firmware updates the hardware vendor recommends.
441/4420 · 442

Sign in to save the translation.

English Marathi Actions
Currently, YaST does not work with transactional updates. This is because YaST performs things immediately and because it cannot edit a read-only filesystem.
 
To work with transactional updates, always use the command <command>transactional-update</command> instead of YaST and Zypper for all software management:
 
Update the system: <command>transactional-update up</command>
 
Install a package: <command>transactional-update pkg in <replaceable>PACKAGE_NAME</replaceable></command>
 
Remove a package: <command>transactional-update pkg rm <replaceable>PACKAGE_NAME</replaceable></command>
 
To revert the last snapshot, that is the last set of changes to the root file system, make sure your system is booted into the next to last snapshot and run: <command>transactional-update rollback</command>
 
Optionally, add a snapshot ID to the end of the command to rollback to a specific ID.
 
When using this system role, by default, the system will perform a daily update and reboot between 03:30 am and 05:00 am. Both of these actions are systemd-based and if necessary can be disabled using <command>systemctl</command>:
 
systemctl disable --now transactional-update.timer rebootmgr.service
 
For more information about transactional updates, see the openSUSE Kubic blog posts <link xlink:href="https://kubic.opensuse.org/blog/2018-04-04-transactionalupdates/"/> and <link xlink:href="https://kubic.opensuse.org/blog/2018-04-20-transactionalupdates2/"/>.
अधिक माहितीसाठी, पहा <link href="https://bugzilla.suse.com/show_bug.cgi?id=1044816"/>.
Installing on Hard Disks With Less Than 12 GB of Capacity
 
The installer will only propose a partitioning scheme if the available hard disk size is larger than 12 GB. If you want to set up, for example, very small virtual machines images, use the guided partitioner to tune partitioning parameters manually.
 
UEFI—Unified Extensible Firmware Interface
UEFI- युनिफाइड एक्सटेंसिबल फर्मवेअर इंटरफेस
Prior to installing openSUSE on a system that boots using UEFI (Unified Extensible Firmware Interface), you are urgently advised to check for any firmware updates the hardware vendor recommends and, if available, to install such an update. A pre-installation of Windows 8 or later is a strong indication that your system boots using UEFI.
UEFI (युनिफाइड एक्स्टेंसिबल फर्मवेअर इंटरफेस) चा वापर करून बूट होणाऱ्या प्रणालीवर ओपन सोस स्थापित करण्याआधी, हार्डवेअर विक्रेता शिफारस केलेल्या कोणत्याही फर्मवेअर अद्यतनांसाठी आणि जर उपलब्ध असेल तर, अशी अद्ययावत स्थापित करण्याची तात्काळ सल्ला घ्यावी. विंडोज 8 किंवा नंतरचे प्रि-इंस्टॉलेशन एक मजबूत संकेत आहे जो तुमची प्रणाली UEFI वापरुन बूट करतो.
<emphasis>Background:</emphasis> Some UEFI firmware has bugs that cause it to break if too much data gets written to the UEFI storage area. However, there is no clear data of how much is <quote>too much</quote>.
<emphasis>1Background: </emphasis> काही UEFI फर्मवेअरमध्ये बग आहेत जे UEFI स्टोरेज एरियामध्ये खूप जास्त डेटा लिहील्यास ते खंडित होऊ शकतात. मात्र, किती स्पष्ट आहे की <quote> 3 टू जास्त </ quote> 4 आहे.
openSUSE minimizes the risk by not writing more than the bare minimum required to boot the OS. The minimum means telling the UEFI firmware about the location of the openSUSE boot loader. Upstream Linux kernel features that use the UEFI storage area for storing boot and crash information (<literal>pstore</literal>) have been disabled by default. Nevertheless, it is recommended to install any firmware updates the hardware vendor recommends.
ओपनसुसे ओएस बूट करण्यासाठी आवश्यक किमान पेक्षा जास्त लिहित नसल्यामुळे धोका कमी करतो. ओपनस्यूज बूट लोडरच्या स्थानाविषयी UEFI फर्मवेयरला सांगण्याचे किमान म्हणजे म्हणजे अपस्ट्रीम Linux कर्नल गुणविशेष जे बूट व क्रॅश माहिती (<literal>1pstore </ literal> 2) साठवण्याकरिता UEFI स्टोरेज क्षेत्रास मुलभूतरित्या अकार्यान्वीत केले गेले आहे. असे असले तरी, हार्डवेअर विक्रेता शिफारस केलेल्या कोणत्याही फर्मवेअर अद्ययावत स्थापित करण्याची शिफारस केली जाते.
UEFI, GPT, and MS-DOS Partitions
UEFI, GPT, आणि MS-DOS विभाजने
Together with the EFI/UEFI specification, a new style of partitioning arrived: GPT (GUID Partition Table). This new schema uses globally unique identifiers (128-bit values displayed in 32 hexadecimal digits) to identify devices and partition types.
EFI / UEFI निर्देशसह, विभाजनप्रणालीची एक नवीन शैली आली आहे: GPT (GUID विभाजन तक्ता). ही नवीन स्कीमा जागतिक पातळीवर अद्वितीय अभिज्ञापक (32 हेक्साडेसिमल अंकांमध्ये प्रदर्शित होणारे 128-बिट मूल्य) वापरते आणि डिव्हाइसेस आणि विभाजन प्रकार ओळखण्यासाठी.
Additionally, the UEFI specification also allows legacy MBR (MS-DOS) partitions. The Linux boot loaders (ELILO or GRUB 2) try to automatically generate a GUID for those legacy partitions, and write them to the firmware. Such a GUID can change frequently, causing a rewrite in the firmware. A rewrite consists of two different operations: Removing the old entry and creating a new entry that replaces the first one.
याव्यतिरिक्त, UEFI निर्देशन लेगसी MBR (MS-DOS) विभाजनांना देखील परवानगी देते. लिनक्स बूट लोडर्स (ELILO किंवा GRUB 2) त्या लीगेसी विभाजनांकरीता स्वयं GUID निर्माण करण्याचा प्रयत्न करतात, आणि त्यास फर्मवॅरवर लिहा. अशी GUID वारंवार बदलू शकते, ज्यामुळे फर्मवेअरमध्ये पुनर्लेखन होऊ शकते. पुनर्रचनामध्ये दोन वेगळ्या ऑपरेशन असतात: जुने प्रविष्टी काढून टाकणे आणि एक नवीन एंट्री तयार करणे जे पहिल्या एकला पुनर्स्थित करते.
Modern firmware has a garbage collector that collects deleted entries and frees the memory reserved for old entries. A problem arises when faulty firmware does not collect and free those entries. This can result in a non-bootable system.
आधुनिक फर्मवेअरमध्ये कचऱ्याचे कलेक्टर आहेत जे हटविलेल्या नोंदी एकत्रित करते आणि जुन्या नोंदींसाठी आरक्षित मेमरी मुक्त करते. समस्या उद्भवली जेव्हा दोषपूर्ण फर्मवेअरने त्या प्रविष्ट्या गोळा केल्या नाहीत आणि मुक्त केले नाहीत यामुळे नॉन-बूटेबल सिस्टम होऊ शकते.
To work around this problem, convert the legacy MBR partition to GPT.
या समस्येवर उपाय म्हणून, लेगसी एमबीआर विभाजन जीपीटीमध्ये रूपांतरित करा.
System Upgrade
सिस्टम श्रेणीसुधार
This section lists notes related to upgrading the system. For supported scenarios and detailed upgrade instructions, see the documentation at:
या विभागात प्रणाली सुधारीत करण्यासंबंधीची नोट्स समाविष्टीत आहे. तपशीलवार अपग्रेड सूचनांसाठी, दस्तऐवजीकरण पहा <link href="https://doc.opensuse.org/documentation/leap/startup/html/book.opensuse.startup/cha.update.osuse.html"/>.
Make sure to also review the following sections of this documentation:
 
Repository Path Updates
 
<emphasis role="strong">Repository Location Changes:</emphasis> Starting with Leap 15.5, the ppc64le and aarch64 versions are no longer stored under <literal>ports</literal> (see below). The amv7hl architecture remains unchanged.
 
<emphasis role="strong">For Upgrading Users:</emphasis> If you're moving from Leap 15.3 or earlier, switch to the new repository locations. Old paths are obsolete. New path details are available <link xlink:href="https://en.opensuse.org/SDB:System_upgrade#Note_about_ports_(non_intel_architectures)">here</link>.
 
<emphasis role="strong">Easy Upgrade Tip:</emphasis> Download and install the <literal>openSUSE-repos-Leap</literal> package for automatic path updates. Get it <link xlink:href="https://software.opensuse.org/package/openSUSE-repos-Leap">here</link>.
 
Packaging Changes
 
Deprecated Packages
 
Deprecated packages are still shipped as part of the distribution but are scheduled to be removed the next version of openSUSE Leap. These packages exist to aid migration, but their use is discouraged and they may not receive updates.
 

Loading…

No matching activity found.
Browse all string changes

Things to check

Consecutive duplicated words

Text contains the same word twice in a row: म्हणजे

Reset

XML syntax

The translation is not valid XML

Reset

Glossary

English Marathi
No related strings found in the glossary.

String information

Source string description
(itstool) path: sect2/para
Source string location
xml/release-notes.xml:251
String age
a year ago
Last updated
a month ago
Source string age
a year ago
Translation file
po/mr.po, string 50