From: Richard Laager <rlaager@wiktel.com>
To: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
Cc: grub-devel@gnu.org, Zachary Bedell <pendorbound@gmail.com>
Subject: Re: [Patch] Robustly search for ZFS labels & uberblocks
Date: Thu, 02 Feb 2012 05:13:13 -0600 [thread overview]
Message-ID: <1328181193.3572.71.camel@watermelon.coderich.net> (raw)
In-Reply-To: <1327999542.3471.20.camel@watermelon.coderich.net>
[-- Attachment #1.1: Type: text/plain, Size: 68 bytes --]
Attached are two more patches to add to the stack.
--
Richard
[-- Attachment #1.2: zfs-on-linux-rlaager10.patch --]
[-- Type: text/x-patch, Size: 548 bytes --]
Index: grub/util/grub-probe.c
===================================================================
--- grub.orig/util/grub-probe.c 2012-02-02 03:36:38.827815635 -0600
+++ grub/util/grub-probe.c 2012-02-02 03:39:22.727085000 -0600
@@ -323,6 +323,11 @@
if (path != NULL)
{
grub_path = canonicalize_file_name (path);
+ if (! grub_path)
+ {
+ grub_util_error (_("failed to get canonical path of %s"), path);
+ return;
+ }
device_names = grub_guess_root_devices (grub_path);
free (grub_path);
}
[-- Attachment #1.3: zfs-on-linux-rlaager11.patch --]
[-- Type: text/x-patch, Size: 572 bytes --]
Index: grub/util/grub-probe.c
===================================================================
--- grub.orig/util/grub-probe.c 2012-02-02 04:04:16.154167324 -0600
+++ grub/util/grub-probe.c 2012-02-02 04:07:11.916090000 -0600
@@ -363,6 +363,16 @@
}
*curdrive = 0;
+ if (print == PRINT_DRIVE)
+ {
+ for (curdrive = drives_names; *curdrive; curdrive++)
+ {
+ printf ("(%s)", *curdrive);
+ putchar (delim);
+ }
+ return;
+ }
+
if (print == PRINT_FS || print == PRINT_FS_UUID
|| print == PRINT_FS_LABEL)
{
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-02-02 11:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 18:45 [Patch] Robustly search for ZFS labels & uberblocks Zachary Bedell
2011-09-28 21:20 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-01-19 11:36 ` Richard Laager
2012-01-22 14:18 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-01-22 20:31 ` Richard Laager
2012-01-24 7:12 ` Richard Laager
2012-01-27 19:04 ` Zachary Bedell
2012-01-27 22:22 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-01-28 2:50 ` Richard Laager
2012-01-28 12:51 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-01-28 16:50 ` Richard Laager
2012-01-28 17:06 ` Darik Horn
2012-01-28 17:39 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-01-28 18:33 ` Richard Laager
2012-01-28 19:21 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-01-29 22:42 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-01-31 8:45 ` Richard Laager
2012-02-02 11:13 ` Richard Laager [this message]
2012-02-03 10:02 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-02-03 9:52 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-02-03 11:20 ` Richard Laager
2012-01-28 18:40 ` Darik Horn
2012-01-28 19:27 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-01-30 1:22 ` Richard Laager
2012-01-30 1:43 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-03 14:45 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=1328181193.3572.71.camel@watermelon.coderich.net \
--to=rlaager@wiktel.com \
--cc=grub-devel@gnu.org \
--cc=pendorbound@gmail.com \
--cc=phcoder@gmail.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).