From: Julian Anastasov <ja@ssi.bg>
To: lartc@vger.kernel.org
Subject: Re: [Linux Diffserv] Re: [LARTC] ingress qdisc on kernel 2.2.21 with
Date: Fri, 12 Jul 2002 12:26:32 +0000 [thread overview]
Message-ID: <marc-lartc-102647691129664@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102638963713023@msgid-missing>
Hello,
On Fri, 12 Jul 2002, jamal wrote:
> If you look at the old postings on the diffserv mailing list youll see
> about 70% of the questions were related to "my patch failed" etc (people
> patching in the wrong directory etc). Believe it or not a _lot_ of Linux
> users still hate patching (I have matured to accept it) or are not
> very skilled or bothered to learn; they just install connectiva 8 and are
> off to cook: i.e they just want things to work.
> Now unlike MS, we have the code! infact Werner has clearly documented what
> the changes from 2.2->2.4 are in his doc. I know the only time i have
> lately is for breathing (hopefully fresh air at work) and this backporting
> requires abuse of the brain cells more than thinking i.e its mechanical
> and therefore requires concentration/focus;
>
> so if someone could submit a backport patch <hint, hint> i think we would
> put it up the website. I believe we could even push it into the 2.2 next
> release since this stuff is pretty much stable right now.
At least, we need valid patch with the most needed
fixes. I think, I can walk the both trees and to fix the
obvious bugs that are fixed in 2.4. At first look, the changes
are not too much, so we will be back soon with the most needed
fixes. I can report that the small part of the code I'm using looks
stable enough.
> > > BTW, what is the motivatein behind:
> > > http://www.linuxvirtualserver.org/~julian/01_ingress-breaks-fw-1.diff
> >
> > At least, FW_REDIRECT, not sure for any others
> >
>
> I am trying to think of some way to probably do this from ingress instead
> since some people actually want that overwrite.
ok :) But then you have to add ipchains support for tc
in addition to the iptables' one. My wish was to have only the
needed bugfixes :)
> cheers,
> jamal
Regards
--
Julian Anastasov <ja@ssi.bg>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-07-12 12:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 12:06 [Linux Diffserv] Re: [LARTC] ingress qdisc on kernel 2.2.21 with jamal
2002-07-12 9:57 ` [Linux Diffserv] Re: [LARTC] ingress qdisc on kernel 2.2.21 jamal
2002-07-12 10:11 ` [Linux Diffserv] Re: [LARTC] ingress qdisc on kernel 2.2.21 with jamal
2002-07-12 10:49 ` Julian Anastasov
2002-07-12 11:37 ` jamal
2002-07-12 12:26 ` Julian Anastasov [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=marc-lartc-102647691129664@msgid-missing \
--to=ja@ssi.bg \
--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.