From: jhi@snakemail.hut.fi (Jarkko Hietaniemi)
Subject: Amiga Mach FAQ
Organization: Helsinki University of Technology, Finland
Distribution: comp
Date: 23 Jan 93 18:07:57 GMT


(NB: this is *not* crossposted to comp.os.mach now because
     a mite earlier version was posted there just a few days ago)

Note a new feature: keyword index at the end.

--
AmigaMach FAQ

$Id: KludgeMach-FAQ,v 1.20 1993/01/23 17:49:24 jhi Exp jhi $

====== WHAT?

Mach kernel (MK78) has been ported to Commodore Amigas.

KludgeMach
The Amiga Mach port is also known affectionately as "KludgeMach".

=== System Requirements
The port works provably on the following platforms:

- A3000 with AmigaDOS 2.04 in RAM with 4MB fast RAM (68030 25MHz)
- A2500 with 2 MB fast RAM (68030)
- A2000 with GVP Combo (68030 33MHz)
- A500  with CSA MegaMidget Racer (68030)

== CPU requirement
Motorola 68030 definitely works, 68020 should be sufficient as long as
a MMU (68851) is available.  MMU is ABSOLUTELY required.  On a
68040 Mach sort of boots but checking needs to be made whether the
same binaries and sources still run on a 68030.

== Memory requirement
To boot the KludgeMach at least 2MB fast RAM is required.
KludgeMach DOES NOT USE chip RAM at all.  By tweaking sources the
fast RAM requirement could perhaps be pushed down to 512kB.

== Diskspace requirement
Diskspace requirement of the binaries is only 300kB.
The current distribution CONTAINS ONLY THE SOURCES and to build Mach
at least 3MB of fast RAM is required.  To build the binaries, 25MB of
diskspace is needed, of this 15MB is for Mach, 10MB for the
development tools.  The minimum memory requirement for the compilation
is at least 2 MB (works only with optimization turned off), 4MB is
probably enough.

== Future requirements
NOTE: these requirements are only for now; in near future the
distribution is likely to grow significantly because device drivers
and servers are added.  The recommended minimum is then 4MB fast RAM
and 40MB disk.  Nice-to-have amounts are then 8MB fast RAM and 100MB disk:
this much is needed for double build directories and for possible
Mach-based filesystem's playground.

====== WHY?

The KludgeMach project aims at building a free UNIXish environment for
the Commodore Amiga computers.  As its base it will use the Mach
microkernel built at Carnegie Mellon university (CMU).  Mach is
OS-independent, however, and therefore other OSs could also be run
on top of it as servers.

====== WHERE?

The port is available by FTP from the following places:
(the IP addresses are also mentioned to cater those poor souls that
 do not have name servers)

Australia FTP sites:

        monu1.cc.monash.edu.au:/pub/mach              GMT+10 (NSW)
        IP: 130.194.1.101

Europe FTP sites:

        ftp.funet.fi:/pub/mach/amiga                  GMT+2  (EET)
        (or /pub/amiga/mach, both work)
        IP: 128.214.6.100

        ftp.dfv.rwth-aachen.de:/pub/amiga/mach        GMT+1  (MET)
        (or ftp.informatik.rwth-aachen.de, both work)
        IP: 137.226.4.105

United States FTP sites:

        homeboy.wpi.edu:/pub/mach                     GMT-5  (EST)
        IP: 130.215.8.99

        oes.orst.edu:/pub/mach                        GMT-8  (PST)
        IP: 128.193.124.2

== monu1 Role
monu1.cc.monash.edu.au is the primary distribution site BUT DO USE
THE SITE NEAREST TO YOU WHEN DOWNLOADING (ftp get'ting), NOT monu1.
The link to "down under" is seriously limited.  When uploading (ftp
put'ting), use the incoming/ directory of monu1.  Also remember to do
your ftp'ing when there is night at the site you are using.  The
distribution is mirrored daily from monu1 to homeboy and oes and from
there daily to Germany and Finland.

== To Get Started
You need only the file

/pub/mach/amiga/KludgeMach-<latest>.tar.Z

to get started. Currently the latest version is 0.007, based on CMU
MK78.  Note that the European sites have one directory deeper
hierarchy, you will need to get

        /pub/mach/amiga/amiga/KludgeMach-<latest>.tar.Z

== SIM
SIM is a kernel debugger that will be useful if (when) you
start hacking on the Mach kernel.  It was done by Stefan Walter
<swalter@avalon.physik.unizh.ch>.

== Developing Tools
If you develop AmigaMach, it is best to use the tools provided
in the distribution (directory tools/).  This because then everyone
will know what the others are talking about (basically, face the
same bugs :-).  If you want/need to use some other tools, please
first discuss the choice in the mailing list and then if the new tool
is really deemed necessary, provide it to others by uploading it
to monu1.  The tools that are currently agreed upon are:

        gcc-2.2.2       (remember to apply *Amiga* fixes 1 to 3)
        OR
        gcc-2.3.3       *)
        pdksh-920711
        dmake
        gtar10
        GNU parser/patch utils

*) Niklas Hallqvist <niklas@appli.se>:  Works for building the Mach
   kernel but NOT for for example building utilities because static
   libraries are not working.  2.3.3 is not going to be OK for about
   five weeks (= before mid-February 1993) because Markus Wild
   (the Amiga gcc porter and maintainer) will be away for that
   period of time.

== monu1 Contents
The full contents of the monu1 distribution were Fri Jan 22 1993 2:15pm:

/pub/mach:                      - you are here
total 12
-rw-r--r--  1 1606         2761 Sep 11 13:33 README
drwxr-xr-x  4 1606         2048 Jan 15 17:28 amiga
drwxr-xr-x  2 1606         2048 Oct  6 12:46 cmu_src
drwxr-xr-x  2 1606         2048 Oct  6 12:46 contrib
drwxrwx-wx  2 1606         2048 Jan  7 12:29 incoming

/pub/mach/amiga:                - sources to AmigaMach
total 6550
-rw-r--r--  1 ftp         19798 Jan  2 01:48 AmigaMach-FAQ
-rw-r--r--  1 1606         5178 Oct 18 01:45 Bootstrap.patch
-rw-r--r--  1 1606         2065 Oct 19 12:37 Bootstrap2.patch
-rw-r--r--  1 1606        26580 Jan  7 12:37 GVP.patch
-rw-r--r--  1 1606      3041123 Sep 20 15:52 KludgeMach-0.006.tar.Z
-rw-r--r--  1 ftp       3317969 Dec 14 15:36 KludgeMach-0.007.tar.Z
-rw-r--r--  1 ftp         19798 Jan  2 01:48 KludgeMach-FAQ
-rw-r--r--  1 1606         8341 Sep  3 19:52 KludgeMach-README
-rw-r--r--  1 1606         5301 Oct 22 17:45 SCSI.patch
-rw-r--r--  1 1606         5944 Oct 22 17:45 SCSI2.patch
-rw-r--r--  1 1606        68957 Sep  3 12:51 SIM.lha
-rw-r--r--  1 1606         8928 Jan 15 17:28 adosfsys.tar.Z
drwxr-xr-x  2 1606         2048 Oct  6 12:48 diffs
-rw-r--r--  1 1606        35326 Sep 27 12:58 hd_wilde.diff
-rw-r--r--  1 ftp         53096 Sep 11 12:50 scsi9091.lzh
drwxr-xr-x  2 1606         2048 Jan  7 12:30 tools
-rw-r--r--  1 ftp         25840 Sep 11 12:50 uart.tar.Z

/pub/mach/amiga/diffs:          - differences between versions
total 60
-rw-r--r--  1 1606        41209 Sep 11 15:33 KludgeMach-0.000-0.003.diff
-rw-r--r--  1 1606        15232 Sep 18 00:12 KludgeMach-0.004-0.005.diff
-rw-r--r--  1 1606         1689 Sep 21 01:54 KludgeMach-0.005-0.006.diff

/pub/mach/amiga/tools:          - tools that might be helpful
total 8086
-rw-r--r--  1 1606          388 Oct  5 11:21 GettingGNUTools
-rw-r--r--  1 1606       345600 Sep  4 18:43 dmake.lha
-rw-r--r--  1 1606           80 Sep  4 18:47 dmake.lha.readme
-rw-r--r--  1 ftp          7286 Oct  5 00:42 gcc-2.2.2-fix2.lha
-rw-r--r--  1 ftp        173155 Dec 14 17:42 gcc-2.2.2-fix3.lha
-rw-r--r--  1 1606      3306066 Sep  4 11:54 gcc-2.2.2.lha
-rw-r--r--  1 1606          213 Sep  4 11:55 gcc-2.2.2.lha.readme
-rw-r--r--  1 ftp       3588223 Jan  4 00:51 gcc-2.3.3.lha
-rw-r--r--  1 ftp         32720 Sep  5 21:42 gcc222-fix1.lha
-rw-r--r--  1 ftp        244736 Sep 11 12:54 gtar10.lha
-rw-r--r--  1 ftp         86380 Sep  9 08:15 parserutils.lha
-rw-r--r--  1 ftp         54538 Sep  9 08:15 patchutils.lha
-rw-r--r--  1 1606       304585 Sep  4 11:55 pdksh-920711.lha
-rw-r--r--  1 1606          154 Sep  4 11:55 pdksh-920711.lha.readme

/pub/mach/cmu_src:              - unretouced CMU sources
total 4818
-rw-r--r--  1 1606          254 Sep  5 10:38 getting_bsdss
-rw-r--r--  1 1606      2863311 Sep  3 13:52 mk78.tar.Z
-rw-r--r--  1 1606       219675 Sep  3 13:53 poe9.tar.Z
-rw-r--r--  1 1606      1777023 Sep  3 13:53 user18.tar.Z

/pub/mach/contrib:              - other random sources
total 494
-rw-r--r--  1 1606           26 Sep  8 15:39 .login
-rw-r--r--  1 1606        92701 Sep  3 12:51 MachSun3.tar.Z
-rw-r--r--  1 1606        10327 Sep  8 11:27 Trigger
-rw-r--r--  1 1606        69167 Sep  3 12:52 mach030.tar.Z
-rw-r--r--  1 1606        11476 Sep  8 11:30 mach_disklabel_diffs.tar.Z
-rw-r--r--  1 1606       283131 Sep  8 11:33 poe-kernel-with-disk-image.tar.Z
-rw-r--r--  1 1606         2571 Sep  8 11:27 second_SYS.h

/pub/mach/incoming:             - put new stuff here

== European Hierarchy
Note that the European sites have one directory deeper hierarchy, you
will need to cd to /pub/mach/amiga, just /pub/mach is not enough.
Note also that the directory hierarchy (where the things are) may
mutate because new material will accumulate and the hierarchy might
need reorganizing.  The rule of thumb: use the nearest ftp site, cd to
/pub/mach or /pub/mach/amiga (non-Europe and Europe, respectively) and
hunt for READMEs and FAQs.

== Amiga Development Tools
In addition, oes.orst.edu mirrors amiga.physik.unizh.ch:/amiga/devel
at /pub/mach/devel.  The directory contains all kinds of Amiga program
development tools.  ftp.funet.fi has very similar directory called
/pub/amiga/programming/c.

ftp.funet.fi also has a copy of soda.berkeley.edu:/pub/mach
at /pub/mach/soda.berkeley.edu,  this directory contains
BSD single server material.  This is not continuously mirrored, it
is only a snapshot of 7th of September 1992.

== Mach documentation
Mach documentation is available by ftp from

        mach.cs.cmu.edu:doc                     GMT-5  (EST)
        IP: 128.2.209.192

For example doc/osf/kernel_principles.ps is a good starting place.

====== BEWARE!

KludgeMach works, but only for suitably small values of "works".
Hardcore hacker attitude useful.

====== WHO?

The initial port was done by Bryan Ford <baford@peruvian.utah.edu>.

Amiga Mach is working but still far from complete.  Minor details such
as an operating system are still missing.  Volunteers for all kind of
jobs are very welcome.

- coordinators for various levels of the development work

  Michael Saleeba <zik@aurora.cc.monash.edu> maintains the primary
  distribution site and has volunteered to act as a clearing-house.
  Report both to the list and to Michael if you have some special
  skills, hardware or just time to hack around.

  Michael is also in charge of the "offical" releases so SEND YOUR PATCHES
  TO Michael.  Here are the guidelines:
> * Use diff -rc to create a patch I can apply directly to the directory
> structure.
> 
> * Send the patch to me and tell me you want it added. Tell me which
> version it was derived from in case of merge problems.
> 
> * I'll add it to the diffs directory and increment the version on the
> tar file. I'll also keep one recent "known to be kinda working"
> version around.

- ftp service: the number of ftp sites is adequate (5) at the moment. *)
  The people in charge are:
  monu1.cc.monash.edu.au      Michael Saleeba
  homeboy.wpi.edu             Dominic Giampolo <nick@homeboy.wpi.edu>
  oes.orst.edu                        Erik Bennett <bennett@oes.orst.edu>
  ftp.dfv.rwth-aachen.de      Stefan Becker
                                <stefanb@pool.informatik.rwth-aachen.de>
  ftp.funet.fi                        Jarkko Hietaniemi <jhi@ftp.funet.fi>
*) If you are, however, *routinely* mirroring AmigaMach somewhere
   around the world, please drop jhi@ftp.funet.fi a note so your site
   can be added to this list.

- further work on the Mach kernel:
  The initial port to MK74 was done by Bryan Ford, Bryan also upgraded
  the sources to MK78.  Additional work has been done by
  Niklas Hallqvist <niklas@appli.se> and by Stefan Becker.
  Niklas also maintains the amiga-mach mailing list.

- console device: Bryan Ford and Keith Gabryelski <ag@monique.rt.com>,
  a former Amiga UNIX Development Team member, are working on this.

- drivers: SCSI, AT IDE, WD33C92, WD33C93, Commodore 2065/2090/2091
  expertise needed.

  GVP series II SCSI support is already in by Niklas Hallqvist
  <niklas@appli.se>.

    The official C= Amiga UNIX (SVR4.2) has many device drivers WITH sources.
    Their copyright status needs to be checked from Commodore.  Keith
    Gabryelski has volunteered to contact C= about this.
    Ty Sarna <tsarna@endicor.com> is contacting GVP about their
    drivers.  Markus Illenseer <markus@techfak.uni-bielefeld.de>
    has already contacted Ralph Babel of GVP: 
> He knew about the Mach Port already, he is very interested on a running
> kernel and a running Server. But he is not willing to implement a GVP SCSI
> driver while nothing is running on the kernal. He states that he has not much
> time to do something which is as yet not very usefull. But he is willing to
> do something when the situation is more stable and more reliable.
> I asked him whether he could start on a GVP support when the driver for
> the A3000-SCSi and the A2091 is finished, and he thought this could be
> a point to enter into Mach.

    Other 3rd party vendors like IVS could also use some
    questioning.  

- an OS :-) Work and queries are currently progressing on several fronts:

  BNR2SS/BSDSS: Michael Saleeba [Zik] <zik.aurora.cc.monash.edu>
  The situation is a bit muddy: CMU has stopped SUPing BSDSS.

  BSD4.4: Real Soon Now -- the "lite" or unencumbered version should
  be released 4Q92. *)

*) This is running KIND OF late...Anyone know anything about the schedule?

  Berkeley Sprite: Ty Sarna has researched this possibility.  Sprite
  unfortunately seems at the moment be unsuitable:

Mike Kupfer <kupfer@cs.berkeley.edu>:
>
> I understand that you're interested in the Mach-based Sprite
> single-server.  I'm the person who did the single-server.  I no longer
> work for the University of California, but I can give you some
> information about the server.
> 
> - The sources for the Sprite single-server are available for anonymous
>   ftp from allspice.berkeley.edu, in ~ftp/pub.  These sources are
>   primarily intended for browsing.  They do not include a bunch of
>   header files, Sprite libc sources, makefile libraries, or the
>   CThreads changes necessary to build the server.  (Actually, the
>   CThreads changes might be in a recent MK release; I haven't
>   checked.)  Please note that the ftp service on allspice is a bit
>   unreliable.  If you have problems using it, you can send mail to
>   root@sprite.berkeley.edu, and somebody will kick the appropriate
>   daemon.
> 
> - The Sprite single-server implements a subset of Sprite
>   functionality.  There is no binary compatibility, either with native
>   Sprite or with UNIX.  Process migration is not supported, nor is
>   access to the local disk.  Most of the Sprite distributed file
>   system is implemented, including Sprite cache consistency and
>   support for Sprite pseudo-devices.  The single-server currently only
>   runs on DECstations.  Performance of the Andrew benchmark is roughly
>   1/2 that of native Sprite on a DECstation 5000.
> 
> - Because the single-server cannot access the local disk, it can only
>   be used within an existing Sprite cluster.  That is, before you can
>   run the Sprite single-server, you would have to first install native
>   Sprite.  This is a non-trivial task.  In fact, the Sprite group gave
>   up on supporting external sites in early 1992, and requests for a
>   Sprite distribution are now politely refused.
> 
> - If you would like to browse any of the missing sources, I can try to
>   put together a tar file for you.  Also, feel free to send me mail if
>   you have additional questions.  Please be patient if I am slow in
>   answering--I already have many other things that need my attention.
> 

  CMU POE: VOLUNTEER NEEDED TO CHECK ON THIS: can a UNIX server
  be built from the sources available and is an AT&T license needed???
  not entirely free either???

  GNU Hurd: Michael Saleeba:
