**New Users** Resources and Forum Usage

If you are new to Linux or new to Sabayon Linux and just not sure where to post, here ya go. Post without fear of being told to RTFM :-)

Moderator: Moderators

Posts: 9051
Joined: Sat Jan 14, 2006 0:55
Location: Midwest USA

**New Users** Resources and Forum Usage

Post by wolfden » Mon Oct 16, 2006 8:42

Last updated 01/11/08

Alright people we are getting way too many redundant posts. The forum has a wonderful feature called search and can be found at the top of the page or simply click:

That will allow you to enter in keywords to search the entire forum. PLEASE USE this before Posting, chances are someone else has had the same problem. We don't need a dozen threads on the same matter. The more threads the helpers have to go thru the slower the response time is. If a thread is redundant you're gonna be told to use the search feature anyway.

SabayonLinux = Gentoo so therefore you will want to bookmark these sites:
http://wiki.sabayonlinux.org/index.php?title=FAQ <-- FAQ
http://www.gentoo.org/doc/en/list.xml <------- Gentoo Documentation Resources List
http://gentoo-wiki.com/Main_Page <--- full of howto and everything else
http://www.gentoo-wiki.info/ <--- temp gentoo wiki till gentoo wiki is rebuilt
http://www.gentoo.org/doc/en/ <------- Gentoo Documentation Resources
http://google.com <--- simply enter the word Gentoo plus your keywords
http://gentoo-wiki.com/Official_Gentoo_Documentation <---- Official Gentoo Documentation
http://www.gentoo.org/doc/en/handbook/index.xml <--- Gentoo Handbook
http://linuxreviews.org/gentoo/emerge/ <--- Emerge Quick User Guide
http://wiki.sabayonlinux.org/index.php? ... tage_Guide <-- Emerge/Portage Guide - Update/Install Packages - Source Package Manager
http://gentoo-wiki.com/HOWTO_Use_Portage_Correctly <--Use Portage Correctly
http://wiki.sabayonlinux.org/index.php?title=En:Entropy <--- Binary Package Manager
http://www.sabayonlinux.org/wiki/index. ... =Main_Page <--- Sabayon Wiki
http://gentoo-wiki.com/TIP_Converting_from_or_to_Debian <--- Converting from Debian to Gentoo
http://gentoo-portage.com/Browse <---Browse Portage via Web
http://www.sabayonlinux.org/forum/viewt ... 54&t=10578 <-- Understanding /etc/make.conf
http://www.sabayonlinux.org/forum/viewt ... 54&t=10863 <-- Understanding config files/update config files
http://www.sabayonlinux.org/forum/viewt ... =54&t=5531 <-- unofficial world update/update entire system
http://www.sabayonlinux.org/forum/viewt ... =53&t=9882 <-- howto update compiz-fusion to latest dev. version
http://www.sabayonlinux.org/forum/viewt ... 518#p72605 <-- how not to look stupid asking for help

Those links will tell anyone what Gentoo is and how to use it. The amount of Gentoo documentation is just unreal, spend sometime searching.

Learn the Package Managers
<<<<< This is vitally important >>>>>
http://wiki.sabayonlinux.org/index.php? ... tage_Guide <-- Emerge/Portage Guide - Update/Install Packages - Source Package Manager
http://wiki.sabayonlinux.org/index.php?title=En:Entropy <--- Binary Package Manager

If anyone else has a great source of info, please post it. Let's try to be resourceful here.

When posting please post in the correct forum for the version of SabayonLinux you are running. Please note the more information you give us the more easier it will be to help you. Information can include computer hardware, software version(s), desktop manager your using, things like that. Simply posting My X Don't Work!! is not enough. If you post is resolved please edit your original post title and append [Solved] to it (see Why, and how to add "[Solved]" to your post. Please read.).
kolsyra wrote:Here is a very good site for understanding Linux in general. Very good reading if you lack the fundamental "how Linux works" knowledge but also very entertaining for someone that just wants to know more about Linux:

Lots of other good guides can be found on that site. Feel free to add it in the top post.

For those with the !!! Unable to calculate Linux Kernel version

