Solved Re: starting kde on boot

2005-07-23 Thread Qv6
On Thursday 21 July 2005 12:15 pm, Stephen Marley wrote:
 On Thu, Jul 21, 2005 at 05:04:49PM +0100, Edd Barrett wrote:
   #based on a solution posted by S.Marley
  
   echo -n ' kdm'; (sleep 5; /usr/local/bin/kdm 
   ${kdm_flags}) 
 
  Don't do that. Use /etc/ttys if thats the effect you want.

 Any good reason not to? I posted the a solution using ttys too, but
 both required a sleep.

 To the OP: run genkdmconf

Thanks to all. The issue has been resolved. I'll try and put all steps 
in one little guide or howto (from zero to desktop in OpenBSD) so all 
the info on building an obsd kde desktop can be found in one place.



Re: Solved Re: starting kde on boot

2005-07-23 Thread Darrel

On Sat, 23 Jul 2005, Qv6 wrote:


On Thursday 21 July 2005 12:15 pm, Stephen Marley wrote:

On Thu, Jul 21, 2005 at 05:04:49PM +0100, Edd Barrett wrote:

#based on a solution posted by S.Marley

echo -n ' kdm'; (sleep 5; /usr/local/bin/kdm
${kdm_flags}) 


Don't do that. Use /etc/ttys if thats the effect you want.


Any good reason not to? I posted the a solution using ttys too, but
both required a sleep.

To the OP: run genkdmconf


Thanks to all. The issue has been resolved. I'll try and put all steps
in one little guide or howto (from zero to desktop in OpenBSD) so all
the info on building an obsd kde desktop can be found in one place.



Please do.  I can use Macintosh and am learning to use  FreeBSD, but 
so far have only had some success with Packet Firewall on OpenBSD.  I 
learned how to bridge this afternoon.  :)


I got the sources for 3.7 and Ports okay, but have not been abled 
to run X yet.  I am not sure whether to do this:


# rm -rf /usr/Xbld
# mkdir -p /usr/Xbld
# cd /usr/Xbld
# lndir ../XF4
   [...lots of output...]
# make build
   [...lots of output...]

There is not a directory called XF4?

Apparently, I was not very good with 3.7/tools/ as well, because I had 
to compile with:

# cd /usr/src/etc  env DESTDIR=/ make distrib-dirs

Thanks,
Darrel



starting kde on boot

2005-07-21 Thread Qv6
Folk,

This one has me scratching my head:

I can boot into kdm, login as a regular user and have a stock X working.
I can type startx once I'm logged in and have kde up, but with no 
mouse functionality.
The relevant section of /etc/rc.local reads thus:
#based on a solution posted by S.Marley

echo -n ' kdm'; (sleep 5; /usr/local/bin/kdm  ${kdm_flags}) 

Kdm_flags is set in rc.local.conf

I have a .xsession file in ~ that has this line

exec startx

I have also tried startkde instead of startx in .xsession, but I cannot 
get kde to come up once I'm logged in.
/etc/X11/xdm/xsession has been edited.

Any clues? something I've missed?

TIA



Re: starting kde on boot

2005-07-21 Thread Edd Barrett
 I can boot into kdm, login as a regular user and have a stock X working.
 I can type startx once I'm logged in and have kde up, but with no
 mouse functionality.

? Not sure about that one, if your mouse works in kdm.

 The relevant section of /etc/rc.local reads thus:
 #based on a solution posted by S.Marley
 
 echo -n ' kdm'; (sleep 5; /usr/local/bin/kdm  ${kdm_flags}) 
 

Don't do that. Use /etc/ttys if thats the effect you want.

 Kdm_flags is set in rc.local.conf
 
 I have a .xsession file in ~ that has this line
 
 exec startx

no. You would not put startx in .xsession. you would put exec
startkde or exec wmaker for example. Then upon running startx on
the shell, it would then execute your wm.

 
 I have also tried startkde instead of startx in .xsession, but I cannot
 get kde to come up once I'm logged in.

Thats right if your are going to use xdm. kdm will do all of that
malarky for you however. To summarize, if you want to use kdm,
.xsession is not relevant.

I think you need to tell us what exactly how you want your workstation
to behave.

Edd



Re: starting kde on boot

2005-07-21 Thread Stephan Tesch
Am Donnerstag, 21. Juli 2005 17:44 schrieben Sie:

Hi,

Since you are using KDE, did you run genkdmconf to create the kdm 
configuration files (eg. /usr/local/share/config/kdm/Xsession)?

HTH,
Stephan

 Folk,

 This one has me scratching my head:

 I can boot into kdm, login as a regular user and have a stock X working.
 I can type startx once I'm logged in and have kde up, but with no
 mouse functionality.
 The relevant section of /etc/rc.local reads thus:
 #based on a solution posted by S.Marley

   echo -n ' kdm'; (sleep 5; /usr/local/bin/kdm  ${kdm_flags}) 

 Kdm_flags is set in rc.local.conf

 I have a .xsession file in ~ that has this line

   exec startx

 I have also tried startkde instead of startx in .xsession, but I cannot
 get kde to come up once I'm logged in.
 /etc/X11/xdm/xsession has been edited.

 Any clues? something I've missed?

 TIA



Re: starting kde on boot

2005-07-21 Thread Stephen Marley
On Thu, Jul 21, 2005 at 05:04:49PM +0100, Edd Barrett wrote:
  #based on a solution posted by S.Marley
  
  echo -n ' kdm'; (sleep 5; /usr/local/bin/kdm  ${kdm_flags}) 
  
 
 Don't do that. Use /etc/ttys if thats the effect you want.

Any good reason not to? I posted the a solution using ttys too, but both
required a sleep.

To the OP: run genkdmconf

-- 
stephen



Re: starting kde on boot

2005-07-21 Thread Edd Barrett
On 21/07/05, Stephen Marley [EMAIL PROTECTED] wrote:
 On Thu, Jul 21, 2005 at 05:04:49PM +0100, Edd Barrett wrote:
   #based on a solution posted by S.Marley
  
   echo -n ' kdm'; (sleep 5; /usr/local/bin/kdm  ${kdm_flags}) 
  
 
  Don't do that. Use /etc/ttys if thats the effect you want.
 
 Any good reason not to? I posted the a solution using ttys too, but both
 required a sleep.
 
 To the OP: run genkdmconf
 
 --
 stephen
 
 

they do? I use xdm and I didnt use a sleep. Maybe its a kdm issue? 

Edd



Re: starting kde on boot

2005-07-21 Thread Stephen Marley
On Thu, Jul 21, 2005 at 08:03:49PM +0100, Edd Barrett wrote:
 On 21/07/05, Stephen Marley [EMAIL PROTECTED] wrote:
 
 they do? I use xdm and I didnt use a sleep. Maybe its a kdm issue? 

Yes, it's a kdm specific issue. It seems all gettys need to be spawned
before kdm kicks in otherwise the keyboard doesn't work correctly or the
X server shows up on the wrong console.

-- 
stephen