o mount (and unmount) devfs in the chroot'd filesystem
o handle umounting devfs in case of a keyboard interrupt
o remove MAKEDEV from the fixit floppy so things fit again (mount_devfs was
added in a separate commit)
o explicitly remove mfsroot.gz and loader.conf when building the cd-rom area
as otherwice cp -Rp aborts when a previous run left identical files around
o increase the number of inodes on the drivers floppy; moving drivers from
the kernel there (to shrink it's size) caused things to overflow
o while we're increasing the driver's floppy inode config, separate out all
parameters from the boot floppy
Approved by: re
the BOOTMFS kernel. These help reduce the kernel size so things fit
in a floppy image. There are more low-hanging fruit to be had here
if things fail to fit again.
to reduce the size of the bootstrap kernels. This is needed to make
stuff fit in primary floppy images. Specific drivers moved: RAID
support, tx Ethernet, and wi (wireless). Probably want to revisit
at least the last two drivers before release.
Submitted by: jhay (mostly)
floppies.
kern-small.flp and mfsroot-small.flp are for old machines that don't
support 1.44MB floppy. These floppies don't have pci related devices.
kern.flp and mfsroot.flp are normal 1.44MB floppy images.
time before the release (novel concept for me, I know :( )
Translation updates:
hardware/alpha/proc-alpha.sgml: 1.41 -> 1.44
hardware/common/dev.sgml: 1.91 -> 1.106
hardware/i386/proc-i386.sgml: 1.2 -> 1.3
relnotes/common/new.sgml: 1.355 -> 1.432
relnotes/common/relnotes.ent: 1.2 -> 1.3
Translation fixes:
hardware/sparc64/proc-sparc64.sgml
installation/common/install.sgml
installation/common/trouble.sgml
installation/sparc64/install.sgml
readme/article.sgml
Affected by the removal of the seperate release.ent file (FINALLY!):
errata/article.sgml
hardware/alpha/article.sgml
hardware/i386/article.sgml
hardware/ia64/article.sgml
hardware/sparc64/article.sgml
installation/alpha/article.sgml
installation/i386/article.sgml
installation/sparc64/article.sgml
relnotes/alpha/article.sgml
relnotes/i386/article.sgml
relnotes/sparc64/article.sgml
share/sgml/catalog
share/sgml/release.dsl
share/sgml/release.ent
Changed for the addition of the PC98 release notes, German version
hardware/Makefile
installation/Makefile
relnotes/Makefile
hardware/common/hw.ent
(and of course all the new files for pc98)
Thanks again to Martin Heinen for cleanup.
in seperate directories. This mostly affects RELENG_4 where
not doing so results in ${CHROOTDIR}/usr/src/release being
filled with object files, and "srelease" distribution having
them in.
PR: misc/43825
Prodded by: re (murray)
to use DOC_LANG to specify which languages the doc/ is built for.
Note: be aware that the DOC_LANG setting in /etc/make.conf will now
take the effect on "make release". (This is probably the desired
behavior anyway.)
PR: docs/42924
under way to move the remnants of the a.out toolchain to ports. As the
comment in src/Makefile said, this stuff is deprecated and one should not
expect this to remain beyond 4.0-REL. It has already lasted WAY beyond
that.
Notable exceptions:
gcc - I have not touched the a.out generation stuff there.
ldd/ldconfig - still have some code to interface with a.out rtld.
old as/ld/etc - I have not removed these yet, pending their move to ports.
some includes - necessary for ldd/ldconfig for now.
Tested on: i386 (extensively), alpha
Modified release notes: newsyslog(8) now uses bzip2(1) by default.
Move two TCP-related release notes from the general kernel section to
the networking protocols section. Minor wording adjustment in one
item, note MFC of the other.
into the install kernel. Unfortunately pcn(4) also needs mii(4) so that
would also have to added to install kernel, which will bloat it up so that it
doesn't fit on the floppy any more. Turns out we grew a lnc(4) module since
I last looked. So handle it as a kld loadable module during install rather
than have it statically compiled into the kernel.
lnc(4) will attach to AMD PCnet/FAST NICs if pcn(4) does not attach.
I.e. pcn(4) gets first chance. There is a problem however in that pcn(4)
was moved out of the install kernel so that the module would be used.
This however causes bad installs if one has an AMD PCnet/FAST NIC.
and the TCP bandwidth delay product window limiting features.
note: the -current version of the retransmit timer defaults
to 200ms while the -stable version defaults to 1 second for now.
MFC after: 3 days
Modified release notes: em(4) has been reported to work on ia64,
OpenSSL 0.9.6g, tweak cross-building note and note MFC.
Remove an obsolete release note about DEC 3000 support on floppies.
release/${TARGET}/drivers.conf file which list drivers that have to
go into the third floppy.
Also shuffle i386/drivers.conf so that the floppies don't overflow
anymore. Anybody with real/better usage statistics is welcome to
shuffle it differently.
Reviewed by: ru
are no longer propagated to the chrooted environment, e.g. NOKERBEROS.
On the other hand, TMPDIR and MAKEOBJDIRPREFIX should no longer be.
Spotted by: Alexandr Listopad <laa@reis.zp.ua>
then download the distfiles for the ports needed to build the docs before
we enter the chroot environment. This is useful since often times releases
get in a funk trying to download distfiles in the chroot.
Approved by: re (murray, bmah)
MFC after: 5 days
Following a suggestion by Ruslan, the initial creation of the
includes and libraries (and build tools) is now done by
invoking "make buildworld" (with -DPICOBSD which eventually will
limit the amount of stuff built with a 2-line change in Makefile.inc1).
The correct environment is then used for subsequent builds.
Also remove write_mfs_in_kernel.c in favour of using dd
All the above is conditional on __FreeBSD_version, as the previous
method still worked for versions earlier than 500035, and I am
unsure on how the "new" method works for earlier versions.
Finally, note that the crunch.conf files need some work because
some libraries (e.g. gmd) have gone away from the base installation.
different architectures may choose to use different default values
for CFLAGS, for example. (It was added in rev. 1.200 as a measure
to make boot images fit the floppies, and was never reverted.)
Changed release notes: KSE (rewrite and status update), Binutils
2.12.1 (20020622 snapshot).
MFCs noted: libpcap-0.7.1, tcpdump-3.7.1, OpenSSH through 3.4p1.
Also retroactively note some OpenSSH items as MFC-ed and historic.
I'm not sure when these were merged, but I'm pretty sure it was a long
time ago.
no longer fits 1.44M but...
Moved vx(4) and all miibus consumers (including miibus) out
from kern.flp to mfsroot.flp. This leaves 9K of the free
space for kern.flp.
pam_ksu(8), uuidgen(1).
Updated release notes: libpcap-0.7.1, tcpdump-3.7.1.
Also do some markup fixes to recently-added items so that they don't
try to use entities for manpages that have been removed, in the spirit
of rev. 1.359.
filesystem expands the inode to 256 bytes to make space for 64-bit
block pointers. It also adds a file-creation time field, an ability
to use jumbo blocks per inode to allow extent like pointer density,
and space for extended attributes (up to twice the filesystem block
size worth of attributes, e.g., on a 16K filesystem, there is space
for 32K of attributes). UFS2 fully supports and runs existing UFS1
filesystems. New filesystems built using newfs can be built in either
UFS1 or UFS2 format using the -O option. In this commit UFS1 is
the default format, so if you want to build UFS2 format filesystems,
you must specify -O 2. This default will be changed to UFS2 when
UFS2 proves itself to be stable. In this commit the boot code for
reading UFS2 filesystems is not compiled (see /sys/boot/common/ufsread.c)
as there is insufficient space in the boot block. Once the size of the
boot block is increased, this code can be defined.
Things to note: the definition of SBSIZE has changed to SBLOCKSIZE.
The header file <ufs/ufs/dinode.h> must be included before
<ufs/ffs/fs.h> so as to get the definitions of ufs2_daddr_t and
ufs_lbn_t.
Still TODO:
Verify that the first level bootstraps work for all the architectures.
Convert the utility ffsinfo to understand UFS2 and test growfs.
Add support for the extended attribute storage. Update soft updates
to ensure integrity of extended attribute storage. Switch the
current extended attribute interfaces to use the extended attribute
storage. Add the extent like functionality (framework is there,
but is currently never used).
Sponsored by: DARPA & NAI Labs.
Reviewed by: Poul-Henning Kamp <phk@freebsd.org>
the size of the rendered release notes. By default, any element with
a role="historic" attribute won't get rendered in the output unless
the INCLUDE_HISTORIC Makefile variable is defined.
the second buildworld environment is fully isolated from parent's
environment variables.
Tested virtually on: snapshots.jp.FreeBSD.org
Approved by: arch@ (silently)
MFC after: 2 weeks
as of 4.6-RELEASE (or earlier). This commit shouldn't have any immediate
effect, but we'll eventually use some stylesheet magic to remove
the historic release notes from the output stream. This will have
the effect of making the 5.0-RELEASE release notes contain material
only relevent to -CURRENT *or* recently MFC-ed to 4-STABLE.
The stylesheet fixes will follow later, once I work out a couple more
details. I wanted to get this commit done now, before anything gets
MFC-ed in the post-4.6 world (so we don't need to go back later and
figure this out).
If a historic release note gets modified, it may very well be
appropriate to remove its historic attribute.
In fact, these variable are set as environment variables since we run
"make TARGET=xxx TARGET_ARCH=xxx"; TARGET and TARGET_ARCH are declared
in the command line arguments. However, if you are not make(1) guy,
it is hard to understand that TARGET/TARGET_ARCH are appropriately set
in a chroot environment (as environment variables).
Now, the only environment variable need to be set explicitly is 'PATH'.
If we set PATH in /mk script, we can make pristine sandbox for release
build (i.e., "env -i /usr/sbin/chroot ${CHROOT} /mk" will work).
Valuable comments about this issue from: ru
Tested on (virtually): snapshots.jp.FreeBSD.org
MFC after: 2 weeks
create a link to man.cgi with a manpath for 5-current. Following this
link gives a "Sorry, no data found for `labpc(4)'". Instead, simply
write labpc(4) without any markup (for which pkg_update(1) is prior art)
Remove some whitespace at EOL while I'm here.
Discussed with an okayed by: bmah
Just update the 'original revision' markers of some files where the last
update of the english version has no impact on the translated version
(spelling checks are a premium cause of this) except making it harder
to find the changes that still need to be translated/comitted.
is still ongoing), catman(1) rewrite, makewhatis(1) rewrite,
spkrtest(8) rewrite.
Modified release note: killall(1) for markup.
Deleted release notes: Perl upgrade, style.perl(7) manpage, one note
about killall(1) was obsolete.
arch. This makes "make release TARGET_ARCH=foo" really work.
(I only tested with "make rerelease" before to save some time and did
not notice the problem.)
fsdb(8) blocks (+MFC), who(1) -H/-T/-m/-u/-q, xargs(1) -L, general
note on SuSv3/POSIX.1 conformance.
Modified release notes: The system awk is now BWK awk (noted in three
places), uudecode(1)/uuencode(1) -o/-m (+MFC), xargs(1) -I/-J.
