From: "John R. Hogerhuis" <jhoger@pobox.com>
To: Mike Tremoulet <coffeemike@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] pcap-based networking?
Date: Thu, 26 Aug 2004 23:28:31 -0700 [thread overview]
Message-ID: <1093588111.32369.950.camel@aragorn> (raw)
In-Reply-To: <5640213304082623084cf26dd3@mail.gmail.com>
On Thu, 2004-08-26 at 23:08, Mike Tremoulet wrote:
> So, having said all that, is there a quickstart guide to understanding
> the structure/design of the current qemu code? I'm going to have to
> learn the guts of pcap programming, remember how c actually works, and
> basically come up to speed on a lot of things.
>
No. There's lots of code. Some documentation. But 95% of the code (and
the documentation) doesn't have anything to do with networking. Just
focus on the sections that matter to you. As you come up against
problems, get your copy of K&R, ask someone on IRC, or if it's QEMU
specific ask here on the list.
The pcap stuff is just a library/API. Any API takes some time to learn,
but at least you have the source if the API documentation is
problematic.
Anyway half the reason for working with Free Software is that when I
invest time to learn something, I can actually take that knowledge with
me and apply it anywhere I go without worrying about violating someone's
trade secrets or proprietary intellectual property. At the risk of being
patronizing, my advice if you want to be a good FOSS programmer is never
be afraid of learning anything. Don't plan to think about starting to do
something... just jump in and get it done.
-- John.
next prev parent reply other threads:[~2004-08-27 6:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 16:42 [Qemu-devel] pcap-based networking? Mike Tremoulet
2004-08-26 17:15 ` John R. Hogerhuis
2004-08-26 17:19 ` Mike Tremoulet
2004-08-26 17:48 ` John R. Hogerhuis
2004-08-27 6:08 ` Mike Tremoulet
2004-08-27 6:28 ` John R. Hogerhuis [this message]
2004-08-27 6:32 ` Mike Tremoulet
2004-08-26 17:33 ` Jim C. Brown
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=1093588111.32369.950.camel@aragorn \
--to=jhoger@pobox.com \
--cc=coffeemike@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).