From: Jan Pokorný <jpokorny@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] FYI: dlm.service possibly silenty overwritten with DisplayLink driver installer
Date: Wed, 21 Nov 2018 00:28:47 +0100 [thread overview]
Message-ID: <20181120232847.GF6337@redhat.com> (raw)
Accidentally, when searching for something systemd related, dlm.service
caught my eye, and surprisingly, it was rather in a HW support in Linux
SW enablement context. Briefly looking into the Ubuntu driver that
allegedly contained that file (or recipe to create it, actually), I've
realized the respective installer would simply overwrite the regular
cluster DLM related service file without any hesitations
(unless I miss something).
So take this as a heads-up to watch out for that circumstance, three
letter acronyms are apparently not very namespace-collision-proof.
I logged this with their "Feature Suggestion" asking for more
carefulness:
https://support.displaylink.com/forums/287786-displaylink-feature-suggestions/suggestions/36068896
--
Jan (Poki)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20181121/44f0ec55/attachment.sig>
reply other threads:[~2018-11-20 23:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20181120232847.GF6337@redhat.com \
--to=jpokorny@redhat.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).