public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: John Mylchreest <johnm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] devfs is dead, let's move on
Date: Thu, 07 Jul 2005 20:52:20 +0100	[thread overview]
Message-ID: <1120765940.30316.62.camel@localhost> (raw)
In-Reply-To: <20050706224651.GA19853@kroah.com>

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

On Wed, 2005-07-06 at 15:46 -0700, Greg KH wrote:
> If we can move away from some of our devfs-like names, we stand to
> reclaim a lot of memory from everyone's machines.  As an example, if we
> drop all of the tty/pts/vc/vcc symlinks, and just go with the default
> kernel name, we save 2.5Mb of space in tempfs/ramfs.  I've done this on
> my machines and everything seems to work just fine (it looks like
> everything that was trying to use a tty node was just using the symlink
> anyway.)
> 
> So, anyone have any objections to me changing the default udev naming
> scheme in this manner?

No objections here. I've been waiting fort his move for a little while
now. The only real problems will be with those 2.4 (devfs) users who
refuse to move, maybe this is good enough incentive.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-07-07 19:57 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-06 22:46 [gentoo-dev] devfs is dead, let's move on Greg KH
2005-07-06 23:04 ` Greg KH
2005-07-06 23:06 ` Roy Marples
2005-07-06 23:16   ` Greg KH
2005-07-07  0:35   ` Mike Frysinger
2005-07-07  9:34 ` Henrik Brix Andersen
2005-07-07 13:55 ` Martin Schlemmer
2005-07-07 19:44   ` [gentoo-dev] " Duncan
2005-07-07 20:06     ` Martin Schlemmer
2005-07-07 20:19       ` [gentoo-dev] " Duncan
2005-07-07 20:52   ` [gentoo-dev] " Greg KH
2005-07-07 23:22     ` Martin Schlemmer
2005-07-08 17:06       ` Greg KH
2005-07-08 18:16         ` Stephen Bennett
2005-07-08 18:36           ` Martin Schlemmer
2005-07-08 18:43         ` Martin Schlemmer
2005-07-07 14:18 ` Chris Gianelloni
2005-07-08 17:12   ` Greg KH
2005-07-09  1:00     ` Georgi Georgiev
2005-07-09  2:31       ` Greg KH
2005-08-01 22:14     ` Greg KH
2005-08-01 23:23       ` Kumba
2005-08-01 23:32         ` Greg KH
2005-08-01 23:40           ` Kumba
2005-08-01 23:56             ` Greg KH
2005-07-07 17:39 ` Georgi Georgiev
2005-07-08 17:15   ` Greg KH
2005-07-07 19:52 ` John Mylchreest [this message]
2005-07-07 20:49   ` Greg KH
2005-07-09  3:56   ` Kumba
2005-07-09  4:42     ` Greg KH
2005-07-09  5:22       ` Kumba
2005-07-08 17:49 ` Michiel de Bruijne
2005-07-08 22:25   ` Greg KH
2005-07-08 22:46     ` Michiel de Bruijne
2005-07-08 23:35     ` Martin Schlemmer
2005-07-09  0:44       ` Michiel de Bruijne
2005-07-09  0:58         ` Martin Schlemmer
2005-07-09  2:28       ` Greg KH
2005-07-09 18:34       ` Richard Fish
2005-07-09 18:50         ` Philippe Trottier
2005-07-11  7:47         ` Martin Schlemmer
2005-07-12 22:08           ` Mike Frysinger
2005-07-13  9:00             ` Martin Schlemmer
2005-07-13 12:55               ` Mike Frysinger
2005-07-13 14:44             ` Richard Fish
2005-07-15 23:37 ` Carlos Silva
2005-07-17 13:24   ` 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=1120765940.30316.62.camel@localhost \
    --to=johnm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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