From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [RFC] Support for UEFI ESP in os-prober
Date: Fri, 31 May 2013 18:12:56 +0200 [thread overview]
Message-ID: <51A8CC08.8060303@gmail.com> (raw)
In-Reply-To: <20130531184843.235759e8@opensuse.site>
[-- Attachment #1: Type: text/plain, Size: 2176 bytes --]
On 31.05.2013 16:48, Andrey Borzenkov wrote:
> В Mon, 1 Oct 2012 13:25:50 +0200
> "Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com> пишет:
>
>> I haven‘t had time to view in details but os-prober isn‘t managed by us but
>> by debian-boot team so you need to contact them. Also I‘d prefer more of
>> detection to be done on runtime than it‘s done in current model
>
> In the meantime os-prober part is integrated in Debian as of 1.58.
> The patch adds missing part from grub2 side. How does it look like?
>
Go ahead. I must say I'm generally disappointed with os-prober and have
ideas to move away from it. I'll start another topic for it.
> ---
> ChangeLog | 5 +++++
> util/grub.d/30_os-prober.in | 16 ++++++++++++++++
> 2 files changed, 21 insertions(+)
>
> diff --git a/ChangeLog b/ChangeLog
> index e9ef17e..798369d 100644
> --- a/ChangeLog
> +++ b/ChangeLog
> @@ -1,3 +1,8 @@
> +2013-05-31 Andrey Borzenkov <arvidjaar@gmail.com>
> +
> + * util/grub.d/30_os-prober.in: Add support for probing EFI
> + System Partition (as of os-prober 1.58).
> +
> 2013-05-30 Josh Triplett <josh@joshtriplett.org>
>
> * grub-core/normal/cmdline.c (grub_cmdline_get): Fix Ctrl-u
> diff --git a/util/grub.d/30_os-prober.in b/util/grub.d/30_os-prober.in
> index 04f32a1..5e3c5d8 100644
> --- a/util/grub.d/30_os-prober.in
> +++ b/util/grub.d/30_os-prober.in
> @@ -149,6 +149,22 @@ EOF
> }
> EOF
> ;;
> + efi)
> +
> + EFIPATH=${DEVICE#*@}
> + DEVICE=${DEVICE%@*}
> + onstr="$(gettext_printf "(on %s)" "${DEVICE}")"
> + cat << EOF
> +menuentry '$(echo "${LONGNAME} $onstr" | grub_quote)' --class windows --class os \$menuentry_id_option 'osprober-efi-$(grub_get_device_id "${DEVICE}")' {
> +EOF
> + save_default_entry | sed -e "s/^/\t/"
> + prepare_grub_to_access_device ${DEVICE} | sed -e "s/^/\t/"
> +
> + cat <<EOF
> + chainloader ${EFIPATH}
> +}
> +EOF
> + ;;
> linux)
> if [ "x$BTRFS" = "xbtrfs" ]; then
> LINUXPROBED="`linux-boot-prober btrfs ${BTRFSuuid} ${BTRFSsubvol} 2> /dev/null | tr ' ' '^' | paste -s -d ' '`"
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
next prev parent reply other threads:[~2013-05-31 16:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-29 15:04 [RFC] Support for UEFI ESP in os-prober Andrey Borzenkov
2012-09-30 20:30 ` yannubuntu
2012-10-01 11:25 ` Vladimir 'phcoder' Serbinenko
2013-05-31 14:48 ` Andrey Borzenkov
2013-05-31 16:12 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-05-31 17:03 ` Bruce Dubbs
2013-05-31 17:55 ` Chris Murphy
2013-06-05 15:56 ` Mads Kiilerich
2013-06-05 16:56 ` Andrey Borzenkov
2013-06-05 17:21 ` Bruce Dubbs
2013-06-05 17:58 ` Andrey Borzenkov
2013-06-05 18:43 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-06-05 18:53 ` Bruce Dubbs
2013-06-05 19:03 ` Andrey Borzenkov
2013-06-05 19:29 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-06-05 17:51 ` Vladimir 'φ-coder/phcoder' Serbinenko
[not found] <mailman.26139.1370458399.22519.grub-devel@gnu.org>
2013-06-06 15:33 ` Tom Davies
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=51A8CC08.8060303@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@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 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).