From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: [PATCH] nvmetcli: More refined cleanup of README
Date: Mon, 01 Aug 2016 11:26:46 -0700 [thread overview]
Message-ID: <1470076006.5653.2.camel@linux.intel.com> (raw)
In-Reply-To: <20160801112354.GE28246@infradead.org>
On Mon, 2016-08-01@04:23 -0700, Christoph Hellwig wrote:
> On Thu, Jul 28, 2016@10:37:06AM -0700, Jay Freyensee wrote:
> > --- a/README
> > +++ b/README
> > @@ -12,6 +12,11 @@ https://github.com/agrover/configshell-fb first.
> > nvmetcli can be run directly from the source directory or
> > installed
> > using setup.py.
> >
> > +If you choose to use the provided exe 'nvmetcli', you can move
> > +'nvmetcli' to /usr/sbin and the file 'nvmet.service' to
> > +/lib/systemd/system for global management of NVMe target setups
> > +for the machine.
>
> Hmm. Maybe we'll need to add a install rule to setup.py instead?
> Either way the preferred way to install nvmetcli is to use the deb
> or rpm packaging created by make deb or make rpm. The documentation
> should point to those as the first choice.
That would probably work too.
I can say .deb/.rpm is preferrred, but from my previous experience,
.rpm doesn't always work, hence the background info.
>
> > Common Package Dependencies and Problems
> > -----------------------------------------
> > nvmetcli uses the 'python-six' and 'pyparsing' packages
> > @@ -53,6 +58,13 @@ The following walks through an example using
> > interactive mode.
> > ...> create hostnqn
> >
> > #
> > +# remove access of a subsystem by deleting the Host NQN
> > +#
> > +
> > +...> cd /subsystems/testnqn/allowed_hosts/
> > +...> delete hostnqn
> > +
> > +#
> > # Alternatively this allows any host to connect to the subsystsem.
> > Only
> > # use this in tightly controller environments:
> > #
> > @@ -65,7 +77,7 @@ The following walks through an example using
> > interactive mode.
> > # unused one will be used.
> > #
> >
> > -...> cd namespaces
> > +...> cd /subsystems/testnqn/namespaces
> > ...> create 1
> > ...> cd 1
> > ...> set device path=/dev/nvme0n1
>
> But I've applied this part already and pushed it out.
OK. I'll add another blurb on discovery and referrals, hopefully soon.
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2016-08-01 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 17:37 [PATCH] nvmetcli: More refined cleanup of README Jay Freyensee
2016-07-29 20:01 ` Sagi Grimberg
2016-08-01 11:23 ` Christoph Hellwig
2016-08-01 18:26 ` J Freyensee [this message]
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=1470076006.5653.2.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 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.