From: Anthony Liguori <aliguori@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: [PATCH] Add cramfs support to dom0
Date: Thu, 01 Sep 2005 18:29:57 -0500 [thread overview]
Message-ID: <43178EF5.7080201@us.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 268 bytes --]
Add cramfs support to the dom0 kernel (staticly).
I've found cramfs to be very useful for simplifying Xen testing with QEMU.
Also, I imagine cramfs is used frequently for initrds so it's probably a
good
idea to support it out of the box.
Regards,
Anthony Liguori
[-- Attachment #2: 6573_cramfs.diff --]
[-- Type: text/x-patch, Size: 986 bytes --]
# HG changeset patch
# User Anthony Liguori <anthony@codemonkey.ws>
# Node ID 592b1acd3bac146ec31c06dc0ea16ab20b9faf43
# Parent af78c9d526e0b3502629fb0ef09064920157c0c5
Add cramfs support to the dom0 kernel (staticly).
I've found cramfs to be very useful for simplifying Xen testing with QEMU.
Also, I imagine cramfs is used frequently for initrds so it's probably a good
idea to support it out of the box.
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
diff -r af78c9d526e0 -r 592b1acd3bac linux-2.6-xen-sparse/arch/xen/configs/xen0_defconfig_x86_32
--- a/linux-2.6-xen-sparse/arch/xen/configs/xen0_defconfig_x86_32 Thu Sep 1 10:45:50 2005
+++ b/linux-2.6-xen-sparse/arch/xen/configs/xen0_defconfig_x86_32 Thu Sep 1 23:27:02 2005
@@ -1124,7 +1124,7 @@
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
-# CONFIG_CRAMFS is not set
+CONFIG_CRAMFS=y
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2005-09-01 23:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43178EF5.7080201@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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.