Re: fd0 at fdc0 drive 0: density unknown

2017-09-10 Thread bofh 
On Sat, Sep 9, 2017 at 5:58 AM, Stuart Henderson 
wrote:

> On 2017-09-08, Tony Montana  wrote:
> >> booting. I agree that it's a bit ugly, but it makes booting about 5
> seconds
> >> faster.
> >
> > It's not just a bit ugly... It's horrible. It has to go. I'm surprised
> > noone has reverted this crazy change yet.
>
> Disable the floppy drive controller in your VM config then. (I'd be
> surprised if you see this on a physical machine, I can't find any where
> this shows up, even back to the oldest x86 I have in production which
> is from 2002).
>

But but but... that'd require the user to actually think about what they
are doing...

Re: fd0 at fdc0 drive 0: density unknown

2017-09-09 Thread Stuart Henderson 
On 2017-09-08, Tony Montana  wrote:
>> The old behavior was that the kernel would wait after the "fdc0 ..." line 
>> until fd0 attaches. Now it does the waiting in the background and continues 
>> booting. I agree that it's a bit ugly, but it makes booting about 5 seconds 
>> faster.
>
> It's not just a bit ugly... It's horrible. It has to go. I'm surprised
> noone has reverted this crazy change yet.

Disable the floppy drive controller in your VM config then. (I'd be
surprised if you see this on a physical machine, I can't find any where
this shows up, even back to the oldest x86 I have in production which
is from 2002).

Re: fd0 at fdc0 drive 0: density unknown

2017-09-08 Thread Theo de Raadt 
> > The old behavior was that the kernel would wait after the "fdc0 ..." line 
> > until fd0 attaches. Now it does the waiting in the background and continues 
> > booting. I agree that it's a bit ugly, but it makes booting about 5 seconds 
> > faster.
> 
> It's not just a bit ugly... It's horrible. It has to go. I'm surprised
> noone has reverted this crazy change yet.

usb devices attach late all the time also.

Tony, your opinion counts for very little around here -- quite a few
rungs below my cats...

Re: fd0 at fdc0 drive 0: density unknown

2017-09-08 Thread Tony Montana 
> The old behavior was that the kernel would wait after the "fdc0 ..." line 
> until fd0 attaches. Now it does the waiting in the background and continues 
> booting. I agree that it's a bit ugly, but it makes booting about 5 seconds 
> faster.

It's not just a bit ugly... It's horrible. It has to go. I'm surprised
noone has reverted this crazy change yet.

Re: fd0 at fdc0 drive 0: density unknown

2017-09-08 Thread Stefan Fritsch 
On Thursday, 7 September 2017 19:15:31 CEST Arfnokill wrote:
> Using snapshots on amd64. Since two days ago the kernel prints this fd0 at
> fdc0 drive 0: density unknown very late during boot.
> 
> It starts reordering libraries, and BAM... fd0 at fdc0 drive 0: density
> unknown in blue background. It's just cosmetic I guess, but it's
> uncomfortable.
> 
> Anybody else seeing this with recent snapshots?

The old behavior was that the kernel would wait after the "fdc0 ..." line 
until fd0 attaches. Now it does the waiting in the background and continues 
booting. I agree that it's a bit ugly, but it makes booting about 5 seconds 
faster.

fd0 at fdc0 drive 0: density unknown

2017-09-07 Thread Arfnokill 
Using snapshots on amd64. Since two days ago the kernel prints this fd0 at fdc0 
drive 0: density unknown very late during boot.

It starts reordering libraries, and BAM... fd0 at fdc0 drive 0: density unknown 
in blue background. It's just cosmetic I guess, but it's uncomfortable.

Anybody else seeing this with recent snapshots?