Phasors are okay, and light sabers are cool, but a disruptor is where it's really at. There's just something about shooting the target and watching it glow for a couple of seconds before vaporizing into a cloud of neutrinos that's hard to beat.
When they remake Dirty Harry in 200 years, he'll be using the most powerful disruptor out there. "Being this is a UCG-9002, the most powerful disruptor in the universe, and it will vaporize your head clean off, you've got to ask yourself a question..."
Good idea if it helps to avoid blowing up non-combatants, and useful for knowing where to call in the 500 pound bomb if necessary.
As a general rule, it is always advisable to avoid barbequeing women and children who aren't involved in the fight if it's at all possible to do so. It's counterproductive and feeds the enemy's propaganda machine.
I find it unbelievable that the NSA hasn't developed a custom government-only Blackberry type of device for senior officials to use. All the functionality can be built into a custom firmware/hardware solution that is ultra-encrypted and archives everything to a secure server.
If they haven't, they should build something like this.
It does not make it worse than useless for all businesses. Some may be so tight on capital that license fees are the difference between profit and loss that they may well still take the risk. You may be thinking of large businesses with several layers of risk-adverse management, but many businesses are just above mom-and-pop size, with technically skilled owners and personnel who can get by without support. Perspective is everything.
Also, commercial support is available for most OSS projects.
I've released some of my code as LGPL libraries, as they may benefit someone else and possibly get me a little assistance testing and developing the code. It's nothing business critical, but does make developing some things a bit easier. But I don't do support for this code, either. My attitude is - "you have source" because it is only of use to other developers who should be fully capable of figuring it out.
"If the software is a key component of my business it's got to continue to be available." -- like, say, MS Access 95 that runs the client-end of a database and breaks on Access XP, and can't be changed because the ex-employee who developed it got hit by a train?
OSS is most certainly not there to reward "freeloaders" who want functionality and support for free.
This is just an attempt to use the courts as a weapon to protect a monopoly position. The tip of that weapon is an injunction delaying the public network while the private one is built, resulting in a "win" for the company regardless of the actual outcome of the lawsuit.
Really, it just amounts to a "hack" of the legal system. The process itself can be hijacked to delay competitors, or even bankrupt them outright through legal fees and other costs in the pre-trial parts of a case.
They know he'll be expelled, but that the Governor ( Palin) will appoint his successor to serve out the rest of the term.
It was basically a choice of "yes" or "no" to giving a Republican seat to the Democrats.
Everyone knows Stevens is going to prison. His reelection just serves as a placeholder for the person who's actually going to take the Senate seat in his stead.
I don't believe that the Governor can appoint herself to the post, so at least the Democrats don't have to worry about hearing the words "Senator Palin".
GPL authors generally do not want to put code out there to be used as a no-cost alternative to commercial development libraries and programs, while getting nothing in return.
Basically, the "license fee" for GPL code is that the person/company reselling it must give back changes and/or distribute source. And they must abide by any attribution demands as well.
Or negotiate a commercial use license. MySQL does that.
You may be able to run RDP across even the low speed links - choose the bare minimum screen resolution and color depth possible. It will still be pretty frustrating and slow, but you could use it with enough patience. Or you can run VNC, though I believe its performance will be less than RDP.
For CLI access, install an SSH server on the Windows box. If your code runs as a service, you can interface to it through a CLI client. It's some development work, but possible.
For power, I like APC's smart power strips. They support HTTP and SSH access.
Whatever solution I used, it would have to be run over an encrypted satellite link.
That's an outside group running that ad. Notice no "I approved this message" at the end.
All campaigns draw their share of asshats, who are sometimes organized asshats. Obama is a polarizing figure - either you love him or you don't for the most part, whereas McCain is more or less a "meh" figure. Palin, however, is polarizing.
It's still a bunch of melted (actually, vaporized) copper, but it's nowhere near 70 tons.
All the above assumes that the beam stays perfectly coherent and doesn't have any losses due to heating of surrounding material. In reality, the beam would rapidly diverge, and heat would begin to flow through the copper. Oh, also, ejected copper plasma would at some point begin to interfere with the beam itself before it reached the copper itself. This would rapidly de-focus the beam and absorb energy, so the plasma ejecta would get oh-my-god hot while shielding remaining copper from being damaged.
I noticed that here in Pittsburgh, we have a relatively new entrant into the DSL space (Cavtel) who are offering the maximum possible speeds(up to 8 Mb/s, depending on line quality) with no caps and no tiers and they advertise a price lower than Verizon's 3 Mb/s service. Basically, they set themselves up as a CLEC and have access to the last-mile copper and their own backbone (probably transit) links.
I wonder if the caps will make it profitable for more of this type of activity to take place? Could we see some alternative DSL providers open up shop?
I'd say the only regulation that would make sense WRT peering is to bring in one simple rule:
Any provider who sells Internet connectivity to end-users (individuals, companies, data centers) must divest themselves of any backbone business, and vice-versa. If we're going to "tier" the providers, then the top tier (transit providers) must only offer transit links to those selling the actual end-user connectivity. IE: providers must choose to be "wholesalers" or "retailers" and may not be both.
Or...
Any provider selling end-user connectivity must peer at no charge to any other provider selling the same.
(Note - just tossing out ideas here. I doubt either of those would be practical, but we have to start someplace.)
The elephant in the room right now is that a small group of Tier 1 providers have effectively formed a cartel that restrains trade in Internet bandwidth. Those in "the club" gain a huge cost savings over those forced to buy transit links, which are identical to the free peering links they provide each other.
In no other industry would such behavior be allowed.
The idea is to encourage new players to enter the market. More competition benefits the end customers, whereas a few large providers tend to act like a de-facto monopoly.
What about the numbnuts out there that use a Sawsall to open the damn things? I must admit to being tempted, but decided prudence mandated scissors instead.
Considering the uncertainty of where it will hit, what does the/. community think would be a good line to place on any of these occuring:
1. Debris Hits John McCain in the head? 2. Debris Hits John McCain AND Sarah Palin in the head? 3. Debris hits Barak Obama in the head? 4. Debris Hits Barak Obama AND Joe Biden in the head? 5. Debris Hits George Bush in the head? 6. Debris Hits Osama bin Laden in the head? 7. Debris hits nobody in the head? 8. Debris hits nobody's house? 9. Debris causes zero real damage to everything? 10. Who cares what we talk about on/. anyway?
The issue isn't "speed" so much as having the network gear participating in the traffic flow as an active partner.
For example, network vendors are rolling out gear that works at Layer 7 now, doing things like verification of XML Schemas, looking for XSS attacks, and sanitizing variables in HTTP POST requests. All of these really belong in the application itself.
Really, it doesn't matter that much where the functionality resides, but it sure seems like the approach is very similar to rolling out front-end processors (like the IBM 3270 days). Except now it's not so much to split processing tasks as much as to control what data reaches the hosts communicating across the network itself.
Humans are used because "true believers" are easily recruited and highly reliable, whereas electronics and the expertise to build a reliable remote control system isn't. Plus, any remote is subject to jamming and easily rendered ineffective. Plus, buying the servos and motion-control gear does leave a bit of a paper trail.
Plus, the press picks up far more readily on a suicide attack rather than a remote-controlled one. Suicide attacks give the impression of a "fighter" dying for a cause, wheras a remote attack is easily spun as "cowardly murdering bastards." (Note: even the suicide attackers are murdering bastards.) It's really hard to "spin" a remote-controlled attack on civillians as anything but cowardly murdering bastard type asshattery.
Slashdot Mirror
Phasors are okay, and light sabers are cool, but a disruptor is where it's really at. There's just something about shooting the target and watching it glow for a couple of seconds before vaporizing into a cloud of neutrinos that's hard to beat.
When they remake Dirty Harry in 200 years, he'll be using the most powerful disruptor out there. "Being this is a UCG-9002, the most powerful disruptor in the universe, and it will vaporize your head clean off, you've got to ask yourself a question..."
Good idea if it helps to avoid blowing up non-combatants, and useful for knowing where to call in the 500 pound bomb if necessary.
As a general rule, it is always advisable to avoid barbequeing women and children who aren't involved in the fight if it's at all possible to do so. It's counterproductive and feeds the enemy's propaganda machine.
I find it unbelievable that the NSA hasn't developed a custom government-only Blackberry type of device for senior officials to use. All the functionality can be built into a custom firmware/hardware solution that is ultra-encrypted and archives everything to a secure server.
If they haven't, they should build something like this.
The key is being in the right place at the right time with the right bullshit and the right ideas.
It does not make it worse than useless for all businesses. Some may be so tight on capital that license fees are the difference between profit and loss that they may well still take the risk. You may be thinking of large businesses with several layers of risk-adverse management, but many businesses are just above mom-and-pop size, with technically skilled owners and personnel who can get by without support. Perspective is everything.
Also, commercial support is available for most OSS projects.
I've released some of my code as LGPL libraries, as they may benefit someone else and possibly get me a little assistance testing and developing the code. It's nothing business critical, but does make developing some things a bit easier. But I don't do support for this code, either. My attitude is - "you have source" because it is only of use to other developers who should be fully capable of figuring it out.
"If the software is a key component of my business it's got to continue to be available." -- like, say, MS Access 95 that runs the client-end of a database and breaks on Access XP, and can't be changed because the ex-employee who developed it got hit by a train?
OSS is most certainly not there to reward "freeloaders" who want functionality and support for free.
This is just an attempt to use the courts as a weapon to protect a monopoly position. The tip of that weapon is an injunction delaying the public network while the private one is built, resulting in a "win" for the company regardless of the actual outcome of the lawsuit.
Really, it just amounts to a "hack" of the legal system. The process itself can be hijacked to delay competitors, or even bankrupt them outright through legal fees and other costs in the pre-trial parts of a case.
n/t
They know he'll be expelled, but that the Governor (
Palin) will appoint his successor to serve out the rest of the term.
It was basically a choice of "yes" or "no" to giving a Republican seat to the Democrats.
Everyone knows Stevens is going to prison. His reelection just serves as a placeholder for the person who's actually going to take the Senate seat in his stead.
I don't believe that the Governor can appoint herself to the post, so at least the Democrats don't have to worry about hearing the words "Senator Palin".
GPL authors generally do not want to put code out there to be used as a no-cost alternative to commercial development libraries and programs, while getting nothing in return.
Basically, the "license fee" for GPL code is that the person/company reselling it must give back changes and/or distribute source. And they must abide by any attribution demands as well.
Or negotiate a commercial use license. MySQL does that.
You may be able to run RDP across even the low speed links - choose the bare minimum screen resolution and color depth possible. It will still be pretty frustrating and slow, but you could use it with enough patience. Or you can run VNC, though I believe its performance will be less than RDP.
For CLI access, install an SSH server on the Windows box. If your code runs as a service, you can interface to it through a CLI client. It's some development work, but possible.
For power, I like APC's smart power strips. They support HTTP and SSH access.
Whatever solution I used, it would have to be run over an encrypted satellite link.
The GPL is pretty strict about any distribution requiring source being made available. Embedded devices are no exception.
Yep. Typos...
Multiply everything above by 10.
So, 7.348 Mg or 16.2 k pounds.
About 8 tons.
That's an outside group running that ad. Notice no "I approved this message" at the end.
All campaigns draw their share of asshats, who are sometimes organized asshats. Obama is a polarizing figure - either you love him or you don't for the most part, whereas McCain is more or less a "meh" figure. Palin, however, is polarizing.
Uh, some math errors exist in some of the parent posts.
A 1.5mm diameter beam that is 40 meters long has a volume given by:
V = pi * r^2 * d
If r and d are in cm, then:
V = pi * (0.15/2)^2 * 400
V = pi * 0.005625 * 400
V = 7.07 cm^3.
At 9 g/cm, this gives a mass of 63.2 grams.
If we're melting/vaporizing this much in 86 uS, that gives a rate of
63.2 / 0.000086 = 734,883.72 g/s (or 1,620.14 lb/s).
It's still a bunch of melted (actually, vaporized) copper, but it's nowhere near 70 tons.
All the above assumes that the beam stays perfectly coherent and doesn't have any losses due to heating of surrounding material. In reality, the beam would rapidly diverge, and heat would begin to flow through the copper. Oh, also, ejected copper plasma would at some point begin to interfere with the beam itself before it reached the copper itself. This would rapidly de-focus the beam and absorb energy, so the plasma ejecta would get oh-my-god hot while shielding remaining copper from being damaged.
We also have FIOS available here.
I noticed that here in Pittsburgh, we have a relatively new entrant into the DSL space (Cavtel) who are offering the maximum possible speeds(up to 8 Mb/s, depending on line quality) with no caps and no tiers and they advertise a price lower than Verizon's 3 Mb/s service. Basically, they set themselves up as a CLEC and have access to the last-mile copper and their own backbone (probably transit) links.
I wonder if the caps will make it profitable for more of this type of activity to take place? Could we see some alternative DSL providers open up shop?
I'd say the only regulation that would make sense WRT peering is to bring in one simple rule:
Any provider who sells Internet connectivity to end-users (individuals, companies, data centers) must divest themselves of any backbone business, and vice-versa. If we're going to "tier" the providers, then the top tier (transit providers) must only offer transit links to those selling the actual end-user connectivity. IE: providers must choose to be "wholesalers" or "retailers" and may not be both.
Or...
Any provider selling end-user connectivity must peer at no charge to any other provider selling the same.
(Note - just tossing out ideas here. I doubt either of those would be practical, but we have to start someplace.)
The elephant in the room right now is that a small group of Tier 1 providers have effectively formed a cartel that restrains trade in Internet bandwidth. Those in "the club" gain a huge cost savings over those forced to buy transit links, which are identical to the free peering links they provide each other.
In no other industry would such behavior be allowed.
The idea is to encourage new players to enter the market. More competition benefits the end customers, whereas a few large providers tend to act like a de-facto monopoly.
What about the numbnuts out there that use a Sawsall to open the damn things? I must admit to being tempted, but decided prudence mandated scissors instead.
Considering the uncertainty of where it will hit, what does the /. community think would be a good line to place on any of these occuring:
1. Debris Hits John McCain in the head? /. anyway?
2. Debris Hits John McCain AND Sarah Palin in the head?
3. Debris hits Barak Obama in the head?
4. Debris Hits Barak Obama AND Joe Biden in the head?
5. Debris Hits George Bush in the head?
6. Debris Hits Osama bin Laden in the head?
7. Debris hits nobody in the head?
8. Debris hits nobody's house?
9. Debris causes zero real damage to everything?
10. Who cares what we talk about on
Let the National Guard handle those... if they happen. *
Besides, why not just do it in 3D for really good realism? **
* Please let no riots happen!
** 3D is really cool
(Disclaimer: I like 3D so much, I built a camera.)
Gee - wouldn't that be more useful for the pr0n awards?
Or the HDTV shots of the riots when Obama loses?
You nailed it on the speed parameter.
The issue isn't "speed" so much as having the network gear participating in the traffic flow as an active partner.
For example, network vendors are rolling out gear that works at Layer 7 now, doing things like verification of XML Schemas, looking for XSS attacks, and sanitizing variables in HTTP POST requests. All of these really belong in the application itself.
Really, it doesn't matter that much where the functionality resides, but it sure seems like the approach is very similar to rolling out front-end processors (like the IBM 3270 days). Except now it's not so much to split processing tasks as much as to control what data reaches the hosts communicating across the network itself.
If they REALLY hate it that much, just turn off the routers until the .gov relents.
Humans are used because "true believers" are easily recruited and highly reliable, whereas electronics and the expertise to build a reliable remote control system isn't. Plus, any remote is subject to jamming and easily rendered ineffective. Plus, buying the servos and motion-control gear does leave a bit of a paper trail.
Plus, the press picks up far more readily on a suicide attack rather than a remote-controlled one. Suicide attacks give the impression of a "fighter" dying for a cause, wheras a remote attack is easily spun as "cowardly murdering bastards." (Note: even the suicide attackers are murdering bastards.) It's really hard to "spin" a remote-controlled attack on civillians as anything but cowardly murdering bastard type asshattery.