From owner-freebsd-current Tue Apr 18 7:21: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 882E837B565 for ; Tue, 18 Apr 2000 07:20:58 -0700 (PDT) (envelope-from julian@elischer.org) Received: from gothic.iinet.net.au (gothic.iinet.net.au [203.59.24.252]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id WAA32059; Tue, 18 Apr 2000 22:20:55 +0800 Received: from jules.elischer.org (reggae-11-45.nv.iinet.net.au [203.59.69.45]) by gothic.iinet.net.au (8.8.5/8.8.5) with SMTP id WAA16915; Tue, 18 Apr 2000 22:20:48 +0800 Message-ID: <38FC6EF4.1CFBAE39@elischer.org> Date: Tue, 18 Apr 2000 07:19:32 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Peter Wemm Cc: Soren Schmidt , current@FreeBSD.ORG Subject: Re: HEADSUP! linprocfs going away in 72 hours. References: <20000418123537.A24141CD7@overcee.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > > > The biggest problem is that it re-opens a security hole that > was explicitly patched in procfs. then look at the hole, don't remove it. That's throwing the baby out with the bathwater.. It's a godsend when trying to run Linux binaries. > > Also, the way I see it, the linux procfs should probably only be > visible to linux sysvec processes... I think that you're overly compilcating things for the sake of an aesthetic argument. > It would be a damn shame to let > /compat/linux/procfs "sneak in" to the expected system > requirements for bsd > programs so that developers can use the easy way out rather than doing > something properly. That's extremely unlikely as most systems wouldn't have it.. Since I need it, I thought all my christmasses had come at once when I found it in the system as standard! The old port was cumbersom, always got out of date, and was not automatically updated when you rebuilt everything leading to lots of hours wasted looking for the reason for crashes. I can see moving it out to where the rest of the linux emulation code is but to remove it entirely seems the typical viking axe bloody-minded behaviour that's getting too familiar. > > > Julian > > Cheers, > -Peter -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message