I am a FC6(test3) user. glibc version comes with the distro is 2.4.90-29. My application runs sshd daemon and logons users to their respective chrooted homes. Now /proc is not purposely made available in the chrooted env. sshd's login process (chrooted) calls ttyname. It fails as it does not find /proc mounted. This used to work with glibc-2.4-4 (on FC5) and before. Now this strict dependency breaks my application. Even simple command like `tty` fails in if /proc is not mounted.
glibc cannot work reliably at all without /proc. This is (unfortunately) the only interface to all kinds of kernel details.
BTW, if you for whatever reason don't want to mount whole /proc into the chroots, you can always at least mount --bind there parts of it sufficient enough to make all programs you want to run in the chroot happy.
(In reply to comment #2) > BTW, if you for whatever reason don't want to mount whole /proc into the chroots, > you can always at least mount --bind there parts of it sufficient enough > to make all programs you want to run in the chroot happy. I agree but, 'ttyname' i belive does a 'readlink' on '/proc/self/fd/n' and 'self' will be known only to the forked 'sshd' child,so binding 'part' of the proc fs in this case is not possible. Hope i got it right.
Fixed. *** This bug has been marked as a duplicate of bug 1451 ***
*** This bug has been marked as a duplicate of bug 14516 ***