From: Corey Hickey <bugfood-ml@fatooh.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Does anyone have got an iproute2+esfq package for debian ?
Date: Mon, 11 Dec 2006 04:24:48 +0000 [thread overview]
Message-ID: <457CDD90.8050508@fatooh.org> (raw)
In-Reply-To: <457CBB8C.7020309@wanadoo.fr>
First of all, you have to understand that if you use the "reply"
function of your email program, your message will be marked as a reply
to the message you replied to. Changing the subject line doesn't make a
difference. Unless you are actually replying to a message, you _must_
use your email program's "new message" function.
Probably you don't see this effect because you're not using a threaded
view to list your email messages, but it tends to annoy those of us who do.
By now it's too late, but please remember next time you want to ask a
question.
Meanwhile...
Sébastien CRAMATTE wrote:
> Does anyone have got an iproute2+esfq package for debian sarge ?
> I've got many error trying building it from source ...
>
> I use debian sarge 3.1 and gcc 3.3.5-3
>
> I've started getting a recent iproute2 package from backports.org
> and esfq-iprout2.patch from fatooh.org
My ESFQ patches are created to work with the original source;
distributions tend to modify the source of packages with their own
customizations. In this case, it appears one of those customizations if
incompatible.
The latest iproute2 release with the latest ESFQ patch builds fine for me.
http://linux-net.osdl.org/index.php/Iproute2
This section from the ESFQ README may be of use to you:
You don't necessarily have to install the entire patched version of
iproute2 if you don't want to (perhaps you would rather keep your
distribution's package). All you need is the tc binary.
# cp -p tc/tc /sbin/tc-esfq
# chown root:root /sbin/tc-esfq
Just modify your scripts to use /sbin/tc-esfq instead of /sbin/tc.
> #apt-get source iproute
> #cd /usr/src/iproute-20061002
>
> this command doesn't create tc/q_esfq.c file
> #patch -p1 --dry-run < ../esfq-iproute2.patch
Of course. That's the point of --dry-run: to see what errors might
happen without screwing up a source tree by half-applying a broken or
outdated patch. :)
-Corey
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-12-11 4:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-11 1:59 [LARTC] Does anyone have got an iproute2+esfq package for debian ? Sébastien CRAMATTE
2006-12-11 2:05 ` Sébastien CRAMATTE
2006-12-11 4:24 ` Corey Hickey [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=457CDD90.8050508@fatooh.org \
--to=bugfood-ml@fatooh.org \
--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.