slim login problem - anyone succeed in configuring slim?
dear friends
my machine is old and now i am running xfce4, and i just want to get rid of kdm, and think i should try slim http://slim.berlios.de/index.php i tried putting Code:
x1:4:respawn:/usr/bin/slim >& /dev/null did any one succeed in running slim in slack12? |
Do you haveth fox libraries compiled and installed. slim uses the fox libs.
For an easier and better alternative use wdm which just needs windowmaker installed (for the libs) which is already part of slackware. slim is a fox-libs clone of wdm anyway, so if you like slim you shoulf like wdm. Get sources and/or package here: http://distro.ibiblio.org/pub/linux/...inDisplay/wdm/ |
slim was soo slim ;)
let me try wdm then and i will come back soon with the results thank you Note: shall i install amigo tgzs? |
Yes, I think the package I have will work for you. If not, you can try re-compiling it as a first test of src2pkg once we get that working correctly(from the anyone with athlon-xp) thread.
This is not the correct thing to do: Code:
x1:4:respawn:/usr/bin/slim >& /dev/null Code:
#! /bin/sh |
any special option specific for athlon xp ?
i simply tried src2pkg wdm-1.28.tar.gz or shall i try src2pkg -a i686 wdm-1.28.tar.gz |
Ok, so you are using src2pkg -good.
At the moment the athlon support won't be working but we'll work on that. Still you should have no problem getting a package, but you#ll want to pass a couple of options to configure to get a better package: src2pkg -e='--localstatedir=/var --disable-pam \ --with-wdmdir=/etc/X11/wdm --with-fake-home=/var/run/wdm \ --enable-exitlogin --enable-aafont' wdm-1.28.tar.gz That should do the trick. You can test the thing easily just by booting up normally in runlevel 3 and then typing 'wdm' after logging in as root. If you like what you see, then do the edit I suggested on your rc.4 file and then boot up into runlevel 4 to use it. if you want to stcik with it, I'll try over the next few days to get together the materials I have for the way I use it which makes it really easy and slick to use. I even have it running xpenguins so you get animated penguins to go with the login screen :-) My 4-year-old son loves em! I created a really flexible system for wdm which lets you have autostart files for each window manager without having to edit the system-wide initrc. And I've written a configuration tool which lets you put all the options into just one configuration file -it's really pretty slick and versatile! |
Quote:
the configure option had done the job, earlier it was showing missing libraries error message(with src2pkg wdm.xxx..x.x) this one worked, thank you for the great explanatory posts now i dont want kdm :) now the funny part is there is no xfce4 option in wdm :) and no themes, looks like we are working with slackware8 later on i will beautify it Edit : editted /etc/X11/wdm/wdm-config added Xfce and logos regards |
I was just looking this morning at my other source directory for the modified wdm. It does include xfce and nearly any other window manager you have installed. The yources and package contain quite many files and lots of changes that make it work really smooth. Because of this, I need to take a little time to arrange the sources so that you can work with them more easily, before I upload them. I'll let you know when they are ready. Since you like what you see, I'll try to get this done soon so you can enjoy wdm and use it more effectively.
Meanwhile, I'll include here a copy of the /etc/X11/wdm/Xclients file which should give you an entry for xfce: Code:
#!/usr/bin/bash -login |
i went for a coffee and came back i editted the /etc/X11/wdm/wdm-config and i added xfce here
Code:
DisplayManager*wdmWm: WindowMaker:BlackBox:KDE Code:
! DisplayManager*wdmBg: none regards rkrishna |
i was being silly :-), now i added xdce part of Xclients to my Xclients file. let me check if it works or not
Edit: i should copy ur Xclients and check. because simply adding the relevent part of xfce didnt worked or i didnt copied properly Quote:
no kde, no blackbox i will try to fix it thank you |
Lets try doing it this way. I've uploaded my directory with the 'hacked' version of wdm. Dont try building it from source just yet since things need to be fixed up to make that easier.
But, there is a tgzp ackage there which should work just fine for you since you are running Slack-11.0. You'll find that here: http://distro.ibiblio.org/pub/linux/...jects/AFX-wdm/ Be sure to download the README there also as it will tell you more about how to use the modified version. When you install the package it will automatically configure itself to use any of the main window managers you have installed. wdm uses several configuration files for different features. But my 'hacks' have provided a configuration tool (/etc/X11/wdm/ConfigureWDM). Using this tool allows you to make most configuration changes just by editing the file /etc/wdm.conf and then running the program /etc/X11/wdm/ConfigureWDM. I'll explain any questions you have about using it. |
Quote:
thank u let me try it |
worked., all those tuxes moving flying .. thank you
i just installed your package and it is working nicely without any additional configuration
i think i should change the name of the thread to be slim --> wdm the funny part is, we started from slim and endedup configuring something else thank you once again to your patience and help regards rkrishna |
Glad that it is working for you. I always take note of references to slim as it is a clone of wdm. wdm was originally based on xdm but no longer includes any xdm code. But the config files and names are still mostly the same as for xdm.
My AFX-wdm is one of my favorite little hacks. Since you have started using it, I'll tell you about an undocumented trick that I built in. This is mostly useful if you someitmes run different window managers. AFX-wdm can use autostart files to start programs to run on your desktop. You can set up one file which will start the same programs for any window manager or you can set up individual files with different options for each window manager. This system allows you to autostart programs without having to edit your system-wide xintrc files. For instance, I use WindowMaker with ROX-Filer and 'taskbar' as my main desktop. So, when I want to use Window Maker I want the Filer and taskbare panel to be started automatically. I do this by cerating a hidden file called '.Xstartup.wmaker' in my $HOME directory. Inside it has these lines: rox -p=Default taskbar -amx & For icewm I have a file called '.Xstartup.icewm' witht these lines: icewmtray & rox -p=Default To use one file with the same entries for all window managers just name it '.Xstartup.all' Note that usually all entries will have an '&' at the end in order to background the process. ROX-Filer doesn't need this as it backgrounds itself. be sure to read the /etc/wdm.conf file for tips on how you can change settings if you want to -like changing the images displayed. |
Quote:
Quote:
and let me make more changes in other places, have to do a lot of configuration in slack 12. then i wil beautify my wdm, thank you |
Just because the thread is so SLiM I wanted to tell how good SLiM works on several slackware 12 boxes I configured.
You simply have to run make && make install or you can even instead of make install run make DESTDIR=/tmp/slimpkg install and than go there and run makepkg slim-1.3.0-i686-1.tgz (for example). If you installed that package or did run make install you have a file /etc/slim.conf in there I do "deamon no" and "hidecursor true" you can chose a default user there and so one ... In /etc/inittab you can chose runlevel 4 as default and than I change my /etc/rc.d/rc.4 so it matches the following: Code:
#! /bin/sh Code:
cp my_favorit_picture.jpg /usr/share/slim/themes/default/background.jpg |
/y0shi
thank you for the help, right now i am using wdm, haev to try slim too, but my only problem was to, get it running. i think i even tried editing the rc.4 file. i have to check once again. anyway thank you for your information, it will also help others who wanted to make slim their login manager ;) regards |
You can test run slim (or wdm) by booting normally into runlevel 3. Then login as root and just run display manager. This will at least tell if it's working. If it does start, you can then check if it works for runlevel 4 by editing your rc.4 file as needed. Then from a console give the command 'init 4'. If it works (at least to let you login) but you need/want to change something or re-test, after logging in from the GUI as root, open a terminal and run 'init 5'. This will kill the display manager and return you to the command-line login. To re-test run 'init 4' again. this makes it easier to be sure you have got things working right before commiting to booting up in runlevel 4.
|
Quote:
|
No, actually I menat 'init 5'. Trying to switch to runlevel 3 from runlevel 4 can cause lockups. If youn really need to be back in runlevel 3 after being in runlevel 4, you can run 'init 3' after logging in from runlevel 5 -but this shouldn't be necessary as runlevel 5 and 3 are setup the same for Slackware. I'm not sure why it doesn't always work to switch directly from 4 to 3 and not all setups will show this problem, but still it seems to be a safer way to exit from runlevel 4.
|
Quote:
but all other linuxes use init 5 for graphical login manager i tried slim from telinit 3 and it caused some problem. wil try slim later |
All times are GMT -5. The time now is 02:27 AM. |