In reality, Google only offers 99.9% per month (99% for "reduced availability", I'm not sure what these prices are for) and the value of the guarantee is pathetic: they credit (not even refund) you a maximum of half your bill that month if availability is =95%. They could be down a full day and only knock 25% of you bill next month. That can barely be considered an SLA.
In my experience that is even better than most SLAs I've seen. Standard is to prorate the month and reduce that month's bill or add a credit to the next for the amount down so if you are paying $1000 monthly and you are down a day you get $33.40 back (assuming 30 days in the month).
I already have a 2 TB nas stuffed with movies bit this has the advantage that it is off site.
If your house burns down your NAS goes with it. At least this way I have off site recovery.
Yes, I can come up with a thousand free market answers. And yes, that pretty much answers your question.
Would you buy a vehicle from any company whatsoever if you knew that parts were difficult to acquire? A manufacturer can play a game with parts availability only if they don't plan to stay in business.
Maybe we should go back to renting our phones from ATT as well.
I think the summary was actually saying that Apple did NOT clearly spell out its support schedules like many other software companies DO. Rough quote - "this would not be noteworthy if Apple, like other software vendors, DID...."
So it's saying other software vendors DO do that, but Apple does not. Which is what you're saying. Can't we all just get along...
For all of Microsoft's failures, bad business practices (particularly in the past), etc., they seem to be doing some things right these days. I'm not too big of a fan of the new start screen (easily fixed)
Yeah, they got the link wrong...not sure what happened there.
Hi all -- I submitted this review, but it looks like something ate the link for the book. Here's where to buy it:
- You can buy DRM-free PDF, epub and mobi ebooks directly from the author
- Or you can buy the dead tree version from Amazon
I believe the Amazon link gives the author a few more shekels, but he makes the most money from the first link; details from his website's page on this book.
If you're a Unix or Linux sysadmin, you know sudo: it's that command that lets you run single commands as root from your own account, rather than logging in as root. And if you're like me, here's what you know about configuring sudo:
- Run sudoedit and uncomment the line that says "%wheel ALL=(ALL) ALL".
- Make sure you're in the wheel group.
Okay, so you can now run any command as root. Awesome! But not everyone is as careful as you are (or at least, as you like to think you are). If you're a sysadmin, you need to stop people from shooting themselves in the foot. (Might also want to stop yourself from self-inflicted gunshot wounds.) There should be some way of restricting use, right? Just gotta check out the man page.... And that's where I stopped, every time. I've yet to truly understand Extended Backus-Naur Form (sue me), and my eyes would glaze over. And so I'd go back to putting some small number of people in the "wheel" group, and letting them run sudo, and cleaning up the occasional mess afterward.
Fortunately, Michael W. Lucas has written "Sudo Mastery: User Access Control for Real People". If his name sounds familiar, there's a reason for that: he's been cranking out excellent technical books for a long time, on everything from FreeBSD to Cisco routers to DNSSEC. He just, like, does this: he takes deep, involved subjects that you don't even know you need to know more about, and he makes them understandable. It's a good trick, and we're lucky he's turned his attention to sudo.
The book clocks in at 144 pages (print version), and it's packed with information from start to finish. Lucas starts with the why and how of sudo, explaining why you need to know it and how sudo protects you. He moves on to the syntax; it's kind of a bear at first, but Chapter 2, "sudo and sudoers", takes care of that nicely. Have you locked yourself out of sudo with a poor edit? I have; I've even managed to do it on many machines, all at once, by distributing that edit with CFEngine. Lucas covers this in Chapter 3, "Editing and Testing Sudoers", a chapter that would have saved my butt. By the time you've added a few entries, you're probably ready for Chapter 4, "Lists and Aliases".
sudo has lots of ways to avoid repeating yourself, and I picked up a few tricks from this chapter I didn't know about — including that sudo can run commands as users other than root. Need to restart Tomcat as the tomcat user? There's a sudoers line for that. I'm ashamed to admit that I didn't know this.
There is a lot more in this book, too. You can override sudo defaults for different commands or users (you can change the lecture text; maybe sometimes there *is* a technical solution for a social problem...). You can stuff sudo directives into LDAP and stop copying files around. You can edit files with sudoedit. You can record people's sudo commands, and play them back using sudoreplay. The list goes on.
Sounds like a lot, doesn't it? It is. But the book flies by, because Lucas is a good writer: he packs a lot of information into the pages while remaining engaging and funny. The anecdotes are informative, the banter is witty, and there's no dry or boring to be found anywhere.
Shortcomings: Maybe you don't like humour in your tech books; if so, you could pass this up, but man, you'd be missing out. There wasn't an index in the EPUB version I got, which I always miss. Other than that: I'm mad Lucas didn't write this book ten years ago.
Score: 10 out of 10. If you're a Linux or Unix sysadmin, you need this book; it's just that simple.
Where to buy:
- You can buy the ebook version from Lucas himself.
- You can also buy the ebook or a dead-tree version from Amazon.com.
Link to Original Source
Germany does it by being a lot more picky about what courses they cover and they only allow as many students as the job market will allow for into the programs.
This has nothing to do with internal combustion vs electric and everything to do with the fact that Tesla is removing the car dealers from the chain and the middlemen want to keep their share.
The real issue here is that you were filtering at the wrong point. It should have been your customers doing egress filtering in this case.
He didn't say spoofing, he said transiting, so they are people who have their own IP blocks assigned and are using those. The advantage is that you can have multiple uplinks and use the second as backup if your primary goes down and all of the ips never change.