Date: Sun, 26 Mar 2000 00:59:29 -0500 (EST) From: Brian Fundakowski Feldman <green@FreeBSD.org> To: Dag-Erling Smorgrav <des@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/miscfs/linprocfs linprocfs_misc.c Message-ID: <Pine.BSF.4.21.0003260052580.15890-100000@green.dyndns.org> In-Reply-To: <200003251941.LAA67435@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 25 Mar 2000, Dag-Erling Smorgrav wrote: > des 2000/03/25 11:41:20 PST > > Modified files: > sys/miscfs/linprocfs linprocfs_misc.c > Log: > Attempt to provide real values for meminfo. What's the point, exactly? This linprocfs is kinda lame, in the traditional sense of the word. Shouldn't it have the features which the regular procfs has, too? Linux procfs doesn't only have an "exe" file in the pid-directories. This linprocfs seems to only have some of the "differences" between the two, and doesn't form the necessary "full" procfs. I'm sure some VFS work could be done to make the pid dirs unions, but why can't the missing functions/files from the original procfs be duplicated in linprocfs, as a simple solution? Right now, I just don't see the good in linprocfs. > Revision Changes Path > 1.2 +53 -20 src/sys/miscfs/linprocfs/linprocfs_misc.c -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" 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.21.0003260052580.15890-100000>