I'm assuming the system is electric, but it could only meet the "no CO2" if the electric power is nuclear, hydro, solar, etc... If it's traditional electric power, it's just moving the source of the CO2 and perhaps the efficiency.
First and foremost... ask if you can bring a radio onboard before even thinking about any of this. Their radio operator will probably notice your operations.
Second, the Sailmail service doesn't even require an amateur radio license. It works over commercial frequencies.
You're still trying to weasel in some "lessened severity" argument completely based on having a lower market share. A piece of crap code is a piece of crap code, whether 20 people or 20 million people run it. Especially if the one with 20 people is trying to tout itself as being more secure.
Lower Market Share = Less Vulnerable is a nice sidestepping attempt, but isn't rooted in the reality of the actual severity of the System A Bug A vs System B Bug B analysis.
"Oh, but when our stuff breaks (just as badly as BigCorp's stuff), it's better... because it doesn't affect as many people. Why? Because we suck and can't sell as many as BigCorp. But remember: We're Better."
If there was a car that had a critical flaw and exploded into flames if you hit it from behind hard enough.... BUT only 0.03% of Americans drove the car... then the NHTSA shouldn't really consider that a 'critical' flaw, it shouldn't be viewed as 'badly' as the same type of flaw in a Honda Accord (driven by far more people)...
All because the market share of this explosion-prone car is low?
That's some whacked-out thinking right there. Just because the company can't get market share doesn't lessen the potential (or real) impact of the vulnerability. I don't care if that's Apple or Nortel or Mythic Entertainment.
A kernel developer can choose to flag or not to flag his work as "GPLONLY", which means that if you want to use his work, whatever is 'calling' his work AND EVERYTHING DOWN THE CHAIN must be GPL pristine. Linus and the kernel itself is simply providing the enforcement mechanism.
The key point here is that each developer may choose to set or not set that GPLONLY flag. Having someone like ndiswrapper come forth and basically whine and cry that the system is unfair and that they should be allowed to bend or break the rules is idiotic. This is simply enforcing the wishes of the individual developers that have asked that their contributions be flagged "GPLONLY".
Don't like it? Don't call that portion of the kernel, or write your own section in replacement that isn't flagged GPLONLY and manage to get it included in the kernel... but don't trample the wishes of the developer that wrote the code you're calling.
"That doesn't change the fact that tangible personal property as a whole is not subject to property taxes (or anything structurally similar) in most US jurisdictions. Nor does it change that merely waving one's hand at a wikipedia article on "ad valorem" taxes fails to rebut the preceding fact."
Nor does your claim of knowledge about 'most US jurisdictions' have any merit whatsoever without at least some evidence. I at least went to the effort of posting something more than unsubstantiated opinion. You on the other hand...
Might want to talk to various state and local governments and their DMV departments. A quick search on Google for "ad valorem vehicle tax" comes up with links to government websites in Mississippi, Georgia, North Carolina, New Mexico...
I know for a fact that in various counties in Alabama for instance, every year vehicle owners pay a tax (part of their vehicle license that) is based on the value of the vehicle. This tax is paid each and every year the car is licensed, not just the first time when it's purchased or transferred to a new owner.
For example:
"What is ad valorem tax? Ad valorem tax is the property tax you pay annually on your vehicle. How is ad valorem tax collected? Property taxes on motor vehicles are assessed and collected forward on a current basis. Property taxes on motor vehicles are due and payable on:
the first day of the renewal month of the owner
the date the motor vehicle enters the State
the date the motor vehicle is removed from the inventory of a dealer
or the date on which the motor vehicle is otherwise determined to be taxable, whichever comes first."
It also fits in the unused boot sectors of a hard drive, but the point was that there are fewer sectors and less space to play with on a floppy... so maybe I should have worded it that it *even* fits in the unused boot sectors of a floppy or hard drive.
Last I checked, his bootloader could load nearly any OS for x86. Doing all of that in a few KILOBYTES of otherwise unused space would be just about impossible with anything other that assembly.
I guess they're forgetting about things like optimized device drivers, true performance-oriented embedded systems architectures, microcode segments, and anything to do with hardware development.
Perfect examples - add yours here
on
GAO Report Slams FCC
·
· Score: 2, Insightful
Verizon FIOS and the 'disconnecting copper' claims. FCC looks the other way.
Broadband over Power Line and all the resultant RF interference... FCC manipulates measurement techniques, breaks it's own rules... Even international organizations say BPL causes excessive RF interference. FCC looks the other way. FCC brought to court.
If a high-school kid was a massive warez junkie and managed to accumulate 1.5 million dollars worth of pirated software, would the IPI consider that 1.5 million dollars worth of lost sales... from a kid with a maximum $2K-$3K a year income?
Doesn't seem to me they're looking at actual buying potential of the 'offender'... just theoretical maximum revenue lost by the producer.
If Cisco were the problem, everyone would be switching to Juniper. Or Extreme. Or Foundry. Or some other vendor in a long list. (Many are switching, but not too many for price, especially in this part of the market.)
Is it worth what they charge? Hard to say, but the market must say yes, since people keep buying. And yeah HT and PCI-E are cheap, but no one that I know of can build anything even closely resembling PC-grade electronics or using PC-class interfaces and keep up with the traffic.
We're talking about lots of custom ASICs just to start. I would guess that if PCI-E were enough to handle the load, they'd use it. Last thing I knew of that Cisco made as a router that's still around that uses something similar to the PC industry is the Cisco 7200 router. The midplane (split backplane) is two PCI backplanes. Still going strong, but that device is now a midrange WAN edge good up to about OC3 speeds, good for fanning OC3s out into DS3s or smaller. Not good for multi-gigabit heavy lifting.
Wanna make a few billion? Come up with a design of a network device that handles online insertion and removal of interface cards, that handles the same or higher levels of traffic, that is based on PC hardware as much as possible, that runs an OS with similar capabilities, and that costs less to develop, build and maintain both as a producer and for the consumer.
The US DSL/cable/etc business model is built on a certain amount of oversubscription, just like (nearly) every network out there. I have worked for several companies, up to top 10 of the Fortune 500, and not a single one of them had a network that wasn't oversubscribed to a certain degree... even on the LAN (which is where it's the cheapest).
Those of you that work in a corporate environment with any density (>20 users on a floor, more than one floor)... If you've got a gigabit LAN, go ask your network guy if they have a 10-gig uplink for every 10 ports on the floor.
. . .
After he stops laughing and realizes you're serious, ask him why they are running an oversubscribed network. If he's on the design side, he'll end up telling you that you don't build a network for that level of traffic if it simply doesn't use it (most don't). The most likely place you're going to see a fully non-oversubscribed network is one that supports a supercomputer with many nodes. Even then you might see some.
It's just not economically feasible to build non-oversubscribed networks. Any of you know how much a card for a Cisco GSR that has just two OC-192 intermediate-reach ports on it is? MSRP is $585,000.
$585K for two 10 gigabit intermediate reach ports. And to build a non-oversubscribed network for a small community with say 2000 users on 8-meg cable connections that cost $60 a month. Gotta pay for the cable plant itself (to a certain degree), the fiber to link the customer-facing nodes (how much it cost to dig/hang/lay the fiber), the routers in the customer-facing nodes, the cards in the routers in those nodes (more bandwidth = higher cost cards), the distribution routers that link all the customer nodes together (and their cards), core routers with higher-speed interfaces to tie it all together if you have any decent number of distribution nodes (and their cards), peering routers to your upstream bandwidth provider (and cards), maintenance on every router/switch (which runs ~20-30% yearly over and above the purchase price), spares of a few of your most commonly-failing equipment, datacenter space, AC, cooling, engineering staff costs, field maintenance staff costs, systems administrators staff costs, 24x7 NOC staff costs, 24x7 helpdesk costs, multiple layers of management (each of those fields has to have management in an organization of any size), training costs to keep up on the latest developments, staff turnover costs, taxes... and that's before we've paid for one bit of peering bandwidth or even thought about making a profit - or considered what Mother Nature, backhoes, or out of control drunk drivers do to the equipment and fiber that make up the customer-facing network that sits in equipment sheds on concrete pads on the side of the road. And don't forget to add another 100% or so to all of those equipment costs, for redundancy. Don't want the whole east side of the city down because one port/device/fiber failed, do you?
There's a lot more than just a couple of Linksys gig switches and some cable RF converters that make up a cablemodem network. There's more than just a card in a phone switch that makes up a DSL network. The gear is very expensive, typically because there's lots of R&D that must go into the boxes to make them able to do what they do without having horrendous failure rates (which still happens sometimes).
Yes they are... in hardware. With custom ASICs. With tables set aside for wirespeed port lookups.
It's not that the hardware can't do it, it's that there is 'handled at wirespeed by custom hardware' and 'handled at (much) slower than wirespeed by software'.
Until someone goes to the trouble to develop routines and hardware to run it on that can handle that deep of an inspection and have it only drop the 'offending' packets, and have it do it at wirespeed, then your only challenge is to get it included in major pieces of the infrastructure that make up the internet.
There are many many horror stories out there from Tivo 3 and Tivo HD users about cable installers making 3, 4, 5 or more trips to get them working, or going through stacks of cards just to get two to work... The cablecard setup procedure *should* be as simple and seamless as a DirecTV authorization or a cable box authorization, but something's broken either in the process or the architecture.
To reduce or eliminate computer crime, first step is to make illegal the tools to determine whether or not you are vulnerable, and tools that find unknown vulnerabilities.
Makes you wonder if any of the vulnerability scanner companies will ever be able to do business in Germany again. I guess every company that has such a scanner has to now turn the devices over to the state?
Do a search for mirrors of LAYO.COM and you'll find that a gentleman built a test device that used aluminum and H2O, performing the same oxidation and releasing hydrogen. He even submitted the device to BMW for testing, to which their only complaint/question was how to filter the aluminum oxide powder.
Over 10+ years doing networking at various levels up to "Network Architect", I can honestly say that I have spent more time doing network-layer application debugging than nearly anything else... hours and hours with a sniffer, meetings with people trying to determine which piece talks where, what it does with the data.
Latest example? Doing replacements of user-facing switches around the same time as the PC group is upgrading machines and (finally) deploying XP SP2. Suddenly, I get pulled in on a ticket where "the mail is slow". It takes up to an hour for someone to get an email *from* the inside *to* the inside, but the issue can't be replicated on demand.
Nearly two weeks later, many impromptu meetings later, we find a user who is reporting the problem right now. An obscure bug combining Outlook 2000 and the XP SP2 firewall that prevents the periodic back-and-forth between the server and the client.
But, of course... it was a "network problem" from the beginning... until we debugged their app for them and showed them what it was doing. Plus a link to the bug on Microsoft's website.
Bleh.
You can't keep new code from getting issued from network hardware manufacturers (unless of course you like running vulnerable software), you can't keep applications from using more and more bandwidth, you can't keep security requirements from constantly changing, and you can't get away with "I'm sorry, the network won't support that, because the server group told us to stop making changes.
In most cases, a network engineer is only trying to keep ahead of the ever-present crush of demands on the network of uptime, survivability, resilience, growth, speed, support, and status/health reporting to management.
Slashdot Mirror
They might have a way to block Skype, or it could just be a large amount of jitter from you to the Skype gateway you were trying to reach.
I'm assuming the system is electric, but it could only meet the "no CO2" if the electric power is nuclear, hydro, solar, etc... If it's traditional electric power, it's just moving the source of the CO2 and perhaps the efficiency.
First and foremost... ask if you can bring a radio onboard before even thinking about any of this. Their radio operator will probably notice your operations.
Second, the Sailmail service doesn't even require an amateur radio license. It works over commercial frequencies.
http://www.sailmail.com/smprimer.htm#Getting%20Connected%20via%20Radio
Third, the modem required for Sailmail is several hundred dollars, not counting the radio and the antenna (another thousand plus)...
"Blizzard understands end game progression"
Yeah, only if you like standing around looking for groups for hours and hours on end between "Tier 1" 5-mans and everything else.
You're still trying to weasel in some "lessened severity" argument completely based on having a lower market share. A piece of crap code is a piece of crap code, whether 20 people or 20 million people run it. Especially if the one with 20 people is trying to tout itself as being more secure.
Lower Market Share = Less Vulnerable is a nice sidestepping attempt, but isn't rooted in the reality of the actual severity of the System A Bug A vs System B Bug B analysis.
"Oh, but when our stuff breaks (just as badly as BigCorp's stuff), it's better... because it doesn't affect as many people. Why? Because we suck and can't sell as many as BigCorp. But remember: We're Better."
So to use an analogy...
If there was a car that had a critical flaw and exploded into flames if you hit it from behind hard enough.... BUT only 0.03% of Americans drove the car... then the NHTSA shouldn't really consider that a 'critical' flaw, it shouldn't be viewed as 'badly' as the same type of flaw in a Honda Accord (driven by far more people)...
All because the market share of this explosion-prone car is low?
That's some whacked-out thinking right there. Just because the company can't get market share doesn't lessen the potential (or real) impact of the vulnerability. I don't care if that's Apple or Nortel or Mythic Entertainment.
What I (as a non-developer) got out of this was:
A kernel developer can choose to flag or not to flag his work as "GPLONLY", which means that if you want to use his work, whatever is 'calling' his work AND EVERYTHING DOWN THE CHAIN must be GPL pristine. Linus and the kernel itself is simply providing the enforcement mechanism.
The key point here is that each developer may choose to set or not set that GPLONLY flag. Having someone like ndiswrapper come forth and basically whine and cry that the system is unfair and that they should be allowed to bend or break the rules is idiotic. This is simply enforcing the wishes of the individual developers that have asked that their contributions be flagged "GPLONLY".
Don't like it? Don't call that portion of the kernel, or write your own section in replacement that isn't flagged GPLONLY and manage to get it included in the kernel... but don't trample the wishes of the developer that wrote the code you're calling.
why my wife came home today with an application for the space program... and my name was already filled out at the top.
"That doesn't change the fact that tangible personal property as a whole is not subject to property taxes (or anything structurally similar) in most US jurisdictions. Nor does it change that merely waving one's hand at a wikipedia article on "ad valorem" taxes fails to rebut the preceding fact."
Nor does your claim of knowledge about 'most US jurisdictions' have any merit whatsoever without at least some evidence. I at least went to the effort of posting something more than unsubstantiated opinion. You on the other hand...
Might want to talk to various state and local governments and their DMV departments. A quick search on Google for "ad valorem vehicle tax" comes up with links to government websites in Mississippi, Georgia, North Carolina, New Mexico...
I know for a fact that in various counties in Alabama for instance, every year vehicle owners pay a tax (part of their vehicle license that) is based on the value of the vehicle. This tax is paid each and every year the car is licensed, not just the first time when it's purchased or transferred to a new owner.
For example:
"What is ad valorem tax?
Ad valorem tax is the property tax you pay annually on your vehicle.
How is ad valorem tax collected?
Property taxes on motor vehicles are assessed and collected forward on a
current basis.
Property taxes on motor vehicles are due and payable on:
the first day of the renewal month of the owner
the date the motor vehicle enters the State
the date the motor vehicle is removed from the inventory of a dealer
or the date on which the motor vehicle is otherwise determined to be
taxable, whichever comes first."
From http://www.licensemobile.com/forms/Wrongcounty.pdf
Ad valorem taxes, anyone?
http://en.wikipedia.org/wiki/Ad_valorem/
"When you can write a bootloader that fits in the unused sectors on a floppy disc" ... or hard disc. Geez, +1 for not even visiting TFsite.
It also fits in the unused boot sectors of a hard drive, but the point was that there are fewer sectors and less space to play with on a floppy... so maybe I should have worded it that it *even* fits in the unused boot sectors of a floppy or hard drive.
Last I checked, his bootloader could load nearly any OS for x86. Doing all of that in a few KILOBYTES of otherwise unused space would be just about impossible with anything other that assembly.
When you can write a bootloader that fits in the unused sectors on a floppy disc using Java or C++, come talk to me and I'll be impressed. Until then...
I guess they're forgetting about things like optimized device drivers, true performance-oriented embedded systems architectures, microcode segments, and anything to do with hardware development.
Verizon FIOS and the 'disconnecting copper' claims. FCC looks the other way.
Broadband over Power Line and all the resultant RF interference... FCC manipulates measurement techniques, breaks it's own rules... Even international organizations say BPL causes excessive RF interference. FCC looks the other way. FCC brought to court.
If a high-school kid was a massive warez junkie and managed to accumulate 1.5 million dollars worth of pirated software, would the IPI consider that 1.5 million dollars worth of lost sales... from a kid with a maximum $2K-$3K a year income?
Doesn't seem to me they're looking at actual buying potential of the 'offender'... just theoretical maximum revenue lost by the producer.
If Cisco were the problem, everyone would be switching to Juniper. Or Extreme. Or Foundry. Or some other vendor in a long list. (Many are switching, but not too many for price, especially in this part of the market.)
Is it worth what they charge? Hard to say, but the market must say yes, since people keep buying. And yeah HT and PCI-E are cheap, but no one that I know of can build anything even closely resembling PC-grade electronics or using PC-class interfaces and keep up with the traffic.
We're talking about lots of custom ASICs just to start. I would guess that if PCI-E were enough to handle the load, they'd use it. Last thing I knew of that Cisco made as a router that's still around that uses something similar to the PC industry is the Cisco 7200 router. The midplane (split backplane) is two PCI backplanes. Still going strong, but that device is now a midrange WAN edge good up to about OC3 speeds, good for fanning OC3s out into DS3s or smaller. Not good for multi-gigabit heavy lifting.
Wanna make a few billion? Come up with a design of a network device that handles online insertion and removal of interface cards, that handles the same or higher levels of traffic, that is based on PC hardware as much as possible, that runs an OS with similar capabilities, and that costs less to develop, build and maintain both as a producer and for the consumer.
The US DSL/cable/etc business model is built on a certain amount of oversubscription, just like (nearly) every network out there. I have worked for several companies, up to top 10 of the Fortune 500, and not a single one of them had a network that wasn't oversubscribed to a certain degree... even on the LAN (which is where it's the cheapest).
Those of you that work in a corporate environment with any density (>20 users on a floor, more than one floor)... If you've got a gigabit LAN, go ask your network guy if they have a 10-gig uplink for every 10 ports on the floor.
.
.
.
After he stops laughing and realizes you're serious, ask him why they are running an oversubscribed network. If he's on the design side, he'll end up telling you that you don't build a network for that level of traffic if it simply doesn't use it (most don't). The most likely place you're going to see a fully non-oversubscribed network is one that supports a supercomputer with many nodes. Even then you might see some.
It's just not economically feasible to build non-oversubscribed networks. Any of you know how much a card for a Cisco GSR that has just two OC-192 intermediate-reach ports on it is? MSRP is $585,000.
$585K for two 10 gigabit intermediate reach ports. And to build a non-oversubscribed network for a small community with say 2000 users on 8-meg cable connections that cost $60 a month. Gotta pay for the cable plant itself (to a certain degree), the fiber to link the customer-facing nodes (how much it cost to dig/hang/lay the fiber), the routers in the customer-facing nodes, the cards in the routers in those nodes (more bandwidth = higher cost cards), the distribution routers that link all the customer nodes together (and their cards), core routers with higher-speed interfaces to tie it all together if you have any decent number of distribution nodes (and their cards), peering routers to your upstream bandwidth provider (and cards), maintenance on every router/switch (which runs ~20-30% yearly over and above the purchase price), spares of a few of your most commonly-failing equipment, datacenter space, AC, cooling, engineering staff costs, field maintenance staff costs, systems administrators staff costs, 24x7 NOC staff costs, 24x7 helpdesk costs, multiple layers of management (each of those fields has to have management in an organization of any size), training costs to keep up on the latest developments, staff turnover costs, taxes... and that's before we've paid for one bit of peering bandwidth or even thought about making a profit - or considered what Mother Nature, backhoes, or out of control drunk drivers do to the equipment and fiber that make up the customer-facing network that sits in equipment sheds on concrete pads on the side of the road. And don't forget to add another 100% or so to all of those equipment costs, for redundancy. Don't want the whole east side of the city down because one port/device/fiber failed, do you?
There's a lot more than just a couple of Linksys gig switches and some cable RF converters that make up a cablemodem network. There's more than just a card in a phone switch that makes up a DSL network. The gear is very expensive, typically because there's lots of R&D that must go into the boxes to make them able to do what they do without having horrendous failure rates (which still happens sometimes).
Yes they are... in hardware. With custom ASICs. With tables set aside for wirespeed port lookups.
It's not that the hardware can't do it, it's that there is 'handled at wirespeed by custom hardware' and 'handled at (much) slower than wirespeed by software'.
Until someone goes to the trouble to develop routines and hardware to run it on that can handle that deep of an inspection and have it only drop the 'offending' packets, and have it do it at wirespeed, then your only challenge is to get it included in major pieces of the infrastructure that make up the internet.
There are many many horror stories out there from Tivo 3 and Tivo HD users about cable installers making 3, 4, 5 or more trips to get them working, or going through stacks of cards just to get two to work... The cablecard setup procedure *should* be as simple and seamless as a DirecTV authorization or a cable box authorization, but something's broken either in the process or the architecture.
To reduce or eliminate computer crime, first step is to make illegal the tools to determine whether or not you are vulnerable, and tools that find unknown vulnerabilities.
Makes you wonder if any of the vulnerability scanner companies will ever be able to do business in Germany again. I guess every company that has such a scanner has to now turn the devices over to the state?
Their HR20 receiver appears to use linux, yet nothing that even looks like it complies with the GPL...
Do a search for mirrors of LAYO.COM and you'll find that a gentleman built a test device that used aluminum and H2O, performing the same oxidation and releasing hydrogen. He even submitted the device to BMW for testing, to which their only complaint/question was how to filter the aluminum oxide powder.
Over 10+ years doing networking at various levels up to "Network Architect", I can honestly say that I have spent more time doing network-layer application debugging than nearly anything else... hours and hours with a sniffer, meetings with people trying to determine which piece talks where, what it does with the data.
Latest example? Doing replacements of user-facing switches around the same time as the PC group is upgrading machines and (finally) deploying XP SP2. Suddenly, I get pulled in on a ticket where "the mail is slow". It takes up to an hour for someone to get an email *from* the inside *to* the inside, but the issue can't be replicated on demand.
Nearly two weeks later, many impromptu meetings later, we find a user who is reporting the problem right now. An obscure bug combining Outlook 2000 and the XP SP2 firewall that prevents the periodic back-and-forth between the server and the client.
But, of course... it was a "network problem" from the beginning... until we debugged their app for them and showed them what it was doing. Plus a link to the bug on Microsoft's website.
Bleh.
You can't keep new code from getting issued from network hardware manufacturers (unless of course you like running vulnerable software), you can't keep applications from using more and more bandwidth, you can't keep security requirements from constantly changing, and you can't get away with "I'm sorry, the network won't support that, because the server group told us to stop making changes.
In most cases, a network engineer is only trying to keep ahead of the ever-present crush of demands on the network of uptime, survivability, resilience, growth, speed, support, and status/health reporting to management.