su den 13.03.2005 Klokka 15:04 (-0500) skreiv Daniel Jacobowitz: > I can't find any documentation about this, but it seems like the same > problem that has been causing me headaches lately; when I replace glibc > from the server side of an nfsroot, the client has a couple of > variously wrong reads before it sees the new files. If it breaks NFS > so badly, why is it the default for the Linux NFS server?
No, that's a very different issue: you are violating the NFS cache consistency rules if you are changing a file that is being held open by other machines. The correct way to do the above is to use GNU install with the '-b' option: that will rename the version of glibc that is in use, and then install the new glibc in a different inode. Cheers, Trond -- Trond Myklebust <[EMAIL PROTECTED]> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
