On Wednesday 2020-06-17 08:03 +0100, Iain Hibbert output:
:On Wed, 17 Jun 2020, Geoff Wing wrote:
:> Hi,
:> I cannot see (in CVS or FTP):
:> src/etc/rc.d/blocklistd
:src/external/bsd/blocklist/etc/rc.d/blocklistd
Thanks. I guess I had a botched build during the changes since m
On Sunday 2020-06-14 22:01 -0400, Christos output:
:I've renamed blacklist to blocklist, so if you are currently using it,
:you should rename things accordingly:
:
: - rc.conf variable
: - /var/db/blacklist.db file
: - npf table name
:
:Apologies for the inconvenience,
:christos
On Saturday 2020-06-06 01:16 +0100, ci4...@gmail.com output:
:On my system from the 4th of June I get unresolved libuv for host,
:nslookup, dig.
:# ldd /usr/bin/dig | grep uv
:-luv.1 => not found
:Is this some local problem? Should I do a clean rebuild?
Hi,
libuv was being installed for a
Hi,
I have an error with the new openssh 8.2. The option "compression" is
not being handled properly.
I blew away my objdir for crypto/external/bsd/openssh before rebuilding
but still getting this error. Anyone else able to reproduce or maybe
something else caused a build error for me?
% ssh
On Monday 2019-12-16 19:56 -0600, ed...@pettijohn-web.com output:
:> > Certificate/key created like so:
:> > openssl req -x509 -nodes -days 365 -sha256 -newkey rsa:2048 -keyout
:> > mycert.pem -out mycert.pem
[...]
:> > Is this a problem with my setup?
:> Think it may be an httpd issue. Used the
Hi,
there is a wrong year in doc/CHANGES.
Regards,
Geoff
Index: doc/CHANGES
===
RCS file: /cvsroot/src/doc/CHANGES,v
retrieving revision 1.2587
diff -u -r1.2587 CHANGES
--- doc/CHANGES 2 Oct 2019 11:18:55 - 1.2587
+++
Hi,
I'm getting quite a few crashes in 8.99.51/9.99.2 on amd64
8.99.51 + modules I built
9.99.2 + modules from nyftp (NetBSD 9.99.2 (GENERIC) #0: Wed Jul 31 16:40:25
UTC 2019)
It seems to be related to npf although when I booted with npf started
during rc processing and then issuing
Hi,
running /sbin/dmesg and /bin/date I am seeing a timezone name of "LMT" instead
of my normal "AEST"
Copying "date" and my zoneinfo file from a working computer, I still see bad
info.
>From -current (compiled myself and from nyftp snapshot):
% TZ=Australia/Melbourne date; TZ=NZ date
Wed Apr 17
On Thursday 2019-03-14 10:57 +, ci4...@gmail.com output:
:Well, after installing the unstripped zsh+modules and ncurses, I no
:longer get zsh any crashes. Plus, as I mentioned, there was some
:jemalloc updates a couple of days ago. Hence, no idea.
Hi,
if you ended up configuring with
Hi,
brief background: on an amd64 VM (1 CPU on VMWare ESXi) I had a network
interface (vmx) failing because it could not get an interrupt slot. The
vmx wants 3 interrupts per interface (tx/rx/link-state). I had a few
on an admin machine and one started failing when ahcisata was changed to
use
On Sunday 2018-10-28 13:16 +1100, Geoff Wing output:
:Hi,
:I'm running the same -current build on two x64 machines. One is a VM
:and the other is bare-metal. I'm rebuilding in case something funny
:happened in the build and noone else can reproduce anything similar.
:
:The ntpdate in /var/run
On Sunday 2018-10-28 08:32 +0700, Robert Elz output:
:I don't suppose that your ToD clock is 6 seconds incorrect, and
:ntpdate run from /etc/rc is fixing that (but the ToD clock isn't being
:updated) ?
:
:if it is not that, then you're right, something weird is happening.
Hi,
I'm running the same
On Sunday 2018-10-28 07:19 +0700, Robert Elz output:
: | The dmesg time matches what appears in kern.boottime but I don't see a 5-6
: | second step in rc.log when ntpdate is run.
:You wouldn't now. The system from which you showed that output has
:been up for a month. During that month,
On Saturday 2018-10-27 19:03 +0700, Robert Elz output:
:Date:Sat, 27 Oct 2018 17:39:16 +1100
:From:Geoff Wing
:Message-ID: <20181027063916.ga2...@primenet.com.au>
:
: | dates output by "dmesg -T" are not matching real time. Using a program
Hi,
dates output by "dmesg -T" are not matching real time. Using a program
to generate a segfault dmesg is showing times in the future:
# sysctl -w kern.logsigexit=1
kern.logsigexit: 0 -> 1
# ./segfault; date
[1]18445 segmentation fault ./segfault
Sat Oct 27 17:33:56 AEDT 2018
# dmesg -T |
On Friday 2018-09-28 19:05 +1000, Geoff Wing output:
:Hi,
:I'm seeing a kassert panic with NPF tables and kernel options DEBUG/LOCKDEBUG
:
:config:
: include "arch/amd64/conf/GENERIC"
: options DEBUG
: options LOCKDEBUG
:
Hi,
this is with the
Hi,
I'm seeing a kassert panic with NPF tables and kernel options DEBUG/LOCKDEBUG
config:
include "arch/amd64/conf/GENERIC"
options DEBUG
options LOCKDEBUG
My /etc/npf.conf has tables with type hash and type tree
Does anyone else have this
On Saturday 2018-04-07 23:37 +1000, Andreas Gustafsson output:
:The build is now failing in a different place, and the new failure did
:not get reported automatically because it was hidden by the one above:
Christos just fixed this (though his fix is missing an update for an
unused #define around
Hi,
npf previously had no issues using a "ruleset" in multiple groups, however
it now has a problem and fails with
npfctl: (re)load failed: some table has a duplicate entry?
The following is a minimal npf.conf to illustrate with it failing due to
the second ``ruleset "blacklistd"''
Hi,
anyone else seeing this sort of stuff?
% dig www.netbsd.org.
14-Feb-2018 16:05:39.436 ENGINE_by_id failed (crypto failure)
14-Feb-2018 16:05:39.436 error:25070067:DSO support
routines:DSO_load:could not load the shared
Hi,
the following files need changes to build a full tree with MKINET6=NO
external/apache2/mDNSResponder/dist/mDNSPosix/mDNSUNP.c
external/bsd/dhcpcd/dist/src/dhcpcd.c
external/bsd/dhcpcd/dist/src/if-bsd.c
external/bsd/tcpdump/bin/Makefile
mDNSUNP.c needs
Hi,
I have an issue where "su" is hanging after get password/key.
It happens with both Kerberos and normal password authentication.
CTRL-C will give an "Interrupted system call".
Kernel is -current amd64 GENERIC plus DEBUG/LOCKDEBUG stuff
My /etc/pam.d/su is the same as base src.
openpam was
On Saturday 2017-04-01 18:14 -0700, John Nemeth output:
: As others have noted, you are totally concentrating on the
:wrong thing. The fact that it "won't build dk structures" is of
:no relevance. The first thing that has to happen is detecting the
:drive. Anyway, can you capture a dmesg?
On Saturday 2017-04-01 11:19 -0700, John Nemeth output:
:On Apr 1, 11:18pm, Geoff Wing wrote:
:} With a fresh 7.1 I have wd[0-9] (and /etc/fstab entries for them) (on i386).
I meant wd0[abefgh] ...
: How old is this system? What is the partition type of the
:NetBSD partition? Can you show
Reply-To
Organization: PrimeNet Computer Consultancy
On Saturday 2017-04-01 12:54 +, mlel...@serpens.de output:
:No need to scan for disklabels if the kernel already uses the disklabel.
:But this has nothing to do with "adding bootloaders". I can only imagine
:that you want to add boot
On Saturday 2017-04-01 08:35 +0200, Martin Husemann output:
:On Sat, Apr 01, 2017 at 05:31:20PM +1100, Geoff Wing wrote:
:> The system installed as an old MBR (+63 sector) system.
:> It did not add any dk stuff for /etc/fstab.
:> It did NOT leave room to add the dk stuff at the start of
Christos Zoulas <chris...@astron.com> typed:
: In article <20170310020544.ga...@primenet.com.au>,
: Geoff Wing <g...@pobox.com> wrote:
:>using the following /etc/npf.conf and an empty file "/etc/npf_blacklist"
:>I get a crash in hashinit(): "KASSERT(element
Hi,
using the following /etc/npf.conf and an empty file "/etc/npf_blacklist"
I get a crash in hashinit(): "KASSERT(elements > 0);"
#10 0x80cf6365 in kern_assert (fmt=fmt@entry=0x810db938 "kernel
%sassertion \"%s\" failed: file \"%s\", line %d ")
at
On Tuesday 2017-01-24 15:59 +1100, Geoff Wing output:
:starting -current on amd64, I get a crash during (presumably) /etc/rc.d/npf
Panics from previous message were when I had
pseudo-device npf
in my kernel config. Removing that I get panics at the same
place (npfctl
Hi,
starting -current on amd64, I get a crash during (presumably) /etc/rc.d/npf
I have some dynamic tables in /etc/npf.conf, e.g.
table type tree dynamic
though maybe not relevant.
Panics are copied from phone video. I can't get a crash dump, nor
does my computer keep system message
Hi,
on an amd64 machine, I was getting the child sshd process seg-faulting
(I believe after dropping privileges but I wasn't getting a coredump) when
trying to accept a connection (``sshd -d -d -d'' wasn't really helpful).
It had three legacy lines in its sshd_config:
HostKey
Hi,
with -current today, when I "/etc/rc.d/ipfilter start" on amd64 it panics in
sys/net/pfil.c:
pfil_add_hook(pfil_func_t func, void *arg, int flags, pfil_head_t *ph)
...
KASSERT((flags & ~PFIL_ALL) == 0);
...
Unfortunately my machine is mostly headless and I can't get dmesg saved
after
On Monday 2016-08-15 17:14 +1000, Joerg Sonnenberger output:
:[] There are still quite a few issues with NPF, primarily
:documentation issues, but also some functional ones. It seems a bit
[...]
I recently ran into an NPF bug (PR 50511 from December last year).
A cursory scan suggested it was
Hi,
with May builds of i386 (cross-compiled from amd64), when I run
squid (pkgsrc build), I get a seg fault, with a backtrace showing
over 20k calls to calloc() in libgnumalloc.
e.g.
.
#22690 0xbb97b58c in calloc () from /usr/lib/libgnumalloc.so.1
#22691 0xbb97b58c in calloc () from
On Friday 2016-04-15 16:20 +1000, Ryota Ozaki output:
:> panic: kernel "(la->la_flags & LLE_STATIC) == 0 failed: .. if_arp",
line 1220
:The source code of your kernel looks a bit old:
: http://nxr.netbsd.org/xref/src/sys/netinet/if_arp.c#1220
:
:You can see the version of the file by:
: $
On Friday 2016-04-15 13:20 +1000, Geoff Wing output:
:panic: kernel "(la->la_flags & LLE_STATIC) == 0 failed: .. if_arp", line
1220
:It also deletes and adds in a static arp address:
: "arp -d 1.2.3.4; arp -s 1.2.3.4 xx:xx:xx:xx:xx:xx"
Taking out the stati
Hi,
with the new networking setup, I'm getting a crash using clean amd64
build (GENERIC kernel) during rc script processing.
After getting past netstart.local, I'll get
interface address is missing from cache = 0x0 in delete
arp: writing to routing socket: No such file
Hi,
for a long time, the parser reading /etc/exports would treat the following
example from exports(5):
/u -maproot=bin: -network 131.104.48 -mask 255.255.255.0
as 131.104.48/24
Currently it's being treated as 131.104.0.48 (seen via ``showmount -e'')
I'm guessing it changed in the last
Updating from a couple of weeks ago, amd is now failing on startup.
Logs say:
Nov 13 22:38:50 computername amd[345]/fatal: cannot create rpc/udp
service
Nov 13 22:38:50 computername amd[345]/info: Finishing with status 2
I'm guessing this is from
On Friday 2015-11-13 22:47 +1100, Geoff Wing output:
: Nov 13 22:38:50 computername amd[345]/fatal: cannot create rpc/udp
service
: Nov 13 22:38:50 computername amd[345]/info: Finishing with status 2
As soon as I post this, I see that Matthias Scheler posted a fix,
so hopefully can
Hi,
recently external/bsd/ntp/dist/ntpd/ntp_parser.[ch] have been
built in the source directories, presumably from ntp_parser.y
Obviously this is not the right spot for them. I haven't seen
a fix in the last couple of days but may have missed it.
Regards,
Geoff
41 matches
Mail list logo
