Commit Graph

384 Commits

Author SHA1 Message Date
brooks
1f3769b470 Note the deprecation of the abbreviation of a number of ipfw options. 2005-01-15 01:53:49 +00:00
ru
8666720902 Warn about the NOFOO -> NO_FOO conversion, and remind users to
read the COMMON ITEMS section of this file for proper upgrade
instructions.
2004-12-23 16:03:08 +00:00
sam
1d13972272 Note requirement to manually load/configure ancillary wlan modules.
Requested by:	silby
2004-12-20 04:27:23 +00:00
brian
e16d632c18 Mention the necessity for ``enable echo'' in ppp(8). 2004-12-13 17:52:10 +00:00
obrien
733d63140d Slightly embelish the 20040710 entry about the requirement for
'hint.sio.0.flags="0x10"' on Alpha.

Also move the sio name changes to chronological change order.
2004-12-12 07:22:16 +00:00
sam
b1b615a9fb note ath+wlan changes 2004-12-11 23:21:31 +00:00
mlaier
d7a4686564 Remove some (no longer vaild) notes about PFIL_HOOKS. 2004-12-08 04:08:33 +00:00
jhb
1facc14f4c Add a note about 80386 support being removed from HEAD. 2004-11-16 21:18:41 +00:00
phk
47d248f4ca Add note about changed root mount semantics for (preloaded) memory disks 2004-11-10 07:39:27 +00:00
andre
d06f3bef4e Remove RFC1644 T/TCP support from the TCP side of the network stack.
A complete rationale and discussion is given in this message
and the resulting discussion:

 http://docs.freebsd.org/cgi/mid.cgi?4177C8AD.6060706

Note that this commit removes only the functional part of T/TCP
from the tcp_* related functions in the kernel.  Other features
introduced with RFC1644 are left intact (socket layer changes,
sendmsg(2) on connection oriented protocols)  and are meant to
be reused by a simpler and less intrusive reimplemention of the
previous T/TCP functionality.

