From: "Randy.Dunlap" <rddunlap@osdl.org>
To: rusty@rustcorp.com.au
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Loading a module multtiple times
Date: Wed, 30 Apr 2003 14:05:57 -0700 [thread overview]
Message-ID: <20030430140557.12e13f1a.rddunlap@osdl.org> (raw)
Hi Rusty-
I was looking into a bug in /proc/net/dev truncated output.
/proc/net/dev lists {if (!buggy)} all loaded network interfaces.
To get a large number of network interfaces, Christian (below)
told me to copy driver/net/dummy.o to several different file names
and then insmod them. It seems to have worked for him, and it works
that way in 2.4.recent, but it's not working for me. See error
messages below.
Which way is expected behavior?
What should be the expected behavior?
or am I just seeing bugs (failures) that noone else sees?
It seems like not supporting this is likely to cause some problems.
Thanks,
~Randy
(was: [BUG 2.5.67 (and probably earlier)] /proc/dev/net doesnt show all net devices)
On Wed, 30 Apr 2003 09:11:11 +0200 Christian Bornträger <linux@borntraeger.net> wrote:
| > How do I configure the dummy network driver to get loads of interfaces?
|
| Just copy the dummy.o to dummy1.o dummy2.o dummy3.o, insmod and ifconfig
| them.
Doesn't work for me. insmod (from ver. 0.9.11a module-init-tools)
won't load multiple copies of dummy[n].o or dummy[n].ko.
(with dummy already loaded)
For the .o files, it says:
dummy: no version magic, tainting kernel.
Error inserting 'dummy1.o': -1 File exists
and for the .ko files, it says:
Error inserting 'dummy1.ko': -1 File exists
---
next reply other threads:[~2003-04-30 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 21:05 Randy.Dunlap [this message]
2003-04-30 22:42 ` Loading a module multtiple times Kai Germaschewski
2003-05-01 2:12 ` Rusty Russell
2003-05-01 5:10 ` Randy.Dunlap
2003-05-01 6:22 ` Rusty Russell
2003-05-01 10:09 ` Alan Cox
2003-04-30 21:59 Chuck Ebbert
2003-05-01 11:54 Chuck Ebbert
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=20030430140557.12e13f1a.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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).