Updating src tree:
P src/distrib/sets/lists/comp/mi
P src/distrib/sets/lists/man/mi
P src/doc/3RDPARTY
P src/games/fortune/datfiles/fortunes
P src/share/man/man4/Makefile
P src/share/man/man4/speaker.4
U src/share/man/man4/wsbell.4
P src/share/man/man4/wsmux.4
P src/share/man/man9/Makefile
U src/s
from Thor Lancelot Simon:
> On Tue, Jun 13, 2017 at 09:20:24PM +, Thomas Mueller wrote:
> > I don't run dhcpcd or anything like that from /etc/rc.conf but ran
> > dhcpcd -dM re0 :
> It appears dhcpcd sends DISCOVER messages for a full minute and receives
> no responses. Are you sure
I'll see if I can do some chaos monkey thing for wd(4) to test the error
paths.
I'm not quite sure what kind of special error recovery would be necessary
to add though. With NCQ, if there is any error, all pending commands are
cancelled by the device. There is nothing to recover by HBA. The comman
Date:Tue, 13 Jun 2017 17:23:12 -0400
From:Thor Lancelot Simon
Message-ID: <20170613212312.ga20...@panix.com>
| On Tue, Jun 13, 2017 at 09:20:24PM +, Thomas Mueller wrote:
| >
| > I don't run dhcpcd or anything like that from /etc/rc.conf but ran
| > dhcp
On Tue, Jun 13, 2017 at 09:20:24PM +, Thomas Mueller wrote:
>
> I don't run dhcpcd or anything like that from /etc/rc.conf but ran
> dhcpcd -dM re0 :
It appears dhcpcd sends DISCOVER messages for a full minute and receives
no responses. Are you sure the DHCP server is OK?
Thor
from Roy Marples and my previous post:
> > Using dhcpcd or dhclient makes me rusty on directly setting internet
> > interface; any suggestions for improvement on what I did are welcome.
> > But directly configuring internet interface uncripples an otherwise
> > crippled NetBSD installation.
On 13/06/2017 11:22, Robert Elz wrote:
> Look for /libexec/dhcpcd-run-hooks (which should be executable) and
> /libexec/dhcpcd-hooks/* which should have a bunch of files that should
> be readable (do not need 'x' not that it would hurt.) I'm not sure
> just where the ifconfig's get done though.
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2017.06.13.09.11.22 nat src/share/man/man4/Makefile,v 1.638
2017.06.13.09.11.22 nat src/share/man/man9/Makefile,v 1.415
Log files can be found at:
Date:Tue, 13 Jun 2017 07:33:35 +
From:"Thomas Mueller"
Message-ID: <38.87.01815.C459F395@dnvrco-omsmta03>
| I tried again with dhcpcd and did worse,
You are still not telling us what "worse" means, what was the state
before you did the manual configuration (b
Hi Thomas
On 13/06/2017 08:33, Thomas Mueller wrote:
> I tried again with dhcpcd and did worse, then did directly (after ps -aux and
> killing job number for dhcpcd)
>
> ifconfig re0 inet 192.168.0.4 netmask 255.255.255.0
> route add default 192.168.0.1
>
> and then was successful with "host n
Already fixed:
http://mail-index.netbsd.org/source-changes/2017/06/13/msg085302.html
On Tue, 13 Jun 2017, NetBSD Test Fixture wrote:
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 sour
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 2017.06.13.06.39.09.
An extract from the build.sh output follows:
AWK=/tmp/bracket/build/2017.06.13.06.39.09-i386/to
from Robert Elz:
> | Do you really mean netstat -nrf inet4 , or should that be inet?
> Roy meant the latter. (That weird inconsistency is annoying, we should
> support "inet4" as an alias to "inet" everywhere. But we don't...)
> | Now if I knew what options/parameters to tweak, I could t
13 matches
Mail list logo
