All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
	John Levon <levon@movementarian.org>
Subject: RE: [PATCH 1/2] libfsimage
Date: Mon, 30 Oct 2006 14:12:43 +0000	[thread overview]
Message-ID: <1162217563.6230.54.camel@sisko.scot.redhat.com> (raw)
In-Reply-To: <8A87A9A84C201449A0C56B728ACF491E932D@liverpoolst.ad.cl.cam.ac.uk>

Hi,

On Mon, 2006-10-30 at 11:58 +0000, Ian Pratt wrote:

> > The downside is that it no longer picks up updates, fixes 
> > etc. from the official upstream support for libext2fs / 
> > libreiserfs, so we're just duplicating the places where 
> > filesystem support needs to be maintained.
> 
> [Apparently, libresierfs is moribund and doesn't actually support
> current v3 filesystems anyhow. We need to look at other ways of pulling
> kernels out.]

Ugh.  So is pygrub non-functional on Novell/SuSE systems on reiserfs?
Or are they using a patched libreiserfs?

> As I understand it, John's scheme doesn't necessarily prevent using the
> existing libraries -- you could have external binaries linked against
> the existing libraries, or you could choose to statically link if your
> distro didn't normally include those libraries.

Well, the patches as presented moved all the reiser/ext2 knowledge into
pygrub itself.  I'm certainly not opposed to changes to the pygrub
interface, just to unnecessary replicating of fs-specific code inside
the Xen tools.

Cheers,
 Stephen

  reply	other threads:[~2006-10-30 14:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-30 11:58 [PATCH 1/2] libfsimage Ian Pratt
2006-10-30 14:12 ` Stephen C. Tweedie [this message]
2006-10-30 14:35   ` Gerd Hoffmann
2006-10-30 14:53   ` John Levon
  -- strict thread matches above, loose matches on Subject: below --
2006-10-30 14:20 Ian Pratt
2006-10-30 15:02 ` John Levon
2006-11-03 23:09   ` Stephen C. Tweedie
2006-10-27 18:58 John Levon
2006-10-30 11:14 ` Stephen C. Tweedie
2006-10-30 12:31   ` John Levon
2006-10-30 14:08     ` Stephen C. Tweedie
2006-10-30 14:59       ` John Levon
2006-10-31  9:54 ` Tim Deegan
2006-10-31 13:14   ` John Levon

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=1162217563.6230.54.camel@sisko.scot.redhat.com \
    --to=sct@redhat.com \
    --cc=Ian.Pratt@cl.cam.ac.uk \
    --cc=levon@movementarian.org \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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.