Ergebnis für URL: http://www.openbsd.org/faq/faq4.html#Download[1]OpenBSD FAQ - Installation Guide [2][FAQ Index]
____________________________________________________________________________
* [3]Overview of the Installation Procedure
* [4]Pre-Installation Checklist
* [5]Downloading OpenBSD
* [6]Creating Install Media
* [7]Performing a Simple Install
* [8]File Sets
* [9]Disk Partitioning
* [10]Bootstrapping Wireless Firmware
* [11]Sending Your dmesg After the Install
* [12]Customizing the Install Process
* [13]Multibooting
____________________________________________________________________________
Overview of the Installation Procedure
The OpenBSD installer uses a special ramdisk kernel (bsd.rd) that spawns a live
environment running entirely in memory. It contains the install script and a
small number of utilities needed to perform a complete installation. These
utilities can also be useful for disaster recovery.
The ramdisk kernel can be booted from a number of different sources:
* CD/DVD
* USB drive
* An existing partition
* Over the network ([14]PXE or other [15]network boot options)
* Floppy disk
Not every [16]platform supports all of these options.
If you have a running OpenBSD system, bsd.rd is all you need to reinstall or
upgrade to a newer version. To do so, [17]download and verify the new bsd.rd,
place it on an existing filesystem, and boot from it. The general method of
booting bsd.rd is to change your boot kernel from /bsd to /bsd.rd through
whatever means used on your platform.
Booting from bsd.rd on an amd64 system can be done like so:
Using drive 0, partition 3.
Loading......
probing: pc0 com0 com1 mem[638K 1918M a20=on]
disk: hd0+ hd1+
>> OpenBSD/amd64 BOOT 3.33
boot> bsd.rd
This will boot the kernel named bsd.rd from the first partition of the first
recognized hard disk.
If you need to specify a different drive or partition, just prefix the kernel
name with its location. The following example would boot from the fourth
partition of the second hard drive:
Using drive 0, partition 3.
Loading......
probing: pc0 com0 com1 mem[638K 1918M a20=on]
disk: hd0+ hd1+
>> OpenBSD/amd64 BOOT 3.33
boot> boot hd1d:/bsd.rd
OpenBSD boot loaders are documented in the architecture-specific [18]boot(8) man
pages.
Pre-Installation Checklist
Before you start, you should have some idea what you want to end up with. A few
things worth considering beforehand:
* Machine name
* Hardware installed and available:
+ Verify compatibility with your hardware. You may want to consult the
platform-specific installation notes, especially if you're using one of
the non-x86 CPU architectures. They contain detailed instructions and
any possible caveats:
[[19]alpha] [[20]amd64] [[21]arm64] [[22]armv7] [[23]hppa] [[24]i386]
[[25]landisk] [[26]loongson] [[27]luna88k] [[28]macppc] [[29]octeon]
[[30]powerpc64] [[31]riscv64] [[32]sparc64]
+ If wireless internet is your only networking option, does the card
require additional firmware? If so, read the section on
[33]bootstrapping wireless firmware.
* Install method to be used
* Desired disk layout:
+ Does existing data need to be saved elsewhere?
+ Will OpenBSD coexist on this system with another OS? If so, how will
each system be booted? Will you need to install a boot manager?
+ Will the entire disk be used for OpenBSD, or do you want to keep an
existing partition/OS? (or space for a future one)
+ How do you wish to sub-partition the OpenBSD part of your disk?
+ Do you want disk encryption?
* Network settings, if not using DHCP:
+ Domain name and DNS address
+ IP address and subnet masks for each NIC
+ Gateway address
Downloading OpenBSD
The following installation images are available:
install75.img A disk image that can be written to a USB flash drive or similar
device. Includes the [34]file sets.
____________________________________________________________________________
[35]amd64 | [36]arm64 | [37]i386 | [38]octeon | [39]powerpc64 | [40]riscv64 |
[41]sparc64
miniroot75.img The same as above, but file sets are not included. They can be
pulled down from the internet or from a local disk.
____________________________________________________________________________
[42]alpha | [43]amd64 | [44]arm64 | [45]armv7 | [46]i386 | [47]landisk |
[48]loongson | [49]luna88k | [50]octeon | [51]powerpc64 | [52]riscv64 |
[53]sparc64
install75.iso An ISO 9660 image that can be used to create an install CD/DVD.
Includes the file sets.
____________________________________________________________________________
[54]alpha | [55]amd64 | [56]arm64 | [57]hppa | [58]i386 | [59]macppc |
[60]powerpc64 | [61]sparc64
cd75.iso The same as above, but file sets are not included.
____________________________________________________________________________
[62]alpha | [63]amd64 | [64]hppa | [65]i386 | [66]loongson | [67]macppc |
[68]sparc64
floppy75.img Supports some older machines that lack other booting options.
____________________________________________________________________________
[69]amd64 | [70]i386 | [71]sparc64
Images can also be downloaded from a number of alternate [72]mirror sites.
An SHA256 file containing checksums can be found in the same directory as the
installation files. You can confirm that none of the downloaded files were
mangled in transit using the [73]sha256(1) command.
$ sha256 -C SHA256 miniroot*.img
(SHA256) miniroot75.img: OK
Or, if you're using the GNU coreutils:
$ sha256sum -c --ignore-missing SHA256
miniroot75.img: OK
However, this only checks for accidental corruption. You can use [74]signify(1)
and the SHA256.sig file to cryptographically verify the downloaded image.
$ signify -Cp /etc/signify/openbsd-75-base.pub -x SHA256.sig miniroot*.img
Signature Verified
miniroot75.img: OK
Note that the signify package on other operating systems may not include the
required [75]public key, or it may be installed in another location.
The install75.iso and install75.img images do not contain an SHA256.sig file, so
the installer will complain that it can't check the signature of the included
sets:
Directory does not contain SHA256.sig. Continue without verification? [no]
This is because it would make no sense for the installer to verify them. If
someone were to make a rogue installation image, they could certainly change the
installer to say the files were legitimate. If the image's signature has been
verified beforehand, it is safe to answer "yes" at that prompt.
Creating Install Media
Flash Drives
A bootable USB flash drive can be created by attaching the target device and
copying over the image with [76]dd(1).
Using OpenBSD, assuming the device was recognized as sd6:
# dd if=install*.img of=/dev/rsd6c bs=1M
Note that the raw I/O device is used: rsd6c rather than sd6c.
Details of this will vary on other platforms. If you're using a different OS, be
sure to select the appropriate device name: /dev/sdX on Linux or /dev/rdiskX on
macOS for example.
CD-ROMs
You can create a bootable CD-ROM on OpenBSD by using [77]cdio(1).
# cdio tao cd*.iso
Performing a Simple Install
If you need instructions on booting from your preferred media, check the relevant
[78]platform page of your machine.
The installer is designed to install OpenBSD in a very usable default
configuration with a minimum of user intervention. In fact, you can often just
hit to get a good OpenBSD install, moving your hands to the rest of the
keyboard only to enter the root password.
After the [79]dmesg(8) is shown, you will see the first installer question:
...
root on rd0a swap on rd0b dump on rd0b
erase ^?, werase ^W, kill ^U, intr ^C, status ^T
Welcome to the OpenBSD/amd64 7.5 installation program.
(I)nstall, (U)pgrade, (A)utoinstall or (S)hell?
Choose (I)nstall and follow the instructions.
File Sets
The complete OpenBSD installation is broken up into a number of file sets:
bsd The kernel (required)
bsd.mp The multi-processor kernel (only on some platforms)
bsd.rd The [80]ramdisk kernel
base75.tgz The base system (required)
comp75.tgz The compiler collection, headers and libraries
man75.tgz Manual pages
game75.tgz Text-based games
xbase75.tgz Base libraries and utilities for X11 (requires xshare75.tgz)
xfont75.tgz Fonts used by X11
xserv75.tgz X11's X servers
xshare75.tgz X11's man pages, locale settings and includes
New users are recommended to install all of them.
Some libraries from xbase75.tgz, like freetype or fontconfig, can be used outside
of X by programs that manipulate text or graphics. Such programs will usually
need fonts, either from xfont75.tgz or font packages. For the sake of simplicity,
the developers decided against maintaining a minimal xbase75.tgz set that would
allow most non-X ports to run.
Adding a File Set After Install
If you chose to skip some file sets at install time, you might realize later that
you really do need them after all. Simply boot [81]bsd.rd from your root file
system and choose (U)pgrade. When you get to the list of file sets, select the
ones you need.
Disk Partitioning
OpenBSD can be installed in as little as 512MB, but using a device that small is
something for advanced users. Until you have some experience, 8GB or more disk
space is recommended.
Unlike some other operating systems, OpenBSD encourages users to split their disk
into a number of partitions, rather than just one or two large ones. Some of the
reasons for doing so are:
* Security: Some of OpenBSD's default security features rely on filesystem
[82]mount options such as nosuid, nodev, noexec or wxallowed.
* Stability: A user or a misbehaved program can fill a filesystem with garbage
if they have write permissions for it. Your critical programs, which
hopefully run on a different filesystem, do not get interrupted.
* [83]fsck(8): You can mount partitions that you never or rarely need to write
to as readonly most of the time, which will eliminate the need for a
filesystem check after a crash or power interruption.
The installer will create a partitioning plan based on the size of your hard
disk. While this will not be a perfect layout for all people, it provides a good
starting point for figuring out what you need. Read about disklabel's defaults
for [84]automatic disk allocation and the [85]hier(7) man page before making
decisions about custom partitioning schemes.
* Since some [86]packages need to be started from a wxallowed filesystem, it is
recommended to have a separate /usr/local partition.
* Very small partitions can become troublesome when you need to upgrade.
* A /home partition can be nice. New version of the OS? Leave your /home
partition untouched, wipe and reload everything else.
* You may also want to create an [87]altroot partition for backing up your root
filesystem.
* A system exposed to the internet should have a separate /var and maybe even a
separate /var/log.
* Compiling some [88]ports from source can take huge amounts of space on your
/usr and /tmp partitions.
Bootstrapping Wireless Firmware
For licensing reasons, some firmware cannot be directly distributed with OpenBSD.
The [89]fw_update(8) tool will automatically download and install any missing
firmware, but this requires a working internet connection.
In the case of certain hardware configurations, such as a laptop with no ethernet
port, the user will have to manually download and install the firmware in order
to get online for the first time. This can be done pre-installation, by adding
the firmware files to the install media, or after the OS has been installed from
a CD or disk.
Adding firmware files to the install media will not enable the hardware during
the installation process. They will be added to the target disk, so the hardware
can be used after the first boot into the installed system.
Start by finding the wireless adapter's [90]interface name with [91]dmesg(8).
From an existing OpenBSD installation, mount the install image as a vnode disk
with [92]vnconfig(8) and use [93]fw_update(8) to download the required files to
it. This example uses firmware for an [94]iwm(4) card:
# vnconfig install75.img
vnd0
# mount /dev/vnd0a /mnt
# fw_update -Fv -p /mnt iwm
# umount /mnt
# vnconfig -u vnd0
The resulting file can then be used to [95]create a bootable install image with
the necessary firmware.
If you don't have an existing OpenBSD system with internet access, use another
computer to download the appropriate file from
[96]http://firmware.openbsd.org/firmware/ and put it on a USB drive that's
readable by OpenBSD. Then, on the OpenBSD machine, [97]mount(8) the drive and use
[98]fw_update(8) to install it from there.
Sending Your dmesg After the Install
After a successful install, look at the output of the [99]dmesg(8) command and
see if anything stands out. If a device shows up as not configured, this means
that it is not currently supported by the kernel. This may be improved in the
future by sending the dmesg. A quote from /usr/src/etc/root/root.mail:
If you wish to ensure that OpenBSD runs better on your machines, please do us
a favor (after you have your mail system configured!) and type something like:
# (dmesg; sysctl hw.sensors) | \
mail -s "Sony VAIO 505R laptop, apm works OK" dmesg@openbsd.org
so that we can see what kinds of configurations people are running. As shown,
including a bit of information about your machine in the subject or the body
can help us even further. We will use this information to improve device driver
support in future releases. (Please do this using the supplied GENERIC kernel,
not for a custom compiled kernel, unless you're unable to boot the GENERIC
kernel. If you have a multi-processor machine, dmesg results of both GENERIC.MP
and GENERIC kernels are appreciated.) The device driver information we get from
this helps us fix existing drivers. Thank you!
Alternatively, save your dmesg output to a text file and send us its contents:
$ (dmesg; sysctl hw.sensors) > ~/dmesg.txt
Please configure your email client to use plain text. In particular, do not use
HTML formatting or forced line breaks. Put the dmesg into the body of the mail,
not as an attachment.
Customizing the Install Process
The site75.tgz File Set
The OpenBSD install and upgrade scripts allow the selection of a user-created set
called site75.tgz. Like the official [100]file sets, this is a [101]tar(1)
archive rooted in / and untarred with the -xzphf options. It is installed last,
so it can be used to complement and modify the files from a default install.
Furthermore, it is possible to use hostname-dependent sets named
site75-$(hostname -s).tgz. Note: If you intend to provide the sets over HTTP(s),
place site75.tgz in your source directory and include it in your index.txt. It
will then be an option at install time.
The install.site and upgrade.site Scripts
If the site75.tgz file set contains an executable file /install.site, the
installer runs it with [102]chroot(8) based at the freshly installed system's
root. Similarly, the upgrade script runs /upgrade.site. The latter can be placed
in the system's root directory before rebooting for the upgrade.
Example usage:
* Set the system time.
* Do an immediate backup/archive of the new system before you expose it to the
rest of the world.
* Have a set of arbitrary commands be run after the first boot. This will
happen if install.site is used to append any such commands to an
[103]rc.firsttime(8) file (appending to this file is necessary since the
installer itself may write to this file). At boot time, rc.firsttime is
executed once then deleted.
Multibooting
Multibooting is having several operating systems on one computer, with some means
of selecting which OS is to boot. You may want to familiarize yourself with the
[104]OpenBSD boot process before you start. A brief introduction to [105]fdisk(8)
is in the section on [106]using OpenBSD's fdisk.
If you are adding OpenBSD to an existing system, you will probably need to create
some free space before installing OpenBSD. In addition to your existing system's
native tools, [107]gparted may be useful for deleting or resizing existing
partitions. Preferably use one of the four primary MBR partitions for booting
OpenBSD. Extended partitions may not work.
[108]rEFInd is reported to usually work. [109]GRUB is reported to usually fail.
In either case, you are completely on your own.
Windows
The Boot Configuration Data (BCD) store allows multiple versions of Windows to be
booted through bcdedit. A good introduction can be found in [110]this article. If
you want a GUI alternative, you may want to try [111]EasyBCD.
You will need a copy of your OpenBSD install's [112]Partition Boot Record (PBR).
You can copy it to a file using a process similar to:
# dd if=/dev/rsd0a of=openbsd.pbr bs=512 count=1
where sd0a is your boot device, and you will need to get the file openbsd.pbr to
your Windows system partition.
Once OpenBSD's PBR is copied to the Windows system partition, you need a shell
with administrative privileges to run the following commands:
C:\Windows\system32> bcdedit /create /d "OpenBSD/i386" /application bootsector
The entry {0154a872-3d41-11de-bd67-a7060316bbb1} was successfully created.
C:\Windows\system32> bcdedit /set {0154a872-3d41-11de-bd67-a7060316bbb1} device boot
The operation completed successfully.
C:\Windows\system32> bcdedit /set {0154a872-3d41-11de-bd67-a7060316bbb1} path \openbsd.pbr
The operation completed successfully.
C:\Windows\system32> bcdedit /set {0154a872-3d41-11de-bd67-a7060316bbb1} device partition=
c:
The operation completed successfully.
C:\Windows\system32> bcdedit /displayorder {0154a872-3d41-11de-bd67-7060316bbb1} /addlast
The operation completed successfully.
Note that OpenBSD expects the computer's real-time clock to be set to Coordinated
Universal Time (UTC). See [113]this section for more info.
References
1. http://www.openbsd.org/index.html
2. http://www.openbsd.org/faq/index.html
3. http://www.openbsd.org/faq/faq4.html#bsd.rd
4. http://www.openbsd.org/faq/faq4.html#Checklist
5. http://www.openbsd.org/faq/faq4.html#Download
6. http://www.openbsd.org/faq/faq4.html#MkInsMedia
7. http://www.openbsd.org/faq/faq4.html#Install
8. http://www.openbsd.org/faq/faq4.html#FilesNeeded
9. http://www.openbsd.org/faq/faq4.html#Partitioning
10. http://www.openbsd.org/faq/faq4.html#WifiOnly
11. http://www.openbsd.org/faq/faq4.html#SendDmesg
12. http://www.openbsd.org/faq/faq4.html#site
13. http://www.openbsd.org/faq/faq4.html#Multibooting
14. http://www.openbsd.org/faq/faq6.html#PXE
15. https://man.openbsd.org/diskless
16. http://www.openbsd.org/plat.html
17. http://www.openbsd.org/faq/faq4.html#Download
18. https://man.openbsd.org/boot.8
19. https://ftp.openbsd.org/pub/OpenBSD/7.5/alpha/INSTALL.alpha
20. https://ftp.openbsd.org/pub/OpenBSD/7.5/amd64/INSTALL.amd64
21. https://ftp.openbsd.org/pub/OpenBSD/7.5/arm64/INSTALL.arm64
22. https://ftp.openbsd.org/pub/OpenBSD/7.5/armv7/INSTALL.armv7
23. https://ftp.openbsd.org/pub/OpenBSD/7.5/hppa/INSTALL.hppa
24. https://ftp.openbsd.org/pub/OpenBSD/7.5/i386/INSTALL.i386
25. https://ftp.openbsd.org/pub/OpenBSD/7.5/landisk/INSTALL.landisk
26. https://ftp.openbsd.org/pub/OpenBSD/7.5/loongson/INSTALL.loongson
27. https://ftp.openbsd.org/pub/OpenBSD/7.5/luna88k/INSTALL.luna88k
28. https://ftp.openbsd.org/pub/OpenBSD/7.5/macppc/INSTALL.macppc
29. https://ftp.openbsd.org/pub/OpenBSD/7.5/octeon/INSTALL.octeon
30. https://ftp.openbsd.org/pub/OpenBSD/7.5/powerpc64/INSTALL.powerpc64
31. https://ftp.openbsd.org/pub/OpenBSD/7.5/riscv64/INSTALL.riscv64
32. https://ftp.openbsd.org/pub/OpenBSD/7.5/sparc64/INSTALL.sparc64
33. http://www.openbsd.org/faq/faq4.html#WifiOnly
34. http://www.openbsd.org/faq/faq4.html#FilesNeeded
35. https://cdn.openbsd.org/pub/OpenBSD/7.5/amd64/install75.img
36. https://cdn.openbsd.org/pub/OpenBSD/7.5/arm64/install75.img
37. https://cdn.openbsd.org/pub/OpenBSD/7.5/i386/install75.img
38. https://cdn.openbsd.org/pub/OpenBSD/7.5/octeon/install75.img
39. https://cdn.openbsd.org/pub/OpenBSD/7.5/powerpc64/install75.img
40. https://cdn.openbsd.org/pub/OpenBSD/7.5/riscv64/install75.img
41. https://cdn.openbsd.org/pub/OpenBSD/7.5/sparc64/install75.img
42. https://cdn.openbsd.org/pub/OpenBSD/7.5/alpha/miniroot75.img
43. https://cdn.openbsd.org/pub/OpenBSD/7.5/amd64/miniroot75.img
44. https://cdn.openbsd.org/pub/OpenBSD/7.5/arm64/miniroot75.img
45. https://cdn.openbsd.org/pub/OpenBSD/7.5/armv7/
46. https://cdn.openbsd.org/pub/OpenBSD/7.5/i386/miniroot75.img
47. https://cdn.openbsd.org/pub/OpenBSD/7.5/landisk/miniroot75.img
48. https://cdn.openbsd.org/pub/OpenBSD/7.5/loongson/miniroot75.img
49. https://cdn.openbsd.org/pub/OpenBSD/7.5/luna88k/miniroot75.img
50. https://cdn.openbsd.org/pub/OpenBSD/7.5/octeon/miniroot75.img
51. https://cdn.openbsd.org/pub/OpenBSD/7.5/powerpc64/miniroot75.img
52. https://cdn.openbsd.org/pub/OpenBSD/7.5/riscv64/miniroot75.img
53. https://cdn.openbsd.org/pub/OpenBSD/7.5/sparc64/miniroot75.img
54. https://cdn.openbsd.org/pub/OpenBSD/7.5/alpha/install75.iso
55. https://cdn.openbsd.org/pub/OpenBSD/7.5/amd64/install75.iso
56. https://cdn.openbsd.org/pub/OpenBSD/7.5/arm64/install75.iso
57. https://cdn.openbsd.org/pub/OpenBSD/7.5/hppa/install75.iso
58. https://cdn.openbsd.org/pub/OpenBSD/7.5/i386/install75.iso
59. https://cdn.openbsd.org/pub/OpenBSD/7.5/macppc/install75.iso
60. https://cdn.openbsd.org/pub/OpenBSD/7.5/powerpc64/install75.iso
61. https://cdn.openbsd.org/pub/OpenBSD/7.5/sparc64/install75.iso
62. https://cdn.openbsd.org/pub/OpenBSD/7.5/alpha/cd75.iso
63. https://cdn.openbsd.org/pub/OpenBSD/7.5/amd64/cd75.iso
64. https://cdn.openbsd.org/pub/OpenBSD/7.5/hppa/cd75.iso
65. https://cdn.openbsd.org/pub/OpenBSD/7.5/i386/cd75.iso
66. https://cdn.openbsd.org/pub/OpenBSD/7.5/loongson/cd75.iso
67. https://cdn.openbsd.org/pub/OpenBSD/7.5/macppc/cd75.iso
68. https://cdn.openbsd.org/pub/OpenBSD/7.5/sparc64/cd75.iso
69. https://cdn.openbsd.org/pub/OpenBSD/7.5/amd64/floppy75.img
70. https://cdn.openbsd.org/pub/OpenBSD/7.5/i386/floppy75.img
71. https://cdn.openbsd.org/pub/OpenBSD/7.5/sparc64/floppy75.img
72. http://www.openbsd.org/ftp.html
73. https://man.openbsd.org/sha256
74. https://man.openbsd.org/signify
75. https://ftp.openbsd.org/pub/OpenBSD/7.5/openbsd-75-base.pub
76. https://man.openbsd.org/dd
77. https://man.openbsd.org/cdio
78. http://www.openbsd.org/plat.html
79. https://man.openbsd.org/dmesg
80. http://www.openbsd.org/faq/faq4.html#bsd.rd
81. http://www.openbsd.org/faq/faq4.html#bsd.rd
82. https://man.openbsd.org/mount#o
83. https://man.openbsd.org/fsck
84. https://man.openbsd.org/disklabel#AUTOMATIC_DISK_ALLOCATION
85. https://man.openbsd.org/hier
86. http://www.openbsd.org/faq/faq15.html
87. http://www.openbsd.org/faq/faq14.html#altroot
88. http://www.openbsd.org/faq/ports/index.html
89. https://man.openbsd.org/fw_update
90. https://man.openbsd.org/?query=wireless&apropos=1
91. https://man.openbsd.org/dmesg
92. https://man.openbsd.org/vnconfig
93. https://man.openbsd.org/fw_update
94. https://man.openbsd.org/iwm
95. http://www.openbsd.org/faq/faq4.html#MkInsMedia
96. http://firmware.openbsd.org/firmware/
97. https://man.openbsd.org/mount
98. https://man.openbsd.org/fw_update
99. https://man.openbsd.org/dmesg
100. http://www.openbsd.org/faq/faq4.html#FilesNeeded
101. https://man.openbsd.org/tar
102. https://man.openbsd.org/chroot
103. https://man.openbsd.org/rc.firsttime
104. http://www.openbsd.org/faq/faq14.html#BootAmd64
105. https://man.openbsd.org/fdisk
106. http://www.openbsd.org/faq/faq14.html#fdisk
107. https://gparted.org/
108. https://www.rodsbooks.com/refind/
109. https://www.gnu.org/software/grub/
110. https://technet.microsoft.com/en-us/library/cc721886%28WS.10%29.aspx
111. https://neosmart.net/EasyBCD/
112. http://www.openbsd.org/faq/faq14.html#BootAmd64
113. http://www.openbsd.org/faq/faq10.html#TimeZone
Usage: http://www.kk-software.de/kklynxview/get/URL
e.g. http://www.kk-software.de/kklynxview/get/http://www.kk-software.de
Errormessages are in German, sorry ;-)