On 14/01/16(Thu) 22:14, Martin Pieuchot wrote:
> This should fix the problem various people reported when using urtwn(4)
> over xhci(4). This problem did not disappear but after iwm(4) got
> imported bugs@ reports stopped ;)
>
> It's a screw up in my initial understanding of the documentation. W
One of the checks missing to have an unlocked forwarding path is related
to multicast. We must ensure that the list of multicast groups attached
to an ifp is not modified when the CPU processing a packet is traversing
it.
In order to prepare for such change the diff below introduces a new
functio
Hi,
this diff adds client side certificate checks to httpd. Most parts are straight
forward. But, to transfer the whole certificate authority store to the server
process through the imsg infrastructure I had to change this in an chunked
transfer. Documentation of this feature in httpd.conf.5 is
Hi there,
Here is a patch I received from Harald Dunkel; it ensured the backup
file has the same timestamp as the original file. This behaviour
comforms with emacs' behaviour. I think this patch is also useful for
upstream mg so I post it here.
Index: fileio.c
===
On Thu, Jan 14, 2016 at 8:56 PM, sven falempin
wrote:
>
>
> On Thu, Jan 14, 2016 at 3:14 PM, sven falempin
> wrote:
>
>>
>> On Thu, Jan 14, 2016 at 1:08 PM, sven falempin
>> wrote:
>>
>>> Dear Tech Reader,
>>> Maybe this would be misc but i am trying to avoid some useless answer.
>>> This is op
Below is a trivial patch to support Moxa CP-168U 8-port serial PCI cards.
Bought one from ebay, but learned that only model C168H is currently
supported. Peeked at FreeBSD, found [1] which indicated it would be rather
trivial to add. Built, tested, works.
[1] https://bugs.freebsd.org/bugzilla
+ { /* "Moxa Technologies, CP-168U" */
+ { PCI_VENDOR_MOXA, PCI_PRODUCT_MOXA_CP168U, 0, 0},
+ { 0x, 0x, 0, 0},
+ {
Can you look into filling in the sub-vendor fields?
You can find these using pcidump -
On Fri, 15 Jan 2016 05:33:52 +0100, Stefan Kempf wrote:
> pipe_write() has an orig_resid = uio->uio_resid(). So orig_resid better
> be a size_t also. Looks good otherwise.
>
> ok with the updated diff below?
OK millert@.
- todd
> + /* Moxa Technologies Co., Ltd. PCI I/O Card 8S RS232 */
> + { /* "Moxa Technologies, CP-168U" */
> + { PCI_VENDOR_MOXA, PCI_PRODUCT_MOXA_CP168U, 0, 0},
> + { 0x, 0x, 0, 0},
> + {
> + { PUC_CO
> Can you look into filling in the sub-vendor fields?
Like this you mean? They're the same as the vendor and product fields.
Index: pucdata.c
===
RCS file: /cvs/src/sys/dev/pci/pucdata.c,v
retrieving revision 1.100
diff -u -p -r1.10
> Like this you mean? They're the same as the vendor and product fields.
Thanks. (In general if they are the same, it means this vendor intends
to keep changing the primarly product ID uniquely for each new product).
But we can include them. It's easy enough. Thanks for the diff.
On Fri, Jan 15, 2016 at 12:53:32PM -0700, Theo de Raadt wrote:
> Nope.
>
> The manual page is correct.
>
> > Small correction.
> >
> > ===
> > RCS file: /cvs/src/share/man/man7/hier.7,v
> > retrieving revision 1.150
> > diff -u -p -
Nope.
The manual page is correct.
> Small correction.
>
> ===
> RCS file: /cvs/src/share/man/man7/hier.7,v
> retrieving revision 1.150
> diff -u -p -r1.150 hier.7
> --- hier.77 Jan 2016 08:58:14 - 1.150
> +++ hier.7
Small correction.
===
RCS file: /cvs/src/share/man/man7/hier.7,v
retrieving revision 1.150
diff -u -p -r1.150 hier.7
--- hier.7 7 Jan 2016 08:58:14 - 1.150
+++ hier.7 15 Jan 2016 19:49:16 -
@@ -49,8 +49,6 @@ fi
> Sorry, got confused with file(1) output.
Yes, you will have noticed that file(1) no longer says "static".
The confusion is because static means a few things, historically.
One aspect is whether the program depends on any other shared
libraries.
Another aspect is the code generation model.
Tr
Hello,
I had nothing better to do tonight after work so I read a little in httpd.
I have come up with a patch for i386 and any architecture where off_t !=
size_t.
So on i386 there is this:
uranus$ ./sizetest
off_t = 8
size_t = 4
and I have these files in a directory:
uranus$ ls -lhi
total 126
Ping?
Also, any thoughts on the editline.3 diff[1] sent later in this thread?
[1] http://marc.info/?l=openbsd-tech&m=145150775627284&w=2
Ingo Schwarze wrote:
> Hi Christian & Michael,
>
> Michael McConville wrote on Thu, Dec 24, 2015 at 04:19:03PM -0500:
> > Christian Heckendorf wrote:
>
> >>
On Fri, Jan 15, 2016 at 08:36:05PM +, Peter J. Philipp wrote:
> Hello,
>
> I had nothing better to do tonight after work so I read a little in httpd.
> I have come up with a patch for i386 and any architecture where off_t !=
> size_t.
>
> So on i386 there is this:
>
> uranus$ ./sizetest
> o
On Sat, Jan 16, 2016 at 04:35:16AM +, Peter J. Philipp wrote:
> Hello again,
>
> I couldn't sleep because for some reason my head was spinning around this
> code. In sleep I reviewed what I remembered of this code and noticed two
> things.
>
> 1. My patch was against 5.8 not -current, so i
Hi,
I noticed that the sndiod(8) manual doesn't mention that:
- `sndiod -d' doesn't daemonize
- the `d' flag can be specified multiple times
The wording was taken from syslogd.8.
Index: sndiod.8
===
RCS file: /cvs/src/usr.bin/sndiod
I've been using pf for years and really like it. I accidentally discovered
some undesirable behavior from the rule parser that caused some rules to be
skipped. This has happened to me twice and there was much hair pulling.
The short version is rules starting with # but ending in \ get treated as
> I've been using pf for years and really like it. I accidentally discovered
> some undesirable behavior from the rule parser that caused some rules to be
> skipped. This has happened to me twice and there was much hair pulling.
>
> The short version is rules starting with # but ending in \ get
22 matches
Mail list logo