Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Marcelo Araujo <chelupulus@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Unknown qdisc "htb", hence option "default" is unparsable
Date: Mon, 18 Oct 2004 12:13:39 +0000	[thread overview]
Message-ID: <1775d24d0410180513511056ed@mail.gmail.com> (raw)
In-Reply-To: <marc-lartc-105660880414915@msgid-missing>

Thanks a lot to everybody..!!

it's work :)

(i think :-p)

See ya.

Marcelo


On Wed, 06 Oct 2004 19:40:25 -0700, gypsy <gypsy@iswest.com> wrote:
> Marcelo Araujo wrote:
> >
> >
> > This is "tc" in /sbin/
> > -rwxr-xr-x    1 root     root       114716 Nov  3  2003 tc
> > This is "tc" in htb3.6-020525.tgz
> > -rwxrwxr-x    1 root     root       101992 May 12  2002 tc
> >
> > The "tc" from the tarball is small compare to the system, so my question is,
> > can i use the tc from the tarball without any know issue? may i update my
> > kernel? what version are sure to work?
> 
> The tc you got from the tarball has been stripped of the debug info.  It
> is 100% functional and fine.
> 
> Unless you encounter problems, your kernel should be fine too.
> 
> gypsy
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2004-10-18 12:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-26  6:25 [LARTC] Unknown qdisc "htb", hence option "default" is unparsable rio
2003-06-26  6:39 ` AW: " Martin Teufel
2003-06-26  6:48 ` [LARTC] Unknown qdisc "htb", hence option "default" is K S Sreeram
2004-10-06 15:06 ` [LARTC] Unknown qdisc "htb", hence option "default" is unparsable Marcelo Araujo
2004-10-07  2:40 ` gypsy
2004-10-18 12:13 ` Marcelo Araujo [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=1775d24d0410180513511056ed@mail.gmail.com \
    --to=chelupulus@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox