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
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 j
> > 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
> 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
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
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.
An
6 matches
Mail list logo