From owner-freebsd-current Wed May 31 12:31: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id C556E37B90D for ; Wed, 31 May 2000 12:30:55 -0700 (PDT) (envelope-from daemon@mips.inka.de) Received: from bigeye.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 12xECY-00050B-00; Wed, 31 May 2000 21:30:50 +0200 Received: (from daemon@localhost) by bigeye.mips.inka.de (8.9.3/8.9.3) id TAA78512 for freebsd-current@freebsd.org; Wed, 31 May 2000 19:42:52 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: "fetch | sh" panics system Date: 31 May 2000 19:42:51 +0200 Message-ID: <8h3iur$2cl7$1@bigeye.mips.inka.de> References: <20000530162831.A27439@sushi.unix-ag.uni-kl.de> To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christian Weisgerber wrote: > The following, completely innocuous command line > $ fetch -o - http://sites.inka.de/mips/unix/freebsd/xterm.shar | sh > executed as a non-priviledged user, reproducibly panics the machine. Some people have mailed that this particular command line just works on their machines. I'm not surprised. Still there must be some sort of problem, which happens to be triggered accidentally on my box for this unlikely case. I updated to yesterday's -CURRENT, and the problem persists. This is perfectly reproducible. I'll happily provide more details on my configuration, if anybody can give me a clue what might sensibly affect this. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message