-----Original Message-----
Maybe this could be part of kdeedu. It would certainly be handy for us to have methods of restricting access. It would be good to draft up a list of requirements for KDE in which it could be safely used in a school without kids going wild in the Control Center. Luckily due to Linux's permissions, most of the damage can be prevented. :)
Good idea. I'll have a look what would need to be done, and perhaps try writing an app (I think kdeadmin would be a better place) to do this :)
This would be cool. Like you say in your other mail, a policy editor would be a good idea. It would be handy if this was a kcontrol. Let me
Don't copy the WIndows roaming profile mess.
know when you have started and I will pitch in if I can.
I'd suggest going back more towards the old fashioned unix style global and per user config files. But with the addition that the global config file also contains directives to say if a value can be overridden by a local configuration file, if the end user can alter settings. Something http_proxy [ @admin default proxy1:3128 @staff,user1 default proxy2:3128 @@ mandatory proxy3:3128 ] -- Mark Evans St. Peter's CofE High School Phone: +44 1392 204764 X109 Fax: +44 1392 204763