Сборка и настройка awesome на нетбуке

lupo@gentoo-laptop ~ % cat /proc/cpuinfo 
processor    : 0
vendor_id    : GenuineIntel
cpu family    : 6
model        : 14
model name    : Genuine Intel(R) CPU           T1350  @ 1.86GHz
stepping    : 8
microcode    : 0x39
cpu MHz        : 1867.000
cache size    : 2048 KB
fdiv_bug    : no
hlt_bug        : no
f00f_bug    : no
coma_bug    : no
fpu        : yes
fpu_exception    : yes
cpuid level    : 10
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx constant_tsc arch_perfmon bts aperfmperf pni monitor est tm2 xtpr pdcm dts
bogomips    : 3723.92
clflush size    : 64
cache_alignment    : 64
address sizes    : 32 bits physical, 32 bits virtual
power management:

lupo@gentoo-laptop ~ % free -m
             total       used       free     shared    buffers     cached
Mem:           882        842         40          0         90        352
-/+ buffers/cache:        398        483
Swap:         2047          6       2041

gentoo-laptop ~ # grep DISPLAYMANAGER /etc/conf.d/xdm
DISPLAYMANAGER="slim"

gentoo-laptop ~ # grep -v '^#|^$' /etc/slim.conf
default_path        /bin:/usr/bin:/usr/local/bin
default_xserver     /usr/bin/X
xserver_arguments   -nolisten tcp -br -deferglyphs 16
halt_cmd            /sbin/shutdown -h now
reboot_cmd          /sbin/shutdown -r now
console_cmd         /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
xauth_path         /usr/bin/xauth 
authfile           /var/run/slim.auth
numlock             off
login_cmd           exec /bin/bash -login ~/.xinitrc %session
sessionstart_cmd    /usr/bin/sessreg -a -l :0.0 %user
sessionstop_cmd     /usr/bin/sessreg -d -l :0.0 %user
daemon    yes
sessions        awesome           
sessiondir           /etc/X11/Sessions
screenshot_cmd      import -window root /home/lupo/Desktop/slim.png
welcome_msg         Welcome to %host
shutdown_msg       The system is halting...
reboot_msg         The system is rebooting...
default_user        lupo
focus_password      yes
auto_login          yes
current_theme       lotus-midnight
lockfile            /var/run/slim.pid
logfile             /var/log/slim.log

lupo@gentoo-laptop ~ % cat ~/.xinitrc                                                                                  [gentoo-laptop][0:47]
# Run conky
conky -p 5 -c ~/.conky/conkyrc_head &
conky -p 5 -c ~/.conky/conkyrc_info &
# Run Wicd client for managing wifi and wired sets.
wicd-gtk &
# Run Parcellite — a lightweight GTK+ clipboard manager.
parcellite &
# Run kbdd 
kbdd &
# Run yeahconsole
yeahconsole &
# Run @
exec awesome

grep DISPLAYMANAGER /etc/conf.d/xdm
DISPLAYMANAGER="slim"

