public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Dax Kelson <dax@gurulabs.com>
Cc: "Jeff V. Merkey" <jmerkey@timpanogas.org>, linux-kernel@vger.kernel.org
Subject: Re: /net/ip_vs.h in stock kernels
Date: Sun, 12 Nov 2000 23:38:19 -0700	[thread overview]
Message-ID: <20001112233819.C15243@vger.timpanogas.org> (raw)
In-Reply-To: <3A0C91C7.D5530CFF@timpanogas.org> <Pine.SOL.4.21.0011112251070.15229-100000@ultra1.inconnect.com>
In-Reply-To: <Pine.SOL.4.21.0011112251070.15229-100000@ultra1.inconnect.com>; from dax@gurulabs.com on Sat, Nov 11, 2000 at 10:52:38PM -0700

On Sat, Nov 11, 2000 at 10:52:38PM -0700, Dax Kelson wrote:
> Jeff V. Merkey said once upon a time (Fri, 10 Nov 2000):
> 
> > 
> > I noticed that the ip_vs.h include is not in the main kernel tree or ip
> > virtual switch support while I was attempting to buid the pirahnna web
> > server.  Is this module a patch located somewhere else on
> > ftp.kernel.org.
> 
> Jeff,
> 	Red Hat started included the IPVS patches from
> http://www.linuxvirtualserver.org/ starting with RH6.1 (I believe).  You
> can find the patch they use in the kernel src.rpm, or go get the patch
> from the URL listed above.

Dax,

Thanks.  I noticed the pirahna web server rpm would rebuild unless the 
kernel had this patch.  I was wondering why it wasn't in the stock kernels
since it's GPL.  We may want to consider including it.

Jeff

> 
> Dax
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2000-11-13  5:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-11  0:24 /net/ip_vs.h in stock kernels Jeff V. Merkey
2000-11-12  5:52 ` Dax Kelson
2000-11-13  6:38   ` Jeff V. Merkey [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=20001112233819.C15243@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=dax@gurulabs.com \
    --cc=jmerkey@timpanogas.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox