text:
CPAM with TWW/GNUstep and TWW HPMS

= GNUstep and TWW HPMS =

GNUstep aim to enable same source code to generate same software application with lease efforts. The approach is an intrusive approach with it own merits. we believe by incorporate CPAM ablitity within GNUstep. it can be most errogant and humble, intrusive and compatible.

GNUstep package by TWW HPMS tools
Following are quick examples for GNUsteppers. It is not a HellowWorld type of easy example. The package source still need to be refined. Goal of gnustep-core-1.0.sb is to digitalize this document at http://www.gnustep.org/resources/documentation/User/GNUstep/gnustep-howto.html.

Software Build: gnustep-core-1.0.sb in a XML file

 * This sb file can reproduce the build process with following command

sb gnustep-core-1.10.sb;sb -i gnustep-core-1.10.sb

 * Following command will list out the software modules in a GNUstep core

[root] sb -q module-names gnustep-core-1.10.sb gnustep-base ffcall gnustep-examples gnustep-gui gworkspace gnustep-make gnustep-back [root]

Note: HPUX portion of instruction is most like not correct.
 * gnustep-core-1.10.sb

[root] cat gnustep-core-1.10.sb

 gnustep-make-1.10.0 GNUstep  gcc332r

<![CDATA[ case "${SB_SYSTYPE}" in ;; CFLAGS="-O2" CC_LD_RT="-R" GCCR_LIB=/opt/TWWfsw/gcc332r/lib ./configure CC="${CC:-gcc}" CFLAGS="${CFLAGS:--O2}" \ LDFLAGS="${CC_LD_RT}${GCCR_LIB}" \ --prefix=${INSTALL_PREFIX} ;; CFLAGS="-O2" CC_LD_RT="-R" GCCR_LIB=/opt/TWWfsw/gcc332r/lib CC=/opt/TWWfsw/gcc332/bin/gcc ./configure CC="${CC:-gcc}" CFLAGS="${CFLAGS:--O2}" \ LDFLAGS="${CC_LD_RT}${GCCR_LIB}" \ --prefix=${INSTALL_PREFIX}
 * -hpux11.11)
 * -hpux10.20)
 * -linux*)

;; set -x CFLAGS="-O2 -mcpu=v8" CC_LD_RT="-R" CC=/opt/TWWfsw/bin/gcc GCCR_LIB=/opt/TWWfsw/gcc332r/lib ./configure CC="${CC:-gcc}" CFLAGS="${CFLAGS:--O2}" \ LDFLAGS="${CC_LD_RT}${GCCR_LIB}" \ --prefix=${INSTALL_PREFIX} esac ]]> ![CDATA[ ase "${SB_SYSTYPE}" in -hpux11.11) ;; -hpux10.20) make clean make ;; -linux*) -solaris2.[689]) make clean make sac ]>
 * -solaris2.[689])

![CDATA[ make install make sure GNUstep.sh script can be accessed via /opt/TWWfsw/bin kdir -p ${INSTALL_PREFIX}/bin n -s ${INSTALL_PREFIX}/System/Makefiles/GNUstep.sh \ {INSTALL_PREFIX}/bin/GNUstep.sh ]>

<![CDATA[ case "${SB_SYSTYPE}" in ;; ;; ;;
 * -hpux11.11)
 * -hpux10.20)
 * -linux*)
 * -solaris2.[689])

esac ]]>

ffcall-1.9 ffcall19  gcc332r

 </script-header>

<![CDATA[

case "${SB_SYSTYPE}" in ;; CFLAGS="-O2 -march=1.1" CC_LD_RT="-R" GCC332R_LIB=/opt/TWWfsw/gcc332r SSL_LIB=/opt/TWWfsw/libopenssl097/lib/ XML_LIB=/opt/TWWfsw/libxml242/lib XML=/opt/TWWfsw/libxml242 ICONV=/opt/TWWfsw/libiconv16 CC=gcc ./configure CC="${CC:-gcc}" CFLAGS="${CFLAGS:--O2}" \ LDFLAGS="${CC_LD_RT}${XML_LIB}:${GCC332R_LIB}:${LDFLAGS+${LDFLAGS}}" \ --prefix=${INSTALL_PREFIX} \ --enable-shared ;; CFLAGS="-O2" GCC332R_LIB=/opt/TWWfsw/gcc332r SSL_LIB=/opt/TWWfsw/libopenssl097/lib/ XML_LIB=/opt/TWWfsw/libxml242/lib XML=/opt/TWWfsw/libxml242 INSTALL_PREFIX=/opt/TWWfsw/ffcall19 ./configure --prefix=${INSTALL_PREFIX} --enable-shared ;; CFLAGS="-O2 -mcpu=v8" CC_LD_RT="-R" GCC332R_LIB=/opt/TWWfsw/gcc332r SSL_LIB=/opt/TWWfsw/libopenssl097/lib/ XML_LIB=/opt/TWWfsw/libxml242/lib XML=/opt/TWWfsw/libxml242 INSTALL_PREFIX=/opt/TWWfsw/ffcall19 CC=gcc ./configure CC="${CC:-gcc}" CFLAGS="${CFLAGS:--O2}" \ LDFLAGS="${CC_LD_RT}${XML_LIB}:${GCC332R_LIB}:${LDFLAGS+${LDFLAGS}}" \ --prefix=${INSTALL_PREFIX} \ --enable-shared
 * -hpux11.11)
 * -hpux10.20)
 * -linux*)
 * -solaris2.[689])

;; esac ]]> <![CDATA[ case "${SB_SYSTYPE}" in ;; gmake clean gmake
 * -hpux11.11)
 * -hpux10.20)

;; ;; esac ]]> <![CDATA[ gmake install ]]>
 * -linux*)
 * -solaris2.[689])

<![CDATA[ case "${SB_SYSTYPE}" in ;; ;; ;; esac ]]>
 * -hpux11.11)
 * -hpux10.20)
 * -linux*)
 * -solaris2.[689])

<module name="gnustep-base"> <build-name>gnustep-base-1.10.1</build-name> <install-name>GNUstep</install-name> <syntaxhighlight path="src/core/gnustep-base-1.10.1.tar.gz"  /> <depend var="GCC332R">gcc332r <depend var="LIBXML">libxml242 <depend var="LIBOPENSSL">libopenssl097 <depend var="LIBEXPAT">libexpat <depend var="FFCALL">ffcall19

<script-header> </script-header>

<![CDATA[

case "${SB_SYSTYPE}" in ;; CFLAGS="-O2 -march=1.1" CC_LD_RT="-Wl,+b -Wl," GCC332R_LIB=/opt/TWWfsw/gcc332r SSL_LIB=/opt/TWWfsw/libopenssl097/lib/ XML_LIB=/opt/TWWfsw/libxml242/lib XML=/opt/TWWfsw/libxml242 ICONV=/opt/TWWfsw/libiconv16 CC=gcc ;; CFLAGS="-O2" CC_LD_RT="-Wl,-rpath," GCCR_LIB=/opt/TWWfsw/gcc332r/lib CC=/opt/TWWfsw/gcc332/bin/gcc . ${INSTALL_PREFIX}/System/Library/Makefiles/GNUstep.sh export LD_LIBRARY_PATH=/opt/TWWfsw/ffcall19:/opt/TWWfsw/libopenssl097/lib:/opt/TWWfsw/gcc332r/lib:$LD_LIBRARY_PATH ./configure CC="${CC:-gcc}" CFLAGS="${CFLAGS:--O2}" \ --prefix=${INSTALL_PREFIX} \ --with-include-flags=-I/opt/TWWfsw/libtiff35/include \ --with-library-flags=-L/opt/TWWfsw/libtiff35/lib \ --with-ffi-include=/opt/TWWfsw/ffcall19/inlcude \ --with-ffi-library=/opt/TWWfsw/ffcall19/lib \ --with-libiconv-library="${ICONV}" \ --with-xml-prefix="${XML}" \ --with-openssl-include=/opt/TWWfsw/libopenssl097/include \ --with-openssl-library=/opt/TWWfsw/libopenssl097/lib \ --disable-xmltest
 * -hpux11.11)
 * -hpux10.20)
 * -linux*)
 * 1) LDFLAGS="${CC_LD_RT}${GCCR_LIB}"

;; CFLAGS="-O2 -mcpu=v8" CC_LD_RT="-R" GCC332R_LIB=/opt/TWWfsw/gcc332r SSL_LIB=/opt/TWWfsw/libopenssl097/lib/ XML_LIB=/opt/TWWfsw/libxml242/lib XML=/opt/TWWfsw/libxml242 ICONV=/opt/TWWfsw/libiconv16 CC=/opt/TWWfsw/bin/gcc . ${INSTALL_PREFIX}/System/Library/Makefiles/GNUstep.sh export LD_LIBRARY_PATH=/opt/TWWfsw/ffcall19:/opt/TWWfsw/libopenssl097/lib:/opt/TWWfsw/gcc332r/lib:$LD_LIBRARY_PATH ./configure CC="${CC:-gcc}" CFLAGS="${CFLAGS:--O2}" LDFLAGS="${CC_LD_RT}${XML_LIB}:${GCC332R_LIB}:${LDFLAGS+${LDFLAGS}}" \ --prefix=${INSTALL_PREFIX} \ --with-include-flags=-I/opt/TWWfsw/libtiff35/include \ --with-library-flags=-L/opt/TWWfsw/libtiff35/lib \ --with-ffi-include=/opt/TWWfsw/ffcall19/inlcude \ --with-ffi-library=/opt/TWWfsw/ffcall19/lib \ --with-libiconv-library="${ICONV}" \ --with-xml-prefix="${XML}" \ --with-openssl-include=/opt/TWWfsw/libopenssl097/include \ --with-openssl-library=/opt/TWWfsw/libopenssl097/lib \ --disable-xmltest
 * -solaris2.[689])

;; esac ]]>

<![CDATA[ case "${SB_SYSTYPE}" in ;; ;; . ${INSTALL_PREFIX}/System/Library/Makefiles/GNUstep.sh export LD_LIBRARY_PATH=/opt/TWWfsw/gcc332r/lib:$LD_LIBRARY_PATH gmake clean gmake ;; . ${INSTALL_PREFIX}/System/Library/Makefiles/GNUstep.sh export LD_LIBRARY_PATH=/opt/TWWfsw/gcc332r/lib:$LD_LIBRARY_PATH gmake clean gmake esac ]]>
 * -hpux11.11)
 * -hpux10.20)
 * -linux*)
 * 1) Turn verbose support in GNUstep's makefile system.
 * 2) gmake messages=yes
 * -solaris2.[689])

<![CDATA[ . ${INSTALL_PREFIX}/System/Library/Makefiles/GNUstep.sh export LD_LIBRARY_PATH=/opt/TWWfsw/gcc332r/lib:$LD_LIBRARY_PATH gmake install ]]>

<![CDATA[ case "${SB_SYSTYPE}" in ;; ;; ;; esac ]]>
 * -hpux11.11)
 * -hpux10.20)
 * -linux*)
 * -solaris2.[689])

<module name="gnustep-gui"> <build-name>gnustep-gui-0.9.4</build-name> <install-name>GNUstep</install-name> <syntaxhighlight path="src/core/gnustep-gui-0.9.4.tar.gz" systype="*-solaris*" /> <depend var="JPEG">jpeg <depend var="UNGIF">libungif <depend var="CUPS">cups1120 <depend var="TIFF">tiff <depend var="PNG">libpng12 <depend var="ASPELL">aspell05

<![CDATA[

case "${SB_SYSTYPE}" in ;; ;; ;; CFLAGS="-O2 -mcpu=v8" CC_LD_RT="-R" JPEG_LIB=/opt/TWWfsw/jpeg/lib UNGIF_LIB=/opt/TWWfsw/libungif/lib CUPSR_LIB=/opt/TWWfsw/cups1120/lib TIFF_LIB=/opt/TWWfsw/tiff/lib PNG_LIB=/opt/TWWfsw/libpng12/lib . ${INSTALL_PREFIX}/System/Library/Makefiles/GNUstep.sh export LD_LIBRARY_PATH=/opt/TWWfsw/gcc332r/lib:$LD_LIBRARY_PATH:/opt/TWWfsw/libpng12/lib:/opt/TWWfsw/cups1120/lib
 * -hpux11.11)
 * -hpux10.20)
 * -linux*)
 * -solaris2.[689])

