We ARE talking servers from 2005-2007 here.
The V490, V890, E6900, E20000, E25000 stopped shipping in April 2009. The V445 is Ultrasparc IIIi, was announced in 2007, I think first shipped in 2008, with Solaris 10. So it won't even make *one* OS upgrade?
Strange, most place I dealt with the server was gone when the support ran out, which was typically 3 to 5 years depending on the contract.
So, you didn't have any "big iron" then?
Now since i'm sure Oracle doesn't sell support for this hardware anymore
They do.
I bet most companies have already shitcanned them or sold them off, so I bet this will only affect a minority at best. For those that are still running what is frankly in computing terms ancient hardware it isn't like there aren't free Linux distros that will run on these machines,
You want to run an unsupported, experimental port of Linux on an E6900, or an E10000, or an E20000?
and if you are so concerned about money you are running actual business on a server that old frankly I doubt you're gonna pay for an upgrade to the latest and greatest Solaris anyway.
In this market (midrange servers), it's usually not about the money, but the supposed "stability". And, you wouldn't pay to upgrade, you've been paying premium software support to be able to run whatever version of Solaris is supported.
So I don't see this as any different than say MSFT saying they wouldn't support running Winserver 2K10 on a P4, since that is the age we are talking about here. I just don't see old servers getting expensive new OSes, that just wouldn't make any sense. Maybe someone can chime in here and say why they'd buy new server licenses to run on 6 year old tech?
Our company bought new UltraSparc III and IV servers (V215s, V445s) in 2008 (bad decision, I didn't support it). At the same time we bought Sun X4450 Intel-based servers. Guess which ones will still have a supported OS in 7 year's time? The cheaper ones with 4 times the cores.
We ARE talking servers from 2005-2007 here. Servers unlikely and unsuitable for production or any other professional use anyway.
In some environments, the only reason SPARC boxes were bought was for their longer support lifetime (e.g. "minimum of 7 years support") than competing x86 models.
Since virtualising old installs is more difficult on Solaris for SPARC, I predict this will just accelerate migrations to x86, or for environments that need midrange servers, PPC or Itanium.
... as most users don't use vanilla upstream kernels. And, most distributors / distros have a supported release which provides Xen Dom0 support (including Red Hat).
I agree on Nokia's unnecessary device proliferation, however not:
Too many OSs, no clear dev schemes for third parties.
Since S^3 (all S^3 phones ship with Qt 4.7) shipped, the dev scheme for all smart phones (including S60v3/S60v5, S^3, Maemo 5 / N900, upcoming Maemo6 or Meego devices) was Qt and Qt Quick. Until the MS agreement, which removed almost all incentive to develop for Symbian.
In the meantime, Qt for Android is coming along nicely
iPhone and Android have been eating the aging Symbian for lunch and the Maemo/Meego replacements haven't been ready.
It seems that the Maemo replacements *are* ready, except for a tussle with Intel about whether they can be called "Meego compatible", "Meego ready" or otherwise use the Meego brand. Since Intel now employs two thirds of the Technical Steering Group which makes this decision (Nokia's representative moved to Intel after the Nokia MS announcement), and Intel isn't happy about the Nokia MS announcement, the fact that the Maemo 6 phones haven't been announced is due to the MS agreement, not that the phones aren't technically ready.
I figure the layoffs are about to begin and who do you think that will be, the Microsoft Phone developers or the Qt developers?
Well, the question is, why are layoffs coming? Because phones aren't selling, after Nokia announced "our current phones are dead, our new phones won't be ready for a while".
While a change was required, announcing a drastic change without having new products on the (3-month) horizon is foolish.
It seems many companies are keen to pick up the Qt developers
...And I will say that again -- Linux in a production environment does not belong in VM in the first place.
How do you add memory to a large Java application (requiring >12GB memory), which can't be load-balanced without having significant downtime. To take a server down, pull it out the rack, add 8 DIMMs, get the server back in the rack, and boot it will take at least 15 minutes, but more likely about 30.
Sure, if we had HA clusters everywhere, we could do this without virtualisation, but at the cost of running (roughly) twice the hardware.
We live-migrate the production VM to the spare (Xen) hypervisor, take the hypervisor that getting a memory upgrade down, add DIMMs, boot the box, and live-migrate the VM back, then dynamically increase the memory available to the VM. The last bit that is required is a restart of the application (granted, a minute or two).
Since we were having some failures of the application, and wanted to reduce the proportion of users affected, we at one stage migrated from having 4 production (clustered - where clustering wasn't improving availability) instances to 8 (standalone) instances (where only one application instance can be accommodated on a single OS image). Virtualisation allowed us to do that with less impact than it would have been without virtualisation. We have since added more instances without the cost and delay of procuring/installing/zoning more hardware.
I don't want to pay for their modem firmware updates and other network management traffic
1. Most likely, their ability to provide management of the modem is in the terms of service. Even if you saw a significant difference, how would you prove it was firmware updates, and even if you could, would you be able to get reimbursed for the traffic?
2. Most likely, the modem updates and network management traffic is a small fraction of your total bandwidth usage (e.g. 20MB/month).
Most ISPs (well, those that don't have complex "this service is free, this is not" products) do accounting based on the interface counters of the virtual interface on the border router. To be able to separate the firmware and network management traffic, they would need to do DPI instead. The cost of the equipment upgrades to do this would have to be passed on to the consumer. Most likely, that would cost more than what the firmware updates and management traffic are costing you.
Yes, being able to see (without incurring more bandwidth use) how much you have used is useful, but not for the purpose you wanted
... and printer/scanner resolution, and photo print sizes are about the only other ones. Of course, the Americans couldn't come up with increasing sizes of print media that have the same ratios, so depending on whether you're printing your digital photos at 4x6 or 5x7 or 8x10 you have to crop them differently
Does it control anything besides XBMC/media pl
From one of the articles:
"The Nyxboard Hybrid supports IR to function as a universal remote for your TV and includes an RF adapter for operating your home theater device without line-of-sight."
For a while I've been looking forward to getting this http://www.amazon.com/Portable-Wireless-Keyboard-Rechargeable-Notebooks/dp/B003UE52ME/ref=sr_1_2?s=electronics&ie=UTF8&qid=1298676916&sr=1-2
For half of the price,
When it launched just over a year ago, it was going for $90
you get a keyboard+touchpad combo in a very compact package, and it has a backlight which I admit to needing most of the time. It's even more stylish, so while I agree that a dedicated remote layout is a good idea, the price, and the availability of very good alternatives make me doubt it will have that much success.
You weren't clear on the subject of your last sentence, but I currently have a cheap (15 GBP) RF remote for XBMC, and 4 other IR remotes (amp, TV, DVD/HDD player/recorder, Satellite receiver). While I can use the amplifier's remote for most of the functions on the TV and DVD player, I still need at least the DVD player's remote for some features (switching between HDD and DVD etc.), the bluetooth-only solution won't help me, and neither will a Logitech Harmony (currently), but the Nyxboard Hybrid remote for XBMC etc. may just
We just need more details on how programmable the IR portion is.
Well, the story linked to has the summary:
(Reuters) - Microsoft Corp stepped up its rivalry with Google Inc with a formal complaint to EU antitrust regulators, claiming Google systematically thwarts Internet search competition.
No other part of the article make a statement about what the complaint is about. So, I fail to see how slashdotters are stupid. Maybe the author of the article was (intentionally?) misleading?
Forced is a bit strong. I'm running OS/X
If it is not on Apple hardware, you are in licence violation.
This is (IMHO) anti-competitive, I will not support Apple in any way while they have such restrictions.
Our own web applications are regularly tested on a wide variety of browsers (on Windows and Linux), but not Mac OS X, since we have almost no Apple hardware. Mac OS X users are unlucky, if there is some Mac-OS-specific bug, they will have to find it and report it
we recently were stunned by the very high cost of redhat support. Its more expensive than microsoft.
I suspect you were comparing licensing (MS) to support (RH), not support to support.
If every distro is doing the same thing, this is not going to be very good for the future of Linux.
If every distro were doing as much (proportionally) upstream work as Red hat, it would be very good for the future of Linux.
Engineers at every distro are going to waste a lot time trying to figure what other distros had been patching, which part of the code had been changed while a specific issue was fixed, etc.
But, they shouldn't be. They should be tracking *upstream*, putting their effort into *upstream*, instead of following other forks of the kernel.
Even though Linux distros are quite fragmented, but the current kernel development has been working quite well, because every distro is playing by the rule (more or less), which is quite transparent.
But, this has nothing to do with upstream kernel development, to which Red Hat is still contributing directly. This only has to do with development of Red Hat's Linux-based kernel (which is actually a fork).
If you're a Windows user - get Picasa.
If you're a Mac user - iPhoto works great.
If you're a Linux/BSD user - teach her about tar.
Don't you think Digikam (which can upload to Facebook, and download entire albums from Facebook) would be a more appropriate suggestion for Linux/BSD users?
"When it comes to humility, I'm the greatest." -- Bullwinkle Moose
