Bug#882766: Proposal: reinstate automated device selection, blacklisting d-i?

[Cyril Brulebois]

Package: grub-installer
Severity: important

Hi,

If records/recollection are correct, we've been prompting for the boot
device to install grub on since this upload:
| grub-installer (1.86) unstable; urgency=low
| 
|   [ Vincent McIntyre ]
|   * Support menu selection of GRUB boot disk. Closes: #706112
| 
|  -- Cyril Brulebois   Mon, 29 Apr 2013 13:53:27 +0200


One of the reasons was that there seemed to be no reliable way to detect
what device we've booted the installer from, and we've had issues with
wiping the d-i installation images for several years before that upload.

Proposal: restore the old device detection, and blacklist anything that
seems to be holding a Debian Installer image. Beware: we don't want to
trigger the same side effects as os-prober did (see os-prober uploads
between 1.72 and 1.75). One way to avoid the read-only mounting could be
to ensure a given token is present in a certain location of Debian
installation images.

Feedback welcome!


KiBi.

Re: Aaargh - 5 files could not be downloaded.

[Steve McIntyre]

On Sat, Nov 25, 2017 at 08:52:02PM -0200, Thiago Feijó wrote:
>When downloading debian-9.2.1-amd64-DVD-4.template via jigdo, this error
>occurs:
>
>Aaargh - 5 files could not be downloaded. This should not
>happen! Depending on the problem, it may help to retry downloading
>the missing files.
>
>What is the resolution?

Hi Thiago,

Checking now, things work OK for me. What mirror are you using with
jigdo, if any?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"...In the UNIX world, people tend to interpret `non-technical user'
 as meaning someone who's only ever written one device driver." -- Daniel Pead