From: Cameron Patrick <cameron@patrick.wattle.id.au>
To: Trent Lloyd <lathiat@bur.st>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] hostfs / current->fsuid
Date: Tue, 22 Jun 2004 21:50:45 +0800 [thread overview]
Message-ID: <20040622135044.GG25291@patrick.wattle.id.au> (raw)
In-Reply-To: <20040621034434.GC2735@thump.bur.st>
[-- Attachment #1: Type: text/plain, Size: 442 bytes --]
Hi Trent,
Since no-one else has answered yet, I'll have a shot...
On Mon, Jun 21, 2004 at 11:44:35AM +0800, Trent Lloyd wrote:
| I was looking into trying to modify hostfs so if UML ran as root it
| would keep the same permissions
I've no idea about modifying hostfs, but have you looked into using
NFS instead? Sure, it's a security nightmare, but it can't be worse
than running UML as root! Performance might suck though.
Cameron.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-22 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 3:44 [uml-devel] hostfs / current->fsuid Trent Lloyd
2004-06-22 13:50 ` Cameron Patrick [this message]
2004-06-22 18:35 ` BlaisorBlade
2004-06-23 0:48 ` Trent Lloyd
2004-06-23 4:09 ` [uml-devel] " Sven Köhler
2004-06-23 6:02 ` Trent Lloyd
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=20040622135044.GG25291@patrick.wattle.id.au \
--to=cameron@patrick.wattle.id.au \
--cc=lathiat@bur.st \
--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