From owner-freebsd-current@FreeBSD.ORG Sun Jun 20 23:17:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8AE9E16A4CE for ; Sun, 20 Jun 2004 23:17:59 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.199]) by mx1.FreeBSD.org (Postfix) with SMTP id 24F7243D4C for ; Sun, 20 Jun 2004 23:17:59 +0000 (GMT) (envelope-from jcagle@gmail.com) Received: by mproxy.gmail.com with SMTP id d78so194404rnf for ; Sun, 20 Jun 2004 16:17:54 -0700 (PDT) Received: by 10.38.207.32 with SMTP id e32mr10019rng; Sun, 20 Jun 2004 16:17:54 -0700 (PDT) Message-ID: <6863f0c9040620161714ec8d14@mail.gmail.com> Date: Sun, 20 Jun 2004 18:17:54 -0500 From: John Cagle To: freebsd-current@freebsd.org In-Reply-To: <20040620194058.9394.qmail@web14805.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20040620194058.9394.qmail@web14805.mail.yahoo.com> cc: Rostislav Krasny Subject: Re: Entropy device is blocked. Dance fandango on keyboard to unblock. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jun 2004 23:17:59 -0000 On Sun, 20 Jun 2004 12:40:58 -0700 (PDT), Rostislav Krasny wrote: > I already reported this problem at 19 April 2004 but it is not fixed > yet. You can find my original report and a reply to it there: > > http://lists.freebsd.org/pipermail/freebsd-current/2004-April/025991.html > http://lists.freebsd.org/pipermail/freebsd-current/2004-April/026036.html > > When I tried to install the latest i386/5.2-CURRENT-20040619-JPSNAP > snapshot the problem happened again. Does somebody know when this > problem would be fixed? I also see this same problem when installing 5-CURRENT snapshots. It is not obvious, since you don't see the "dance fandango" message unless you switch to the appropriate virtual terminal. Surely, this is a "must-fix" for 5.3 (or 5.2.2)... and I know your name's not Shirley. ;-) John