Geoff and Jerry,
On Feb 4, 2009, at 2:17 AM, Geoff Shipman wrote:
Jerry,
I received update they did not use a force option to the attach just
the
-u. They noted that no log file was created in the
/var/sadm/system/logs directory of the NGZ.
This attach was stymied originally by a Veritas
Geoff Shipman wrote:
> Jerry,
>
> I received update they did not use a force option to the attach just the
> -u. They noted that no log file was created in the
> /var/sadm/system/logs directory of the NGZ.
>
> This attach was stymied originally by a Veritas package VRTSat that had
> patch 117
Jerry,
I received update they did not use a force option to the attach just the
-u. They noted that no log file was created in the
/var/sadm/system/logs directory of the NGZ.
This attach was stymied originally by a Veritas package VRTSat that had
patch 117499-02 with garbage characters in the
Jerry and Mike,
I have requested the log data as well as verification the -F option was
not used. I also asked for showrev -p output from the NGZ.
I will update when available. The log data looks to be in the
/var/sadm/system/logs directory of the NGZ and the file is called
update_log.
Thanks
Geoff Shipman wrote:
> Jerry,
>
> Thanks for the update on the /etc/release file. The customer is more
> concerned regarding the kernel patch info not listed in the NGZ.
>
>>From uname output in the NGZ we can see the kernel matches the global
> value. Its the lack of showrev -p data for that
On Mon, Feb 2, 2009 at 9:07 AM, Geoff Shipman wrote:
> Jerry,
>
> Thanks for the update on the /etc/release file. The customer is more
> concerned regarding the kernel patch info not listed in the NGZ.
>
> >From uname output in the NGZ we can see the kernel matches the global
> value. Its the la
Jerry,
Thanks for the update on the /etc/release file. The customer is more
concerned regarding the kernel patch info not listed in the NGZ.
>From uname output in the NGZ we can see the kernel matches the global
value. Its the lack of showrev -p data for that kernel revision that
customer is
Geoff Shipman wrote:
> Hello All,
>
> I attached a NGZ that was from an alternate system to a Update 6 system
> using the -u option. The NGZ is sparse but I don't think a whole root
> would behave much differently. The update worked and the NGZ was
> attached but I noted that the kernel revisio
Hello All,
I attached a NGZ that was from an alternate system to a Update 6 system
using the -u option. The NGZ is sparse but I don't think a whole root
would behave much differently. The update worked and the NGZ was
attached but I noted that the kernel revision via uname -a was the new
versio
