Date: Mon, 12 Jun 2000 04:02:25 -0700 From: "David O'Brien" <obrien@freebsd.org> To: Juriy Goloveshkin <j@avias.com> Cc: current@freebsd.org Subject: Re: static linked files in /usr/bin Message-ID: <20000612040224.A89807@dragon.nuxi.com> In-Reply-To: <Pine.BSF.4.21.0006121215520.5939-100000@localhost>; from j@avias.com on Mon, Jun 12, 2000 at 12:42:42PM %2B0400 References: <20000611202732.B82436@dragon.nuxi.com> <Pine.BSF.4.21.0006121215520.5939-100000@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 12, 2000 at 12:42:42PM +0400, Juriy Goloveshkin wrote: > but /usr/bin and /usr/lib usualy live at the same filesystem and if > /usr/lib may be broken, what we may say about /usr/bin? Statically linked binaries in /usr/bin/ will still be usable. You didn't think about what I said. Tar *is* a recovery tool. I've killed libc.so.* and ld-elf.os before suffiently bad that I was quite glad tar was statically linked. > maybe RELEASE-bin* must be splited? say... configs,binaries and developer > stuff(includes,gcc stuff, lib*.a, developer's manpages) Diffs? -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000612040224.A89807>