From: Mihai Moldovan <ionic@ionic.de>
To: The development of GNU GRUB <grub-devel@gnu.org>,
Daniel Kiper <dkiper@net-space.pl>,
Jeff Norden <jeff@math.tntech.edu>
Subject: Re: Proposed PATCH to allow control of the kernel ordering in grub.cfg
Date: Fri, 21 Dec 2018 06:20:34 +0100 [thread overview]
Message-ID: <8901df9b-4333-caac-5153-0dd888079134@ionic.de> (raw)
In-Reply-To: <20181220115349.sza6zil6zn7n43wg@tomti.i.net-space.pl>
[-- Attachment #1.1: Type: text/plain, Size: 1162 bytes --]
* On 12/20/18 12:53 PM, Daniel Kiper wrote:
>> diff --git a/util/grub.d/10_linux.in b/util/grub.d/10_linux.in
>> index 4532266be..f2dea11e9 100644
>> --- a/util/grub.d/10_linux.in
>> +++ b/util/grub.d/10_linux.in
>> @@ -193,7 +193,14 @@ submenu_indentation=""
>>
>> is_top_level=true
>> while [ "x$list" != "x" ] ; do
>> - linux=`version_find_latest $list`
>> + linux=""
>> + if [ "x${GRUB_PREFERRED_KERNEL}" != "x" ]; then
>> + linux=`echo $list | tr ' ' '\n' | grep "${GRUB_PREFERRED_KERNEL}" | tr '\n' ' '`
>
> s/grep/egrep/?
Just a tiny nit: egrep/fgrep have been deprecated in POSIX/SUS.
Initially, egrep, fgrep and grep were different programs (the rationale for that
being that the original implementers didn't find a way to come up with a
[space/time] efficient generic algorithm usable for all three variants), but
subsequent grep standard specifications were written with the same functionality
exposed via the -E and -F flags.
Unless you really want to target ancient platforms, I'd try to go for grep -E/-F
instead, even if typically egrep/fgrep will stay around as symlinks for quite a
long time.
Mihai
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 898 bytes --]
next prev parent reply other threads:[~2018-12-21 5:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 6:50 Proposed PATCH to allow control of the kernel ordering in grub.cfg Jeff Norden
2018-12-20 11:53 ` Daniel Kiper
2018-12-21 5:20 ` Mihai Moldovan [this message]
2018-12-21 0:26 ` Jeff Norden
2018-12-27 14:23 ` Jeff Norden
2018-12-31 8:09 ` Mihai Moldovan
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=8901df9b-4333-caac-5153-0dd888079134@ionic.de \
--to=ionic@ionic.de \
--cc=dkiper@net-space.pl \
--cc=grub-devel@gnu.org \
--cc=jeff@math.tntech.edu \
/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.