All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nicos@pcsystems.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE added a new feature: disable pc speaker
Date: Fri, 04 May 2001 22:01:02 +0200	[thread overview]
Message-ID: <3AF30A7E.DC8D9914@pcsystems.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]



[-- Attachment #2: Type: message/rfc822, Size: 944 bytes --]

From: Nico Schottelius <nicos@pcsystems.de>
To: Keith Owens <kaos@ocs.com.au>
Subject: Re: added a new feature: disable pc speaker
Date: Fri, 04 May 2001 21:58:50 +0200
Message-ID: <3AF309FA.24767C26@pcsystems.de>



Keith Owens wrote:

> On Fri, 04 May 2001 13:37:08 +0200,
> Nico Schottelius <nicos@pcsystems.de> wrote:
> >I have searched a long time for a method to disable the internal
> >speaker for every application, every daemon and so on.
>
> Userspace problem, userspace fix.

This sounds good :) ... but ->

>
>   setterm -blength 0 (text)
>   xset b 0 (X11)

This was what I tried and used before. Aplications like Netscape
get a beep throught it, although running xset b 0 or xset b off.



                 reply	other threads:[~2001-05-04 20:02 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=3AF30A7E.DC8D9914@pcsystems.de \
    --to=nicos@pcsystems.de \
    --cc=linux-kernel@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 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.