Re: net boot installation stops with "openpty() failed"

[Alexander Bartolich <alexander.bartolich%gmx.at@localhost>]

Manuel Bouyer wrote:
> On Fri, Feb 19, 2010 at 12:29:09AM +0100, Alexander Bartolich wrote:
> > [...]
> >   tar: ./dev/dtyC00: Cannot mknod: Invalid argument
> >   tar: ./dev/dtyC01: Cannot mknod: Invalid argument
> >   tar: ./dev/dtya: Cannot mknod: Invalid argument
> >   tar: ./dev/dtyb: Cannot mknod: Invalid argument
> >   tar: ./dev/dtyc: Cannot mknod: Invalid argument
> >   tar: ./dev/dtyd: Cannot mknod: Invalid argument
> >   tar: ./dev/tap: Cannot mknod: Invalid argument
> >   tar: Exiting with failure status due to previous errors
>
> that would be your problem I guess. The NFS root is missing some
> devices. Maybe a limitation on device numbers on linux/XFS ?

An ext2 file system on ram disk solves the problem with GNU tar.

# vdir dty* tap
crw------- 1 uucp root  12,  524288 2009-07-30 02:22 dtya
crw------- 1 uucp root  12,  524289 2009-07-30 02:22 dtyb
crw------- 1 uucp root  12,  524290 2009-07-30 02:22 dtyc
crw------- 1 uucp root  36,  524288 2009-07-30 02:22 dtyC00
crw------- 1 uucp root  36,  524289 2009-07-30 02:22 dtyC01
crw------- 1 uucp root  12,  524291 2009-07-30 02:22 dtyd
crw------- 1 root root 169, 1048575 2009-07-30 02:22 tap

Weird device numbers, indeed.

The installation still fails, however. I guess that the kernel based
NFS server also does not like the device numbers. Perhaps the user-mode
server works better.

Anyway, in the mean time I organized a CD drive, booted from it, and
made a full installation over NFS. Looks good.

Ciao

    Alexander.