The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2021.04.25.05.33.20 thorpej src/tests/dev/scsipi/libscsitest/scsitest.c,v
1.4
2021.04.25.05.52.22 nia src/share/man/man8/compat_linux.8,v 1.42
Logs can
Hi,
Jason Thorpe writes:
> Folks --
>
> I just merged the thorpej-cfargs branch, which contains some
> mostly-mechanical cleanups and some small but very useful enhancements to the
> device auto configuration subsystem. I've made an effort to build just about
> every kernel config we have, a
> On Apr 24, 2021, at 6:53 PM, Izumi Tsutsui wrote:
>
> thorpej@ wrote:
>
>> Folks --
>>
>> I just merged the thorpej-cfargs branch, which contains some
>> mostly-mechanical cleanups and some small but very useful enhancements
>> to the device auto configuration subsystem.
>
> Maybe several
thorpej@ wrote:
> Folks --
>
> I just merged the thorpej-cfargs branch, which contains some
> mostly-mechanical cleanups and some small but very useful enhancements
> to the device auto configuration subsystem.
Maybe several section 5 and 9 man pages should be updated to sync
with the changes?
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2021.04.24.23.40.16.
An extract from the build.sh output follows:
nbmake[4]: stopped in /tmp/build/2021.04.24.23.40.
Folks --
I just merged the thorpej-cfargs branch, which contains some mostly-mechanical
cleanups and some small but very useful enhancements to the device auto
configuration subsystem. I've made an effort to build just about every kernel
config we have, and boot said kernel on a reasonable var
On Sat, 24 Apr 2021 at 20:11, Martin Husemann wrote:
>
> On Sat, Apr 24, 2021 at 03:19:16PM +, nia wrote:
> > Thank you! This works great, I'll make note of it in the NetBSD Guide's
> > section
> > on networking.
>
> Another option (as rjs hinted) is to only have a vether0.ifconfig (I did
> t
On Sat, Apr 24, 2021 at 03:19:16PM +, nia wrote:
> Thank you! This works great, I'll make note of it in the NetBSD Guide's
> section
> on networking.
Another option (as rjs hinted) is to only have a vether0.ifconfig (I did
that with bridge0.ifconfig for other setups) and use ! lines to do the
On Sat, Apr 24, 2021 at 07:57:30AM -0700, Jason Thorpe wrote:
>
> > On Apr 24, 2021, at 5:42 AM, nia wrote:
> >
> > I wonder if there's an initialization order difference
> > somewhere.
>
> If you want to have control over the initialization order, you need to set
> auto_ifconfig=NO. On one o
> On Apr 24, 2021, at 5:42 AM, nia wrote:
>
> I wonder if there's an initialization order difference
> somewhere.
If you want to have control over the initialization order, you need to set
auto_ifconfig=NO. On one of my systems that has a bunch of Qemu VMs:
auto_ifconfig=NO
net_interfaces="
nia wrote:
>I just updated our home router from 9.1 to -current because a
>roommate wanted to use wg(4).
>
>I use tap as a bridge endpoint for two NICs that are used for
>the LAN.
>
>I thought I'd be able to copy the configs and do a straightforward
>subtitution from tap to vether but this doesn
I just updated our home router from 9.1 to -current because a
roommate wanted to use wg(4).
I use tap as a bridge endpoint for two NICs that are used for
the LAN.
I thought I'd be able to copy the configs and do a straightforward
subtitution from tap to vether but this doesn't work.
/etc/rc.d/net
12 matches
Mail list logo