export PATH=/opt/TWWfsw/cups1120/bin:${PATH} set -x ./configure CC="${CC:-gcc}" CFLAGS="${CFLAGS:--O2}" \ LDFLAGS="${CC_LD_RT}${JPEG_LIB}:${UNGIF_LIB}:/opt/TWWfsw/aspell05/lib:\ ${CUPSR_LIB}:${TIFF_LIB}:\ ${PNG_LIB}:${LDFLAGS+${LDFLAGS}}" \ --prefix=${INSTALL_PREFIX} \ --with-jpeg-include="/opt/TWWfsw/libpng12/include \ -I/opt/TWWfsw/libungif/include \ -I/opt/TWWfsw/tiff/include \ -I/opt/TWWfsw/cups1120/include \ -I/opt/TWWfsw/jpeg/include \ -I/opt/TWWfsw/libopenssl097/include" \ --with-jpeg-library="/opt/TWWfsw/libpng12/lib \ -L/opt/TWWfsw/libungif/lib \ -L/opt/TWWfsw/jpeg/lib \ -L/opt/TWWfsw/cups1120/lib \ -L/opt/TWWfsw/tiff/lib \ -L/opt/TWWfsw/libopenssl097/lib" \ --disable-gsnd esac ]]>    <![CDATA[ case "${SB_SYSTYPE}" in    *-hpux11.11)       ;;     *-hpux10.20) ;;    *-linux*)      ;;     *-solaris2.[689]) . ${INSTALL_PREFIX}/System/Library/Makefiles/GNUstep.sh export LD_LIBRARY_PATH=/opt/TWWfsw/gcc332r/lib:$LD_LIBRARY_PATH:/opt/TWWfsw/libpng12/lib:/opt/TWWfsw/cups1120/lib:/opt/TWWfsw/libpng12/lib gmake ;;    esac ]]>

<![CDATA[ . ${INSTALL_PREFIX}/System/Library/Makefiles/GNUstep.sh    gmake install ]]>

<![CDATA[ case "${SB_SYSTYPE}" in ;; ;; ;;
 * -hpux11.11)
 * -hpux10.20)
 * -linux*)
 * -solaris2.[689])

esac ]]>

<module name="gnustep-back"> <build-name>gnustep-back-0.9.4</build-name> <install-name>GNUstep</install-name> <syntaxhighlight path="src/core/gnustep-back-0.9.4.tar.gz" systype="*-solaris*" />

<![CDATA[ case "${SB_SYSTYPE}" in ;; ;; ;; . ${INSTALL_PREFIX}/System/Library/Makefiles/GNUstep.sh export LD_LIBRARY_PATH=/opt/TWWfsw/gcc332r/lib:$LD_LIBRARY_PATH:/opt/TWWfsw/libpng12/lib:/opt/TWWfsw/cups1120/lib set -x echo $LD_LIBRARY_PATH ./configure CC="${CC:-gcc}" CFLAGS="${CFLAGS:--O2}" \ --prefix=${INSTALL_PREFIX} \ --disable-glx \ --disable-xim \ --disable-glitz \ --enable-server=x11 \ --enable-graphics=xlib \ --with-x esac ]]>    <![CDATA[ case "${SB_SYSTYPE}" in    *-hpux11.11)       ;;     *-hpux10.20) ;;    *-linux*)      ;;     *-solaris2.[689]) . ${INSTALL_PREFIX}/System/Library/Makefiles/GNUstep.sh export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/TWWfsw/libungif/lib:\ /opt/TWWfsw/jpeg/lib:/opt/TWWfsw/cups1120/lib:/opt/TWWfsw/tiff/lib:\ /opt/TWWfsw/libpng12/lib gmake ;;    esac ]]>
 * -hpux11.11)
 * -hpux10.20)
 * -linux*)
 * -solaris2.[689])

<![CDATA[ . ${INSTALL_PREFIX}/System/Library/Makefiles/GNUstep.sh    gmake install ]]>

<![CDATA[ case "${SB_SYSTYPE}" in ;; ;; ;; esac ]]>
 * -hpux11.11)
 * -hpux10.20)
 * -linux*)
 * -solaris2.[689])

<build-name>GWorkspace-0.6.5</build-name> <install-name>GNUstep</install-name> <syntaxhighlight path="src/core/gworkspace-0.6.5.tar.gz" />

<![CDATA[

case "${SB_SYSTYPE}" in ;; ;;
 * -hpux11.11)
 * -hpux10.20)
 * -linux*)

;; . ${INSTALL_PREFIX}/System/Library/Makefiles/GNUstep.sh export LD_LIBRARY_PATH=/opt/TWWfsw/gcc332r/lib:$LD_LIBRARY_PATH:/opt/TWWfsw/libpng12/lib:/opt/TWWfsw/cups1120/lib set -x echo $LD_LIBRARY_PATH ./configure CC="${CC:-gcc}" CFLAGS="${CFLAGS:--O2}" \ --prefix=${INSTALL_PREFIX} \ esac ]]>    <![CDATA[ case "${SB_SYSTYPE}" in    *-hpux11.11)       ;;     *-hpux10.20) ;;    *-linux*)      ;;     *-solaris2.[689]) . ${INSTALL_PREFIX}/System/Library/Makefiles/GNUstep.sh export LD_LIBRARY_PATH=/opt/TWWfsw/gcc332r/lib:$LD_LIBRARY_PATH:/opt/TWWfsw/libpng12/lib:/opt/TWWfsw/cups1120/lib cd FSNode;gmake install export LD_LIBRARY_PATH=/opt/TWWfsw/gcc332r/lib:$LD_LIBRARY_PATH:/opt/TWWfsw/libpng12/lib:/opt/TWWfsw/cups1120/lib cd ..; gmake ;;    esac ]]>
 * -solaris2.[689])

<![CDATA[ . ${INSTALL_PREFIX}/System/Library/Makefiles/GNUstep.sh    gmake install ]]>

<![CDATA[ case "${SB_SYSTYPE}" in ;; ;; ;;
 * -hpux11.11)
 * -hpux10.20)
 * -linux*)
 * -solaris2.[689])

esac ]]>

<module name="gnustep-examples"> <build-name>gnustep-examples-1.0.0</build-name> <install-name>GNUstep</install-name> <syntaxhighlight path="src/core/gnustep-examples-1.0.0.tar.gz" />

<![CDATA[

case "${SB_SYSTYPE}" in ;; ;;
 * -hpux11.11)
 * -hpux10.20)
 * -linux*)

;; esac ]]>    <![CDATA[ case "${SB_SYSTYPE}" in    *-hpux11.11)       ;;     *-hpux10.20) ;;    *-linux*)      ;;     *-solaris2.[689]) . ${INSTALL_PREFIX}/System/Library/Makefiles/GNUstep.sh export LD_LIBRARY_PATH=/opt/TWWfsw/gcc332r/lib:$LD_LIBRARY_PATH:/opt/TWWfsw/libpng12/lib:/opt/TWWfsw/cups1120/lib cd FSNode;gmake install export LD_LIBRARY_PATH=/opt/TWWfsw/gcc332r/lib:$LD_LIBRARY_PATH:/opt/TWWfsw/libpng12/lib:/opt/TWWfsw/cups1120/lib cd ..; gmake ;;    esac ]]>
 * -solaris2.[689])

<![CDATA[ . ${INSTALL_PREFIX}/System/Library/Makefiles/GNUstep.sh    gmake install ]]>

<![CDATA[ case "${SB_SYSTYPE}" in ;; ;; ;;
 * -hpux11.11)
 * -hpux10.20)
 * -linux*)
 * -solaris2.[689])

esac ]]>

Gnustep core packages

[root]

Package build: gnustep-core-1.0.pb in a XML file
This pb file can reproduce the package build process with following command to generate a native package for a local PMS.

pb -1 gnustep-core-1.10.pb

Note: HPUX portion of instruction is most likely not correct. [root] cat gnustep-core-1.10.pb <?xml version="1.0"?> <package name="gnustep-core" version="1.10" revision="1"> <package-manager name="depot"> GNUstep GNU Free Software Foundation. GNUstep is a cross-platform, object-oriented framework for desktop application development. <install-name>GNUstep</install-name>

<pkgname-base>TWccase</pkgname-base>

1.10      1

</package-manager>

<package-manager name="pkgadd"> System Environment/Daemons GNUstep GNU Free Software Foundation. GNUstep is a cross-platform, object-oriented framework for desktop application development.

<install-name>GNUstep</install-name> <pkgname-base>GNUstp1a</pkgname-base> 1.10      1

<change date="2004 Sept 28" revision="1" author="T.J. Yang" email="tj_yang@hotmail.com"> GNUstep core 1.10 for Solaris </package-manager>

<package-manager name="rpm4"> System Environment/Daemons ClearCase 1.10 GNU Free Software Foundation.

GNUstep is a cross-platform, object-oriented framework for desktop application development.

<install-name>GNUstep</install-name>

<pkgname-base>TWgnustep</pkgname-base>

1.10      1

<postinstall path="pkg/postinstall-linux"/> <preremove  path="pkg/preremove-linux"/>

</package-manager> [root]

Makefile entry to automate the sb,pb and package upload to package depot
This is a snipped makefile for showing the gnustep-core-1.10 task in a makefile.

gnustep-core-1.10: \ /opt/TWWfsw/gnustep-core-1.10 /opt/dist/cd/GNUstp1au gnustep-core-1.10-gen-pkg-inst gnustep-core-1.10-upload

/opt/TWWfsw/gnustep-core-1.10: /opt/TWWfsw/ffcall19 \ /opt/TWWfsw/GNUstep/System/Library/Makefiles \ /opt/TWWfsw/GNUstep/System/Library/Libraries/Resources/gnustep-base/Languages \ /opt/TWWfsw/GNUstep/System/Library/KeyBindings \ /opt/TWWfsw/GNUstep/System/Library/Documentation/man

/opt/TWWfsw/ffcall19: ${SB} -m ffcall ${SRCDIR}/gnustep-core-1.10/gnustep-core-1.10.sb       ${SB} -m ffcall -i ${SRCDIR}/gnustep-core-1.10/gnustep-core-1.10.sb /opt/TWWfsw/GNUstep/System/Library/Makefiles: ${SB} -m gnustep-make ${SRCDIR}/gnustep-core-1.10/gnustep-core-1.10.sb       ${SB} -m gnustep-make -i ${SRCDIR}/gnustep-core-1.10/gnustep-core-1.10.sb /opt/TWWfsw/GNUstep/System/Library/Libraries/Resources/gnustep-base/Languages: ${SB} -m gnustep-base ${SRCDIR}/gnustep-core-1.10/gnustep-core-1.10.sb       ${SB} -m gnustep-base -i ${SRCDIR}/gnustep-core-1.10/gnustep-core-1.10.sb /opt/TWWfsw/GNUstep/System/Library/KeyBindings: ${SB} -m gnustep-gui ${SRCDIR}/gnustep-core-1.10/gnustep-core-1.10.sb       ${SB} -m gnustep-gui -i  ${SRCDIR}/gnustep-core-1.10/gnustep-core-1.10.sb /opt/TWWfsw/GNUstep/System/Library/Documentation/man: ${SB} -m gnustep-back ${SRCDIR}/gnustep-core-1.10/gnustep-core-1.10.sb       ${SB} -m gnustep-back -i ${SRCDIR}/gnustep-core-1.10/gnustep-core-1.10.sb /opt/dist/cd/GNUstp1au: ${PB} -1 ${SRCDIR}/gnustep-core-1.10/gnustep-core-1.10.pb gnustep-core-1.10-gen-pkg-inst: ${GPD} ${SRCDIR}/gnustep-core-1.10/gnustep-core-1.10.pb >> /opt/dist/cd/pkg-db.xml (cd /opt/dist/cd;zip data.zip  GNUstp1a* ;${M5S}  data.zip |awk '{print $$1}' > data.zip.md5) (cd /opt/dist/cd;zip -r gnustep-core-1.10.pkgadd.pkg-inst pkg-db.xml data.zip data.zip.md5; ${M5S}  gnustep-core-1.10.pkgadd.pkg-inst  |awk '{print $$1}' > gnustep-core-1.10.pkgadd.pkg-inst.md5) cd /opt/dist/cd;rm -f pkg-db.xml data.zip data.zip.md5 gnustep-core-1.10-upload: cd /opt/dist/cd;${RSYNC} -azpv gnustep-core-1.10.pkgadd.pkg-inst gnustep-core-1.10.pkgadd.pkg-inst.md5 root@gnustep.example.com:${DEST}/${ARCHI} cd /opt/dist/cd;rm -f /opt/dist/cd/pkg-db.xml gnustep-core-1.10.pkgadd.pkg-inst gnustep-core-1.10.pkgadd.pkg-inst.md5 gnustep-core-1.10-clean: rm -rf /opt/TWWfsw/GNUstep /opt/dist/cd/GNUstp1a*

