I use DVRRDK_02.80.00.10 and nfs_DM816x_EVM.tar.gz. And Every time I bootup, I need to key in "root" for username. Is there any way to skip this?
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
I use DVRRDK_02.80.00.10 and nfs_DM816x_EVM.tar.gz. And Every time I bootup, I need to key in "root" for username. Is there any way to skip this?
Hereunder are my trial
before trial:
/etc/rc5.d/S99startapp: line 6: syntax error: "fi" unexpected
_ _ ___ _ _ _
| | | | | ||| |___ ___| | _ ___
| |_| | |) | ~ | . | _| |/_| -|
|_____|___ /____/ ___|_| |_| _|-__|
DVR_Netra Board (2011.04)
dvr login: root
root@dvr:~#
after trial:
/etc/rc5.d/S99startapp: line 6: syntax error: "fi" unexpected
login: root
root@dvr:~#
It seems unsuccessful for my request. Any further idea?
That S99startapp error doesn't look good. I assume that's not part of getty change. There are a few different versions of getty. Every version having different options. I was making a guess that you are using the tinylogin getty. Looks like "-n" means no banner. Try executing "/sbin/getty -h" to what options are offered. Do a "ls -l /sbin/getty" to see if there is a symbolic link to the real program, tinylogin, busybox, etc.
That S99startapp error doesn't look good. I assume that's not part of getty change.
==> Yes. By my verification, they're independent.
There are a few different versions of getty. Every version having different options.
I was making a guess that you are using the tinylogin getty.
==> Yes. They use tinylogin with version 1.4. See message below
root@dvr:~# getty
Tinylogin v1.4 (2011.04.11-10:00+0000) multi-call binary
Usage: getty getty [OPTIONS]... baud_rate,... line [termtype]
Looks like "-n" means no banner. Try executing "/sbin/getty -h" to what options are offered.
==> see following for reference
root@dvr:~# getty -h
Tinylogin v1.4 (2011.04.11-10:00+0000) multi-call binary
Usage: getty getty [OPTIONS]... baud_rate,... line [termtype]
Do a "ls -l /sbin/getty" to see if there is a symbolic link to the real program, tinylogin, busybox, etc.
==> see following for reference
root@dvr:~# ls -l /sbin/getty
lrwxrwxrwx 1 1014 1016 16 Jun 29 2012 /sbin/getty -> ../bin/tinylogin
I downloaded the source code(tinylogin-1.4.tar.bz2) and check that and found it seems different meanings from yours
Maybe it's different version.
case 'I': /* initstring */
...
case 'L': /* force local */
...
case 'H': /* fake login host */
...
case 'f': /* custom issue file */
...
case 'h': /* enable h/w flow control */
...
case 'i': /* do not show /etc/issue */
...
case 'l': /* non-default login program */
...
case 'm': /* parse modem status message */
...
case 'n': /* no prompt */
...
case 't': /* time out */
...
case 'w': /* wait CRLF */
Any further idea?
Some Google searches on "getty autologin".
http://osdir.com/ml/linux.busybox/2004-05/msg00208.html
http://wiki.gumstix.org/index.php?title=AutoLogin
http://ciffer.net/~svend/blog/entry/Autologin_on_serial_consoles/
Looks like a couple approaches used. One is specifying a non-deffault login program:
S:2345:respawn:/sbin/getty 115200 ttyO2 -n -l /bin/sh
S:2345:respawn:/sbin/getty 115200 ttyO2 -n -l /usr/local/bin/autologin
where autologin is a compiled program or a wrapper shell script. If you ar elucky, you'll have an autologin already on your file system somewhere. The other approach is directly starting a shell on a terminal:
tty02::respawn:-/bin/sh
There might some problems with ctrl-C withi this approach. That's all I got.
Hello, M1234QWer
I was able to skip the login prompt on my DM816x board. Here are the steps:
1.Change the symbolic link to point to the busybox's getty:
<board-shell># ln -s /bin/busybox /sbin/getty
2.In board's /etc/inittab change the getty line to:
S:2345:respawn:/sbin/getty 115200 ttyO2 -n -l /bin/autologin
3. Create executable /bin/autologin script with the following content:
#!/bin/sh
exec /bin/login -f root
When you reboot your board it should take effect. I am using EZSDK. Tell me if it is still not working.
BR
Hello Vladimir,
After following steps, I can do that
a. change the symbolic link to the busybox's getty:
<board-shell># ln -s /bin/busybox /sbin/getty
b. In board's /etc/inittab change the getty line to:
S:2345:respawn:/sbin/getty 115200 ttyO2 -n -l /bin/autologin
c. Create /bin/autologin script with the following content:
#!/bin/sh
exec /bin/login -f root
d. <board-shell># chmod +x /bin/autologin
e. <board-shell># reboot
Really appreciate for your help. Thanks
Hi there,
I tried this trick on DVRRDK, but it didn't work. I definitely made sure I was using getty from busybox, not the original tinylogin.
Anything I missed?
Thanks,
-Perry
Hello,
@ -Perry
How about your autologin script, are you sure it is executed? Did you add there some echo-s?
BR
Vladimir