Bug#464728: bootcd: Unable to connect via ssh with error
Hi, I've encountered the same issue. I was able to track the problem down to /dev/pts directory. My quick and dirty workaround is to rm -rf /dev/pts, and ln -s /dev.ro/pts /dev/. After this is done, I can ssh into the box, and run xterm. Hope this helps. Yifang -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#464728: bootcd: Unable to connect via ssh with error "stdin: is not a tty"
Schumacher, Bernd wrote: A bootcd can only be made from a running system. A debootstrap image is not automatically a running system, instead it is only designed for chroot. The following Packages are needed: lvm2 grub mkisofs fdutils file dosfstools realpath syslinux Also some other packages may be helpfull: less psmisc net-tools ssh vim netbase xbase-clients star console-common console-data console-tools Did you also install them ? Maybe some more packages are needed. In general, to file a bug against bootcd, you have to prove that the system you used to build the bootcd is really bootable and running. I tried installing all the packages you suggested and I got no result (I think most of them are really not relevant for any installation, btw). Anyway you are right: running bootcd from a just installed (real) lenny works fine so I think this bug is not relevant and can be closed. I would appreciate a guide to use a chroot instead of installing a real system, tough. Thanks, Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#464728: bootcd: Unable to connect via ssh with error "stdin: is not a tty"
A bootcd can only be made from a running system. A debootstrap image is not automatically a running system, instead it is only designed for chroot. The following Packages are needed: lvm2 grub mkisofs fdutils file dosfstools realpath syslinux Also some other packages may be helpfull: less psmisc net-tools ssh vim netbase xbase-clients star console-common console-data console-tools Did you also install them ? Maybe some more packages are needed. In general, to file a bug against bootcd, you have to prove that the system you used to build the bootcd is really bootable and running. Regards Bernd > -Original Message- > From: Alessandro Polverini [mailto:[EMAIL PROTECTED] > Sent: Freitag, Februar 08, 2008 18:32 > To: Debian Bug Tracking System > Subject: Bug#464728: bootcd: Unable to connect via ssh with > error "stdin: is not a tty" > > Package: bootcd > Severity: important > > I made a deboostrap image from scracth using lenny, udev and > kernel 2.6.24. > > Everything seems to work fine but I can't ssh any more on my > box, I get the error: > stdin: is not a tty > > Any workaround would be very welcome > > -- System Information: > Debian Release: lenny/sid > APT prefers testing > APT policy: (600, 'testing'), (500, 'stable'), (50, > 'unstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 2.6.21-2-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > >
Bug#464728: bootcd: Unable to connect via ssh with error "stdin: is not a tty"
Package: bootcd Severity: important I made a deboostrap image from scracth using lenny, udev and kernel 2.6.24. Everything seems to work fine but I can't ssh any more on my box, I get the error: stdin: is not a tty Any workaround would be very welcome -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (600, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.21-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]