In case you didn't already know, Newark element14 is a USA vendor owned by Premier Farnel and based in Indiana. This so-called "news" story is a waste of everyone's time.
What, Newark element14 is not easy enough to order from? Does it really matter? My two Raspberry Pi units arrived almost instantly from Newark element14 the moment they became available.
There were severe satellite gaps in the 1980s. GOES East had to be moved to a more central location to observe both coasts when GOES West failed and its replacement suffered a launch failure.
I used to get excited by long uptimes. People who were obsessed by this concept started this silly web site called uptimes.org. After a while of blatantly fraudulent uptime claims and other silliness it was shut down.
Nobody cares anymore about computers that haven't been turned off for ten years. In my own house I have experienced 400+ days of uptimes, which is an impressive feat, but nobody cares, and the more you think about it, nobody should care.
Yes, nobody should care about long uptimes. The reliability of a system is shown by how perfectly it recovers from a system failure--not on the reliance of a power supply that keeps it from having a system failure. That's a philosophy that has served me and my systems well for more than twenty years.
Still, when I shut down the servers in my house with 400+ day uptimes, I have to shed a tear and a quiet *sniff*. Sigh.
A trick that I use in today's office cubicles worked fine back in college. Just get one or two cheap desk fans. They are always too noisy for the airflow they deliver, but the point is that they provide enough white noise and pink noise that makes life bearable.
If you can't sleep with white and pink noise, just give yourself one or two nights to get used to it. You will get used to it.
I assure you that the x86 Acer C7 Chromebook was indeed using Silverlight to run Netflix until this change happened this week. I even right-clicked on the Netflix video and it definitely indicated it was a Silverlight plugin on my Chromebook.
Of course, this week, it's claiming the video is an HTML object, so it's hard to prove this, but it was definitely Silverlight on x86 Chromebooks last week.
I did the "right-click" on this x86 Chromebook when it was running a Netflix movie and it did indicate it was using Silverlight. It was using the Pepper plugin API which is specific to the Google Chrome browser and, also, is/was available on the x86 version of the Google Chromebook.
It is absolutely *not* Miguel de Icaza's Moonlight. It is the real Microsoft Silverlight on x86 in Google Chrome. In additionk, it was definitely running on the Google Acer C7 Chromebook until some time late last week.
Wow, I really thought the local copy was protected somehow. Perhaps you should talk to the Google developers about this, especially since the Chromebook "guest" login is promoted as a feature.
I had a fair amount of skepticism about the Chromebook, but I'm a fan of the old-school "light" and "thin client" platforms which continue to fail in the marketplace. When I recently obtained my Chromebook at a substantially lower price than the totally equivalent Windows laptop, I was convinced it was a great deal for what it's designed for. Of course, to use it, I had to submit to the "Google is everything" idea for those tasks I use the Chromebook for, which, I have to say, (for these tasks only), I am not an opponent of.
Wow, that is nice. On my x86 Acer C7 Chromebook, which was using Silverlight just last week, is stellar using HTML5. I was wondering why the video looks and "feels" different.
Starting now, all the operating system distributions should turn off PasswordAuthentication by default. This really is a non-problem.
As for denial-of-service "script kiddie" attacks, SSH already has built-in rate-limiting in the form of the MaxAuthTries, MaxSessions, and MaxStartups, and even LoginGraceTime and, of course, UseDNS=no.
Besides these two easy and readily available fixes that have been in place for years, why are you logging every visit to SSH on your system, anyway? That's just asking for a DoS attack that fills your log directory or the log directory on your designated loghost. That is, unless you're smart enough to keep a bastion host's log directory in its own volume.
Unless, of course, this is the first you've heard of a bastion host.
These old beasts are still, watt per watt, more efficient than the x86 architecture. The local cache per processor, along with the highly optimized RISC pipeline, can't be matched.
It's a shame that we are saddled with legacy CISC-to-RISC just-in-time conversions and bus contention, even with the Xeon and Opteron's huge local caches. The SPARC was just better.
This concept of "Net Neutrality" is not sustainable. If I run an ISP and over 85% of my traffic is going to Google or Netflix or Amazon AWS (which is also Netflix) then, from my point of view, someone needs to pay for it. I'm not sure it's my subscribers who should pay since it will cost them too much money in subscripton usage fees.
It's undeniable. If my ISP traffic is consumed by so much traffic by a such-and-such upstream vendor, shouldn't that such-and-such upstream vendor share in the cost of providing that traffic? I think so, especially since such-and-such upstream vendor is collecting subscription fees from my subscriber AND collecting advertisement royalties for that traffic.
I dare say that the current model is not sustainable. The coming years will experience a fascinating sea-change in the so-called "net neutrality" model.
Having used the Ubuntu LTS releases, I cannot disagree with this sentiment. On most systems I have returned to Red Hat Enterprise, or, more specifically, the CentOS derivatives, for quality releases. In my experience, the Ubuntu LTS releases aren't tested to the high standard that the Red Hat Enterprise releases are, but I expected that, to be honest, and wasn't surprised at all.
I'm a big fan of long-term releases, only because I may be one of those individuals who might be responsible for systems that do not have access to the internet in order to support the "rolling release" model.
It's nice to be able to have a stable, known-good server installation on several isolated networks that just need an occasional update of dpkgs and completely expect it to work fine after it's been restarted. I don't think the same is expected in a rolling release model.
The idea that a rolling release maintains binary compatibility is, so far, been proven false. In our world, long-term releases make sense.
Burgers are never flipped at McDonalds or Burger King. McDonalds uses a dual-surface grill, contacting the beef from top and bottom. Burger King uses a broiler with flames on the top and bottom.
No flipping burgers. Note this for future reference.
This company is one of a long line of owners of the "Atari" name. Just like Activision, this has nothing to do with the original company aside from the name and some licensed titles from the original company.
Slashdot Mirror
In case you didn't already know, Newark element14 is a USA vendor owned by Premier Farnel and based in Indiana. This so-called "news" story is a waste of everyone's time.
Sheesh.
What, Newark element14 is not easy enough to order from? Does it really matter? My two Raspberry Pi units arrived almost instantly from Newark element14 the moment they became available.
Why is this news? Just cut it out, already.
There were severe satellite gaps in the 1980s. GOES East had to be moved to a more central location to observe both coasts when GOES West failed and its replacement suffered a launch failure.
We'll get through this.
My Samsung Galaxy S3 and iPhone hang up when I slam them down on the table.
The Galaxy also mutes when I cover the screen with my hand.
I'm not sure what all the fuss is about.
I used to get excited by long uptimes. People who were obsessed by this concept started this silly web site called uptimes.org. After a while of blatantly fraudulent uptime claims and other silliness it was shut down.
Nobody cares anymore about computers that haven't been turned off for ten years. In my own house I have experienced 400+ days of uptimes, which is an impressive feat, but nobody cares, and the more you think about it, nobody should care.
Yes, nobody should care about long uptimes. The reliability of a system is shown by how perfectly it recovers from a system failure--not on the reliance of a power supply that keeps it from having a system failure. That's a philosophy that has served me and my systems well for more than twenty years.
Still, when I shut down the servers in my house with 400+ day uptimes, I have to shed a tear and a quiet *sniff*. Sigh.
A trick that I use in today's office cubicles worked fine back in college. Just get one or two cheap desk fans. They are always too noisy for the airflow they deliver, but the point is that they provide enough white noise and pink noise that makes life bearable.
If you can't sleep with white and pink noise, just give yourself one or two nights to get used to it. You will get used to it.
I assure you that the x86 Acer C7 Chromebook was indeed using Silverlight to run Netflix until this change happened this week. I even right-clicked on the Netflix video and it definitely indicated it was a Silverlight plugin on my Chromebook.
Of course, this week, it's claiming the video is an HTML object, so it's hard to prove this, but it was definitely Silverlight on x86 Chromebooks last week.
I did the "right-click" on this x86 Chromebook when it was running a Netflix movie and it did indicate it was using Silverlight. It was using the Pepper plugin API which is specific to the Google Chrome browser and, also, is/was available on the x86 version of the Google Chromebook.
It is absolutely *not* Miguel de Icaza's Moonlight. It is the real Microsoft Silverlight on x86 in Google Chrome. In additionk, it was definitely running on the Google Acer C7 Chromebook until some time late last week.
Sorry to burst your bubble.
Wow, I really thought the local copy was protected somehow. Perhaps you should talk to the Google developers about this, especially since the Chromebook "guest" login is promoted as a feature.
I had a fair amount of skepticism about the Chromebook, but I'm a fan of the old-school "light" and "thin client" platforms which continue to fail in the marketplace. When I recently obtained my Chromebook at a substantially lower price than the totally equivalent Windows laptop, I was convinced it was a great deal for what it's designed for. Of course, to use it, I had to submit to the "Google is everything" idea for those tasks I use the Chromebook for, which, I have to say, (for these tasks only), I am not an opponent of.
Am I incorrect in assuming that the local copy of your synchronized data is encrypted on a Chromebook?
At these prices and levels of effort, why not just get a Chromebook, anyway?
Wow, that is nice. On my x86 Acer C7 Chromebook, which was using Silverlight just last week, is stellar using HTML5. I was wondering why the video looks and "feels" different.
I'm waiting for the DRM toilet video in 5...4...3...2...
Starting now, all the operating system distributions should turn off PasswordAuthentication by default. This really is a non-problem.
As for denial-of-service "script kiddie" attacks, SSH already has built-in rate-limiting in the form of the MaxAuthTries, MaxSessions, and MaxStartups, and even LoginGraceTime and, of course, UseDNS=no.
Besides these two easy and readily available fixes that have been in place for years, why are you logging every visit to SSH on your system, anyway? That's just asking for a DoS attack that fills your log directory or the log directory on your designated loghost. That is, unless you're smart enough to keep a bastion host's log directory in its own volume.
Unless, of course, this is the first you've heard of a bastion host.
Lua is all over the Logitech Squeezebox by SlimDevices. It's Tcl for the new generation.
Looks like I got my RPi model B just in time!
More memory, more better.
That's a good point.
Even dollar-for-dollar it was never better.
These old beasts are still, watt per watt, more efficient than the x86 architecture. The local cache per processor, along with the highly optimized RISC pipeline, can't be matched.
It's a shame that we are saddled with legacy CISC-to-RISC just-in-time conversions and bus contention, even with the Xeon and Opteron's huge local caches. The SPARC was just better.
This concept of "Net Neutrality" is not sustainable. If I run an ISP and over 85% of my traffic is going to Google or Netflix or Amazon AWS (which is also Netflix) then, from my point of view, someone needs to pay for it. I'm not sure it's my subscribers who should pay since it will cost them too much money in subscripton usage fees.
It's undeniable. If my ISP traffic is consumed by so much traffic by a such-and-such upstream vendor, shouldn't that such-and-such upstream vendor share in the cost of providing that traffic? I think so, especially since such-and-such upstream vendor is collecting subscription fees from my subscriber AND collecting advertisement royalties for that traffic.
I dare say that the current model is not sustainable. The coming years will experience a fascinating sea-change in the so-called "net neutrality" model.
Having used the Ubuntu LTS releases, I cannot disagree with this sentiment. On most systems I have returned to Red Hat Enterprise, or, more specifically, the CentOS derivatives, for quality releases. In my experience, the Ubuntu LTS releases aren't tested to the high standard that the Red Hat Enterprise releases are, but I expected that, to be honest, and wasn't surprised at all.
I'm a big fan of long-term releases, only because I may be one of those individuals who might be responsible for systems that do not have access to the internet in order to support the "rolling release" model.
It's nice to be able to have a stable, known-good server installation on several isolated networks that just need an occasional update of dpkgs and completely expect it to work fine after it's been restarted. I don't think the same is expected in a rolling release model.
The idea that a rolling release maintains binary compatibility is, so far, been proven false. In our world, long-term releases make sense.
Burgers are never flipped at McDonalds or Burger King. McDonalds uses a dual-surface grill, contacting the beef from top and bottom. Burger King uses a broiler with flames on the top and bottom.
No flipping burgers. Note this for future reference.
This company is one of a long line of owners of the "Atari" name. Just like Activision, this has nothing to do with the original company aside from the name and some licensed titles from the original company.
Sure, they say they're sending to 100+ Million users, but only a tiny fraction of those are actual people. They could have saved a lot of bandwidth.