Code: Select all

emerge =gentoo-sources-2.6.18-r4  (note - replace gentoo-sources-2.6.18-r4, with your present kernel use uname -r)
cd /usr/src/linux
zcat /proc/config.gz > .config
make prepare modules_prepare

If make prepare modules_prepare fails just emerge nvidia-drivers or ati-drivers, which ever one u have.
FOR THOSE WITH ERROR: "ERROR: Certificate verification error for xxxxxx" by AjeZ

run : emerge ca-certificates

and after that, run again the previous emerge command
For people having trouble getting vmWare to play nicely, follow these instructions courtesy of civll64:

Code: Select all

emerge =gentoo-sources-2.6.18-r4  (note - replace gentoo-sources-2.6.18-r4, with your present kernel use uname -r)
emerge vmware-modules
depmod vmmon -a
depmod vmnet -a
layman -f -a vmware
emerge vmware-server
do the config
/etc/init.d/vmware start && rc-update add vmware default
add yourself to the vwmare group

For Those that are having the frozen KDE daemon, menu froze or konqueror not opening, simply run in konsole - that will work till you reboot:
killall -SIGKILL kded

How to update the mini menu to the DVD Suse style Kicker
you need to remove "kicker" lines from /etc/portage/package.mask than

# emerge --sync && layman -s sabayon && USE="-kdeinvisibility" emerge kicker && exit && dcop kicker kicker restart

For Nvidia Kernel Mismatch
emerge -C nvidia-drivers; rmmod nvidia; rm /lib/modules/$(uname -r)/video/nvidia.ko; rm /usr/lib/opengl/nvidia -rf; emerge nvidia-drivers; eselect opengl set nvidia; reboot

Cheat Codes:

Code: Select all

noddc res=1024x768 refresh=60 opengl=ati


Code: Select all

noddc res=1024x768 refresh=60 opengl=nvidia

How to use? hit F5 on the boot up screen of the livecd/dvd and add one of the lines above pending on your hardware
More Cheat/Boot Parameters here:
http://www.sabayonlinux.org/wiki/index. ... ayon_Linux
Cool FireFox Search Engine Plugins
http://mycroft.mozdev.org/download.html ... orm=Search
Sabayon Linux Forum Plugin:
Firefox search plugins for http://packages.sabayonlinux.org :
Standard Edition

Professional Edition
http://wolf911.us/sabayon/search/profes ... 86-64.html

For Konqueror --> http://www.sabayonlinux.org/forum/viewt ... 57&t=11030
For those that can login as root but not user, as root:

Code: Select all

mkdir /var/run/console/

Remove KDE and run Gnome Desktop by senofed
if you're like me and find yourself using gnome software more than KDE and like the speeds of gnome.. here's a quick step guide to removing kde from your system

1. emerge gdm
2. edit your /etc/conf.d/xdm to boot with gdm
3. run this script as root:

Code: Select all

for p in /var/db/pkg/kde-base/*; do echo $p|sed -e 's#.*/#=#'|xargs emerge -C; done

4a. remove the rest of the KDE packages in your applications lists that are used by KDE or
4b. revdep-rebuild X to fix broken packages that have KDE dependencies
64 bit vs. 32 bit debate - unsure which one?
For everyday use, there is nearly no difference between 64bit and 32bit. 64bit is generally faster when it comes to floating point computing which is normally the case in multimedia applications and 3D rendering.

Great Article with Benchmarks:
http://enterprise.linux.com/enterprise/ ... ml?tid=121
How to check the md5sum of an iso:
First you download the iso and for simplicity lets say u download an iso called sabayon.iso to your home folder. Jump into Konsole/Terminal and you should already be defaulted to you home directory so all you have to do is.

Code: Select all

md5sum sabayonlinux.iso

wait a bit and it will return the md5. K3b will also give you the md5 when it loads the iso. Just start K3b -- select burn iso -- browse to iso -- it automatically will start checking the iso, wait for it to finish.
Also see this great howto - http://www.sabayonlinux.org/forum/viewt ... 50&t=11094

Will continue to update this as needed
Last edited by wolfden on Sun May 27, 2007 2:34, edited 48 times in total.

