INSTALLATION NOTES for OpenBSD/loongson 7.6


What is OpenBSD?
----------------

OpenBSD is a fully functional, multi-platform UN*X-like Operating
System based on Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite.
There are several operating systems in this family, but OpenBSD
differentiates itself by putting security and correctness first.  The
OpenBSD team strives to achieve what is called a "secure by default"
status.  This means that an OpenBSD user should feel safe that their
newly installed machine will not be compromised.  This "secure by
default" goal is achieved by taking a proactive stance on security.

Since security flaws are essentially mistakes in design or implement-
ation, the OpenBSD team puts as much importance on finding and fixing
existing design flaws and implementation bugs as it does writing new
code.  This means that an OpenBSD system will not only be more secure,
but it will be more stable.  The source code for all critical system
components has been checked for remote-access, local-access, denial-
of-service, data destruction, and information-gathering problems.

In addition to bug fixing, OpenBSD has integrated strong cryptography
into the base system.  A fully functional IPsec implementation is
provided as well as support for common protocols such as SSL and SSH.
Network filtering and monitoring tools such as packet filtering, NAT,
and bridging are also standard, as well as several routing services,
such as BGP and OSPF.  For high performance demands, support for
hardware cryptography has also been added to the base system.  Because
security is often seen as a tradeoff with usability, OpenBSD provides
as many security options as possible to allow the user to enjoy secure
computing without feeling burdened by it.

Because OpenBSD is from Canada, the export of Cryptography pieces
(such as OpenSSH and IPsec) to the world is not restricted.

(NOTE: OpenBSD can not be re-exported from the US once it has entered
the US.  Because of this, take care NOT to get the distribution from
a mirror server in the US if you are outside of Canada and the US.)

A list of software and ideas developed by the OpenBSD project is
available on the web at https://www.OpenBSD.org/innovations.html.

A comprehensive list of the improvements brought by the 7.6 release
is also available at https://www.OpenBSD.org/76.html.

OpenBSD/loongson runs on various Loonson processor-based systems, such
as the popular Lemote Yeeloong and Gdium Liberty netbooks, as well as
the Lemote Fuloong 2F mini PC and the Lemote Lynloong all-in-one PC.


Sources of OpenBSD:
-------------------

Please refer to https://www.openbsd.org/ftp.html for all the ways you may
acquire OpenBSD.


OpenBSD 7.6 Release Contents:
-----------------------------

The OpenBSD 7.6 release is organized in the following way.  In the
.../7.6 directory, for each of the architectures having an OpenBSD 7.6
binary distribution, there is a sub-directory.

The loongson-specific portion of the OpenBSD 7.6 release is found in the
"loongson" subdirectory of the distribution.  That subdirectory is laid
out as follows:

.../7.6/loongson/

	INSTALL.loongson	Installation notes; this file.

	SHA256		Output of the cksum(1) program using the option
			-a sha256, usable for verification of the
			correctness of downloaded files.

	SHA256.sig	The above file, signed with the OpenBSD signing key
			for the 7.6 release, usable for verification of the
			integrity of the above file, and thus of the
		        downloaded files.

	*.tgz		loongson binary distribution sets; see below.

	bsd		A stock GENERIC loongson kernel which will be
			installed on your system during the install.

	bsd.mp		A stock GENERIC.MP loongson kernel, with support for
			multiprocessor machines, which can be used instead
			of the GENERIC kernel after the install.

	bsd.rd		A compressed RAMDISK kernel; the embedded
			filesystem contains the installation tools.
			Used for simple installation from a pre-existing
			system.

	cd76.iso	A simple bootable filesystem image consisting of the
			bsd.rd installation kernel, suitable to be used
			as a bootable CD-ROM image, but will require the base
			and X sets be found via another media or network.

	miniroot76.img	A miniroot filesystem image to be used if you
			for some reason can't or don't want to use the
			ramdisk installation method.

	boot		The OpenBSD/loongson bootloader.

The OpenBSD/loongson binary distribution sets contain the binaries which
comprise the OpenBSD 7.6 release for loongson systems.  There are eight
binary distribution sets.  The binary distribution sets can be found in
the "loongson" subdirectory of the OpenBSD 7.6 distribution tree,
and are as follows:

	base76	 The OpenBSD/loongson 7.6 base binary distribution.  You MUST
		 install this distribution set.  It contains the base OpenBSD
		 utilities that are necessary for the system to run and be
		 minimally functional.  This includes parts of the toolchain
		 required to relink a kernel.
		 It includes shared library support, and excludes everything
		 described below.
		 [ 138.7 MB gzipped, 434.9 MB uncompressed ]

	comp76	 The OpenBSD/loongson Compiler tools.  All of the tools relating
		 to C and C++ are supported.  This set includes the system
		 include files (/usr/include), the compiler
		 toolchain, 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.
		 [ 62.3 MB gzipped, 260.1 MB uncompressed ]

	game76	 This set includes the games and their manual pages.
		 [ 2.7 MB gzipped, 7.2 MB uncompressed ]

	man76	 This set includes all of the manual pages for the binaries
		 and other software contained in the base set.
		 Note that it does not include any of the manual pages
		 that are included in the other sets.
		 [ 7.6 MB gzipped, 29.5 MB uncompressed ]

	xbase76  This set includes the base X distribution.  This includes
		 programs, headers and libraries.
		 [ 46.7 MB gzipped, 173.5 MB uncompressed ]

	xfont76  This set includes all of the X fonts.
		 [ 22.4 MB gzipped, 34.1 MB uncompressed ]

	xserv76  This set includes all of the X servers.
		 [ 10.5 MB gzipped, 40.6 MB uncompressed ]

	xshare76 This set includes all text files equivalent between all
		 architectures.
		 [ 4.4 MB gzipped, 23.8 MB uncompressed ]



OpenBSD System Requirements and Supported Devices:
--------------------------------------------------

The following machines are supported by OpenBSD/loongson:

	Lemote Fuloong 2F
	  onboard serial port, audio, USB and Ethernet are supported;
	  onboard display is only supported in the video mode setup by
	  the firmware (usually 640x400x8), without acceleration.

	Lemote Lynloong (LM9001 and LM9002 models)
	  onboard audio, USB and Ethernet are supported;
	  onboard display is only supported in the 1368x768x16 video mode
	  set up by the firmware, without acceleration.

	Lemote Yeeloong (8.9" and 10.1" models)
	  all onboard devices (keyboard, trackpad, display, SD card reader,
	  USB ports, Ethernet adapter, wireless network adapter, audio,
	  webcam on the 8.9" model, battery and power information) are
	  supported.

	Gdium Liberty 1000
	  all onboard devices (keyboard, trackpad, display, SD card reader,
	  USB ports, Ethernet adapter, wireless network adapter,
	  battery information) are supported except for the audio controller.



Verifying the OpenBSD Installation Media:
-----------------------------------------

OpenBSD installations are able to verify files for the next
release.  The OpenBSD 7.6 release was signed with the
/etc/signify/openbsd-76-base.pub release key.

If you have an existing OpenBSD installation, you can run signify(1)
to verify the signature and checksum.  For example, run the following
to verify that the cd76.iso file was distributed by the OpenBSD team:
	signify -C -p /etc/signify/openbsd-76-base.pub -x SHA256.sig cd76.iso

If you are unable to run or compile signify(1), use sha256(1) with the SHA256
file to see if a file was corrupt during the transfer.


Getting the OpenBSD System onto Useful Media:
---------------------------------------------

Installation is supported from several media types, including:

	CD-ROM
	FFS partitions
	DOS (FAT) partitions
	EXT2 partitions
	Remote NFS partition
	HTTP

The steps necessary to prepare the distribution sets for installation
depend on which method of installation you choose.  Some methods
require a bit of setup first that is explained below.

The installation allows installing OpenBSD directly from HTTP mirror
sites over the internet, however you must consider the speed and
reliability of your internet connection for this option.  It may save
much time and frustration to download the distribution sets to a local
server or disk and perform the installation from there, rather than
directly from the internet.

The variety of options listed may seem confusing, but situations vary
widely in terms of what peripherals and what sort of network arrangements
a user has, the intent is to provide some way that will be practical.

To install OpenBSD using a remote partition, mounted via
NFS, you must do the following:

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

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

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

	Once the NFS server is set up properly and you have the
	information mentioned above, you can proceed to the next
	step in the installation or upgrade process.

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

	Place the distribution sets you wish to upgrade somewhere
	in your current file system tree.  At a bare minimum, you
	must upgrade the "base" binary distribution, and so must
	put the "base76" set somewhere in your file system.  It
	is recommended that you upgrade the other sets, as well.



Preparing your System for OpenBSD Installation:
-----------------------------------------------

Most loongson systems are shipped with a Linux system installed on the disk
drive or SSD.  This system will likely use two partitions, one for the
system and applications, and another for the user data. OpenBSD will in turn
need its own MBR partition.

If there is no unpartitioned space left on the disk, it will be necessary to
shrink and recreate the data partition; before installing OpenBSD/loongson,
you should make sure any important data on this partition is backed up.

If you intend to only use OpenBSD on your machine, please note that, at this
point, it is necessary to keep an ext2 or ext3 Linux partition, to be able
to boot the system.

Before you install your system, you should familiarize yourself with PMON,
the open source firmware and bootloader of your machine.

Entering PMON:

    Upon power-up, or after a reset, a splash screen is displayed while PMON
    initializes.

    On Lemote systems, after PMON initializes, a text mode boot menu appears.
    At this menu, you can either select one of the systems to boot with the
    arrows keys and press enter, or abort the countdown sequence and get to
    the PMON commandline by hitting `c'.

    If you have set up your machine to automatically boot into OpenBSD,
    and want to enter PMON, you should press the `Del' key or
    `ESC [ G' if you are using a serial console. You must have attached a
    VGA monitor for the last step, as the commands you type on the console,
    will show up on the VGA monitor.

    On Gdium systems, the system proceeds to immediately boot into the
    operating system; to enter PMON, repeatedly press the `del' key
    (on the top right corner of the keyboard) before the G-Key lits,
    until the splash screen disappears and a PMON prompt appears.

    PMON command are entered at the ``PMON>'' prompt; you may correct typos
    using the backspace key, and retrieve previous commands from the history
    using Ctrl-P. On Lemote systems, unfortunately, there is no cursor shape
    displayed, which can make command line editing quite tedious.

PMON file path concepts:

    The filenames used by PMON always mention explicitly the location of
    the filesystem they refer to, as well as the filesystem type. They
    are constructed as
    	/dev/fs/<filesystem type>@<device name>/<path within the filesystem>

    On Lemote systems, the internal storage (either a disk drive or an SSD)
    is `wd0'. On the Gdium Liberty, the G-Key slot is `usbg0'. Other devices
    connected to the USB ports are named `usb0', `usb1', etc, in the order
    PMON configures them. At any time the ``devls'' command will list
    the devices you can boot from. Note that it is not possible to boot from
    the SD card reader.

    Supported filesystems are `ext2', for Linux ext2 and ext3 filesystem
    partition, and `iso9660' for CD-ROM.

    As an example, the /boot/vmlinux file on the first partition of the
    hard disk becomes:
	/dev/fs/ext2@wd0/boot/vmlinux



Installing the OpenBSD System:
------------------------------

Installing OpenBSD is a relatively simple process. If you take your time
and are careful to read the information presented by the installer, you
shouldn't have any trouble.

Booting the installation media:

The easiest way to boot into the OpenBSD installer is to copy the miniroot
image to a USB stick using dd(1) and boot bsd.rd from the PMON prompt:

    PMON> boot -k /dev/fs/ext2@usb0/bsd.rd

on Lemote systems, and

    PMON> load /dev/fs/ext2@usb0/bsd.rd
    PMON> g

on Gdium systems.

Another way to boot into the OpenBSD installer is to copy the bsd.rd
installation kernel to the main Linux partition, and boot from it.

Assuming the installation kernel has been copied to /boot/bsd.rd on the
Linux system, at the PMON prompt, enter

    PMON> boot -k /dev/fs/ext2@wd0/boot/bsd.rd

on Lemote systems, and

    PMON> load /dev/fs/ext2@usbg0/boot/bsd.rd
    PMON> g

on Gdium systems.

Netbooting the installation kernel can be done as well. First, check the name
of the PMON device for the onboard interface using the ``devls'' command.
This is likely to be either rtl0 (on Yeeloong) or rtk0 (on Fuloong). Then,
assign it an address and fetch the installation kernel from a tftp server:

    PMON> ifaddr <device name> <your ip>
    PMON> boot -k tftp://<server ip>/bsd.rd

You should now be ready to install OpenBSD.

The following is a walk-through of the steps you will take while getting
OpenBSD installed on your hard disk.

The installation procedure is designed to gather as much information about
your system setup as possible at the beginning, so that no human interaction
is required as soon as the questions are over.

The order of these questions might be quite disconcerting if you are used to
other installation procedures, including older OpenBSD versions.

If any question has a default answer, it will be displayed in brackets ("[]")
after the question.  If you wish to stop the installation, you may hit
Control-C at any time, but if you do, you'll have to begin the installation
process again from scratch.  Using Control-Z to suspend the process may be a
better option, or at any prompt enter "!" to get a shell, from which "exit"
will return you back to that prompt.


	Once the kernel has loaded, you will be presented with the
	OpenBSD kernel boot messages which contain information about
	the hardware that was detected and supported by OpenBSD.

	After the kernel is done initializing, you will be asked whether
	you wish to do an "(I)nstall", "(U)pgrade" or an "(A)utoinstall".
	Enter "I" for a fresh install or "U" to upgrade an existing
	installation.  Enter "A" to start an unattended installation
	where all of your answers are supplied in a response file (more
	on that in "Preparing an unattended installation of OpenBSD").

	If you are connected with a serial console, you will next be
	asked for your terminal type.
	You should choose the terminal type from amongst those listed.
	(If your terminal type is xterm, just use vt220).

	If you are connected using a glass console, you will next be
	asked for your keyboard layout (the default being the US QWERTY
	layout).  Depending on your keyboard type, not all international
	layouts may be supported; answering "?" (which, on QWERTY layouts,
	is the key to the left of the right "shift" key, shifted) will
	display a list of supported layouts.
	(If you do not need to change the keyboard layout, just press
	enter.)

	The first question you will be asked is the system hostname.
	Reply with the name of the system, without any domain part.

	You will now be given an opportunity to configure the network.
	The network configuration you enter (if any) can then be used to
	do the install from another system using HTTP, and will also be
	the configuration used by the system after the installation is
	complete.

	The install program will give you a list of network interfaces you
	can configure.  For each network interface you select to configure,
	you will be asked for:

	- the symbolic host name to use (except for the first
	  interface setup, which will reuse the host name entered at the
	  beginning of the installation).

	- the IPv4 settings: address and netmask.  If the IP address
	  should be obtained from a DHCP server, simply enter "dhcp"
	  when asked for the address.

	- the IPv6 settings (address, prefix length, and default router).
	  You may enter "autoconf" when asked for the address for the
	  interface to configure automatically via router solicitation
	  messages.

	After all interfaces have been configured, if there have been
	any IPv4 interfaces set up, you will be asked for the IPv4 default
	route.  This step is skipped if you only have one IPv4 interface
	setup, and it is configured with DHCP.

	The install program will also ask you for your DNS domain name,
	and the domain name servers, unless this information has
	already been obtained from a DHCP server during interface setup.

	You will then be asked to enter the initial root password
	of the system, twice.

	Although the install program will only check that the two
	passwords match, you should make sure to use a strong password.
	As a minimum, the password should be at least eight characters
	long and a mixture of both lower and uppercase letters, numbers
	and punctuation characters.

	You will then be asked whether you want to start sshd(8) by
	default.

	You will now be given the possibility to set up a user account
	on the forthcoming system.  This user will be added to the
	"wheel" group.

	Enter the desired login name, or "n" if you do not want to
	add a user account at this point.  Valid login names are
	sequences of digits and lowercase letters, and must start
	with a lowercase letter.  If the login name matches this
	criteria, and doesn't conflict with any of the administrative
	user accounts (such as "root", "daemon" or "ftp"), you
	will be prompted for the user's descriptive name, as well
	as its password, twice.

	As for the root password earlier, the install program will only
	check that the two passwords match, but you should make sure to
	use a strong password here as well.

	If you have chosen to set up a user account, and you had chosen
	to start sshd(8) on boot, you will be asked if you want to allow
	sshd(8) logins as root.

	Depending on the installation media you are using, you may now
	be given the opportunity to configure the time zone your system
	will use.  If the installation program skips this question, do
	not be alarmed: the time zone will be configured at the end of
	the installation.
	The installation program will now tell you which disks it can
	install on, and ask you which it should use.

	Reply with the name of your root disk.

	Disks on OpenBSD/loongson are partitioned using either "MBR"
	or "GPT" partitioning schemes.  You will need to create one
	disk partition in which the OpenBSD filesystems will be created.


	The fdisk(8) utility will be invoked to let you edit your MBR
	partitioning.  The current MBR partitions defined will be
	displayed and you will be allowed to modify them, and add new
	partitions.

	The setup will need one 'Linux files' partition and an 'OpenBSD'
	partition. If you use the whole disk option, the install script
	will create a small 'Linux files' partition and use the rest of
	the disk for the OpenBSD installation.

	After your OpenBSD MBR partition has been set up, the real
	partition setup can follow.

	The file system layout is stored in the OpenBSD disk label. Each
	file system is stored in its own "disk label partition", which
	is a subdivision of the OpenBSD disk partition you created. In
	the text below, "partition" refers to these subdivisions.

	You will be shown a default layout with the recommended file
	systems. This default layout is based on the disk size.

	You will be given the choice of accepting the proposed layout,
	editing it, or creating your own custom layout. These
	last two choices will invoke the disklabel(8) interactive editor,
	allowing you to create your desired layout.

	Within the editor, you will see at least a "c" partition of
	fstype "unused". This represents the whole disk and cannot be
	modified.
	Linux partitions defined on the disk will usually show up as
	partition 'i', 'j' and so on.

	You must create partition "a" as a native OpenBSD partition, i.e.
	one with "4.2BSD" as the fstype, to hold the root file system.

	In addition to partition "a" you should create partition "b" with
	fstype "swap", and native OpenBSD partitions to hold separate file
	systems such as /usr, /tmp, /var, and /home.

	You will need to provide a mount point for all partitions you
	define.  Partitions without mount points, or not of the
	4.2BSD fstype, will neither be formatted nor mounted during the
	installation.

	For quick help while in the interactive editor, enter "?".
	The "z" command (which deletes all partitions and starts with a
	clean label), the "A" command (which performs the automatic
	partition layout) and the "n" command (to change mount points)
	are of particular interest.

	Although the partitions' position and size are written in exact
	sector values, you do not need a calculator to create your
	partitions!  Human-friendly units can be specified by adding "k",
	"m" or "g" after any numbers to have them converted to kilobytes,
	megabytes or gigabytes. Or you may specify a percentage of the
	disk size using "%" as the suffix.

	Enter "M" to view the entire manual page (see the info on the
	"-E" flag).  To exit the editor enter "q".

	After the layout has been saved, new filesystems will be
	created on all partitions with mount points.
	This will DESTROY ALL EXISTING DATA on those partitions.

	After configuring your root disk, the installer will
	return to the list of available disks to configure.

	You can choose the other disks to use with OpenBSD in
	any order, and will get to set up their layout similarly
	to the root disk above. However, for non-root disks,
	you will not be proposed a default partition layout.

	When all your disks are configured, simply hit return
	at the disk prompt.

	After these preparatory steps have been completed, you will be
        able to extract the distribution sets onto your system.  There
        are several install methods supported:
	HTTP, CD-ROM, or a local disk partition.

	To install via HTTP:
		To begin an HTTP install you will need the following
		pieces of information:
		1) Proxy server URL if you are using a URL-based HTTP
		   proxy (squid, CERN FTP, Apache 1.2 or higher).
		   You need to define a proxy if you are behind a
		   firewall that blocks outgoing HTTP connections
		   (assuming you have a proxy available to use).
		2) The IP address (or hostname if you configured
		   DNS servers earlier in the install) of an HTTP
		   server carrying the OpenBSD 7.6 distribution.
		   The installation program will try to fetch a list
		   of such servers; depending on your network settings,
		   this might fail.  If the list could be fetched, it
		   will be displayed, and you can choose an entry from
		   the list (the first entries are expected to be the
		   closest mirrors to your location).
		3) The directory holding the distribution sets.

		Then refer to the section named "installation set selection"
		below.

	To install from CD-ROM:
		When installing from a CD-ROM, you will be asked which
		device holds the distribution sets.  This will typically
		be "cd0".  If there is more than one partition on the
		CD-ROM, you will be asked which partition the distribution
		is to be loaded from.  This is normally partition "a".

		You will also have to provide the relative path to the
		directory on the CD-ROM which holds the distribution, for
		the loongson this is "7.6/loongson".

		Then refer to the section named "installation set selection"
		below.

	To install from an NFS mounted directory:
		When installing from an NFS-mounted directory, you must
		have completed network configuration above, and also
		set up the exported file system on the NFS server in
		advance.

		First you must identify the IP address of the NFS server
		to load the distribution from, and the file system the
		server expects you to mount.

		The install program will also ask whether or not TCP
		should be used for transport (the default is UDP).  Note
		that TCP only works with newer NFS servers.

		You will also have to provide the relative path to the
		directory on the file system where the distribution sets
		are located.  Note that this path should not be prefixed
		with a "/".

		Then refer to the section named "installation set selection"
		below.

	To install from a local disk partition:
		When installing from a local disk partition, you will
		first have to identify which disk holds the distribution
		sets.
		This is normally "wdN" or "sdN", where N is a number.
		Next you will have to identify the partition within that disk
		that holds the distribution; this is a single letter between
		"a" and "p".

		You will also have to identify the type of file system
		residing in the partition identified.  Currently, you can
		install from partitions that have been formatted as the
		Berkeley fast file system (ffs), Linux (ext2) or MS-DOS.

		You will also have to provide the relative path to the
		directory on the file system where the distribution sets
		are located.  Note that this path should not be prefixed
		with a "/".

		Then refer to the next section.

	Installation set selection:
		A list of available distribution sets found on the
		given location will be listed.

		You may individually select distribution sets to install
		by entering their names or wildcards (e.g. "*.tgz" or
		"base*|comp*"), or you may enter "all" to select all the
		sets (which is what most users will want to do).
		You may also enter "abort" to deselect everything and
		restart the selection from scratch, or unselect sets
		by entering their name prefixed with "-" (e.g. "-x*").

		It is also possible to enter an arbitrary filename and
		have it treated as a file set.

		When you are done selecting distribution sets, enter
		"done".  The files will begin to extract.

	After the files have been extracted, you will be given the choice
	to select a new location from which to install distribution sets.
	If there have been errors extracting the sets from the previous
	location, or if some sets have been missing, this allows you to
	select a better source.

	Also, if the installation program complains that the distribution
	sets you have been using do not match their recorded checksums, you
	might want to check your installation source (although this can
	happen between releases, if a snapshot is being updated on a mirror
	server with newer files while you are installing).

	The last thing you might need to configure, if you did not get
	the chance to earlier, is the time zone your system will be using.
	For this work properly, it is expected that you have installed at
	least the "base76" and "bsd" distribution sets.

	The installation program will then proceed to save the system
	configuration, create all the device nodes needed by the installed
	system, and will install bootblocks on the root disk.

	On multiprocessor systems, if the bsd.mp kernel has been installed,
	it will be renamed to "bsd", which is the default kernel the boot
	blocks look for.  The single processor kernel, "bsd", will be
	available as "bsd.sp".

	Finally, you will be asked whether you would like to install
	non-free firmware files (which can't be tightly integrated to
	the OpenBSD system) on first boot, by invoking fw_update(8) on
	the next boot.

