text:
Georgia Water/Laws/Erosion and Sedimentation Act

Erosion and Sedimentation Act of 1975 O.C.G.A. 12-7-1. text and Code sections

Summary of the Act
"This Georgia law regulates land-disturbing activity, which is defined as "any activity which may result in soil erosion from water or wind and the movement of sediments into state water or onto lands within the state, including, but not limited to, clearing, dredging, grading, excavating, transporting, and filling of land but not including agricultural practices as described in paragraph (5) of Code Section 12-7-17." A number of activities are exempted from regulation under this act, including: Partial exemptions apply to
 * surface mining and granite quarrying (they are covered under other laws);
 * minor activities (home gardens, landscaping, etc.);
 * agricultural operations;
 * projects conducted under NRCS supervision;
 * DOT projects; and
 * public water system reservoirs.
 * forestry land management practices,
 * activities of utility companies,
 * state road and tollway authorities, and
 * any projects involving less than one acre of disturbed area.

The Department of Natural Resources' Environmental Protection Division (EPD) is responsible for enforcing the law. EPD may delegate duties to local issuing authorities. In order to be certified as a local issuing authority, a local government must have local ordinances for land disturbing activities, the ability to enforce such ordinances, and qualified personnel to monitor and enforce permits.

Applicants for land disturbing permits must demonstrate that they have erosion and sedimentation control plans that meet |Best Management Practices established for the particular application.

The law also mandates stream buffer protection; for most streams, a 25 foot buffer is required, but for trout streams a 50 foot buffer must be maintained. An exemption to this buffer requirement was added to allow stream crossing for water and sewer lines, however there are specific guidelines to be followed in order to protect these streams." ,

Act Amendments in 2003
In 2003, the Act was amended by HB 285, which requires a mandatory certification program for individuals involved in land disturbing activities
 * 12-7-19(a). After December 31, 2006, all persons involved in land development design, review, permitting, construction, monitoring, or inspection or any land-disturbing activity shall meet the education and training certification requirements
 * 12-7-20. Creates a Stakeholder Advisory Board to oversee the education and training program.
 * 12-7-21(a). Creates a study panel to recommend erosion controls and turbidity standards, by July 2006.
 * 12-7-22. Calls for an electronic filing and reporting system.
 * 12-5-23(5)(B). Sets up a fee system ($80 per acre land disturbed) administered by Georgia EPD.

Legislative history
The completion report of the Dirt II panel includes a detailed timeline of events related to the Georgia program.

Effectiveness of the Act
The Georgia Department of Audits and Accounts conducted a performance audit of the state's erosion and control program in 2001, with a follow-up review in 2004.

State documents

 * 1) Appendix G. Laws and regulations affecting wildlife in Georgia Acknowledgment that first draft of section (here) on "Summary of the Act" was quoted from this Appendix G.
 * 2) Repairing the Chattahoochee - The Dirt II Technical Panel Completion Report, A Summary of the Work, Findings, Recommendations,and History of the Erosion and Sedimentation Control Technical Study Committee, published by the Chattahoochee-Flint Regional Development Center, Franklin, Georgia, July 2001.
 * 3) Erosion Prevention and Sediment Control in Georgia - A Development Guide to Risk Management and Cost Control, 1993, by the Dirt II Technical Panel.
 * 4) “Performance Audit - Erosion and Sediment Control Program, DNR Environmental Protection Division and State Soil and Water Conservation Commission, September 2001,” by Performance Audit Operations Division, Georgia Department of Audits and Accounts.
 * 5) "Follow-Up Review - Erosion and Sedimentation Control Program, DNR: Environmental Protection Division and State Soil and Water Conservation Commission," Performance Audit and Operations Division, Georgia Department of Audits and Accounts, November 2004, Report 04-23.
 * 6) Georgia Department of Natural Resources, Environmental Protection Division, “Authorization to Discharge Under the National Pollutant Discharge Elimination System Storm Water Discharges Associated with Construction Activities,” signed June 12, 2000, effective August 1, 2000 through July 31, 2003. (This has been superseded by the newer 2003 permit, Georgia Stormwater General Permit for Construction Activities.)
 * 7) Rules of Georgia Department of Natural Resources, Chapter 391-3-7, Erosion and sediment control.

Best management practices

 * 1) Demonstration Sites of Best Management Practices: A Manual for the Upper Etowah River Alliance, Fall 2001, Michael Bien, Jehan El-Jourbagy, Liv LiaBraaten, Shana Udvardy. River Basin Center, University of Georgia. (Demonstrating the use of BMPs to control stormwater runoff and erosion at two sites in the Etowah watershed.)
 * 2) James E. Kundell and Todd C. Rasmussen, Erosion and Sedimentation: Scientific and Regulatory Issues (Atlanta, GA: Georgia Board of Natural Resources, 1995).

Riparian buffers

 * 1) Georgia's Trout Stream Buffer Program Assessment Under the Georgia Erosion and Sedimentation Act and Georgia Water Quality Control Act, by Terry A. DeMeo, Don R. Christy, and James E. Kundell, Carl Vinson Institute of Government - University of Georgia, Athens GA, 2005. (Funded by Georgia EPD)
 * 2) "Implications of Changes in Riparian Buffer Protection for Georgia's Trout Streams, Institute of Ecology, The University of Georgia, Athens GA, 2005. (Funded by Georgia EPD, compared the potential effectiveness of 100-foot versus 50-foot buffers in providing healthy conditions for trout.)
 * 3) Guidebook for Developing Local Riparian Buffer Ordinances, 2000, by Seth Wenger and Laurie Fowler, River Basin Center, University of Georgia.
 * 4) Habitat Conservation Plan for the Upper Etowah River Watershed: Road Crossings - Effects and Recommendations, Fall 2001, Audrey Baggett, Erica Chiao, Tracey Harton. River Basin Center, University of Georgia. (Recommendations for bridge and culvert design to protect aquatic habitat in the Upper Etowah watershed; part of a watershed-wide Habitat Conservation Plan being developed for darters and other aquatic life.)
 * 5) 2001 Progress Report: Trout Stream Buffer Study, December 2001, James E. Kundell, Judy L. Meyer, Elizabeth A. Kramer, C. Rhett Jackson, Geoffrey C. Poole, Krista L. Jones, B. Lane Rivenbark, Laura E. England, Mark C. Scott, William Bumback. River Basin Center, University of Georgia.
 * 6) 2002 Progress Report: Trout Stream Buffer Study, June 2002, James E. Kundell, Judy L. Meyer, Elizabeth A. Kramer, C. Rhett Jackson, Geoffrey C. Poole, Krista L. Jones, B. Lane Rivenbark, William Bumback. River Basin Center, University of Georgia.
 * 7) Protecting Stream and River Corridors: Creating Effective Local Riparian Buffer Ordinances, 2000, Seth Wenger and Laurie Fowler, River Basin Center, University of Georgia.
 * 8) A Review of the Literature on Riparian Buffer Width, Extent and Vegetation, 1999, Seth Wenger, River Basin Center, University of Georgia.


text:
User talk:80.212.110.4

Welcome to Wikibooks, collection of open-content textbooks! You don't have to log in to read or edit articles on Wikibooks, but creating an account is quick, free and non-intrusive, requires no personal information, and gives you many benefits, including:
 * The use of a username of your choice
 * The ability to view all your contributions via a "My contributions" link
 * Your own user page
 * Your own talk page which, if you choose, also allows users to send you messages without knowing your e-mail address
 * The use of your own personal watchlist to which you can add articles that interest you
 * The ability to rename pages
 * The ability to upload images
 * The ability to customize the appearance and behavior of the website
 * The eligibility to become an administrator
 * The right to be heard in votes and elections
 * Your IP address will no longer be visible to other users.

We hope that you choose to become a Wikibooks and create an account. We hope you enjoy your time here on Wikibooks as a Wikibookian! -- LV (Dark Mark) 16:00, 14 December 2005 (UTC)

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: User talk:80.212.110.4


text:
Talk:Rhetoric and Composition/Citation

My name is Seth and I would like to work on the citation portion of this wikibook. In particular I would like to look at the MLA portion and bring it up to date with the newest edition of the MLA manual to make sure that everything is current with it. Snaslund88 2-7-2017

Should we include the website www.easybib.com? I find it very helpful when I am writing a paper. --BethH 16:16, 16 November 2007 (UTC)

I was comfortable doing the MLA portion of in-text citations and works cited example, but I am unfamiliar working with APA. Does anyone want to take it? ShellyT-P 14Dec2005 fgfhghghgfh

As a composition instructor, I have come across this as a potentially good OER source to use. I have noticed some outdated examples and information in the MLA section, specifically for MLA 8. I would like to make changes to that aspect of the book and update it for current use. --Aaron Grimes, 25 April 2019

I updated the MLA section to accurately reflect MLA 8 changes. --Aaron Grimes, 2 May 2019

APA Citation
Hello, my name is Mariel and I'd like to work on everything APA under citing sources. In addition, if allowed, I'd like to add an APA subsection under Citing Outside Sources in a Bibliography. Thanks!

title: Talk:Rhetoric and Composition/Citation


text:
Georgia Water/Policy/Georgia Game and Fish Code

Chapter 2. Water Policy
 * 2.3. Georgia Water Law

