From: Manish Kathuria <manish@tuxspace.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Please help in choosing the right patches
Date: Wed, 08 Feb 2006 07:22:39 +0000 [thread overview]
Message-ID: <43E9996F.9050508@tuxspace.com> (raw)
In-Reply-To: <BAY20-DAV57865DCAF56318C38727E97010@phx.gbl>
Sandeep Agarwal wrote:
> Manish Kathuria wrote:
> >
> >>Sandeep Agarwal wrote:
> >>
> >>
> >> I have gone through http://www.ssi.bg/~ja/nano.txt AND further
> >> http://www.ssi.bg/~ja/ & got confused in choosing the right patch.
> >> Please suggest if I will choose Jumbo Patch patch-2.4.20-ja1.diff , is
> >> any other patches also required after this? If yes, is there
> >> any sequence in applying these patches?
> >>
> >
> >For your purpose, you need to choose one of the patches at
> >http://www.ssi.bg/~ja/#routes depending on your kernel. You dont need
> >the Jumbo patch for load balancing and failover. The "routes" patch
> >should suffice.
> >
> >--
> >Manish Kathuria
> >http://www.tuxspace.com/
> Thanks Manish.
> I have download routes-2.4.20-9.diff as I have RHEL3.0 (Kernel
> 2.4.21-9EL) & apply the same.
> But the output as follows. Is this normal or any problem?
>
> # patch -p1 < routes-2.4.20-9.diff
> Hunk #1 FAILED at 162.
> Hunk #2 succeeded at 180 with fuzz 1 (offset 5 lines).
> 1 out of 3 hunks FAILED -- saving rejects to file
> linux/include/net/ip_fib.h.rej
> patching file linux/include/net/route.h
> Hunk #1 FAILED at 49.
> Hunk #2 succeeded at 120 with fuzz 2 (offset -8 lines).
> Hunk #3 FAILED at 140.
> 2 out of 3 hunks FAILED -- saving rejects to file
> linux/include/net/route.h.rej
> patching file linux/net/ipv4/arp.c
> patching file linux/net/ipv4/fib_frontend.c
> Hunk #3 succeeded at 212 with fuzz 2.
> Hunk #4 FAILED at 222.
> Hunk #5 FAILED at 244.
The Red Hat kernels are not just plain vanilla kernels. They already
have a number of patches applied by Red Hat and it is likely that the
patch being applied by you is conflicting by one of those. You can
either try some other kernel version or download a plain vanilla kernel
from http://www.kernel.org/ and apply the routes patch on it.
--
Manish
http://www.tuxspace.com/
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-02-08 7:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 5:42 [LARTC] Please help in choosing the right patches Sandeep Agarwal
2006-02-07 18:58 ` Manish Kathuria
2006-02-08 6:51 ` Sandeep Agarwal
2006-02-08 7:22 ` Manish Kathuria [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=43E9996F.9050508@tuxspace.com \
--to=manish@tuxspace.com \
--cc=lartc@vger.kernel.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.