Hi!
On Thu, 17 Jan 2008, David wrote:
Thanks. I see the commit in git (f37dc9af). I'll test it a bit later :-)
Would this also correct the issue with invalidating (config) volumes
which come after deluge volumes or is that unrelated?
I didn't have a chance to test that yet. If you do, let me know the
result. :P
Great, looks like both the volume-related issues are fixed :-) Thanks.
One thing I noticed is that tos-deluge no longer outputs the 'slot
image version' (ie, is this slot up to date with the same slot on
other motes). I sometimes compared that value when checking if
dissemination is working.
I removed that field completely because we don't really need it anymore. If
the dissemination worked then you should see using -p that the correct
image (UID) is in the proper place.
--
Razvan ME
Maybe you can add a -v option to tos-deluge where a lot of extra
technical info is printed out? (crcs, image vers, etc), but by default
you just get the basic info? Python's 'optparse' module would make
this easy to add :-)
David.
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
