Date: Mon, 15 Jun 2015 13:26:30 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Paul Macdonald <paul@ifdnrg.com> Cc: freebsd-questions@freebsd.org Subject: Re: freebsd-update error ln: ///rescue/[: No such file or directory Message-ID: <44d20wsx15.fsf@lowell-desk.lan> In-Reply-To: <557F0520.9020105@ifdnrg.com> (Paul Macdonald's message of "Mon, 15 Jun 2015 18:02:24 %2B0100") References: <557F0002.4060400@ifdnrg.com> <44h9q8sys8.fsf@lowell-desk.lan> <557F0520.9020105@ifdnrg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Paul Macdonald <paul@ifdnrg.com> writes: > /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). "[" is another name for "test", as used in shell scripts. Don't delete it, even if you think it's "funny looking." > I'd assumed that something was truncated in output but can see now > that it literally can't find /rescue/[ Yes. and can't link to it. The vast majority of the commands in /rescue/ are hard links to the same executable, which modifies its behaviour according to the name under which it was invoked. I don't use freebsd-update, but I wouldn't expect it to put in new links if the thing they're linking to isn't present -- in fact, I'd expect it to only make new links if the target had been installed or replaced. > scp'd [ from a different box, free-update fetch/update happy now. Be sure that you took /rescue/[ rather than /bin/[ ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44d20wsx15.fsf>