From owner-freebsd-security  Tue Dec 19 10:45:12 2000
From owner-freebsd-security@FreeBSD.ORG  Tue Dec 19 10:45:10 2000
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from daedalus.cs.brandeis.edu (daedalus.cs.brandeis.edu [129.64.3.179])
	by hub.freebsd.org (Postfix) with ESMTP
	id 321FB37B400; Tue, 19 Dec 2000 10:45:06 -0800 (PST)
Received: from localhost (meshko@localhost)
	by daedalus.cs.brandeis.edu (8.9.3/8.9.3) with ESMTP id NAA20394;
	Tue, 19 Dec 2000 13:45:02 -0500
Date: Tue, 19 Dec 2000 13:45:01 -0500 (EST)
From: Mikhail Kruk <meshko@cs.brandeis.edu>
To: Dag-Erling Smorgrav <des@ofug.org>
Cc: Kris Kennaway <kris@FreeBSD.ORG>, Mike Tancsa <mike@sentex.net>,
	<freebsd-security@FreeBSD.ORG>
Subject: Re: FreeBSD Security Advisory: FreeBSD-SA-00:77.procfs
In-Reply-To: <xzplmtcy5vg.fsf@flood.ping.uio.no>
Message-ID: <Pine.LNX.4.30.0012191343530.19915-100000@daedalus.cs.brandeis.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: meshko@daedalus.cs.brandeis.edu
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> > Everything seems to work just fine (including ps and who to the extent I'm
> > using them). The only problem I've had so far is that Star Office core
> > dumps.
>
> Update your linprocfs to one that provides proc/<pid>/cmdline and see
> if that helps. If not, please try to truss(1) or ktrace(1) soffice and
> see what files it tries to open.

see you previous e-mail :) I was talking about things you loose when you
umount procfs
Apparently Star office uses FreeBSD procfs, not linprocfs (not sure how).



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message