From: BlaisorBlade <blaisorblade_spam@yahoo.it> (by way of BlaisorBlade <blaisorblade_spam@yahoo.it>)
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] filemap feature 2.4.22-5um
Date: Sat, 18 Oct 2003 18:34:50 +0200 [thread overview]
Message-ID: <200310181834.50216.blaisorblade_spam@yahoo.it> (raw)
Alle 16:08, martedì 14 ottobre 2003, Steve Schmidtke ha scritto:
> Doug Dumitru wrote:
> >A couple of questions. I noticed that you are not mapping /proc/mm.
>
> [...]
>
> >This looks like one per virtual process (minus threads). Am I reading
> > this right.
>
> yes. The discussion for a previous patch considered a "mm" table to hold a
> pool of /proc/mm files to handle one fd per process.
> [....]
Nooo! Don't make your like hard!
Search for this thread "[uml-user] chroot'ing an UML - /proc/mm" on
http://marc.theaimsgroup.com/ !
You can use mount --bind inside the host to make /proc/mm visible to UML.
I.e. it should be something such(NOT TRIED!):
cd <chroot path>
mkdir proc
touch proc/mm #You must create the mount point. In this case it's a file.
(as root)mount --bind /proc/mm proc/mm
<start Uml binary with "# chroot . linux ...." >
About the ugliness, it's only a userspace syntax matter. This is the v2 of
the umlwrap syntax. Instead of this:
umlwrap -bind=21,/dev/shm/mconsole1 -dir=/home/uml -- \
/bin/linux mem=48M uml_dir=/uml/ umid=um1 filemap=22,/uml/um1/pid \
22</dev/shm/pid filemap=21,/uml/um1/mconsole
We can have this:
umlwrap -dir=/home/uml -bind=/dev/shm/mconsole1,/uml/um1/mconsole \
-map=r,/dev/shm/pid,/uml/um1/pid-- /bin/linux mem=48M uml_dir=/uml/
umid=um1
umlwrap will then setup the needed "filemap" options, at the end of the
command line. However, does UML(unlike vanilla kernel) supports so long(>512
char) command lines in the internal kernel part, (in the userspace part it's
granted)? If not, we can use a patch out there that is already used by
Knoppix.
By the way, if umlwrap is smart enough, maybe it can guess whether to use
-map, -bind or -connect by itself(at least partially, i.e. stating the file).
However this isn't a problem here. And for the length of settings, there is
scripting!
Bye
--
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 sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise
Linux in the Boardroom; in the Front Office; & in the Server Room
http://www.enterpriselinuxforum.com
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2003-10-18 16:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-18 16:34 BlaisorBlade [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-18 17:15 [uml-devel] filemap feature 2.4.22-5um Steve Schmidtke
2003-10-18 1:31 Steve Schmidtke
2003-10-18 12:37 ` Henrik Nordstrom
2003-10-18 21:57 ` Goetz Bock
2003-10-18 22:29 ` Henrik Nordstrom
2003-10-18 14:27 ` Adam Heath
2003-10-14 22:58 Steve Schmidtke
2003-10-15 8:43 ` azu
2003-10-15 20:13 ` Jeff Dike
2003-10-14 14:08 Steve Schmidtke
2003-10-14 3:54 Steve Schmidtke
2003-10-13 5:15 ` Jeff Dike
2003-10-14 6:19 ` Doug Dumitru
2003-10-17 17:14 ` Adam Heath
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=200310181834.50216.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--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