-3

When reading the discussion between Linux and Tytso about the misbehavior of the new Linux ext4 filesystem I had a ~/.kde speedy and feature idea:

If we have a(some) file(s)
~/.kde/mount_in_ramfs/config_YYYMMDD_HHMM.tar
Kde could take the newest tar and mount the config files via ramfs.
When the user terminates kde,
Kde should tar the modified config files again as above.

Benefit: We continue to have the beloved file interface with configs at the speed and integrity of a databased registry.

eulenreich wrote:When reading the discussion between Linux and Tytso about the misbehavior of the new Linux ext4 filesystem I had a ~/.kde speedy and feature idea:

If we have a(some) file(s)
~/.kde/mount_in_ramfs/config_YYYMMDD_HHMM.tar
Kde could take the newest tar and mount the config files via ramfs.
When the user terminates kde,
Kde should tar the modified config files again as above.

Benefit: We continue to have the beloved file interface with configs at the speed and integrity of a databased registry.

How big is the penalty for reading the config stuff of the disk file by file? And you create another problem: when your computer goes down your config is flushed down the toilet with everything else in the RAM. And it's expensive too: I have to allocate at least 60 mb RAM. It's probably better to use preload stuff instead. This link may be of intrest.

Either way this is a distro thingy, not a kde one.