linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Ed Sweetman <safemode@comcast.net>
Cc: Adrian Bunk <bunk@fs.tum.de>, Jim Gifford <maillist@jg555.com>,
	"Adam J. Richter" <adam@yggdrasil.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Future devfs plans
Date: Tue, 27 Jul 2004 17:24:15 -0400	[thread overview]
Message-ID: <1090963455.1094.106.camel@mindpipe> (raw)
In-Reply-To: <41057B58.1040808@comcast.net>

On Mon, 2004-07-26 at 17:44, Ed Sweetman wrote:
> Adrian Bunk wrote:
> 
> >On Sun, Jul 25, 2004 at 08:17:42PM -0400, Ed Sweetman wrote:
> >     
> >  apt-get install alsa-base
> >
> >  
> >
> And someone who compiles the kernel for themselves and never needs the 
> alsa-base deb wouldn't have any ability to create the devices.  MAKEDEV 
> is the proper place to create devices, not a separate snddevices 
> script.  This is still a debian bug.

Ditto someone hacking on ALSA, or who needs to use ALSA CVS to get some
new feature, who doesn't want to have to build a .deb every time they
recompile.

This is a debian bug and not a valid objection to ditching devfs.

Lee


  parent reply	other threads:[~2004-07-27 21:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-26 14:45 Future devfs plans Adam J. Richter
2004-07-26  0:00 ` Jim Gifford
2004-07-26  0:17   ` Ed Sweetman
2004-07-26  0:29     ` Lee Revell
2004-07-26  0:59     ` Lee Revell
2004-07-26 18:09     ` Adrian Bunk
2004-07-26 21:44       ` Ed Sweetman
2004-07-26 23:01         ` CaT
2004-07-27 21:24         ` Lee Revell [this message]
2004-07-27 22:35           ` Adrian Bunk
2004-07-27 22:39             ` Lee Revell
2004-07-26  0:21 ` Rafael do N. Pereira
2004-07-26  0:31 ` Ramón Rey Vicente
2004-07-26  0:35   ` Ramón Rey Vicente
2004-07-26  5:35   ` Andreas Jellinghaus
2004-07-26  6:58     ` Erik Steffl
2004-07-27 16:55       ` David Bryson
2004-07-27 18:44         ` Erik Steffl

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=1090963455.1094.106.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=adam@yggdrasil.com \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maillist@jg555.com \
    --cc=safemode@comcast.net \
    /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 NNTP newsgroup(s).