Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 23 Sep 2019 20:50:53 +0000
From:      "Poul-Henning Kamp" <phk@phk.freebsd.dk>
To:        Warner Losh <imp@bsdimp.com>
Cc:        lausts@acm.org, FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: Booting anything after r352057 kills console
Message-ID:  <18606.1569271853@critter.freebsd.dk>
In-Reply-To: <CANCZdfr5TPUX9uvmbm7oFPBTO7rgBGg-Rb0PcOjt-1-gL8et=g@mail.gmail.com>
References:  <11db909b-57ee-b452-6a17-90ec2765c36e@acm.org> <18332.1569268545@critter.freebsd.dk> <CANCZdfr5TPUX9uvmbm7oFPBTO7rgBGg-Rb0PcOjt-1-gL8et=g@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--------
In message <CANCZdfr5TPUX9uvmbm7oFPBTO7rgBGg-Rb0PcOjt-1-gL8et=3Dg@mail.gma=
il.com>
, Warner Losh writes:

>We are working on making drm ports less problematic on upgrade...

Yes, I know.

But when you track current, it seems that it takes a port-reinstall
to get on that wagon...

-- =

Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    =

Never attribute to malice what can adequately be explained by incompetence=
.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18606.1569271853>