Re: Installing OpenBSD -current snapshots

2019-11-27 Thread Robert Klein
On Wed, 27 Nov 2019 20:29:27 -0600 Edgar Pettijohn wrote: > On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote: > > I have successfully installed OpenBSD 6.6 release and would like to > > give the Current Snapshots a try. I went to a mirror, and to: > > > > Index of

Re: Installing OpenBSD -current snapshots

2019-11-27 Thread Edgar Pettijohn
On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote: > I have successfully installed OpenBSD 6.6 release and would like to give > the Current Snapshots a try. I went to a mirror, and to: > > Index of /pub/OpenBSD/snapshots/amd64/ > > I saw install66.fs (probably for usb memstick) and

Re: Installing OpenBSD -current snapshots

2019-11-27 Thread Clay Daniels
Never mind, I found the instructions the the same mirror directory,in a plain text file called "INSTALL.amd64". Forgive the dummy here, Clay On Wed, Nov 27, 2019 at 8:05 PM Clay Daniels wrote: > I have successfully installed OpenBSD 6.6 release and would like to give > the Current Snapshots a

Installing OpenBSD -current snapshots

2019-11-27 Thread Clay Daniels
I have successfully installed OpenBSD 6.6 release and would like to give the Current Snapshots a try. I went to a mirror, and to: Index of /pub/OpenBSD/snapshots/amd64/ I saw install66.fs (probably for usb memstick) and install66.iso (surely for a cd/dvd) at ~450Mb. I picked the install66.fs,

Deleting softraid Devices Fujitsu Sparc

2019-11-27 Thread Kihaguru Gathura
Hi, An error while deleting softraid device follows -- Available disks are: sd0 sd1 sd2. Which disk is the root disk? ('?' for details) [sd0] ? sd0: FUJITSU, MAT3073N SUN72G, 0602

snmpd(8) custom OID names

2019-11-27 Thread Joel Carnat
Hello, I have set custom OIDs in my snmpd.conf(5). When I walk or get those values, using snmp(1) or snmpget(1), the "name" parameters is not listed. I only get values described as OPENBSD-BASE-MIB::localTest.* Is there a straight way to get the configured names from snmp clients? Or do I have

Re: SIGBUS on octeon for my program

2019-11-27 Thread Peter J. Philipp
On Wed, Nov 27, 2019 at 09:16:51AM -0500, David Higgs wrote: > I don't speak ktrace but looks like alignment problems with a stack > variable. What does gdb report? > > --david Hi David, I'm going to upgrade to -current and then report back.. it'll take me a few days to do that (I'm super

Re: SIGBUS on octeon for my program

2019-11-27 Thread Peter J. Philipp
On Wed, Nov 27, 2019 at 03:13:19PM +0100, Janne Johansson wrote: > There was a fix recently for the stack getting unaligned committed just > recently, do you have that? > If not, test on current. Ok it'll take me a bit to test on current, as I don't have that fix yet. Thanks a lot! I'll come

Re: SIGBUS on octeon for my program

2019-11-27 Thread David Higgs
I don't speak ktrace but looks like alignment problems with a stack variable. What does gdb report? --david On Wed, Nov 27, 2019 at 8:48 AM Peter J. Philipp wrote: > Hi, > > My DNS program gets a SIGBUS when I execute it. I have ktraced it, upped > limits and searched in the mips64 source

Re: SIGBUS on octeon for my program

2019-11-27 Thread Janne Johansson
There was a fix recently for the stack getting unaligned committed just recently, do you have that? If not, test on current. Den ons 27 nov. 2019 kl 14:48 skrev Peter J. Philipp : > Hi, > > My DNS program gets a SIGBUS when I execute it. I have ktraced it, upped > limits and searched in the

SIGBUS on octeon for my program

2019-11-27 Thread Peter J. Philipp
Hi, My DNS program gets a SIGBUS when I execute it. I have ktraced it, upped limits and searched in the mips64 source for answers, could this be a compiler problem? ktrace-> 41651 dddctl CALL connect(6,0xfcacb0,16) 41651 dddctl STRU struct sockaddr { AF_INET, 192.168.177.2:10053

Re: Router with WAN subnet - dedicated IP per Host

2019-11-27 Thread Henry Jensen
On Tue, 26 Nov 2019 20:06:40 - (UTC) Stuart Henderson wrote: > On 2019-11-26, Henry Jensen wrote: > > On Tue, 26 Nov 2019 12:27:16 - (UTC) > > Stuart Henderson wrote: > > > >> > 192.168.1.2 < rdr-to/nat-to > 11.22.33.40 > >> > 192.168.1.3 < rdr-to/nat-to > 11.22.33.41 > >> > > >> >