On Thu, 2009-08-20 at 00:16 -0400, Girish M G wrote: > Sebastien Roy wrote: > > On Wed, 2009-08-19 at 23:15 -0400, Girish M G wrote: > >> Folks, > >> > >> Why is that /etc/dladm/datalink.conf is not copied over to the new BE > >> from old BE? > > > > I'm not sure exactly what you mean. The way to do a live-upgrade with > > zfs is to do a "lucreate -n <new-name>", which automatically creates a > > zfs snapshot of the current BE, including all files within it, thus > > creating <new-name>'s zfs filesystem. All files are duplicated in each > > BE automatically. > > > > Are you referring to some other mechanism? > > Yes. You can install a different image on your new BE other than what > you have in old BE. That is, new BE need not be derived from old BE. > > In that case, lucreate as this mechanism of copying over some files to > new BE. So that when we boot over to new BE, this configuration is still > there. > > If I understand things correctly, the files that will be copied over is > defined by /etc/lu/lu_transfer_list on the machine you live upgraded. > > /ws/install-nv-gate/usr/src/cmd/inst/liveupgrade/files/lu_transfer_list > > and in there /etc/dladm/datalink.conf is missing
Right, but is that used anymore? I haven't seen anyone use lu that way since zfs root became an option. It was extremely unreliable (probably because keeping that list of files up to date was not feasible) and most people just did an lumake everytime anyway to copy all files from the current BE to the other one. In any case, if there's a bug here and it's simple to fix, then maybe you can take that on, but with the demise of SXCE and the lack of upgrade option from s10, the live-upgrade stuff in OpenSolaris will meet a timely end in a few builds anyway... -Seb
