Sabayon Wiki - User contributions [en]

En:Wiki Admins

2013-05-19T20:07:48Z

Aposteeltje:

{{i18n|[[De:Wiki Administratoren|de]] [[En:Wiki Admins|en]] [[It:Wiki Admins|it]] [[Tr:Wiki_Yöneticileri|tr]] [[Zh TW:Wiki Admins|zh tw]]}}

* [[User:Lxnay|Lxnay]]
** Jabber: lxnay at sabayonlinux dot org
** Email: lxnay at sabayonlinux dot org
*[[User:Ironsight|Ironsight]]
**Email: rabidweezle at gmail dot com
*[[User:Aposteeltje|Aposteeltje]]
**Email: bwg-inc71 at zeelandnet dot nl
[[Category:Sabayon Wiki|Wiki AdminsEn]]

En:Entropy

2013-03-30T18:42:58Z

Aposteeltje: /* Rigo, the Graphical package Manager */

{{I18n| [[Ca:Entropy|ca]] [[De:Entropy|de]] [[En:Entropy|en]] [[Es:Entropy|es]] [[Fr:Entropy|fr]] [[It:Entropy|it]] [[Pl:Entropy|pl]] [[Pt:Entropy|pt]] [[Ru:Entropy|ru]] [[Tr:Entropy|Tr]]}}

{{Note|There is no requirement to use the '''sudo''' command in Sabayon Linux. Use the '''su''' command to log-in to the root user's account, perform the steps listed, then type '''exit''' to log-out from the root user's account when you have finished. Where stated in this article, you must use this method. A hash (#) prompt indicates you are logged-in as the root user; a dollar ($) prompt indicates you are logged-in under your own account.}}

==Notices==
Mandatory Entropy upgrade for all versions of Sabayon Linux below 5.2: [[Known_Issues#02.2F12.2F10_Mandatory_Entropy_Update_and_Wireless_KDE4.4|Mandatory Entropy Update and Wireless KDE 4.4]]

URL changes for all versions of Sabayon Linux below 5.2: [[Known_Issues#03.2F16.2F10_URL_Change_for_Entropy_Repository|URL Change for Entropy Repository]]

==About Entropy==
[[Image:Entropy_logo.png|thumb|The Entropy Project Logo]]
Entropy is the name of the Sabayon Linux binary package management system. This is the name for the complete infrastructure, composed by [[Equo]] client (textual), [[Sulfur]] and Rigo client (graphical), Reagent and Activator server applications.

Sabayon is based on Gentoo's testing branch, which is about on par with Debian Sid releases. Entropy takes packages from Gentoo testing and they are pre-compiled, then offered to you in binary form. There is a time delay from when Sabayon compiles these packages for Entropy and when you receive them. It is recommended to only use 1 of the package managers(either Entropy or Portage) to avoid any possible conflicts as a result of the time delay. Generally, Entropy packages will be slightly more stable because they will have already been released in Gentoo testing for a period of time(exact amount of time varies), prior to being released in Entropy.

Some highlights:
* Gentoo Linux compatible (caution, mixing entropy and portage is for advanced users)
* Takes the best from Portage, Yum and APT
* Fast as lightning
* SQLite-powered (embedded)
* Smart and User-centric
* Powerful Packages: multiple packages inside one single archive (Smart Packages)
* Supports self-contained applications (Smart Applications)
* Backward Compatible Packages: they can be used in Gentoo Linux after a quick conversion
* Multiple branches support (each branch is a release version)
* Database corruptions aware: rescue and system health scanning tools included
* Easy to deploy and use in a Network Environment
* Multiple repositories aware: everyone can create one
* Extensible and Human Understandable API
* Strongest Artificial Intelligence (Entropy has a brain)
* Great sense of humour, and much more...

===What are the main goals of Entropy?===
There were multiple reasons that led Entropy creation:
*Providing better efficiency, extraordinary speed, less power consumption to Sabayon Linux systems, making Sabayon one of the TOP leading Linux distributions.
*Unlock Gentoo to resource-constrained hardware or where CPU power shouldn't be wasted by compilers.
*Provide an easy and modern way to handle a Gentoo-based system while keeping independent from Portage codebase and at the same time being 100% compatible.
*Providing a higher grade of AI in package managers arena: Entropy guesses users' needs and acts accordingly.
*Proposing a new Point of View for developers: Web 2.0 revolution applied to package managers, being Desktop-wise, user-friendly and bringing new ideas for a key component of a Linux desktop system.

== Installing Entropy ==

{{Note| Currently, the releases supporting Entropy are: '''Sabayon Linux 3.5 and above.'''}}

There are 2 supported ways to install Entropy: either using the Sabayon Linux Portage overlay, or by using Equo itself. This is possible as all versions of Sabayon Linux after 3.5 come with Entropy installed by default. It is recommended to use Entropy with all current Sabayon releases.

{{Note|Installing Entropy in Gentoo Linux or in any other release is not supported officially although it is possible.}}

=== Upgrading Entropy using Equo ===

As of version 3.5 of Sabayon, Entropy has been included by default. To upgrade it to the latest (and greatest) version, open a terminal (such as Konsole in KDE or Terminal in GNOME) and enter the commands shown below.

1. Become root (enter the root password when prompted):
{{Console| <pre class="clear">$ su</pre>}}
2. Update the Equo Database:
{{Console| <pre class="clear"># equo update</pre>}}
That will update the database to the latest version.

3. Download and install the latest version of Entropy:
{{Console| <pre class="clear"># equo install entropy rigo</pre>}}
4. To test it's working, run:
{{Console| <pre class="clear"># equo --version</pre>}}
If you get a version number such as:
entropy: 180
equo: 180
Then it has installed and is working!

=== Installing Entropy using Portage ===

{{Warning|'''emerge and layman are Portage commands, Portage is not our package manager but is available to advanced users. Any steps using these commands can be safely ignored.'''}}

Installing via Portage can be completed using the procedure listed below. Open a terminal (such as konsole) and enter the commands:

1. Become root (enter the root password when prompted):
{{Console| <pre class="clear">$ su</pre>}}
2. Update the Sabayon overlays to the latest versions:
{{Console| <pre class="clear"># layman --sync sabayon
# layman --sync sabayon-distro</pre>}}
If you get an error message that the overlays do not exist then you need to add them:
{{Console| <pre class="clear"># layman --add sabayon
# layman --add sabayon-distro</pre>}}

3. Emerge Entropy, Equo and Rigo to install the latest versions:
{{Console| <pre class="clear"># emerge entropy equo rigo</pre>}}
4. To test it's working, run:
{{Console| <pre class="clear"># equo --version</pre>}}
If you get a version number such as:
entropy: 180
equo: 180
Then it has installed and is working!

==Packages Entropy Downloads==
Packages are downloaded and stored in '''/var/lib/entropy/client/packages/''' For instance on amd64 using Branch 5 they are stored in '''/var/lib/entropy/client/packages/packages/amd64/5'''

You can use the command below to clean them up:
{{Console| <pre class="clear"># equo cleanup</pre>}}

== About Equo, the Commandline package Manager ==

[[Image:Equo--help_ouput.png|thumb|400px|Equo in Action]]

{{main|Equo}}

Equo is the command line client-side application for the Entropy package management system, and should be always performed as Root. It is capable of installing, removing and updating packages, resolving dependences, reverse dependency handling and configuration file handling and that's just to start with.

=== Basic Usage ===

There are several options you can use when using Equo, a few of the basic commands are shown below.

Searching for a package can be accomplished by running the equo search command:
{{Console| <pre class="clear"># equo search <package name></pre>}}
To install a package use the install function, the --ask amendment is optional but recommended.
{{Console| <pre class="clear"># equo install <package> --ask</pre>}}
To remove a package use the remove function as shown below:
{{Console| <pre class="clear"># equo remove <package> --ask</pre>}}
To upgrade all your packages to the latest versions use this command:
{{Console| <pre class="clear"># equo upgrade --ask</pre>}}
As you can see from the examples above, the "--ask" amendment is optional, but highly recommended, as it not only gives you more information about the packages being installed, but also the dependencies that may come with them, giving you more control about what is going to be installed, followed by a confirmation/abortion of the command.

=== List Of Equo Functions ===

For a detailed list of the equo functions, you can always enter:
{{Console| <pre class="clear"># equo --help</pre>}}
or
{{Console| <pre class="clear"># man equo</pre>}}
at the commandline, or view them here:
[[En:List Of Equo Functions]]

== [[Rigo]], the Graphical package Manager ==

{{Note|Although still available, Sulfur has been replaced by [[Rigo]].}}

{{Warning|'''Sulfur is (yet) still available in the Repositories, but is no longer developed and will most likely NOT work anymore!!!'''}}

[[Sulfur]] was the (old) GUI (Graphical User Interface) to [[Equo]], the Sabayon Linux Binary Package Manager.
Sulfur will no longer exist in the future so [[Rigo]] will be the new and improved GUI package manager for entropy store.

=== [[Rigo]] ===

[[Image:Rigo.png|thumb|400px|The Rigo user interface]]

[[Rigo]] is the improved graphical replacement for [[Sulfur]].

=== Features ===

* "google search" like interface
* very simple and straight forward
* Rigo is faster and more responsive
* append the various packages by browsing
* easy manage repositories
* show list of pending configuration files to update
* and many more!

=== Usage ===

For a detailed usage guide, please visit the [[Rigo]] page which contains a visual walk-through of all the features.

==Package Repositories==
===What are Package Repositories===
Repositories are a storage location from which software packages may be retrieved and installed on a computer. Sabayon's Repositories contain over 10,000 different packages per architecture (x86/x86_64).

=== Why are there all these repositories? ===

Sabayon offers 4 official repositories but by default you only use one of them.

* '''sabayon-hell'''
Not a place you want to be really. This repository is used by our [http://en.wikipedia.org/wiki/Build_system build system] "Matter". The Entropy repository team carefully made lists of packages that could always be updated once a new version gets released in Portage. The build system does nothing more then work down this list and add the packages here. Since they are NOT checked by humans we can never know if the work that was done by the build system is actually what we wanted it to be.
Each monday the Entropy team evaluates what Matter did and moves these packages to sabayon-limbo (testing) repository.

* '''sabayon-limbo'''
This is the testing repository. All packages that are compiled and packaged are pushed in this repository. Work on this repository goes on 24/7.
While all packages that land here are tested at compilation phase, it is possible they have problems while running them. If you enable this repository keep in mind that things can break, you receive more updates because packages get recompiled and repackaged if needed.

{{Warning|Please note that the sabayon-limbo is an overlay repo, you MUST keep sabayonlinux.org repo enabled!
Otherwise you will have missing dependencies.}}

* '''sabayonlinux.org'''
This is the repository mostly refered to as "main". Every monday most, if not all, packages from sabayon-limbo (testing) get moved into this one.

* '''sabayon-weekly'''
This is by default the only enabled repository. It is a copy of sabayonlinux.org (main) repository. Every saturday night it gets renewed.
This repository was introduced to build in a delay between when packages get moved from testing and are available for all users. This gives packagers additional time to test packages in the main repository and fix issues if any before the copy is made.

=== How can I enable a different repository? ===

In ''/etc/entropy/repositories.conf'' you find the general configuration that count for all repositories. The different repositories are inherited from a subdirectory: ''/etc/entropy/repositories.conf.d''

In this subdirectory you'll find some predefined examples for the different repositories.

If you see that some example files are missing, then please read section: [[En:Repositories]]

Example how to enable sabayonlinux.org:
{{Console| <pre class="clear">
# cd /etc/entropy/repositories.conf.d
# mv entropy_sabayonlinux.org.example entropy_sabayonlinux.org
# equo update
</pre>}}

If you later wish to disable this repository:
{{Console| <pre class="clear"># equo repo disable sabayonlinux.org</pre>}}

{{Warning|'''Do not combine sabayon-weekly with sabayon-limbo!'''}}

If you only have sabayon-limbo and sabayon-weekly enabled you will at some point get into a situation where a previously updated package taken from sabayon-limbo wants to downgrade to the version from weekly again. Why does this happen?

As described above packages move from sabayon-limbo into sabayonlinux.org. If you do not have that repository enabled the package manager will fallback on the version it can find, the one in sabayon-weekly. This will cause unwanted downgrades and maybe breakages at some point.

=== Updating Package Repositories ===

To update the database of all packages in the repositories in your '''/etc/entropy/repositories.conf''', run (as root):
{{Console| <pre class="clear"># equo update</pre>}}

Use the same file to add additional repositories. Currently what is in the '''repositories.conf''' file is all that is available.

=== Available Repositories mirrors ===

'''Production repositories:'''
{{Console| <pre class="clear"># Sabayon Linux Official Repository
repository|sabayonlinux.org|Sabayon Linux Official Repository|http://cerberus.itti.ifce.edu.br/entropy|http://pkg.sabayon.org,sabayon.org
repository|sabayonlinux.org||http://riksun.riken.go.jp/pub/pub/Linux/sabayon/entropy|
repository|sabayonlinux.org||http://ftp.sh.cvut.cz/MIRRORS/sabayon/entropy|
repository|sabayonlinux.org||http://ftp2.cz.freebsd.org/pub/sabayon/entropy|
repository|sabayonlinux.org||http://debian.mirror.dkm.cz/sabayon/entropy|
repository|sabayonlinux.org||http://mirror.us.sabayon.org/sabayon/entropy|
repository|sabayonlinux.org||http://mirror.umoss.org/sabayonlinux/entropy|
repository|sabayonlinux.org||ftp://ftp.klid.dk/sabayonlinux/entropy|
repository|sabayonlinux.org||http://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository|sabayonlinux.org||ftp://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository|sabayonlinux.org||http://mirrors.cs.wmich.edu/sabayon/entropy|
repository|sabayonlinux.org||http://ftp.surfnet.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository|sabayonlinux.org||ftp://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository|sabayonlinux.org||http://ftp.cc.uoc.gr/mirrors/linux/SabayonLinux/entropy|
repository|sabayonlinux.org||http://mirror.dun.nu/sabayonlinux/entropy|
repository|sabayonlinux.org||http://ftp.rnl.ist.utl.pt/pub/sabayon ftp://ftp.rnl.ist.utl.pt/pub/sabayon|
repository|sabayonlinux.org||http://mirror.internode.on.net/pub/sabayonlinux/entropy|
repository|sabayonlinux.org||http://cross-lfs.sabayonlinux.org/entropy|
repository|sabayonlinux.org||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
</pre>}}

Note that you can use the following command to optimise the order of the mirrors in '''/etc/entropy/repositories.conf'''. This command pings the mirrors and, based on the response times, orders the mirrors in '''/etc/entropy/repositories.conf''' accordingly:

For the '''Daily''' repository, use:
{{Console| <pre class="clear"># equo repo mirrorsort sabayonlinux.org</pre>}}

For the '''Weekly''' repository, use:
{{Console| <pre class="clear"># equo repo mirrorsort sabayon-weekly</pre>}}

And for the '''testing''' repository, use:
{{Console| <pre class="clear"># equo repo mirrorsort sabayon-limbo</pre>}}

'''Testing repositories:'''
''These can break your system, only add them when you really know what you are doing.''
{{Console| <pre class="clear"># Limbo
repository = sabayon-limbo|Sabayon Limbo Testing Repository|http://cerberus.itti.ifce.edu.br/entropy|http://pkg.sabayon.org,sabayon.org
repository = sabayon-limbo||http://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository = sabayon-limbo||http://ftp.rnl.ist.utl.pt/pub/sabayon ftp://ftp.rnl.ist.utl.pt/pub/sabayon|
repository = sabayon-limbo||http://mirror.internode.on.net/pub/sabayonlinux/entropy|
repository = sabayon-limbo||ftp://mirror.aarnet.edu.au/pub/SabayonLinux/entropy|
repository = sabayon-limbo||http://cross-lfs.sabayonlinux.org/entropy|
repository = sabayon-limbo||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
</pre>}}

=== Community Repositories ===

{{main|Community Repositories}}

Community Repositories are user-managed packages repositories. Users can recompile packages with different settings, add their own ones and make all available to other people. Repository publishers are responsible for how a package is compiled and what is compiled.

== Masking and Unmasking Packages in Entropy ==

You can find the files to edit in '''/etc/entropy/packages/'''.
* Use '''package.mask''' to mask a file, see '''package.mask.example''' for more information.
* Use '''package.unmask''' to unmask a file. See '''package.unmask.example''' for more information.


==Adding Additional Packages Manually==
[https://packages.sabayon.org/ Sabayon Linux Package Repository]

You can download packages and place them in the package directory for Entropy to use. See [[FAQ#Where_does_Entropy_download_the_packages_to.3F|Where to Put Packages]]

==Fresh Install - What to do?==
So you just installed a fresh copy of Sabayon Linux and are wondering what to do next.

The first thing to do is of course learn how to use the Entropy package manager. It is vital to know your package manager. So read first, then do.

===Using Entropy to upgrade all installed packages===

Now that you have learned about the Entropy package manager, let's get our package list for the package manager current. You will have to be root to use the commands, so open a terminal and enter '''su''' with the root password and, if you did it correctly, your prompt will change to a hash symbol (#) to show you are now logged in as the root user. '''DO NOT use sudo'''.
{{Console| <pre class="clear"># equo update</pre>}}

If you run into problems with that then try:
{{Console| <pre class="clear"># equo update --force</pre>}}

Next, as mentioned in the section above, it is a good idea to optimize the sorting of mirrors so that all package upgrades will be downloaded as quickly as possible:
{{Console| <pre class="clear"># equo repo mirrorsort sabayon-weekly</pre>}}

Once you have that completed it is vital to get Entropy upgraded to the latest version before doing a full system upgrade. Upgrade will bring your system to current development.
{{Console| <pre class="clear"># equo install entropy rigo equo --relaxed
# equo conf update</pre>}}

Once the Entropy code is upgraded to the latest version, fully upgrade the rest of your system with these two commands:
{{Console| <pre class="clear"># equo update
# equo upgrade --ask</pre>}}

Follow what is happening on the screen, as Entropy will show you what it is going to do and ask for confirmations.
* The 'equo update' command will update the database on your PC with the latest information on packages available in the Entropy repositories;
* the 'equo upgrade' command will download from the repositories the binary files for new versions of packages installed on your PC and then install the new versions of those packages.

Time of process depends on how many packages, bandwidth and hardware. After it is done, make sure to:
{{Console| <pre class="clear"># equo conf update</pre>}}

You will want to make your selection but you really should get to know your config files as they will change your system. More than likely most will select -5. I always look over the config files as I don't want some of my configs getting overwritten.

The final step is to run the following commands, checking for missing dependencies and stability:

{{Console| <pre class="clear"># equo deptest
# equo libtest</pre>}}

After this has finished, reboot and enjoy your freshly installed fully updated Sabayon.

{{Note|The equo upgrade command does not upgrade the kernel if a new version happens to be available in the Entropy repository. If you want to install a newer version of the kernel then you must:
# install the newer kernel manually using equo;
# ensure that the symbolic link to the kernel sources is pointing to the correct version of the kernel sources (by using the 'eselect kernel' command);
# install the corresponding kernel modules manually using equo;
# ensure that the correct OpenGL implementation for your video driver is selected (by using the 'eselect opengl' command);
# ensure the new kernel is included in the menu in grub.conf (SL 5.1-r1 and earlier) or grub.cfg (SL 5.2 and onwards).}}

What about using [[Sulfur]]? I do not recommend using Sulfur for the initial upgrade. Equo is 100x's more reliable and you won't end up with the issues that Sulfur can cause. So do your initial installation with Equo then look at using Sulfur or even better Rigo after that.

==The kernel==

===Misunderstandings about the kernel===
Some people have a lot of questions about the kernel., Questions like:

I installed kernel 3.8.5. but still, "uname -a" is showing 3.8.0

or

I want to customize kernel 3.8.5 , but /usr/src only shows 3.8.0

Well, let me explain that:

Every version of the kernel is followed by little updates., called "patchlevel" ., indicated by the third number.

So, 3.7.4 is just a update to the 3.7 serie. , just as 3.8.3 is a update to the 3.8 serie.

Uname -a or -r ,

cat /proc/version,

eselect kernel and eselect bzimage

/usr/src

and even the kernelline in grub.cfg

are ALL using the BASE notation of the kernel., and NOT it's updates. that stays "0" , Allthough you ARE running it.

(3.5.0) (3.6.0) (3.7.0) etc.

So, when you choose 3.7.0 in GRUB, or "eselect kernel" , or whatever, and kernel 3.7.4 is installed.,

(you can check that with command: equo query installed "linux-sabayon" )

in fact you ARE booting with 3.7.4 (only not showed), and you can assure yourself that it is.....

===Upgrading the Linux kernel===

{{Note|'''Entropy should never call a new kernel by itself, unless you're already running 3.7 for example. But then it's a update: r1, r2, etc.'''
However in some cases, like VirtualBox is known to install a new kernel when installing VirtualBox.
You can bypass that by doing:

equo install virtualbox.bin --nodeps

as described in the wiki.
Entropy itself will never just install a new kernel. This is mostly invoked by other packages, such as VirtualBox, or if the user explicitly invokes it.}}
For detailed instructions on updating the kernel using Entropy use the following link:
* [[HOWTO:_Upgrade_kernel_using_Entropy|How to upgrade the kernel using Entropy]]

The kernel image is not upgraded automatically; you have to upgrade it manually. You install a new version of the kernel image as you would any other package, i.e. using either the equo command or Rigo. For example, if you currently have the 3.6-r3 kernel image installed on your PC and version 3.7-r3 is available in the Entropy repositories then you can install the new version by entering the command:
{{Console|<pre class="clear"># equo install sys-kernel/linux-sabayon-3.7-r3</pre>}}

Once you have installed a new version of the kernel image you must install the relevant modules your PC requires, which have been compiled specifically for that version of the kernel image. When you do this, you must specify the full package name, including the kernel version, of the modules.

For example, if you had just installed the 3.7.0 kernel image (the Entropy package sys-kernel/linux-sabayon-3.7.0) then you would have to install the relevant modules for it like so:
{{Console|<pre class="clear"># equo install x11-drivers/ati-drivers-12.10#3.7.0-sabayon</pre>}}

If you do not include the "#3.7.0-sabayon" in the package name then, if the ati-drivers-12.10 package for an earlier version of the kernel happens to be in the repositories, it would be installed/re-installed instead of the module you need.

The above example assumes you are using the closed-source FGLRX driver for an AMD GPU, but the same principle applies if you are using an NVIDIA closed-source driver with an NVIDIA GPU, or if you are using any other software that is a kernel module (VirtualBox modules are another example).

You must also use the 'eselect kernel' command to make the symbolic link to the kernel sources point to the new version of the kernel sources, and you must use the 'eselect opengl' command to select the correct OpenGL implementation for your video driver. The Entropy kernel image package will take care of upgrading the Grub2 grub.cfg file to include the new kernel image in the Grub menu.

The instructions above assume you are upgrading to a later version of the kernel, but are equally applicable if you are downgrading to an earlier version of the kernel.

=== Using Kernel Switcher ===

'''kernel-switcher''' is an easy-to-use tool to simplify upgrading the kernel in Sabayon Linux. Remember, doing regular upgrades will not upgrade the kernel: you need to invoke a kernel change. This is done to prevent users from breaking their system and then screaming in the forums or in irc.

{{Console| <pre class="clear">
# kernel-switcher --help
>> kernel-switcher - Sabayon Linux Kernel Switcher BETA
>> switch kernel: kernel-switcher switch <kernel package>
>> list kernels: kernel-switcher list
>> this help: kernel-switcher help
</pre>}}

The '''kernel-switcher list''' command is a nice feature, but can be overwhelming as it lists all kernels currently available in the repository. You may prefer to use '''equo search linux-sabayon''' as ''linux-sabayon'' is the Sabayon kernel package. With '''equo search linux-sabayon''' you can see if any newer kernels exist. For example, if you find that ''linux-sabayon-3.8.0'' is available as an upgrade, you would upgrade to it as follows:

{{Console| <pre class="clear">
# kernel-switcher switch linux-sabayon-3.8.0
>> @@ Calculating dependencies …
>> ## [U] [sabayonlinux.org] sys-kernel/linux-firmwares-3.8.0|0 [3.8.0|0]
>> ## [N] [sabayonlinux.org] sys-kernel/linux-sabayon-3.8.0|0
>> ## [N] [sabayonlinux.org] net-wireless/broadcom-sta-5.100.82.38-r1#3.8.0-sabayon|0
>> ## [N] [sabayonlinux.org] x11-drivers/nvidia-drivers-260.19.29#3.8.0-sabayon|0
</pre>}} 

Notice it pulls the new kernel plus new versions of kernel modules/drivers that are currently installed. Let it download and install everything needed for the new kernel. Once this is done, GRUB 2 will reflect the change so that, when you reboot, the new kernel is available to select. A few other things need to be done before you reboot: Sometimes the OpenGL libraries get reset and the user finds video is not working properly, so you need to check and set them back:

{{Console| <pre class="clear">
# eselect opengl list

Available OpenGL implementations:
[1] nvidia *
[2] xorg-x11
</pre>}}

In the above example the asterisk indicates that the ''nvidia'' OpenGL libraries are selected, which I do need. If it was set to ''xorg-x11'', I would use the following command to select the closed-source OpenGL libraries:

{{Console| <pre class="clear"># eselect opengl set 1</pre>}}

Another thing to check is the symlink to the kernel:

{{Console| <pre class="clear">
# eselect kernel list

Available kernel symlink targets:
[1] linux-3.7.0-sabayon
[2] linux-3.8.0-sabayon *
</pre>}}

Great, it's set to the new kernel. Since you are using GRUB, maybe there's no point(?), but you can as well issue

{{Console| <pre class="clear"># eselect bzimage list</pre>}}

and make sure your newest kernel is selected. Otherwise you can select it by issuing

{{Console| <pre class="clear"># eselect bzimage set <NUMBER></pre>}}

where <NUMBER> stands for the number of the desired kernel in the previous list. E.g:

{{Console| <pre class="clear"># eselect bzimage set 2</pre>}}

It is also worth running the both commands:

{{Console| <pre class="clear">
# equo deptest
# equo libtest
</pre>}}

This will make sure things are proper. Once that is complete, reboot to your new kernel.

== Using Portage to upgrade the Entropy code ==

{{Warning|'''emerge and layman are Portage commands, Portage is not our package manager but is available to advanced users. Any steps using these commands can be safely ignored.'''}}

We changed the overlay to git now, so for Sabayon Linux version < 4.1 version you need to do the following:
{{Note|This step is optional but recommended.}}

{{Console| <pre class="clear">
# layman -d sabayon
# layman -d sabayon-distro
# layman -L
# layman -a sabayon
# layman -a sabayon-distro
</pre>}}

'''If''' it complains about not having git installed, then do:

{{Console| <pre class="clear"># equo install dev-vcs/git</pre>}}

You should also update the Portage package list in case you need to use Portage to install the latest version of Entropy if you run into trouble upgrading Entropy using the Entropy commands listed earlier. This step is optional but, if you have problems getting Entropy working, you will need to perform this step to get the latest version of Entropy from the Sabayon Portage overlays.

{{Console| <pre class="clear"># emerge --sync && layman --sync sabayon && layman --sync sabayon-distro</pre>}}

If you get an error message that the Sabayon overlays do not exist then you need to add them:

{{Console| <pre class="clear">
# layman --add sabayon
# layman --add sabayon-distro
</pre>}}

{{Note|The first emerge --sync is a little time consuming, but it's a one-time deal.}}

Now, if you have problems getting the equo update to function or problems getting latest Entropy installed, you can use emerge to get the latest version instead. Follow below for how to install Entropy via Portage:

{{Console| <pre class="clear"># emerge entropy equo rigo</pre>}}

Hopefully now you are ready to start the upgrading process:

{{Console| <pre class="clear"># equo upgrade --ask</pre>}}

Before you reboot you should check some things first: [http://forum.sabayon.org/viewtopic.php?f=76&t=16399 Please look at this thread to see what I mean]. There can be critical things to take care of first before you can safely reboot. Generally it's not a big issue, but a kernel change does require some additional work. You will need to reinstall your drivers/modules to match the kernel.

Make sure you also grab the kernel sources:
{{Console| <pre class="clear"># equo install sabayon-sources</pre>}}

You should also keep your Portage ebuild list updated from time to time, just to be safe. You don't have to do it daily, but maybe once a week.

{{Note|You do not have to do this step at all, until or unless you run into problems.}}

The following step only speeds up the process later by wasting the time doing it now:

{{Console| <pre class="clear"># emerge --sync && layman --sync sabayon && layman --sync sabayon-distro</pre>}}

If you get an error message that the Sabayon overlays do not exist then you need to add them:

{{Console| <pre class="clear">
# layman --add sabayon
# layman --add sabayon-distro
</pre>}}

==Hopping Branches==

{{Note|Since branch 5, Sabayon Linux became a 'Rolling Release', so 'hopping' is not needed anymore. Just upgrade the system as stated above.
The following is '''only''' for people running branch 4.2, 4.1, or 4.}}

Switching branches is as easy as typing equo hop [branch], replace the [branch] with the one you want to hop to. So let's say we are using Sabayon Linux 4.2 and want to jump to branch 5, all we have to do is:

{{Console| <pre class="clear"># equo hop 5</pre>}}

Now we need to update our package list with new branch:

{{Console| <pre class="clear"># equo update</pre>}}

Always get the latest package manager first:

{{Console| <pre class="clear"># equo install entropy equo rigo --relaxed</pre>}}

Now you are ready to start your upgrade:

{{Console| <pre class="clear"># equo upgrade</pre>}}

There could be many packages involved with this and can be time consuming so plan a head for this before doing it. Also see thread http://forum.sabayon.org/viewtopic.php?f=54&t=16399 for some good learning on things you will need to check.

Update your config files when done with upgrade:

{{Console| <pre class="clear"># equo conf update</pre>}}

Before rebooting:
* check your kernel with 'eselect kernel list' and make sure it is correct latest kernel selected, it will have the * next to it.
* check gcc version with 'gcc-config -l' and make sure it is on latest one
* check 'binutils-config -l' and make sure it's set
* check 'eselect opengl list' for right driver
* check '''/boot/grub/grub.conf''' to make sure it updated properly
* check 'eselect python list' and make sure it's set to the latest one

Do not ever go backwards with your branches, meaning, don't go from Branch 5 back to Branch 4.

==Testing Branch / Rolling Releases==
=== Warning - Read first ===
{{Warning|'''This branch of Entropy is dangerous. Read this section from beginning to end before doing anything with it.'''}}

Let us quickly go through the most common factors that make running the testing branch impractical:
* A good amount of experience with Portage and related tools is crucial to fix problems that are likely to arise when using the testing branch. Reporting problems encountered on this branch is good and helps with the Sabayon development process, but it is not a way for you to get a fix quickly. Only Portage is likely to do that for you.
* Solid understanding of Linux (OS including programs) is highly important, too. You can expect to be confronted with new configuration options and non-trivial problems. You will need pretty extensive knowledge to either diagnose and solve, or work around these problems, at a point in time when they have little to no distribution-specific documentation yet - sometimes not even any good documentation at all.
* High maintenance - just to explicitly state the other consequence of the two points directly above.
* High bandwidth consumption - there are some package upgrades almost every day, and the amount of upgrades can easily hit a few hundred MB every week.

{{Note|Don't forget, that there's a 5 TB constraint for Sabayon Linux' servers - and the upkeep costs a pretty penny. So if you don't interested in improving packages in the testing branch, please consider the economic aspect, too.}}

If you have any doubt about meeting one or more of the criteria outlined before, but need or want to use the testing branch / rolling releases anyway, '''it is strongly recommended that you make use of some virtualization software (and its snapshotting features), rather than deploying the testing branch in your main installation'''. That way, if some operation goes wrong, you typically won't need to resolve any issues, but can just revert to the last working snapshot - which will in turn allow you to try a more selective operation, or simply defer the operation until later. Modern virtualization software can interact fairly nicely with the host, like displaying windows as if they were part of the host, or share files between host and guest, so this should be the way to go even if you need the most recent version of some program in day-to-day use.

'''Basically use it on your own risk, don't blame us if anything breaks and your system doesn't work since its unsupported at this stage. We did tell you about the risks and what is good to think over before adding the limbo repo.'''

=== Setting it up ===

You can add this to /etc/entropy/repositories.conf:
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayon.org|http://pkg.sabayon.org#bz2

Our next release is from packages that are put into the Limbo Repository. This will keep you rolling consistently all the time. This prevents the large amount of packages that hops cause. You will run into bugs/issues at times, but they are usually sorted pretty quickly.

So after adding that line you can then simply do:

{{Console| <pre class="clear">
# equo update
# equo upgrade
</pre>}}

How often you do it is up to you. Once a day or once a week, whatever works for you.

=== Adding Entropy Mirror ===

The file to edit: /etc/entropy/repositories.conf

You may notice a big slowdown with Entropy and the Limbo Repo, so please add this mirror under your existing Limbo line:

{{File|/etc/entropy/repositories.conf| <pre class="clear">
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayonlinux.org/entropy|http://pkg.sabayonlinux.org
</pre>}}

so it should look like:

{{File|/etc/entropy/repositories.conf| <pre class="clear">
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayonlinux.org/entropy|http://pkg.sabayonlinux.org
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://na.mirror.garr.it/mirrors/sabayonlinux/entropy/|http://na.mirror.garr.it/mirrors/sabayonlinux/entropy#bz2
</pre>}}

Now you should have good speeds again. '''You may have to put a # in front of the top one to force equo to use garr only.''' For example:

{{File|/etc/entropy/repositories.conf| <pre class="clear">
# repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayonlinux.org/entropy|http://pkg.sabayonlinux.org
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://na.mirror.garr.it/mirrors/sabayonlinux/entropy/|http://na.mirror.garr.it/mirrors/sabayonlinux/entropy#bz2
</pre>}}

Another thing you can do is make it look like:

{{File|/etc/entropy/repositories.conf| <pre class="clear">
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayonlinux.org/entropy|http://pkg.sabayonlinux.org
repository|sabayon-limbo||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
</pre>}}

You will still get the update db from pkg site, but it should download the packages from garr. I leave the choice up to you.

En:Entropy

2013-03-30T18:42:32Z

Aposteeltje: /* Rigo */

{{I18n| [[Ca:Entropy|ca]] [[De:Entropy|de]] [[En:Entropy|en]] [[Es:Entropy|es]] [[Fr:Entropy|fr]] [[It:Entropy|it]] [[Pl:Entropy|pl]] [[Pt:Entropy|pt]] [[Ru:Entropy|ru]] [[Tr:Entropy|Tr]]}}

{{Note|There is no requirement to use the '''sudo''' command in Sabayon Linux. Use the '''su''' command to log-in to the root user's account, perform the steps listed, then type '''exit''' to log-out from the root user's account when you have finished. Where stated in this article, you must use this method. A hash (#) prompt indicates you are logged-in as the root user; a dollar ($) prompt indicates you are logged-in under your own account.}}

==Notices==
Mandatory Entropy upgrade for all versions of Sabayon Linux below 5.2: [[Known_Issues#02.2F12.2F10_Mandatory_Entropy_Update_and_Wireless_KDE4.4|Mandatory Entropy Update and Wireless KDE 4.4]]

URL changes for all versions of Sabayon Linux below 5.2: [[Known_Issues#03.2F16.2F10_URL_Change_for_Entropy_Repository|URL Change for Entropy Repository]]

==About Entropy==
[[Image:Entropy_logo.png|thumb|The Entropy Project Logo]]
Entropy is the name of the Sabayon Linux binary package management system. This is the name for the complete infrastructure, composed by [[Equo]] client (textual), [[Sulfur]] and Rigo client (graphical), Reagent and Activator server applications.

Sabayon is based on Gentoo's testing branch, which is about on par with Debian Sid releases. Entropy takes packages from Gentoo testing and they are pre-compiled, then offered to you in binary form. There is a time delay from when Sabayon compiles these packages for Entropy and when you receive them. It is recommended to only use 1 of the package managers(either Entropy or Portage) to avoid any possible conflicts as a result of the time delay. Generally, Entropy packages will be slightly more stable because they will have already been released in Gentoo testing for a period of time(exact amount of time varies), prior to being released in Entropy.

Some highlights:
* Gentoo Linux compatible (caution, mixing entropy and portage is for advanced users)
* Takes the best from Portage, Yum and APT
* Fast as lightning
* SQLite-powered (embedded)
* Smart and User-centric
* Powerful Packages: multiple packages inside one single archive (Smart Packages)
* Supports self-contained applications (Smart Applications)
* Backward Compatible Packages: they can be used in Gentoo Linux after a quick conversion
* Multiple branches support (each branch is a release version)
* Database corruptions aware: rescue and system health scanning tools included
* Easy to deploy and use in a Network Environment
* Multiple repositories aware: everyone can create one
* Extensible and Human Understandable API
* Strongest Artificial Intelligence (Entropy has a brain)
* Great sense of humour, and much more...

===What are the main goals of Entropy?===
There were multiple reasons that led Entropy creation:
*Providing better efficiency, extraordinary speed, less power consumption to Sabayon Linux systems, making Sabayon one of the TOP leading Linux distributions.
*Unlock Gentoo to resource-constrained hardware or where CPU power shouldn't be wasted by compilers.
*Provide an easy and modern way to handle a Gentoo-based system while keeping independent from Portage codebase and at the same time being 100% compatible.
*Providing a higher grade of AI in package managers arena: Entropy guesses users' needs and acts accordingly.
*Proposing a new Point of View for developers: Web 2.0 revolution applied to package managers, being Desktop-wise, user-friendly and bringing new ideas for a key component of a Linux desktop system.

== Installing Entropy ==

{{Note| Currently, the releases supporting Entropy are: '''Sabayon Linux 3.5 and above.'''}}

There are 2 supported ways to install Entropy: either using the Sabayon Linux Portage overlay, or by using Equo itself. This is possible as all versions of Sabayon Linux after 3.5 come with Entropy installed by default. It is recommended to use Entropy with all current Sabayon releases.

{{Note|Installing Entropy in Gentoo Linux or in any other release is not supported officially although it is possible.}}

=== Upgrading Entropy using Equo ===

As of version 3.5 of Sabayon, Entropy has been included by default. To upgrade it to the latest (and greatest) version, open a terminal (such as Konsole in KDE or Terminal in GNOME) and enter the commands shown below.

1. Become root (enter the root password when prompted):
{{Console| <pre class="clear">$ su</pre>}}
2. Update the Equo Database:
{{Console| <pre class="clear"># equo update</pre>}}
That will update the database to the latest version.

3. Download and install the latest version of Entropy:
{{Console| <pre class="clear"># equo install entropy rigo</pre>}}
4. To test it's working, run:
{{Console| <pre class="clear"># equo --version</pre>}}
If you get a version number such as:
entropy: 180
equo: 180
Then it has installed and is working!

=== Installing Entropy using Portage ===

{{Warning|'''emerge and layman are Portage commands, Portage is not our package manager but is available to advanced users. Any steps using these commands can be safely ignored.'''}}

Installing via Portage can be completed using the procedure listed below. Open a terminal (such as konsole) and enter the commands:

1. Become root (enter the root password when prompted):
{{Console| <pre class="clear">$ su</pre>}}
2. Update the Sabayon overlays to the latest versions:
{{Console| <pre class="clear"># layman --sync sabayon
# layman --sync sabayon-distro</pre>}}
If you get an error message that the overlays do not exist then you need to add them:
{{Console| <pre class="clear"># layman --add sabayon
# layman --add sabayon-distro</pre>}}

3. Emerge Entropy, Equo and Rigo to install the latest versions:
{{Console| <pre class="clear"># emerge entropy equo rigo</pre>}}
4. To test it's working, run:
{{Console| <pre class="clear"># equo --version</pre>}}
If you get a version number such as:
entropy: 180
equo: 180
Then it has installed and is working!

==Packages Entropy Downloads==
Packages are downloaded and stored in '''/var/lib/entropy/client/packages/''' For instance on amd64 using Branch 5 they are stored in '''/var/lib/entropy/client/packages/packages/amd64/5'''

You can use the command below to clean them up:
{{Console| <pre class="clear"># equo cleanup</pre>}}

== About Equo, the Commandline package Manager ==

[[Image:Equo--help_ouput.png|thumb|400px|Equo in Action]]

{{main|Equo}}

Equo is the command line client-side application for the Entropy package management system, and should be always performed as Root. It is capable of installing, removing and updating packages, resolving dependences, reverse dependency handling and configuration file handling and that's just to start with.

=== Basic Usage ===

There are several options you can use when using Equo, a few of the basic commands are shown below.

Searching for a package can be accomplished by running the equo search command:
{{Console| <pre class="clear"># equo search <package name></pre>}}
To install a package use the install function, the --ask amendment is optional but recommended.
{{Console| <pre class="clear"># equo install <package> --ask</pre>}}
To remove a package use the remove function as shown below:
{{Console| <pre class="clear"># equo remove <package> --ask</pre>}}
To upgrade all your packages to the latest versions use this command:
{{Console| <pre class="clear"># equo upgrade --ask</pre>}}
As you can see from the examples above, the "--ask" amendment is optional, but highly recommended, as it not only gives you more information about the packages being installed, but also the dependencies that may come with them, giving you more control about what is going to be installed, followed by a confirmation/abortion of the command.

=== List Of Equo Functions ===

For a detailed list of the equo functions, you can always enter:
{{Console| <pre class="clear"># equo --help</pre>}}
or
{{Console| <pre class="clear"># man equo</pre>}}
at the commandline, or view them here:
[[En:List Of Equo Functions]]

== Rigo, the Graphical package Manager ==

{{Note|Although still available, Sulfur has been replaced by [[Rigo]].}}

{{Warning|'''Sulfur is (yet) still available in the Repositories, but is no longer developed and will most likely NOT work anymore!!!'''}}

[[Sulfur]] was the (old) GUI (Graphical User Interface) to [[Equo]], the Sabayon Linux Binary Package Manager.
Sulfur will no longer exist in the future so [[Rigo]] will be the new and improved GUI package manager for entropy store.

=== [[Rigo]] ===

[[Image:Rigo.png|thumb|400px|The Rigo user interface]]

[[Rigo]] is the improved graphical replacement for [[Sulfur]].

=== Features ===

* "google search" like interface
* very simple and straight forward
* Rigo is faster and more responsive
* append the various packages by browsing
* easy manage repositories
* show list of pending configuration files to update
* and many more!

=== Usage ===

For a detailed usage guide, please visit the [[Rigo]] page which contains a visual walk-through of all the features.

==Package Repositories==
===What are Package Repositories===
Repositories are a storage location from which software packages may be retrieved and installed on a computer. Sabayon's Repositories contain over 10,000 different packages per architecture (x86/x86_64).

=== Why are there all these repositories? ===

Sabayon offers 4 official repositories but by default you only use one of them.

* '''sabayon-hell'''
Not a place you want to be really. This repository is used by our [http://en.wikipedia.org/wiki/Build_system build system] "Matter". The Entropy repository team carefully made lists of packages that could always be updated once a new version gets released in Portage. The build system does nothing more then work down this list and add the packages here. Since they are NOT checked by humans we can never know if the work that was done by the build system is actually what we wanted it to be.
Each monday the Entropy team evaluates what Matter did and moves these packages to sabayon-limbo (testing) repository.

* '''sabayon-limbo'''
This is the testing repository. All packages that are compiled and packaged are pushed in this repository. Work on this repository goes on 24/7.
While all packages that land here are tested at compilation phase, it is possible they have problems while running them. If you enable this repository keep in mind that things can break, you receive more updates because packages get recompiled and repackaged if needed.

{{Warning|Please note that the sabayon-limbo is an overlay repo, you MUST keep sabayonlinux.org repo enabled!
Otherwise you will have missing dependencies.}}

* '''sabayonlinux.org'''
This is the repository mostly refered to as "main". Every monday most, if not all, packages from sabayon-limbo (testing) get moved into this one.

* '''sabayon-weekly'''
This is by default the only enabled repository. It is a copy of sabayonlinux.org (main) repository. Every saturday night it gets renewed.
This repository was introduced to build in a delay between when packages get moved from testing and are available for all users. This gives packagers additional time to test packages in the main repository and fix issues if any before the copy is made.

=== How can I enable a different repository? ===

In ''/etc/entropy/repositories.conf'' you find the general configuration that count for all repositories. The different repositories are inherited from a subdirectory: ''/etc/entropy/repositories.conf.d''

In this subdirectory you'll find some predefined examples for the different repositories.

If you see that some example files are missing, then please read section: [[En:Repositories]]

Example how to enable sabayonlinux.org:
{{Console| <pre class="clear">
# cd /etc/entropy/repositories.conf.d
# mv entropy_sabayonlinux.org.example entropy_sabayonlinux.org
# equo update
</pre>}}

If you later wish to disable this repository:
{{Console| <pre class="clear"># equo repo disable sabayonlinux.org</pre>}}

{{Warning|'''Do not combine sabayon-weekly with sabayon-limbo!'''}}

If you only have sabayon-limbo and sabayon-weekly enabled you will at some point get into a situation where a previously updated package taken from sabayon-limbo wants to downgrade to the version from weekly again. Why does this happen?

As described above packages move from sabayon-limbo into sabayonlinux.org. If you do not have that repository enabled the package manager will fallback on the version it can find, the one in sabayon-weekly. This will cause unwanted downgrades and maybe breakages at some point.

=== Updating Package Repositories ===

To update the database of all packages in the repositories in your '''/etc/entropy/repositories.conf''', run (as root):
{{Console| <pre class="clear"># equo update</pre>}}

Use the same file to add additional repositories. Currently what is in the '''repositories.conf''' file is all that is available.

=== Available Repositories mirrors ===

'''Production repositories:'''
{{Console| <pre class="clear"># Sabayon Linux Official Repository
repository|sabayonlinux.org|Sabayon Linux Official Repository|http://cerberus.itti.ifce.edu.br/entropy|http://pkg.sabayon.org,sabayon.org
repository|sabayonlinux.org||http://riksun.riken.go.jp/pub/pub/Linux/sabayon/entropy|
repository|sabayonlinux.org||http://ftp.sh.cvut.cz/MIRRORS/sabayon/entropy|
repository|sabayonlinux.org||http://ftp2.cz.freebsd.org/pub/sabayon/entropy|
repository|sabayonlinux.org||http://debian.mirror.dkm.cz/sabayon/entropy|
repository|sabayonlinux.org||http://mirror.us.sabayon.org/sabayon/entropy|
repository|sabayonlinux.org||http://mirror.umoss.org/sabayonlinux/entropy|
repository|sabayonlinux.org||ftp://ftp.klid.dk/sabayonlinux/entropy|
repository|sabayonlinux.org||http://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository|sabayonlinux.org||ftp://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository|sabayonlinux.org||http://mirrors.cs.wmich.edu/sabayon/entropy|
repository|sabayonlinux.org||http://ftp.surfnet.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository|sabayonlinux.org||ftp://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository|sabayonlinux.org||http://ftp.cc.uoc.gr/mirrors/linux/SabayonLinux/entropy|
repository|sabayonlinux.org||http://mirror.dun.nu/sabayonlinux/entropy|
repository|sabayonlinux.org||http://ftp.rnl.ist.utl.pt/pub/sabayon ftp://ftp.rnl.ist.utl.pt/pub/sabayon|
repository|sabayonlinux.org||http://mirror.internode.on.net/pub/sabayonlinux/entropy|
repository|sabayonlinux.org||http://cross-lfs.sabayonlinux.org/entropy|
repository|sabayonlinux.org||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
</pre>}}

Note that you can use the following command to optimise the order of the mirrors in '''/etc/entropy/repositories.conf'''. This command pings the mirrors and, based on the response times, orders the mirrors in '''/etc/entropy/repositories.conf''' accordingly:

For the '''Daily''' repository, use:
{{Console| <pre class="clear"># equo repo mirrorsort sabayonlinux.org</pre>}}

For the '''Weekly''' repository, use:
{{Console| <pre class="clear"># equo repo mirrorsort sabayon-weekly</pre>}}

And for the '''testing''' repository, use:
{{Console| <pre class="clear"># equo repo mirrorsort sabayon-limbo</pre>}}

'''Testing repositories:'''
''These can break your system, only add them when you really know what you are doing.''
{{Console| <pre class="clear"># Limbo
repository = sabayon-limbo|Sabayon Limbo Testing Repository|http://cerberus.itti.ifce.edu.br/entropy|http://pkg.sabayon.org,sabayon.org
repository = sabayon-limbo||http://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository = sabayon-limbo||http://ftp.rnl.ist.utl.pt/pub/sabayon ftp://ftp.rnl.ist.utl.pt/pub/sabayon|
repository = sabayon-limbo||http://mirror.internode.on.net/pub/sabayonlinux/entropy|
repository = sabayon-limbo||ftp://mirror.aarnet.edu.au/pub/SabayonLinux/entropy|
repository = sabayon-limbo||http://cross-lfs.sabayonlinux.org/entropy|
repository = sabayon-limbo||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
</pre>}}

=== Community Repositories ===

{{main|Community Repositories}}

Community Repositories are user-managed packages repositories. Users can recompile packages with different settings, add their own ones and make all available to other people. Repository publishers are responsible for how a package is compiled and what is compiled.

== Masking and Unmasking Packages in Entropy ==

You can find the files to edit in '''/etc/entropy/packages/'''.
* Use '''package.mask''' to mask a file, see '''package.mask.example''' for more information.
* Use '''package.unmask''' to unmask a file. See '''package.unmask.example''' for more information.


==Adding Additional Packages Manually==
[https://packages.sabayon.org/ Sabayon Linux Package Repository]

You can download packages and place them in the package directory for Entropy to use. See [[FAQ#Where_does_Entropy_download_the_packages_to.3F|Where to Put Packages]]

==Fresh Install - What to do?==
So you just installed a fresh copy of Sabayon Linux and are wondering what to do next.

The first thing to do is of course learn how to use the Entropy package manager. It is vital to know your package manager. So read first, then do.

===Using Entropy to upgrade all installed packages===

Now that you have learned about the Entropy package manager, let's get our package list for the package manager current. You will have to be root to use the commands, so open a terminal and enter '''su''' with the root password and, if you did it correctly, your prompt will change to a hash symbol (#) to show you are now logged in as the root user. '''DO NOT use sudo'''.
{{Console| <pre class="clear"># equo update</pre>}}

If you run into problems with that then try:
{{Console| <pre class="clear"># equo update --force</pre>}}

Next, as mentioned in the section above, it is a good idea to optimize the sorting of mirrors so that all package upgrades will be downloaded as quickly as possible:
{{Console| <pre class="clear"># equo repo mirrorsort sabayon-weekly</pre>}}

Once you have that completed it is vital to get Entropy upgraded to the latest version before doing a full system upgrade. Upgrade will bring your system to current development.
{{Console| <pre class="clear"># equo install entropy rigo equo --relaxed
# equo conf update</pre>}}

Once the Entropy code is upgraded to the latest version, fully upgrade the rest of your system with these two commands:
{{Console| <pre class="clear"># equo update
# equo upgrade --ask</pre>}}

Follow what is happening on the screen, as Entropy will show you what it is going to do and ask for confirmations.
* The 'equo update' command will update the database on your PC with the latest information on packages available in the Entropy repositories;
* the 'equo upgrade' command will download from the repositories the binary files for new versions of packages installed on your PC and then install the new versions of those packages.

Time of process depends on how many packages, bandwidth and hardware. After it is done, make sure to:
{{Console| <pre class="clear"># equo conf update</pre>}}

You will want to make your selection but you really should get to know your config files as they will change your system. More than likely most will select -5. I always look over the config files as I don't want some of my configs getting overwritten.

The final step is to run the following commands, checking for missing dependencies and stability:

{{Console| <pre class="clear"># equo deptest
# equo libtest</pre>}}

After this has finished, reboot and enjoy your freshly installed fully updated Sabayon.

{{Note|The equo upgrade command does not upgrade the kernel if a new version happens to be available in the Entropy repository. If you want to install a newer version of the kernel then you must:
# install the newer kernel manually using equo;
# ensure that the symbolic link to the kernel sources is pointing to the correct version of the kernel sources (by using the 'eselect kernel' command);
# install the corresponding kernel modules manually using equo;
# ensure that the correct OpenGL implementation for your video driver is selected (by using the 'eselect opengl' command);
# ensure the new kernel is included in the menu in grub.conf (SL 5.1-r1 and earlier) or grub.cfg (SL 5.2 and onwards).}}

What about using [[Sulfur]]? I do not recommend using Sulfur for the initial upgrade. Equo is 100x's more reliable and you won't end up with the issues that Sulfur can cause. So do your initial installation with Equo then look at using Sulfur or even better Rigo after that.

==The kernel==

===Misunderstandings about the kernel===
Some people have a lot of questions about the kernel., Questions like:

I installed kernel 3.8.5. but still, "uname -a" is showing 3.8.0

or

I want to customize kernel 3.8.5 , but /usr/src only shows 3.8.0

Well, let me explain that:

Every version of the kernel is followed by little updates., called "patchlevel" ., indicated by the third number.

So, 3.7.4 is just a update to the 3.7 serie. , just as 3.8.3 is a update to the 3.8 serie.

Uname -a or -r ,

cat /proc/version,

eselect kernel and eselect bzimage

/usr/src

and even the kernelline in grub.cfg

are ALL using the BASE notation of the kernel., and NOT it's updates. that stays "0" , Allthough you ARE running it.

(3.5.0) (3.6.0) (3.7.0) etc.

So, when you choose 3.7.0 in GRUB, or "eselect kernel" , or whatever, and kernel 3.7.4 is installed.,

(you can check that with command: equo query installed "linux-sabayon" )

in fact you ARE booting with 3.7.4 (only not showed), and you can assure yourself that it is.....

===Upgrading the Linux kernel===

{{Note|'''Entropy should never call a new kernel by itself, unless you're already running 3.7 for example. But then it's a update: r1, r2, etc.'''
However in some cases, like VirtualBox is known to install a new kernel when installing VirtualBox.
You can bypass that by doing:

equo install virtualbox.bin --nodeps

as described in the wiki.
Entropy itself will never just install a new kernel. This is mostly invoked by other packages, such as VirtualBox, or if the user explicitly invokes it.}}
For detailed instructions on updating the kernel using Entropy use the following link:
* [[HOWTO:_Upgrade_kernel_using_Entropy|How to upgrade the kernel using Entropy]]

The kernel image is not upgraded automatically; you have to upgrade it manually. You install a new version of the kernel image as you would any other package, i.e. using either the equo command or Rigo. For example, if you currently have the 3.6-r3 kernel image installed on your PC and version 3.7-r3 is available in the Entropy repositories then you can install the new version by entering the command:
{{Console|<pre class="clear"># equo install sys-kernel/linux-sabayon-3.7-r3</pre>}}

Once you have installed a new version of the kernel image you must install the relevant modules your PC requires, which have been compiled specifically for that version of the kernel image. When you do this, you must specify the full package name, including the kernel version, of the modules.

For example, if you had just installed the 3.7.0 kernel image (the Entropy package sys-kernel/linux-sabayon-3.7.0) then you would have to install the relevant modules for it like so:
{{Console|<pre class="clear"># equo install x11-drivers/ati-drivers-12.10#3.7.0-sabayon</pre>}}

If you do not include the "#3.7.0-sabayon" in the package name then, if the ati-drivers-12.10 package for an earlier version of the kernel happens to be in the repositories, it would be installed/re-installed instead of the module you need.

The above example assumes you are using the closed-source FGLRX driver for an AMD GPU, but the same principle applies if you are using an NVIDIA closed-source driver with an NVIDIA GPU, or if you are using any other software that is a kernel module (VirtualBox modules are another example).

You must also use the 'eselect kernel' command to make the symbolic link to the kernel sources point to the new version of the kernel sources, and you must use the 'eselect opengl' command to select the correct OpenGL implementation for your video driver. The Entropy kernel image package will take care of upgrading the Grub2 grub.cfg file to include the new kernel image in the Grub menu.

The instructions above assume you are upgrading to a later version of the kernel, but are equally applicable if you are downgrading to an earlier version of the kernel.

=== Using Kernel Switcher ===

'''kernel-switcher''' is an easy-to-use tool to simplify upgrading the kernel in Sabayon Linux. Remember, doing regular upgrades will not upgrade the kernel: you need to invoke a kernel change. This is done to prevent users from breaking their system and then screaming in the forums or in irc.

{{Console| <pre class="clear">
# kernel-switcher --help
>> kernel-switcher - Sabayon Linux Kernel Switcher BETA
>> switch kernel: kernel-switcher switch <kernel package>
>> list kernels: kernel-switcher list
>> this help: kernel-switcher help
</pre>}}

The '''kernel-switcher list''' command is a nice feature, but can be overwhelming as it lists all kernels currently available in the repository. You may prefer to use '''equo search linux-sabayon''' as ''linux-sabayon'' is the Sabayon kernel package. With '''equo search linux-sabayon''' you can see if any newer kernels exist. For example, if you find that ''linux-sabayon-3.8.0'' is available as an upgrade, you would upgrade to it as follows:

{{Console| <pre class="clear">
# kernel-switcher switch linux-sabayon-3.8.0
>> @@ Calculating dependencies …
>> ## [U] [sabayonlinux.org] sys-kernel/linux-firmwares-3.8.0|0 [3.8.0|0]
>> ## [N] [sabayonlinux.org] sys-kernel/linux-sabayon-3.8.0|0
>> ## [N] [sabayonlinux.org] net-wireless/broadcom-sta-5.100.82.38-r1#3.8.0-sabayon|0
>> ## [N] [sabayonlinux.org] x11-drivers/nvidia-drivers-260.19.29#3.8.0-sabayon|0
</pre>}} 

Notice it pulls the new kernel plus new versions of kernel modules/drivers that are currently installed. Let it download and install everything needed for the new kernel. Once this is done, GRUB 2 will reflect the change so that, when you reboot, the new kernel is available to select. A few other things need to be done before you reboot: Sometimes the OpenGL libraries get reset and the user finds video is not working properly, so you need to check and set them back:

{{Console| <pre class="clear">
# eselect opengl list

Available OpenGL implementations:
[1] nvidia *
[2] xorg-x11
</pre>}}

In the above example the asterisk indicates that the ''nvidia'' OpenGL libraries are selected, which I do need. If it was set to ''xorg-x11'', I would use the following command to select the closed-source OpenGL libraries:

{{Console| <pre class="clear"># eselect opengl set 1</pre>}}

Another thing to check is the symlink to the kernel:

{{Console| <pre class="clear">
# eselect kernel list

Available kernel symlink targets:
[1] linux-3.7.0-sabayon
[2] linux-3.8.0-sabayon *
</pre>}}

Great, it's set to the new kernel. Since you are using GRUB, maybe there's no point(?), but you can as well issue

{{Console| <pre class="clear"># eselect bzimage list</pre>}}

and make sure your newest kernel is selected. Otherwise you can select it by issuing

{{Console| <pre class="clear"># eselect bzimage set <NUMBER></pre>}}

where <NUMBER> stands for the number of the desired kernel in the previous list. E.g:

{{Console| <pre class="clear"># eselect bzimage set 2</pre>}}

It is also worth running the both commands:

{{Console| <pre class="clear">
# equo deptest
# equo libtest
</pre>}}

This will make sure things are proper. Once that is complete, reboot to your new kernel.

== Using Portage to upgrade the Entropy code ==

{{Warning|'''emerge and layman are Portage commands, Portage is not our package manager but is available to advanced users. Any steps using these commands can be safely ignored.'''}}

We changed the overlay to git now, so for Sabayon Linux version < 4.1 version you need to do the following:
{{Note|This step is optional but recommended.}}

{{Console| <pre class="clear">
# layman -d sabayon
# layman -d sabayon-distro
# layman -L
# layman -a sabayon
# layman -a sabayon-distro
</pre>}}

'''If''' it complains about not having git installed, then do:

{{Console| <pre class="clear"># equo install dev-vcs/git</pre>}}

You should also update the Portage package list in case you need to use Portage to install the latest version of Entropy if you run into trouble upgrading Entropy using the Entropy commands listed earlier. This step is optional but, if you have problems getting Entropy working, you will need to perform this step to get the latest version of Entropy from the Sabayon Portage overlays.

{{Console| <pre class="clear"># emerge --sync && layman --sync sabayon && layman --sync sabayon-distro</pre>}}

If you get an error message that the Sabayon overlays do not exist then you need to add them:

{{Console| <pre class="clear">
# layman --add sabayon
# layman --add sabayon-distro
</pre>}}

{{Note|The first emerge --sync is a little time consuming, but it's a one-time deal.}}

Now, if you have problems getting the equo update to function or problems getting latest Entropy installed, you can use emerge to get the latest version instead. Follow below for how to install Entropy via Portage:

{{Console| <pre class="clear"># emerge entropy equo rigo</pre>}}

Hopefully now you are ready to start the upgrading process:

{{Console| <pre class="clear"># equo upgrade --ask</pre>}}

Before you reboot you should check some things first: [http://forum.sabayon.org/viewtopic.php?f=76&t=16399 Please look at this thread to see what I mean]. There can be critical things to take care of first before you can safely reboot. Generally it's not a big issue, but a kernel change does require some additional work. You will need to reinstall your drivers/modules to match the kernel.

Make sure you also grab the kernel sources:
{{Console| <pre class="clear"># equo install sabayon-sources</pre>}}

You should also keep your Portage ebuild list updated from time to time, just to be safe. You don't have to do it daily, but maybe once a week.

{{Note|You do not have to do this step at all, until or unless you run into problems.}}

The following step only speeds up the process later by wasting the time doing it now:

{{Console| <pre class="clear"># emerge --sync && layman --sync sabayon && layman --sync sabayon-distro</pre>}}

If you get an error message that the Sabayon overlays do not exist then you need to add them:

{{Console| <pre class="clear">
# layman --add sabayon
# layman --add sabayon-distro
</pre>}}

==Hopping Branches==

{{Note|Since branch 5, Sabayon Linux became a 'Rolling Release', so 'hopping' is not needed anymore. Just upgrade the system as stated above.
The following is '''only''' for people running branch 4.2, 4.1, or 4.}}

Switching branches is as easy as typing equo hop [branch], replace the [branch] with the one you want to hop to. So let's say we are using Sabayon Linux 4.2 and want to jump to branch 5, all we have to do is:

{{Console| <pre class="clear"># equo hop 5</pre>}}

Now we need to update our package list with new branch:

{{Console| <pre class="clear"># equo update</pre>}}

Always get the latest package manager first:

{{Console| <pre class="clear"># equo install entropy equo rigo --relaxed</pre>}}

Now you are ready to start your upgrade:

{{Console| <pre class="clear"># equo upgrade</pre>}}

There could be many packages involved with this and can be time consuming so plan a head for this before doing it. Also see thread http://forum.sabayon.org/viewtopic.php?f=54&t=16399 for some good learning on things you will need to check.

Update your config files when done with upgrade:

{{Console| <pre class="clear"># equo conf update</pre>}}

Before rebooting:
* check your kernel with 'eselect kernel list' and make sure it is correct latest kernel selected, it will have the * next to it.
* check gcc version with 'gcc-config -l' and make sure it is on latest one
* check 'binutils-config -l' and make sure it's set
* check 'eselect opengl list' for right driver
* check '''/boot/grub/grub.conf''' to make sure it updated properly
* check 'eselect python list' and make sure it's set to the latest one

Do not ever go backwards with your branches, meaning, don't go from Branch 5 back to Branch 4.

==Testing Branch / Rolling Releases==
=== Warning - Read first ===
{{Warning|'''This branch of Entropy is dangerous. Read this section from beginning to end before doing anything with it.'''}}

Let us quickly go through the most common factors that make running the testing branch impractical:
* A good amount of experience with Portage and related tools is crucial to fix problems that are likely to arise when using the testing branch. Reporting problems encountered on this branch is good and helps with the Sabayon development process, but it is not a way for you to get a fix quickly. Only Portage is likely to do that for you.
* Solid understanding of Linux (OS including programs) is highly important, too. You can expect to be confronted with new configuration options and non-trivial problems. You will need pretty extensive knowledge to either diagnose and solve, or work around these problems, at a point in time when they have little to no distribution-specific documentation yet - sometimes not even any good documentation at all.
* High maintenance - just to explicitly state the other consequence of the two points directly above.
* High bandwidth consumption - there are some package upgrades almost every day, and the amount of upgrades can easily hit a few hundred MB every week.

{{Note|Don't forget, that there's a 5 TB constraint for Sabayon Linux' servers - and the upkeep costs a pretty penny. So if you don't interested in improving packages in the testing branch, please consider the economic aspect, too.}}

If you have any doubt about meeting one or more of the criteria outlined before, but need or want to use the testing branch / rolling releases anyway, '''it is strongly recommended that you make use of some virtualization software (and its snapshotting features), rather than deploying the testing branch in your main installation'''. That way, if some operation goes wrong, you typically won't need to resolve any issues, but can just revert to the last working snapshot - which will in turn allow you to try a more selective operation, or simply defer the operation until later. Modern virtualization software can interact fairly nicely with the host, like displaying windows as if they were part of the host, or share files between host and guest, so this should be the way to go even if you need the most recent version of some program in day-to-day use.

'''Basically use it on your own risk, don't blame us if anything breaks and your system doesn't work since its unsupported at this stage. We did tell you about the risks and what is good to think over before adding the limbo repo.'''

=== Setting it up ===

You can add this to /etc/entropy/repositories.conf:
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayon.org|http://pkg.sabayon.org#bz2

Our next release is from packages that are put into the Limbo Repository. This will keep you rolling consistently all the time. This prevents the large amount of packages that hops cause. You will run into bugs/issues at times, but they are usually sorted pretty quickly.

So after adding that line you can then simply do:

{{Console| <pre class="clear">
# equo update
# equo upgrade
</pre>}}

How often you do it is up to you. Once a day or once a week, whatever works for you.

=== Adding Entropy Mirror ===

The file to edit: /etc/entropy/repositories.conf

You may notice a big slowdown with Entropy and the Limbo Repo, so please add this mirror under your existing Limbo line:

{{File|/etc/entropy/repositories.conf| <pre class="clear">
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayonlinux.org/entropy|http://pkg.sabayonlinux.org
</pre>}}

so it should look like:

{{File|/etc/entropy/repositories.conf| <pre class="clear">
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayonlinux.org/entropy|http://pkg.sabayonlinux.org
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://na.mirror.garr.it/mirrors/sabayonlinux/entropy/|http://na.mirror.garr.it/mirrors/sabayonlinux/entropy#bz2
</pre>}}

Now you should have good speeds again. '''You may have to put a # in front of the top one to force equo to use garr only.''' For example:

{{File|/etc/entropy/repositories.conf| <pre class="clear">
# repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayonlinux.org/entropy|http://pkg.sabayonlinux.org
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://na.mirror.garr.it/mirrors/sabayonlinux/entropy/|http://na.mirror.garr.it/mirrors/sabayonlinux/entropy#bz2
</pre>}}

Another thing you can do is make it look like:

{{File|/etc/entropy/repositories.conf| <pre class="clear">
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayonlinux.org/entropy|http://pkg.sabayonlinux.org
repository|sabayon-limbo||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
</pre>}}

You will still get the update db from pkg site, but it should download the packages from garr. I leave the choice up to you.

En:Entropy

2013-03-30T14:08:36Z

Aposteeltje: /* Upgrading the Linux kernel */

{{I18n| [[Ca:Entropy|ca]] [[De:Entropy|de]] [[En:Entropy|en]] [[Es:Entropy|es]] [[Fr:Entropy|fr]] [[It:Entropy|it]] [[Pl:Entropy|pl]] [[Pt:Entropy|pt]] [[Ru:Entropy|ru]] [[Tr:Entropy|Tr]]}}

{{Note|There is no requirement to use the '''sudo''' command in Sabayon Linux. Use the '''su''' command to log-in to the root user's account, perform the steps listed, then type '''exit''' to log-out from the root user's account when you have finished. Where stated in this article, you must use this method. A hash (#) prompt indicates you are logged-in as the root user; a dollar ($) prompt indicates you are logged-in under your own account.}}

==Notices==
Mandatory Entropy upgrade for all versions of Sabayon Linux below 5.2: [[Known_Issues#02.2F12.2F10_Mandatory_Entropy_Update_and_Wireless_KDE4.4|Mandatory Entropy Update and Wireless KDE 4.4]]

URL changes for all versions of Sabayon Linux below 5.2: [[Known_Issues#03.2F16.2F10_URL_Change_for_Entropy_Repository|URL Change for Entropy Repository]]

==About Entropy==
[[Image:Entropy_logo.png|thumb|The Entropy Project Logo]]
Entropy is the name of the Sabayon Linux binary package management system. This is the name for the complete infrastructure, composed by [[Equo]] client (textual), [[Sulfur]] and Rigo client (graphical), Reagent and Activator server applications.

Sabayon is based on Gentoo's testing branch, which is about on par with Debian Sid releases. Entropy takes packages from Gentoo testing and they are pre-compiled, then offered to you in binary form. There is a time delay from when Sabayon compiles these packages for Entropy and when you receive them. It is recommended to only use 1 of the package managers(either Entropy or Portage) to avoid any possible conflicts as a result of the time delay. Generally, Entropy packages will be slightly more stable because they will have already been released in Gentoo testing for a period of time(exact amount of time varies), prior to being released in Entropy.

Some highlights:
* Gentoo Linux compatible (caution, mixing entropy and portage is for advanced users)
* Takes the best from Portage, Yum and APT
* Fast as lightning
* SQLite-powered (embedded)
* Smart and User-centric
* Powerful Packages: multiple packages inside one single archive (Smart Packages)
* Supports self-contained applications (Smart Applications)
* Backward Compatible Packages: they can be used in Gentoo Linux after a quick conversion
* Multiple branches support (each branch is a release version)
* Database corruptions aware: rescue and system health scanning tools included
* Easy to deploy and use in a Network Environment
* Multiple repositories aware: everyone can create one
* Extensible and Human Understandable API
* Strongest Artificial Intelligence (Entropy has a brain)
* Great sense of humour, and much more...

===What are the main goals of Entropy?===
There were multiple reasons that led Entropy creation:
*Providing better efficiency, extraordinary speed, less power consumption to Sabayon Linux systems, making Sabayon one of the TOP leading Linux distributions.
*Unlock Gentoo to resource-constrained hardware or where CPU power shouldn't be wasted by compilers.
*Provide an easy and modern way to handle a Gentoo-based system while keeping independent from Portage codebase and at the same time being 100% compatible.
*Providing a higher grade of AI in package managers arena: Entropy guesses users' needs and acts accordingly.
*Proposing a new Point of View for developers: Web 2.0 revolution applied to package managers, being Desktop-wise, user-friendly and bringing new ideas for a key component of a Linux desktop system.

== Installing Entropy ==

{{Note| Currently, the releases supporting Entropy are: '''Sabayon Linux 3.5 and above.'''}}

There are 2 supported ways to install Entropy: either using the Sabayon Linux Portage overlay, or by using Equo itself. This is possible as all versions of Sabayon Linux after 3.5 come with Entropy installed by default. It is recommended to use Entropy with all current Sabayon releases.

{{Note|Installing Entropy in Gentoo Linux or in any other release is not supported officially although it is possible.}}

=== Upgrading Entropy using Equo ===

As of version 3.5 of Sabayon, Entropy has been included by default. To upgrade it to the latest (and greatest) version, open a terminal (such as Konsole in KDE or Terminal in GNOME) and enter the commands shown below.

1. Become root (enter the root password when prompted):
{{Console| <pre class="clear">$ su</pre>}}
2. Update the Equo Database:
{{Console| <pre class="clear"># equo update</pre>}}
That will update the database to the latest version.

3. Download and install the latest version of Entropy:
{{Console| <pre class="clear"># equo install entropy rigo</pre>}}
4. To test it's working, run:
{{Console| <pre class="clear"># equo --version</pre>}}
If you get a version number such as:
entropy: 180
equo: 180
Then it has installed and is working!

=== Installing Entropy using Portage ===

{{Warning|'''emerge and layman are Portage commands, Portage is not our package manager but is available to advanced users. Any steps using these commands can be safely ignored.'''}}

Installing via Portage can be completed using the procedure listed below. Open a terminal (such as konsole) and enter the commands:

1. Become root (enter the root password when prompted):
{{Console| <pre class="clear">$ su</pre>}}
2. Update the Sabayon overlays to the latest versions:
{{Console| <pre class="clear"># layman --sync sabayon
# layman --sync sabayon-distro</pre>}}
If you get an error message that the overlays do not exist then you need to add them:
{{Console| <pre class="clear"># layman --add sabayon
# layman --add sabayon-distro</pre>}}

3. Emerge Entropy, Equo and Rigo to install the latest versions:
{{Console| <pre class="clear"># emerge entropy equo rigo</pre>}}
4. To test it's working, run:
{{Console| <pre class="clear"># equo --version</pre>}}
If you get a version number such as:
entropy: 180
equo: 180
Then it has installed and is working!

==Packages Entropy Downloads==
Packages are downloaded and stored in '''/var/lib/entropy/client/packages/''' For instance on amd64 using Branch 5 they are stored in '''/var/lib/entropy/client/packages/packages/amd64/5'''

You can use the command below to clean them up:
{{Console| <pre class="clear"># equo cleanup</pre>}}

== About Equo, the Commandline package Manager ==

[[Image:Equo--help_ouput.png|thumb|400px|Equo in Action]]

{{main|Equo}}

Equo is the command line client-side application for the Entropy package management system, and should be always performed as Root. It is capable of installing, removing and updating packages, resolving dependences, reverse dependency handling and configuration file handling and that's just to start with.

=== Basic Usage ===

There are several options you can use when using Equo, a few of the basic commands are shown below.

Searching for a package can be accomplished by running the equo search command:
{{Console| <pre class="clear"># equo search <package name></pre>}}
To install a package use the install function, the --ask amendment is optional but recommended.
{{Console| <pre class="clear"># equo install <package> --ask</pre>}}
To remove a package use the remove function as shown below:
{{Console| <pre class="clear"># equo remove <package> --ask</pre>}}
To upgrade all your packages to the latest versions use this command:
{{Console| <pre class="clear"># equo upgrade --ask</pre>}}
As you can see from the examples above, the "--ask" amendment is optional, but highly recommended, as it not only gives you more information about the packages being installed, but also the dependencies that may come with them, giving you more control about what is going to be installed, followed by a confirmation/abortion of the command.

=== List Of Equo Functions ===

For a detailed list of the equo functions, you can always enter:
{{Console| <pre class="clear"># equo --help</pre>}}
or
{{Console| <pre class="clear"># man equo</pre>}}
at the commandline, or view them here:
[[En:List Of Equo Functions]]

== Rigo, the Graphical package Manager ==

{{Note|Although still available, Sulfur has been replaced by [[Rigo]].}}

{{Warning|'''Sulfur is (yet) still available in the Repositories, but is no longer developed and will most likely NOT work anymore!!!'''}}

[[Sulfur]] was the (old) GUI (Graphical User Interface) to [[Equo]], the Sabayon Linux Binary Package Manager.
Sulfur will no longer exist in the future so [[Rigo]] will be the new and improved GUI package manager for entropy store.

=== Rigo ===

[[Image:Rigo.png|thumb|400px|The Rigo user interface]]

Rigo is the improved graphical replacement for [[Sulfur]].

=== Features ===

* "google search" like interface
* very simple and straight forward
* Rigo is faster and more responsive
* append the various packages by browsing
* easy manage repositories
* show list of pending configuration files to update
* and many more!

=== Usage ===

For a detailed usage guide, please visit the [[Rigo]] page which contains a visual walk-through of all the features.

==Package Repositories==
===What are Package Repositories===
Repositories are a storage location from which software packages may be retrieved and installed on a computer. Sabayon's Repositories contain over 10,000 different packages per architecture (x86/x86_64).

=== Why are there all these repositories? ===

Sabayon offers 4 official repositories but by default you only use one of them.

* '''sabayon-hell'''
Not a place you want to be really. This repository is used by our [http://en.wikipedia.org/wiki/Build_system build system] "Matter". The Entropy repository team carefully made lists of packages that could always be updated once a new version gets released in Portage. The build system does nothing more then work down this list and add the packages here. Since they are NOT checked by humans we can never know if the work that was done by the build system is actually what we wanted it to be.
Each monday the Entropy team evaluates what Matter did and moves these packages to sabayon-limbo (testing) repository.

* '''sabayon-limbo'''
This is the testing repository. All packages that are compiled and packaged are pushed in this repository. Work on this repository goes on 24/7.
While all packages that land here are tested at compilation phase, it is possible they have problems while running them. If you enable this repository keep in mind that things can break, you receive more updates because packages get recompiled and repackaged if needed.

{{Warning|Please note that the sabayon-limbo is an overlay repo, you MUST keep sabayonlinux.org repo enabled!
Otherwise you will have missing dependencies.}}

* '''sabayonlinux.org'''
This is the repository mostly refered to as "main". Every monday most, if not all, packages from sabayon-limbo (testing) get moved into this one.

* '''sabayon-weekly'''
This is by default the only enabled repository. It is a copy of sabayonlinux.org (main) repository. Every saturday night it gets renewed.
This repository was introduced to build in a delay between when packages get moved from testing and are available for all users. This gives packagers additional time to test packages in the main repository and fix issues if any before the copy is made.

=== How can I enable a different repository? ===

In ''/etc/entropy/repositories.conf'' you find the general configuration that count for all repositories. The different repositories are inherited from a subdirectory: ''/etc/entropy/repositories.conf.d''

In this subdirectory you'll find some predefined examples for the different repositories.

If you see that some example files are missing, then please read section: [[En:Repositories]]

Example how to enable sabayonlinux.org:
{{Console| <pre class="clear">
# cd /etc/entropy/repositories.conf.d
# mv entropy_sabayonlinux.org.example entropy_sabayonlinux.org
# equo update
</pre>}}

If you later wish to disable this repository:
{{Console| <pre class="clear"># equo repo disable sabayonlinux.org</pre>}}

{{Warning|'''Do not combine sabayon-weekly with sabayon-limbo!'''}}

If you only have sabayon-limbo and sabayon-weekly enabled you will at some point get into a situation where a previously updated package taken from sabayon-limbo wants to downgrade to the version from weekly again. Why does this happen?

As described above packages move from sabayon-limbo into sabayonlinux.org. If you do not have that repository enabled the package manager will fallback on the version it can find, the one in sabayon-weekly. This will cause unwanted downgrades and maybe breakages at some point.

=== Updating Package Repositories ===

To update the database of all packages in the repositories in your '''/etc/entropy/repositories.conf''', run (as root):
{{Console| <pre class="clear"># equo update</pre>}}

Use the same file to add additional repositories. Currently what is in the '''repositories.conf''' file is all that is available.

=== Available Repositories mirrors ===

'''Production repositories:'''
{{Console| <pre class="clear"># Sabayon Linux Official Repository
repository|sabayonlinux.org|Sabayon Linux Official Repository|http://cerberus.itti.ifce.edu.br/entropy|http://pkg.sabayon.org,sabayon.org
repository|sabayonlinux.org||http://riksun.riken.go.jp/pub/pub/Linux/sabayon/entropy|
repository|sabayonlinux.org||http://ftp.sh.cvut.cz/MIRRORS/sabayon/entropy|
repository|sabayonlinux.org||http://ftp2.cz.freebsd.org/pub/sabayon/entropy|
repository|sabayonlinux.org||http://debian.mirror.dkm.cz/sabayon/entropy|
repository|sabayonlinux.org||http://mirror.us.sabayon.org/sabayon/entropy|
repository|sabayonlinux.org||http://mirror.umoss.org/sabayonlinux/entropy|
repository|sabayonlinux.org||ftp://ftp.klid.dk/sabayonlinux/entropy|
repository|sabayonlinux.org||http://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository|sabayonlinux.org||ftp://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository|sabayonlinux.org||http://mirrors.cs.wmich.edu/sabayon/entropy|
repository|sabayonlinux.org||http://ftp.surfnet.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository|sabayonlinux.org||ftp://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository|sabayonlinux.org||http://ftp.cc.uoc.gr/mirrors/linux/SabayonLinux/entropy|
repository|sabayonlinux.org||http://mirror.dun.nu/sabayonlinux/entropy|
repository|sabayonlinux.org||http://ftp.rnl.ist.utl.pt/pub/sabayon ftp://ftp.rnl.ist.utl.pt/pub/sabayon|
repository|sabayonlinux.org||http://mirror.internode.on.net/pub/sabayonlinux/entropy|
repository|sabayonlinux.org||http://cross-lfs.sabayonlinux.org/entropy|
repository|sabayonlinux.org||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
</pre>}}

Note that you can use the following command to optimise the order of the mirrors in '''/etc/entropy/repositories.conf'''. This command pings the mirrors and, based on the response times, orders the mirrors in '''/etc/entropy/repositories.conf''' accordingly:

For the '''Daily''' repository, use:
{{Console| <pre class="clear"># equo repo mirrorsort sabayonlinux.org</pre>}}

For the '''Weekly''' repository, use:
{{Console| <pre class="clear"># equo repo mirrorsort sabayon-weekly</pre>}}

And for the '''testing''' repository, use:
{{Console| <pre class="clear"># equo repo mirrorsort sabayon-limbo</pre>}}

'''Testing repositories:'''
''These can break your system, only add them when you really know what you are doing.''
{{Console| <pre class="clear"># Limbo
repository = sabayon-limbo|Sabayon Limbo Testing Repository|http://cerberus.itti.ifce.edu.br/entropy|http://pkg.sabayon.org,sabayon.org
repository = sabayon-limbo||http://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository = sabayon-limbo||http://ftp.rnl.ist.utl.pt/pub/sabayon ftp://ftp.rnl.ist.utl.pt/pub/sabayon|
repository = sabayon-limbo||http://mirror.internode.on.net/pub/sabayonlinux/entropy|
repository = sabayon-limbo||ftp://mirror.aarnet.edu.au/pub/SabayonLinux/entropy|
repository = sabayon-limbo||http://cross-lfs.sabayonlinux.org/entropy|
repository = sabayon-limbo||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
</pre>}}

=== Community Repositories ===

{{main|Community Repositories}}

Community Repositories are user-managed packages repositories. Users can recompile packages with different settings, add their own ones and make all available to other people. Repository publishers are responsible for how a package is compiled and what is compiled.

== Masking and Unmasking Packages in Entropy ==

You can find the files to edit in '''/etc/entropy/packages/'''.
* Use '''package.mask''' to mask a file, see '''package.mask.example''' for more information.
* Use '''package.unmask''' to unmask a file. See '''package.unmask.example''' for more information.


==Adding Additional Packages Manually==
[https://packages.sabayon.org/ Sabayon Linux Package Repository]

You can download packages and place them in the package directory for Entropy to use. See [[FAQ#Where_does_Entropy_download_the_packages_to.3F|Where to Put Packages]]

==Fresh Install - What to do?==
So you just installed a fresh copy of Sabayon Linux and are wondering what to do next.

The first thing to do is of course learn how to use the Entropy package manager. It is vital to know your package manager. So read first, then do.

===Using Entropy to upgrade all installed packages===

Now that you have learned about the Entropy package manager, let's get our package list for the package manager current. You will have to be root to use the commands, so open a terminal and enter '''su''' with the root password and, if you did it correctly, your prompt will change to a hash symbol (#) to show you are now logged in as the root user. '''DO NOT use sudo'''.
{{Console| <pre class="clear"># equo update</pre>}}

If you run into problems with that then try:
{{Console| <pre class="clear"># equo update --force</pre>}}

Next, as mentioned in the section above, it is a good idea to optimize the sorting of mirrors so that all package upgrades will be downloaded as quickly as possible:
{{Console| <pre class="clear"># equo repo mirrorsort sabayon-weekly</pre>}}

Once you have that completed it is vital to get Entropy upgraded to the latest version before doing a full system upgrade. Upgrade will bring your system to current development.
{{Console| <pre class="clear"># equo install entropy rigo equo --relaxed
# equo conf update</pre>}}

Once the Entropy code is upgraded to the latest version, fully upgrade the rest of your system with these two commands:
{{Console| <pre class="clear"># equo update
# equo upgrade --ask</pre>}}

Follow what is happening on the screen, as Entropy will show you what it is going to do and ask for confirmations.
* The 'equo update' command will update the database on your PC with the latest information on packages available in the Entropy repositories;
* the 'equo upgrade' command will download from the repositories the binary files for new versions of packages installed on your PC and then install the new versions of those packages.

Time of process depends on how many packages, bandwidth and hardware. After it is done, make sure to:
{{Console| <pre class="clear"># equo conf update</pre>}}

You will want to make your selection but you really should get to know your config files as they will change your system. More than likely most will select -5. I always look over the config files as I don't want some of my configs getting overwritten.

The final step is to run the following commands, checking for missing dependencies and stability:

{{Console| <pre class="clear"># equo deptest
# equo libtest</pre>}}

After this has finished, reboot and enjoy your freshly installed fully updated Sabayon.

{{Note|The equo upgrade command does not upgrade the kernel if a new version happens to be available in the Entropy repository. If you want to install a newer version of the kernel then you must:
# install the newer kernel manually using equo;
# ensure that the symbolic link to the kernel sources is pointing to the correct version of the kernel sources (by using the 'eselect kernel' command);
# install the corresponding kernel modules manually using equo;
# ensure that the correct OpenGL implementation for your video driver is selected (by using the 'eselect opengl' command);
# ensure the new kernel is included in the menu in grub.conf (SL 5.1-r1 and earlier) or grub.cfg (SL 5.2 and onwards).}}

What about using [[Sulfur]]? I do not recommend using Sulfur for the initial upgrade. Equo is 100x's more reliable and you won't end up with the issues that Sulfur can cause. So do your initial installation with Equo then look at using Sulfur or even better Rigo after that.

==The kernel==

===Misunderstandings about the kernel===
Some people have a lot of questions about the kernel., Questions like:

I installed kernel 3.8.5. but still, "uname -a" is showing 3.8.0

or

I want to customize kernel 3.8.5 , but /usr/src only shows 3.8.0

Well, let me explain that:

Every version of the kernel is followed by little updates., called "patchlevel" ., indicated by the third number.

So, 3.7.4 is just a update to the 3.7 serie. , just as 3.8.3 is a update to the 3.8 serie.

Uname -a or -r ,

cat /proc/version,

eselect kernel and eselect bzimage

/usr/src

and even the kernelline in grub.cfg

are ALL using the BASE notation of the kernel., and NOT it's updates. that stays "0" , Allthough you ARE running it.

(3.5.0) (3.6.0) (3.7.0) etc.

So, when you choose 3.7.0 in GRUB, or "eselect kernel" , or whatever, and kernel 3.7.4 is installed.,

(you can check that with command: equo query installed "linux-sabayon" )

in fact you ARE booting with 3.7.4 (only not showed), and you can assure yourself that it is.....

===Upgrading the Linux kernel===

{{Note|'''Entropy should never call a new kernel by itself, unless you're already running 3.7 for example. But then it's a update: r1, r2, etc.'''
However in some cases, like VirtualBox is known to install a new kernel when installing VirtualBox.
You can bypass that by doing:

equo install virtualbox.bin --nodeps

as described in the wiki.
Entropy itself will never just install a new kernel. This is mostly invoked by other packages, such as VirtualBox, or if the user explicitly invokes it.}}
For detailed instructions on updating the kernel using Entropy use the following link:
* [[HOWTO:_Upgrade_kernel_using_Entropy|How to upgrade the kernel using Entropy]]

The kernel image is not upgraded automatically; you have to upgrade it manually. You install a new version of the kernel image as you would any other package, i.e. using either the equo command or Rigo. For example, if you currently have the 3.6-r3 kernel image installed on your PC and version 3.7-r3 is available in the Entropy repositories then you can install the new version by entering the command:
{{Console|<pre class="clear"># equo install sys-kernel/linux-sabayon-3.7-r3</pre>}}

Once you have installed a new version of the kernel image you must install the relevant modules your PC requires, which have been compiled specifically for that version of the kernel image. When you do this, you must specify the full package name, including the kernel version, of the modules.

For example, if you had just installed the 3.7.0 kernel image (the Entropy package sys-kernel/linux-sabayon-3.7.0) then you would have to install the relevant modules for it like so:
{{Console|<pre class="clear"># equo install x11-drivers/ati-drivers-12.10#3.7.0-sabayon</pre>}}

If you do not include the "#3.7.0-sabayon" in the package name then, if the ati-drivers-12.10 package for an earlier version of the kernel happens to be in the repositories, it would be installed/re-installed instead of the module you need.

The above example assumes you are using the closed-source FGLRX driver for an AMD GPU, but the same principle applies if you are using an NVIDIA closed-source driver with an NVIDIA GPU, or if you are using any other software that is a kernel module (VirtualBox modules are another example).

You must also use the 'eselect kernel' command to make the symbolic link to the kernel sources point to the new version of the kernel sources, and you must use the 'eselect opengl' command to select the correct OpenGL implementation for your video driver. The Entropy kernel image package will take care of upgrading the Grub2 grub.cfg file to include the new kernel image in the Grub menu.

The instructions above assume you are upgrading to a later version of the kernel, but are equally applicable if you are downgrading to an earlier version of the kernel.

=== Using Kernel Switcher ===

'''kernel-switcher''' is an easy-to-use tool to simplify upgrading the kernel in Sabayon Linux. Remember, doing regular upgrades will not upgrade the kernel: you need to invoke a kernel change. This is done to prevent users from breaking their system and then screaming in the forums or in irc.

{{Console| <pre class="clear">
# kernel-switcher --help
>> kernel-switcher - Sabayon Linux Kernel Switcher BETA
>> switch kernel: kernel-switcher switch <kernel package>
>> list kernels: kernel-switcher list
>> this help: kernel-switcher help
</pre>}}

The '''kernel-switcher list''' command is a nice feature, but can be overwhelming as it lists all kernels currently available in the repository. You may prefer to use '''equo search linux-sabayon''' as ''linux-sabayon'' is the Sabayon kernel package. With '''equo search linux-sabayon''' you can see if any newer kernels exist. For example, if you find that ''linux-sabayon-3.8.0'' is available as an upgrade, you would upgrade to it as follows:

{{Console| <pre class="clear">
# kernel-switcher switch linux-sabayon-3.8.0
>> @@ Calculating dependencies …
>> ## [U] [sabayonlinux.org] sys-kernel/linux-firmwares-3.8.0|0 [3.8.0|0]
>> ## [N] [sabayonlinux.org] sys-kernel/linux-sabayon-3.8.0|0
>> ## [N] [sabayonlinux.org] net-wireless/broadcom-sta-5.100.82.38-r1#3.8.0-sabayon|0
>> ## [N] [sabayonlinux.org] x11-drivers/nvidia-drivers-260.19.29#3.8.0-sabayon|0
</pre>}} 

Notice it pulls the new kernel plus new versions of kernel modules/drivers that are currently installed. Let it download and install everything needed for the new kernel. Once this is done, GRUB 2 will reflect the change so that, when you reboot, the new kernel is available to select. A few other things need to be done before you reboot: Sometimes the OpenGL libraries get reset and the user finds video is not working properly, so you need to check and set them back:

{{Console| <pre class="clear">
# eselect opengl list

Available OpenGL implementations:
[1] nvidia *
[2] xorg-x11
</pre>}}

In the above example the asterisk indicates that the ''nvidia'' OpenGL libraries are selected, which I do need. If it was set to ''xorg-x11'', I would use the following command to select the closed-source OpenGL libraries:

{{Console| <pre class="clear"># eselect opengl set 1</pre>}}

Another thing to check is the symlink to the kernel:

{{Console| <pre class="clear">
# eselect kernel list

Available kernel symlink targets:
[1] linux-3.7.0-sabayon
[2] linux-3.8.0-sabayon *
</pre>}}

Great, it's set to the new kernel. Since you are using GRUB, maybe there's no point(?), but you can as well issue

{{Console| <pre class="clear"># eselect bzimage list</pre>}}

and make sure your newest kernel is selected. Otherwise you can select it by issuing

{{Console| <pre class="clear"># eselect bzimage set <NUMBER></pre>}}

where <NUMBER> stands for the number of the desired kernel in the previous list. E.g:

{{Console| <pre class="clear"># eselect bzimage set 2</pre>}}

It is also worth running the both commands:

{{Console| <pre class="clear">
# equo deptest
# equo libtest
</pre>}}

This will make sure things are proper. Once that is complete, reboot to your new kernel.

== Using Portage to upgrade the Entropy code ==

{{Warning|'''emerge and layman are Portage commands, Portage is not our package manager but is available to advanced users. Any steps using these commands can be safely ignored.'''}}

We changed the overlay to git now, so for Sabayon Linux version < 4.1 version you need to do the following:
{{Note|This step is optional but recommended.}}

{{Console| <pre class="clear">
# layman -d sabayon
# layman -d sabayon-distro
# layman -L
# layman -a sabayon
# layman -a sabayon-distro
</pre>}}

'''If''' it complains about not having git installed, then do:

{{Console| <pre class="clear"># equo install dev-vcs/git</pre>}}

You should also update the Portage package list in case you need to use Portage to install the latest version of Entropy if you run into trouble upgrading Entropy using the Entropy commands listed earlier. This step is optional but, if you have problems getting Entropy working, you will need to perform this step to get the latest version of Entropy from the Sabayon Portage overlays.

{{Console| <pre class="clear"># emerge --sync && layman --sync sabayon && layman --sync sabayon-distro</pre>}}

If you get an error message that the Sabayon overlays do not exist then you need to add them:

{{Console| <pre class="clear">
# layman --add sabayon
# layman --add sabayon-distro
</pre>}}

{{Note|The first emerge --sync is a little time consuming, but it's a one-time deal.}}

Now, if you have problems getting the equo update to function or problems getting latest Entropy installed, you can use emerge to get the latest version instead. Follow below for how to install Entropy via Portage:

{{Console| <pre class="clear"># emerge entropy equo rigo</pre>}}

Hopefully now you are ready to start the upgrading process:

{{Console| <pre class="clear"># equo upgrade --ask</pre>}}

Before you reboot you should check some things first: [http://forum.sabayon.org/viewtopic.php?f=76&t=16399 Please look at this thread to see what I mean]. There can be critical things to take care of first before you can safely reboot. Generally it's not a big issue, but a kernel change does require some additional work. You will need to reinstall your drivers/modules to match the kernel.

Make sure you also grab the kernel sources:
{{Console| <pre class="clear"># equo install sabayon-sources</pre>}}

You should also keep your Portage ebuild list updated from time to time, just to be safe. You don't have to do it daily, but maybe once a week.

{{Note|You do not have to do this step at all, until or unless you run into problems.}}

The following step only speeds up the process later by wasting the time doing it now:

{{Console| <pre class="clear"># emerge --sync && layman --sync sabayon && layman --sync sabayon-distro</pre>}}

If you get an error message that the Sabayon overlays do not exist then you need to add them:

{{Console| <pre class="clear">
# layman --add sabayon
# layman --add sabayon-distro
</pre>}}

==Hopping Branches==

{{Note|Since branch 5, Sabayon Linux became a 'Rolling Release', so 'hopping' is not needed anymore. Just upgrade the system as stated above.
The following is '''only''' for people running branch 4.2, 4.1, or 4.}}

Switching branches is as easy as typing equo hop [branch], replace the [branch] with the one you want to hop to. So let's say we are using Sabayon Linux 4.2 and want to jump to branch 5, all we have to do is:

{{Console| <pre class="clear"># equo hop 5</pre>}}

Now we need to update our package list with new branch:

{{Console| <pre class="clear"># equo update</pre>}}

Always get the latest package manager first:

{{Console| <pre class="clear"># equo install entropy equo rigo --relaxed</pre>}}

Now you are ready to start your upgrade:

{{Console| <pre class="clear"># equo upgrade</pre>}}

There could be many packages involved with this and can be time consuming so plan a head for this before doing it. Also see thread http://forum.sabayon.org/viewtopic.php?f=54&t=16399 for some good learning on things you will need to check.

Update your config files when done with upgrade:

{{Console| <pre class="clear"># equo conf update</pre>}}

Before rebooting:
* check your kernel with 'eselect kernel list' and make sure it is correct latest kernel selected, it will have the * next to it.
* check gcc version with 'gcc-config -l' and make sure it is on latest one
* check 'binutils-config -l' and make sure it's set
* check 'eselect opengl list' for right driver
* check '''/boot/grub/grub.conf''' to make sure it updated properly
* check 'eselect python list' and make sure it's set to the latest one

Do not ever go backwards with your branches, meaning, don't go from Branch 5 back to Branch 4.

==Testing Branch / Rolling Releases==
=== Warning - Read first ===
{{Warning|'''This branch of Entropy is dangerous. Read this section from beginning to end before doing anything with it.'''}}

Let us quickly go through the most common factors that make running the testing branch impractical:
* A good amount of experience with Portage and related tools is crucial to fix problems that are likely to arise when using the testing branch. Reporting problems encountered on this branch is good and helps with the Sabayon development process, but it is not a way for you to get a fix quickly. Only Portage is likely to do that for you.
* Solid understanding of Linux (OS including programs) is highly important, too. You can expect to be confronted with new configuration options and non-trivial problems. You will need pretty extensive knowledge to either diagnose and solve, or work around these problems, at a point in time when they have little to no distribution-specific documentation yet - sometimes not even any good documentation at all.
* High maintenance - just to explicitly state the other consequence of the two points directly above.
* High bandwidth consumption - there are some package upgrades almost every day, and the amount of upgrades can easily hit a few hundred MB every week.

{{Note|Don't forget, that there's a 5 TB constraint for Sabayon Linux' servers - and the upkeep costs a pretty penny. So if you don't interested in improving packages in the testing branch, please consider the economic aspect, too.}}

If you have any doubt about meeting one or more of the criteria outlined before, but need or want to use the testing branch / rolling releases anyway, '''it is strongly recommended that you make use of some virtualization software (and its snapshotting features), rather than deploying the testing branch in your main installation'''. That way, if some operation goes wrong, you typically won't need to resolve any issues, but can just revert to the last working snapshot - which will in turn allow you to try a more selective operation, or simply defer the operation until later. Modern virtualization software can interact fairly nicely with the host, like displaying windows as if they were part of the host, or share files between host and guest, so this should be the way to go even if you need the most recent version of some program in day-to-day use.

'''Basically use it on your own risk, don't blame us if anything breaks and your system doesn't work since its unsupported at this stage. We did tell you about the risks and what is good to think over before adding the limbo repo.'''

=== Setting it up ===

You can add this to /etc/entropy/repositories.conf:
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayon.org|http://pkg.sabayon.org#bz2

Our next release is from packages that are put into the Limbo Repository. This will keep you rolling consistently all the time. This prevents the large amount of packages that hops cause. You will run into bugs/issues at times, but they are usually sorted pretty quickly.

So after adding that line you can then simply do:

{{Console| <pre class="clear">
# equo update
# equo upgrade
</pre>}}

How often you do it is up to you. Once a day or once a week, whatever works for you.

=== Adding Entropy Mirror ===

The file to edit: /etc/entropy/repositories.conf

You may notice a big slowdown with Entropy and the Limbo Repo, so please add this mirror under your existing Limbo line:

{{File|/etc/entropy/repositories.conf| <pre class="clear">
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayonlinux.org/entropy|http://pkg.sabayonlinux.org
</pre>}}

so it should look like:

{{File|/etc/entropy/repositories.conf| <pre class="clear">
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayonlinux.org/entropy|http://pkg.sabayonlinux.org
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://na.mirror.garr.it/mirrors/sabayonlinux/entropy/|http://na.mirror.garr.it/mirrors/sabayonlinux/entropy#bz2
</pre>}}

Now you should have good speeds again. '''You may have to put a # in front of the top one to force equo to use garr only.''' For example:

{{File|/etc/entropy/repositories.conf| <pre class="clear">
# repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayonlinux.org/entropy|http://pkg.sabayonlinux.org
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://na.mirror.garr.it/mirrors/sabayonlinux/entropy/|http://na.mirror.garr.it/mirrors/sabayonlinux/entropy#bz2
</pre>}}

Another thing you can do is make it look like:

{{File|/etc/entropy/repositories.conf| <pre class="clear">
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayonlinux.org/entropy|http://pkg.sabayonlinux.org
repository|sabayon-limbo||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
</pre>}}

You will still get the update db from pkg site, but it should download the packages from garr. I leave the choice up to you.

En:FAQ

2013-03-07T22:34:46Z

Aposteeltje: /* How do I update everything at once? */

{{I18n| [[Ca:FAQ|ca]] [[En:FAQ|en]] [[Es:FAQ|es]] [[It:FAQ|it]]}}

=FAQs=

=='''General Questions regarding Sabayon Linux'''==
===What is Sabayon Linux===
Sabayon Linux is a pre-configured distribution with the tenets of Performance, Versatility, and Stability, based on the source-based distribution named Gentoo Linux, a particularly customizable distribution. If you have other questions on Gentoo and its philosophy, I request you visit their website: http://gentoo.org. 
In particular, Sabayon emanates substantially from Gentoo's testing branch, one of the most popular source-based Linux distributions, which is about on par with Debian's unstable branch called Sid. Though based on the bleeding edge, you will find Sabayon is quite stable and perhaps more cutting edge than many. Although both Sabayon and Gentoo are rolling releases, Sabayon will have release snapshots. 

===How is Sabayon Linux maintained?===
As Ubuntu uses some of the packages from Debian, so Sabayon receives its packages from Gentoo. 
Sabayon, when using the package manager "Entropy" is binary based. Currently Sabayon has about 10,000 packages in Entropy. And when Sabayon is using the package manager "Portage", it is source based. The Gentoo repository is quite huge. 

===What is the difference between source-based and binary based distribution?===
Most distros, such as Ubuntu, Debian, Red Hat, Fedora and SUSE, install binary packages. Simply put, a binary package is the pre-compiled program, compiled on another computer and made available for download and installation on other computers. 
A source-based distro is one that compiles its programs from source code on the target computer at the time of installation, rather than relying on others to compile and package them. Source-based distros generally also have in their repositories some binary (pre-compiled) packages; these will be the large programs such as LibreOffice, the reason being that the compilation of these can take several hours. 
'''overlays'''
* Overlay: We have our own Portage overlay for ebuilds. Ebuilds are script files that contain instructions for the Portage package manager on how to install the package from its source code.
* Performance: We have modified the Portage make.conf file in order to ensure that our distribution will run at higher speed on newer computers and as fast as possible on older computers.
* Variability: Again, we have modified make.conf in order to cater to a wide spectrum of hardware, using the x86 and amd64 (x86_64) processor architectures.
* Entropy: We have a binary manager that can be used as the one, unique package manager. It functions also with Portage so that you can use them both if you are an experienced user. The Entropy binary packages are ready-built and can be installed immediately without the need to compile anything from the source code.
* The main branch of Gentoo is considered Gentoo stable. Sabayon is based on Gentoo's testing branch.
* Sabayon has different versions ready for quick and pain free installation. The Gentoo installation is done from the ground up, relying on you to make all the configuration choices.
* Gentoo has '''use''' flags. Sabayon will ignore '''use''' flags when using Entropy, but will apply the '''use''' flags when using portage. 

===Why choose Sabayon Linux ?===
1. Variety
Sabayon has multiple editions to choose from. From a variety of desktops to a variety of packages and installations that can enjoyed by new linux users as well as by power users who prefer a higher level of customization.
2. Sabayon is a rolling release.
Once installed you should not need to reinstall a new updated version, since you can use the update tools. Entropy is a GUI tool and front-end for the text console based Equo. This allows you to have the latest and greatest packages available to you, at all times.
3. The Anaconda installer.
The Anaconda installer in Sabayon greatly simplifies installation including disk partition setup and disk encryption, if desired or required.
4. Choice of package managers and repositories.
Sabayon's package manager Entropy is binary and currently contains about 10,000 packages in its repositories. Gentoo's package manager Portage is source based and has a quite huge repo.
5. Support.
Sabayon is highly active and well maintained. You can find help through our forums, live help, and the ever-growing wiki.
6. Look and feel.
Sabayon is generally considered one of the more visually attractive Linux distros. From the installer, to the desktops, and even down to the terminal which has a useful color scheme applied to make any work on the command line pleasing to the eye and easy to understand.
7. Using Sabayon helps to save the world
Test results have shown that using Sabayon Linux '''improves''' the economy; '''helps''' reduce global warming; is generally '''good''' for the environment; '''promotes''' world peace; and helps to fight off '''alien invasive''' species from other galaxies. It is also shown to be helpful in '''improving''' the health of your sense of '''humor''', which is important to keep from bashing your head on the key board during difficult moments. (Test results have been claimed to vary, but number 7 is considered an attempt at '''humor'''.) 

===Should I use Sabayon as a source-based or binary based distribution?===
Sabayon Linux has two package managers: [[Entropy]] (binary packages) and Portage (source packages). As you can install binary packages instead of source code-based packages, Sabayon Linux offers users a choice and the best of both worlds. The binary packages in the Entropy repository have been built by using the Portage package manager and then packaged using Entropy packaging tools on that computer. The binary packages are stored in the Entropy repository and you install them on your computer by using either the [[Equo]] command line client or the [[Rigo]] GUI client. As the release time and date of packages are a little different between the 2 package managers it is recommended to use one package manager consistently to avoid conflicts.

Generally, using Entropy with binary packages is recommended to new users and those who just want everything to work easily.

Portage(source based) is recommended for more advanced users who wish to customize their installation to a higher degree.

There are two main advantages to source-based distributions:
# Firstly, source-based distros often have the newest software before binary distros do. This is due mainly to the fact that rather than having to compile a package and then test it on different machines, all that is required in Sabayon Linux is a file telling it where to find the source code and how to compile it.
#Secondly, undoubtedly a program will eventually have a feature you don't need, and will just take up space or slow down the program. In a binary distro, you're stuck with this feature. In a source-based distro you have the option of removing unwanted features at the time of compilation (assuming you are using Portage rather than Entropy). 

===System Requirements===
* '''Live Environment - No 3D Desktop''':
** ''i686'' Processor
** at least ''512 MB'' of RAM (1 GB suggested)
** a ''2D'' graphics card
** a ''[http://en.wikipedia.org/wiki/Display_Data_Channel DDC] capable Monitor''
** ''mouse'' and ''keyboard''

* '''Live Environment - 3D Desktop''':
** ''i686'' Processor (starting from AMD K6 and Intel Pentium II)
** at least ''512 MB'' of RAM (1 GB suggested)
** an '''[http://en.wikipedia.org/wiki/OpenGL OpenGL] capable 3D graphics card''' (mostly NVIDIA, ATI, Intel, VIA)
** a ''[http://en.wikipedia.org/wiki/Display_Data_Channel DDC] capable Monitor''
** ''mouse'' and ''keyboard''

* '''Installation''':
{{Note| Please note that the Requirements indicated for Installation may be a bit too low for some Desktop Environments.
A full KDE Desktop for example, CAN run with only 1 GB RAM, but you will most likely run out of memory during a session, especially when running large programs, such as firefox, thunderbird and/or libreoffice. Please keep that in mind.}}
** ''i686'' Processor
** at least ''512 MB'' of RAM (1 GB suggested for decent eyecandy effects)
** an '''[http://en.wikipedia.org/wiki/OpenGL OpenGL] capable 3D graphics card''' (mostly NVIDIA, ATI, Intel, VIA)
** ''20'' GB of free space, that is bare minimum DVD Install. ''30+'' GB is highly recommended.
** ''8 GB'' of free space for miniCD. 10+ GB is recommended
** ''Internet connection'' (not mandatory but highly suggested)
** a ''[http://en.wikipedia.org/wiki/Display_Data_Channel DDC] capable Monitor''
** ''mouse'' and ''keyboard'' 

=== What Editions are available in Sabayon Linux? ===

Sabayon is all about choice. You have many flavors to choose from.

You can download them from the mirrors, here:
* [http://www.sabayon.org/mirrors Sabayon Mirrors Page]

The following choices are the main releases available in 32Bit (x86) or 64Bit (amd64):
{{Note| "amd64" is also suitable for '''Intel''' based 64bit Processors}}
1. KDE
2. Gnome
3. LXDE
4. MATE
5. XFCE
6. Enlightenment
All of the above mentioned Desktop Environments are fully-featured.

7. CoreCDX
CoreCDX is a minimal install for those wishing to configure the system more to their liking,
(for more advanced users) in 32bit or 64bit., and uses the Fluxbox Window Manager.

=== How can I contribute to, or support Sabayon Linux ===
There are several ways to contribute:

* The Sabayon foundation is always looking for funds.
For more information, see: http://www.sabayon.org/donate
* Translations.
We are always looking for translators. For the Wiki, as well as translating Sabayon into your native language. 

You may subscribe to our wonderful Wiki, and translate the articles into your own Language, or write your own articles about some area of working with Gnu/Linux. 

If you want to translate Sabayon into your own language, please see:
[[En:HOWTO: Translate Sabayon]] 

If you want to translate the Wiki articles into your own language, please see:
[[En:Translations]] and [[Editing_Guidelines]] 

* Subscribe to our Forum
Help out others with problems. Perhaps problems you've had once too, 
and know the answer or a solution.
http://forum.sabayon.org/ 

* Join us on Facebook or Google+
There are lots of Discussions going on on facebook and Google+. Want to help out, or participate? 
https://www.facebook.com/groups/36125411841/ 
https://plus.google.com/+sabayon/posts 

*setup more download mirrors
We need more mirrors! 

Check out this link to learn more about what it takes to mirror the Sabayon Linux project.
http://wiki.sabayon.org/index.php?title=Mirroring_Sabayon 

=='''The liveCD/DVD'''==
===Should I get the 32-bit or the 64-bit edition?===
This is a never-ending, debatable question. For new users, 32-bit is easier to operate as 64-bit may be a bit fussier. Everything should work in 64-bit as the 32-bit version. Keep in mind that you are still using mostly 32-bit applications. The average desktop user is not going to see benefits over the 32-bit. I suggest to people to try both and see for themselves. In my experience I see most new people picking the 32-bit version. You can certainly Google for more information on this debate.
64bit would seem to be the direction things are going in, though most applications are still in 32bit. 64bit has gotten more support these days and become more widespread in use. 64bit is currently more secure, however most 64bit systems use multi libraries. multi libraries allow you to use both 64 and 32bit apps. A 64bit system using multi libraries will have a certain amount of vulnerability as a 32 bit system.

===Can I install without having to burn the ISO to CD or DVD?===
Yes, you can [http://www.sabayonlinux.org/forum/viewtopic.php?f=50&t=12023 install if you don't have a CD or DVD burner.] Another way, if your computer can boot USB pen drives, is to use UNetbootin or similar to install the Sabayon Linux ISO to a pen drive and create a bootable pen drive (think of it as a fast LiveCD/DVD). Then you can boot the pen drive to get to a Live desktop, and install Sabayon Linux from there, just as you would from a LiveCD/DVD.

=== burning / checking the .iso image ===

One of the most common problems with burning a Linux install CD/DVD is that people sometimes don't understand that an iso image file is not a normal file. You cannot just burn the iso to disc to and expect it to work. I repeat: '''you cannot simply put the iso file on a blank disk and expect it to work'''. In order to properly make a CD or DVD out of an iso image, you need special software. Instructions for Nero and Isorecorder are included; for other programs, see the manual for the software, or just give one of these a shot.

With Nero you just select file and burn image, then select the .iso file you want to burn. The software handles the rest.

If you're looking for a good, alternative freeware solution, you can download a free image burner.

isorecorder [http://isorecorder.alexfeinman.com/isorecorder.htm] Simply download and install the correct version for your version of windows, then right click on the .iso and tell it to burn.

=== checking the integrity of the burned disc ===

Many people know they can check if a downloaded ISO file is OK by comparing the md5sum of the ISO file against the md5sum posted on the SL mirrors. For example:

{{Console| <pre class="clear">
# md5sum -c SabayonLinux-x86_64-3.4f.iso.md5
SabayonLinux-x86_64-3.4f.iso: OK
</pre>}}

cf. the contents of ftp://bo.mirror.garr.it/mirrors/sabayonlinux/SabayonLinux-x86_64-3.4f.iso.md5 which are:
645600788920443b372baae3544acffa SabayonLinux-x86_64-3.4f.iso

so the ISO I downloaded was good.

Remember - verify the MD5 sum for the version of Sabayon that you downloaded - they are all different. The MD5s can be found on the mirrors listed at: http://www.sabayonlinux.org/mirrors

But a different method is needed to verify the '''integrity''' of the LiveDVD/CD itself. You should select the verify written data checkbox in K3b before burning the DVD/CD, but if you forgot or still have doubts then the following method can be used to check the integrity of the burnt LiveDVD/CD:

If you only have Windows installed on your HDD, apparently you can use a Windows shareware application, see the following Web page for details:
http://www.mepis.org/docs/en/index.php?title=Checking_the_integrity_of_a_Live_CD

A WARNING:

1. I have not checked if the method for Windows on the above-mentioned Web page actually works, so use it at your own risk.

Under Linux:

Insert the LiveDVD into the optical drive, let the disc spin up and then enter the following three commands:

{{Console| <pre class="clear">
md5sum /dev/cdrom | awk '{print $1}' > md5a.txt
md5sum ~/Sabayon_Linux_8_amd64_K.iso | awk '{print $1}' > md5b.txt
diff -qs md5a.txt md5b.txt
</pre>}}

(Obviously change the path and/or the ISO file name to match your circumstances.)

If you get an error message while the md5sum is reading the disc, there must be something wrong either with the burn or with the optical drive itself.

If you get the message "Files md5a.txt and md5b.txt differ" then the burn was bad.

If you get the message "Files md5a.txt and md5b.txt are identical" then the burn was good.

=== Passwords on live CD/DVD ===

* The root password:
no password is required: just press the Enter key.

* The sabayonuser password:
no password is required: just press the Enter key.

*For older releases (version 6 and earlier) the password for Root is "root" (without the quotes) and the password for Sabayonuser is "sabayonuser" (without the quotes).

=== The Booting process ===

The boot process of the liveCD/DVD should be pretty straight forwarded, just as many other Linux Distrtibutions.

However, you could get into problems, when having hardware that isn't supported by default, for example.

Or having old hardware that the current drivers don't support.

When having a old NVidia card, and you've downloaded the latest ISO, chances are that it will not start the Window Manager/Desktop Environment, but rather present you with a black screen.

There is nothing wrong with the ISO, it is because "nvidia-drivers-304.64" or higher is installed by default.

You can bypass that by hitting ctrl-alt-f1, remove the nvidia-drivers, (nouveau is installed too), and restart xdm., as explained below:

'''Removing latest nvidia-drivers:'''
# Press the "CTRL-ALT-F1" key combination.
"#" is just indicated that you have to be root, so do not include that with the actual commands...
{{Console| <pre class="clear"># su</pre>}}
{{Console| <pre class="clear"># equo remove nvidia-drivers --ask</pre>}}
Check that "x11-drivers/nvidia-drivers" got removed., nothing else... and confirm with "yes"

Restart XDM:
{{Console| <pre class="clear"># /etc/init.d/xdm restart</pre>}}

For a overall view of which cards support what driver., please see: http://www.nvidia.com/object/IO_32667.html

If you wish to be guided through the boot process and the several options it offers, we have a visual walkthrough.

Please see: [[Visual_Tour:_Boot-menu_Sabayon_LiveCD/DVD]]

Workarounds for problematic Hardware, during the boot process are discussed here:

[[Sabayon_Linux#Boot_parameters_and_workarounds_for_problematic_Hardware]]

'''cheatcodes for ATI and nVidia'''

ATI
noddc res=1024x768 refresh=60 opengl=ati
nVidia
noddc res=1024x768 refresh=60 opengl=nvidia

To use the cheatcodes, hit F5 on the boot up screen of the livecd/dvd and add one of the lines above pending on your hardware

see: [[Visual_Tour:_Boot-menu_Sabayon_LiveCD/DVD]]

When you need to edit xorg.conf, or have to create it for special reasons, the following visual tour will show you how to edit Xorg.conf:

[[Visual_Tour:_Part_2_Editing_the_xorg.conf]]

=='''After installation'''==

===What is Entropy or Equo?===
[[Entropy]] is the binary package manager of Sabayon Linux. To install binary packages you use either the command line client [[Equo]] or the newest Graphical GUI [[Rigo]].

A binary package is a file package containing the already-compiled files to install instead of having to compile the source code. Equo, and [[rigo]] handle these files.

===I just installed it, what do I do first?===
This question has always amazed me. Who says there is anything to do? How about just using the operating system and getting familiar with it? Take some time and read the documentation. If you insist on having to do something then emerge --sync && layman -S to update your Portage package list, or, if using Entropy, see [http://wiki.sabayonlinux.org/index.php?title=Entropy#Fresh_Install_-_What_to_do.3F Fresh Install]

===The GUI for managing packages===

[[rigo]] is the GUI for the Entropy package manager.

{{Warning|'''emerge and layman are Portage commands, Portage is not our own package manager but is available to advanced users. Any steps using these commands can be safely ignored'''}}

There are GUIs for the Portage package manager, but they are no substitute for using emerge on the command line.
* Currently we have Kuroo4, and porthole. Kuroo4 seems to be the best, but only available in Portage.
Personally if you have to rely on a GUI, then try to just use it as a browser of Portage, but still use the command line to install your packages. You will save yourself a lot of headaches. Search and gather your information needed with the GUI then open up Konsole or Terminal and install using the emerge command.

===How do I update/install packages?===
There are 2 package managers, Entropy and Portage. It is highly recommended that you choose and only use 1 package manager. Conflicts can arise from mixing both package managers.
Please read the [[Entropy]] page. Entropy is the package manager specially developed for Sabayon Linux. It has a command line interface ([[Equo]]) and a GUI interface ([[Sulfur]]). Equo commands and Sulfur GUI are Entropy and recommended for newer users of Sabayon Linux. Advanced users of Sabayon Linux may wish to use Portage, the package manager developed for Gentoo Linux, on which Sabayon Linux is based. For information on Portage, please read [[HOWTO: The Complete Portage Guide]].

===How do I install several packages?===
For Entropy:
{{Console| <pre class="clear"># equo install foo foo foo foo foo</pre>}}

For Portage:
{{Console| <pre class="clear"># emerge foo foo foo foo foo</pre>}}

The package manager will install each package one after another. Replace foo with actual package name.

===How do I search for a package?===
* For Entropy:
{{Console| <pre class="clear"># equo search foo</pre>}}
or use the [[rigo]] GUI, or on the Web:[http://packages.sabayon.org/ Sabayon Linux Web site's Entropy package search page].
* For Portage:
{{Console| <pre class="clear"># emerge -s foo</pre>}}
or use a GUI such as Kuroo4.
* Via [http://gentoo-portage.com/Browse Gentoo-Portage] or via [http://packages.gentoo.org/ Packages-Gentoo].

'''Using EIX'''
* For Portage:
I highly recommend using eix. It's the best tool you can have at your hands for searching. It is a command line tool, but it is very powerful and will tell you lots of information.
{{Console| <pre class="clear"># emerge eix && eix-update
# eix foo</pre>}}

You can use eix in Entropy too:
{{Console| <pre class="clear"># equo install eix && eix-update
# eix foo</pre>}}

Example output of eix gedit:
{{Console| <pre class="clear"> [I] app-editors/gedit
Available versions: 2.18.2-r1 2.20.3 (~)2.20.4 {acl debug doc python spell xattr}
Installed versions: 2.20.4(07:05:31 AM 12/29/2007)(python -debug -doc -spell -xattr)
Homepage: http://www.gnome.org/
Description: A text editor for the GNOME desktop</pre>}}
Eix has the ability to search Portage and all overlays. Simply edit the /etc/eix-sync.conf file and just add * to it
{{Console| <pre class="clear"># echo '*' >> /etc/eix-sync.conf</pre>}}
Then do:
{{Console| <pre class="clear"># eix-remote update</pre>}}
Now when you search, it will tell where and what overlay a package is in if it is not in the Portage main tree. This will widen your abilities to find packages, as overlays contain a lot of ebuilds too.

http://en.gentoo-wiki.com/wiki/Eix

===Can I emerge 2 packages at same time in Portage?===
Yes you can, but it can and will bog your system down. It's not really recommended.
===How do I update everything at once?===
For Entropy:
{{Console| <pre class="clear"># equo update
# equo upgrade
# equo conf update</pre>}}

See the Sabayon Wiki article [[Entropy]] for details.

{{Warning|'''emerge and layman are Portage commands. Portage is not our package manager but is available to advanced users. Any steps using these commands can be safely ignored'''}}

If you are new to this distro and have no understanding of Portage, we do not recommend this until you get to know how this distro works. This is one of the fastest ways to destroy your system. This distro is not like the other distros that have the big easy button update. For your information though, 'world update' is what Gentoo calls updating your entire system. It looks at your 'world file' and compares it to Portage and then proceeds to update all packages. Following is how:

{{Console| <pre class="clear"># emerge -- sync && layman -S
# emerge -ua world</pre>}}

* [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap3 Maintaining Software]
* [http://wiki.sabayon.org/index.php?title=HOWTO:_Unoffical_Guide_To_World_Update Unofficial Guide to World Update]
You've been warned. When you come yelling because your system won't boot, don't expect sympathy.

N.B. The term 'world' is not used in Entropy.

===How do I uninstall a package?===
* For Entropy:
{{Console| <pre class="clear"># equo remove foo</pre>}}
Note - this can remove dependencies.

*For Portage:
{{Console| <pre class="clear"> # emerge -C foo</pre>}}
Note - this will not remove the dependencies. You will need to run [http://en.gentoo-wiki.com/wiki/Gentoo_maintenance#depclean depclean] for that. I stress great caution with depclean, as it means what it says.

===How do I find out which packages depend on a certain package?===
{{Console| <pre class="clear"># equery depends foo</pre>}}
It will tell you all files depending on that package. See [http://www.gentoo.org/doc/en/gentoolkit.xml using gentoolkit] for more information and commands.

===I keep getting !!! ARCH is not set... Are you missing the 'etc/make.profile' symlink?===
In Konsole/Terminal use the '''su''' command to become the root user and then:
* Run the following command: '''eselect profile list'''
* Look for something like: '''default-linux/x86/2007.0/desktop''' and note the number in front of it.
* Then do: '''eselect profile set #''' <--replace the # with the number. In my case it would be '''eselect profile set 6'''
Now you should be good to go again.

===Do I have to download the LiveCD/DVD every time to upgrade?===
No, Sabayon is a rolling release. However in some cases upgrading via live DVD may prove more time efficent.

Entropy:
The equo command makes upgrading easy - see [[Entropy]].

Portage:
Portage is recommended for advanced users that prefer a higher degree of customization. That being said, Gentoo documentation is quite extensive and helpful for those wanting to dive into it.

Always backup your files before doing anything. My personal opinion: backup, fresh install, restore backup.

===How do I check for security updates ?===
It's pretty easy to keep your [http://www.gentoo.org/doc/en/security/security-handbook.xml?part=1&chap=14 system secure.]
Entropy does this for you automatically.

For Portage:
* Open up konsole or terminal and enter the command '''su''' to become the root user.
* Run the command '''glsa-check -t all''' to check your system.
* Then to fix, run '''glsa-check -f $(glsa-check -t all)'''

You can also visit our security wiki for more helpful tips:
* [http://wiki.sabayon.org/index.php?title=En:Security Sabayon Security wiki]

===How do I handle blocked packages?===
This is an issue in Portage. You are going to run into [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap4 packages blocking other packages.] This can happen for several reasons, e.g. a package has been dropped from Portage as it no longer exists or is no longer supported. In most cases you will simply have to remove (uninstall) the package that is blocking the new package. You will want to do some research on this first. Don't take Portage for granted and blindly do as it says without checking out what or why.

Note - latest versions of Portage (version 2.2 and higher) handle most blockages.

===How to handle masked packages?===
A package is complaining that it is [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap5 masked] and cannot install. This is one of those times you want to check why it is masked. A masked package is usually masked to prevent you from busting things. There are several ways a package can be masked. You can still install masked packages by unmasking them, but make sure you find out first why they are masked.

===How do I update the config files?===
As you install stuff, some packages are going to bring in new versions of their config files. These config files are important as they may have new settings for that package that need to be implemented. I stress that is is very, very crucial that you pay attention to these config files. You can change the entire outcome of your installation if you are not careful. Get to know your [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10863 config files.] There are several ways to handle these files:

For Entropy:
{{Console| <pre class="clear"># equo conf update</pre>}}

For Portage:
[http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=4#doc_chap1 dispatch-conf] and [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=4#doc_chap2 etc-update] are probably the most popular ways of handling updates to config files. A GUI tool is [http://etc-proposals.berlios.de/ etc-proposals.]

Please handle these files with care. You can't know these files enough.

===Where do I start to configure my system?===
For Entropy:
All packages are pre-configured remotely as they have been compiled on a remote computer. You do not need to (and cannot) do anything. If a package has been compiled without a specific USE flag that you need, then you will either have to request to the Entropy repository maintainers that the package be rebuilt (file a bug report in [http://bugs.sabayonlinux.org/ bugzilla]) and the new version placed in the Entropy repository, or use Portage to rebuild it yourself.

For Portage:
The file [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578 make.conf] is your heart and soul of your operating system. Learn it, edit it and build a lean, mean machine. Sabayon Linux ships with a generic make.conf that tries to support everything under the sun. You don't need all that stuff and by configuring, you will have lesser issues with Portage and conflicts.

===Where does Portage download the packages to?===
They are downloaded and stored in the directory '''/usr/portage/distfiles/'''

===Where does Entropy download the packages to?===
They are downloaded and stored in the directory '''/var/tmp/entropy/packages/'''
For instance, on my amd64 using Branch 4 they are stored in '''/var/tmp/entropy/packages/amd64/5'''

===How do I clean out Entropy downloaded packages?===

{{Console| <pre class="clear"># equo cleanup</pre>}}
See [http://wiki.sabayonlinux.org/index.php?title=En:List_Of_Equo_Functions Sabayon Wiki page of Equo commands] or equo --help --verbose

=='''Additional'''==
=== How do I get the Desktop Cube thing working?===
The desktop cube and 3D graphics do not work after I installed Sabayon Linux to the hard disk, but do work when I'm using the LiveCD/DVD.

Well, in theory what you see when you run the LiveCD/DVD is what you get when you install Sabayon Linux. So if the 3D desktop was working with the LiveCD/DVD then it should work when you boot your new installation. Well, we know all about theories; it doesn't work for everyone. You can either search in the Sabayon Linux Forums and the Sabayon Wiki for help on how to get the 3D desktop working with your particular model of graphics card, or you can ask in IRC #sabayon.

First thing you need to do: make sure the md5sum is good after you downloaded the .iso file, I can't stress that enough. Make sure you have burnt the CD/DVD as slowly as possible, and enable Burn Verify in your burning application.

You will be asked those two questions every time, so please do this so we don't have to waste bandwidth re-asking. It may seem petty to you to check the md5sum but, without knowing you're starting out with a good ISO file, it's pointless to continue. We can spend weeks troubleshooting and if your md5sum was bad, we just waste a lot of time and it causes a lot of frustration. With a bad md5sum you can still get a bootable working desktop, but may have issues elsewhere. So keep in mind, just because it boots, doesn't mean the ISO file is good. How do I check the md5sum and disk you ask? Well, luckily for you: [[HOWTO: Checking the integrity of a LiveCD or LiveDVD]].

OK, so you made sure the md5sum was good and you burnt the disk at a nice slow speed with Burn Verify enabled. Now we can start looking at other things. Do you have the correct video driver and the latest version of it? That will be the first thing to know.

NVIDIA card owners, the following link will save you hours of frustration. Yes, certain cards require certain drivers: http://en.gentoo-wiki.com/wiki/Nvidia. If you do not know or understand what is 'masking' then please read more (Portage users, see http://dev.gentoo.org/~dang/masked.txt. Entropy users, see [[Entropy#Masking_and_Unmasking_Packages_in_Entropy]].

Our Wiki also has a HowTo get NVIDIA and ATI cards working too, so use the relevant information: [[HOWTO: Get Ati or Nvidia Video Cards working in Sabayon]]. Also search the Sabayon Linux Forums for posts mentioning your card manufacturer and model.

The above method will work for most people, but you will find that maybe it didn't work for you. Why? I don't know. A little bit of research into /etc/X11/xorg.conf can usually resolve the remaining few that have problems. The following link is full of information for AIGLX: http://en.gentoo-wiki.com/wiki/AIGLX/Troubleshooting. Again, only use the information that is relevant. You will want to pay attention to the xorg.conf settings shown on that page and compare it to your xorg.conf so it matches.

Still having problems? Buy a new video card!

If you want to post your special way of how you got it working - please do. Mine just works all the time so I don't have such problems.

===Multimedia===
Does this include support for some privately-owned platforms? Yes, Sabayon Linux supports DVDs, MP3, WMA, AAC, DivX. Moreover, it supports a lot of open platforms, such as Ogg Vorbis, Matroska, Ogg Theora, FLAC, and coder-decoder Xvid.

===Games===
[http://www.sabayonlinux.org/forum/viewforum.php?f=43 Please Visit our Gaming Shed]

===AIGLX===
Q: Is AIGLX available?

A: If your graphics card is capable, then this should work out-of-the-box. If you are having trouble, start with the Gentoo Wiki article http://en.gentoo-wiki.com/wiki/AIGLX/Troubleshooting.

Q: In [[HOWTO: Get Ati or Nvidia Video Cards working in Sabayon]] it states that ATI GPUs can use AIGLX with the closed-source driver FGLRX. Is it feasible? Previously this worked only with XGL and open source DRI (direct giving infrastructure) Radeon driver.

A: AIGLX is supported by both the open-source Radeon driver and the closed-source FGLRX driver. N.B. Not all ATI cards are supported by the closed-source FGLRX driver and must use the Radeon driver. To find out if the closed-source driver supports your ATI card, see the release notes for the relevant version of the FGLRX driver (a.k.a. AMD Catalyst driver for Linux).

===3D Desktop/Compiz Questions===
'''The cube was working on LiveCD/DVD but doesn't on install, now what?'''

Well, now it's getting difficult as we need to [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=11723 check more things.] You will need the assistance of the Sabayon Linux Forum or IRC to help. I recommend you try and find the source of your problem first. When logged in, open a Konsole/Terminal window and type in the command fusion-icon and see what the error message is in the Konsole/Terminal. You will need to post that error message with your request for help. Make sure you have installed the latest video drivers for your video card also.

'''How do I update Compiz-Fusion to latest Dev. Version?'''

We have a [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=9882 guide on the forum] that is maintained to keep up with the changes in Compiz-Fusion development. This is for Portage users.

'''How do I know if my card will work with Compiz-Fusion?'''

We have a [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=8773 card list] that the community has reported on if their card works or not. It's not a complete list, but a good list to reference.

'''Where can I get more help on Compiz-Fusion?'''

I would suggest their [http://forum.compiz-fusion.org/ support forum.]

===How do I install KDE 4.x.x with Equo?===

{{Console| <pre class="clear"># equo install kde-meta-4.x.x</pre>}}

Replace the x's with the version of KDE you want to install.

===How Do I enable Autologin?===
The real question is, do you really want to? If yes, you should get a hammer and hit yourself in the head repeatedly. Logging in, especially logging in as user, not root, is a very basic but powerful security measure. Hostile programs cannot be autorun on your system if you log in as user. Also no one can accidently/purposefully find your collection of porn, google searches, or downloaded emails simply by pushing the power button if you set a user with password.
[http://wiki.sabayonlinux.org/index.php?title=En:HOWTO:_Setting_Up_Autologin Please see our Wiki page for how to do this.]

===How Do I change the positioning of notifications?===
By default the sabayon gnome version comes with [https://launchpad.net/notify-osd notify-osd]. This is developed by Canonical and
Mark Shuttleworth says the positioning won't be configurable [http://www.markshuttleworth.com/archives/265#comment-316838].
So if you want the notifications to appear in another corner you'll have to uninstall notify-osd and install [http://www.galago-project.org/news/index.php notification-daemon].
After that you will be able to configure the positioning with {{Console| $ notification-properties}}

===Networking Questions===
'''How do I find out what network card I have?'''

As root user, enter the command '''lspci''' in a Konsole or Terminal window. That will list hardware; look for your Ethernet controller.

'''How do I set-up my network?'''

Well, hopefully the LiveCD/DVD recognizes your network card, and NetworkManager sets your network up for you. If it doesn't, try running the command as root: simply '''su''' and run '''net-setup'''. You're going to want to consult the [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4 Gentoo Networking section.]

'''I can ping my router but can't access the Internet'''

You're probably having DNS issues. You need to edit the file /etc/resolv.conf and enter the correct DNS, then restart your network. If you don't know what to use for DNS, use 4.2.2.2

===Sound Questions===
'''I have no sound, what do I do?'''

* Let's see if you computer detects your sound card so, from a command line, use '''su''' to become root user, and run '''alsaconf''' - hopefully your card shows up and all you have to do is select and go.
* After running that, you can use '''alsamixer''' to adjust your sound settings. Press F6 to select your card in ALSAMixer and make sure no channels are muted and that the channel volumes are turned up.
* [http://wiki.sabayon.org/index.php?title=HOWTO:_Resolve_Problems_with_HDA-Intel_Sound_Cards If you have HDA-Intel Card, Please see this HowTo]

'''How can I determine what sound card I have?'''

As root user run the command '''lspci | grep -i audio'''

'''How do I install the alsa-driver instead of having it in the kernel?'''

Sabayon Linux comes with ALSA built into the kernel. You can't install the alsa-drivers while ALSA is built into the kernel. You have to remove ALSA from the kernel before you install the alsa-driver package. So use the '''su''' command to become the root user, and then enter the following commands:

{{Console| <pre class="clear">
# cd /usr/src/linux
# make menuconfig
# make && make modules_install
# cp arch/i386/boot/bzImage /boot/kernel_name <--replace kernel_name with the actual name of kernel
</pre>}}

* Reboot

{{Console| <pre class="clear">
# emerge alsa-driver
</pre>}}
* More info: [http://www.gentoo.org/doc/en/alsa-guide.xml Gentoo ALSA Guide.]

'''Why do I have to run alsaconf every time I reboot?'''

This usually happens if you have more than one sound card in your machine. Many people have an on-board sound card and then stick in a better sound card. Disable your on-board sound card via your BIOS and when you run alsaconf again, ALSA will restore your sound each time you reboot.

===Video Questions===
'''My NVIDIA card is a legacy card, what driver do I need?'''

You will need to compare your card with the information below to find out which driver is best for your card:
* [http://en.gentoo-wiki.com/wiki/Nvidia Check out the Nvidia Howto]
* [http://www.gentoo.org/doc/en/nvidia-guide.xml Also the Nvidia Guide]

'''I need help with my AMD/ATI card!'''

I don't have ATI so I can't supply much help here, but I can point you to:
* [http://en.gentoo-wiki.com/wiki/Graphics_drivers#AMD.2FATI Howto Ati Drivers]
* [http://www.gentoo.org/doc/en/ati-faq.xml Gentoo FAQ on ATI]

===How do I setup AIGLX with my ATI?===
* [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=12438 HOWTO AIGLX with ATI and Sabayon 3.5]

'''How do I setup Dual Monitors?'''

Personally I use twin view and it works great with Compiz-Fusion also. Check out the [http://en.gentoo-wiki.com/wiki/Dual_Monitors Gentoo Wiki article X.Org/Dual Monitors]

'''Video Worked on LiveCD/DVD, but not once install. Options?'''

If your video was fine on the LiveCD/DVD I would boot the LiveCD/DVD and copy the xorg.conf from it to your hard drive install. There are several ways to do this.

* Option 1 - Boot up and browse to /etc/X11/ and copy the file xorg.conf to your installed version. You should be able to access your installed version through the /media directory so it may be something like /media/mydrive/etc/X11/ Reboot the computer and you should have what you had on the LiveCD/DVD. Always backup your files before overwriting.
* Option 2 - Boot up and browse to /etc/X11/xorg.conf and use something like http://www.pastebin.ca to paste your xorg.conf file there. Note the URL so that when you reboot to your installed version you can access it. Then just rename your existing xorg.conf and make a new one with the one you pasted.
* If you still don't have any luck, we may need to look at your drivers. Try reinstalling your video drivers, but, before reinstalling, make sure you are getting the latest drivers. NVIDIA users, make sure you are using the proper drivers for your card. See Question 1 under Video Questions.

===How do I know what Version of Sabayon I installed?===

{{Console| <pre class="clear">
# cat /etc/sabayon-release
</pre>}}
N.B. Sabayon Linux is a 'rolling release' distro. Therefore, if you have upgraded your installation via Entropy or Portage then your installation will no longer be the version recorded in /etc/sabayon-release, as that file tells you the version of the LiveCD/DVD that you used to install Sabayon Linux.

=='''Help and Support Questions'''==

'''How Do I get Log files to get better support?'''

With the package app-misc/sabayonlive-tools, you can easily gather important information to help you debug and provide vital information for the support team to help you. [http://forum.sabayonlinux.org/viewtopic.php?f=60&t=15530 Please see this thread to learn how].

'''Where Do I file a Bug Report?'''

Please use our [http://bugs.sabayonlinux.org/ bugzilla]

'''Where can I get help?'''

Are you lost and confused? There are a lot of great resources out there. I highly encourage you to do some searching first before running into IRC or the Forum and making the same post that has already been posted 100 times. It gets really old answering the same question day in and day out when it's so well documented.
* [http://www.sabayonlinux.org/forum/index.php Sabayon Linux Forum]
* [http://www.sabayonlinux.org/wiki/ Sabayon Linux Wiki]
* [http://www.gentoo.org/doc/en/handbook/index.xml Gentoo Handbook]
* [http://gentoo-wiki.com/Official_Gentoo_Documentation Official Gentoo Documentation]
* [http://gentoo-wiki.com/Main_Page Gentoo Wiki]
* [http://gentoo-portage.com/Browse Gentoo Portage]
* [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1 A Portage Introduction]
* irc.freenode.net in channel #Sabayon also on desktop Get Live Help -- note to IRC users, be human and have patience. Do not paste errors in the room either. To paste messages in IRC, use [http://pastebin.ca/ pastebin.ca], [http://www.sabayon.org/pastebin] or your favorite pasting site. Then simply give the URL for your pasted text so others can view your error. The people in IRC are not paid to be there, they do it out of dedication, so treat them nicely. Trolling, stupidity, and rudeness will get you banned. Also note that the IRC room is not there to teach you Linux or hold your hand. Don't be lazy, do your part too.
* Quick note when pasting error messages - Do not paste the error message alone: everyone thinks that ERROR: x11-base/xgl-0.0.1_pre20070915 failed is the error, it's not. The error is above that. Post the entire build log so we don't have to waste time waiting for you to post back with the actual error. If you read below the ERROR: it even says to paste the uppermost error and call stack if relevant.

En:FAQ

2013-03-07T22:32:06Z

Aposteeltje: /* How do I search for a package? */

{{I18n| [[Ca:FAQ|ca]] [[En:FAQ|en]] [[Es:FAQ|es]] [[It:FAQ|it]]}}

=FAQs=

=='''General Questions regarding Sabayon Linux'''==
===What is Sabayon Linux===
Sabayon Linux is a pre-configured distribution with the tenets of Performance, Versatility, and Stability, based on the source-based distribution named Gentoo Linux, a particularly customizable distribution. If you have other questions on Gentoo and its philosophy, I request you visit their website: http://gentoo.org. 
In particular, Sabayon emanates substantially from Gentoo's testing branch, one of the most popular source-based Linux distributions, which is about on par with Debian's unstable branch called Sid. Though based on the bleeding edge, you will find Sabayon is quite stable and perhaps more cutting edge than many. Although both Sabayon and Gentoo are rolling releases, Sabayon will have release snapshots. 

===How is Sabayon Linux maintained?===
As Ubuntu uses some of the packages from Debian, so Sabayon receives its packages from Gentoo. 
Sabayon, when using the package manager "Entropy" is binary based. Currently Sabayon has about 10,000 packages in Entropy. And when Sabayon is using the package manager "Portage", it is source based. The Gentoo repository is quite huge. 

===What is the difference between source-based and binary based distribution?===
Most distros, such as Ubuntu, Debian, Red Hat, Fedora and SUSE, install binary packages. Simply put, a binary package is the pre-compiled program, compiled on another computer and made available for download and installation on other computers. 
A source-based distro is one that compiles its programs from source code on the target computer at the time of installation, rather than relying on others to compile and package them. Source-based distros generally also have in their repositories some binary (pre-compiled) packages; these will be the large programs such as LibreOffice, the reason being that the compilation of these can take several hours. 
'''overlays'''
* Overlay: We have our own Portage overlay for ebuilds. Ebuilds are script files that contain instructions for the Portage package manager on how to install the package from its source code.
* Performance: We have modified the Portage make.conf file in order to ensure that our distribution will run at higher speed on newer computers and as fast as possible on older computers.
* Variability: Again, we have modified make.conf in order to cater to a wide spectrum of hardware, using the x86 and amd64 (x86_64) processor architectures.
* Entropy: We have a binary manager that can be used as the one, unique package manager. It functions also with Portage so that you can use them both if you are an experienced user. The Entropy binary packages are ready-built and can be installed immediately without the need to compile anything from the source code.
* The main branch of Gentoo is considered Gentoo stable. Sabayon is based on Gentoo's testing branch.
* Sabayon has different versions ready for quick and pain free installation. The Gentoo installation is done from the ground up, relying on you to make all the configuration choices.
* Gentoo has '''use''' flags. Sabayon will ignore '''use''' flags when using Entropy, but will apply the '''use''' flags when using portage. 

===Why choose Sabayon Linux ?===
1. Variety
Sabayon has multiple editions to choose from. From a variety of desktops to a variety of packages and installations that can enjoyed by new linux users as well as by power users who prefer a higher level of customization.
2. Sabayon is a rolling release.
Once installed you should not need to reinstall a new updated version, since you can use the update tools. Entropy is a GUI tool and front-end for the text console based Equo. This allows you to have the latest and greatest packages available to you, at all times.
3. The Anaconda installer.
The Anaconda installer in Sabayon greatly simplifies installation including disk partition setup and disk encryption, if desired or required.
4. Choice of package managers and repositories.
Sabayon's package manager Entropy is binary and currently contains about 10,000 packages in its repositories. Gentoo's package manager Portage is source based and has a quite huge repo.
5. Support.
Sabayon is highly active and well maintained. You can find help through our forums, live help, and the ever-growing wiki.
6. Look and feel.
Sabayon is generally considered one of the more visually attractive Linux distros. From the installer, to the desktops, and even down to the terminal which has a useful color scheme applied to make any work on the command line pleasing to the eye and easy to understand.
7. Using Sabayon helps to save the world
Test results have shown that using Sabayon Linux '''improves''' the economy; '''helps''' reduce global warming; is generally '''good''' for the environment; '''promotes''' world peace; and helps to fight off '''alien invasive''' species from other galaxies. It is also shown to be helpful in '''improving''' the health of your sense of '''humor''', which is important to keep from bashing your head on the key board during difficult moments. (Test results have been claimed to vary, but number 7 is considered an attempt at '''humor'''.) 

===Should I use Sabayon as a source-based or binary based distribution?===
Sabayon Linux has two package managers: [[Entropy]] (binary packages) and Portage (source packages). As you can install binary packages instead of source code-based packages, Sabayon Linux offers users a choice and the best of both worlds. The binary packages in the Entropy repository have been built by using the Portage package manager and then packaged using Entropy packaging tools on that computer. The binary packages are stored in the Entropy repository and you install them on your computer by using either the [[Equo]] command line client or the [[Rigo]] GUI client. As the release time and date of packages are a little different between the 2 package managers it is recommended to use one package manager consistently to avoid conflicts.

Generally, using Entropy with binary packages is recommended to new users and those who just want everything to work easily.

Portage(source based) is recommended for more advanced users who wish to customize their installation to a higher degree.

There are two main advantages to source-based distributions:
# Firstly, source-based distros often have the newest software before binary distros do. This is due mainly to the fact that rather than having to compile a package and then test it on different machines, all that is required in Sabayon Linux is a file telling it where to find the source code and how to compile it.
#Secondly, undoubtedly a program will eventually have a feature you don't need, and will just take up space or slow down the program. In a binary distro, you're stuck with this feature. In a source-based distro you have the option of removing unwanted features at the time of compilation (assuming you are using Portage rather than Entropy). 

===System Requirements===
* '''Live Environment - No 3D Desktop''':
** ''i686'' Processor
** at least ''512 MB'' of RAM (1 GB suggested)
** a ''2D'' graphics card
** a ''[http://en.wikipedia.org/wiki/Display_Data_Channel DDC] capable Monitor''
** ''mouse'' and ''keyboard''

* '''Live Environment - 3D Desktop''':
** ''i686'' Processor (starting from AMD K6 and Intel Pentium II)
** at least ''512 MB'' of RAM (1 GB suggested)
** an '''[http://en.wikipedia.org/wiki/OpenGL OpenGL] capable 3D graphics card''' (mostly NVIDIA, ATI, Intel, VIA)
** a ''[http://en.wikipedia.org/wiki/Display_Data_Channel DDC] capable Monitor''
** ''mouse'' and ''keyboard''

* '''Installation''':
{{Note| Please note that the Requirements indicated for Installation may be a bit too low for some Desktop Environments.
A full KDE Desktop for example, CAN run with only 1 GB RAM, but you will most likely run out of memory during a session, especially when running large programs, such as firefox, thunderbird and/or libreoffice. Please keep that in mind.}}
** ''i686'' Processor
** at least ''512 MB'' of RAM (1 GB suggested for decent eyecandy effects)
** an '''[http://en.wikipedia.org/wiki/OpenGL OpenGL] capable 3D graphics card''' (mostly NVIDIA, ATI, Intel, VIA)
** ''20'' GB of free space, that is bare minimum DVD Install. ''30+'' GB is highly recommended.
** ''8 GB'' of free space for miniCD. 10+ GB is recommended
** ''Internet connection'' (not mandatory but highly suggested)
** a ''[http://en.wikipedia.org/wiki/Display_Data_Channel DDC] capable Monitor''
** ''mouse'' and ''keyboard'' 

=== What Editions are available in Sabayon Linux? ===

Sabayon is all about choice. You have many flavors to choose from.

You can download them from the mirrors, here:
* [http://www.sabayon.org/mirrors Sabayon Mirrors Page]

The following choices are the main releases available in 32Bit (x86) or 64Bit (amd64):
{{Note| "amd64" is also suitable for '''Intel''' based 64bit Processors}}
1. KDE
2. Gnome
3. LXDE
4. MATE
5. XFCE
6. Enlightenment
All of the above mentioned Desktop Environments are fully-featured.

7. CoreCDX
CoreCDX is a minimal install for those wishing to configure the system more to their liking,
(for more advanced users) in 32bit or 64bit., and uses the Fluxbox Window Manager.

=== How can I contribute to, or support Sabayon Linux ===
There are several ways to contribute:

* The Sabayon foundation is always looking for funds.
For more information, see: http://www.sabayon.org/donate
* Translations.
We are always looking for translators. For the Wiki, as well as translating Sabayon into your native language. 

You may subscribe to our wonderful Wiki, and translate the articles into your own Language, or write your own articles about some area of working with Gnu/Linux. 

If you want to translate Sabayon into your own language, please see:
[[En:HOWTO: Translate Sabayon]] 

If you want to translate the Wiki articles into your own language, please see:
[[En:Translations]] and [[Editing_Guidelines]] 

* Subscribe to our Forum
Help out others with problems. Perhaps problems you've had once too, 
and know the answer or a solution.
http://forum.sabayon.org/ 

* Join us on Facebook or Google+
There are lots of Discussions going on on facebook and Google+. Want to help out, or participate? 
https://www.facebook.com/groups/36125411841/ 
https://plus.google.com/+sabayon/posts 

*setup more download mirrors
We need more mirrors! 

Check out this link to learn more about what it takes to mirror the Sabayon Linux project.
http://wiki.sabayon.org/index.php?title=Mirroring_Sabayon 

=='''The liveCD/DVD'''==
===Should I get the 32-bit or the 64-bit edition?===
This is a never-ending, debatable question. For new users, 32-bit is easier to operate as 64-bit may be a bit fussier. Everything should work in 64-bit as the 32-bit version. Keep in mind that you are still using mostly 32-bit applications. The average desktop user is not going to see benefits over the 32-bit. I suggest to people to try both and see for themselves. In my experience I see most new people picking the 32-bit version. You can certainly Google for more information on this debate.
64bit would seem to be the direction things are going in, though most applications are still in 32bit. 64bit has gotten more support these days and become more widespread in use. 64bit is currently more secure, however most 64bit systems use multi libraries. multi libraries allow you to use both 64 and 32bit apps. A 64bit system using multi libraries will have a certain amount of vulnerability as a 32 bit system.

===Can I install without having to burn the ISO to CD or DVD?===
Yes, you can [http://www.sabayonlinux.org/forum/viewtopic.php?f=50&t=12023 install if you don't have a CD or DVD burner.] Another way, if your computer can boot USB pen drives, is to use UNetbootin or similar to install the Sabayon Linux ISO to a pen drive and create a bootable pen drive (think of it as a fast LiveCD/DVD). Then you can boot the pen drive to get to a Live desktop, and install Sabayon Linux from there, just as you would from a LiveCD/DVD.

=== burning / checking the .iso image ===

One of the most common problems with burning a Linux install CD/DVD is that people sometimes don't understand that an iso image file is not a normal file. You cannot just burn the iso to disc to and expect it to work. I repeat: '''you cannot simply put the iso file on a blank disk and expect it to work'''. In order to properly make a CD or DVD out of an iso image, you need special software. Instructions for Nero and Isorecorder are included; for other programs, see the manual for the software, or just give one of these a shot.

With Nero you just select file and burn image, then select the .iso file you want to burn. The software handles the rest.

If you're looking for a good, alternative freeware solution, you can download a free image burner.

isorecorder [http://isorecorder.alexfeinman.com/isorecorder.htm] Simply download and install the correct version for your version of windows, then right click on the .iso and tell it to burn.

=== checking the integrity of the burned disc ===

Many people know they can check if a downloaded ISO file is OK by comparing the md5sum of the ISO file against the md5sum posted on the SL mirrors. For example:

{{Console| <pre class="clear">
# md5sum -c SabayonLinux-x86_64-3.4f.iso.md5
SabayonLinux-x86_64-3.4f.iso: OK
</pre>}}

cf. the contents of ftp://bo.mirror.garr.it/mirrors/sabayonlinux/SabayonLinux-x86_64-3.4f.iso.md5 which are:
645600788920443b372baae3544acffa SabayonLinux-x86_64-3.4f.iso

so the ISO I downloaded was good.

Remember - verify the MD5 sum for the version of Sabayon that you downloaded - they are all different. The MD5s can be found on the mirrors listed at: http://www.sabayonlinux.org/mirrors

But a different method is needed to verify the '''integrity''' of the LiveDVD/CD itself. You should select the verify written data checkbox in K3b before burning the DVD/CD, but if you forgot or still have doubts then the following method can be used to check the integrity of the burnt LiveDVD/CD:

If you only have Windows installed on your HDD, apparently you can use a Windows shareware application, see the following Web page for details:
http://www.mepis.org/docs/en/index.php?title=Checking_the_integrity_of_a_Live_CD

A WARNING:

1. I have not checked if the method for Windows on the above-mentioned Web page actually works, so use it at your own risk.

Under Linux:

Insert the LiveDVD into the optical drive, let the disc spin up and then enter the following three commands:

{{Console| <pre class="clear">
md5sum /dev/cdrom | awk '{print $1}' > md5a.txt
md5sum ~/Sabayon_Linux_8_amd64_K.iso | awk '{print $1}' > md5b.txt
diff -qs md5a.txt md5b.txt
</pre>}}

(Obviously change the path and/or the ISO file name to match your circumstances.)

If you get an error message while the md5sum is reading the disc, there must be something wrong either with the burn or with the optical drive itself.

If you get the message "Files md5a.txt and md5b.txt differ" then the burn was bad.

If you get the message "Files md5a.txt and md5b.txt are identical" then the burn was good.

=== Passwords on live CD/DVD ===

* The root password:
no password is required: just press the Enter key.

* The sabayonuser password:
no password is required: just press the Enter key.

*For older releases (version 6 and earlier) the password for Root is "root" (without the quotes) and the password for Sabayonuser is "sabayonuser" (without the quotes).

=== The Booting process ===

The boot process of the liveCD/DVD should be pretty straight forwarded, just as many other Linux Distrtibutions.

However, you could get into problems, when having hardware that isn't supported by default, for example.

Or having old hardware that the current drivers don't support.

When having a old NVidia card, and you've downloaded the latest ISO, chances are that it will not start the Window Manager/Desktop Environment, but rather present you with a black screen.

There is nothing wrong with the ISO, it is because "nvidia-drivers-304.64" or higher is installed by default.

You can bypass that by hitting ctrl-alt-f1, remove the nvidia-drivers, (nouveau is installed too), and restart xdm., as explained below:

'''Removing latest nvidia-drivers:'''
# Press the "CTRL-ALT-F1" key combination.
"#" is just indicated that you have to be root, so do not include that with the actual commands...
{{Console| <pre class="clear"># su</pre>}}
{{Console| <pre class="clear"># equo remove nvidia-drivers --ask</pre>}}
Check that "x11-drivers/nvidia-drivers" got removed., nothing else... and confirm with "yes"

Restart XDM:
{{Console| <pre class="clear"># /etc/init.d/xdm restart</pre>}}

For a overall view of which cards support what driver., please see: http://www.nvidia.com/object/IO_32667.html

If you wish to be guided through the boot process and the several options it offers, we have a visual walkthrough.

Please see: [[Visual_Tour:_Boot-menu_Sabayon_LiveCD/DVD]]

Workarounds for problematic Hardware, during the boot process are discussed here:

[[Sabayon_Linux#Boot_parameters_and_workarounds_for_problematic_Hardware]]

'''cheatcodes for ATI and nVidia'''

ATI
noddc res=1024x768 refresh=60 opengl=ati
nVidia
noddc res=1024x768 refresh=60 opengl=nvidia

To use the cheatcodes, hit F5 on the boot up screen of the livecd/dvd and add one of the lines above pending on your hardware

see: [[Visual_Tour:_Boot-menu_Sabayon_LiveCD/DVD]]

When you need to edit xorg.conf, or have to create it for special reasons, the following visual tour will show you how to edit Xorg.conf:

[[Visual_Tour:_Part_2_Editing_the_xorg.conf]]

=='''After installation'''==

===What is Entropy or Equo?===
[[Entropy]] is the binary package manager of Sabayon Linux. To install binary packages you use either the command line client [[Equo]] or the newest Graphical GUI [[Rigo]].

A binary package is a file package containing the already-compiled files to install instead of having to compile the source code. Equo, and [[rigo]] handle these files.

===I just installed it, what do I do first?===
This question has always amazed me. Who says there is anything to do? How about just using the operating system and getting familiar with it? Take some time and read the documentation. If you insist on having to do something then emerge --sync && layman -S to update your Portage package list, or, if using Entropy, see [http://wiki.sabayonlinux.org/index.php?title=Entropy#Fresh_Install_-_What_to_do.3F Fresh Install]

===The GUI for managing packages===

[[rigo]] is the GUI for the Entropy package manager.

{{Warning|'''emerge and layman are Portage commands, Portage is not our own package manager but is available to advanced users. Any steps using these commands can be safely ignored'''}}

There are GUIs for the Portage package manager, but they are no substitute for using emerge on the command line.
* Currently we have Kuroo4, and porthole. Kuroo4 seems to be the best, but only available in Portage.
Personally if you have to rely on a GUI, then try to just use it as a browser of Portage, but still use the command line to install your packages. You will save yourself a lot of headaches. Search and gather your information needed with the GUI then open up Konsole or Terminal and install using the emerge command.

===How do I update/install packages?===
There are 2 package managers, Entropy and Portage. It is highly recommended that you choose and only use 1 package manager. Conflicts can arise from mixing both package managers.
Please read the [[Entropy]] page. Entropy is the package manager specially developed for Sabayon Linux. It has a command line interface ([[Equo]]) and a GUI interface ([[Sulfur]]). Equo commands and Sulfur GUI are Entropy and recommended for newer users of Sabayon Linux. Advanced users of Sabayon Linux may wish to use Portage, the package manager developed for Gentoo Linux, on which Sabayon Linux is based. For information on Portage, please read [[HOWTO: The Complete Portage Guide]].

===How do I install several packages?===
For Entropy:
{{Console| <pre class="clear"># equo install foo foo foo foo foo</pre>}}

For Portage:
{{Console| <pre class="clear"># emerge foo foo foo foo foo</pre>}}

The package manager will install each package one after another. Replace foo with actual package name.

===How do I search for a package?===
* For Entropy:
{{Console| <pre class="clear"># equo search foo</pre>}}
or use the [[rigo]] GUI, or on the Web:[http://packages.sabayon.org/ Sabayon Linux Web site's Entropy package search page].
* For Portage:
{{Console| <pre class="clear"># emerge -s foo</pre>}}
or use a GUI such as Kuroo4.
* Via [http://gentoo-portage.com/Browse Gentoo-Portage] or via [http://packages.gentoo.org/ Packages-Gentoo].

'''Using EIX'''
* For Portage:
I highly recommend using eix. It's the best tool you can have at your hands for searching. It is a command line tool, but it is very powerful and will tell you lots of information.
{{Console| <pre class="clear"># emerge eix && eix-update
# eix foo</pre>}}

You can use eix in Entropy too:
{{Console| <pre class="clear"># equo install eix && eix-update
# eix foo</pre>}}

Example output of eix gedit:
{{Console| <pre class="clear"> [I] app-editors/gedit
Available versions: 2.18.2-r1 2.20.3 (~)2.20.4 {acl debug doc python spell xattr}
Installed versions: 2.20.4(07:05:31 AM 12/29/2007)(python -debug -doc -spell -xattr)
Homepage: http://www.gnome.org/
Description: A text editor for the GNOME desktop</pre>}}
Eix has the ability to search Portage and all overlays. Simply edit the /etc/eix-sync.conf file and just add * to it
{{Console| <pre class="clear"># echo '*' >> /etc/eix-sync.conf</pre>}}
Then do:
{{Console| <pre class="clear"># eix-remote update</pre>}}
Now when you search, it will tell where and what overlay a package is in if it is not in the Portage main tree. This will widen your abilities to find packages, as overlays contain a lot of ebuilds too.

http://en.gentoo-wiki.com/wiki/Eix

===Can I emerge 2 packages at same time in Portage?===
Yes you can, but it can and will bog your system down. It's not really recommended.
===How do I update everything at once?===
For Entropy:
{{Console| <pre class="clear"># equo update
# equo upgrade
# equo conf update</pre>}}

See the Sabayon Wiki article [[Entropy]] for details.

{{Warning|'''emerge and layman are Portage commands. Portage is not our package manager but is available to advanced users. Any steps using these commands can be safely ignored'''}}

If you are new to this distro and have no understanding of Portage, we do not recommend this until you get to know how this distro works. This is one of the fastest ways to destroy your system. This distro is not like the other distros that have the big easy button update. For your information though, 'world update' is what Gentoo calls updating your entire system. It looks at your 'world file' and compares it to Portage and then proceeds to update all packages. Following is how:

{{Console| <pre class="clear"># emerge -- sync && layman -S
# emerge -ua world</pre>}}

* [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap3 Maintaining Software]
* [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=5531 Unofficial Guide to World Update]
You've been warned. When you come yelling because your system won't boot, don't expect sympathy.

N.B. The term 'world' is not used in Entropy.

===How do I uninstall a package?===
* For Entropy:
{{Console| <pre class="clear"># equo remove foo</pre>}}
Note - this can remove dependencies.

*For Portage:
{{Console| <pre class="clear"> # emerge -C foo</pre>}}
Note - this will not remove the dependencies. You will need to run [http://en.gentoo-wiki.com/wiki/Gentoo_maintenance#depclean depclean] for that. I stress great caution with depclean, as it means what it says.

===How do I find out which packages depend on a certain package?===
{{Console| <pre class="clear"># equery depends foo</pre>}}
It will tell you all files depending on that package. See [http://www.gentoo.org/doc/en/gentoolkit.xml using gentoolkit] for more information and commands.

===I keep getting !!! ARCH is not set... Are you missing the 'etc/make.profile' symlink?===
In Konsole/Terminal use the '''su''' command to become the root user and then:
* Run the following command: '''eselect profile list'''
* Look for something like: '''default-linux/x86/2007.0/desktop''' and note the number in front of it.
* Then do: '''eselect profile set #''' <--replace the # with the number. In my case it would be '''eselect profile set 6'''
Now you should be good to go again.

===Do I have to download the LiveCD/DVD every time to upgrade?===
No, Sabayon is a rolling release. However in some cases upgrading via live DVD may prove more time efficent.

Entropy:
The equo command makes upgrading easy - see [[Entropy]].

Portage:
Portage is recommended for advanced users that prefer a higher degree of customization. That being said, Gentoo documentation is quite extensive and helpful for those wanting to dive into it.

Always backup your files before doing anything. My personal opinion: backup, fresh install, restore backup.

===How do I check for security updates ?===
It's pretty easy to keep your [http://www.gentoo.org/doc/en/security/security-handbook.xml?part=1&chap=14 system secure.]
Entropy does this for you automatically.

For Portage:
* Open up konsole or terminal and enter the command '''su''' to become the root user.
* Run the command '''glsa-check -t all''' to check your system.
* Then to fix, run '''glsa-check -f $(glsa-check -t all)'''

You can also visit our security wiki for more helpful tips:
* [http://wiki.sabayon.org/index.php?title=En:Security Sabayon Security wiki]

===How do I handle blocked packages?===
This is an issue in Portage. You are going to run into [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap4 packages blocking other packages.] This can happen for several reasons, e.g. a package has been dropped from Portage as it no longer exists or is no longer supported. In most cases you will simply have to remove (uninstall) the package that is blocking the new package. You will want to do some research on this first. Don't take Portage for granted and blindly do as it says without checking out what or why.

Note - latest versions of Portage (version 2.2 and higher) handle most blockages.

===How to handle masked packages?===
A package is complaining that it is [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap5 masked] and cannot install. This is one of those times you want to check why it is masked. A masked package is usually masked to prevent you from busting things. There are several ways a package can be masked. You can still install masked packages by unmasking them, but make sure you find out first why they are masked.

===How do I update the config files?===
As you install stuff, some packages are going to bring in new versions of their config files. These config files are important as they may have new settings for that package that need to be implemented. I stress that is is very, very crucial that you pay attention to these config files. You can change the entire outcome of your installation if you are not careful. Get to know your [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10863 config files.] There are several ways to handle these files:

For Entropy:
{{Console| <pre class="clear"># equo conf update</pre>}}

For Portage:
[http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=4#doc_chap1 dispatch-conf] and [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=4#doc_chap2 etc-update] are probably the most popular ways of handling updates to config files. A GUI tool is [http://etc-proposals.berlios.de/ etc-proposals.]

Please handle these files with care. You can't know these files enough.

===Where do I start to configure my system?===
For Entropy:
All packages are pre-configured remotely as they have been compiled on a remote computer. You do not need to (and cannot) do anything. If a package has been compiled without a specific USE flag that you need, then you will either have to request to the Entropy repository maintainers that the package be rebuilt (file a bug report in [http://bugs.sabayonlinux.org/ bugzilla]) and the new version placed in the Entropy repository, or use Portage to rebuild it yourself.

For Portage:
The file [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578 make.conf] is your heart and soul of your operating system. Learn it, edit it and build a lean, mean machine. Sabayon Linux ships with a generic make.conf that tries to support everything under the sun. You don't need all that stuff and by configuring, you will have lesser issues with Portage and conflicts.

===Where does Portage download the packages to?===
They are downloaded and stored in the directory '''/usr/portage/distfiles/'''

===Where does Entropy download the packages to?===
They are downloaded and stored in the directory '''/var/tmp/entropy/packages/'''
For instance, on my amd64 using Branch 4 they are stored in '''/var/tmp/entropy/packages/amd64/5'''

===How do I clean out Entropy downloaded packages?===

{{Console| <pre class="clear"># equo cleanup</pre>}}
See [http://wiki.sabayonlinux.org/index.php?title=En:List_Of_Equo_Functions Sabayon Wiki page of Equo commands] or equo --help --verbose

=='''Additional'''==
=== How do I get the Desktop Cube thing working?===
The desktop cube and 3D graphics do not work after I installed Sabayon Linux to the hard disk, but do work when I'm using the LiveCD/DVD.

Well, in theory what you see when you run the LiveCD/DVD is what you get when you install Sabayon Linux. So if the 3D desktop was working with the LiveCD/DVD then it should work when you boot your new installation. Well, we know all about theories; it doesn't work for everyone. You can either search in the Sabayon Linux Forums and the Sabayon Wiki for help on how to get the 3D desktop working with your particular model of graphics card, or you can ask in IRC #sabayon.

First thing you need to do: make sure the md5sum is good after you downloaded the .iso file, I can't stress that enough. Make sure you have burnt the CD/DVD as slowly as possible, and enable Burn Verify in your burning application.

You will be asked those two questions every time, so please do this so we don't have to waste bandwidth re-asking. It may seem petty to you to check the md5sum but, without knowing you're starting out with a good ISO file, it's pointless to continue. We can spend weeks troubleshooting and if your md5sum was bad, we just waste a lot of time and it causes a lot of frustration. With a bad md5sum you can still get a bootable working desktop, but may have issues elsewhere. So keep in mind, just because it boots, doesn't mean the ISO file is good. How do I check the md5sum and disk you ask? Well, luckily for you: [[HOWTO: Checking the integrity of a LiveCD or LiveDVD]].

OK, so you made sure the md5sum was good and you burnt the disk at a nice slow speed with Burn Verify enabled. Now we can start looking at other things. Do you have the correct video driver and the latest version of it? That will be the first thing to know.

NVIDIA card owners, the following link will save you hours of frustration. Yes, certain cards require certain drivers: http://en.gentoo-wiki.com/wiki/Nvidia. If you do not know or understand what is 'masking' then please read more (Portage users, see http://dev.gentoo.org/~dang/masked.txt. Entropy users, see [[Entropy#Masking_and_Unmasking_Packages_in_Entropy]].

Our Wiki also has a HowTo get NVIDIA and ATI cards working too, so use the relevant information: [[HOWTO: Get Ati or Nvidia Video Cards working in Sabayon]]. Also search the Sabayon Linux Forums for posts mentioning your card manufacturer and model.

The above method will work for most people, but you will find that maybe it didn't work for you. Why? I don't know. A little bit of research into /etc/X11/xorg.conf can usually resolve the remaining few that have problems. The following link is full of information for AIGLX: http://en.gentoo-wiki.com/wiki/AIGLX/Troubleshooting. Again, only use the information that is relevant. You will want to pay attention to the xorg.conf settings shown on that page and compare it to your xorg.conf so it matches.

Still having problems? Buy a new video card!

If you want to post your special way of how you got it working - please do. Mine just works all the time so I don't have such problems.

===Multimedia===
Does this include support for some privately-owned platforms? Yes, Sabayon Linux supports DVDs, MP3, WMA, AAC, DivX. Moreover, it supports a lot of open platforms, such as Ogg Vorbis, Matroska, Ogg Theora, FLAC, and coder-decoder Xvid.

===Games===
[http://www.sabayonlinux.org/forum/viewforum.php?f=43 Please Visit our Gaming Shed]

===AIGLX===
Q: Is AIGLX available?

A: If your graphics card is capable, then this should work out-of-the-box. If you are having trouble, start with the Gentoo Wiki article http://en.gentoo-wiki.com/wiki/AIGLX/Troubleshooting.

Q: In [[HOWTO: Get Ati or Nvidia Video Cards working in Sabayon]] it states that ATI GPUs can use AIGLX with the closed-source driver FGLRX. Is it feasible? Previously this worked only with XGL and open source DRI (direct giving infrastructure) Radeon driver.

A: AIGLX is supported by both the open-source Radeon driver and the closed-source FGLRX driver. N.B. Not all ATI cards are supported by the closed-source FGLRX driver and must use the Radeon driver. To find out if the closed-source driver supports your ATI card, see the release notes for the relevant version of the FGLRX driver (a.k.a. AMD Catalyst driver for Linux).

===3D Desktop/Compiz Questions===
'''The cube was working on LiveCD/DVD but doesn't on install, now what?'''

Well, now it's getting difficult as we need to [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=11723 check more things.] You will need the assistance of the Sabayon Linux Forum or IRC to help. I recommend you try and find the source of your problem first. When logged in, open a Konsole/Terminal window and type in the command fusion-icon and see what the error message is in the Konsole/Terminal. You will need to post that error message with your request for help. Make sure you have installed the latest video drivers for your video card also.

'''How do I update Compiz-Fusion to latest Dev. Version?'''

We have a [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=9882 guide on the forum] that is maintained to keep up with the changes in Compiz-Fusion development. This is for Portage users.

'''How do I know if my card will work with Compiz-Fusion?'''

We have a [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=8773 card list] that the community has reported on if their card works or not. It's not a complete list, but a good list to reference.

'''Where can I get more help on Compiz-Fusion?'''

I would suggest their [http://forum.compiz-fusion.org/ support forum.]

===How do I install KDE 4.x.x with Equo?===

{{Console| <pre class="clear"># equo install kde-meta-4.x.x</pre>}}

Replace the x's with the version of KDE you want to install.

===How Do I enable Autologin?===
The real question is, do you really want to? If yes, you should get a hammer and hit yourself in the head repeatedly. Logging in, especially logging in as user, not root, is a very basic but powerful security measure. Hostile programs cannot be autorun on your system if you log in as user. Also no one can accidently/purposefully find your collection of porn, google searches, or downloaded emails simply by pushing the power button if you set a user with password.
[http://wiki.sabayonlinux.org/index.php?title=En:HOWTO:_Setting_Up_Autologin Please see our Wiki page for how to do this.]

===How Do I change the positioning of notifications?===
By default the sabayon gnome version comes with [https://launchpad.net/notify-osd notify-osd]. This is developed by Canonical and
Mark Shuttleworth says the positioning won't be configurable [http://www.markshuttleworth.com/archives/265#comment-316838].
So if you want the notifications to appear in another corner you'll have to uninstall notify-osd and install [http://www.galago-project.org/news/index.php notification-daemon].
After that you will be able to configure the positioning with {{Console| $ notification-properties}}

===Networking Questions===
'''How do I find out what network card I have?'''

As root user, enter the command '''lspci''' in a Konsole or Terminal window. That will list hardware; look for your Ethernet controller.

'''How do I set-up my network?'''

Well, hopefully the LiveCD/DVD recognizes your network card, and NetworkManager sets your network up for you. If it doesn't, try running the command as root: simply '''su''' and run '''net-setup'''. You're going to want to consult the [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4 Gentoo Networking section.]

'''I can ping my router but can't access the Internet'''

You're probably having DNS issues. You need to edit the file /etc/resolv.conf and enter the correct DNS, then restart your network. If you don't know what to use for DNS, use 4.2.2.2

===Sound Questions===
'''I have no sound, what do I do?'''

* Let's see if you computer detects your sound card so, from a command line, use '''su''' to become root user, and run '''alsaconf''' - hopefully your card shows up and all you have to do is select and go.
* After running that, you can use '''alsamixer''' to adjust your sound settings. Press F6 to select your card in ALSAMixer and make sure no channels are muted and that the channel volumes are turned up.
* [http://wiki.sabayon.org/index.php?title=HOWTO:_Resolve_Problems_with_HDA-Intel_Sound_Cards If you have HDA-Intel Card, Please see this HowTo]

'''How can I determine what sound card I have?'''

As root user run the command '''lspci | grep -i audio'''

'''How do I install the alsa-driver instead of having it in the kernel?'''

Sabayon Linux comes with ALSA built into the kernel. You can't install the alsa-drivers while ALSA is built into the kernel. You have to remove ALSA from the kernel before you install the alsa-driver package. So use the '''su''' command to become the root user, and then enter the following commands:

{{Console| <pre class="clear">
# cd /usr/src/linux
# make menuconfig
# make && make modules_install
# cp arch/i386/boot/bzImage /boot/kernel_name <--replace kernel_name with the actual name of kernel
</pre>}}

* Reboot

{{Console| <pre class="clear">
# emerge alsa-driver
</pre>}}
* More info: [http://www.gentoo.org/doc/en/alsa-guide.xml Gentoo ALSA Guide.]

'''Why do I have to run alsaconf every time I reboot?'''

This usually happens if you have more than one sound card in your machine. Many people have an on-board sound card and then stick in a better sound card. Disable your on-board sound card via your BIOS and when you run alsaconf again, ALSA will restore your sound each time you reboot.

===Video Questions===
'''My NVIDIA card is a legacy card, what driver do I need?'''

You will need to compare your card with the information below to find out which driver is best for your card:
* [http://en.gentoo-wiki.com/wiki/Nvidia Check out the Nvidia Howto]
* [http://www.gentoo.org/doc/en/nvidia-guide.xml Also the Nvidia Guide]

'''I need help with my AMD/ATI card!'''

I don't have ATI so I can't supply much help here, but I can point you to:
* [http://en.gentoo-wiki.com/wiki/Graphics_drivers#AMD.2FATI Howto Ati Drivers]
* [http://www.gentoo.org/doc/en/ati-faq.xml Gentoo FAQ on ATI]

===How do I setup AIGLX with my ATI?===
* [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=12438 HOWTO AIGLX with ATI and Sabayon 3.5]

'''How do I setup Dual Monitors?'''

Personally I use twin view and it works great with Compiz-Fusion also. Check out the [http://en.gentoo-wiki.com/wiki/Dual_Monitors Gentoo Wiki article X.Org/Dual Monitors]

'''Video Worked on LiveCD/DVD, but not once install. Options?'''

If your video was fine on the LiveCD/DVD I would boot the LiveCD/DVD and copy the xorg.conf from it to your hard drive install. There are several ways to do this.

* Option 1 - Boot up and browse to /etc/X11/ and copy the file xorg.conf to your installed version. You should be able to access your installed version through the /media directory so it may be something like /media/mydrive/etc/X11/ Reboot the computer and you should have what you had on the LiveCD/DVD. Always backup your files before overwriting.
* Option 2 - Boot up and browse to /etc/X11/xorg.conf and use something like http://www.pastebin.ca to paste your xorg.conf file there. Note the URL so that when you reboot to your installed version you can access it. Then just rename your existing xorg.conf and make a new one with the one you pasted.
* If you still don't have any luck, we may need to look at your drivers. Try reinstalling your video drivers, but, before reinstalling, make sure you are getting the latest drivers. NVIDIA users, make sure you are using the proper drivers for your card. See Question 1 under Video Questions.

===How do I know what Version of Sabayon I installed?===

{{Console| <pre class="clear">
# cat /etc/sabayon-release
</pre>}}
N.B. Sabayon Linux is a 'rolling release' distro. Therefore, if you have upgraded your installation via Entropy or Portage then your installation will no longer be the version recorded in /etc/sabayon-release, as that file tells you the version of the LiveCD/DVD that you used to install Sabayon Linux.

=='''Help and Support Questions'''==

'''How Do I get Log files to get better support?'''

With the package app-misc/sabayonlive-tools, you can easily gather important information to help you debug and provide vital information for the support team to help you. [http://forum.sabayonlinux.org/viewtopic.php?f=60&t=15530 Please see this thread to learn how].

'''Where Do I file a Bug Report?'''

Please use our [http://bugs.sabayonlinux.org/ bugzilla]

'''Where can I get help?'''

Are you lost and confused? There are a lot of great resources out there. I highly encourage you to do some searching first before running into IRC or the Forum and making the same post that has already been posted 100 times. It gets really old answering the same question day in and day out when it's so well documented.
* [http://www.sabayonlinux.org/forum/index.php Sabayon Linux Forum]
* [http://www.sabayonlinux.org/wiki/ Sabayon Linux Wiki]
* [http://www.gentoo.org/doc/en/handbook/index.xml Gentoo Handbook]
* [http://gentoo-wiki.com/Official_Gentoo_Documentation Official Gentoo Documentation]
* [http://gentoo-wiki.com/Main_Page Gentoo Wiki]
* [http://gentoo-portage.com/Browse Gentoo Portage]
* [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1 A Portage Introduction]
* irc.freenode.net in channel #Sabayon also on desktop Get Live Help -- note to IRC users, be human and have patience. Do not paste errors in the room either. To paste messages in IRC, use [http://pastebin.ca/ pastebin.ca], [http://www.sabayon.org/pastebin] or your favorite pasting site. Then simply give the URL for your pasted text so others can view your error. The people in IRC are not paid to be there, they do it out of dedication, so treat them nicely. Trolling, stupidity, and rudeness will get you banned. Also note that the IRC room is not there to teach you Linux or hold your hand. Don't be lazy, do your part too.
* Quick note when pasting error messages - Do not paste the error message alone: everyone thinks that ERROR: x11-base/xgl-0.0.1_pre20070915 failed is the error, it's not. The error is above that. Post the entire build log so we don't have to waste time waiting for you to post back with the actual error. If you read below the ERROR: it even says to paste the uppermost error and call stack if relevant.

En:FAQ

2013-03-07T22:30:48Z

Aposteeltje: /* How do I search for a package? */

{{I18n| [[Ca:FAQ|ca]] [[En:FAQ|en]] [[Es:FAQ|es]] [[It:FAQ|it]]}}

=FAQs=

=='''General Questions regarding Sabayon Linux'''==
===What is Sabayon Linux===
Sabayon Linux is a pre-configured distribution with the tenets of Performance, Versatility, and Stability, based on the source-based distribution named Gentoo Linux, a particularly customizable distribution. If you have other questions on Gentoo and its philosophy, I request you visit their website: http://gentoo.org. 
In particular, Sabayon emanates substantially from Gentoo's testing branch, one of the most popular source-based Linux distributions, which is about on par with Debian's unstable branch called Sid. Though based on the bleeding edge, you will find Sabayon is quite stable and perhaps more cutting edge than many. Although both Sabayon and Gentoo are rolling releases, Sabayon will have release snapshots. 

===How is Sabayon Linux maintained?===
As Ubuntu uses some of the packages from Debian, so Sabayon receives its packages from Gentoo. 
Sabayon, when using the package manager "Entropy" is binary based. Currently Sabayon has about 10,000 packages in Entropy. And when Sabayon is using the package manager "Portage", it is source based. The Gentoo repository is quite huge. 

===What is the difference between source-based and binary based distribution?===
Most distros, such as Ubuntu, Debian, Red Hat, Fedora and SUSE, install binary packages. Simply put, a binary package is the pre-compiled program, compiled on another computer and made available for download and installation on other computers. 
A source-based distro is one that compiles its programs from source code on the target computer at the time of installation, rather than relying on others to compile and package them. Source-based distros generally also have in their repositories some binary (pre-compiled) packages; these will be the large programs such as LibreOffice, the reason being that the compilation of these can take several hours. 
'''overlays'''
* Overlay: We have our own Portage overlay for ebuilds. Ebuilds are script files that contain instructions for the Portage package manager on how to install the package from its source code.
* Performance: We have modified the Portage make.conf file in order to ensure that our distribution will run at higher speed on newer computers and as fast as possible on older computers.
* Variability: Again, we have modified make.conf in order to cater to a wide spectrum of hardware, using the x86 and amd64 (x86_64) processor architectures.
* Entropy: We have a binary manager that can be used as the one, unique package manager. It functions also with Portage so that you can use them both if you are an experienced user. The Entropy binary packages are ready-built and can be installed immediately without the need to compile anything from the source code.
* The main branch of Gentoo is considered Gentoo stable. Sabayon is based on Gentoo's testing branch.
* Sabayon has different versions ready for quick and pain free installation. The Gentoo installation is done from the ground up, relying on you to make all the configuration choices.
* Gentoo has '''use''' flags. Sabayon will ignore '''use''' flags when using Entropy, but will apply the '''use''' flags when using portage. 

===Why choose Sabayon Linux ?===
1. Variety
Sabayon has multiple editions to choose from. From a variety of desktops to a variety of packages and installations that can enjoyed by new linux users as well as by power users who prefer a higher level of customization.
2. Sabayon is a rolling release.
Once installed you should not need to reinstall a new updated version, since you can use the update tools. Entropy is a GUI tool and front-end for the text console based Equo. This allows you to have the latest and greatest packages available to you, at all times.
3. The Anaconda installer.
The Anaconda installer in Sabayon greatly simplifies installation including disk partition setup and disk encryption, if desired or required.
4. Choice of package managers and repositories.
Sabayon's package manager Entropy is binary and currently contains about 10,000 packages in its repositories. Gentoo's package manager Portage is source based and has a quite huge repo.
5. Support.
Sabayon is highly active and well maintained. You can find help through our forums, live help, and the ever-growing wiki.
6. Look and feel.
Sabayon is generally considered one of the more visually attractive Linux distros. From the installer, to the desktops, and even down to the terminal which has a useful color scheme applied to make any work on the command line pleasing to the eye and easy to understand.
7. Using Sabayon helps to save the world
Test results have shown that using Sabayon Linux '''improves''' the economy; '''helps''' reduce global warming; is generally '''good''' for the environment; '''promotes''' world peace; and helps to fight off '''alien invasive''' species from other galaxies. It is also shown to be helpful in '''improving''' the health of your sense of '''humor''', which is important to keep from bashing your head on the key board during difficult moments. (Test results have been claimed to vary, but number 7 is considered an attempt at '''humor'''.) 

===Should I use Sabayon as a source-based or binary based distribution?===
Sabayon Linux has two package managers: [[Entropy]] (binary packages) and Portage (source packages). As you can install binary packages instead of source code-based packages, Sabayon Linux offers users a choice and the best of both worlds. The binary packages in the Entropy repository have been built by using the Portage package manager and then packaged using Entropy packaging tools on that computer. The binary packages are stored in the Entropy repository and you install them on your computer by using either the [[Equo]] command line client or the [[Rigo]] GUI client. As the release time and date of packages are a little different between the 2 package managers it is recommended to use one package manager consistently to avoid conflicts.

Generally, using Entropy with binary packages is recommended to new users and those who just want everything to work easily.

Portage(source based) is recommended for more advanced users who wish to customize their installation to a higher degree.

There are two main advantages to source-based distributions:
# Firstly, source-based distros often have the newest software before binary distros do. This is due mainly to the fact that rather than having to compile a package and then test it on different machines, all that is required in Sabayon Linux is a file telling it where to find the source code and how to compile it.
#Secondly, undoubtedly a program will eventually have a feature you don't need, and will just take up space or slow down the program. In a binary distro, you're stuck with this feature. In a source-based distro you have the option of removing unwanted features at the time of compilation (assuming you are using Portage rather than Entropy). 

===System Requirements===
* '''Live Environment - No 3D Desktop''':
** ''i686'' Processor
** at least ''512 MB'' of RAM (1 GB suggested)
** a ''2D'' graphics card
** a ''[http://en.wikipedia.org/wiki/Display_Data_Channel DDC] capable Monitor''
** ''mouse'' and ''keyboard''

* '''Live Environment - 3D Desktop''':
** ''i686'' Processor (starting from AMD K6 and Intel Pentium II)
** at least ''512 MB'' of RAM (1 GB suggested)
** an '''[http://en.wikipedia.org/wiki/OpenGL OpenGL] capable 3D graphics card''' (mostly NVIDIA, ATI, Intel, VIA)
** a ''[http://en.wikipedia.org/wiki/Display_Data_Channel DDC] capable Monitor''
** ''mouse'' and ''keyboard''

* '''Installation''':
{{Note| Please note that the Requirements indicated for Installation may be a bit too low for some Desktop Environments.
A full KDE Desktop for example, CAN run with only 1 GB RAM, but you will most likely run out of memory during a session, especially when running large programs, such as firefox, thunderbird and/or libreoffice. Please keep that in mind.}}
** ''i686'' Processor
** at least ''512 MB'' of RAM (1 GB suggested for decent eyecandy effects)
** an '''[http://en.wikipedia.org/wiki/OpenGL OpenGL] capable 3D graphics card''' (mostly NVIDIA, ATI, Intel, VIA)
** ''20'' GB of free space, that is bare minimum DVD Install. ''30+'' GB is highly recommended.
** ''8 GB'' of free space for miniCD. 10+ GB is recommended
** ''Internet connection'' (not mandatory but highly suggested)
** a ''[http://en.wikipedia.org/wiki/Display_Data_Channel DDC] capable Monitor''
** ''mouse'' and ''keyboard'' 

=== What Editions are available in Sabayon Linux? ===

Sabayon is all about choice. You have many flavors to choose from.

You can download them from the mirrors, here:
* [http://www.sabayon.org/mirrors Sabayon Mirrors Page]

The following choices are the main releases available in 32Bit (x86) or 64Bit (amd64):
{{Note| "amd64" is also suitable for '''Intel''' based 64bit Processors}}
1. KDE
2. Gnome
3. LXDE
4. MATE
5. XFCE
6. Enlightenment
All of the above mentioned Desktop Environments are fully-featured.

7. CoreCDX
CoreCDX is a minimal install for those wishing to configure the system more to their liking,
(for more advanced users) in 32bit or 64bit., and uses the Fluxbox Window Manager.

=== How can I contribute to, or support Sabayon Linux ===
There are several ways to contribute:

* The Sabayon foundation is always looking for funds.
For more information, see: http://www.sabayon.org/donate
* Translations.
We are always looking for translators. For the Wiki, as well as translating Sabayon into your native language. 

You may subscribe to our wonderful Wiki, and translate the articles into your own Language, or write your own articles about some area of working with Gnu/Linux. 

If you want to translate Sabayon into your own language, please see:
[[En:HOWTO: Translate Sabayon]] 

If you want to translate the Wiki articles into your own language, please see:
[[En:Translations]] and [[Editing_Guidelines]] 

* Subscribe to our Forum
Help out others with problems. Perhaps problems you've had once too, 
and know the answer or a solution.
http://forum.sabayon.org/ 

* Join us on Facebook or Google+
There are lots of Discussions going on on facebook and Google+. Want to help out, or participate? 
https://www.facebook.com/groups/36125411841/ 
https://plus.google.com/+sabayon/posts 

*setup more download mirrors
We need more mirrors! 

Check out this link to learn more about what it takes to mirror the Sabayon Linux project.
http://wiki.sabayon.org/index.php?title=Mirroring_Sabayon 

=='''The liveCD/DVD'''==
===Should I get the 32-bit or the 64-bit edition?===
This is a never-ending, debatable question. For new users, 32-bit is easier to operate as 64-bit may be a bit fussier. Everything should work in 64-bit as the 32-bit version. Keep in mind that you are still using mostly 32-bit applications. The average desktop user is not going to see benefits over the 32-bit. I suggest to people to try both and see for themselves. In my experience I see most new people picking the 32-bit version. You can certainly Google for more information on this debate.
64bit would seem to be the direction things are going in, though most applications are still in 32bit. 64bit has gotten more support these days and become more widespread in use. 64bit is currently more secure, however most 64bit systems use multi libraries. multi libraries allow you to use both 64 and 32bit apps. A 64bit system using multi libraries will have a certain amount of vulnerability as a 32 bit system.

===Can I install without having to burn the ISO to CD or DVD?===
Yes, you can [http://www.sabayonlinux.org/forum/viewtopic.php?f=50&t=12023 install if you don't have a CD or DVD burner.] Another way, if your computer can boot USB pen drives, is to use UNetbootin or similar to install the Sabayon Linux ISO to a pen drive and create a bootable pen drive (think of it as a fast LiveCD/DVD). Then you can boot the pen drive to get to a Live desktop, and install Sabayon Linux from there, just as you would from a LiveCD/DVD.

=== burning / checking the .iso image ===

One of the most common problems with burning a Linux install CD/DVD is that people sometimes don't understand that an iso image file is not a normal file. You cannot just burn the iso to disc to and expect it to work. I repeat: '''you cannot simply put the iso file on a blank disk and expect it to work'''. In order to properly make a CD or DVD out of an iso image, you need special software. Instructions for Nero and Isorecorder are included; for other programs, see the manual for the software, or just give one of these a shot.

With Nero you just select file and burn image, then select the .iso file you want to burn. The software handles the rest.

If you're looking for a good, alternative freeware solution, you can download a free image burner.

isorecorder [http://isorecorder.alexfeinman.com/isorecorder.htm] Simply download and install the correct version for your version of windows, then right click on the .iso and tell it to burn.

=== checking the integrity of the burned disc ===

Many people know they can check if a downloaded ISO file is OK by comparing the md5sum of the ISO file against the md5sum posted on the SL mirrors. For example:

{{Console| <pre class="clear">
# md5sum -c SabayonLinux-x86_64-3.4f.iso.md5
SabayonLinux-x86_64-3.4f.iso: OK
</pre>}}

cf. the contents of ftp://bo.mirror.garr.it/mirrors/sabayonlinux/SabayonLinux-x86_64-3.4f.iso.md5 which are:
645600788920443b372baae3544acffa SabayonLinux-x86_64-3.4f.iso

so the ISO I downloaded was good.

Remember - verify the MD5 sum for the version of Sabayon that you downloaded - they are all different. The MD5s can be found on the mirrors listed at: http://www.sabayonlinux.org/mirrors

But a different method is needed to verify the '''integrity''' of the LiveDVD/CD itself. You should select the verify written data checkbox in K3b before burning the DVD/CD, but if you forgot or still have doubts then the following method can be used to check the integrity of the burnt LiveDVD/CD:

If you only have Windows installed on your HDD, apparently you can use a Windows shareware application, see the following Web page for details:
http://www.mepis.org/docs/en/index.php?title=Checking_the_integrity_of_a_Live_CD

A WARNING:

1. I have not checked if the method for Windows on the above-mentioned Web page actually works, so use it at your own risk.

Under Linux:

Insert the LiveDVD into the optical drive, let the disc spin up and then enter the following three commands:

{{Console| <pre class="clear">
md5sum /dev/cdrom | awk '{print $1}' > md5a.txt
md5sum ~/Sabayon_Linux_8_amd64_K.iso | awk '{print $1}' > md5b.txt
diff -qs md5a.txt md5b.txt
</pre>}}

(Obviously change the path and/or the ISO file name to match your circumstances.)

If you get an error message while the md5sum is reading the disc, there must be something wrong either with the burn or with the optical drive itself.

If you get the message "Files md5a.txt and md5b.txt differ" then the burn was bad.

If you get the message "Files md5a.txt and md5b.txt are identical" then the burn was good.

=== Passwords on live CD/DVD ===

* The root password:
no password is required: just press the Enter key.

* The sabayonuser password:
no password is required: just press the Enter key.

*For older releases (version 6 and earlier) the password for Root is "root" (without the quotes) and the password for Sabayonuser is "sabayonuser" (without the quotes).

=== The Booting process ===

The boot process of the liveCD/DVD should be pretty straight forwarded, just as many other Linux Distrtibutions.

However, you could get into problems, when having hardware that isn't supported by default, for example.

Or having old hardware that the current drivers don't support.

When having a old NVidia card, and you've downloaded the latest ISO, chances are that it will not start the Window Manager/Desktop Environment, but rather present you with a black screen.

There is nothing wrong with the ISO, it is because "nvidia-drivers-304.64" or higher is installed by default.

You can bypass that by hitting ctrl-alt-f1, remove the nvidia-drivers, (nouveau is installed too), and restart xdm., as explained below:

'''Removing latest nvidia-drivers:'''
# Press the "CTRL-ALT-F1" key combination.
"#" is just indicated that you have to be root, so do not include that with the actual commands...
{{Console| <pre class="clear"># su</pre>}}
{{Console| <pre class="clear"># equo remove nvidia-drivers --ask</pre>}}
Check that "x11-drivers/nvidia-drivers" got removed., nothing else... and confirm with "yes"

Restart XDM:
{{Console| <pre class="clear"># /etc/init.d/xdm restart</pre>}}

For a overall view of which cards support what driver., please see: http://www.nvidia.com/object/IO_32667.html

If you wish to be guided through the boot process and the several options it offers, we have a visual walkthrough.

Please see: [[Visual_Tour:_Boot-menu_Sabayon_LiveCD/DVD]]

Workarounds for problematic Hardware, during the boot process are discussed here:

[[Sabayon_Linux#Boot_parameters_and_workarounds_for_problematic_Hardware]]

'''cheatcodes for ATI and nVidia'''

ATI
noddc res=1024x768 refresh=60 opengl=ati
nVidia
noddc res=1024x768 refresh=60 opengl=nvidia

To use the cheatcodes, hit F5 on the boot up screen of the livecd/dvd and add one of the lines above pending on your hardware

see: [[Visual_Tour:_Boot-menu_Sabayon_LiveCD/DVD]]

When you need to edit xorg.conf, or have to create it for special reasons, the following visual tour will show you how to edit Xorg.conf:

[[Visual_Tour:_Part_2_Editing_the_xorg.conf]]

=='''After installation'''==

===What is Entropy or Equo?===
[[Entropy]] is the binary package manager of Sabayon Linux. To install binary packages you use either the command line client [[Equo]] or the newest Graphical GUI [[Rigo]].

A binary package is a file package containing the already-compiled files to install instead of having to compile the source code. Equo, and [[rigo]] handle these files.

===I just installed it, what do I do first?===
This question has always amazed me. Who says there is anything to do? How about just using the operating system and getting familiar with it? Take some time and read the documentation. If you insist on having to do something then emerge --sync && layman -S to update your Portage package list, or, if using Entropy, see [http://wiki.sabayonlinux.org/index.php?title=Entropy#Fresh_Install_-_What_to_do.3F Fresh Install]

===The GUI for managing packages===

[[rigo]] is the GUI for the Entropy package manager.

{{Warning|'''emerge and layman are Portage commands, Portage is not our own package manager but is available to advanced users. Any steps using these commands can be safely ignored'''}}

There are GUIs for the Portage package manager, but they are no substitute for using emerge on the command line.
* Currently we have Kuroo4, and porthole. Kuroo4 seems to be the best, but only available in Portage.
Personally if you have to rely on a GUI, then try to just use it as a browser of Portage, but still use the command line to install your packages. You will save yourself a lot of headaches. Search and gather your information needed with the GUI then open up Konsole or Terminal and install using the emerge command.

===How do I update/install packages?===
There are 2 package managers, Entropy and Portage. It is highly recommended that you choose and only use 1 package manager. Conflicts can arise from mixing both package managers.
Please read the [[Entropy]] page. Entropy is the package manager specially developed for Sabayon Linux. It has a command line interface ([[Equo]]) and a GUI interface ([[Sulfur]]). Equo commands and Sulfur GUI are Entropy and recommended for newer users of Sabayon Linux. Advanced users of Sabayon Linux may wish to use Portage, the package manager developed for Gentoo Linux, on which Sabayon Linux is based. For information on Portage, please read [[HOWTO: The Complete Portage Guide]].

===How do I install several packages?===
For Entropy:
{{Console| <pre class="clear"># equo install foo foo foo foo foo</pre>}}

For Portage:
{{Console| <pre class="clear"># emerge foo foo foo foo foo</pre>}}

The package manager will install each package one after another. Replace foo with actual package name.

===How do I search for a package?===
* For Entropy:
{{Console| <pre class="clear"># equo search foo</pre>}}
or use the [[rigo]] GUI, or use the [http://www.sabayon.org/packages Sabayon Linux Web site's Entropy package search page].
* For Portage:
{{Console| <pre class="clear"># emerge -s foo</pre>}}
or use a GUI such as Kuroo4.
* Via [http://gentoo-portage.com/Browse Gentoo-Portage] or via [http://packages.gentoo.org/ Packages-Gentoo].

'''Using EIX'''
* For Portage:
I highly recommend using eix. It's the best tool you can have at your hands for searching. It is a command line tool, but it is very powerful and will tell you lots of information.
{{Console| <pre class="clear"># emerge eix && eix-update
# eix foo</pre>}}

You can use eix in Entropy too:
{{Console| <pre class="clear"># equo install eix && eix-update
# eix foo</pre>}}

Example output of eix gedit:
{{Console| <pre class="clear"> [I] app-editors/gedit
Available versions: 2.18.2-r1 2.20.3 (~)2.20.4 {acl debug doc python spell xattr}
Installed versions: 2.20.4(07:05:31 AM 12/29/2007)(python -debug -doc -spell -xattr)
Homepage: http://www.gnome.org/
Description: A text editor for the GNOME desktop</pre>}}
Eix has the ability to search Portage and all overlays. Simply edit the /etc/eix-sync.conf file and just add * to it
{{Console| <pre class="clear"># echo '*' >> /etc/eix-sync.conf</pre>}}
Then do:
{{Console| <pre class="clear"># eix-remote update</pre>}}
Now when you search, it will tell where and what overlay a package is in if it is not in the Portage main tree. This will widen your abilities to find packages, as overlays contain a lot of ebuilds too.

http://en.gentoo-wiki.com/wiki/Eix

===Can I emerge 2 packages at same time in Portage?===
Yes you can, but it can and will bog your system down. It's not really recommended.
===How do I update everything at once?===
For Entropy:
{{Console| <pre class="clear"># equo update
# equo upgrade
# equo conf update</pre>}}

See the Sabayon Wiki article [[Entropy]] for details.

{{Warning|'''emerge and layman are Portage commands. Portage is not our package manager but is available to advanced users. Any steps using these commands can be safely ignored'''}}

If you are new to this distro and have no understanding of Portage, we do not recommend this until you get to know how this distro works. This is one of the fastest ways to destroy your system. This distro is not like the other distros that have the big easy button update. For your information though, 'world update' is what Gentoo calls updating your entire system. It looks at your 'world file' and compares it to Portage and then proceeds to update all packages. Following is how:

{{Console| <pre class="clear"># emerge -- sync && layman -S
# emerge -ua world</pre>}}

* [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap3 Maintaining Software]
* [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=5531 Unofficial Guide to World Update]
You've been warned. When you come yelling because your system won't boot, don't expect sympathy.

N.B. The term 'world' is not used in Entropy.

===How do I uninstall a package?===
* For Entropy:
{{Console| <pre class="clear"># equo remove foo</pre>}}
Note - this can remove dependencies.

*For Portage:
{{Console| <pre class="clear"> # emerge -C foo</pre>}}
Note - this will not remove the dependencies. You will need to run [http://en.gentoo-wiki.com/wiki/Gentoo_maintenance#depclean depclean] for that. I stress great caution with depclean, as it means what it says.

===How do I find out which packages depend on a certain package?===
{{Console| <pre class="clear"># equery depends foo</pre>}}
It will tell you all files depending on that package. See [http://www.gentoo.org/doc/en/gentoolkit.xml using gentoolkit] for more information and commands.

===I keep getting !!! ARCH is not set... Are you missing the 'etc/make.profile' symlink?===
In Konsole/Terminal use the '''su''' command to become the root user and then:
* Run the following command: '''eselect profile list'''
* Look for something like: '''default-linux/x86/2007.0/desktop''' and note the number in front of it.
* Then do: '''eselect profile set #''' <--replace the # with the number. In my case it would be '''eselect profile set 6'''
Now you should be good to go again.

===Do I have to download the LiveCD/DVD every time to upgrade?===
No, Sabayon is a rolling release. However in some cases upgrading via live DVD may prove more time efficent.

Entropy:
The equo command makes upgrading easy - see [[Entropy]].

Portage:
Portage is recommended for advanced users that prefer a higher degree of customization. That being said, Gentoo documentation is quite extensive and helpful for those wanting to dive into it.

Always backup your files before doing anything. My personal opinion: backup, fresh install, restore backup.

===How do I check for security updates ?===
It's pretty easy to keep your [http://www.gentoo.org/doc/en/security/security-handbook.xml?part=1&chap=14 system secure.]
Entropy does this for you automatically.

For Portage:
* Open up konsole or terminal and enter the command '''su''' to become the root user.
* Run the command '''glsa-check -t all''' to check your system.
* Then to fix, run '''glsa-check -f $(glsa-check -t all)'''

You can also visit our security wiki for more helpful tips:
* [http://wiki.sabayon.org/index.php?title=En:Security Sabayon Security wiki]

===How do I handle blocked packages?===
This is an issue in Portage. You are going to run into [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap4 packages blocking other packages.] This can happen for several reasons, e.g. a package has been dropped from Portage as it no longer exists or is no longer supported. In most cases you will simply have to remove (uninstall) the package that is blocking the new package. You will want to do some research on this first. Don't take Portage for granted and blindly do as it says without checking out what or why.

Note - latest versions of Portage (version 2.2 and higher) handle most blockages.

===How to handle masked packages?===
A package is complaining that it is [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap5 masked] and cannot install. This is one of those times you want to check why it is masked. A masked package is usually masked to prevent you from busting things. There are several ways a package can be masked. You can still install masked packages by unmasking them, but make sure you find out first why they are masked.

===How do I update the config files?===
As you install stuff, some packages are going to bring in new versions of their config files. These config files are important as they may have new settings for that package that need to be implemented. I stress that is is very, very crucial that you pay attention to these config files. You can change the entire outcome of your installation if you are not careful. Get to know your [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10863 config files.] There are several ways to handle these files:

For Entropy:
{{Console| <pre class="clear"># equo conf update</pre>}}

For Portage:
[http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=4#doc_chap1 dispatch-conf] and [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=4#doc_chap2 etc-update] are probably the most popular ways of handling updates to config files. A GUI tool is [http://etc-proposals.berlios.de/ etc-proposals.]

Please handle these files with care. You can't know these files enough.

===Where do I start to configure my system?===
For Entropy:
All packages are pre-configured remotely as they have been compiled on a remote computer. You do not need to (and cannot) do anything. If a package has been compiled without a specific USE flag that you need, then you will either have to request to the Entropy repository maintainers that the package be rebuilt (file a bug report in [http://bugs.sabayonlinux.org/ bugzilla]) and the new version placed in the Entropy repository, or use Portage to rebuild it yourself.

For Portage:
The file [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578 make.conf] is your heart and soul of your operating system. Learn it, edit it and build a lean, mean machine. Sabayon Linux ships with a generic make.conf that tries to support everything under the sun. You don't need all that stuff and by configuring, you will have lesser issues with Portage and conflicts.

===Where does Portage download the packages to?===
They are downloaded and stored in the directory '''/usr/portage/distfiles/'''

===Where does Entropy download the packages to?===
They are downloaded and stored in the directory '''/var/tmp/entropy/packages/'''
For instance, on my amd64 using Branch 4 they are stored in '''/var/tmp/entropy/packages/amd64/5'''

===How do I clean out Entropy downloaded packages?===

{{Console| <pre class="clear"># equo cleanup</pre>}}
See [http://wiki.sabayonlinux.org/index.php?title=En:List_Of_Equo_Functions Sabayon Wiki page of Equo commands] or equo --help --verbose

=='''Additional'''==
=== How do I get the Desktop Cube thing working?===
The desktop cube and 3D graphics do not work after I installed Sabayon Linux to the hard disk, but do work when I'm using the LiveCD/DVD.

Well, in theory what you see when you run the LiveCD/DVD is what you get when you install Sabayon Linux. So if the 3D desktop was working with the LiveCD/DVD then it should work when you boot your new installation. Well, we know all about theories; it doesn't work for everyone. You can either search in the Sabayon Linux Forums and the Sabayon Wiki for help on how to get the 3D desktop working with your particular model of graphics card, or you can ask in IRC #sabayon.

First thing you need to do: make sure the md5sum is good after you downloaded the .iso file, I can't stress that enough. Make sure you have burnt the CD/DVD as slowly as possible, and enable Burn Verify in your burning application.

You will be asked those two questions every time, so please do this so we don't have to waste bandwidth re-asking. It may seem petty to you to check the md5sum but, without knowing you're starting out with a good ISO file, it's pointless to continue. We can spend weeks troubleshooting and if your md5sum was bad, we just waste a lot of time and it causes a lot of frustration. With a bad md5sum you can still get a bootable working desktop, but may have issues elsewhere. So keep in mind, just because it boots, doesn't mean the ISO file is good. How do I check the md5sum and disk you ask? Well, luckily for you: [[HOWTO: Checking the integrity of a LiveCD or LiveDVD]].

OK, so you made sure the md5sum was good and you burnt the disk at a nice slow speed with Burn Verify enabled. Now we can start looking at other things. Do you have the correct video driver and the latest version of it? That will be the first thing to know.

NVIDIA card owners, the following link will save you hours of frustration. Yes, certain cards require certain drivers: http://en.gentoo-wiki.com/wiki/Nvidia. If you do not know or understand what is 'masking' then please read more (Portage users, see http://dev.gentoo.org/~dang/masked.txt. Entropy users, see [[Entropy#Masking_and_Unmasking_Packages_in_Entropy]].

Our Wiki also has a HowTo get NVIDIA and ATI cards working too, so use the relevant information: [[HOWTO: Get Ati or Nvidia Video Cards working in Sabayon]]. Also search the Sabayon Linux Forums for posts mentioning your card manufacturer and model.

The above method will work for most people, but you will find that maybe it didn't work for you. Why? I don't know. A little bit of research into /etc/X11/xorg.conf can usually resolve the remaining few that have problems. The following link is full of information for AIGLX: http://en.gentoo-wiki.com/wiki/AIGLX/Troubleshooting. Again, only use the information that is relevant. You will want to pay attention to the xorg.conf settings shown on that page and compare it to your xorg.conf so it matches.

Still having problems? Buy a new video card!

If you want to post your special way of how you got it working - please do. Mine just works all the time so I don't have such problems.

===Multimedia===
Does this include support for some privately-owned platforms? Yes, Sabayon Linux supports DVDs, MP3, WMA, AAC, DivX. Moreover, it supports a lot of open platforms, such as Ogg Vorbis, Matroska, Ogg Theora, FLAC, and coder-decoder Xvid.

===Games===
[http://www.sabayonlinux.org/forum/viewforum.php?f=43 Please Visit our Gaming Shed]

===AIGLX===
Q: Is AIGLX available?

A: If your graphics card is capable, then this should work out-of-the-box. If you are having trouble, start with the Gentoo Wiki article http://en.gentoo-wiki.com/wiki/AIGLX/Troubleshooting.

Q: In [[HOWTO: Get Ati or Nvidia Video Cards working in Sabayon]] it states that ATI GPUs can use AIGLX with the closed-source driver FGLRX. Is it feasible? Previously this worked only with XGL and open source DRI (direct giving infrastructure) Radeon driver.

A: AIGLX is supported by both the open-source Radeon driver and the closed-source FGLRX driver. N.B. Not all ATI cards are supported by the closed-source FGLRX driver and must use the Radeon driver. To find out if the closed-source driver supports your ATI card, see the release notes for the relevant version of the FGLRX driver (a.k.a. AMD Catalyst driver for Linux).

===3D Desktop/Compiz Questions===
'''The cube was working on LiveCD/DVD but doesn't on install, now what?'''

Well, now it's getting difficult as we need to [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=11723 check more things.] You will need the assistance of the Sabayon Linux Forum or IRC to help. I recommend you try and find the source of your problem first. When logged in, open a Konsole/Terminal window and type in the command fusion-icon and see what the error message is in the Konsole/Terminal. You will need to post that error message with your request for help. Make sure you have installed the latest video drivers for your video card also.

'''How do I update Compiz-Fusion to latest Dev. Version?'''

We have a [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=9882 guide on the forum] that is maintained to keep up with the changes in Compiz-Fusion development. This is for Portage users.

'''How do I know if my card will work with Compiz-Fusion?'''

We have a [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=8773 card list] that the community has reported on if their card works or not. It's not a complete list, but a good list to reference.

'''Where can I get more help on Compiz-Fusion?'''

I would suggest their [http://forum.compiz-fusion.org/ support forum.]

===How do I install KDE 4.x.x with Equo?===

{{Console| <pre class="clear"># equo install kde-meta-4.x.x</pre>}}

Replace the x's with the version of KDE you want to install.

===How Do I enable Autologin?===
The real question is, do you really want to? If yes, you should get a hammer and hit yourself in the head repeatedly. Logging in, especially logging in as user, not root, is a very basic but powerful security measure. Hostile programs cannot be autorun on your system if you log in as user. Also no one can accidently/purposefully find your collection of porn, google searches, or downloaded emails simply by pushing the power button if you set a user with password.
[http://wiki.sabayonlinux.org/index.php?title=En:HOWTO:_Setting_Up_Autologin Please see our Wiki page for how to do this.]

===How Do I change the positioning of notifications?===
By default the sabayon gnome version comes with [https://launchpad.net/notify-osd notify-osd]. This is developed by Canonical and
Mark Shuttleworth says the positioning won't be configurable [http://www.markshuttleworth.com/archives/265#comment-316838].
So if you want the notifications to appear in another corner you'll have to uninstall notify-osd and install [http://www.galago-project.org/news/index.php notification-daemon].
After that you will be able to configure the positioning with {{Console| $ notification-properties}}

===Networking Questions===
'''How do I find out what network card I have?'''

As root user, enter the command '''lspci''' in a Konsole or Terminal window. That will list hardware; look for your Ethernet controller.

'''How do I set-up my network?'''

Well, hopefully the LiveCD/DVD recognizes your network card, and NetworkManager sets your network up for you. If it doesn't, try running the command as root: simply '''su''' and run '''net-setup'''. You're going to want to consult the [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4 Gentoo Networking section.]

'''I can ping my router but can't access the Internet'''

You're probably having DNS issues. You need to edit the file /etc/resolv.conf and enter the correct DNS, then restart your network. If you don't know what to use for DNS, use 4.2.2.2

===Sound Questions===
'''I have no sound, what do I do?'''

* Let's see if you computer detects your sound card so, from a command line, use '''su''' to become root user, and run '''alsaconf''' - hopefully your card shows up and all you have to do is select and go.
* After running that, you can use '''alsamixer''' to adjust your sound settings. Press F6 to select your card in ALSAMixer and make sure no channels are muted and that the channel volumes are turned up.
* [http://wiki.sabayon.org/index.php?title=HOWTO:_Resolve_Problems_with_HDA-Intel_Sound_Cards If you have HDA-Intel Card, Please see this HowTo]

'''How can I determine what sound card I have?'''

As root user run the command '''lspci | grep -i audio'''

'''How do I install the alsa-driver instead of having it in the kernel?'''

Sabayon Linux comes with ALSA built into the kernel. You can't install the alsa-drivers while ALSA is built into the kernel. You have to remove ALSA from the kernel before you install the alsa-driver package. So use the '''su''' command to become the root user, and then enter the following commands:

{{Console| <pre class="clear">
# cd /usr/src/linux
# make menuconfig
# make && make modules_install
# cp arch/i386/boot/bzImage /boot/kernel_name <--replace kernel_name with the actual name of kernel
</pre>}}

* Reboot

{{Console| <pre class="clear">
# emerge alsa-driver
</pre>}}
* More info: [http://www.gentoo.org/doc/en/alsa-guide.xml Gentoo ALSA Guide.]

'''Why do I have to run alsaconf every time I reboot?'''

This usually happens if you have more than one sound card in your machine. Many people have an on-board sound card and then stick in a better sound card. Disable your on-board sound card via your BIOS and when you run alsaconf again, ALSA will restore your sound each time you reboot.

===Video Questions===
'''My NVIDIA card is a legacy card, what driver do I need?'''

You will need to compare your card with the information below to find out which driver is best for your card:
* [http://en.gentoo-wiki.com/wiki/Nvidia Check out the Nvidia Howto]
* [http://www.gentoo.org/doc/en/nvidia-guide.xml Also the Nvidia Guide]

'''I need help with my AMD/ATI card!'''

I don't have ATI so I can't supply much help here, but I can point you to:
* [http://en.gentoo-wiki.com/wiki/Graphics_drivers#AMD.2FATI Howto Ati Drivers]
* [http://www.gentoo.org/doc/en/ati-faq.xml Gentoo FAQ on ATI]

===How do I setup AIGLX with my ATI?===
* [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=12438 HOWTO AIGLX with ATI and Sabayon 3.5]

'''How do I setup Dual Monitors?'''

Personally I use twin view and it works great with Compiz-Fusion also. Check out the [http://en.gentoo-wiki.com/wiki/Dual_Monitors Gentoo Wiki article X.Org/Dual Monitors]

'''Video Worked on LiveCD/DVD, but not once install. Options?'''

If your video was fine on the LiveCD/DVD I would boot the LiveCD/DVD and copy the xorg.conf from it to your hard drive install. There are several ways to do this.

* Option 1 - Boot up and browse to /etc/X11/ and copy the file xorg.conf to your installed version. You should be able to access your installed version through the /media directory so it may be something like /media/mydrive/etc/X11/ Reboot the computer and you should have what you had on the LiveCD/DVD. Always backup your files before overwriting.
* Option 2 - Boot up and browse to /etc/X11/xorg.conf and use something like http://www.pastebin.ca to paste your xorg.conf file there. Note the URL so that when you reboot to your installed version you can access it. Then just rename your existing xorg.conf and make a new one with the one you pasted.
* If you still don't have any luck, we may need to look at your drivers. Try reinstalling your video drivers, but, before reinstalling, make sure you are getting the latest drivers. NVIDIA users, make sure you are using the proper drivers for your card. See Question 1 under Video Questions.

===How do I know what Version of Sabayon I installed?===

{{Console| <pre class="clear">
# cat /etc/sabayon-release
</pre>}}
N.B. Sabayon Linux is a 'rolling release' distro. Therefore, if you have upgraded your installation via Entropy or Portage then your installation will no longer be the version recorded in /etc/sabayon-release, as that file tells you the version of the LiveCD/DVD that you used to install Sabayon Linux.

=='''Help and Support Questions'''==

'''How Do I get Log files to get better support?'''

With the package app-misc/sabayonlive-tools, you can easily gather important information to help you debug and provide vital information for the support team to help you. [http://forum.sabayonlinux.org/viewtopic.php?f=60&t=15530 Please see this thread to learn how].

'''Where Do I file a Bug Report?'''

Please use our [http://bugs.sabayonlinux.org/ bugzilla]

'''Where can I get help?'''

Are you lost and confused? There are a lot of great resources out there. I highly encourage you to do some searching first before running into IRC or the Forum and making the same post that has already been posted 100 times. It gets really old answering the same question day in and day out when it's so well documented.
* [http://www.sabayonlinux.org/forum/index.php Sabayon Linux Forum]
* [http://www.sabayonlinux.org/wiki/ Sabayon Linux Wiki]
* [http://www.gentoo.org/doc/en/handbook/index.xml Gentoo Handbook]
* [http://gentoo-wiki.com/Official_Gentoo_Documentation Official Gentoo Documentation]
* [http://gentoo-wiki.com/Main_Page Gentoo Wiki]
* [http://gentoo-portage.com/Browse Gentoo Portage]
* [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1 A Portage Introduction]
* irc.freenode.net in channel #Sabayon also on desktop Get Live Help -- note to IRC users, be human and have patience. Do not paste errors in the room either. To paste messages in IRC, use [http://pastebin.ca/ pastebin.ca], [http://www.sabayon.org/pastebin] or your favorite pasting site. Then simply give the URL for your pasted text so others can view your error. The people in IRC are not paid to be there, they do it out of dedication, so treat them nicely. Trolling, stupidity, and rudeness will get you banned. Also note that the IRC room is not there to teach you Linux or hold your hand. Don't be lazy, do your part too.
* Quick note when pasting error messages - Do not paste the error message alone: everyone thinks that ERROR: x11-base/xgl-0.0.1_pre20070915 failed is the error, it's not. The error is above that. Post the entire build log so we don't have to waste time waiting for you to post back with the actual error. If you read below the ERROR: it even says to paste the uppermost error and call stack if relevant.

En:FAQ

2013-03-07T22:27:03Z

Aposteeltje: /* The GUI for managing packages */

{{I18n| [[Ca:FAQ|ca]] [[En:FAQ|en]] [[Es:FAQ|es]] [[It:FAQ|it]]}}

=FAQs=

=='''General Questions regarding Sabayon Linux'''==
===What is Sabayon Linux===
Sabayon Linux is a pre-configured distribution with the tenets of Performance, Versatility, and Stability, based on the source-based distribution named Gentoo Linux, a particularly customizable distribution. If you have other questions on Gentoo and its philosophy, I request you visit their website: http://gentoo.org. 
In particular, Sabayon emanates substantially from Gentoo's testing branch, one of the most popular source-based Linux distributions, which is about on par with Debian's unstable branch called Sid. Though based on the bleeding edge, you will find Sabayon is quite stable and perhaps more cutting edge than many. Although both Sabayon and Gentoo are rolling releases, Sabayon will have release snapshots. 

===How is Sabayon Linux maintained?===
As Ubuntu uses some of the packages from Debian, so Sabayon receives its packages from Gentoo. 
Sabayon, when using the package manager "Entropy" is binary based. Currently Sabayon has about 10,000 packages in Entropy. And when Sabayon is using the package manager "Portage", it is source based. The Gentoo repository is quite huge. 

===What is the difference between source-based and binary based distribution?===
Most distros, such as Ubuntu, Debian, Red Hat, Fedora and SUSE, install binary packages. Simply put, a binary package is the pre-compiled program, compiled on another computer and made available for download and installation on other computers. 
A source-based distro is one that compiles its programs from source code on the target computer at the time of installation, rather than relying on others to compile and package them. Source-based distros generally also have in their repositories some binary (pre-compiled) packages; these will be the large programs such as LibreOffice, the reason being that the compilation of these can take several hours. 
'''overlays'''
* Overlay: We have our own Portage overlay for ebuilds. Ebuilds are script files that contain instructions for the Portage package manager on how to install the package from its source code.
* Performance: We have modified the Portage make.conf file in order to ensure that our distribution will run at higher speed on newer computers and as fast as possible on older computers.
* Variability: Again, we have modified make.conf in order to cater to a wide spectrum of hardware, using the x86 and amd64 (x86_64) processor architectures.
* Entropy: We have a binary manager that can be used as the one, unique package manager. It functions also with Portage so that you can use them both if you are an experienced user. The Entropy binary packages are ready-built and can be installed immediately without the need to compile anything from the source code.
* The main branch of Gentoo is considered Gentoo stable. Sabayon is based on Gentoo's testing branch.
* Sabayon has different versions ready for quick and pain free installation. The Gentoo installation is done from the ground up, relying on you to make all the configuration choices.
* Gentoo has '''use''' flags. Sabayon will ignore '''use''' flags when using Entropy, but will apply the '''use''' flags when using portage. 

===Why choose Sabayon Linux ?===
1. Variety
Sabayon has multiple editions to choose from. From a variety of desktops to a variety of packages and installations that can enjoyed by new linux users as well as by power users who prefer a higher level of customization.
2. Sabayon is a rolling release.
Once installed you should not need to reinstall a new updated version, since you can use the update tools. Entropy is a GUI tool and front-end for the text console based Equo. This allows you to have the latest and greatest packages available to you, at all times.
3. The Anaconda installer.
The Anaconda installer in Sabayon greatly simplifies installation including disk partition setup and disk encryption, if desired or required.
4. Choice of package managers and repositories.
Sabayon's package manager Entropy is binary and currently contains about 10,000 packages in its repositories. Gentoo's package manager Portage is source based and has a quite huge repo.
5. Support.
Sabayon is highly active and well maintained. You can find help through our forums, live help, and the ever-growing wiki.
6. Look and feel.
Sabayon is generally considered one of the more visually attractive Linux distros. From the installer, to the desktops, and even down to the terminal which has a useful color scheme applied to make any work on the command line pleasing to the eye and easy to understand.
7. Using Sabayon helps to save the world
Test results have shown that using Sabayon Linux '''improves''' the economy; '''helps''' reduce global warming; is generally '''good''' for the environment; '''promotes''' world peace; and helps to fight off '''alien invasive''' species from other galaxies. It is also shown to be helpful in '''improving''' the health of your sense of '''humor''', which is important to keep from bashing your head on the key board during difficult moments. (Test results have been claimed to vary, but number 7 is considered an attempt at '''humor'''.) 

===Should I use Sabayon as a source-based or binary based distribution?===
Sabayon Linux has two package managers: [[Entropy]] (binary packages) and Portage (source packages). As you can install binary packages instead of source code-based packages, Sabayon Linux offers users a choice and the best of both worlds. The binary packages in the Entropy repository have been built by using the Portage package manager and then packaged using Entropy packaging tools on that computer. The binary packages are stored in the Entropy repository and you install them on your computer by using either the [[Equo]] command line client or the [[Rigo]] GUI client. As the release time and date of packages are a little different between the 2 package managers it is recommended to use one package manager consistently to avoid conflicts.

Generally, using Entropy with binary packages is recommended to new users and those who just want everything to work easily.

Portage(source based) is recommended for more advanced users who wish to customize their installation to a higher degree.

There are two main advantages to source-based distributions:
# Firstly, source-based distros often have the newest software before binary distros do. This is due mainly to the fact that rather than having to compile a package and then test it on different machines, all that is required in Sabayon Linux is a file telling it where to find the source code and how to compile it.
#Secondly, undoubtedly a program will eventually have a feature you don't need, and will just take up space or slow down the program. In a binary distro, you're stuck with this feature. In a source-based distro you have the option of removing unwanted features at the time of compilation (assuming you are using Portage rather than Entropy). 

===System Requirements===
* '''Live Environment - No 3D Desktop''':
** ''i686'' Processor
** at least ''512 MB'' of RAM (1 GB suggested)
** a ''2D'' graphics card
** a ''[http://en.wikipedia.org/wiki/Display_Data_Channel DDC] capable Monitor''
** ''mouse'' and ''keyboard''

* '''Live Environment - 3D Desktop''':
** ''i686'' Processor (starting from AMD K6 and Intel Pentium II)
** at least ''512 MB'' of RAM (1 GB suggested)
** an '''[http://en.wikipedia.org/wiki/OpenGL OpenGL] capable 3D graphics card''' (mostly NVIDIA, ATI, Intel, VIA)
** a ''[http://en.wikipedia.org/wiki/Display_Data_Channel DDC] capable Monitor''
** ''mouse'' and ''keyboard''

* '''Installation''':
{{Note| Please note that the Requirements indicated for Installation may be a bit too low for some Desktop Environments.
A full KDE Desktop for example, CAN run with only 1 GB RAM, but you will most likely run out of memory during a session, especially when running large programs, such as firefox, thunderbird and/or libreoffice. Please keep that in mind.}}
** ''i686'' Processor
** at least ''512 MB'' of RAM (1 GB suggested for decent eyecandy effects)
** an '''[http://en.wikipedia.org/wiki/OpenGL OpenGL] capable 3D graphics card''' (mostly NVIDIA, ATI, Intel, VIA)
** ''20'' GB of free space, that is bare minimum DVD Install. ''30+'' GB is highly recommended.
** ''8 GB'' of free space for miniCD. 10+ GB is recommended
** ''Internet connection'' (not mandatory but highly suggested)
** a ''[http://en.wikipedia.org/wiki/Display_Data_Channel DDC] capable Monitor''
** ''mouse'' and ''keyboard'' 

=== What Editions are available in Sabayon Linux? ===

Sabayon is all about choice. You have many flavors to choose from.

You can download them from the mirrors, here:
* [http://www.sabayon.org/mirrors Sabayon Mirrors Page]

The following choices are the main releases available in 32Bit (x86) or 64Bit (amd64):
{{Note| "amd64" is also suitable for '''Intel''' based 64bit Processors}}
1. KDE
2. Gnome
3. LXDE
4. MATE
5. XFCE
6. Enlightenment
All of the above mentioned Desktop Environments are fully-featured.

7. CoreCDX
CoreCDX is a minimal install for those wishing to configure the system more to their liking,
(for more advanced users) in 32bit or 64bit., and uses the Fluxbox Window Manager.

=== How can I contribute to, or support Sabayon Linux ===
There are several ways to contribute:

* The Sabayon foundation is always looking for funds.
For more information, see: http://www.sabayon.org/donate
* Translations.
We are always looking for translators. For the Wiki, as well as translating Sabayon into your native language. 

You may subscribe to our wonderful Wiki, and translate the articles into your own Language, or write your own articles about some area of working with Gnu/Linux. 

If you want to translate Sabayon into your own language, please see:
[[En:HOWTO: Translate Sabayon]] 

If you want to translate the Wiki articles into your own language, please see:
[[En:Translations]] and [[Editing_Guidelines]] 

* Subscribe to our Forum
Help out others with problems. Perhaps problems you've had once too, 
and know the answer or a solution.
http://forum.sabayon.org/ 

* Join us on Facebook or Google+
There are lots of Discussions going on on facebook and Google+. Want to help out, or participate? 
https://www.facebook.com/groups/36125411841/ 
https://plus.google.com/+sabayon/posts 

*setup more download mirrors
We need more mirrors! 

Check out this link to learn more about what it takes to mirror the Sabayon Linux project.
http://wiki.sabayon.org/index.php?title=Mirroring_Sabayon 

=='''The liveCD/DVD'''==
===Should I get the 32-bit or the 64-bit edition?===
This is a never-ending, debatable question. For new users, 32-bit is easier to operate as 64-bit may be a bit fussier. Everything should work in 64-bit as the 32-bit version. Keep in mind that you are still using mostly 32-bit applications. The average desktop user is not going to see benefits over the 32-bit. I suggest to people to try both and see for themselves. In my experience I see most new people picking the 32-bit version. You can certainly Google for more information on this debate.
64bit would seem to be the direction things are going in, though most applications are still in 32bit. 64bit has gotten more support these days and become more widespread in use. 64bit is currently more secure, however most 64bit systems use multi libraries. multi libraries allow you to use both 64 and 32bit apps. A 64bit system using multi libraries will have a certain amount of vulnerability as a 32 bit system.

===Can I install without having to burn the ISO to CD or DVD?===
Yes, you can [http://www.sabayonlinux.org/forum/viewtopic.php?f=50&t=12023 install if you don't have a CD or DVD burner.] Another way, if your computer can boot USB pen drives, is to use UNetbootin or similar to install the Sabayon Linux ISO to a pen drive and create a bootable pen drive (think of it as a fast LiveCD/DVD). Then you can boot the pen drive to get to a Live desktop, and install Sabayon Linux from there, just as you would from a LiveCD/DVD.

=== burning / checking the .iso image ===

One of the most common problems with burning a Linux install CD/DVD is that people sometimes don't understand that an iso image file is not a normal file. You cannot just burn the iso to disc to and expect it to work. I repeat: '''you cannot simply put the iso file on a blank disk and expect it to work'''. In order to properly make a CD or DVD out of an iso image, you need special software. Instructions for Nero and Isorecorder are included; for other programs, see the manual for the software, or just give one of these a shot.

With Nero you just select file and burn image, then select the .iso file you want to burn. The software handles the rest.

If you're looking for a good, alternative freeware solution, you can download a free image burner.

isorecorder [http://isorecorder.alexfeinman.com/isorecorder.htm] Simply download and install the correct version for your version of windows, then right click on the .iso and tell it to burn.

=== checking the integrity of the burned disc ===

Many people know they can check if a downloaded ISO file is OK by comparing the md5sum of the ISO file against the md5sum posted on the SL mirrors. For example:

{{Console| <pre class="clear">
# md5sum -c SabayonLinux-x86_64-3.4f.iso.md5
SabayonLinux-x86_64-3.4f.iso: OK
</pre>}}

cf. the contents of ftp://bo.mirror.garr.it/mirrors/sabayonlinux/SabayonLinux-x86_64-3.4f.iso.md5 which are:
645600788920443b372baae3544acffa SabayonLinux-x86_64-3.4f.iso

so the ISO I downloaded was good.

Remember - verify the MD5 sum for the version of Sabayon that you downloaded - they are all different. The MD5s can be found on the mirrors listed at: http://www.sabayonlinux.org/mirrors

But a different method is needed to verify the '''integrity''' of the LiveDVD/CD itself. You should select the verify written data checkbox in K3b before burning the DVD/CD, but if you forgot or still have doubts then the following method can be used to check the integrity of the burnt LiveDVD/CD:

If you only have Windows installed on your HDD, apparently you can use a Windows shareware application, see the following Web page for details:
http://www.mepis.org/docs/en/index.php?title=Checking_the_integrity_of_a_Live_CD

A WARNING:

1. I have not checked if the method for Windows on the above-mentioned Web page actually works, so use it at your own risk.

Under Linux:

Insert the LiveDVD into the optical drive, let the disc spin up and then enter the following three commands:

{{Console| <pre class="clear">
md5sum /dev/cdrom | awk '{print $1}' > md5a.txt
md5sum ~/Sabayon_Linux_8_amd64_K.iso | awk '{print $1}' > md5b.txt
diff -qs md5a.txt md5b.txt
</pre>}}

(Obviously change the path and/or the ISO file name to match your circumstances.)

If you get an error message while the md5sum is reading the disc, there must be something wrong either with the burn or with the optical drive itself.

If you get the message "Files md5a.txt and md5b.txt differ" then the burn was bad.

If you get the message "Files md5a.txt and md5b.txt are identical" then the burn was good.

=== Passwords on live CD/DVD ===

* The root password:
no password is required: just press the Enter key.

* The sabayonuser password:
no password is required: just press the Enter key.

*For older releases (version 6 and earlier) the password for Root is "root" (without the quotes) and the password for Sabayonuser is "sabayonuser" (without the quotes).

=== The Booting process ===

The boot process of the liveCD/DVD should be pretty straight forwarded, just as many other Linux Distrtibutions.

However, you could get into problems, when having hardware that isn't supported by default, for example.

Or having old hardware that the current drivers don't support.

When having a old NVidia card, and you've downloaded the latest ISO, chances are that it will not start the Window Manager/Desktop Environment, but rather present you with a black screen.

There is nothing wrong with the ISO, it is because "nvidia-drivers-304.64" or higher is installed by default.

You can bypass that by hitting ctrl-alt-f1, remove the nvidia-drivers, (nouveau is installed too), and restart xdm., as explained below:

'''Removing latest nvidia-drivers:'''
# Press the "CTRL-ALT-F1" key combination.
"#" is just indicated that you have to be root, so do not include that with the actual commands...
{{Console| <pre class="clear"># su</pre>}}
{{Console| <pre class="clear"># equo remove nvidia-drivers --ask</pre>}}
Check that "x11-drivers/nvidia-drivers" got removed., nothing else... and confirm with "yes"

Restart XDM:
{{Console| <pre class="clear"># /etc/init.d/xdm restart</pre>}}

For a overall view of which cards support what driver., please see: http://www.nvidia.com/object/IO_32667.html

If you wish to be guided through the boot process and the several options it offers, we have a visual walkthrough.

Please see: [[Visual_Tour:_Boot-menu_Sabayon_LiveCD/DVD]]

Workarounds for problematic Hardware, during the boot process are discussed here:

[[Sabayon_Linux#Boot_parameters_and_workarounds_for_problematic_Hardware]]

'''cheatcodes for ATI and nVidia'''

ATI
noddc res=1024x768 refresh=60 opengl=ati
nVidia
noddc res=1024x768 refresh=60 opengl=nvidia

To use the cheatcodes, hit F5 on the boot up screen of the livecd/dvd and add one of the lines above pending on your hardware

see: [[Visual_Tour:_Boot-menu_Sabayon_LiveCD/DVD]]

When you need to edit xorg.conf, or have to create it for special reasons, the following visual tour will show you how to edit Xorg.conf:

[[Visual_Tour:_Part_2_Editing_the_xorg.conf]]

=='''After installation'''==

===What is Entropy or Equo?===
[[Entropy]] is the binary package manager of Sabayon Linux. To install binary packages you use either the command line client [[Equo]] or the newest Graphical GUI [[Rigo]].

A binary package is a file package containing the already-compiled files to install instead of having to compile the source code. Equo, and [[rigo]] handle these files.

===I just installed it, what do I do first?===
This question has always amazed me. Who says there is anything to do? How about just using the operating system and getting familiar with it? Take some time and read the documentation. If you insist on having to do something then emerge --sync && layman -S to update your Portage package list, or, if using Entropy, see [http://wiki.sabayonlinux.org/index.php?title=Entropy#Fresh_Install_-_What_to_do.3F Fresh Install]

===The GUI for managing packages===

[[rigo]] is the GUI for the Entropy package manager.

{{Warning|'''emerge and layman are Portage commands, Portage is not our own package manager but is available to advanced users. Any steps using these commands can be safely ignored'''}}

There are GUIs for the Portage package manager, but they are no substitute for using emerge on the command line.
* Currently we have Kuroo4, and porthole. Kuroo4 seems to be the best, but only available in Portage.
Personally if you have to rely on a GUI, then try to just use it as a browser of Portage, but still use the command line to install your packages. You will save yourself a lot of headaches. Search and gather your information needed with the GUI then open up Konsole or Terminal and install using the emerge command.

===How do I update/install packages?===
There are 2 package managers, Entropy and Portage. It is highly recommended that you choose and only use 1 package manager. Conflicts can arise from mixing both package managers.
Please read the [[Entropy]] page. Entropy is the package manager specially developed for Sabayon Linux. It has a command line interface ([[Equo]]) and a GUI interface ([[Sulfur]]). Equo commands and Sulfur GUI are Entropy and recommended for newer users of Sabayon Linux. Advanced users of Sabayon Linux may wish to use Portage, the package manager developed for Gentoo Linux, on which Sabayon Linux is based. For information on Portage, please read [[HOWTO: The Complete Portage Guide]].

===How do I install several packages?===
For Entropy:
{{Console| <pre class="clear"># equo install foo foo foo foo foo</pre>}}

For Portage:
{{Console| <pre class="clear"># emerge foo foo foo foo foo</pre>}}

The package manager will install each package one after another. Replace foo with actual package name.

===How do I search for a package?===
* For Entropy:
{{Console| <pre class="clear"># equo search foo</pre>}}
or use the [[rigo]] GUI, or use the [http://www.sabayon.org/packages Sabayon Linux Web site's Entropy package search page].
* For Portage:
{{Console| <pre class="clear"># emerge -s foo</pre>}}
or use a GUI such as Portato.
* Via [http://gentoo-portage.com/Browse Gentoo-Portage] or via [http://packages.gentoo.org/ Packages-Gentoo].

'''Using EIX'''
* For Portage:
I highly recommend using eix. It's the best tool you can have at your hands for searching. It is a command line tool, but it is very powerful and will tell you lots of information.
{{Console| <pre class="clear"># emerge eix && eix-update
# eix foo</pre>}}

You can use eix in Entropy too:
{{Console| <pre class="clear"># equo install eix && eix-update
# eix foo</pre>}}

Example output of eix gedit:
{{Console| <pre class="clear"> [I] app-editors/gedit
Available versions: 2.18.2-r1 2.20.3 (~)2.20.4 {acl debug doc python spell xattr}
Installed versions: 2.20.4(07:05:31 AM 12/29/2007)(python -debug -doc -spell -xattr)
Homepage: http://www.gnome.org/
Description: A text editor for the GNOME desktop</pre>}}
Eix has the ability to search Portage and all overlays. Simply edit the /etc/eix-sync.conf file and just add * to it
{{Console| <pre class="clear"># echo '*' >> /etc/eix-sync.conf</pre>}}
Then do:
{{Console| <pre class="clear"># eix-remote update</pre>}}
Now when you search, it will tell where and what overlay a package is in if it is not in the Portage main tree. This will widen your abilities to find packages, as overlays contain a lot of ebuilds too.

http://en.gentoo-wiki.com/wiki/Eix

===Can I emerge 2 packages at same time in Portage?===
Yes you can, but it can and will bog your system down. It's not really recommended.
===How do I update everything at once?===
For Entropy:
{{Console| <pre class="clear"># equo update
# equo upgrade
# equo conf update</pre>}}

See the Sabayon Wiki article [[Entropy]] for details.

{{Warning|'''emerge and layman are Portage commands. Portage is not our package manager but is available to advanced users. Any steps using these commands can be safely ignored'''}}

If you are new to this distro and have no understanding of Portage, we do not recommend this until you get to know how this distro works. This is one of the fastest ways to destroy your system. This distro is not like the other distros that have the big easy button update. For your information though, 'world update' is what Gentoo calls updating your entire system. It looks at your 'world file' and compares it to Portage and then proceeds to update all packages. Following is how:

{{Console| <pre class="clear"># emerge -- sync && layman -S
# emerge -ua world</pre>}}

* [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap3 Maintaining Software]
* [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=5531 Unofficial Guide to World Update]
You've been warned. When you come yelling because your system won't boot, don't expect sympathy.

N.B. The term 'world' is not used in Entropy.

===How do I uninstall a package?===
* For Entropy:
{{Console| <pre class="clear"># equo remove foo</pre>}}
Note - this can remove dependencies.

*For Portage:
{{Console| <pre class="clear"> # emerge -C foo</pre>}}
Note - this will not remove the dependencies. You will need to run [http://en.gentoo-wiki.com/wiki/Gentoo_maintenance#depclean depclean] for that. I stress great caution with depclean, as it means what it says.

===How do I find out which packages depend on a certain package?===
{{Console| <pre class="clear"># equery depends foo</pre>}}
It will tell you all files depending on that package. See [http://www.gentoo.org/doc/en/gentoolkit.xml using gentoolkit] for more information and commands.

===I keep getting !!! ARCH is not set... Are you missing the 'etc/make.profile' symlink?===
In Konsole/Terminal use the '''su''' command to become the root user and then:
* Run the following command: '''eselect profile list'''
* Look for something like: '''default-linux/x86/2007.0/desktop''' and note the number in front of it.
* Then do: '''eselect profile set #''' <--replace the # with the number. In my case it would be '''eselect profile set 6'''
Now you should be good to go again.

===Do I have to download the LiveCD/DVD every time to upgrade?===
No, Sabayon is a rolling release. However in some cases upgrading via live DVD may prove more time efficent.

Entropy:
The equo command makes upgrading easy - see [[Entropy]].

Portage:
Portage is recommended for advanced users that prefer a higher degree of customization. That being said, Gentoo documentation is quite extensive and helpful for those wanting to dive into it.

Always backup your files before doing anything. My personal opinion: backup, fresh install, restore backup.

===How do I check for security updates ?===
It's pretty easy to keep your [http://www.gentoo.org/doc/en/security/security-handbook.xml?part=1&chap=14 system secure.]
Entropy does this for you automatically.

For Portage:
* Open up konsole or terminal and enter the command '''su''' to become the root user.
* Run the command '''glsa-check -t all''' to check your system.
* Then to fix, run '''glsa-check -f $(glsa-check -t all)'''

You can also visit our security wiki for more helpful tips:
* [http://wiki.sabayon.org/index.php?title=En:Security Sabayon Security wiki]

===How do I handle blocked packages?===
This is an issue in Portage. You are going to run into [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap4 packages blocking other packages.] This can happen for several reasons, e.g. a package has been dropped from Portage as it no longer exists or is no longer supported. In most cases you will simply have to remove (uninstall) the package that is blocking the new package. You will want to do some research on this first. Don't take Portage for granted and blindly do as it says without checking out what or why.

Note - latest versions of Portage (version 2.2 and higher) handle most blockages.

===How to handle masked packages?===
A package is complaining that it is [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap5 masked] and cannot install. This is one of those times you want to check why it is masked. A masked package is usually masked to prevent you from busting things. There are several ways a package can be masked. You can still install masked packages by unmasking them, but make sure you find out first why they are masked.

===How do I update the config files?===
As you install stuff, some packages are going to bring in new versions of their config files. These config files are important as they may have new settings for that package that need to be implemented. I stress that is is very, very crucial that you pay attention to these config files. You can change the entire outcome of your installation if you are not careful. Get to know your [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10863 config files.] There are several ways to handle these files:

For Entropy:
{{Console| <pre class="clear"># equo conf update</pre>}}

For Portage:
[http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=4#doc_chap1 dispatch-conf] and [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=4#doc_chap2 etc-update] are probably the most popular ways of handling updates to config files. A GUI tool is [http://etc-proposals.berlios.de/ etc-proposals.]

Please handle these files with care. You can't know these files enough.

===Where do I start to configure my system?===
For Entropy:
All packages are pre-configured remotely as they have been compiled on a remote computer. You do not need to (and cannot) do anything. If a package has been compiled without a specific USE flag that you need, then you will either have to request to the Entropy repository maintainers that the package be rebuilt (file a bug report in [http://bugs.sabayonlinux.org/ bugzilla]) and the new version placed in the Entropy repository, or use Portage to rebuild it yourself.

For Portage:
The file [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578 make.conf] is your heart and soul of your operating system. Learn it, edit it and build a lean, mean machine. Sabayon Linux ships with a generic make.conf that tries to support everything under the sun. You don't need all that stuff and by configuring, you will have lesser issues with Portage and conflicts.

===Where does Portage download the packages to?===
They are downloaded and stored in the directory '''/usr/portage/distfiles/'''

===Where does Entropy download the packages to?===
They are downloaded and stored in the directory '''/var/tmp/entropy/packages/'''
For instance, on my amd64 using Branch 4 they are stored in '''/var/tmp/entropy/packages/amd64/5'''

===How do I clean out Entropy downloaded packages?===

{{Console| <pre class="clear"># equo cleanup</pre>}}
See [http://wiki.sabayonlinux.org/index.php?title=En:List_Of_Equo_Functions Sabayon Wiki page of Equo commands] or equo --help --verbose

=='''Additional'''==
=== How do I get the Desktop Cube thing working?===
The desktop cube and 3D graphics do not work after I installed Sabayon Linux to the hard disk, but do work when I'm using the LiveCD/DVD.

Well, in theory what you see when you run the LiveCD/DVD is what you get when you install Sabayon Linux. So if the 3D desktop was working with the LiveCD/DVD then it should work when you boot your new installation. Well, we know all about theories; it doesn't work for everyone. You can either search in the Sabayon Linux Forums and the Sabayon Wiki for help on how to get the 3D desktop working with your particular model of graphics card, or you can ask in IRC #sabayon.

First thing you need to do: make sure the md5sum is good after you downloaded the .iso file, I can't stress that enough. Make sure you have burnt the CD/DVD as slowly as possible, and enable Burn Verify in your burning application.

You will be asked those two questions every time, so please do this so we don't have to waste bandwidth re-asking. It may seem petty to you to check the md5sum but, without knowing you're starting out with a good ISO file, it's pointless to continue. We can spend weeks troubleshooting and if your md5sum was bad, we just waste a lot of time and it causes a lot of frustration. With a bad md5sum you can still get a bootable working desktop, but may have issues elsewhere. So keep in mind, just because it boots, doesn't mean the ISO file is good. How do I check the md5sum and disk you ask? Well, luckily for you: [[HOWTO: Checking the integrity of a LiveCD or LiveDVD]].

OK, so you made sure the md5sum was good and you burnt the disk at a nice slow speed with Burn Verify enabled. Now we can start looking at other things. Do you have the correct video driver and the latest version of it? That will be the first thing to know.

NVIDIA card owners, the following link will save you hours of frustration. Yes, certain cards require certain drivers: http://en.gentoo-wiki.com/wiki/Nvidia. If you do not know or understand what is 'masking' then please read more (Portage users, see http://dev.gentoo.org/~dang/masked.txt. Entropy users, see [[Entropy#Masking_and_Unmasking_Packages_in_Entropy]].

Our Wiki also has a HowTo get NVIDIA and ATI cards working too, so use the relevant information: [[HOWTO: Get Ati or Nvidia Video Cards working in Sabayon]]. Also search the Sabayon Linux Forums for posts mentioning your card manufacturer and model.

The above method will work for most people, but you will find that maybe it didn't work for you. Why? I don't know. A little bit of research into /etc/X11/xorg.conf can usually resolve the remaining few that have problems. The following link is full of information for AIGLX: http://en.gentoo-wiki.com/wiki/AIGLX/Troubleshooting. Again, only use the information that is relevant. You will want to pay attention to the xorg.conf settings shown on that page and compare it to your xorg.conf so it matches.

Still having problems? Buy a new video card!

If you want to post your special way of how you got it working - please do. Mine just works all the time so I don't have such problems.

===Multimedia===
Does this include support for some privately-owned platforms? Yes, Sabayon Linux supports DVDs, MP3, WMA, AAC, DivX. Moreover, it supports a lot of open platforms, such as Ogg Vorbis, Matroska, Ogg Theora, FLAC, and coder-decoder Xvid.

===Games===
[http://www.sabayonlinux.org/forum/viewforum.php?f=43 Please Visit our Gaming Shed]

===AIGLX===
Q: Is AIGLX available?

A: If your graphics card is capable, then this should work out-of-the-box. If you are having trouble, start with the Gentoo Wiki article http://en.gentoo-wiki.com/wiki/AIGLX/Troubleshooting.

Q: In [[HOWTO: Get Ati or Nvidia Video Cards working in Sabayon]] it states that ATI GPUs can use AIGLX with the closed-source driver FGLRX. Is it feasible? Previously this worked only with XGL and open source DRI (direct giving infrastructure) Radeon driver.

A: AIGLX is supported by both the open-source Radeon driver and the closed-source FGLRX driver. N.B. Not all ATI cards are supported by the closed-source FGLRX driver and must use the Radeon driver. To find out if the closed-source driver supports your ATI card, see the release notes for the relevant version of the FGLRX driver (a.k.a. AMD Catalyst driver for Linux).

===3D Desktop/Compiz Questions===
'''The cube was working on LiveCD/DVD but doesn't on install, now what?'''

Well, now it's getting difficult as we need to [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=11723 check more things.] You will need the assistance of the Sabayon Linux Forum or IRC to help. I recommend you try and find the source of your problem first. When logged in, open a Konsole/Terminal window and type in the command fusion-icon and see what the error message is in the Konsole/Terminal. You will need to post that error message with your request for help. Make sure you have installed the latest video drivers for your video card also.

'''How do I update Compiz-Fusion to latest Dev. Version?'''

We have a [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=9882 guide on the forum] that is maintained to keep up with the changes in Compiz-Fusion development. This is for Portage users.

'''How do I know if my card will work with Compiz-Fusion?'''

We have a [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=8773 card list] that the community has reported on if their card works or not. It's not a complete list, but a good list to reference.

'''Where can I get more help on Compiz-Fusion?'''

I would suggest their [http://forum.compiz-fusion.org/ support forum.]

===How do I install KDE 4.x.x with Equo?===

{{Console| <pre class="clear"># equo install kde-meta-4.x.x</pre>}}

Replace the x's with the version of KDE you want to install.

===How Do I enable Autologin?===
The real question is, do you really want to? If yes, you should get a hammer and hit yourself in the head repeatedly. Logging in, especially logging in as user, not root, is a very basic but powerful security measure. Hostile programs cannot be autorun on your system if you log in as user. Also no one can accidently/purposefully find your collection of porn, google searches, or downloaded emails simply by pushing the power button if you set a user with password.
[http://wiki.sabayonlinux.org/index.php?title=En:HOWTO:_Setting_Up_Autologin Please see our Wiki page for how to do this.]

===How Do I change the positioning of notifications?===
By default the sabayon gnome version comes with [https://launchpad.net/notify-osd notify-osd]. This is developed by Canonical and
Mark Shuttleworth says the positioning won't be configurable [http://www.markshuttleworth.com/archives/265#comment-316838].
So if you want the notifications to appear in another corner you'll have to uninstall notify-osd and install [http://www.galago-project.org/news/index.php notification-daemon].
After that you will be able to configure the positioning with {{Console| $ notification-properties}}

===Networking Questions===
'''How do I find out what network card I have?'''

As root user, enter the command '''lspci''' in a Konsole or Terminal window. That will list hardware; look for your Ethernet controller.

'''How do I set-up my network?'''

Well, hopefully the LiveCD/DVD recognizes your network card, and NetworkManager sets your network up for you. If it doesn't, try running the command as root: simply '''su''' and run '''net-setup'''. You're going to want to consult the [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4 Gentoo Networking section.]

'''I can ping my router but can't access the Internet'''

You're probably having DNS issues. You need to edit the file /etc/resolv.conf and enter the correct DNS, then restart your network. If you don't know what to use for DNS, use 4.2.2.2

===Sound Questions===
'''I have no sound, what do I do?'''

* Let's see if you computer detects your sound card so, from a command line, use '''su''' to become root user, and run '''alsaconf''' - hopefully your card shows up and all you have to do is select and go.
* After running that, you can use '''alsamixer''' to adjust your sound settings. Press F6 to select your card in ALSAMixer and make sure no channels are muted and that the channel volumes are turned up.
* [http://wiki.sabayon.org/index.php?title=HOWTO:_Resolve_Problems_with_HDA-Intel_Sound_Cards If you have HDA-Intel Card, Please see this HowTo]

'''How can I determine what sound card I have?'''

As root user run the command '''lspci | grep -i audio'''

'''How do I install the alsa-driver instead of having it in the kernel?'''

Sabayon Linux comes with ALSA built into the kernel. You can't install the alsa-drivers while ALSA is built into the kernel. You have to remove ALSA from the kernel before you install the alsa-driver package. So use the '''su''' command to become the root user, and then enter the following commands:

{{Console| <pre class="clear">
# cd /usr/src/linux
# make menuconfig
# make && make modules_install
# cp arch/i386/boot/bzImage /boot/kernel_name <--replace kernel_name with the actual name of kernel
</pre>}}

* Reboot

{{Console| <pre class="clear">
# emerge alsa-driver
</pre>}}
* More info: [http://www.gentoo.org/doc/en/alsa-guide.xml Gentoo ALSA Guide.]

'''Why do I have to run alsaconf every time I reboot?'''

This usually happens if you have more than one sound card in your machine. Many people have an on-board sound card and then stick in a better sound card. Disable your on-board sound card via your BIOS and when you run alsaconf again, ALSA will restore your sound each time you reboot.

===Video Questions===
'''My NVIDIA card is a legacy card, what driver do I need?'''

You will need to compare your card with the information below to find out which driver is best for your card:
* [http://en.gentoo-wiki.com/wiki/Nvidia Check out the Nvidia Howto]
* [http://www.gentoo.org/doc/en/nvidia-guide.xml Also the Nvidia Guide]

'''I need help with my AMD/ATI card!'''

I don't have ATI so I can't supply much help here, but I can point you to:
* [http://en.gentoo-wiki.com/wiki/Graphics_drivers#AMD.2FATI Howto Ati Drivers]
* [http://www.gentoo.org/doc/en/ati-faq.xml Gentoo FAQ on ATI]

===How do I setup AIGLX with my ATI?===
* [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=12438 HOWTO AIGLX with ATI and Sabayon 3.5]

'''How do I setup Dual Monitors?'''

Personally I use twin view and it works great with Compiz-Fusion also. Check out the [http://en.gentoo-wiki.com/wiki/Dual_Monitors Gentoo Wiki article X.Org/Dual Monitors]

'''Video Worked on LiveCD/DVD, but not once install. Options?'''

If your video was fine on the LiveCD/DVD I would boot the LiveCD/DVD and copy the xorg.conf from it to your hard drive install. There are several ways to do this.

* Option 1 - Boot up and browse to /etc/X11/ and copy the file xorg.conf to your installed version. You should be able to access your installed version through the /media directory so it may be something like /media/mydrive/etc/X11/ Reboot the computer and you should have what you had on the LiveCD/DVD. Always backup your files before overwriting.
* Option 2 - Boot up and browse to /etc/X11/xorg.conf and use something like http://www.pastebin.ca to paste your xorg.conf file there. Note the URL so that when you reboot to your installed version you can access it. Then just rename your existing xorg.conf and make a new one with the one you pasted.
* If you still don't have any luck, we may need to look at your drivers. Try reinstalling your video drivers, but, before reinstalling, make sure you are getting the latest drivers. NVIDIA users, make sure you are using the proper drivers for your card. See Question 1 under Video Questions.

===How do I know what Version of Sabayon I installed?===

{{Console| <pre class="clear">
# cat /etc/sabayon-release
</pre>}}
N.B. Sabayon Linux is a 'rolling release' distro. Therefore, if you have upgraded your installation via Entropy or Portage then your installation will no longer be the version recorded in /etc/sabayon-release, as that file tells you the version of the LiveCD/DVD that you used to install Sabayon Linux.

=='''Help and Support Questions'''==

'''How Do I get Log files to get better support?'''

With the package app-misc/sabayonlive-tools, you can easily gather important information to help you debug and provide vital information for the support team to help you. [http://forum.sabayonlinux.org/viewtopic.php?f=60&t=15530 Please see this thread to learn how].

'''Where Do I file a Bug Report?'''

Please use our [http://bugs.sabayonlinux.org/ bugzilla]

'''Where can I get help?'''

Are you lost and confused? There are a lot of great resources out there. I highly encourage you to do some searching first before running into IRC or the Forum and making the same post that has already been posted 100 times. It gets really old answering the same question day in and day out when it's so well documented.
* [http://www.sabayonlinux.org/forum/index.php Sabayon Linux Forum]
* [http://www.sabayonlinux.org/wiki/ Sabayon Linux Wiki]
* [http://www.gentoo.org/doc/en/handbook/index.xml Gentoo Handbook]
* [http://gentoo-wiki.com/Official_Gentoo_Documentation Official Gentoo Documentation]
* [http://gentoo-wiki.com/Main_Page Gentoo Wiki]
* [http://gentoo-portage.com/Browse Gentoo Portage]
* [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1 A Portage Introduction]
* irc.freenode.net in channel #Sabayon also on desktop Get Live Help -- note to IRC users, be human and have patience. Do not paste errors in the room either. To paste messages in IRC, use [http://pastebin.ca/ pastebin.ca], [http://www.sabayon.org/pastebin] or your favorite pasting site. Then simply give the URL for your pasted text so others can view your error. The people in IRC are not paid to be there, they do it out of dedication, so treat them nicely. Trolling, stupidity, and rudeness will get you banned. Also note that the IRC room is not there to teach you Linux or hold your hand. Don't be lazy, do your part too.
* Quick note when pasting error messages - Do not paste the error message alone: everyone thinks that ERROR: x11-base/xgl-0.0.1_pre20070915 failed is the error, it's not. The error is above that. Post the entire build log so we don't have to waste time waiting for you to post back with the actual error. If you read below the ERROR: it even says to paste the uppermost error and call stack if relevant.

En:Translations

2013-03-07T22:04:01Z

Aposteeltje:

{{i18n|[[Ca:Translations|ca]] [[De:Translations|de]] [[En:Translations|en]] [[Es:Translations|es]] [[Id: Translations|id]] [[Id_Java:Translations|id_j]] [[It:Translations|it]] [[Ru:Translations|ru]] [[Tr:Translations|tr]] [[Zh:Translations|zh]]}}

To add a translation of an article you should prefix the articles title with the language code that your translating to. For example:

*English: en:Main_Page
*Español: es:Main_Page
*Deutsch: de:Main_Page

You should also change the articles title to reflect the language you are translating to. The same basis applies for any articles you are writing that are not translations i.e. writing an article that doesn't exist yet in any particular language should still have the language code attached.

See below examples:

{|
|-
|[[Image:Trans1.png|right|350px|350px]]

|-
|[[Image:Trans2.png|right|350px|350px]]

-|}
[[Category:Sabayon Wiki|TranslationsEn]]

File:Trans2.png

2013-03-07T21:59:40Z

Aposteeltje:

File:Trans1.png

2013-03-07T21:59:03Z

Aposteeltje:

Installing and configure Compiz Fusion

2013-03-03T23:20:31Z

Aposteeltje:

{{I18n| [[Installing_and_configure_Compiz_Fusion]]}}

In this Tutorial we are showing you how to install, and configure Compiz.

Compiz is a compositing manager, which means that it enhances the overall user interaction by adding fancy effects to your windows, from drop shadows to awesome desktop effects like the Desktop Cube or the Expo view.

By installing the Meta-package, basically everything you need will be installed.., however, for convenience some other packages should be installed also.

Before executing Compiz, you must know that it starts with a empty profile, and therefore must be configured first before starting.

Please follow the steps below, to successfully install/configure Compiz, ready for usage.

* Open your favourite Terminal, and become root.
{|
|-
|[[Image:Compiz1.png|right|350px|350px]]
Install the Compiz meta-package by entering:
{{Console| <pre class="clear">equo install x11-wm/compiz-fusion --ask</pre>}}
Confirm everything by typing: Y

|-
|[[Image:Compiz2.png|right|350px|350px]]
After confirming everything, the packages will be downloaded and installed.

|-
|[[Image:Compiz3.png|right|350px|350px]]
Now Compiz is installed, but not ready yet for usage., for convenience we're also installing:

the unsupported plugins (perfectly safe, but still use at own risk!), Emerald and themes to draw the borders,

and fusion-icon to launch Compiz:

{{Console| <pre class="clear">equo install compiz-plugins-unsupported emerald emerald-themes fusion-icon –ask</pre>}}
Again, confirm everything by typing: Y

|-
|[[Image:Compiz4.png|right|350px|350px]]
When everything is done and installed, next we need to configure Compiz, before executing.

Enter the “ALT-F2” key combination, or a terminal as normal user, and enter:
{{Console| <pre class="clear">ccsm</pre>}}
The Compiz Preferences Window will open.

|-
|[[Image:Compiz5.png|right|350px|350px]]
As you can see here, nothing is enabled yet. But we want to move our windows around, and resize them.,

so scroll down to the end, until you see section “Window Management”

There, we enable the “move window and resize window” plugins, by clicking/marking on the squares.

|-
|[[Image:Compiz6.png|right|350px|350px]]
Next, we would like to have Borders on our windows, so you can expand, minimize or close them.

In order to do so, scroll up a bit, 'till you reached section “Effects”

Enable the “Window Decoration” plugin, by marking the square.

|-
|[[Image:Compiz7.png|right|350px|350px]]
Now it's safe to run Compiz for basic usage. Close Compiz's Preferences Window,

and execute: “Compiz Fusion Icon”, which can be found under System, in the Startup menu,

or by: ALT-F2, and enter: fusion-icon

To choose different borders, right-click fusion-icon in the systray, and select “Emerald Theme Manager”

|-
|[[Image:Compiz8.png|right|350px|350px]]
Select the Border-theme you want. Once selected a theme, it should be applied immediately.

|-
|[[Image:Compiz9.png|right|350px|350px]]
If you're kinda lazy, and think configuring all this is too much effort, simply import a default-profile.

You can download a default profile with the settings enabled, as described above, here:

[[http://dl.dropbox.com/u/63727544/compiz-default-profile compiz-default-profile]]

(right-click the link, and select save as...)

Save it for convenience to your home folder.

right-click the fusion-icon in the systray, and select "Settings Manager"

|-
|[[Image:Compiz10.png|right|350px|350px]]
In the left Pane, click on Preferences.

|-
|[[Image:Compiz11.png|right|350px|350px]]
Click on "import". In the screen that follows, navigate to your home folder, select "all files"

and select the file you have just downloaded.

Changes will be applied immediately. Done.....
|}

If you are new to Compiz, and want to explore the other functions., e.g. what they do, etc.
please see:
[[http://wiki.compiz.org/CCSM Configuration]]

You will be redirected to the Official Compiz Wiki page.

Installing and configure Compiz Fusion

2013-03-03T22:41:44Z

Aposteeltje:

Installing and configure Compiz Fusion

2013-03-03T22:35:22Z

Aposteeltje:

{{I18n| [[Installing_and_configure_Compiz_Fusion]]}}

In this Tutorial we are showing you how to install, and configure Compiz.

Compiz is a compositing manager, which means that it enhances the overall user interaction by adding fancy effects to your windows, from drop shadows to awesome desktop effects like the Desktop Cube or the Expo view.

By installing the Meta-package, basically everything you need will be installed.., however, for convenience some other packages should be installed also.

Before executing Compiz, you must know that it starts with a empty profile, and therefore must be configured first before starting.

Please follow the steps below, to successfully install/configure Compiz, ready for usage.

* Open your favourite Terminal, and become root.
{|
|-
|[[Image:Compiz1.png|right|350px|350px]]
Install the Compiz meta-package by entering:
{{Console| <pre class="clear">equo install x11-wm/compiz-fusion --ask</pre>}}
Confirm everything by typing: Y

|-
|[[Image:Compiz2.png|right|350px|350px]]
After confirming everything, the packages will be downloaded and installed.

|-
|[[Image:Compiz3.png|right|350px|350px]]
Now Compiz is installed, but not ready yet for usage., for convenience we're also installing:

the unsupported plugins (perfectly safe, but still use at own risk!), Emerald and themes to draw the borders,

and fusion-icon to launch Compiz:

{{Console| <pre class="clear">equo install compiz-plugins-unsupported emerald emerald-themes fusion-icon –ask</pre>}}
Again, confirm everything by typing: Y

|-
|[[Image:Compiz4.png|right|350px|350px]]
When everything is done and installed, next we need to configure Compiz, before executing.

Enter the “ALT-F2” key combination, or a terminal as normal user, and enter:
{{Console| <pre class="clear">ccsm</pre>}}
The Compiz Preferences Window will open.

|-
|[[Image:Compiz5.png|right|350px|350px]]
As you can see here, nothing is enabled yet. But we want to move our windows around, and resize them.,

so scroll down to the end, until you see section “Window Management”

There, we enable the “move window and resize window” plugins, by clicking/marking on the squares.

|-
|[[Image:Compiz6.png|right|350px|350px]]
Next, we would like to have Borders on our windows, so you can expand, minimize or close them.

In order to do so, scroll up a bit, 'till you reached section “Effects”

Enable the “Window Decoration” plugin, by marking the square.

|-
|[[Image:Compiz7.png|right|350px|350px]]
Now it's safe to run Compiz for basic usage. Close Compiz's Preferences Window,

and execute: “Compiz Fusion Icon”, which can be found under System, in the Startup menu,

or by: ALT-F2, and enter: fusion-icon

To choose different borders, right-click fusion-icon in the systray, and select “Emerald Theme Manager”

|-
|[[Image:Compiz8.png|right|350px|350px]]
Select the Border-theme you want. Once selected a theme, it should be applied immediately.

|-
|[[Image:Compiz9.png|right|350px|350px]]
If you're kinda lazy, and think configuring all this is too much effort, simply import a default-profile.

You can download a default profile with the settings enabled, as described above, here:

[[http://dl.dropbox.com/u/63727544/compiz-default-profile compiz-default-profile]]

Save it for convenience to your home folder.

right-click the fusion-icon in the systray, and select "Settings Manager"

|-
|[[Image:Compiz10.png|right|350px|350px]]
In the left Pane, click on Preferences.

|-
|[[Image:Compiz11.png|right|350px|350px]]
Click on "import". In the screen that follows, navigate to your home folder, select "all files"

and select the file you have just downloaded.

Changes will be applied immediately. Done.....
|}

If you are new to Compiz, and want to explore the other functions., e.g. what they do, etc.
please see:
[[http://wiki.compiz.org/CCSM Configuration]]

File:Compiz11.png

2013-03-03T21:57:39Z

Aposteeltje:

File:Compiz10.png

2013-03-03T21:55:52Z

Aposteeltje:

File:Compiz9.png

2013-03-03T21:53:15Z

Aposteeltje:

Installing and configure Compiz Fusion

2013-03-03T19:57:09Z

Aposteeltje:

{{I18n| [[Installing_and_configure_Compiz_Fusion]]}}

In this Tutorial we are showing you how to install, and configure Compiz.

Compiz is a compositing manager, which means that it enhances the overall user interaction by adding fancy effects to your windows, from drop shadows to awesome desktop effects like the Desktop Cube or the Expo view.

By installing the Meta-package, basically everything you need will be installed.., however, for convenience some other packages should be installed also.

Before executing Compiz, you must know that it starts with a empty profile, and therefore must be configured first before starting.

Please follow the steps below, to successfully install/configure Compiz, ready for usage.

* Open your favourite Terminal, and become root.
{|
|-
|[[Image:Compiz1.png|right|350px|350px]]
Install the Compiz meta-package by entering:
{{Console| <pre class="clear">equo install x11-wm/compiz-fusion --ask</pre>}}
Confirm everything by typing: Y

|-
|[[Image:Compiz2.png|right|350px|350px]]
After confirming everything, the packages will be downloaded and installed.

|-
|[[Image:Compiz3.png|right|350px|350px]]
Now Compiz is installed, but not ready yet for usage., for convenience we're also installing:

the unsupported plugins (perfectly safe, but still use at own risk!), Emerald and themes to draw the borders,

and fusion-icon to launch Compiz:

{{Console| <pre class="clear">equo install compiz-plugins-unsupported emerald emerald-themes fusion-icon –ask</pre>}}
Again, confirm everything by typing: Y

|-
|[[Image:Compiz4.png|right|350px|350px]]
When everything is done and installed, next we need to configure Compiz, before executing.

Enter the “ALT-F2” key combination, or a terminal as normal user, and enter:
{{Console| <pre class="clear">ccsm</pre>}}
The Compiz Preferences Window will open.

|-
|[[Image:Compiz5.png|right|350px|350px]]
As you can see here, nothing is enabled yet. But we want to move our windows around, and resize them.,

so scroll down to the end, until you see section “Window Management”

There, we enable the “move window and resize window” plugins, by clicking/marking on the squares.

|-
|[[Image:Compiz6.png|right|350px|350px]]
Next, we would like to have Borders on our windows, so you can expand, minimize or close them.

In order to do so, scroll up a bit, 'till you reached section “Effects”

Enable the “Window Decoration” plugin, by marking the square.

|-
|[[Image:Compiz7.png|right|350px|350px]]
Now it's safe to run Compiz for basic usage. Close Compiz's Preferences Window,

and execute: “Compiz Fusion Icon”, which can be found under System, in the Startup menu,

or by: ALT-F2, and enter: fusion-icon

To choose different borders, right-click fusion-icon in the systray, and select “Emerald Theme Manager”

|-
|[[Image:Compiz8.png|right|350px|350px]]
Select the Border-theme you want. Once selected a theme, it should be applied immediately.
|}

If you are new to Compiz, and want to explore the other functions., e.g. what they do, etc.
please see:
[[http://wiki.compiz.org/CCSM Configuration]]

File:Compiz8.png

2013-03-03T19:55:53Z

Aposteeltje:

File:Compiz7.png

2013-03-03T19:54:59Z

Aposteeltje:

File:Compiz6.png

2013-03-03T19:54:07Z

Aposteeltje:

File:Compiz5.png

2013-03-03T19:53:13Z

Aposteeltje:

File:Compiz4.png

2013-03-03T19:52:27Z

Aposteeltje:

File:Compiz3.png

2013-03-03T19:51:36Z

Aposteeltje:

File:Compiz2.png

2013-03-03T19:50:45Z

Aposteeltje:

File:Compiz1.png

2013-03-03T19:49:31Z

Aposteeltje:

Talk:Installing and configure Compiz Fusion

2013-03-03T19:46:28Z

Aposteeltje: Blanked the page

Installing and configure Compiz Fusion

2013-03-03T19:46:08Z

Aposteeltje: Blanked the page

En:Tips

2013-03-03T15:08:39Z

Aposteeltje: /* XScreensaver, The manual */

{{I18n| [[Ca:Tips|ca]] [[De:Tips|de]] [[En:Tips|en]] [[Es:Tips|es]] [[Id:Tips|id]] [[Tr:Tips|tr]]}}

=Tips=

==Resources==

[[Sabayon Linux|Sabayon]] is basically [http://gentoo.org Gentoo] (Gentoo's testing branch)so many things related to Gentoo also apply to Sabayon. With this in mind the following links will be very helpful in solving any problems you may have. Make sure to bookmark them. In particular, Sabayon is based on Gentoo's testing branch which is about on par with Debian's Sid (unstable branch) releases. Though based on the bleeding edge, you will find Sabayon is quite stable and perhaps more cutting edge.

A key difference is Sabayon, when using the package manager Entropy, loads packages in binary form, with thier own dependencies, and use flags can not be set. However, Sabayon when using portage is basically "gentoo testing" and more customizable, also more bleeding edge. . .

*http://en.gentoo-wiki.com/wiki/Main_Page <--- full of howto and everything else
*http://www.gentoo.org/doc/en/ <------- Gentoo Documentation Resources
*http://google.com <--- simply enter the word Gentoo plus your keywords
*http://www.gentoo.org/doc/en/handbook/index.xml <--- Gentoo Handbook
*http://linuxreviews.org/gentoo/emerge/ <--- Emerge User Guide
*http://www.sabayonlinux.org/wiki/index.php?title=Main_Page <--- Sabayon Wiki
*http://www.gentoo-wiki.info/TIP_Converting_from_or_to_Debian <--- Converting from Debian to Gentoo
*http://gentoo-portage.com/Browse <---Browse Portage via Web

Those links will tell anyone what Gentoo is and how to use it. The amount of Gentoo documentation is just unreal, spend sometime searching.

'''kolsyra wrote:'''
Here is a very good site for understanding Linux in general. Very good reading if you lack the fundamental "how Linux works" knowledge but also very entertaining for someone that just wants to know more about Linux:
http://www.linuxtopia.org/online_books/introduction_to_linux/index.html

Sabayon Linux Wiki page with a list of on-line and printed books about Linux:
*http://wiki.sabayon.org/index.php?title=Books

== Easy searching the Sabayon-Forum ==
Sometimes, when searching the Forum on a particular subject, you get the message:
{{Console| <pre class="clear">The following words in your search query were ignored because they are too common words</pre>}}
Instead of using the Forum's search-box, you can use DuckDuckGo search engine:
* https://duckduckgo.com/
If, for example you want to search for '''Xorg''' , enter the following in the Search field:
{{Console| <pre class="clear">xorg site:forum.sabayon.org</pre>}}

The same works for Google-search, too., but vice-versa:
* http://www.google.com
If, for example you want to search for '''Xorg''' , enter the following in the Search field:
{{Console| <pre class="clear">site:forum.sabayon.org xorg</pre>}}

==ERROR: Certificate verification error for xxxxxx==

run:
# emerge ca-certificates
and after that, run again the previous emerge command.

==frozen KDE daemon, menu froze or konqueror not opening==
For Those that are having the frozen KDE daemon, menu froze or konqueror not opening, simply run in konsole - that will work till you reboot:

killall -SIGKILL kded

==For Nvidia Kernel Mismatch==
# emerge -C nvidia-drivers; rmmod nvidia; rm /lib/modules/$(uname -r)/video/nvidia.ko; rm /usr/lib/opengl/nvidia -rf; emerge nvidia-drivers; eselect opengl set nvidia; reboot

==Cheat Codes==

ATI
noddc res=1024x768 refresh=60 opengl=ati
nVidia
noddc res=1024x768 refresh=60 opengl=nvidia

How to use? hit F5 on the boot up screen of the livecd/dvd and add one of the lines above pending on your hardware
More Cheat/Boot Parameters here:
[[En:Sabayon_Linux#Boot_parameters_and_workarounds_for_problematic_Hardware Boot parameters and workarounds for problematic Hardware]]

==FireFox Search Engine Plugins ==

* [https://addons.mozilla.org/en-US/firefox/addon/3682 Firefox Addon] << allows you to add searches easily directly from website - add forum, wiki, etc..

* http://mycroft.mozdev.org/download.html?name=gentoo&sherlock=yes&opensearch=yes&submitform=Search

* [http://forum.sabayon.org/forum/viewtopic.php?t=8536 Sabayon Linux Forum Search Plugin]

==Checking your MD5SUM==

'''Before''' you attempt installing Sabayon (or any Linux distro for that matter) you should check your md5sum. "What on earth is that!?" you may ask. Well, md5sum is an ingenious algorithm which, when you run a string of data through it, will spit out a string of letters and numbers. This string will be totally and completely unique to that data. So in our case, we want to create an md5sum of the Sabayon LiveCD or LiveDVD .iso file.

Why should I go through all the trouble?

Well, when the developers create the master .iso from which all the other .iso's will be copied and distributed the developers calculate an md5sum of that .iso. They then post the results of the md5sum in the release notes. This is so you can verify if the .iso you have downloaded has not been tampered with, or has downloaded correctly.

MANY installation error are a result of folks not checking their md5sums before trying to install. Hey folks, entropy is real! Sometimes bits of a file get lost in the shuffle. Make sure your .iso file is 100% there.

So how on earth do I check this vaunted md5sum.

In Linux it could not be easier:

<code>md5sum /path/to/file.iso</code>

You can then compare the outcome with the official, posted md5sum to verify that you have EXACTLY the same file as lxnay created!

Remember to also verify the integrity of the LiveCD/DVD once you have burned it, to make sure that your burner didn't make any boo boos. The procedure for verifying the integrity of a LiveCD/DVD is given on the following Wiki page:

*[[HOWTO: Checking the integrity of a LiveCD or LiveDVD]]

You can also use K3B to check the md5sum. This is done automatically when you chose to burn a cd or dvd iso image to disc, using this program. Then as before, check it against the published md5sum.

In the windows world? You are trying to jump into the Linuxverse? There are several programs out there for free.
Here is one.[http://www.download.com/3000-2248-10050856.html]

==Installation==

* [[En:Introduction#Installation_Guide:_Step_by_Step|Installation Guide: Step by Step]]

Once you've installed Sabayon, be sure to check out the Package Managers and learn them

[[Entropy ]] and [[HOWTO: The Complete Portage Guide]].

[[Entropy#Fresh_Install_-_What_to_do.3F]]

==Live CD Display is Compressed or Partially Viewable==
When booting from the LiveCD/DVD and your display is extremely small resolution or appears to be compressed or partially viewable try booting with the following command line option:
 
'''res=1024x768'''
 
This will give you a resolution of 1024 by 768. If you need a different resolution just change the height and width to that which you require.

==Useful aliases==
I have gathered information from a few sources to come up with a useful list of aliases that users may want to put into their environment.

'''Goes in $HOME/.bashrc'''

# Lists files in various ways
# -l in single column format, I use this when I want to see the extra attributes about a file
# the addition of 'h' shows file sizes in human readable form
# the addition of 'a' shows hidden files (names starting with '.')
# the addition of 'F' annotates files with addition chars
# feel free to man ls for a more detailed explanation
alias ll='ls -l' # or alias ll='ls -lh'
alias l.='ls -a'
alias ll.='ls -al'
alias ls='ls -aF --color=always'

# Simply renames grep to search
alias search=grep

# Shortcut to mount and unmount your cdrom drive
# ? doesn't this happen automatically on most distros ?
alias mcd='mount /mnt/cdrom'
alias ucd='umount /mnt/cdrom'

# Starts Midnight Commander in colored mode
alias mc='mc -c'

# Directory traversal
# Seems SuSE used to set these by default
alias ..='cd ..'
alias ...='cd ../..'

# Adding the -i will prompt for confirmation which can be good for new
# and unexpected/annoying for more experienced users
alias rm='rm -i'
alias cp='cp -i'
alias mv='mv -i'

# Fixes wrong typing
alias sl='ls'

# Forces modprobe to always be verbose
alias modprobe='modprobe -v'

# Shows all running tasks
alias pm='ps auxw | more'

# Reports disk usage in human readable format
alias df='df -h'

# Create shortcuts to different directories
# alias cda='cd /var/www/localhost/htdocs'

# for some reason, sometimes cpufreqd decides to run the
# CPU at max speed even though the load is 0.01. This
# alias lets me see if that's happening.
alias cur='sed -e "s/000$/ MHz/" < /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq'

# Allows for you to search what you have typed previously
alias gh='history | grep -i'

'''More info at the following'''

[http://safari.oreilly.com/0596009658/bash3-CHP-3-SECT-2 Learning the bash Shell, 3rd Edition]

[http://en.tldp.org/HOWTO/Bash-Prompt-HOWTO/ Bash Prompt HOWTO]

[http://freeunix.dyndns.org:8088/site2/howto/Bash.shtml Customizing your Bash environment]

[http://www.hypexr.org/bash_tutorial.php Getting Started with BASH]

==Restore KDE pager after loading Compiz==
When The standard KDE Desktop is loaded, you will find the pager next to the kick-off starter icon.,

consisting of four little Desktop icons.

However, when you start Compiz, it becomes one big Desktop icon.

This is a known bug at KDE.org, see:

https://bugs.kde.org/show_bug.cgi?id=198105

On that same bug report, they offer a workaround, but only works with a little adjustment.

Here's what you got to do, to get it working:

As normal user, open your favourite terminal, and enter:
{{Console| <pre class="clear">nano -w ~/.kde4/Autostart/plasma-restart.sh</pre>}}
Enter the following text: 
#!/bin/bash
(sleep 10 && kbuildsycoca4 &&
kquitapp plasma-desktop >/dev/null 2>&1 &&
kstart plasma-desktop & >/dev/null 2>&1 &&
exit 0) &

Save the script, by hitting the (CTRL+O) key-combination, and exit the nano editor. (CTRL+X)

Now, we have to make the script executable.

At the terminal, enter:
{{Console| <pre class="clear">chmod +x ~/.kde4/Autostart/plasma-restart.sh</pre>}}
What the script basically does is Forcing the plasma-desktop to restart and restore the 4 little pager buttons,

while compiz is running. The delay of 10 secs. (sleep 10) is necessarily for Compiz to get fully loaded, and then execute the script.

After a reboot, or restarting XDM, you should have Compiz enabled., AND the four little Desktop pager.

==Revdep-Rebuild==
'''Note: Revdep-Rebuild is not for Entropy systems, only for Portage. Entropy users must NEVER run this command.'''


In my travels of Sabayon I have come across many who have let their packages get all too out of date for a revdep-rebuild to fix. I've prepared a short script [http://xelserv.com:81/eclipse/revdep-update.sh here] which overrides the old revdep-rebuild with an optional update feature. You can either keep this somewhere independant of revdep-rebuild, or replace revdep-rebuild with it - it should be able to stand on its own. Look [http://forum.sabayonlinux.org/viewtopic.php?f=54&t=13322&start=0&st=0&sk=t&sd=a here] if there's anything you'd like to know or ask about.

==Editing text files as root==

Some people like to have an ''"Edit as root"'' for text files in right click menu.
The way for do this for konqueror is create a file ended in .desktop (example: ''kwrite.desktop'') in '''/usr/share/apps/konqueror/servicemenus/''' with the following code inside:
{{Console| <pre class="clear">[Desktop Entry]
ServiceTypes=text/*
Actions=EditAsRoot
Encoding=UTF8
X-KDE-Priority=TopLevel

[Desktop Action EditAsRoot]
Name=Edit as root
Icon=kwrite
Exec=kdesu -u root -n --noignorebutton -c 'kwrite %U'</pre>}}

''ServiceTypes=text/*''

Tells what kind of files will be afected by this menu entry. In this case, all text files. You can open kcontrol and take a look in KDE components, file associations for see what you can add. For example, if you want to add also .desktop files (like the one we are creating!), the line will be ''ServiceTypes=text/*,application/x-desktop''

''X-KDE-Priority=TopLevel''

With this line, you will see ''"Edit as root"'' when you do right click. Without that line you will see the option under submenu ''actions''.

==[[Existing Reiser4 partitions - CAREFUL!]]==

==terminal reverse search==

Terminal power users already know that a log of all the commands you execute are kept in history. (Go ahead, type history to see them.)

Well, you can also search your command history as you type, using the very useful Ctrl+R key combination.

In the terminal, hold down Ctrl and press R to invoke "reverse-i-search." Type a letter - like s - and you'll get a match for the most recent command in your history that starts with s. Keep typing to narrow your match. When you hit the jackpot, press Enter to execute the suggested command.

Also, !characters will execute the last command that matches the specified characters. (So !ssh will run the last ssh you used.)

Of course good history search only works if you've got a long history. To extend the length of the history list in your terminal, add the following lines to your .bash_profile:

HISTFILESIZE=1000000000 HISTSIZE=1000000

Once you've got your history built up, you can use this command to see what items you type in the terminal the most. (Great way to decide what aliases you need to set up.)

history|awk '{print $2}'|awk 'BEGIN {FS="|"} {print $1}'|sort|uniq -c|sort -r

The result will be a list of commands you've issued ordered by frequency. This is a fabulous way to identify what commands could use a shorter alias; for example, if I type ssh mylongservername.com 20 times a day, it's worth setting up an alias like sshg to get that done in fewer keystrokes.

==alternative KDE task-manager==

If you have got many tasks in your task-manager you should consider using Smooth-tasks.

This alternative task-manager allows you to just display the icons of a task thus using less space but still maintaining the ability of the user to distinguish the different tasks.

Install smooth-tasks from Entropy.

After installing and substituting it with the original task-manager, you should have a deep look at the settings since they are much broader.

One way of using the features of smooth-tasks could be to only display the icons of tasks and move the panel to the left or right of the screen. This is most useful on widescreens.

'''caution:'''

for those of you who use KDE and will be upgrading to '''KDE 4.8.0''' when it becomes available in Entropy:
If you're using the smooth-tasks widget, it seems that it does not work in '''KDE 4.8.0'''
However, there is a widget called '''Icon-Only Task Manager''' which does basically the same thing. So use that instead.
When using Desktop-effects, rather than Compiz, you have to untick 'Highlight Window' (Kickoff > System Settings > Desktop Effects | 'All Effects' tab), otherwise, when you hover the mouse pointer over the icon on the Panel of a minimised window, both the window preview and the window itself are displayed while the mouse pointer is over the icon.

==Install standalone fonts downloaded from the Internet==

If you downloaded some fonts as standalone files (ie. somefont.ttf) you can install them in 2 ways. If you want to install them for the current user only follow these steps:
# cp somefont.ttf ~/.fonts/
# cd ~/.fonts
# fc-cache

If ~/.fonts does not exists, just create it.

If you want to set the fonts up for the whole system and all the users, copy all of them in /usr/share/fonts/ and run the fc-cache command there as root.

==How to change menu icon in Razor-Qt==

When using Razor-qt you'll find that you can't change the menu icon like we can in KDE.

However, there is still a way to change the default icon into our nice looking Sabayon "foot" logo. :-)
or whatever image you like.

For this to work, we need the commandline, a image editor, and a custom image.

So first we will need to make an image that will work with the main menu.

Next we will edit the image. You can use your preferred image editor, but in this example i will use Gimp.

In Gimp, when the image is loaded, Go to Image >> Scale Image.

Under image size '''make sure''' the width and height '''both''' are '''64'''.

If you put 64 in one and the other changes click on the chain to the right.

Next, click File>Save As... and change the name to: mainmenu.png

Then click on: Select File Type (By Extension) and scroll down to .png and save it in your home directory or wherever you like.


Now we need to backup the existing menu image.
Open the terminal, and become root by entering "su", followed with the "root" password.
backup the existing menu image:
# cp /usr/share/razor/themes/light/mainmenu.png /usr/share/razor/themes/light/backup.mainmenu.png
Replace light with your current theme but light is default.
Then we will need to copy the image you made to that directory.
In this example, i saved the image to my Desktop:
# cp $HOME/Desktop/mainmenu.png /usr/share/razor/themes/light/
That's all.
After log out and back in, you should have a nice picture of your choice as your Menu icon.

==Learning to work with the VI (VIM) editor==

For those who like to learn working with the VI editor, but can't find proper documentation, or doesn't understand the manpage or help function:

VI has a build-in tutor., that will learn you in a interactive way, the ins and outs of VI.

instead of run vi or vim, run:
# vimtutor
at the commandline, and follow the instructions.

While running "vimtutor", you are actually already running VI.
Enjoy learning :-)

==XScreensaver, The manual==

How to automatically run / replace XScreensaver on startup on different desktop environments:

{{Note| In the manual is explained how to replace the KDE-screensaver with xscreensaver.
However, since KDE-4 the path has changed., so the path given in the manual is wrong!!!
The right path should be:
/usr/lib/kde4/libexec/kscreenlocker
Also, you do not have to make it executable anymore. (it already is...)}}

*http://www.jwz.org/xscreensaver/man1.html

En:HOWTOs

2013-03-01T15:15:02Z

Aposteeltje: /* Desktops|Compiz-Fusion| */

{{I18n|[[De:HOWTOs|de]] [[En:HOWTOs|en]] [[Es:HOWTOs|es]] [[It:HOWTOs|it]] [[pl:HOWTOs|pl]] [[tr:HOWTOs|tr]] [[uk:HOWTOs|uk]]}}

=HOWTOs=

==Taking a Tour==
{{See also|[[:Category:Visual Tour]]}}
*[[Visual Tour: Installing Sabayon]]
*[[Visual Tour: Boot-menu Sabayon LiveCD/DVD]]
*[[Visual Tour: Part 2 Editing the xorg.conf]]

==Installation==
{{see also|[[:Category:Installation]]}}
*[[HOWTO: Burn Sabayon from Windows]]
*[[HOWTO: Checking the integrity of a LiveCD or LiveDVD]]
*[[HOWTO: Install Sabayon with GRUB2 and GPT on a New System]]
*[[HOWTO: Manual Partitioning with Sabayon Linux]]
*[[HOWTO: Upgrade kernel using Entropy]]
*[[HOWTO: Advice on the hostname to specify when installing Sabayon Linux]]
*[[HOWTO: Dual boot Sabayon Linux and Windows]]
* [http://wiki.sabayon.org/index.php?title=En:Introduction#Installation_Guide:_Step_by_Step HOWTO: Installation Guide: Step by Step (For new Linux users)]
*[[HOWTO: Install from an existing Linux system]] (aka ''The Gentoo way'' aka ''The chroot way'')

== remove Desktop Environments ==
* HOWTO: [[Remove_KDE]]
* HOWTO: [[Remove_XFCE]]
* HOWTO: [[Remove_Mate]]
* HOWTO: [[Remove_Gnome]]
* HOWTO: [[Remove_RazorQT]]

==Package Management==
{{see also|[[:Category:Package Management]]}}
*[[HOWTO: Safely mix Entropy and Portage]]
*[[HOWTO: Fix what portage breaks (minimize portage use by moving packges back to entropy).]]

==Hardware==
{{See also|[[:Category:Hardware]]}}
*[[HOWTO:_Resolve_Problems_with_HDA-Intel_Sound_Cards|HOWTO: Resolve Problems with HDA-INTEL Sound Cards]]
*[[HOWTO: Backup and Restore your partition table]]
*[[HOWTO: Slow KDM Login FIX]]
*[[HOWTO: UUID and Volumes]]
*[[HOWTO: Mount LVM]]
*[[HOWTO: Mount Encrypted Partition]]
*[[HOWTO: Make The Function Keys Work On An Apple Keyboard]]
*[[En:HOWTO: Install a Printer|HOWTO: Install a Printer]]

==Graphics==
{{see also|[[:Category:Graphics]]}}
*[[HOWTO: Common X Issues]]
*[[En:HOWTO: Changing Resolution|HOWTO: Changing Resolution]]
*[[HOWTO: Get 3D desktop working after install]]
*[[HOWTO: Get Ati or Nvidia Video Cards working in Sabayon]]
*[[HOWTO: Create a boot option for easy dual to single display switching]]
*[[HOWTO: Using Custom Framebuffer Resolution with GRUB2]]

==Networking==
{{see also|[[:Category:Networking]]}}
*[[HOWTO: Setting up PPTP VPN connection in konsole]]
*[[HOWTO: Replace NM with WICD]]
*[[HOWTO: NM7 Create a STATIC IP]]
*[[HOWTO: Get networking and network services working in Sabayon aka The Networking Guide]]
*[[HOWTO: Sharing e-mail between Sabayon Linux and Windows on a dual boot PC]]
*[[HOWTO: Passwordless SSH with Single Signon]]
*[http://webssh.cz.cc/ Using your browser as SSH client] (external site)
*[[HOWTO: Connecting to PPPoE (xDSL) service as non-root user]]
*[[HOWTO: Passwordless Samba Share]]
*[[HOWTO: Huawei e220 and e169]]
*[[HOWTO: Vista printer sharing]]
*[[HOWTO: Changing the hostname]]
*[[HOWTO: XBOX360 Internet Through Laptop]]
*[[HOWTO: Avoid network configurations being overwritten after reboot]]
*[[HOWTO: Samba foldersharing in Dolphin or Nautilus the smooth way]]
*[[HOWTO: full dns support]]

==Wireless==
{{see also|[[:Category:Wireless]]}}
*[[HOWTO: Connecting to GPRS/EDGE/4G t-mobile with IPwireless PCMCIA card]]

==Firewall==
{{see also|[[:Category:Firewalls]]}}
*[[En:HOWTO: Setting Guarddog Firewall init script]]
*[[En:HOWTO: Make a Firewall using Shorewall and Webmin]]

==Gaming==
{{see also|[[:Category:Gaming]]}}
*[[Savage: Battle For Newerth]] - how to update
*[[How to install Quake4]]
*[[Native Games]]
*[http://www.sabayonlinux.org/forum/viewtopic.php?f=43&t=1989 Enemy Territory] - Punk Buster and Sound
*[[FreeSpace 2]]
*[[Neverwinter Nights]]
*[[Quake]]
*[[Duke Nukem 3D]]

==Multimedia==
{{see also|[[:Category:Multimedia]]}}
*[[HOWTO: Setup Bluetooth Headphones]]
*[[HOWTO: Setup shoutcast server on SL box]]
*[[HOWTO: Amarok with MySQL database]]
*[[HOWTO: KMid]]
*[[How to get TV working in VLC with PVR]]
*[[HOWTO: Recording videos of your screen (screen video capture)]]
*[[HOWTO: Pithos on SL for Pandora users.]]
*[[HOWTO: Compile Cinelerra 4.3]]

==Desktops|Compiz-Fusion|==
{{See also|[[:Category:Desktops]]}}
*[[Enable/disable XGL or AIGLX after Install]]
*[[Black borders around windows fix (ATI)]]
*[[To start sabayon with aiglx enabled.]]
*[[Installing and configure Compiz Fusion]]

==Virtual Machines==
{{see also|[[:Category:Virtual Machines]]}}
*[[HOWTO: Using Virtualbox]]

==Performance Tweaks==
*[[How to optimize and accelerate your system]]
*[[HOWTO: Set Clock]]

==Power management==
*[[Auto hibernate after suspend]]

==Security==
*[[eCryptfs]]
*[[HOWTO: Encrypted Fake Partition]]

==Other==
*[[HOWTO: Using Molecule Example]]
*[[HOWTO: Restore Grub2]]
*[[HOWTO: chroot from a LiveCD]]
*[[HOWTO: Use xdelta]]
*[[HOWTO: Setup MySQL and JDBC for java to database programming]]
*[[En:HOWTO: Setting Up Autologin|HOWTO: Setting Up Autologin]]
*[[HOWTO: Skype for Linux]]
*[[HOWTO: Google Earth freezes at splash screen]]
*[[HOWTO: Compile and install aMSN with antialiasing]]
*[[HOWTO: Booting Sabayon LiveDVD Image from a USB Device with Grub]]
*[[HOWTO: booting Sabayon CoreCD image from a USB flash with Syslinux]]
*[[HOWTO: Fake Raid 0 Bios and Dual Boot Sabayon and XP]]
*[[HOWTO: Run FrostWire]]
*[[HOWTO:Make widgets (karamba) appear on all desktops extras ...]]
*[[HOWTO: Get RSS-glx(Really Slick Screensavers) to work on KDE4 and also add all xscreensavers]]
*[[HOWTO: Restore user default Sabayon settings]]
*[[HOWTO: Automount NTFS partitions as read/write]]
*[[HOWTO: Checkout SVN]] - checking out the source for the latest work.
*[[HOWTO: Installing CUPS Print to PDF driver]]
*[[HOWTO: Enable sudo]]
*[[HOWTO: Disk imaging using Partimage]]
*[[HOWTO: USB pen drive will not automount]]
*[[HOWTO: IRC Translation]]
*[[Getting Started]]
*[[HOWTO: Read Microsoft Outlook .MSG files in Linux]]
*[[HOWTO:Translate_Entropy]]
*[[HOWTO: Get 64bit Sun Java Working in Firefox]]
*[[HOWTO: Clock, Time, UTC, Dual boot with Windows]]
*[[HOWTO: Repair filesystem using fsck on a raid setup]]
*[[HOWTO: change the resolution of your framebuffer]]
*[[HOWTO: separate boot partition with PartedMagic and Clonezilla (dedicated GRUB2 partition)]]
*[[HOWTO: Install LAMPP / XAMPP web development environment]]
*[[HOWTO: Install Oracle 11g XE (Express Edition)]]
[[Category:HOWTOs| En]]

Talk:Using GDM with XGL and Compiz Fusion

2013-03-01T15:14:06Z

Aposteeltje: Aposteeltje moved page Talk:Using GDM with XGL and Compiz Fusion to Talk:Installing and configure Compiz Fusion: blowing new life into this document.. :-)

#REDIRECT [[Talk:Installing and configure Compiz Fusion]]

Using GDM with XGL and Compiz Fusion

2013-03-01T15:14:06Z

Aposteeltje: Aposteeltje moved page Using GDM with XGL and Compiz Fusion to Installing and configure Compiz Fusion: blowing new life into this document.. :-)

#REDIRECT [[Installing and configure Compiz Fusion]]

Talk:Installing and configure Compiz Fusion

2013-03-01T15:14:06Z

Aposteeltje: Aposteeltje moved page Talk:Using GDM with XGL and Compiz Fusion to Talk:Installing and configure Compiz Fusion: blowing new life into this document.. :-)

=== Marked for Deletion ===
XGL is no longer being developed and has been dropped.

Installing and configure Compiz Fusion

2013-03-01T15:14:05Z

Aposteeltje: Aposteeltje moved page Using GDM with XGL and Compiz Fusion to Installing and configure Compiz Fusion: blowing new life into this document.. :-)

{{Warning| <This page is outdated and will be renewed. Please don't use it's content !!!
This page will be rewritten into a full tutorial about how to install and configure compiz.
When Done, this warning will be removed. Thank you.>}}

== Setting up GDM ==

What we are going to do first is sync portage and the overlays to make sure that we have the latest GDM available to us.

{{Console| <pre class="clear">emerge --sync && layman -s sabayon</pre>}}

Then emerge gdm by doing

{{Console| <pre class="clear">emerge -va gdm</pre>}}

Then backup your gdm.conf and your custom.conf by doing this:

{{Console| <pre class= "clear">cp /usr/share/gdm/defaults.conf /usr/share/gdm/defaults.conf.bak
cp /etc/X11/gdm/custom.conf /etc/X11/gdm/custom.conf.bak</pre>}}

Then browse to /etc/conf.d/xdm and change:
{{File|/etc/conf.d/xdm | <pre class="clear">DISPLAYMANAGER="kdm"</pre>}} to
{{File|/etc/conf.d/xdm | <pre class="clear">DISPLAYMANAGER="gdm"</pre>}}

Also as a precaution check /etc/rc.conf and make sure that it says something like this:
{{File| /etc/rc.conf| <pre class="clear">DISPLAYMANAGER has moved to /etc/conf.d/xdm</pre>}}

== Configuring GDM ==

Now we move into the actual phase of configuring it to use XGL.

*Run {{Commandgui|gdmsetup}}
*Select the {{Commandgui|Security}} tab
*Click the {{Commandgui|Configure X Server}} button found at the bottom right of the tab

We will first delete all available entry's for the X server. Don't call me crazy. They'll be replaced.

*Click on the {{Commandgui|Standard Server}} that appears in the "Servers to Start" list.
*Click on the {{Commandgui|remove}} button. Goodbye X.

Now we replace that with a new X server.

*Click the {{Commandgui|Add/Modify}} button.
*Set the new server to use {{Commandgui|VT:1 for nVidia users or VT:0 for ATI users.}}
*Do not add any thing else. Click ok when done.
*Name the server {{Commandgui|Xgl.}}
*In the command line add this: <pre class "code">/usr/bin/Xgl -br -ac -accel glx:pbuffer -accel xv</pre> for nVidia users or <pre class "code">/usr/bin/Xgl :0 -ac -accel glx:pbuffer -accel xv:pbuffer</pre> for ATI users.

== Compiz Fusion ==

Follow said wiki: [[HOWTO:_Latest_Compiz-Fusion]]

== Resources ==

*The one and only resource: http://gentoo-wiki.com/HOWTO_XGL#Configuring_GDM_to_Use_the_Xgl_Server

--[[User:Element|Element]] 11:21, 29 July 2007 (PDT)

[[Category:Compiz-Fusion]]

En:Repositories

2013-03-01T14:10:38Z

Aposteeltje:

{{I18n| [[De:Repositories|de]] [[En:Repositories|en]]}}

In /etc/entropy/repositories.conf you find the general configuration that count for all repositories. The different repositories are inherited from a subdirectory: /etc/entropy/repositories.conf.d

In this subdirectory you should find some predefined examples for the different repositories.

However, in some cases, somehow those example files are missing, so you'll have to create them manually.

If this is the case, then follow the below instructions to create them, and eventually enable those you wish to use.

Open your favourite terminal and become root.

Navigate to the subdirectory:
{{Console| <pre class="clear"># cd /etc/entropy/repositories.conf.d</pre>}}

Now we create the files, beginning with a underscore(dash down)., so later on you can easily enable/disable them, using the commandline, or even with Rigo/Sulfur.

To create the '''daily''' Repository, (if missing):
{{Console| <pre class="clear"># nano -w _entropy_sabayonlinux.org</pre>}}

Make sure it has the following content:
{{Console| <pre class="clear"># Sabayon Linux Official Repository
repository = sabayonlinux.org|Sabayon Linux Official Repository|http://best.sabayon.org/entropy|http://pkg.sabayon.org#bz2
repository = sabayonlinux.org||http://gd.tuwien.ac.at/opsys/linux/sabayonlinux/entropy|
repository = sabayonlinux.org||http://ftp.kddilabs.jp/Linux/packages/sabayonlinux/entropy|
repository = sabayonlinux.org||http://mirror.internode.on.net/pub/sabayon/entropy|
repository = sabayonlinux.org||http://sabayon.c3sl.ufpr.br/entropy|
repository = sabayonlinux.org||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
repository = sabayonlinux.org||http://mirror.clarkson.edu/sabayon/entropy|
repository = sabayonlinux.org||http://cross-lfs.sabayonlinux.org/entropy|
repository = sabayonlinux.org||http://mirror.umd.edu/sabayonlinux/entropy|
repository = sabayonlinux.org||http://ftp.cc.uoc.gr/mirrors/linux/SabayonLinux/entropy|
repository = sabayonlinux.org||http://ftp.rnl.ist.utl.pt/pub/sabayon/entropy|
repository = sabayonlinux.org||http://mirror.yandex.ru/sabayon/entropy|
repository = sabayonlinux.org||http://dl.sabayon.org/entropy|
repository = sabayonlinux.org||http://redir.sabayon.org/entropy|
repository = sabayonlinux.org||http://debian.mirror.dkm.cz/sabayon/entropy|
repository = sabayonlinux.org||ftp://ftp.klid.dk/sabayonlinux/entropy|
repository = sabayonlinux.org||http://pkg.sabayon.org|
repository = sabayonlinux.org||http://mirror.de.sabayon.org/entropy|
repository = sabayonlinux.org||http://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository = sabayonlinux.org||ftp://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository = sabayonlinux.org||http://mirror.freelydifferent.com/sabayon/entropy|
repository = sabayonlinux.org||http://ftp.surfnet.nl/pub/os/Linux/distr/sabayonlinux/entropy|
</pre>}}

Save the file (ctrl-o) and exit the nano editor (ctrl-x).

To create the '''weekly''' Repository, (if missing):
{{Console| <pre class="clear"># nano -w _entropy_sabayon-weekly</pre>}}

Make sure it has the following content:
{{Console| <pre class="clear"># weekly
repository = sabayon-weekly|Sabayon Linux Official Repository|http://dl.sabayon.org/entropy|http://pkg.sabayon.org#bz2
repository = sabayon-weekly||http://redir.sabayon.org/entropy|
repository = sabayon-weekly||http://ftp.kddilabs.jp/Linux/packages/sabayonlinux/entropy|
repository = sabayon-weekly||http://gd.tuwien.ac.at/opsys/linux/sabayonlinux/entropy|
repository = sabayon-weekly||ftp://ftp.riken.jp/Linux/sabayon/entropy|
repository = sabayon-weekly||http://mirror.optusnet.com.au/sabayon/entropy|
repository = sabayon-weekly||http://mirror.internode.on.net/pub/sabayon/entropy|
repository = sabayon-weekly||http://sabayon.c3sl.ufpr.br/entropy|
repository = sabayon-weekly||http://mirror.clarkson.edu/sabayon/entropy|
repository = sabayon-weekly||http://cross-lfs.sabayonlinux.org/entropy|
repository = sabayon-weekly||http://mirror.umd.edu/sabayonlinux/entropy|
repository = sabayon-weekly||http://best.sabayon.org/entropy|
repository = sabayon-weekly||ftp://ftp.rnl.ist.utl.pt/pub/sabayon/entropy|
repository = sabayon-weekly||http://ftp.cc.uoc.gr/mirrors/linux/SabayonLinux/entropy|
repository = sabayon-weekly||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
repository = sabayon-weekly||http://debian.mirror.dkm.cz/sabayon/entropy|
repository = sabayon-weekly||ftp://ftp.klid.dk/sabayonlinux/entropy|
repository = sabayon-weekly||http://pkg.sabayon.org|
repository = sabayon-weekly||http://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository = sabayon-weekly||ftp://ftp.belnet.be/mirror/sabayonlinux/entropy|
repository = sabayon-weekly||ftp://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository = sabayon-weekly||http://mirror.freelydifferent.com/sabayon/entropy|
repository = sabayon-weekly||http://ftp.surfnet.nl/pub/os/Linux/distr/sabayonlinux/entropy|
</pre>}}

Save the file (ctrl-o) and exit the nano editor (ctrl-x).

To create the '''testing''' Repository (Limbo), (if missing):
{{Console| <pre class="clear"># nano -w _entropy_sabayon-limbo</pre>}}

Make sure it has the following content:
{{Console| <pre class="clear"># Limbo
repository = sabayon-limbo|Sabayon Limbo Testing Repository|http://gd.tuwien.ac.at/opsys/linux/sabayonlinux/entropy|http://pkg.sabayon.or$
repository = sabayon-limbo||ftp://ftp.riken.jp/Linux/sabayon/entropy|
repository = sabayon-limbo||http://mirror.optusnet.com.au/sabayon/entropy|
repository = sabayon-limbo||http://mirror.internode.on.net/pub/sabayon/entropy|
repository = sabayon-limbo||http://ftp.kddilabs.jp/Linux/packages/sabayonlinux/entropy|
repository = sabayon-limbo||http://sabayon.c3sl.ufpr.br/entropy|
repository = sabayon-limbo||http://cross-lfs.sabayonlinux.org/entropy|
repository = sabayon-limbo||http://mirror.clarkson.edu/sabayon/entropy|
repository = sabayon-limbo||http://mirror.umd.edu/sabayonlinux/entropy|
repository = sabayon-limbo||ftp://ftp.rnl.ist.utl.pt/pub/sabayon/entropy|
repository = sabayon-limbo||http://ftp.cc.uoc.gr/mirrors/linux/SabayonLinux/entropy|
repository = sabayon-limbo||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
repository = sabayon-limbo||http://debian.mirror.dkm.cz/sabayon/entropy|
repository = sabayon-limbo||http://best.sabayon.org/entropy|
repository = sabayon-limbo||http://pkg.sabayon.org|
repository = sabayon-limbo||ftp://ftp.klid.dk/sabayonlinux/entropy|
repository = sabayon-limbo||http://redir.sabayon.org/entropy|
repository = sabayon-limbo||http://dl.sabayon.org/entropy|
repository = sabayon-limbo||http://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository = sabayon-limbo||http://mirror.freelydifferent.com/sabayon/entropy|
repository = sabayon-limbo||http://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository = sabayon-limbo||http://ftp.surfnet.nl/pub/os/Linux/distr/sabayonlinux/entropy|
</pre>}}

Save the file (ctrl-o) and exit the nano editor (ctrl-x).

Now if you want to enable/disable the different repositories, the command is:
{{Console| <pre class="clear"># equo repo enable repository</pre>}}
{{Console| <pre class="clear"># equo repo disable repository</pre>}}

to enable '''daily''':
{{Console| <pre class="clear"># equo repo enable sabayonlinux.org</pre>}}

to enable '''weekly''':
{{Console| <pre class="clear"># equo repo enable sabayon-weekly</pre>}}

and to enable '''limbo''' testing repository:
{{Console| <pre class="clear"># equo repo enable sabayon-limbo</pre>}}

When using [[Rigo]], please see: [[Rigo#Manage_Repositories]]

En:FAQ

2013-03-01T12:59:53Z

Aposteeltje: /* How can I contribute to, or support Sabayon Linux */

{{I18n| [[Ca:FAQ|ca]] [[En:FAQ|en]] [[Es:FAQ|es]] [[It:FAQ|it]]}}

=FAQs=

=='''General Questions regarding Sabayon Linux'''==
===What is Sabayon Linux===
Sabayon Linux is a pre-configured distribution with the tenets of Performance, Versatility, and Stability, based on the source-based distribution named Gentoo Linux, a particularly customizable distribution. If you have other questions on Gentoo and its philosophy, I request you visit their website: http://gentoo.org. 
In particular, Sabayon emanates substantially from Gentoo's testing branch, one of the most popular source-based Linux distributions, which is about on par with Debian's unstable branch called Sid. Though based on the bleeding edge, you will find Sabayon is quite stable and perhaps more cutting edge than many. Although both Sabayon and Gentoo are rolling releases, Sabayon will have release snapshots. 

===How is Sabayon Linux maintained?===
As Ubuntu uses some of the packages from Debian, so Sabayon receives its packages from Gentoo. 
Sabayon, when using the package manager "Entropy" is binary based. Currently Sabayon has about 10,000 packages in Entropy. And when Sabayon is using the package manager "Portage", it is source based. The Gentoo repository is quite huge. 

===What is the difference between source-based and binary based distribution?===
Most distros, such as Ubuntu, Debian, Red Hat, Fedora and SUSE, install binary packages. Simply put, a binary package is the pre-compiled program, compiled on another computer and made available for download and installation on other computers. 
A source-based distro is one that compiles its programs from source code on the target computer at the time of installation, rather than relying on others to compile and package them. Source-based distros generally also have in their repositories some binary (pre-compiled) packages; these will be the large programs such as LibreOffice, the reason being that the compilation of these can take several hours. 
'''overlays'''
* Overlay: We have our own Portage overlay for ebuilds. Ebuilds are script files that contain instructions for the Portage package manager on how to install the package from its source code.
* Performance: We have modified the Portage make.conf file in order to ensure that our distribution will run at higher speed on newer computers and as fast as possible on older computers.
* Variability: Again, we have modified make.conf in order to cater to a wide spectrum of hardware, using the x86 and amd64 (x86_64) processor architectures.
* Entropy: We have a binary manager that can be used as the one, unique package manager. It functions also with Portage so that you can use them both if you are an experienced user. The Entropy binary packages are ready-built and can be installed immediately without the need to compile anything from the source code.
* The main branch of Gentoo is considered Gentoo stable. Sabayon is based on Gentoo's testing branch.
* Sabayon has different versions ready for quick and pain free installation. The Gentoo installation is done from the ground up, relying on you to make all the configuration choices.
* Gentoo has '''use''' flags. Sabayon will ignore '''use''' flags when using Entropy, but will apply the '''use''' flags when using portage. 

===Why choose Sabayon Linux ?===
1. Variety
Sabayon has multiple editions to choose from. From a variety of desktops to a variety of packages and installations that can enjoyed by new linux users as well as by power users who prefer a higher level of customization.
2. Sabayon is a rolling release.
Once installed you should not need to reinstall a new updated version, since you can use the update tools. Entropy is a GUI tool and front-end for the text console based Equo. This allows you to have the latest and greatest packages available to you, at all times.
3. The Anaconda installer.
The Anaconda installer in Sabayon greatly simplifies installation including disk partition setup and disk encryption, if desired or required.
4. Choice of package managers and repositories.
Sabayon's package manager Entropy is binary and currently contains about 10,000 packages in its repositories. Gentoo's package manager Portage is source based and has a quite huge repo.
5. Support.
Sabayon is highly active and well maintained. You can find help through our forums, live help, and the ever-growing wiki.
6. Look and feel.
Sabayon is generally considered one of the more visually attractive Linux distros. From the installer, to the desktops, and even down to the terminal which has a useful color scheme applied to make any work on the command line pleasing to the eye and easy to understand.
7. Using Sabayon helps to save the world
Test results have shown that using Sabayon Linux '''improves''' the economy; '''helps''' reduce global warming; is generally '''good''' for the environment; '''promotes''' world peace; and helps to fight off '''alien invasive''' species from other galaxies. It is also shown to be helpful in '''improving''' the health of your sense of '''humor''', which is important to keep from bashing your head on the key board during difficult moments. (Test results have been claimed to vary, but number 7 is considered an attempt at '''humor'''.) 

===Should I use Sabayon as a source-based or binary based distribution?===
Sabayon Linux has two package managers: [[Entropy]] (binary packages) and Portage (source packages). As you can install binary packages instead of source code-based packages, Sabayon Linux offers users a choice and the best of both worlds. The binary packages in the Entropy repository have been built by using the Portage package manager and then packaged using Entropy packaging tools on that computer. The binary packages are stored in the Entropy repository and you install them on your computer by using either the [[Equo]] command line client or the [[Rigo]] GUI client. As the release time and date of packages are a little different between the 2 package managers it is recommended to use one package manager consistently to avoid conflicts.

Generally, using Entropy with binary packages is recommended to new users and those who just want everything to work easily.

Portage(source based) is recommended for more advanced users who wish to customize their installation to a higher degree.

There are two main advantages to source-based distributions:
# Firstly, source-based distros often have the newest software before binary distros do. This is due mainly to the fact that rather than having to compile a package and then test it on different machines, all that is required in Sabayon Linux is a file telling it where to find the source code and how to compile it.
#Secondly, undoubtedly a program will eventually have a feature you don't need, and will just take up space or slow down the program. In a binary distro, you're stuck with this feature. In a source-based distro you have the option of removing unwanted features at the time of compilation (assuming you are using Portage rather than Entropy). 

===System Requirements===
* '''Live Environment - No 3D Desktop''':
** ''i686'' Processor
** at least ''512 MB'' of RAM (1 GB suggested)
** a ''2D'' graphics card
** a ''[http://en.wikipedia.org/wiki/Display_Data_Channel DDC] capable Monitor''
** ''mouse'' and ''keyboard''

* '''Live Environment - 3D Desktop''':
** ''i686'' Processor (starting from AMD K6 and Intel Pentium II)
** at least ''512 MB'' of RAM (1 GB suggested)
** an '''[http://en.wikipedia.org/wiki/OpenGL OpenGL] capable 3D graphics card''' (mostly NVIDIA, ATI, Intel, VIA)
** a ''[http://en.wikipedia.org/wiki/Display_Data_Channel DDC] capable Monitor''
** ''mouse'' and ''keyboard''

* '''Installation''':
{{Note| Please note that the Requirements indicated for Installation may be a bit too low for some Desktop Environments.
A full KDE Desktop for example, CAN run with only 1 GB RAM, but you will most likely run out of memory during a session, especially when running large programs, such as firefox, thunderbird and/or libreoffice. Please keep that in mind.}}
** ''i686'' Processor
** at least ''512 MB'' of RAM (1 GB suggested for decent eyecandy effects)
** an '''[http://en.wikipedia.org/wiki/OpenGL OpenGL] capable 3D graphics card''' (mostly NVIDIA, ATI, Intel, VIA)
** ''20'' GB of free space, that is bare minimum DVD Install. ''30+'' GB is highly recommended.
** ''8 GB'' of free space for miniCD. 10+ GB is recommended
** ''Internet connection'' (not mandatory but highly suggested)
** a ''[http://en.wikipedia.org/wiki/Display_Data_Channel DDC] capable Monitor''
** ''mouse'' and ''keyboard'' 

=== What Editions are available in Sabayon Linux? ===

Sabayon is all about choice. You have many flavors to choose from.

You can download them from the mirrors, here:
* [http://www.sabayon.org/mirrors Sabayon Mirrors Page]

The following choices are the main releases available in 32Bit (x86) or 64Bit (amd64):
{{Note| "amd64" is also suitable for '''Intel''' based 64bit Processors}}
1. KDE
2. Gnome
3. LXDE
4. MATE
5. XFCE
6. Enlightenment
All of the above mentioned Desktop Environments are fully-featured.

7. CoreCDX
CoreCDX is a minimal install for those wishing to configure the system more to their liking,
(for more advanced users) in 32bit or 64bit., and uses the Fluxbox Window Manager.

=== How can I contribute to, or support Sabayon Linux ===
There are several ways to contribute:

* The Sabayon foundation is always looking for funds.
For more information, see: http://www.sabayon.org/donate
* Translations.
We are always looking for translators. For the Wiki, as well as translating Sabayon into your native language. 

You may subscribe to our wonderful Wiki, and translate the articles into your own Language, or write your own articles about some area of working with Gnu/Linux. 

If you want to translate Sabayon into your own language, please see:
[[En:HOWTO: Translate Sabayon]] 

If you want to translate the Wiki articles into your own language, please see:
[[En:Translations]] and [[Editing_Guidelines]] 

* Subscribe to our Forum
Help out others with problems. Perhaps problems you've had once too, 
and know the answer or a solution.
http://forum.sabayon.org/ 

* Join us on Facebook or Google+
There are lots of Discussions going on on facebook and Google+. Want to help out, or participate? 
https://www.facebook.com/groups/36125411841/ 
https://plus.google.com/+sabayon/posts 

*setup more download mirrors
We need more mirrors! 

Check out this link to learn more about what it takes to mirror the Sabayon Linux project.
http://wiki.sabayon.org/index.php?title=Mirroring_Sabayon 

=='''The liveCD/DVD'''==
===Should I get the 32-bit or the 64-bit edition?===
This is a never-ending, debatable question. For new users, 32-bit is easier to operate as 64-bit may be a bit fussier. Everything should work in 64-bit as the 32-bit version. Keep in mind that you are still using mostly 32-bit applications. The average desktop user is not going to see benefits over the 32-bit. I suggest to people to try both and see for themselves. In my experience I see most new people picking the 32-bit version. You can certainly Google for more information on this debate.
64bit would seem to be the direction things are going in, though most applications are still in 32bit. 64bit has gotten more support these days and become more widespread in use. 64bit is currently more secure, however most 64bit systems use multi libraries. multi libraries allow you to use both 64 and 32bit apps. A 64bit system using multi libraries will have a certain amount of vulnerability as a 32 bit system.

===Can I install without having to burn the ISO to CD or DVD?===
Yes, you can [http://www.sabayonlinux.org/forum/viewtopic.php?f=50&t=12023 install if you don't have a CD or DVD burner.] Another way, if your computer can boot USB pen drives, is to use UNetbootin or similar to install the Sabayon Linux ISO to a pen drive and create a bootable pen drive (think of it as a fast LiveCD/DVD). Then you can boot the pen drive to get to a Live desktop, and install Sabayon Linux from there, just as you would from a LiveCD/DVD.

=== burning / checking the .iso image ===

One of the most common problems with burning a Linux install CD/DVD is that people sometimes don't understand that an iso image file is not a normal file. You cannot just burn the iso to disc to and expect it to work. I repeat: '''you cannot simply put the iso file on a blank disk and expect it to work'''. In order to properly make a CD or DVD out of an iso image, you need special software. Instructions for Nero and Isorecorder are included; for other programs, see the manual for the software, or just give one of these a shot.

With Nero you just select file and burn image, then select the .iso file you want to burn. The software handles the rest.

If you're looking for a good, alternative freeware solution, you can download a free image burner.

isorecorder [http://isorecorder.alexfeinman.com/isorecorder.htm] Simply download and install the correct version for your version of windows, then right click on the .iso and tell it to burn.

=== checking the integrity of the burned disc ===

Many people know they can check if a downloaded ISO file is OK by comparing the md5sum of the ISO file against the md5sum posted on the SL mirrors. For example:

{{Console| <pre class="clear">
# md5sum -c SabayonLinux-x86_64-3.4f.iso.md5
SabayonLinux-x86_64-3.4f.iso: OK
</pre>}}

cf. the contents of ftp://bo.mirror.garr.it/mirrors/sabayonlinux/SabayonLinux-x86_64-3.4f.iso.md5 which are:
645600788920443b372baae3544acffa SabayonLinux-x86_64-3.4f.iso

so the ISO I downloaded was good.

Remember - verify the MD5 sum for the version of Sabayon that you downloaded - they are all different. The MD5s can be found on the mirrors listed at: http://www.sabayonlinux.org/mirrors

But a different method is needed to verify the '''integrity''' of the LiveDVD/CD itself. You should select the verify written data checkbox in K3b before burning the DVD/CD, but if you forgot or still have doubts then the following method can be used to check the integrity of the burnt LiveDVD/CD:

If you only have Windows installed on your HDD, apparently you can use a Windows shareware application, see the following Web page for details:
http://www.mepis.org/docs/en/index.php?title=Checking_the_integrity_of_a_Live_CD

A WARNING:

1. I have not checked if the method for Windows on the above-mentioned Web page actually works, so use it at your own risk.

Under Linux:

Insert the LiveDVD into the optical drive, let the disc spin up and then enter the following three commands:

{{Console| <pre class="clear">
md5sum /dev/cdrom | awk '{print $1}' > md5a.txt
md5sum ~/Sabayon_Linux_8_amd64_K.iso | awk '{print $1}' > md5b.txt
diff -qs md5a.txt md5b.txt
</pre>}}

(Obviously change the path and/or the ISO file name to match your circumstances.)

If you get an error message while the md5sum is reading the disc, there must be something wrong either with the burn or with the optical drive itself.

If you get the message "Files md5a.txt and md5b.txt differ" then the burn was bad.

If you get the message "Files md5a.txt and md5b.txt are identical" then the burn was good.

=== Passwords on live CD/DVD ===

* The root password:
no password is required: just press the Enter key.

* The sabayonuser password:
no password is required: just press the Enter key.

*For older releases (version 6 and earlier) the password for Root is "root" (without the quotes) and the password for Sabayonuser is "sabayonuser" (without the quotes).

=== The Booting process ===

The boot process of the liveCD/DVD should be pretty straight forwarded, just as many other Linux Distrtibutions.

However, you could get into problems, when having hardware that isn't supported by default, for example.

Or having old hardware that the current drivers don't support.

When having a old NVidia card, and you've downloaded the latest ISO, chances are that it will not start the Window Manager/Desktop Environment, but rather present you with a black screen.

There is nothing wrong with the ISO, it is because "nvidia-drivers-304.64" or higher is installed by default.

You can bypass that by hitting ctrl-alt-f1, remove the nvidia-drivers, (nouveau is installed too), and restart xdm., as explained below:

'''Removing latest nvidia-drivers:'''
# Press the "CTRL-ALT-F1" key combination.
"#" is just indicated that you have to be root, so do not include that with the actual commands...
{{Console| <pre class="clear"># su</pre>}}
{{Console| <pre class="clear"># equo remove nvidia-drivers --ask</pre>}}
Check that "x11-drivers/nvidia-drivers" got removed., nothing else... and confirm with "yes"

Restart XDM:
{{Console| <pre class="clear"># /etc/init.d/xdm restart</pre>}}

For a overall view of which cards support what driver., please see: http://www.nvidia.com/object/IO_32667.html

If you wish to be guided through the boot process and the several options it offers, we have a visual walkthrough.

Please see: [[Visual_Tour:_Boot-menu_Sabayon_LiveCD/DVD]]

Workarounds for problematic Hardware, during the boot process are discussed here:

[[Sabayon_Linux#Boot_parameters_and_workarounds_for_problematic_Hardware]]

'''cheatcodes for ATI and nVidia'''

ATI
noddc res=1024x768 refresh=60 opengl=ati
nVidia
noddc res=1024x768 refresh=60 opengl=nvidia

To use the cheatcodes, hit F5 on the boot up screen of the livecd/dvd and add one of the lines above pending on your hardware

see: [[Visual_Tour:_Boot-menu_Sabayon_LiveCD/DVD]]

When you need to edit xorg.conf, or have to create it for special reasons, the following visual tour will show you how to edit Xorg.conf:

[[Visual_Tour:_Part_2_Editing_the_xorg.conf]]

=='''After installation'''==

===What is Entropy or Equo?===
[[Entropy]] is the binary package manager of Sabayon Linux. To install binary packages you use either the command line client [[Equo]] or the newest Graphical GUI [[Rigo]].

A binary package is a file package containing the already-compiled files to install instead of having to compile the source code. Equo, and [[rigo]] handle these files.

===I just installed it, what do I do first?===
This question has always amazed me. Who says there is anything to do? How about just using the operating system and getting familiar with it? Take some time and read the documentation. If you insist on having to do something then emerge --sync && layman -S to update your Portage package list, or, if using Entropy, see [http://wiki.sabayonlinux.org/index.php?title=Entropy#Fresh_Install_-_What_to_do.3F Fresh Install]

===The GUI for managing packages===

[[rigo]] is the GUI for the Entropy package manager.

{{Warning|'''emerge and layman are Portage commands, Portage is not our own package manager but is available to advanced users. Any steps using these commands can be safely ignored'''}}

There are GUIs for the Portage package manager, but they are no substitute for using emerge on the command line.
* [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10158 Portato] is a GUI for Portage that we recommend as it is the most actively developed. [http://portato.origo.ethz.ch/ Home Page]
Personally if you have to rely on a GUI, then try to just use it as a browser of Portage, but still use the command line to install your packages. You will save yourself a lot of headaches. Search and gather your information needed with the GUI then open up Konsole or Terminal and install using the emerge command.

===How do I update/install packages?===
There are 2 package managers, Entropy and Portage. It is highly recommended that you choose and only use 1 package manager. Conflicts can arise from mixing both package managers.
Please read the [[Entropy]] page. Entropy is the package manager specially developed for Sabayon Linux. It has a command line interface ([[Equo]]) and a GUI interface ([[Sulfur]]). Equo commands and Sulfur GUI are Entropy and recommended for newer users of Sabayon Linux. Advanced users of Sabayon Linux may wish to use Portage, the package manager developed for Gentoo Linux, on which Sabayon Linux is based. For information on Portage, please read [[HOWTO: The Complete Portage Guide]].

===How do I install several packages?===
For Entropy:
{{Console| <pre class="clear"># equo install foo foo foo foo foo</pre>}}

For Portage:
{{Console| <pre class="clear"># emerge foo foo foo foo foo</pre>}}

The package manager will install each package one after another. Replace foo with actual package name.

===How do I search for a package?===
* For Entropy:
{{Console| <pre class="clear"># equo search foo</pre>}}
or use the [[rigo]] GUI, or use the [http://www.sabayon.org/packages Sabayon Linux Web site's Entropy package search page].
* For Portage:
{{Console| <pre class="clear"># emerge -s foo</pre>}}
or use a GUI such as Portato.
* Via [http://gentoo-portage.com/Browse Gentoo-Portage] or via [http://packages.gentoo.org/ Packages-Gentoo].

'''Using EIX'''
* For Portage:
I highly recommend using eix. It's the best tool you can have at your hands for searching. It is a command line tool, but it is very powerful and will tell you lots of information.
{{Console| <pre class="clear"># emerge eix && eix-update
# eix foo</pre>}}

You can use eix in Entropy too:
{{Console| <pre class="clear"># equo install eix && eix-update
# eix foo</pre>}}

Example output of eix gedit:
{{Console| <pre class="clear"> [I] app-editors/gedit
Available versions: 2.18.2-r1 2.20.3 (~)2.20.4 {acl debug doc python spell xattr}
Installed versions: 2.20.4(07:05:31 AM 12/29/2007)(python -debug -doc -spell -xattr)
Homepage: http://www.gnome.org/
Description: A text editor for the GNOME desktop</pre>}}
Eix has the ability to search Portage and all overlays. Simply edit the /etc/eix-sync.conf file and just add * to it
{{Console| <pre class="clear"># echo '*' >> /etc/eix-sync.conf</pre>}}
Then do:
{{Console| <pre class="clear"># eix-remote update</pre>}}
Now when you search, it will tell where and what overlay a package is in if it is not in the Portage main tree. This will widen your abilities to find packages, as overlays contain a lot of ebuilds too.

http://en.gentoo-wiki.com/wiki/Eix

===Can I emerge 2 packages at same time in Portage?===
Yes you can, but it can and will bog your system down. It's not really recommended.
===How do I update everything at once?===
For Entropy:
{{Console| <pre class="clear"># equo update
# equo upgrade
# equo conf update</pre>}}

See the Sabayon Wiki article [[Entropy]] for details.

{{Warning|'''emerge and layman are Portage commands. Portage is not our package manager but is available to advanced users. Any steps using these commands can be safely ignored'''}}

If you are new to this distro and have no understanding of Portage, we do not recommend this until you get to know how this distro works. This is one of the fastest ways to destroy your system. This distro is not like the other distros that have the big easy button update. For your information though, 'world update' is what Gentoo calls updating your entire system. It looks at your 'world file' and compares it to Portage and then proceeds to update all packages. Following is how:

{{Console| <pre class="clear"># emerge -- sync && layman -S
# emerge -ua world</pre>}}

* [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap3 Maintaining Software]
* [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=5531 Unofficial Guide to World Update]
You've been warned. When you come yelling because your system won't boot, don't expect sympathy.

N.B. The term 'world' is not used in Entropy.

===How do I uninstall a package?===
* For Entropy:
{{Console| <pre class="clear"># equo remove foo</pre>}}
Note - this can remove dependencies.

*For Portage:
{{Console| <pre class="clear"> # emerge -C foo</pre>}}
Note - this will not remove the dependencies. You will need to run [http://en.gentoo-wiki.com/wiki/Gentoo_maintenance#depclean depclean] for that. I stress great caution with depclean, as it means what it says.

===How do I find out which packages depend on a certain package?===
{{Console| <pre class="clear"># equery depends foo</pre>}}
It will tell you all files depending on that package. See [http://www.gentoo.org/doc/en/gentoolkit.xml using gentoolkit] for more information and commands.

===I keep getting !!! ARCH is not set... Are you missing the 'etc/make.profile' symlink?===
In Konsole/Terminal use the '''su''' command to become the root user and then:
* Run the following command: '''eselect profile list'''
* Look for something like: '''default-linux/x86/2007.0/desktop''' and note the number in front of it.
* Then do: '''eselect profile set #''' <--replace the # with the number. In my case it would be '''eselect profile set 6'''
Now you should be good to go again.

===Do I have to download the LiveCD/DVD every time to upgrade?===
No, Sabayon is a rolling release. However in some cases upgrading via live DVD may prove more time efficent.

Entropy:
The equo command makes upgrading easy - see [[Entropy]].

Portage:
Portage is recommended for advanced users that prefer a higher degree of customization. That being said, Gentoo documentation is quite extensive and helpful for those wanting to dive into it.

Always backup your files before doing anything. My personal opinion: backup, fresh install, restore backup.

===How do I check for security updates ?===
It's pretty easy to keep your [http://www.gentoo.org/doc/en/security/security-handbook.xml?part=1&chap=14 system secure.]
Entropy does this for you automatically.

For Portage:
* Open up konsole or terminal and enter the command '''su''' to become the root user.
* Run the command '''glsa-check -t all''' to check your system.
* Then to fix, run '''glsa-check -f $(glsa-check -t all)'''

You can also visit our security wiki for more helpful tips:
* [http://wiki.sabayon.org/index.php?title=En:Security Sabayon Security wiki]

===How do I handle blocked packages?===
This is an issue in Portage. You are going to run into [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap4 packages blocking other packages.] This can happen for several reasons, e.g. a package has been dropped from Portage as it no longer exists or is no longer supported. In most cases you will simply have to remove (uninstall) the package that is blocking the new package. You will want to do some research on this first. Don't take Portage for granted and blindly do as it says without checking out what or why.

Note - latest versions of Portage (version 2.2 and higher) handle most blockages.

===How to handle masked packages?===
A package is complaining that it is [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap5 masked] and cannot install. This is one of those times you want to check why it is masked. A masked package is usually masked to prevent you from busting things. There are several ways a package can be masked. You can still install masked packages by unmasking them, but make sure you find out first why they are masked.

===How do I update the config files?===
As you install stuff, some packages are going to bring in new versions of their config files. These config files are important as they may have new settings for that package that need to be implemented. I stress that is is very, very crucial that you pay attention to these config files. You can change the entire outcome of your installation if you are not careful. Get to know your [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10863 config files.] There are several ways to handle these files:

For Entropy:
{{Console| <pre class="clear"># equo conf update</pre>}}

For Portage:
[http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=4#doc_chap1 dispatch-conf] and [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=4#doc_chap2 etc-update] are probably the most popular ways of handling updates to config files. A GUI tool is [http://etc-proposals.berlios.de/ etc-proposals.]

Please handle these files with care. You can't know these files enough.

===Where do I start to configure my system?===
For Entropy:
All packages are pre-configured remotely as they have been compiled on a remote computer. You do not need to (and cannot) do anything. If a package has been compiled without a specific USE flag that you need, then you will either have to request to the Entropy repository maintainers that the package be rebuilt (file a bug report in [http://bugs.sabayonlinux.org/ bugzilla]) and the new version placed in the Entropy repository, or use Portage to rebuild it yourself.

For Portage:
The file [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578 make.conf] is your heart and soul of your operating system. Learn it, edit it and build a lean, mean machine. Sabayon Linux ships with a generic make.conf that tries to support everything under the sun. You don't need all that stuff and by configuring, you will have lesser issues with Portage and conflicts.

===Where does Portage download the packages to?===
They are downloaded and stored in the directory '''/usr/portage/distfiles/'''

===Where does Entropy download the packages to?===
They are downloaded and stored in the directory '''/var/tmp/entropy/packages/'''
For instance, on my amd64 using Branch 4 they are stored in '''/var/tmp/entropy/packages/amd64/5'''

===How do I clean out Entropy downloaded packages?===

{{Console| <pre class="clear"># equo cleanup</pre>}}
See [http://wiki.sabayonlinux.org/index.php?title=En:List_Of_Equo_Functions Sabayon Wiki page of Equo commands] or equo --help --verbose

=='''Additional'''==
=== How do I get the Desktop Cube thing working?===
The desktop cube and 3D graphics do not work after I installed Sabayon Linux to the hard disk, but do work when I'm using the LiveCD/DVD.

Well, in theory what you see when you run the LiveCD/DVD is what you get when you install Sabayon Linux. So if the 3D desktop was working with the LiveCD/DVD then it should work when you boot your new installation. Well, we know all about theories; it doesn't work for everyone. You can either search in the Sabayon Linux Forums and the Sabayon Wiki for help on how to get the 3D desktop working with your particular model of graphics card, or you can ask in IRC #sabayon.

First thing you need to do: make sure the md5sum is good after you downloaded the .iso file, I can't stress that enough. Make sure you have burnt the CD/DVD as slowly as possible, and enable Burn Verify in your burning application.

You will be asked those two questions every time, so please do this so we don't have to waste bandwidth re-asking. It may seem petty to you to check the md5sum but, without knowing you're starting out with a good ISO file, it's pointless to continue. We can spend weeks troubleshooting and if your md5sum was bad, we just waste a lot of time and it causes a lot of frustration. With a bad md5sum you can still get a bootable working desktop, but may have issues elsewhere. So keep in mind, just because it boots, doesn't mean the ISO file is good. How do I check the md5sum and disk you ask? Well, luckily for you: [[HOWTO: Checking the integrity of a LiveCD or LiveDVD]].

OK, so you made sure the md5sum was good and you burnt the disk at a nice slow speed with Burn Verify enabled. Now we can start looking at other things. Do you have the correct video driver and the latest version of it? That will be the first thing to know.

NVIDIA card owners, the following link will save you hours of frustration. Yes, certain cards require certain drivers: http://en.gentoo-wiki.com/wiki/Nvidia. If you do not know or understand what is 'masking' then please read more (Portage users, see http://dev.gentoo.org/~dang/masked.txt. Entropy users, see [[Entropy#Masking_and_Unmasking_Packages_in_Entropy]].

Our Wiki also has a HowTo get NVIDIA and ATI cards working too, so use the relevant information: [[HOWTO: Get Ati or Nvidia Video Cards working in Sabayon]]. Also search the Sabayon Linux Forums for posts mentioning your card manufacturer and model.

The above method will work for most people, but you will find that maybe it didn't work for you. Why? I don't know. A little bit of research into /etc/X11/xorg.conf can usually resolve the remaining few that have problems. The following link is full of information for AIGLX: http://en.gentoo-wiki.com/wiki/AIGLX/Troubleshooting. Again, only use the information that is relevant. You will want to pay attention to the xorg.conf settings shown on that page and compare it to your xorg.conf so it matches.

Still having problems? Buy a new video card!

If you want to post your special way of how you got it working - please do. Mine just works all the time so I don't have such problems.

===Multimedia===
Does this include support for some privately-owned platforms? Yes, Sabayon Linux supports DVDs, MP3, WMA, AAC, DivX. Moreover, it supports a lot of open platforms, such as Ogg Vorbis, Matroska, Ogg Theora, FLAC, and coder-decoder Xvid.

===Games===
[http://www.sabayonlinux.org/forum/viewforum.php?f=43 Please Visit our Gaming Shed]

===AIGLX===
Q: Is AIGLX available?

A: If your graphics card is capable, then this should work out-of-the-box. If you are having trouble, start with the Gentoo Wiki article http://en.gentoo-wiki.com/wiki/AIGLX/Troubleshooting.

Q: In [[HOWTO: Get Ati or Nvidia Video Cards working in Sabayon]] it states that ATI GPUs can use AIGLX with the closed-source driver FGLRX. Is it feasible? Previously this worked only with XGL and open source DRI (direct giving infrastructure) Radeon driver.

A: AIGLX is supported by both the open-source Radeon driver and the closed-source FGLRX driver. N.B. Not all ATI cards are supported by the closed-source FGLRX driver and must use the Radeon driver. To find out if the closed-source driver supports your ATI card, see the release notes for the relevant version of the FGLRX driver (a.k.a. AMD Catalyst driver for Linux).

===3D Desktop/Compiz Questions===
'''The cube was working on LiveCD/DVD but doesn't on install, now what?'''

Well, now it's getting difficult as we need to [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=11723 check more things.] You will need the assistance of the Sabayon Linux Forum or IRC to help. I recommend you try and find the source of your problem first. When logged in, open a Konsole/Terminal window and type in the command fusion-icon and see what the error message is in the Konsole/Terminal. You will need to post that error message with your request for help. Make sure you have installed the latest video drivers for your video card also.

'''How do I update Compiz-Fusion to latest Dev. Version?'''

We have a [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=9882 guide on the forum] that is maintained to keep up with the changes in Compiz-Fusion development. This is for Portage users.

'''How do I know if my card will work with Compiz-Fusion?'''

We have a [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=8773 card list] that the community has reported on if their card works or not. It's not a complete list, but a good list to reference.

'''Where can I get more help on Compiz-Fusion?'''

I would suggest their [http://forum.compiz-fusion.org/ support forum.]

===How do I install KDE 4.x.x with Equo?===

{{Console| <pre class="clear"># equo install kde-meta-4.x.x</pre>}}

Replace the x's with the version of KDE you want to install.

===How Do I enable Autologin?===
The real question is, do you really want to? If yes, you should get a hammer and hit yourself in the head repeatedly. Logging in, especially logging in as user, not root, is a very basic but powerful security measure. Hostile programs cannot be autorun on your system if you log in as user. Also no one can accidently/purposefully find your collection of porn, google searches, or downloaded emails simply by pushing the power button if you set a user with password.
[http://wiki.sabayonlinux.org/index.php?title=En:HOWTO:_Setting_Up_Autologin Please see our Wiki page for how to do this.]

===How Do I change the positioning of notifications?===
By default the sabayon gnome version comes with [https://launchpad.net/notify-osd notify-osd]. This is developed by Canonical and
Mark Shuttleworth says the positioning won't be configurable [http://www.markshuttleworth.com/archives/265#comment-316838].
So if you want the notifications to appear in another corner you'll have to uninstall notify-osd and install [http://www.galago-project.org/news/index.php notification-daemon].
After that you will be able to configure the positioning with {{Console| $ notification-properties}}

===Networking Questions===
'''How do I find out what network card I have?'''

As root user, enter the command '''lspci''' in a Konsole or Terminal window. That will list hardware; look for your Ethernet controller.

'''How do I set-up my network?'''

Well, hopefully the LiveCD/DVD recognizes your network card, and NetworkManager sets your network up for you. If it doesn't, try running the command as root: simply '''su''' and run '''net-setup'''. You're going to want to consult the [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4 Gentoo Networking section.]

'''I can ping my router but can't access the Internet'''

You're probably having DNS issues. You need to edit the file /etc/resolv.conf and enter the correct DNS, then restart your network. If you don't know what to use for DNS, use 4.2.2.2

===Sound Questions===
'''I have no sound, what do I do?'''

* Let's see if you computer detects your sound card so, from a command line, use '''su''' to become root user, and run '''alsaconf''' - hopefully your card shows up and all you have to do is select and go.
* After running that, you can use '''alsamixer''' to adjust your sound settings. Press F6 to select your card in ALSAMixer and make sure no channels are muted and that the channel volumes are turned up.
* [http://wiki.sabayon.org/index.php?title=HOWTO:_Resolve_Problems_with_HDA-Intel_Sound_Cards If you have HDA-Intel Card, Please see this HowTo]

'''How can I determine what sound card I have?'''

As root user run the command '''lspci | grep -i audio'''

'''How do I install the alsa-driver instead of having it in the kernel?'''

Sabayon Linux comes with ALSA built into the kernel. You can't install the alsa-drivers while ALSA is built into the kernel. You have to remove ALSA from the kernel before you install the alsa-driver package. So use the '''su''' command to become the root user, and then enter the following commands:

{{Console| <pre class="clear">
# cd /usr/src/linux
# make menuconfig
# make && make modules_install
# cp arch/i386/boot/bzImage /boot/kernel_name <--replace kernel_name with the actual name of kernel
</pre>}}

* Reboot

{{Console| <pre class="clear">
# emerge alsa-driver
</pre>}}
* More info: [http://www.gentoo.org/doc/en/alsa-guide.xml Gentoo ALSA Guide.]

'''Why do I have to run alsaconf every time I reboot?'''

This usually happens if you have more than one sound card in your machine. Many people have an on-board sound card and then stick in a better sound card. Disable your on-board sound card via your BIOS and when you run alsaconf again, ALSA will restore your sound each time you reboot.

===Video Questions===
'''My NVIDIA card is a legacy card, what driver do I need?'''

You will need to compare your card with the information below to find out which driver is best for your card:
* [http://en.gentoo-wiki.com/wiki/Nvidia Check out the Nvidia Howto]
* [http://www.gentoo.org/doc/en/nvidia-guide.xml Also the Nvidia Guide]

'''I need help with my AMD/ATI card!'''

I don't have ATI so I can't supply much help here, but I can point you to:
* [http://en.gentoo-wiki.com/wiki/Graphics_drivers#AMD.2FATI Howto Ati Drivers]
* [http://www.gentoo.org/doc/en/ati-faq.xml Gentoo FAQ on ATI]

===How do I setup AIGLX with my ATI?===
* [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=12438 HOWTO AIGLX with ATI and Sabayon 3.5]

'''How do I setup Dual Monitors?'''

Personally I use twin view and it works great with Compiz-Fusion also. Check out the [http://en.gentoo-wiki.com/wiki/Dual_Monitors Gentoo Wiki article X.Org/Dual Monitors]

'''Video Worked on LiveCD/DVD, but not once install. Options?'''

If your video was fine on the LiveCD/DVD I would boot the LiveCD/DVD and copy the xorg.conf from it to your hard drive install. There are several ways to do this.

* Option 1 - Boot up and browse to /etc/X11/ and copy the file xorg.conf to your installed version. You should be able to access your installed version through the /media directory so it may be something like /media/mydrive/etc/X11/ Reboot the computer and you should have what you had on the LiveCD/DVD. Always backup your files before overwriting.
* Option 2 - Boot up and browse to /etc/X11/xorg.conf and use something like http://www.pastebin.ca to paste your xorg.conf file there. Note the URL so that when you reboot to your installed version you can access it. Then just rename your existing xorg.conf and make a new one with the one you pasted.
* If you still don't have any luck, we may need to look at your drivers. Try reinstalling your video drivers, but, before reinstalling, make sure you are getting the latest drivers. NVIDIA users, make sure you are using the proper drivers for your card. See Question 1 under Video Questions.

===How do I know what Version of Sabayon I installed?===

{{Console| <pre class="clear">
# cat /etc/sabayon-release
</pre>}}
N.B. Sabayon Linux is a 'rolling release' distro. Therefore, if you have upgraded your installation via Entropy or Portage then your installation will no longer be the version recorded in /etc/sabayon-release, as that file tells you the version of the LiveCD/DVD that you used to install Sabayon Linux.

=='''Help and Support Questions'''==

'''How Do I get Log files to get better support?'''

With the package app-misc/sabayonlive-tools, you can easily gather important information to help you debug and provide vital information for the support team to help you. [http://forum.sabayonlinux.org/viewtopic.php?f=60&t=15530 Please see this thread to learn how].

'''Where Do I file a Bug Report?'''

Please use our [http://bugs.sabayonlinux.org/ bugzilla]

'''Where can I get help?'''

Are you lost and confused? There are a lot of great resources out there. I highly encourage you to do some searching first before running into IRC or the Forum and making the same post that has already been posted 100 times. It gets really old answering the same question day in and day out when it's so well documented.
* [http://www.sabayonlinux.org/forum/index.php Sabayon Linux Forum]
* [http://www.sabayonlinux.org/wiki/ Sabayon Linux Wiki]
* [http://www.gentoo.org/doc/en/handbook/index.xml Gentoo Handbook]
* [http://gentoo-wiki.com/Official_Gentoo_Documentation Official Gentoo Documentation]
* [http://gentoo-wiki.com/Main_Page Gentoo Wiki]
* [http://gentoo-portage.com/Browse Gentoo Portage]
* [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1 A Portage Introduction]
* irc.freenode.net in channel #Sabayon also on desktop Get Live Help -- note to IRC users, be human and have patience. Do not paste errors in the room either. To paste messages in IRC, use [http://pastebin.ca/ pastebin.ca], [http://www.sabayon.org/pastebin] or your favorite pasting site. Then simply give the URL for your pasted text so others can view your error. The people in IRC are not paid to be there, they do it out of dedication, so treat them nicely. Trolling, stupidity, and rudeness will get you banned. Also note that the IRC room is not there to teach you Linux or hold your hand. Don't be lazy, do your part too.
* Quick note when pasting error messages - Do not paste the error message alone: everyone thinks that ERROR: x11-base/xgl-0.0.1_pre20070915 failed is the error, it's not. The error is above that. Post the entire build log so we don't have to waste time waiting for you to post back with the actual error. If you read below the ERROR: it even says to paste the uppermost error and call stack if relevant.

En:Main Page

2013-03-01T12:49:20Z

Aposteeltje:

{{I18n| [[Ca:Main_Page|ca]] [[Cs:Main_Page|cs]] [[De:Hauptseite|de]] [[En:Main_Page|en]] [[Es:Main_Page|es]] [[Fr:Main_Page|fr]] [[Gr:Main_Page|gr]] [[Id:Main_Page|id]] [[It:Main_Page|it]] [[Pl:Strona_Glowna|pl]] [[Ru:Main_Page|ru]] [[Sv:Main_Page|sv]] [[TR:Ana_Sayfa|tr]] [[Zh_TW:Main_Page|zh_tw]]}}

='''Welcome to Sabayon Linux Wiki!'''=
{{Featured|[[Entropy| En:Entropy]]|Entropy is our answer to Portage. This is a binary-based client that is designed to allow more freedom to new users, and more choices in packages in the community repos.}}

Sabayon Linux is based on the source-based distro named [http://www.gentoo.org/ Gentoo]. Gentoo is a highly customizable distro and, using Gentoo's excellent development techniques, we have created a pre-configured distribution with the tenets of Performance, Versatility, and Stability. Please see the [[Introduction]] and [[Sabayon Linux]] sections in this Wiki, and we stress highly that you need to learn how to use the package managers [[Entropy]] and Portage ([[HOWTO: The Complete Portage Guide]]). We do stress the use of Entropy rather than Portage, but you will need to understand Portage also.

===Editors===
Wiki editors, make sure you look at the [[Editing Guidelines]] before editing or creating a new article, and add new articles to their appropriate sections below.

<div style="width: 70%;">{{Note| '''Translations'''

We are always looking for translators. We want to be able to bring Sabayon Linux to the entire World, but we need '''your''' help to do that. Please look at the Wiki article on [[En:Translations|translations]] and feel free to edit/add any page you like.
}}</div>

== Sections of Sabayon Linux Wiki ==
{|style="width: 100%"
|[[Image:Pens.png|16px]] [[Editing Guidelines]]
|[[Image:Helmet.png|16px]] [[Wiki Admins]]
|[[Image:Document.png|16px]] [[Wiki News]]
|}

{|style="width: 100%;"
|[[Image:Help-browser.png|left]] '''[[FAQ]]''' Frequently Asked Questions

|[[Image:Abc.png|left]] '''[[En:Introduction|Introduction]]''' Introduction / New Users Start Here
|-
|[[Image:SabayonLogoSmall.png|left|32px]] '''[[En:Sabayon Linux|Sabayon Linux]]''' Information About Sabayon Linux

|[[Image:Beginners-guide.jpg|left|32px]] '''[[En:Beginners Guide|Beginners Guide]]''' from booting to installing
|-
|[[Image:EntropyLogoSmall.png|left|32px]] '''[[En:Entropy|Entropy Package Manager]]''' The Entropy Package Management System

|[[Image:Howto.png|left]] '''[[HOWTOs]]''' HOWTO's for Entropy Systems Only
|-
|[[Image:Information.png|left]] '''[[Tips]]''' Tips & Tricks for your average Joe

|[[Image:Hardware flash.png|left]] '''[[Hardware]]''' Hardware related help
|-
|[[Image:Padlock1.png|left]] '''[[En:Security|Security]]''' Security articles and help

|[[Image:Info.png|left]] '''[[Known Issues]]''' Current Known Issues
|-
|[[Image:Portage.png|left|32px]] '''[[HOWTOs for Portage]]''' HOWTO's related to Portage

|[[Image:Archive.png|left|32px]] '''[[Sabayon-Wiki Archive]]''' Old, outdated articles.
|-
|}

__NOTOC__
__NOEDITSECTION__

En:Main Page

2013-03-01T12:48:56Z

Aposteeltje:

{{I18n| [[Ca:Main_Page|ca]] [[Cs:Main_Page|cs]] [[De:Hauptseite|de]] [[En:Main_Page|en]] [[Es:Main_Page|es]] [[Fr:Main_Page|fr]] [[Gr:Main_Page|gr]] [[Id:Main_Page|id]] [[It:Main_Page|it]] [[Pl:Strona_Glowna|pl]] [[Ru:Main_Page|ru]] [[Sv:Main_Page|sv]] [[TR:Ana_Sayfa|tr]] [[Zh_TW:Main_Page|zh_tw]]}}

='''Welcome to Sabayon Linux Wiki!'''=
{{Featured|[[Entropy| En:Entropy]]|Entropy is our answer to Portage. This is a binary-based client that is designed to allow more freedom to new users, and more choices in packages in the community repos.}}

Sabayon Linux is based on the source-based distro named [http://www.gentoo.org/ Gentoo]. Gentoo is a highly customizable distro and, using Gentoo's excellent development techniques, we have created a pre-configured distribution with the tenets of Performance, Versatility, and Stability. Please see the [[Introduction]] and [[Sabayon Linux]] sections in this Wiki, and we stress highly that you need to learn how to use the package managers [[Entropy]] and Portage ([[HOWTO: The Complete Portage Guide]]). We do stress the use of Entropy rather than Portage, but you will need to understand Portage also.

===Editors===
Wiki editors, make sure you look at the [[Editing Guidelines]] before editing or creating a new article, and add new articles to their appropriate sections below.

<div style="width: 70%;">{{Note| '''Translations'''

We are always looking for translators. We want to be able to bring Sabayon Linux to the entire World, but we need '''your''' help to do that. Please look at the Wiki article on [[En:Translations|translations]] and feel free to edit/add any page you like.
}}</div>

== Sections of Sabayon Linux Wiki ==
{|style="width: 100%"
|[[Image:Pens.png|16px]] [[Editing Guidelines]]
|[[Image:Helmet.png|16px]] [[Wiki Admins]]
|[[Image:Document.png|16px]] [[Wiki News]]
|}

{|style="width: 100%;"
|[[Image:Help-browser.png|left]] '''[[FAQ]]''' Frequently Asked Questions

|[[Image:Abc.png|left]] '''[[En:Introduction|Introduction]]''' Introduction / New Users Start Here
|-
|[[Image:SabayonLogoSmall.png|left|32px]] '''[[En:Sabayon Linux|Sabayon Linux]]''' Information About Sabayon Linux

|[[Image:Beginners-guide.jpg|left|32px]] '''[[En:Beginners Guide|Beginners Guide]]''' from booting to installing
|-
|[[Image:EntropyLogoSmall.png|left|32px]] '''[[En:Entropy|Entropy Package Manager]]''' The Entropy Package Management System

|[[Image:Howto.png|left]] '''[[HOWTOs]]''' HOWTO's for Entropy Systems Only
|-
|[[Image:Information.png|left]] '''[[Tips]]''' Tips & Tricks for your average Joe

|[[Image:Hardware flash.png|left]] '''[[Hardware]]''' Hardware related help
|-
|[[Image:Padlock1.png|left]] '''[[En:Security|Security]]''' Security articles and help

|[[Image:Info.png|left]] '''[[Known Issues]]''' Current Known Issues
|-
|[[Image:Portage.png|left|32px]] '''[[HOWTOs_for_Portage]]''' HOWTO's related to Portage

|[[Image:Archive.png|left|32px]] '''[[Sabayon-Wiki Archive]]''' Old, outdated articles.
|-
|}

__NOTOC__
__NOEDITSECTION__

Portage Package Manager

2013-03-01T12:48:02Z

Aposteeltje: Aposteeltje moved page Portage Package Manager to HOWTOs for Portage: Title indicates that it's about the Package manager. However, this is the HOWTO section for Portage users.

#REDIRECT [[HOWTOs for Portage]]

HOWTOs for Portage

2013-03-01T12:48:02Z

Aposteeltje: Aposteeltje moved page Portage Package Manager to HOWTOs for Portage: Title indicates that it's about the Package manager. However, this is the HOWTO section for Portage users.

{{I18n| [[De:Portage Paketverwalter|de]] [[Portage Package Manager|en]] [[Tr:Portage Package Manager|tr]]}}

[http://en.wikipedia.org/wiki/Portage_(software) Portage] is a package management system used by [http://www.gentoo.org Gentoo Linux]. Gentoo is sometimes referred to as a meta-distribution due to the extreme flexibility of Portage, which even makes it operating-system-independent. [http://www.sabayon.org Sabayon Linux] is based on Gentoo, but is a bit different in a few ways. Portage is not the default package manager for Sabayon and should only be used by those that are highly experienced with Gentoo. Sabayon Linux Entropy Server uses Portage to bring you the binary packages, making your life much simpler.

This page is to separate Portage HowTo articles from Entropy HowTo articles. If you have a HowTo article for Portage, please add it here.

==Warning==

{{Warning| '''The Portage package manager is not the default package manager of Sabayon. It should only be used by advanced users who understand the Portage system and understand what flags can do to a system. If you insist on using Portage and you FUBAR your Sabayon Linux installation, you are on your own. This is your big warning, so pay attention to it.'''}}

=HowTos=

==Portage Stuff==
*[[HOWTO: Install Packages on Sabayon / The Complete Portage Guide]]
*[[HOWTO: Upgrade kernel using genkernel]]
*[[HOWTO: Unoffical Guide To World Update]]
*[[HOWTO: Switch from Test to Stable Packages]]
*[[HOWTO: Use Sabayon LiveDVD/CD to recover GCC]]
*[[HOWTO: Example of Installing 3rd Party Ebuilds]]
*[[HOWTO: Safely mix Entropy and Portage]]
*[[HOWTO: Install Himerge]]
*[[HOWTO: gtk-engines-kde4]]
*[[HOWTO: Install e17]]
*[[HOWTO: Avant Window Navigator (AWN)]]
*[[HOWTO: Latest Compiz-Fusion]]
*[[HOWTO:_Install_VirtualBox]]
*[[Setup VMWare-server]]
*[[HOWTO: Sipie]] << Sirius Radio Player
*[[HOWTO: Setup Mythtv]]
*[[HOWTO: PyKaraoke]]
*[[HOWTO: Install FrostWire]]
*[[Creative XFi titanium driver fix]]
*[[HOWTO: Realtek 8187b Wireless Networking]]
*[[HOWTO: Belkin wireless g usb network adapter F5D7050]]
*[[HOWTO: intel 945 Resolution]]
*[[HOWTO: Installing Bibus in Sabayon Linux - Also how to install sqliteodbc v7.0 ]]

En:Main Page

2013-03-01T12:45:16Z

Aposteeltje:

{{I18n| [[Ca:Main_Page|ca]] [[Cs:Main_Page|cs]] [[De:Hauptseite|de]] [[En:Main_Page|en]] [[Es:Main_Page|es]] [[Fr:Main_Page|fr]] [[Gr:Main_Page|gr]] [[Id:Main_Page|id]] [[It:Main_Page|it]] [[Pl:Strona_Glowna|pl]] [[Ru:Main_Page|ru]] [[Sv:Main_Page|sv]] [[TR:Ana_Sayfa|tr]] [[Zh_TW:Main_Page|zh_tw]]}}

='''Welcome to Sabayon Linux Wiki!'''=
{{Featured|[[Entropy| En:Entropy]]|Entropy is our answer to Portage. This is a binary-based client that is designed to allow more freedom to new users, and more choices in packages in the community repos.}}

Sabayon Linux is based on the source-based distro named [http://www.gentoo.org/ Gentoo]. Gentoo is a highly customizable distro and, using Gentoo's excellent development techniques, we have created a pre-configured distribution with the tenets of Performance, Versatility, and Stability. Please see the [[Introduction]] and [[Sabayon Linux]] sections in this Wiki, and we stress highly that you need to learn how to use the package managers [[Entropy]] and Portage ([[HOWTO: The Complete Portage Guide]]). We do stress the use of Entropy rather than Portage, but you will need to understand Portage also.

===Editors===
Wiki editors, make sure you look at the [[Editing Guidelines]] before editing or creating a new article, and add new articles to their appropriate sections below.

<div style="width: 70%;">{{Note| '''Translations'''

We are always looking for translators. We want to be able to bring Sabayon Linux to the entire World, but we need '''your''' help to do that. Please look at the Wiki article on [[En:Translations|translations]] and feel free to edit/add any page you like.
}}</div>

== Sections of Sabayon Linux Wiki ==
{|style="width: 100%"
|[[Image:Pens.png|16px]] [[Editing Guidelines]]
|[[Image:Helmet.png|16px]] [[Wiki Admins]]
|[[Image:Document.png|16px]] [[Wiki News]]
|}

{|style="width: 100%;"
|[[Image:Help-browser.png|left]] '''[[FAQ]]''' Frequently Asked Questions

|[[Image:Abc.png|left]] '''[[En:Introduction|Introduction]]''' Introduction / New Users Start Here
|-
|[[Image:SabayonLogoSmall.png|left|32px]] '''[[En:Sabayon Linux|Sabayon Linux]]''' Information About Sabayon Linux

|[[Image:Beginners-guide.jpg|left|32px]] '''[[En:Beginners Guide|Beginners Guide]]''' from booting to installing
|-
|[[Image:EntropyLogoSmall.png|left|32px]] '''[[En:Entropy|Entropy Package Manager]]''' The Entropy Package Management System

|[[Image:Howto.png|left]] '''[[HOWTOs]]''' HOWTO's for Entropy Systems Only
|-
|[[Image:Information.png|left]] '''[[Tips]]''' Tips & Tricks for your average Joe

|[[Image:Hardware flash.png|left]] '''[[Hardware]]''' Hardware related help
|-
|[[Image:Padlock1.png|left]] '''[[En:Security|Security]]''' Security articles and help

|[[Image:Info.png|left]] '''[[Known Issues]]''' Current Known Issues
|-
|[[Image:Portage.png|left|32px]] '''[[Portage Package Manager]]''' HOWTO's related to Portage

|[[Image:Archive.png|left|32px]] '''[[Sabayon-Wiki Archive]]''' Old, outdated articles.
|-
|}

__NOTOC__
__NOEDITSECTION__

Installing and configure Compiz Fusion

2013-03-01T12:42:01Z

Aposteeltje:

HOWTO: Unoffical Guide To World Update

2013-02-23T14:16:21Z

Aposteeltje: /* Updating */

{{Warning| '''Portage (emerge) is not the primary package manager for Sabayon, this article is for advanced users only. In other words if this fails for you, its your fault. You have been warned.'''}}
=World Update and Understanding Configs=

==Updating==

First let me say that there is a several ways to doing things on SL. I am not saying that my way is the best way by any means. This is simply my way of how I do things with a fresh install to make a stable system. You should probably read the other articles below first to better understand things.

First thing - I alway buy my hardware that I know is linux supported and has good drivers. So get to know your hardware, I can't say that enough as it will save you a lot of headaches.

'''DO NOTE''' - I can not tell you what you can safely remove from your system as you need to know your hardware and what is safe to uninstall, remove from config files and remove from kernel. I am going to try and stay very basic here so you can get the idea.

Fresh install and everything is working great so now what?

----
Well I head to the /etc/make.conf file and edit that thing to my liking and double checking things over. I remove any unnecessary things. Remember to edit these files you must be root. If you like nano you can simple go into Konsole and punch in su than enter your password. You can edit the file by doing

{{Console| <pre class="clear"># nano -w /etc/make.conf</pre>}}

or if you simply must have a GUI you can go to konsole and enter

{{Console| <pre class="clear">$ kdesu konqueror</pre>}}

and when the box pops up, enter your password, wait a bit and a new window will come up. In that window you are root to everything and can edit anything. Pretty simple so far right? If you need help figuring out what options are available in the [http://www.gentoo-wiki.info/Make.conf.example make.conf] then refer to the Gentoo Handbook and Wiki often.

----
Ok, so now that I got that set I like to head to the kernel and add to it and remove things I don't need by doing in konsole:

{{Console| <pre class="clear"># zcat /proc/config.gz > /usr/src/config

# genkernel --kernel-config=/usr/src/config --menuconfig --bootloader=grub --gensplash=sabayon all --luks</pre>}}

'''or if you use lvm do:''' - noted for waltercool

# genkernel --kernel-config=/usr/src/config --menuconfig --bootloader=grub --gensplash=sabayon --lvm2 all --luks

''note the # means you must be root, don't actually use the #''

This step is not necessary if you don't care that your kernel is big. I always need to enable some sound stuff and you may need to enable drivers, again, this is where knowing where your hardware is very important. You remove the wrong thing and your puter will not boot. Skip this step if you have a funny look on your face at this time.

----
NOTE: Before doing the following 'emerge -e' commands, you may want to customize your CFLAGS in make.conf so that it is optimized for your CPU type. The following two commands take very a long time, so it's worth it to optimize while you are taking the time to do this. Please refer to [http://en.gentoo-wiki.com/wiki/Safe_Cflags Gentoo Safe CFLAGS Guide] for the correct setting for your specific CPU. Do not change your CHOST as described in that guide, changing CHOST is dangerous and not recommended. See [http://www.gentoo-wiki.info/HOWTO_change_CHOST_relatively_safely this HOWTO] if you wish to risk changing your CHOST.

Now some of you may totally think I am crazy here but as far as software removal I do that later. Yes I know I can remove software at this time that I will never use and save time when I recompile the system, but this is my unofficial stable system and I know it will work cause I have done it several times. So with that being said I want to now recompile just the system. Now I prefer to do :

# emerge -e system || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

Notice I have not done an emerge --sync yet and I don't want to do that yet, that will come later. So now several hours are going to go by. This a great thing to do when you are about to go to bed. After that is done, I like to do the world recompile:

# emerge -e world || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

do note once again that I have not used emerge --sync yet and this is going to be another lengthy process. You may do both commands at once by simply doing:

# emerge -e system || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done && emerge -e world || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

I just like to break it up.

----
So now I have finished recompiling everything and my processor is going Dude! Well now I punch in:

# emerge --sync && layman -S

to update my portage tree and overlays. First time syncs on SL are slow, I promise they will get faster after the first time. Once that is done I punch in:

# emerge -upDN world

this will pull up just under 400 packages, WOW!! Well lets get the show on the road.

# emerge -uN world

Now you look at that and go what happened to the D ?, again this is my guide and that will come later. Now you are probably sitting there thinking I thought SL doesn't recommend a world update. My feelings are this: no you don't need to, but SL 3.3 makes it a piece of cake to world update. Pre 3.3 I don't recommend, as you will be forever swamped with recompiling. Now with the world update you are going to run into bumps and this is where reading the ERROR MESSAGES is going to come to be Very Important. If you listen to what portage is telling you and use the Gentoo bugzilla and Gentoo forums for searching you can usually find the solution. Once a package fails I simply:

# emerge --resume --skipfirst

to continue on. I like to do this method to see what packages are failing. If you don't care:

# emerge -uN world || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

then it will auto skip and keep on going till finished. Now I don't try and fix any packages till it is completely done. Once it is done I look look at

#emerge -upN world

and go through each package and install it with the fix needed to get it to install. At this time I will simple remove any packages that have failed that I know I don't need. So now we are done and

# emerge -upN world

shows no packages left in it, time I fire up

# emerge -upDN world

YAY more packages to compile! The amount of packages won't be that much. So we wait for that to finish and I usually fix the errors as it goes along since it isn't very many packages. Now we have the entire system rebuilt, well almost. It's time to run:

# revdep-rebuild

and if that fails do:

# revdep-rebuild

It will find more packages to recompile! Your processor is probably plotting some sort of revenge against you at this time. So now what? Well, you are gonna have some config files that are screaming for an update. Now I like to use:

# etc-update

There is several ways to update config files, this is my way of doing it. So I punch in etc-update and many will auto merge, which is great with me. I look over the remaining ones left and determine if they are safe or not to update. Off the top of my head I believe all changes in 3.3 are safe, but look and if you are unsure, don't do it. So we have recompiled everything after making changes to system, updated the config files. Are we done? Do we dare reboot? Let's live dangerously and reboot, I mean a reinstall is only 40 minutes to do anyway right?

----
So we rebooted, prayed and we made it back to our Desktop!! So now, I like all the multimedia features the web has to offer, so I want to experience it all, so I open up my konsole again and punch in:

USE="divx gmedia gtk nls quicktime realmedia wmp" emerge mplayerplug-in

Yes, I know you can add this to your package.use file, but this is my guide and you should add it to your /etc/portage/package.use file for future use. Now I can sit back and view all the goodness of web multimedia! I hate totem handling the web plugins cause it sucks at doing so. I don't uninstall totem I simply move all the totem plugins out of the plugins folder:
/usr/lib/nsbrowser/plugins
and put em in
/usr/lib/nsbrowser
Just in case I ever want to put them back.

Alrighty then, we are world updated now. You can continue to stay world update and SL updated with the overlay by:

# emerge --sync && layman -S && emerge -uDN world

A handy automated script for this can be found here:
[http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=11870 Update Script]

----
Conclusion - my systems are rock solid no matter what I throw at them. It's a long process, but that's fine with me cause the results are worth it. Do keep in mind that it will take less time with the mini as there is less to deal with. It will require thinking and deciphering and good abilities of effective searching. No I can not help you world update your system as I have no idea what hardware you use or what you use your computer for. Is there a chance you may hose your system? Of course there is! It shouldn't happen if you pay attention. I can't stress enough to read the [http://www.gentoo.org/doc/en/handbook/index.xml Gentoo Handbook], look at the [http://gentoo-wiki.com Gentoo Wiki], look at the [http://forums.gentoo.org/ Gentoo Forum], look at the [http://wiki.sabayonlinux.org SL Wiki], look at the [http://www.sabayonlinux.org/forum SL Forum] and don't forget [http://google.com Google], bookmark them all!

That's it in a nutshell and I take NO and I mean NO Responsibilities for a hosed system. Your millage is going to vary of course depending on what hardware and software you use.

Input is welcome and I will answer questions if I know the answers.

HAPPY COMPILING!

[http://www.sabayonlinux.org/forum/viewtopic.php?t=5531 Forum Discussion]

==Understanding make.conf - An Introduction==
{{File|/etc/make.conf|<pre class="clear">
# These settings were set by the catalyst build script that automatically built this stage
# Please consult /etc/make.conf.example for a more detailed example
CFLAGS="-O3 -march=native -funroll-all-loops -m3dnow -msse3 -funit-at-a-time -fpeel-loops -ftracer -funswitch-loops -fomit-frame-pointer -pipe"
LDFLAGS="-Wl,-O1 -Wl,--enable-new-dtags -Wl,--sort-common -s"
CHOST="i586-pc-linux-gnu"
USE="win32codecs mp3 quicktime type1 divx4linux dvb dvd dvdread live mpeg nvidia jpeg truetype v4l v4l2 xv xvid multilib gnutls arts cups ppds foomatic-db \
alsa gimpprint freetype gnome X gtk gtk2 unicode moznocompose moznoirc moznomail kde qt samba xinerama xine theora kdeenablefinal wifi hal ieee1394 \
oggvorbis lm_sensors logitech-mouse zeroconf artswrappersuid nptl nptlonly rdesktop dvdr css gphoto2 openexr speex jpeg2k povray scanner musicbrainz \
accessibility audiofile exif xscreensaver ffmpeg vcd sndfile musepack asterisk mbrola pam_chroot pam_timestamp pwdb pda sms irda kig-scripting speedo \
browserplugin nsplugin ldap kerberos firefox dga aac dts xvmc dbus hal dvi on-the-fly-crypt dri xprint acpi ada ruby perforce cjk fat hfs jfs ntfs reiser4 \
xfs reiserfs skins cdda real shout stream a52 wxwindows vlm lirc libcaca remote stats lcd unichrome 7zip commercial mozsvg canvas xml2 glut java glitz svg \
avahi ogg vorbis aalib flac gdbm mikmod timidity kdgraphics dlloader exscalibar ipod visualization mono cdr nntp cairo djvu nautilus evo ole pdf xml ladspa \
soundtouch bzip2 udev mad fuse rtsp tiff kdehiddenvisibility dvi usb kipi aiglx musicbrainz pulseaudio dv lame mp3rtp udev cdr dvi djvu libnotify bzip2 aalib \
startup-notification nsplugin jingle gsm dbox2 opengl sdl png gif qt3 qt4 qt3support apache2 mysql php ssl xml berkdb innobd pcre"
CXXFLAGS="${CFLAGS}"
ACCEPT_KEYWORDS="~x86"
LINGUAS="en"
MAKEOPTS="-s -j3"
PORTAGE_NICENESS="8"
FEATURES="parallel-fetch"
CONFIG_PROTECT="/usr/kde/3.5/share/config/kdm/ /etc"
VIDEO_CARDS="vesa vga nvidia"
INPUT_DEVICES="evdev keyboard mouse"
LIRC_DEVICES="audio audio_alsa"
PORTAGE_ELOG_CLASSES="warn error log info"
PORTAGE_ELOG_SYSTEM="save"
# FEATURES="buildpkg"
source /usr/portage/local/layman/make.conf
EMERGE_DEFAULT_OPTS="--with-bdeps y"
</pre>}}

Above you will find a make.conf and is a vital component to your operating system. If you don't know this file you are defeating the purpose of this distro. One of the biggest things about gentoo based is being able to build the operating sytem to you. Using the default settings are going to work, but you are not taking full advantage of your potentials. You can ease our portage frustration also, like compiling issues.

Why do we need make.conf?
Portage uses this file to know how to build your entire system. All the settings you put here, portage reads and builds to them.

'''CFLAGS'''
CFLAGS are C compiler flags, usually GCC (GNU Compiler Collection) options.
CFLAGS are commonly used to specify the architecture of your computer, as well as the CPU you are using and any other special options you would like to enable or disable. This information is important to GCC because it tells it exactly how to customize the assembly instructions it creates from the application's source code.
http://gentoo-wiki.com/CFLAGS

'''LDFLAGS'''
Deals with your hash tables and compiler See for more information:
http://gentoo-wiki.com/TIP_Safe_LDFLAGS
http://lwn.net/Articles/192624/
Your not going to be touching these, so moving right along.

'''CHOST'''
Variable declares the target build host for your system You don't want to change this value unless you know what you are doing. You simply can't change it to i686 and go about using your computer. There is situations that may cause you to have to change this. For instance, lets say you upgrade your cpu or need a certain package that won't work with your current architect. Gentoo has a guide for changing it. Follow it closely or you will have a hosed system.
http://www.gentoo.org/doc/en/change-chost.xml

'''CXXFLAGS'''
CXXFLAGS is set to use all the options present in CFLAGS. This is what you'll want almost without fail. You shouldn't ever need to specify additional options in CXXFLAGS.
http://www.gentoo.org/doc/en/gcc-optimization.xml

'''USE'''
In Gentoo a USE flag is a representation of an option, a global setting for your final system. USE flags affect how many of the packages on your system will build. These depend on the software and your computer usage. It's important to know these and to thin the list down to your usage. You will see that I have a lot in mine, but that is because of testing I do for SL. All these USE settings are global, meaning they effect every package on your system. The more USE settings you have, the more conflicts you can encounter with portage when compiling software. There is a /etc/portage/package.use file that you can use to individually tell packages how you want them built.
http://gentoo-portage.com/USE
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=2

'''ACCEPT_KEYWORDS="~x86"'''
This is for setting which branch of portage you want to use. Stable vs. Unstable "bleeding edge". You can see by the ~ we are not using the stable branch so we are bleeding edge.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=3

'''LINGUAS'''
I hope this is self explanatory, but if not - your language
http://www.gentoo.org/doc/en/guide-localization.xml

'''MAKEOPTS'''
You define how many parallel compilations should occur when you install a package. A good choice is the number of CPUs in your system plus one, but this guideline isn't always perfect.
http://gentoo-wiki.com/Safe_Cflags
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=5

'''PORTAGE_NICENESS'''
If you keep using your computer while compiling packages you will notice that your box is less responsive than usual. This is caused by having two "groups" of processes with the same nice priority: your usual running processes, and emerge (and its child processes). Now, if you could renice emerge and its children to a higher nice value (i.e. lower priority), compiling would take somewhat longer, but your workstation will be as responsive as before.
http://gentoo-wiki.com/Portage_Niceness

'''FEATURES'''
Portage has several additional features that makes your Gentoo experience even better. Many of these features rely on certain software tools that improve performance, reliability, security, ...
Parallel fetch:
When you are emerging a series of packages, Portage can fetch the source files for the next package in the list even while it is compiling another package, thus shortening compile times..
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=3

'''CONFIG_PROTECT'''
This variable contains a space-delimited list of directories which should be protected by Portage during updates.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=5

'''VIDEO_CARDS'''
I see people's make.conf often and in the default make.conf there is like 20 video cards listed. Why compile more than you have too? Get rid of all the cards not in your computer.
http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml

'''INPUT_DEVICES'''
The same goes here, get rid of any equipment you don't have. My desktop doesn't have touchpad - why compile it?
http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml

'''LIRC_DEVICES'''
Linux Infrared Remote Control - this is where you are going to set your devices
http://gentoo-wiki.com/HOWTO_LIRC

'''source /usr/portage/local/layman/make.conf''' -- location for your layman, for managing your overlays such as sabayon, xeffects, etc....

Extras that I have added, just for my own use. You will not see these in a default make.conf
------------------------------------------------------------------------------------------------------------------------

'''PORTAGE_ELOG_CLASSES'''
Ebuild Logging -
Portage can create per-ebuild logfiles, but only when the PORT_LOGDIR variable is set to a location that is writable by Portage (the portage user). By default this variable is unset. If you don't set PORT_LOGDIR, then you won't receive any build logs with the current logging system, though you may receive some logs from the new elog. If you do have PORT_LOGDIR defined and you use elog, you will receive build logs and any logs saved by elog, as explained below.

Portage offers fine-grained control over logging through the use of elog:

* '''PORTAGE_ELOG_CLASSES:''' This is where you set what kinds of messages to be logged. You can use any space-separated combination of info, warn, error, log, and qa.
o info: Logs "einfo" messages printed by an ebuild
o warn: Logs "ewarn" messages printed by an ebuild
o error: Logs "eerror" messages printed by an ebuild
o log: Logs the "elog" messages found in some ebuilds
o qa: Logs the "QA Notice" messages printed by an ebuild
'''PORTAGE_ELOG_SYSTEM:''' This selects the module(s) to process the log messages. If left empty, logging is disabled. You can use any space-separated combination of save, custom, syslog, mail, save_summary, and mail_summary. You must select at least one module in order to use elog.
* save: This saves one log per package in $PORT_LOGDIR/elog, or /var/log/portage/elog if $PORT_LOGDIR is not defined.
* custom: Passes all messages to a user-defined command in $PORTAGE_ELOG_COMMAND; this will be discussed later.
* syslog: Sends all messages to the installed system logger.
* mail: Passes all messages to a user-defined mailserver in $PORTAGE_ELOG_MAILURI; this will be discussed later. The mail features of elog require >=portage-2.1.1.
* save_summary: Similar to save, but it merges all messages in $PORT_LOGDIR/elog/summary.log, or /var/log/portage/elog/summary.log if $PORT_LOGDIR is not defined.
* mail_summary: Similar to mail, but it sends all messages in a single mail when emerge exits.
http://www.gentoo.org/doc/en/handbook/h ... t=3&chap=1
**portage-2.1.3: "echo" - this prints all logged messages again at the end of the emerge

'''FEATURES="buildpkg"''' for building your own binary packages and saving them
http://gentoo-wiki.com/HOWTO_setup_a_PO ... OST_server
http://www.gentoo.org/proj/en/base/amd64/emul/index.xml

source /usr/portage/local/layman/make.conf -- location for your layman, for managing your overlays such as sabayon, xeffects, etc....

'''EMERGE_DEFAULT_OPTS="--with-bdeps y"''' # considers also build-time deps at dependency calculations
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=2

'''Man Make.conf'''
http://gentoo-wiki.com/MAN_makeconf

Do you see now why it is important to know this file? This file can make your gentoo based distro a much better experience. The gentoo handbook can help you set it up properly. Remember to take full advantage of changes, you need to be using certain flags like emerge --newuse foo. Recompiling your entire sytem and world is what you need to do to take advantage of your changes. Like for me I simple run emerge -uDN --world - that will update and make sure all packages are following my settings. If I changed a USE flag it will rebuild the packages effected and update packages to latest in portage.

Recompiling your system is not going to be easy if you are new to all of this. I recommend getting to know portage and how to work with portage before attempting it. It's something you just don't jump into. Your going to run into all sorts of issues and gonna have to search and find your answers. As of 3.4 you are gonna run into a python update, which requires taking care of first as things will break and need to get updated to the new python. Pending on your system - it can take several days to complete the process.
Learn your world file and cleaning it out before starting, this will save many hours of recompiling packages you don't need. The world file is a record of packages which have been specifically installed by the user. More specifically it's a list of packages which the user wants to keep installed and updated on their system. It will not record the dependencies of those packages, but instead uses the dependencies of the currently installed packages to keep track of this information. http://gentoo-wiki.com/HOWTO_Use_Portage_Correctly

You will also want to get yourself familiar with the files in your /etc/portage/ you will need to use them to mask and unmask needed packages. Also use em for telling how certain packages should be built.

Read thru the unofficial guide for a world update
viewtopic.php?f=54&t=5531

Best advice - Use the operating system till you know it, than start diving into the depths of the internal stuff. I know it is frustrating for people that are new, but if you give it time and stick with it, it will all come together. If all this information totally terrifies you, than stick with the default settings. Use the information for you knowledge. Topic is open for discussion.

[http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578 Forum Discussion]

==Config Files - An Introduction==

Without config files the operating sytem would be blah. Are you finding yourself confused with all the messages of portage telling you:
IMPORTANT: 124 config files in '/usr/share/X11/xkb' need updating

Well unfortunately with the amount of config files on your computer it is impossible to go over them all. I'm going to try and hit on the more important ones that are used more frequently.

Do you have to update your config files? The answer will be yes. Why? Cause things change over time.

How do I update my config files, portage keeps telling me I have config files to update? Well there is several ways to do this, you will need to run one of the following more popular methods.:
--------etc-update: http://www.gentoo-wiki.info/HOWTO_etc-update
--------dispatch-conf: http://www.gentoo-wiki.info/TIP_dispatch-conf

Do not and I repeat, do not blindly auto merge config file updates. You can hose your system to the point it won't boot back up. Well there is so many, how do I know if it is safe to or not? Good question and the rule of thumb is - if you have not edited a config file than generally your are safe, but this isn't a sure fire way. Using dispatch-conf will keep a back up copy of you old config files in case you need to restore them. Get to know your config files so you can be aware of certain files.

Remember to edit the config files you need to be root, so you will want to open konsole, type su, enter password and than nano or vi the file. You can do this via GUI too, just open konsole and run kdesu konqueror and when the box comes up, enter you root password and than you will have a root file manager window, gnome users will use gksu nautilus.

'''/etc/rc.conf''' - for general, system-wide configuration. Read the comments in the file, it's pretty well explained. If your window manager suddenly changes upon boot, this is one of the first files to check.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/conf.d/xdm''' - Is what controls your GUI login and window Manager. So if you GUI or login is messed up, be sure to check it out. It's self explanatory.
http://www.gentoo-wiki.info/HOWTO_Activate_Graphical_login

'''/etc/hosts''' - helps in resolving host names to IP addresses for hosts that aren't resolved by your nameserver.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/make.conf''' - This file contains various variables that are used by Portage. Portage will check the currently-defined environment variables first for any settings.
http://www.gentoo-wiki.info/MAN_makeconf
http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578

'''/boot/grub/grub.conf''' - Your boot manager so you can boot 1 or more operating systems. This is one of the first screens you will see and is asking for you to choose what operating system to boot.
http://www.gentoo-wiki.info/HOWTO_Quick_GRUB
http://www.gentoo-wiki.info/HOWTO_Dual_boot

'''/etx/X11/xorg.conf''' - Xorg is the X Window server which allows users to have a graphical environment. Got resolution problems? This file is for you.
http://www.gentoo.org/doc/en/xorg-config.xml

'''/etc/conf.d/net''' - your network configuration, see /etc/conf.d/net.example for a very well documented example â€“ dhcp, static, wireless, wired networking settings
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/resolv.conf''' - your DNS file, nothing to complicated, but if you can access your router but can't get web pages to load - check this file for DNS settings
http://www.gentoo.org/doc/en/home-router-howto.xml

'''/etc/fstab''' - This file contains the mount points of your partitions. Need to mount a hard drive? Add it here so it is available on every boot up.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/modules.autoload.d/kernel-2.6''' - You may have decided to compile some kernel components as modules (as opposed to compiled directly into the kernel) and would like to have them autoloaded on bootup like you did with 2.4. Also, if you installed any external modules from the portage tree you will probably want to autoload them too.
http://www.gentoo.org/doc/en/migration-to-2.6.xml

'''/etc/exports''' This is great for doing shares on the network using NFS
http://www.gentoo-wiki.info/HOWTO_Share_Directories_via_NFS
This also works great of sharing portage across multiple computers. You only need to sync one main computer than share your portage so the other computers will connect to your main computer for emerges
http://www.gentoo-wiki.info/HOWTO_Using_a_shared_portage_via_NFS

This hardly puts a dent in the amount of config files, but those are the ones I run across the most, plus trying to keep it friendly for people new to config files. I could of mentioned like local.start, but that is for experienced people.

Generally you can google and find some thing about the config file. Enter into google "gentoo xorg.conf" and you will find your answer. Feel free to add more that I may have missed here.

[http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10863 Forum Discussion]

HOWTO: Unoffical Guide To World Update

2013-02-23T14:12:15Z

Aposteeltje: /* Updating */

{{Warning| '''Portage (emerge) is not the primary package manager for Sabayon, this article is for advanced users only. In other words if this fails for you, its your fault. You have been warned.'''}}
=World Update and Understanding Configs=

==Updating==

First let me say that there is a several ways to doing things on SL. I am not saying that my way is the best way by any means. This is simply my way of how I do things with a fresh install to make a stable system. You should probably read the other articles below first to better understand things.

First thing - I alway buy my hardware that I know is linux supported and has good drivers. So get to know your hardware, I can't say that enough as it will save you a lot of headaches.

'''DO NOTE''' - I can not tell you what you can safely remove from your system as you need to know your hardware and what is safe to uninstall, remove from config files and remove from kernel. I am going to try and stay very basic here so you can get the idea.

Fresh install and everything is working great so now what?

----
Well I head to the /etc/make.conf file and edit that thing to my liking and double checking things over. I remove any unnecessary things. Remember to edit these files you must be root. If you like nano you can simple go into Konsole and punch in su than enter your password. You can edit the file by doing

{{Console| <pre class="clear"># nano -w /etc/make.conf</pre>}}

or if you simply must have a GUI you can go to konsole and enter

{{Console| <pre class="clear">$ kdesu konqueror</pre>}}

and when the box pops up, enter your password, wait a bit and a new window will come up. In that window you are root to everything and can edit anything. Pretty simple so far right? If you need help figuring out what options are available in the [http://www.gentoo-wiki.info/Make.conf.example make.conf] then refer to the Gentoo Handbook and Wiki often.

----
Ok, so now that I got that set I like to head to the kernel and add to it and remove things I don't need by doing in konsole:

{{Console| <pre class="clear"># zcat /proc/config.gz > /usr/src/config

# genkernel --kernel-config=/usr/src/config --menuconfig --bootloader=grub --gensplash=sabayon all --luks</pre>}}

'''or if you use lvm do:''' - noted for waltercool

# genkernel --kernel-config=/usr/src/config --menuconfig --bootloader=grub --gensplash=sabayon --lvm2 all --luks

''note the # means you must be root, don't actually use the #''

This step is not necessary if you don't care that your kernel is big. I always need to enable some sound stuff and you may need to enable drivers, again, this is where knowing where your hardware is very important. You remove the wrong thing and your puter will not boot. Skip this step if you have a funny look on your face at this time.

----
NOTE: Before doing the following 'emerge -e' commands, you may want to customize your CFLAGS in make.conf so that it is optimized for your CPU type. The following two commands take very a long time, so it's worth it to optimize while you are taking the time to do this. Please refer to [http://en.gentoo-wiki.com/wiki/Safe_Cflags Gentoo Safe CFLAGS Guide] for the correct setting for your specific CPU. Do not change your CHOST as described in that guide, changing CHOST is dangerous and not recommended. See [http://gentoo-wiki.com/HOWTO_change_CHOST_relatively_safely this HOWTO] if you wish to risk changing your CHOST.

Now some of you may totally think I am crazy here but as far as software removal I do that later. Yes I know I can remove software at this time that I will never use and save time when I recompile the system, but this is my unofficial stable system and I know it will work cause I have done it several times. So with that being said I want to now recompile just the system. Now I prefer to do :

# emerge -e system || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

Notice I have not done an emerge --sync yet and I don't want to do that yet, that will come later. So now several hours are going to go by. This a great thing to do when you are about to go to bed. After that is done, I like to do the world recompile:

# emerge -e world || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

do note once again that I have not used emerge --sync yet and this is going to be another lengthy process. You may do both commands at once by simply doing:

# emerge -e system || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done && emerge -e world || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

I just like to break it up.

----
So now I have finished recompiling everything and my processor is going Dude! Well now I punch in:

# emerge --sync && layman -S

to update my portage tree and overlays. First time syncs on SL are slow, I promise they will get faster after the first time. Once that is done I punch in:

# emerge -upDN world

this will pull up just under 400 packages, WOW!! Well lets get the show on the road.

# emerge -uN world

Now you look at that and go what happened to the D ?, again this is my guide and that will come later. Now you are probably sitting there thinking I thought SL doesn't recommend a world update. My feelings are this: no you don't need to, but SL 3.3 makes it a piece of cake to world update. Pre 3.3 I don't recommend, as you will be forever swamped with recompiling. Now with the world update you are going to run into bumps and this is where reading the ERROR MESSAGES is going to come to be Very Important. If you listen to what portage is telling you and use the Gentoo bugzilla and Gentoo forums for searching you can usually find the solution. Once a package fails I simply:

# emerge --resume --skipfirst

to continue on. I like to do this method to see what packages are failing. If you don't care:

# emerge -uN world || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

then it will auto skip and keep on going till finished. Now I don't try and fix any packages till it is completely done. Once it is done I look look at

#emerge -upN world

and go through each package and install it with the fix needed to get it to install. At this time I will simple remove any packages that have failed that I know I don't need. So now we are done and

# emerge -upN world

shows no packages left in it, time I fire up

# emerge -upDN world

YAY more packages to compile! The amount of packages won't be that much. So we wait for that to finish and I usually fix the errors as it goes along since it isn't very many packages. Now we have the entire system rebuilt, well almost. It's time to run:

# revdep-rebuild

and if that fails do:

# revdep-rebuild

It will find more packages to recompile! Your processor is probably plotting some sort of revenge against you at this time. So now what? Well, you are gonna have some config files that are screaming for an update. Now I like to use:

# etc-update

There is several ways to update config files, this is my way of doing it. So I punch in etc-update and many will auto merge, which is great with me. I look over the remaining ones left and determine if they are safe or not to update. Off the top of my head I believe all changes in 3.3 are safe, but look and if you are unsure, don't do it. So we have recompiled everything after making changes to system, updated the config files. Are we done? Do we dare reboot? Let's live dangerously and reboot, I mean a reinstall is only 40 minutes to do anyway right?

----
So we rebooted, prayed and we made it back to our Desktop!! So now, I like all the multimedia features the web has to offer, so I want to experience it all, so I open up my konsole again and punch in:

USE="divx gmedia gtk nls quicktime realmedia wmp" emerge mplayerplug-in

Yes, I know you can add this to your package.use file, but this is my guide and you should add it to your /etc/portage/package.use file for future use. Now I can sit back and view all the goodness of web multimedia! I hate totem handling the web plugins cause it sucks at doing so. I don't uninstall totem I simply move all the totem plugins out of the plugins folder:
/usr/lib/nsbrowser/plugins
and put em in
/usr/lib/nsbrowser
Just in case I ever want to put them back.

Alrighty then, we are world updated now. You can continue to stay world update and SL updated with the overlay by:

# emerge --sync && layman -S && emerge -uDN world

A handy automated script for this can be found here:
[http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=11870 Update Script]

----
Conclusion - my systems are rock solid no matter what I throw at them. It's a long process, but that's fine with me cause the results are worth it. Do keep in mind that it will take less time with the mini as there is less to deal with. It will require thinking and deciphering and good abilities of effective searching. No I can not help you world update your system as I have no idea what hardware you use or what you use your computer for. Is there a chance you may hose your system? Of course there is! It shouldn't happen if you pay attention. I can't stress enough to read the [http://www.gentoo.org/doc/en/handbook/index.xml Gentoo Handbook], look at the [http://gentoo-wiki.com Gentoo Wiki], look at the [http://forums.gentoo.org/ Gentoo Forum], look at the [http://wiki.sabayonlinux.org SL Wiki], look at the [http://www.sabayonlinux.org/forum SL Forum] and don't forget [http://google.com Google], bookmark them all!

That's it in a nutshell and I take NO and I mean NO Responsibilities for a hosed system. Your millage is going to vary of course depending on what hardware and software you use.

Input is welcome and I will answer questions if I know the answers.

HAPPY COMPILING!

[http://www.sabayonlinux.org/forum/viewtopic.php?t=5531 Forum Discussion]

==Understanding make.conf - An Introduction==
{{File|/etc/make.conf|<pre class="clear">
# These settings were set by the catalyst build script that automatically built this stage
# Please consult /etc/make.conf.example for a more detailed example
CFLAGS="-O3 -march=native -funroll-all-loops -m3dnow -msse3 -funit-at-a-time -fpeel-loops -ftracer -funswitch-loops -fomit-frame-pointer -pipe"
LDFLAGS="-Wl,-O1 -Wl,--enable-new-dtags -Wl,--sort-common -s"
CHOST="i586-pc-linux-gnu"
USE="win32codecs mp3 quicktime type1 divx4linux dvb dvd dvdread live mpeg nvidia jpeg truetype v4l v4l2 xv xvid multilib gnutls arts cups ppds foomatic-db \
alsa gimpprint freetype gnome X gtk gtk2 unicode moznocompose moznoirc moznomail kde qt samba xinerama xine theora kdeenablefinal wifi hal ieee1394 \
oggvorbis lm_sensors logitech-mouse zeroconf artswrappersuid nptl nptlonly rdesktop dvdr css gphoto2 openexr speex jpeg2k povray scanner musicbrainz \
accessibility audiofile exif xscreensaver ffmpeg vcd sndfile musepack asterisk mbrola pam_chroot pam_timestamp pwdb pda sms irda kig-scripting speedo \
browserplugin nsplugin ldap kerberos firefox dga aac dts xvmc dbus hal dvi on-the-fly-crypt dri xprint acpi ada ruby perforce cjk fat hfs jfs ntfs reiser4 \
xfs reiserfs skins cdda real shout stream a52 wxwindows vlm lirc libcaca remote stats lcd unichrome 7zip commercial mozsvg canvas xml2 glut java glitz svg \
avahi ogg vorbis aalib flac gdbm mikmod timidity kdgraphics dlloader exscalibar ipod visualization mono cdr nntp cairo djvu nautilus evo ole pdf xml ladspa \
soundtouch bzip2 udev mad fuse rtsp tiff kdehiddenvisibility dvi usb kipi aiglx musicbrainz pulseaudio dv lame mp3rtp udev cdr dvi djvu libnotify bzip2 aalib \
startup-notification nsplugin jingle gsm dbox2 opengl sdl png gif qt3 qt4 qt3support apache2 mysql php ssl xml berkdb innobd pcre"
CXXFLAGS="${CFLAGS}"
ACCEPT_KEYWORDS="~x86"
LINGUAS="en"
MAKEOPTS="-s -j3"
PORTAGE_NICENESS="8"
FEATURES="parallel-fetch"
CONFIG_PROTECT="/usr/kde/3.5/share/config/kdm/ /etc"
VIDEO_CARDS="vesa vga nvidia"
INPUT_DEVICES="evdev keyboard mouse"
LIRC_DEVICES="audio audio_alsa"
PORTAGE_ELOG_CLASSES="warn error log info"
PORTAGE_ELOG_SYSTEM="save"
# FEATURES="buildpkg"
source /usr/portage/local/layman/make.conf
EMERGE_DEFAULT_OPTS="--with-bdeps y"
</pre>}}

Above you will find a make.conf and is a vital component to your operating system. If you don't know this file you are defeating the purpose of this distro. One of the biggest things about gentoo based is being able to build the operating sytem to you. Using the default settings are going to work, but you are not taking full advantage of your potentials. You can ease our portage frustration also, like compiling issues.

Why do we need make.conf?
Portage uses this file to know how to build your entire system. All the settings you put here, portage reads and builds to them.

'''CFLAGS'''
CFLAGS are C compiler flags, usually GCC (GNU Compiler Collection) options.
CFLAGS are commonly used to specify the architecture of your computer, as well as the CPU you are using and any other special options you would like to enable or disable. This information is important to GCC because it tells it exactly how to customize the assembly instructions it creates from the application's source code.
http://gentoo-wiki.com/CFLAGS

'''LDFLAGS'''
Deals with your hash tables and compiler See for more information:
http://gentoo-wiki.com/TIP_Safe_LDFLAGS
http://lwn.net/Articles/192624/
Your not going to be touching these, so moving right along.

'''CHOST'''
Variable declares the target build host for your system You don't want to change this value unless you know what you are doing. You simply can't change it to i686 and go about using your computer. There is situations that may cause you to have to change this. For instance, lets say you upgrade your cpu or need a certain package that won't work with your current architect. Gentoo has a guide for changing it. Follow it closely or you will have a hosed system.
http://www.gentoo.org/doc/en/change-chost.xml

'''CXXFLAGS'''
CXXFLAGS is set to use all the options present in CFLAGS. This is what you'll want almost without fail. You shouldn't ever need to specify additional options in CXXFLAGS.
http://www.gentoo.org/doc/en/gcc-optimization.xml

'''USE'''
In Gentoo a USE flag is a representation of an option, a global setting for your final system. USE flags affect how many of the packages on your system will build. These depend on the software and your computer usage. It's important to know these and to thin the list down to your usage. You will see that I have a lot in mine, but that is because of testing I do for SL. All these USE settings are global, meaning they effect every package on your system. The more USE settings you have, the more conflicts you can encounter with portage when compiling software. There is a /etc/portage/package.use file that you can use to individually tell packages how you want them built.
http://gentoo-portage.com/USE
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=2

'''ACCEPT_KEYWORDS="~x86"'''
This is for setting which branch of portage you want to use. Stable vs. Unstable "bleeding edge". You can see by the ~ we are not using the stable branch so we are bleeding edge.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=3

'''LINGUAS'''
I hope this is self explanatory, but if not - your language
http://www.gentoo.org/doc/en/guide-localization.xml

'''MAKEOPTS'''
You define how many parallel compilations should occur when you install a package. A good choice is the number of CPUs in your system plus one, but this guideline isn't always perfect.
http://gentoo-wiki.com/Safe_Cflags
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=5

'''PORTAGE_NICENESS'''
If you keep using your computer while compiling packages you will notice that your box is less responsive than usual. This is caused by having two "groups" of processes with the same nice priority: your usual running processes, and emerge (and its child processes). Now, if you could renice emerge and its children to a higher nice value (i.e. lower priority), compiling would take somewhat longer, but your workstation will be as responsive as before.
http://gentoo-wiki.com/Portage_Niceness

'''FEATURES'''
Portage has several additional features that makes your Gentoo experience even better. Many of these features rely on certain software tools that improve performance, reliability, security, ...
Parallel fetch:
When you are emerging a series of packages, Portage can fetch the source files for the next package in the list even while it is compiling another package, thus shortening compile times..
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=3

'''CONFIG_PROTECT'''
This variable contains a space-delimited list of directories which should be protected by Portage during updates.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=5

'''VIDEO_CARDS'''
I see people's make.conf often and in the default make.conf there is like 20 video cards listed. Why compile more than you have too? Get rid of all the cards not in your computer.
http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml

'''INPUT_DEVICES'''
The same goes here, get rid of any equipment you don't have. My desktop doesn't have touchpad - why compile it?
http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml

'''LIRC_DEVICES'''
Linux Infrared Remote Control - this is where you are going to set your devices
http://gentoo-wiki.com/HOWTO_LIRC

'''source /usr/portage/local/layman/make.conf''' -- location for your layman, for managing your overlays such as sabayon, xeffects, etc....

Extras that I have added, just for my own use. You will not see these in a default make.conf
------------------------------------------------------------------------------------------------------------------------

'''PORTAGE_ELOG_CLASSES'''
Ebuild Logging -
Portage can create per-ebuild logfiles, but only when the PORT_LOGDIR variable is set to a location that is writable by Portage (the portage user). By default this variable is unset. If you don't set PORT_LOGDIR, then you won't receive any build logs with the current logging system, though you may receive some logs from the new elog. If you do have PORT_LOGDIR defined and you use elog, you will receive build logs and any logs saved by elog, as explained below.

Portage offers fine-grained control over logging through the use of elog:

* '''PORTAGE_ELOG_CLASSES:''' This is where you set what kinds of messages to be logged. You can use any space-separated combination of info, warn, error, log, and qa.
o info: Logs "einfo" messages printed by an ebuild
o warn: Logs "ewarn" messages printed by an ebuild
o error: Logs "eerror" messages printed by an ebuild
o log: Logs the "elog" messages found in some ebuilds
o qa: Logs the "QA Notice" messages printed by an ebuild
'''PORTAGE_ELOG_SYSTEM:''' This selects the module(s) to process the log messages. If left empty, logging is disabled. You can use any space-separated combination of save, custom, syslog, mail, save_summary, and mail_summary. You must select at least one module in order to use elog.
* save: This saves one log per package in $PORT_LOGDIR/elog, or /var/log/portage/elog if $PORT_LOGDIR is not defined.
* custom: Passes all messages to a user-defined command in $PORTAGE_ELOG_COMMAND; this will be discussed later.
* syslog: Sends all messages to the installed system logger.
* mail: Passes all messages to a user-defined mailserver in $PORTAGE_ELOG_MAILURI; this will be discussed later. The mail features of elog require >=portage-2.1.1.
* save_summary: Similar to save, but it merges all messages in $PORT_LOGDIR/elog/summary.log, or /var/log/portage/elog/summary.log if $PORT_LOGDIR is not defined.
* mail_summary: Similar to mail, but it sends all messages in a single mail when emerge exits.
http://www.gentoo.org/doc/en/handbook/h ... t=3&chap=1
**portage-2.1.3: "echo" - this prints all logged messages again at the end of the emerge

'''FEATURES="buildpkg"''' for building your own binary packages and saving them
http://gentoo-wiki.com/HOWTO_setup_a_PO ... OST_server
http://www.gentoo.org/proj/en/base/amd64/emul/index.xml

source /usr/portage/local/layman/make.conf -- location for your layman, for managing your overlays such as sabayon, xeffects, etc....

'''EMERGE_DEFAULT_OPTS="--with-bdeps y"''' # considers also build-time deps at dependency calculations
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=2

'''Man Make.conf'''
http://gentoo-wiki.com/MAN_makeconf

Do you see now why it is important to know this file? This file can make your gentoo based distro a much better experience. The gentoo handbook can help you set it up properly. Remember to take full advantage of changes, you need to be using certain flags like emerge --newuse foo. Recompiling your entire sytem and world is what you need to do to take advantage of your changes. Like for me I simple run emerge -uDN --world - that will update and make sure all packages are following my settings. If I changed a USE flag it will rebuild the packages effected and update packages to latest in portage.

Recompiling your system is not going to be easy if you are new to all of this. I recommend getting to know portage and how to work with portage before attempting it. It's something you just don't jump into. Your going to run into all sorts of issues and gonna have to search and find your answers. As of 3.4 you are gonna run into a python update, which requires taking care of first as things will break and need to get updated to the new python. Pending on your system - it can take several days to complete the process.
Learn your world file and cleaning it out before starting, this will save many hours of recompiling packages you don't need. The world file is a record of packages which have been specifically installed by the user. More specifically it's a list of packages which the user wants to keep installed and updated on their system. It will not record the dependencies of those packages, but instead uses the dependencies of the currently installed packages to keep track of this information. http://gentoo-wiki.com/HOWTO_Use_Portage_Correctly

You will also want to get yourself familiar with the files in your /etc/portage/ you will need to use them to mask and unmask needed packages. Also use em for telling how certain packages should be built.

Read thru the unofficial guide for a world update
viewtopic.php?f=54&t=5531

Best advice - Use the operating system till you know it, than start diving into the depths of the internal stuff. I know it is frustrating for people that are new, but if you give it time and stick with it, it will all come together. If all this information totally terrifies you, than stick with the default settings. Use the information for you knowledge. Topic is open for discussion.

[http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578 Forum Discussion]

==Config Files - An Introduction==

Without config files the operating sytem would be blah. Are you finding yourself confused with all the messages of portage telling you:
IMPORTANT: 124 config files in '/usr/share/X11/xkb' need updating

Well unfortunately with the amount of config files on your computer it is impossible to go over them all. I'm going to try and hit on the more important ones that are used more frequently.

Do you have to update your config files? The answer will be yes. Why? Cause things change over time.

How do I update my config files, portage keeps telling me I have config files to update? Well there is several ways to do this, you will need to run one of the following more popular methods.:
--------etc-update: http://www.gentoo-wiki.info/HOWTO_etc-update
--------dispatch-conf: http://www.gentoo-wiki.info/TIP_dispatch-conf

Do not and I repeat, do not blindly auto merge config file updates. You can hose your system to the point it won't boot back up. Well there is so many, how do I know if it is safe to or not? Good question and the rule of thumb is - if you have not edited a config file than generally your are safe, but this isn't a sure fire way. Using dispatch-conf will keep a back up copy of you old config files in case you need to restore them. Get to know your config files so you can be aware of certain files.

Remember to edit the config files you need to be root, so you will want to open konsole, type su, enter password and than nano or vi the file. You can do this via GUI too, just open konsole and run kdesu konqueror and when the box comes up, enter you root password and than you will have a root file manager window, gnome users will use gksu nautilus.

'''/etc/rc.conf''' - for general, system-wide configuration. Read the comments in the file, it's pretty well explained. If your window manager suddenly changes upon boot, this is one of the first files to check.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/conf.d/xdm''' - Is what controls your GUI login and window Manager. So if you GUI or login is messed up, be sure to check it out. It's self explanatory.
http://www.gentoo-wiki.info/HOWTO_Activate_Graphical_login

'''/etc/hosts''' - helps in resolving host names to IP addresses for hosts that aren't resolved by your nameserver.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/make.conf''' - This file contains various variables that are used by Portage. Portage will check the currently-defined environment variables first for any settings.
http://www.gentoo-wiki.info/MAN_makeconf
http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578

'''/boot/grub/grub.conf''' - Your boot manager so you can boot 1 or more operating systems. This is one of the first screens you will see and is asking for you to choose what operating system to boot.
http://www.gentoo-wiki.info/HOWTO_Quick_GRUB
http://www.gentoo-wiki.info/HOWTO_Dual_boot

'''/etx/X11/xorg.conf''' - Xorg is the X Window server which allows users to have a graphical environment. Got resolution problems? This file is for you.
http://www.gentoo.org/doc/en/xorg-config.xml

'''/etc/conf.d/net''' - your network configuration, see /etc/conf.d/net.example for a very well documented example â€“ dhcp, static, wireless, wired networking settings
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/resolv.conf''' - your DNS file, nothing to complicated, but if you can access your router but can't get web pages to load - check this file for DNS settings
http://www.gentoo.org/doc/en/home-router-howto.xml

'''/etc/fstab''' - This file contains the mount points of your partitions. Need to mount a hard drive? Add it here so it is available on every boot up.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/modules.autoload.d/kernel-2.6''' - You may have decided to compile some kernel components as modules (as opposed to compiled directly into the kernel) and would like to have them autoloaded on bootup like you did with 2.4. Also, if you installed any external modules from the portage tree you will probably want to autoload them too.
http://www.gentoo.org/doc/en/migration-to-2.6.xml

'''/etc/exports''' This is great for doing shares on the network using NFS
http://www.gentoo-wiki.info/HOWTO_Share_Directories_via_NFS
This also works great of sharing portage across multiple computers. You only need to sync one main computer than share your portage so the other computers will connect to your main computer for emerges
http://www.gentoo-wiki.info/HOWTO_Using_a_shared_portage_via_NFS

This hardly puts a dent in the amount of config files, but those are the ones I run across the most, plus trying to keep it friendly for people new to config files. I could of mentioned like local.start, but that is for experienced people.

Generally you can google and find some thing about the config file. Enter into google "gentoo xorg.conf" and you will find your answer. Feel free to add more that I may have missed here.

[http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10863 Forum Discussion]

HOWTO: Unoffical Guide To World Update

2013-02-23T14:06:18Z

Aposteeltje: /* Updating */

{{Warning| '''Portage (emerge) is not the primary package manager for Sabayon, this article is for advanced users only. In other words if this fails for you, its your fault. You have been warned.'''}}
=World Update and Understanding Configs=

==Updating==

First let me say that there is a several ways to doing things on SL. I am not saying that my way is the best way by any means. This is simply my way of how I do things with a fresh install to make a stable system. You should probably read the other articles below first to better understand things.

First thing - I alway buy my hardware that I know is linux supported and has good drivers. So get to know your hardware, I can't say that enough as it will save you a lot of headaches.

'''DO NOTE''' - I can not tell you what you can safely remove from your system as you need to know your hardware and what is safe to uninstall, remove from config files and remove from kernel. I am going to try and stay very basic here so you can get the idea.

Fresh install and everything is working great so now what?

----
Well I head to the /etc/make.conf file and edit that thing to my liking and double checking things over. I remove any unnecessary things. Remember to edit these files you must be root. If you like nano you can simple go into Konsole and punch in su than enter your password. You can edit the file by doing

{{Console| <pre class="clear"># nano -w /etc/make.conf</pre>}}

or if you simply must have a GUI you can go to konsole and enter

{{Console| <pre class="clear">$ kdesu konqueror</pre>}}

and when the box pops up, enter your password, wait a bit and a new window will come up. In that window you are root to everything and can edit anything. Pretty simple so far right? If you need help figuring out what options are available in the [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578 make.conf] then refer to the Gentoo Handbook and Wiki often.

----
Ok, so now that I got that set I like to head to the kernel and add to it and remove things I don't need by doing in konsole:

{{Console| <pre class="clear"># zcat /proc/config.gz > /usr/src/config

# genkernel --kernel-config=/usr/src/config --menuconfig --bootloader=grub --gensplash=sabayon all --luks</pre>}}

'''or if you use lvm do:''' - noted for waltercool

# genkernel --kernel-config=/usr/src/config --menuconfig --bootloader=grub --gensplash=sabayon --lvm2 all --luks

''note the # means you must be root, don't actually use the #''

This step is not necessary if you don't care that your kernel is big. I always need to enable some sound stuff and you may need to enable drivers, again, this is where knowing where your hardware is very important. You remove the wrong thing and your puter will not boot. Skip this step if you have a funny look on your face at this time.

----
NOTE: Before doing the following 'emerge -e' commands, you may want to customize your CFLAGS in make.conf so that it is optimized for your CPU type. The following two commands take very a long time, so it's worth it to optimize while you are taking the time to do this. Please refer to [http://en.gentoo-wiki.com/wiki/Safe_Cflags Gentoo Safe CFLAGS Guide] for the correct setting for your specific CPU. Do not change your CHOST as described in that guide, changing CHOST is dangerous and not recommended. See [http://gentoo-wiki.com/HOWTO_change_CHOST_relatively_safely this HOWTO] if you wish to risk changing your CHOST.

Now some of you may totally think I am crazy here but as far as software removal I do that later. Yes I know I can remove software at this time that I will never use and save time when I recompile the system, but this is my unofficial stable system and I know it will work cause I have done it several times. So with that being said I want to now recompile just the system. Now I prefer to do :

# emerge -e system || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

Notice I have not done an emerge --sync yet and I don't want to do that yet, that will come later. So now several hours are going to go by. This a great thing to do when you are about to go to bed. After that is done, I like to do the world recompile:

# emerge -e world || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

do note once again that I have not used emerge --sync yet and this is going to be another lengthy process. You may do both commands at once by simply doing:

# emerge -e system || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done && emerge -e world || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

I just like to break it up.

----
So now I have finished recompiling everything and my processor is going Dude! Well now I punch in:

# emerge --sync && layman -S

to update my portage tree and overlays. First time syncs on SL are slow, I promise they will get faster after the first time. Once that is done I punch in:

# emerge -upDN world

this will pull up just under 400 packages, WOW!! Well lets get the show on the road.

# emerge -uN world

Now you look at that and go what happened to the D ?, again this is my guide and that will come later. Now you are probably sitting there thinking I thought SL doesn't recommend a world update. My feelings are this: no you don't need to, but SL 3.3 makes it a piece of cake to world update. Pre 3.3 I don't recommend, as you will be forever swamped with recompiling. Now with the world update you are going to run into bumps and this is where reading the ERROR MESSAGES is going to come to be Very Important. If you listen to what portage is telling you and use the Gentoo bugzilla and Gentoo forums for searching you can usually find the solution. Once a package fails I simply:

# emerge --resume --skipfirst

to continue on. I like to do this method to see what packages are failing. If you don't care:

# emerge -uN world || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

then it will auto skip and keep on going till finished. Now I don't try and fix any packages till it is completely done. Once it is done I look look at

#emerge -upN world

and go through each package and install it with the fix needed to get it to install. At this time I will simple remove any packages that have failed that I know I don't need. So now we are done and

# emerge -upN world

shows no packages left in it, time I fire up

# emerge -upDN world

YAY more packages to compile! The amount of packages won't be that much. So we wait for that to finish and I usually fix the errors as it goes along since it isn't very many packages. Now we have the entire system rebuilt, well almost. It's time to run:

# revdep-rebuild

and if that fails do:

# revdep-rebuild

It will find more packages to recompile! Your processor is probably plotting some sort of revenge against you at this time. So now what? Well, you are gonna have some config files that are screaming for an update. Now I like to use:

# etc-update

There is several ways to update config files, this is my way of doing it. So I punch in etc-update and many will auto merge, which is great with me. I look over the remaining ones left and determine if they are safe or not to update. Off the top of my head I believe all changes in 3.3 are safe, but look and if you are unsure, don't do it. So we have recompiled everything after making changes to system, updated the config files. Are we done? Do we dare reboot? Let's live dangerously and reboot, I mean a reinstall is only 40 minutes to do anyway right?

----
So we rebooted, prayed and we made it back to our Desktop!! So now, I like all the multimedia features the web has to offer, so I want to experience it all, so I open up my konsole again and punch in:

USE="divx gmedia gtk nls quicktime realmedia wmp" emerge mplayerplug-in

Yes, I know you can add this to your package.use file, but this is my guide and you should add it to your /etc/portage/package.use file for future use. Now I can sit back and view all the goodness of web multimedia! I hate totem handling the web plugins cause it sucks at doing so. I don't uninstall totem I simply move all the totem plugins out of the plugins folder:
/usr/lib/nsbrowser/plugins
and put em in
/usr/lib/nsbrowser
Just in case I ever want to put them back.

Alrighty then, we are world updated now. You can continue to stay world update and SL updated with the overlay by:

# emerge --sync && layman -S && emerge -uDN world

A handy automated script for this can be found here:
[http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=11870 Update Script]

----
Conclusion - my systems are rock solid no matter what I throw at them. It's a long process, but that's fine with me cause the results are worth it. Do keep in mind that it will take less time with the mini as there is less to deal with. It will require thinking and deciphering and good abilities of effective searching. No I can not help you world update your system as I have no idea what hardware you use or what you use your computer for. Is there a chance you may hose your system? Of course there is! It shouldn't happen if you pay attention. I can't stress enough to read the [http://www.gentoo.org/doc/en/handbook/index.xml Gentoo Handbook], look at the [http://gentoo-wiki.com Gentoo Wiki], look at the [http://forums.gentoo.org/ Gentoo Forum], look at the [http://wiki.sabayonlinux.org SL Wiki], look at the [http://www.sabayonlinux.org/forum SL Forum] and don't forget [http://google.com Google], bookmark them all!

That's it in a nutshell and I take NO and I mean NO Responsibilities for a hosed system. Your millage is going to vary of course depending on what hardware and software you use.

Input is welcome and I will answer questions if I know the answers.

HAPPY COMPILING!

[http://www.sabayonlinux.org/forum/viewtopic.php?t=5531 Forum Discussion]

==Understanding make.conf - An Introduction==
{{File|/etc/make.conf|<pre class="clear">
# These settings were set by the catalyst build script that automatically built this stage
# Please consult /etc/make.conf.example for a more detailed example
CFLAGS="-O3 -march=native -funroll-all-loops -m3dnow -msse3 -funit-at-a-time -fpeel-loops -ftracer -funswitch-loops -fomit-frame-pointer -pipe"
LDFLAGS="-Wl,-O1 -Wl,--enable-new-dtags -Wl,--sort-common -s"
CHOST="i586-pc-linux-gnu"
USE="win32codecs mp3 quicktime type1 divx4linux dvb dvd dvdread live mpeg nvidia jpeg truetype v4l v4l2 xv xvid multilib gnutls arts cups ppds foomatic-db \
alsa gimpprint freetype gnome X gtk gtk2 unicode moznocompose moznoirc moznomail kde qt samba xinerama xine theora kdeenablefinal wifi hal ieee1394 \
oggvorbis lm_sensors logitech-mouse zeroconf artswrappersuid nptl nptlonly rdesktop dvdr css gphoto2 openexr speex jpeg2k povray scanner musicbrainz \
accessibility audiofile exif xscreensaver ffmpeg vcd sndfile musepack asterisk mbrola pam_chroot pam_timestamp pwdb pda sms irda kig-scripting speedo \
browserplugin nsplugin ldap kerberos firefox dga aac dts xvmc dbus hal dvi on-the-fly-crypt dri xprint acpi ada ruby perforce cjk fat hfs jfs ntfs reiser4 \
xfs reiserfs skins cdda real shout stream a52 wxwindows vlm lirc libcaca remote stats lcd unichrome 7zip commercial mozsvg canvas xml2 glut java glitz svg \
avahi ogg vorbis aalib flac gdbm mikmod timidity kdgraphics dlloader exscalibar ipod visualization mono cdr nntp cairo djvu nautilus evo ole pdf xml ladspa \
soundtouch bzip2 udev mad fuse rtsp tiff kdehiddenvisibility dvi usb kipi aiglx musicbrainz pulseaudio dv lame mp3rtp udev cdr dvi djvu libnotify bzip2 aalib \
startup-notification nsplugin jingle gsm dbox2 opengl sdl png gif qt3 qt4 qt3support apache2 mysql php ssl xml berkdb innobd pcre"
CXXFLAGS="${CFLAGS}"
ACCEPT_KEYWORDS="~x86"
LINGUAS="en"
MAKEOPTS="-s -j3"
PORTAGE_NICENESS="8"
FEATURES="parallel-fetch"
CONFIG_PROTECT="/usr/kde/3.5/share/config/kdm/ /etc"
VIDEO_CARDS="vesa vga nvidia"
INPUT_DEVICES="evdev keyboard mouse"
LIRC_DEVICES="audio audio_alsa"
PORTAGE_ELOG_CLASSES="warn error log info"
PORTAGE_ELOG_SYSTEM="save"
# FEATURES="buildpkg"
source /usr/portage/local/layman/make.conf
EMERGE_DEFAULT_OPTS="--with-bdeps y"
</pre>}}

Above you will find a make.conf and is a vital component to your operating system. If you don't know this file you are defeating the purpose of this distro. One of the biggest things about gentoo based is being able to build the operating sytem to you. Using the default settings are going to work, but you are not taking full advantage of your potentials. You can ease our portage frustration also, like compiling issues.

Why do we need make.conf?
Portage uses this file to know how to build your entire system. All the settings you put here, portage reads and builds to them.

'''CFLAGS'''
CFLAGS are C compiler flags, usually GCC (GNU Compiler Collection) options.
CFLAGS are commonly used to specify the architecture of your computer, as well as the CPU you are using and any other special options you would like to enable or disable. This information is important to GCC because it tells it exactly how to customize the assembly instructions it creates from the application's source code.
http://gentoo-wiki.com/CFLAGS

'''LDFLAGS'''
Deals with your hash tables and compiler See for more information:
http://gentoo-wiki.com/TIP_Safe_LDFLAGS
http://lwn.net/Articles/192624/
Your not going to be touching these, so moving right along.

'''CHOST'''
Variable declares the target build host for your system You don't want to change this value unless you know what you are doing. You simply can't change it to i686 and go about using your computer. There is situations that may cause you to have to change this. For instance, lets say you upgrade your cpu or need a certain package that won't work with your current architect. Gentoo has a guide for changing it. Follow it closely or you will have a hosed system.
http://www.gentoo.org/doc/en/change-chost.xml

'''CXXFLAGS'''
CXXFLAGS is set to use all the options present in CFLAGS. This is what you'll want almost without fail. You shouldn't ever need to specify additional options in CXXFLAGS.
http://www.gentoo.org/doc/en/gcc-optimization.xml

'''USE'''
In Gentoo a USE flag is a representation of an option, a global setting for your final system. USE flags affect how many of the packages on your system will build. These depend on the software and your computer usage. It's important to know these and to thin the list down to your usage. You will see that I have a lot in mine, but that is because of testing I do for SL. All these USE settings are global, meaning they effect every package on your system. The more USE settings you have, the more conflicts you can encounter with portage when compiling software. There is a /etc/portage/package.use file that you can use to individually tell packages how you want them built.
http://gentoo-portage.com/USE
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=2

'''ACCEPT_KEYWORDS="~x86"'''
This is for setting which branch of portage you want to use. Stable vs. Unstable "bleeding edge". You can see by the ~ we are not using the stable branch so we are bleeding edge.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=3

'''LINGUAS'''
I hope this is self explanatory, but if not - your language
http://www.gentoo.org/doc/en/guide-localization.xml

'''MAKEOPTS'''
You define how many parallel compilations should occur when you install a package. A good choice is the number of CPUs in your system plus one, but this guideline isn't always perfect.
http://gentoo-wiki.com/Safe_Cflags
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=5

'''PORTAGE_NICENESS'''
If you keep using your computer while compiling packages you will notice that your box is less responsive than usual. This is caused by having two "groups" of processes with the same nice priority: your usual running processes, and emerge (and its child processes). Now, if you could renice emerge and its children to a higher nice value (i.e. lower priority), compiling would take somewhat longer, but your workstation will be as responsive as before.
http://gentoo-wiki.com/Portage_Niceness

'''FEATURES'''
Portage has several additional features that makes your Gentoo experience even better. Many of these features rely on certain software tools that improve performance, reliability, security, ...
Parallel fetch:
When you are emerging a series of packages, Portage can fetch the source files for the next package in the list even while it is compiling another package, thus shortening compile times..
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=3

'''CONFIG_PROTECT'''
This variable contains a space-delimited list of directories which should be protected by Portage during updates.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=5

'''VIDEO_CARDS'''
I see people's make.conf often and in the default make.conf there is like 20 video cards listed. Why compile more than you have too? Get rid of all the cards not in your computer.
http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml

'''INPUT_DEVICES'''
The same goes here, get rid of any equipment you don't have. My desktop doesn't have touchpad - why compile it?
http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml

'''LIRC_DEVICES'''
Linux Infrared Remote Control - this is where you are going to set your devices
http://gentoo-wiki.com/HOWTO_LIRC

'''source /usr/portage/local/layman/make.conf''' -- location for your layman, for managing your overlays such as sabayon, xeffects, etc....

Extras that I have added, just for my own use. You will not see these in a default make.conf
------------------------------------------------------------------------------------------------------------------------

'''PORTAGE_ELOG_CLASSES'''
Ebuild Logging -
Portage can create per-ebuild logfiles, but only when the PORT_LOGDIR variable is set to a location that is writable by Portage (the portage user). By default this variable is unset. If you don't set PORT_LOGDIR, then you won't receive any build logs with the current logging system, though you may receive some logs from the new elog. If you do have PORT_LOGDIR defined and you use elog, you will receive build logs and any logs saved by elog, as explained below.

Portage offers fine-grained control over logging through the use of elog:

* '''PORTAGE_ELOG_CLASSES:''' This is where you set what kinds of messages to be logged. You can use any space-separated combination of info, warn, error, log, and qa.
o info: Logs "einfo" messages printed by an ebuild
o warn: Logs "ewarn" messages printed by an ebuild
o error: Logs "eerror" messages printed by an ebuild
o log: Logs the "elog" messages found in some ebuilds
o qa: Logs the "QA Notice" messages printed by an ebuild
'''PORTAGE_ELOG_SYSTEM:''' This selects the module(s) to process the log messages. If left empty, logging is disabled. You can use any space-separated combination of save, custom, syslog, mail, save_summary, and mail_summary. You must select at least one module in order to use elog.
* save: This saves one log per package in $PORT_LOGDIR/elog, or /var/log/portage/elog if $PORT_LOGDIR is not defined.
* custom: Passes all messages to a user-defined command in $PORTAGE_ELOG_COMMAND; this will be discussed later.
* syslog: Sends all messages to the installed system logger.
* mail: Passes all messages to a user-defined mailserver in $PORTAGE_ELOG_MAILURI; this will be discussed later. The mail features of elog require >=portage-2.1.1.
* save_summary: Similar to save, but it merges all messages in $PORT_LOGDIR/elog/summary.log, or /var/log/portage/elog/summary.log if $PORT_LOGDIR is not defined.
* mail_summary: Similar to mail, but it sends all messages in a single mail when emerge exits.
http://www.gentoo.org/doc/en/handbook/h ... t=3&chap=1
**portage-2.1.3: "echo" - this prints all logged messages again at the end of the emerge

'''FEATURES="buildpkg"''' for building your own binary packages and saving them
http://gentoo-wiki.com/HOWTO_setup_a_PO ... OST_server
http://www.gentoo.org/proj/en/base/amd64/emul/index.xml

source /usr/portage/local/layman/make.conf -- location for your layman, for managing your overlays such as sabayon, xeffects, etc....

'''EMERGE_DEFAULT_OPTS="--with-bdeps y"''' # considers also build-time deps at dependency calculations
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=2

'''Man Make.conf'''
http://gentoo-wiki.com/MAN_makeconf

Do you see now why it is important to know this file? This file can make your gentoo based distro a much better experience. The gentoo handbook can help you set it up properly. Remember to take full advantage of changes, you need to be using certain flags like emerge --newuse foo. Recompiling your entire sytem and world is what you need to do to take advantage of your changes. Like for me I simple run emerge -uDN --world - that will update and make sure all packages are following my settings. If I changed a USE flag it will rebuild the packages effected and update packages to latest in portage.

Recompiling your system is not going to be easy if you are new to all of this. I recommend getting to know portage and how to work with portage before attempting it. It's something you just don't jump into. Your going to run into all sorts of issues and gonna have to search and find your answers. As of 3.4 you are gonna run into a python update, which requires taking care of first as things will break and need to get updated to the new python. Pending on your system - it can take several days to complete the process.
Learn your world file and cleaning it out before starting, this will save many hours of recompiling packages you don't need. The world file is a record of packages which have been specifically installed by the user. More specifically it's a list of packages which the user wants to keep installed and updated on their system. It will not record the dependencies of those packages, but instead uses the dependencies of the currently installed packages to keep track of this information. http://gentoo-wiki.com/HOWTO_Use_Portage_Correctly

You will also want to get yourself familiar with the files in your /etc/portage/ you will need to use them to mask and unmask needed packages. Also use em for telling how certain packages should be built.

Read thru the unofficial guide for a world update
viewtopic.php?f=54&t=5531

Best advice - Use the operating system till you know it, than start diving into the depths of the internal stuff. I know it is frustrating for people that are new, but if you give it time and stick with it, it will all come together. If all this information totally terrifies you, than stick with the default settings. Use the information for you knowledge. Topic is open for discussion.

[http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578 Forum Discussion]

==Config Files - An Introduction==

Without config files the operating sytem would be blah. Are you finding yourself confused with all the messages of portage telling you:
IMPORTANT: 124 config files in '/usr/share/X11/xkb' need updating

Well unfortunately with the amount of config files on your computer it is impossible to go over them all. I'm going to try and hit on the more important ones that are used more frequently.

Do you have to update your config files? The answer will be yes. Why? Cause things change over time.

How do I update my config files, portage keeps telling me I have config files to update? Well there is several ways to do this, you will need to run one of the following more popular methods.:
--------etc-update: http://www.gentoo-wiki.info/HOWTO_etc-update
--------dispatch-conf: http://www.gentoo-wiki.info/TIP_dispatch-conf

Do not and I repeat, do not blindly auto merge config file updates. You can hose your system to the point it won't boot back up. Well there is so many, how do I know if it is safe to or not? Good question and the rule of thumb is - if you have not edited a config file than generally your are safe, but this isn't a sure fire way. Using dispatch-conf will keep a back up copy of you old config files in case you need to restore them. Get to know your config files so you can be aware of certain files.

Remember to edit the config files you need to be root, so you will want to open konsole, type su, enter password and than nano or vi the file. You can do this via GUI too, just open konsole and run kdesu konqueror and when the box comes up, enter you root password and than you will have a root file manager window, gnome users will use gksu nautilus.

'''/etc/rc.conf''' - for general, system-wide configuration. Read the comments in the file, it's pretty well explained. If your window manager suddenly changes upon boot, this is one of the first files to check.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/conf.d/xdm''' - Is what controls your GUI login and window Manager. So if you GUI or login is messed up, be sure to check it out. It's self explanatory.
http://www.gentoo-wiki.info/HOWTO_Activate_Graphical_login

'''/etc/hosts''' - helps in resolving host names to IP addresses for hosts that aren't resolved by your nameserver.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/make.conf''' - This file contains various variables that are used by Portage. Portage will check the currently-defined environment variables first for any settings.
http://www.gentoo-wiki.info/MAN_makeconf
http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578

'''/boot/grub/grub.conf''' - Your boot manager so you can boot 1 or more operating systems. This is one of the first screens you will see and is asking for you to choose what operating system to boot.
http://www.gentoo-wiki.info/HOWTO_Quick_GRUB
http://www.gentoo-wiki.info/HOWTO_Dual_boot

'''/etx/X11/xorg.conf''' - Xorg is the X Window server which allows users to have a graphical environment. Got resolution problems? This file is for you.
http://www.gentoo.org/doc/en/xorg-config.xml

'''/etc/conf.d/net''' - your network configuration, see /etc/conf.d/net.example for a very well documented example â€“ dhcp, static, wireless, wired networking settings
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/resolv.conf''' - your DNS file, nothing to complicated, but if you can access your router but can't get web pages to load - check this file for DNS settings
http://www.gentoo.org/doc/en/home-router-howto.xml

'''/etc/fstab''' - This file contains the mount points of your partitions. Need to mount a hard drive? Add it here so it is available on every boot up.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/modules.autoload.d/kernel-2.6''' - You may have decided to compile some kernel components as modules (as opposed to compiled directly into the kernel) and would like to have them autoloaded on bootup like you did with 2.4. Also, if you installed any external modules from the portage tree you will probably want to autoload them too.
http://www.gentoo.org/doc/en/migration-to-2.6.xml

'''/etc/exports''' This is great for doing shares on the network using NFS
http://www.gentoo-wiki.info/HOWTO_Share_Directories_via_NFS
This also works great of sharing portage across multiple computers. You only need to sync one main computer than share your portage so the other computers will connect to your main computer for emerges
http://www.gentoo-wiki.info/HOWTO_Using_a_shared_portage_via_NFS

This hardly puts a dent in the amount of config files, but those are the ones I run across the most, plus trying to keep it friendly for people new to config files. I could of mentioned like local.start, but that is for experienced people.

Generally you can google and find some thing about the config file. Enter into google "gentoo xorg.conf" and you will find your answer. Feel free to add more that I may have missed here.

[http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10863 Forum Discussion]

HOWTO: Unoffical Guide To World Update

2013-02-23T14:04:47Z

Aposteeltje: /* Updating */

{{Warning| '''Portage (emerge) is not the primary package manager for Sabayon, this article is for advanced users only. In other words if this fails for you, its your fault. You have been warned.'''}}
=World Update and Understanding Configs=

==Updating==

First let me say that there is a several ways to doing things on SL. I am not saying that my way is the best way by any means. This is simply my way of how I do things with a fresh install to make a stable system. You should probably read the other articles below first to better understand things.

First thing - I alway buy my hardware that I know is linux supported and has good drivers. So get to know your hardware, I can't say that enough as it will save you a lot of headaches.

'''DO NOTE''' - I can not tell you what you can safely remove from your system as you need to know your hardware and what is safe to uninstall, remove from config files and remove from kernel. I am going to try and stay very basic here so you can get the idea.

Fresh install and everything is working great so now what?

----
Well I head to the /etc/make.conf file and edit that thing to my liking and double checking things over. I remove any unnecessary things. Remember to edit these files you must be root. If you like nano you can simple go into Konsole and punch in su than enter your password. You can edit the file by doing

{{Console| <pre class="clear"># nano -w /etc/make.conf</pre>}}

or if you simply must have a GUI you can go to konsole and enter

{{Console| <pre class="clear">$ kdesu konqueror</pre>}}

and when the box pops up, enter your password, wait a bit and a new window will come up. In that window you are root to everything and can edit anything. Pretty simple so far right? If you need help figuring out what options are available in the [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578 make.conf] then refer to the Gentoo Handbook and Wiki often.

----
Ok, so now that I got that set I like to head to the kernel and add to it and remove things I don't need by doing in konsole:

{{Console| <pre class="clear"># zcat /proc/config.gz > /usr/src/config

# genkernel --kernel-config=/usr/src/config --menuconfig --bootloader=grub --gensplash=sabayon all --luks</pre>}}

'''or if you use lvm do:''' - noted for waltercool

# genkernel --kernel-config=/usr/src/config --menuconfig --bootloader=grub --gensplash=sabayon --lvm2 all --luks

''note the # means you must be root, don't actually use the #''

This step is not necessary if you don't care that your kernel is big. I always need to enable some sound stuff and you may need to enable drivers, again, this is where knowing where your hardware is very important. You remove the wrong thing and your puter will not boot. Skip this step if you have a funny look on your face at this time.

----
NOTE: Before doing the following 'emerge -e' commands, you may want to customize your CFLAGS in make.conf so that it is optimized for your CPU type. The following two commands take very a long time, so it's worth it to optimize while you are taking the time to do this. Please refer to [http://http://en.gentoo-wiki.com/wiki/Safe_Cflags Gentoo Safe CFLAGS Guide] for the correct setting for your specific CPU. Do not change your CHOST as described in that guide, changing CHOST is dangerous and not recommended. See [http://gentoo-wiki.com/HOWTO_change_CHOST_relatively_safely this HOWTO] if you wish to risk changing your CHOST.

Now some of you may totally think I am crazy here but as far as software removal I do that later. Yes I know I can remove software at this time that I will never use and save time when I recompile the system, but this is my unofficial stable system and I know it will work cause I have done it several times. So with that being said I want to now recompile just the system. Now I prefer to do :

# emerge -e system || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

Notice I have not done an emerge --sync yet and I don't want to do that yet, that will come later. So now several hours are going to go by. This a great thing to do when you are about to go to bed. After that is done, I like to do the world recompile:

# emerge -e world || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

do note once again that I have not used emerge --sync yet and this is going to be another lengthy process. You may do both commands at once by simply doing:

# emerge -e system || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done && emerge -e world || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

I just like to break it up.

----
So now I have finished recompiling everything and my processor is going Dude! Well now I punch in:

# emerge --sync && layman -S

to update my portage tree and overlays. First time syncs on SL are slow, I promise they will get faster after the first time. Once that is done I punch in:

# emerge -upDN world

this will pull up just under 400 packages, WOW!! Well lets get the show on the road.

# emerge -uN world

Now you look at that and go what happened to the D ?, again this is my guide and that will come later. Now you are probably sitting there thinking I thought SL doesn't recommend a world update. My feelings are this: no you don't need to, but SL 3.3 makes it a piece of cake to world update. Pre 3.3 I don't recommend, as you will be forever swamped with recompiling. Now with the world update you are going to run into bumps and this is where reading the ERROR MESSAGES is going to come to be Very Important. If you listen to what portage is telling you and use the Gentoo bugzilla and Gentoo forums for searching you can usually find the solution. Once a package fails I simply:

# emerge --resume --skipfirst

to continue on. I like to do this method to see what packages are failing. If you don't care:

# emerge -uN world || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

then it will auto skip and keep on going till finished. Now I don't try and fix any packages till it is completely done. Once it is done I look look at

#emerge -upN world

and go through each package and install it with the fix needed to get it to install. At this time I will simple remove any packages that have failed that I know I don't need. So now we are done and

# emerge -upN world

shows no packages left in it, time I fire up

# emerge -upDN world

YAY more packages to compile! The amount of packages won't be that much. So we wait for that to finish and I usually fix the errors as it goes along since it isn't very many packages. Now we have the entire system rebuilt, well almost. It's time to run:

# revdep-rebuild

and if that fails do:

# revdep-rebuild

It will find more packages to recompile! Your processor is probably plotting some sort of revenge against you at this time. So now what? Well, you are gonna have some config files that are screaming for an update. Now I like to use:

# etc-update

There is several ways to update config files, this is my way of doing it. So I punch in etc-update and many will auto merge, which is great with me. I look over the remaining ones left and determine if they are safe or not to update. Off the top of my head I believe all changes in 3.3 are safe, but look and if you are unsure, don't do it. So we have recompiled everything after making changes to system, updated the config files. Are we done? Do we dare reboot? Let's live dangerously and reboot, I mean a reinstall is only 40 minutes to do anyway right?

----
So we rebooted, prayed and we made it back to our Desktop!! So now, I like all the multimedia features the web has to offer, so I want to experience it all, so I open up my konsole again and punch in:

USE="divx gmedia gtk nls quicktime realmedia wmp" emerge mplayerplug-in

Yes, I know you can add this to your package.use file, but this is my guide and you should add it to your /etc/portage/package.use file for future use. Now I can sit back and view all the goodness of web multimedia! I hate totem handling the web plugins cause it sucks at doing so. I don't uninstall totem I simply move all the totem plugins out of the plugins folder:
/usr/lib/nsbrowser/plugins
and put em in
/usr/lib/nsbrowser
Just in case I ever want to put them back.

Alrighty then, we are world updated now. You can continue to stay world update and SL updated with the overlay by:

# emerge --sync && layman -S && emerge -uDN world

A handy automated script for this can be found here:
[http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=11870 Update Script]

----
Conclusion - my systems are rock solid no matter what I throw at them. It's a long process, but that's fine with me cause the results are worth it. Do keep in mind that it will take less time with the mini as there is less to deal with. It will require thinking and deciphering and good abilities of effective searching. No I can not help you world update your system as I have no idea what hardware you use or what you use your computer for. Is there a chance you may hose your system? Of course there is! It shouldn't happen if you pay attention. I can't stress enough to read the [http://www.gentoo.org/doc/en/handbook/index.xml Gentoo Handbook], look at the [http://gentoo-wiki.com Gentoo Wiki], look at the [http://forums.gentoo.org/ Gentoo Forum], look at the [http://wiki.sabayonlinux.org SL Wiki], look at the [http://www.sabayonlinux.org/forum SL Forum] and don't forget [http://google.com Google], bookmark them all!

That's it in a nutshell and I take NO and I mean NO Responsibilities for a hosed system. Your millage is going to vary of course depending on what hardware and software you use.

Input is welcome and I will answer questions if I know the answers.

HAPPY COMPILING!

[http://www.sabayonlinux.org/forum/viewtopic.php?t=5531 Forum Discussion]

==Understanding make.conf - An Introduction==
{{File|/etc/make.conf|<pre class="clear">
# These settings were set by the catalyst build script that automatically built this stage
# Please consult /etc/make.conf.example for a more detailed example
CFLAGS="-O3 -march=native -funroll-all-loops -m3dnow -msse3 -funit-at-a-time -fpeel-loops -ftracer -funswitch-loops -fomit-frame-pointer -pipe"
LDFLAGS="-Wl,-O1 -Wl,--enable-new-dtags -Wl,--sort-common -s"
CHOST="i586-pc-linux-gnu"
USE="win32codecs mp3 quicktime type1 divx4linux dvb dvd dvdread live mpeg nvidia jpeg truetype v4l v4l2 xv xvid multilib gnutls arts cups ppds foomatic-db \
alsa gimpprint freetype gnome X gtk gtk2 unicode moznocompose moznoirc moznomail kde qt samba xinerama xine theora kdeenablefinal wifi hal ieee1394 \
oggvorbis lm_sensors logitech-mouse zeroconf artswrappersuid nptl nptlonly rdesktop dvdr css gphoto2 openexr speex jpeg2k povray scanner musicbrainz \
accessibility audiofile exif xscreensaver ffmpeg vcd sndfile musepack asterisk mbrola pam_chroot pam_timestamp pwdb pda sms irda kig-scripting speedo \
browserplugin nsplugin ldap kerberos firefox dga aac dts xvmc dbus hal dvi on-the-fly-crypt dri xprint acpi ada ruby perforce cjk fat hfs jfs ntfs reiser4 \
xfs reiserfs skins cdda real shout stream a52 wxwindows vlm lirc libcaca remote stats lcd unichrome 7zip commercial mozsvg canvas xml2 glut java glitz svg \
avahi ogg vorbis aalib flac gdbm mikmod timidity kdgraphics dlloader exscalibar ipod visualization mono cdr nntp cairo djvu nautilus evo ole pdf xml ladspa \
soundtouch bzip2 udev mad fuse rtsp tiff kdehiddenvisibility dvi usb kipi aiglx musicbrainz pulseaudio dv lame mp3rtp udev cdr dvi djvu libnotify bzip2 aalib \
startup-notification nsplugin jingle gsm dbox2 opengl sdl png gif qt3 qt4 qt3support apache2 mysql php ssl xml berkdb innobd pcre"
CXXFLAGS="${CFLAGS}"
ACCEPT_KEYWORDS="~x86"
LINGUAS="en"
MAKEOPTS="-s -j3"
PORTAGE_NICENESS="8"
FEATURES="parallel-fetch"
CONFIG_PROTECT="/usr/kde/3.5/share/config/kdm/ /etc"
VIDEO_CARDS="vesa vga nvidia"
INPUT_DEVICES="evdev keyboard mouse"
LIRC_DEVICES="audio audio_alsa"
PORTAGE_ELOG_CLASSES="warn error log info"
PORTAGE_ELOG_SYSTEM="save"
# FEATURES="buildpkg"
source /usr/portage/local/layman/make.conf
EMERGE_DEFAULT_OPTS="--with-bdeps y"
</pre>}}

Above you will find a make.conf and is a vital component to your operating system. If you don't know this file you are defeating the purpose of this distro. One of the biggest things about gentoo based is being able to build the operating sytem to you. Using the default settings are going to work, but you are not taking full advantage of your potentials. You can ease our portage frustration also, like compiling issues.

Why do we need make.conf?
Portage uses this file to know how to build your entire system. All the settings you put here, portage reads and builds to them.

'''CFLAGS'''
CFLAGS are C compiler flags, usually GCC (GNU Compiler Collection) options.
CFLAGS are commonly used to specify the architecture of your computer, as well as the CPU you are using and any other special options you would like to enable or disable. This information is important to GCC because it tells it exactly how to customize the assembly instructions it creates from the application's source code.
http://gentoo-wiki.com/CFLAGS

'''LDFLAGS'''
Deals with your hash tables and compiler See for more information:
http://gentoo-wiki.com/TIP_Safe_LDFLAGS
http://lwn.net/Articles/192624/
Your not going to be touching these, so moving right along.

'''CHOST'''
Variable declares the target build host for your system You don't want to change this value unless you know what you are doing. You simply can't change it to i686 and go about using your computer. There is situations that may cause you to have to change this. For instance, lets say you upgrade your cpu or need a certain package that won't work with your current architect. Gentoo has a guide for changing it. Follow it closely or you will have a hosed system.
http://www.gentoo.org/doc/en/change-chost.xml

'''CXXFLAGS'''
CXXFLAGS is set to use all the options present in CFLAGS. This is what you'll want almost without fail. You shouldn't ever need to specify additional options in CXXFLAGS.
http://www.gentoo.org/doc/en/gcc-optimization.xml

'''USE'''
In Gentoo a USE flag is a representation of an option, a global setting for your final system. USE flags affect how many of the packages on your system will build. These depend on the software and your computer usage. It's important to know these and to thin the list down to your usage. You will see that I have a lot in mine, but that is because of testing I do for SL. All these USE settings are global, meaning they effect every package on your system. The more USE settings you have, the more conflicts you can encounter with portage when compiling software. There is a /etc/portage/package.use file that you can use to individually tell packages how you want them built.
http://gentoo-portage.com/USE
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=2

'''ACCEPT_KEYWORDS="~x86"'''
This is for setting which branch of portage you want to use. Stable vs. Unstable "bleeding edge". You can see by the ~ we are not using the stable branch so we are bleeding edge.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=3

'''LINGUAS'''
I hope this is self explanatory, but if not - your language
http://www.gentoo.org/doc/en/guide-localization.xml

'''MAKEOPTS'''
You define how many parallel compilations should occur when you install a package. A good choice is the number of CPUs in your system plus one, but this guideline isn't always perfect.
http://gentoo-wiki.com/Safe_Cflags
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=5

'''PORTAGE_NICENESS'''
If you keep using your computer while compiling packages you will notice that your box is less responsive than usual. This is caused by having two "groups" of processes with the same nice priority: your usual running processes, and emerge (and its child processes). Now, if you could renice emerge and its children to a higher nice value (i.e. lower priority), compiling would take somewhat longer, but your workstation will be as responsive as before.
http://gentoo-wiki.com/Portage_Niceness

'''FEATURES'''
Portage has several additional features that makes your Gentoo experience even better. Many of these features rely on certain software tools that improve performance, reliability, security, ...
Parallel fetch:
When you are emerging a series of packages, Portage can fetch the source files for the next package in the list even while it is compiling another package, thus shortening compile times..
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=3

'''CONFIG_PROTECT'''
This variable contains a space-delimited list of directories which should be protected by Portage during updates.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=5

'''VIDEO_CARDS'''
I see people's make.conf often and in the default make.conf there is like 20 video cards listed. Why compile more than you have too? Get rid of all the cards not in your computer.
http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml

'''INPUT_DEVICES'''
The same goes here, get rid of any equipment you don't have. My desktop doesn't have touchpad - why compile it?
http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml

'''LIRC_DEVICES'''
Linux Infrared Remote Control - this is where you are going to set your devices
http://gentoo-wiki.com/HOWTO_LIRC

'''source /usr/portage/local/layman/make.conf''' -- location for your layman, for managing your overlays such as sabayon, xeffects, etc....

Extras that I have added, just for my own use. You will not see these in a default make.conf
------------------------------------------------------------------------------------------------------------------------

'''PORTAGE_ELOG_CLASSES'''
Ebuild Logging -
Portage can create per-ebuild logfiles, but only when the PORT_LOGDIR variable is set to a location that is writable by Portage (the portage user). By default this variable is unset. If you don't set PORT_LOGDIR, then you won't receive any build logs with the current logging system, though you may receive some logs from the new elog. If you do have PORT_LOGDIR defined and you use elog, you will receive build logs and any logs saved by elog, as explained below.

Portage offers fine-grained control over logging through the use of elog:

* '''PORTAGE_ELOG_CLASSES:''' This is where you set what kinds of messages to be logged. You can use any space-separated combination of info, warn, error, log, and qa.
o info: Logs "einfo" messages printed by an ebuild
o warn: Logs "ewarn" messages printed by an ebuild
o error: Logs "eerror" messages printed by an ebuild
o log: Logs the "elog" messages found in some ebuilds
o qa: Logs the "QA Notice" messages printed by an ebuild
'''PORTAGE_ELOG_SYSTEM:''' This selects the module(s) to process the log messages. If left empty, logging is disabled. You can use any space-separated combination of save, custom, syslog, mail, save_summary, and mail_summary. You must select at least one module in order to use elog.
* save: This saves one log per package in $PORT_LOGDIR/elog, or /var/log/portage/elog if $PORT_LOGDIR is not defined.
* custom: Passes all messages to a user-defined command in $PORTAGE_ELOG_COMMAND; this will be discussed later.
* syslog: Sends all messages to the installed system logger.
* mail: Passes all messages to a user-defined mailserver in $PORTAGE_ELOG_MAILURI; this will be discussed later. The mail features of elog require >=portage-2.1.1.
* save_summary: Similar to save, but it merges all messages in $PORT_LOGDIR/elog/summary.log, or /var/log/portage/elog/summary.log if $PORT_LOGDIR is not defined.
* mail_summary: Similar to mail, but it sends all messages in a single mail when emerge exits.
http://www.gentoo.org/doc/en/handbook/h ... t=3&chap=1
**portage-2.1.3: "echo" - this prints all logged messages again at the end of the emerge

'''FEATURES="buildpkg"''' for building your own binary packages and saving them
http://gentoo-wiki.com/HOWTO_setup_a_PO ... OST_server
http://www.gentoo.org/proj/en/base/amd64/emul/index.xml

source /usr/portage/local/layman/make.conf -- location for your layman, for managing your overlays such as sabayon, xeffects, etc....

'''EMERGE_DEFAULT_OPTS="--with-bdeps y"''' # considers also build-time deps at dependency calculations
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=2

'''Man Make.conf'''
http://gentoo-wiki.com/MAN_makeconf

Do you see now why it is important to know this file? This file can make your gentoo based distro a much better experience. The gentoo handbook can help you set it up properly. Remember to take full advantage of changes, you need to be using certain flags like emerge --newuse foo. Recompiling your entire sytem and world is what you need to do to take advantage of your changes. Like for me I simple run emerge -uDN --world - that will update and make sure all packages are following my settings. If I changed a USE flag it will rebuild the packages effected and update packages to latest in portage.

Recompiling your system is not going to be easy if you are new to all of this. I recommend getting to know portage and how to work with portage before attempting it. It's something you just don't jump into. Your going to run into all sorts of issues and gonna have to search and find your answers. As of 3.4 you are gonna run into a python update, which requires taking care of first as things will break and need to get updated to the new python. Pending on your system - it can take several days to complete the process.
Learn your world file and cleaning it out before starting, this will save many hours of recompiling packages you don't need. The world file is a record of packages which have been specifically installed by the user. More specifically it's a list of packages which the user wants to keep installed and updated on their system. It will not record the dependencies of those packages, but instead uses the dependencies of the currently installed packages to keep track of this information. http://gentoo-wiki.com/HOWTO_Use_Portage_Correctly

You will also want to get yourself familiar with the files in your /etc/portage/ you will need to use them to mask and unmask needed packages. Also use em for telling how certain packages should be built.

Read thru the unofficial guide for a world update
viewtopic.php?f=54&t=5531

Best advice - Use the operating system till you know it, than start diving into the depths of the internal stuff. I know it is frustrating for people that are new, but if you give it time and stick with it, it will all come together. If all this information totally terrifies you, than stick with the default settings. Use the information for you knowledge. Topic is open for discussion.

[http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578 Forum Discussion]

==Config Files - An Introduction==

Without config files the operating sytem would be blah. Are you finding yourself confused with all the messages of portage telling you:
IMPORTANT: 124 config files in '/usr/share/X11/xkb' need updating

Well unfortunately with the amount of config files on your computer it is impossible to go over them all. I'm going to try and hit on the more important ones that are used more frequently.

Do you have to update your config files? The answer will be yes. Why? Cause things change over time.

How do I update my config files, portage keeps telling me I have config files to update? Well there is several ways to do this, you will need to run one of the following more popular methods.:
--------etc-update: http://www.gentoo-wiki.info/HOWTO_etc-update
--------dispatch-conf: http://www.gentoo-wiki.info/TIP_dispatch-conf

Do not and I repeat, do not blindly auto merge config file updates. You can hose your system to the point it won't boot back up. Well there is so many, how do I know if it is safe to or not? Good question and the rule of thumb is - if you have not edited a config file than generally your are safe, but this isn't a sure fire way. Using dispatch-conf will keep a back up copy of you old config files in case you need to restore them. Get to know your config files so you can be aware of certain files.

Remember to edit the config files you need to be root, so you will want to open konsole, type su, enter password and than nano or vi the file. You can do this via GUI too, just open konsole and run kdesu konqueror and when the box comes up, enter you root password and than you will have a root file manager window, gnome users will use gksu nautilus.

'''/etc/rc.conf''' - for general, system-wide configuration. Read the comments in the file, it's pretty well explained. If your window manager suddenly changes upon boot, this is one of the first files to check.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/conf.d/xdm''' - Is what controls your GUI login and window Manager. So if you GUI or login is messed up, be sure to check it out. It's self explanatory.
http://www.gentoo-wiki.info/HOWTO_Activate_Graphical_login

'''/etc/hosts''' - helps in resolving host names to IP addresses for hosts that aren't resolved by your nameserver.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/make.conf''' - This file contains various variables that are used by Portage. Portage will check the currently-defined environment variables first for any settings.
http://www.gentoo-wiki.info/MAN_makeconf
http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578

'''/boot/grub/grub.conf''' - Your boot manager so you can boot 1 or more operating systems. This is one of the first screens you will see and is asking for you to choose what operating system to boot.
http://www.gentoo-wiki.info/HOWTO_Quick_GRUB
http://www.gentoo-wiki.info/HOWTO_Dual_boot

'''/etx/X11/xorg.conf''' - Xorg is the X Window server which allows users to have a graphical environment. Got resolution problems? This file is for you.
http://www.gentoo.org/doc/en/xorg-config.xml

'''/etc/conf.d/net''' - your network configuration, see /etc/conf.d/net.example for a very well documented example â€“ dhcp, static, wireless, wired networking settings
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/resolv.conf''' - your DNS file, nothing to complicated, but if you can access your router but can't get web pages to load - check this file for DNS settings
http://www.gentoo.org/doc/en/home-router-howto.xml

'''/etc/fstab''' - This file contains the mount points of your partitions. Need to mount a hard drive? Add it here so it is available on every boot up.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/modules.autoload.d/kernel-2.6''' - You may have decided to compile some kernel components as modules (as opposed to compiled directly into the kernel) and would like to have them autoloaded on bootup like you did with 2.4. Also, if you installed any external modules from the portage tree you will probably want to autoload them too.
http://www.gentoo.org/doc/en/migration-to-2.6.xml

'''/etc/exports''' This is great for doing shares on the network using NFS
http://www.gentoo-wiki.info/HOWTO_Share_Directories_via_NFS
This also works great of sharing portage across multiple computers. You only need to sync one main computer than share your portage so the other computers will connect to your main computer for emerges
http://www.gentoo-wiki.info/HOWTO_Using_a_shared_portage_via_NFS

This hardly puts a dent in the amount of config files, but those are the ones I run across the most, plus trying to keep it friendly for people new to config files. I could of mentioned like local.start, but that is for experienced people.

Generally you can google and find some thing about the config file. Enter into google "gentoo xorg.conf" and you will find your answer. Feel free to add more that I may have missed here.

[http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10863 Forum Discussion]

HOWTO: Unoffical Guide To World Update

2013-02-23T14:02:17Z

Aposteeltje: /* Updating */

{{Warning| '''Portage (emerge) is not the primary package manager for Sabayon, this article is for advanced users only. In other words if this fails for you, its your fault. You have been warned.'''}}
=World Update and Understanding Configs=

==Updating==

First let me say that there is a several ways to doing things on SL. I am not saying that my way is the best way by any means. This is simply my way of how I do things with a fresh install to make a stable system. You should probably read the other articles below first to better understand things.

First thing - I alway buy my hardware that I know is linux supported and has good drivers. So get to know your hardware, I can't say that enough as it will save you a lot of headaches.

'''DO NOTE''' - I can not tell you what you can safely remove from your system as you need to know your hardware and what is safe to uninstall, remove from config files and remove from kernel. I am going to try and stay very basic here so you can get the idea.

Fresh install and everything is working great so now what?

----
Well I head to the /etc/make.conf file and edit that thing to my liking and double checking things over. I remove any unnecessary things. Remember to edit these files you must be root. If you like nano you can simple go into Konsole and punch in su than enter your password. You can edit the file by doing

{{Console| <pre class="clear"># nano -w /etc/make.conf</pre>}}

or if you simply must have a GUI you can go to konsole and enter

{{Console| <pre class="clear">$ kdesu konqueror</pre>}}

and when the box pops up, enter your password, wait a bit and a new window will come up. In that window you are root to everything and can edit anything. Pretty simple so far right? If you need help figuring out what options are available in the [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578 make.conf] then refer to the Gentoo Handbook and Wiki often.

----
Ok, so now that I got that set I like to head to the kernel and add to it and remove things I don't need by doing in konsole:

{{Console| <pre class="clear"># zcat /proc/config.gz > /usr/src/config

# genkernel --kernel-config=/usr/src/config --menuconfig --bootloader=grub --gensplash=sabayon all --luks</pre>}}

'''or if you use lvm do:''' - noted for waltercool

# genkernel --kernel-config=/usr/src/config --menuconfig --bootloader=grub --gensplash=sabayon --lvm2 all --luks

''note the # means you must be root, don't actually use the #''

This step is not necessary if you don't care that your kernel is big. I always need to enable some sound stuff and you may need to enable drivers, again, this is where knowing where your hardware is very important. You remove the wrong thing and your puter will not boot. Skip this step if you have a funny look on your face at this time.

----
NOTE: Before doing the following 'emerge -e' commands, you may want to customize your CFLAGS in make.conf so that it is optimized for your CPU type. The following two commands take very a long time, so it's worth it to optimize while you are taking the time to do this. Please refer to [http://http://en.gentoo-wiki.com/wiki/Safe_Cflags] for the correct setting for your specific CPU. Do not change your CHOST as described in that guide, changing CHOST is dangerous and not recommended. See [http://gentoo-wiki.com/HOWTO_change_CHOST_relatively_safely this HOWTO] if you wish to risk changing your CHOST.

Now some of you may totally think I am crazy here but as far as software removal I do that later. Yes I know I can remove software at this time that I will never use and save time when I recompile the system, but this is my unofficial stable system and I know it will work cause I have done it several times. So with that being said I want to now recompile just the system. Now I prefer to do :

# emerge -e system || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

Notice I have not done an emerge --sync yet and I don't want to do that yet, that will come later. So now several hours are going to go by. This a great thing to do when you are about to go to bed. After that is done, I like to do the world recompile:

# emerge -e world || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

do note once again that I have not used emerge --sync yet and this is going to be another lengthy process. You may do both commands at once by simply doing:

# emerge -e system || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done && emerge -e world || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

I just like to break it up.

----
So now I have finished recompiling everything and my processor is going Dude! Well now I punch in:

# emerge --sync && layman -S

to update my portage tree and overlays. First time syncs on SL are slow, I promise they will get faster after the first time. Once that is done I punch in:

# emerge -upDN world

this will pull up just under 400 packages, WOW!! Well lets get the show on the road.

# emerge -uN world

Now you look at that and go what happened to the D ?, again this is my guide and that will come later. Now you are probably sitting there thinking I thought SL doesn't recommend a world update. My feelings are this: no you don't need to, but SL 3.3 makes it a piece of cake to world update. Pre 3.3 I don't recommend, as you will be forever swamped with recompiling. Now with the world update you are going to run into bumps and this is where reading the ERROR MESSAGES is going to come to be Very Important. If you listen to what portage is telling you and use the Gentoo bugzilla and Gentoo forums for searching you can usually find the solution. Once a package fails I simply:

# emerge --resume --skipfirst

to continue on. I like to do this method to see what packages are failing. If you don't care:

# emerge -uN world || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

then it will auto skip and keep on going till finished. Now I don't try and fix any packages till it is completely done. Once it is done I look look at

#emerge -upN world

and go through each package and install it with the fix needed to get it to install. At this time I will simple remove any packages that have failed that I know I don't need. So now we are done and

# emerge -upN world

shows no packages left in it, time I fire up

# emerge -upDN world

YAY more packages to compile! The amount of packages won't be that much. So we wait for that to finish and I usually fix the errors as it goes along since it isn't very many packages. Now we have the entire system rebuilt, well almost. It's time to run:

# revdep-rebuild

and if that fails do:

# revdep-rebuild

It will find more packages to recompile! Your processor is probably plotting some sort of revenge against you at this time. So now what? Well, you are gonna have some config files that are screaming for an update. Now I like to use:

# etc-update

There is several ways to update config files, this is my way of doing it. So I punch in etc-update and many will auto merge, which is great with me. I look over the remaining ones left and determine if they are safe or not to update. Off the top of my head I believe all changes in 3.3 are safe, but look and if you are unsure, don't do it. So we have recompiled everything after making changes to system, updated the config files. Are we done? Do we dare reboot? Let's live dangerously and reboot, I mean a reinstall is only 40 minutes to do anyway right?

----
So we rebooted, prayed and we made it back to our Desktop!! So now, I like all the multimedia features the web has to offer, so I want to experience it all, so I open up my konsole again and punch in:

USE="divx gmedia gtk nls quicktime realmedia wmp" emerge mplayerplug-in

Yes, I know you can add this to your package.use file, but this is my guide and you should add it to your /etc/portage/package.use file for future use. Now I can sit back and view all the goodness of web multimedia! I hate totem handling the web plugins cause it sucks at doing so. I don't uninstall totem I simply move all the totem plugins out of the plugins folder:
/usr/lib/nsbrowser/plugins
and put em in
/usr/lib/nsbrowser
Just in case I ever want to put them back.

Alrighty then, we are world updated now. You can continue to stay world update and SL updated with the overlay by:

# emerge --sync && layman -S && emerge -uDN world

A handy automated script for this can be found here:
[http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=11870 Update Script]

----
Conclusion - my systems are rock solid no matter what I throw at them. It's a long process, but that's fine with me cause the results are worth it. Do keep in mind that it will take less time with the mini as there is less to deal with. It will require thinking and deciphering and good abilities of effective searching. No I can not help you world update your system as I have no idea what hardware you use or what you use your computer for. Is there a chance you may hose your system? Of course there is! It shouldn't happen if you pay attention. I can't stress enough to read the [http://www.gentoo.org/doc/en/handbook/index.xml Gentoo Handbook], look at the [http://gentoo-wiki.com Gentoo Wiki], look at the [http://forums.gentoo.org/ Gentoo Forum], look at the [http://wiki.sabayonlinux.org SL Wiki], look at the [http://www.sabayonlinux.org/forum SL Forum] and don't forget [http://google.com Google], bookmark them all!

That's it in a nutshell and I take NO and I mean NO Responsibilities for a hosed system. Your millage is going to vary of course depending on what hardware and software you use.

Input is welcome and I will answer questions if I know the answers.

HAPPY COMPILING!

[http://www.sabayonlinux.org/forum/viewtopic.php?t=5531 Forum Discussion]

==Understanding make.conf - An Introduction==
{{File|/etc/make.conf|<pre class="clear">
# These settings were set by the catalyst build script that automatically built this stage
# Please consult /etc/make.conf.example for a more detailed example
CFLAGS="-O3 -march=native -funroll-all-loops -m3dnow -msse3 -funit-at-a-time -fpeel-loops -ftracer -funswitch-loops -fomit-frame-pointer -pipe"
LDFLAGS="-Wl,-O1 -Wl,--enable-new-dtags -Wl,--sort-common -s"
CHOST="i586-pc-linux-gnu"
USE="win32codecs mp3 quicktime type1 divx4linux dvb dvd dvdread live mpeg nvidia jpeg truetype v4l v4l2 xv xvid multilib gnutls arts cups ppds foomatic-db \
alsa gimpprint freetype gnome X gtk gtk2 unicode moznocompose moznoirc moznomail kde qt samba xinerama xine theora kdeenablefinal wifi hal ieee1394 \
oggvorbis lm_sensors logitech-mouse zeroconf artswrappersuid nptl nptlonly rdesktop dvdr css gphoto2 openexr speex jpeg2k povray scanner musicbrainz \
accessibility audiofile exif xscreensaver ffmpeg vcd sndfile musepack asterisk mbrola pam_chroot pam_timestamp pwdb pda sms irda kig-scripting speedo \
browserplugin nsplugin ldap kerberos firefox dga aac dts xvmc dbus hal dvi on-the-fly-crypt dri xprint acpi ada ruby perforce cjk fat hfs jfs ntfs reiser4 \
xfs reiserfs skins cdda real shout stream a52 wxwindows vlm lirc libcaca remote stats lcd unichrome 7zip commercial mozsvg canvas xml2 glut java glitz svg \
avahi ogg vorbis aalib flac gdbm mikmod timidity kdgraphics dlloader exscalibar ipod visualization mono cdr nntp cairo djvu nautilus evo ole pdf xml ladspa \
soundtouch bzip2 udev mad fuse rtsp tiff kdehiddenvisibility dvi usb kipi aiglx musicbrainz pulseaudio dv lame mp3rtp udev cdr dvi djvu libnotify bzip2 aalib \
startup-notification nsplugin jingle gsm dbox2 opengl sdl png gif qt3 qt4 qt3support apache2 mysql php ssl xml berkdb innobd pcre"
CXXFLAGS="${CFLAGS}"
ACCEPT_KEYWORDS="~x86"
LINGUAS="en"
MAKEOPTS="-s -j3"
PORTAGE_NICENESS="8"
FEATURES="parallel-fetch"
CONFIG_PROTECT="/usr/kde/3.5/share/config/kdm/ /etc"
VIDEO_CARDS="vesa vga nvidia"
INPUT_DEVICES="evdev keyboard mouse"
LIRC_DEVICES="audio audio_alsa"
PORTAGE_ELOG_CLASSES="warn error log info"
PORTAGE_ELOG_SYSTEM="save"
# FEATURES="buildpkg"
source /usr/portage/local/layman/make.conf
EMERGE_DEFAULT_OPTS="--with-bdeps y"
</pre>}}

Above you will find a make.conf and is a vital component to your operating system. If you don't know this file you are defeating the purpose of this distro. One of the biggest things about gentoo based is being able to build the operating sytem to you. Using the default settings are going to work, but you are not taking full advantage of your potentials. You can ease our portage frustration also, like compiling issues.

Why do we need make.conf?
Portage uses this file to know how to build your entire system. All the settings you put here, portage reads and builds to them.

'''CFLAGS'''
CFLAGS are C compiler flags, usually GCC (GNU Compiler Collection) options.
CFLAGS are commonly used to specify the architecture of your computer, as well as the CPU you are using and any other special options you would like to enable or disable. This information is important to GCC because it tells it exactly how to customize the assembly instructions it creates from the application's source code.
http://gentoo-wiki.com/CFLAGS

'''LDFLAGS'''
Deals with your hash tables and compiler See for more information:
http://gentoo-wiki.com/TIP_Safe_LDFLAGS
http://lwn.net/Articles/192624/
Your not going to be touching these, so moving right along.

'''CHOST'''
Variable declares the target build host for your system You don't want to change this value unless you know what you are doing. You simply can't change it to i686 and go about using your computer. There is situations that may cause you to have to change this. For instance, lets say you upgrade your cpu or need a certain package that won't work with your current architect. Gentoo has a guide for changing it. Follow it closely or you will have a hosed system.
http://www.gentoo.org/doc/en/change-chost.xml

'''CXXFLAGS'''
CXXFLAGS is set to use all the options present in CFLAGS. This is what you'll want almost without fail. You shouldn't ever need to specify additional options in CXXFLAGS.
http://www.gentoo.org/doc/en/gcc-optimization.xml

'''USE'''
In Gentoo a USE flag is a representation of an option, a global setting for your final system. USE flags affect how many of the packages on your system will build. These depend on the software and your computer usage. It's important to know these and to thin the list down to your usage. You will see that I have a lot in mine, but that is because of testing I do for SL. All these USE settings are global, meaning they effect every package on your system. The more USE settings you have, the more conflicts you can encounter with portage when compiling software. There is a /etc/portage/package.use file that you can use to individually tell packages how you want them built.
http://gentoo-portage.com/USE
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=2

'''ACCEPT_KEYWORDS="~x86"'''
This is for setting which branch of portage you want to use. Stable vs. Unstable "bleeding edge". You can see by the ~ we are not using the stable branch so we are bleeding edge.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=3

'''LINGUAS'''
I hope this is self explanatory, but if not - your language
http://www.gentoo.org/doc/en/guide-localization.xml

'''MAKEOPTS'''
You define how many parallel compilations should occur when you install a package. A good choice is the number of CPUs in your system plus one, but this guideline isn't always perfect.
http://gentoo-wiki.com/Safe_Cflags
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=5

'''PORTAGE_NICENESS'''
If you keep using your computer while compiling packages you will notice that your box is less responsive than usual. This is caused by having two "groups" of processes with the same nice priority: your usual running processes, and emerge (and its child processes). Now, if you could renice emerge and its children to a higher nice value (i.e. lower priority), compiling would take somewhat longer, but your workstation will be as responsive as before.
http://gentoo-wiki.com/Portage_Niceness

'''FEATURES'''
Portage has several additional features that makes your Gentoo experience even better. Many of these features rely on certain software tools that improve performance, reliability, security, ...
Parallel fetch:
When you are emerging a series of packages, Portage can fetch the source files for the next package in the list even while it is compiling another package, thus shortening compile times..
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=3

'''CONFIG_PROTECT'''
This variable contains a space-delimited list of directories which should be protected by Portage during updates.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=5

'''VIDEO_CARDS'''
I see people's make.conf often and in the default make.conf there is like 20 video cards listed. Why compile more than you have too? Get rid of all the cards not in your computer.
http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml

'''INPUT_DEVICES'''
The same goes here, get rid of any equipment you don't have. My desktop doesn't have touchpad - why compile it?
http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml

'''LIRC_DEVICES'''
Linux Infrared Remote Control - this is where you are going to set your devices
http://gentoo-wiki.com/HOWTO_LIRC

'''source /usr/portage/local/layman/make.conf''' -- location for your layman, for managing your overlays such as sabayon, xeffects, etc....

Extras that I have added, just for my own use. You will not see these in a default make.conf
------------------------------------------------------------------------------------------------------------------------

'''PORTAGE_ELOG_CLASSES'''
Ebuild Logging -
Portage can create per-ebuild logfiles, but only when the PORT_LOGDIR variable is set to a location that is writable by Portage (the portage user). By default this variable is unset. If you don't set PORT_LOGDIR, then you won't receive any build logs with the current logging system, though you may receive some logs from the new elog. If you do have PORT_LOGDIR defined and you use elog, you will receive build logs and any logs saved by elog, as explained below.

Portage offers fine-grained control over logging through the use of elog:

* '''PORTAGE_ELOG_CLASSES:''' This is where you set what kinds of messages to be logged. You can use any space-separated combination of info, warn, error, log, and qa.
o info: Logs "einfo" messages printed by an ebuild
o warn: Logs "ewarn" messages printed by an ebuild
o error: Logs "eerror" messages printed by an ebuild
o log: Logs the "elog" messages found in some ebuilds
o qa: Logs the "QA Notice" messages printed by an ebuild
'''PORTAGE_ELOG_SYSTEM:''' This selects the module(s) to process the log messages. If left empty, logging is disabled. You can use any space-separated combination of save, custom, syslog, mail, save_summary, and mail_summary. You must select at least one module in order to use elog.
* save: This saves one log per package in $PORT_LOGDIR/elog, or /var/log/portage/elog if $PORT_LOGDIR is not defined.
* custom: Passes all messages to a user-defined command in $PORTAGE_ELOG_COMMAND; this will be discussed later.
* syslog: Sends all messages to the installed system logger.
* mail: Passes all messages to a user-defined mailserver in $PORTAGE_ELOG_MAILURI; this will be discussed later. The mail features of elog require >=portage-2.1.1.
* save_summary: Similar to save, but it merges all messages in $PORT_LOGDIR/elog/summary.log, or /var/log/portage/elog/summary.log if $PORT_LOGDIR is not defined.
* mail_summary: Similar to mail, but it sends all messages in a single mail when emerge exits.
http://www.gentoo.org/doc/en/handbook/h ... t=3&chap=1
**portage-2.1.3: "echo" - this prints all logged messages again at the end of the emerge

'''FEATURES="buildpkg"''' for building your own binary packages and saving them
http://gentoo-wiki.com/HOWTO_setup_a_PO ... OST_server
http://www.gentoo.org/proj/en/base/amd64/emul/index.xml

source /usr/portage/local/layman/make.conf -- location for your layman, for managing your overlays such as sabayon, xeffects, etc....

'''EMERGE_DEFAULT_OPTS="--with-bdeps y"''' # considers also build-time deps at dependency calculations
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=2

'''Man Make.conf'''
http://gentoo-wiki.com/MAN_makeconf

Do you see now why it is important to know this file? This file can make your gentoo based distro a much better experience. The gentoo handbook can help you set it up properly. Remember to take full advantage of changes, you need to be using certain flags like emerge --newuse foo. Recompiling your entire sytem and world is what you need to do to take advantage of your changes. Like for me I simple run emerge -uDN --world - that will update and make sure all packages are following my settings. If I changed a USE flag it will rebuild the packages effected and update packages to latest in portage.

Recompiling your system is not going to be easy if you are new to all of this. I recommend getting to know portage and how to work with portage before attempting it. It's something you just don't jump into. Your going to run into all sorts of issues and gonna have to search and find your answers. As of 3.4 you are gonna run into a python update, which requires taking care of first as things will break and need to get updated to the new python. Pending on your system - it can take several days to complete the process.
Learn your world file and cleaning it out before starting, this will save many hours of recompiling packages you don't need. The world file is a record of packages which have been specifically installed by the user. More specifically it's a list of packages which the user wants to keep installed and updated on their system. It will not record the dependencies of those packages, but instead uses the dependencies of the currently installed packages to keep track of this information. http://gentoo-wiki.com/HOWTO_Use_Portage_Correctly

You will also want to get yourself familiar with the files in your /etc/portage/ you will need to use them to mask and unmask needed packages. Also use em for telling how certain packages should be built.

Read thru the unofficial guide for a world update
viewtopic.php?f=54&t=5531

Best advice - Use the operating system till you know it, than start diving into the depths of the internal stuff. I know it is frustrating for people that are new, but if you give it time and stick with it, it will all come together. If all this information totally terrifies you, than stick with the default settings. Use the information for you knowledge. Topic is open for discussion.

[http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578 Forum Discussion]

==Config Files - An Introduction==

Without config files the operating sytem would be blah. Are you finding yourself confused with all the messages of portage telling you:
IMPORTANT: 124 config files in '/usr/share/X11/xkb' need updating

Well unfortunately with the amount of config files on your computer it is impossible to go over them all. I'm going to try and hit on the more important ones that are used more frequently.

Do you have to update your config files? The answer will be yes. Why? Cause things change over time.

How do I update my config files, portage keeps telling me I have config files to update? Well there is several ways to do this, you will need to run one of the following more popular methods.:
--------etc-update: http://www.gentoo-wiki.info/HOWTO_etc-update
--------dispatch-conf: http://www.gentoo-wiki.info/TIP_dispatch-conf

Do not and I repeat, do not blindly auto merge config file updates. You can hose your system to the point it won't boot back up. Well there is so many, how do I know if it is safe to or not? Good question and the rule of thumb is - if you have not edited a config file than generally your are safe, but this isn't a sure fire way. Using dispatch-conf will keep a back up copy of you old config files in case you need to restore them. Get to know your config files so you can be aware of certain files.

Remember to edit the config files you need to be root, so you will want to open konsole, type su, enter password and than nano or vi the file. You can do this via GUI too, just open konsole and run kdesu konqueror and when the box comes up, enter you root password and than you will have a root file manager window, gnome users will use gksu nautilus.

'''/etc/rc.conf''' - for general, system-wide configuration. Read the comments in the file, it's pretty well explained. If your window manager suddenly changes upon boot, this is one of the first files to check.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/conf.d/xdm''' - Is what controls your GUI login and window Manager. So if you GUI or login is messed up, be sure to check it out. It's self explanatory.
http://www.gentoo-wiki.info/HOWTO_Activate_Graphical_login

'''/etc/hosts''' - helps in resolving host names to IP addresses for hosts that aren't resolved by your nameserver.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/make.conf''' - This file contains various variables that are used by Portage. Portage will check the currently-defined environment variables first for any settings.
http://www.gentoo-wiki.info/MAN_makeconf
http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578

'''/boot/grub/grub.conf''' - Your boot manager so you can boot 1 or more operating systems. This is one of the first screens you will see and is asking for you to choose what operating system to boot.
http://www.gentoo-wiki.info/HOWTO_Quick_GRUB
http://www.gentoo-wiki.info/HOWTO_Dual_boot

'''/etx/X11/xorg.conf''' - Xorg is the X Window server which allows users to have a graphical environment. Got resolution problems? This file is for you.
http://www.gentoo.org/doc/en/xorg-config.xml

'''/etc/conf.d/net''' - your network configuration, see /etc/conf.d/net.example for a very well documented example â€“ dhcp, static, wireless, wired networking settings
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/resolv.conf''' - your DNS file, nothing to complicated, but if you can access your router but can't get web pages to load - check this file for DNS settings
http://www.gentoo.org/doc/en/home-router-howto.xml

'''/etc/fstab''' - This file contains the mount points of your partitions. Need to mount a hard drive? Add it here so it is available on every boot up.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/modules.autoload.d/kernel-2.6''' - You may have decided to compile some kernel components as modules (as opposed to compiled directly into the kernel) and would like to have them autoloaded on bootup like you did with 2.4. Also, if you installed any external modules from the portage tree you will probably want to autoload them too.
http://www.gentoo.org/doc/en/migration-to-2.6.xml

'''/etc/exports''' This is great for doing shares on the network using NFS
http://www.gentoo-wiki.info/HOWTO_Share_Directories_via_NFS
This also works great of sharing portage across multiple computers. You only need to sync one main computer than share your portage so the other computers will connect to your main computer for emerges
http://www.gentoo-wiki.info/HOWTO_Using_a_shared_portage_via_NFS

This hardly puts a dent in the amount of config files, but those are the ones I run across the most, plus trying to keep it friendly for people new to config files. I could of mentioned like local.start, but that is for experienced people.

Generally you can google and find some thing about the config file. Enter into google "gentoo xorg.conf" and you will find your answer. Feel free to add more that I may have missed here.

[http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10863 Forum Discussion]

En:Repositories

2013-02-20T23:44:01Z

Aposteeltje:

{{I18n| [[De:Repositories|de]] [[En:Repositories|en]]}}

In /etc/entropy/repositories.conf you find the general configuration that count for all repositories. The different repositories are inherited from a subdirectory: /etc/entropy/repositories.conf.d

In this subdirectory you should find some predefined examples for the different repositories.

However, in some cases, somehow those example files are missing, so you'll have to create them manually.

If this is the case, then follow the below instructions to create them, and eventually enable those you wish to use.

Open your favourite terminal and become root.

Navigate to the subdirectory:
{{Console| <pre class="clear"># cd /etc/entropy/repositories.conf.d</pre>}}

Now we create the files, beginning with a underscore(dash down)., so later on you can easily enable/disable them, using the commandline, or even with Rigo/Sulfur.

To create the '''daily''' Repository, (if missing):
{{Console| <pre class="clear"># nano -w _entropy_sabayonlinux.org</pre>}}

Make sure it has the following content:
{{Console| <pre class="clear"># Sabayon Linux Official Repository
epository = sabayonlinux.org|Sabayon Linux Official Repository|http://best.sabayon.org/entropy|http://pkg.sabayon.org#bz2
repository = sabayonlinux.org||http://gd.tuwien.ac.at/opsys/linux/sabayonlinux/entropy|
repository = sabayonlinux.org||http://ftp.kddilabs.jp/Linux/packages/sabayonlinux/entropy|
repository = sabayonlinux.org||http://mirror.internode.on.net/pub/sabayon/entropy|
repository = sabayonlinux.org||http://sabayon.c3sl.ufpr.br/entropy|
repository = sabayonlinux.org||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
repository = sabayonlinux.org||http://mirror.clarkson.edu/sabayon/entropy|
repository = sabayonlinux.org||http://cross-lfs.sabayonlinux.org/entropy|
repository = sabayonlinux.org||http://mirror.umd.edu/sabayonlinux/entropy|
repository = sabayonlinux.org||http://ftp.cc.uoc.gr/mirrors/linux/SabayonLinux/entropy|
repository = sabayonlinux.org||http://ftp.rnl.ist.utl.pt/pub/sabayon/entropy|
repository = sabayonlinux.org||http://mirror.yandex.ru/sabayon/entropy|
repository = sabayonlinux.org||http://dl.sabayon.org/entropy|
repository = sabayonlinux.org||http://redir.sabayon.org/entropy|
repository = sabayonlinux.org||http://debian.mirror.dkm.cz/sabayon/entropy|
repository = sabayonlinux.org||ftp://ftp.klid.dk/sabayonlinux/entropy|
repository = sabayonlinux.org||http://pkg.sabayon.org|
repository = sabayonlinux.org||http://mirror.de.sabayon.org/entropy|
repository = sabayonlinux.org||http://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository = sabayonlinux.org||ftp://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository = sabayonlinux.org||http://mirror.freelydifferent.com/sabayon/entropy|
repository = sabayonlinux.org||http://ftp.surfnet.nl/pub/os/Linux/distr/sabayonlinux/entropy|
</pre>}}

Save the file (ctrl-o) and exit the nano editor (ctrl-x).

To create the '''weekly''' Repository, (if missing):
{{Console| <pre class="clear"># nano -w _entropy_sabayon-weekly</pre>}}

Make sure it has the following content:
{{Console| <pre class="clear"># weekly
repository = sabayon-weekly|Sabayon Linux Official Repository|http://dl.sabayon.org/entropy|http://pkg.sabayon.org#bz2
repository = sabayon-weekly||http://redir.sabayon.org/entropy|
repository = sabayon-weekly||http://ftp.kddilabs.jp/Linux/packages/sabayonlinux/entropy|
repository = sabayon-weekly||http://gd.tuwien.ac.at/opsys/linux/sabayonlinux/entropy|
repository = sabayon-weekly||ftp://ftp.riken.jp/Linux/sabayon/entropy|
repository = sabayon-weekly||http://mirror.optusnet.com.au/sabayon/entropy|
repository = sabayon-weekly||http://mirror.internode.on.net/pub/sabayon/entropy|
repository = sabayon-weekly||http://sabayon.c3sl.ufpr.br/entropy|
repository = sabayon-weekly||http://mirror.clarkson.edu/sabayon/entropy|
repository = sabayon-weekly||http://cross-lfs.sabayonlinux.org/entropy|
repository = sabayon-weekly||http://mirror.umd.edu/sabayonlinux/entropy|
repository = sabayon-weekly||http://best.sabayon.org/entropy|
repository = sabayon-weekly||ftp://ftp.rnl.ist.utl.pt/pub/sabayon/entropy|
repository = sabayon-weekly||http://ftp.cc.uoc.gr/mirrors/linux/SabayonLinux/entropy|
repository = sabayon-weekly||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
repository = sabayon-weekly||http://debian.mirror.dkm.cz/sabayon/entropy|
repository = sabayon-weekly||ftp://ftp.klid.dk/sabayonlinux/entropy|
repository = sabayon-weekly||http://pkg.sabayon.org|
repository = sabayon-weekly||http://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository = sabayon-weekly||ftp://ftp.belnet.be/mirror/sabayonlinux/entropy|
repository = sabayon-weekly||ftp://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository = sabayon-weekly||http://mirror.freelydifferent.com/sabayon/entropy|
repository = sabayon-weekly||http://ftp.surfnet.nl/pub/os/Linux/distr/sabayonlinux/entropy|
</pre>}}

Save the file (ctrl-o) and exit the nano editor (ctrl-x).

To create the '''testing''' Repository (Limbo), (if missing):
{{Console| <pre class="clear"># nano -w _entropy_sabayon-limbo</pre>}}

Make sure it has the following content:
{{Console| <pre class="clear"># Limbo
repository = sabayon-limbo|Sabayon Limbo Testing Repository|http://gd.tuwien.ac.at/opsys/linux/sabayonlinux/entropy|http://pkg.sabayon.or$
repository = sabayon-limbo||ftp://ftp.riken.jp/Linux/sabayon/entropy|
repository = sabayon-limbo||http://mirror.optusnet.com.au/sabayon/entropy|
repository = sabayon-limbo||http://mirror.internode.on.net/pub/sabayon/entropy|
repository = sabayon-limbo||http://ftp.kddilabs.jp/Linux/packages/sabayonlinux/entropy|
repository = sabayon-limbo||http://sabayon.c3sl.ufpr.br/entropy|
repository = sabayon-limbo||http://cross-lfs.sabayonlinux.org/entropy|
repository = sabayon-limbo||http://mirror.clarkson.edu/sabayon/entropy|
repository = sabayon-limbo||http://mirror.umd.edu/sabayonlinux/entropy|
repository = sabayon-limbo||ftp://ftp.rnl.ist.utl.pt/pub/sabayon/entropy|
repository = sabayon-limbo||http://ftp.cc.uoc.gr/mirrors/linux/SabayonLinux/entropy|
repository = sabayon-limbo||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
repository = sabayon-limbo||http://debian.mirror.dkm.cz/sabayon/entropy|
repository = sabayon-limbo||http://best.sabayon.org/entropy|
repository = sabayon-limbo||http://pkg.sabayon.org|
repository = sabayon-limbo||ftp://ftp.klid.dk/sabayonlinux/entropy|
repository = sabayon-limbo||http://redir.sabayon.org/entropy|
repository = sabayon-limbo||http://dl.sabayon.org/entropy|
repository = sabayon-limbo||http://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository = sabayon-limbo||http://mirror.freelydifferent.com/sabayon/entropy|
repository = sabayon-limbo||http://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository = sabayon-limbo||http://ftp.surfnet.nl/pub/os/Linux/distr/sabayonlinux/entropy|
</pre>}}

Save the file (ctrl-o) and exit the nano editor (ctrl-x).

Now if you want to enable/disable the different repositories, the command is:
{{Console| <pre class="clear"># equo repo enable repository</pre>}}
{{Console| <pre class="clear"># equo repo disable repository</pre>}}

to enable '''daily''':
{{Console| <pre class="clear"># equo repo enable sabayonlinux.org</pre>}}

to enable '''weekly''':
{{Console| <pre class="clear"># equo repo enable sabayon-weekly</pre>}}

and to enable '''limbo''' testing repository:
{{Console| <pre class="clear"># equo repo enable sabayon-limbo</pre>}}

When using [[Rigo]], please see: [[Rigo#Manage_Repositories]]

En:Repositories

2013-02-20T22:54:12Z

Aposteeltje:

{{I18n| [[De:Repositories|de]] [[En:Repositories|en]]}}

In /etc/entropy/repositories.conf you find the general configuration that count for all repositories. The different repositories are inherited from a subdirectory: /etc/entropy/repositories.conf.d

In this subdirectory you should find some predefined examples for the different repositories.

However, in some cases, somehow those example files are missing, so you'll have to create them manually.

If this is the case, then follow the below instructions to create them, and eventually enable those you wish to use.

Open your favourite terminal and become root.

Navigate to the subdirectory:
{{Console| <pre class="clear"># cd /etc/entropy/repositories.conf.d</pre>}}

Now we create the files, beginning with a underscore(dash down)., so later on you can easily enable/disable them, using the commandline, or even with Rigo/Sulfur.

To create the '''daily''' Repository, (if missing):
{{Console| <pre class="clear"># nano -w _entropy_sabayonlinux.org</pre>}}

Make sure it has the following content:
{{Console| <pre class="clear"># Sabayon Linux Official Repository
repository|sabayonlinux.org|Sabayon Linux Official Repository|http://cerberus.itti.ifce.edu.br/entropy|http://pkg.sabayon.org,sabayon.org
repository|sabayonlinux.org||ftp://ftp.riken.jp/Linux/sabayon/entropy|
repository|sabayonlinux.org||http://mirror.optusnet.com.au/sabayon/entropy|
repository|sabayonlinux.org||http://ftp2.cz.freebsd.org/pub/sabayon/entropy|
repository|sabayonlinux.org||http://debian.mirror.dkm.cz/sabayon/entropy|
repository|sabayonlinux.org||http://mirror.us.sabayon.org/sabayon/entropy|
repository|sabayonlinux.org||http://mirror.umoss.org/sabayonlinux/entropy|
repository|sabayonlinux.org||ftp://ftp.klid.dk/sabayonlinux/entropy|
repository|sabayonlinux.org||http://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository|sabayonlinux.org||ftp://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository|sabayonlinux.org||http://mirrors.cs.wmich.edu/sabayon/entropy|
repository|sabayonlinux.org||http://ftp.surfnet.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository|sabayonlinux.org||ftp://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository|sabayonlinux.org||http://ftp.cc.uoc.gr/mirrors/linux/SabayonLinux/entropy|
repository|sabayonlinux.org||http://mirror.dun.nu/sabayonlinux/entropy|
repository|sabayonlinux.org||ftp://ftp.rnl.ist.utl.pt/pub/sabayon/entropy|
repository|sabayonlinux.org||http://ftp.rnl.ist.utl.pt/pub/sabayon/entropy|
repository|sabayonlinux.org||http://mirror.internode.on.net/pub/sabayon/entropy|
repository|sabayonlinux.org||http://cross-lfs.sabayonlinux.org/entropy|
repository|sabayonlinux.org||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
</pre>}}

Save the file (ctrl-o) and exit the nano editor (ctrl-x).

To create the '''weekly''' Repository, (if missing):
{{Console| <pre class="clear"># nano -w _entropy_sabayon-weekly</pre>}}

Make sure it has the following content:
{{Console| <pre class="clear"># weekly
repository = sabayon-weekly|Sabayon Linux Official Repository|http://gd.tuwien.ac.at/opsys/linux/sabayonlinux/entropy|http://pkg.sabayon.org#bz2
repository = sabayon-weekly||ftp://ftp.rnl.ist.utl.pt/pub/sabayon/entropy|
repository = sabayon-weekly||http://ftp.rnl.ist.utl.pt/pub/sabayon/entropy|
repository = sabayon-weekly||http://mirror.optusnet.com.au/sabayon/entropy|
repository = sabayon-weekly||ftp://ftp.riken.jp/Linux/sabayon/entropy|
repository = sabayon-weekly||http://mirror.clarkson.edu/sabayon/entropy|
repository = sabayon-weekly||http://mirror.internode.on.net/pub/sabayon/entropy|
repository = sabayon-weekly||http://sabayon.c3sl.ufpr.br/entropy|
repository = sabayon-weekly||http://ftp.kddilabs.jp/Linux/packages/sabayonlinux/entropy|
repository = sabayon-weekly||http://mirror.freelydifferent.com/sabayon/entropy|
repository = sabayon-weekly||http://cross-lfs.sabayonlinux.org/entropy|
repository = sabayon-weekly||http://mirror.umd.edu/sabayonlinux/entropy|
repository = sabayon-weekly||http://pkg.sabayon.org|
repository = sabayon-weekly||http://ftp.cc.uoc.gr/mirrors/linux/SabayonLinux/entropy|
repository = sabayon-weekly||ftp://ftp.klid.dk/sabayonlinux/entropy|
repository = sabayon-weekly||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
repository = sabayon-weekly||http://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository = sabayon-weekly||http://debian.mirror.dkm.cz/sabayon/entropy|
repository = sabayon-weekly||ftp://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository = sabayon-weekly||http://ftp.surfnet.nl/pub/os/Linux/distr/sabayonlinux/entropy|
</pre>}}

Save the file (ctrl-o) and exit the nano editor (ctrl-x).

To create the '''testing''' Repository (Limbo), (if missing):
{{Console| <pre class="clear"># nano -w _entropy_sabayon-limbo</pre>}}

Make sure it has the following content:
{{Console| <pre class="clear"># Limbo
repository = sabayon-limbo|Sabayon Limbo Testing Repository|http://gd.tuwien.ac.at/opsys/linux/sabayonlinux/entropy|http://pkg.sabayon.or$
repository = sabayon-limbo||ftp://ftp.riken.jp/Linux/sabayon/entropy|
repository = sabayon-limbo||http://mirror.optusnet.com.au/sabayon/entropy|
repository = sabayon-limbo||http://mirror.internode.on.net/pub/sabayon/entropy|
repository = sabayon-limbo||http://ftp.kddilabs.jp/Linux/packages/sabayonlinux/entropy|
repository = sabayon-limbo||http://sabayon.c3sl.ufpr.br/entropy|
repository = sabayon-limbo||http://cross-lfs.sabayonlinux.org/entropy|
repository = sabayon-limbo||http://mirror.clarkson.edu/sabayon/entropy|
repository = sabayon-limbo||http://mirror.umd.edu/sabayonlinux/entropy|
repository = sabayon-limbo||ftp://ftp.rnl.ist.utl.pt/pub/sabayon/entropy|
repository = sabayon-limbo||http://ftp.cc.uoc.gr/mirrors/linux/SabayonLinux/entropy|
repository = sabayon-limbo||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
repository = sabayon-limbo||http://debian.mirror.dkm.cz/sabayon/entropy|
repository = sabayon-limbo||http://best.sabayon.org/entropy|
repository = sabayon-limbo||http://pkg.sabayon.org|
repository = sabayon-limbo||ftp://ftp.klid.dk/sabayonlinux/entropy|
repository = sabayon-limbo||http://redir.sabayon.org/entropy|
repository = sabayon-limbo||http://dl.sabayon.org/entropy|
repository = sabayon-limbo||http://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository = sabayon-limbo||http://mirror.freelydifferent.com/sabayon/entropy|
repository = sabayon-limbo||http://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository = sabayon-limbo||http://ftp.surfnet.nl/pub/os/Linux/distr/sabayonlinux/entropy|
</pre>}}

Save the file (ctrl-o) and exit the nano editor (ctrl-x).

Now if you want to enable/disable the different repositories, the command is:
{{Console| <pre class="clear"># equo repo enable repository</pre>}}
{{Console| <pre class="clear"># equo repo disable repository</pre>}}

to enable '''daily''':
{{Console| <pre class="clear"># equo repo enable sabayonlinux.org</pre>}}

to enable '''weekly''':
{{Console| <pre class="clear"># equo repo enable sabayon-weekly</pre>}}

and to enable '''limbo''' testing repository:
{{Console| <pre class="clear"># equo repo enable sabayon-limbo</pre>}}

When using [[Rigo]], please see: [[Rigo#Manage_Repositories]]

En:Repositories

2013-02-20T22:08:27Z

Aposteeltje:

{{I18n| [[De:Repositories|de]] [[En:Repositories|en]]}}

In /etc/entropy/repositories.conf you find the general configuration that count for all repositories. The different repositories are inherited from a subdirectory: /etc/entropy/repositories.conf.d

In this subdirectory you should find some predefined examples for the different repositories.

However, in some cases, somehow those example files are missing, so you'll have to create them manually.

If this is the case, then follow the below instructions to create them, and eventually enable those you wish to use.

Open your favourite terminal and become root.

Navigate to the subdirectory:
{{Console| <pre class="clear"># cd /etc/entropy/repositories.conf.d</pre>}}

Now we create the files, beginning with a underscore(dash down)., so later on you can easily enable/disable them, using the commandline, or even with Rigo/Sulfur.

To create the '''daily''' Repository, (if missing):
{{Console| <pre class="clear"># nano -w _entropy_sabayonlinux.org</pre>}}

Make sure it has the following content:
{{Console| <pre class="clear"># Sabayon Linux Official Repository
repository|sabayonlinux.org|Sabayon Linux Official Repository|http://cerberus.itti.ifce.edu.br/entropy|http://pkg.sabayon.org,sabayon.org
repository|sabayonlinux.org||ftp://ftp.riken.jp/Linux/sabayon/entropy|
repository|sabayonlinux.org||http://mirror.optusnet.com.au/sabayon/entropy|
repository|sabayonlinux.org||http://ftp2.cz.freebsd.org/pub/sabayon/entropy|
repository|sabayonlinux.org||http://debian.mirror.dkm.cz/sabayon/entropy|
repository|sabayonlinux.org||http://mirror.us.sabayon.org/sabayon/entropy|
repository|sabayonlinux.org||http://mirror.umoss.org/sabayonlinux/entropy|
repository|sabayonlinux.org||ftp://ftp.klid.dk/sabayonlinux/entropy|
repository|sabayonlinux.org||http://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository|sabayonlinux.org||ftp://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository|sabayonlinux.org||http://mirrors.cs.wmich.edu/sabayon/entropy|
repository|sabayonlinux.org||http://ftp.surfnet.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository|sabayonlinux.org||ftp://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository|sabayonlinux.org||http://ftp.cc.uoc.gr/mirrors/linux/SabayonLinux/entropy|
repository|sabayonlinux.org||http://mirror.dun.nu/sabayonlinux/entropy|
repository|sabayonlinux.org||ftp://ftp.rnl.ist.utl.pt/pub/sabayon/entropy|
repository|sabayonlinux.org||http://ftp.rnl.ist.utl.pt/pub/sabayon/entropy|
repository|sabayonlinux.org||http://mirror.internode.on.net/pub/sabayon/entropy|
repository|sabayonlinux.org||http://cross-lfs.sabayonlinux.org/entropy|
repository|sabayonlinux.org||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
</pre>}}

Save the file (ctrl-o) and exit the nano editor (ctrl-x).

To create the '''weekly''' Repository, (if missing):
{{Console| <pre class="clear"># nano -w _entropy_sabayon-weekly</pre>}}

Make sure it has the following content:
{{Console| <pre class="clear"># weekly
repository = sabayon-weekly|Sabayon Linux Official Repository|http://gd.tuwien.ac.at/opsys/linux/sabayonlinux/entropy|http://pkg.sabayon.org#bz2
repository = sabayon-weekly||ftp://ftp.rnl.ist.utl.pt/pub/sabayon/entropy|
repository = sabayon-weekly||http://ftp.rnl.ist.utl.pt/pub/sabayon/entropy|
repository = sabayon-weekly||http://mirror.optusnet.com.au/sabayon/entropy|
repository = sabayon-weekly||ftp://ftp.riken.jp/Linux/sabayon/entropy|
repository = sabayon-weekly||http://mirror.clarkson.edu/sabayon/entropy|
repository = sabayon-weekly||http://mirror.internode.on.net/pub/sabayon/entropy|
repository = sabayon-weekly||http://sabayon.c3sl.ufpr.br/entropy|
repository = sabayon-weekly||http://ftp.kddilabs.jp/Linux/packages/sabayonlinux/entropy|
repository = sabayon-weekly||http://mirror.freelydifferent.com/sabayon/entropy|
repository = sabayon-weekly||http://cross-lfs.sabayonlinux.org/entropy|
repository = sabayon-weekly||http://mirror.umd.edu/sabayonlinux/entropy|
repository = sabayon-weekly||http://pkg.sabayon.org|
repository = sabayon-weekly||http://ftp.cc.uoc.gr/mirrors/linux/SabayonLinux/entropy|
repository = sabayon-weekly||ftp://ftp.klid.dk/sabayonlinux/entropy|
repository = sabayon-weekly||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
repository = sabayon-weekly||http://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository = sabayon-weekly||http://debian.mirror.dkm.cz/sabayon/entropy|
repository = sabayon-weekly||ftp://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository = sabayon-weekly||http://ftp.surfnet.nl/pub/os/Linux/distr/sabayonlinux/entropy|
</pre>}}

Save the file (ctrl-o) and exit the nano editor (ctrl-x).

To create the '''testing''' Repository (Limbo), (if missing):
{{Console| <pre class="clear"># nano -w _entropy_sabayon-limbo</pre>}}

Make sure it has the following content:
{{Console| <pre class="clear"># Limbo
repository = sabayon-limbo|Sabayon Limbo Testing Repository|http://cerberus.itti.ifce.edu.br/entropy|http://pkg.sabayon.org,sabayon.org
repository = sabayon-limbo||http://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository = sabayon-limbo||ftp://ftp.rnl.ist.utl.pt/pub/sabayon/entropy/standard|
repository = sabayon-limbo||http://ftp.rnl.ist.utl.pt/pub/sabayon/entropy/standard|
repository = sabayon-limbo||ftp://ftp.riken.jp/Linux/sabayon/entropy|
repository = sabayon-limbo||http://mirror.optusnet.com.au/sabayon/entropy|
repository = sabayon-limbo||http://mirror.internode.on.net/pub/sabayon/entropy|
repository = sabayon-limbo||http://cross-lfs.sabayonlinux.org/entropy|
repository = sabayon-limbo||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
</pre>}}

Save the file (ctrl-o) and exit the nano editor (ctrl-x).

Now if you want to enable/disable the different repositories, the command is:
{{Console| <pre class="clear"># equo repo enable repository</pre>}}
{{Console| <pre class="clear"># equo repo disable repository</pre>}}

to enable '''daily''':
{{Console| <pre class="clear"># equo repo enable sabayonlinux.org</pre>}}

to enable '''weekly''':
{{Console| <pre class="clear"># equo repo enable sabayon-weekly</pre>}}

and to enable '''limbo''' testing repository:
{{Console| <pre class="clear"># equo repo enable sabayon-limbo</pre>}}

When using [[Rigo]], please see: [[Rigo#Manage_Repositories]]

En:Repositories

2013-02-20T21:56:46Z

Aposteeltje:

{{I18n| [[De:Repositories|de]] [[En:Repositories|en]]}}

In /etc/entropy/repositories.conf you find the general configuration that count for all repositories. The different repositories are inherited from a subdirectory: /etc/entropy/repositories.conf.d

In this subdirectory you should find some predefined examples for the different repositories.

However, in some cases, somehow those example files are missing, so you'll have to create them manually.

If this is the case, then follow the below instructions to create them, and eventually enable those you wish to use.

Open your favourite terminal and become root.

Navigate to the subdirectory:
{{Console| <pre class="clear"># cd /etc/entropy/repositories.conf.d</pre>}}

Now we create the files, beginning with a underscore(dash down)., so later on you can easily enable/disable them, using the commandline, or even with Rigo/Sulfur.

To create the '''daily''' Repository, (if missing):
{{Console| <pre class="clear"># nano -w _entropy_sabayonlinux.org</pre>}}

Make sure it has the following content:
{{Console| <pre class="clear"># Sabayon Linux Official Repository
repository|sabayonlinux.org|Sabayon Linux Official Repository|http://cerberus.itti.ifce.edu.br/entropy|http://pkg.sabayon.org,sabayon.org
repository|sabayonlinux.org||ftp://ftp.riken.jp/Linux/sabayon/entropy|
repository|sabayonlinux.org||http://mirror.optusnet.com.au/sabayon/entropy|
repository|sabayonlinux.org||http://ftp2.cz.freebsd.org/pub/sabayon/entropy|
repository|sabayonlinux.org||http://debian.mirror.dkm.cz/sabayon/entropy|
repository|sabayonlinux.org||http://mirror.us.sabayon.org/sabayon/entropy|
repository|sabayonlinux.org||http://mirror.umoss.org/sabayonlinux/entropy|
repository|sabayonlinux.org||ftp://ftp.klid.dk/sabayonlinux/entropy|
repository|sabayonlinux.org||http://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository|sabayonlinux.org||ftp://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository|sabayonlinux.org||http://mirrors.cs.wmich.edu/sabayon/entropy|
repository|sabayonlinux.org||http://ftp.surfnet.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository|sabayonlinux.org||ftp://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository|sabayonlinux.org||http://ftp.cc.uoc.gr/mirrors/linux/SabayonLinux/entropy|
repository|sabayonlinux.org||http://mirror.dun.nu/sabayonlinux/entropy|
repository|sabayonlinux.org||ftp://ftp.rnl.ist.utl.pt/pub/sabayon/entropy/standard|
repository|sabayonlinux.org||http://ftp.rnl.ist.utl.pt/pub/sabayon/entropy/standard|
repository|sabayonlinux.org||http://mirror.internode.on.net/pub/sabayon/entropy|
repository|sabayonlinux.org||http://cross-lfs.sabayonlinux.org/entropy|
repository|sabayonlinux.org||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
</pre>}}

Save the file (ctrl-o) and exit the nano editor (ctrl-x).

To create the '''weekly''' Repository, (if missing):
{{Console| <pre class="clear"># nano -w _entropy_sabayon-weekly</pre>}}

Make sure it has the following content:
{{Console| <pre class="clear"># weekly
repository = sabayon-weekly|Sabayon Linux Official Repository|http://http://gd.tuwien.ac.at/opsys/linux/sabayonlinux/entropy/standard|http://pkg.sabayon.org#bz2
repository = sabayon-weekly||ftp://ftp.rnl.ist.utl.pt/pub/sabayon/entropy/standard|
repository = sabayon-weekly||http://ftp.rnl.ist.utl.pt/pub/sabayon/entropy/standard|
repository = sabayon-weekly||http://mirror.optusnet.com.au/sabayon/entropy|
repository = sabayon-weekly||ftp://ftp.riken.jp/Linux/sabayon/entropy|
repository = sabayon-weekly||http://mirror.clarkson.edu/sabayon/entropy|
repository = sabayon-weekly||http://mirror.internode.on.net/pub/sabayon/entropy|
repository = sabayon-weekly||http://sabayon.c3sl.ufpr.br/entropy|
repository = sabayon-weekly||http://ftp.kddilabs.jp/Linux/packages/sabayonlinux/entropy|
repository = sabayon-weekly||http://mirror.freelydifferent.com/sabayon/entropy|
repository = sabayon-weekly||http://cross-lfs.sabayonlinux.org/entropy|
repository = sabayon-weekly||http://mirror.umd.edu/sabayonlinux/entropy|
repository = sabayon-weekly||http://pkg.sabayon.org|
repository = sabayon-weekly||http://ftp.cc.uoc.gr/mirrors/linux/SabayonLinux/entropy|
repository = sabayon-weekly||ftp://ftp.klid.dk/sabayonlinux/entropy|
repository = sabayon-weekly||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
repository = sabayon-weekly||http://ftp.fsn.hu/pub/linux/distributions/sabayon/entropy|
repository = sabayon-weekly||http://debian.mirror.dkm.cz/sabayon/entropy|
repository = sabayon-weekly||ftp://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository = sabayon-weekly||http://ftp.surfnet.nl/pub/os/Linux/distr/sabayonlinux/entropy|
</pre>}}

Save the file (ctrl-o) and exit the nano editor (ctrl-x).

To create the '''testing''' Repository (Limbo), (if missing):
{{Console| <pre class="clear"># nano -w _entropy_sabayon-limbo</pre>}}

Make sure it has the following content:
{{Console| <pre class="clear"># Limbo
repository = sabayon-limbo|Sabayon Limbo Testing Repository|http://cerberus.itti.ifce.edu.br/entropy|http://pkg.sabayon.org,sabayon.org
repository = sabayon-limbo||http://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy|
repository = sabayon-limbo||ftp://ftp.rnl.ist.utl.pt/pub/sabayon/entropy/standard|
repository = sabayon-limbo||http://ftp.rnl.ist.utl.pt/pub/sabayon/entropy/standard|
repository = sabayon-limbo||ftp://ftp.riken.jp/Linux/sabayon/entropy|
repository = sabayon-limbo||http://mirror.optusnet.com.au/sabayon/entropy|
repository = sabayon-limbo||http://mirror.internode.on.net/pub/sabayon/entropy|
repository = sabayon-limbo||http://cross-lfs.sabayonlinux.org/entropy|
repository = sabayon-limbo||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy|
</pre>}}

Save the file (ctrl-o) and exit the nano editor (ctrl-x).

Now if you want to enable/disable the different repositories, the command is:
{{Console| <pre class="clear"># equo repo enable repository</pre>}}
{{Console| <pre class="clear"># equo repo disable repository</pre>}}

to enable '''daily''':
{{Console| <pre class="clear"># equo repo enable sabayonlinux.org</pre>}}

to enable '''weekly''':
{{Console| <pre class="clear"># equo repo enable sabayon-weekly</pre>}}

and to enable '''limbo''' testing repository:
{{Console| <pre class="clear"># equo repo enable sabayon-limbo</pre>}}

When using [[Rigo]], please see: [[Rigo#Manage_Repositories]]