Re: Installer - add BIOS boot partition?
Lennart Sorensen (2019-01-14):
> Hmm, I recall having it give a checklist in the past, but I could be
> remembering wrong.
>
> Certainly if I run dpkg-reconfigure grub-pc, it offers me a checklist
> of which devices to install grub on, so having both sda and sdb
> selected works fine.
If you go for a manual list, space-separated "/dev/sda /dev/sdb" works
just fine.
This is likely “grub-pc grub-pc/install_devices multiselect” in debconf
(but please double check!).
Checking grub2, this is very likely:
,---[ debian/grub-pc.templates.in ]---
| Template: grub-pc/install_devices
| Type: multiselect
| Choices-C: ${RAW_CHOICES}
| Choices: ${CHOICES}
| _Description: GRUB install devices:
| The grub-pc package is being upgraded. This menu allows you to select which
| devices you'd like grub-install to be automatically run for, if any.
| .
| Running grub-install automatically is recommended in most situations, to
| prevent the installed GRUB core image from getting out of sync with GRUB
| modules or grub.cfg.
| .
| If you're unsure which drive is designated as boot drive by your BIOS, it is
| often a good idea to install GRUB to all of them.
| .
| Note: it is possible to install GRUB to partition boot records as well, and
| some appropriate partitions are offered here. However, this forces GRUB to
| use the blocklist mechanism, which makes it less reliable, and therefore is
| not recommended.
`---
Cheers,
--
Cyril Brulebois (k...@debian.org)
Processed: [bts-link] source package src:busybox
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:busybox > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #918846 (http://bugs.debian.org/918846) > # Bug title: busybox: CVE-2018-20679 > # * https://bugs.busybox.net/show_bug.cgi?id=11506 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 918846 + fixed-upstream Bug #918846 [src:busybox] busybox: CVE-2018-20679 Added tag(s) fixed-upstream. > usertags 918846 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > thanks Stopping processing here. Please contact me if you need assistance. -- 918846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918846 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Installer - add BIOS boot partition?
On Sat, Jan 12, 2019 at 05:55:50PM +1300, Richard Hector wrote: > Ok - as long as I remember to install to both. There's no option to > install to both in one invocation, is there? Or a config file that > records which drives are/might be used for booting? Hmm, I recall having it give a checklist in the past, but I could be remembering wrong. Certainly if I run dpkg-reconfigure grub-pc, it offers me a checklist of which devices to install grub on, so having both sda and sdb selected works fine. -- Len Sorensen
[bts-link] source package src:busybox
# # bts-link upstream status pull for source package src:busybox # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #918846 (http://bugs.debian.org/918846) # Bug title: busybox: CVE-2018-20679 # * https://bugs.busybox.net/show_bug.cgi?id=11506 # * remote status changed: (?) -> RESOLVED # * remote resolution changed: (?) -> FIXED # * closed upstream tags 918846 + fixed-upstream usertags 918846 + status-RESOLVED resolution-FIXED thanks
Re: UEFI Secure Boot changes in d-i and live images
On Sun, Jan 13, 2019 at 07:23:43PM +, Steve McIntyre wrote: > Hi folks, Hi Steve, > I've just pushed changes to a few bits of d-i this weekend to make SB > work for amd64: Epic!! This is fantastic news :) > The effect of these changes is that the next daily and weekly debian > installer images (tomorrow) should Just Work (TM) end-to-end with UEFI > Secure Boot. The changes to efi-image also mean that our next live > image builds will do SB (for live and installation). > > I'll test all these again in the next couple of days to verify that > things have pulled through as I expect, then it's time to post to > d-d-a and write a blog too. We've made great progress already. These > last changes just tie it all together for end users. I've just given a try to the build of this night on my locked-down-beyond-any-doubt laptop. It does not boot but it gets to the grub menu (see attached picture) going throught the shim (I see a "Botting in insecure mode" along the way). I think that w.r.t EFI SB, it's all fine. Thank you to everybody involved in this more bit of freedom. Kind regards, Domenico -- 3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13 signature.asc Description: PGP signature
