All of lore.kernel.org
 help / color / mirror / Atom feed
From: crosser@average.org (Eugene Crosser)
To: linux-kernel@vger.kernel.org
Subject: Re: [Acpi] Re: ACPI fundamental locking problems
Date: 7 Jul 2001 17:37:52 +0400	[thread overview]
Message-ID: <9i73bg$psv$1@pccross.average.org> (raw)
In-Reply-To: <Pine.GSO.4.21.0107070727030.24836-100000@weyl.math.psu.edu>

In article <Pine.GSO.4.21.0107070727030.24836-100000@weyl.math.psu.edu>,
        Alexander Viro <viro@math.psu.edu> writes:

>> Doesn't the approach "treat a chunk of data built into bzImage as
>> populated ramfs" look cleaner?  No need to fiddle with tar format,
>> no copying data from place to place.
> 
> What the hell _is_ "populated ramfs"? The thing doesn't live in array
> of blocks. Its directory structure consists of a bunch of dentries.

I am stupid.  But the point still stays: having an image of pre-populated
filesystem (some other than ramfs) that you only need to load into
RAM seems more sutable than parsing tar format.  Maybe (probably) I am
missing something.

Eugene

  reply	other threads:[~2001-07-07 13:41 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-04 10:37 [Acpi] Re: ACPI fundamental locking problems Dave J Woolley
2001-07-04 11:03 ` Alan Cox
2001-07-04 17:05   ` Linus Torvalds
2001-07-05  8:20     ` Helge Hafting
2001-07-05  8:34       ` Jeff Garzik
2001-07-05 11:21       ` Alan Cox
2001-07-05 13:42       ` Alexander Viro
2001-07-05 15:17       ` Linus Torvalds
2001-07-06  7:34         ` Benjamin Herrenschmidt
2001-07-06  8:45         ` Helge Hafting
2001-07-06 11:16           ` Alan Cox
2001-07-06 12:42             ` Daniel Phillips
2001-07-09 23:05         ` Pavel Machek
2001-07-07 10:32     ` Eugene Crosser
2001-07-07 11:32       ` Alexander Viro
2001-07-07 13:37         ` Eugene Crosser [this message]
2001-07-07 13:50           ` Jeff Garzik
2001-07-07 17:24             ` Daniel Phillips
2001-07-07 21:31               ` Jamie Lokier
2001-07-07 21:44                 ` Steve VanDevender
2001-07-08  7:26                 ` Alexander Viro
2001-07-08 16:46                   ` Jonathan Lundell
2001-07-09 14:40                 ` Anthony DeBoer
2001-07-07 11:34       ` Jeff Garzik
2001-07-07 21:40         ` Mike Touloumtzis
2001-07-07 21:54           ` Jamie Lokier
2001-07-07 22:00             ` arjan
2001-07-07 22:15               ` Jamie Lokier
2001-07-07 22:04             ` Mike Touloumtzis
2001-07-07 22:14               ` Jamie Lokier
2001-07-08  2:57                 ` Keith Owens
2001-07-12 15:57     ` Eric W. Biederman
2001-07-12 16:14       ` Jeff Garzik
2001-07-12 21:18         ` Eric W. Biederman
  -- strict thread matches above, loose matches on Subject: below --
2001-07-06  5:26 Andreas Dilger

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='9i73bg$psv$1@pccross.average.org' \
    --to=crosser@average.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.