text:
Ada Programming/Input Output

Overview
The standard Ada libraries provide several Input/Output facilities, each one adapted to specific needs. Namely, the language defines the following dedicated packages:
 * Text_IO
 * Sequential_IO
 * Direct_IO
 * Stream_IO

The programmer must choose the adequate package depending on the application needs. For example, the following properties of the data handled by the application should be considered:
 * Data contents: plain text, or binary data?
 * Accessing the data: random access, or sequential access?
 * Medium: data file, console, network/data-bus?
 * Data structure: homogeneous file (sequence of the same data field), heterogeneous file (different data fields)?
 * Data format: adherence to an existing data format, or the application can freely choose a new one?

For example, Stream_IO is very powerful and can handle complex data structures but can be heavier than other packages; Sequential_IO is lean and easy to use but cannot be used by applications requiring random data access; Text_IO can handle just textual data, but it is enough for handling the command-line console.

The following table gives some advices for choosing the more adequate one:

So the most important lesson to learn is choosing the right one. This chapter will describe more in detail these standard packages, explaining how to use them effectively. Besides these Ada-defined packages for general I/O operations each Ada compiler usually has other implementation-defined Input-Output facilities, and there are also other external libraries for specialized I/O needs like XML processing or interfacing with databases.

Text I/O
Text I/O is probably the most used Input/Output package. All data inside the file are represented by human readable text. Text I/O provides support for line and page layout but the standard is free form text.

Main Str  String 1  80 Last Natural AdaText_IOGet_Line Str Last AdaText_IOPut_Line Str 1 Last

This example copies text from standard input to standard output when all lines are shorter than 80 characters, the string length. See package Text I/O how to deal with longer lines.

The package also contains several generic packages for converting numeric and enumeration types to character strings; there are child packages for handling Bounded and Unbounded strings, allowing the programmer to read and write different data types in the same file easily (there are ready-to-use instantiations of these generic packages for the Integer, Float, and Complex types). Finally, the same family of Ada.Text_IO packages (including the several children and instantiation packages) for the type Wide_Character and Wide_Wide_Character.

It is worth noting that the family of Text_IO packages provide some automatic text processing. For example, the Get procedures for numeric and enumeration types ignore white space at the beginning of a line (Get_Line for String does not present this behavior), or adding line and page terminators when closing the file. This is thus adequate for applications handling simple textual data, but users requiring direct management of text (e.g. raw access to the character encoding) must consider other packages like Sequential_IO.

See this tutorial for a longer example of using text I/O in Ada.

Direct I/O
Direct I/O is used for random access files which contain only elements of one specific type. With Direct_IO you can position the file pointer to any element of that type (random access), however you can't freely choose the element type, the element type needs to be a definite subtype.

Sequential I/O
Direct I/O is used for random access files which contain only elements of one specific type. With Sequential_IO it is the other way round: you can choose between definite and indefinite element types but you have to read and write the elements one after the other.

Stream I/O
Stream I/O is the most powerful input/output package which Ada provides. Stream I/O allows you to mix objects from different element types in one sequential file. In order to read/write from/to a stream each type provides a 'Read and 'Write attribute as well as an 'Input and 'Output attribute. These attributes are automatically generated for each type you declare.

The 'Read and 'Write attributes treat the elements as raw data. They are suitable for low level input/output as well as interfacing with other programming languages.

The 'Input and 'Output attributes add additional control information to the file, like for example the 'First and 'Last attributes for an array.

In object orientated programming you can also use the 'Class'Input and 'Class'Output attributes - they will store and recover the actual object type as well.

Stream I/O is also the most flexible input/output package. All I/O attributes can be replaced with user defined functions or procedures using representation clauses and you can provide your own Stream I/O types using flexible object oriented techniques.

Wikibook

 * Ada Programming
 * Ada Programming/Libraries/Ada.Direct_IO
 * Ada Programming/Libraries/Ada.Sequential_IO
 * Ada Programming/Libraries/Ada.Streams
 * Ada Programming/Libraries/Ada.Streams.Stream_IO
 * Ada Programming/Libraries/Ada.Text_IO.Text_Streams
 * Ada Programming/Libraries/Ada.Text_IO
 * Ada Programming/Libraries/Ada.Text_IO.Enumeration_IO (nested package)
 * Ada Programming/Libraries/Ada.Text_IO.Integer_IO (nested package)
 * Ada Programming/Libraries/Ada.Text_IO.Modular_IO (nested package)
 * Ada Programming/Libraries/Ada.Text_IO.Float_IO (nested package)
 * Ada Programming/Libraries/Ada.Text_IO.Fixed_IO (nested package)
 * Ada Programming/Libraries/Ada.Text_IO.Decimal_IO (nested package)
 * Ada Programming/Libraries/Ada.Text_IO.Bounded_IO
 * Ada Programming/Libraries/Ada.Text_IO.Unbounded_IO
 * Ada Programming/Libraries/Ada.Text_IO.Complex_IO (specialized needs annex)
 * Ada Programming/Libraries/Ada.Text_IO.Editing (specialized needs annex)
 * Ada Programming/Libraries/Ada.Integer_Text_IO
 * Ada Programming/Libraries/Ada.Float_Text_IO
 * Ada Programming/Libraries/Ada.Complex_Text_IO (specialized needs annex)
 * Ada Programming/Libraries/Ada.Storage_IO (not a general-purpose I/O package)
 * Ada Programming/Libraries/Ada.IO_Exceptions
 * Ada Programming/Libraries/Ada.Command_Line
 * Ada Programming/Libraries/Ada.Directories
 * Ada Programming/Libraries/Ada.Environment_Variables
 * Ada Programming/Libraries/GNAT.IO (implementation defined)
 * Ada Programming/Libraries/GNAT.IO_Aux (implementation defined)
 * Ada Programming/Libraries/GNAT.Calendar.Time_IO (implementation defined)
 * Ada Programming/Libraries/System.IO (implementation defined)
 * Ada Programming/Libraries
 * Ada Programming/Libraries/GUI
 * Ada Programming/Libraries/Web
 * Ada Programming/Libraries/Database
 * Ada Programming/Platform
 * Ada Programming/Platform/Linux
 * Ada Programming/Platform/Windows

Ada 95 Quality and Style Guide

|InputOutput Programación en Ada/Entrada-salida

title: Ada Programming/Input Output


text:
Cookbook:Calorie

A Calorie or kilocalorie (sometimes kcal, C, Cal or less accurately calorie or cal) is a unit of energy; it is equal to 4185.5 Joules or 3.968 Btu. Calories provide the energy needed for growth and activity.

Decreasing intake
Some people may decrease their caloric intake for health-related reasons or out of a desire for weight loss. Decreasing caloric intake can be done through reducing the overall amount of food one eats, switching to lower-calorie foods, or a combination of both methods.

Increasing intake
Some people may need to increase their caloric intake for short-term energy yield or long-term weight gain.

One can easily increase the calorie content of a dish by adding oil and fat. A tasty way to do this is by frying food; in particular the deep-fat method adds a large amount of fat to food. Oil can also be added to many soups without greatly affecting their taste or texture.

Normally low-calorie foods such as vegetables can be enhanced by adding cheese, salad dressing, and gravy. Fruits can be treated with cream or chocolate. Many snack foods, such as pretzels and crackers, can be dipped in butter or peanut butter.

When increasing caloric intake for a shorter-term jolt of energy (such as for running a race), increased consumption of fats is not recommended. Typically, in the day or two before the needed energy boost, one should consume a larger amount of carbohydrates.

High-calorie recipes

 * Deep Fried Mars Bar
 * French Fries
 * Breaded Fried Oysters
 * Kashkaval Pane
 * Modak
 * Fried Eggs
 * Fried Rice
 * French toast
 * Fried Meatballs
 * Crême anglaise
 * Wiejska

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

title: Cookbook:Calorie


text:
Movie Making Manual/Equipment and software reviews

=Hardware reviews=

Video Cameras

 * http://cnet.com

miniDV, DVCam, DVCpro, DV50

 * Canon XL1-S review

=Software=

There is a large variety of software available, ranging from free solutions such as Windows Movie Maker/iMovie (included with any new PC/Mac), to professional solutions like Adobe Premier Pro (available for Windows and Mac OSX) and Final Cut Pro (Mac OSX only). There is also a number of programs in between: Adobe offers Premier Elements, essentially a stripped down version of Premier Pro, for more basic editing. Apple likewise offers Final Cut Express. If you are building a workstation specifically for editing, you are probably looking at something like Premier Pro. It should be noted that Adobe offers a Production Package that includes a number of titles from the Adobe family, including Premier, AfterEffects, and Photoshop Extended, all of which can be very useful for even more advanced editing than what Premier alone offers.

=Software reviews=

Top 10 Video Editing Software Review http://video-editing-software-review.toptenreviews.com/

/Tools and equipment


text:
Movie Making Manual/Canon XL1-S review

=Pros=
 * Good image quality
 * Interchangable lenses
 * Tried and tested - used in 28 Days Later.

=Cons=
 * The supplied zoom lens has horrible electronic "manual" controls over the zoom and focus - there's no direct mechanical coupling between the rings and the glass. It's pretty tough to zoom smoothly or to focus responsively
 * No XLR mic support
 * No true 16:9
 * No LCD screen
 * Not HDV

title: Movie Making Manual/Canon XL1-S review


text:
OpenOffice.org/Quickstarter

 A quickstarter  is a feature that can be found in the system tray (at the bottom right of the computer, along with the clock etc. (at least on MS Windows Operating Systems). Basically it serves to accelerate the process of starting programs such as OpenOffice.org. In OpenOffice.org it typically reduces the time taken to load the initial document from maybe 50 seconds down to 15 or 20 seconds.

The downside of having it constantly monitoring your computer could be that it uses memory, which on a low cost computer may be better used by other, more crucial, programs. Nevertheless any current operating system has virtual memory support, and programs are swapped to disk when they are inactive. In these cases no resources will be wasted if we have enough swap space.

It is started by default unless you indicate that you do not want the quickstarter feature when you first install the program.

Using and removing the quickstarter
If you right click on the OpenOffice.org logo (the seagull on ocean logo in the system tray) you get a list of options to create new OpenOffice.org documents, or to open a template, you also get an opportunity to open an existing document, of any format. At the bottom you can see options to exit the quick starter, and above it there should be a tick where it asks whether you want to load OpenOffice.org during system startup. If you click to exit the quickstarter, then when you restart the computer the quickstarter will re-appear. To make it go away for good you must click where it asks if you want to load OpenOffice.org during system startup, so that the tick disappears. If you hold the mouse over the quickstarter a piece of text indicates OpenOffice.org, version, and quickstarter. If you left click a box appears offering options to open documents, templates or samples, create new documents, or explore the My Documents folder. This is the best way to take advantage of the features the quickstarter offers.

If you want quickstarter to reappear
Windows: Find the quickstart executable (in a typical Windows install, it would be at C:\Program Files\OpenOffice.org 2.0\program), and launch it.

You should then see an icon in the System Tray. Right click the System Tray icon and select "Load OpenOffice.org During System Start-Up".

title: OpenOffice.org/Quickstarter


text:
Talk:OpenOffice.org/Quickstarter

How to restart closed quickstarter Elaborate on Organize-Brief mention re database

title: Talk:OpenOffice.org/Quickstarter


text:
Talk:Latin/Lesson 6-Pronouns

Untitled
Needs the reflexive pronoun (se--nom., sibi (dat.), as well as the intensive (ipse, etc.)

It's not made quite clear that personal pronouns are only one type of pronoun.

title: Talk:Latin/Lesson 6-Pronouns


text:
Cookbook:Injera (Ethiopian Teff Flatbread)

| Cuisine of Ethiopia Injera is a flatbread eaten in Ethiopia and Eritrea. It is made with teff flour. Teff is a tiny round grain that is grown in the highlands of Eritrea and highlands of Ethiopia. While teff is very nutritious, pure teff flour contains no gluten, and little else in the way of binding proteins. This makes teff ill-suited for making raised bread; however injera still takes advantage of the special properties of fermentation, which gives it an airy, bubbly texture, and also a sour taste.

Ingredients

 * 1 cup teff flour
 * 1½ cups warm but not hot water
 * 1 pinch of salt
 * Oil for frying
 * Fermentation starter (optional; see notes)

Procedure

 * 1) Mix the flour with the water, and the salt. Add your fermentation starter if using one.
 * 2) Set aside to ferment overnight, or at least 12 hours. There should be bubbles on the surface from fermenting, before you use it.
 * 3) Heat a large, flat pan until it is hot enough to make a droplet of water sizzle. Oil it very lightly, just enough to make the pan shine.
 * 4) Pour or ladle some batter onto the pan, spiralling outwards from the centre. Only a thin layer is required—a little thicker than a crêpe but not by much.
 * 5) As it cooks, the surface of the injera will become covered in holes or pits. When the entire injera has changed colour and the edges start to lift from the pan, remove it and set aside, then pour the next injera and repeat until finished.

Notes, tips and variations

 * If you can't get it to ferment by itself, try a good fermentation starter like a teaspoonful of kefir. Baker's yeast alone will not make for good flavour, as bacteria are needed also, but a teaspoonful of yoghurt plus a pinch of yeast might do the trick if you can't get kefir. Note that fermentation starter may contain gluten.
 * Traditional injera is made with teff, but if this is difficult to get, it can be made with sorghum or wheat flour.
 * Since teff is often quite expensive outside of Africa, it is often mixed with wheat flour to give the injera some of the teff flavour but for less expense. Mix ¼ cup of teff flour with ¾ cup of sorghum or wheat flour, for the recipe above.


text:
Cookbook:Basque Cuisine

| European cuisines

Introduction
The Basque Country, or Euskal Herria as it is known to its inhabitants, encompasses three provinces of France and four of Spain. The origins of the Basque people are unknown, but it is likely that they have inhabited the region since prehistoric times.

Like the Basque language, which is distinct from any other known language, Basque cuisine is unique and superb. Its major focus is on fresh, well-prepared dishes using local, seasonal ingredients.

Food is an integral part of Basque culture, so important that gastronomic societies, where men meet to cook, eat and engage in other social activities exist throughout the country.

Dining Customs
Breakfast is a light meal, often accompanied by cafe con leche, or coffee with milk. Dinner, the major meal of the day is usually served at in the mid-afternoon. It often includes soup and several other courses served with wine. Supper is served at 9:00pm and is a lighter meal than dinner.

Basque Cuisine
Basque dishes are not based on elaborate sauces or spice combinations. The excellence of Basque cooking is due to the use of high quality, local ingredients in season, combined with preparation that enhances, rather than masks, the natural flavor of the food. The most important ingredient in Basque cuisine is the fresh ingredient.

The Basque Country borders the Atlantic Bay of Biscay, and its people have a long history of seafaring. Seafood is one of the mainstays of Basque cuisine. Cod, hake and fresh tuna are popular, although more unusual dishes are also served, using bream, elvers or other types of fish and seafood.

Dried beans are another staple of Basque cuisine and are especially common during the winter months. The traditional broad bean has become largely replaced by the haricot bean. Several excellent varieties of beans are grown in the Basque Country, including the Alubias de Tolosa. A variety of other vegetables are used in Basque cuisine including peppers, peas, green beans and potatoes.

Meat, including pork, beef and lamb, as well as poultry and wild game also have their place in Basque cooking. Cured meats such as excellent hams and sausages are produced in the Basque Country.

Other foods common to Basque Cuisine include mushrooms which are very popular, especially in the spring and fall when they are in season and hand-made cheeses from ewe's milk.

Fish and Seafood
Bacalao al Pil-Pil - Cod with Garlic Sauce This popular dish is made from salt-cod in a sauce of garlic and olive oil. The name is said to have been derived the sound of the bubbling oil: "pilpileo". Bacalao a la Vizcaina - Cod in Pepper Sauce A rich dish from salt-cod in a red pepper sauce.

Merluza en Salsa Verde - Hake in Green Sauce A traditional dish made from hake in a sauce that derives it green color from parsley.

Marmitako - Tuna Stew There are many variation of this classic seaman's stew although fresh tuna, potatoes, onions and peppers are usually included. It is named for the pot in which it is cooked, the marmita.

Besugo a la Brasa - Grilled Sea Bream The bream is grilled whole or split open over a charcoal fire. The fish is sometimes sprinkled with vinegar before serving. Txipirones en su Tinta - Squid in their own Ink Squid are prepared in a sauce of onions, peppers, tomato and their own ink, which is toxic until it is cooked.

Vegetable and Legume Dishes
Menestra - Braised Vegetables Traditionally Navarrese, this dish is now served throughout the Basque Country. Especially popular in spring, it consists of a mixture of vegetables which often includes peas, asparagus and artichokes as well as other vegetables. Pimientos de Gernika - Fried Green Peppers A specialty of the Bizkaian region, Gernika peppers, named for the area in which they are grown are lightly fried in olive oil and pressed flat before serving.

Alubias de Tolosa - Beans from Tolosa The dried beans are cooked slowly in an earthenware pot with garlic and olive oil. This dish is usually served with cabbage. The beans of Tolosa are well known and the city of Tolosa holds a bean cook-off each year. Pochas con Codornices - Fresh Haricot Beans with Quail A specialty of Navarre, pochas are beans that are harvested before being completely dried. Besides the beans and quail, tomatoes, a pepper and garlic and are also usually added. The title of the dish always lists the beans first, a symbol of the importance of the beans.

Meats, Cured Meats and Poultry
Chorizo - Sausage A sausage made from pork, fat, paprika, garlic and salt, Chorizo is used in many Basque recipes. Lengua a la Tolosana - Tolosa Tongue Popular in the area of Pasus, this dish consists of calf's tongue simmered in wine and stock with tomatoes and an onion. Jambon de Bayonne - Bayonne Ham The lightly smoked Bayonne ham is a specialty of the area of the Basque Country located within France. Tender and sweet, the ham comes from the Black and White Basque pig. It takes a year to cure the Bayonne ham.

Soups
Porrusalda - Leek Potato Soup One of the traditional Basque soups, Porrusalda is a soup made from leeks and potatoes flavored with garlic. Salt cod is also sometimes added, as are carrots. Porrusalda means "Leek Soup" in the Basque language.

Mushrooms
Revuelto de Zizak - Scrambled Eggs with St George's Mushrooms Zizaks or Perretxikos are highly prized and expensive mushrooms that appear in the spring. They are especially popular in the Province of Alava. This very simple dish, cooked in olive oil and seasoned only with salt and sometimes garlic, enhances the flavor and scent of the Zizaks.

Cheese
Idiazabal - Ewe's Milk Cheese hand-made womans' milk cheeses are produced in the mountains of the Basque Country. One famous Basque cheese, the smoky-flavored Idiazabal, is made from the milk of the ancient Latxa breed of sheep, which evolved in the region.

Drinks
Cider Cider is a popular drink in the Basque Country and is both home-brewed and served in Sidrerías or cider houses. Wine A common wine in the Basque country Txakoli is a young wine that comes in both red and white varieties. Fine wine is produced in the Rioja region in Alava.

title: Cookbook:Basque Cuisine


text:
Slackersbible

This Handbook is based on the work of the FreeBSD Documentation Project Slackware Handbook

Make sure to check the submission queue on that project. It's equally important to verify content as well checking for spelling mistakes. This makes our job easier as well as the jobs of those who will need to revise your work.

Have Fun!!!

