Dear all For a solution some of you could help to create, the idea is using YaST profile + SaX2 -a with a boot menu options which trigger a flag to run SaX2 -a as needed and if X being configure correctly it will using YaST profile to reserve the configuration. Of course you can use the same way to boot menu trigger the SaX -a or even firsttime, but "very end user" may like the automagically way. ----------------------------------- 刘俊贤 Alex Lau PRC Beijing Linux R&D Engineer Mainland-Mobile (8610) 13910181404 HongKong-Mobile (852) 91621631
On Thu, Aug 30, 2007 at 6:32 PM, in message <d6b310ce0708300332v6aaf72a7r2d2375c179b97ea1@mail.gmail.com>, "Benji Weber" <b.weber@warwick.ac.uk> wrote: On 30/08/2007, Cristian Rodriguez <crrodriguez@suse.de> wrote: no joke, when your xserver is misconfigured and dont work, you are redirected to a console no ? so, sax.sh -a will just fix your problem..
I think the original point was it would be nicer to redirect straight to sax2 -a. sax2 -a whilst solving the problem is completely useless to anyone who doesn't know that it exists.
_ Benjamin Weber
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org