From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Peter Maydell <peter.maydell@linaro.org>,
Programmingkid <programmingkidx@gmail.com>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Networking documentation for a Mac OS X guest
Date: Fri, 4 Dec 2015 11:36:38 +0000 [thread overview]
Message-ID: <56617AC6.10307@ilande.co.uk> (raw)
In-Reply-To: <CAFEAcA8T2+_fZV+UM5h7OkpywOgNJ3vSP=9KnvM6w=qNDaZ8Ww@mail.gmail.com>
On 04/12/15 00:02, Peter Maydell wrote:
> On 3 December 2015 at 23:24, Programmingkid <programmingkidx@gmail.com> wrote:
>> I would like to make a little tutorial on how to make networking
>> work for a Mac OS X guest. Where would you suggest I put such
>> documentation? The qemu-doc file is what I was thinking about using.
>
> Hmm. I think for "doing stuff for a particular guest" type tutorials
> we've got a few links and pages on the wiki; perhaps an entry in
> http://wiki.qemu.org/Manual under "for users that target for a specific
> platform" for OSX guests in general? Then you could have a page giving
> suggestions for the command line in general as well as networking
> in particular. (The existing links in that subsection are all
> external but there's no reason we couldn't have an internal-to-the-wiki
> link there too.)
Is it worth setting up per-arch homepages on the wiki? This is something
I've thought about recently since most of the information out on the
internet regarding QEMU's ability to run various systems is badly out of
date with regard to SPARC/PPC. Even better if they could go in the left
hand list with easy to remember URLs like /SPARC, /PPC, /ARM etc...
ATB,
Mark.
next prev parent reply other threads:[~2015-12-04 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 23:24 [Qemu-devel] Networking documentation for a Mac OS X guest Programmingkid
2015-12-04 0:02 ` Peter Maydell
2015-12-04 11:36 ` Mark Cave-Ayland [this message]
2015-12-04 11:46 ` Peter Maydell
2015-12-05 14:10 ` Mark Cave-Ayland
2015-12-05 16:20 ` Programmingkid
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=56617AC6.10307@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.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.