Is it possible/advisable to have user NOT own home folder?
I have previously asked questions about preventing users from deleting certain key files/folders in their home directory by doing something like so:

    /home
    └── [-rw-rw-r-- daedalus    ]  daedalus
        ├── [-rw-rw-r-- root    ]  do_not_delete_file.cpp
        ├── [-rw-rw-r-- root    ]  do_not_delete_file.html
        ├── [-rw-rw-r-- root    ]  do_not_delete_file.php
        ├── [drwxrwxr-x root    ]  do_not_delete_folder
        │   ├── [-rw-rw-r-- root    ]  do_not_delete_file.cpp
        │   ├── [-rw-rw-r-- root    ]  do_not_delete_file.html
        │   └── [-rw-rw-r-- root    ]  do_not_delete_file.php
        └── [-rw-rw-r-- daedalus  ]  index.html

But that fails because user `daedalus` has write, and therefore delete, permissions on their own `/home/daedalus` folder. Thus, although they can't modify, for example, `do_not_delete_file.php`, they can always delete it, and later replace it.

but what if instead I had something like this

    /home
    └── [-rw-rw-r-- root    ]  daedalus
        ├── [-rw-rw-r-- root    ]  do_not_delete_file.cpp
        ├── [-rw-rw-r-- root    ]  do_not_delete_file.html
        ├── [-rw-rw-r-- root    ]  do_not_delete_file.php
        ├── [drwxrwxr-x root    ]  do_not_delete_folder
        │   ├── [-rw-rw-r-- root    ]  do_not_delete_file.cpp
        │   ├── [-rw-rw-r-- root    ]  do_not_delete_file.html
        │   └── [-rw-rw-r-- root    ]  do_not_delete_file.php
        ├── [drwxrwxr-x daedalus    ]  Documents
        └── [-rw-rw-r-- root  ]  index.html

I'm assuming this is possible with a little `chmod` action, but is it going to lead to many many problems when programs naturally assume they have write permissions to the home directory? If this is a bad idea, could I get some other suggestions as to how to tackle this.
Is it possible/advisable to have user NOT own home folder?
===

I have previously asked questions about preventing users from deleting certain key files/folders in their home directory by doing something like so:

    /home
    └── [-rw-rw-r-- daedalus    ]  daedalus
        ├── [-rw-rw-r-- root    ]  do_not_delete_file.cpp
        ├── [-rw-rw-r-- root    ]  do_not_delete_file.html
        ├── [-rw-rw-r-- root    ]  do_not_delete_file.php
        ├── [drwxrwxr-x root    ]  do_not_delete_folder
        │   ├── [-rw-rw-r-- root    ]  do_not_delete_file.cpp
        │   ├── [-rw-rw-r-- root    ]  do_not_delete_file.html
        │   └── [-rw-rw-r-- root    ]  do_not_delete_file.php
        └── [-rw-rw-r-- daedalus  ]  index.html

But that fails because user `daedalus` has write, and therefore delete, permissions on their own `/home/daedalus` folder. Thus, although they can't modify, for example, `do_not_delete_file.php`, they can always delete it, and later replace it.

but what if instead I had something like this

    /home
    └── [-rw-rw-r-- root    ]  daedalus
        ├── [-rw-rw-r-- root    ]  do_not_delete_file.cpp
        ├── [-rw-rw-r-- root    ]  do_not_delete_file.html
        ├── [-rw-rw-r-- root    ]  do_not_delete_file.php
        ├── [drwxrwxr-x root    ]  do_not_delete_folder
        │   ├── [-rw-rw-r-- root    ]  do_not_delete_file.cpp
        │   ├── [-rw-rw-r-- root    ]  do_not_delete_file.html
        │   └── [-rw-rw-r-- root    ]  do_not_delete_file.php
        ├── [drwxrwxr-x daedalus    ]  Documents
        └── [-rw-rw-r-- root  ]  index.html

I'm assuming this is possible with a little `chmod` action, but is it going to lead to many many problems when programs naturally assume they have write permissions to the home directory? If this is a bad idea, could I get some other suggestions as to how to tackle this.