From: Zdenek Kabelac <zkabelac@redhat.com>
To: Gang He <GHe@suse.com>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] devices/dir configuration option in /etc/lvm/lvm.conf can be edited?
Date: Mon, 14 Oct 2019 12:55:38 +0200 [thread overview]
Message-ID: <f1ffa375-ac99-fc4c-3499-7b8432d3910f@redhat.com> (raw)
In-Reply-To: <CH2PR18MB32063E1556F117BA9B9F5285CF900@CH2PR18MB3206.namprd18.prod.outlook.com>
Dne 14. 10. 19 v 12:52 Gang He napsal(a):
> Hi Zdenek,
>
> Thanks for explaining.
> That means we should tell the user, you should not edit this option (dir = "/dev") in the lvm.conf, right?
>
Basically yes.
The option is there for 'skilled' users who know exactly how the whole 'device
creation process' works - essentially these days this option is mostly useful
only for some testing...
Regards
Zdenek
next prev parent reply other threads:[~2019-10-14 10:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 8:00 [linux-lvm] devices/dir configuration option in /etc/lvm/lvm.conf can be edited? Gang He
2019-10-14 10:39 ` Zdenek Kabelac
2019-10-14 10:52 ` Gang He
2019-10-14 10:55 ` Zdenek Kabelac [this message]
2019-10-14 13:19 ` Alasdair G Kergon
2019-10-15 2:19 ` Gang He
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=f1ffa375-ac99-fc4c-3499-7b8432d3910f@redhat.com \
--to=zkabelac@redhat.com \
--cc=GHe@suse.com \
--cc=linux-lvm@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).