*forehead-slap* Thank you! Yes, that's the REALLY BIG one. First six months they'll have some residual immunity courtesy their mother (if the mother's vaccines are up to date), after that there's that terrible gap.
"One thing I've never understood, however . . . is why we care so much about ensuring that EVERYONE gets a series of vaccinations? I mean, as long as I'm vaccinated and I vaccinate my kid, what the fuck does it matter if five kids in their class don't get vaccinated? "
If there aren't enough vaccinated people around, and the disease is in the community, and you or your family can't have the vaccine for some reason (e.g. egg allergy, for a common one)... then you're fucked. It's in your interest that as many people as possible around you get the vaccine too.
And, of course, Microsoft could have shown up any time to the WHATWG list. They were asked, repeatedly. They didn't want to play. So everyone else got together to implement the future without them.
This is law, not code, so "probably will";-) But yes - a GPL violation is a copyright violation, and the FSF and SFLC know just how to communicate that. So it's all good,
In the case of Android tablets violating the GPL, Matthew Garrett has been doing sterling work chasing up violators and... asking for their code. And guess what, it often works fine. Mind you, he's the guy who successfully DMCAed the MPAA.
Except the case where the judgement for GPL violation included the physical televisions containing the violating code. Which was a bankruptcy default (and the real legal lesson is: show up in court), but nevertheless establishes that a GPL violation suit can attract the same sort of penalties as any other copyright suit.
The only way to do this is to send the file (or a good copy) off to another box that root on the first box doesn't have access to. It's like keeping multiple copies of a ledger and flagging any detected differences.
"I just took over a network. I'm still discovering "secrets", since nothing was well documented. Maybe the root password to a box is one of the 100 passwords in the three documents with passwords. Maybe not. I don't care to count how many machines I've had to use less than traditional methods to get onto, because no one knew any passwords."
You poor, poor soul. (hands over LARGE drink) I suggest you set up a copy of MediaWiki, call it the "sysadmin's wiki" and just use it as your personal notebook for all this shit.
A single sysadmin is a seriously problematic anti-pattern even when you don't want to be the single point of failure. There's a theoretically infinite amount of work, and there's never enough time for documentation that would make you not indispensable.
So while you're waiting for a second sysadmin, or at least a PFY, you have to work out how the hell to make yourself not indispensable.
The key point in terms of this article is: anyone with root on a Unix box can actually do what the hell they like - but almost no sysadmins do, because we're nerds and actually care about getting stuff right, or we wouldn't be doing this for a living. Yes, you can haxx0r the logs. No, no-one will care.
* It is the job of every sysadmin to automate themselves out of existence. The trick there is that you are never actually automated out of existence, because there will always, always be new things for you to do. * Maintain an intranet wiki. Just use MediaWiki, it looks like Wikipedia and people think they understand that, and even if they don't it's quite usable out the box to sysadmin standards. I use ours as my personal notebook and if anyone else benefits that's just fine. * Document by reflex, even just notes. Cut'n'paste the terminal to the wiki. Everything. The search function will save your arse. I may be unusual in being one of the few sysadmins I know who likes documentation. * If paranoid managers who don't know what you do for a living want audit logs, just get in the habit of using sudo. sudo -s in extremis. Autosave history. * The ideal is that every service can just be restarted if it fails, and that a crashed box will come back with all services. This tempts people to administer Unix like Windows, but robustifying the services is enough discipline to feel like you're doing things properly. My boss and I agree this is an excellent ideal and sometimes we even bother. Hiccups are documented on the wiki. *cough*
Anyone else got ideas on the simple notion of getting a damn PFY when you need one?
Oh, definitely, the risk is much less. And running something with a virus attached is very unlikely to trash your home directory as much as doing the same on Windows would do to your whole system.
This is really not safe - in the default setup, for instance, the Z: drive is Unix / (file tree root). Wine DOES NOT SANDBOX in any actually effective manner.
People have run viruses with Wine. Wine is compatible enough to run malware!
Any binary running in Wine can do anything that user can do, like trashing the home directory or filling/tmp .
If you want to be cautious, run it as a different username (with access to your X11 screen). Wine is compatible with toxic waste too.
Everything John Young has ever said about Wikileaks, he's changed his mind the next thing he writes. It's a concentric series of retcons and "I didn't say that."
Start two new columns, one for "wikileaks" one for any of the subjects on twitter's worldwide trend list (there's some guy called Mike Ashley who is top trending on two different versions of his name right now).
Slashdot Mirror
In further news, home fucking is killing prostitution.
... a new high score!!!
*forehead-slap* Thank you! Yes, that's the REALLY BIG one. First six months they'll have some residual immunity courtesy their mother (if the mother's vaccines are up to date), after that there's that terrible gap.
"One thing I've never understood, however . . . is why we care so much about ensuring that EVERYONE gets a series of vaccinations? I mean, as long as I'm vaccinated and I vaccinate my kid, what the fuck does it matter if five kids in their class don't get vaccinated? "
http://en.wikipedia.org/wiki/Herd_immunity
If there aren't enough vaccinated people around, and the disease is in the community, and you or your family can't have the vaccine for some reason (e.g. egg allergy, for a common one) ... then you're fucked. It's in your interest that as many people as possible around you get the vaccine too.
In the print world, standard margin at retail is 25-30%, at distributor is 50%. Only 30% is small.
http://thedailyindexed.tumblr.com/
See, the whole thing is actually a web site. When you pay 99c for the app on the iPad, you're buying a nice index.
Go through the indexed pages. Can you find me one story that's worth paying for, that offers value unavailable elsewhere?
Product Manager, i.e. herder of developers. Came from Powerset, who Microsoft bought to pump up MSN Search into BinG!!
And, of course, Microsoft could have shown up any time to the WHATWG list. They were asked, repeatedly. They didn't want to play. So everyone else got together to implement the future without them.
This is law, not code, so "probably will" ;-) But yes - a GPL violation is a copyright violation, and the FSF and SFLC know just how to communicate that. So it's all good,
In the case of Android tablets violating the GPL, Matthew Garrett has been doing sterling work chasing up violators and ... asking for their code. And guess what, it often works fine. Mind you, he's the guy who successfully DMCAed the MPAA.
Except the case where the judgement for GPL violation included the physical televisions containing the violating code. Which was a bankruptcy default (and the real legal lesson is: show up in court), but nevertheless establishes that a GPL violation suit can attract the same sort of penalties as any other copyright suit.
Most corporate iPhone apps are shit. "Let's offer our website ... on iPhone! Yeah, people will pay for that!"
"Don't restrict, but instead log exactly who does what change when and why, and make it trivial to undo any change.
For example, for /etc use revision-control, and require that all changes be comitted."
Yes yes yes. The great thing about this is, it makes the sysadmin's life easier.
The only way to do this is to send the file (or a good copy) off to another box that root on the first box doesn't have access to. It's like keeping multiple copies of a ledger and flagging any detected differences.
"I just took over a network. I'm still discovering "secrets", since nothing was well documented. Maybe the root password to a box is one of the 100 passwords in the three documents with passwords. Maybe not. I don't care to count how many machines I've had to use less than traditional methods to get onto, because no one knew any passwords."
You poor, poor soul. (hands over LARGE drink) I suggest you set up a copy of MediaWiki, call it the "sysadmin's wiki" and just use it as your personal notebook for all this shit.
A single sysadmin is a seriously problematic anti-pattern even when you don't want to be the single point of failure. There's a theoretically infinite amount of work, and there's never enough time for documentation that would make you not indispensable.
So while you're waiting for a second sysadmin, or at least a PFY, you have to work out how the hell to make yourself not indispensable.
The key point in terms of this article is: anyone with root on a Unix box can actually do what the hell they like - but almost no sysadmins do, because we're nerds and actually care about getting stuff right, or we wouldn't be doing this for a living. Yes, you can haxx0r the logs. No, no-one will care.
* It is the job of every sysadmin to automate themselves out of existence. The trick there is that you are never actually automated out of existence, because there will always, always be new things for you to do.
* Maintain an intranet wiki. Just use MediaWiki, it looks like Wikipedia and people think they understand that, and even if they don't it's quite usable out the box to sysadmin standards. I use ours as my personal notebook and if anyone else benefits that's just fine.
* Document by reflex, even just notes. Cut'n'paste the terminal to the wiki. Everything. The search function will save your arse. I may be unusual in being one of the few sysadmins I know who likes documentation.
* If paranoid managers who don't know what you do for a living want audit logs, just get in the habit of using sudo. sudo -s in extremis. Autosave history.
* The ideal is that every service can just be restarted if it fails, and that a crashed box will come back with all services. This tempts people to administer Unix like Windows, but robustifying the services is enough discipline to feel like you're doing things properly. My boss and I agree this is an excellent ideal and sometimes we even bother. Hiccups are documented on the wiki. *cough*
Anyone else got ideas on the simple notion of getting a damn PFY when you need one?
That's interesting! I have this January 2007 post to wine-devel. That's linked from the Wine FAQ.
Did you write up and post the results of your experiment somewhere? That would definitely be worth a FAQ link too.
Yes. The Wine FAQ, "Risks" says approximately that.
The real answer, of course, is "consider not running dubious and possibly-infected cracks" ...
Oh, definitely, the risk is much less. And running something with a virus attached is very unlikely to trash your home directory as much as doing the same on Windows would do to your whole system.
The "Risks" section of the Wine FAQ answers canonically.
If you've done this, please post a HOWTO to the Wine wiki, or at least the forum!
This is really not safe - in the default setup, for instance, the Z: drive is Unix / (file tree root). Wine DOES NOT SANDBOX in any actually effective manner.
People have run viruses with Wine. Wine is compatible enough to run malware!
Any binary running in Wine can do anything that user can do, like trashing the home directory or filling /tmp .
If you want to be cautious, run it as a different username (with access to your X11 screen). Wine is compatible with toxic waste too.
You kids and your argumentum ad cellarium!
FF4b is way more responsive for my usage (a metric arseload of tabs) than FF 3.6. I'm just waiting for my extensions to update.
Yes, I recall when Wikileaks was being touted how John Young wrote that the whole thing must be a scam.
Everything John Young has ever said about Wikileaks, he's changed his mind the next thing he writes. It's a concentric series of retcons and "I didn't say that."
They posted it to give us a chance for lulz.
I mean, really. Is ANYONE reading this going to think "what a great idea, I'll just sign my DNS up with Amazon"?
As a commenter suggests in the story:
"A game for Tweetdeck users.
Start two new columns, one for "wikileaks" one for any of the subjects on twitter's worldwide trend list (there's some guy called Mike Ashley who is top trending on two different versions of his name right now).
Now, which column is moving fastest?
That's why nobody believes Twitter isn't censoring."