Кто ни будь пробовал инсталировать Unix System V под WinUAE?

[Anonimous]

Люди добрые у меня проблемма. скачал инсталятор Unix System V. Хочеться проинсталлировать по емуль WinUAE, но никак не получаеться. Кто нибусь сталкивался с этой проблеммой? Если решние вообще существует пожалуйста поделитесь опытом. Заранее благодарен.

[Dimon_LCS]

Люди добрые у меня проблемма. скачал инсталятор Unix System V. Хочеться проинсталлировать по емуль WinUAE, но никак не получаеться. Кто нибусь сталкивался с этой проблеммой? Если решние вообще существует пожалуйста поделитесь опытом. Заранее благодарен.

хехе
я качал архив и пытался на амигу 1200 поставить - дохлый номер - ей нужно именно железо от амига 3000unix вариант

[agents]

Я тут как то лазил по сети и наткнулся на UNIX на амиге,далее текстовик для каких машин предназначена и т.п,кому интерестно.


INSTALL(8) NetBSD System Manager's Manual INSTALL(8)

NAME
INSTALL - Installation procedure for NetBSD/amiga.

CONTENTS
About this Document............................................1
What is NetBSD?................................................2
Upgrade path to NetBSD 1.6.....................................2
Changes Between The NetBSD 1.5 and 1.6 Releases................2
Kernel......................................................2
Networking..................................................3
File system.................................................4
Security....................................................4
System administration and user tools........................4
Miscellaneous...............................................5
amiga specific..............................................6
The Future of NetBSD...........................................6
Sources of NetBSD..............................................7
NetBSD 1.6 Release Contents....................................7
NetBSD/amiga subdirectory structure.........................8
Miniroot file system........................................9
Binary distribution sets....................................9
NetBSD/amiga System Requirements and Supported Devices........10
Supported devices..........................................11
Getting the NetBSD System on to Useful Media..................12
Preparing your System for NetBSD installation.................15
Preparing your hard disk with HDToolBox....................15
Transferring the miniroot file system......................17
Installing the NetBSD System..................................17
Booting....................................................18
Once your kernel boots.....................................18
Post installation steps.......................................20
Upgrading a previously-installed NetBSD System................23
Once your kernel boots.....................................24
Compatibility Issues With Previous NetBSD Releases............25
Issues affecting an upgrade from NetBSD 1.5................25
Issues affecting an upgrade from NetBSD 1.4 or prior.......26
Using online NetBSD documentation.............................26
Administrivia.................................................27
Thanks go to..................................................28
We are........................................................30
Legal Mumbo-Jumbo.............................................34
The End.......................................................37

DESCRIPTION
About this Document

This document describes the installation procedure for NetBSD 1.6 on the
amiga platform. It is available in four different formats titled
INSTALL.ext, where .ext is one of .ps, .html, .more, or .txt:

.ps PostScript.

.html Standard Internet HTML.

.more The enhanced text format used on UNIX-like systems by the
more(1) and less(1) pager utility programs. This is the
format in which the on-line man pages are generally pre-
sented.

.txt Plain old ASCII.

You are reading the ASCII version.

What is NetBSD?

