No, see from the utilities perspective, peak capacity is the most expensive thing they provide. They are far more happy if electricity demand is even all day rather than peaking in the afternoon. Of course if these systems are implemented electricity prices will go up in the morning, but they'll go down in the afternoon and overall they'll decline because the utilities don't need all that expensive peak capacity, which tends to be generated by expensive sources like natural gas turbines rather than cheap coal and nuclear power. That said, hydroelectric can be easilly ramped up and down to meet demand, but there isn't all that much hydro around, and there isn't much left to develop.
Try running 100Base-T over untwisted cables... If you screw up while making your own it's a pretty easy thing to end up doing, where each line pair should go isn't obvious, you need the proper wiring diagram. I've done this and while for short runs of 10-15 ft it still works your connect degrads pretty quickly if you do anything longer or have any source of noise. (like the large shortwave radio transmitter close to work...)
And why the hell do you think that dog food is magicly going to go down in price in the future just because of inflation? Dog food prices will probably stay basicly stable, matching inflation. So 20 years from now it'll cost $1 a day, in 20 year from now dollars, rather then $0.25
'Course maybe you're assuming that instead of spending the money you'll now put it in a nice dollar generating investment in which case yes the dog will probably come out on top.
No solar panels increase albedo, big time. Hardly any of the solar energy that hits them is converted to electricity. Instead it's all converted to heat, solar panels are black after all. Plain sand has a very low albedo being very light color.
Didn't you read the artical and see what it said on how large-scale use of solar would cause a large increase in the absorbtion of sunlight?
The root problem here is that when you reinstall machines you aren't restoring the original ssh host keys. Why don't you start making backups of those keys and restoring them to the proper places whenever you do a reinstall?
Secondly for key distribution why don't you setup a cronjob that will copy the host key list from a single, secure, server every hour or something via scp? Then just make sure that servers host key never changes by doing the above.
Or make a script along the lines of:
for i in host1 host2 host3
ssh root@$i "scp someserver:/keyslist keyslist"
end
and run it every time you need to update all of the key lists.
All those methods are quite secure as they all use scp to do the copying and will fail should the host key of the machine somehow change, say by an imposter. Unless someone manages to break into the machine itself your fine.
Yes, it's true that there will be many copies, and many of them will be relatively "near" me on the Internet. However, it is not expected that all (or even most) data will be one hop away. Any data that is more than one hop away will end up being proxied (transferred) 1 time for each server. That's how anonymity is provided. If we're talking about really big files like MP3s, number one, that means that, as a Freenet node, I'm passing through a LOT of traffic to the people near me proxying through me.
You're forgetting just how powerfull the automatic adaptation of the routing is. Simulations have shown again and again that the number of hops for any data is kept *very* low, about 5 hops for a large network with lots of data. As data is requested the routing tables get optimized so that the node that returned the data is likely to be contacted again for similar data. Also on insertion the data is more likely to go to that node.
Also should you ever request data twice it's one hop. I know I request a heck of a lot of data multiple times...
It's not as efficient as normal internet routing for unpopular data but way more efficient for popular data. And I'll guess that a good %70 of the data I use would be classified as "popular", slashdot front page and stuff linked off of it for instance. (this is ignoring dynamicly created stuff which Freenet can't do anyway)
Number two, it means that, when I click "download," it's got to be actually downloaded and uploaded two or three times for the average case. If one of those links in the middle has a 56k (or reboots in the middle), it's gonna be a REALLY slow process.
As I mentioned network speed will be taken into account in future versions of Freenet so your 56k modem will only be used as a last resort.
As for rebooting nodes just plain don't get rebooted often. Nodes that don't aren't on 24/7 just don't get added to routing tables. Freenet is *very* harsh against nodes that aren't always on. Probably more harsh then it should be really.
You then finish, "Freenet doesn't do a very good job of this because it doesn't take network speeds into acocount...But it will be quite simple to add support for that and will be done after a few more releases." Yes, and, if you do that, it'll become a backbone network, because all clients will "want" to connect to the few fast peers. If I'm the RIAA, I just DMCA notice all those fast peers' ISPs on the same day, and the network falls over.
The fastest peers won't be the same for everyone. It's far faster to connect to a system 3 hops away from you then some system on the other side of the planet. Anyway Freenet is already biased torwards nodes with big datastores. And if you do knock out those nodes not all that much happens. I've tested this on my node and if I block access to even a node with %70 of the references things return to normal in a few hours. And it's unlikely that any node would rival the hundreds of smaller nodes around.
Regardless of specific attacks, my point is that Freenet (or any P2P) is, by definition, going to be more complex (and hence more expensive) than a simple, centralized system, and will therefor only be used when the primary overriding concern is trying to hide who is distributing the content, not for people who want to put up family pictures.
Any *free* system is going to be used for illegal stuff if the users can get away with it. Freenet still provides many advantages over centralized servers when you're trying to serve large data. The automatic caching makes the slashdot effect just not happen. The *more* often a site is requested the faster and more reliable it is to get the site. I use Freenet, this is true and works really well even in spite of all the bugs and other nastyness in the network right now.
Freenet is anonymous, it's archetecture automaticly does proxying and multiple layers at that. While the first node you connect to can figure out who you are they can't easilly determine if you initiated the request and any nodes down the further down the chain don't have a clue about who you are. Unlike Gnutella when a Freenet request is fufilled the requesting node doesn't directly connect to the node that has the data.
Secondly by creating many copies of popular data you are decreasing the amount of bandwidth used in exchange for increasing the amount of space used. Say you have a popular site in Europe that's getting lots of hits from the US. Without Freenet every time someone in the US wants the data their request has to go over congested international links, very wastefull that. With Freenet a copy of the data, probably many copies in fact, would soon get stored in the US reducing the load on those slow international links. Even though the data has to go through many nodes in between, and has multiple copies of it made, you still get a significant savings in bandwidth usage. And any copies made while en-route are likely to be used again by other people because those copies are by-nature "close" to the keyspace that node serves.
Ever heard of Akamia? They do essentially the same thing with their network to reduce the load on sites around the net.
Now currently Freenet doesn't do a very good job of this because it doesn't take network speeds into account when choosing nodes while routing messages. But it will be quite simple to add support for that and will be done after a few more releases.
Freenet isn't 100% anonymous but it's pretty good. All freenet messages can't be traced back to the IP they came from, Freenet does it's own routing. Also inter-node traffic is encrypted twice, first data can only be decrypted by the requester, the key used to request the data is used as an encryption key for the data. Secondly traffic between nodes is encrypted to stop packet sniffers. It is possible for a node to find out what keys other nodes are requested from it but as the keys are encrypted you have to find the mappings of plain-text keys to encrypted keys by running robots that look for data on Freenet, not a easy task nor can they uncover everything.
Freenet isn't and never will be 100% resistant to attacks but it's way, way better then anything else.
Requesting your own files doesn't work. You would have to do the requests from nodes all over the network. If you just request from one single node it will get the data, cache it then just give you the data every time. So only that one node would have a copy of your data.
Telling your node to not delete specific files doesn't work. Just because a specific node has some data on it doesn't mean any other node can find it. Each node has a set of references that point to other nodes. If a key x is "close" to reference y then the node pointed to by reference y will be contacted. But the references don't last forever and are only renewed by someone requesting data. If no-one requests the data the references to your data will eventually decay. When that happens even if someone did want to request the data they would be able to find it.
See this page for a more indepth discussion of this.
Well with 99% of the nodes knocked out the bandwidth carrying capacity would go to shit. (of course there wouldn't be noded around to use the bandwidth) Also I have to wonder if the routers and the like could reconfigure themselves effectively. This would be a *massive* change and even with routing protocols and the like I'd expect something to go wrong.
Any network engineers out there have any idea of what would really happen?
I've got a mirror of the the fuzz paper up at http://esm.sourceforge.net/fuzz-nt.ps and also on Freenet as the key KSK@fuzz-nt.ps You can download the key by directly clicking on the link (it will go through my freenet gateway) or by using your own freenet code.
No reputation again? Me thinks someone saw the high bids on the previous auction, $70,000 when it ended, and decided to try the game themselves. Two words: Be suspicious.
Hate to say this but the guy's seller rating is zero, there is a good chance he's not legit. Besides this is a heck of a lot of stuff all said to be in mint condition, or so he claims.
But every form of music you list is at a different quality. Why should the music company suddenly be forced to give you a better quality recording of the music when they introduce a new form of it, tape -> cd for instance? I can agree with allowing you to make a copy of your music in a different form but forcing a company to make the new form free, or even to offer a discount, is in the realm of marketing, not ethics or law.
This release contains forward-looking statements regarding financial results for future periods. Actual results could differ materially. Among the factors which could cause results to differ materially is the possibility that the Pentium 4 and PlayStation2 ramps will be slower than expected, that shipment of Rambus ICs and other licensed products by Rambus licensees will be below forecast, that no additional licenses for SDRAM-compatible ICs will be signed, that prices of RDRAMs will remain high compared to SDRAMs and that litigation and building costs will exceed the Company?s plans.
It's just the disclaimer saying what *could* go wrong, not what is likely to go wrong. (though IMO in this case many of those things are quite likely to happen) So at the very least they aren't willing to publicly admit that they're screwed. Who knows, maybe they even believe it themselves. Sometimes people lie often enough that they start to believe their own lies...
The LGPL is considered a last resort license. For instead libc *has* to be under the LGPL for you to be able to use proprietary programs with it, so they have no choice. But otherwise the use of the LGPL is frowned upon.
Russia was and still is anything but free. Sure you wouldn't have software companies on your ass, but if you did anything politically unapproved you would have the KGB following you around. The USA is a lot more "free" then Russia.
XML may not help us one bit. The word format is documented, sort of. The problem is that to actually *display* Word and other MS documents you need a lot of MS-specific stuff because everything is encapsulated with OLE. The same will apply to XML. We'll be able to easilly see the *basic* structure but displaying any document will be hard because of all of the MS-specific DLL's and other junk that does all the real work.
The problem is those companies that don't want to have to abide to all of the GPL rules will still try to do as much as they possibly can to get the advantages of GPLed software without any of the disadvantages. This isn't a problem for companies trying to exploit GPLed software for their own uses. The problem is that there may be loopholes in the GPL that allow those companies to exploit the GPLed software and not give back to the community.
Early Cyrix chips ran extremely hot. Without a very good quality heat-sink they would burn up, I know, I've had to deal with badly made Cyrix systems at work. Right now two of my computers are rejects that were permanently fried after 2 years of high-temp operation.
Though I am somewhat seriously getting a Cyrix III just so I can use fewer fans. I've had enough of high-performence.:)
One thing everyone forgets about emulating Macs, IE emulating PowerPC's, is that Apple still controls the Mac BIOS. That's why you don't see any Mac clones. (well Apple did experiment with licencing the BIOS but decided against it in the end) The Crusoe isn't going to be any different.
The most recent version of Bochs supports different sound output devices. Look at the default.bochsrc configuration file and search for/dev/dsp and you'll find the line you need to change.
I just made a patch for UAE 0.7.6 that adds a -e option that allows you to specify the device used for sound output. Download it here. To apply it simply go into your UAE source directory and type patch -p0 < patchfile where patchfile is the patch you want to apply.
Slashdot Mirror
No, you're wrong. The write leveling is done by the controller on the USB thumb drive itself, not the computer it's attached too.
Ref: http://www.storagesearch.com/siliconsys-art1.html
No, see from the utilities perspective, peak capacity is the most expensive thing they provide. They are far more happy if electricity demand is even all day rather than peaking in the afternoon. Of course if these systems are implemented electricity prices will go up in the morning, but they'll go down in the afternoon and overall they'll decline because the utilities don't need all that expensive peak capacity, which tends to be generated by expensive sources like natural gas turbines rather than cheap coal and nuclear power. That said, hydroelectric can be easilly ramped up and down to meet demand, but there isn't all that much hydro around, and there isn't much left to develop.
Try running 100Base-T over untwisted cables... If you screw up while making your own it's a pretty easy thing to end up doing, where each line pair should go isn't obvious, you need the proper wiring diagram. I've done this and while for short runs of 10-15 ft it still works your connect degrads pretty quickly if you do anything longer or have any source of noise. (like the large shortwave radio transmitter close to work...)
And why the hell do you think that dog food is magicly going to go down in price in the future just because of inflation? Dog food prices will probably stay basicly stable, matching inflation. So 20 years from now it'll cost $1 a day, in 20 year from now dollars, rather then $0.25
'Course maybe you're assuming that instead of spending the money you'll now put it in a nice dollar generating investment in which case yes the dog will probably come out on top.
No solar panels increase albedo, big time. Hardly any of the solar energy that hits them is converted to electricity. Instead it's all converted to heat, solar panels are black after all. Plain sand has a very low albedo being very light color.
Didn't you read the artical and see what it said on how large-scale use of solar would cause a large increase in the absorbtion of sunlight?
The root problem here is that when you reinstall machines you aren't restoring the original ssh host keys. Why don't you start making backups of those keys and restoring them to the proper places whenever you do a reinstall?
Secondly for key distribution why don't you setup a cronjob that will copy the host key list from a single, secure, server every hour or something via scp? Then just make sure that servers host key never changes by doing the above.
Or make a script along the lines of:
for i in host1 host2 host3
ssh root@$i "scp someserver:/keyslist keyslist"
end
and run it every time you need to update all of the key lists.
All those methods are quite secure as they all use scp to do the copying and will fail should the host key of the machine somehow change, say by an imposter. Unless someone manages to break into the machine itself your fine.
Yes, it's true that there will be many copies, and many of them will be relatively "near" me on the Internet. However, it is not expected that all (or even most) data will be one hop away. Any data that is more than one hop away will end up being proxied (transferred) 1 time for each server. That's how anonymity is provided. If we're talking about really big files like MP3s, number one, that means that, as a Freenet node, I'm passing through a LOT of traffic to the people near me proxying through me.
You're forgetting just how powerfull the automatic adaptation of the routing is. Simulations have shown again and again that the number of hops for any data is kept *very* low, about 5 hops for a large network with lots of data. As data is requested the routing tables get optimized so that the node that returned the data is likely to be contacted again for similar data. Also on insertion the data is more likely to go to that node.
Also should you ever request data twice it's one hop. I know I request a heck of a lot of data multiple times...
It's not as efficient as normal internet routing for unpopular data but way more efficient for popular data. And I'll guess that a good %70 of the data I use would be classified as "popular", slashdot front page and stuff linked off of it for instance. (this is ignoring dynamicly created stuff which Freenet can't do anyway)
Number two, it means that, when I click "download," it's got to be actually downloaded and uploaded two or three times for the average case. If one of those links in the middle has a 56k (or reboots in the middle), it's gonna be a REALLY slow process.
As I mentioned network speed will be taken into account in future versions of Freenet so your 56k modem will only be used as a last resort.
As for rebooting nodes just plain don't get rebooted often. Nodes that don't aren't on 24/7 just don't get added to routing tables. Freenet is *very* harsh against nodes that aren't always on. Probably more harsh then it should be really.
You then finish, "Freenet doesn't do a very good job of this because it doesn't take network speeds into acocount...But it will be quite simple to add support for that and will be done after a few more releases." Yes, and, if you do that, it'll become a backbone network, because all clients will "want" to connect to the few fast peers. If I'm the RIAA, I just DMCA notice all those fast peers' ISPs on the same day, and the network falls over.
The fastest peers won't be the same for everyone. It's far faster to connect to a system 3 hops away from you then some system on the other side of the planet. Anyway Freenet is already biased torwards nodes with big datastores. And if you do knock out those nodes not all that much happens. I've tested this on my node and if I block access to even a node with %70 of the references things return to normal in a few hours. And it's unlikely that any node would rival the hundreds of smaller nodes around.
Regardless of specific attacks, my point is that Freenet (or any P2P) is, by definition, going to be more complex (and hence more expensive) than a simple, centralized system, and will therefor only be used when the primary overriding concern is trying to hide who is distributing the content, not for people who want to put up family pictures.
Any *free* system is going to be used for illegal stuff if the users can get away with it. Freenet still provides many advantages over centralized servers when you're trying to serve large data. The automatic caching makes the slashdot effect just not happen. The *more* often a site is requested the faster and more reliable it is to get the site. I use Freenet, this is true and works really well even in spite of all the bugs and other nastyness in the network right now.
Freenet is anonymous, it's archetecture automaticly does proxying and multiple layers at that. While the first node you connect to can figure out who you are they can't easilly determine if you initiated the request and any nodes down the further down the chain don't have a clue about who you are. Unlike Gnutella when a Freenet request is fufilled the requesting node doesn't directly connect to the node that has the data.
Secondly by creating many copies of popular data you are decreasing the amount of bandwidth used in exchange for increasing the amount of space used. Say you have a popular site in Europe that's getting lots of hits from the US. Without Freenet every time someone in the US wants the data their request has to go over congested international links, very wastefull that. With Freenet a copy of the data, probably many copies in fact, would soon get stored in the US reducing the load on those slow international links. Even though the data has to go through many nodes in between, and has multiple copies of it made, you still get a significant savings in bandwidth usage. And any copies made while en-route are likely to be used again by other people because those copies are by-nature "close" to the keyspace that node serves.
Ever heard of Akamia? They do essentially the same thing with their network to reduce the load on sites around the net.
Now currently Freenet doesn't do a very good job of this because it doesn't take network speeds into account when choosing nodes while routing messages. But it will be quite simple to add support for that and will be done after a few more releases.
Also, when data is placed on Freenet, it's split into pieces and distributed to several nodes making it even tougher.
Actually file splitting hasn't been implemented yet on Freenet. It probably will be by version 0.4.0 (current is 0.3.7) but not yet.
Perhaps you are thinking about how related files, such as file comprising a website on Freenet, get put on different nodes when they are inserted?
Freenet isn't 100% anonymous but it's pretty good. All freenet messages can't be traced back to the IP they came from, Freenet does it's own routing. Also inter-node traffic is encrypted twice, first data can only be decrypted by the requester, the key used to request the data is used as an encryption key for the data. Secondly traffic between nodes is encrypted to stop packet sniffers. It is possible for a node to find out what keys other nodes are requested from it but as the keys are encrypted you have to find the mappings of plain-text keys to encrypted keys by running robots that look for data on Freenet, not a easy task nor can they uncover everything.
Freenet isn't and never will be 100% resistant to attacks but it's way, way better then anything else.
Requesting your own files doesn't work. You would have to do the requests from nodes all over the network. If you just request from one single node it will get the data, cache it then just give you the data every time. So only that one node would have a copy of your data.
Telling your node to not delete specific files doesn't work. Just because a specific node has some data on it doesn't mean any other node can find it. Each node has a set of references that point to other nodes. If a key x is "close" to reference y then the node pointed to by reference y will be contacted. But the references don't last forever and are only renewed by someone requesting data. If no-one requests the data the references to your data will eventually decay. When that happens even if someone did want to request the data they would be able to find it.
See this page for a more indepth discussion of this.
Well with 99% of the nodes knocked out the bandwidth carrying capacity would go to shit. (of course there wouldn't be noded around to use the bandwidth) Also I have to wonder if the routers and the like could reconfigure themselves effectively. This would be a *massive* change and even with routing protocols and the like I'd expect something to go wrong.
Any network engineers out there have any idea of what would really happen?
I've got a mirror of the the fuzz paper up at http://esm.sourceforge.net/fuzz-nt.ps and also on Freenet as the key KSK@fuzz-nt.ps You can download the key by directly clicking on the link (it will go through my freenet gateway) or by using your own freenet code.
No reputation again? Me thinks someone saw the high bids on the previous auction, $70,000 when it ended, and decided to try the game themselves. Two words: Be suspicious.
Hate to say this but the guy's seller rating is zero, there is a good chance he's not legit. Besides this is a heck of a lot of stuff all said to be in mint condition, or so he claims.
I'd be wary...
But every form of music you list is at a different quality. Why should the music company suddenly be forced to give you a better quality recording of the music when they introduce a new form of it, tape -> cd for instance? I can agree with allowing you to make a copy of your music in a different form but forcing a company to make the new form free, or even to offer a discount, is in the realm of marketing, not ethics or law.
The full statment is:
This release contains forward-looking statements regarding financial results for future periods. Actual results could differ materially. Among the factors which could cause results to differ materially is the possibility that the Pentium 4 and PlayStation2 ramps will be slower than expected, that shipment of Rambus ICs and other licensed products by Rambus licensees will be below forecast, that no additional licenses for SDRAM-compatible ICs will be signed, that prices of RDRAMs will remain high compared to SDRAMs and that litigation and building costs will exceed the Company?s plans.
It's just the disclaimer saying what *could* go wrong, not what is likely to go wrong. (though IMO in this case many of those things are quite likely to happen) So at the very least they aren't willing to publicly admit that they're screwed. Who knows, maybe they even believe it themselves. Sometimes people lie often enough that they start to believe their own lies...
The LGPL is considered a last resort license. For instead libc *has* to be under the LGPL for you to be able to use proprietary programs with it, so they have no choice. But otherwise the use of the LGPL is frowned upon.
Russia was and still is anything but free. Sure you wouldn't have software companies on your ass, but if you did anything politically unapproved you would have the KGB following you around. The USA is a lot more "free" then Russia.
XML may not help us one bit. The word format is documented, sort of. The problem is that to actually *display* Word and other MS documents you need a lot of MS-specific stuff because everything is encapsulated with OLE. The same will apply to XML. We'll be able to easilly see the *basic* structure but displaying any document will be hard because of all of the MS-specific DLL's and other junk that does all the real work.
Don't get your hopes up.
The problem is those companies that don't want to have to abide to all of the GPL rules will still try to do as much as they possibly can to get the advantages of GPLed software without any of the disadvantages. This isn't a problem for companies trying to exploit GPLed software for their own uses. The problem is that there may be loopholes in the GPL that allow those companies to exploit the GPLed software and not give back to the community.
Early Cyrix chips ran extremely hot. Without a very good quality heat-sink they would burn up, I know, I've had to deal with badly made Cyrix systems at work. Right now two of my computers are rejects that were permanently fried after 2 years of high-temp operation.
Though I am somewhat seriously getting a Cyrix III just so I can use fewer fans. I've had enough of high-performence. :)
One thing everyone forgets about emulating Macs, IE emulating PowerPC's, is that Apple still controls the Mac BIOS. That's why you don't see any Mac clones. (well Apple did experiment with licencing the BIOS but decided against it in the end) The Crusoe isn't going to be any different.
The most recent version of Bochs supports different sound output devices. Look at the default .bochsrc configuration file and search for /dev/dsp and you'll find the line you need to change.
I just made a patch for UAE 0.7.6 that adds a -e option that allows you to specify the device used for sound output. Download it here. To apply it simply go into your UAE source directory and type patch -p0 < patchfile where patchfile is the patch you want to apply.
I hope this helps.