Lemote systems final steps:

	Lemote systems ship with a boot menu.  After an installation
	preserving the Linux partitions is complete, you can add an OpenBSD
	entry to the boot menu to be able to boot OpenBSD more easily.

	The boot menu contents are found in /boot/boot.cfg on the Linux
	partition. To add an OpenBSD entry, simply add a new entry in the
	file, such as:

		title OpenBSD
			kernel /dev/fs/ext2@wd0/boot/boot
			args ""

	In the example above, /dev/fs/ext2@wd0/boot/boot is the PMON path
	to the OpenBSD bootloader, which is copied to that location by the
	install script.

	You may make OpenBSD the default option by changing the ``default''
	line near the top of the file. The value on this line is the index
	of the default entry, starting at zero. So if you added the OpenBSD
	entry as the fourth entry in the file, it would become the default
	choice with:

		default 3

	The timeout until the default choice is selected, in seconds, can
	be modified on the ``timeout'' line.

	However, due to side effects of PMON operation, automatic loading
	of OpenBSD binaries (bootloader or kernel) causes a register dump
	to be silently displayed by PMON; while it won't be visible on
	screen, PMON will gladly wait for user input to continue if it
	believes it has written too much output.

	To overcome this annoyance, simply change the `moresz' environment
	variable to a large value (30 or larger will do):

	    PMON> set moresz 30

	The bootloader will attempt to load the kernel file set in the `bsd'
	environment variable. Should this fail, it will wait for user
	commands. The value of `bsd' should be a path within the OpenBSD
	root filesystem on the disk, such as:

	    PMON> set bsd /bsd

	If you have removed the Linux installation or if you do not want to
	use the boot menu, you may simply disable it in the environment, and
	set the `al' variable to point to the bootloader path:

	    PMON> set ShowBootMenu no
	    PMON> set al /dev/fs/ext2@wd0/boot/boot

	Alternatively, you might want to create a /boot/boot.cfg file in the
	small Linux partition created by the installation.

	On the Fuloong 2F, getting PMON to use the serial console is tricky,
	due to PMON bugs and design decisions made by Lemote. PMON's default
	serial speed is 115200, and OpenBSD will also use that speed. By
	default, it is only possible to use serial input if no USB keyboard is
	attached. PMON will nevertheless display its output on the VGA display.
	To get full serial access, the first step is to boot into PMON> with
	both serial console and VGA display but no USB keyboard attached.
	You can type on the serial console, but output will be shown on the
	VGA display. Next enter the following commands:

	    PMON> set novga 1
	    PMON> set nokbd 1
	    PMON> set al ""
	    PMON> set ShowBootMenu no

	If you have a dual boot setup, mount the Linux boot partition and
	rename /boot/boot.cfg so that it does not get found by PMON. This
	will enable full serial access to PMON on the Fuloong 2F.

