Mini Shell
3
�
Ld�q � @ s d Z ddlmZmZmZmZmZmZmZ ddl m
Z
ddl m Z ddl
mZmZmZmZmZmZmZmZ ddlmZ G dd� de�ZG d d
� d
e�ZG d d � d e�ZG d
d� de�Z G dd� de�Z G dd� de�Z G dd� de�Z G dd� de �Z G dd� de�Z!dS )a�
This module exports the classes that define a section of a kickstart file. A
section is a chunk of the file starting with a %tag and ending with a %end.
Examples of sections include %packages, %pre, and %post.
You may use this module to define your own custom sections which will be
treated just the same as a predefined one by the kickstart parser. All that
is necessary is to create a new subclass of Section and call
parser.registerSection with an instance of your new class.
� )�
KS_SCRIPT_PRE�KS_SCRIPT_POST�KS_SCRIPT_TRACEBACK�KS_SCRIPT_PREINSTALL�KS_SCRIPT_ONERROR�KS_MISSING_IGNORE�KS_MISSING_PROMPT)�KickstartParseError)�KSOptionParser)�FC4�F7�F9�F18�F21�F22�F24�RHEL7)�_c @ sH e Zd ZdZdZdZdZdd� Zdd� Zd d
� Z d d � Z
e d
d� �Z dS )�Sectiona� The base class for defining kickstart sections. You are free to
subclass this as appropriate.
Class attributes:
allLines -- Does this section require the parser to call handleLine
for every line in the section, even blanks and comments?
sectionOpen -- The string that denotes the start of this section. You
must start your tag with a percent sign.
timesSeen -- This attribute is for informational purposes only. It is
incremented every time handleHeader is called to keep
track of the number of times a section of this type is
seen.
F� r c K s" || _ | j j| _|jdd�| _dS )a- Create a new Script instance. At the least, you must pass in an
instance of a baseHandler subclass.
Valid kwargs:
dataObj -- A class that should be populated by this Section. It almost
always should be Script, or some subclass of it.
�dataObjN)�handler�version�getr )�selfr �kwargs� r � /usr/lib/python3.6/sections.py�__init__; s
zSection.__init__c C s dS )zvThis method is called when the %end tag for a section is seen. It
is not required to be provided.
Nr )r r r r �finalizeI s zSection.finalizec C s dS )a8 This method is called for every line of a section. Take whatever
action is appropriate. While this method is not required to be
provided, not providing it does not make a whole lot of sense.
Arguments:
line -- The complete line, with any trailing newline.
Nr )r �liner r r �
handleLineN s zSection.handleLinec C s | j d7 _ dS )a< This method is called when the opening tag for a section is seen.
Not all sections will need this method, though all provided with
kickstart include one.
Arguments:
args -- A list of all strings passed as arguments to the section
opening tag.
� N)� timesSeen)r �lineno�argsr r r � handleHeaderY s
zSection.handleHeaderc C s
| j dkS )z�This property is given for consistency with KickstartCommand objects
only. It simply returns whether timesSeen is non-zero.
r )r# )r r r r �seenf s z Section.seenN)
�__name__�
__module__� __qualname__�__doc__�allLines� sectionOpenr# r r r! r& �propertyr' r r r r r ( s
r c @ s4 e Zd ZdZdZdd� Zdd� Zdd� Zd d
� Zd S ) � NullSectiona, This defines a section that pykickstart will recognize but do nothing
with. If the parser runs across a %section that has no object registered,
it will raise an error. Sometimes, you may want to simply ignore those
sections instead. This class is useful for that purpose.
Tc O s. t j| f|�|� |jd�| _g | _g | _dS )z�Create a new NullSection instance. You must pass a sectionOpen
parameter (including a leading '%') for the section you wish to
ignore.
r- N)r r r r- �_args�_body)r r% r r r r r u s zNullSection.__init__c C s
|| _ d S )N)r0 )r r$ r% r r r r& s zNullSection.handleHeaderc C s | j j|� d S )N)r1 �append)r r r r r r! � s zNullSection.handleLinec C sT dj | j�}|r&ddj | j�|f }nddj | j� }| jjj|� g | _g | _d S )N�
z %s
%s
%%end� z%s
%%end)�joinr1 r0 r Z_null_section_stringsr2 )r �body�sr r r r � s zNullSection.finalizeN) r( r) r* r+ r, r r& r! r r r r r r/ m s
r/ c @ sL e Zd ZdZdZdZdZdd� Zdd� Zdd� Z d d
� Z
d d � Z d
d� Z dS )�
ScriptSectionTr c O s$ t j| f|�|� i | _| j� d S )N)r r �_script� _resetScript)r r% r r r r r � s zScriptSection.__init__c C s^ t | j| j| j| jdd�}|jdddddtd� |jdd d
td d d
� |jdddtdd� |S )NF)�prog� description�epilogr �
addVersionz
--erroronfail� errorOnFail�
store_truea
If the error script fails, this option will cause an
error dialog to be displayed and will halt installation.
The error message will direct you to where the cause of
the failure is logged.)�dest�action�default�help�
introducedz
--interpreter� interpreterz/bin/shz/usr/bin/pythonz�
Allows you to specify a different scripting language,
such as Python. Replace /usr/bin/python with the
scripting language of your choice.
)rA rC rE �metavarrD z--logz --logfile�logzi
Log all messages from the script to the given log file.
)rA rE rD )r
r- � _description�_epilogr � add_argumentr )r �opr r r �
_getParser� s
zScriptSection._getParserc C s dd dd dg d�| _ d S )Nz/bin/shF)�interprH r? r$ �chrootr6 )r9 )r r r r r: � s zScriptSection._resetScriptc C s | j d j|� d S )Nr6 )r9 r2 )r r r r r r! � s zScriptSection.handleLinec C s� dj | jd �j� dkr d S | jd | jd | jd | jd | jd | jd d
�}| jd k r�| j| jd f|�}| j� | jjj|� d S ) Nr4 r6 r rN rO r$ rH r? �type)rN ZinChrootr$ Zlogfiler? rP )r5 r9 �stripr r: r �scriptsr2 )r r r7 r r r r � s
zScriptSection.finalizec C sv t j| ||� | j� }|j|dd� |d�}|j| jd< || jd< |j| jd< |j| jd< t|d�rr|j | jd < dS )
z�Process the arguments to a %pre/%post/%traceback header for later
setting on a Script instance once the end of the script is found.
This method may be overridden in a subclass if necessary.
r" N)r% r$ rN r$ rH r? �nochrootrO )
r r& rM �
parse_argsrF r9 rH r? �hasattrrS )r r$ r% rL �nsr r r r& � s
zScriptSection.handleHeaderN)
r( r) r* r, rI rJ �_titler rM r: r! r r& r r r r r8 � s r8 c @ s$ e Zd ZdZdZdZdZdd� ZdS )�PreScriptSectionz%prezPre-installation scripta�
You can add commands to run on the system immediately after the ks.cfg
has been parsed and the lang, keyboard, and url options have been
processed. This section must be at the end of the kickstart file (after
the commands) and must start with the %pre command. You can access the
network in the %pre section; however, name service has not been
configured at this point, so only IP addresses will work.
Preinstallation scripts are required to be closed with %end.
If your script spawns a daemon process, you must make sure to close
``stdout`` and ``stderr``. Doing so is standard procedure for creating
daemons. If you do not close these file descriptors, the installation
will appear hung as anaconda waits for an EOF from the script.
.. note::
The pre-install script is not run in the chroot environment.
a�
Example
-------
Here is an example %pre section::
%pre
#!/bin/bash
hds=""
mymedia=""
for file in /sys/block/sd*; do
hds="$hds $(basename $file)"
done
set $hds
numhd=$(echo $#)
drive1=$(echo $hds | cut -d' ' -f1)
drive2=$(echo $hds | cut -d' ' -f2)
if [ $numhd == "2" ] ; then
echo "#partitioning scheme generated in %pre for 2 drives" > /tmp/part-include
echo "clearpart --all" >> /tmp/part-include
echo "part /boot --fstype ext4 --size 512 --ondisk sda" >> /tmp/part-include
echo "part / --fstype ext4 --size 10000 --grow --ondisk sda" >> /tmp/part-include
echo "part swap --recommended --ondisk $drive1" >> /tmp/part-include
echo "part /home --fstype ext4 --size 10000 --grow --ondisk sdb" >> /tmp/part-include
else
echo "#partitioning scheme generated in %pre for 1 drive" > /tmp/part-include
echo "clearpart --all" >> /tmp/part-include
echo "part /boot --fstype ext4 --size 521" >> /tmp/part-include
echo "part swap --recommended" >> /tmp/part-include
echo "part / --fstype ext4 --size 2048" >> /tmp/part-include
echo "part /home --fstype ext4 --size 2048 --grow" >> /tmp/part-include
fi
%end
This script determines the number of hard drives in the system and
writes a text file with a different partitioning scheme depending on
whether it has one or two drives. Instead of having a set of
partitioning commands in the kickstart file, include the line:
``%include /tmp/part-include``
The partitioning commands selected in the script will be used.
c C s t j| � t| jd< d S )NrP )r8 r: r r9 )r r r r r: # s
z PreScriptSection._resetScriptN)r( r) r* r- rW rI rJ r: r r r r rX � s
0rX c @ s e Zd ZdZdZdZdd� ZdS )�PreInstallScriptSectionz %pre-installzPre-install ScriptaC
You can use the %pre-install section to run commands after the system has been
partitioned, filesystems created, and everything is mounted under /mnt/sysimage
Like %pre these scripts do not run in the chrooted environment.
Each %pre-install section is required to be closed with a corresponding %end.
c C s t j| � t| jd< d S )NrP )r8 r: r r9 )r r r r r: 2 s
z$PreInstallScriptSection._resetScriptN)r( r) r* r- rW rI r: r r r r rY ' s rY c @ s, e Zd ZdZdZdZdZdd� Zdd� Zd S )
�PostScriptSectionz%postzPost-installation Scripta�
You have the option of adding commands to run on the system once the
installation is complete. This section must be at the end of the
kickstart file and must start with the %post command. This section is
useful for functions such as installing additional software and
configuring an additional nameserver.
You may have more than one %post section, which can be useful for cases
where some post-installation scripts need to be run in the chroot and
others that need access outside the chroot.
Each %post section is required to be closed with a corresponding %end.
If you configured the network with static IP information, including a
nameserver, you can access the network and resolve IP addresses in the %post
section. If you configured the network for DHCP, the /etc/resolv.conf file
has not been completed when the installation executes the %post section. You
can access the network, but you can not resolve IP addresses. Thus, if you
are using DHCP, you must specify IP addresses in the %post section.
If your script spawns a daemon process, you must make sure to close stdout
and stderr. Doing so is standard procedure for creating daemons. If you do
not close these file descriptors, the installation will appear hung as
anaconda waits for an EOF from the script.
The post-install script is run in a chroot environment; therefore, performing
tasks such as copying scripts or RPMs from the installation media will not
work.
a=
Examples
--------
Run a script named ``runme`` from an NFS share::
%post
mkdir /mnt/temp
mount 10.10.0.2:/usr/new-machines /mnt/temp
open -s -w -- /mnt/temp/runme
umount /mnt/temp
%end
Copy the file /etc/resolv.conf to the file system that was just
installed::
%post --nochroot
cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf
%end
**If your kickstart is being interpreted by the livecd-creator tool, you should
replace /mnt/sysimage above with $INSTALL_ROOT.**
c C s$ t j| �}|jddddtdd� |S )Nz
--nochrootrS r@ Fz�
Allows you to specify commands that you would like to
run outside of the chroot environment.)rA rB rC rE rD )r8 rM rK r )r rL r r r rM o s
z PostScriptSection._getParserc C s" t j| � d| jd< t| jd< d S )NTrO rP )r8 r: r9 r )r r r r r: w s
z PostScriptSection._resetScriptN) r( r) r* r- rW rI rJ rM r: r r r r rZ 6 s rZ c @ s e Zd ZdZdZdZdd� ZdS )�OnErrorScriptSectionz%onerrorzHandling Errorsa�
These scripts run when the installer hits a fatal error, but not necessarily
a bug in the installer. Some examples of these situations include errors in
packages that have been requested to be installed, failures when starting VNC
when requested, and error when scanning storage. When these situations happen,
installaton cannot continue. The installer will run all %onerror scripts in
the order they are provided in the kickstart file.
In addition, %onerror scripts will be run on a traceback as well. To be exact,
all %onerror scripts will be run and then all %traceback scripts will be run
afterwards.
Each %onerror script is required to be closed with a corresponding %end.
.. note::
These scripts could potentially run at
any stage in installation - early on, between making filesystems and installing
packages, before the bootloader is installed, when attempting to reboot, and
so on. For this reason, these scripts cannot be run in the chroot environment
and you should not trust anything in the installed system. These scripts are
primarily for testing and error reporting purposes.
c C s t j| � t| jd< d S )NrP )r8 r: r r9 )r r r r r: � s
z!OnErrorScriptSection._resetScriptN)r( r) r* r- rW rI r: r r r r r[ | s r[ c @ s e Zd ZdZdZdZdd� ZdS )�TracebackScriptSectionz
%tracebackzHandling Tracebacksa�
These scripts run when the installer hits an internal error (a traceback, as
they are called in Python) and cannot continue. When this situation happens,
the installer will display an error dialog to the screen that prompts the user
to file a bug or reboot. At the same time, it will run all %traceback scripts
in the order they are provided in the kickstart file.
Each %traceback script is required to be closed with a corresponding %end.
.. note::
These scripts could potentially run at
any stage in installation - early on, between making filesystems and installing
packages, before the bootloader is installed, when attempting to reboot, and
so on. For this reason, these scripts cannot be run in the chroot environment
and you should not trust anything in the installed system. These scripts are
primarily for testing and error reporting purposes.
c C s t j| � t| jd< d S )NrP )r[ r: r r9 )r r r r r: � s
z#TracebackScriptSection._resetScriptN)r( r) r* r- rW rI r: r r r r r\ � s r\ c @ s, e Zd ZdZdZdd� Zdd� Zdd� Zd S )
�PackageSectionz %packageszPackage Selectionc C s* |j d�d }|j� }| jjj|g� d S )N�#r )� partition�rstripr �packages�add)r r �hr r r r! � s zPackageSection.handleLinec C s t | jdd| jdd�}|jddddtd� |jd ddd
td� |jd ddttd d
� |jdddtdd� |jdddttdd� |jdddttdd� |jddddt dd� |jdd td d � |jd d ddtd d� |jd!d"ddt
d#d� |jd$d%t d t d&d'� |jd(d)t d t d*d'� |S )+Nad
Use the %packages command to begin a kickstart file
section that lists the packages you would like to
install.
Packages can be specified by group or by individual
package name. The installation program defines
several groups that contain related packages. Refer
to the repodata/\*comps\*.xml file on the first CD-ROM
for a list of groups. Each group has an id, user
visibility value, name, description, and package
list. In the package list, the packages marked as
mandatory are always installed if the group is
selected, the packages marked default are selected
by default if the group is selected, and the packages
marked optional must be specifically selected even
if the group is selected to be installed.
In most cases, it is only necessary to list the
desired groups and not individual packages. Note
that the Core group is always selected by default,
so it is not necessary to specify it in the
%packages section.
The %packages section is required to be closed with
%end. Also, multiple %packages sections may be given.
This may be handy if the kickstart file is used as a
template and pulls in various other files with the
%include mechanism.
Here is an example %packages selection::
%packages
@X Window System
@GNOME Desktop Environment
@Graphical Internet
@Sound and Video
dhcp
%end
As you can see, groups are specified, one to a line,
starting with an ``@`` symbol followed by the full
group name as given in the comps.xml file. Groups
can also be specified using the id for the group,
such as gnome-desktop. Specify individual packages
with no additional characters (the dhcp line in the
example above is an individual package).
You can also specify environments using the ``@^``
prefix followed by full environment name as given in
the comps.xml file. If multiple environments are
specified, only the last one specified will be used.
Environments can be mixed with both group
specifications (even if the given group is not part
of the specified environment) and package
specifications.
Here is an example of requesting the GNOME Desktop
environment to be selected for installation::
%packages
@^gnome-desktop-environment
%end
Additionally, individual packages may be specified
using globs. For instance::
%packages
vim*
kde-i18n-*
%end
This would install all packages whose names start
with "vim" or "kde-i18n-".
You can also specify which packages or groups not to
install from the default package list::
%packages
-autofs
-@Sound and Video
%end
a�
Group-level options
-------------------
In addition, group lines in the %packages section
can take the following options:
``--nodefaults``
Only install the group's mandatory packages, not
the default selections.
``--optional``
In addition to the mandatory and default packages,
also install the optional packages. This means all
packages in the group will be installed.
F)r; r< r= r r> z
--excludedocsr@ a;
Do not install any of the documentation from any packages.
For the most part, this means files in /usr/share/doc*
will not get installed though it could mean other files
as well, depending on how the package was built.)rB rC rD rE z--ignoremissinga�
Ignore any packages or groups specified in the packages
section that are not found in any configured repository.
The default behavior is to halt the installation and ask
the user if the installation should be aborted or
continued. This option allows fully automated
installation even in the error case.z--nobasezr
Do not install the @base group (installed by default,
otherwise).)rB rC �
deprecated�removedrD z--nocorea6
Do not install the @core group (installed by default,
otherwise).
**Omitting the core group can produce a system that is
not bootable or that cannot finish the install. Use
with caution.**)rB rC rE rD z --ignoredepsZ resolveDepsZ store_falser )rA rB rd re rD z
--resolvedepsz --default�defaultPackagesa!
Install the default package set. This corresponds to the
package set that would be installed if no other
selections were made on the package customization screen
during an interactive install.)rA rB rC rE rD z --instLangsa�
Specify the list of languages that should be installed.
This is different from the package group level
selections, though. This option does not specify what
package groups should be installed. Instead, it controls
which translation files from individual packages should
be installed by setting RPM macros.)rC rE rD z
--multilib�multiLibzx
Enable yum's "all" multilib_policy as opposed to the
default of "best".z--excludeWeakdeps�excludeWeakdepsa
Do not install packages from weak dependencies. These
are packages linked to the selected package set by
Recommends and Supplements flags. By default weak
dependencies will be installed.z --timeout�timeoutz�
Set up yum's or dnf's timeout. It is a number of seconds
to wait for a connection before timing out.)rA rP rC rE rD z --retries�retriesz�
Set up yum's or dnf's retries. It is a number of times
any attempt to retrieve a file should retry before
returning an error.)
r
r- r rK r r r r r
r r �intr )r rL r r r rM � sJ R
zPackageSection._getParserc C s t j| ||� | j� }|j|dd� |d�}|jrJ|jrJttd�|d��n |jrf|jrfttd�|d��|j | j
j _ |j | j
j _
|jr�t| j
j _n
t| j
j _|jr�d| j
j _|jdk r�|j| j
j _|j| j
j _|j| j
j _|j| j
j _|j| j
j _|j| j
j _d| j
j _dS )z�Process the arguments to the %packages header and set attributes
on the Version's Packages instance appropriate. This method may be
overridden in a subclass if necessary.
r" N)r% r$ z.--default and --nobase cannot be used together)r$ z.--default and --nocore cannot be used togetherT)r r& rM rT rf Znobaser r ZnocoreZ excludedocsr ra Z excludeDocsZaddBaseZ
ignoremissingr Z
handleMissingr rC Z instLangsrg rh ri rj r' )r r$ r% rL rV r r r r& g s,
zPackageSection.handleHeaderN)r( r) r* r- rW r! rM r& r r r r r] � s *r] N)"r+ Zpykickstart.constantsr r r r r r r Zpykickstart.errorsr Zpykickstart.optionsr
Zpykickstart.versionr r r
r r r r r Zpykickstart.i18nr �objectr r/ r8 rX rY rZ r[ r\ r] r r r r �<module> s $ ( E$KKF