[prev in list] [next in list] [prev in thread] [next in thread] 

List:       suse-linux-uk-schools
Subject:    Re: [suse-linux-uk-schools] Hi all
From:       "Mark Evans" <mpe () st-peters-high ! devon ! sch ! uk>
Date:       2001-12-03 15:39:33
[Download RAW message or body]

> 
> > -----Original Message-----
> > From:	Chris Howells [SMTP:chrish@gmx.co.uk]
> > Sent:	Monday, December 03, 2001 1:25 PM
> > To:	suse-linux-uk-schools@suse.com
> > Subject:	Re: [suse-linux-uk-schools] Hi all
> > 
> > May I ask what kind of work? What I'd really love is for somebody to make
> > it possible to  restrict the things that are possible in KDE -- for example
> > so that a school could use it on the desktop without the kids fiddling with
> > all the settings.
> > 
> > I did notice however something that Waldo put on:
> > 
> > http://developer.kde.org/development-versions/kde-3.0-release-plan.html
> > 
> > about preventing users changing the wallpaper, and stuff.
> 	[Simon Wood]  
> 
> 	Can't this be done by sym-linking the appropriate parts of '.kde' to a non \
> writable master copy. I though I'd limit my users (my wife) in this fashion but see \
> told me not to....

The problem is you can need to think quite hard about exactly what you
link.

IMHO it's a design defficency quite a bit of software (not just KDE)
has, apparently copied from Windows. Which is to make everything
only end user configurable. Which is a pain where not only don't
you want the end user configuring things they wouldn't have the
first clue anyway. (I find web browser settings an especial annoyance.)

> 
> 	You could also limit access to the config application. Ah the power of the UID....

-- 
Mark Evans
St. Peter's CofE High School
Phone: +44 1392 204764 X109
Fax: +44 1392 204763


[prev in list] [next in list] [prev in thread] [next in thread]