Table of Contents

 * 1) About
 * 2) License
 * 3) Preface
 * 4) Getting Started
 * 5) Introduction
 * 6) Installing Slackware Linux
 * 7) UNIX Basics
 * 8) Synopsis
 * 9) Virtual Consoles and Terminals
 * 10) Permissions
 * 11) Processes
 * 12) Text Editing
 * 13) Installing Applications
 * 14) How to compile source code
 * 15) The X Window System
 * 16) Synopsis
 * 17) Common Tasks
 * 18) Desktop Applications
 * 19) Multimedia
 * 20) Synopsis
 * 21) Configuring sound
 * 22) Configuring the Slackware Kernel
 * 23) Configuring your first linux 2.6 kernel
 * 24)  System Administration
 * 25) Configuration and Tuning
 * 26) The Slackware Booting Process
 * 27) Users and Basic Account Management
 * 28) Security
 * 29) SELinux
 * 30) Storage
 * 31) Volume Management
 * 32) Localization
 * 33) The Cutting Edge
 * 34) Software Management
 * 35) Network Communication
 * 36) Appendices

Source
From the MadPenguin Slackware Handbook.

title: Slackersbible


text:
Slackersbible/Preface

Intended Audience
The first section of the Handbook will guide the new user through the installation of Slackware Linux and gently introduces the concepts and conventions that underpin the OS. Working through this section requires little more than the desire to learn and the fortitude to attempt an installation.

The second, far larger, section of the Handbook is a comprehensive reference to all manner of topics of interest to Slackware Linux system administrators. Some of these chapters may recommend that you do some prior reading, and this is noted in the synopsis at the beginning of each chapter.

title: Slackersbible/Preface


text:
Cookbook:Dashi (Japanese Soup Stock)

 * Soup | Cuisine of Japan

Dashi is a broth used to make miso soup. When only kelp (konbu) is used, you get kombu-dashi. This is bland, and appears to be unpopular for use in miso soup. A chunk of kelp about 6 inches across might be reasonable for a quart of broth. When sardines or anchovies are also used, you get niboshi-dashi. This seems to be the most popular choice for making miso soup. You might add a bit of sake in this case. About 10 little fish (guppy-sized) per quart of broth should do. When both kelp (konbu) and bonito flakes (katsuo-bushi) are used, you get katsuobushi-dashi. This appears to be the second most popular choice for making miso soup. About 1 cup of bonito flakes per quart of broth should do. At first you produce primary dashi (ichiban-dashi). This is good for clear soups. If you use the solids a second time, you get secondary dashi (niban-dashi). This is good for thick soups and for cooking vegetables.

Ingredients
Any of the following (to taste):
 * Dried konbu (kelp) seaweed (konbu)
 * Clams (asari or shijimi)
 * Dried bonito flakes (katsuo-bushi)
 * Dried mackerel flakes (sababushi)
 * Dried sardines or anchovies (niboshi)
 * Dried shiittake mushroom mushrooms (hoshi-shiitake)

 * Dried young "flying fishes" (飛魚;tobiuo or あご;ago,unique name to Japanese-oceanside.)

Procedure

 * 1) If using sardines or anchovies, remove the heads and intestines. Discard these, keeping the bodies.
 * 2) Boil fish in water, as if you were making tea.
 * 3) Filter the liquid or scoop the solids out of it. The liquid is your dashi.

Notes, tips, and variations

 * Both kombu and the fish flakes may be found at most reasonably-sized Asian markets or bought cheaply online
 * Katsuobushi is sold in many forms, including small, single-serving packets and in mesh bags to aid removal. An 80 g bag of the flakes will make about 4L of stock.
 * Most cheap restaurants in Japan and abroad use a powdered mix of salt, MSG, and fish-flavour extract from Ajinomoto, the company whose founder discovered MSG and a Knorr-like presence in Japan. This powdered "instant dashi" is also readily available in the places mentioned above. The recipe provided here will provide a less-salty, deeper-flavoured but similar broth.

title: Cookbook:Dashi (Japanese Soup Stock)


text:
Slackersbible/About

The goal of the Slackware Handbook project is to create a document that closely resembles the FreeBSD Handbook in framework and content, but all about Slackware Linux. Envisioned by Narayan Newton and brought to life by Mad Penguin, the Slackware Handbook is unlike any other technical documentation in the world in that it is a completely 'live' medium. This is one book that will never age, never become obsolete, never collect dust... all because it is in perpetual development by dedicated technology professionals from around the globe.

Anyone will be allowed to contribute, but everything submitted to the book is moderated by a peer review system. If something is inaccurate or misleading, it will be caught and fixed. If something is out of date, it will be updated. In keeping with the true nature of Open Source, it will be completely open for anyone to read, download, and share. The Slackware Handbook will prove to be one of the most accurate technical documents on the planet.

title: Slackersbible/About


text:
Slackersbible/Introduction

Slackware is the oldest Linux distribution still in active development. Dating back to 1993, it is still being maintained by its creator Patrick Volkerding with help from developers from all around the world.

It is a very sturdy yet simple distribution, whose main goals are simplicity and stability. Slackware also strives to be the most "UNIX-like" Linux distribution.

If you want a distribution that will force you to understand Linux and its Unix heritage, Slackware is for you. If, instead, you want the complexities of Linux hidden from you, look for a different distribution.

Don't however let this intimidate you, Slackware is no more difficult to learn or become proficient in than any other distribution. The main difference will be in the way you perform tasks, Slackware is far more dependent on the command line interface (cli) than it is on graphical tools. If you compare it to driving a car, you can think of Slackware as a manual/stick and distributions like Mandrake and Redhat as automatics.

To Quote the Slackware Web page:

What is Slackware Linux?

"The Official Release of Slackware Linux by Patrick Volkerding is an advanced Linux operating system, designed with the twin goals of ease of use and stability as top priorities. Including the latest popular software while retaining a sense of tradition, providing simplicity and ease of use alongside flexibility and power, Slackware brings the best of all worlds to the table.

"Originally developed by Linus Torvalds in 1991, the UNIX(tm)-like Linux operating system now benefits from the contributions of millions of users and developers around the world. Slackware Linux provides new and experienced users alike with a fully-featured system, equipped to serve in any capacity from desktop workstation to machine-room server. Web, ftp, and email servers are ready to go out of the box, as are a wide selection of popular desktop environments. A full range of development tools, editors, and current libraries is included for users who wish to develop or compile additional software."

title: Slackersbible/Introduction


text:
Slackersbible/Installation

Synopsis
The following chapter will cover most of the basic installation procedures for the Slackware Linux operating system. Much of this material has been collected from the Internet and from my personal Slackware experiences.

After reading this chapter, you will know:

 * What the system requirements for Slackware are
 * How to obtain Slackware CD's
 * How to prepare for installing Slackware Linux
 * How to allocate space and format your hard drives
 * How to become familiar with the install tool
 * How to choose your installation media
 * How to choose what you want installed
 * The basics of the actual operating system install
 * What your post installation options are

Pre-install preparations
Before installing Slackware Linux on your system, there are a few things that need to be done.

2.2.1 Know your system

It is a good idea to make a list of components inside your computer. The easiest way to do so is to use an application on an installed operating system. If you don't have an OS installed you can maybe use a Live CD or you could just open up your case and see what's inside. Once you have the information you need, you can check the internet to see if there are any known problems between Linux and your hardware. Slackware requires at least:

 * a 486 processor
 * 16MB RAM
 * a 3.5" floppy drive, however you can now perform the installation with a CD set, so a CD-ROM drive is recommended

Another good thing might be to run "lspci" from inside a Linux environment on your computer, whether during install or from a Knoppix or other bootable environment.

2.2.2 Backup

When you want to install Slackware Linux on a disk which contains valuable data it is recommended to backup that data. Also make sure the backups are usable! Slackware Linux asks for confirmation before erasing or overwriting data on your disk, but once you have confirmed there is no way to undo the action.

2.2.3 Installation Location

If you want Slackware Linux to install to the whole disk and don't want to keep any of the data on that disk, you can skip this section.

A hard disc can be divided into different pieces. These pieces are called partitions. Originally PC's only supported upto four partitions, these 'main' partitions are therefore named the primary partitions. Because four partitions in some cases were not enough, a new kind of partition was created: the extended partition. This is a special partition because it contains other partitions, these partitions are named the logical partitions.

To install Slackware Linux you need at least two partitions: one primary partition to install Slackware and a swap partition.

A swap partition is used by the kernel to write unused memory blocks to the hard disc, it can be either a logical or a primary partition. The size can be anything up to 2 Gb for Intel machines. However, there is no official rule to the minimum size although a lot of people use the same size for their swap as they have in RAM. These two, swap size and RAM size, are added together and make virtual memory. On older machines the minimum virtual memory is 12 MB. The total size depends on what kind of applications you are going to use.

Partitions are defined by a number which represents the kind of data the partition contains: the partition ID. For a Linux swap partition the ID is 82 and for a normal Linux partition the ID is 83.

The normal primary Linux partition only has a minimum size which differs from every distribution. Slackware Linux needs approx. 200-500 MB for an minimal installation (without X or extra applications) and 2 GB for a full installation.

For those of you into the security aspect, you can visit http://www.linuxpackages.net/gen_pdf.php?file=securing.html to read "Securing Slackware 8" by a SANS graduate.

The partitions on your disk(s) can be modified in several ways.You can use:

* fdisk in DOS or Windows. * the built-in fdisk with the Slackware Linux installation CD. * PartitionMagic®, which is a commercial program for Windows which can resize NTFS and other partitions.

Be careful with using these programs though, if you make a mistake, you can lose all your data. Be sure to make backups!

Note: A software RAID installation paragraph should also be considered. For this, John Lange should be contacted and asked if he agrees to put in here his tutorial from http://www.langefamily.ca/howto/SlackwareRaidHowTo.html. LVM/EVMS installation instructions could also prove useful.

2.2.4 Network configuration information

During installation the installer will ask you for your Network details. It is a good idea to write these details down, from maybe your Windows settings. If you don't know your networking details, ask your Internet service provider or Network Administrator.

If you connect to the Internet with DSL or Cable you may need the following information:

* IP address (example, 192.168.1.100) * IP address of the gateway (example, 192.168.1.1) * IP address of the DNS server (example, 4.2.2.2) * Hostname (example, "mybox") * Subnet Mask (example, 255.255.255.0)

If you do not need this information because it is configured automatically with DHCP you do not have to write down anything, but remember to select DHCP.

If you connect to the Internet using a modem you will need the following information:

