Sponsored Content
Full Discussion: ldom patching
Operating Systems Solaris ldom patching Post 302636527 by Revo on Monday 7th of May 2012 02:30:02 PM
Old 05-07-2012
As you can have the guest domains running at different patch levels than the host, and each other, as they are effectively "independant" machines I don't think it matters, as long as you follow the patch guidelines and recommendations for whichever you do.

We have always done the host domain first, but that is ore of an internal method of getting approval from the differing departments with "machines" running on it.

Of course, whichever you do, you do have a good full backup before you start work right? Smilie
 

7 More Discussions You Might Find Interesting

1. Solaris

Autosys on LDOM

Has anyone configured an Autosys server to run on a Solaris LDOM? I can't think of any obvious reason why there would be a problem with it, but.... Jerry (0 Replies)
Discussion started by: JerryHone
0 Replies

2. AIX

ldom and lpar

hi, Plz let me know if the concept of sun ldom and aix lpar is same or not. thnx, snj (1 Reply)
Discussion started by: snjksh
1 Replies

3. Solaris

ldom and zone

hi, what is the difference between ldom and zone. can we install any other os than sun in ldom. thanks, snj. (2 Replies)
Discussion started by: snjksh
2 Replies

4. Solaris

VxVM5.1 in a Ldom

Has any one installed and used VxVM5.1 in a Ldom .. i was able to install it but when i try to initialize a disk it gives me following error as the disks are imported from ZFS backend .. :-( and they does not show the target no. /etc/vx/bin/vxdisksetup -if c0d2s2 VxVM vxdisksetup ERROR... (0 Replies)
Discussion started by: fugitive
0 Replies

5. Solaris

LDOM reconfiguration after SB replacement

Hi All, server was down with hardware issue and we couldn't took the LDOM configuration backup. Now system-board replaced and we need to get recreate OLD LDOM configuration. please advice with me the possible solution. :mad::( Thanks N (1 Reply)
Discussion started by: Naveen.6025
1 Replies

6. Solaris

Ldom problem

Hi People, I have been trying to learn solaris ldoms, have created one on a T2000 and get the following error when try to install it off DVD WARNING: /virtual-devices@100/channel-devices@200/disk@1: Communication error with Virtual Disk Server using Port 0. Retrying If anyone could help... (8 Replies)
Discussion started by: callmebob
8 Replies

7. Solaris

Saving LDOM Confguration

Hi, I am new to Solaris LDOMs. I just need to confirm if I save the guest LDOM configuration. Destroy the LDOM and need to use exported xml file to setup same LDOM, is OS installation required or everything will come as it is for new LDOM. I heard that -------- ldm list-constraints -x... (3 Replies)
Discussion started by: praveensharma21
3 Replies
SHAPE_PATCH(1)						      General Commands Manual						    SHAPE_PATCH(1)

NAME
shape_patch - shapeTools RMS generate patch file SYNOPSIS
shape patch OLDRELEASE=<name1> NEWRELEASE=<name2> [PATCHFILE=<filename>] DESCRIPTION
Shape patch generates a patch file for updating $(OLDRELEASE) to $(NEWRELEASE). Both releases are identified by release names associated with the macros OLD-/NEWRELEASE on the command line. Valid release names are those generated by any of the shape_RMS (pre-)release building procedures (see shape_releas(1)). Performing 'vl -all' with the release identification file as argument usually gives a good overview of existing release names. Patch generation happens recursively over all subsystems being part of the current node. Hence, triggering shape patch from the top node of the central source repository creates a patch file for the whole system. The output of shape patch is stored in a file named <name1>+2+<name2>.pat. When the PATCHFILE macro is set on the command line, $(PATCH- FILE) is taken as output file name instead. Defining PATCHFILE=- on the command line causes the patch to be written to standard output. Note: For patches invoking multiple subsystems, $(PATCHFILE) should be set to an absolute pathname. If not, the patch generation procedure will leave an equally named patch file for each visited subsystem. The patch is constructed using the vdiff(1) command and can be applied to any installation of $(OLDRELEASE) by invoking patch(1). INCONVENIENCES
On System V machines, the generated patch file name will almost certainly exceed the 14 characters filename length limit. SEE ALSO
shape_releas(1), vdiff(1), patch(1) FILES
<name1>+2+<name2>.pat 13.10.119 SHAPE_PATCH(1)
All times are GMT -4. The time now is 02:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy