From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@sun.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH, RFC] mke2fs: get device topology values from blkid
Date: Fri, 18 Sep 2009 09:30:27 -0500 [thread overview]
Message-ID: <4AB39983.1000001@redhat.com> (raw)
In-Reply-To: <20090918142024.GU2537@webber.adilger.int>
Andreas Dilger wrote:
> On Sep 18, 2009 09:04 -0500, Eric Sandeen wrote:
>> Andreas Dilger wrote:
>>>> + rc = blkid_probe_set_device(pr, fd, 0, 0);
>>> Is this in the e2fsprogs blkid code yet? I'm guessing not, since you
>> right, not yet. I don't know what the long-term plan is for e2fsprogs
>> blkid; keeping 2 trees in sync seems like a lot of work w/o much gain...
>
> I thought that was Ted's plan? We usually recommend people to update to
> the latest e2fsprogs, yet not everyone will be able to upgrade to the
> latest util-linux, especially if it is pulling in other libraries that
> can cause package conflicts (e.g. with xfstools or similar).
It doesn't much matter to me personally since my distro ;) seems pretty
well committed to using the blkid & libuuid now in util-linux-ng.
I guess I'm not thinking too much about a world where people are pulling
down tarballs & doing make install; I'm sure that still goes on but
those folks are smart enough to handle things moving around, or should be.
*shrug*
As long as we can teach the e2fsprogs build to optionally pull libblkid
& libuuid headers from the system rather than the e2fsprogs tree, it'll
give the flexibility we need.
-Eric
next prev parent reply other threads:[~2009-09-18 14:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 22:22 [PATCH, RFC] mke2fs: get device topology values from blkid Eric Sandeen
2009-09-18 5:55 ` Andreas Dilger
2009-09-18 14:04 ` Eric Sandeen
2009-09-18 14:20 ` Andreas Dilger
2009-09-18 14:30 ` Eric Sandeen [this message]
2009-09-18 16:43 ` Theodore Tso
2009-09-18 16:57 ` Eric Sandeen
2009-09-18 6:13 ` Martin K. Petersen
2009-09-18 14:18 ` Andreas Dilger
2009-09-18 14:23 ` Eric Sandeen
2009-09-18 19:40 ` Martin K. Petersen
2009-09-18 20:28 ` Andreas Dilger
2009-09-20 20:46 ` Martin K. Petersen
2009-09-22 14:30 ` Ric Wheeler
2009-09-18 23:59 ` Karel Zak
2009-09-19 3:03 ` Eric Sandeen
2009-09-21 17:06 ` [PATCH V2] " Eric Sandeen
2009-10-02 16:32 ` [PATCH V3] " Eric Sandeen
2009-10-04 19:16 ` Theodore Tso
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=4AB39983.1000001@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@sun.com \
--cc=linux-ext4@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 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.