11-08-2016
A few comments:
- some patches might apply to packages that are required to be in sync across all zones including the global one (SUNW_PKG_ALLZONES property). In such case the patch will refuse to be applied to a single zone or the global zone only.
- for obvious reasons, kernel patches are of this kind
- Patches that do not modify files residing in inherited file-systems can be applied to a sparse zone.
This User Gave Thanks to jlliagre For This Post:
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-sink
STG-SINK(1) StGit Manual STG-SINK(1)
NAME
stg-sink - Send patches deeper down the stack
SYNOPSIS
stg sink [-t <target patch>] [-n] [<patches>]
DESCRIPTION
This is the opposite operation of linkstg:float[]: move the specified patches down the stack. It is for example useful to group stable
patches near the bottom of the stack, where they are less likely to be impacted by the push of another patch, and from where they can be
more easily committed or pushed.
If no patch is specified on command-line, the current patch gets sunk. By default patches are sunk to the bottom of the stack, but the --to
option allows to place them under any applied patch.
Sinking internally involves popping all patches (or all patches including <target patch>), then pushing the patches to sink, and then
(unless --nopush is also given) pushing back into place the formerly-applied patches.
OPTIONS
-n, --nopush
Do not push back on the stack the formerly-applied patches. Only the patches to sink are pushed.
-t TARGET, --to TARGET
Specify a target patch to place the patches below, instead of sinking them to the bottom of the stack.
-k, --keep
Keep the local changes.
STGIT
Part of the StGit suite - see linkman:stg[1]
StGit 03/13/2012 STG-SINK(1)