From: Kamil Konieczny <k.konieczny@partner.samsung.com>
To: valdis.kletnieks@vt.edu, Pintu Kumar <pintu.ping@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Damian Tometzki <damian.tometzki@icloud.com>,
kernelnewbies@kernelnewbies.org
Subject: Re: How to verify linux-next
Date: Mon, 02 Oct 2017 10:11:34 +0200 [thread overview]
Message-ID: <ee494e9a-0067-5416-b0a7-56fb3ef19d83@partner.samsung.com> (raw)
In-Reply-To: <10625.1506699956@turing-police.cc.vt.edu>
On 29.09.2017 17:45, valdis.kletnieks@vt.edu wrote:
> On Fri, 29 Sep 2017 19:56:41 +0530, Pintu Kumar said:
>
>> 1) If you have pointers on how to setup ssh/net connection on QEMU
>> with busybox, do let me know.
>
> Busybox doesn't do that as far as I know, as it's intended as a single-user
> /sbin/init replacement. You'll need a full-featured userspace with an actual
> init daemon (sysvinit, systemd, etc) and an ssh daemon (openssh, or if you want [...]
What about /usr/bin/ssh as init replacement ?
--
Best regards,
Kamil Konieczny
Samsung R&D Institute Poland
next prev parent reply other threads:[~2017-10-02 8:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 9:42 How to verify linux-next Pintu Kumar
2017-09-29 9:46 ` Pintu Kumar
2017-09-29 10:38 ` Pintu Kumar
2017-09-29 12:41 ` valdis.kletnieks
2017-09-29 13:05 ` Damian Tometzki
2017-09-29 13:14 ` Damian Tometzki
2017-09-29 14:26 ` Pintu Kumar
2017-09-29 15:45 ` valdis.kletnieks
2017-10-02 8:11 ` Kamil Konieczny [this message]
2017-10-02 11:04 ` valdis.kletnieks
2017-09-29 17:53 ` Pintu Kumar
2017-09-29 21:50 ` Theodore Ts'o
2017-09-30 3:58 ` Pintu Kumar
2017-09-30 5:25 ` Theodore Ts'o
2017-10-01 16:28 ` Pintu Kumar
2017-10-01 16:44 ` Damian Tometzki
2017-10-01 16:48 ` Randy Dunlap
2017-10-01 17:03 ` Mike Galbraith
2017-10-01 18:47 ` Pintu Kumar
2017-10-01 16:47 ` Theodore Ts'o
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=ee494e9a-0067-5416-b0a7-56fb3ef19d83@partner.samsung.com \
--to=k.konieczny@partner.samsung.com \
--cc=damian.tometzki@icloud.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pintu.ping@gmail.com \
--cc=valdis.kletnieks@vt.edu \
/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).