From owner-freebsd-questions@FreeBSD.ORG Tue Jun 16 07:32:02 2015 Return-Path: Delivered-To: freebsd-questions@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 22C10ED9 for ; Tue, 16 Jun 2015 07:32:02 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from bede.qeng-ho.org (bede.qeng-ho.org [217.155.128.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BD46C878 for ; Tue, 16 Jun 2015 07:32:01 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from arthur.home.qeng-ho.org (arthur.home.qeng-ho.org [172.23.1.2]) by bede.home.qeng-ho.org (8.14.9/8.14.7) with ESMTP id t5G7VpuT006163; Tue, 16 Jun 2015 08:31:52 +0100 (BST) (envelope-from freebsd@qeng-ho.org) Message-ID: <557FD0E7.3050309@qeng-ho.org> Date: Tue, 16 Jun 2015 08:31:51 +0100 From: Arthur Chance User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Paul Macdonald CC: freebsd-questions@freebsd.org Subject: Re: freebsd-update error ln: ///rescue/[: No such file or directory References: <557F0002.4060400@ifdnrg.com> <44h9q8sys8.fsf@lowell-desk.lan> <557F0520.9020105@ifdnrg.com> In-Reply-To: <557F0520.9020105@ifdnrg.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jun 2015 07:32:02 -0000 On 15/06/2015 18:02, Paul Macdonald wrote: > > > On 15/06/2015 17:48, Lowell Gilbert wrote: >> Paul Macdonald writes: >> >>> I just saw a large list of errors for freebsd-update of the form >>> >>> Installing updates... >>> >>> ln: ///rescue/[: No such file or directory >>> ln: ///rescue/[: No such file or directory >>> .... >>> >>> is this something to panic about? >> Panic, no. But it is a problem; your /rescue tree is basically >> unpopulated. >> >> You didn't hand-delete "/rescue/[", did you? >> >> I'm not sure what the best way to re-install rescue would be, but you >> definitely want to do so. You might go years without needing it, but it >> saves a lot of time (and panic) when you do. > > /rescue is populated ( see first email), but i do note that it's > modification date is March, and that it does not have the odd looking [ > binary ( which i remember someone asking about in this list a while back). > I'd assumed that something was truncated in output but can see now that > it literally can't find /rescue/[ > > scp'd [ from a different box, free-update fetch/update happy now. Almost all entries in /rescue are the same file hard linked - try "ls -i /rescue" to confirm this. Unless the missing file is one of the exceptions (nextboot or dhclient-script on my system), you can recreate it simply by hard linking ln /rescue/rescue /rescue/ Also "/rescue/rescue command args" acts like "/rescue/command args" for any command that's crunched into rescue. -- Those who do not learn from computing history are doomed to GOTO 1