Re: retries and timeouts for radiusctl(8) test

ok yasuoka On Fri, 21 Feb 2020 15:32:53 +1000 David Gwynne wrote: > we (work) use radiusctl as part of a check script with relayd so > we can try and keep a radius service available with some magical > routing and redirect configs. > > radiusctl is currently pretty simple and sends a radius requ

retries and timeouts for radiusctl(8) test

we (work) use radiusctl as part of a check script with relayd so we can try and keep a radius service available with some magical routing and redirect configs. radiusctl is currently pretty simple and sends a radius request, and then waits for a reply. however, it does not implement retries and ti

diff: init efifb even if VGA is probed.

Hello, I am testing a new hardware, HPE DL20 Gen10. When efiboot starts the kernel, the video display becomes distorted and never recovered until CPU reset. Our kernel tries to initialized console twice, first trial is done before getting boot info and second trial is done after getting boot inf

Re: [PATCH] make cwm parse /etc/ssh/ssh_known_hosts (global known hosts) as well as user's known_hosts

I don't like this, and think it is dangerous coupling between systems. If anything similar to browsers, window managers should not have access to anything in the ~/.ssh directory. Or well, any other object they don't actually need. Franz Bettag wrote: > Dear OpenBSD folks, > > appended you

rc.subr.8: Fix daemon_rtable route command mention

Without "exec" the comand is invalid. $ tail -n2 /etc/rc.subr [ "${daemon_rtable}" -eq "$(id -R)" ] || rcexec="route -T ${daemon_rtable} exec ${rcexec}" OK? Index: share/man/man8/rc.subr.8 === RCS fi

Re: amd64: use ffs2 for filesystems created by install

On Thu, Feb 20, 2020 at 08:20:13PM +0100, Otto Moerbeek wrote: > On Thu, Feb 20, 2020 at 07:48:25PM +0100, Otto Moerbeek wrote: > > > On Thu, Feb 20, 2020 at 07:27:55PM +0100, Matthias Schmidt wrote: > > > > > Hi Otto, > > > > > > * Otto Moerbeek wrote: > > > > Hi, > > > > > > > > This is amd6

Re: amd64: use ffs2 for filesystems created by install

On Thu, Feb 20, 2020 at 07:48:25PM +0100, Otto Moerbeek wrote: > On Thu, Feb 20, 2020 at 07:27:55PM +0100, Matthias Schmidt wrote: > > > Hi Otto, > > > > * Otto Moerbeek wrote: > > > Hi, > > > > > > This is amd64 only, it contains some i386 pieces, but those are > > > incomplete. > > > > > > W

Re: amd64: use ffs2 for filesystems created by install

On Thu, Feb 20, 2020 at 07:27:55PM +0100, Matthias Schmidt wrote: > Hi Otto, > > * Otto Moerbeek wrote: > > Hi, > > > > This is amd64 only, it contains some i386 pieces, but those are > > incomplete. > > > > With the diff, install uses ffs2 for the filesystems created during > > install. All bo

Re: amd64: use ffs2 for filesystems created by install

Hi Otto, * Otto Moerbeek wrote: > Hi, > > This is amd64 only, it contains some i386 pieces, but those are > incomplete. > > With the diff, install uses ffs2 for the filesystems created during > install. All boot loaders (except the floppy one) contain support for > loading a kernel from ffs2. >

Re: upd(4): force boolean indicator to be 0 or 1

Anyone? Op Mon, 20 Jan 2020 12:22:07 +0100 schreef Boudewijn Dijkstra : Some upd(4) devices use -1 for "On" and some use 1. sysctl(8) and sensorsd(8) hide this detail from the user, which makes it difficult to define low and high values in sensorsd.conf(5). Also see https://marc.info/?l=op

amd64: use ffs2 for filesystems created by install

Hi, This is amd64 only, it contains some i386 pieces, but those are incomplete. With the diff, install uses ffs2 for the filesystems created during install. All boot loaders (except the floppy one) contain support for loading a kernel from ffs2. To test, create a snapshot (see release(8)) with t