From: Peter Staubach <staubach@redhat.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: drepper@redhat.com, viro@ZenIV.linux.org.uk,
bharata@linux.vnet.ibm.com, libc-alpha@sourceware.org,
jblunck@suse.de, ezk@cs.sunysb.edu, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, hch@lst.de, cmm@us.ibm.com,
haveblue@us.ibm.com
Subject: Re: [RFC] Union mount readdir support in glibc
Date: Fri, 14 Mar 2008 13:53:51 -0400 [thread overview]
Message-ID: <47DABBAF.4040005@redhat.com> (raw)
In-Reply-To: <E1Ja5Tf-0003Op-Fi@pomaz-ex.szeredi.hu>
Miklos Szeredi wrote:
>>> Actually, do we really need it other than to 0 and to current position
>>> (i.e. full rewind and a no-op)?
>>>
>> Ever heard of the little function "telldir"?
>>
>
> Actually, telldir/seekdir is already broken for some filesystems (NFS
> comes to mind). POSIX was really crazy to require a working seekdir
> implementation, and userspace should quickly start _not_ using it.
>
>
What makes you think that telldir/seekdir don't work for NFS? The over the
wire protocols clearly take values which could be retrieved and stored via
those interfaces.
ps
> The more new filesystems it doesn't work, the better, IMHO.
>
> Miklos
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-03-14 17:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 5:55 [RFC] Union mount readdir support in glibc Bharata B Rao
2008-03-11 8:09 ` Roland McGrath
2008-03-11 12:49 ` Bharata B Rao
2008-03-12 4:28 ` Bharata B Rao
2008-03-14 3:53 ` Ulrich Drepper
2008-03-14 5:39 ` Al Viro
2008-03-14 7:13 ` Ulrich Drepper
2008-03-14 8:41 ` Miklos Szeredi
2008-03-14 17:53 ` Peter Staubach [this message]
2008-03-14 20:51 ` Miklos Szeredi
2008-03-14 20:58 ` Trond Myklebust
2008-03-14 15:07 ` Jan Blunck
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=47DABBAF.4040005@redhat.com \
--to=staubach@redhat.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=drepper@redhat.com \
--cc=ezk@cs.sunysb.edu \
--cc=haveblue@us.ibm.com \
--cc=hch@lst.de \
--cc=jblunck@suse.de \
--cc=libc-alpha@sourceware.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@ZenIV.linux.org.uk \
/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