From: md@Linux.IT (Marco d'Itri)
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: netdev@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Backward compatibility and WAN netdev configuration
Date: Wed, 1 Feb 2006 15:49:17 +0100 [thread overview]
Message-ID: <20060201144917.GA7644@wonderland.linux.it> (raw)
In-Reply-To: <m3psm7tksr.fsf@defiant.localdomain>
On Feb 01, Krzysztof Halasa <khc@pm.waw.pl> wrote:
> a) Currently it consists of mid-layer WAN protocols single module (Cisco
> HDLC, FR etc.) + low-level hardware HDLC card driver (C101, N2, PCI200SYN
> etc.). I'm thinking about splitting the protocol module into separate
> modules - it would make them independent, users would be able to
> load, say, FR without PPP or X.25 and underlying syncppp, lapb etc.
> From the technical POV it would be superior to current code but it
> would require sysadmins to change modprobe.conf, add another modprobe
> or something like that. Not a real problem but the upgrade can't be
> automatic.
Why you cannot support autoloading the modules when a specific protocol
is needed?
--
ciao,
Marco
next prev parent reply other threads:[~2006-02-01 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 10:50 [RFC] Backward compatibility and WAN netdev configuration Krzysztof Halasa
2006-02-01 14:49 ` Marco d'Itri [this message]
2006-02-01 18:33 ` Krzysztof Halasa
2006-02-01 18:39 ` Stephen Hemminger
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=20060201144917.GA7644@wonderland.linux.it \
--to=md@linux.it \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).