title: CPAM with TWW/GNUstep and TWW HPMS


text:
CPAM with TWW/Authors

= Authors = T.J. Yang

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

title: CPAM with TWW/Authors


text:
Entomology/What are arachnids?

Introduction
Arachnids are commonly mistaken for insects. The group includes spiders, scorpions, ticks and sun-spiders (which are not real spiders).

title: Entomology/What are arachnids?


text: Template:Chordata keys

title: Template:Chordata keys


text: Template:Carnivora keys

title: Template:Carnivora keys


text: Template:Aves keys

title: Template:Aves keys


text: Template:Animalia keys

title: Template:Animalia keys


text:
The Unofficial Enlightenment User's Manual/Enlightenment17 Theming Tutorial

This is the tutorial to create and design themes for the Window Manager Enlightenment DR17.

What we need

If you don't know how to install Enlightenment17 Themes, go to (Un)official Enlightenment Documentation

Themes are not yet a part of Enlightenment17. If you want to install this nevertheless, you must place a new theme in the ~/.e/e/themes/ directory and name it "default.eet" or if you have a very recent build, name it "default.edj", because the .eet extension has been depreciated. Then restart Enlightenment with "enlightenment_remote -restart".

Further discussion like this belongs on the talk page.


text:
User talk:Popski

Thanks for your notice, I deleted the Light Cubes book. You can also put notes like this on the Votes for deletion page. --Andreas 21:32, 20 Mar 2005 (UTC)

Consider Moving?
Popski,

I see you've already found this page:

http://en.wikibooks.org/wiki/Blender_3D

Would you consider moving your Memobook wikibook? Right now it is here:

http://en.wikibooks.org/wiki/Blender_MemoBook

It seems to make more sense (to me, anyways) if it's here:

http://en.wikibooks.org/wiki/Blender_3D:_MemoBook

... and we can keep all the English Blender 3D books under http://en.wikibooks.org/wiki/Blender_3D

Let me know. Thanx. --Spiderworm 15:13, 31 Mar 2005 (UTC)

 * Ok, done.

.blend?
Popski,

Would you mind sharing the .blends for your pawns with the material settings you used? I really like them and would like to create a materials tute with them. --Spiderworm 18:59, 5 Apr 2005 (UTC)

 * No problem Spiderworm, but I am looking for a global solution of sharing .blend files. The best would be if we could upload and download .blend files on Commons, but for this we will have to wait... You can read more about this topic here. Second reasonable place for this is Open Clip Art Library. Answer about this option you can read here. Maybe is on Blender Community to do this. I didn't ask them yet... In the meantime I will try to collect this files and put them somewhere on Ljudmila.org. --Popski 10:58, 7 Apr 2005 (UTC)

 * I absolutely agree about putting them on the commons, and in fact several days ago put up this feature request http://bugzilla.wikimedia.org/show_bug.cgi?id=1790 ....  haven't seen any action on it and don't know if there will be.  Maybe we can find another, temporary host for these things...  I do have a website will some free space and could fit some blends on there, still thinking about it.  I hope the wikimedia folks will allow these other sorts of files because I could see it being very beneficial for Blender users.  --Spiderworm 18:13, 7 Apr 2005 (UTC)

 * We could wait for years for our public 3D model repository... :/ Ok, Spiderworm you can download models temporary from my home server. Have fun! --Popski 13:45, 23 Apr 2005 (UTC)

 * Here is now possible to upload also .blend files: http://www.ourmedia.org --Popski 09:42, 27 May 2005 (UTC)

 * Here is talk about uploading all this files.--Popski 19:12, 1 September 2005 (UTC)

NeoRandom Chess
This seems like primary research to me, which as a general rule we don't allow. See About for details. - Aya T E C 19:11, 17 August 2005 (UTC)

Moving/Renaming of NeoRandom Chess
I hope you notice that I didn't delete the NeoRandom Chess Wikibook, and I don't intend to either. From the discussion on the Votes for deletion regarding this Wikibook, the concensus (from what I was able to read as well as my own opinion) was to keep this Wikibook, but to rename it to merge it into the larger Chess Wikibook. I know you consider this to be your own invention, and I have no problem with that either. In terms of renaming the page, you are also welcome to change it back, or to rename it from a more generic "Random Opening Chess" back to "NeoRandom Chess". As a registered user you have this capability... it is not something that is exclusive to any admin or developer. Just try to avoid getting into a page move fight, and make any changes of that nature something that is discussed on the "discussion page" of any Wikibook module you are working on first.

Seriously, I want to thank you for your contributions here on Wikibooks, and I hope that you contribute much more to this project. There are many positive things that can happen here, and I hope you don't get the wrong impressions about anybody else trying to make Wikibooks a more productive place to be at. It is very likely that the NeoRandom chess page will be here on Wikibooks for several years, perhaps long after you have moved on and do other things with your life besides contribute to Wikibooks. By becoming a sub-page of the Chess Wikibook, that future will be ensured much better than if it were simply left as a stand-alone "article". I also think it is a neat variant of Chess, and when I get a good Chess partner I may try it out in a "quick game". --Rob Horning 23:30, 2 September 2005 (UTC)

Hi Popski
Hey man, remember me? Just wanted to show you my new wikiblog. User:Spiderworm/blog --Spiderworm 16:56, 2 September 2005 (UTC)

 * Hey! Of course remember you I.! That's why useful history is :)
 * that's how Yoda twin speaks.

 * Where your User:Spiderworm/plok is? A, I knew it that is somewhere here around. brb --Jodopopski

title: User talk:Popski


text:
User:Guanabot~enwikibooks

I am Guanaco. I am currently fixing double redirects. Guanaco 22:33, 14 November 2005 (UTC)

This user is an officially registered bot. It was registered on the 17:44, 31 Mar 2005 (UTC). In case this bot needs to be removed its status, please contact a steward at Requests for permissions - m:user:Anthere

title: User:Guanabot~enwikibooks


text:
Baseball/Hitting Basics

Finding a bat
The first thing you need to do is find a bat that suits you. The bat should be as tall as your hip when stood on the ground. The length may vary if you are a somewhat experienced batter and you know what length you like. Weight is a key issue when looking for a bat. As bat speed is key, a hitter should look for the lightest possible stick to swing, but keep this in mind: from a physics perspective, the formula $$m1v1i x m2v2i = m1v2f x m2v2f$$ where m1 is the mass of the ball, m2 is the bat, and v1,v2 are their respective speeds(i being initial, f being final). Wacky math aside, a heavier bat moving at the same speed as a less massive bat will empart more force on the ball, making the difference between a high fly, and a home run. An appropriate test for finding a bat of proper weight for your strength category is to hold the bat handle in one hand, parallel to the ground for 45 seconds. If you can hold it up, you should be strong enough to swing the stick. This is just a general rule of thumb. if you find your speed is too slow, shave two ounces off the bats' mass.

Gripping the bat
The grip the batter uses is important because it determines the bat speed. Your bottom hand should be placed half an inch from the knob of the bat. The “door-knocking” knuckles of you top hand should be roughly aligned with the "door-knocking" knuckles of your bottom hand. Reach back behind you and touch the head of the bat to your buttocks or your lower back. Now bring the bat around and hit the ground. Examine your knuckles and this is where you should try to have them. Remember to grip the bat loosely.

The Stance, feet
Lets first start from the feet and work our way up. This process is long and perhaps the most important to get right. First, you need to place your front foot about 6-8 inches away from the top corner of the plate. Place you back foot parallel to your front foot and about shoulder-width apart. Now tilt your front foot at a little less than a 45-degree angle. It should be pointing at about the space between the second basemen and the first basemen (given you are a right handed batter). Now bend your knees and transfer your weight so that about 75% of it is resting on your back foot. Also, always remember to be on the balls of your feet, and not flatfooted.

The Stance, body, arms, and head
Now that you have the feet set, next on the list is the rest of your body. Your hip, shoulder and head should all be pointing to the pitcher. The hands should be held around the batters dominant breast. The back elbow should be at a 45-degree angle downward allowing for the bat to be at a 45-degree angle across your shoulder. The top of your top hand should be in the general area of the top of your back shoulder. Your chin should be in the area between either on your front shoulder or about an inch from it, and your head needs to be still at all times. Make sure you are comfortable because you must be relaxed in order to be a great hitter.

The Stride and Load
A batters stride should be short and only about three to four inches. All you're going to do is take a little step forward and point your toes toward the pitcher, keep in mind that most of your weight is on your back foot. Now onto the load. In the load technique you should shift your upper body weight slightly back in order to get that extra bit of power before you swing. Note that the Stride and Load are done at the same time. Also, against a live pitcher, the batters stride foot should go down as well as upper body weight shifting back at exactly the same time as the pitcher's front foot hits the ground. This is done in order to help your timing and reduce the risk of getting thrown off by a curve or change up.

Head action and ball tracking
The batter's head needs to be perfectly still and he must watch the ball from the pitcher's hand to the time it hits the bat. Your chin should transfer from your front shoulder to your back shoulder during the swing of the bat. You should make connection with the ball out in front of your body. Note that this all takes place during the swing.

The Swing
After the load and stride the next step for you is to swing the bat. The swing should be in a straight and slightly downward motion, always keeping your hands on the inside of your body. While this is happening the batter's back foot should pivot and the hips would turn forward so they too are now facing the pitcher. At the same time your hips are completely forward, the bat should be parallel to the ground and about waist height with both arms fully extended on a downward slant. This is where the point of contact should be.

Extension and Finish
After the point of contact, your arms should extend to shoulder height. At this point your wrists will involuntarily flip over and the bat should be pointing at the left fielder (given again that you are a right handed batter). Even during and after the extension, your head should still be looking at the invisible spot that was once the point of contact. The final step is to let the bat carry itself over your shoulder and run to first base.

title: Baseball/Hitting Basics


text:
Talk:Baseball/Hitting Basics

History from the Wikipedia page

 * (cur) (last) 23:18, 20 Mar 2005 Howrealisreal
 * (cur) (last) 23:16, 20 Mar 2005 Howrealisreal m (cleanup request)
 * (cur) (last) 23:13, 20 Mar 2005 64.12.116.201

title: Talk:Baseball/Hitting Basics


text:
Dichotomous Key/Chiroptera

1

 * Claw on second toes of the forelimb
 * Present -
 * Not present -

3: Microchiroptera

 * Tail length
 * Long - ../Rhinopomatidae/
 * Short or absent -

4

 * Shape of posterior tip of last caudal vertebrae
 * T-shaped - ../Nycteridae/
 * Same as other vertebrae -

5

 * Suction cups on wrists and ankles
 * Present -
 * Not present -

6

 * Number of phalanges
 * Two, united for most of their length - ../Myzopodidae/
 * Other - ../Thyropteridae/

7

 * Secondary fold on tragus
 * Present - ../Mormoopidae/
 * Not present, or tragus not present -

8

 * Tragus
 * Divided - ../Megadermatidae/
 * Not divided, or not present -

title: Dichotomous Key/Chiroptera


text: Template:Mollusca keys

title: Template:Mollusca keys


text:
User:Brevam

Brevam is a Japanese Wikimedian.

ja:User:Brevam

title: User:Brevam


text:
Dichotomous Key/Cephalopoda

1

 * External shell
 * Present - ../Nautiloidea/
 * Not present - 2

