From: Christoph Hellwig <hch@infradead.org>
To: Maurizio Lombardi <mlombard@bsdbackstore.eu>
Cc: Richard Weinberger <richard@nod.at>,
linux-nvme <linux-nvme@lists.infradead.org>,
Daniel Wagner <wagi@monom.org>
Subject: Re: nvmetcli creates tilde directories
Date: Wed, 9 Apr 2025 01:58:16 -0700 [thread overview]
Message-ID: <Z_Y2qHCEFDnRRpyy@infradead.org> (raw)
In-Reply-To: <D91YFPG2AMZG.1QFEKLMBO5J9Q@bsdbackstore.eu>
On Wed, Apr 09, 2025 at 10:11:24AM +0200, Maurizio Lombardi wrote:
> On Wed Apr 9, 2025 at 9:43 AM CEST, Richard Weinberger wrote:
> > Hi!
> >
> > After playing with nvmetcli, I noticed that my home directory was sprinkled
> > with directories named "~".
> > It seems like configshell used by nvmetcli does not resolve "~" to my home directory.
>
> Is this a regression? Which version of configshell is Tumbleweed
> running?
>
> There were some large changes to configshell upstream recently so I am
> wondering if something has been broken.
FYI, I recently had a ~ directory show up in my home directory as well,
but didn't manage to track it down. I've not used nvmetcli on that
system, but did use targetcli so configshell would be involved as well.
This is on a debian unstable system using configshell-fb 1:2.0.0-1.
next prev parent reply other threads:[~2025-04-09 10:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 7:43 nvmetcli creates tilde directories Richard Weinberger
2025-04-09 8:11 ` Maurizio Lombardi
2025-04-09 8:53 ` Richard Weinberger
2025-04-09 8:56 ` Maurizio Lombardi
2025-04-09 11:32 ` Richard Weinberger
2025-04-09 12:07 ` Maurizio Lombardi
2025-04-11 13:51 ` Maurizio Lombardi
2025-04-09 8:58 ` Christoph Hellwig [this message]
2025-04-14 8:48 ` Maurizio Lombardi
2025-04-14 8:51 ` Richard Weinberger
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=Z_Y2qHCEFDnRRpyy@infradead.org \
--to=hch@infradead.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mlombard@bsdbackstore.eu \
--cc=richard@nod.at \
--cc=wagi@monom.org \
/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.