___
> devel mailing list
> devel@ntpsec.org
> http://lists.ntpsec.org/mailman/listinfo/devel
--
- *John D. Bell*
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
This is a test message to the mailing list, to diagnose apparent failure
to deliver, etc.
It can safely be ignored.
- *John D. Bell*
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
, 'itemset', 'lookahead', 'solved'
(shift/reduce conflicts), or 'all'
Does any of this help?
- *John D. Bell*
On 06/22/2018 02:24 PM, Eric S. Raymond via devel wrote:
> Hal Murray :
>> e...@thyrsus.com said:
>>> If we had intr
I've not looked at the build system configuration *at all* closely
(perhaps a more accurate reading would be "at all"), but can't you just
configure it to not use the offending -W switch when analyzing/compiling
the parser's C code?
- *John D. Bell*
On 06/18/2018
Gentlemen,
This was sent to "cont...@ntpsec.org", and I thought it should end
up to your attention.
- JDB
Forwarded Message
Subject:[cont...@ntpsec.org] draft-ietf-ntp-ma and
draft-ietf-ntp-using-nts-for-ntp in NTPSec?
Date: Tue, 27 Feb 2018 04:25:23 +
resultant
"versions"?
This _might_ give you the ability to see the 'shape' of the code
under the various assumptions about supported kernel features, etc.
- *John D. Bell*
On 12/03/2017 05:17 PM, Eric S. Raymond via devel wrote:
> Hal Murray :
>> e...@th
either.
Eric, since you are an expert in YACC-based systems, would it be worth
the effort to write such an AST-generating parser, and using *that*?
Maybe not to the level of a releasable tool, but to get beyond the 80%
point? Or does that fall under
eleased versions should be in a "tried
and true" language (_even_ with the security/reliability considerations.)
My $0.02 worth.
- *John D. Bell*
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
7/2017 03:59 PM, Gary E. Miller via devel wrote:
> Yo Eric!
>
> On Mon, 7 Aug 2017 15:51:13 -0400
> "Eric S. Raymond via devel" wrote:
>
>> John D. Bell :
>>> I thought that one necessity before 1.0 were at least preliminary
>>> "packaged"
On 08/07/2017 12:58 PM, Eric S. Raymond via devel wrote:
> Summary:
>
> * We need to start working towards a 1.0 release no later than 28 September.
>
> * I need our senior devs to identify any release-blocker issues
> and tell me what they think our pre-release priorities shou
Gentlemen - I got this via "cont...@ntpsec.org". Don't have the nsec
right now to figure out if his is a lost cause or not - JDB
Forwarded Message
Subject:[cont...@ntpsec.org] Uputronics Ublox GPS v3.2b (c) 2016 &
Additional Raspberry Pi revision detection info.
as well push the
portability/compatibility issues off onto the maintainers of the
interpreter.
- John D. Bell
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
specially the Server ones which
would be more in use in datacenters).
- John D. Bell
On 04/18/2017 03:06 PM, Eric S. Raymond wrote:
> Hal Murray :
>>>> If we are using a build time, we can run an external script
>>>> to generate the date in a convenient format.
>&
Eric,
The old-school way to check this is "id | grep 'uid=0(' >/dev/null"
and look at the exit status. Has worked as far back as SunOS 4 and
systems in that era; works AFAIK on all Linux distros.
- John D. Bell
On 01/21/2017 01:50 AM, Eric S. Raymond
Mark,
On that page you cited, it says " On public and internal projects
the Guest role is not enforced. All users will be able to create issues,
leave comments, and pull or download the project code." Since NTPsec is
a public project, *can* one explicitly grant 'Guest' access? Or is th
get the code
simplified
and streamlined in single-thread mode as far as possible, and then design
and code a POSIX-threading-conformant "improvement".
- *John D. Bell*
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
Sorry about that. I think I'll have the installer check for existing
version(s)
in /usr/sbin and /usr/local, somehow preserve it
(tarball in /usr/local/ntp/old_version ?) and put symlinks in
/usr/*bin to point to the stuff in /usr/local.
Let me think about this some more.
file put things into
/usr/local, and using the /etc/alternatives symlink trick to pick out the
'right' version. And of course having an uninstall script which backs it
all out, and undoes the symlink indirection.
Thoughts?
- *John D. Bell*
On Mon, Jul 4, 2016 at 6:57 PM, Gary E.
directory with a "-rpmnew" suffix. Then the admin has to resolve
conflicts manually.
> Where would you document what happened and/or how to switch back?
Good question. Suggestions?
- *John D. Bell*
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
suggest I treat the
presence of a ''conflicting'' version? Save the config files, and
overwrite/remove all the old executables? Move everything aside, and put
our entire "best practices" package in place?? Ask for manual
intervention??? Halt, catch fire, burn it all
Sorry for the double email. The list won't let me post from my ''real''
address.
On Jun 13, 2016 6:58 PM, "John D. Bell" wrote:
>
> Gentlemen,
>
> I will not (at least for the foreseeable future) be able to make
> ticktock.uh.utoled
controllably.
Welcome to the Dark Side Systems Administration!
/me hands Eric a cookie. :D
- John D. Bell
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
22 matches
Mail list logo
