public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Otto Wyss <otto.wyss@bluewin.ch>
To: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Booting a modular kernel through a multiple streams file
Date: Thu, 20 Dec 2001 19:47:44 +0100	[thread overview]
Message-ID: <3C22324D.B0DD7A75@bluewin.ch> (raw)
In-Reply-To: <Pine.GSO.4.21.0112161542420.937-100000@weyl.math.psu.edu> <3C1E3E4D.FFCAC861@bluewin.ch> <20011217120749.P855@lynx.no>

> Well "multiple streams file format" is purely a FILESYSTEM issue.  When it
> is outside of the filesystem, it is an ARCHIVE (e.g. tar, cpio, zip, SHA, etc).
> So this whole concept is bogus.
> 
It is a FILESYSTEM issue and an ARCHIVE is simply an implementation of the
"multiple streams file format" (MSFF), with archiving in mind. But it is not at
all bogus as long as it _isn't_ supported directly by the kernel. The MSFF
kernel support has more uses (i.e. transparently accessing anything inside as if
it were a directory). Since it is a kind of fs within an fs it can be easy
accessed from a boot loader regardless of the surrounding fs. I.e. Lilo can
access it regardless if the MSFF is on SCSI raid system, a FAT floppy or a Mac
Zip drive (on i386). 

> > So anybody has to write a kernel module for the cpio/tar format and help
> > with implementing it into  boot loaders. Maybe you could give some help.
> 
> Well, the good news is that this whole discussion is moot.  Al Viro has
> already written a kernel patch which does all of this, and I'm sure he
> is just waiting to get it into the 2.5 kernel.  It creates an "initramfs"
> which is populated from a cpio (or tar, can't remeber) archive attached
> to the kernel image.
> 
When I first read about initramfs I considered it just a slight improvement of
initrd and now after more reading about it, I still think it's not the best
solution. It still has to be loaded somewhere. Well initramfs might be usable
but it is just another special case for the booting process. 

With MSFF the kernel just sees it as an ordinary directory and accesses modules
as if they where ordinary files (maybe within sub directories). The bootloader
first just sees a file and tries to start the stream in it. Depending on how
smart the MSFF is the boot loader does not even need to know the MSFF itself as
long as it is able to start the stream. Otherwise if the MSFF is i.e. a tar
archive even Lilo doesn't need much intelligence to start the kernel within.

O. Wyss

  reply	other threads:[~2001-12-20 18:48 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-16 20:37 Booting a modular kernel through a multiple streams file Otto Wyss
2001-12-16 20:50 ` Alexander Viro
2001-12-17 18:49   ` Otto Wyss
2001-12-17 19:07     ` Andreas Dilger
2001-12-20 18:47       ` Otto Wyss [this message]
2001-12-16 21:06 ` H. Peter Anvin
2001-12-16 22:02   ` antirez
2001-12-16 22:18     ` H. Peter Anvin
2001-12-23  0:08 ` Dave Cinege
2001-12-23  6:26   ` Eric W. Biederman
2001-12-23 13:48   ` Alan Cox
2001-12-23 17:57     ` Dave Cinege
2001-12-23 23:05     ` Marcus Meissner
2001-12-24  2:38       ` Alan Cox
2001-12-27 10:58       ` Wilfried Weissmann
  -- strict thread matches above, loose matches on Subject: below --
2001-12-17 19:53 Grover, Andrew
2001-12-17 20:26 ` Alexander Viro
2001-12-17 22:10 Grover, Andrew
2001-12-18  2:31 ` Alexander Viro
2001-12-18  5:46   ` Craig Christophel
2001-12-23  0:28   ` Dave Cinege
2001-12-23  0:44   ` Dave Cinege
2001-12-23  1:39   ` H. Peter Anvin
2001-12-23  2:10     ` Alexander Viro
2001-12-23  3:00       ` Dave Cinege
2001-12-23  3:52         ` Alexander Viro
2001-12-23  4:41         ` Ryan Cumming
2001-12-23  5:52           ` Dave Cinege
2001-12-23  7:16             ` Bernd Eckenfels
2001-12-23  8:06               ` H. Peter Anvin
2001-12-23 12:22                 ` Kai Henningsen
2001-12-23 20:58                   ` Erik Mouw
     [not found] <Pine.GSO.4.21.0112180350550.6100-100000@weyl.math.psu.edu>
2001-12-18 11:16 ` James A Sutherland
2001-12-18 19:10   ` H. Peter Anvin
2001-12-19  9:27     ` James A Sutherland
2001-12-19 10:11       ` Erik Andersen
2001-12-23  0:39     ` Dave Cinege
2001-12-23  0:42       ` H. Peter Anvin
2001-12-23  1:15         ` Dave Cinege
2001-12-23  1:35           ` H. Peter Anvin
2001-12-23  2:08             ` Alexander Viro
2001-12-18 17:43 Grover, Andrew
2001-12-18 18:45 ` Alexander Viro
2001-12-18 18:49 ` Greg KH
2001-12-18 17:47 Grover, Andrew
2001-12-18 18:53 ` Alexander Viro
2001-12-18 19:43 ` David Weinehall
2001-12-18 19:50 Grover, Andrew
2001-12-18 20:26 ` Alexander Viro
2001-12-18 20:30 ` M. R. Brown
2001-12-18 20:35 ` H. Peter Anvin
2001-12-19  9:34 ` James A Sutherland
2001-12-23  1:02   ` Dave Cinege
2001-12-23  9:10     ` James A Sutherland
2001-12-19 14:13 ` Erik Mouw
2001-12-18 20:35 Torrey Hoffman
     [not found] <Pine.GSO.4.21.0112190313080.9963-100000@weyl.math.psu.edu>
2001-12-19  8:47 ` Eric W. Biederman
2001-12-19 14:55   ` Alexander Viro
2001-12-19 15:49     ` Eric W. Biederman
2001-12-19 17:03       ` Alexander Viro
2001-12-19 19:01         ` Eric W. Biederman
2001-12-20  3:30         ` H. Peter Anvin
2001-12-23  7:20 Grover, Andrew
2001-12-23  9:15 ` Eric W. Biederman
2001-12-23  9:47   ` H. Peter Anvin
2001-12-23 21:24     ` Eric W. Biederman

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=3C22324D.B0DD7A75@bluewin.ch \
    --to=otto.wyss@bluewin.ch \
    --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