11-09-2016
I wouldn't use "normally" but "most" instead. All patches are "normal".
Kernel is an example, there are many patches that aren't kernel patches but that nevertheless need to be applied to all zones, not only the global one as you state.
Your last statement is incorrect and contradict the first statement of my previous posting.
6 More Discussions You Might Find Interesting
1. Solaris
Hi Guys,
My requirement is I have file called /opt/orahome/.profile in non global zone.
PATH=/usr/bin:/usr/ucb:/etc:/usr/sbin:/usr/local/bin:/usr/openwin/bin:.
export PATH
PS1="\${ORACLE_SID}:`hostname`:\$PWD$ "
export PS1
EDITOR=vi
export EDITOR
ENV=/opt/orahome/.kshrc
export ENV... (1 Reply)
Discussion started by: vijaysachin
1 Replies
2. Solaris
Hi Experts,
Can advise on this:
Global zone running on solaris 10, & the local zones on top running on solaris 9, but we need to patch the solaris 9 local zones & also the solaris 10 global zone.
Which should be patched first to avoid any crash in case, first local zones... (1 Reply)
Discussion started by: fizan
1 Replies
3. Solaris
I'm in an LDOM. I'm building non-global IP exclusive zones. I am using manifests and profiles to configure the system after install so I don't have to tab through the sysconfig startup dialog everytime I boot a system the first time for settings that never change (DNS, regional data, NTP etc). I... (0 Replies)
Discussion started by: os2mac
0 Replies
4. Solaris
I have a few non-globa zones running in a 10.10.xx.xx network on a machine that is on a 192.168.xx.xx network.
My goal is to allow each of the non-global zones to communicate to each other while not communicating on the 192.168.xx.xx network.
I am using the current version of Solaris 10 in... (7 Replies)
Discussion started by: BradJM
7 Replies
5. Solaris
Hi all - not really a problem as such, but just hoping someone can shed some light.
We point rexplorer to multiple Global zones and it works as expected. However, each Non-Global zone get around a hundred of root su'ing to root messages, i.e.:
SU 07/14 03:02 + ??? root-root
SU 07/14 03:02 +... (5 Replies)
Discussion started by: dlam
5 Replies
6. Solaris
I am planning to do solaris 11 global zone patching having solaris 10 branded zone. I have a doubts on step 8 specially
Can someone clear my step 8 doubts or if anything wrong between step 1 to step 9 please correct that also as I have pretty good idea about Step 10 mean patching in solaris 10... (2 Replies)
Discussion started by: amity
2 Replies
LEARN ABOUT DEBIAN
stg-squash
STG-SQUASH(1) StGit Manual STG-SQUASH(1)
NAME
stg-squash - Squash two or more patches into one
SYNOPSIS
stg squash [options] <patches>
DESCRIPTION
Squash two or more patches, creating one big patch that contains all their changes. In more detail:
1. Pop all the given patches, plus any other patches on top of them.
2. Push the given patches in the order they were given on the command line.
3. Squash the given patches into one big patch.
4. Allow the user to edit the commit message of the new patch interactively.
5. Push the other patches that were popped in step (1).
Conflicts can occur whenever we push a patch; that is, in step (2) and (5). If there are conflicts, the command will stop so that you can
resolve them.
OPTIONS
-n NAME, --name NAME
Name of squashed patch.
-m MESSAGE, --message MESSAGE
Use MESSAGE instead of invoking the editor.
-f FILE, --file FILE
Use the contents of FILE instead of invoking the editor. (If FILE is "-", write to stdout.)
--save-template FILE
Instead of running the command, just write the message template to FILE, and exit. (If FILE is "-", write to stdout.)
When driving StGit from another program, it is often useful to first call a command with --save-template, then let the user edit the
message, and then call the same command with --file.
STGIT
Part of the StGit suite - see linkman:stg[1]
StGit 03/13/2012 STG-SQUASH(1)