From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH nvme-cli v2 0/2] auto generate hostnqn file on installation
Date: Thu, 17 Nov 2016 14:54:46 +0200 [thread overview]
Message-ID: <1479387288-13367-1-git-send-email-sagi@grimberg.me> (raw)
This set is designed to help the user by auto-generating a hostnqn and
placing it in /etc/nvme/hostnqn file upon installation of nvme-cli (in
case such a file doesn't exist).
The user can re-generate different hostnqns on demand by running:
$ nvme gen-hostnqn
Only the deb package is tested.
Changes from v1:
- don't keep local hostnqn var for sprintf
- don't delete /etc/nvme if it contains other files other
than what we installed (hostnqn)
Changes from v0 (rfc):
- Moved hostnqn generation to nvme with the command gen-hostnqn
- Cleanup hostnqn file only on purge in debian
Sagi Grimberg (2):
nvme-cli: Add nvme hostnqn generation option
nvme.spec/debian: Auto generate host nqn as part of install
Makefile | 1 +
debian/postinst | 20 ++++++++++++++++++++
debian/postrm | 10 ++++++++++
nvme-builtin.h | 1 +
nvme.c | 12 ++++++++++++
nvme.spec.in | 17 +++++++++++++++++
6 files changed, 61 insertions(+)
create mode 100644 debian/postinst
create mode 100644 debian/postrm
--
2.7.4
next reply other threads:[~2016-11-17 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 12:54 Sagi Grimberg [this message]
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
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=1479387288-13367-1-git-send-email-sagi@grimberg.me \
--to=sagi@grimberg.me \
/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).