From owner-freebsd-chat Wed Nov 11 18:21:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08246 for freebsd-chat-outgoing; Wed, 11 Nov 1998 18:21:09 -0800 (PST) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from thelab.hub.org (nat0574.mpoweredpc.net [142.177.190.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08238 for ; Wed, 11 Nov 1998 18:21:07 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id UAA27653; Wed, 11 Nov 1998 20:54:43 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 11 Nov 1998 20:54:42 -0400 (AST) From: The Hermit Hacker To: Andrzej Bialecki cc: freebsd-chat@FreeBSD.ORG Subject: Linux emulation Re: StarOffice-5.0... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Moved to -chat... On Thu, 12 Nov 1998, Andrzej Bialecki wrote: > On Wed, 11 Nov 1998, The Hermit Hacker wrote: > > > Just curious, but what exactly does that '/proc/*/cmdline' thing > > "do", and is there any reason why it is inappropriate for it to be a > > standard part of our /proc? > > It\s just a copy of the argv[0]. Why the programs can\t access their > argv[0] instead is beyond me - looks like a very stupid thing... Agreed...but, if there a reason to *not* incorporate it? > > When talkign with friends that use Linux, and talking about our > > /proc file system, they think its hilarious that I can't go into proc and > > find out what irqs are being used by the system...maybe I'm missing > > something, but about the only way I can do it currently is to look through > > dmesg output? Is there another way? > > >From my POV, it's hilarious to go to /proc to read the hardware > parameters of the system - the name "proc" is supposed to mean "info > related to processes", isn't it? Agreed...so, now, what do we have? We have this *great* operating system built upon several years of stable code that can't run what is probably one of the most monumental software packages (free software packages, at that) that makes the difference between whether or not FreeBSD can go anywhere except in the machine room as a server... ...all because adding /proc/*/cmdline is basically putting more information into /proc then /proc "means"? Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message