About this Document What is NetBSD? Changes Between The NetBSD 9 and 10 Releases Features to be removed in a later release The NetBSD Foundation Sources of NetBSD NetBSD 10.1 Release Contents NetBSD/atari subdirectory structure Binary distribution sets NetBSD/atari System Requirements and Supported Devices Supported devices Getting the NetBSD System on to Useful Media Preparing your System for NetBSD installation Preparing your hard disk for the NetBSD installation. Booting the installer on an existing system Booting the installer on new systems. Using loadbsd.ttp Installing the NetBSD System Running the sysinst installation program Introduction General Quick install Booting NetBSD Network configuration Installation drive selection and parameters Selecting which sets to install Partitioning the disk Preparing your hard disk Getting the distribution sets Installation from CD-ROM Installation using FTP Installation using NFS Installation from an unmounted file system Installation from a local directory Extracting the distribution sets Configure additional items Finalizing your installation Post installation steps Upgrading a previously-installed NetBSD System Compatibility Issues With Previous NetBSD Releases Using online NetBSD documentation Administrivia Thanks go to Legal Mumbo-Jumbo The End
This document describes the installation procedure for
NetBSD
10.1 on the
atari
platform.
It is available in four different formats titled
INSTALL.ext,
where
.ext
is one of
.ps, .html, .more,
or .txt:
.ps.html.moremore(1)
and
less(1)
pager utility programs.
This is the format in which the on-line
man
pages are generally presented.
.txtYou are reading the HTML version.
The NetBSD Operating System is a fully functional open-source operating system derived from the University of California, Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on many different different system architectures (ports) across a variety of distinct CPU families, and is being ported to more. The NetBSD 10.1 release contains complete binary releases for most of these system architectures, with preliminary support for the others included in source form. For more information please visit https://www.NetBSD.org/.
NetBSD is a completely integrated system. In addition to its highly portable, high performance kernel, NetBSD features a complete set of user utilities, compilers for several languages, the X Window System, firewall software and numerous other tools, all accompanied by full source code.
NetBSD is a creation of the members of the Internet community. Without the unique cooperation and coordination the net makes possible, NetBSD would not exist.
The NetBSD 10.1 release provides many significant changes, including support for many new devices, hundreds of bug fixes, new and updated kernel subsystems, and numerous userland enhancements. The result of these improvements is a stable operating system fit for production use that rivals most commercially available systems.
One important new feature in this release is the support for extended attributes and access control lists on FFS file systems.
For new installations the installer will by default disable these features, so the file system is compatible with older NetBSD releases (before 10), and allow other operating systems to mount this file systems at least in read-only mode.
If you want a new installed file system to support extended attributes,
change the file system type from
``FFSv2''
to
``FFSv2ea''
in the partitioning menu.
You can also convert file systems later, using the
fsck_ffs(8)
utility.
More details are available in
this guide.
If you are upgrading from a version of NetBSD-current please also check the Compatibility Issues With Previous NetBSD Releases.
It is impossible to completely summarize the massive development that
went into the
NetBSD
10.1 release.
The complete list of changes can be found in
CHANGES
CHANGES-10.1
which are also present in the top level directory of the
NetBSD 10.1 release tree.
groff(1).
Man pages are now handled with
mandoc(1),
and
groff(1)
can still be found in pkgsrc as
textproc/groff.
pf(4).
This packet filter is obsolete and unmaintained in
NetBSD.
It will be eventually removed due to possible long-standing
security issues and lack of multiprocessor support.
New installations should use
npf(7).
The
NetBSD
Foundation is a tax exempt, not-for-profit 501(c)(3) corporation
that devotes itself to the traditional goals and spirit of the
NetBSD
Project and owns the trademark of the word
``NetBSD''.
It supports the design, development, and adoption of
NetBSD
worldwide.
More information on the
NetBSD
Foundation, its composition, aims, and work can be found at:
https://www.NetBSD.org/foundation/
Refer to
mirrors
The root directory of the NetBSD 10.1 release is organized as follows:
.../NetBSD-10.1/
CHANGESCHANGES-10.0CHANGES-10.1CHANGES.prevLAST_MINUTEREADME.filesimages/source/In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures for which NetBSD 10.1 has a binary distribution.
The source distribution sets can be found in subdirectories of the
source
subdirectory of the distribution tree.
They contain the complete sources to the system.
The source distribution sets are as follows:
config(1)
utility.
All the above source sets are located in the
source/sets
subdirectory of the distribution tree.
The source sets are distributed as compressed tar files.
Except for the
pkgsrc
set, which is traditionally unpacked into
/usr/pkgsrc,
all sets may be unpacked into
/usr/src
with the command:
# cd / ; tar -zxpf set_name.tgz
In each of the source distribution set directories, there are files which contain the checksums of the files in the directory:
MD5SHA512The SHA512 digest is safer, but MD5 checksums are provided so that a wider range of operating systems can check the integrity of the release files.
atari
subdirectory of the distribution:
.../NetBSD-10.1/atari/.
It contains the following files and directories:
INSTALL.htmlINSTALL.psINSTALL.txtINSTALL.more.more
file contains underlined text using the
more(1)
conventions for indicating italic and bold display.
binary/kernel/netbsd-SMALL030.gznetbsd-ATARITT.gznetbsd-FALCON.gznetbsd-HADES.gznetbsd-MILAN-ISAIDE.gznetbsd-MILAN-PCIIDE.gzsets/installation/floppy/miniroot/misc/atari/binary/sets
subdirectory
of the
NetBSD
10.1
distribution tree, and are as follows:
/usr/include)
and the various system libraries (except the shared
libraries, which are included as part of the
base
set).
This set also includes the manual pages for
all of the utilities it contains, as well as the
system call and library manual pages.
/etc
and in several other places.
This set
must
be installed if you are installing the system from scratch, but should
not
be used if you are upgrading.
/netbsd.
You
must
install the kernel that matches your hardware.
/usr/share.
/rescue.
groff(1),
all related programs, and their manual pages.
NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on X.Org. Binary sets for the X Window System are distributed with NetBSD. The sets are:
The atari binary distribution sets are distributed as gzipped tar files
named with the extension
.tgz,
e.g.
base.tgz.
The instructions given for extracting the source sets work equally
well for the binary sets, but it is worth noting that if you use that
method, the filenames stored in the sets are relative and therefore
the files are extracted
below the current directory.
Therefore, if you want to extract the binaries into your system, i.e.
replace the system binaries with them, you have to run the
tar -xzpf
command from the root directory (
/
) of your system.
Additional kernels to those included in the distribution sets may be found
in the
atari/binary/kernel
subdirectory of the
NetBSD
10.1 distribution tree.
These kernels are generally named something like
netbsd-BOOT.gz
or some other suitable name.
Please note that these kernels are simply gzipped and are not in tar archives.
There are six atari floppy images to be found in the
atari/installation/floppies
subdirectory of the
NetBSD
10.1 distribution.
Three of them are bootable
TOS
kernel floppies and the other
three are installation floppies.
They are described in more detail below.
There are gzipped versions of each available, for easier downloading.
(The gzipped versions have the
.gz
extension added to their names.)
For the TT030 and Falcon, the (720 KB) floppy is named
boot.fs
and
the kernel supplied is
BOOT.
For the Hades, you need the
hades-boot.fs
floppy (1.44 MB), the kernel is
HADES.
For the Milan, you need the
milan-boot.fs
floppy (1.44 MB), the kernel is MILAN-PCIIDE.
/
(root) and
/usr
partitions and getting
ready to extract (and possibly first fetching) the distribution
sets.
There is enough on this file system to allow you to
make a slip connection, configure an ethernet, mount an NFS
file system or ftp.
You can also load distribution sets from a SCSI tape or from one of
your existing
GEMDOS
partitions.
The floppies meant for 720 KB disks are named
miniroot.fs.1
and
miniroot.fs.2.
There is also an image for an 1.44 MB disk:
miniroot.fs.
There are also
TOS
utilities in the
atari/installation/misc
subdirectory, which you will need to get
NetBSD/atari
up-and-running.
gzip.ttp -d filename.gz
atari/floppies
directory.
sysinst.fs
to a partition with id SWP.
In this way, you can run the installation from the swap partition
instead of a memory disk.
This is a necessity for small memory systems.
NetBSD/atari 10.1 runs on the TT030, Falcon, Hades and MilanI machines. An FPU is not required. The minimum amount of RAM required is 4 MB. On the Hades, only the Tseng PCI VGA cards (ET4000/ET6000/ET6100) are supported in the 10.1 release. When an unsupported video card is present, you can use NetBSD with a serial console only.
A minimal installation requires around 100MB of disk space, plus a swap
partition size of 2*RAM (and always greater than 20MB).
You will probably want to compile your own kernel, as
GENERIC
is large and bulky in order to accommodate all people,
BOOT
is small and might not have all the features you want).
This list is incomplete by definition.
We can not test all SCSI peripherals, ISA cards or PCI cards.
If you have problems with such peripherals, please contact the
port-atari@NetBSD.org
mailing list.
Installation is supported from several media types, including:
No matter what you do, however, you'll need to have three disks handy, on which you will put the install and boot floppy images.
All the images are available from the directory
installation/floppies
under the root of the
NetBSD/atari
tree at your favorite archive site.
If you are using
NetBSD/atari
to make the floppies, you should use
the command
dd(1)
to write the raw floppy images (.fs files) to
the disk.
As an example, to write the first part of the miniroot file system
onto a 720 KB floppy in fd0 use:
# dd if=miniroot.fs.1 of=/dev/rfd0b bs=9b
If you are using
TOS
to make the floppies, grab the
rawwrite
utility from the
atari/utils
directory and issue the command:
rawwrite boot.fs
This will create the boot-floppy on the floppy in drive a. The floppies should be pre-formatted on 720 KB / 1.44 MB for both the dd and rawwrite commands to work. Pre-formatting can be best done using the desktop format command. Some other utilities seem to be giving problems.
Since the 1.3 release, it is also possible to use HD-floppies.
You should than use the floppy device
/dev/rfd0c
or add the
-H
flag to
rawwrite.
The steps necessary to prepare the distribution sets for installation depend on which method of installation you choose. The various methods are explained below.
Note where you placed the files, you will need this later.
Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk.
# cd .../NetBSD-10.1/atari/binary/sets
# T=<tape_device>
# mt -f $T rewind
# for f in base etc comp games man misc rescue text
dd if=$f.tgz of=$T conv=osync bs=5k
# done
# mt -f $T rewind
where
``<tape_device>''
is the name of the (non-rewinding!) tape
device that you're using (probably something like
/dev/nrst0,
but we make no guarantees 8-).
If you can't figure it out, ask your system administrator.
Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk.
If
NetBSD
has to share the disk with another operating system, you can
either take care of partitioning your harddisk before installing
NetBSD
or delay this until the installer requests you to do it.
If you decide to do it now, please create space for at least
/
(root) and swap partitions.
Whatever you decide, take note of the paragraphs below!
You need this info to create bootable disks.
If you want to use an AHDI partitioning scheme and you want to be able to boot directly into NetBSD, there are some constraints on the partition layout.
As you might know, every hard disk has a `root sector' that contains information about the size of the hard disk and the partitions on the hard disk. The root sector can only contain the necessary data for four partitions. Nobody thought that this limitation would cause any problems. After all, 640 KByte should be enough. As hard disks grew, it was necessary to define more than four partitions. In order to be more or less compatible with the old format, a new type of partition entry was defined: XGM partitions.
An XGM partition is a `look over there' sign: Another root sector can be found at the start of the XGM partition. This root sector contains the remaining real partitions. And this is the big mystery: Partitions defined in the root sector of the hard disk are called `primary partitions', partitions defined in the root sector of an XGM partition are called `extended partitions'.
The bootblock will only work if the first NBD partition is a primary partition. This is not a limitation of NetBSD but a limitation of TOS/AHDI: You can only boot from primary partitions.
If you are creating your partitions with HDX, you'll have to be very careful to fulfill this rule. HDX has some very strange ideas when it comes to extended partitions. Fortunately, you can edit this stuff: The ``Edit partition scheme of the unit'' dialog box has a button labeled ``expert''. This button is inactive unless you have defined more than four partitions. Click on it after you have defined the sizes of the partitions.
A new dialog box appears on the screen. The left side contains two blocks of partitions; the upper block always contains the first four partitions, the lower block contains the last three partitions. If you have defined less than 7 partitions, some fields of the lower block will contain the string ``unused''. Some of the partitions will be displayed in reverse video: These are the extended partitions.
The right side contains six possible ranges for the extended partitions. It is not possible to define your own range, you will have to use one of the schemes offered by HDX. To quote from Ghostbusters: Choose and die. The default scheme used by HDX is the first scheme: Extended partitions start with the second partition and end with the second to last partition. If you have defined 7 partitions, partitions #2 to #5 will be extended partitions, while partitions #1, #6 and #7 will be primary partitions.
You can move the extended partition range by clicking on one of the buttons on the right side of the dialog box. Try to find one where your first NetBSD partition is a primary partition. Golden rules:
dd if=sysinst.fs of=/dev/rsd0b
where
/dev/rsd0b
should be the device path of the swap partition your system
is configured to use.
Once the file is copied, reboot back to the booter
and use the '-b' option to make the kernel prompt for a root device.
Now enter the swap device as your root device to start the installer.
For new new installations on small memory systems, things are a bit more complicated. The easiest way is to mark an AHDI partition as id 'SWP'. You can either accomplish this with HDdriver or use the chg_pid.ttp program supplied on the bootfloppy. To use the fifth partition of your first drive to a swap partition, do the following:
chg_pid -w 0 4 SWP
As you can see, both the drive and the partition numbers are zero based.
When a swap partition has been created, you can transfer the installer using the file2swp.ttp command, which is also on the bootfloppy. This program copies a (gzipped) file to the first AHDI partition with id 'SWP' on the designated disk. To copy sysinst.fs to your first SCSI disk, use:
file2swp -w -f sysinst.fs s0
Note that file2swp automatically detects a gzipped file, there is no need for a .gz extension.
loadbsd -b a:/netbsd
You should see the screen clear and some information about your system as the kernel configures the hardware. Then you will be prompted for a root device. If you copied the installer to a swap partition, as explained above, you have to enter the swap partition as the boot device. When you used your first SCSI disk, this will be sd0b. On the first IDE drive it would be wd0b.
If you didn't copy the installer to swap, you need to use the RAMdisk, so remove the GEMDOS kernel boot floppy from the drive if present and insert the NetBSD install floppy 1. Now enter the name of the boot device depending on the floppy type you have inserted. Use:
Installing NetBSD is a relatively complex process, but, if you have this document in hand and are careful to read and remember the information which is presented to you by the install program, it shouldn't be too much trouble.
Before you begin, you must have already prepared your hard disk as detailed in the section on preparing your system for install.
The following is a walk-through of the steps necessary to get NetBSD installed on your hard disk.
Using sysinst, installing NetBSD is a relatively easy process. Still, you should read this document and have it available during the installation process. This document tries to be a good guide to the installation, and as such, covers many details for the sake of completeness. Do not let this discourage you; the install program is not hard to use.
The following is a walk-through of the steps you will take while
installing
NetBSD
on your hard disk.
sysinst
is a menu-driven program that guides you through the installation process.
Sometimes questions will be asked, and in many cases
the default answer will be displayed in brackets
(``[ ]'')
after the question.
If you wish to stop the installation, you may press
CONTROL-C
at any time, but if you do, you'll have to begin the installation
process again from scratch by running the
/sysinst
program from the command prompt.
It is not necessary to reboot.
First, let's describe a quick install. The other sections of this document go into the installation procedure in more detail, but you may find that you do not need this. If you want detailed instructions, skip to the next section. This section describes a basic installation, using a CD / DVD as the install medium.
.***********************************************.
* NetBSD-10.1 Install System *
* *
*>a: Install NetBSD to hard disk *
* b: Upgrade NetBSD on a hard disk *
* c: Re-install sets or install additional sets *
* d: Reboot the computer *
* e: Utility menu *
* f: Config menu *
* x: Exit Install System *
.***********************************************.
root
user when prompted by
sysinst,
logging in as
root
and setting a password should be your first task.
You are also advised to read
afterboot(8).
Boot the system as described in the "Booting the installer" section above.
Once NetBSD has booted and printed all the boot messages, you will be presented with a welcome message and a main menu. It will also include instructions for using the menus.
If you do not intend to use networking during the installation, but you do want your machine to be configured for networking once the system is installed, you should first go to the Utility menu and select the Configure network option. If you only want to temporarily use networking during the installation, you can specify these parameters later. If you are not using the Domain Name System (DNS), you can give an empty response when asked to provide a server.
To start the installation, select Install NetBSD to hard disk from the main menu.
The first thing is to identify the disk on which you want to
install
NetBSD.
sysinst
will report a list of disks it finds
and ask you for your selection.
You should see disk names like
sd0
or
sd1.
The next step is to choose which distribution sets you wish to install. Options are provided for full, minimal, and custom installations. If you choose sets on your own, base, etc, and a kernel must be selected.
You will be prompted if you want an AHDI compatible partitioning on your disk. If you are installing NetBSD on a dedicated drive, just answer 'no' and skip to the next section.
If you answer 'yes', the ahdilabel program is started. You can now change the AHDI partition IDs on your root disk. Because NetBSD imposes a special ordering in disk partitions it uses for / (root) and swap. Also, because it wants to guard you against an unwanted demolition of partitions used by other systems, you have to tell it what partitions it is allowed to use. You have to mark the partition you want to use as swap SWP or (deprecated!) NBS and the other partitions as NBD. Note that all the changes you make to the IDs are reversible as long as you remember the original value. ahdilabel is capable of creating or changing an AHDI compatible partitioning on the disk, and in the partition-ID editor, the partitions are shown in the order that AHDI created them. When you leave this editor and continue with sysinst, your changes to the IDs do have consequences to the partition order! They will show up as follows:
abd (and up)The partition table of the NetBSD part of a disk is called a disklabel. If your disk already has a disklabel written to it, you can choose Use existing partition sizes. Otherwise, select Set sizes of NetBSD partitions.
If you want to use NetBSD on an AHDI partitioned disk, you will have to use: Use Existing.
After you have chosen your partitions and their sizes (or if you opted to use the existing partitions), you will be presented with the layout of the NetBSD disklabel and given one more chance to change it. For each partition, you can set the type, offset and size, block and fragment size, and the mount point. The type that NetBSD uses for normal file storage is called 4.2BSD. A swap partition has a special type called swap. Some partitions in the disklabel have a fixed purpose.
a/)
bcd-pd
is the partition mounted on
/usr,
but this is historical practice and not a fixed value.
You will then be asked to name your disk's disklabel. The default response will be OK for most purposes. If you choose to name it something different, make sure the name is a single word and contains no special characters. You don't need to remember this name.
You are now at the point of no return. Apart from the changes you made with ahdilabel nothing has been modified on your disk yet. If you confirm that you want to install NetBSD, the partitions now assigned to NetBSD will be actually written to. If you are sure you want to proceed, select yes.
The install program will now label your disk and create the file systems you specified. The file systems will be initialized to contain NetBSD bootstrapping binaries and configuration files. You will see messages on your screen from the various NetBSD disk preparation tools that are running. There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. Otherwise, you can continue the installation program after pressing the return key.
The NetBSD distribution consists of a number of sets that come in the form of gzipped tar files. At this point, you will be presented with a menu which enables you to choose from one of the following methods of installing the sets. Some of these methods will first transfer the sets to your hard disk, others will extract the sets directly.
For all these methods, the first step is to make the sets available for extraction. The sets can be made available in a few different ways. The following sections describe each of the methods. After reading about the method you will be using, you can continue to the section labeled `Extracting the distribution sets'.
When installing from a CD-ROM, you will be asked to specify
the device name for your CD-ROM drive
(usually cd0)
and the directory name on the CD-ROM where the distribution files are.
sysinst will then check that the files are actually present in the specified location and proceed to the extraction of the sets.
To install using FTP, you first need to configure
your network setup if you haven't already done so.
sysinst
will help you with this, asking if you want to use DHCP.
If you do not use DHCP, you can enter network configuration
details yourself.
If you do not have DNS set up for the machine that you
are installing on, you can just press
RETURN
in answer to this question, and DNS will not be used.
You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, the account name and password used to log into that host using FTP, and optionally a proxy server to use. If you did not set up DNS, you will need to specify an IP address instead of a hostname for the FTP server.
sysinst will then transfer the set files from the remote site to your hard disk.
To install using NFS, you first need to configure
your network setup if you haven't already done so.
sysinst
will do this for you, asking you
if you want to use DHCP.
If you do not use DHCP, you can enter network configuration
details yourself.
If you do not have DNS set up for the machine that you
are installing on, you can just press
RETURN
in answer to this question, and DNS will not be used.
You will also be asked to specify the host that you want to transfer the sets from and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e., correctly exported to your machine.
If you did not set up DNS, you will need to specify an IP address instead of a hostname for the NFS server.
In order to install from a local file system, you will
need to specify the device that the file system resides
on
(for example wd1e),
the type of the file system,
and the directory on the specified file system where the sets are located.
sysinst
will then check if it
can indeed access the sets at that location.
This option assumes that you have already done some preparation yourself. The sets should be located in a directory on a file system that is already accessible. sysinst will ask you for the name of this directory.
A progress bar will be displayed while the distribution sets are being extracted.
After all the files have been extracted, the device node files will be created. If you have already configured networking, you will be asked if you want to use this configuration for normal operation. If so, these values will be installed in the network configuration files.
The next menu will allow you to select a number of additional items to configure, including the time zone that you're in, to make sure your clock has the right offset from UTC, the root user's shell, and the initial root password.
You can also enable installation of binary packages, which installs the
pkgin(1)
tool for managing binary packages for third-party software.
This will
feel familiar to users of package tools such as
apt-get
or
yum.
If you prefer to install third-party software from source, you can install
the
pkgsrc(7)
tree.
Finally, you can enable some daemons such as
sshd(8),
ntpd(8),
or
mdnsd(8).
Congratulations, you have successfully installed NetBSD 10.1. You can now reboot the machine and boot NetBSD from hard disk.
Once you've got the operating system running, there are a few things you need to do in order to bring the system into a properly configured state. The most important steps are described below.
postinstall(8).
/etc/rc.conf
If you or the installation software haven't done any configuration of
/etc/rc.conf
(sysinst
normally will),
the system will drop you into single user mode on first reboot with the
message
/etc/rc.conf is not configured. Multiuser boot aborted.
and with the root file system
(/)
mounted read-only.
When the system asks you to choose a shell, simply press
RETURN
to get to a
/bin/sh
prompt.
If you are asked for a terminal type, respond with
vt220
(or whatever is appropriate for your terminal type)
and press
RETURN.
You may need to type one of the following commands to get your delete key
to work properly, depending on your keyboard:
# stty erase '^h'
# stty erase '^?'
At this point, you need to configure at least
one file in the
/etc
directory.
You will need to mount your root file system read/write with:
# /sbin/mount -u -w /
Change to the
/etc
directory and take a look at the
/etc/rc.conf
file.
Modify it to your tastes, making sure that you set
rc_configured=YES
so that your changes will be enabled and a multi-user boot can
proceed.
Default values for the various programs can be found in
/etc/defaults/rc.conf,
where some in-line documentation may be found.
More complete documentation can be found in
rc.conf(5).
When you have finished editing
/etc/rc.conf,
type
exit
at the prompt to
leave the single-user shell and continue with the multi-user boot.
Other values that may need to be set in
/etc/rc.conf
for a networked environment are
hostname
and possibly
defaultroute.
You may also need to add an
ifconfig_int
for your
<int>
network interface,
along the lines of
ifconfig_le0="inet 192.0.2.123 netmask 255.255.255.0"
or, if you have
myname.my.dom
in
/etc/hosts:
ifconfig_le0="inet myname.my.dom netmask 255.255.255.0"
To enable proper hostname resolution, you will also want to add an
/etc/resolv.conf
file or (if you are feeling a little more adventurous) run
named(8).
See
resolv.conf(5)
or
named(8)
for more information.
Instead of manually configuring networking,
DHCP can be used by setting
dhcpcd=YES
in
/etc/rc.conf.
You will have to edit the
/etc/ttys
file.
If you don't have a Milan, you must disable the
ttyEx
devices.
For the Milan, you will have to disable the
ttyex
devices.
This is easy, just change 'on' to 'off' on the corresponding lines.
After reboot, you can log in as
root
at the login prompt.
If you didn't set a password in
sysinst,
there
is no initial password.
You should create an account for yourself (see below) and protect it and the
``root''
account with good passwords.
By default, root login from the network is disabled (even via
ssh(1)).
One way to become root over the network is to log in as a different
user that belongs to group
``wheel''
(see
group(5))
and use
su(1)
to become root.
Use the
useradd(8)
command to add accounts to your system.
Do not
edit
/etc/passwd
directly! See
vipw(8)
and
pwd_mkdb(8)
if you want to edit the password database.
If you installed the X Window System, you may want to read the chapter about X in the NetBSD Guide:
If you wish to install any of the software freely available for UNIX-like systems you are strongly advised to first check the NetBSD package system, pkgsrc. pkgsrc automatically handles any changes necessary to make the software run on NetBSD. This includes the retrieval and installation of any other packages the software may depend upon.
atari/10.1/All
subdir.
If you installed
pkgin(1)
in the
sysinst
post-installation configuration menu, you can use it to automatically install
binary packages over the network.
Assuming that
/usr/pkg/etc/pkgin/repositories.conf
is correctly configured, you can install them with the following commands:
# pkgin install tcsh bash perl apache xfce4 firefox ...
The above command will install the Tenex-csh and Bourne Again shells, the Perl programming language, Apache web server, Xfce desktop environment and the Firefox web browser as well as all the packages they depend on.
If it was not automatically installed,
pkgin(1)
can be installed on a fresh
NetBSD
system with
pkg_add(1):
export PKG_PATH=https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/$(uname -p)/$(uname -r | cut -d_ -f1)/All pkg_add pkgin
pkgsrc(7)
framework for compiling packages and did not install it from the
sysinst(8)
post-installation configuration menu, you can obtain it by retrieving
the file
/usr/pkgsrc
(though other locations work fine) with the commands:
# cd /usr
# tar -zxpf pkgsrc.tar.gz
After extracting, see the
doc/pkgsrc.txt
file in the extraction directory (e.g.,
/usr/pkgsrc/doc/pkgsrc.txt)
for more information.
/etc/mail/aliases
to forward root mail to the right place.
Don't forget to run
newaliases(1)
afterwards.
/etc/rc.local
to run any local daemons you use.
/etc
files are documented in section 5 of the manual; so just invoking
# man 5 filename
is likely to give you more information on these files.
The easiest way to upgrade to NetBSD 10.1 is with binaries, and that is the method documented here.
To do the upgrade, you must first boot the system as described in the Booting the installer section. You must also have at least the base and kern binary distribution sets available. Finally, you must have sufficient disk space available to install the new binaries. Since files already installed on the system are overwritten in place, you only need additional free space for files which weren't previously installed or to account for growth of the sets between releases.
Since upgrading involves replacing the kernel, boot blocks, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to back up any important data on the NetBSD partition or on another operating system's partition on your disk before beginning the upgrade process.
The upgrade procedure is similar to an installation, but without the hard disk partitioning.
Fetching the binary sets is done in the same manner as the installation procedure; refer to the installation part of the document for help. File systems are checked before unpacking the sets.
After a new kernel has been copied to your hard disk, your
machine is a complete
NetBSD
10.1
system.
However, that doesn't mean that you're finished with the upgrade process.
You will probably want to update the set of device nodes you have in
/dev.
If you've changed the contents of
/dev
by hand, you will need to be careful about this, but if
not, you can just cd into
/dev,
and run the command:
# sh MAKEDEV all
sysinst
will attempt to merge the settings stored in your
/etc
directory with the new version of
NetBSD
using the
postinstall(8)
utility.
However,
postinstall(8)
is only able to deal with changes that are easily automated.
It is recommended that you use the
etcupdate(8)
tool to merge any remaining configuration changes.
Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD 10.1.
Note that sysinst will automatically invoke
postinstall fix
In
NetBSD9
and earlier, filesystems listed in
/etc/fstab
would be mounted before non-legacy
zfs
filesystems. Starting from
NetBSD10
this order has been reversed.
If you have ever run a version of NetBSD-current between April 18, 2020 and September 23, 2022 (the version numbers used in the affected time range are between 9.99.56 and 9.99.106) your FFS file systems might have broken extended attributes stored.
You should follow this guide before booting the updated system multi-user for the first time.
Note that you do not need to do anything special if you never did run any affected kernel, especially if you have never run NetBSD-current.
The display drivers used for modern GPUs and the whole subsystem supporting it (DRM/KMS) have been updated to a newer version. Unfortunately not all issues with this have been resolved before the NetBSD10.0 release. You can find a list of issues in the Open issues with new DRM/KMS section of the release engineering wiki page.
A number of things have been removed from the NetBSD 10.1 release. See the ``Components removed from NetBSD'' section near the beginning of this document for a list.
Documentation is available if you installed the manual
distribution set.
Traditionally, the
``man pages''
(documentation) are denoted by
`name(section)'.
Some examples of this are
intro(1),
man(1),
apropos(1),
passwd(1),
and
passwd(5).
The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8.
The man command is used to view the documentation on a topic, and is started by entering man [section] topic. The brackets [] around the section should not be entered, but rather indicate that the section is optional. If you don't ask for a particular section, the topic with the lowest numbered section name will be displayed. For instance, after logging in, enter
# man passwd
to read the documentation for
passwd(1).
To view the documentation for
passwd(5),
enter
# man 5 passwd
instead.
If you are unsure of what man page you are looking for, enter
# apropos subject-word
where subject-word is your topic of interest; a list of possibly related man pages will be displayed.
If you've got something to say, do so!
We'd like your input.
There are various mailing lists available via the mailing list
server at
majordomo@NetBSD.org.
See
https://www.NetBSD.org/mailinglists/
for details.
There are various mailing lists set up to deal with comments and questions about this release. Please send comments to: netbsd-comments@NetBSD.org.
To report bugs, use the
send-pr(1)
command shipped with
NetBSD,
and fill in as much information about the problem as you can.
Good bug reports include lots of details.
Bugs also can be submitted and queried with the web interface at
https://www.NetBSD.org/support/send-pr.html
There are also port-specific mailing lists, to discuss aspects of
each port of
NetBSD.
Use majordomo to find their addresses, or visit
https://www.NetBSD.org/mailinglists/
If you're interested in doing a serious amount of work on a specific port, you probably should contact the `owner' of that port (listed below).
If you'd like to help with NetBSD, and have an idea as to how you could be useful, send us mail or subscribe to: netbsd-users@NetBSD.org.
As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP or WWW somewhere, then mail the appropriate list about it. If you'd rather not do that, mail the list saying you'll send the data to those who want it.
Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick
for their work on BSD systems, support, and encouragement.
All product names mentioned herein are trademarks or registered trademarks of their respective owners.
The following notices are required to satisfy the license terms of the software that we have mentioned in this document:
NetBSD is a registered trademark of The NetBSD Foundation, Inc.
In the following statement, the phrase ``this text'' refers to portions
of the system documentation.
Portions of this text are reprinted and reproduced in electronic form in
NetBSD, from IEEE Std 1003.1, 2004 Edition, Standard for
Information Technology -- Portable Operating System Interface (POSIX),
The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the
Institute of Electrical and Electronics Engineers, Inc and The Open Group.
In the event of any discrepancy between these versions and the original
IEEE and The Open Group Standard, the original IEEE and The Open Group
Standard is the referee document.
The original Standard can be obtained online at
http://www.opengroup.org/unix/online.html.
This notice shall appear on any product containing this material.
In the following statement, "This software" refers to the parallel port driver:
Some files have the following copyright:
Permission to use, copy, modify and distribute this software and its
documentation is hereby granted, provided that both the copyright
notice and this permission notice appear in all copies of the
software, derivative works or modified versions, and any portions
thereof, and that both notices appear in supporting documentation.
CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS
CONDITION. CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND FOR
ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
Carnegie Mellon requests users of this software to return to
any improvements or extensions that they make and grant Carnegie the
rights to redistribute these changes.
Some files have the following copyright:
Author: Chris G. Demetriou
Permission to use, copy, modify and distribute this software and
its documentation is hereby granted, provided that both the copyright
notice and this permission notice appear in all copies of the
software, derivative works or modified versions, and any portions
thereof, and that both notices appear in supporting documentation.
Carnegie Mellon requests users of this software to return to
any improvements or extensions that they make and grant Carnegie the
rights to redistribute these changes.
Some files have the following copyright:
Permission to use, copy, modify, and distribute this
software and its documentation for any purpose and without
fee is hereby granted, provided that the above copyright
notice appear in all copies. Stanford University
makes no representations about the suitability of this
software for any purpose. It is provided "as is"
without express or implied warranty.
Copyright (c) 1991,1990,1989 Carnegie Mellon University
All Rights Reserved.
Software Distribution Coordinator or Software.Distribution@CS.CMU.EDU
School of Computer Science
Carnegie Mellon University
Pittsburgh PA 15213-3890
All rights reserved.
CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS"
CONDITION. CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND
FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
Software Distribution Coordinator or Software.Distribution@CS.CMU.EDU
School of Computer Science
Carnegie Mellon University
Pittsburgh PA 15213-3890