On Monday 17 May 2004 15:54, Gray, Tim wrote:
> Ok so my /etc/skel should be empty right now and I need to drop the .kde
> directory in there or jsut the contents of the .kde file and then go
> editing and hunting from there?
You might even want to try just creating a new test user, make the minimum
amount of changes in the Control Center, log out and then copy the
entire /home/username/.kde directory to /etc/skel - then you can start
tweaking with all those lovely ASCII conf files, and begin the exciting trail
of save conf -> new user' -> log in -> not quite right -> delete user (ensure
you delete their homedir afterwards)
> I dont care about app defaults, I just want to eliminate the user needing
> to choose anything when they first log-in. I want kde to default to no
> eye-candy, low-processor settings and a default theme (redmond to help fool
> the whiney users) and then never ever care about my default design again.
Sounds like you're in exactly the same boat as I was... you're welcome to a
copy of my /etc/skel [1] since it might speed the process up a bit.
> will what is in /etc/skel force changes on the user every single time?
Not at all. It will only affect new users. Once they have logged in, they are
still free to customise their installation and choose all manner of foul
themes, window decorations, wallpaper, fonts and then complain that they
can't read anything on-screen. I guess if you have NFS-homedirs like I do, it
would be an option to chown the kde conf files to root.root so at least any
changes will not persist across logins...
Cheers,
Gavin.
[1] http://bum.net/skel.tar.gz
___________________________________________________
.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
