text:
User:"juan carlos arango"

LIMITES
1)$$\lim_{x\to -2}\frac {x^3+2x^2+1-1}{x+2}$$

=$$\lim_{x\to -2}\frac {x^3+2x^2}{x+2}$$

=$$\lim_{x\to -2}\frac {x^2(x+2)}{x+2}$$

=$$\lim_{x\to -2}\ x^2$$

=$$\ 4$$

BY JUAN CARLOS ARANGO

2)$$\lim_{x\to 1}\frac {x^2-1}{x^3-1}$$

=$$\lim_{x\to 1}\frac {(x-1)(x+1)}{(x-1)(x^2+x+1}$$

=$$\lim_{x\to 1}\frac {x+1}{x^2+x+1}$$

=$$\frac {2}{1+1+1}$$

=$$\frac {2}{3}$$

BY JUAN CARLOS ARANGO

3)$$\lim_{x\to 1}\frac {t^3-t}{t^3-1}$$

=$$\lim_{x\to 1}\frac {t(t^-1)}{(t-1)(t^2+t+1}$$

=$$\lim_{x\to 1}\frac {t(t+1)(t-1)}{t-1(x^2+x+1)}$$

=$$\frac {1(1+1)}{1^2+1+1}$$

=$$\frac {2}{3}$$

BY JUAN CARLOS ARANGO

DERIVADAS
4)$$\ y= \frac{4x^3-2x}{7}$$
 * $$\ y'=\frac{12x^2-2(7)-0(4x^3-2x)}{(7^2)}$$
 * $$\ y'=\frac{12x^2-2(7)}{(7^2)}$$
 * $$\ y'=\frac{12x^2-2}{7}$$

BY JUAN CARLOS ARANGO

5)$$\ y= \frac{4-3x}{2+x}$$
 * $$\ y'=\frac{-3(2+x)-(4-3x)(1)}{(2+x)^2}$$
 * $$\ y'=\frac{-6-3x-4+3x}{(2+x)^2}$$
 * $$\ y'=\frac{-10}{(2+x)^2}$$

BY JUAN CARLOS ARANGO

6) $$\ y={x^3-x^2+2x}$$
 * $$\ y'={3x^2-2x+2}$$

BY JUAN CARLOS ARANGO 7)$$\ y={w(x)v(x)w(x)}$$
 * $$\ y={w^2(x)v(x)}$$
 * $$\ y'={2w(x)(w'(x))v(x)+w^2v'(x)}$$

BY JUAN CARLOS ARANGO

PROBLEMAS DE RAZON DE CAMBIO
8)Con que rapídes baja el nivel de un fluido contenido en un tanque cilindrico de almacenamiento si bombeamos hacia fuera el fluido a razon 3000 l/min

 * $$\frac {dh}{dt}=3000 l/min$$

 * $$\ v={pir^2h (metros cubicos)}$$

 * $$\ m^3={1000 l}$$

 * $$\frac {dv}{dt}=1000pir^2(\frac {dh}{dt})$$

 * $$\frac {-3000}{1000pir^2}=\frac {dh}{dt}$$

 * $$\frac {-3000}{1000pir^2}=\frac {dh}{dt}$$

 * $$\frac {-3000}{1000pir^2}=\frac {dh}{dt}$$

 * $$\frac {-3l}{pir^2}=\frac {dh}{dt}$$

BY JUAN CARLOS ARANGO

9)un globo de aire caliente se eleva vericalmente desde un campo y es raestreado por un localizador a 500m del punto de despeje. en el instante en que el angulo del localizador es pi/4 el angulo se esta elevando a razon de 0.14 rad/min ¿conque velocidad se esta elevando el globo en ese instante?

 * $$\frac {dx}{dt}=0.14 rad/min$$

 * $$\ tanx=\frac {h}{500}$$

 * $$\ h={500}{tanx}$$

 * $$\frac {dh}{dt}=500sec^2x(\frac {dx}{dt})$$

 * $$\frac {dh}{dt}=500sec^2(pi/4)0.14$$

 * $$\frac {dh}{dt}=500(2)0.14$$

 * $$\frac {dh}{dt}=140 m/min$$

BY JUAN CARLOS ARANGO

title: User:"juan carlos arango"


text:
Russian

RUSSIAN РУССКИЙ

Learning the Russian Language, for English Speakers

de:Russisch: Grammatik Ρωσικά Rusa Ruso Enseignement du russe Russo רוסית Russisch Rosyjski Russo Venäjän kieli Русский язык как иностранный Rusça 俄语

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

title: Russian


text:
User talk:Klugscheisser~enwikibooks

--dustin 03:00, 15 Jul 2004 (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 Klugscheisser. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Klugscheisser~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:20, 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:09, 19 April 2015 (UTC)

title: User talk:Klugscheisser~enwikibooks


text:
User talk:69.79.62.141

You need to log in. Dysprosia 05:10, 15 Jul 2004 (UTC)

title: User talk:69.79.62.141


text:
Talk:Waves/Vectors

Is anyone here working on this going to finish the pictures in this module, especially Figures 2.1 - 2.4 ?

I would like to refer to this section in some of the modules I'm working on instead of writing my own vector tutorial redundantly. H Padleckas 13:28, 15 Jul 2004 (UTC)

Hi, at the following url, https://en.wikibooks.org/wiki/Waves/Vectors, below figure 4 says "All that remains to be proven for equation (2.6) to hold …", there is no equation (2.6) on that page that I can find.

title: Talk:Waves/Vectors


text:
User talk:Jimregan

This message is from Wikibooks member H Padleckas. Apparently, you wrote, or mostly wrote, the Wikibooks module Modern Physics:Math:Vectors, however never uploaded many of the pictures for it, in particular Figures 2.1 - 2.4. Are you going to finish the pictures in this module, especially Figures 2.1 - 2.4 ? Do you need help in making the pictures?

I would like to refer to this section in some of the modules I'm working on instead of writing my own vector tutorial redundantly. H Padleckas 14:02, 15 Jul 2004 (UTC)

User:Carandol has added vector pictures 1 - 4
User User:Carandol hass added pictures 1 - 4 in place of the empty spaces for Figures 2.1 - 2.4 in module Modern Physics:Math:Vectors, which you had started. Do you want to check to see what Carandol did? Also I'm thinking of adding more pictures myself showing scalars. H Padleckas 07:19, 16 Jul 2004 (UTC)

title: User talk:Jimregan


text:
User:SIB

sv:Användare:Softssa en:User:Softssa

title: User:SIB


text:
ASP.NET

ASP.NET is a web programming platform developed by Microsoft. It is the successor to Active Server Pages. The term "classic ASP" is often used to distinguish previous versions of Active Server Pages with the .NET (pronounced "dot net") versions.

This wikibook is an introduction to ASP.NET. It assumes no prior experience with web programming or with any particular web programming language or platform (including classic ASP), though we will often compare ways of doing things in ASP.NET with ways of doing them in other languages, especially PHP. We believe the differences between classic ASP and ASP.NET are substantial enough to merit separate treatment.

Getting Started

 * /About ASP.NET/ : About the ASP.NET Language
 * /Your First Page/ : Building Your First ASP.NET Page
 * /Examining The Page Structure/ : Examining ASP.NET's Page Structure
 * /Adding A Little Interactivity/ :

Adding Some Interactivity
So far, we haven't done anything we couldn't have done much more easily with straight HTML and a bit of CSS. But we have to start with the basics and work up, as in any subject.

Advanced Topics

 * /Membership/
 * /Roles/
 * /Profiles/
 * /Role-Based Security/
 * /Cryptography/
 * /Templating/
 * /Database/
 * /Data Access Layer and Business Logic Layer/

A Quick Summary

 * /Web Server Controls/
 * /User Controls/
 * /Custom Control/
 * /Data Grid/, /Grid View/ (ASP.NET 2.0)
 * /Array/, /Collections/
 * Interoperability in referring any unmanaged assemblies into your Web Site
 * AJAX & Atlas (Asynchronous Page development)

Programmeren in ASP.NET

title: ASP.NET


text:
User:Kellerkind

Hm, ich schau mich nur mal um & werde zukünftig wohl etwas beitragen. Ansonsten findet man meine Benutzerseite in der Wikipedia.

title: User:Kellerkind


text:
Cookbook:Yorkshire Pudding

| Cuisine of the United Kingdom

A Yorkshire pudding is a light, fluffy dish that is usually cooked and served alongside a roast dinner, traditionally made with roast meat—especially roast beef. It comes from Yorkshire, a region in the United Kingdom, and is popular across the island. The exact recipe differs from area to area, even from family to family, so the below recipe offers a generic approach to the tasty pudding.

Ingredients

 * 140 g plain flour
 * 4 ea. (200 g) eggs
 * 200 ml milk
 * Sunflower oil or meat drippings
 * ¼ teaspoon salt
 * ¼ teaspoon pepper
 * Thyme (optional)
 * Rosemary (optional)
 * Mustard powder (optional)
 * Sage (optional)
 * Red onion (optional)

Equipment

 * 2 x 4-hole Yorkshire pudding tins, or a 12-hole large muffin tin
 * Large bowl
 * Jug
 * Whisk
 * Sieve
 * Silicone spatula
 * Oven gloves

Procedure

 * 1) Preheat the oven to 230°C (210°C convection)
 * 2) Fill your tin(s) with a thin layer of your chosen oil, and place into the oven to heat up.
 * 3) Sieve flour into a bowl, then beat in eggs until smooth.
 * 4) Slowly add the milk in stages, beating as you go until well-mixed.
 * 5) Season with salt and pepper. Add optional ingredients as desired.
 * 6) Transfer the batter to a pouring jug. For best results, rest the batter in the fridge for 1 hour.
 * 7) Being swift, but careful, remove the hot tin(s) from the oven, and evenly fill the holes with your batter.
 * 8) Place the tin(s) back into the oven, and leave them undisturbed for 20–25 minutes until puffed and golden brown. Opening the oven door can upset the cooking of the Yorkshire puddings—trust the process and watch with the door closed.
 * 9) Serve immediately. They can also be cooled and frozen for up to 1 month.

Notes, tips, and variations

 * For the best Yorkshire puddings, make sure your oil is as hot as it can be. Try a little batter first to see if it instantly puffs up.

title: Cookbook:Yorkshire Pudding


text:
User talk:Nuntaro

Witam na Wikibooks! Mam nadzieję, że zamierzasz wniść jakiś wkład w tę bibliotekę darmowych podręczników szkolnych. Jeśli tak to proszę dopisz się na stonach: Owocnej pracy, Reytan 16:21, 15 Jul 2004 (UTC)
 * 1) Kontakt z autorami i bibliotekarzami
 * 2) Polscy bibliotekarze

title: User talk:Nuntaro


text:
Talk:General Relativity/Covariant Differentiation

I've already covered coordinate transformations in the section "Coordinate systems and the comma derivative," so you might wanna take a look at that before you spend time talking about transforming coordinates.

Also, concerning your notation $$\partial_{\mu} f $$, note that I am going to use the notation $$\nabla_{\mu} \mathbf{T} $$ for covariant differention along $$\mathbf{e}_\mu$$. However, I AM going to use your notation $$\partial_{\mu} f$$ for scalar-valued functions such as $$f$$, so this is good as we are consistent at this point.

Finally, your use of latin indices (i, j, & k) could potentially cause confusion later, as I am going to add a section on the vierbein bundle, at which point latin indices will have a VERY different meaning than greek indices (which I have been using elsewhere so far). -Lathem

You are right. I'm being very sloppy here, and I should be using greek indices. I'm trying to remember the derivation of the covariant derivative from memory, and doing a bad job of it. -- Roadrunner


text:
The Voynich Manuscript/F6r

Transcription, comments, theories, links to do with VMs page f6r to be added here... :-)

Description:
One plant, that takes up most of the right and bottom halves of the page.

One long paragraph (14 lines) at the top, left justified. The first three lines are right-justified, the rest follows the plant's profile on the right. The first six lines are interrupted by a flower or pod.

Comments:
It is not clear whether pods or flowers are represented here.

title: The Voynich Manuscript/F6r


text:
The Voynich Manuscript/F6v

Transcription, comments, theories, links to do with VMs page f6v to be added here... :-)

Description:
One plant, that takes up most of the right half of the page.

Two paragraphs (4.8 and 15.8 lines) at the top, left-justified, ending at mid-page. The first is right-justified too, and two of its lines are interrupted by a flower. The second follows the plant's outline on the right.

title: The Voynich Manuscript/F6v


text:
The Voynich Manuscript/F7r

Transcription, comments, theories, links to do with VMs page f7r to be added here... :-)

Description:
One plant with no leaves and a single huge flower, spanning the entire height and width of the page.

 * Root: a short, vertical, cylindrical stem that splits into two almost horizontal mousetails.

 * Stem: straight, vertical.

 * Branches: none.

 * Leaves: none.

 * Flowers: a single flower at the tip of the stem.

 * Stalk: not visible, or indistinguishable from stem.

 * Chalyx: eight symmetrical sepals, shaped like long parabolas.

 * Corolla: four layers, of decreasing sizes, each having four symmetric petals, located diagonally with respect to  the previous layer.

 * Core: none.

Two paragraphs (with 4.3 lines and 4.5 lines), both left- and right-justified: one at the top, interrupted by the flower; one just below mid-page, interrupted by the main stem.

Comments:
Petersen has identified this plant with high confidence as

Nymphaea alba (white water lily, seerose)

http://www.runeberg.org/nordflor/181.html

http://linnaeus.nrm.se/flora/di/nymphaea/nymph/nympcan2.jpg

There is indeed a good match in the shape and arrangement of the petals and sepals. Also, the lack of leaves and branches in f7v is plausibly explained by the fact that Nymphaea's flowers float on the water's surface, and thus may have been hidden from the artist's view.

But if f7v is Nymphaea alba, then what do we make of f2v?

title: The Voynich Manuscript/F7r


text:
The Voynich Manuscript/F7v

Transcription, comments, theories, links to do with VMs page f7v to be added here... :-)

Description:
One plant, spanning from the bottom edge to 3/4 of the way to the top.

Two paragraphs (with 4.5 and 3.9 lines) at the top, left- and right-justified. The last three lines of the second paragraph are interrupted by the plant's flowers.

title: The Voynich Manuscript/F7v


text:
The Voynich Manuscript/F8r

Transcription, comments, theories, links to do with VMs page f8r to be added here... :-)

Description:
One plant with a single, big, odd-shaped leaf and a "collar" around its stem, horizontally centered and spanning the page vertically from edge to edge.

Three paragraphs (with 6.5, 3.6, 6.6 lines), left- and right-justified and interrupted by the plant's stem, fill up the bottom 3/4 of the page. Each paragraph is followed by a right-justified two-word title.

Comments:
The plant is very strange, both for the leaf shape and for the "collar" around the stem. Perhaps it is a mushroom (e.g. Amanita), which the artist mistook for a plant and tried to draw as such?

The text format too is quite unusual, both in its length and in the presence of titles.

title: The Voynich Manuscript/F8r


text:
The Voynich Manuscript/F8v

Transcription, comments, theories, links to do with VMs page f58v to be added here...

Description:
One plant, spanning top to bottom, slightly offset to the left.

Two paragraphs (with 10.1 and 5.3 lines), left- and right-justified: one next to the top margin, one next to the bottom margin, both interrupted by the plant.

There is a mark in the SE corner, resembling "^pm9" ("^" over the "p"), with thick strokes.

Comments:
The mark in the SE corner is almost surely the quire number, "1st" in abbreviated Latin.

title: The Voynich Manuscript/F8v


text:
PostScript FAQ

This FAQ covers PostScript language and Ghostscript software suite, as the most common free PostScript interpreter.

Table of Contents

 * /General/
 * /Using PostScript/
 * /Programming PostScript/
 * /Known errors/
 * /Using Ghostscript/

title: PostScript FAQ


text:
File:VectorIntro1.png

Taken from http://kestrel.nmt.edu/~raymond/classes/ph13xbook/index.html a GNUFDL source

Copyright ©1998, 2000, 2001, 2003 David J. Raymond

/Images

title: File:VectorIntro1.png


text:
File:VectorIntro2.png

Taken from http://kestrel.nmt.edu/~raymond/classes/ph13xbook/index.html a GNUFDL source

Copyright ©1998, 2000, 2001, 2003 David J. Raymond

/Images

title: File:VectorIntro2.png


text:
File:VectorIntro3.png

Taken from http://kestrel.nmt.edu/~raymond/classes/ph13xbook/index.html a GNUFDL source

Copyright ©1998, 2000, 2001, 2003 David J. Raymond

/Images

title: File:VectorIntro3.png


text:
File:VectorIntro4.png

Summary
/Images

title: File:VectorIntro4.png


text:
Cookbook:Boiling

Boiling, as it applies to cooking, means cooking foods in boiling water. In most populated parts of the world, plain water boils at temperatures from about 200°F to 212°F (95°C to 100°C). This varies with the atmospheric pressure, which in turn varies with both altitude and weather. When the water is salted, the boiling temperature is slightly higher than for clean water.

When the atmospheric pressure on the surface of the water is lessened, boiling takes place at a lower temperature than that mentioned, and in extremely high altitudes the boiling point is so lowered that to cook certain foods by means of boiling water is difficult. As the water heats in the process of boiling, tiny bubbles appear on the bottom of the vessel in which it is contained and rise to the surface. Then, gradually, the bubbles increase in size until large ones form, rise rapidly, and break, thus producing constant agitation of the water.

Effects
Boiling has various effects on foods. It toughens the albumin in eggs, softens the fiber and dissolves the connective tissues in meat, softens the cellulose in cereals, vegetables, and fruits, and dissolves other substances in many foods. A good point to bear in mind in preparing foods by boiling is that slowly boiling water has the same temperature as rapidly boiling water and is therefore able to do exactly the same work. However, certain recipes may specify rapid boiling or slow boiling due to other conditions (such as not wanting to disintegrate soft food, or wanting to make use of the bubbles that appear in rapid boiling).

Turning the stove on high, keeping the gas burning full heat, or running the fire hard to keep the water boiling rapidly is therefore unnecessary; besides, it wastes fuel without doing the work any faster and sometimes not so well. However, there are several factors that influence the rapidity with which water may be brought to the boiling point; namely, the kind of utensil used, the amount of surface exposed, and the quantity of heat applied.

A cover placed on a saucepan or a kettle in which food is to be boiled retains the heat, and thus causes the temperature to rise more quickly; besides, a cover so used prevents a loss of water by condensing the steam as it rises against the cover. As water boils, some of it constantly passes off in the form of steam, and for this reason syrups or sauces become thicker the longer they are cooked.

The evaporation takes place all over the surface of the water; consequently, the greater the surface exposed, the more quickly is the quantity of water decreased during boiling. Another point to observe in the boiling process is that foods boiled rapidly in water have a tendency to lose their shape and are reduced to small pieces if allowed to boil long enough.

Many recipes for pork ribs call for parboiling them before cooking, but this method is not recommended, as water is a solvent and may wash away flavors.

Health Purposes
Besides serving to cook foods, boiling also renders water safe, as it kills off any germs that may be present. Boiled water, as is known, loses its good taste. However, as this change is brought about by the loss of air during boiling, the flavor can be restored and air again introduced if the water is shaken in a partly filled jar or bottle, or beaten vigorously for a short time with an egg beater or whisk.

title: Cookbook:Boiling


text:
Cookbook talk:Boiling

The initial two posts were copied and pasted from the "Woman's Institute Library of Cookery Volume 1", found at Project Gutenberg. liblamb 23:11, 15 Jul 2004 (UTC)

Are you sure?
"Boiling has various effects on foods. It toughens the albumin in eggs, toughens the fiber and dissolves the connective tissues in meat, softens the cellulose in cereals, vegetables, and fruits, and dissolves other substances in many foods."

Is that "toughens" or "softens" ?

pop
pop

title: Cookbook talk:Boiling


text:
Cookbook:Simmering

Simmering, or stewing, is a modification of boiling. By this method, food is cooked in liquid at a temperature below the boiling point, or anywhere from 185 to 200 degrees Fahrenheit (85-95 Celsius). Water at the simmering point always moves gently--never rapidly as it does in boiling. Less heat and consequently less fuel are required to cook foods in this way, unless, of course, the time consumed in cooking the food at a low temperature is much greater than that consumed in cooking it more rapidly.

Aside from permitting economy in the use of fuel, simmering, or stewing, cooks deliciously certain foods that could not be selected for the more rapid methods. For example, tough cuts of meat and old fowl can be made tender and tasty by long cooking at a low temperature, for this method tends to soften the fiber and to develop an excellent flavor. Tough vegetables, too, can be cooked tender by the simmering process without using so much fuel as would be used if they were boiled, for whatever method is used they require long cooking. Beets, turnips, and other winter vegetables should be stewed rather than boiled, as it is somewhat difficult to cook them tender, especially in the late winter and early spring. If dry beans and peas are brought to the simmering point and then allowed to cook, they can be prepared for the table in practically the same length of time and without so much fuel as if they boiled continuously.

title: Cookbook:Simmering


text:
Cookbook talk:Simmering

The initial post was copied and pasted from the "Woman's Institute Library of Cookery Volume 1", found at Project Gutenberg. liblamb 23:22, 15 Jul 2004 (UTC)

title: Cookbook talk:Simmering


text:
Cookbook:Steaming

Steaming is the cooking of food by the application of steam. In this cooking process, the food is put into a steamer, which is a cooking utensil that consists of a vessel with a perforated bottom placed over one containing water. As the water boils, steam rises and cooks the food in the upper, or perforated, vessel. Steamers are sometimes arranged with a number of perforated vessels, one on top of the other. Such a steamer permits the cooking of several foods at the same time without the need of additional fuel, because a different food may be placed in each vessel.

Steaming is preferable to boiling in some cases, because there is no loss of mineral salts nor food substances. The flavour is not so likely to be lost as when food is boiled. Some delicate fish is best cooked by steaming as it does not break up as it might in boiling water. Vegetables prepared in this way prove very palatable, and very often variety is added to the diet by steaming bread, cake, and pudding mixtures and then, provided a crisp outside is desired, placing them in a hot oven to dry out the moist surface.

Recipes that call for steaming

 * Bengal Potatoes
 * Mussels with Potatoes
 * Steamed Artichoke
 * Steamed Rice

ספר מתכונים/אידוי

title: Cookbook:Steaming


text:
Cookbook talk:Steaming

The initial post was copied and pasted from the "Woman's Institute Library of Cookery Volume 1", found at Project Gutenberg. liblamb 23:27, 15 Jul 2004 (UTC)

Steaming cooking
Suggest add Category:Steaming cooking. --BoldLuis (discuss • contribs) 00:01, 13 April 2020 (UTC)

title: Cookbook talk:Steaming


text:
How to Play Violin

This book teaches violin. For fiddle, see How to Play Fiddle.

For more information

 * Intriguing historical background on violin
 * Music Theory: a site that provides a course on music theory

Related Wiki Books

 * Compendium of Fiddle Styles
 * Ethnography of Fiddle
 * Contemporary Fiddlers
 * Cello Handbook

ਵਿਓਲੀਨ

title: How to Play Violin


title: Template:GFDL-1.1-plus


text:
User:Donarreiskoffer

see: w:user:donarreiskoffer

title: User:Donarreiskoffer


text:
Talk:Algebra/Arithmetic/Numerical Axioms

The version written on August 3rd, 2003 contradicts the module Algebra/Further arithmetic and other algebra books such as the Reference given below because Axiom 1 states that there is a natural number 0 and the other sources say that the natural numbers are 1, 2, 3, 4, ..... Effectively the other sources say that 0 is a whole number but not a natural number.

Reference: ALGEBRA AND TRIGONOMETRY with Analytic Geometry, Ninth Edition, by Earl Slotkowski and Jeffery Cole, Brooks/Cole Publishing Company 1997

H Padleckas 09:55, 16 Jul 2004 (UTC)


text:
The Voynich Manuscript/F9r

Transcription, comments, theories, links to do with VMs page f9r to be added here... :-)

Description:
One plant flush against the right margin, spanning the page vertically edge to edge, with branches and roots that take up the bottom 2/3 of the page.

Two paragraphs (with 5 and 3.9 lines), left- and right-justified. Both are interrupted by the plant's flower head.

The second paragraph is followed by a centered title-like line which may be the true last line of the paragraph.

Comments:
The unusual shape of the leaves should make the plant easy to identify.

title: The Voynich Manuscript/F9r


text:
The Voynich Manuscript/F9v

Transcription, comments, theories, links to do with VMs page f9v to be added here... :-)

Description:
One plant, flush against the right and bottom edges, reaching almost to the top.

 * Root: a bundle of thin wires. Dark overpaint?

 * Stem: one straight. Light color.

 * Branches: two symmetrical pairs, oblique.

 * Leaves: the four lower ones are medium width, lance-shaped, with smooth edges; the others have the same outline but are deeply cut into five narrow points. Dark color.

 * Stalk: short, mostly missing.

 * Flowers: five, at the tips of stem and branches.

 * Stalk: medium length, thin

 * Chalyx: flat or everted, with short triangular sepals, partly hidden by corolla.

 * Petals: five rounded petals, a large one on top, the others like "arms and legs".

 * Core: very small. Medium and dark colors.

Two paragraphs (with 3.7 and 7.7 lines) at the top, left-justified. The first one is right-justified; the second one follows the plant's profile on the right. Both are interrupted in several places by the flowers and leaves.

Comments:
Petersen identifies this plant, with high confidence, as "Viola trinitalis". I coudn't find such species, but "herba trinitatis" is the herbalists' name for Viola tricolor (heartsease,wild pansy) [1,2,3].

Indeed, comparing f9v with a drawing by Carl Lindman [1], we see an almost perfect match --- including the roots, and the two types of leaves.

Dennis Mardle [10 Oct 1998] observes that the details match also Viola arvensis (field pansy), which hybridises with V. tricolor and is very similar in shape, including especially the dimorphic leaves [1,4].

The colors may help resolve this issue. The flowers of Viola tricolor are usually purple and white with yellow core; Lindman's drawing shows V. arvensis as white (or light blue?) with yellow core. Jim Reeds color list [03 Mar 1998] reports some blue on this page, to be confirmed.

In either case, there is one odd detail: the flowers in f9v are upside-down. Also the two bottom flowers are somewhat different.

Viola tricolor was used internally to treat epilepsy, asthma and bronchitis (whole plant), as an emetic and purgative (seeds) and as a heart tonic (flowers). Externally it was used to treat skin diseases [2]. The flowers are reported to be edible.

References:
[1] Carl Axel Magnus Lindman
 * Bilder ur Nordens Flora
 * 227. A. Styvmorsviol, Viola tricolor L.; B. Åkerviol, Viola arvensis Murr.
 * http://www.runeberg.org/nordflor/
 * http://www.runeberg.org/nordflor/227.html

[2] Mrs. M. Grieve, F.R.H.S.
 * A Modern Herbal
 * Viola tricolor - Heartsease
 * http://www.botanical.com/botanical/mgmh/mgmh.html
 * http://www.botanical.com/botanical/mgmh/h/hearts10.html

[3] ECNC DATABASE: SAXIFRAGA European Flora Slides
 * Viola tricolor ssp. tricolor
 * http://www.ecnc.nl/doc/ecnc/saxifrag/euroflor.html
 * http://www.ecnc.nl/gif/viotritr.gif

[4] ECNC DATABASE: SAXIFRAGA European Flora Slides
 * Viola Arvensis Murr.
 * http://www.ecnc.nl/doc/ecnc/saxifrag/euroflor.html
 * http://www.ecnc.nl/gif/vioarv.gif

title: The Voynich Manuscript/F9v


text:
The Voynich Manuscript/F10r

Transcription, comments, theories, links to do with VMs page f10r to be added here... :-)

Description:
One plant, flush against the right and bottom edges, reaching almost to the top.

Two paragraphs (with 4.4 and 6.8 lines) at the top. They are left- and right-justified, except for the last four lines of paragraph 2, which follow the plan'ts outline on the right. Paragraph 2 is interrupted by the flower stalk.

title: The Voynich Manuscript/F10r


text:
The Voynich Manuscript/F10v

Transcription, comments, theories, links to do with VMs page f10v to be added here... :-)

Description:
One plant, flush against the bottom edge and the right margin, reaching 2/3 of the way to the top.

Two paragraphs (with 2.6 and 3.8 lines) at the top, left- and right-justified, ending just above the plant.

title: The Voynich Manuscript/F10v


text:
Cryptography/Enigma machine

The Enigma was an electro-mechanical rotor cypher machine used for both encryption and decryption, widely used in various forms in Europe from the early 1920s on. It is most famous for having been adopted by most German military forces from about 1930 on. Ease of use and the supposedly unbreakable cypher were the main reasons for its widespread use. The machine had two inherent weaknesses: it guaranteed that a letter would never be encrypted to itself and the rightmost rotor would rotate a set number of places before the next would rotate (26 in the initial version). In German usage the failure to replace the rotors over many years of service and patterns in messages further weakened the system. The cypher was broken, and the reading of information in the messages it didn't protect is sometimes credited with ending World War II at least a year earlier than it would have otherwise.

The counterpart British encryption machine, Typex, and several American ones, e.g. the SIGABA (or M-134-C in Army use), were similar in principle to Enigma, but far more secure. The first modern rotor cypher machine, by Edward Hebern, was considerably less secure, a fact noted by William F. Friedman when it was offered to the US Government.

History
Enigma was developed by Arthur Scherbius in various versions dating back to 1919. He set up a Berlin company to produce the machine, and the first commercial version (Enigma-A) was offered for sale in 1923. Three more commercial versions followed, and the Enigma-D became the most important when several copies were purchased by the Reichsmarine in 1926. The basic design was then picked up by the Army in 1929, and thereafter by practically every German military organization and by many parts of the Nazi hierarchy. In the German Navy, it was called the "M" machine.

