From: Ludwig Nussel <ludwig.nussel@suse.de>
To: linux-fsdevel@vger.kernel.org
Cc: Andreas Dilger <adilger@sun.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] implement uid mount option for ext2
Date: Tue, 28 Jul 2009 09:50:02 +0200 [thread overview]
Message-ID: <200907280950.04099.ludwig.nussel@suse.de> (raw)
In-Reply-To: <20090727191453.GQ4231@webber.adilger.int>
Andreas Dilger wrote:
> [...]
> A more "obvious" solution would be to just have the filesystem mounted
> with this option to make ALL files appear to be owned by the UID specified
> to the "uid=${localuid}", which would at least more closely match the
> behaviour of the fat/vfat filesystems with the uid= option.
Well, I don't mind. The change to have it that way is trivial.
> New files
> could be created using the local UID with no more effort than creating
> them with uid=0, but there would be less surprise on another system if
> files don't magically appear as owned by root.
Sure, the disadvantage is that by using the local id the fs might
aggregate many different uids over time which looks weird on a
legacy system though.
> My further suggestion was that if it is possible to optionally specify
> the remote UID then at least one side does not have to have this patch
> in order to mount and use the filesystem. Hence, my suggestion to have
> "uid={localuid}[={diskuid}]". The [={diskuid}] part could be optional,
> and doesn't add any significant complication to the patch, AFAICS.
> Initialize the diskuid = localuid, and if the additional diskuid is given
> use that instead, for all inodes written to the disk.
Hmm, ok. Could be used to have all files root owned too.
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
next prev parent reply other threads:[~2009-07-28 7:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 11:36 [PATCH 0/2] implement uid mount option for ext2 and ext3 Ludwig Nussel
2009-07-23 11:36 ` [PATCH 1/2] implement uid mount option for ext2 Ludwig Nussel
2009-07-23 11:36 ` [PATCH 2/2] implement uid mount option for ext3 Ludwig Nussel
2009-07-23 14:37 ` [PATCH 0/2] implement uid mount option for ext2 and ext3 Randy Dunlap
2009-07-23 21:23 ` Valdis.Kletnieks
2009-07-24 10:23 ` Ludwig Nussel
2009-07-30 9:07 ` Pavel Machek
2009-07-24 10:30 ` [PATCH 0/2] implement uid mount option for ext2 and ext3, try 2 Ludwig Nussel
2009-07-24 10:30 ` [PATCH 1/2] implement uid mount option for ext2 Ludwig Nussel
2009-07-24 10:30 ` [PATCH 2/2] implement uid mount option for ext3 Ludwig Nussel
2009-07-24 16:52 ` [PATCH 1/2] implement uid mount option for ext2 Andreas Dilger
2009-07-24 18:58 ` John Stoffel
2009-07-24 23:16 ` Jamie Lokier
2009-07-27 14:56 ` John Stoffel
2009-07-25 15:44 ` Ludwig Nussel
2009-07-27 19:14 ` Andreas Dilger
2009-07-28 7:50 ` Ludwig Nussel [this message]
2009-07-28 11:01 ` [PATCH 0/2] implement uid mount option for ext2 and ext3, try 3 Ludwig Nussel
2009-07-28 11:01 ` [PATCH 1/2] implement uid and gid mount options for ext2 Ludwig Nussel
2009-07-28 11:01 ` [PATCH 2/2] implement uid and gid mount options for ext3 Ludwig Nussel
2009-07-28 18:11 ` [PATCH 0/2] implement uid mount option for ext2 and ext3, try 3 Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
2009-04-08 13:21 [RFC] [PATCH 0/2] implement uid mount option for ext2 and ext3 Ludwig Nussel
2009-04-08 13:21 ` [PATCH 1/2] implement uid mount option for ext2 Ludwig Nussel
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=200907280950.04099.ludwig.nussel@suse.de \
--to=ludwig.nussel@suse.de \
--cc=adilger@sun.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).