From owner-freebsd-current Wed Nov 11 15:56:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21216 for freebsd-current-outgoing; Wed, 11 Nov 1998 15:56:51 -0800 (PST) (envelope-from owner-freebsd-current@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 PAA21210 for ; Wed, 11 Nov 1998 15:56:46 -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 TAA27364; Wed, 11 Nov 1998 19:54:24 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 11 Nov 1998 19:54:23 -0400 (AST) From: The Hermit Hacker To: Andrzej Bialecki cc: =?ISO-8859-2?Q?S=F8ren_Schmidt?= , daeron@Wit401305.student.utwente.nl, shawn@cpl.net, osa@etrust.ru, current@FreeBSD.ORG Subject: Re: StarOffice-5.0... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Nov 1998, Andrzej Bialecki wrote: > On Wed, 11 Nov 1998, Søren Schmidt wrote: > > > It seems Andrzej Bialecki wrote: > > > > Yes, I've got the diffs against relatively fresh current. BTW, I asked > > > this question on -emulation, but got back a profound silence... Can we/ > > > should we incorporate this patch, and hide it under a kernel option, say > > > PROCFS_CMDLINE? The life would be soooo easier for people new to our linux > > > emulation... > > > > Hmm, if we should have a Linsux compatible /proc, it really should be > > a beast mounted on /compat/linux/proc. If you provide this, I'm sure > > it will be received with open arms :) > > I proposed some option which is within my reach (considering my skills and > time available). If not - well, the issue will have to wait until either > my abilities become appropriate, or someone else will take it over. As it > is now, I propose the above hack as a temporary solution. 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? 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? 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-current" in the body of the message