From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] hostfs as root
Date: Wed, 17 Sep 2003 18:43:49 +0200 [thread overview]
Message-ID: <200309171843.49052.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <26716.1062787141@marajade.sandelman.ottawa.on.ca>
Alle 20:39, venerdì 5 settembre 2003, Michael Richardson ha scritto:
> >> If you have a simple /sbin/mount that you can recommend that solves
> >> my problem, I will consider using it.
>
> Matt> The fact that you said it broke _potato_'s mount, specifically,
> led Matt> me to believe that newer versions did not do this (they do).
>
> Ah, so your fix basically breaks all distros? I have no idea.
> Then clearly it needs to be fixed in the kernel, don't you think?
>
> Matt> However, the fix to mount is trivial, so you can easily create an
> Matt> /sbin/mount which should work.
>
> I think that removing your patch is a better idea. Find another way to
> make tar happy.
>
> Booting the system is pretty important.
I think that since anyway there is not a permission layer, you shouldn't boot
off an hostfs filesystem. Mount with -o loop a new file, then copy all the
filesystem content. Or maybe(but ask to other developers/check docs) if you
have a whole partition, say ubd0=/dev/<your part> to UML. With hostfs,
anyway, if you don't run the guest with root privileges, files created by
root will be owned by the user running the Uml(i.e. it can happen that
everything works, especially if you login in the Uml only with a uid=<uid of
Uml on the host>, but not everything will work), while root won't have access
to certain files(you can avoid also this, by not putting in that hierarchy
any file of root from the host).
--
cat <<EOSIGN
Paolo Giarrusso, aka Blaisorblade
Linux Kernel 2.4.21/2.6.0-test on an i686; Linux registered user n. 292729
EOSIGN
-------------------------------------------------------
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-17 18:14 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
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 [this message]
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=200309171843.49052.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=mcr@sandelman.ottawa.on.ca \
--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