:> 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- repeatable crash in -current (softupdates, NFS) Viren R.Shah
- Re: repeatable crash in -current (softupdates, NFS) Eivind Eklund
- Re: repeatable crash in -current (softupdates, NF... Lester Igo
- Re: repeatable crash in -current (softupdates, NF... Viren R.Shah
- Re: repeatable crash in -current (softupdates... Matthew Dillon
- Re: repeatable crash in -current (softupd... Eivind Eklund
- Re: repeatable crash in -current (so... Eivind Eklund
- Re: repeatable crash in -current (so... Matthew Dillon
- Re: repeatable crash in -current... Matthew Dillon
- Re: repeatable crash in -cur... Viren R.Shah
- Re: repeatable crash in -cur... Viren R.Shah
- Re: repeatable crash in -cur... Matthew Dillon
- Re: repeatable crash in -current (softupdates, NFS) Greg Lehey
- Re: repeatable crash in -current (softupdates, NF... Viren R.Shah
- Re: repeatable crash in -current (softupdates... Matthew Dillon
- Re: repeatable crash in -current (softupd... Julian Elischer
- Re: repeatable crash in -current (so... Matthew Dillon
- Re: repeatable crash in -current... Doug Rabson