Game and Fish Code (O.C.G.A. 27-1-1)

Summary of the Act
"This legislation provides the ownership of, jurisdiction over, and control of all wildlife to be vested in the State of Georgia. The section declares that custody of all wildlife in the State is vested with the Georgia Department of Natural Resources for management and regulation.

The Wildlife Resources Division is the principal State agency vested with statutory authority for the protection, management and conservation of terrestrial wildlife and fresh water wildlife resources, including fish, game, nongame, and endangered species. All licensing of recreational and commercial fish and wildlife activities, excluding shellfish, is performed by the Wildlife Resources Division.

The Coastal Resources Division issues shellfish permits, regulates marine fisheries activities including the opening and closing of the commercial shrimp harvesting season, areas of shrimp harvest, regulates marine species size and creel limits, and enforces the National Shellfish Sanitation Program.

The Commissioner of the Department of Natural Resources has directed that there will be cooperation and coordination between the Divisions of the Department in the administration of their respective responsibilities."


text:
User talk:62.77.225.242

Please stop. If you continue to use Wikibooks for advertising, you will be temporarily blocked from editing.

title: User talk:62.77.225.242


text:
Georgia Water/Policy/Georgia Coastal Management Act

'''Chapter 2. Water Policy'''
 * 2.3. Georgia Water Laws

Georgia Coastal Management Act (O.C.G.A. 12-5-320)

Summary of the Act
"The Coastal Management Act provides enabling authority for the State to prepare and administer a coastal management program. The Act does not establish new regulations or laws; it is designed to establish procedural requirements for the Department of Natural Resources to develop and implement a program for the sustainable development and protection of coastal resources. It establishes the Department of Natural Resources as the State agency to receive and disburse federal grant monies. It establishes the Governor as the approving authority of the program and as the person that must submit the program to the federal government for approval under the federal Coastal Zone Management Act.  It requires other State agencies to cooperate with the Coastal Resources Division when exercising their activities within the coastal area."


text:
User:Nplus~enwikibooks

I'm a user of:
 * Bulgarian version of wikipedia
 * English version of wikipedia

If you want to translate something from Bulgarian you can ask me.

Здрасти,

Би ли гласувала за Българската уикикнига също и на Collaboration of the Month/January 2006 voting тъй като са я преместили там. Благодаря ти. --Vanka5 19:29, 29 December 2005 (UTC)

title: User:Nplus~enwikibooks


text:
User talk:Pooop~enwikibooks

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Pooop. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Pooop~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:37, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 05:23, 19 April 2015 (UTC)

title: User talk:Pooop~enwikibooks


text:
User talk:82.163.198.238

Vandalizing books is not helpful to the wikibooks project. Useful contributions are welcome. Jonathan888 17:25, 14 December 2005 (UTC)

title: User talk:82.163.198.238


text:
User talk:70.32.206.42

Welcome to Wikibooks, collection of open-content textbooks! You don't have to log in to read or edit articles on Wikibooks, but creating an account is quick, free and non-intrusive, requires no personal information, and gives you many benefits, including:
 * The use of a username of your choice
 * The ability to view all your contributions via a "My contributions" link
 * Your own user page
 * Your own talk page which, if you choose, also allows users to send you messages without knowing your e-mail address
 * The use of your own personal watchlist to which you can add articles that interest you
 * The ability to rename pages
 * The ability to upload images
 * The ability to customize the appearance and behavior of the website
 * The eligibility to become an administrator
 * The right to be heard in votes and elections
 * Your IP address will no longer be visible to other users.

We hope that you choose to become a Wikibooks and create an account. We hope you enjoy your time here on Wikibooks as a Wikibookian! -- LV (Dark Mark) 17:32, 14 December 2005 (UTC)

title: User talk:70.32.206.42


text:
Jakarta EE Programming/Jakarta Server Pages Syntax

The JavaServer Pages is a technology for inserting dynamic content into an HTML or XML page using a Java servlet container. In other word, instead of sending HTML pages to web clients that are always the same for every one, you can send HTML pages that can be different for each client and each time they receive it (using database data for instance). To explain it, let's have a simple HTML page on a web server. The data flow is simple. To put it simply, the client requests a HTML page by sending the page URL and the server returns the given HTML page:

Here are the HTML file and the display on the client:

The returned page is always the same. Now we want to display the current time. To do so, we add a servlet container to the web server. The HTML page will no longer exist on the server. When the page will be requested by a client, a Java class will generate the HTML page and the HTML page will be sent to the client. This Java class is called a servlet:

Here are the Java class, the generated HTML file and the display on the client:

Now the page is dynamic but the servlet is hard to code and to read. So we will use a JavaServer Page (JSP). A JSP is written like a HTML page. It has the file extension  for HTML page and the file extension   for an XML markup page. In addition to the HTML syntax, it has embedded scriptlets and jsp tags. A scriptlet is a portion of Java code. The servlet container generates a servlet from the JSP and the servlet will be used to generate HTML pages or XML content. The HTML markups will remains as it is. The embedded scriptlets are inserted into the code of the servlet. The jsp tags are transformed into Java code. So let's use a JSP:

Actually, the servlet is generated by the JSP only for the first request call. The same servlet is reused after then. It is generated again when the JSP will change. Now we have a JSP, that generates a servlet, that generates a HTML page, that will be displayed to the client:

Scripting elements
There are three basic kinds of scripting elements that allow java code to be inserted directly into the JSP. <%! int serverInstanceVariable = 1; %> Declaration tags also allow methods to be defined. <%!   /**     * Converts the Object into a string or if     * the Object is null, it returns the empty string. */   public String toStringOrBlank(Object obj) { if (obj != null) { return obj.toString; }       return ""; } %> <% int localStackBasedVariable = 1; out.println(localStackBasedVariable); %> <%= "expanded inline data " + 1 %> <%-- This is my first JSP. --%>
 * A declaration tag places a variable definition inside the body of the java servlet class. Static data members may be defined as well. Also inner classes can be defined here.
 * A scriptlet tag places all of the statements contained within it, inside the  method of the java servlet class.
 * An expression tag places an expression to be evaluated inside the java servlet class. Expressions should not be terminated with a semi-colon.
 * A comment tag does nothing. It is ignored. It lets you document the file. It is different from a HTML comment as a HTML comment will appear in the generated HTML file.

Directives
JSP directives are added at the top of a JSP page. These directives control how the JSP compiler generates the servlet. The following directives are available:

<%@ include file="somefile.jspf" %>
 * include : The include directive informs the JSP compiler to include a complete file into the current file. It is as if the contents of the included file were pasted directly into the original file. This functionality is similar to the one provided by the C preprocessor. Included files generally have the extension "jspf" (for JSP Fragment):

 * page : The page directive has several attributes:

<%@ page import="java.util.*" %> <%-- example import --%> <%@ page contentType="text/html" %> <%-- example contentType --%> <%@ page isErrorPage="false" %> <%-- example for non error page --%> <%@ page isThreadSafe="true" %> <%-- example for a thread safe JSP --%> <%@ page session="true" %> <%-- example for using session binding --%> <%@ page autoFlush="true" %> <%-- example for setting autoFlush --%> <%@ page buffer="20kb" %> <%-- example for setting Buffer Size --%>
 * Note: Only the "import" page directive can be used multiple times in the same JSP.

<%@ taglib prefix="myprefix" uri="taglib/mytag.tld" %>
 * taglib : The taglib directive indicates that a JSP tag library is to be used. The directive requires a prefix (much like a namespace in C++) and the URI for the tag library description.

Example
Regardless of whether the JSP compiler generates Java source code for a servlet or emits the byte code directly, it is helpful to understand how the JSP compiler transforms the page into a Java servlet. For example, consider the following input JSP and its resulting generated Java Servlet.

Implicit objects
We have seen that we can declare objects in a scriplet that we can use further. There are also already declared objects that can be used by the programmer. They are called implicit object:

JSP actions
JSP actions are XML tags that invoke built-in web server functionality. They are executed at runtime. Some are standard and some are custom (which are developed by Java developers). The following are the standard ones.

jsp:include
Like the include directive, this tag includes a specified jsp into the returned HTML page but it works differently. The Java servlet temporarily hands the request and response off to the specified JavaServer Page. Control will then return to the current JSP, once the other JSP has finished. Using this, JSP code will be shared between multiple other JSPs, rather than duplicated.

jsp:param
Can be used inside a,   or   block. Specifies a parameter that will be added to the request's current parameters.

jsp:forward
Used to hand off the request and response to another JSP or servlet. Control will never return to the current JSP. In this forwarding example, the request is forwarded to.

jsp:plugin
Older versions of Netscape Navigator and Internet Explorer used different tags to embed an applet. This action generates the browser specific tag needed to include an applet. The plugin example illustrates an HTML uniform way of embedding applets in a web page. Before the advent of the  tag, there was no common way of embedding applets. Currently, the  tag does not allow for dynamically called applets. For example,  cannot be used with a charting applet that requires the data points to be passed in as parameters unless the number of data points is constant. You cannot, for example, loop through a ResultSet to create the  tags. Each  tag must be hand-coded.

jsp:fallback
The content to show if the browser does not support applets.

jsp:getProperty
Gets a property from the specified JavaBean.

JSP tag libraries
In addition to the pre-defined JSP actions, developers may add their own custom actions using the JSP Tag Extension API. Developers write a Java class that implements one of the Tag interfaces and provide a tag library XML description file that specifies the tags and the java classes that implement the tags.

Consider the following JSP.

<%@ taglib uri="mytaglib.tld" prefix="myprefix" %> …  <%-- The start tag --%> …  <%-- The end tag --%> …

The JSP compiler will load the mytaglib.tld XML file:

The JSP compiler will see that the tag  is implemented by the java class  : The first time the tag is used in the file, it will create an instance of. Then (and each additional time that the tag is used), it will invoke the method  when it encounters the starting tag. It looks at the result of the start tag, and determines how to process the body of the tag. The body is the text between the start tag and the end tag. The  method may return one of the following:

Note: If tag extends the  class, the method   will be called when the body has been processed just prior to calling the. This method is used to implement looping constructs.

When it encounters the end tag, it invokes the  method. The method may return one of two values:

If you want to iterate the body a few times, your java class (tag handler) must implement the  interface. It returns  — which means to invoke the body again.

JSP Standard Tag Library (JSTL)
The JavaServer Pages Standard Tag Library (JSTL) is a component of the Java EE Web application development platform. It extends the JSP specification by adding a tag library of JSP tags for common tasks, such as XML data processing, conditional execution, loops and internationalization.

Struts Tag Library
The Struts project includes the Struts Tag Library, the bulk of which is useful independently of the Struts architecture.

Internationalization
Internationalization in JSP is accomplished the same way as in a normal Java application, that is by using resource bundles.

Expression Language
The Expression Language (EL) is a faster/easier way to display parameter values. It is available since JSP 2.0. For instance, it allows developers to create Velocity-style templates: Same as

It also offers a clearer way to navigate nested beans. Consider some beans:

Then, if an instance of Person was to be placed onto a request attribute under the name "person", the JSP would have:

Same as.

JSP Technology in the Java EE 5 Platform
The focus of Java EE 5 has been ease of development by making use of Java language annotations that were introduced by J2SE 5.0. JSP 2.1 supports this goal by defining annotations for dependency injection on JSP tag handlers and context listeners.

Another key concern of the Java EE 5 specification has been the alignment of its webtier technologies, namely JavaServer Pages (JSP), JavaServer Faces (JSF), and JavaServer Pages Standard Tag Library (JSTL).

The outcome of this alignment effort has been the Unified Expression Language (EL), which integrates the expression languages defined by JSP 2.0 and JSF 1.1.

The main key additions to the Unified EL that came out of the alignment work have been: A pluggable API for resolving variable references into Java objects and for resolving the properties applied to these Java objects, Support for deferred expressions, which may be evaluated by a tag handler when needed, unlike their regular expression counterparts, which get evaluated immediately when a page is executed and rendered, and Support for lvalue expression, which appear on the left hand side of an assignment operation. When used as an lvalue, an EL expression represents a reference to a data structure, for example: a JavaBeans property, that is assigned some user input. The Unified EL is defined in its own specification document, which is delivered along with the JSP 2.1 specification.

Thanks to the Unified EL, JSTL tags, such as the JSTL iteration tags, can be used with JSF components in an intuitive way.

JSP 2.1 leverages the Servlet 2.5 specification for its web semantics.

Model-view-controller paradigm
A model-view-controller pattern can be used with the JSP files in order to split the presentation from request processing and computer data storage. Either regular servlets or separate JSP files are used to process the request. After the request processing has finished, control is passed to a JSP used only for creating the output. There are several platforms based on Model-view-controller pattern for web tiers (such as Barracuda, Apache Struts, Stripes, and the Spring MVC framework).

Environment
Both the Java Server (J2EE specification) and the page scripts and/or extended customised programming added operate by (in the runtime context of being loaded programs used) a special pre-installed base program called a Virtual Machine that integrates with the host Operating System, this type being the Java Virtual Machine (JVM).

Because either, both a Compiler-JVM set (called an SDK or JDK) or the lone JVM (called a JRE, Java Runtime Environment) is made for most computer platform OSs and the compiled programs for the JVM are compiled into special Java Byte code files for the JVM the Byte-code files (compiled Java program .class files) can be effectively transferred between platforms with no requirement to be recompiled excepting versioning compatibility, or special circumstance. The source code for these J2EE servlet or J2EE JSP programs is almost always supplied with J2EE JSP material and J2EE Web Applications because the server must call the compiler when loading them. These small extension programs (custom tags, servlets, beans, page scripting) are variable and likely to be updated or changed either shortly before runtime or intermittently but particularly when sending JSP page requests themselves,  it requires the JSP server to have access to a Java compiler (SDK or JDK) and the required source code (not simply the JVM JRE and byte code class files) to successfully exploit the method of serving.

JSP syntax has two basic forms, scriptlet and markup though fundamentally the page is either HTML or XML markup. Scriptlet tagging (called Scriptlet Elements) (delimited) blocks of code with the markup are not effectively markup and allows any java server relevant API (e.g. the servers running binaries themselves or database connections API or java mail API) or more specialist JSP API language code to be embedded in an HTML or XML page provided the correct declarations in the JSP file and file extension of the page are used. Scriptlet blocks do not require to be completed in the block itself only the last line of the block itself being completed syntactically correctly as a statement is required, it can be completed in a later block. This system of split inline coding sections is called step over scripting because it can wrap around the static markup by stepping over it. At runtime (during a client request) the code is compiled and evaluated, but compilation of the code generally only occurs when a change to the code of the file occurs. The JSP syntax adds additional XML-like tags, called JSP actions, to be used to invoke built-in functionality. Additionally, the technology allows for the creation of JSP tag libraries that act as extensions to the standard HTML or XML tags. JVM operated Tag libraries provide a platform independent way of extending the capabilities of a Web server. Note that not all company makes of Java servers are J2EE specification compliant.

Programmation JEE/JSP Programmeren in Java/JSP


text:
Ecology/Main Glossary

<<< << Chapter 1 | Glossary 1 |

A Glossary of Terms Related to Basic Ecology

Biological control or biocontrol: 1. In general, the control of the numbers of one organism as a result of natural predation by another or others. Specifically, the human use of natural predators for the control of pests or weeds. Also applied to the introduction of large numbers of sterilized males of the pest species, whose matings result in the laying of infertile eggs (Allaby, 1998). 2. The release of one species to control another (Carlton, 2001). 3. The management of weeds using introduced herbivores (often insects) as biological control agents (Booth et al., 2003). 4. Control method involving a biological control agent that is a natural enemy of a target pest (Heutte and Bella, 2003).

Biological diversity or biodiversity: Used to describe species richness, ecosystem complexity, and genetic variation (Allaby 1998).

Bioregion: A biological subdivision of the earth’s surface delineated by the flora and fauna of the region (Allaby 1998).

Biota: The plants and animals of a specific region or period, or the total aggregation of organisms in the biosphere (Allaby 1998). Community: Any grouping of populations of different organisms that live together in a particular environment (Allaby 1998).

Disturbance: An event or change in the environment that alters the composition and successional status of a biological community and may deflect succession onto a new trajectory, such as a forest fire or hurricane, glaciation, agriculture, and urbanization (Art 1993).

Ecosystem: A discrete unit, or community of organisms and their physical environment (living and non-living parts), that interact to form a stable system (Allaby 1998).

Endemic: A species or taxonomic group that is restricted to a particular geographic areas because of such factors as isolation or response to soil or climatic conditions; this species is said to be endemic to the place (Allaby 1998) and would be native.

Exotic species: This term is commonly used in publications and literature, and is similar to the terms alien species, foreign species, introduced species, non indigenous species, and non native species (Heutte and Bella 2003). Other definitions include: 1. An introduced, non native species, or a species that is the result of direct or indirect, deliberate or accidental introduction of the species by humans, and for which introduction permitted the species to cross a natural barrier to dispersal (Noss and Cooperrider 1994). 2. In North America, often refers to those species not present in a bioregion before the entry of Europeans in the 16th century, or present in later parts of that region and later introduced to an ecosystem by human-mediated mechanisms (Cohen and Carlton 1988).

Fauna: The animal life of a region or geological period (Allaby 1998)

Fitness: Survival and reproduction ability of an individual

Flora: Plant or bacterial life forms of a region or geological period (Allaby 1998).

Habitat: 1. The place, including physical and biotic conditions, where a plant or an animal usually occurs (Allaby 1998). 2. The physical conditions that surround a species, or species population, or assemblage of species, or community (Clements and Shelford, 1939).

Indigenous: A species that occurs naturally in an area; a synonym for native species (Allaby 1998), although see "endemic".

Native range: The ecosystem that a species inhabits (Booth et al. 2003).

Native species: 1. A synonym for indigenous species 2. A species that occurs naturally in an area, and has not been introduced by humans either intentionally or unintentionally (Allaby 2005). 3. In North America, a species established before the year 500 (Jeschke and Strayer 2005)

Naturalized species: 1. A species that was originally introduced from a different country, a different bioregion, or a different geographical area, but now behaves like a native species in that it maintains itself without further human intervention and now grows and reproduces in native communities (Allaby 1998). 2. A non native species that forms self-sustaining populations but is not necessarily an invasive species (Booth et al. 2003).

Niche: the role the species plays in the functioning of the ecosystem: the "functional status of an organism in its community" (Charles Elton, in Odum, 1959).

Population: A group of potentially inter-breeding individuals of the same species found in the same place at the same time (Booth et al. 2003).

Ruderal species: A plant associated with human dwellings, construction, or agriculture, that usually colonizes disturbed or waste ground. Ruderals are often weeds which have high demands for nutrients and are intolerant of competition. See also native weed or invasive native (Allaby 1998).

Species:  A group of organisms formally recognized as distinct from other groups; the taxon rank in the hierarchy of biological classification below that of genus; the basic unit of biological classification, usually defined by the reproductive isolation of the group from all other groups of organisms (Allaby 1998).

Weed: 1. A plant in the wrong place, being one that occurs opportunistically on land or in water that has been disturbed by human activities (see also ruderal species and native weed or invasive native), or on cultivated land, where it competes for nutrients, water, sunlight, or other resources with cultivated plants such as food crops. Under different circumstances the weed plant itself may be cultivated for beneficial purposes (Allaby, 1998). 2. A native or introduced species that has a perceived negative ecological or economic effect on agricultural or natural ecosystems (Booth et al., 2003). 3. A plant growing in an area where it is not wanted (Royer and Dickinson, 1999).

title: Ecology/Main Glossary


text:
User talk:38.116.192.13

Please stop adding nonsense to Wikibooks. It is considered vandalism. If you would like to experiment, use the sandbox. Thank you. -- Herby talk thyme 14:36, 11 January 2007 (UTC)

This is your last warning. The next time you vandalize a page you will be blocked from editing Wikibooks.  -- Herby talk thyme 14:42, 11 January 2007 (UTC)

To those whom it may concern, this is the IP of a whole school system. Out of 1000-2000 people, there WILL be people who will vandalize. Just block this account. Those who DO contribute will have a registered account anyways. —The preceding unsigned comment was added by 38.116.192.13 (talk • contribs) 14:29, 12 Jan 2007 (UTC)

 * And noted -- Herby talk thyme 14:46, 12 January 2007 (UTC)

title: User talk:38.116.192.13


text: Template:X86 Assembly/X86-inst

title: Template:X86 Assembly/X86-inst


text:
Template talk:X86 Assembly/X86-inst

this is a template for the x86 Assembly wikibook. -- 19:02, 14 December 2005 (UTC)

title: Template talk:X86 Assembly/X86-inst


text: Template:X86 Assembly/X86-inst-1

title: Template:X86 Assembly/X86-inst-1


text:
Template:X86 Assembly/X86-inst-2

This template is for the x86 Assembly book. The instruction operands are in GAS format: op src, dest on the left, and Intel syntax on the right.

title: Template:X86 Assembly/X86-inst-2


text:
Arimaa/Elephant and Horse Attacks

Objectives and Risks
The Elephant and Horse Attack (commonly known as the “EH Attack” or “E+H Attack”) is a very popular system and is seen much more frequently than the Elephant and Camel Attack due to the high risks involved with the latter. The important distinction is that the attacker’s Camel remains safe during an Elephant and Horse Attack and can be used to counterbalance the defender’s Camel. In the Elephant and Camel Attack, by contrast, the defender’s Camel becomes quite powerful if the attacking Camel is taken hostage and the cost for abandoning the hostage is more severe for the attacker. The Elephant and Horse Attack is currently very effective against the best computer programs but there is not yet a consensus in the Arimaa community as to whether the E+H Attack is the best system to use against a strong human defender.

'Note: For simplicity, many examples below will assume that the Gold player is attacking the c6 trap. Naturally, the same theories can apply equally to attacks on all 4 traps.'

Reasons to use the Elephant and Horse Attack:

 * to trap enemy pieces when the enemy Elephant is too far away, or unable, to defend the trap
 * to create a wall with two strong pieces so that a Rabbit may be advanced along the outside
 * to distract the enemy Elephant from the opposite wing
 * to encourage a Horse hostage in order to decentralize the enemy Elephant
 * to encourage a Horse hostage in order to attempt an Elephant blockade
 * to encourage a Horse hostage with the intention of swarming the trap with small pieces and releasing the attacking Elephant

Summary of risks (assuming Gold attacks the c6 trap):
 * the Horse may be taken hostage
 * the Horse may be framed – this is a major disadvantage if the attacking Elephant is pinned to the c5, b6 or c7 square
 * the opposing player may be able to begin an attack on the trap just vacated by the Horse and/or Elephant

Ideal Placement of Pieces
The attacker should employ the Elephant and Horse attack against a trap that does not have a defending Camel. It is often disastrous if the Horse is taken hostage by the Camel and the attacking Elephant becomes decentralized during a rescue operation.

When attacking an enemy trap, a very effective plan is to place the Horse on b6 and the Elephant on d6. The advantages are:
 * if the enemy Elephant cannot reach c5, it is usually difficult for the defender to place a piece on c5, making it problematic to defend the trap – even if a defender can reach c5 it may still be in danger of being pushed towards the c3 trap
 * if the Horse is taken hostage it will be safe from the f6 trap
 * if the Horse is framed, the Elephant is ideally placed on d6 – it can be quite disadvantageous for the attacker if the Gold Elephant is pinned to c5, b6 or c7
 * the Horse cannot become forked on the d6 square while the Elephant is standing there!
 * the Horse is located as far as possible from the enemy Elephant and Camel while still maintaining a convenient escape route along the ‘a’ or ‘b’ file – this becomes especially important if the Gold Elephant ever moves away from the c6 trap
 * the Horse can effectively assist an advancing Rabbit on the ‘a’ file
 * if the Gold Horse occupies b6, then the Silver Horse is denied its ideal defensive square
 * the defensive position becomes highly cramped

If there is a Silver Rabbit on d8, it is usually a good idea to pull it to d7 with the Elephant:
 * it will become an obstacle for a Silver Camel that is located behind the f6 trap
 * the Rabbit may be captured after Gold controls the c6 trap
 * a Silver defender is removed from the back rank for the benefit of any advanced Gold Rabbits

The attacking Horse can also occupy the c7 square rather than the b6 square in order to capture an enemy piece on c8, just as a Camel often does during an Elephant and Camel Attack. However, this is sometimes dangerous for the attacking Horse and some players prefer to simply leave the Horse at b6. The major problem is that during an Elephant and Horse Attack on c6, the enemy Camel often lurks at a nearby square, such as f7. And that Camel would love nothing more than to hold the Horse hostage behind the c6 trap in order to either paralyze the Elephant, or lure it behind the trap. Before the Gold Horse is moved to c7, it is prudent to ensure that the Silver Elephant cannot create any threats that will distract the Gold Elephant from the c6 trap.

If the defender has many pieces near the trap, it may be necessary to advance a third attacker in order to quickly seize control of the trap. If possible, the third attacker should be a Dog, or weaker, so that the other Horse and the Camel can be used defensively.

Defensive Systems and Counter-Attacks
There are a few simple and effective prophylactic measures that the defender can use to prevent or delay the Elephant and Horse Attack. By placing defending Horses on the outside of both traps (on the ‘b’ and ‘g’ files), the enemy will need to devote some extra moves to first pull the Horse away from the square, then occupy it with the attacking Horse. The defending Elephant will usually arrive on the scene long before the attacker can accomplish his/her objectives. A second possibility is to guard the trap with both a Camel and a Horse – of course, the opposing player may simply attack the other trap in that case! A third preventative measure commonly used is to threaten an Elephant and Horse Attack on the same wing. For example, if Horses are defending traps at b3 and b6 and then Gold Elephant moves to the b5 square, the Silver Elephant can simply move to the b4 square and neither player will successfully carry out the Elephant and Horse Attack – not yet.

If the prophylactic measures fail, and the opposing player does carry out an Elephant and Horse Attack there are several defensive options:
 * occupy the c5 square with the Elephant in order to neutralize the attack
 * take the Horse hostage with the Elephant – current Arimaa theory considers this to be a dubious decision
 * use the Camel, possibly with supporting pieces, to counter-attack on the opposite wing – there is a risk involved because the Gold Elephant may decide to abandon the Horse in order to pursue the Silver Camel
 * launch an Elephant and Horse Attack on the same wing – if both armies can maintain 2 defenders on the traps then a curious, but temporary, stalemate sometimes occurs
 * launch an Elephant and Horse Attack on the opposite wing – this is much riskier than an attack on the same wing because mutual attrition followed by a Rabbit race on opposite wings becomes a distinct possibility
 * create a distraction for the Gold Elephant so that the c6 trap will be abandoned

Another tactic that the defender can use with the Silver Elephant on c5, Silver Horse on b7 and Gold Horse on b6 is to pull the attacking Horse down to b5 (returning the Elephant to c5) and then move the defending horse onto b6. From the d6 square, the Gold Elephant cannot assist the Gold Horse in returning to b6. Similarly, if there was a defending piece on c7, the Silver Elephant could pull the Gold Horse to c6 and then occupy b6 with the Silver Horse. This would force the Gold Horse to escape through the c7 square (if possible) in order to avoid being framed.

Ideas for Setup
An Elephant and Horse Attack can be commenced with the first moves of the game, and for this reason nearly all players setup either Horses or the Camel on the b2, g2, b7 and g7 squares. The Horses on these files have the dual purpose of threatening, and defending against, an Elephant and Horse Attack. A balanced distribution of forces is essential for defending against an attack; if one home trap is defended with 2 Horses and a Camel, the opposing player is likely to attack the opposite trap.

Most players like to assign their Camels in a defensive role during the opening of the game. For those players, the Camel is an ideal defender against the Elephant and Horse Attack and is often setup in the middle or behind a trap and, more importantly, the Camel’s mobility should be maintained during the game so that it can easily move from one home trap to the other. Players that do not use the Camel defensively against the Elephant and Horse Attack may setup with it located on the ‘a’, ‘b’, ‘g’ or ‘h’ file for possible offensive action.

Dogs and Cats are very often setup behind the home traps. They are very effective in those positions but they will require three supporting pieces to maintain a Horse frame on the trap. Another possibility is to setup Dogs and Cats on a2, a7, h2, or h7 for the job of unfreezing the trap defenders that are attacked by the enemy Elephant on the ‘b’ and ‘g’ files. This is sometimes preferable to advancing Rabbits for the same purpose.

At the current time, most players like to setup four Rabbits on the ‘a’ and ‘h’ files and no Rabbits on the ‘d’ and ‘e’ files. There are several ideas behind this setup related to this chapter:
 * Rabbits in the middle of the home territory may become obstacles for defensive pieces that desire to move between traps, especially on the 2nd and 3rd ranks
 * if the enemy Elephant attempts to pull a stronger piece from the 'b' or 'g' file then the 2nd rank 'a' or 'h' file Rabbit can be advanced to unfreeze the stronger piece with one fewer step than a 1st rank ‘a’ or ‘h’ file Rabbit
 * Rabbits can be advanced on the perimeter more safely than in the middle
 * outside, 2nd rank Rabbits are one step closer towards participating in an Elephant blockade on the ‘b’ file
 * Rabbits advanced up the middle of the board may be exploited by the enemy to blockade the friendly Elephant in the 6th rank middle
 * players that prefer to generate goal threats on the outside, rather than the middle of the board, like to stack extra Rabbits on the 'a' and 'h' files

Against an opponent that enjoys using the Elephant and Horse Attack, it is not recommended to place Rabbits behind a home trap on c2, f2, c7 or f7. They are awkward and vulnerable defenders against the E+H Attack.

If Both Camels Have Been Trapped
If each player traps the enemy Camel plus one Horse, the strategic situation will be identical to the one that arises after all four Horses are trapped and the Camels remain on the board (because the relative strengths and distribution of pieces are equivalent). Therefore, if each side has no Camel and one Horse, the Elephant and Horse Attack contains all of the risks that would be associated with an Elephant and Camel Attack with four pieces removed from the board. As such, both players should consider alternative strategies that do not expose the second strongest remaining piece to a hostage situation.

If Attacker’s Camel Has Been Trapped
If the attacker has already lost the Camel (hopefully some compensatory enemy piece(s) were captured), then the Elephant and Horse Attack is usually a strategic mistake. It involves all of the same risks that were discussed in the Elephant and Camel Attack chapter due to the power of the unopposed enemy Camel; only in exceptional circumstances would the attack be beneficial.

A player that has lost the Camel but gained smaller piece(s) as compensation should instead consider strategies that involve goal threats, blockades, obtaining a Camel hostage, or creating an open tactical game in which the enemy Camel cannot effectively participate.

If Defender’s Camel Has Been Trapped
If the opposing player has already lost the Camel in exchange for a couple of weaker pieces, there are differences of opinion amongst Arimaa experts about whether the side with the Camel should use the Lone Elephant Attack or the Elephant and Horse Attack. The ideal strategy can vary considerably from one situation to the next, so both players will need to rely upon judgement and experience rather than relying upon rules carved in stone.

title: Arimaa/Elephant and Horse Attacks


text:
User talk:12.222.197.19

Please stop adding nonsense to Wikibooks. It is considered vandalism. If you would like to experiment, use the sandbox. Thank you. -- LV (Dark Mark) 20:48, 14 December 2005 (UTC)

title: User talk:12.222.197.19


text:
User talk:Plotor~enwikibooks

Good luck! -- LV (Dark Mark) 21:06, 14 December 2005 (UTC)

 * Not that it really matters, but why did you alter my comments? Why did you make it appear as if I said "Good luck!"? Thanks. -- LV (Dark Mark) 22:30, 14 December 2005 (UTC)

 * Aaaaah... after reading the comment in the talk page for game manuals, I can see how there was some confusion. In case you don't see the message there, I will repeat it here. The "Good luck!" was not sarcastic. It is included in the official welcome template. I just noticed your name a lot and thought I'd welcome you to the Wikibooks community. I do not make any judgements on what you edit. I am sorry if there was any confusion. Just keep upo the good work, my friend. Cheers. -- LV (Dark Mark) 22:38, 14 December 2005 (UTC)

 * LOL, I'm sorry LV, I honestly thought that there was the standard Wikibooks welcome, and one line later you added a personal "Good luck." I didn't expect a welcome template to actually be signed by another user.  And so I thought I was erasing a lot of default text and leaving only a personal message.  Thank you for the clarification.  Now that I understand it, I'll leave it there in the spirit of good will that it was intended. 01:54, 15 December 2005 (UTC)

Just saying I've added a responce to your comment on the Wikibooks_talk:Game_manual_guidelines page. So did Lord Voldemort. --Dragontamer 22:58, 14 December 2005 (UTC)

 * Got it, thank you very much for your support. I guess I'll keep plugging away at the project while the issue is resolved.  I am trying to keep it very legitimate, and making sure that every important link is connected, as well as adding the proper references back and forth between WP and WB. Plotor 01:54, 15 December 2005 (UTC)

VFD
In response to some of your comments on WB:VFD I have copied some text from Wikipedia:
 * Assume good faith. Wikibooks has worked remarkably well so far based on a policy of nearly complete freedom to edit. People come here to collaborate and write good articles.
 * Treat others as you would have them treat you.
 * Be polite, please!
 * People can't see you or know for sure your mood. Irony isn't always obvious, and blunt, raw text can easily appear rude. Be careful of the words you choose — what you intended might not be what others think
 * Argue facts, not personalities.
 * Be civil.
 * Although it's understandably difficult in a heated argument, if the other party is not as civil as you'd like them to be, make sure to be more civil than him or her, not less.
 * That way at least you're not spiralling down to open conflict and name-calling by your own accord, you're actively doing something about it: taking a hit and refraining from hitting back -- everybody appreciates that (or at least they should).
 * However, don't hesitate to let the other party know that you're not comfortable with their tone in a neutral way -- otherwise they might think you're too dense to understand their "subtlety", and you'll involuntarily encourage them (e.g. "I know you've been sarcastic above, but I don't think that's helping us resolve the issue. However, I don't think your argument stands because...").
 * Be prepared to apologize.
 * Forgive and forget.

Thanks, Gerard Foley 01:31, 24 December 2005 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Plotor. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Plotor~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:35, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 05:22, 19 April 2015 (UTC)

title: User talk:Plotor~enwikibooks


text: User talk:24.144.134.146

title: User talk:24.144.134.146


text:
User talk:82.37.43.40

Please stop adding nonsense to Wikibooks. It is considered vandalism. If you would like to experiment, use the sandbox. Thank you.

title: User talk:82.37.43.40


text: User talk:67.128.92.3

title: User talk:67.128.92.3


text:
User:Plotor~enwikibooks

Hi. I'm me. More later.

title: User:Plotor~enwikibooks


text:
Arimaa/Elephant and Minor Piece Attacks

This chapter addresses attacks with an Elephant and Dog(s), Cat(s) and/or Rabbit(s). These types of attacks are rarely seen in the opening because the defensive setup on both sides is normally too sturdy to allow a successful attack by such weak invaders. Therefore, most of the situations covered will deal with the middlegame or endgame.
 * 1) /Objectives and Risks/
 * 2) /Ideal Placement of Pieces/
 * 3) /Defensive Systems and Counter-Attacks/
 * 4) /On a Depleted Board/
 * 5) /Burrowing with a Rabbit/
 * 6) /Illustrative Games/

title: Arimaa/Elephant and Minor Piece Attacks


text:
User talk:130.88.166.55

Welcome to Wikibooks, collection of open-content textbooks! You don't have to log in to read or edit articles on Wikibooks, but creating an account is quick, free and non-intrusive, requires no personal information, and gives you many benefits, including:
 * The use of a username of your choice
 * The ability to view all your contributions via a "My contributions" link
 * Your own user page
 * Your own talk page which, if you choose, also allows users to send you messages without knowing your e-mail address
 * The use of your own personal watchlist to which you can add articles that interest you
 * The ability to rename pages
 * The ability to upload images
 * The ability to customize the appearance and behavior of the website
 * The eligibility to become an administrator
 * The right to be heard in votes and elections
 * Your IP address will no longer be visible to other users.

We hope that you choose to become a Wikibooks and create an account. We hope you enjoy your time here on Wikibooks as a Wikibookian! -- LV (Dark Mark) 22:41, 14 December 2005 (UTC)

title: User talk:130.88.166.55


text:
Ancient History/Egypt/Pharaohs

Pharaohs
Pharaohs were kings in ancient Egypt, considered by their subjects to be divine. The word "Pharaoh" literally means "great house". This term refers to both the royal household in which the king dwelled and also the veneration and wonder the people held for the position. They were the most important people in the country of Egypt. The Pharaoh's word was never questioned as he had supreme authority, represented by the crook and flail. Many gifts were given to him in his honor. It was common for a Pharaoh to marry his sibling to "preserve the divinity within the blood line." Yet at the same time the Pharaohs had multiple wives, so the heir did not always come from the sibling-wife.

Early Dynastic

 * Years 3100-2700 B.C.
 * 1st to 2nd Dynasty

Pharaohs in the Old Kingdom

 * Khufu
 * Khafra fff
 * Menkaura
 * Shepseskaf

Pharaohs in the Middle Kingdom

 * Years 2050-1800 B.C.
 * 11th to 12th Dynasty

Pharaohs in the New Kingdom

 * Tutankamun
 * Akhenaton

Hellenistic Pharaohs

 * Alexander The Great
 * Ptolamys

Koningen aan de Nijl/Farao

title: Ancient History/Egypt/Pharaohs


text:
User talk:130.88.52.63

Welcome to Wikibooks, collection of open-content textbooks! You don't have to log in to read or edit articles on Wikibooks, but creating an account is quick, free and non-intrusive, requires no personal information, and gives you many benefits, including:
 * The use of a username of your choice
 * The ability to view all your contributions via a "My contributions" link
 * Your own user page
 * Your own talk page which, if you choose, also allows users to send you messages without knowing your e-mail address
 * The use of your own personal watchlist to which you can add articles that interest you
 * The ability to rename pages
 * The ability to upload images
 * The ability to customize the appearance and behavior of the website
 * The eligibility to become an administrator
 * The right to be heard in votes and elections
 * Your IP address will no longer be visible to other users.

We hope that you choose to become a Wikibooks and create an account. We hope you enjoy your time here on Wikibooks as a Wikibookian! -- LV (Dark Mark) 23:06, 14 December 2005 (UTC)

title: User talk:130.88.52.63


text:
User talk:67.184.106.211

Please stop adding nonsense to Wikibooks. It is considered vandalism. If you would like to experiment, use the sandbox. Thank you. -- LV (Dark Mark) 23:07, 14 December 2005 (UTC)

title: User talk:67.184.106.211


text:
Xandros

Contents

 * 1) /Installing Software/
 * 2) /Installing Codecs for Multimedia Formats/
 * 3) /Manually Adding Launch Icons/

Other Sites

 * ArchLUG.org's Xandros Kwikis
 * Desktop-Linux.Net's Xandros 2.0 Tips page
 * German-language Xandros users forum
 * DesktopOS.com Xandros Desktop forum
 * James' unofficial Xandros 1.0 HOWTO directory

title: Xandros


text:
Xandros/Installing Software

Safe Install (Xandros Networks)
The recommended way of installing new software is to use a program called Xandros Networks, an application that installs, removes and updates software. Xandros Networks can be launched from the desktop and the Launch menu.

Common Applications
From the menu on the left, select "New Applications". You will see a list of common software packages offered and tested by Xandros which are not found on your computer. To install any of these, simply click on the "Install Now" to the right of the software description.

All Available Supported Applications
Expanding the "New Applications" on the left reveals the software categories for all available supported software from Xandros Networks. Selecting a category will reveal the software packages in that category. To install one of these packages, selected the desired software package and click "Install".

Searching for Software
If you don't know the category or the name of the software you want to install, you can search for it. Enter the name or type of software you want in the text box in the top-right corner of the window and click the "Search" button.

Easy Install (Autopackage)
Autopackage is a simple way to install software on a wide variety of Linux distributions.

To install your first software from Autopackage:
 * 1) Go to the Autopackage Downloads site.
 * 2) Download the software package you want to install and save it on your computer.
 * 3) Go to the folder where you saved the software package.
 * 4) Click on the package with your right mouse button.
 * 5) Click on the Properties menu item.
 * 6) Select the Permissions tab.
 * 7) Check the top-most "Exec" checkbox.
 * 8) Click OK.
 * 9) Open the software package.

This is a one-time process. After your first package software package from Autopackage has been installed, installing further software packages is as easy as downloading the file and double-clicking it.

title: Xandros/Installing Software


text:
Xandros/Installing Codecs for Multimedia Formats

Warning: These instructions are for installing Linux software that will playback WMA-encoded media files, and the bundle noted also includes numerous codecs that are of questionable and legally uncertain status.

Xandros natively supports several multimedia formats, like the popular MP3 format, but not all of them, such as the WMA format. This guide will give you support for these other formats.

 * 1) Open Xandros Networks
 * 2) Open the Edit menu and select "Set Application Sources..."
 * 3) Click on the "Add..." button
 * 4) Add the following line exactly as it is shown:
 * 5) *deb ftp://ftp.nerim.net/debian-marillat/ sarge main
 * 6) Click the "OK" button.
 * 7) Click the "OK" button.
 * 8) By using the search function in the top-right corner, find and install a package called "w32codecs".
 * 9) And by searching for "libdvdcss", you can play encoded DVDs.


text:
User talk:64.228.142.89

Thank you so much for your contributions so far on the Maple Story guide.

May you please register though? It helps a lot in terms of tracking changes, and other stuff. Its free, easy, and has advantages :) Also, I would be able to email you without knowing your email address (supposedly, but I can't seem to figure out how to use that feature)

Again, thanks for your help so far--Dragontamer 02:13, 15 December 2005 (UTC)

title: User talk:64.228.142.89


text:
User talk:MajesticMystic

Nice to have you on board. As a note, you can sign your name with the signature feature like this and if you want to add the date, just sign like this ~. It is general convention to add a -- before your name.

Now, I will display the general welcome template. :-p

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally.

--Dragontamer 02:26, 15 December 2005 (UTC)

 * Oh, and in "forums", to reply to a post, put a : in front of your text. Anyway, I've tried to get more people onboard, but no one seems to want to help. GFAQs people just want to vandalize :-/ Sleepywood people would rather create their own guides. But I'll get what i want eventually :) When the guide is big enough, people will start joining in.

 * There has been some controversy on Game Guides on Wikibooks; however, they have seemed to revolve around the idea that Game Guides generally look like **** on Wikibooks. Look at the Starcraft Wikibook for example. Anyway, I'd like to help clean up the Maple Guide a bit, and if you don't want to, that is fine as well :) Other little things that may help... you can program new code into Wikibooks through "templates". I've programmed a few in myself, so go on and use them. If you can't figure out how to use them, all you gotta do is put a

 * I hope you help out more often as well :) Takes a bit of load off of me, and I'm sure it makes the guide better --Dragontamer 02:30, 15 December 2005 (UTC)

 * I found an edit on your mage guide dealing with your name... I'm not sure if this was by You or not, so I reverted it. Change it back with while logged in if you want to, and I'll stop reverting it.

 * Aight, cool. Remember, anyone can edit what you put up on a wiki, so some people like to screw up names and stuff. I try to keep an eye out for that kind of stuff... but it is hard to tell if it was you or someone else who wanted to screw up your name.

 * As for templates... they are kinda complex to make and use... A tutorial on one is here, in the  Editing guide. The basics are simple though... As you can see on this page, there is the  template (click the edit bar). Templates can get "parameters" to change some of their text, so realy each template is used differently. The templates I've been making are listed on the MapleStory talk page, and I've been trying to document them... still kinda hard to use/explain. --Dragontamer 12:38, 16 December 2005 (UTC)

Brace for impact on MapleStory guide
I'm going to Sleepywood to ask for help on the guide... but just as an FYI, generally 1 or 2 malicious people will come in and try to demolish the guide (if from GFAQS, about 5 of them will come :-/ ). If I'm not on for whatever reason, just know that you can go back to an old "file" in ~4 clicks.
 * 1) Click on the "history" on the top of the screen
 * 2) click on the date of the last good edit
 * 3) click on the edit button
 * 4) Click save page

This will save an old version as the "main" page, and thus, undoing whatever the other guys have done. You can go back on *any* history file. Every edit is saved as an edit, and can be undone in this way. (much much easier than combing through the article again). By clicking "last" and "current", you can see the differences between the last version, and the current version. Pretty easy stuff, but I can see where someone could get confused.

Just know, whatever they do with mouse actions and so forth, you (or anyone) can undo in 4 clicks of a button :) (plus the possibility of being banned from editing, more on that later) Admins, can do it in 1 click, and User:Derbeth generally gets the obvious vandalisms in an instant (they got a little program that scans all edits).

Of course, only do that when it is obviously a vandal. If they are posting misinformation (aka, they are n00bs who think too much of themselves) then move it into an FAQ section or something. (Like what I've done in the Bowmen Anti-Builds section. ) If you aren't sure, post it up and the admin will talk to you. They are generally nice about those kinds of things :)

In the case of trying to find who the vandal is, just click on the "last" on the history file. You will see what he edited.

If it is too much, you can ask for Admins to ban a specific IP address or username on the Vandalism in Progress page.

Also, the admins have an idea of Assume_good_faith. Basically, use common sense here. Dont ask someone to be banned because they are doing a newbie test (usually they are in the form of "omfg, are you sure i can edit here?"). But if they do it more than a few times... go ahead and ask them :) --Dragontamer 13:00, 16 December 2005 (UTC)

