... yeah, but Debian also doesn't have a DSA on this bug that I can find, no recent release of 2.4.27 (ie: no backported fixes) and no release of 2.4.28.
Love Debian, but still trying to find the best way to patch my Debian machines.
... yes, the CIA World Factbook describes Palmyra Atoll as "about 20 times the size of The Mall in Washington, DC" with a population of 4-20 nature conservancy staff. And that's only where the rediculousness starts.
Took a quick run through Mandrake Move, and I think I've decided it's great for Mandrake users, but not as a Windows migration path. Here are a couple of things I noticed:
- fat partitions were recognized and mounted under/mnt, but at easy to find icon would be good
- could not find configuration or documentation about palm sync'ing.
- menu items are nicely named by function rather than program name, but sometimes understate what they do. ie: with a menu option like 'create a web page' I would expect a WYSIWIG editor, instead it launches Quanta, a down and dirty HTML editor.
- user intervetion is required on boot to do things like select language. This means that you really do need the USB key enabled version so that you can store these settings.
That said, it booted and configured itself properly, looks pretty, and seems to have lots of apps.
A great way to handle integration testing is to participate in a group that does it together like, say Debian. I really appreciate the community's work to make sure that everything works.
It looks like the Loki order page is swamped right now (comming back with mysql too many connections messages), so maybe the community is doing it's bit.
So.. if you like games, or like companys that work hard to make GNU/Linux more popular follow me over to Loki with a credit card.
Continually extendable method and apparatus for the exclusive registration of processes or ideas
What is claimed is:
1. A method of describing and registering a process or idea to gain exclusive rights of use for a period of time, said method comprising:
applicaton made by the first party;
"examination" made by a second party;
legislation made by the governing party.
2. The method of registration described in claim 1 furthur comprising:
the use of many long words and akward phrases to obscure the true process or idea from all, particularly those already employing said process or idea.
3. The method of registration described in claim 1 furthur comprising:
the use of many long words and vague phrases to allow the applicants legal staff to enhance the extent of the original idea at a later date.
4. The method of registration described in claim 1 furthur comprising:
the use of many long words and repetitive phrases to lul all parties involved to sleep by the end of the first few paragraphs.
5. The method of registration described in claim 1 furthur comprising:
the use of money, influence, gifts, liquor, partys, favours, or other substance of worth or precieved worth to achieve any of the following:
speed the registration process;
augment the "examiner's" judgement;
lengthen the period of time for which the rights are granted.
6. An apparatus to administer the registration process described in claim 1 comprising:
a building, or shelter, or location at which to meet;
a slot, or bag, or box, or container, or electronic store in which new descriptions of processes or ideas arrive for "examination";
a backlog, or time keeping device, or three hour work day, or "management" by which an enormous passage of time occurs;
a person, or group of persons, or roulette wheel, or mammal, or scale, or contest deciding the fate of each new description;
an announcement, or posting, or head nod, or thumbs up, or mouse click, or any single action denoting the processes or ideas to be granted exclusive rights.
7. The administration apparatus described in claim 6 furthur comprising:
a shiny web interface for the appearance of transparency.
8. The administration apparatus described in claim 6 furthur comprising:
the introduction of substances mentioned in claim 5, or other parties who may not be mentioned in this document;
I disagree, I am writing some moderatly involved pages right now to be released publicly and would be pretty ticked to see someone add a feature and not return it to the public. Right now my solution will probably be to write my own extension to GPL, but I would prefer a uniform system to avoid licence conflicts that can be so pesky.
At the CFP conference in Toronto Tim O'Reilly pointed out a possible weakness in the GPL. If websites, like www.onlinephotolab.com, become more and more like applications, the GPL's intention to keep freely developed software open and free is not met, the website's code can be closed even if it includes GPL code because it is not being distributed. This extends beyond only websites to any client server setup over the net.
What plans are there to address this issue? Might a new, stronger licence be developed that web developers might choose to keep their code free if they desire?
Is it time to get ready to fork? It is still a bit premature, let's wait and see how things work out, but the code for most of these sites is GPL, as long as we have that then if things start to smell fishy then we run.
What really has me curious is the chemical/electrical interfacing. From the Times article I'm assuming that what they have right now is inorganic, so are the gates still transfering electrons? Does anyone know of work in this area?
I agree, OGG support would be easy and should be there
... yeah, but Debian also doesn't have a DSA on this bug that I can find, no recent release of 2.4.27 (ie: no backported fixes) and no release of 2.4.28.
Love Debian, but still trying to find the best way to patch my Debian machines.
(please let me know if I'm missing something)
... yes, the CIA World Factbook describes Palmyra Atoll as "about 20 times the size of The Mall in Washington, DC" with a population of 4-20 nature conservancy staff. And that's only where the rediculousness starts.
IANAL, but I believe you have to apply to be a registered charity in Canada with the CRA. See the documentation to become a registered charity.
Took a quick run through Mandrake Move, and I think I've decided it's great for Mandrake users, but not as a Windows migration path. Here are a couple of things I noticed: /mnt, but at easy to find icon would be good
- fat partitions were recognized and mounted under
- could not find configuration or documentation about palm sync'ing.
- menu items are nicely named by function rather than program name, but sometimes understate what they do. ie: with a menu option like 'create a web page' I would expect a WYSIWIG editor, instead it launches Quanta, a down and dirty HTML editor.
- user intervetion is required on boot to do things like select language. This means that you really do need the USB key enabled version so that you can store these settings.
That said, it booted and configured itself properly, looks pretty, and seems to have lots of apps.
A great way to handle integration testing is to participate in a group that does it together like, say Debian. I really appreciate the community's work to make sure that everything works.
UnitedLinux appears to be misleading readers by posing this question in their FAQ:
"Free for non-commercial" is not similar to the "Absolutely free for anyone" availability of GNU/Linux
Yes, but as seen in the case of a certain DeCSS author, the USA seems to think that American law does apply to the entire world.
The fear is unfortunate, but understandable in my mind.
It looks like the Loki order page is swamped right now (comming back with mysql too many connections messages), so maybe the community is doing it's bit.
So.. if you like games, or like companys that work hard to make GNU/Linux more popular follow me over to Loki with a credit card.
Continually extendable method and apparatus for the exclusive registration of processes or ideas
What is claimed is:
1. A method of describing and registering a process or idea to gain exclusive rights of use for a period of time, said method comprising:
applicaton made by the first party;
"examination" made by a second party;
legislation made by the governing party.
2. The method of registration described in claim 1 furthur comprising:
the use of many long words and akward phrases to obscure the true process or idea from all, particularly those already employing said process or idea.
3. The method of registration described in claim 1 furthur comprising:
the use of many long words and vague phrases to allow the applicants legal staff to enhance the extent of the original idea at a later date.
4. The method of registration described in claim 1 furthur comprising:
the use of many long words and repetitive phrases to lul all parties involved to sleep by the end of the first few paragraphs.
5. The method of registration described in claim 1 furthur comprising:
the use of money, influence, gifts, liquor, partys, favours, or other substance of worth or precieved worth to achieve any of the following:
speed the registration process;
augment the "examiner's" judgement;
lengthen the period of time for which the rights are granted.
6. An apparatus to administer the registration process described in claim 1 comprising:
a building, or shelter, or location at which to meet;
a slot, or bag, or box, or container, or electronic store in which new descriptions of processes or ideas arrive for "examination";
a backlog, or time keeping device, or three hour work day, or "management" by which an enormous passage of time occurs;
a person, or group of persons, or roulette wheel, or mammal, or scale, or contest deciding the fate of each new description;
an announcement, or posting, or head nod, or thumbs up, or mouse click, or any single action denoting the processes or ideas to be granted exclusive rights.
7. The administration apparatus described in claim 6 furthur comprising:
a shiny web interface for the appearance of transparency.
8. The administration apparatus described in claim 6 furthur comprising:
the introduction of substances mentioned in claim 5, or other parties who may not be mentioned in this document;
I disagree, I am writing some moderatly involved pages right now to be released publicly and would be pretty ticked to see someone add a feature and not return it to the public. Right now my solution will probably be to write my own extension to GPL, but I would prefer a uniform system to avoid licence conflicts that can be so pesky.
At the CFP conference in Toronto Tim O'Reilly pointed out a possible weakness in the GPL. If websites, like www.onlinephotolab.com, become more and more like applications, the GPL's intention to keep freely developed software open and free is not met, the website's code can be closed even if it includes GPL code because it is not being distributed. This extends beyond only websites to any client server setup over the net.
What plans are there to address this issue? Might a new, stronger licence be developed that web developers might choose to keep their code free if they desire?
Is it time to get ready to fork? It is still a bit premature, let's wait and see how things work out, but the code for most of these sites is GPL, as long as we have that then if things start to smell fishy then we run.
Sounds reasonable?
What really has me curious is the chemical/electrical interfacing. From the Times article I'm assuming that what they have right now is inorganic, so are the gates still transfering electrons? Does anyone know of work in this area?