From: Jeff Dike <jdike@addtoit.com>
To: Henrik Nordstrom <uml@henrik.marasystems.com>
Cc: user-mode-linux-user@lists.sourceforge.net,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] A quick humfs HOWTO
Date: Thu, 08 Apr 2004 07:34:35 -0400 [thread overview]
Message-ID: <200404081134.i38BYZB6001887@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Thu, 08 Apr 2004 10:35:48 +0200." <Pine.LNX.4.44.0404081027360.7910-100000@filer.marasystems.com>
uml@henrik.marasystems.com said:
> Can data be a symlink on the host?
Yup.
> I would suggest adding an option to optionally allow specifying the
> path to data, this to allow humfs permission shadows to easily be
> created of existing trees. If data can be a symlink this option can be
> managed in humfsify.
With humfsify currently, you set up the data tree, and it takes it from there.
So you can make data a symlink, and it will just work.
At some point, I'll have humsify create the data tree as well, and then it
will be possible to tell it to make it a symlink.
> Also, what happens if there is a mismatches between metadata and data
> content?
Bad things happen. The filesystem still needs to be hardened against
mismatches.
> I wouldsuggest adding a read-only flag, preventing UML from mounting
> the directory read-write.
Good idea.
> How is this information used by humfsify? Can these be made optional
> (then use current uid/gid, or don't care)
Don't care isn't a possibility. humfsify chowns everything in the data tree
to this uid and gid. UML needs write access to everything if root is to
behave as root.
Possible it could run as a normal user, but my expectation is that people
will loop-mount ubd volumes as their data sources, and those are filled with
root-owned files. The only place that makes sense is when you already have
a tree which is completely owned by the UML user.
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
next prev parent reply other threads:[~2004-04-08 11:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 2:07 [uml-devel] A quick humfs HOWTO Jeff Dike
2004-04-08 6:25 ` Nuno Silva
2004-04-08 8:43 ` Henrik Nordstrom
2004-04-09 18:49 ` BlaisorBlade
2004-04-12 15:06 ` Michael Richardson
2004-04-13 6:51 ` Henrik Nordstrom
2004-04-12 15:05 ` Michael Richardson
2004-04-08 7:58 ` [uml-devel] Re: [uml-user] " Rus Foster
2004-04-08 11:23 ` Jeff Dike
2004-04-08 8:35 ` [uml-devel] " Henrik Nordstrom
2004-04-08 11:34 ` Jeff Dike [this message]
2004-04-08 12:09 ` Henrik Nordstrom
2004-04-08 9:54 ` Nick Craig-Wood
2004-04-08 10:07 ` Henrik Nordstrom
2004-04-08 11:41 ` Jeff Dike
2004-04-08 10:26 ` stian
2004-04-08 11:41 ` Jeff Dike
2004-04-08 12:52 ` Jeff Dike
2004-04-08 12:03 ` [uml-devel] " Gerd Knorr
2004-04-08 12:49 ` Jeff Dike
2004-04-08 13:01 ` Gerd Knorr
2004-04-08 13:49 ` Robin Green
2004-04-12 15:11 ` Michael Richardson
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=200404081134.i38BYZB6001887@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=uml@henrik.marasystems.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@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