mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Albert Cahalan" <acahalan@gmail.com>
To: jonsmirl@gmail.com, alan@lxorguk.ukuu.org.uk, hpa@zytor.com,
	greg@kroah.com, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] Clean up old names in tty code to current names
Date: Mon, 10 Jul 2006 22:18:35 -0400	[thread overview]
Message-ID: <787b0d920607101918q6e1d77e8r22d998a820670dbd@mail.gmail.com> (raw)

Jon Smirl writes:

> If I use udev to rename my devices, the names aren't going
> to match /proc/tty and what ps shows.

It's not as if ps will mislead you. You get "?" if you
redirected stderr or if you lack permission to examine
the /proc/*/fd/* links.

Of course, failing to follow Documentation/devices.txt is
complete foolishness. We have standards you know. The names
are pretty much part of the ABI. Feel free to swap /dev/zero
with /dev/random if you believe otherwise.

> The idea behind udev is that the kernel only deals in device
> numbers and all naming happens in user space.

For many things, the kernel knows:

$ cat /proc/*/maps | egrep '000[ ].*/dev'
3001e000-30020000 rw-s 90000000 03:0d 2989877    /dev/fb0
3002a000-3004a000 rw-s f0000000 03:0d 2990830    /dev/mem
3004a000-3104a000 rw-s 94000000 03:0d 2989877    /dev/fb0

The kernel only needs to remember, by keeping a dentry around.

Not that a devices.txt-compliant devfs wouldn't kick ass...

             reply	other threads:[~2006-07-11  2:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-11  2:18 Albert Cahalan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-10  4:11 Jon Smirl
2006-07-10  4:54 ` Andrew Morton
2006-07-10  7:14 ` H. Peter Anvin
2006-07-10  9:44 ` Alan Cox
2006-07-10 12:41   ` Jon Smirl
2006-07-10 13:10     ` Alan Cox
2006-07-10 13:03       ` Jon Smirl
2006-07-10 13:12         ` CaT
2006-07-10 13:18           ` Jon Smirl
2006-07-10 13:43         ` Alan Cox
2006-07-10 14:07           ` Jon Smirl
2006-07-10 14:17             ` Jan Engelhardt
2006-07-10 14:37             ` Alan Cox
2006-07-10 14:42             ` Antonino A. Daplas
2006-07-10 14:57               ` Jon Smirl
2006-07-10 15:19                 ` Alan Cox
2006-07-10 15:10                   ` Valdis.Kletnieks
2006-07-10 15:21                     ` Russell King
2006-07-10 15:38                       ` Valdis.Kletnieks
2006-07-10 15:35                   ` Antonino A. Daplas
2006-07-10 15:54                     ` Jon Smirl
2006-07-10 16:04                       ` H. Peter Anvin
2006-07-10 22:14                       ` Jan Engelhardt
2006-07-10 18:13               ` Alistair John Strachan
2006-07-11 21:54             ` Greg KH
2006-07-11 21:52     ` Greg KH

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=787b0d920607101918q6e1d77e8r22d998a820670dbd@mail.gmail.com \
    --to=acahalan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=hpa@zytor.com \
    --cc=jonsmirl@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®