Use these instructions if there is no existing Linux system on your machine, or if you want to replace an existing Linux system.

To open the Main Menu, click the Main Menu icon in the panel or press Alt+F1.

Favorites shows a default selection of key programs for quick access, whereas Applications shows all applications installed on your system. To navigate through the menu structure, click an entry and use the arrow icons at the right or the left to switch back and forth. Computer and Recently Used provide quick access to some frequently used places, applications, or documents. Leave shows several options for leaving the session such as logging out, locking the screen (access can only be regained with a password), shutting down or restarting the computer. Some computers offer to suspend your session to RAM or disc.

If you often need a program and do not want to dig into the menu structure, you can integrate the icon into the Favorites tab. Right-click the icon on any of the other tabs and choose Add to Favorites.

KRunner is a helper application that lets you quickly start programs. Apart from that, it offers a search function for finding applications or locations.

Press Alt+F2 to open the Run Command dialog. Type a command, for example, dolphin. While you are typing, the dialog shows a list of applications or actions that match your input. Select one of the results or press Enter to start the highlighted application or action. The command to start the application is often (but not always) the application name written in lowercase.

The Run Command dialog allows you also to use different features. Click on the question mark icon to see a list of active features. To configure or get a list of all features, click on the wrench icon. You can use so-called Web shortcuts defined in Konqueror to send search requests directly to a search engine without first opening the browser. Another interesting feature is to calculate a mathematical expression like =2+2^4-sin(2). Very useful is to convert units, for example, from miles per hour into kilometres per hour. Just insert the expression 60 mph in km/h to get the converted value.

Both the Main Menu and the Run Command dialog offer a search function that lets you quickly start programs even if you do not already know the exact application name or command. To search for an application, start typing a command or part of the application name in the Main Menu Search field or the input field in the Run Command dialog. Each character you enter narrows down the search.

From the list below the input field, choose the application matching your query.

Desktop elements can be locked in their current position to prevent them from being moved around on the desktop. As long as the desktop elements are locked you cannot add, move, or remove any objects to or from your desktop.

To lock or unlock the desktop elements, click the cashew icon (desktop toolbox) at the upper right corner of the desktop and select Lock Widgets or Unlock Widgets.

Alternatively, right-click an empty patch on the desktop and select Lock Widgets or Unlock Widgets.

In the following, you can find some examples of how to change individual desktops elements.

To delete an icon from your desktop, right-click the program icon and select Remove this Icon.

Apart from changing individual desktop elements, KDE allows you to personalize your desktop to a very high degree. Possibilities to adjust the overall appearance and behavior of your desktop can be found in the Personal Settings configuration dialog.

Start the Personal Settings from the Main Menu by selecting Favorites+Configure Desktop.

The settings are grouped into different categories. Hover over an icon to see more details. Performing tasks in some areas of the personal settings requires system administrator (root) permissions.

Change the settings as desired. No changes take effect until you click Apply. To discard changes in the recent view that you have not yet applied, click Reset. To reset all items in the recent view to the default values, click Defaults.

To get back to the start-up view (showing all categories) again, click Overview at the top left corner of the dialog. You can also enter a search string at the top of the window (for example, Screen Saver) to find the category which holds options related to the search string. Each character you enter in the Search field further narrows the search.

For easier overview of all categories, you can also switch to a tree view by clicking Configure and selecting another View Style.

The Dolphin main window consists of the following elements:

Menu Bar:  The menu bar holds menu items for actions like copying, moving, or deleting files, changing views, starting additional tools, defining your settings, and getting help.

Toolbar:  The toolbar provides quick access to frequently used functions that can also be accessed via the menu. If you hover the mouse pointer over an icon, a short description is displayed.

Location Bar:  The location bar displays the path to the current directory. It is available in two versions: one shows the path to the current directory with icons for every parent folder in a “bread crumb” view. Click any icon in the bread crumb view to change to that directory. The second version of the location bar shows the path to the current directory as a string of text you can edit.

Panels:  By default, Dolphin shows the Places panel. It allows quick access to some often-used places like your home directory, the root directory of the file system (/), the trash bin, and removable media. There are several other panels you can add to the main window by clicking View+Panels.

Display Field (Working Space):  The display field shows the contents of the selected directory or file. By default, Dolphin displays the contents of your home directory on start-up. By default, clicking a folder or file in Dolphin directly starts an action: Dolphin loads the file into an application for further processing or opens the folder.

Status Bar:  Shows the file type and size of the currently selected object and allows you to enlarge or diminish the size of the icons or entries shown in the display field.

To perform actions like copying, moving, creating or deleting files, you need appropriate permissions to the folders and files involved in your action.

To copy, move, or delete a file or folder, proceed as follows:

To quickly filter for certain filenames in the current directory, press Ctrl+I to add the Filter input field to the bottom of the Dolphin main window. Type any part of the filename you are searching for to see all files in the current directory containing the search string. For more detailed and advanced searches, press Ctrl+F to use the desktop search. For more information, refer to Section 2.14.2, “Using Strigi Desktop Search”.

Dolphin offers many options for adjusting the view and the overall settings according to your preferences.

Detach the panels from the main Dolphin window by clicking the left icon at the top of each panel. Click the panel's title bar and drag it to another place on the desktop. To reintegrate the panel into the Dolphin window, click the left symbol at the top of the panel again.

Both browsers offer different kinds of search options: you can find information on the Web or you can search the current Web page for keywords.

Konqueror offers predefined Web shortcuts for quickly searching the Web. For example, to search the Web for yast using the Google search engine, just type gg: yast into the Konqueror location bar (or the Run Command dialog) and press Enter.

You can also define individual Web shortcuts in Konqueror and Firefox as described in Section 2.8.3, “Configuring Preferences”.

If you download a file with Firefox or Konqueror, a dialog window appears asking you if you want to save the file or to open it with a specific application. Also choose if to remember the action you selected for this type of file. By default, Firefox saves the file to the folder configured in the Firefox Preferences and shows your finished downloads in the Downloads dialog.

To open the downloaded files directly from there, right-click and select Open. To clean up the history of downloaded files, click Clear List.

Adjust preferences in Konqueror or Firefox. In Konqueror, access the configuration dialog with Settings+Configure Konqueror. To change the behavior of Konqueror as Web browser, select one of the Web Browsing sub categories in the left sidebar to show the options for the relevant category. For example, you can “hide” Konqueror's real identity and make Konqueror identify as a different browser (for example, Internet Explorer*) for certain Web sites you visit. To do so, select Browser Identification, and click New to add a new, site-specific identification.

You might also want to configure the Web shortcuts you can use with Konqueror (and the Run Command dialog). In the Konqueror configuration dialog, click Web Shortcuts to see which shortcuts are already defined. Click New to define new shortcuts. Leave the Konqueror configuration dialog with OK to apply your changes.

In Firefox, select Edit+Preferences to open the Firefox Preferences. Click the icons in the upper display field to access the options for the relevant category. For example, change the default download folder on the General page, or adjust the pop-up blocking feature on the Content page. Click OK to apply the changes.

To configure a Web shortcut for a search in Firefox, browse to the Web page with the desired search field. Right-click the search field and choose Add a Keyword for this Search.... Enter a Keyword and leave the dialog with OK.

To start Kontact, press Alt+F2 and enter kontact. To access one of its components like KMail, click the corresponding icon in the left sidebar.

Before you can send or receive mails, you must configure an e-mail identity and account:

To write a new mail, click the Mail icon in the Kontact main window and press Ctrl+N to open the mail composer. After you have finished your mail, click Send to send it immediately. In case you have configured multiple e-mail accounts, keep the Send button pressed, then select the account from which you want to send the mail.

Apart from PDF files, Okular allows you to view a great number of file formats, such as PostScript, several image formats, OpenDocument format (ODF), OpenDocument text (ODT), some eBook formats (ePub), and even Microsoft* Compiled HTML Help (CHM). Okular also provides support for bookmarks, annotations, form fields and multimedia content, and the rotation of pages.

Start Okular from the Main Menu or press Alt+F2 and enter okular.

To open a document, select File+Open and choose the desired file from the file system. Navigate through the document by using the navigation icons at the top or bottom of the window. Depending on which icon you click on the navigation panel on the left, the sidebar either shows a table of Contents, a Thumbnail view of each page, the Reviews, or your Bookmarks for this file. To filter for any text listed in the sidebar or the overall document, enter a string into the input field at the top of the sidebar. If you want to select and copy text or images from the file in Okular, click the Selection icon in the toolbar and select one of the options from the context menu. Click the Browse icon to switch back to browsing the document.

If Acrobat Reader is not installed by default, install the acroread package with YaST. To start Acrobat reader, press Alt+F2 and enter acroread. Click File+Open, locate the desired PDF file and click Open to view the file.

To perform basic and advanced searches, use KFind. Start it from the Main Menu by clicking Applications+Find Files/Folders or press Alt+F2 and enter kfind.

Strigi Desktop Search offers advanced search capabilities,by additionally searching for metadata such as tags, ratings, and even source URLs for downloads. It requires the services nepomuk and strigi to run. To activate these services, press Alt+F2 and enter strigi. Choose Nepomuk/Strigi server Configuration to start the configuration dialog. Enable the two services on the tab Basic Settingsand leave the dialog by clicking Apply and OK.

Once activated, you can use KRunner (Alt+F2) to search for files by just typing a keyword. A more advanced search interface is available in the Dolphin file manager. Press Ctrl+F in Dolphin to activate the desktop search. You can filter the search results for Filename, Content or location.

Click the Main Menu button on your panel and select Leave+Logout. This ends your session but leaves the system running. To start a parallel session as a different user, select Leave+Switch User instead.

Click Leave, then select one of the following options:

The bottom panel can be customized to meet your individual needs, and additional panels can be added and configured to further personalize your desktop.

To add a new panel, right-click a blank space in the bottom panel and select New Panel. To delete a panel, right-click a blank space in the panel and select Delete This Panel. openSUSE requires that at least one panel is left on the desktop.

To run a program in openSUSE, click Computer on the panel to open the main menu screen. If the program you want does not appear in the main menu screen, click More Applications to view a list of all available applications grouped in categories. You can also limit the list to show only applications with a specific name by entering all or part of the name into the Filter field. Click an entry in the list to start the corresponding program.

You can also add an icon to your panel that opens a more traditional version of the main menu. Right-click a blank space on the panel, select Add to Panel, then double-click Traditional Main Menu.

If you already know the name of an application but are not sure how to start it from the main menu, use the Search field in the main menu. Click Computer, type a portion of the application name in the Search field, then press Enter. If the application is installed on your system, the name of the application appears in the Needle search dialog box. Click the name to start the program.

Press Alt+F2 to open the Run Application dialog. Type a command, for example, f-spot, and press Enter or click Run to start the application. The command to start the application is often (but not always) the application name written in lowercase.

To delete an icon from your desktop, simply click the program icon and press the Delete key on your keyboard.

In addition to letting you change individual desktop elements, GNOME lets you extensively personalize your desktop. You can find more settings to adjust the overall appearance and behavior of your desktop in the GNOME Control Center. There, you can also change fonts, keyboard and mouse configurations, regional and language settings, parameters for your Internet and network usage, and more.

To start the Control Center, click Computer, then click Control Center on the right of the main menu.

If you have files you have not used recently but want to keep on your computer, you can compress the files into a tape archive (TAR) format.

To extract an archived file, right-click the file and select Extract Here.

Use the Nautilus bookmarks feature to mark your favorite folders.

You can also organize your bookmarks list by clicking Bookmarks+Edit Bookmarks and making your selections in the dialog box.

To change the order of your bookmarks, click a bookmark shown in the Edit Bookmarks dialog and drag it to the desired location.

To search the current Web page for words, press Ctrl+F to open the Find bar at the bottom of the window. Enter your search keyword there and use the buttons to the right of the box to search in different directions or to select all hits in the text.

If you download a file with Firefox, the Firefox download manager starts and saves this file to the folder configured in Firefox Preferences. By default, the Downloads folder in your home directory is the destination for downloaded files. Firefox shows your finished downloads in the Downloads window.

Open the downloaded files directly from the Downloads window or from the destination folder. To clean up the history of downloaded files, click Clean List.

To adjust the default download folder or to activate or modify the pop-up blocking feature, click Edit+Preferences.

Here also configure many other settings such as appearance, language, privacy, and tab options. Click the icons and set the options on each page according to your preferences. Click Close to apply the changes.

To locate files or programs on your computer, click Computer. Enter a search term in the Search field and press Enter. The results are displayed in the Needle.

You can also start the Needle application by clicking Computer+More Applications+Accessories+Desktop Search.

GNOME Do describes itself as an “intelligent launcher that makes performing common tasks on your computer simple and efficient.” It is extensible with plug-ins.

Start it by pressing Super+Space. The Super is normally located on the left and right Windows or Penguin key.

GNOME Do allows you to perform specific actions. For example, if you type b, it displays a starter button for the Banshee, the music player:

To customize GNOME Do to your needs, select the arrow button on the upper-right corner of the window and select Preferences. It gives you a list of plug-ins to search for mails in Evolution, listen to your music, etc.

Click Computer+Logout, then select one of the following options:

Log out.  Logs you out of the current session and returns you to the login screen.

Switch User.  Suspends your session, allowing another user to log in and use the computer.

Click Computer+Shutdown, then select one of the following options:

Shutdown.  Logs you out of the current session, then turns off the computer.

Restart.  Logs you out of the current session, then restarts the computer.

Suspend.  Puts your computer in a temporary state that conserves power. The state of your session is preserved, however, including all applications you have running and all documents you have open.

Hibernate.  Suspends your session, using no power until the computer is restarted. The state of your session is preserved, however, including all applications you have running and all documents you have open.

In all modules you can save your documents as native LibreOffice files, LibreOffice templates, Microsoft files and StarOffice files.

The Navigator tool displays information about the contents of a document. It also lets you quickly jump to different elements. For example, you can use the Navigator to get a quick overview of all images included in the document. To open the Navigator, click View+Navigator or with F5. The elements listed in the Navigator vary according to the LibreOffice module being used.

You can also navigate your files with the following shortcuts:

LibreOffice comes with a set of predefined templates, and you can find additional templates on the Internet. If you want to create your own templates, you need to determine what you want the document to look like and create the styles you need in that template.

For text document, spreadsheets, presentations, and drawings, you can easily create a template from an existing document as follows:

LibreOffice Writer allows you to create a new document in one of the following ways:

To use a standard format and predefined elements for your own documents, try a wizard (a small utility that lets you make some basic initial decisions and then produces a ready-made document from a template). For example, to create a business letter, click File+Wizards+Letter. With the wizard's dialogs, you can create a basic document that uses a standard format.

Enter text in the document window as desired. Use the Formatting toolbar or the Format menu to adjust the appearance of the document. Use the File menu or the relevant buttons in the toolbar to print and save your document. With the options under Insert, add extra items to your document, such as a table, picture, or chart.

With LibreOffice you can customize the default settings with the Format menu.

Below is a list of the most popular options available in most modules:

If you are working with a very large document (such as a book), you might find it easier to manage the book with a master document, rather than keeping the book in a single file. A master document enables you to quickly apply formatting changes to a large document or to jump to each subdocument for editing.

A master document is a Writer document that serves as a container for multiple Writer files. You can maintain chapters or other subdocuments as individual files collected in the master document. Master documents are also useful if multiple people are working on a document. You can separate each person’s relevant part of the document into subdocuments, allowing multiple writers to work on their subdocuments at the same time without the danger of overwriting each other’s work.

The LibreOffice help files contain more complete information about working with master documents. Look for the topic entitled Working with Master Documents and Subdocuments.

In addition to being a full-featured word processor, Writer also functions as an HTML editor. Writer includes HTML tags that can be applied the same way as any other style in a Writer document. You can view the document as it will appear online, or you can directly edit the HTML code.

If you prefer to edit HTML code directly, or if you want to see the HTML code created when you edited the HTML file as a Writer document, click View+HTML Source. In HTML Source mode, the Formatting and Styles list is not available. The first time you switch to HTML Source mode, you are prompted to save the file as HTML, if you have not already done so.

You can include tabular data in the Writer, Impress and Draw module. Insert basic tables directly into your document either with the following menus items or by using the toolbar:

To enter data, select a cell with your mouse pointer and begin typing. To move around cells, use the arrow keys. →| moves to the next cell, skipping over the contents of the cell and Shift+→| moves backwards.

You can use Table menu or the Table toolbar to modify the table.

Start LibreOffice and select File+New+Spreadsheet to create a new spreadsheet. Access the individual sheets by clicking the respective tabs at the bottom of the window.

Enter data in the cells as desired. To adjust appearance, either use the Formatting toolbar or the Format menu—or define styles. Use the File menu or the relevant buttons in the toolbar to print and save your document.

Calc comes with a few built-in cell and page styles to improve the appearance of your spreadsheets and reports. Although these built-in styles are adequate for many uses, you will probably find it useful to create styles for your own frequently-used formatting preferences.

Use LibreOffice Impress to create presentations for screen display or printing, such as slide shows or transparencies. If you have used other presentation software, you can move comfortably to Impress, which works very similarly to other presentation software.

Impress can open and save Microsoft Powerpoint presentations, which means you can exchange presentations with Powerpoint users, as long as you save your presentations in Powerpoint format.

LibreOffice allows you to use 3D transitions for your slides. Access the available transitions by selecting Slide Show+Slide Transitions.

You can either create a brand new presentation (without any preformatted slides) or use an existing template or presentation for your new document. Impress uses styles and templates the same way other LibreOffice modules do. A wizard leads you through the options available for creating new presentations.

LibreOffice includes a database module (Base). Use Base to design a database to store many different kinds of information, from a simple address book or recipe file to a sophisticated document management system.

Tables, forms, queries, and reports can be created manually or using convenient wizards. For example, the Table Wizard contains a number of common fields for business and personal use. A wizard guides you through the steps to create a new database.

LibreOffice Base comes with several predefined database fields to help you create a database. A wizard guides you through the steps to create a new database. The following steps are specific to creating an address book using predefined fields, but it should be easy to use the predefined fields for any of the built-in database options. The process for creating a database can be broken into several subprocesses:

Use LibreOffice Draw to create graphics and diagrams. You can save your drawings in today’s most common formats and import them into any application that lets you import graphics, including the other LibreOffice modules. You can also create Flash versions of your drawings.

LibreOffice allows you to import Scalable Vector Graphics (*.svg) and WordPerfect Graphics (*.wpg). Select File+Open and use the Filter drop-down list to view which file formats can be opened.

To embed an existing Draw graphic into an LibreOffice document, select Insert+Object+OLE Object. Select Create from file and click Search to navigate to the Draw file to insert. If you insert a file as OLE object, you can easily edit the object later by double-clicking it.

It is usually difficult to include complex mathematical formulas in your documents. The LibreOffice Math equation editor lets you create formulas using operators, functions, and formatting assistants. You can then save those formulas as objects that can be imported into other documents. Math functions can be inserted into other LibreOffice documents like any other graphic object.

Using Math, you can enter your equation in three different ways:

Math is not a calculator. The functions it creates are graphical objects. Even if they are imported into Calc, these functions cannot be evaluated.

The YaST software manager can install packages or patterns from all currently enabled repositories. It offers different views and filters to make it easier to find the software you are searching for. The Search view is the default view of the window. To change view, click View and select one of the following entries from the drop-down list. The selected view opens in a new tab.

	Finding Packages not Belonging to an Active Repository
To list all packages that do not belong to an active repository, choose View+Repositories+@System and then choose Secondary Filter+Unmaintained Packages. This is useful, for example, if you have deleted a repository and would like to make sure no packages from that repository remain installed.

Certain packages are dependent on other packages, such as shared libraries. On the other hand, some packages cannot coexist with others on the system. If possible, YaST automatically resolves these dependencies or conflicts. If your choice results in a dependency conflict that cannot be automatically solved, you need to solve it manually as described in Section 5.2.4, “Checking Software Dependencies”.

	Removal of Packages
When removing any packages, by default YaST only removes the selected packages. If you want YaST to also remove any other packages that become unneeded after removal of the specified package, select Options+Cleanup when deleting packages.

	Installing Source Packages
Installing source packages with YaST Software Manager is not possible at the moment. Use the command line tool zypper for this purpose. For more information, see Section 9.1.2.1, “Installing Source Packages”.

Instead of updating individual packages, you can also update all installed packages or all packages from a certain repository. When mass updating packages, the following aspects are generally considered:

Which of the aspects has the highest importance for choosing the update candidates depends on the respective update option you choose.

Most packages are dependent on other packages. If a package, for example, uses a shared library, it is dependent on the package providing this library. On the other hand some packages cannot coexist with each other, causing a conflict (for example, you can only install one mail transfer agent: sendmail or postfix). When installing or removing software, the Software Manager makes sure no dependencies or conflicts remain unsolved to ensure system integrity.

In case there exists only one solution to resolve a dependency or a conflict, it is resolved automatically. Multiple solutions always cause a conflict which needs to be resolved manually. If solving a conflict involves a vendor or architecture change, it also needs to be solved manually. When clicking Accept to apply any changes in the Software Manager, you get an overview of all actions triggered by the automatic resolver which you need to confirm.

By default, dependencies are automatically checked. A check is performed every time you change a package status (for example, by marking a package for installation or removal). This is generally useful, but can become exhausting when manually resolving a dependency conflict. To disable this function, uncheck Dependencies+Autocheck. Manually perform a dependency check with Dependencies+Check Now. A consistency check is always performed when you confirm your selection with Accept.

To review a package's dependencies, right-click it and choose Show Solver Information. A map showing the dependencies opens. Packages that are already installed are displayed in a green frame.

	Manually Solving Package Conflicts
Unless you are very experienced, follow the suggestions YaST makes when handling package conflicts, otherwise you may not be able to resolve them. Keep in mind that every change you make, potentially triggers other conflicts, so you can easily end up with a steadily increasing number of conflicts. In case this happens, Cancel the Software Manager, Abandon all your changes and start again.

Figure 5.1. Conflict Management of the Software Manager¶

The easiest way to find a package is to use the search field in the upper right corner of the software manager. Enter a search term and press Enter. By default it will search package names and summaries. Press the search item to change this filter and search the file lists, for example.

The software manager also offers different views and filters for displaying package lists. These are available from the pull-down menu in the upper left corner:

The box in the lower right corner of the dialog also allows to filter for packages that are Installed, Not Installed or Upgradable. If you select the No Status entry, all available packages from the configured repositories are displayed, independent of their status.

Instead of updating individual packages, you can also update all installed packages or all packages from a certain repository. When mass updating packages, the following aspects are generally considered:

Which of the aspects has the highest importance for choosing the update candidates depends on the respective update option you choose.

Most packages are dependent on other packages. If a package, for example, uses a shared library, it will be dependent on the package providing this library. On the other hand, some packages cannot coexist with each other, causing a conflict (for example, you can only install one mail transfer agent: sendmail or postfix). When installing or removing software, the Software Manager makes sure no dependencies or conflicts remain unresolved to ensure system integrity.

In case there exists only one solution to resolve a dependency or a conflict, it is resolved automatically. Multiple solutions always cause a conflict which needs to be resolved manually. If solving a conflict involves a vendor or architecture change, it also needs to be solved manually. When clicking Apply to apply any changes in the Software Manager, you get an overview of all actions triggered by the automatic resolver which you need to confirm.

By default, dependencies are automatically checked. A check is performed every time you change a package status (for example, by marking a package for installation or removal). This is generally useful, but can become exhausting when manually resolving a dependency conflict. To disable this function, uncheck Dependencies+Autocheck. Manually perform a dependency check with Dependencies+Check Now. A consistency check is always performed when you confirm your selection with Apply.

	Manually Solving Package Conflicts
Unless you are very experienced, follow the suggestions YaST makes when handling package conflicts, otherwise you may not be able to resolve them. Keep in mind that every change you make, potentially triggers other conflicts, so you can easily end up with a steadily increasing number of conflicts. In case this happens, click Cancel and Quit the software manger. Relaunch it to start again.

Figure 5.2. Conflict Management of the Software Manager¶

You can either add repositories from a local harddisk, from a removable medium (like a CD, DVD or a USB mass storage) or from a network.

To add repositories from the Configured Software Repositories dialog in YaST proceed as follows:

Now you can install software from this repository as described in Section 5.2, “Using the KDE Interface (Qt)” or in Section 5.3, “Using the GNOME Interface (GTK+)”.

YaST also offers a list of predefined popular repositories available under Community Repositories. Among others, it includes driver repositories for nVidia and ATI graphics cards, and popular projects from the openSUSE® Build Service, such as the Mozilla repository (containing packages with the most recent versions of Firefox and Thunderbird).

The Configured Software Repositories overview of the Software Repositories lets you change the following repository properties:

To ensure their integrity, software repositories can be signed with the GPG Key of the repository maintainer. Whenever you add a new repository, YaST offers to import its key. Verify it as you would do with any other GPG key and make sure it does not change. If you detect a key change, something might be wrong with the repository. Disable the repository as an installation source until you know the cause of the key change.

To manage all imported keys, click GPG Keys... in the Configured Software Repositories dialog. Select an entry with the mouse to show the key properties at the bottom of the window. Add, Edit or Delete keys with a click on the respective buttons.

The Software Updater icon resides in the system tray of your panel depicting a gearwheel with a green arrow. To start Software Updater manually, choose System Settings+SoftwareManagement+Software Updates from the main menu. Alternatively, Alt+F2 and enter kpk_update.

	Icon Visibility
The Software Updater icon is only visible in the system tray, if patches are available. Hover over the icon to see the number of patches available.

5.5.1.1. Installing Patches¶

1. Whenever software updates are available, the applet icon appears in the panel. Left-click the Software Updater icon to launch the Review and Update software window.

2. Select a patch for installation by ticking its checkbox. Get detailed information on a patch by clicking on its title. To select all available patches for installation, tick the checkbox in the table header.

3. Click Apply to start the patch installation.

4. In case you have started the patch installation for the first time, you will be asked to enter the root password twice in order to proceed. If you also check Remember authorization you will never be asked again to provide the password.

5. The Additional Changes window showing an installation summary opens. Click Continue to finish the installation.

Figure 5.3. KDE Software Updater

The YaST Online Update offers advanced features to customize the patch installation. Please refer to Chapter 6, YaST Online Update for more information.

5.5.1.2. Configuring the KDE Software Updater¶

By default Software Updater checks for updates every 24 hours, notifies you when patches are available and does not automatically install patches. These settings can be changed with the Software Management settings. To open the Software Management settings choose System Settings+Software Management+Settings from the main menu. Alternatively, press Alt+F2 and enter kpk_settings. The settings for Software Updater are available in the Update Settings section.

	Patch Origin
The Software Management settings also allows you to configure the repositories (Origin of Packages) to be used. This setting not only applies to Software Updater but also to the KDE Software Management module (Get and Remove Software). Make sure the repository Updates for openSUSE 12.1 is always selected—otherwise you will not receive patches.

The update applet resides in the notification area of the panel. Its icon changes depending on the availability and relevance of patches and the status of the update. To invoke the applet manually, choose Computer+More Applications+System+Software Update.

	Icon visibility
By default, the update applet icon is only visible in the notification area, if patches are available.

5.5.2.1. Installing Patches¶

Procedure 5.2. Installing Patches

1. Whenever new patches are available, a notification message will appear and the Update Applet icon will be visible in the notification area. Either click Install updates in the notification message or click the icon to open the Software Update window.

2. All security and important patches are preselected. It is strongly recommended to install these patches. Trivial patches can be manually selected by ticking the respective check boxes. Get detailed information on a patch by clicking on its title.

3. Click Install Updates to start the patch installation.

4. The Additional Confirmation Required window showing an installation summary opens. Click Continue to proceed.

5. Enter the root password in the authentication screen and proceed with Authenticate.

Figure 5.4. GNOME Update Applet

The YaST Online Update offers advanced features to customize the patch installation. Please refer to Chapter 6, YaST Online Update for more information.

The Online Update window consists of four sections.

Figure 6.1. YaST Online Update—Qt Interface

The Summary section on the left lists the available patches for openSUSE. The patches are sorted by security relevance: security, recommended, and optional. You can change the view of the Summary section by selecting one of the following options from Show Patch Category:

Each list entry in the Summary section consists of a symbol and the patch name. For an overview of the possible symbols and their meaning, press Shift+F1. Actions required by Security and Recommended patches are automatically preset. These actions are Autoinstall, Autoupdate and Autodelete.

If you install an up-to-date package from a repository other than the update repository, the requirements of a patch for this package may be fulfilled with this installation. In this case a check mark is displayed in front of the patch summary. The patch will be visible in the list until you mark it for installation. This will in fact not install the patch (because the package already is up-to-date), but mark the patch as having been installed.

Select an entry in the Summary section to view a short Patch Description at the bottom left corner of the dialog. The upper right section lists the packages included in the selected patch (a patch can consist of several packages). Click an entry in the upper right section to view details about the respective package that is included in the patch.

The Online Update window consists of four main sections.

Figure 6.2. YaST Online Update—GTK Interface

The upper right section lists the available (or already installed) patches for openSUSE. To filter patches according to their security relevance, click the corresponding Priority entry in the upper right section of the window: Security, Recommended, Optional or Any priority.

If all available patches are already installed, the Package listing in the upper right section will show no entries. The box in the bottom left-hand section shows the number of both available and already installed patches and lets you toggle the view to either Available or Installed patches.

Select an entry in the Package listing section to view a patch description and further details at the bottom right corner of the dialog. As a patch can consist of several packages, click the Applies to entry in the lower right section to see which packages are included in the respective patch.

Click on a patch entry to open a row with detailed information about the patch in the bottom of the window. Here you can see a detailed patch description as well as the versions available. You can also choose to Install optional patches—security and recommended patches are already preselected for installation.

The general syntax of Zypper is:

zypper [global-options]command[command-options][arguments] ...

The components enclosed in brackets are not required. The simplest way to execute Zypper is to type its name, followed by a command. For example, to apply all needed patches to the system type:

zypper patch

Additionally, you can choose from one or more global options by typing them just before the command. For example, --non-interactive means running the command without asking anything (automatically applying the default answers):

zypper --non-interactive patch

To use the options specific to a particular command, type them right after the command. For example, --auto-agree-with-licenses means applying all needed patches to the system without asking to confirm any licenses (they will automatically be accepted):

zypper patch --auto-agree-with-licenses

Some commands require one or more arguments. When using the install command, for example, you need to specify which package(s) to install:

zypper install mplayer

Some options also require an argument. The following command will list all known patterns:

zypper search -t pattern

You can combine all of the above. For example, the following command will install the mplayer and amarok packages from the factory repository while being verbose:

zypper -v install --from factory mplayer amarok

The --from option makes sure to keep all repositories enabled (for solving any dependencies) while requesting the package from the specified repository.

Most Zypper commands have a dry-run option that does a simulation of the given command. It can be used for test purposes.

zypper remove --dry-run MozillaFirefox

To install or remove packages use the following commands:

zypper install package_name
zypper remove package_name

Zypper knows various ways to address packages for the install and remove commands:

To install and remove packages simultaneously use the +/- modifiers. To install emacs and remove vim simultaneously, use:

zypper install emacs -vim

To remove emacs and install vim simultaneously, use:

zypper remove emacs +vim

To prevent the package name starting with the - being interpreted as a command option, always use it as the second argument. If this is not possible, precede it with --:

zypper install -emacs +vim       # Wrong
zypper install vim -emacs        # Correct
zypper install -- -emacs +vim    # same as above
zypper remove emacs +vim         # same as above

If (together with a certain package) you automatically want to remove any packages that become unneeded after removing the specified package, use the --clean-deps option:

rm package_name --clean-deps

By default, Zypper asks for a confirmation before installing or removing a selected package, or when a problem occurs. You can override this behavior using the --non-interactive option. This option must be given before the actual command (install, remove, and patch) as in the following:

zypper --non-interactive install package_name

This option allows the use of Zypper in scripts and cron jobs.

	Do not Remove Mandatory System Packages
Do not remove packages such as glibc, zypper, kernel, or similar packages. These packages are mandatory for the system and, if removed, may cause the system to become unstable or stop working altogether.

zypper source-install package_name

zypper source-install -D package_name # source package only
zypper source-install -d package_name # build dependencies only

zypper search -t srcpackage

zypper verify

zypper install-new-recommends

There are three different ways to update software using Zypper: by installing patches, by installing a new version of a package or by updating the entire distribution. The latter is achieved with the zypper dist-upgrade command which is discussed in Section 16.1, “Upgrading the System”.

zypper patch

zypper patch --bugzilla=number

zypper patch --cve=number

zypper patch --cve=CVE-2010-2713

zypper update

zypper update package_name
zypper install package_name

zypper list-updates

zypper list-updates --all

9.1.3.3. Upgrading to a New Product Version¶

To easily upgrade your installation to a new product version (for example, from openSUSE 11.4 to openSUSE 12.1), first adjust your repositories to match the current openSUSE repositories. For details, refer to Section 9.1.4, “Managing Repositories with Zypper”. Then use the zypper dist-upgrade command with the required repositories. This command ensures that all packages will be installed from the repositories currently enabled. For detailed instructions, refer to Section 16.1.4, “Distribution Upgrade with zypper”.

To restrict the distribution upgrade to packages from a certain repository while considering also the other repositories for satisfying dependencies, use the --from option and specify the repository by either its alias, its number or URI.

Differences between zypper update and zypper dist-upgrade

Choose zypper update to update packages to newer versions available for your product version while maintaining system integrity. zypper update will honor the following rules: no vendor changes no architecture changes no downgrades keep installed packages When executing zypper dist-upgrade, all packages will be installed from the repositories currently enabled. This rule is enforced, so packages might change vendor or architecture or even might get downgraded. All packages that have unfulfilled dependencies after the upgrade will be uninstalled.

All installation or patch commands of Zypper rely on a list of known repositories. To list all repositories known to the system, use the command:

zypper repos

The result will look similar to the following output:

# | Alias                 | Name                  | Enabled | Refresh
--+-----------------------+-----------------------+---------+--------
1 | Updates               | Updates               | Yes     | Yes
2 | openSUSE 11.2-0       | openSUSE 11.2-0       | No      | No
3 | openSUSE-11.2-Debug   | openSUSE-11.2-Debug   | No      | Yes
4 | openSUSE-11.2-Non-Oss | openSUSE-11.2-Non-Oss | Yes     | Yes
5 | openSUSE-11.2-Oss     | openSUSE-11.2-Oss     | Yes     | Yes
6 | openSUSE-11.2-Source  | openSUSE-11.2-Source  | No      | Yes

When specifying repositories in various commands, an alias, URI or repository number from the zypper repos command output can be used. A repository alias is a short version of the repository name for use in repository handling commands. Note that the repository numbers can change after modifying the list of repositories. The alias will never change by itself.

By default, details such as the URI or the priority of the repository are not displayed. Use the following command to list all details:

zypper repos -d

zypper addrepo URIalias

zypper removerepo 3

zypper modifyrepo -er -p 20 'updates'

zypper renamerepo 'Mozilla Firefox' firefox

Zypper offers various methods to query repositories or packages. To get lists of all products, patterns, packages or patches available, use the following commands:

zypper products
zypper patterns
zypper packages
zypper patches

To query all repositories for certain packages, use search. It works on package names, or, optionally, on package summaries and descriptions. Using the wildcards * and ? with the search term is allowed. By default, the search is not case-sensitive.

zypper search firefox       # simple search for "firefox"
zypper search "*fire*"      # using wildcards
zypper search -d fire       # also search in package descriptions and summaries
zypper search -u firefox    # only display packages not already installed

To search for packages which provide a special capability, use the command what-provides. For example, if you would like to know which package provides the perl module SVN::Core, use the following command:

zypper what-provides 'perl(SVN::Core)'

To query single packages, use info with an exact package name as an argument. It displays detailed information about a package. To also show what is required/recommended by the package, use the options --requires and --recommends:

zypper info --requires MozillaFirefox

The what-provides package is similar to rpm -q --whatprovides package, but rpm is only able to query the RPM database (that is the database of all installed packages). Zypper, on the other hand, will tell you about providers of the capability from any repository, not only those that are installed.

Zypper now comes with a configuration file, allowing you to permanently change Zypper's behavior (either system-wide or user-specific). For system-wide changes, edit /etc/zypp/zypper.conf. For user-specific changes, edit ~/.zypper.conf. If ~/.zypper.conf does not yet exist, you can use /etc/zypp/zypper.conf as template: copy it to ~/.zypper.conf and adjust it to your liking. Refer to the comments in the file for help about the available options.

In case you have problems to access packages from configured repositories (for example, zypper cannot find a certain package though you know that it exists in one the repositories), it can help to refresh the repositories with:

zypper refresh

If that does not help, try

zypper refresh -fdb

This forces a complete refresh and rebuild of the database, including a forced download of raw metadata.

If the btrfs file system is used on the root partition and snapper is installed, zypper automatically calls snapper (via script installed by snapper) when committing changes to the file system to create appropriate file system snapshots. These snapshots can be used for reverting any changes made by zypper. For more information about snapper, see man snapper.

Zypper (and YaST) currently only make snapshots of the root filesystem. Other subvolumes cannot be configured. This feature is not supported on the default file system.

For more information on managing software from the command line, enter zypper help, zypper help command or refer to the zypper(8) manpage. For a complete and detailed command reference, including cheat sheets with the most important commands, and information on how to use Zypper in scripts and applications, refer to http://en.opensuse.org/SDB:Zypper_usage. A list of software changes for the latest openSUSE version can be found at . .

RPM packages have a GnuPG signature. To verify the signature of an RPM package, use the command rpm --checksig package-1.2.3.rpm to determine whether the package originates from Novell/SUSE or from another trustworthy facility. This is especially recommended for update packages from the Internet.

Normally, the installation of an RPM archive is quite simple: rpm -i package.rpm. With this command the package is installed, but only if its dependencies are fulfilled and if there are no conflicts with other packages. With an error message, rpm requests those packages that need to be installed to meet dependency requirements. In the background, the RPM database ensures that no conflicts arise—a specific file can only belong to one package. By choosing different options, you can force rpm to ignore these defaults, but this is only for experts. Otherwise, you risk compromising the integrity of the system and possibly jeopardize the ability to update the system.

The options -U or --upgrade and -F or --freshen can be used to update a package (for example, rpm -F package.rpm). This command removes the files of the old version and immediately installs the new files. The difference between the two versions is that -U installs packages that previously did not exist in the system, but -F merely updates previously installed packages. When updating, rpm updates configuration files carefully using the following strategy:

Following an update, .rpmsave and .rpmnew files should be removed after comparing them, so they do not obstruct future updates. The .rpmorig extension is assigned if the file has not previously been recognized by the RPM database.

Otherwise, .rpmsave is used. In other words, .rpmorig results from updating from a foreign format to RPM. .rpmsave results from updating from an older RPM to a newer RPM. .rpmnew does not disclose any information as to whether the system administrator has made any changes to the configuration file. A list of these files is available in /var/adm/rpmconfigcheck. Some configuration files (like /etc/httpd/httpd.conf) are not overwritten to allow continued operation.

The -U switch is not just an equivalent to uninstalling with the -e option and installing with the -i option. Use -U whenever possible.

To remove a package, enter rpm -e package. rpm, which only deletes the package if there are no unresolved dependencies. It is theoretically impossible to delete Tcl/Tk, for example, as long as another application requires it. Even in this case, RPM calls for assistance from the database. If such a deletion is, for whatever reason, impossible (even if no additional dependencies exist), it may be helpful to rebuild the RPM database using the option --rebuilddb.

To guarantee the operational security of a system, update packages must be installed in the system from time to time. Previously, a bug in a package could only be eliminated by replacing the entire package. Large packages with bugs in small files could easily result in this scenario. However the SUSE RPM offers a feature enabling the installation of patches in packages.

The most important considerations are demonstrated using pine as an example:

More information, including information about the patch feature of RPM, is available in the man pages of rpm and rpmbuild.

	Official Updates for openSUSE
In order to make the download size of updates as small as possible, official updates for openSUSE are not provided as Patch RPMs, but as Delta RPM packages. For details, see Section 9.2.4, “Delta RPM Packages”.

Delta RPM packages contain the difference between an old and a new version of an RPM package. Applying a delta RPM onto an old RPM results in a completely new RPM. It is not necessary to have a copy of the old RPM because a delta RPM can also work with an installed RPM. The delta RPM packages are even smaller in size than patch RPMs, which is an advantage when transferring update packages over the Internet. The drawback is that update operations with delta RPMs involved consume considerably more CPU cycles than plain or patch RPMs.

The prepdeltarpm, writedeltarpm and applydeltarpm binaries are part of the delta RPM suite (package deltarpm) and help you create and apply delta RPM packages. With the following commands, create a delta RPM called new.delta.rpm. The following command assumes that old.rpm and new.rpm are present:

prepdeltarpm -s seq -i info old.rpm > old.cpio
prepdeltarpm -f new.rpm > new.cpio
xdelta delta -0 old.cpio new.cpio delta
writedeltarpm new.rpm delta info new.delta.rpm

Finally, remove the temporary working files old.cpio, new.cpio, and delta.

Using applydeltarpm, you can reconstruct the new RPM from the file system if the old package is already installed:

applydeltarpm new.delta.rpm new.rpm

To derive it from the old RPM without accessing the file system, use the -r option:

applydeltarpm -r old.rpm new.delta.rpm new.rpm

See /usr/share/doc/packages/deltarpm/README for technical details.

With the -q option rpm initiates queries, making it possible to inspect an RPM archive (by adding the option -p) and also to query the RPM database of installed packages. Several switches are available to specify the type of information required. See Table 9.1, “The Most Important RPM Query Options”.

For example, the command rpm -q -i wget displays the information shown in Example 9.2, “rpm -q -i wget”.

Name        : wget                         Relocations: (not relocatable)
Version     : 1.11.4                            Vendor: openSUSE
Release     : 1.70                          Build Date: Sat 01 Aug 2009 09:49:48 CEST
Install Date: Thu 06 Aug 2009 14:53:24 CEST      Build Host: build18
Group       : Productivity/Networking/Web/Utilities   Source RPM: wget-1.11.4-1.70.src.rpm
Size        : 1525431                          License: GPL v3 or later
Signature   : RSA/8, Sat 01 Aug 2009 09:50:04 CEST, Key ID b88b2fd43dbdc284
Packager    : http://bugs.opensuse.org
URL         : http://www.gnu.org/software/wget/
Summary     : A Tool for Mirroring FTP and HTTP Servers
Description :
Wget enables you to retrieve WWW documents or FTP files from a server.
This can be done in script files or via the command line.
[...]

The option -f only works if you specify the complete filename with its full path. Provide as many filenames as desired. For example, the following command

rpm -q -f /bin/rpm /usr/bin/wget

results in:

rpm-4.8.0-4.3.x86_64
wget-1.11.4-11.18.x86_64

If only part of the filename is known, use a shell script as shown in Example 9.3, “Script to Search for Packages”. Pass the partial filename to the script shown as a parameter when running it.

#! /bin/sh
for i in $(rpm -q -a -l | grep $1); do
    echo "\"$i\" is in package:"
    rpm -q -f $i
    echo ""
done

The command rpm -q --changelog rpm displays a detailed list of change information about a specific package (in this case, the rpmpackage), sorted by date.

With the help of the installed RPM database, verification checks can be made. Initiate these with -V, -y or --verify. With this option, rpm shows all files in a package that have been changed since installation. rpm uses eight character symbols to give some hints about the following changes:

In the case of configuration files, the letter c is printed. For example, for changes to /etc/wgetrc (wget package):

rpm -V wget
S.5....T c /etc/wgetrc

The files of the RPM database are placed in /var/lib/rpm. If the partition /usr has a size of 1 GB, this database can occupy nearly 30 MB, especially after a complete update. If the database is much larger than expected, it is useful to rebuild the database with the option --rebuilddb. Before doing this, make a backup of the old database. The cron script cron.daily makes daily copies of the database (packed with gzip) and stores them in /var/adm/backup/rpmdb. The number of copies is controlled by the variable MAX_RPMDB_BACKUPS (default: 5) in /etc/sysconfig/backup. The size of a single backup is approximately 1 MB for 1 GB in /usr.

All source packages carry a .src.rpm extension (source RPM).

	Installed Source Packages
Source packages can be copied from the installation medium to the hard disk and unpacked with YaST. They are not, however, marked as installed ([i]) in the package manager. This is because the source packages are not entered in the RPM database. Only installed operating system software is listed in the RPM database. When you “install” a source package, only the source code is added to the system.

The following directories must be available for rpm and rpmbuild in /usr/src/packages (unless you specified custom settings in a file like /etc/rpmrc):

When you install a source package with YaST, all the necessary components are installed in /usr/src/packages: the sources and the adjustments in SOURCES and the relevant .spec file in SPECS.

Do not experiment with system components (glibc, rpm, sysvinit, etc.), because this endangers the stability of your system.

The following example uses the wget.src.rpm package. After installing the source package, you should have files similar to those in the following list:

/usr/src/packages/SOURCES/wget-1.11.4.tar.bz2
/usr/src/packages/SOURCES/wgetrc.patch
/usr/src/packages/SPECS/wget.spec

rpmbuild -bX /usr/src/packages/SPECS/wget.spec starts the compilation. X is a wild card for various stages of the build process (see the output of --help or the RPM documentation for details). The following is merely a brief explanation:

The binary RPM created can now be installed with rpm -i or, preferably, with rpm -U. Installation with rpm makes it appear in the RPM database.

The danger with many packages is that unwanted files are added to the running system during the build process. To prevent this use build, which creates a defined environment in which the package is built. To establish this chroot environment, the build script must be provided with a complete package tree. This tree can be made available on the hard disk, via NFS, or from DVD. Set the position with build --rpms directory. Unlike rpm, the build command looks for the .spec file in the source directory. To build wget (like in the above example) with the DVD mounted in the system under /media/dvd, use the following commands as root:

cd /usr/src/packages/SOURCES/
mv ../SPECS/wget.spec .
build --rpms /media/dvd/suse/ wget.spec

Subsequently, a minimum environment is established at /var/tmp/build-root. The package is built in this environment. Upon completion, the resulting packages are located in /var/tmp/build-root/usr/src/packages/RPMS.

The build script offers a number of additional options. For example, cause the script to prefer your own RPMs, omit the initialization of the build environment or limit the rpm command to one of the above-mentioned stages. Access additional information with build --help and by reading the build man page.

Midnight Commander (mc) can display the contents of RPM archives and copy parts of them. It represents archives as virtual file systems, offering all usual menu options of Midnight Commander. Display the HEADER with F3. View the archive structure with the cursor keys and Enter. Copy archive components with F5.

A full-featured package manager is available as a YaST module. For details, see Chapter 5, Installing or Removing Software.

If you use the KDE or GNOME desktop environment you can configure Auto Login for a certain user as well as Passwordless Login for all users. Auto login causes a user to become automatically logged in to the desktop environment on boot. This functionality can only be activated for one user at a time. Login without password allows all users to log in to the system after they have entered their username in the login manager.

	Security Risk
Enabling Auto Login or Passwordless Login on a machine that can be accessed by more than one person is a security risk. Without the need to authenticate, any user can gain access to your system and your data. If your system contains confidential data, do not use this functionality.

If you want to activate auto login or login without password, access these functions in the YaST User and Group Administration with Expert Options+Login Settings.

On any system with multiple users, it is a good idea to enforce at least basic password security policies. Users should change their passwords regularly and use strong passwords that cannot easily be exploited. For local users, proceed as follows:

To protect data in home directories against theft and hard disk removal, you can create encrypted home directories for users. These are encrypted with LUKS (Linux Unified Key Setup), which results in an image and an image key being generated for the user. The image key is protected with the user's login password. When the user logs into the system, the encrypted home directory is mounted and the contents are made available to the user.

	Fingerprint Reader Devices and Encrypted Home Directories
If you want to use a fingerprint reader device, you must not use encrypted home directories. Otherwise logging in will fail, because decrypting during login is not possible in combination with an active fingerprint reader device.

With YaST, you can create encrypted home directories for new or existing users. To encrypt or modify encrypted home directories of already existing users, you need to know the user's current login password. By default, all existing user data is copied to the new encrypted home directory, but it is not deleted from the unencrypted directory.

	Security Restrictions
Encrypting a user's home directory does not provide strong security from other users. If strong security is required, the system should not be physically shared.

Find background information about encrypted home directories and which actions to take for stronger security in Section “Using Encrypted Home Directories” (Chapter 10, Encrypting Partitions and Files, ↑Security Guide).

If your system includes a fingerprint reader you can use biometric authentication in addition to standard authentication via login and password. After registering their fingerprint, users can log into the system either by swiping a finger on the fingerprint reader or by typing in a password.

Fingerprints can be registered with YaST. Find detailed information about configuration and use of fingerprint authentication in Chapter 7, Using the Fingerprint Reader (↑Security Guide). For a list of supported devices, refer to http://www.freedesktop.org/wiki/Software/fprint/libfprint.

To prevent system capacities from being exhausted without notification, system administrators can set up quotas for users or groups. Quotas can be defined for one or more file systems and restrict the amount of disk space that can be used and the number of inodes (index nodes) that can be created there. Inodes are data structures on a file system that store basic information about a regular file, directory, or other file system object. They store all attributes of a file system object (like user and group ownership, read, write, or execute permissions), except file name and contents.

openSUSE allows usage of soft and hard quotas. Soft quotas usually define a warning level at which users are informed that they are nearing their limit, whereas hard quotas define the limit at which write requests are denied. Additionally, grace intervals can be defined that allow users or groups to temporarily violate their quotas by certain amounts.

openSUSE also ships command line tools like repquota or warnquota with which system administrators can control the disk usage or send e-mail notifications to users exceeding their quota. With quota_nld, administrators can also forward kernel messages about exceeded quotas to D-BUS. For more information, refer to the repquota, the warnquota and the quota_nld man page.