From owner-freebsd-questions@FreeBSD.ORG Mon Jun 15 17:02:31 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 39F5E1BC for ; Mon, 15 Jun 2015 17:02:31 +0000 (UTC) (envelope-from paul@ifdnrg.com) Received: from outbound.ifdnrg.com (outbound.ifdnrg.com [193.200.98.38]) by mx1.freebsd.org (Postfix) with ESMTP id CCE6E5E3 for ; Mon, 15 Jun 2015 17:02:30 +0000 (UTC) (envelope-from paul@ifdnrg.com) Received: from [192.168.100.230] (cpc72297-sgyl28-2-0-cust55.18-2.cable.virginm.net [81.98.112.56]) (authenticated bits=0) by outbound.ifdnrg.com (8.15.1/8.14.9) with ESMTPSA id t5FH2O45059991 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Mon, 15 Jun 2015 18:02:26 +0100 (BST) (envelope-from paul@ifdnrg.com) X-Authentication-Warning: outbound.ifdnrg.com: Host cpc72297-sgyl28-2-0-cust55.18-2.cable.virginm.net [81.98.112.56] claimed to be [192.168.100.230] Message-ID: <557F0520.9020105@ifdnrg.com> Date: Mon, 15 Jun 2015 18:02:24 +0100 From: Paul Macdonald User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 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> In-Reply-To: <44h9q8sys8.fsf@lowell-desk.lan> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit 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: Mon, 15 Jun 2015 17:02:31 -0000 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. thanks -- ------------------------- Paul Macdonald IFDNRG Ltd Web and video hosting ------------------------- t: 0131 5548070 m: 07970339546 e: paul@ifdnrg.com w: http://www.ifdnrg.com ------------------------- IFDNRG 40 Maritime Street Edinburgh EH6 6SA ---------------------------------------------------- High Specification Dedicated Servers from £100.00pm ----------------------------------------------------