Re: ntpclient names

Yo Hal! On Thu, 23 Feb 2017 03:41:53 -0800 Hal Murray wrote: > > Our scripts are just for developers and for packagers to get a > > start. > > I think we can do a better job of providing the information that a > packager needs. No argument there. RGDS GARY

Re: ntpclient names

> Our scripts are just for developers and for packagers to get a start. I think we can do a better job of providing the information that a packager needs. -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org

Re: ntpclient names

Yo Royce! On Wed, 22 Feb 2017 12:50:39 -0900 Royce Williams wrote: > > Nothing we do says an admin can't "rm /usr/bin/XXX". I often have > > that in my build scripts. No need to clutter the build options for > > that. > > Bespoke downstream file removal has its place --

Re: ntpclient names

g...@rellim.com said: > I'm unaware of anything in NTPsec that does things behind anyone's back. >> Does it start a server? Does it run a cron job? Does it install >> hooks that some code I do need might call? > Now I'm really lost. I'm unaware of anything in NTPsec does any of that >

Re: ntpclient names

On Wed, Feb 22, 2017 at 11:30 AM, Gary E. Miller wrote: > > Yo Achim! > > On Wed, 22 Feb 2017 18:21:01 +0100 > Achim Gratz wrote: > > > Gary E. Miller writes: > > > Mark was thinking of a separate ntp-tools package or option. Many > > > distros has a X

Re: ntpclient names

Yo Achim! On Wed, 22 Feb 2017 18:21:01 +0100 Achim Gratz wrote: > Gary E. Miller writes: > > Mark was thinking of a separate ntp-tools package or option. Many > > distros has a X package and a matching X-tools package. We could > > make that easy with a build option. > > >

Re: ntpclient names

Mark Atwood : > > 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. Reasonable point. I'll

Re: ntpclient names

Yo Hal! On Tue, 21 Feb 2017 14:58:33 -0800 Hal Murray wrote: > e...@thyrsus.com said: > > I've forgotten. What's the actual problem with including ntpviz in > > the standard install? > > 1) General clutter for the 99% who won't use it. Yes. > 2) It drags in a

Re: ✘ntpclient names

Gary E. Miller : > Yo Mark! > > On Tue, 21 Feb 2017 22:25:28 + > Mark Atwood wrote: > > > Call it "therm" or "thermal" then, instead of "heat" or "temperature"? > > I can live with ntplogtherm I like the way you guys are thinking. --

Re: ntpclient names

e...@thyrsus.com said: > I've forgotten. What's the actual problem with including ntpviz in the > standard install? 1) General clutter for the 99% who won't use it. 2) It drags in a big pile of stuff, starting with gnuplot. -- These are my opinions. I hate spam.

Re: ntpclient names

> 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

Re: ntpclient names

Yo Eric! On Tue, 21 Feb 2017 17:13:54 -0500 "Eric S. Raymond" wrote: > > We need to figure out how to handle ntpviz and friends. I think it > > should NOT be part of the standard install set. At a minimum, > > there should be an easy way to skip it during install. > >

Re: ntpclient names

Hal Murray : > As long as they don't get installed, I don't think the ntp prefix is > important. Nevertheless, I think we should maintain namespace discipline even for the uninstalled stuff. It's not always easy to predict what will *remain* uninstalled. >A hyphen after

Re: ✘ntpclient names

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

Re: ntpclient names

Yo Hal! On Tue, 21 Feb 2017 13:01:35 -0800 Hal Murray wrote: > >>gps-log -> ntpgpslog > >> temp-log -> ntptemplog > >> makeheat -> ntpmakeheat > > > That works for me. I'd make 'em shorter if I could, but don't see > > any obvious way to do that

Re: ntpclient names

>> gps-log -> ntpgpslog >> temp-log -> ntptemplog >> makeheat -> ntpmakeheat > That works for me. I'd make 'em shorter if I could, but don't see any > obvious way to do that that wouldn't reduce them to garble. Those names aren't going to be typed by hand very often so I

Re: ✘ntpclient names

Gary E. Miller : > Yo All! > > Eric wants all ntp programs to start with 'ntp' and not have hypens. > > So, how about: > > gps-log -> ntpgpslog > temp-log -> ntptemplog > makeheat -> ntpmakeheat > > Suggestions? That works for me. I'd make 'em shorter

✘ntpclient names

Yo All! Eric wants all ntp programs to start with 'ntp' and not have hypens. So, how about: gps-log -> ntpgpslog temp-log -> ntptemplog makeheat -> ntpmakeheat Suggestions? RGDS GARY --- Gary E.