I suggest once a year. It's a good opportunity to test high-availability components and failover procedures, and to re-arrange power layouts and replace UPS batteries. Too many clients get pretty fussy about even scheduled reboots, and communicating the downtime to everyone in a large environment can create political battles.
You still have to deal with an unnecessary gravity well launching from the moon. Solar sails and asteroid mining present some fascinating economics: Solar sails can act as solar mirrors, providing rocket free orbital guidance, power for electricity generation and magnetic funneling of the solar wind into a centrifuge for refininng deuterium and tritium out of the solar wind.
There are interesting reasons to build lunar bases, but this is not one of them. If you need mining operations, use the solar sails to guide asteroids in for asteroid mining. The lead times for return on investment are very long, but that kind of long range investment is what governments are designed for.
The article has problems, but that "rare Earth" comment is merely confusing. It means elements or isotopes rare on Earth. People will misread it or associate it with the "rare earth" materials, as you did. That confusion is a very understandable one, and the editor should have noticed it.
If it were spelled "rare earth", then it would be clearly wrong.
It doesn't have to be "law", if it's enforced by custom. The observation is relevant: if women are not physically there as part of protest movements, it's a sign that they are either kept out of public events, or that it's only the men who are interested in the issue. Such movements are very likely to be controllable by police or military force, and will be so controlled by governments with any power left.
_Failed_ revolutions are a dime a dozen. _Successful_ revolutions, or changes of regime imposed from outside, require popular support.
Those problems may be why the non-profit _exists_. People passionately involved in political or social issues are often _very_ political and social. Excited, eager volunteers can far too easily become disillusioned and angry: this certainly happens in the open source community all the time. After all, OpenBSD was created when Theo de Raadt had issues with the rest of the NetBSD development group. You can try to weed out all dangerous emotional issues from your agenda, you can try to filter out over-passionate members, but then you lose the very ability to create or to change the world that non-profits are created for.
With that in mind, the admins can also be passionate about issues and often are. Often underpaid and administered by people confused about technology, keeping things working with limited non-profit budgets is an artform, and I applaud and learn fascinating tricks from such personnel, and try to share knowledge with them to both of our advantages. In this case, the knowledge is about protocols for password management, protecting email backups, arranging reliable and recoverable and _thorough_ offsite backups and restoration procedures, and how to detect malicious behavior early.
Giving good advice requires some background of the operating systems and amount of data involved. Are there databases involved? Personal information such as credit cards and home addresses? Email from the board of directories? Is it on an Exchange mail server, or GMail services? The details matter a lot.
Have you ever _tried_ to get a warrant against a script kiddie? The last time I tried, the police and the ISP from where the script kiddie was acting both passed it along to FBI, who did _nothing_. Actually getting a prosecution basically involves educating them in how things work, even wuth the much vaunted FBI computer crime teams.
The legal word you are looking for for threats against one's person or safety is "assault". The legal word for laying hands on someone else against their wil and without other justifiable cause is "battery". The word "attack" has _never_ had the kind of "purely physical attack" definition you claim. The ambiguity is in your limited definition of the world: I can see where that would be confusing.
Only if they weren't "attacks". They often include theft, including theft of money and private information. They're often expensive to repair, They often break or impedes other computer services, and the most common forms of them are for illegal activity (such as spam running DDOS attachs). Or have you failed to look at what botnets are and how they are run?
Because such attacks far outnumer mere "exploitation attempts", and because even a mere "exploitation attempt" involves theft of computer resources or private data, yes, it's reasonable to call them "attacks".
Good point. Is bluetooth and wi-fi peer-to-peer in the latest smartphones? I admit mine is not the latest. I've actually not seen it built-in.
I could see issues with laptop communications linked to bluetooth audio devices, just as I can see issues with class notes stored in calculators. And today, there's live access to Wikipedia for _everything_ as a problem in tests.
Excuse me, but how do you reach a cell phone tower to share data from inside a Faraday cage?
Built-in walkie talkie systems might be able to connect, but most such in modern cell phones are simply free use of the local cell system for other subscribers. They still require the cell towers.
Oh, my. I love such audits. The staff from the targeted company very prepare PowerPoint slides, checklists, and presentations. And I get to go quietly look at their systems and see what they failed to mention or what they completely lied about, and ideally find a disgruntled employee or two to let me know off the official record where to look. Separating them from their managers is difficult, but well worth the time and support invested.
When you have 1000 servers, in 30 or more different configurations, typos, changes, and unexpected conflicts are inevitable. They're aggravated by complete fear of clean-up and integration operations, where ordinary system upgrades and software cleanups cannot occur until after complete project planning, which triples their timescale and makes them far, far more likely to fail catastrophically.
It's a complex balancing act: I appreciate my role's ability to come in from outside and support the competent people who've been struggling, unthanked and ignored, to actually get their systems working with external validation.
That also doesn't make it a crime: the changes in child-rape laws, the changes in spousal rape laws, the changes in sexual abuse laws in the workplace (especially in third world countries), and the policies in different countries of what constitutes drug-aided rape involving alcohol or light intoxicant, or even the relationships between therapist and client or priest and worshipper involving sexuality all have had different standards at different times. Throw in rape as a legal punishment or as treatment of conquered civilians, both men and women, and you have a long, long history of rape as a legal procedure.
That doesn't make it fair, proper, or safe. Like slavery, it insults other people's bodies and takes away their control over their fate and especially their own bodies. But it's certainly a legally supported act in many societies, and is a fairly frequent behavior in the animal kingdom, so it's as natural as other slightly unusual sexual behaviors, including homosexuality, incest, polyamory, or doing it standing up or back to front.
It doessn't. Recent regulatory changes at the SEC, and promises to "review" the situation, have carefully avoided striking at the heart of the larger investment companies and groups that both engage in this sort of behavior, and have enough spare cash to fund politicians and arrange their own "reports" for the SEC on how disemboweling thihs sort of high-speed trading would "hinder the market".
It's insider trading with a high-tech cover. The data is not avaialble to ordinary investors in time for them to take keaningful action: the millisecond of having their servers right near the NySE overwhelm the reponse times of any ordinary trading entity and prevent their meaningful responses.
Don't blame the vendors. The specs for Vista were metamorphosing from day to day until Service Pack 1, and no vendor could predict which way the other vendors would sway things, so there was no _point_ for them in alpha testing. And don't forget the nightmare that was WinFS, which has corectly been discarded entirely. Shoving an ill-managed, demonstrably fragile, resource gobbling and impossible to repair database into the kernel's filesystem components was a bad idea. It's why Berkeley DB was never successfully integrated into ext2: it's a destabilizing approach and was deservedly discarded, although it wasted thousands of hours of vendor engineer time trying to integrate storage devices to support it.
The first issue is that you have to convince people that their business practices are wrong. This is not easy, and often requires lying through your teeth with statistics. Testing costs time and money and slows down releases. _Foolish_ testing, with lots of business case meetings and Powerpoint slides and expensive test configurations that don't actually test anything but demoware, is even more expensive and wasteful. The testing needs to actually prevent support calls, save engineering time re-fixing the same bugs, prevent support calls, and especially _help sales_. Ideally, they also help prevent liability: look up the phrase "always mount a scratch monkey" for the canonical story of failing to test a change.
The second issue sounds like a basic source control issue. It sounds like developers or engineers are reverting fixes after you've made them and committed them, and this should _never_ happen. Switching to a better source control process sounds vital to your issues, and may solve a lot of your issues without expensive test suites. Which source control suits your local programming styles is your own choice, but having a central trunk or repository that changes, and logging of changes, is committed to might at least help you cover your backside the next time this happens.
And the heat, water, and electricity must be "free" in your building.
2000 messages/month of "practially nothing" adds up, and I'm getting plenty of months like that when some "consultant" misconfigures my old, documented, robust alert system and just goes ahead and "turns on everything, to debug". Then everry single one of dozens or hundreds or even thousands of systems starts sending distinct alerts, because they've sidetracked my very careful hierarchy of "if this alert happens, it means the VPN is down: _wait_ before alerting for every remote server."
Given Hillary's accomplishments as an attorney, presidential committee leader, and secretary of state, what makes you think she'd be any more competent as a president?
She's intelligent and skilled, but not as a leader of a diverse group with different agendas. We saw that with her attempts at universal health care, and we're seeing it now with her wishy-wasy if not schizophrenic handling of Iraq, Afghanistan, Korea, and China.
No, she's too easy to trip up, especially in the debates. And given her beauty pageant history and modeling attempts, I'd unsurprised if there are some embarassing but verifiable photos of her awaiting publication if it looks like she stands a chance.
Do note that during the '08 election, she followed her script exactly. This may be because she was mishandled by McCain's advisors, but also may be because she can't work without a script and could be worse than Reagan that way.
You're less likely to get _any_ improvements. User and developer feedback, flavored with the information in the publicly available source code, have been tremendours sources of Linux and GPL software features and fixes. And one thing that I do as a developer is to publish my patches to the vendors, so that they can integrate them in their next release. (This happens several times a year for me: it's very gratifying, it saves me considerable time in setting up workarounds, and it looks very good on my annual performance reviews.)
2) Company goes under because they didn't make the incredible sums of money they told their venture capitalists they would make. (This is *very* common with portable device manufacturers.) Or becasue their batteries melt. Or because their manager embezzled the money. Or because they get bought up by another company that could not care less about their purchased company's previous owners.
3) In any case, with such a company, your device never had any support anyway: if they can't be bothered to follow the very modest requirements of the GPL, they doubtless had no support capacity anyway. I've actually seen this in manufacturing and software, and the weirdness companies companies go through to avoid having anyone actually take support calls, which cost time and money.
Consider GPL compliance a very good litmus for the device quality. If they can't be bothered to obey simple laws about copyright, what are they violating in terms of bettery recharger handling or basic physical manufacture quality?
I've met far too many programmers, barely half my age, who've already ruined their hands with poor keyboard technique. They've lost the ability to get into the actual code and have doomed themselves to cut&paste programming because their hands can no longer handle typing what they really need: they're forced to let the GUI do it for them, and the result is sometimes very poor code.
Where do you possibly derive this? Most murders and rapes are committed by family members: there's nothing like living that close to someone, especially someone under your physical care or control, to tempt abuse. Religion may ritualize it and set standards such as the child body changing of ear piercing, circumcision, or clitorectomy practiced by various cultures. But how many members of any genocidal army were genuinely religious? How many just followed orders and killed scapegoats?
Slashdot Mirror
I suggest once a year. It's a good opportunity to test high-availability components and failover procedures, and to re-arrange power layouts and replace UPS batteries. Too many clients get pretty fussy about even scheduled reboots, and communicating the downtime to everyone in a large environment can create political battles.
You still have to deal with an unnecessary gravity well launching from the moon. Solar sails and asteroid mining present some fascinating economics: Solar sails can act as solar mirrors, providing rocket free orbital guidance, power for electricity generation and magnetic funneling of the solar wind into a centrifuge for refininng deuterium and tritium out of the solar wind.
There are interesting reasons to build lunar bases, but this is not one of them. If you need mining operations, use the solar sails to guide asteroids in for asteroid mining. The lead times for return on investment are very long, but that kind of long range investment is what governments are designed for.
The article has problems, but that "rare Earth" comment is merely confusing. It means elements or isotopes rare on Earth. People will misread it or associate it with the "rare earth" materials, as you did. That confusion is a very understandable one, and the editor should have noticed it.
If it were spelled "rare earth", then it would be clearly wrong.
It doesn't have to be "law", if it's enforced by custom. The observation is relevant: if women are not physically there as part of protest movements, it's a sign that they are either kept out of public events, or that it's only the men who are interested in the issue. Such movements are very likely to be controllable by police or military force, and will be so controlled by governments with any power left.
_Failed_ revolutions are a dime a dozen. _Successful_ revolutions, or changes of regime imposed from outside, require popular support.
Those problems may be why the non-profit _exists_. People passionately involved in political or social issues are often _very_ political and social. Excited, eager volunteers can far too easily become disillusioned and angry: this certainly happens in the open source community all the time. After all, OpenBSD was created when Theo de Raadt had issues with the rest of the NetBSD development group. You can try to weed out all dangerous emotional issues from your agenda, you can try to filter out over-passionate members, but then you lose the very ability to create or to change the world that non-profits are created for.
With that in mind, the admins can also be passionate about issues and often are. Often underpaid and administered by people confused about technology, keeping things working with limited non-profit budgets is an artform, and I applaud and learn fascinating tricks from such personnel, and try to share knowledge with them to both of our advantages. In this case, the knowledge is about protocols for password management, protecting email backups, arranging reliable and recoverable and _thorough_ offsite backups and restoration procedures, and how to detect malicious behavior early.
Giving good advice requires some background of the operating systems and amount of data involved. Are there databases involved? Personal information such as credit cards and home addresses? Email from the board of directories? Is it on an Exchange mail server, or GMail services? The details matter a lot.
Have you ever _tried_ to get a warrant against a script kiddie? The last time I tried, the police and the ISP from where the script kiddie was acting both passed it along to FBI, who did _nothing_. Actually getting a prosecution basically involves educating them in how things work, even wuth the much vaunted FBI computer crime teams.
The legal word you are looking for for threats against one's person or safety is "assault". The legal word for laying hands on someone else against their wil and without other justifiable cause is "battery". The word "attack" has _never_ had the kind of "purely physical attack" definition you claim. The ambiguity is in your limited definition of the world: I can see where that would be confusing.
Only if they weren't "attacks". They often include theft, including theft of money and private information. They're often expensive to repair, They often break or impedes other computer services, and the most common forms of them are for illegal activity (such as spam running DDOS attachs). Or have you failed to look at what botnets are and how they are run?
Because such attacks far outnumer mere "exploitation attempts", and because even a mere "exploitation attempt" involves theft of computer resources or private data, yes, it's reasonable to call them "attacks".
Good point. Is bluetooth and wi-fi peer-to-peer in the latest smartphones? I admit mine is not the latest. I've actually not seen it built-in.
I could see issues with laptop communications linked to bluetooth audio devices, just as I can see issues with class notes stored in calculators. And today, there's live access to Wikipedia for _everything_ as a problem in tests.
Excuse me, but how do you reach a cell phone tower to share data from inside a Faraday cage?
Built-in walkie talkie systems might be able to connect, but most such in modern cell phones are simply free use of the local cell system for other subscribers. They still require the cell towers.
sudo fuser -k /sbin/syslogd /var/log/secure
sudo history -c
sudo rm -f
And most institutions will never actually notice. Remote syslog daemons are typically overwhelmed with debris.
Oh, my. I love such audits. The staff from the targeted company very prepare PowerPoint slides, checklists, and presentations. And I get to go quietly look at their systems and see what they failed to mention or what they completely lied about, and ideally find a disgruntled employee or two to let me know off the official record where to look. Separating them from their managers is difficult, but well worth the time and support invested.
When you have 1000 servers, in 30 or more different configurations, typos, changes, and unexpected conflicts are inevitable. They're aggravated by complete fear of clean-up and integration operations, where ordinary system upgrades and software cleanups cannot occur until after complete project planning, which triples their timescale and makes them far, far more likely to fail catastrophically.
It's a complex balancing act: I appreciate my role's ability to come in from outside and support the competent people who've been struggling, unthanked and ignored, to actually get their systems working with external validation.
That also doesn't make it a crime: the changes in child-rape laws, the changes in spousal rape laws, the changes in sexual abuse laws in the workplace (especially in third world countries), and the policies in different countries of what constitutes drug-aided rape involving alcohol or light intoxicant, or even the relationships between therapist and client or priest and worshipper involving sexuality all have had different standards at different times. Throw in rape as a legal punishment or as treatment of conquered civilians, both men and women, and you have a long, long history of rape as a legal procedure.
That doesn't make it fair, proper, or safe. Like slavery, it insults other people's bodies and takes away their control over their fate and especially their own bodies. But it's certainly a legally supported act in many societies, and is a fairly frequent behavior in the animal kingdom, so it's as natural as other slightly unusual sexual behaviors, including homosexuality, incest, polyamory, or doing it standing up or back to front.
Rape *is* a relationship. A nasty one, but like slavery, a relationship none the less.
Never assume otherwise, or you will be very confused by the slippery slope between normal human tensions and abuse.
It doessn't. Recent regulatory changes at the SEC, and promises to "review" the situation, have carefully avoided striking at the heart of the larger investment companies and groups that both engage in this sort of behavior, and have enough spare cash to fund politicians and arrange their own "reports" for the SEC on how disemboweling thihs sort of high-speed trading would "hinder the market".
It's insider trading with a high-tech cover. The data is not avaialble to ordinary investors in time for them to take keaningful action: the millisecond of having their servers right near the NySE overwhelm the reponse times of any ordinary trading entity and prevent their meaningful responses.
Don't blame the vendors. The specs for Vista were metamorphosing from day to day until Service Pack 1, and no vendor could predict which way the other vendors would sway things, so there was no _point_ for them in alpha testing. And don't forget the nightmare that was WinFS, which has corectly been discarded entirely. Shoving an ill-managed, demonstrably fragile, resource gobbling and impossible to repair database into the kernel's filesystem components was a bad idea. It's why Berkeley DB was never successfully integrated into ext2: it's a destabilizing approach and was deservedly discarded, although it wasted thousands of hours of vendor engineer time trying to integrate storage devices to support it.
The first issue is that you have to convince people that their business practices are wrong. This is not easy, and often requires lying through your teeth with statistics. Testing costs time and money and slows down releases. _Foolish_ testing, with lots of business case meetings and Powerpoint slides and expensive test configurations that don't actually test anything but demoware, is even more expensive and wasteful. The testing needs to actually prevent support calls, save engineering time re-fixing the same bugs, prevent support calls, and especially _help sales_. Ideally, they also help prevent liability: look up the phrase "always mount a scratch monkey" for the canonical story of failing to test a change.
The second issue sounds like a basic source control issue. It sounds like developers or engineers are reverting fixes after you've made them and committed them, and this should _never_ happen. Switching to a better source control process sounds vital to your issues, and may solve a lot of your issues without expensive test suites. Which source control suits your local programming styles is your own choice, but having a central trunk or repository that changes, and logging of changes, is committed to might at least help you cover your backside the next time this happens.
And the heat, water, and electricity must be "free" in your building.
2000 messages/month of "practially nothing" adds up, and I'm getting plenty of months like that when some "consultant" misconfigures my old, documented, robust alert system and just goes ahead and "turns on everything, to debug". Then everry single one of dozens or hundreds or even thousands of systems starts sending distinct alerts, because they've sidetracked my very careful hierarchy of "if this alert happens, it means the VPN is down: _wait_ before alerting for every remote server."
Given Hillary's accomplishments as an attorney, presidential committee leader, and secretary of state, what makes you think she'd be any more competent as a president?
She's intelligent and skilled, but not as a leader of a diverse group with different agendas. We saw that with her attempts at universal health care, and we're seeing it now with her wishy-wasy if not schizophrenic handling of Iraq, Afghanistan, Korea, and China.
No, she's too easy to trip up, especially in the debates. And given her beauty pageant history and modeling attempts, I'd unsurprised if there are some embarassing but verifiable photos of her awaiting publication if it looks like she stands a chance.
Do note that during the '08 election, she followed her script exactly. This may be because she was mishandled by McCain's advisors, but also may be because she can't work without a script and could be worse than Reagan that way.
You're less likely to get _any_ improvements. User and developer feedback, flavored with the information in the publicly available source code, have been tremendours sources of Linux and GPL software features and fixes. And one thing that I do as a developer is to publish my patches to the vendors, so that they can integrate them in their next release. (This happens several times a year for me: it's very gratifying, it saves me considerable time in setting up workarounds, and it looks very good on my annual performance reviews.)
Or, what is also very likely.
1) You buy _anything_ from no-name company.
2) Company goes under because they didn't make the incredible sums of money they told their venture capitalists they would make. (This is *very* common with portable device manufacturers.) Or becasue their batteries melt. Or because their manager embezzled the money. Or because they get bought up by another company that could not care less about their purchased company's previous owners.
3) In any case, with such a company, your device never had any support anyway: if they can't be bothered to follow the very modest requirements of the GPL, they doubtless had no support capacity anyway. I've actually seen this in manufacturing and software, and the weirdness companies companies go through to avoid having anyone actually take support calls, which cost time and money.
Consider GPL compliance a very good litmus for the device quality. If they can't be bothered to obey simple laws about copyright, what are they violating in terms of bettery recharger handling or basic physical manufacture quality?
I've met far too many programmers, barely half my age, who've already ruined their hands with poor keyboard technique. They've lost the ability to get into the actual code and have doomed themselves to cut&paste programming because their hands can no longer handle typing what they really need: they're forced to let the GUI do it for them, and the result is sometimes very poor code.
Where do you possibly derive this? Most murders and rapes are committed by family members: there's nothing like living that close to someone, especially someone under your physical care or control, to tempt abuse. Religion may ritualize it and set standards such as the child body changing of ear piercing, circumcision, or clitorectomy practiced by various cultures. But how many members of any genocidal army were genuinely religious? How many just followed orders and killed scapegoats?