public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakob Oestergaard <jakob@unthought.net>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: argv0 revisited...
Date: Thu, 16 Jan 2003 15:59:08 +0100	[thread overview]
Message-ID: <20030116145908.GF8621@unthought.net> (raw)
In-Reply-To: <b04dqu$4f5$1@ncc1701.cistron.net>

On Wed, Jan 15, 2003 at 07:46:38PM +0000, Miquel van Smoorenburg wrote:
> In article <20030115191942.GD47@DervishD>,
> DervishD  <raul@pleyades.net> wrote:
> >> > of init. Remember, is not any program, is an init. Should be a more
> >> > clean way, I suppose :??
> >> I don't think is that big a deal ... if you startup the system normally,
> >> sooner or later, /proc is going to be mounted. A [quickie] variation is:
> >
> >    Yes, I know, and that's one option, but I would like to avoid the
> >mounting. Not a big deal, anyway, as you say. The only thing is that
> >it won't work in kernels without proc enabled (yes, there are people
> >without 'proc', size issues, I suppose, etc...).
> 
> I assume that init is passed on the kernel command line like
> init=/what/ever, right ?
> 
> Why not make that INIT=/what/ever, then make this /sbin/init:

Why not make a kernel patch that sets the INIT environment variable for
the init process ?

-- 
................................................................
:   jakob@unthought.net   : And I see the elder races,         :
:.........................: putrid forms of man                :
:   Jakob Østergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............:

  parent reply	other threads:[~2003-01-16 14:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15 18:51 argv0 revisited Perez-Gonzalez, Inaky
2003-01-15 19:19 ` DervishD
2003-01-15 19:46   ` Miquel van Smoorenburg
2003-01-15 20:22     ` DervishD
2003-01-16 14:59     ` Jakob Oestergaard [this message]
2003-01-17 10:55       ` DervishD
  -- strict thread matches above, loose matches on Subject: below --
2003-01-15 18:22 Perez-Gonzalez, Inaky
2003-01-15 18:44 ` DervishD
2003-01-16 11:04   ` Horst von Brand
2003-01-16 11:27     ` DervishD
2003-01-17 10:51       ` Rogier Wolff
2003-01-17 11:20         ` DervishD
     [not found]       ` <200301161603.h0GG3DX0001895@eeyore.valparaiso.cl>
2003-01-17 10:58         ` DervishD
2003-01-15 18:17 DervishD

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=20030116145908.GF8621@unthought.net \
    --to=jakob@unthought.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miquels@cistron.nl \
    /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