Aros Install Manual Version 0.40a

q0O!
|q:co||oc|oq oquo|

2 - AROS INSTALLATION MANUAL

AROS PUBL!C L!CENSE (APL)

You may obtain a copy of the License at
http:ffwww.aros.orgflicense.html

D!SCLA!NER OF WARRANTY.

COvERED CODE !S PROv!DED UNDER TH!S L!CENSE ON AN AS !S" BAS!S,
W!THOUT WARRANTY OF ANY K!ND, E!THER EXPRESSED OR !NPL!ED, !NCLUD!NG,
W!THOUT L!N!TAT!ON, WARRANT!ES THAT THE COvERED CODE !S FREE OF DEFECTS,
NERCHANTABLE, F!T FOR A PART!CULAR PURPOSE OR NON-!NFR!NG!NG. THE ENT!RE
R!SK AS TO THE QUAL!TY AND PERFORNANCE OF THE COvERED CODE !S W!TH YOU.
SHOULD ANY COvERED CODE PROvE DEFECT!vE !N ANY RESPECT, YOU (NOT THE
!N!T!AL DEvELOPER OR ANY OTHER CONTR!BUTOR) ASSUNE THE COST OF ANY
NECESSARY SERv!C!NG, REPA!R OR CORRECT!ON. TH!S D!SCLA!NER OF WARRANTY
CONST!TUTES AN ESSENT!AL PART OF TH!S L!CENSE. NO USE OF ANY COvERED CODE
!S AUTHOR!ZED HEREUNDER EXCEPT UNDER TH!S D!SCLA!NER.

L!N!TAT!ON OF L!AB!L!TY.

UNDER NO C!RCUNSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT
(!NCLUD!NG NEGL!GENCE), CONTRACT, OR OTHERW!SE, SHALL YOU, THE !N!T!AL
DEvELOPER, ANY OTHER CONTR!BUTOR, OR ANY D!STR!BUTOR OF COvERED CODE,
OR ANY SUPPL!ER OF ANY OF SUCH PART!ES, BE L!ABLE TO ANY PERSON FOR ANY
!ND!RECT, SPEC!AL, !NC!DENTAL, OR CONSEQUENT!AL DANAGES OF ANY CHARACTER
!NCLUD!NG, W!THOUT L!N!TAT!ON, DANAGES FOR LOSS OF GOODW!LL, WORK
STOPPAGE, CONPUTER FA!LURE OR NALFUNCT!ON, OR ANY AND ALL OTHER
CONNERC!AL DANAGES OR LOSSES, EvEN !F SUCH PARTY SHALL HAvE BEEN
!NFORNED OF THE POSS!B!L!TY OF SUCH DANAGES. TH!S L!N!TAT!ON OF L!AB!L!TY
SHALL NOT APPLY TO L!AB!L!TY FOR DEATH OR PERSONAL !NJURY RESULT!NG FRON
SUCH PARTY'S NEGL!GENCE TO THE EXTENT APPL!CABLE LAW PROH!B!TS SUCH
L!N!TAT!ON. SONE JUR!SD!CT!ONS DO NOT ALLOW THE EXCLUS!ON OR L!N!TAT!ON
OF !NC!DENTAL OR CONSEQUENT!AL DANAGES, SO TH!S EXCLUS!ON AND L!N!TAT!ON
NAY NOT APPLY TO YOU.

COPYR!GHT AND TRADENARKS.
Copyright 1995-2007, The AROS Development Team. All rights reserved.
Amiga is a trademark of Amiga !nc. All other trademarks belong to their respective
owners.
The AROS Kitty mascot is 2003 by Eric Schwartz
The image used in the cover is 2005 by Damir Sijakovic.

This manual was produced using a variety of resources and documentation available in
www.aros.org and other AROS resource sites by Joao Ralha and Peter Hutchison.
Original documentation by Stefan Rieken, Natt Parsons, Adam Chodorowski, Neil
Cafferkey, Sergey Nineychev

AROS INSTALLATION MANUAL - 3

TABLE OF CONTENTS

WELCOME...........................................................................................................5
DOCUMENTATION CONVENTIONS............................................................................5
OTHER USEFUL OR REFERENCE DOCUMENTATION........................................................6
INTRODUCTION............................................................................. 7
AVAILABILITY .....................................................................................................7
DISTRIBUTION....................................................................................................7
SUPPORT............................................................................................................7
WARNING...........................................................................................................S
CHAPTER 1: FIRST STEPS.............................................................. 9
AROS REQUIREMENTS..........................................................................................9
AROS MEDIA......................................................................................................9
CDRON ..............................................................................................................9
Floppy .............................................................................................................. 10
CHAPTER 2: INSTALLATION ........................................................ 11
IMPORTANT ......................................................................................................11
GETTING READY.................................................................................................11
!nstalling AROS Only ......................................................................................... 11
!nstalling AROS along with Windows(R)fDOS(R) ................................................. 11
!nstalling AROS along with LinuxfBSD .................... Errol Marcador no definido.
!nstalling AROS along with other systems ........................................................... 13
AUTOMATIC INSTALLATION..................................................................................13
MANUAL INSTALL...............................................................................................17
Partitioning....................................................................................................... 18
Formatting........................................................................................................ 20
Copying the system........................................................................................... 21
!nstalling the bootloader.................................................................................... 23
Preparing to boot .............................................................................................. 23
AROSJI3S6-LINUX AND AROSJI3S6-FREEBSD HOSTED INSTALL ...........................23
APPENDIX I - FILE SYSTEMS ADDITIONAL INFO....................... 26
WHAT'S A FILE SYSTEM.......................................................................................26
AROS NATIVE FILE SYSTEMS ...............................................................................26
(Amiga) Old File System.................................................................................... 26
Fast File System................................................................................................ 27
Smart File System............................................................................................. 28
!SO 9660.......................................................................................................... 30

