From: md@Linux.IT (Marco d'Itri)
To: Lucas De Marchi <lucas.de.marchi@gmail.com>
Cc: Lubomir Rintel <lkundrak@v3.sk>,
Lucas De Marchi <lucas.demarchi@intel.com>,
linux-modules <linux-modules@vger.kernel.org>,
jeyu@kernel.org
Subject: Re: [RESEND PATCH] modprobe: install default configuration
Date: Fri, 8 Sep 2017 23:30:48 +0200 [thread overview]
Message-ID: <20170908213048.d4lwkemko53sqagb@bongo.bofh.it> (raw)
In-Reply-To: <CAKi4VAKS7Vo6WoEJGjY6cRMZxmSsv4mj=eRhhHCnYno0DoP5Ag@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]
On Sep 08, Lucas De Marchi <lucas.de.marchi@gmail.com> wrote:
> On Fri, Sep 1, 2017 at 4:28 AM, Lubomir Rintel <lkundrak@v3.sk> wrote:
> > Some network devices have an awful habit of creating interfaces when loaded,
> > despite not asked for. Worse even, they do so while being autoloaded due to an
> > attempt to create a device via netlink:
I agree that this behaviour by dummy, bonding, etc is unfortunate
and annoying; however, I do not believe that user space tools
maintainers overriding the decisions of kernel maintainers will help
creating an healty environment.
As the Debian kmod maintainer I would also be seriously concerned about
carrying this change since it would break existing configurations on
upgrades.
> It seems you forgot to follow up on the feedback I gave last time and
> asked for opinions.
>
> https://lkml.org/lkml/2016/6/14/336
I think that this would create excessive complexity and force everybody
to learn the semantics of this new directive.
If you really believe that copying the whole file would be bad then just
split the directives in multiple files.
--
ciao,
Marco
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2017-09-08 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 11:28 [RESEND PATCH] modprobe: install default configuration Lubomir Rintel
2017-09-08 21:03 ` Lucas De Marchi
2017-09-08 21:30 ` Marco d'Itri [this message]
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=20170908213048.d4lwkemko53sqagb@bongo.bofh.it \
--to=md@linux.it \
--cc=jeyu@kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=lucas.de.marchi@gmail.com \
--cc=lucas.demarchi@intel.com \
/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).