public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: markgw@sgi.com
Cc: Greg Banks <gnb@melbourne.sgi.com>, Timothy Shimmin <tes@sgi.com>,
	Richard Scobie <richard@sauce.co.nz>,
	xfs@oss.sgi.com
Subject: Re: Filestreams (and 64bit inodes)
Date: Thu, 12 Jun 2008 22:45:12 -0500	[thread overview]
Message-ID: <4851ED48.90103@sandeen.net> (raw)
In-Reply-To: <4851E774.2070401@sgi.com>

Mark Goodwin wrote:

> struct dirent has an embedded ino_t too, so for completeness we should also
> be looking for readdir(), readdir64(), getdirentries(), 
> getdirentries64(), etc.

*sigh*

>>> I'm going to see if I can't leverage Fedora to clean some of this up.
>>>
>>> -Eric
>>>
>> Good luck with that.
> 
> Yes good luck :)
> (and the plan for statically linked apps? ...)

I plan to encourage fedora to keep discouraging them ;)

-Eric

      parent reply	other threads:[~2008-06-13  3:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-07 23:11 Filestreams Richard Scobie
2008-06-09  3:31 ` Filestreams Eric Sandeen
2008-06-10  1:49   ` Filestreams Timothy Shimmin
2008-06-10  2:14     ` Filestreams Richard Scobie
2008-06-10 23:09     ` Filestreams (and 64bit inodes) Richard Scobie
2008-06-11  1:39       ` Timothy Shimmin
2008-06-11  2:47         ` Richard Scobie
2008-06-11  3:23         ` Eric Sandeen
2008-06-12 13:52           ` Eric Sandeen
2008-06-13  1:28             ` Greg Banks
2008-06-13  3:06               ` Eric Sandeen
2008-06-13  3:24                 ` Greg Banks
2008-06-13  3:20               ` Mark Goodwin
2008-06-13  3:40                 ` Greg Banks
2008-06-13  3:46                   ` Eric Sandeen
2008-06-13  3:57                     ` Greg Banks
2008-06-13  5:35                   ` Greg Banks
2008-06-13 13:28                     ` Eric Sandeen
2008-06-13  3:45                 ` Eric Sandeen [this message]

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=4851ED48.90103@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=gnb@melbourne.sgi.com \
    --cc=markgw@sgi.com \
    --cc=richard@sauce.co.nz \
    --cc=tes@sgi.com \
    --cc=xfs@oss.sgi.com \
    /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