Light DM issues

[VastOne]

@PackRat

Booted to .xinitrc no issue... though I was a bit surprised that I actually had to initiate it with a startx command... Is there anyway to login and have a startx start upon that login... easy fecking peasy indeed

@statmonkey... I have no issue in getting the code the way we want/need it and creating a deb just for that also... dpkg-repack tool is awesome just for that

Will talk later... need to do some shopping

This has been a productive day for V-Ger

[VastOne]

FECK LightDm and any other BS login managers

Thanks to PackRat I began looking closely at xinit and startx and .xinitrc

I created this file .bash_profile and now when I login from the initial tty screen, fluxbox starts perfectly.. If I find a way to have a background image or statement on that tty, it will be perfect

First install xinit

Code Select Expand

sudo apt-get install xinit

or

Code Select Expand

get xinit

~/.bash_profile

Code Select Expand


# Created by V-Ger for use in the VSIDO env
# ~/.bash_profile: executed by bash(1) for login shells.

# the default umask is set in /etc/login.defs
#umask 022

# include .bashrc if it exists
if [ -f ~/.bashrc ]; then
    . ~/.bashrc
fi

# set PATH so it includes user's private bin if it exists
if [ -d ~/bin ] ; then
    PATH=~/bin:"${PATH}"

fi

#start X at login
if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]]; then
  exec startx

fi

This will be the default .xinitrc

Code Select Expand

#!/bin/sh

########################################################################
##  Created by V-Ger for use in the VSIDO env                         ##
########################################################################

########################################################################
##  Merge in defaults and keymaps                                     ##
########################################################################

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

if [ -f $sysresources ]; then
    /usr/bin/xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    /usr/bin/xmodmap $sysmodmap
fi

if [ -f $userresources ]; then
    /usr/bin/xrdb -merge $userresources
fi

if [ -f $usermodmap ]; then
    /usr/bin/xmodmap $usermodmap
fi

########################################################################
##  Start FluxBox Desktop Environment                                    ##
########################################################################

  exec dbus-launch --exit-with-session /usr/bin/startfluxbox
fi

This will be on the next ISO released

[PackRat]

Booted to .xinitrc no issue... though I was a bit surprised that I actually had to initiate it with a startx command... Is there anyway to login and have a startx start upon that login... easy fecking peasy indeed

Just like you did it with the .bash_profile, or - with sysv  or bsd init - you can put startx in the rc.local. I don't know if the rc.local file will become deprecated as systemd moves forward. I suppose you could write a startx.service file to get you where you want to go. And take a look with htop to see how much memory you save by not using a display manager.

there is also this method

#start X at login
if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]]; then
  exec startx
fi

I believe that will startx when you log in from tty1 and then log you out when you exit X.

And since you are calling xmodmap and xrdb in your .xinitrc, you can comment those commands out of your ~/.fluxbox/startup  - no harm calling them twice, just being efficient.

As far as images go, you may be able to do what slackware and some other distros do with the Tux penguine image in the upper left - I don't know how that is accomplished. Another option would be some ascii art like FreeBSD does. A full screen image may be out of the question - even if you put it in the frame buffer, I think it would cover the login prompt.

Finally, I'm not sure if the ck-launch-session part is necessary any more. That refers to console kit which is now handled by systemd - the example I posted earlier was for slackware bsd init. Doesn't seem to matter, just another of those efficient coding things. It's a learning process, no doubt in my mind you'll master it.

[VastOne]

^ Thanks for those PackRat...  I have made the changes you suggested and it is becoming a clearer picture now.  One I am enjoying

The changes are reflected in the post above and the config files

I will look at putting some kind of image there eventually..

Today has been a good day

Thanks to everyone who assisted...

[jedi]

Works perfectly, of course!  Nice work PackRat, you've inspired VastOne!  This works beautifully.  I had removed lightdm on Sunday last, and started using SliM.  Today I removed SliM as well, and am using the above two files to login and out.
Beautiful work guys...   

[PackRat]

cool it's working for you two.

This is a good read - explains how all this works together on logins:

http://www.linuxfromscratch.org/blfs/view/svn/postlfs/profile.html

I have never used a .bash_logout file, but that looks like it could be interesting.

[VastOne]

^ Thanks for that... A really well done read and explanation. I will be following that closely for the VSIDO standards.

[PackRat]

No problem.

Right now I'm setting up the .xinitrc for multiple window managers ( we all have at least 3 installed, correct  ).

Automounting removable drives is a bit trickier; I have a work-around-and-around-and-around going that works just fine, but there has to be something more elegant.

Seen some references to systemd.automount (for Manjaro) for external drives, nfs shares and that sort of thing never heard of that service before. Will need to investigate it at some point.

[jeffreyC]

I think that they have done something like what you are working on over at LinuxBBQ, I know they have no love for login managers.
Maybe worth a look, why spend time reinventing the wheel?
The fish may be biting or............

[PackRat]

thanks

just looked at their cream edition with all the wm's. Got the ncurses list of wm's going; just need to figure out automounting for removable media.

[VastOne]

Got this in a tweet... Thought it was nice ... have not had a chance to follow up yet

Too busy being sick

Eugenio Paolantonio @eugenio_g7   From Semplice Linux

@VSIDO I'm reading in your forums that you have issues with lightdm,  here's the fix we used: Hope it helps!

[PackRat]

That's cool those people visit the vsido forum and offer up some help. Kudos to semplice.

[lwfitz]

Did someone say the fish are biting?

[PackRat]

I wish.

[statmonkey]

That is beyond cool.  Semplice is a nice package, really well put together.  I actually have my Mother using it, can't be too bad if it's usable for an 86 year old.  I also found the people over there very helpful.