Language Selection

English French German Italian Portuguese Spanish

Using Your Linux Desktop

Filed under
Linux

Sample Chapter 1: Logging In

Linux provides two basic types of interface for you to use when working with your computer: GUI (graphical user interface) and CLI (command-line interface). An overview of the interface types is provided in Chapter 5. In this chapter, the most common type of interface, a GUI called a desktop, is discussed in detail. The CLI is discussed in detail in Chapter 7.

Linux can start without a desktop, but most users prefer to have Linux start with a desktop. The installation instructions provided in Chapter 4 result in a desktop opening at startup. A desktop interface functions as the top of your desk, supplying an empty working surface and a set of tools.

Different distributions provide different desktops, but most provide KDE (K Desktop Environment) and/or GNOME (Gnu Network Object Model Environment)-the Big Two of Linux desktops. The default desktop differs by distribution. For instance, Fedora defaults to GNOME, and Mandrake/SuSE defaults to KDE. However, you can change the default once you decide which desktop you prefer.

KDE and GNOME are open source software, each developed in a project of its own. New versions are released independently of Linux releases or the release of any specific Linux distribution. As a result, different distributions include different KDE and/or GNOME versions. In addition, KDE and GNOME are very configurable. Almost everything about them can be changed. Consequently, KDE and GNOME don't look exactly the same in different distributions or versions of distributions.

When using this book, remember that your KDE or GNOME may not look exactly like the book. Most of the figures in the book are Fedora Core 2 (KDE 3.2/GNOME 2.6) or Mandrake 10 (KDE 3.2/GNOME 2.4). Your version may be older or newer. Because your KDE and GNOME may not always look and behave exactly as shown in the book, it's best to consider the instructions in this chapter as suggestions, rather than an exact map. It provides clues to the most likely places to find configuration tools, but not necessarily a detailed route.

This chapter describes the contents of your desktop and how to use them. Then, when you are comfortable with the default appearance and behavior of your Linux, you find out how to change everything.

Logging In

To access your desktop, you must log in using a Linux account. When you power on your computer, the process goes as follows:

  1. The computer boots up.
  2. The computer prompts you to log in.
  3. You log in to an account, typing your password.
  4. The desktop displays.

After the computer boots (Step 1), you see a login screen. The login screens for Fedora Core, Mandrake, and SuSE are shown in Figure 6-1.

Notice that Mandrake and SuSE give you a choice of accounts. In this case, only one account (janet) is available. If more accounts were installed, they would also be on the login screen. Accounts are discussed in Chapter 8.

Select an account by clicking it. In SuSE, the account name appears in the Login field. Type the password in the Password field and click Go! to log in. In Mandrake, a second screen appears, as shown in Figure 6-2.

Full Article with screenshots and many other sample chapters. (Actually it looks to me as if the whole book is available there online.) <shrugs>

More in Tux Machines

Linux: To recurse or not

Linux and recursion are on very good speaking terms. In fact, a number of Linux command recurse without ever being asked while others have to be coaxed with just the right option. When is recursion most helpful and how can you use it to make your tasks easier? Let’s run through some useful examples and see. Read more

Today in Techrights

Android Leftovers

today's leftovers

  • MX Linux Review of MX-17 – For The Record
    MX Linux Review of MX-17. MX-17 is a cooperative venture between the antiX and former MEPIS Linux communities. It’s XFCE based, lightning fast, comes with both 32 and 64-bit CPU support…and the tools. Oh man, the tools available in this distro are both reminders of Mepis past and current tech found in modern distros.
  • Samsung Halts Android 8.0 Oreo Rollouts for Galaxy S8 Due to Unexpected Reboots
    Samsung stopped the distribution of the Android 8.0 Oreo operating system update for its Galaxy S8 and S8+ smartphones due to unexpected reboots reported by several users. SamMobile reported the other day that Samsung halted all Android 8.0 Oreo rollouts for its Galaxy S8/S8+ series of Android smartphones after approximately a week since the initial release. But only today Samsung published a statement to inform user why it stopped the rollouts, and the cause appears to be related to a limited number of cases of unexpected reboots after installing the update.
  • Xen Project Contributor Spotlight: Kevin Tian
    The Xen Project is comprised of a diverse set of member companies and contributors that are committed to the growth and success of the Xen Project Hypervisor. The Xen Project Hypervisor is a staple technology for server and cloud vendors, and is gaining traction in the embedded, security and automotive space. This blog series highlights the companies contributing to the changes and growth being made to the Xen Project and how the Xen Project technology bolsters their business.
  • Initial Intel Icelake Support Lands In Mesa OpenGL Driver, Vulkan Support Started
    A few days back I reported on Intel Icelake patches for the i965 Mesa driver in bringing up the OpenGL support now that several kernel patch series have been published for enabling these "Gen 11" graphics within the Direct Rendering Manager driver. This Icelake support has been quick to materialize even with Cannonlake hardware not yet being available.
  • LunarG's Vulkan Layer Factory Aims To Make Writing Vulkan Layers Easier
    Introduced as part of LunarG's recent Vulkan SDK update is the VLF, the Vulkan Layer Factory. The Vulkan Layer Factory aims to creating Vulkan layers easier by taking care of a lot of the boilerplate code for dealing with the initialization, etc. This framework also provides for "interceptor objects" for overriding functions pre/post API calls for Vulkan entry points of interest.