[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

could not set new controlling tty



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I'm getting an error out of an install CD I've just built:

...
anaconda installer init version 10.2.0.57 starting
mounting /proc filesystem... done
mounting /dev filesystem... done
mounting /dev/pts (unix98 pty) filesystem... done
mounting /sys filesystem... done
could not set new controlling tty
...

According to the code, this appears to be due to a setsid() failure,
which according to the doco, can only occur with an EPERM.

All I can find on the web is some indication that the kernel hasn't been
compiled with the correct options.  I'm use kernel-2.6.11-1.14.FC3 for
this, and this exact kernel certainly runs up my build server.

I'm using anaconda-10.2.0.57 to buildinstall this.  I do note that
upd-instroot is still attempting to look for kernel-BOOT which hasn't
been around for quite some time ...

This is the first time I've used buildinstall to create initrd.img
instead of copying it directly from FC3, but I'm very rigorous about the
process.  Even with --debug, it runs to completion quite normally.

It's quite possible a necessary package hasn't been installed, excepting
 I'm not sure its gotten far enough along to discover this.

Please help.

Alan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFCebZkCfroLk4EZpkRAvSSAKCle6EyilzkLFaQTRxcTOVxMj8VAwCfVxa/
UOGknQ/6YGmV2QMWP3GGiNY=
=VHy0
-----END PGP SIGNATURE-----


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]