Actually, Philips, who is the owner of the CD trademarks, have explicitly forbidden their use in conjunction with CDs with broken ECC, which is how the DRM works.
It doesn't just prevent copies, it also makes sure your "CD" is toast as soon as it get a minor scratch.
In short, breeder reactors need an external neutron source for sustaining fission. This is because U-238 fission only releases one neutron, where U-235 releases two which is needed to keep a chain reaction going.
That's wrong on multiple counts. U-238 isn't fissile; it absorbs neutrons to form U-239, which beta-decays to Pu-239 fairly rapidly. U-233, U-235 or Pu-239 fission generally produce multiple neutrons per reaction, although of course the break-even point is higher (2) than for pure fission (1). This means that for a critical chain reaction, a much higher neutron flux needs to be maintained; however, there is no reason one can't build a critical U-238- or Th-232-fuelled breeder, meaning no external neutron source.
20 years ago, it was explained to me that the reason European telephone companies didn't issue itemized bills except by explicit customer request was that telephone billing records had been used by Gestapo after invading other countries to figure out who to eliminate as possible "security threats" -- if X was suspected of being involved with the resistance, and Y had called X some time before the invasion, X and Y would both find themselves in a box car pretty soon.
It wasn't just that the data wasn't retained, the data was never even collected unless you requested it -- otherwise the only billing information that would be kept was a running counter.
Today, the supposedly-democratic countries want to use surveillance that would have given Gestapo and Stasi wet dreams; it's probably no coincidence that the prime ministers in the countries that have pushed the most (UK and Sweden) have been ones acting like power is a God-given right to them personally.
Actually, this chip is the same chip that they've been pushing for years for Microsoft's DRM stuff (Palladium.) Yet another attempt at making it sound like you're benefitting, instead of getting raked over the coals.
(...) It becomes clear that TCP can not utilize the full bandwidth because after having transmitted a window of data, it must wait until the acknowledges come back from the receiver. Because the delay is the same as on the normal speed link, there is a long pause between sending the last segment of the window until a new window is opened by the acknowledments.
You realize that that article talks about issues that had been long since solved by 1996, and list the solutions to them? In the case of the particular quote, the TCP Window Scale Option.
There are a number of networking enhancements that can't be done because the port number is encoded in a different part of the packet -- and not in every packet! -- than the IP address.
Going to an endpoint model means, of course, that a single computer would claim a netblock, not a single "IP address". Consider an IPv4 where there there are no port numbers, addresses are 48 bits, and each computer claim a/32 by default. The advantage is that you don't have to use a different lookup scheme and syntax if you're running 300 web servers on your one host as opposed to, say, web, ssh etc. Some of that is trying to happen with SRV DNS records, but it's poorly supported at best.
Also, I never understood why IPv4 wasn't just a subset of IPv6? Why can't my existing IPv4 addresses also be IPv6 addresses with a standard prefix? Maybe this has changed, but when IPv6 came out it looked like that wasn't part of it.
They are, the prefix is ffff::/96. In addition, there is 6to4, which lets you use your IPv4 address as a 48-bit IPv6 prefix, 2002:<IPv4 address>/48.
The problem is... who will deploy the first IPv4-unreachable Internet service?
NAT and firewalling are completely separate things. Since they're done at network boundaries, they are usually combined in one device, but they don't have to be.
NAT is a pretty bad thing. Unfortunately the IPv6 people haven't considered the requirements for managing that large of an address space except by hierarchy (which breaks as soon as you want to have a backup link to another ISP), so I fear we'll still have to have NAT in an IPv6 world.
Cisco is probably one of the companies responsible for IPv6 being such a mess it is. The IP router vendors, led by Cisco, pushed for as few changes as possible over IPv4 in order to leverage expertise and be ready for deployment quickly. So far, so good. It's lifespan (until another switchover would be needed) was estimated at 30 years; this is roughly how long IPv4 has lasted since it's predecessor, NCP, was retired.
However, everyone involved completely underestimated the cost of switchover and overestimated its rate of adoption. This ultimately means that IPv6 is not enough of an advancement to justify its deployment costs. The end result is that IPv6 is already one-quarter through its estimated 30-year lifespan and it isn't even widely deployed yet.
I suspect that what we need is an IPv7 that would include:
No fixed size address space limit.
Removal of the arbitrary distinction of hosts and ports in favour of a unified end point specifier.
Routing assistance built into the transport protocols, to augment the current AS system.
If we start now, this might be deployable by 2020 or so...:-/
IPv6 supports network migration quite easilly. Basically the idea is that you change your prefix but leave the rest of the address the same. Since you had a clue when you set up the network (right?:), all your addressing is done through DNS and your machines are configured by DHCPv6 or the native IPv6 router discovery protocol (which is part of the IPv6 stack), so just changing the prefix on your router and in DNS will cause your entire network to migrate over to the new network automagically.
... and it drops all your connections in the process. Had the protocol had proper abstraction between endpoints and routing paths, this would not be a problem. Unfortunately the router vendors pushed for IPv6 to be as similar to IPv4 as possible, which meant lots of baggage, which we only now are learning how to deal with.
There is another aspect to this. Memory is getting to the point where a router can handle the entire IPv4 address space as a linear table, which eliminates a huge bunch of tricks that Cisco has made a business from, lowering the barrier to entry. Cisco needs IPv6 to take off in the core Internet, in order to keep out competition.
Actually, you don't even need the ISS. All you need is a drop tower with vacuum inside. Any object in free fall is in zero gee. This technique is commonly used, on Earth, to manufacture small, cheap metal spheres.
What it really comes down to is that carriage, whether or not it is DSL, Cable, WiMax or whatever, needs to be separated from connectivity to the public internet, which are the two services that are bundled together when one buys from an ISP. This is equivalent to being forced to buy your cell phone company's hideously expensive international long distance service, when you can have your pick of international carriers calling from your home phone. Otherwise, say goodbye to being able to get static IP addresses or other useful stuff, and say hello to port blocking and intrusive monitoring.
Of course, with the current FCC, guess which way it's going. Pretty soon we're back in the bad old days of monopoly carriers.
According to bc(1) with scale cranked up, exp(pi*sqrt(163)) seems to evaluate to 262537412640768743.999999999999250072597198185 6888 79353856337336990862707537410378210647910118607312 951181346186064504193083887949753864...
(Note: the mentioned William Della Croce is someone who fraudulently attempted to register Linux as a trademark; he got sued and transferred the trademark to Linus as part of settling the lawsuit.)
Typed Drawing Word Mark LINUX Goods and Services IC 009. US 021 023 026 036 038. G & S: computer operating system software to facilitate computer use and operation. FIRST USE: 19940802. FIRST USE IN COMMERCE: 19940802 Mark Drawing Code (1) TYPED DRAWING Serial Number 74560867 Filing Date August 15, 1994 Current Filing Basis 1A Original Filing Basis 1A Published for Opposition June 13, 1995 Change In Registration CHANGE IN REGISTRATION HAS OCCURRED Registration Number 1916230 Registration Date September 5, 1995 Owner (REGISTRANT) Croce, William R. Della, Jr. INDIVIDUAL UNITED STATES 33 Snow Hill St. Boston MASSACHUSETTS 02113
(LAST LISTED OWNER) TORVALDS, LINUS INDIVIDUAL Assignee of FINLAND 5774 CANNES PLACE SAN JOSE CALIFORNIA 95138 Assignment Recorded ASSIGNMENT RECORDED Attorney of Record ROBERT T. DAUNT Type of Mark TRADEMARK Register PRINCIPAL Affidavit Text SECT 15. SECT 8 (6-YR). Live/Dead Indicator LIVE
If you're really worried about it, you can put it in just about any compound which contains hydrogen, and it will still be radioactive, just not a gas. Combine it with oxygen (ditritium oxide) and you have superheavy radioactive water - unfortunately it's 2.5 times as heavy as the constitutent tritium, and it will give off monatomic oxygen as the tritium decays, which is highly corrosive.
Well, tritium is a beta emitter, which probably is a good thing... means the damage isn't going to be as focused on the inner surface of the lungs as for an alpha emitter (beta has larger penetration depth.)
Radon is in many ways the worst case; it's a heavy gas (pools around, stays in your lungs after inhalation) which quickly decays into a chain of very active alpha emitters; in fact, some of the most active in the whole uranium decay chain.
Slashdot Mirror
Actually, Philips, who is the owner of the CD trademarks, have explicitly forbidden their use in conjunction with CDs with broken ECC, which is how the DRM works.
It doesn't just prevent copies, it also makes sure your "CD" is toast as soon as it get a minor scratch.
That's wrong on multiple counts. U-238 isn't fissile; it absorbs neutrons to form U-239, which beta-decays to Pu-239 fairly rapidly. U-233, U-235 or Pu-239 fission generally produce multiple neutrons per reaction, although of course the break-even point is higher (2) than for pure fission (1). This means that for a critical chain reaction, a much higher neutron flux needs to be maintained; however, there is no reason one can't build a critical U-238- or Th-232-fuelled breeder, meaning no external neutron source.
You've never been to Iceland, have you? Distances in Iceland are pretty huge, at least once you get out of the rather miniscule towns.
In this case you get Sony versus Microsoft, not Sony versus Google.
It wasn't just that the data wasn't retained, the data was never even collected unless you requested it -- otherwise the only billing information that would be kept was a running counter.
Today, the supposedly-democratic countries want to use surveillance that would have given Gestapo and Stasi wet dreams; it's probably no coincidence that the prime ministers in the countries that have pushed the most (UK and Sweden) have been ones acting like power is a God-given right to them personally.
Actually, this chip is the same chip that they've been pushing for years for Microsoft's DRM stuff (Palladium.) Yet another attempt at making it sound like you're benefitting, instead of getting raked over the coals.
You realize that that article talks about issues that had been long since solved by 1996, and list the solutions to them? In the case of the particular quote, the TCP Window Scale Option.
There are a number of networking enhancements that can't be done because the port number is encoded in a different part of the packet -- and not in every packet! -- than the IP address.
/32 by default. The advantage is that you don't have to use a different lookup scheme and syntax if you're running 300 web servers on your one host as opposed to, say, web, ssh etc. Some of that is trying to happen with SRV DNS records, but it's poorly supported at best.
Going to an endpoint model means, of course, that a single computer would claim a netblock, not a single "IP address". Consider an IPv4 where there there are no port numbers, addresses are 48 bits, and each computer claim a
They are, the prefix is ffff::/96. In addition, there is 6to4, which lets you use your IPv4 address as a 48-bit IPv6 prefix, 2002:<IPv4 address>/48.
The problem is... who will deploy the first IPv4-unreachable Internet service?
NAT is a pretty bad thing. Unfortunately the IPv6 people haven't considered the requirements for managing that large of an address space except by hierarchy (which breaks as soon as you want to have a backup link to another ISP), so I fear we'll still have to have NAT in an IPv6 world.
You know that one of the working assumptions of IPv6 is that your ISP can change your netblock prefix at any time, right?
However, everyone involved completely underestimated the cost of switchover and overestimated its rate of adoption. This ultimately means that IPv6 is not enough of an advancement to justify its deployment costs. The end result is that IPv6 is already one-quarter through its estimated 30-year lifespan and it isn't even widely deployed yet.
I suspect that what we need is an IPv7 that would include:
If we start now, this might be deployable by 2020 or so... :-/
There is another aspect to this. Memory is getting to the point where a router can handle the entire IPv4 address space as a linear table, which eliminates a huge bunch of tricks that Cisco has made a business from, lowering the barrier to entry. Cisco needs IPv6 to take off in the core Internet, in order to keep out competition.
Actually, you don't even need the ISS. All you need is a drop tower with vacuum inside. Any object in free fall is in zero gee. This technique is commonly used, on Earth, to manufacture small, cheap metal spheres.
Karl Rove, of course.
What it really comes down to is that carriage, whether or not it is DSL, Cable, WiMax or whatever, needs to be separated from connectivity to the public internet, which are the two services that are bundled together when one buys from an ISP. This is equivalent to being forced to buy your cell phone company's hideously expensive international long distance service, when you can have your pick of international carriers calling from your home phone. Otherwise, say goodbye to being able to get static IP addresses or other useful stuff, and say hello to port blocking and intrusive monitoring.
Of course, with the current FCC, guess which way it's going. Pretty soon we're back in the bad old days of monopoly carriers.
Close, but as far as I can tell, no cigar.
5 6888 79353856337336990862707537410378210647910118607312 951181346186064504193083887949753864...
According to bc(1) with scale cranked up, exp(pi*sqrt(163)) seems to evaluate to
262537412640768743.99999999999925007259719818
No, you weren't. I think Ralph Nader proposed this quite a while ago (no, I'm not kidding.)
Sounds a whole lot like the Bush Administration being taken to task over internment camps... just say "offensive" and pretend it's not true.
The USPTO registration number is 1916230.a tion&entry=1916230&action=Request+Status
http://tarr.uspto.gov/servlet/tarr?regser=registr
(Note: the mentioned William Della Croce is someone who fraudulently attempted to register Linux as a trademark; he got sued and transferred the trademark to Linus as part of settling the lawsuit.)
Typed Drawing
Word Mark LINUX
Goods and Services IC 009. US 021 023 026 036 038. G & S: computer operating system software to facilitate computer use and operation. FIRST USE: 19940802. FIRST USE IN COMMERCE: 19940802
Mark Drawing Code (1) TYPED DRAWING
Serial Number 74560867
Filing Date August 15, 1994
Current Filing Basis 1A
Original Filing Basis 1A
Published for Opposition June 13, 1995
Change In Registration CHANGE IN REGISTRATION HAS OCCURRED
Registration Number 1916230
Registration Date September 5, 1995
Owner (REGISTRANT) Croce, William R. Della, Jr. INDIVIDUAL UNITED STATES 33 Snow Hill St. Boston MASSACHUSETTS 02113
(LAST LISTED OWNER) TORVALDS, LINUS INDIVIDUAL Assignee of FINLAND 5774 CANNES PLACE SAN JOSE CALIFORNIA 95138
Assignment Recorded ASSIGNMENT RECORDED
Attorney of Record ROBERT T. DAUNT
Type of Mark TRADEMARK
Register PRINCIPAL
Affidavit Text SECT 15. SECT 8 (6-YR).
Live/Dead Indicator LIVE
C'mon guys... mirrors.kernel.org is only pumping 1100 Mbit/s so far... plenty of bandwidth to spare :)
http://mirrors.kernel.org/fedora/core/4/
ftp://mirrors.kernel.org/fedora/core/4/
rsync://mirrors.kernel.org/fedora/core/4/
Let's call it the Oceanian ID Card!
If you're really worried about it, you can put it in just about any compound which contains hydrogen, and it will still be radioactive, just not a gas. Combine it with oxygen (ditritium oxide) and you have superheavy radioactive water - unfortunately it's 2.5 times as heavy as the constitutent tritium, and it will give off monatomic oxygen as the tritium decays, which is highly corrosive.
Well, tritium is a beta emitter, which probably is a good thing... means the damage isn't going to be as focused on the inner surface of the lungs as for an alpha emitter (beta has larger penetration depth.)
Radon is in many ways the worst case; it's a heavy gas (pools around, stays in your lungs after inhalation) which quickly decays into a chain of very active alpha emitters; in fact, some of the most active in the whole uranium decay chain.
mirrors.kernel.org takes up most of the disk space. 10 TB obviously includes plenty of room to grow.