From owner-freebsd-stable Sun Oct 7 3:42:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 5B97137B403 for ; Sun, 7 Oct 2001 03:42:36 -0700 (PDT) Received: (from olli@localhost) by lurza.secnetix.de (8.9.3/8.9.3) id MAA75357; Sun, 7 Oct 2001 12:42:35 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Date: Sun, 7 Oct 2001 12:42:35 +0200 (CEST) Message-Id: <200110071042.MAA75357@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG Reply-To: freebsd-stable@FreeBSD.ORG Subject: Re: Problems with installing 4.4-2001104-STABLE In-Reply-To: <20011006191100.A50977@svzserv.kemerovo.su> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.1-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Eugene Grosbein wrote: > kernel.GENERIC > 9440 blocks > DEBUG: wait for gunzip returned status of -1! Maybe this is completely unrelated, but I've seen gzip report "broken pipe" when extracting .tar.gz files like "gzip -dc foo.tar.gz | tar xf -". This happened to me on recently updated machines, so my guess is that something must have changed in gzip/gunzip. By the way, the exracted files are perfectly OK and complete, so it seems to be just cosmetic, apart from the exit code that indicates failure (which is a lie). Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message