> They have bits of it running. The work they've done to date is
> available from prep.ai.mit.edu if I remember correctly. You've got to
> realise they're building an OS pretty much from scratch though, so
> it's going to take time.
> 
> Some time ago I spoke with Richard Stallman on the subject. He's very
> interested in having m68k-based machines running the Hurd. In fact
> apparently GNU have a couple of Amigas they'd like to use to help
> develop the Hurd, so it'd be nice if we could help out with that :-)

  Linux:
  The upper layers may be portable enough to make an UNIX server???
  Some work has been done on this by Markus Wild and the result was
  a disappointment: 
> Well... I took a (really quick..) look at Linux sources, and well, I didn't
> like them. You literally smell i386, messydos, pee-cee in every corner
> of the source, really not a pleasure imagining that this beast should ever
> run on something different than what it was targeted for.
  Wild is also the right person to contact about the gcc port for
  Amiga, dmake and gtar.

  Some sort of porting of Linux to Amiga _is_, however, underway.
  Could some one who knows more please comment?

  386BSD: are the upper layers of Jolitz' work portable enough?
  Michael Richardson <mcr@latour.sandelman.ocunix.on.ca> has at least a
  partial answer:
>   Yes, it is. The ISA bus architecture stuff is sufficiently isolated
> that making it work on other types of 386 system would be a snap. The
> 386 specific stuff is isolated to one directory tree (in which the isa
> stuff is located) as well. 
>   I am unclear as to how a Mach single server interacts with the rest
> of mach so I can't comment more.

- stabile 68040 port: Michael L. Hitch <osymh@trex.oscs.montana.edu>
  is working on this

- contacts with C= technical people about hardware (and AmigaOS emulator???)

  Some C= current and former employees have already stepped out of
  the woodwork:

  Ken Dyke              <kcd@cbmvax.cbm.commodore.com>
  AmigaOS Networking

  Keith Gabryelski
  AmigaUNIX Networking, X11, serial devices, Ethnernet devices,
  random hardware (audio, clock, etc)

- contacts with GNU project NEEDED (see the above discussion about Hurd)

- cross-compilation environment
  Jukka Partanen <jtp@cs.hut.fi> is researching this area.

- RDB (Rigid Block Standard) experts needed

- AmigaOS emulator (C= co-operation needed most probably?)

- this FAQ file is maintained by Jarkko Hietaniemi

DRAMATIS PERSONAE

Erik Bennett            <bennett@oes.orst.edu>
        oes.orst.edu ftp maintainer

Stefan Becker           <stefanb@pool.informatik.rwth-aachen.de>
        ftp.dfv.rwth.aachen-de ftp maintainer

Ken Dyke                <kcd@cbmvax.cbm.commodore.com>
        C= AmigaOS Networking engineer

Bryan Ford              <baford@peruvian.utah.edu>
        the author of the initial port of Amiga Mach

Keith Gabryelski        <ag@monique.rt.com>
        former C= Amiga UNIX Networking/X11/device Engineer
        C= Amiga UNIX device driver source status

Dominic Giampolo        <nick@homeboy.wpi.edu>
        homeboy.wpi.edu ftp maintainer

Niklas Hallqvist        <niklas@appli.se>
        GVP SCSI driver maintainer
        amiga-mach mailing list maintainer

Jarkko Hietaniemi       <jhi@ftp.funet.fi>
        ftp.funet.fi ftp maintainer
        FAQ maintainer

Michael L. Hitch        <osymh@trex.oscs.montana.edu>
        68040 porting

Mike Kupfer		<kupfer@cs.berkeley.edu>
	Sprite single server
	(nothing to do with AmigaMach (yet? :-))

