<div dir="ltr">Clarifs below~<br><div><br>On Sun, Mar 6, 2016 at 11:51 AM, Adam Holt <span dir="ltr"><<a href="mailto:holt@laptop.org" target="_blank">holt@laptop.org</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>In Haiti many teachers and kids would prefer the time was set correctly on their XO-1 laptops, no matter if the time is off by a couple minutes. So they could really use a script that creates the following /boot/olpc.fth, writing it out to an attached USB stick:<br></div><div><pre style="margin-left:40px">\ Open Firmware<br>select /rtc decimal 0 0 0 1 1 1804 set-time<br>\ Optionally unlock XO<br>disable-security<br clear="all"></pre>Then the teacher/operator can walk around the room to fix all XO's clocks (refreshing the USB time as often as she/he wants). Of course not every day can be Haitian Independence Day (Jan 1 1804!) so what the script should really do is create a timestamp 1 minute into the future, filling out those 6 numbers above correctly.<br><br>The untrained operator (teacher typically) will then move the USB stick to the XO(s) in need, to set their RTC's (real-time-clocks). Some ambitious teachers will want to do this every month/semester it appears, to sanitize/harmonize all clocks in their classroom/school as much as possible!<br><br></div><div>Any recommended approaches to getting the UX clean, so that such untrained operator have a visual confirmation that the USB stick has been updated with a proper time-stamp, and (perhaps just as important??) the stick mounted+unmounted effortlessly without too much risk, when this USB stick is recreated hundreds of times within 1 day? A non-confusing command line script can work, that says basically 2 things:<br><ul><li>PLEASE INSERT A USB STICK<br></li><li>USB STICK READY: REMOVE IT NOW!</li></ul>The less keyboard activity required from the teacher the better. But I'm tempted by command syntax as follows:<br></div></div></blockquote><div><br><div style="margin-left:40px">usb-timestamper <minute<u><b>s</b></u>-into-the-future></div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div style="margin-left:40px"></div>Such that running "/bin/usb-timestamper 5" would create USB sticks timestamped 5 minutes into the future. The default should be 1 minute into the future, so running "/bin/usb-timestamper" would be equivalent to "/bin/usb-timestamper 1".<br><br>Conclusion: am just looking for general suggestions from everyone as we cook up something simple!</div></div></blockquote><div><br>We do not want to rely on networking or mesh At All. KISS (key it simple/stupid) at the firmware level allows the teacher/operator to move thru the classroom quite rapidly, fixing the time on each XO laptop as often as s/he wants. 2 examples scenarios, showing how this will be used:<br></div><div><ol><li>Teacher/operator may choose to run "usb-timestamper 10" once as s/he enters each classroom, if she wants to timestamp the USB stick 10min into the future, and then apply this rapidly to all 50 XO's in a classroom/lab over the coming 20minutes. Works great ifs/he does not care that the XO's clocks are off by +/- 10min!</li><li>Or if teacher/operator is perfectionist, then usb-timestamper (interactive command-line program) can be left running on hir own XO laptop that s/he carries around the room -- updating the USB stick repeatedly while walking around the classroom -- such that each of that room's 50 XO laptops has an almost-exact clock, accurate within a minute or so.</li></ol></div> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>in this case, as USB sticks are the most reliable and quick approach in this case.<br><br></div><div>Clarif: I will of course train the teacher/operator to set the clock correctly on their own XO-1, which will typically be running OLPC OS 13.2.7 -- so that all these "offline-NTP sticks" are created based on a reasonably accurate baseline timestamp :)<br clear="all"><br>--<br><div><div dir="ltr">Unsung Heroes of OLPC, interviewed live @ <a href="http://unleashkids.org" target="_blank">http://unleashkids.org</a> !</div></div>
</div>
</div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr">Unsung Heroes of OLPC, interviewed live @ <a href="http://unleashkids.org" target="_blank">http://unleashkids.org</a> !</div></div>
</div></div></div>