Comment Re:How long must we suffer? (Score 1) 164
Looks like it's back up and running. I can sign into the CC application as well as their various web properties.
Looks like it's back up and running. I can sign into the CC application as well as their various web properties.
Your main workflow, on the other hand, shouldn't be constrained by your network. There's so many things that could wrong in that chain.
1. your computer
2. your router/LAN
3. your ISP
4. the internet (yeah, sometimes everything breaks)
5. Adobe's servers
as opposed to just (1) if you've purchased a static installation.
And this is where some clarity is needed, I suspect. Again, as has been stated numerous times in this thread: the applications will continue working as long as they have already validated your subscription. For instance, I just fired Photoshop and Premiere up. Both popped open a dialog that said, basically, "Hey, we can't validate your subscription, but you can continue using the app until July 28, 2014. If we can't connect by then, your product will stop working."
There are a *FEW* folks that will run into problems authenticating and consequently not being able to use the product. Why their machines haven't authenticated in the past is beyond me. But the dialog is clear: I have almost 2.5 months! I suspect most people (other than those trying to do new installs... UGH!) are in the same boat.
Is it ideal? Oh hell no. Is there anything we can realistically do about it? Well, we can leave Adobe if that's our choice. But as has been pointed out elsewhere, their products really *are* the best out there. I know comparing FCPX and Premiere Pro is almost laughable (and I've done it on my new Mac Pro). As optimized as FCPX is for the new Macs, Premiere is *still* faster for what I do. No one else really has a Photoshop. Or a Lightroom if you don't need PShop's grunt.
Another solution: stick with the CS6 versions of the suite assuming you've already purchased them. The problem with that is: they're not being developed any more, and will *only* have major bug fixes done. What? Can't run them on the latest OS de'jour? Tough shitski. You're outta luck.
I'm not trying to defend the CC sub model because it sucks the big'n. But I *like* Adobe's software, so I'll continue p[l]aying along. If something better appears, I'll look into it.
Adobe, incompetent? I wasn't aware that there was any doubt about that?
I think their application developers are top notch, actually. Their IT and infrastructure guys, on the other hand? Not... so much. If a "competence injection" could be given, I'd aim it towards their inf guys, not their devs.
The best part is that this is happening on the eve of Adobe canceling sales of perpetual licensing to Adobe Creative Suite products
I attached a comment to this article before it was posted, but it looks like timothy nuked it before he made it live.
This "sniff test" for this is: hack. Not maintenance. I say that because the authentication system went down, as best I can tell, around 1700EST Wednesday. Afternoon maintenance is not unheard of, but it seems like a silly and unlikely thing to do.
Hope I'm wrong about that.
Fortunately, as I pointed out: you can still the CC apps while this debacle is being un-FUBAR'd. That is unless it takes them up to 2 months to fix it, at which point the app will no longer be able to authenticate and validate your subscription. THEN it's "NO Photoshop for you!"
If it takes them that long to fix this, then they are truly, completely, and absolutely incompetent...
I should have put this in the main body but: the sniff test for this seems to indicate a hack, given the time of day the authentication system tanked (circa 1700EST). It's *unlikely* to be due to maintenance, specially at that time of day. And catastrophic hardware and/or software failure should be recovered by now.
Yeah, for a TI-99/4a with it's 256 bytes of actual CPU 'scratchpad' RAM on the TMS9900's 16-bit system bus vs today's 16GBs is, what, about 67 million?
I had the same challenge, but today's computer has 48GB. There aren't enough 0s in the poll.
As for me personally, I too own a dual-stack router (RVS4000) but Comcast is trying to nickel and dime me on switching to IPv6. They want me to buy a new cable modem (because I refuse to pay the "rental fee")
Are you in one of the markets they have IPv6 available? I didn't think they'd rolled it out everywhere yet.
Further: are you on a D2 or D3 cable connection? If you're still on a D2 modem, I'd recommend taking the plunge and bumping up to D3. IPv6 becomes much easier, and you'll have a bigger speed potential.
I never stated that what I said was exact fact
Perhaps you were speculating. The tone of your post was one of (an attempt at?) knowledge. And it's a bit misguided.
The insight I've gained tells me that NO ONE is ready to simply flip a switch; it's going to be a painful, multi-year migration.
I don't want to speak for Morgaine, but I suspect this last sentence in your post is probably one of the things he took issue with. You're making it sound like administrators and network engineers need to
flip a switch
to migrate to v6 and that's not the case. It's more like flipping a switch and adding IPv6 to the game.
There's a distinct and important difference.
Where you're partially right is the challenge with old network gear that can easily handle IPv4 in hardware. A lot of those devices aren't capable of handling v6 in hardware, and possibly not even in software depending on how old they are. Enterprises with established network hardware are often loathe to swap them out for newer devices. If a switch needs to be flipped, it's that: replacement of old, legacy (and quite frankly, crappy) hardware.
And once enabled, IPv6 works totally happily and transparently alongside IPv4 in the home network and at the server end, so there are no "switch over" issues. IPv4 continues to work exactly as it did prior to enabling IPv6.
What he said. Every device in my house is dual-stacked and happily running with both v4 and v6. It took all of 10 minutes to create a new account with the likes of Hurricane Electric and then set up my tunnel. I've got an entire
Well... maybe.
The tunnel broker solution is a very easy one for those of us not connected to an ISP that provides a native IPv6 solution (yet?) And once you enable it, most of your browsers and whatnot will automatically try the v6 address they get back from an FQDN look-up.
As an aside, I recently tried to create an IPv6-only Linux VM on my VMWare rig. I wanted to see if enough of the infrastructure services were available via v6 to work. It worked fine; NTP, yum upgrades (CentOS), etc all work on it. The only interesting challenge is my NAS at home doesn't yet support NFS via v6.
What's the AAAA record for slashdot.org?
I was going to post this exact thing. Hey... slashdot...
$ dig www.slashdot.org aaaa | grep "ANSWER SECTION"
$
Whassupwiddat?
For folks that want to let Adobe know about their displeasure regarding the new licensing model, make a Feature Request here: http://www.adobe.com/go/wish
The more, the merrier.
jas
My game of choice at the moment is Battlefield 3. The availability of that game isn't the only thing preventing me from converting to Linux for gaming. What about the next game I want to play, and the one after that? Are they also going to be released for Linux at the same time they're released for Windows?
Further, there's better support for the hardware I'm using when I play:
- Thrustmaster HOTAS joystick and throttle for flying in the game (including drivers to remap the buttons, toggles, etc)
- nVidia GTX680 with 3 LCD panels attached, running nVidia's surround video
- Sound Blaster from Creative, which includes utilities for controlling which output the card sends sound through, etc.
When I'm gaming, I just want the rig to work. I don't foresee that happening with Linux any time soon.
Your hands should be kept at shoulder width and shoulder height. For some that's 10/2, for others 9/3 (though that's pretty rare). Generally it's between those two for most people. If the bag deploys, it'll inflate within the bends in your elbows, and potentially push your hands outwards towards the side. You might end up with bruised knuckles, but that'll be the extent of it.
jas (15+ years on the race track, and have done the accident thing)
HELP!!!! I'm being held prisoner in /usr/games/lib!