03-20-2009
Cool.. that worked
Thanks guys!!!
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Quick question would it effect Linux if I upgraded my Ram from 128RD Ram to 256RDRAM (I'm going to simply pop in a second 128 RAM chip)...would I need to change any configuration options etc or would Linux detect all this with no problem? (4 Replies)
Discussion started by: PravusMentis
4 Replies
2. UNIX for Advanced & Expert Users
Is there an easy (and safe) way to upgrade RedHat versions remotely? I know the difference between 7.2 and 7.3 is just a bunch of newer .rpm file versions. Or is there more? Do I have to boot the CD and choose upgrade? What if I'm 100 miles from the server and would like to avoid traveling there?... (1 Reply)
Discussion started by: ArkiMage
1 Replies
3. SuSE
Hello,
Anyone out there deal with updating OS on linux servers remotely? We use Suse but like to hear what someone else does with any linux version. We have network connectivity to our remote locations but it's just a DSL connection, so some will be fast and some will be slow.
Thanks for... (1 Reply)
Discussion started by: benefactr
1 Replies
4. News, Links, Events and Announcements
two articles related to live upgrades that i found useful and noteworthy.
Solaris 10 5/08 Live Upgrade Gotcha :: Col’s Tech Stuff
Solaris Live Upgrade and Patches :: Col’s Tech Stuff (0 Replies)
Discussion started by: pupp
0 Replies
5. AIX
Lets says I have 2 HMC's A and B, connected to a p570 managed system.
Right now the firmware level of the p570 is EM320_076 and that needs to be upgraded to EM340_095.
Now the HMC's are at V7R3.3 and as per the code matrix the HMC's needs to be upgraded to V7R3.4 Servicepack 2.
Now my... (5 Replies)
Discussion started by: balaji_prk
5 Replies
6. AIX
Hi everyone,
My current AIX OS level is "7100-01-06-1241"
and I am planning to upgrade it to " 7100-02-03 ".
Can i directly upgrade it to "7100-02-03" from 7100-01-06" ?
or first i need to upgrade the "7100-01-06" LPAR to TL 02 and then reboot and
then upgrade it to TL 02 SP03 ?
... (4 Replies)
Discussion started by: System Admin 77
4 Replies
7. What is on Your Mind?
On my never ending quest to get rid of table tags and make the site responsive for all device sizes, I plan to use CSS Flexbox with jQuery.
I tried using Bootstrap Flex and CSS Grids, but none of these worked as easy and clean as CSS Flexbox.
For example, today I changed the top header area... (0 Replies)
Discussion started by: Neo
0 Replies
8. What is on Your Mind?
Dear All,
I have made significant progress coding new discussion thread tagging features.
As always, we want all users to tag thread and moderators to tag threads with relevant keywords.
Moving forward, in addition to the #1 important "human tagging", we will also auto tag threads with one... (4 Replies)
Discussion started by: Neo
4 Replies
LEARN ABOUT PHP
shape_patch
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
20.7.119 SHAPE_PATCH(1)