Linked by Thom Holwerda on Fri 21st Mar 2008 21:49 UTC
Editorial "I used KDE as my primary desktop from 1996 through 2006, when I installed the GNOME version of Ubuntu and found that I liked it better than the KDE desktop I'd faced every morning for so many years. Last January, I got a new Dell Latitude D630 laptop and decided to install Kubuntu on it, but within a few weeks, I went back to GNOME. Does this mean GNOME is now a better desktop than KDE, or just that I have become so accustomed to GNOME that it's hard for me to give it up?"
Thread beginning with comment 306230
To view parent comment, click here.
To read all comments associated with this story, please click here.
sbergman27
Member since:
2005-07-24

Too much effort. I'm a geek, but not that much of a geek.
...
I generally just copy the config files if I have to reinstall. Haven't bothered to find out if there's another way because that's about as easy as it gets.


I administer about a hundred Linux desktops on XDMCP/NX servers. And believe me, copying around config files to change settings is *not* as easy as it gets. Not granular enough. I need more control and fine-grained configurability than that.

I use gconftool-2 scripts. But for larger chunks of config, I believe you can --dump particular branches of gconf to xml and then load them to various accounts. For example:

gconftool-2 --dump /apps/evolution > evolution.xml
gconftool-2 --load=evolution.xml

Or say you just wanted calendar settings:

gconftool-2 --dump /apps/evolution/calendar > calendar.xml

Copying around config files sounds like something out of the DOS dark ages.

Reply Parent Score: 3

elsewhere Member since:
2005-07-13

I administer about a hundred Linux desktops on XDMCP/NX servers. And believe me, copying around config files to change settings is *not* as easy as it gets. Not granular enough. I need more control and fine-grained configurability than that.

I use gconftool-2 scripts. But for larger chunks of config, I believe you can --dump particular branches of gconf to xml and then load them to various accounts. For example:

gconftool-2 --dump /apps/evolution > evolution.xml
gconftool-2 --load=evolution.xml

Or say you just wanted calendar settings:

gconftool-2 --dump /apps/evolution/calendar > calendar.xml

Copying around config files sounds like something out of the DOS dark ages.


You're arguing that gconftool is somehow slicker than cp .kde/share/config/whatever destination. Different strokes for different folks.

In fact, to be pedantic, if you're administering multiple clients, then KDE's Kiosk infrastructure is optimized for that, and has been for some time. That's why the config file structure is set up the way it is. It has a hierarchy that gives you the adminstrator granular control over the user setup, and application configurations, and the extent that they can change it.

I guess it's the difference between copying chunks of gfconf settings and pasting them into multiple accounts, or simply setting up one or more profiles and applying it to multiple accounts. Again, different strokes. ;)

Reply Parent Score: 3

sbergman27 Member since:
2005-07-24

You're arguing that gconftool is somehow slicker than cp .kde/share/config/whatever destination.

Absolutely. Try setting Suzzie's default home page, and make her pdf viewer default to full screen using cp.

Different strokes for different folks.

No. Necessary granularity and flexibility for the admin.

In fact, to be pedantic, if you're administering multiple clients, then KDE's Kiosk infrastructure is optimized for that,

Perhaps. But the DE needs to work for both the admin and the users. KDE might be great for me. But although I keep an eye on it, try out each new release, and respect some of the technology, it is nowhere near suitable for my users. And I would not subject them to it.

Edited 2008-03-23 18:46 UTC

Reply Parent Score: 2

leos Member since:
2005-09-21

I administer about a hundred Linux desktops on XDMCP/NX servers. And believe me, copying around config files to change settings is *not* as easy as it gets. Not granular enough. I need more control and fine-grained configurability than that.


Fine, I'm not the right person to ask about KDE tools to support your need (I'm sure it can be done, but I'm not a systems administrator). We're talking home users here, not systems administrators.

Copying around config files sounds like something out of the DOS dark ages.


For a single user, it's way easier. You don't really expect a home user to bother to learn the syntax of some random config exporting tool do you? Most users will just setup their environment manually after a reinstall, and the next easiest thing is to copy config files (I just copy the whole .kde directory). A dedicated tool is more powerful, but no one but system admins would ever use it, so it's not really relevant to the discussion.

Reply Parent Score: 3

sbergman27 Member since:
2005-07-24

We're talking home users here, not systems administrators.
...
You don't really expect a home user to bother to learn the syntax of some random config exporting tool do you? Most users will just

The topic was geek users who think they need to be able to tweak every conceivable setting. And you just changed it to Aunt Tillie.

Aunt Tillie is just fine without gconftool, gconf-editor, *or* the several kitchen sinks in KDE.

And a geek who can't handle gconf-editor is a pretty feeble geek, IMO.

Edited 2008-03-23 04:52 UTC

Reply Parent Score: 4