Jukka Partanen          <jtp@cs.hut.fi>
        cross-compilation environment

Michael Richardson      <mcr@latour.sandelman.ocunix.on.ca>
        386BSD preliminary peek

Michael Saleeba         <zik@aurora.cc.monash.edu>
        monu1.cc.monash.edu.au ftp maintainer (the primary site)
        the central coordinator
        the official releases
	
Ty Sarna                <tsarna@endicor.com>
        Sprite research
        GVP contact

Stefan Walter		<swalter@avalon.physik.unizh.ch>
	SIM

Markus Wild             <wild@amiga.physik.unizh.ch>
        Linux preliminary peek
        Amiga ports of GCC and gtar
        dmake

====== HOW?

Want more information?

Join the mailing lists

amiga-mach@appli.se
machm68k@yoyo.cc.monash.edu.au

by sending a subscribe message (Subject: subscribe) to

amiga-mach-request@appli.se
machm68k-request@yoyo.cc.monash.edu.au

NOTE: do not send your subscribal messages to amiga-mach or machm68k.

amiga-mach mailing list is the main mailing list to use.  It can,
however, can get quite congested at times.  The machm68k mailing list
is for discussion about porting Mach to m68k platforms in general, not
just the Amiga.                                                               

The main list, amiga-mach, is most useful as an information channel
both for asking questions and for sending answers and progress reports.
For specific subprojects people are encouraged to use either personal
mail or create mailing lists if the subject is not necessarily useful
for "general public".
For example people working actively with console driver might get
together and create a sub-mailing list.  A person who knows how to and
is able to create and maintain a mailing list is needed.

machm68k mailing list is currently rather quiet because a generic
Mach port to Motorola does not yet exist, only a port to Amiga.
There has been some discussion about the syscall conventions
of Amiga UNIX, MacIntoshes and Mac's A/UX on the amiga-mach list.
Standardizing call conventions would make possible to have binary
compability between m68k-based Machs.

This FAQ is updated about biweekly and then merged to the ftp distribution.
It is sent about monthly to the amiga-mach mailing list and crossposted to
the following USENET newsgroups:

comp.os.mach,comp.sys.amiga.hardware,comp.sys.amiga.programmer,comp.unix.amiga

