RE: PXES 0.9, WYSE 5150SE, X nsc driver, screenartifacts

On Wed, 2005-04-06 at 00:05, Dan wrote:
> > There's no need to build a new image, specifying xd=vesa or
> > X_DRIVER=vesa in kernel command line does the trick.
> 
> I thought there might be an option like that, But i was not able to find
> the relevant documentation. Perhaps I did not look hard enough.
> 
> Can i set X_DRIVER in default.conf? (I have PXES fetch the configuration
> via tftp)
Yes, you can.
> 
> Is there a definitive list of the options PXES accepts?
# cat /var/run/pxes/env (99.9% of them ;-)
This document could shed some light
(http://prdownloads.sourceforge.net/pxes/PXES_PREBUILT_Images.pdf?download)

> 
> Also, will PXES be moving to xorg any time soon? Or will you stick with
> XFree86 for the forseeable future?
Yes, PXES 1.1 will be xorg based.
> 
> Thanks once again,
Are you using PXE boot ?
Are you planning to reflash those units ?
Have you seen PXES EE components (http://pxes.sf.net/enterprise) they
would help you with this task.
Could you give me a brief list of pros and cons between Wyse Linux and
PXES (this helps a lot to improve PXES) ?
> 
> Dan
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> pxes-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/pxes-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQBCU1pblPY0gYfhm/IRAlwKAJ9iqatU6wCAXpH7qa+cLg6FBOznngCgoE8/
heS/3T93LwJAFb1ulOrvvY8=
=MV0e
-----END PGP SIGNATURE-----