summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* For users of FreeBSD <= 6.2 we recommend during the x.org 7.x upgradekris2008-03-052-1/+19
| | | | | | | | | | | | | | | | | | | | | that they add X11BASE=${LOCALBASE} to /etc/make.conf since X11BASE was hard-wired to the now-wrong location in old releases. However, both X11BASE and LOCALBASE have moved out of scope of src/ into ports/ now, which causes problems for upgraded users who have old make.conf files still containing the above setting. X11BASE becomes null and we instruct ssh and sshd to look for xauth in /bin/xauth where it is unlikely to be found. Instead, provide a copy of the default LOCALBASE?=/usr/local setting here. We also have to deal with the case where the user only overrides LOCALBASE and doesn't set an explicit X11BASE (in ports it will be set implicitly but not here), which will also move the location of xauth. MFC after: 3 days Reported by: rwatson
* The non-POSIX environment variable MAKE was supersededyar2008-03-051-1/+1
| | | | | | by MAKEFLAGS ages ago, so don't mention it in comments. Tested with: cmp(1)
* Don't forget to set MAKEFLAGS in the childs' environmentyar2008-03-052-31/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | from the .MAKEFLAGS global variable even if it's empty or unset. This means setting MAKEFLAGS to just an empty string in the latter case. If not doing so, make(1) behaved inconsistently WRT MAKEFLAGS. In particular, it would let a `-f foo' option down to sub-makes if .MAKEFLAGS was unset. E.g., env MAKEFLAGS="-f mymakefile" make would pass `-f mymakefile' down to sub-makes via their environment (unless mymakefile added something to .MAKEFLAGS). But any additional options appearing would change this behaviour to not passing `-f mymakefile' to sub-makes, as in: env MAKEFLAGS="-f mymakefile" make -D DUMMY or env MAKEFLAGS="-f mymakefile -D DUMMY" make (unless mymakefile cleared .MAKEFLAGS). Also make(1) would leave MAKEFLAGS at its initial value if the makefile set .MAKEFLAGS to an empty value. I.e., it was impossible to override MAKEFLAGS with an empty value. (Note well that makefiles are not to touch MAKEFLAGS directly, they alter .MAKEFLAGS instead. So make(1) can filter out things such as -f when copying MAKEFLAGS to .MAKEFLAGS at startup. Direct modifications to MAKEFLAGS just go nowhere.) While the original intentions of the BSD make authors are somewhat unclear here, the bug proves that NOT passing -f options down is the settled behaviour because the opposite behaviour is totally unreliable in the presence of any other options. In addition, not passing down -f's found in the environment is consistent with doing so WRT the command line. Update the manpage accordingly and make the whole description of MAKEFLAGS and .MAKEFLAGS more consistent as this change indeed brings more consistency into the reliable behaviour of make(1). Submitted by: ru (main.c) Tested with: make world
* o We don't have to keep track of the PIC, nor do we have to make suremarcel2008-03-051-28/+39
| | | | | | | it's probed first. The PowerPC platform code deals with everything. As such, probe devices in order of their location in the memory map. o Refactor the ocpbus_alloc_resource for readability and make sure we set the RID in the resource as per the new convention.
* Use the new command file feature of ddb(8) to support setting ddb(4)brooks2008-03-056-2/+64
| | | | | | | | | scripts at boot. This is currently disabled by default. /etc/ddb.conf contains some potentially reasonable default scripts. PR: conf/119995 Submitted by: Scot Hetzel <swhetzel at gmail dot com> (Earlier version) X-MFC after: textdumps
* mdoc changes to make this manpage consistent with our other section 4 manpages.brueffer2008-03-051-8/+19
|
* Add the ability to read a file of commands to ddb(8) modeled after thebrooks2008-03-052-5/+81
| | | | feature in ipfw(8).
* o Various fixes related to PCI Express:marcel2008-03-051-37/+65
| | | | | | | | | | | | | | | | | | | | | | | | | - Even for the PCI Express host controller we need to use bus 0 for configuration space accesses to devices directly on the host controller's bus. - Pass the maximum number of slots to pci_ocp_init() because the caller knows how many slots the bus has. Previously a PCI or PCI-X bus underneath a PCI Express host controller would not be enumerated properly. o Pull the interrupt routing logic out of pci_ocp_init() and into its own function. The logic is not quite right and is expected to be a bit more complex. o Fix/add support for PCI domains. The PCI domain is the unit number as per other PCI host controller drivers. As such, we can use logical bus numbers again and don't have to guarantee globally unique bus numbers. Remove pci_ocp_busnr. Return the highest bus number ito the caller of pci_ocp_init() now that we don't have a global variable anymore. o BAR programming fixes: - Non-type0 headers have at most 1 BAR, not 0. - First write ~0 to the BAR in question and then read back its size. Obtained from: Juniper Networks (mostly)
* Initialize mnt_stat.f_iosize before autostarting UFS1 extattrs.kib2008-03-051-0/+1
| | | | | | | | | | | | | | It is normally initialized by ffs_statfs() after ffs_mount finished. The extattr autostart code calls the ufs_lookup(), that uses value above to iterate over the directory blocks, see bmask initialization in the ufs_lookup() and ufsdirhash. Having the filesystem with root directory spanning more then one block would result in reading a random kernel memory. PR: kern/120781 Test case provided by: rwatson MFC after: 1 week
* Oops, I accidently concatenated uslcom.[c4] multiple times before therink2008-03-052-2012/+0
| | | | | | commit :-/ Quickly fix before things get broken... Pointyhat to: me
* Import uslcom(4) from OpenBSD - this is a driver for Silicon Laboratoriesrink2008-03-0510-0/+2560
| | | | | | | | CP2101/CP2102 based USB serial adapters. Reviewed by: imp, emaste Obtained from: OpenBSD MFC after: 2 weeks
* Add info about few missing GEOM classes that use geom(8).pjd2008-03-051-1/+13
|
* Change float_t and double_t to long double on i386. All floating pointbde2008-03-051-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | expressions on i386 are evaluated in the range of the long double type, so this is wrong in a different but hopefully less worse way than before. Since expressions are evaluated in long double registers, there is no runtime cost to using long double instead of double to declare intermediate values (except in cases where this avoids compiler bugs), and by careful use of float_t or double_t it is possible to avoid some of the compiler bugs in this area, provided these types are declared as long double. I was going to change float.h to be less broken and more usable in combination with the change here (in particular, it is more necessary to know the effective number of bits in a double_t when double_t != double, since DBL_MANT_DIG no longer logically gives this, and LDBL_MANT_DIG doesn't give it either with FreeBSD-i386's default rounding precision. However, this was too hard for now. In particular, LDBL_MANT_DIG is used a lot in libm, so it cannot be changed. One thing that is completely broken now is LDBL_MAX. This may have sort of worked when it was changed from DBL_MAX in 2002 (adding 0 to it at runtime gave +Inf, but you could at least compare with it), but starting with gcc-3.3.1 in 2003, it is always +Inf due to evaluating it at compile time in the default rounding precision.
* Oops, back out previous commit since it was to the wrong file.bde2008-03-051-5/+4
|
* Change float_t and double_t to long double on i386. All floating pointbde2008-03-051-4/+5
| | | | | | | | | | | | | | | | | | | | | | | | expressions on i386 are evaluated in the range of the long double type, so this is wrong in a different but hopefully less worse way than before. Since expressions are evaluated in long double registers, there is no runtime cost to using long double instead of double to declare intermediate values (except in cases where this avoids compiler bugs), and by careful use of float_t or double_t it is possible to avoid some of the compiler bugs in this area, provided these types are declared as long double. I was going to change float.h to be less broken and more usable in combination with the change here (in particular, it is more necessary to know the effective number of bits in a double_t when double_t != double, since DBL_MANT_DIG no longer logically gives this, and LDBL_MANT_DIG doesn't give it either with FreeBSD-i386's default rounding precision. However, this was too hard for now. In particular, LDBL_MANT_DIG is used a lot in libm, so it cannot be changed. One thing that is completely broken now is LDBL_MAX. This may have sort of worked when it was changed from DBL_MAX in 2002 (adding 0 to it at runtime gave +Inf, but you could at least compare with it), but starting with gcc-3.3.1 in 2003, it is always +Inf due to evaluating it at compile time in the default rounding precision.
* Expand the nfs_opts array to include all possible stringrodrigc2008-03-051-1/+4
| | | | | | | | | | | mount options that mount_nfs could pass down, if it passed down string mount options. Right now, mount_nfs jut passes down a single mount option named "nfs_args" with a fully initialized 'struct nfs_args'. In future commits, we will add code to the kernel for parsing stringified NFS mount options, so that we can convert mount_nfs to pass string options from userspace to kernel, instead of an initialized struct nfs_args.
* In nfs_mount(), default initialize struct nfs_argsrodrigc2008-03-051-1/+25
| | | | | | | | | | | | | | the same way that it is default initialized in revision 1.77 of mount_nfs.c. Right now, this is a no-op, because currently we initialize struct nfs_args in mount_nfs in userspace, and pass it down into the kernel via nmount(), so we overwrite whatever we initialize here with the value passed in from userspace. However, this lays the groundwork for moving away from passing struct nfs_args from userspace to kernel via nmount(), so that we can instead pass string mount options via nmount() which can be parsed in the kernel. This will make it easier to add new NFS mount options.
* For a mounted file system which is read-only, whenrodrigc2008-03-051-1/+3
| | | | | | | | | | | | | | | | | | | | | | doing the MNT_RELOAD, pass in "ro" and "update" string mount options to nmount() instead of MNT_RDONLY and MNT_UPDATE flags. Due to the complexity of the mount parsing code especially with respect to the root file system, passing in MNT_RDONLY and MNT_UPDATE flags would do weird things and would cause fsck to convert the root file system from a read-only mount to read-write. To test: - boot into single user mode - show mounted file systems with: mount - root file system should be mounted read-only - fsck / - show mounted file systems with: mount - root file system should still be mounted read-only PR: 120319 MFC after: 1 month Reported by: yar
* - Don't overwrite the recently allocated 'nset' in cpuset_setthread() byjeff2008-03-051-1/+1
| | | | | | | | passing it to cpuset_which(). Pass in 'set' instead. This argument is not used but for convenience cpuset_which() nulls all incoming parameters. Submitted by: davidxu
* Add rl(4) supportkevlo2008-03-051-0/+2
|
* Remove hacks which filter out MNT_ROOTFS.rodrigc2008-03-051-15/+1
| | | | | | | They are no longer needed now that we filter out MNT_ROOTFS inside the nmount() call in revision 1.267 of vfs_mount.c. Reviewed by: rink
* Increase and decrease in_sigcancel_handler accordingly to avoid possibledavidxu2008-03-051-2/+2
| | | | error caused by nested SIGCANCEL stack, it is a bit complex.
* Use cpuset defined in pthread_attr for newly created thread, for now,davidxu2008-03-053-21/+57
| | | | | | | we set scheduling parameters and cpu binding fully in userland, and because default scheduling policy is SCHED_RR (time-sharing), we set default sched_inherit to PTHREAD_SCHED_INHERIT, this saves a system call.
* Add more cpu affinity function's symbols.davidxu2008-03-051-0/+6
|
* Check actual size of cpuset kernel is using and define underscore versiondavidxu2008-03-051-7/+42
| | | | of API.
* Remove hacks to filter out MNT_ROOTFS, since we nowrodrigc2008-03-051-10/+0
| | | | do that internally inside nmount() in revision 1.267 of vfs_mount.c.
* Plug memory leak in jumbo buffer allocation failure path.yongari2008-03-051-4/+12
| | | | | | | | | | | | Patch in the PR was modified to check active jumbo buffers in use and other possible jumbo buffer leak. Jumbo buffer usage in lge(4) still wouldn't be reliable due to lack of driver lock in local jumbo buffer allocator. Either introduce a new lock to protect jumbo buffer or switch to UMA backed page allocator for jumbo frame is required. PR: kern/78072
* - Remove the -i argument when running a command to simplify things ajeff2008-03-053-14/+177
| | | | | | | | little bit and to prevent users from specifying a private mask that may later restrict other group changes. - Add a man page which brueffer generously contributed to. Sponsored by: Nokia
* - Verify that when a user supplies a mask that is bigger than the kerneljeff2008-03-053-34/+107
| | | | | | | | | | mask none of the upper bits are set. - Be more careful about enforcing the boundaries of masks and child sets. - Introduce a few more CPU_* macros for implementing these tests. - Change the cpusetsize argument to be bytes rather than bits to match other apis. Sponsored by: Nokia
* - add '-f' option to force root node.simokawa2008-03-052-8/+23
| | | | | | | | - fix byte order in read_write_quad() - show hostnames in the list - fix typo in manpage MFC after: 1 week
* Add detection of isolation state.yongari2008-03-051-0/+5
| | | | PR: kern/76710
* It seems some don't care for the anchient joke. Add WITHOUT_OLD_JOKEobrien2008-03-041-0/+2
| | | | to your CFLAGS if you fall into this camp.
* No need to tell make to DTRT with "make love", just do it.obrien2008-03-042-11/+0
| | | | | Also remove the 2002/08/31 bootstrapping aid for upgrades from year old (mid-2001) systems.
* Temporarily back out revision 1.98 to give Portmgr some time toobrien2008-03-041-2/+2
| | | | | | | address PR ports/121363 (current day re-opening of PR ports/73797) to make ports CFLAGS more independent of src/'s CFLAGS WRT aliasing. Discussed with: brooks
* Change the default port range for outgoing connections by introducingrpaulo2008-03-042-44/+29
| | | | | | | | | | | | | | | | IPPORT_EPHEMERALFIRST and IPPORT_EPHEMERALLAST with values 10000 and 65535 respectively. The rationale behind is that it makes the attacker's life more difficult if he/she wants to guess the ephemeral port range and also lowers the probability of a port colision (described in draft-ietf-tsvwg-port-randomization-01.txt). While there, remove code duplication in in_pcbbind_setup(). Submitted by: Fernando Gont <fernando at gont.com.ar> Approved by: njl (mentor) Reviewed by: silby, bms Discussed on: freebsd-net
* Back out revision 1.97, which backed out part of revision 1.96.obrien2008-03-041-2/+2
| | | | | | | Change the default CFLAGS to match the simple defaults that the tinderboxes use. By using -fno-strict-aliasing by default we are choosing to ignore problems in code which had the potential to shoot ourselves in the foot.
* Add support for automatic promotion of 4KB page mappings to 2MB pagealc2008-03-042-105/+1081
| | | | | | | | | mappings. Automatic promotion can be enabled by setting the tunable "vm.pmap.pg_ps_enabled" to a non-zero value. By default, automatic promotion is disabled. (Expect this to change.) Reviewed by: ups Tested by: kris, Peter Holm
* Implement 128 items node name hash for faster name search.mav2008-03-041-47/+70
| | | | Increase node ID hash size from 32 to 128 items.
* Force an explicit dependency on opt_global.h for all module object filesjhb2008-03-041-0/+7
| | | | | | | | | when building modules as part of a kernel build just as we do for kernel object files. MFC after: 1 week Reported by: kmacy, kris Reviewed by: ru
* <limits.h> is necessary for using INT_MIN, so included it hereimp2008-03-041-0/+1
| | | | | | | | explicitly rather than relying on name space pollution to pull it in for us. NB: The usage of INT_MIN is somewhat bogus and suspect to my eye, but this commit doesn't address that issue.
* Continue on-going campaign to replace lockmgr locks with sx locks whererwatson2008-03-042-12/+14
| | | | | | | | | the specific semantics of ockmgr aren't required: update UFS1 extended attributes to protect its data structures using an sx lock. While here, update comments on lock granularity. MFC after: 2 weeks
* Move setting of MNTK_MPSAFE flag before UFS1 extended attributerwatson2008-03-041-3/+3
| | | | | | | | auto-start so that the flag is set before we start performing I/O in the auto-start routine. MFC after: 2 weeks Suggested by: kib
* Move a stray paragraph on .Ev MAKEFLAGS to where it belongs.yar2008-03-041-14/+14
|
* Revise the description of how .Ev MAKEFILE and .Va .MAKEFILE relate.yar2008-03-041-21/+27
| | | | | | | | | The most important point is that -f option(s) are never copied from .Ev MAKEFILE to .Va .MAKEFILE by make(1), which is consistent with handling the command line. (-f silently sit in .Ev MAKEFILE and go to make's children unless overwritten via .Va .MAKEFILE) Bump .Dd.
* Fix incorrect field name.mav2008-03-041-1/+1
|
* Fix the Giant leak in the nfsrv_remove().kib2008-03-041-2/+6
| | | | | Reported by: pluknet <pluknet gmail com> MFC after: 1 week
* Split descriptions of .Ev MAKEFILE and .Va .MAKEFLAGS for clarity.yar2008-03-041-2/+2
|
* Make it possible to continue working after calling doadump()ru2008-03-041-0/+1
| | | | manually from debugger. (This got broken in rev. 1.122.)
* Note 7.0 was the first version that FreeBSD/pc98 had a MACHINE of pc98imp2008-03-041-8/+7
| | | | instead of i386.
* Linux requires -D__dead2= and -D__unused= to get rid of theimp2008-03-041-1/+1
| | | | | sys/cdef.h-isms in the make source. The variant of linux I tried it on doesn't have arc4random, so -Darc4random=random too.
OpenPOWER on IntegriCloud