On 15/11/2013 18:22, Rob wrote:
[]
You *what* I find confusing?
[]
I find it confusing that the behaviour on one Raspberry Pi differed from
that on another Raspberry Pi, both running Linux 3.x.
--
Cheers,
David
Web: http://www.satsignal.eu
___
David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
On 15/11/2013 18:22, Rob wrote:
[]
You *what* I find confusing?
[]
I find it confusing that the behaviour on one Raspberry Pi differed from
that on another Raspberry Pi, both running Linux 3.x.
Well, Linux 3.x is not really an
On 16/11/2013 11:07, Rob wrote:
David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
On 15/11/2013 18:22, Rob wrote:
[]
You *what* I find confusing?
[]
I find it confusing that the behaviour on one Raspberry Pi differed from
that on another Raspberry Pi, both running Linux 3.x.
Well,
David Taylor writes:
I'm going to try an upgrade on the 3.2.27+ RPi to 3.6.11 and see what
changes. I was surprised that using the same NTP source, using the same
sudo make install command, put binary files which I had just compiled
using make in different locations. I had hoped that NTP
David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
I'm going to try an upgrade on the 3.2.27+ RPi to 3.6.11 and see what
changes. I was surprised that using the same NTP source, using the same
sudo make install command, put binary files which I had just compiled
using make in
On 16/11/2013 11:36, Harlan Stenn wrote:
David Taylor writes:
I'm going to try an upgrade on the 3.2.27+ RPi to 3.6.11 and see what
changes. I was surprised that using the same NTP source, using the same
sudo make install command, put binary files which I had just compiled
using make in
On Sat, 16 Nov 2013 11:20:33 +, David Taylor wrote:
I had hoped that NTP might be
consistent, but presumably if the underlying OS differs the results from
make install will differ.
make install is usually the last step of a configure / make / make install
sequence.
With the configure
I have compiled and installed NTP on a number of Raspberry Pi Linux
systems, variants of Debian Wheezy, but on one I see that when I run:
$ sudo make install
I get the executables files in two different directories:
ntpdc ntpq ntptrace = /usr/local/sbin
ntpd ntpdate ntp-keygen ntptime
On Fri, Nov 15, 2013 at 9:09 AM, David Taylor
david-tay...@blueyonder.co.uk.invalid wrote:
I get the executables files in two different directories:
ntpdc ntpq ntptrace = /usr/local/sbin
ntpd ntpdate ntp-keygen ntptime ntp-wait = /usr/local/sbin
Those look like the same directory to me
On 2013-11-15, David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
I have compiled and installed NTP on a number of Raspberry Pi Linux
systems, variants of Debian Wheezy, but on one I see that when I run:
$ sudo make install
I get the executables files in two different
Corrected version:
On 15/11/2013 14:09, David Taylor wrote:
I have compiled and installed NTP on a number of Raspberry Pi Linux
systems, variants of Debian Wheezy, but on one I see that when I run:
$ sudo make install
I get the executables files in two different directories:
ntpdc ntpq
David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
I was expecting all the executables to be in /usr/local/bin/. Why might
this be? Linux is not well known to me.
Thanks to Trevor, Rob and Steve for your answers. Whilst it may be
trivial for those familiar with the OS, it's not
12 matches
Mail list logo
