bityard Blog

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
2014:01:20:hmc_update_to_7.7.8.0 [2014/01/20 22:53] – created Frank Fegert2014:01:20:hmc_update_to_7.7.8.0 [2014/01/20 23:03] (current) – Frank Fegert
Line 13: Line 13:
  
 For me, the good news gathered from the release notes was: For me, the good news gathered from the release notes was:
-  * **Power Enterprise Pools** to share CoD resources among the machines in your environment without the need of a special RPQ (''chcodpool'', ''lscodpool'' and ''mkcodpool''). I still dare to dream that some day IBM will allow a fully dynamical sharing, even of non-CoD resources for us mere mortals. <+  * **Power Enterprise Pools** to share CoD resources among the machines in your environment without the need of a special RPQ (''chcodpool'', ''lscodpool'' and ''mkcodpool''). I still dare to dream that some day IBM will allow a fully dynamic sharing, even of non-CoD resources for us mere mortals. <
   * **LPM evacuation** to support the migration of all LPARs off a system within a single command, much like the VMware maintenance mode (''migrlpar [...] <nowiki>--</nowiki>all''). <   * **LPM evacuation** to support the migration of all LPARs off a system within a single command, much like the VMware maintenance mode (''migrlpar [...] <nowiki>--</nowiki>all''). <
   * **Regeneration and XML export** of the hypervisor runtime configuration (''mkprofdata''). <   * **Regeneration and XML export** of the hypervisor runtime configuration (''mkprofdata''). <
Line 121: Line 121:
 </code> < </code> <
  
-The MH01388 update still shows error messages with regard to symlink creation appearing during the update process, so i guess my DCR MR0809134336 went straight into the circular file. The newly introduced error message "''cp: cannot stat `.dev': No such file or directory''" probably originates from the shell script ''/images/installImages'' inside the MH01388 installation ISO image:+The MH01388 update still shows error messages with regard to symlink creation appearing during the update process, so i guess my DCR MR0809134336 went straight into the circular file. The newly introduced error message "''cp: cannot stat `.dev': No such file or directory''" probably also originates from the shell script ''/images/installImages'' inside the MH01388 installation ISO image:
  
 <code bash /images/installImages> <code bash /images/installImages>
Line 145: Line 145:
 dr-xr-xr-x 2 root root  2048 Nov 22 23:47 info dr-xr-xr-x 2 root root  2048 Nov 22 23:47 info
 -r-xr-xr-x 1 root root 15397 Nov  6 18:56 installImages -r-xr-xr-x 1 root root 15397 Nov  6 18:56 installImages
--r--r--r-- 1 root root 16384 Nov 25 16:49 .installImages.swp 
 -r-xr-xr-x 1 root root  2644 Oct 29 22:05 installK2Payloads.sh -r-xr-xr-x 1 root root  2644 Oct 29 22:05 installK2Payloads.sh
 -r--r--r-- 1 root root    28 Oct 29 01:45 inventory -r--r--r-- 1 root root    28 Oct 29 01:45 inventory
Line 158: Line 157:
 </cli> </cli>
  
-So either someone forgot to remove the not necessary copy command from the install script, or the file ''.dev'' supposed to be existing was forgotten. Either way lets hope the file ''.dev'' doesn't contain any vital information. Aside from that, up to now no issues with the new HMC version.+So either someone forgot to remove the not necessary copy command from the install script, or the file ''.dev'' supposed to be existing was forgotten during creation of the ISO image. Either way lets hope the file ''.dev'' doesn't contain any vital information. Aside from that, up to now no issues with the new HMC version.