Gdium systems final steps:

	Gdium systems do not have a boot menu, and directly boot the system
	(Linux, by default). Unfortunately, the OpenBSD bootloader operation
	is very limited on this machine, as it can not access USB devices
	(which means no keyboard input as well).

	To overcome this and be able to boot OpenBSD nevertheless, the
	bootloader relies upon PMON's ability to load a Linux so-called
	``initrd'' image. By making PMON load the kernel as the ``initrd''i
	image, and then run the bootloader, the bootloader will be able to
	``load'' the OpenBSD kernel correctly.

	The path to the file booted by default is set in the `al' environment
	variable, and the path to the initrd image is set in the `rd'
	environment variable.

	To boot the bsd kernel on the G-Key by default, assuming it has been
	copied to /boot/bsd on the first ext3 partition, and the bootloader
	has been copied to /boot/boot on the same filesystem, the settings
	are:

	    PMON> set al /dev/fs/ext2@usbg0/boot/boot
	    PMON> set rd /dev/fs/ext2@usbg0/boot/bsd

	Alternatively, you can disable autoboot by removing this variable:

	    PMON> unset al


Congratulations, you have successfully installed OpenBSD 7.6.  When you
reboot into OpenBSD, you should log in as "root" at the login prompt.
You should create yourself an account, if you skipped this step during
installation, and protect it and the "root" account with good passwords.

