From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: Peter Osterlund <petero2@telia.com>,
linux-kernel@vger.kernel.org, bfennema@falcon.csc.calpoly.edu,
Christoph Hellwig <hch@lst.de>, Al Viro <viro@ftp.linux.org.uk>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC][PATCH] UDF filesystem uid fix
Date: Wed, 15 Feb 2006 19:31:48 +0200 [thread overview]
Message-ID: <1140024709.24898.7.camel@localhost> (raw)
In-Reply-To: <43F34ED5.8020306@cfl.rr.com>
On Wed, 2006-02-15 at 10:55 -0500, Phillip Susi wrote:
> Maybe I should amend the patch to work like this:
>
> uid/gid : specify default id when -1 is on disk
> uid/gid = force : ignore ids on disk
> uid/gid = [no]save : do [not] save actual id to disk ( save -1 instead )
>
> Possibly with nosave being the default. Would this be more acceptable?
Yeah, sounds much better to me. However, I am wondering if we can
actually drop the nosave/save cases completely. Wouldn't we get the same
semantics by letting uid/gid specify the default id and make the ignore
case look like we're always reading -1 from disk, and never writing out
any ids? So as a desktop user, you mount with "uid=", "gid=", and
"force" passed as mount option and it works as expected.
Pekka
next prev parent reply other threads:[~2006-02-15 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 18:17 [RFC][PATCH] UDF filesystem uid fix Peter Osterlund
2006-02-13 9:49 ` Pekka Enberg
2006-02-13 16:51 ` Phillip Susi
2006-02-14 7:28 ` Pekka J Enberg
2006-02-14 11:36 ` Sergey Vlasov
2006-02-14 15:54 ` Phillip Susi
2006-02-15 7:31 ` Pekka Enberg
2006-02-15 15:55 ` Phillip Susi
2006-02-15 17:31 ` Pekka Enberg [this message]
2006-02-15 18:48 ` Phillip Susi
2006-02-15 20:28 ` Pekka Enberg
2006-03-04 23:19 ` Phillip Susi
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=1140024709.24898.7.camel@localhost \
--to=penberg@cs.helsinki.fi \
--cc=akpm@osdl.org \
--cc=bfennema@falcon.csc.calpoly.edu \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
--cc=psusi@cfl.rr.com \
--cc=viro@ftp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.