2. Ensure all &arch entities end with ';' (no effect on output).
3. Ensure all &arch lists for drivers/features are comma-separated.
PR: docs/127840 (item 2 only)
MFC after: 1 week
port.
2. Increase the known working maximum memory configuration from
8gb to 32gb.
PR: docs/102148 (1)
Submitted by: Mike Meyer <mwm@mired.org> (1 - partially)
Reviewed by: hrs
Approved by: re (hrs)
MFC after: 1 minute
1. separating L2 tables (ARP, NDP) from the L3 routing tables
2. removing as much locking dependencies among these layers as
possible to allow for some parallelism in the search operations
3. simplify the logic in the routing code,
The most notable end result is the obsolescent of the route
cloning (RTF_CLONING) concept, which translated into code reduction
in both IPv4 ARP and IPv6 NDP related modules, and size reduction in
struct rtentry{}. The change in design obsoletes the semantics of
RTF_CLONING, RTF_WASCLONE and RTF_LLINFO routing flags. The userland
applications such as "arp" and "ndp" have been modified to reflect
those changes. The output from "netstat -r" shows only the routing
entries.
Quite a few developers have contributed to this project in the
past: Glebius Smirnoff, Luigi Rizzo, Alessandro Cerri, and
Andre Oppermann. And most recently:
- Kip Macy revised the locking code completely, thus completing
the last piece of the puzzle, Kip has also been conducting
active functional testing
- Sam Leffler has helped me improving/refactoring the code, and
provided valuable reviews
- Julian Elischer setup the perforce tree for me and has helped
me maintaining that branch before the svn conversion
freaks me out. But it turns out we might be able to generalize
a few of the other things RE uses to assemble the package trees
for releases if the DVDs use a naming theme close to what is used
for the CDROMS (disc1, disc2, etc). So change the name to dvd1.
Hopefully this way src/release/scripts/{package-split.py,package-trees.sh}
can be generalized instead of copied-and-hacked.
MFC after: 5 days
or not to build a tree used for the creation of a DVD image. If that is
enabled set up a DVD tree by installing everything we normally install
to the individual CDROM trees into the one DVD tree. The result is one
image with all the install bits, livefs bits, and doc bits suitable for
burning to a DVD instead of CDROM.
Enable building the DVD for amd64 and i386.
MFC after: 1 week
- Add support for .Fx, just in case somebody starts using it.
- Only add the arch information to the first para per manual page.
This improves output for axe(4), and generally seems to make sense
(I hope).
- Remove an unneeded line for non-compat mode.
This removes some vertical whitespace in the output.
Whitespace was intentionally not fixed in the SGML for the related
lists, to make the actual change more clear. This file is in need of
a major whitespace cleanup anyway.
complains about "Malformed numbers" while unpacking the dists and
what winds up on the disk isn't correct. Use this as an opportunity
to switch over to bsdcpio since at this point we don't even build
and install the gnu cpio by default. Note sysinstall needed to be
tweaked a bit (dropping tape block size setting) because it seems
bsdcpio doesn't do anything with block sizes, at least as far as
reading from archives goes. That wasn't really a problem since
installations from tape have been broken for a while and the rest
of sysinstall's tape support code will be removed shortly.
mininal set of ports required to make the docs. However,
we also need ports/sysutils/cdrtools in order to make the
ISO images. When a platform doesn't have packages, the
release will fail in that case. Add ports/sysutils/cdrtools
to RELEASEPORTSMODULE for the DOMINIMALDOCPORTS case to
handle the NOPORTS release build.
Note that this change doesn't try to handle the NOPORTS with
NODOC case. For we have NOPORTSATALL set and it seems wrong
to check out a ports module in that case.
- It is opt-out for now so as to give it maximum testing, but it may be
turned opt-in for stable branches depending on the consensus. You
can turn it off with WITHOUT_SSP.
- WITHOUT_SSP was previously used to disable the build of GNU libssp.
It is harmless to steal the knob as SSP symbols have been provided
by libc for a long time, GNU libssp should not have been much used.
- SSP is disabled in a few corners such as system bootstrap programs
(sys/boot), process bootstrap code (rtld, csu) and SSP symbols themselves.
- It should be safe to use -fstack-protector-all to build world, however
libc will be automatically downgraded to -fstack-protector because it
breaks rtld otherwise.
- This option is unavailable on ia64.
Enable GCC stack protection (aka Propolice) for kernel:
- It is opt-out for now so as to give it maximum testing.
- Do not compile your kernel with -fstack-protector-all, it won't work.
Submitted by: Jeremie Le Hen <jeremie@le-hen.org>
syscons(4) Colemak keyboard layout support,
jme(4) for JMicron JMC250 Gigabit/JMC260 Fast Ethernet controllers,
ISDN4BSD and netatm removal,
libarchive-based cpio added and GNU cpio renamed as gcpio,
jexec(8) -j option added,
ping6(8) return value is now the same as ping(8),
tar(1) --numeric-owner, -S, and -s options added, and
pkg_create(1) -n option added.
a bogus partition table and puts the file system on the whole
partition. geom_part doesn't expose the 'c' partition as it's an
artifact of the BSD label and not to be used. Secondly, gpart(8)
is the preferred tool for partitioning disks on ia64.
can't find fsck_4.2bsd because there was no fstab file saying what
filesystem type it is looking at so it got the filesystem type from
the disk's label. When that fails admins who haven't been in this
situation before are most likely to try "fsck -t ufs /dev/ad0s1a" because
ufs is the type used in fstab files on working systems but that also fails
complaining it can't find fsck_ufs.
This just sets it up so /stand in the MFS image (/sbin is a symlink
to /stand) includes hard links pointing fsck_4.2bsd and fsck_ufs to
fsck_ffs which is what is present in /sbin on installed systems.
Prodded by: obrien
MFC after: 1 day
shell. This would break them for floppy based fixit mode which still
seems to use /stand except that vi(1) and more(1) don't exist in /stand
on the fixit floppy so it really doesn't matter what these settings are
there. These paths work for CD-based fixit mode.
This is just "temporary" and on its way to 7.0-REL. I'm too chicken to
make what is probably the correct adjustment this close to release. It
seems /mnt2 is just a symbolic link, and stuff really gets mounted as
/dist. Adjusting paths to that for 8.X is probably the right thing to
do and I'll try that after 7.0 is done.
Noticed by: gallatin
MFC after: 1 day
binaries for the fixit floppy bin/ed/main.c causes a gcc warning
message about argc possibly being clobbered by longjmp or vfork.
We have threatened to ditch floppies for 8.0 but I don't want to
do quite that much rototilling yet so for now turn off -Werror while
building ed (and everything else) for the fixit floppy.
Thanks to jb for pointing out NO_WERROR.
is enabled). This saves around 80MB (for i386) on the ISO images.
Note that this is only from the install media, not the installed
system where the symbols are still installed, if part of the release.
Should anybody want the symbols which match disc1/livecd, they can
just be extracted from the kernel distribution files.
Reviewed by: kensmith
floppy types (in fact, we have only one left!)
Also cleanup some code, using || and && in some places, and
using "export VAR=value" instead of two separate lines.
- use proper make configuration for the build, using
${BINMAKE} as evaluated by ${VERSION}/src/Makefile
- remove -lmytinfo from crunch.conf
- remove support for login_access in tinyware/login
- remove "machine i386" from the kernel config file
It might actually be interesting to extend the script to do
a cross build for !i386 ...
MFC after: 3 days
- Mention tzdata2007h update. An in advance &merged; is
added so that we don't have to change this again when
it is actually MFC'ed.
Approved by: re (bmah)
unusability of OFW consoles. [1]
Try to use trademark entities where appropriate in the "Supported
Processors" section.
Submitted by: kris [1]
Approved by: re (implicitly)
- ng_h4(4) MPSAFE
- ng_ppp(4) MPSAFE + MFC
- zyd(4) added
- cpufreq(4) in GENERIC
Modified release notes:
- cached(8) renamed to nscd(8), also moved entry to now correct place
- Camellia is now supported in geli(8) as well
Approved by: re (blanket)
Updated release note: tzdata2007g [1].
[1] Technically I should remove the &merged; entity here but the commit has
a one-week MFC-after so I figure I can leave it this way for now.
Approved by: re (implicitly)
pointer to the installation chapter of the Handbook (it might be a
good idea to sprinkle a few more through this article).
De-emphasize the floppy disk part of installation media; it's
generally believed that most users install from CDROM or DVD
nowadays.
Use &arch.* entities where appropriate.
Bump copyright date while here.
Approved by: re (implicitly)
top-level release/doc directory. We were building in share/sgml first,
which caused us to autogenerate hardware notes entities in the wrong
format (we want to build these via ${RELNOTES_LANG}/hardware/Makefile,
in order to get the HWNOTES_MI variable).
Approved by: re (kensmith)
for quite some time. All relevant content has been moved to the
installation chapter of the FreeBSD Handbook, which will be the
single source of FreeBSD installation instructions.
In addition to removing redundancy, this change also removes the last
of the machine-dependent documents in the release documentation
set (the release notes and hardware notes were unified to produce
machine-independent documents).
Approved by: re (blanket for installation notes removal)
Nods from: blackend, brueffer, simon, trhodes
No objections on: doc@
Helpful hints from: blackend
floppies or ISO images). We retain the concept of MD
release documentation for now, although it's fairly unlikely
that we'll ever do this again.
Approved by: re (blanket for installation guide removal)
API change.
Modified release notes: Clarify architectures for nfe(4) note and
mention that it replaces nve(4) in i386/amd64 GENERIC [1].
Suggested by: Michael Plass [1]
Approved by: re (implicitly)
Add some more verbage with respect to jemalloc and resource limits [2].
Submitted by: delphij [1]
Collaboration with: jasone [2]
Approved by: re (implicit)
- tmpfs on i386,amd64
- gem(4) altq support
- AUDIT and SCTP in GENERIC
- FireWire MPSAFE
- netstat SCTP support
- dhclient RFC 3442 support (1)
Modified release notes:
- MFC markers: mxge(4) and netcat
- touch -A entry grammar fix (2)
- More manpage references used
Submitted by: Andrey V. Elsukov (1)
ceri (2)
Approved by: re (blanket)
/etc/rc.d/sendmail whether or not to run newaliases if the database
is missing or the aliases text file is newer than aliases.db.
In my opinion, the aliases file should never be automatically rebuilt.
The current text form could represent a work in progress. Therefore,
in FreeBSD 7.0, this new option will default to "NO". When this rc.d
change is MFC'ed, it will need to remain "YES" to maintain backward
compatibility.
PR: conf/86252
Approved by: re (kensmith)
MFC after: 3 days
- GCC SSP enabled by default
- X11BASE change
- touch -A
- fwip(4) and dcons(4) in GENERIC
- FireWire/dcons support in the i386/amd64 loader
Modified release notes:
- MFCs noted: newly supported ftpd RFCs, lagg(4), mpt(4) changes,
snd_atiixp(4) suspend/resume
- sa(8) entry moved to the correct place
- xorg 7.2 update
went away around the time of 5.0, when doing binary upgrades from
within sysinstall (at least from 4.X) was deemed hazardous due to the
huge differences between these two major versions.
It's much less risky now, and it's also high time that we mentioned
freebsd-update(8) too.
release documentation from *.TXT files to the RELNOTESng *.sgml
files. I'm pretty sure that, five years later, nobody is wondering
where the original *.TXT files went to in our source tree, so
remove this file to declutter the source tree a bit.
that can be used for resizing NTFS partitions (to make room for
FreeBSD).
Based on some text that was...
Submitted by: Hal Burch, Szakacsits Szabolcs
PR: 65477
MFC after: 3 days
- edsc(4) added
- pmcstat(4) -c and -t flags, defaults changed
- rpcbind -h and -6 flags
Modified release notes:
- Moved pmcstat information from kernel to userland section
- MSI-X supported as well, remove ref to pci(4) manpage, which is
different from the kernel's PCI code
- rpc.lockd/rpc.statd entry moved to the right place
- IPLware 3.33 support for pc98
- CAM MPSAFE
- ahc(4) and ahd(4) MPSAFE
- pseudofs(9) and consumers MPSAFE
- OpenBSM 1.0 alpha 14
- lastcomm -X flag
- ftpd(8) RFC2389 and RFC2640 support
Modified release notes:
- ncurses was updated from version 5.2-20020615
While here, moved the lagg(4) and XFS entries to the correct places.
the following ports tree changes:
- libtool13 removed.
- pkgconfig moved to pkg-config.
- Default dependency for USE_GHOSTSCRIPT changed from
ghostscript-gnu to ghostscript-gpl.
- Also added missing docproj dependencies.
Reported by: Dmitriy Kirhlarov
Submitted by: sem, ru
MFC after: 3 days
- priv(9) KPI added
- ipw/iwi firmware in the base system
Updated release notes:
- OpenSSL updated to 0.9.8e
- GNOME updated to 2.8.0
- acpi_dock(4) and acpi_hpet MFC
- msk(4) MFC
now contained entirely in a single DocBook article, which has
information pertinent to all architectures. This will improve
the maintainability of the hardware notes going forward by
reducing complexity of the build process, improving the visibiilty
of the architecture-specific text, and removing the need to generate
an extra version of the document for every architecture.
Remove all of the MD hardware notes stuff; all relevant content
has been folded into hardware/article.sgml.
No objections from: freebsd-doc@
manner consistent with the new MI-style hardware notes document.
man2hwnotes.pl now defaults to generating entities for the MI-style
hardware notes (i.e. hardware/article.sgml). A new -c
option causes it to generate entities for the older MD-style
hardware notes (i.e. hardware/common/dev.sgml).
The Makefile infrastructure supplies the -c option to man2hwnotes.pl
now unless the HWNOTES_MI Makefile variable is defined, so
compatiblity is preserved for hardware notes translations that
aren't converted to the new organization yet. As translations
convert, they should define HWNOTES_MI in their hardware/Makefile.
When all the relevant translations catch up, the compatibility goop
in share/mk/doc.relnotes.mk and share/sgml/Makefile can be removed.
Thanks go to simon@ for help with the backwards compatiblity
mechanism.
Tested with: en_US.ISO8859-1, zh_CN.GB2312
Convert MD references in the supported devices section from arch=""
attributes for conditional compilation to entities that will just
print architecture names. (The entities aren't defined yet...this
will happen in a future commit.)
Rather than rendering a different version of the release notes for
every architecture, we now produce a single release notes document
that covers all architectures.
This change makes document maintenence easier (because there is no
longer a need to support each architecture specifically in the
src/release/doc/ and www/ build infrastructures). It's also
easier to read because there is now exactly one release notes document,
and readers can see changes that affected various subsets of
architectures.
Discussed on: -doc@
them unsigned I made the possible overflows hard to detect,
and it only saved 1 bit which isn't principal, even less now
that the underlying issue with the total of virtual memory has
been fixed. (For the record, it will overflow with >=2T of
VM total, with 32-bit ints used to keep counters in pages.)
- While here, fix printing of other "struct vmtotal" members
such as t_rq, t_dw, t_pw, and t_sw as they are also signed.
Reviewed by: bde
MFC after: 3 days
- Fix overflow bugs in sysctl(8), systat(1), and vmstat(8)
when printing values of "struct vmmeter" in kilobytes as
they don't necessarily fit into 32 bits. (Fix sysctl(8)
reporting of a total virtual memory; it's in pages too.)
packages on disc2. This will also let users decide if they want to
have a CD of the docs at all - unless they're disconnected from the
net they will probably find the Web site more useful.
Reviewed by: ru
MFC after: 3 days
it possible to e.g. distribute kernels with config names larger
than eight symbols, without the clash. Previousy, LALALALA
and LALALALA-SMP would be the same tarball. (I think this
comes from the old days where tarballs were put on the MS-DOS
formatted diskettes.)
MFC after: 3 days
fsdb(8) btime.
Modified release notes: Changed Xbox note to only point to the
platforms page (there are pointers to additional information
there)...note MFC.
MFCs noted: IPFilter 4.1.13.
what's going on in cases where the "state engine" doesn't act as
expected, e.g. in the case of a list not being closed in the manual
page being parsed.
- Bump copyright year.
MFC after: 1 week