The install program leaves root an initial mail message.  We recommend
you read it, as it contains answers to basic questions you might have
about OpenBSD, such as configuring your system, installing packages,
getting more information about OpenBSD, sending in your dmesg output
and more.  To do this, run

	mail

and then just enter "more 1" to get the first message.  You quit mail by
entering "q".

Some of the files in the OpenBSD 7.6 distribution might need to be
tailored for your site.  We recommend you run:

	man afterboot

which will tell you about a bunch of the files needing to be reviewed.
If you are unfamiliar with UN*X-like system administration, it's
recommended that you buy a book that discusses it.



Preparing an unattended installation of OpenBSD:
------------------------------------------------

If "(A)utoinstall" is chosen at the install prompt or if the
installation system detects that it booted from the network, and
isn't interrupted within 5 seconds, it attempts a fully-automatic
installation.

The installer autoconfigures a DHCP IPv4 address on the network interface the
system booted from, or in case of multiple interfaces it will ask which one
to use. Upon success, it retrieves a response file via HTTP. If that
fails, the installer asks for the response file location, which can be
either a URL or a local path, and retrieves the response file from
there.

The "next-server" DHCP option specifies the hostname part of the URL,
as in "http://<next-server>/install.conf".  The "filename" DHCP
parameter specifies the installer mode, e.g. "auto_install".  On
architectures where this parameter is used for netbooting, create
a symbolic link named "auto_install" pointing to the boot program.

