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

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

Line 138:

Line 138:

Sulfur will no longer exist in the future so [[Rigo]] will be the new and improved GUI package manager for entropy store.

Sulfur will no longer exist in the future so [[Rigo]] will be the new and improved GUI package manager for entropy store.

−

=== Rigo ===

+

=== [[Rigo]] ===

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

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

−

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

+

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

=== Features ===

=== Features ===

Line 271:

Line 271:

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.

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==

+

== 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.

+

+

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.

+

<!-- FIXME: insert equo commands? ('mask' and 'unmask') -->

==Adding Additional Packages Manually==

==Adding Additional Packages Manually==

[https://packages.sabayon.org/ Sabayon Linux Package Repository]

[https://packages.sabayon.org/ Sabayon Linux Package Repository]

−

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

+

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?==

==Fresh Install - What to do?==

Line 326:

Line 330:

# 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).}}<!-- TODO: Better replacing this with kernel switcher? It may be confusing … --~~~~ -->

# 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).}}<!-- TODO: Better replacing this with kernel switcher? It may be confusing … --~~~~ -->

−

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 after that.

+

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.

−

==Upgrading the Linux kernel==

+

==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.

+

+

{{Console|<pre class="clear">

+

$ uname -a

+

$ uname -r

+

$ eselect kernel

+

$ eselect bzimage

+

$ ls /usr/src

+

</pre>}}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, in fact you ARE booting with 3.7.4 (only not showed), and you can assure yourself that it is:

{{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.'''

{{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.'''

Line 357:

Line 394:

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.

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===

+

=== 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.

'''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

+

{{Console| <pre class="clear">

+

# kernel-switcher --help

>> kernel-switcher - Sabayon Linux Kernel Switcher BETA

>> kernel-switcher - Sabayon Linux Kernel Switcher BETA

>> switch kernel: kernel-switcher switch <kernel package>

>> switch kernel: kernel-switcher switch <kernel package>

>> list kernels: kernel-switcher list

>> list kernels: kernel-switcher list

−

>> this help: kernel-switcher help</pre>}}

+

>> 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-2.6.38 is available as an upgrade, you would upgrade to it as follows:

+

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:

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:

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

+

{{Console| <pre class="clear">

+

# eselect opengl list

Available OpenGL implementations:

Available OpenGL implementations:

[1] nvidia *

[1] nvidia *

−

[2] xorg-x11</pre>}}

+

[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:

+

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>}}

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

Line 389:

Line 433:

Another thing to check is the symlink to the kernel:

Another thing to check is the symlink to the kernel:

−

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

+

{{Console| <pre class="clear">

+

# eselect kernel list

Available kernel symlink targets:

Available kernel symlink targets:

−

[1] linux-2.6.37-sabayon

+

[1] linux-3.7.0-sabayon

−

[2] linux-2.6.38-sabayon *</pre>}}

+

[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

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

Line 405:

Line 451:

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

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

−

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

+

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

−

It is also worth running:

+

It is also worth running the both commands:

−

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

+

{{Console| <pre class="clear">

−

+

# equo deptest

−

followed by:

+

# equo libtest

−

+

</pre>}}

−

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

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

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

−

==Using Portage to upgrade the Entropy code==

+

== 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.'''}}

{{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 <4.1 version you need to do the following:

+

We changed the overlay to git now, so for Sabayon Linux version < 4.1 version you need to do the following:

−

(N.B. This step is optional but recommended.)

+

{{Note|This step is optional but recommended.}}

−

{{Console| <pre class="clear"># layman -d sabayon

+

+

{{Console| <pre class="clear">

+

# layman -d sabayon

# layman -d sabayon-distro

# layman -d sabayon-distro

# layman -L

# layman -L

# layman -a sabayon

# layman -a sabayon

−

# layman -a sabayon-distro</pre>}}

+

# layman -a sabayon-distro

+

</pre>}}

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

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

+

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

{{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.

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.

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

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.

+

{{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:

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>}}

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

Hopefully now you are ready to start the upgrading process:

Hopefully now you are ready to start the upgrading process:

+

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

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

−

Before you reboot you should check some things first: [http://forum.sabayonlinux.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.

+

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:

Make sure you also grab the kernel sources:

Line 452:

Line 508:

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.

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:

+

+

{{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:

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

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>}}

+

{{Console| <pre class="clear">

+

# layman --add sabayon

+

# layman --add sabayon-distro

+

</pre>}}

==Hopping Branches==

==Hopping Branches==

−

{{Note|Since branch 5, SabayonLinux became a 'Rolling Release', so 'hopping' is not needed anymore. Just upgrade the system as stated above.

+

{{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.}}

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:

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:

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.sabayonlinux.org/viewtopic.php?f=54&t=16399 for some good learning on things you will need to check.

+

+

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:

Update your config files when done with upgrade:

+

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

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

Before rebooting:

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 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 gcc-config -l and make sure it is on latest one

+

* 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 'binutils-config -l' and make sure it's set

−

-- check eselect opengl list for right driver

+

* check 'eselect opengl list' for right driver

−

-- check /boot/grub/grub.conf to make sure it updated properly

+

* 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

+

* 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.

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

Line 499:

Line 569:

* 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.

* 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.

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.

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.

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:

So after adding that line you can then simply do:

−

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

−

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

+

{{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.

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

=== Adding Entropy Mirror ===

=== Adding Entropy Mirror ===

+

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

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:

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

Revision as of 21:01, 2 April 2013

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.

About Entropy

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.

Installing Entropy

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.

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):

$ su

2. Update the Equo Database:

# equo update

That will update the database to the latest version.

3. Download and install the latest version of Entropy:

# equo install entropy rigo

4. To test it's working, run:

# equo --version

If you get a version number such as:

entropy: 180
equo: 180

Then it has installed and is working!

Installing Entropy using Portage

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):

$ su

2. Update the Sabayon overlays to the latest versions:

# layman --sync sabayon
# layman --sync sabayon-distro

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

# layman --add sabayon
# layman --add sabayon-distro

3. Emerge Entropy, Equo and Rigo to install the latest versions:

# emerge entropy equo rigo

4. To test it's working, run:

# equo --version

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:

# equo cleanup

About Equo, the Commandline package Manager

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:

# equo search <package name>

To install a package use the install function, the --ask amendment is optional but recommended.

# equo install <package> --ask

To remove a package use the remove function as shown below:

# equo remove <package> --ask

To upgrade all your packages to the latest versions use this command:

# equo upgrade --ask

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.

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.

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 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.

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

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):

# equo update

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

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:

# equo repo mirrorsort sabayonlinux.org

For the Weekly repository, use:

# equo repo mirrorsort sabayon-weekly

And for the testing repository, use:

# equo repo mirrorsort sabayon-limbo

Testing repositories:These can break your system, only add them when you really know what you are doing.

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

You can download packages and place them in the package directory for Entropy to use. See 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.

# equo update

If you run into problems with that then try:

# equo update --force

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:

# equo repo mirrorsort sabayon-weekly

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.

# equo install entropy rigo equo --relaxed
# equo conf update

Once the Entropy code is upgraded to the latest version, fully upgrade the rest of your system with these two commands:

# equo update
# equo upgrade --ask

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:

# equo conf update

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:

# equo deptest
# equo libtest

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

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.

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:

# equo install sys-kernel/linux-sabayon-3.7-r3

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:

# equo install x11-drivers/ati-drivers-12.10#3.7.0-sabayon

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.

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:

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:

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:

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.

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

# layman --add sabayon
# layman --add sabayon-distro

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:

# emerge entropy equo rigo

Hopefully now you are ready to start the upgrading process:

# equo upgrade --ask

Before you reboot you should check some things first: 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:

# equo install sabayon-sources

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.

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:

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

# layman --add sabayon
# layman --add sabayon-distro

Hopping Branches

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:

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

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.

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

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:

# equo update
# equo upgrade

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: