- While reading install/12957 it was suggested
(http://mail-index.netbsd.org/port-i386/2006/11/27/0000.html)
that all notes, marked with '[PCMCIA]' should go and be
replaced with a more generic explanation about removable
devices.
- I noticed the HTML output concatenates 'NetBSD' and '4.0',
which is ugly.
- The IP addresses for ftp.NetBSD.org are wrong.
Cleanup dd options accordingly to the following policy:
1) put if, of, bs, conv in this order
2) for reading/writing from/to disk don't use sync
4) reading from tape - use sync
3) writing to tape - use osync
Noted by Don Yuniskis (auryn at gci-net.com) via install/13749. Thanks!
Reviewed by <martin>. Thank you!
* simplify commands to extracts sets & pkgsrc
* add spaces around \(em - why this isn't rendered as — is far
beyond me, can someone with *roff fu have a look?
Inspired by posting by James K. Lowden on netbsd-docs.
XXX the hardware list needs real work. :(
newfs and mount the target filesystem.
In Hauke's words: "Basically, the mac68k md_make_bsd_partitions() function,
which replaces the MI make_bsd_partitions() because the mac68k port does not
have an on-disk BSD disklabel, neglected to sign up BSD partitions for
newfs'ing and mounting by setting the appropriate flags."
Revert the commit to the install notes (rev. 1.14 of notes/mac68k/prep) which
added a warning and a workaround for this bug, as requested by hubertf in the
PR log.
${RELEASEDIR}/${MACHINE}. The former is the blessed way as it's
defined as a "subdirectory used below ${RELEASEDIR} when building a
release" and defaults to MACHINE in bsd.own.mk.
Make sure that ${RELEASEDIR}/${RELEASEMACHINEDIR} exists before
installing notes in to it. It only ever worked because ~all ports
build at least one kernel as part of make release, and so the release
directory was created when kernel sets are installed.
XXX: Why don't we create ${RELEASEDIR}/${RELEASEMACHINEDIR} from the
top-level makefile before running make release?
