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 22:28:02 +0200 [thread overview]
Message-ID: <1140035282.3926.4.camel@localhost> (raw)
In-Reply-To: <43F37773.5030203@cfl.rr.com>
On Wed, 2006-02-15 at 13:48 -0500, Phillip Susi wrote:
> True, that would work. It would require the addition of another mount
> option though, so I wonder, is that really needed? What problem with
> the current patch would this solve? Is there really a need to save real
> ids to the disk with the current uid option and no force? Keep in mind
> that udf is meant for removable media where the uids aren't going to
> make any sense in another system.
Yeah, but even for removable media proper uid/gid makes sense. For
instance, if I am sharing an usb stick with someone else on the same
computer, uid/gid is useful. Anyway, I prefer that force thing and if
everyone else disagrees with me, now would be a good time to say so.
Pekka
next prev parent reply other threads:[~2006-02-15 20:28 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
2006-02-15 18:48 ` Phillip Susi
2006-02-15 20:28 ` Pekka Enberg [this message]
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=1140035282.3926.4.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.