public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexey Maslennikov <alexey.maslennikov@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64]  Re: arts
Date: Sat, 9 Jul 2005 02:10:02 +0300	[thread overview]
Message-ID: <200507090210.07611.alexey.maslennikov@gmail.com> (raw)
In-Reply-To: <42CE6778.20304@gotadsl.co.uk>

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

As far as I remember, /dev/dsp is only used with OSS.
In case you use ALSA, it is created by OSS emulation. Possibly OSS emulation 
modules are not loaded. Module names are something like snd_*_oss.

P.S. I can be very wrong about it.


On Friday 08 July 2005 14:46, Peter Humphrey wrote:
> Tres Melton wrote:
> >On Fri, 2005-07-08 at 11:57 +0100, Peter Humphrey wrote:
> >>I hope I'm not hijacking this thread   ;-)    but can anyone tell me
> >>what creates /dev/dsp in the first place? On this newly reinstalled
> >>Xfce4 system it doesn't exist, even though the kernel sound modules do
> >>and have been loaded.
> >
> >I think that it is created by the deprecated devfs package.  The newer
> >udev package uses /dev/sound/dsp and make /dev/dsp a link to the newer
> >one for compatibility but since you don't have one it may only create
> >the link if the old device was there.
>
> Hmm. /dev/sound/dsp doesn't exist either, but I find:
>
> prh@wstn ~ $ ls -lL /dev/dsp?
> crw-rw----  1 root audio 14, 19 Mar  4 13:40 /dev/dsp1
> crw-rw----  1 root audio 14, 35 Mar  4 13:40 /dev/dsp2
> crw-rw----  1 root audio 14, 51 Mar  4 13:40 /dev/dsp3
>
> Now I find I've somehow omitted alsasound from the default runlevel;
> putting it in there and /etc/init.d/alsasound start gives /dev/dsp as a
> link to /dev/sound/dsp. So I've answered my own question, but I hope
> I've also exposed another little fact.
>
> --
> Rgds
> Peter Humphrey
> Linux Counter 5290, Aug 93.

-- 
Alexey Maslennikov
Oracle DBA and developer
*NIX system administrator

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2005-07-08 23:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-08  3:23 [gentoo-amd64] arts Benny Pedersen
2005-07-08  3:42 ` Zac Medico
2005-07-08  9:21 ` [gentoo-amd64] arts Duncan
2005-07-08 10:57   ` Peter Humphrey
2005-07-08 11:17     ` Tres Melton
2005-07-08 11:46       ` Peter Humphrey
2005-07-08 23:10         ` Alexey Maslennikov [this message]
2005-07-09  1:00           ` [gentoo-amd64] " Duncan
2005-07-09  2:37           ` [gentoo-amd64] " Luigi Pinna
2005-07-09  9:40             ` Alexey Maslennikov
2005-07-09 11:22               ` [gentoo-amd64] arts Luigi Pinna
2005-07-09 12:01                 ` [gentoo-amd64] arts Duncan
2005-07-11 16:04                   ` Luigi Pinna
2005-07-11 17:44                     ` Alexey Maslennikov
2005-07-12 11:16                     ` [gentoo-amd64] " Duncan
2005-07-09 10:15             ` Duncan
2005-07-10 10:17   ` [gentoo-amd64] " Benny Pedersen
2005-07-10 11:50     ` [gentoo-amd64] " Duncan

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=200507090210.07611.alexey.maslennikov@gmail.com \
    --to=alexey.maslennikov@gmail.com \
    --cc=gentoo-amd64@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