Date: Wed, 11 Nov 1998 18:36:09 -0800 From: Mike Smith <mike@smith.net.au> 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: <199811120236.SAA06936@dingo.cdrom.com> In-Reply-To: Your message of "Wed, 11 Nov 1998 19:54:23 -0400." <Pine.BSF.4.05.9811111952370.337-100000@thelab.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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 duplicates the contents of the argv[] array. It's not entirely clear why they feel that argv[] isn't good enough. > 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? I have to ask - why do you care? I can think of much better things to do with my time than stare at the list of IRQ's in use - what do they expect them to do? A little song and dance number perhaps? (If you need the information, try 'systat -vmstat'.) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com 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?199811120236.SAA06936>