| 1 |
On 1/20/20 1:01 PM, Ulrich Mueller wrote: |
| 2 |
> |
| 3 |
> It's just awful to have a one user at second level (like /home/amavis) |
| 4 |
> when all others are at third level (like /home/staff/joe). |
| 5 |
> |
| 6 |
|
| 7 |
Finally an honest argument =) |
| 8 |
|
| 9 |
I agree. But all we're doing is choosing the default here. GLEP81 lets |
| 10 |
the user override the home directory in those rare cases to put it under |
| 11 |
/home/guests. For everyone else, you get |
| 12 |
|
| 13 |
/home/user1 |
| 14 |
/home/user2 |
| 15 |
/home/user3 |
| 16 |
/home/user4 |
| 17 |
|
| 18 |
instead of |
| 19 |
|
| 20 |
/home/user1 |
| 21 |
/home/user2 |
| 22 |
/var/lib/user3/home |
| 23 |
/home/user4 |
| 24 |
|
| 25 |
I think it's weird that my bash_history winds up under /var/lib. |
| 26 |
|
| 27 |
|
| 28 |
> Besides, nothing guarantees that your username under /home won't collide |
| 29 |
> with an existing subdirectory name. |
| 30 |
|
| 31 |
You can make the same argument about /var/lib. And keep in mind that we |
| 32 |
already have "collisions" for $HOME every time someone switches from |
| 33 |
user.eclass to a GLEP81 user. The risk for /home is no greater than |
| 34 |
anywhere else, and we've deemed that risk acceptable, whatever it is. |
Archives