I still don't understand why data coming from the phone itself and data from a tethered device is treated differently. I can suck down 2 GB over the air using any number of pre-installed apps I'm not allowed to remove, but the second I want to tether my laptop to my phone to use a MB or two to check my email on a screen bigger than 3", I have to pay $20-$60 more a month with no pro-rated cost, or risk having my service cancelled. I just need to use it for a day or a week when I'm on vacation or off site. How is the data different because it's coming through the phone from another device than if it was coming from the phone itself?
It's no surprise with policies like this designed to deliberately make it difficult, annoying, and expensive to their customers that many would look to bypass their carriers mandatory second (or third) data plan required for tethering.
Do they even realize how much money they are loosing to pay-for-access 802.11 providers if they would just offer what customers want for a reasonable price and not feeling like we're being raped?
This à la carte sale of minutes, texts, and data is the biggest racket in history. How about this: $10/month per phone to cover your record keeping and base data prices to cover things like the phones tying up the network to ping pong the towers and servers all the time, then a reasonable per minute/MB/txt charge (i.e. 2-3 cents a minute/MB/txt regardless of it being sent or received) and everyone pays what they use. I'm ok with having a $20 bill one month and a $160 bill the next if that's what I used. I would much rather see that then the same $120 every month if I used 5 of everything vs 5000. This would also hopefully lead to more responsible use of phones in the first place. If base costs were reasonable to where a kid could pay for it with their allowance as long as they didn't go over board, then we probably wouldn't end up with quite so many people glued to the screen while "driving"/loosely aiming their vehicles down the roads.
If you're a corporation and you want to count on the bill being the same every month, than sure you can opt in to the current system we're using now so you have the same number of dollars every time it comes to pay the bill, but I really don't think many corporations would go for that kind of thing if it wasn't such a rip off to do it any other way.
Or because Verizon forces Bing to be the default search on all Android phones they sell, with no way to uninstall it or change it. (Without rooting the phone)
A little tidbit Adobe conveniently leaves out of their security announcements. It should read: "The sandbox will protect you, unless you're using the Pro version of our product that you paid a lot of money for. Mostly because we were too lazy and inept to include it, or have the security team release updates more than 4 times a year." Because everyone knows, the bad guys only work on release schedules.
Too bad OCZ's Vertex 3 line does nothing but blue screen and cause system freezes as well as not being detected by the BIOS on occasion. 9 firmware revisions since we bought them, installed in multiple computers, and still no fix. They won't be getting my business. Doesn't matter how fast it is if you can't rely on it.
I don't quite agree with that. It strikes me more as a defensive acquisition. Grab the licenser before someone else does.
There are other vectors to that end as well. The DEC/ARM StrongARM flavor, which evolved into Intel's Xscale, which was tossed by Intel to Marvell, presumably so they could focus on the Atom. Maybe.
Not really, they were originally trying to get MacOS to run on custom Alpha's with DEC's help, but the DEC engineers wouldn't do it.
64 bit, 200+ MHz CPU in the early 90's. Things would have been a lot different today if they weren't so pig headed. (Both Apple and DEC). I think this was even before Intel stole core logic from the Alpha for the Pentium II.
Yeah, then there was the AppleVision monitor series. I spent about $700 on the AppleVision 1710AV which arc'ed itself to death by blowing the Vertical Deflection board. Rather than fix the defective SONY tube or make the board more robust, they would just replace the deflection board ($300 for the part). It would then arc itself to death again, replace the board, arc itself to death again... HELLO?! IS ANYBODY HOME?! They say insanity is doing the same thing over and over and expecting different results...
I've also heard many stories of people who have had their iBook logic boards replaced (Both G3 and G4's) and had the problem re-occour. Now that the "insert-apple-product free repair program" has ended, everyone who bought said product is just SOL. That is BS. Say you have a unit that has had no problems until one week after the repair program ends like my friend did? I wish someone at Apple would wake up and actually fix these flaws instead of just replacing defective parts with defective parts.
A big feature like being able to make VoIP or VideoIP calls over a WiFi network instead of cell networks? Possibly the result of the Apple/Cisco iPhone trade name infringement? I would be very surprised to see that Cisco didn't have something to do with this.
You could create a GPLv3 fork of NetBSD though. That might revive NetBSD. You might just take the kernel though, letting distributions form around it. Debian already supports Hurd and FreeBSD kernels; they could do a NetBSD one as well.
They already started. There's a debian userland with NetBSD kernel and NetBSD userland with a debian kernel in the works. It hasn't been updated in a while but the project tree is still there: Debian NetBSD.
At most, the games only care about the number of screens, not the low level details of the hardware. Most of them just open whatever the main display is.
If you only have one logical screen, and a quad SLI card, then each GPU will be rendering a portion of the scene. With the Voodoo 4/5 it was broken up in alternating rows. I think the nVidia SLI divides the scene up by the number of GPUs.
I guess there is still a bit of the soul of 3Dfx alive in nVidia after all.
Apple also tried to switch to Alpha instead of PowerPC in the early 90's. Image where we would be today if the PowerMac 6100 was a 64-bit 21064 running at 150+ MHz in 1994.
Not to mention that RedHat is more of an investment banking company than a software company. The software is already written, they just butcher it and backport incompatible patches to the kernel and break their ABI every time they update something. It's a miracle that anyone actually gets anything to work that hasn't been specifically written for RedHat. (Mind you that RHEL AS 2.1 binaries don't work on RHEL 3 or RHEL 4 in most cases)
using 1310 buffer headers and 1310 cluster IO buffer headers
9AppleLynx is not compatible with its superclass, 14IOFireWireLink superclass changed?
\^[[33mFailed to load extension com.apple.driver.AppleLynx.
\^[[0mCouldn't alloc class "AppleLynx"
and don't appear to have firewire. Ioreg still shows the device node, but nothing attached itself to it.
Because it takes an incredibly long time to index 2000+ ID3 tags, add them to an array and sort it every time you hit play. With flash, hd and cpu speeds in the devices themselves taking off, this might not be such a big hit as it once was, but its still a lot of time. It'd be nice if they had the ability to rebuild the database on the device, say if it was corrupted or updated, but I don't want to sit and wait 30 seconds every time I hit play.
If they want to be "more onto the Mac" they could start by updating YIM more than once every two years. Even MSN messenger has them beat for the moment.
This argument is so beyond rediculous and obviously a troll. Whoever modded it up should have moderator privledges permantently revoked.
"If my machine cannot compile an operating system supposedly designed for it..." and it compiles fine on a cross compiler... there's a bug in GCC. NetBSD doesn't write GCC, so therefore the NetBSD cross compile framework is at fault. Ah I see, your logic makes perfect sense!
By your logic no current operating system could exist since the code would have to be initially cross compiled on some other architecture or written on the target from scratch in assembly. Good luck with that.
Some of the turbo pump parts spin at 37,000 RPM. For them to be spinning at that speed and then suddenly not pumping against anything could only be described as bad news. I imagine pump cavitation from low fluid or pressure levels would probably cause the pumps to explode or shear off their drive shafts.
The cryogenic fuels are pumped through the collar of the engine to keep it cool, so I don't really think that you could get it too cold. Too hot maybe, but IANASSMEE
Think a lapel microphone where there's a tiny mic clipped to your tie and a transmitter box in your pocket or some such connected by a wire to the microphone. Not a handheld wireless microphone.
Just to clarify, the NetBSD version is 1.6.1, not 2.6.1. No need for hype or version number creep. 2.0 is close to release, currently at RC4. At the rate RC's have been going by, mid November is probably a realistic release date.
Slashdot Mirror
Then what do you say to StrongARM?
http://www.netbsd.org/ports/pmax/ :)
I still don't understand why data coming from the phone itself and data from a tethered device is treated differently. I can suck down 2 GB over the air using any number of pre-installed apps I'm not allowed to remove, but the second I want to tether my laptop to my phone to use a MB or two to check my email on a screen bigger than 3", I have to pay $20-$60 more a month with no pro-rated cost, or risk having my service cancelled. I just need to use it for a day or a week when I'm on vacation or off site. How is the data different because it's coming through the phone from another device than if it was coming from the phone itself?
It's no surprise with policies like this designed to deliberately make it difficult, annoying, and expensive to their customers that many would look to bypass their carriers mandatory second (or third) data plan required for tethering.
Do they even realize how much money they are loosing to pay-for-access 802.11 providers if they would just offer what customers want for a reasonable price and not feeling like we're being raped?
This à la carte sale of minutes, texts, and data is the biggest racket in history. How about this: $10/month per phone to cover your record keeping and base data prices to cover things like the phones tying up the network to ping pong the towers and servers all the time, then a reasonable per minute/MB/txt charge (i.e. 2-3 cents a minute/MB/txt regardless of it being sent or received) and everyone pays what they use. I'm ok with having a $20 bill one month and a $160 bill the next if that's what I used. I would much rather see that then the same $120 every month if I used 5 of everything vs 5000. This would also hopefully lead to more responsible use of phones in the first place. If base costs were reasonable to where a kid could pay for it with their allowance as long as they didn't go over board, then we probably wouldn't end up with quite so many people glued to the screen while "driving"/loosely aiming their vehicles down the roads.
If you're a corporation and you want to count on the bill being the same every month, than sure you can opt in to the current system we're using now so you have the same number of dollars every time it comes to pay the bill, but I really don't think many corporations would go for that kind of thing if it wasn't such a rip off to do it any other way.
Or because Verizon forces Bing to be the default search on all Android phones they sell, with no way to uninstall it or change it. (Without rooting the phone)
A little tidbit Adobe conveniently leaves out of their security announcements. It should read: "The sandbox will protect you, unless you're using the Pro version of our product that you paid a lot of money for. Mostly because we were too lazy and inept to include it, or have the security team release updates more than 4 times a year." Because everyone knows, the bad guys only work on release schedules.
Too bad OCZ's Vertex 3 line does nothing but blue screen and cause system freezes as well as not being detected by the BIOS on occasion. 9 firmware revisions since we bought them, installed in multiple computers, and still no fix. They won't be getting my business. Doesn't matter how fast it is if you can't rely on it.
I don't quite agree with that. It strikes me more as a defensive acquisition. Grab the licenser before someone else does. There are other vectors to that end as well. The DEC/ARM StrongARM flavor, which evolved into Intel's Xscale, which was tossed by Intel to Marvell, presumably so they could focus on the Atom. Maybe.
Not really, they were originally trying to get MacOS to run on custom Alpha's with DEC's help, but the DEC engineers wouldn't do it. 64 bit, 200+ MHz CPU in the early 90's. Things would have been a lot different today if they weren't so pig headed. (Both Apple and DEC). I think this was even before Intel stole core logic from the Alpha for the Pentium II.
Quite right, and even before OpenDoc, it was OLE done correctly. Unlike Microsoft, whom even after all these years can't get it right.
Yeah, then there was the AppleVision monitor series. I spent about $700 on the AppleVision 1710AV which arc'ed itself to death by blowing the Vertical Deflection board. Rather than fix the defective SONY tube or make the board more robust, they would just replace the deflection board ($300 for the part). It would then arc itself to death again, replace the board, arc itself to death again... HELLO?! IS ANYBODY HOME?! They say insanity is doing the same thing over and over and expecting different results...
I've also heard many stories of people who have had their iBook logic boards replaced (Both G3 and G4's) and had the problem re-occour. Now that the "insert-apple-product free repair program" has ended, everyone who bought said product is just SOL. That is BS. Say you have a unit that has had no problems until one week after the repair program ends like my friend did? I wish someone at Apple would wake up and actually fix these flaws instead of just replacing defective parts with defective parts.
A big feature like being able to make VoIP or VideoIP calls over a WiFi network instead of cell networks? Possibly the result of the Apple/Cisco iPhone trade name infringement? I would be very surprised to see that Cisco didn't have something to do with this.
This from a guy who's historical predictions have always been spot on... and you'll never need more than 640k of RAM!
They already started. There's a debian userland with NetBSD kernel and NetBSD userland with a debian kernel in the works. It hasn't been updated in a while but the project tree is still there: Debian NetBSD.
And divide resources, users, time, and effort further?
At most, the games only care about the number of screens, not the low level details of the hardware. Most of them just open whatever the main display is.
If you only have one logical screen, and a quad SLI card, then each GPU will be rendering a portion of the scene. With the Voodoo 4/5 it was broken up in alternating rows. I think the nVidia SLI divides the scene up by the number of GPUs.
I guess there is still a bit of the soul of 3Dfx alive in nVidia after all.
Apple also tried to switch to Alpha instead of PowerPC in the early 90's. Image where we would be today if the PowerMac 6100 was a 64-bit 21064 running at 150+ MHz in 1994.
Not to mention that RedHat is more of an investment banking company than a software company. The software is already written, they just butcher it and backport incompatible patches to the kernel and break their ABI every time they update something. It's a miracle that anyone actually gets anything to work that hasn't been specifically written for RedHat. (Mind you that RHEL AS 2.1 binaries don't work on RHEL 3 or RHEL 4 in most cases)
using 1310 buffer headers and 1310 cluster IO buffer headers
9AppleLynx is not compatible with its superclass, 14IOFireWireLink superclass changed?
\^[[33mFailed to load extension com.apple.driver.AppleLynx.
\^[[0mCouldn't alloc class "AppleLynx"
and don't appear to have firewire. Ioreg still shows the device node, but nothing attached itself to it.
Because it takes an incredibly long time to index 2000+ ID3 tags, add them to an array and sort it every time you hit play. With flash, hd and cpu speeds in the devices themselves taking off, this might not be such a big hit as it once was, but its still a lot of time. It'd be nice if they had the ability to rebuild the database on the device, say if it was corrupted or updated, but I don't want to sit and wait 30 seconds every time I hit play.
If they want to be "more onto the Mac" they could start by updating YIM more than once every two years. Even MSN messenger has them beat for the moment.
"If my machine cannot compile an operating system supposedly designed for it..." and it compiles fine on a cross compiler... there's a bug in GCC. NetBSD doesn't write GCC, so therefore the NetBSD cross compile framework is at fault. Ah I see, your logic makes perfect sense!
By your logic no current operating system could exist since the code would have to be initially cross compiled on some other architecture or written on the target from scratch in assembly. Good luck with that.
The cryogenic fuels are pumped through the collar of the engine to keep it cool, so I don't really think that you could get it too cold. Too hot maybe, but IANASSMEE
http://www.boeing.com/defense-space/space/propul/S SMEamaz.html
http://www.optipoint.com/far/turbo.htm
Think a lapel microphone where there's a tiny mic clipped to your tie and a transmitter box in your pocket or some such connected by a wire to the microphone. Not a handheld wireless microphone.
Where's the option to mod the submitter down? This is quite possibly the most inaccurate crap I've ever seen. On the front page no less.
Just to clarify, the NetBSD version is 1.6.1, not 2.6.1. No need for hype or version number creep. 2.0 is close to release, currently at RC4. At the rate RC's have been going by, mid November is probably a realistic release date.