* Your ISP's phone number to dial. * The COM: port to which your modem is connected. * Username and password to login with your ISP.

2.2.5 Download installation files

You should consider what kind of install you would like to do. The easiest and recommended method is to purchase Slackware on CD or burn it to CD yourself. At the Slackware website, simply click "Get Slack" and from there pick a location and mirror you would like to download from. Simply download the .iso files and burn them to CD. As of Slackware 9.1, there are two CDs to Slackware. The first CD is essential, containing the kernel, GNU applications and utilities, the graphical environment (X.org) and some graphical environments and applications. The second CD contains only KDE and Gnome desktop environments, and is optional.

Booting

 * 1) Start with your computer turned off.

 * 1) Turn on the computer. As it starts it should display an option to enter the system set up menu, or BIOS, commonly reached by keys like F2, F10, Del, or Alt+S. Use whichever keystroke is indicated on screen. In some cases your computer may display a graphic while it starts. Typically, pressing Esc will dismiss the graphic and allow you to see the necessary messages.

 * 1) Find the setting that controls which devices the system boots from. This is usually labeled as the ``Boot Order'' and commonly shown as a list of devices, such as Floppy, CDROM, First Hard Disk, and so on.

If you needed to prepare boot floppies, then make sure that the floppy disk is selected. If you are booting from the CDROM then make sure that that is selected instead. In case of doubt, you should consult the manual that came with your computer, and/or its motherboard.

Make the change, then save and exit. The computer should now restart.

Installing from CDROM
If you have the bootable CD, available in the official disc set published by Slackware, Inc. or by downloading the cdrom image from http://www.slackware.com/getslack/, a CD-based installation will be a bit simpler for you. To start the installation you are going to have to put the cd in the cdrom and restart the computer, granted that you changed the bios options to accommodate for the cdrom boot. If everything goes as planned you should see this prompt.

ISOLINUX 2.10 2004-06-18 Copyright (C) 1994-2004 H. Peter Anvin Welcome to Slackware version 10.0 (Linux kernel 2.4.26)! If you need to pass extra parameters to the kernel, enter them at the prompt below after the name of the kernel to boot (scsi.s etc). NOTE: In most cases the kernel will detect your hardware, and parameters are not needed.

Here are some examples (and more can be found in the BOOTING file): hdx=cyls,heads,sects,wpcom,irq (needed in rare cases where probing fails) or hdx=cdrom (force detection of an IDE/ATAPI CD-ROM drive) where hdx can be any of hda through hdt.

In a pinch, you can boot your system from here with a command like:

For example, if the Linux system were on /dev/hda1.

boot: bare.i root=/dev/hda1 noinitrd ro

This prompt is just for entering extra parameters. If you don't need to enter any parameters, hit ENTER to boot the default kernel "bare.i" or press [F2] for a listing of more kernel choices.

Installing nvidia graphical drivers
NOTE: this guide assumes you have already gone run though xorgconfig and are already using working video drivers.

If you own a nvidia based Geforce video card than installation of the drivers cannot be easier. Head over to the nvidiadriver selectionpage and select the latest released drivers suited to your computers architecture.

It is highly recommended that you read the README which will explain in depth a whole lot of stuff about the drivers installation and settings of the /etc/X11/xorg.conf file. But basically all you need to do is log out of X and as root cd to where the drivers were downloaded to and run:

(arch being the architecture and x representing the version)

 * 1) sh NVIDIA-Linux-arch-x.x-xxxx-pkg1.run

This will unpack the self archiving package and take you though the nvidia-installer's step by step driver installation.

Once this is done open up your xorg.conf file (/etc/X11/xorg.conf) and found in the "# Graphics device section" and change the line:

Driver "nv" (or) Driver "vesa"

to

Driver "nvidia"

and in the Module section make sure you have the following line

Load "glx"

and remove these lines if they exist

Load "dri" Load "GLcore"

Now you should be able to start up X again and everything should be fine.

title: Slackersbible/Installation


text:
Template:Confusing

Places a page in Category:Pages needing clarification

title: Template:Confusing


text:
Slackersbible/UNIX Basics

Synopsis
The following chapter will cover the basic commands and functionality of the Slackware Linux operating system. Much of this material is relevant for any UNIX® like operating system. Feel free to skim over this chapter if you are familiar with the material. If you are new to Slackware, then you will definitely want to read through this chapter carefully.

After reading this chapter, you will know:

 * How to use the "virtual consoles" of Slackware.
 * How UNIX file permissions work.
 * The default Slackware file system layout.
 * The Slackware disk organization.
 * How to mount and unmount file systems.
 * What processes, daemons, and signals are.
 * What a shell is, and how to change your default login environment.
 * How to use basic text editors.
 * What devices and device nodes are.
 * What binary format is used under Slackware.
 * How to read manual pages for more information.

Virtual Consoles and Terminals
Slackware can be used in various ways. One of them is typing commands to a text terminal. A lot of the flexibility and power of a UNIX® operating system is readily available at your hands when using Slackware this way. This section describes what terminals and consoles are, and how you can use them.

The Console
By default, Slackware is configured to boot into the command line interface, unless you've changed this, the system will present you with a login prompt after it boots, right after the startup scripts finish running. You will see something similar to:

Loading OSS compatibility modules for ALSA. Welcome to Linux 2.4.26 (tty1) hawk login:

The messages might be a bit different on your system, but you will see something similar. The last two lines are what we are interested in right now. The second last line reads:

Welcome to Linux 2.4.26 (tty1)

This line contains some bits of information about the system you have just booted. You are looking at a Slackware console. The name of this machine (every UNIX machine has a name) is hawk, and you are now looking at its system console--the tty1 terminal. Finally, the last line is always:

login:

This is the part where you are supposed to type in your username to log into Slackware. The next section describes how you can do this.

Logging into Slackware
Slackware is a multiuser, multiprocessing system. This is the formal description that is usually given to a system that can be used by many different people, who simultaneously run a lot of programs on a single machine. Every multiuser system needs some way to distinguish one user from the rest. In Slackware (and all the UNIX like operating systems), this is accomplished by requiring that every user must log into the system before being able to run programs. Every user has a unique name (the username) and a personal, secret key (the password). Slackware will ask for these two before allowing a user to run any programs. Right after Slackware boots and finishes running its startup scripts, it will present you with a prompt and ask for a valid username:

login:

For the sake of this example, let us assume that your username is john. Type john at this prompt and press Enter. You should then be presented with a prompt to enter a password:

login: john Password:

Type in john's password now, and press Enter. The password is not echoed! You need not worry about this right now. Suffice it to say that it is done for security reasons. If you have typed your password correctly, you should by now be logged into Slackware and ready to try out all the available commands. You should see the MOTD or message of the day followed by a command prompt (a #, $, or % character). This indicates you have successfully logged into Slackware. 3.2.3 Multiple Consoles

Running UNIX commands in one console is fine, but Slackware can run many programs at once. Having one console where commands can be typed would be a bit of a waste when an operating system like Slackware can run dozens of programs at the same time. This is where virtual consoles can be very helpful. Slackware can be configured to present you with many different virtual consoles. You can switch from one of them to any other virtual console by pressing a couple of keys on your keyboard. Each console has its own different output channel, and Slackware takes care of properly redirecting keyboard input and monitor output as you switch from one virtual console to the next.

Special key combinations have been reserved by Slackware for switching consoles. You can use Ctrl+Alt-F1, Alt-F2, through Alt-F8 to switch to a different virtual console in Slackware. TTY1 (Ctrl+Alt+F1) is the default virtual console that you see at login. TTY1 through TTY6 are available at all times in text mode. TTY7 and higher become graphical virtual consoles when the graphical system is started.

As you are switching from one console to the next, Slackware takes care of saving and restoring the screen output. The result is an ``illusion of having multiple ``virtual screens and keyboards that you can use to type commands for Slackware to run. The programs that you launch on one virtual console do not stop running when that console is not visible. They continue running when you have switched to a different virtual console.

Permissions
Slackware is based on several key UNIX concepts. The first and most pronounced is that Slackware is a multi-user operating system. The system can handle several users all working simultaneously on completely unrelated tasks. The system is responsible for properly sharing and managing requests for hardware devices, peripherals, memory, and CPU time fairly to each user.

Because the system is capable of supporting multiple users, everything the system manages has a set of permissions governing who can read, write, and execute the resource. These permissions are stored as three octets broken into three pieces, one for the owner of the file, one for the group that the file belongs to, and one for everyone else. This numerical representation works like this: Value Permission 	             Directory Listing 0    No read, no write, no execute  --- 1    No read, no write, execute     --x 2    No read, write, no execute     -w- 3    No read, write, execute        -wx 4    Read, no write, no execute     r-- 5    Read, no write, execute        r-x 6    Read, write, no execute        rw- 7    Read, write, execute           rwx

You can use the -l command line argument to ls(1) to view a long directory listing that includes a column with information about a file's permissions for the owner, group, and everyone else. For example, a ls -l in an arbitrary directory may show:

% ls -l total 530 -rw-r--r-- 1 root wheel 512 Sep 5 12:31 myfile -rw-r--r-- 1 root wheel 512 Sep 5 12:31 otherfile -rw-r--r-- 1 root wheel 7680 Sep 5 12:31 email.txt ...

Here is how the first column of ls -l is broken up:

-rw-r--r--

The first (leftmost) character tells if this file is a regular file, a directory, a special character device, a socket, or any other special pseudo-file device. In this case, the - indicates a regular file. The next three characters, rw- in this example, give the permissions for the owner of the file. The next three characters, r--, give the permissions for the group that the file belongs to. The final three characters, r--, give the permissions for the rest of the world. A dash means that the permission is turned off. In the case of this file, the permissions are set so the owner can read and write to the file, the group can read the file, and the rest of the world can only read the file. According to the table above, the permissions for this file would be 644, where each digit represents the three parts of the file's permission.

This is all well and good, but how does the system control permissions on devices? Slackware actually treats most hardware devices as a file that programs can open, read, and write data to just like any other file. These special device files are stored on the /dev directory.

Directories are also treated as files. They have read, write, and execute permissions. The executable bit for a directory has a slightly different meaning than that of files. When a directory is marked executable, it means it can be traversed into, that is, it is possible to "cd" (change directory) into it. This also means that within the directory it is possible to access files whose names are known (subject, of course, to the permissions on the files themselves).

In particular, in order to perform a directory listing, read permission must be set on the directory, whilst to delete a file that one knows the name of, it is necessary to have write and execute permissions to the directory containing the file.

There are more permission bits, but they are primarily used in special circumstances such as setuid binaries and sticky directories. If you want more information on file permissions and how to set them, be sure to look at the chmod manual page. 3.3.1 Symbolic Permissions

Contributed by Tom Rhodes.

Symbolic permissions, sometimes referred to as symbolic expressions, use characters in place of octal values to assign permissions to files or directories. Symbolic expressions use the syntax of (who) (action) (permissions), where the following values are available:

Option Letter 	Represents (who) 	u 	User (who) 	g 	Group owner (who) 	o 	Other (who) 	a 	All (world) (action) 	+ 	Adding permissions (action) 	- 	Removing permissions (action) 	= 	Explicitly set permissions (permissions) 	r 	Read (permissions) 	w 	Write (permissions) 	x 	Execute (permissions) 	s 	Set UID or GID

These values are used with the chmod command just like before, but with letters. For an example, you could use the following command to block other users from accessing FILE:

% chmod go= FILE

A comma separated list can be provided when more than one set of changes to a file must be made. For example the following command will remove the groups and world write permission on FILE, then it adds the execute permissions for everyone:

% chmod go-w,a+x FILE

Processes
Slackware is a multi-tasking operating system. This means that it seems as though more than one program is running at once. Each program running at any one time is called a process. Every command you run will start at least one new process, and there are a number of system processes that run all the time, keeping the system functional.

Each process is uniquely identified by a number called a process ID, or PID, and, like files, each process also has one owner and group. The owner and group information is used to determine what files and devices the process can open, using the file permissions discussed earlier. Most processes also have a parent process. The parent process is the process that started them. For example, if you are typing commands to the shell then the shell is a process, and any commands you run are also processes. Each process you run in this way will have your shell as its parent process. The exception to this is a special process called init(8). init is always the first process, so its PID is always 1. init is started automatically by the kernel when Slackware starts.

Foreground and Background

When you run a command, usually that command is in the foreground (you see it) and it's using the computer until it is finished. This might seem obvious until you realize that there are things that can be done about this. For example, if you start a command and then decide that you would like to terminate it, you can usually use Ctrl+C to terminate it. Also, if you'd like to start other commands rather than wait for the program to quit, you may use Ctrl+Z to stop it, so that it will no longer run and be "in your way".

A stopped application can be brought to the foreground once again using the "fg" command, where it will resume running. This is useful if you want to let the command continue, or if you'd like to use Ctrl+C to terminate it.

Another thing that can be done is to use an ampersand (&) after a command to cause it to run in the background. When you do this, you might see the following:

root@darkstar:~# updatedb & [1] 12353

This means that the program has been started, and has been given the PID (program identification number) of 12353, which is useful should you want to terminate it with "kill 12353".

Two commands are particularly useful to see the processes on the system, ps(1) and top(1). The ps command is used to show a static list of the currently running processes, and can show their PID, how much memory they are using, the command line they were started with, and so on. The top command displays all the running processes, and updates the display every few seconds, so that you can interactively see what your computer is doing.

By default, ps only shows you the commands that are running and are owned by you. For example:

raven@hawk:~$ ps PID TTY TIME CMD 31674 pts/1 00:00:00 bash 31686 pts/1 00:00:00 ps

As you can see in this example, the output from ps(1) is organized into a number of columns. PID is the process ID discussed earlier. PIDs are assigned starting from 1, go up to 99999, and wrap around back to the beginning when you run out. The TT column shows the tty the program is running on, and can safely be ignored for the moment. STAT shows the program's state, and again, can be safely ignored. TIME is the amount of time the program has been running on the CPU--this is usually not the elapsed time since you started the program, as most programs spend a lot of time waiting for things to happen before they need to spend time on the CPU. Finally, COMMAND is the command line that was used to run the program.

ps(1) supports a number of different options to change the information that is displayed. One of the most useful sets is auxww. a displays information about all the running processes, not just your own. u displays the username of the process' owner, as well as memory usage. x displays information about daemon processes, and ww causes ps(1) to display the full command line, rather than truncating it once it gets too long to fit on the screen. The output from top(1) is similar. A sample session looks like this:

raven@hawk:~$ top top - 22:52:10 up 11:29, 2 users, load average: 0.13, 0.04, 0.01 Tasks: 34 total, 1 running, 33 sleeping, 0 stopped, 0 zombie Cpu(s): 0.0% user, 0.0% system, 0.0% nice, 100.0% idle Mem: 190788k total, 187268k used, 3520k free, 44340k buffers Swap: 976712k total, 740k used, 975972k free, 86176k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1 root 8 0 240 240 212 S 0.0 0.1 0:04.64 init 2 root 9 0 0 0 0 S 0.0 0.0 0:00.24 keventd 3 root 19 19 0 0 0 S 0.0 0.0 0:00.35 ksoftirqd_CPU0 4 root 9 0 0 0 0 S 0.0 0.0 0:01.16 kswapd 5 root 9 0 0 0 0 S 0.0 0.0 0:00.05 bdflush 6 root 9 0 0 0 0 S 0.0 0.0 0:00.30 kupdated 10 root -1 -20 0 0 0 S 0.0 0.0 0:00.00 mdrecoveryd 11 root 9 0 0 0 0 S 0.0 0.0 0:00.00 kreiserfsd 60 root 9 0 588 588 508 S 0.0 0.3 0:00.07 syslogd 63 root 9 0 448 448 392 S 0.0 0.2 0:00.04 klogd 75 root 8 0 688 688 520 S 0.0 0.4 0:00.17 cardmgr 157 root 9 0 492 460 428 S 0.0 0.2 0:00.00 dhcpcd 272 root 9 0 0 0 0 S 0.0 0.0 0:00.00 khubd 762 root 9 0 520 520 464 S 0.0 0.3 0:00.00 inetd 765 root 9 0 1408 1408 1308 S 0.0 0.7 0:00.21 sshd 776 root 4 0 564 564 496 S 0.0 0.3 0:00.00 crond 778 daemon 9 0 616 616 548 S 0.0 0.3 0:00.01 atd

The output is split into two sections. The header (the first five lines) shows the PID of the last process to run, the system load averages (which are a measure of how busy the system is), the system uptime (time since the last reboot) and the current time. The other figures in the header relate to how many processes are running (47 in this case), how much memory and swap space has been taken up, and how much time the system is spending in different CPU states.

Below that are a series of columns containing similar information to the output from ps(1). As before you can see the PID, the username, the amount of CPU time taken, and the command that was run. top(1) also defaults to showing you the amount of memory space taken by the process. This is split into two columns, one for total size, and one for resident size--total size is how much memory the application has needed, and the resident size is how much it is actually using at the moment.

top(1) automatically updates this display every two seconds; this can be changed with the s option.

Text Editors
Much of UNIX administration involved editing configuration files, most of which are simply text files. Here we will address several of the most common UNIX text editors and their basic operations.

vi
There is arguably no text editor more ubiquitous in the UNIX world than vi. This fact alone serves as a reason that all serious UNIX (and Slackware) users should learn at least its basic features. The name comes from the command "visual" used to switch the ex line editor into visual mode. This fact serves to illustrate two interesting things about vi. First, that vi is a modal editor, which means that its editing functions change depending on the state, or mode, that the program is in. The second interesting thing to note is that the name is, like much of UNIX programs, and extension of another. vi has all the user customization and extensibility UNIX users demand, which makes it an extremely powerful program.

Modal Editing
By contrast to some text editors that simply echo keystrokes to the screen and rely on function key combinations for extended features, modal editors--and by extension, vi--use the editor mode to define what actions are perform on the text file. This is best explained by example.

1 ~ ~ ~ ~ ~ ~ ~ ~ ~                             VIM - Vi IMproved ~ ~                              version 7.0.122 ~                          by Bram Moolenaar et al. ~                 Vim is open source and freely distributable ~ ~                       Become a registered Vim user! ~               type  :help register   for information ~ ~               type  :q               to exit ~               type  :help  or    for on-line help ~               type  :help version7   for version info ~ ~ ~ ~ ~ ~ ~ ~

What you see is a modern version of vi called Vim. Vim inherits nearly all of the features of the original, proprietary version of vi, and adds a multitude of its own features which are distributed under a GPL-compatible free software license. The screen above is what Vim looks like when it first loads. In this state, it is in Normal mode. Normal mode is also referred to as Command mode, because from this mode you can execute various commands, or actions, on the text, such as changing, deleting, copying, etcetera. To enter text in standard fashion, you must first switch vi to Insert mode.

From this initial mode we can enter text by switching to Insert mode in one of several ways. The easiest is just to press the "i" key (for insert). Now you can enter text as you wish. All standard alphanumeric characters, including punctuation, are echoed to the display as typed:

1 vi is my favorite text editor. ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ -- INSERT --
 * Figure 5.1.1-1 :

