mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: TeLeNiEkO <telenieko@telenieko.com>
To: linux-kernel@vger.kernel.org
Subject: 2 Possible bugs, 1 'stuff'
Date: Tue, 30 Jan 2001 23:35:49 +0100	[thread overview]
Message-ID: <20010130233549.A5149@telenieko.com> (raw)

On kernel 2.4.0:
 The ne2k-pci driver (NE2000 PCI) cannont be compiled as a module. I tried it on two computers and I had really hard problems.
 I built it in. If this wasn't notified yet let me know and I'll recompile the kernel to get the exact error message and bring it to you. (It was about unresolved simbols, you won't need to habe the card to see it!)

The other think is about Traffic Shaping and QoS:
Wendy:/etc/ipconf# tc filter add dev eth1 parent 1:0 protocol ip prio 100 u32 match ip dst 192.168.0.69 flowid 1:2
RTNETLINK answers: Invalid argument

Both 1:0 and 1:2 are created, and according to the howto that should run (and it did on 2.2.18), if you want I'll send you a complete list of the commands issued to 'tc'.

(Traffic Shaper and QoS was compiled as built-in, i got more unresolved simbols having them as modules!)

The other thing...
 Many new users are coming to linux world. But the BUG-HUNTING really goes far for a lot of people. Many people are trying linux for first time, after 2 months they try to get witth kernel update and OOOhh, they find a bug! then:
 a) They don't find a nice button to notify the bug on their desktop... and the most clever can't find it on a website.
 b) When they read the BUG-HUNTING doc they just get the windows CD and go back to monkeys world.

So, as Linux intends to approach to more "home-users" each day, there should be an easier way to notify bugs, for thoose users. Remember that it's while you mess up with things is when bugs appear. 
And there's nothing better than a novice user to mess-up with a kernel ;o)

So, try to find an easier, but reallybly way, for notifiing bugs (a form on kernel.org won't do much!)

And let me know about the ne2k-pci and TF bugs (if they are).

sincerelly,
 TeLeNiEkO (Barcelona, Spain)

PD: If you want full info about one of the "bugs" let me know, and I'll do my best to recompile the kernel.
-
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:[~2001-01-30 22:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010130233549.A5149@telenieko.com \
    --to=telenieko@telenieko.com \
    --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

all inboxes | Powered by JetHome®