The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Frank Cusack <fcusack@fcusack.com>
To: torvalds@osdl.org, lkml <linux-kernel@vger.kernel.org>
Subject: /proc/beep
Date: Wed, 10 Sep 2003 21:14:14 -0700	[thread overview]
Message-ID: <20030910211413.A17000@google.com> (raw)

/proc/beep is a kernel tweak that sends beep "signals" to a userspace
process reading the /proc/beep file.  There are one or two of these
modules you can find on the Internet.  In order to support them the
kernel needs to export kd_mksound.

Would a /proc/beep module be accepted into the main tree?  From the
ones I've found, I can understand why they might not be accepted.  But
I'm willing to do the [small amount of] work required to get one looking
like other kernel modules.

If not, could at least kd_mksound be exported by default anyway?  This 
would allow homegrown /proc/beep's to not require any kernel mods.

thx
/fc

             reply	other threads:[~2003-09-11  4:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-11  4:14 Frank Cusack [this message]
2003-09-11  4:42 ` /proc/beep Neil Brown
2003-09-11 17:22   ` /proc/beep Frank Cusack

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=20030910211413.A17000@google.com \
    --to=fcusack@fcusack.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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