From: "Marko Petrović" <petrovicmarko2006@gmail.com>
To: linux-um@lists.infradead.org
Cc: richard@nod.at, anton.ivanov@cambridgegreys.com,
johannes@sipsolutions.net,
"Marko Petrović" <petrovicmarko2006@gmail.com>
Subject: [PATCH 1/2] Document new xattrperm flag
Date: Fri, 14 Apr 2023 00:30:23 +0200 [thread overview]
Message-ID: <20230413223024.11513-2-petrovicmarko2006@gmail.com> (raw)
In-Reply-To: <20230413223024.11513-1-petrovicmarko2006@gmail.com>
Signed-off-by: Marko Petrović <petrovicmarko2006@gmail.com>
---
...to_v2.rst => user_mode_linux_howto_v3.rst} | 20 +++++++++----------
1 file changed, 9 insertions(+), 11 deletions(-)
rename Documentation/virt/uml/{user_mode_linux_howto_v2.rst => user_mode_linux_howto_v3.rst} (99%)
diff --git a/Documentation/virt/uml/user_mode_linux_howto_v2.rst b/Documentation/virt/uml/user_mode_linux_howto_v3.rst
similarity index 99%
rename from Documentation/virt/uml/user_mode_linux_howto_v2.rst
rename to Documentation/virt/uml/user_mode_linux_howto_v3.rst
index af2a97429692..709eef10dd7d 100644
--- a/Documentation/virt/uml/user_mode_linux_howto_v2.rst
+++ b/Documentation/virt/uml/user_mode_linux_howto_v3.rst
@@ -1007,23 +1007,21 @@ an existing root_fs file::
# mount root_fs uml_root_dir -o loop
-
-You need to change the filesystem type of ``/`` in ``etc/fstab`` to be
-'hostfs', so that line looks like this::
-
- /dev/ubd/0 / hostfs defaults 1 1
-
Then you need to chown to yourself all the files in that directory
-that are owned by root. This worked for me::
+that are owned by root so that the kernel can access them.
+This worked for me::
- # find . -uid 0 -exec chown jdike {} \;
+ # find uml_root_dir -uid 0 -not -type l -exec chown jdike {} \;
Next, make sure that your UML kernel has hostfs compiled in, not as a
-module. Then run UML with the boot device pointing at that directory::
+module. Then run UML with the appropriate kernel command line
+parameters::
- ubd0=/path/to/uml/root/directory
+ rootfstype=hostfs rw hostfs=uml_root_dir,xattrperm
-UML should then boot as it does normally.
+You should have extended attributes supported and enabled on
+your host filesystem since UML uses them to store correct file
+permissions.
Hostfs Caveats
--------------
--
2.39.2
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2023-04-13 22:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 22:30 Document new xattrperm flag Marko Petrović
2023-04-13 22:30 ` Marko Petrović [this message]
2023-04-14 7:17 ` [PATCH 1/2] " Johannes Berg
2023-04-13 22:30 ` [PATCH 2/2] hostfs: store permissions in extended attributes Marko Petrović
2023-04-14 2:33 ` [PATCH v2 " Marko Petrović
2023-04-14 7:40 ` Johannes Berg
2023-04-14 17:19 ` Marko Petrović
2023-04-18 8:26 ` Johannes Berg
2023-04-25 16:10 ` Marko Petrović
2023-04-14 10:54 ` Richard Weinberger
2023-04-14 17:52 ` Marko Petrović
2023-04-14 17:59 ` Richard Weinberger
2023-04-15 16:48 ` [PATCH v3 " Marko Petrović
2023-04-16 17:24 ` Marko Petrović
2023-04-18 8:31 ` Johannes Berg
2023-04-25 16:35 ` Marko Petrović
2023-04-25 17:11 ` Johannes Berg
2023-08-28 19:48 ` Richard Weinberger
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=20230413223024.11513-2-petrovicmarko2006@gmail.com \
--to=petrovicmarko2006@gmail.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=johannes@sipsolutions.net \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
/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