Discussed on:	-arch
2004-11-02 22:22:22 +00:00
andre
a8987888fb Shave 40 unused bytes from struct tcpcb. 2004-10-22 19:55:04 +00:00
phk
0e4076f54e Add an entry about some tty devices being renamed. 2004-10-18 21:24:21 +00:00
obrien
e41071dc59 Remove the suggestion to use libmap.conf to deal with the version bump.
People have a tendency to add things to libmap.conf and forget about them
(as we've seen in the mailing lists before).
The compat4x port should be used instead.
2004-10-17 14:59:18 +00:00
mtm
9763558fd4 Add additional information on how to cope with the change. 2004-10-10 16:12:09 +00:00
mtm
15ba1cfe47 2004-10-07 14:06:23 +00:00
mtm
c95a2c6f6b Note libthr ABI breakage. 2004-10-07 05:45:39 +00:00
dougb
c5171b8fc8 Make it more clear that if named is enabled, it will be chrooted by default.
Change to syslogd restart as suggested by des.
2004-10-04 20:11:34 +00:00
des
be3092c71a Document how to set up libmap.conf to deal with the library version bump. 2004-10-03 10:08:12 +00:00
kensmith
911789fdaa Bump the library version numbers for the following libraries:
/lib/{libm,libreadline}
	/usr/lib/{libhistory,libopie,libpcap}

in preparation for doing the same thing to RELENG_5.  HUGE amounts of
help for determining what to bump provided by kris.

Discussed on:	freebsd-current
Approved by:	re (not required for commit but something like this should be)
2004-10-01 15:38:07 +00:00
mlaier
b65eae4c19 Add an additional struct inpcb * argument to pfil(9) in order to enable
passing along socket information. This is required to work around a LOR with
the socket code which results in an easy reproducible hard lockup with
debug.mpsafenet=1. This commit does *not* fix the LOR, but enables us to do
so later. The missing piece is to turn the filter locking into a leaf lock
and will follow in a seperate (later) commit.

This will hopefully be MT5'ed in order to fix the problem for RELENG_5 in
forseeable future.

Suggested by:		rwatson
A lot of work by:	csjp (he'd be even more helpful w/o mentor-reviews ;)
Reviewed by:		rwatson, csjp
Tested by:		-pf, -ipfw, LINT, csjp and myself
MFC after:		3 days

LOR IDs:		14 - 17 (not fixed yet)
2004-09-29 04:54:33 +00:00
dougb
84038e9ef8 Amend the named chroot update instructions by adding a stop and start
of syslogd. The rc.d/syslogd script has the logic already to create
a socket in the chroot dir, it just needs to be restarted.

Reminded by:	matusita
2004-09-28 13:44:41 +00:00
dougb
a0c7847c5b Create a named chroot directory structure in /var/named, and use it
by default when named is enabled. Also, improve our default directory
layout by creating /var/named/etc/namedb/{master|slave} directories,
and use the former for the generated localhost* files.

Rather than using pax to copy device entries, mount devfs in the
chroot directory.

There may be some corner cases where things need to be adjusted,
but overall this structure has been well tested on a production
network, and should serve the needs of the vast majority of users.

UPDATING has instructions on how to do the conversion for those
with existing configurations.
2004-09-28 09:46:00 +00:00
dougb
dc4195df1c Update the BIND 9 entry with information about files that
have moved, or should be removed.
2004-09-26 07:50:23 +00:00
dougb
954ae57b98 Add an entry to tell the world about BIND 9. 2004-09-25 03:41:38 +00:00
andre
197eb4f541 Backout the last entry. It went to the wrong branch. 2004-09-22 20:42:30 +00:00
andre
116dc0a8cc MFC: Make PFIL_HOOKS a permanent part of the kernel and remove the associated
kernel compile option.

Approved by:	re (scottl)
2004-09-22 19:23:39 +00:00
seanc
7580811af2 Bring back etc/rc.d/ntpdate as requested by scads of people. This isn't a
complete backout as the ntpd_sync_on_start etc/rc.conf tunable is still
present, though the default is now NO (was YES).  Since we're no longer
syncing time at startup by default when ntpd is enabled (as was the case
24hrs ago), remove UPDATING entry pointing out that ntpd(1) -g is slower
than ntpdate(1).

Hopefully ntpd_sync_on_start="YES" can be made the default for -CURRENT
after 5.3 is cut.  At the very least, this should be set to YES when a
user requests to have ntpd enabled via sysinstall(1).

Requested by:	many
2004-09-15 01:08:33 +00:00
seanc
dcf0d84fcd Stop using ntpdate(1) in our startup proceedure. Replace ntpdate(1) with
calls to ntpd -g.  ntpd is noticably slower than ntpdate, but is also more
accurate.  This removes the nasty hackery in rc.d/ntpdate that would parse
out ntp servers from /etc/ntp.conf (ntpd knows how to read its own config
file).  By default, ntpd *will* sync with its listed time servers.  To
turn this off so that ntpd does not sync, ntpd_sync_on_start="NO" can be
added to /etc/rc.conf.  If ntpd is not enabled (the default), then time is
not synced on startup.  ntpdate's use has been depreciated by the ntpd
authors for quite some time so this change shouldn't be unexpected.

Suggested by:	des
Approved by:	roberto (resident ntp guru)
2004-09-14 03:01:38 +00:00
mlaier
c3040d05d9 Put in a note about the changed pflogd format (for 64 bit archs). 2004-09-14 02:39:55 +00:00
jmg
3db8b85883 document the recent change to debug.witness.*
fix spelling of debug.witness.kdb

MFC after:	5 days
2004-09-06 23:37:17 +00:00
imp
141fd6eb39 Expand the 4.x -> current updating section. Update to show how to use
make kernel.  Update the compatibility slice section.  Note about
updating devices in the kernel config file.  MAKEOBJDIRPREFIX changes
and mention the port alternative to COMPAT4X=yes.  Fix copyright.

This should be MFC'd.
2004-09-04 21:03:10 +00:00
brooks
9baee72236 Back out ifi_epoch. The ABI breakage is too disruptive this close to
5-STABLE. ifi_epoch will shortly be reintroduced with less precistion
using the space currently allocated to ifi_unused.
2004-09-02 05:07:29 +00:00
brooks
aac3e70226 Add warnings about ifconfig incompatabilities caused by the addition of
ifi_epoch.
2004-09-01 15:14:13 +00:00
brooks
922e581a21 Add a new variable, ifi_epoch, to struct if_data. It is set to the last
time the interface counters were zeroed, currently the time if_attach()
was called.  It is indentended to be a valid value for RFC2233's
ifCounterDiscontinuityTime and to make it easier for applications to
verify that the interface they find at a given index is the one that was
there last time they looked.

An if_epoch "compatability" macro has not been created as ifi_epoch has
never been a member of struct ifnet.

Approved by:	andre, bms, wollman
2004-08-30 06:29:26 +00:00
rwatson
25e168c12a Add an updating entry for the recent change in network stack locking
default for debug.mpsafenet, pointing at the recent announcement and
things to try if instability is experienced.
2004-08-28 17:08:30 +00:00
andre
d243747d92 Always compile PFIL_HOOKS into the kernel and remove the associated kernel
compile option.  All FreeBSD packet filters now use the PFIL_HOOKS API and
thus it becomes a standard part of the network stack.

If no hooks are connected the entire packet filter hooks section and related
activities are jumped over.  This removes any performance impact if no hooks
are active.

Both OpenBSD and DragonFlyBSD have integrated PFIL_HOOKS permanently as well.
2004-08-27 15:16:24 +00:00
imp
3b8f16bada Recommend using make kernel for current -> current upgrades. No reason
to have multiple commands for that.
Use relative paths into the src tree consistantly in the instructions.
Fix minor nits that have crept into things.

# is preseedrandom still necessary?
2004-08-25 19:39:13 +00:00
imp
41e5880d79 Add a blanket note about 5.x being the same as 6.0 and vice versa for
the time being.  Also add a note that says we are going to remove the
band-aides for 4.early -> 6.0 after 5.3-RELEASE so people get used to
the idea, even though it has been planned since before 5.0 was
released.
2004-08-23 18:51:36 +00:00
imp
2ce9ba8acb Two items:
o we're 6.x now, so say so in the first few lines of the file.
	o note that I'll be trimming this file around 5.3 release time.
2004-08-23 18:47:13 +00:00
obrien
7e4379230d Hit people over the head so they realize run-time errors of the form
/libexec/ld-elf.so.1: Undefined symbol "_ZNSs20_S_empty_rep_storageE"
does mean they are hitting the GCC 3.4 ABI change issue.
2004-08-21 19:44:43 +00:00
julian
fe9f220a60 Align netgraph message fields ready for 64-bit (and 128 bit :-) machines.
requires a recompile of netgraph users.
Also change the size of a field in the bluetooth code
that was waiting for the next change that needed recompiles so
it could piggyback its way in.

Submitted by:	jdp, maksim
MFC after:	2 days
2004-08-20 01:24:23 +00:00
andre
5681dff740 Fix spelling error in my last blurb.
Pointed out by:	ru
2004-08-19 19:45:28 +00:00
andre
a286477242 Put in a note about the ipfw to pfil_hooks conversion and the requirement
of having said in the kernel to be able to use ipfw.
2004-08-19 18:54:54 +00:00
dwmalone
2a8512cc38 Add a note about RANDOM_IP_ID. 2004-08-14 16:16:01 +00:00
ru
88ee315d1d Proofreading the 4.x -> 5.x upgrade procedure. 2004-08-13 13:14:05 +00:00
ru
155b11f9d0 Spell check the 20040806 entry. 2004-08-12 06:25:05 +00:00
jmg
d06adac9a4 add comment about needing to upgrade loader.rc on i386 systems that have
problems loading modules...

Solution by:	ru
2004-08-12 00:00:15 +00:00
mlaier
fd24e0374c Add another UPDATING entry about recompiling modules implementing network
interfaces due to a change in the size of struct ifnet.
2004-08-07 09:41:30 +00:00
imp
74250a12b7 Since we upgraded compilers, and the kernel build to match, we can't build
new kernels on older userlands.  Document this fact in the entry that talked
about the system upgrade.
2004-08-07 04:17:03 +00:00
markm
4f0e0f97f5 Update for the null.ko removal. 2004-08-03 19:29:48 +00:00