01-20-2012
Thanks a lot! I am going to give it a shot
9 More Discussions You Might Find Interesting
1. Solaris
Hi All ,
I try to install some packages in my global zone...
On the execution of the installion of the script it quits by saying the error
"Non global zone check failed"
Kindly help me in this regard
Thanks in advance,
jeganr (7 Replies)
Discussion started by: jegaraman
7 Replies
2. Solaris
Hi Gurus
I am not able to ping the local zone from global zone
when i am trying to ping i am getting below
ICMP Host Unreachable from gateway zone ( 192.268.35.210)
for icmp from zone ( 192.168.35.210) to sun1 ( 192.168.35.210)
However i can ping local zone from global
please... (12 Replies)
Discussion started by: kumarmani
12 Replies
3. Solaris
How to check the global zone name from local zone. (6 Replies)
Discussion started by: fugitive
6 Replies
4. Solaris
Dears,
I would like to convert solaris 10 x86 and solaris 10 sparc (Global Zones) physical servers into Local zones.
i found a document which seems to be helpful but i'm stuck @ the 1st step.
to test this i want to do it 1st on x86 system running under vmware ESXi and if it succeeds i will... (1 Reply)
Discussion started by: mduweik
1 Replies
5. Solaris
I have configured three zones on Solaris-11. These are non-global zones contain Solaris-11 only. One of the zone is not booting up, complaining about IP address in use, while it is not.
root@tdpdmsp02 # zoneadm list -icv
ID NAME STATUS PATH BRAND IP... (3 Replies)
Discussion started by: solaris_1977
3 Replies
6. Solaris
Am new on Solaris
If I compare with ESXi default timezone is UTC and we have to set BIOS timezone to UTC too .
What we follow and best practice in Solaris Sparc servers .
Thanks in advance . (2 Replies)
Discussion started by: Shirishlnx
2 Replies
7. Programming
I can't compile anything, the final make error says "Command failed for target `install-recursive'", but I am not able to identify the root cause of that error, I tried with cc, gcc 4.5, also gcc 5.2, using make, using gmake 3.82, ld 5.11, gld 2.31... and I am totally stuck yet... please help, to... (4 Replies)
Discussion started by: sugar222
4 Replies
8. 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
9. Solaris
Hi, hoping someone can help, its been a while since I used Solaris.
After creating a NGZ (non global zone), the NGZ can access the GZ (Global Zone) and the GZ can access the NGZ (using ssh, zlogin)
However, the NGZ cannot access any other netwqork devices, it can't even see the default router
... (2 Replies)
Discussion started by: GazinLincoln
2 Replies
LEARN ABOUT FREEBSD
i8254
ATTIMER(4) BSD Kernel Interfaces Manual ATTIMER(4)
NAME
attimer -- i8254 Programmable Interval Timer (AT Timer) driver
SYNOPSIS
This driver is a mandatory part of x86 kernels.
The following tunables are settable from the loader(8):
hint.attimer.X.clock
controls support for the event timer functionality. Setting this value to 0 disables it. The default value is 1.
hint.attimer.X.timecounter
controls support for the time counter functionality. Setting this value to 0 disables it. The default value is 1.
hw.i8254.freq
allows overriding the default counter frequency. The same value is also available at run-time via the machdep.i8254_freq sysctl.
DESCRIPTION
This driver uses i8254 Programmable Interval Timer (AT Timer) hardware to supply the kernel with one timecounter and one event timer, and to
generate sound tones for the system speaker. This hardware includes three channels. Each channel includes a 16 bit counter which decreases
with a known, platform-dependent frequency. Counters can operate in several different modes, including periodic and one-shot. The output of
each channel has platform-defined wiring: one channel is wired to the interrupt controller and may be used as event timer, one channel is
wired to the speaker and used to generate sound tones, and one timer is reserved for platform purposes.
The attimer driver uses a single hardware channel to provide both time counter and event timer functionality. To make this possible, the
respective counter must be running in periodic mode. As a result, the one-shot event timer mode is supported only when time counter func-
tionality is disabled.
The event timer provided by the driver is irrelevant to CPU power states.
SEE ALSO
apic(4), atrtc(4), eventtimers(4), hpet(4), timecounters(4)
BSD
May 26, 2014 BSD