gmane.os.netbsd.devel.userlevel archive

495 archived articles, newest first (page 2 of 5). Latest articles →

Re: PR 43133 should be closed
Sat, 28 Feb 2026 06:34:07 +0700
Robert Elz <[email protected]> • #23826
Re: PR 43133 should be closed
Fri, 27 Feb 2026 13:06:58 -0500 (EST)
Mouse <[email protected]> • #23825
Re: PR 43133 should be closed
Fri, 27 Feb 2026 22:51:29 +0700
Robert Elz <[email protected]> • #23824
Re: PR 43133 should be closed
Fri, 27 Feb 2026 09:00:32 +0000 (UTC)
Benny Siegert <[email protected]> • #23823
Re: PR 17179 can be closed
Fri, 27 Feb 2026 00:48:00 +0100
Hauke Fath <[email protected]> • #23822
Re: PR 17179 can be closed
Thu, 26 Feb 2026 17:43:45 -0600
Jacob Pipkin <[email protected]> • #23821
PR 43133 should be closed
Thu, 26 Feb 2026 17:28:11 -0600
[email protected] • #23820
Re: PR 17179 can be closed
Fri, 27 Feb 2026 06:25:05 +0700
Robert Elz <[email protected]> • #23819
PR 17179 can be closed
Thu, 26 Feb 2026 14:42:34 -0600
Jacob Pipkin <[email protected]> • #23818
Re: PR 28402
Mon, 23 Feb 2026 11:30:20 -0600
Jacob Pipkin <[email protected]> • #23817
PR 28402
Mon, 23 Feb 2026 11:21:59 -0600
Jacob Pipkin <[email protected]> • #23816
ccgconfig(8) questions
Sat, 21 Feb 2026 07:38:40 +0700
Robert Elz <[email protected]> • #23815
Re: Managing pkgsrc openssl certs
Wed, 18 Feb 2026 11:17:22 +0100
Edgar Fuß <[email protected]> • #23814
Managing pkgsrc openssl certs
Mon, 16 Feb 2026 17:18:36 +0100
Edgar Fuß <[email protected]> • #23813
Re: rm -iR
Fri, 6 Feb 2026 16:33:51 -0500
Jan Schaumann <[email protected]> • #23812
Re: rm -iR
Wed, 04 Feb 2026 15:46:03 +0700
Robert Elz <[email protected]> • #23811
Re: rm -iR
Wed, 4 Feb 2026 05:48:24 +0000 (UTC)
RVP <[email protected]> • #23810
Re: rm -iR
Tue, 03 Feb 2026 17:27:22 -0500
Greg Troxel <[email protected]> • #23809
Re: rm -iR
Tue, 3 Feb 2026 16:52:17 -0500 (EST)
Mouse <[email protected]> • #23808
Re: rm -iR
Tue, 3 Feb 2026 16:11:57 -0500
Jan Schaumann <[email protected]> • #23807
Re: rm -iR
Tue, 03 Feb 2026 15:21:04 -0500
Greg Troxel <[email protected]> • #23806
rm -iR
Tue, 3 Feb 2026 14:30:46 -0500
Jan Schaumann <[email protected]> • #23805
Re: editline's readline compat
Sun, 25 Jan 2026 16:08:17 -0500 (EST)
Mouse <[email protected]> • #23804
editline's readline compat
Sun, 25 Jan 2026 13:48:22 -0500
Greg Troxel <[email protected]> • #23803
Re: set -e oddity
Sun, 25 Jan 2026 03:20:39 +0700
Robert Elz <[email protected]> • #23802
set -e oddity
Sat, 24 Jan 2026 19:24:16 +0100
Edgar Fuß <[email protected]> • #23801
Fully integrate zstd into base system
Fri, 16 Jan 2026 01:36:24 +1100
Simon Burge <[email protected]> • #23800
Re: set -e again
Wed, 14 Jan 2026 21:22:49 +0700
Robert Elz <[email protected]> • #23799
Re: set -e again
Wed, 14 Jan 2026 21:09:41 +0700
Robert Elz <[email protected]> • #23798
Re: set -e again
Wed, 14 Jan 2026 13:46:16 +0000
Crystal Kolipe <[email protected]> • #23797
Re: set -e again
Wed, 14 Jan 2026 13:39:42 +0000 (UTC)
RVP <[email protected]> • #23796
Re: set -e again
Wed, 14 Jan 2026 07:41:41 -0500 (EST)
Mouse <[email protected]> • #23795
Re: set -e again
Wed, 14 Jan 2026 10:28:37 +0000
Crystal Kolipe <[email protected]> • #23794
Re: set -e again
Tue, 13 Jan 2026 21:30:58 -0500 (EST)
Mouse <[email protected]> • #23793
Re: set -e again
Tue, 13 Jan 2026 18:14:51 -0800
"Greg A. Woods" <[email protected]> • #23792
set -e again
Wed, 14 Jan 2026 01:18:47 +0000
David Holland <[email protected]> • #23791
udp and spec issues
Wed, 7 Jan 2026 09:15:12 +0530
sayan chaudhuri <[email protected]> • #23790
Re: base is too large
Sun, 4 Jan 2026 19:54:10 +0000
nia <[email protected]> • #23789
Re: base is too large
Sun, 4 Jan 2026 19:48:38 +0300
Valery Ushakov <[email protected]> • #23788
Re: base is too large
Sun, 4 Jan 2026 10:57:16 -0500 (EST)
Mouse <[email protected]> • #23787
Re: base is too large
Sun, 4 Jan 2026 16:30:21 +0100
Tobias Nygren <[email protected]> • #23786
Re: base is too large
Sun, 4 Jan 2026 15:14:13 +0000
Taylor R Campbell <[email protected]> • #23785
Re: base is too large
Sun, 04 Jan 2026 09:31:19 -0500
Greg Troxel <[email protected]> • #23784
base is too large
Sun, 4 Jan 2026 12:22:08 +0000
nia <[email protected]> • #23783
Re: Replacing GNU diff
Sat, 27 Dec 2025 14:45:19 -0800
Jason Thorpe <[email protected]> • #23782
Re: Replacing GNU diff
Sat, 27 Dec 2025 21:16:29 +0000
nia <[email protected]> • #23781
Re: Replacing GNU diff
Sat, 27 Dec 2025 12:29:37 -0800
Jason Thorpe <[email protected]> • #23780
Re: Replacing GNU diff
Sat, 27 Dec 2025 20:22:29 +0000
nia <[email protected]> • #23779
Re: Bug in scanf?
Fri, 19 Dec 2025 14:04:53 +0100
наб <[email protected]> • #23778
Re: odd script(1) behavior - script bug, man bug, ?
Wed, 17 Dec 2025 09:11:49 +0000 (UTC)
RVP <[email protected]> • #23777
Re: odd script(1) behavior - script bug, man bug, ?
Tue, 16 Dec 2025 13:11:25 -0500
Greg Troxel <[email protected]> • #23776
Re: odd script(1) behavior - script bug, man bug, ?
Tue, 16 Dec 2025 12:57:27 -0500 (EST)
Mouse <[email protected]> • #23775
Re: odd script(1) behavior - script bug, man bug, ?
Tue, 16 Dec 2025 12:45:41 -0500
Greg Troxel <[email protected]> • #23774
Re: odd script(1) behavior - script bug, man bug, ?
Tue, 16 Dec 2025 12:28:25 -0500 (EST)
Mouse <[email protected]> • #23773
Re: odd script(1) behavior - script bug, man bug, ?
Tue, 16 Dec 2025 12:05:44 -0500
Greg Troxel <[email protected]> • #23772
Re: odd script(1) behavior - script bug, man bug, ?
Tue, 16 Dec 2025 11:11:30 -0500 (EST)
Mouse <[email protected]> • #23771
odd script(1) behavior - script bug, man bug, ?
Tue, 16 Dec 2025 08:42:42 -0500
Greg Troxel <[email protected]> • #23770
Re: Bug in scanf?
Wed, 10 Dec 2025 19:21:05 +0300
Valery Ushakov <[email protected]> • #23769
Re: Bug in scanf?
Wed, 10 Dec 2025 15:36:55 +0000
Crystal Kolipe <[email protected]> • #23768
Re: Bug in scanf?
Wed, 10 Dec 2025 16:03:08 +0100
Martin Husemann <[email protected]> • #23767
Re: Bug in scanf?
Wed, 10 Dec 2025 15:55:22 +0100
Edgar Fuß <[email protected]> • #23766
Re: Bug in scanf?
Wed, 10 Dec 2025 15:19:59 +0100
Martin Husemann <[email protected]> • #23765
Re: Bug in scanf?
Wed, 10 Dec 2025 06:13:55 -0800
Carlo Arenas <[email protected]> • #23764
Re: Bug in scanf?
Wed, 10 Dec 2025 17:09:49 +0300
Valery Ushakov <[email protected]> • #23763
Re: Bug in scanf?
Wed, 10 Dec 2025 08:04:26 -0600
Jacob Pipkin <[email protected]> • #23762
Re: Bug in scanf?
Wed, 10 Dec 2025 10:07:15 +0100
Anders Magnusson <[email protected]> • #23761
Re: Bug in scanf?
Tue, 9 Dec 2025 20:22:44 +0100
Roland Illig <[email protected]> • #23760
Re: Bug in scanf?
Tue, 9 Dec 2025 09:27:43 +0100
Anders Magnusson <[email protected]> • #23759
Re: Bug in scanf?
Tue, 09 Dec 2025 10:24:19 +0700
Robert Elz <[email protected]> • #23758
Re: Bug in scanf?
Tue, 09 Dec 2025 09:49:00 +0700
Robert Elz <[email protected]> • #23757
Bug in scanf?
Mon, 8 Dec 2025 20:45:00 +0100
Anders Magnusson <[email protected]> • #23756
Re: '/bin/sh -c' with multiple args
Fri, 5 Dec 2025 08:31:39 +0100
Michael van Elst <[email protected]> • #23755
Re: '/bin/sh -c' with multiple args
Fri, 05 Dec 2025 09:57:49 +0700
Robert Elz <[email protected]> • #23754
Re: '/bin/sh -c' with multiple args
Fri, 05 Dec 2025 09:11:25 +0700
Robert Elz <[email protected]> • #23753
Re: '/bin/sh -c' with multiple args
Thu, 4 Dec 2025 19:59:54 -0500
Jan Schaumann <[email protected]> • #23752
Re: '/bin/sh -c' with multiple args
Fri, 05 Dec 2025 07:44:31 +0700
Robert Elz <[email protected]> • #23751
Re: '/bin/sh -c' with multiple args
Fri, 5 Dec 2025 00:15:43 +0000
Taylor R Campbell <[email protected]> • #23750
Re: '/bin/sh -c' with multiple args
Thu, 4 Dec 2025 23:08:53 +0000 (UTC)
RVP <[email protected]> • #23749
Re: '/bin/sh -c' with multiple args
Thu, 4 Dec 2025 22:41:36 +0000 (UTC)
RVP <[email protected]> • #23748
Re: '/bin/sh -c' with multiple args
Thu, 4 Dec 2025 23:08:38 +0100
Roland Illig <[email protected]> • #23747
Re: '/bin/sh -c' with multiple args
Thu, 4 Dec 2025 22:01:56 -0000 (UTC)
[email protected] (Michael van Elst) • #23746
'/bin/sh -c' with multiple args
Thu, 4 Dec 2025 16:52:12 -0500
Jan Schaumann <[email protected]> • #23745
Re: Sharing ELF definitions between NetBSD userspace and kernel
Sat, 29 Nov 2025 19:52:24 +0000
David Holland <[email protected]> • #23744
Re: Replacing GNU diff
Fri, 28 Nov 2025 09:51:48 -0800
"Greg A. Woods" <[email protected]> • #23743
Replacing GNU diff
Fri, 28 Nov 2025 15:16:58 +0000
nia <[email protected]> • #23742
Re: Sharing ELF definitions between NetBSD userspace and kernel
Wed, 26 Nov 2025 19:14:12 +0000
"Joseph Koshy" <[email protected]> • #23741
Re: Sharing ELF definitions between NetBSD userspace and kernel
Tue, 25 Nov 2025 17:13:29 -0500 (EST)
Mouse <[email protected]> • #23740
Sharing ELF definitions between NetBSD userspace and kernel
Tue, 25 Nov 2025 21:22:48 +0000
"Joseph Koshy" <[email protected]> • #23739
Re: How signal-safe is our malloc()?
Wed, 19 Nov 2025 03:56:57 +0000
David Holland <[email protected]> • #23738
Re: mount race prevention
Tue, 18 Nov 2025 18:57:07 +0000
Crystal Kolipe <[email protected]> • #23737
Re: mount race prevention
Tue, 18 Nov 2025 13:58:02 -0500 (EST)
Mouse <[email protected]> • #23736
Re: mount race prevention
Tue, 18 Nov 2025 19:36:11 +0100
Edgar Fuß <[email protected]> • #23735
Re: mount race prevention
Tue, 18 Nov 2025 12:25:56 -0500 (EST)
Mouse <[email protected]> • #23734
mount race prevention
Tue, 18 Nov 2025 17:53:50 +0100
Edgar Fuß <[email protected]> • #23733
Re: ipcs(1) manual page
Fri, 14 Nov 2025 14:35:29 -0500
Jan Schaumann <[email protected]> • #23732
Re: How signal-safe is our malloc()?
Fri, 14 Nov 2025 19:07:43 -0000 (UTC)
[email protected] (Christos Zoulas) • #23731
Re: ipcs(1) manual page
Fri, 14 Nov 2025 21:56:01 +0300
Valery Ushakov <[email protected]> • #23730
How signal-safe is our malloc()?
Fri, 14 Nov 2025 13:55:08 -0500 (EST)
Mouse <[email protected]> • #23729
Re: Replacing malloc et al in programs.
Fri, 14 Nov 2025 21:50:13 +0300
Valery Ushakov <[email protected]> • #23728
Re: ipcs(1) manual page
Fri, 14 Nov 2025 08:10:37 -0500
Jan Schaumann <[email protected]> • #23727
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.