Young Hen
Posts: 36
Joined: Sun Oct 08, 2006 14:31
Location: Sweden

Post by kolsyra » Sat Oct 21, 2006 10:16

Here is a very good site for understanding Linux in general. Very good reading if you lack the fundamental "how Linux works" knowledge but also very entertaining for someone that just wants to know more about Linux:

Lots of other good guides can be found on that site. Feel free to add it in the top post.

Square Bottle
Growing Hen
Posts: 106
Joined: Wed Oct 11, 2006 6:57
Location: San Diego, CA

Post by Square Bottle » Wed Nov 08, 2006 8:53

For people who get an error that ends with something along the lines of "Unable to detect linux architecture" when trying to emerge certain programs, you're looking for this: http://www.sabayonlinux.org/forum/viewt ... nux+kernel

P.S. Maybe the name of this section could be changed to "Read Me First For Help: Resources and Forum Usage" or something like that to make it really nice and obvious for people like me who didn't make the association.

Square Bottle
Growing Hen
Posts: 106
Joined: Wed Oct 11, 2006 6:57
Location: San Diego, CA

Post by Square Bottle » Tue Nov 21, 2006 5:54

For people having trouble getting vmWare to play nicely, follow these instructions courtesy of civll64:

Code: Select all

emerge =gentoo-sources-2.6.18
emerge vmware-modules
depmod vmmon -a
depmod vmnet -a
layman -f -a vmware
emerge vmware-server
do the config
/etc/init.d/vmware start && rc-update add vmware default
add yourself to the vwmare group

Old Dear Hen
Posts: 964
Joined: Mon Nov 27, 2006 9:48
Location: Land Down Under / Australia

Post by Appleman1234 » Mon Dec 18, 2006 10:02

Here is my contribution to it. (If someone wants they can make my contribution a separate sticky.)
Note: wolfden and ajez give me feedback on IRC and cvill64, split and sticky my post if you think it is worth it .

Problems that users experience with Sabayon can be split into a few groups

1. Sabayon Software (from our overlay) Error / BUG

2. Software that is installed with Sabayon Error / BUG

3. Hardware or Software Configuration Error / BUG

4. User lack of knowledge / confusion.

The procedure for getting support on or resolving all the these problems is quite similar.
1. Experience the problem
2. Document / Identify the problem

3. Attempt to solve the problem by one's self
4. Attempt to solve the problem, by requesting support of others.
5. Probem resolved.

So many Sabayon users, forget to try steps 2 and 3, which make steps 4 and 5 harder to achieve.

In Step 2

After experiencing a problem you should document it, using a text editor, State what the problem is, what software is invovled or if it is hardware related what hardware is involved, provide software and hardware information, Sabayon version information and relevant outputs and errors. If providing this on IRC, then use a pastebin service.

Recording details for errors is as important as recording which snake bite you if you have been bitten by a snake, it makes the resolution (or antidote identification and application) a lot lot easier.

In Step 3.

So many people fail at step 3, and rush onto step 4. It is shameful, Google was invented for a reason and is your friend.
Other valid resources include: (wolfden has already mentioned most of these I know)
Unofficial Gentoo Wiki http://gentoo-wiki.com/
Offical Gentoo Documentation http://gentoo-wiki.com/Official_Gentoo_Documentation
Gentoo Documentation http://www.gentoo.org/doc/en/
Gentoo Handbook http://www.gentoo.org/doc/en/handbook/index.xml
Portage / Emerge Guide http://linuxreviews.org/gentoo/emerge/
Sabayon Forums http://www.sabayonlinux.org/forum/
Sabayon Wiki http://www.sabayonlinux.org/wiki/index. ... =Main_Page
Gentoo Forums http://forums.gentoo.org
Linux forums in general http://www.linuxquestions.org, http://www.linuxforums.org , http://linuxforum.com or just google the words linux and forum
Google Linux search http://www.google.com/linux
Google your problem linux , or your problem gentoo , or your problem sabayon
Too many other resources to list.

Other solutions in Step 3 are found by configuring, experimently and using internal help like man command, and the kioslaves man:/ and help:/.

