linux-um archives
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Paul Wagland <paul@kungfoocoder.org>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Thoughts on HUMFS and metadata
Date: Mon, 19 Apr 2004 14:58:15 -0400	[thread overview]
Message-ID: <200404191858.i3JIwFsP024786@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Mon, 19 Apr 2004 09:52:49 +0200." <8D87591F-91D6-11D8-8B4A-000A95CD704C@kungfoocoder.org>

paul@kungfoocoder.org said:
> 1. Do files really need to exist in data if they are block, character
>  or sockets? Surely it is enough to just look at the metadata for
> these   files and create the appropriate dir entry in the UML. 

Permissions are stored with the real file.  This makes "metadata" a bit of a 
misnomer - I just moved the information that absolutely needed to move.

> 2. When COW humfs "partitions" are made, will it be possible to
> separately copy metadata and data? For instance, if I change only the
>  uid, gid and/or permissions, do I need to also create a new copy of
> the   data, or can I only update my local metadata and use the data
> from the   parent?

A suitable implementation could optimize the COWing of permissions and other
non-data.  I'm not sure how worth-while that would be.

> 3. When COW humfs "partitions" are made, how will files be deleted in
>  the second humfs? I would assume (but could easily be wrong ;-) )
> that   the easiest way to do COW is for every file access, first check
> your   humfs, if it does not exist, then check your parent humfs. If
> this is   done, then how do you delete a file? I can see that one easy
> option is   to introduce a "deleted" metadata node, that only contains
> the word   deleted, and would signify that this file does not exist in
> this COWed   copy.

That's the plan, more or less.

> 4. Since metadata is basically a copy of "permission data" does it
> also   make sense for humfs metadata to include things like
> capabilities and   ACL's? 

If they are stored in the filesystem, then it might make sense.

				Jeff



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  parent reply	other threads:[~2004-04-19 18:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19  7:52 [uml-devel] Thoughts on HUMFS and metadata Paul Wagland
2004-04-19  9:00 ` Henrik Nordstrom
2004-04-19  9:56   ` Henrik Nordstrom
2004-04-19 18:58 ` Jeff Dike [this message]
2004-04-19 18:42   ` Paul Wagland
2004-04-19 20:15     ` Jeff Dike
2004-04-19 19:56       ` Paul Wagland
2004-04-19 21:13         ` Paul Wagland
2004-04-20  0:27           ` Jeff Dike

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=200404191858.i3JIwFsP024786@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=paul@kungfoocoder.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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