All the is*() ctype.h functions take an int as argument, but valid
values are only EOF, and the range of values of `unsigned char'.
All, but one: the XPG4 isascii(), which has no such restriction.
Quoting https://pubs.opengroup.org/onlinepubs/9699919799/ :
``The isascii() function is defined on al
On 12/05/2021 15:15, Patrick Wildt wrote:
> Hi,
>
> when hvn(4) attaches it sends commands and waits for replies to come
> back in, hence the interrupt function is being polled. Unfortunately
> it seems that the 'receive pipe' has both command completion and data
> packets. As it turns out, whil
I am likely going to simply track file changes and revert them for a reset to
factory defaults facilitation, rather than maintaining a build system for a
custom bsd.rd.
One assumption that I have made is that newfs and dd altroot to root and reboot
in rc.securelevel would fail or be problematic?
Friendly ping.
Ashton Fagg writes:
> My new Intel Z590-based machine seems to have some different kind of
> Intel audio device onboard.
>
> I couldn't find very much online about it (all the usual pci id
> databases don't seem to have it yet). The only really useful thing I
> found was this:
>
>
any takers?
On Fri, 2021-06-04 at 22:11 +0200, Martijn van Duren wrote:
> ping
>
> On Fri, 2021-05-28 at 08:19 +0200, Martijn van Duren wrote:
> > As the original comment said:
> > /*
> > * This should probably go into parsevarbinds, but that's for a
> > * next refactor
> > */
> >
> > This mo
I hear there are circuses out there where the dhcp server hands us a /32
and so the default gateway is not reachable.
The comment in sbin/dhclient/kroute.c suggests that the Google Clown
Platform operates in this way. I seem to recall mumblings that Hetzner
does something similar on their VPS.
Cu
Here's my take at documenting the missing pledge promises in pledge.2
and placing them in a reasonable order with the others. Each of these
just enabled various ioctl or sysctl interfaces.
I'm unhappy with the explanation for drm, but don't know how to
explain the purpose of these ioctls, and cou
Regarding the vmm chunk -- as I said in my other reply, these
explanations are too precise. They risk becoming outdated as things
change. Furthermore, some of those ioctl may work in one way, but not
another way. Which would be too complicated to describe also. I urge
simple messaging:
.It Va
Theo de Raadt writes:
> Regarding the vmm chunk -- as I said in my other reply, these
> explanations are too precise. They risk becoming outdated as things
> change. Furthermore, some of those ioctl may work in one way, but not
> another way. Which would be too complicated to describe also.
Dave Voutila wrote:
> Theo de Raadt writes:
>
> > Regarding the vmm chunk -- as I said in my other reply, these
> > explanations are too precise. They risk becoming outdated as things
> > change. Furthermore, some of those ioctl may work in one way, but not
> > another way. Which would be too
On Fri, Jun 11, 2021 at 10:03:07AM -0400, Ashton Fagg wrote:
> Friendly ping.
>
> Ashton Fagg writes:
>
> > My new Intel Z590-based machine seems to have some different kind of
> > Intel audio device onboard.
> >
> > I couldn't find very much online about it (all the usual pci id
> > databases d
Jonathan Gray writes:
> I can't find 0xf0c8 in the datasheets either.
>
> I've committed this but moved the added line in pcidevs to maintain
> ordering by device id. Thanks for the patch.
Great, thank you!
Hi,
setitimer(2) has a one hundred million second upper bound for timers.
Any timer interval larger than this is considered invalid and we set
EINVAL.
There is no longer any reason to use this particular limit. Kclock
timeouts support the full range of a timespec, so we can trivially
increase th
On Fri, Jun 11, 2021 at 09:16:46AM -0600, Theo de Raadt wrote:
> Dave Voutila wrote:
>
> > Theo de Raadt writes:
> >
> > > Regarding the vmm chunk -- as I said in my other reply, these
> > > explanations are too precise. They risk becoming outdated as things
> > > change. Furthermore, some of th
I do not consider it necessarily a bug so I did not send this bugs@, but
this did impact ProxyJump in my ~/.ssh/config. I'd formerly had:
ProxyJump host, anotherhost
This currently/now fails with "Invalid ProxyJump". Re-checking the ssh_config
manual page though I saw the clarification of "separa
15 matches
Mail list logo
