20 pointsby todsacerdoti4 hours ago2 comments
  • tengwar2an hour ago
    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.
    • skobes15 minutes ago
      Tomorrow: modify man pages from kernel space!
    • deafpolygon18 minutes ago
      Always check the man pages..
  • yokoprime2 hours ago
    I struggle to see a valid usecase for this that isn’t handled by symlinks.
    • regularfry2 hours ago
      If I symlink ~/.ssh -> ~/.config/ssh, I still have .ssh in my ~. Whereas if I rewrite it, I don't.
      • hvenevan hour ago
        Will you not have `~/.ssh`? If you have `.ssh .config/ssh` as a rewrite rule, `stat ~/.ssh` will still find it.
        • txtsdan hour ago
          The point is to have a clean home directory.
          • jl638 minutes ago
            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 /.