Windows & Ubuntu may allow their users to be stupid or ignorant, Gentoo is user friendly, but it is very selective about its friends, Sabayon is less selective, but if you don't bother at least trying to understand the basics of Sabayon and its family / heritage (Gentoo and Linux), just like a friend you don't spend time with, your relationship become strained and difficult. (This is just an analogy, we all know Macs are the only computers with feelings :P)

In Step 4

Using forums and IRC,
Be specific and be patient, follow rules and guidelines
If on IRC and nick is sabayonlive-* then use /nick to change
Socialising on IRC is in -social and more than 3 lines is pastebin material
You will have to tolerate antics of some IRC members, Sabayon is a close knit , friends like family, developers, contribuers, helpers and users group.
Our LIVE Help invovles real people with real lives :)
Don't troll
Read http://catb.org/~esr/faqs/smart-questions.html before asking your question or raising your problem
If needs be file a Sabayon bug in our bugzilla or a Gentoo bug in their bugzilla.

In Step 5
Now that you problem is resolved, enjoy and be grateful
or file a resolved bug report or forum howto or wiki artcle on how to fix your problem especially if it is a common one.

Growing Hen
Posts: 144
Joined: Mon Dec 11, 2006 0:55

Re: Resources and Forum Useage

Post by Element » Thu Dec 21, 2006 1:51

wolfden wrote:For those with the ipw3945 - this is now in the mini 3.2
the mini has this fix in it, altough after you install you need to when you boot up for the first time

# /etc/init.d/ipw3945d start && rc-update add ipw3945d default

Hey the actual command for the Intel IPW3945d is ipw3945d then do rc-update add ipw3945 boot default. Don't mean to annoy you, just trying to clean up some mistakes. I don't know if what you posted will actually work, it didn't for me, but what I posted did.

Thanks for listening [Element]
On Sabayon @ Freenode: <ColdFlo> im not asking for support <ColdFlo> im asking for help

Posts: 680
Joined: Tue Jan 02, 2007 17:08
Location: Virginia, usa

Post by davemc » Wed Mar 28, 2007 4:40

Although there exists quite a bit of documentation and makeshift “how to's” via Google, i'm going to write a short guide on how to use the onboard Virtual Machine that comes with SL 3.3, along with a few comments on Paravirtualization methods that can be used to make things fun.


Emulation: “Emulation refers to the ability of a program or device to imitate another program or device. Many printers, for example, are designed to emulate Hewlett-Packard LaserJet printers because so much software is written for HP printers. By emulating an HP printer, a printer can work with any software written for a real HP printer. Emulation "tricks" the software into believing that a device is really some other device.”


Virtualization: “In computing, virtualization is a broad term that refers to the abstraction of computer resources. One useful definition, from independent IT analyst firm Enterprise Management Associates, is "a technique for hiding the physical characteristics of computing resources from the way in which other systems, applications, or end users interact with those resources. This includes making a single physical resource (such as a server, an operating system, an application, or storage device) appear to function as multiple logical resources; or it can include making multiple physical resources (such as storage devices or servers) appear as a single logical resource." “


Paravirtualization: “In computing, paravirtualization is a virtualization technique that presents a software interface to virtual machines that is similar but not identical to that of the underlying hardware. This requires operating systems to be explicitly ported to run on top of the virtual machine monitor (VMM), which the owner of exclusive rights in a proprietary operating system may decline to allow for strategic purposes, but may enable the VMM itself to be simpler and for the virtual machines that run on it to achieve higher performance.”


Short and sweet, Virtualization involves full hardware and software emulation (pretending), while Paravirtualization involves partial. Although many mistakenly believe that full virtualization is possible on average x86 systems, it is in fact, not. Full Virtualization involves a total and complete emulation of an entire operating system including all of its abilities – networking, printing, sound, fully functional apps, etc. What is possible is various forms of Paravirtualization to varying degree's of usability. Examples of this are VMWare, Virtual Machine, Win4Lin, Parrallels, Mac-on-Linux, Crossover, Cedega, wine, Xen, Qemu/Kqemu, KVM, and others.



