mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Werner Almesberger <Werner.Almesberger@epfl.ch>
To: Amit D Chaudhary <amit@muppetlabs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: question \ information request on init \ boot sequence when using initrd
Date: Tue, 27 Mar 2001 08:36:54 +0200	[thread overview]
Message-ID: <20010327083654.E18314@almesberger.net> (raw)
In-Reply-To: <3ABFFDCD.3000803@muppetlabs.com>
In-Reply-To: <3ABFFDCD.3000803@muppetlabs.com>; from amit@muppetlabs.com on Mon, Mar 26, 2001 at 06:41:17PM -0800

Amit D Chaudhary wrote:
> To put it in brief, since running sbin/init from /linuxrc as resulting 
> in init not having PID 1 and thereby not doing some initialization as 
> expected.

Easy solution: don't run linuxrc, run something else instead. E.g.
putting the following into the kernel's command line should do th
trick:
init=/your_script root=/dev/ram

(With your_script being the original version, without real-root-dev)

> Thereby instead of loading running /sbin/init, we just set 
> /proc/sys/kernel/real-root-dev to /dev/ram0's value which then does the 

Anything involving real-root-dev is likely to be an anachronism.
Combining it with pivot_root just makes it more weird.

> Is this ok or should be modify /sbin/init to run properly inspite of PID 
> <> 1 or is there a 3rd way of doing this?

I'd consider the "PID of init must be 1" a bit of an anachronism too.
After all, a modern Unix system has quite a few demons that you don't
want to kill either, so why make init special ? But anyway, you don't
need to change init.

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, ICA, EPFL, CH           Werner.Almesberger@epfl.ch /
/_IN_N_032__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/

  reply	other threads:[~2001-03-27  6:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-27  2:41 Amit D Chaudhary
2001-03-27  6:36 ` Werner Almesberger [this message]
     [not found] <985660830.32357@whiskey.enposte.net>
2001-03-27  4:17 ` Stuart Lynne
2001-03-27  6:32   ` Scott Murray

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=20010327083654.E18314@almesberger.net \
    --to=werner.almesberger@epfl.ch \
    --cc=amit@muppetlabs.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®