public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: gmssixty gmssixty <gmssixty@gmail.com>,
	Randy Dunlap <rdunlap@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: How can I add "busybox sh" as init during boot of the custom kernel?
Date: Mon, 23 Oct 2023 18:41:04 +0700	[thread overview]
Message-ID: <ZTZb0AndJBwnAOYT@debian.me> (raw)
In-Reply-To: <CAOx-CDWzJWqYGhoJ4HPhio5-5zE025jYrmVpocryyxMfwfwsxw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 839 bytes --]

On Mon, Oct 23, 2023 at 05:06:38PM +0600, gmssixty gmssixty wrote:
> 
> What would I write in /sbin/init? I mean, what will be the content of
> /sbin/init? Should I write: "exec /bin/busybox sh" in /sbin/init? Or
> should I write "/bin/busybox sh" in /sbin/init?

Since you have Busybox system, /sbin/init should be a symlink to
/bin/busybox.

> 
> BTW, what is top-post?

A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-10-23 11:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-22 23:56 How can I add "busybox sh" as init during boot of the custom kernel? gmssixty gmssixty
2023-10-23  0:14 ` Randy Dunlap
2023-10-23  0:34   ` gmssixty gmssixty
2023-10-23  1:59     ` Randy Dunlap
2023-10-23 11:06       ` gmssixty gmssixty
2023-10-23 11:41         ` Bagas Sanjaya [this message]
2023-10-23 13:34           ` gmssixty gmssixty

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=ZTZb0AndJBwnAOYT@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=gmssixty@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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