You can probably find various overall safety record stats via Google, but in the meantime you might be interested in the NHTSA safety rating for the Model S. If you don't believe the five-star rating merely because the link I've provided happens to be a (rather detailed) Tesla press release, you're welcome to contact the NHTSA and verify the claim yourself.
Yes. I sincerely doubt I ever got an opportunity to speak with anyone who went to law school; the quality of the responses I got read more like some intern was copying and pasting boilerplate PR material instead.
Apparently you have a gross misunderstanding of the legal concepts of trademark dilution, promotional use, and licensing. Logos slapped on cars in various racing circuits must really dilute the brands involved, huh? It's probably also worth mentioning that I offered to contribute 30% of all proceeds back to financially support open source projects of Canonical's choosing as well, which isn't exactly insignificant after small volume production costs are accounted for in something meant as an exercise in open source awareness promotion. Judging by the boilerplate PR nature of the replies I got, I never even spoke with anyone who went to law school. Apparently you're the idiot here.
You go right ahead and make your own distribution, including a nice toolchain and community to support it. I'll be over there promoting successful distros and projects that I use on a daily basis.
I strongly suspect you have no idea at all what "make your own distro" means.
That just pisses me off, since I was calling my "cost of production" $10/hour for designing, purchasing, printing, and assembling the components of various kite designs (and some were pretty nifty designs) on a part time / evening hours basis. The end result would have cost about USD $2-3/unit for kids. The t-shirts you linked to probably cost about $2 to produce, and are being sold at > $20 apiece. Lovely.
It's not reasonable at all. Canonical could easily grant a narrow use license for the trademarked logo on grounds of promotional value, with the value specifically being talking to kids about an operating system they can control and contribute to themselves. They simply chose to default to the policy of ignoring the potential value without any further discussion on the matter. Then again, what do you expect of a distribution that rides on the coattails of Debian with every release, right?
Your sentiment is well taken, and just for reference I'm a Debian fan of some 13 years (I've run Debian [and various BSD flavors] on all my core infrastructure for ages, and have worked as a senior engineer responsible for hundreds of Ubuntu hosts containing thousands of virtualized Linux guests of varying distros). That said, Canonical has actually done a decent job of promoting Ubuntu, and it's a fact that getting people introduced to Ubuntu first and other distros later (owing to the DFSG, which is a good thing, but only tenable under certain conditions) has been a somewhat easier route than some others in terms of helping kids discover open operating systems.
I am not a lawyer, but I do have extensive experience in contract composition and review, along with extensive experience in trademark protection. This is precisely why I contacted Canonical before printing any kite sails, but I was still disappointed with the outcome. Again, oh well.
Just to make things clear, you're certainly right that alternatives exist. That said, you should be aware that various other projects also enjoy protection under United States trademark laws, although they are far less hostile than Canonical in my experience.
To further illustrate the problem with review of trademark concerns at Ubuntu, several years ago I contacted their legal department with a request to be permitted to use the Ubuntu logo, alongside those of several other notable open source Linux and BSD distributions, for printing on the sails of small kites for sale at the cost of production. The objective was to create an opportunity for people to ask "hey, what's that logo represent" and engage youngsters in a discussion on open source operating systems. The request was summarily denied with some hand waving about brand protection and value to the company. Oh well.
To extend the analogy a bit and pay additional credit to the wolf, some wolves can and do function quite well as sheep dogs. In keeping with the nature of wolves, sometimes the line between what is perceived as a protector and what is perceived as a threat is only a matter of interpretation on the part of leaders that are ill-equipped to make the determination in the first place. To clarify the point a bit, you cannot ever truly tame a wolf. You can establish a relationship with it based on mutual respect and hierarchy, but you cannot bend it entirely to your will. Dogs are another matter, and can be broken.
I speak from experience, having been fortunate enough to have a wolf as a member of my family in my life.
I should have clarified the remote sync bit. The idea is to only rsync the encrypted deltas of your primary mirror. Doing it this way with an added layer of tracking does incur a ton of additional overhead for your local storage to gain minimized network transfer, though. A better method, one I've actually used in the past, involves a script that scans your rdiff-backup mirror for changed files, encrypts them, and shuttles the encrypted files off to remote servers. The state of your mirror is saved in a simple flat file, one line per entry. You could use a persistent key-value store instead if you like.
I use ZFS for bulk data storage, but then added complexity comes from getting the snapshots encrypted and mirrored to offsite servers with any reasonable level of efficiency. All things considered, I'd say ZFS snapshots are great for local point in time recovery, but you'd really want to use something akin to the "track/encrypt/upload" method described above for maximum efficiency.
Write yourself a simple set of scripts that use rdiff-backup or rsnapshot to perform differential/incremental backups to an internal host, make a secondary mirror encrypted at a file level with GPG/PGP, and use rsync to sync the encrypted mirror to several offsite hosts. Done. If this level of security matters to you, do it yourself.
Why would you host your critical infrastructure on any hosting provider that has only one datacenter? If your stuff can't go down, you need to have it designed to work in a distributed manner and hosted in more than one physical facility. This costs more money, though.
Replying to my own post for one bit of clarification: the VOIP and XMPP aspects may not qualify as completely managed services depending on what you have in mind, but there's nothing stopping you from operating them on otherwise managed infrastructure.
I'm a senior engineer at FireHost, and we can provide managed infrastructure and installation assistance for the things you've listed, complete with managed SSL VPN access for all your employees.
Again, this is an admittedly shameless plug, but it does answer the question.
Trained in first aid? Doing something macho? What a joke. If one of my children were dying and I knew anything resembling proper help were more than ten minutes away, you can bet your ass I'd put her in the car and do whatever was necessary to get her to the nearest hospital or clinic as fast as possible. That would likely include calling emergency services dispatch on the way and asking for an intercept on my route, but again, you can bet I'd be flying for a doctor. You can keep your "I'm trained" attitude, and that's coming from someone who served alongside Navy Corpsmen. They'd give you exactly the same response in a grievous situation: don't play doctor, do what you can to initially stabilize a life-threatening condition within reason if that means throwing someone else in the car to attempt to stem severe bleeding and/or administer CPR en route, and get to a physician as fast as possible. That last part doesn't include waiting around for an ambulance in severe situations. The one exception I would make to this would be any case involving a potential spinal injury, in which case the victim should not be moved unless the alternative is certain death from other factors.
I've got mod points, and I was gonna mod sI4shd0rk's comment "Interesting", but instead I'll put a note here for the benefit of others that I must admit I find your comment rather sexy as well.
Blackwater changed their name quite some time ago, first to another variant of Blackwater, then to Xe Services, and most recently to Academi. Their security forces are largely comprised of prior special forces operatives, and they are some of the best on the planet in terms of military operations. I'd wager if push came to shove, they'd be more effective than you think against any single army out of the lower 2/3 standing forces on the planet.
In reality, the favored approach is simply to find a force that doesn't like the force you oppose (for whatever reason), and send in folks from Academi to manage their combat operations and make financial deals with them. You lose a whole lot fewer operatives that way, and all it takes is money to make your goals a reality. Large "strategic risk management" firms are better poised than ever to conduct such operations, and those capabilities are indeed growing over time.
I'm former Navy, and I know guys doing these gigs. This is the modern expression and expansion of the age-old mercenary concept, only with more corporate boardrooms involved.
Grammars evolve. We certainly don't speak Old English anymore. In English grammar, one attribute of nouns is countability; this is to say that nouns are classified as countable or uncountable. While American English strongly tends toward classification of "software" as an uncountable noun, this is not necessarily the case for the rest of the English-speaking world, and the trend in many regions is toward considering the word countable.
Having grown up in the United States, hearing the phrase "a software" bothered me until a few years ago. However, I'm no longer particularly annoyed by the phrase, and tend to simply use it as a linguistic hint that the speaker is likely not from the United States.
Slashdot Mirror
You can probably find various overall safety record stats via Google, but in the meantime you might be interested in the NHTSA safety rating for the Model S. If you don't believe the five-star rating merely because the link I've provided happens to be a (rather detailed) Tesla press release, you're welcome to contact the NHTSA and verify the claim yourself.
Yes. I sincerely doubt I ever got an opportunity to speak with anyone who went to law school; the quality of the responses I got read more like some intern was copying and pasting boilerplate PR material instead.
Apparently you have a gross misunderstanding of the legal concepts of trademark dilution, promotional use, and licensing. Logos slapped on cars in various racing circuits must really dilute the brands involved, huh? It's probably also worth mentioning that I offered to contribute 30% of all proceeds back to financially support open source projects of Canonical's choosing as well, which isn't exactly insignificant after small volume production costs are accounted for in something meant as an exercise in open source awareness promotion. Judging by the boilerplate PR nature of the replies I got, I never even spoke with anyone who went to law school. Apparently you're the idiot here.
Reference the other comment.
You go right ahead and make your own distribution, including a nice toolchain and community to support it. I'll be over there promoting successful distros and projects that I use on a daily basis.
I strongly suspect you have no idea at all what "make your own distro" means.
The little pamphlet talking about Ubuntu and other distros would probably have sparked the question if natural curiosity didn't. Just guessing here.
That just pisses me off, since I was calling my "cost of production" $10/hour for designing, purchasing, printing, and assembling the components of various kite designs (and some were pretty nifty designs) on a part time / evening hours basis. The end result would have cost about USD $2-3/unit for kids. The t-shirts you linked to probably cost about $2 to produce, and are being sold at > $20 apiece. Lovely.
It's not reasonable at all. Canonical could easily grant a narrow use license for the trademarked logo on grounds of promotional value, with the value specifically being talking to kids about an operating system they can control and contribute to themselves. They simply chose to default to the policy of ignoring the potential value without any further discussion on the matter. Then again, what do you expect of a distribution that rides on the coattails of Debian with every release, right?
Your sentiment is well taken, and just for reference I'm a Debian fan of some 13 years (I've run Debian [and various BSD flavors] on all my core infrastructure for ages, and have worked as a senior engineer responsible for hundreds of Ubuntu hosts containing thousands of virtualized Linux guests of varying distros). That said, Canonical has actually done a decent job of promoting Ubuntu, and it's a fact that getting people introduced to Ubuntu first and other distros later (owing to the DFSG, which is a good thing, but only tenable under certain conditions) has been a somewhat easier route than some others in terms of helping kids discover open operating systems.
I am not a lawyer, but I do have extensive experience in contract composition and review, along with extensive experience in trademark protection. This is precisely why I contacted Canonical before printing any kite sails, but I was still disappointed with the outcome. Again, oh well.
Just to make things clear, you're certainly right that alternatives exist. That said, you should be aware that various other projects also enjoy protection under United States trademark laws, although they are far less hostile than Canonical in my experience.
To further illustrate the problem with review of trademark concerns at Ubuntu, several years ago I contacted their legal department with a request to be permitted to use the Ubuntu logo, alongside those of several other notable open source Linux and BSD distributions, for printing on the sails of small kites for sale at the cost of production. The objective was to create an opportunity for people to ask "hey, what's that logo represent" and engage youngsters in a discussion on open source operating systems. The request was summarily denied with some hand waving about brand protection and value to the company. Oh well.
To extend the analogy a bit and pay additional credit to the wolf, some wolves can and do function quite well as sheep dogs. In keeping with the nature of wolves, sometimes the line between what is perceived as a protector and what is perceived as a threat is only a matter of interpretation on the part of leaders that are ill-equipped to make the determination in the first place. To clarify the point a bit, you cannot ever truly tame a wolf. You can establish a relationship with it based on mutual respect and hierarchy, but you cannot bend it entirely to your will. Dogs are another matter, and can be broken.
I speak from experience, having been fortunate enough to have a wolf as a member of my family in my life.
Is a bag of marshmallows involved at some point? That would change everything.
I should have clarified the remote sync bit. The idea is to only rsync the encrypted deltas of your primary mirror. Doing it this way with an added layer of tracking does incur a ton of additional overhead for your local storage to gain minimized network transfer, though. A better method, one I've actually used in the past, involves a script that scans your rdiff-backup mirror for changed files, encrypts them, and shuttles the encrypted files off to remote servers. The state of your mirror is saved in a simple flat file, one line per entry. You could use a persistent key-value store instead if you like.
I use ZFS for bulk data storage, but then added complexity comes from getting the snapshots encrypted and mirrored to offsite servers with any reasonable level of efficiency. All things considered, I'd say ZFS snapshots are great for local point in time recovery, but you'd really want to use something akin to the "track/encrypt/upload" method described above for maximum efficiency.
Write yourself a simple set of scripts that use rdiff-backup or rsnapshot to perform differential/incremental backups to an internal host, make a secondary mirror encrypted at a file level with GPG/PGP, and use rsync to sync the encrypted mirror to several offsite hosts. Done. If this level of security matters to you, do it yourself.
I believe you just mixed up MC Hammer and Vanilla Ice in the same lyric joke, which transcends bad to reach the realm of the unforgivable.
Factor in eight decimal places worth of divisibility to that 20 million limit. I hope you understand why that's significant.
If it's at all possible, it would certainly require government level funding.
Sort of like NSA funding?
Why would you host your critical infrastructure on any hosting provider that has only one datacenter? If your stuff can't go down, you need to have it designed to work in a distributed manner and hosted in more than one physical facility. This costs more money, though.
Replying to my own post for one bit of clarification: the VOIP and XMPP aspects may not qualify as completely managed services depending on what you have in mind, but there's nothing stopping you from operating them on otherwise managed infrastructure.
I'm a senior engineer at FireHost, and we can provide managed infrastructure and installation assistance for the things you've listed, complete with managed SSL VPN access for all your employees.
Again, this is an admittedly shameless plug, but it does answer the question.
Trained in first aid? Doing something macho? What a joke. If one of my children were dying and I knew anything resembling proper help were more than ten minutes away, you can bet your ass I'd put her in the car and do whatever was necessary to get her to the nearest hospital or clinic as fast as possible. That would likely include calling emergency services dispatch on the way and asking for an intercept on my route, but again, you can bet I'd be flying for a doctor. You can keep your "I'm trained" attitude, and that's coming from someone who served alongside Navy Corpsmen. They'd give you exactly the same response in a grievous situation: don't play doctor, do what you can to initially stabilize a life-threatening condition within reason if that means throwing someone else in the car to attempt to stem severe bleeding and/or administer CPR en route, and get to a physician as fast as possible. That last part doesn't include waiting around for an ambulance in severe situations. The one exception I would make to this would be any case involving a potential spinal injury, in which case the victim should not be moved unless the alternative is certain death from other factors.
I've got mod points, and I was gonna mod sI4shd0rk's comment "Interesting", but instead I'll put a note here for the benefit of others that I must admit I find your comment rather sexy as well.
Blackwater changed their name quite some time ago, first to another variant of Blackwater, then to Xe Services, and most recently to Academi. Their security forces are largely comprised of prior special forces operatives, and they are some of the best on the planet in terms of military operations. I'd wager if push came to shove, they'd be more effective than you think against any single army out of the lower 2/3 standing forces on the planet.
In reality, the favored approach is simply to find a force that doesn't like the force you oppose (for whatever reason), and send in folks from Academi to manage their combat operations and make financial deals with them. You lose a whole lot fewer operatives that way, and all it takes is money to make your goals a reality. Large "strategic risk management" firms are better poised than ever to conduct such operations, and those capabilities are indeed growing over time.
I'm former Navy, and I know guys doing these gigs. This is the modern expression and expansion of the age-old mercenary concept, only with more corporate boardrooms involved.
Grammars evolve. We certainly don't speak Old English anymore. In English grammar, one attribute of nouns is countability; this is to say that nouns are classified as countable or uncountable. While American English strongly tends toward classification of "software" as an uncountable noun, this is not necessarily the case for the rest of the English-speaking world, and the trend in many regions is toward considering the word countable.
Having grown up in the United States, hearing the phrase "a software" bothered me until a few years ago. However, I'm no longer particularly annoyed by the phrase, and tend to simply use it as a linguistic hint that the speaker is likely not from the United States.
Given that some viruses infect bacteria and alter their genetic profiles, sure, some of that is possible.
That's why I always encrypt to myself as well as the recipient. It's not difficult.