Sabayon Wiki - User contributions [en]

HOWTO: Upgrade kernel using genkernel

2013-05-04T02:11:48Z

Fitzcarraldo: change grub-mkconfig to grub2-mkconfig as recently the former has resulted in error messages (see recent forum thread).

{{I18n| [[HOWTO:_Upgrade_kernel_using_genkernel|en]] [[Es:COMO:_Actualizar_el_kernel_usando_genkernel|es]] [[Pl:HOWTO:_Aktualizacja_kernela_z_wykorzystaniem_genkernel|pl]]}}
{{Warning| This how-to is for the Portage package manager. Please use the Entropy package manager if you are not familiar with Portage.}}

{{Warning| Before actually performing any of the commands listed below, read through the entire article and WARNING No. 1 at the end, as it may alter what commands you use.}}

Open a Konsole/Terminal window and use the su command to log in as the root user.

'''If''' you have a separate boot partition, make sure it is mounted onto /boot before proceeding. For example, if the boot partition is /dev/sda3 then:

{{Console| <pre class="clear"># mount /dev/sda3 /boot</pre>}}

'''Update portage and genkernel first, then install the newest kernel source code:'''

{{Console| <pre class="clear"># emerge --sync && layman -S</pre>}}
{{Console| <pre class="clear"># emerge genkernel</pre>}}
{{Console| <pre class="clear"># USE="sources_standalone" emerge sabayon-sources</pre>}}

{{Note|'''Note 1:''' There's no need to merge genkernel if the latest version is already installed.}}

{{Console| <pre class="clear"># eselect kernel list</pre>}}
Note which kernel in the list you want to install. It has a number like this next to it: [x]. More than likely x = 2 [2]. Now use this number in the following command, in order to set the symlink to the new version of the kernel:
{{Console| <pre class="clear"># eselect kernel set x </pre>}}
{{Console| <pre class="clear"># zcat /proc/config.gz > /usr/src/config </pre>}}

{{Note|'''Note 2:''' If you are just making some changes to the same version of kernel and rebuilding it then using the zcat command is probably appropriate. However if you are upgrading or downgrading to a different version of kernel then the zcat command is probably not appropriate. See WARNING No. 1 at the end of this article for what to do in the latter case.}}

'''Do the following if you manually edited your partitions:'''

{{Console| <pre class="clear"># genkernel --kernel-config=/usr/src/config --menuconfig --splash=sabayon --disklabel --luks all</pre>}}

'''Do the following if you used anaconda's automatic diskdruid or created a lvm:'''

{{Console| <pre class="clear"># genkernel --kernel-config=/usr/src/config --menuconfig --splash=sabayon --disklabel --lvm --luks all</pre>}}

{{Note|'''Note 3:''' If you get an error about an expected integer expression on line 96 of gen_funcs.sh, you will most likely need to update your config files. I used etc-update and selected the second option (-5).}}

{{Note|'''Note 4:''' If you have an older version of genkernel, for example 3.4.7-x, replace "--lvm" with "--lvm2" and "--splash" with "--gensplash".}}

{{Note|'''Note 5:''' If you want to be able to use a UUID for real_root in grub.conf then include "--disklabel". Otherwise you can omit the "--disklabel" (which I normally do).}}

{{Note|'''Note 6:''' "--disklabel" is needed if, after you have built the kernel and reboot, mounting of the root partition fails and you see an error message "blkid: not found". See Gentoo Bugzilla Report No. 229847 for more details. Alternatively, edit grub.conf and make real_root point to the file name of the root partition (/dev/sda5 or whatever) rather than to the root partition's UUID.}}

{{Note|'''Note 7:''' "--luks" is only needed if you want LUKS support for disk encryption.}}

When you get into the linux kernel menu where you can go and edit all sorts of linux kernel variables (and it's very tempting to mess with), unless you are very, VERY well versed in understanding what it is you are doing, the default settings are '''good and reliable''' to start with and will create a kernel that actually WORKS.

SO, you can simply exit and save without changing anything, this way your kernel will compile and you can actually boot into it.

'''Then we need to rebuild our modules and such to make sure everything works with the new kernel. So do:'''

{{Console| <pre class="clear"># module-rebuild rebuild</pre>}}

'''Sometimes this will fail if old modules are still around, so you might need to re-emerge your video drivers'''

I had to re-emerge my nvidia drivers because the old drivers were no longer in the portage tree:

{{Console| <pre class="clear"># emerge nvidia-drivers</pre>}}

OR, if you have an ATI GPU:

{{Console| <pre class="clear"># emerge ati-drivers</pre>}}

and if it says that ati-drivers-<version> is unavailable, try:
{{Console| <pre class="clear"># module-rebuild del ati-drivers-<version> </pre> }}
If you still have problems, you can clean-out and renew your moduledb first like this:
{{Console| <pre class="clear"># rm /var/lib/module-rebuild/moduledb
# module-rebuild populate
# module-rebuild rebuild</pre>}}
Note that the latest kernel has built-in wireless stuff, causing the wireless modules to fail the module-rebuild. The trick is to make sure the wireless stuff is enabled during the kernel compile.

Currently genkernel only knows about Grub Legacy, so you will need to regenerate the Grub2 grub.cfg file after completing the above, using the following command:

{{Console| <pre class="clear"># grub2-mkconfig -o /boot/grub/grub.cfg</pre>}}

Any questions/problems/comments can be posted on the forums.

Now, reboot.

Choose to boot into your freshly compiled kernel, the old reliable one will still be there and may be a nice backup for safe keeping so, don't worry about getting rid of it.

There you have it. It will take some time, but it's good.

'''Unsupported kernels'''

For other unsupported kernels, please have a look at [http://forums.gentoo.org/viewforum-f-51.html?sid=7501d92f6d58ea97b587da5f80918293 the unsupported software section at the Gentoo forums.]

Most unsupported kernels are in the custom-kernels overlay which is accessible with Layman.

{{Console| <pre class="clear"># layman -a custom-kernels</pre>}}

-------

'''WARNING No. 1''': Think carefully about what you are trying to achieve here, i.e. do you want to upgrade to a newer version of the kernel or do you want to rebuild the same version of the kernel you are currently using (perhaps, optionally, making some manual changes to the kernel configuration)? Note that the zcat command mentioned above creates a configuration file based on '''the currently-running kernel'''. However, the configuration of the current kernel may not be suitable for the new version of the kernel sources you just merged (downloaded). It could be that you want or need to use a configuration file for the new version of kernel you have just merged. To give a hypothetical example in order to try and illustrate the distinction, let's suppose you are currently running the 2.6.22 kernel but now want to build the 2.6.25 kernel. In which case you would not need to bother with the zcat command as some of the configuration parameters in the 2.6.22 kernel do not exist in the 2.6.25 kernel (and vice versa), so instead of using a file /usr/src/config you could create using zcat, you would instead use the .config file (notice the dot) in the directory /usr/src/linux-2.6.25-sabayon/ created when you merged linux-sabayon-2.6.25 earlier, which is different from the .config file (and config file created by zcat) for the 2.6.22 kernel. In other words, you would instead use the command:

{{Console| <pre class="clear"># genkernel --kernel-config=/usr/src/linux-2.6.25-sabayon/.config --menuconfig --bootloader=grub --splash=sabayon --disklabel all</pre>}}

(or

{{Console| <pre class="clear"># genkernel --kernel-config=/usr/src/linux-2.6.25-sabayon/.config --menuconfig --bootloader=grub --splash=sabayon --disklabel --lvm all </pre>}}

if you used anaconda's automatic diskdruid or created a lvm.)

Notice the difference between "--kernel-config=/usr/src/config" ( the file "config" would be created by using the zcat command) and "--kernel-config=/usr/src/linux-2.6.25-sabayon/.config" (the file ".config" would be created when you merge linux-sabayon-2.6.25).

Note also that the file /usr/src/linux-2.6.25-sabayon/.config would be the same as the file /usr/portage/local/layman/sabayon/sys-kernel/linux-sabayon/files/linux-sabayon-2.6.25-x86.config if you merged linux-sabayon-2.6.25 for the x86 edition of Sabayon Linux, or the file /usr/portage/local/layman/sabayon/sys-kernel/linux-sabayon/files/linux-sabayon-2.6.25-amd64.config if you merged linux-sabayon-2.6.25 for the x86_64 edition of Sabayon Linux. Thus, if you run one of the above commands and an error message is displayed to the effect that /usr/src/linux-2.6.25-sabayon/.config cannot be opened, then try using --kernel-config=/usr/portage/local/layman/sabayon/sys-kernel/linux-sabayon/files/linux-sabayon-2.6.25-x86.config (or /usr/portage/local/layman/sabayon/sys-kernel/linux-sabayon/files/linux-sabayon-2.6.25-amd64.config if you have the 64-bit edition of SL installed). Note also that the default location of the Portage overlay sources has been changed from directory /usr/portage/local/layman/ to directory /usr/local/portage/layman/ in the latest version of SL (and Gentoo), so modify the aforementioned command accordingly if you are using SL 4.0 and onwards. For example, in the case of the 2.6.31 kernel the switch would be the following for the x86 edition:

{{Console| <pre class="clear">--kernel-config=/usr/local/portage/layman/sabayon/sys-kernel/linux-sabayon/files/linux-sabayon-2.6.31-x86.config </pre>}}

and the following for the x86_64 edition:

{{Console| <pre class="clear">--kernel-config=/usr/local/portage/layman/sabayon/sys-kernel/linux-sabayon/files/linux-sabayon-2.6.31-amd64.config </pre>}}

{{Note|'''Note 8:''' In SL 5.2 and onwards (Layman 1.3.0 and onwards), replace "/usr/local/portage/layman/" with "/var/lib/layman/" in the text above.}}

{{Note|'''Note 9:''' Use "/usr/portage/distfiles/sabayon-2.6.34-amd64.config" instead of "/var/lib/layman/sabayon/sys-kernel/linux-sabayon/files/linux-sabayon-2.6.34-amd64.config" (replace "amd64" with "x86" for x86) for kernel 2.6.34 and onwards.}}

{{Note|'''Note 10:''' The location of the .config file changed again for kernel 3.0.0 (and possibly earlier). Rather than adding notes here ad infinitum, please use the '''locate''' command (install '''mlocate''' if not already installed) to find the .config file.}}

[[Category:Installation]]

Talk:De:Main Page

2012-01-14T06:59:19Z

Fitzcarraldo:

Hier ist eine URL encoding Referenz. 
Leider greift der Spamschutz etwas zu gut und so muss man manchmal ein wehnig improvisieren. 
Das funktioniert allerdings nicht im Artikeltext ... )= 
[Fitzcarraldo wrote] Thanks, Yokmp. I've removed the link from this Discussion page, though, as it is still a spam link here! 
[[User:Yokmp|yokmp]] 06:29, 11 January 2012 (CET)

HOWTO: Read Microsoft Outlook .MSG files in Linux

2011-12-31T00:02:19Z

Fitzcarraldo: Reverted edits by Vinodpcvita (Talk) to last revision by Fitzcarraldo

'''How to read Microsoft Outlook .MSG files in Linux'''

I have literally thousands of .MSG files which I saved from Outlook Exchange Server several years ago and now want to access under Linux. However Linux e-mail clients cannot read or import Microsoft Outlook .MSG files or .PST files. Nope, not even Evolution, KMail or Thunderbird. At least with .PST files one could import them into Microsoft Outlook Express, export them in MBOX format and then import them into Evolution, KMail or Thunderbird.

But with Outlook .MSG files a guy named Matijs van Zuijlen came to the rescue with a Perl utility he calls "MSGConvert: A .MSG to mime/mbox converter". You can read about installing and using it on his Web site (http://www.matijs.net/software/msgconv/) but I thought I'd explain here how to install and use it, as his instructions may be confusing to newcomers to Linux and/or Perl.

'''1. Installation'''

Run the following commands when connected to the Internet, to download and install certain Perl modules and their dependencies from CPAN (Comprehensive Perl Archive Network):

{{Console| <pre class="clear">
perl -MCPAN -e 'install("Email::Outlook::Message")'
perl -MCPAN -e 'install("Email::LocalDelivery")'
perl -MCPAN -e 'install("Getopt::Long")'
perl -MCPAN -e 'install("Pod::Usage")'
perl -MCPAN -e 'install("File::Basename")'
</pre>}}
Then download the Perl script msgconvert.pl (see the link "script itself" near the bottom of the above-mentioned Web page). I would suggest saving the script in your home directory.

'''2. Using MSGConvert'''

If the Microsoft Outlook .msg file you want to convert is called test_message.msg then you would type the following at the command line (not as root):

{{Console| <pre class="clear">
perl -w ~/msgconvert.pl ~/test_message.msg
</pre>}}
and the file ~/test_message.msg.mime will be created.

If KMail does not open the .mime file, do the following:

a) select K Menu > Control Centre > KDE Components > File Associations

b) click on the "+" next to "message" to expand it

c) select rfc822

d) On the General tab, under Filename Patterns click on Add and add *.mime to the box and click Apply.

Notes for newcomers to Linux:
1. The tilde means "your home directory". So in my case I can type either "~/test_message.msg" or "/home/fitzcarraldo/test_message.msg".
2. Linux is case-sensitive, and test_message.msg and test_message.MSG are two different file names as far as Linux is concerned.

Article created by Fitzcarraldo on 30 April 2008.

Tr:HOWTO: Changing the hostname

2011-11-01T15:41:18Z

Fitzcarraldo: Reverted edits by Janwalls (Talk) to last revision by Hatalar205

{{I18n| [[Tr:HOWTO: Changing the hostname|tr]]}}

'''Sabayon Linux çalışan bir bilgisayarda HOSTNAME değiştirme'''

{{Note|Aşağıdaki örnekte hostname olarak "acertm8215" i kullandım çünkü Acer TravelMate8215 dizüstüm var, ama açıkcası siz istediğiniz herhangi bir hostname i kullanabilirsiniz.}}

Sabayon Liux kurulumu sırasında "localhost" öntanımlı hostname i kabul etmiş olabilirsiniz, veya hostname adınızı (ör. "sabayonx86", "neptune" veya herneise) olarak özelleştirmiş olabilirsiniz. Her iki durumda da, bir şekilde şuanki hostname nizi değiştirmek isteyebilirsiniz, bu makale nasıl yapacağınızı açıklar.

1. Şuanki hostname nizin doğru ayarlandığını kontrol edin

{{Console| <pre class="clear">uname -a</pre>}}

{{Console| <pre class="clear">hostname</pre>}}

{{Console| <pre class="clear">hostname -f</pre>}}

{{Console| <pre class="clear">hostname -a</pre>}}

{{Console| <pre class="clear">hostname -d</pre>}}

2. /etc/conf.d/hostname i düzenleyin

Değiştirin:

{{File|/etc/conf.d/hostname| <pre class="clear">HOSTNAME="localhost"</pre>}}

buna değiştirin:

{{File|/etc/conf.d/hostname| <pre class="clear">HOSTNAME="acertm8215"</pre>}}

3. /etc/hosts düzenleyin

Değiştirin:

{{File|/etc/hosts| <pre class="clear">127.0.0.1 localhost localhost.localdomain localhost</pre>}}

buna değiştirin:

{{File|/etc/hosts| <pre class="clear">127.0.0.1 acertm8215 localhost.localdomain localhost</pre>}}

4. Kernelde bulunan hostname i değiştirin

Şuanki hostname i görmek için:

{{Console| <pre class="clear">sysctl kernel.hostname</pre>}}

Mevcut hostname i değiştirmek için:

{{Console| <pre class="clear">sysctl kernel.hostname=acertm8215</pre>}}

5. /etc/samba/smb.conf dosyasındaki netbios adını değiştirin (çünkü öntanımlı olaral hostname "localhost" dır)

Değiştirin:

{{File|/etc/samba/smb.conf| <pre class="clear">netbios name = localhost</pre>}}

buna değiştirin:

{{File|/etc/samba/smb.conf| <pre class="clear">netbios name = acertm8215</pre>}}

6. /etc/dhcp/dhclient.conf dosyasındaki hostname i değiştirin (aksi takdirde bilgisayarınızın bağlandığı diğer ağ bağlantılarına hala eski hostname i bildirecektir):

Değiştirin:

{{File|/etc/dhcp/dhclient.conf|<pre class="clear">
send host-name "localhost";
supersede host-name "localhost";
</pre>}}

buna değiştirin:

{{File|/etc/dhcp/dhclient.conf|<pre class="clear">
send host-name "acertm8215";
supersede host-name "acertm8215";
</pre>}}

{{Note|Yukarıdakiler dhclient in bilgisayarınızdaki çalışan DHCP istemcisi olduğunu farz eder (çünkü dhclient Sabayon Linux'un öntanımlı olarak kullandığı DHCP istemcisidir). Ama, farklı bir DHCP istemcisi kulanmaya kara verdiyseniz (ör. dhcpcd) farklı bir dosyayı düzenlemeniz gerekecek.}}

7. Yeniden başlatın (veya ağı yeniden başlatın).

8. Yeni hostname in doğru olarak atandığından emin olmak için Adım 1'i tekrarlayın.

8 Ocak 2009 'de Fitzcarraldo tarafından yazılmıştır.

HOWTO: Belkin wireless g usb network adapter F5D7050

2011-09-22T01:10:39Z

Fitzcarraldo: Removed reference to an article that no longer exists on the Web. Tidied up a bit. Changed to follow SL Wiki editing guidelines.

Thought I would offer this brief 'how to' on setting this device up. It comes with a USB Wireless G stick and also a base station that you could use to move the USB stick around. The cable on the base is about 8 - 10 feet long. The stick works with or without the base.

This device is a relatively cheap USB Wireless G pen/stick - you can get them for circa US$40 and mine has a great signal strength sitting 6 rooms away (about 200 feet) from an access point. You can get one from an on-line store even (e.g. http://www.nextdaypc.com/main/products/details.aspx?pid=1912738&rsmainid=ND0011694&).

It can use 2 different modules depending on the FCC ID:
K7SF5D7050A - rt2500
K7SF5D7050B - rt73

The modules are in Portage. However, I couldn't get it to work with the ones included on the Sabayon Linux 3.2 LiveDVD, and lsmod would actually show both the rt2500 and rt73 modules loaded. I tried for about 3 hours to get it to work with the one for my card, which uses the rt73 module.

The modules are also available at http://rt2x00.serialmonkey.com

This brief howto covers the rt73 setup.

Download the daily cvs from the above address - rt73-cvs-daily.tar.gz

Extract it:
{{Console| <pre class="clear">$ tar xzfvp rt73-cvs-daily.tar.gz</pre>}}

Remove the ones that are in Portage:
{{Console| <pre class="clear"># emerge -C rt2500
# emerge -C rt73
# emerge -C rt73-firmware</pre>}}

Remove the leftover modules in your kernel modules directory. Since I am still running 2.6.18-gentoo-4, mine are at:
{{Console| <pre class="clear"># rm /lib/modules/2.6.18-gentoo-r4/net/rt2500.ko
# rm /lib/modules/2.6.18-gentoo-r4/net/rt73.ko</pre>}}

Change to the directory you extracted the daily cvs:
{{Console| <pre class="clear"># cd rt73*/Module</pre>}}

Make and make install:
{{Console| <pre class="clear"># make && make install</pre>}}

Edit the file /etc/modules.d/rt73 and change it to:
{{Console| <pre class="clear">#alias usbra? rt73
alias ra0 rt73</pre>}}

Run modules-update force:
{{Console| <pre class="clear"># modules-update force</pre>}}

Load the module:
{{Console| <pre class="clear"># modprobe rt73</pre>}}

Now, run the command iwconfig and it should show something about rausb0 but it wont have an IP address yet.
{{Console| <pre class="clear"># iwconfig</pre>}}

create the net.rausb0 by linking it to net.eth0 in the init.d directory:
{{Console| <pre class="clear"># /etc/init.d/net.rausb0 start</pre>}}

And use default settings. If you need to set ESSID or Encryption, you will need to modify /etc/conf.d/wireless

When done, you should be able to run iwconfig and show your connected settings:
{{Console| <pre class="clear"># iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

vmnet1 no wireless extensions.

vmnet8 no wireless extensions.

rausb0 RT73 WLAN ESSID:"tSp"
Mode:Managed Frequency=2.462 GHz Access Point: 00:06:25:A5:A4:F5
Bit Rate=11 Mb/s
RTS thr:off Fragment thr=65534 B
Encryption key:off
Link Quality=77/100 Signal level:-62 dBm Noise level:-99 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0</pre>}}

[http://sabayonlinux.org/forum/viewtopic.php?f=52&t=2862 Forum Discussion]

[[Category:Wireless|Belkin wireless g usb network adapter F5D7050]]

HOWTO: Unoffical Guide To World Update

2011-08-25T13:46:39Z

Fitzcarraldo: /* Updating */ Changed cursor for kdesu command, as it should be run from your own user account, not root user's account.

{{Warning| '''Portage (emerge) is not the primary package manager for Sabayon, this article is for advanced users only. In other words if this fails for you, its your fault. You have been warned.'''}}
=World Update and Understanding Configs=

==Updating==

First let me say that there is a several ways to doing things on SL. I am not saying that my way is the best way by any means. This is simply my way of how I do things with a fresh install to make a stable system. You should probably read the other articles below first to better understand things.

First thing - I alway buy my hardware that I know is linux supported and has good drivers. So get to know your hardware, I can't say that enough as it will save you a lot of headaches.

'''DO NOTE''' - I can not tell you what you can safely remove from your system as you need to know your hardware and what is safe to uninstall, remove from config files and remove from kernel. I am going to try and stay very basic here so you can get the idea.

Fresh install and everything is working great so now what?

----
Well I head to the [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578 /etc/make.conf] file and edit that thing to my liking and double checking things over. I remove any unnecessary things. Remember to edit these files you must be root. If you like nano you can simple go into Konsole and punch in su than enter your password. You can edit the file by doing

{{Console| <pre class="clear"># nano -w /etc/make.conf</pre>}}

or if you simply must have a GUI you can go to konsole and enter

{{Console| <pre class="clear">$ kdesu konqueror</pre>}}

and when the box pops up, enter your password, wait a bit and a new window will come up. In that window you are root to everything and can edit anything. Pretty simple so far right? If you need help figuring out what options are available in the [http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578 make.conf] then refer to the Gentoo Handbook and Wiki often.

----
Ok, so now that I got that set I like to head to the kernel and add to it and remove things I don't need by doing in konsole:

{{Console| <pre class="clear"># zcat /proc/config.gz > /usr/src/config

# genkernel --kernel-config=/usr/src/config --menuconfig --bootloader=grub --gensplash=sabayon all --luks</pre>}}

'''or if you use lvm do:''' - noted for waltercool

# genkernel --kernel-config=/usr/src/config --menuconfig --bootloader=grub --gensplash=sabayon --lvm2 all --luks

''note the # means you must be root, don't actually use the #''

This step is not necessary if you don't care that your kernel is big. I always need to enable some sound stuff and you may need to enable drivers, again, this is where knowing where your hardware is very important. You remove the wrong thing and your puter will not boot. Skip this step if you have a funny look on your face at this time.

----
NOTE: Before doing the following 'emerge -e' commands, you may want to customize your CFLAGS in make.conf so that it is optimized for your CPU type. The following two commands take very a long time, so it's worth it to optimize while you are taking the time to do this. Please refer to [http://gentoo-wiki.com/Safe_Cflags Gentoo Safe CFLAGS Guide] for the correct setting for your specific CPU. Do not change your CHOST as described in that guide, changing CHOST is dangerous and not recommended. See [http://gentoo-wiki.com/HOWTO_change_CHOST_relatively_safely this HOWTO] if you wish to risk changing your CHOST.

Now some of you may totally think I am crazy here but as far as software removal I do that later. Yes I know I can remove software at this time that I will never use and save time when I recompile the system, but this is my unofficial stable system and I know it will work cause I have done it several times. So with that being said I want to now recompile just the system. Now I prefer to do :

# emerge -e system || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

Notice I have not done an emerge --sync yet and I don't want to do that yet, that will come later. So now several hours are going to go by. This a great thing to do when you are about to go to bed. After that is done, I like to do the world recompile:

# emerge -e world || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

do note once again that I have not used emerge --sync yet and this is going to be another lengthy process. You may do both commands at once by simply doing:

# emerge -e system || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done && emerge -e world || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

I just like to break it up.

----
So now I have finished recompiling everything and my processor is going Dude! Well now I punch in:

# emerge --sync && layman -S

to update my portage tree and overlays. First time syncs on SL are slow, I promise they will get faster after the first time. Once that is done I punch in:

# emerge -upDN world

this will pull up just under 400 packages, WOW!! Well lets get the show on the road.

# emerge -uN world

Now you look at that and go what happened to the D ?, again this is my guide and that will come later. Now you are probably sitting there thinking I thought SL doesn't recommend a world update. My feelings are this: no you don't need to, but SL 3.3 makes it a piece of cake to world update. Pre 3.3 I don't recommend, as you will be forever swamped with recompiling. Now with the world update you are going to run into bumps and this is where reading the ERROR MESSAGES is going to come to be Very Important. If you listen to what portage is telling you and use the Gentoo bugzilla and Gentoo forums for searching you can usually find the solution. Once a package fails I simply:

# emerge --resume --skipfirst

to continue on. I like to do this method to see what packages are failing. If you don't care:

# emerge -uN world || until emerge --resume --skipfirst; do emerge --resume --skipfirst; done

then it will auto skip and keep on going till finished. Now I don't try and fix any packages till it is completely done. Once it is done I look look at

#emerge -upN world

and go through each package and install it with the fix needed to get it to install. At this time I will simple remove any packages that have failed that I know I don't need. So now we are done and

# emerge -upN world

shows no packages left in it, time I fire up

# emerge -upDN world

YAY more packages to compile! The amount of packages won't be that much. So we wait for that to finish and I usually fix the errors as it goes along since it isn't very many packages. Now we have the entire system rebuilt, well almost. It's time to run:

# revdep-rebuild

and if that fails do:

# revdep-rebuild

It will find more packages to recompile! Your processor is probably plotting some sort of revenge against you at this time. So now what? Well, you are gonna have some config files that are screaming for an update. Now I like to use:

# etc-update

There is several ways to update config files, this is my way of doing it. So I punch in etc-update and many will auto merge, which is great with me. I look over the remaining ones left and determine if they are safe or not to update. Off the top of my head I believe all changes in 3.3 are safe, but look and if you are unsure, don't do it. So we have recompiled everything after making changes to system, updated the config files. Are we done? Do we dare reboot? Let's live dangerously and reboot, I mean a reinstall is only 40 minutes to do anyway right?

----
So we rebooted, prayed and we made it back to our Desktop!! So now, I like all the multimedia features the web has to offer, so I want to experience it all, so I open up my konsole again and punch in:

USE="divx gmedia gtk nls quicktime realmedia wmp" emerge mplayerplug-in

Yes, I know you can add this to your package.use file, but this is my guide and you should add it to your /etc/portage/package.use file for future use. Now I can sit back and view all the goodness of web multimedia! I hate totem handling the web plugins cause it sucks at doing so. I don't uninstall totem I simply move all the totem plugins out of the plugins folder:
/usr/lib/nsbrowser/plugins
and put em in
/usr/lib/nsbrowser
Just in case I ever want to put them back.

Alrighty then, we are world updated now. You can continue to stay world update and SL updated with the overlay by:

# emerge --sync && layman -S && emerge -uDN world

A handy automated script for this can be found here:
[http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=11870 Update Script]

----
Conclusion - my systems are rock solid no matter what I throw at them. It's a long process, but that's fine with me cause the results are worth it. Do keep in mind that it will take less time with the mini as there is less to deal with. It will require thinking and deciphering and good abilities of effective searching. No I can not help you world update your system as I have no idea what hardware you use or what you use your computer for. Is there a chance you may hose your system? Of course there is! It shouldn't happen if you pay attention. I can't stress enough to read the [http://www.gentoo.org/doc/en/handbook/index.xml Gentoo Handbook], look at the [http://gentoo-wiki.com Gentoo Wiki], look at the [http://forums.gentoo.org/ Gentoo Forum], look at the [http://wiki.sabayonlinux.org SL Wiki], look at the [http://www.sabayonlinux.org/forum SL Forum] and don't forget [http://google.com Google], bookmark them all!

That's it in a nutshell and I take NO and I mean NO Responsibilities for a hosed system. Your millage is going to vary of course depending on what hardware and software you use.

Input is welcome and I will answer questions if I know the answers.

HAPPY COMPILING!

[http://www.sabayonlinux.org/forum/viewtopic.php?t=5531 Forum Discussion]

==Understanding make.conf - An Introduction==
{{File|/etc/make.conf|<pre class="clear">
# These settings were set by the catalyst build script that automatically built this stage
# Please consult /etc/make.conf.example for a more detailed example
CFLAGS="-O3 -march=native -funroll-all-loops -m3dnow -msse3 -funit-at-a-time -fpeel-loops -ftracer -funswitch-loops -fomit-frame-pointer -pipe"
LDFLAGS="-Wl,-O1 -Wl,--enable-new-dtags -Wl,--sort-common -s"
CHOST="i586-pc-linux-gnu"
USE="win32codecs mp3 quicktime type1 divx4linux dvb dvd dvdread live mpeg nvidia jpeg truetype v4l v4l2 xv xvid multilib gnutls arts cups ppds foomatic-db \
alsa gimpprint freetype gnome X gtk gtk2 unicode moznocompose moznoirc moznomail kde qt samba xinerama xine theora kdeenablefinal wifi hal ieee1394 \
oggvorbis lm_sensors logitech-mouse zeroconf artswrappersuid nptl nptlonly rdesktop dvdr css gphoto2 openexr speex jpeg2k povray scanner musicbrainz \
accessibility audiofile exif xscreensaver ffmpeg vcd sndfile musepack asterisk mbrola pam_chroot pam_timestamp pwdb pda sms irda kig-scripting speedo \
browserplugin nsplugin ldap kerberos firefox dga aac dts xvmc dbus hal dvi on-the-fly-crypt dri xprint acpi ada ruby perforce cjk fat hfs jfs ntfs reiser4 \
xfs reiserfs skins cdda real shout stream a52 wxwindows vlm lirc libcaca remote stats lcd unichrome 7zip commercial mozsvg canvas xml2 glut java glitz svg \
avahi ogg vorbis aalib flac gdbm mikmod timidity kdgraphics dlloader exscalibar ipod visualization mono cdr nntp cairo djvu nautilus evo ole pdf xml ladspa \
soundtouch bzip2 udev mad fuse rtsp tiff kdehiddenvisibility dvi usb kipi aiglx musicbrainz pulseaudio dv lame mp3rtp udev cdr dvi djvu libnotify bzip2 aalib \
startup-notification nsplugin jingle gsm dbox2 opengl sdl png gif qt3 qt4 qt3support apache2 mysql php ssl xml berkdb innobd pcre"
CXXFLAGS="${CFLAGS}"
ACCEPT_KEYWORDS="~x86"
LINGUAS="en"
MAKEOPTS="-s -j3"
PORTAGE_NICENESS="8"
FEATURES="parallel-fetch"
CONFIG_PROTECT="/usr/kde/3.5/share/config/kdm/ /etc"
VIDEO_CARDS="vesa vga nvidia"
INPUT_DEVICES="evdev keyboard mouse"
LIRC_DEVICES="audio audio_alsa"
PORTAGE_ELOG_CLASSES="warn error log info"
PORTAGE_ELOG_SYSTEM="save"
# FEATURES="buildpkg"
source /usr/portage/local/layman/make.conf
EMERGE_DEFAULT_OPTS="--with-bdeps y"
</pre>}}

Above you will find a make.conf and is a vital component to your operating system. If you don't know this file you are defeating the purpose of this distro. One of the biggest things about gentoo based is being able to build the operating sytem to you. Using the default settings are going to work, but you are not taking full advantage of your potentials. You can ease our portage frustration also, like compiling issues.

Why do we need make.conf?
Portage uses this file to know how to build your entire system. All the settings you put here, portage reads and builds to them.

'''CFLAGS'''
CFLAGS are C compiler flags, usually GCC (GNU Compiler Collection) options.
CFLAGS are commonly used to specify the architecture of your computer, as well as the CPU you are using and any other special options you would like to enable or disable. This information is important to GCC because it tells it exactly how to customize the assembly instructions it creates from the application's source code.
http://gentoo-wiki.com/CFLAGS

'''LDFLAGS'''
Deals with your hash tables and compiler See for more information:
http://gentoo-wiki.com/TIP_Safe_LDFLAGS
http://lwn.net/Articles/192624/
Your not going to be touching these, so moving right along.

'''CHOST'''
Variable declares the target build host for your system You don't want to change this value unless you know what you are doing. You simply can't change it to i686 and go about using your computer. There is situations that may cause you to have to change this. For instance, lets say you upgrade your cpu or need a certain package that won't work with your current architect. Gentoo has a guide for changing it. Follow it closely or you will have a hosed system.
http://www.gentoo.org/doc/en/change-chost.xml

'''CXXFLAGS'''
CXXFLAGS is set to use all the options present in CFLAGS. This is what you'll want almost without fail. You shouldn't ever need to specify additional options in CXXFLAGS.
http://www.gentoo.org/doc/en/gcc-optimization.xml

'''USE'''
In Gentoo a USE flag is a representation of an option, a global setting for your final system. USE flags affect how many of the packages on your system will build. These depend on the software and your computer usage. It's important to know these and to thin the list down to your usage. You will see that I have a lot in mine, but that is because of testing I do for SL. All these USE settings are global, meaning they effect every package on your system. The more USE settings you have, the more conflicts you can encounter with portage when compiling software. There is a /etc/portage/package.use file that you can use to individually tell packages how you want them built.
http://gentoo-portage.com/USE
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=2

'''ACCEPT_KEYWORDS="~x86"'''
This is for setting which branch of portage you want to use. Stable vs. Unstable "bleeding edge". You can see by the ~ we are not using the stable branch so we are bleeding edge.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=3

'''LINGUAS'''
I hope this is self explanatory, but if not - your language
http://www.gentoo.org/doc/en/guide-localization.xml

'''MAKEOPTS'''
You define how many parallel compilations should occur when you install a package. A good choice is the number of CPUs in your system plus one, but this guideline isn't always perfect.
http://gentoo-wiki.com/Safe_Cflags
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=5

'''PORTAGE_NICENESS'''
If you keep using your computer while compiling packages you will notice that your box is less responsive than usual. This is caused by having two "groups" of processes with the same nice priority: your usual running processes, and emerge (and its child processes). Now, if you could renice emerge and its children to a higher nice value (i.e. lower priority), compiling would take somewhat longer, but your workstation will be as responsive as before.
http://gentoo-wiki.com/Portage_Niceness

'''FEATURES'''
Portage has several additional features that makes your Gentoo experience even better. Many of these features rely on certain software tools that improve performance, reliability, security, ...
Parallel fetch:
When you are emerging a series of packages, Portage can fetch the source files for the next package in the list even while it is compiling another package, thus shortening compile times..
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=3

'''CONFIG_PROTECT'''
This variable contains a space-delimited list of directories which should be protected by Portage during updates.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=5

'''VIDEO_CARDS'''
I see people's make.conf often and in the default make.conf there is like 20 video cards listed. Why compile more than you have too? Get rid of all the cards not in your computer.
http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml

'''INPUT_DEVICES'''
The same goes here, get rid of any equipment you don't have. My desktop doesn't have touchpad - why compile it?
http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml

'''LIRC_DEVICES'''
Linux Infrared Remote Control - this is where you are going to set your devices
http://gentoo-wiki.com/HOWTO_LIRC

'''source /usr/portage/local/layman/make.conf''' -- location for your layman, for managing your overlays such as sabayon, xeffects, etc....

Extras that I have added, just for my own use. You will not see these in a default make.conf
------------------------------------------------------------------------------------------------------------------------

'''PORTAGE_ELOG_CLASSES'''
Ebuild Logging -
Portage can create per-ebuild logfiles, but only when the PORT_LOGDIR variable is set to a location that is writable by Portage (the portage user). By default this variable is unset. If you don't set PORT_LOGDIR, then you won't receive any build logs with the current logging system, though you may receive some logs from the new elog. If you do have PORT_LOGDIR defined and you use elog, you will receive build logs and any logs saved by elog, as explained below.

Portage offers fine-grained control over logging through the use of elog:

* '''PORTAGE_ELOG_CLASSES:''' This is where you set what kinds of messages to be logged. You can use any space-separated combination of info, warn, error, log, and qa.
o info: Logs "einfo" messages printed by an ebuild
o warn: Logs "ewarn" messages printed by an ebuild
o error: Logs "eerror" messages printed by an ebuild
o log: Logs the "elog" messages found in some ebuilds
o qa: Logs the "QA Notice" messages printed by an ebuild
'''PORTAGE_ELOG_SYSTEM:''' This selects the module(s) to process the log messages. If left empty, logging is disabled. You can use any space-separated combination of save, custom, syslog, mail, save_summary, and mail_summary. You must select at least one module in order to use elog.
* save: This saves one log per package in $PORT_LOGDIR/elog, or /var/log/portage/elog if $PORT_LOGDIR is not defined.
* custom: Passes all messages to a user-defined command in $PORTAGE_ELOG_COMMAND; this will be discussed later.
* syslog: Sends all messages to the installed system logger.
* mail: Passes all messages to a user-defined mailserver in $PORTAGE_ELOG_MAILURI; this will be discussed later. The mail features of elog require >=portage-2.1.1.
* save_summary: Similar to save, but it merges all messages in $PORT_LOGDIR/elog/summary.log, or /var/log/portage/elog/summary.log if $PORT_LOGDIR is not defined.
* mail_summary: Similar to mail, but it sends all messages in a single mail when emerge exits.
http://www.gentoo.org/doc/en/handbook/h ... t=3&chap=1
**portage-2.1.3: "echo" - this prints all logged messages again at the end of the emerge

'''FEATURES="buildpkg"''' for building your own binary packages and saving them
http://gentoo-wiki.com/HOWTO_setup_a_PO ... OST_server
http://www.gentoo.org/proj/en/base/amd64/emul/index.xml

source /usr/portage/local/layman/make.conf -- location for your layman, for managing your overlays such as sabayon, xeffects, etc....

'''EMERGE_DEFAULT_OPTS="--with-bdeps y"''' # considers also build-time deps at dependency calculations
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=2

'''Man Make.conf'''
http://gentoo-wiki.com/MAN_makeconf

Do you see now why it is important to know this file? This file can make your gentoo based distro a much better experience. The gentoo handbook can help you set it up properly. Remember to take full advantage of changes, you need to be using certain flags like emerge --newuse foo. Recompiling your entire sytem and world is what you need to do to take advantage of your changes. Like for me I simple run emerge -uDN --world - that will update and make sure all packages are following my settings. If I changed a USE flag it will rebuild the packages effected and update packages to latest in portage.

Recompiling your system is not going to be easy if you are new to all of this. I recommend getting to know portage and how to work with portage before attempting it. It's something you just don't jump into. Your going to run into all sorts of issues and gonna have to search and find your answers. As of 3.4 you are gonna run into a python update, which requires taking care of first as things will break and need to get updated to the new python. Pending on your system - it can take several days to complete the process.
Learn your world file and cleaning it out before starting, this will save many hours of recompiling packages you don't need. The world file is a record of packages which have been specifically installed by the user. More specifically it's a list of packages which the user wants to keep installed and updated on their system. It will not record the dependencies of those packages, but instead uses the dependencies of the currently installed packages to keep track of this information. http://gentoo-wiki.com/HOWTO_Use_Portage_Correctly

You will also want to get yourself familiar with the files in your /etc/portage/ you will need to use them to mask and unmask needed packages. Also use em for telling how certain packages should be built.

Read thru the unofficial guide for a world update
viewtopic.php?f=54&t=5531

Best advice - Use the operating system till you know it, than start diving into the depths of the internal stuff. I know it is frustrating for people that are new, but if you give it time and stick with it, it will all come together. If all this information totally terrifies you, than stick with the default settings. Use the information for you knowledge. Topic is open for discussion.

[http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578 Forum Discussion]

==Config Files - An Introduction==

Without config files the operating sytem would be blah. Are you finding yourself confused with all the messages of portage telling you:
IMPORTANT: 124 config files in '/usr/share/X11/xkb' need updating

Well unfortunately with the amount of config files on your computer it is impossible to go over them all. I'm going to try and hit on the more important ones that are used more frequently.

Do you have to update your config files? The answer will be yes. Why? Cause things change over time.

How do I update my config files, portage keeps telling me I have config files to update? Well there is several ways to do this, you will need to run one of the following more popular methods.:
--------etc-update: http://www.gentoo-wiki.info/HOWTO_etc-update
--------dispatch-conf: http://www.gentoo-wiki.info/TIP_dispatch-conf

Do not and I repeat, do not blindly auto merge config file updates. You can hose your system to the point it won't boot back up. Well there is so many, how do I know if it is safe to or not? Good question and the rule of thumb is - if you have not edited a config file than generally your are safe, but this isn't a sure fire way. Using dispatch-conf will keep a back up copy of you old config files in case you need to restore them. Get to know your config files so you can be aware of certain files.

Remember to edit the config files you need to be root, so you will want to open konsole, type su, enter password and than nano or vi the file. You can do this via GUI too, just open konsole and run kdesu konqueror and when the box comes up, enter you root password and than you will have a root file manager window, gnome users will use gksu nautilus.

'''/etc/rc.conf''' - for general, system-wide configuration. Read the comments in the file, it's pretty well explained. If your window manager suddenly changes upon boot, this is one of the first files to check.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/conf.d/xdm''' - Is what controls your GUI login and window Manager. So if you GUI or login is messed up, be sure to check it out. It's self explanatory.
http://www.gentoo-wiki.info/HOWTO_Activate_Graphical_login

'''/etc/hosts''' - helps in resolving host names to IP addresses for hosts that aren't resolved by your nameserver.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/make.conf''' - This file contains various variables that are used by Portage. Portage will check the currently-defined environment variables first for any settings.
http://www.gentoo-wiki.info/MAN_makeconf
http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10578

'''/boot/grub/grub.conf''' - Your boot manager so you can boot 1 or more operating systems. This is one of the first screens you will see and is asking for you to choose what operating system to boot.
http://www.gentoo-wiki.info/HOWTO_Quick_GRUB
http://www.gentoo-wiki.info/HOWTO_Dual_boot

'''/etx/X11/xorg.conf''' - Xorg is the X Window server which allows users to have a graphical environment. Got resolution problems? This file is for you.
http://www.gentoo.org/doc/en/xorg-config.xml

'''/etc/conf.d/net''' - your network configuration, see /etc/conf.d/net.example for a very well documented example â€“ dhcp, static, wireless, wired networking settings
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/resolv.conf''' - your DNS file, nothing to complicated, but if you can access your router but can't get web pages to load - check this file for DNS settings
http://www.gentoo.org/doc/en/home-router-howto.xml

'''/etc/fstab''' - This file contains the mount points of your partitions. Need to mount a hard drive? Add it here so it is available on every boot up.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8

'''/etc/modules.autoload.d/kernel-2.6''' - You may have decided to compile some kernel components as modules (as opposed to compiled directly into the kernel) and would like to have them autoloaded on bootup like you did with 2.4. Also, if you installed any external modules from the portage tree you will probably want to autoload them too.
http://www.gentoo.org/doc/en/migration-to-2.6.xml

'''/etc/exports''' This is great for doing shares on the network using NFS
http://www.gentoo-wiki.info/HOWTO_Share_Directories_via_NFS
This also works great of sharing portage across multiple computers. You only need to sync one main computer than share your portage so the other computers will connect to your main computer for emerges
http://www.gentoo-wiki.info/HOWTO_Using_a_shared_portage_via_NFS

This hardly puts a dent in the amount of config files, but those are the ones I run across the most, plus trying to keep it friendly for people new to config files. I could of mentioned like local.start, but that is for experienced people.

Generally you can google and find some thing about the config file. Enter into google "gentoo xorg.conf" and you will find your answer. Feel free to add more that I may have missed here.

[http://www.sabayonlinux.org/forum/viewtopic.php?f=54&t=10863 Forum Discussion]

Setup Flock

2011-08-19T12:17:02Z

Fitzcarraldo: Undo revision 10774 by spammer MerrillFeasel

==''' Pre Install Notes '''==

'''Flock''' is a Web Browser which bills itself as a Social Networking Web Browser, which basically makes it Firefox with some very loud bells and whistles.

Alternative to this Howto is available at the site [http://gentoo-wiki.com/Flock/Installation] which explains how to install the software using emerge.

I'm also doing this from the KDE interface, using Sabayon Linux 3.4f and installing Flock 0.9.1.2, however most of it will work on Gnome.. as long as you know how to add a desktop icon.

During the HowTo commands use a ~ in the path,, this should denote your home folder,if you are logged i as '''root''' ('''su''') this will take you to the home folder of the root user, and not your user..

----

==''' Downloading Flock '''==

Flock may be downloaded from The Flock Webpage [http://www.flock.com/] Click on the Get Flock now link this will download Flock to your default download location as a tar.gz file

For the rest of the Howto we will assume your default download location is at ~/download

==''' Installing Flock '''==

Installation, is easy, there are probably easier ways to do it than this, i do know this way works..

Open up konsole

'''cd ~/download
tar -xzvf flock*.tar.gz'''

'''su'''

'''mv flock /opt/flock'''

'''exit''' (take you back to normal user)

==''' Setup a Toolbar Icon '''==

On the KDE Toolbar,

Right Click and choose Add Application to Panel, then Add Non KDE Application

In the dialog box which appears enter the following in the correct fields

Button Title = '''Flock'''
Decription = '''Social Browser'''
Executable = '''/opt/flock/flock'''

Click on the Icon, and browse to '''/opt/flock/icons''' and choose an icon from here.

Click on OK, and Launch the browser

==''' Migration Wizard '''==

If you have been using Firefox previous to this, then on the first load, Flock will launch a wizard which will attempt to import your settings. How you progress with this is up to you.

==''' Getting the Media Files to work '''==
I found that the media files, and plugins which work in Firefox didn't work in Flock, however geting this done took only a few minutes (and is an area the migration wizard should really improve on)

For this i simply copied the plugins from the /opt/netscape/plugins to /opt/flock/plugins with

'''cp /opt/netscape/plugins/*.* /opt/flock/plugins/.'''

Then copied the pluginsreg.dat from ~/.mozilla/firefox into the flock profile folder

'''cp ~/.mozilla/firefox/pluginsreg.dat ~/.flock/browser'''

Next i edited the pluginreg.dat file using nano in konsole

'''cd
cd .flock/browser
nano pluginreg.dat'''

And changed all the lines which pointed to /opt/netscape/plugins to /opt/flock.plugins, i did this as when i tried using flock with an unedited pluginreg.dat it ould not launch the media players, however editing did make a difference, as it all worked fine

With this done, restart Flock, and all should now work fine..

== '''Firefox Extensions''' ==

Flock does offer support for basic firefox extentions, and so fa only the All in One Sidebar has failed on me..

Savage: Battle For Newerth

2011-08-19T12:12:38Z

Fitzcarraldo: Undo revision 10775 by spammer LunaMelinda

So you have this beautiful new sabayon desktop with Savage: Battle For Newerth and you go to play and you can't get on any server because

'''you must update'''
'''LINUX: Game Patch (requires Savage 2.00c)'''

Open konsole or terminal and:
<pre> su </pre>
<pre> # cd /opt/savage </pre>
<pre> # wget http://www.notforidiots.com/SFE/SFE.tar.gz</pre>
<pre> # tar -zxvf SFE.tar.gz </pre>

and that was it, I started getting on servers without any problem.

Not in love with this game but, well, there you go.

[[Category:Gaming|Savage: Battle For Newerth]]

En:Wiki Admins

2011-05-06T16:11:58Z

Fitzcarraldo: 11:22, 5 May 2011 Wolfden changed his group membership from Bureaucrats and Administrators to (none) ‎

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

* [[User:Lxnay|Lxnay]]
** Jabber: lxnay at sabayonlinux dot org
** Email: lxnay at sabayonlinux dot org
*[[User:Ironsight|Ironsight]]
**Email: rabidweezle at gmail dot com

[[Category:Sabayon Wiki|Wiki AdminsEn]]

HOWTO: Clock, Time, UTC, Dual boot with Windows

2011-04-22T00:56:18Z

Fitzcarraldo: Added item (c) make CLOCK_SYSTOHC="yes" for /etc/conf.d/clock users, and item (b) make clock_systohc="YES" in case the as-installed file does not have that.

==Clock, Time, UTC, Dual boot with Windows==

===Introduction===

{{Note|

This article is intended for three different types of Linux user:

: 1) This article will be of interest to you if you only run Linux on your PC and are having trouble getting the clock on the Panel to display the correct time.

: 2) If you only run Linux on your PC then this article will also be of interest to you if you need to know the time in other timezones (perhaps you have friends or relatives in other timezones, or you have a laptop and take it with you to other timezones).

: 3) If you dual boot with Windows then this article is also applicable.}}

This article covers Gentoo/Sabayon Linux before and after migration to Baselayout-2 and OpenRC (as covered in the Gentoo Baselayout and OpenRC Migration Guide). Any differences to clock and timezone-related files before and after migration are indicated in the article. '''If you are using Sabayon Linux 3.5 or a later version then you are already using Baselayout-2 and OpenRC.''' If you are using Sabayon Linux 3.4 or an earlier version then, unless you have manually migrated, you are not using Baselayout-2 and OpenRC.

===Terminology===

First let me define a few terms I'm going to use in this article:

'Hardware clock' (also known as 'BIOS clock' or 'CMOS clock') is the battery-backed clock on your motherboard. 'System clock' is the software clock that only exists when Linux is running, and is the clock that is displayed on the Panel. 'Local Time' is the time in your timezone.

===Configuration===

Linux is flexible and, if you want, you can configure it to write the time of the system clock to the hardware clock when you shutdown Linux. You don't have to do this, but it's a good idea. Why? Because the hardware clock tends to drift over time, so it's good to adjust it now and again. If you either manually adjust your system clock to the correct time or use NTP (network time protocol) to do it automatically via the Internet then you will be ensuring that the hardware clock is kept at the correct time. The various Linux distributions provide different ways of configuring how the distribution behaves, but for Gentoo/Sabayon Linux there is an environment variable called CLOCK_SYSTOHC (clock_systohc if you are using Baselayout-2 and OpenRC) in a text file /etc/conf.d/clock (/etc/conf.d/hwclock if you are using Baselayout-2 and OpenRC) which is used for this purpose: making CLOCK_SYSTOHC="yes" (clock_systohc="YES" if you are using Baselayout-2 and OpenRC) will make Gentoo/SL write the time of the system clock to the hardware clock at shutdown. Conversely, making CLOCK_SYSTOHC="no" (clock_systohc="NO" if you are using Baselayout-2 and OpenRC) will mean that the time of the system clock is not written to the hardware clock at shutdown.

Now, the text file /etc/conf.d/clock (/etc/conf.d/hwclock if you are using Baselayout-2 and OpenRC) can also contain an environment variable called CLOCK ('''clock''' if you are using Baselayout-2 and OpenRC). Here's an excerpt from the file clock, followed by an excerpt from the file hwclock:

{{File|/etc/conf.d/clock|<pre class="clear">
# /etc/conf.d/clock

# Set CLOCK to "UTC" if your system clock is set to UTC (also known as
# Greenwich Mean Time). If your clock is set to the local time, then
# set CLOCK to "local". Note that if you dual boot with Windows, then
# you should set it to "local".

CLOCK=""

# Select the proper timezone. For valid values, peek inside of the
# /usr/share/zoneinfo/ directory. For example, some common values are
# "America/New_York" or "EST5EDT" or "Europe/Berlin".

TIMEZONE=""

# If you wish to pass any other arguments to hwclock during bootup,
# you may do so here.

CLOCK_OPTS=""

# If you want to set the Hardware Clock to the current System Time
# during shutdown, then say "yes" here.

CLOCK_SYSTOHC=""

# Newer FHS specs say this file should live in /var/lib rather than
# /etc. If you care about such things, feel free to change this value.
# Note that a blank value means that you do not wish to even use the
# adjtime facility. This is the default behavior as adjtime can be
# very fragile. If the clock is updated without updating the adjtime
# file (which is common when using services such as ntp), then the
# clock can be screwed up when it gets updated at next boot.

#CLOCK_ADJTIME="/var/lib/adjtime"
#CLOCK_ADJTIME="/etc/adjtime"
CLOCK_ADJTIME=""

### ALPHA SPECIFIC OPTIONS ###

# If your alpha uses the SRM console, set this to "yes".
SRM="no"

# If your alpha uses the ARC console, set this to "yes".
ARC="no"
</pre>}}

{{File|/etc/conf.d/hwclock|<pre class="clear">
# Set CLOCK to "UTC" if your system clock is set to UTC (also known as
# Greenwich Mean Time). If your clock is set to the local time, then
# set CLOCK to "local". Note that if you dual boot with Windows, then
# you should set it to "local".
clock="local"

# If you want to set the Hardware Clock to the current System Time
# during shutdown, then say "YES" here.
# You normally don't need to do this if you run a ntp daemon.
clock_systohc="YES"

# If you wish to pass any other arguments to hwclock during bootup,
# you may do so here. Alpha users may wish to use --arc or --srm here.
clock_args=""
</pre>}}

In the case of Gentoo/Sabayon Linux, perform the following if you '''are not using Baselayout-2 and OpenRC''':

1. Edit /etc/conf.d/clock and: '''a)''' make CLOCK="local"; '''b)''' make TIMEZONE="<your timezone>" (if you are in Spain, for example, you would enter TIMEZONE="Europe/Madrid"); '''c)''' make CLOCK_SYSTOHC="yes".

2. Set the timezone information as per Gentoo Handbook Chapter 7. If you are in Spain, for example, you would enter the following command as root user in a Terminal window:
{{Console| <pre class="clear"> rm /etc/localtime && cp /usr/share/zoneinfo/Europe/Madrid /etc/localtime </pre>}}

Or, if you '''are using Baselayout-2 and OpenRC''', perform the following:

1. Edit /etc/conf.d/hwclock and '''a)''' make clock="local"; '''b)''' make clock_systohc="YES" if it is not already that.

2. Edit /etc/timezone and enter your timezone (if you are in Spain, for example, you would make the contents of the file /etc/timezone to be "Europe/Madrid" without the quotes).

3. Set the timezone information as per Gentoo Handbook Chapter 7. If you are in Spain, for example, you would enter the following command as root user in a Terminal window:
{{Console| <pre class="clear"> rm /etc/localtime && cp /usr/share/zoneinfo/Europe/Madrid /etc/localtime </pre>}}

The proper contents for the file /etc/timezone is the path relative to your timezone from /usr/share/zoneinfo. For example, for someone living on the east coast of the United States, the correct contents of /etc/timezone would be "America/New_York" (without the quotes).

{{Warning| Do not make /etc/localtime a symlink, even though some people make this recommendation for other Linux distributions.
The "rm /etc/localtime &&" shown above is in case /etc/localtime is already a symlink to the file you are trying to copy.}}

===Dual Boot with Windows===

If you dual boot Linux and Windows, the chances are that you've already come across the problem of the on-screen clocks in Linux and Windows having a difference of one or more hours; this usually happens twice a year when the clocks change in countries that adopt Daylight Saving Time (but can also occur in between, depending on how the two operating systems have been configured). You can experience various effects depending on how your Linux and Windows have been configured, such as the on-screen clock moving forwards (or backwards) by 1 hour in Linux on the allotted day, then when you boot Windows the clock moves forwards (or backwards) by a further 1 hour.

The first thing you need to know is that Windows stores the Local Time in the hardware clock and that is what is displayed in the System Notification Area on the Taskbar, whereas Linux keeps the times in the hardware clock and system clock separate, and only reads the time from the hardware clock at startup. When you boot Linux it reads the time in the hardware clock and sets the system clock to that time and applies any timezone offset that you have defined in a configuration file. Thus the time in the hardware clock and system clock can be -- and usually is -- different.

As you can see in the configuration file in the directory /etc/conf.d/, the comment in the file recommends that you edit the file to make CLOCK/clock="local" if you dual boot with Windows. This appears to make sense, given that Windows' clock (the hardware clock) contains local time, so when you boot Linux it will copy the time in the hardware clock to the system clock, find that CLOCK/clock="local" and therefore not make any adjustment to the time in the system clock.

However, this can also cause problems. The first time you boot into Windows after Daylight Saving Time starts or finishes in your timezone, Windows will automatically detect this and, if you have 'Automatically perform Daylight Savings update' ticked, Windows will adjust the hardware clock because it assumes the hardware clock contains Local Time. Because Linux has no way of knowing this has happened, its system clock will be out by at least an hour. In addition, if you initially had the hardware clock set to UTC and are using CLOCK/clock="UTC" and have configured Linux to display the time in your timezone, the clock will be wrong under Windows too.

{{Note|'''Note 1:''' Notice that the time of the Windows clock will not change if you boot Windows first following the start/end of Daylight Saving Time. The Windows clock will only be correct again once you have booted and shutdown Linux.}}

{{Note|'''Note 2:''' If you have migrated to Baselayout-2 and OpenRC from a Baselayout-1 installation, you may find that you see the following error message if you boot up in Verbose Mode (press Alt-F1 during boot):

ERROR: cannot start hwclock as fsck would not start

I happened to find the correct solution in Gentoo Bugzilla Report No. 224171, which is to delete the old script /etc/init.d/clock. The file /etc/init.d/clock is a script that is redundant after migrating to Baselayout-2 and OpenRC. Merging openrc should have removed it, but didn't.

Anyway, to summarise, here's what I did as root user in a Terminal window to fix the problem:

# mv /etc/init.d/clock /etc/init.d/clock.bak
# /lib/rc/bin/rc-depend -u

The "/lib/rc/bin/rc-depend -u" rebuilds your deptree. I'm not sure if I needed to do that, but it doesn't do any harm to rebuild it.}}

===My Situation===

I am based in the UK but I travel frequently with my laptop to different timezones. I also have friends, relatives and work colleagues in various timezones who I contact often, so I need to know what time it is there before telephoning. And, just to complicate matters further, I dual boot SL and Windows 7.

If I were to set the Windows clock to the timezone of the area where I live "(UTC) Dublin, Edinburgh, Lisbon, London", untick "Automatically adjust clock for Daylight Saving Time", and make the Linux variables clock="local", /etc/timezone "Europe/London" and clock_systohc="YES" then, providing I stayed in the UK, my hardware clock and my Linux system clock would be correct (with the caveat in '''Note 1''' above). I have not ticked the 'Automatically adjust clock for Daylight Saving Time' box, in order to avoid Windows adding/subtracting an additional hour if I have used Linux before Windows after the beginning or end of Daylight Saving Time. Furthermore, in Linux, by hovering my mouse pointer over the clock on the Panel I can make the clock on the Panel display the times of all the timezones I ticked in the list Time Zones in Clock Settings.

If I were to travel to another timezone, I could change the time displayed by the clock on the Panel to the time of the new timezone I'm in by right-clicking on the clock on the Panel. This would not change the time in the system clock, which would remain as the time at the Local Timezone (UK time, as I have not changed the Local Time), just the time displayed on the clock on the Panel. If I boot into Windows it would still display the time in the UK.

If I were to change the Windows clock to a different timezone to reflect the new timezone I'm now visiting, the next time I boot into Linux it would make the Local Timezone time equal to the local time in the hardware clock and write the time in the system clock to the hardware clock on shutdown. Both the time in Local Timezone and the time in the hardware clock would then be correct. So, wherever I am, I can change the configuration of the timezone of the Windows clock to the timezone I happen to be in (but leave the Daylight Saving Time correction unticked). In Gentoo/Sabayon Linux I would also need to edit /etc/timezone to contain the new timezone, and set the timezone information as per Gentoo Handbook Chapter 7.

[This page created by Fitzcarraldo on 17.08.08]

Books

2011-02-02T15:39:16Z

Fitzcarraldo: Book title is "Linux Sea", not "Linux sea".

*General Linux Documentation and free Books: [http://www.tldp.org/]
*Official Gentoo Documentation: [http://www.gentoo.org/doc/en/]
*Gentoo Wiki: [http://www.gentoo-wiki.com]
*Introduction to Linux: [http://tldp.org/LDP/intro-linux/html/intro-linux.html]
*Linux Sea: [http://swift.siphos.be/linux_sea/]
*Linux Knowledge Base and Tutorial [http://sourceforge.net/projects/linkbat/]
*Put Yourself In Command: [http://en.flossmanuals.net/gnulinux]
*Bash Guide for Beginners: [http://tille.garrels.be/training/bash/]
*Advanced Bash-Scripting Guide: [http://tldp.org/LDP/abs/html/]
*Advanced Linux Programming: [http://www.advancedlinuxprogramming.com/]
*Linux Kernel in a Nutshell:[http://www.kroah.com/lkn/]

Printed books that are not free but good guides:
*Linux Phrasebook, Scott Granneman: [http://www.amazon.com/gp/product/0672328380/]
*Linux Pocket Guide, Daniel J. Barrett: [http://www.amazon.com/Linux-Pocket-Guide-Daniel-Barrett/dp/0596006284]

HOWTO: booting Sabayon CoreCD image from a USB flash with Syslinux

2011-01-30T05:36:47Z

Fitzcarraldo: Corrected "Unetbooting" to "UNetbootin" and added hyperlink to the UNetbootin home page.

You need +512MB USB flash and .iso of Sabayon CoreCD (here: 5.2 x86).

You get CoreCD installed on one of extended partitions, Sabayon will be working.

It is recommended to backup:
[[HOWTO: separate boot partition with PartedMagic and Clonezilla (dedicated GRUB2 partition)]]

Install using [http://unetbootin.sourceforge.net/ UNetbootin] is a much more preferable way. This HOWTO is about manual install using Syslinux (you have to install Syslinux package during process)

0. Prepare ext4 extended partition to hold CoreCD (here: /dev/sda6). 12GB should
be enough.

1. Insert USB flash, run mount:

{{Console| <pre class="clear">
$ su
# mount
</pre>}}

to find where your USB flash is mounted (here: /dev/sdb1 on /media/disk). Unmount it
{{Console| <pre class="clear">
# umount /media/disk
</pre>}}

2. (!) From here and ahead, be careful when writing something like /dev/sdb or /dev/sdb1. Because /dev/sda is your first HDD, and many commands here could make it unbootable. Also, there is a difference in /dev/sdb (USB flash device) and /dev/sdb1 (partition of that device), don't spend time changing this.

Create one primary boot partition
{{Console| <pre class="clear">
# fdisk -cu /dev/sdb
</pre>}}
Useful commands of fdisk are:
p - partition table
d - delete partition
n - create partition
a - toogle boot flag
w - save and exit

The result:
{{Console| <pre class="clear">
# fdisk -lu /dev/sdb
Device Boot Start End Blocks Id System
/dev/sdb1 * 2048 8000306 3999129+ 83 Linux
</pre>}}
Create FAT 32 file system (use FAT 16 for -4GB)
{{Console| <pre class="clear">
# mkfs.vfat -F 32 /dev/sdb1
</pre>}}
3. Install MBR from syslinux on USB flash
{{Console| <pre class="clear">
# equo install syslinux
# dd if=/usr/share/syslinux/mbr.bin of=/dev/sdb
</pre>}}
Mount USB flash
{{Console| <pre class="clear">
# mkdir -p /mnt/usb
# mount -t vfat /dev/sdb1 /mnt/usb
</pre>}}
Mount .iso (here: Sabayon_Linux_CoreCD_5.2_x86.iso)
{{Console| <pre class="clear">
# mkdir -p /mnt/cdrom
# mount -o loop,ro -t iso9660 /media/sda10/tmp/Sabayon_Linux_CoreCD_5.2_x86.iso /mnt/cdrom
</pre>}}
Copy files
{{Console| <pre class="clear">
# cp -r /mnt/cdrom/* /mnt/usb
# mv /mnt/usb/isolinux/* /mnt/usb
# mv /mnt/usb/isolinux.cfg /mnt/usb/syslinux.cfg
# rm -rf /mnt/usb/isolinux*
</pre>}}
Install syslinux on USB flash
{{Console| <pre class="clear">
# syslinux /dev/sdb1
</pre>}}
Test a newly created USB using QEMU
{{Console| <pre class="clear">
# umount /dev/sdb1
# sync ; echo 3 > /proc/sys/vm/drop_caches ; qemu -usb /dev/sdb1
</pre>}}
4. Boot from Sabayon 5.2 CoreCD USB flash.

If it writes something, wait. If it wanting you to select graphical mode, try
800x600 - works for sure. After booting, start installer and follow instructions. Install CoreCD to extended partition (here: /dev/sda6) by choosing a "/" (root) mount point.

(optional) If you followed HOWTO about backup, you already have a separate boot partition (here: /dev/sda1) with GRUB2. So, do not install bootloader to MBR, but install at root.

Reboot to your old Sabayon, open /boot/grub/grub.cfg on CoreCD (!) partition, and find 2 menu entries for CoreCD, they boot from different (hd0,?) and are started at
{{File| (/boot/grub/grub.cfg)| <pre class="clear">
### BEGIN /etc/grub.d/10_linux ###
</pre>}}

Copy them to /etc/grub.d/40_custom. Remove old grub.cfg (make a backup of it!), and generate a new grub.cfg
{{Console| <pre class="clear">
# rm /media/sda1/boot/grub/grub.cfg
# grub-mkconfig -o /media/sda1/boot/grub/grub.cfg
</pre>}}
Test changes using QEMU
{{Console| <pre class="clear"># sync ; echo 3 > /proc/sys/vm/drop_caches ; qemu -hda /dev/sda</pre>}}

Pl:HOWTOs

2010-12-30T15:59:49Z

Fitzcarraldo: Undo revision 9254 by Killas (Talk) User 'Killas' is a spammer.

{{I18n|[[En:HOWTOs|en]] [[Es:HOWTOs|es]] [[It:HOWTOs|it]] [[pl:HOWTOs|pl]]}}

==Pierwsze kroki==
{{See also|[[:Category:Visual Tour]]}}
*[[Visual Tour:Uruchomienie komputera z LiveDVD/CD Sabayon Linux Gnome]]
*[[Visual Tour: Instalacja Sabayon Linux Gnome]]
*[[pl:Visual_Tour:_Uruchomienie_komputera_z_LiveDVD/CD_Sabayon_Linux_KDE4|Visual Tour: Uruchomienie komputera z LiveDVD/CD Sabayon Linux KDE4]]
*[[pl:Visual_Tour:_Instalacja_Sabayon_Linux_KDE4|Visual Tour: Instalacja Sabayon Linux KDE4]]
*[[pl:Visual_Tour:_Poprawiamy_wygląd_i_funkcjonowanie_KWin_w_SL_5_-_KDE_4.3|Visual Tour: Poprawiamy wygląd i funkcjonowanie KWin w SL 5 - KDE 4.3]]
*[[pl:Visual_Tour:_Instalacja_dodatkowego_oprogramowania_przy_pomocy_Sulfur |Visual Tour: Instalacja dodatkowego oprogramowania przy pomocy Sulfur]]
*[[pl:Visual_Tour:_Edycja_xorg.conf|Visual Tour: Edycja xorg.conf]]

==Instalacja==
{{see also|[[:Category:Installation]]}}
*[[HOWTO: Nagrywanie płyty instalacyjnej w Windows]]
*[[HOWTO: Sprawdzanie integralności LiveCD lub LiveDVD]]
*[[HOWTO: Ręczne Partycjonowanie w Sabayon Linux]]
*[[HOWTO: Korzystanie z xdelta]]
*[[Pl:HOWTO: Aktualizacja kernela z wykorzystaniem genkernel|HOWTO: Aktualizacja kernela z wykorzystaniem genkernel]]
*[[Pl:HOWTO: Aktualizacja kernela z wykorzystaniem Entropii|HOWTO: Aktualizacja kernela z wykorzystaniem Entropii]]
*[[HOWTO: Użycie Sabayon LiveDVD/CD do naprawy GCC]]
*[[HOWTO: Porada w sprawie wyboru hostname podczas instalacji Sabayon Linux]]

==Polonizacja==
*[[Pl:HOWTO: Polonizacja systemu|HOWTO:Polonizacja systemu]]
*[[Pl:HOWTO: Polonizacja firefoxa|HOWTO:Polonizacja Firefox]]
*[[Pl:HOWTO: Polskie znaki w man|HOWTO:Polskie znaki w 'man']]

==Zarządzanie energią==
*[[Pl:HOWTO: Parkowanie dyskow |HOWTO:Parkowanie dysków w laptopach]]

==Zarządzanie pakietami==
{{see also|[[:Category:Package Management]]}}
*[[Pl:HOWTO:_Instalacja_oprogramowania_w_Sabayon_/_Kompletny_przewodnik_po_portage|HOWTO: Instalacja oprogramowania w Sabayon / Kompletny przewodnik po portage]]
*[[HOWTO: Instalacja Himerge]]
*[[HOWTO: Nieoficjalny przewodnik aktualizacji systemu]]

==Grafika==
*[[Pl:HOWTO: Instalacja sterowników NVIDIA w Sabayon Linux|HOWTO: Instalacja sterowników NVIDIA w Sabayon Linux]]

==Sprzęt==
*[[Pl:HOWTO: Montowanie partycji NTFS|HOWTO: Montowanie partycji NTFS]]
*[[Pl:HOWTO: Problemy z HDA-Intel |HOWTO: Problemy z dźwiękiem w kartach muzycznych z chipsetem HDA-Intel]]

==Sieć==
*[[Pl:HOWTO: Instalacja Broadcom |HOWTO: Instalacja sterowników karty Broadcom serii BCM4311, BCM4312, BCM4321, and BCM4322 ]]
*[[Pl:HOWTO: Wykorzystanie narzędzia "Ndiswrapper" |HOWTO: Instalacja karty sieciowej przy pomocy sterowników dla Windows ]]

==Inne==

Es:HOWTO: Manual Partitioning with Sabayon Linux

2010-12-30T15:57:25Z

Fitzcarraldo: Undo revision 9255 by Killas (Talk) User 'Killas' is a spammer.

{{i18n|[[En:HOWTO: Manual Partitioning with Sabayon Linux|en]] [[Es:HOWTO: Manual Partitioning with Sabayon Linux|es]]}}

{|
|-
|[[Image:Schermata1.png|right|350px|350px]]
Se que LVM no es exactamente la manera perfecta de hacer una instalacion en Linux, pero es la unica que particiona en forma automatica. Decidi publicar este pequeño COMO con fotografias:
primero que nada, seleccione particionamiento manual cuando se le solicite.
|-
|[[Image:Schermata2.png|right|350px|350px]]
luego, escoja el espacio libre en donde deseamos instalar Sabayon Linux y haga click en Nuevo.

|-
|[[Image:Schermata3.png|right|350px|350px]]
La primera particion a crear es la particion boot, con ext3. En mi caso, he escogido un tamaño fijo de 100 MB. pero mi notebook es utilizada para cuestiones de desarrollo, por lo que necesito mas espacio, para mas kernels. Usted puede escoger con tranquilidad 32 MB que es mas que suficiente para el usuario comun.

|-
|[[Image:Schermata2.png|right|350px|350px]]
Ahora, seleccione el espacio libre y presione Nuevo otra vez.

|-
|[[Image:Schermata4.png|right|350px|350px]]
Esta vez vamos a crear una particion swap, por el tamaño yo he escogido 1500 MB, que es un espacio decente, pero usted puede escoger mas si tiene mas de 1 GB de RAM.

|-
|[[Image:Schermata5.png|right|350px|350px]]
Es hora de crear una particion root, como lo hizo anteriormente, seleccione el espacio libre y de click en Nuevo.

|-
|[[Image:Schermata6.png|right|350px|350px]]
Estamos a punto de seleccionar todo el espacio libre que queda. como el tipo sistema de archivos... yo he escogido ext4, pero esto es EXPERIMENTAL.

|-
|[[Image:Schermata7.png|right|350px|350px]]
Como puede ver, esta es nuestra configuracion final.

|-
|Espero que esto sea util para todos ~
Luca Palermo
|}

[[Category:Installation|Manual Partitioning with Sabayon LinuxEs]]

Talk:HOWTO: Upgrade kernel using Entropy

2010-12-21T20:04:25Z

Fitzcarraldo: Added note about incorporating the comment by user 'Thompson'.

I have got a suggestion for how to search which modules are installed for one's kernel version:
Instead of running

{{Console| <pre class="clear"> equo search <kernel-version> > kernel-upgrade.txt </pre>}}

''(BTW, the pipe is unnecessary. You can redirect the output of equo directly to another file.)''

run

{{Console| <pre class="clear"> equo query installed <kernel-version> > kernel-upgrade.txt </pre>}}

This way you will only see packages that are actually installed on your machine,
thus not having to search the text-file to find out, which kernel-modules are installed, and which
ones aren't. Be careful though, to really only update your kernel-modules!

E.g. I did an upgrade from '''2.6.35''' to '''2.6.36''', and in my '''kernel-upgrade.txt'''
there was also this package listed:

{{Console| <pre class="clear"> sys-apps/iproute2-2.6.35-r2 </pre>}}

This is '''NOT''' a kernel module! But if one reads the Description of the packages listed this is
quite easy to find out.

==================================================================================================

Good idea, but if you append "-sabayon" to the kernel version then you won't even get that one 'rogue' package you listed. For example, the following would do it:

{{Console| <pre class="clear">equo query installed 2.6.35-sabayon</pre>}}

resulting in:

{{Console| <pre class="clear"># equo query installed 2.6.35-sabayon
>> @@ Searching...
>> @@ Package: app-emulation/virtualbox-guest-additions-3.2.8#2.6.35-sabayon branch: 5, [__system__]
>> Installed: version: 3.2.8 ~ tag: 2.6.35-sabayon ~ revision: 2
>> Slot: 0,2.6.35-sabayon
>> Homepage: http://www.virtualbox.org/
>> Description: VirtualBox kernel modules and
>> user-space tools for Linux guests
>> License: GPL-2
>> @@ Package: net-wireless/broadcom-sta-5.60.48.36-r1#2.6.35-sabayon branch: 5, [__system__]
>> Installed: version: 5.60.48.36-r1 ~ tag: 2.6.35-sabayon ~ revision: 2
>> Slot: 0,2.6.35-sabayon
>> Homepage: http://www.broadcom.com/support/802.11/linux_sta.php
>> Description: Broadcom's IEEE 802.11a/b/g/n
>> hybrid Linux device driver.
>> License: Broadcom
>> @@ Package: net-wireless/ndiswrapper-1.56#2.6.35-sabayon branch: 5, [__system__]
>> Installed: version: 1.56 ~ tag: 2.6.35-sabayon ~ revision: 2
>> Slot: 0,2.6.35-sabayon
>> Homepage: http://ndiswrapper.sourceforge.net/
>> Description: Wrapper for using Windows drivers
>> for some wireless cards
>> License: GPL-2
>> @@ Package: x11-drivers/ati-drivers-10.8#2.6.35-sabayon branch: 5, [__system__]
>> Installed: version: 10.8 ~ tag: 2.6.35-sabayon ~ revision: 1
>> Slot: 1,2.6.35-sabayon
>> Homepage: http://www.ati.com
>> Description: Ati precompiled drivers for r600
>> (HD Series) and newer chipsets
>> License: AMD GPL-2 QPL-1.0 as-is
>> @@ Package: x11-drivers/nvidia-drivers-256.53#2.6.35-sabayon branch: 5, [__system__]
>> Installed: version: 256.53 ~ tag: 2.6.35-sabayon ~ revision: 1
>> Slot: 0,2.6.35-sabayon
>> Homepage: http://www.nvidia.com/
>> Description: NVIDIA X11 driver and GLX libraries
>> License: NVIDIA
>> @@ Package: x11-drivers/xf86-video-virtualbox-3.2.8#2.6.35-sabayon branch: 5, [__system__]
>> Installed: version: 3.2.8 ~ tag: 2.6.35-sabayon ~ revision: 2
>> Slot: 0,2.6.35-sabayon
>> Homepage: http://www.virtualbox.org/
>> Description: VirtualBox video driver
>> License: GPL-2
>> Keyword: 2.6.35-sabayon
>> Found: 6 entries</pre>}}

In fact, one could filter the package names out of that by using grep like so:

{{Console| <pre class="clear"># equo query installed 2.6.35-sabayon | grep '#'</pre>}}

For example:

{{Console| <pre class="clear"># equo query installed 2.6.35-sabayon | grep '#'
>> @@ Package: app-emulation/virtualbox-guest-additions-3.2.8#2.6.35-sabayon branch: 5, [__system__]
>> @@ Package: net-wireless/broadcom-sta-5.60.48.36-r1#2.6.35-sabayon branch: 5, [__system__]
>> @@ Package: net-wireless/ndiswrapper-1.56#2.6.35-sabayon branch: 5, [__system__]
>> @@ Package: x11-drivers/ati-drivers-10.8#2.6.35-sabayon branch: 5, [__system__]
>> @@ Package: x11-drivers/nvidia-drivers-256.53#2.6.35-sabayon branch: 5, [__system__]
>> @@ Package: x11-drivers/xf86-video-virtualbox-3.2.8#2.6.35-sabayon branch: 5, [__system__]</pre>}}

''Fitzcarraldo'', Mon Dec 20 03:44:55 GMT 2010

==================================================================================================

I have incorporated your suggestion, ''Thompson'', along with the filters I mentioned above. Thanks for taking the time to comment.

BTW, if you want to edit the article and make the examples consistent (they are for a hotchpotch of kernel versions at the moment) then please feel free. You might want to update the examples to cover e.g. originally-installed kernel is 2.6.35 and kernel to be installed is 2.6.36.

''Fitzcarraldo'', Tue Dec 21 20:01:41 GMT 2010

==================================================================================================

HOWTO: chroot from a LiveCD

2010-12-11T09:54:42Z

Fitzcarraldo: Added note about logging in as the root user.

Boot a Sabayon Linux LiveCD/DVD or other Live disc. Get to a virtual terminal (console) or open a Konsole/Terminal window on the Desktop, and log-in as the root user.

{{Warning|Make sure the LiveCD/DVD you use is for the same architecture as the architecture of the installation on the hard disk, i.e. to chroot to a 64-bit installation (e.g. amd64) you cannot use a 32-bit LiveCD/DVD (e.g. x86), and vice versa. You will see an error message "chroot: cannot run command `/bin/bash': Exec format error" if you try to chroot from a LiveCD/DVD of a different architecture.}}

{{Note|Whilst it is possible to mount filesystems from within the chrooted system, this is not recommended. The reason for this is that the LiveCD/DVD environment won't know about these mounted systems, so if you forget about them and leave them mounted when you exit from the chroot environment, they will not be unmounted properly when the system shuts down, which could cause damage to the filesystems on those mounts.}}

Mount the root partition of the installed system (and, if you have /boot on a separate partition, mount that too). If separate partitions are used for other areas of the system (for example, a separate partition for /var/log) then you will need to mount them too. Additionally, mount the /dev and /proc filesystems so that they can be used by the chrooted environment.

In the following example, /dev/hda1 is the /boot partition and /dev/hda3 is the root partition. Obviously replace those with the device names for ''your'' boot partition (if you have one) and ''your'' root partition. If your partition names are of the form /dev/'''s'''d<letter><number> rather than /dev/'''h'''d<letter><number> then obviously use that form instead. Obviously, if you do not have /boot on a separate partition to / (root) then you should omit the mount and umount commands referring to /boot.

{{Console| <pre class="clear"># mkdir -p /mnt/sabayon/boot
# mount /dev/hda3 /mnt/sabayon
# mount /dev/hda1 /mnt/sabayon/boot
# mount -t proc none /mnt/sabayon/proc
# mount -o bind /dev /mnt/sabayon/dev</pre>}}

So now we are set to enter into our installed system:

{{Console| <pre class="clear"># chroot /mnt/sabayon /bin/bash
# env-update
# source /etc/profile
# export PS1="(chroot) $PS1"</pre>}}

You should then end up with the following prompt:

{{Console| <pre class="clear">(chroot) #</pre>}}

Grub2 reads the /etc/mtab file to ascertain the filesystems that are currently mounted, so /etc/mtab must be up-to-date. If you do '''not''' have a separate boot partition then update /etc/mtab using the following command:

{{Console| <pre class="clear">(chroot) # grep -v rootfs /proc/mounts > /etc/mtab</pre>}}

or the following command if you '''do''' have a separate boot partition:

{{Console| <pre class="clear">(chroot) # cp /proc/mounts /etc/mtab</pre>}}

From now on, you can enter commands as if you were using your installed system directly. You could, for example, install a package by using either the equo or emerge commands. The ability to act directly on the installed system like this is very useful in the event that something is broken and you cannot boot to a working system. You might want to revert to an earlier version of a video driver that you know works, or you might want to fix the kernel config and rebuild it because a change you made to the kernel earlier resulted in a kernel panic when you rebooted. And so on.

{{Console| <pre class="clear">(chroot) # <enter any command you want></pre>}}

Once you have finished, you can exit from the chroot environment and unmount the drives:

{{Console| <pre class="clear">(chroot) # exit
# umount /mnt/sabayon/boot /mnt/sabayon/dev /mnt/sabayon/proc /mnt/sabayon</pre>}}

Reboot the PC. If your actions during the chroot session were successful then your installed system should boot normally.

En:HOWTO: Run Sabayon Without Burning The Image

2010-10-11T08:51:41Z

Fitzcarraldo: Replaced update-grub command. Pointed out by someone in the SL Forums.

{{Note|If you are looking for installing via USB please see the [http://unetbootin.org Unetbootin homepage], this guide if for installing from a hard disk partition.}}

If you do not have a correctly working DVD writer or no blank DVDs then this guide is to show you how to install using a spare partition on your hard drive.

First, you need to ensure that you have a free partition of at least 5 gigs. Mine is /dev/sda4. I used the gparted bootable CD to shrink /dev/sda3.

Make an ext2 (or ext3 or ext4) filesystem on this partition

{{Console|<pre class = "clear"># mkfs -t ext2 /dev/sda4</pre>}}

Make two separate mountpoints. I used /mnt/iso and /mnt/sda4

{{Console|<pre class = "clear"># mkdir /mnt/iso /mnt/sda4</pre>}}

Mount the ISO and partition

{{Console|<pre class = "clear"># mount -t iso9660 -o ro,loop=/dev/loop0 /home/jvj/Sabayon-Linux-x86-3.5_Loop2-r2.iso /mnt/iso
# mount /dev/sda4 /mnt/sda4</pre>}}

Copy the files from the mounted ISO to the mounted partition:
{{Console|<pre class="clear"># cp -rvp /mnt/iso/* /mnt/sda4</pre>}}

'''Grub1:'''
''On releases < Sabayon 5.2, or any distribution that uses Grub 1 (grub legacy)''

Once the files have all copied, cd to /boot/grub/

{{Console|<pre class = "clear"># cd /boot/grub/</pre>}}

and add these lines to grub.conf: (note that because of line-wrapping the line that starts with kernel ends with --)
{{File|(/boot/grub/grub.conf)|<pre class="clear">...
...
title Sabayon Linux x86 Test
root (hd0,3)
kernel /boot/sabayon root=/dev/ram0 aufs init=/linuxrc cdroot=/dev/sda4 looptype=squashfs max_loop=64 loop=/livecd.squashfs splash=silent,theme:sabayon vga=791 CONSOLE=/dev/tty1 music quiet --
initrd /boot/sabayon.igz</pre>}}

(Save grub.conf, and run grub-install (again assuming sda is your root drive):
{{Console|<pre class = "clear"># grub-install /dev/sda</pre>}}

'''Grub2:'''
''Since Sabayon 5.2 (or any distribution that uses GRUB 2)''

If you followed this HOWTO thoroughly and successfully installed Sabayon from a HDD partition, but for some reason cannot boot a newly installed system, or just want to reinstall it again from that HDD partition, or even if you haven't installed Sabayon yet, here is how you can boot to installation partition directly from GRUB2 boot screen:

Add this to /etc/grub.d/40_custom under the comment line, at the end of the file :

{{File|(/etc/grub.d/40_custom)|<pre class="clear">
menuentry "Sabayon install" {
set root=(hd0,7)
linux /boot/sabayon root=/dev/ram0 aufs init=/linuxrc cdroot=/dev/sda7 looptype=squashfs max_loop=64 loop=/livecd.squashfs splash=verbose quiet
initrd /boot/sabayon.igz
}
</pre>}}

Don't forget to type in the right partition (/dev/sda7 in this example, which corresponds to root=(0,7) ).

After that, run '''grub-mkconfig -o /boot/grub/grub.cfg''' as root, and reboot the machine. Launch the GRUB menu by pressing the left shift key just after the BIOS screen, and select "Sabayon install".

En:HOWTO: Setting Up Autologin

2010-10-06T12:17:00Z

Fitzcarraldo: Added item about removing sabayon-mce from system runlevels (still reported as a problem in SL 5.4 and good to mention anyway. Also tidied some text up.

{{I18n| [[En:HOWTO:_Setting_Up_Autologin|en]] [[It:HOWTO:_Setting_Up_Autologin|it]] [[Tr:NASIL: Otomatik girişi etkinleştirme|tr]]}}
{{Warning|<center>'''Never''' ever enable Autologin for root!</center>}}

This Howto will help you setting up your Autologin, so that you will need no more to authenticate in a login prompt. 
Be aware that this is a security risk, since anyone will be able to get access to your computer with no need of any password or authorization, this is intended just for home computers.

= Setting Up Autologin in KDE4 =

Some users reported the inability to set up the Autologin from within the KDE Control Center, they reported the page to be grayed out, with the message: 
"There is no login dialog in themed mode" 
If it is not your case, then setting the Autologin with the Control Center is the recommended way, otherwise proceed with the Howto.

'''1.''' Become root with the ''su'' command in your favourite console application, for example "Konsole".
{{Console| <pre class="clear">su</pre>}}
Type in your root password.

'''2.''' Make sure that the Sabayon Media Centre init script is not in a system runlevel:
{{Console| <pre class="clear">rc-update del sabayon-mce boot
rc-update del sabayon-mce default</pre>}}

'''3.''' Open up the ''kdmrc'' file with your favourite editor, we will use ''kwrite'' in this example. 
The ''kdmrc'' file is usually located in: ''/usr/kde/4.2/share/config/kdm/kdmrc'' 

If it is not there, try to find it with the locate command:
{{Console| <pre class="clear">locate kdmrc</pre>}}
or the find command:
{{Console| <pre class="clear">find / -name kdmrc</pre>}}

In this example we will suppose that it is located at ''/usr/kde/4.2/share/config/kdm/kdmrc''. 

Now we will open it up with ''kwrite'':
{{Console| <pre class="clear">kwrite /usr/kde/4.2/share/config/kdm/kdmrc</pre>}}

Notice that KDE4 may require the full path to "kwrite", in this case you will receive an error message:
{{Console| <pre class="clear"># kwrite
bash: kwrite: command not found</pre>}}

You could use "nano" instead:
{{Console| <pre class="clear">nano /usr/kde/4.2/share/config/kdm/kdmrc</pre>}}

or launch "kwrite" using "kdesu" '''from your normal user account, not the root user account''':
{{Console| <pre class="clear">kdesu kwrite /usr/kde/4.2/share/config/kdm/kdmrc</pre>}}

'''4.''' Now we are going to setup our preferences, we can notice a section in this file with the Autologin preferences; these lines are commented. 
Commented lines are marked with a '#', and are ignored; if a preference is commented, it is going to be used the default configuration for that setting. 

The relevant lines for our purpose are:
{{Console| <pre class="clear">#AutoLoginEnable=true</pre>}}
and
{{Console| <pre class="clear">#AutoLoginUser=fred</pre>}}
We want them to enable the Autologin with our default user, assume that the default user we want to Autologin is ''micia''. 
We set ''#AutoLoginEnable=true'' to:
{{Console| <pre class="clear">AutoLoginEnable=true</pre>}}
So that the preference is no more ignored, and we set ''#AutoLoginUser=fred'' to:
{{Console| <pre class="clear">AutoLoginUser=micia</pre>}}

This is it, save the file, reboot, and see if it worked.

= Setting Up Autologin for Gnome (GDM) =

This is an easy one, just use ''gdmsetup'' to configure your preferences. 
You have to run it as ''root'', so, as usual:

'''1.''' Open up your favourite console application, for example ''gnome-terminal'' and type:
{{Console| <pre class="clear">su</pre>}}
Now type in your root password.

'''2.''' Make sure that the Sabayon Media Centre init script is not in a system runlevel:
{{Console| <pre class="clear">rc-update del sabayon-mce boot
rc-update del sabayon-mce default</pre>}}

'''3.''' Run ''gdmsetup'':
{{Console| <pre class="clear">gdmsetup</pre>}}
And enable Automatic Login for your user.

Someone reported that ''gdmsetup'' was not in their root $PATH variable, if this is your case executing ''gdmsetup'' should output something like:
{{Console| <pre class="clear">il-padre-mobile micia # gdmsetup
bash: gdmsetup: command not found</pre>}}
You will need to find the ''gdmsetup'' executable, with ''locate'' or ''find'' as above, for example using ''find'':
{{Console| <pre class="clear">find / -name gdmsetup</pre>}}
Suppose that the result is:
{{Console| <pre class="clear"># find / -name gdmsetup
/usr/sbin/gdmsetup
/etc/security/console.apps/gdmsetup
/etc/pam.d/gdmsetup</pre>}}
Obviously the one which interests us is ''/usr/sbin/gdmsetup'', we then execute it explicitly with:
{{Console| <pre class="clear">/usr/sbin/gdmsetup</pre>}}

This should work for the GDM Display Manager. 
I hope this will help someone, good luck!

HOWTO: Vista printer sharing

2010-08-18T15:24:38Z

Fitzcarraldo: Reformatted to use Wiki numbering hash code.

'''How to enable Sabayon Linux 4.0-r1 to use a printer connected to a PC running Windows Vista on your network'''

{{Note|Example entries are shown in quotation marks. You do not actually type the quotation marks.}}

a) In /etc/samba/smb.conf make sure the home network workgroup name is the same as the name of the Workgroup configured in the Vista PC (which is "WORKGROUP", without the quotes, in my case).

b) Enable Authentication in Vista Home Edition (see item c below if you have Vista Business, Ultimate, or Enterprise)

#Start the Registry Editor by selecting Start, All Programs, Accessories, Run.
#In the ‘Open’ field of the Run dialog box, type regedit and click the ‘OK’ button.
#The User Account Control system will ask for permission to continue. Click the ‘Continue’ button.
#In the Registry window, expand the following:
##HKEY_LOCAL_MACHINE
##SYSTEM
##CurrentControlSet
##Control
##Lsa
#In the ‘Value’ pane of the Registry Editor, check to see if the following DWORD exists: lmcompatibilitylevel. If it does, perform the following:
##Right-click lmcompatibilitylevel and select ‘Modify’ from the pop-up menu.
##Enter a Value data of 1.
##Click the ‘OK’ button.
#If the lmcompatibilitylevel DWORD does not exist, create a new DWORD.
##From the Registry Editor menu, select Edit, New, DWORD (32-bit) Value.
##A new DWORD called ‘New Value #1’ will be created.
##Rename the new DWORD to lmcompatibilitylevel.
##Right-click lmcompatibilitylevel and select ‘Modify’ from the pop-up menu.
##Enter a Value data of 1.
##Click the ‘OK’ button.
#Restart your Windows Vista computer.

c) Enable Authentication in Vista Business, Ultimate, and Enterprise (see item b above if you have Vista Home Edition)

#Start the Group Policy Editor by selecting Start, All Programs, Accessories, Run.
#In the ‘Open’ field of the Run dialog box, type gpedit.msc and click the ‘OK’ button.
#The User Account Control system will ask for permission to continue. Click the ‘Continue’ button.
#Expand the following objects in the Group Policy Editor:
##Computer Configuration
##Windows Settings
##Security Settings
##Local Policies
##Security Options
#Right-click the ‘Network security: LAN Manager authentication level’ policy item, and select ‘Properties’ from the pop-up menu.
#Select the ‘Local Security Settings’ tab.
#Select ‘Send LM & NTLM – user NTLMv2 session security if negotiated’ from the dropdown menu.
#Click the ‘OK’ button.
#Close the Group Policy Editor.
#Restart your Windows Vista computer.

d) Enable Printer Sharing in Windows Vista

#Select ‘Control Panel' from the Start menu.
#Select ‘Printer’ from the Hardware and Sound group.
#A list of installed printers and faxes will display.
#Right-click on the icon of the printer you wish to share and select ‘Sharing’ from the pop-up menu.
#Click the ‘Change sharing options’ button.
#The User Account Control system will ask for permission to continue. Click the ‘Continue’ button.
#Place a check mark next to the ‘Share this printer’ item.
#Enter a name for the printer in the ‘Share name’ field (do not use any spaces). This is the name that you will enter as part of the device URI on your Sabayon Linux PC.
#Click the ‘Apply’ button.
#Close the printer’s Properties window and the Printers and Faxes window.

e) Make sure the firewall software (Norton, Kaspersky, McAfee, AVG or whatever) on the Vista PC is configured to enable incoming network traffic from Local Network i.e. your home network. For example, I configured Kaspersky Internet Security to allow TCP/IP and UDP traffic from my Local Network (both were disabled by default).

f) Add the Shared Printer to your Sabayon Linux PC

#Right-click on the Desktop and select 'Create New > Link to Location (URL)...' to create a Desktop Config File (desktop icon) for the URL http://localhost:631/, and call it CUPS. You can click on the icon in the Properties window and select the CUPS icon too.
#Launch the CUPS browser interface by double-clicking on the desktop icon you just created.
#Click on 'Add Printer'.
#Fill in the 'Name' field (no spaces allowed: e.g. "Canon_MP510_Printer").
#Fill in the 'Location' field (e.g. "Connected to Acer SA90 in Lounge").
#Fill in the 'Description' field (e.g. "Canon MP510"). Click on 'Continue'.
#Select 'Device:' as 'Windows Printer via SAMBA'. Click on 'Continue'.
#Enter 'Device URI:'. In my case I entered "smb://WORKGROUP/SA90/Canon_MP510_Printer" because "WORKGROUP" is the Windows Workgroup defined on my Vista PC, "SA90" is the name of the Vista PC defined on my Vista PC, and "Canon_MP510_Printer" is the name of the shared printer defined on my Vista PC. Click on 'Continue'.
#Select the 'Make' of printer from the list and click 'Continue'.
#Select the 'Model' of printer from the list and click 'Continue'. (In my case my printer's driver was not installed by default with Sabayon Linux 4.0-r1, so I had to install it myself before carrying out this procedure -- see my post on the Canon MP510 printer in the Sabayon Linux Forums for details.)
#Enter "root" as the 'Username' and enter the root 'Password'.
#Wait for the printer details to appear in the CUPS browser window (or click on the 'Printers' tab).
#Click on 'Set Printer Options' and select what options you want (e.g. 'Paper Feed: Front Feeder' for the Canon MP510). Click on 'Set Printer Options'.
#Click on 'Print Test Page' to make sure everything is working correctly.

Article created by Fitzcarraldo on 7 January 2009, with acknowledgement to Tom Nelson of About.com:Macs for the instructions about configuring the Vista end (see http://macs.about.com/od/macwindows/ss/printsharevista.htm).

[[Category:Printing|Vista printer sharing]]

Getting Help In IRC

2010-06-23T16:30:50Z

Fitzcarraldo: Corrected "english" to "English".

==How to get useful help on IRC==

IRC (Internet Relay Chat) is a real-time chat where you can talk to other people from around the planet. Although many channels deal with smalltalk about the weather, girl-friends and politics there are IRC networks and channels that are dedicated to provide support for a piece of software or an operating system. irc.freenode.net for example exists to support open-source projects. If you are in a help channel, please do your best to stay on topic. The IRC channel is not there for social interaction, it's for technical support. This means technical support in relation to Sabayon, we are not here to support other distros, or help you with your homework. We also will not help you with items of questionable legal integrity. Please stay calm, and do not start yelling or throwing tantrums if someone doesn't respond how you want them to. In case you need urgent help, or need something on the Sabayon Forums or Sabayon Wiki further clarified. This page will provide you with some very good guidelines to make the most out of using the #sabayon IRC channel (which is also the same thing as the webchat/get live help link)

==Don't ask to ask==

It's a bad manner if someone enters a channel and asks "May I ask a question?" or "Can anyone help me?". Although that may be polite in normal human interaction it does not work that way on IRC. You are simply supposed to just ask your question right away. Remember while this is real-time interaction, people in IRC are frequently multi-tasking. Please be patient, and someone will get to your question eventually. If necessary, go grab a drink and a snack, and come back to the computer. Being impatient and leaving in less than 2 minutes doesn't give anyone much of a chance to answer your question.

==Do not repeat yourself==

Asking the same question every minute is annoying. If anyone in the channel isn't paying attention then they will not read you the second and third time. Those who came back from lunch or sleep will likely see in their scrollback or lastlog what has happened lately. This is demanding and is poor IRC etiquette. Repetition may get you ignored.

==Answer the questions that you get asked==

It may sometimes be hard to follow all the conversation on IRC, but if people are trying to help you and need to ask you a few questions, please answer them all. Frequently this information is necessary to know how to answer your questions or what solution is necessary. It is not uncommon for things to be different between two different versions of a distro or program, or even under different architectures. If you get asked three questions and only answer one or keep asking the same question time and again (showing that you don't read what you get asked) you risk to be ignored. Show some initiative and your problem will likely be fixed within a few minutes. If you believe you have answered a question, and the people helping you REPEAT the question, it most likely means that you have given insufficient information. Please keep in mind, if someone asks you a version number, latest, and most recent are NOT version numbers. If you are unsure of how to get the information to answer the questions you are asked, PLEASE ask how. We are not mind-readers in IRC. In addition, please do not leave those who are helping you waiting for long periods. We are volunteers who choose to help. If you do not respond in a timely manner, we will assume that we're being ignored and move on to someone or something else.

==Be precise==

There is nothing worse than "My printer doesn't work." or "My mail server doesn't work.". How are others supposed to help you when you don't give them any information? Make sure you include at least this information:

* What did you try to accomplish? (I wanted to fetch my mails via POP3.)
* What has happened (wrongly) instead? (But my inbox remains empty.)
* What environment are you using? (I am using kmail 1.8 in KDE 3.4.)
* What did you try to find the cause? (I already checked my POP3 account setup.)
* Are there error message or log files? (The error message reads: "SSL negotiation failed.")
* Has it ever worked? What did you change? (I switched accounts to a new provider. It worked before with another provider.)

If all this information is included then you will have a high chance of getting a useful reply. If you are unsure of how to provide proper information to us to help you solve your problem, we will tell you what commands to run, but if you do know, pastebinning the output of a few commands in advance would be of great help. lspci, lsusb, eselect opengl list, eselect kernel list, uname -a, lsmod, ifconfig, iwconfig are commands that you would be commonly asked for the output of, as well as knowing what version of Sabayon you are running. Keep in mind there are usually several varieties of a version in circulation; 2 Editions per architecture (ie. A 32 bit DVD and CD, as well as a 64 bit DVD and CD, and if there were public betas that means there are additional DVD's with a particular version numbers. Betas will usually be called loop)

Please note that many of the information gathering commands need to be run as root.
[http://wiki.sabayonlinux.org/index.php?title=Getting_Help_In_IRC#Do_not_flood_the_channel_-_use_a_pastebin Please click here for explanation of a pastebin.]

==Tell what you are doing==

Others only know what you tell them. If you change things silently then nobody will know about it. The worst thing you can do is say: "I changed something. Now I have another problem." This will get you ignored quickly. If you expect help you need to work with the supporters. Please help us to help you.
Also, if you are having problems and working off a HOWTO page, please supply us with the URL so we can be looking at the same thing you are.

==Write, Log or Print ==

If you have received help, please write down, print, or make a logfile of all the steps you took to fix your situation. There is nothing worse than helping someone, and having to repeatedly walk them through the same steps over and over again. It shows a lack of willingness to learn and or follow directions, and shows the people who have helped you that they have wasted time.

==Read the /topic==

Your IRC client will likely show you the "topic" of a channel when you enter it. If you have missed it, most clients will give you a recap if you type "/topic". You will find items of importance to the channel, and may also find links to documentation. Asking something that is clearly answered in the topic is poor form. If there are FAQ URLs listed in the topic, look there first to see if you can find the answer to your question.

==Do not be demanding==

Do not expect a single person to stay online until your problem is fixed. IRC is a stateless medium. Anyone can quit at any time. People stay there because they like staying there. Nobody is paid for helping you. Instead it's a behavior that will likely get people to ignore you, or worse, for you to get kicked out of the channel. We are all volunteers, please do not abuse us.

==Don't Rush Things==

There is a chance that sometimes the solution to your problem may take some time. It is best not to rush through things. You won't remember if you rush, and you're at risk of making mistakes if you rush. When asking for help, please be able to take the time that is necessary to get your problem solved. Not everything has a quick fix. Things that are guaranteed to take some time are initial synchronisation of the package managers and world updates. Please do not start these if you cannot let them finish. For certain things it's fine to leave the computer doing it's own thing while you go do others, then pick up where you left off, but do not start a world update if you cannot let it take the time to finish, as you risk causing major system problems.

==Do not /msg people without asking==

You can either talk to others in a channel publicly or /msg them privately. However the doing the latter without permissions is considered rude. Don't monopolise a single person for your purpose. Others may also be interested in the solution to your problem, or they may have alternative solutions.

==Unintended rudeness==

Sometimes you may feel that others are rude. You may get a response like "Reinstall the package. Restart the service. Read the /usr/share/doc/mysoftware/README." Although this is a very brief reply it is likely not meant to be rude. IRC is often like human interaction without all the friendly bits. Other people have probably answered your question a dozen of times today and they just want to help you solve the problem - not become close friends with you. Don't be offended by it. The people don't mean it.

==Speak English==

In most channels the language spoken is English. This is generally due to the fact that there are people from all around the World, and it tends to be the common language shared between most people. It doesn't matter if your English is bad. Most people in the World speak something different than English, too. And if you find another person that speaks your language then do not start to talk in your local language in channel. Nobody else can follow you and it's considered rude. If you are insecure with English, you can use a web-translator. It doesn't always give the best results, but it breaks down the barriers. Please visit the following link if you need IRC Translation. [[HOWTO: IRC Translation]]

==Don't be lazy - read the documentation==

If people tell you to read the documentation then you should do so. Never say: "I'm too lazy. Come on. You all know what I need to do. Just tell me what I need to do." or "I clicked on Live Help" then cop an attitude of entitlement. This will get you ignored for all eternity. However, you can expect to be told where to find the documentation. If you get an URL, load it and read it. It is difficult to help people who refuse to help themselves. If you make an effort, this will go far with everyone. If after reading, the documentation is too technical or you don't understand certain sections then say so. We are more than happy to clarify information, if you're making an effort to help yourself. People who are repeatedly lazy get remembered and generally ignored.

In general, IRC should be your last stop for help. Sabayon has very active forums and a rather complete wiki. Because Sabayon is also a gentoo based distro, you can find plenty of help on their forums and wiki as well. Please make use of these first, then if something is confusing to you or if you want to verify something, that is considered proper use of IRC help. The bugtrackers for sabayon and gentoo are also good places to look, and always remember, google is your friend.

==Follow Directions==

When you are getting help in the IRC channel, if people are telling you to run commands, please do not get creative with them. Cut and paste them from IRC into your terminal. If we give you commands to run, the EXACT syntax needs to be followed, and if we ask for the output of a command, we need you to give us the EXACT output. Linux is case sensitive, meaning that lspci, LSPCI and Lspci are three different things to your system, and only one of them is right. Spelling and punctuation are important. Many commands given in help channels are chained or piped commands, so the && and | symbols you see are not there for decoration. they're part of the command. Also, if something is given in quotes, it's generally to set it apart from the rest of the sentence, leave off the quotes unless you're told otherwise. Also, you will frequently see nopaste as being part of a command. This is a script which will take the output of the command you are running and pipe it to a pastebin so we can see what's happening. Please keep in mind, a large proportion of the commands we will be giving you to run, need to be ran as root. Please use su instead of sudo to become root. Also, please keep in mind that most GUI interfaces are not meant to be run as root, so you will get "command not found" when attempting to do that, similarly to when you would try to run a command that needs to be run as root as user.

In addition, if we have given you a howto guide to follow or a link explaining the solution to your problem please read it fully before applying your solution. Many of the howto's start from a point where you don't have a particular thing installed, and there's a bit that you can skip over in them. Please do feel free to ask, especially if we're telling you a necessary component is installed and the howto guide is telling you to install it.

==Stay if you can==

Using IRC is a matter of give and take. At the beginning you will surely you'll have questions over questions. Just ask them and be grateful if you get attention and replies. Others do not expect more than a "Thank you." for their help.

If you can, please consider staying online in the channel. The more knowledge you gain the more you can help other people. And you probably get to know people you like to hang out with - even if it's just virtually. It's perfectly fine to leave yourself lurking in a help channel. Chances are if you go through your scrollback, you'll learn something new. Even the experts find this to be true!

==Tell others about the solution==

If you have been having a challenging problem, it doesn't help anyone if you just say "Nevermind, found it." and quit the channel. Please tell the others what the solution to your problem was so everybody can learn from it.

==Do not flood the channel - use a pastebin==

Sometimes you need to show others more than one line. Perhaps parts of your configuration files or a log file. Never just copy and paste larger amounts of text right into the channel. Always use a pastebin. Pastebins are public services (web sites) where you can paste your text and everybody can access them as a URL. Just paste your contents there and send the URL into the channel. That should allow everybody who's interested to take a look. Just don't paste it without any comment.

Common pastebins are as follows, please choose one. No need to post your problem to ALL of them:
* http://www.rafb.net
* http://www.pastebin.com
* http://www.pastie.org
* http://nopaste.com
* http://papernapkin.org
* http://nopaste.info
* http://dpaste.com
* http://1t2.us/

==Not everybody is an expert==

When getting responses be careful about who you trust. While malicious "helpers" are very rare in #Sabayon, we haven't been without some problem users in the past. Most of the people helping in the channel know what they're doing. If people are opped or voiced, you can be guaranteed they will not give you malicious commands to run. If you are unsure about what you are running, it's fine to ask the purpose of a command. You can also get a list of malicious commands if you type "?? malicious" in channel (minus the quotes of course) and the bot will give you a link regarding that.Some people just want to feel important and reply to you although they have no more clue than you do. Some people are even jokers who want to be funny by telling you how to erase your harddisk. Malicious helpers will be banned.

==ACKNOWLEDGEMENTS==
My thanks to the people at workaround.com for providing me with a wonderful link to plagiarise. While the article appearing here has been edited in some places, there is still some of the original work left. The original workaround.com link may be found [http://workaround.org/moin/GettingHelpOnIrc here.] Pardon the poor spacing. What I added was spaced properly, but the original article was single spaced. I put additional spaces between sentences where I spotted it, but I"m sure I didn't catch them all.

-- Lythandrel

HOWTO: PyKaraoke

2010-06-21T20:05:19Z

Fitzcarraldo: Updated for latest version (0.7.3) of PyKaraoke, and KDE 4

{{Warning| '''This article uses Portage. Do not proceed if you have no idea what Portage is.'''}}
'''How to install the PyKaraoke application for playing karaoke files under Sabayon Linux'''

{{Note|The two alternatives for playing karaoke files in Linux are KMid and PyKaraoke. Earlier versions of KMid did not support international characters or diacritics (accents), but the latest versions do. PyKaraoke also supports international characters and diacritics.}}

PyKaraoke can play CDG (.mp3+.cdg, .ogg+.cdg, .wav+.cdg), MIDI (.mid/.kar) and MPEG (.mpg) karaoke files. You can read about PyKaraoke (Python Powered Karaoke) on its home page http://www.kibosh.org/pykaraoke/

Open a Terminal window, log-in as the root user and follow the steps below.

1. Install the Timidity MIDI player if it is not already installed:

{{Console| <pre class="clear">emerge -1v timidity++</pre>}}

2. Install the Timidity patches required by PyKaraoke:

{{Console| <pre class="clear">emerge -1v timidity-eawpatches</pre>}}

3. Install sdl-mixer with the timidity USE flag (and mp3 USE flag if you will want to play mp3 files using PyKaraoke):

{{Console| <pre class="clear">USE="mp3 timidity" emerge -1v sdl-mixer</pre>}}

{{Note|The package sdl-mixer was already installed when I installed Sabayon Linux, but I was getting the message "Error opening file. <class 'pygame.error'> Module format not recognized" from PyKaraoke when I tried to play a .mid or .kar file. It was because sdl-mixer had been compiled without the timidity USE flag, hence the recompile of sdl-mixer shown above.}}

4. Use your favourite text editor and add the following line to /etc/make.conf if it's not there already:

{{File|/etc/make.conf| <pre class="clear">PORTDIR_OVERLAY="${PORTDIR_OVERLAY} /usr/local/portage/"</pre>}}

5. Create a directory to store a local ebuild for PyKaraoke:

{{Console| <pre class="clear">mkdir -p /usr/local/portage/media-sound/pykaraoke</pre>}}

6. Download the ebuild file pykaraoke-0.7.1.ebuild from Gentoo Bugzilla Report No. 137415 and copy it to /usr/local/portage/media-sound/pykaraoke/pykaraoke-0.7.3.ebuild (notice that it is renamed).

7. Download the file pykaraoke-0.7.3.zip from the Download page of the above-mentioned PyKaraoke Web site and copy it to the directory /usr/portage/distfiles/

8. Install the PyKaraoke package:

{{Console| <pre class="clear">emerge -1v pykaraoke</pre>}}

If an error message is displayed stating that the pakage is masked by missing keyword, edit as root user the file /etc/portage/package.keyword and add the following line:
{{File|/etc/portage/package.keyword|<pre class="clear">~media-sound/pykaraoke-0.7.3 **</pre>}}

{{Note|A PyKaraoke icon will automatically be added to Kickoff > Applications > Multimedia, so you can launch PyKaraoke using that, or just enter the command pykaraoke at the command line if you prefer.}}

Article created by Fitzcarraldo on 10 April 2009.

[[Category:Multimedia|PyKaraoke]]

Sabayon Linux2

2010-06-08T14:35:30Z

Fitzcarraldo: Updated password instructions for LiveDVD.

=Sabayon Linux Overview=
== '''What is Sabayon Linux''' ==

== Real World Equivalent ==

"Sabayon is an Italian dessert made with egg yolks, sugar, a sweet liquor (usually Marsala wine), and sometimes cream or whole eggs. It is a very light custard, which has been whipped to incorporate a large amount of air."

Source: [http://en.wikipedia.org/wiki/Sabayon Wikipedia].

== Real theory ==

[http://en.wikipedia.org/wiki/Sabayon_Linux Sabayon Linux] is an ''Operating System'', just like Windows, powered by the [http://www.kernel.org Linux Kernel], [http://www.gnu.org GNU] and built from the users' side. There are many "Linux" flavours, geeks usually call them "[http://en.wikipedia.org/wiki/Linux_distribution distributions]". We are a Linux distribution though. Even if Linux is known to not be as simple as the commercial counterparts in some (and few) cases, we are trying to provide to our users the best and most complete '''Computing Experience'''.

Our philosophy follows two simple statements:

''a)'' '''Out of the box functionalities''': In a perfect World, everything should work without human intervention

''b)'' '''KISS''': '''K'''eep '''I'''t '''S'''imple '''S'''tupid! That's self-explanatory

Moreover, to achieve this, believe it or not, ''Sabayon Linux'' uses [http://en.wikipedia.org/wiki/Gentoo_linux Gentoo Linux] as its base. It is (and it will always be) ''100% compatible'' with it. We are one of the most ''scalable'' distributions and are happy to support everyone from the most creative kernel hacker to the newbie of the newbies. Why do we say that? Because of point ''a)'' above and because [http://en.wikipedia.org/wiki/Gentoo_linux Gentoo Linux], is the ''most extensible'' Linux distribution. No one can say anything to the contrary.

== '''What is ''not'' Sabayon Linux''' ==

* It is not a '''binary-only''' distribution. Yes, you can install '''Sabayon Linux''' in half an hour and have a powerful Desktop under your hands. But our current policy does not mind the idea to fork Gentoo Linux packages management only because users don't like to waste their time with compilations. We have a clear idea, if you don't want to compile a lot of packages just wait for the next release, because, you always be able to:
** Update your current installation to the latest '''Sabayon Linux''' by running the ''Installer'' and choosing the ''Upgrade'' option
** Keeping up to date. '''Sabayon Linux''' release cycles are very very short. And if you just want to keep your PC secure, just use the ''glsa-check'' utility.

* It is '''not''' developed with politics in mind. This means that if we like an application over another, it's just because it could work better and be closer to our '''out-of-the-box''' philosophy described above.

* It is '''not''' Company driven. We have always been first of all, users, and then developers. That's our power and our view. We only want something that gets the job done, without Microsoft and their superficial Operating System implementation.

* It is '''not''' Ubuntu! We don't try to mimic any other distribution. We just take the best from each one.

== '''Why this name?''' ==

== '''Why Sabayon Linux is different from other distributions?''' ==
* Sabayon offers a complete out-of-the-box experience. This means it comes with preinstalled Multimedia, Internet and Gaming Abilities.
* Release are done in a short time. This means that you dont have depend on updating "by hand" to the latest and greates Software Available. Also you dont have to fiddle around with updates, and your system keeps consistent.
* Unlike most other Distributions its completely independent from commercial interests. No big firm stands behind Sabayon, and dicates how the Distribution should look like. The Developers of Sabayon Linux are all Users from other Distributions, so they started to make basically a distribution "from users for Users".

== '''Screenshots''' ==
Screenshots are available at:

[http://shots.linuxquestions.org/index.php?os=SabayonLinux LinuxQuestions.org], [http://www.thecodingstudio.com/opensource/linux/screenshots/?os=sabayonlinux TCS] and
[http://shots.osdir.com/slideshows/slideshow.php?release=758&slide=16&title=sabayonlinux+3.2+screenshots/ OSDir]

[http://www.youtube.com Youtube Search for Sabayon]
[http://kde-look.org Kde-look.org]
[http://www.lynucs.org Lynucs Screenshot Archive]

=Sabayon Linux Common Questions=
== '''Prerequisites and System Requirements for running Sabayon Linux''' ==

* '''Live Environment - No 3D Desktop''':
** ''i586'' Processor (starting from AMD K5 and Intel Pentium)
** at least ''128Mb'' of RAM (256 suggested)
** a ''2D'' graphics card
** a ''DDC capable Monitor''
** ''mouse'' and ''keyboard''

* '''Live Environment - 3D Desktop''':
** ''i686'' Processor (starting from AMD K6 and Intel Pentium II)
** at least ''256Mb'' of RAM (512 suggested)
** an '''OpenGL capable 3D graphics card''' (mostly NVIDIA, ATI, Intel, VIA)
** a ''DDC capable Monitor''
** ''mouse'' and ''keyboard''

* '''Installation''':
** ''i586'' Processor (see above)
** at least ''192Mb'' of RAM (256 suggested)
** ''8GB'' of free space
** ''Internet connection'' (not mandatory but highly suggested)
** a ''DDC capable Monitor''
** ''mouse'' and ''keyboard''

'''Passwords on Live-CD/DVD''':

* root password:
For older releases the password is "root" (without the quotes). For newer releases, no password is required: just press the Enter key.
* sabayonuser password:
For older releases the password is "sabayonuser" (without the quotes). For newer releases, no password is required: just press the Enter key.

== '''Boot Methods for special ways of using Sabayon''' ==

'''NOTE:''' ''Starting from SabayonLinux 3.2, all these options can be choosen without typing anything on the boot command line''

* ''Start the SabayonLinux Live system''.
sabayon

* ''Start the Graphical Installation''.
install

* ''Start the Text mode Installation''.
text-install

* ''Start the SabayonLinux Live system without proprietary drivers''.
genuine

* ''Start the SabayonLinux Live system without loading X.Org''.
console

* ''Start the SabayonLinux Live system with Internet Kiosk framework''.
internetkiosk

* ''Start the SabayonLinux Live system with Internet Kiosk framework + NX Client''.
internetkiosknx

* ''Start the SabayonLinux Live system in Debug mode (expert)''.
debug

* ''Perform a memory test''.
memtest

== '''Boot parameters and workarounds for problematic Hardware''' ==

'''Sabayon Linux''' supports some extra features that can be enabled by adding the ''boot parameters below''. Moreover, you can tune the system to behave in different ways.

* '''lang''': set a specific localization
lang=fr_FR
lang=en_GB
lang=it_IT
lang=es_ES
* '''res''': set a specific resolution
res=1280x1024
res=1920x1440
res=800x600
* '''refresh''': set a specific Monitor Vertical Refresh Rate for X.Org
refresh=75
refresh=50-85
* '''hsync''': set a specific Monitor Horizontal Sync Rate for X.Org
hsync=64
hsync=28-110
* '''xdriver''': force X.Org to use a specific Video driver
xdriver=i810
xdriver=sis
xdriver=mga
* '''insmod''': force the loading of a specific kernel module
insmod=ndiswrapper
insmod=agpgart,gameport
* '''rmmod''': force the unloading of a specific kernel module
rmmod=ndiswrapper
rmmod=i2c,gameport
* '''sound=mute''': do not autoconfigure the sound mixer.
* '''nofreqscaling''': disable the autoconfiguration of CPU frequency scaling.
* '''noddc''': disable DDC Monitor autoconfiguration.
* '''session=''': autostart a specific Desktop Environment. Available kde,gnome,xfce,fluxbox,e16
** To autostart Fluxbox for example:
session=fluxbox
* '''music''': enable music during boot (experimental).
* '''autoscramble''': randomization of root and sabayonuser passwords.
* '''nox''': start the System without X.Org.
* '''legacy''': start with safe parameters - for legacy compatibility.
* '''noaccelmanager''': disable Acceleration Manager (for 3D desktop selection).
* '''noapic nolapic''': disable APIC (mostly used on some faulty bioses).
* '''gentoo=nohdparm nohdparm ide=nodma''': If the system hangs on hdparm service startup or your system does not have DMA Hard drives, try this.
* '''acpi=off''': disable ACPI completely.
* '''pci=noacpi''': disable ACPI for PCI maps (HP servers and VIA chipsets).
* '''floppy.floppy=thinkpad''': useful for some ThinkPad notebooks.
* '''all-generic-ide''': useful when your IDE CD/DVD Reader is not detected at boot
* '''vga=771''': useful on some wide-screen laptops. It forces a healthy framebuffer resolution.

'''NOTE:''' ''Feel free to add extra cheat codes.''

== '''Special features''' ==

'''Sabayon Linux''' supports some enhanced features, like the ''ability to surf anonymously'', ''Internet Kiosk framework'' and ''persistent home directory''.

== What is Tor/Privoxy ==

Just start with the boot option:
* '''tor''': enable the system to use Tor/Privoxy system to surf the web anonymously.

[http://en.wikipedia.org/wiki/Tor_%28anonymity_network%29 '''Tor (The Onion Router)'''] is a free software implementation of second-generation onion routing — a system enabling its users to communicate anonymously on the Internet. Originally sponsored by the US Naval Research Laboratory, Tor became an Electronic Frontier Foundation (EFF) project in late 2004. The EFF supported Tor financially until November 2005 [1], and continues to provide web hosting for the project.

Like all current low-latency anonymity networks, Tor is vulnerable to correlation attacks from attackers who can watch both ends of a user's connection. In a number of countries, including the US, various government agencies have access to connection data of a large number of internet service providers. Because of this, Tor is not suitable for protection against big-brother-like observation by those government agencies.

== What is Internet Kiosk ==

Again, just start with the boot option:
* '''internetkiosk''': enable Internet Kiosk mode (do not use this - use the command outside).
* '''nxclient''': used along with "internetkiosk" parameter, autostarts NX Client.

'''Internet Kiosk''' is an automated ''Internet navigation system'' based on Sabayon Linux, KDE and NoMachine NX Server/Client. You can not only surf the internet, you can listen to music across the NX network, burn CD/DVD from your terminal, print your photo, play 2D games, use your Flash Pen, write and read Office documents (OpenDocument and MSOffice ones).

* How it works:
** Internet Kiosk System starts if you meet these requirements:
*** A NoMachine NX Server available (that will be the real locked-in user desktop)
*** A Thin Client with NX Client or an OLD Computer with at least 192MB of RAM, a DVD Reader and 2MB of non-volatile memory like USB flash memory or IDE HD.

* There are two Operational modes:
** '''Internet Kiosk NX''': A memory device /dev/sda1 or /dev/hda1 must be available. This can be formatted in ext3, reiserfs, xfs, reiser4, ext2 or FAT32 (very important because most of USB keys are pre-formatted with this filesystem). If you don't have this partition, you can boot SabayonLinux LiveDVD normally and then use Partition Editor on the desktop (aka GParted) to create it. Priority is given to /dev/sda1. So, if you have /dev/sda1 and /dev/hda1, /dev/sda1 will be used. At boot time, init scripts change Default Desktop Environment to Fluxbox, stop some services, like SSH, Syslog, Clamav, FreeNX Server, and autostart NX Client with the configuration files created/stored (automagically by SabayonLinux) on our non-volatile memory. In addition, a script "startinternetkiosk.sh" can be placed on it and will be called in the boot runlevel. From 2.60.2, another script "startinternetkiosk_endboot.sh", can be called before X load and must be placed in the same directory of startinternetkiosk.sh.
** '''Internet Kiosk''': The difference is that it will only call "startinternetkiosk.sh" (boot runlevel) and "startinternetkiosk_endboot.sh" (before X start) from your non-volatile memory and no other changes are made.

== What is XsistenCe ==

* '''One Removable Device''' (USB storage) + '''Sabayon Linux''' = ''your data everywhere''. In other words, you can use your Home directory in read/write mode and your data will be stored on your external non-volatile removable device.
** Just have a previously formatted USB external disk (like a flash pen).
** A blank file called "xsistence-mode" on the root of the USB storage above.
** Some free space on it, at least 15 Mb.
** Add "xsistence" boot option to enable it.
*** If the System detects a previously created image file, it will use that.
*** If the System does not detect an XsistenCe image, it will be created.
*** You can specify the size (MB) of it, by adding: "xsistence_mb=xxx"

* boot example:
sabayon xsistence xsistence_mb=100

== '''Gaming and multimedia capabilities''' ==

'''Sabayon Linux''' is the most advanced and complete Linux distribution when it comes to ''multimedia completeness and capabilities''. Use the parameters below only in ISOLINUX command line mode (no need to write those in ''Sabayon Linux 3.2'').

* '''quake4''': start [http://www.quake4game.com Quake4] playable demo.
* '''coldwar''': start [http://www.coldwar-game.com ColdWar] playable demo.
* '''geexbox''': start [http://www.geexbox.org GeeXboX] 1.0 Media Center.
* '''mediacenter''': start Sabayon Linux with [http://freevo.sourceforge.net/ Freevo Media Center].

== '''OpenGL and Accelerated Desktop''' ==

If you want to try to get your '''OpenGL Acceleration''' or your Accelerated Desktop to work ''in cases that it doesn't'', just poke with the commands below. You only need to add those parameters to the boot commandline.

* '''opengl'''
** Force the System to use a specific OpenGL subsystem, when autodetection fails.
example for NVIDIA (with NVIDIA Proprietary drivers):
'''opengl=nvidia'''
example for ATI (with ATI Proprietary drivers)
'''opengl=ati'''
example for X.Org Mesa implementation
'''opengl=xorg-x11'''

* '''agpgart'''
** Force the System to load the AGP driver, when the autodetection fails.

* '''noaccelmanager'''
** Disable the loading of the Acceleration Manager application.

* '''aiglx'''
** Enable AIGLX Desktop Acceleration and disable Acceleration Manager.

* '''xgl'''
** Enable XGL Desktop Acceleration and disable Acceleration Manager.

== '''Supported languages''' ==

- The DVD Editions support '''every language available''' for the respective application.
For example, starting from ''Sabayon Linux 3.2'', we support all GNOME, KDE, Firefox and OpenOffice language packs.

- Language support on the '''MiniEditions''' is limited to ''English'', for space reasons.

== '''MiniEditions, what are they?''' ==
A smaller version of the Sabayon Distribution.
Small enough to fit on a cd.
Includes
Kernel 2.6.*
KDE 3.5.*
Fluxbox
and Basic Applications.

=Sabayon Linux specific Documentation=
== '''Package management, Security Updates''' ==
Please look here: [[Package Management]]
== '''Release Notes and solutions of problems for specific Versions''' ==
* [[3.25c MINI]]
* [[3.26 DVD]]
* [[3.30]]

HOWTO: KMid

2010-06-05T14:11:21Z

Fitzcarraldo: Added note about KMid now supporting international characters, and modified the note about PyKaraoke.

'''Procedure to get audio output from the Midi/karaoke player KMid if you don't have an external Midi device or sound card with Midi hardware synthesizer'''

{{Note|KMid now supports international characters and diacritics (accents), so it is now a viable alternative to PyKaraoke if you have MIDI tracks with lyrics in Arabic, Chinese, Cyrillic, French, Greek, Japanese, Portuguese, Spanish and so on.}}

The following procedure works on an Acer TravelMate 8215WLMi laptop PC running Sabayon x86-64 3.3 and should work on all PCs that can play Midi files using the TiMidity++ Midi player but do not produce sound when Midi files are played using the KMid Midi/karaoke player. Both TiMidity++ and KMid are installed on the Sabayon 3.3 LiveDVD and will be installed by default onto your HDD if you perform a full installation of Sabayon 3.3.

'''What is KMid?'''

Unlike the Midi player TiMidity++, which is an ALSA sequencer and Midi to PCM (Wave) converter with its own built-in software Midi synthesizer, KMid requires either external Midi hardware or a PC sound card which has a hardware Midi synthesizer. If you only want to play Midi files you could therefore consider using TiMidity++ instead of KMid. However, unlike TiMidity++, KMid can display song lyrics if they have been embedded in Midi files (.mid and .kar) for the purpose of karaoke. So, if it is a karaoke Midi player you want, KMid rather than TiMidity++ will be the player you want to use.

Now, TiMidity++ can also be used as an ALSA sequencer and Midi to PCM (WAV) converter by external programs, so it is possible to use TiMidity++ to drive your sound card by converting the output from KMid, i.e. KMid plays the Midi file and sends the output to TiMidity++ which converts it to PCM (WAV) and sends it to the sound card. To do this, carry out the following steps in the order given:

'''STEP 1'''

Open a Terminal and type:

{{Console| <pre class="clear">$ timidity -iA -Os</pre>}}

The -iA selects TiMidity's ALSA sequencer interface, and the -Os (that's the letter O, not the number zero) sets the TiMidity output mode to 'ALSA pcm device'

'''STEP 2'''

Launch KMid

'''STEP 3'''

Settings > MIDI Setup..., select 'TiMidity TiMidity port 0 - ALSA device' and click OK.

'''STEP 4'''

File > Open, enter the file name of the .mid or .kar file that you would like to play and then click Open. If the file contains lyrics, these will appear in the grey KMid window.

'''STEP 5'''

Click on the Play button to listen to the Midi file playing. If the Midi file contains embedded lyrics then you will see the words of the lyrics turn yellow in time to the music so that you can sing along.

'''NOTES'''

{{Note| The Midi instruments are defined in so-called Midi 'sound font' files. The use of TiMidity++ to sequence and output the Midi files played by KMid means that the Midi sound fonts supplied with TiMidity++ are used.}}

{{Note| The procedure given above is probably not the only way to get KMid to produce sound, and there may be ways of getting the output from KMid to sound better. The sound quality of some Midi files played using TiMidity++ are reasonable, while others are distorted even though they sound fine when played using a Midi player under Windows XP. Thus it may be worthwhile experimenting with TiMidity++ settings (type "timidity -h" without the quotes in Terminal to see the list of available TiMidity++ parameters) or with other Midi sound fonts if you can get hold of them.}}

{{Note|PyKaraoke is a good alternative to KMid (see the Sabayon Linux Wiki article [[HOWTO: PyKaraoke]]).}}

----

Authored by Fitzcarraldo, 06.04.07

[[Category:Multimedia|KMid]]

HOWTO: separate boot partition with PartedMagic and Clonezilla (dedicated GRUB2 partition)

2010-05-09T15:37:18Z

Fitzcarraldo: Removed "emerge portage" in last step as this could break Entropy. Replaced it with "layman -S" which is what should be done in combination with "emerge --sync".

You will need GRUB2 installed (equo install grub), a separate partition (here: /dev/sda1), .zip file of PartedMagic (USB version, here: pmagic-usb-4.10.zip), .zip file of Clonezilla (stable 486 version recommended, here: clonezilla-live-1.2.4-28-486.zip).

You will get a separate boot partition, with ext3 file system compatible with Windows operation systems, from which you can boot to GRUB2 (for sure!), to PartedMagic running from RAM (if some partitioning is needed), or to Clonezilla running from RAM (to make backup/restore).

0. Prepare partition
{{Console| <pre class="clear">
$ su
# mkdir /media/sda1
# mkfs.ext3 -I 128 /dev/sda1
# mount /dev/sda1 /media/sda1
</pre>}}

1. Unzip PartedMagic and Clonezilla

Unzip PartedMagic to /media/sda1/tmp1. Find directory called "pmagic", containing files bzImage and initramfs, move it to /media/sda1.

Unzip Clonezilla to /media/sda1/tmp2. Find directory called "live", move it to /media/sda1.
{{Console| <pre class="clear">
# mv /media/sda1/live /media/sda1/live-hd
# rm -rf /media/sda1/tmp*
</pre>}}

2. Add PartedMagic and Clonezilla to bootloader

{{File| (/etc/grub.d/40_custom)| <pre class="clear">
menuentry "PartedMagic" {
set root=(hd0,1)
linux /pmagic/bzImage edd=off noapic load_ramdisk=1 prompt_ramdisk=0 rw vga=791
loglevel=0 max_loop=256 keymap=us
initrd /pmagic/initramfs
}
menuentry "Clonezilla" {
set root=(hd0,1)
linux /live-hd/vmlinuz boot=live union=aufs vga=788 ip=frommedia
live-media-path=/live-hd bootfrom=/dev/hda1 toram=filesystem.squashfs
initrd /live-hd/initrd.img
}
</pre>}}

3. Install bootloader to MBR and copy its files to boot partition, generate a new grub.cfg

{{Console| <pre class="clear">
# grub2-install --root-directory=/media/sda1 /dev/sda
# grub-mkconfig -o /media/sda1/boot/grub/grub.cfg
</pre>}}

4. Test changes using QEMU

{{Console| <pre class="clear">
# sync ; echo 3 > /proc/sys/vm/drop_caches ; qemu -hda /dev/sda
</pre>}}

If QEMU does not work as needed, remove it and then install it via Portage

{{Console| <pre class="clear">
# equo remove qemu --nodeps
# emerge --sync && layman -S && emerge qemu
</pre>}}

--donnie

HOWTO: Install a HP Printer

2009-11-22T18:18:54Z

Fitzcarraldo:

Installing a HP printer under Sabayon Linux

Installing HP printer under Sabayon Linux the easy way.

1). First you want to install hplip. You can either find the package in sulfur or just type "equo install hplip" in the console. If prompted to add a config, you can merge it and hplip will be added to startup.

2). Once it's installed, open hplip.

3). When hplip is first run, it will inform you that no printers are found and give you an option to begin setup.

4). Select How Your Printer will be Connected to Your Computer.

5). Select the Printer to be Configured.

6). Select the PPD file (or driver) to be Used for Your Printer. (Usually you will want to select the recommended PPD file.)

7). Enter any Printer Information You Wish to Update/Change.

8). Confirm the Printer Settings and Finish the Configuration Process.

You're done! For more information on hplip (including supported printers), please visit http://hplipopensource.com/hplip-web/index.html .

[[Category:Printing|Install a HP Printer]]

HOWTO: Sharing e-mail between Sabayon Linux and Windows on a dual boot PC

2009-10-26T11:42:54Z

Fitzcarraldo: Added a couple of line feeds before the new note, and added a date to the note so folk will know that it's new.

==Introduction==

If you want to share common e-mail folders and e-mail between Sabayon Linux and Windows XP on a dual boot PC, here is how I did it.

To share e-mail between Windows XP and Sabayon Linux, I use the Mozilla Thunderbird e-mail client, which has versions for Windows and Linux. (I have Windows XP on a FAT32 partition; I have not tried this with Windows on a NTFS partition.) The procedure below works for Thunderbird 2.0.0.0.

===Installation and configuration===

1. Download and install Thunderbird in Windows XP, and accept the Thunderbird wizard’s offer to import e-mails and address book from Outlook Express. (This does not delete any of the e-mails or address book contents in Outlook Express.)

In my case the Thunderbird e-mail folder was created at:

C:\Documents and Settings\Fitzcarraldo\Application Data\Profiles\o6wzbdjb.default\Mail\Local Folders

2. Boot Sabayon Linux and check if Thunderbird is already installed (K Menu > Applications > <s>Internet</s> Office). If not, install it from a Terminal window by typing:

{{Console| <pre class="clear">sudo emerge mozilla-thunderbird</pre>}}

3. Launch Thunderbird, cancel the New Account Wizard that pops up, and close Thunderbird.

4. Copy the file prefs.js from the Windows XP partition to the Sabayon Linux partition and overwrite the file prefs.ps in the Linux directory. For example, I copied the following file:

C:\Documents and Settings\Fitzcarraldo\Application Data\Profiles\o6wzbdjb.default\prefs.js

to:

~/.thunderbird/hqdk3hng.default/prefs.js

(You can select View > Show Hidden Files in Konqueror and use the GUI to copy the file, or you can do it from a Terminal window.)

5. Open the file ~/.thunderbird/hqdk3hng.default/prefs.js using a text editor and search for all lines containing “C:\\Documents and Settings\\...” (I am using “...” here to shorten the long path) and replace them with the Sabayon Linux path. For example, in my case I changed the following line:

{{File|~/.thunderbird/hqdk3hng.default/prefs.js|<pre class="clear">
user_pref("mail.server.server2.directory", "C:\\Documents and Settings\\Fitzcarraldo\\Application Data\\Thunderbird\\Profiles\\o6wzbdjb.default\\Mail\\Local Folders");
</pre>}}

to:

{{File|~/.thunderbird/hqdk3hng.default/prefs.js|<pre class="clear">
user_pref("mail.server.server2.directory", "/media/ACER/Documents and Settings/Fitzcarraldo/Application Data/Thunderbird/Profiles/o6wzbdjb.default/Mail/Local Folders");
</pre>}}

because the Windows C: drive is mounted to /media/ACER in my case. You can look in /media if you are not sure what your Windows XP C: drive is mounted to in Sabayon Linux.

6. Finally, delete any lines containing “[ProfD]”. These are relative paths which will be generated automatically.

7. Now launch Thunderbird in Sabayon Linux and verify that you can see your e-mail. Create a new message and then reboot Windows XP and verify that the draft is accessible from Windows XP. (Note that the Windows XP partition has to be mounted otherwise Thunderbird will not show any e-mails.)

====Format of dates displayed in Thunderbird's Date column====

Although I had configured Sabayon Linux 3.3 to use the GB locale (K Menu > Control Centre > Regional & Accessibility > Country/Region & Language), Thunderbird still displayed dates in the Date column in US format. When I opened a Terminal window and typed “echo $LANG”, the result was “en_US.UTF-8”. Therefore I edited the file /etc/env.d/02locale and changed all occurrences of “en_US.UTF-8” to “en_GB.UTF-8”. This did not fix the problem (it should have, because the environment variables are created by the /etc/profile script from files in /etc/env.d, so I don’t why this did not occur). Then I added the following lines at the end of the file /etc/profile:

{{File| (/etc/profile)| <pre class="clear"># The three environment variables below were added on 23.05.07 by Fitzcarraldo
# (I changed en_US to en_GB in /etc/env.d/02locale too, but it didn't work):
LANG="en_GB.UTF-8"
LANGUAGE="en_GB.UTF-8"
LC_ALL="en_GB.UTF-8" </pre>}}

This time Thunderbird did display the short date in the UK format (DD/MM/YY).

===Configuration of Thunderbird to access Webmail accounts===

You can also configure Thunderbird to access Webmail accounts such as Hotmail, Yahoo etc. Here's how to do it:

1. Go to the Web site http://webmail.mozdev.org/installation.html and download the files Web-Mail-x.x.x and Hotmail-x.x.x (where "x.x.x" is the latest version number available) to your Desktop or wherever.

2. Launch Thunderbird and select Tools > Add-ons

3. Click on Install, browse to the location on your HDD where you saved the above-mentioned files, select the file and click Open to install. Repeat for each file you downloaded.

4. Set up e-mail accounts as follows:

Edit > Account Settings...

Add Account...

Tick Web Mail and click on Next

You need to have server settings of:

<pre>POP
Server Type: POP
Incoming Server: localhost
UserName: fitxcarraldo@hotmail.com </pre>

<pre>SMTP
Server Name: localhost
UserName: fitxcarraldo@hotmail.com </pre>

Make sure that Outgoing Server (SMTP) on the Account Settings – <Web Mail – fitxcarraldo@hotmail.com> page is set to Webmail – localhost

Change the Port to 4096 on the Server Settings page. (Use secure connection: Never)

Go to Outgoing Server (SMTP) > Webmail – localhost > Edit and change the Port to 2048. (Use secure connection: No)

5. Click on Tools > Add-ons again and click on Preferences for Webmail 1.2.1. Set the POP port as 4096, the SMTP port as 2048 and the IMAP port as 5120. (I have just chosen random values greater than 1024 for these three ports, as they have to be greater than 1024 for Linux, but the ports must match the ports in the Account Settings.) Then start the servers. Click on the Logging tab and enable logging.

6. Click on Tools > Add-ons again and click on Preferences for Webmail – Hotmail 1.2.2b1. Make sure the Hotmail domain where you have your Hotmail e-mail account (hotmail.co.uk, hotmail.com or whatever) is in the list, if not add it. Select the account then click the Mode, POP and SMTP tabs and select the options you want. Then click Close.

7. Use Konqueror to browse the hidden folder .thunderbird in your home folder. Inside the .thunderbird folder I have a folder hqdk3hng.default and, inside that, a folder WebmailData. Using the mouse, select WebmailData, delete it and create a new folder with the same name (right-click on the window and select Create New > Folder... ).

8. Exit and restart Thunderbird. Make sure the servers are running (see above for how to view them). If you have any problems, http://webmail.mozdev.org/ has FAQs, a forum, screendumps, instructions and so on.

NOTE:
The e-mail address given in the examples above is fictitious, to avoid spam.

{{Note| October 2009: Hotmail/MSN access via Thunderbird is now much easier because Microsoft now has POP and SMTP servers for users of these Webmail services. So you do not need to use the WebMail and Hotmail add-ons any more. You just need to configure each Windows Live account as follows:

Edit > Account Settings

Server Settings

Server Type: POP Mail Server

Server Name: pop3.live.com

Port: 995

Use secure connection: SSL

Ougoing Server (SMTP)

Server Name: smtp.live.com

Port:587

Use secure connection: TLS
}}

[This page created by Fitzcarraldo on 26.05.07]

HOWTO: Disk imaging using Partimage

2009-10-24T11:12:02Z

Fitzcarraldo: Improved the English in Step 18.

'''How to backup disk partitions ("disk imaging") using Partimage'''

Partimage is a FOSS application for backing up disk partitions (a.k.a. disk imaging). Unlike the Unix/Linux ''dd'' command, Partimage only backs up the used blocks of a partition (there’s no point backing up empty blocks), and it also has an option to compress the backup if desired. It has other options, such as splitting the backup over multiple CDs, DVDs, Zip disks etc.

If you want to backup your core partitions they need to be unmounted, so use a LiveCD or LiveDVD with Partimage on it.

I think the best way to use Partimage is to download the ISO of the latest version of the Gentoo-based SystemRescueCd:

http://www.sysresccd.org/Main_Page

and burn it to a CD-R. I used K3b to burn it, but you can use Nero or any other method of burning ISOs (such as the method given on the SystemRescueCd Web site). I downloaded the file systemrescuecd-x86-0.4.2.iso from the above-mentioned site (this version works with both x86 and x86-64 CPUs).

Then read the online documentation for Partimage:

http://www.partimage.org/Main_Page

and specifically the Chapters 1 (Introduction), 3 (Usage: basics) and 5 (Backing up the partition table), plus Chapter 4 (Network support) if you're going to backup over a network. Note that Chapter 5 is very important otherwise the backups you make of your partitions will be useless:

http://www.partimage.org/Partimage-manual

I backup my laptop's HDD partitions (Windows XP and Sabayon Linux) to an external USB HDD as explained below. Note that, as some of your partitions will be bigger than 4 Gb, you cannot back them up to a HDD formatted as FAT32. So make sure you are backing up to a HDD that is formatted to support files bigger than 4 Gb (e.g. formatted as ext2, ext3, NTFS, etc.)

1. Set the BIOS of your PC so that the optical drive will boot first.

2. Insert the SystemRescueCd CD into the optical drive and restart the PC.

3. When the root prompt (%) appears, type the following:

{{Console| <pre class="clear">startx</pre>}}

4. Right-click on the Terminal icon (the PC monitor with Tux) and select 'Launch' to open a Terminal window.

5. At the root prompt (%) type:

{{Console| <pre class="clear">cd /mnt
mkdir SEA_DISC</pre>}}

N.B. Choose any directory name you want. I use "SEA_DISC" because that's the volume name of my external USB HDD and I don't want to get confused.

6. Right-click on the desktop and select 'Partimage' from the pop-up menu.

7. Partimage will launch. Scroll down the list of HDDs to decide partitions you want to back up, and to see which HDD (partition) you want to back them up to. In my case I see that my 320 Gb external NTFS-formatted USB HDD is called “sdc1” (this can change, depending on what external USB HDDs I have plugged in to my laptop at the time). The full list displayed by Partimage for my current situation is:

hda1 <-- the FAT 32 WinXP factory restore partition on my laptop's HDD

hda2 <-- the FAT32 WinXP C: drive on my laptop's HDD

hda3 <-- the ext3 /boot primary partition on my laptop's HDD

hda4 <-- the extended partition on my laptop's HDD

hda5 <-- the ext3 /home logical partition on my laptop's HDD

hda6 <-- the ext3 / logical partition on my latptop's HDD

hda7 <-- the linux-swap logical partition on my laptop's HDD

sda1 <-- my FAT32 iRiver music player with 40 Gb HDD

sdb1 <-- my NTFS external Iomega 40 Gb USB HDD

sdc1 <-- my NTFS external Seagate 320 Gb USB HDD

8. Based on my current situation (see Points 5 and 7 above) I type the following in the Terminal window:

{{Console| <pre class="clear">ntfs-3g /dev/sdc1 /mnt/SEA_DISC</pre>}}

N.B. If my external HDD were formatted as ext3 instead of NTFS then I would have instead typed:

{{Console| <pre class="clear">mount /dev/sdc1 /mnt/SEA_DISC</pre>}}

9. In the Partimage window I select the partition I want to back up. Let's say for example that I want to back up hda1, so I use the scroll keys to select that partition.

10. Then I use the TAB key to select the box 'Image file to create/use' and I enter the full path of the file I want to save the partition into. In my case this would be:

{{Console| <pre class="clear">/mnt/SEA_DISC/win-xp-hda1.partimg.gz</pre>}}

N.B. You can call the file whatever you want. I could have called it "/mnt/SEA_DISC/mybackup.gz" or whatever, but you must add the suffix ".gz" to it if you want to create a Gzip file (there are three choices with Partimage: read the online Documentation -- see the link I gave earlier).

11. Press F5 to go to the next page of Partimage.

12. Use the TAB key and tab down to 'Image split mode' and select 'Automatic split' (use the cursor keys, and SPACE bar to select).
WARNING added 3 February 2008: I have had "invalid compression level" error messages when trying to restore images, so I recommend that, instead of selecting 'Automatic split', you select 'Into files whose size is:' and a file size of '2037 MiB'. See the Partimage Forum thread http://www.partimage.org/forums/viewtopic.php?t=213 for further details.

13. Press F5 to go to the next page of Partimage.

14. Enter any description for your backup file you want. For my example above, I'd enter (without the quotes) "WinXP factory restore partition on Acer TM 8215 WLMi".

15. Use the TAB key to select the "OK" box, then press ENTER to start the backup. The backup process can take several hours if the partition you are backing up is large and you have selected compression. For example, one of my laptop’s partitions is 72.33 Gb, contains 32.12 Gb of data and was saved as a compressed Gzip file of 17.51 Gb in 2 hours 31 minutes. The Partimage window displays the estimated time and progress of the backup.

16. Once the partition has been backed up to my external USB HDD, I repeat the above steps for all the other partitions on my laptop's HDD that I want to back up. In my case, I backup all the partitions on my laptop's HDD.

17. When I have finished backing up the partitions, I follow the instructions in Chapter 5 of the on-line documentation for Partimage:

http://www.partimage.org/Partimage-manual_Backup-partition-table

to backup the partition tables for the primary partitions and extended partition on my laptop's HDD. In the Terminal window I type:

{{Console| <pre class="clear">cd /root
mkdir partition-backup
cd partition-backup
dd if=/dev/hda of=backup-hda.mbr count=1 bs=512
cp backup-hda.mbr /mnt/SEA_DISC/backup-hda.mbr
sfdisk -d /dev/hda > backup-hda.sf
cp backup-hda.sf /mnt/SEA_DISC/backup-hda.sf</pre>}}

N.B. I type "hda" because my laptop's HDD is hda, the first disk (see Point 7 above). Yours may be different, so use the correct name for your situation.

(BTW, sfdisk is a tool in the sys-apps/util-linux package, and is installed on SystemRescueCd.)

Then I exit from everything, remove the SystemRescueCd CD from the optical drive and reboot my PC in order to return to SL. All done!

18. To restore a partition from the backup files you created using Partimage, you also use Partimage. Follow Steps 1 to 7 again. Having used Partimage to create the backup files, it should be obvious from the text displayed on the Partimage user interface what to do to restore them. However,restoring the MBR and the partition tables you saved in Step 17 is more complicated, and instructions for doing this can be found in Chapter 5 of the on-line documentation for Partimage. In the Terminal window I type:

{{Console| <pre class="clear">dd if=/mnt/SEA_DISC/backup-hda.mbr of=/dev/hda
sfdisk /dev/hda < /mnt/SEA_DISC/backup-hda.sf</pre>}}

Then reboot.

P.S. Even if you don’t use Linux, you can use SystemRescueCd and Partimage to backup your Windows/Vista partitions.

Article created by Fitzcarraldo on 12 October 2007. Item 12 modified by Fitzcarraldo on 3 February 2008 with a warning about a potential problem restoring images. Item 18 added 24 October 2009.

[[Category:Filesystems|Disk imaging using Partimage]]
[[Category:HOWTO|Disk imaging using Partimage]]

Anaconda

2009-01-30T19:47:11Z

Fitzcarraldo: Trivial change: added a missing word.

== Wikipedia's explanation ==

Anaconda is the installer for Red Hat Linux and Fedora Core. It is written in Python and C, with a graphical frontend using PyGTK and a text frontend using python-newt. A kickstart file can be used to automatically configure the installation, allowing users to run it with minimal supervision.

Anacondas are lizard-eating pythons, and the SuSE logo is a lizard, hence the choice of naming.

== Sabayon Linux's explanation ==
(by Laura)

Sabayon's own variety of Anaconda is not the same as the one developed and used by Fedora, it is more similar to the one used by Vidalinux. In addition Sabayon's Anaconda has several essential changes that make it easy to install your Sabayon Linux System.

At present Sabayon uses Anaconda to install itself on hard disc / drive.

Interesting notes:
*Sabayon Linux's Anaconda will continue to be customized and specialized in order to make your Sabayon installation experience easier and more enjoyable.

HOWTO: Skype for Linux

2008-10-03T09:45:42Z

Fitzcarraldo: Updated to follow new editing guidelines

===HOWTO: Skype for Linux===

The following procedure works on an Acer TravelMate 8215WLMi laptop PC running Sabayon x86-64 3.3 and Skype for Linux 1.3.0.53_API. [See the addenda at the bottom of this page for later versions.]

The Acer TravelMate 8215WLMi uses an Intel soundcard. You will need to find out precisely which type of soundcard your PC uses and edit the appropriate configuration file for it as explained in this procedure. There are ALSA configuration files in directory /usr/share/alsa/cards for many different soundcards. AlsaConf (see STEP 2 below) should tell you which soundcard you have if you are not sure.

'''Problems with Skype that this procedure may resolve'''

This procedure may help you resolve the following problems when trying to use Skype for Linux with Sabayon Linux:

- The microphone appears not to work: you can hear the other party but they cannot hear you.

- The Skype window displays the message “Problem with sound device”, or displays the message “Connecting” ad infinitum.

- The Terminal window from which you launched Skype displays the following message:

{{Console|<pre class="clear">ALSA lib pcm_dsnoop.c:606:(snd_pcm_dsnoop_open) unable to open slave</pre>}}

- You can connect to the Skype Test Call service but usually the 'bong' informing you that the recording period has finished is immediately followed by a second 'bong' instead of your voice being played back.

- You can sometimes connect to the Skype Test Call service and record your voice correctly but usually you cannot and experience one or more of the above problems.

- You can sometimes connect to a third party and have a conversation but usually you cannot and experience one or more of the above problems.

'''STEP 1'''

First make sure that your PC has the latest versions of the ALSA software. I do this by launching Kuroo, typing alsa into the Filter box, ticking the Updates radio button and then opening a Terminal window and using the emerge -u command as root to update all the installed ALSA-related packages displayed by Kuroo. Updating listed third-party applications such as TiMidity++ is not necessary.

'''STEP 2'''

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

Run AlsaConf as root and click on OK, to make sure ALSA is configured. AlsaConf should also tell you which soundcard your PC has. If AlsaConf lists a second soundcard which is described as a “legacy” soundcard, do not select the “legacy” soundcard.

'''STEP 3'''

Launch Recording Tool (KRec) and use it to see if the PC microphone is recording correctly.

'''STEP 4'''

{{Console|<pre class="clear">$ alsamixer</pre>}}

Run AlsaMixer and make sure nothing is muted and that both Front Mic, Mic, and the two Capture columns are not muted/disabled, and set them to maximum. (Use the TAB key to cycle through all the parameters in AlsaMixer; to select different parameters press the left and right arrow keys; to increase/decrease volumes use the up/down arrow keys, to mute/unmute use the Space bar. To see all the parameters simultaneously you can maximise the window.) By the way, I also ran KMix and found that anything I did in KMix was mirrored in AlsaMixer, and vice versa except for the two Capture sliders in KMix. Volume Control, though, matches AlsaMixer exactly, so you can use Volume Control instead of AlsaMixer if you want.

'''STEP 5'''

Select Control Centre > Sound & Multimedia > Sound System > Hardware and change ‘Select the audio device:’ from ‘Autodetect’ to ‘Advanced Linux Sound Architecture’ and tick ‘Full duplex’.

'''STEP 6'''

Repeat STEP 3. You should find that KRec works: you should be able to record your voice and play it back.

'''STEP 7'''

{{Console|<pre class="clear"># cp /usr/share/alsa/cards/HDA-Intel.conf /usr/share/alsa/cards/HDA-Intel.conf.bak</pre>}}

As root, backup your soundcard’s ALSA configuration file. This is just a precautionary measure in case you need to revert. Bear in mind that the example above is for the Acer TravelMate 8215WLMi which uses an Intel soundcard. You will need to find out precisely which type of soundcard your PC uses and edit the appropriate configuration file in /usr/share/alsa/cards. There are ALSA configuration files in /usr/share/alsa/cards for many different soundcards.

'''STEP 8'''

As root, edit /usr/share/alsa/cards/HDA-Intel.conf (or whatever the ALSA configuration file is called for your soundcard) and change:

{{File|/usr/share/alsa/cards/HDA-Intel.conf|<pre class="clear">
capture.pcm {
type plug
slave.pcm {
@func concat
strings [ "dsnoop:" $CARD ]
}
</pre>}}

to

{{File|/usr/share/alsa/cards/HDA-Intel.conf|<pre class="clear">
capture.pcm {
type plug
slave.pcm {
@func concat
strings [ "hw:" $CARD ]
}
</pre>}}

i.e. replace "dsnoop:" with "hw:"

'''STEP 9'''

{{Console|<pre class="clear">$ sudo skype</pre>}}

Launch Skype as root and you may find that Skype now works consistently. The Skype Test Call service should work correctly and consistently. You should also be able to make a long call without problem.

This HowTo is based on the [http://www.sabayonlinux.org/forum/viewtopic.php?t=6080 Sabayon Forum post here.]

Authored by Fitzcarraldo, 18.04.07

==ADDENDUM No. 1==

16 July 2007: See the following warning by Skype for Linux forum member 'berkus', one of the Skype developers on the Skype for Linux forum, about ALSA 1.0.14 stopping the microphone from working:

http://forum.skype.com/index.php?showtopic=66544&st=40&p=413813&#entry413813

The command to restart the ALSA modules ('berkus' refers) is:

{{Console|<pre class="clear">/etc/init.d/alsasound restart</pre>}}

Note that the above warning has nothing to do with the problem stopping the microphone working that is documented above. Even if you have not installed ALSA 1.0.14 the procedure above may help you get your microphone working with Skype.

==ADDENDUM No. 2==

16 August 2007: I have found that I do not need to edit the new version of /usr/share/alsa/cards/HDA-Intel.conf now that I have updated to the latest version of ALSA (1.0.14) and the latest version of Skype (1.4.0.94) from Portage. This version of Skype for Linux is much better than the version (1.3.0.53_API) originally discussed on the Wiki page.

==ADDENDUM No. 3==

7 October 2007: Here is how I got Skype (Beta) 1.4.0.99 to work (Skype was giving the error message “Call Failed: Problem with Audio Capture”). I needed to do this for both SL 3.4 Loop 2b and SL 3.4f.

'''STEP 1'''

emerge -u to get the latest version of the ALSA packages alsa-firmware (1.0.14), alsa-headers (1.0.14), alsa-lib (1.0.14a-r1), alsa-plugins (1.0.14), alsa-tools (1.0.14).

'''STEP 2'''

Run alsaconf as root in a Terminal window and click on the OK buttons and click on your audio card. It should be obvious.

'''STEP 3'''

Run alsamixer as root in a Terminal window and make sure nothing is muted (pressing M toggles on/off) and volume levels are turned up (not into the red region, though). Ditto for the two Capture channels.

'''STEP 4'''

Run GNOME Volume Control or KDE KMix (KMix does not work properly on my laptop: the Capture channels reset to zero every time) and double-check nothing is muted and levels are all non-zero.

'''STEP 5'''

emerge -u skype to get the latest version of Skype (1.4.0.99).

'''STEP 6'''

K Menu > Control Centre > Sound & Multimedia > Sound System, click on the Hardware tab and tick the box Override device location and enter "default" (without the quotes) in the box beside it. Don't change anything else in the as-installed settings. Click Apply.

'''STEP 7'''

Reboot.

'''STEP 8'''

Launch Skype and select Options > Sound Devices. Select the following settings:

<pre>Sound In HDA Intel (hw:Intel,2)
Sound Out HDA Intel (hw:Intel,0)
Ringing HDA Intel (hw:Intel,0)</pre>

N.B. My sound card is HDA Intel. Yours could be different, but try to select the (hw:*,2) and (hw:*,0) as I've shown above.

'''STEP 9'''

If the above still does not get Skype working, try also: K Menu > Control Centre > Sound & Multimedia > Sound System and untick 'Enable the sound system' under the General tab. I had to do this.

==ADDENDUM No. 4==

8 October 2007: Here is how I got Skype 1.4.0.118 to work with the 64-bit version of SL.

I emerged version 1.4.0.118 it but it did not run with the 64-bit version of SL I'm using and the following error message was displayed:

{{Console|<pre class="clear">/opt/skype/skype: error while loading shared libraries: libsigc-2.0.so.0: cannot open shared object file: No such file or directory</pre>}}

I looked in the directory /opt/skype/ and there is the following symlink:

{{Console|<pre class="clear">lrwxrwxrwx 1 root root 20 2007-10-07 01:07 /opt/skype/libsigc-2.0.so.0 -> libsigc-2.0.so.0.0.0</pre>}}

The above was flashing red in the Terminal window, indicating that the file libsigc-2.0.so.0.0.0 did not exist.

This is what I had to do to get Skype 1.4.0.118 to work with 64-bit SL:

'''STEP 1'''

Uninstalled Skype 1.4.0.118

'''STEP 2'''

Re-installed Skype 1.4.0.99

'''STEP 3'''

Copied the library file to a safe place:

{{Console|<pre class="clear">cp /opt/skype/libsigc-2.0.so.0.0.0 /home/fitzcarraldo/Desktop/libsigc-2.0.so.0.0.0</pre>}}

'''STEP 4'''

Uninstalled Skype 1.4.0.99

'''STEP 5'''

Re-installed Skype 1.4.0.118

'''STEP 6'''

Copied the library file I had saved in Step 3 back to the /opt/skype/ directory:

{{Console|<pre class="clear">cp /home/fitzcarraldo/Desktop/libsigc-2.0.so.0.0.0 /opt/skype/libsigc-2.0.so.0.0.0</pre>}}

Now Skype 1.4.0.118 launches and works correctly.

HOWTO:Recording videos of your screen (screen video capture)

2008-09-22T15:46:07Z

Fitzcarraldo: HOWTO:Recording videos of your screen (screen video capture) moved to HOWTO: Recording videos of your screen (screen video capture): Missing space after colon

#REDIRECT [[HOWTO: Recording videos of your screen (screen video capture)]]

Kuroo

2007-12-20T02:36:41Z

Fitzcarraldo: Improved the explanation of what Kuroo is, and removed the condescending language.

==Description==
A GUI application that enables the user to synchronise with Portage, view all the packages in the Portage tree, install packages, view a list of the packages installed on the user's PC, update or un-install those packages, view and edit USE flags and perform other tasks pertaining to package management. Kuroo is a GUI alternative to the terminal commands for Portage such as emerge, eix and so on. An alternative GUI application for package management is called Portato.

HOWTO: Google Earth freezes at splash screen

2007-08-06T14:20:57Z

Fitzcarraldo: Improved introduction, and added footnote about creation date

==How to get Google Earth to run under XGL if your PC uses an ATI GPU==

===Introduction===

If Google Earth just hangs at the splash screen and your PC has an ATI graphics card then try the following fix, which makes Google Earth use an older version of an ATI library (the older library is put in the Google Earth directory and does not affect the latest version of the library, which is in a different directory).

This works on an Acer 8215WLMi laptop running SL x86-64 3.4 Loop 2b with XGL active and Google Earth 4.0.2723 as installed to the HDD from the LiveDVD.

===Installing the old library===

Download the file '''ati-driver-installer-8.27.10-x86.run''' from the ATI Web site. I downloaded it to my Desktop (/home/fitzcarraldo/Desktop). Then type the following commands into a Terminal window (replacing "/home/fitzcarraldo/Desktop" with the directory where you stored the downloaded file):

{{Console|<pre class="clear">
$ sudo mkdir /tmp/ati_extract

$ sudo sh /home/fitzcarraldo/Desktop/ati-driver-installer-8.27.10-x86.run --extract /tmp/ati_extract

$ sudo cp /tmp/ati_extract/arch/x86/usr/X11R6/lib/libGL.so.1.2 /opt/googleearth/libGL.so.1</pre>}}

===How to launch Google Earth===

There are two alternative ways of launching Google Earth: from the command line or via the GUI. To launch Google Earth from the command line, type the following into a Terminal window:

{{Console|<pre class="clear">$ DISPLAY=:0 googleearth</pre>}}

To launch Google Earth via the GUI, you need to modify slightly the Desktop Configuration File (the shortcut icon on the Desktop) that was installed automatically when you installed SL to the HDD. Edit the command in the Application tab of the Desktop Config File to say '''DISPLAY=:0 googleearth %f''' instead of just “googleearth %f”.

Note: Apparently some people have to use e.g. “DISPLAY=:93” instead “DISPLAY=:0”.

[This page created by Fitzcarraldo on 05.08.07]

HOWTO: USB pen drive will not automount

2007-06-30T14:23:15Z

Fitzcarraldo: Initial entry

'''HOWTO: USB pen drive will not automount'''

'''Introduction'''

I found that my 512 Mb USB pen drive (a.k.a. memory stick, a.k.a. flash drive, etc.) would not mount under Sabayon Linux 3.3 (although it did automount under Windows XP, Windows 2000 and Ubuntu Linux 6.06). This seems to be a common problem with various manufacturers' pen drives under various Linux distros.

Running '''dmesg''' from the command line showed "attempt to access beyond end of device" and "p1 exceeds device capacity" error messages. If I inserted the USB pen drive it showed up in GParted as a faulty partition (the little warning triangle). If I formatted it with GParted I could then mount it manually and copy files to and from the drive via the command line. However, as soon as I pulled out the pen drive, it reverted to its previous state and, if re-inserted into the PC, again could not be mounted.

I believe that the firmware in the pen drive has a bug that treats the pen drive as if it has one more sector than it really does. To get around this, try the procedure below, which worked with my model of pen drive and has worked with several other manufacturers' pen drives too.

'''STEP 1'''

Back up any important data on the pen drive.

'''STEP 2'''

Use a low-level formatting tool to low-level format the pen drive (GParted cannot do it, GParted can only perform a normal format). I used a freeware utility for Windows called HDDGURU Low Level Format Tool (http://hddguru.com/) as I do not know of one for Linux.

'''STEP 3'''

Use GParted to format the pen drive to FAT32 and then set the boot bit.

The pen drive should then be able to automount. Some pen drives work fine without having to perform this procedure, others need to be low level formatted.

This HowTo is based on the [http://www.sabayonlinux.org/forum/viewtopic.php?t=2941 Sabayon Forum post here.]

Authored by Fitzcarraldo, 30.06.07