Showing posts with label SUSE Linux. Show all posts
Showing posts with label SUSE Linux. Show all posts

Tuesday, September 16, 2008

SUSE Linux Family Products - Personal category

Novell divides its SUSE Linux products into Enterprise and Personal. This is essentially the distinction between the versions that are sold with a paid-for software maintenance system and those that are not. The Personal category now consists of just one product, SUSE Linux Professional. (In the past there was a cut-down version of SUSE Linux Professional known as SUSE Linux Personal; with the release of 9.3 this product was dropped. Do not confuse Novell’s customer category Personal with SUSE’s former product SUSE Linux Personal.)

SUSE Linux Professional
SUSE Linux Professional now contains versions for both the x86 (Intel-compatible PC 32-bit) and x86-64 (Athlon 64, Opteron, and Intel EM64T) platforms. It consists of five CDs and two double-layer DVDs. The five CDs form is an installation set for x86 machines. One of the DVDs is an installation DVD for both x86 and x86-64; the other DVD provides the source packages. The Professional version contains a wide range of software, including desktop and server software and development tools. It actually contains considerably more packages than the Enterprise Server versions but should be regarded as essentially an unsupported version, but limited installation support is included in the price of the boxed set. A new version of SUSE Linux Professional appears twice a year.

A Live DVD version (it’s been a DVD since version 9.2; previously this was a Live CD) is released with each version. This is available by FTP and can be burned to disk. This version cannot be installed, but booting a PC from this DVD provides a live Linux system that can be used to evaluate SUSE Linux without installing it or, if you want, as a way of carrying a Linux system around with you (perhaps with a USB stick to hold your files).

Traditionally SUSE did not provide ISO images of the distribution for download. This changed in the summer of 2005 when the full ISO images for version 9.3 were provided in this way. The Professional version has always been made available in an FTP version that allows for network installation, either directly from the FTP site or using a local mirror.

Recently, SUSE has also begun to offer a DVD ISO image (by FTP) of a cut-down installable version of the Professional distribution. This should be thought of as an evaluation edition, or as a replacement for the old Personal edition. This version is made available rather later in the product cycle than the FTP version and is known as the FTP DVD version.

openSUSE
Although the software concerned was almost all open source and freely distributable, the development of SUSE Linux was traditionally a closed process. Beta testing was done internally by the company with the help of volunteers from partner companies and the members of the public who carried out the testing under non-disclosure agreements.

When the first beta version of 10.0 was ready in August 2005, the beta testing process and the development of SUSE was opened up with the start of the openSUSE project. This is intended to create a community around the development of SUSE Linux and make the cutting-edge version of SUSE an entirely free one. In some ways the concept is similar to the Fedora project, which plays a similar role in the development of Red Hat; however, openSUSE aims to draw in a wider genuine participation by outside users and developers and has an interest in desktop usability and the needs of end users.

Future versions of SUSE Linux (at least in the short term) will be available both from openSUSE and as boxed versions that will include the traditional manuals and additional non-free software (such as Sun Java, Adobe Acrobat Reader, proprietary drivers of certain kinds, and so on).

Source of Information : SUSE Linux 10 Bible

Friday, August 29, 2008

Choosing a SUSE Linux Desktop Environment: KDE and GNOME

With Windows and the Macintosh, the desktop is just that—the desktop. Linux is all about choices, and so is X, KDE or GNOME.

One of the cool things is that you can remain indecisive your whole life: You can choose what desktop to load every time you log in. Of course, you don't have to choose that often either; SUSE Linux will load whatever desktop you loaded last time by default (and the initial default, assuming you installed it, is KDE).

When you first install SUSE Linux, YaST will recommend installing just the KDE desktop. You can choose to install GNOME instead, or install both if you have enough disk space.

With very few exceptions, all software designed for one desktop will happily run on the other, and will even show up in the other's Start menu. A trivial example is that SUSE installs identical default wallpaper for both desktops. You might find that one application designed for GNOME runs a little slower on KDE (or vice versa), but these types of issues are rarely catastrophic. All the Linux products not designed with either desktop (like OpenOffice.org and the Mozilla family) will also run beautifully in both.

Another key similarity is the capability to display multiple virtual desktops. If you regularly run one of those other operating systems and if you're a busy person, the desktop can get awfully crowded with a web browser, email client, word processor, and project manager all up at the same time. You can wind up Alt+Tabbing between apps, resizing and minimizing windows, or heavily working the taskbar to keep up. Wouldn't it be nice to have each application in its own desktop, away from the others? By default, GNOME and KDE offer you two virtual desktops (GNOME calls them workspaces). You can have up to 16 in KDE and 36 in GNOME. You can switch between them by pressing the Ctrl key along with the F key corresponding to the desktop number (that is, to switch to Desktop 2, press Ctrl+F2; for Desktop 3, press Ctrl+F3, and so on). For the incurable customizers, you can use descriptive names for each desktop, and even have different wallpaper on each one! You can have some applications (such as your schedule or time tracker) appear on all desktops, and choose whether you want to see the applications on other desktops in the taskbar. The taskbar will always show you your desktop lineup, with representations of the windows.

KDE is older, more stable, and has more applications designed for it. Its technological underpinnings come from the commercial Qt libraries from Trolltech, and for a long time Qt's licensing scheme was not open source.

GNOME is the relative newcomer and has only recently become a stable system. Its technological underpinnings come from the first Linux killer app: The GNU Image Manipulation Program The GIMP. It began as an open-source rebellion, but has the support of many leading Linux-oriented corporations.

GNOME was the first desktop project to put usability at the top of its concerns, producing a truly admirable Human Interface Guidelines (HIG) document that has been a model for later efforts (including KDE's forthcoming HIG project). It has ambitions beyond the desktop as well. Many of its most partisan developers believe it provides a model framework for all software development.

One more common function for both desktop environments is a very handy application launcher. Press Alt+F2 to bring up a dialog box. Enter the name of an application to launch it. If you enter a URL, the default browser (Konqueror in KDE, Epiphany in GNOME) opens on that site. This way, you save time browsing through menus or opening new shells.


KDE: The K Desktop Environment
The KDE project began in 1996 and has been the default desktop environment for SUSE Linux for nearly all that time. SUSE Linux 9.2 includes KDE 3.3. SUSE Linux also uses the KDE Display Manager to provide a graphical login screen after it has booted.

When you first log in to KDE, it will take a few seconds to load, but when it's finished you will see the basic elements of the desktop. Windows users should feel pretty comfortable with this opening experience—a few icons on the desktop, a taskbar (called the Kicker in KDE parlance) along the bottom, with assorted applications ready for quick access and a clock in the right corner (optionally configured to show the seconds passing by).

By default, KDE loads any applications that were running when your last session ended, so you can pick up where you left off. The SUSE icon in the left corner of the Kicker opens the application menus. To its right, the icons on the left side give you access to your home directory (via the Konqueror file manager), the Konsole Xterminal shell, the SUSE Help Center, the Konqueror web browser, and the Kontact personal information manager (the Outlook-style combined email, address book, and calendar program).

You will notice that KDE developers have a fetish for naming their programs with a K in front. This can be kreative, or just a little too kute, but it is a handy way of identifying what applications are K-specific. The Kicker panel is highly customizable; right-click anywhere to add or remove icons from the panel. The Configure Panel screen also lets you put the panel on a different side of the screen and set several other options.

In the right corner of the Kicker, next to the clock, are more application icons that always run. Mouse over each to see what they are. The smaller SUSE icon is the SUSEWatcher application, which checks the YaST Online Update (YOU) servers regularly to see if updates are available. These fix security problems and occasionally give you new versions of installed applications. Watch for an exclamation mark on this icon to get new updates. The Klipper clipboard utility offers much more than its Windows counterpart. Among other things, Klipper stores your last seven cut/copy actions by default, so you can paste several items in sequence if you choose. Klipper will remember your clipboard actions over sessions, too.

So many applications have been written for KDE that the YaST initial installation menu separates out some from the default KDE installation. It's all there if you want it, though.


GNOME: The GNU Network Object Model Environment
When you open GNOME for the first time, you may notice two differences between it and KDE: The look is a lot less cluttered, and the taskbar is at the top of the screen. You might even miss it the first time you look.

The GNOME panels are highly configurable with a curious collection of applications that you have much more control over than in KDE. Displaying many of the same characteristics and applications by default as KDE, the whole look is a bit cleaner with the much smaller icons.

The Programs menu was built for SUSE (indicated by the Novell icon attached to it) and is identical to the default Kicker menu in KDE, but there is a separate menu for quick access to System tools, including YaST, the file finder, and the logout button. The left side default applications include the Epiphany web browser, the Evolution groupware/personal information manager tool, and OpenOffice.org Writer, along with SUSEWatcher and SUSEPlugger. On the right, in addition to the clock, is the volume control and the list of all open applications.

In the bottom panel is your task/workspace switcher (right-click it to change the number of workspaces/desktops) and a window hiding tool to show just the desktop. Active applications and documents also appear in the bottom panel.

To add an icon to either panel, right-click exactly in the spot where you want the item to appear and choose Add to Panel. You can then select your item from the menu. Among the choices is a weather report with the current temperature and conditions for many global cities. Select your own location—or the place you want to be.

Source of Information : SUSE Linux 10 Unleashed

Thursday, August 28, 2008

Understanding SUSE Linux X Window System

The X Window System represents two primary concepts. The X Window System was created to keep the UNIX kernel and GUI code separate. It was also designed for distributed processing based on the client/server model. That is, with X you don't need to have a computer with massive amounts of hard drive space and RAM to run graphical applications. A thin client with a connection to an X server is all you need. Nonetheless, if you have the aforementioned massive hard drive and hundreds of megabytes of RAM, you can host both the X server and many clients on your own machine.

The X server's primary job is to create and manage windows, dialog boxes, buttons, and other graphical elements on a screen. That screen can be located practically anywhere in the world, and perhaps even on a laptop on the International Space Station. X is extremely portable, too. After you have configured X the way you (or your system administrators) want it, you can take that configuration file with you and copy it into any other X-capable machine and it will run the same way.

Dozens of applications have been developed to manage windows for X, and hundreds of X client programs exist to help users work in the graphical environment X provides. It all begins, however, with the fundamental question: What do you want your window decorations to look like?

Configuring X in SUSE Linux
SaX (also referred to as SaX) is the X configuration tool for SUSE Linux. It runs for the first time during the initial SUSE Linux installation, where it identifies your graphics card, installs the graphics drivers, and sets up X to its default configuration. The settings are stored in the /etc/X11/XF86Config file. You can edit this file manually, but that would be unnecessary risky behavior.

To open SaX after the initial installation, go to YaST, Hardware, Graphics Card and Monitor. A second window will open with your initial monitor and card listed, along with the resolution and whether the card supports 3D acceleration. Click Change to open SaX and configure X.

When you open SaX, you can see that it manages much more than your desktop settings. The Multihead section will configure a multiple monitor setup; Input Devices include keyboard, mouse, touchscreen, and graphics tablet; and Access Control covers Virtual Network Client (VNC) access and XAccess, a tool for controlling your mouse with the keypad (especially useful for people who can't see the screen). SaX usually does a terrific job of identifying your video card and setting up the X environment. It can make mistakes, but before you hand edit XF86Config, try choosing the Reprobe button in SaX. With the wrong Monitor Frequency settings, it is possible (if quite rare) to blow out your monitor.

If SaX has incorrectly identified either your monitor or graphics card, click the appropriate link and then click Properties. You will get a list of manufacturers and models to select from. Select the correct one; if you have a Linux driver disk for the item, click the Manufacturer's Disk button to install the new drivers. You can read and make changes to the frequency range and other settings in the Frequencies and Expert tabs, but don't do this unless you are absolutely sure you know what you're doing. Click OK and Finish to confirm your choices. As you make changes in each SaX component, be aware that nothing is written into the configuration file until you click Finalize and test the new setup.

There's not much to do in the Color and Resolution section. SaX detects the maximum color depth and all the resolutions your card will support and sets both defaults to the highest possible. Unless you have a fairly ancient machine, the color depth will be set at 16-bit True Color. This is the only thing you can change.

Change the position if the desktop is large enough in width and height, but you are seeing empty space on one side. Change the size if you're seeing empty space on both sides. Keep pushing the appropriate arrow buttons until it looks right; then click Save.
When you're finished changing settings, click Finalize on the main SaX screen. You'll be asked to test the new configuration, which is always a good idea. If everything looks good, click Save; if the desktop image fails, click Ctrl+Alt+Esc to kill the X server and review your selections.

In most cases, you'll be using a display manager to log in and start X, but there may come a time when something breaks and you can't get into the display manager. Don't panic! You may still be able to get into X.

If this happens at boot, you will get a text-based login prompt. Log in as user, and you should be sitting in your home directory (type pwd to make sure). Look for the .xinitrc file: ls -a .xinitrc.

SUSE Linux puts a default file in Home called .xinitrc.template. Make a copy of this file to activate it:cp .xinitrc.template .xinitrc

Now, type the magic word: startx

This should get you in and may help you solve the original problem.

Source of Information : SUSE Linux 10 Unleashed

Wednesday, August 20, 2008

How SUSU Linux Loading the Kernel

When GRUB hands over the process to the SUSE Linux kernel, it leaves the scene. The kernel now takes charge, putting up the message Uncompressing Linux...; it is present and available to you until you shut down the system. While the kernel boots, SUSE Linux puts up a nice blue wallpaper to hide all the boring text that scrolls by as the kernel initializes first your peripheral hardware, then the hard drive and attending file systems, followed by the serial ports. Press the Esc key to watch the boot process unfold.

As a user, or even as an administrator, you don't have much direct interaction with the Linux kernel. You run applications, which occasionally interact with the kernel to get things done. In the kernel's view of things, an application is simply a process, one of many it deals with. The father of all processes, which the kernel loads soon after the kernel itself loads, is called init, located in the /sbin directory. The rest of the boot process (and later, the shutdown process) is really handled by init, not the kernel. All other processes are started by init or one of its child processes. Init is centrally configured by the /etc/inittab file.

After activating the serial ports, the kernel runs a series of boot scripts, located at /etc/rc.d/boot.d, which activates (and, if required, mounts) still more devices and local file systems.

Then boot.clock sets up the system clock, ldconfig identifies the current time zone, and local networking interfaces are turned on via boot.sysctrl, boot.localnet (for the loopback interface), and boot.isapnp.

Finally, the kernel's System Boot Control declares

The system has been set up and runs /etc/init.d/boot.local. This program invokes the appropriate runlevel for the system. There is much more on runlevels in the next section, but a standard networked desktop will launch Runlevel 5 as it hits the home stretch of the boot process.

At Runlevel 5, networking services are started and various other services and the system logs come online. The sound driver, keyboard maps, CUPS printer interfaces, mail transfer agent, and xinetd Internet services come next.

Finally, the kernel starts the X Window System and the display manager (KDM by default) that allows the user to log in. Logging in loads the desired desktop, and you're done.

To closely examine your most recent boot process, open /var/log/boot.msg in a text editor, or open the YaST View Startup Log module from the Misc page.

Source of Information : SUSE Linux 10 Unleashed

SUSE Linux GRUB Versus LILO

You may not realize it unless you are dual booting multiple operating systems, but after your BIOS starts firing up the fan, the microprocessor chip, and the power supply, a boot manager, or bootloader, takes over the process until the kernel starts up.

Linux supports a variety of open-source and proprietary boot managers, but you can install only two with YaST: the Grand Unified Bootloader (GRUB) and the Linux Loader (LILO). GRUB has been the default bootloader for SUSE Linux since v8.2, but LILO still runs quite a few systems, and you may want to use it instead.

LILO succeeded load in as the primary Linux bootloader and seems to be in the long process of being superseded by GRUB. LILO carries out its single task, booting to a file system, well. It is not quite as flexible nor as configurable as GRUB. Nonetheless, it is still the default bootloader for systems in which the Root partition is installed on CPU-dependent RAID controllers (such as many Promise or Highpoint controllers), Software RAID, or Logical Volume (LVM) managed disk.

The chief difference between the two bootloaders is in how they find and load file systems. LILO looks for a file system based on where the partition table says it is. GRUB can read and identify several file systems (ext2, ext3, ReiserFS, JFS, XFS, Minix, and DOS).

In YaST, the Boot Loader Configuration module is on the System page. You can set LILO as the default if you want and set many other options in this screen. If you prefer, you can edit the file directly by clicking Edit Configuration Files.

By default, GRUB displays a menu, allowing you to boot SUSE Linux from the hard drive, from a floppy drive, or into fail-safe mode. Fail-safe mode loads a kernel version with a set of parameters that makes it possible to boot with some hardware problems. If there's another operating system on your computer, GRUB will list this on your boot menu as well. After 8 seconds, GRUB will boot the first item on the menu; that is, SUSE Linux. At the bottom of the GRUB menu, you can specify options for the kernel, if you are so inclined.

You can see how each process builds on the previous one, allowing different operating systems to work on the same hardware. The GRUB menu you see is controlled by the GRUB configuration file, which is located at /boot/grub/menu.lst.

The first portion of menu.lst defines options for the display of the GRUB menu, such as the color scheme of the menu, the default menu option, and the number of seconds (timeout) before GRUB runs the default menu option.

Following the display options are a list of items that will be displayed in the GRUB menu. Each menu item begins with "title." This particular GRUB menu will display three items:
• SUSE LINUX 10.0
• Floppy
• Failsafe—SUSE LINUX 10.0

The remaining lines tell GRUB where to find the operating system files needed to run Linux. These include the following:
• root: This command sets the current root device to the specified device.
• kernel: This command loads the primary boot image from the boot image file.
• initrd: This command loads an initial ramdisk for the boot image.

To configure how GRUB boots your system, you can either manually edit menu.lst with a text editor, or you can use the YaST System, Boot Loader module. In addition to manually editing the menu.lst file and using YaST, you can also use the GRUB shell to configure how your system boots. Simply enter grub at the shell prompt. To learn how to manipulate GRUB from the shell, see the grub man page.

Source of Information : SUSE Linux 10 Unleashed

Saturday, August 2, 2008

SUSE Linux History

SUSE is the oldest existing commercial distribution of Linux. The company was founded in 1992 near Nuremberg in Germany. The first release of a Linux distribution by SUSE was early in 1994.

SUSE is a German acronym for Software und System Entwicklung or Software and System Development (not a terribly original or gripping name for a software company). However, the full name is never used; the company has been known as SUSE since the earliest days. More accurately, the company has been known as S.u.S.E., then as SuSE, and now SUSE as the marketing people gradually got to work on the corporate image of the company.

The company was founded on September 2, 1992. The founders were Roland Dyroff, Thomas Fehr, Burchard Steinbild, and Hubert Mantel, all in their mid-twenties at the time. Three of the founders were still at University studying mathematics: Thomas Fehr had already graduated and was working as a software engineer. The original intention was that the company would do consulting work and software development for clients; according to Hubert Mantel’s account, this did not work out very well as work was in short supply, and after a while the group had the idea of distributing Linux. Initially the company distributed a version of Linux called SLS (Soft Landing Systems). Later they switched to Slackware, producing a German-language version in cooperation with Slackware’s founder, Patrick Volkerding.

According to the recollections of Bodo Bauer (one of the very earliest SUSE employees), the SUSE people decided that rather than constantly fixing bugs in Slackware before shipping their translated and enhanced version, it would be better to produce their own distribution. They also felt the lack of a good installation and configuration tool in Slackware. The result was that SUSE took Florian LaRoche’s Jurix distribution as a starting point and began to develop YaST. (Florian also joined the SUSE team.) The first true SUSE distribution was released in May 1996 and was numbered 4.2 (an intentional reference to the use of the number 42 in The Hitchhiker’s Guide to the Galaxy by Douglas Adams).

At the time that early versions of Red Hat (and Red Hat clones) were ubiquitous in the United States, SUSE Linux gained popularity in Europe. SUSE became a worldwide
company with the establishment of offices in the United States (1997) and in the United Kingdom (1999).

SUSE never attempted an IPO, although there were rumors that this would happen at one stage. Instead, the company went through a number of rounds of funding from venture capitalist and industry sources. Over-optimism and too rapid an expansion led to a point in 2001 when the company was forced to downsize significantly to survive. After that time, stricter financial discipline, the release of the enterprise versions, and the growing uptake of Linux by business put the company on a sound footing. With the takeover by Novell in 2003, the investors recouped their investment, while the market’s approval became very clear in the dramatic and sustained rise in Novell’s stock following the announcement.

Originally SUSE provided one product (simply known as S.u.S.E. Linux), which was released about three times a year and was available for the x86 platform only. The current SUSE Professional is the direct descendant of this, and the current version number of 10.0 is one of a series that goes back to the original 4.2. In 2000, the SUSE offering was split into Professional and Personal versions, and versions for other hardware platforms (Alpha, Sparc, and PPC) were released.

The following year, SUSE released the Enterprise Server 7 version, and in due course, versions of Enterprise Server for IA64 (Itanium), PPC (intended for the IBM iSeries and pSeries), S/390, and zSeries were released. SUSE developed powerful tools to aid in the process of porting Linux to other platforms, and there was close collaboration with IBM in the production of versions for the PPC-based iSeries and pSeries and for the S/390 and zSeries mainframes. SUSE also worked with AMD on the development of a version for the Hammer chip (now known as the Opteron and Athlon 64).

The story goes that an entire distribution for this architecture was completed and tested using emulation before AMD had any hardware to offer; when the first machine arrived at SUSE from AMD, the installation CD booted and installed flawlessly. SUSE uses a system known as AutoBuild that takes the same source code for all packages and builds the distribution for all platforms from it. This ensures a high degree of compatibility between versions on different platforms and is one of the key advantages of the SUSE Enterprise Server.

SUSE also released a series of mail server products leading up to the SUSE Linux OpenExchange Server 4, a mail and groupware server allowing integration with popular desktop clients, including Outlook and, hence, becoming a competitor to Microsoft Exchange Server. OpenExchange was developed jointly by SUSE and Netline, who wrote the groupware element. This has now been released as a separate product under the GPL, and can be run on other Linux versions as well as SUSE. Enterprise Server 7 was succeeded by Enterprise Server 8 (available on x86, IA64, AMD64, iSeries, pSeries, and zSeries) in November 2002.

Prior to the release of Enterprise Server 8 (in November 2002), the UnitedLinux consortium was established, with SUSE, Connectiva, Turbolinux, and SCO as members. UnitedLinux was an agreed core, developed by SUSE for enterprise distributions to be issued by the other vendors in the consortium. Following the defection of SCO from the Linux community and its extraordinary decision to take legal actions against IBM and Linux distributors and users, the UnitedLinux consortium lost its importance and is now only of historical interest.

Enterprise Server 8 was followed by Enterprise Server 9 in August 2004, continuing a pattern of Enterprise releases separated by less than two years. These releases overlap each other in time: the full life cycle of each enterprise release is five years from initial release until the final end of support and maintenance, which means that at any one time there are two fully supported versions of the Enterprise Server, one of which is approaching its end of life. The next version in the Enterprise Server line is expected to be released in the first quarter of 2006. March 2005 saw the release of the Novell Open Enterprise Server (based on SLES 9), marking the fulfillment of Novell’s intention of integrating its NetWare product with Linux: the Open Enterprise Server makes NetWare’s core functionality a service running on Linux rather than an operating system in itself and provides versions of Novell’s directory services and management software on top of this platform.

In the early days, SUSE appeared to be simply one of a large number of Linux distributions. However, unlike many of the other distributions, SUSE had a developer team of real quality and strength in numbers. This fact was not lost on IBM when they increasingly cooperated with SUSE in development work for their high-end platforms, and it gradually became apparent that there were really only two Linux companies that really mattered—namely, SUSE and Red Hat.

Historically, however, there were some differences between the two companies’ philosophies. Both Red Hat and SUSE provided boxed versions of their consumer version for sale. Red Hat offered ISO images identical to the CDs in the boxed product for download; SUSE did not, but allowed an FTP installation. SUSE somewhat controversially placed a licensing restriction on the redistribution of the YaST installation and administration tool; while the source remained open, it was not permissible to redistribute YaST on media offered for sale. This prevented a proliferation of SUSE clones in the way that there were numerous Linux distributions “based on Red Hat.”
Since the takeover of SUSE by Novell, however, the YaST license has been changed to the GPL, and more recently ISO images have been made available by FTP. Both these changes can be seen as signs of Novell’s confidence in SUSE’s leading place in the Linux market.

SUSE made a clearer distinction between the company’s enterprise and consumer versions than Red Hat did. Red Hat was already offering commercial software maintenance and support system on its boxed product (Red Hat 7.x, 8.x, and so on) when it introduced its enterprise versions (Advanced Server and Enterprise Server). Its subsequent withdrawal of all support for the boxed versions was something of a PR disaster for Red Hat and left many commercial users feeling very dissatisfied and looking for other options. A considerable proportion of these users migrated at that time to SUSE.

Source of Information : SUSE Linux 10 Bible

Wednesday, July 23, 2008

Comparing SUSE to Other Linux Versions

Using openSUSE Linux might be the best way to learn Linux if you have an eye toward becoming a Linux professional. With its focus on community development, you can be assured that you are getting some of the latest open source software available. The skills you learn will scale up nicely to the largest enterprise computing environments.

Besides Novell, Red Hat, Inc. is the other major corporation that is marketing Linux distributions in the enterprise market. The Red Hat operating systems follow the same basic dual-distribution model, with Red Hat Enterprise Linux (RHEL) as the basis of its commercial products and Fedora as its free, community-supported Linux system.

Debian is considered to be a high-quality Linux distribution with a strong commitment to the ideals of open source software. Many derivative Linux distributions, such as the popular Ubuntu Linux and the KNOPPIX live CD, are based on Debian. And although Debian is good for use in small business, the project doesn’t have the same enterprise infrastructure (training, support, documentation, and so on) that is built around SUSE Enterprise Linux.

Source of Information : Wiley SUSE Linux Toolbox 1000 plus Commands for openSUSE and SUSE Linux Enterprise

Tuesday, July 22, 2008

SUSE Linux

SUSE (pronounced SOO-zuh) is a Linux operating system owned by Novell, Inc. SUSE stands for the German phrase Software- und System-Entwicklung (meaning Software and System Development). Its roots come from Slackware Linux, and SUSE officially became an independent Linux distribution in 1996 when SUSE released its first version: 4.2. SUSE was, and remains, one of the most popular Linux distributions in Europe. In November of 2003, Novell acquired SUSE and put corporate drive behind the project.
Today SUSE comes in three editions:

• SUSE Linux Enterprise Desktop (SLED) became the commercial, subscription based Linux operating system produced by Novell, Inc. The goal was to provide an enterprise-ready desktop environment, offering support, training, documentation, hardware certification, and other products to support SLED customers.

• SUSE Linux Enterprise Server (SLES) is the SUSE Linux Enterprise Server edition, which focuses on server use rather than desktop use.

• openSUSE, an open source version of SUSE Linux without proprietary software or the support options of the enterprise Novell offerings, was launched by Novell in 2005. openSUSE is a community-driven operating system that is distributed for free (as is) and has become known for its hardware support and stability.

Source of Information : Wiley SUSE Linux Toolbox 1000 plus Commands for openSUSE and SUSE Linux Enterprise

Saturday, February 2, 2008

SUSE Linux related posts

SUSE Linux
SUSE (pronounced SOO-zuh) is a Linux operating system owned by Novell, Inc. SUSE stands for the German phrase Software- und System-Entwicklung (meaning Software and System Development).


SUSE Linux History
SUSE is the oldest existing commercial distribution of Linux. The company was founded in 1992 near Nuremberg in Germany. The first release of a Linux distribution by SUSE was early in 1994.


SUSE Linux Family Products - Personal category
Novell divides its SUSE Linux products into Enterprise and Personal. This is essentially the distinction between the versions that are sold with a paid-for software maintenance system and those that are not. The Personal category now consists of just one product, SUSE Linux Professional.


Comparing SUSE to Other Linux Versions
Using openSUSE Linux might be the best way to learn Linux if you have an eye toward becoming a Linux professional. With its focus on community development, you can be assured that you are getting some of the latest open source software available. The skills you learn will scale up nicely to the largest enterprise computing environments.


SUSE Linux GRUB Versus LILO
You may not realize it unless you are dual booting multiple operating systems, but after your BIOS starts firing up the fan, the microprocessor chip, and the power supply, a boot manager, or bootloader, takes over the process until the kernel starts up.


How SUSU Linux Loading the Kernel
When GRUB hands over the process to the SUSE Linux kernel, it leaves the scene. The kernel now takes charge, putting up the message Uncompressing Linux...; it is present and available to you until you shut down the system. While the kernel boots, SUSE Linux puts up a nice blue wallpaper to hide all the boring text that scrolls by as the kernel initializes first your peripheral hardware, then the hard drive and attending file systems, followed by the serial ports. Press the Esc key to watch the boot process unfold.


Understanding SUSE Linux X Window System
The X Window System represents two primary concepts. The X Window System was created to keep the UNIX kernel and GUI code separate. It was also designed for distributed processing based on the client/server model. That is, with X you don't need to have a computer with massive amounts of hard drive space and RAM to run graphical applications. A thin client with a connection to an X server is all you need. Nonetheless, if you have the aforementioned massive hard drive and hundreds of megabytes of RAM, you can host both the X server and many clients on your own machine.


Choosing a SUSE Linux Desktop Environment: KDE and GNOME
One of the cool things is that you can remain indecisive your whole life: You can choose what desktop to load every time you log in. Of course, you don't have to choose that often either; SUSE Linux will load whatever desktop you loaded last time by default (and the initial default, assuming you installed it, is KDE).