Package and System Management Tools for SUSE Linux Enterprise Server and openSUSE

By: coolguys-suse

June 3, 2013 1:03 am





By Dobrin Dobrev

The purpose of this page is to point out some tools for package and system management specific to SUSE Linux Enterprise Server and openSUSE.

This page is linked from the images which run SUSE in a cloud provider environment so some prior Linux experience is assumed.

Install Additional Software

SUSE Linux Enterprise Server and openSUSE use zypper for package management and YaST for system administration.

Full description of zypper commands.

Best usage is under root. Some of the most popular uses are:

To search for nmap: zypper search nmap

To install nmap: sudo zypper in nmap

To list repositories: zypper lr

To list updates : zypper lu

To patch the system: zypper patch

There are many more zypper commands in addition to this short list. Explore a full description of zypper commands, or type zypper -h

System Management

The system management tool YaST can be run as yast from the command line. To run YaST, you must be root. More information can be found here:

In case you need to install YaST after you have already set up the image, run this from the command line:

zypper install --type pattern yast2_basis

Once installed, just type yast as root to see this screen: (click image to enlarge)


Cloud-Specific Info

Microsoft Azure

Amazon EC2

SUSE Linux Enterprise Server launched on Amazon EC2 in August 2010. Follow the links below to deploy a SUSE image on Amazon and for more information.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Tags: , , ,
Categories: SLES on Azure, SUSE in the Cloud, SUSE Linux Enterprise Server, SUSE Studio, Technical Solutions

Disclaimer: As with everything else at SUSE Conversations, this content is definitely not supported by SUSE (so don't even think of calling Support if you try something and it blows up).  It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.