Since RTLinux offers read/write directly, I wonder what the problem is?

On Fri, Nov 09, 2001 at 03:25:19PM +0100, Ivan Martinez wrote:
>       What I need from unistd.h is to allow users to use the standard 
> open-read-write-close interface with realtime fifos, which AFAIK is supposed 
> to work in realtime code and it actually does in my non-C++ modules.
>       The alternative is rtf_put-rtf_get, but then I can't say DSLib completely 
> encapsulates RTLinux' interface anymore.
>       Ivan
> 
> On Friday 09 November 2001 09:51, Chunky Kibbles wrote:
> > On Thu, Nov 08, 2001 at 04:56:31PM +0100, Ivan Martinez wrote:
> > > Anybody help me with this, or you won't have a brand new DSLib v1.3.0
> > > supporting C++
> > > ;-)
> >
> > <unistd snippage>
> >
> > What do you need from unistd.h? The problem is that if you're in
> > suitable kernel space for a real-time module, you won't be allowed
> > most of the functions in unistd. poll() is right out. fork() doesn't
> > makes sense...
> >
> > Gary (-;
> > -- [rtl] ---
> > To unsubscribe:
> > echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
> > echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
> -- [rtl] ---
> To unsubscribe:
> echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
> echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
> --
> For more information on Real-Time Linux see:
> http://www.rtlinux.org/
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
--
For more information on Real-Time Linux see:
http://www.rtlinux.org/

Reply via email to