summaryrefslogtreecommitdiffstats
path: root/UPDATING
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* Get the current year number straight and remove one instance of trailingkan2004-07-291-2/+2
| | | | | | whitespace. Time travel spoiled by: ru
* Document /usr/ports/UPDATING and have a brief pointer re x11imp2004-07-291-0/+4
|
* Add a note about recent GCC import.kan2004-07-291-0/+11
|
* back out the localkg changes until things have settled.eik2004-07-281-13/+0
| | | | Discussed with: mtm
* Add an UPDATING entry about recompiling modules implementing networkrwatson2004-07-271-0/+6
| | | | interfaces due to a change in the size of struct ifnet.
* Typo.mtm2004-07-251-1/+1
| | | | Submitted By: demon
* Ports related rc.d cleanups:mtm2004-07-241-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | o Separate out local (ports) scripts that use rc.d, and the old style startup/shutdown scripts and execute them separately. On startup the rc.d style scripts are executed first and then the old-style scripts. On shutdown, exactly the reverse happens. o The rc.d ports scripts should now behave more like base system scripts. Scripts ending in .sh will be sourced into the current shell, while the rest will be executed in a subshell. Previously, all ports scripts, regardless of the .sh suffix, were executed in a subshell. o The parent script, /etc/rc.d/localpkg, passes its command line arguments straight to the rc.d ports scripts. This means they should now honor faststop and faststart commands as well. Old style scripts, should not see any differences. They will still get either a start or stop command. o The initial phrase shown during shutdown has been changed to use "local packages" instead of "daemon processes" to be more inline with the phrase used during local package startup. The phrases are also used only for old-style ports script startup/shutdown, whereas previously they were being used for both rc.d and old-style scripts. This should make startup/shutdown output a bit less ugly. Discussed with: portmgr Has Reservations: eik
* English fixes, no content change.schweikh2004-07-241-9/+9
|
* Add the change of the sound drivers.tanimura2004-07-161-0/+5
|
* Fix typo in 20040702 entry.simon2004-07-111-1/+1
| | | | Noticed by: Andre Guibert de Bruet <andy@siliconlandmark.com>
* Add 3 new entries:marcel2004-07-111-0/+30
| | | | | | | | o __FreeBSD_version bumped to 502122 o Alpha console initialization requires the same sio(4) hints as on other platforms. Options NO_SIO and DEV_SC removed. o KDB framework: Added KDB and GDB; Renamed WITNESS_DDB, DDB_TRACE DDB_UNATTENDED. Removed GDB_REMOTE_CHAT and DDB_NOKLDSYM.
* Bump __FreeBSD_versionemax2004-07-091-0/+4
| | | | Reviewed by: kris, ru
* Add note about ULE breakage at the moment.imp2004-07-051-0/+10
| | | | Submitted by: Xin LI
* Wordsmith and spell-correct last commitbms2004-06-301-6/+6
|
* Remove the home-grown metadata facility in favour of the now genericjulian2004-06-301-0/+9
| | | | | | mbuf tags facility. Netgraph modules will all need a recompile. Submitted by: Gleb Smirnoff <glebius@cell.sick.ru>
* Note the ACPI blacklist changes.njl2004-06-301-0/+8
| | | | Prodded by: imp
* Make some bugfixes and improve some text in the description of how togreen2004-06-261-5/+11
| | | | | | update from 4.x to 5.x. Submitted by: Frerich Raabe <raabe@kde.org>
* Add "privsep" user/group _pflogd:_pflogd (64:64) to make pflogd(8) workmlaier2004-06-231-0/+6
| | | | | | | | again. This user/group is not required for install* targets, hence do not add them to CHECK_UIDS/CHECK_GIDS in Makefile.inc1 (no need to annoy people). Discussed-on: -current
OpenPOWER on IntegriCloud