public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kent Robotti <dwilson24@nyc.rr.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Initramfs and TMPFS!
Date: Fri, 26 Aug 2005 20:08:51 +0000	[thread overview]
Message-ID: <20050826200851.GA851@Linux.nyc.rr.com> (raw)
In-Reply-To: <20050826190647.GA12296@taniwha.stupidest.org>

On Fri, Aug 26, 2005 at 12:06:47PM -0700, Chris Wedgwood wrote:
> On Thu, Aug 25, 2005 at 09:39:15PM -0400, dwilson24@nyc.rr.com wrote:
> 
> > Wouldn't it be better to put overmount_rootfs in initramfs.c
> > and call it only if there's a initramfs?
> 
> I don't see what or how that helps.  Yes we can shuffle some code
> about but the real problem still exists.
> 
> That is is that (by design) the early userspace is unpacked as soon as
> possible before all kernel subsystems are up.

Overmount_rootfs shouldn't take place until you know for sure the
kernel detects an initramfs.

I know the patch only has one purpose and you can assume the user is
using it just for that, but if the user uses the patched kernel without
an initramfs it runs overmount_rootfs anyway.

Also, in shmem.c init_tmpfs isn't run because it assumes that
overmount_rootfs will be, so if the kernel is being used in a
non initramfs way (tmpfs isn't registered). 

   #ifndef CONFIG_EARLYUSERSPACE_ON_TMPFS
   module_init(init_tmpfs)
   #endif /* !CONFIG_EARLYUSERSPACE_ON_TMPFS */

  reply	other threads:[~2005-08-26 19:59 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-26  1:39 Initramfs and TMPFS! dwilson24
2005-08-26 19:06 ` Chris Wedgwood
2005-08-26 20:08   ` Kent Robotti [this message]
2005-08-26 20:22     ` Chris Wedgwood
2005-08-26 21:34       ` Kent Robotti
     [not found]       ` <20050826211231.GA957@Linux.nyc.rr.com>
     [not found]         ` <20050827004045.GA17686@taniwha.stupidest.org>
2005-08-27  3:21           ` Kent Robotti
2005-08-27  4:11             ` Chris Wedgwood
  -- strict thread matches above, loose matches on Subject: below --
2005-09-03  8:29 Chuck Ebbert
2005-08-27  8:19 Kent Robotti
2005-08-27 21:28 ` Chris Wedgwood
2005-08-27 21:42   ` Lee Revell
2005-08-27 22:45   ` Kent Robotti
2005-08-27 22:42     ` David Weinehall
2005-08-27 22:57     ` Patrick McFarland
2005-08-27 23:38     ` Chris Wedgwood
2005-08-27 23:41   ` Alistair John Strachan
2005-08-28  0:21     ` Patrick McFarland
2005-08-28  5:36     ` Willy Tarreau
     [not found] <4Fuuy-6df-11@gated-at.bofh.it>
     [not found] ` <4FJMZ-1YX-17@gated-at.bofh.it>
2005-08-26 15:49   ` Bodo Eggert
2005-08-26  6:09 Kent Robotti
2005-08-25 19:32 dwilson24
2005-08-25 19:05 Alan Jenkins
2005-08-26 10:37 ` Erik Mouw
2005-08-26 19:08 ` Chris Wedgwood
2005-08-25 18:23 robotti
2005-08-25 18:15 robotti
2005-08-25 19:10 ` Ian Campbell
2005-08-26 10:29 ` Erik Mouw
2005-08-25 15:38 robotti
2005-08-25 16:00 ` Erik Mouw
2005-08-26 19:10 ` Chris Wedgwood
2005-08-25 15:34 robotti
2005-08-25 15:54 ` Erik Mouw
2005-08-26 15:03 ` Horst von Brand
2005-08-25  4:35 robotti
2005-08-25 13:49 ` Chris Wedgwood
2005-08-25  4:32 robotti
2005-08-25 13:47 ` Chris Wedgwood
2005-08-24 22:41 robotti
2005-08-25  3:12 ` Chris Wedgwood
2005-08-24  3:15 robotti
2005-08-23 22:05 robotti
2005-08-24  2:57 ` Chris Wedgwood
2005-08-24 20:52   ` Wakko Warner
2005-08-24 20:59     ` Chris Wedgwood
2005-08-23 21:16 robotti
2005-08-23 21:24 ` Olivier Galibert
2005-08-25  3:14 ` Chris Wedgwood

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=20050826200851.GA851@Linux.nyc.rr.com \
    --to=dwilson24@nyc.rr.com \
    --cc=cw@f00f.org \
    --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