Versions of Enigma were used for practically all German (and much other European Axis) radio, and often telegraph, communications throughout the war; even weather reports were encrypted with an Enigma machine. Both the Spanish (during the Civil War) and Italians (during World War II) are said to have used one of the commercial models, unchanged, for military communications. This was unwise, for the British (and one presumes, others) had succeeded in breaking the plain commercial version(s) or their equivalents. This contributed to the British defeat of a large part of the Italian fleet at Matapan.

Operation
The Enigma machine was electro-mechanical, meaning it used a combination of electrical and mechanical parts. The mechanism consisted primarily of a typewriter-style keyboard, which operated electrical switches as well as a gearing mechanism.

The electrical portion consisted of a battery attached through the keys to lamps. In general terms, when a key was held down on the keyboard, one of the lamps would be lit up by the battery. In the picture to the right you can see the typewriter keys at the front of the machine, and the lights are the small (barely visible) circles "above" the keyboard in the middle of the machine.

The heart of the basic machine was mechanical, consisting of several connected rotors. Enigma rotors in most versions consisted of flat disks with 26 contacts on each side, arranged in a circular manner around the outer faces of the disk. Every contact on one side of each disk is wired to a different contact on the other side. For instance, in a particular rotor the 1st contact on one side of the rotor might be wired to the 14th contact on the other side, the 2nd one on the first side to the 22nd on the other, and so forth. Each rotor in the set supplied with an Enigma was wired differently than the others, and the German military/party models used different rotor wirings than did any of the commercial models.

Inside the machine were three slots (in most variants) into which the rotors could be placed. The rotors were "stacked" in the slots in such a way that the contacts on the "output" side of one rotor were in contact with the "input" contacts on the next. The third rotor in most versions was connected to a reflector (unique to the Enigma family amongst the various rotor machines designed in the period) which was hard wired to feed outputs of the third rotor back into different contacts of the third rotor, thence back to the first rotor, but by a different route. In the picture you can see the three stacked rotors at the very top of the machine, with teeth protruding from the panel surface which allow the rotors to be turned by hand.

When a key was pressed on the keyboard, current from the battery flowed from the switch controlled by that key, say A, into a position on the first rotor. There it would travel through the rotor's internal wiring to, say, the J position on the other side. It would then go into the next rotor, perhaps turned such that the first rotor's J was lined up with the second's X. From there it would travel to the other side of the second rotor, and so on. Because the signal had travelled through the rotors and back, some other letter than A would light in the lamp array – thus substituting one letter for another, the fundamental mechanism in all substitution cypher systems.

Because the rotors changed position (rather like an automobile odometer) with every key press, A might be Q this time, but the next A would be something different, perhaps T. After 26 letters were pressed, a cam on the rotor advanced the rotor in the next slot by one position. The substitution alphabet thus changed with every plaintext letter, and kept changing with every plaintext letter for a very long time.

Better yet, due to the "random" wiring of each rotor, the exact sequence of these substitution alphabets varied depending on the initial position of the rotors, their installed order, and which rotors were installed in the machine. These settings were referred to as the initial settings, and were given out in books once a month (to start with—they became more frequent later on).

The most common versions of the machine were symmetrical in the sense that decipherment works in the same way as encypherment: type in the cyphertext and the sequence of lit lamps will correspond to the plaintext. However, this works only if the decyphering machine has the same configuration (i.e., initial settings) as had the encrypting machine (rotor sequence, wiring, alphabet ring settings, and initial positions); these changed regularly (at first monthly, then weekly, then daily and even more often nearer the end of the War on some networks) and were specified in key schedules distributed to Enigma users.

title: Cryptography/Enigma machine


text:
Cookbook:Braising

Braising (from the French word braiser) is a cooking technique that uses a mixture of dry and wet heats. First, the food is sautéed in a fat, charring it and sealing in flavour. Then the food is simmered slowly with a small amount of liquid which results in tender, flavourful food.

Braising relies on heat, time, and moisture to successfully break down tough connective tissue and collagens in meat. It is an ideal way to cook tougher cuts. Many classic braised dishes such as Coq au Vin are highly-evolved methods of cooking otherwise tough and unpalatable foods. Swissing, stewing and pot-roasting are all braising types.

Most braises follow the same basic steps. The meat or poultry is first browned in hot fat. Aromatic vegetables are sometimes then browned as well. A cooking liquid that often includes an acidic element, such as tomatoes or wine, is added to the pot, which is covered. The dish cooks in relatively low heat in an oven or atop the stove until the meat is fork-tender. Often the cooking liquid is finished to create a sauce or gravy.

A successful braise intermingles the flavors of the foods being cooked and the cooking liquid. Also, the dissolved collagens and gelatins from the meat enrich and add body to the liquid. Braising is economical, as it allows the use of tough and inexpensive cuts, and efficient, as it often employs a single pot to cook an entire meal.

Familiar braised dishes include Murshed, pot roast, beef stew, Swiss steak, chicken cacciatore, goulash, braised tilapia and beef bourguignon, among others. Braising is also used extensively in the cuisines of Asia, particularly Chinese cuisine. Vegetables can also be braised. Glazed carrots are an example of a quick-braise, one which is done for a short period of time.

title: Cookbook:Braising


text:
Cookbook talk:Braising

The initial post was copied and pasted from the "Woman's Institute Library of Cookery Volume 1", found at Project Gutenberg. liblamb 19:55, 16 Jul 2004 (UTC)

 * Original post replaced with entry from Wikipedia due to serious anachronisms in technique. —The preceding unsigned comment was added by Nedhorn (talk • contribs) 2007-03-10T11:32:35.

title: Cookbook talk:Braising


text:
Cookbook:Sautéing

Sautéing is cooking food in a small quantity of fat or oil. When sautéing, a very small amount of oil is placed in a shallow pan, and when it is sufficiently hot, the food is put into it. Foods that are to be sautéed are usually sliced thin or cut into small pieces, and they are sometimes turned frequently during the process of cooking. The term "sauté" is derived from the French word for "jumping", used to describe the action of the food in the pan. Generally the minimum possible amount of oil is used, which differentiates it from shallow-frying.

The term pan-frying is sometimes the English equivalent of sautéing (which is a French word) if only a very small amount of oil is used. Some people consider it a different technique, which uses more fat and takes longer. Stir-frying uses higher temperatures and continual stirring. With modern non-stick pans the amount of oil required can be quite small, or even omitted.

Tips for Proper Technique
While different ingredients will call for variations in this technique, there are some general guidelines to help ensure an ideal outcome.

Mise en place
The first rule is be prepared. If your recipe calls for chopped ingredients in step 12, make sure you have them chopped now. While experienced cooks will successfully chop the next ingredient while the rest are cooking, this is not a path to follow for the inexperienced. For one thing, chopping times for the experienced cook are generally much shorter, so the cooking food doesn't have a chance to burn. For another, the experienced cook can quickly assess whether food is done. A less experienced cook should be much more attentive to the pan to become more familiar with the stages of "doneness".

The pan is hot enough if a few small drops of water flicked from your fingertips vaporise immediately, or if a larger drop of water hisses and floats across the surface of the pan on a cushion of its own steam.

Use the fond
When sautéing cuts of meat, many recipes will call for you to deglaze the pan with a flavorful liquid (e.g. stock, wine, spirits, or even fruit juices). The dark brown bits of meat left behind from the high heat cooking are called "fond" and are as intensely flavored as pan drippings from roasted meats. These should generally be scraped off the bottom of the pan and dissolved into the deglazing liquid. In especially elegant preparations, the pan sauce created is strained to remove the solid bits, leaving only the dissolved flavorings in a smooth sauce.

When using garlic and onion
When sautéing with both onions and garlic, be sure to sauté the onions first until they are clear, then add the garlic, and continue to sauté until it is pale gold. The onion takes longer to cook, thus if both are added at the same time, the garlic will be browned by the time the onion is done, which results in an undesirable dominant pungency. Garlic will add its flavour much more harmoniously when only sautéed to a pale gold.

Recipes that call for sautéing

 * Arroz con Pollo
 * Baked Lamb and Yogurt
 * Black-Eyed Peas and Kale
 * Bulgher Burger
 * Coq au Vin
 * Eggplant and Chickpea Skillet
 * Fiddlehead-Portobello Linguine
 * Low Country Shrimp and Grits
 * Paprika Chicken
 * Pesto
 * Potato-Chickpea Curry
 * Vegetable Pie
 * Egg Rice
 * Spaghetti with Bolognese meat sauce

title: Cookbook:Sautéing


text:
Cookbook talk:Sautéing

The initial post was copied and pasted from the "Woman's Institute Library of Cookery Volume 1", found at Project Gutenberg. liblamb 20:03, 16 Jul 2004 (UTC)

title: Cookbook talk:Sautéing


text:
Cookbook:Frying

Frying is the cooking of food in fat. This takes several forms, from deep-frying, where the food is completely immersed in hot oil, to sautéing where food is cooked in a frying pan where there is only a thin coating of oil. Frying is the fastest way to cook, as it is the most efficient way to transfer heat into the food. Despite using liquid oil, frying is considered to be a dry cooking method as water is not used in the cooking process and ideally the cooking oil will not be absorbed by the food, thus no moisture is added by cooking.

Deep-frying
Deep frying involves fully immersing food in hot oil. It is an extremely fast cooking method, and, despite the use of liquid oil, is best classified as a dry cooking method because it does not involve liquid water.

Shallow-frying
Shallow-frying involves partially submerging food in hot oil. Generally, quite a bit less than the bottom third—and occasionally up to half—of the food will be in oil.

Pan-frying
The term "pan-frying" is a somewhat ambiguous term that can refer either to shallow-frying or sautéing over lower heat with less agitation. Check your specific recipe for clarifying details when possible.

Sautéing
Sautéing is cooking food in a small quantity of fat or oil. When sautéing, a very small amount of oil is placed in a shallow pan, and when it is sufficiently hot, the food is put into it. Foods that are to be sautéed are usually sliced thin or cut into small pieces, and they are sometimes turned frequently during the process of cooking. The term "sauté" is derived from the French word for "jumping", used to describe the action of the food in the pan. Generally the minimum possible amount of oil is used, which differentiates it from shallow-frying.

