My situation: Old iPhone 3S, I switched carriers months ago, so no active AT&T contract.
I used the AT&T Wireless Support Chat, Tech Support. Told them I wanted an unlock. Initially got told they couldn't do it, I quoted the press release article. After a couple minutes, the tech opened a ticket for unlocking and said I'll hear by April 16th, 2012. So we'll wait and see.
Short version: Chat works, but be ready with that copy and paste. Also reading asking for a supervisor is helping some folks.
Is there any chance at all of having a Jabber (or something else open-source) instant messager interface for at least whispers, but perhaps guild/officer communication as well? Would make arranging raids and such while we're at work a lot easier where we can't run the WoW client but can run Pidgin or Trillian.:)
Actually, Cisco already has line cards doing 40Gbit and 100Gbit on single fibers, and even their mid-range stuff can do a (theoretical) 720Gbit (Cisco 6500 or 7600, Supervisor 720, fabric-enabled line cards).
10Gbit is trivial these days, in the routing/switching department.
Re:Social hack - use "bullfight" for "speed trap".
on
Is Your GPS Naive?
·
· Score: 1
1) Bumper tag between 4 cars ahead of me. Unable to stop for the suddenly stopped vehicle ahead of me.
3) Truck, no brake lights, locked up tires rear-ended stopped vehicle ahead of him. Unable to stop.
I had already been driving 22 hours and 1,500 miles So, in short, you're a driver who likes to tailgate and take stupid risks while driving.
In at least one state I know of, you most likely would have been found liable for #1 and #3 because you were following too closely and not allowing yourself enough time for defensive action.
Forgive me if I view the rest of your post in that light.
Just a couple minor corrections:
1) Amiga didn't have a unified memory space with NUMA cache-coherency between all participating chips The Amiga did have a unified memory space. See http://en.wikipedia.org/wiki/Chip_RAM . The cache bit, not so much.:)
2) Amiga had multiple processors, but they were all Commodore parts, and soldered in. We're talking about bus standards, and ISAs, and your choice of vendors and upgradability and all that stuff which is more difficult to spec-out AND get buy-in for. It's not a vendor stovepipe. Only a small note here, on MOST Amigas the chips (actually almost all the chips) were in sockets. For example, Amiga 500 owners commonly upgraded their Fat Agnus chips to Fatter Agnus (512KB chip RAM access to 1MB chip RAM, plus a couple minor details). Etc. etc. They were all Commodore parts, however.
Make all the features you do have work well. That's one thing I have to give Cisco gear, whatever features they choose to include on a given system, they all work. Very strongly disagree. Examples: - Kerberos. Cisco claims to support it. Techincally they kind of do if you don't mind 56 bit encryption over telnet and other issues... - ARP inspection and DHCP snooping took MANY versions to settle into something remotely approaching working, and there are still quite a few issues there (try uploading the binding database via SCP sometime...) - The 3750 RPS hardware solution sucks. (I'm hoping the 3750-Es are re-engineered) This on top of us getting a bad batch of 3750s with flakey power supplies (we had 5 or 6 blow a couple weeks after install) was not fun. (The RPS will only power 1 device out of 6, and when it does kick over, you have to manually push a button to have it revert back to the (fixed) 3750. When you do, you have a 50/50 shot of it working fine, or rebooting the stack...) - The Sup720 line still has a few issues - we have multiple instances of one of a "redundant" pair of Sup720s crash, and take the other sup with it, leaving both in rommon... - Etc. etc. etc.
Their QoS stuff is different across every platform they have it seems. Some lines have the very nifty auto qos feature (3750s, for example). Others you need to sit there and calculate out queueing strategies and so on yourself, and its different for every blade. Now, I can understand wanting the ability for that level of detail, but I guess I just like the auto qos better. (We primarily use QoS for the VoIP phones, which is what auto qos was designed for...)
Moreover, does the resolution of a title matter all that much to you yet? Do you have an HDTV that can even reach 1080p? If you do does reaching 1080p make you more like to buy a game? Most bigger TVs put out in the past year do 1080p native, both display and on inputs. Mine that I bought 10 months ago will do it, and I have several other friends that bought similiar fully-1080p capable sets as soon as they came out - they had been waiting for exactly that.
I would wager a good 30% of the people I know have HDTVs that can do 1080p. Most of the others don't have rooms big enough to warrant a screen big enough to make 1080p useful (and that is a consideration - you need a screen bigger than about 50" or so for 1080p to be practical, and that takes a good-sized viewing distance), or are the perputal 'wait-and-see-next-years-models' type.
That being said, I'm getting a little irked at seeing "Yeah, but nobody has 1080p yet!" on headlines on Slashdot (in one form or another). Yes, people have 1080p. The same people with enough disposable income to be buying these other sorts of toys.
We've had a huge number of problems with Cisco's stuff, and unfortuantely are basically locked into Cisco for everything.
Cisco IOS is badly fragmented across Cisco's different product lines. Entire command sets are different for no easily acceptable reason (i.e. commands that do the same thing are named different, or have their parameters in a different order, or a different format). Their SNMP support is absolutely pathetic (no Q-BRIDGE-MIB on anything, they use idiotic community indexing, SNMPv3 has more bugs than I care to think about (contexts (which they use for community indexing in SNMPv3) barely work, and you can't wildcard them).
Their software-only platforms are almost as bad. ACS is notorious for having absolutely no useful diagnostics. (Someone can't authenticate against your LDAP server? Good luck figuring out why...) CallManager isn't quite so bad, except its backup software locks up every week or so and keeps future backups from running until we get in and kill the task. All their Java interfaces require/different/,/conflicting/ versions of Java - one may require 1.4 and nothing else will work, another will require 1.5... and nothing else will work. (Fortuantely they're getting away from Java for their web-based front ends and just going with straight web pages).
Their hardware is OBSCENELY expensive. Our pricing is under NDA, but its still stupid, stupid expensive.
Their technical support is horrid - we groan every time we have to open a TAC case cause we know we're going to waste at least two hours with some idiot before we finally get bumped to someone who actually knows what all the funny little acryonyms in our cases stand for. We have been flat out lied to by TAC on numerous cases, as well.
But, they're Cisco, and the Powers That Be know the word "Cisco", and have seen it around a while, so we go with it.
Should someone go to jail for 5 to 10 years, be stripped of their right to vote, be stripped of their ability to work in federal jobs for the rest of their lives, etc for a $750 crime? Honestly, I think they should, yes. If someone is as self-centered, ill-raised, and disrespectful to do the crime, they have no business voting, no business working for the government they obviously don't care about, and should in fact spend some jail time. 5 to 10 years is perhaps harsh, but certainly some.
Speaking as someone that just had to pay $750 to clean up after some vandals, those laws aren't harsh enough. The people who did it got off with a slap on the wrist - they didn't even have to pay a dime because the police couldn't prove it was them. Now I'm probably going to spend another $300 or so for some cameras because the little shits who did it will probably want revenge for my bringing the police after them.
Good for the early game, but in late game I always preferred lots of big ships stocked to the gills with SP phasers, rangemaster, and high-energy focus.:)
Heh, the way we found out, fortuantely, was in our lab trying to upgrade IOS to a version that didn't go on right for whatever reason. Problem being, the built-in flash on the 720s have enough room for only one image. Grrrr. TAC agreed (after many back-and-forths) that XModem was broken, end of story, no further assistance. Heh.
We have them in our core with the 4 port 10 gigabit ethernet blades in them... massive overkill, but they work OK...
Don't fubar the IOS though - XModem recovery doesn't work on the Sup720s, you're stuck with using Flash cards, assuming you have them. Cisco wanted $1000 for a 256MB flash card... so we went down to Best Buy and picked up a ye-old-standard-512MB CompactFlash for $40, which worked just fine...
This is just my personal opinion, but I'm not really comfortable with 2.6 until they make a 2.7 to toss all the gee-whiz development stuff in to, which they seem to still be using 2.6 for. Until then, mentally I classify 2.6 as a development/unstable kernel, and don't use it for much. I have a couple friends that have had good luck, and some that have horrid luck. One of our servers at work has some very, very odd issues with 2.6, and there are others that won't run 2.4 without patched drivers and the like out the wazoo. I use 2.6 for my desktop machine and it seems OK, although there are a couple weird things.
My senior project (in '99) was to make a distributed 'make' system that was client/server based, could deal with multiple architectures, deal with cross-compilers lending a hand, and status monitoring of it all. Oh, and base it off standard make files, with no other changes to code needed besides running dmake (distributed make) rather than make. Oh, and present full High Level Design and Low Level Design docs before implementation (which actually helped a lot). Used C for most of it, except the GUI (I was in a 4 man team, I don't remember what the GUI guy programmed it in). Ended up working very well, shorting the compile times for our sponser company from days to minutes (they had a LOT of individual PCs but none of them were particularly quick about it).
Was a learning experience, but the main thing I personally got out of it was learning the value behind doing HLD and LLD documentation instead of just coding from the seat of my pants. Just wish I would do it more, actually, would save me a ton of rewriting code. Bleh.
Actually, given the reliability of new versions of IOS, I can pretty much guarantee they DON'T do much regression testing at all. We have gotten more broken things in IOS from "upgrading" than I care to think about.
Slashdot Mirror
My situation: Old iPhone 3S, I switched carriers months ago, so no active AT&T contract.
I used the AT&T Wireless Support Chat, Tech Support. Told them I wanted an unlock. Initially got told they couldn't do it, I quoted the press release article. After a couple minutes, the tech opened a ticket for unlocking and said I'll hear by April 16th, 2012. So we'll wait and see.
Short version: Chat works, but be ready with that copy and paste. Also reading asking for a supervisor is helping some folks.
To Jeffrey Kaplan,
Is there any chance at all of having a Jabber (or something else open-source) instant messager interface for at least whispers, but perhaps guild/officer communication as well? Would make arranging raids and such while we're at work a lot easier where we can't run the WoW client but can run Pidgin or Trillian. :)
Actually, Cisco already has line cards doing 40Gbit and 100Gbit on single fibers, and even their mid-range stuff can do a (theoretical) 720Gbit (Cisco 6500 or 7600, Supervisor 720, fabric-enabled line cards).
10Gbit is trivial these days, in the routing/switching department.
In at least one state I know of, you most likely would have been found liable for #1 and #3 because you were following too closely and not allowing yourself enough time for defensive action.
Forgive me if I view the rest of your post in that light.
As for bus architectures, Zorro III was theoritical 50MB/sec (in practice could only be driven around 20MB/sec, according to http://www.thule.no/haynie/systems/amiga3k/docs/a
- Kerberos. Cisco claims to support it. Techincally they kind of do if you don't mind 56 bit encryption over telnet and other issues...
- ARP inspection and DHCP snooping took MANY versions to settle into something remotely approaching working, and there are still quite a few issues there (try uploading the binding database via SCP sometime...)
- The 3750 RPS hardware solution sucks. (I'm hoping the 3750-Es are re-engineered) This on top of us getting a bad batch of 3750s with flakey power supplies (we had 5 or 6 blow a couple weeks after install) was not fun. (The RPS will only power 1 device out of 6, and when it does kick over, you have to manually push a button to have it revert back to the (fixed) 3750. When you do, you have a 50/50 shot of it working fine, or rebooting the stack...)
- The Sup720 line still has a few issues - we have multiple instances of one of a "redundant" pair of Sup720s crash, and take the other sup with it, leaving both in rommon...
- Etc. etc. etc.
Their QoS stuff is different across every platform they have it seems. Some lines have the very nifty auto qos feature (3750s, for example). Others you need to sit there and calculate out queueing strategies and so on yourself, and its different for every blade. Now, I can understand wanting the ability for that level of detail, but I guess I just like the auto qos better. (We primarily use QoS for the VoIP phones, which is what auto qos was designed for...)
I would wager a good 30% of the people I know have HDTVs that can do 1080p. Most of the others don't have rooms big enough to warrant a screen big enough to make 1080p useful (and that is a consideration - you need a screen bigger than about 50" or so for 1080p to be practical, and that takes a good-sized viewing distance), or are the perputal 'wait-and-see-next-years-models' type.
That being said, I'm getting a little irked at seeing "Yeah, but nobody has 1080p yet!" on headlines on Slashdot (in one form or another). Yes, people have 1080p. The same people with enough disposable income to be buying these other sorts of toys.
We've had a huge number of problems with Cisco's stuff, and unfortuantely are basically locked into Cisco for everything.
/different/, /conflicting/ versions of Java - one may require 1.4 and nothing else will work, another will require 1.5... and nothing else will work. (Fortuantely they're getting away from Java for their web-based front ends and just going with straight web pages).
Cisco IOS is badly fragmented across Cisco's different product lines. Entire command sets are different for no easily acceptable reason (i.e. commands that do the same thing are named different, or have their parameters in a different order, or a different format). Their SNMP support is absolutely pathetic (no Q-BRIDGE-MIB on anything, they use idiotic community indexing, SNMPv3 has more bugs than I care to think about (contexts (which they use for community indexing in SNMPv3) barely work, and you can't wildcard them).
Their software-only platforms are almost as bad. ACS is notorious for having absolutely no useful diagnostics. (Someone can't authenticate against your LDAP server? Good luck figuring out why...) CallManager isn't quite so bad, except its backup software locks up every week or so and keeps future backups from running until we get in and kill the task. All their Java interfaces require
Their hardware is OBSCENELY expensive. Our pricing is under NDA, but its still stupid, stupid expensive.
Their technical support is horrid - we groan every time we have to open a TAC case cause we know we're going to waste at least two hours with some idiot before we finally get bumped to someone who actually knows what all the funny little acryonyms in our cases stand for. We have been flat out lied to by TAC on numerous cases, as well.
But, they're Cisco, and the Powers That Be know the word "Cisco", and have seen it around a while, so we go with it.
EVGA.
http://www.evga.com/community/messageboard/
Speaking as someone that just had to pay $750 to clean up after some vandals, those laws aren't harsh enough. The people who did it got off with a slap on the wrist - they didn't even have to pay a dime because the police couldn't prove it was them. Now I'm probably going to spend another $300 or so for some cameras because the little shits who did it will probably want revenge for my bringing the police after them.
Good for the early game, but in late game I always preferred lots of big ships stocked to the gills with SP phasers, rangemaster, and high-energy focus. :)
Samsung's line of DLPs that came out this year do 1080p, take 1080p on component and HDMI, and are under $3k.
Actually, this year's Samsung DLPs (HLS-xx87W and 88W) have 1080p support on both HDMIs and component inputs.
One I just learned:
Any Person Studying This Needs Desperate Psychotherapy.
Heh, the way we found out, fortuantely, was in our lab trying to upgrade IOS to a version that didn't go on right for whatever reason. Problem being, the built-in flash on the 720s have enough room for only one image. Grrrr. TAC agreed (after many back-and-forths) that XModem was broken, end of story, no further assistance. Heh.
We have them in our core with the 4 port 10 gigabit ethernet blades in them... massive overkill, but they work OK...
Don't fubar the IOS though - XModem recovery doesn't work on the Sup720s, you're stuck with using Flash cards, assuming you have them. Cisco wanted $1000 for a 256MB flash card... so we went down to Best Buy and picked up a ye-old-standard-512MB CompactFlash for $40, which worked just fine...
Yeah, we're stuck using them as "routers", rather amusing... but they do OSPF and BGP well enough.
Except one of Cisco's newest line, the Sup720s on Cat6ks, don't offer IOS 12.3 yet...
Oh, and there's no IOS at all for the Sup32s, even though one has been promised for almost a year now (bit hard by that one)...
Same with Cat3750s....
Mind you, I think all of these support IPv6 anyway, but I'm just refuting your "IOS 12.3 and that runs on everything" line...
This is just my personal opinion, but I'm not really comfortable with 2.6 until they make a 2.7 to toss all the gee-whiz development stuff in to, which they seem to still be using 2.6 for. Until then, mentally I classify 2.6 as a development/unstable kernel, and don't use it for much. I have a couple friends that have had good luck, and some that have horrid luck. One of our servers at work has some very, very odd issues with 2.6, and there are others that won't run 2.4 without patched drivers and the like out the wazoo. I use 2.6 for my desktop machine and it seems OK, although there are a couple weird things.
My senior project (in '99) was to make a distributed 'make' system that was client/server based, could deal with multiple architectures, deal with cross-compilers lending a hand, and status monitoring of it all. Oh, and base it off standard make files, with no other changes to code needed besides running dmake (distributed make) rather than make. Oh, and present full High Level Design and Low Level Design docs before implementation (which actually helped a lot). Used C for most of it, except the GUI (I was in a 4 man team, I don't remember what the GUI guy programmed it in). Ended up working very well, shorting the compile times for our sponser company from days to minutes (they had a LOT of individual PCs but none of them were particularly quick about it).
Was a learning experience, but the main thing I personally got out of it was learning the value behind doing HLD and LLD documentation instead of just coding from the seat of my pants. Just wish I would do it more, actually, would save me a ton of rewriting code. Bleh.
(shudder) I remember having to install a pair of those for a RAID card we bought from Sun (that never worked right).
I kept looking from the directions to the case and back again, thinking, "You're joking, right? What do I look like, a four handed midget monkey?"
Actually, given the reliability of new versions of IOS, I can pretty much guarantee they DON'T do much regression testing at all. We have gotten more broken things in IOS from "upgrading" than I care to think about.
January 27, 1995, found by the magical "dart in a calendar on the wall" method.