On Fri, Oct 23, 2009 at 8:34 AM, Marty Scholes <[email protected]> wrote: > [...] > Shortly after the SXCE EOL announcement, I took the plunge and installed > OSol and noticed things went rather smoothly, but I am experiencing a few > things not mentioned elsewhere. > > The Xinerama option (utxconfig) is not honored -- at all. The workaround is > after > every restart to perform the following. > > $ pfexec rm /etc/opt/SUNWut/ut_disable_xinerama > $ pfexec /opt/SUNWut/sbin/utrestart -c > > Has anyone else noticed this?
That's caused by logic in /etc/init.d/utsyscfg. That script runs during boot. It looks to see whether Xsun on this system supports Xinerama. If not then it creates that file, which disables Xinerama for Sun Ray. On OSol Xsun does not exist so the file always gets created. This has been fixed in SRSS 4.2. You can work around it in SRSS 4.1 by editing /etc/init.d/utsyscfg and inserting a 'return' statement as the first line in the 'xsunoptions' function, or comment out the call to 'xsunoptions' in the 'case' clause near line 387. As the discussion in the 'Which OS' thread says, lots of little OSol niggles have been fixed in 4.2. > Also, the DTUs on a MH display seem to refresh one at a time. For example, I > will go to a virtual desktop and the right screen will refresh, then the > center, then > the left. The order seems to be random, but they don't refresh > simultaneously. I > assumed this was because I had only a single 100mb NIC on the server, allowing > one DTU to consume all bandwidth. Later this year, I will be putting in a > V40Z > which has GBE and am hopeful it will perform better. Maybe. You'll still only have 100MBps to each Sun Ray unit. The GbE link might even hurt painting, depending on how well the switch buffers UDP traffic that comes in at 1Gb but needs to go out at 100Mbps. If that happens then you can tell Solaris to use a more fine-grained scheduling timer and that will allow the Xserver to pace its painting traffic more smoothly. The serialised painting is just a quirk of the way multihead was implemented. It looks odd at session startup or when hotdesking but apparently isn't a cause for concern after that. Since nobody has reported it as a problem, reworking that code is a long way down our Xserver to-do list. > Finally, is there any way to control which is the "primary" DTU in terms of > where > the login screen appears and which DTU has the GNOME task bar, menus, etc.? > It seems that the leftmost DTU always plays that role, regardless of which DTU > is primary on the MH group. It's up to Gnome to place those items. I don't know of any way to influence how it positions them, but I'm only an occasional multihead user. Perhaps someone with more multihead experience can help with this one. OttoM. __ ottomeister Disclaimer: These are my opinions. I do not speak for my employer. _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
