Re: linuxfs_probs

• To: gdenys@acm.org (Geert Denys)
• Subject: Re: linuxfs_probs
• From: Godmar Back <gback@cs.utah.edu>
• Date: Mon, 1 Mar 1999 16:38:17 -0700 (MST)
• Cc: oskit-users@cs.utah.edu
• In-Reply-To: <36DB1DAF.21AB6226@acm.org> from "Geert Denys" at Mar 1, 99 11:07:27 pm
• Sender: owner-oskit-users@fast.cs.utah.edu

 I don't think the OSKit supports named pipes at this time.
You should be able to use unnamed pipes, however.

	- Godmar

> 
> Hi,
> because I need to exchange data between an oskit_socket-implementation and my Java protocol stack, I use named pipes for the moment. I can read and write regular files on my Linux-fs with the Oskit. With named pipes however, problems arise, both when trying to read or write.
> 
> Oskit is giving me the following output when attempting to read or write to a named pipe:
> 
> ___________________________
> Dump of trap_state at 0x00171ea0
> ... some registers
> trapno 13, error 00000000, from kernel mode
> ...
> terminates due to trap
> 
> backtrace fp=171e54
> 
> _exit(1) called
> ____________________________
> 
> Any help is welcome.
> =================================
> To subscribe or unsubscribe, send mail with "subscribe" or "unsubscribe"
> to oskit-users-request@flux.cs.utah.edu.  The oskit-announce list is low
> volume - if you want to subscribe, mail oskit-announce-request@flux.cs.utah.edu
> 

=================================
To subscribe or unsubscribe, send mail with "subscribe" or "unsubscribe"
to oskit-users-request@flux.cs.utah.edu.  The oskit-announce list is low
volume - if you want to subscribe, mail oskit-announce-request@flux.cs.utah.edu

• linuxfs_probs
• From: Geert Denys <gdenys@acm.org>

• Prev: linuxfs_probs
• Next: kernel too big
• Index(es):
  • Main
  • Thread