Developers, please weigh in on what you think the NTPSec project's
goals for the next year ought to be. These goals can be coding
projects ("Move the Python code to Go") process goals ("Halve the size
of the issue list") or project infrastructure goals ("Build a hardware
lab so we can live-test sup
> I'll start the ball rolling with this big one: It's time to move out of C.
I want to threadify things, and taking advantage of that, I want to run at
full wire speed on a gigabit link with a modest server class CPU.
I have test code running. I'm pretty sure it will work. But my test code is
As long as we are in blue sky mode...
What was the name for your attempt to get a GPSD style replay of old data?
Did we ever figure out why that didn't work?
The GPSD code is one way: Input => output. There is no back and forth, no
request => response which changes internal state. Does that
On Fri, Jun 18, 2021, at 6:08 AM Hal Murray via devel wrote:
>
> As long as we are in blue sky mode...
>
> What was the name for your attempt to get a GPSD style replay of old data?
> Did we ever figure out why that didn't work?
It was called testframe IIRC...
https://blog.ntpsec.org/2017/02/22/t
Are there any C to golang or rust transpilers that work
reasonably well? The last time I checked the best rust
transpiler generated rs files that were just shallow glosses
and the golang transpiler was somewhat inadequate and
verbose.
An early-started long-lived tread for each of DNS, clock-
manip
Is it worthwhile improving the current C code to a 'hardened'
programming standard?�
Example
- Joint Strike Fighter standards
https://www.stroustrup.com/JSF-AV-rules.pdf
- NASA JPL standards
https://andrewbanks.com/wp-content/uploads/2019/07/JPL_Coding_Standar
Hal Murray :
> > I'll start the ball rolling with this big one: It's time to move out of C.
>
> I want to threadify things, and taking advantage of that, I want to run at
> full wire speed on a gigabit link with a modest server class CPU.
>
> I have test code running. I'm pretty sure it will w
Hal Murray :
> What was the name for your attempt to get a GPSD style replay of old data?
> Did we ever figure out why that didn't work?
I did. There's a blog post about it:
https://blog.ntpsec.org/2017/02/22/testframe-the-epic-failure.html
--
http://www.catb.org/~esr/";>Eric
Yo MLewis!
On Fri, 18 Jun 2021 20:17:56 -0400
MLewis via devel wrote:
> Is it worthwhile improving the current C code to a 'hardened'
> programming standard?�
>
> Example
> - Joint Strike Fighter standards
> https://www.stroustrup.com/JSF-AV-rules.pdf
That is for C++. And anything JSF (F-35
James Browning via devel :
> Are there any C to golang or rust transpilers that work
> reasonably well? The last time I checked the best rust
> transpiler generated rs files that were just shallow glosses
> and the golang transpiler was somewhat inadequate and
> verbose.
This is still the state of
MLewis :
>Is it worthwhile improving the current C code to a 'hardened' programming
>standard?�
>
>Example
>- Joint Strike Fighter standards
>[1]https://www.stroustrup.com/JSF-AV-rules.pdf
>- NASA JPL standards
>
> [2]https://andrewbanks.com/wp-content/uploads/2019/07
e...@thyrsus.com said:
> I did. There's a blog post about it:
> https://blog.ntpsec.org/2017/02/22/testframe-the-epic-failure.html
>From there:
> One was what in discussion on the mailing list I later tagged "the code-path
> split". There are two kinds of NTP hosts; one uses a kernel facility
12 matches
Mail list logo
