So it does. Not sure how I missed that, but I did. Oh well. Thanks :-/
John
On 1 October 2016 at 14:31, Theo Buehler wrote:
> On Sat, Oct 01, 2016 at 01:38:49PM +1000, john slee wrote:
> > Not sure if folks are interested in this or not, but it sure caused me
> some
> >
On Sat, Oct 01, 2016 at 01:38:49PM +1000, john slee wrote:
> Not sure if folks are interested in this or not, but it sure caused me some
> angst this morning. OSX has the same behaviour and also doesn't document
> it. I assume it has been that way for a long, long time.
>
> My first patch. Thanks
Not sure if folks are interested in this or not, but it sure caused me some
angst this morning. OSX has the same behaviour and also doesn't document
it. I assume it has been that way for a long, long time.
My first patch. Thanks for all the cool stuff :-)
Index: bin/test/test.1
Hello,
patch below makes life easier for clients, which always use same source port,
when talking to server (e.g. think of NFS). The scenario we are dealing with
is as follows:
- client mounts remote NFS share
- there is a PF sitting between client and NFS server. the mount
> From: Jeremie Courreges-Anglas
> Date: Fri, 30 Sep 2016 17:00:45 +0200
>
> Mark Kettenis writes:
>
> [...]
>
> >> > -for (i = 0; kbdenc_tab[i].value; i++)
> >> > -printf("%s\n", kbdenc_tab[i].name);
> >> > +for (i =
On Fri, Sep 30, 2016 at 05:19:22PM +0200, Jan Stary wrote:
> The diff below removes a .Pp before an .It
> which mandoc complains about and ignores.
>
> Jan
>
fixed, thanks.
jmc
>
> Index: ksh.1
> ===
> RCS file:
> Diff below is a possible way to fix this. But in a way we're cheating
> here since we'll still consume more than 2047 bytes of stack space
> when we descend into wskbd_initmute(). So perhaps we should rewrite
> this code to dynamically allocate the mixer_devinfo structs?
yes, it should be
The diff below removes a .Pp before an .It
which mandoc complains about and ignores.
Jan
Index: ksh.1
===
RCS file: /cvs/src/bin/ksh/ksh.1,v
retrieving revision 1.181
diff -u -p -r1.181 ksh.1
--- ksh.1 27 Sep 2016
Ping.
On Mon, Sep 19, 2016 at 09:22:50PM -0400, David Hill wrote:
> Hello -
>
> Here are the final bcopy->memcpy conversions in netinet6 that I am
> comfortable with. There is also one (bcmp()) to (memcmp() != 0)
> conversion since the memory is not overlapping.
>
> This, with the last
Mark Kettenis writes:
[...]
>> > - for (i = 0; kbdenc_tab[i].value; i++)
>> > - printf("%s\n", kbdenc_tab[i].name);
>> > + for (i = 0; i < encs->nencodings; i++) {
>> > + n = _tab[0];
>> > + found = 0;
>> > + encoding =
> From: Jeremie Courreges-Anglas
> Date: Fri, 30 Sep 2016 13:32:57 +0200
>
> Mark Kettenis writes:
>
> >> Date: Thu, 29 Sep 2016 14:19:43 +0200 (CEST)
> >> From: Mark Kettenis
> >>
> >> This diff adds a WSKBDIO_GETENCODINGS
We compile out kernel with -Wframe-larger-than=2047 to make sure we
don't write stupid code that blows the kernel stack. Now clang thinks
it is clever and considers it a good idea to inline functions when the
function and the caller live in the same source file. A particular
case where this
Jeremie Courreges-Anglas writes:
> j...@wxcvbn.org (Jeremie Courreges-Anglas) writes:
>
>> SNMP uses UDP and snmpd listens on a single address. This means that
>> you can have issues with the source address of the replies sent by
>> snmpd. "listen on $loopback_address":
>>
>>
j...@wxcvbn.org (Jeremie Courreges-Anglas) writes:
> SNMP uses UDP and snmpd listens on a single address. This means that
> you can have issues with the source address of the replies sent by
> snmpd. "listen on $loopback_address":
>
> http://marc.info/?l=openbsd-misc=147445870822415=2
>
>
j...@wxcvbn.org (Jeremie Courreges-Anglas) writes:
> Looks like it's not completely obvious how to set a custom securelevel,
> at least one user went the /etc/sysctl.conf way, which has the nasty
> side-effect of preventing the use of /etc/pf.conf.
>
> Should we add more belts and suspenders?
Mark Kettenis writes:
>> Date: Thu, 29 Sep 2016 14:19:43 +0200 (CEST)
>> From: Mark Kettenis
>>
>> This diff adds a WSKBDIO_GETENCODINGS ioctl and uses it to print a
>> list of supported encodings like the old kvm groveling code did. The
>>
"Theo de Raadt" writes:
>> On 2016-09-26, Jeremie Courreges-Anglas wrote:
>>
>> >>> So I think that we agree that EISDIR is more useful, and seems safe from
>> >>> a portability POV. I've built base and x sets on i386, and ajacoutot
>> >>> ran the ports
This diff makes route get and route monitor work. sockaddr_bfd is so we
can play like the other RTAX_* indexes in rti_info of route messages.
OK?
$ route -n monitor
got message of size 128 on Wed Sep 28 21:35:32 2016
RTM_BFD: bidirectional forwarding
18 matches
Mail list logo