Dear community let me ask if probe os and services (aka firmware) source code available in public? Where I find it if yes, and why it's not public if not available? -- -- With regards, Eugene S
Hi Evgeniy On Sun, 13 Jan 2019 at 11:03, Evgeniy S. <eject.in.ua@gmail.com> wrote:
Dear community let me ask if probe os and services (aka firmware) source code available in public? Where I find it if yes, and why it's not public if not available?
https://atlas.ripe.net/resources/source-code/ HTH,
-- "If you want to go fast, go alone. If you want to go far, go together."
Hi Iñigo, thank you for helping I overlooked that information on website and Github repository. Btw, I see some discrepancy there (which can be improved): 1) commit to Gihub repository - last was Jun 14, 2018; 2) listed firmware (last 4790 from Jun 27 2017) on https://atlas.ripe.net/resources/source-code/ page; 3) actual firmware version we have installed on probes 4940 (I found no way to fund when it was released and when probe was updated); -- Evgeniy S On Sun, Jan 13, 2019 at 1:54 PM Iñigo Ortiz de Urbina < inigo@infornografia.net> wrote:
Hi Evgeniy
On Sun, 13 Jan 2019 at 11:03, Evgeniy S. <eject.in.ua@gmail.com> wrote:
Dear community let me ask if probe os and services (aka firmware) source code available in public? Where I find it if yes, and why it's not public if not available?
https://atlas.ripe.net/resources/source-code/
HTH,
-- "If you want to go fast, go alone. If you want to go far, go together."
-- -- With regards, Eugene Sudyr
On 2019/01/13 16:41 , Evgeniy S. wrote:
thank you for helping I overlooked that information on website and Github repository.
Btw, I see some discrepancy there (which can be improved): 1) commit to Gihub repository - last was Jun 14, 2018; 2) listed firmware (last 4790 from Jun 27 2017) on https://atlas.ripe.net/resources/source-code/ page; 3) actual firmware version we have installed on probes 4940 (I found no way to fund when it was released and when probe was updated);
Thank you for your interest in the measurement source code. Based on community feedback we switched from releasing tar-balls to publishing our git repository on github. However, this transition requires a bit more work: 1) The structure of the git repository needs to be improved. At the moment there is one branch per release. That should be switched to a release branch with tags. 2) It is not clear what should be done with the old tar files. Note that currently we publish only the measurement source code. We are working toward releasing the remaining code (a collection of shell scripts) as well to allow people to create software probes. The complete project for making software probes possible is more involved, it requires backend and procedural changes as well. Philip
participants (3)
-
Evgeniy S.
-
Iñigo Ortiz de Urbina
-
Philip Homburg