From: Ben Collins <bcollins@debian.org>
To: Pat Suwalski <pat@suwalski.net>
Cc: Werner Almesberger <wa@almesberger.net>,
Pavel Machek <pavel@ucw.cz>, Matthias Schniedermeyer <ms@citd.de>,
"Martin J. Bligh" <mbligh@aracnet.com>,
Marc Giger <gigerstyle@gmx.ch>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 623] New: Volume not remembered.
Date: Wed, 23 Apr 2003 22:34:34 -0400 [thread overview]
Message-ID: <20030424023434.GF354@phunnypharm.org> (raw)
In-Reply-To: <3EA74BF1.2090700@suwalski.net>
On Wed, Apr 23, 2003 at 10:29:05PM -0400, Pat Suwalski wrote:
> Werner Almesberger wrote:
> >So you're claiming that users will find it more difficult to add
> >one line to rc.local than upgrading their kernel ?
>
> No.
>
> I believe he is saying that ever since 1984 and the Mac Plus, it has
> been expected that sound works right away without adding any lines anywhere.
>
> I have not seen a computer in the last year and a half that has not had
> either onboard sound or a card. It is very standard hardware these days.
> Therefore, your soundcard should work just like your keyboard does. You
> do not have to add any lines to any rc script to get the keyboard
> working, do you? Sound should not have to be any different, in an ideal
> world.
Sound may be a standard feature, but it does not get driven by a
standard interface like PS2 or HID keyboards do. It's also not as
straight forward as "sound or no sound". There's many different levels
of sound hardware, from the 2-channel basic stereo, to the 6-way Dolby
Digital 5.1.
Whether or not a line is needed in an rc script is really a shortcoming
of userspace, IMO. It's the responsibility of userspace to setup the
user's environment in the most friendly way.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
next prev parent reply other threads:[~2003-04-24 2:38 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 16:23 [Bug 623] New: Volume not remembered Martin J. Bligh
2003-04-23 16:32 ` Marc Giger
2003-04-23 16:45 ` Matthias Schniedermeyer
2003-04-23 16:56 ` Martin J. Bligh
2003-04-23 17:21 ` Matthias Schniedermeyer
2003-04-23 13:26 ` Pat Suwalski
2003-04-23 17:26 ` Martin J. Bligh
2003-04-23 17:45 ` Disconnect
2003-04-23 17:47 ` Matthias Schniedermeyer
2003-04-23 18:44 ` Martin J. Bligh
2003-04-23 17:49 ` Pat Suwalski
2003-04-23 18:56 ` Jörn Engel
2003-04-23 22:17 ` Pavel Machek
2003-04-23 22:35 ` Pat Suwalski
2003-04-23 22:55 ` Pavel Machek
2003-04-24 2:19 ` Werner Almesberger
2003-04-24 2:29 ` Pat Suwalski
2003-04-24 2:34 ` Ben Collins [this message]
2003-04-24 7:22 ` Jamie Lokier
2003-04-24 13:31 ` Werner Almesberger
2003-04-24 4:30 ` Valdis.Kletnieks
2003-04-23 23:15 ` Martin J. Bligh
2003-04-23 21:34 ` Werner Almesberger
2003-04-23 21:36 ` Martin J. Bligh
2003-04-23 22:14 ` Werner Almesberger
2003-04-23 22:18 ` Martin J. Bligh
2003-04-23 22:55 ` Werner Almesberger
2003-04-24 0:11 ` Jamie Lokier
2003-04-24 0:43 ` Werner Almesberger
2003-04-24 1:11 ` Jamie Lokier
2003-04-24 1:18 ` Martin J. Bligh
2003-04-24 1:22 ` Pat Suwalski
2003-04-24 2:11 ` Werner Almesberger
2003-04-24 2:40 ` Martin J. Bligh
2003-04-24 3:37 ` Werner Almesberger
2003-04-24 4:47 ` Martin J. Bligh
2003-04-24 13:16 ` Werner Almesberger
2003-04-24 7:14 ` Jamie Lokier
2003-04-24 13:38 ` Werner Almesberger
2003-04-24 13:49 ` Matthias Schniedermeyer
2003-04-24 14:08 ` Pat Suwalski
2003-04-24 14:34 ` Matthias Schniedermeyer
2003-04-24 15:04 ` Werner Almesberger
2003-04-24 15:23 ` Matthias Schniedermeyer
2003-04-24 16:01 ` Werner Almesberger
2003-04-24 16:26 ` Jaroslav Kysela
2003-04-24 21:22 ` Werner Almesberger
2003-04-25 10:03 ` Jaroslav Kysela
2003-04-25 10:30 ` Werner Almesberger
2003-04-24 21:36 ` Jamie Lokier
2003-04-24 23:55 ` Werner Almesberger
2003-04-25 0:05 ` Pat Suwalski
2003-04-25 10:41 ` Werner Almesberger
2003-04-25 10:04 ` Alan Cox
2003-04-25 17:44 ` Werner Almesberger
2003-04-25 17:59 ` Martin J. Bligh
2003-04-26 0:31 ` Pat Suwalski
2003-04-24 22:51 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-04-24 0:31 Ian Kumlien
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=20030424023434.GF354@phunnypharm.org \
--to=bcollins@debian.org \
--cc=gigerstyle@gmx.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=ms@citd.de \
--cc=pat@suwalski.net \
--cc=pavel@ucw.cz \
--cc=wa@almesberger.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 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.