Re: OpenBSD `ftp` port for MSVC (Windows)

Hi Samuel, first, note that this is off-topic on tech@. If you see a need to continue the thread, please move it to misc@. Samuel Marks wrote on Sun, Sep 05, 2021 at 02:10:14PM -0400: > WiP, basically just started this: >

Re: riscv64: icache flush using sysarch(2)

On Sat, Sep 04 2021, Jeremie Courreges-Anglas wrote: > The first problem I was able to diagnose using egdb on riscv was > lang/python/2.7 using libffi and aborting in libcompiler-rt (the > compilerrt_abort() call below). > > --8<-- > #elif defined(__riscv) && defined(__linux__) > #define

OpenBSD `ftp` port for MSVC (Windows)

WiP, basically just started this: https://github.com/offscale/libacquire/tree/423b751/libacquire/openbsd_ftp What: - My project allows for switching between the HTTPS interface provided by your OS, and libcurl's HTTPS interface. Why OpenBSD `ftp` port: - I don't have a "pure" socket solution,

dwctwo(4) isoc

In case you are playing around with isoc transfers (uvideo, uaudio) on dwctwo(4), and you are facing kernel crashes, you can try this diff. Or if you just want to regression test it. It basically does: * Fix DMA allocation out of interrupt context. * Fix a memory leak on DMA allocation during

Re: Update to pcap-filter.5/tcpdump.8 (was: update to tcpdump(8))

On Sun, Sep 05, 2021 at 04:43:34PM +0200, Denis Fondras wrote: > Le Sat, Sep 04, 2021 at 09:57:10PM +0100, Jason McIntyre a ?crit : > > the diff looks ok to me. but run any doc changes through "mandoc > > -Tlint", and look at any issues your diff may have introduced. in this > > case it's just

Update to pcap-filter.5/tcpdump.8 (was: update to tcpdump(8))

Le Sat, Sep 04, 2021 at 09:57:10PM +0100, Jason McIntyre a écrit : > the diff looks ok to me. but run any doc changes through "mandoc > -Tlint", and look at any issues your diff may have introduced. in this > case it's just trailing whitespace, but it's super helpful to check your > work. >

Re: man sed(1) diff

On Sun, Sep 05, 2021 at 02:01:37PM +0200, Ingo Schwarze wrote: > Hello, > > i see where Ian's confusion is coming from, even though arguably, > the existing text is accurate. But it is not a good idea to insert > exceptions as parenthetic remarks in the middle of an enumeration > of steps that

Re: man sed(1) diff

On Sun, Sep 05, 2021 at 09:51:44AM +0100, ropers wrote: > I. > > Not to engage in pointless bikeshedding, but I find this clearer and > --if I understand things correctly-- also more technically accurate: > > Index: sed.1 > === >

Re: man sed(1) diff

Hello, i see where Ian's confusion is coming from, even though arguably, the existing text is accurate. But it is not a good idea to insert exceptions as parenthetic remarks in the middle of an enumeration of steps that is already somewhat long and complicated. I think it is better to explain

snaps: scp uses SFTP protocol by default

Hi, Just letting you know that the snaps rolling out now have scp defaulting to use the SFTP protocol by default. We hope to keep this change in the next release, so please report any problems you encounter either here (tech@), to bugs@ or to openssh@. One thing to be aware of: copying to/from a

Re: Fix: tcp_output window calculation error

On 22/07/21(Thu) 15:03, Jan Klemkow wrote: > Hi, > > This calculation of the receive window has a logic error: > > If win is 0 it will be overwritten by (rcv_adv - rcv_nxt). Thus, win > will be (rcv_adv - rcv_nxt) even if its below (sb_hiwat / 4). Why is this a problem? > We could just remove

man sed(1) diff

I. Not to engage in pointless bikeshedding, but I find this clearer and --if I understand things correctly-- also more technically accurate: Index: sed.1 === RCS file: /cvs/src/usr.bin/sed/sed.1,v retrieving revision 1.60 diff -C8