The NetBSD Operating System is a fully functional Open Source UNIX-like
operating system derived from the University of California, Berkeley Net-
working Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD
runs on fifty three different system architectures (ports), featuring
seventeen machine architectures across eleven distinct CPU families, and
is being ported to more. The NetBSD 1.6 release contains complete binary
releases for thirty eight different system architectures. (The fifteen
remaining are not fully supported at this time and are thus not part of
the binary distribution. For information on them, please see the NetBSD
web site at http://www.netbsd.org/.)

NetBSD is a completely integrated system. In addition to its highly
portable, high performance kernel, NetBSD features a complete set of user
utilities, compilers for several languages, the X Window System, firewall
software and numerous other tools, all accompanied by full source code.

NetBSD is a creation of the members of the Internet community. Without
the unique cooperation and coordination the net makes possible, it's
likely that NetBSD wouldn't exist.

Upgrade path to NetBSD 1.6
If you are not installing your system ``from scratch'' but instead are
going to upgrade an existing system already running NetBSD you need to
know which versions you can upgrade with NetBSD 1.6.

NetBSD 1.6 is an upgrade of NetBSD 1.5.3 and earlier major and patch re-
leases of NetBSD.

The intermediate development versions of code available on the main trunk
in our CVS repository (also known as ``NetBSD-current'') from after the
point where the release cycle for 1.6 was started are designated by ver-
sion identifiers such as 1.6A, 1.6B, etc. These identifiers do not des-
ignate releases, but indicate major changes in internal kernel APIs.
Note that the kernel from NetBSD 1.6 can not be used to upgrade a system
running one of those intermediate development versions. Trying to use
the NetBSD 1.6 kernel on such a system will probably result in problems.

Please also note that it is not possible to do a direct ``version'' com-
parison between any of the intermediate development versions mentioned
above and 1.6 to determine if a given feature is present or absent in
1.6. The development of 1.6 and the subsequent ``point'' releases is
done on a separate branch in the CVS repository. The branch was created
when the release cycle for 1.6 was started, and during the release cycle
of 1.6 and its patch releases selected fixes and enhancements have been
imported from the main development trunk.

Changes Between The NetBSD 1.5 and 1.6 Releases

The NetBSD 1.6 release provides numerous significant functional enhance-
ments, including support for many new devices, integration of hundreds of
bug fixes, new and updated kernel subsystems, and many user-land enhance-
ments. The result of these improvements is a stable operating system fit
for production use that rivals most commercially available systems.

It is impossible to completely summarize over eighteen months of develop-
ment that went into the NetBSD 1.6 release. Some highlights include:

Kernel

o Ports to new platforms including: algor, dreamcast, evbarm, hpcarm,
hpcsh, newsmips, sandpoint, sgimips, sun2, and walnut.

o Unified Buffer Cache (UBC) removes size restriction of the file sys-
tem's buffer cache to use all available RAM (if not otherwise used!)
and improves overall system performance.

o Round-robin page colouring implemented for various ports for better
cache utilisation, more deterministic run-time behaviour, and faster
program execution.

o A rewritten SCSI middle layer to provide a cleaner interface between
the different kernel layers, including a kernel thread to handle er-
ror recovery outside of the interrupt context. See scsipi(9).

o A new pipe implementation with significantly higher performance due
to lower overheads, which uses the UVM Page Loan facility.

o New boot loader flags -v (bootverbose) and -q (bootquiet), to be used
by kernel code to optionally print information during boot.

o An in-kernel boot time device configuration manager userconf(4), ac-
tivated with the -c boot loader flag.

o A work-in-progress snapshot of ACPI support, based on the 20010831
snapshot of the Intel ACPICA reference implementation.

o USB 2.0 support, in the form of a preliminary driver for the ehci(4)
host controller.

o Basic kernel support for IrDA in the form of the irframe(4) IrDA
frame level driver. Serial dongles and the oboe(4) driver are cur-
rently supported.

o Kernel configuration files can be embedded into the kernel for later
retrieval. Refer to INCLUDE_CONFIG_FILE in options(4) for more in-
formation.

o Many more kernel tunable variables added to sysctl(8).

o Linux binary emulation has been greatly improved, and now supports
Linux kernel version 2.4.18.

Networking

o Hardware assisted IPv4 TCP and UDP checksumming and caching of the
IPv6 TCP pseudo header. Support for checksum offloading on the
DP83820 Gigabit Ethernet, 3Com 3c90xB, 3Com 3c90xC, and Alteon
Tigon/Tigon2 Gigabit Ethernet cards.

o Zero-Copy for TCP and UDP transmit path achieved through page loaning
code for sosend().

o In-kernel ISDN support, from the ISDN4BSD project.

o 802.1Q VLAN (virtual LAN) support. See vlan(4).

o IPFilter now supports IPv6 filtering.

o ndbootd(8) added; used to netboot NetBSD/sun2 machines.

o racoon(8) added; IKE key management daemon for IPsec key negotiation,
from the KAME project.

o WEP encryption supported in ifconfig(8) and awi(4) driver.

o wi(4) and wiconfig(8) now support scanning for access points, and de-
faults to BSS instead of ad-hoc mode.

o Bridging support; currently only for ethernet. See bridge(4).

o In-kernel PPP over Ethernet (PPPoE) - RFC 2516, with much lower over-
head than user-land PPPoE clients. See pppoe(4).

o ifwatchd(8) added; invokes up-script and down-script when a network
interface goes up and down. Used by pppoe(4).

File system

o Enhanced stability of LFS version 2, the BSD log-structured file sys-
tem.

o dump(8), dumpfs(8), fsck_ffs(8), fsirand(8), newfs(8), and tunefs(8)
support a -F option to manipulate file system images in regular
files.

o makefs(8) added; creates file system images from a directory tree.
(Currently ffs only.)

o Enhanced ffs_dirpref() by Grigoriy Orlov, which noticeably improves
performance on FFS file systems when creating directories, and subse-
quently manipulating them.

o Fixes for free block tracking and directory block allocation in FFS
softdeps.

o Correctly support FFS file systems with a large number of cylinder
groups.

o Fix the endian independant FFS (FFS_EI) support.

o newfs(8) calculates default block size from the file system size, and
uses the largest possible cylinders/group (cpg) value if -c isn't
given.

o dpti(4) driver added; an implementation of the DPT/Adaptec SCSI/I2O
RAID management interface. Allows the use of the Linux versions of
dptmgr, raidutil, dptelog, (etc).

o Support for Windows 2000 `NTFS' (NTFS5).

o Tagged queueing support for SCSI drivers based on the ncr53c9x con-
troller.

Security

o Addition of a chroot(8) hierarchy for services including named(8),
ntpd(8), and sshd(8).

o Additional passwd(5) ciphers: MD5, and DES with more encryption
rounds. See passwd.conf(5).

o Several more code audits were performed.

o /etc/security performs many more checks and is far more flexible in
how it monitors changes. See security.conf(5).

System administration and user tools

o sushi(8) added; a menu based system administration tool.

o pgrep(1) and pkill(1) added; find or signal processes by name or oth-
er attributes.

o System upgrades are made easier through the etcupdate(8) script which
helps updating the /etc config files interactively, and the
/etc/postinstall script which is provided to check for or fix config-
uration changes that have occurred in NetBSD.

o stat(1) added; a user interface to the information returned by the
stat(2) system call.

o BSD sort(1) replaces GNU sort(1).

o The ``stop'' operation for rc.d(8) scripts waits until the service
terminates before returning. This improves the reliability of
``restart'' operations as well.

o Swap devices can be removed at system shutdown by enabling swapoff in
rc.conf(5).

o An optional watchdog timer which will terminate rc.shutdown(8) after
the number of seconds provided in rcshutdown_timeout from rc.conf(5).

Miscellaneous

o Support for multibyte LC_CTYPE locales has been integrated from the
Citrus project. Many Chinese, Japanese, Korean, and other encodings
are now available.

o Full support for cross-compilation of the base system, even as a non-
root user! src/build.sh is available for doing arbitrary cross-
builds; see src/BUILDING for more information. At least 38 ports for
the NetBSD 1.6 release were cross-built on a NetBSD/i386 system using
this mechanism.

o Migrated the following CPU platforms to ELF: arm, and m68k (including
amiga, hp300, mac68k, mvme68k, sun2, and x68k).

o Updates of most third party packages that are shipped in the base
system to the following latest stable releases:
- amd 6.0.6
- BIND 8.3.3
- binutils 2.11.2
- bzip2 1.0.2
- cvs 1.11
- dhcp 3.0.1rc9
- file 3.38
- gcc 2.95.3
- groff 1.16.1
- Heimdal 0.4e
- IPfilter 3.4.27
- kerberos4 1.1
- ksh from pdksh 5.2.14p2
- less 374
- nvi 1.79
- OpenSSH 3.4
- OpenSSL 0.9.6g
- Postfix 1.1.11
- ppp 2.4.0
- routed 2.24
- sendmail 8.11.6
- tcpdump 3.7.1

o Many new packages in the pkgsrc system, including the latest open
source desktop KDE3, OpenOffice, perl, Apache and many more. At the
time of writing, there are over 3000 third party packages available
in pkgsrc.

o Added AGP GART driver agp(4) for faster access to graphics boards.

o init(8) will create an mfs (memory based file system) /dev if
/dev/console is missing.

o vmstat(8) displays kernel hash statistics with -H and -h hash.

o wscons(4) supports blanking of VGA consoles.

Kernel interfaces have continued to be refined, and more subsystems and
device drivers are shared among the different ports. You can look for
this trend to continue.

amiga specific

This is the eighth major release of NetBSD for the Amiga and DraCo line
of computers.

New port-specific features include:

o Two stage boot loader capable of loading ELF or a.out as well as com-
pressed kernels.

o New device driver support:
- ZEUS ISDN-link and Individual Computers ISDN surfer
- BSC ISDN MAster II
- Repulse audio board
- Toccata driver (experimental)

The Future of NetBSD

The NetBSD Foundation has been incorporated as a non-profit organization.
Its purpose is to encourage, foster and promote the free exchange of com-
puter software, namely the NetBSD Operating System. The foundation will
allow for many things to be handled more smoothly than could be done with
our previous informal organization. In particular, it provides the
framework to deal with other parties that wish to become involved in the
NetBSD Project.

The NetBSD Foundation will help improve the quality of NetBSD by:

o providing better organization to keep track of development efforts,
including co-ordination with groups working in related fields.

o providing a framework to receive donations of goods and services and
to own the resources necessary to run the NetBSD Project.

o providing a better position from which to undertake promotional ac-
tivities.

o periodically organizing workshops for developers and other interested
people to discuss ongoing work.

We intend to begin narrowing the time delay between releases. Our ambi-
tion is to provide a full release every six to eight months.

We hope to support even more hardware in the future, and we have a rather
large number of other ideas about what can be done to improve NetBSD.

We intend to continue our current practice of making the NetBSD-current
development source available on a daily basis.

We intend to integrate free, positive changes from whatever sources sub-
mit them, providing that they are well thought-out and increase the us-
ability of the system.

Above all, we hope to create a stable and accessible system, and to be
responsive to the needs and desires of NetBSD users, because it is for
and because of them that NetBSD exists.

Sources of NetBSD

Refer to
http://www.netbsd.org/Sites/net.html.

NetBSD 1.6 Release Contents

The root directory of the NetBSD 1.6 release is organized as follows:

.../NetBSD-1.6/

CHANGES Changes since earlier NetBSD releases.

LAST_MINUTE Last minute changes.

MIRRORS A list of sites that mirror the NetBSD 1.6 distribution.

README.files README describing the distribution's contents.

TODO NetBSD 's todo list (also somewhat incomplete and out of
date).

patches/ Post-release source code patches.

source/ Source distribution sets; see below.

In addition to the files and directories listed above, there is one di-
rectory per architecture, for each of the architectures for which
NetBSD 1.6 has a binary distribution. There are also README.export-
control files sprinkled liberally throughout the distribution tree, which
point out that there are some portions of the distribution that may be
subject to export regulations of the United States, e.g. code under
src/crypto and src/sys/crypto. It is your responsibility to determine
whether or not it is legal for you to export these portions and to act
accordingly.

The source distribution sets can be found in subdirectories of the source
subdirectory of the distribution tree. They contain the complete sources
to the system. The source distribution sets are as follows:

gnusrc This set contains the ``gnu'' sources, including the source for
the compiler, assembler, groff, and the other GNU utilities in
the binary distribution sets.
55 MB gzipped, 247 MB uncompressed

pkgsrc This set contains the ``pkgsrc'' sources, which contain the in-
frastructure to build third-party packages.
12 MB gzipped, 94 MB uncompressed

sharesrc This set contains the ``share'' sources, which include the
sources for the man pages not associated with any particular
program; the sources for the typesettable document set; the
dictionaries; and more.
4 MB gzipped, 16 MB uncompressed

src This set contains all of the base NetBSD 1.6 sources which are
not in gnusrc, sharesrc, or syssrc.
27 MB gzipped, 136 MB uncompressed

syssrc This set contains the sources to the NetBSD 1.6 kernel for all
architectures; config(8); and dbsym(8).
22 MB gzipped, 114 MB uncompressed

xsrc This set contains the sources to the X Window System.
78 MB gzipped, 394 MB uncompressed

All the above source sets are located in the source/sets subdirectory of
the distribution tree.

The source sets are distributed as compressed tar files. Except for the
pkgsrc set, which is traditionally unpacked into /usr/pkgsrc, all sets
may be unpacked into /usr/src with the command:
# ( cd / ; tar -zxpf - ) < set_name.tgz

The sets/Split/ subdirectory contains split versions of the source sets
for those users who need to load the source sets from floppy or otherwise
need a split distribution. The split sets are named set_name.xx where
set_name is the distribution set name, and xx is the sequence number of
the file, starting with ``aa'' for the first file in the distribution
set, then ``ab'' for the next, and so on. All of these files except the
last one of each set should be exactly 240,640 bytes long. (The last
file is just long enough to contain the remainder of the data for that
distribution set.)

The split distributions may be reassembled and extracted with cat as fol-
lows:

# cat set_name.?? | ( cd / ; tar -zxpf - )

In each of the source distribution set directories, there are files which
contain the checksums of the files in the directory:

BSDSUM Historic BSD checksums for the various files in that di-
rectory, in the format produced by the command:
cksum -o 1 file.

CKSUM POSIX checksums for the various files in that directory,
in the format produced by the command:
cksum file.

MD5 MD5 digests for the various files in that directory, in
the format produced by the command:
cksum -m file.

SYSVSUM Historic AT&T System V UNIX checksums for the various
files in that directory, in the format produced by the
command:
cksum -o 2 file.

The MD5 digest is the safest checksum, followed by the POSIX checksum.
The other two checksums are provided only to ensure that the widest pos-
sible range of system can check the integrity of the release files.

NetBSD/amiga subdirectory structure

The amiga-specific portion of the NetBSD 1.6 release is found in the
amiga subdirectory of the distribution: .../NetBSD-1.6/amiga/
INSTALL.html
INSTALL.ps
INSTALL.txt
INSTALL.more Installation notes in various file formats, including this
file. The .more file contains underlined text using the
more(1) conventions for indicating italic and bold display.
binary/
kernel/
netbsd-GENERIC.gz
A gzipped NetBSD kernel containing code
for everything supported in this re-
lease.
netbsd.INSTALL.gz
A somewhat smaller kernel, which you
can use to boot the system on memory-
tight systems. This is the same kernel
as present on the miniroot.
sets/ amiga binary distribution sets; see below.
installation/
floppy/ amiga boot and installation floppies; see below.
miniroot/
amiga miniroot file system image; see below.
misc/ Miscellaneous amiga installation utilities; see
installation section, below.

Miniroot file system

The Amiga now uses a single miniroot file system for both an initial in-
stallation and for an upgrade. A gzipped version is available, for easi-
er downloading. (The gzipped version has the .gz extension added to
their names.)

miniroot.fs This file contains a BSD root file system setup to help you
install the rest of NetBSD or to upgrade a previous version
of NetBSD. This includes formatting and mounting your /
(root) and /usr partitions and getting ready to extract (and
possibly first fetching) the distribution sets. There is
enough on this file system to allow you to make a SLIP or
PPP connection, configure an Ethernet, mount an NFS file
system or ftp. You can also load distribution sets from a
SCSI tape or from one of your existing AmigaDOS partitions.

Binary distribution sets

The NetBSD amiga binary distribution sets contain the binaries which com-
prise the NetBSD 1.6 release for the amiga. There are eight binary dis-
tribution sets. The binary distribution sets can be found in the
amiga/binary/sets subdirectory of the NetBSD 1.6 distribution tree, and
are as follows:

base The NetBSD 1.6 amiga base binary distribution. You must in-
stall this distribution set. It contains the base NetBSD util-
ities that are necessary for the system to run and be minimally
functional. It includes shared library support, and excludes
everything described below.
17 MB gzipped, 41 MB uncompressed

comp Things needed for compiling programs. This set includes the
system include files (/usr/include) and the various system li-
braries (except the shared libraries, which are included as
part of the base set). This set also includes the manual pages
for all of the utilities it contains, as well as the system
call and library manual pages.
14 MB gzipped, 52 MB uncompressed

etc This distribution set contains the system configuration files
that reside in /etc and in several other places. This set must
be installed if you are installing the system from scratch, but
should not be used if you are upgrading.
1 MB gzipped, 1 MB uncompressed

games This set includes the games and their manual pages.
3 MB gzipped, 7 MB uncompressed

kern-GENERIC
This set contains a NetBSD/amiga 1.6 GENERIC kernel, named
/netbsd. You must install this distribution set.
2 MB gzipped, 3 MB uncompressed

man This set includes all of the manual pages for the binaries and
other software contained in the base set. Note that it does
not include any of the manual pages that are included in the
other sets.
7 MB gzipped, 27 MB uncompressed

misc This set includes the (rather large) system dictionaries, the
typesettable document set, and other files from /usr/share.
3 MB gzipped, 8 MB uncompressed

text This set includes NetBSD's text processing tools, including
groff(1), all related programs, and their manual pages.
2 MB gzipped, 6 MB uncompressed

NetBSD maintains its own set of sources for the X Window System in order
to assure tight integration and compatibility. These sources are based
on XFree86, and tightly track XFree86 releases. They are currently
equivalent to XFree86 3.3.6. Binary sets for the X Window System are
distributed with NetBSD. The sets are:

xbase The basic files needed for a complete X client environment.
This does not include the X servers.
3 MB gzipped, 7 MB uncompressed

xcomp The extra libraries and include files needed to compile X
source code.
2 MB gzipped, 8 MB uncompressed

xcontrib Programs that were contributed to X.
1 MB gzipped, 1 MB uncompressed

xfont Fonts needed by X.
6 MB gzipped, 7 MB uncompressed

xmisc Miscellaneous X programs.
1 MB gzipped, 1 MB uncompressed

xserver
2 MB gzipped, 4 MB uncompressed

The amiga binary distribution sets are distributed as gzipped tar files
named with the extension .tgz, e.g. base.tgz.

The instructions given for extracting the source sets work equally well
for the binary sets, but it is worth noting that if you use that method,
the filenames stored in the sets are relative and therefore the files are
extracted below the current directory. Therefore, if you want to extract
the binaries into your system, i.e. replace the system binaries with
them, you have to run the tar -xpf command from the root directory ( / )
of your system. This utility is used only in a Traditional method in-
stallation.

Note: Each directory in the amiga binary distribution also has its own
checksum files, just as the source distribution does.

NetBSD/amiga System Requirements and Supported Devices

NetBSD 1.6 runs on any Amiga that has a 68020 or better CPU with some
form of MMU, and on 68060 DraCos.

NetBSD does not, and will never, run on run on A1000, A500, A600, A1200,
A2000, A4000/EC030, CDTV and CD32 systems that are not enhanced by a CPU
board.

For 68020 and 68030 systems, a FPU is recommended but not required for
the system utilities. 68LC040, 68040V and 68LC060 systems don't work
correctly at the moment.

The minimal configuration requires 6 MB of RAM (not including CHIPMEM!)
and about 75 MB of disk space. To install the entire system requires
much more disk space, and to run X or compile the system, more RAM is
recommended. (6 MB of RAM will actually allow you to compile, however it
won't be speedy. X really isn't usable on a 6 MB system.)

Here is a table of recommended HD partition sizes for a full install:

Partition Suggested + X Needed + X
/ (root) 25 MB 25 MB 20 MB 20 MB
/usr 245 MB 270 MB 120 MB 145 MB
/var 20 MB 20 MB 5 MB 5 MB
swap 2*RAM below 32 MB, then up to you

Anything else is up to you!

As you may note the recommended size of /usr is 125 MB greater than need-
ed. This is to leave room for a kernel source and compile tree as you
will probably want to compile your own kernel. GENERIC is large and
bulky to accommodate all people. For example, most people's machines
have an FPU, so you do not need the bulky FPU_EMULATE option.

Preconfigured or precompiled packages are installed below /usr/pkg by de-
fault. You should either make /usr larger (if you intend to install a
lot of them), make /usr/pkg an additional partition, use the -p option to
pkg_add to install them in a different place, or link /usr/pkg to a dif-
ferent place.

If you only have less than 8 MB of fast memory, you should make your swap
partition larger, as your system will be doing much more swapping. Espe-
cially: do not place it onto a old small (and normally slow) disk!

Supported devices

o A4000/A1200 IDE controller, including ATAPI devices

o SCSI host adapters
- 33c93 based boards: A2091, A3000 builtin, A3000 builtin
modified for Apollo accelerator board, and GVP series II.
- 53c80 based boards: 12 Gauge, IVS, Wordsync/Bytesync and
Emplant The Emplant SCSI adapter has been reported by a
party to hang after doing part of the installation without
problems
- 53c710 based boards: A4091, Magnum, Warp Engine, Zeus and
DraCo builtin
- FAS216 based SCSI boards: FastLane Z3, Blizzard I and II,
Blizzard IV, Blizzard 2060, CyberSCSI Mk I and II
- 53c770 based SCSI boards: Cyberstorm Mk III SCSI, Cyber-
storm PPC SCSI

o Video controllers
- ECS, AGA and A2024 built in on various Amigas
- Retina Z2 (no X server available), Retina Z3 and Altais
- Cirrus CL GD 54xx based boards: GVP Spectrum, Picasso II,
II+ and IV, Piccolo and Piccolo SD64
- Tseng ET4000 based boards: Domino and Domino16M proto, oM-
niBus, Merlin
- A2410 (no X server available)
- Cybervision 64
- Cybervision 64/3D

o Audio I/O
- Amiga builtin
- Melody Mpeg-audio layer 2 board
- Repulse audio board

o Ethernet controllers
- A2065 Ethernet
- Hydra Ethernet
- ASDG Ethernet
- A4066 Ethernet
- Ariadne Ethernet
- Ariadne II Ethernet
- Quicknet Ethernet
- X-surf Ethernet port

o ARCnet controllers
- A2060 ARCnet

o Most SCSI tape drives, including Archive Viper, Cipher SCSI-2
ST150

o SCSI-2 scanners behaving as SCSI-2 scanner devices, HP Scanjet
II, Mustek SCSI scanner. SCSI scanner support is machine inde-
pendent, so it should work, but hasn't been tested yet on most
Amiga configurations. There are reports that the Mustek and HP
ScanJet hang if accessed from the A3000. This might apply to
other 33C93-Adapters, too.

o Most SCSI CD-ROM drives

o Serial/Parallel cards
- HyperCom 3Z, HyperCom 4, HyperCom 3+ and 4+
- MultiFaceCard II and III
- A2232 (normal and clockdoubled)
- IOBlix Zorro-Bus

o Amiga floppy drives with Amiga (880/1760kB) and IBM
(720/1440kB) encoding. Our floppy driver doesn't notice when
mounted floppies are write-protected at the moment. Your flop-
py will stay unchanged, but you might not notice that you
didn't write anything due to the buffer cache. Also note that
HD floppy drives only get detected as such if a HD floppy is
inserted at boot time.

o Amiga parallel port

o Amiga serial port

o Amiga mouse

o DraCo serial port, including serial mouse

o DraCo parallel printer port

o Real-time clocks
- A2000, A3000, A4000 builtin (r/w)
- DraCo builtin (r/o)

If its not on the above lists, there is no support for it in this re-
lease. Especially (but this is an incomplete list), there are no drivers
for: Blizzard III SCSI option, Ferret SCSI, Oktagon SCSI.

Getting the NetBSD System on to Useful Media

Installation is supported from several media types, including:

o AmigaDOS
o CD-ROM
o MS-DOS floppy
o FTP
o Remote NFS partition
o Tape
o Existing NetBSD partitions, if performing an upgrade

The steps necessary to prepare the distribution sets for installation de-
pend upon which installation medium you choose. The steps for the vari-
ous media are outlined below.

AmigaDOS partition
To install NetBSD from an AmigaDOS partition, you need to
get the NetBSD distribution sets you wish to install on
your system on to an AmigaDOS partition. All of the
set_name.xx pieces can be placed in a single directory in-
stead of separate ones for each distribution set. This
will also simplify the installation work later on.

Note where you place the files as you will need this lat-
er.

Once you have done this, you can proceed to the next step
in the installation process, preparing your hard disk.

CD-ROM To install NetBSD from a CD-ROM drive, make sure it is a
SCSI CD-ROM on a SCSI bus currently supported by NetBSD
(refer to the supported hardware list) or an ATAPI cd-rom
connected to the A1200 or A4000 internal IDE connector.
If it is a SCSI CD-ROM on a non-supported SCSI bus like
Blizzard-3 SCSI or Apollo SCSI you must first copy the
distribution sets to an AmigaDOS partition as described
above.

If your SCSI CD-ROM is connected to a supported SCSI host
adapter, or it is an ATAPI cd-rom connected to the
A1200/A4000 internal IDE connector, simply put the CD into
the drive before installation.

Find out where the distribution set files are on the CD-
ROM.

Proceed to the instruction on installation.

MS-DOS floppy Count the number of set_name.xx files that make up the
distribution sets you want to install or upgrade. You
will need one sixth that number of 1.44 MB floppies.

Format all of the floppies with MS-DOS. Do not make any
of them bootable MS-DOS floppies, i.e. don't use format /s
to format them. (If the floppies are bootable, then the
MS-DOS system files that make them bootable will take up
some space, and you won't be able to fit the distribution
set parts on the disks.) If you're using floppies that
are formatted for MS-DOS by their manufacturers, they
probably aren't bootable, and you can use them out of the
box.

Place all of the set_name.xx files on the MS-DOS disks.

Once you have the files on MS-DOS disks, you can proceed
to the next step in the installation or upgrade process.
If you're installing NetBSD from scratch, go to the sec-
tion on preparing your hard disk, below. If you're up-
grading an existing installation, go directly to the sec-
tion on upgrading.

FTP The preparations for this installation/upgrade method are
easy; all you need to do is make sure that there's an FTP
site from which you can retrieve the NetBSD distribution
when you're about to install or upgrade. You need to know
the numeric IP address of that site, and, if it's not on a
network directly connected to the machine on which you're
installing or upgrading NetBSD, you need to know the nu-
meric IP address of the router closest to the NetBSD ma-
chine. Finally, you need to know the numeric IP address
of the NetBSD machine itself. If you don't have access to
a functioning nameserver during installation, the IP ad-
dress of ftp.netbsd.org is 204.152.184.75 (as of June,
2002).

Once you have this information, you can proceed to the
next step in the installation or upgrade process. If
you're installing NetBSD from scratch, go to the section
on preparing your hard disk, below. If you're upgrading
an existing installation, go directly to the section on
upgrading.

Note: This method of installation is recommended only for
those already familiar with using BSD network con-
figuration and management commands. If you aren't,
this documentation should help, but is not intended
to be all-encompassing.

NFS Place the NetBSD distribution sets you wish to install in-
to a directory on an NFS server, and make that directory
mountable by the machine on which you are installing or
upgrading NetBSD. This will probably require modifying
the /etc/exports file on of the NFS server and resetting
its mount daemon (mountd). (Both of these actions will
probably require superuser privileges on the server.)

You need to know the numeric IP address of the NFS server,
and, if the server is not on a network directly connected
to the machine on which you're installing or upgrading
NetBSD, you need to know the numeric IP address of the
router closest to the NetBSD machine. Finally, you need
to know the numeric IP address of the NetBSD machine it-
self.

Once the NFS server is set up properly and you have the
information mentioned above, you can proceed to the next
step in the installation or upgrade process. If you're
installing NetBSD from scratch, go to the section on
preparing your hard disk, below. If you're upgrading an
existing installation, go directly to the section on up-
grading.

Note: This method of installation is recommended only for
those already familiar with using BSD network con-
figuration and management commands. If you aren't,
this documentation should help, but is not intended
to be all-encompassing.

Tape To install NetBSD from a tape, you need to make a tape
that contains the distribution set files, in `tar' format.

If you're making the tape on a UNIX-like system, the easi-
est way to do so is probably something like:

# tar -cf tape_device dist_directories

where tape_device is the name of the tape device that de-
scribes the tape drive you're using; possibly /dev/rst0,
or something similar, but it will vary from system to sys-
tem. (If you can't figure it out, ask your system admin-
istrator.) In the above example, dist_directories are the
distribution sets' directories, for the distribution sets
you wish to place on the tape. For instance, to put the
misc, base, and etc distributions on tape (in order to do
the absolute minimum installation to a new disk), you
would do the following:

# cd .../NetBSD-1.6
# cd amiga/binary
# tar -cf tape_device misc etc kern

Note: You still need to fill in tape_device in the
example.

Once you have the files on the tape, you can proceed to
the next step in the installation or upgrade process. If
you're installing NetBSD from scratch, go to the section
on preparing your hard disk, below. If you're upgrading
an existing installation, go directly to the section on
upgrading.

Upgrade If you are upgrading NetBSD, you also have the option of
installing NetBSD by putting the new distribution sets
somewhere in your existing file system, and using them
from there. To do that, you must do the following:

Place the distribution sets you wish to upgrade somewhere
in your current file system tree. Please note that the
/dev on the floppy used for upgrades only knows about wd0,
wd1, sd0, sd1, and sd2. If you have more than two IDE
drives or more than three SCSI drives, you should take
care not to place the sets on the high-numbered drives.

At a bare minimum, you must upgrade the base and kern bi-
nary distributions, and so must put the base and kern sets
somewhere in your file system. If you wish, you can do
the other sets, as well, but you should not upgrade the
etc distribution; it contains contains system configura-
tion files that you should review and update by hand.

Once you have done this, you can proceed to the next step
in the upgrade process, actually upgrading your system.

Preparing your System for NetBSD installation

You will need an AmigaDOS hard drive prep tool to prepare your hard
drives for use with NetBSD/amiga. HDToolBox is provided with the system
software and on floppy installation disks since Release 2.0 of AmigaDOS,
so we will provide instructions for its use.

Note that NetBSD can't currently be installed on disks with a sector size
other than 512 bytes (e.g., ``640 MB'' 90mm M-O media). You can, howev-
er, mount ADOSFS partitions on such M-O's.

Preparing your hard disk with HDToolBox

A full explanation of HDToolBox can be found with your AmigaDOS manuals
and is beyond the scope of this document.

The first time you partition a drive, you need to set its drive type so
that you have working geometry parameters. To do this you enter the
``Change drive type'' menu, and either use ``read parameters from drive''
or set them manually.

Note you will be modifying your HD's. If you mess something up here you
could lose everything on all the drives that you configure. It is there-
fore advised that you:

1. Write down your current configurations. Do this by examining
each partition on the drive and the drives parameters (from
Change drive type.)

2. Back up the partitions you are keeping.

What you need to do is partition your drives; creating at least root,
swap and /usr partitions and possibly at least one more for /usr/local if
you have the space.

This should be done as the HDToolBox manual describes. One thing to note
is that if you are not using a Commodore controller you will need to
specify the device your SCSI controller uses, e.g. if you have a Warp
Engine you would:

From cli
hdtoolbox warpdrive.device

From wb Set the tooltype

SCSI_DEVICE_NAME=warpdrive.device

The important things you need to do above and beyond normal partitioning
includes (from Partition Drive section):

1. Marking all NetBSD partitions as non-bootable, with two exceptions:
the root partition (/), if you want to boot NetBSD directly, or the
swap partition, if you want to boot the installation miniroot di-
rectly.

2. Changing the file system parameters of the partitions to NetBSD
ones. This must be done from the partitioning section and
``Advanced options'' must be enabled.

To make the needed changes:

1. Click the ``Adv. Options'' button
2. Click the ``Change file system'' button
3. Choose ``Custom File System''
4. Turn off ``Automount'' if on.
5. Set the dostype to one of these three choices:

root partition : 0x4e425207 (NBR\007)
swap partition : 0x4e425301 (NBS\001)
other partitions: 0x4e425507 (NBU\007)

Here `other' refers to other partitions you will format for
reading and writing under NetBSD (e.g. /usr)

Make sure you press RETURN to enter this value as some ver-
sions of HDToolBox will forget your entry if you don't.
6. Turn custom boot code off
7. Set Reserved Blocks start and end to 0.
8. Click Ok.

On the root (/) (and, for installation, swap) partition, set instead
this:

1. Turn custom boot code on
2. Set Reserved Blocks start and end to 0.
3. Set Number of Custom Boot Blocks to 16.
4. Set Automount This Partition on
5. Click Ok.

Mask and maxtransfer are not used with NetBSD.

Caveat: The swap (for installation) and the root partition (if you plan
to use the bootblocks) must be within the first 4 gigabytes of
the disk! The reason for the former is that xstreamtodev uses
trackdisk.device compatible I/O-calls, the reason for the latter
is that the bootblock gets a 32bit partition offset from the op-
erating system.

Once this is done NetBSD/amiga will be able to recognize your disks and
which partitions it should use.

Transferring the miniroot file system

The NetBSD/amiga installation or upgrade now uses a miniroot file system
which is installed on the partition used by NetBSD for swapping. This
removes the requirement of using a floppy disk for the file system used
by the installation or upgrade process. It also allows more utilities to
be present on the file system than would be available when using an 880
KB floppy disk.

Once the hard disk has been prepared for NetBSD, the miniroot file system
(miniroot.fs) is transferred to the swap partition configured during the
hard disk prep (or the existing swap partition in the case of an up-
grade). The xstreamtodev utility provided in the amiga/installation/misc
directory can be used on AmigaDOS to transfer the file system for either
a new installation or an upgrade. The file system can also be trans-
ferred on an existing NetBSD system for an update by using dd. This
should only be done after booting NetBSD into single-user state. It may
also be possible to shutdown to single-user, providing that the single-
user state processes are not using the swap partition.

On AmigaDOS, the command:

xstreamtodev --input=miniroot.fs --rdb-name=<swap partition>

where <swap partition> is the name you gave to the NetBSD partition to be
used for swapping. If xstreamtodev is unable to determine the SCSI driv-
er device name or the unit number of the specified partition, you may al-
so need to include the option

--device=<driver.name>

and/or

--unit=<SCSI unit number>

To transfer the miniroot using NetBSD, you should be booted up in single
user state on the current NetBSD system, or use the shutdown now command
to shutdown to single-user state. Then copy the miniroot using dd:

dd if=miniroot.fs of=/dev/rsd0b

where /dev/rsd0b should be the device path of the swap partition your
system is configured to use. Once the file is copied, reboot back to
AmigaDOS to boot the upgrade kernel.

Caveat: Once you have started installation, if you abort it and want to
retry you must reinstall the miniroot.fs on the swap partition.

Installing the NetBSD System

Installing NetBSD is a relatively complex process, but, if you have this
document in hand and are careful to read and remember the information
which is presented to you by the install program, it shouldn't be too
much trouble.

Before you begin, you must have already prepared your hard disk as de-
tailed in the section on preparing your system for install.

The following is a walk-through of the steps necessary to get NetBSD in-
stalled on your hard disk. If you wish to stop the installation, you may
press CONTROL-C at any prompt, but if you do, you'll have to begin again
from scratch.

Transfer the miniroot file system onto the hard disk partition used by
NetBSD for swapping, as described in the "Preparing your System for NetB-
SD Installation" section above.

Booting

NetBSD, with boot blocks installed

[This description is for V40 (OS 3.1) ROMs. For older ROMs, there might
be small differences. Check your AmigaDOS documentation to learn about
the exact procedure.] Using bootblocks may not work on some systems, and
may require a mountable file system on others.

Reboot your machine, holding down both mouse buttons if you have a 2-but-
ton mouse, the outer mouse buttons if you have a 3-button mouse. On the
DraCo, press the left mouse button instead, when the boot screen prompts
you for it.

From the boot menu, select Boot Options. Select the swap partition with
the miniroot, and then ok. Select Boot now. The machine will boot the
bootblock, which will prompt your for a command line. You have a few
seconds time to change the default. Entering an empty line will accept
the default.

The bootblock uses command lines of the form:
file [options]
where file is the kernel file name on the partition where the boot block
is on, and [options] may contain the following:

If you have an AGA machine, and your monitor will handle the dblNTSC
mode, you may include the -A option to enable the dblNTSC display mode.

If your machine has a fragmented physical memory space, as, e.g., DraCo
machines, you should add the -n2 option to enable the use of all memory
segments.

Once your kernel boots

You should see the screen clear and some information about your system as
the kernel configures the hardware. Note which hard disk device(s) are
configured (sd0, sd1, etc.) Then you will be prompted for a root device.
At this time type sd0b, where sd0 is the device which contains the swap
partition you created during the hard disk preparation. When prompted
for a dump device, answer `none' for the install (normally, you would
tell it one of the swap devices). When prompted for the root file system
type, confirm `generic', which will auto-detect it.

If the system should hang after entering the root device, try again with

netbsd -I ff -b

This disables synchronous transfer on all SCSI devices on the first bus.

The system should continue to boot. For now ignore ``WARNING'' messages
about bad dates in clocks, and a warning about /etc/rc not existing.
Eventually you will be be asked to enter the pathname of the shell, just
press RETURN. After a short while, you will be asked to select the type
of your keyboard. After you have entered a valid response here, the sys-
tem asks you if you want to install or upgrade your system. Since you
are reading the install section, `i' would be the proper response here...

