From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: Bernard Pidoux <pidoux@ccr.jussieu.fr>
Cc: linux-hams@vger.kernel.org
Subject: Re: Rose module and kernel 2.6.11
Date: Wed, 13 Apr 2005 00:16:02 +0100 [thread overview]
Message-ID: <20050412231602.GA4548@linux-mips.org> (raw)
In-Reply-To: <425ADD44.8090509@ccr.jussieu.fr>
On Mon, Apr 11, 2005 at 10:25:40PM +0200, Bernard Pidoux wrote:
> I have noticed something strange with rose module and 2.6 kernel (at
> least 2.6.10 and 2.6.11).
>
> When loading rose module, it loads now automatically ax25 module. Good.
Modprobe certainly got that right in 2.4 also.
> But, it also creates 9 interfaces from rose0 to rose9 with hardware
> address 0000000 as seen with IP address or ifconfig.
>
> Is this what rose module should do actually ?
> With previous versions, loading rose module did not create any rose
> interface. They were created by the application such as ROSE/FPAC.
It's crufty, yes. No idea why the code was written the way it is but on
startup the code will generate 10 ROSE interfaces just in case. However
the kernel does no "ifconfig roseX up", so ifconfig shouldn't display
them without the -a option. If that happens to you then then I guess one
of your distribution's configuration mechanisms is playing a little
crazy. You can easily see that in /proc/net/dev - any ROSE system will
have 10 rose%d devices in there.
73 de DL5RB op Ralf
--
Loc. JN47BS / CQ 14 / ITU 28 / DOK A21
next prev parent reply other threads:[~2005-04-12 23:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 3:34 Knoppix and Soundmodem David Hambly
2005-04-08 17:16 ` David Hambly
2005-04-11 20:25 ` Rose module and kernel 2.6.11 Bernard Pidoux
2005-04-12 23:16 ` Ralf Baechle DL5RB [this message]
2005-10-23 16:22 ` Knoppix and Soundmodem Douglas Cole
2005-10-23 23:46 ` w9ya
2005-10-24 5:34 ` w9ya
2005-10-24 16:00 ` Jim Bayer
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=20050412231602.GA4548@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-hams@vger.kernel.org \
--cc=pidoux@ccr.jussieu.fr \
/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.