Most of the tools are covered by the GNU GPL, some are public domain, and others have a Berkeley style copyright. To cover the GNU GPL `restrictions', the basic rule is if you give out any binaries, you must also make the source available. For the full details, be sure to read the text of the GNU General Public License (GPL).
The Cygwin API library found in the winsup subdirectory of the source code is also covered by the GNU GPL. By default, all executables link against this library (and in the process include GPL'd Cygwin glue code). This means that unless you modify the tools so that compiled executables do not make use of the Cygwin library, your compiled programs will also have to be free software distributed under the GPL with source code available to all.
Cygnus' Native Win32 GNUPro subscriptions include a commercial license for Cygwin that is more suitable for commercial use of the Cygwin library. Pricing for a GNUPro Subscription starts at $6000 for three developers and includes GNUPro Toolkit, Developer Support, and a commercial-use license for 100 copies of the Cygwin library. Contact info@cygnus.com for more information about this license. All other questions should be sent to the project mailing list cygwin@sourceware.cygnus.com.
Considering the 'unconventional' nature of Crusoe, and the fact it is targeted to mobile processors, I really don't think the 'software' mentioned is Linux-related in the least.
I mean, they have the source to Linux, even without Linus. But what Linus has, that few other people do, is the knowledge and experience necessary to develop an entirely new OS. Which is probably why they hired him in the first place.
... but wasn't NT a joint venture between Microsoft and IBM?
Yeah, but Digital bought into the whole NT thing.. They even ported NT to the Alpha.. Digital, the once mighty minicomputer giant, then started losing a lot of money, and were bought by a PC company.
-joev, former DEC employee, who actually worked in Digital's NT marketing group...
The true test will be whether or not the thing can
Listen to a human
Output to another language.
Have another device listen to that output,
Output back to the original language.
(In other words, box -i english -o mandarin < english.au | box -i mandarin -o english > english2.au) Only then will I be convinced that this isn't crap:^)
Now if OnSale and other online-stores would only switch to Apache, it would make my surfing alot easier. Many times I've been surfing for that special piece of hardware only to find myself drumming my fingers on the desk waiting for their lame server to send me a page or two.
They're probably not slow because of the web server, but because of their particular backend systems... Load balancing is your friend:^)
Then, they added 7 of 9. While most of the viewers today, only watch it because of Jeri Ryan, I think it is a cheap publicity stunt. She adds nothing of value to the series.
How dare you say that! She has the best pair of breasts in the Delta quadrant...
In a way, The Original Series is a lot like this. There was no week to week continuity. There was no defined 'mission': Each week's episode was self-contained, and didn't depend on stuff in *any* other episode.
And it was fun.
That's what has been missing in TNG, DS9, and VOY. I can't watch Voyager, especially after they brought in T of A.
So, my vote is for the anthology series, with maybe a small number of characters who show up more regularly than others.. This way, we could get a marines episode, an academy episode, a 'love story' episode, a Q episode, a 'where are they now' episode, etc..
The studio excuse is that this would be horribly expensive. Well, TOS got by with some *very* clever people, and strong, passionate writing. Not bean counters, attempting to build a strategy that would turn a long-term profit, by studying 'market demographics', etc.
And no more 'use the real-life person generated in the holodeck to remodulate the dilithum crystals with a pulsed-phased tachyon bean emitter module'.
For the record, I think 'portals' are dumb, too. But, The Masses seem to want pretty graphics, and My News next to My Weather next to web based email (Ack!). It's a market-driven phenomenon, and would quickly die out of people would stop using them.
So, I wouldn't blame The Man for this, blame the people too lazy to explore what's out there. There were pioneers on the 'net, blazing new trails, as it were... Now, the homesteaders are coming in, building towns and stripmalls.
One of my favorites is the movie GUI. Anytime you see people using computers in the movies, the windows ALWAYS zoom, make neato swooshing sounds, the mouse clicks always are audiable (*click!*), etc. etc.
A buddy of mine coined this interface (as seen in Hackers) "FreeLSD"...:^)
Perhaps I should have included requirements specification, as well as functional design in the original guideline. The implementation phase is relatively high because I'm including unit testing as part of the implementation cycle. After the dust settles, the whole thing needs to be tested in many ways, including input verification, as well as stress testing. This will hopfully iron out any unforseen situations, like thread deadlocks and such introduced in the implementation phase. However, I completely agree that the design, interface contracts and all, should be committed before implementation. Unfortunately, many parts of these specifications depend on integration with other, third-party software whose interface specifications or documentation may not be complete.
How much testing you do shouldn't really be set down as any predesignated percentage, AFAIC.. You test it until it's done being tested.
Unfortunately, my clients have strict deadlines that need to be met, for business reasons. Each day of slippage can result in a loss of hundreds of thousands of dollars for these folks. Which is why I spend a lot of time pushing back on them when they ask for more features after the design phase.
And, there are important constratints around this. For example, *no* features are to be added after the design phase, unless it is
absolutely critical
the requestors understand the implications to the schedule (ie, more features = more implementation = more testing)
In the real world, however, the PHBs financing the operation can't get this concept through their thick skulls. When this happens to me, I tell then my recommendations; it's their dime, they can ignore it if they want to, but the reason they pay me (I hope) is that I know what I'm talking about. I've seen this happen before, and if something goes wrong, it's NMFP.
They can feel free to buy more of my time to fix the problems they brought upon themselves.
Overall, Athlon achieves a higher level of performance than the Pentium III at equal speeds, leading to crisper, more realistic graphics, according to testers.
Well, *I'm* not gonna buy it unless it makes my sound more realistic, too.
Let's see.. Out of my male geek acquaintences in Boston and SF, 2 are engaged, 4 are living with their long-term SOs, and a few other do the love-em-and-leave-em thing.
I seem to be the only one out of my little circle who this article describes fairly well:^/ And that's probably due to the fact I'm on the road almost all the time.
That notwithstanding, it's still a fairly low percentage.
That's it. That's the only question they should ask. S-1 statements are full of warnings in all caps that say
THIS OFFERING INVOLVES A HIGH DEGREE OF RISK. YOU SHOULD CAREFULLY CONSIDER THE RISKS DESCRIBED BELOW AND THE OTHER INFORMATION IN THIS PROSPECTUS BEFORE DECIDING TO INVEST IN THE SHARES OF COMMON STOCK.
The Libertarians would probably rather see NASA cut completely, and have space exploration be taken over by private industry, academia, and individuals.
Then again, under the Libertarian ideal, you wouldn't be taxed as much (or at all!), and could donate that money to some space development organization, instead of spending it meddling in other nations' civil wars..
Slashdot Mirror
What are the licensing terms?
Most of the tools are covered by the GNU GPL, some are public domain, and others have a Berkeley style copyright. To cover the GNU GPL `restrictions', the basic rule is if you give out any binaries, you must also make the source available. For the full details, be sure to read the text of the GNU General Public License (GPL).
The Cygwin API library found in the winsup subdirectory of the source code is also covered by the GNU GPL. By default, all executables link against this library (and in the process include GPL'd Cygwin glue code). This means that unless you modify the tools so that compiled executables do not make use of the Cygwin library, your compiled programs will also have to be free software distributed under the GPL with source code available to all.
Cygnus' Native Win32 GNUPro subscriptions include a commercial license for Cygwin that is more suitable for commercial use of the Cygwin library. Pricing for a GNUPro Subscription starts at $6000 for three developers and includes GNUPro Toolkit, Developer Support, and a commercial-use license for 100 copies of the Cygwin library. Contact info@cygnus.com for more information about this license. All other questions should be sent to the project mailing list cygwin@sourceware.cygnus.com.
Not unless Linus licenses the name to them.. Linus owns the 'Linux' name...
-joev
I mean, they have the source to Linux, even without Linus. But what Linus has, that few other people do, is the knowledge and experience necessary to develop an entirely new OS. Which is probably why they hired him in the first place.
Yeah, but Digital bought into the whole NT thing.. They even ported NT to the Alpha.. Digital, the once mighty minicomputer giant, then started losing a lot of money, and were bought by a PC company.
-joev, former DEC employee, who actually worked in Digital's NT marketing group...
- Listen to a human
- Output to another language.
- Have another device listen to that output,
- Output back to the original language.
(In other words, box -i english -o mandarin < english.au | box -i mandarin -o english > english2.au) Only then will I be convinced that this isn't crap-joev
They're probably not slow because of the web server, but because of their particular backend systems... Load balancing is your friend :^)
-joev
How dare you say that! She has the best pair of breasts in the Delta quadrant ...
Q.E.D.
And it was fun.
That's what has been missing in TNG, DS9, and VOY. I can't watch Voyager, especially after they brought in T of A.
So, my vote is for the anthology series, with maybe a small number of characters who show up more regularly than others.. This way, we could get a marines episode, an academy episode, a 'love story' episode, a Q episode, a 'where are they now' episode, etc..
The studio excuse is that this would be horribly expensive. Well, TOS got by with some *very* clever people, and strong, passionate writing. Not bean counters, attempting to build a strategy that would turn a long-term profit, by studying 'market demographics', etc.
And no more 'use the real-life person generated in the holodeck to remodulate the dilithum crystals with a pulsed-phased tachyon bean emitter module'.
So, I wouldn't blame The Man for this, blame the people too lazy to explore what's out there. There were pioneers on the 'net, blazing new trails, as it were... Now, the homesteaders are coming in, building towns and stripmalls.
A buddy of mine coined this interface (as seen in Hackers ) "FreeLSD"... :^)
Heh. (for the sarcasm-impaired)
Linus didn't have a schedule to keep, or clients to satisfy :^)
How much testing you do shouldn't really be set down as any predesignated percentage, AFAIC.. You test it until it's done being tested.
Unfortunately, my clients have strict deadlines that need to be met, for business reasons. Each day of slippage can result in a loss of hundreds of thousands of dollars for these folks. Which is why I spend a lot of time pushing back on them when they ask for more features after the design phase.
- 33% design
- 33% implementation
- 33% testing
And, there are important constratints around this. For example, *no* features are to be added after the design phase, unless it is- absolutely critical
- the requestors understand the implications to the schedule (ie, more features = more implementation = more testing)
In the real world, however, the PHBs financing the operation can't get this concept through their thick skulls. When this happens to me, I tell then my recommendations; it's their dime, they can ignore it if they want to, but the reason they pay me (I hope) is that I know what I'm talking about. I've seen this happen before, and if something goes wrong, it's NMFP.They can feel free to buy more of my time to fix the problems they brought upon themselves.
Well, *I'm* not gonna buy it unless it makes my sound more realistic, too.
*sound of hand smacking forehead*
http://developer.java.sun.com/developer/technicalA rticles/ConsumerProduc ts/JavaTanks/tankdemo.tar.gz
Whoa.. With a little bit of creative artwork...
Hey, if they're GPLed, do your part and post the source! :^)
Yow.. This resembles the CIA (or CDC? Can't recall the acronym used) in Snowcrash...
I seem to be the only one out of my little circle who this article describes fairly well :^/ And that's probably due to the fact I'm on the road almost all the time.
That notwithstanding, it's still a fairly low percentage.
That's it. That's the only question they should ask. S-1 statements are full of warnings in all caps that say
Then again, under the Libertarian ideal, you wouldn't be taxed as much (or at all!), and could donate that money to some space development organization, instead of spending it meddling in other nations' civil wars..
I believe it's designed with such a huge space, so routers can be more efficient (ie, don't have to break apart subnets, etc.)
My Tulip (040) runs just fine under BeOS...