Basically a network/local/user specific configuration database. Playing with it can break apps that expect their config to be in it, or to be of the type expected, even though they shouldn’t.
This about:config on Firefox but system wide. It’s your ~/.config and /etc/ folders in one database format, also manageable with AD and proper permissions.
Is It a frontend for dconf? I have to admit I never tinkered with any dconf stuff before as I live mostly in terminal and web browsers. Does dconf share similarities with windows registry?
So, what’s the advantage of using windows registry? I’m mainly using linux, so the concept of registry sounds really strange in my head.
When the developers don’t abuse it, it’s a central place where all the settings and configuration parameters should be.
There’s no main advantage, it’s just a different concept.
Linux sysadmin for the past 25 years here that also has to work with Windows servers.
Basically a network/local/user specific configuration database. Playing with it can break apps that expect their config to be in it, or to be of the type expected, even though they shouldn’t.
This about:config on Firefox but system wide. It’s your
~/.configand/etc/folders in one database format, also manageable with AD and proper permissions.If you’re using a Linux distribution: are you familiar with
gsettingsor some equivalent?Is It a frontend for dconf? I have to admit I never tinkered with any dconf stuff before as I live mostly in terminal and web browsers. Does dconf share similarities with windows registry?
Yes exactly, they’re similar. I guess there’s a universal desire for tree like data stores.