OpenSAP Introduction To SUSE

Week 1 Unit 1:
Flavors of SUSE Linux

More Than One SUSE Linux
There are two primary types of SUSE Linux:
open.sap.com Slide 2
openSUSE
openSUSE is an open source project, SUSE being the primary contributor.

There are two current releases of openSUSE:
openSUSE Leap openSUSE Tumbleweed

A “rolling release” Linux distribution
Major releases match the SUSE Linux Enterprise
Server (SLES) release version New versions of individual packages are made available
o Example: openSUSE Leap 15 for SLES 15 as soon as they are stabilized
Minor releases match the Service Pack level for
SLES Receives security updates, bug fixes, and new features
as soon as they are integrated and tested by the
o Example: openSUSE Leap 15.1 for SLES 15 openSUSE community
sp1
Targeted at developers and power users Targeted at users who want the latest software package
versions
Why openSUSE?
If you are new to openSUSE (and even open source software):

o openSUSE is free software, as in free beer and free speech
o It is safe and stable
o Complete, easy and fun
If you are an advanced user:
o Large, well supported Linux distribution
o Learning curve, but customizable
o Community projects, apps, Tumbleweed, collaboration, etc.
If you are a FOSS (Free and Open Source Software) developer:
o Regular release schedule, large package library, Tumbleweed
o Community collaboration
o Foundational support from SUSE
SUSE Linux Enterprise Server (SLES)
SUSE Linux Enterprise Server (SLES) is a refined and enhanced openSUSE.

o SLES 15 is a multimodal operating system (OS) that paves the way for IT transformation in the software-
defined era
• Multimodal – works in traditional data centers and in cloud deployments
o SLES 15 makes traditional IT infrastructure efficient and provides an engaging platforms for developers
o SLES 15 can be easily deployed and transition workloads across on-premise and public cloud environments
o SLES 15 makes traditional IT infrastructure more efficient with Modular+ architecture
• Modular+ - everything is a module (i.e.- High Availability, Base System, Desktop Apps)
o SLES 15 accelerates the transition from community Linux based developer setups to fully supported
enterprise Linux environments
Relationship between openSUSE and SLES
openSUSE
Leap 15.1
SUSE Linux Enterprise Server
openSUSE
Leap 15
Binary Code Base
openSUSE
Leap 42.3 IBM System z IBM POWER X86_64
SLES Common Code Base

openSUSE
Leap 42.2
SLES Maintenance Model
Copyright © SUSE LLC
© 2019 SUSE LLC. All rights reserved. SUSE and the SUSE logo are registered trademarks of SUSE
LLC in the United States and other countries. All third-party trademarks are the property of their
respective owners.
Thank You!
Contact Information:
open@sap.com
Week 1 Unit 2:
Introduction to YaST
What is YaST?
YaST (Yet another Setup Tool) is a local system configuration tool for Linux, most prominently used by
SUSE Linux Enterprise Server and openSUSE
Using YaST, you can configure the network, storage devices, software, and most network services
shipped as part of SLES.
YaST has four user interfaces:
o Command line non-interactive
• Example: yast -i vim
o Command line interactive
• Example: yast lan interactive
o Graphical
o Non-graphical (ncurses)
The appearance of the user interface depends on which command you use to start YaST
Starting YaST - Graphical
There are multiple ways to start YaST:

o GNOME: Activities > Show Applications > YaST
Starting YaST – Command Line
o Get root permissions:

• Example: su –
o List modules: yast -l or yast --list, then start YaST with the module:
Starting YaST – Where you start YaST matters
When using interactive YaST, there are two different commands (from a command line) to
start it, each with different possible results depending on where you typed the YaST
command:
o yast – always launches the ncurses interface
o yast2 – can launch the graphical or ncurses interface depending on the location where the
command is called from
Command Terminal in X Command Line

yast ncurses ncurses
yast2 graphical ncurses
Graphical YaST
The graphical interface of YaST is organized

into two sections when started,
categories and modules.
Categories are on the left and organize the

various modules into loosely related
topics such as Software, Network
Services, and Security and Users.
Selecting a category on the left displays
the contained modules on the right.
Non-Graphical YaST
Like the graphical interface of YaST, the

non-graphical, or ncurses interface, is
organized into two sections when started,
categories and modules.
Using the arrow keys or the various hotkeys
highlighted in yellow, settings can be
changed through the ncurses interface
with exactly the same effect as with the
graphical interface.
Key Description
Tab Move focus to the next frame or item
Shift-Tab Move focus back to the previous frame or item
Arrow Keys Navigate in a frame
Space (De-) Select a highlighted item
Enter Select menu item or button
YaST Modules
YaST has a series of modules that allow configuration of various components.

Modules allow you shape the product according to your needs.
Each module has a clearly defined scope. These include the following:
o lan – configure the network in SLES
o firewall – view and change the firewall settings
o nfs – configure an nfs client
o nfs-server – setup and configure an nfs server
o partitioner – manage disk space and partitions
o scc – configure SUSE Support Center configuration and subscription information
o sudo – modify sudo properties and settings
o sw_single – add or remove software packages
respective owners.
Thank You!
open@sap.com
Week 1 Unit 3:
The SLES Unified Installer
What is the Unified Installer?
SUSE Linux Enterprise Server is installed through the use of the Unified Installer
Previous versions of SLES had separate installation media for each sub-product
The Unified Installer allows several different products to be installed from a single installation medium,
despite having only one relatively small .iso (less than 670MB)
Unified Installer Product Options
Upon starting the Unified Installer, the first screen you are presented with after booting
allows you to choose the product you wish to install.
Your options are:
o SUSE Linux Enterprise Server 15 SP1
o SUSE Linux Enterprise High Performance Computing 15 SP1
o SUSE Linux Enterprise Real Time 15 SP1
o SUSE Linux Enterprise Server for SAP Applications 15 SP1
o SUSE Linux Enterprise Desktop 15 SP1
o SUSE Manager Server 4.0
o SUSE Manager Proxy 4.0
o SUSE Manager Retail Branch Server 4.0
Note that you will need a registration code for the product
you select
Access to Packages
When installing via the installation medium, only a minimal command line based system can be
installed, unless:
o The system being installed has connectivity to SUSE Customer Center (SCC)
o The system being installed has connectivity to a Repository Mirroring Tool (RMT)
o The second .iso has been downloaded, SLE-15-Packages, and is made available during the
installation
In order to use SCC or an RMT, you will need a

