And you determined this how? Can you show any dtrace output, or similar?
Determined by stopping one zone and testing connectivity from global+remaining
zone. Starting zone again and repeat.
I think you might be confusing simpler with familiar.
I tnking your'e making an assumption without
I can't see how virtualising a NIC can have a lesser resource impact on an
already challenged machine than using aliases.
From what I can see, the problem is resource bound. Either the CPU can't
handle the virtualization, or the NIC driver isn't handling it.
Whichever it is, the machine is
Hi,
I recently installed my ageing test machine with OSol snv_134. Zero problems
and the driver utility reported all hardware working.
The machine configuration is:
Shuttle PC, AMD Athlon 64 3000+, 2GB DDR-400, 200GB HDD.
First thing I did was to turn off gdm to save on resources.
Next,
Before you go all macahoic on the audience, consider this - if you think
Oracles' lack of communication is bad, try a life with Pastor Jobs. At first it
was great - as with any drug. Then came the hard drugs of heavy machinery
emptying your pockets, and at last the thugs of the legal shutting
I continually say that solaris opensolaris are designed to be servers, not
desktops. I'd like
to go into the reasons why, and see what other opinions people have about
this.
Your'e way off.
The characteristics that I think make up servers:
Servers are always on.
Nope. One of the
Empty barrels tend to make the loudest noises...
It has been stated time and time again that it's _very unlikely_ that anything
will be revealed before the fiscal year is over. That's on thursday the
earliest.
So why not keep a little peace and zip it until then? At least Oracle will
reveal
Thank you for your correction. I was misguided. Nevertheless, 4 days aren't
that much (and two of them a week-end) so I think it'll be prudent to wait a
few days more :)
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