Advantages and uses

As commented above, its advantages are many. Software debugging, resource sharing, networking, optimized use of available resources, or just playing around and testing other operating systems without actually rebooting or installing. Plus, its a lot of fun!

Techniques “How to”

For this to work, you need to have an .iso file handy. Download any distro .iso file and place it on your Desktop. The SL .iso will not work with this, sorry.

1.Lets start with the onboard Virtual Machine Hypervisor that comes packaged with your new SL 3.3 install (full version). Double click it and the first window pops up which includes the “Open Connection” dialoque wizard. Click the down arrow and select “KVM/QEMU”, as SL 3.3 does not have a XEN kernel so it wont work. You also have two other options, “Local host” and “Other hypervisor”. Were going to use “Local host”. “Other hypervisor” is used to link off another, already existing connection to which you insert the URL link. Ive never tried this option, but it sounds like fun! Anyway, click on “local host” and then click “Connect”.

2.Your now at the KVM/QEMU virtual machine manager. It will be blank if this is your first time here. There are four buttons at the bottom - “delete”, “new”, “details”, and “open”. Click on “new”.

3.Enter the “create new virtual system” wizard! Read it and click on “forward”.

4.Now you need to enter a name and click “Forward”. It can be any name you choose.

5.Leave the settings on this window as is and click “forward”. Only “Fully Virtualized”, and “i686” can really be used, as x86_64 has not been enabled for guest machines yet. I do not know if the other options work or not, but you can try them! :)

6.Next comes time to select the .iso you just downloaded onto your Desktop. Choose “ISO Image Location”, and enter, or browse to its location. Choose the “OS Type” and the “OS Variant” and hit “Forward”. Im not sure what “Other” would be under the OS Type, but when it comes to Virtual Machine, play play play! Thats what its all about!

7.Next comes assigning a “file” for the guest OS to operate in. All this really does is create a free space for the ISO to stretch its virtual legs in should you wish to install it or download files within the guest environment. You can choose to use an existing partition, or “Simple File”. Select “Simple File” and type /home/username/Desktop/ISO, where “username” is your account name, and enter in a file size big enough to handle the ISO your going to virtualize. You'll have to make that call as distro's like DSL or Puppylinux tend to run just great on 200megs of space, while SuSe requires at least 5 Gigs. Keep in mind too that the more complex the distro your virtualizing, the more resource intensive its going to be, and thus load down your system overall and make it slow and graphics choppy. Anyway, unselect “Allocate entire virtual disk now”, as there really is no reason to do this and it takes a lot of time for the virtual machine to create it. Click “Forward”.

8.Now select the RAM you think you'll need. I typically go with VM Max Memory of 999, and VM Startup Memory of 500. I have 2 Gigs of onboard RAM, so assigning 1 Gig still leaves me with plenty to spare. Also note here that just because you assign a Max of 1 Gig, does not mean that the virtual machine will be using the full amount of it all the time. It will allocate it as needed. Now, choose the VCPU's the emulator will run. Rule of thumb - If your machine isnt dual core, then DONT choose two! :=}

9.Click “Forward”, and your in the final selection screen. If your happy with what you see, click Finish. If not, back buttun and fix what you need to.

10.Now your back on the virtual machine manager window and you should be looking at your new virtual machine displayed in the window. Select it, and click “Open”, and bada bing, bada BOOM, it starts up! You should see the Virtual Machine Console with “run”, “Pause”, and “Shutdown” buttons at the top. In the main window you should see your ISO boot screen where you can select boot options just like on the livecd. Select one and watch it boot right up to the login screen where you then login and commence tearing it up just like you would on a livecd. You will notice some chopiness from time to time if you run graphics intensive stuff. You should have working internet, but thats about it as the VM does not normally enable networking or sound... Not that big of a deal, at least for me.

OK, now how about the other stuff

The Sabayon Forums have a great deal of information on manual paravirtualization. Read through these links for the detailed “how to”. As there is already so much information here, I wont go into more detail than this.

http://www.sabayonlinux.org/forum/viewt ... hlight=kvm

