summaryrefslogtreecommitdiffstats
path: root/include
Commit message (Collapse)AuthorAgeFilesLines
* Add skeleton build dirs for pf userland:mlaier2004-02-281-0/+8
| | | | | | | | | | | | | | | | | | libexec/ftp-proxy - ftp proxy for pf sbin/pfctl - equivalent to sbin/ipf sbin/pflogd - deamon logging packets via if_pflog in pcap format usr.sbin/authpf - authentification shell to modify pf rulesets Bring along some altq headers used to satisfy pfctl/authpf compile. This helps to keep the diff down and will make it easy to have a altq-patchset use the full powers of pf. Also make sure that the pf headers are installed. This does not link anything to the build. There will be a NO_PF switch for make.conf once pf userland is linked. Approved by: bms(mentor)
* Sync HEAD sources to vendor branch import of routed v2.27 from rhyolite.com.bms2004-02-251-1/+4
| | | | | | | | Update <protocols/routed.h> for the MD5 changes requested in bin/35843. Preserve local changes. Education by: obrien, markm, pointy-stick PR: bin/35843 (and doubtless others)
* Make the resolver(3) and many associated interfaces much more reentrant.green2004-02-252-3/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The getaddrinfo(3), getipnodebyname(3) and resolver(3) can coincide now with what should be totally reentrant, and h_errno values will now be preserved correctly, but this does not affect interfaces such as gethostbyname(3) which are still mostly non-reentrant. In all of these relevant functions, the thread-safety has been pushed down as far as it seems possible right now. This means that operations that are selected via nsdispatch(3) (i.e. files, yp, dns) are protected still under global locks that getaddrinfo(3) defines, but where possible the locking is greatly reduced. The most noticeable improvement is that multiple DNS lookups can now be run at the same time, and this shows major improvement in performance of DNS-lookup threaded programs, and solves the "Mozilla tab serialization" problem. No single-threaded applications need to be recompiled. Multi-threaded applications that reference "_res" to change resolver(3) options will need to be recompiled, and ones which reference "h_errno" will also if they desire the correct h_errno values. If the applications already understood that _res and h_errno were not thread-safe and had their own locking, they will see no performance improvement but will not actually break in any way. Please note that when NSS modules are used, or when nsdispatch(3) defaults to adding any lookups of its own to the individual libc _nsdispatch() calls, those MUST be reentrant as well.
* Add getopt_long_only()ache2004-02-241-1/+3
|
* In the comment tell about optreset extension for NetBSD ghetopt_long()ache2004-02-231-1/+2
|
* Add optreset to getopt.h too since NetBSD getopt_long() (but not GNU one)ache2004-02-232-1/+8
| | | | use it too.
* Try to better mimic GNU getopt.h which does not assume to make visibleache2004-02-232-6/+13
| | | | all unistd.h functions, use _GETOPT_DECLARE define for that.
* Fix comment: GNU getopt.h to which this header tries to mimic does not declareache2004-02-231-1/+1
| | | | getsubopt/optreset
* POSIX clearly states that getsubopt() should be declared in <stdlib.h>,ache2004-02-232-8/+2
| | | | not in <unistd.h>
* Add NO_BLUETOOTH knob to the build processemax2004-01-281-0/+2
| | | | | Requested by: phk Reviewed by: imp (mentor), ru
* remove EAI_NODATA aliased to EAI_NONAME.ume2004-01-151-1/+0
| | | | PR: bin/61369
* Add and document ffsl(), fls() and flsl().des2004-01-131-0/+3
|
* It was reported that when using nss_ldap, getgrent(3) would behavenectar2004-01-091-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | incorrectly when encountering `large' groups (many members and/or many long member names). The reporter tracked this down to the glibc NSS module compatibility code (nss_compat.c): it would prematurely record that a NSS module was finished iterating through its database in some cases. Two aspects are corrected: 1. nss_compat.c recorded that a NSS module was finished iterating whenever the module reported something other than SUCCESS. The correct logic is to continue iteration when the module reports either SUCCESS or RETURN. The __nss_compat_getgrent_r and __nss_compat_getpwent_r routines are updated to reflect this. 2. An internal helper macro __nss_compat_result is used to map glibc NSS status codes to BSD NSS status codes (e.g. NSS_STATUS_SUCCESS -> NS_SUCCESS). It provided the obvious mapping. When a NSS routine is called with a too-small buffer, the convention in the BSD NSS code is to report RETURN. (This is used to implement reentrant APIs such as getpwnam_r(3).) However, the convention in glibc for this case is to set errno = ERANGE and overload TRYAGAIN. __nss_compat_result is updated to handle this case. PR: bin/60287 Reported by: Lachlan O'Dea <odela01@ca.com>
* Define _PATH_MKSNAP_FFS and use it in dump(8) instead of assumingiedowse2004-01-041-0/+1
| | | | | | that mksnap_ffs(8) can be found using the current $PATH. Reviewed by: mckusick
* Now I understand what Bruce was getting at - -1 can be parsed as twojkh2003-12-182-2/+2
| | | | | tokens, so it does indeed need to be parenthesized. Duh. Sometimes it can stare you right and the face and you still don't see it. Thanks, bde.
* Adjust in response to various bits of brucification:jkh2003-12-182-2/+4
| | | | | | | | | | | | | | 1) Fix style issues in comments. 2) Properly namespaceify changes 3) Appropriate sectioning of changes Not changed: parenthesis around macro rvalue. That would make the additions inconsistent with the other entries there, merely a different style violation rather than a clear and obvious improvement so I'm going to have to disagree with the judges on that one. If someone wishes to adjust *all* the rvalues to conform to fully parenthesized marco rule, that would be both consistent and reasonable but that's beyond the scope of the changes I wish to make at this time.
* OK, someone was tab happy in this file. A tab after #define?! OK, fine,jkh2003-12-171-1/+1
| | | | | I'll keep the same style regardless of the wisdom of it. :) Clarified by: eivind
* Correct inexplicable tab smash.jkh2003-12-171-1/+1
| | | | Noticed by: Nate Lawson <nate@root.org>
* Conformance: Add REG_ENOSYS (see ↵jkh2003-12-171-0/+1
| | | | http://www.opengroup.org/onlinepubs/007904975/basedefs/regex.h.html)
* Conformance: Define FNM_NOSYS (see ↵jkh2003-12-171-0/+2
| | | | http://www.opengroup.org/onlinepubs/007904975/basedefs/fnmatch.h.html)
* Move the bktr(4) <arch>/include/ioctl_{bt848,meteor}.h files to dev/bktrobrien2003-12-081-3/+6
| | | | | | as these ioctl's aren't MD. This also means they are installed in /usr/include/dev/bktr now. Also provide compatability wrappers for where these headers lived in 4.x.
* Fix sort order.obrien2003-12-081-1/+1
|
* Change the definition of NULL on ia64 (for LP64 compilations) frommarcel2003-12-0710-39/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | an int constant to a long constant. This change improves consistency in the following two ways: 1. The first 8 arguments are always passed in registers on ia64, which by virtue of the generated code implicitly widens ints to longs and allows the use of an 32-bit integral type for 64-bit arguments. Subsequent arguments are passed onto the memory stack, which does not exhibit the same behaviour and consequently do not allow this. In practice this means that variadic functions taking pointers and given NULL (without cast) work as long as the NULL is passed in one of the first 8 arguments. A SIGSEGV is more likely the result if such would be done for stack-based arguments. This is due to the fact that the upper 4 bytes remain undefined. 2. All 64-bit platforms that FreeBSD supports, with the obvious exception of ia64, allow 32-bit integral types (specifically NULL) when 64-bit pointers are expected in variadic functions by way of how the compiler generates code. As such, code that works correctly (whether rightfully so or not) on any platform other than ia64, may fail on ia64. To more easily allow tweaking of the definition of NULL, this commit removes the 12 definitions in the various headers and puts it in a new header that can be included whenever NULL is to be made visible. This commit fixes GNOME, emacs, xemacs and a whole bunch of ports that I don't particularly care about at this time...
* Add support for timeout: and attempts: resolver options.murray2003-12-071-0/+2
| | | | | Submitted by: Paul Vixie <paul@vix.com> / ISC MFC After: 1 week
* Install UDF header files to unbreak /sbin building when /sys is not present.scottl2003-11-221-1/+1
| | | | Submitted by: imura@ryu16.org
* Add the userland part of the NET_RT_IFMALIST sysctl MIB. A new function,bms2003-11-141-0/+9
| | | | | | getifmaddrs(), is added to retrieve current multicast group memberships. Reviewed by: harti
* Add the pthread_atfork() prototype.deischen2003-11-041-0/+2
| | | | Reviewed by: davidxu
* Add a new flag to vis(3): VIS_GLOB which encodes the glob(3) magicphk2003-10-301-0/+1
| | | | characters '*', '?' and '['.
* *blush*. stdhash.h != strhash.hpeter2003-10-291-1/+1
| | | | Sorry folks.
* Don peril sensitive (ie: bikeshed sensitive) sunglasses and quietlypeter2003-10-281-64/+0
| | | | | | | | | | | send strhash(3) off to sleep with the fishes. Nothing in our tree uses it. It has no documentation. It is nonstandard and in spite of the filename strhash.c and strhash.h, it lives in application namespace by providing compulsory global symbols hash_create()/hash_destroy()/hash_search()/ hash_traverse()/hash_purge()/hash_stats() regardless of whether you #include <strhash.h> or not. If it turns out that there is a huge application for this after all, I can repocopy it somewhere safer and we can revive it elsewhere. But please, not in libc!
* Argh. Forward declare some structs rather than increase include filepeter2003-10-261-0/+2
| | | | dependencies.
* Prototype yp_maplist()peter2003-10-261-0/+1
|
* style.ume2003-10-241-1/+1
| | | | Reported by: bde
* oops, EAI_NONAME is not EAINONAME.ume2003-10-241-1/+1
|
* workaround to have backward compatibility for EAI_NODATA.ume2003-10-231-0/+1
| | | | | | it will be removed on 23 Apr 2004. Submitted by: terry
* oops, I forget to diable EAI_ADDRFAMILY and EAI_NODATA.ume2003-10-231-0/+6
|
* stop use of NI_WITHSCOPEID. it was deprecated.ume2003-10-211-0/+2
| | | | Obtained from: KAME
* Add code to support pthread spin lock.davidxu2003-09-091-0/+7
| | | | Reviewed by: deischen
* Add small piece of code to support pthread_rwlock_timedrdlock anddavidxu2003-09-061-0/+4
| | | | pthread_rwlock_timedrwlock.
* Add code to support barrier synchronous object and implementdavidxu2003-09-041-0/+16
| | | | | | pthread_mutex_timedlock(). Reviewed by: deischen
* Add a new machine independent varargs.h and use it as a central placekan2003-09-012-3/+46
| | | | | | | to announce the demise of varargs support in GCC versions 3.3+ and to direct users to stdarg.h instead. Fall back to machine/varargs.h for older GCC versions.
* Update gethostname() prototype to match source and standard.wollman2003-08-191-1/+1
|
* Make C++ safeimp2003-07-141-0/+4
|
* Don't be so chatty about osreldate.h creation steps when make(1)ru2003-07-041-1/+1
| | | | is run in non-compat mode (-j without -B).
* Fixed namespace pollution and unsorting of the 1003.1-1990 list inbde2003-07-011-1/+1
| | | | previous commit.
* Add /rescue bits. This basically encompasses all of bin and sbin alonggordon2003-06-291-0/+35
| | | | | | with a couple of bits from usr.bin in a crunchgen'd binary. Submitted by: Tim Kientzle <kientzle@acm.org>
* Move path definitions to include/paths.h. This makes it easier to overridegordon2003-06-291-0/+3
| | | | | | these definitions in the /rescue case. Submitted by: Tim Kientzle <kientzle@acm.org>
* Convert fsck and mount to using execvP to find fsck_foo and mount_foo.gordon2003-06-291-0/+3
| | | | | | | This simplifies the code path and makes the default path easy to override in the /rescue case. Submitted by: Tim Kientzle <kientzle@acm.org>
* Add a libc function execvP that takes the search path as an arguement.gordon2003-06-291-0/+1
| | | | | | | | Change execvp to be a wrapper around execvP. This is necessary for some of the /rescue pieces. It may also be more generally applicable as well. Submitted by: Tim Kientzle <kientzle@acm.org> Approved by: Silence on arch@
* enable installation of sys/net80211sam2003-06-281-2/+2
|
OpenPOWER on IntegriCloud