Return to BSD News archive
Xref: sserve comp.unix.amiga:7389 comp.unix.misc:13022 comp.unix.programmer:18480 comp.unix.bsd:14369
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!darkstar.UCSC.EDU!news.hal.COM!olivea!decwrl!portal.com!purple
From: purple@shell.portal.com (Todd Vierling)
Newsgroups: comp.unix.amiga,comp.unix.misc,comp.unix.programmer,comp.unix.bsd
Subject: The AmiNIX FAQ, posting 1
Followup-To: comp.unix.amiga
Date: 23 Jul 1994 06:47:47 GMT
Organization: Portal an InterNetNews Site
Lines: 90
Message-ID: <30qeej$alf@news1.svc.portal.com>
NNTP-Posting-Host: jobe.shell.portal.com
The AmiNIX Operating System FAQ - Current version: 0.2.1 Alpha
1. What is AmiNIX?
1.1. Define AmiNIX, please.
AmiNIX is an implementation of the publically available 4.4BSD (NetBSD)
for the Amiga computer, that uses its native operating system AmigaOS as
a microkernal and base for its operations. As such, AmiNIX has the ability
to run concurrently with AmigaOS and can use any hardware that AmigaOS can
use.
1.2. Where can I get it?
AmiNIX is going through the same testing stages as just about any software;
alpha, beta, and gamma testing. No FTP site or other method has yet been
set for obtaining the gamma versions of AmiNIX.
2. What are its features and drawbacks?
2.1. What can I run on it?
Since its C-language implementation is the same as BSD UNIX, it is
functionally identical to BSD when compiling programs. In addition, `true'
NetBSD and SunOS binaries will run as long as the correct CPU and/or FPU
is being used.
2.2. What equipment does it run on?
AmiNIX's kernal will be distributed in several forms:
68000+/No MMU/No FPU (1) (2)
68020+/No MMU used/No FPU (1) (2)
68020+/No MMU used/FPU required (2)
68020+/MMU used/No FPU (1)
68020+/MMU used/FPU required
68040/MMU used/68040 FPU used
(1) No FPU is in this implementation and as such, may require FPU emulation
code in the final version. (Or, may require compilation to its own
libraries.)
(2) No MMU is in this implementation and as such, no virtual memory or memory
protection can be used.
The libraries will also have the variations above excluding the MMU/No MMU
differences as this only matters in the kernal.
2.3. What special hardware works on it?
Just about anything with an Amiga interface. Network cards require SANA-II
device drivers. Serial cards require serial.device compatible interfaces,
etc. Ttys can even be routed through AmigaOS windows.
2.4. How do filesystems work?
True UNIX filesystems may be mounted, however the shared format will
most likely be the popular usage; filename translation of AmigaOS files to
UNIX. Security measures are implemented to prevent problems (i.e. a soft
or symbolic link to a not normally accessible AmigaOS directory will
not show up nor allow .. parenting from it).
2.5. What problems can I have, especially relating to security?
Well, first off, the non-MMU versions are VERY insecure and recommended only
for testing and single-user applications. For multi-user applications, the
MMU version is needed for the memory protection. Since system calls are made
through a TRAP function call (not NetBSD's TRAP #1 -- actually TRAP #7, but
TRAP #1 is kept for the binary compatibility mentioned above), suoervisor
mode as well as AmigaOS itself is kept from access of AmiNIX programs.
(After all, we don't want someone calling Supervisor() from AmiNIX, do we? :)
2.6. How do libraries work?
Linked libraries such as libc will be provided. However, as AmiNIX moves
along, some of the more common functions or ones used in the kernal too will
become dynamically loaded shared libraries in a proprietary LoadSeg()able
format, with the linked library containing only TRAP #7 glue.
3. What about programming help?
I could always use extra brains, but remember you will need good knowledge
of 680x0 supervisor mode, UNIX internals and system calls (LOW LEVEL, not
printf() or the like), and UNIX file formats like a.out.
If you think you can help mail me at purple@shell.portal.com.
------------------------------------------------------------------------------
If you have any additional questions you'd like to see answered here, send