From owner-freebsd-current Tue Apr 22 20:12:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA29942 for current-outgoing; Tue, 22 Apr 1997 20:12:29 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA29933 for ; Tue, 22 Apr 1997 20:12:22 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id WAA03824; Tue, 22 Apr 1997 22:12:06 -0500 (EST) From: "John S. Dyson" Message-Id: <199704230312.WAA03824@dyson.iquest.net> Subject: Re: Recent vfork kernel changes broke csh & tcsh! In-Reply-To: from "[______ ______]" at "Apr 23, 97 06:49:42 am" To: ache@nagual.ru (=?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?=) Date: Tue, 22 Apr 1997 22:12:06 -0500 (EST) Cc: toor@dyson.iquest.net, sef@Kithrup.COM, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Tue, 22 Apr 1997, John S. Dyson wrote: > > > I am backing it out anyway. > > No! Lets fix imgact_shell.c in the way Tor Egge suggest instead and see, > what happens... Modifiyng "const" argument of exec is true bug in > imgact_shell.c > Whomever fixes the imgact_shell problem can turn on the RFMEM option for vfork() again. Too many people were having problems, and there are other things to do. John