[osol-discuss] what is a door file ?
In solaris, lately I have seen some door files.. can someone please enlighten me about the door files [EMAIL PROTECTED]:/u/mulleyn file /var/run/syslog_door /var/run/syslog_door: door [EMAIL PROTECTED]:/u/mulleyn like What are door files mainly for and what purpose do they serve..etc..,/ Regards, Nikhil ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] libm sources from SchilliX-0.2 have been released
Note that this is not a source that is in a really clean state, but it compiles using a standard make program (smake) and it creates an installable tar archive that includes the resulting binaries and include files. ftp://ftp.berlios.de/pub/schillix/libm-sun-freebsd-schily-0.3.tar.bz2 As long as Sun does not publish the original Solaris libm sources, tese sources may help to create Solaris ports like the Solaris PPC port. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED](work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: what is a door file ?
from the libdoor(3LIB) manpage: Doors are a fast light-weight RPC mechanism for secure control transfer between processes on the same machine. Conceptu- ally, a thread in one process can issue a call using a door descriptor that causes code to be executed in another pro- cess and then returns using the traditional synchronous RPC model. Doors can also be used to pass data and file descriptors between processes. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: what is a door file ?
Oh..Thanks William :) Is there any small code example for demonstration .. Thanks again. NikhilOn 11/13/05, William D. Hathaway [EMAIL PROTECTED] wrote: from the libdoor(3LIB) manpage:Doors are a fast light-weight RPCmechanismforsecurecontrol transferbetweenprocesseson the same machine. Conceptu- ally, a thread in one process can issue a call using adoor descriptorthatcauses code to be executed in another pro- cess and then returns using the traditional synchronousRPC model. Doorscanalsobeusedtopassdata and file descriptors between processes.This message posted from opensolaris.org___opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: what is a door file ?
For sample code, Rich Teer has examples (and a whole 40 page chapter on doors) in his excellent Solaris Systems Programming book. I would highly recommend this book to anyone that is programming on Solaris. You can download sample source code and find more info on his book at http://www.rite-group.com/rich/ssp/ (the doors chapter is 22). This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: what is a door file ?
On Sun, 13 Nov 2005, Nikhil wrote: Oh..Thanks William :) Is there any small code example for demonstration .. Hi Nikhil, If you have Solaris Systems Programming, check out pages 951 - 992. Rich provides numerous examples and a great explanationn of the door IPC facility. Thanks, - Ryan -- UNIX Administrator http://daemons.net/~matty ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: what is a door file ?
William D. Hathaway wrote: For sample code, Rich Teer has examples (and a whole 40 page chapter on doors) in his excellent Solaris Systems Programming book. I would highly recommend this book to anyone that is programming on Solaris. You can download sample source code and find more info on his book at http://www.rite-group.com/rich/ssp/ (the doors chapter is 22). This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org I don't have code samples, but I did a brief writeup on doors for a custoemr magazine a few years back. http://au.sun.com/news/onsun/2002-11/tech_tips.html alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Staff Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Anyone succeded in porting xine to Nevada?
In Nexenta we have it: % apt-cache search xine libxine1c2 - the xine video/media player library, binary files xdmx - Distributed Multi-head X server libxinerama-dev - X11 Xinerama extension library (development headers) libxinerama1-dbg - X11 Xinerama extension library (debug package) libxinerama1 - X11 Xinerama extension library libxine-dev - the xine video player library, development packages totem-xine - A simple media player for the Gnome desktop based on xine totem-gstreamer - A simple media player for the Gnome desktop based on gstreamer x11proto-panoramix-dev - X11 panoramiX extension wire protocol x11proto-xinerama-dev - X11 Xinerama extension wire protocol totem - A simple media player for the Gnome desktop (dummy package) though, it is not tested well... Erast On Sun, 2005-11-13 at 17:39 -0300, Alfredo Peña wrote: I'm trying to run xine-ui in Nevada b25 (Solaris Express build 25) without success. Here is what I have right now: - xinelib should be compiled with gcc and linked with gld, Solaris native ld doesn't work (lots of relocation problems) - there are several glibc functions used by xinelib and xine-ui that doesn't have an implementation in Solaris libc and the xine configuration step doesn't check for. These are strsep, strndup and getline. I replaced them with implementations I found in the web. - gxine cannot be built with the gnome version shipped, as it requires gnome 2.10, so I tried xine-ui xine-ui dumps core after initialising the xshm extension, this is the stack trace: #0 0xce3ff4f8 in resolve_object () from /usr/lib/libX11.so.4 #1 0xce3ff854 in _XsunOsDynamicLoad () from /usr/lib/libX11.so.4 #2 0xce3a2763 in _XOpenLC () from /usr/lib/libX11.so.4 #3 0xce3b5cf7 in _XlcCurrentLC () from /usr/lib/libX11.so.4 #4 0xce3ed917 in _XkbGetCharset () from /usr/lib/libX11.so.4 #5 0xce3eb879 in _XkbLoadDpy () from /usr/lib/libX11.so.4 #6 0xce3b77b8 in XKeysymToKeycode () from /usr/lib/libX11.so.4 #7 0x080c2d7f in xitk_init () Can anybody give me a tip on what is wrong? Thanks, Alf ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Anyone succeded in porting xine to Nevada?
On 11/13/05, Alfredo Peña [EMAIL PROTECTED] wrote: I'm trying to run xine-ui in Nevada b25 (Solaris Express build 25) without success. Here is what I have right now: - xinelib should be compiled with gcc and linked with gld, Solaris native ld doesn't work (lots of relocation problems) - there are several glibc functions used by xinelib and xine-ui that doesn't have an implementation in Solaris libc and the xine configuration step doesn't check for. These are strsep, strndup and getline. I replaced them with implementations I found in the web. - gxine cannot be built with the gnome version shipped, as it requires gnome 2.10, so I tried xine-ui xine-ui dumps core after initialising the xshm extension, this is the stack trace: #0 0xce3ff4f8 in resolve_object () from /usr/lib/libX11.so.4 #1 0xce3ff854 in _XsunOsDynamicLoad () from /usr/lib/libX11.so.4 #2 0xce3a2763 in _XOpenLC () from /usr/lib/libX11.so.4 #3 0xce3b5cf7 in _XlcCurrentLC () from /usr/lib/libX11.so.4 #4 0xce3ed917 in _XkbGetCharset () from /usr/lib/libX11.so.4 #5 0xce3eb879 in _XkbLoadDpy () from /usr/lib/libX11.so.4 #6 0xce3b77b8 in XKeysymToKeycode () from /usr/lib/libX11.so.4 #7 0x080c2d7f in xitk_init () Can anybody give me a tip on what is wrong? Thanks, Alf xine builds and runs fine on S10 FCS with SunStudio 10 and /usr/ccs/bin/ld and very aggressive optimizations, on both UltraSPARC and X86. on SPARC it runs with no problems at all, no dropped frames, with the xshm extension. on X86 it runs equally well with the xv extension and Xorg. both SPARC and X86 run with no problems in fullscreen mode (definition of no problems: watching a 2hr 15min DVD movie with no problems to report). screenshots of running xine with libxine-1.1.0 and xine-ui 0.99.4: http://www.flickr.com/photos/skipjackdes/ strsep and strndup are provided by libxine and can be found in libxineutil.a. getline is part of GNU libgettext. ./configure checks for these functions and flags their presence or absence in libxine's config.h. the SEGV above is caused by calls to libintl_bindtextdomain(). --Stefan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