Illustration table

HOW TO USE THIS MANUAL

Welcome

This is manual is meant to get people used to AROS. !t is for everybody
interested in AROS, as it tries to provide information on AROS in different
levels of expertise. We'll try to cover everything in depth, but in such a
way that you don't need to learn what you don't want to learn.

!t tries to cover multiple platform usage, with the exception of AFA (AROS
for Amiga) although many issues covered here should apply.

First chapters on this manual are for you to get the hangs on the W!NP
usage of the AROS, they cover most basic and essential aspects of daily
usage of an operating system.
Later chapters are intended mostly for expert use and consult purpose.

!f you're familiar with Amiga and AmigaDOS itself, most of the subject
covered here should not be novelty to you, but there's a lot of hardware
and software specific subjects that are dealt here that might be of use to
you.

Documentation Conventions

The following conventions are used through out this manual:

KEYWORDS Keywords are displayed in all uppercase letters, however,
the arguments are not case sensitive (unless stated
otherwise).
<n> Angle brackets enclose variable information that the user
should address.
Courier
Text appearing in Courier font (black colour) represents
information displayed on AROS screen
Courier
Text appearing in Courier font (blue colour) represents
information displayed on host OS screen
Key1+Key2 Key combinations displayed with a + (plus) sign
connecting them indicate that pressing the keys
simultaneously for a giving action or procedure.

Notice the side of this page it has some image with different purposes.
The purposes are illustrated and described on that page.

Also on the side of the page might be the !con program that the excerpt
near it refers to, basically it acts as quick reference.

Did you know.
This image regards
some more curious
aspect of AROS itself
or related subject.

Warning:
This kind of image is
intended to get your
attention regarding
some procedure or
behaviour which might
require caution from
your part.

NOTE:
This image regards
something that you
should know in order
to perform an
operation on the best
possible manner.

ExampleJTutorial
This underlines an
example of an
integrated or complex
operation performed
under AROS.

Hardware related:
!t pinpoints some
important points
regarding hardware
support, behaviour or
configuration.

Other useful or reference documentation

You should also read the following manuals:
AROS User Nanual
AROS Shell Nanual

Also it's recommended that you read other more actively maintained
documentation, which is kept in http:ffwww.aros.orgf.

INTRODUCTION

AROS has a command line interface, the 'Shell'. You can start it with menu
Wanderer>Shell. A window with the path of the current AROS window will
be opened. The prompt normally shows the number of the Shell and the
current path.

Availability
AROS is currently under heavy development. The result is that you have
to choose between stability and features. There are two types of binary
packages possible: snapshots and nightly builds.

Currently, there's no snapshots available, because the ones existed before
are too obsolete to reflect the current status. So the users are encouraged
to download the nightly builds instead.

Nightly builds are done, as the name implies, automatically every night
directly from the Subversion tree and contain the latest code. However,
they have not been tested in any way and can be horribly broken,
extremely buggy and may even destroy your system if you're very
unlucky. Nost of the time though, they work fine.

Please see the download page for more information on nightly builds
available and how to download them - http:ffaros.sourceforge.netf.

Distribution

There's also some pre-installed AROS packages either native or hosted
flavours, this is a list of the current distribution packages and sites:

Name Type Status Location
AROS-NAX Native Discontinued (NfA)

AROS-
Workshop
Native Not maintained http:ffreziztanzia.free.frfArosf

velocity Hosted Discontinued (NfA)

vmwAROS Hosted f
Native
Reg. maintained http:ffwww.vmwaros.orgf

WinAROS Hosted !n progress http:ffamidevcpp.amiga-
world.defWinArosfWinAros012008.exe

Support

Aside from the official AROS web site ( http:ffwww.aros.org), there's the
AROS ARCH!vES web site where you can uploadfdownload all the latest

Did you know that
AmigaOS only
supported hard disk
autoboot from version
1.3 upwards?

Launched in 1985 the
Amiga 1000 sported the
AmigaOS 1.0 which was
by most people simply
referenced as Kickstart
1.0 and workbench 1.0.
But hard disk support was
missing from the initial
release.

With the launch of
Kickstart 1.3 the Amiga
operating system finally
offered a viable option for
hard disk users.

