Novell LINUX ENTERPRISE DESKTOP 10 SP2 - DEPLOYMENT GUIDE 08-05-2008 Deployment Manual page 317

[example group]
Label=Language
Label[de]=Sprache
Label[ru]=Язык
Configuration Entry Lock Down
All configuration entries can be protected from being overwritten. You can lock down
entire configuration files, groups, or individual keys. Do this by adding [Si] on a separate
line at the beginning of a file, placing it behind the group name, or adding it behind a
key.
[example group][$i]
Label=Language
[example group 2]
UserName[$i]=$USER
11.2.3 Activating Profiles
Profiles can be created anywhere in the file system. To make the KDE environment
read your profiles, you must make them known to the system in /etc/kde3rc. The
default profile location /var/lib/kde-profiles/ is already configured there.
By default, a custom profile is not associated to users or groups. You can make this
association in the user profile map file at /etc/kde-user-profile. The only
exception from this is the default profile. If you create a profile named "default" under
/var/lib/kde-profiles/ this is automatically associated to all users on this
machine (such a profile does not exist by default).
Find more detailed information about activating profiles and mapping them to users in
the KIOSK framework documentation.
11.2.4 Examples
SUSE Linux Enterprise comes with three predefined profiles (redmond, simplified, and
Thinclient) located in /var/lib/kde-profiles. You may use one of these as a
template for your own profile.
KDE Configuration for Administrators 301