Subject: Re: console messages in X screwing up the screen
To: None <port-mac68k@netbsd.org>
From: Tim & Alethea Larson <thelarsons3@cox.net>
List: port-mac68k
Date: 05/16/2006 18:42:20
thelarsons3@cox.net wrote:
> I'm trying to set up my Mystic CC for use as an X-terminal.  I was reading 9.18 of the FAQ, which says:
> 
> 9.18  How do I keep console messages from messing up my X screen?
> You need to either run xconsole or else run an xterm with the "-C" option. Even then, you need to have the
>     options         UCONSOLE
> line uncommented in your config file (the GENERIC config is set up this way). Due to a bug in xconsole, you may also need to have your X startup scripts chown the console to yourself and make it readable by you.
> You can also edit /etc/syslog.conf to redirect syslog output to wherever you would like it to go.
> 
> Question 1: my xterm gives the warning "utmp_update: /dev/ttyp0: Is not owned by you" when I launch it.  The xconsole says "Couldn't open console".  I installed the aterm package I built on my other box, but when I try to launch I get "aterm: can't load color ''White'', colorID = 0, (29)" twice before it aborts.  Are these related?  What is going on?
> 
> Question 2: what is this "config" file it speaks of?  Another page says this has something to do with how the kernel is compiled?
> 
> Question 3: how do I chown the console?  Is this something I put in my personal X scripts, or a system X script, or what?

Does nobody bother running X on mac68k?  Anyone?  Anyone?  Bueller?


Tim
-- 
Tim & Alethea
christtrek.org