Stir-frying
Stir-frying involves frying food quickly over very high heat in an oiled pan. While stir-frying, you generally stir continually. A special slope-sided pan called a wok is designed for stir-frying. An open flame heat source such as gas works best when using a wok.

Sweating
To sweat is to cook moist foods over low heat in a small amount of fat, usually in a covered pan or pot. Often used to describe the way aromatic vegetables such as onions, carrots and celery are cooked prior to adding other ingredients. The objective in sweating vegetables is to soften them and release the moisture in them, not to brown them. This release of moisture is how the term "sweat" gets its name. It is also known as butter-steam. Frequently the fat is provided by rendering fat from some fatty meat, such as bacon, which also adds additional flavor.

Related techniques

 * Some frying techniques are accompanied by deglazing, which makes use of the browning that occurs.

Kochbuch/ Techniken/ Braten ספר מתכונים/טיגון Kookboek/Braden

title: Cookbook:Frying


text:
Cookbook talk:Frying

The initial post was copied and pasted from the "Woman's Institute Library of Cookery Volume 1", found at Project Gutenberg. liblamb 20:07, 16 Jul 2004 (UTC)

title: Cookbook talk:Frying


text:
Cookbook talk:Broiling

The initial post was copied and pasted from the "Woman's Institute Library of Cookery Volume 1", found at Project Gutenberg. liblamb 20:09, 16 Jul 2004 (UTC)

European ovens and grilling
I propose to (eventually) change this article to reflect the fact that most European ovens include a grill. Also, grilling is usually considered a healthy option because fat released from the cooking food cannot be reabsorbed. This tends to contradict the article's assertion that it is used to retain the juices of meat. LittlePete 11:27, 27 March 2007 (UTC)

Is there evidence for the searing claim
Given that this post contradicts the long standing advice from many cooks that one should sear a steak at high temperature to retain the juices first not last, is there any reference to back up this interesting claim to do the opposite? IanKloester (discuss • contribs) 22:27, 29 December 2012 (UTC)

title: Cookbook talk:Broiling


text:
Cookbook:Broiling

Broiling or Grilling is the use of radiant heat for cooking, usually called grilling in British and Australian English and broiling in US English. Typically this is done in an electric oven, using only the upper heating element, with the door partially open. Gas ovens often provide a very effective lower drawer for broiling. Gas ovens, in a way analogous to gas ranges, provide a hotter, flame-based heat source that is preferred by most cooks over electric broilers. This is where the term "flame broiled" comes from.

Broiling is used to retain the juices of meat while developing flavor. Broiling does not soften the fibers of tough meat. It is best used for tender meat, including poultry. Broiling is not the most economical way of cooking, and the browning of meat can create carcinogenic (albeit tasty) chemicals.

The food should be exposed to intense heat last, to ensure even cooking and less juice escaping. How does that work? Heat damages surface proteins that keep the juice in. The higher the heat, the more damage. So, contrary to popular belief, searing before cooking through will NOT lock in the juices. The food that is being broiled should be turned just once. Once the outside is browned, the heat may need to be reduced to ensure that the center will cook before the outside burns.

title: Cookbook:Broiling


text:
Cookbook:Sunshine Cake

| Dessert | Cake

Nothing more delicious in the way of cake can be made than sunshine cake. It is especially nice to serve with a frozen dessert of some kind, for it is not too rich and it is attractive in color.

Ingredients

 * 6 eggs, separated
 * ⅓ tsp cream of tartar
 * 1 cup white granulated sugar
 * ¾ cup flour
 * 1 tsp lemon juice
 * 1 tsp vanilla

Procedure

 * 1) Whip the yolks with a rotary beater until they are thick and lemon-colored.
 * 2) Whip the egg whites until they are foamy, add the cream of tartar, and continue whipping until they are dry.
 * 3) Fold the sugar into the egg whites, then then fold the yolks into this mixture.
 * 4) Sift the flour several times and add it.
 * 5) Add the lemon juice and vanilla.
 * 6) Pour batter into a sponge-cake pan, and bake.

Notes, tips, and variations

 * Original source is

title: Cookbook:Sunshine Cake


text:
User:Canscorch

Pages I've been helping to maintain
America's Army: Special Forces Community Tactics Guide

Ways to contact Canscorch
Private message me on the America's Army Forums as canscorch.

Private message me on ArmyOps-Tracker as canscorch.

Use Xfire. My Xfire ID is canscorch as well (no suprise).

Messages
1. I think cohesive is a good thing. If you have any ideas, go right ahead and implement them. In the future, if you want to contact me, my email account is a lot faster. Good work.

title: User:Canscorch


text:
A History of Japan: From Mythology to Nationhood

Table of Contents

 * 1) Introduction
 * 2) Prehistory through the Jomon Period
 * 3) The Yayoi Period
 * 4) The Kofun or Yamato Period
 * 5) The Asuka Period
 * 6) The Nara Period
 * 7) The Spread of Buddhism in Japan
 * 8) The Early Heian Period
 * 9) The Middle Heian Period
 * 10) The Late Heian Period
 * 11) The Kamakura Period
 * 12) The Kemmu Restoration
 * 13) The Nanboku-chō Period
 * 14) The Muromachi Period
 * 15) The Warring States Period
 * 16) The Azuchi–Momoyama Period
 * 17) The Edo Period
 * 18) The Meiji Restoration
 * 19) The Meiji Period
 * 20) The Taisho Period
 * 21) The Rise of Militarism
 * 22) World War II
 * 23) The American Occupation of Japan
 * 24) Post-War Japan
 * 25) Japan Today
 * Further Reading
 * Structure

日本史 일본의 역사 日本历史


text:
Talk:A History of Japan: From Mythology to Nationhood

Renamed Pages
I have moved pages to the state they used to be in as the book was nearing completion until everything was moved around and made unreadable.


text:
User talk:Berni~enwikibooks

Re: Bronstein
Na wenn der Bronstein kein Mathe-Buch ist dann weiss ich's ja auch nicht ;) Zumindest unsere Profs bläuen uns ein, dass das quasi unsere Bibel sein muss ...

LaTeX-Wörterbuch
Bist Du Administrator? Könntest Du automatisch LaTeX-Wörterbuch:_makeindex ins deutsche wikibooks übertragen? Oder hilft da nur Handarbeit? Gruß, Ciciban 09:20, 2 Sep 2004 (UTC)

Image copyright problem with Image:Pyth.png
Thanks for uploading Image:Pyth.png. However, the image may soon be deleted unless we can determine the copyright holder and copyright status. The Wikimedia Foundation is very careful about the images included in Wikibooks because of copyright law (see Wikibooks' Copyright policy).

The copyright holder is usually the creator, the creator's employer, or the last person who was transferred ownership rights. Copyright information on images is signified using copyright templates. The three basic license types on Wikibooks are open content, public domain, and fair use. Find the appropriate template in Image copyright tags and place it on the image page like this:.

Please signify the copyright information on any other images you have uploaded or will upload. Remember that images without this important information or giving false information can be deleted by an administrator. If you have any questions, feel free to contact me, or ask them at the Study help desk. Thank you. MichaelFrey 14:08, 24 June 2006 (UTC)

(Look here, same on http://de.wikibooks.org/wiki/Benutzer_Diskussion:Berni)

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 Berni. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Berni~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:02, 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) 04:38, 19 April 2015 (UTC)

title: User talk:Berni~enwikibooks


text:
Learning the vi Editor/vile

Overview
vile is a vi clone which doesn't claim to be a vi clone. The idea behind vile is to have an editor which works similar to vi but provides features for editing multiple files in multiple window-areas like emacs. In fact, vile development started by using MicroEMACS as the base, and not a vi clone, and also not full blown Emacs. MicroEMACS is an emacs-like editor (MicroEMACS's author didn't like full-blown emacs, and the vile authors didn't like (Micro)EMACS mode-less way of working). So vile was developed.

vile provides the most common vi commands (as used by their authors), but not all vi commands. The implemented commands are supposed to work more or less like the original vi commands. The window management and buffer management came from MicroEMACS.

Much work has gone into the vile documentation after the first versions were almost undocumented. It is recommended to consult the documentation to find out the differences and extensions of vile, compared to vi.

Resources

 * vile
 * MicroEMACS

title: Learning the vi Editor/vile


text:
Van Dwelling/Source List

Van dwelling resources on the web:

 * Vandwelling Yahoo Group - The archives of this mailing list is probably the best resource on the web.
 * Vanabode - travel, camp and live forever on $20 a day
 * Mr. Sharkey's Housetrucks -- Nifty housetrucks, housebuses. Lots of pictures and design ideas.
 * Roger Beck's Housetrucks.com -- Website of Roger Beck, author of Some Turtles Have Nice Shells, a picture book of housetrucks, and housebuses.
 * Bus to RV Conversions -- Lots of books for converting a bus to a housetruck/RV.
 * del.icio.us vandwelling tags -- del.icio.us community bookmarks to resources of interest to vandwellers
 * Hoopty Life -- A first person guide and blog about successful living as a full-time van dweller.
 * Car Living -- A guide to living in vans and cars from Australia with tutorials on how to install a dual battery system, how to cook on your car engine and how to wardrive.
 * Vandogtraveller – From Van to Home DIY van conversion ebook -- How I made an old rusty van into my off-grid home for living and travelling in full time
 * Keith’s Schoolbus Conversion Blog -- a blog on converting a schoolbus to a RV
 * Jake's School Bus Conversion Project: tips on installing a bathroom and kitchen into a schoolbus -- including a toilet and propane stove.
 * School Bus Conversion Website
 * NomadLife.wiki - gathering information for van dwellers and other nomads living on the road

title: Van Dwelling/Source List


text:
Cocoa Programming

If you are a beginner, please consider Programming Mac OS X with Cocoa for Beginners

About Cocoa
Cocoa is the name Apple Computer uses for their extended implementation of the OpenStep specification, first created by NeXT for their OPENSTEP operating system. It provides a useful set of tools to help developers create programs and user interfaces within Mac OS X. There are three implementations of the OpenStep specification, the one originally provided with the OPENSTEP operating system, but the most common ones today are the one provided by Apple, and the other by GNUstep, a free software implementation of OpenStep.

