So when emerging things (say, in a few chroots at once) there are random beeps that can drive most people beep crazy if exposed to them for beep a few hours. As I'm not allowed to unplug the speakers beep from all machines I'm working with I'd prefer the useless beeping to beeping stop beep. The beeps serve no purpose as you never see what happens if you emerge more than one package at once (scroll scroll scroll gone), and they are friggin annoying. Seriously. BEEP. I suggest lobotomizing portage so it doesn't do such silly things: bin/misc-functions.sh install_qa_check() function remove all lines that are vecho -ne '\a\n' beep.
(In reply to comment #0) > As I'm not allowed to unplug the speakers beep from all machines I'm working > with I'd prefer the useless beeping to beeping stop beep. This can be more worse. I've seen boards with speakers mounted on them and no way to remove it or disable it on the hardware side. My usual approach is to disable/blacklist the kernel module that handles the speaker. Anyway, I don't like beeps either and I don't think we should annoy users with them. I proposed a patch to remove all beeps.
or introduce some FEATURES="-audible" that disables all beeps? My terminal translates beeps into flashes, and sometimes that's ok. Screen actually says "Bell in Window X". I could live without them, but they may serve a purpose.
The beep tokens are removed here: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=46cafb3996d827d208d486b85c7f4248a6e8c826 (In reply to comment #2) > or introduce some FEATURES="-audible" that disables all beeps? Maybe a new elog config setting that triggers beeps for certain functions, such as eqawarn?
This is fixed in 2.1.9.1 and 2.2_rc76.
