Sponsored Content
Full Discussion: 10 Recommended
Operating Systems Solaris 10 Recommended Post 302093050 by goasutlor on Tuesday 17th of October 2006 05:28:09 AM
Old 10-17-2006
You can check release of os that you install by

more /etc/release

you will know release of os

And if you install latest recommend patch on you box when you use command
uname -a you must see 5.10 Generic_(latest kernel patch version)

Smilie
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Crontab - Recommended way to edit?

What is the best way to modify the crontab file?? Edit the file and then use crontab 'filename' ??? I do not know how to use pico editor - so I cannot modify it this way, Any help is appreciated. (3 Replies)
Discussion started by: frustrated1
3 Replies

2. Linux

Recommended server for linux

Hi all, if you have to choose between an IBM x346 with serveraid 7k or an HP Proliant DL380 with smart array 6i to install Red Hat Enterprise Linux AS release 3 Update 3, which one would be your first choice? thks Bert (1 Reply)
Discussion started by: bert.n
1 Replies

3. UNIX for Dummies Questions & Answers

best or recommended unix os for new user

hello, I want to learn more on unix, and being use to windows (VERY SAD i know) i want to learn more, but which unix is recommended for a new user to become novice to advance? also what is a great website to look into to gain more knowledge of unix, i have the commands pretty good in my head,... (0 Replies)
Discussion started by: Siten0308
0 Replies

4. UNIX for Dummies Questions & Answers

recommended books for beginners

hi! what books do you recommend for someone like me who has no experience with unix? (2 Replies)
Discussion started by: briant
2 Replies

5. Solaris

Solaris 10 Recommended Patches

Does anyone get the following error message below when trying to download solaris 10 recommended patch? End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and... (8 Replies)
Discussion started by: Sarccastik Dude
8 Replies

6. Solaris

smpatch and recommended bundle

Hello, I am working on patching several systems and have begun working with smpatch as a possibly quicker way to accomplish patching. I have some observations that trouble me. The "smpatch analyze" only shows a small number of patches for a system (yes the registration is complete with a... (0 Replies)
Discussion started by: justme3
0 Replies

7. Solaris

10 Recommended Patch Not Working

Hello, The 10_Recommended update failed on 3 of 191, which was patch 119254-73 (the 1st 2 patches were skipped). I looked up the patch on Sunsolve (http://sunsolve.sun.com/search/document.do?assetkey=1-21-119254), which stated that 121133-02 was a required patch for 119254-73. I did a "showrev... (7 Replies)
Discussion started by: stringman
7 Replies

8. Red Hat

Recommended Linux books

Hi All, What books do you recomend to have for quick reference in regarding to Linux administration and performance monitoring? Thanks for your insight. (2 Replies)
Discussion started by: Beginer0705
2 Replies

9. Solaris

Can't unzip Recommended cluster

Hi all, got an annoyance going on at the moment.... Solaris 10 update 9. Trying to apply the latest 10_Recommended.zip when I rununzip 10_Recommended.zip I get unzip: cannot find 10_Recommended.zip It's there and all should be fine. a bit of Googling and I thought I had it... (1 Reply)
Discussion started by: Martincorneuk
1 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 26.9.119 SHAPE_PATCH(1)
All times are GMT -4. The time now is 09:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy