From: Matt Zimmerman <mdz@debian.org>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] hostfs as root
Date: Fri, 5 Sep 2003 10:01:19 -0400 [thread overview]
Message-ID: <20030905140119.GM11825@alcor.net> (raw)
In-Reply-To: <11307.1062769436@marajade.sandelman.ottawa.on.ca>
On Fri, Sep 05, 2003 at 09:43:56AM -0400, Michael Richardson wrote:
>
> >>>>> "Matt" == Matt Zimmerman <mdz@debian.org> writes:
> Matt> The problem I ran into which led me to this bug was extracting tar
> Matt> archives.
> Matt> When they contain read-only files, tar opens them for writing with
> Matt> read-only
> Matt> permissions. Since UML was creating the file and then, subsequently,
> Matt> attempting to open it for writing, the second open failed.
>
> How is this the correct thing to do for the UML then?
> What bug did you uncover?
I described it above. tar was completely unable to extract files with
read-only permissions.
> Matt> I think that in general, having the permissions silently changed
> Matt> would be
> Matt> unwise, though I admit that u-r permissions are weird at best. It
>
> Well, if the opener is root, you get to ignore the permissions. That means
> that something has to break.
>
> I propose:
> stat(), save permissions
> chmod(u+rw) (as appropriate for the open)
> open()
> chmod(oldperms)
Sounds like a recipe for lots of race conditions.
> Matt> would
> Matt> seem better to have mount fixed to stop doing this strange thing, and
> Matt> eventually to emulate full permission control in hostfs.
>
> Well, leaving us in a lurch is decidely not friendly.
> Your fix has broken debian potato's mount. Being able to run other distros,
> versions, etc. inside of UML is one of the major features of UML.
OK, so mount is already fixed. So the only problem is that you can't use an
old, mildly buggy version of mount with root-hostfs as a non-root user on
the host. I'd rather be able to extract tar files than have that scenario.
You must have already worked around some other problems in order to run
potato in this configuration; it wouldn't work out of the box with a 2.4
kernel. How are you managing device nodes? Loading any kernel modules?
--
- mdz
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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:[~2003-09-05 14:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0309020854560.26729-100000@filer.marasystems.com>
2003-09-02 16:28 ` [uml-devel] hostfs as root Michael Richardson
2003-09-03 9:32 ` Henrik Nordstrom
2003-09-03 15:47 ` Matt Zimmerman
2003-09-03 18:22 ` Michael Richardson
2003-09-03 18:55 ` Henrik Nordstrom
2003-09-03 19:16 ` Matt Zimmerman
2003-09-05 0:55 ` Michael Richardson
2003-09-05 1:10 ` Matt Zimmerman
2003-09-05 13:43 ` Michael Richardson
2003-09-05 14:01 ` Matt Zimmerman [this message]
2003-09-05 15:50 ` Michael Richardson
2003-09-05 16:06 ` Adam Heath
2003-09-05 16:28 ` Michael Richardson
2003-09-05 16:44 ` Adam Heath
2003-09-05 16:13 ` Matt Zimmerman
2003-09-05 17:37 ` Michael Richardson
2003-09-05 18:02 ` Matt Zimmerman
2003-09-05 18:39 ` Michael Richardson
2003-09-05 18:49 ` Matt Zimmerman
2003-09-17 16:43 ` BlaisorBlade
2003-09-05 15:14 stian
2003-09-05 17:58 ` Michael Richardson
2003-09-05 18:19 ` Matt Zimmerman
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=20030905140119.GM11825@alcor.net \
--to=mdz@debian.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