I think martin_xsa wanted create a group robots too,<br>as part of <a href="http://wiki.laptop.org/go/11.2.0/Robotics_plan">http://wiki.laptop.org/go/11.2.0/Robotics_plan</a><br><br>Gonzalo<br><br><div class="gmail_quote">
On Tue, Jan 3, 2012 at 11:12 AM, Paul Fox <span dir="ltr"><<a href="mailto:pgf@laptop.org">pgf@laptop.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
roughly speaking, we chose the "dialout" group because a) it's a<br>
traditional group for access to UNIX serial devices, b) many USB<br>
devices that activities need access to are actually serial devices,<br>
and c) the "olpc" user is already a member of "dialout". is it<br>
important that Lego devices be protected by a separate group<br>
membership?<br>
<br>
the current udev rule isn't added by Sugar -- it's in the olpc-utils<br>
rpm distributed by OLPC. we can add a modified rule once we agree<br>
on what it should look like.<br>
<br>
i can't remember at the moment where the default passwd and group<br>
files come from -- if the rule needs a new group, we'll need to modify<br>
those files as well.<br>
<br>
paul<br>
<div class="im"><br>
alan jhonn aguiar schwyn wrote:<br>
><br>
> Hi,<br>
> In a few of months, all our High Schools (of Uruguay) will receive and robotic<br>
> kit (Lego).<br>
> At "Universidad de la República", "Facultad de Ingeniería" we are workingwith<br>
> it and the XO...<br>
> <a href="http://www.youtube.com/watch?v=S8HRbDLO7LM" target="_blank">http://www.youtube.com/watch?v=S8HRbDLO7LM</a><br>
><br>
> In other parallel road, we are working on a 2.0 version of the Butia Robot<br>
> <a href="http://www.fing.edu.uy/inco/proyectos/butia" target="_blank">www.fing.edu.uy/inco/proyectos/butia</a><br>
><br>
> That uses USB4all IO board which resulted from a thesis given at ourUniversity<br>
> (also will have arduino compatibility)<br>
> <a href="http://www.fing.edu.uy/inco/grupos/mina/pGrado/pgusb/" target="_blank">http://www.fing.edu.uy/inco/grupos/mina/pGrado/pgusb/</a><br>
><br>
</div> > USB4all is based on 18f4550 pic.The vendor is Microchip,<br>
<div class="im"> > SYSFS{idVendor}=="04d8"And have: productID=0x000b //bootloader<br>
> productID=0x000c //pic18f4550 generic comunication<br>
><br>
> The actual Sugar image, only have permissions for LEGO WeDo.<br>
> If you see in: /etc/udev/rules.d you find the correspondient:<br>
> "30-olpc-wedo.rules".<br>
> The file add this rule:<br>
> SYSFS{idVendor}=="0694", SYSFS{idProduct}=="0003", GROUP="dialout", MODE="0660"<br>
> This means: 0694 is LEGO 0003 the model: WeDo<br>
> To the NXT we need add: {idProduct}=="0002"<br>
> But, for each model add a new line.. not is a good form..<br>
> Exist another way, a generic rule:<br>
> BUS=="usb", SYSFS{idVendor}=="0694", GROUP="lego", MODE="0660"<br>
> That says: if is USB and fabricated by 0694 (LEGO) lets 0660 (4: read+ 2: write)<br>
> If add this permissions to "lego" group, we need create it..<br>
> But, we don't make it, an use an existing group like "root"? Or another...<br>
> Suggestions?<br>
> We can make a generic group "robot" that have permissions for: lego wedo, lego<br>
> nxt, butia, etc...<br>
> Regards!<br>
</div> > Alan part 2 text/plain 129<br>
> _______________________________________________<br>
> Devel mailing list<br>
> <a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br>
> <a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
<br>
=---------------------<br>
paul fox, <a href="mailto:pgf@laptop.org">pgf@laptop.org</a><br>
<br>_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
<br></blockquote></div><br>