dCore Import Debian Packages to Mountable SCE extensions > dCore X86

group ids

<< < (5/6) > >>

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.


--- Quote ---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.

--- End quote ---

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...

Navigation

[0] Message Index

[#] Next page

[*] Previous page