From: valdis.kletnieks@vt.edu (valdis.kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to verify linux-next
Date: Mon, 02 Oct 2017 07:04:41 -0400 [thread overview]
Message-ID: <214615.1506942281@turing-police.cc.vt.edu> (raw)
In-Reply-To: <ee494e9a-0067-5416-b0a7-56fb3ef19d83@partner.samsung.com>
On Mon, 02 Oct 2017 10:11:34 +0200, Kamil Konieczny said:
> What about /usr/bin/ssh as init replacement ?
Well, if you are OK with your system panicking right away. :)
(Hint - the init process needs to be something that can run as a daemon).
If you use /usr/sbin/sshd, that has a *slightly* better chance of working,
except then you will need a *lot* of custom coding in your initramfs to do all
the system setup usually done by init during boot - mounting file systems,
configuring network interfaces, etc etc etc. Plus, sshd probably doesn't have
some of the code needed for a true init process, such as reaping child
processes it didn't spawn itself, cleanly shutting down/rebooting, and so on...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 486 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20171002/5b25db4e/attachment.bin
next prev parent reply other threads:[~2017-10-02 11:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOuPNLik8AiWiBXokFAVpbnFxdLz8T+2wZPWfWLn-F+piAHCSw@mail.gmail.com>
2017-09-29 9:46 ` How to verify linux-next Pintu Kumar
2017-09-29 10:38 ` Pintu Kumar
2017-09-29 12:41 ` valdis.kletnieks at vt.edu
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 at vt.edu
2017-10-02 8:11 ` Kamil Konieczny
2017-10-02 11:04 ` valdis.kletnieks at vt.edu [this message]
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=214615.1506942281@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.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 NNTP newsgroup(s).