public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nscott@aconex.com>
To: Thomas Tsai <thomas@nchc.org.tw>
Cc: xfs@oss.sgi.com
Subject: Re: Build xfs 3.0 deb problem
Date: Wed, 8 Apr 2009 14:10:14 +1000 (EST)	[thread overview]
Message-ID: <430737146.3196421239163814099.JavaMail.root@mail-au.aconex.com> (raw)
In-Reply-To: <20090408115648.efaee933.thomas@nchc.org.tw>


----- "Thomas Tsai" <thomas@nchc.org.tw> wrote:

> tkx for reply soon.
> 
> My package name is partclone(partclone.org), like partimage, but I

Sounds like xfs_copy(8)?

> used libxfs to check bitmap/super block and backup xfs partition. It's
> GPL licensed.
> 
> We need GPL tool to backup XFS partition. The partimage can do that
> but get some problems(not based on the xfs library).
> The xfs library you maintained well, and it's why I use xfslibs-dev's
> liarbry to write backup tool, "partclone.xfs" .

Can this use xfs_copy directly?

> so..., may I use xfslibs-dev to build partclone?
> or stop it and remove?

Its historically proved disasterous having ondisk filesystem knowledge
in tools (e.g. grub) ... and restricts what filesystem developers can
do in terms of extending their ondisk formats, somewhat.  It'd be alot
better if you could use a tool shipped by the XFS folk rather than one
you write yourself (libxfs is a very error prone interface modelled on
kernel code, it wasn't designed as a general purpose API).

cheers.

-- 
Nathan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2009-04-08  4:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08  2:05 Build xfs 3.0 deb problem Thomas Tsai
2009-04-08  2:46 ` Nathan Scott
2009-04-08  3:56   ` Thomas Tsai
2009-04-08  4:10     ` Nathan Scott [this message]

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=430737146.3196421239163814099.JavaMail.root@mail-au.aconex.com \
    --to=nscott@aconex.com \
    --cc=thomas@nchc.org.tw \
    --cc=xfs@oss.sgi.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