gconf as the "linux-registry"?

["Ville Jutvik" <ville jutvik home se>]

As we all know, Linux is using configuration-files. Microsoft replaced window's .ini-files with the registry in Windows 95 and it solved a lot of problems. Programs written for windows can alter the system's behaviour for example (such as installing a new driver). This can't be done in Linux due it's configuration files that virtually only humans can edit. I think that this is a big obstacle that could stop Linux from entering the desktop market on a large scale.

A couple of days ago, a friend of mine told me about the gconf-project. I have looked at it and I think it's a brilliant solution to a common problem. Why don't we try to extend gconf's borders across Gnome's and try to make a common, all-purpose "linux-registry", that could store the majority of Linux's configuration-files? If this could be achived a large step towards the desktop-market would have been taken.

What are the problems with achiving this goal?
What features would need to be added to gconf?
Has this topic been on display before?

Eager for answers.

Best regards,
Ville Jutvik
ville jutvik home sewritten for windows can alter the system's behaviour for example (such as installing a new driver). This can't be done in Linux due it's configuration files that virtually only humans can edit. I think that this is a big obstacle that could stop Linux from entering the desktop market on a large scale.

A couple of days ago, a friend of mine told me about the gconf-project. I have looked at it and I think it's a brilliant solution to a common problem. Why don't we try to extend gconf's borders across Gnome's and try to make a common, all-purpose "linux-registry", that could store the majority of Linux's configuration-files? If this could be achived a large step towards the desktop-market would have been taken.

What are the problems with achiving this goal?
What features would need to