From: Jonathan Masters <mastersj@periscope-systems.freeserve.co.uk>
To: linux-sound@vger.kernel.org
Subject: FIXED
Date: Thu, 19 Aug 1999 04:47:57 +0000 [thread overview]
Message-ID: <marc-linux-sound-93506414424969@msgid-missing> (raw)
Hi,
You know that little sound problem from ealier on? well, it turns
out that all I needed to do was symlink the sound modules to any
different name and then load them twice with the appropriate parameters.
It's *very* cool now that I've got two sbs working together. Will get
midi working on the second card when I've got some time.....
I find "cat /dev/audio > /dev/audio1" to give some kind of strange
satisfaction - now that just says thatI'm far too tired and just plain
odd, etc.... :)
--
Jonathan C. Masters (jonathan@oxlug.org) PGP: www.brookes.ac.uk/~95227860/KEY
"Upon this rock I will build my church
and the gates of hell shall not prevail against it". -- Matthew 16, 17-18
reply other threads:[~1999-08-19 4:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-sound-93506414424969@msgid-missing \
--to=mastersj@periscope-systems.freeserve.co.uk \
--cc=linux-sound@vger.kernel.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