S - AROS INSTALLATION MANUAL
AROS software tool,applications and related files (sort of aminet for
AROS):
http:ffarchives.aros-exec.orgf

There are also files that might be downloaded from Aminet for AROS:
http:ffaminet.netf

You may find that the information in this manual or the supplied on the
AROS is not quite to your satisfaction, so we encourage you to seek
answers to your questions in AROS community.

That way you might contribute to AROS yourself.
The AROS community has two major forums where they usually meet:

AROS-EXEC

http:ffaros-exec.orgf
AROS-WORLD

http:ffwww.arosworld.orgf

Also there's an official !RC channel for AROS, unsurprisingly named #aros,
on the FreeNode network. Please connect to irc.freenode.net, which will
redirect to a server close to you. !t's for discussing everything and
anything related to AROS, including development and how to take over
the world. On rare occasions, if the main channel is very noisy,
development related discussions move to #aros.dev.

Warning

AROS is alpha quality software. This means that it is currently
mostly fun to play with and cool to develop for. !f you came
here because you thought AROS was a finished, complete and
fully usable operating system, you will most likely be
disappointed. AROS isn't there yet, but we're slowly moving in
the right direction.

Warning:

READ ABOUT THE
AROS PUBL!C
L!CENSE (APL) AND
D!SCLA!NER OF
WARRANTY ON
PAGE 2.


CHAPTER 1: FIRST STEPS

AROS requirements

AROSfi386-pc and AROSfX86-6+x Native

You will need an average PC!-based PC (i+86 or Pentium) with PSf2
mouse and PSf2 or AT keyboard, !DE hard disk and CD-RON, (S)vGA
video card and monitor. Also most of available PC-compatible vN (virtual
machine) can be used. QENU, vmvare, Q, Bochs, NS vPC are known to
work. At least 16 NB of RAN and vESA-compliant vGA card is
recommended. There's a generic accelerated drivers (H!DD's) for AT! and
nvidia cards. Also you can add the networking interface card (there's
some supported) to try networking in AROS. !f you're in trouble, please
check the FAQ if it contains any information on your kind of hardware in:
http:ffwww.aros.org

AROSfi386-linux and AROSfi386-freebsd-hosted

To run AROSfi386-linux or AROSfi386-freebsd you will need the following:

