From: "Randy.Dunlap" <rddunlap@osdl.org>
To: linux@borntraeger.net
Cc: acme@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: [BUG 2.5.67 (and probably earlier)] /proc/dev/net doesnt show all net devices
Date: Tue, 29 Apr 2003 13:07:42 -0700 [thread overview]
Message-ID: <20030429130742.2c38b5f3.rddunlap@osdl.org> (raw)
In-Reply-To: <20030429092857.4ebffcc9.rddunlap@osdl.org>
On Tue, 29 Apr 2003 09:28:57 -0700 "Randy.Dunlap" <rddunlap@osdl.org> wrote:
| On Tue, 29 Apr 2003 14:34:18 +0200 Christian Bornträger <linux@borntraeger.net> wrote:
|
| | Summary: /proc/net/devices doesnt show all devices using cat. With dd all are
| | available.
| |
| | I tested a kernels prior to
| | http://linus.bkbits.net:8080/linux-2.5/cset@1.797.156.3
| | and it doesnt seem to have this problem.
|
|
| I haven't tried to make that many net devices.
| Acme, does this look helpful?
| Christian, can you test this patch?
|
| --
|
|
| diff -Naur ./net/core/dev.c%SEQ ./net/core/dev.c
| --- ./net/core/dev.c%SEQ 2003-04-28 15:07:01.000000000 -0700
| +++ ./net/core/dev.c 2003-04-29 09:06:18.000000000 -0700
| @@ -1789,7 +1789,7 @@
| struct net_device *dev;
| loff_t i;
|
| - for (i = 0, dev = dev_base; dev && i < pos; dev = dev->next);
| + for (i = 0, dev = dev_base; dev && i < pos; dev = dev->next, i++);
|
| return i == pos ? dev : NULL;
| }
| -
Oh well, I don't think that works.
How do I configure the dummy network driver to get loads of interfaces?
--
~Randy
next prev parent reply other threads:[~2003-04-29 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 12:34 [BUG 2.5.67 (and probably earlier)] /proc/dev/net doesnt show all net devices Christian Bornträger
2003-04-29 16:28 ` Randy.Dunlap
2003-04-29 20:07 ` Randy.Dunlap [this message]
2003-04-30 7:11 ` Christian Bornträger
2003-04-30 15:49 ` Randy.Dunlap
2003-04-30 8:12 ` Christian Bornträger
2003-05-01 21:12 ` Randy.Dunlap
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=20030429130742.2c38b5f3.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=acme@conectiva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@borntraeger.net \
/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;
as well as URLs for NNTP newsgroup(s).