From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9943 invoked from network); 12 Jan 2000 17:41:40 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 12 Jan 2000 17:41:40 -0000 Received: (qmail 14932 invoked by alias); 12 Jan 2000 17:41:25 -0000 Mailing-List: contact zsh-users-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 2865 Received: (qmail 14925 invoked from network); 12 Jan 2000 17:41:24 -0000 Sender: fg@mandrakesoft.com To: zsh-users@sunsite.auc.dk Subject: Re: Since pws13... References: <1000111173757.ZM9679@candle.brasslantern.com> From: Francis GALIEGUE Date: 12 Jan 2000 18:24:54 +0100 In-Reply-To: "Bart Schaefer"'s message of "Tue, 11 Jan 2000 17:37:57 +0000" Message-ID: X-Mailer: Gnus v5.7/Emacs 20.5 "Bart Schaefer" writes: > > I'm not entirely sure that will take care of your problem, because the set > of functions from -bart-8 worked fine for me before I remembered to make > the equivalent change in my own startup files, but its certainly a step in > the right direction. > Well, no, that wasn't it at all finally :) The problem is really strange indeed: it's a kernel patch which makes zsh choke! The culprit patch is SecureLinux... Go figure... The only related thing I can see about it is a limited preload of dentries, which would explain why all the suggested replacements to programs were builtins! -- fg # rm *;o o: command not found