Page 3 of 3

Re: Compiling Kernel with cgroups support and other patches

Posted: 27. Jan 2011, 11:42
by garby
Shador wrote:Upload a diff of your config and the stock slackware config to some pastebin site or similar.
Please find the diff file between the stock slackware and my config at http://pastebin.com/3AjcDWDn

Re: Compiling Kernel with cgroups support and other patches

Posted: 27. Jan 2011, 19:04
by Shador
From lxc-checkconfig:

Code: Select all

echo -n "File capabilities: " &&
    [[ ${KVER_MINOR} < 33 ]] && is_enabled CONFIG_SECURITY_FILE_CAPABILITIES ||
    [[ ${KVER_MINOR} > 32 ]] &&  $SETCOLOR_SUCCESS && echo -e "enabled" &&
    $SETCOLOR_NORMAL

Re: Compiling Kernel with cgroups support and other patches

Posted: 28. Jan 2011, 13:13
by garby
Thanks shado for the 'dirty hack' ;-)

BTW, I am having a weird problem. Once I start an lxc-container, gdm instances uses the entire resources of both of the processor.

How can I disable gdm and start x directly. I tried with a solution here (http://www.fprimex.com/linux/slackware/ ... ay-manager) but does not look like working. I tried to use CDM (http://cdm.ghost1227.com/X11), but even after specifying the binaries in (/etc/rc.d/rc.4) and commented the x4 line in the /etc/inittab, it does not present at init 4 boot (followed https://wiki.archlinux.org/index.php/CDM).

Simply I do not want to start gdm or start in runlevel 3 and then use a command to enter xserver (like startx with a tiling wm like i3) as a user. Could anyone throw some light on this? Thanks!


UPDATE: It does not seem gdm problem, because even when I run x without GDM and start a container, htop shows that the following process uses 100% of the CPU resources and 5.7% of Memory:
/usr/bin/X :0 -nolisten tcp -dpi 96 vt7 -auth /home/user/.serverauth.2452
Any input appreciated. Thanks!

(PS: In the same machine in the debian installation, it only took me 5 minutes to install, configure and run lxc ;-) and with slack/Salix I am struggling for the last four days! hmmmmm)

Re: Compiling Kernel with cgroups support and other patches

Posted: 28. Jan 2011, 18:41
by Shador
Runlevels are configured in /etc/inittab:

You can add a custom runlevel like this for example:

Code: Select all

x:5:respawn:/bin/su shador -l -c "/bin/bash --login -c 'cd; exec startx' >/dev/null 2>&1"
To change the default runlevel, set this line:

Code: Select all

id:5:initdefault: