I've heard of ground differentials as large as 90 volts on ships -- a serious problem, and one you wouldn't expect on a metal vessel surrounded by nice conductive salt water.
I would recommend you run some fairly heavy -- 12 gauge should do -- ground wires in between the points you will be running the ethernet, and use the cables to interconnect the equipment ground points. Once you've done this, there shouldn't be any dangerous potentials on your ethernet lines. While you're at it, I'd also suggest you occasionally check for currents running on those ground wires; if you hook an ammeter around the wire and see more than a few dozen milliamps, you've got a bigger problem than ethernet grounding.
When I've "changed" my domain, I've always left the old one up and pointing to the same server. Unless NetNanny was doing reverse DNS to discover alternate names, there'd be no good reason to discontinue the old one. You'd also wind up breaking any old existing links to the website. There's lots of good reasons why, if the library had that original domain, it should have left it active.
For all you know, someone hacked the Piqua library's home page and sent a juicy story to the local paper.
Whether this is being done here in the U. S. of A, or in central Africa, there are costs involved. If you want to lend out CDs, over and over, clean them, polish them, sort them back into their bins and lend them out again, you're using up valuable materials and wasting the time of a trained professional who could be more productive elsewhere. Burning single replacements also takes more time per disc than burning a stack. Given the cost of individual discs nowadays it will still be less expensive to just give them out. If the people in that area can't afford a quarter per disc, then give them away for free; it's still less expensive than this lending scheme.
If you're going to be physically wiring up the neighborhood, I'd strongly recommend using fiber. If you want to be a CABLE COMPANY, supplying TV service as well as internet, you should look into set-top boxes with fiber inputs; you might wind up laying coax, but do yourself a favor and LAY FIBER TOO.
For wireless, 802.11 (not B) will supply a fairly decent amount of bandwidth to a pretty wide area -- so long as the weather is good. I live in a desert area, so it's decent here, but if you get a significant amount of rain, I'd recommend against it, both for you and your customers.
For permission to lay cable, contact your local government to see what permits and requirements there are for underground or above-ground cable runs. Some cities and counties are pretty lax about it; some can get quite anal. Knowing someone in government may help you.
There may be other local conditions you need to know about before you start work. High ground water may make long-term cable emplacement problematic. A low water table may make equipment grounding a serious expense. You might want to snoop around in the cities near you to figure out if you need anything special.
What you're essentially doing is creating a development fork, with the original "tine" not being developed.
I suppose you should take some time and try and contact the original developers, and see if you can get an official go-ahead. But if you can't, go right ahead.
In the worst case, if the original maintainers come back and cause such a stink about your taking over the project, they can take what you produced and merge or develop their own fork.
If it is legal to "borrow" the CD to install on the computer, it ought to be legal to simply give them away. It would be less expensive for you, once you've considered the manpower costs of recataloging and inspecting, to simply mass-burn the CDs and give them out, and not have to deal with returns. You could also charge a nominal fee, say 25 cents, that would completely cover the costs of the discs and then some.
A solar sail would be a good way to provide a sustained force on an asteroid; it need not be an elaborate structure, nor tightly defined as a spacecraft would need; a large parachute-like sail would be sufficient. It would be passive, requiring no fuel except what's needed to plant it, and its effectiveness would increase as the object approached its perigee, near the Sun.
But as the article says, you need a long lead time to move the asteroid enough to be sure it misses the Earth. Whichever method is eventually used, we'll still need to scan the sky, so as to catch them early.
You're still converting one form of energy into another. That infrared would otherwise be radiating to other objects, increasing their entropy. The infrared produced is tiny compared to the total entropy of the object radiating it, so you could look at it as absorbing the small amount of spontaneous order generated from chaos.
In addition, as I said in the subject, light is light. If one frequency of light can be turned into energy, they all ought to be susceptible to the same concept, if not the same receiver.
Here's a question for you, and for everyone else: Would a solar cell continue to operate in an ambient temperature sufficient to generate that frequency in black-body radiation?
No, it's "hey, you USED mine - now let me USE yours."
You always have the option not to use the GPL'd code. There are closed-source alternatives for pretty much anything GPL'd software can do. Of course, you have to pay for it. Further, most GPL authors are willing to license their code for proprietary use -- again, if the money is right.
GPL'd code is not FREE code. There is a price. If it's not the price you want to pay, then don't buy it!
Let me get this straight: You have the software company who was distributing the product containing your GPL'd code, and you have other coders who have contributed to the project, and who do not want their proprietary code made public. Now, either the other coders knew they were working with your code and may have been aware of the GPL licensing, or they didn't.
If they were aware of the licensing restrictions on the code they were working with, then they are morally in the wrong and a court will probably rule against them.
If they were not so aware, as in if the software company concealed the knowledge of GPL restrictions from them, or had them working on a separate segment of the code which was included in the project but not directly involved with the GPL, then it's the software company's fault in scheduling conflicting licenses. It is not YOUR responsibility to PUBLISH the source code, it is that company's; you might only be distributing that source, and perhaps not even that. The software company would have the options of:
(1) Withdrawing the program from the market completely; (2) Replacing your GPL'd code with equivalent proprietary code, and keeping the codebase secret; (3) Replacing the other coders' proprietary code with open-sourceable code (or licensing their code for open-source use) and publishing the codebase; (4) Publishing the codebase as-is, and risk being sued by the other coders; (5) Keeping the codebase secret, and risk being sued by you.
I do not see any way a court would hold you liable for making the software company publish the code; it was not your decision to tie their code up with yours. If it does head to court, though... Get a good lawyer.
Never mind what happens when you try to run dozens of such machines in an office environment (especially in an office building with lots of small individual tenants who won't want to coordinate bandwidth use)... You're taking up valuable radio spectrum just to avoid using a 9' cable? That's ludicrous.
If you're writing 8 pixels for each byte of data you transfer to the video adapter, then yes. But speed isn't the question; it's all the nice, antialiased fonts and window effects and code libraries that users are now familiar with and used to. If you don't believe me, do some work on an old Mac SE. Or even that Amiga, running the old OS. You'll find the windowing system laughable and grating.
Trying to fit a memory-intensive desktop system into a small space is going to be difficult because they're opposite goals. System 6 and prior MacOS did it, but only by using black-and-white graphics and not providing most of the tools you'd expect nowadays from a graphical desktop. I think even GEOS needed several disks worth of data to load its desktop. And if the goal is to allow novice users to operate small distros, they'd take one look at that desktop and go "ew! Linux sucks!" and switch back to Windows.
It also means you have a limited selection; even a place like Wal Mart can't carry every variation of what you want. Heck, no downtown smaller than NYC's could. Amazon bills itself as the "world's largest bookstore" for a reason; it would take a few dozen warehouses the size of a Border's to carry every title out there.
Actually, a very few antibiotics also have antiviral effects. This is because infected cells often have some of their biological machinery changed due to the genetic change, and begin operating at a more primitive level.
Slashdot Mirror
I've heard of ground differentials as large as 90 volts on ships -- a serious problem, and one you wouldn't expect on a metal vessel surrounded by nice conductive salt water.
I would recommend you run some fairly heavy -- 12 gauge should do -- ground wires in between the points you will be running the ethernet, and use the cables to interconnect the equipment ground points. Once you've done this, there shouldn't be any dangerous potentials on your ethernet lines. While you're at it, I'd also suggest you occasionally check for currents running on those ground wires; if you hook an ammeter around the wire and see more than a few dozen milliamps, you've got a bigger problem than ethernet grounding.
When I've "changed" my domain, I've always left the old one up and pointing to the same server. Unless NetNanny was doing reverse DNS to discover alternate names, there'd be no good reason to discontinue the old one. You'd also wind up breaking any old existing links to the website. There's lots of good reasons why, if the library had that original domain, it should have left it active.
For all you know, someone hacked the Piqua library's home page and sent a juicy story to the local paper.
There is no "www.fleshpublic.lib.oh.us".
Whether this is being done here in the U. S. of A, or in central Africa, there are costs involved. If you want to lend out CDs, over and over, clean them, polish them, sort them back into their bins and lend them out again, you're using up valuable materials and wasting the time of a trained professional who could be more productive elsewhere. Burning single replacements also takes more time per disc than burning a stack. Given the cost of individual discs nowadays it will still be less expensive to just give them out. If the people in that area can't afford a quarter per disc, then give them away for free; it's still less expensive than this lending scheme.
If you're going to be physically wiring up the neighborhood, I'd strongly recommend using fiber. If you want to be a CABLE COMPANY, supplying TV service as well as internet, you should look into set-top boxes with fiber inputs; you might wind up laying coax, but do yourself a favor and LAY FIBER TOO.
For wireless, 802.11 (not B) will supply a fairly decent amount of bandwidth to a pretty wide area -- so long as the weather is good. I live in a desert area, so it's decent here, but if you get a significant amount of rain, I'd recommend against it, both for you and your customers.
For permission to lay cable, contact your local government to see what permits and requirements there are for underground or above-ground cable runs. Some cities and counties are pretty lax about it; some can get quite anal. Knowing someone in government may help you.
There may be other local conditions you need to know about before you start work. High ground water may make long-term cable emplacement problematic. A low water table may make equipment grounding a serious expense. You might want to snoop around in the cities near you to figure out if you need anything special.
I'm surprised no one put a link to the original Slashdot entry...
I'd hate to see the history of the net destroyed if the sprinkler system goes off in their server room...
What you're essentially doing is creating a development fork, with the original "tine" not being developed.
I suppose you should take some time and try and contact the original developers, and see if you can get an official go-ahead. But if you can't, go right ahead.
In the worst case, if the original maintainers come back and cause such a stink about your taking over the project, they can take what you produced and merge or develop their own fork.
If it is legal to "borrow" the CD to install on the computer, it ought to be legal to simply give them away. It would be less expensive for you, once you've considered the manpower costs of recataloging and inspecting, to simply mass-burn the CDs and give them out, and not have to deal with returns. You could also charge a nominal fee, say 25 cents, that would completely cover the costs of the discs and then some.
Just posting the prices everywhere, far and wide, on servers outside the US, for everyone to see?
Then again... Maybe that's what they want? After all, any publicity is good publicity...
Definitely.
There's been a lot of talk about canning our current email system and going with a semi-p2p replacement. This replacement should include cryptography.
> To ruin the net to save Disney is the equivalent of
;-)
> burning down the library of Alexandria to save
> monastic scribes
Ahh, I'd always wondered what had happened...
A solar sail would be a good way to provide a sustained force on an asteroid; it need not be an elaborate structure, nor tightly defined as a spacecraft would need; a large parachute-like sail would be sufficient. It would be passive, requiring no fuel except what's needed to plant it, and its effectiveness would increase as the object approached its perigee, near the Sun.
But as the article says, you need a long lead time to move the asteroid enough to be sure it misses the Earth. Whichever method is eventually used, we'll still need to scan the sky, so as to catch them early.
You're still converting one form of energy into another. That infrared would otherwise be radiating to other objects, increasing their entropy. The infrared produced is tiny compared to the total entropy of the object radiating it, so you could look at it as absorbing the small amount of spontaneous order generated from chaos.
In addition, as I said in the subject, light is light. If one frequency of light can be turned into energy, they all ought to be susceptible to the same concept, if not the same receiver.
Here's a question for you, and for everyone else: Would a solar cell continue to operate in an ambient temperature sufficient to generate that frequency in black-body radiation?
No, it's "hey, you USED mine - now let me USE yours."
You always have the option not to use the GPL'd code. There are closed-source alternatives for pretty much anything GPL'd software can do. Of course, you have to pay for it. Further, most GPL authors are willing to license their code for proprietary use -- again, if the money is right.
GPL'd code is not FREE code. There is a price. If it's not the price you want to pay, then don't buy it!
Let me get this straight: You have the software company who was distributing the product containing your GPL'd code, and you have other coders who have contributed to the project, and who do not want their proprietary code made public. Now, either the other coders knew they were working with your code and may have been aware of the GPL licensing, or they didn't.
If they were aware of the licensing restrictions on the code they were working with, then they are morally in the wrong and a court will probably rule against them.
If they were not so aware, as in if the software company concealed the knowledge of GPL restrictions from them, or had them working on a separate segment of the code which was included in the project but not directly involved with the GPL, then it's the software company's fault in scheduling conflicting licenses. It is not YOUR responsibility to PUBLISH the source code, it is that company's; you might only be distributing that source, and perhaps not even that. The software company would have the options of:
(1) Withdrawing the program from the market completely;
(2) Replacing your GPL'd code with equivalent proprietary code, and keeping the codebase secret;
(3) Replacing the other coders' proprietary code with open-sourceable code (or licensing their code for open-source use) and publishing the codebase;
(4) Publishing the codebase as-is, and risk being sued by the other coders;
(5) Keeping the codebase secret, and risk being sued by you.
I do not see any way a court would hold you liable for making the software company publish the code; it was not your decision to tie their code up with yours. If it does head to court, though... Get a good lawyer.
Never mind what happens when you try to run dozens of such machines in an office environment (especially in an office building with lots of small individual tenants who won't want to coordinate bandwidth use)... You're taking up valuable radio spectrum just to avoid using a 9' cable? That's ludicrous.
If you're writing 8 pixels for each byte of data you transfer to the video adapter, then yes. But speed isn't the question; it's all the nice, antialiased fonts and window effects and code libraries that users are now familiar with and used to. If you don't believe me, do some work on an old Mac SE. Or even that Amiga, running the old OS. You'll find the windowing system laughable and grating.
Trying to fit a memory-intensive desktop system into a small space is going to be difficult because they're opposite goals. System 6 and prior MacOS did it, but only by using black-and-white graphics and not providing most of the tools you'd expect nowadays from a graphical desktop. I think even GEOS needed several disks worth of data to load its desktop. And if the goal is to allow novice users to operate small distros, they'd take one look at that desktop and go "ew! Linux sucks!" and switch back to Windows.
Not a player, a recorder. Something that'll burn video to a disc without checking if the video stream is specified as protected.
Dumb question -- anyone seen any consumer DVD recorders where the security could be bypassed?
> But, stores like Borders will order a title for you
Sure. At list price only.
It also means you have a limited selection; even a place like Wal Mart can't carry every variation of what you want. Heck, no downtown smaller than NYC's could. Amazon bills itself as the "world's largest bookstore" for a reason; it would take a few dozen warehouses the size of a Border's to carry every title out there.
Actually, a very few antibiotics also have antiviral effects. This is because infected cells often have some of their biological machinery changed due to the genetic change, and begin operating at a more primitive level.
Rats drown in Wordstar.
(An old palindrome)