| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
Unlike HOME, I haven't found any benefit to making this non-writeable
and having to write modules for every program that might want to use
it.
|
|
|
|
| |
Let's stop fighting this.
|
|
|
|
| |
These interfere with the defaults that NixOS now has and break podman.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
I think when I implemented this I didn't know about tmpfiles.d(5).
Now I do, so let's use that instead.
I don't think the imperativeNix option is necessary any more since the
home directory is created read-only, but if it turns out that
.nix-defexpr and .nix-profile are coming back, I can look into the
best way to solve that then.
|
| |
|
|
|
|
|
|
| |
There's not anything confidential in the top level of my home
directory, and this makes it easy to have unpriveleged services that
read non-sensitive data from it.
|
| |
|
|
|
|
|
|
|
| |
This group, specific to NetworkManager, didn't really belong as part
of the user definition. It's still not ideal that the networking
module is aware of my user -- it might be nicer to have some generic
framework for admin groups. But this is fine for now.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This ended up being way more trouble than it was worth, and the approach
just flat out didn't work for stuff like OpenSSH.
|
|
|