If you don't have access to an Apple Macintosh, and you would like to learn how to use the OPENSTEP frameworks, then running GNUstep is worth a consideration (and should be sufficient to let you experience the power of the OPENSTEP frameworks).

Getting ready to program
If you are using an Apple Macintosh computer running Mac OS 10.2 or later (the latest version of Mac OS X is recommended) then you can find all the tools needed to develop Cocoa programs on the last software install CD. The tools are also available from Apple's Developer's Website. In order to download them, you need to create a free account and login. You can also find them in the "Installers" folder of your "Applications" folder (they could be outdated, make sure you run software update after the installation). The two programs you will use most extensively are Xcode (known as Project Builder in versions before 10.3) and Interface Builder.

If you are using GNUstep then you may already have the tools installed. The programs you will need to complete most of the tutorials in this book are ProjectCenter and Gorm. You will need to refer to the GNUstep website for help installing these.

Before starting any of the modules that make up this book you should have a good, basic knowledge of the C programming language. C will help you understand programming in general.

It would be advantageous for you to learn Objective-C as well, as it is the core language for developing Cocoa applications, and may help to assist in understanding the machinery behind Cocoa applications. Learning Objective-C while learning Cocoa is also possible.

Modules

 * First steps
 * Objective-C basics
 * Memory management
 * Foundation Kit
 * Application Kit
 * Basics
 * Commonly used items:
 * Cocoa Programming/sheets
 * Cocoa Programming/toolbars
 * Cocoa Programming/drawers
 * Cocoa Programming/progress indicators
 * Cocoa Programming/preferences
 * status items
 * Cocoa Programming/dock menus
 * Cocoa Programming/wrapping command line tools
 * multithreading
 * Cocoa Programming/vector drawings
 * Cocoa Programming/OpenGL
 * Cocoa Programming/Web Kit
 * Cocoa Programming/web content

Cocoa

title: Cocoa Programming


text:
User talk:João Jerónimo~enwikibooks

Oi João, bemvindo, prazer! Podes assinar com e com data assim ~. Get-back-world-respect 00:27, 18 Jul 2004 (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 João Jerónimo. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name João Jerónimo~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:18, 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:06, 19 April 2015 (UTC)

title: User talk:João Jerónimo~enwikibooks


text: File:Cocoa project type.png

title: File:Cocoa project type.png


text: File:Cocoa application name.png

title: File:Cocoa application name.png


text: File:Cocoa first steps nib selected.png

title: File:Cocoa first steps nib selected.png


text:
Cocoa Programming/First steps

This module will walk you through the process of creating your first Cocoa application.

This module is intended to help you become comfortable with the basics of the tools you will be using and will not go into great detail about them.

The application you will write will take two numbers entered by the user via a graphical user interface and will multiply them together. The product of the two numbers will be sent to the graphical user interface.

Starting
The first thing you need to do is start Xcode. Xcode should be located in /Developer/Applications (the Applications folder inside the Developer folder on your hard-drive). We'll be using Xcode a lot in coming modules so you might like to add it to your Dock now.

Launch Xcode by double clicking its icon.

Creating a project
Once Xcode has started you are ready to create your project.

From the file menu choose "New Project". The following dialog box will appear.

Select "Cocoa Application" and click "Next". A dialog box will appear asking you to name your project.

Call your project "Multiply" and click "Finish". Xcode will then create your project and set up some starting files for you. Once this is done the following window should appear and we are ready to get started.

Building the Interface
Since your application is going to be quite simple you can jump right in and build the user interface! Click the small arrow next to "NIB files" and double click on "MainMenu.nib". This will start Interface Builder, a helpful program that you use to assemble graphical user interfaces. Once Interface Builder has started you will have windows similar to the following on your screen. Don't worry if the windows look slightly different or are positioned differently.

The first thing your interface needs is a way for the user to enter the two numbers to multiply. A basic textbox is appropriate for this purpose. Click on the "Cocoa-Text" tab of the interface elements palette. From this tab you should drag a basic text box onto the applications window. When dragging interface elements around dotted blue lines will sometimes appear. These lines help you position elements according to the Apple Human Interface guidelines. Position the textbox near the top left of the window as shown in the next diagram.

Once the first textbox is in position you should add another to hold the second number that will be entered by the user and a third to hold the product. Your window should look something like the following.

Right now your window has nothing to explain to the user what it does! It needs some labels. From the interface elements palette drag a label into your applications window (the label element is the one that says "System Font Text"). Once this is in your window double click it and change it to read "x" drag its right border as far left as it can go and place it between the first two textfields. Create another label that reads "=" and place it between the last two text fields. Your application should now look something like the following.

Now your application needs a way to activate the multiplication. Choose the "Cocoa-Controls" tab of the interface elements palette and drag a button into your applications window. place it below the right textfield. Double click the button and change its text to read "Calculate". Since this is the last item we will be adding to our interface you might like to also resize the window so that it doesn't have so much extra space. Your window should now look something like the following.

But how do these items work together? At the moment the textfields and button aren't connected in any way. We will connect them to an controller object that we shall now create. Click on the "Classes" tab of the "MainMenu.nib" window and choose "NSObject" (it's all the way to the left). With NSObject selected choose "Subclass NSObject" from the "Classes" menu.

Call the new class "MultiplyController". With the new MultiplyController selected choose "Instantiate MultiplyController" from the "Classes" Menu. This will create an instance of the class to which we can connect interface elements.

Now when you look at the "Instances" tab of the "MainMenu.nib" window you will see the instance of the MultiplyController class. Before we can connect the interface elements to the controller we have to give the controller outlets and actions. Outlets are connections to interface elements e.g. textfields and actions are methods that that can be called by interface elements e.g. when a button is pressed.

Click on "MultiplyController" in the "Classes" tab and then choose "Show Info" (or "Show Inspector" if you are running Tiger) from the "Tools" menu. Click the "Outlets" tab of the Info window then click "Add". Call the new outlet "firstNumber". Add two more outlets called "secondNumber" and "product".

In the "Actions" tab click "Add" and call the new action "Multiply".

Now you need to connect all the parts up. To do this you need to click on the "Instances" tab of the "MainMenu.nib" window. Then hold down control on your keyboard and drag from the instance of "MultiplyController" to the first textfield in your application window. A blue line will appear showing the connection you are making. Once you have reached the first textfield stop dragging and the info window will show you the possible outlets to connect. Choose "firstNumber" and then click "Connect". The screenshot shows the situation just after the connection has been made, hence the button in the inspector window now shows "disconnect", and there is a ball next to the firstNumber outlet showing that it is the target of the connection illustrated by the illustration on the left.

Do the same for the "secondNumber" outlet and the second textfield. And finally connect the right textfield to the "product" outlet. Now we need to connect up the "Calculate" button to the multiply action of MultiplyController. This is also done by control+dragging but this time you start at the button and drag to the class instance. This is because this the message to do the multiplication needs to flow from the button to the controller.

Now that you have your actions and outlets hooked up you can save your work in Interface Builder. But before you leave Interface Builder there is one more thing you should do. Select "MultiplyController" in the "Classes" tab of the "Main Menu.nib" window. and then choose "Create Files for MultiplyController" from the "Classes" menu.

In the sheet which appears you should make sure the both "MultiplyController.h" and "MultiplyController.m" are checked then click "Choose"

You can then save any changes you have made and quit Interface Builder.

Writing the code
With the interface now completed you can write the code for the MultiplyController class. Make sure you have Xcode selected and click "Other Sources". The sources for your application will now be displayed on the right. Double click on "MultiplyController.m" to open it for editing.

Currently its contents are: @implementation MultiplyController - (IBAction)multiply:(id)sender { } @end If you don't understand this then you might need to read through Programming:Objective-C.
 * 1) import "MultiplyController.h"

What we need is for the "multiply:" method to get the two numbers, multiply them together, and place the product in the result textfield. To do this change the method to the following.

- (IBAction)multiply:(id)sender {    [product setIntValue:[firstNumber intValue] * [secondNumber intValue]]; }

If you understand Objective-C this should make sense to you. If not you should read Programming:Objective-C.

Save "MultiplyController.m" and close it. Choose "Build and Run" from the "Build" menu. Assuming you didn't make any errors the application should run. Type in some numbers and press calculate.

Exercises

 * 1) Currently the multiply application works with integers. Modify the code so that it works with floats.
 * 2) Modify the interface to make the application update when you change the contents of one of the text boxes.

title: Cocoa Programming/First steps


text: File:Cocoa first steps interface builder.png


text: File:Cocoa first steps nstextbox construction.png


text: File:Cocoa first steps textfields.png

title: File:Cocoa first steps textfields.png


text: File:Cocoa first steps labled text fields.png


text: File:Cocoa first steps complete window.png


text: File:Cocoa first steps subclass nsobject.png


text: File:Cocoa first steps instantiate multiplycontroller.png


text: File:Cocoa first steps adding outlets.png


text: File:Cocoa first steps adding actions.png


text:
User:Bodo Thiesen

Du suchst bestimmt den hier: http://www.wikiservice.at/support/wiki.cgi?BodoThiesen

title: User:Bodo Thiesen


text: File:Cocoa basics connecting outlets.png


text:
Cookbook:Tater Tot Casserole

| Meat Recipes | Midwestern U.S. cuisine

Tater tot casserole is another easy and tasty casserole.

Ingredients

 * 1–2 pounds (0.45–0.91 kg) ground beef
 * 1 can cream of mushroom soup or cream of chicken soup
 * ½ bag of tater tots (approximately)

Procedure

 * 1) Brown hamburger and drain.
 * 2) Mix in cream of mushroom or cream of chicken soup.
 * 3) Put mixture in casserole dish and cover the top with one layer of tater tots.
 * 4) Bake at 350 F for 1 hour or until done.

Notes, tips, and variations

 * Try adding peas or other vegetables.
 * A can of cheddar cheese soup is also a great way to make a meaty, cheesy casserole!
 * Shortly before the dish is ready, sprinkle the top with some grated cheddar cheese also.

title: Cookbook:Tater Tot Casserole


