One of the annoyances of Linux is working out where configuration information is, following through multiple layers of indirection and files over-riding other files. This looks like adding another layer, another place to look, and if you're reading the man file for a shell (for example) it probably won't even mention that this could invalidate the information contained in that in the man file.
You're not wrong. In a worst case scenario I resort to using strace to figure out where a program is reading config from.. from what I understand, if this kernel module is in use then even that approach wouldn't help.
But since the use case is personal dotfiles, I imagine the user isn't going to forget that they set this up.
The use case is that you can actually use your home directory without either (a) hiding files or (b) wading through 40 config files and dirs that XDG ignorant devs put there.
I didn’t understand what this was from the title. Perhaps a better description would be “mod_rewrite for your homedir”
One of the annoyances of Linux is working out where configuration information is, following through multiple layers of indirection and files over-riding other files. This looks like adding another layer, another place to look, and if you're reading the man file for a shell (for example) it probably won't even mention that this could invalidate the information contained in that in the man file.
You're not wrong. In a worst case scenario I resort to using strace to figure out where a program is reading config from.. from what I understand, if this kernel module is in use then even that approach wouldn't help.
But since the use case is personal dotfiles, I imagine the user isn't going to forget that they set this up.
> working out where configuration information is
Generally, good behaved applications have an entry in their man page that spells out these details for you, so you don't have to work out anything.
Unfortunately so many packages these days don’t even have a man page at all let alone one with good config info.
Well ... hopefully they're open source and all that.
Tomorrow: modify man pages from kernel space!
Always check the man pages..
I struggle to see a valid usecase for this that isn’t handled by symlinks.
If I symlink ~/.ssh -> ~/.config/ssh, I still have .ssh in my ~. Whereas if I rewrite it, I don't.
Will you not have `~/.ssh`? If you have `.ssh .config/ssh` as a rewrite rule, `stat ~/.ssh` will still find it.
The point is to have a clean home directory.
You could write a kernel module, then, that just hides certain symlinks from you (which is effectively what this module is).
Abandon hope.
I just treat ~ as a system-owned configuration area, and put my actual files (documents, photos, etc.) in a completely different hierarchy under /.
The use case is that you can actually use your home directory without either (a) hiding files or (b) wading through 40 config files and dirs that XDG ignorant devs put there.
I absolutely love this and have wanted to take the time to build this for years precisely because of dotfiles. Thank you!