All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Chip Salzenberg <chip@pobox.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: "Missing, Reward Offered: /proc/asound/dev"
Date: Mon, 19 May 2003 11:28:09 +0200	[thread overview]
Message-ID: <s5h7k8ne15i.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030516205018.GI7921@perlsupport.com>

At Fri, 16 May 2003 16:50:18 -0400,
Chip Salzenberg wrote:
> 
> OK, I'm in the habit of playing with the CVS drivers, and of course
> when it breaks it's my own fault, and that's fine ... but:
> 
> Today I see in CVS that the "/proc/asound/dev" directory is not just
> temporarily broken; its support has been entirely removed.  Now none
> of my alsa apps (well, OK, I only have two) are happy, nor do they
> have any prospect of being happy in the future.

well, the device files on proc fs seem not favorite of kernel people,
and we are trying to remove them entirely.  the current cvs version
supports only static device files or devfs for the dynamic device
files.

please remove the symlink on /dev/snd and run snddevices script in
alsa-driver package to create static device files.  once after you
made them, everything should work as it was.


Takashi


-------------------------------------------------------
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

      reply	other threads:[~2003-05-19  9:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16 20:50 "Missing, Reward Offered: /proc/asound/dev" Chip Salzenberg
2003-05-19  9:28 ` Takashi Iwai [this message]

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=s5h7k8ne15i.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=chip@pobox.com \
    /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.