# HG changeset patch # User Oleksandr Gavenko # Date 1456140895 -7200 # Node ID 870693ce6ff06c95657c648dc8e9893d22d991e9 # Parent 123f59618e87f2c592f01e6c68abfa818cbfe13a Fix my RST article style by 'check-format-policy' target. diff -r 123f59618e87 -r 870693ce6ff0 about-uri.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/about-uri.rst Mon Feb 22 13:34:55 2016 +0200 @@ -0,0 +1,58 @@ +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst + +================== + about URI schema +================== +.. contents:: + :local: + +About +===== + +See: + + * http://en.wikipedia.org/wiki/About:_URI_scheme + +Firefox +======= + + about: + same page as "Help -> About" + about:blank + blank page, useful for setting as your home page + about:buildconfig + show your Mozilla build options + about:cache + displays cache statistics and disk cache directory location + about:config + GUI for modifying user preferences + about:crashes + crash reports + about:credits + list of contributors to the Mozilla projects + about:licence + show product licences + about:licence + show product licences + about:logo + application logo + about:memory + memory usage (since Firefox 3.6) + about:mozilla + easter eggs - "Book of Mozilla" + about:plugins + lists all your plugins as well as other useful information + about:rights + your rights + about:robots + easter egg (since 2008-03-08 trunk builds) + about:sessionrestore + interface for viewing about last session + about:support + same page as "Help -> Troubleshooting information" (since Firefox 3.6) + +See: + + * http://kb.mozillazine.org/About_protocol_links + diff -r 123f59618e87 -r 870693ce6ff0 apache.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/apache.rst Mon Feb 22 13:34:55 2016 +0200 @@ -0,0 +1,20 @@ +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst + +==================== + Apache HTTP server +==================== +.. contents:: + :local: + +How to reload config file? +========================== + +For Linux:: + + $ /etc/init.d/apache2 restart + +or for FreeBSD:: + + $ /usr/local/etc/rc.d/apache2 restart + diff -r 123f59618e87 -r 870693ce6ff0 archive.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/archive.rst Mon Feb 22 13:34:55 2016 +0200 @@ -0,0 +1,18 @@ +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst + +==================== + Archive management +==================== +.. contents:: + :local: + +How crack password archive? +=========================== +:: + + $ rarcrack archive.ext [--threads thread_num] [--type rar|zip|7z] + +See: + + * http://rarcrack.sourceforge.net/ diff -r 123f59618e87 -r 870693ce6ff0 at.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/at.rst Mon Feb 22 13:34:55 2016 +0200 @@ -0,0 +1,27 @@ +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst + +============= + AT commands +============= +.. contents:: + :local: + +Spec +==== + +Nokia AT commands spec: + + http://wiki.forum.nokia.com/index.php/Category:AT_Command + Nokia AT command spec + http://www.forum.nokia.com/info/sw.nokia.com/id/95672052-6c77-488d-a055-acef77e4cdc5/AT_Command_Set_For_Nokia_GSM_And_WCDMA_Products_v1_2_en.pdf.html + AT Command Set For Nokia GSM And WCDMA Products v1.2 + +Motorola AT commands spec: + + * http://developer.motorola.com/docstools/developerguides/AT_Commands_Ref.pdf/ + * http://developer.motorola.com/docstools/developerguides/C24_AT_Commands.pdf/ + * http://developer.motorola.com/docstools/developerguides/G24-Lite_AT_Commands_Reference_Manual.pdf/ + * http://developer.motorola.com/docstools/developerguides/G24_AT_Commands_Developer_Guide.pdf/ + * http://developer.motorola.com/docstools/developerguides/iO270_Developer_Guide.pdf/ + diff -r 123f59618e87 -r 870693ce6ff0 auto-proof.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/auto-proof.rst Mon Feb 22 13:34:55 2016 +0200 @@ -0,0 +1,206 @@ +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst + +================ + Theorem prover +================ +.. contents:: + :local: + +Info/links +========== + + * http://en.wikipedia.org/wiki/Automated_theorem_proving + +proofgeneral +============ +:: + + $ sudo apt-get install proofgeneral + $ sudo apt-get install proofgeneral-coq + $ sudo apt-get install proofgeneral-misc + $ sudo apt-get install proofgeneral-doc + $ sudo apt-get install proofgeneral-minlog + +or build from source:: + + $ make clean + $ make compile EMACS=xemacs + $ cat ~/.emacs + ... + (load-file "dir/generic/proof-site.el") + ... + +See: + + * http://proofgeneral.inf.ed.ac.uk/ + +Isabelle +======== + +Isabelle is a generic proof assistant. + +It allows mathematical formulas to be expressed in a formal language and +provides tools for proving those formulas in a logical calculus. The main +application is the formalization of mathematical proofs and in particular +formal verification, which includes proving the correctness of computer +hardware or software and proving properties of computer languages and +protocols. + +See: + + * http://isabelle.in.tum.de/overview.html + * http://en.wikipedia.org/wiki/Isabelle_(theorem_prover) + +IsarMathLib +=========== + +The goal of the project is to create a library of formalized mathematics, +similar to the Mizar Mathematical Library, but written for the Isabelle/Isar +theorem prover (ZF logic). + +See: + + http://isarmathlib.org/ + Home page + http://savannah.nongnu.org/projects/isarmathlib + Project page + http://lists.nongnu.org/mailman/listinfo/isarmathlib-devel + Mail list + +This site is an experimental HTML rendering of fragments of the IsarMathLib +project. IsarMathLib is a library of mathematical proofs formally verified by +the Isabelle theorem proving environment. The formalization is based on the +Zermelo-Fraenkel set theory. + +Tiddly Formal Math +================== + +This site is an experimental TiddlyWiki rendering of fragments of the +IsarMathLib project. IsarMathLib is a library of mathematical proofs formally +verified by the Isabelle theorem proving environment. The formalization is +based on the Zermelo-Fraenkel set theory. + +See: + + * http://formalmath.tiddlyspot.com/ + +HOL Light +========= + +HOL Light is a computer program to help users prove interesting mathematical +theorems completely formally in higher order logic. It sets a very exacting +standard of correctness, but provides a number of automated tools and +pre-proved mathematical theorems (e.g. about arithmetic, basic set theory and +real analysis) to save the user work. It is also fully programmable, so users +can extend it with new theorems and inference rules without compromising its +soundness. + +Ocalm. + +See: + + * http://www.cl.cam.ac.uk/~jrh13/hol-light/index.html + +ACL2 +==== + +ACL2 (A Computational Logic for Applicative Common Lisp) is a software system +consisting of a programming language, an extensible theory in a first-order +logic, and a mechanical theorem prover. ACL2 is designed to support automated +reasoning in inductive logical theories, mostly for the purpose of software +and hardware verification. The input language and implementation of ACL2 are +built on Common Lisp. ACL2 is free, open source (GPL) software. + +:: + + $ sudo apt-get install acl2 + +See: + + * http://www.cs.utexas.edu/users/moore/acl2/ + * http://en.wikipedia.org/wiki/ACL2 + +PVS Specification and Verification System +========================================= + +Old (1992). Many article in 199x. + +The system is implemented in Common Lisp, and is released under the GNU +General Public License (GPL). + +See: + + * http://pvs.csl.sri.com/ + * http://en.wikipedia.org/wiki/Prototype_Verification_System + * http://www-formal.stanford.edu/clt/ARS/Entries/pvs + +The TPTP Problem Library for Automated Theorem Proving +====================================================== + +The TPTP (Thousands of Problems for Theorem Provers) is a library of test +problems for automated theorem proving (ATP) systems. The TPTP supplies the +ATP community with: + + * A comprehensive library of the ATP test problems that are available today, + in order to provide an overview and a simple, unambiguous reference + mechanism. + * A comprehensive list of references and other interesting information for + each problem. + * Arbitrary size instances of generic problems (e.g., the N-queens problem). + * A utility to convert the problems to existing ATP systems' formats. + * General guidelines outlining the requirements for ATP system evaluation. + * Standards for input and output for ATP systems. + +The principal motivation for the TPTP is to support the testing and evaluation +of ATP systems, to help ensure that performance results accurately reflect the +capabilities of the ATP system being considered. A common library of problems +is necessary for meaningful system evaluations, meaningful system comparisons, +repeatability of testing, and the production of statistically significant +results. The TPTP is such a library. + +See: + + * http://www.cs.miami.edu/~tptp/ + +SPASS +===== + +An Automated Theorem Prover for First-Order Logic with Equality. + +See: + + * http://www.spass-prover.org/index.html + +Competition +=========== + +See: + + * http://www.cs.miami.edu/~tptp/CASC/ + * http://www.cs.albany.edu/~nvm/cade.html + +Conference +========== + +IJCAR is a series of conferences on the topics of automated reasoning, +automated deduction, and related fields. It is organized semi-regularly as a +merger of other meetings. IJCAR replaces those independent conferences in the +years it takes place. The conference is organized by CADE Inc., and CADE has +always been one of the conferences partaking in IJCAR. + +See: + + * http://www.ijcar.org/ + * http://en.wikipedia.org/wiki/International_Joint_Conference_on_Automated_Reasoning + +Top 100 +======= + + http://www.cs.ru.nl/~freek/100/ + (winner) + http://personal.stevens.edu/~nkahl/Top100Theorems.html + (orig list) + http://www.cse.unsw.edu.au/~kleing/top100/#5 + (Isabelle) + diff -r 123f59618e87 -r 870693ce6ff0 cellular-automaton.rst --- a/cellular-automaton.rst Mon Feb 22 13:34:05 2016 +0200 +++ b/cellular-automaton.rst Mon Feb 22 13:34:55 2016 +0200 @@ -1,4 +1,4 @@ -.. -*- coding: utf-8 -*- +.. -*- coding: utf-8; -*- .. include:: HEADER.rst ================ diff -r 123f59618e87 -r 870693ce6ff0 color.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/color.rst Mon Feb 22 13:34:55 2016 +0200 @@ -0,0 +1,15 @@ +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst + +======= + Color +======= +.. contents:: + :local: + +Color names +=========== + + * http://en.wikipedia.org/wiki/Web_colors + * http://en.wikipedia.org/wiki/X11_color_names + diff -r 123f59618e87 -r 870693ce6ff0 cracking.rst --- a/cracking.rst Mon Feb 22 13:34:05 2016 +0200 +++ b/cracking.rst Mon Feb 22 13:34:55 2016 +0200 @@ -1,4 +1,4 @@ -.. coding: utf-8 +.. -*- coding: utf-8; -*- .. include:: HEADER.rst =========== diff -r 123f59618e87 -r 870693ce6ff0 devel-rules.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/devel-rules.rst Mon Feb 22 13:34:55 2016 +0200 @@ -0,0 +1,594 @@ +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst + +============================ + Software development rules +============================ +.. contents:: + :local: + +General discussion +================== + +See: + + http://en.wikipedia.org/wiki/List_of_software_development_philosophies + http://en.wikipedia.org/wiki/List_of_eponymous_laws + +Principle of good enough (POGE) +=============================== + +It favours quick-and-simple (but potentially extensible) designs over +elaborate systems designed by committees. + +Once the quick-and-simple design is deployed, it can then evolve as needed, +driven by user requirements. + +This kind of design is not appropriate in systems where it is not possible to +evolve the system over time, or where the full functionality is required from +the start. + +See: + + http://en.wikipedia.org/wiki/Principle_of_good_enough + +No Silver Bullet +================ + +There is no single development, in either technology or management technique, +which by itself promises even one order of magnitude improvement within a +decade in productivity, in reliability, in simplicity. + +See: + + http://en.wikipedia.org/wiki/No_Silver_Bullet + +Rule of thumb +============= + +A rule of thumb is a principle that postulate in some case use simple +procedure wich produce approximate result instead use complex but exact +produce. + +See: + + http://en.wikipedia.org/wiki/Rule_of_thumb + +The Zero One or Infinity +======================== + +The Zero One or Infinity (ZOI) rule is a rule of thumb in software design. It +suggests that arbitrary limits on the number of instances of a particular +entity should not be allowed. Specifically, that an entity should either be +forbidden entirely, one should be allowed, or any number (presumably, to the +limit of available storage) of them should be allowed. It should not be the +software that puts a hard limit on the number of instances of the entity. + + http://en.wikipedia.org/wiki/Zero_One_Infinity + +80-20 rule (pareto principle) +============================= + +This rule postulate that roughly 80% of the effects come from 20% of the +causes. + +This rule applied to optimisation (most time spent by program only by little +piece of code), functionality (80% of users use only 20% of program +functionality); bugs (fixing the top 20% of most reported bugs solve 80% of +the error and crashes). + +See: + + http://en.wikipedia.org/wiki/80:20_rule + +1% rule +======= + +The 1% rule states that the number of people who create content on the +internet represents approximately 1% (or less) of the people actually viewing +that content. + +See: + + http://en.wikipedia.org/wiki/1%25_rule_%28Internet_culture%29 + +Parkinson's Law +=============== + +Work expands so as to fill the time available for its completion. + +Data expands to fill the space available for storage. + +See: + + http://en.wikipedia.org/wiki/Parkinson%27s_law + +Ninety-ninety rule +================== + +The first 90% of the code accounts for the first 10% of the development time. +The remaining 10% of the code accounts for the other 90% of the development +time. + +See: + + http://en.wikipedia.org/wiki/Ninety-ninety_rule + +Wirth's law +=========== + +Software is getting slower more rapidly than hardware becomes faster. + +See: + + http://en.wikipedia.org/wiki/Wirth%27s_law + +Student syndrome +================ + +Student syndrome refers to the phenomenon that many people will start to fully +apply themselves to a task just at the last possible moment before a deadline. + +The student syndrome is a form of procrastination (). + +See: + + http://en.wikipedia.org/wiki/Student_syndrome + +Conway's Law +============ + +...organizations which design systems ... are constrained to produce designs +which are copies of the communication structures of these organizations. + +Example: Consider a two-person team of software engineers, A and B. Say A +designs and codes a software class X. Later, the team discovers that class X +needs some new features. If A adds the features, A is likely to simply expand X +to include the new features. If B adds the new features, B may be afraid of +breaking X, and so instead will create a new derived class X2 that inherits X's +features, and puts the new features in X2. So the final design is a reflection +of who implemented the functionality. + +A real life example: NASA's Mars Climate Orbiter crashed because one team used +United States customary units (e.g., inches, feet and pounds) while the other +used metric units for a key spacecraft operation. + +See: + + http://en.wikipedia.org/wiki/Conway%27s_Law + +Brooks's law +============ + +It takes some time for the people added to a project to become productive. + +Communication overheads increase as the number of people increases. + +Adding manpower to a late software project makes it later. + +See: + + http://en.wikipedia.org/wiki/Brooks%27_law + +Code bloat +========== + +Code bloat is the production of code that is perceived as unnecessarily long, +slow, or otherwise wasteful of resources. Code bloat generally refers to +source code size but sometimes is used to refer to the generated code size or +even the binary file size. + + http://en.wikipedia.org/wiki/Code_bloat + +Software bloat +============== + +Software bloat is a term used to describe the tendency of newer computer +programs to have a larger installation footprint, or have many unnecessary +features that are not used by end users, or just generally use more system +resources than necessary, while offering little or no benefit to its users. + + +Comparison of Microsoft Windows minimum hardware requirements (for 32-bit +versions): + +Windows version Processor Memory Hard disk +Windows 95[4] 25 MHz 4 MB ~50 MB +Windows 98[5] 66 MHz 16 MB ~200 MB +Windows 2000[6] 133 MHz 32 MB 650 MB +Windows XP[7] 233 MHz 64 MB 1.5 GB +Windows Vista[8] 800 MHz 512 MB 15 GB +Windows 7[9] 1 GHz 1 GB 16 GB + +.. epigraph:: + + Every program attempts to expand until it can read mail. Those programs which + cannot so expand are replaced by ones which can. + + -- Jamie Zawinski + +Second-system effect +==================== + +In computing, the second-system effect or sometimes the second-system syndrome +refers to the tendency, when following on from a relatively small, elegant, +and successful system, to design the successor as an elephantine, +feature-laden monstrosity. The term was first used by Fred Brooks in his +classic The Mythical Man-Month.[1] It described the jump from a set of simple +operating systems on the IBM 700/7000 series to OS/360 on the 360 series. + +Inner-platform effect +===================== + +The inner-platform effect is the tendency of software architects to create a +system so customizable as to become a replica, and often a poor replica, of +the software development platform they are using. + +XXX read more http://thedailywtf.com/Articles/The_Inner-Platform_Effect.aspx + + http://en.wikipedia.org/wiki/Inner-platform_effect + +Feature creep +============= + +Feature creep is the proliferation of features in a product such as computer +software. Extra features go beyond the basic function of the product and so +can result in baroque over-complication, or "featuritis", rather than simple, +elegant design. + + http://en.wikipedia.org/wiki/Feature_creep + +Bullet-point engineering +======================== + +Bullet-point engineering is a software design anti-pattern where developers +use the features of competing software packages as checklists of features to +implement in their own product. These features are often implemented poorly +and haphazardly, without any real design, merely so they can be added to a +bulleted list of features in marketing material. Bullet point engineering +often leads to feature creep and software bloat but may also simply result in +a poorly designed imitative product. + + http://en.wikipedia.org/wiki/Bullet-point_engineering + +KISS +==== + +Keep it simple and stupid, or keep it simple, stupid! + +Instruction creep and function creep, two instances of creeping featuritis, +are examples of failure to follow the KISS principle in software development. + + http://en.wikipedia.org/wiki/KISS_principle + +Minimalism +========== + +In computing, minimalism refers to the application of minimalist philosophies +and principles in hardware and software design and usage. + + http://en.wikipedia.org/wiki/Minimalism_%28computing%29 + +Unix philosophy +=============== + +.. epigraph:: + + "Do one thing and do it well." + + -- Doug McIlroy + +.. epigraph:: + + "Write programs that do one thing and do it well. Write programs to work + together. Write programs to handle text streams, because that is a universal + interface." + + -- Doug McIlroy + +.. epigraph:: + + #. You cannot tell where a program is going to spend its time. Bottlenecks + occur in surprising places, so do not try to second guess and put in a speed + hack until you've proven that's where the bottleneck is. + #. Measure. Do not tune for speed until your performance analysis tool tells + you which part of the code overwhelms the rest. + #. Fancy algorithms tend to run more slowly on small data sets than simple + algorithms. They tend to have a large constant factor in O(n) analysis, and + n is usually small. So don't get fancy unless Rule 2 indicates that n is big + enough. + #. Simplify your algorithms and data structures wherever it makes sense because + fancy algorithms are more difficult to implement without defects. The data + structures in most programs can be built from array lists, linked lists, + hash tables, and binary trees. + #. Data dominates. If you have chosen the right data structures and organized + things well, the algorithms will almost always be self-evident. Data + structures, not algorithms, are central to programming. + + -- Pike: Notes on Programming in C. + +.. epigraph:: + + 1. Small is beautiful. + 2. Make each program do one thing well. + 3. Build a prototype as soon as possible. + 4. Choose portability over efficiency. + 5. Store data in flat text files. + 6. Use software leverage to your advantage. + 7. Use shell scripts to increase leverage and portability. + 8. Avoid captive user interfaces. + 9. Make every program a filter. + + -- Mike Gancarz: The UNIX Philosophy + +With this not all agree: + + 1. Allow the user to tailor the environment. + 2. Make operating system kernels small and lightweight. + 3. Use lowercase and keep it short. + 4. Save trees. + 5. Silence is golden. + 6. Think parallel. + 7. The sum of the parts is greater than the whole. + 8. Look for the 90-percent solution. + 9. Worse is better. + 10. Think hierarchically. + + +** Misc. + +"Unix is simple. It just takes a genius to understand its simplicity." + -– Dennis Ritchie +"Unix never says 'please'." + -– Rob Pike + + http://en.wikipedia.org/wiki/Unix_philosophy + +Worse is better +=============== + +In the "Worse is better" design style, simplicity of both the interface and +the implementation is more important than any other attribute of the system — +including correctness, consistency and completeness. + +Simplicity + The design must be simple, both in implementation and interface. It is + more important for the implementation to be simpler than the interface. + Simplicity is the most important consideration in a design. +Correctness + The design must be correct in all observable aspects. It is slightly better + to be simple than correct. +Consistency + The design must not be overly inconsistent. Consistency can be sacrificed + for simplicity in some cases, but it is better to drop those parts of the + design that deal with less common circumstances than to introduce either + implementational complexity or inconsistency. +Completeness + The design must cover as many important situations as is practical. All + reasonably expected cases should be covered. Completeness can be sacrificed + in favor of any other quality. In fact, completeness must be sacrificed + whenever implementation simplicity is jeopardized. Consistency can be + sacrificed to achieve completeness if simplicity is retained; especially + worthless is consistency of interface. + + http://dreamsongs.com/WIB.html + Lisp: Good News, Bad News, How to Win Big + +The right thing +=============== + +The MIT approach (known as "The right thing"): + +Simplicity + The design must be simple, both in implementation and interface. It is + more important for the interface to be simpler than the implementation. +Correctness + The design must be correct in all observable aspects. Incorrectness is + simply not allowed. +Consistency + The design must be consistent. A design is allowed to be slightly less + simple and less complete to avoid inconsistency. Consistency is as important + as correctness. +Completeness + The design must cover as many important situations as is practical. All + reasonably expected cases must be covered. Simplicity is not allowed to + overly reduce completeness. + + http://dreamsongs.com/WIB.html + Lisp: Good News, Bad News, How to Win Big + +YAGNI +===== + +"You aren't gonna need it" (or YAGNI for short) is the principle in extreme +programming that programmers should not add functionality until it is +necessary. + + http://en.wikipedia.org/wiki/You_ain%27t_gonna_need_it + +DRY (DIE) +========= + +Don't Repeat Yourself (DRY) or Duplication is Evil (DIE). + + * VCS allow multiple and diverging copies ("branches"). + * Source code generation. + + http://en.wikipedia.org/wiki/Don%27t_repeat_yourself + +Do it yourself (DIY) +==================== + +Do it yourself (or DIY) is a term used to describe building, modifying, or +repairing of something without the aid of experts or professionals. + +when tasklist longer then people life mutch easy use already written libraries +then wrote own. + + http://en.wikipedia.org/wiki/Do_it_yourself + +Once and Only Once (OAOO) +========================= + +MoSCoW Method +============= + +The capital letters in MoSCoW stand for: + + * M - MUST have this (included in the current delivery timebox in order + for it to be a success). + * S - SHOULD have this if at all possible (critical to the success of the + project, but are not necessary for delivery in the current delivery + timebox). + * C - COULD have this if it does not affect anything else (nice to have). + * W - WON'T have this time but WOULD like in the future. + + http://en.wikipedia.org/wiki/MoSCoW_Method + +Separation of concerns +====================== + +In computer science, separation of concerns (SoC) is the process of separating +a computer program into distinct features that overlap in functionality as +little as possible. A concern is any piece of interest or focus in a program. +Typically, concerns are synonymous with features or behaviors. Progress +towards SoC is traditionally achieved through modularity of programming and +encapsulation (or "transparency" of operation), with the help of information +hiding. Layered designs in information systems are also often based on +separation of concerns (e.g., presentation layer, business logic layer, data +access layer, database layer). + +HyperText Markup Language (HTML) and cascading style sheets (CSS) are +languages intended to separate style from content. + + http://en.wikipedia.org/wiki/Separation_of_concerns + +Modular design +============== + +In systems engineering, modular design — or "modularity in design" — is an +approach that subdivides a system into smaller parts (modules) that can be +independently created and then used in different systems to drive multiple +functionalities. + + http://en.wikipedia.org/wiki/Modular_design + +Occam's razor +============= + +"entia non sunt multiplicanda praeter necessitatem" + +Entities must not be multiplied beyond necessity. + +Code and fix +============ + +Programmers immediately begin producing code. Bugs must be fixed before the +product can be shipped. + + http://en.wikipedia.org/wiki/Code_and_fix + +Cowboy coding +============= + +Cowboy coding is a term used to describe software development where the +developers have autonomy over the development process. This includes control +of the project's schedule, algorithms, tools, and coding style. + +A cowboy coder can be a lone developer or part of a group of developers with +either no external management or management that controls only non-development +aspects of the project, such as its nature, scope, and feature set (the +"what", but not the "how"). + + http://en.wikipedia.org/wiki/Cowboy_coding + +Extreme Programming +=================== + + http://en.wikipedia.org/wiki/Extreme_Programming + +Hollywood Principle +=================== + +In computer programming, the Hollywood Principle is stated as "don't call us, +we'll call you." It has applications in software engineering; see also +implicit invocation for a related architectural principle. + + http://en.wikipedia.org/wiki/Hollywood_Principle + +Inversion of control +==================== + +Inversion of control, or IoC, is an abstract principle describing an aspect of +some software architecture designs in which the flow of control of a system is +inverted in comparison to procedural programming. + + http://en.wikipedia.org/wiki/Inversion_of_control + +Literate programming +==================== + + http://en.wikipedia.org/wiki/Literate_Programming + +Model-driven architecture +========================= + + http://en.wikipedia.org/wiki/Model-driven_architecture + +Quick-and-dirty +=============== + +Quick-and-dirty is a term used in reference to anything that is an easy way to +implement a workaround or "kludge." Its usage is popular among programmers, +who use it to describe a crude solution or programming implementation that is +imperfect, inelegant, or otherwise inadequate, but which solves or masks the +problem at hand, and is generally faster and easier to put in place than a +proper solution. + + http://en.wikipedia.org/wiki/Quick-and-dirty + +Release early, release often +============================ + +Release early, release often (sometimes abbreviated RERO) is a software +development philosophy that emphasizes the importance of early and frequent +releases in creating a tight feedback loop between developers and testers or +users. + + http://en.wikipedia.org/wiki/Release_early,_release_often + +Test-driven development +======================= + +Test-driven development (TDD) is a software development technique that relies +on the repetition of a very short development cycle: First the developer +writes a failing automated test case that defines a desired improvement or new +function, then produces code to pass that test and finally refactors the new +code to acceptable standards. + + http://en.wikipedia.org/wiki/Test-driven_development + +Unified Process +=============== + +The Unified Software Development Process or Unified Process is a popular +iterative and incremental software development process framework. The +best-known and extensively documented refinement of the Unified Process is the +Rational Unified Process (RUP). + + http://en.wikipedia.org/wiki/Unified_Process + +Waterfall model +=============== + + 1. Requirements specification + 2. Design + 3. Construction (AKA implementation or coding) + 4. Integration + 5. Testing and debugging (AKA Validation) + 6. Installation + 7. Maintenance + + http://en.wikipedia.org/wiki/Waterfall_model + +* Do it yourself. diff -r 123f59618e87 -r 870693ce6ff0 dns.rst --- a/dns.rst Mon Feb 22 13:34:05 2016 +0200 +++ b/dns.rst Mon Feb 22 13:34:55 2016 +0200 @@ -4,6 +4,8 @@ ====== DNS. ====== +.. contents:: + :local: About DNS resolving protocol. ============================= diff -r 123f59618e87 -r 870693ce6ff0 freedom.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/freedom.rst Mon Feb 22 13:34:55 2016 +0200 @@ -0,0 +1,258 @@ +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst + +============================ + The Open Source Definition +============================ +.. contents:: + :local: + +Version 1.9 + +The indented, italicized sections below appear as annotations to the Open Source +Definition (OSD) and are not a part of the OSD. A plain version of the OSD without +annotations can be found here. Introduction + +Open source doesn't just mean access to the source code. The distribution terms of +open-source software must comply with the following criteria: + +1. Free Redistribution + +The license shall not restrict any party from selling or giving away the software as a +component of an aggregate software distribution containing programs from several different +sources. The license shall not require a royalty or other fee for such sale. + +Rationale: By constraining the license to require free redistribution, we eliminate the +temptation to throw away many long-term gains in order to make a few short-term sales +dollars. If we didn't do this, there would be lots of pressure for cooperators to defect. + +2. Source Code + +The program must include source code, and must allow distribution in source code as well +as compiled form. Where some form of a product is not distributed with source code, there +must be a well-publicized means of obtaining the source code for no more than a reasonable +reproduction cost preferably, downloading via the Internet without charge. The source code +must be the preferred form in which a programmer would modify the program. Deliberately +obfuscated source code is not allowed. Intermediate forms such as the output of a +preprocessor or translator are not allowed. + +Rationale: We require access to un-obfuscated source code because you can't evolve +programs without modifying them. Since our purpose is to make evolution easy, we require +that modification be made easy. + +3. Derived Works + +The license must allow modifications and derived works, and must allow them to be +distributed under the same terms as the license of the original software. + +Rationale: The mere ability to read source isn't enough to support independent peer review +and rapid evolutionary selection. For rapid evolution to happen, people need to be able to +experiment with and redistribute modifications. + +4. Integrity of The Author's Source Code + +The license may restrict source-code from being distributed in modified form only if the +license allows the distribution of "patch files" with the source code for the purpose of +modifying the program at build time. The license must explicitly permit distribution of +software built from modified source code. The license may require derived works to carry a +different name or version number from the original software. + +Rationale: Encouraging lots of improvement is a good thing, but users have a right to know +who is responsible for the software they are using. Authors and maintainers have +reciprocal right to know what they're being asked to support and protect their +reputations. + +Accordingly, an open-source license must guarantee that source be readily available, but +may require that it be distributed as pristine base sources plus patches. In this way, +"unofficial" changes can be made available but readily distinguished from the base source. + +5. No Discrimination Against Persons or Groups + +The license must not discriminate against any person or group of persons. + +Rationale: In order to get the maximum benefit from the process, the maximum diversity of +persons and groups should be equally eligible to contribute to open sources. Therefore we +forbid any open-source license from locking anybody out of the process. + +Some countries, including the United States, have export restrictions for certain types of +software. An OSD-conformant license may warn licensees of applicable restrictions and +remind them that they are obliged to obey the law; however, it may not incorporate such +restrictions itself. + +6. No Discrimination Against Fields of Endeavor + +The license must not restrict anyone from making use of the program in a specific field of +endeavor. For example, it may not restrict the program from being used in a business, or +from being used for genetic research. + +Rationale: The major intention of this clause is to prohibit license traps that prevent +open source from being used commercially. We want commercial users to join our community, +not feel excluded from it. + +7. Distribution of License + +The rights attached to the program must apply to all to whom the program is redistributed +without the need for execution of an additional license by those parties. + +Rationale: This clause is intended to forbid closing up software by indirect means such as +requiring a non-disclosure agreement. + +8. License Must Not Be Specific to a Product + +The rights attached to the program must not depend on the program's being part of a +particular software distribution. If the program is extracted from that distribution and +used or distributed within the terms of the program's license, all parties to whom the +program is redistributed should have the same rights as those that are granted in +conjunction with the original software distribution. + +Rationale: This clause forecloses yet another class of license traps. + +9. License Must Not Restrict Other Software + +The license must not place restrictions on other software that is distributed along with +the licensed software. For example, the license must not insist that all other programs +distributed on the same medium must be open-source software. + +Rationale: Distributors of open-source software have the right to make their own choices +about their own software. + +Yes, the GPL is conformant with this requirement. Software linked with GPLed libraries +only inherits the GPL if it forms a single work, not any software with which they are +merely distributed. + +10. License Must Be Technology-Neutral + +No provision of the license may be predicated on any individual technology or style of +interface. + +Rationale: This provision is aimed specifically at licenses which require an explicit +gesture of assent in order to establish a contract between licensor and licensee. +Provisions mandating so-called "click-wrap" may conflict with important methods of +software distribution such as FTP download, CD-ROM anthologies, and web mirroring; such +provisions may also hinder code re-use. Conformant licenses must allow for the possibility +that (a) redistribution of the software will take place over non-Web channels that do not +support click-wrapping of the download, and that (b) the covered code (or re-used portions +of covered code) may run in a non-GUI environment that cannot support popup dialogues. + +* Social Contract with the Free Software Community + +Version 1.1 + +1. Debian will remain 100% free + +We provide the guidelines that we use to determine if a work is free in the document +entitled The Debian Free Software Guidelines. We promise that the Debian system and all +its components will be free according to these guidelines. We will support people who +create or use both free and non-free works on Debian. We will never make the system +require the use of a non-free component. + +2. We will give back to the free software community + +When we write new components of the Debian system, we will license them in a manner +consistent with the Debian Free Software Guidelines. We will make the best system we can, +so that free works will be widely distributed and used. We will communicate things such as +bug fixes, improvements and user requests to the upstream authors of works included in our +system. + +3. We will not hide problems + +We will keep our entire bug report database open for public view at all times. Reports +that people file online will promptly become visible to others. + +4. Our priorities are our users and free software + +We will be guided by the needs of our users and the free software community. We will place +their interests first in our priorities. We will support the needs of our users for +operation in many different kinds of computing environments. We will not object to +non-free works that are intended to be used on Debian systems, or attempt to charge a fee +to people who create or use such works. We will allow others to create distributions +containing both the Debian system and other works, without any fee from us. In furtherance +of these goals, we will provide an integrated system of high-quality materials with no +legal restrictions that would prevent such uses of the system. + +5. Works that do not meet our free software standards + +We acknowledge that some of our users require the use of works that do not conform to the +Debian Free Software Guidelines. We have created contrib and non-free areas in our archive +for these works. The packages in these areas are not part of the Debian system, although +they have been configured for use with Debian. We encourage CD manufacturers to read the +licenses of the packages in these areas and determine if they can distribute the packages +on their CDs. Thus, although non-free works are not a part of Debian, we support their use +and provide infrastructure for non-free packages (such as our bug tracking system and +mailing lists). + +* The Debian Free Software Guidelines (DFSG) + + 1. Free Redistribution + +The license of a Debian component may not restrict any party from selling or giving away +the software as a component of an aggregate software distribution containing programs from +several different sources. The license may not require a royalty or other fee for such +sale. + + 2. Source Code + +The program must include source code, and must allow distribution in source code as well +as compiled form. + +3. Derived Works + +The license must allow modifications and derived works, and must allow them to be +distributed under the same terms as the license of the original software. + +4. Integrity of The Author's Source Code + +The license may restrict source-code from being distributed in modified form _only_ if the +license allows the distribution of patch files with the source code for the purpose of +modifying the program at build time. The license must explicitly permit distribution of +software built from modified source code. The license may require derived works to carry a +different name or version number from the original software. (This is a compromise. The +Debian group encourages all authors not to restrict any files, source or binary, from +being modified.) + +5. No Discrimination Against Persons or Groups + +The license must not discriminate against any person or group of persons. + +6. No Discrimination Against Fields of Endeavor + +The license must not restrict anyone from making use of the program in a specific field of +endeavor. For example, it may not restrict the program from being used in a business, or +from being used for genetic research. + +7. Distribution of License + +The rights attached to the program must apply to all to whom the program is redistributed +without the need for execution of an additional license by those parties. + +8. License Must Not Be Specific to Debian + +The rights attached to the program must not depend on the program's being part of a Debian +system. If the program is extracted from Debian and used or distributed without Debian but +otherwise within the terms of the program's license, all parties to whom the program is +redistributed should have the same rights as those that are granted in conjunction with +the Debian system. + +9. License Must Not Contaminate Other Software + +The license must not place restrictions on other software that is distributed along with +the licensed software. For example, the license must not insist that all other programs +distributed on the same medium must be free software. + +10. Example Licenses + +The GPL, BSD, and Artistic licenses are examples of licenses that we consider free. + +* The Free Software Definition + +Free software is a matter of the users' freedom to run, copy, distribute, study, change +and improve the software. More precisely, it refers to four kinds of freedom, for the +users of the software: + + * The freedom to run the program, for any purpose (freedom 0). + * The freedom to study how the program works, and adapt it to your needs (freedom 1). + Access to the source code is a precondition for this. + * The freedom to redistribute copies so you can help your neighbor (freedom 2). + * The freedom to improve the program, and release your improvements to the public, so + that the whole community benefits (freedom 3). + * Access to the source code is a precondition for this. diff -r 123f59618e87 -r 870693ce6ff0 ftp.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/ftp.rst Mon Feb 22 13:34:55 2016 +0200 @@ -0,0 +1,19 @@ +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst + +===== + FTP +===== +.. contents:: + :local: + +~/.netrc file +============= + +``~/.netrc`` store connection and authentication info for FVP clients in form of +plain text file:: + + machine ... login ... password ... + +Also available macro definition. + diff -r 123f59618e87 -r 870693ce6ff0 gtd.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/gtd.rst Mon Feb 22 13:34:55 2016 +0200 @@ -0,0 +1,25 @@ +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst + +====================================== + Getting thins done. Time management. +====================================== +.. contents:: + :local: + +Хронофаги. +========== + + * Желание знать все детали. + * Недостатки кооперации или разделения труда. + * Недостатки планирования. + * Нечеткая постановка цели. + * Обсуждение сложных вопросов без надлежащей подготовки. + * Отвлекающая обстановка. + * Отрывающие от дел телефонные звонки, письма и разговоры. + * Отсутствие приоритетов в делах. + * Попытка слишком много сделать за один раз. + * Потеря интереса к проекту. + * Распорядок дня не увязан с ритмом продуктивности. + * Синдром «откладывания». + diff -r 123f59618e87 -r 870693ce6ff0 ipa.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/ipa.rst Mon Feb 22 13:34:55 2016 +0200 @@ -0,0 +1,16 @@ +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst + +===== + IPA +===== +.. contents:: + :local: + +See: + + * http://en.wikipedia.org/wiki/International_Phonetic_Alphabet + * http://en.wikipedia.org/wiki/English_phonology + * http://en.wikipedia.org/wiki/Old_English_phonology + * http://en.wikipedia.org/wiki/Russian_phonology + * http://en.wikipedia.org/wiki/Ukrainian_phonology diff -r 123f59618e87 -r 870693ce6ff0 laser-disk.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/laser-disk.rst Mon Feb 22 13:34:55 2016 +0200 @@ -0,0 +1,186 @@ +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst + +============ + Laser disk +============ +.. contents:: + :local: + +What best DVD-R or DVD+R? +========================= + +The DVD-R format was developed by Pioneer in 1997 vc DVD+R in 2002 by Sony. + +DVD+R format was not an official DVD format until January 25, 2008. + +DVD-R(W) and DVD+R(W) format are incompatible. + +DVD-R(W) use amplitude modulation, DVD+R(W) use phase modulation, so more reliable. + +On multi-session DVD-R(W) disk any session take up to 96 MB in time on DVD+R(W) +every session take exactly 2 MB. + +DVD+R(W) win! + +See + + http://en.wikipedia.org/wiki/DVD-R + http://en.wikipedia.org/wiki/DVD%2BR + +What capacity of DVD? +===================== + ++----------+-------------------------------------------+ +| | Capacity | ++ Type +-----------+---------------+------+--------+ +| | sectors | bytes | GB | GiB | +| | 2,048B | | | | ++----------+-----------+---------------+------+--------+ +|DVD-R (SL)| 2,298,496 | 4,707,319,808 | 4.7 | 4.384 | +|DVD+R (SL)| 2,295,104 | 4,700,372,992 | 4.7 | 4.378 | +|DVD-R DL | 4,171,712 | 8,543,666,176 | 8.5 | 7.957 | +|DVD+R DL | 4,173,824 | 8,547,991,552 | 8.5 | 7.961 | ++----------+-----------+---------------+------+--------+ + +Vendor +====== + +** Verbatim. + +Archival Grade CD & DVD - for store critical data. + + http://www.verbatim.ru + http://www.verbatim.com/optical/archival/ + +** TDK. + + http://www.tdk-media.com + +** Intenso. + + http://www.intenso.de + +* Lifetime. + +What is the life expectancy of a CD-R? +====================================== + +Approximately 100 years under proper storage conditions (from TDK support). + + http://www.cd-info.com/archiving/ + +How many times can I rewrite to a CD-RW? +======================================== + +A CD-RW disc can be erased and rewritten up to a 1,000 times. Reliability and +performance will not decrease, even as the number of rewrites increase. + +Make an ISO image +================= +:: + + $ dd if=/dev/dvd of=dvd.iso # for dvd + $ dd if=/dev/cdrom of=cd.iso # for cdrom + $ dd if=/dev/scd0 of=cd.iso # if cdrom is scsi + + $ mkisofs -o /tmp/cd.iso /tmp/directory/ # from file hierarchy + +Burning tools +============= + +** cdrtools. + +In 2006 build system of cdrtools changed and have CDDL, which incomputable +with GPL. + +See + + http://cdrecord.berlios.de/private/cdrecord.html + http://en.wikipedia.org/wiki/Cdrecord + +** cdrkit. + +Fully GPL alternative for cdrtools. Includes: + + * wodim (an acronym for write optical disk media), which was forked from the cdrecord program in + cdrtools. + * icedax (an acronym for incredible digital audio extractor), which was forked from the cdda2wav + program in cdrtools. + * genisoimage (short for generate ISO image), which was forked from the mkisofs program in + cdrtools. + +See + + http://www.cdrkit.org/ + http://en.wikipedia.org/wiki/Cdrkit + +Installing under Debian:: + + $ sudo apt-get install wodim genisoimage + +Cygwin (cdrecord is symlink to wodim, mkisofs is symlink to genisoimage, cdrkit contain only +READMY):: + + $ setup.exe -p cdrkit,wodim,genisoimage + +Make iso image:: + + $ genisoimage -A "" -gui -J -R -o ... + + is up to 128 bytes. -J adds Joliet directory records wich useful on +Windows. -R adds the Rock Ridge protocol. + +To test your image mount it (on Linux):: + + $ sudo mount -t iso9660 -o loop,ro + +Burn iso image +============== + +cdrskin +------- + +See + + http://scdbackup.sourceforge.net/cdrskin_eng.html + http://en.wikipedia.org/wiki/Cdrskin + + $ sudo apt-get install cdrskin + +xorriso +------- + +xorriso copies file objects from POSIX compliant filesystems into Rock Ridge +enhanced ISO 9660 filesystems and allows session-wise manipulation of such +filesystems. It can load the management information of existing ISO images and +it writes the session results to optical media or to filesystem objects. + +Vice versa xorriso is able to restore file objects from ISO 9660 filesystems. + +See + + http://scdbackup.webframe.org/xorriso_eng.html + http://en.wikipedia.org/wiki/xorriso + +ImgBurn +------- + +ImgBurn is a lightweight CD / DVD / HD DVD / Blu-ray burning application that +everyone should have in their toolkit! + +For Windows 95/98/2000/XP/Vista/2008/7, work in Wine under Linux. + + http://www.imgburn.com/ + home page + +** CDBurnerXP. + +Это бесплатная программа для записи CD и DVD, Blu-Ray и HD-DVD дисков. Она +поддерживает запись и создание ISO-образов. + +For Windows XP/Vista/2008/7. Require .NET >= version 2.0. + + http://www.cdburnerxp.se/ru/home + home page + diff -r 123f59618e87 -r 870693ce6ff0 lpt.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/lpt.rst Mon Feb 22 13:34:55 2016 +0200 @@ -0,0 +1,47 @@ +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst + +===== + LPT +===== +.. contents:: + :local: + +USB to LPT chip +=============== + +** PL-2305. + +The PL-2305 USB-to-IEEE-1284 Bridge Controller is a low-cost high-performance single chip solution +that provides bi-directional connectivity between any standard IEEE-1284 compliant parallel port +devices and the Universal Serial Bus (USB) interface. + + * Universal Serial Bus Specification Rev. 1.1 compliant + * USB full speed communication and bus powered + * USB Printer Class Specification 1.0 compliant + * IEEE-1284 1994 (bi-directional parallel interface) specification compliant + * Optional external EEPROM for customized USB Vendor ID, Product ID, Device Release Number, + Manufacturer String Descriptor, Product String Descriptor, Serial Number String Descriptor, and + any other string descriptors up to 248 bytes in total size + * Low-level printer class drivers provided for Windows 98, and Windows 2000 + * 48-Pin SSOP package + +:: + + $ lsusb + ... ID 067b:2305 Prolific Technology, Inc. PL2305 Parallel Port + +See: + + http://www.prolific.com.tw/eng/products.asp?id=6 + About page. + http://www.prolific.com.tw/eng/downloads.asp?ID=36 + Driver download page. + +USB to LPT driver +================= + +** Linux. + +See 'linux-src/drivers/usb/class/usblp.c'. + diff -r 123f59618e87 -r 870693ce6ff0 mc.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/mc.rst Mon Feb 22 13:34:55 2016 +0200 @@ -0,0 +1,15 @@ +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst + +==================== + Midnight commander +==================== +.. contents:: + :local: + +Useful key binding +================== +:: + + M-h display the history for the current input line. + M-H displays the directory history, equivalent to depressing the 'v' with the mouse. diff -r 123f59618e87 -r 870693ce6ff0 nntp.rst --- a/nntp.rst Mon Feb 22 13:34:05 2016 +0200 +++ b/nntp.rst Mon Feb 22 13:34:55 2016 +0200 @@ -4,6 +4,8 @@ ======= NNTP. ======= +.. contents:: + :local: Installing INN2 on Debian. ========================== diff -r 123f59618e87 -r 870693ce6ff0 ntp.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/ntp.rst Mon Feb 22 13:34:55 2016 +0200 @@ -0,0 +1,52 @@ +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst + +===== + NTP +===== +.. contents:: + :local: + +What is NTP? +============ + +NTP is a protocol to synchronizing the clocks on host using publicly +available NTP servers. + +How use? +======== + +To use you must know NTP servers. Here list some of them:: + + 0.debian.pool.ntp.org 1.debian.pool.ntp.org + 2.debian.pool.ntp.org + uk.pool.ntp.org ua.pool.ntp.org + +Some servers are national. They can be found as ISO 639 code with .pool.ntp.org +suffix. + +Under Debian +============ + +Install ``ntpdate`` package:: + + $ sudo apt-get install ntpdate + +and sync date with some NTP server:: + + # sudo ntpdate 0.debian.pool.ntp.org + +Under Windows +============= + +See: + + http://support.microsoft.com/kb/q216734/ + Windows Time Service Tools and Settings. + http://support.microsoft.com/kb/q223184/ + How to configure an authoritative time server in Windows 2000. + http://support.microsoft.com/kb/307897/ + How to synchronize the time with the Windows Time service in Windows XP. + http://support.microsoft.com/kb/216734/ + How to configure an authoritative time server in Windows 2000. + diff -r 123f59618e87 -r 870693ce6ff0 power-management.rst --- a/power-management.rst Mon Feb 22 13:34:05 2016 +0200 +++ b/power-management.rst Mon Feb 22 13:34:55 2016 +0200 @@ -4,6 +4,8 @@ ================== Power management ================== +.. contents:: + :local: * ACPI power states. diff -r 123f59618e87 -r 870693ce6ff0 proxy.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/proxy.rst Mon Feb 22 13:34:55 2016 +0200 @@ -0,0 +1,18 @@ +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst + +============ + HTTP proxy +============ +.. contents:: + :local: + +Environment variable +==================== +:: + + http_proxy="delegate proxy IP":"delegate proxy port" + use_proxy=1 + http_proxy_auth="proxy user name":"proxy user password" + use_proxy_auth=1 + diff -r 123f59618e87 -r 870693ce6ff0 samba.rst --- a/samba.rst Mon Feb 22 13:34:05 2016 +0200 +++ b/samba.rst Mon Feb 22 13:34:55 2016 +0200 @@ -1,4 +1,4 @@ -.. -*- coding: utf-8 -*- +.. -*- coding: utf-8; -*- .. include:: HEADER.rst ======== diff -r 123f59618e87 -r 870693ce6ff0 search.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/search.rst Mon Feb 22 13:34:55 2016 +0200 @@ -0,0 +1,16 @@ +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst + +================ + Search engines +================ +.. contents:: + :local: + +List of search engines +====================== + + http://en.wikipedia.org/wiki/Lucene + http://en.wikipedia.org/wiki/Xapian + http://en.wikipedia.org/wiki/Sphinx_%28search_engine%29 + diff -r 123f59618e87 -r 870693ce6ff0 security.rst --- a/security.rst Mon Feb 22 13:34:05 2016 +0200 +++ b/security.rst Mon Feb 22 13:34:55 2016 +0200 @@ -1,4 +1,4 @@ -.. -*- coding: utf-8 -*- +.. -*- coding: utf-8; -*- .. include:: HEADER.rst =========== diff -r 123f59618e87 -r 870693ce6ff0 virus.rst --- a/virus.rst Mon Feb 22 13:34:05 2016 +0200 +++ b/virus.rst Mon Feb 22 13:34:55 2016 +0200 @@ -1,8 +1,11 @@ -.. -*- coding: utf-8 -*- +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst ================================= Computer viruses and rootckits. ================================= +.. contents:: + :local: Online virus scaner. ==================== diff -r 123f59618e87 -r 870693ce6ff0 web-semantic.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/web-semantic.rst Mon Feb 22 13:34:55 2016 +0200 @@ -0,0 +1,24 @@ +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst + +============== + Semantic WEB +============== +.. contents:: + :local: + +About +===== + + http://www4.wiwiss.fu-berlin.de/bizer/toolkits/index.htm + Developers Guide to Semantic Web Toolkits for different Programming Languages + +Sesame +====== + +Sesame is an open source framework for storage, inferencing and querying of +RDF data. + + http://www.openrdf.org/ + Home page. + diff -r 123f59618e87 -r 870693ce6ff0 windows-hotkey.rst --- a/windows-hotkey.rst Mon Feb 22 13:34:05 2016 +0200 +++ b/windows-hotkey.rst Mon Feb 22 13:34:55 2016 +0200 @@ -1,9 +1,14 @@ .. -*- coding: utf-8; -*- .. include:: HEADER.rst -* Список используемых в Windows XP сочетаний клавиш. +================= + Windows hotkeys +================= +.. contents:: + :local: -** Основные сочетания клавиш. +Основные сочетания клавиш +========================= * CTRL+C: копирование * CTRL+X: вырезание @@ -45,7 +50,8 @@ * SHIFT при загрузке компакт-диска в привод для компакт-дисков: предотвращение автоматического воспроизведения компакт-диска * CTRL+SHIFT+ESC: вызов диспетчера задач -** Сочетания клавиш для диалоговых окон. +Сочетания клавиш для диалоговых окон +==================================== При нажатии клавиш SHIFT+F8 в окнах списков связного выбора включается режим связного выбора. В этом режиме можно использовать клавиши со стрелками, чтобы @@ -68,7 +74,8 @@ если папка выбрана в диалоговом окне Сохранение документа или Открытие документа -** Горячие клавиши стандартной клавиатуры Microsoft Keyboard. +Горячие клавиши стандартной клавиатуры Microsoft Keyboard +========================================================= * Эмблема Windows: открывает или закрывает меню «Пуск» * Эмблема Windows+BREAK: вызов диалогового окна Свойства системы @@ -83,7 +90,8 @@ * Эмблема Windows+R: вызов диалогового окна Запуск программы * Эмблема Windows+U: вызов диспетчера служебных программ -** Сочетания клавиш специальных возможностей. +Сочетания клавиш специальных возможностей +========================================= * Удерживание правого SHIFT 8 секунд: включение и отключение фильтрации ввода * Левый ALT+левый SHIFT+PRINT SCREEN: включение и отключение высокой контрастности @@ -92,7 +100,8 @@ * Удерживание клавиши NUM LOCK 5 секунд: включение и отключение озвучивания переключения * Эмблема Windows+U: вызов диспетчера служебных программ -** Сочетания клавиш в обозревателе Windows Explorer. +Сочетания клавиш в обозревателе Windows Explorer +================================================ * Клавиша END: переход вниз активного окна * Клавиша HOME: переход вверх активного окна @@ -102,7 +111,8 @@ * СТРЕЛКА ВЛЕВО: сворачивание выбранного объекта, если развернут, или выбор родительской папки * СТРЕЛКА ВПРАВО: отображение выбранного объекта, если свернут, или выбор первой вложенной папки -** Сочетания клавиш для таблицы символов. +Сочетания клавиш для таблицы символов +===================================== Дважды щелкнув символ на сетке знаков, можно перемещаться по сетке, используя сочетания клавиш: @@ -119,7 +129,8 @@ * CTRL+END: переход к последнему символу * Клавиша ПРОБЕЛ: переключение режимов увеличения и обычного представления выбранного символа -** Сочетания клавиш для главного окна консоли управления (MMC). +Сочетания клавиш для главного окна консоли управления (MMC) +=========================================================== * CTRL+O: открывает сохраненную консоль * CTRL+N: открывает новую консоль @@ -134,7 +145,8 @@ * ALT+F: вызов меню «Файл» * ALT+O: вызов меню «Избранное» -** Сочетания клавиш окна консоли управления (MMC). +Сочетания клавиш окна консоли управления (MMC) +============================================== * CTRL+P: печать текущей страницы или активной области * ALT+знак «минус»: вызов меню «Окно» активного окна консоли @@ -147,7 +159,8 @@ * Клавиша F2: переименование выбранного объекта * CTRL+F4: закрытие активного окна консоли; если консоль содержит только одно окно, данное сочетание клавиш закрывает консоль -** Подключение к удаленному рабочему столу. +Подключение к удаленному рабочему столу +======================================= * CTRL+ALT+END: открытие диалогового окна Безопасность Microsoft Windows NT * ALT+PAGE UP: переключение между программами слева направо @@ -163,7 +176,8 @@ области в буфер обмена на сервере терминалов (действие, аналогичное нажатию клавиши PRINT SCREEN на локальном компьютере) -** Навигация в обозревателе Microsoft Internet Explorer. +Навигация в обозревателе Microsoft Internet Explorer +==================================================== * CTRL+B: открывает диалоговое окно Упорядочить избранное * CTRL+E: открывает панель «Поиск» @@ -176,3 +190,4 @@ * CTRL+P: открывает диалоговое окно Печать * CTRL+R: обновление текущей веб-страницы * CTRL+W: закрытие текущего окна +