From: Nico Schottelius <nicos@pcsystems.de>
To: Oystein Viggen <oysteivi@tihlde.org>
Cc: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: added a new feature: disable pc speaker
Date: Fri, 04 May 2001 22:09:03 +0200 [thread overview]
Message-ID: <3AF30C5F.7445714F@pcsystems.de> (raw)
In-Reply-To: <8340.988979784@ocs3.ocs-net> <03wv7xm085.fsf@colargol.tihlde.org>
> > setterm -blength 0 (text)
> > xset b 0 (X11)
>
> Well, some buggy programs don't care about you turning off beeping in
> X. I think gnome-terminal or such has its own checkbox for turning
> beeps on or off.
Exactly.
> I still agree that this is fixing userspace bugs in the kernel, and
> probably not desirable, even if I think I'd disable the pc speaker if
> the kernel actually asked me. If nothing else, I figure it would make
> my kernel 0.5k or so smaller ;)
Something about that, didn't make any comparision to a original
2.4.4 kernel.
I first thought the same Keith did, a userspace program.
This could call the same asm code used in kd_nosound,
but the problem is, the next time _kd_mksound is called,
sound is enabled again.
Can somebody give me a hint where to find documentation about
sysctl and howto use/program that ?
This is what Simon and David suggested.
But as long as I am not able to make sysctl's, I would like
to add this feature under the General setup.
What do you think ?
Nico
next prev parent reply other threads:[~2001-05-04 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-04 11:37 added a new feature: disable pc speaker Nico Schottelius
2001-05-04 11:48 ` Simon Richter
2001-05-04 12:36 ` Keith Owens
2001-05-04 18:35 ` Oystein Viggen
2001-05-04 20:09 ` Nico Schottelius [this message]
2001-05-04 20:18 ` Oystein Viggen
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=3AF30C5F.7445714F@pcsystems.de \
--to=nicos@pcsystems.de \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=oysteivi@tihlde.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