linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Werner Almesberger <wa@almesberger.net>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Jamie Lokier <jamie@shareable.org>,
	Matthias Schniedermeyer <ms@citd.de>,
	Marc Giger <gigerstyle@gmx.ch>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	pat@suwalski.net
Subject: Re: [Bug 623] New: Volume not remembered.
Date: Thu, 24 Apr 2003 00:37:42 -0300	[thread overview]
Message-ID: <20030424003742.J3557@almesberger.net> (raw)
In-Reply-To: <25450000.1051152052@[10.10.2.4]>; from mbligh@aracnet.com on Wed, Apr 23, 2003 at 07:40:54PM -0700

Martin J. Bligh wrote:
> You turn it off once, and your distro keeps it that way. Doesn't seem
> that onerous to me. 

Okay, so now your distribution is aware of this configuration
issue.

> Indeed. Initial impression of people upgrading a kernel from 2.4 to 2.5/6
> is that "sound doesn't work in 2.5/6". Not good.

... but now it isn't. What gives ?

(Besides, you've just added the "silent" flag as another config item
besides the volume setting, using different interfaces, different
permissions, etc.)

> And all for the fact that when the user sets up the system, it just
> works. With sensible defaults. Instead of being an elitist piece of
> crap that only l33t g33ks can use.

Fine. But this discussion isn't about the end-user experience,
but about where a certain parameter should be set, and what its
transient default value should be.

Unexperienced users will just install a set of packages to upgrade
to a new kernel. So this change can just be included in one of
these upgrades. No superhuman effort needed.

As far as those are concerned who painstakingly build their own
kernel, update the things listed in Documentation/Changes, avoid
suble traps like CONFIG_SERIO_I8042, don't get confused by needing
new module utilities, etc., I'm fairly confident that they'll
consider setting the volume a rather minor challenge.

And you could even take the sting out of this one by adding an
appropriate warning to Documentation/Changes. That's a about all
the kernel-side support this issue deserves.

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina         wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/

  reply	other threads:[~2003-04-24  3:26 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
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 [this message]
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
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=20030424003742.J3557@almesberger.net \
    --to=wa@almesberger.net \
    --cc=gigerstyle@gmx.ch \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=ms@citd.de \
    --cc=pat@suwalski.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 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).