group ids

[Jason W]

Ok, I see what you are talking about.  I will look for a solution.

[Jason W]

For now, the passwordless login is the same as Core.  Will see if the gid boot option can be worked in with Busybox commands as it may be useful for some purposes.

[netnomad]

hi jason,

the passwordless login works fine, thank you :-)

how would you recommend to config the shell without a saved /etc/passwd?

i have still problems with bash.
in my bootlocal.sh i config my shell with the command:
sudo usermod -s /bin/bash -g 1000 user
but this has no effect so long i do not logout and login again.

after a new login the configuration in passwd concerning the shell works.

thank you for your help.

[Jason W]

Without using a backup for /etc/passwd like I do on my system, I am not sure.

[netnomad]

... and what do you recommend me to do?

[Jason W]

To make bash your default shell, looks like you have to back up /etc/passwd.  I back mine up and other files for persistent passwords.

[netnomad]

hi jason,

but with the user tc:staff i received the bash in the shell without /etc/passwd in my backup.
i also did not use a password for the login of the user tc.
i do not understand whats the difference.

in my bootlocal.sh i config my shell with the command:
sudo usermod -s /bin/bash -g 1000 user
but this has no effect so long i do not logout and login again.

do you think that we could position the mentioned usermod-command in that way
that the bash is used with the first login?

thank you for your patience and considerations.

[Jason W]

What behavior do you see with this in standard Core in terms of the bash extension being loaded and available for the login shell?  I wish dCore to stay in line with standard Core in base functions as much as possible except for what is needed for dCore to operate with it's different packages source.  If what you see in dCore in terms of bash being made available as the standard shell on login is the same as seen in Core, then that is where dCore needs to be.   When changes are made in Core that apply or can be ported to the other Core ports - piCore, 64 bit, dCore, etc - it is better that way so we keep the same expected functionality.  Rather than each port going on tangents that make it different in boot codes and other base operations and concepts aside from package management.  I hope you understand. 

[netnomad]

hi jason,

i fully agree to your opinion to stay in line with core and all its great flavors!
i just wonder what happened... perhaps in my changed configurations from tc:staff to user:user,
that i am not able to use bash in the same way i experienced before.
so i really don't want that dcore is changed in an uncompatible way to core.

perhaps you see a way with ~/.xinitrc, ~/.xsession or ~/.X.d/* to initiate the shell to use bash?
or perhaps helps a command in ~/.profile?
it would be very kind of you if you still want to consider whether there is a way
that the command in bootlocal.sh could take effect in the first login.

thank you for any idea or help for solving this issue.

[netnomad]

now i give the backup of /etc/passwd a try...

[Jason W]

These new changes caused breakage, please understand that I need to revert to the previous user setup in base.  I will test the passwordless login tonight, and if that needs fixing I will tend to it.  Thanks.

[netnomad]

hi jason,

did you solve the problem?

thank you for your help and commitment.

[netnomad]

hi jason,

in the last cut you reserved the uid 1000 and 1001.
unfortunately in my configuration the gid 1000 was used by pulse-access,
while user was configured as 1000:1000.
perhaps you could also reserve the gid 1000 and 1001?
perhaps you want to extend the range for uid and gid from 1000 to 1100,
then it is more in the framework of debian and these kind of conflicts can be avoided?

the autologin without password works, but for the re-login a password is needed.
in the moment i prefer to use the cut 2016.05.03.01.09.

user@dcore:~$ version -r
You are running:                          dCore-jessie:2016.05.03.01.09
The latest release candidate is:    dCore-jessie:2016.05.12.23.09

user@dcore:~$ cat /etc/passwd | grep 1000
user:x:1000:1000:Linux User,,,:/home/user:/bin/bash

user@dcore:~$ cat /etc/group | grep 1000
user:x:1000:

i hope that you want to transfer these pleasant features in the current cuts.

thank you for your help and commitment.

[Jason W]

The pulsation startup script has been changed to add a system group for pulse access.  But apparently even just reserving those 1000 1001 groups is causing breakage if the bug report in the e20 USB thread turns out correct.  We need to stay with the base system user and group setup that has worked for a long time though I was hoping to make some allowances in the group file. 

[netnomad]

hi jason,

now i backup passwd, shadow and group.
user and root get stored passwords and i boot with autologin.
pulse-access got the gid 1003.
user:user has 1000:1000.
the autologin is passwordless, the re-login is done per password.

so that seems to be the most compatible compromise and it seems to work well.

thank you for your advises and your help.