Sabayon Wiki - User contributions [en]

File:Sulfur prefs .png

2010-11-18T09:48:45Z

Wolfden:

File:Sulfur config.png

2010-11-18T09:45:11Z

Wolfden:

File:Sulfur repo.png

2010-11-18T09:40:38Z

Wolfden:

File:Sulfur security2.png

2010-11-18T09:34:19Z

Wolfden:

File:Sulfur security.png

2010-11-18T09:30:53Z

Wolfden:

File:Last confirm.png

2010-11-18T08:42:02Z

Wolfden:

File:Updates confirm.png

2010-11-18T08:40:24Z

Wolfden:

File:Updates window.png

2010-11-18T08:34:36Z

Wolfden:

File:Icon load.png

2010-11-18T08:28:24Z

Wolfden: uploaded a new version of "File:Icon load.png"

File:Updates.png

2010-11-18T08:14:13Z

Wolfden:

File:Sulfun undone.png

2010-11-18T07:35:25Z

Wolfden:

File:Sulfur undo.png

2010-11-18T07:32:15Z

Wolfden:

File:Sulfur commit.png

2010-11-18T07:27:55Z

Wolfden:

File:Sulfur queue.png

2010-11-18T07:25:05Z

Wolfden:

File:Sulfur package.png

2010-11-18T07:20:53Z

Wolfden:

File:Sulfur confirm.png

2010-11-18T07:15:30Z

Wolfden:

File:Sulfur select.png

2010-11-18T07:11:55Z

Wolfden:

File:Sulfur install from search.png

2010-11-18T07:06:02Z

Wolfden: uploaded a new version of "File:Sulfur install from search.png"

File:Sulfur advanced.jpg

2010-11-18T06:56:14Z

Wolfden:

File:Sulfur.jpg

2010-11-18T06:53:17Z

Wolfden: uploaded a new version of "File:Sulfur.jpg"

Sulfur GUI

HOWTO: Example of Installing 3rd Party Ebuilds

2010-09-08T06:45:02Z

Wolfden:

{{Warning| '''Portage (emerge) is not the primary package manager for Sabayon, this article is for advanced users only. In other words if this fails for you, its your fault. You have been warned.'''}}
You may run into a really nice piece of software and discover that is it not in portage nor in an overlay. You really want the software and would like the package manager to handle it for easier maintenance. I stress using the package manager for everything. It’s just one of those things you don’t question and follow the proper practices. One of the first things I do is head over to [http://bugs.gentoo.org/ Gentoo’s bugzilla] and see if an ebuild has been submitted. In this scenario I will use [http://code.google.com/p/galaxium/ Galaxium] im software as an example. I jump over to Gentoo bugzilla and presto, someone has already done up the [http://bugs.gentoo.org/show_bug.cgi?id=229645 ebuild]. Now if you’re new to portage you maybe thinking great, but what do I do with these ebuilds. So than we need to look at the gentoo wiki for a guide on [http://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds 3rd party ebuilds]. Let me do a quick walk through of this process. You will need to be root to do this process. Since Galaxium has two ebuilds, we need to create two directory structures, which are:(Note I edited the ebuilds and [http://bugs.sabayonlinux.org/show_bug.cgi?id=459 resubmitted] them to sabayon linux bugzilla so I will be using those one - reason for edit was so I could install it on my 64 bit install.)

In terminal/konsole

su and enter your root password
# mkdir -p /usr/local/portage/dev-dotnet/libanculus-sharp
# mkdir -p /usr/local/portage/net-im/galaxium

How do you know what to name the directories? You want to follow the [http://gentoo-portage.com/Browse proper categories layout that Gentoo uses].

First thing we need to do is make sure your /etc/make.conf has the correct line in it so it can find your custom ebuilds. Simply add:
PORTDIR_OVERLAY="${PORTDIR_OVERLAY} /usr/local/portage/"
to it if it’s not there.

Than we need to get the ebuilds into the directories and digest them so we can install them, let’s start with libanculus-sharp first:

# cd /usr/local/portage/dev-dotnet/libanculus-sharp << changes u to the correct directory >>
# wget -O libanculus-sharp-0.3.1.ebuild http://bugs.sabayonlinux.org/attachment.cgi?id=53 << will get the ebuild and put it in the directory >>
# ebuild libanculus-sharp-0.3.1.ebuild manifest << prepares the ebuild for install >>

You will notice when you digest a file it will retrieve the files from the internet it needs and place them into your /usr/portage/distfiles Now you can emerge your ebuild by:

# emerge libanculus-sharp

Now we can do Galaxium:

# cd /usr/local/portage/net-im/galaxium
# wget -O galaxium-0.7.3.ebuild http://bugs.sabayonlinux.org/attachment.cgi?id=52
# ebuild galaxium-0.7.3.ebuild manifest
# emerge galaxium

Pretty painless and now your ebuild is there to stay and it’s easy to [http://gentoo-wiki.com/HOWTO_Create_an_Updated_Ebuild maintain when a new version comes out]. Now you maybe thinking what do I do if I can’t find an ebuild for the software I want. Well you can [http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=1 learn how to make an ebuild] or use the [http://bugs.sabayonlinux.org/ sabayonlinux bugzilla] and request an ebuild and maybe some kind package maintainer will build it and put it in the overlay for you. You can [https://answers.launchpad.net/sabayonlinux/+addquestion request a package for Entropy package manager also]. The above method works great tho if you can’t wait for a package or even an updated version to get into an overlay or portage.

''Please note this package is now officially in the Sabayon Linux overlay.''

[[Category:Package Management|Example of Installing 3rd Party Ebuilds]]

HOWTO: Install FrostWire

2010-06-30T23:13:45Z

Wolfden: New page: Getting FrostWire to work on Sabayon Linux has been a frustration up until now. By following the steps below you'll have FrostWire working in a matter of minutes. {{Note| Be sure to run '...

Getting FrostWire to work on Sabayon Linux has been a frustration up until now. By following the steps below you'll have FrostWire working in a matter of minutes.

{{Note| Be sure to run '''emerge --sync && layman -S''' before proceding.}}

'''Step 1.'''
In a terminal, become root.
{{Console| <pre class="clear">su</pre>}}
Enter your root password when prompted.

'''Step 2.'''
Emerge Sun's Java.
{{Console| <pre class="clear"># emerge sun-jre-bin</pre>}}

'''Step 3.'''
Emerge FrostWire.
{{Console| <pre class="clear"># emerge frostwire-bin</pre>}}

'''Step 4.'''
These steps are borrowed from the [http://www.sabayonlinux.org/forum/viewtopic.php?f=53&t=9882 Compiz-Fusion Update Guide].
{{Console| <pre class="clear"># echo "x11-libs/libX11 xcb" >> /etc/portage/package.use
# emerge x11-libs/libX11
# CFLAGS="-DNDEBUG" emerge x11-libs/libxcb</pre>}}

'''Step 5.'''
Make the FrostWire run script executable.
{{Console| <pre class="clear"># chmod +x /usr/share/frostwire/runFrostwire.sh</pre>}}

'''Step 6.'''
Click on the FrostWire entry in your menu, or just type "frostwire" (no quotes) in your console (as a regular user) and hit enter. It should work now.

File:Portage.png

2010-06-30T22:05:49Z

Wolfden:

File:Kdevt8.png

2010-04-01T02:50:47Z

Wolfden:

File:Kdevt7.png

2010-04-01T02:50:21Z

Wolfden: uploaded a new version of "Image:Kdevt7.png"

File:Kdevt6.png

2010-04-01T02:49:41Z

Wolfden: uploaded a new version of "Image:Kdevt6.png"

File:Kdevt5.png

2010-04-01T02:49:15Z

Wolfden: uploaded a new version of "Image:Kdevt5.png"

File:Kdevt4.png

2010-04-01T02:48:53Z

Wolfden: uploaded a new version of "Image:Kdevt4.png"

File:Kdevt3.png

2010-04-01T02:48:15Z

Wolfden: uploaded a new version of "Image:Kdevt3.png"

File:Kdevt2.png

2010-04-01T02:47:55Z

Wolfden: uploaded a new version of "Image:Kdevt2.png"

File:Kdevt.png

2010-04-01T02:47:37Z

Wolfden: uploaded a new version of "Image:Kdevt.png"

File:Gnomevt8.png

2010-04-01T02:29:08Z

Wolfden: uploaded a new version of "Image:Gnomevt8.png"

File:Gnomevt7.png

2010-04-01T02:28:39Z

Wolfden: uploaded a new version of "Image:Gnomevt7.png"

File:Gnomevt6.png

2010-04-01T02:28:14Z

Wolfden: uploaded a new version of "Image:Gnomevt6.png"

File:Gnomevt5.png

2010-04-01T02:27:49Z

Wolfden: uploaded a new version of "Image:Gnomevt5.png"

File:Gnomevt4.png

2010-04-01T02:27:26Z

Wolfden: uploaded a new version of "Image:Gnomevt4.png"

File:Gnomevt3.png

2010-04-01T02:26:29Z

Wolfden:

File:Gnomevt2.png

2010-04-01T02:25:26Z

Wolfden: uploaded a new version of "Image:Gnomevt2.png"

File:Gnomevt.png

2010-04-01T02:25:00Z

Wolfden: uploaded a new version of "Image:Gnomevt.png"

Known Issues

2010-03-16T22:01:08Z

Wolfden: /* 02/12/10 Mandatory Entropy Update and Wireless KDE4.4 */

==03/16/10 URL Change for Entropy Repository==
Please see this topic http://forum.sabayon.org/viewtopic.php?f=76&t=17144&sid=0223fbd47ed1bc0ccd777fdcdce290f3 it has a working repository config file. This effects all versions pre 5.2

==02/12/10 Mandatory Entropy Update and Wireless KDE4.4==
Wireless issues after KDE 4.4 update
Friday, February 12, 2010 5:37 AM
With KDE 4.4, we had to drop the old Plasma-based Network Manager tool, you must install knetworkmanager or nm-applet (GNOME)

Entropy update required
Friday, February 12, 2010 5:34 AM
If you are having download problems, they may be caused by your Entropy version not up-to-date. You can solve this by updating Entropy this way: equo update && equo install entropy equo --nodeps && equo upgrade

==10/14/09 Slow Speeds with Limbo Repo==
You may notice a big slow down with entropy and Limbo Repo, please add this mirror under your existing Limbo line
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayonlinux.org/entropy|http://pkg.sabayonlinux.org
so it should look like
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

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

# 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

Another thing you can do is make it look like:
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|
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.

==9/8/09 Gnome 5.0 and jpg==
Gnome 5.0 having jpg issues - fix is to reinstall gtk+
#equo install gtk+

also run as user
$ update-mime-database ~/.local/share/mime/

==8/3/09 Late Bugs Fixes==
Make sure before you install 5.0 that you run the Update Installer. The button is found by launching the Install to Disk. It will download the latest fixes and restart the install process.

==6/20/09 Mibbit WebChat==
Freenode had banned mibbit, which is the webchat that we had been using for Live Help. Please use an irc client to connect to live help or you can use the [http://webchat.freenode.net/ Freenode webchat] - channel #Sabayon

==4/29/09 Adding Users==
[http://forum.sabayonlinux.org/viewtopic.php?f=86&t=16777 Please see this thread on kuser and gnome user]
I find doing the command line method the easiest
# useradd -m -G users,wheel,audio -s /bin/bash john
# passwd john
Password: (Enter the password for john)
Re-enter password: (Re-enter the password to verify)

Fitzcarraldo recommends [http://wiki.vpslink.com/HOWTO:_Gentoo_Primer_-_Post-Installation_Steps#Superadduser Superadduser] - [http://www.sysadmin.md/wp-content/uploads/2008/04/superadduser.png screenshots]

==3/29/09 Grub Issue==

Getting reports that Grub issues are hitting a lot of people also, luckily you have some options.

1. The livedvd that you used to install with has in the installer an option to just reinstall grub, so boot up the livedvd, run the installer till you get to reinstall boot loader.

2. I highly recommend Super Grub Disk, it's a wonderful tool to restore Grub, saves a lot of headaches http://www.supergrubdisk.org/ Download the iso, burn it, boot it up, fix, reboot. Keep it safe as you will probably use it again.

3. Advanced users can chroot in and reinstall grub - dave_64, one of the IRC helpers says the archlinux wiki is good guide for this http://wiki.archlinux.org/index.php/Reinstalling_GRUB << he said he never chrooted before and was able to by following that guide.

I'm not sure what the prevention for this is, common sense tells me to reinstall grub before rebooting. I have a different grub so I can't test this out. I'm guessing the grub-install command

# grub-install /dev/sda

==3/27/09 Entropy Wiki Addition==
http://wiki.sabayonlinux.org/index.php?title=En:Entropy#Fresh_Install_-_What_to_do.3F

hopefully this will help people get started with the entire process

==3/25/09 ext4 with kernel .29==
We have a new issue now with 2.6.29

If you upgrade to kernel 2.6.29 and have ext4, you have to edit you /etc/fstab file and remove the extents option as it is now default
so you will have a line like

/dev/sdb8 / ext4 extents,user_xattr,noatime 1 1

THIS IS WRONG NOW

You need to change it so it looks like:

/dev/sdb8 / ext4 user_xattr,noatime 1 1

THIS IS CORRECT

if you don't remove the extents option, your system will be stuck in Read Only mode and nothing will start up, you will have to reboot to the previous kernel to edit the /etc/fstab file than reboot back to .29

==3/21/09 Update Information==
We are seeing plenty of people having problems with updates as they don't realize what happens when there is a kernel change.

Remember when you change kernels - your modules/drivers must match new kernel.

For example - I upgrade and before I reboot I want to make sure of a few things

wolf64 wolfden # uname -r
2.6.28-sabayon

oh look, I has a new kernel now, Did my nvidia-driver update? Probably not, but I can use

# equo search nvidia-driver

to see what I do have installed - x11-drivers/nvidia-drivers-96.43.09-r10#2.6.27-sabayon << DO NOT WANT

let's make sure my kernel is eselected first - if it isn't than it is pointless to rebuild modules as you would be building on the wrong kernel

wolf64 wolfden # eselect kernel list
Available kernel symlink targets:
[1] linux-2.6.27-sabayon
[2] linux-2.6.28-sabayon *

sweet, it is eselected to the right kernel, if it wasn't I would have had to eselect kernel set 2

so I better

# equo install nvidia-driver

to get x11-drivers/nvidia-drivers-180.41-r1#2.6.28-sabayon << DO WANT

now lets make sure eselect is point to right opengl

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

woot! and it is set to my nvidia, if it wasn't, I would of had to eselect opengl set 1

2.6.28-sabayon and x11-drivers/nvidia-drivers-180.41-r1#2.6.28-sabayon

Notice my Kernel matches my driver to same kernel version. This is critical, otherwise you are gonna boot up to a blinking cursor and run around screaming I Need Support!!!

This is not just an entropy or Sabayon Linux thing. Every time you change kernel in a distro you must rebuild the drivers/modules to work with your new kernel. This includes all hardware like cams, video, any thing that is a module.

and always always always

# equo conf update

and deal with the config files, you should look over this list and pay attention, most of time -5 is going to work fine, but if you suddenly boot to a different login manager, than you know you overwrote a config file you shouldn't of like /etc/conf.d/xdm, some others I do not over write are /etc/conf.d/hostname and /etc/conf.d/hwclock, there is a couple others but I'm not going to list em all, you should get to know our config files

===Udev Issue===

We are seeing some weird thing with udev being removed from startup and this is bad bad bad, so before rebooting, make sure udev is in your startup by doing
wolf64 wolfden # rc-update show
system-tools-backends | default
mount-ro | shutdown
sshd | default
dmesg | sysinit
hotplug | boot
serial | boot
x-setup | boot
keymaps | boot
syslog-ng | default
mdadm | default
local | nonetwork default
portmap | default
udev | sysinit
hwclock | boot
termencoding | boot
fbcondecor | default
savecache | shutdown
sabayon-mce | boot
fsck | boot
consolefont | boot
swap | default
root | boot
dbus | boot
NetworkManager | default
modules | boot
devfs | sysinit
xdm | boot
vixie-cron | default
mtab | boot
samba | default
sysctl | boot
device-mapper | boot
alsasound | default
avahi-daemon | default
killprocs | shutdown
procfs | boot
hald | boot
localmount | boot
netmount | default
cupsd | default
hostname | boot
nfs | default
net.lo | boot
dhcdbd | default
urandom | default
lvm | boot
bootmisc | boot

Look for udev and if you don't see it

# rc-update add udev sysinit

if you reboot without udev starting, you won't get far as everything is going to fail and you will than be reading chrooting 101 to save your install

===Networking Issue===

Another thing with Networking breaking:

http://forum.sabayonlinux.org/viewtopic.php?f=52&t=16007

http://forum.sabayonlinux.org/viewtopic.php?f=52&t=16086

Hopefully in the future as entropy develops, some of these concerns will be address and make things even smoother for ya. Fabio is always making it better and easier for you, but in the meantime, keep these things in mind when you see a kernel change. Knowledge is power and the more you know what is changing in your system the better.

HOWTO: Get 64bit Sun Java Working in Firefox

2009-12-04T08:05:14Z

Wolfden:

https://jdk6.dev.java.net/plugin2/

1.
equo remove emul-linux-x86-java
2.
equo remove icedtea

if you use portage - use emerge -C in replace of equo remove

3.
emerge sun-jdk

4.
java-config --set-system-vm sun-jdk-1.6

so that java-config --list-available-vms shows:
*) Sun JDK 1.6.0.12_beta2 [sun-jdk-1.6]

5. set the plugin

eselect java-nsplugin set 64bit sun-jdk-1.6

so that eselect java-nsplugin list shows:

Available 32-bit Java browser plugins

Available 64-bit Java browser plugins

[1] sun-jdk-1.6 current

Head on over to http://www.javatester.org/version.html

why this over icetea? some are reporting it works on more sites than icetea. It's worked on all sites I tested it on, sometimes I have to hit the refresh page button twice, but it works.

[http://forum.sabayonlinux.org/viewtopic.php?f=5&t=15448&p=88386#p88386 Forum Discussion]

File:Installk21.png

2009-10-03T08:44:41Z

Wolfden: uploaded a new version of "Image:Installk21.png"

File:Installk20.png

2009-10-03T08:44:20Z

Wolfden: uploaded a new version of "Image:Installk20.png"

File:Installk19.png

2009-10-03T08:44:00Z

Wolfden: uploaded a new version of "Image:Installk19.png"

File:Installk18.png

2009-10-03T08:43:02Z

Wolfden: uploaded a new version of "Image:Installk18.png"

File:Installk17.png

2009-10-03T08:42:38Z

Wolfden: uploaded a new version of "Image:Installk17.png"

File:Installk16.png

2009-10-03T08:42:20Z

Wolfden: uploaded a new version of "Image:Installk16.png"

File:Installk15.png

2009-10-03T08:41:26Z

Wolfden: uploaded a new version of "Image:Installk15.png"

File:Installk13.png

2009-10-03T08:38:16Z

Wolfden: uploaded a new version of "Image:Installk13.png"

File:Installk12.png

2009-10-03T08:36:36Z

Wolfden: uploaded a new version of "Image:Installk12.png"

File:Installk11.png

2009-10-03T08:33:58Z

Wolfden: uploaded a new version of "Image:Installk11.png"