From owner-freebsd-current Mon Nov 29 15: 8:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4ADA1154D5; Mon, 29 Nov 1999 15:08:22 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA12218; Mon, 29 Nov 1999 15:08:22 -0800 (PST) (envelope-from dillon) Date: Mon, 29 Nov 1999 15:08:22 -0800 (PST) From: Matthew Dillon Message-Id: <199911292308.PAA12218@apollo.backplane.com> To: Eivind Eklund Cc: "Viren R.Shah" , freebsd-current@FreeBSD.ORG Subject: Re: repeatable crash in -current (softupdates, NFS) References: <14399.63511.296802.242618@jabberwock.rstcorp.com> <19991127191729.A53832@bitbox.follo.net> <14402.62122.461010.454021@jabberwock.rstcorp.com> <199911292152.NAA09656@apollo.backplane.com> <19991129235631.P60031@bitbox.follo.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Eivind, I'm not sure that change you made is legal. People use :> symlink creation the same way they use O_EXCL file creation - as a :> locking mechanism. In fact, in NFSv2 O_EXCL file creation is not :> atomic (I'm pretty sure) and symlink was the *only* method available. : :The sum of the changes I made does not (or is at least not supposed :to) change the semantics of symlink creation. If you see some way the :semantics are changed, please tell me - that's an error. Ah, ok. Now I see what you've done. I'm still not sure that's right, I'll have to go over it in more detail. I'll get back to you in private email. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message