| Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn
|
|
of boot floppies from the INSTALL.alpha notes.
ok deraadt@
|
|
tweaked along the way by at least myself and tj;
ok tj deraadt
|
|
|
|
OK sthen@
|
|
The etc and xetc sets are now inside baseXX.tgz and xbaseXX.tgz.
'looks good' deraadt@
|
|
and verbose, who would ever spend their time reading them.
|
|
ok miod@
|
|
|
|
|
|
|
|
of unix arcana, we will not condescend to tell you how. why spoil the fun?
|
|
|
|
|
|
places to check for this information, or trial and error, with error
resulting in things getting fixed. Scary false warnings don't help anyone.
Unmaintainable lists are always unmaintained.
|
|
|
|
|
|
No regression has been reported since libusb became the prefered
solution to work with USB scanners.
req. by mpi@
ok ian@ mpi@ miod@
|
|
|
|
people curs^Wblessed with EISA-capable alpha systems.
|
|
|
|
have a real miniroot to be dd'ed to the disk, and that's fine; but when
we are talking about booting bsd.rd (either from an existing setup, or the
network, or the cd-rom images), then refer to it as `installation kernel'.
|
|
|
|
removal of misc. Better late than never.
|
|
|
|
General huzzahs.
"go for it" deraadt@
|
|
- do not mention tape as an installation media on systems where it is very
unlikely that a tape drive can be connected to (i.e. anything with only
USB as expansion capabilities)
- do not mention that fetching the installation sets from a partition is
``for upgrades only''. You may do this for installation, but of course
you can not use a partition which will be newfs'ed for that purpose.
- mention ext2fs partitions as possible installation sets source only on
platforms where the installation media actually can mount an ext2fs
filesystem.
- stress the fact that the sparc miniroot image is a GENERIC kernel with
a little on-disk filesystem, and not a RAMDISK kernel with a little
in-memory filesystem, and thus must not be overwritten during installation
(i.e. be careful if you repartition the disk the miniroot has been put on).
- more conv=sync -> conv=osync for tape setup instructions.
- model-specific layout changes on armish, loongson and socppc instructions.
- fix various typos and grammar mistaeks.
"sure" deraadt@ (without eyeballing)
|
|
|
|
|
|
are very close to the Tsunami systems (rpb family 34) and share the existing
Tsunami code; the tsc(4) Tsunami controller code is extended to handle the
Titan differences, except for the Titan AGP GART which is left unsupported
for now.
Tested to not cause regressions on DS20 (deraadt@) and ES40 (miod@).
Titan support tested by Sergey Prysiazhnyi on DS25, many thanks for your time!
|
|
|
|
section when it is mentioned in the supported systems section
shortly before.
|
|
HFS + disklabel setups.
|
|
Also, the per-platform features are moved to a common place, which makes
the MD layout easier to work on. m4.common is still a tangled mess of subtly
placed dnl, though...
|
|
802.11 wireless as chipsets used and products change rapidly, but
rather display just a list of the supported chipsets like we do in www.
Discussed with jmc and deraadt
|
|
|
|
|
|
|
|
|
|
|
|
be very hard to maintain such lists, it is inconsistent, and of limited use;
ok krw miod
|
|
sysmerge can help you upgrade etc and xetc afterwards.
|
|
|
|
to enable it if necessary. From FreeBSD.
|
|
- mention more models supported by each floppy
- mention more supported and unsupported models
- sync cdrom boot instructions with reality
- update ftp urls, ftp.digital.com no longer exist (but I resisted whining
at HP which does not provide all the contents formerly available from
ftp.digital.com and which you have to pick from educational sites which
have mirrored them)
- various little rewording
with help from sobrado@
|
|
unattended when configured for serial console and no keyboard is plugged.
|
|
- document questions in proper order: hostname before network configuration,
DNS only if network is configured, sshd and ntpd, aperture only on
machines which need it, serial console only on machines which need it.
This is done by splitting the end of OpenBSDCommonURL in various
macros, OpenBSDInstallWrapup, OpenBSDInstallAperture, OpenBSDInstallConsole
and OpenBSDInstallWrapupPart2.
- use the above macros when appropriate, OpenBSDInstallWrapup* being
mandatory on all arches.
- remove serial console configuration blurb on sparc and sparc64, it is
handled by OpenBSDInstallConsole now.
|
|
|
|
the various AlphaServer references less ambiguous.
|