From: info <info@dressmaker.ca>
To: alsa-devel@alsa-project.org
Subject: Re: Dead link in wiki under Tutorials
Date: Fri, 16 Oct 2020 13:33:33 -0400 [thread overview]
Message-ID: <235e02f7-70f0-d150-4e80-92844ef0f2af@dressmaker.ca> (raw)
In-Reply-To: <09f11cd1-473b-726e-84c9-3de8b9cf9fe3@dressmaker.ca>
There seems to be zero interest in restoring the tutorials, even though
only 1 tutorial link works.
I totally get it that it may be hard for you to reach out to the authors
of external material on dead web sites. But you should have not so much
difficulty restoring those 404 pages that link back to your own wiki.
Could you?
Thanks
Alex
On 2020-10-04 05:17 PM, info wrote:
> On the page
> https://www.alsa-project.org/wiki/Tutorials_and_Presentations there
> are dead links.
>
> ALSA 0.9.0 HOWTO <http://www.suse.de/%7Emana/alsa090_howto.html> - Dr
> Matthias Nagorni has writen a comprehensive tutorial for audio
> application developers.
> is dead. The article has been removed.
>
> Howto use the ALSA API <http://equalarea.com/paul/alsa-audio.html> -
> Paul Davis has also written a brief explanation.
> is dead. His site has been removed from the hosting site.
>
> ALSA Sequencer (draft)
> <http://www.alsa-project.org/%7Efrank/alsa-sequencer/> - Frank van de
> Pol's draft on programming the alsa sequencer.
> is dead, 404 error.
>
> Kernel OSS-Emulation
> <http://www.alsa-project.org/%7Eiwai/OSS-Emulation.html> - Takashi
> Iwai has written some notes on how ALSA handles OSS applications.
> is dead, 404 error.
>
> It is worth trying to restore them because there are very few
> resources on ALSA programming.
>
> Regards
> Alex
>
next prev parent reply other threads:[~2020-10-16 17:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 16:22 Discover a microphone device, to later discover if it is receiving input info
2020-10-04 21:17 ` Dead link in wiki under Tutorials info
2020-10-16 17:33 ` info [this message]
2020-10-09 12:39 ` Discover a microphone device, to later discover if it is receiving input info
2020-10-09 14:07 ` Jaroslav Kysela
2020-10-09 15:35 ` Takashi Iwai
2020-10-09 16:11 ` info
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=235e02f7-70f0-d150-4e80-92844ef0f2af@dressmaker.ca \
--to=info@dressmaker.ca \
--cc=alsa-devel@alsa-project.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;
as well as URLs for NNTP newsgroup(s).