Date: Mon, 11 Sep 1995 19:37:26 +0100 From: Gary Palmer <gary@palmer.demon.co.uk> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: current@freefall.freebsd.org Subject: Re: Is nullfs broken in -current? Message-ID: <6410.810844646@palmer.demon.co.uk> In-Reply-To: Your message of "Mon, 11 Sep 1995 00:22:14 PDT." <199509110722.AAA01160@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199509110722.AAA01160@time.cdrom.com>, "Jordan K. Hubbard" writes: >I just attempted to use it to loop "/usr/src" and "/usr/obj" mounts on >my system (^&*$@%!! broken make macros!) and every time I compile >anything substantive from /usr/src I now get a divide by zero and >panic. I could go into more detail here and will if this isn't >immediately reproducible by those interested in nullfs. Last person >I saw in that code was... David? Amazing - I'm getting to the end of my mail backlog :-) Comment: AFAIK, nullfs has always been broken for `writing' - but I used it successfully on my machine here for over 2 months read only fine. I think that may be your problem... Gary
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6410.810844646>