home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Amiga GigaPD 3
/
Amiga_GigaPD_v3_3of3.iso
/
netbsd
/
docs
/
faq.ascii
< prev
next >
Wrap
Text File
|
1993-06-25
|
60KB
|
2,443 lines
Amiga-NetBSD-FAQ
11. January 1994
Guenther Grau, et al
2 FAQ-Amiga-NetBSD
Copyright c 1993
Started by Mike Schwartz (mykes@shell.portal.com)
(mykes@irc)
Idea of using Texinfo by Carsten Hammer
(chammer@dave.hrz.uni-bielefeld.de) (chammer@irc)
Working Texinfo, additions and corrections by Guenther
Grau (s_grau@ira.uka.de) (Maeuschen@irc)
Current FAQ author is Guenther Grau (s_grau@ira.uka.de)
(Maeuschen@irc).
NetBSD-Amiga was ported by Markus Wild (mtk@irc)
(mw@eunet.ch)
Copyright (C) 1993, 1994 Guenther Grau
Permission is granted to make and distribute verbatim
copies of this manual provided the copyright notice and this
permission notice are preserved on all copies.
Permission is granted to copy and distribute transla-
tions of this manual into another language, under the above
conditions for modified versions, except that this permis-
sion notice may be stated in a translation approved by Guen-
ther Grau (s_grau@ira.uka.de).
FAQ-Amiga-NetBSD 3
_1. _I_n_t_r_o_d_u_c_t_i_o_n
Welcome to the NetBSD-Amiga-FAQ.
This FAQ was composed to reduce the traffic on the net
and to avoid people asking the same questions repeatedly,
just as any other FAQ. Please write all comments, sugges-
tions, etc. to the current maintainter of the FAQ. This will
help to keep this FAQ up-to-date and useful. Thank you for
reading the FAQ, because that's why I put so many hours of
work into it:-)
It should be clear at this point that we are talking
about the port of NetBSD to the Amiga. Therefore whenever
NetBSD is mentioned, it is only an abbreviation for NetBSD-
Amiga, except stated otherwise.
4 FAQ-Amiga-NetBSD
_2. _G_e_n_e_r_a_l _t_h_i_n_g_s
This chapter contains general information about NetBSD.
_2._1. _T_h_e _n_a_m_e _o_f _t_h_e _g_a_m_e: _W_h_a_t _i_s _N_e_t_B_S_D?
NetBSD is a Unix-like operating system. It is very
portable and runs on very different architektures such as
Amiga, HP, Mac, Sun, PC, ... It is developed by people all
around the world on the Net. Therefore it is called NetBSD.
For a complete description of a Unix-like operating system,
please refer to some books about unix or get any of the
comp.unix.* Newsgroups FAQ.
_2._2. _W_h_o _i_s _w_o_r_k_i_n_g _o_n _t_h_e _p_o_r_t?
NetBSD was ported to the Amiga by mtk, Markus Wild, who
also ported GCC to AmigaDOS and who did the ixemul.library.
Somehow he has an uncanny knack of diving into massive pro-
jects done by other people and making them work well on the
amiga! Once NEtBSD-Amiga was useable, a lot of people joined
in and contributed a lot to the project. I don't want to
list any names, because I am sure I would forget some brave
soul. Maybe I try to set up a complete list later.
FAQ-Amiga-NetBSD 5
_3. _W_h_a_t _d_o _I _n_e_e_d _t_o _r_u_n _N_e_t_B_S_D
This chapter describes the hardware related topics of
NetBSD. It will explain, what kind of hardware you need to
be able to run NetBSD.
_3._1. _W_h_a_t _k_i_n_d _o_f _A_m_i_g_a_s _w_i_l_l _i_t _r_u_n _o_n?
There are three major requirements your system must
fulfill to be able to run NetBSD. You must have an apropri-
ate cpu, enough memory and enough harddiskspace for NetBSD.
_3._1._1. _W_h_i_c_h _c_p_u _i_s _n_e_e_d_e_d?
It depends heavily on the type of cpu your system has,
whether NetBSD runs on your Amiga or if it doesn't. NetBSD,
as any other modern Unix-derivate, too, must have a memory-
management-unit (MMU) to be able to run. This is needed as
all the processes that run under Unix are separated from
each others, so no process can do any harm to any other.
If your system is equipped with one of the following
cpu's you have the possibility to run NetBSD:
68020 with 68851 (MMU)
68030
68040
Note: It is very important that you have the _real_
cpu's, i.e. no EC-version, or whatever. These versions are
missing the MMU-part of the cheap and are therefore cheaper.
It is not possible to simply add a 68851 (MMU) to these
chips. You have to replace your cpu, if possible, or you
have to buy a cpu-board equipped with one of the 'real'
cpu's mentioned above to be able to run NetBSD.
NetBSD is known to run on A500, A2000 and A4000/EC30
equipped with additional processor boards that have one oth
the abouve CPUs. It runs on stock A3000 and A4000/40.
6 FAQ-Amiga-NetBSD
_3._1._2. _H_o_w _m_u_c_h _m_e_m_o_r_y _d_o _I _n_e_e_d?
Theoretically, you only need 2MB of fast RAM and 1MB of
chip. The need for chipmemory is only needed for the
startup, so if someone rewrites the program that loads the
kernel into the memory and starts it, it would be possible
to boot the kernel with 512KB-CHIP-RAM. Currently the kernel
is loaded into the chipmemory and then copied into the larg-
est chunk of fast memory found. Therefore 2MB is the bare
minimun and will not allow you to do anything useful, but
booting. It is possible to run NetBSD, in such a low memory
situation, because it uses a mechanism named Paging. It
writes currently unused parts of programs to the disk, thus
freeing some memory for other parts. Writing to disk is very
slow, compared to the execution of programs in memory, so
the system will be to slow to be useable. So, to have an
actual useable system, you should have at least 4MB of
FAST-RAM, preferably more. When you want to use X-Windows, a
graphical user interface on top of NetBSD, you probably need
about 6MB or even more to do anything useful.
_3._1._3. _H_o_w _m_u_c_h _d_i_s_k_s_p_a_c_e _d_o _I _n_e_e_d?
8MB of hard disk space will theoretically be sufficient
to boot NetBSD, but again a lot more is needed to do any-
thing useful. So, in practice, or to really use NetBSD, you
will need at least 100M of hard disk, and even more is pre-
fered.
You will need about twice your RAM amount just for a
swap partition on your drive, that is where NetBSD writes
the parts of programs which are currently not used to free
up some memory for other programs.
_3._1._4. _W_h_a_t _o_t_h_e_r _h_a_r_d_w_a_r_e _r_e_q_u_i_r_e_m_e_n_t_s _a_r_e _t_h_e_r_e?
As mentioned earlier, there are no other requirements
for speacial hardware. You can use any other device with
NetBSD, provided the device is already supported by NetBSD.
In general it should be possible to support any kind of
hardware, but the need of the technical inforamtion on the
hardware to be supported is sometimes hard to obtain, but it
is even harder to find someone who has the knowledge, the
will and the time to actually write a piece of special
software for NetBSD to support the device, called a device-
driver.
To actually find out, which devices are already sup-
ported, see the file "compatibility-list" that comes with
FAQ-Amiga-NetBSD 7
the documentation from NetBSD.
A tape drive is recommended for NetBSD, as for any
other operating system, too. You should do regularly backups
in order to be able to restore the data you might have
accidentially destroyed. Especially when you are doing
kernel-development, chances are, that you may trash your
harddisk. The system is normally quite stable, so doing
backups is not a must, but you should do it.
A modem is recommended, too, in order to be able to
connect to the internet or at least send some mail to other
NetBSD-users. This will enable you to obtain the latest
updates and discussions on NetBSD.
8 FAQ-Amiga-NetBSD
_4. _W_h_a_t _a_b_o_u_t _b_u_i_l_d_i_n_g _t_h_e _k_e_r_n_e_l _m_y_s_e_l_f?
Theoreticall you have two options here. You can build
the kernel under AmigaOS or under NetBSD itself. In the
beginning of the development, NetBSD was compiled under Ami-
gaOS, of course, but now almost everybody works under NetBSD
itself. It is highly recommended that you build the kernel
under NetBSD, because you save a lot of HD-space on the
Amiga side and, the more important reason, the possibility
that other developers can help you with the problems that
might occur is much higher.
You will need to get the current version of
bsdsyssrc.720.tar.gz file from the ftp site and put it onto
one of the NetBSD-partitions.
You will need at least 7Megs of room on your /usr par-
tition. If you don't have enough room, you can use a soft-
link to put the usr/src/sys subdir on a different partition.
See question "How do I use softlinks" for more information
on softlinks.
The details are in the RECOMPILE text file of what to
change. You also need to edit the Makefile.amiga file and
put correct path to the gcc compiler in it. Change the CPP=
line to read
CPP=/usr/gnu/lib/gcc-lib/netbsdamiga/2.4.5/cpp -traditional
You also need to get a bsd version of the config pro-
gram, which is on the ftp.eunet.ch ftp site. Copy this
config binary into /usr/sbin. Then type:
config AMIGA
cd ../compile/AMIGA
make Good luck. Building stuff like this from other
environments is not that big a deal. You will get com-
pile errors - just use your editor and fix what's
wrong. A good rule to remember is that 100% of the
code has been compiled before and it works when com-
piled :-)
Since kernel version 490 NetBSD is able to boot a new
kernel from NetBSD. just do:
mknod /dev/reboot c 2 20
cp vmunix.* /dev/reboot
Then it should load the kernelimage vmunix.* and
reboot.
FAQ-Amiga-NetBSD 9
_5. _N_e_t_B_S_D - _L_i_n_u_x - _A_m_i_g_a-_U_n_i_x - _M_i_n_i_x
Currently there are four possibilies to run Unix on the
Amiga.
The first one was Amiga-Unix. This is a commercial unix
from Commodore. It is neither sold nor supported any more.
The second unix on the Amiga was Minix from A.S. Tanen-
baum, a very famous operating system professor. It runs on
every Amiga and does not support memory protection and some
other features needed to get the real unix feeling. It is
commercial, too. It's major aim is to be an operating system
to play around with. It was developed for the computer sci-
ence students Tanenbaum held lectures for.
The third available unix on the Amiga was NetBSD. It
gives you almost anything you might want to expect from a
free unix clone. It runs quite stable. NetBSD is being
developed on several platform, which gives it a large back-
ground of supporters. All users will benefit from platform
independent changes made to it. It was designed to be as
portable as possible. Currently there are ports to the
Amiga, Intel-based PCs, HP-300 (680x0)-based, Macs, Sun3,
Sun-Sparcs and some other platforms. NetBSD-Amiga was added
a binary-compatibility-mode for sun3-binaries. Of course,
this means only binary-compatibel with static linked
binaries. This shows some of the possibilities of NetBSD. If
we are going to have the same shared libraries on both
sides, running shared linked binaries will eventually be
possible, too. Markus Wild reports, that he is already able
to run a sun3-compiled emacs on NetBSD. NetBSD-Amiga is
based on the NetBSD-current sources and is updated regu-
larly. Any changes made to the sources will go back to the
NetBSD-current source tree, so that future distributions
contains these changes. A lot of changes made in the 4.4BSD
are already incoorporated into NetBSD, some others are still
to come. NetBSD contains a lot of other fancy features,
other unix-based operating systems are missing, e.g. cpu-
time- or quotas. NetBSD is copyrighted software, but you are
free to use, modify and distribute it. Note that it is NOT
under the GPL (General Public License, the Gnu Cpoyright (-
left)) and the developers of NetBSD want it to keep this
state. Therefore it is not possible to include any software
which is under the GPL into the kernel. NetBSD is available
in source, but anybody is free to take the current sources
and provide them together with his own binaries, i.e. you
don't have to provide the sources of your own work. This
offer the opportunity for software developer to keep the
sources of the programms they sell. This is not possible
under GPL, where you must provide the source.
The forth available unix on the Amiga is Linux. It was
10 FAQ-Amiga-NetBSD
designed to run on Intel-based PCs. However, Hamish Mac-
Donald did a major rewrite of the sources, so that it is now
possible to run Linux on the Amiga. It adopted the NetBSD-
SCSI-driver for the hd's and is now quite useable. It
already contains a floppy-driver, although this is not com-
pletly functional yet. Everybody has to decide by them-
selves, which unix is best for them. For now I can say, that
using NetBSD is the best way to go, as Linux still has some
more nasty bugs in it and is missing a lot of the func-
tionality you might want to use, but this can change in the
future. A criteria for the decision can be that Linux tries
to be Posix compliant, whereas NetBSD tries to act as a
BSD-system, of course. I cannot say anything about the
future development of the two.
FAQ-Amiga-NetBSD 11
_6. _F_r_e_q_u_e_n_t_l_y _A_s_k_e_d _Q_u_e_s_t_i_o_n_s _a_n_d _t_h_e_i_r _a_n_s_w_e_r_s
_6._1. _H_o_w _d_o _I _g_e_t _N_e_t_B_S_D?
The primary distribution site of NetBSD is
ftp.eunet.ch. You can ftp to there and get the all the docs
in /pub/NetBSD/incoming/DOCS. This is were the latest ver-
sions of all the NetBSD-Amiga related docs can be found.
_6._2. _H_o_w _d_o _I _i_n_s_t_a_l_l _i_t?
Get the file "NetBSD.Install.720" and follow its
instructions. See 'How do I get NetBSD' for instructions on
where to find it.
_6._3. _D_o_e_s _N_e_t_B_S_D _s_u_p_p_o_r_t _m_y _d_e_v_i_c_e?
The file "compatibility-list" that comes with the
NetBSD distribution contains all the gathered information on
the devices that work with NetBSD. See 'How do I get NetBSD'
for instructions on where to find it.
_6._4. _I _c_a_n_n_o_t _s_u _t_o _r_o_o_t
If a users should be able to 'su' (switch or substitute
a user) to root, then he must be a member of group wheel.
_6._5. _I _h_a_v_e _p_r_o_b_l_e_m_s _w_i_t_h _m_y _t_a_p_e _d_r_i_v_e.
When NetBSD boots, it reports for some tape drives that
the drive is not supported. Ignore this message. It is
particulary dumb that you get this message for CBM's own
A3070 tape drive.
NetBSD seems to work with everyone's tape drive so far.
Not that many brands have been tested yet. There are two
regularly occuring problems with the tape drives and there
is a workaround for each. Evenutally, we'll get all this
stuff working right.
12 FAQ-Amiga-NetBSD
Note that there have been some bugfixes for tapedrives,
but I don't know exactly, if all the problems below are
already fixed, so I mention them here nevertheless.
_6._5._1. _T_a_p_e_d_r_i_v_e -- _P_r_o_b_l_e_m _1
After I just used btn on the AmigaOS side to write a
tape, I booted bsd and tar reports some error when I try to
read from the tape drive.
Solution:
NetBSD doesn't issue a SCSI reset command to SCSI ID's
4 and 5 - these are assumed to be tape drives, and sending
the reset makes drives like the A3070 make a lot of annoying
reset/rewind noises. The solution to the problem is to
either power cycle your tape drive before or after bsd is
booted. The problem goes away and bsd can then read the
tape. Note that if the tape is rewinding, you will get an
error trying to read from it. Just wait until the tape is
done rewinding and try again.
_6._5._2. _T_a_p_e_d_r_i_v_e -- _P_r_o_b_l_e_m _2
If I write small files to the tape from NetBSD and try
to read them from the AmigaOS side, there doesn't appear to
be anything on the tape. This may occur in the other direc-
tion, too.
Solution:
If you are using tar to make the tapes, add a fairly
big file to the end of the tape. For example, i want to
just put vmunix on tape, so normally, I'd just:
tar cvfp tape: vmunix
What I need to do to workaround the problem is:
tar cvfp tape: vmunix rootfs.gz
And on the bsd side:
tar xvfp /dev/rst0 vmunix
FAQ-Amiga-NetBSD 13
_6._5._3. _G_e_n_e_r_a_l _w_o_r_k_a_r_o_u_n_d _f_o_r _t_a_p_e_d_r_i_v_e _p_r_o_b_l_e_m_s
If you cannot get your tapedrive to get to work with
NetBSD, write a new device driver for your tapedrive, or
wait until someone else does so. As a workaround you can
write a tar-file with tar to an unused partition, boot into
AmigaDOS and user dcp or devtofile and back this up. It is a
kludge, but it works.
_6._6. _W_h_a_t _d_o _I _n_e_e_d _t_o _k_n_o_w _a_b_o_u_t _s_o_f_t_l_i_n_k_s?
A softlink is basically a pointer to a file or sub-
directory that redirects normal unix subdir tree processing
to other places. Let's use some examples to clarify the use
of softlinks.
Above, we talked about building the kernel under netbsd
environment. Well, if you had made only a 50M /usr parti-
tion like I did, there is NOT enough room to untar and build
the bsdsyssrc.tgz (kernel). Using softlinks, you can put
the bsdsyssrc stuff on your /opt partition (where I put
mine) and fake unix into thinking it is in /usr/src/sys.
Here's how to do it:
cd /usr
mkdir src
cd src
ln -s /opt/sys sys
Now do:
ls -laF
and you will see something like:
sys@ -> /opt/sys
Now you can just:
cd /opt
tar xzvfp /dev/rst0
and untar the bsdsyssrc there. It will make a /opt/sys
for you. Now if you:
cd /usr/src/sys
you have really done:
cd /opt/sys
14 FAQ-Amiga-NetBSD
Another use for softlinks. I recommend this, actually.
I put all my amiga (CBM) header files on tape, then
untarred them to /opt/cbm then I made a link:
ln -s /opt/cbm /cbm
Now I can:
cd /cbm
and get to my headers. I also put font files in
/cbm/fonts. For example, /cbm/fonts/topaz.c is the
output of dumpfont (run that under amigaos) to create a
topaz font for kernel compiling. I also have a
/cbm/fonts/mach.c for the kernel_font.c.distrib and a
cedfont.c for a cedfont I made. In the kernel source
tree, I did:
cd /usr/src/sys/arch/amiga/dev
ln -s /cbm/fonts/topaz.c kernel_font.c
And when I build the kernel, it uses topaz.c to make
the font for the console. Slick? :-)
I hope you get the idea now. One thing that took me a
while to get straight is the ORDER of the names on the ln
command line :-) Just remember:
ln -s {ORIGINAL} {LINK}
and alphabetically, ORIGINAL is before LINK :-) (Just
like the cp-command)
_6._7. _I _h_a_v_e _n_o _u_p_t_i_m_e-_c_o_m_m_a_n_d?
Do 'ln -s /usr/bin/w /usr/bin/uptime'
_6._8. _H_o_w _d_o _I _u_p_d_a_t_e _t_h_e _h_e_a_d_e_r _f_i_l_e_s _a_u_t_o_m_a_t_i_c_a_l_l_y ?
Hubert Feyrer writes:
Whenever a new kernel comes out, it's possible for
some kernal-structures to be changed. You can
install the altered headers by hand, but there's a
easier way by using symlinks into the src-tree.
In particular, the files under
/usr/include/machine and /usr/include/sys are
often altered. To replace those files with the one
that came with your latest kernel-sources, simply
link /usr/src/sys/sys to /usr/include/sys and
FAQ-Amiga-NetBSD 15
/usr/src/sys/arch/amiga/include to
/usr/include/machine: cd /usr/include mv sys
sys.old mv include include.old ln -s
/usr/src/sys/sys sys ln -s
/usr/src/sys/arch/amiga/include machine
_6._9. _H_o_w _d_o _I _g_e_t _a /_u_s_r/_l_o_c_a_l?
As netbsd comes configured (i.e. after you install it),
some things either don't work right or are just missing.
There is no /usr/local in the distributed netbsd
distribution. There SHOULD be a /usr/local, so you have to
create it. Use the following:
mkdir -p /usr/local/man/man1
mkdir /usr/local/man/man2
mkdir /usr/local/man/man3
mkdir /usr/local/man/man4
mkdir /usr/local/man/man5
mkdir /usr/local/man/man6
mkdir /usr/local/man/man7
mkdir /usr/local/man/man8
mkdir /usr/local/man/cat1
mkdir /usr/local/man/cat2
mkdir /usr/local/man/cat3
mkdir /usr/local/man/cat4
mkdir /usr/local/man/cat5
mkdir /usr/local/man/cat6
mkdir /usr/local/man/cat7
mkdir /usr/local/man/cat8
mkdir /usr/games
mkdir /usr/local/lib
16 FAQ-Amiga-NetBSD
chmod -r 755 /usr/local
Once you've done this setup, you can install new
packages!
_6._1_0. _W_h_a_t _p_a_c_k_a_g_e_s _c_a_n _I _i_n_s_t_a_l_l _f_o_r _B_S_D _t_o _e_n_h_a_n_c_e _i_t?
Currently, you can install the following software
packages under bsd. The porting job has already been done.
Just get the tar file and the readme and it will give you
instructions. If you want to use more packages, ftp to one
of the NetBSD-current mirrors and get the sources for
whatever is availble there. Most of it should compile right
out of the box, but due to the rapid changes there might be
some incompatibilities.
o+ ados.tar.gz - a start for an amigados emulator for
unix/bsd.
o+ anethack.tar.z - nethack ported to netbsd.
o+ ascreen.tar.z - screen, a multisession program, that
gives you more than one screen with separate shells on
each.
o+ atcsh.tar.z - the tcsh shell ported to NetBSD.
o+ aterm.tar.z - linux's most wonderful term program,
ported to NetBSD.
it works like dnet, sortof - only better. It lets you
have
multiple remote shells, but also lets you run irc
clients
directly on the netbsd machine. It also has ftp and
telnet
clients for it so you can ftp, for example, right
to/from your
netbsd harddisk over the internet. It also has the
ability
to allow anyone else on internet to telnet in to your
netbsd
machine. (irc, ftp, telnet clients not ported yet).
o+ config.tgz - source to config so you can compile it
under netbsd to
build your kernels under netbsd.
FAQ-Amiga-NetBSD 17
o+ grofflibg++bin.tar.gz - gnu roff and libg++. You need
groff to have
man pages formatted, and libg++ to compile c++
programs.
o+ term107.tar.z - unhacked sources to term107 (aterm) so
you can
easily compile it on remote (i.e. not your netbsd)
machine.
o+ manpages.tar.z - man pages for sections 2 and 3 of
/usr/man. Library
and os calls documented.
o+ bffs1.25.lzh - archive of the amiga bffs (berkeley
file system) tools
and filesystem handler. Handler reads your bsd
partitions,
but doesn't write (according to the docs). It
contains
the needed filetodev program for installing netbsd in
the
first place.
o+ diff-2.3.tgz - port of gnu diff (needed for RCS)
o+ rcs-5.6.0.1.tgz - port of RCS (requires diff-2.3.tgz
:-)
o+ perl-4.036.tar.gz - port of perl
o+ X11R5.*.tar.gz - X11R5 package
o+ cat12345678.tar.gz - all man-pages, already formatted.
_6._1_1. _H_o_w _D_o _I _g_e_t _m_a_n _p_a_g_e_s.
The man-pages are currently in the distribution
directory of NetBSD . The are called cat*.tar.gz. Please
get them and install, i.e. gunzip and tar xf, them to the
appropriate directory. Be warned, they take about 1 MB of
diskspace.
18 FAQ-Amiga-NetBSD
_6._1_2.
_H_o_w _c_a_n _I _m_o_d_i_f_y _t_h_e _k_e_r_n_e_l _t_o _w_o_r_k _w_i_t_h _m_y _g_r_a_p_h_i_c _c_a_r_d?
mtk says:
Ok, from my memory, these files need to be changed:
o+ grfvar.h add defines for your board analogue the
others
o+ device.h add manufacturer/product code
o+ autoconfig.c add man/prod to switch statement, and set
to BITMAP type
o+ write grf_XX.c and ite_XX.c, look at the existing
drivers
in general, grf_ should deal with the
framebuffer as such,
and ite_ should care about the
framebuffer in text-mode,
ie. drawing characters, scrolling
lines, etc.
o+ add your board to the dispatch tables in grf.c and
ite.c
o+ add - if necessary - new grf1 entry to conf/AMIGA
o+ add your new files to conf/files.amiga
o+ reconfig the kernel, make, cross fingers, debug ;-)
_6._1_3. _W_h_a_t _a_b_o_u_t _X-_W_i_n_d_o_w_s?
I am very proud to announce that X-Windows DOES run on
NetBSD-Amiga. Things have become accellerated quite a bit
as more people work on the port of any kind of software!
I cite Philippe Brand (PhB@telesys-innov.fr):
Port has been done mainly by Olivier Raoul, my
brother Olivier & friends
(raoul_o@boson.epita.fr). Their internet
connection is broken down for at least one month,
so you can send email to NetBSD list or private to
me and I'll forward them quickly. All machines
should be able to run it, provided you have enough
RAM. As for now standard custom chips are
FAQ-Amiga-NetBSD 19
supported, and they will work on the support for
the Retina card, as soon as they can get hold of
one. X-color will be available with standard
customs chips as they told me.
_6._1_4. _W_h_a_t _a_b_o_u_t _n_e_t_w_o_r_k_i_n_g?
Ethernetsupport is working perfectly. FTP and telnet
work both in client- and server-mode, NFS was only testet as
client with only one filesystem mounted read-only. Also,
NetBSD-Amiga has proofed Internet-compatibility in running a
NNTP-based News-Server for several weeks.
If you don't have a Ethernet-card but want to connect
to a a unix-box, you can do this using SLIP (Serial Line
Internet Protocol) or PPP (Point to Point Protocol) over a
serial line. This way you can use all TCP/IP services to all
hosts on you network without any restrictions.
_6._1_5. _W_h_a_t _a_b_o_u_t _a_c_c_e_s_s_i_n_g _a_d_o_s-_f_i_l_e_s _f_r_o_m _N_e_t_B_S_D?
Niklas Hallqvist, Email: niklas@appli.se is currently
working on a solution for this, but his time is very
limited. So, if you want to have it fast, contact him and
help him or do it on your own.
_6._1_6.
_I_s _t_h_e_r_e _a _d_e_b_u_g_g_e_r _f_o_r _N_e_t_B_S_D. _I_s _t_h_e_r_e _a_n_y? _I_f _s_o, _w_h_e_r_e _i_s _i_t?
Andy Heffernan ahh@netcom.com has ported gdb-4.11 to
NetBSD. It still contains some minor bugs, but it is already
useable.
_6._1_7. _H_o_w _d_o _I _g_e_t /_d_e_v/_r_e_l_o_a_d _a_n_d /_d_e_v/_z_e_r_o _a_n_d /_d_e_v/_p_a_r ?
As root do:
mknod /dev/reboot c 2 20 mknod
/dev/zero c 2 12
mknod /dev/par c 11 0
20 FAQ-Amiga-NetBSD
_6._1_8. _D_o_e_s _N_e_t_B_S_D _r_u_n _o_n _t_h_e _6_8_0_4_0?
Yes. Michael L. Hitch (osymh@montana.edu) has made it
possible.
_6._1_9. _H_o_w _d_o _I _c_r_e_a_t_e _a_c_c_o_u_n_t_s _a_n_d _c_h_a_n_g_e _u_s_e_r-_i_n_f_o_r_m_a_t_i_o_n?
Use vipw and chpass.
_6._2_0. _H_o_w _d_o _I _g_e_t _a _r_e_b_o_o_t _t_h_a_t _r_e_b_o_o_t_s _i_n_t_o _N_e_t_B_S_D
Do the following:
# mv /sbin/reboot /sbin/reboot.amiga
# echo "cp /vmunix /dev/reboot" >/sbin/reboot
'reboot' reboots NetBSD, 'reboot.amiga' reboots into
Amiga-DOS.
_6._2_1. _H_o_w _d_o _I _g_e_t _c_r_o_n _t_o _w_o_r_k?
Put the crontab-cmd setuid root:
# chmod u+s /usr/bin/crontab
then start the correct cron-daemon in /etc/rc .replace
'cron' by
'/usr/libexec/crond'. To create a user's first crontab do
'crontab
-r /dev/null'.
_6._2_2. _H_o_w _d_o _I _g_e_t _a _s_e_r_i_a_l _t_e_r_m_i_n_a_l _t_o _w_o_r_k _c_o_r_r_e_c_t_l_y?
Add the following line in /etc/ttys:
tty00 "/usr/libexec/getty std.19200" vt100 on secure
Other values for speed can be looked up in /etc/gettytab
_6._2_3. _D_o_e_s _N_e_t_B_S_D _w_o_r_k _w_i_t_h _m_y _r_e_t_i_n_a _a_n_d _m_y _n_o_n_a_m_e-
_m_o_n_i_t_o_r?
NetBSD opens a ~800x600 screen with ~75Hz on the
retina, if present. Some monitors are not able to display a
screen with such a high diplay-rate. So, for your on sake,
set _retina_default_mon to 0 before starting NetBSD.
FAQ-Amiga-NetBSD 21
_6._2_4. _H_o_w _c_a_n _I _a_c_c_e_s_s _F_l_o_p_p_i_e_s _f_r_o_m _N_e_t_B_S_D?
Currently it is not possible to read or write floppies
from NetBSD. A floppy-driver is being worked on, but it is
not complete yet.
_6._2_5. _C_a_n _I _r_u_n _N_e_t_B_S_D _w_i_t_h _m_y _I_D_E-_d_r_i_v_e?
Currently you are not able to run NetBSD with an IDE-
drive. You need an IDE device-driver, which is able to talk
to an IDE-drive. Up to now, nobody volunteered to write one,
so if you want to do so, please go ahead.
_6._2_6. _W_h_a_t _P_r_o_j_e_c_t_s _a_r_e _b_e_i_n_g _w_o_r_k_e_d _o_n?
See the file "projects" for more information. See
question "How do I get NetBSD" for how to obtain this file.
_6._2_7. _I_s _t_h_e_r_e _a _M_a_i_l_i_n_g-_l_i_s_t?
Yes. The list structure for NetBSD on the Amiga:
NetBSD-Amiga - This is the main list that contains
helpful information on installation and
general questions about NetBSD on the Amiga.
New kernel versions and binaries
announcements will appear in this list. A
Frequently Asked Questions will be posted
bi-weekly to monthly.
NetBSD-X - This is the list for installation and
development specifically geared towards
running X under NetBSD on the Amiga.
NetBSD-Dev - This is the list for specifically for
kernel hackers.
How to get on (or off of) the lists:
To: NetBSD-Request@cbmuucp.commodore.com
Subject: SUBSCRIBE NETBSD
Allow a couple of days for the transaction to occur.
If after a few days nothing happens, then resend the
22 FAQ-Amiga-NetBSD
request.
Some acceptable subjects:
SUBSCRIBE X - this will get you on the
NetBSD-X list. UNSUBSCRIBE NETBSD-DEV - this will
remove you from the NetBSD-Dev list. SUBSCRIBE -
this will get you on the NetBSD-Amiga list (the default).
Acceptable aliases:
admin: netbsd-
admin@cbmuucp.commodore.com netbsd-
request@cbmuucp.commodore.com
billc@iceCuBE.rain.com
X list: netbsd-
x@cbmuucp.commodore.com
x@cbmuucp.commodore.com Dev
list: netbsd-dev@cbmuucp.commodore.com
dev@cbmuucp.commodore.com
NetBSD list: netbsd-
amiga@cbmuucp.commodore.com
netbsd@cbmuucp.commodore.com
Past postings:
Past postings to any of the groups are not archived
here. However, you can find an archive from the NetBSD-Amiga
list on ftp.uni-regensburg.de:/pub/NetBSD-
Amiga/DOCS/Mailinglist-Archive. This directory contains all
mails from the NetBSD-Amiga mailing-list, all mails of one
month go into one file. The .Subject-files contain only the
subject-lines of the corresponding month.
You can read the files using your favourite email-frontend.
Just copy the file to /var/spool/mail/$USER (or
/var/mail/$USER, or whatever) and start elm, emacs or
anything else.
Policy:
Commodore Business Machines, Commodore International
Limited, or any of it subsideraries neither cares, nor
endorses this mailing list, the NetBSD project on the Amiga,
or anything affiliated with this project (muchless even
knows what NetBSD is, or what a mailing list is, for that
matter). They are just nice enough to allocate some CPU and
disk space for us, for which we are virtually grateful (just
nod your head and smile, like when some is talking to you in
a foreign language and you have no translator near).
FAQ-Amiga-NetBSD 23
_6._2_8. _I_s _t_h_e_r_e _a _N_e_w_s_g_r_o_u_p _f_o_r _N_e_t_B_S_D?
Yes and no. There is no NetBSD specific Newsgroup, but
most the Newsgroup comp.unix.amiga is the one with the most
NetBSD-Amiga related postings. You may also subscribe to
comp.os.386bsd.{announce, development, apps, bugs, misc,
questions}. Although NetBSD-Amiga is not completely
reintegrated into the source tree, work is underway. So if
you have general NetBSD questions, the above mentioned
newsgroups are fine. If you think that your questions are
more Amiga specific, please use the Amiga-newsgroup.
_6._2_9. _H_o_w _c_a_n _I _a_u_t_o_b_o_o_t _i_n_t_o _m_u_l_t_i-_u_s_e_r _m_o_d_e?
Eduardo Horvath (eeh@public.btr.com) writes
Now for the technical stuff. The boot parameter
is passed to the kernel in d7 (the way the HP
seems to have done it.) The new loadbsd will
default to single user booting. If you specify
the -a flag (ala DECstations), loadbsd will tell
the kernel to autoboot. Older kernels simply
ignore this parameter. new loadbsd usage:
-a boot up to multiuser mode.
-b ask for which root device [I have roots on
3 different disks at times].
-k reserve the first 4M of fast mem [Some one
else is going to have to answer that it is
used for].
-p Currently not used - it's to specify that
the highest priority fastmem segement is
to be used for NetBSD instead of the largest
segment. The higher priority segment is
usually faster (i.e. 32 bit memory), but
some people have smaller amounts of 32 bit
memory.
-t This is a "test" option. It prints out
the memory list information being passed
to the kernel and also exits without actually
starting NetBSD.
_6._3_0. _p_s _d_o_e_s _n_o_t _w_o_r_k _o_n _m_y _s_y_s_t_e_m.
The file /vmunix has to be the same like the kernel you
are running. Just copy your the kernel you started to
/vmunix.
24 FAQ-Amiga-NetBSD
_6._3_1. _N_e_t_B_S_D _o_n _n_o_n _A_3_0_0_0 _m_a_c_h_i_n_e_s.
When you try to run NetBSD on a new machine with a new
configuration other than an A3000, then have a close look at
the is_a3000() function. Currently this function detremines
if NetBSD is running on an A3000 in a very kludgy way. This
is a matter of change in the future, but we have to live
with it today.
_6._3_2. _N_e_t_B_S_D _d_o_e_s _n_o_t _u_s_e _a_l_l _m_y _m_e_m_o_r_y.
Currently NetBSD only uses the largest chunk of Fast-
Memory it can find on boot-up. This might change in the
future, but today there is no workaround for this.
If your memory is continuous, but NetBSD doesn't use
all of it, use the following trick from Chriss Hopps:
Everyone does know about mergemem from workbench
1.3 right? If your memory is contigous but not
merged into a single memlist netbsd doesn't seem
to think its contiguous (bogus). You can run
Mergemem (Sys:system/mergemem) and like magic
netbsd will use the extra ram I am currently doing
this with 4 M 32 on a 2630, 2M on a gvp
csontroller and 2M on a supra 8M board.
_6._3_3. _N_e_t_B_S_D _a_s_k_s _m_e _r_o_o_t _d_e_v_i_c_e?
You have got an old version of loadbsd! Please get a
new one. It's in the bin directory. vmunix-644 and later
won't load correctly with the old one.
_6._3_4. _W_h_e_r_e _c_a_n _I _f_i_n_d _i_x_e_m_u_l._v_e_r_s_i_o_n >= _3_9._4_6?
If loadbsd starts with opening a requester asking you
for a version of the ixemul.library, it ok to continue and
boot with Version 39.45. mtk says:
No problem running it with r45. r46 is a
networking version, I think I only released r47 in
the networking package.
FAQ-Amiga-NetBSD 25
_6._3_5. _H_o_w _d_o _I _r_e_p_o_r_t _b_u_g_s?
If you encountered a bug, before reporting this bug,
please get sure it is really a bug and not your own
mistake/misusage. If you need help, write to the mailing-
list or post your question/bug-report to the appropriate
newsgroups (see "Is there a newsgroup for NetBSD"). If you
report a bur, please try to give as much information as
possible. This includes your configuration and the output
you got.
_6._3_6. _W_h_y _d_o_e_s _N_e_t_B_S_D _n_o_t _c_h_a_n_g_e _m_y _c_l_o_c_k?
At the moment NetBSD is able to read the internal
clock, but it is not possible to write to this clock. You
can set the clock on the AmigaDos side and NetBSD will
recognize the change. It should not be too difficult to add
this functionality to NetBSD, but up to now, nobody did it.
_6._3_7. _W_h_y _d_o_e_s _v_i _t_e_l_l _m_e _h_e _c_a_n_n_o_t _r_e_a_d /_e_t_c/_t_e_r_m_c_a_p ?
This is a bug in the termcap-library. It looks for
/usr/share/misc/termcap, but if it can't find this it says,
that that it can't read /etc/termcap. Move the emacs-termcap
to /etc/termcap and make a symbolic link from
/usr/share/misc/termcap to /etc/termcap.
_6._3_8. _H_o_w _c_a_n _I _c_h_a_n_g_e _t_h_e _c_o_n_s_o_l_e _t_o _a_u_t_o_w_r_a_p?
Use echo -n "^[[?7h". If you compile the kernel for
yourself, you can change the auto-wrap-default in ite.c to
1.
_6._3_9. _N_e_t_B_S_D _w_i_l_l _n_o_t _b_o_o_t _i_n_t_o _m_u_l_t_i-_u_s_e_r-_m_o_d_e
If NetBSD hangs when you are trying to boot into
multiuser-mode, check if you removed the named in /etc/rc.
named causes the machine to hang, if you are not connected
to the internet.
_6._4_0. _H_o_w _d_o _I _u_s_e _b_i_n_p_a_t_c_h?
26 FAQ-Amiga-NetBSD
binpatch is a small utility to patch the kernel. It
uses the bugging information to locate the variables. So,
for example, if your drive is not able to be run in sync-
mode, you can disable the sync-mode by using binpatch as
follows:
Assuming the hd is on ID5 :
# binpatch -s _inhibit_sync vmunix (get address of
_inhibit_sync)
_inhibit_sync(0x12345): 0 (0x0) (replace 0x12345 by
real value from now on)
{Addr=0x12345+Unit (==5)==0x1234a}
# binpatch -b -a 0x1234a -r 1 (replace 0x1234a with
calculated value)
This inhibits sync-handshake on unit 5.
The options of binpatch are:
-s search for an address of a variable
-a <address> specify the address you want to patch
-b patch only a byte value
-w patch a word value (2 bytes)
-l patch a long word value (4 bytes)
-r the value to replace the old value
Another example from mtk:
Remark to Retina-owners with monitors that don't
grok the default video-mode opened by BSD, you're
now able to binpatch this to an inferior mode:
binpatch -s _retina_default_mon -r 1 will give
you 640x512 with 31.5kHz and
binpatch -s _retina_default_mon -r 2 will give
you 768x600 with 38kHz -r 3 is the default at
64kHz.
_6._4_1.
_N_e_t_B_S_D _t_e_l_l_s _m_e: _i_n_i_t _F_A_T_A_L _e_r_r_o_r: _c_o_n_s_o_l_e: _I_n_t_e_r_r_u_p_t_e_d _s_y_s_t_e_m _c_a_l_l
You forgot to install libexec/getty.
FAQ-Amiga-NetBSD 27
_6._4_2. _H_o_w _d_o _I _g_e_t _a _M_e_t_a-_K_e_y _f_o_r _E_m_a_c_s ?
According to mtk, enter 'stty cs8 -istrip -parenb' and
use any Amiga-key as meta-key.
_6._4_3. _H_o_w _d_o _I _g_e_t _a _g_e_r_m_a_n _k_e_y_m_a_p?
Starting from 644 the distribution contains (in
sys/arch/amiga/stand/loadkmap) a prog to do just this.
Compile it, generate the german keymap and user loadkmap to
get a german keymap:
bin-kbdmap >din
loadkmap din
_6._4_4. _H_o_w _d_o _I _g_e_t _d_m_e_s_g _t_o _w_o_r_k?
chmod u+s /usr/sbin/dmesg
_6._4_5. _i_o_c_t_l (_G_D_I_N_F_O): _i_n_v_a_l_i_d _a_r_g_u_m_e_n_t. _W_h_a_t _i_s _w_r_o_n_g?
Starting with version 713 support for Non-BSD
partitions was added. This
meant that pre-713 binaries of programs depending on
sizeof (struct
disklabel) got obsolete. Specifically newfs, mount_mfs
(which is a link
to newfs) and disklabel didn't work anymore. Newer
versions of these
can be gotten from ftp.eunet.ch, either in bin-newest or
in bin-sbin.tar.gz
if it's newer than Nov 22 1993. If you've compiled the
thing yourself,
recompile it making sure that you use a post-713 version
of sys/disklabel.h
which can be found either in a recent (post-713)
bsdsyssrc.xxx.tar.gz
archive or a post-713 release of bin-usr.include.tar.gz.
_6._4_6. _W_h_a_t _i_s /_b_i_n-_n_e_w_e_s_t _f_o_r?
This directory contains the latest versions of some
programs. If a program does not work as expected, look into
this directory to see, if someone has put up a later version
into it, than the one you are using. This directory was
28 FAQ-Amiga-NetBSD
created to remove to need to update bin-distribution every
time a binary has changed.
_6._4_7. _H_o_w _t_o _s_e_t _u_p _S_L_I_P?
1 Dialup (and maybe login to) a SLIP port
(kermit is a good way to do this).
2 slattach -a -h -s 38400 //dev/tty00
3 ifconfig sl0 LOCAL-IP-ADDR REMOTE-IP-ADDR -arp
-trailers up
4 route add 0.0.0.0 REMOTE-IP-ADDR
Well, here are the steps I used to get it running.
First let me state that the terminal server I dial-in to
haas support for SLIP, so I only need to connect to it and
tell it I want a SLIP connection. Others may have to
actually login and start SLIP on the login session. Also
because of this connection method my IP address can change
each time.
1. Edit /etc/netstart to turn off the servers you won't
use, but leave routed on. Setup /etc/hosts for your
node and any others and make sure "hostname" and
"domainname" reflect the proper things.
2. Run kermit to connect to the remote node:
set modem none (I use this to keep the line alive)
set line /dev/tty00 set speed 38400 (This
may depend on your modem) (Can
NetBSD support 57.6Kbaud?) set flow rts/cts
dial ### connect <Do what ever to
get SLIP running remotely> Cntrl-\ Q (Kill off
Kermit, leaving line up)
3. Start up the local SLIP service: slattach -a
-h -s 38400 /dev/tty00
4. Enable the network connection: ifconfig sl0
inet <local IP addr> <remote IP addr> -arp -trailers up
5. Turn on routing: route add 0.0.0.0 <remote
IP addr>
I tried to setup routing information int he
/etc/gateways file, but routed seemed to ignore it.
FAQ-Amiga-NetBSD 29
Anyone know more details on how this should be done
or if routed supports the file? I also tried to use
"default" in place of "0.0.0.0" in the route comand,
but it does not understand that syntax. I got that syntax
from SUNOS 4.1 manuals and AmiTCP setup.
6. To avoid adding everything to your /etc/hosts file,
turn on DNS access if you have it avialable on the
remote end. Do this by creating or copying a
/etc/resolv.config file from the reomte network.
Now all I need is to build ftptool on the NetBSD end
and I can start downloading software directly to my Amiga :)
_6._4_8. _C_a_n _I _r_e_a_d _a _s_u_n _t_a_p_e _d_a_t_a _c_a_r_t_i_d_g_e?
The original sun Archive tape drive, will read/write
both
QIC-11,QIC-24 format. To maximize you chances of reading
the
tape from your tape drive use the QIC-24 format. How? Do
a :
tar -cvf /dev/rts8
will create a QIC-24 formatted tape.
_6._4_9. _W_h_a_t _i_f _m_y _t_a_p_e _d_r_i_v_e _o_n _t_h_e _s_u_n _i_s _a _A_r_c_h_i_v_e _V_i_p_e_r?
Though the hardware of a 'Archive Viper' is capable of
reading/writing
multiple tape formats, sun only supports on format for
writing, QIC-150.
So using /dev/rts0, /dev/rst8, /dev/rst16, /dev/rst24
will all produce
a QIC-150 formatted tape.
_6._5_0. _H_o_w _c_a_n _I _t_e_l_l _w_h_a_t _t_y_p_e _o_f _t_a_p_e _d_r_i_v_e _m_y _s_u_n _h_a_s?
You don't, just use /dev/rst8 for all data cartridge
systems. Note if it
isn't a 8mm tape or a 4mm tape then it probably is a Data
Cartridge.
30 FAQ-Amiga-NetBSD
_6._5_1.
_H_o_w _c_a_n _I _f_i_n_d _t_h_e _m_a_j_o_r _a_n_d _m_i_n_o_r _n_u_m_b_e_r_s _f_o_r _d_e_v_i_c_e_s?
Simply look into sys/arch/amiga/amiga/conf.c There is
an array organized by major device numbers. Minors are the
unit numbers.
_6._5_2. _D_o_e_s _N_e_t_B_S_D _r_u_n _w_i_t_h _t_h_e _P_R_O_T_O-_C_h_i_p?
Yes. The ONLY problem which may occure is that some
drives (!) do not like to be enabled to the sync mode, which
the PROTO does not handle properly. Again: this depends on
the drives you are using, and the kludges in the kernel.
FAQ-Amiga-NetBSD 31
_7. _W_h_a_t _w_e_n_t _w_r_o_n_g _w_i_t_h _t_h_e _l_a_t_e_s_t _d_i_s_t_r_i_b_u_t_i_o_n?
_7._1. _l_i_b_c _g_o_t _c_r_i_p_p_l_e_d
A part of libc got crippled, so all programs linked
with this part do not function properly. This affects the
regular expression matching.
_7._1._1. _s_e_d
Neither of the distributed sed does not work properly.
Get gnu-sed-2.03 and use the sed in usr gnu to built it or
rebuilt libc.
_7._1._2. _e_x_p_r
expr does not work properly and there is no workaround
for it, other than building a new libc and then rebuilding
expr.
_7._2. _g_c_c
Most of the headerfiles generated in /usr/gnu/lib/gcc-
lib/netbsdamiga/2.5.6/include are bogus.
Remove all the files *EXCEPT* the following (at least
that's what mtk did after discovering the problem):
total 50 -rw-r--r-- 1 root 10 495 Dec 8 19:26
README -rw-r--r-- 1 root 10 3719 Dec 8 22:08 float.h
-rw-r--r-- 1 root 10 2922 Dec 8 19:26 limits.h -rw-r--
r-- 1 root 10 9573 Dec 8 19:30 math-68881.h -rw-r--r--
1 root 10 5394 Dec 8 19:25 math.h drwxr-xr-x 2 root 10
512 Dec 8 19:31 objc
_7._3. _r_o_o_t_f_s__7_2_0
Make a symbolic link from /usr/share/misc/termcap to
/etc/termcap. This gets vi and more working without
complaining.
32 FAQ-Amiga-NetBSD
A few binaries are not stripped in /bin and /sbin. This
is not really a bug, but consumes a bit of hd-space. To save
even more space remove /bin/sh and make a hard link from
/bin/bash to sh. Both files are identical in this release,
anyway.
So, to sum up:
cd /bin exec csh strip bash rm sh ln -f bash sh strip
less strip ash strip red
cd /sbin strip chown strip ldconfig exec bash
_7._4. _R_e_c_o_m_p_i_l_i_n_g _t_h_e _k_e_r_n_e_l
I found some odd things in building the kernel that
I'll pass on for other first time builders:
- make sure the /lib/cpp link is right. Mine
pointed to the wrong gcc version.
- I had two config programs on my system. One
in /usr/sbin which didn't work but was used by
default from the path. The other was in /usr/share
and it worked.
- I had to change the ENTRY macro in
sys/lib/libkern/amiga/DEFS.h to be from:
.globl /**/x; .even; _/**/x: to:
.globl ##x; .even; _##x##: and I
had to copy it into sys/lib/libkern/m68k
- I had to copy fpspnull.s to fpsp.s
- I had to make .s versions of strncmp and
strncpy using gcc -S on the c versions in
sys/lib/libkern
_7._5. _L_o_a_d_i_n_g _t_h_e _k_e_r_n_e_l
Please use the latest loadbsd.730 to load kernels >=
720. This avoids some problems you might encounter
otherwise.
If the kernel doesn't boot, try binpatch -s
_ite_default_height -r 400 [kernel name]. You can also use
200 instead of 400.
FAQ-Amiga-NetBSD 33
_7._6. _C_o_n_s_o_l_e _b_u_g
The current console has a bug, which shows when using
man.
Please do the following binpatch:
binpatch _kernel_font_baseline -b -r 6 [kernel name]
_7._7. _p_a_n_i_c: _c_a_n_n_o_t _m_o_u_n_t _r_o_o_t
Generally there seem to be 2 standard possibilities:
(1) Your scsi controler cannot dma to the mmu
memory. Solution: binpatch _scsi_no_dma to 1.
(2) You did not install the rootfs to the appropriate
block. Solution: binpatch _sddebug to 1. This will
output you, where NetBSD looks for the rootfs. Write
down this number and filetodev the rootfs to the
proper position.
(Be sure to have reserved blocks = 0.
hdtoolbox sometimes doesn't change this value
correct)
For me none of the two worked. Michael L. Hitch seems
to have found the problem as beeing something of 16 vs 32
bit word access problem of my '030. But I'd suggest, you try
the first 2 ways before going more into this.
FAQ-Amiga-NetBSD i
Table of Contents
1 Introduction .................................. 3
2 General things ................................ 4
2.1 The name of the game: What is NetBSD? ........ 4
2.2 Who is working on the port? .................. 4
3 What do I need to run NetBSD .................. 5
3.1 What kind of Amigas will it run on? .......... 5
3.1.1 Which cpu is needed? ......................... 5
3.1.2 How much memory do I need? ................... 6
3.1.3 How much diskspace do I need? ................ 6
3.1.4 What other hardware requirements are there?
4 What about building the kernel myself? ........ 8
5 NetBSD - Linux - Amiga-Unix - Minix ........... 9
6 Frequently Asked Questions and their answers
6.1 How do I get NetBSD? ......................... 11
6.2 How do I install it? ......................... 11
6.3 Does NetBSD support my device? ............... 11
6.4 I cannot su to root .......................... 11
6.5 I have problems with my tape drive. ........ 11
6.5.1 Tapedrive -- Problem 1 ....................... 12
6.5.2 Tapedrive -- Problem 2 ....................... 12
6.5.3 General workaround for tapedrive problems
6.6 What do I need to know about softlinks? ...... 13
6.7 I have no uptime-command? .................... 14
ii FAQ-Amiga-NetBSD
6.8
How do I update the header files automatically ? ...... 14
6.9 How do I get a /usr/local? ................... 15
6.10
What packages can I install for BSD to enhance it?
6.11 How Do I get man pages. ..................... 17
6.12
How can I modify the kernel to work with my graphic card?
6.13 What about X-Windows? ....................... 18
6.14 What about networking? ...................... 19
6.15 What about accessing ados-
files from NetBSD? .................................... 19
6.16
Is there a debugger for NetBSD. Is there any? If so, where is it?
6.17
How do I get /dev/reload and /dev/zero and /dev/par ?
6.18 Does NetBSD run on the 68040? ............... 20
6.19 How do I create accounts and change user-
information? .......................................... 20
6.20
How do I get a reboot that reboots into NetBSD ........ 20
6.21 How do I get cron to work? .................. 20
6.22
How do I get a serial terminal to work correctly? ..... 20
6.23
Does NetBSD work with my retina and my noname-
monitor? .............................................. 20
6.24 How can I access Floppies from NetBSD? ...... 21
6.25 Can I run NetBSD with my IDE-drive? ......... 21
6.26 What Projects are being worked on? .......... 21
6.27 Is there a Mailing-list? .................... 21
6.28 Is there a Newsgroup for NetBSD? ............ 23
6.29 How can I autoboot into multi-user mode?
FAQ-Amiga-NetBSD iii
6.30 ps does not work on my system. .............. 23
6.31 NetBSD on non A3000 machines. ............... 24
6.32 NetBSD does not use all my memory. .......... 24
6.33 NetBSD asks me root device? ................ 24
6.34 Where can I find ixemul.version >= 39.46?
6.35 How do I report bugs? ....................... 25
6.36 Why does NetBSD not change my clock? ........ 25
6.37
Why does vi tell me he cannot read /etc/termcap ? ..... 25
6.38 How can I change the console to autowrap?
6.39 NetBSD will not boot into multi-user-mode
6.40 How do I use binpatch? ...................... 25
6.41
NetBSD tells me: init FATAL error: console: Interrupted system call
6.42 How do I get a Meta-Key for Emacs ? ......... 27
6.43 How do I get a german keymap? ............... 27
6.44 How do I get dmesg to work? ................. 27
6.45
ioctl (GDINFO): invalid argument. What is wrong? ...... 27
6.46 What is /bin-newest for? .................... 27
6.47 How to set up SLIP? ......................... 28
6.48 Can I read a sun tape data cartidge? ........ 29
6.49
What if my tape drive on the sun is a Archive Viper?
6.50
How can I tell what type of tape drive my sun has?
6.51
How can I find the major and minor numbers for devices?
6.52 Does NetBSD run with the PROTO-Chip? ........ 30
7 What went wrong with the latest distribution?
iv FAQ-Amiga-NetBSD
7.1 libc got crippled ............................ 31
7.1.1 sed .......................................... 31
7.1.2 expr ......................................... 31
7.2 gcc .......................................... 31
7.3 rootfs_720 ................................... 31
7.4 Recompiling the kernel ....................... 32
7.5 Loading the kernel ........................... 32
7.6 Console bug .................................. 33
7.7 panic: cannot mount root ..................... 33