[ntp:questions] Unexpected executable locations from "sudo make install" on RPi Linux
david-taylor at blueyonder.co.uk.invalid
Sat Nov 16 11:20:33 UTC 2013
On 16/11/2013 11:07, Rob wrote:
> David Taylor <david-taylor at 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 indicator of the operating environment.
> It is the version of the kernel only.
> "Windows 5.x" also does not tell you if it is Windows 2000 or Windows XP.
> What you need to compare is the distributor name and version, like
> "Raspbian Wheezy".
Yes, these were the same, the official distribution, as far as I know.
> The kernel has nothing to do with the filesystem naming conventions,
> and in fact the whole "sbin" thing was not part of original Unix, it
> was changed later. In early Unix versions most programs were in the
> bin directory and some that you really were not supposed to use as
> a user were in lib or even etc.
> At some point in time, a reorganization was done to make etc only for
> config items, lib only for libraries, and then sbin was invented for
> the programs that would not belong in bin.
Thanks for that background information.
> However, every Linux system can setup things differently when the maker
> likes to. On top of that, there is an individual that lately tends
> to change many things just because he thinks it is better that way
> (usually disregarding the incompatability problems it causes), and some
> distributors listen to him while others thankfully don't.
Same has happened with Apple's iOS with a top management change. <G>
> For the Raspberry Pi, different Linux distributions are available.
> So you will find some difference in details, even when the kernel
> is the same.
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 might be
consistent, but presumably if the underlying OS differs the results from
"make install" will differ.
More information about the questions