[Chaosnet-3] Different HOME

[Creamers158]

Suggestion:

If setting up / changing the the default configuration in the bootstrap like:

# Configuration
KM_USER="km"
KM_HOME="/data/km"

The creation of the user should be accordingly:

useradd -m -d "$KM_HOME" -s /bin/bash "$KM_USER"

[MrLutik]

Thank you for the suggestion! However...

Here's what's happening:

Current Configuration:

KM_USER="km"
KM_HOME="/home/km"

Current User Creation (line 95):

useradd -m -s /bin/bash "$KM_USER"

Why this is correct:

The -m flag in useradd automatically creates the home directory at the default location /home/$KM_USER, which is exactly /home/km - matching our KM_HOME configuration.

Your suggestion would be needed IF:
The KM_HOME variable was set to a non-standard location like /data/km or /opt/km

In that case, yes, we would need: useradd -m -d "$KM_HOME" -s /bin/bash "$KM_USER"

Current behavior:

✅ KM_HOME="/home/km" matches the default home directory created by useradd -m
✅ No explicit -d flag needed since we're using the default location

If you want to change the home directory location:
Then you're absolutely right - you would need to:
Change KM_HOME to your desired path (e.g., /data/km)
Update the useradd command to: useradd -m -d "$KM_HOME" -s /bin/bash "$KM_USER"
But as the script stands now, it's working correctly for the default /home/km location.

Does this clarify the situation, or would you like me to suggest making the script more flexible to support custom home directories?

[Creamers158]

I did indeed need a custom location. Simply changing KM_HOME would have broken it.
This issue was meant as a suggestion to make the script more flexible for situations where organizations already have users, Docker setups, or data in place, and don’t want to be forced into specific configurations.
As the script stands now, though, it’s working correctly.

[MrLutik]

Ok, that's I can add.