Date: Wed, 18 Jun 2003 14:28:47 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Dmitry Sivachenko <demon@freebsd.org> Cc: arch@freebsd.org Subject: Re: cvs commit: src/sys/fs/nullfs null.h null_subr.c null_vnops.c Message-ID: <39515.1055939327@critter.freebsd.dk> In-Reply-To: Your message of "Wed, 18 Jun 2003 16:20:54 %2B0400." <20030618122054.GA55870@fling-wing.demos.su>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20030618122054.GA55870@fling-wing.demos.su>, Dmitry Sivachenko writes : >On Wed, Jun 18, 2003 at 01:53:29PM +0200, Poul-Henning Kamp wrote: >> All of this have tangled the simple component formerly known as the >> buffer cache up in so many ways, that it is very hard for anybody >> to make heads and tails of it any more. >> >> So I am tempted to answer you question with: "Because it is all a >> mess" >> > >Are there any more-or-less correct FS implementation in the system one >could learn how things should be done from? The only arguably correct FS we have is by fiat of most use UFS. Unfortunately that is also the most complex FS we have. This is also a situation we should try to fix. -- 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?39515.1055939327>