12-01-2006
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Simple question:
After applying a cluster patch to a sun solaris box I am left with a root volume 81% full. I could run through the hassle of resizing the slices which is way too much work for a Ultra 5 running DNS only.
Is there a way to clean up the /var/sadm/pkg area, aka dump the save info. (5 Replies)
Discussion started by: edkung
5 Replies
2. Solaris
"Solaris 10 is here and so are the latest patches. For a limited time SunSolve will provide access to all Solaris 10 patches. Download the latest Solaris 10 patches using Patchfinder and find updated support content using the SunSolve Knowledgebase. After this promotion ends, Solaris 10 security... (2 Replies)
Discussion started by: busta
2 Replies
3. Solaris
Is there any way to show the patches that have been installed in what order, or by date?
For example, we have servers, we run the sun patch cluster on them every so often. but then we have some 1zee 2zee's which id like to identify.
do i ahve to go into each directory and look at time stamps?... (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies
4. Solaris
I am seeking help to add patches to Solaris 10 on 64 bit Sparc server. This is to prepare the server for the installation of Oracle 10g. Please list command and specific directory that patches should be added to. Thanks (4 Replies)
Discussion started by: duke0001
4 Replies
5. Solaris
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
Has anyone ever seen the patch cluster just hang and do nothing?
When I run in debug mode, here is where it hangs...
I tried clearing out my profile, running in different shells, I have no idea whats going on, any help is appreciated...
export/home/unixadm/10_Recommended>ksh -x... (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
7. Solaris
Hi Friends...
can some one tel me any tool for analysing patch on solaris, then download n install it wit all dependency patches???? (3 Replies)
Discussion started by: sudhan143
3 Replies
8. Solaris
Hello all,
I wanted to check in Solaris 10 machine whether it has got all the required patches .
Is there any way to find out.
Rgds
Rj (6 Replies)
Discussion started by: jegaraman
6 Replies
9. Solaris
Can anyone link me to where I can get solaris 10 patches, since now sunsolve.sun.com redirects to some useless oracle support page? (1 Reply)
Discussion started by: goodvikings
1 Replies
10. Solaris
Hi,
From security guy, I was told to install below three patches on Solaris-10 (Sparc) server
120272-31
124393-12
125731-11
Here is output from server -
# showrev -p | grep 120272-31
# showrev -p | grep 120272
Patch: 120011-14 Obsoletes: 116781-02, 117447-01, 117463-05, 118371-10,... (3 Replies)
Discussion started by: solaris_1977
3 Replies
LEARN ABOUT DEBIAN
stg-import
STG-IMPORT(1) StGit Manual STG-IMPORT(1)
NAME
stg-import - Import a GNU diff file as a new patch
SYNOPSIS
stg import [options] [<file>|<url>]
DESCRIPTION
Create a new patch and apply the given GNU diff file (or the standard input). By default, the file name is used as the patch name but this
can be overridden with the --name option. The patch can either be a normal file with the description at the top or it can have standard
mail format, the Subject, From and Date headers being used for generating the patch information. The command can also read series and mbox
files.
If a patch does not apply cleanly, the failed diff is written to the .stgit-failed.patch file and an empty StGIT patch is added to the
stack.
The patch description has to be separated from the data with a --- line.
OPTIONS
-m, --mail
Import the patch from a standard e-mail file.
-M, --mbox
Import a series of patches from an mbox file.
-s, --series
Import a series of patches from a series file or a tar archive.
-u, --url
Import a patch from a URL.
-n NAME, --name NAME
Use NAME as the patch name.
-p N, --strip N
Remove N leading slashes from diff paths (default 1).
-t, --stripname
Strip numbering and extension from patch name.
-i, --ignore
Ignore the applied patches in the series.
--replace
Replace the unapplied patches in the series.
-b BASE, --base BASE
Use BASE instead of HEAD for file importing.
--reject
Leave the rejected hunks in corresponding *.rej files.
-e, --edit
Invoke an editor for the patch description.
-d, --showdiff
Show the patch content in the editor buffer.
-a "NAME <EMAIL>", --author "NAME <EMAIL>"
Use "NAME <EMAIL>" as the author details.
--authname AUTHNAME
Use AUTHNAME as the author name.
--authemail AUTHEMAIL
Use AUTHEMAIL as the author e-mail.
--authdate AUTHDATE
Use AUTHDATE as the author date.
--sign
Add a "Signed-off-by:" to the end of the patch.
--ack
Add an "Acked-by:" line to the end of the patch.
STGIT
Part of the StGit suite - see linkman:stg[1]
StGit 03/13/2012 STG-IMPORT(1)