From: CaT <cat@zip.com.au>
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@vger.kernel.org
Subject: Re: Future devfs plans
Date: Tue, 27 Jul 2004 09:01:16 +1000 [thread overview]
Message-ID: <20040726230116.GA6339@zip.com.au> (raw)
In-Reply-To: <41057B58.1040808@comcast.net>
On Mon, Jul 26, 2004 at 05:44:56PM -0400, Ed Sweetman wrote:
> Adrian Bunk wrote:
> > apt-get install alsa-base
> >
> >Check
> >
> > /var/lib/dpkg/info/alsa-base.postinst
> >
> >and (surprise, surprise!), you'll note the snddevices script is executed
> >when installing the alsa-base package.
>
> And someone who compiles the kernel for themselves and never needs the
Like I.
> alsa-base deb wouldn't have any ability to create the devices. MAKEDEV
alsa-base doesn't supply any modules:
# apt-file list alsa-base
alsa-base: etc/apm/event.d/alsa
alsa-base: etc/devfs/conf.d/alsa
alsa-base: etc/init.d/alsa
alsa-base: usr/share/alsa-base/alsa-base.conf
alsa-base: usr/share/alsa-base/modules-snippet.conf
alsa-base: usr/share/alsa-base/program-wrapper
alsa-base: usr/share/alsa-base/snddevices
alsa-base: usr/share/doc/alsa-base/FAQ
alsa-base: usr/share/doc/alsa-base/NEWS.Debian.gz
alsa-base: usr/share/doc/alsa-base/README
alsa-base: usr/share/doc/alsa-base/README.Debian
alsa-base: usr/share/doc/alsa-base/SOUNDCARDS.gz
alsa-base: usr/share/doc/alsa-base/WARNING
alsa-base: usr/share/doc/alsa-base/changelog.Debian.gz
alsa-base: usr/share/doc/alsa-base/copyright
alsa-base: usr/share/doc/alsa-base/examples/modules-1.0.conf
alsa-base: usr/share/linda/overrides/alsa-base
alsa-base: usr/share/lintian/overrides/alsa-base
And the init.d script doesn't do any loading of modules. It saves and
restores the mixer settings.
> is the proper place to create devices, not a separate snddevices
> script. This is still a debian bug.
Correct, for any version of debian where the supplied kernel is >= 2.6
I'd say.
--
Red herrings strewn hither and yon.
next prev parent reply other threads:[~2004-07-26 23:11 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 [this message]
2004-07-27 21:24 ` Lee Revell
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=20040726230116.GA6339@zip.com.au \
--to=cat@zip.com.au \
--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 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.