From owner-freebsd-questions@FreeBSD.ORG Sun Mar 2 08:30:09 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 157981065670 for ; Sun, 2 Mar 2008 08:30:09 +0000 (UTC) (envelope-from sonicy@otenet.gr) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.77]) by mx1.freebsd.org (Postfix) with ESMTP id 837708FC12 for ; Sun, 2 Mar 2008 08:30:08 +0000 (UTC) (envelope-from sonicy@otenet.gr) Received: from [192.168.0.1] (athedsl-366477.home.otenet.gr [87.202.159.106]) by kane.otenet.gr (8.13.8/8.13.8/Debian-3) with ESMTP id m228U5wF024111; Sun, 2 Mar 2008 10:30:06 +0200 Message-ID: <47CA65C5.7010101@otenet.gr> Date: Sun, 02 Mar 2008 10:31:01 +0200 From: Manolis Kiagias User-Agent: Thunderbird 2.0.0.12 (X11/20080227) MIME-Version: 1.0 To: Tore Lund References: <47C93ABA.6020903@otenet.gr> <47C9C2B6.3000807@netscape.net> In-Reply-To: <47C9C2B6.3000807@netscape.net> Content-Type: text/plain; charset=ISO-8859-7; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: freebsd-update upgrade problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Mar 2008 08:30:09 -0000 Tore Lund wrote: > Manolis Kiagias wrote: > >> Hi, >> >> I have already upgraded a couple of machines from 7.0-RC1/2 to >> 7.0-RELEASE using: >> >> freebsd-update -r 7.0-RELEASE upgrade >> >> However, on this one machine, I get this: >> >> freebsd-update: cannot open files/.gz: No such file or directory >> > > I have no answer, but as step in hopefully the right direction, let me > ask: does /var/db/freebsd-update/files exist when you get that message? > Are there any files in it? > > I upgraded yesterday, and my ../files directory is full of *.gz files. > I can't really remember, but since I've deleted and recreated the entire folder, it should have been recreated at first run as well. I didn't really solve the freebsd-update problem, but I upgraded the machine in the following way: I did a binary upgrade from the CD, then csup'd the sources and recompiled the kernel. I guess if there continues to be a problem with freebsd-update, it may exhibit itself during normal updates as well.