% DO NOT EDIT leaflet_e.tex Built from leaflet_e.e_tex
% File Name or Produced From: leaflet.l_tex
% This line appears in output file leaflet_english.tex
% DO NOT EDIT OR BASE DIFFS ON leaflet_english.tex & leaflet_german.tex !
%	hey are transient files output files generated by the Makefile. 
% ONLY EDIT leaflet.teg ! (teg is an ancronym for Tex English & German)
%
%   Informationsbroschüre über BSD, erstellt anläßlich der
%   Messe »Systems 2001« in München.
%
%   Leaflet on the BSDs, in English & German (first written for a trade show).
%
%   Original by Oliver Fromme  <olli_ERASE@fromme.com>
%
%   Update 20.12.2002 - Rainer Duffner
%   Merge der Leaflets von Oliver Fromme und Daniel Lang
%   TeX scrapped from Oliver ....
%
%   Update Jan 2003 Julian H. Stacey
%   	Introduced Combined English + German format,
%   	translated Rainer's version to English
%	Tweaked english half a little, with typos+style feedback from
%	Kevin Kinsey from advocacy_ERASE@freebsd.org
%
%   Update by Rainer 14th March 2004 to get German on one sheet of paper
%
%   Update by Julian 15th March 2004 to review English.
%	plus added more info and URLs at end to fill white space
%	as English always takes less space than German.
%
%   Fri Mar 19 01:00:12 CET 2004 jhs stopped editing, over to Rainer.
%
%   NetBSD updates handwritten from Hubert, + Other updates from others
%   @ Stammtisch 2004.03.17, merged by Julian, with some own small changes,
%   including removal of name Unix from the English version.
%   The name is getting ever more problematic, with SCO sueing anyone for
%   anything, & real Unix people know BSD is Unix anyway, & businesmen
%   don't care or need to know, & youngsters & joe public dumb MS user
%   have heard of Linux, not Unix !
%
%   THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS"
%   AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
%   TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
%   PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR
%   OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
%   SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
%   LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
%   USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
%   AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
%   LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
%   ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
%   POSSIBILITY OF SUCH DAMAGE.
%
% PENDING: 
% Issue pending work by editors are marked eg PENDING:JULIAN PENDING:RAINER
%
% PENDING:Any_Tex_Person Add vertical fold peck marks for columns
%
% PENDING:Any_Tex_Person Decorate: Add Logos, such as X-Windows,
%	Apache, Penguin (as source compatible - &amp; we have an emulator)
%	      Tex Person</i></li>
%
% PENDING:Any_Tex_Person       >USA Letter: Native format is A4.
%	Diffs are welcome to switch to USA Letter. Any such diffs will be
%	stored in <a href="Makefile">Makefile</a> to support switchable A4
%	&amp; USA format.</li>
%
% WARNING:
% Avoid use of !}fmt within vi on the German sections, as it zaps umlauts,
% (It's nice on the English sections though, to make source more readable 
% to human editors).
%
% UMLAUTS
% When julian edits this (as may also other people in USA sometime)
% we use straight ascii, vi within xterm, & the umlauts don't show up properly,
% so A) one needs to be careful not to damage them (as they use bit 8),
% B) Here's a table below, so umlauts can be repaired or eg capitalised 
% on occasion etc.
%	Symbolic 1byte	Spelt Out as a string
%	a:	ä	\xE4
%	o:	ö	\xF6
%	u:	ü	\xFC
%	A:
%	O:
%	U:
%	ss	ß	\xDF

\documentclass[10pt]{article}

% ----
\usepackage{pslatex}
% PENDING:JULIAN latex2html: Warning: No implementation found for package: pslatex.
% ----
% Probably default, so dont need to specify it.
% \usepackage{english}
% ----
\usepackage[T1]{fontenc}
% PENDING:JULIAN latex2html: Warning: No implementation found for option: `T1' for `fontenc' package
% PENDING:JULIAN latex2html: Warning: No implementation found for package: fontenc.
% ----
\usepackage[latin1]{inputenc}
% ----
\usepackage{epsf,picinpar}
% PENDING:JULIAN latex2html: Warning: No implementation found for package: epsf
% PENDING:JULIAN latex2html: Warning: No implementation found for package: picinpar
% ----

