I checked in the version output line. Unless you can tell me why it hurts anything for the shared memory segment ID to be printed first, I'm going to file that under "things that aren't going to be perfect."
On 5/25/11 9:34 AM, Nathan Kidd wrote: > On 11-05-24 10:24 PM, DRC wrote: >> This belongs in __vgl_fakerinit(). > > Heh, where it was till I didn't like the line > > [VGL] Shared memory segment ID for vglconfig: 510853141 > > always getting printed first. The attached patch achieves this instead > by not printing the shared memory segment line till __vgl_fakerinit(). > > Again, not a simple one-liner to achieve this: > > [VGL] VirtualGL v2.2.80 64-bit (Build 20110524) > [VGL] Shared memory segment ID for vglconfig: 510853141 > > instead of: > > [VGL] Shared memory segment ID for vglconfig: 510853141 > [VGL] VirtualGL v2.2.80 64-bit (Build 20110524) > > -Nathan > > > > ------------------------------------------------------------------------------ > vRanger cuts backup time in half-while increasing security. > With the market-leading solution for virtual backup and recovery, > you get blazing-fast, flexible, and affordable data protection. > Download your free trial now. > http://p.sf.net/sfu/quest-d2dcopy1 > > > > _______________________________________________ > VirtualGL-Devel mailing list > VirtualGL-Devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/virtualgl-devel ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ VirtualGL-Devel mailing list VirtualGL-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-devel
