Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1092707
| From | Olaf Buddenhagen <olafbuddenhagen@gmx.net> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#481468: memtest86+: Should not run update-grub unconditionally in postinst |
| Date | 2022-02-10 21:40 +0100 |
| Message-ID | <DPooq-VGb-7@gated-at.bofh.it> (permalink) |
| References | <DOy6t-oDg-13@gated-at.bofh.it> <au68W-76N-27@gated-at.bofh.it> <DOy6t-oDg-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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-
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
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
csiph-web