Another +1 for Tomato here. WRT54GL, nice and stable.
Set outbound bandwidth limit a little bit below your true uplink speed. Put voip traffic at highest priority, FPS/latency-sensitive games and the like on high, regular interactive stuff on normal (e.g. web surfing) and bulk stuff on low.
Agreed. I think Google did the "release early release often" on purpose. They are new to the OS/API platform building game and probably wanted as much community feedback as possible before v1.0.
The thing is, on the scale we are talking about gravity is actually a weak force compared to the forces that keep atoms apart and most of the space is empty. So unless you have unusual conditions like very high pressure/temperature the same forces that keep nuclear fusion from happening will keep the hole from eating matter.
they suck everything in including light Only if you get inside the event horizon. If you stay outside it, a black hole behaves pretty much like any other object of the same mass.
Say for example that the sun was replaced with a black hole of the same mass. Earth would continue in its orbit just like it does today, because the gravity force of the black hole would be the same. It would get cold and dark, though. The event horizon of a sun-mass black hole is at 3km.
What then about our theoretical mini black hole? Well, lower mass translates to smaller event horizon - an earth-mass black hole would be at 9mm. A poster above did the math for a 5-neutron black hole - 4x10^-54 metres; for comparison a helium atom is 3x10^-11 metres. So even if mini black holes exist and are stable, it is not like one of them will instantly eat the earth.
Rugged flash drives are only "like 1% of the market" because people for some reason seem to be unwilling to spend a few $ more.
Out of curiosity, what is the price difference between the cheapest x GB stick and a similar size rugged drive like a Corsair Flash Voyager? In my neck of the wood it is literally just a few $.
We lost the original meaning of hacker due to journalists failing to understand (or deliberately ignoring) the difference between hacker and cracker.
I'll be damned if I let the iCrowd do the same to "bricked". A device that can be recovered is not bricked! Oh, and don't get me started on "jailbreak".
As for Verizon "opening up" their network, that's a funny variety of newspeak. It is still more closed than any GSM carrier. Verizon's variety of "open" means that they are publishing specs and setting up a certification lab so that 3rd party manufacturers can make devices compatible with their network. You can't use any old CDMA phone and use it on Verizon, it has to be Verizon certified.
Compare to GSM, where you can take any unlocked phone, put in a sim-card from any GSM carrier you like and off you go. There is no need for the phone to be $cell_carrier_x certified, it is sufficient that the phone complies with the GSM spec.
The CDMA family is: CDMA (2G) - CDMA2000 (2.5G) - EV-DO (3G) - UMB (4G)
The GSM family is: GSM (2G) - EDGE/GPRS (2.5G) - UMTS (3G) - HSDPA/HSUPA (3.5G) - LTE (4G)
I`d say the router is worthy of flame no matter what OS it is running. A router must be stable, it should not crash even if you send complete random gibberish at it.
If it turns out that XPSP3 is sending broken UPnP traffic to the router, then MS is a valid flame target for not following the spec properly. That does however not absolve the router.
16GB thumb drives don't exist... the biggest I've seen is 4GB... Where you live, middle of Amazon rainforest? 16GB thumbdrives been round pretty long time. 32GB is the largest that is currently available in the retail channel. Even eensy teensy size of your fingernail microSDHC cards reached 8GB a while ago.
As for SSD having higher cost; more complicated interface logic (pci, sata/pata, etc), they tend to use SLC instead of MLC flash, they tend to be in a parallel or interleaved organization, some have proper on-board logic for wear leveling (compared to the "smartmedia" format that thumbdrives tend to use), etc..
Current Atom is not in any way suitable for phones. It pulls too many watts, especially at idle, and it needs a northbridge chip which is an absolute pig when it comes to power efficiency. If you read marketing materials you might come off with the impression that Atom is the best thing since sliced bread, but if you look at the actual numbers you will see that it uses way too much power for this kind of use.
Atom might, perhaps, show up in a few phones when Moorestown comes out sometime in 2009. Moorestown is a SOC, containing an Atom cpu core plus most of the other stuff you would need on a phone in a single chip. It is however expected to still need more watts than a comparable ARM-based smartphone SOC.
Hence why I said that "Atom doesn't make much sense except on devices where X86 compatibility is a plus".
The Atom is geared towards cell phones, smartphones, and PDAs. You kid, right? Atom is not for cell phones. At idle the Atom draws 15-20 times more electricity than what you want on a phone.
Not to mention that Atom is a CPU only, you have to add a north/southbridge to get something comparable to a current ARM cell-phone SOC. To give an example - the TI Omap2420 contains everything plus the kitchen sink -accelerated 2d/3d, 3G stuff, SD-card controller, USB interface, IRDA interface, memory controller, display controller (including TV-out)...
Currently, the Atom doesn't make much sense except on devices where X86 compatibility is a plus. In other words, subnotebooks.
4) Any S60 (i.e. Nokia smartphone) device plus putty. If the keyboard is too small, use a bluetooth wireless keyboard.
5) Internet tablet/surfpad. Most of them (like Nokia 770/N800/N810) can connect to a phone over bluetooth to get you online when only cell is available.
The question was HTF do I get a decent smartphone with AT&T/Cingular?
AT&T/Cingular use GSM. Empaler's answer is correct.
I love this country no one can agree on anything so nothing ever really gets done properly Not really, at least not with regards to cell carrier control of handsets. The problem is that the FCC punted on Carterphone regulation.
If he has line of sight, I'd say to get two 802.11G access points that can be configured to bridge mode and use external antennas.
Although at 500 Meters your getting near the limit Try five times the limit for twisted pair. 10/100/1000BaseT is specced to 100 meters. It might work, but you're running way outside spec.
10Base2 coax "thinnet" is 185 meters.
10Base5 coax "thicknet" is 500 meters.
If he wants to drag some cable I'd recommend running some cat3 and get a couple vdsl bridges.
The out-of-box hplj4 (both in win and lin) usually does the job if you need a generic ps driver.
Has saved me several times when I just needed to get basic printing up and running and I'm in a "can't find native driver"/"native driver is umpteen megabytes and I'm on slow net" situation.
So wouldn't that cause games to trickle down to Linux via people reverse engineering and other methods, as well? Short answer: No.
Long answer: The 3D API on both Mac and Linux is OpenGL, porting would be easier than it would be if it was originally written for DirectX/Direct3D. However, OSX has a bunch of Mac-only APIs - there is no rule that says that porting from those to Linux equivalents will be any easier than porting from Win32.
"They call it pollution, we call it life?"
Another +1 for Tomato here. WRT54GL, nice and stable.
Set outbound bandwidth limit a little bit below your true uplink speed. Put voip traffic at highest priority, FPS/latency-sensitive games and the like on high, regular interactive stuff on normal (e.g. web surfing) and bulk stuff on low.
Great. So we now have confirmation that the bastardization of the term "bricked" has even permeated AT&T. Damn the appleheads.
Agreed. I think Google did the "release early release often" on purpose. They are new to the OS/API platform building game and probably wanted as much community feedback as possible before v1.0.
Yes, it will grow if it eats something.
The thing is, on the scale we are talking about gravity is actually a weak force compared to the forces that keep atoms apart and most of the space is empty. So unless you have unusual conditions like very high pressure/temperature the same forces that keep nuclear fusion from happening will keep the hole from eating matter.
Say for example that the sun was replaced with a black hole of the same mass. Earth would continue in its orbit just like it does today, because the gravity force of the black hole would be the same. It would get cold and dark, though. The event horizon of a sun-mass black hole is at 3km.
What then about our theoretical mini black hole? Well, lower mass translates to smaller event horizon - an earth-mass black hole would be at 9mm. A poster above did the math for a 5-neutron black hole - 4x10^-54 metres; for comparison a helium atom is 3x10^-11 metres. So even if mini black holes exist and are stable, it is not like one of them will instantly eat the earth.
You were one of those that bought an iPhone before September '07, right?
I should have qualified my use of the word "cheat".
As a way to improve performance it is certainly a valid technology.
The "cheat" part is more in the way of marketing; pen drives are typically sold as "x MB/s read/write" while HDs are sold as "x RPM y MB cache".
Rugged flash drives are only "like 1% of the market" because people for some reason seem to be unwilling to spend a few $ more.
Out of curiosity, what is the price difference between the cheapest x GB stick and a similar size rugged drive like a Corsair Flash Voyager? In my neck of the wood it is literally just a few $.
Because SLC is both faster and more durable than MLC?
almost all bricked phones were later recovered
We lost the original meaning of hacker due to journalists failing to understand (or deliberately ignoring) the difference between hacker and cracker.
I'll be damned if I let the iCrowd do the same to "bricked". A device that can be recovered is not bricked! Oh, and don't get me started on "jailbreak".
EV-DO is a 3G flavor of CDMA, so no luck there.
As for Verizon "opening up" their network, that's a funny variety of newspeak. It is still more closed than any GSM carrier. Verizon's variety of "open" means that they are publishing specs and setting up a certification lab so that 3rd party manufacturers can make devices compatible with their network. You can't use any old CDMA phone and use it on Verizon, it has to be Verizon certified.
Compare to GSM, where you can take any unlocked phone, put in a sim-card from any GSM carrier you like and off you go. There is no need for the phone to be $cell_carrier_x certified, it is sufficient that the phone complies with the GSM spec.
The CDMA family is:
CDMA (2G) - CDMA2000 (2.5G) - EV-DO (3G) - UMB (4G)
The GSM family is:
GSM (2G) - EDGE/GPRS (2.5G) - UMTS (3G) - HSDPA/HSUPA (3.5G) - LTE (4G)
3G network that is based on W-CDMA
In other words, what the rest of the world calls UMTS?
I`d say the router is worthy of flame no matter what OS it is running. A router must be stable, it should not crash even if you send complete random gibberish at it.
If it turns out that XPSP3 is sending broken UPnP traffic to the router, then MS is a valid flame target for not following the spec properly. That does however not absolve the router.
Oh, you're such a git.
As for SSD having higher cost; more complicated interface logic (pci, sata/pata, etc), they tend to use SLC instead of MLC flash, they tend to be in a parallel or interleaved organization, some have proper on-board logic for wear leveling (compared to the "smartmedia" format that thumbdrives tend to use), etc..
Current Atom is not in any way suitable for phones. It pulls too many watts, especially at idle, and it needs a northbridge chip which is an absolute pig when it comes to power efficiency. If you read marketing materials you might come off with the impression that Atom is the best thing since sliced bread, but if you look at the actual numbers you will see that it uses way too much power for this kind of use.
Atom might, perhaps, show up in a few phones when Moorestown comes out sometime in 2009. Moorestown is a SOC, containing an Atom cpu core plus most of the other stuff you would need on a phone in a single chip. It is however expected to still need more watts than a comparable ARM-based smartphone SOC.
Hence why I said that "Atom doesn't make much sense except on devices where X86 compatibility is a plus".
Not to mention that Atom is a CPU only, you have to add a north/southbridge to get something comparable to a current ARM cell-phone SOC. To give an example - the TI Omap2420 contains everything plus the kitchen sink -accelerated 2d/3d, 3G stuff, SD-card controller, USB interface, IRDA interface, memory controller, display controller (including TV-out)...
Currently, the Atom doesn't make much sense except on devices where X86 compatibility is a plus. In other words, subnotebooks.
4) Any S60 (i.e. Nokia smartphone) device plus putty. If the keyboard is too small, use a bluetooth wireless keyboard.
5) Internet tablet/surfpad. Most of them (like Nokia 770/N800/N810) can connect to a phone over bluetooth to get you online when only cell is available.
The question was HTF do I get a decent smartphone with AT&T/Cingular?
AT&T/Cingular use GSM. Empaler's answer is correct. I love this country no one can agree on anything so nothing ever really gets done properly Not really, at least not with regards to cell carrier control of handsets. The problem is that the FCC punted on Carterphone regulation.
Look into vdsl/vdsl2 bridges, they are designed to do exactly this thing.
See f.ex. http://www.versatek.com/products/vx150.htm
10Base2 coax "thinnet" is 185 meters.
10Base5 coax "thicknet" is 500 meters.
If he wants to drag some cable I'd recommend running some cat3 and get a couple vdsl bridges.
The out-of-box hplj4 (both in win and lin) usually does the job if you need a generic ps driver.
Has saved me several times when I just needed to get basic printing up and running and I'm in a "can't find native driver"/"native driver is umpteen megabytes and I'm on slow net" situation.
Long answer: The 3D API on both Mac and Linux is OpenGL, porting would be easier than it would be if it was originally written for DirectX/Direct3D. However, OSX has a bunch of Mac-only APIs - there is no rule that says that porting from those to Linux equivalents will be any easier than porting from Win32.