public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jnair at ensim dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/3353] ttyname's new strict dependency on /proc breaks chrooted applications
Date: Fri, 13 Oct 2006 05:30:00 -0000	[thread overview]
Message-ID: <20061013053032.28524.qmail@sourceware.org> (raw)
In-Reply-To: <20061012113826.3353.jnair@ensim.com>


------- Additional Comments From jnair at ensim dot com  2006-10-13 05:30 -------
(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.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=3353

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2006-10-13  5:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-12 11:38 [Bug libc/3353] New: " jnair at ensim dot com
2006-10-12 20:57 ` [Bug libc/3353] " drepper at redhat dot com
2006-10-12 21:04 ` jakub at redhat dot com
2006-10-13  5:30 ` jnair at ensim dot com [this message]
     [not found] <bug-3353-131@http.sourceware.org/bugzilla/>
2014-06-17  4:51 ` fweimer at redhat dot com
2014-06-17 13:39 ` fweimer at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061013053032.28524.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).