No worries Michael, all good :)

Cheers,

Michel

> On 9 Jan 2023, at 11:47, Michael J. Oghia <[email protected]> wrote:
> 
> Ah OK, great! Thank you, and sorry for being such a nooby luddite :-)
> 
> Best,
> -Michael
> 
> 
> On Mon, Jan 9, 2023 at 11:42 AM Michel Stam <[email protected] 
> <mailto:[email protected]>> wrote:
>> Hi Michael,
>> 
>> Oh of course, happy new year to you too (keep forgetting).
>> 
>> In that case, you don’t have to do anything to keep your probe up to date, 
>> this should all happen automatically.
>> 
>> Cheers,
>> 
>> Michel
>> 
>>> On 9 Jan 2023, at 11:31, Michael J. Oghia <[email protected] 
>>> <mailto:[email protected]>> wrote:
>>> 
>>> Hi Michel,
>>> 
>>> Happy New Year! Yes, exactly, the small white probes.
>>> 
>>> Best,
>>> -Michael
>>> 
>>> On Mon, Jan 9, 2023 at 11:27 AM Michel Stam <[email protected] 
>>> <mailto:[email protected]>> wrote:
>>>> Hi Michael,
>>>> 
>>>> Are you running hardware probes (the small white boxes)? 1100 only applies 
>>>> to those.
>>>> 
>>>> Let me know.
>>>> 
>>>> Regards,
>>>> 
>>>> Michel
>>>> 
>>>>> On 9 Jan 2023, at 11:12, Michael J. Oghia <[email protected] 
>>>>> <mailto:[email protected]>> wrote:
>>>>> 
>>>>> Hi Michel, all:
>>>>> 
>>>>> I'm a big fan of the Atlas programme, and have hosted probes for years 
>>>>> now (and I'm an active member of this community). However, I don't have a 
>>>>> technical or engineering background and while one of my probes is close 
>>>>> to me, another is not. Both of the probes I host have firmware version 
>>>>> 5080 (1100). 
>>>>> 
>>>>> Is there anything I need to do right now to update the software? And if 
>>>>> not (e.g., it's the latest for now), can the NCC provide detailed 
>>>>> instructions for how to do so (i.e., in the style of "WikiHow") so we can?
>>>>> 
>>>>> Best,
>>>>> -Michael
>>>>> 
>>>>> 
>>>>> On Mon, Jan 9, 2023 at 10:19 AM Michel Stam <[email protected] 
>>>>> <mailto:[email protected]>> wrote:
>>>>>> Hi guys,
>>>>>> 
>>>>>> The automatic update for the CentOS package was removed as of 5080. This 
>>>>>> means that the update to 5080 will still be automatic, but not any more 
>>>>>> after this (say 5090 onwards).
>>>>>> This was a request by several users because Atlas forced the update, 
>>>>>> which violated their sysadmin policies.
>>>>>> 
>>>>>> As to updating the package, we are looking to see if it is possible to 
>>>>>> make an RPM that is part of the base RedHat repository, together with a 
>>>>>> packager. We could do something similar for Debian (possibly others, 
>>>>>> such as OpenWRT).
>>>>>> 
>>>>>> I’m not sure what you mean with methods:
>>>>>> How many probe users are using auto-update is a bit difficult to answer, 
>>>>>> since right now it is forced, but as of the next software release it 
>>>>>> will not be. 
>>>>>> Which operating systems are used is also a bit difficult since we do not 
>>>>>> provide an official Debian package yet, and the software does not 
>>>>>> differentiate between different flavours of Linux.
>>>>>> 
>>>>>> Hope this helps.
>>>>>> 
>>>>>> Regards,
>>>>>> 
>>>>>> Michel
>>>>>> 
>>>>>> > On 8 Jan 2023, at 01:36, Seth David Schoen <[email protected] 
>>>>>> > <mailto:[email protected]>> wrote:
>>>>>> > 
>>>>>> > Alexander Bochmann writes:
>>>>>> > 
>>>>>> >> When using the CentOS binary repo as recommended, the software should 
>>>>>> >> auto-update during normal system update procedures.
>>>>>> >> 
>>>>>> >> For source releases (Debian), you're more or less on your own. 
>>>>>> >> Updating 
>>>>>> >> is still easy - just go through the initial installation again, minus 
>>>>>> >> registration.
>>>>>> > 
>>>>>> > I see, so that's a pretty significant difference in the experiences of
>>>>>> > people using different systems.
>>>>>> > 
>>>>>> > Is it clear how many probe users use each of these methods? (which
>>>>>> > might indicate whether it could be worth maintaining a more automated
>>>>>> > installation method for Debian-based systems)
>>>>>> > 
>>>>>> > -- 
>>>>>> > ripe-atlas mailing list
>>>>>> > [email protected] <mailto:[email protected]>
>>>>>> > https://lists.ripe.net/mailman/listinfo/ripe-atlas
>>>>>> 
>>>>>> 
>>>>>> -- 
>>>>>> ripe-atlas mailing list
>>>>>> [email protected] <mailto:[email protected]>
>>>>>> https://lists.ripe.net/mailman/listinfo/ripe-atlas
>>>> 
>> 

-- 
ripe-atlas mailing list
[email protected]
https://lists.ripe.net/mailman/listinfo/ripe-atlas

Reply via email to