Date: Thu, 16 Dec 1999 09:18:33 -0800 From: "David O'Brien" <obrien@FreeBSD.ORG> To: current@FreeBSD.ORG Subject: Re: sh(1) broken caching [was: Re: Broken sh(1)?] Message-ID: <19991216091832.A74110@dragon.nuxi.com> In-Reply-To: <19991216154020.A41154@cons.org>; from cracauer@cons.org on Thu, Dec 16, 1999 at 03:40:20PM %2B0100 References: <712.945183175@axl.noc.iafrica.com> <38565DEA.4487DF53@scc.nl> <19991216154020.A41154@cons.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 16, 1999 at 03:40:20PM +0100, Martin Cracauer wrote: > You can also fool sh into running the *wrong* binary if if you have > two in showdowed paths: pdksh does not suffer from either this problem or the problem that started this thread (and does not coredump). We've shown in the past that pdksh is actually smaller (when linked statically) than ash. I still think we should *seriously* consider switching to pdksh. -- -- David (obrien@NUXI.com) 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?19991216091832.A74110>