Robert Milkowski wrote: > Hi. > > I've noticed that it's actually a link to /tmp/something sinc b39. > > The problem is that I have snv installs over the network from Linux > servers (boot and install server) and by default Solaris tries to > mount its image using NFSv4 from within x86.miniroot and it can't > mount (I don't know if it's a nfs4_domain problem or something else). > I don't know how to tell Linux nfs server not to use/adversize v4 > (like we can do in Solaris) so normally I modyfied /etc/default/NFS > in x86.miniroot to tell Solaris that highest version to use as a > client is v3 - it helps. > > Since b39 I remove a symbolink link and put my /etc/default/NFS file. > But maybe I can do it more cleanly? >
This change was a result of integrating the NFSv4 domain setting into sysidtool. sysidtool writes its configuration changes into the running files, and then they are copied into the installed system at the end, so the /tmp symlink is used to provide a writable target since / is read-only for installation. A better way might be to use a begin script to populate the /tmp/root/etc/default/nfs with your preferred version, because by replacing the symlink you're making that part of sysid not operate correctly. That likely isn't a problem if you're not actually changing it from the default on any of your installs. > ps. Solaris should fallback to nfsv3 I was told - proper bug was > reported, can't remember bug id right now. > I see 6341772 as one possibility, though that's x86 specific. Dave