\paperheight=21cm	%   ISO A4 short side
\paperwidth=9.9cm	%   ISO A4 long side / 3
\special{papersize=99mm,210mm}

% PENDING:JULIAN 	dvips -t landscape -o tmp.leaflet_english.ps leaflet_english.dvi
%		dvips: both landscape and papersize specified:  ignoring landscape   


%%% %   Uncomment this to print "Entwurf" ("Draft") on each
%%% %   page's background in large, light grey letters.
%%%
%%% %   Some PostScript magic ...
%%% \special{!userdict begin /bop-hook{gsave 90 20 translate
%%% 70 rotate /Times-Roman findfont 116 scalefont setfont
%%% 0 0 moveto 0.85 setgray (ENTWURF) show grestore}def end}

%   Setup the text area on each page.
%   Borders:  left and right 0.5cm each,
%             to and bottom 1.0cm each.
%   (Note:  DVI drivers imply an offset of 1in top/left.)
\textheight=19cm	%   21cm - 2 * 1cm
\textwidth=8.9cm	%   9.9cm - 2 * 0.5cm
\topmargin=-2.81cm
\oddsidemargin=-2.04cm

\sloppy
\nonfrenchspacing
\parindent=0pt
\parskip=1ex
\pagestyle{empty}

\newcommand{\UNIX}{UNIX\textregistered}
\newcommand{\TOG}{The Open Group\texttrademark}
\newcommand{\Abschnitt}[1]{
	\begin{center}
		\large{\sffamily\bfseries #1}
	\end{center}
 }

\newcommand{\UAbschnitt}[1] {
	\begin{center}
		\small{\center{\sffamily\bfseries #1}}
	\end{center}
 }

%==================  end of preamble  ==================

\begin{document}

\begin{center}
%	BIM -- Berkeley in Munich \ $<$bim_ERASE@mailman.berklix.org$>$\\
	\large\textsc{BIM -- Berkeley in Munich} \\
	http://www.berklix.org/bim/ \\
	\large\textsc{presents:}
\end{center}

\begin{center}
	\Huge\textbf{BSD}\\
	\large\textsc{Berkeley Software Distribution}
\end{center}

\vskip 0pt plus 1fill

\hspace*{0.1\textwidth}{\epsfxsize=0.8\textwidth \leavevmode \epsffile{bug.ps}}

\vskip 0pt plus 1fill

This leaflet aims to give an overview of the three open
source representatives of the family of BSD 
% \UNIX 
computer operating systems:

\begin{center}
\large\bfseries
\begin{tabular}{l@{\quad}l}
	FreeBSD	& \texttt{http://www.freebsd.org/} \\
	NetBSD	& \texttt{http://www.netbsd.org/} \\
	OpenBSD	& \texttt{http://www.openbsd.org/}
% Hubert said NetBSD had discussed it, & wanted to be always quoted 
% as http://www.NetBSD.org 
% however we want this leaflet to have some uniformity, & most people I've
% spoken to in BIM, think this is silly, & named doesn't distinguish anyway.
% so the NetBSD request is out-voted, & we'll leave all domains in URL's as
% lower case.
\end{tabular}
\end{center}

\vskip 0pt plus 1fill

\begin{center}
\small{
% PENDING:RAINER Convert u: in next line to capitals.
Deutsch übersetzung auch erhaltlich:
\vskip 0pt 
http://www.berklix.org/bim/leaflet/
 }
\vskip 0pt plus 1fill
\end{center}

 {\footnotesize
\hbox to \hsize{\textcopyright{} BIM, http://www.berklix.org/bim/
%	\hss Stand 10/2001\@.  Alle Angaben ohne Gewähr.}
	\hss March 2004\@.  
	Subject to change.
%	Errors and omissions excepted.
%	No responsibility accepted.
%	Use at own risk.
%	No guarantee of correctness.
%	PENDING:JULIAN above is not colloquially correct
 }
\hbox to \hsize{Typeset:  \LaTeXe{} on FreeBSD 
4.9
	\hss Printed:  dvips\,/\,ps2pdf}
\hbox to \hsize{\hss
	Prepared/ Printed in Germany\quad-\quad Imprim\'e en Allemagne
	\hss}
\par}

\newpage

\Abschnitt{
% Introduction
What Is BSD ?
 }

% What Is BSD ?
This leaflet aims to give the most important answers,
% on that theme
plus starting points to get you asking more questions that go deeper
than this leaflet covers.

\Abschnitt{
Many BSDs - One Philosophy
 }

%	Traditionaly one divides UNIX operating systems into two
%	groups: System V ("`SysV"' for short) and BSD\@.  The latter 
BSD originated
at the University of Berkeley, California.  Today's BSD Systems are
direct descendants from "`4.4BSD Lite2"', the last official BSD
version from Berkeley.

The origins of BSD go back to the 1970s, and the history is too
complex to roll out here, but one can say:

\begin{itemize}
\item
There's over 30 years development work in BSD systems, in that the
software has been continually improved to modern requirements, but
without ever throwing out the entire thing and starting completely
anew.  
% As a result today BSD derivatives are mature stable Unixes without teething troubles.
As a result BSD derivatives are mature and stable without teething troubles.

\item
Over time, multiple loosely coupled branches of BSD have evolved,
each following their own objectives, but remaining very similar
and through cross porting of interfaces, drivers and applications
remaining interchangeable.

\item
Today, derivatives include:
FreeBSD, NetBSD, OpenBSD,
and
BSDi;
Other BSD derivatives also exist, but aren't covered here for lack of space:
Darwin (from Apple), DragonflyBSD; plus
commercial BSD derivatives: BSDi from Wind River, and Mac OS-X from Apple.
% I think Darwin is MacOS X, minus the proprietary parts (Cocoa etc.), 
% but open-source.

\item
None of the BSDs is a "`Linux Distribution"' - Linux and the BSDs
are similar insofar as they use much of the same software, eg
Gcc etc.) but kernel, licence, and development models are markedly
different.
\end{itemize}

\Abschnitt{
Why Use BSD ?
% Similarities
 }
All BSDs have the following attributes and conditions in common.

\UAbschnitt{
BSD Licence
 }
The majority of the source code of the BSD operating systems is available
under the standard BSD licence.  In contrast to the GPL licence
used by the Linux Kernel, BSD licences 
% (there are several variants)
allow distribution of binaries without accompanying sources, which
is important for commercial products, which are based on BSD code
but for which companies want to release either no, or only partial
sources.

\UAbschnitt{
From One Mould
 }
Each BSD encompasses not just the kernel, but also a number of
system libraries (libc, libpam...), user programs (ls, more, find,
sort, lpr...) and system administrator commands (ifconfig, chown,
cron, dump, restore...) as well as build tools (gcc, make, ld) as
the "`operating system"', that are regarded as a unified
whole, and maintained as such. 
% Old
%	Upgrades apply to the whole operating
%	system and not just to the kernel
%	, (as with Linux).
%	Hubert says - Dont mention Linux :-)
% New idea from Hubert, reformulated by Julian:
Upgrades to the kernel and tools interfacing to it at are synchronised
and released together as a cohesive whole.
% 	unlike Linux !	(but don't print say that :-)

The entire operating system including the kernel can be rebuilt from the
sources with just a few commands. 
% Hubert suggest omit discussion of Linux, Julian agrees.
%	(Gentoo Linux now
%	offers similar capability, though without the other BSD advantages.)
%	that `now' is now old !
A strict separation between operating system and supplementary
applications (eg Apache,
Netscape, OpenOffice etc) prevails, implemented
in seperate source hierarchies. In consequence application programs
can be updated separately, which increases the longevity of
installations.
% (OpenBSD is warted & bundles Apache in src/ but Free & Net do Not.)

\UAbschnitt{
Professional Development
 }
All BSDs maintain their complete operating system source code in a
CVS repository. Thus all changes can be reconstructed, reviewed and
if necessary also reversed.
% jhs needs review of next bit from Rainer
A release engineering team controls the entire integrated product.

\UAbschnitt{
Tight Organisation
 }
The BSD projects are not undisciplined heaps of code, in which many
dabble, but form professional organisations similar to commercial
software projects. Each has a "`Steering Committee" ', called
\textit{Core }, which overviews programming sub projects etc.
Around the core teams there are numerous sub projects of developers
- called \textit{Commiters } - responsible for addition and
maintenance of documentation, kernel, driver, networking, applications and
3rd party package sources etc.

\UAbschnitt{
Software Galore !
 }
All BSDs can compile and run 
% over 99\% of source code 
software
available from eg http://freshmeat.net, and there are usually also pre-compiled
binary packages (Gimp, KDE, teTeX etc).

ABIs (Application Binary Interfaces) allow Linux programs to run
on the BSDs, for cases where the only binary package available is
for Linux. Thus further programs can be run on BSD even if the
latest version is only available for Linux, (eg 
%
% Ex Julian's English List:
% Netscape7, StarOffice 6,0, Quake3
% Ex Rainer's German List:
% Acrobat-Reader, Netscape7, StarOffice 6.0, Quake3 
% Merged list follows:
Acrobat-Reader,
Netscape 7,
Quake 3,
StarOffice 6.0
etc.).
%------------------------------------------------------------------------------
There's no noticeable speed impact.  The quality and functionality
of the Linux ABIs is however not equally well developed on all BSDs -
FreeBSD has the most functionality.
% Hubert didn't like the above statement, I Julian didn't write it,
% well, not the original German equivalent anyaway, but
% I'm not inclined to delete it until I'm better informed, 
% maybe FreeBSD still does have more Linux ABI functionality than netBSD ?
%------------------------------------------------------------------------------

\UAbschnitt{
Stable File System
 }
%------------------------------------------------------------------------------
The UFS file system has been highly valued for years and offers
very high performance. The \textit{Softupdates } option enhances performance,
and secures data integrity in the unlikely event of a crash.
%------------------------------------------------------------------------------
The FreeBSD 5.x series also provides faster booting: File systems are safely 
mounted even before asynchronous checking later !
(Attractive for corporate systems with large disc arrays).
%------------------------------------------------------------------------------
Raid is supported, both hardware and software.
% NetBSD web says @ 2004.03: software RAID 0, 1, 4, 5, and 6
% But that may change, & list of hardware will change, & BSDs will vary,
% so leave it as a bald terse statement.
%------------------------------------------------------------------------------


\UAbschnitt{
Ports/ Packages System
% Used to be called here "Ports System" until:
% Hubert pointed out:
%	NetBSD has packages not ports, the NetBSD package source structure 
%	is more advanced, supporting numerous other OSs such as Solaris.
% Julian pointed out :
%	- some people unsophisticates who only know about binaries, do know
%	  what a package is (from Linux), but don't know what a port is.
%	- technical sophisticates who know what porting means, but don't
%	  know Free & Open BSD can get the naming confused with
%	  `porting' to new CPU types.
% However, FreeBSD also has over twice as many ports as NetBSD, & lots more
% use Free than Net, so hardd to know whether to use label ports or packages.
 }
Much free software is only available in source format, or has
licencing restrictions on distribution in binary \textit{Package }
format, (the BSD equivalent of Linux RPMs).  The \textit{Ports
Framework} covers such contingencies.  It consists of a hierarchy
of Makefiles and where necessary patches, which unpack generic source
packages, compile and install them. The Ports System can 
fetch and apply sources and binaries it needs from the Internet, or from
CDROM, including building and installing any dependencies.

Individual BSDs In Detail:

\Abschnitt{FreeBSD - http://www.freebsd.org}
On normal PCs (Intel i386 derivative Hardware) FreeBSD is the
most frequently encountered representative of the BSD family.  This
is probably because it offers the broadest hardware support for
this platform, and is best optimised for it. Also it tends more
than the other two to "`functional comfortable-ness"' as experienced
on other desk top systems.  Thus it is more attractive for newcomers,
also offering the biggest collection of ported software, with over
10000
% @ 2004.03
packages.
FreeBSD no longer regards itself just as a pure server system for
skilled administrators, but aims itself also at end
users, particularly newcomers from Windows and Linux.
% --------
FreeBSD 5.0 (released Jan 2003) now supports
a variety of computer architectures: 
% --------
%	Julian's ENGLISH
%	alpha (DEC's Alpha/AXP), i386 (Intel and AMD, pentiums etc), ia64 (Intel's Itanium), pc98 (Japanese PCs), sparc64 (Sun's UltraSparc.  
%	Rainer's GERMAN
%	Alpha, AMD64/Opteron, Intel Itanium, UltraSPARC-III 
% Now Merged:
AMD 64/Opteron,
DEC Alpha/AXP),
Intel Itanium,
Intel Pentiums etc,
Pc98 (Japan),
Sun UltraSparc-III,
% --------
% --------
Power PC and StrongARM ports are in progress, but not available yet.
% --------
% Hubert advises @ 2004.03 Re SMP bit below I subsequently commented out.
% ( 
%       Indeed, that's not correct any more. Without knowing the
%	exact context of that line, I can tell you that SMP is supported
%	on i386, vax, alpha, mac, sparc and soon sparc64.
% However someone else @ 2004.03 BIM Stammtisch said SMP still
% wan't in the default main stream NetBSD
% It is in FreeBSD-5, It needs a kernel compilation in FreeBSD-4
% PENDING:RAINER Your decision please, what do we say.
FreeBSD alone of the three offers matured SMP multi processor support.
% )

\Abschnitt{NetBSD - http://www.netbsd.org}
NetBSD is slightly older than FreeBSD. Its most outstanding characteristic
is the large and growing number of hardware platforms it supports - far
more architectures than any other operating system. The list
would exceed space here, and would
quickly be incomplete and obsolete so refer to the NetBSD web page.
In many cases the decision to go NetBSD is easy, as it's the only
one available which runs on the hardware. If one has such exotic
hardware, that none of the three BSD systems run on it so far, the
chance is greatest with NetBSD that a port can be achieved with
acceptable effort.
Although not much older than FreeBSD, NetBSD happily portrays itself
as the "`big brother" ' of open source BSDs. It tends more than the
other two to maintain traditional BSD characteristics.  This
conservative behavior also has quite a positive, compensatory effect
on the other BSD systems.
Due to modular hardware and driver infrastructure NetBSD is attractive
for embedded applications, on Strongarm, 
% Shark,
PPC etc)

\Abschnitt{OpenBSD - http://www.openbsd.org}
OpenBSD split from NetBSD in 1996, and is the youngest
of the three. 
Although it inherited a lot of platform-ports from NetBSD, 
some of the rarer platforms have become stunted due to lack of resources.

"`OpenBSD's"' emphasis is on "`Security"'. Though FreeBSD
and NetBSD have also not neglected this, it's where OpenBSD shines.
This doesn't mean that OpenBSD is a "`Security Software Stew"',
rather "`Security"' in OpenBSD also means \textit{Correctness}.
The team led by Theo de Raadt has performed a complete line by line
source code audit of the operating system to weed out any bugs and
detect and remove possible vulnerabilties.  (Naturally FreeBSD and
NetBSD also profited from this, as corrections were
adopted, where appropriate).  OpenBSD's  support for security also
means extensive support for cryptography.  Prominent here is the
unique support for several hardware crypto accelerator cards and
the broad integration of strong cryptography in the OS.  As Theo
de Raadt lives in Canada, these algorithms are not encumbered with
USA export restrictions.

\Abschnitt{--- Extra Info ---}
The English leaflet is maintained in parallel with the German version,
but as English is more compact, there's space below for extra info.

\Abschnitt{Meet BIM - Berkeley In Munich}
Berkeley In Munich meet monthly.
No membership fees, no bureacracy, join us !
http://www.berklix.org/bim/stammtisch/

\Abschnitt{Join BIM Mail Lists}
Mail: majordomo@ berklix.org  - Web:  http://www.berklix.org/help/

\Abschnitt{Free BSD and Other Software}
http://www.berklix.com/~jhs/free/ -  Free Software.

http://www.berklix.com/labels/ - BSD Cdrom Labels

\Abschnitt{Commercial BSD Support}
http://www.bsdpie.eu	- BSD Professionals In Europe

http://www.berklix.com/consultants/	- Global BSD Consultants Index


\vskip 0pt plus 1fill

\hbox to \hsize{\hss\rule{10em}{0.4pt}\hss}
\footnotesize
% \UNIX\
% is a registered trademark and
% \TOG\
% in the USA and other countries. All other marks and names are
% property of their respective owners; all appropriate registered
% trade marks and registered trade marks are recognized as such; their
% use serves only identification purposes.

\end{document}

%==================  T H E  E N D ==================
