From: Tong Li <tonli-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Problem about inst_simple()
Date: Fri, 02 Dec 2016 17:37:30 +0800 [thread overview]
Message-ID: <1480671450.22333.16.camel@redhat.com> (raw)
Hello Harald,
I was working on fixing the 95ssh-client issue. The code in my last
pull request(#184) copies only customized UserKnownHostsFile under
/root to initramfs, which fix the problem we meet in kdump process. Now
I am trying to make it more general. Users may set UserKnownHostsFile
to something like ~/foo, but it seems inst_simple() can't handle this
kind of path well now. In my test, this issue can be handled by
replacing "~" in such a variable to "${HOME}". Should we just place the
checking and replacing code in 95ssh-client module, or add it to
inst_simeple() in case that other modules attempt to install a file
whose path is like "~/foo"? What do you think about it?
Regards,
Tong
reply other threads:[~2016-12-02 9:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1480671450.22333.16.camel@redhat.com \
--to=tonli-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).