Origonal Research
http://en.wikibooks.org/wiki/Maple_Story/ThiefGuide#Endure_or_Booster.3F

Hmm, is this your own opinion or is this agreed by most Sins? Sleepywood guys don't seem to agree that high Endure is better than high Booster. Then again, I'm not a thief so blah.

 * Well, I went ahead and tried to make Booster sound better, but still, look it over... I really dont know what I'm talking bout here anyway :) --Dragontamer 04:25, 18 December 2005 (UTC)

Put your name as an author in Maple Story
MapleStory/Authors

I hope you don't mind :) Of course, if you do, you can always remove it. --Dragontamer 06:47, 27 December 2005 (UTC)

Graphics
I didn't do the bowman graphics, though I am alright at doing graphics IMO. (enough to understand what looks good) :-) Yeah, I'll do them, my email is prtiglao@gmail.com. Tell me when you send them. --Dragontamer 21:47, 4 January 2006 (UTC)

title: User talk:MajesticMystic


text:
Sonic the Hedgehog 3

Sonic the Hedgehog 3, or simply Sonic 3, is a platform game in the Sonic the Hedgehog series. It was released as a sequel to Sonic the Hedgehog 2.

General

 * /Controls/
 * /Items/

Normal

 * /Angel Island Zone/
 * /Hydrocity Zone/
 * /Marble Garden Zone/
 * /Carnival Night Zone/
 * /Icecap Zone/
 * /Launch Base Zone/

Bonus

 * /Bonus Stages/
 * /Special Stages/

title: Sonic the Hedgehog 3


text:
Talk:Guide to Social Activity/Losing fear

the Have no regrets part was truly inspiring. Don't even think of touching it. -thanks whoever wrote it, you may have changed my life (*note online disinhibition effect) unsigned comment by 138.89.17.196 at 02:53, 15 December 2005

What if the girl is best friends with another boy?
She's also a friend of mines, and she hangs with a crowd that are mostly my clasmmates (she isn't)... and like i hate the fact that people find out and start sayin "u like ___!" and keep singin it...

=/ --207.112.42.193 17:55, 8 December 2006 (UTC)

brilliant
whoever wrote this document is a genius. My sincere thanks to you. IT will defenetely change the way i think. May God bless you.

Recommendations for gender changes,etc.
I think that the issue of making it gender neutral would defeat the purpose for having the article. It is after all, according to the title, "a guide for getting a girl (for guys).." That being said, I think that to resolve the issue that there could be similar guides such as attracting women (for women) etc. The problem of removing gender, etc for a dating guide is that it would dramatically weaken the article and make it not much value for anyone, male or female trying to meet a woman. For example, straight men and lesbians almost certainly will have different takes on how to attract a woman, or even, which women they are more likely to try to meet.


text:
User:Kaldari

Please see my user page in Wikipedia for more info.

title: User:Kaldari


text:
Talk:Rhetoric and Composition/Argument

The sample essay is one of my own works, I hope it works for this page, Stephanie Wolf

strengthening argument example
I've shortened/simplified sentences throughout argument section for easy clarity. But I'm curious about the example. The ToDo mentions to strengthen the example. Can we rewrite the sample argument given by Stephanie Wolf? Or should we create a new argumentative example? And if we would rewrite her example, how should we make note that this is her example, but has since been reworked since first posting? Karl Klint

I think it's okay to rewrite the essay as you see fit. There's already a disclaimer about how the essay has been changed. --Mattbarton.exe 15:10, 3 May 2007 (UTC)

title: Talk:Rhetoric and Composition/Argument


text:
User:Swapnil durgade/Service management under Linux

3 types of services

Service started by init
1. Configured in /etc/inittab 2. Typically non-TCP/IP services, e.g. dial-in Modems, X windows system, serial ports 3. Provide respawn capability 4. Changes to inittab can be activated with init q

Services launched by System V startup scripts
1. Process are started by System V init script method 2. Program Name often end in 'd' 3. Script takes start, stop, restart etc. arguments 4. two ways to start services a. /etc/init.d/ldp start b. service ldp start 5. To start service automatically in a runlevel, we need a start and kill symbolic link in appropriate run level /etc/rc.d/rc[0-6].d

Service launched by xinetd
1. unlike inetd xinetd does not require that the services in its configuration file be listed in /etc/services

2. It can do access control on all services based on: a. address of remote host b. time of access c. name of remote host d. domain name of remote host

3. It can prevent denial-of-access attacks by

a. placing limits on the number of servers for each service (avoids process table overflows) b. placing an upper bound on the number of processes it will fork c. placing limits on the size of log files it creates d. placing limits on the number of connection a single host can initiate e. place limits on the rate of incoming connections f. discontinue services if the load exceeds specified limit

Controlling access with 'hosts.allow' and 'hosts.deny'
ACCESS CONTROL FILES The access control software consults two files. The search stops at the first match: 1· Access will be granted when a (daemon,client) pair matches an entry in the /etc/hosts.allow file. 2· Otherwise, access will be denied when a (daemon,client) pair matches an entry in the /etc/hosts.deny file. 3· Otherwise, access will be granted. A Non-existing  access  control  file is treated as if it were an empty file. Thus, access control can be turned off by providing no access control files.

'chkconfig' to manager services
Dones not modify current state of System V services

Changes to services managed my xinetd comes into effict immediatly

Can also manage xinetd services

Usage Example 1. chkconfig --list                                     :lists all services in all runlevels 2. chkconfig list                             :lists on/off status in all runlevels 2. chkconfig on                               :enables service in runlevel 2,3,4, and 5 3. chkconfig off                              :disables service in runlevel 2,3,4, and 5 4. chkconfig add                              :ensures either a kill or start symbolic link is setup for every runlevel 5. chkconfig del                              :removes service from chkconfig management 6. chkconfig --level    :turn service on/off in specified levels

-Swapnil (Wednesday, December 15, 2005) Email- swapnil_durgade@yahoo.com


text:
Computer Programming/Design by Contract

This page about DbC focuses on Design by Contract more closely than its cousin. The reason is that Eiffel's DbC (and that of very few other languages) provide close integration of complete DbC with all aspects of the respective language, and the respective language's definitions.

Designing by Contract
»Not without my abstract data types.«

First, Design by Contract applies to modules, to the routines in the modules, to loops in subroutines, and between statements. Exceptions are involved, too. That is to say, you cannot have partial contracts. Contracts involve the whole module at every level of refinement.

If you set up a module(!) contract, the contract's clauses apply to an entire module throughout its entire life time. If you use a module that has a contract, you are obliged to obey its visible rules.

There are two views of a module, the client's view, and the supplier's view. When you write a subroutine, and the subroutine calls other subroutines contained in some module, then your subroutine becomes a client of the module. The client sees two parts of the module's contract:

 * 1) the module's invariants and
 * 2) the preconditions and the postconditions of the module's subroutines.

The module itself is considered a supplier from the clients point of view, it supplies subroutines. The supplier sees more of the module and adds some internal contract clauses, so to speak. The supplier will have to provide, that is, write

 * 1) the module's invariants,
 * 2) the preconditions and the postconditions of the module's subroutines,
 * 3) loop invariants and loop variants,
 * 4) check instructions
 * 5) consistent exception handling

All of these are assertions, or, in the case of exceptions, consistent with assertions.

Check the presence of supporting facilities per language here: Design by contract.

Assertions
The purpose of an assertion is twofold: First, it states expected values of (computed) variables and their relations. Second, it facilitates testing that the variables do have the values stated and that the relations are indeed true. Being part of a program, assertions can be used as run-time checks of variables and their relations. But at the same time, assertions allow reasoning about the program before it is run. You use assertions for showing that a module, subroutine, loop, etc. is correct.

Each assertion is a Boolean expression, and is either True or False. Example:

$$s = 0$$ or else $$g(s) = 2 * t$$

There are two relations in the example involving two variables, some values are computed. The two equality tests are either True or False, and are connected by or else, a Boolean operator.

Taken to the module level, assertions can express requirements that a client must satisfy when calling the module's subroutine. The requirements are stated as preconditions of a subroutine, that is, assertions involving the subroutine's formal arguments and possibly other features of the module. In return, a subroutine's postcondition describes what the subroutine will have to offer as a result. Again, the postcondition is expressed using an assertion involving the subroutine's results and possibly other features of the module. A typical subroutine description, part of the module's contract might look like this:

pop require has_items: not is_empty ensure one_less: count = old count - 1

The subroutine  takes no argument, and it doesn't return anything. However, it modifies the module, a stack. Therefore the pre- and postconditions are assertions that refer to other features of the module, and. Useful names are attached to the assertions for reference.

To complete the contract, another assertion is added at the module level, the module invariant. The relations of the module invariant inform the client about the state of the module by saying what is guaranteed between each call of a subroutine of the module. Example:

invariant sensible_count: count >= 0

Contract violations are assertions that evaluate to False. Typically, when the program does not live up to its assertions, an exception is raised, because the program is obviously wrong. The situation is then handled using the exception mechanisms of the language, bridled by the rules that Design by Contract requires.

Extensive program analysis based on assertions can in some cases be performed at compile time. This amounts in a mechanical proof that certain checks are not necessary. The checks can then be omitted from the compiled program. See SPARK programming language.

 * If an assertion is false, there is a bug in the program!

