Date: Sun, 27 Jun 2004 22:58:38 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Michael Nottebrock <michaelnottebrock@gmx.net> Cc: "Karl M. Joch" <k.joch@ctseuro.com> Subject: Re: HEADSUP: ibcs2 and svr4 compat headed for history Message-ID: <27578.1088369918@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 27 Jun 2004 18:41:08 %2B0200." <200406271841.08596.michaelnottebrock@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200406271841.08596.michaelnottebrock@gmx.net>, Michael Nottebrock w rites: >> No, I am not able to maintain the moduls because i am not a good enough >> programmer. If that would be the case i would have adapted the stallion >> stl driver. > >In that case, you have to make yourself (and your customers, by proxy) heard. >If you don't complain loud enough, nobody will know that you depend on this >driver. Well, yes, making sure we know what bits are in use out there is always a good idea, but it is not enough to get things to stick around in the long run. That takes developer mind-share, and that seems to be pretty universally absent for ibcs2 and svr4. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?27578.1088369918>