World + dog seems to have some sort of opinion about what.NET actually is, but the one thing practically everybody has agreed upon up to now is that MS.NET does not contain anything new.
Well then - this is about a patent application, not a patent grant. A patent gets a lot harder and more expensive to fight once it's been granted (seems to take a lawsuit), so the most productive thing to do right now is to dig up sufficient evidence of 'prior art' to make sure this patent is never granted in the first place.
Demanding a per CPU fee from Linux users and/or distributers for alleged patent infringements would be the single most stupid thing SCO could possibly do.
This actually reminds me of the time (1987) IBM launched their MCA bus based PS/2 line. IBM then reportedly demanded a 'per system ever produced' fee from clone makers wanting to license the MCA technology in order to make clones/compatibles. Unsurprisingly, a few months later we had the EISA bus, a few years on the MCA bus is extinct and the world runs on PCI. Strategic blunders like these have killed off large corporations in the past.
Then again, if the real target is a certain software marketing outfit a bit further north on the US west coast, the process might reveal a few more skeletons in various corporate closets. That might of course turn interesting if you're into that sort of thing.
There is no other way to put it. Docbook, in either SGML or XML variants, is the way to go. Period. It has all the elements you will ever need for software docs, your data will always be readble (sgml or xml is text), you can integrate documentation "build" in your make files, you can include or exclude content based on conditionals, the system forces you to think and structure your material sensibly.
Installing all the necessary components by hand can be a rather painful excersise for the uninitiated, though. It's usually best to install your favourite distribution's docbook package. IIRC on Debian all it took was an "apt-get install docbook", your mileage may vary elsewhere but I hear FreeBSD has everything you need, nicely packaged.
You would do well to read the "duck book" (online at http://docbook.org or available from O'Reilly). Other useful resources are the FreeBSD project's documentation primer at among other places http://www.freebsd.org/docproj/sgml.html. If you ever need to set up a windows machine for sensible doc writing, you'll find Markus Hoenicka's guide at http://ourworld.compuserve.com/homepages/hoenicka_ markus/ indispensable.
We had 8 pigeons at the pinging end and for some reason only six at the other. After the first four replies were sent, the remaining two pigeons escaped, leaving us in the 'carrier lost' state.
Slashdot Mirror
World + dog seems to have some sort of opinion about what .NET actually is, but the one thing practically everybody has agreed upon up to now is that MS.NET does not contain anything new.
Well then - this is about a patent application, not a patent grant. A patent gets a lot harder and more expensive to fight once it's been granted (seems to take a lawsuit), so the most productive thing to do right now is to dig up sufficient evidence of 'prior art' to make sure this patent is never granted in the first place.
It would be safe to assume that "IP" in this case expands to "Intellectual Property", not "Internet Protocol".
Demanding a per CPU fee from Linux users and/or distributers for alleged patent infringements would be the single most stupid thing SCO could possibly do.
This actually reminds me of the time (1987) IBM launched their MCA bus based PS/2 line. IBM then reportedly demanded a 'per system ever produced' fee from clone makers wanting to license the MCA technology in order to make clones/compatibles. Unsurprisingly, a few months later we had the EISA bus, a few years on the MCA bus is extinct and the world runs on PCI. Strategic blunders like these have killed off large corporations in the past.
Then again, if the real target is a certain software marketing outfit a bit further north on the US west coast, the process might reveal a few more skeletons in various corporate closets. That might of course turn interesting if you're into that sort of thing.
There is no other way to put it. Docbook, in either SGML or XML variants, is the way to go. Period. It has all the elements you will ever need for software docs, your data will always be readble (sgml or xml is text), you can integrate documentation "build" in your make files, you can include or exclude content based on conditionals, the system forces you to think and structure your material sensibly.
_ markus/ indispensable.
Installing all the necessary components by hand can be a rather painful excersise for the uninitiated, though. It's usually best to install your favourite distribution's docbook package. IIRC on Debian all it took was an "apt-get install docbook", your mileage may vary elsewhere but I hear FreeBSD has everything you need, nicely packaged.
You would do well to read the "duck book" (online at http://docbook.org or available from O'Reilly). Other useful resources are the FreeBSD project's documentation primer at among other places http://www.freebsd.org/docproj/sgml.html. If you ever need to set up a windows machine for sensible doc writing, you'll find Markus Hoenicka's guide at http://ourworld.compuserve.com/homepages/hoenicka
Does this mean that the freebsd sound has better-than-linux support for the Yamaha sound chip as well?
We had 8 pigeons at the pinging end and for some reason only six at the other. After the first four replies were sent, the remaining two pigeons escaped, leaving us in the 'carrier lost' state.