grep -v '^#|^$' /etc/slim.conf
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path        /bin:/usr/bin:/usr/local/bin
default_xserver     /usr/bin/X
xserver_arguments   -nolisten tcp -br -deferglyphs 16
# Commands for halt, login, etc.
halt_cmd            /sbin/shutdown -h now
reboot_cmd          /sbin/shutdown -r now
console_cmd         /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
#suspend_cmd        /usr/sbin/suspend
# Full path to the xauth binary
xauth_path         /usr/bin/xauth
# Xauth file for server
authfile           /var/run/slim.auth
# Activate numlock when slim starts. Valid values: on|off
numlock             on
# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor          false
# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
#
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd           exec /bin/sh - ~/.xinitrc %session
login_cmd           exec /bin/bash -login ~/.xinitrc %session
#login_cmd           exec /bin/bash -login /usr/share/slim/Xsession %session
# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
#
# sessionstart_cmd      some command
# sessionstop_cmd       some command
sessionstart_cmd        /usr/bin/sessreg -a -l :0.0 %user
sessionstop_cmd     /usr/bin/sessreg -d -l :0.0 %user
# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
daemon  yes
# Available sessions:
# The current chosen session name replaces %session in the login_cmd
# above, so your login command can handle different sessions.
# If no session is chosen (via F1), %session will be an empty string.
# see the xinitrc.sample file shipped with slim sources
#sessions            xfce4,icewm,wmaker,blackbox
sessions        awesome
# Alternatively, read available sessions from a directory:
sessiondir           /etc/X11/Sessions
# Executed when pressing F11 (requires media-gfx/imagemagick for import)
# Alternative is media-gfx/scrot. See Gentoo bug 252241 for more info.
screenshot_cmd      import -window root /slim.png
#screenshot_cmd      scrot /root/slim.png
# welcome message. Available variables: %host, %domain
welcome_msg         Welcome to %host
# Session message. Prepended to the session name when pressing F1
# session_msg         Session:
# shutdown / reboot messages
shutdown_msg       The system is halting...
reboot_msg         The system is rebooting...
# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user        chipset
# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
focus_password      yes
# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
auto_login          yes
# current theme, use comma separated list to specify a set to
# randomly choose from
current_theme       slim-gentoo-simple
# Lock file, /etc/init.d/xdm expects slim.pid
lockfile            /var/run/slim.pid
# Log file
logfile             /var/log/slim.log

cat ~/.xinitrc
cat: /root/.xinitrc: Нет такого файла или каталога

 $ x11vnc
###############################################################
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
#@                                                           @#
#@  **  WARNING  **  WARNING  **  WARNING  **  WARNING  **   @#
#@                                                           @#
#@        YOU ARE RUNNING X11VNC WITHOUT A PASSWORD!!        @#
#@                                                           @#
#@  This means anyone with network access to this computer   @#
#@  may be able to view and control your desktop.            @#
#@                                                           @#
#@ >>> If you did not mean to do this Press CTRL-C now!! <<< @#
#@                                                           @#
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
#@                                                           @#
#@  You can create an x11vnc password file by running:       @#
#@                                                           @#
#@       x11vnc -storepasswd password /path/to/passfile      @#
#@  or   x11vnc -storepasswd /path/to/passfile               @#
#@  or   x11vnc -storepasswd                                 @#
#@                                                           @#
#@  (the last one will use ~/.vnc/passwd)                    @#
#@                                                           @#
#@  and then starting x11vnc via:                            @#
#@                                                           @#
#@      x11vnc -rfbauth /path/to/passfile                    @#
#@                                                           @#
#@  an existing ~/.vnc/passwd file from another VNC          @#
#@  application will work fine too.                          @#
#@                                                           @#
#@  You can also use the -passwdfile or -passwd options.     @#
#@  (note -passwd is unsafe if local users are not trusted)  @#
#@                                                           @#
#@  Make sure any -rfbauth and -passwdfile password files    @#
#@  cannot be read by untrusted users.                       @#
#@                                                           @#
#@  Use x11vnc -usepw to automatically use your              @#
#@  ~/.vnc/passwd or ~/.vnc/passwdfile password files.       @#
#@  (and prompt you to create ~/.vnc/passwd if neither       @#
#@  file exists.)  Under -usepw, x11vnc will exit if it      @#
#@  cannot find a password to use.                           @#
#@                                                           @#
#@                                                           @#
#@  Even with a password, the subsequent VNC traffic is      @#
#@  sent in the clear.  Consider tunnelling via ssh(1):      @#
#@                                                           @#
#@    http://www.karlrunge.com/x11vnc/#tunnelling            @#
#@                                                           @#
#@  Or using the x11vnc SSL options: -ssl and -stunnel       @#
#@                                                           @#
#@  Please Read the documention for more info about          @#
#@  passwords, security, and encryption.                     @#
#@                                                           @#
#@    http://www.karlrunge.com/x11vnc/faq.html#faq-passwd    @#
#@                                                           @#
#@  To disable this warning use the -nopw option, or put     @#
#@  'nopw' on a line in your ~/.x11vncrc file.               @#
#@                                                           @#
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
###############################################################
10/01/2012 16:19:10 x11vnc version: 0.9.13 lastmod: 2011-08-10  pid: 17314
10/01/2012 16:19:10 XOpenDisplay("") failed.
10/01/2012 16:19:10 Trying again with XAUTHLOCALHOSTNAME=localhost ...
10/01/2012 16:19:10
10/01/2012 16:19:10 *** XOpenDisplay failed. No -display or DISPLAY.
10/01/2012 16:19:10 *** Trying ":0" in 4 seconds.  Press Ctrl-C to abort.
10/01/2012 16:19:10 *** 1 2 3 4
Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key10/01/2012 16:19:14 XOpenDisplay(":0") failed.
10/01/2012 16:19:14 Trying again with XAUTHLOCALHOSTNAME=localhost ...
Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key10/01/2012 16:19:14 XOpenDisplay(":0") failed.
10/01/2012 16:19:14 Trying again with unset XAUTHLOCALHOSTNAME ...
Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key10/01/2012 16:19:14
10/01/2012 16:19:14 ***************************************
10/01/2012 16:19:14 *** XOpenDisplay failed (:0)
*** x11vnc was unable to open the X DISPLAY: ":0", it cannot continue.
*** There may be "Xlib:" error messages above with details about the failure.
Some tips and guidelines:
** An X server (the one you wish to view) must be running before x11vnc is
   started: x11vnc does not start the X server.  (however, see the -create
   option if that is what you really want).