Index
	Topic                                                Line

	386BSD ............................................ 394
	68020 ............................................. 21
	68030 ............................................. 15, 16, 17, 18, 21, 24
	68040 ............................................. 23, 404, 460
	68851 ............................................. 22
	A/UX .............................................. 522
	A2000 ............................................. 17
	A2065 ............................................. 288
	A2090 ............................................. 288
	A2091 ............................................. 288
	A2500 ............................................. 16
	A3000 ............................................. 15
	A500 .............................................. 18
	ag@monique.rt.com ................................. 444
	Amiga Development Tools ........................... 216
	Amiga UNIX drivers ................................ 294
	amiga-mach ........................................ 495
	amiga-mach mailing list ........................... 453, 505
	amiga-mach-request ................................ 500
	amiga.physik.unizh.ch ............................. 217
	AmigaOS ........................................... 439
	AmigaOS emulator .................................. 426
	appli.se .......................................... 495
	AT IDE ............................................ 288
	Australia FTP sites ............................... 62
	baford@peruvian.utah.edu .......................... 441
	bennett@oes.orst.edu .............................. 432
	Berkeley Sprite ................................... 322
	BEWARE! ........................................... 235
	BNR2SS/BSDSS ...................................... 314
	Bryan Ford ........................................ 280, 285, 441
	BSD single server ................................. 224
	BSD4.4 ............................................ 317
	C= ................................................ 439, 446
	C= Amiga UNIX ..................................... 445, 446
	C= Amiga UNIX drivers ............................. 294
	C= contact ........................................ 407
	Carnegie Mellon university ........................ 52
	chip RAM .......................................... 28
	CMU ............................................... 52, 315, 365
	CMU POE ........................................... 365
	Combo ............................................. 17
	CPU requirement ................................... 20
	cross-compilation environment ..................... 421, 467
	CSA MegaMidget Racer .............................. 18
	Developing Tools .................................. 110
	Diskspace requirement ............................. 31
	dmake ............................................. 389, 487
	Dominic Giampolo .................................. 448
	DRAMATIS PERSONAE ................................. 430
	Erik Bennett ...................................... 432
	Europe FTP sites .................................. 67
	European Hierarchy ................................ 100, 207
	FAQ ............................................... 428, 457, 526
	fast RAM .......................................... 15, 16, 27, 29, 34, 43
	FTP ............................................... 58
	ftp servers ....................................... 267
	FTP sites ......................................... 58
	ftp.dfv.rwth-aachen.de ............................ 73, 272
	ftp.dfv.rwth.aachen-de ............................ 436
	ftp.funet.fi ...................................... 69, 219, 222, 274, 456
	Future requirements ............................... 40
	GCC ............................................... 486
	gcc ............................................... 119, 121, 132, 388
	GNU ............................................... 419
	GNU contact ....................................... 419
	GNU Hurd .......................................... 369
	gtar .............................................. 389, 486
	GVP ............................................... 291, 479
	GVP Combo ......................................... 17
	GVP contact ....................................... 297
	GVP SCSI driver ................................... 452
	homeboy ........................................... 79
	homeboy.wpi.edu ................................... 270, 449
	How to join the mailing lists? .................... 493
	HOW? .............................................. 489
	Hurd .............................................. 369
	initial port ...................................... 242, 442
	IP addresses ...................................... 59
	IVS ............................................... 309
	Jarkko Hietaniemi ................................. 455
	jhi@ftp.funet.fi .................................. 455
	jtp@cs.hut.fi ..................................... 466
	Jukka Partanen .................................... 466
	kcd@cbmvax.cbm.commodore.com ...................... 438
	Keith Gabryelski .................................. 285, 444
	Ken Dyke .......................................... 438
	KludgeMach ........................................ 10
	kupfer@cs.berkeley.edu ............................ 462
	Linux ............................................. 380, 485
	Mach documentation ................................ 227
	machm68k .......................................... 496
	machm68k mailing list ............................. 519
	machm68k-request .................................. 501
	MacIntosh ......................................... 522
	mailing lists ..................................... 493
	Markus Wild ....................................... 484
	mcr@latour.sandelman.ocunix.on.ca ................. 469
	Megamidget Racer .................................. 18
	Memory requirement ................................ 26
	Michael L. Hitch .................................. 459
	Michael Richardson ................................ 469
	Michael Saleeba ................................... 472
	microkernel ....................................... 52
	Mike Kupfer ....................................... 325, 462
	Mirroring Hierarchy ............................... 91
	MMU ............................................... 22
	monu1 ............................................. 64, 86, 134
	monu1 Contents .................................... 134
	monu1 Role ........................................ 85
	monu1.cc.monash.edu.au ............................ 269, 473
	Motorola .......................................... 520
	nick@homeboy.wpi.edu .............................. 448
	Niklas Hallqvist .................................. 282, 451
	niklas@appli.se ................................... 451
	oes ............................................... 82
	oes.orst.edu ...................................... 271, 433
	osymh@trex.oscs.montana.edu ....................... 459
	Other Driver Vendors .............................. 309
	Patch Submission Guidelines ....................... 255
	Platform requirements ............................. 12
	POE ............................................... 365
	RDB ............................................... 424
	Rigid Block Standard .............................. 424
	SCSI .............................................. 288, 291
	SCSI II ........................................... 291
	SIM ............................................... 105, 482
	soda.berkeley.edu ................................. 223
	Sprite ............................................ 322, 478
	Sprite single server .............................. 463
	Stefan Becker ..................................... 282
	Stefan Walter ..................................... 481
	stefanb@pool.informatik.rwth-aachen.de ............ 435
	swalter@avalon.physik.unizh.ch .................... 481
	System Requirements ............................... 12
	the latest version ................................ 99
	To Get Started .................................... 94
	tsarna@endicor.com ................................ 477
	Ty Sarna .......................................... 477
	United States FTP sites ........................... 77
	UNIX .............................................. 50
	Uploading ......................................... 89
	USENET ............................................ 528
	WD33C92 ........................................... 288
	WD33C93 ........................................... 288
	Western Digital ................................... 288
	WHAT? ............................................. 5
	WHERE? ............................................ 56
	WHO? .............................................. 240
	WHY? .............................................. 48
	wild@amiga.physik.unizh.ch ........................ 484
	yoyo.cc.monash.edu.au ............................. 496
	zik@aurora.cc.monash.edu .......................... 472

END_OF_FAQ