openSUSE 11.
Start-Up Copyright © 2006–2011 Novell, Inc. and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For Novell trademarks, see the Novell Trademark and Service Mark list http://www.
Contents About This Guide vii Part I Installation and Setup 1 1 3 Installation with YaST 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 1.11 1.12 1.13 1.14 1.15 2 Setting Up Hardware Components with YaST 2.1 2.2 2.3 2.4 3 Choosing the Installation Media . . . . . . . . . . . . . . . Choosing the Installation Method . . . . . . . . . . . . . . . The Installation Workflow . . . . . . . . . . . . . . . . . . System Start-Up for Installation . . . . . . . . . . . . . . . The Boot Screen . . . . . . . . . .
3.3 4 5 Keeping the System Up-to-date . . . . . . . . . . . . . . . 44 Accessing the Internet 51 4.1 4.2 51 53 Direct Internet Connection . . . . . . . . . . . . . . . . . Internet Connection Via Network . . . . . . . . . . . . . . Using NetworkManager 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 Use Cases for NetworkManager . . . . Enabling NetworkManager . . . . . . Configuring Network Connections . . . Using KNetworkManager . . . . . . . Using GNOME NetworkManager Applet . NetworkManager and VPN .
Part III Help and Troubleshooting 115 8 117 Help and Documentation 8.1 8.2 8.3 8.4 8.5 8.6 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Common Problems and Their Solutions 9.1 9.2 9.3 9.4 9.5 9.6 A Using the KDE Help Center . . . . . . . . . . Using GNOME Help . . . . . . . . . . . . . . Browsing Man and Info Pages From Your Desktop . Additional Help Resources . . . . . . . . . . . For More Information . . . . . . . . . . . . . Support for openSUSE . . . . . . . .
About This Guide This manual will see you through your initial contact with openSUSE®. Check out the various parts of this manual to learn how to install, use and enjoy your system. Installation and Setup Guides you through the installation process and the basic configuration of your system. Introduces YaST, the central tool for installation and configuration of your system. Learn how to set up or modify key components of your system and how to connect to the internet.
KDE User Guide (↑KDE User Guide) Introduces the KDE desktop of openSUSE. It guides you through using and configuring the desktop and helps you perform key tasks. It is intended mainly for users who want to make efficient use of KDE as their default desktop. GNOME User Guide (↑GNOME User Guide) Introduces the GNOME desktop of openSUSE. It guides you through using and configuring the desktop and helps you perform key tasks.
updates at http://www.novell.com/documentation where you can download PDF or HTML versions of the manuals for your product. 2 Feedback Several feedback channels are available: Bugs and Enhancement Requests To report bugs for a product component, or to submit enhancement requests, please use https://bugzilla.novell.com/. For documentation bugs, submit a bug against the component Documentation for the respective product. If you are new to Bugzilla, you might find the following articles helpful: • http://en.
4 About the Making of This Manual This book is written in Novdoc, a subset of DocBook (see http://www.docbook.org). The XML source files were validated by xmllint, processed by xsltproc, and converted into XSL-FO using a customized version of Norman Walsh's stylesheets. The final PDF is formatted through XEP from RenderX. The open source tools and the environment used to build this manual are available in the package susedoc that is shipped with openSUSE.
Part I.
1 Installation with YaST Install your openSUSE® system with YaST, the central tool for installation and configuration of your system. YaST guides you through the installation process and the basic configuration of your system. During the installation and configuration process, YaST analyzes both your current system settings and your hardware components and proposes installation settings based on this analysis.
Choose this medium option for a first look at openSUSE. The LiveCD version runs on your computer using RAM without touching your hard drive and no installation is needed. However, you can also install openSUSE from the running live system. There is no network connection required beyond the mere downloading of the medium. TIP: Booting the LiveCD from an USB Stick Live CD iso images can also be used as boot images for USB sticks.
desktop. It is not possible to update an existing system with a LiveCD, you can only perform a new installation (with automatic configuration). Installing from a Network Server Choose this option if you have an installation server available in your network or want to use an external server as the source of your installation data. This setup can be configured to boot from physical media (Floppy, CD/DVD, or hard disk) or configured to boot via network using PXE/BOOTP. Refer to Section 1.2.
TIP: Booting from DVD on UEFI machines ►amd64 em64t: DVD1 can be used as a boot medium for machines equipped with UEFI (Unified Extensible Firmware Interface). Refer to your vendor's documentation for specific information. If booting fails, try to enable CSM (Compatibility Support Module) in your firmware. ◄ 1.2.
as described below. When Microsoft Windows is booted again, openSUSE 11.3 Installer is automatically uninstalled. TIP: Installing openSUSE alongside Microsoft Windows openSUSE can easily be installed alongside Microsoft Windows. Carry out the installation as described below—an existing Windows installation will automatically be detected and a dual boot option will be installed.
Rescue System Starts a minimal Linux system without a graphical user interface. For more information, see Section 9.6.4.1, “Using the Rescue System” (page 151). This option is not available on LiveCDs. Check Installation Media This option is only available when you install from media created from downloaded ISOs. In this case it is recommended to check the integrity of the installation medium. This option starts the installation system before automatically checking the media.
[F2]Language Select the display language and a corresponding keyboard layout for the installation. The default language is English (US). [F3]Video Mode Select various graphical display modes for the installation. Select Text Mode if the graphical installation causes problems. [F4]Source Normally, the installation is performed from the inserted installation medium. Here, select other sources, like FTP or NFS servers.
TIP: Installation without a Mouse If the installer does not detect your mouse correctly, use [Tab] for navigation, arrow keys to scroll, and [Enter] to confirm a selection. Various buttons or selection fields contain a letter with an underscore. Use [Alt] + [Letter] to select a button or a selection directly instead of navigating there with the [Tab] button. 1.6 Welcome Start the installation of openSUSE by choosing your language.
played. This step is skipped when installing from a LiveCD, since this medium only supports a new installation with automatic configuration. New installation Select this option to start a new installation from scratch. Update Select this option to update an existing installation to a newer version. For more information about system updates, see Chapter 14, Upgrading the System and System Changes (↑Reference). Figure 1.
1.7.1 Add-On Products Add-on products can be installed either from a local source (CD, DVD, or directory) or from a network source (HTTP, FTP, NFS, CIFS,...). When installing from a network source, you need to configure the network first (unless you are performing a network installation— in this case the existing network configuration is used). Choose Yes, Run the Network Setup and proceed as described in Section 1.7.1.1, “Network Setup” (page 12).
the cursor at the rough direction of your region and left-click to zoom. Now choose your country or region by left-clicking. Right-click to return to the world map. Figure 1.4 Clock and Time Zone To set up the clock, choose whether the Hardware Clock is Set to UTC. If you run another operating system on your machine, such as Microsoft Windows, it is likely your system uses local time instead.
provide the usual integrated desktop functionality. In Minimal Server Selection (Text Mode), only console terminals are available. Figure 1.5 Desktop Selection 1.10 Suggested Partitioning Define a partition setup for openSUSE in this step. In most cases a reasonable scheme that can be accepted without change is proposed. If a hard disk containing only Windows FAT or NTFS partitions is selected as the installation target, YaST proposes to shrink one of these partitions.
Figure 1.6 Suggested Partitioning 1.10.1 Partitioning a Specific Disk If your machine contains more than one hard disk and you want to restrict the partitioning proposal to just one disk, choose Create Partition Setup and then select a specific disk from the list. If the chosen hard disk does not contain any partitions yet, the whole hard disk will be used for the proposal. Otherwise, you can choose which existing partition(s) to utilize.
2. Run scandisk. 3. Run defrag. After these preparations, restart the openSUSE installation. When you turn to the partitioning setup, proceed as before and select Shrink Windows Partition. After a quick check of the partition, the dialog for resizing the Windows partition opens. The bar graph shows how much disk space is currently occupied by Windows and how much space is still available. To change the proposed settings use the slider or the input fields to adjust the partition sizing. Figure 1.
1.11 Create New User Create a local user in this step. Administrating local users is a suitable option for stand-alone workstations. If setting up a client on a network with centralized user authentication, click Change and proceed with the Section 1.11.1, “Expert Settings” (page 18). After entering the first name and last name, either accept the proposal or specify a new Username that will be used to log in. Finally, enter a password for the user.
Use this Password for the System Administrator If checked, the same password you have entered for the user will be used for the system administrator root. This option is suitable for stand-alone workstations or machines in a home network that are administrated by a single user. When not checked, you are prompted for a system administrator password in the next step of the installation workflow (see Section 1.11.2, “Password for the System Administrator root” (page 19)).
LDAP Users are administered centrally on an LDAP server for all systems in the network. More information is available in Section “Configuring an LDAP Client with YaST” (Chapter 4, LDAP—A Directory Service, ↑Security Guide). NIS Users are administered centrally on an NIS server for all systems in the network. See Section “Configuring NIS Clients” (Chapter 3, Using NIS, ↑Security Guide) for more information. Windows Domain SMB authentication is often used in mixed Linux and Windows networks.
1.12 Installation Settings On the last step before the real installation takes place, you can alter installation settings suggested by YaST and also review the settings you made so far. To modify the suggestions, either click Change and select the category to change or click on one of the headlines. After configuring any of the items presented in these dialogs, you are always returned to the Installation Settings window, which is updated accordingly. Figure 1.
figuring the Boot Loader with YaST” (Chapter 17, The Boot Loader GRUB, ↑Reference). The boot method should only be changed by experienced users. 1.12.3 Software openSUSE contains a number of software patterns for various application purposes. Click Software to start the pattern selection and modify the installation scope according to your needs. Select your pattern from the list and see a pattern description in the right part of the window.
Choose secondary languages to be able to switch to one of these languages at any time without having to install additional packages. For more information, see Chapter 9, Changing Language and Country Settings with YaST (↑Reference). To change the keyboard layout, select Keyboard Layout. By default, the layout corresponds to the language chosen for installation. Select the keyboard layout from the list.
1.12.10 Firewall By default SuSEfirewall2 is enabled on all configured network interfaces. To globally disable the firewall for this computer, click on Disable. If the firewall is enabled, you may Open the SSH port in order to allow remote connections via secure shell. 1.13 Performing the Installation After configuring all installation settings, click Install in the Installation Settings window to start the installation. Some software may require a license confirmation.
1.14.1 Automatic System Configuration Having rebooted, the system starts the Automatic Configuration. This routine attempts to configure your network and Internet access and sets up your hardware. This process does not need any interaction. You can change the settings made by Automatic Configuration at any time on the installed system with YaST. Continue with Section 1.15, “Graphical Login” (page 27). 1.14.2 Manual System Configuration Having rebooted, the system starts the manual configuration.
General Network Settings Enable or disable the use of NetworkManager as described above. Also change the IPv6 support here. By default the IPv6 support is enabled. To disable it, click Disable IPv6. For more information about IPv6, see Section “IPv6—The Next Generation Internet” (Chapter 21, Basic Networking, ↑Reference). Firewall By default SuSEfirewall2 is enabled on all configured network interfaces. To globally disable the firewall for this computer, click on Disable.
prerequisite for the automatic addition of the default repositories and for updating online. If you have multiple network interfaces, verify that the desired card is used to connect to the Internet. If not, click Change Device. To start the test, select Yes, Test Connection to the Internet and click Next. In the following dialog, view the progress of the test and the results. Detailed information about the test process is available via View Logs.
1.14.2.5 Release Notes After completing the user authentication setup, YaST displays the release notes. Reading them is recommended, because they contain important up-to-date information which was not available when the manuals were printed. If you successfully tested the Internet connection, read the most recent version of the release notes, as fetched from openSUSE's servers. Use Miscellaneous > Release Notes in YaST or start the SUSE Help Center to view the release notes after installation. 1.14.2.
the GNOME User Guide (↑GNOME User Guide). These manuals can be accessed via the Help function in both KDE and GNOME.
2 Setting Up Hardware Components with YaST YaST allows you to configure hardware items at installation time as well as on an already-installed system. Configure audio hardware, printers or scanner support or learn which hardware components are connected to your computer by using the YaST Hardware Information module. TIP: Graphics card, monitor, mouse and keyboard settings Graphics card, monitor, mouse and keyboard can be configured with either KDE or GNOME tools. 2.
The dialog shows all sound cards that are already configured. If YaST cannot detect your sound card automatically, configure it manually as described in Procedure 2.1, “Configuring a New Sound Card” (page 30). For this, you need to know your sound card vendor and model. If in doubt, refer to your sound card documentation for the required information.
6 To remove a sound card configuration that you no longer need, select the respective entry and click Delete. 7 Click OK to save the changes and leave the YaST sound module. Procedure 2.2 Modifying Sound Card Configurations 1 To change the configuration of an individual sound card (for experts only!), select the sound card entry in the Sound Configuration dialog and click Edit. This takes you to the Sound Card Advanced Options where you can fine-tune a number of parameters.
It is also possible to share printers over the network. Further information about printing (general information, technical details, and troubleshooting) is available in Chapter 11, Printer Operation (↑Reference). In YaST, click Hardware > Printer to start the printer module. By default it opens in the Printer Configurations view, displaying a list of all printers that are available and configured. This is especially useful when having access to a lot of printers via the network.
2 Click Add in the Printer Configurations screen 3 If your printer is already listed under Specify the Connection, proceed with the next step. Otherwise, try to Detect More or start the Connection Wizard. 4 Enter the vendor name and the model name into the input box under Find and Assign a Driver and click Search for. 5 Choose the driver marked as recommended that best matches your printer.
4 Enter the full path to the PPD file into the input box under Make a Printer Description File Available or choose the file from a dialog box by clicking on Browse 5 Click OK to return to the Add New Printer Configuration screen. 6 In order to directly use this PPD file, proceed as described in Procedure 2.3, “Adding a New Local Printer” (page 32). Otherwise, click Cancel. 2.3.1.
Procedure 2.6 Printing via a Single CUPS server 1 Start the YaST printer module with Hardware > Printer 2 Launch the Print via Network screen from the left pane. 3 Check Do All Your Printing Directly via One Single CUPS Server and specify the name or IP address of the server. 4 Click Test Server to make sure you have chosen the correct name or IP address. 5 Click OK to return to the Printer Configurations screen. All printers available via the CUPS server are now listed. Procedure 2.
Procedure 2.8 Sharing Printers 1 Start the YaST printer module with Hardware > Printer 2 Launch the Share Printers screen from the left pane. 3 Select Allow Remote Access. For more detailed configuration, additional options are available: • Check For computers within the local network and enable browsing mode by also checking Publish printers by default within the local network. • Add the network interface to be used by the CUPS server.
6 Leave the configuration screen with OK. 2.4.1 Configuring an HP All-In-One Device An HP All-In-One device can be configured with YaST even if it is connected to the parallel port or is made available via the network. If you own a USB HP All-In-One device, start configuring as described in Procedure 2.9, “Configuring a USB or SCSI Scanner” (page 36). If it is detected properly and the Test succeeds, it is ready to use.
4 Leave with OK. The network scanner is now listed in the Scanner Configuration window and is ready to use.
3 Installing, Removing and Updating Software Change the software collection of your system using YaST. In YaST's software management tool search for software components you want to add or remove. YaST resolves all the dependencies for you. Keep your system up-to-date by managing software updates with openSUSE Updater. 3.1 Installing Software Software is available via RPM packages. Each package contains the program itself, the configuration files, and additional documentation.
On the other hand, some packages cannot co-exist with others on the system. In this case a list of packages that have automatically been chosen for deletion is presented. Accept them by clicking Continue. If your choice results in a dependency conflict that cannot be automatically solved, you need to manually solve these conflicts as described in Section “Checking Software Dependencies” (Chapter 3, Installing or Removing Software, ↑Reference).
2 From the View button in the upper left corner, select Patterns. Now you see various pattern sets listed in the left pane. 3 Click on a pattern name for a list of all packages included in the pattern. Choose one or more patterns for installation by clicking the checkbox on front of the pattern's name. 4 Click Accept to proceed. 5 Confirm the automatic changes that were made to resolve dependencies with Continue. Procedure 3.
3 Clicking on a pattern's name, for example on Technical Writing, opens the list of packages it contains in the right pane. To install the pattern, right-click on the pattern's name and choose Install. Add or deselect single packages in the right pane. 4 Click Apply to install the listed packages. 3.2 Removing Software If you want to remove software from the system, proceed as follows if you have KDE running (for GNOME see below): Procedure 3.
be aware that each change you make may lead to other conflicts. To discard all changes you made, click Cancel two times and then Abandon. With GNOME running, proceed as follows: 1 Start YaST and click Software > Software Management to start the package manager. 2 From the grouping menu in the upper left corner, select Groups. From the left pane choose All Packages from the top list and Installed from the bottom list. Search for single packages as described in Section 3.1, “Installing Software” (page 39).
3.3 Keeping the System Up-to-date openSUSE offers a continuous stream of software security patches for your product. The update applet informs you about the availability of patches and lets you easily install them with just a few clicks. 3.3.1 Using the KDE Updater Applet The openSUSE community also provides updates to newer versions of software packages. The updater applet optionally keeps a list of all programs installed on your system and informs you whenever newer versions are available.
Blue Circle with Question Mark No update repository is defined. When you click the updater applet in this state, you are asked if you want to check for updates. If you agree, the YaST Online Update Configuration module is started. 3.3.1.1 Installing Patches The Online Update Applet offers two modes for installing patches: the simple installation mode will automatically install all security and recommended patches, while the detailed mode lets you choose which patches to install. Procedure 3.
4 Click Install to start the patch installation. 5 In case you have started the patch installation for the first time, you will be asked to enter the root password in order to proceed. If you also check Remember authorization you will never be asked again to provide the password. 6 The updater performs the installation of the patches. You can monitor the installation status by hovering the mouse over the update applet icon. See the system tray for status messages and a progress meter. Figure 3.
availability of updates, click on the icon to launch the software installation window. Click on Details and then on the Upgrade tab to open the list with new software versions. Either select single packages by activating the box in front of an entry, or click Select All Packages. Install starts the installation of the selected software packages. You will be prompted for the root password. See the system tray for status messages and a progress meter.
Automatically Start Updater on Login Start the applet automatically when the user logs in. Active by default. Back-End Choose between different back-ends. The Package Kit Plugin is used by default. If you prefer the ZYpp Plugin, make sure to install the package kupdateapplet-zypp. Always Show Detailed View Activate this option when you prefer the detailed patch view that lists all patches available with short summaries rather than the simple view.
3.3.2.1 Installing Software Updates 1 Whenever software updates are available, the applet icon appears in the panel. 2 Click on the applet icon to start the Software Update applet. 3 It is safe to install all preselected software updates in one go. If you have special demands, you can modify the preselected set by changing the state of the check boxes in the Install column. Click Install Updates. Figure 3.
3.3.2.2 Configuring the Software Update Applet To configure the update applet, right-click the update icon in the panel and choose Preferences. The configuration dialog lets you modify the following settings: Check for Updates Choose how often a check for updates is performed: Hourly, Daily, Weekly, or Never. Automatically Install Configure whether patches are installed automatically or not (default). Automatic installation can be chosen for either security patches only or for all patches. Figure 3.
4 Accessing the Internet If you have chosen not to configure Internet access during the installation, you can perform this task at any time using YaST. How to configure your computer to access the Internet depends on your environment. If the computer you are installing is part of a network which already is connected to the Internet, the only thing to do is to link your machine to the network.
connecting). Regardless whether you choose an ISP from the list or add a custom provider, you need to enter at least your login and password. For configuration details, refer to Section “DSL” (Chapter 21, Basic Networking, ↑Reference). 4.1.2 Checklist ISDN In case your internal ISDN card is not detected automatically you will need to know the vendor and the name of the device. NOTE: ISDN Modem or Terminal Adapter If you are using an external ISDN modem or terminal adapter, refer to Section 4.1.
4.1.4 Checklist Cable Modem Accessing the Internet through the TV cable requires a cable modem. Such a modem is connected to the computer via ethernet cable. Therefore it is only necessary to configure your network card accordingly. For details, refer to Section “Cable Modem” (Chapter 21, Basic Networking, ↑Reference). 4.
5 Using NetworkManager NetworkManager is the ideal solution for laptops and other portable computers. It supports state-of-the-art encryption types and standards for network connections, including connections to 802.1X protected networks. 802.1X is the “IEEE Standard for Local and Metropolitan Area Networks—Port-Based Network Access Control”. With NetworkManager, you do not need to worry about configuring network interfaces and switching between wired or wireless networks when you are moving.
5 After choosing the method for managing network connections, set up your network card using automatic configuration via DHCP or a static IP address or configure your modem (for dial-up connections, use Network Devices > Modem). To configure an internal or USB ISDN modem, select Network Devices > ISDN. To configure an internal or USB DSL modem, select Network Devices > DSL.
Figure 5.1 GNOME Network Connections Dialog If you use KDE, open the main menu and click Configure Desktop. In the Personal Settings then select Network Settings on the General tab to open the network configuration dialog. Figure 5.2 KDE Network Configuration Dialog Alternatively, you can also start the configuration dialogs from the NetworkManager applet in the system tray. In KDE, left-click the icon and select Manage Connections. In GNOME, right-click the icon and select Edit Connections.
Procedure 5.1 Adding or Editing Connections When configuring network connections with NetworkManager, you can also define system connections that can be shared by all users. In contrast to user connections, system connections are made available right after NetworkManager is started—before any users log in. For more details about both types of connections, refer to Section 5.7.1, “User and System Connections” (page 66). Currently, the system connection option is not available in KNetworkManager.
Figure 5.3 KNetworkManager—Configured and Available Connections At the moment, Bluetooth connections cannot be configured with NetworkManager. 5.4 Using KNetworkManager The KDE front-end for NetworkManager is the KNetworkManager applet. If the network has been set up for NetworkManager control, the applet usually starts automatically with the desktop environment and is shown as an icon in the system tray. If your system tray does not show any network connection icon, the applet is probably not started.
1 Left-click the applet icon and select Wireless 802.11 (Create Network Connection). KNetworkManager shows a list of available visible wireless networks, including details about signal strength and security. 2 To connect to a visible network, select the network from the list and click Connect. If the network is encrypted, a dialog opens. Choose the type of Security the network uses and enter the appropriate credentials.
3 Set the encryption on the Wireless Security tab. IMPORTANT: Unprotected Wireless Networks Are a Security Risk If you set Security to None, everybody can connect to your network, reuse your connectivity and intercept your network connection. To restrict access to your access point and to secure your connection, use encryption. You can choose between various WEP and WPA–based encryptions.
Procedure 5.2 Configuring Multiple Tray Icons for KNetworkManager As KNetworkManager can keep multiple connections active at once, you might wish to be informed about the connection status for several connections at one glance. You can do so by using multiple NetworkManager icons in your system tray, each representing a different group of connection types (for example, one icon for wired connections, another icon for wireless connections). 1 In the configuration dialog, switch to the Tray Icon tab.
If your system tray does not show any network connection icon, the applet is probably not started. Press [Alt] + [F2] and enter nm-applet to start it manually. 5.5.1 Connecting to Wired Networks If your computer is connected to an existing network with a network cable, use the NetworkManager applet to choose the network connection. 1 Left-click the applet icon to show a menu with available networks. The currently used connection is selected in the menu.
5.5.3 Configuring Your Wireless Card as an Access Point If your wireless card supports access point mode, you can use NetworkManager for configuration. NOTE: Availability of Options Depending on your system set-up, you may not be allowed to configure connections. In a secured environment, some options might be locked or require root permission. Ask your system administrator for details. 1 Click the NetworkManager applet and select Create New Wireless Network.
• NetworkManager-novellvpn-kde4 or NetworkManager-novellvpn-gnome. NovellVPN support for KDE is not available yet, but is currently being worked on. OpenVPN To use this VPN technology, install • NetworkManager-openvpn and • NetworkManager-openvpn-kde4 or NetworkManager-openvpn-gnome. vpnc (Cisco) To use this VPN technology, install • NetworkManager-vpnc and • NetworkManager-vpnc-kde4 or NetworkManager-vpnc-gnome.
5.7.1 User and System Connections NetworkManager knows two types of connections: user and system connections. User connections are connections that become available to NetworkManager when the first user logs in. Any required credentials are asked from the user and when the user logs out, the connections are disconnected and removed from NetworkManager.
5.8 Frequently Asked Questions In the following, find some frequently asked questions about configuring special network options with NetworkManager. How to tie a connection to a specific device? By default, connections in NetworkManager are device type-specific: they apply to all physical devices with the same type. If more than one physical device per connection type is available (for example, your machine is equipped with two ethernet cards), you can tie a connection to a certain device.
down list, choose Shared. That will enable IP traffic forwarding and run a DHCP server on the device. Confirm your changes in NetworkManager. 2. As the DCHP server uses port 67, make sure that it is not blocked by the firewall: On the machine sharing the connections, start YaST and select Security and Users > Firewall. Switch to the Allowed Services category. If DCHP Server is not already shown as Allowed Service, select DCHP Server from Services to Allow and click Add. Confirm your changes in YaST.
ogy are installed. For more information, see Section 5.6, “NetworkManager and VPN” (page 64). No Network Connection Available If you have configured your network connection correctly and all other components for the network connection (router, etc.) are also up and running, it sometimes helps to restart the network interfaces on your computer. To do so, log in to a command line as root and run rcnetwork restart. 5.
Part II.
6 Basic Concepts If this is your first encounter with a Linux system you probably want to learn something about the basic concepts of Linux before getting started. The graphical user interfaces of Linux, Mac OS* and Windows* show rather similar desktop components, which makes it easy to move from one graphical environment to the next. However, if you take a look at the underlying system you will soon notice some differences.
For your daily work, you usually log in to your system as normal user. Performing some administrative tasks or running certain programs such as YaST requires root permissions. You can easily switch from your normal account to root and back to your normal user account after accomplishing the administrative task. How to do so in a shell is described in Section 7.4, “Becoming Root” (page 93). If you are working with a graphical user interface you are usually prompted to enter the root password when necessary.
6.2 The Linux File System All users, including the superuser, have their own home directories where all private data, like documents, bookmarks, or e-mail, are stored. System directories holding central configuration files or executable files can only be modified by the superuser. Read more about access permissions and how to modify them according to your needs in Section 7.5, “Modifying File Permissions” (page 94).
on a partition or a device unless it is mounted. But don't worry— most of the time you do not have to mount partitions or devices manually. During the installation of your system, you can define partitions to be mounted automatically when the system is started. Removable devices are usually also detected and mounted automatically by your system. The desktop environments such as KDE or GNOME will inform you about the appearance of a new device. Figure 6.
Figure 6.3 File and Folders in KDE File Manager Hidden Files Similar to Windows, Linux also distinguishes between “normal” files and hidden files which are often configuration files that you usually do not want to access or see as a normal user. In Linux, hidden files are indicated by a dot in front (for example, .hiddenfile).
6.2.2 The Directory Structure The following table provides a short overview of the most important higher-level directories that you find on a Linux system. Find more detailed information about the directories and important subdirectories in the following list. Table 6.1 Overview of a Standard Directory Tree Directory Contents / Root directory—the starting point of the directory tree. /bin Essential binary files, such as commands that are needed by both the system administrator and normal users.
Directory Contents /usr Secondary hierarchy with read-only data. /var Variable data such as log files. /windows Only available if you have both Microsoft Windows* and Linux installed on your system. Contains the Windows data. The following list provides more detailed information and gives some examples of which files and subdirectories can be found in the directories: /bin Contains the basic shell commands that may be used both by root and by other users.
/media Contains mount points for removable media, such as CD-ROMs, USB sticks and digital cameras (if they use USB). /media generally holds any type of drive except the hard drive of your system. As soon as your removable medium has been inserted or connected to the system and has been mounted, you can access it from here. /mnt This directory provides a mount point for a temporarily mounted file system. root may mount file systems here. /opt Reserved for the installation of third-party software.
/usr/local In this directory the system administrator can install local, distribution-independent extensions. /usr/share/doc Holds various documentation files and the release notes for your system. In the manual subdirectory find an online version of this manual. If more than one language is installed, this directory may contain versions of the manuals for different languages. Under packages find the documentation included in the software packages installed on your system.
6.3.1 Permissions for User, Group and Others Three permission sets are defined for each file object on a Linux system. These sets include the read, write, and execute permissions for each of three types of users—the owner, the group, and other users. You can view and change the access permissions of a file or folder in the file managers of your desktop or in a shell (see Section 7.5, “Modifying File Permissions” (page 94)). Figure 6.
Type User Permissions Group Permissions Permissions for Others - rw- r-- r-- The first column of the list consists of one leading character followed by nine characters grouped in three blocks. The leading character indicates the file type of the object: in this case, the hyphen (–) shows that kde-start.xml is a file. If you find the character d instead, this shows that the object is a directory, like local in Example 6.1, “Access Permissions For Files and Folders” (page 82).
Access Permission File Folder pletely from the directory as long as they do not have write permissions for the directory where the file is located. Execute (x) Users can execute the file. This permission is only relevant for files like programs or shell scripts, not for text files. If the operating system can execute the file directly, users do not need read permission to execute the file.
7 Shell Basics When working with Linux these days, you can communicate with the system almost without ever requiring a command line interpreter (the shell). After booting your Linux system, you are usually directed to a graphical user interface that guides you through the login process and the following interactions with the operating system. The graphical user interface in Linux (the X Window System or X11) is initially configured during installation.
word and press [Enter]. The prompt now changes and shows some useful information as in the following example: ❶ ❷ ❸ tux@linux:~> ❶ Your login. ❷ The hostname of your computer. ❸ Path to the current directory. Directly after login, the current directory usually is your home directory, indicated by the ~ symbol (tilde) . When you are logged in at a remote computer the information provided by the prompt always shows you which system you are currently working on.
Also keep this in mind for commands to delete objects. Before entering a command like rm (without any option) for removing a file, you should know if you really want to get rid of the object: it will be deleted irretrievably, without confirmation. 7.2.1 Using Commands without Options In Section 6.3.1, “Permissions for User, Group and Others” (page 82) you already got to know one of the most basic commands: ls, which used to list the contents of a directory. This command can be used with or without options.
❺ File size in bytes. ❻ Date and time of the last change. ❼ Name of the object. Usually, you can combine several options by prefixing only the first option with a hyphen and then write the others consecutively without a blank. For example, if you want to see all files in a directory in long listing format, you can combine the two options -l and -a (show all files) for the ls command. Executing ls -la shows also hidden files in the directory, indicated by a dot in front (for example, .hiddenfile).
(for example, info ls). You can browse an info page with a viewer directly in the shell and display the different sections, called “nodes.” Use [Space] to move forward and [<—] to move backwards. Within a node, you can also browse with [Page ↑] and [Page ↓] but only [Space] and [<—] will take you also to the previous or subsequent node. Like for the man pages, press [Q] to end the viewing mode. Note that man pages and info pages do not exist for all commands.
Relative Path Enter a path to the relevant file or directory by using the current directory as a starting point. This implies to give the levels you have to move up or down in the file system tree to reach the target directory of file, starting from the current directory. Paths contain filenames, directories or both, separated by slashes. Absolute paths always start with a slash. Relative paths do not have a slash at the beginning, but can have one or two dots.
7.3.1 Examples for Working with Files and Directories Suppose you want to copy a file located somewhere in your home directory to a subdirectory of /tmp that you need to create first. Procedure 7.1 Creating and Changing Directories From your home directory create a subdirectory in /tmp: 1 Enter mkdir /tmp/test mkdir stands for “make directory”. This command creates a new directory named test in the /tmp directory. In this case, you are using an absolute path to create the test directory.
2 To create a new, empty file named myfile.txt in the Documents directory, enter touch ~/Documents/myfile.txt Usually, the touch command updates the modification and access date for an existing file. If you use touch with a filename which does not exist in your target directory, it creates a new file. 3 Enter ls -l ~/Documents The new file should appear in the list of contents. 4 To copy the newly created file, enter cp ~/Documents/myfile.txt . Do not forget the dot at the end.
• to move a file or directory to a new location or • to do both in one step. 3 Coming to the conclusion that you do not need the file any longer, you can delete it by entering rm tuxfile.txt Bash deletes the file without any confirmation. 4 Move up one level with cd .. and check with ls -l test if the test directory is empty now. 5 If yes, you can remove the test directory by entering rmdir test 7.4 Becoming Root As you learned inSection 6.
7.4.2 Using sudo Alternatively, you can also use sudo (superuser “do”) to execute some tasks which normally are for roots only. With sudo, administrators can grant certain users root privileges for some commands. Depending on the system configuration, users can then run root commands by entering their normal password only. Due to a timestamp function, users are only granted a “ticket” for a restricted period of time after having entered their password. The ticket usually expires after a few minutes.
As root, you can also change the ownership of a file: with the command chown (change owner) you can transfer ownership to a new user. 7.5.1 Examples for Changing Access Permissions and Ownership The following example shows the output of an ls -l command in a shell. Example 7.
chmod o+w Procedure 7.5 kde_quick.xml gnome_quick.xml Changing Ownership Suppose you are tux and want to transfer the ownership of the file kde_quick.xml to an other user, named wilber. In this case, proceed as follows: 1 Enter the username and password for root. 2 Enter chown wilber kde_quick.xml 3 Check what happened with ls -l kde_quick.xml You should get the following output: -rw-r--r-- 1 wilber users 47896 2006-06-21 09:46 kde_quick.
Just type one or several letters from the command you are searching for. Each character you enter narrows down the search. The corresponding search result is shown on the right side of the colon whereas your input appears on the left of the colon. To accept a search result, press [Esc]. The prompt now changes to its normal appearance and shows the command you chose. You can now edit the command or directly execute it by pressing [Enter].
1 Press [↑] repeatedly until cd ~ appears. 2 Press [Enter] to execute the command and to switch to your home directory. By default, your home directory contains two subdirectories starting with the same letter, Documents and Desktop. 3 Enter cd D and press [→|]. Nothing happens since Bash cannot identify to which one of the subdirectories you want to change.
1d List the contents of your home directory.
NOTE: Using Wildcards in rm Commands Wildcards in a rm command can be very useful but also dangerous: you might delete more files from your directory than intended. To see which files would be affected by the rm, run your wildcard string with ls instead of rm first. 7.7 Editing Texts In order to edit files from the command line, you will need to know the vi editor. vi is a default editor which can be found on nearly every UNIX/Linux system.
3 Write some sentences. If you want to insert a new line, first press [Esc] to switch back to command mode. Press [O] to insert a new line and to switch to insert mode again. 4 In the insert mode, you can edit the text with the arrow keys and with [Del]. 5 To leave vi, press [Esc] to switch to command mode again. Then press [:] which takes you to the extended mode. The bottom line now shows a colon. 6 To leave vi and save your changes, type wq (w for write; q for quit) and press [Enter].
if you have installed KDE desktop or locate .gnome if you have installed GNOME desktop. You will see that locate displays all file names in the database that contain the string .kde or .gnome anywhere. To learn how to modify this behavior refer to the man page of locate. 2 To search your home directory for all occurrences of filenames that contain the file extension .txt, use find ~ -name '*.
takes you to the beginning, and [End] to the end of the document. To end the viewing mode, press [Q]. more Instead of less, you can also use the older program more. It has basically the same function—however, it is less convenient because it does not allow you to scroll backwards. Use [Space] to move forward. When you reach the end of the document, the viewer closes automatically. cat The cat command displays the contents of a file, printing the entire contents to the screen without interruption.
simply appends the output of the ls command to an already existing file named filelist.txt. If the file does not exist, it is created. 2 Redirections also works the other way round. Instead of using the standard input from the keyboard for a command, you can use a file as input: sort < filelist.txt This will force the sort command to get its input from the contents of filelist .txt. The result is shown on the screen.
If you have started several background processes (also named jobs) from the same shell, the jobs command gives you an overview of the jobs. It also shows the job number in brackets and their status: tux@linux:~> jobs [1] Running [2]- Running [3]+ Stopped okular book.opensuse.startup-xep.pdf & okular book.opensuse.reference-xep.pdf & man jobs To bring a job to the foreground again, enter fg job_number.
7.12 Important Linux Commands This section gives insight into the most important commands. There are many more commands than listed in this chapter. Along with the individual commands, parameters are listed and, where appropriate, a typical sample application is introduced. To learn more about the various commands, use the manual pages, accessed with man followed by the name of the command, for example, man ls. Man pages are displayed directly in the shell.
mv [options] source target Copies source to target then deletes the original source. -b Creates a backup copy of the source before moving -i Waits for confirmation, if necessary, before an existing targetfile is overwritten rm [options] files Removes the specified files from the file system. Directories are not removed by rm unless the option -r is used.
chmod [options] mode files Changes the access permissions. The mode parameter has three parts: group, access, and access type. group accepts the following characters: u User g Group o Others For access, grant access with + and deny it with -.
tar options archive files tar puts one or more files into an archive. Compression is optional. tar is a quite complex command with a number of options available.
place it in the background by appending an ampersand (&), so you can immediately continue working on the same command line (updatedb &). This command usually runs as a daily cron job (see cron.daily). find [options] With find, search for a file in a given directory. The first argument specifies the directory in which to start the search. The option -name must be followed by a search string, which may also include wild cards. Unlike locate, which uses a database, find scans the actual directory. 7.12.1.
diff [options] file1 file2 The diff command compares the contents of any two files. The output produced by the program lists all lines that do not match. This is frequently used by programmers who need only to send their program alterations and not the entire source code. -q Only reports whether the two files differ -u Produces a “unified” diff, which makes the output more readable 7.12.1.
all the mounted drives. If a directory is specified, the information is limited to the drive on which that directory is located. -h Shows the number of occupied blocks in gigabytes, megabytes, or kilobytes—in human-readable format -T Type of file system (ext2, nfs, etc.) du [options] [path] This command, when executed without any parameters, shows the total disk space occupied by files and subdirectories in the current directory.
ps [options] [process_ID] If run without any options, this command displays a table of all your own programs or processes—those you started. The options for this command are not preceded by hyphen. aux Displays a detailed list of all processes, independent of the owner kill [options] process_ID Unfortunately, sometimes a program cannot be terminated in the normal way.
ssh [options] [user@]hostname [command] SSH is actually an Internet protocol that enables you to work on remote hosts across a network. SSH is also the name of a Linux program that uses this protocol to enable operations on remote computers. 7.12.2.4 Miscellaneous passwd [options] [username] Users may change their own passwords at any time using this command. The administrator root can use the command to change the password of any user on the system.
Part III.
8 Help and Documentation openSUSE® comes with various sources of information and documentation, many of which are already integrated in your installed system: Desktop Help Centers The help centers of both the KDE desktop (KDE help center) and the GNOME desktop (Help) provide central access to the most important documentation resources on your system, in searchable form.
Figure 8.1 Main Window of the KDE Help Center The menu and the toolbar provide options for printing contents from the help center, searching the currently displayed page, and navigating and customizing the help center. The display field in the right part of the window always shows the currently selected contents, such as online manuals, search results, or Web pages. The navigation area in the left part of the window contains several tabs: Contents Presents a tree view of all available information sources.
2 To combine your search strings with operands, click Method and select the operand to use. 3 Choose an option from Max. Results to limit the number of hits to display. 4 To restrict your search to certain types of documentation, choose an option from Scope selection. With Default, a predefined selection of documents is searched. All includes all types of documents in the search. Custom lets you define which documents to include in your search. Just activate the documents you want in the list.
The menu and the toolbar provide options for navigating and customizing the help center, for searching and for printing contents from Help. To view a table of contents, click the home icon or press [Alt] + [Home]. The help topics are grouped into categories presented as links. Click one of the links to open a list of topics for that category. To search for an item, just enter the search string into the search field at the top of the window. 8.
8.4 Additional Help Resources In addition to the online versions of the openSUSE manuals installed under /usr/ share/doc, you can also access the product-specific manuals and documentation on the Web. For an overview of all documentation available for openSUSE check out your product-specific documentation Web page at http://www.novell.com/ documentation/. If you are searching for additional product-related information, you can also refer to the following Web sites: • openSUSE Wiki English [http://en.
8.5.2.1 HOWTOs HOWTOs are usually a short, informal, step-by-step guides to accomplishing specific tasks. HOWTOs can also be found in the package howto and are installed under /usr/ share/doc/howto. 8.5.2.2 Frequently Asked Questions FAQs (frequently asked questions) are a series of questions and answers. They originate from Usenet newsgroups where the purpose was to reduce continuous reposting of the same basic questions. 8.5.2.
8.5.5 Standards and Specifications There are various sources that provide information about standards or specifications. http://www.linux-foundation.org/en/LSB The Linux Foundation is an independent nonprofit organization that promotes the distribution of free and open source software. The organization endeavors to achieve this by defining distribution-independent standards. The maintenance of several standards, such as the important LSB (Linux Standard Base), is supervised by this organization. http://www.
http://www.din.de , http://www.din.com The Deutsches Institut für Normung (DIN) is a registered technical and scientific association. It was founded in 1917. According to DIN, the organization is “the institution responsible for standards in Germany and represents German interests in worldwide and European standards organizations.” The association brings together manufacturers, consumers, trade professionals, service companies, scientists and others who have an interest in the establishment of standards.
• Configuration of the graphical user interface (without the hardware acceleration feature of the graphics card). • Installation of the boot manager in the MBR of the first hard disk without modifying the BIOS mapping. • Setup of Internet access with a supported PCI ISDN card or external serial modem (not USB). Conversely, setup of DSL based on PPPoE with a supported NIC. • Basic configuration of a supported WLAN adapter. • Basic configuration of an ALSA-supported PCI sound card.
• United States and Canada: +1-404-5854-269 • Germany, Austria, Switzerland: Phone: +49 (0)911-8946-0303 • UK: +44-2030-025-943 • All other countries (English only): please see http://support.open-slx.com/ products/opensuse/contact.html For the most recent contact information, refer to http://support.open-slx.com/ products/opensuse/contact.html. 8.6.1.2 Important Notes 1. Free installation support is offered to customers with a valid and activated registration code.
a variety of problems. The SUSE Help Center on your desktop provides additional information about installed packages, the vital HOWTOs, and info pages. You can access the latest Support Database articles online at http://www.open-slx .com/usersupport or access the community Support Database at http://en.open-slx .org/SDB. The Support Database, one of the most frequently used databases in the Linux world, offers our customers a wealth of analysis and solution approaches.
9 Common Problems and Their Solutions This chapter describes a range of potential problems and their solutions. Even if your situation is not precisely listed here, there may be one similar enough to offer hints to the solution of your problem. 9.1 Finding and Gathering Information Linux reports things in a very detailed way.
Log File Description /var/log/samba/ Directory containing Samba server and client log messages. /var/log/SaX.log Hardware messages from the SaX display and KVM system. /var/log/warn All messages from the kernel and system log daemon with the “warning” level or higher. /var/log/wtmp Binary file containing user login records for the current machine session. View it with last. /var/log/Xorg.*.log Various start-up and runtime logs from the X Window system.
File Description /proc/meminfo Displays memory status. /proc/modules Displays the individual modules. /proc/mounts Displays devices currently mounted. /proc/partitions Shows the partitioning of all hard disks. /proc/version Displays the current version of Linux. Apart from the /proc file system, the Linux kernel exports information with the sysfs module, an in-memory filesystem. This module represents kernel objects, their attributes and relationships.
9.2 Installation Problems Installation problems are situations when a machine fails to install. It may fail entirely or it may not be able to start the graphical installer. This section highlights some of the typical problems you may run into, and offers possible solutions or workarounds for these kinds of situations. 9.2.1 Checking Media If you encounter any problems using the openSUSE installation media, check the integrity of your installation media.
When installing from a KDE or GNOME Live CD, you can also create a “Live USB stick” to boot from. Refer to http://en.opensuse.org/Live_USB_stick for detailed instructions. 9.2.4 Booting from Installation Media Fails One reason why a machine does not boot the installation media can be an incorrect boot sequence setting in BIOS. The BIOS boot sequence must have DVD drive set as the first entry for booting. Otherwise the machine would try to boot from another medium, typically the hard disk.
3 Exit the menu with [Esc]. 4 Open Configure Adapter Settings. Under Additional Options, select Boot Device Options and press [Enter]. 5 Enter the ID of the DVD drive and press [Enter] again. 6 Press [Esc] twice to return to the start screen of the SCSI BIOS. 7 Exit this screen and confirm with Yes to boot the computer. Regardless of what language and keyboard layout your final installation will be using, most BIOS configurations use the US keyboard layout as depicted in the following figure: Figure 9.
If this fails, proceed as above, but choose Safe Settings instead. This option disables ACPI and DMA support. Most hardware will boot with this option. If both of these options fail, use the boot options prompt to pass any additional parameters needed to support this type of hardware to the installation kernel. For more information about the parameters available as boot options, refer to the kernel documentation located in /usr/src/linux/Documentation/kernel-parameters.txt.
Once you have determined the right parameter combination, YaST automatically writes them to the boot loader configuration to make sure that the system boots properly next time. If unexplainable errors occur when the kernel is loaded or during the installation, select Memory Test in the boot menu to check the memory. If Memory Test returns an error, it is usually a hardware error. 9.2.
3 Select Installation then press [Enter] to start the installation . Instead of starting right into the graphical installation routine, the system continues to run in a text mode, then halts, displaying a message containing the IP address and port number at which the installer can be reached via a browser interface or a VNC viewer application.
Screen Resolutions Use the F keys to determine the screen resolution for installation. If you need to boot in text mode, choose [F3]. 9.3 Boot Problems Boot problems are situations when your system does not boot properly (does not boot to the expected runlevel and login screen). 9.3.1 Fails to Load the GRUB Boot Loader If the hardware is functioning properly, it is possible that the boot loader is corrupted and Linux cannot start on the machine. In this case, it is necessary to repair the boot loader.
changes here, disable future SuSEconfig changes by setting CHECK_INITTAB in /etc/sysconfig/suseconfig to no. If the runlevel is set to 5, your desktop or X Windows software is probably misconfigured or corrupted. Examine the log files at /var/log/Xorg.*.log for detailed messages from the X server as it attempted to start. If the desktop fails during start, it may log error messages to /var/log/messages. If these error messages hint at a configuration problem in the X server, try to fix these issues.
tives. For additional background information about PAM and the syntax of the configuration files involved, refer to Chapter 2, Authentication with PAM (↑Security Guide). • The home partition is encrypted. Find more information about this topic in Section 9.4.3, “Login to Encrypted Home Partition Fails” (page 142).
3 Try to log in from a console (using [Ctrl] + [Alt] + [F1]). If this is successful, the blame cannot be put on PAM, because it is possible to authenticate this user on this machine. Try to locate any problems with the X Window System or the desktop (GNOME or KDE). For more information, refer to Section 9.4.4, “Login Successful but GNOME Desktop Fails” (page 143) and Section 9.4.5, “Login Successful but KDE Desktop Fails” (page 144).
To locate the cause of the login failures with network authentication, proceed as follows: 1 Check whether the user remembered their password correctly before you start debugging the whole authentication mechanism. 2 Determine the directory server which the machine relies on for authentication and make sure that it is up and running and properly communicating with the other machines.
During the boot time, you have to enter the passphrase to unlock your encrypted partition. If you do not enter it, the boot process continues, leaving the partition locked. To unlock your encrypted partition, proceed as follows: 1 Switch to the text console with [Ctrl] + [Alt] + [F1]. 2 Become root. 3 Restart the unlocking process again with: /etc/init.d/boot.crypto restart 4 Enter your passphrase to unlock your encrypted partition.
If this causes the login problems, attempt to recover only the critical application data and reconfigure the remainder of the applications. 9.4.5 Login Successful but KDE Desktop Fails There are several reasons why a KDE desktop would not allow users to login. Corrupted cache data can cause login problems as well as corrupt KDE desktop configuration files. Cache data is used at desktop start-up to increase performance. If this data is corrupted, start-up is slowed down or fails entirely.
6 After the desktop has started successfully, copy the user's own configurations back into place: cp -a KDEDIR/share .kde/share Replace KDEDIR with the directory from Step 3 (page 144). IMPORTANT If the user's own adjustments caused the login to fail and continue to do so, repeat the procedure as described above, but do not copy the .kde/ share directory. 9.5 Network Problems Many problems of your system may be network-related, even though they do not seem to be at first.
NTP (Time Service) A malfunctioning or completely broken NTP service could affect Kerberos authentication and X server functionality. NFS (File Service) If any application needs data stored in an NFS mounted directory, it will not be able to start or function properly if this service was down or misconfigured. In the worst case scenario, a user's personal desktop configuration would not come up if their home directory containing the .gconf or .
from another machine, it is the server that is not running at all or not configured correctly. If ping fails with unknown host, the name service is not configured correctly or the hostname used was incorrect. For further checks on this matter, refer to Step 4b (page 147). If ping still fails, either your network card is not configured correctly or your network hardware is faulty.
zone information. For detailed information about DNS, refer to Chapter 23, The Domain Name System (↑Reference). If you have made sure that the DNS configuration of your host and the DNS server are correct, proceed with checking the configuration of your network and network device. 4c If your system cannot establish a connection to a network server and you have excluded name service problems from the list of possible culprits, check the configuration of your network card.
4 Collect any information about the state of NetworkManager in /var/log/ NetworkManager. For more information about NetworkManager, refer to Chapter 5, Using NetworkManager (page 55). 9.6 Data Problems Data problems are when the machine may or may not boot properly but, in either case, it is clear that there is data corruption on the system and that the system needs to be recovered.
1 As root, start YaST and select System > System Backup. 2 Create a backup profile holding all details needed for the backup, filename of the archive file, scope, and type of the backup: 2a Select Profile Management > Add. 2b Enter a name for the archive. 2c Enter the path to the location of the backup if you want to keep a local backup. For your backup to be archived on a network server (via NFS), enter the IP address or name of the server and the directory that should hold your archive.
6 Click OK to apply your settings and have the first backup start at the time specified. 9.6.3 Restoring a System Backup Use the YaST System Restoration module to restore the system configuration from a backup. Restore the entire backup or select specific components that were corrupted and need to be reset to their old state. 1 Start YaST > System > System Restoration. 2 Enter the location of the backup file.
• Check, modify, and reinstall the boot loader configuration. • Resize partitions using the parted command. Find more information about this tool at the GNU Parted website http://www.gnu.org/software/parted/parted .html. The rescue system can be loaded from various sources and locations. The simplest option is to boot the rescue system from the original installation medium: 1 Insert the installation medium into your DVD drive. 2 Reboot the system. 3 At the boot screen, press [F4] and choose DVD-ROM.
Checking and Manipulating Configuration Files As an example for a configuration that might be fixed using the rescue system, imagine you have a broken configuration file that prevents the system from booting properly. You can fix this using the rescue system. To manipulate a configuration file, proceed as follows: 1 Start the rescue system using one of the methods described above.
mount /dev/sda6 /mnt mount --bind /dev /mnt/dev 2 Now you can “change root” into the new environment: chroot /mnt 3 Then mount /proc and /sys: mount /proc mount /sys 4 Finally, mount the remaining partitions from the installed system: mount -a 5 Now you have access to the installed system. Before rebooting the system, unmount the partitions with umount -a and leave the “change root” environment with exit.
• /etc/grub.conf • /boot/grub/device.map • /boot/grub/menu.lst • /etc/sysconfig/bootloader 3 Reinstall the boot loader using the following command sequence: grub --batch < /etc/grub.
A GNU Licenses This appendix contains the GNU General Public License version 2 and the GNU Free Documentation License version 1.2. GNU General Public License Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works.
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12.
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. PREAMBLE The purpose of this License is to make a manual, textbook, or other functional and useful document “free” in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially.
has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.
COLLECTIONS OF DOCUMENTS You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.
Index Symbols A access permissions directory, 83 file, 83 file system, 81 AutoYaST cloning system, 27 B Bash commands, 86 completion, 97 features, 96 history, 96 jobs, 104 pipes, 103 processes, 104 redirection, 103 searching, 101 shortcut keys, 89 wild cards, 97 boot screen, 7 booting DVDs, from, 133 C cards sound, 29 case-sensitivity directory name, 76 file name, 76 cat, 103, 110 cd, 107 chgrp, 107 chmod, 108 chown, 107 clear, 114 commands, 102-103, 106-114 bg, 104 cat, 110 cd, 107 chgrp, 107 chmod, 94,
configuring printing, 31-36 local printers, 32 network printing, 34 sharing printers, 35 scanner, 36 HP All-In-One, 37 network, 37 sound cards, 29 cp, 106 D date, 112 device mount, 75 df, 111 diff, 111 directories /, 78 /bin, 78-79 /boot, 78-79 /dev, 78-79 /etc, 78-79 /home, 78-79 /lib, 78-79 /media, 78, 80 /mnt, 78, 80 /opt, 78, 80 /root, 78, 80 /sbin, 78, 80 /srv, 78, 80 /tmp, 78, 80 /usr, 79-80 /var, 79, 81 /windows, 79, 81 changing, 107 creating, 107 deleting, 107 paths, 89 structure, 78 directory acce
gzip, 108 H halt, 114 hardware information, 132 head, 102 help, 117 Help, 119 help center, 117 info pages, 88 KDE help center, 117 Linux documentation project (TLDP), 121 man pages, 88, 106 Novell/SUSE manuals, vii online documentation, 121 options, 88 specifications, 123 standards, 123 TLDP FAQs, 122 guides, 122 Usenet, 122 Wikipedia, 122 History Bash, 96 host, 113 I info pages, 88 installation, 3-28 add-on, 12 automatic configuration, 24 boot screen, 7 clock, 12 desktop selection, 13 domain name, 24 har
L less, 102, 110 license agreement, 10 Linux basic concepts, 73 case-sensitivity, 76 file extensions, 76 file system, 75 hidden files, 77 multiuser system, 73 ln, 107 locate, 109 ls, 86-87, 106 options, 87 M man pages, 88, 106 memory test, 8 mkdir, 107 more, 103 mount, 111 device, 75 drive, 75 partition, 75 removable media, 75 mv, 107 N NetworkManager, 55 configuring, 56 enabling, 55 GNOME NetworkManager applet, 62 KNetworkManager, 59 security, 65 troubleshooting, 68 VPN, 64 Novell/SUSE manuals, vii O op
shell basics, 85 jobs, 104 pipes, 103 processes, 104 prompt, 86 redirection, 103 root, 93 starting, 85 shells commands, 106-114 sound configuring in YaST, 29 fonts, 31 MIDI, 31 ssh, 114 su, 114 system rebooting, 114 rescuing, 151 shutdown, 114 T tail, 102 tar, 109 TLDP, 121 HOWTOs, 122 top, 112 U umount, 111 updatedb, 109 US Keyboard Layout, 134 users concept, 73 groups, 74 roles, 73 root, 73 superuser, 73 system administrator, 73 V vi, 100 VPN, 64 W Wild Cards Bash, 97 wild cards, 109 Y YaST add-on, 1
