version 1.60, 2014/03/31 03:36:54 |
version 1.61, 2014/03/31 16:02:48 |
|
|
<hr> |
<hr> |
|
|
<ul> |
<ul> |
<li>One of the install scripts has a flaw that makes the CD-ROM mount fail |
<li> |
when using the CD-ROM as the install source media. |
<font color="#009000"><strong>CD RELEASE WORKAROUND</strong></font> |
To workaround this use the following sequence of commands before |
<i>All architectures</i><br> |
starting the install script. This must be done each time the install |
One of the install scripts has a flaw that makes the CD-ROM mount fail |
kernel is booted if the install script is to be run and the CD-ROM |
when using the CD-ROM as the install source media. |
is the media to install from. Do the following at the shell prompt: |
To workaround this use the following sequence of commands before |
|
starting the install script. This must be done each time the install |
|
kernel is booted if the install script is to be run and the CD-ROM |
|
is the media to install from. Do the following at the shell prompt: |
<pre><b>#</b> ed install.sub |
<pre><b>#</b> ed install.sub |
/{_filesystem/s//{_fstype/ |
/{_filesystem/s//{_fstype/ |
wq |
wq |
|
|
that you can restart the install by: |
that you can restart the install by: |
<pre><b>#</b> install |
<pre><b>#</b> install |
</pre> |
</pre> |
</ul> |
<p> |
<br> |
<li> |
<h3><font color="#e00000">alpha</font></h3> |
<font color="#009000"><strong>CD RELEASE WORKAROUND</strong></font> |
<ul> |
<i>alpha only</i><br> |
<li>CD2 does not boot on the alpha, as had been planned. Instead, you |
CD2 does not boot on the alpha, as had been planned. Instead, you |
must use the floppy install method. This is not significantly |
must use the floppy install method. This is not significantly |
harder.. |
harder.. |
</ul> |
<p> |
<br> |
<li> |
<h3><font color="#e00000">i386</font></h3> |
<font color="#009000"><strong>BOOT BLOCK BUG</strong></font> |
<ul> |
<i>i386 only</i><br> |
<li>Some rarer PC BIOSs do not like the hardrive bootblocks when used |
Some rarer PC BIOSs do not like the hardrive bootblocks when used |
as a MBR. The symptom is that the BIOS says "READ ERROR" when booting, |
as a MBR. The symptom is that the BIOS says "READ ERROR" when booting, |
but everything suggests it should work fine. In those cases, it is |
but everything suggests it should work fine. In those cases, it is |
sufficient to install OS-BS or some other primary bootloader as the main |
sufficient to install OS-BS or some other primary bootloader as the main |
MBR, then install OpenBSD in a partition all by itself starting at a |
MBR, then install OpenBSD in a partition all by itself starting at a |
non-zero offset. For instance, start OpenBSD at next track boundary or so. |
non-zero offset. For instance, start OpenBSD at next track boundary or so. |
<li>The i386/X11/SUMS.md5 file contains 4 incorrect MD5 checksums. |
<p> |
|
<li> |
|
<font color="#009000"><strong>WRONG CHECKSUMS</strong></font> |
|
<i>i386 only</i><br> |
|
The i386/X11/SUMS.md5 file contains 4 incorrect MD5 checksums. |
These have been corrected on the ftp mirrors. The correct lines are:<br> |
These have been corrected on the ftp mirrors. The correct lines are:<br> |
MD5 (X33doc.tgz) = 6aa0be7987f9a3cf32a63b5ea9a83b39<br> |
MD5 (X33doc.tgz) = 6aa0be7987f9a3cf32a63b5ea9a83b39<br> |
MD5 (X33html.tgz) = 6ba39d41aef7c75c35a0533275c6f8c0<br> |
MD5 (X33html.tgz) = 6ba39d41aef7c75c35a0533275c6f8c0<br> |
MD5 (X33ps.tgz) = ea49fc1b12c17fc16ece7d0e4ad4ee06<br> |
MD5 (X33ps.tgz) = ea49fc1b12c17fc16ece7d0e4ad4ee06<br> |
MD5 (RELNOTES) = 689fda20596a4eb82f86ded51efb01f4<br> |
MD5 (RELNOTES) = 689fda20596a4eb82f86ded51efb01f4<br> |
<li>A lot of people with IDE disk drives fail to read the |
<p> |
|
A lot of people with IDE disk drives fail to read the |
INSTALL.i386 document, and hence end up with geometry translation |
INSTALL.i386 document, and hence end up with geometry translation |
problems. Read the document, please. |
problems. Read the document, please. |
</ul> |
<p> |
<br> |
<li> |
<h3><font color="#e00000">amiga</font></h3> |
<font color="#009000"><strong>RELEASE BUG</strong></font> |
<ul> |
<i>amiga only</i><br> |
<li>The amiga install has a flaw wrt Tseng based graphic cards: when entering |
The amiga install has a flaw wrt Tseng based graphic cards: when entering |
multiuser mode the console won't get a login prompt. This is due to |
multiuser mode the console won't get a login prompt. This is due to |
a problem in the shipped /dev/MAKEDEV script. To fix, enter single |
a problem in the shipped /dev/MAKEDEV script. To fix, enter single |
user mode and do: |
user mode and do: |
<pre><b>#</b> cd /dev |
<pre><b>#</b> cd /dev |
<b>#</b> sh MAKEDEV ttye6 |
<b>#</b> sh MAKEDEV ttye6 |
</pre> |
</pre> |
</ul> |
<p> |
<h3><font color="#e00000">sparc</font></h3> |
<li> |
<ul> |
<font color="#009000"><strong>RELEASE BUG</strong></font> |
<li>The sparc X11R6.3 xdm-config files reference /usr/X11R6.3/... This is |
<i>sparc only</i><br> |
due to X11R6.3's default config file contents. To fix, su and |
The sparc X11R6.3 xdm-config files reference /usr/X11R6.3/... This is |
type: |
to X11R6.3's default config file contents. To fix, su and |
|
type: |
<pre><b>#</b> cd /usr |
<pre><b>#</b> cd /usr |
<b>#</b> ln -s X11R6 X11R6.3 |
<b>#</b> ln -s X11R6 X11R6.3 |
</pre> |
</pre> |
<li>The sparc "single floppy install disk" has a problem when you specify |
<p> |
"dumb" in response to the terminal type query. As a work-around |
<li> |
first specify an invalid terminal such as "bogus" and when prompted |
<font color="#009000"><strong>RELEASE BUG</strong></font> |
again for a terminal type, enter "dumb" and it will work correctly. |
<i>sparc only</i><br> |
<li>When netbooting an older sparc system such as a Sun4 or Sun4c, the boot |
The sparc "single floppy install disk" has a problem when you specify |
may hang up at the end of the tftp transfer of the bootstrap due |
"dumb" in response to the terminal type query. As a work-around |
to the tftp transfer working in 512-byte blocks. If this occurs |
first specify an invalid terminal such as "bogus" and when prompted |
create a "padded" version of the bootstrap (boot or zboot) as follows: |
again for a terminal type, enter "dumb" and it will work correctly. |
|
<p> |
|
<li> |
|
<font color="#009000"><strong>RELEASE BUG</strong></font> |
|
<i>sparc only</i><br> |
|
When netbooting an older sparc system such as a Sun4 or Sun4c, the boot |
|
may hang up at the end of the tftp transfer of the bootstrap due |
|
to the tftp transfer working in 512-byte blocks. If this occurs |
|
create a "padded" version of the bootstrap (boot or zboot) as follows: |
<pre><b>#</b> cd /tftpboot |
<pre><b>#</b> cd /tftpboot |
<b>#</b> dd if=boot of=newboot obs=512 conv=osync |
<b>#</b> dd if=boot of=newboot obs=512 conv=osync |
<b>#</b> mv newboot boot |
<b>#</b> mv newboot boot |
</pre> |
</pre> |
<li>The sparc install script has two flaws that make the kernel copy |
<p> |
and the bootblock install fail. The kernel copy only fails |
<li> |
then installing from CD-ROM. To workaround this use the |
<font color="#009000"><strong>RELEASE BUG</strong></font> |
following sequence of commands before starting the install |
<i>sparc only</i><br> |
script. This must be done each time the install kernel is |
The sparc install script has two flaws that make the kernel copy |
booted if the install script is to be run and the CD-ROM is |
and the bootblock install fail. The kernel copy only fails |
the media to install from. Do the following at the shell |
then installing from CD-ROM. To workaround this use the |
prompt: |
following sequence of commands before starting the install |
if you install from CD-ROM do the following: |
script. This must be done each time the install kernel is |
|
booted if the install script is to be run and the CD-ROM is |
|
the media to install from. Do the following at the shell |
|
prompt: |
|
<p> |
|
If you install from CD-ROM do the following: |
<pre><b>#</b> ed install.md |
<pre><b>#</b> ed install.md |
/\/bsd/s//\/mnt2\/2.1\/sparc\/bsd/ |
/\/bsd/s//\/mnt2\/2.1\/sparc\/bsd/ |
wq |
wq |
|
|
wq |
wq |
<b>#</b> |
<b>#</b> |
</pre> |
</pre> |
The following one you'll have to do always (not only then |
<p> |
installing from CD-ROM) |
The following one you'll have to do always (not only then |
|
installing from CD-ROM) |
<pre><b>#</b> ed /usr/mdec/binstall |
<pre><b>#</b> ed /usr/mdec/binstall |
/getopt/,/getopt/+4d |
/getopt/,/getopt/+4d |
wq |
wq |
<b>#</b> |
<b>#</b> |
</pre> |
</pre> |
</ul> |
<p> |
<h3><font color="#e00000">pmax</font></h3> |
<li> |
<ul> |
<font color="#009000"><strong>RELEASE BUG</strong></font> |
<li> When using the X11R6 binaries from the 2.1 release you will get |
<i>pmax only</i><br> |
|
When using the X11R6 binaries from the 2.1 release you will get |
errors like: |
errors like: |
<pre><b>#</b> mkfontdir |
<pre><b>#</b> mkfontdir |
mkfontdir: undefined symbol: 'astpending' 12 |
mkfontdir: undefined symbol: 'astpending' 12 |
|
|
Please be careful while doing this - because the libc is a very |
Please be careful while doing this - because the libc is a very |
sensitive part of the system. You can remove the original_libc.so.16.1 |
sensitive part of the system. You can remove the original_libc.so.16.1 |
after the next reboot if everything is working fine. |
after the next reboot if everything is working fine. |
</ul> |
|
<p> |
<p> |
<h3><font color="#e00000">mac68k</font></h3> |
<li> |
<ul> |
<font color="#009000"><strong>RELEASE BUG</strong></font> |
<li>The installer generates incorrect /etc/fstab files causing messages such as "file system read-only" on bootup. |
<i>mac68k only</i><br> |
To correct, boot to single-user mode (by clicking that checkbox in the Booter's Booting:Options dialog) and do the following: |
The installer generates incorrect /etc/fstab files causing messages such |
|
as "file system read-only" on bootup. To correct, boot to single-user |
|
mode (by clicking that checkbox in the Booter's Booting:Options dialog) |
|
and do the following: |
<pre> |
<pre> |
<b>#</b> mount /dev/sd0a / |
<b>#</b> mount /dev/sd0a / |
<b>#</b> ed /etc/fstab |
<b>#</b> ed /etc/fstab |
|
|
Make this correction as soon as possible after installing the system. |
Make this correction as soon as possible after installing the system. |
The installer should not have specified the filesystem as the old |
The installer should not have specified the filesystem as the old |
"ufs" type; the "ffs" type is more correct. |
"ufs" type; the "ffs" type is more correct. |
|
<p> |
<li>The installer forgets to install the kernel onto the filesystem. |
<li> |
|
<font color="#009000"><strong>RELEASE BUG</strong></font> |
|
<i>mac68k only</i><br> |
|
The installer forgets to install the kernel onto the filesystem. |
This is because the installer expects all packages including the kernel to |
This is because the installer expects all packages including the kernel to |
be tar'ed and gzip'ed. The kernel was not shipped that way. Therefore, you |
be tar'ed and gzip'ed. The kernel was not shipped that way. Therefore, you |
must make this correction <em>before attempting to boot the system</em>. |
must make this correction <em>before attempting to boot the system</em>. |
|
|
<pre> |
<pre> |
> cpin bsd-generic bsd |
> cpin bsd-generic bsd |
</pre> |
</pre> |
Good luck. |
<p> |
|
|
</ul> |
</ul> |
|
|
</body> |
</body> |