Re: [PATCH] ksh: Fail gracefully if sethistsize() fails

On Sat, 19 Oct 2019 16:32:56 +0100, Jeremie Courreges-Anglas said: > > Before: > > $ HISTSIZE=10 /bin/sh > > /bin/sh: internal error: unable to allocate memory > > <--- no ksh > Could you provide more details please? A fatal error and a crash are > very different problems.

acpipci(4) _CRS again

So here is another attempt to use information from ACPI to decide what parts of the address space are usable for PCI devices. This version attaches the PCI busses late such that the various hacks for VMs to prevent multiple disk drivers to attach to the same disk still work. Please test,

[UPDATE] xf86-video-amdgpu and xf86-video-ati to versions 19.1.0

Hi, the X drivers for ATI and AMD video cards are updated and released simultanemously, given that they share a lot of code. The patch below updates the 2 drivers to versions 19.1.0 which where recently released by X.Org. Apply to /usr/xenocara (or $XSRCDIR) using 'patch -p0 -E' and rebuild

Re: [PATCH] ksh: Fail gracefully if sethistsize() fails

On Fri, Oct 18 2019, tho...@habets.se wrote: > This can be hard to debug, and could indeed prevent debugging, since > it can take out the ability to run /bin/sh, depending on how you've > set up your environment. > > Before: > $ HISTSIZE=10 /bin/sh > /bin/sh: internal error: unable to

ssh-keygen.1 fixes regarding new -Y flag

Hello tech@, Find a patch fixing some details in ssh-keygen.1 regarding the new -Y flag for signing and verifying signatures. Precisely: - Include a missing 'returning a zero exit status' in `-Y verify` paragraph. - Don't include `option` in `.Fl I` in ALLOWED SIGNERS section. -Lucas Index:

Re: bgpctl(8) shutdown communication

Jeremie Courreges-Anglas wrote: > On Sat, Oct 19 2019, "Theo de Raadt" wrote: > > Jeremie Courreges-Anglas wrote: > > > >> On Sat, Oct 19 2019, Claudio Jeker wrote: > >> > bgpd supports up to 255 byte shutdown communications. So the manpage is > >> > not telling the truth. Also I don't think

Re: bgpctl(8) shutdown communication

On Sat, Oct 19 2019, "Theo de Raadt" wrote: > Jeremie Courreges-Anglas wrote: > >> On Sat, Oct 19 2019, Claudio Jeker wrote: >> > bgpd supports up to 255 byte shutdown communications. So the manpage is >> > not telling the truth. Also I don't think it is helpful to mention the >> > limit at

Re: bgpctl(8) shutdown communication

I also think a truncated message is way more useful than a replacement which throws away the content of the message! Jeremie Courreges-Anglas wrote: > On Sat, Oct 19 2019, Claudio Jeker wrote: > > bgpd supports up to 255 byte shutdown communications. So the manpage is > > not telling the

Re: diff for sysupgrade.sh in anticipation of release 10.0

On Wed, Oct 09, 2019 at 04:38:07PM +, Chris Waddey wrote: > > Hello all. > > I know this isn't necessary for quite a while, but in anticipation of > OpenBSD 10.0, I suggest the following diff to sysupgrade.sh: Thanks. There were two more copies of this code in the tree which ajacoutot and I

Re: bgpctl(8) shutdown communication

On Sat, Oct 19 2019, Claudio Jeker wrote: > bgpd supports up to 255 byte shutdown communications. So the manpage is > not telling the truth. Also I don't think it is helpful to mention the > limit at all. bgpctl will exit with 'shutdown reason too long' if the text > is too long which is good

Re: xhci(4): fix endless loop when transfer is aborted

On Fri, Oct 18, 2019 at 05:14:24PM +0200, Martin Pieuchot wrote: > As soon as a transfer with an error condition is passed to > usb_transfer_complete(), usbd_start_next() won't be called. > > If the callback of that transfer had already enqueue a new xfer, via > usbd_transfer(), it will stay on

bgpctl(8) shutdown communication

bgpd supports up to 255 byte shutdown communications. So the manpage is not telling the truth. Also I don't think it is helpful to mention the limit at all. bgpctl will exit with 'shutdown reason too long' if the text is too long which is good enough. For best interop people should keep the