2: Coleoidea

 * Modified (or lost) arm pair
 * Arm pair IV - 3
 * Arm pair II - 4

3: Decapodiformes

 * Cornea
 * Present - 6
 * Not present - 5

4: Octopodiformes

 * Photophores
 * Present - Vampyroteuthis infernalis
 * Not present - ../Octopoda/

5

 * Shell shape
 * Horn-shaped - Spirula spirula
 * Other or not present - 7

6: Sepioidea

 * Cuttlebone
 * Present - ../Sepiidae/
 * Not present - 8

7

 * Gladius
 * Present - ../Oegopsida/
 * Not present - 10

8: Sepiolida

 * Depressions on funnel locking-apparatus
 * One - ../Sepiolidae/
 * Two, or apparatus fused - ../Sepiadariidae/

9

 * Adhesive organ on dorsal surface of mantle
 * Present - ../Idiosepiidae/
 * Not present - ../Myopsida/

10

 * Branchial canals in gills
 * Present - 11
 * Not present - 9

11: Bathyteuthoida

 * Buccal connectives attaching to border of arms IV
 * Dorsal border of arms IV - ../Bathyteuthidae/
 * Ventral border of arms IV - ../Chtenopterygidae/

cs:Dichotomický klíč:Cephalopoda

title: Dichotomous Key/Cephalopoda


text:
Network Plus Certification

This wikibook discusses the information necessary to obtain the CompTIA Network+ certification. The Network+ certification is an internationally recognized validation of the technical knowledge required of foundation-level IT network practitioners. The CompTIA Network+ and A+ exams can be applied together toward the Microsoft Certified Systems Administrator (MCSA) program, and other corporations such as Novell, Cisco and HP also recognize CompTIA Network+ as part of their certification tracks.

The Network+ certification ensures that the successful candidate has the important knowledge and skills necessary to manage, maintain, troubleshoot, install, operate and configure basic network infrastructure, describe networking technologies, basic design principles, and adhere to wiring standards and use testing tools. Although not a prerequisite, it is recommended that CompTIA Network+ candidates have at least nine months of experience in network support or administration or adequate academic training, along with a CompTIA A+ certification.

Book contents

 * /Introduction/ [[Image:100%.svg]]
 * Exam Objectives [[Image:100%.svg]]
 * Domain 1: Network Technologies [[Image:25%.svg]]
 * Domain 2: Network Media and Topologies [[Image:25%.svg]]
 * Domain 3: Network Devices [[Image:25%.svg]]
 * Domain 4: Network Management [[Image:25%.svg]]
 * Domain 5: Network Tools [[Image:25%.svg]]
 * Domain 6: Network Security [[Image:25%.svg]]
 * Appendix A: Memory Aids [[Image:25%.svg]]

Training

 * PowerCert.com

Related Wikibooks

 * A+ Certification
 * CCNA Certification
 * Communication Networks
 * FOSS: Network Infrastructure and Security
 * Wireless Home Network Basics

title: Network Plus Certification


text:
Dichotomous Key/Proboscidea

1

 * Fingers at tip of trunk
 * One - 2
 * Two - Asian Elephant, Elephas maximus

2: Loxodonta

 * Ear shape
 * Rounded - African savannah elephant, Loxodonta africana
 * Pointed - African forest elephant, Loxodonta cyclotis

title: Dichotomous Key/Proboscidea


text:
Dichotomous Key/Amphibia

1

 * Number of vertebrae
 * Nine or fewer - 2
 * More than nine - 3

Bold text

2: Salientia

 * Tailwagging muscles
 * Present - 6
 * Not present - 7

3

 * Tail
 * Present in all life stages - 5
 * Not present in all life stages - 4

5: Caudata

 * Narrow grooves between each nostril and the upper lip
 * Present - Plethodontidae
 * Not present - 14

6

 * Inscriptional ribs
 * Present - Leiopelmatidae
 * Not present - Ascaphus truei

7

 * Endochondral ossifications in the hyoid plate (distinct from parahyoid bones)
 * Present - Bombinatoridae''
 * Not present - 8

8

 * Narrow epipubic cartilage plate
 * Present - Discoglossidae
 * Not present - 9

9

 * Astragalus and calcaneum
 * Fused - Pelodytidae
 * Not fused - 10

10

 * Metatarsal spade
 * Present - 13
 * Not present - 11

11

 * Tongue shape
 * Paddle-shaped - Megophryidae
 * Other or not existent - 12

12

 * Tongue
 * Present - Neobatrachia
 * Not present - Pipidae

13

 * Elongate atlantal neural arch
 * Present - Rhinophrynus dorsalis
 * Not present - Pelobatidae

14

 * Fertilization
 * Internal - 15
 * External -

15: Salamandroidea
Dicamptodontidae, Salamandridae, Ambystomatidae, Proteidae, Rhyacotritonidae, Amphiumidae
 * Premaxillae
 * Fused - 18
 * Separated - 19

16

 * Metamorphosis
 * Present (fully or partially) - 17
 * Not present - Sirenidae

17: Cryptobranchoidea

 * Metamorphosis
 * Partial - Cryptobranchidae
 * Full - Hynobiidae

18

 * Operculum
 * Present - 20
 * Not present - 21

19

 * Operculum
 * Present - Salamandridae
 * Not present - Amphiumidae

20

 * Lacrimal bone
 * Present - Dicamptodontidae
 * Not present - Ambystomatidae

21

 * Bilaterally paired septomaxillary bones
 * Present - Rhyacotritonidae
 * Not present - Proteidae

title: Dichotomous Key/Amphibia


text:
Dichotomous Key/Dermaptera

1

 * Wings
 * Present - 2
 * Not present - 3

2: Forficulina
Forficulina (Common earwigs) -- This group includes several families and almost all species (about 2200 world wide) you will find.

3

 * Shape of cerci
 * Filiform - 4
 * Rod-shaped - 5

4: Hemimerina
Only about 20 species living on hamster rats in sub-Saharan Africa. No chance to find elsewhere.

5: Arixenina
Few species, too, living on or close to bats in the Philippines and Borneo (Sarawak) region. No chance to find elsewhere.

title: Dichotomous Key/Dermaptera


text:
Cookbook talk:Samosa

Ingredient missing
It is written in the recipe that flour will be rolled in a ball but there is no actual mention of the amount of flour to use. And maybe an idea of the amount of samosa it will make would be a nice idea. 24.201.116.26 04:18, 21 Mar 2005 (UTC)

One ball makes two samosas. The amount of flour required depends on the size of the samosa and the amount of filling.

-- This recipe is terrible. Olive oil????? use plain vegetable oil, mustard oil or ghee. add cumin and coriander seeds to the mix _________________________________________________________ Where on earth do they use olive oil for Samosas?
 * Thats a good Question! Maybe western world uses it.--Navinsingh133 (discuss • contribs) 20:25, 16 April 2018 (UTC)

Division of Ingredient list into two parts
I suggest breaking of ingredients list into two parts That way it will be more clear and concise. Thank you.--Navinsingh133 (discuss • contribs) 20:25, 16 April 2018 (UTC)
 * Dough for cover
 * Fillings

title: Cookbook talk:Samosa


text:
Talk:How To Build A Computer/Decisions, Decisions, Decisions

If you add or remove a section, please update the TOC on the main page.


text:
Talk:How To Assemble A Desktop PC/Choosing the parts

If you add or remove a section, please update the TOC on the main page.

Page size
The article is currently at 35K. This might cause problems with older browser. I was wondering if we should even care about it and maybe split this up or scale this guide down.

is anyone against splitting it up? -CarbonUnit

How sould we split this up? - CarbonUnit

 * Perhaps move the "secondary components" and "peripherals" sections onto a new page? (The distinction between them is getting more blurry, because manufacturers of "secondary components" that go inside the case are starting to distribute the same functionality in a "peripheral" that plugs into USB or ethernet.) --DavidCary 16:32, 28 December 2005 (UTC)

 * I think it would make sense to split it. IMO, the question is how exactly should it be split up?  I'm thinking each of the major questions could be a subpage, with the list of necessary components linking to each of those subpages.  But that's just my opinion.  Or, choosing the parts, then acquiring the parts, then a description of what to look for in each.  Bpogi 00:13, 22 February 2007 (UTC)

 * I've begun copying individual sections to new subpages. Already finished with CPU; see How_To_Assemble_A_Desktop_PC/Choosing_the_parts/CPU. —Bpogi 03:20, 26 February 2007 (UTC)

 * Looks good so far.
 * Alas, it appears that the CPU section on this page is slowly diverging from the How_To_Assemble_A_Desktop_PC/Choosing_the_parts/CPU page.
 * In the name of Wiki:OnceAndOnlyOnce, I moved all the text from the CPU section of this page to that page.
 * Hopefully that leads to one page with all the best up-to-date information, rather than 2 pages that each have some up-to-date information and some obsolete information.
 * Even though that edit reduced this page from 101,730 bytes to 84,877 bytes, it still seems a bit long to me. What else can we split into a separate page?
 * --DavidCary (discuss • contribs) 18:37, 10 February 2011 (UTC)

On the other hand....
''On the other hand, somebody who is going to be playing the latest games on their new computer  is going to need a lot more graphics power. However, they may not want to spend much on computer  peripherals such as scanners, printers, or webcameras, because they have no interest in such devices. On the other hand, someone may want a computer that offers both office and gaming experiences, and in that case they should expect to spend additional money on peripheral devices, along with  high-powered internal components.''

Sounds wrong.

 * Then fix it! Every page has an edit button on it.Reub2000

Meta: Editing
Section editing seems *horribly* broken here; is there a known reason? --Baylink 00:57, 2 August 2005 (UTC)

Addressing low wage / adventurous teenager groups
You are nicely describing how to build a machine by assembling parts, however, this is likely to be out of the scope for a larger readership of this book. What about the not so unlikely case that one finds a machine on the street waiting to be collected for transport to a landfill site, free for grab, or one is donated one, that one is interested to understand better. This might also be appropriate to readers in the third world. If this proposal gets some backup, then I might start something in that direction. 139.30.161.225 14:59, 8 August 2005 (UTC)

Buying parts
I feel there should be a part on where to get parts. For example, buying parts online can be very cheap, but have problems of their own (such as rebate issues, shipping time, shipping cost, potentially limited warrenty, no way to test the part befroe you get it). Some online distributors which could be noted: www.pricewatch.com, www.newegg.com, www.tigerdirect.com, www.geeks.com.

--24.145.203.118 18:33, 27 August 2005 (UTC)

Places to get parts outside the USA
So far, *all* the online computer dealers I've seen only ship within the USA. And I live in Mexico. So, I'd really like some suggestions about what to do if you're not from the States. 201.128.248.147 02:00, 15 December 2005 (UTC)

 * Find a site that ships computer parts in/to Mexico and add it to the list of sites. -Bpogi 00:20, 22 February 2007 (UTC)

Dual Core
Seeing how dual-core CPU setup is getting quite common these days, I suggest elaborating on that a bit in the CPU section, such as advantages and disadvantages and so forth.

4800dpi resolution
"For most purposes, a mid-range Inkjet Printer will be more than enough for most people, and you will generally want one that is capable of printing around 4800dpi"

Unless you want to print a bunch of photos, is 4800dpi really necessary? Most text and simple graphics are printed well below 1200dpi.

 * Even if you're printing photos, you don't really need 4800dpi. A 3x5" photo at 4800x1200 dpi, about the standard of a mid- to high-end inkjet = 86,400,000 = 86.4 MP.  But it does look better with 4800dpi.  --Bpogi 03:57, 22 February 2007 (UTC)

 * I agree that 1200dpi is more than adequate for text and simple graphics.
 * However, a "pixel" on screen requires more than one "dot" on paper to adequately reproduce. A digital color photograph that looks great at 72 pixels per inch on screen looks horrible when printed on paper at 72 dots per inch or even 300 dots per inch. --DavidCary (discuss • contribs) 17:51, 10 February 2011 (UTC)

