> On Jul 5, 2022, at 1:51 AM, Otto Moerbeek wrote:
>
> On Mon, Jul 04, 2022 at 05:44:33PM -0400, Daniel Dickman wrote:
>
>>
>>
>>> On Sun, 3 Jul 2022, Daniel Dickman wrote:
>>>
>>> On Sat, Jul 2, 2022 at 9:26 PM Ben Fuller wrote:
I noticed Montenegro doesn't have an entry. Pre
On Sat, Jul 02, 2022 at 02:12:56PM +, Visa Hankala wrote:
> Remove the leftovers of the old poll/select mechanism.
> This includes the fields si_seltid and si_flags in struct selinfo.
> They should now always be zero because nothing calls selrecord().
>
> selwakeup() becomes a wrapper for KNOT
On Mon, Jul 04, 2022 at 05:44:33PM -0400, Daniel Dickman wrote:
>
>
> On Sun, 3 Jul 2022, Daniel Dickman wrote:
>
> > On Sat, Jul 2, 2022 at 9:26 PM Ben Fuller wrote:
> > >
> > > I noticed Montenegro doesn't have an entry. Presumably this file hasn't
> > > been updated since before 2006!
> >
On Mon, Jul 4, 2022 at 8:09 PM Daniel Dickman wrote:
>
>
>
> > On Jul 4, 2022, at 8:07 PM, Ben Fuller wrote:
> >
> > On Mon, Jul 04, 2022 at 19:30:19 -0400, Daniel Dickman wrote:
> Maldive Islands:Male
> >>> A more common name is just "{The }Maldives".
> >>
> >> I don't think so. See this a
Hi,
Once again, I am trying to change our approach to TSC sync testing to
eliminate false positive results. Instead of trying to repair the TSC
by measuring skew, we just spin in a lockless loop looking for skew
and mark the TSC as broken if we detect any.
This is motivated in part by some multi
On Mon, Jul 04, 2022 at 08:04:14PM -0400, Daniel Dickman wrote:
> The patch below removes the (small) amount of code used to identify NexGen
> CPUs. I'm doubtful that these CPUs would be supported anymore and we don't
> do anything with the information once we identify a NexGen CPU.
>
> The code
> On Jul 4, 2022, at 8:07 PM, Ben Fuller wrote:
>
> On Mon, Jul 04, 2022 at 19:30:19 -0400, Daniel Dickman wrote:
Maldive Islands:Male
>>> A more common name is just "{The }Maldives".
>>
>> I don't think so. See this article:
>> https://www.bbc.com/news/magazine-18233844
>>
>> which s
The patch below removes the (small) amount of code used to identify NexGen
CPUs. I'm doubtful that these CPUs would be supported anymore and we don't
do anything with the information once we identify a NexGen CPU.
The code does a division early in the i386 boot process (in locore0) and
checks t
On Mon, 4 Jul 2022, Ben Fuller wrote:
> On Mon, Jul 04, 2022 at 17:44:33 -0400, Daniel Dickman wrote:
> > I had some time on my hand and took a stab on this. A few notes:
>
> Ach, you beat me to sending a patch. I made almost exactly the same changes as
> you have. I've noted some of my though
On Mon, Jul 04, 2022 at 05:44:33PM -0400, Daniel Dickman wrote:
> I also noticed NetBSD removed The Hague as a capital of The Netherlands,
> but I disagree with that. Maybe some of the Dutch folks on this mailing
> list can weigh in which is right.
Amsterdam is the capital, The Hague is the seat
On Mon, Jul 04, 2022 at 11:15:24PM +0200, Claudio Jeker wrote:
> On Mon, Jul 04, 2022 at 01:28:12PM -0500, Scott Cheloha wrote:
> > Hi,
> >
> > Couple things:
> >
> > [...]
>
> I don't like the introduction of all these local variables that are just
> hard to follow and need extra code pathes. H
On Sun, 3 Jul 2022, Daniel Dickman wrote:
> On Sat, Jul 2, 2022 at 9:26 PM Ben Fuller wrote:
> >
> > I noticed Montenegro doesn't have an entry. Presumably this file hasn't
> > been updated since before 2006!
>
> These files could use a big overhaul and are very dated.
>
> In the below, make
On Mon, Jul 04, 2022 at 01:28:12PM -0500, Scott Cheloha wrote:
> Hi,
>
> Couple things:
>
> - Use additional timespec variables to make our intent more obvious.
>
> Add "elapsed", "utc_offset", and "utc_start".
>
> "roff" is a confusing name, "utc_offset" is better.
>
> Yes, I know the c
When the fdt does not provide a list of brightness states, pwmbl(4)
builds a 256 state ramp (i.e. state[i] = i with 0 <= i < 256).
The following diff keeps that behaviour, but gets rid of the malloc
call for that ramp, since the values are trivially known.
Compiles but not tested due to the lack
Hi,
Couple things:
- Use additional timespec variables to make our intent more obvious.
Add "elapsed", "utc_offset", and "utc_start".
"roff" is a confusing name, "utc_offset" is better.
Yes, I know the clock is called CLOCK_REALTIME, but that's a
historical accident. Ideally they woul
On Mon, Jul 04, 2022 at 05:22:51PM +, Klemens Nanni wrote:
> There's not just bridge(4) but veb(4) also, but netstart(8) does not treat
> either of them specially, so stick to just "bridges" without Xr.
>
> Swap one mention for consistency with the rest.
>
> Feedback? OK?
>
i agree this mak
Make it look like a proper usage.
365:ifmstart "" "aggr trunk svlan vlan carp pppoe tun tap gif etherip gre egre
nvgre eoip vxlan pflow wg"
370:ifmstart "aggr trunk svlan vlan carp pppoe"
397:ifmstart "tun tap gif etherip gre egre nvgre eoip vxlan pflow wg"
Feedback? OK?
Index: netstart
===
There's not just bridge(4) but veb(4) also, but netstart(8) does not treat
either of them specially, so stick to just "bridges" without Xr.
Swap one mention for consistency with the rest.
Feedback? OK?
Index: netstart.8
===
RCS file
Hi
Thanks for your reply.
Yes, sure. This fix would also be correct.
Best Regards
Sibar Soumi
Software Developer
achelos GmbH | Vattmannstraße 1 | 33100 Paderborn | GERMANY
sibar.so...@achelos.de | www.achelos.de | www.iot.achelos.com | Follow us:
LinkedIn | XING | YouTube
-Ursprüngl
19 matches
Mail list logo