The response file contains lines with key/value pairs separated by
an equals sign "=", where the key is a non-ambiguous part (up to the
question mark) of the installer question, consisting of whitespace
separated words. The value is what would have been entered at the
interactive prompt. Empty lines and lines beginning with a "#"
character are ignored. The installer uses default answers in case
of missing answers.

Here is a response file example that uses a hashed password (see
encrypt(1) for more details) for root and a public ssh key for the
user that is created during the installation.

           System hostname = openbsd
           Password for root = $2a$14$Z4xRMg8vDpgYH...GVot3ySoj8yby
           Setup a user = puffy
           Password for user = *************
           Public ssh key for user = ssh-ed25519 AAAAC3NzaC1...g3Aqre puffy@ai
           What timezone are you in = Europe/Stockholm
           Location of sets = http
           HTTP Server = ftp.eu.openbsd.org

The "System hostname" key above matches the following full question
asked during an interactive installation:

  System hostname? (short form, e.g. 'foo')

While the installation is in progress the installer writes all output
to the file /ai.log, which is available as mail on the freshly
installed system after the initial reboot.  If the installation is
successful the system will reboot automatically; otherwise, you will
be dropped back into the shell where you can look at the /ai.log file
or try again.





Upgrading a previously-installed OpenBSD System:
------------------------------------------------

Warning! Upgrades to OpenBSD 7.6 are currently only supported from the
immediately previous release.  The upgrade process will also work with older
releases, but might not execute some migration tasks that would be necessary
for a proper upgrade.

The best solution, whenever possible, is to backup your data and reinstall
from scratch. As a minimum, if the toolchain (the "comp" set) was installed,
you should remove all files within /usr/include before attempting to
upgrade.

