From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Art Boulatov <art@ksu.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: filesystem for initrd
Date: Sat, 10 Mar 2001 19:28:53 -0500 [thread overview]
Message-ID: <3AAAC6C5.EF198D4A@mandrakesoft.com> (raw)
In-Reply-To: <3AAAC179.8020109@ksu.ru>
Art Boulatov wrote:
> I'm in the process of creating a custom "system partition"
> for out Linux servers, which is actually an initial ramdisk,
> coming from hd or network on boot
> to load necessary drivers and perform important checks
> before the real filesystems get mounted,
> and I did not find any info on
> what filesystems can I use
> for initrd, are there any restrictions?
> Mostly interested in cramfs,
> due to it's compression.
Any filesystem which works with a normal block device, such as a hard
drive, will work with a ramdisk. Read ramdisk.txt and initrd.txt in the
linux/Documentation directory, in your Linux kernel source tree.
cramfs is nice but still read-only at the moment... You might be able
to get away with stacking ramfs on top of that. If not, it shouldn't be
hard to modify cramfs so that it allows fs modifications... just stick
the updated pages in RAM until the file is unlinked or the fs is
unmounted.
--
Jeff Garzik | "You see, in this world there's two kinds of
Building 1024 | people, my friend: Those with loaded guns
MandrakeSoft | and those who dig. You dig." --Blondie
next prev parent reply other threads:[~2001-03-11 0:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-11 0:06 filesystem for initrd Art Boulatov
2001-03-11 0:28 ` Jeff Garzik [this message]
2001-03-12 13:51 ` Ingo Oeser
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=3AAAC6C5.EF198D4A@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=art@ksu.ru \
--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