summaryrefslogtreecommitdiffstats
path: root/share/man (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Add imxtmu(4), a driver to support the temperature sensors onpatrick2019-08-272-3/+51
| | | | | | the i.MX8M SoCs. ok kettenis@
* amlclock(4)kettenis2019-08-271-0/+42
|
* amlclock(4)kettenis2019-08-272-4/+5
|
* amlreset(4)kettenis2019-08-262-3/+45
|
* amluart(4)kettenis2019-08-262-2/+44
|
* sysctl(2): add kern.utc_offset: successor to the DST/TIMEZONE options(4)cheloha2019-08-211-2/+3
| | | | | | | | | | | | | | | | | | | | | The DST and TIMEZONE options(4) are incompatible with KARL, so we need some other way to compensate for an RTC running with a known offset. Enter kern.utc_offset, an offset in minutes East of UTC. TIMEZONE has always been minutes West, but this is inconsistent with how everyone else talks about timezones, hence the flip. TIMEZONE has the advantage of being compiled into the binary. Our new sysctl(2) has no such luck, so it needs to be set as early as possible in boot, from sysctl.conf(5), so we can correct the kernel clock from the RTC's local time to UTC before daemons like ntpd(8) and cron(8) start. To encourage this, kern.utc_offset is made immutable after the securelevel(7) is raised to 1. Prompted by yasuoka@. Discussed with deraadt@, kettenis@, yasuoka@. Additional testing by yasuoka@. ok deraadt@, yasuoka@
* i broke the example slightly by making the driver more compliant with 802.1Q.dlg2019-08-201-4/+7
|
* Mention ipmi@acpi and ipmi@iic. Add a short description for SSIF.kettenis2019-08-191-2/+6
|
* knock out useless Pp;jmc2019-08-161-2/+1
|
* STP works fine on etherip(4), it was gif(4) that lacked a MAC address.dlg2019-08-161-5/+2
| | | | | | | | | | | | getting etherip(4) to talk to a switch so i could verify this was pretty fun. remi@ pointed this bit of the manpage out somewhere, but it didn't seem right anymore since etherip(4) was split out of gif(4). these days if we have an interface that can be added to a bridge, we try to make it look like an actual ethernet interface, which includes having a mac address. we don't really have interfaces that change modes and have these edge cases anymore.
* instructions for replacing cert.pem are probably more harmful than helpful.tedu2019-08-121-14/+2
| | | | noticed by freda_bundchen. ok gilles millert
* No specific called "exec(3)", so move primary manpage to a name whichderaadt2019-08-111-7/+4
| | | | | | | | does exist -- execv(3). Still call this a family but without "Nm". Adjust Xr in various pages to refer to the precise function used rather than the family, in most cases the semantics of execve(2) are being referenced, so change the Xr. ok jmc
* sxisyscon(4)kettenis2019-08-111-2/+3
|
* sxisyscon(4)kettenis2019-08-111-0/+42
|
* remove groff leftover. from micah muertb2019-08-101-4/+2
|
* add zte mf920v; from christoph r. winterjmc2019-08-091-2/+4
|
* Fix a bunch of typos in various man pages.fcambus2019-08-081-3/+3
|
* Document iwm(4) CCMP offload support. Text copied from iwn(4) man page.stsp2019-08-081-2/+6
|
* clarify the DEBUG text a little, since sthen noted it wasn;t particularlyjmc2019-08-081-4/+5
| | | | | | clear; ok/tweaks sthen
* add a manual page for smbiosjsg2019-08-052-2/+38
| | | | ok kettenis@
* Xr pf 4dlg2019-08-051-1/+2
|
* document how to make technically non-compliant TPMRsdlg2019-08-051-2/+17
|
* tweak the iavf text a little, and add an entry to pci.4;jmc2019-08-042-6/+8
| | | | ok jmatthew
* add a manpage for tpmr(4).dlg2019-08-012-3/+167
| | | | | the examples section need to be cut down a lot, but this is a good start.
* uppercase Ethernet;jmc2019-07-311-3/+3
|
* basic man page for iavf(4)jmatthew2019-07-302-2/+51
|
* remove uneeded macro in previous;jmc2019-07-301-3/+2
|
* Expand description of ac_flag values into a tagged list.millert2019-07-291-7/+38
| | | | OK mestre@ jmc@ deraadt@
* Add AUNVEIL bit to the acct(5) manpage since it's already being used by bothmestre2019-07-291-2/+3
| | | | | | kernel and userland. OK deraadt@ jmc@
* vinvalbuf(9): tlseep -> tsleep_nsec(9); ok millert@cheloha2019-07-251-5/+9
|
* vwaitforio(9): tsleep(9) -> tsleep_nsec(9); ok visa@cheloha2019-07-191-4/+9
|
* getblk(9): tsleep(9) -> tsleep_nsec(9); ok visa@cheloha2019-07-191-4/+4
|
* explain escaping of end-of-sentence characters;schwarze2019-07-152-4/+17
| | | | missing info reported by Ian <ropers at gmail dot com> on misc@
* Document locking with fdrelease().visa2019-07-151-2/+5
|
* one old PERMIT_* escaped! they're gone nowespie2019-07-141-3/+3
|
* non-null -> not .Dv NULLmpi2019-07-121-5/+6
| | | | Suggested by schwarze@ in a different thread
* Document & cross Xr rtable_walk(9).mpi2019-07-123-4/+80
| | | | With inputs from jmc@ and schwarze@
* REGRESS_ROOT_TARGETS has less magic than documentedespie2019-07-091-3/+3
| | | | okay bluhm@
* The non-standard .EX/.EE macro pair was invented for Version 9 AT&T UNIXschwarze2019-07-091-6/+10
| | | | | | and only got adopted by GNU two decades later. Thanks to Doug McIlroy <doug at cs dot dartmouth dot edu> for pointing out the error.
* more cleanup, in particular remove more braces around .Dv,schwarze2019-07-081-23/+11
| | | | remove some bogus .Dv, and get rid of .Tn
* Get rid of an old convention of wrapping preprocessor constants in curlyanton2019-07-081-5/+5
| | | | | | braces. no objection from jmc@ and schwarze@
* tweak previous; ok dlgjmc2019-07-051-22/+16
|
* make the pointer value argument name "v" instead of "value"dlg2019-07-051-6/+9
| | | | | | | | this makes a sentence read better when there's no syntax hilighting in effect. while here, say the write-write memory barrier is implemented with membar_producer so it's easier to go read about what that provides.
* Xr between all the different smr pages.dlg2019-07-053-10/+16
|
* +aggr.4dlg2019-07-051-2/+3
|
* make a start at a manpage for aggr(4)dlg2019-07-051-0/+130
|
* Remove a useless kernel lock from the TCP socket splicing path.bluhm2019-07-041-6/+9
| | | | | | | | | | | When send buffer space in the drain socket becomes available, a task is added to move data, and also the userland was informed. The latter is not usefull as this would mix a kernel and user stream. So programs do not wait for this event. Avoid calling sowakeup() from sowwakeup(), this also reduces grabing the kernel lock. Instead inform the userland about the write event when the splicing is dissolved in sounsplice(). OK claudio@
* Add tsleep_nsec(9), msleep_nsec(9), and rwsleep_nsec(9).cheloha2019-07-031-7/+74
| | | | | | | | | | | | | | | | | | | | | | | | Equivalent to their unsuffixed counterparts except that (a) they take a timeout in terms of nanoseconds, and (b) INFSLP, aka UINT64_MAX (not zero) indicates that a timeout should not be set. For now, zero nanoseconds is not a strictly valid invocation: we log a warning on DIAGNOSTIC kernels if we see such a call. We still sleep until the next tick in such a case, however. In the future this could become some sort of poll... TBD. To facilitate conversions to these interfaces: add inline conversion functions to sys/time.h for turning your timeout into nanoseconds. Also do a few easy conversions for warmup and to demonstrate how further conversions should be done. Lots of input from mpi@ and ratchov@. Additional input from tedu@, deraadt@, mortimer@, millert@, and claudio@. Partly inspired by FreeBSD r247787. positive feedback from deraadt@, ok mpi@
* use the standard spelling of the word "idiosyncrasy";schwarze2019-07-011-3/+3
| | | | suggested by Michal Nowak <mnowak at startmail dot com>
* document control name changesespie2019-07-011-5/+9
|
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.