diff options
Diffstat (limited to 'distrib')
| -rw-r--r-- | distrib/notes/alpha/contents | 15 | ||||
| -rw-r--r-- | distrib/notes/alpha/install | 78 |
2 files changed, 67 insertions, 26 deletions
diff --git a/distrib/notes/alpha/contents b/distrib/notes/alpha/contents index 03c322217ad..59589949c20 100644 --- a/distrib/notes/alpha/contents +++ b/distrib/notes/alpha/contents @@ -1,4 +1,4 @@ -dnl $OpenBSD: contents,v 1.58 2014/11/10 07:15:41 jsg Exp $ +dnl $OpenBSD: contents,v 1.59 2014/12/13 15:45:53 miod Exp $ TopPart OpenBSDfloppy @@ -42,10 +42,19 @@ OpenBSDinstalliso OpenBSDcd + bootxx, boot The OpenBSD/MACHINE first and second-level boot + loader; useful to update your boot loader if you want + to reinstall from an old OpenBSD setup but the existing + boot loader is too old to load bsd.rd correctly. + + netboot The OpenBSD/MACHINE network boot loader, for bootp + or dhcpd protocols. + + netboot.mop The OpenBSD/MACHINE network boot loader, for MOP + protocol. + OpenBSDfloppydesc(three,Each,s) -dnl boot, bootxx, netboot -dnl DistributionDescription(ten) OpenBSDbase(67412475,206465200) diff --git a/distrib/notes/alpha/install b/distrib/notes/alpha/install index a384201d0d1..fe9424666b4 100644 --- a/distrib/notes/alpha/install +++ b/distrib/notes/alpha/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.39 2014/03/19 01:59:48 tedu Exp $ +dnl $OpenBSD: install,v 1.40 2014/12/13 15:45:53 miod Exp $ OpenBSDInstallPrelude There are several ways to install OpenBSD onto a disk. The easiest way is @@ -53,44 +53,76 @@ Booting from Network: UN*X-like operating systems. More information on diskless booting can be found in the OpenBSD diskless(8) manual page. - In this case, you will need to set up dhcpd on the server, which can - serve bootp protocol requests. Start by editing the /etc/dhcpd.conf - on the bootserver, and declare an information block. Here is an - example: + Alpha systems can download their boot code over the network either + using the old DEC MOP protocol, or the common bootp protocol. - subnet 10.0.0.0 netmask 255.0.0.0 { + Older systems, such as the DEC 3000 systems, can only use the MOP + protocol. + + Booting from a bootp or dhcp server: + + You will need to set up dhcpd on the server, which can serve + bootp protocol requests. Start by editing the /etc/dhcpd.conf + on the bootserver, and declare an information block. Here is an + example: + + subnet 10.0.0.0 netmask 255.0.0.0 { host piper { always-reply-rfc1048 "true"; filename "netboot"; option root-path "/alpha"; - hardware ethernet 00:02:56:00:73:31; + hardware ethernet 08:00:2b:3d:28:2a; fixed-address 10.42.42.42; } - } + } - Do not forget to enable dhcpd. + Do not forget to start dhcpd. - You will also need to enable tftpd, for the MACHINE to download the - "netboot" from the server in the /tftpboot directory. + You will also need to start tftpd, for the system to download + the "netboot" file from the server in the /tftpboot directory. - Next, you need to add an entry for your MACHINE in /etc/bootparams. - For example: + Booting from a MOP server: - piper root=myserver:/alpha + You will need to copy netboot.mop into + /tftpboot/mop/1a2b3c4d5e6f.SYS, where "1a2b3c4d5e6f" represents + the six octets of your Ethernet address, which can be obtained + with ``show dev'' at the SRM prompt. For example, the filename + for the machine in the dhcp example above would be + "08002b3d282a.SYS". Note that the MAC portion of the filename + must be lower case, but the "SYS" extension must be upper case. + + Do not forget to start mopd. + + Common netboot steps: + + A few more services need to be enabled on the boot server. - Enable rpc.bootparamd either by turning it on in /etc/rc.conf and - rebooting, or by running it manually. + First, add the Ethernet address to /etc/ethers file, as in: - Only uncompressed kernels are supported for booting in this release. - This means you have to execute the following command on your boot - server before installing a new kernel for your MACHINE to boot: + 08:00:2b:3d:28:2a piper - # gzip -dc bsd.rd > /alpha/bsd + and start rarpd. + + Second, you will need to export a directory for your new machine + to mount over NFS, in order to get its kernel. This is + accomplished by adding an entry to /etc/exports such as: + + /alpha piper + + The NFS server (which may be a different machine than the + MOP or dhcp server) will need to run nfsd, mountd, and the + rpc portmapper. See the exports(5) manpage for more + information. + + Last, you will need to add an entry for your system in + /etc/bootparams, to point to the NFS server. For example: + + piper root=myserver:/alpha - This assumes you have path /alpha exported via NFS. + and start bootparamd. - Once loaded, netboot will mount /alpha over NFS and load the kernel - from there. + Once loaded, the boot loader will mount /alpha over NFS and load + the kernel from there. Installing using the Floppy, CD-ROM or Network procedure: |