From: Benjamin Drung <benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: rdma-core: Location of 70-persistent-ipoib.rules
Date: Mon, 11 Sep 2017 13:33:47 +0200 [thread overview]
Message-ID: <1505129627.3732.3.camel@profitbricks.com> (raw)
Hi,
70-persistent-ipoib.rules is installed in /etc/udev/rules.d on Debian.
lintian complains about it:
E: udev-rule-in-etc
N:
N: This package ships a udev rule and installs it under
N: /etc/udev/rules.d, which is reserved for user-installed files. The
N: correct directory for system rules is /lib/udev/rules.d.
N:
N: Refer to https://bugs.debian.org/559208 for details.
N:
N: Severity: important, Certainty: certain
N:
N: Check: files, Type: binary, udeb
N:
Since 70-persistent-ipoib.rules is just a commented example, should we
better put it into /usr/share/doc/rdma-core instead (where udev.md is
placed)?
--
Benjamin Drung
System Developer
Debian & Ubuntu Developer
ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin
Email: benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org
Web: https://www.profitbricks.com
Sitz der Gesellschaft: Berlin.
Registergericht: Amtsgericht Charlottenburg, HRB 125506B.
Geschäftsführer: Achim Weiss.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-09-11 11:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 11:33 Benjamin Drung [this message]
[not found] ` <1505129627.3732.3.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-09-11 16:25 ` rdma-core: Location of 70-persistent-ipoib.rules Jason Gunthorpe
[not found] ` <20170911162521.GD32117-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-09-22 16:45 ` Doug Ledford
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=1505129627.3732.3.camel@profitbricks.com \
--to=benjamin.drung-eikl63zcoxah+58jc4qpia@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.