En:Entropy - Revision history

Ryuno-Ki: /* Misunderstandings about the kernel - beautified the code */

2013-04-02T21:01:16Z

‎Misunderstandings about the kernel - beautified the code

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

2013-03-30T18:42:58Z

‎Rigo, the Graphical package Manager

Aposteeltje: /* Rigo */

2013-03-30T18:42:32Z

‎Rigo

Aposteeltje: /* Upgrading the Linux kernel */

2013-03-30T14:08:36Z

‎Upgrading the Linux kernel

Ryuno-Ki: /* Testing Branch / Rolling Releases - code beautified */

2013-03-24T21:07:08Z

‎Testing Branch / Rolling Releases - code beautified

Ryuno-Ki: /* Hopping Branches - fixed some typos */

2013-03-24T20:31:53Z

‎Hopping Branches - fixed some typos

Ryuno-Ki: /* Using Portage to upgrade the Entropy code - put Notes in Note-boxes */

2013-03-24T20:19:38Z

‎Using Portage to upgrade the Entropy code - put Notes in Note-boxes

Ryuno-Ki: /* Using Kernel Switcher - code beautified. FIXME with kernel-switcher and new package naming */

2013-03-21T22:16:00Z

‎Using Kernel Switcher - code beautified. FIXME with kernel-switcher and new package naming

Ryuno-Ki: /* Using Entropy to upgrade all installed packages - FIXME: Replacing Sulfur with Rigo at the end of the subsection? */

2013-03-21T20:29:45Z

‎Using Entropy to upgrade all installed packages - FIXME: Replacing Sulfur with Rigo at the end of the subsection?

Ryuno-Ki: /* Adding Additional Packages Manually - fixed link */

2013-03-21T20:09:17Z

‎Adding Additional Packages Manually - fixed link

@@ Line 345: / Line 345: @@
 Well, let me explain that:
-Every version of the kernel is followed by little updates., called "patchlevel" ., indicated by the third number.
+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.
+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 ,
+{{Console|<pre class="clear">
+$ uname -a
-cat /proc/version,
+$ uname -r
+$ eselect kernel
-eselect kernel and eselect bzimage
+$ eselect bzimage
+$ ls /usr/src
-/usr/src
+</pre>}}and even the kernelline in grub.cfg
-−
 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.
@@ Line 363: / Line 361: @@
 (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.,
+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:
-−
-(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.....
+{{Console|<pre class="clear"># equo query installed "linux-sabayon"</pre>}}
 ===Upgrading the Linux kernel===

@@ Line 129: / Line 129: @@
 [[En:List Of Equo Functions]]
-== Rigo, the Graphical package Manager ==
+== [[Rigo]], the Graphical package Manager ==
 {{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.
-=== Rigo ===
+=== [[Rigo]] ===
 [[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 ===

@@ Line 332: / Line 332: @@
 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==
 {{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 536: / Line 536: @@
 * 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.
 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.
@@ Line 542: / Line 543: @@
 === 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
+ 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 upgrade</pre>}}
+{{Console| <pre class="clear">
 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>}}
+{{File|/etc/entropy/repositories.conf| <pre class="clear">
 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
+{{File|/etc/entropy/repositories.conf| <pre class="clear">
-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>}}
+# repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayonlinux.org/entropy|http://pkg.sabayonlinux.org
 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>}}
+{{File|/etc/entropy/repositories.conf| <pre class="clear">
 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.

@@ Line 491: / Line 491: @@
 ==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.}}
 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.sabayonlinux.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 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.

@@ Line 429: / Line 429: @@
 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.'''}}
-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
 # layman -d sabayon-distro
 # layman -L
 # layman -a sabayon
-# layman -a sabayon-distro</pre>}}
+# layman -a sabayon-distro
 '''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:
-Note: the first emerge --sync is a little time consuming, but it's a one-time deal.
+{{Console| <pre class="clear">
 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.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:
@@ Line 464: / Line 475: @@
 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>}}
+{{Console| <pre class="clear">
 ==Hopping Branches==

@@ Line 361: / Line 361: @@
 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.
-{{Console| <pre class="clear"># kernel-switcher --help
+{{Console| <pre class="clear">
       >> 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>}}
+      >>   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-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:
-{{Console| <pre class="clear"># kernel-switcher switch linux-sabayon-2.6.38
+{{Console| <pre class="clear">
       >>  @@ Calculating dependencies …
-      >>  ## [U] [sabayonlinux.org] sys-kernel/linux-firmwares-2.6.38|0   [2.6.37|0]
+      >>  ## [U] [sabayonlinux.org] sys-kernel/linux-firmwares-3.8.0|0   [3.8.0|0]
-      >>  ## [N] [sabayonlinux.org] sys-kernel/linux-sabayon-2.6.38|0
+      >>  ## [N] [sabayonlinux.org] sys-kernel/linux-sabayon-3.8.0|0
-      >>  ## [N] [sabayonlinux.org] net-wireless/broadcom-sta-5.100.82.38-r1#2.6.38-sabayon|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#2.6.38-sabayon|0</pre>}}
+      >>  ## [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:
-{{Console| <pre class="clear"># eselect opengl list
+{{Console| <pre class="clear">
       Available OpenGL implementations:
       [1]   nvidia *
-      [2]   xorg-x11</pre>}}
+      [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:
+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>}}
@@ Line 393: / Line 400: @@
 Another thing to check is the symlink to the kernel:
-{{Console| <pre class="clear"># eselect kernel list
+{{Console| <pre class="clear">
       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 *
 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 409: / Line 418: @@
 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:
-−
-{{Console| <pre class="clear"># equo deptest</pre>}}
-followed by:
+It is also worth running the both commands:
-{{Console| <pre class="clear"># equo libtest</pre>}}
+{{Console| <pre class="clear">
 This will make sure things are proper.  Once that is complete, reboot to your new kernel.

@@ Line 330: / 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 … --~~~~ -->
-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==

@@ Line 281: / Line 281: @@
 [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?==