From: Mohamed Eldesoky <eldesoky.lists@gmail.com>
To: "Gary W. Smith" <gary@primeexalia.com>,
netfilter <netfilter@lists.netfilter.org>
Subject: Re: dig doesn't work
Date: Mon, 14 Mar 2005 11:26:16 +0200 [thread overview]
Message-ID: <1403218a050314012612cfb19e@mail.gmail.com> (raw)
In-Reply-To: <27594E8BA9D5CA458F5EF87D88B6B48F0199C5@pxtvjoexd01.pxt.primeexalia.com>
umm
This should be it.
But it is lots of headache
Gonna try
On Sun, 13 Mar 2005 09:20:13 -0800, Gary W. Smith <gary@primeexalia.com> wrote:
> Did you apply all of the RH specific patches as well or did you use the
> vanilla kernel. I had exactly that problem where there are several
> things compiled to use RH's modified glibc. To get around that you MUST
> apply all of the patches in the same order that they do in the
> SRPMS/SPECS file.
>
> RHES3 is a hybrid kernel (which I found out when everything segfaulted)
> that uses many of the 2.6 networking features. As a result it's heavily
> incompatible from vanilla sources.
>
> My suggestion is that you make a chance to the vanilla source, diff it,
> create a patch and append it to the RH kernel Spec file. That works for
> most of the stuff that I have done.
>
> Hope that helps.
>
> Gary
>
> > -----Original Message-----
> > From: netfilter-bounces@lists.netfilter.org [mailto:netfilter-
> > bounces@lists.netfilter.org] On Behalf Of Mohamed Eldesoky
> > Sent: Sunday, March 13, 2005 5:23 AM
> > To: netfilter; EBTables Users
> > Subject: dig doesn't work
> >
> > I use RHEL3AS
> > Patched my system for ebtables, using 2.4 kernels.
> > Now the dig command gives segmentation fault
> > Did it occure to anyone ??
> > --
> > Mohamed Eldesoky
> > www.eldesoky.net
> > RHCE
>
>
--
Mohamed Eldesoky
www.eldesoky.net
RHCE
next prev parent reply other threads:[~2005-03-14 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 17:20 dig doesn't work Gary W. Smith
2005-03-14 9:26 ` Mohamed Eldesoky [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-13 13:22 Mohamed Eldesoky
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=1403218a050314012612cfb19e@mail.gmail.com \
--to=eldesoky.lists@gmail.com \
--cc=gary@primeexalia.com \
--cc=netfilter@lists.netfilter.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