I have successfully used FAI to install Debian servers in the past. For what I needed it worked great. It is supposed to support other distributions and automatic updates as well but I haven't tried it for either of those uses.
While it is true that there is a cost to storing energy after it is generated it is also true that there is a non-zero cost to transmiting electricity as well. This cost increases as the distance increases. So at some point the two cancel each other out and it makes more sence to store the energy produced localy.
While the Baby Bells own the last mile to the customer they own the cables because the states where they operate allowed AT&T to have a Monopoly on the telephone infrastructure. This monopoly was granted to avoid the requirement for multiple incompatible telephone competitors in each market and in return the state/local government got to regulate the industry.
So while the Baby Bells own the copper wire that connects the customer to the central office that copper was installed under monopoly conditions, and in return for regulation. Now that the regulators are trying to restore competition they are attempting to balance the head start that the Baby Bells got using the government granted monopoly with equal access to facilities. If the Baby Bells (or their parent AT&T) got a leg up to enter the market place (i.e. the monopoly) why shouldn't the competitors get access to that infrastructure during the transition period to even the playing field.
I think a better way to handle all of this is to move the last mile assets into a wholesale infrastructure company and make both the Baby Bells and the new competitors pay to access the last mile.
Many people are complaining that using UDP to trasfer file attachments is impractical and that TCP transmission makes more sence for sending file attachments and that is true.
What I haven't seen anyone say is that when you want to do an application like realtime voice streaming (AKA online telephone chat) you don't care if you miss a few packets here or there.
Congestion becomes a problem when all of these users attempt to do realtime voice chat at the same time. If the protocols don't support congestion managment and don't back off their transmission rates then lots of packets get droped at the bottleneck routers and regular traffic gets bogged down as well.
It has to do with the design of the filesystem arch.
The os loads executable images into memory and backs those executable memory pages with the image on the disk. Unlike unix the file is locked by name instead of by inode so when you try to over write the file Windows complains (the file is locked so that any code that is swapped out to disk can be reloaded).
Now if the filesystem was based on inodes and the inode was locked instead the file could be unlinked from the directory and an new one created and linked to the same directory entry.
Instead to replace files there is a special API that tells Windows that the next time it reboots to do the file replacement before any applications load the executable images and they are locked into memory.
Slashdot Mirror
I have successfully used FAI to install Debian servers in the past. For what I needed it worked great. It is supposed to support other distributions and automatic updates as well but I haven't tried it for either of those uses.
While it is true that there is a cost to storing energy after it is generated it is also true that there is a non-zero cost to transmiting electricity as well. This cost increases as the distance increases. So at some point the two cancel each other out and it makes more sence to store the energy produced localy.
While the Baby Bells own the last mile to the customer they own the cables because the states where they operate allowed AT&T to have a Monopoly on the telephone infrastructure. This monopoly was granted to avoid the requirement for multiple incompatible telephone competitors in each market and in return the state/local government got to regulate the industry.
So while the Baby Bells own the copper wire that connects the customer to the central office that copper was installed under monopoly conditions, and in return for regulation. Now that the regulators are trying to restore competition they are attempting to balance the head start that the Baby Bells got using the government granted monopoly with equal access to facilities. If the Baby Bells (or their parent AT&T) got a leg up to enter the market place (i.e. the monopoly) why shouldn't the competitors get access to that infrastructure during the transition period to even the playing field.
I think a better way to handle all of this is to move the last mile assets into a wholesale infrastructure company and make both the Baby Bells and the new competitors pay to access the last mile.
What I haven't seen anyone say is that when you want to do an application like realtime voice streaming (AKA online telephone chat) you don't care if you miss a few packets here or there.
Congestion becomes a problem when all of these users attempt to do realtime voice chat at the same time. If the protocols don't support congestion managment and don't back off their transmission rates then lots of packets get droped at the bottleneck routers and regular traffic gets bogged down as well.
The os loads executable images into memory and backs those executable memory pages with the image on the disk. Unlike unix the file is locked by name instead of by inode so when you try to over write the file Windows complains (the file is locked so that any code that is swapped out to disk can be reloaded).
Now if the filesystem was based on inodes and the inode was locked instead the file could be unlinked from the directory and an new one created and linked to the same directory entry.
Instead to replace files there is a special API that tells Windows that the next time it reboots to do the file replacement before any applications load the executable images and they are locked into memory.