registration code for the product you select.
Add On Product
A minimal installation of SUSE Linux Enterprise Server with no additional software selected
is of limited use.
• In order to add functionality to your product, select a module or extension that matches
your needs
• All products listed in the Extensions and Modules Selection screen have dependencies on
at least the Basesystem Module, with other dependencies likely
Note that dependencies between modules are not handled

automatically, so consult the Installation Quick Start Guide or
Deployment Guide for more information:
o https://www.suse.com/documentation/sles-
15/book_quickstarts/data/art_modules.html
o https://www.suse.com/documentation/sles-
15/book_sle_deployment/data/book_sle_deployment.h
tml
Installation Summary
Before any changes are written to disk for the installation

of SLES, you are presented with a summary of the
proposed install.
• Changes can be made by clicking the available links
and modifying settings as desired
• When selections have been verified as correct, select
the Install button
respective owners.
Thank You!
open@sap.com
Week 1 Unit 4:
SLES Modules and Extensions
SLES Modules
SLES has a series of modules that allow configuration of various components.

Modules allow you shape the product according to your needs.
Each module has a clearly defined scope. These include the following:
o Basesystem – adds a basic system on top of the Installer. Required by all other modules and
extensions
o Desktop Applications – adds a graphical user interface and essential desktop applications to the
system
o Development Tools – contains compilers and libraries required for compiling and debugging
applications. Replaces the former Software Development Kit (SDK)
o Legacy – contains packages that were available in previous versions of SLES, but have been
discontinued
o Server Applications – adds server functionality by providing network services such as DHCP
server, name server, or web server
o Web and Scripting – contains packages intended for a running web server
SUSE Linux Enterprise Server Extensions
• SLES extensions provide advanced capabilities for tasks, such as live patching and high
availability clustering
• Extensions are offered as subscriptions and require a registration key that is liable for costs
• Extensions usually have their own release notes that are available from
https://www.suse.com/releasenotes
• The currently available extensions are:
o SUSE Linux Enterprise High Availability Extension
o SUSE Linux Enterprise Live Patching
o SUSE Enterprise Storage
o SUSE Linux Enterprise Workstation Extension
Installing Modules and Extensions
Modules and Extensions can be installed when initially setting up the system, and also on an existing
SUSE Linux Enterprise Server Installation
• For an new installation:
o The steps are part of the installation routine
o Either network access to SCC or SMT/RMT, or offline with additional installation media
• For an existing installation:
o Launch the YaST module Add System Extensions or Modules and follow instructions
Extension Detail: High Availability Extension
SUSE Linux Enterprise High Availability Extension is an integrated suite of open source
technologies that enables you to implement highly available physical and virtual Linux
clusters.
• High availability clustering is used to automate application and data recovery
• Flexible policy-driven clustering solution to eliminate single points of failure
• Servers are continuously monitored; workloads are transferred when faults or failures
occur
Extension Detail: Live Patching
Using SUSE Linux Enterprise Live Patching, you can apply patches to your Linux kernel
without rebooting your system.
• Your applications keep running while you patch the Linux kernel with critical updates
• Maximize uptime for a wide range of systems and applications
Extension Detail: Enterprise Storage
An intelligent software-defined storage solution, powered by CEPH technology, which

enables you to transform your enterprise storage infrastructure.
• Simple to manage, agile infrastructure with increased speed of delivery, durability and
reliability
• Reduce costs and alleviate proprietary hardware lock-in
• Truly open and unified, intelligent software-defined storage solution
respective owners.
Thank You!
open@sap.com
Week 2 Unit 1:
The Filesystem Hierarchy Standard (FHS)
The Linux Standards Base (LSB) and the FHS
The Filesystem Hierarchy Standard (FHS) is part of the Linux Standards Base. It includes the
following information:
• Which directories must be located on the first level and what they contain
• Defines a two-layer hierarchy
o What’s under the top layer (root or “/”)
o What’s under /usr and /var
The FHS includes the following design factors:
o Compartmentalization – by separating out components of the filesystem, gain security and
order
o Writability – where can users and processes safely store files
o Shareability – who can access what, with and without changes to default permissions
The FHS is maintained by the Linux Foundation
FHS First Layer
/
bin sbin lib lib64 etc usr opt root boot home run mnt var srv tmp dev sys proc
/bin – user binaries /mnt – temporarily mounted filesystems