The reason is that the program does not produce the results that it must produce according to the assertions. Here is a list of the possible assertions in Design by Contract (C means visible to clients (outside the module), S means visible to supplier (inside the module)):

 * Module Invariants (C, S): Module invariants assert what is true after initialisation of the module. They also assert the same truths before and after any execution of one of its subprograms.
 * Preconditions (C, S): A precondition of a subprogram states what must be true before calling the subprogram. Usually, it expresses relations of (computed) module variables and subprogram parameters. Only if the precondition is true can the subprogram execute in order to fulfil its postcondition.
 * Postconditions (C, S): Postconditions state what will be true about (computed) variables and relations when the subprogram has finished successfully.
 * (Loop variants) (S): A loop variant is an expression (of type Natural) whose value decreases towards zero on each iteration of the loop. Typically one of the variables of the loop is used to express this property. The loop variant guarantees termination.
 * Loop invariants (S): A loop invariant expresses a relation that is true when the loop is entered, or entered once more. The relation will name variables of interest to the loop.
 * Checks (S): When a statement has executed, it will likely have changed the value of one or more variables by assignment. A check expresses the programmer's expectation of the relation between these variables after the assignment.

Preconditions P and postconditions Q of a subprogram S frame the subprogram in the sense of a Hoare triple: {at least P} S {guarantees Q}, provided the module invariant is True before and after the call! Notice this last requirement. The module must be in a known good state, because the preconditions and the postconditions may refer to the module's state.

Design by contract is not input checking
By implication, the rule from above about false assertions means that assertions are not to be used as replacements for input validation. When you can't trust your input, use means provided by your language in a conditional, like the attribute in Ada. For example, calling Sqrtx where x = 123 is a bug in using Sqrt, a violation of the contract. The caller has failed to test x before sending it to the math routine.

Assertions can't replace conditionals
Can you pass all kinds of numbers to Sqrt and just prepare to handle the exception raised when the precondition of Sqrt evaluates to false? In other words, can you deliberately ignore the contract? The answer is no, for at least two reasons.

 * 1) If a module has been shown to be correct, assertion checking might have been turned off for this module, expecting that clients will fulfil their part of the contract. A contract violation by the caller could then go unnoticed and might produce a vastly erroneous computation.
 * 2) If the called subprogram is not Sqrt but controls the speed of a train, you can't just pass invalid input until it doesn't happen to make the speed-control subprogram fail with an exception. Worse, see 1.

Example: A Stack
(This example is given in very minimal Ada notation, knowing that language support for DbC is pretty good, in particular in Ada 2005, but limited. Imagining require, ensure, and invariant in place of the comments marked pre, post, and inv will render the following closer to the Eiffel original. Use the facilities that your language provides for expressing assertions and exception handling.)

The exclamation points (`<tt>!</tt>') below are only a notational device. They stand for the facilities available with the respective languages. Their meaning is only informative of the contract.

Item Stack is_empty Boolean count Natural top Item pushx Item pop Stack Notice that up to this point, there is no executable statement in the module. It's just a package specification with contractual pre- and postconditions, and a module invariant. Yet the module's contract is complete as far as clients of this module are concerned.

The function  states as precondition that there must be an element on the stack, otherwise it cannot succeed. To express this, it refers to another function of the same module,. Note that the module invariant does allow an empty stack. The function  has neither precondition nor postcondition, but is mentioned in a module invariant. This means that clients can still expect that  returns a value

Now if is_empty False then by count 0, count 0 must be true because is_empty if and only if count 0.

 * A software component is correct in the sense of these contracts if you finally prove it, using the assertions and rules from the language definition.

The internal view of the module, in this case a package body, shows how assertions can be placed in an program. It is important to understand that assert in Ada, require in Eiffel, etc. are tightly integrated with the languages' exception handling mechanisms. This is unlike what you might be guessing if you know C's assert. (The implementation of the example stack is actually based on Ada.Containers, similar to how Eiffel's STACK classes are usually implemented. It could also be based on D's arrays, or whatever language you choose.)

Assertion_PolicyCheck ...   s Vector ...    top  Item assert is_empty "stack is empty" sLast_Element top Think about the effects of turning assertion checking on or off. Assertions express a contract, they do not handle invalid input.

Exceptions and Contracts
What if a precondition is true, but some statement from the executing subprogram raises an exception? Chances are that the postcondition can no longer be established by the subprogram. It will fail. However, what about the state of the module?

The first answer to the question about the state of the module is given by this rule:

 * When an exception is allowed to propagate from the subprogram, the module invariant must first be established.

The second answer can be different, depending on the language. The Eiffel way, for reference, is to retry the routine in case of an exception: If the exception is handled, and the subprogram should retry to fulfil its postcondition, then both its precondition, and the module invariant must first be established. (Otherwise the system cannot act like invoking the routine again without violating the contract.)

Ada, like some other languages, has nested blocks, so exception handling could start from a block's preconditions. Hence if you manage to restore the block's preconditions, you can retry the block. A block may be nested inside a loop, for example. Then your handler will have to assign values to variables satisfying the necessary preconditions of a loop execution.

Inheritance
TBD

In brief, the preconditions of overridden methods are or-ed, the post-conditions are and-ed.

For modules built around derived types, it must be possible to substitute an object of a derived type for an object of the parent type such that a dispatching call can still rely on the parent's contract. Likewise, the postconditions of the feature that gets actually called must imply the postconditions of the parents' features.

A Flaw
Given an OO parent type T, together with one of its methods,

T     foox T n Count  Natural

and a type derived from T, called D, with the method overridden,

D  T     foox D n Count  Natural

imagine a reference to an OO variable of some type in the T hierarchy. Then

x T   D      xfoo42

Who is to blame?

Concurrency
TBD

One new (to the discussion so far) problem introduced by concurrent execution is this: Suppose

 * 1) a module's routines should do their work on behalf of more than one caller at a time,
 * 2) an “instance” of some routine may be interrupted by another “instance”

Then for example what was true about the module state when the first call was initiated might no longer be true after executing the second call has changed the state of the module. This extends to pre/postcondition checks: Since the assertions of the routines will likely refer to their module's state (and to anything visible in general), they can become inconsistent.

A first attempt at a solution is to make the precondition check, the execution of a routine, and the postcondition check sequential and exclusive. That is, as long as a caller is served by the routine, other calls to the routine are made pending until the routine has finished.

But in addition, since the routine's assertions are about module state, any service of the module called by any other caller should be put on hold.

See also guards, SCOOP, Ada (tasking and protected types, synchronized interfaces).

title: Computer Programming/Design by Contract


text:
User:GorgeUbuasha/My sand box

Scratch Space
a 0  a  1

a 0  a  1

WiKi markup and Ada comments
OK:

But:

, versus and versus

(From [Computer_programming/Design_by_Contract])

Resolution: look at this WiKi's templates syntax, named and numbered parameters, like in. IOW RTFM. Thanks to ManuelGR for pointing this out.

title: User:GorgeUbuasha/My sand box


text:
User:Narasing

Hello I am narasing from india

title: User:Narasing


text: User talk:200.199.217.1

title: User talk:200.199.217.1


text:
User talk:195.175.37.71

Please stop. If you continue to use Wikibooks for advertising, you will be temporarily blocked from editing.

title: User talk:195.175.37.71


text: User talk:70.81.114.63

title: User talk:70.81.114.63


text:
User talk:221.112.111.102

Please stop. If you continue to blank pages, you will be blocked from editing.

title: User talk:221.112.111.102


text: User talk:69.234.209.123

title: User talk:69.234.209.123


text:
User talk:80.0.69.162

Please stop adding nonsense to Wikibooks. It is considered vandalism. If you would like to experiment, use the sandbox. Thank you.

title: User talk:80.0.69.162


text:
User talk:67.158.71.181

Please stop adding nonsense to Wikibooks. It is considered vandalism. If you would like to experiment, use the sandbox. Thank you.

title: User talk:67.158.71.181


text:
User talk:69.65.75.60

Please stop adding nonsense to Wikibooks. It is considered vandalism. If you would like to experiment, use the sandbox. Thank you.

title: User talk:69.65.75.60


text:
User talk:Swapnil durgade

Leave a message

welcome
Hello and welcome to Wikibooks. Have you read Naming policy? Pages you're creating are not linked (every book should be placed in a bookshelf. Every book should also have proper chapter names, as it is written in the naming policy.

If you have any questions, leave me a message. --Derbeth talk 09:53, 15 December 2005 (UTC)

 * I think you contribute useful material, the problem is that our visitors should be able to find them. I suggest you put your pages as chapters of Guide to UNIX (you can consult Kernigh who planned this book where to put your work). You could also gather your pages into a new book, but I don't think we need two books on the same subject. --Derbeth talk 09:02, 16 December 2005 (UTC)

subpages
I moved the subpages from your user page into your user namespace. If you have any questions, let me know. --Whiteknight (talk) (projects) 19:47, 12 July 2006 (UTC)

thank you
Thank you for your "Cryptography/Notes". It appears someone else thought they were useful enough to use in the Cryptography Wikibook. --DavidCary (discuss • contribs) 14:48, 12 August 2012 (UTC)

title: User talk:Swapnil durgade