Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1092438 > unrolled thread

Bug#481468: memtest86+: Should not run update-grub unconditionally in postinst

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#481468: memtest86+: Should not run update-grub unconditionally in postinst Fabio Fantoni <fantonifabio@tiscali.it> - 2022-02-08 13:50 +0100
    Bug#481468: memtest86+: Should not run update-grub unconditionally in postinst Olaf Buddenhagen <olafbuddenhagen@gmx.net> - 2022-02-10 21:40 +0100
      Bug#481468: memtest86+: Should not run update-grub unconditionally in postinst Fabio Fantoni <fantonifabio@tiscali.it> - 2022-02-10 23:40 +0100

#1092438 — Bug#481468: memtest86+: Should not run update-grub unconditionally in postinst

[Multipart message — attachments visible in raw view] — view raw

Hi, /etc/kernel-img.conf seems specific options related to kernel so I 
don't think is good do some additional condition based on it, I don't 
know other similar option that can be used out of this.

If there are other possibilities or the problem is relevant please tell 
me I will reconsider it.

[toc] | [next] | [standalone]

#1092707

Hi,

On Tue, Feb 08, 2022 at 01:39:58PM +0100, Fabio Fantoni wrote:

> Hi, /etc/kernel-img.conf seems specific options related to kernel so I don't
> think is good do some additional condition based on it, I don't know other
> similar option that can be used out of this.

Well, first of all, I'm using update-grub nowadays -- so I don't
personally care any more... To be honest, I didn't even remember filing
this issue back then :-)

Fundamentally, memtest behaves largely like a kernel image for most
intents and purposes -- so using options from /etc/kernel-img.conf would
make sense in principle... However, the options in question for
disabling update-grub etc. seem to have been dropped altogether: which I
guess is the source of the confusion here -- best I can tell, this bug
is simply obsolete at this point...

-antrik-

[toc] | [prev] | [next] | [standalone]

#1092718

[Multipart message — attachments visible in raw view] — view raw

Il 10/02/2022 21:35, Olaf Buddenhagen ha scritto:
> Hi,
>
> On Tue, Feb 08, 2022 at 01:39:58PM +0100, Fabio Fantoni wrote:
>
>> Hi, /etc/kernel-img.conf seems specific options related to kernel so I don't
>> think is good do some additional condition based on it, I don't know other
>> similar option that can be used out of this.
> Well, first of all, I'm using update-grub nowadays -- so I don't
> personally care any more... To be honest, I didn't even remember filing
> this issue back then :-)
>
> Fundamentally, memtest behaves largely like a kernel image for most
> intents and purposes -- so using options from /etc/kernel-img.conf would
> make sense in principle... However, the options in question for
> disabling update-grub etc. seem to have been dropped altogether: which I
> guess is the source of the confusion here -- best I can tell, this bug
> is simply obsolete at this point...
>
> -antrik-

Thanks for your reply, I recently become the new maintainer and am 
reviewing all open bugs.

This bug report even if is near 14 years old and the proposed 
modification did not seem optimal to me it still seemed good to ask to 
be sure if the problem persisted.

Since the proposed option has been dropped and the problem is no longer 
relevant, I close the bug.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web