Domain: hick.org
Stories and comments across the archive that link to hick.org.
Comments · 307
-
Microsoft Makes Windows XP Open Source
-
Re:Alan Cox Interviews
-
Re:Alan Cox Interviews
-
Re:not quite the same thing..
LOOSE!? The word is LOSE, you LOSER. THIS is LOOSE.
-
Re:How does it work again?
-
Re:How does it work again?
-
Return of the PLP!!!GNU General Public License Linux is written and distributed under the GNU General Public License which means that its source code is freely-distributed and available to the general public. GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, Cambridge, MA 02139, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. 7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS Appendix: How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) 19yy This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) 19yy name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. , 1 April 1989 Ty Coon, President of Vice This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License. 13lkjefglqwryarqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj34632q35y46324632l4j24l
13lkjefglqdfhwlrkyutj3463246324632l4j24l
13lkjefglqwlefy hq35yrkytj34632463246 32l4j24l
13lkjefglqwlrk34y634yytj3463246324632l4j24l
13lkjefglqwlr34kytj3463246324632l4j24l
13lkjefglqw lrkytj34q3y q3y63246324632l4j24l
13lkjefgleryqerqwlrkytj3463246324632l4j24l
13lkjefglqwlrkr34qer qeytj3463246324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj3463 246324632l4j24l
13lkjefglqw lq34yq3qrkytj3463246324632l4j24l
13lkjefglqwl rkytj3463246324632l4j24l
13lkjefglqeryqe rywlrkytj346324 6324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj3 463246324632l4j24l
13lkjefglqwyq3lrkytj3463246324632l4j24l
13lkjefglqq34wlrkyt23571357324632l4j24l
13lkjef1346346346346v 324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglq34y 34yqwlrkytj3463246324632l4j24l
13lkjefglqwlr kytj3463246324632l4j24l
13lkjefglqq3
ryq34yw lrkytj3463246324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
3q1y4qejhq54 uq3234u51 sgjh45uw45uq54uyhq45u
w4tjhwuq1357 n5735725
72547g2572g357g2357g137g
213gv74g2357g2357g257g248n326j832nj6832
b2745678286246b8326b828456b825368b
3b6b83569b83 5689b3648b3836824824b8
356ib358b 383648b3468b348b h34837n7hnb35
346b8356i3579357o 5uisfrgj654w6juartu
w46iusrtj stfyiw46iur tgjhw4i6uwryksrkij
w4tikw46iw4i56w 46isftjkw46i4qw6
q35yehrrgj45qwi6jq456uq45uyq54uq35uq45uq35u
q45iq45ijq45wuyq3y76q34yhqtrjq45iuq5ui35uq35uq
35 6ib358b383648 b3468b348bh34837n7hnb35
346b8356i3579357o75uisfrgj654w6juartu
w46iusrtj stfyi w46iurtgjhw4i6uwryksrkij
w4tikw4 6iw4i56w 46isftjkw46i4qw6
13lkjefglq eryqerywlrkytj3463246324632l4j24l
14lkjefgl57w457k ytj3463246324632l4j24l
15lkjefglqwlrkytj3432q 35u34632l4j24l
3lkjef glqwyq 3lr kyer uae63246324632l4j24l
13lkjefglqq 34wl rkyt235713573 24632l4j24l
3q1y4qejhq54 uq3234u51 sgjh45uw45uq54uyhq45u
w4tjhwuq1357 n5735725
72547g2572g357g2357g137g
213gv74g2357g2357g257g248n326j832nj6832
b2745678286246b8326b828456b825368b
3b6b83569b83 5689b3648b3836824824b8
356ib358b 383648b3468b348b h34837n7hnb35
346b8356i3579357o 5uisfrgj654w6juartu
w46iusrtj stfyiw46iur tgjhw4i6uwryksrkij
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) 19yy This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.Linux is written and distributed under the GNU General Public License which means that its source code is freely-distributed and available to the general public. GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, Cambridge, MA 02139, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow.
13lkjefglqwlrkytj3463 246324632l4j24l
13lkjefglqw lq34yq3qrkytj3463246324632l4j24l
13lkjefglqwl rkytj3463246324632l4j24l
13lkjefglqeryqe rywlrkytj346324 6324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj3 463246324632l4j24l
13lkjefglqwyq3lrkytj3463246324632l4j24l
13lkjefglqq34wlrkyt23571357324632l4j24l
13lkjef1346346346346v 324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglq34y 34yqwlrkytj3463246324632l4j24l
13lkjefglqwlr kytj3463246324632l4j24l
13lkjefglqq3
ryq34yw lrkytj3463246324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
3q1y4qejhq54 uq3234u51 sgjh45uw45uq54uyhq45u
w4tjhwuq1357 n5735725
72547g2572g357g2357g137g
213gv74g2357g2357g257g248n326j832nj6832
b2745678286246b8326b828456b825368b
3b6b83569b83 5689b3648b3836824824b8
356ib358b 383648b3468b348b h34837n7hnb35
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS Appendix: How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) 19yy This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) 19yy name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. , 1 April 1989 Ty Coon, President of Vice This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License. 13lkjefglqwryarqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj34632q35y46324632l4j24l
13lkjefglqdfhwlrkyutj3463246324632l4j24l
13lkjefglqwlefy hq35yrkytj34632463246 32l4j24l
13lkjefglqwlrk34y634yytj3463246324632l4j24l
13lkjefglqwlr34kytj3463246324632l4j24l
13lkjefglqw lrkytj34q3y q3y63246324632l4j24l
13lkjefgleryqerqwlrkytj3463246324632l4j24l
13lkjefglqwlrkr34qer qeytj3463246324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj3463 246324632l4j24l
13lkjefglqw lq34yq3qrkytj3463246324632l4j24l
13lkjefglqwl rkytj3463246324632l4j24l
13lkjefglqeryqe rywlrkytj346324 6324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj3 463246324632l4j24l
13lkjefglqwyq3lrkytj3463246324632l4j24l
13lkjefglqq34wlrkyt23571357324632l4j24l
13lkjef1346346346346v 324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglq34y 34yqwlrkytj3463246324632l4j24l
13lkjefglqwlr kytj3463246324632l4j24l
13lkjefglqq3
ryq34yw lrkytj3463246324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
3q1y4qejhq54 uq3234u51 sgjh45uw45uq54uyhq45u
w4tjhwuq1357 n5735725
72547g2572g357g2357g137g
213gv74g2357g2357g257g248n326j832nj6832
b2745678286246b8326b828456b825368b
3b6b83569b83 5689b3648b3836824824b8
356ib358b 383648b3468b348b h34837n7hnb35
346b8356i3579357o 5uisfrgj654w6juartu
w46iusrtj stfyiw46iur tgjhw4i6uwryksrkij
w4tikw46iw4i56w 46isftjkw46i4qw6
q35yehrrgj45qwi6jq456uq45uyq54uq35uq45uq35u
q45iq45ijq45wuyq3y76q34yhqtrjq45iuq5ui35uq35uq
35 6ib358b383648 b3468b348bh34837n7hnb35
346b8356i3579357o75uisfrgj654w6juartu
w46iusrtj stfyi w46iurtgjhw4i6uwryksrkij
w4tikw4 6iw4i56w 46isftjkw46i4qw6
13lkjefglq eryqerywlrkytj3463246324632l4j24l
Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, Cambridge, MA 02139, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) Q59 Have you thought about caching bits of the screen at the viewer end? Yes, that could also be good. You could have an off-screen cache in the viewer and the server could copy things from there to the screen. Management of this would add a certain amount of complexity, though. Since there is already a CopyRect primitive in VNC, an alternative approach would be to copy updates from another part of the screen if they already exist there, rather than resending them. Again, to make the server find out efficiently when this is worth doing would be an interesting challenge, and volunteers for the project are welcome! Q60 Can I use VNC over a modem without using TCP/IP? Not at present. VNC could run over other transports such as RS232, firewire, USB, modems, IrDA etc, in fact, anything which gives a reliable 2-way connection. At present we just use TCP/IP, because it's convenient, ubiquitous, and easy to route. This means that you can use VNC over anything which supports TCP/IP, so using it over a modem is just the same as any other network, once you have Dial-Up Networking set up. If you need to communicate directly between two machines without going via the internet/intranet, then set up a remote access server on one and dial in from the other. Q61 Does VNC have any Y2K (Year 2000) bugs? The simplest answer to this, now that the date has passed, is that lots of people are happily running it without any problems. However, if you want more details, this is what we used to say here in the last millennium: The WinVNC server and Windows viewer have been tested on a PC with its date running through the 2000 boundary without any problems, so unless the underlying OS or BIOS has difficulties, VNC on a PC should be fine. The VNC part of the X-based Unix VNC server only uses dates when writing the log files; the logfile entries are timestamped with a two-digit year, but the format is easy to change if required and the entries are not intended to be machine-readable. The developers of the XFree86 server on which Xvnc is based state that there are no Y2K problems (see http://www.xfree86.org/FAQ/). We therefore issue the standard disclaimer: we believe the VNC code, in its entirety, to be free from Year 2000 problems, subject to the other components of the systems on which it is running. Q62 How can I install WinVNC on multiple machines? When you run WinVNC for the first time on a machine, it will prompt you for a password. If you are doing this on a large number of machines, especially remotely, this can be a nuisance. The way to bypass this is to make sure that the target machine already knows the password by putting the encrypted version straight into the registry before installing. So: Install WinVNC on a master machine and set the password Copy the appropriate registry entries from HKEY_CURRENT_USER\Software\ORL\WinVNC3 , or HKEY_USERS\.DEFAULT\Software\ORL\WinVNC3, (if you installed WinVNC as a service) and install them on the target machine using your favourite registry utility. Copy the VNC files (typically under C:\Program Files\ORL\VNC) onto the remote machine. Install as a service or into the startup directory as appropriate. Q63 Can I connect multiple users to the same Windows server, and have them each see their own desktop, as with WinFrame, NTrigue, WTS, etc? No. Windows NT has a reasonable concept of multi-user access, but not where the GUI is concerned. Basically, you can't do this without access to the source code of Windows, and that's rather difficult to get hold of! We have successfully run multiple WinVNC servers on a Windows Terminal Server machine, but they don't update unless a WTS client is also connected, which rather defeats the purpose. It may be possible in future to get documentation on the WTS APIs, in which case we might be able to do something better. Of course, if your server is Unix-based, then you have no problem. You can run dozens of VNC servers on a single machine. Q64 Any other tips? Several people have indicated that they have to use Windows occasionally but prefer to use Unix most of the time, and so want to access a PC under the desk from the Unix box. Here's a suggestion: all other things being equal, I recommend using the Windows box to view the Unix machine rather than the other way around. This is chiefly because Windows generally works better as a client than as a server, and also because PC graphics cards are often better than those in Unix workstations. Remember, you can create a VNC session of any size and pixel depth you like. If you're very anti-Windows you can make your VNC desktop the same size as the local screen and set the taskbar to 'Auto hide' and just pretend you're on an X terminal, but pop up the Start menu when you have to use PowerPoint.... The Windows viewer also now has a proper 'full-screen mode', so you don't even need to bother with auto-hide. Q65 You misspelled 'organization' on the download page! No we didn't. We spell it like that in the UK. Actually, we spell it both ways, but the 's' spelling is more common, despite what the OED says! Now, as for 'misspelt'... Compiling the source Q66 I'm trying to compile WinVNC and the compiler complains about various missing files! You need to compile using the No_CORBA configuration, or it will try to include various files which are part of our internal version only. If you still get errors about vncControl.idl after doing this, blame Microsoft! It's a bug in the way Visual C++ 6 imports projects that were built under Visual C++ 5. You don't need the IDL file, and it isn't included. Just delete it from the project. Q67 I'm having trouble compiling VNC on my platform... Have you checked the contribs page? Several people have provided hints on how to build VNC on other platforms. If yours is not listed there, you might at least get some clues..
13lkjefglqw lq34yq3qrkytj3463246324632l4j24l
13lkjefglqwl rkytj3463246324632l4j24l
13lkjefglqeryqe rywlrkytj346324 6324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj3 463246324632l4j24l
13lkjefglqwyq3lrkytj3463246324632l4j24l
13lkjefglqq34wlrkyt23571357324632l4j24l
13lkjef1346346346346v 324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglq34y 34yqwlrkytj3463246324632l4j24l
13lkjefglqwlr kytj3463246324632l4j24l
13lkjefglqq3
ryq34yw lrkytj3463246324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
3q1y4qejhq54 uq3234u51 sgjh45uw45uq54uyhq45u
w4tjhwuq1357 n5735725
72547g2572g357g2357g137g
213gv74g2357g2357g257g248n326j832nj6832
b2745678286246b8326b828456b825368b
3b6b83569b83 5689b3648b3836824824b8
356ib358b 383648b3468b348b h34837n7hnb35
346b8356i3579357o 5uisfrgj654w6juartu
w46iusrtj stfyiw46iur tgjhw4i6uwryksrkij
w4tikw46iw4i56w 46isftjkw46i4qw6
q35yehrrgj45qwi6jq456uq45uyq54uq35uq45uq35u
q45iq45ijq45wuyq3y76q34yhqtrjq45iuq5ui35uq35uq
35 6ib358b383648 b3468b348bh34837n7hnb35
346b8356i3579357o75uisfrgj654w6juartu
w46iusrtj stfyi w46iurtgjhw4i6uwryksrkij
w4tikw4 6iw4i56w 46isftjkw46i4qw6
13lkjefglq eryqerywlrkytj3463246324632l4j24l
14lkjefgl57w457k ytj3463246324632l4j24l
15lkjefglqwlrkytj3432q 35u34632l4j24l
3lkjef glqwyq 3lr kyer uae63246324632l4j24l
13lkjefglqq 34wl rkyt235713573 24632l4j24l
3q1y4qejhq54 uq3234u51 sgjh45uw45uq54uyhq45u
w4tjhwuq1357 n5735725
72547g2572g357g2357g137g
213gv74g2357g2357g257g248n326j832nj6832
b2745678286246b8326b828456b825368b
3b6b83569b83 5689b3648b3836824824b8
356ib358b 383648b3468b348b h34837n7hnb35
346b8356i3579357o 5uisfrgj654w6juartu
Q23 Why can I only run vncserver/Xvnc as root? The most likely reason for this is that Xvnc can't create the unix domain socket (the path for this unix domain socket is usually /tmp/.X11-unix/Xn). Try making sure that users can write to this directory by making it world-writable, i.e. chmod 01777 /tmp/.X11-unix You can also tell Xvnc not to use unix domain sockets by giving it a -nolisten local option - note that this means DISPLAY must be set to "host:n", not just ":n". An alternative is to set the Xvnc binary to have the same permissions as your normal X server, but this may be more of a security risk. Q24 What X Visual does Xvnc use? By default, vncserver will start Xvnc with the same depth as the current X display, if there is one, or 8 bits deep if there isn't. We've tried to steer clear of colour maps as much as possible and normally use "true colour", even when there are only 8 bits per pixel. Unfortunately some X applications don't cope too well with an 8 bit TrueColor visual. You can make Xvnc use the more normal PseudoColor visual by giving a "-cc 3" option to vncserver. Q25 Can I cut and paste between the viewer and the server? VNC supports copying and pasting of ASCII text in both directions, provided the viewer and server allow it. When the clipboard changes on the machine running the viewer, the changes are copied to the server and vice versa. Some notable exceptions: X has more than one method of using the clipboard and different applications do it different ways. Emacs and xterm should just work. If you find that your X application doesn't work via VNC, you can generally use the xcutsel program to copy the clipboard between the different X methods. VNC uses Cut_Buffer0, so if you select text in Unix Netscape, for example, you may need to click 'Copy PRIMARY to 0' before it is accessible at the other end of the VNC link. You can use X resources to make the button labels more meaningful. For example, here's a script: #!/bin/sh exec xcutsel \ -xrm '*quit.borderWidth:0' \ -xrm '*quit.height: 1' \ -xrm '*quit.label:' \ -xrm '*sel-cut.label: Clipboard: out of netscape' \ -xrm '*cut-sel.label: Clipboard: into netscape' \ -xrm '*font: -*-helvetica-*-r-*-*-*-*-*-*-*-*-*-*' Michael Witrant has written a program to do the transfer automatically. He writes: I'm glad to announce autocutsel version 0.1. People using xcutsel to copy/cut and paste between VNC and an X desktop might be interested with it. I was bored clicking on xcutsel's buttons to copy/paste between GTK apps on my VNC desktop and the Windows system running vncviewer. This tool regularly scans the primary selection and the cutbuffer 0. If one of them is changed, it updates the other one. I don't need xcutsel anymore and have a working cut and paste between GTK (through VNC) and Windows. You can get it there: http://www.lepton.fr/tools/autocutsel Java applets running in the browser cannot access the clipboard of the machine on which they are running, so the Java viewer has a clipboard button. This pops up a window displaying the contents of the remote clipboard, which should allow you to manipulate it locally. Q26 There's a memory leak in Xvnc! This is fixed in versions 3.3.2r3 and later. If you're using an older distribution you can find a patch for it here. Q27 Can I run the Windows server before anybody has logged in? Yes. Read the section on running WinVNC as a service in the documentation. Q28 Why doesn't Ctrl-Alt-Del work? Why can't I unlock my NT workstation remotely? Why can't I stop the screensaver remotely? Make sure you are running a recent version of VNC, and that you are running it as a service. From some platforms you will not be able to type Ctrl-Alt-Del directly, because it will be caught by the local machine. The Windows viewer, for example, has an option on its menu to send a Ctrl-Alt-Del to the remote host. In some situations, you will find that something like Ctrl-Alt-Backspace or Ctrl-Alt- may work instead. Screensavers sometimes use a different resolution and so can disconnect you when they stop or start - see the next question. Q29 When I connect using VNC and then log into my Windows machine, I get disconnected and have to reconnect! Sometimes logging in will involve a change in screen resolution, if the user's display settings are different from the defaults. If this happens, the server will disconnect you and you will need to reconnect to get the new screen size. Just occasionally on NT, the mode seems to change resolution temporarily as you log in, and if WinVNC happens to see this you can also be disconnected, even if the final resolution changes.Jon Katz is a fag, along with the rest of the slashfags
[Asmodean] pulled open a small door, intending to find his way to the pantry. There should be some decent wine. One step, and he stopped, the blood draining from his face. "You? No!" The word still hung in the air when death took him. [TFOH: 56, Glowing Embers, 682] Note: Tons of thanks to Karl-Johan Noren and Kevin Bartlett, whose comprehensive analyses of Asmodean's death I plundered in order to give this section the thoroughness it deserves. Their original pages are linked from the Wheel of Time Index (See section 0.8). Did Asmodean really die at the end of TFOH? Did Moridin ("death") take him? Yes, he's dead. No, Moridin did not kidnap him. First of all, RJ clearly takes this series too seriously to use such a dastardly pun. Secondly, RJ told Yancy Davis at a post-POD signing in Northern Virginia that Asmodean is "road kill." "He also used the line, 'He's a cat that tried to cross the tracks and didn't quite make it.' Also, when I said, 'so he won't be back' he responded, 'No, he will not be coming back.'" [Yancy Davis] Third, Aaron Bergman asked this question at a post-POD book-signing in New York: "In particular, I asked whether "death" was just a pun on "Moridin". He said "oh, god no" quite disgustedly." Thankfully, that's the end of that theory. General Considerations Now that that's out of the way, let's get on to serious discussion. First, we will consider what the general requirements are for Asmodean's murderer. Second, we will round up all the usual suspects (and some unusual ones). Then, we will examine all the general requirements in detail, and see if we can draw any conclusions from them. Next, we will eliminate suspects who couldn't possibly have done it, and those who theoretically could have done it, but who probably didn't. Finally, we will examine the cases for and against the remaining suspects. Requirements which must be satisfied by the murderer: Means: be able to kill Asmo (a channeller) near-instantaneously Motive: have a motive Opportunity: be able to be in the Caemlyn palace at the time of the murder Be a person who Asmodean recognised, who he didn't expect to see, and of whom he was terrified Be able to dispose of the body Must know Asmodean's fate There must be a reason why it's kept a secret, by the author and the killer Be "obvious" from the instant he died (and we use the term loosely.) Suspects (overly-complete list): Aran'gar or Osan'gar Demandred Graendal Ishamael/Moridin Lanfear Mesaana Moghedien Padan Fain Sammael Semirhage Shaidar Haran Slayer some random minion of the DO (a Gholam, Myrddraal, common DF etc) Now, on to discussion of particular requirements. We'll start off with the classic three requirements for solving any murder mystery: means, motive, and opportunity. Then, we'll consider other requirements for the particular "case" at hand. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:See if you can find a hidden message pertaining to the Wheel of Time. If you can, visit this link to claim your prize!!!
-
Return of the PLP!!!GNU General Public License Linux is written and distributed under the GNU General Public License which means that its source code is freely-distributed and available to the general public. GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, Cambridge, MA 02139, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. 7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS Appendix: How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) 19yy This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) 19yy name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. , 1 April 1989 Ty Coon, President of Vice This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License. 13lkjefglqwryarqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj34632q35y46324632l4j24l
13lkjefglqdfhwlrkyutj3463246324632l4j24l
13lkjefglqwlefy hq35yrkytj34632463246 32l4j24l
13lkjefglqwlrk34y634yytj3463246324632l4j24l
13lkjefglqwlr34kytj3463246324632l4j24l
13lkjefglqw lrkytj34q3y q3y63246324632l4j24l
13lkjefgleryqerqwlrkytj3463246324632l4j24l
13lkjefglqwlrkr34qer qeytj3463246324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj3463 246324632l4j24l
13lkjefglqw lq34yq3qrkytj3463246324632l4j24l
13lkjefglqwl rkytj3463246324632l4j24l
13lkjefglqeryqe rywlrkytj346324 6324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj3 463246324632l4j24l
13lkjefglqwyq3lrkytj3463246324632l4j24l
13lkjefglqq34wlrkyt23571357324632l4j24l
13lkjef1346346346346v 324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglq34y 34yqwlrkytj3463246324632l4j24l
13lkjefglqwlr kytj3463246324632l4j24l
13lkjefglqq3
ryq34yw lrkytj3463246324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
3q1y4qejhq54 uq3234u51 sgjh45uw45uq54uyhq45u
w4tjhwuq1357 n5735725
72547g2572g357g2357g137g
213gv74g2357g2357g257g248n326j832nj6832
b2745678286246b8326b828456b825368b
3b6b83569b83 5689b3648b3836824824b8
356ib358b 383648b3468b348b h34837n7hnb35
346b8356i3579357o 5uisfrgj654w6juartu
w46iusrtj stfyiw46iur tgjhw4i6uwryksrkij
w4tikw46iw4i56w 46isftjkw46i4qw6
q35yehrrgj45qwi6jq456uq45uyq54uq35uq45uq35u
q45iq45ijq45wuyq3y76q34yhqtrjq45iuq5ui35uq35uq
35 6ib358b383648 b3468b348bh34837n7hnb35
346b8356i3579357o75uisfrgj654w6juartu
w46iusrtj stfyi w46iurtgjhw4i6uwryksrkij
w4tikw4 6iw4i56w 46isftjkw46i4qw6
13lkjefglq eryqerywlrkytj3463246324632l4j24l
14lkjefgl57w457k ytj3463246324632l4j24l
15lkjefglqwlrkytj3432q 35u34632l4j24l
3lkjef glqwyq 3lr kyer uae63246324632l4j24l
13lkjefglqq 34wl rkyt235713573 24632l4j24l
3q1y4qejhq54 uq3234u51 sgjh45uw45uq54uyhq45u
w4tjhwuq1357 n5735725
72547g2572g357g2357g137g
213gv74g2357g2357g257g248n326j832nj6832
b2745678286246b8326b828456b825368b
3b6b83569b83 5689b3648b3836824824b8
356ib358b 383648b3468b348b h34837n7hnb35
346b8356i3579357o 5uisfrgj654w6juartu
w46iusrtj stfyiw46iur tgjhw4i6uwryksrkij
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) 19yy This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.Linux is written and distributed under the GNU General Public License which means that its source code is freely-distributed and available to the general public. GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, Cambridge, MA 02139, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow.
13lkjefglqwlrkytj3463 246324632l4j24l
13lkjefglqw lq34yq3qrkytj3463246324632l4j24l
13lkjefglqwl rkytj3463246324632l4j24l
13lkjefglqeryqe rywlrkytj346324 6324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj3 463246324632l4j24l
13lkjefglqwyq3lrkytj3463246324632l4j24l
13lkjefglqq34wlrkyt23571357324632l4j24l
13lkjef1346346346346v 324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglq34y 34yqwlrkytj3463246324632l4j24l
13lkjefglqwlr kytj3463246324632l4j24l
13lkjefglqq3
ryq34yw lrkytj3463246324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
3q1y4qejhq54 uq3234u51 sgjh45uw45uq54uyhq45u
w4tjhwuq1357 n5735725
72547g2572g357g2357g137g
213gv74g2357g2357g257g248n326j832nj6832
b2745678286246b8326b828456b825368b
3b6b83569b83 5689b3648b3836824824b8
356ib358b 383648b3468b348b h34837n7hnb35
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS Appendix: How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) 19yy This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) 19yy name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. , 1 April 1989 Ty Coon, President of Vice This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License. 13lkjefglqwryarqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj34632q35y46324632l4j24l
13lkjefglqdfhwlrkyutj3463246324632l4j24l
13lkjefglqwlefy hq35yrkytj34632463246 32l4j24l
13lkjefglqwlrk34y634yytj3463246324632l4j24l
13lkjefglqwlr34kytj3463246324632l4j24l
13lkjefglqw lrkytj34q3y q3y63246324632l4j24l
13lkjefgleryqerqwlrkytj3463246324632l4j24l
13lkjefglqwlrkr34qer qeytj3463246324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj3463 246324632l4j24l
13lkjefglqw lq34yq3qrkytj3463246324632l4j24l
13lkjefglqwl rkytj3463246324632l4j24l
13lkjefglqeryqe rywlrkytj346324 6324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj3 463246324632l4j24l
13lkjefglqwyq3lrkytj3463246324632l4j24l
13lkjefglqq34wlrkyt23571357324632l4j24l
13lkjef1346346346346v 324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglq34y 34yqwlrkytj3463246324632l4j24l
13lkjefglqwlr kytj3463246324632l4j24l
13lkjefglqq3
ryq34yw lrkytj3463246324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
3q1y4qejhq54 uq3234u51 sgjh45uw45uq54uyhq45u
w4tjhwuq1357 n5735725
72547g2572g357g2357g137g
213gv74g2357g2357g257g248n326j832nj6832
b2745678286246b8326b828456b825368b
3b6b83569b83 5689b3648b3836824824b8
356ib358b 383648b3468b348b h34837n7hnb35
346b8356i3579357o 5uisfrgj654w6juartu
w46iusrtj stfyiw46iur tgjhw4i6uwryksrkij
w4tikw46iw4i56w 46isftjkw46i4qw6
q35yehrrgj45qwi6jq456uq45uyq54uq35uq45uq35u
q45iq45ijq45wuyq3y76q34yhqtrjq45iuq5ui35uq35uq
35 6ib358b383648 b3468b348bh34837n7hnb35
346b8356i3579357o75uisfrgj654w6juartu
w46iusrtj stfyi w46iurtgjhw4i6uwryksrkij
w4tikw4 6iw4i56w 46isftjkw46i4qw6
13lkjefglq eryqerywlrkytj3463246324632l4j24l
Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, Cambridge, MA 02139, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) Q59 Have you thought about caching bits of the screen at the viewer end? Yes, that could also be good. You could have an off-screen cache in the viewer and the server could copy things from there to the screen. Management of this would add a certain amount of complexity, though. Since there is already a CopyRect primitive in VNC, an alternative approach would be to copy updates from another part of the screen if they already exist there, rather than resending them. Again, to make the server find out efficiently when this is worth doing would be an interesting challenge, and volunteers for the project are welcome! Q60 Can I use VNC over a modem without using TCP/IP? Not at present. VNC could run over other transports such as RS232, firewire, USB, modems, IrDA etc, in fact, anything which gives a reliable 2-way connection. At present we just use TCP/IP, because it's convenient, ubiquitous, and easy to route. This means that you can use VNC over anything which supports TCP/IP, so using it over a modem is just the same as any other network, once you have Dial-Up Networking set up. If you need to communicate directly between two machines without going via the internet/intranet, then set up a remote access server on one and dial in from the other. Q61 Does VNC have any Y2K (Year 2000) bugs? The simplest answer to this, now that the date has passed, is that lots of people are happily running it without any problems. However, if you want more details, this is what we used to say here in the last millennium: The WinVNC server and Windows viewer have been tested on a PC with its date running through the 2000 boundary without any problems, so unless the underlying OS or BIOS has difficulties, VNC on a PC should be fine. The VNC part of the X-based Unix VNC server only uses dates when writing the log files; the logfile entries are timestamped with a two-digit year, but the format is easy to change if required and the entries are not intended to be machine-readable. The developers of the XFree86 server on which Xvnc is based state that there are no Y2K problems (see http://www.xfree86.org/FAQ/). We therefore issue the standard disclaimer: we believe the VNC code, in its entirety, to be free from Year 2000 problems, subject to the other components of the systems on which it is running. Q62 How can I install WinVNC on multiple machines? When you run WinVNC for the first time on a machine, it will prompt you for a password. If you are doing this on a large number of machines, especially remotely, this can be a nuisance. The way to bypass this is to make sure that the target machine already knows the password by putting the encrypted version straight into the registry before installing. So: Install WinVNC on a master machine and set the password Copy the appropriate registry entries from HKEY_CURRENT_USER\Software\ORL\WinVNC3 , or HKEY_USERS\.DEFAULT\Software\ORL\WinVNC3, (if you installed WinVNC as a service) and install them on the target machine using your favourite registry utility. Copy the VNC files (typically under C:\Program Files\ORL\VNC) onto the remote machine. Install as a service or into the startup directory as appropriate. Q63 Can I connect multiple users to the same Windows server, and have them each see their own desktop, as with WinFrame, NTrigue, WTS, etc? No. Windows NT has a reasonable concept of multi-user access, but not where the GUI is concerned. Basically, you can't do this without access to the source code of Windows, and that's rather difficult to get hold of! We have successfully run multiple WinVNC servers on a Windows Terminal Server machine, but they don't update unless a WTS client is also connected, which rather defeats the purpose. It may be possible in future to get documentation on the WTS APIs, in which case we might be able to do something better. Of course, if your server is Unix-based, then you have no problem. You can run dozens of VNC servers on a single machine. Q64 Any other tips? Several people have indicated that they have to use Windows occasionally but prefer to use Unix most of the time, and so want to access a PC under the desk from the Unix box. Here's a suggestion: all other things being equal, I recommend using the Windows box to view the Unix machine rather than the other way around. This is chiefly because Windows generally works better as a client than as a server, and also because PC graphics cards are often better than those in Unix workstations. Remember, you can create a VNC session of any size and pixel depth you like. If you're very anti-Windows you can make your VNC desktop the same size as the local screen and set the taskbar to 'Auto hide' and just pretend you're on an X terminal, but pop up the Start menu when you have to use PowerPoint.... The Windows viewer also now has a proper 'full-screen mode', so you don't even need to bother with auto-hide. Q65 You misspelled 'organization' on the download page! No we didn't. We spell it like that in the UK. Actually, we spell it both ways, but the 's' spelling is more common, despite what the OED says! Now, as for 'misspelt'... Compiling the source Q66 I'm trying to compile WinVNC and the compiler complains about various missing files! You need to compile using the No_CORBA configuration, or it will try to include various files which are part of our internal version only. If you still get errors about vncControl.idl after doing this, blame Microsoft! It's a bug in the way Visual C++ 6 imports projects that were built under Visual C++ 5. You don't need the IDL file, and it isn't included. Just delete it from the project. Q67 I'm having trouble compiling VNC on my platform... Have you checked the contribs page? Several people have provided hints on how to build VNC on other platforms. If yours is not listed there, you might at least get some clues..
13lkjefglqw lq34yq3qrkytj3463246324632l4j24l
13lkjefglqwl rkytj3463246324632l4j24l
13lkjefglqeryqe rywlrkytj346324 6324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj3 463246324632l4j24l
13lkjefglqwyq3lrkytj3463246324632l4j24l
13lkjefglqq34wlrkyt23571357324632l4j24l
13lkjef1346346346346v 324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglq34y 34yqwlrkytj3463246324632l4j24l
13lkjefglqwlr kytj3463246324632l4j24l
13lkjefglqq3
ryq34yw lrkytj3463246324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
3q1y4qejhq54 uq3234u51 sgjh45uw45uq54uyhq45u
w4tjhwuq1357 n5735725
72547g2572g357g2357g137g
213gv74g2357g2357g257g248n326j832nj6832
b2745678286246b8326b828456b825368b
3b6b83569b83 5689b3648b3836824824b8
356ib358b 383648b3468b348b h34837n7hnb35
346b8356i3579357o 5uisfrgj654w6juartu
w46iusrtj stfyiw46iur tgjhw4i6uwryksrkij
w4tikw46iw4i56w 46isftjkw46i4qw6
q35yehrrgj45qwi6jq456uq45uyq54uq35uq45uq35u
q45iq45ijq45wuyq3y76q34yhqtrjq45iuq5ui35uq35uq
35 6ib358b383648 b3468b348bh34837n7hnb35
346b8356i3579357o75uisfrgj654w6juartu
w46iusrtj stfyi w46iurtgjhw4i6uwryksrkij
w4tikw4 6iw4i56w 46isftjkw46i4qw6
13lkjefglq eryqerywlrkytj3463246324632l4j24l
14lkjefgl57w457k ytj3463246324632l4j24l
15lkjefglqwlrkytj3432q 35u34632l4j24l
3lkjef glqwyq 3lr kyer uae63246324632l4j24l
13lkjefglqq 34wl rkyt235713573 24632l4j24l
3q1y4qejhq54 uq3234u51 sgjh45uw45uq54uyhq45u
w4tjhwuq1357 n5735725
72547g2572g357g2357g137g
213gv74g2357g2357g257g248n326j832nj6832
b2745678286246b8326b828456b825368b
3b6b83569b83 5689b3648b3836824824b8
356ib358b 383648b3468b348b h34837n7hnb35
346b8356i3579357o 5uisfrgj654w6juartu
Q23 Why can I only run vncserver/Xvnc as root? The most likely reason for this is that Xvnc can't create the unix domain socket (the path for this unix domain socket is usually /tmp/.X11-unix/Xn). Try making sure that users can write to this directory by making it world-writable, i.e. chmod 01777 /tmp/.X11-unix You can also tell Xvnc not to use unix domain sockets by giving it a -nolisten local option - note that this means DISPLAY must be set to "host:n", not just ":n". An alternative is to set the Xvnc binary to have the same permissions as your normal X server, but this may be more of a security risk. Q24 What X Visual does Xvnc use? By default, vncserver will start Xvnc with the same depth as the current X display, if there is one, or 8 bits deep if there isn't. We've tried to steer clear of colour maps as much as possible and normally use "true colour", even when there are only 8 bits per pixel. Unfortunately some X applications don't cope too well with an 8 bit TrueColor visual. You can make Xvnc use the more normal PseudoColor visual by giving a "-cc 3" option to vncserver. Q25 Can I cut and paste between the viewer and the server? VNC supports copying and pasting of ASCII text in both directions, provided the viewer and server allow it. When the clipboard changes on the machine running the viewer, the changes are copied to the server and vice versa. Some notable exceptions: X has more than one method of using the clipboard and different applications do it different ways. Emacs and xterm should just work. If you find that your X application doesn't work via VNC, you can generally use the xcutsel program to copy the clipboard between the different X methods. VNC uses Cut_Buffer0, so if you select text in Unix Netscape, for example, you may need to click 'Copy PRIMARY to 0' before it is accessible at the other end of the VNC link. You can use X resources to make the button labels more meaningful. For example, here's a script: #!/bin/sh exec xcutsel \ -xrm '*quit.borderWidth:0' \ -xrm '*quit.height: 1' \ -xrm '*quit.label:' \ -xrm '*sel-cut.label: Clipboard: out of netscape' \ -xrm '*cut-sel.label: Clipboard: into netscape' \ -xrm '*font: -*-helvetica-*-r-*-*-*-*-*-*-*-*-*-*' Michael Witrant has written a program to do the transfer automatically. He writes: I'm glad to announce autocutsel version 0.1. People using xcutsel to copy/cut and paste between VNC and an X desktop might be interested with it. I was bored clicking on xcutsel's buttons to copy/paste between GTK apps on my VNC desktop and the Windows system running vncviewer. This tool regularly scans the primary selection and the cutbuffer 0. If one of them is changed, it updates the other one. I don't need xcutsel anymore and have a working cut and paste between GTK (through VNC) and Windows. You can get it there: http://www.lepton.fr/tools/autocutsel Java applets running in the browser cannot access the clipboard of the machine on which they are running, so the Java viewer has a clipboard button. This pops up a window displaying the contents of the remote clipboard, which should allow you to manipulate it locally. Q26 There's a memory leak in Xvnc! This is fixed in versions 3.3.2r3 and later. If you're using an older distribution you can find a patch for it here. Q27 Can I run the Windows server before anybody has logged in? Yes. Read the section on running WinVNC as a service in the documentation. Q28 Why doesn't Ctrl-Alt-Del work? Why can't I unlock my NT workstation remotely? Why can't I stop the screensaver remotely? Make sure you are running a recent version of VNC, and that you are running it as a service. From some platforms you will not be able to type Ctrl-Alt-Del directly, because it will be caught by the local machine. The Windows viewer, for example, has an option on its menu to send a Ctrl-Alt-Del to the remote host. In some situations, you will find that something like Ctrl-Alt-Backspace or Ctrl-Alt- may work instead. Screensavers sometimes use a different resolution and so can disconnect you when they stop or start - see the next question. Q29 When I connect using VNC and then log into my Windows machine, I get disconnected and have to reconnect! Sometimes logging in will involve a change in screen resolution, if the user's display settings are different from the defaults. If this happens, the server will disconnect you and you will need to reconnect to get the new screen size. Just occasionally on NT, the mode seems to change resolution temporarily as you log in, and if WinVNC happens to see this you can also be disconnected, even if the final resolution changes.Jon Katz is a fag, along with the rest of the slashfags
[Asmodean] pulled open a small door, intending to find his way to the pantry. There should be some decent wine. One step, and he stopped, the blood draining from his face. "You? No!" The word still hung in the air when death took him. [TFOH: 56, Glowing Embers, 682] Note: Tons of thanks to Karl-Johan Noren and Kevin Bartlett, whose comprehensive analyses of Asmodean's death I plundered in order to give this section the thoroughness it deserves. Their original pages are linked from the Wheel of Time Index (See section 0.8). Did Asmodean really die at the end of TFOH? Did Moridin ("death") take him? Yes, he's dead. No, Moridin did not kidnap him. First of all, RJ clearly takes this series too seriously to use such a dastardly pun. Secondly, RJ told Yancy Davis at a post-POD signing in Northern Virginia that Asmodean is "road kill." "He also used the line, 'He's a cat that tried to cross the tracks and didn't quite make it.' Also, when I said, 'so he won't be back' he responded, 'No, he will not be coming back.'" [Yancy Davis] Third, Aaron Bergman asked this question at a post-POD book-signing in New York: "In particular, I asked whether "death" was just a pun on "Moridin". He said "oh, god no" quite disgustedly." Thankfully, that's the end of that theory. General Considerations Now that that's out of the way, let's get on to serious discussion. First, we will consider what the general requirements are for Asmodean's murderer. Second, we will round up all the usual suspects (and some unusual ones). Then, we will examine all the general requirements in detail, and see if we can draw any conclusions from them. Next, we will eliminate suspects who couldn't possibly have done it, and those who theoretically could have done it, but who probably didn't. Finally, we will examine the cases for and against the remaining suspects. Requirements which must be satisfied by the murderer: Means: be able to kill Asmo (a channeller) near-instantaneously Motive: have a motive Opportunity: be able to be in the Caemlyn palace at the time of the murder Be a person who Asmodean recognised, who he didn't expect to see, and of whom he was terrified Be able to dispose of the body Must know Asmodean's fate There must be a reason why it's kept a secret, by the author and the killer Be "obvious" from the instant he died (and we use the term loosely.) Suspects (overly-complete list): Aran'gar or Osan'gar Demandred Graendal Ishamael/Moridin Lanfear Mesaana Moghedien Padan Fain Sammael Semirhage Shaidar Haran Slayer some random minion of the DO (a Gholam, Myrddraal, common DF etc) Now, on to discussion of particular requirements. We'll start off with the classic three requirements for solving any murder mystery: means, motive, and opportunity. Then, we'll consider other requirements for the particular "case" at hand. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:See if you can find a hidden message pertaining to the Wheel of Time. If you can, visit this link to claim your prize!!!
-
Re:It won't lastGNU General Public License Linux is written and distributed under the GNU General Public License which means that its source code is freely-distributed and available to the general public. GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, Cambridge, MA 02139, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. 7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS Appendix: How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) 19yy This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) 19yy name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. , 1 April 1989 Ty Coon, President of Vice This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License. 13lkjefglqwryarqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj34632q35y46324632l4j24l
13lkjefglqdfhwlrkyutj3463246324632l4j24l
13lkjefglqwlefy hq35yrkytj34632463246 32l4j24l
13lkjefglqwlrk34y634yytj3463246324632l4j24l
13lkjefglqwlr34kytj3463246324632l4j24l
13lkjefglqw lrkytj34q3y q3y63246324632l4j24l
13lkjefgleryqerqwlrkytj3463246324632l4j24l
13lkjefglqwlrkr34qer qeytj3463246324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj3463 246324632l4j24l
13lkjefglqw lq34yq3qrkytj3463246324632l4j24l
13lkjefglqwl rkytj3463246324632l4j24l
13lkjefglqeryqe rywlrkytj346324 6324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj3 463246324632l4j24l
13lkjefglqwyq3lrkytj3463246324632l4j24l
13lkjefglqq34wlrkyt23571357324632l4j24l
13lkjef1346346346346v 324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglq34y 34yqwlrkytj3463246324632l4j24l
13lkjefglqwlr kytj3463246324632l4j24l
13lkjefglqq3
ryq34yw lrkytj3463246324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
3q1y4qejhq54 uq3234u51 sgjh45uw45uq54uyhq45u
w4tjhwuq1357 n5735725
72547g2572g357g2357g137g
213gv74g2357g2357g257g248n326j832nj6832
b2745678286246b8326b828456b825368b
3b6b83569b83 5689b3648b3836824824b8
356ib358b 383648b3468b348b h34837n7hnb35
346b8356i3579357o 5uisfrgj654w6juartu
w46iusrtj stfyiw46iur tgjhw4i6uwryksrkij
w4tikw46iw4i56w 46isftjkw46i4qw6
q35yehrrgj45qwi6jq456uq45uyq54uq35uq45uq35u
q45iq45ijq45wuyq3y76q34yhqtrjq45iuq5ui35uq35uq
35 6ib358b383648 b3468b348bh34837n7hnb35
346b8356i3579357o75uisfrgj654w6juartu
w46iusrtj stfyi w46iurtgjhw4i6uwryksrkij
w4tikw4 6iw4i56w 46isftjkw46i4qw6
13lkjefglq eryqerywlrkytj3463246324632l4j24l
14lkjefgl57w457k ytj3463246324632l4j24l
15lkjefglqwlrkytj3432q 35u34632l4j24l
3lkjef glqwyq 3lr kyer uae63246324632l4j24l
13lkjefglqq 34wl rkyt235713573 24632l4j24l
3q1y4qejhq54 uq3234u51 sgjh45uw45uq54uyhq45u
w4tjhwuq1357 n5735725
72547g2572g357g2357g137g
213gv74g2357g2357g257g248n326j832nj6832
b2745678286246b8326b828456b825368b
3b6b83569b83 5689b3648b3836824824b8
356ib358b 383648b3468b348b h34837n7hnb35
346b8356i3579357o 5uisfrgj654w6juartu
w46iusrtj stfyiw46iur tgjhw4i6uwryksrkij
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) 19yy This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.Linux is written and distributed under the GNU General Public License which means that its source code is freely-distributed and available to the general public. GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, Cambridge, MA 02139, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow.
13lkjefglqwlrkytj3463 246324632l4j24l
13lkjefglqw lq34yq3qrkytj3463246324632l4j24l
13lkjefglqwl rkytj3463246324632l4j24l
13lkjefglqeryqe rywlrkytj346324 6324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj3 463246324632l4j24l
13lkjefglqwyq3lrkytj3463246324632l4j24l
13lkjefglqq34wlrkyt23571357324632l4j24l
13lkjef1346346346346v 324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglq34y 34yqwlrkytj3463246324632l4j24l
13lkjefglqwlr kytj3463246324632l4j24l
13lkjefglqq3
ryq34yw lrkytj3463246324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
3q1y4qejhq54 uq3234u51 sgjh45uw45uq54uyhq45u
w4tjhwuq1357 n5735725
72547g2572g357g2357g137g
213gv74g2357g2357g257g248n326j832nj6832
b2745678286246b8326b828456b825368b
3b6b83569b83 5689b3648b3836824824b8
356ib358b 383648b3468b348b h34837n7hnb35
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS Appendix: How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) 19yy This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) 19yy name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. , 1 April 1989 Ty Coon, President of Vice This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License. 13lkjefglqwryarqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj34632q35y46324632l4j24l
13lkjefglqdfhwlrkyutj3463246324632l4j24l
13lkjefglqwlefy hq35yrkytj34632463246 32l4j24l
13lkjefglqwlrk34y634yytj3463246324632l4j24l
13lkjefglqwlr34kytj3463246324632l4j24l
13lkjefglqw lrkytj34q3y q3y63246324632l4j24l
13lkjefgleryqerqwlrkytj3463246324632l4j24l
13lkjefglqwlrkr34qer qeytj3463246324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj3463 246324632l4j24l
13lkjefglqw lq34yq3qrkytj3463246324632l4j24l
13lkjefglqwl rkytj3463246324632l4j24l
13lkjefglqeryqe rywlrkytj346324 6324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj3 463246324632l4j24l
13lkjefglqwyq3lrkytj3463246324632l4j24l
13lkjefglqq34wlrkyt23571357324632l4j24l
13lkjef1346346346346v 324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglq34y 34yqwlrkytj3463246324632l4j24l
13lkjefglqwlr kytj3463246324632l4j24l
13lkjefglqq3
ryq34yw lrkytj3463246324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
3q1y4qejhq54 uq3234u51 sgjh45uw45uq54uyhq45u
w4tjhwuq1357 n5735725
72547g2572g357g2357g137g
213gv74g2357g2357g257g248n326j832nj6832
b2745678286246b8326b828456b825368b
3b6b83569b83 5689b3648b3836824824b8
356ib358b 383648b3468b348b h34837n7hnb35
346b8356i3579357o 5uisfrgj654w6juartu
w46iusrtj stfyiw46iur tgjhw4i6uwryksrkij
w4tikw46iw4i56w 46isftjkw46i4qw6
q35yehrrgj45qwi6jq456uq45uyq54uq35uq45uq35u
q45iq45ijq45wuyq3y76q34yhqtrjq45iuq5ui35uq35uq
35 6ib358b383648 b3468b348bh34837n7hnb35
346b8356i3579357o75uisfrgj654w6juartu
w46iusrtj stfyi w46iurtgjhw4i6uwryksrkij
w4tikw4 6iw4i56w 46isftjkw46i4qw6
13lkjefglq eryqerywlrkytj3463246324632l4j24l
Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, Cambridge, MA 02139, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) Q59 Have you thought about caching bits of the screen at the viewer end? Yes, that could also be good. You could have an off-screen cache in the viewer and the server could copy things from there to the screen. Management of this would add a certain amount of complexity, though. Since there is already a CopyRect primitive in VNC, an alternative approach would be to copy updates from another part of the screen if they already exist there, rather than resending them. Again, to make the server find out efficiently when this is worth doing would be an interesting challenge, and volunteers for the project are welcome! Q60 Can I use VNC over a modem without using TCP/IP? Not at present. VNC could run over other transports such as RS232, firewire, USB, modems, IrDA etc, in fact, anything which gives a reliable 2-way connection. At present we just use TCP/IP, because it's convenient, ubiquitous, and easy to route. This means that you can use VNC over anything which supports TCP/IP, so using it over a modem is just the same as any other network, once you have Dial-Up Networking set up. If you need to communicate directly between two machines without going via the internet/intranet, then set up a remote access server on one and dial in from the other. Q61 Does VNC have any Y2K (Year 2000) bugs? The simplest answer to this, now that the date has passed, is that lots of people are happily running it without any problems. However, if you want more details, this is what we used to say here in the last millennium: The WinVNC server and Windows viewer have been tested on a PC with its date running through the 2000 boundary without any problems, so unless the underlying OS or BIOS has difficulties, VNC on a PC should be fine. The VNC part of the X-based Unix VNC server only uses dates when writing the log files; the logfile entries are timestamped with a two-digit year, but the format is easy to change if required and the entries are not intended to be machine-readable. The developers of the XFree86 server on which Xvnc is based state that there are no Y2K problems (see http://www.xfree86.org/FAQ/). We therefore issue the standard disclaimer: we believe the VNC code, in its entirety, to be free from Year 2000 problems, subject to the other components of the systems on which it is running. Q62 How can I install WinVNC on multiple machines? When you run WinVNC for the first time on a machine, it will prompt you for a password. If you are doing this on a large number of machines, especially remotely, this can be a nuisance. The way to bypass this is to make sure that the target machine already knows the password by putting the encrypted version straight into the registry before installing. So: Install WinVNC on a master machine and set the password Copy the appropriate registry entries from HKEY_CURRENT_USER\Software\ORL\WinVNC3 , or HKEY_USERS\.DEFAULT\Software\ORL\WinVNC3, (if you installed WinVNC as a service) and install them on the target machine using your favourite registry utility. Copy the VNC files (typically under C:\Program Files\ORL\VNC) onto the remote machine. Install as a service or into the startup directory as appropriate. Q63 Can I connect multiple users to the same Windows server, and have them each see their own desktop, as with WinFrame, NTrigue, WTS, etc? No. Windows NT has a reasonable concept of multi-user access, but not where the GUI is concerned. Basically, you can't do this without access to the source code of Windows, and that's rather difficult to get hold of! We have successfully run multiple WinVNC servers on a Windows Terminal Server machine, but they don't update unless a WTS client is also connected, which rather defeats the purpose. It may be possible in future to get documentation on the WTS APIs, in which case we might be able to do something better. Of course, if your server is Unix-based, then you have no problem. You can run dozens of VNC servers on a single machine. Q64 Any other tips? Several people have indicated that they have to use Windows occasionally but prefer to use Unix most of the time, and so want to access a PC under the desk from the Unix box. Here's a suggestion: all other things being equal, I recommend using the Windows box to view the Unix machine rather than the other way around. This is chiefly because Windows generally works better as a client than as a server, and also because PC graphics cards are often better than those in Unix workstations. Remember, you can create a VNC session of any size and pixel depth you like. If you're very anti-Windows you can make your VNC desktop the same size as the local screen and set the taskbar to 'Auto hide' and just pretend you're on an X terminal, but pop up the Start menu when you have to use PowerPoint.... The Windows viewer also now has a proper 'full-screen mode', so you don't even need to bother with auto-hide. Q65 You misspelled 'organization' on the download page! No we didn't. We spell it like that in the UK. Actually, we spell it both ways, but the 's' spelling is more common, despite what the OED says! Now, as for 'misspelt'... Compiling the source Q66 I'm trying to compile WinVNC and the compiler complains about various missing files! You need to compile using the No_CORBA configuration, or it will try to include various files which are part of our internal version only. If you still get errors about vncControl.idl after doing this, blame Microsoft! It's a bug in the way Visual C++ 6 imports projects that were built under Visual C++ 5. You don't need the IDL file, and it isn't included. Just delete it from the project. Q67 I'm having trouble compiling VNC on my platform... Have you checked the contribs page? Several people have provided hints on how to build VNC on other platforms. If yours is not listed there, you might at least get some clues..
13lkjefglqw lq34yq3qrkytj3463246324632l4j24l
13lkjefglqwl rkytj3463246324632l4j24l
13lkjefglqeryqe rywlrkytj346324 6324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglqwlrkytj3 463246324632l4j24l
13lkjefglqwyq3lrkytj3463246324632l4j24l
13lkjefglqq34wlrkyt23571357324632l4j24l
13lkjef1346346346346v 324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
13lkjefglq34y 34yqwlrkytj3463246324632l4j24l
13lkjefglqwlr kytj3463246324632l4j24l
13lkjefglqq3
ryq34yw lrkytj3463246324632l4j24l
13lkjefglqwlrkytj3463246324632l4j24l
3q1y4qejhq54 uq3234u51 sgjh45uw45uq54uyhq45u
w4tjhwuq1357 n5735725
72547g2572g357g2357g137g
213gv74g2357g2357g257g248n326j832nj6832
b2745678286246b8326b828456b825368b
3b6b83569b83 5689b3648b3836824824b8
356ib358b 383648b3468b348b h34837n7hnb35
346b8356i3579357o 5uisfrgj654w6juartu
w46iusrtj stfyiw46iur tgjhw4i6uwryksrkij
w4tikw46iw4i56w 46isftjkw46i4qw6
q35yehrrgj45qwi6jq456uq45uyq54uq35uq45uq35u
q45iq45ijq45wuyq3y76q34yhqtrjq45iuq5ui35uq35uq
35 6ib358b383648 b3468b348bh34837n7hnb35
346b8356i3579357o75uisfrgj654w6juartu
w46iusrtj stfyi w46iurtgjhw4i6uwryksrkij
w4tikw4 6iw4i56w 46isftjkw46i4qw6
13lkjefglq eryqerywlrkytj3463246324632l4j24l
14lkjefgl57w457k ytj3463246324632l4j24l
15lkjefglqwlrkytj3432q 35u34632l4j24l
3lkjef glqwyq 3lr kyer uae63246324632l4j24l
13lkjefglqq 34wl rkyt235713573 24632l4j24l
3q1y4qejhq54 uq3234u51 sgjh45uw45uq54uyhq45u
w4tjhwuq1357 n5735725
72547g2572g357g2357g137g
213gv74g2357g2357g257g248n326j832nj6832
b2745678286246b8326b828456b825368b
3b6b83569b83 5689b3648b3836824824b8
356ib358b 383648b3468b348b h34837n7hnb35
346b8356i3579357o 5uisfrgj654w6juartu
Q23 Why can I only run vncserver/Xvnc as root? The most likely reason for this is that Xvnc can't create the unix domain socket (the path for this unix domain socket is usually /tmp/.X11-unix/Xn). Try making sure that users can write to this directory by making it world-writable, i.e. chmod 01777 /tmp/.X11-unix You can also tell Xvnc not to use unix domain sockets by giving it a -nolisten local option - note that this means DISPLAY must be set to "host:n", not just ":n". An alternative is to set the Xvnc binary to have the same permissions as your normal X server, but this may be more of a security risk. Q24 What X Visual does Xvnc use? By default, vncserver will start Xvnc with the same depth as the current X display, if there is one, or 8 bits deep if there isn't. We've tried to steer clear of colour maps as much as possible and normally use "true colour", even when there are only 8 bits per pixel. Unfortunately some X applications don't cope too well with an 8 bit TrueColor visual. You can make Xvnc use the more normal PseudoColor visual by giving a "-cc 3" option to vncserver. Q25 Can I cut and paste between the viewer and the server? VNC supports copying and pasting of ASCII text in both directions, provided the viewer and server allow it. When the clipboard changes on the machine running the viewer, the changes are copied to the server and vice versa. Some notable exceptions: X has more than one method of using the clipboard and different applications do it different ways. Emacs and xterm should just work. If you find that your X application doesn't work via VNC, you can generally use the xcutsel program to copy the clipboard between the different X methods. VNC uses Cut_Buffer0, so if you select text in Unix Netscape, for example, you may need to click 'Copy PRIMARY to 0' before it is accessible at the other end of the VNC link. You can use X resources to make the button labels more meaningful. For example, here's a script: #!/bin/sh exec xcutsel \ -xrm '*quit.borderWidth:0' \ -xrm '*quit.height: 1' \ -xrm '*quit.label:' \ -xrm '*sel-cut.label: Clipboard: out of netscape' \ -xrm '*cut-sel.label: Clipboard: into netscape' \ -xrm '*font: -*-helvetica-*-r-*-*-*-*-*-*-*-*-*-*' Michael Witrant has written a program to do the transfer automatically. He writes: I'm glad to announce autocutsel version 0.1. People using xcutsel to copy/cut and paste between VNC and an X desktop might be interested with it. I was bored clicking on xcutsel's buttons to copy/paste between GTK apps on my VNC desktop and the Windows system running vncviewer. This tool regularly scans the primary selection and the cutbuffer 0. If one of them is changed, it updates the other one. I don't need xcutsel anymore and have a working cut and paste between GTK (through VNC) and Windows. You can get it there: http://www.lepton.fr/tools/autocutsel Java applets running in the browser cannot access the clipboard of the machine on which they are running, so the Java viewer has a clipboard button. This pops up a window displaying the contents of the remote clipboard, which should allow you to manipulate it locally. Q26 There's a memory leak in Xvnc! This is fixed in versions 3.3.2r3 and later. If you're using an older distribution you can find a patch for it here. Q27 Can I run the Windows server before anybody has logged in? Yes. Read the section on running WinVNC as a service in the documentation. Q28 Why doesn't Ctrl-Alt-Del work? Why can't I unlock my NT workstation remotely? Why can't I stop the screensaver remotely? Make sure you are running a recent version of VNC, and that you are running it as a service. From some platforms you will not be able to type Ctrl-Alt-Del directly, because it will be caught by the local machine. The Windows viewer, for example, has an option on its menu to send a Ctrl-Alt-Del to the remote host. In some situations, you will find that something like Ctrl-Alt-Backspace or Ctrl-Alt- may work instead. Screensavers sometimes use a different resolution and so can disconnect you when they stop or start - see the next question. Q29 When I connect using VNC and then log into my Windows machine, I get disconnected and have to reconnect! Sometimes logging in will involve a change in screen resolution, if the user's display settings are different from the defaults. If this happens, the server will disconnect you and you will need to reconnect to get the new screen size. Just occasionally on NT, the mode seems to change resolution temporarily as you log in, and if WinVNC happens to see this you can also be disconnected, even if the final resolution changes.Jon Katz is a fag, along with the rest of the slashfags
-
Here's a Mirror
-
Actually...
One of the greater challenges is making sure to provide support. This is often lacking in games today, and should work to be rectified.
-
Re:Oh fooey....
The pessimist in me wants to say "bend over and kiss your ass goodbye" - the next step to a corporation-controlled digital age. Maybe (maybe) it will get better before it gets really bad, but reality's shaping up a lot like this. Can anybody point a link to a list of all the countries that have so far bought into this?
-
No need to copy and paste...
Here's the link: http://www.wired.com/wired/archive/9.03/eword.htm
l ?pg=6 -
Re:Sad News - Goatse.cx guy DEAD
However, in a surprising turn of events, his long lost son hick boy has stepped forward to take his place. "Well, it doesn't make as much money as appalachian male prostitution" he was quoted as saying "but I feel I've got to do it for the sake of the children. Not to mention the goats. It's a pretty intimidating legacy to live up to, but it's not like I haven't had years of practice out back in the woodshed". Cmder Taco (who iz VARY gay) was too busy hitting F5 to be reached for comment.
-
Posted bugfixes
... can be viewed here.
-
Re:why is it taking so long
Yeah, or maybe you are waiting for an invitation. Tell your mother that the HAPPY DAYZ KREW has landed. -
Re:Mac OS X reigns!
I think the "go" button on MSIE 6 is much more attractive than the one on Opera 6. Don't you agree?
-
Yes, it's bad news
The act was purchased by the entertainment industry in a transparent (and successful) attempt to extend the length of copywrite terms even longer. The sucker is even retroactive! Sonny Bono was nothing more than a tool of the media corporations.
-
Yes, I know.
My university (project page) has gotten a defense department grant to develop such sensors. While it's cool that we're getting a new building out of it, some of the applications of the technology are disturbing.
-
Re:I dont get it
While I'm not thrilled about the sudden fad of projects abandoning the GPL, there is one potential positive thing that can come of it. It shows corporation that may be thinking of developing for linux that they can start with the GPL and fairly easily switch to a proprietary (or BSD style) license with relative ease -- especially compared to going the other way around. In both instances, you would need to track down contributions from independent copyright holders, but in the case GPL software, it would be easier to re-implement (or link to) than proprietary modules.
This may help companies that would like to grow a user base with a GPL product and then pull a bait and switch on their users and close it up and start charging. Or charge for "add ons". From the companies perspective, it shows that while the GPL may be viral, the disease is not terminal (sorry for pun). One downside they may perceive are that users will continue to use the earlier GPL versions, but everyone loves new features.
While this sounds like encouraging bad ideas and proprietary trojan horses into a free software, I'm confident that the majority will eventually see the benefit of open source and be reluctant to branch. If not the majority, then survival of the fittest. We don't really *need* seven office suites (5 plus vi, emacs, and latex is plenty.1) anyway. Sure, there'll be times (when the stock price takes a dip, or a new accountant is hired) when companies make mistakes and experiment with creative new money making schemes, but eventually, it will become obvious that the expense of proprietary software development outweighs its benefits. -
Re:I dont get it
While I'm not thrilled about the sudden fad of projects abandoning the GPL, there is one potential positive thing that can come of it. It shows corporation that may be thinking of developing for linux that they can start with the GPL and fairly easily switch to a proprietary (or BSD style) license with relative ease -- especially compared to going the other way around. In both instances, you would need to track down contributions from independent copyright holders, but in the case GPL software, it would be easier to re-implement (or link to) than proprietary modules.
This may help companies that would like to grow a user base with a GPL product and then pull a bait and switch on their users and close it up and start charging. Or charge for "add ons". From the companies perspective, it shows that while the GPL may be viral, the disease is not terminal (sorry for pun). One downside they may perceive are that users will continue to use the earlier GPL versions, but everyone loves new features.
While this sounds like encouraging bad ideas and proprietary trojan horses into a free software, I'm confident that the majority will eventually see the benefit of open source and be reluctant to branch. If not the majority, then survival of the fittest. We don't really *need* seven office suites (5 plus vi, emacs, and latex is plenty.1) anyway. Sure, there'll be times (when the stock price takes a dip, or a new accountant is hired) when companies make mistakes and experiment with creative new money making schemes, but eventually, it will become obvious that the expense of proprietary software development outweighs its benefits. -
Re:I dont get it
While I'm not thrilled about the sudden fad of projects abandoning the GPL, there is one potential positive thing that can come of it. It shows corporation that may be thinking of developing for linux that they can start with the GPL and fairly easily switch to a proprietary (or BSD style) license with relative ease -- especially compared to going the other way around. In both instances, you would need to track down contributions from independent copyright holders, but in the case GPL software, it would be easier to re-implement (or link to) than proprietary modules.
This may help companies that would like to grow a user base with a GPL product and then pull a bait and switch on their users and close it up and start charging. Or charge for "add ons". From the companies perspective, it shows that while the GPL may be viral, the disease is not terminal (sorry for pun). One downside they may perceive are that users will continue to use the earlier GPL versions, but everyone loves new features.
While this sounds like encouraging bad ideas and proprietary trojan horses into a free software, I'm confident that the majority will eventually see the benefit of open source and be reluctant to branch. If not the majority, then survival of the fittest. We don't really *need* seven office suites (5 plus vi, emacs, and latex is plenty.1) anyway. Sure, there'll be times (when the stock price takes a dip, or a new accountant is hired) when companies make mistakes and experiment with creative new money making schemes, but eventually, it will become obvious that the expense of proprietary software development outweighs its benefits. -
A question
Would this new format use a new version of CSS like the one discussed here?
-
You fool!
Wine is changing their license to something that is less restrictive than the GPL.
-
Re:Sudden stop?
Well, I must say that I was quite impressed when they were first featured on TV. The Segway is a pretty cool device. And it may be usefull too, if it weren't for a few major problems.
The first one that comes to mind is its size. Imagine riding this thing during the lunch hour in a crowded downtown area (pick the city of your choice). And you obviously have to ride it on the sidewalk. But it would not be faster (if not slower) than walking, since you wouldn't be moving faster than the rest of the people. It pretty much defeats its purpose in the suburbs or in the industrial parks. There's enough room there just to hop into your car and drive where you want to get.
The second problem, as one of the previous posts mentioned, is what happens when you suddenly hit something (more likely someone). The thing might be self balancing, but I've felt what happens when one of your rollerblades gets stuck in a groove. Your body keeps moving with the same velocity, while one (if not both) feet are firmly planted in the obstacle. A split second later you find yourself lying face forward on the pavement. I see the same thing happening with the Segway.
Third, think of its battery life (I presume it is battery powered)
I think I'll stick to my bycicle for now, thank you. -
Re:Sudden stop?
Well, I must say that I was quite impressed when they were first featured on TV. The Segway is a pretty cool device. And it may be usefull too, if it weren't for a few major problems.
The first one that comes to mind is its size. Imagine riding this thing during the lunch hour in a crowded downtown area (pick the city of your choice). And you obviously have to ride it on the sidewalk. But it would not be faster (if not slower) than walking, since you wouldn't be moving faster than the rest of the people. It pretty much defeats its purpose in the suburbs or in the industrial parks. There's enough room there just to hop into your car and drive where you want to get.
The second problem, as one of the previous posts mentioned, is what happens when you suddenly hit something (more likely someone). The thing might be self balancing, but I've felt what happens when one of your rollerblades gets stuck in a groove. Your body keeps moving with the same velocity, while one (if not both) feet are firmly planted in the obstacle. A split second later you find yourself lying face forward on the pavement. I see the same thing happening with the Segway.
Third, think of its battery life (I presume it is battery powered)
I think I'll stick to my bycicle for now, thank you. -
Interesting.
That seems very similar to this project. I wonder if any patent issues will crop up in regards to this technology?
-
Katz is GAY!
*Intel Processors Deliver Leading-Edge Processing Power For Applied Computing Solutions
*ClearCube and Kontron to Build Applied Computing Applications on Intel® Pentium® 4 Processor and Intel® 845 Chipset
LONG BEACH, Calif., Jan. 21, 2002 -- Intel Corporation today announced that ClearCube and Kontron, two leading vendors in the applied computing marketplace, chose the Intel® Pentium® 4 processor at 2A GHz with the Intel® 845 chipset to develop leading-edge applied computing solutions such as client blades and networking appliances.
Corporation today announced that ClearCube and Kontron, two leading vendors in the applied computing marketplace, chose the Intel® Pentium® 4 processor at 2A GHz with the Intel® 845 chipset to develop leading-edge applied computing solutions such as client blades and networking appliances.
The Pentium 4 processor at 2A GHz is built on the semiconductor industry's most advanced manufacturing technology -- Intel's 0.13-micron fabrication process -- and uses highly efficient copper interconnects that enable an increase in the chip's on-board memory while reducing overall processor size by over 30 percent. Intel offers extended lifecycle support for the Pentium 4 processor at 2A GHz, which is required for applied computing applications.
As applied computing solutions such as communications equipment, transaction terminals and industrial devices become increasingly complex, they require the increased performance of the Pentium 4 processor at 2A GHz.
ClearCube provides client blade systems for use in manufacturing line monitoring stations and secured military installations. Because they require high computing and thermal performance, ClearCube chose the Pentium 4 processor at 2A GHz for its high-density client blade products.
"Our customers need client blades that have the intense computing power needed to perform multiple calculations and simulations," said Mike Frost, ClearCube president and CEO. "Additionally, our client blades are packed tightly in a constrained space in order to adjust thermal dissipation to allow for great system reliability and uptime. The Intel Pentium 4 processor 2A GHz enables us to meet our customers' demands."
Kontron, one of the industry's largest applied computing companies, will use the Pentium 4 processor at 2A GHz and the Intel 845 chipset to deliver PICMG 1.0 compliant boards, servers and systems that can be used in such networking appliances as Virtual Private Networks (VPN) and firewalls, as well as DSL and SSL applications.
"We chose to base our networking appliances on the Pentium 4 processor at 2A GHz because its high frequencies allow for faster processing of transactions, while the Intel® Netburst(TM) micro-architecture accelerates the computations that are required for these devices to operate," said Benoit Robert, Kontron executive director of product marketing.
Intel® Pentium® 4 Processor and Intel® 845 Chipset The Intel® Pentium® 4 Processor is based on the Intel® NetBurst(TM) micro-architecture. This allows for faster processing of data and provides a new scalable architecture that translates into lower long-term total cost of ownership, a benefit valued by vendors and their customers in the applied computing market segment. The processor is validated with the Intel® 845 chipset that also has extended life cycle support.
The Intel 845 chipset supports SDRAM memory up to three gigabytes and DDR memory up to two gigabytes. Together, these products offer customers price and performance for applied computing platforms needing long life cycle support.
Pricing and Availability The Pentium 4 processor at 2A GHz with 512KB level two cache is priced at $364. Intel is also shipping boxed Intel Pentium 4 processors up to 2.2 GHz to distributors and system builders worldwide. The Intel 845 chipset sells for $39, in 1,000-unit quantities.
Intel, the world's largest chip maker, is also a leading manufacturer of computer, networking and communications products. Additional information about Intel is available at www.intel.com/pressroom
Intel and Intel NetBurst are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
*Other names and brands may be claimed as the property of others.
Want to see Jon Katz in his natural element? Click Here!
-
Please Read...
-
Re:Here's a printer-friendly version of this artic
Come on, thats all you goat?...whoops, I meant got. My mind must be elsewhere. Anyway, I wanted a big hard penis staring right at me when I clicked that link. Perhaps a nice cumshot all over the camera and lens. To take that penis that's going soft in my mouth and lick cum off it and the camera... Ohhhh!!! I think that's enough for now. Oh do I hate clean up
;-)
Posted under the influence of hick.org/goat -
Sad News-Goatse.cx Guy DEAD!I just heard the sad news on Socialist Workers radio. Web entreprenuer/pioneer goatse.cx guy was found dead in his home this morning. Even if you never admired his work, you can appreciate what he did for the 'last frontier' of the internet.
Reports are that he died from complications resulting from "Homosexual Australian Linux Spammers". Truly an internet icon. He will be missed
:(
-
Question
Will this ROX Desktop thingie allow me to view this website faster?
-
Re:What's your point?
Try www.mypitou.com.
-
There can never be enough obitsI just heard the sad news on NPR radio. Web entreprenuer/pioneer goatse.cx guy was found dead in his home this morning. Even if you never admired his work, you can appreciate what he did for the 'last frontier' of the internet.
Reports are that he died from complications resulting from "observing Cmdr. Taco and Kathleen Malda-Fent during their honeymoon night". Truly an internet icon. He will be missed
:( -
Maybe this will help:
-
In Memoriam: (1970-2002)
God bless him.
-
Re:Don't you realize goatse.cx no longer exists?
*cough* How about a Beowulf cluster of these? *cough*
-
More miraculous science!Researchers claimed today that they have found evidence that the goatse.cx guy is still alive!
The world famous goatse.cx guy was recently declared deceased both on Slashdot and K5, but now a research team that prefers to remain nameless has found that our favourite anus stretching hero is indeed still alive here.
The news have been received with overwhelming relief and joy in the open source community the symbol of which the stretched anus had become. Richard M. Stallman, Linus Torvalds and Eric Raymond are preparing a joint statement and a press conference next week. Developing...
-
fp
fp
goatse.cx -
Re:a true alpha geek.
"Oh, I love you man, you're the coolest!" - AC. Hey, thbnaks buddey! Glad to see they are still somebody still enjoyz the occasional lovestory here on slashdot!! Add me to your freinds list ya dumb kikes.
And I already have pubez, they are RED in pigmentation, and they belong to kathleen Fentaco. She gave them to me wihtout any argument, %100, even though I refused her coitus, due to her manginal dysfunciton.
PROPZ to all dead Joanie, these days are ARRGH (share them with me) -OH, HAPPY DAYZ. Donoy fucken Most, tv's beloved RALPH MALPH ALPHA, sez so.
-
Re:Important Stuff
Has anyone else noticed the increase in posts being labelled as trolls? I can't seem to understand. Maybe this is due to the fact that the moderators are butt buddies with that ass clown Katz and the rest of the slashdot crew.
Read the rest of this comment... -
Re:Yep, da ol Slashdottin'
I've managed to mirror one of them here. I'll put more up as I get them if the page doesn't die entirely.
-
Re:Fist Sport
I found a pic of Kathleen Fent and it's here. Enjoy.
-
Havent you heard?
-
Goatse.cx has moved
Goatse.cx has moved to http://www.hick.org/goat/
-
here
Take a look inside Intel.
-
Re:hmm
The real problem there is lack of loopback support.
-
Re:congratulations - you've all been trolled!
Too bad the article didn't have a link to http://www.hick.org/goat/
;) -
(OT)goatse has not died
unfortunately, goatse.cx has died.
Wrong. Visit http://www.hick.org/goat/ for the true story. (How many characters per line do I need again?)
-
Fags
Why Slashdot Sucks
Any given story posted to slashdot's main page will inevitably result in few 'insightful', 'informative', or
'interesting' comments. While you may be asking yourself - I see all kinds of these posts for every story!
Well...you can be assured that this is due to the fact that the people who are moderating these posts - are MORONS!
It amazes me how one group of people can think they've got it figured out and everyone else out there is an
idiot for not feeling the same way they do. This of course is the sentiment of 99.9% of slashdot commentators who
always are pushing that in any case - LINUX is the choice that should be made - no matter what. It's this kind of
closed mindedness that hurts the reputation of Linux and shows to most of the world that people who use Linux are
absolute jackass morons.
Slashdot - while the concept seems somewhat interesting lacks several things. One of which is content. Now
the site says, 'News for nerds, Stuff that matters'...this is far from true. Let's examine a little more closely.
The phrase 'News for nerds' - well being that nerd is a rather broad topic these days, slashdot's editors have
opened the content engine up from interesting and cutting edge articles to crap such as 'AOL vs. Trillian' a topic
that has been beaten to death by many other crappy articles about AOL blocking access to their network resources.
Why do the editors allow such crap to pass by? Because they see it as a chance for more of their impotent jerk off
user base to spew their load of crap along to anyone who will pass by and read this gay and moronic comment. Ok,
now onto the 'Stuff that matters' ... I have seen may one article posted to slashdot's main page which in any way
MATTERS in the true sense of the word. Does it really MATTER that AOL has blocked Trillian's access to the aim
servers? No, it doesn't. Does it really matter if TrustE has a bad idea about how to stop spam - no...It sure
doesn't. As we can all see...not only does the site suck - so does its slogan.
Now...more onto the user base which constantly feels the need to post inane comments that have more to do
about inner crying because the world is not working the way they want it to. "But this is crap...why is AOL doing
this - is this legal?" Good input jack off. Perhaps some of you who post such stupidity will realize that you are
not only wasting your time, but in turn everyone who reads your comments grows more moronic and stupid by the day.
Read the rest of this comment...