<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
<div>> 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?</div><div><br></div><div>No.. was only a idea...</div><div><br></div><div>Seeing the Wiki appears this:</div><div><br></div><div><a href="http://wiki.laptop.org/go/Robots/udev_rules">http://wiki.laptop.org/go/Robots/udev_rules</a>
</div><div><br></div><div>In the article: <a href="http://wiki.laptop.org/go/11.2.0/Robotics_plan" style="font-size: 10pt; ">http://wiki.laptop.org/go/11.2.0/Robotics_plan</a></div><div><br></div><div>Can be add USB4all in the list? <a href="http://wiki.laptop.org/go/11.2.0/Robotics_plan#Dev_and_test_matrix" style="font-size: 10pt; ">http://wiki.laptop.org/go/11.2.0/Robotics_plan#Dev_and_test_matrix</a></div><div><br></div><div><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></div><div>+1</div> </div></body>
</html>