Re: Unable to determine your tty name error.

[Paul Boddie <paul@boddie.org.uk>]

On Thursday 09 May 2013 17:09:39 mind entropy wrote:
>
> dev entries:
>
> total 12
> drwxr-xr-x  3 root root    4096 May  9 20:28 .
> drwxr-xr-x 19 root root    4096 Jun 22  2012 ..
> crw-r--r--  1 root root   5,  1 May  8 23:08 console
> crw-rw-rw-  1 root root   1,  3 May  8 01:06 null
> drwxr-xr-x  2 root root    4096 Jan  1  1970 pts
> crw-r--r--  1 root root   4,  0 May  9 20:27 tty
> crw-r--r--  1 root root   4,  0 May  9 20:28 tty0
> crw-r--r--  1 root root   4,  1 May  9 20:28 tty1
> crw-r--r--  1 root root   4,  2 May  9 20:28 tty2
> crw-r--r--  1 root root   4,  3 May  9 20:28 tty3
> crw-r--r--  1 root root   4,  4 May  9 20:28 tty4
> crw-------  1 root root 204, 64 Jan  1  1970 ttySAC0
> crw-r--r--  1 root root 204, 65 May  8 01:06 ttySAC1
> crw-r--r--  1 root root 204, 66 May  8 01:06 ttySAC2
>
> Now I get the following error:
>
> login: PAM Failure, aborting: Critical error - immediate abort

For what it's worth, I configure devices on an Emdebian system using some 
commands provided in the following script:

http://hgweb.boddie.org.uk/qi-emdebian/file/tip/qi-emdebian-postsetup#l76

I did look at the device table documentation but couldn't really figure it 
out, or maybe I just thought that the mknod commands were more transparent; I 
don't really remember which now.

Paul