| Time | Subject | # followups | From |
|---|
| Wed, 31 May 2023 |
| 18:56 |
Re: [RFC] inetd(8) changes proposal |
(0) |
tlaronde |
| 18:53 |
Re: [RFC] inetd(8) changes proposal |
(0) |
Mouse |
| 18:25 |
Re: [RFC] inetd(8) changes proposal |
(0) |
tlaronde |
| 18:19 |
Re: [RFC] inetd(8) changes proposal |
(1) |
tlaronde |
| 17:15 |
Re: [RFC] inetd(8) changes proposal |
(0) |
tlaronde |
| 12:16 |
Re: [RFC] inetd(8) changes proposal |
(1) |
Mouse |
| 12:12 |
Re: [RFC] inetd(8) changes proposal |
(0) |
Mouse |
| 11:57 |
Re: [RFC] inetd(8) changes proposal |
(3) |
Luke Mewburn |
| 11:50 |
Re: [RFC] inetd(8) changes proposal |
(0) |
Luke Mewburn |
| 11:50 |
Re: [RFC] inetd(8) changes proposal |
(1) |
Mouse |
| 11:29 |
Re: [RFC] inetd(8) changes proposal |
(0) |
tlaronde |
| 11:20 |
Re: [RFC] inetd(8) changes proposal |
(2) |
tlaronde |
| 10:55 |
Re: [RFC] inetd(8) changes proposal |
(1) |
tlaronde |
| 10:44 |
Re: [RFC] inetd(8) changes proposal |
(2) |
tlaronde |
| 10:42 |
Re: [RFC] inetd(8) changes proposal |
(1) |
Luke Mewburn |
| Tue, 30 May 2023 |
| 23:35 |
Re: [RFC] inetd(8) changes proposal |
(1) |
Mouse |
| 21:33 |
Re: [RFC] inetd(8) changes proposal |
(3) |
Robert Elz |
| 19:03 |
Re: [RFC] inetd(8) changes proposal |
(0) |
tlaronde |
| 17:33 |
Re: [RFC] inetd(8) changes proposal |
(3) |
Robert Elz |
| 15:55 |
Re: bl*cklist configuration, ssh only |
(1) |
Michael van Elst |
| 14:23 |
bl*cklist configuration, ssh only |
(1) |
ignatios |
| 14:12 |
[RFC] inetd(8) changes proposal |
(2) |
tlaronde |
| 10:17 |
Re: Sanitizing (canonicalising) the block device n |
(0) |
J. Hannken-Illjes |
| Mon, 29 May 2023 |
| 12:50 |
Re: inetd(8): continue or exit on error? |
(0) |
tlaronde |
| 12:37 |
Re: inetd(8): continue or exit on error? |
(1) |
Taylor R Campbell |
| 11:49 |
Re: inetd(8): continue or exit on error? |
(1) |
Mouse |
| 11:30 |
Re: inetd(8): continue or exit on error? |
(1) |
tlaronde |
| 11:25 |
Re: inetd(8): continue or exit on error? |
(0) |
tlaronde |
| 11:19 |
Re: inetd(8): continue or exit on error? |
(1) |
Taylor R Campbell |
| 11:14 |
Re: inetd(8): continue or exit on error? |
(1) |
tlaronde |
| 10:44 |
Re: inetd(8): continue or exit on error? |
(1) |
David Brownlee |
| 10:38 |
Re: inetd(8): continue or exit on error? |
(1) |
Michael van Elst |
| 10:11 |
Re: inetd(8): continue or exit on error? |
(0) |
tlaronde |
| 09:47 |
Re: inetd(8): continue or exit on error? |
(2) |
tlaronde |
| 09:04 |
Re: inetd(8): continue or exit on error? |
(1) |
Michael van Elst |
| 08:11 |
inetd(8): continue or exit on error? |
(3) |
tlaronde |
| Sun, 28 May 2023 |
| 10:54 |
Re: MAXPATHLEN vs PATH_MAX |
(0) |
tlaronde |
| 06:26 |
Re: MAXPATHLEN vs PATH_MAX |
(1) |
David Holland |
| 06:00 |
Re: MAXPATHLEN vs PATH_MAX |
(1) |
tlaronde |
| Sat, 27 May 2023 |
| 21:22 |
Re: Sanitizing (canonicalising) the block device n |
(0) |
Robert Elz |
| 20:50 |
Re: MAXPATHLEN vs PATH_MAX |
(1) |
David Holland |
| 18:59 |
Re: Sanitizing (canonicalising) the block device n |
(0) |
Mouse |
| 18:42 |
Re: Sanitizing (canonicalising) the block device n |
(0) |
tlaronde |
| 18:40 |
Re: Sanitizing (canonicalising) the block device n |
(0) |
Mouse |
| 18:11 |
Re: Sanitizing (canonicalising) the block device n |
(1) |
tlaronde |
| 17:04 |
Sanitizing (canonicalising) the block device name |
(5) |
Robert Elz |
| 12:12 |
[BUG] in src/usr.sbin/inetd (?) |
(0) |
tlaronde |
| 07:13 |
MAXPATHLEN vs PATH_MAX |
(1) |
tlaronde |
| Wed, 24 May 2023 |
| 19:28 |
Bugs in sbin/mount/pathadj.c? |
(0) |
tlaronde |
| Tue, 23 May 2023 |
| 22:05 |
Re: pulling in changes to nsswitch from FreeBSD? |
(0) |
Brett Lymn |
| Thu, 18 May 2023 |
| 21:28 |
Re: unresolvable R_X86_64_NONE relocation against |
(0) |
RVP |
| 12:16 |
Re: unresolvable R_X86_64_NONE relocation against |
(1) |
Edgar Fuß |
| 12:03 |
Re: pulling in changes to nsswitch from FreeBSD? |
(1) |
Taylor R Campbell |
| 09:37 |
Re: unresolvable R_X86_64_NONE relocation against |
(1) |
RVP |
| 08:30 |
porting nss-pam-ldapd (was: pulling in changes to |
(0) |
Edgar Fuß |
| Wed, 17 May 2023 |
| 22:24 |
pulling in changes to nsswitch from FreeBSD? |
(2) |
Brett Lymn |
| 20:37 |
Re: NetBSD 10 and NetBSD 11... |
(0) |
Jason Thorpe |
| 19:39 |
NetBSD 10 and NetBSD 11... |
(1) |
tlaronde |
| 19:34 |
Re: NetBSD 10 and NetBSD 11... |
(1) |
Martin Husemann |
| 19:19 |
Re: NetBSD 10 and NetBSD 11... |
(2) |
Jason Thorpe |
| 19:14 |
Re: NetBSD 10 and NetBSD 11... |
(2) |
tlaronde |
| 19:09 |
Re: NetBSD 10 and NetBSD 11... |
(1) |
Martin Husemann |
| 19:09 |
Re: NetBSD 10 and NetBSD 11... |
(0) |
tlaronde |
| 19:09 |
Re: NetBSD 10 and NetBSD 11... |
(0) |
tlaronde |
| 15:06 |
unresolvable R_X86_64_NONE relocation against symb |
(1) |
Edgar Fuß |
| 09:33 |
Re: using gas/gld from devel/binutils |
(0) |
Martin Husemann |
| 09:18 |
Re: using gas/gld from devel/binutils |
(1) |
Edgar Fuß |
| Mon, 08 May 2023 |
| 16:54 |
Re: debugging/tracing a setuid program |
(0) |
Mouse |
| 16:12 |
Re: debugging/tracing a setuid program |
(1) |
Edgar Fuß |
| Fri, 05 May 2023 |
| 18:42 |
Re: debugging/tracing a setuid program |
(1) |
Mouse |
| 18:39 |
Re: debugging/tracing a setuid program |
(0) |
Emmanuel Dreyfus |
| 18:29 |
Re: debugging/tracing a setuid program |
(2) |
Edgar Fuß |
| 17:31 |
Re: debugging/tracing a setuid program |
(1) |
Mouse |
| 17:20 |
Re: debugging/tracing a setuid program |
(1) |
Edgar Fuß |
| 16:57 |
Re: debugging/tracing a setuid program |
(1) |
Mouse |
| 16:48 |
debugging/tracing a setuid program |
(1) |
Edgar Fuß |
| Wed, 03 May 2023 |
| 00:19 |
Re: usr.bin/mail: cmd3.c:bangexp(): "borked"?, and |
(0) |
Steffen Nurpmeso |
| 00:09 |
usr.bin/mail: cmd3.c:bangexp(): "borked"?, and BSD |
(1) |
Steffen Nurpmeso |