| Age | Commit message (Collapse) | Author |
|---|
|
change for files on the tape.
Prompted by and discussed with claudio@.
|
|
refers to ;H but shows ;A in examples; spotted by nick@
|
|
ok miod@
|
|
ok miod@
|
|
|
|
|
|
Describe with much more details how to successfully boot from various
devices, including non-built-in ethernet or SCSI controllers; also hint
that most of the MVME147 and the MVME187 can not netboot at all.
This should be much, much more understandable (but we need to run this
through a drunk pvalchev@ to be sure).
|
|
my bad. Spotted by pvalchev@.
|
|
|
|
|
|
|
|
does not support NFS mounts.
|
|
used to are, if at all; so warn people setting up diskless systems under
SunOS or other operating systems that they might need to edit MAKEDEV for
it to run properly on the host system.
|
|
via ifconfig -m, there is no need to suggest canonical media flags on
some arches, especially since the end user might have a different
interface with different flags; instead, be more cosy and mention that
looking at the manual page for the interface might be helpful for
desperate cases.
Thus, merge the OpenBSDInstallNet and OpenBSDInstallNet2 macros, and
remove thde in-between text for the arches that had such a paragraph.
|
|
No text changes except for harmonization, and the blurb about network
interface flags has bene slightly changed for some arches.
|
|
- Provide typical Solaris command lines for creating floppies, dumping
miniroots to disks, and filling tapes.
- Make the tape generation script more versatile.
- When SunOS add_client(8) is mentioned, mention Solaris share(1M) as well.
- Add ``Installing from Solaris'' instructions for sparc and sparc64 ports
- While there, slight fixes to the ``Installing from SunOS'' sections on
sparc and sun3.
|
|
|
|
This time:
- update hardware list, reorganize it more logically
- gets most of the bsd.rd description and instructions on par with other
arches
- document hov to create a boot tape, and how to boot via s-records
- tries to be more verbose about board setup
This is still way too concise. If you write english better than me (trivial)
and know mvme68k a bit, you're welcome to help fill the blanks.
At least this is better than the existing instructions, and deraadt@ agrees.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