You can see from this example that Vim displays the text as typed, "vi is my favorite text editor.", as well as the fact that it is now in Insert mode. To switch back to Command mode, simply press the escape key (Esc). vi will return to Command mode (and Vim will change its display to reflect this by removing "-- INSERT --" from the bottom of the screen.

 * Important : Commands Are Case Sensitive : Be careful. vi commands (such as "i" here) are case sensitive, so a capital "I" is not the same command as a lower case "i".  By the same token it is highly recommended not to use CAPSLOCK on your keyboard while editing in vi.  Despite being largely superfluous to most typists anyway, using CAPSLOCK can lead to unexpected results when you switch back to Command mode.

Basic Commands
"So what good is Command mode?" you ask. Good question. Let's take a look at some basic commands that illustrate the power of modal editing.

Moving the Cursor
Command mode may seem to add complication to the text editing process, but it is actually designed to increase productivity. One of the first fruits you will glean from Command mode is increased speed editing text. Command mode makes text editing faster than standard text editing even if you only know a handful of commands. Take the previous example (see Figure 5.1.1-1). If you were to press "Esc" at the end of the line, vi would enter Command mode and the cursor would be placed atop the last character typed. From this state, you can use the "h", "j", "k", and "l" keys to move the cursor left, down, up, and right, respectively, throughout the file one character at a time.

Yanking, Putting and Deleting Text
vi uses registers to store text temporarily. Using the yank and put commands, you can copy or remove text from a portion of the file into the register and put it somewhere else.

File Operations
So now that you can do a few commands, you probably want to open a file do some editing.

Emacs
Emacs is another popular UNIX text editor and, like vi, is extremely powerful. Emacs was originally conceived by Richard Stallman, the founder of the GNU project, as a set of editor macros for another text editor. This eventually became what is known today as Emacs (derived from Editor MACroS).

title: Slackersbible/UNIX Basics


text: Japanese/Kanji/Lesson 2

title: Japanese/Kanji/Lesson 2


text:
Set Theory/Zermelo-Fraenkel (ZF) Axioms

Formally, a set is not defined besides what the axioms say. We can define any collection of objects as a class, so that any set is a class, but not any class is a set (classes which are not set are sometimes known as proper classes).

The Zermelo-Fraenkel (ZF) Set Theory Axioms
In order to prove some of the fundamental results of set theory, and to begin to define other branches of mathematics based on it, we need to start with some axioms that we religiously take to be true. There are many possibilities for choices of axioms, but the most popular set of axioms is the Zermelo-Fraenkel system, or, more generally, Zermelo-Fraenkel with the Axiom of Choice.

We will start by saying that the universe is non-empty.

$$\exists y: \forall x: (x \notin y)$$ "there exists a set with no elements."

We call a set that contains no elements, an empty set. A natural question to ask is whether such a set is unique.

We will need a notion of equality between sets.

$$\forall x: \forall y: ((x=y)\Leftrightarrow(\forall z: (z \in x)\Leftrightarrow(z \in y)))$$ "if two sets have the same elements, then they are said to be equal."

We can now prove the uniqueness of an empty set. We prove this informally, and use the argument: reductio ad absurdum. Which in English means proof by contradiction.

We define the empty set as $$\emptyset$$.

So far, we have only shown the existence of the empty set. Thus motivates our next axiom.

$$\forall x: \forall y: \exists m: \forall u: (u \in m) \Leftrightarrow ((u=x)\vee(u=y))$$ "if we have two sets $$x$$ and $$y$$, then we can form an unordered pair set $$m$$ that contains exactly $$x$$ and $$y$$. We write this as $$\{x,y\}$$."

It follows directly from ZF2, that the unordered pair set is de facto unique (so our intuition that order does not matter in unordered pair sets is true, $$\{x,y\}=\{y,x\}$$). It also follows directly from ZF2 that if $$x$$ is a set, then by ZF3 we have a set containing $$x$$, i.e., $$\{x\}$$.

Our theory so far shows the existence of infinitely many sets. We get $$\emptyset$$ with ZF1, and by ZF3 we get $$\{\emptyset\}$$, and again by ZF3 we get $$\{\{\emptyset\}\}$$, and so on...

The notion of infinite here is used informally since we have not yet defined it.

The only con we currently have in our theory is that we can only form empty sets, singleton sets, and pair sets. More precisely, we can say,
 * empty$$(x):\Leftrightarrow(\forall y: y \notin x)$$
 * singleton$$(x):\Leftrightarrow(\forall y: (x=\{y\}))$$
 * pair$$(x):\Leftrightarrow(\forall y: \forall z: (x=\{y,z\})\wedge(y \neq z))$$

We can now define an ordered pair set as $$(x,y)=\{\{x\},\{x,y\}\}$$. It is easy to see that if $$x \neq y$$, then $$(x,y)\neq(y,x)$$. This was defined by Kuratowski in 1921.

To define larger sets, we need the following axiom.

$$\forall x: \exists u: \forall y: (y \in u) \Leftrightarrow (\exists z: (y \in z)\wedge(z \in x))$$ "for any set $$x$$, there exists another set whose elements are precisely the elements of the elements of $$x$$. We write the set $$u$$ as $$\bigcup u$$."

So, the union of sets $$\{x,y\}$$ and $$\{z\}$$ is simply $$\{x,y,z\}$$. Thus we have a triple set. We can continue unionising sets to form even larger sets.

We also have the usual notion of unionising two sets, i.e., the union of set $$x$$ and set $$y$$, which we write as $$x \cup y$$, is defined as $$\bigcup\{x,y\}$$.

Given a set $$z$$ and a formula in the language of set theory $$\phi(x,y)$$, such that for all $$x$$ there exists a unique $$y$$ such that $$\phi(x,y)$$ is true. Then there exists a set $$a$$ whose elements are all those $$y$$. We write this as the set $$\{y \, | \, \exists x \in z: \phi(x,y)\}$$.

Intuitively, we can think of this as the existence of a map.

The following axiom follows from ZF5, but we will write it since it is useful to have. We shall name it ZF 5.1 to exaggerate the fact that it can be proven from ZF5.

Given a set $$y$$ and a formula in the language of set theory $$\phi(x)$$. Then we have a set of all $$z \in y$$ such that $$\phi(z)$$ is true. We write this as the set $$\{z \in y \, | \, \phi(z)\}$$.

The uniqueness of such a set (both from ZF5 and ZF 5.1) follows from ZF2.

ZF5 and ZF 5.1 are both axiom schemes since it comprises infinitely many axioms - one for each formula $$\phi$$. Notice that the restriction $$x\in A$$ in this axiom helps us to avoid Russell's paradox - in this paradox a "set" of the form $$\{x\,|\,P(x)\}$$, with $$ P(x)= x\not\in x $$, was used.

From this, we can now define the intersection set. We define the intersection of set $$x$$, denoted as $$\bigcap x$$, as $$\{z\in\bigcup x\,|\,(\forall y\in x:z\in y)\}$$.

Note that we can now define the subset abbreviation symbol $$\subseteq$$. We say $$x\subseteq y$$ to mean $$\forall a: (a\in x)\Rightarrow(a\in y)$$. Exercise: Explain why the complement set of set $$x\subseteq y$$ is de facto a set.

Now we can prove that the universal set is not a set. We use the same argument as above, i.e., reductio ad absurdum.

The set of all sets is not a set.

$$\forall x: \exists y: \forall z: (z \in y)\Leftrightarrow(\forall a:(a \in z)\Rightarrow(a \in x))$$ "if $$x$$ is a set, then there exists a set $$\mathcal{P}(x)$$ whose elements are the subsets of $$x$$."

So the power set of an empty set, is the set of an empty set, i.e., $$\mathcal{P}(\emptyset)=\{\emptyset\}$$.

As we will see, there is no way to define an infinite set given our current axioms, so we require the following axiom.

An inductive set exists. An inductive set is a set $$I$$ such that, $$\emptyset \in I$$, and $$x \in I \Rightarrow x \cup \{x\} \in I$$.

The following axiom is somewhat of a convention but various models of set theory have been defined without it, or even using axiom stating things close to the opposite.

For every non-empty set $$x$$ there is some $$y \in x$$ such that $$x \cap y=\emptyset$$.

These eight axioms complete the list of axioms for ZF Set Theory.

The next axiom is called the Axiom of Choice or AC for short. ZF together with AC is called ZFC Set Theory.

For every set $$S$$ of nonempty disjoint sets, there exists a function $$f$$ defined on $$S$$ such that, for each set $$x \in S$$, $$f(x) \in x$$.

title: Set Theory/Zermelo-Fraenkel (ZF) Axioms


text:
Nuclear Physics/Nuclear Fusion and Fission

Introduction
Nuclear fusion and fission are the processes by which the nucleus of an atom gains (fusion) or loses (fission) protons, transforming into a different type of atom. Both processes release energy. Nuclear fusion and fission occur in nature, for example, within a star, and artificially, for example in a nuclear reactor.

Energy is released from the nucleus if the ../Nuclear Binding Energies/ of the nucleus is increased.

Where Does the Energy Come From?
Everyone has heard of the equation $$ E = mc^2 $$ but surprisingly few know what it actually means. As well as having heavy implications in electrodynamics and other fields, it says that energy and mass are like beasts, and you can convert one to the other. The Binding Energy, also known as the mass defect, is where this energy comes from. Mass is lost from the nucleus, and energy is released.

Fusion
Fusion is the process of combining the nuclei of smaller atoms(less protons & neutrons and hence, a smaller atomic number) to create a larger atom. In many stars, the process starts with hydrogen (H) atoms combining to form helium atoms (He) then combining again to form Beryllium (Be) atoms and so on... The process stops when all the atoms are converted to Iron (Fe) and the star is thus dead. The reason for this is that once the atoms reach Iron and higher, the energy required to fuse the atoms becomes greater than the energy released by the atoms.

More precisely, fusion is only favourable up to Iron since it is only up to this point that the energy per nucleon (proton and neutron) continues to decrease. The most efficient energy/nucleon reactions that can occur in the process of fusion are Hydrogen-Hydrogen reactions, or between various isotopes of hydrogen. For nuclei heavier than Iron, the tendency is for fission (see other section) to become more viable in terms of liberating energy, i.e. to reduce stored energy/nucleon.

Fusion occurs naturally in environments where a sufficiently large amount of matter is collapsed under gravitational pressure that atoms are stripped of their electrons and nuclei have a sufficiently low mean free path (i.e. their density is fairly high). The aggregate of matter forming such an object is then usually referred to as a star.

Fusion Power
Since the yield from hydrogen fusion is actually higher than for uranium fission, the byproducts are largely benign (with the exception of high energy neutrons), and the materials can be readily obtained by electrolysis from a plentiful resource (water), it is natural to consider trying to build fusion power plants. Since the nuclei are charged, it is possible to control them using powerful magnetic fields, and this is the standard idea in trying to control hydrogen plasma in order to produce a sustained and controlled nuclear reaction. Although progress has been steady, considerable engineering obstacles still need to be overcome.

Wikipedia's entry on Fusion Power

Fission
This is the breakdown of large, heavy nuclei, to make smaller, lighter, more stable nuclei with a lower energy state and release energy at the same time, this is the process used in creating nuclear weapons. A nucleus may split in many different ways, in fact it is very rare for an even split to occur, one "half" being larger than the other in most cases. the mechanism maybe something like this an unstable (large Neutron rich isotope)is held together by the strong nuclear force because it is unstable it distorts allowing the coulomb repulsion between the positive protons to over come the strong nuclear attraction and separate them this forms two highly energetic halves. these may increase their stability by emitting neutrons, these are known as prompt neutrons. Other neutrons maybe emitted later these are known as not surprisingly delayed neutrons. There are two types of fission, the first is spontaneous(this happens without first absorbing a neutron)and more common neutron induced fission which is as its name implies.

For power generation only nuclear fission occurring in a chain reaction is of interest. It is performed controlled in a reactor and uncontrolled in a nuclear bomb. For running a chain reaction the absence of neutron captures and materials with fissionables nuclei are required. The only natural nuclei, which can be used for reactor operation is uranium235. Others like plutonium239 have to be created artificially, however also in a reactor, which requires a fuel like uranium235 or plutonium239. Interestingly a few billion years ago, building a reactor would have been much easier, as there was a much higher concentration of uranium235 in natural uranium! You can read the exact content therefore under Change of isotope composition of natural uranium.

The Proton-Proton Chain
This is the main fusion process in stars with masses similar to our Sun. The core temperature reached in such stars is in the order of 15 million Kelvin. For larger stars, with higher core temperatures, the Carbon-Nitrogen-Oxygen cycle fusion process becomes the dominant mechanism. Basically the Branch I reactions are as follows, with the ultimate generation of 26.72 MeV of energy. These reactions generate approximately 85% of the Sun's solar energy production. p + p = d + e+ + νe p + d = 3He + γ 3He + 3He = 4He +2p Branch II and III of main sequence hydrogen burning produce much less energy.

Branch II 3He + 4He = 7Be + γ e- + 7Be = 7Li + νe p + 7Li = 4He + 4He Branch III p + 7Be = 8B + γ 8B = 8Be* + e+ + νe 8Be* = 4He + 4He

The Carbon-Nitrogen-Oxygen Cycle
This reaction takes place in stars 1.3 times more massive than our own, it is almost exactly the same as the proton-proton chain except that it uses carbon as catalyst. The carbon in the reaction is not used up and is recycled at the end of the reaction. The CNO process generates 26.72 MeV of energy, this is the main branch.

p + 12C = 13N + γ + 1.95 MeV

13N = 13C + e+ + ve + 2.22 MeV

13C + p = 14N + γ + 7.54 MeV

14N + p = 15O + γ + 7.35 MeV

15O = 15N + e+ + ve + 2.75 MeV

15N + p = 12C + 4He + 4.96 MeV

Branch ||

There is a small chance that the last reaction in the branch above will not happen and that instead this reaction will.

15N + p = 16O + γ + 12.13 MeV

16O + p = 17F + γ + 0.60 MeV

17F = 17O + e+ + ve + 2.76 MeV

17O + p = 14N + 4He + 1.19 MeV

14N + p = 15O + γ + 7.35 MeV

15O = 15N + e+ + ve + 2.75 MeV

However the nitrogen produced in the last reaction will eventually take part in the last reaction of the first branch.

Branch |||

The last branch only takes place in particularly very massive stars where the 17O + p in the third reaction of the second branch produces a 18F + γ instead. This can also be called the OF cycle as the oxygen and fluorine used in the reaction are recycled.

17O + p = 18F + γ + 5.61 MeV

18F = 18O + e+ + ve + 1.65 MeV

18O + p = 19F + γ + 7.99 MeV

19F + p = 16O + 4He + 8.11 MeV

16O + p = 17F + γ + 0.60 MeV

17F = 17O + e+ + ve

It is important to note that all of the cycles can be simplified into one reaction because all branches will use the same reactants and produce the products.

4p = 4He + 2e+ + 2ve + 3γ + 26.72 MeV

The positrons released in the reaction will annihilate with the electrons and produce more energy in the form of gamma rays.


text: Japanese/Kanji/Lesson 3

title: Japanese/Kanji/Lesson 3


text:
Nuclear Physics/Nuclear Binding Energies

Binding energy is the amount of energy required to separate something down into its base components. In nuclear terms, the energy is derived from the Strong Nuclear Force.

The binding energy must come from somewhere, and in the case, because mass and energy are so strongly linked by Einstein's Equation E = mc2 the Binding Energy is proportional to the Difference in Mass of the Atom, compared to the sum of its parts. This is also called the mass defect. The larger the mass defect, the more stable the isotope is.

Example of Binding Energy:

The Binding Energy of a Deuterion 2H
A deuterion is the nucleus of a deuterium atom, and consists of one proton and one neutron. The masses of the constituents are:

 * mproton = 1.007276 u (where u represents the Atomic mass unit ≈ 1.66053886 x 10-27 kg)
 * mneutron= 1.008665 u
 * mproton + mneutron = 1.007276 + 1.008665 = 2.015941 u

The mass of the deuterion is:

 * Atomic Mass 2H = 2.013553 u

The mass difference = 2.015941 - 2.013553 = .002388 u. = 3.9654 x 10-30 kilograms.

Binding Energies of Isotopes
Iron is one of the most stable nuclei around. A picture should really be added here.

but if h= 1.007277, then 2h= 2.014554 and the difference between p and n is .001388. when you add this difference you get 2.0028434=2h.

try this h=1,007825,n=1.008665 then 2h =2.01565 and 1.008665-1.007825=.00084 then add that difference to change p to n, so 2.01565+.00084=2.01649 now sub. the so call binding energy, 2.01649-.002388= 2.014102 and this is mass of 2d that I find in text books!!! also .002388u mult. by 931.5 = 2.224422 in MeV units! if you follow the above 2.014102 times 2 is 4.028204. and 3 times 4.028204 is 12.084612, this is carbon. 12carbon(12.084612) + 1.007825 = 13nitrogen(13.092437) + .00084 = 13.093277(before the loss of a +beta and neutrino!). 13.093277 - .002388 = 13carbon(13.090889), add 1.007825 to get 14nitrogon(14.098714). again add 1.007825 to get 15oxygen(15.106539). again add .00084 to get 15.107379(again this is before loss of a +beta and neutrino!). again subtrack .002388 to get 15nitrogen(15.104991). now add 1.007825 to get 16oxygen(16.112816). 16oxygen(16.112816) = 12carbon(12.084612) + 4helium(4.028204) and this is the carbon cycle in stars.

in David Wayne Ferrin's note: the proton is 1.007277, and Hydrogen is 1.007277+(+beta=.000548)= 1.007825. Also .002388= (2(+beta)+2(-beta)+2(.000098)) or .002388=(.001194+.001194)=((.000548)+(.000548)+(.000098))x2, that is in a world with perfect field breaking symmetry, in fusion this happens 1.007825 + (1.007825 + .000840) = 2.01649. Ok, look this .002388 - .000840 = .001548, .000840 = .000548(first beta) + .000292, and .000292 = (.000098 + .000098 + .000096), and .001548 = (.001096(.000548x2)(second and third) + .000452), now add .000096 + .000452 = .000548(fourth). When betas are formed they do so in pairs (one real, one virtual), so do neutrinos = .000098. Now take 2.016490-1.006985(too light)=1.009505(too heavy). To 1.006985(tl) add .000292= 1.007277 add .000548= 1.007825 add (.000292+.000548)=.000840= 1.008665 add .000840= 1.009505(th). And if 1.006985/3= .3356616667 add .000840= .3365016667*3= 1.009505. .3356616667*931.5= 312.6688425, .3365016667*931.5= 313.451325, and 312.6688425 + (2*313.4513025)=939.5714476/931.5= 1.008665.


text:
Talk:Climate Change/Mitigation Strategies/Office

Things this page needs:

 * Graphs
 * "Put this into context": figures for how much $$CO_2$$ humans produce each year


text:
User:JustinLillich~enwikibooks

Dean of SLES: School of Literature & English Studies Areas of Focus: Web Content, Hypertext Fiction, Literature, Creative Writing, Technical Writing, New Media, Literary Criticism

I have a passion for the written word. I love to read and have since I was a child. I came from a very literary minded family. My mother works as a children's librarian and through her I have come to my love for reading. It was my purpose with the SLES to create a forum much like that of the ancient philosophers; a place where students and teachers would be able to create their own texts and study the work of previous attendees. Hopefully this goal will someday be achieved.

I have a personal blog, the handwritten hypertext, which I use as my base of operations and discussion on the web. There, you will find links to my del.icio.us tags and other original content. There will also be a course on the writing of the weblog posted there in a serial lesson system.

Enjoy all the SLES has to offer. Please feel free to contact those others who are involved with this school and we will continue to serve the knowledge seeking public.

= Courses for School of Literature and English Studies =

Undergraduate

 * Engl 1101 Rhetoric and Composition I
 * Engl 1102 Rhetoric and Composition II
 * Engl 3600 Advanced Composition
 * Engl 3610 Introduction to Fiction
 * Engl 3660 Introduction to Web Writing
 * Engl 3700 Advanced Rhetoric
 * Engl 3810 Introduction to Technical Writing
 * Engl 4551- Web Writing I: The Weblog
 * Engl 4552- Web Writing II: The Wiki

Graduate
My graduate involvement is by appointment only. I will only teach these courses on a one to one basis. In order to apply for such a course, please contact me by email at mailto:justin.lillich@gmail.com

= Projects = = Current Interests & Course Work =
 * Thesis revisions
 * Comprehensive Exams
 * Planning my oral defense
 * Writing the Cirriculum Vita
 * Jack London
 * Chaucer: Troilus & Criseyde
 * Literary Criticism

title: User:JustinLillich~enwikibooks


text:
User talk:JustinLillich~enwikibooks

Getting Help

 * I absolutely agree, but where to go? People seem to be dead around this place and kicking them into gear seems to be difficult.  Go with whatever ideas you have and any help from me you have with you.  Put something up on the talk page or maybe at the bottom of the main page. ~Amish

Names

 * I thought about that and if you're up for it, we can certainly do it. I mean, I'm using my user name like you are, in that it's basically my name anyways.  I figure if folks are interested, they can always click and see my name.  Amish

Requirements of a "Decree"
At some point, we should come up with a list of requirements in order to get a "decree" (which is what the Wikiversity folks call it, not me). What courses, what level courses, etc. Just a thought. There's no rush and I think we should take some time in deciding. This would be something no one else in the Wikiversity has done thus far, and that, too, makes it exciting! Amish

New to Wikiversity
Justin, Amish-

Just wanted to say hello. I've been using Wikipedia for some time now, just dabbling here and there in some of the areas where I know things. I stumbled onto this Wikiversity page a few days ago and would like to be more involved. My schedule is hectic at times, but I'd like to do as much as I can.

My focus is primarily Writing and Rhetoric (or Rhetoric and Composition depending on where you study), and I was curious about how you see that component falling under the larger umbrella of English and Literature Studies. I know that Writing and Rhetoric can tend to be a hot button item within schools of English, so I wanted to check with you before making major changes.

Would you be interested in having a school of Rhetoric and Composition under the larger umbrella of English and Literature studies that would cover the courses for composition, linguistics, grammar, professional (or other forms of non-creative) writing, rhetoric, teaching writing, etc.?

My thought is, the English department could be split into three "schools" or "sub-departments"? One school could focus on English studies, which consists primarily of literature and languages. Another school would focus on rhetoric and composition, which covers the previously mentioned headings. And our third school would cover all of our creative writing components.

So, if a student were in pursuit of a decree in English from our Wikiversity, the literature classes the student takes would be handled by faculty from the school of English studies. The composition classes would be handled by faculty from the school of Rhetoric and Composition. And any creative writing would be handled by faculty from the school of Creative Writing.

In order for a student to receive a decree, they would have to take a certain number of classes from each "school" of English. Depending on their focus, they might be obligated to take more classes in a certain school than another.

This just seems like a great place to be innovative with our decisions and think outside of the box. Wikiversity, as much as we might want it to be, is not a university. And I don't think that's a bad thing. Universities have set ways, traditions. This is our chance to be progressive and change the way we handle our fields of interest.

Just let me know if we can continue discussing some possible options for renovating how we do business. I mean, do we have to use the same class numbering system as a major university for our classes to mean as much? I don't think so. Why don't we sit down and think about how we can improve what we didn't like about the format of our educations? What do we have to lose?

I don't know if you guys saw Kathleen Blake Yancey's speech at the Conference on College Composition and Communication last year, but it addresses some of these key issues. We are in a revolutionary time right now, thanks to technology and the ability to communicate in new and different ways. We should be thinking of new ways to conduct our business. If you'd like a copy of the speech, e-mail me at ztheday@hotmail.com, and I can get it to you.

Thanks,

ztheday aka John Anderson

 * I personally think we're better off with the standard numbering. I also think that we should be able to move freely within SLES and run courses where we like.  With only three of us so far, why should we limit ourselves, especially since I feel we would all have knowledge in every area.  I don't see why I couldn't run a course in CW and LS and Justin run in Web Writing and LS or Comp, etc.  I figure we have the ability to run more courses in this forum than in a real university setting (where maybe you could run 2 or 3 at the most!).  While the courses themselves can be reworked, I think that a basic frame is a decent idea.  Amish

Welcome Back!!!
Boy am I glad to see you! I haven't been doing much of late as I'm not sure what will happen with Wikiversity. I say we start building this section into a perfect model and see if we can't get this whole project kick started. Up for it? Atrivedi

 * Also, if you want it, the top departmental slot is yours. Just keeping the seat warm :) Atrivedi

