SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
i want to try awesome window manager but i cannot get it to start when i log in. i'm using kdm and there is no awesome to choose in the session type list.
i have tried xwmconfig and selected awesome but it looks like kdm is not respecting it.
i have also tried xdm and i cannot specify any manager apart from kde.
here are my .xinitrc
$ cat .xinitrc
# $Xorg: xinitrc.cpp,v 1.3 2000/08/17 19:54:30 cpqbld Exp $
# merge in defaults and keymaps
if [ -f $sysresources ]; then
/usr/bin/xrdb -merge $sysresources
if [ -f $sysmodmap ]; then
if [ -f $userresources ]; then
/usr/bin/xrdb -merge $userresources
if [ -f $usermodmap ]; then
$ cat .xsession
# This program, based on code found in the gpg-agent man page, is
# presumably licensed under the GPL.
# As the effects of this default .xsession on an account using
# (t)csh are not yet known, feedback and/or suggestions are welcomed.
if [ -x "$(which gpg-agent)" ]; then
if test -f $HOME/.gpg-agent-info && kill -0 $(cut -d: -f 2 $HOME/.gpg-agent-info) 2>/dev/null; then
eval $(gpg-agent --daemon)
echo $GPG_AGENT_INFO >$HOME/.gpg-agent-info
# Note that the new option --write-env-file may be used instead.
# You should always add the following lines to your .bashrc or whatever
# initialization file is used for all shell invocations:
You can take one of the xinitrc files in /etc/X11/init and use it as a starting point. Copy and rename it and then edit it to run awesome. You'll then need to start by running from runlevel 3. Run xwmconfig and choose the entry for awesome. Then 'startx'.
Usually you'll have a couple of entries in the xintrc file -since these minimal window managers don't alway have a desktop menu, you'll probably want to start at least an xterm to run at startup. So something like this should work at the bottom of the xintrc file:
i changed /etc/X11/xinit/xinitrc to be a symlink to /etc/X11/xinit/xinitrc.awesome rather than /etc/X11/xinit/xinitrc.kde. i also changed from kdm to xdm and it seems to be working now. thanks for your help
how i have to check this window manager out... it's different... does anyone know how to:
1. use key codes (revealed by xev) to make keyboard shortcuts
2. close a window (no little x button in the top right corner)
3. configure awesome so that the screens are not separate, ie so that each doesn't have it's own set of tags (dual screens)
4. related to 3, is there a keyboard shortcut that jumps between the two screens when they are separate
Zoran, I use awesome quite a bit. Which version of awesome are you using and where did you get it from?
The key is reading and customizing your configuration file. You should spend some time reading the awesome wiki. The entire window manager is keyboard driven, so you don't click a button to close a window.
I actually maintain the awesome SlackBuild from SlackBuilds.org in case that is what you used to install awesome. If that's what you used, then make sure you are reading about awesome2 and not awesome3 since my slackbuild script is for awesome2. Awesome3 is completely different than awesome2. I believe the default configuration setting for awesome2 is to use Mod4-Shift-c (see the sample config file in the docs directory /usr/share/doc/awesome-2.3.4 if you used the SlackBuild script from SlackBuilds.org).
No, I don't plan on it. I mentioned this on the SlackBuilds.org mailing list awhile back. Personally, I am happy with awesome2 and I am not crazy about all the changes in awesome3 and how it's now all lua-based. It seems you basically need to learn lua in order to write a config file now. If someone comes along and submits a separate SlackBuild for awesome3 to SlackBuilds.org that would be great, but it ain't gonna be me. :-)
And if the wiki dropped all the information about awesome2, that is unfortunate. It was my understanding it was going to be kept up there because so many users are remaining with awesome2. There are plenty of sample configs out there -- just google for "awesome2 awesomerc" or something like that.