.config

[illoai at gmail.com]

On 23 November 2011 08:31, ajtiM <lumiwa at gmail.com> wrote:
> On Wednesday 23 November 2011 05:46:33 Polytropon wrote:
>> On Wed, 23 Nov 2011 05:39:21 -0600, ajtiM wrote:
>> > Hi!
>> >
>> > I succesfully installed FreeBSD 9.0 RC-2 and I didn't have problems with
>> > bsdinstall and others. What I didn't have on 8.2 is when I start KDE4
>> > with startx I got directory .config in /. I have one .config in /home
>> > but what it happened? When I deleted as root and I start again KDE4 as
>> > user I got it again. Inside is a file Trolltech.conf (the same is in
>> > /home/.config).
>>
>> That file seems to be part of Qt. How can it be
>> created outside your $HOME when you startx? That's
>> somewhat strange... how _can_ that happen?
>>
>>       % cd
>>       % touch ../bla
>>       touch: ../bla: Permission denied
>>       % touch /bla
>>       touch: /bla: Permission denied
>>
>> Only root permissions allow the creation of files
>> in that specific directories.
>>
>> Neither /.config or /home/.config should exist.
>> It shoud be ~/.config for your user account.
>>
>> I also have ~/.config/Trolltech.conf. I'm not using
>> KDE, but one KDE program, maybe other Qt-based programs.
>> Maybe one of them has installed the directory (at
>> this correct location)?
>>
>>       % ls .config/
>>       Trolltech.conf
>>       audacious/
>>       autostart/
>>       gsmartcontrol/
>>       gtk-2.0/
>>       menus/
>>
>> Okay, seems that other toolkits also use it. :-)
>
> I don't know how this happened but I have it start all the time when I startx.
> Troltech.conf:
>
> [Qt%20Plugin%20Cache%204.7.false]
> usr\local\kde4\lib\kde4\plugins\kauth\backend\kauth_backend_plugin.so=40704,
> 0, i386 usr/local/share/qt4/mkspecs/freebsd g++-4 full-config, 201
> 1-11-20T16:14:25
> usr\local\kde4\lib\kde4\plugins\kauth\helper\kauth_helper_plugin.so=40704, 0,
> i386 usr/local/share/qt4/mkspecs/freebsd g++-4 full-config, 2011-
> 11-20T16:14:25

A dirty workaround might be to link /.config
to something innocuous.  One could obvio-
usly also have /.config mounted as a tmpfs(5).
So it couldn't persist from boot to boot.

The cleanest solution is to forgo qt/kde, but
then you're slightly more limited in what you
can use for office-type stuff.

-- 
--