Template:Miscellaneous bookshelf ...
... is only for existing book of good quality.

Stages.
The lowest possible stage is and  - Please fill in the propper date. A red link (non existing book) can not - by definition - be finished by 25%. It is also not finished by 1% as it has not been started ;-).

--Krischik T 07:14, 15 February 2006 (UTC)

Redesign for the school
As you can tell, I've been thinking a lot about what this school is to become.

I figure that this is the safest place to write about what I want to do with this thing. I think it is best to do it point by point.

 * First of all, the basic structure of the school at this point could survive in the form of a text book. I believe it is important for us to look at building a textbook with what we have and working from there.  It would be a great idea for us to hold off on working through a school and set our sights on writing the text book first.
 * Secondly, course names and numbers: There should not have been so many course names and numbers this early. I know I fell into the trap of writing the names of every class I've ever seen in a course catalog.  At this point, there should be a basic set of work to look at.  I don't think I would be able to build much more than a couple courses at this point, and the work that would be done in just one class would be crazy enough.  The courses I teach at the University are bad enough.
 * Third, the name of the school. English isn't the only language that has literature or writing.  Any language that has a body of writing should be present here.  Without naming it something along the lines of the school of world literature, we should stick to a basic, all encompassing name.  My suggestion  School of Composition and Literature.  It's short, gets the point across.
 * Finally, the command structure. I don't know how long it will mean anything, but we'll try to have a board of directors and a person in charge of this board.  I think that most of the other schools are going with who posted to them first, so that is the way this will stand as well.  Those of you who have put your names on the lists of faculty will be considered the members of the board until such time as you see fit to no longer be attached.  It is the only really fair way to do this.

Overall, I think this will create a better system of keeping up with what I hope will be a busy schedule. We have to let Wikimedia know that we're in this for the long haul. As it's really really late here, I'm going to bed. See you all around! Cheers. --JustinLillich 06:42, 18 February 2006 (UTC)

 * I suggested 'School of Literary Studies' on the SLES talk page. It was a part of my master plan from before. Atrivedi

oh yeah
I believe a "Dean" is the head of a "School", where as a "Chair" is the head of a department, which is what you are :). Atrivedi

Makes sense
I suppose. I wasn't thinking about it that way, as I'm trying to bring all narrative languages under one heading instead of the traditional university English department.

JustinLillich T 00:23, 20 Feb 2006 (UTC)

You still out there??
They've approved Wikiversity! We can do this for real now! If you're still in, let's start working...from scratch. First things: School of Literary Studies. Not just English. Anything. Hope you're still with us! Atrivedi

Image copyright problem with Image:Writing-2.png
Thanks for uploading Image:Writing-2.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. SB_Johnny | talk 07:29, 15 September 2006 (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 JustinLillich. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name JustinLillich~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:21, 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:JustinLillich~enwikibooks


text:
Cookbook:Fish

| Basic foodstuffs | Seafood

Fish are odorless, nutritious, and tasty.

Fish should never have the so-called "fishy" smell, which actually comes from bacterial decay. It is best to get live fish. The second best choice would be frozen-at-sea fish, often marked FAS. Refrigerated fish are generally a poor choice, especially for timid buyers who are hesitant to demand a chance to smell the fish prior to purchase. Avoid fish with any discolored area. Do not store unfrozen fish for long.

Canned fish are often good, but very different in taste, and selection is limited. Canned salmon and anchovies are particularly high in calcium, because the bones are softened by canning and are eaten with the flesh.

While it is generally unwise to eat any fish raw, wild freshwater fish are particularly likely to carry parasites that can infect humans.

Note: the names of fish vary around the world. Also, many different fish are often sold under the same name if they share roughly the same appearance.

Kookboek/Vis

title: Cookbook:Fish


text:
Blender 3D: Noob to Pro/Basic Animation

Frames and Keyframes
A is a snapshot of the scene at one moment in time. An animation consists of displaying a succession of frames representing successive moments in time; if these are shown sufficiently quickly (at least 24 frames per second), the eye is fooled into seeing smooth movement, instead of a succession of still poses.

This is the principle behind both cinema film and digital video. But long before these were invented, it was known that you could make a sequence of drawings on pages of a flipbook, which could then be rapidly flipped by hand to produce an animation.

In live action video, we can capture the frames simply by letting the camera record as the scene unfolds. In hand-drawn animation (cartoons), each frame had to be drawn by a human animator (though there were some shortcut techniques like articulated character pieces, separately-moving scenery layers etc). Actually what would happen was that the most skilled artists would create s representing pivotal points in the animation (starting and ending poses in a character’s movement etc), and the lower-paid assistants would have the job of filling in all the intermediate frames to produce smooth movement between those endpoints.

Computer animation works in a similar way, except here Blender is your lower-paid assistant. You go to crucial points in the timeline of your animation, position and pose your objects/characters appropriately, and tell Blender that this is a keyframe for the relevant transformations (positioning/rotation/scaling) of those objects/characters. Then when you run the animation, Blender will interpolate the specified transformation parameters between keyframes, giving you smooth motion over those intervals.

The Timeline
At the bottom of the default Blender screen layout is a window called the. This gives you an overview of your animation.

You can zoom the view in and out with the mouse wheel, or scroll left and right with.

The numbers across the bottom are frame numbers, with your animation starting at frame 1. The light grey background indicates the total duration of the animation. The vertical green line is positioned at the current frame time, and the current frame number is also displayed in the box between the start/end values and the transport controls, and at the lower left of the viewport in the 3D view window. Yellow lines indicate where keyframes have been inserted.

You can set the current frame time by clicking with at the desired position. You can hop forward and backward a frame at a time with the left- and right-arrow keys, skip to the next or previous keyframe with the up- or down-arrow keys, and jump immediately to the first or last frame by holding down and pressing left- or right-arrow.

You can also “scrub” by dragging with across the timeline, which causes the animation to run backwards or forwards at whatever speed you choose, locked to the times across which you drag.

title: Blender 3D: Noob to Pro/Basic Animation