summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* The last argument of execl(3) should be cast explicitly.tb2019-12-281-2/+2
| | | | ok kn
* regenkn2019-12-282-0/+5
|
* Attach Symbios Logic Flash Accelerator eMLC cardskn2019-12-282-2/+4
| | | | | | | | | | Those can be found in SPARC T4 machines, mine has the F80 800G model. Since other devices with different flash configurations use the same vendor/product ID, use the LSI chip name as product name as pointed out by jmatthew, thanks. OK jmatthew deraadt
* Convert the speclisth hash buckets into SLIST macros. This makesbluhm2019-12-274-32/+22
| | | | | the vnode alias code more readable. OK visa@
* Build dig with support for the Cookies EDNS option (aka SIT / Source identitysthen2019-12-271-2/+3
| | | | tokens), ok deraadt@
* Support regex search in copy mode, from Anindya Mukherjee in GitHubnicm2019-12-271-38/+359
| | | | issue 2038.
* make -n stop after parsing the config.benno2019-12-271-3/+7
| | | | | make -nv print the parsed configuration, then stop. ok sthen@, seems better deraadt@
* Fix ifconfig WPA key installation with max allowed length SSIDs.stsp2019-12-271-15/+17
| | | | ok claudio phessler deraadt sthen
* tidy up the page;jmc2019-12-271-95/+81
|
* Relink ospf6d regress testdenis2019-12-271-1/+2
|
* Don't start background scans before WPA handshake has completed.stsp2019-12-271-1/+4
| | | | ok phessler
* Remove the kernel lock in pipe read and write routines since everythinganton2019-12-271-12/+7
| | | | | | | | is serialized by the pipe_lock by now. The kernel lock is however still needed when interacting with kqueue in order to prevent a race and when potentially issuing SIGIO signals. ok visa@
* Since we are now parsing rDNS proposals we can check for them.florian2019-12-271-0/+8
|
* slaacctl output changed with the addition of rDNS proposals.florian2019-12-271-6/+55
| | | | Failing regress tests noticed by bluhm.
* sort -Y internally in the options list, as is already done in synopsis;jmc2019-12-271-17/+17
|
* in the options list, sort -Y and -y;jmc2019-12-271-5/+5
|
* use a standard synopsis/usage() layout, and tidy up the man page a little;jmc2019-12-272-97/+62
| | | | | some macro simplifications from schwarze ok schwarze deraadt kn
* tsleep -> tsleep_nsec(9) in setroot()kn2019-12-261-2/+2
| | | | OK cheloha bluhm
* Do not fail an assertion when a high level macro occurs in the bodyschwarze2019-12-261-2/+14
| | | | | | | of a conditional inside a .ce request block. Instead, abort the .ce block just like when there is no conditional in between. Bug found by espie@ working on the textproc/fstrcmp port.
* Fix white spaces.bluhm2019-12-261-13/+15
|
* Use absolute path for config files.denis2019-12-261-6/+8
|
* Unlink ospf6d testsdenis2019-12-261-2/+1
| | | | It fails on bluhm@ test infrastructure
* Skip regress ftpd if there is no anonymous ftp user with existingbluhm2019-12-261-2/+10
| | | | home directory.
* Pass correct value into iterator callback for time formats.nicm2019-12-261-5/+4
|
* implement unregister_shrinker()jsg2019-12-264-5/+9
| | | | ok kettenis@
* Move extern declarations of vfsops variables into header file.bluhm2019-12-262-43/+13
| | | | OK visa@
* Convert struct vfsops initializer to C99 style.bluhm2019-12-2610-141/+141
| | | | OK visa@
* In ACPI mode, do not generate "cpu" nodes for CPUs that are disabled.kettenis2019-12-261-3/+5
| | | | | Fixes booting on ACPI machines where the MADT table lists CPUs that are disabled such as the od1000 with new EDK2 firmware.
* enable shrinker for ttmjsg2019-12-261-7/+0
| | | | ok kettenis@
* Add a number of new formats to inspect what sessions and clients anicm2019-12-264-6/+243
| | | | window is present or active in. From Tyler Culp in GitHub issue 2034.
* Add point-to-point support for broadcast interfaces.remi2019-12-264-6/+18
| | | | | tested by Kapetanakis Giannis ok denis@
* It is believed that an implementation of madvise was available injsg2019-12-261-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SunOS 4.0 based on text from the following papers. "Two 4.2BSD system calls, madvise and mincore, remain unspecified, madvise is intended to provide information to the system to influence its management policies. Since a major rework of such policies was deferred to a future release, we decided to defer full specification and implementation of madvise until that time." R. Gingell, J. Moran, W. Shannon "Virtual Memory Architecture in SunOS" Proceedings of USENIX Summer Conference, June 1987 AUUGN Volume 8 Number 5, October 1987 "Memory management related system calls based on the original 4.2BSD specification that were implemented include mmap, munmap, mprotect, madvise, and mincore." J. Moran "SunOS Virtual Memory Implementation" Proceedings of the Spring 1988 European UNIX Users Group Conference, April 1988 AUUGN Volume 9 Number 3, June 1988 and a reference in "Global Index", Part Number: 800-1758-10, Revision A, of 9 May 1988 bitsavers pdf/sun/sunos/4.0/800-1758-10A_Global_Index_198805.pdf discussed with an ok schwarze@
* exit_type is already set up with exactly the information we need,espie2019-12-251-11/+10
| | | | | | so get rid of cluttered duplicate logic okay kn@
* disable a few more things which might look in /usr/local.deraadt2019-12-251-1/+5
| | | | | (I decided to take a look at ktrace -di output of the whole compilation procedure)
* Replace macros knote_alloc() and knote_free() with direct use ofvisa2019-12-251-11/+4
| | | | | | | pool_get() and pool_put(). This makes it clearer that the knote allocation cannot fail and that the error check is unnecessary. OK anton@, kettenis@, mpi@
* Use FOREACH macro to iterate over mnt_vnodelist.bluhm2019-12-251-3/+2
| | | | OK millert@ visa@ benno@
* WSDISPLAYIO_GTYPE is u_int not intjsg2019-12-255-7/+7
|
* Hook up the shrinker for inteldrm(4). This is a "light" version that onlykettenis2019-12-258-13/+91
| | | | | | | drops graphics buffers that are cached and not in active use. Help from beck@ for pointing out how to hook this up to our pagedaemon. ok jsg@
* Condense a few multi line comments into single line ones. While hereanton2019-12-251-40/+13
| | | | turn them into proper sentences. Gets rid of 27 lines in total.
* Protect remaining fields of `struct pipe' using the pipe_lock. In orderanton2019-12-252-41/+61
| | | | | | | | | | | to simplify the locking pattern, revert back to using a hand-rolled I/O lock just like FreeBSD and NetBSD does. The state of pipes is quite different compared to when I made use of a rwlock for the I/O lock in revision 1.96. Most notably, the pipe_lock can now be used while sleeping. This does imply that witness(4) tracking of the I/O lock is lost but the implementation ends up being simpler. ok visa@
* TIMEOUT_INITIALIZER(9): C99 initializerscheloha2019-12-251-3/+8
|
* timeout(9): new flag: TIMEOUT_SCHEDULED, new statistic: tos_scheduledcheloha2019-12-253-19/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This flag is set whenever a timeout is put on the wheel and cleared upon (a) running, (b) deletion, and (c) readdition. It serves two purposes: 1. Facilitate distinguishing scheduled and rescheduled timeouts. When a timeout is put on the wheel it is "scheduled" for a later softclock(). If this happens two or more times it is also said to be "rescheduled". The tos_rescheduled value thus indicates how many distant timeouts have been cascaded into a lower wheel level. 2. Eliminate false late timeouts. A timeout is not late if it is due before softclock() has had a chance to schedule it. To track this we need additional state, hence a new flag. rprocter@ raises some interesting questions. Some answers: - This interface is not stable and name changes are possible at a later date. - Although rescheduling timeouts is a side effect of the underlying implementation, I don't forsee us using anything but a timeout wheel in the future. Other data structures are too slow in practice, so I doubt that the concept of a rescheduled timeout will be irrelevant any time soon. - I think the development utility of gathering these sorts of statistics is high. Watching the distribution of timeouts under a given workflow is informative. ok visa@
* delete a few sentences which only restate what is already obvious;schwarze2019-12-241-18/+2
| | | | OK jmc@ deraadt@ kn@
* Remove non-sensical line. The node certainly hasn't been rebuilt yet,espie2019-12-241-3/+1
| | | | | | | | | and the first thing job_attach_node does is... set the field to BUILDING. probably remnants of code prior to refactoring okay captain_obvious
* dmesg(8) allocated a bit too much memory due to padding of structbluhm2019-12-241-2/+3
| | | | | msgbuf. Use the same size algorithm in kernel and userland. OK cheloha@ guenther@ deraadt@
* Fill in names for consbufsize and consbuf sysctl for nicer kdump(1)bluhm2019-12-241-3/+3
| | | | output.
* Merge two missed fixes from login.c to login_passwd.c.millert2019-12-241-4/+5
| | | | | | - use the correct length when checking for "-v lastchance=yes" - don't try to zero pass if it is NULL From miod@
* The console buffer is allocated during startup. initconsbuf() isbluhm2019-12-241-9/+4
| | | | | | | only called from main(). There allocation must not fail, so better use M_WAITOK and remove error handling. As it is not a temporary buffer, M_TTYS is more appropriate. OK deraadt@ mpi@
* simplify assertionsanton2019-12-241-17/+5
|
* Fix name of option, GitHub issue 2030.nicm2019-12-241-3/+3
|
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.