mailman.ripe.net
Sign In Sign Up
Manage this list Sign In Sign Up

Keyboard Shortcuts

Thread View

  • j: Next unread message
  • k: Previous unread message
  • j a: Jump to all threads
  • j l: Jump to MailingList overview

atlas-sw-probes

Thread Start a new thread
Download
Threads by month
  • ----- 2025 -----
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2024 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2023 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2022 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2021 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2020 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2019 -----
  • December
  • November
  • October
atlas-sw-probes@ripe.net

January 2023

  • 2 participants
  • 2 discussions
Compiling instructions for building from source
by Georg 28 Sep '23

28 Sep '23
Hi, I'd like to build the sofware probe from source for Archlinux, and would like to provide the resulting recipe (a so-called PKGBUILD) to the Arch User Repository as well. Reading through the build scripts for debian and centos left a few open questions, is there any direction on how to build the sw probe without these scripts? I'd like to avoid using the hardcoded libevent 2.1.11 or even a bundled busybox, is this possible and foreseen? A pointer to build instructions would be much appreciated. Thank you in advance Georg ps: after subscribing to this mailinglist I received a welcome message with a bunch of outdated links, you might want to consider updating them.
3 5
0 0
Instructions for updating software probe version
by mivens 11 Jan '23

11 Jan '23
Hello, I'm running a software probe on a Raspberry Pi running Raspian bullseye and from looking at /usr/local/atlas/state/FIRMWARE_APPS_VERSION I appear to be running version 5020. I note from https://atlas.ripe.net/docs/howtos/software-probes.html that as a host, I am expected to "Keep the version of your software up-to-date by upgrading to newer versions as they become available" but I have not found any explicit instuctions on how to do this. I would assume that it would be as simple as updating the local Github repo, and rebuilding the deb file from the main branch then doing a dpkg -i for the new Debian package to install the updated version. Unfortunately, it is not clear to me from looking at the repo what version I am expected to upgrade to. The CHANGES.rst file in the Github repo at https://github.com/RIPE-NCC/ripe-atlas-software-probe/blob/master/CHANGES.r… only mentions up to release 5040 but there are tags currently up to 5083 in the software-probe repo at https://github.com/RIPE-NCC/ripe-atlas-software-probe/tags which do not appear to be in any particular order. There are no releases listed at at https://github.com/RIPE-NCC/ripe-atlas-software-probe/releases The main probe release page at https://atlas.ripe.net/docs/releases/firmware.html mentions up to version 5080. Questions: Am I correct that I am should keep the software up to date? Are there instuctions on how to do this that I have missed? If not could the documentation could be updated with this and shared with the mailing list in the meantime? Many thanks
2 2
0 0

HyperKitty Powered by HyperKitty version 1.3.10.