29 Feb 2000 buzzz 1.00
buzzz — go buzzz.
buzzz -l i (loudness) -d f (duration) [-f f (frequency)] [--dragonfly (dragon style)] [--bumblebee (bumble style)] [--disk (computer style)] [-style (some style)] [--scan (scan mode)] [-sd i (scan duration)] <file.bzz|dir> (tune source)
buzzz buzzes. It can do so in different styles, at different base frequencies, and at different volumes. See the OPTIONS section for a description of all options.
The -l loudness and -d duration options are both mandatory. The last argument given must be a file containing the tune to buzz, or a directory containing such tune files. The tune must be contained in an interval of at most five tones. Non-conforming tunes may damage your soundcard.
Frequency in Hertz, can be specified as a positive real number.
Loudness, which is specified as an integer inbetween 0 and 100.
Duration in hours, can be specified as a positive real.
These are unary options specifying the style in which to buzz.
str should be one of bumblebee, dragonfly, mosquito, or disk.
This will buzz 10 seconds for each tune specified. Refer also to the -sd option.
Sets the scan time in (an integer number of) seconds. This affects the --scan option.
/etc/zoem/foriamzoem.bzz contains the zoem jingle.
/etc/zoem/zoem.ascii-art contains zoem related ascii art. An excerpt is shown below.
Currently, no environmental issues with buzzz.
If the tune spans an interval larger than 5 tones, buzzz will emit little beeps. If the interval exceeds an octave, buzzz will fork and exec bell.
repeats itself, especially from a buzzing point of view. Refer to  for an in-depth analysis. A different point of view is presented in .
The bell(1) manual.
On the www it is difficult to show a manual page as compiled for rendering in a terminal, but one can view a manual page as compiled for rendering by a postscript interpreter. Lo and behold buzzz.ps.
 Bugs Bunny. Foo Bar. A history of making, maintenance, repair, and disposal.
 Donald Duck. The futile mistake, and how it changes my life every day.