dial up is "more than adequate"
Given the number of pages with graphics, ads or other features that any one using the web, even passively, is likely to use, I find the idea that dial up is "more than adequate" misleading. I feel it should be changed to just "adequate" to give the true level of quality offered by dial up. 122.49.141.104 (talk) 03:52, 15 August 2010 (UTC)
 * 1) As someone who was until recently using dial-up, it's not adequate at all for the web. Wikipedia pages will take up to half an hour to load. Dial-up can really only handle IRC and email (oh, and telnet).

 * Most of the stuff that's loaded is either images, flash ads, or excess CSS stuff. If you're still using a low-speed internet connection, you probably want to use a browser that supports hiding images/flash/css until you explicitly want to load them.  Oh, and none of the modern browsers make this an easy task to switch back and forth. --Sigma 7 (talk) 16:52, 15 August 2010 (UTC)

Language Usage
It seems to me that there is some very relaxed usage of language throughout this wikibook. I've slowly begun going through each section and changing the language to a more proper and concise format. It would be nice to have some help though as I'm sure to miss something. Certain sections seem as though they are written by an avid gamer and don't really reflect the general computer market. Please be careful about language use when editing, and make sure to use proper full sentences that get your point across clearly.

 * I'm helping. BTW, please sign comments.  --Bpogi 00:56, 22 February 2007 (UTC)

Audience
There have been other discussions and comments in above topics about the target audience and what information should be included, so I'm just starting this topic for that purpose. Have at it. --Bpogi 21:52, 22 February 2007 (UTC)

I would bet pesos to pizza (the geek version of dollars to donuts) that most people who read this article are near the novice end of the spectrum. Tech professionals already know this stuff and would not go out of their way to look for a generic guide, although they might look for information specific to the hardware they are looking to install. Even power users, or people who think they are power users, are apt to just dive in and start playing with the parts. With that in mind, you should assume that the reader knows little to nothing about standard terminology, safety and compatibility concerns, etc. Peter B. Steiger, Cheyenne WY

Old systems
Mabey you should state at the beginnig whether this book will tell you how to assemble a system out of old parts.

The problem with that is that old parts can be too slow for modern OSes, unless you are running Linux. A lot of the parts in old PCs are incompatible with today's hardware and software.Microsoftwin108576 (discuss • contribs) 22:21, 26 December 2015 (UTC)

Motherboard Bandwidths
Motherboard bandwidths do not seem to be mentioned in this WikiBook. Sometimes there can be subtle issues in motherboard bandwidth, and it is important to check for them. An important example is the 780i, in which there is not truly enough northbridge-southbridge bandwidth to feed system RAM to its two PCI-E 2.0 x16 slots, nor is the interconnect bandwidth truly sufficient. Note: This does NOT mean the 780i motherboard is weak on bandwidth compared to the competition.

Windows vs Linux
Hello,

I feel this WikiBook is biased towards Windows, it says that Windows is a "perfect" solution for "every" need, whereas GNU/Linux based Systems are a "good" alternative, also mentioning "preform many of the same functions as Windows and features similar programs". The text In my humble opinion, neither is perfect and will ever be and maybe we should also mention that Linux/UNIX can do lots of things Windows CANNOT do, even for Joe Customer ( supports more/especially older hardware), is safer, has less virii and other malware, allows better multiuser usage ( ~/bin, ~/etc, etc.. etc.. ) and can have higher performance in a lot of situations, especially with lots of programs loaded and regarding program launch time.

We should also consider the "ranking" as well as the fact that some VERY obsolete systems are mentioned( even though we could mention FreeDOS as arguably the "best"/ most modern DOS ), whereas some other, maybe more pro-user oriented but still easy-to-use systems are not mentioned at all ( I think Solaris here, has very good support, even the free one is great + great application integration + good security/performance/updates/etc + easy installer) 84.161.35.36 (talk) 16:46, 22 April 2009 (UTC)

Prices of parts
The part prices given in the text are useless to anyone outside of North America. Someone's added a link to XE, but manufacturers sell components in Australia (this also may be true in other areas) at a much higher price than amount in US$ and shipping. Perhaps a more comprehensive list of shops would be better. 182.239.140.221 (talk) 07:34, 22 August 2010 (UTC)

 * Prices within the United States are a moving target and are fairly useless even to American readers. They're of marginal usefulness for comparing relative prices between different types of hardware at an instant in time. —QuicksilverT @ 19:56, 21 February 2011 (UTC)

needs updating
this book appears to be at least 4 or 5 years out of date. I did some work on this page, but more remains. Aunva6 (discuss • contribs) 21:42, 7 February 2013 (UTC)

Split
Should this page be split into parts further? (As has been done for the CPU page?) --Mbrickn (discuss • contribs) 21:38, 17 August 2021 (UTC)


text:
User:Sunny256

Yet another user page on wiki* I have to update. Hm. Dozens of them now, so I'll just point you to the versions on the English and Norwegian wikipedia.

title: User:Sunny256


text:
Talk:A Neutral Look at Operating Systems

 * For the old history from A Neutral Look at Operating Systems/Proprietary OSs see /Archive 1
 * For the old history from Talk:A Neutral Look at Operating Systems/Proprietary OSs see /Archive 2
 * For the old history from A Neutral Look at Operating Systems/Open Source OSs see /Archive 3

Accuracy of the information provided
T''hanks for taking time to clarify this. The matter I raised was of technical accuracy and not politics. My comments are inline ..''

I would like to comment about the information on Linux operating system. I had created that section but it was edited and some of the information was edited. The edited form is inaccurate and full of mis-information.
 * There is no OS called Linux in this world, Linux is name of the kernel which is a small part of the OS (if you call the OS linux the you should call windows kernel.dll and OS X -> MAC-3, name of the respective kernels). Word linux for OS is a misnomer, It is a GNU OS with linux kernel. GNU OS also runs with BSD kernel and HURD kernel. I believe this needs to be clarified in the document. The OS is called GNU/Linux and not Linux.

I was in primary school then, but does that matter? It is traditional for the term "OS" and the name of any particular OS to refer both to the kernel and to the system in general. Sorry if you don't like that, but that's the way it is. When Linux® was being formed, people like Theodore T'so and H. J. Lu went looking for userspace code. This is much like AT&T and Sun did in grabbing BSD code, much like Richard Stallman planned to do, and of course the obvious thing that anybody would do. Some code, none of it being terribly special, came from the GNU project. Please note that a BSD C library existed, and the gcc compiler was not exactly a major undertaking. The code you see today exists primarily by the efforts of companies that consider themselves to be Linux® vendors. The core Linux® developers, to this very day, do not use the term "GNU/Linux". A good number of them seem to find it offensive. What you are seeing here is a political power grab. Richard Stallman has even changed some of the FSF software and licenses in an effort to force his views on the world. Even if the idea of cobbling together a full system from available parts was unique to Richard Stallman (hah!), he would still have no moral right to rename the efforts of others. The Hurd has swiped many parts (ext2 driver, hardware drivers, TCP/IP...) from Linux®, yet Richard Stallman refuses to acknowledge this in the name of his OS. Apparantly he doesn't see the hypocracy. One final thing... the term "GNU/Linux" is a violation of the Linux® trademark. You're not allowed to abuse a trademark like that. AlbertCahalan 06:51, 26 Apr 2005 (UTC) ''I believe its your preference (and respect it), if you want to call the whole system Linux, but I would be nice if we clarify in the document the system known as Linux&reg has Linux kernel and other SW which comes from other sources. So that next time a Apache bug is published people do not think it as a Linux bug. May be GNU/Linux is violation of trademark (do not know legal issues).''
 * Being a Linux® developer for a decade, I happen to know this is wrong. I was there; were you?

 * Linux is Open Source SW -> Linux Kernel and most of the SW comes under GPL hence its a Free SW and not Open Source. There is a subtle difference bw Free and Open Source but subtituting one for other leads to mis information. (SW like Mozilla, covered by MPL, BSD etc are open source but not Free).

''again from purely technical accuracy point of view shouldn't we tell that stuff like Kernel, gcc gnome etc are Free SW while mozilla etc are open source, and pointg the readers to definitions and difference between two. '' These are the major concerns that I have, I hope you would correct it as soon as possible so that it becomes more factual.
 * When using the term "operating system" to mean the whole system, Mozilla is included. It comes on the same CD-ROM as everything else and it gets installed along with everything else. There are other examples if you now suddenly wish to use a restrictive definition of "operating system". So it is correct to use the term "Open Source". AlbertCahalan 06:51, 26 Apr 2005 (UTC)

 * Let's not perpetuate Orwellian newspeak, political correctness, and similar. Linux® is an OS developed by Linus Torvalds and others. AlbertCahalan 06:54, 26 Apr 2005 (UTC)

''Agreed may be these details are out of scope of the document but I believe they would add technical accuracy to it. Besides my intent has been to point out this rather than promoting any point of view.''

The notion of technical accuracy applied to political information like Free vs Open and Linux vs GNU / Linux is ludicrous. And who cares anyways?

The subject of OSes is more than large enough to deserve several books devoted to it. And those books have more merit that stay away from politics. There are a thousand websites where users can educate themselves about the politics of FLOSS and Linux, why should all that crud be reproduced here? It boggles the mind. A book on the politics of OSes has about as much educational value as The Book of Crime.

If you want to discuss the politics of OSes, move it to a more aptly named book, like The Politics Of Operating Systems, then at least people could stay away from the book since they'd know it had nothing of interest. Truth in advertising is a good idea!

"Red Hat GNU/Linux" vs. "Red Hat Linux"
Someone renamed all the Linux distributions: http://en.wikibooks.org/w/index.php?title=A_Neutral_Look_at_Operating_Systems&diff=0&oldid=137024

While I admire the w:Be Bold technique of *doing* something rather than whining about it on the talk page, I reverted those changes.

In my opinion, people that make stuff can call it whatever counter-intuitive, incorrect name they want. Does "mince meat pie" (Cookbook:Mincemeat Tart) actually have any meat in it ? No. But when a chef gives me tasty pastries, I let him call it whatever he wants to call it. [To go a little off topic, it's called Mincemeat because traditionally it was actually made with meat, and I don't just mean suet. Disgusting idea, I know]

This thing may, technically, be a "GNU/Linux" distribution from "Red Hat, Inc.". But if the people that make it give it the name "Red Hat Linux", then that is its name. They are, of course, free to change that name to something technically more accurate.

--DavidCary 07:33, 8 Jun 2005 (UTC)

Worse than that: the whole "GNU/" thing is Stallman's personal and illegitimate effort to take credit for the efforts of others. He's had quite some success pushing the idea with people who don't know the history behind Linux, GNU, BSD, X11, TeX, and all the rest. AlbertCahalan 23:05, 8 Jun 2005 (UTC)

To Do List
''Hey... I thought I'd add a bit of direction to this before it really gets underway. Add a few ideas if you have them, and if they seem to be complete, remove them. Nothing worse than trying to start something that's already finished :P'' --Noogz 07:11, 21 Mar 2005 (UTC)

 * Write information on various Linux distros. Debian is already here(writing something about Debian-based systems? Ubuntu, etc.), but I'd like to see the rest of the Big 6 (Red Hat, SuSE, Mandrake, Gentoo and Slackware) get some info; even add a few of the BSD's.  If this does happen, seperate the BSDs from the Linucies under the "Open Source" heading.
 * Write info on differences between versions of Windows (e.g. Why one should upgrade from 98 to XP).
 * Explain (dis)advantages of both proprietary and FLOSS OSes (IN GENERAL).
 * Identify strengths/weaknesses of each system (e.g. OS X is good for Multimedia; Windows is good for Gaming).

 * "Why one should upgrade from 98 to XP"
 * Was _THAT_ an _UP_grade?

Absolutely not. Nothing on that list should be in this book. Even proprietary vs FLOSS is a general software development issue and has nothing to do with operating systems. If you're going to write a book about operating systems and you're going to bother calling it "neutral", there shouldn't be any irrelevant political crap.