/var – variable files
/sbin – system binaries
/srv – site-specific data served by the system
/lib – libraries /tmp – temporary files
/lib64* – 64bit libraries /dev – device files
/etc – configuration files /sys – information about devices, drivers, etc.
/proc – virtual filesystem with kernel and
/usr – programs, libraries and more
process information
/opt – optional and third-party applications
/root – root user home directory
/boot – boot loader files
/home – user home directories
/run – run-time variable data
FHS Second Layer - /usr
/
bin
sbin
lib
include
share
local
src
/usr/bin – most executables
/usr/sbin – system admin programs
/usr/lib – libraries and application directories
/usr/share – documentation and man pages
/usr/local – locally installed programs
/usr/src – source code for kernel and programs
FHS Second Layer - /var
/
lib
lock
/var/lib – variable libraries, like databases spool
/var/lock – lock files for multiuser access run
/var/spool – queues (printers, email) log
/var/run – information about running processes

/var/log – service log files
respective owners.
Thank You!
open@sap.com
Week 2 Unit 2:
Linux File Types
Linux File Types
The Seven File Types
There are 7 different file types in Linux:

o Normal files
o Directories
o Links
o Sockets
o Pipes (FIFOs)
o Block Devices
o Character Devices
Linux File Types
File Types: Normal Files and Directories
• Normal files
o Sets of data addressed with one name
o Examples:
• ASCII text files
• Executable files
• Graphics files
• Directories
o Organize files on the disk
o Contain files and/or subdirectories
o Implement the hierarchical file system
Linux File Types
File type: Introduction to Links
• Hard Links
o Secondary file names for files
o Multiple file names referencing a single inode
o Referenced file must reside on the same filesystem FileB FileA
• Symbolic Links
o References to other files on the system (or over the network)
o The inode contains a reference to another file name
o Referenced files can exist in the same filesystem or in another filesystem
o A symbolic link (sometimes called soft) can reference a non-existent file (broken link)
FileB FileA
Linux File Types
File type: Links Visualized
File1link.txt File1.txt Symlink-to-File1.txt

(hard link)
Filesystem
(inodes)
Data
Volume 1 Volume 2
Linux File Types
File type: Sockets and Pipes
• Sockets
o Logical endpoint for communication between processes
o Used for two-way communication
Process 1234 Process 4321
• Pipes (sometimes called a FIFO – First In First Out)

o Logical endpoint for communication on the filesystem for output from a process
o Used for one-way communication
o Multiple processes can read from the pipe
Process 9876 Process 6789
Linux File Types
File type: Device Files
• Device file represent hardware

o Link between hardware devices and kernel drivers
o Kernel drivers read from and write to the device file
o The kernel gets the data to the hardware in the correct format
o Except network cards (have their own method)
• Types of device files

o Block devices
o Character devices
Device files are automatically created by a system tool called udev. There are tools for and
circumstances when manual creation of device files is necessary.
Linux File Types
File type: Block Device Files
• Block device files are primarily used for storage

o 1st initialized hard drive = /dev/sda
o 2nd initialized hard drive = /dev/sdb
o etc.
Partition numbers are appended to the device name:
Device Name
First primary partition on the first drive /dev/sda1
Second primary partition or an extended /dev/sda2
partition on the first drive
First primary partition on the third hard drive /dev/sdc1
First logical partition on the first hard drive /dev/sda5
Second logical partition o the first hard drive /dev/sda6
Linux File Types
File type: Block Device Files
• Character devices provide unbuffered access directly to a hardware device

o Sometimes referred to as raw devices
o Many different options for character devices, making their use and application wide and varied
• Examples of character devices:

o Keyboard
o Mouse
respective owners.
Thank You!
open@sap.com
Week 2 Unit 3:
User Management
User Management
User ID (UID) and Group ID (GID)
Since operating systems handle numbers better than strings, users and groups are administered as
numbers:
• The User ID, or UID, is the number representing a user
o 0: root
o 1 – 99: System
o 100 – 499: System accounts
o ≥ 1000: Normal (unprivileged) accounts
• The Group ID, or GID, is the number representing a group (with users as members)
o 0: root
o 1 – 99: System groups
o 100 – 499: Dynamically allocated system groups
o ≥ 1000: Normal groups
User Management
User and Group Information: CLI
• There are several tools for viewing user and group information from a command line or shell:
o whoami: who is executing this command
server1:~> whoami
tux
o id <user> : list uid, gid and any groups the user is in
server1:~> id tux
uid=1000(tux) gid=100(users) groups=100(users)
o groups : list the groups the user is a member of
server1:~> groups tux
tux : users
User Management
User and Group Database Files
• Users, groups and passwords are stored in the following files:

o Users: /etc/passwd – contains user account information, with the exception of the user account password
o Password hashes: /etc/shadow – contains user account password hashes and policies
o Groups: /etc/group – stores group information, such as names and members
User Management
Contents of /etc/passwd
• The fields of /etc/passwd are as follows:

o User login name
o Password field
o User ID
o Primary group ID
o Comments (GECOS)
o Home Directory
o Default shell
User Management
Contents of /etc/shadow
• The fields of /etc/shadow are as follows:

o User login name
o Hashed password field
o Last change
o Next possible change
o Must Change
o Warning
o Grace limit
o Expiration/Lock
User Management
Contents of /etc/group
• The fields of /etc/group are as follows:

