iB::Topic::a couple of X questions

	Damn Small Linux :: Damn Small Linux Board The DSL Forums

» Welcome Guest
[ Log In :: Register ]

Damn Small Linux Board » Damn Small Linux » X and Fluxbox » a couple of X questions

		Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
		Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic

[ Track this topic :: Email this topic :: Print this topic ]

Topic: a couple of X questions

< Next Oldest | Next Newest >

jwaddell

Group: Members
Posts: 2
Joined: Nov. 2006

Posted: Nov. 14 2006,19:08

Hey all,

I've built a secure openvpn livecd based off of dsl and I'm having a couple of little issues I'd like to clean up relating to X and jwm.

The first is related to jwm and that is I desire the openvpn startup script to run automatically. The way I tried to do what was to put it just after the <RootMenu> label. I expected it to just run when X came up. However the mouse has to be moved to get it to start (this is intermittent...sometimes a mouse move, sometimes a mouse click, sometimes it doesn't come up). So the question is what is the best way to get a script to run on X window start-up. If I put it in the .xinitrc then there are issues of backgrounding that end up having jwm not start...hmmm.

The second is a more generic issue in that. I don't have control over which machines the cd will be deployed to. In alpha testing we've discovered plenty of machines that do not autodetect the video correctly and dump the user either into no X, completely broken system, or into an 8-bit X where the remote system the user is being sent to can not be used properly...blah. Any advice on either problem is welcome.

Jeff

^thehatsrule^ Offline

Group: Members
Posts: 3275
Joined: July 2006

Posted: Nov. 14 2006,19:38

What did you put in .xinitrc?
Afaik, putting the execution line ie. after the dillo one with a & at the end for backgrounding works in most cases.

You could have it boot with "dsl xsetup" to be asked for the video... don't know about doing it automagically though. You could also try the vesa video driver with the full XF86 server and see if that works better.

jwaddell

Group: Members
Posts: 2
Joined: Nov. 2006

Posted: Nov. 14 2006,21:04

I understand that I can background a process with '&'. The problem is that the script blocks waiting for the password to the key so it can connect via vpn...If I background that it still blocks... If I try to reverse order and launch the jwm backgrounded first, jwm just starts and then exits...which causes the xsession to end. It's an annoyance...I'll keep playing around with the order and how the scripts are written to see what can be done...I'm mostly just disappointed that I *thought* jwm had a launch app on initiation feature and apparently it does not. I'm also annoyed that openvpn does not seem to return a useful error code so I can NOT bring up the remote desktop session when vpn FAILS to connect. Thanks for the reply

Jeff

mikshaw

Group: Members
Posts: 4856
Joined: July 2004

Posted: Nov. 14 2006,22:08

I'm not completely clear on your issue, but this is what it sounds like.....

You need to input a password before the vpn session will run. If it's backgrounded then you can't get at the password, but if it's not backgrounded then the window manager doesn't start until after the vpn session ends.

If this is true, try running the startup script from xinitrc in aterm, backgrounded:
aterm -e /path/to/script &

--------------
http://www.tldp.org/LDP/intro-linux/html/index.html