If we change our mind because we find more benefits in using a different
method it shouldn't be hard to implement.

Federico

On Fri, Apr 14, 2017 at 11:28 AM marco.cappellacci <
[email protected]> wrote:

> You have already answered.
>
> Now I think /tmp/sysinfo/model is the simpler and best way to get model
> information.
>
> Thank you so much
>
> Marco
>
>
> Il giorno venerdì 14 aprile 2017 11:22:43 UTC+2, Federico Capoano ha
> scritto:
>>
>> I thought that getting it from /tmp/sysinfo/model was simpler so I chose
>> that one (keep it simple approach).
>>
>> What do you mean for portable? Since the deamon only runs on OpenWRT and
>> LEDE, it is not necessary to think about other linux based systems.
>>
>> What real advantages there would be to get this from /proc/cpuinfo?
>>
>> Federico
>>
>>
>> On Friday, April 14, 2017 at 9:11:03 AM UTC+2, marco.cappellacci wrote:
>>>
>>> Hi Federico,
>>> I see you get model information from /tmp/sysinfo/model
>>> I think is more clear and portable to get this information from
>>> /proc/cpuinfo
>>>
>>> What do you think about it?
>>>
>>> Il giorno giovedì 13 aprile 2017 19:27:49 UTC+2, Federico Capoano ha
>>> scritto:
>>>>
>>>> Started working on it, see pull request 53
>>>> <https://github.com/openwisp/django-netjsonconfig/pull/53> to track
>>>> progress.
>>>>
>>>>
>>>> On Wednesday, April 12, 2017 at 5:43:15 PM UTC+2, Federico Capoano
>>>> wrote:
>>>>>
>>>>> See https://github.com/openwisp/django-netjsonconfig/issues/52
>>>>>
>>>>> Federico
>>>>>
>>>> --
> You received this message because you are subscribed to the Google Groups
> "OpenWISP" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to