From: Patrick Shirkey <pshirkey@boosthardware.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Removal of /proc/asound ?
Date: Tue, 20 May 2003 01:36:00 +0900 [thread overview]
Message-ID: <3EC907F0.9060208@boosthardware.com> (raw)
In-Reply-To: s5h4r3re0a8.wl@alsa2.suse.de
Takashi Iwai wrote:
>>How will this work if the user does not have a DEVFS enabled kernel?
>
>
> run snddevices script once. that's all.
>
Phew. Picked this thread up late but here you allay my fears. basically
if you don't run ./snddevices you get devfs and if you do you get proc.
This seems to have been working for a while (like 6 months or more). Is
there more to this than meets the eye???
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Being on stage with the band in front of crowds shouting, "Get off! No!
We want normal music!", I think that was more like acting than anything
I've ever done.
Goldie, 8 Nov, 2002
The Scotsman
-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java
code to make your application fit in a relational database is painful,
don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
next prev parent reply other threads:[~2003-05-19 16:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 22:16 Removal of /proc/asound ? Erik de Castro Lopo
2003-05-17 11:55 ` Jaroslav Kysela
2003-05-17 22:13 ` Erik de Castro Lopo
2003-05-19 9:46 ` Takashi Iwai
2003-05-19 10:03 ` Erik de Castro Lopo
2003-05-19 10:21 ` Jaroslav Kysela
2003-05-20 4:40 ` Conrad Parker
2003-05-20 5:09 ` David B Harris
2003-05-20 5:48 ` Conrad Parker
2003-05-20 8:15 ` Erik de Castro Lopo
2003-05-20 11:37 ` James Courtier-Dutton
2003-05-19 16:36 ` Patrick Shirkey [this message]
2003-05-21 11:18 ` Takashi Iwai
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=3EC907F0.9060208@boosthardware.com \
--to=pshirkey@boosthardware.com \
--cc=alsa-devel@lists.sourceforge.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