Re: New PXES user with a couple questions

> I run a small lab with some aging NCD Xterms.  I've recently been given
> some old Dell Latitudes to work with.  After a bit of searching, I found
>  the PXES project and it looks like the perfect solution.
>
> I installed PXES and was able to get a working Thin Client without much
> trouble.  Thanks to Diego for such a useful product!
>
> There are a few questions I have that I can't find answers to in any
> FAQs or docs.  Maybe some list members can help out...
>
> I'll start with the easy question:  PXES has a fish logo, is it supposed
>  to be pronounced "Pisces"?
I think it's more like "pixies".
>
> Issue #1:
> When I boot a machine, it takes about 7 or 8 minutes to load the image.
>   Is this just me?  I've tried both a stock build and a custom config
> and get approximately the same result.  The client is a P3@650 with
> 192MB RAM.  The server's not slow either and they're on 100Mbps switched
>  network.  Once booted, I can XDMCP into a Solaris Gnome session and
> have  incredibly fast graphics response when dragging/scrolling (faster
> than  most Windows PCs get on their console) so I know it's not a
> network issue.
Should boot in 15-30 SECONDS !!
Perhaps an issue in your TFTP server ?
Try the same TFTP session after the thin client has booted (CTRL-ALT-F3):
# tftp server
- get /pxes/pxes-0.8.squash
- quit
or whaterver image are you using and time the transaction.

>
> Issue #2:
> The only other issue I have is that I can't figure out how to get back
> to the PXES desktop after finishing an XDM session.  If I use windowed
> mode, I can't close the window and if I go full screen, I can't exit
> (from the Solaris login prompt, I've tried the "Return to Local Session"
>  or whatever it's called).  I wouldn't mind so much that I have to
> reboot  to connect to a different XDM server, but it takes me 8 minutes
> to  reboot (see issue #1).
I suppose you're using a LOCAL session, with a local desktop and launching
an XDM session. And yes, there's a bug in the window manager and you will
not be able to close the window, just minimize it.
You can use an indirect session to get a remote XDM connection menu.
XDM method indirect or
# X :1 -inidrect server
or
# Xnest :1 -inidrect server

>
> If someone can point me at some docs or tell me what I'm doing wrong,
> I'd greatly appreciate it.  Either one of these alone isn't a show
> stopper, but the two of them together are.  So a fix or workaround for
> either problem would get me up and running.
>
> Thanks for any help!
>
> 						The Amigo
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
> REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
> _______________________________________________
> pxes-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/pxes-devel


-- 
<pre>
    ______  ________
   /  /   \/  /___  )  I  N   T   E   G   R   A   C   I   O   N
  /  /       /___  /   I  N   F   O   R   M   A   T   I   C   A
 /__/__/\___/_____'

 Diego Torres Milano Maipu 42 Office 164 - (C1084ABB) Buenos Aires  Argentina
[email protected]  Tel: +5411 4331-2233 Fax +5411 4331-3377 www.in3.com.ar
</pre>




-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND