Hello all,
On Fri, 19 Apr 2019 13:17:32 +0100 Steve McIntyre wrote:
*In the installer*, we're not seeing *any* "change" events for the
hard disk (vda in my case), in either stretch or buster. We just get
the "add" and "remove" events. In the buster installer, my temporary
hack of forcing the "
Hey folks,
On Sun, Apr 07, 2019 at 01:01:34AM +0100, Ben Hutchings wrote:
>On Sat, 2019-04-06 at 16:54 +0100, Steve McIntyre wrote:
>> Actually...
>>
>> On Sat, Apr 06, 2019 at 04:36:59PM +0100, Steve McIntyre wrote:
>> > We need to run update-dev *after* the filesystem creation scripts and
>> >
On Sat, 2019-04-06 at 16:54 +0100, Steve McIntyre wrote:
> Actually...
>
> On Sat, Apr 06, 2019 at 04:36:59PM +0100, Steve McIntyre wrote:
> > We need to run update-dev *after* the filesystem creation scripts and
> > this fixes things. I've just copiet it to 99update-dev locally while
> > testing
On Tue, Jan 15, 2019 at 04:29:36PM +, Steve McIntyre wrote:
>I've let this slip off my radar since, and it's not gone away.
>
>I'm seeing this problem really obviously with live installations now,
>as I've just been testing them with Secure Boot.
>
>Hoping to play with this more in the next few
Actually...
On Sat, Apr 06, 2019 at 04:36:59PM +0100, Steve McIntyre wrote:
>
>We need to run update-dev *after* the filesystem creation scripts and
>this fixes things. I've just copiet it to 99update-dev locally while
>testing and that made all the difference. It could probably also just
>be move
I've let this slip off my radar since, and it's not gone away.
I'm seeing this problem really obviously with live installations now,
as I've just been testing them with Secure Boot.
Hoping to play with this more in the next few days...
On Tue, Jul 25, 2017 at 11:33:36PM +0100, Steve McIntyre wro
A discussion with Steve suggested looking at when udev updates
/dev/disk/by-uuid - has something changed that stops that directory
being refreshed after partman-base is done (or at least before
bootstrap-base starts)?
I ran some stretch/jessie comparison installs on the following VM system:
amd
We noticed this issue today and there is a further aspect to it.
I won't have time to make a proper bug report for a couple of days.
The initrd path that was given to the pxe netboot installer
gets included in the boot command line, to wit:
GRUB_CMDLINE_LINUX="initrd=::debian/stretch/amd64/de
the promised attachment, inline
uname -a: Linux testbox 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u2
(2017-06-26) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Skylake Host
Bridge/DRAM Registers [8086:191f] (rev 07)
lspci -knn: Subsystem: Dell Device [1028:06b9]
l
On Fri, Jul 28, 2017 at 12:28:58PM +1000, Vincent McIntyre wrote:
> the promised attachment, inline
A perusal of the syslog turned up this
A perusal of the syslog turned up this
Jul 28 01:27:32 grub-installer: info: Installing grub on '/dev/sdc'
Jul 28 01:27:32 grub-installer: info: grub-instal
Hey folks,
Leif (in CC) pointed this out to me after he did a fresh Stretch
installation over the weekend. I've just verified the problem
myself. Our initial thought was that this might be specific to
installations onto NVME, but I've tested and it's not, it's generic.
Right at the end of a simpl
11 matches
Mail list logo
