From: David Markey <admin@dmarkey.com>
To: Xen-devel <xen-devel@lists.xensource.com>
Subject: XCP: pygrub missing ext4 support.
Date: Sat, 19 Jun 2010 17:00:57 +0100 [thread overview]
Message-ID: <AANLkTinqjutS_EFILQnpn45ksn2Kkun29Yo8rEkAPPus@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 949 bytes --]
XCP pygrub should have ext4 support.
It currently doesn't because the libfsimage ext2fs-lib module is linked
against libext2fs, which doesnt have ext4 support in XCP.
Instead, XCP should use the ext2fs module that comes with libfsimage, which
has ext4 support.
Most new releases of distributions has it as their default filesystem.
Most notably, Ubuntu 10.04
An easy way for the build to use ext2fs instead of ext2fs-lib, is to not
have ext2fs/ext2fs.h present.
Alternatively this patch hard codes it.
(From 4.0)
--- a/tools/libfsimage/Makefile 2010-06-19 16:52:04.231221516 +0100
+++ b/tools/libfsimage/Makefile 2010-06-19 16:52:08.803250922 +0100
@@ -1,8 +1,7 @@
XEN_ROOT = ../..
include $(XEN_ROOT)/tools/Rules.mk
-SUBDIRS-y = common ufs reiserfs iso9660 fat zfs
-SUBDIRS-y += $(shell env CC="$(CC)" ./check-libext2fs)
+SUBDIRS-y = common ufs reiserfs iso9660 fat zfs ext2fs
.PHONY: all clean install
all clean install: %: subdirs-%
[-- Attachment #1.2: Type: text/html, Size: 1400 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2010-06-19 16:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 16:00 David Markey [this message]
2010-06-19 16:07 ` XCP: pygrub missing ext4 support Pasi Kärkkäinen
2010-06-21 9:59 ` Michal Novotny
2010-06-21 11:26 ` David Markey
2010-06-21 11:29 ` Michal Novotny
2010-06-21 11:38 ` David Markey
2010-06-21 11:48 ` Michal Novotny
2010-06-21 11:55 ` David Markey
2010-06-21 11:58 ` Michal Novotny
2010-06-21 12:44 ` Pasi Kärkkäinen
2010-06-21 13:02 ` Michal Novotny
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=AANLkTinqjutS_EFILQnpn45ksn2Kkun29Yo8rEkAPPus@mail.gmail.com \
--to=admin@dmarkey.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).