From owner-freebsd-current  Sun Feb 25 10:10:20 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA09510
          for current-outgoing; Sun, 25 Feb 1996 10:10:20 -0800 (PST)
Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA09503
          for <current@freebsd.org>; Sun, 25 Feb 1996 10:10:18 -0800 (PST)
Received: (from imb@localhost)
	by asstdc.scgt.oz.au (8.6.12/BSD4.4)
	id FAA00531; Mon, 26 Feb 1996 05:09:46 +1100
From: michael butler <imb@scgt.oz.au>
Message-Id: <199602251809.FAA00531@asstdc.scgt.oz.au>
Subject: Re: -current breaks shell and tset
To: andreas@knobel.gun.de (Andreas Klemm)
Date: Mon, 26 Feb 1996 05:09:44 +1100 (EST)
Cc: current@freebsd.org
In-Reply-To: <199602251607.RAA00217@knobel.gun.de> from "Andreas Klemm" at Feb 25, 96 05:07:44 pm
X-Mailer: ELM [version 2.4 PL24beta]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
Precedence: bulk

Andreas Klemm writes:

> If I try to do a simple
> # cd /
> I get the message:
> chdir: Too many arguments.
 
> My tcsh (even after rebuild in single user mode from the 
> ports collection) isn't useable...

This is another non-obvious side-effect of the broken
lib/libc/db/hash/hash.c which also broke -stable completely. You have to get
a fixed version, remake termcap and anything else that was statically linked
with libc :-(

On -stable (since I backed out of running -current for precisely this kind
of instability) reversing out the change does not appear to fix kvm_mkdb
(and probably more) .. ps only spits out process names in parentheses. But
then, the -stable kernel doesn't even boot any more here ..

	michael