Sun xterm revisited.

[Wesley Hosking <wes@atlantek.com.au>]

Brian Schramm writes:
 > OK.  I asked for help once before on this.  I now need this fixed so I am
 > back to it.
 > 
 > I have Debian potato running at this time.  I did use Debian slink working
 > fine.  I saved the etc and other configuration data off the old slink
 > system on CD so I could use it to rebuild my system with.  I have
 > everything set up the way that I had it before and am still not able to
 > get the Sun xterms working.  I have set the tty0, tty2 and console on the
 > xterm directory and the debian directory to be readwrite by the world.  I
 > still get the same error messages.  I have run through all my thoughts on
 > this and I have not gotten anywhere.  I think the xfs is working but that
 > is one of the error messages.
 > Here is the error messages on the console of the bootp computer:
 > 
 > fh_verify: dev/tty2 permission failure, acc=8, error=30
 > fh_verify: dev/console permission failure, acc=8, error=30
 > fh_verify: dev/tty0 permission failure, acc=8, error=30
 > 

I get these also - I believe its something to do with it trying 
to change permissions on devices in a read-only file system.
(I had to do a hack to the 2.2.* kernel code to ignore this error - it 
should be a problem for the kernels that you are running).


 > Here is the error messages on the Xterm boot screen:
 > 
 > pexextensioninit: couldn't open default pex font file roman_mcouldn't load
 > xkb keymap, falling back to pre-xkb keymap
 > xdmcp fatal error: manager unwilling host unwilling
 >  

looks more like an xdm error, more than anything else...

What does you /var/tmp/xdm-errors look like :

mine says that I have forgotten to make xbanners available (it works
anyway)....


/usr/X11/lib/X11/xdm/Xsetup-picard_0: xbanner: command not found
/var/tmp/xdm-errors (END) 


The file locations are all set from xdm-config :
(mine follows ... )...

!
! $Id: xdm-config.Template,v 1.1 1998/01/11 11:45:25 root Exp root $
!
DisplayManager.errorLogFile:    /var/tmp/xdm-errors
DisplayManager.pidFile:         /var/tmp/xdm-pid
DisplayManager.keyFile:         /var/tmp/xdm-keys
DisplayManager.servers:         /usr/X11R6/lib/X11/xdm/Xservers
DisplayManager.accessFile:      /usr/X11R6/lib/X11/xdm/Xaccess
DisplayManager*authorize:       true
DisplayManager*resources:       /usr/X11R6/lib/X11/xdm/Xresources
DisplayManager*session:         /usr/X11R6/lib/X11/xdm/Xsession
DisplayManager*authComplain:    false
DisplayManager*chooser:         /usr/X11R6/lib/X11/xdm/chooser
!DisplayManager._0.setup:       /usr/X11R6/lib/X11/xdm/Xsetup_0
!DisplayManager._0.startup:     /usr/X11R6/lib/X11/xdm/GiveConsole
!DisplayManager._0.reset:       /usr/X11R6/lib/X11/xdm/TakeConsole
!
! Client Xsetup files defined from here.
!
DisplayManager.oldspock_0.setup:        /usr/X11/lib/X11/xdm/Xsetup-oldspock_0
DisplayManager.oldspock_atlantek_com_au_0.setup:        /usr/X11/lib/X11/xdm/Xse
tup-oldspock_0
DisplayManager.picard_0.setup:  /usr/X11/lib/X11/xdm/Xsetup-picard_0
DisplayManager.picard_atlantek_com_au_0.setup:  /usr/X11/lib/X11/xdm/Xsetup-pica
rd_0
xdm-config (END) 


...
Best thing to do is play around with xdm a bit from the command line
and see what it says, maybe strace it, or if you are masochistic debug 
what the problem might be (xdm has flags for tracing what is going
on).

wes
===========================================================================
This Mail was sent to netboot mailing list by:
Wesley Hosking <wes@atlantek.com.au>
To get help about this list, send a mail with 'help' as the only string in
it's body to majordomo@baghira.han.de. If you have problems with this list,
send a mail to netboot-owner@baghira.han.de.