Adding a new user on Linux.

cancel
Showing results for 
Search instead for 
Did you mean: 

Adding a new user on Linux.

Jump to solution
411 Views
ricardo_ioct
Contributor III

Ladies and Gentlemens,

I'm facing a little problem while using the adduser command on linux. When I tried to add a new user, the console bricks at the password point, not accepting any character neither CTRL+C. The only command supported is finger+reset button. ^^

This is my configuration:

- i.MX53 Novpeck board(pretty much the same as QSB);

- LINUX BSP 11.09;

- Standard USB-to-serial converter;

And this is the adduser output:

root@freescale ~$ adduser horus

adduser: horus: login already in use

root@freescale ~$ passwd horus

Changing password for horus

Enter the new password (minimum of 5, maximum of 8 characters)

Please use a combination of upper and lower case letters and numbers.

Enter new password:


(Deadlock)

Funny fact: When I reboot the board, the new user actually has been created. I tried to login with it, but, again, whenever I need to type a password, the console stops to work.

I hope somebody could help me, or just say that I'm not the only one that are not capable to create a new user on Linux(so shame...).

Regards,

Labels (2)
Tags (2)
0 Kudos
1 Solution
60 Views
AlanZhang
Contributor V

Hi,

Following is my test snapshot based on i.MX53 QSD running ltib 110901, pls check! I did not encounter your deadlock. No problem.

---------------------------------------------------------------------------------

arm-none-linux-gnueabi-gcc (4.4.4_09.06.2010) 4.4.4
root filesystem built on Thu, 20 Sep 2012 14:08:28 +0800
Freescale Semiconductor, Inc.

freescale login: root
login[2192]: root login on 'ttymxc0'
root@freescale ~$ adduser horus
Changing password for horus
New password:
Bad password: too weak
Retype password:
Password for horus changed by root
root@freescale ~$ su horus
horus@freescale ~$

Re-login log message:

Booted NFS, not relocating: /tmp /var
mount: mounting usbfs on /proc/bus/usb failed: No such file or directory
starting pid 2187, tty '': '/sbin/getty -L ttymxc0 115200 vt100'

arm-none-linux-gnueabi-gcc (4.4.4_09.06.2010) 4.4.4
root filesystem built on Thu, 20 Sep 2012 14:08:28 +0800
Freescale Semiconductor, Inc.

freescale login: horus
Password:
horus@freescale ~$

------------------------------------------------

Regards,

Alan Zhang

View solution in original post

0 Kudos
2 Replies
61 Views
AlanZhang
Contributor V

Hi,

Following is my test snapshot based on i.MX53 QSD running ltib 110901, pls check! I did not encounter your deadlock. No problem.

---------------------------------------------------------------------------------

arm-none-linux-gnueabi-gcc (4.4.4_09.06.2010) 4.4.4
root filesystem built on Thu, 20 Sep 2012 14:08:28 +0800
Freescale Semiconductor, Inc.

freescale login: root
login[2192]: root login on 'ttymxc0'
root@freescale ~$ adduser horus
Changing password for horus
New password:
Bad password: too weak
Retype password:
Password for horus changed by root
root@freescale ~$ su horus
horus@freescale ~$

Re-login log message:

Booted NFS, not relocating: /tmp /var
mount: mounting usbfs on /proc/bus/usb failed: No such file or directory
starting pid 2187, tty '': '/sbin/getty -L ttymxc0 115200 vt100'

arm-none-linux-gnueabi-gcc (4.4.4_09.06.2010) 4.4.4
root filesystem built on Thu, 20 Sep 2012 14:08:28 +0800
Freescale Semiconductor, Inc.

freescale login: horus
Password:
horus@freescale ~$

------------------------------------------------

Regards,

Alan Zhang

View solution in original post

0 Kudos
60 Views
ricardo_ioct
Contributor III

Hello Alan Zhang,

Sorry by take a long time to reply, but I figure out what was happening. As I can notice, you was using ttymxc0 to do the login, and I know that is the default. But, on my application, I had to change the login to ttymxc1. Even after I change it on uBoot env, and on LTIB's inittab line argument too, when I try to do passwd or adduser, the application expects the password input on ttymxc0, thus causing the deadlock. I could confirm it putting back the login on ttymxc0. Apparently, I'll need to recompile u-Boot, using ttymxc1 as primary login serial.

Thank you for the reply.

Regards,

Ricardo.

0 Kudos