All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH] 30_os-prober: add $onstr ot top level Linux entries too
Date: Sun, 7 Apr 2013 10:34:52 +0400	[thread overview]
Message-ID: <20130407103452.5c22fe2a@opensuse.site> (raw)
In-Reply-To: <516079EC.50609@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]

В Sat, 06 Apr 2013 21:39:24 +0200
Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com> пишет:

> On 05.04.2013 09:30, Andrey Borzenkov wrote:
> 
> > This fixes two issues
> > 
> > 1. It visually distinguishes between multiple installations of the
> > same OS version. Currently all of them get identical titles.
> > 
> 
> I don't know how "speaking" the device names are in practice. They are
> not stable and what is sda1 under one install can be sdb1 under another
> one. Perhaps we should use some other kind of identifier for this.
> 

Well,

a) those names are from the perspective of a single installation only.
In this respect it does not matter how another install calls it.

b) this is already used for some of menu entries. So it is just to
establish consistency. If something better is invented, I am fine with
it, but current situation is inconsistent.

> > 2. linux prober is using "(on /dev/xxx)" as indication that entry has
> > to be skipped. Top level entries should be skipped too.
> 
> This is improper. This string can be translated and e.g. '(на /dev/xxx)'
> or '(auf /dev/xxx)' won't match '(on /dev/xxx)'. "$menuentry_id_option
> 'osprober-" should be used instead (and (on ...) be kept in or-way for
> backward compatibility).
> 

Ah. Did not occur to me, thank you for idea! 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-04-07  6:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05  7:30 [PATCH] 30_os-prober: add $onstr ot top level Linux entries too Andrey Borzenkov
2013-04-06 19:39 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-07  6:34   ` Andrey Borzenkov [this message]
2013-04-10 22:13 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-19 12:15   ` Andrey Borzenkov

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=20130407103452.5c22fe2a@opensuse.site \
    --to=arvidjaar@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 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.