Were the two drivers different?
On Tue, Jun 21, 2016 at 6:33 AM Eric S. Raymond wrote:
> Refclock 38 (the Hopf 6021 serial driver) was redundant with a mode of
> refclock 8, the parse drive, that also supports the 6021.
>
> I also removed the Hopf 6039 refclock due to a proprietary-driver
> depe
Cool.
I need to fill in my ignorance about the parse driver, and prompt a
discussion about which other drivers can be superseded by additions to the
parse driver.
..m
On Fri, Jun 24, 2016 at 9:42 PM Eric S. Raymond wrote:
> Mark Atwood :
> > Were the two drivers different?
>
Is getaddrinfo_a() in RTEMS? QNX? BSD?
On Sun, Jun 26, 2016 at 7:06 AM Eric S. Raymond wrote:
> Eric S. Raymond :
> > > What would you do if we discovered a case where we wanted it?
> >
> > Cry a lot. Then add logic to force synchronous DNS when memlocking is
> > selected, and document this
- Original message -
From: scan-ad...@coverity.com
Subject: New Defects reported by Coverity Scan for ntpsec
Date: Sat, 25 Jun 2016 20:01:41 -0700
Hi,
Please find the latest report on new defect(s) introduced to ntpsec
found with Coverity Scan.
3 new defect(s) introduced to ntpsec found
Thank you Eric. Have read, am pondering, and welcome other people to weigh
in.
..m
On Tue, Jun 28, 2016 at 8:30 PM Eric S. Raymond wrote:
> In recent discussion of the removal of memlock, Hal Murray said
> "Consider ntpd running on an old system that is mostly lightly loaded
> and doesn't have
this is was discussed heavily in cii meetings. will expand later. on my
phone
On Wed, Jun 29, 2016, 12:03 PM Hal Murray wrote:
>
> fallenpega...@gmail.com said:
> > Thank you Eric. Have read, am pondering, and welcome other people to
> weigh
> > in.
>
> The big picture question that comes to
Cool! Thank you Hal.
On Fri, Jul 1, 2016 at 9:53 PM Hal Murray wrote:
> I just pushed the code.
>
> You will get things like this:
>
> 57570 76638.360 3600 19.221 29.499 1541 0 0 0 2984 288288 2123 0 8428
> 57570 80238.357 3600 20.812 25.956 1062 0 0 0 3024 246608 2274 0 12652
> 57570 83838.357
..m
--
Mark Atwood
Project Manager pro tem, The NTPsec Project
On Thu, Jul 14, 2016, at 12:36, Looney, Caeley M (UNC) wrote:
> Good Afternoon!
>
> I work with David Wheeler at IDA on the CII Badging Process, and I
> noticed that NTPsec is making great progress towards gettin
Re IRIG being "primary time source in high end audio and video work"
You are kidding me. SIgh.
Can you expand on that for me please?
..m
On Sat, Jul 23, 2016 at 5:42 PM Gary E. Miller wrote:
> Yo Eric!
>
> On Sat, 23 Jul 2016 15:32:56 -0400 (EDT)
> e...@thyrsus.com (Eric S. Raymond) wrote:
>
I know that IRIG is still live, but... is this particular application
feeding the IRIG into a NTPD?
On Sat, Jul 23, 2016 at 7:44 PM Gary E. Miller wrote:
> Yo Mark!
>
> On Sun, 24 Jul 2016 01:30:05 +0000
> Mark Atwood wrote:
>
> > Re IRIG being "primary time source i
8:07 PM Gary E. Miller wrote:
> Yo Mark!
>
> On Sun, 24 Jul 2016 02:52:00 +
> Mark Atwood wrote:
>
> > I know that IRIG is still live, but... is this particular application
> > feeding the IRIG into a NTPD?
>
> Not yet, but that was what I quoted. I believe
the fact that it was an obsolete sound card was itself reason to kill it.
leave it killed, and fossilized in the git history.
enjoy your vacation, eric.
..m
On Sun, Jul 24, 2016, 4:36 AM Eric S. Raymond wrote:
> Gary E. Miller :
> > > Yes. But there's still the issue that the IRIG driver I re
Can the palisade/trimble driver be replaced with a parse driver?
On Sun, Jul 31, 2016 at 4:23 PM Eric S. Raymond wrote:
> Hal Murray :
> >
> > e...@thyrsus.com said:
> > > Drivers that very well might fail the ten-year test: truetime,
> magnavox,
> > > palisade, oncore, jupiter.
> >
> > Palisade
Good point.
On Sun, Jul 31, 2016, 8:13 PM Eric S. Raymond wrote:
> Hal Murray :
> > > Can the palisade/trimble driver be replaced with a parse driver?
> >
> > I doubt it, but I'm far from familiar with the parse driver.
> >
> > Based on Eric's previous comments, the parse driver handles devices
If we make this change, framing it as "it's how chronyd has been doing it
for the past N years" makes it a much easier sell.
Especially if we can make the file format the same.
What principled objections would the hardcore time nerds have? We do have
to keep their needs firmly in mind.
..m
On
This looks great, Christian.
Is there anything we need to do to have our buildbot system test it?
..m
On Tue, Aug 9, 2016 at 8:10 AM Christian Ehrhardt <
christian.ehrha...@canonical.com> wrote:
> Hi,
> I wanted to give the ML a ping as well about this, so that not only the
> Pull Request is ex
It is time for another point release.
I've received enough private communications from people who are
successfuilly running lab machines on tip, and people who are successfully
running lab machines on the previous point release, and that my work with
the CII is illuminating the need for proof of m
Start with the warning, while we think of a solution.
Thank you, Hal.
On Thu, Aug 11, 2016 at 4:05 PM Hal Murray wrote:
>
> I think I have found the problem.
>
> minsane defaults to 1 so ntpd is "happy" as soon as a server gets past the
> individual server filtering.
>
> I don't see any simple
The long term, I like the DNS for solutions to this kind of problem. But,
under what name?
Other solutions are putting it in AWS & Cloudfront, and in their
equivalents at AZR and at GCS. To take that route, I would want to arrange
that Amazon, Microsoft, and Google donate that capacity. The th
On Mon, Aug 15, 2016 at 8:14 AM Eric S. Raymond wrote:
> We don't need all the past leap files. The data is only ever modified by
> appending a line.
>
>
I'm a crazy competitionist. Git resources need histories.
OTOH, it looks like the eggert/tz repo already exists. On the other other
hand, it
I have no overrule on this point. Pray continue.
And welcome back, Hal.
On Thu, Aug 18, 2016 at 8:01 PM Eric S. Raymond wrote:
> Heads up, Mark! Policy sanity check requested.
>
> Hal Murray :
> >
> > e...@thyrsus.com said:
> > > This does, however, leave me with a question: How are we doing
Ok. Thank you Hal and Eric.
Eric, remove the existing traps code from NTPsec.
We will build a snmp subagent later, when we see user need..
..m
On Thu, Sep 8, 2016 at 4:23 AM Eric S. Raymond wrote:
> Hal Murray :
> > I don't know of any reason not to remove it, especially if it is broken.
>
make sure they are defined by the posix level we are targeting
On Mon, Sep 12, 2016, 4:01 PM Eric S. Raymond wrote:
> Hal Murray :
> >
> > Our current code has ifdefs for SIGQUIT and several others. That may
> have
> > been leftover from Windows.
> >
> > man 7 signal says:
> >First the
we are not making Rust part of NTPsec right now. but maybe in a year or
so, at this pace
On Mon, Sep 12, 2016, 12:54 PM Hal Murray wrote:
>
> e...@thyrsus.com said:
> > Every Unix-like system, for sure. Checking...Rust has a Windows port. So
> > does Go. Are there any other tarhets you're wor
Go has a GC. the Go standard library and the complier implementation will
always be utterly controlled by Google, and will be full of Google magic.
Go's usecase is to solve Google's problems, and can basically be modelled
as "compiled Python that forcefully avoids all of the kinds of typos that
Dr
Hi!
I have added a draft of the release checklist to devel/hacking.txt
Please look it over, and give feedback.
My next rev of it will include the actually command line commands..
Thank you!
..m
> -Original Message-
> From: Eric S. Raymond [mailto:e...@thyrsus.com]
> Sent: Tuesday, Sep
we need to be packaged for debian, rasbian, ubuntu, gentoo, redhat, and
suse for 1.0 and be working towards getting into their distribution system
(apt, yum, etc)
On Wed, Oct 5, 2016, 6:27 AM Eric S. Raymond wrote:
> Heads up, Mark! Possible strategy and external-relations issues.
>
> I think w
I want to have a conversation with our new funding sources about their
expectations, as i ponder Case Nightmare Red/Green/Blue
On Wed, Oct 5, 2016, 10:08 AM Eric S. Raymond wrote:
> Mark Atwood :
> > we need to be packaged for debian, rasbian, ubuntu, gentoo, redhat, and
> > suse
Hi!
I've been following this discussion.
We should remove the GPSD JSON driver from NTPsec.
It is an attractive nuisance. The SHM driver, possibly with improvements,
is a better interface between NTPsec and GPSD.
..m
On Thu, Oct 20, 2016 at 2:53 PM Eric S. Raymond wrote:
> Hal Murray :
> >
Hi!
I would like to formalize a policy about development communication, which
can be touch-in-cheek expressed as:
If it wasn't in email, it didn't happen.
It is currently popular and trendy to use a "chat-centric" developer
communication model. Chat-centric dev does make sense for rapidly chang
Got it, thanks!
On Fri, Oct 21, 2016, 5:20 PM Gary E. Miller wrote:
> Yo Mark!
>
> On Fri, 21 Oct 2016 21:00:24 +0000
> Mark Atwood wrote:
>
> > We should remove the GPSD JSON driver from NTPsec.
>
> I spend 40 minutes last night trying to get the GPSD SHM driver r
On Thu, Nov 3, 2016 at 11:54 AM Hal Murray wrote:
> > One wonders, for example, why exactly one response (readstats) has a
> binary
> > payload
>
> My guess is history. It's probably left over from before the mode6/mode7
> stuff got sorted out and Mills decided that mode6 should be all text.
>
>
https://hypothesis.readthedocs.io/en/latest/
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
On Sun, Nov 27, 2016 at 1:00 AM Achim Gratz wrote:
> Eric S. Raymond writes:
> > OK, there are two ways we can handle this.
>
> The third way is building a hash table that maps each possible unique
> prefix to the actual full-length command.
>
>
I was on a project years ago that did that (minimal
Hello Sanjeev,
Feel free to edit them out the docs, and we will review them in pull
requests.
Thank you for all your work!
..m
On Thu, Dec 1, 2016 at 10:42 AM Eric S. Raymond wrote:
> Sanjeev Gupta :
> > While re-reading docs today, I came across references to asymmetric
> > key crypto; do I un
I am signing up NTPsec.
On Thu, Dec 1, 2016 at 8:13 PM Sanjeev Gupta wrote:
>
> https://security.googleblog.com/2016/12/announcing-oss-fuzz-continuous-fuzzing.html
>
> ...
> OSS-Fuzz is launching in Beta right now, and will be accepting
> suggestions for candidate open source projects. In order
On Sat, Dec 10, 2016 at 11:00 AM Eric S. Raymond wrote:
>
> Pretty much every distribution in the universe ships a default
> ntp.conf with a restriction sectio that looks like this:
> [...]
> I'm requesting comment on the following behavior change:
> (1) Make these the default restrictions at sta
I will see if I can get us a Z/machine target
On Mon, Dec 12, 2016 at 11:53 AM Gary E. Miller wrote:
> Yo Eric!
>
> On Mon, 12 Dec 2016 14:35:21 -0500
> "Eric S. Raymond" wrote:
>
> > Gary E. Miller :
> > > I would be nice to have a BIGENDIAN host as a buildbot worker.
> >
> > We don't? Oh, th
Suggestion: '?' to display all the keystroke commands.
On Tue, Dec 13, 2016 at 8:00 AM Eric S. Raymond wrote:
> In response to requests by Hal and Gary, ntpmon now has some keystroke
> commands.
>
> a:: Change peer display to apeers mode, showing association IDs.
>
> n:: Toggle display of hostn
I think we are now bikesheding. Let someone else driveby command aliases
for ntpmon.
Does anyone else have any ideas for any other data displays to add to it?
..m
On Tue, Dec 13, 2016 at 11:36 AM Gary E. Miller wrote:
> Yo Eric!
>
> On Tue, 13 Dec 2016 14:30:26 -0500
> "Eric S. Raymond" wrot
If Hal thinks it should go, it should go. Thank you Hal!
On Mon, Dec 19, 2016 at 4:26 AM Eric S. Raymond wrote:
> Hal Murray :
> >
> > There is a showall parameter to the worker printout code for the peers
> > display in ntpq and ntpmon.
> >
> > ntpmon has the s keyboard command to toggle it.
Hi!
Things are looking good for the 0.9.6 release.
Everyone, please update .../NEWS with any significant work and improvements
you have landed.
If you you any reason not to tag and release 0.9.6 in the next few days,
please let us know.
Thank you, everyone!
..m
r, --minor, and --point
>options.
>
>
> I can see commit 76e974cf
>
> sanjeev@X201wily:~/SRC/ntpsec$ git show 76e974cf
> commit 76e974cf16da204c6da73d6fa204677d94990088
> Author: Mark Atwood
> Date: Fri Dec 30 21:16:45 2016 +
>
> version 0.9.6
>
>
Hi!
We've had a couple of cases recently where potential contributors show up
on gitlab.com with a request to join the gitlab project as a developer.
Our preferred way to interact with additional contributors is via gitlab
pull requests.
However, people may be asking to join the gitlab project s
Granting someone Guest access does add them to
https://gitlab.com/groups/NTPsec/group_members so it's not just a no-op.
On Tue, Jan 3, 2017 at 11:24 AM Eric S. Raymond wrote:
> Mark Atwood :
> > I think it may be productive to hand out Guest level access just for the
> > ask
Hi!
My friend Greg Rubin, who does security work for Amazon, took at quick look
at NTPsec 0.9.6, and asks the following queston:
"Why does ntpkeygen pass a low entropy ignored seed into SystemRandom? It's
ignored, so it doesn't matter, but it's the type of error which concerns
me."
..m
_
Pyflakes test requirement has been added to .../devel/hacking.txt
On Wed, Jan 4, 2017 at 2:47 PM Hal Murray wrote:
> > We do not take patches that fail pyflakes.
>
> If that's the policy, it should be announced and documented.
>
> Are there other similar policies?
>
>
> --
> These are my opinion
Thank you Achim
On Wed, Jan 4, 2017 at 11:53 AM Achim Gratz wrote:
>
> I've kept to rasPi running through the leap second.
>
> The first was following the PTB servers as a stratum2 and monitoring
> both a DCF77 and a GPS (via USB). This one correctly announced the leap
> second and kept the tim
> what is pep8?
https://pypi.python.org/pypi/pep8
pep8 is a tool to check your Python code against most of the style and
formatting conventions in "PEP 8"
A "PEP" is a "Python Enhancement Proposal". Think of it as an "RFC" in the
Python Community. PEP 8 is a specification of a "best practices" f
On Wed, Jan 4, 2017 at 4:50 PM Daniel Poirot wrote:
> Uncrustify is both useful and has a clever name!
Running uncrustify against NTPsec is good idea, but it needs to be a flag
day, because it will be a huge patch.
..m
___
devel mailing list
devel@n
Did Dr Mills have a preferred C style? If he did, was it not terrible?
What is everyone else's preferred C indent style?
I have my own favorite, but I'm not the one who has to read and rework the
C code.
..m
On Thu, Jan 5, 2017 at 11:18 AM Daniel Poirot wrote:
> Before long, everyone will be
Miller wrote:
> Yo Mark!
>
> On Thu, 05 Jan 2017 19:32:55 +
> Mark Atwood wrote:
>
> > What is everyone else's preferred C indent style?
>
> I'm stuck in the past, with s slightly modified K&R style.
>
> > I have my own favorite, but I'm
Interesting. He makes good points, and I have earned a living coding in
Ada, myself. But all that said, there are sufficient good reasons not to
port to Ada. Well, unless and until the DOD, the ARPA, or the
Physikalisch-Technische Bundesanstalt want to pay us enough to do it, at
which point it can
While I was reading up on uncrustify, opensource.com posted an article
about clang-format.
https://opensource.com/article/17/1/coding-style
Does anyone have any comments or experience comparing them?
I will probably spend the time to play with both of them, and run diffs of
the output of each.
On Sun, Jan 8, 2017 at 4:47 PM Gary E. Miller wrote:
>
> Yes, threads will help a lot. I remember when Apache and Mysql started
> to use good threading. It really helps when you can use all 16 cores
> on a CPU instead of just one.
>
MySQL is not something I would hold up as an example of good
On Sun, Jan 8, 2017 at 6:47 PM Gary E. Miller wrote:
>
> I think not. Most of the threads will be servering clients. All a
> thread needs to serve a client is the incoming packet and the current
> local time. No locks needed for that.
>
> The client threads will prolly need some locking, but I
I think that the difference between uncrustify and clang-formatter is that
clang-formatter actually uses the clang parser, so it should be able to
injest any valid C.
But, it will be an interesting experiment.
..m
On Fri, Jan 13, 2017 at 9:09 AM Eric S. Raymond wrote:
> Mark Atw
I just spent an hour talking with Andrew Bartlett of Catalyist. He is the
author of the msntp feature in NTP Classic.
The feature is actually in place for Samba clients. Given that, we likely
will want to put it back, but do it better than how it was originally
hammered into Classic.
He hope w
If you want a randomly different thing to relaxation hack on with Go,
instead of an IRC server, consider a Matrix.ORG server. A Matrix.org
server that is binary and performant actually has a good chance of
significant uptake. But, your choice, your project.
Thank you for your work, Eric. I ha
I prefer :: tagged IPv6 addresses for IPv4 addresses. No need for a
redundant flag.
On Mon, Jan 23, 2017 at 12:48 PM Gary E. Miller wrote:
> Yo Hal!
>
> On Sun, 22 Jan 2017 20:10:36 -0800
> Hal Murray wrote:
>
> > All the MRU list needs is a flag to specify if the IP address
> > is 4 or 6
There is still the threaded DNS lookup bug that Hal discovered, and his
proposed new threaded DNS design.
On Mon, Jan 23, 2017 at 2:11 PM Eric S. Raymond wrote:
> Gary E. Miller :
> > > 3. The JSON refclock is a mess that has never worked quite right,
> > > without a clear purpose in life. I'd p
If we are going to have an SSL dependency, I have a pretty strong
preference towards WolfSSL
if we are going to have an OpenSSL dependency, it needs to be to the latest
stable OpenSSL release.
What would be using an SSL library for, that libsodium does not already
provide?
What all are we using
Can libsodium upstream take a pull request that adds the hash functions
that we need?
On Fri, Jan 27, 2017 at 7:40 AM Eric S. Raymond wrote:
> Hal Murray :
> > We currently have 2 and 1/4 crypto packages. That seems like the sort of
> > things you like to clean up.
>
> Yes.
>
> > I would have s
How hard would the following be?
Just go ahead and add SHA256 to NTPsec
then
Write an I-D modifying the NTP4 protocol documenting it.
then
Write a patch to NTP classic for it. (yes, I know, icky code)
..m
___
devel mailing list
devel@ntpsec.org
http://
MAC.
>
> On 1/27/17, Mark Atwood wrote:
> > How hard would the following be?
> >
> > Just go ahead and add SHA256 to NTPsec
> > then
> > Write an I-D modifying the NTP4 protocol documenting it.
> > then
> > Write a
AM Gary E. Miller wrote:
> Yo Mark!
>
> On Fri, 27 Jan 2017 18:14:15 +
> Mark Atwood wrote:
>
> > If we are going to have an SSL dependency, I have a pretty strong
> > preference towards WolfSSL
>
> It may be the best, but it is not in Gentoo. I suspect few distr
iller wrote:
> Yo Mark!
>
> On Fri, 27 Jan 2017 18:17:40 +
> Mark Atwood wrote:
>
> > Can libsodium upstream take a pull request that adds the hash
> > functions that we need?
>
> My understanding is that they considered md5 and sha1 too dangerous to
> use and
27, 2017 3:21 PM, "Eric S. Raymond" wrote:
>
> Mark Atwood :
> > We do need to get wacking on the weeds on removing more of this thicket.
>
> Here are our constraints:
>
> * Daniel has stated that he prefers the OpenSSL implementations of MD5 and
> SHA-1. He&#
I like the idea of removing more IPv4 specific code.
If we do, can we still get arrival timestamp from the kernel?
How do standard display functions display v6 mapped v4 addresses? How do
we want them displayed?
Are there any places left in the code that are storing addresses in
packed-4-octet
How stable is their ID?
How much effort will it be to add it to NTPsec?
My next strawman proposal that we add it NTPsec as soon as convenient, but
make it an option for now.
..m
On Fri, Jan 27, 2017 at 10:40 AM Mark Atwood
wrote:
> Ok, thanks for the update.
>
> ..m
>
> On Fr
I think what we will do is implement the new "legacy" auth protocol as soon
as Daniel feels comfortable with it, and implement new new secure time
protocol on, again, as soon as Daniel feels comfortable and then delivers
the code.
Dropping support for the legacy legacy MD5 method is not on our roa
they don't require updating
On Sat, Jan 28, 2017, 5:38 PM Hal Murray wrote:
>
> Do they need to be updated? I just noticed one that was 2015.
>
> Should that go on the release checklist?
>
>
> --
> These are my opinions. I hate spam.
>
>
>
> ___
> de
Is there a reason to keep dumbclock? Maybe it exists as a starting
framework for when someone wants to write a new clockdriver?
..m
On Sun, Jan 29, 2017 at 5:36 AM Eric S. Raymond wrote:
> Here are the full current stats:
>
> all71320 (100.00%) in 298 files
> c 60694
I wonder if we should just start recommending that people plug one of Keith
Packard's ChaosKey's into a USB port on their NTP boxes.
https://keithp.com/blogs/chaoskey/
I just leave one plugged into my main working NUC all the time.
..m
On Sun, Jan 29, 2017 at 5:15 PM Hal Murray wrote:
>
> g..
PM Gary E. Miller wrote:
> Yo Mark!
>
> On Sun, 29 Jan 2017 07:58:24 +
> Mark Atwood wrote:
>
> > > Do they need to be updated? I just noticed one that was 2015.
>
> > they don't require updating
>
> US Copyright is now generally 70 years after t
Kill it
On Sun, Jan 29, 2017 at 9:05 PM Eric S. Raymond wrote:
> Mark Atwood :
> > Is there a reason to keep dumbclock? Maybe it exists as a starting
> > framework for when someone wants to write a new clockdriver?
>
> Actually, I only left dumbclock in because you said
My inclination is that when more clock types show up, they get a driver
running in it's own process space, and exporting a SHM buffer.
The problem with covering existing drivers to that is... testing them.
..m
On Sun, Jan 29, 2017 at 10:49 PM Eric S. Raymond wrote:
> Hal Murray :
> > It's not
Hello Hugh,
No need to be off list, we like to work in public as much as possible.
Yes, please make those connections, and prod your friends on this issue.
..m
On Mon, Jan 30, 2017 at 12:37 AM Hugh Blemings wrote:
> Hiya,
>
> /me de-lurks
>
> On 30/01/2017 19:28, Eric S. Raymond wrote:
> > Ha
That's... complicated.
We don't need to have a notice attached to every file, because there is a
copyright notice attached to the project as a whole, and there is a notice
attached to each repo. Individual files generally don't each need their
own notice, since individual files generally no longe
ial FOSS audit tools like Protecode and BlackDuck will match a
> snippet and attribute to the FOSS project.
>
>
> On Jan 30, 2017, at 12:30 PM, Mark Atwood wrote:
>
> That's... complicated.
>
> We don't need to have a notice attached to every file, because there is
at 11:16 AM Daniel Poirot wrote:
> What's fun is hearing "No copyright needed, I got it off Stack Overflow!"
>
> ...wrong
>
>
> On Jan 30, 2017, at 12:58 PM, Mark Atwood wrote:
>
> Commercial FOSS audit tools like Protecode and Blackduck will be able to
>
I will sweep through the documentation files, and add the correct forms and
content for the copyright and license markings.
..m
On Mon, Jan 30, 2017 at 12:02 PM Gary E. Miller wrote:
> Yo Mark!
>
> On Mon, 30 Jan 2017 18:58:55 +0000
> Mark Atwood wrote:
>
> > When you cr
No objections from me.
On Thu, Feb 16, 2017 at 1:13 PM Gary E. Miller wrote:
> Yo All!
>
> Currently waf has:
>
> --enable-debug (ignored)
> --disable-debug Disable debugging code
> --enable-debug-gdb Enable GDB debugging symbols
> --enable-debug-timing Collect timing s
My own preference would be
ntploggps
ntplogheat
ntpmakeheat
eg. {prefix}{verb}{thenoun}
"temp" is too overloaded as "temporary".
Short is not needed, the day of 15 character filenames and typing over a
110bps ASR33 with 500ms of lag are far in the distant past.
But that's just a preference of
> What's the actual problem with including ntpviz in the standard install
Anything that triggers a surprise dependency to load libx, a font renderer,
or a font pack onto a ssh & text console -only host gets a veto from me.
..m
On Tue, Feb 21, 2017 at 2:14 PM Eric S. Raymond wrote:
> Hal Murr
Call it "therm" or "thermal" then, instead of "heat" or "temperature"?
On Tue, Feb 21, 2017 at 2:24 PM Gary E. Miller wrote:
> Yo Mark!
>
> On Tue, 21 Feb 2017 22:12:26 +
> Mark Atwood wrote:
>
> > My own preference would be
>
++
On Tue, Feb 21, 2017 at 2:26 PM Gary E. Miller wrote:
> Yo Mark!
>
> On Tue, 21 Feb 2017 22:20:57 +0000
> Mark Atwood wrote:
>
> > > What's the actual problem with including ntpviz in the standard
> > > install
> >
> > Anything that t
I'm ready.
On Sun, Mar 5, 2017 at 12:26 PM Eric S. Raymond wrote:
> Mark has asked me to try to graft onto our repository a branch
> representing NTP Classic development since the fork.
>
> For ugly reasons that I will detail in later mail, I think this is
> just barely doable, but not with conv
Thank you so much, Sanjeev.
Do you know if your talk will be video recorded?
..m
On Sun, Mar 12, 2017 at 2:45 PM Sanjeev Gupta wrote:
> Hi,
>
> FossAsia is a large(ish) hacker conference in Singapore, now 4 or 5 years
> old. I thought of a short talk on NTPsec.
>
> The blurb (which is not pos
Sanjeev,
You can see a video of Susan's recent talk at
https://www.oreilly.com/ideas/the-internet-is-going-to-fall-down-if-i-dont-fix-this-susan-sons?imm_mid=0eb1c1&cmp=em-webops-na-na-newsltr_security_20161129
and her slide deck is at
http://slides.com/hedgemage/savingtime
Which GPS receiver pu
Are there any worrisome performance or conformance issues with time64_t on
any of our 32bit targets?
..m
On Mon, Mar 13, 2017 at 5:03 PM Hal Murray wrote:
>
> I have the leap second code mostly cleaned up. It builds but the tests
> still
> get several errors. There is no reference to ntpcal_x
A lot of useful work has gone into NTPsec since the 0.9.6 release on
2016-12-30, and we have some good momentum right now, which we want to
demonstrate.
To that end, I would like to cut the 0.9.7 release a week from today, on
2017-03-21.
..m
___
devel m
$ git log touch-20170321.1
> commit 899f8859082c6de768caf84daad26aeceb3143fd
> Author: Mark Atwood
> Date: Tue Mar 21 22:15:26 2017 +
>
> version 0.9.7
>
> Signed-off-by: Mark Atwood
>
> Mark, did you create this by hand for some reason? grep-find isn't showing
> anything that looks
at some point be satiated; but those
> who torment us for our own good will torment us without end, for they
> do so with the approval of their consciences.
> -- C. S. Lewis
> ___
> devel mailing list
> devel@ntpsec.org
> http:/
topology, or in the local hypervisor or
container topology.
And yes, can someone Not Me ask on the NTP list?
..m
On Fri, Mar 31, 2017 at 12:31 PM Gary E. Miller wrote:
> Yo Mark!
>
> On Fri, 31 Mar 2017 19:19:04 +
> Mark Atwood wrote:
>
> > I would like some discussion
ble.
..m
On Fri, Mar 31, 2017 at 1:42 PM Gary E. Miller wrote:
> Yo Mark!
>
> On Fri, 31 Mar 2017 20:06:32 +
> Mark Atwood wrote:
>
> > I'm inclined to say drop the feature.
>
> Me too, but only as a me too. Don't blame me!
>
> > Yes defen
awesome!
On Mon, Jan 25, 2016 at 2:27 AM Eric S. Raymond wrote:
> An encouraging news bulletin because things have been a bit slow over the
> holidays:
>
> I'm now able to do Coverity scanning again after a hiatus of about three
> weeks due to my cov-build tools going stale when I ubgraded to Ub
Hi!
If the buildbot status makes me happy, and nobody chimes in with a blocker,
I will tag and release ntpsec 0.9.1 at about 7pm PST this evening 2016-01-25
Thank you, everyone.
..m
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailma
On Mon, Jan 25, 2016 at 11:39 AM Mark Atwood
wrote:
> If the buildbot status makes me happy, and nobody chimes in with a
> blocker, I will tag and release ntpsec 0.9.1 at about 7pm PST this evening
> 2016-01-25
>
>
Hi!
I'm happy with buildbot, I created a clean VM and cl
No worries. Fix 2845 2882 2772 2948 2939 2935 2937 2814 2829 2887 2958
2962, and we will call that 0.9.2
Thanks!
..m
On Mon, Jan 25, 2016 at 6:37 PM Eric S. Raymond wrote:
> Hal Murray :
> > The real question is are we going to track fixes from NTP Classic and if
> so
> > who, how, when, etc?
1 - 100 of 295 matches
Mail list logo