The installer starts with a nice welcome messages. Read this message
carefully, it also informs you of the risks involved in continuing! If
you still want to go on, type `y'. The installer now continues by trying
to figure out your disk configuration. When it is done, you will be
prompted to select a root device from the list of disks it has found.

You should know at this point that the disks are not numbered according
to their SCSI-ID! The NetBSD kernel numbers the SCSI drives (and other
devices on the SCSI bus) sequentially as it finds them. The drive with
the lowest SCSI-ID will be called sd0, the next one sd1, etc. Also, any
ATAPI disk drives (e.g. ZIP) will be configured as ``SCSI'' drives, too,
and will be configured before any `real' SCSI drives if connected to the
Amiga internal port on A4000/A1200 (if any are present). Real IDE drives
will be configured as wd0, wd1, etc.

The installer will offer you to look at the NetBSD disk label of the
disks at this point. You should do this, to find out what partition let-
ters the NetBSD kernel assigned to the partitions you created, and as a
check whether the disk number you are going to use is right.

you are now at the point of no return. If you confirm that you want to
install NetBSD, your hard drive will be modified, and perhaps its con-
tents scrambled at the whim of the install program. Type Control-C now
if you don't want this.

At this time, you will need to tell the installer which partition will be
associated with the different file systems. Normally, you'll want to add
a partition for /usr, at least.

