From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22492 invoked by uid 1002); 3 Nov 2003 09:37:13 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 25065 invoked from network); 3 Nov 2003 09:37:13 -0000 Message-ID: <1128.134.188.150.80.1067852232.squirrel@callisto.cs.kun.nl> In-Reply-To: <1067849092.3305.12.camel@localhost> References: <3FA5AF6F.5030501@codewordt.co.uk> <1067849092.3305.12.camel@localhost> Date: Mon, 3 Nov 2003 10:37:12 +0100 (CET) From: "Paul de Vrieze" To: gentoo-dev@gentoo.org User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal Subject: Re: [gentoo-dev] Vanilla behaviour in Gentoo Linux (long email) X-Archives-Salt: afabbf2f-9c0e-410b-a03b-0bedabe63a85 X-Archives-Hash: fbea0ae79c8b16c736a05ef1d320122b > > The FEATURES="sound" and FEATURES="notify" make sense to me, assuming > they're set by default along with some sort of FEATURES="logmessages" > that would save messages for later. > > I've been duly annoyed by beeps late at night while others are sleeping > as well. > > Every ebuild with 'sleep' or beeps would need to be checked to make sure > any instance wasn't necessary. > I agree with you. As a temporary solution to the beep problem you might consider using "emerge bla &>/tmp/bla.log&", which aditionally gives you a log so you can more easilly debug issues. Paul -- gentoo-dev@gentoo.org mailing list