To upgrade OpenBSD 7.6 from a previous version, start with the general
instructions in the section "Installing OpenBSD".

Boot from your usual boot device.
When prompted, select the (U)pgrade option rather than the (I)nstall
option at the prompt in the install process.

You will be presented with a welcome message, and depending on how you are
connected to the system, you will be asked to set the terminal type or to
choose a keyboard layout.

The upgrade script will ask you for the existing root partition, and
will use the existing filesystems defined in /etc/fstab to install the
new system in.  It will also use your existing network parameters.

From then, the upgrade procedure is very close to the installation
procedure described earlier in this document.

However, it is strongly advised that you unpack the etc.tgz and the
xetc.tgz files found in /var/sysmerge in a temporary
directory and merge changes by hand, or with the help of the sysmerge(8)
helper script, since all components of your system may not function
correctly until your files in "/etc" are updated.



Getting source code for your OpenBSD System:
--------------------------------------------

Now that your OpenBSD system is up and running, you probably want to get
access to source code so that you can recompile pieces of the system.

You can get the pieces over the internet using anonymous CVS, rsync,
FTP or HTTP(s). For more information, see:

	https://www.OpenBSD.org/anoncvs.html
	https://www.OpenBSD.org/ftp.html


Using online OpenBSD documentation:
-----------------------------------

Documentation is available if you first install the manual pages
distribution set.  Traditionally, the UN*X "man pages" (documentation)
are denoted by "name(section)".  Some examples of this are

	intro(1),
	man(1),
	apropos(1),
	passwd(1),
	passwd(5) and
	afterboot(8).

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
least-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.


Adding third party software - packages and ports:
--------------------------------------------------------

As complete as your OpenBSD system is, you may want to add any of several
excellent third party software applications.  There are several ways to do
this.  You can:

1) Use the OpenBSD package collection to grab a pre-compiled
   and tested version of the application for your hardware.

2) Use the OpenBSD ports collection to automatically get any
   needed source file, apply any required patches, create the
   application, and install it for you.

3) Obtain the source code and build the application based
   upon whatever installation procedures are provided with the
   application.

Instructions for installing applications from the various sources using
the different installation methods follow.

You should also refer to the packages(7) manual page.

Installing applications from the ftp.OpenBSD.org package collection:

	All available packages for your architecture have been placed on
	ftp.OpenBSD.org in the directory pub/OpenBSD/7.6/packages/mips64el/
	You may want to peruse this to see what packages are available.  The
	packages are also on the OpenBSD mirror sites.  See

		https://www.OpenBSD.org/ftp.html

	for a list of current mirror sites.

	Installation of a package is very easy.
	1) become the superuser (root)
	2) use the "pkg_add" command to install the software

	"pkg_add" is smart enough to know how to download the software
	from the OpenBSD HTTP server.  Example:

    $ su
    Password: <enter your root password>
    # pkg_add emacs

Installing applications from the OpenBSD ports collection:

	See https://www.openbsd.org/faq/faq15.html#Ports for current
	instructions on obtaining and installing OpenBSD ports.

	You should also refer to the ports(7) manual page.

Installing other applications:

	If an OpenBSD package or port does not exist for an application
	you're pretty much on your own.  The first thing to do is ask
	<ports@OpenBSD.org> if anyone is working on a port -- there may
	be one in progress.  If no such port exists, you might want to
	look at the FreeBSD ports or NetBSD pkgsrc for inspiration.

	If you can't find an existing port, try to make your own and
	feed it back to OpenBSD.  That's how our ports collection grows.
	Some details can be found in the OpenBSD Porter's Handbook at
	https://www.openbsd.org/faq/ports/
	with more help coming from the mailing list, <ports@OpenBSD.org>.



Administrivia:
--------------

There are various mailing lists available via the mailing list
server at <majordomo@OpenBSD.org>.  To get help on using the mailing
list server, send mail to that address with an empty body, and it will
reply with instructions.

More information about the various OpenBSD mailing list and proper
netiquette is available at

	https://www.OpenBSD.org/mail.html

To report bugs, use the "sendbug" command shipped with OpenBSD,
and fill in as much information about the problem as you can.  Good
bug reports include lots of details.  Additionally, bug reports can
be sent by mail to:

	bugs@OpenBSD.org

As a favor, please avoid mailing huge documents or files to the
mailing lists.  Instead, put the material you would have sent on
a web server, then mail the appropriate list about it, or if
you'd rather not do that, mail the list saying you'll send the data
to those who want it.

For more information about reporting bugs, see

	https://www.OpenBSD.org/report.html