You were running on 32 bit? You will hit the same limit whether you have 256MB or 16GB then.
Sorry, what? You are saying that a 32-bit machine with no swap and 256MB or RAM would allow 3GB of memory to malloc'ed? I don't think so. My point was that with a total of 2GB of memory in the system (2GB RAM and zero swap), a program can malloc 3GB.
That's not what the OOM killer is for. Linux will allow over-commitment of memory (programs can malloc more memory (RAM plus swap) than is available). If all the malloc'ed memory is actually used, this can lead to more memory having been allocated than is available. This is when the OOM killer starts work killing tasks.
This behavior can be modified by changing the values in/proc/sys/vm/overcommit_ratio and/proc/sys/vm/overcommit_memory.
As an experiment, I wrote a little progrem that malloc'ed 200MB chunks of memory. I ran this on a Linux box with 2GB of RAM and all the SWAP disabled. The program could malloc 3GB of RAM before the allocation requests failed.
And make the pricing transparent. No more adding in fees, especially fees that a carrier cannot tell you how much they will be before selling the service, but magically, can calculate them after you have signed on the dotted line.
I am just waiting for a carrier to offer a 1c/month plan (plus fees and taxes), where the fees and taxes are somewhere between $50 and $100/month.
Well, I have. I ordered an item that was to be delivered via UPS at about the time my company moved office. The item was addressed to the new office. The UPS driver, went to the old address, saw that we have moved and took the item back to the UPS depot. I called UPS to tell them that if they could just, you know, deliver the package to the address that was on the package, all would be good. Instead, they delivered it to the address that my company had used a few years earlier.What's so hard about reading the address on a package and delivering a package there?
I am tired of trucking my way down to the local UPS distribution center to try to get my packages.
Try living in Italy. There, the mail carriers will tear a corner of your package so you have to go to the post office to collect it and ensure it isn't damaged, all while curious postal workers are looking over your shoulder.
Think about what Microsoft is saying here. All MS is saying is that the sample was too small.
What Microsft is saying is that an unknown number of Microsoft customers was hit with some kind of zero-day attack. It doen't equate to a 100% success rate in real life, it says nothing about MSE's success rate in catching zero day attacks. All it says is that the sample size of zero-day attacks was too small for meaningful analysis.
This is probably just an example of a clueless PHB who doesn't realize the souce of the winapp2.ini files.
Perhaps a polite letter asking how you are violating their TOS, pointing out the source of the winapp2.ini files? Also, you probably never accepted their TOS did you?
But right now the market for hard disks is between two giants (Western Digital and Seagate) and one tiny little division of Toshiba that doesn't make much if any 3.5" models
And SSDs. The availability of drop-in replacements for spinning-disk hard drives alters the market dynamics. SSDs are a lot more expensive, but they also offer some big benefits: lower power, faster access. The availability of SSDs is likely to impact the price of spinning platters much more than the 2-supplier oligopoly.
Many years ago, I owned a car for which I bought a new oil filter from the dealer. The filter came with a notice that I had to check the length of the spigot, and, if it was too long, I should shorten it. The spigot on my car was indeed too long. This was not a recall item -- no assistance was provided by the manufacturer in fixing the length of the spigot. Apparently the manufacturer felt free to change the specifications of my car after selling it. I complained about this, but to no avail.
However, after some investigation, I found that the dealers had a similar notice, but the maximum allowed length of the spigot was a little longer, and the spigot on my car was not too long by this specification.
that you're an idiot because it is exactly the same as saying Android 2.x and 3.x were so bad that Google abandoned
Well, perhaps I am an idiot for arguing with an AC troll, but.....
Seriously, you think that the disconnect between Windows phone 7 to Windows Phone 8 is the same as Google upgrading Android from 2.x to 3.x and onwards. Seriously?
Then, there is the app store. The app store lags other ecosystems
nope, not ovi
And you call me an idiot? My point was about the Windows Phone app store, not ovi. Windows Phones can't use ovi.
Maemo failed, MeeGo failed, and there is no reason whatsoever that Tizen would have any more success.
Neither Maemo nor MeeGo has been significantly tested in the market and your comment about Tizen is pure speculation.
the only difference between windows phone and all the other failed oses
... is that Windows Phone is a proven failure. (FTFY)
Well please tell me how it would have been different with any other OS, they all have the same problem
No, they don't. Windows Phone 7.x was so bad that Microsoft abandoned it. What does that tell you? For specifics, try getting an incoming call on Skype (under Win Phone 7.x) without having the Skype app open and taking up the full screen. Secondly, the fact that Skype is owned by Microsoft and is pre-installed on WP8 devices is a big barrier to carriers promoting the phones. Then, there is the app store. The app store lags other ecosystems, despite Microsoft offering a phone OS for how long?
Perhaps the real objective difference is that Windows Phone has failed in the past, while the others are untried. Oh, and let's not forget the licensing cost.
But its better to have a company with the means to stick it out and invest in the product even through a lengthy period of unprofitability, because that's what you need to do if you're entering an established market without a disruptive product
Translation: a company prepared to use monopoly rents to establish a presence in other markets. Exactly what anti-trust legislation is supposed to prevent.
This is Tomi Ahonen. Laying into Nokia and Windows Phone is his USP.
Yes, it is Tomi Ahonen and he has been very critical of Nokia's adoption of Windows Phone, but please tell me where he is wrong. Otherwise your posting is just argumentum ad-hominem.
Just to remind you, he predicted the insignificant market share Nokia has achieved with Windows phone, while every other analyst predicted much higher sales.
It's not the job of government to protect broken business models. In this case AT&T should either charge more for the phone or their ETF, or (and I suspect that this is the real answer), the "unlocked" price for the phone is artificially inflated.
If they contributed, they contributed. Does it matter that they did so because there is a demand for their VMs to run Linux, rather than out of the goodness of their hearts?
Actually, the why may not matter, but the fact is that the code they contributed did not really improve Linux, it just allowed Linux to run under Microsoft's closed-source Hyper-V. The code was aimed at improving Microsoft's own platform, not Linux.
Slashdot Mirror
Sorry, what? You are saying that a 32-bit machine with no swap and 256MB or RAM would allow 3GB of memory to malloc'ed? I don't think so. My point was that with a total of 2GB of memory in the system (2GB RAM and zero swap), a program can malloc 3GB.
That's not what the OOM killer is for. Linux will allow over-commitment of memory (programs can malloc more memory (RAM plus swap) than is available). If all the malloc'ed memory is actually used, this can lead to more memory having been allocated than is available. This is when the OOM killer starts work killing tasks.
This behavior can be modified by changing the values in /proc/sys/vm/overcommit_ratio and /proc/sys/vm/overcommit_memory.
As an experiment, I wrote a little progrem that malloc'ed 200MB chunks of memory. I ran this on a Linux box with 2GB of RAM and all the SWAP disabled. The program could malloc 3GB of RAM before the allocation requests failed.
And make the pricing transparent. No more adding in fees, especially fees that a carrier cannot tell you how much they will be before selling the service, but magically, can calculate them after you have signed on the dotted line.
I am just waiting for a carrier to offer a 1c/month plan (plus fees and taxes), where the fees and taxes are somewhere between $50 and $100/month.
I assume that would be a McLaren F1, cost 0.5M pounds when new, now worth significantly more.
According to TFA (I know, WTF, I actually read TFA?), a reboot does not fix this problem, but a power cycle does.
Really?
Well, I have. I ordered an item that was to be delivered via UPS at about the time my company moved office. The item was addressed to the new office. The UPS driver, went to the old address, saw that we have moved and took the item back to the UPS depot. I called UPS to tell them that if they could just, you know, deliver the package to the address that was on the package, all would be good. Instead, they delivered it to the address that my company had used a few years earlier.What's so hard about reading the address on a package and delivering a package there?
Try living in Italy. There, the mail carriers will tear a corner of your package so you have to go to the post office to collect it and ensure it isn't damaged, all while curious postal workers are looking over your shoulder.
Of course they still have to pander to shareholders. Just different shareholders.
Think about what Microsoft is saying here. All MS is saying is that the sample was too small.
What Microsft is saying is that an unknown number of Microsoft customers was hit with some kind of zero-day attack. It doen't equate to a 100% success rate in real life, it says nothing about MSE's success rate in catching zero day attacks. All it says is that the sample size of zero-day attacks was too small for meaningful analysis.
There are strong connections between the investors in Silver Lake Partners and Microsoft.
This is probably just an example of a clueless PHB who doesn't realize the souce of the winapp2.ini files.
Perhaps a polite letter asking how you are violating their TOS, pointing out the source of the winapp2.ini files? Also, you probably never accepted their TOS did you?
And SSDs. The availability of drop-in replacements for spinning-disk hard drives alters the market dynamics. SSDs are a lot more expensive, but they also offer some big benefits: lower power, faster access. The availability of SSDs is likely to impact the price of spinning platters much more than the 2-supplier oligopoly.
Many years ago, I owned a car for which I bought a new oil filter from the dealer. The filter came with a notice that I had to check the length of the spigot, and, if it was too long, I should shorten it. The spigot on my car was indeed too long. This was not a recall item -- no assistance was provided by the manufacturer in fixing the length of the spigot. Apparently the manufacturer felt free to change the specifications of my car after selling it. I complained about this, but to no avail. However, after some investigation, I found that the dealers had a similar notice, but the maximum allowed length of the spigot was a little longer, and the spigot on my car was not too long by this specification.
I saw an advert for BART police the other day: Base pay $127k, plus benefits, including fully paid retirement.
Well, perhaps I am an idiot for arguing with an AC troll, but.....
Seriously, you think that the disconnect between Windows phone 7 to Windows Phone 8 is the same as Google upgrading Android from 2.x to 3.x and onwards. Seriously?
And you call me an idiot? My point was about the Windows Phone app store, not ovi. Windows Phones can't use ovi.
Neither Maemo nor MeeGo has been significantly tested in the market and your comment about Tizen is pure speculation.
A couple of individual markets where the market share is higher does not make his prediction for worldwide market share wrong.
No, they don't. Windows Phone 7.x was so bad that Microsoft abandoned it. What does that tell you? For specifics, try getting an incoming call on Skype (under Win Phone 7.x) without having the Skype app open and taking up the full screen. Secondly, the fact that Skype is owned by Microsoft and is pre-installed on WP8 devices is a big barrier to carriers promoting the phones. Then, there is the app store. The app store lags other ecosystems, despite Microsoft offering a phone OS for how long?
Perhaps the real objective difference is that Windows Phone has failed in the past, while the others are untried. Oh, and let's not forget the licensing cost.
Translation: a company prepared to use monopoly rents to establish a presence in other markets. Exactly what anti-trust legislation is supposed to prevent.
Yes, it is Tomi Ahonen and he has been very critical of Nokia's adoption of Windows Phone, but please tell me where he is wrong. Otherwise your posting is just argumentum ad-hominem.
Just to remind you, he predicted the insignificant market share Nokia has achieved with Windows phone, while every other analyst predicted much higher sales.
Did the submitter read this blog posting from an analyst first?
It's not the job of government to protect broken business models. In this case AT&T should either charge more for the phone or their ETF, or (and I suspect that this is the real answer), the "unlocked" price for the phone is artificially inflated.
"Ah, Your Majesty, there is no second."
The first race was actually for the "R.Y.S. £100 Cup", subsequently re-named "America's cup"
For a complete discussion, just read this story
Actually, the why may not matter, but the fact is that the code they contributed did not really improve Linux, it just allowed Linux to run under Microsoft's closed-source Hyper-V. The code was aimed at improving Microsoft's own platform, not Linux.
What, did anyone think that copyright was intended to protect anyone except the rich and powerful?
Hollywood inaccurate...... film at 11.
Wait, what?
But seriously, when did anyone expect historical accuracy from Hollywood. Another example that outraged many Brits