11-27-2009
you should boot the system to single user and apply your patches. where is your patch log?
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi
quick and question for the unix expert here
i downloaded the lastest patch from sun.
i'm ready to patch my production server. should i just patch it as is or go in to init 1 or init S to do the patching.
someone told me that you can just patch the server in init 3 and some other... (2 Replies)
Discussion started by: xNYx
2 Replies
2. UNIX for Dummies Questions & Answers
Hey guys,
I was able to get my NIC running and set it to DHCP... I can ping it....SSH....and Telnet to my Solaris 9 machine. But when im on the machine I can't get Netscape or the automatic patching software to connect. Is there some DNS things i need to set or something im a little stumped.
... (6 Replies)
Discussion started by: kingdbag
6 Replies
3. Solaris
Hello to all, I have a quick question. I am learning Solaris, with Solaris 10 x86, and one of the chapters in the manual is about patching. So can I download free patches from the Sun page, I mean with out paying a license. Because It would be a great exercise to patch my installation of Solaris.... (1 Reply)
Discussion started by: piukeman
1 Replies
4. Solaris
Hi Gurus,
I am new to solaris patching.. while doing the patching do we need to have the root previligies and also need help while doing patching work if the server has veritas on it........
Thanks in advance.......... (10 Replies)
Discussion started by: samanth009
10 Replies
5. Solaris
Hi All,
I have a question ? Which all patches need to be applied in single user mode and which all not .Is there any rule all patches need to be applied in /var/tmp.Thanks in advance for answers.:) (1 Reply)
Discussion started by: rama krishna
1 Replies
6. Solaris
OK, finally managed to get root access to the machines.
Now running
# uname -a
SunOS unknown 5.8 Generic_108528-22 sun4u sparc SUNW,UltraAX-e2
# showrev -p
Patch: 112668-01 Obsoletes: Requires: Incompatibles: Packages: SUNWgzip
Patch: 109889-01 Obsoletes: 109353-04 Requires: ... (2 Replies)
Discussion started by: Norman Khine
2 Replies
7. Solaris
Hi all,
I would like to ask what will be the best practice for the following setup
/ - c0t0d0s0 - current BE (named First)
/ - c0t0d1s0 - alternate BE (name Second)
i have a non-global zone with zonepath in /zones/myzone
/mnt/opt - c0t0d2s6 (shared between the 2 BE)... (3 Replies)
Discussion started by: javanoob
3 Replies
8. Solaris
Hi Gurus
I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow.
Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 Replies
LEARN ABOUT OPENSOLARIS
brands
brands(5) Standards, Environments, and Macros brands(5)
NAME
brands - alternate operating environments for non-global zones
DESCRIPTION
The branded zone (BrandZ) framework extends the Solaris Zones infrastructure described in zones(5) to include the creation of brands, which
provide non-global zones that contain non-native operating environments.
The term "brand" can refer to a wide range of operating environments. All brand management is performed as extensions to the current zones
structure.
Every zone is configured with an associated brand. The brand type is used to determine which scripts are executed when a zone is installed
and booted. In addition, a zone's brand is used to properly identify the correct application type at application launch time. The default
is the native brand.
A branded zone will support exactly one brand of non-native binary, which means that a branded zone provides a single operating environ-
ment. Once a zone has been assigned a brand, that brand cannot be changed or removed.
BrandZ extends the zones tools in the following ways:
o A brand is an attribute of a zone, set at zone create time.
o The zonecfg tool (see zonecfg(1M)) is used to set a zone's brand type and configure the zone.
o The zoneadm tool (see zoneadm(1M)) is used to report a zone's brand type and administer the zone.
Device Support
The devices supported by each zone are documented in the man pages and other documentation for that brand. The zones infrastructure detects
any attempt to add an unsupported device and issues a warning to the administrator. If the administrator chooses to add an unsupported
device despite that warning, that device might or might not work as expected. The configuration will be untested and unsupported.
ATTRIBUTES
See attributes(5) for a description of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWzoneu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
mdb(1), zlogin(1), zonename(1), dtrace(1M), in.rlogind(1M), sshd(1M), zoneadm(1M), zonecfg(1M), kill(2), priocntl(2), getzoneid(3C),
ucred_get(3C), getzoneid(3C), proc(4), attributes(5), lx(5), native(5), privileges(5), zones(5), lx_systrace(7D), crgetzoneid(9F)
SunOS 5.11 13 Feb 2009 brands(5)