From: Sam Johnston <samjie@gmail.com>
To: Rik van Riel <riel@redhat.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen and Firewalling
Date: Mon, 18 Apr 2005 01:49:30 +0100 [thread overview]
Message-ID: <eda77ff805041717498ac36b7@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0504171957100.13054@chimarrao.boston.redhat.com>
Thanks Rik,
I've just worked out why my recompiling failed before - needed to
specify ARCH=xen ala:
make ARCH=xen menuconfig
It would be good to see netfilter included by default in domU kernels
in future releases, unless there's a reasonable reason not to. I see
it was just added to dom0 recently by iap10@labyrinth.cl.cam.ac.uk:
ChangeSet@1.1703, 2005-01-29 22:20:09+00:00, iap10@labyrinth.cl.cam.ac.uk
Add iptables modules to the default xen0 kernel, and add example
configuration files for a NAT setup.
Sam
On 4/18/05, Rik van Riel <riel@redhat.com> wrote:
> On Mon, 18 Apr 2005, Sam Johnston wrote:
>
> > Is there a reason for this? Is simply doing a make menuconfig inside
> > linux-2.6.10-xenU and setting the requisite options sufficient?
>
> Yes, reconfiguring and recompiling is enough.
>
> --
> "Debugging is twice as hard as writing the code in the first place.
> Therefore, if you write the code as cleverly as possible, you are,
> by definition, not smart enough to debug it." - Brian W. Kernighan
>
next prev parent reply other threads:[~2005-04-18 0:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 23:30 Xen and Firewalling Sam Johnston
2005-04-17 23:57 ` Rik van Riel
2005-04-18 0:49 ` Sam Johnston [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-18 9:59 Ian Pratt
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=eda77ff805041717498ac36b7@mail.gmail.com \
--to=samjie@gmail.com \
--cc=riel@redhat.com \
--cc=xen-devel@lists.xensource.com \
/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.