From owner-freebsd-current Mon Sep 11 18:00:51 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA14022 for current-outgoing; Mon, 11 Sep 1995 18:00:51 -0700 Received: from disperse.demon.co.uk (disperse.demon.co.uk [158.152.1.77]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id SAA14015 for ; Mon, 11 Sep 1995 18:00:42 -0700 Received: from post.demon.co.uk by disperse.demon.co.uk id aa15830; 11 Sep 95 21:02 +0100 Received: from palmer.demon.co.uk by post.demon.co.uk id aa17944; 11 Sep 95 20:59 +0100 Received: from localhost (localhost [127.0.0.1]) by palmer.demon.co.uk (8.6.11/8.6.11) with SMTP id TAA06412 ; Mon, 11 Sep 1995 19:37:27 +0100 X-Message: This is a dial-up site. Quick responses to e-mails should not be relied upon. Thanks! To: "Jordan K. Hubbard" cc: current@freefall.freebsd.org Subject: Re: Is nullfs broken in -current? In-reply-to: Your message of "Mon, 11 Sep 1995 00:22:14 PDT." <199509110722.AAA01160@time.cdrom.com> Date: Mon, 11 Sep 1995 19:37:26 +0100 Message-ID: <6410.810844646@palmer.demon.co.uk> From: Gary Palmer Sender: current-owner@FreeBSD.org Precedence: bulk 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