[PATCH libssl] Fix typo in man page

--- src/lib/libssl/man/SSL_CTX_set_cipher_list.3 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/lib/libssl/man/SSL_CTX_set_cipher_list.3 b/src/lib/libssl/man/SSL_CTX_set_cipher_list.3 index 64da0092d..6f15dbaaa 100644 ---

Re: fwide() does not unlock if error was occurred

On Mon, Dec 2, 2019 at 7:48 PM Masato Asou wrote: > fwide() does not unlock if error was occurred. > > ok? > ok guenther@

fwide() does not unlock if error was occurred

fwide() does not unlock if error was occurred. ok? Index: lib/libc/stdio/fwide.c === RCS file: /cvs/src/lib/libc/stdio/fwide.c,v retrieving revision 1.5 diff -u -p -r1.5 fwide.c --- lib/libc/stdio/fwide.c 31 Aug 2015 02:53:57

tcpdump(8): RFC 8300 Network Service Header (NSH) printing

this handles printing of NSH packets as per RFC 8300. i was trying to understand how the protocol was put together, and this helped me a lot. it looks like this: $ ./obj/tcpdump -nr /home/dlg/tmp/nsh.pcap tcpdump: WARNING: snaplen raised from 116 to 262144 09:13:40.394208 NSH spi 777 si 7 md1:

Re: grep -R with no path

On Mon, Dec 02, 2019 at 08:31:02AM +, Miod Vallat wrote: > grep(1), when invoked with the -R option but no path, displays a > "recursive search of stdin" warning and acts as if -R had not been > specified. > > GNU grep, in that case, will perform a recursive search in the current > directory,

Re: ix(4) need support for X553

On 18.11.2019. 0:31, Hrvoje Popovski wrote: > On 14.11.2019. 1:06, Stuart Henderson wrote: >> Apart from the obvious style(9) problems, can anyone give me guidance on >> how to approach this diff? I'm quite uneasy at the amount of changes but >> these >> nics are quite important, they're all over

Re: grep -R with no path

On Mon, 02 Dec 2019 23:09:23 +0100, Jeremie Courreges-Anglas wrote: > This diff moves the fake argv logic moves into grep_tree() where we can > opt for pretty-printing. ok? That's similar to what I was going to propose. OK millert@ - todd

Re: grep -R with no path

On Mon, Dec 02 2019, Jeremie Courreges-Anglas wrote: [...] > I have had a similar diff for some time but didn't push for it because > nitpicking: GNU grep doesn't prepend "./" to file names in this case. > I have a diff to do this but let's keep the nitpicking for later. Current: --8<--

unveil radioctl/fdformat/gpioctl

Hi tech@ radioctl/fdformat/gpioctl need to open the device and then all operations go through ioctls forbidden by pledge but no further filesystem access is needed so it can be disallowed right afterwards. CAVEAT: The sources for these applications are simple enough to follow, but unfortunately

Re: grep -R with no path

On Mon, 02 Dec 2019 08:31:02 +, Miod Vallat wrote: > grep(1), when invoked with the -R option but no path, displays a > "recursive search of stdin" warning and acts as if -R had not been > specified. > > GNU grep, in that case, will perform a recursive search in the current > directory, i.e.

Re: grep -R with no path

On Mon, Dec 02, 2019 at 06:08:35PM +0100, Jeremie Courreges-Anglas wrote: > On Mon, Dec 02 2019, Marc Espie wrote: > > On Mon, Dec 02, 2019 at 08:31:02AM +, Miod Vallat wrote: > >> grep(1), when invoked with the -R option but no path, displays a > >> "recursive search of stdin" warning and

Re: grep -R with no path

On Mon, Dec 02 2019, Marc Espie wrote: > On Mon, Dec 02, 2019 at 08:31:02AM +, Miod Vallat wrote: >> grep(1), when invoked with the -R option but no path, displays a >> "recursive search of stdin" warning and acts as if -R had not been >> specified. >> >> GNU grep, in that case, will perform

Infinite sleeps in sys/miscfs

Ok? Index: miscfs/deadfs/dead_vnops.c === RCS file: /cvs/src/sys/miscfs/deadfs/dead_vnops.c,v retrieving revision 1.30 diff -u -p -r1.30 dead_vnops.c --- miscfs/deadfs/dead_vnops.c 19 Oct 2019 06:56:18 - 1.30 +++

Infinite sleeps in sys/scsi

Convert them to msleep_nsec(9) and tsleep_nsec(9), ok? Index: scsi/scsi_base.c === RCS file: /cvs/src/sys/scsi/scsi_base.c,v retrieving revision 1.250 diff -u -p -r1.250 scsi_base.c --- scsi/scsi_base.c1 Dec 2019 16:56:26 -

Infinite sleeps in sys/nfs

Convert all of them to tsleep_nsec(9), ok? Index: nfs/nfs_aiod.c === RCS file: /cvs/src/sys/nfs/nfs_aiod.c,v retrieving revision 1.7 diff -u -p -r1.7 nfs_aiod.c --- nfs/nfs_aiod.c 28 Aug 2015 00:03:54 - 1.7 +++

rewrite dhcpv6 handling in tcpdump(8)

tcpdump segfaulted on me when i was running it on sparc64, and i think i narrowed it down to the dhcp6 code. while trying to fix it i discovered that it implements parsing of some extremely pre-rfc dhcpv6 protocol, and is completely wrong. this rewrites it so it follows the most recent rfc,

Re: syscall call-from verification

My bad, SBCL uses the libc's wrappers indeed looking at the sources. Le ven. 29 nov. 2019 à 22:41, Josh Elsasser a écrit : > > On Fri, Nov 29, 2019 at 10:12:10AM +0100, Thomas de Grivel wrote: > > Maybe Go is not the only problem, I see SBCL compiling syscalls too. > > > > Truth is libc is for C

Re: change to bsd.port.mk to help debug packages a bit

On Wed, Nov 27, 2019 at 05:55:47PM +0100, Marc Espie wrote: > This should get rid of the weird error (don't know how to make > .../all/debug-*.tgz) when switching from !DEBUG_PACKAGES to DEBUG_PACKAGES. > > Basically, this introduces a "build two targets at once" in bsd.port.mk. > > make has

Re: grep -R with no path

On Mon, Dec 02, 2019 at 08:31:02AM +, Miod Vallat wrote: > grep(1), when invoked with the -R option but no path, displays a > "recursive search of stdin" warning and acts as if -R had not been > specified. > > GNU grep, in that case, will perform a recursive search in the current > directory,

grep -R with no path

grep(1), when invoked with the -R option but no path, displays a "recursive search of stdin" warning and acts as if -R had not been specified. GNU grep, in that case, will perform a recursive search in the current directory, i.e. uses an implicit "." path if none is given. This is IMO a much