From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Robert Millan <rmh@gnu.org>
Subject: Re: [Patch] Enable libzfs detection on Linux
Date: Thu, 10 Nov 2011 21:39:20 +0100 [thread overview]
Message-ID: <4EBC3678.8070702@gmail.com> (raw)
In-Reply-To: <CAOfDtXP6xNJuEfck7hRskdXJAD0WNpfOqJUc_tnvfhW_qvyf0Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
On 10.11.2011 21:02, Robert Millan wrote:
> Hi Zachary,
>
> 2011/9/14 Zachary Bedell <pendorbound@gmail.com>:
>> FWIW, my commit comment locally for this was:
>> * Adjusts autoconf logic to properly detect libzfs on Linux.
>> * Includes additional headers necessary for libspl.
> Excuse me if I missed something, but weren't you holding the position
> that libzfs ABI was too unstable and relying on it from external
> programs was a bad idea?
>
> Recently Debian has had severe problems in this area because of this.
> C.f. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645305
>
> Last month I sent a proof of concept patch that implements this idea
> (in "getroot for ZFS without libzfs?" thread). Did you see this part
> of the thread?
And I dislike this pseudo device.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2011-11-10 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 17:48 [Patch] Enable libzfs detection on Linux Zachary Bedell
2011-08-18 16:49 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-09-14 18:39 ` Zachary Bedell
2011-11-03 14:51 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-10 20:02 ` Robert Millan
2011-11-10 20:38 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-10 20:39 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-11-15 22:37 ` Seth Goldberg
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=4EBC3678.8070702@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
--cc=rmh@gnu.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.