diff options
Diffstat (limited to 'distrib')
| -rw-r--r-- | distrib/notes/alpha/xfer | 24 | ||||
| -rw-r--r-- | distrib/notes/i386/xfer | 26 | ||||
| -rw-r--r-- | distrib/notes/sparc/xfer | 26 | ||||
| -rw-r--r-- | distrib/notes/sparc64/xfer | 26 | ||||
| -rw-r--r-- | distrib/notes/sun3/xfer | 8 |
5 files changed, 55 insertions, 55 deletions
diff --git a/distrib/notes/alpha/xfer b/distrib/notes/alpha/xfer index 58887df6469..5ab882a5979 100644 --- a/distrib/notes/alpha/xfer +++ b/distrib/notes/alpha/xfer @@ -14,14 +14,14 @@ floppy disk. Creating a bootable floppy disk using DOS/Windows: - First you need to get access to the OpenBSD Bootable floppy - images. If you can access the CD-ROM distribution under DOS - the bootable disks are in the OSREV/MACHINE directory, otherwise - you you will have to download them from one of the OpenBSD - ftp or http mirror sites, using ftp or a web-viewer. In either - case, take care to do "binary" transfers, since these are - images files and any DOS cr/lf translations or control/z EOF - interpretations will result in corrupted transfers. + First you need to get access to the OpenBSD bootable floppy + images. If you can access the distribution from the CD-ROM under + DOS, you will find the bootable disks in the OSREV/MACHINE + directory. Otherwise, you will have to download them from one of + the OpenBSD ftp or http mirror sites, using an ftp client or a web + browser. In either case, take care to do "binary" transfers, since + these are images files and any DOS cr/lf translations or control/z + EOF interpretations will result in corrupted transfers. You will also need to go to the "tools" directory and grab a copy of the rawrite.exe utility and its documentation. This @@ -48,9 +48,9 @@ Creating a bootable floppy disk using DOS/Windows: Creating a bootable floppy disk using SunOS or other Un*x-like system: First, you will need obtain a local copy of the bootable filesystem - image as described above. If possible use cksum or md5 to verify - the checksums of the images vs. the values in the CKSUM or MD5 - files on the mirror site. + image as described above. If possible use the cksum(1) or md5(1) + commands to verify the checksums of the images vs. the values in + the CKSUM or MD5 files on the mirror site. Next, use the dd(1) utility to copy the file to the floppy drive. Under SunOS, the command would be: @@ -61,7 +61,7 @@ Creating a bootable floppy disk using SunOS or other Un*x-like system: this to conform to local naming conventions for the floppy and options suitable for copying to a "raw" floppy image. The key issue is that the device name used for the floppy *must* be one - that refers to the whole 2880 block image, not a partition or + that refers to the correct block device, not a partition or compatibility mode, and the copy command needs to be compatible with the requirement that writes to a raw device must be in multiples of 512-byte blocks. The variations are endless and diff --git a/distrib/notes/i386/xfer b/distrib/notes/i386/xfer index 45ed14c7fda..b3649168bbf 100644 --- a/distrib/notes/i386/xfer +++ b/distrib/notes/i386/xfer @@ -15,19 +15,19 @@ 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 use ftp get/reget to transfer the distribution sets to a local server or disk and perform the installation -from there, rather than directly on the internet. +from there, rather than directly from the internet. Creating a bootable floppy disk using DOS/Windows: - First you need to get access to the OpenBSD Bootable floppy - images. If you can access the CD-ROM distribution under DOS - the bootable disks are in the OSREV/MACHINE directory, otherwise - you you will have to download them from one of the OpenBSD - ftp or http mirror sites, using ftp or a web-viewer. In either - case, take care to do "binary" transfers, since these are - images files and any DOS cr/lf translations or control/z EOF - interpretations will result in corrupted transfers. + First you need to get access to the OpenBSD bootable floppy + images. If you can access the distribution from the CD-ROM under + DOS, you will find the bootable disks in the OSREV/MACHINE + directory. Otherwise, you will have to download them from one of + the OpenBSD ftp or http mirror sites, using an ftp client or a web + browser. In either case, take care to do "binary" transfers, since + these are images files and any DOS cr/lf translations or control/z + EOF interpretations will result in corrupted transfers. You will also need to go to the "tools" directory and grab a copy of the rawrite.exe utility and its documentation. This @@ -54,9 +54,9 @@ Creating a bootable floppy disk using DOS/Windows: Creating a bootable floppy disk using SunOS or other Un*x-like system: First, you will need obtain a local copy of the bootable filesystem - image as described above. If possible use cksum or md5 to verify - the checksums of the images vs. the values in the CKSUM or MD5 - files on the mirror site. + image as described above. If possible use the cksum(1) or md5(1) + commands to verify the checksums of the images vs. the values in + the CKSUM or MD5 files on the mirror site. Next, use the dd(1) utility to copy the file to the floppy drive. Under SunOS, the command would be: @@ -67,7 +67,7 @@ Creating a bootable floppy disk using SunOS or other Un*x-like system: this to conform to local naming conventions for the floppy and options suitable for copying to a "raw" floppy image. The key issue is that the device name used for the floppy *must* be one - that refers to the whole 2880 block image, not a partition or + that refers to the correct block device, not a partition or compatibility mode, and the copy command needs to be compatible with the requirement that writes to a raw device must be in multiples of 512-byte blocks. The variations are endless and diff --git a/distrib/notes/sparc/xfer b/distrib/notes/sparc/xfer index e2f49dd758a..381f6036b03 100644 --- a/distrib/notes/sparc/xfer +++ b/distrib/notes/sparc/xfer @@ -36,14 +36,14 @@ a user has, the intent is to provide some way that will be practical. Creating a bootable floppy disk using DOS/Windows: - First you need to get access to the OpenBSD Bootable floppy - images. If you can access the CD-ROM distribution under DOS - the bootable disks are in the OSREV/sparc directory, otherwise - you you will have to download them from one of the OpenBSD - ftp or http mirror sites, using ftp or a web-viewer. In either - case, take care to do "binary" transfers, since these are - images files and any DOS cr/lf translations or control/z EOF - interpretations will result in corrupted transfers. + First you need to get access to the OpenBSD bootable floppy + images. If you can access the distribution from the CD-ROM under + DOS, you will find the bootable disks in the OSREV/MACHINE + directory. Otherwise, you will have to download them from one of + the OpenBSD ftp or http mirror sites, using an ftp client or a web + browser. In either case, take care to do "binary" transfers, since + these are images files and any DOS cr/lf translations or control/z + EOF interpretations will result in corrupted transfers. You will also need to go to the "tools" directory and grab a copy of the rawrite.exe utility and its documentation. This @@ -70,9 +70,9 @@ Creating a bootable floppy disk using DOS/Windows: Creating a bootable floppy disk using SunOS or other Un*x-like system: First, you will need obtain a local copy of the bootable filesystem - image as described above. If possible use cksum or md5 to verify - the checksums of the images vs. the values in the CKSUM or MD5 - files on the mirror site. + image as described above. If possible use the cksum(1) or md5(1) + commands to verify the checksums of the images vs. the values in + the CKSUM or MD5 files on the mirror site. Next, use the dd(1) utility to copy the file to the floppy drive. Under SunOS, the command would be: @@ -83,7 +83,7 @@ Creating a bootable floppy disk using SunOS or other Un*x-like system: this to conform to local naming conventions for the floppy and options suitable for copying to a "raw" floppy image. The key issue is that the device name used for the floppy *must* be one - that refers to the whole 2880 block image, not a partition or + that refers to the correct block device, not a partition or compatibility mode, and the copy command needs to be compatible with the requirement that writes to a raw device must be in multiples of 512-byte blocks. The variations are endless and @@ -201,7 +201,7 @@ 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 use ftp get/reget to transfer the distribution sets to a local server or disk and perform the installation -from there, rather than directly on the internet. +from there, rather than directly from the internet. To install or upgrade OpenBSD using a tape, you need to do the following: diff --git a/distrib/notes/sparc64/xfer b/distrib/notes/sparc64/xfer index f822984704b..2acb680a5a1 100644 --- a/distrib/notes/sparc64/xfer +++ b/distrib/notes/sparc64/xfer @@ -34,14 +34,14 @@ dnl dnl XXX uncomment when floppy available dnl Creating a bootable floppy disk using DOS/Windows: dnl -dnl First you need to get access to the OpenBSD Bootable floppy -dnl images. If you can access the CD-ROM distribution under DOS -dnl the bootable disks are in the OSREV/MACHINE directory, otherwise -dnl you you will have to download them from one of the OpenBSD -dnl ftp or http mirror sites, using ftp or a web-viewer. In either -dnl case, take care to do "binary" transfers, since these are -dnl images files and any DOS cr/lf translations or control/z EOF -dnl interpretations will result in corrupted transfers. +dnl First you need to get access to the OpenBSD bootable floppy +dnl images. If you can access the distribution from the CD-ROM under +dnl DOS, you will find the bootable disks in the OSREV/MACHINE +dnl directory. Otherwise, you will have to download them from one of +dnl the OpenBSD ftp or http mirror sites, using an ftp client or a web +dnl browser. In either case, take care to do "binary" transfers, since +dnl these are images files and any DOS cr/lf translations or control/z +dnl EOF interpretations will result in corrupted transfers. dnl dnl You will also need to go to the "tools" directory and grab a dnl copy of the rawrite.exe utility and its documentation. This @@ -68,9 +68,9 @@ dnl dnl Creating a bootable floppy disk using SunOS or other Un*x-like system: dnl dnl First, you will need obtain a local copy of the bootable filesystem -dnl image as described above. If possible use cksum or md5 to verify -dnl the checksums of the images vs. the values in the CKSUM or MD5 -dnl files on the mirror site. +dnl image as described above. If possible use the cksum(1) or md5(1) +dnl commands to verify the checksums of the images vs. the values in +dnl the CKSUM or MD5 files on the mirror site. dnl dnl Next, use the dd(1) utility to copy the file to the floppy drive. dnl Under SunOS, the command would be: @@ -81,7 +81,7 @@ dnl If you are using something other than SunOS, you may have to adapt dnl this to conform to local naming conventions for the floppy and dnl options suitable for copying to a "raw" floppy image. The key dnl issue is that the device name used for the floppy *must* be one -dnl that refers to the whole 2880 block image, not a partition or +dnl that refers to the correct block device, not a partition or dnl compatibility mode, and the copy command needs to be compatible dnl with the requirement that writes to a raw device must be in dnl multiples of 512-byte blocks. The variations are endless and @@ -203,7 +203,7 @@ dnl mirror sites over the internet, however you must consider the speed and dnl reliability of your internet connection for this option. It may save dnl much time and frustration to use ftp get/reget to transfer the dnl distribution sets to a local server or disk and perform the installation -dnl from there, rather than directly on the internet. +dnl from there, rather than directly from the internet. dnl To install or upgrade OpenBSD using a tape, you need to do the following: diff --git a/distrib/notes/sun3/xfer b/distrib/notes/sun3/xfer index 5cb84eb4508..41517d9254e 100644 --- a/distrib/notes/sun3/xfer +++ b/distrib/notes/sun3/xfer @@ -30,11 +30,11 @@ Creating a bootable hard disk using SunOS or other Un*x-like system: single user mode), and then booting from that partition. Using the "b" partition allows you to boot without overwriting - any useful parts of the disk, you can also use another partition, - but don't used the "a" or "c" partition without understanding + any useful parts of the disk. You can also use another partition, + but don't use the "a" or "c" partition without understanding the disklabel issues described below under "incompatible systems". - This requires that you be running SunOS, Solaris, OpenBSD or NetBSD + This requires that you are running SunOS, Solaris, OpenBSD or NetBSD which have a compatible view of SunOS disk labels and partitions. Use the dd(1) utility to copy the file to the hard drive. @@ -73,7 +73,7 @@ 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 use ftp get/reget to transfer the distribution sets to a local server or disk and perform the installation -from there, rather than directly on the internet. +from there, rather than directly from the internet. To install or upgrade OpenBSD using a tape, you need to do the following: |