List of Examples 2.1 AutoYaST control file (profile) 2.2 Control file container 2.3 Nested resources 2.4 An empty map 3.1 Example file for replacing the host name/domain by script 4.1 General options 4.2 Reporting behavior 4.3 LVM-based guided partitioning 4.4 Creating /, /home and swap partitions 4.5 Using a whole disk as a file system 4.6 Automated partitioning on selected drives 4.7 Installing on multiple drives 4.8 Mount options 4.9 Keeping partitions 4.10 Auto-detection of partitions to be kept. Make sure to backup your /home directory and any configuration files you want to save.Preface Available documentation Improving the documentation Documentation conventions 1 Introduction to AutoYaST 1.1 Motivation 1.2 Overview and concept I Understanding and creating the AutoYaST control file 2 The AutoYaST control file 2.1 Introduction 2.2 Format 2.3 Structure 3 Creating an AutoYaST control file 3.1 Collecting information 3.2 Using the configuration management system (CMS) 3.3 Creating/editing a control file manually 3.4 Creating a control file via script with XSLT 3.5 Checking a control file II AutoYaST configuration examples 4 Configuration and installation options 4.1 General options 4.2 Reporting 4.3 The boot loader 4.4 Partitioning 4.5 iSCSI initiator overview 4.6 Fibre channel over Ethernet configuration (FCoE) 4.7 Country settings 4.8 Software 4.9 Upgrade 4.10 Services and targets 4.11 Network configuration 4.12 Proxy 4.13 NIS client and server 4.14 NIS server 4.15 Hosts definition 4.16 Windows domain membership 4.17 Samba server 4.18 Authentication client 4.19 NFS client and server 4.20 NTP client 4.21 Mail server configuration 4.22 Apache HTTP server configuration 4.23 Squid server 4.24 FTP server 4.25 TFTP server 4.26 Firstboot workflow 4.27 Security settings 4.28 Linux audit framework (LAF) 4.29 Users and groups 4.30 Custom user scripts 4.31 System variables (sysconfig) 4.32 Adding complete configurations 4.33 Ask the user for values during installation 4.34 Kernel dumps 4.35 DNS server 4.36 DHCP server 4.37 Firewall configuration 4.38 Miscellaneous hardware and system components 4.39 Importing SSH keys and configuration 4.40 Configuration management III Managing mass installations with dynamic profiles 5 Supported approaches to dynamic profiles 6 Rules and classes 6.1 Rule-based automatic installation 6.2 Classes 6.3 Mixing rules and classes 6.4 Merging of rules and classes 7 ERB templates 7.1 What is ERB? 7.2 Template helpers 7.3 Running ERB helpers 7.4 Rendering ERB profiles 7.5 Debugging ERB profiles 7.6 ERB compared to rules and classes 8 Combining ERB templates and scripts 8.1 Embedding ERB in your scripts 8.2 Accessing ERB helpers from Ruby scripts IV Understanding the auto-installation process 9 The auto-installation process 9.1 Introduction 9.2 Choosing the right boot medium 9.3 Invoking the auto-installation process 9.4 System configuration V Uses for AutoYaST on installed systems 10 Running AutoYaST in an installed system VI Appendixes A Handling rules B AutoYaST FAQ-frequently asked questions C Advanced linuxrc options C.1 Passing parameters to linuxrc C.2 info file format C.3 Advanced network setup D GNU licenses D.1 GNU Free Documentation License Users interested in changing from the point release version can look at moving to Tumbleweed, which has frequent updates, or to a next generation operating system like MicroOS. Leap 15.5 is expected to be released at the beginning of June 2023, according to the roadmap. The Leap 15.4 release is expected to be maintained and supported with security patches until it reaches its EOL in November 2023. įor new installations, download openSUSE Leap 15.4 images at. Users can upgrade from 15.3 to 15.4 by downloading the iso image or following the instructions on how to upgrade, which is found on. This is why users need to upgrade to the newer minor release openSUSE Leap 15.4! 30, but the lifecycle of Leap is frequently communicated to users.Īn EOL ends updates for the operating system minor version and those who continue to use EOL versions will be exposed to vulnerabilities because these discontinued versions no longer receive security and maintenance updates. Marcus Meissner gave users advanced notice on the announcements mailing list on Nov. Users of openSUSE Leap 15.3 will not be receiving security and maintenance updates once the version goes EOL (end of life) on the last day of 2022.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |