All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taral <taral@taral.net>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tty->name conversion?
Date: Fri, 13 Jul 2001 14:34:26 -0500	[thread overview]
Message-ID: <20010713143426.B7873@taral.net> (raw)
In-Reply-To: <200107131743.f6DHhGc186373@saturn.cs.uml.edu>
In-Reply-To: <200107131743.f6DHhGc186373@saturn.cs.uml.edu>

[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]

On Fri, Jul 13, 2001 at 01:43:16PM -0400, Albert D. Cahalan wrote:
> Taral writes:
> 
> > I noticed that ps still relies on device numbers to determine tty, since
> > /proc/*/stat only exports the device number. Is there any way to get the
> > device name? I noticed that it is not present in tty_struct anywhere
> > (proc_pid_stat() uses task->tty->device, which is a kdev_t).
> >
> > This would be useful to consider if we ever intend to create real
> > unnumbered character/block devices.
> 
> This isn't quite true, at least for the version shipped with Debian.

<snip>

Thanks for your reply. It still remains, however, that for processes
that you do not own, it has to guess, viz:

  319 taral    vc/1     S    Jul12 -zsh
  320 root     tty2     S    Jul12 /sbin/getty 38400 vc/2

Notice that the getty is listed as tty2, even though it opened
/dev/vc/2.

-- 
Taral <taral@taral.net>
This message is digitally signed. Please PGP encrypt mail to me.
"Any technology, no matter how primitive, is magic to those who don't
understand it." -- Florence Ambrose

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

      reply	other threads:[~2001-07-13 19:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-05  7:36 tty->name conversion? Taral
2001-07-13 17:43 ` Albert D. Cahalan
2001-07-13 19:34   ` Taral [this message]

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=20010713143426.B7873@taral.net \
    --to=taral@taral.net \
    --cc=acahalan@cs.uml.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.