So, there you have it. Enjoy virtualization in Sabayon!!

Here is my Demo vid


Posts: 680
Joined: Tue Jan 02, 2007 17:08
Location: Virginia, usa

How to setup Ventrilo in Sabayon

Post by davemc » Sun Apr 15, 2007 1:19

Ventrilo is voice chat. Very handy if you play intensive online team games or if you just want to save the cost of a long distance call. Info here: http://www.ventrilo.com/

Sabayon 3.3+ comes with all the necessary wine components so that eliminates alot of steps. All you have to do now is:

All steps done as user or $ on command line konsole or xterm

1) $winecfg
1a) Audio tab
1b) make sure ALSA is checked. Set Hardware Acceleration to Emulation. Default Sample Rate to 44100, and Default Bits Per Second to 16. Hit OK

Now comes the fun part 8)

Dowload ventrilo client from here: http://www.ventrilo.com/download.php
Download the Windows i386 - 32bit, version 2.3.0 or filename ventrilo-2.3.0-Windows-i386

2) cd to the directory that contains that file you downloaded. For me it was /home/username/Desktop.
2a) $wine ventrilo-2.3.0-Windows-i386

It will now install ventrilo in the .wine folder of your /home/username file. Note that the .wine means that it is a hidden folder, so you will have to, within konqueror > View > Show hidden files, to see it, and you will have to see it later on.

2b) After its finished installing, fire it up for the first time with $wine "C:\Program Files\Ventrilo\Ventrilo.exe"
2c) The client will come up, but will most likely not work yet as its not setup to work within Linux. Setup your username and ventrilo server info. Note that for server you have to have that info already or know what server your friends are on. This will be URL, port, and password if one is needed.
2d) Finish setting that up and then click on the "setup" button. You WILL get an error message when you do that but just click OK and it will take you to the setup window. Now you must check "Use Push-To-Talk" and uncheck "Use DirectInput to detect Hotkey". Ensure "Enable outgoing voice communications" and "Play Key Clicks" are both checked. Also, make double sure that "Use DirectSound" for BOTH Output and Input Device are UNCHECKED! Go through all the tabs at the top and ensure this is so on all screens. Go back to the Voice tab screen and setup your "Hotkey" and Output and Input volumes. NOTE: Using the mouse keys for Hotkey does work, but creates problems because you will not be able to use the mouse to talk when outside the Vent window or if it is not the active one. I use the tilde key but I must click on the vent window to make it the active one to talk. I can hear others at all times though so if you mainly just need to listen, this is no big deal.

Almost there!

3) Now you must setup the correct windows drivers to get GSM and all that good stuff. You will need to copy them from an existing windows install somewhere or download them from the M$ website. They are:


You will find them in windows at C:\\windows\system32. Copy those files to your /.wine/drive_c/windows/system folder. Yes, thats right, you are going to copy them to your wine drive system folder... Not system32 folder.
3a) Now for the system.ini change. Go to your /.wine/drive_c/windows/system.ini and open that up. You are going to write in the following:


When your done with that, save it and close. Your pretty much home free now! Setup a shortcut for ventrilo on your desktop if you like or if wine didnt create one for you already like it did for me. Otherwise a shortcut should have been created in your KDE menu somewhere. Happy voice chatting!
Last edited by davemc on Thu Jun 07, 2007 14:10, edited 1 time in total.

Simple Hen
Posts: 89
Joined: Fri Dec 08, 2006 20:11

Post by Ron.W » Wed Jun 06, 2007 1:01

Let me add some lines here, even if I am not an experienced Sabayon or Gentoo user. To be honest, I am not too familiar with Linux in general, but I really like it, and I know how to handle a PC beyond clicking colorful desktop icons.

The most difficult thing I experienced when using Sabayon (but I am pretty sure this is true for all kind of Linux-Distributions) is: There are unmanageable many hints, manpages and instructions to be found all over the internet, some of them contradictory, or not tailored for what you actually find on your system.