text: File:Cocoa first steps connecting action.png


text: File:Cocoa first steps create files for controller.png


text: File:Cocoa first steps created files for controller.png


text:
Cookbook:Brownies

Brownies are a type of chocolate bar cookie, though they may also be classified as cakes. They usually have a dry and somewhat crispy top layer with a soft and sometimes gooey body (often classified as being either "fudgy" or "cakey", depending on consistency). Chocolate chips and nuts are often added to the main recipes, depending upon taste.

title: Cookbook:Brownies


text: File:Cocoa first steps running multiply.png


text: User:Migue1 angel

title: User:Migue1 angel


text:
Serial Programming/Serial Linux

Scope
This page is about the classic Unix C APIs for controlling serial devices. Languages other than C might provide appropriate wrappers to these APIs which look similar, or come with their own abstraction (e.g. Java). Nevertheless, these APIs are the lowest level of abstraction one can find for serial I/O in Unix. And, in fact they are also the highest abstraction in C on standard Unix. Some Unix versions ship additional vendor-specific proprietary high-level APIs. These APIs are not discussed here.

Actual implementations of classic Unix serial APIs do vary in practice, due to the different versions of Unix and its clones, like Linux. Therefore, this module just provides a general outline. It is highly recommended that you study a particular Unix version's manual (man pages) when programming for a serial device in Unix. The relevant man pages are not too great a read, but they are usually complete in their listing of options and parameters. Together with this overview it should be possible to implement programs doing serial I/O under Unix.

Basics
Linux, or any Unix, is a multi-user, multi-tasking operating system. As such, programs usually don't, and are usually not allowed to, access hardware resources like serial UARTs directly. Instead, the operating system provides

 * 1) low-level drivers for mapping the device into the file system (/dev and/or /device/ file system entries),
 * 2) the standard system calls for opening, reading, writing, and closing the device, and
 * 3) the standard system call for controlling a device, and/or
 * 4) high-level C libraries for controlling the device.

The low-level driver not only maps the device into the file system with the help of the kernel, it also encapsulates the particular hardware. The user often does not even know or care what type of UART is in use.

Classic Unix systems often provide two different device nodes (or minor numbers) for serial I/O hardware. These provide access to the same physical device via two different names in the /dev hierarchy. Which node is used affects how certain serial control signals, such as DCD (data carrier detect), are handled when the device is opened. In some cases this can be changed programmatically, making the difference largely irrelevant. As a consequence, Linux only provides the different devices for legacy programs.

Device names in the file system can vary, even on the same Unix system, as they are simply aliases. The important parts of a device name (such as in /dev) are the major and minor numbers. The major number distinguishes a serial port, for example, from a keyboard driver, and is used to select the correct driver in the kernel. Note that the major number differs between different Unix systems. The minor number is interpreted by the device driver itself. For serial device drivers, it is typically used to detect which physical interface to use. Sometimes, the minor number will also be used by the device driver to determine the DCD behavior or the hardware flow control signals to be used.

The typical (but not standardized, see above) device names under Unix for serial interfaces are:

 * /dev/ttyxxx
 * Normal, generic access to the device. Used for terminal and other serial communication (originally for teletypes). More recently, they are also used in modem communication, for example, whereas the /dev/cuaxxx was used on older systems.
 * See the following module on how terminal I/O and serial I/O relate on Unix.

 * /dev/cuaxxx
 * Legacy device driver with special DCD handling. Typically this was used for accessing a modem on old Unix systems, such as running the UUCP communication protocol over the serial line and the modem. The cu in the name stands for the program. The a for ACU (automatic call unit).

The xxx part in the names above is typically a one or two digit number, or a lowercase letter, starting at 'a' for the first interface.

PC-based Unix systems often mimic the DOS/Windows naming for the devices and call them /dev/comxxx. Linux system generally call serial ports /dev/ttySxxx instead.

To summarize, when programming for the serial interface of a Unix system it is highly advisable to provide complete configuration for the device name. Not even the typical /dev path should be hard coded.

Note, devices with the name <tt>/dev/ptyxxx</tt> are pseudo terminal devices, typically used by a graphical user interface to provide a terminal emulator like xterm or dtterm with a "terminal" device, and to provide a terminal device for network logins. There is no serial hardware behind these device drivers.

Basics
Serial I/O under Unix is implemented as part of the terminal I/O capabilities of Unix. And the terminal I/O capabilities of Unix were originally the typewriter/teletype capabilities. Terminal I/O is not limited to terminals, though. The terminal I/O API is used for communication with many serial devices other than terminals, such as modems and printers.

The terminal API itself has evolved over time. These days three terminal APIs are still used in Unix programs and can be found in recent Unix implementations. A fourth one, the very old one from Unix Version 6 exists, but is quite rare these days.

The three common ones are:

 * V7, 4BSD, XENIX style device-specific ioctl-based API,
 * 1) An old one called termio
 * 2) A newer one (although still already a few decades old), which is called termios (note the additional 's').

The newer <tt>termios</tt> API is based on the older <tt>termio</tt> API, and so the two <tt>termio...</tt> APIs share a lot of similarities. The <tt>termios</tt> API has also undergone changes since inception. For example, the method of specifying the baud rate has changed from using pre-defined constants to a more relaxed schema (the constants can still be used as well on most implementations). Systems that support the newer <tt>termios</tt> often also support the older <tt>termio</tt> API, either by providing it in addition, or by providing a <tt>termios</tt> implementation with data structures which can be used in place of the <tt>termio</tt> data structures and work as <tt>termio</tt>. These systems also often just provide one man page under the older name termio(7) which is then in fact the <tt>termios</tt> man page, too.

In addition, some systems provide other, similar APIs, either in addition or as a replacement. <tt>termiox</tt> is such an API, which is largely compatible with <tt>termio</tt> and adds some extensions to it taken from <tt>termios</tt>. So <tt>termiox</tt> can logically be seen as an intermediate step between <tt>termio</tt> and <tt>termios</tt>.

The terminal I/O APIs rely on the standard system calls for reading and writing data. They don't provide their own reading/writing functions. Reading and writing data is done via the read(2) and write(2) system calls. The terminal I/O APIs just add functions for controlling and configuring the device. Most of this happens via the ioctl(2) system call.

Unfortunately, whichever of the standard APIs is used, one fact holds for all of them: They are a slight mess. Well, not really. Communication with terminals was and is a difficult issue, and the APIs reflect these difficulties. But due to the fact that one can do "everything" with the APIs, it is overwhelming when one "just" wants to do some serial communication. So why is there no separate serial-I/O-only API in Unix? There are probably two reasons for this:

 * 1) Terminals/teletypes were the first, and apparently very important, serial devices which were connected to Unix. So that API was created first.
 * 2) Once the API was there, there was no need to create a separate one for serial I/O only, since a large part of terminal I/O is serial I/O, and all needed features were already there in the terminal I/O API.

So which API should one use? There is one good reason to use the old V7 API. It is the simplest among the APIs - after going through some initialization woes on modern Unix systems. In general, however, the newer <tt>termios</tt> API makes the most sense, although it is the most complex one.

Line Discipline
When programming serial interfaces on Unix, there is one phrase - line discipline - which can drive programmers crazy. The line discipline provides the hardware-independent interface for the communication between the computer and the terminal device. It handles such things as editing, job control, and special character interpretation, and performs transformations on the incoming and outgoing data.

This is useful for terminal communication (e.g. when a backspace character should erase the latest character from the send buffer before it goes over the wire, or when different end-of-line character sequences between the terminal and the computer need to be converted). These features are, however, hardly useful when communicating with the plethora of other serial devices, where unaltered data communication is desired.

Much of the serial programming in Unix is hitting the line discipline which is in use over the head so it doesn't touch the data. Monitoring what actually goes over the wire is a good idea.

Unix V6/PWB
Unix Bell Version 6 with the programmer's workbench (PWB) was released in 1975 to universities. It was the first Unix with an audience outside AT&T. It already had a terminal programming API. Actually, at that point it was the typewriter API. That API is not described here in depth.

The usage of this API can in theory be identified by the presence of the following signature in some source code:

In theory, because at that time the C language was still a little bit different.

is supposed to point to a

structure. That structure later became  in Unix V7. Finding the V6 API in source code should be rare. Anyhow, recent Unix versions and clones typically don't support this API any more.

Unix V7
See Serial Programming:Unix/V7

termios
is the API that is in general recommended for serial I/O in Unix. A simple terminal program with  can look like it follows. Please note this program is not intended as a general framework for own programs. It lacks error handling, doesn't buffer data, and uses very inefficient polling, wasting lot of CPU cycles. The program just demonstrates some basics for serial I/O: See Serial_Programming:Unix/termios

termio / ioctl(2)
See Serial Programming:Unix/termio

Introduction
It is possible to do serial I/O on the Unix command line. However, the available control is limited. Reading and writing data can be done with the shell I/O redirections like <, >, and |. Setting basic configuration, like the baud rate, can be done with the <tt>stty</tt> (set terminal type) command.

There is also <tt>libserial</tt> for Linux. It's a simple C++ class which hides some of the complexity of termios.

Configuration with <tt>stty</tt>
The Unix command <tt>stty</tt> allows one to configure a "terminal". Since all serial I/O under Unix is done via terminal I/O, it should be no surprise that stty can also be used to configure serial lines. Indeed, the options and parameters which can be set via stty often have a 1:1 mapping to termio/termios. If the explanations regarding an option in the stty(1) man page is not sufficient, looking up the option in the termio/termios man page can often help.

On "modern" (System V) Unix versions, stty changes the parameters of its current standard input. On older systems, stty changes the parameters of its current standard output. We assume a modern Unix is in use here. So, to change the settings of a particular serial interface, its device name must be provided to stty via an I/O redirect:

stty parameters < /dev/com0 # change setting of /dev/com0

On some systems, the settings done by stty are reverted to system defaults as soon as the device is closed again. This closing is done by the shell as soon as the <tt>stty parameters < /dev/com0</tt> command has finished. So when using the above command, the changes will only be in effect for a few milliseconds.

