Date: Mon, 27 Mar 2000 08:22:25 +0200 (CEST) From: Blaz Zupan <blaz@amis.net> To: Brian Fundakowski Feldman <green@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.0003270817180.454-100000@gold.amis.net> In-Reply-To: <Pine.BSF.4.21.0003270026440.6527-100000@green.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> I'll restate it, hopefully more clearly. How's this: > > And then when some Linux app wants to use parts of procfs that are implemented > in both Linux native procfs and FreeBSD native procfs, but which are not in > FreeBSD native linprocfs? ... then "someone" implements the missing feature in FreeBSD native linprocfs :) But still, isn't having a linprocfs that half of the Linux apps can use better than having no linprocfs and not being able to run the apps at all? I'm not sure how easy it would be (probably not very, because it depends on FreeBSD sources?) to put it in ports together with the Linux emulation libraries. After all, its of no use if you don't have the Linux emulation running. Blaz Zupan, blaz@amis.net, http://home.amis.net/blaz/ Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia 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.0003270817180.454-100000>