Caveat: Do not use the rsdNc or sdNc partitions for anything! They are
for access to the whole disk only and do not correspond to any
Amiga partition!

The install program will now make the file systems you specified. There
should be only one error per file system in this section of the installa-
tion. It will look like this:

newfs: ioctl (WDINFO): Invalid argument
newfs: /dev/rsd0a: can't rewrite disk label

If there are any others, restart from the beginning of the installation
process. This error is ok as the Amiga does not write disklabels cur-
rently. You should expect this error whenever using newfs.

The install will now ask you want to configure any network information.
It ill ask for the machine's host name, domain name, and other network
configuration information.

Since the network configuration might have lead to additional (nfs) file
system entries, you get another chance to modify your fstab.

You are finally at the point where some real data will be put on your
freshly made file systems. Select the device type you wish to install
from and off you go....

Some notes:

o If you want to install from tape, please read the section about
how to create such a tape.

o Some tapes (e.g. Archive Viper 150) refuse to operate with the
default tape density (nrst0). Try nrst0h, nrst0m, or nrst0l
instead.

o Install at least the base and etc sets.

o If you have to specify a path relative to the mount-point and
you need the mount-point itself, use `.'.

Next you will be asked to specify the timezone. Just select the timezone
you are in. The installer will make the correct setup on your root file
system (/). After the timezone-link is installed, the installer will
proceed by creating the device nodes on your root file system under /dev.

Be patient, this will take a while...

Next, the installer will copy your keymap settings to the new system.
After this, it will copy the kernel from the installation miniroot to the
newly installed / upgraded system. If the installed system already has a
kernel, it will ask you for confirmation.

kern.tgz distribution set, this is an old kernel, and you should answer
"y" to install a working (although restricted) INSTALL kernel.

If you did install the kern.tgz kernel, you normally should answer "n".

Finally, the installer ask you if you want to install the bootblock code
on your root disk. This is a matter of personal choice and can also be
done from a running NetBSD system. See the installboot(8) manual page
about how to do this.

Once the installer is done, halt the system with the halt command (wait
for halted to be displayed) and reboot. Then again boot NetBSD this time
selecting the root partition (/) from the boot menu, and tell it to boot

netbsd -s

You need to do your final tweaks now. First mount your file systems like
so:

mount -av

Your system is now complete but not completely configured; you should ad-
just the /etc/sendmail.cf file as necessary to suit your site. You
should also examine and adjust the settings in /etc/rc.conf. You can use
vi(1) or ed(1) to edit the files. If you installed the man pages you can
type man vi or man ed for instructions on how to use these somewhat non-
intuitive editors.

Once you are done with the rest of configuration unmount your file sys-
tems and halt your system, then reboot:

# cd /
# umount -av
# halt

Finally you can now boot your system and it will be completely function-
al:

netbsd

When it boots off of the hard drive, you will have a complete NetBSD sys-
tem! Congratulations! (You really deserve them!!!)

Post installation steps

Once you've got the operating system running, there are a few things you
need to do in order to bring the system into a properly configured state,
with the most important ones described below.

1. Configuring /etc/rc.conf

If you or the installation software haven't done any configuration
of /etc/rc.conf (sysinst usually will), the system will drop you in-
to single user mode on first reboot with the message

/etc/rc.conf is not configured. Multiuser boot aborted.

and with the root file system (/) mounted read-only. When the sys-
tem asks you to choose a shell, simply press RETURN to get to a
/bin/sh prompt. If you are asked for a terminal type, respond with
vt220 (or whatever is appropriate for your terminal type) and press
RETURN. You may need to type one of the following commands to get
your delete key to work properly, depending on your keyboard:
# stty erase '^h'
# stty erase '^?'
At this point, you need to configure at least one file in the /etc
directory. You will need to mount your root file system read/write
with:
# /sbin/mount -u -w /
Change to the /etc directory and take a look at the /etc/rc.conf
file. Modify it to your tastes, making sure that you set
rc_configured=YES so that your changes will be enabled and a multi-
user boot can proceed. Default values for the various programs can
be found in /etc/defaults/rc.conf, where some in-line documentation
may be found. More complete documentation can be found in
rc.conf(5).

If your

[annoynimous]

Люди добрые у меня проблемма. скачал инсталятор Unix System V. Хочеться проинсталлировать по емуль WinUAE, но никак не получаеться. Кто нибусь сталкивался с этой проблеммой? Если решние вообще существует пожалуйста поделитесь опытом. Заранее благодарен.

Расслабься... униху надо ММУ, а в винуае... ну короче понял, да? =)))

[annoynimous]

Я тут как то лазил по сети и наткнулся на UNIX на амиге,далее текстовик для каких машин предназначена и т.п,кому интерестно.

Офонарел столько байды сюда постить? =) Тебя вообще учили, что можно и ссылку дать? $)

[Drop Gloom]

насчет NetBSD у меня есть диск Если кому надо могу подсуетится
Правдо там инсталяция через задницу