Date: Tue, 28 May 1996 15:13:40 EST From: "Kaleb S. KEITHLEY" <kaleb@x.org> To: Terry Lambert <terry@lambert.org> Cc: joerg_wunsch@uriah.heep.sax.de, chat@FreeBSD.ORG Subject: Re: Forgiving select() call. Message-ID: <199605281913.PAA19638@exalt.x.org> In-Reply-To: Your message of Tue, 28 May 1996 11:32:38 EST. <199605281832.LAA11511@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> > > > If there's a secret undocumented select system call in Solaris, I'd > > like to know about it, with something more than anecdotal evidence! > > 1) Build a static SunOS 4.1.3 binary that calls select(2). Been there, done that. See my previous reply. Trussing on Solaris 2.4 shows it calling poll. > 2) Run it on Solaris 2.2 (watch it ENOSYS). > 3) Run it on Solaris 2.3 (watch it work). What does trussing it on 2.3 show it doing? > It's there. But like the BSD 4.4 "HIDDEN" attribute for the "undelete" > and "whiteout" system calls, the calls do exist, even if the syscalls.h > doesn't openly admit it. That's nice, but I don't see how it applies to Solaris. For my money I prefer to use documented features. The fact is that on BSD 4.4 the source is the documentation. When Sun releases the source to Solaris you can make your argument about system calls that aren't in <sys/syscall.h> > Use syscall( 93, ...) in place of a select(2) stub. I'm not sure if > the magic number is significant; you may actually get select(2) if you > use /usr/ucb/cc (the compatability compiler). Yeah, I've done the syscall thing too. Trussing it shows it calling poll. See my previous reply on this topic. >Personally, except for threading, I develop for Solaris using SunOS. You obviously have your reasons for doing that. For my money I develop for Solaris on Solaris. -- Kaleb KEITHLEY
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605281913.PAA19638>