From owner-freebsd-current Wed Nov 11 20:31:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22193 for freebsd-current-outgoing; Wed, 11 Nov 1998 20:31:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-53.ppp.wenet.net [206.15.84.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22185 for ; Wed, 11 Nov 1998 20:31:30 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id UAA00648; Wed, 11 Nov 1998 20:30:56 -0800 (PST) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Wed, 11 Nov 1998 20:30:55 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: The Hermit Hacker cc: Andrzej Bialecki , =?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=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 a copy of argv[]. It's inappropiate for nearly anything, because it's just bloat. Sh scripts can access argv via $0..$x, and a well written C/C++ program does this in main. > 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? OTOH I think it's hilarious that someone can crash a Linux system trying to find info about their aic7xxx scsi adatper*. Perhaps extending kernfs to mirror the sysctl tree, and a machfs for other hardware related things (and then doing a union mount with/of devfs..) would be a good idea. But extending procfs to mirror every ounce of Linux bloatware is hardly a good thing, besides how are irqs an integral part of a process? * Yes, older versions of the Linux aic7xxx driver did have problems like this (2+ adapters created some sort of buffer overflow IIRC), obviously it's fixed now. - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message