You are presuming an enforcement that's not only insane, but impossible.
So you are in favor of passing new rules that you consider to be impossible to enforce? Why do you support that? Please be specific.
And, then it says, you just put hundreds of thousands of these things under highways, and start reaping a non-trivial amount of electricity
And cause a non-trivial increase in rolling resistance and reduction in mileage of the victim vehicles. That energy had to come from somewhere, and collecting it has side-effects.
TANSTAAFL: The first law of thermodynamics as well as economics.
The trees, on the other hand, may appreciate some energy-absorbing sway damping - especially in a storm. (As long as it doesn't interfere with pumping the water up the trunk to the leaves, of course.)
Oops, got the history horribly mixed up. Try this:
Written in 1976, under licensing granting source use in classes, suppressed with the release of System 7 in 1979, which didn't include this license term, (after which Unix source code was deleted from classes and the two-volume set became an underground copier-room classic), general distribution of "ancient source" (including System 6) authorized by SCO and the book reprinted with the 1977 version of the commentary (plus a forward by Ritchie) in 1996.
What was the title of those text books?
Lions' Commentary on UNIX 6th Edition, with Source Code, a.k.a. "The Lions Book".
Written in 1976, under licensing granting source use in classes, suppressed with the release of System 7, which didn't include this license term, (after which Unix source code was deleted from classes and the two-volume set became an underground copier-room classic), general distribution of "ancient source" (including System 6) authorized by SCO in 1976, reprinted in 1977 with updated commentary and again with added historical commentary in 1996.
See the above-referenced Wikipedia article for ISBNs, more details, and links to more history.
To which version of System V are you referring? The original one, SVR2, SVR3, or SVR4 and later?
The entire project (or at least from the start through the initial deployment of SVR4.)
Pagers tend to have better reception than cell phones, at least fairly recently when I last looked this up for my own curiosity. Also, many paging companies have "TAP" servers that you can dial into with a modem to send pages. This is could make a nice last-resort fallback for when a data center has lost network access and you can still provide outbound alerting via a backup landline.
Your argument is that we should wait for a tragedy to make rules to prevent a tragedy.
No, my argument is that telling a 13 year old girl that she has to have her name in a public-facing federal database in order to fly a 9-ounce pink plastic RC copter from a mall kiosk, or face a $20,000 fine will do exactly NOTHING to prevent a bad guy from doing all of the horrible murderous things that we're seeing done with RC toys. Oh, right - there are literally millions of them in the hands of people, with untold millions of flight hours on them, and we're not actually seeing any of that. But you're pretty sure that someone looking to do harm will step up and register their name with the feds, and then write their identifying information on the RC airplane they're going to use to deliberately hurt people? Are you really thinking this through?
The FAA is banned from regulating model aircraft if I recall.
Which is why the Obama administration just instituted their new RC aircraft owner registration system (you have to sign up by the 19th of this month, or face up to $20,000 in fines
Hopefully you're not surprised that an administration that has been found repeatedly by federal courts to have overstepped separation of powers by issuing unconstitutional executive orders would be trying to once again work around the law?
Doesn't matter. Most people who fly RC planes for fun can't afford to fight the administration in court or risk that $20,000 fine. There are a couple of groups trying to take the matter to court, but that will drag out years. In the meantime, we have to play along with the illegal action by the administration.
SYS V needs to go open next, not that overloaded slowlaris, but lean mean SYS V
I was under the impression that the entire POINT of SYS V was for the major UNIX vendors to re-implement the guts of Unix as a clearly, enforceably, proprietary product (after the CONTU recommendations and the resulting copyright law changes explicitly extended copyright to software), then move to it and orphan the original development thread. (This might make opening it a hard sell to the members of the consortium.)
There were at least a couple issues with the proprietary status of the AT&T code:
One issue was that AT&T was still a government-regulated utility monopoly and there were some requirements about disclosing and releasing non-telephone-related inventions they came up with.
The big issue was that, before copyright applied and before software patents were hacked up (by recasting software as one embodiment of, or a component of, a patentable machine or process), the only protection was trade secret and the related contract law. Trade secrets generally stop being enforceable when the secret out of the bag (with some details about whether the claimant contributed to the leak). Bell Labs had shipped code to a LOT of educational institutions. When the U of New South Wales used the System 6 kernel code and an explanation of it as the two-volume text for an Operating System class, the textbooks became an underground classic. This, along with AT&T's benign-neglect licensing policies, led to the burst of little, cheap, generic UNIX boxes, as this was also when microcomputer chips were just becoming powerful enough to do the job.
Up to then a big barrier to entry was that every new machine needed a custom O.S. to deploy, and these were enormous, machine specific, and mostly in assembler. That made it an expensive, undertaking, suitable only for financial giants. But all but under 2,000 lines of Unix was in C, and the entire kernel, which included essentially all the platform-specific code as a subset, was well under 10,000 lines of code. If you had a C compiler and assembler for your new machine, it was a matter of a few man-months to port it and get it up and running. Essentially ALL the utilities and applications came right over. You didn't have to train users, either, because they all worked pretty much just like what they'd used in college.
The game was:
1. Grab a bootleg copy of the code.
2. Port it to your machine and get it working.
3. Go to AT&T and ask for a license "to port Unix to our new machine and sell it."
4. AT&T, as a matter of policy, completely ignores any "violations" you may have committed during the porting phase and cuts you a license at a very reasonable price.
5. You "port Unix in an AMAZINGLY short time" (like the ten minutes it takes to tell Sales to go to market) and you're in business.
6. You (with your new business) and AT&T (with their small cut) slap each other on the back and laugh all the way to the bank. PROFIT! for you. (profit) for AT&T.
7. Because of the policy in 4., everybody ELSE manearly everbody's king a new machine knows they can do the same thing. So many do. AT&T gets a rakeoff from ALL of them. PROFIT! for AT&T. Far more than if they went dog-in-the-manger, held up the first few for all the traffic would bear, and got no more customers for Unix.
And because of this, it was in nearly everbody's interest to NOT challenge the AT&T-proprietary status of Unix. And it stayed this way until SCO's management screwed up and altered step 4. (Even then the case turned on other issues, so it never did come to the point of attacking AT&T's claim that Unix code was proprietary.)
Administration: An ingenious abstraction in politics, designed to receive the kicks and cuffs due to the premier or president. -- Ambrose Bierce