Messages in this thread | | | Subject | Re: [RFC][PATCH] UDF filesystem uid fix | From | Pekka Enberg <> | Date | Wed, 15 Feb 2006 19:31:48 +0200 |
| |
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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |