From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: [PATCH nvme-cli v2 2/2] nvme.spec/debian: Auto generate host nqn as part of install
Date: Thu, 17 Nov 2016 09:58:03 -0800 [thread overview]
Message-ID: <1479405483.3774.5.camel@linux.intel.com> (raw)
In-Reply-To: <1479405067.3774.3.camel@linux.intel.com>
On Thu, 2016-11-17@09:51 -0800, J Freyensee wrote:
> On Thu, 2016-11-17@05:36 -0800, Christoph Hellwig wrote:
> >
> > On Thu, Nov 17, 2016@02:54:48PM +0200, Sagi Grimberg wrote:
> > >
> > >
> > > The installation will generate a hostnqn and store it in
> > > /etc/nvme/hostnqn file (in case it doesn't exist).
> > > This file will be removed upon uninstallation (purge on for
> > > debian).
> > >
> > > Signed-off-by: Sagi Grimberg <sagi at grimberg.me>
> > > ---
> > > ?debian/postinst | 20 ++++++++++++++++++++
> > > ?debian/postrm???| 10 ++++++++++
> > > ?nvme.spec.in????| 17 +++++++++++++++++
> > > ?3 files changed, 47 insertions(+)
> > > ?create mode 100644 debian/postinst
> > > ?create mode 100644 debian/postrm
> > >
> > > diff --git a/debian/postinst b/debian/postinst
> > > new file mode 100644
> > > index 000000000000..b258cf569c3e
> > > --- /dev/null
> > > +++ b/debian/postinst
> > > @@ -0,0 +1,20 @@
> > > +#!/bin/sh
> > > +
> > > +set -e
> > > +
> > > +case "$1" in
> > > +????configure|install)
> > > + if [ ! -f /etc/nvme/hostnqn ]; then
> > > + install -D /dev/null /etc/nvme/hostnqn
> > > + echo $(nvme gen-hostnqn) > /etc/nvme/hostnqn
> >
> > The $() syntax is a bash-ish.??To work with a traditional bourne
> > shell
> > it needs to be `nvme gen-hostnqn`
> >
> > >
> > >
> > > + if [ ! -n "$(ls -A /etc/nvme)" ]; then
> >
> > Same here.
> >
> > >
> > >
> > > + rm -rf /etc/nvme
> > > + fi
> >
> > But maybe you should just do a
> >
> > rmdir /etc/nvme >/dev/null
>
Nevermind, I'm dumb, Nack the comment, I didn't read that right from
the comments and code separated...more coffee :-/
> Please don't do a remove of the directory, just remove the files
> created from this patch (/etc/nvme/hostnqn). ?As I mentioned earlier,
> someone for example could have independently created a discovery.conf
> file in /etc/nvme and might have not wanted that file removed when
> this
> is uninstalled. ?If the directory was created from this patch then
> either leave the directory /etc/nvme behind or test to see if
> /etc/nvme
> is empty after removing /etc/nvme/hostnqn before attempting to remove
> the directory /etc/nvme.
>
>
> >
> >
> > instead?
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2016-11-17 17:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 12:54 [PATCH nvme-cli v2 0/2] auto generate hostnqn file on installation Sagi Grimberg
2016-11-17 12:54 ` [PATCH nvme-cli v2 1/2] nvme-cli: Add nvme hostnqn generation option Sagi Grimberg
2016-11-17 13:34 ` Christoph Hellwig
2016-11-17 17:53 ` J Freyensee
2016-11-17 12:54 ` [PATCH nvme-cli v2 2/2] nvme.spec/debian: Auto generate host nqn as part of install Sagi Grimberg
2016-11-17 13:36 ` Christoph Hellwig
2016-11-17 17:51 ` J Freyensee
2016-11-17 17:58 ` J Freyensee [this message]
2016-11-17 14:36 ` [PATCH nvme-cli v2 0/2] auto generate hostnqn file on installation Christoph Hellwig
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=1479405483.3774.5.camel@linux.intel.com \
--to=james_p_freyensee@linux.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).