From Sabayon Wiki

i18n: ca de en es fr it pl pt ru Tr





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: Mandatory Entropy Update and Wireless KDE 4.4

URL changes for all versions of Sabayon Linux below 5.2: URL Change for Entropy Repository

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.

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.

Entropy for servers and limited-bandwith users

Running Entropy in a server-environment is pretty much the same as for workstations, except for a few things.

On a server you normally don't cleanup your stored packages. (equo cleanup)

Enabling "packages-delta"

When this feature is enabled (when delta packages are available), further package-updates will be downloaded through their .edelta files, saving you a lot of bandwidth.

This means that, when there are updates, only the differences between the packages have to be downloaded.

Thus if the difference is only 400 KB out of a 5 MB package, only the 400 KB is downloaded.

Of course, this only works if you don't cleanup your stored packages., because if "equo cleanup" is run, then the stored binary package (not the installed package)

is removed and then the whole 5 MB will have to be downloaded.

The only downside is that it takes more disc-space.





You can see that users with a limited-bandwith can benefit from this, too.



These settings are controlled by the Entropy configuration file: /etc/entropy/client.conf , so we first need to edit that file, in order to benefit from this.

Open your favourite terminal, switch to root, and edit the file:

nano -w /etc/entropy/client.conf

Scroll down, until you see: packages-autoprune-days = 30 , and change that to:

packages-autoprune-days =

(Thus leaving the parameter empty) This prevents Entropy from automatically cleanup the stored files after "X" days.



Scroll a bit further down, until you see: # packages-delta = ; Uncomment that line by removing the # and change it to:

packages-delta = enable



Now, because we edit this file; the next time you upgrade the system, Entropy wants to revert your settings by asking you to execute equo conf update, and overwrite the file.

Of course we DON'T want that, so select here to keep the old config file.

To prevent that in future upgrades, you can add this file to the files protection list.

Scroll until you find: config-protect-skip = /etc/conf.d/hostname /etc/sudoers /etc/exports, and add this file:

config-protect-skip = /etc/conf.d/hostname /etc/sudoers /etc/exports /etc/entropy/client.conf

Save the file (ctrl-o), and exit the nano editor (ctrl-x)

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 sys-apps/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 in Action

For more information see the Equo main entry

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.

List Of Equo Functions

For a detailed list of the equo functions, you can always enter:

# equo --help

or

# man equo

at the commandline, or view them here: En:List Of Equo Functions

Rigo , the Graphical package Manager

Although still available, Sulfur has been replaced by Rigo

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

enabling a different repository or mirror

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.

To enable a different Repository, add missing example files, and add mirrors that are not listed here;

please read section: En:Repositories



Example how to enable sabayonlinux.org:

# cd /etc/entropy/repositories.conf.d # mv entropy_sabayonlinux.org.example entropy_sabayonlinux.org # equo update

If you later wish to disable this repository:

# equo repo disable sabayonlinux.org

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

# equo update

To add additional repositories, please see: En:Repositories

Testing Branch Limbo

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

Now that you have been warned about the Limbo Testing Repository, but still want to enable it, please see: En:Repositories

Available Repositories mirrors

Production repositories:

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

Note that you can use the following command to optimise the order of the mirrors.

This command pings the mirrors and, based on the response times, orders the mirrors 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.

# Limbo repository = sabayon-limbo|Sabayon Limbo Testing pkg = http://cerberus.itti.ifce.edu.br/entropy pkg = http://pkg.sabayon.org,sabayon.org pkg = http://ftp.nluug.nl/pub/os/Linux/distr/sabayonlinux/entropy pkg = http://ftp.rnl.ist.utl.pt/pub/sabayon ftp://ftp.rnl.ist.utl.pt/pub/sabayon pkg = http://mirror.internode.on.net/pub/sabayonlinux/entropy pkg = ftp://mirror.aarnet.edu.au/pub/SabayonLinux/entropy pkg = http://cross-lfs.sabayonlinux.org/entropy pkg = http://na.mirror.garr.it/mirrors/sabayonlinux/entropy

Community Repositories

For more information see the Community Repositories main entry

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.

to mask a file, see for more information. Use package.unmask to unmask a file. See package.unmask.example for more information.

Adding Additional Packages Manually

Sabayon Linux Package Repository

You can download packages and place them in the package directory for Entropy to use. See Where to Put Packages

Enable debugging symbols

For various reasons you may need debug symbols. They're not provided by default, it takes only little of effort to make them available. Note, that after enabling debug symbols, more disk space will be used. To get them with as little hassle and knowledge possible:

echo 'splitdebug = enabled' >> /etc/entropy/client.conf

After this command you will have to manually reinstall packages you need debug symbols for.

For more knowledge about this, from end of file:

File: /etc/entropy/client.conf # Enable the installation of debug files # Also known as "splitdebug" support # Valid parameters: disable, enable, true, false, disabled, enabled, 0, 1 # Default parameter if unset: disable # splitdebug = enable # HOW SPLITDEBUG WORKS with Entropy # Once you enable the "splitdebug" feature # you just need to (re)install packages in order to # get /usr/lib/debug metadata files installed. That's it. # You can safely remove /usr/lib/debug without affecting # Operating System functionality, at any time.

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 sys-apps/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.

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

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 series, just as 3.8.3 is a update to the 3.8 series.

$ uname -a $ uname -r $ eselect kernel $ eselect bzimage $ ls /usr/src

and even the kernel line in grub.cfg

are ALL using the BASE notation of the kernel, and NOT its updates, that stays "0" , although 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:

# equo query installed "linux-sabayon"

Upgrading the Linux kernel

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

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/nvidia-drivers-375.26-r1#3.7.0-sabayon

If you do not include the "#3.7.0-sabayon" in the package name then, if the nvidia-drivers-375.26-r1 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 same principle applies 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 major version of the kernel, only minor (I.e. 3.12.3 → 3.12.4: YES || 3.12.3 → 3.13.0: NO). To upgrade major version of 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 --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

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:

# 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

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:

# eselect opengl list Available OpenGL implementations: [1] nvidia * [2] xorg-x11

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:

# eselect opengl set 1

Another thing to check is the symlink to the kernel:

# eselect kernel list Available kernel symlink targets: [1] linux-3.7.0-sabayon [2] linux-3.8.0-sabayon *

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

# eselect bzimage list

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

# eselect bzimage set <NUMBER>

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

# eselect bzimage set 2

It is also worth running the both commands:

# equo deptest # equo libtest

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

Using Portage to upgrade the Entropy code

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:

This step is optional but recommended.

# layman -d sabayon # layman -d sabayon-distro # layman -L # layman -a sabayon # layman -a sabayon-distro

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

# equo install dev-vcs/git

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.

# emerge --sync && layman --sync sabayon && layman --sync sabayon-distro

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:

# emerge --sync && layman --sync sabayon && layman --sync sabayon-distro

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:

# equo hop 5

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

# equo update

Always get the latest package manager first:

# equo install entropy equo rigo --relaxed

Now you are ready to start your upgrade:

# equo upgrade

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:

# equo conf update

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

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.