Peter Memishian wrote: > Looks good; a few nits: > > > boot after upgrade. Use of an old bfu script with these new bits will > > result in no network interfaces being available at first boot, which > > can be rectified by rebooting a second time. > > I'm not sure it will result in no network interfaces. Instead, I think > the legacy nodes will just be used and by and large things will "work".
Okay; do we bother mentioning this at all then? After the IP interfaces have been plumbed using the legacy /dev nodes, dlmgmtd will eventually start and the administrator will still be able to use all of the features, I think (correct?). > > The bfu script was changed to merge the /etc/dladm/aggregation.conf > > and /etc/dladm/linkprop.conf files into a single > > /etc/dladm/datalink.conf file with a new format. Once the upgrade is > > done, bfu removes the old aggregation.conf and linkprop.conf files. A > > backwards bfu across the UV changes will not result in the old > > aggregation.conf and linkprop.conf being restored. > > As Cathy commented, the old files are not removed; they're suffixed with > .bak. Right. > > > This is also a flag day for users of _I_nstall. This project > > I think the usual notation is "Cap-eye Install" Fixed. > > chipsets, migration of networking-related configuration from one > > system or zone to another, etc... For examples and documentation, > > One dot after "etc." is enough :-) The more dots, the more stuff is left implied. ;-) I've fixed that. Thanks, -Seb