Structure
The strucure of your book is somewhat wrong, as the for-profit Linux distributions are still GNU/Linux operating systems, and Mac Os X is still a BSD operationg system based on an open source core. I propose the following structure instead:

 * 1) Windows-based OS
 * 2) MS WinXP/Win2003
 * 3) Unix-based OS
 * 4) Solaris
 * 5) BSD
 * 6) partly proprietary distributions
 * 7) Mac OS X
 * 8) free distributions
 * 9) FreeBSD
 * 10) NetBSD
 * 11) OpenBSD
 * 12) GNU/Linux
 * 13) partly proprietary distributions
 * 14) Red Hat and Fedora
 * 15) SUSE
 * 16) free distributions
 * 17) Debian
 * 18) Slackware
 * 19) Gentoo
 * 20) Mandrake
 * I see your point. I will soon make some changes that should resolve some of these issues. This kind of a book is kidna hard to categorize...--Hyperlink 21:38, 22 Mar 2005 (UTC)
 * This sounds better since Red Hat is not an OS, but a distribution. 24.56.22.70 03:13, 16 May 2005 (UTC)
 * I agree, when I first read the TOC, I immedatly thought that this needed to be done. How detailed should this be?  Should this book only cover modern operating systems, or should we add in obsolete ones?  (Windows 95 and Mac OS 9 come to mind) --Zeal17 15:44, 19 August 2005 (UTC)
 * As of now, the structure is still a mess. The Open Source OSs module has an incomplete TOC. Someone editted the Linux module, and now the TOC links in A Neutral Look at Operating Systems to Linux distros are broken. I suggest the flattening of the structure to remove the useless Open Source OSs page, and an update of the table of contents. Kernigh 03:01, 2 October 2005 (UTC)
 * I fixed the TOC to become functional. There are no OSs missing in the main TOC, if I did this right, except for the Linux distros which are grouped into categories. I also gave a minimal fix to the A Neutral Look at Operating Systems/Open Source OSs submodule. I like the unsigned structure presented above, but for now, I will not attempt to change the structure. Kernigh 21:55, 3 October 2005 (UTC)

The structure of the book isn't "somewhat wrong", it is grossly and egregiously wrong. The notion that "for profit" and "open source" (political monikers) have anything at all to do with the nature of operating systems is contemptible. Whoever made the current structure demonstrated cynicism equal to the most corrupt politicians in history. This isn't an advocacy page for Linux goddamnit!

The list should be structured historically, with Unix under a single heading and including both Linux, BSD and Unix System V as subheadings. There should be absolutely no mentions of Redhat, Gentoo or other distributions. There should be a Unix-like category to have somewhere to put Plan 9. DOS falls into the category of CP/M derivatives and hence so do Windows and ReactOS. OS/2 should be put under CP/M-like. Mac should be in its own category, with OS X being shared between Mac and Unix.

As for Kernigh's claim that "there are no OSes missing", it's obvious that he knows nothing about operating systems. There's no mention of EROS, Plan 9, or QNX. And that's just modern OSes.

 * Oops... what I meant by "no OSes missing" was that there would be no OSes in the book that are not linked from the TOC. It is obvious that there are some OSes missing from the book. --Kernigh 20:27, 24 October 2005 (UTC)

 * Welcome to Wikibooks! It would improve this book if you contributed sections for EROS, Plan 9, QNX, and other systems. Also, the split between "proprietary" and "open source" in this book should leave. It does not work because "proprietary" Mac OS X contains some open source code while "open source" Linux distributions sometimes have proprietary code. Meanwhile, the Unix-likes are forced to split into two group. The Unix-likes should be together.

 * I have restored the old TOC to A Neutral Look at Operating Systems. I suggest that someone restructures the TOC to be better. Once the new TOC is finished, remove the old TOC. --Kernigh 20:27, 24 October 2005 (UTC)

New Structure, Redirects, and Red Links
I have rearranged the pages, abolishing the separation between "Proprietary OSs" and "Open Source OSs". Here is the list of redirects which I created when I moved the pages. --Kernigh 04:51, 14 November 2005 (UTC)
 * [/Archive 1|[A Neutral Look at Operating Systems/Proprietary OSs]]
 * A Neutral Look at Operating Systems/Open Source OSs
 * A Neutral Look at Operating Systems/Open Source OSs/Berkeley Software Distribution
 * A Neutral Look at Operating Systems/Open Source OSs/Linux
 * A Neutral Look at Operating Systems/Open Source OSs/FreeDOS
 * A Neutral Look at Operating Systems/Open Source OSs/ReactOS

I left some operating systems in the TOC as red links with Wikipedia articles (including ones from "Proprietary OSs" that were only Wikipedia links). If you have a better idea, then edit the page. --Kernigh 04:51, 14 November 2005 (UTC)

Neutrality
A neutral look on Operating Systems should start with a definition of an operation system and the mechanisms that are used by them. This is independent of the Operating System. Next, each Operating System could be discussed in function of these mechanisms. For example: task scheduling. There are many kinds of the (round robin, multiple priority round robin, etc.). Of course, these 'general' pages could be constructed while developing the specific ones.

''The notion that an operating system can be characterized by a long list of functions and mechanisms is ludicrous. These things are utterly trivial and nobody would learn anything of any significance from such a book. Are you writing a book about operating systems or an outdated technical spec that nobody will use? OSes are characterized by the concepts and principles they use.''

So for example, there are functional OSes, there are object oriented OSes, there are OSes with capabilities, there are stateless OSes and stateful OSes, there are uniform OSes and non-uniform OSes.

 * In theory, but not in practice. EROS and KeyKOS are going nowhere. I see that you wish this to be a book about failed OS experiments. Back in the real world though, we do have more than just UNIX and Windows. Look at embedded systems. We have ThreadX, VxWorks, Palm OS, Symbian OS, QNX, Cisco IOS, MC/OS, VRTX, and TRON. TRON is the world's most popular OS! AlbertCahalan 23:28, 24 October 2005 (UTC)

''The principle embodied by Plan 9 for example is that everything is a file(system). The previous sentence almost completely characterizes Plan 9, where a long dissertation of "mechanisms" would only serve to DISinform and UNeducate people.''

''As for the definition of an OS, which one should that be? Would that be the one made in the early early 70s that no longer applies? Or do you want to go the radical route and provide an actually useful, practical and informative definition? On the, frankly non-existent, chance that you want to be useful and informative, an Operating System is:''

A set of principles and concepts and all of the software which obeys these principles.

This definition explains why X Window is not part of Unix but 8 1/2 is part of Plan 9.

 * Well, it includes the web browser. I've read sworn testamony that attests to this. The practical answer is that the OS is whatever you get on that first set of CDs, no more and no less. AlbertCahalan 23:28, 24 October 2005 (UTC)

 * I do not expect that we will find a perfect abstraction to describe operating systems. It would help Wikibooks if the anonymous user/users who posted this would contribute to A Neutral Look at Operating Systems by editing the pages or adding new ones. This unsigned comment was posted by Kernigh 20:27, 24 October 2005

What Distinguishes Two Operating Systems
Someone restored the obsolete TOC and justified it by writing "It contains some operating systems that are not yet moved to the new version."

This is factually wrong. We aren't interested in the various versions of BSD and they do not merit the appelation of different OSes. They're the same OS. So are all of the Linux distros. They're all the exact same OS just configured slightly differently. You might as well be talking about the differences between different patch versions to Windows 98.

The only distribution of Linux that you'd have even a half chance of arguing is a different OS is RtLinux, and you wouldn't have that chance with anyone that's studied OSes (as opposed to someone that's studied Unix - and how typically provincial of Unixers to think that they're the center of the universe!). None of the Unixes (System V, Solaris, Linux, BSD, even AIX while we're at it) are appreciably different from each other, they're all exactly the same OS.

The minimum distance between two branches of an OS tree that distinguishes different OSes is that between Unix and Plan 9. We should apply the same standards to OSes that we apply to biological species, whether they can interbreed. Since software for any Linux distribution is binary-compatible with any other Linux distribution, it is obviously the same species of OS. Since software for any Linux is source compatible with any other Unix, all Unixes are still the same OS.

You only start getting a different OS when you look at HURD, QNX, VSTa, or Plan 9, all of which are Unix derivatives. And these are different OSes because software for one requires porting to run on another.

There is vastly more difference between VisualWorks Smalltalk and Dolphin Smalltalk than there is between two clones of Unix, and all dialects of Smalltalk are still considered the same language. This is especially relevant since you can treat languages as operating systems and vice versa.

Proposal to Rename the Book
24.200.176.92 recently proposed the renaming of this book to A Political Look at Mainstream End-User Operating Systems. The proposal was made at User talk:Kernigh. I am currently opposing the rename because I think that it would limit contributions to this book. --Kernigh 03:44, 27 October 2005 (UTC)

I don't think we should be so unhesitant to supply an audience for this rude user. The suggestion was not made in a serious and constructive manner. Turning the book into a list of failed OS experiments is no more useful than turning it into yet another Linux-versus-Windows, Linux-versus-BSD, or Linux-distribution-table. AlbertCahalan 04:22, 27 October 2005 (UTC)

''I was rude to Kernigh. To you I was merely brutally honest. You have contributed nothing of any interest to this book and this book as it is currently construed, and as you wish to preserve it, has nothing of interest to contribute to the world. So it's funny how I was rude to the guy who didn't complain and not rude to the ham-fisted lout that responded with force.'' 24.200.176.92 01:51, 28 October 2005 (UTC)

This should be called A Look At Operating Systems for x86. You've left out the operating system that runs 99% of the world's financial transactions and most other commercial activity (z/OS).

 * I agree slightly. Wikibooks should already strive to be neutral. I believe the current title, "A Neutral Look at Operating Systems" is redundant. I agree with the anonymous person above except that to avoid confusion call it "An Overview of Operating Systems for PCs" or something like that. x86 architecture is not implied with all the OS's shown. However I believe this book seems to be mainly looking at personal computers. Correct me if I'm wrong- I haven't read the whole thing. --Evolutionist79 (discuss • contribs) 20:37, 26 April 2011 (UTC)
 * Other operating systems omitted include zVSE, TPF and zVM for mainframes, i(5) for the AS400 and OS/2. Perhaps their omission can be justified by the dirth of publications on the internal structure and logic of these widely used, proprietary operating systems.Ccalvin (discuss • contribs) 12:31, 6 March 2013 (UTC)

merge
I suggest merging the Operating Systems Wikibook into A Neutral Look at Operating Systems. As far as I can tell, both books have the same topic and target audience. --DavidCary (discuss • contribs) 15:19, 19 July 2015 (UTC)


text:
Talk:Islam

It would be a good idea to start some independent research on the islam. Because I want to know how fullgrown people can believe this? I want to know what is the real reason behind it, and why do so many people in poor counties go over to the islam. Why do people in industrialized countries with no future and no hope convert to islam instead of geting an education to fight their situation. Furthermore it would be very interesting to know why the followers of Mohammed dislike philosophy.

Steven —Preceding unsigned comment added by 83.128.15.170 (discuss • contribs) 08:25, 21 March 2005

 * I want to know what is the real reason behind it, and why do so many people in poor counties go over to the islam. The countries of the Gulf Cooperation Council, including Saudi Arabia where Mecca and Medina are located, are wealthier than most parts of the world, though less wealthy than the G8. Some poor countries, like Afghanistan and Mauritania, have a Muslim majority, but some, like Haiti and Democratic Republic of the Congo, have few Muslims. --Kernigh 17:05, 5 February 2006 (UTC)

Merge to Humanities bookshelf
I think that most users look for books on a bookshelf, which makes these Islam books difficult to find. I have marked the module and I suggest moving the Islam books to that bookshelf and redirecting the Islam module to the bookshelf. --Kernigh 17:05, 5 February 2006 (UTC)

title: Talk:Islam


text:
Template:Ada/95/SG1

Chapter : 95/SG1

title: Template:Ada/95/SG1


text:
Template:Ada/95/SG2

