public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miles Bader <miles@gnu.org>
To: "Bryan O'Sullivan" <bos@serpentine.com>
Cc: Miles Bader <miles@gnu.org>,
	Chris Meadors <clubneon@hereintown.net>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: initramfs howto?
Date: Fri, 9 Apr 2004 20:50:42 -0400	[thread overview]
Message-ID: <20040410005042.GF7497@fencepost> (raw)
In-Reply-To: <1081531299.19918.13.camel@serpentine.pathscale.com>

On Fri, Apr 09, 2004 at 10:21:39AM -0700, Bryan O'Sullivan wrote:
> > If so, it'd be nice if it checked for some other name than /init
> > (e.g. /sbin/init) -- there's too much crap in / already.
> 
> I'm agnostic.  It's a two-line patch.  I don't care if it's called
> /spam/fandango/wubble, so long as the brave souls who are trying out
> initramfs don't keep stumbling over the same problem again and again :-)

Indeed; I just wanna raise the point before people start actually using /init
in large numbers...

I wonder if you could move the bulk of stuff (the console open, the calls to
run_init_proces) that happens after prepare_namespace into a separate
function and attempt to call it both before and after prepare_namespace; the
problem seems to be the unlock_kernel &c., which I gather must be done after
prepare_namespace?

-Miles
-- 
I'm beginning to think that life is just one long Yoko Ono album; no rhyme
or reason, just a lot of incoherent shrieks and then it's over.  --Ian Wolff

  reply	other threads:[~2004-04-10  0:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 19:17 initramfs howto? Chris Meadors
2004-04-09  5:56 ` Bryan O'Sullivan
2004-04-09  6:48   ` Miles Bader
2004-04-09 17:21     ` Bryan O'Sullivan
2004-04-10  0:50       ` Miles Bader [this message]
2004-04-19 19:48       ` Chris Lingard
2004-04-19 21:39         ` H. Peter Anvin

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=20040410005042.GF7497@fencepost \
    --to=miles@gnu.org \
    --cc=akpm@osdl.org \
    --cc=bos@serpentine.com \
    --cc=clubneon@hereintown.net \
    --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