illoai at gmail.com illoai at gmail.com
Mon Dec 19 15:48:35 UTC 2011

On 30 November 2011 14:03, Polytropon <freebsd at edvax.de> wrote:
> On Wed, 30 Nov 2011 13:40:19 -0500, illoai at gmail.com wrote:
>> 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.
> The question remains:
> How is a user-started process (e. g. when you run
> the "startx" command) supposed to create directory
> entries and files on root level /, a thing that
> only root and root-like users (and programs!)
> should be allowed to?
>        % mkdir /.config
>        mkdir: /.config: Permission denied
> As a normal user, you _intendedly_ can't do this.
> Why would you assume that a program you start
> can do it?

I don't have any QT/KDE stuff but isn't kdm suid
(& owned by root)?
There're likely a couple of others in that whole
mess, as well.

> Creating such data structures in a _user_ directory
> is completely okay. But in / it simply sounds WRONG.

This I agree with wholeheartedly.

When I first moved to UFS2, the presence of the
heretofore unknown .snap directories gave me
a bit of a paranoid moment.


More information about the freebsd-questions mailing list