I live in arizona, and still find day light savings time to be a HUGE pain - why you ask? I work for an international company that is head quartered in another state. All of our meeting times are based on PST. So twice a year all of my regularly schedule meetings actually change time, while it stays the same for most everyone else.
I keep seeing this claim.
However, we have done a bunch of testing with Xen. There are certain cases where xen can approach native performance. However, start doing high network or IO and it falls off quickly.
Yes, Xen is pretty nice and will continue to get better on hardware that has virtualizatin support but it isn't any where near native performance all the way around yet.
Because you are only buying 1 or 2 cpu's.
When you are trying to stuff 20,000 into one room, you really start to care how much electricity and cooling it takes to run them.
However, if you work with other countries and other time zones it becomes brutal. All of your meetings shift an hour when their time changes while they stay the same in their calendars. 8am meetings are bad enough but when they become 7...ouch
No, you are confused.
In America, people don't have to be responsible for their own actions. That is why we have government. I too would have spilled hot coffee on myself if it wasn't for the warning label.
Hint, that is sarcasm above:)
Agreed. People just don't get it.
Secondary DNS at a different location is important. For example, what happens if your primary DNS is down and your mail server is unavailable? Mail queues up. When things come back on line, mail starts flowing again.
What happens if your primary and seconday are in the same location and your link goes down? Other sites can't look up your name at all and mail starts bouncing.
Huge difference.
I can see what you dont need an enterprise edition - 200 workstations is hardly enterprise.
Try managing 20,000+ linux boxes. Some mixture of ia32 desktop, ia32 server, ia64 desktop, and ia64 server. Then throw commercial vendor software into the loop. They dont typically port to the latest and greatest. Many of the vendors I deal with are just now porting to redhat 6.2 and redhat 7.2. After mixing that all together, the enterprise releases make a lot more sense.
With the enterprise releases, you can get a vendor to port to it after it has been out for a year and there is still 4 years of support left.
I know this type of environment isnt common for a lot of people, but it is definitely out there.
I grew up in a very poor part of New Mexico. A huge percentage of the population was considered poverty. Only the poorest people had satellite TV and cell phones. I used to laugh when you would drive by some trailer house with a hole ripped in the side covered by card board...but there was still a satellite dish on the roof.
I live in arizona, and still find day light savings time to be a HUGE pain - why you ask? I work for an international company that is head quartered in another state. All of our meeting times are based on PST. So twice a year all of my regularly schedule meetings actually change time, while it stays the same for most everyone else.
I keep seeing this claim. However, we have done a bunch of testing with Xen. There are certain cases where xen can approach native performance. However, start doing high network or IO and it falls off quickly. Yes, Xen is pretty nice and will continue to get better on hardware that has virtualizatin support but it isn't any where near native performance all the way around yet.
Wow, you can quote Linus and you don't even give him credit.
Because you are only buying 1 or 2 cpu's. When you are trying to stuff 20,000 into one room, you really start to care how much electricity and cooling it takes to run them.
I agree it is very nice for a lot of things.
However, if you work with other countries and other time zones it becomes brutal. All of your meetings shift an hour when their time changes while they stay the same in their calendars. 8am meetings are bad enough but when they become 7...ouch
No, you are confused. In America, people don't have to be responsible for their own actions. That is why we have government. I too would have spilled hot coffee on myself if it wasn't for the warning label. Hint, that is sarcasm above :)
And you wonder why I will get your promotion
Agreed. People just don't get it. Secondary DNS at a different location is important. For example, what happens if your primary DNS is down and your mail server is unavailable? Mail queues up. When things come back on line, mail starts flowing again. What happens if your primary and seconday are in the same location and your link goes down? Other sites can't look up your name at all and mail starts bouncing. Huge difference.
> Not to mention the ability to address terabytes of memory without using PAE hacks.
Its pretty easy to address lots of memory on 64 bit hardware. You dont need any of these "PAE hacks" on anthing other than x86 - which is 32 bit.
Do you think Solaris addresses more than 4 gigs on x86 without PAE? - ( Hint, the answer is no )
PAE is only needed on x86 hardware. You dont need it on ultra sparc, ia64, or any other 64 bit processor.
I can see what you dont need an enterprise edition - 200 workstations is hardly enterprise. Try managing 20,000+ linux boxes. Some mixture of ia32 desktop, ia32 server, ia64 desktop, and ia64 server. Then throw commercial vendor software into the loop. They dont typically port to the latest and greatest. Many of the vendors I deal with are just now porting to redhat 6.2 and redhat 7.2. After mixing that all together, the enterprise releases make a lot more sense. With the enterprise releases, you can get a vendor to port to it after it has been out for a year and there is still 4 years of support left. I know this type of environment isnt common for a lot of people, but it is definitely out there.
No Doubt.
I grew up in a very poor part of New Mexico. A huge percentage of the population was considered poverty. Only the poorest people had satellite TV and cell phones. I used to laugh when you would drive by some trailer house with a hole ripped in the side covered by card board...but there was still a satellite dish on the roof.