From: dan@djph.net   
      
   On 2025-10-21, s|b wrote:   
   > On Tue, 21 Oct 2025 12:59:42 -0000 (UTC), Dan Purgert wrote:   
   >   
   >> You can't just change the home directory name; it tends to cause   
   >> breakage, especially with graphical logins.   
   >   
   > Yes, we've learned that the hard way now. (-: Why doesn't the OS prevent   
   > a user from doing so or at least give a warning? It's not built for   
   > clueless users, I bet.    
      
   For the same reason that 'rm' doesn't ask if you're really sure you want   
   to remove a file.   
      
   *IDEALLY* it's a very simple case of "rename it back" (using the live   
   session), but as the machine is sort of experimental, it might just be   
   faster/easier to pave over it.   
      
   >> [...]   
   >> Also, setup timeshift (not that it helps with torching $HOME, but...)   
   >   
   > I got that option during installation and for some reason chose not to.   
   > *ouch*   
      
   Note that it wouldn't have fixed *THIS* error -- but it's a good idea   
   for if "boss" goes poking around anywhere else on the filesystem.   
      
      
   --   
   |_|O|_|   
   |_|_|O| Github: https://github.com/dpurgert   
   |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1  E067 6D65 70E5 4CE7 2860   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)