** You must use -display <disp>, -OR- set and export your $DISPLAY
   environment variable to refer to the display of the desired X server.
 - Usually the display is simply ":0" (in fact x11vnc uses this if you forget
   to specify it), but in some multi-user situations it could be ":1", ":2",
   or even ":137".  Ask your administrator or a guru if you are having
   difficulty determining what your X DISPLAY is.
** Next, you need to have sufficient permissions (Xauthority)
   to connect to the X DISPLAY.   Here are some Tips:
 - Often, you just need to run x11vnc as the user logged into the X session.
   So make sure to be that user when you type x11vnc.
 - Being root is usually not enough because the incorrect MIT-MAGIC-COOKIE
   file may be accessed.  The cookie file contains the secret key that
   allows x11vnc to connect to the desired X DISPLAY.
 - You can explicitly indicate which MIT-MAGIC-COOKIE file should be used
   by the -auth option, e.g.:
       x11vnc -auth /home/someuser/.Xauthority -display :0
       x11vnc -auth /tmp/.gdmzndVlR -display :0
   you must have read permission for the auth file.
   See also '-auth guess' and '-findauth' discussed below.
** If NO ONE is logged into an X session yet, but there is a greeter login
   program like "gdm", "kdm", "xdm", or "dtlogin" running, you will need
   to find and use the raw display manager MIT-MAGIC-COOKIE file.
   Some examples for various display managers:
     gdm:     -auth /var/gdm/:0.Xauth
              -auth /var/lib/gdm/:0.Xauth
     kdm:     -auth /var/lib/kdm/A:0-crWk72
              -auth /var/run/xauth/A:0-crWk72
     xdm:     -auth /var/lib/xdm/authdir/authfiles/A:0-XQvaJk
     dtlogin: -auth /var/dt/A:0-UgaaXa
   Sometimes the command "ps wwwwaux | grep auth" can reveal the file location.
   Starting with x11vnc 0.9.9 you can have it try to guess by using:
              -auth guess
   (see also the x11vnc -findauth option.)
   Only root will have read permission for the file, and so x11vnc must be run
   as root (or copy it).  The random characters in the filenames will of course
   change and the directory the cookie file resides in is system dependent.
See also: http://www.karlrunge.com/x11vnc/faq.html