- A working FreeBSD 5.x or Linux installation (doesn't really matter
which distribution you run, as long as it's relatively recent).
- A configured and working X server (for example X.Org or XFree86)
for x11.hidd or libsdl installed (for sdl.hidd).

AROS media

The recommended installation media for AROSfi386-pc is CDRON, since
we can fit the whole system onto a single disc (and also all the
contributed software). This also makes the installation easier, since you
don't have to go through hoops transferring the software on several
floppies.

Since nobody currently sells AROS on CDRON (or any other media for that
matter), you will need access to a CD burner to create the installation disk
yourself.

CDROM

Writing
Simply download the !SO image from the download page and burn it to a
CD using your favourite CD burning program. There's a number of
freeware cd burning programs for any system, and we can point Windows

NOTE:
Although AROS can be
installed to the hard
drive, please
remember, that
installer is still in
testing stage.
So it's execution
present some risk.
As the testing goes,
the process will
become much more
stable and robust.
So please note that
you should not use
install on your working
machine, which HD
contains precious data!
We're taking no
responsibility for any
data loss occurred
during the installation.

users to the !nfraRecorder - it's free, !t's small and fast, and it's just Nero-
killing simple.

Booting
The easiest way to boot from the AROS installation CD is if you have a
computer that supports booting from CDRON. !t might require some
fiddling in the B!OS setup to enable booting from CDRON, as it is quite
often disabled by default. Simply insert the CD into the first CDRON drive
and reboot the computer. The boot is fully automatic, and if everything
works you should see a nice screen after a little while.

!f your computer does not support booting directly from CDRON you can
create a boot floppy and use it together with the CDRON. Simply insert
both the boot floppy and the CD into their respective drives and reboot.
AROS will start booting from the floppy, but after the most important
things have been loaded (including the CDRON file system handler) it will
continue booting from the CDRON.

Floppy

!n these days floppies can be found useful only to boot if your PC's B!OS
doesn't support booting from CD or on some really obsolete PC's. But it's
still maintained.

Writing
To create the boot floppy, you will need to download the disk image from
the download page, extract the archive, and write the boot image to a
floppy disk. !f you are using a UN!X-like operating system (such as Linux
or FreeBSD), you can do this with the following command:

> cd AROS-<version>-i386-pc-boot-floppy
> dd if=aros.bin of=/dev/fd0

!f you are using Windows, you will need to get rawrite to write the image
to a floppy. Please see the documentation of rawrite for information on
how to use it. There's also a GU! version called rawwritewin.

Booting
Simply insert the boot floppy into the drive and reboot the computer. The
boot is fully automatic, and if everything works you should see a nice
screen after a while.

CHAPTER 2: INSTALLATION

Important

Well, note that you have been WARNED that HD installation is in testing
stage at the moment and can be dangerous to your data, so make sure
the PC you're using for install does not contain any useful data or have a
full backup. Using a virtual machine is recommended, as it minimises any
possible risk and allows AROS to be used and tested on any working
machine. There are many free vN`s available now, such as virtual PC, Q,
QENU and vNWare, which are known to work with AROS.

Getting ready

First, set up your HD - either real or a virtual drive image - for use. For a
real drive, this may involve plugging it into the machine (always a good
start) and setting it up in the B!OS. For a virtualiser's or emulator's virtual
drive, you probably just need to select an option to create a new drive
image, and set it as one of the virtual PC's boot devices (the CD drive
must be the first boot device during installation of AROS however).

Another step will be cleaning the HD of any existing partitions, to remove
anything that can prevent our partition creation succeeding. !nstalling
AROS along with another OS is possible, but will require more skills and is
not covered here. For the moment, we will learn how to install AROS as
the only system on the HD.

Installing AROS Only
This is the simplest situation - installing AROS alone on the whole disk.
Your disk can be new or with an unneeded data on it. Basically you'll be
wiping your disk to erase existing data on hard drive.

Installing AROS along with Windows{R)JDOS{R)
!nstalling AROS along with Windows must be an easy task (assuming you
use Windows XP). Generally, you'll need to just follow the installer
prompts as shown above to make this working. !nstaller is designed to
detect your Windows installation and put it to GRUB menu automatically.
Check the chapter above about standalone AROS installation to do this. !f
you ever need to restore previous NT loader, you can use F!XNBR
command in recovery console from your Windows installation CD.

There can be problems with some older and newer Windows versions (like
95f98 and vista). For installing over vista you can use steps, similar to the
ones for Linux with GRUB installer. !n some cases Grub can installed and

WARNING:
Although AROS can be
installed to the hard
drive, please
remember, that
installer is still in
testing stage.
So it's execution
presents some risks.
As the testing goes,
the process will
become much more
stable and robust.
So please note that
you should not use
install on your working
machine, which HD
contains precious data!
We're taking no
responsibility for any
data loss occurred
during the installation.

used to boot vista, you'd just need to add a menu entry to your
fbootfgrubfmenu.lst:

title Windows Vista
root (hd0,0)
makeactive
chainloader +1

!f you prefer to use vista bootloader, you can use some programs like
EasyBCD to manage it's behaviour.

!nstalling AROS along with LinuxfBSD
!nstalling AROS along with Linux or BSD systems is almost the same as
the one for Windows. You'd need to create a free space for AROS with
available tools. Then use !nstallAROS to do the partitioning and formatting
the AROS partition and copy system to it (you can use additional WORK
partition if you want to), but it's better to not install the bootloader
(uncheck the corresponding checkbox):

[ | !nstall Bootloader

After the installer has finished copying the files, it will ask you to reboot.
After the reboot you'd need to boot your LinuxfBSD again, to set up the
bootloader. AROS uses patched GRUB bootloader, able to load kernel from
AFFS. But you don't have to use it, if you put AROS kernel to the place,
where your system kernel is (usually fboot) and use a conventional GRUB
from your distribution. Just copy fbootfaros-i386.gz from AROS LiveCD to
fboot. Then put some new lines to the end of your fbootfgrubfmenu.lst
file to enable AROS menu entry:

title AROS VBE 640x480 16bpp
root (hd0,0)
kernel /boot/aros-pc-i386.gz vesa=640x480x16
ATA=32bit,forcedma nofdc
quiet
boot

You can change the kernel's parameters to set the screen resolution. The
'nofdc' option disables the floppy trackdisk device, which is not too useful
these days but can cause troubles in some cases.

!f you happen to use L!LO or any other booloader, this trick won't be that
easy. (is hard to make L!LO booting AROS kernel). You will need to
somehow chainload AROS GRUB and set it to start up a kernel.

After the reboot, you must be able to see AROS entry in GRUB menu and
boot it.

!nstalling AROS along with other systems
There's a lot of another systems out there on the platforms AROS
supports. !F your system uses GRUB bootloader the process must be fairly
similar to the one of Linux. !f not, please remember that all you need for
AROS to boot is just to place it's files on a partition where GRUB can find it
and boot the kernel.

Automatic installation

Currently the installation is meant to be made by means of !nstallAROS
program, which is located in the Tools drawer on your AROS Live CD.
Please launch it by double clicking on its icon. See it's launched up and
showing you the following screen.

Currently there's a bug in Wanderer when discovering new volumes (this
issue seems to be bypassed already) that quits !nstallAROS from
formatting drives. So please enter the Wanderer menu, select Quit and
confirm in the pop up requestor.


Afterwards click the Proceed button in AROS !nstaller window, to get to a
window with installing options.

You'll be presented with following window:

!n this window you're offered several options. These include:
- Device: The device type where you wish to install AROS. Normally
in PC should be ata.device.
- Unit: the device entry in the chain - 0 for a master set hard-drive,
1 for a slave set hard drive.
- Only use free space: Enabling this option will leave other partitions
alone. Useful for multi system booting.
- Wipe disk - CAUT!ON: !t will use all disk space, erasing all existing
partitions and loosing any data on hard drive!
- Use existing AROS partition: !f the user already has AROS partition
set, this will use the them.

We'll be assuming you want the all disk to used to yourself, so check the
Wipe disk" option. !f you're sure the HD has no partitions set you can
also use the first option.
Just click proceed to carry on to the installation options.


You should set all the options except the choose language options" and
the !nstall development software".
Then click on the proceed button.

At this stage if you've set the partition options you'll need to format them.
You can set the drive unit designations: Example DH0 and DH1 (do not
use colons (:) after the names).

!f you set a Work partition, select the Use Work Partition" option.
Also it's good idea to copy extras and developer files to Work - so select
also this option (Unless you've selected not copy theses files before).

!f everything is properly set just select proceed.


Assuming that you've set the !nstall bootloader", the GRUB settings
window will appear. Just click on proceed again.

At this time you'll start the installation. Just select Proceed to start.
!f you're unsure or care to review all your setting this would be a good
time. After hitting Proceed there's no return!

!f all goes well you'll be copying the AROS Core System files soon. The
window presents you the current file copy status.

!f you've selected to copy the extras stuff then a second progress window
will carry on the file copying process.

!f no errors were found, you'll be presented with a final window, telling
that AROS has been installed.

Manual install

As the !nstallAROS tool is useful now, the following information is kind of
deprecated but still can be of some interest, so it's have been kept here in
case the AROS !nstaller program fails.
Officially we do not recommend hard disk installation for inexperienced
users at the moment so this note was written.

1S - AROS INSTALLATION MANUAL
Partitioning

Single partition install
Here we will learn how to install AROS as the only system on PC and being
placed on a single partition. This is the easiest case to install.

This chapter can be found a bit tricky, as the install feature is incomplete.
First, remember a common rule for this process - reboot after any
significant change made to the file system (we will note where it is
needed). Rebooting means closing the HDToolbox window if it's open and
restarting the computer or vN, so it's an hard reset. You can also try a
soft reset by typing reboot followed by ENTER in the CL! window.

First, find a tool on the AROS CD called HDToolBox. !t's located in the
Tools drawer. This is your HD tormenter for a while. When you run it, you
will see a window with a device-type selector. !n this example (here and
further on), we are using a real or virtual !DE hard drive (also known as
an ATA hard drive). So, clicking on the ata.device entry will show
Devices:1 in the left window. So, this is our HD. By clicking on this entry
we will enter the available HD list.

So here we should see our HD listed. !f it`s a virtual HD, we will see
something like QENU Harddisk or the equivalent vNWare one. !f your HD
is real, you should see its name. !f this doesn't happen, you must make
sure you've correctly prepared your HD. Clicking on the HD name will give
us some information:

Size: <Size of HD>
Partition Table: <type of current PT; must be unknown
after cleanup>
Partitions: <count of partitions on HD; must be 0 as
we've just started>

Well, now we must create a new partition table. Here, for a PC we must
create a PC-NBR type of table. To do this, please press the Create Table
button and choose PC-NBR from the list. Click OK.

Then we must write the changes to disk. To do this, click on the HD's
name and press Save Changes. Answer Yes in the confirmation dialog.
Close the HDToolbox window and reboot the system from the Live CD.

After the system boots up, run HDToolbox again. Now, after entering the
ata.device entry we must see the info "Partition table: PC-NBR,
Partitions:0". That's ok; we haven't set no partitions yet. Let's do it now.
Click on the HD's name to go to the partitions list. The list is empty now.
Click on Create Entry button, choose all the space by clicking on

unselected empty space and click OK. Now in the list you should see a
"Partition 0" entry. Choose it by clicking to get this information:

Size: <Partition size. Almost equal to HD size>
Partition table: Unknown <Not created yet>
Partition type: AROS RDB Partition table <That's OK>
Active: No <Not active>
Bootable: No <Not bootable>
Automount: No <Will not mount on system startup>

Here can be some difference - make a partition in RDB table or as usual
PC-NBR partition. RDB (Rigid Disk Block) is the choice of compatibility and
was used in Amiga HDD`s partitioning, and we can use it too. Although,
AROS supports FFS partitions created within a common PC-NBR table, like
an usual PC partitions like FATfNTFSfetc. Second way can be considered
somewhat more modern and more compatible to some new AROS
programs. Let`s consider both.

FFS in RDB Now, click on Create Table button, select RDB table and click
OK. To save changes, go one level up by clicking the Parent button, select
the HD name again and click the Save Changes button. Answer Yes in the
confirmation dialog twice. Exit from HDToolbox and reboot the machine.

FFS in NBR ...to be added

After booting up, run HDToolbox. Now the info for our Partition 0 is the
same except that the partition table is now RDB (or not). This partition
must be set to ACT!vE. To do this, click on the Switches button, select the
Active checkbox and click OK. Now what? Yes, save the changes by going
a level up and clicking the button. Exit and reboot.

Why are we rebooting so much? Well, HDToolbox and system libraries are
still unfinished and quite buggy, so rebooting after every step helps to
reset them to initial state.

After boot up, HDToolbox must show us that Partition 0 has become
active. That's good, now we must create our disk to install AROS on. Go
one level down by clicking on the "Partition 0" entry.
Now click on the Add Entry" button and choose all the empty space. Now
you should see a "DH0" entry there, which is our disk. Clicking on it shows
the following information:

Size: <well...>
Partition Table: Unknown (it's OK)
Partition Type: Fast Filesystem Intl <OK>
Active: No <OK>
Bootable: No <we must switch it to Yes>
Automount: No <we must switch it to Yes>


Now, go 2 levels up to the HD name, click Save Changes, confirm, exit
and reboot. After booting up (pretty boring, isn't it?) we must set switches
to the DH0 drive in HDToolbox.
Go to the DH0" entry and set switches with the relevant button and
checkboxes:
- Bootable: Yes
- Automount: Yes.
Save changes after going 2 levels up again, confirm and reboot.

We're more than half way to success. After booting up and checking all
the settings for DH0, we must see it's OK now. So now we can exit
HDToolbox with no hesitation left. Now it's time for some CL! magic.

Formatting

We must format our created DH0 drive to make it usable. Currently AROS
have a choice of two filesystems - Fast FileSystem (FFS) and Smart
FileSystem (SFS). FFS is known to be somewhat more stable and
compatible to most programs, SFS is more fail-proof and advanced, but
yet have some issues with some programs. Currently we must set it to
FFS, because GRUB boot loader is not supporting SFS (GRUB2 will). Also
please note that you can get problems using some ported software with
SFS (such as gcc).
So now open the CL! window (right click on upper menu and select Shell
from the first Wanderer menu). At the prompt, enter the !nfo command
(type info and press Enter). You should see our DH0 in the list as DH0:
Not a valid DOS disk. Now we will format it with the command:

>format DRIVE=DH0: NAME=AROS FFS INTL
About to format drive DH0:. This will destroy all data
on the drive. Are
you sure ? (y/N)

Enter y, press Enter and wait a second. You should see the string
Formatting...done displayed. !f you got an error, check for all partition
parameters in HDToolbox, as you may be missing something, and repeat
format process.

!f you're experiencing problems with format (such as ERROR messages,
especially when using partitions in RDB), which is unlikely, then you can
try a good old Amiga FORNAT6+ utility:

>extras/aminet/format64 DRIVE DH0: Name AROS FFS INTL

Now the !nfo command should show:

>DH0: <size> <used> <free> <full 0%> <errors> <r/w
state> <FFS> <AROS>

That's it. Time for the pre-installation reboot.

Copying the system

After reboot, you may notice that you can see our AROS HD on the
desktop now, and it's empty. Now we need to fill it with files.

Now after the Drag'n'Drop support developed in AROS the whole system
can be easily copied from AROS Live CD by just dragging files to DH0:
drawer. !t's only left to replace the file dh0:bootfgrubfmenu.lst with
dh0:bootfgrubfmenu_dh.lst.DH0 then.

You can also Run !nstallAROS in the Tools drawer.
You will see the welcome window. There's a Proceed button for you to
click. Next, you will see partition install options window.

Just select the Use existing AROS partitions (on any drive)" option and
select proceed.
Now you'll be presented with actual !nstall options window.


The options must be set as follows:
- Choose Language Options: No. !t's better to do that later
- !nstall AROS Core System: Yes, we need it. We're here to do that
- !nstall Extra Software: Yes. Uncheck only if you want a light installation
- !nstall Development Software: No. This is mostly a placeholder at a
moment
- !nstall Bootloader: Yes, bootloader will not be installed otherwise.
Select Proceed to continue.

Now you should uncheck the Format Partition" option, because you have done
that already.
The rest of the window shows you the possible installation destinations:

- Destination Partition (default:DH0): DH0 - that's correct
- Use 'Work' Partition - uncheck it. We're installing all-on-one
- Use `Work' Partition - Leave it unchecked.
- Copy Extras and Developer Files to Work? - same as above

Now click Proceed. The window showing bootloader options appears.
GRUB, the GRand Unified Bootloader, is to be installed to DH0 and on
which path. Click Proceed again.


Now the window says you're ready to install. Click Proceed once again.
After that, the copying progress bar will appear as files are copied. Wait a
while until the process finishes. After that, you will get the finishing
window. Now your machine will reboot with the same settings as before,
from AROS Live CD.

Installing the bootloader
Alternatively to last step, !f you're using the CL! for copying the system
files (not using installAros) it may interest you to know that GRUB can be
installed from shell with this command:

c:install-i386-pc device ata.device unit 0 PN <pn> grub
dh0:boot/grub kernel dh0:boot/aros-i386.gz

where PN <pn> (or PART!T!ONNUNBER <pn>) is the number of partition
where GRUB bootloader will be installed.

!f you used the installAROS andfor used the manual install as described
earlier this step should not be required.

Preparing to boot
We have just done our first installation alchemy course, and AROS should
be ready now. We must remove the Live CD from the CD drive (or disable
booting from CD in vN) and check it out. Hear the drum roll? ;)

!f something goes wrong, check the whole procedure and check we're you
might've gone wrong.
You can always get more help on AROS community forums.

AROSJi3S6-linux and AROSJi3S6-freebsd Hosted install

Since AROSfi386-linux and AROSfi386-freebsd are hosted flavours of
AROS, installation is simple. Simply get the appropriate archives for your
platform from the download page and extract them where you want them:

> tar -vxjf AROS-<version>-i386-<platform>-system.tar.bz2

!f you downloaded the contrib archive, you may want to extract it too (but
now it's contents are already included in the system archive and AROS
Live CD):

> tar -vxjf AROS-<version>-i386-all-contrib.tar.bz2

Running

After having extracted all files you can launch AROS like this:


> cd AROS
> ./aros


Appendix I - File Systems additional info

What's a File system

!n computing, a file system (often also written as filesystem) is a method
for storing and organizing computer files and the data they contain to
make it easy to find and access them. File systems may use a data
storage device such as a hard disk or CD-RON and involve maintaining the
physical location of the files, they might provide access to data on a file
server by acting as clients for a network protocol (e.g., NFS, SNB, or 9P
clients), or they may be virtual and exist only as an access method for
virtual data (e.g., procfs).

Nore formally, a file system is a set of abstract data types that are
implemented for the storage, hierarchical organization, manipulation,
navigation, access, and retrieval of data.

AROS native file systems

{Amiga) Old File System
On the Amiga, the Old File System was the filesystem for Amiga OS before
the Amiga Fast File System. Even though it used 512-byte blocks, it
reserved the first small portion of each block for metadata, leaving a very
irregular actual data block capacity of only +88 bytes per block. !t wasn't
very suitable for anything except floppy disks, and it was soon replaced.

History
Originally known as Amiga File System, the filesystem itself was very
similar to that of Xerox Alto Filesystem. Development was from 1982 to
1985 as the filesystem of TripOS. !t received the nickname of "Old" when
Fast File System was released with Amiga OS 2.0.

OFS is very good for repairing the filesystem in the event of a problem,
although the so called DiskDoctor provided by Commodore quickly earned
the name DiskDestroyer, because it could not repair No-DOS type
autostart disks provided by third-party software manufacturers as
bootable disks for games.

Characteristics
Amiga uses NFN encodingfdecoding by default when handling floppy
disks. There are 80 cylinders on an Amiga floppy disk. Each cylinder has 2
NFN tracks, one on each side of the disk. Double density (DD) disks have
11 sectors per NFN track, High density (HD) disks have 22 sectors.

The geometry of an Amiga Floppy Disk is as follows:

* DD disks: 512 bytesfsector, 11 sectorftrack, 2 trackfcyl, 80 cylfdisk

* HD disks: 512 bytesfsector, 22 sectorftrack, 2 trackfcyl, 80 cylfdisk

The DD disk has 11 * 2 * 80 = 1760 (0 to 1759) blocks, while the HD disk
has 22 * 2 * 80 = 3520 blocks.

Amiga stores 880 Kb on a DD disk and 1760 Kb on an HD floppy disk.

The standard Amiga filesystem has an internal 32 bit wide offset
parameter (unsigned). !t tells where to start the readfwrite operation. The
biggest size for an Amiga disk is therefore 2'32 = + Gigabyte.

OFS Datablock stores Block Size BS!ZE-2+ bytes (i.e. normally +88 bytes
at most frequently used BS!ZE of 512 bytes), FFS stores BS!ZE bytes (512
bytes per block).

The Rootblock contains information about the disk: its name, its
formatting date, etc. !t also contains information on accessing the
filesfdirectoriesflinks located at the uppermost (root) directory.

The characters 'f' and ':' are forbidden in file and volume names, but
*!@#${'+8_()=-[|{)';",<>.? and accented letters like a are allowed.

The date fields in the root block (and other blocks) are structured in the
form of DAYS, N!NS and T!CKS. The DAYS field contains the number of
days since January 1. 1978. N!NS is the number of minutes that have
passed since midnight and T!CKS are expressed in 1f50s of a second. A
day value of zero is considered illegal by most programs. Since the DAYS
value is stored as a 32-bit number, the all Amiga based filesystems do not
have an inherent Year 2000 problem or Year 2038 problem.

Files are composed of a file header block, which contains information
about the file (size, last access time, data block pointers, etc), and the
data blocks, which contain the actual data. The file header block contains
up to BS!ZEf+-56 data block pointers (which amounts to 72 entries with
the usual 512 byte blocks). !f a file is larger than that, file extension
blocks will be allocated to hold the data block pointers. File extension
blocks are organised in a linked list, which starts in the File header block
('extension' field).

Fast File System
The Amiga Fast File System (FFS) is a file system used on the Amiga
personal computer. The Amiga Old File System (OFS) was too slow to
keep up with hard drives. FFS differs mainly in the removal of redundant
information. Data blocks contain nothing but data, allowing the filesystem
to manage the transfer of large chunks of data directly from the host
adapter to the final destination.

2S - AROS INSTALLATION MANUAL
History
FFS was introduced with version 1.3 of AmigaOS[1| in 1988[2|.

AmigaOS 3.0, designed for the Amiga +000, introduced two new FFS
modes:
- !nternational mode allows FFS to handle filenames with
international characters.
- Directory Cache mode allows the filesystem to access hard disks
more rapidly by creating a cache of directory contents. As any other
directory caching based systems it used a certain amount of disk
space to store the data (This mode isn't support in AROS).

There was a bug in the old AmigaDOS versions when applying the Hash
function to international characters (ASC!! codes > 128). Consequently,
FFS was then created with the 'international mode' (!NTL). Filename
characters can be lowercase and uppercase, but are not case sensitive.

Also the FFS exhibits the same OFS size limit (+Gb). This limit was
changed with AmigaOS 3.5 and 3.9 and now is 2'6+ = + Exabyte.

Nore recently, NorphOS and AmigaOS + have introduced support for a
slightly updated Fast File System 2, or FFS2. FFS2 is a minor update of
FastFileSystem for AmigaOS + and NorphOS. !t implements long filename
support while maintaining backward compatibility with the older
FastFileSystem and OldFileSystem.

All FFS versions store a "map" of the filesystem in a bitmap which is prone
to deletion or corruption if the OS is reset or crashes during a write,
resulting in data loss or invalidation of the filesystem.

Smart File System
The Smart File System (SFS) is a journaling filesystem used on Amiga
computers.
A journaling file system is a file system that logs changes to a journal
(usually a circular log in a specially-allocated area) before actually writing
them to the main file system. Such file systems are less likely to become
corrupted in the event of power failure or system crash.

Common file systems tend to be very large data structures; updating them
to reflect changes to files and directories usually requires many separate
write operations. This introduces a race condition, in which an interruption
(like a power failure or system crash) can leave data structures in an
invalid intermediate state.

Recovery in a non-journaled file system requires a complete walk of its
data structures to find and correct any inconsistencies - The disk validator

necessity in FFS. This can be slow if the file system is large, and there is
little available !fO bandwidth.

A journaled file system maintains a journal of the changes it intends to
make, ahead of time. After a crash, recovery simply involves replaying
changes in the journal until the file system is consistent again. The
changes are thus said to be atomic (or indivisible) in that they either:
- succeed (have succeeded originally or be replayed completely
during recovery), or
- are not replayed at all.

Journaling can have a severe impact on performance because it requires
that all data be written twice. Netadata-only journaling is a compromise
between reliability and performance that stores only changes to file
metadata in the journal. This still ensures that the file system can recover
quickly when next mounted, but leaves an opportunity for data corruption
because unjournaled file data and journaled metadata can fall out of sync.

History
SFS is a free filesystem written in C originally created in 1998 by John
Hendrikx. After the original author left the Amiga scene in 2000, the
sources for SFS were released and its development continued.

Since Nay 2005 the SFS source code is available under the LGPL license.

Characteristics
!t is designed for performance, scalability and integrity. !t uses block sizes
ranging from 512 (29) to 32768 (215) bytes with a maximum partition size
of 128 GB.

Good performance of the filesystem is realized by grouping multiple
directory entries into a single block and by grouping meta data blocks
together into clusters. A bitmap is used to keep track of free space, and
file data is kept track of using extents arranged into a B+ tree structure.

!ntegrity is maintained by keeping a rollback log of all changes made to
metadata over a certain period of time. The log is written to disk first into
free space and then meta data blocks are overwritten directly. Should the
system crash, the next time the filesystem is mounted it will notice the
uncompleted operation and roll it back to the last known consistent state.
For performance reasons, only metadata integrity is ensured. Actual data
in files can still be corrupted if a write operation is terminated half way
through.

One particular interesting feature of SFS is its ability to defragment itself
while the filesystem is in use, even for locked files. The defragmentation
process is almost completely stateless (apart from the location it is
working on), which means it can be stopped and started instantly. During

defragmentation data integrity is ensured of both meta data and normal
data.

ISO 9660
!SO 9660, a standard published by the !nternational Organization for
Standardization (!SO), defines a file system for CD-RON media. !t aims at
supporting different computer operating systems such as Unix, Windows,
Nac OS and AmigaOS so that data may be exchanged.

An extension to !SO 9660, the Joliet format, adds support to allow longer
file names and non-ASC!! character sets.

DvDs may also use the !SO 9660 file system. However, the UDF file
system is more appropriate on DvDs as it has better support for the larger
media and is better suited for modern operating system needs.

!n AROS (as well as AmigaOS) the !SO 9661f2 disk devices supported are
exhibited in information window as Old File System type disks.

Aros Install Manual Version 0.40a

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Aros Install Manual Version 0.40a

Загружено:

Авторское право:

Доступные форматы

q0O!

Вам также может понравиться