[http://www.adaic.org/docs/95style/html/sec_/-.html. ] 95/SG2

title: Template:Ada/95/SG2


text:
Template:Ada/95/SG3

[http://www.adaic.org/docs/95style/html/sec_/--.html .. ] 95/SG3

title: Template:Ada/95/SG3


text:
Template:Ada/operator

Ada Programming

Usage: *

gives:

Operator

title: Template:Ada/operator


text:
Template:Ada/attribute

Attribute

title: Template:Ada/attribute


text:
Template:Ada/pragma

Pragma

title: Template:Ada/pragma


text:
Template:Ada/package

Ada Programming/Libraries/ Package

title: Template:Ada/package


text:
Talk:Intelligence Intensification/Speed Reading

(Sub)Vocalisation
Regarding "2. Never pronounce the words. Your mouth should be absolutely still.": If I remember rightly, Tony Buzan's speed reading book isn't at all worried about subvocalisation. In fact it encourages it. I suppose the argument above applies only to actual physical vocalisation, as the voice in your head can go as fast as you like. --Odd spark (talk) 22:11, 1 January 2008 (UTC)

Hopping brain
I would dispute the statement that "the brain is faster than the eyes". It is impossible to move the brain. It really just sits there in the brain case. But the eyes rotate and succade quite fast. Regards, June.

 * I guess the idea is that the brain can handle more characters per second (a speed measure) than the eyes can supply.

 * The brain does actually move around a lot inside the head, but suggesting it can keep up with the eye is quite ridiculous. I can skim over this page quite easily with my eyes, but my brain can't put the information together fast enough for it to have any meaning.

Two words at a time
From the text: ''Reading research shows that it is possible to read as many as two words at one time. So keep practicing.'' Haha, clearly it is possible to take in more than two words in a glance. But I find this pessimistic statement incredibly amusing... it really adds to the character of the book I had in mind long time ago when I started it. I wanted the book to be simple and sound without the typical "you'll be a millionaire and have fantastic sex in 21 days" pitch. -Daniel


text:
Mythology/Norse Mythology

Norse culture and language, basics of Norse mythology
Norse mythology refers to the pre-Christian beliefs of the Scandinavian people. It is the most well known version of the older mythology common to the germanic tribes, including the closely related anglo-saxon mythology. The language spoken during the period that the norse gods were worshipped, was Old Norse. By the time this language split up into different languages (not including dialects), Christianity had taken root in much of Northern Europe.

The universe as seen by the believers of norse mythology
The universe was believed to be a collection of flat, circular discs, known as the nine worlds. The worlds were: Alfheim         World of the Light Elves Asgard          World of the Aesir Jotunheim 	 World of the Giants. Midgard 	 Home of mankind. Muspelheim 	 World of fire and the fire-giants, home of the giant Surt. Nidavellir 	 Home of the Dwarves Niflheim 	 World of the ice and that of the dead, which is also known as Hell. Svartalfheim 	 World of the Dark Elves Vanaheim 	 Home of the Vanir

All the nine worlds were connected by the World Tree, or Yggdrasill, the roots and branches connecting the different worlds.

In Niflheim, the dead resided. However, unlike the stories known today of Hell (notice Hel versus hell), Niflheim was a material place located in connection with the other worlds. Surrounding Midgard it was believed a Giant worm lived near the edge of the plate, Midgardsormrinn. In the beginning, there was nothing but an endless void, called the Ginnungagap, and Muspelheim and Niflheim, terrible worlds of pain. Out of this void came Ymir, the first living creature. He was a giant, and became the father of the race of frost giants. Ymir was the father of a six-headed son that was nourished by a cosmic cow called Audumla. Audumla fed herself by licking the salty rime-stone, until that stone was licked into a shape of man. This stone-man was named Buri and he was the first primeval god. Buri was the father of Bor. Bor married the giantess Bestla, and became father of Odin, Ve and Vili. After a time, Ymir grew so evil and large that the three gods slew him, and used him to create the universe. Midgard was created by Ymir's eyebrow as a place for the humans to dwell. The first humans were Ask (ash) and Embla (elm). Sol is the goddess of the Sun, riding the heavens. Her brother Mani, is the moon. It's easy to trace the present day Norwegian words Sol (sun) and måne (moon) to these norse gods.

War of the Aesir and Vanir
The war between the Aesir and Vanir started when the Aesir, tired of her endless talk about gold and wealth, tortured the Vanir goddess Gullveig. When the Vanir demanded equal status as the Aesir, the war broke out. [not finished]

title: Mythology/Norse Mythology


text:
Talk:Perl Programming/Getting started

Italic textlink title

Headline text
[[Media:Example.mp3]] Insert non-formatted text here --210.238.191.254 13:03, 21 Mar 2005 (UTC)

= Major Changes =

Removed convention notes
These notes are stupid, and they break the spirit of wikipedia. It is an abuse to adopt an esoteric formatting convention that will exclude users, and a total maintenance nightmare to keep it in sync. Consider revisiting when wiki books further matures. EvanCarroll 08:00, 23 September 2007 (UTC)

Perl on MS Windows
Should there be mention of Strawberry Perl?

Good question. I was going to ask the same thing. CSJewell (talk) 22:01, 5 June 2010 (UTC)

title: Talk:Perl Programming/Getting started


text:
Talk:Chinese (Mandarin)/Lesson 5

Untitled
This is just a list of "For X ... we use Y" which isn't very helpful for the learner. I think it needs to be compiled into a table. I'm learning Chinese and its quite unhelpful to have to remember measure words seperate from the nouns to which they relate. Ideally after measure words are introduced all further nouns introduced as new vocabulary should have their measure words with them.

--Glisher 13:06, 21 Mar 2005 (UTC)

I'd like to second Glisher's remark and take it one step further. It would be very helpful to have access to an online (or downloadable) chinese dictionary that includes the measure words with the noun. The two resources I am using: zhongwen.com and NJStar bilingual dictionary fail in this regard, which is surprising to me (i am a beginner). Can some kind person direct me to a suitable resource? Many thanks. --Philopedia 19:15, 10 July 2006 (UTC)

negation with quantity
We've got another bad negation, just like in lesson two: 这本书里没有一个汉字 I think it should be: 這本書裏沒有漢字 or 這本書裏一個漢字也沒有. --Yakowenko (talk) 07:30, 17 March 2009 (UTC)
 * sry to interrupt, but "这本书里没有一个汉字" is grammatically right, tho might be a bit confusing for new learners. KonW (talk) 14:17, 30 April 2009 (UTC)

title: Talk:Chinese (Mandarin)/Lesson 5


text:
Template:Ada/95/AI

AI95-00000-00

Usage: *

gives:

Optional arguments: *

gives:

AI:1995

title: Template:Ada/95/AI


text:
User:Prashanthns

http://en.wikipedia.org/wiki/User:Prashanthns

title: User:Prashanthns


text:
Finnish/Grammar-Vowel harmony

^^Contents^^ <>

Vowel Harmony
Finnish, like many Uralic languages, has vowel harmony and it affects what vowels go with which words. It also affects the postpositions and endings of words. In Finnish, there are eight vowels, a, e, i, o, u, y, ä and ö. They are grouped into three groups; front, neutral and back vowels. See the diagram:

The vowels in blue are front vowels (or "hard"), the vowels in green are neutral and the vowels in yellow are back vowels (or "soft").

In Finnish, single words contain only vowels of the same type as the initial, stressed syllable. So, for example, the word, aaltoileva contains only neutral and back vowels, while äidillä contains only front and neutral vowels. With respect to vowel harmony, compound words are separate words, e.g. työmaa, with -ta suffixed työ|maa|ta.

When a word contains only neutral vowels, its suffixes use front vowels. For example, when the postposition -lla or -llä is added to kieli, it becomes kielellä, not kielella.

As a consequence, Finnish speakers often have trouble pronouncing foreign words which do not obey vowel harmony. For example, some Finns may pronounce olympia as olumpia because of the difficulty in producing the sounds of o and y in a row.

Vowel harmony applies to foreign words, too. For example, chat is heard as tsät and consequently the frequentatitive verb "to chat" is tsättäillä (also spelled chattäillä, chattailla, chättäillä, etc.). (Note: chattäillä would lack harmony if it was pronounced as written. ch turns into ts because ch would be prononunced as sh(as in shut) or kh(as in khaki) by people unfamiliar with the word.)

e → i
You may have noticed that nimi (name) corresponds to nimesi (your name), and Suomi (Finland) corresponds to Suomesta (from Finland). This is because there is an e → i mutation. These roots end in an e which changes to i at the end of a word. When a root ending in e has a suffix, the e does not change.

Other roots have i both at the end and before a suffix, as in taksi (taxi) and taksissa (in a taxi). The rule is completely regular---a final e becomes i. However, since the mutation `neutralizes' the e/i distinction word finally, you need to remember whether the suffixed form has e or i. Most of the roots that end in e are "old" words like nimi and suomi. Recent borrowings like taksi don't show the e/i alternation because these roots just end in i.

The k, p and t mutation
Like the i to e mutation, when you put a suffix after a word, some consonants change when you agglutinate. For example Helsinki changes to Helsingissä after you put a suffix, here -ssä, after it. This is called consonant gradation and it mainly affects the consonants k, p and  t. So words like pankki change to pankin. Here is a short, not a complete list:

End Note
Now there is a lot to go through, but take your time and hopefully this will help you to no end. But beware that there is more to go through, as we haven't covered the suffixes yet!

title: Finnish/Grammar-Vowel harmony


text:
American Sign Language

Welcome to the American Sign Language wikibook. American Sign Language, or ASL is a visual language expressed through hand gestures and facial expressions. It is a language used by many Deaf, hard-of-hearing, and hearing people in North America. This wikibook aims to teach ASL vocabulary, grammar and exercises to beginners. Feel free to contribute!

Lessons

 * 1) /Introduction/: /History of American Sign Language/ · /Deaf Culture/ · Alphabet and Numbers - /Location/ - /Linguistics/
 * 2) Level 1: /Fingerspelling 1/ · /Vocabulary 1/ · /Basic Grammar 1/ · /Simple Sentences 1/ - /Grammar 1/
 * 3) /Lesson 2/: /Fingerspelling 2/ · /Vocabulary 2/ · /Basic Grammar 2/ · /Facial Expressions 1/ · /Dialogue 1/
 * 4) /Lesson 3/:

Appendices

 * 1) /Appendix A: Handshapes
 * 2) /Idioms
 * 3) /Profanity
 * 4) /Further Resources

title: American Sign Language


text:
Macroeconomics/Fiscal Policy

Fiscal Policy concerns the use of changes in the amount of government spending, G and taxation T to influence the national economy. This policy can affect both Aggregate Demand (AD) and Aggregate Supply (AS), though it is worth noting that the affect on AD is much more direct and immediate, whereas AS is affected through indirect means over a greater period of time. It is also just about impossible to isolate the two effects - any change in fiscal policy will ultimately affect both AD and AS.

Aggregate Demand
As we already know, AD = C + I + G + (X - M) where 'G' stands for government spending. Taxation is accounted for in the affect it has on the other components of aggregate demand (for example, consumption will fall if more is spent in paying taxes!).

Increases in government spending will increase aggregate demand, which will have affects on the economy overall. It leads to an increase in output and average prices, other things being equal. However, the degree to which output/prices rise depends on the elasticity of AS. This can be easily shown on an AD-AS diagram: If Aggregate Supply is elastic, a large increase in output may result with little risk of inflationary pressures. However, if AS is inelastic increased government spending may not be the best way of boosting the economy, as it is at risk of 'overheating' - that is, at risk of causing inflation rather than growth in output.

Similarly,,, a fall in government spending will 'cool' the economy, and cause a contraction in AD: diagram>

Aggregate Supply
Specific changes in fiscal policy can be used to affect aggregate supply:

Capital Spending
Government spending on infrastructure, such as new transport networks, increases the potential output of an economy. Also, lower corporation taxes mean that businesses can invest greater sums at the same time, contributing both to AD and AS.

Capital spending could also include investment in 'human capital', such as retraining, higher education and vocational training as ways to increase the supply of labour, reduce unemployment and provide a more productive workforce. Human capital is becoming ever more important as many developed countries now aim for a knowledge-based economy, in which labour is more productive.

Workforce Incentives
Changes in the benefits system, such as a reduction in income tax, could create greater incentive for individuals to return to work. This increases labour supply, and hence overall supply as labour is a factor of production. It could be argued that welfare and benefit reform is more important ie. fewer benefits for the unemployed to incentivise them to work.

R&D and Innovation
Increased G could encourage developments in technology, which also increase the potential output of an economy, though without an accompyaning increase in demand, this will only increase 'slack' in the economy, reducing inflationary pressure, rather than an actual increase in total output.

These AS effects are dependent upon carefully targetted government spending, and it is important to note that government spending alone will not necessarily affect AS.

Fiscal Policy Terms

 * Expansionary Fiscal Policy = G > T. That means that government spending is greater than the rate of taxation, so it is a boost to the economy. The disadvantage to this is that a budget deficit will ultimately build up
 * Contractionary Fiscal Policy = G < T. This has a contractionary, deflationary effect on the economy, but it will improve the government finances over time

title: Macroeconomics/Fiscal Policy


text:
How To Assemble A Desktop PC/Noted contributors

 * Noogz - Editor, Hardcore contributor, Team member
 * Reub2000 - Original Author, Hardcore contributor, Team member
 * Hyperlink - Organizer, Team member, Structural Contributor
 * Andreas - Consultant, Print version
 * Yayyak - Contributors
 * KunalThaggarse - Contributor


text:
Talk:Ada Programming/Exceptions

I suspect that the anonymous user is pasting from some source, not only because the page was almost entirely written in the second revision, but because its text uses special characters like the fi ligature. We should investigate which is the source and whether it represents a copyright violation. ManuelGR 00:06, 22 Mar 2005 (UTC)

 * I remebert that one. The text was indeed pasted but from the original author - which can be contacted at irc://#ada if needed. --Krischik 06:59, 6 Apr 2005 (UTC)

 * Thanks, Krischik. One mistery less. And who is he? Just for curiosity given that I often enter in irc://freenode.org/ada ManuelGR 19:16, 6 Apr 2005 (UTC)

title: Talk:Ada Programming/Exceptions


text:
Template:Movie Making Manual/devHeader

This Module is part of the Movie Making Manual

title: Template:Movie Making Manual/devHeader


text:
Template:Movie Making Manual/preHeader

This Module is part of the Movie Making Manual

title: Template:Movie Making Manual/preHeader


text: Template:Movie Making Manual/post header


text:
Template:Movie Making Manual/s&eHeader

This Module is part of the Movie Making Manual

title: Template:Movie Making Manual/s&eHeader


text:
Template:Movie Making Manual/prodHeader

This Module is part of the Movie Making Manual

title: Template:Movie Making Manual/prodHeader


text:
Dichotomous Key/Octopoda

1

 * Cornea
 * Present - 2
 * Not present - 3

2: Incirrata

 * Detachable hectocotylus
 * Present - 5
 * Not present - 6

3: Cirrata

 * Secondary web
 * Present - 4
 * Not present - ../Opisthoteuthidae/

4

 * Shell shape
 * Saddle-shaped - ../Cirroteuthidae/
 * U-shaped - ../Stauroteuthidae/

5: Argonautoida

 * Tissue consistency
 * Gelatinous - 10
 * Muscular - 9

6

 * Eye shape
 * Tubular - ../Amphitretidae/
 * Other - 7

7

 * Eye shape
 * Laterally compressed - ../Bolitaenidae/
 * Other - 8

8

 * Eye shape
 * Rectangular - Vitreledonella richardi
 * Other - ../Octopodidae/

9

 * Web
 * Absent or greatly reduced except in four dorsal arms - ../Tremoctopodidae/
 * Consistent - 11

10

 * Web
 * Absent or greatly reduced except in four dorsal arms - Tremoctopus gelatus
 * Consistent - Haliphron atlanticus

11

 * Funnel locking-apparatus
 * Contains circular pit - ../Argonautidae/
 * Does not contain circular pit - Ocythoe tuberculata

title: Dichotomous Key/Octopoda


text:
Dichotomous Key/Bolitaenidae

1

 * Ligula
 * Present - Bolitaena pygmaea
 * Not present - Japetella diaphana

title: Dichotomous Key/Bolitaenidae


text:
Dichotomous Key/Tremoctopodidae

1

 * Tissue form
 * Gelatinous - Tremoctopus gelatus
 * Muscular - 2

2

 * Number of distal hectocotylus suckers
 * 27-28 - Tremoctopus robsoni
 * 15-22 - 3

3

 * Habitat
 * Atlantic Ocean - Tremoctopus violaceus
 * Pacific Ocean - Tremoctopus gracilis

title: Dichotomous Key/Tremoctopodidae


text:
Dichotomous Key/Oegopsida

1

 * Buccal connective to arms IV
 * Dorsal - 2
 * Ventral - 3

2

 * Funnel locking-cartilage
 * Straight - 4
 * Inverted T - ../Ommastrephidae/

3

 * Carpal locking-apparatus
 * Present - 12
 * Not present - 13

4

 * Gladius conus
 * Present - 5
 * Not present - 6

5

 * Anterior fin attachment
 * Mantle - 8
 * Gladius - 7

6: Histioteuthids

 * Comparative eye size
 * Equal - Psychroteuthis glacialis
 * Unequal, left eye larger - ../Histioteuthidae/

7: Enoploteuthids

 * Hooks on tentacular clubs
 * Present - 9
 * Not present - 10

8

 * Free posterior fin lobes
 * Present - ../Neoteuthidae/
 * Not present - ../Architeuthidae/

9

 * Photophores on eyeballs
 * Present - 11
 * Not present - Ancistrocheirus lesueurii

10

 * Hooks on arm pairs I - III
 * Present - ../Pyroteuthidae/
 * Not present - ../Lycoteuthidae/

11

 * Photophores on mantle
 * Present - ../Enoploteuthidae/
 * Not present - ../Pyroteuthidae/

12
Brachioteuthidae

Cranchiidae

Gonatidae

Cycloteuthidae

Onychoteuthidae

Thysanoteuthidae

13

 * Secondary tentacular club
 * Present - 14
 * Not present - 15

14: Chiroteuthids

 * Number of series of suckers
 * Six (on at least one arm) - 20
 * Other than six (on any arm) - 18

15

 * Proximal region of manus of club greatly expanded
 * Present - ../Brachioteuthidae/
 * Not present - 16

16: Lepidoteuthids

 * Tentacles
 * Absent or reduced in adults - 17
 * Present - ../Pholidoteuthidae/

17

 * Number of hooks
 * Two or fewer - Lepidoteuthis grimaldii
 * Many, in two series - ../Octopoteuthidae/

18

 * Doratopsis paralarva
 * Present - ../Chiroteuthidae/
 * Not present - 19

19

 * Shape of distal ends of tentacles
 * Vermiform - Magnapinna pacifica
 * Other - 21

20

 * Comparative arm length
 * All arms comparable - Batoteuthis skolops
 * Arm pairs I - III much longer than others - Joubiniteuthis portieri

21

 * Ink sac
 * Present - ../Mastigoteuthidae/
 * Not present - ../Promachoteuthidae/

title: Dichotomous Key/Oegopsida


text:
A Neutral Look at Operating Systems/Berkeley Software Distribution

The BSDs originate from the custom Unix distribution created at the University of California at Berkeley. The distro was called the Berkeley Software Distribution. Because BSD was a modified Unix, it was only available to those with Unix source code licenses from AT&T. Later versions of BSD became free software without any AT&T code.

Today, there are four main free operating system projects derived from BSD. This page also mentions three other distributions based on those projects. They all have Wikipedia articles: DragonFly BSD, FreeBSD, PC-BSD, DesktopBSD, NetBSD, OpenBSD, MirOS BSD.

These are also called *BSD projects because they have "BSD" at the end of their names to show their ancestry. The BSD licensing allows for almost any redistribution and modification. Thus, the BSD projects frequently take code from each other; a new feature from one BSD project might appear later in the others.

BSDs are distributed as complete operating systems with kernel and userland. The BSD projects provide a "ports tree" with Makefiles that automate downloading, patching, building, and installing software and handling dependencies; FreeBSD ports and NetBSD pkgsrc are examples. They also provide binary packages of popular ports.

DragonFly BSD
DragonFly BSD is the newest of the four projects. It was started in 2003 as a fork of FreeBSD 4.X by developers that wanted changes in the system design. They are still working on their goals. The following is from their goals page:

 * DragonFly is going to be a multi-year project. It will take a lot of groundwork to even approach the goals we outline here. ... First and foremost among all of our goals is a desire to be able to implement them in small bite-sized chunks, while at the same time maintaining good stability for the system as a whole. ... It's a laudable goal that will sit foremost in our minds, even though we know it is probably not 100% achievable.

FreeBSD
FreeBSD is a high-performance system and regarded as one of the most mature and robust network operating systems. (Some of its clients, such as Yahoo! seem to agree.) It also has many of the portability advantages of NetBSD and security advantages of OpenBSD.

Here are examples of features that reached FreeBSD before the other BSD projects.
 * FreeBSD was the first system with a ports collection based on Makefiles. This assisted in porting Unix software to FreeBSD and installing it. The ports trees of the other BSD projects are derived from this one.
 * FreeBSD was the first to have the soft updates feature to improve disk performance and recovery of filesystems from system crashes.

PC-BSD
PC-BSD is a project to build a system based on FreeBSD and KDE. It is very easy to install. After the other BSDs are installed, they give the user only a root shell prompt, and no graphical user interface is configured. After installing PC-BSD, a KDE desktop environment is already configured. PC-BSD also has a graphical installer which helps the user create a first non-root user account and includes customizing BSD disklabel.

PC-BSD users can download *.pbi files, double-click their icons, and install them as binary packages. This is a rare feature among BSD and even Linux distributions, but common on Windows and Mac OS X. Optionally, KDE menu and desktop items are created. Not only are the *.pbi packages available, but the FreeBSD ports collection is also available.

Both OS installation and *.pbi files are demonstrated in the PC-BSD tour.

DesktopBSD
Another project was started with a goal to provide user-friendly BSD system. DesktopBSD was started independently from PC-BSD and these two projects still remain separate. Similarly, DesktopBSD provides easy-to-use graphical installer and installs fully configured desktop system based on KDE.

DesktopBSD developed its own graphical tools integrated with KDE: ports manager, disk mounter and network configuring tool.

NetBSD
The focus of NetBSD is to provide a stable, multiplatform, research and server operating system. NetBSD is widely regarded as being one of the most portable operating systems.

NetBSD runs on a very wide variety of architectures. There are at least 54 architectures including some very exotic ones such as the Sega Dreamcast. These architectures involve at least 17 processor types. These platforms are supported from a single CVS tree, avoiding the need for third party patches to use various hardware. The highly cross-compilable system (with full toolchain), and excellent documentation make it very useful for developers.

The NetBSD packages collection, pkgsrc, is also portable. pkgsrc supports the other BSDs, Linux, Darwin, and Solaris. A bootstrap script is provided as part of pkgsrc to adapt it to the host OS and build the necessary support tools.

OpenBSD
OpenBSD was forked off NetBSD when Theo de Raadt had a disagreement with the NetBSD Core Team. Theo founded OpenBSD in the early 1990s. Due to living in Canada Theo was able to legally incorporate strong cryptography into OpenBSD without encumberance by US laws.

OpenBSD is widely thought of as "the most secure OS". Its motto is "Secure by Default". OpenBSD developers review all of the code by hand in order to search for security holes. The default installation of OpenBSD leaves a lot of features turned off, contributing to its motto. OpenBSD runs well on many different platforms due to its NetBSD lineage. OpenBSD is also the origin of OpenSSH, which is the most popular implementation of ssh, which replaces insecure network logins with the secure ssh protocol.

The OpenBSD project has been replacing many of the GNU programs in their system with programs having BSD-licenses, non-copyleft versions, but they still use GNU gcc and binutils to build. They also use CVS, a source-revision control system under the GNU GPL license, but plan to replace it with their own OpenCVS when ready. OpenBSD also includes some large packages like perl, Apache 1.x, sendmail, and bind in the base system instead of putting those things into their ports collection. Thus the base OpenBSD system (with no added packages) has more components than the other BSDs.

MirOS BSD
MirOS BSD was a set of patches, and now is a fork, of OpenBSD. The project is based in Europe. They have resurrected some features that OpenBSD dropped, and moved some packages from the base system to MirPorts, the ports collection. There is a plan to port MirOS to Linux kernel.

Quasijarus
Quasijarus is different from the other BSDs. It is a fork of 4.3BSD-Tahoe (without the later 4.4BSD changes that the other *BSD projects have). Like 4.3BSD, it only runs on VAX. Essentially, it is a slightly modified 4.3BSD-Tahoe system.