On Mon, Jan 12, 2009 at 12:28:41PM +0800, Carlos Nazareno wrote: > so does that mean that XO OS ships with all the kids having admin > accounts?
In deployments, the XO ships in a locked state with an activation security system for theft reduction. The operating system builds used by a deployment team are up to them, they may customise, but if they base it on the OLPC builds then the Terminal activity grants them full access (a "root" prompt), and the virtual text console does the same. You can verify this by running the OLPC builds yourself. > > If specific applications are not welcome in a deployment, they should be > > checked for. > > how about after deployment? > like setting user permissions to prevent kids from installing > unauthorized apps? I specifically mean in the context of a deployment in progress, which includes support and ongoing monitoring by the deployment team. Deployment involvement for a child would end when they leave school. After deployment, if the child keeps the laptop, they would have full authority over it, and presumably no longer be cared for by the deployment monitoring systems. -- James Cameron mailto:qu...@us.netrek.org http://quozl.netrek.org/ _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