One way to keep the device open for the duration of the communication is to start the whole communication in a sub shell (using, for example, '( ... )'), and redirecting that input. So to send the string "ATI0" over the serial line, one could use:

( stty parameters  echo "ATI0" ) < /dev/com0 > /dev/com0 Interweaving sending and receiving data is difficult from the command line. Two processes are needed; one reading from the device, and the other writing to the device. This makes it difficult to coordinate commands sent with the responses received. Some extensive shell scripting might be needed to manage this.

A common way to organize the two processes is to put the reading process in the background, and let the writing process continue to run in the foreground. For example, the following script configures the device and starts a background process for copying all received data from the serial device to standard output. Then it starts writing commands to the device:

( stty parameters; cat; )& < /dev/com0 bgPid=$? while read cmd; do   echo "$cmd" done >/dev/com0
 * 1) Set up device and read from it.
 * 2) Capture PID of background process so it is possible
 * 3) to terminate background process once writing is done
 * 4) TODO: Also set up a trap in case script is killed
 * 5)       or crashes.
 * 1) Read commands from user, send them to device

kill $bgPid
 * 1) Terminate background read process

If there is a chance that a response to some command might never come, and if there is no other way to terminate the process, it is advisable to set up a timeout by using the alarm signal and  that signal (signal 14), or simply kill the process:

trap timeout 14 timeout { echo "timeout occurred" } pid=$$ ( sleep 60 ; kill -14 $pid; )& # send alarm signal after 60 sec. or pid=$$ ( sleep 60; kill -9 $pid;)& # brutally kill process after 60 sec.
 * 1) normal script contents goes here
 * 1) normal script contents goes here

Overview
It is possible to provide a serial line with a default configuration. On classic Unix this is done with entries in the <tt>/etc/ttytab</tt> configuration file, on newer (System V R4) systems with <tt>/etc/ttydefs</tt>.

The default configurations make some sense when they are used for setting up terminal lines or dialup lines for a Unix system (and that's what they are for). However, such default configurations are not of much use when doing some serial communication with some other device. The correct function of the communication program should better not depend on some operating system configuration. Instead, the application should be self-contained and configure the device as needed by it.

<tt>/etc/ttytab</tt>
The ttytab format varies from Unix to Unix, so checking the corresponding man page is a good idea. If the device is not intended for a terminal (no login), then the getty field (sometimes also called the program field, usually the 3rd field) for the device entry should be empty. The init field (often the 4th field) can contain an initialization command. Using <tt>stty</tt> here is a good idea. So, a typical entry for a serial line might look like:

# Device   TermType    Getty   Init tty0       unknown     ""      "stty parameters"

<tt>/etc/ttydefs</tt>
Just some hints:

<tt>/etc/ttydefs</tt> provides the configuration as used by the ttymon program. The settings are similar to the settings possible with stty.

<tt>ttymon</tt> is a program which is typically run under control of the Service Access Controller (SAC), as part of the Service Access Facility (SAF).

TODO: Provide info to set up all the sac/sacadm junk.

<tt>/etc/serial.conf</tt>
Just some hints:

A Linux-specific way of configuring serial devices using the setserial program.

<tt>tty</tt>
tty with the -s option can be used to test if a device is a terminal (supports the termio/termios ioctl's). Therefore it can also be used to check if a given file name is indeed a device name of a serial line.

echo -e "Enter serial device name: \c" read dev if tty -s < "$dev"; then echo "$dev is indeed a serial device." else echo "$dev is not a serial device." fi

<tt>tip</tt>
It is a simple program for establishing a terminal connection with a remote system over a serial line. <tt>tip</tt> takes the necessary communication parameters, including the parameters for the serial communication, from a tip-specific configuration file. Details can be found in the <tt>tip</tt>(1) manual page.

Example:

To start the session over the first serial interface (here <tt>ttya</tt>):

tip -9600 /dev/ttya

To leave the session:

~.

Overview
Uucp (Unix-to-Unix-Copy) is a set of programs for moving data over serial lines/modems between Unix computers. Before the rise of the Internet uucp was the heart and foundation of services like e-mail and Usenet (net news) between Unix computers. Today uucp is largely insignificant. However, it is still a good choice if two or more Unix systems should be connected via serial lines/modems.

The uucp suite also contains command line tools for login over a serial line (or another UUCP bearer to a remote system. These tools are <tt>cu</tt> and <tt>ct</tt>. They are e.g. useful when trying to access a device connected via a serial line and when debugging some serial line protocol.

<tt>cu</tt>
<tt>cu</tt> "call another UNIX system", does what the name implies. Only, that the other system does not have to be a UNIX system at all. It just sets up a serial connection, possibly by dialing via a modem.

<tt>cu</tt> is the oldest Unix program for serial communication. It's the reason why some serial devices on classic Unix systems are called something like <tt>/dev/cul0</tt> and <tt>/dev/cua0</tt>. Where cu of course stands for the <tt>cu</tt> program supposed to use the devices, l stands for line - the communication line, and a for acu (automatic call unit).

<tt>ct</tt>
<tt>ct</tt> is intended to spawn a login to a remote system over a modem line, serial line, or similar bearer. It uses the uucp devices list to find the necessary dialing (modem) commands, and the serial line settings.

System Configuration
inittab, ttytab, SAF configuration

title: Serial Programming/Serial Linux


text:
Template:Serial Programming

Serial Programming: Introduction and OSI Network Model -- RS-232 Wiring and Connections -- Typical RS232 Hardware Configuration -- 8250 UART -- DOS -- MAX232 Driver/Receiver Family -- TAPI Communications In Windows -- Linux and Unix -- Java -- Hayes-compatible Modems and AT Commands -- Universal Serial Bus (USB) -- Forming Data Packets -- Error Correction Methods -- Two Way Communication -- Packet Recovery Methods -- Serial Data Networks -- Practical Application Development -- IP Over Serial Connections

title: Template:Serial Programming


text:
User:Caton

 * Wiki sur Nietzsche

title: User:Caton


text:
User:Philipendula

Links

 * Mathematik:Stochastik
 * Mathematik:Zahlentheorie
 * http://de.wikipedia.org/wiki/Benutzer:Philipendula

Spielwiesen

 * Philipendula:Spielwiese1
 * Philipendula:Spielwiese2
 * Philipendula:Boum

title: User:Philipendula


text:
User:Aaron Einstein~enwikibooks

Hi! I'm Aaron Einstein I'm 13 years old, like to play computer games, like to surf the net, and I'd also wouldn't mind ruling the world someday. I've been around the internet alot And have also used the following other Aliases:

 * Aaron9123 (used on Westwood online)
 * AaronEins (Shattered Galaxy)

Other Wiki-Projects' Profiles of Me

 * Wikipedia
 * Wikisource
 * Wikiquote

My other sites

 * My MSN Spaces Blog

Email
AaronEinstein@sympatico.ca

MSN
Add the contact Alloyd@rogers.com (on often).

AIM
Chat with AaronEins3 (rarely online)

Well I would now tlike to close with saying... something... now I forget! Dang! Thanks alot!... Just kiddin'

-Æ

title: User:Aaron Einstein~enwikibooks


text:
Latin/Words and their Flexion

Stem Flexion

 * 1. Words are called in Grammar the Parts of Speech.
 * Words are either Simple, as flagrare flamma, or Compound as con-flagrare, flamm-i-er
 * Every Word has meaning and form. Form helps to determine meaning.

 * 2. Every Word has a STEM and ROOT.
 * Word and Stem may be (but seldom are) the same, as tu, thou; aqua, water, while Root differs: flamma, flame: Root, flag-, blaze.

 * Root and stem are often the same: ag-ere, to act. Such words are called Radical or Primitive: all others are derivative.

 * A Compound Word has only one Stem, but as many Roots as it has composing parts. Thus the Stem of conflagrare is conflagra, the two Roots, cum and flag-.

 * 3. Every true element in a word following the Root is called a SUFFIX.
 * Thus in flamma (for flag-ma) –ma is a Suffix; in flagrare, -r, -a and –re and suffixes.

 * Suffixes may need a connecting Link or Vincular, which is not elemental: reg-I-bus, quer-I-monia. The final Suffix, which converts a Stem into a Word, is called an Ending, as –re in flag-r-a-re.  But the Suffix –ma is not called an Ending because flamma is itself a Stem.  When it forms flammas, s is an Ending.

 * 4. A syllable placed before a word to modify its meaning, not being a root word, is called a PREFIX.
 * Thus in te-tend-I and cin-cinnus, te and cin are Prefixes. But particles in composition, as de-, re-, and se- are not Prefixes as having roots of their own.

 * 5. The last letter of a Root, as g in flag is called the Root Character.
 * The last letter of a stem, as a in flamma, is called the Stem Character. The Stem Character, being of chief importance is also known as the Character of the Word.

 * 6. FLEXION, or Stem Flexion is the method of inflecting a stem, that is, of making such changes in its form to indicate changes in its meaning and uses.
 * This is usually done by suffixing a Flexional Ending to the Stem: flagra-re; flamma-rum. Such suffixed endings sometimes need a Vincular, as I in regibus; sometimes they cause a mutation of the stem, as flamm-is for flamma-is (which is for flamma-bus).  Sometimes change in a letter of the Stem itself is an inflection, such as flamm-a (short a) to flamm-a (long a).  Sometimes both Letter-change and Ending are used; ag-, eg-I.  Sometimes Prefix, Letter Change and Ending are used: can-, ce-cin-ci.

 * 7. How then is a Stem defined?
 * A stem is that part of a Word which is virtually contained in every change of form, though the character is often liable to be hidden through the operation of the laws which determine letter change. So the character of flamma is hidden in the form flammis; the character of virgin- is hidden in the form virgo; the character of dirif- is hidden in the form direxi.

 * 8. How then is a Root defined?
 * A Root is the primitive element in any word; that part which the word has in common with all other kindred words. Thus in agito, the Stem is agrita-, but the root is ag-, which it has in common with ag-o, ag-men, and many other kindred words.  The Root-character and Root-vowel are more liable to be in hidden through letter change than even the Stem-character.  Thus the Root ag- is contained in the words action, examen, redigo, but obscured in word by some mutation.

title: Latin/Words and their Flexion