<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">The problem with having OS version is
that the automatic scripts running get a version number which is
quite complex.<br>
<br>
Firmware in AirOS: XM.ar7240.v5.3.3.sdk.9634.111221.2238<br>
uname -a output in AirOS: Linux version 2.6.15-5.2
(saverio@nockid) (gcc version 4.1.2) <br>
<br>
While in the case of OpenWRT the name extracted with this method:<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="https://github.com/nemesisdesign/nodeshot/blob/refactoring/nodeshot/networking/connector/classes/OpenWRT.py#L24">https://github.com/nemesisdesign/nodeshot/blob/refactoring/nodeshot/networking/connector/classes/OpenWRT.py#L24</a><br>
<br>
OpenWrt Attitude Adjustment (Scooreggione v4 12.09, r36608)<br>
<br>
uname -a output is: Linux version 3.3.8 (saverio@nockid) (gcc
version 4.6.3 20120201 (prerelease) (Linaro GCC 4.6-2012.02) ) <br>
<br>
Is it really useful to have separate fields for OS and OS version?<br>
<br>
<br>
A similar issue is related to RoutingProtocols.<br>
<br>
By just running the script on 2 devices I already have these 2
OLSR entries in the routing protocols DB table:<br>
<br>
name: OLSR; version:
pre-0.6.3-git_-hash_b493c377b33f6e45d0b2e8b4c8e7c5db<br>
name: OLSR; version:
0.6.5.3-git_3491d09-hash_459f792b8d1a10846916b0bf3e21f727<br>
<br>
Federico<br>
<br>
<br>
On 11/06/2013 05:50 PM, Clauz wrote:<br>
</div>
<blockquote cite="mid:527A7361.4020102@ninux.org" type="cite">
<pre wrap="">Hi.
If we want to keep it simple would suggest using "OS" (which is more
general than "Firmware") and "OS Version". In this way also statistics
on OS/Firmware usage could be easily computed.
Clauz
On 11/06/2013 04:28 PM, nemesis wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I don't have time at the moment to refactor the field to become a table.
Maybe in the future if we start offering firmware images to download or
stuff like that it would be a nice feature.
The question was if we should have OS and Firmware fields or if we
should have just OS and in case the device is an embedded device we
could fill OS with the name of the firmware, eg: OpenWRT Attitude
Adjustment, AirOS, ecc
Federico
On Wed, 6 Nov 2013 16:22:14 +0100, Fabio Capriati
<a class="moz-txt-link-rfc2396E" href="mailto:fabio.capriati@gmail.com"><fabio.capriati@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">It's possible to retrive these information from devices remotly and
building automatically this table by script.
2013/11/6 nemesis
Your proposal could be useful if we used that information to
generate the image to be installed on devices, but at the moment this
is not on my todo list, and I would adopt the kiss principle and keep
it as more simple as possible.
Federico
On Wed, 6 Nov 2013 14:35:10 +0100, Fabio Capriati wrote:
In my opinion, it could be righta a table "Firmware" with this
fields:
Integer "ID"
String "Operative System" (OperWRT | MicrotiKOS | AirOS)
String "Name" (Stock | Sburratone | Scorreggione)
Integer "Version"
Bool "Support IPV6"
Bool "Support SNMP"
Bool ....
So into device you can put only the ID reference.
2013/11/6 Stefano De Carlo
Il 06/11/2013 14:00, nemesis ha scritto:
> In the Device table at the moment we have "os" which stands for
> "operating system" and "firmware", both are optional fields.
>
> Does it have sense to have both? Or in case of embedded device
the
OS
> field should be filled with the firmware name?
>
> Have your say
In my experience I think It's best not to have semantic clashes
like
this one and just go for an agnostic term. "Operating System" will
work
just fine for the whole device spectrum.
Stefanauss.
_______________________________________________
Nodeshot mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Nodeshot@ml.ninux.org">Nodeshot@ml.ninux.org</a> [3] [2]
<a class="moz-txt-link-freetext" href="http://ml.ninux.org/mailman/listinfo/nodeshot">http://ml.ninux.org/mailman/listinfo/nodeshot</a> [4] [3]
Links:
------
[1] <a class="moz-txt-link-freetext" href="mailto:stefanauss@gmail.com">mailto:stefanauss@gmail.com</a> [5]
[2] <a class="moz-txt-link-freetext" href="mailto:Nodeshot@ml.ninux.org">mailto:Nodeshot@ml.ninux.org</a> [6]
[3] <a class="moz-txt-link-freetext" href="http://ml.ninux.org/mailman/listinfo/nodeshot">http://ml.ninux.org/mailman/listinfo/nodeshot</a> [7]
_______________________________________________
Nodeshot mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Nodeshot@ml.ninux.org">Nodeshot@ml.ninux.org</a> [8]
<a class="moz-txt-link-freetext" href="http://ml.ninux.org/mailman/listinfo/nodeshot">http://ml.ninux.org/mailman/listinfo/nodeshot</a> [9]
Links:
------
[1] <a class="moz-txt-link-freetext" href="mailto:nemesis@ninux.org">mailto:nemesis@ninux.org</a>
[2] <a class="moz-txt-link-freetext" href="mailto:fabio.capriati@gmail.com">mailto:fabio.capriati@gmail.com</a>
[3] <a class="moz-txt-link-freetext" href="mailto:Nodeshot@ml.ninux.org">mailto:Nodeshot@ml.ninux.org</a>
[4] <a class="moz-txt-link-freetext" href="http://ml.ninux.org/mailman/listinfo/nodeshot">http://ml.ninux.org/mailman/listinfo/nodeshot</a>
[5] <a class="moz-txt-link-freetext" href="mailto:stefanauss@gmail.com">mailto:stefanauss@gmail.com</a>
[6] <a class="moz-txt-link-freetext" href="mailto:Nodeshot@ml.ninux.org">mailto:Nodeshot@ml.ninux.org</a>
[7] <a class="moz-txt-link-freetext" href="http://ml.ninux.org/mailman/listinfo/nodeshot">http://ml.ninux.org/mailman/listinfo/nodeshot</a>
[8] <a class="moz-txt-link-freetext" href="mailto:Nodeshot@ml.ninux.org">mailto:Nodeshot@ml.ninux.org</a>
[9] <a class="moz-txt-link-freetext" href="http://ml.ninux.org/mailman/listinfo/nodeshot">http://ml.ninux.org/mailman/listinfo/nodeshot</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
Nodeshot mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Nodeshot@ml.ninux.org">Nodeshot@ml.ninux.org</a>
<a class="moz-txt-link-freetext" href="http://ml.ninux.org/mailman/listinfo/nodeshot">http://ml.ninux.org/mailman/listinfo/nodeshot</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Nodeshot mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Nodeshot@ml.ninux.org">Nodeshot@ml.ninux.org</a>
<a class="moz-txt-link-freetext" href="http://ml.ninux.org/mailman/listinfo/nodeshot">http://ml.ninux.org/mailman/listinfo/nodeshot</a>
</pre>
</blockquote>
<br>
</body>
</html>