public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/8] FUSE improvements + VFS changes
Date: Tue, 25 Oct 2005 09:39:47 +0100	[thread overview]
Message-ID: <20051025083947.GN7992@ftp.linux.org.uk> (raw)
In-Reply-To: <E1EUIr7-0006zX-00@dorka.pomaz.szeredi.hu>

On Tue, Oct 25, 2005 at 09:04:21AM +0200, Miklos Szeredi wrote:
> > > > The limitations are:
> > > > 
> > > >   1) open("foo", O_CREAT | O_WRONLY, 0444) or similar won't work
> > > > 
> > > >   2) ftruncate on a file not having write permission (but file opened
> > > >      in write mode) will fail
> > > > 
> > > >   3) statfs() cannot return different values based on the path within
> > > >      a filesystem
> > > 
> > >     4) mass of a body cannot vary depending on the way it's turned.
> > > 
> > > Horrible limitations, all of them...
> > 
> > Troll.
> > 
> > We have solution for 1-3, what's your's for 4?
> 
> And in case you're wondering, 1-2 are mandated by SUS, and obscure
> programs like "cp" depend on 1) for example.  So it's not as if these
> limitations were all that fair.

(1) and (2) are real, no arguments here.  It's statfs one that is
bogus (and yes, I should've trimmed the quoted part better).

  reply	other threads:[~2005-10-25  8:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-24 16:45 [PATCH 0/8] FUSE improvements + VFS changes Miklos Szeredi
2005-10-25  4:27 ` Al Viro
2005-10-25  5:56   ` Miklos Szeredi
2005-10-25  7:04     ` Miklos Szeredi
2005-10-25  8:39       ` Al Viro [this message]
2005-10-25  8:55         ` Miklos Szeredi
2005-10-25  8:05     ` Al Viro

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=20051025083947.GN7992@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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