From: Matt Zimmerman <mdz@debian.org>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] hostfs as root
Date: Thu, 4 Sep 2003 21:10:50 -0400 [thread overview]
Message-ID: <20030905011050.GD16552@alcor.net> (raw)
In-Reply-To: <26941.1062723303@marajade.sandelman.ottawa.on.ca>
On Thu, Sep 04, 2003 at 08:55:03PM -0400, Michael Richardson wrote:
> okay.. Makes sense. But, since they are mode 0, we can't open them as
> the user, which root inside could do. Is there some compromise that we can
> do until we have the permissions layer in place?
> Like, forcing u+r on the underlying file maybe?
The problem I ran into which led me to this bug was extracting tar archives.
When they contain read-only files, tar opens them for writing with read-only
permissions. Since UML was creating the file and then, subsequently,
attempting to open it for writing, the second open failed.
I think that in general, having the permissions silently changed would be
unwise, though I admit that u-r permissions are weird at best. It would
seem better to have mount fixed to stop doing this strange thing, and
eventually to emulate full permission control in hostfs.
--
- 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 1:10 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 [this message]
2003-09-05 13:43 ` Michael Richardson
2003-09-05 14:01 ` Matt Zimmerman
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=20030905011050.GD16552@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