From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] fstat(2) on pipes?
Date: Sun, 14 Aug 2016 20:27:11 -0400 (EDT) [thread overview]
Message-ID: <20160815002711.3F3C418C096@mercury.lcs.mit.edu> (raw)
> From: Warren Toomey
> I'm trying to find out what fstat(2) returns when the file descriptor
> is a pipe.
In V6, it returns information about the file (inode) used as a temporary
storage area for data which has been written into the pipe, but not yet read;
i.e. it's an un-named file with a length which varies between 0 and 4KB.
> xv6 has fstat() but returns an error if the file descriptor isn't
> associated with an i-node.
?? All pipe file descriptors should have an inode?
Noel
next reply other threads:[~2016-08-15 0:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 0:27 Noel Chiappa [this message]
2016-08-15 0:59 ` Warren Toomey
-- strict thread matches above, loose matches on Subject: below --
2016-08-15 17:47 Norman Wilson
2016-08-15 14:04 Noel Chiappa
2016-08-15 15:14 ` Random832
2016-08-15 16:56 ` Michael Kjörling
2016-08-15 0:11 Warren Toomey
2016-08-15 0:41 ` Dave Horsfall
2016-08-15 0:54 ` Warren Toomey
2016-08-15 17:53 ` Clem Cole
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160815002711.3F3C418C096@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).