Hi!
> With a recent change I made for UEFI, we now install loader.efi onto the ESP
> and don???t run boot1. That means that /boot.config is no longer read, and so
> console settings need to be put in /boot/loader.conf
Which change is that ?
> I was wondering if people will expect /boot.config
On Thu, Jan 17, 2019, 7:33 PM Rebecca Cran
> With a recent change I made for UEFI, we now install loader.efi onto the
> ESP and don’t run boot1. That means that /boot.config is no longer read,
> and so console settings need to be put in /boot/loader.conf.
> I was wondering if people will expect
On Thu, Jan 17, 2019 at 07:31:38PM -0700, Rebecca Cran wrote:
>
> With a recent change I made for UEFI, we now install loader.efi onto the ESP
> and don’t run boot1. That means that /boot.config is no longer read, and so
> console settings need to be put in /boot/loader.conf.
> I was wondering
With a recent change I made for UEFI, we now install loader.efi onto the ESP
and don’t run boot1. That means that /boot.config is no longer read, and so
console settings need to be put in /boot/loader.conf.
I was wondering if people will expect /boot.config to still be read and so code
should
On Thu, Jan 17, 2019 at 03:53:03PM +0100, Trond Endrestøl wrote:
> On Thu, 17 Jan 2019 04:49-0800, David Wolfskill wrote:
>
> > On Thu, Jan 17, 2019 at 03:37:16PM +0300, Lev Serebryakov wrote:
> ...
> > > I can not build CURRENT r343111 on r343022 world. Looks like r343111
> > > itself cause
On Thu, 17 Jan 2019 15:53+0100, Trond Endrestøl wrote:
> Try the attached patch, [...]
I fail to see how r343113 actually fixes r343111.
Attached patch augments and corrects the changes done in r343113.
--
Trond.Index: contrib/libc++/include/errno.h
On Thu, 17 Jan 2019 04:49-0800, David Wolfskill wrote:
> On Thu, Jan 17, 2019 at 03:37:16PM +0300, Lev Serebryakov wrote:
> >
> > I can not build CURRENT r343111 on r343022 world. Looks like r343111
> > itself cause problems (r343110 builds):
> >
> > In file included from
On Thu, Jan 17, 2019 at 03:37:16PM +0300, Lev Serebryakov wrote:
>
> I can not build CURRENT r343111 on r343022 world. Looks like r343111
> itself cause problems (r343110 builds):
>
> In file included from /data/src/contrib/libc++/src/algorithm.cpp:11:
> In file included from
I can not build CURRENT r343111 on r343022 world. Looks like r343111
itself cause problems (r343110 builds):
In file included from /data/src/contrib/libc++/src/algorithm.cpp:11:
In file included from /data/src/contrib/libc++/include/random:1646:
In file included from
