summaryrefslogtreecommitdiffstats
path: root/UPDATING
Commit message (Collapse)AuthorAgeFilesLines
* Warn about the NOFOO -> NO_FOO conversion, and remind users toru2004-12-231-0/+7
| | | | | read the COMMON ITEMS section of this file for proper upgrade instructions.
* Note requirement to manually load/configure ancillary wlan modules.sam2004-12-201-0/+9
| | | | Requested by: silby
* Mention the necessity for ``enable echo'' in ppp(8).brian2004-12-131-0/+7
|
* Slightly embelish the 20040710 entry about the requirement forobrien2004-12-121-11/+13
| | | | | | 'hint.sio.0.flags="0x10"' on Alpha. Also move the sio name changes to chronological change order.
* note ath+wlan changessam2004-12-111-0/+12
|
* Remove some (no longer vaild) notes about PFIL_HOOKS.mlaier2004-12-081-13/+3
|
* Add a note about 80386 support being removed from HEAD.jhb2004-11-161-0/+4
|
* Add note about changed root mount semantics for (preloaded) memory disksphk2004-11-101-0/+8
|
* Remove RFC1644 T/TCP support from the TCP side of the network stack.andre2004-11-021-0/+5
| | | | | | | | | | | | | | | | 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
* Shave 40 unused bytes from struct tcpcb.andre2004-10-221-0/+5
|
* Add an entry about some tty devices being renamed.phk2004-10-181-0/+8
|
* Remove the suggestion to use libmap.conf to deal with the version bump.obrien2004-10-171-10/+0
| | | | | | 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.
* Add additional information on how to cope with the change.mtm2004-10-101-0/+4
|
* F˜mtm2004-10-071-0/+5
|
* Note libthr ABI breakage.mtm2004-10-071-0/+5
|
* Make it more clear that if named is enabled, it will be chrooted by default.dougb2004-10-041-3/+2
| | | | Change to syslogd restart as suggested by des.
* Document how to set up libmap.conf to deal with the library version bump.des2004-10-031-0/+10
|
* Bump the library version numbers for the following libraries:kensmith2004-10-011-0/+15
| | | | | | | | | | | /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)
* Add an additional struct inpcb * argument to pfil(9) in order to enablemlaier2004-09-291-0/+5
| | | | | | | | | | | | | | | | | | | 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)
* Amend the named chroot update instructions by adding a stop and startdougb2004-09-281-0/+2
| | | | | | | 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
* Create a named chroot directory structure in /var/named, and use itdougb2004-09-281-0/+27
| | | | | | | | | | | | | | | | 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.
* Update the BIND 9 entry with information about files thatdougb2004-09-261-0/+9
| | | | have moved, or should be removed.
* Add an entry to tell the world about BIND 9.dougb2004-09-251-0/+13
|
* Backout the last entry. It went to the wrong branch.andre2004-09-221-5/+0
|
* MFC: Make PFIL_HOOKS a permanent part of the kernel and remove the associatedandre2004-09-221-0/+5
| | | | | | kernel compile option. Approved by: re (scottl)
* Bring back etc/rc.d/ntpdate as requested by scads of people. This isn't aseanc2004-09-151-10/+0
| | | | | | | | | | | | | | 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
* Stop using ntpdate(1) in our startup proceedure. Replace ntpdate(1) withseanc2004-09-141-0/+10
| | | | | | | | | | | | | | 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)
* Put in a note about the changed pflogd format (for 64 bit archs).mlaier2004-09-141-0/+6
|
* document the recent change to debug.witness.*jmg2004-09-061-0/+5
| | | | | | fix spelling of debug.witness.kdb MFC after: 5 days
* Expand the 4.x -> current updating section. Update to show how to useimp2004-09-041-12/+22
| | | | | | | | 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.
* Back out ifi_epoch. The ABI breakage is too disruptive this close tobrooks2004-09-021-0/+8
| | | | | 5-STABLE. ifi_epoch will shortly be reintroduced with less precistion using the space currently allocated to ifi_unused.
* Add warnings about ifconfig incompatabilities caused by the addition ofbrooks2004-09-011-0/+9
| | | | ifi_epoch.
* Add a new variable, ifi_epoch, to struct if_data. It is set to the lastbrooks2004-08-301-0/+5
| | | | | | | | | | | | | 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
* Add an updating entry for the recent change in network stack lockingrwatson2004-08-281-0/+13
| | | | | default for debug.mpsafenet, pointing at the recent announcement and things to try if instability is experienced.
* Always compile PFIL_HOOKS into the kernel and remove the associated kernelandre2004-08-271-0/+4
| | | | | | | | | | | 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.
* Recommend using make kernel for current -> current upgrades. No reasonimp2004-08-251-10/+9
| | | | | | | | 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?
* Add a blanket note about 5.x being the same as 6.0 and vice versa forimp2004-08-231-3/+10
| | | | | | | 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.
* Two items:imp2004-08-231-2/+4
| | | | | 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.
* Hit people over the head so they realize run-time errors of the formobrien2004-08-211-5/+8
| | | | | /libexec/ld-elf.so.1: Undefined symbol "_ZNSs20_S_empty_rep_storageE" does mean they are hitting the GCC 3.4 ABI change issue.
* Align netgraph message fields ready for 64-bit (and 128 bit :-) machines.julian2004-08-201-0/+7
| | | | | | | | | | 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
* Fix spelling error in my last blurb.andre2004-08-191-1/+1
| | | | Pointed out by: ru
* Put in a note about the ipfw to pfil_hooks conversion and the requirementandre2004-08-191-0/+8
| | | | of having said in the kernel to be able to use ipfw.
* Add a note about RANDOM_IP_ID.dwmalone2004-08-141-0/+5
|
* Proofreading the 4.x -> 5.x upgrade procedure.ru2004-08-131-3/+3
|
* Spell check the 20040806 entry.ru2004-08-121-1/+1
|
* add comment about needing to upgrade loader.rc on i386 systems that havejmg2004-08-121-0/+9
| | | | | | problems loading modules... Solution by: ru
* Add another UPDATING entry about recompiling modules implementing networkmlaier2004-08-071-0/+5
| | | | interfaces due to a change in the size of struct ifnet.
* Since we upgraded compilers, and the kernel build to match, we can't buildimp2004-08-071-0/+5
| | | | | new kernels on older userlands. Document this fact in the entry that talked about the system upgrade.
* Update for the null.ko removal.markm2004-08-031-0/+4
|
* Announce the memory device module update.markm2004-08-011-0/+5
|
OpenPOWER on IntegriCloud