From: Anton Ivanov <anton.ivanov@cambridgegreys.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-um@lists.infradead.org
Subject: Re: UML HowTo rewrite
Date: Wed, 22 Apr 2020 14:53:49 +0100 [thread overview]
Message-ID: <6fd55233-8fd0-4ec3-7481-b303f79bda8d@cambridgegreys.com> (raw)
In-Reply-To: <28e23bdd281be6368ed75883ca73ea57de4faaad.camel@sipsolutions.net>
On 22/04/2020 14:47, Johannes Berg wrote:
> On Wed, 2020-04-22 at 14:30 +0100, Anton Ivanov wrote:
>> The initial content is more or less in place.
> Great. I actually saw it (you posted a link to a PR before) and pointed
> a colleague who was interested in what I'm doing with all my time-travel
> simulation and UML to it. I told him feedback would surely be welcome :)
>
>> Comments and PRs to change/add things are welcome.
>>
>> https://github.com/kot-begemot-uk/uml-howto-v2
> Are you going to submit it to the Documentation/ folder in the kernel?
Yes. A couple of revisions, reviews and PRs first though :)
>
> I'd much prefer to contribute changes to the kernel after it lands
> there, otherwise I'd have to jump through (legal) approval hoops ...
Easier to deal with the early "high flux" change rate when it is out of
tree.
>
>
> Btw, one thing that I think is useful to document is how to run
> *without* an image - you don't need a full OS inside. Most of my use
> cases just run something like
>
> ./linux mem=256M root=none hostfs=/ rootfstype=hostfs rootflags=/ init=/some/script.sh
hostfs and hostfs use as root is in the Advanced section.
As I do not use it, can you review it (it is mostly copied from the old
howto).
IMHO hostfs can be significantly improved by using inotify. It has been
on my TODO list for a while now.
>
> Would be a worthwhile addition, I think?
>
> Anyway, like I said above, I'm happy to contribute to this but would
> prefer if it's in the kernel first.
I have a little bit more content to add to the Developing section, but as I said - I am happy to do it after we add it to the tree if everyone thinks that this is better.
>
> johannes
>
>
> _______________________________________________
> linux-um mailing list
> linux-um@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-um
>
--
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661
https://www.cambridgegreys.com/
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
prev parent reply other threads:[~2020-04-22 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 8:01 UML HowTo rewrite Anton Ivanov
2020-04-20 8:30 ` Johannes Berg
2020-04-20 8:33 ` Anton Ivanov
2020-04-22 13:30 ` Anton Ivanov
2020-04-22 13:47 ` Johannes Berg
2020-04-22 13:53 ` Anton Ivanov [this message]
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=6fd55233-8fd0-4ec3-7481-b303f79bda8d@cambridgegreys.com \
--to=anton.ivanov@cambridgegreys.com \
--cc=johannes@sipsolutions.net \
--cc=linux-um@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.