For instance, one should expect to get the appropriate information (if not found right here on Sabayonlinux) from the gentoo-docs or the other sources listed above when trying to configure suspend2 on Sabayon. But the instructions found on Gentoo mislead you http://www.sabayonlinux.org/forum/viewtopic.php?t=7671, since the files and folders described there are not present. And no hint anywhere around why or at least in which way this once has been changed. I understand, that this comes while assimilating and integrating code from other distributions (in this case: Suse 10.1) into the project, and is to be aquisced as a matter of fact. But I think it would be a great help for PC-experienced Sabayon-beginners, if the most importend config files and folders could be listed here thematically for every Sabayon release. This should not be too much and too difficult work, since experienced Sabayon-users find all this at first go in their system and would be easily able to amend the listing for their Sabayon release. The Sabayon-abecederian is literally lost in translation and will spend hours without the overview.

If I am not completely off the mark with this, feel free to complete the following, maybe even in sabayon-wiki, so everybody could add a location he has woked out already:

Suspend2 files
Sabayon 3.2
configuration: /etc/powersave/sleep
logfiles: /usr/var/suspend2ram.log; /usr/var/suspend2disk.log
Sabayon 3.3 /3.4
configuration: (I'll bet location has changed...)
logfiles: ...

Encrypted WLAN
Sabayon 3.2
configuration: /etc/wpa_supplicant/wpa_supplicant.conf
Sabayon 3.3 /3.4
configuration: ...

(to be continued...)

This is a proposal only.


Posts: 9051
Joined: Sat Jan 14, 2006 0:55
Location: Midwest USA

Post by wolfden » Wed Jun 06, 2007 2:42

Do you mean these?

System Related

This is a good place to load any misc applications/scripts at boot. Make sure to append '1>&2 > /dev/null' to the end of the program run line.

This is a good place to unload any programs that were started with '/etc/conf.d/local.start'.

Configuration settings for dispatch-conf (an alternative to etc-update with similar configuration parameters).

Configuration settings for etc-update (such as your favorite diff-command, arguments for cp, mv and rm) are stored here.

Controls which users can log in, and from where. Useful to forbid root logins from anywhere but physical console.

Contains many variables for controlling logins, such as password aging and the number of permissible login attempts by a user.

This is probably the most important of all the configuration files - it controls how Gentoo builds new packages you emerge. See the man page for more information.

File which lists the kernel modules to load at boot

Sets basic system startup options.

Config file for sysctl. Sets kernel parameters on startup, such as ip_forward.

Settings for filesystem types that are NOT indexed by updatedb (or slocate -u). If you want an NFS or Samba mount to be indexed, you can remove the appropriate types from the PRUNEFS variable. The types are the same as used in the /etc/fstab file.

Config file for cryptsetup-luks. Sets cryptsetup-luks parameters on startup, such as mounting points.

Network Related

If you are using DISTCCD to speed up compilation on a network, there are some options here. Of particular interest is the DISTCCD_NICE variable.

Basic network card configuration. Contains details of how the IP address is set, as well as the gateway. Both static IP's and DHCP is configured here.

Wireless network card configuration. You need a pretty new baselayout for this though (eg. 1.9.x).

Lists the IP addresses of hosts on a local network. IMPORTANT: the line localhost should always be present!

Lists your DNS servers. If you are using DHCP, this file will be overwritten each time your network interface goes up.

Settings for the SSH server. One important setting is PermitRootLogin which you can set to "no" to disable root logins (you can still ssh as a normal user, and then su to root).

Hardware Related

This is the list of devices that should be mounted at boot time (e.g. hard disks), and also defines mount points for other devices (e.g. CD-ROMs).


If you are using the GRUB bootloader, this is normally where the boot menu config file is.

If you are using the lilo bootloader, an example config is includes at /etc/lilo.conf.example

See Also HOWTO Framebuffer:Bootsplash:Grubsplash

Sound Related

ALSA audio settings. This file is auto loaded and saved on startup and shutdown. Tune (indirectly) via `alsamixer`

OpenAL per-user settings. This is used by programs that utilize the OpenAL sound library such as Unreal 2003/2004

See Also: HOWTO ALSA sound mixer aka dmix

Video Related

X.org configuration. If this file does not exist then /etc/X11/XF86Config is used.

Post Reply