o Group name
o Group password
o Group ID
o List of secondary group members
User Management
Managing Users and Groups from the Command Line
• Users and groups can be managed via the command line (shell) or through YaST.
Command Description
useradd Create users
usermod Modify existing users
userdel Delete users
groupadd Create groups
groupmod Modify existing groups
groupdel Delete groups
passwd Set/Modify user passwords
gpasswd Set/Modify group passwords
User Management
Managing Users and Groups from YaST
respective owners.
Thank You!
open@sap.com
Week 2 Unit 4:
Filesystem Permissions
Identifying File and Directory Permissions
File and directory permissions and ownership are easily identified from the command line:
o Using the ls –l command, we get something similar to the following:
Type and permissions
Links and contents
Modification time
Ownership
File name
File size
Permissions Explained
Permissions in Linux (and other Unix-like operating systems) use a mode system:
• Files
o Read (r) – File can be opened and read
o Write (w) – File can be modified (but not deleted) -rwxrwxrwx
o Execute (x) – File can be executed (run as a program or script)
• Directories
o Read (r) – Directory contents can be viewed
o Write (w) – Directory contents can be modified (i.e. files can be deleted)
o Execute (x) – Directory can be entered (cd into or through directory)
drwxr-x---
User Group Other
The permissions are listed by User, Group, and Other (meaning everyone else).
User
• The user that has ownership of a file can be given read
(r), write (w), or execute (x) permissions to the file
Other
• The group that has ownership can also be given read,
write or execute permissions
• Anyone that is not the owning user, or in the group that

has ownership, is classified as other and a set of read,
write, and execute permissions applies to them
Group
Binary and Octal Permission Notation
Permissions in Linux can also be expressed in Binary and Octal notation. Binary notation is rarely
used for anything other than calculation.
o Read = 4 in octal notation
o Write = 2 in octal notation
o Execute = 1 in octal notation
Notation User Group Other

Standard rwx rw- r--
Binary 111 110 100
Octal 7 6 4
Modifying File and Directory Modes and Ownership
Permissions in Linux are referred to as the mode and there are tools to change the mode, as well as
the owner and group owner of a file or directory:
o chmod – Change mode
• Can use the regular (rwx) notation or the octal notation
o chown – Change file user and/or group ownership

• Can specify either user or group, or both
o chgrp – Change group ownership
umask
When a file or directory is created in Linux, default permissions are set. Using the umask, an
administrator can limit specifically (via subtraction) what permissions are granted to the user, group
and all others.
Default 666
• Files:
umask 022
Result 644
Default 777
• Directories umask 022
Result 755
Sticky Bit
In addition to the standard read, write, and execute permissions, there are three others: the sticky bit,
SGID, and SUID.
• Sticky bit
o Files: Not applicable
o Directories: A user can only delete files in the directory when the user is root or the owner of the
directory
o There is special notation for the sticky bit:
User Group Other
rwx rwx rwt
rwT
001 111 111 111
110
1 7 7 7
6
Set Group ID (SGID)
• Set Group ID (SGID)

o Files: When a program (the file) is run, this sets the group ID of the process to that of the group
of the file (not the group of the user who executed the file)
o Directories: Files create in this directory belong to the group to which the irectory belongs and
not to the primary group of the user. New Directories created in this directory inherit the SGID
bit
o There is special notation for SGID:
User Group Other

rwx rws rwx
rwS
010 111 111 111
110
2 7 7 7
6
Set User ID (SUID)
• Set User ID (SUID)

o Files: When a program (the file) is run, this sets the user ID of the process to that of the owner
of the file (not the user who executed the file)
o Directories: Not applicable
o There is special notation for SUID:
User Group Other

rws rwx rwx
rwS
100 111 111 111
110
4 7 7 7
6
respective owners.
Thank You!
open@sap.com
Week 2 Unit 5:
Privilege Delegation
Switching Identities
SUSE Linux Enterprise Server administrators frequently need to change system identities in order to
perform daily tasks. There are multiple tools for performing this switch.
o su – Substitute user
• The “-” option gives you a login shell (e.g. su -)
• Execute a single command as a user with the -c option (e.g. su -c “grep tux /etc/shadow”)
o newgrp, sg – Switch primary group
sudo
SUSE Linux administrators will also frequently use the sudo command. Originally it meant “superuser
do”, but has more recently been changed to “substitute user do”.
o sudo – switch to another user (default is root) and perform a task
o On SUSE Linux Enterprise Server, the root password is required by default
• This behavior is different from most other Linux distributions
• Can be changed to the user’s password in the /etc/sudoers file
SUSE default (root’s password) User’s password
sudo’s Configuration File: /etc/sudoers
The primary configuration file for sudo is /etc/sudoers.

o visudo (text based) is the preferred tool for modifying the configuration
• visudo opens /etc/sudoers in the default text editor
• Requires root privileges
o Can be changed to allow user passwords instead of root when performing root-level
tasks
Syntax in /etc/sudoers
The general syntax of the /etc/sudoers file looks like the following:
o <user/%group> <host> = <command1>[, <command2>…]
• User example:
geeko ALL = /sbin/shutdown
geeko ALL = NOPASSWD: /sbin/shutdown
• Group example:
%admins = /sbin/shutdown
sudo Aliases
There are several kinds of aliases that can be used in the /etc/sudoers file:
o User alias – a collection of users
User_Alias <ALIAS NAME> = <user1>[, <user2>, …]
Example: User_Alias POWERUSERS = tux, geeko
o Command Alias – a collection of commands
Cmnd_Alias <ALIAS NAME> = <command1>[, <command2>, …]
Example: Cmnd Alias KPROCS = /bin/kill, /usr/bin/killall
o Host Alias – a collection of hosts
Host_Alias <ALIAS NAME> = <host1>[, <host2>, …]
Example: Host_Alias HOSTS = da1
o Runas Alias – a collection of users that can be reference by UID
Runas_Alias <ALIAS NAME> = <user1>[, <user2>, …]
Example: Runas_Alias RUNASUSERS = tux, geeko
Using sudo Aliases
Aliases are frequently used together to simplify sudo administration.

o Alias use syntax:
<User_Alias> <Host_Alias> = (<user>) <Cmnd_Alias>
Example: POWERUSERS HOSTS = (root) KPROCS
User_Alias POWERUSERS = tux, geeko

Cmnd_Alias KPROCS = /bin/kill, /usr/bin/killall
Host_Alias HOSTS = da1
respective owners.
Thank You!
open@sap.com
Week 3 Unit 1:
Management of RPM Packages
RPM Basics
RPM is made up of several components:

o RPM database
• Contains information on all installed RPM packages
• Keeps track of all files that are changed and created when a user installs an RPM
• Works in the background of the package manager
o RPM package manager
• Utility that handles installing and uninstalling RPM packages
o RPM package
• Software packaged for easy installation onto a SUSE Linux Enterprise Server
RPM Package Components
An RPM package includes the following parts:

o Informational header – a package label that contains information about the software to be
installed
o GPG signature – a key signature to validate the integrity and source of the package
o CPIO archive – all the files of the package are compressed in a CPIO archive
o Installation scripts - Sometimes it is necessary to do some modifications to the system before
and/or after the installation of the package; this can be done by pre- and post installation scripts
Header Signature
CPIO Scripts
RPM Names
SUSE Linux Enterprise Server RPMs follow a naming convention:
o Software name – the name of the package

o Software version – the versions of the software contained in the package
o Release number – the release number of the software version in the package
o Architecture – the hardware architecture the software is compiled for
Installation of RPMs
An RPM can be installed with the rpm command:

o rpm -i <package.rpm>
• Installs the package
o rpm -u <package.rpm>
• Installs or updates an already installed package
o rpm -f <package.rpm>
• Reinstalls or updates an already installed package
• A version of the package must already be installed
An RPM can also be uninstalled with the rpm command:

o rpm -e <package>
RPM Database Query
The RPM database contains useful information and can be queried:
Option Description
rpm -q Query the RPM database
rpm -qp Inspect a package that is not yet installed
The following query options are often used with the -q and -p options:
Option Description
rpm -qa List all installed packages
rpm -qi List package information
rpm -ql (lowercase L) Display file list
rpm -qf Which package does the specified file (with full path) belong to
rpm -qd List only documentation files (-l is implied)
rpm -qc List only configuration files (-l is implied)
Additional RPM Database Queries
Option Description
--dump Display a file list with complete details
Used with -l, -c or -d
--provides List features of the package that another package can request with
--requires
--requires, -R List capabilities the package requires
--scripts List installation scripts (pre-install, post-install, and uninstall)
--changelog Display detailed list of information about a specific package,
specifically about updates and modifications, etc.
RPM Package Verification
RPMs can be verified to ensure integrity using the rpm -V and rpm --checksig commands:
o rpm -- checksig <package.rpm>
o rpm -V <package>
• Return codes give insight on what has changed per file:
Code Description
S List package information
M Mode has changed
5 Size is different
D Device major/minor numbers are different
L Readlink (symbolic link) path mismatch
U User ownership differs
G Group ownership differs
T mtime (modified time) differs
P Capabilities differ
respective owners.
Thank You!
open@sap.com
Week 3 Unit 2:
Software Management with libzypp
libzypp Overview
libzypp is a package manager: a library and set of utilities that allow for package management on
Linux systems.
o Built upon SAT solver, a library to resolve package dependencies
o Supports various software repository types
o Supports signed repositories, delta packages, and package updates
Files on the system RPM libzypp
Software Repositories
What is a software repository?

o Directories that contain RPM software packages and meta-data files
o Can be accessed by RPM package managers
o Can be accessed from different media and local file systems
• DIR
• HD
• ISO
• DVD
• etc.
o Can be accessed via various network protocols
• NFS
• FTP
• HTTP(S)
• SMB/CIFS
The 4 “P”s of libzypp
libzypp categorizes the contents of a repository into one of 4 “P”s:

o Packages
• RPM packages (including patch/delta RPMs)
• Contain files to be installed on the filesystem
o Patterns
• Reference 1 or more packages
• Typically install all packages needed for a certain server “role”
o Products
• Contain 1 or more patterns
• Associated with a product with its own support and maintenance
o Patches
• Reference 1 or more update packages (packages provided as both full and patch/delta RPMs)
libzypp Utilities
libzypp is a backend to several utilities that provide installation and/or update functionality for RPMs
o YaST – use a graphical, ncurses, or non-interactive interface to install or upgrade packages
o PackageKit – use a graphical, desktop toolkit for package updates
o zypper – a command-line tool for software management
o YaST PackageKit zypper
Files on the system RPM libzypp
Terms Recap
Term Description
Repository A local or remote directory containing packages and metadata
Product Represents a whole product
Pattern An installable group of packages dedicated to a certain purpose
Package A compressed file in RPM format that contains the files for a particular program
Patch Consists of one or more packages and may be applied by means of delta RPMs
Delta RPM Consists only of the binary differences between two defined versions of a
package
Package Dependencies Certain packages are dependent on other packages
Using zypper - Repositories
The zypper utility, used from the command line, allows you to manage repositories , as well as
packages, patches, products, and patterns.
o List software repositories:
• zypper lr
o Add a repository:
• Zypper ar <uri> <alias>
o Modify repositories:
• zypper mr [options] <alias|#|uri>
Using zypper - Packages
zypper also is commonly used to manage packages:

o List and search:
• zypper se <string>
o Display package information:
• zypper if <package>
o Install package:
• zypper in <package>
o Remove package:
• zypper rm <package>
Managing Repositories and Software with YaST
YaST can perform the same repository and software functions as zypper from a graphical or ncurses-
based interface:
respective owners.
Thank You!
open@sap.com
Week 3 Unit 3:
Network Management with SLES
Networking Terms
Term Description
Device Network adapter found on the system
Interface Software component creating an interface to a physical device
Link Connection of a device to the network
Address IP address assigned to an interface
Broadcast Address to reach all hosts on the local network
Route Path a network packet takes from the source to the destination
host
Network Related Configuration Files
For each interface used on a SUSE Linux Enterprise Server machine, a configuration file will be
created and stored in the /etc/sysconfig/network/ directory. Each file contains configuration
information that can be easily viewed or changed.
Name resolution is configured via multiple files:

o System’s hostname: /etc/hostname
o Local name resolution: /etc/hosts
o DNS servers: /etc/resolv.conf
o Order of name resolution services: /etc/nsswitch.conf
SUSE sysconfig Network Commands
SLES has several commands for viewing or changing the status of an interface. Each command has a
syntax of: <command> <interface>
o Bring a configured network interface up:
• ifup eth0
o Bring a configure network interface down:
• ifdown eth0
o Display information about a configured network interface:
• ifstatus eth0
Network Configuration with YaST
Within the YaST lan module, an administrator can configure network interfaces, bridges, hostnames,
DNS servers, etc. The same functions can be performed in the ncurses version of YaST.
The ip Command
The ip command can be used to temporarily change network settings, including ip addresses,
network bridge creation, routing, etc. Any changes made with ip will not be saved to configuration
files.
o Syntax:
• ip [address|addr|a] <task> <arguments>
o Display IP address configuration:
• ip addr show (or ip a s )
o Add an IP address to an interface:
• ip addr add 10.0.0.10/24 brd + dev eth0
o Remove an IP address from an interface:
• ip addr del 10.0.0.10/24 dev eth0
o Add a default route:
• Ip route add default via 172.17.2.2
Network Management Tools
Many tools used for network management in SUSE Linux Enterprise Server share common functions found
on other operating systems, such as ping and traceroute:
o ping – use an ICMP packet to verify reachability of a remote host
Option Description
-c count Number of packets to be sent
-I Network interface to be used (uppercase i)
-i seconds Number of seconds to wait between packets
-f Packets are sent are sent at the same rate as replies
-l preload Send packets without waiting for a reply
-b Send packets to the network broadcast address
-t ttl Time To Live for packets to be sent
o traceroute – display route taken to a remote network or host
• Uses UDP (datagrams)
• -n option displays IP addresses instead of FQDN (Fully Qualified Domain Name)
firewalld Basics
Firewall is a term used to describe a mechanism that controls the data flow between networks. When
mentioned in this section we mean a packet filter.
firewalld is a daemon that maintains the system’s iptables rules and offers an interface for
operating on them.
o iptables – a rule-based firewall included in the Linux kernel since the 2.4 release
o firewall-cmd – a command line utility for interacting with firewalld
o firewall-config – a graphical user interface for interacting with firewalld
Security Zones
firewalld implements different security zones. Several zones are predefined, but the administrator can
define custom zones if desired.
o Each zone contains its own set of iptables rules
o Each network interface is a member of exactly one zone
o Connections can also be assigned to a zone based on the source addresses
o Each zone represents a level of trust
• A host can, therefore, offer different services based on trusted or untrusted networks in a defined way
firewalld Configurations
firewalld has two separate configurations:

o Runtime – represents the currently active rules
• Allows for temporary rules that can be discarded after firewalld is restarted
• Allows for experimentation with new rules while being able to revert
o Permanent – represents the saved rules that will be applied when restarting firewalld
respective owners.
Thank You!
open@sap.com
Week 4 Unit 1:
SLES Storage Administration
Linux I/O Stack
Linux storage architecture can be described by the following diagram:
Partitioning Utilities
There are multiple tools for partition management in SUSE Linux Enterprise Server:
o YaST partitioner module – Graphical or ncurses tool for partitioning, formatting and other block device and
filesystem management
o fdisk – traditional command line tool for manipulating MBR (MSDOS) type partition definitions
o parted – command line tool for MBR and GPT type partitions
MBR and GPT
• Master Boot Record • Globally Unique Partition Table

o Boot loader (446 bytes) o Protected MBR (512 bytes)
o GPT header (512 bytes)
o Partition table (64 bytes)
o Partition entries (128 bytes
o Magic number (2 bytes) each)
• Limited to 2 TB hard disks • Limited to 9.2 ZB hard disks
Device Files for Block Devices
• Under MBR (or MSDOS) partition types, partitions are categorized:

o Primary – only 4 primary partitions can exist with MBR
o Extended – a primary partition can be made an extended partition, allowing for multiple sub-partitions
underneath
o Logical – logical partitions are sub-partitions underneath an extended partition.
• Device files under MBR follow a naming routine:
o Primary: /dev/sdx1, /dev/sdx2, /dev/sdx3, etc.
• These are the first, second and third partitions on a scsi device (x)
o Extended: not referenced via a device file since only sub-partitions (logical) are used
o Logical: the first logical partition is /dev/sdx5 as there are only 4 primary partition, so the first logical
partition always begins here
• GPT partitions are all primary partitions and have no special numbering rules
Supported Filesystems
• Making a filesystem on a partition typically is done with the mkfs.<filesystem> command:

o mkfs.ext4, mkfs.xfs, mkfs.btrfs, etc.
• Filesystems supported in SLES 15:
o Ext2
o Ext3 (default in SLE 11) Traditional Linux filesystems
o Ext4
o XFS (default in SLE 12 and 15 for data partitions)
o Btrfs (default in SLE 12 and 15 for /)
o JFS (existing volumes only)
o NTFS-3G (only in SUSE Linux Enterprise Desktop/Desktop Extension)
o VFAT
From an applications perspective – in most cases – the filesystem does not matter because of Linux’s
use of the Virtual Filesystem Switch (VFS). The VFS makes the filesystem opaque.
The Virtual Filesystem Switch (VFS)*
* Also referred to as the Virtual File System.
/etc/fstab
• The /etc/fstab file (file systems table) is the primary configuration file for determining where, how
and when a partition or other storage device is to be mounted on the local system
• There are 6 fields that configure each partition/device
o Field 1: Name, file system label, or UUID
o Field 2: Mount point
o Field 3: Filesystem type
o Field 4: Mount options
o Field 5: Use the dump backup utility?
o Field 6: Sequence of filesystem checks to perform
Device, Filesystem, and Mounting Utilities
o mount/umount – command line tool for adding or removing a partition from the / (root) filesystem
• Examples of options: remount, rw/ro, sync, atime, user, defaults
o lsblk – list block devices
o blkid – display block IDs and the associated block device files
o df – list free disk space

o du – estimate file space usage
o lsof – list open files
o fuser – display the process IDs (PIDs) of processes using specified files
respective owners.
Thank You!
open@sap.com
Week 4 Unit 2:
The Shell Environment
What is the Shell?
The shell is the most basic user interface to SUSE Linux Enterprise Server.
o Also referred to as the command line interface
There are multiple shells available in SLES, and they are listed in /etc/shells:
o bash (Bourne Again SHell) -> the default shell in SLES
o csh – the c shell
o ksh – the korn shell
o tcsh – an enhanced c shell
o zsh – the z shell
o etc.
The shell environment is made up of components that can be customized to the user’s preference
using:
o Variables – the most commonly customized part of the shell environment
o Functions – define core functionality of the shell
o Aliases – allow shortcuts to longer, sometimes complex, commands using shorter input
A shell can be invoked in two different ways
o Login shell – the user’s preferred environment (variables, functions and aliases) is set
• A login shell will ask for a username/password
• A login shell can be requested with the --login option when /bin/bash is called
o Non-login shell – the shell inherits an existing environment (from a previously started shell)
• A non-login shell will not ask for username/password (e.g. – a gnome-terminal session)
Shell Variables and Settings
Global profiles (all users): Order of execution for login shells:

1) /etc/profile
• /etc/profile 2) /etc/profile.d/*.sh
• /etc/profile.d/*.sh 3) /etc/profile.local
4) ~/.profile
• /etc/profile.local 5) /etc/bash.bashrc
6) /etc/bash_completion.d/*sh
7) /etc/bash.bashrc.local
• /etc/bash.bashrc 8) /etc/inputrc
• /etc/bash_completion.d/*.sh 9) ~/.bashrc
10) ~/.alias
• /etc/bash.bashrc.local
Order of execution for non-login shells
• User specific profiles: 1) /etc/bash.bashrc
• ~/.profile 2) /etc/bash_completion.d/*.sh
• ~/.bashrc 3) /etc/bash.bashrc.local
4) /etc/inputrc
• ~/.alias 5) ~/.bashrc
6) ~/.alias
Shell Aliases
A shell alias allows a typed shortcut to longer, more complex, commands using shorter input.
o Define an alias:
alias ALIAS_NAME=“COMMAND”
o Remove an alias:
unalias ALIAS_NAME
o List all defined aliases:
alias
o Alias definition file:
~/.alias
Shell History
When a command is entered in a shell, it is stored in the history file of the user who executed it:
o ~/.bash_history
o View the shell history with the history command
• Scroll through the history with the <up-arrow> and <down-arrow> keys
o Search the history for a command that begins with <string>
• <string><PageUp>/<string><PageDown>
o Search history for any <string>, press ctrl+r
• Execute the found item: press Enter
• Change the found item: press Tab
o Re-execute a numbered command from history:
• !<command-number>
Tab Auto-Completion
Commands in a shell can be automatically completed if they are unambiguous, or a list of possibilities
can be displayed:
Data Channels
Channel Redirection
Command Description
> Redirect stdout into a file
Example: ls /etc > /tmp/etc_files.txt
>> Redirect stdout, appending to a file
2> Redirect stderr into a file
2>> Redirect stderr, appending to a file
< Redirect stdin from a file

Example: mail geeko < email_body.txt
| Use stdout from one command as stdin of another
Example: ls /etc | grep samba
tee Redirects stdout to a file and the terminal
Example: <command> | tee <file>
Chain Commands Together
Command Description
; Chain multiple commands together on a single command line
Example: echo Hello ; echo How are you?
&& Execute a second command only if the first command returns
no error (return code 0)
Example: grep “swap” /etc/fstab && echo Success
|| Execute a second command if the first command returns an
error (i.e. return a code other than 0)
Example: grep “XXX” /etc/fstab || echo Failure
Help Resources
o Command help: <command> -h or <command> --help

o Manual pages: man [section] command
o List for keywords: man –k keyword
o Display descriptions: whatis <command>
o Info pages: info <command>
o Software package documentation in /usr/share/doc/packages/
o Release Notes in /usr/share/doc/release-notes/
respective owners.
Thank You!
open@sap.com
Week 4 Unit 3:
Process Administration Basics
Process Basics
o Terminology
• Program: Executable code, stored on a drive
• Process: Executable code, copied into RAM for execution
• Task: Synonym for process
o Basic process types:
• User: Associated with a controlling shell or terminal
• Daemon: Not associated with a controlling shell or terminal
o Every process is assigned a unique Process ID (PID)
o Processes can spawn other processes (parent/child relationship)
View Processes
Command Description
Display running processes
ps Common options:
aux All processes, with user list
-ef All processes, full-format with CLI
Display running processes with their parent/child
pstree relationships
Common options:
-p Add PIDs to the output
top Display processes, sorted by usage and refreshed at an
interval
Manage Processes
Command Description
kill <PID> [signal] Sends a signal to a specific PID
killall <process_name> [signal] Sends a signal to all processes with a specified name
(e.g. killall firefox TERM)
No. Signal Description No. Signal Description
1 HUP Hangup 11 SEGV Segmentation fault
2 INT Interrupt
12 USR2 User defined
3 QUIT Quit
4 ILL Illegal instruction
13 PIPE Broken pipe
5 TRAP Trace 14 ALRM Alarm clock
6 ABRT Aborted 15 TERM Terminated
7 BUS Bus error 16 STKFLT Stack fault
8 FPE Floating point exception 17 CHLD Child exited
9 KILL Killed 18 CONT Continued
10 USR1 User defined 19 STOP Stopped
Process Priority
o The relative process priority range is from 19 to -20

• -20 is the highest relative priority (a not-nice task has a higher priority)
• 19 is the lowest relative priority (a nice task has a lower priority)
Command Description
nice Launch a task with a specified relative priority

Example: nice 10 xterm
renice Change a running task’s relative priority.

Tasks are specified using their PID
Example: renice -15 –p 2567
Jobs and Processes
o Jobs (processes) can be put into the background to allow continued use of the shell instead of
waiting for each task to finish
• ctrl+z Pause the task
• bg Continues the paused task in the background
o Start a job directly in the background: append “&”
• Example: xeyes &
• jobs – command to view jobs tied to a shell
• fg – bring background tasks into the foreground
respective owners.
Thank You!
open@sap.com
Week 4 Unit 4:
Process Scheduling
Process Scheduling
Cron Jobs
o Cron jobs are the primary way that SUSE Linux Enterprise Server administrators schedule
tasks to be completed regularly. There are cron jobs for users and for the system.
o User cron jobs are configured via the crontab utility:
Option Description
-e Edit a user’s crontab
-l List a user’s crontab
-r Remove a user’s entire crontab
o There are fields in the crontab entries that represent different time intervals:
Process Scheduling
System Cron Jobs
o System cron jobs are kept in the /etc/crontab file

o System cron jobs include a “who” field to designate which user a task should be run as:
o There are also some predefined directories where tasks can be dropped in for hourly, daily,
weekly, or monthly execution:
• /etc/cron.hourly/
• /etc/cron.daily/
• /etc/cron.weekly/
• /etc/cron.monthly/
Process Scheduling
Cron Architecture
Process Scheduling
The at Daemon
Command Description
at, batch Schedule a task
Ctrl+D exits command input
-f: specify a script file
atq View scheduled tasks for a user
atrm <job_number> Remove a scheduled task
File Description
/etc/at.allow Listed users can define jobs
/etc/at.deny Listed users cannot define jobs
respective owners.
Thank You!
open@sap.com

OpenSAP Introduction To SUSE

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

OpenSAP Introduction To SUSE

Caricato da

Copyright:

Formati disponibili

Week 1 Unit 1:

Flavors of SUSE Linux

There are two primary types of SUSE Linux:

openSUSE is an open source project, SUSE being the primary contributor.

openSUSE Leap openSUSE Tumbleweed

If you are new to openSUSE (and even open source software):

SUSE Linux Enterprise Server (SLES) is a refined and enhanced openSUSE.

SLES Common Code Base

There are multiple ways to start YaST:

o Get root permissions:

Command Terminal in X Command Line

The graphical interface of YaST is organized

Categories are on the left and organize the

Like the graphical interface of YaST, the

YaST has a series of modules that allow configuration of various components.

In order to use SCC or an RMT, you will need a

Note that dependencies between modules are not handled

Before any changes are written to disk for the installation

SLES has a series of modules that allow configuration of various components.

An intelligent software-defined storage solution, powered by CEPH technology, which

The FHS is maintained by the Linux Foundation

/bin – user binaries /mnt – temporarily mounted filesystems

/var/spool – queues (printers, email) log

/var/run – information about running processes

There are 7 different file types in Linux:

File1link.txt File1.txt Symlink-to-File1.txt

Process 1234 Process 4321

• Pipes (sometimes called a FIFO – First In First Out)

Process 9876 Process 6789

• Device file represent hardware

• Types of device files

• Block device files are primarily used for storage

Partition numbers are appended to the device name:

• Character devices provide unbuffered access directly to a hardware device

• Examples of character devices:

• Users, groups and passwords are stored in the following files:

• The fields of /etc/passwd are as follows:

• The fields of /etc/shadow are as follows:

• The fields of /etc/group are as follows:

useradd Create users

usermod Modify existing users

userdel Delete users

groupadd Create groups

groupmod Modify existing groups

groupdel Delete groups

passwd Set/Modify user passwords

gpasswd Set/Modify group passwords

Type and permissions

Links and contents

• Anyone that is not the owning user, or in the group that

Notation User Group Other

o chown – Change file user and/or group ownership

o chgrp – Change group ownership

• Set Group ID (SGID)

User Group Other

• Set User ID (SUID)

User Group Other

o newgrp, sg – Switch primary group

SUSE default (root’s password) User’s password

The primary configuration file for sudo is /etc/sudoers.

Aliases are frequently used together to simplify sudo administration.

User_Alias POWERUSERS = tux, geeko

RPM is made up of several components: