Linux Solutions

The article will educate a user with information on GNOME Shell 3.2 extensions covering available extensions, creating an extension, anatomy of extensions, enabling extensions and uninstalling extensions.

The GNOME Shell extension design is designed to give a high degree of power to the parts of the GNOME interface managed by the shell, such as window management and application launching. It simply loads arbitrary JavaScript and CSS. This gives developers a way to make many kinds of changes and share those changes with others, without having to patch the original source code and recompile it, and somehow distribute the patched code.

The extension system is a replacement for the “applets” or “widgets” system of GNOME 2. Extensions can add their own items to the top panel, but they can also do much more: adding a custom search provider, for instance.

Available Extensions
There is a large collection of extensions at the GNOME Shell Extensions repository website. If a user has a recent version of GNOME Shell (3.2), a user will be able to flip the switch on a compatible extension’s page to turn it on.

Creating an Extension
There is a tab to show installed extensions, and any errors that occur while loading an extension are in the “Errors” tab. GNOME Shell comes with an interactive extension creator, runnable from a Unix terminal. It starts a user off with a sample extension:
gnome-shell-extension-tool –create-extension

Anatomy of an extension
When creating an extension, a user must pick a uuid. This is a globally-unique identifier for the extension, similar in form to an email address, but need not be an actual email address. An extension, when installed on the filesystem, is a directory whose name is the same as the extension’s uuid.
Inside the directory, the bare bones of an extension are two files, metadata.json and extension.js. The content of a metadata.json looks like this:
{
“uuid”: “myextension@myname.example.com”,
“name”: “My Cool Extension”,
“description”: “Make windows burst into flame”,
“url”: “http://example.com/~myname/myextension”,
“shell-version”: [ “3.2.2″ ]
}
The extension.js file is simply a JavaScript file; it must however have a function called init, which will be invoked at most once directly after the source JS file is loaded. A user should modify all user interfaces in a separate enable function, and remove all custom functionality in a disable function.
Extension installation locations
Extensions can be installed per-user in ~/.local/share/gnome-shell/extensions, or systemwide in /usr/share/gnome-shell/extensions and /usr/local/share/gnome-shell/extensions.

Enabling extensions
• A user can enable and disable extensions on https://extensions.gnome.org/local/
• Per-user and systemwide extensions have to be enabled before they can be used. A user can do this with the GSettings key, org.gnome.shell.enabled-extensions, or several tools that manipulate this GSettings key, such as GnomeTweakTool or a recent version of gnome-shell-extension-tool.
Uninstalling extensions

• A user can uninstall an extension by clicking the uninstall button (”X”) on https://extensions.gnome.org/local/
• Alternatively a user can check the extension installation locations and delete an extension manually.

After reading the article a user would have gained knowledge GNOME Shell 3.2 extensions covering available extensions, creating an extension, anatomy of extensions, enabling extensions and uninstalling extensions.

The article will provide a user with information on antivirus solutions for linux.

There are a growing number of companies and GNU Projects coming forward to provide Linux antivirus products. The Open Antivirus Project aims to provide open source solutions to multiple antivirus needs, including squid-vscan (virus scanning with squid), samba-vscan (on-access virus scanning with Samba), and VirusHammer (a standalone virus scanner to be run by end users).

Commercial products are becoming available in the mainstream for Linux. McAfee, Trendmicro, Panda Software, Sophos, and Central Command all have products for home Linux users as well as enterprise networks.

Let’s have a look at following antivirus for Linux.

Panda Antivirus for Linux
Panda Software provides a free ‘command line only’ version of their software for use on Red Hat systems. The software can be automated easily by creating a script and then scheduling it to run scans at scheduled times, but real time protection is not possible. Updates to the engine are installed manually after downloading new definition files. If a user is going to run a Linux workstation this provides a nice cost-effective solution, but too many features are missing to consider it for deployment for on commercial servers.

Vexira
Central Command Vexira Antivirus for Linux provides real time protection for workstations as well as servers with the ability to scan email, files, and downloads from external sites. Updates can be downloaded automatically via the Internet, relieving some administration chores. Vexira also has the ability to scan files automatically as they are accessed, and it offers configurable path protection. It also provides email virus notification, blocks access to infected files, and has options for repair - move - rename - deletion of infected files. Vexira provides a command-line scanner, scans archives (.zip, .gz, .tar, etc), and allows for scalable concurrent scanning. Vexira does not provide support for SMP.

RAV Antivirus Desktop
RAV Antivirus Desktop provides a clean graphic user interface for configuring scan engine settings. With the control center, a user can modify settings for scheduled scans, scan actions such as clean, ignore, rename, delete, or copy to a quarantine folder, and even automated updates.
RAV Antivirus for Mail Servers provides support for most email servers including Sendmail, Qmail, Postfix, and CommuniGate Pro.

ServerProtect
Trend Micro’s ServerProtect provides virus protection for Linux servers in a mixed Windows environment. Administration is handled through a Web based interface, and allows administrator the ability to run on demand scans, set scan options for real time and on demand scans, and even automatic updates. ServerProtect allows administrators to configure automated alerts via email, and SNMP. The logs are easy to read and provide adequate information for dealing with file infections. The down side of this product is its lack of support for newer kernels, and SMP systems.

Sophos Antivirus
Sophos Antivirus provides a command line version of their software for use on Linux systems. Creating and scheduling scripts can automate scans. Updates must be downloaded and installed manually. This product does a great job of finding and removing viruses, but lacks many features needed by network administrators.

Central Command’s Vexira Antivirus for Linux is the best product of its kind for providing overall features and protection. Its only downfall, again, is the lack SMP support.

The 3.3 version of the Linux kernel includes a small amount of Android code. According to the Linux Foundation’s Greg Kroah-Hartman, the addition of the Android drivers “makes it easier for Android platform vendors to take the kernel.org release and create a system without having to hunt around for external patches stored on various other servers,” The Linux Foundation’s Greg Kroah-Hartman said.

Linus Torvalds, the father of Linux, announced version 3.3 of the kernel Sunday. Among the most noteworthy changes found in 3.3 is the merging of kernel code from the Android project.
Linux 3.3 also includes support for a new architecture, the Texas Instruments (NYSE: TXN) VelociTI Very Long Instruction Word (VLIW) architecture used in its C6x family of multicore devices. These were developed for embedded processor applications. Other new features include improved balancing, a virtual switch implementation and several network improvements.

Greg Kroah-Hartman, a fellow at The Linux Foundation, told LinuxInsider. “Users of the latest hardware like the new support for new hardware,” Kroah-Hartman elaborated. “Others like some [other] features, and [still] others, increased speed in some areas.”

Enter the Android
However, it’s the incorporation of Android features that have perhaps stirred up the most excitement in the Linux community. Although Android is based on Linux, it was a fork, meaning a separate code base that branched off from the main Linux repository at the Kernel.org website maintained by Torvalds.
There has been tension between the Linux and Android camps since the breakup, with one main point of contention reportedly being Google’s (Nasdaq: GOOG) “WakeLock” technology. WakeLock lets programmers tell the kernel which computing processes should not let the computer go into a sleep state, thus reducing power consumption. It was developed by Google programmers on their own.

What Android Brings to the Table?
Android features included in Linux 3.3 include Binder, Logger and the Low Memory Killer.
Binder identifies the method to invoke and pass arguments between Android processes when one Android process calls a routine in another. Loggers are used to log records to various destinations, such as log files or the console.

Android’s Low Memory Killer is put on top of existing Linux drivers for memory management. It scans the list of running processes and kills one every time its lowmem_shrink function is called.
“These aren’t improvements as-is; they’re different features that the Android platform uses in order to support the way the Android userspace operates,” Kroah-Hartman said. “They all do different and quite varied things.”

Overall, the Android code included in Linux 3.3 is “merely a tiny chunk of drivers [totaling] only 7,000 lines of code,” Kroah-Hartman pointed out. “Your serial port driver is double the size of that.”
Therefore, rather than Linux merging with Android, all that’s happened is that the out-of-tree drivers that the Android platform uses have been added to the main kernel.org tree, Kroah-Hartman stated.

Results of the Android-Linux Tie
The addition of the Android drivers “makes it easier for Android platform vendors to take the kernel.org release and create a system without having to hunt around for external patches stored on various other servers,” Kroah-Hartman pointed out.

The article will provide a reader with information about DRBL’s features is a free software, open source solution to managing the deployment of the GNU/Linux operating system across many clients. Imagine the time required to install GNU/Linux on 40, 30, or even 10 client machines individually. DRBL allows for the configuration all of the client computers by installing just one server machine.

DRBL provides a diskless or systemless environment for client machines. It works on Debian, Ubuntu, Mandriva, Red Hat, Fedora, CentOS and SuSE. DRBL uses distributed hardware resources and makes it possible for clients to fully access local hardware. It also includes Clonezilla, a partitioning and disk cloning utility similar to Symantec Ghost.

Features of DRBL
The features of DRBL:

• Peacefully coexists with other OS
• Simply install DRBL on a single server and all the clients are taken care of
• Save on hardware, budget, and maintenance fees

Peacefully coexists with other OS
DRBL uses PXE/etherboot, NFS, and NIS to provide services to client machines so that it is not necessary to install GNU/Linux on the client hard drives individually. Once the server is ready to be a DRBL server, the client machines can boot via PXE/etherboot (diskless). “DRBL” does NOT touch the client hard drives, therefore, other operating systems (e.g. MS Windows) installed on the client machines will be unaffected. This could be useful in, for example, during a phased deployment of GNU/Linux where users still want to have the option of booting to Windows and running some applications only available on MS windows. DRBL allows great flexibility in the deployment of GNU/Linux.

Simply install DRBL on a single server and all the clients are taken care of.
Using a standard PC, a user can transform a group of client PCs into a working GNU/Linux network in some steps:
• Download the DRBL package
• Run the scripts

In about 30 minutes, all the client machines will be ready to run GNU/Linux and all associated packages. No more deploying client machines one by one.

Save on hardware, budget, and maintenance fees
Hard drives are optional for a DRBL client. The hard drive is just another moving part that creates more noise and is susceptible to failure. If a hard drive is present, the client can be configured to use it as swap space while GNU/Linux is installed and configured on the centralized boot server.

A lot of time can be saved by configuring the client settings at the boot server when using the DRBL centralized boot environment. This gives the system administrator more control over what software configurations are running on each client.

The article will provide a user with information on mounting and reading a Windows XP NFTS partition in Linux. The following tutorial explains how to gain access to a Windows NTFS partition using Linux. Reading or accessing NTFS partitions in Linux is important for many reasons. Some users repair Windows Operating environments using Linux, while others use a dual boot operating environment and would like to have access to their Windows File system.

How to Mount a Windows NTFS file system partition in Linux:
Please note that in step four of this tutorial, replace hdx1 with the actual partition found in step two. For example hda1, hdb2, sda1, etc.
1. Open a terminal and type sudo su
2. Type fdisk -l (note which partition contains the NTFS file system)
3. Type mkdir /media/windows (This directory is where we will access the partition)
4. Type mount /dev/hdx1 /media/windows/ -t ntfs -o nls=utf8,umask=0222
5. Type cd /media/windows (Moves us to the windows directory)
6. Type ls to list the files on the NTFS partition

If a user wants to unmout the Windows NTFS partiton from the terminal then simply typeumount /media/windows/.

In order to access NTFS file system a user will need to install special module i.e. driver. It can be downloaded from following url:
http://www.linux-ntfs.org/content/view/128/64/

A user can select the Fedora Core Linux version and then download appropriate driver according to the kernel version. If a user wants to find out the kernel version then please use following command:
Code:
uname -r
Once downloaded driver use rpm command to install it:
Code:
rpm -ihv kernel-ntfs
Now to mount NTFS windows XP system partition use mount command:
Code:
mkdir -p /mnt/c
mount -t ntfs /dev/hdXY /mnt/c

OR

Code:
mount -t ntfs -o nls=utf8 /dev/hdXY /mnt
Use fdisk -l command to find out name of NTFS partition:
Code:
fdisk -l

How to read information stored on Linux partition?
The Linux operating system utilizes a different file structure than partitions created with the Windows XP operating system, making the process of reading one while accessing the other impossible at first. A user can circumvent this by installing any of the following tools that enable the XP computer to read the information stored on the Linux partition.

1. Explore2fs
Click the Explore2fs page in Resources. Click “Download” for the Windows Explore2fs utility. Select “Save” and save the file to the desktop.
Double click the downloaded file and double click the “Explore2fs.exe” file.
Select “Run.” An onscreen menu will appear allowing a user to browse Linux partitions

2. Linux Reader
- Click the Linux Reader page in Resources.
- Click the “Linux Reader Download Now” link and select “Save.” Save the file to your desktop.
- Double click the file and select “Run.” Click the “Install” option.
- Open “Start,” “Programs,” and “Linux Reader” to read the Linux partitions.
- Click the Ext2 page in Resources.
- Click the “Ext2IFS_1_11a.exe” file and select “Save.” Save the file to the desktop.
- Double click the file and select “Run.” Click “Install.”
- Select a drive letter for the Linux partition.
- Right click “Start,” select “Explore,” and click on the letter of the Linux partition.

The article will provide a reader with information and guidance on how to install Ophcrack and create USB.

Ophcrack is a freeWindows Password Crackeror Windows Login Password Recovery tool that uses rainbow tables to retrieve Windows login passwords from password hashes. The tool is available in two versions (Vista Ophcrack and XP Ophcrack). The bootable flash drive utility can be used to recover, reveal or crack both Windows XP and Windows Vista login passwords.
How to Boot Ophcrack from a portable USB flash drive:
Having Ophcrack for Windows Vista and XP on a USB thumbdrive can come in handy for those who may have lost their Windows admin or user Login Password and need to quickly recover a lost Windows password.

Minimum Flash Drive Capacity: 1GB
Following are the essentials for Ophcrack.
• Windows Computer (Windows XP or Vista)
• 1GB or larger flash drive (fat32 formatted)
• ophcrack-xp-livecd-2.3.1.iso
• Universal USB Installer
• tables_vista_free.zip

Creating a bootable Ophcrack flash drive.
If a user is interested in creating a bootable Ophcrack flash drive then he/she can follow the steps as provided below:
1. Download the Ophcrack XP Live CD ISO
2. Insert the USB Flash Drive
3. Download and run Universal USB Installer, select OphCrack XP, and follow the onscreen instructions
4. Create a folder named vista_free inside the tables folder on the USB Flash Drive
5. Download and unzip the tables_vista_free. zip to thetables/vista_free folder on the USB Flash Drive
6. Reboot the PC and set the system to boot from the USB device
Please note that Ophcrack launches automatically after the system has booted. A user will be able to recover both Windows XP and Windows Vista login Passwords using this single USB tool.
Creating a bootable USB Ophcrack in Windows
Now, let’s learn how to create a bootable USB Ophcrack in Windows.
Minimum Flash Drive Capacity: 512MB
Following tools will be used to create USB Ophcrack:
• Windows Computer (Windows XP is used here)
• 512 MB or larger portable device (USB stick)
• Ophcrack XP or Vista Live CD and tazusb.exe

By reading the article, a user would have gained knowledge and understanding on how to install and create Ophcrack.

The article will provide a user with information and guidance on how to install a Clonezilla and how to run Clonezilla.

Clonezilla Live is a small bootable GNU/Linux distribution for x86/amd64 (x86-64) based computers. Clonezilla SE (Server Edition) has been developed from 2004, and it is used to clone many computers simultaneously. It is an extremely useful tool, however, it does have several limitations. In order to use it, a user must first prepare a DRBL server AND the machine to be cloned must boot from a network (e.g. PXE/Etherboot/gPXE). To address these limitations, in 2007, the Free Software Lab at the NCHC has combined Debian Live with Clonezilla to produce “Clonezilla Live,” a software that can be used to easily clone individual machines. The primary benefit of Clonezilla Live is that it eliminates the need to set up a DRBL server ahead of time and the need for the computer being cloned to boot from a network. Clonezilla Live can be used to clone individual computers using a CD/DVD or USB flash drive. Though the image size is limited by the boot media’s storage capacity, this problem can be eliminated by using a network filesystem such as sshfs or samba.

How to install Clonezilla Live?
To install Clonezilla live, the basic steps are to download pre-build Clonezilla Live then put it in a boot media (CD, USB flash drive or USB hard drive). Two types of files are available, iso and zip. The former one is for CD, the latter is for USB flash drive. Besides, a user can put Clonezilla live on hard drive or PXE server, too.
• For CD/DVD:
Download an ISO file for CD/DVD. Then a user can burn the iso file to a CD/DVD with any burnning program, such K3b on GNU/Linux or InfraRecorder on MS Windows, and remeber to choose “Burn Image” to burn the ISO file on the CD. The CD can then be used to boot the machine a user want to image or clone.
• For USB flash drive or USB hard drive:
To put Clonezilla live on a USB flash drive or USB hard drive, check this doc.
• For hard drive:
To put Clonezilla live on a harddrive with OS installed already, check this doc.
• For PXE server:

How to use Clonezilla live?
Once a user has a bootable Clonezilla Live media, as created in the previous step, a user can boot it in the machine a user wants to clone. Remember to use the Clonezilla live media, such as CD, USB flash drive, USB hard drive, hard drive or PXE to boot the machine. For example, if a user Clonezilla Live in USB flash drive, a user has to boot it via USB device (Ex. USB-HDD or USB-ZIP). If necessary, a user can set the first boot priority in the BIOS as USB-HDD or USB-ZIP so that it can boot Clonezilla Live from the USB flash drive.

The article will provide a user with information and guidance on Clonezilla.
Clonezilla Live is a small bootable GNU/Linux distribution for x86/amd64 (x86-64) based computers. It enables a user to take a clone image of the computer system. This is extremely useful for backing up before doing things like: upgrading the operating system, transfering the data to another/ bigger disk, rolling out an identical disk image to multiple computers.

Clonezilla saves and restores only used blocks in the harddisk. This increases the clone efficiency. Please note it took only about 10 minutes to clone a 5.6 GBytes system image to about 40 computers via multicasting.

Features:
Please note the features of Clonezilla
• Free (GPL) Software.
• Filesystem supported: (1) ext2, ext3, ext4, reiserfs, reiser4, xfs, jfs of GNU/Linux, (2) FAT, NTFS of MS Windows, (3) HFS+ of Mac OS, (4) UFS of FreeBSD, NetBSD, and OpenBSD, and (5) VMFS3 of VMWare ESX. A user can clone GNU/Linux, MS windows, Intel-based Mac OS, and FreeBSD, NetBSD, and OpenBSD, no matter it’s 32-bit (x86) or 64-bit (x86-64) OS. For these file systems, only used blocks in partition are saved and restored. For unsupported file system, sector-to-sector copy is done by dd in Clonezilla.
• LVM2 (LVM version 1 is not) under GNU/Linux is supported.
• Boot loader, including grub (version 1 and version 2) and syslinux, could be reinstalled.
• Unattended mode is supported. Almost all steps can be done via commands and options. A user can also use a lot of boot parameters to customize own imaging and cloning.
• Multicast is supported in Clonezilla SE, which is suitable for massively clone. A user can also remotely use it to save or restore a bunch of computers if PXE and Wake-on-LAN are supported.
• The image file can be on local disk, ssh server, samba server, or NFS server.
• Based on Partclone (default), Partimage (optional), ntfsclone (optional), or dd to image or clone a partition. However, Clonezilla, containing some other programs, can save and restore not only partitions, but also a whole disk.
• By using another free software drbl-winroll, which is also developed by us, the hostname, group, and SID of cloned MS windows machine can be automatically changed.

Minimum System Requirements for Clonezilla live:
• X86 or x86-64 processor
• 196 MB of system memory (RAM)
• Boot device, e.g. CD/DVD Drive, USB port, PXE, or hard drive

Limitations:
• The destination partition must be equal or larger than the source one.
• Differential/incremental backup is not implemented yet.
• Online imaging/cloning is not implemented yet. The partition to be imaged or cloned has to be unmounted.
• Software RAID/fake RAID/firmware RAID is not supported by default. It’s can be done manually only.
• Due to the image format limitation, the image can not be explored or mounted. A user can _NOT_ recovery single file from the image.
• Recovery Clonezilla live with multiple CDs or DVDs is not implemented yet. Now all the files have to be in one CD or DVD if a user chooses to create the recovery iso file.

License:
Clonezilla itself is licensed under the GNU General Public License (GPL) Version 2. However, to run Clonezilla, a lot of free and open source software, e.g. the Linux kernel, a mininal GNU/Linux OS, are required.

If a user has read the article then he/she would have learnt about Clonezilla.

The article will provide a reader with information and guidance on GParted partitioning software and how to use it.

If a user wants to learn about GParted partitioning software then he/she should know about the operating system. No matter which operating system a user has got, they all have in common: partitions. These are logical pieces of the actual hard disk space, defining the size and the file system format for the operating systems and data that are going to be placed on them. Being able to control the partitions is one of the most basic, most important aspects of mastering the operating system. If a user has the knowledge and confidence to manipulate the layout, create it, change it or delete it, a user can adapt the hardware to according to his/her needs, without having to blindly rely on default setups defined by vendors or other people.

GParted can be used in two ways: while booted in an operating system or from a live CD. The recommended way of using GParted is from the live environment. The partitioning operations need to be done on hard disks when they are not in use, to avoid data corruption. Partitions that are in use cannot be modified. They are locked by the operating system that uses them. In technical terms, partitioning can be done only when the hard disk partitions are unmounted. If disks are empty and contain no operating system whatsoever, it does not matter anyway, because the only way a user can access the system is from a live environment.

As a rule of thumb, it is always the best idea to handle partitioning from live CD environment. Every single modern Linux distro ships as a bootable live CD. Not only does this allow a user to get a first impression of the operating system and check hardware compatibility before deciding whether to commit the distro to hard disk, it also allows a user to perform maintenance operations from the live environment.

A user can still use partitioning software against NON-system partition, that is partitions that the operating system is not installed on, and which, on demand can be unmounted. This is true for Windows and Linux alike.

Let’s see the uses of partitioning software:
• Partitioning software cannot be used on partitions that are used (mounted) by an operating system.
• Partitioning software can be used on system partitions only when booted in a live CD environment.
• Partitioning software can be used on data partitions or empty, non-system disks while booted in either local, installed operating systems or from a live CD environment.

After reading the article, a user would have gained knowledge and understating for the Gparted partitioning software.

The article will provide a user with information and guidance on Sabayon 8.0 Linux. Sabayon 8.0 Linux is 3.2, GNOME 3.2.2, KDE 4.7.4 (4.8.0 available in testing repo), Xfce 4.8, LibreOffice 3.4.4 are just some of the things you will find inside the box.

Sabayon Linux or Sabayon (formerly RR4 Linux and RR64 Linux), is a Gentoo-based Linux distribution created by Fabio Erculiani and the Sabayon development team. Sabayon follows the “Out of the box” philosophy, aiming to give the user a wide number of applications ready to use and a self-configured operating system. It is named after an Italian dessert, zabaione which is made from eggs. Sabayon’s logo is an impression of a Gentoo Penguin foot.

Sabayon 8.0’s features
• The first and best way to try a Gentoo-based Linux distribution at its full power, with all working out-of-the-box and no compilation needed at all
• The first Extreme-Rolling Release distribution, with automated repository package version bumping, thanks to Entropy Matter ebuild tracker
• Faster, cleaner and more evolved than any other rolling distro out there: we work hard to bring you the most stable rolling release experience
• Keep up-to-date your system in minutes while maintaining full Gentoo Portage compatibility
• Focusing on performance: GCC 4.6 with Graphite Loop Transformation infrastructure and Link Time Optimizations enabled
• Always up-to-date Linux Kernel 3.2 (and experimental “Fusion” Kernels available in repositories)
• Providing extra Server-oriented Linux kernels (OpenVZ, Vserver, Generic Server)
• Natively supporting the btrfs filesystem (besides ext4, aufs, and others)
• Transform Sabayon into an full-featured HTPC Operating System (Media Center) using XBMC 10.1 (11.0 available soon)
• GNOME 3.2.2 Visual Environment
• KDE 4.7.4 Desktop Environment (4.8.0 available in a few days)
• Improved Xfce 4.8 out-of-the-box experience (for those missing GNOME2)
• Improved LibreOffice integration, updated to 3.4.4
• Migrated to libav as ffmpeg replacement
• Migrated to Java 7 and Subversion 1.7
• Cinnamon and Razor Qt available in repositories
• Entropy Framework (Package Manager, Web Services) updated to 1.0_rc86, consolidating stability and performance
• Support for IME and non-roman fonts at install time
• Support for non-latin languages at install time
• More than 12000 packages available for x86_64, i686
• ARMv7 versions already available, with more than 2000 packages ready to be installed

System requirements
Now, let’s have a look at the systems minimum and recommended requirements.
Minimum requirements for Sabayon 5.2 Gnome and KDE
• i686-compatibile processor (Intel Pentium II, Pentium III, Celeron, AMD Athlon, AMD Duron)
• 512MB RAM
• 6 GB free space
• 2D X.Org supported graphic card
• DVD drive

Recommended requirements for Sabayon 5.2 Gnome and KDE
• Dual Core processor (Intel Core 2 Duo or above, AMD Athlon 64 X2 or above)
• 1024MB RAM
• 15 GB free space
• A 3D accelerated video card with X.Org support (Intel, AMD, NVIDIA)
• DVD drive

After reading the article, a user will gain an understanding and knowledge about Sabayon 8.0 Linux.