On May 19, 2016 8:36 PM, "Chris Cappuccio" <ch...@nmedia.net> wrote: > > Jasper Valentijn [jasper.valent...@gmail.com] wrote: > > Maybe relevant... > > > > diskless(8), Example 10 states: > > > > If the */usr* partition is to be shared between machines, as in the example > > */etc/exports* above, a more suitable entry might be: > > > > myserver:/usr /usr nfs ro 0 0 > > That is a perfect setup, with the current library reordering scheme. > Only the main machine which actually hosts /usr on local disks would > re-order, the other machines would take what they're given and the > re-order operation would fail due to ro.
OK, diskless(8), Example 7 states: Populate myclient's root filesystem on the server. How this is done depends on the client architecture and the version of the OpenBSD distribution. It can be as simple as copying and modifying the server's root filesystem, or perhaps the files can be taken from the standard binary distribution. > > In fact, with the current scheme, this is really the only way you > should mount NFS clients. I mean, even though it's done with an > atomic mv, I wouldn't really want my NFS clients re-ordering shared > /usr/lib on reboot. Shouldn't each diskless client have a unique re-ordering independent of the server? Must an OpenBSD diskless client depend on myserver to reorder even if it's not able? Think not running OpenBSD. I read diskless(8) as: myclient must be OpenBSD and my server could be OpenBSD. Jasper
