Date: Wed, 11 Nov 1998 20:30:55 -0800 (PST) From: Alex Zepeda <garbanzo@hooked.net> To: The Hermit Hacker <scrappy@hub.org> Cc: Andrzej Bialecki <abial@nask.pl>, =?ISO-8859-2?Q?S=F8ren_Schmidt?= <sos@freebsd.dk>, daeron@Wit401305.student.utwente.nl, shawn@cpl.net, osa@etrust.ru, current@FreeBSD.ORG Subject: Re: StarOffice-5.0... Message-ID: <Pine.BSF.4.05.9811112024030.299-100000@zippy.dyn.ml.org> In-Reply-To: <Pine.BSF.4.05.9811111952370.337-100000@thelab.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9811112024030.299-100000>