current-users  

Messages by Thread

• • re: MKCROSSGDB=yes broken in new gdb? matthew green
  • Re: MKCROSSGDB=yes broken in new gdb? Christos Zoulas
  • re: MKCROSSGDB=yes broken in new gdb? matthew green
  • Re: MKCROSSGDB=yes broken in new gdb? Christos Zoulas
• 10.99.7 panic: defibrillate Thomas Klausner
  • Re: 10.99.7 panic: defibrillate Taylor R Campbell
  • Re: 10.99.7 panic: defibrillate Thomas Klausner
  • Re: 10.99.7 panic: defibrillate Thomas Klausner
  • Re: 10.99.7 panic: defibrillate Taylor R Campbell
  • Re: 10.99.7 panic: defibrillate Taylor R Campbell
  • Re: 10.99.7 panic: defibrillate Greg Troxel
  • Re: 10.99.7 panic: defibrillate Taylor R Campbell
  • Re: 10.99.7 panic: defibrillate Thomas Klausner
  • Re: 10.99.7 panic: defibrillate Thomas Klausner
  • Re: 10.99.7 panic: defibrillate Taylor R Campbell
• 10.0_BETA w/MKNSD=yes build fails after OpenSSL update John D. Baker
  • Re: 10.0_BETA w/MKNSD=yes build fails after OpenSSL update Martin Husemann
• axen0 - invalid buffer(pkt#1), continue Lizbeth Mutterhunt, Ph.D
  • axen0 - invalid buffer(pkt#1), continue Lizbeth Mutterhunt, Ph.D
  • axen0 - invalid buffer(pkt#1), continue Lizbeth Mutterhunt, Ph.D
  • axen0 - invalid buffer(pkt#1), continue Lizbeth Mutterhunt, Ph.D
  • axen0 - invalid buffer(pkt#1), continue Lizbeth Mutterhunt, Ph.D
• Build failure for gdb on amd64 Paul Goyette
• distrib sets error for DEBUG build Paul Goyette
• Re: Build failure Paul Goyette
• Why can't a WireGuard interface route packets to itself? logothesia
  • Re: Why can't a WireGuard interface route packets to itself? Lloyd Parkes
  • Re: Why can't a WireGuard interface route packets to itself? logothesia
  • Re: Why can't a WireGuard interface route packets to itself? Lloyd Parkes
  • Re: Why can't a WireGuard interface route packets to itself? logothesia
  • Re: Why can't a WireGuard interface route packets to itself? Martin Husemann
  • Re: Why can't a WireGuard interface route packets to itself? logothesia
• Strange behavior for route(8) Paul Goyette
  • Re: Strange behavior for route(8) Greg Troxel
  • Re: Strange behavior for route(8) Paul Goyette
  • Re: Strange behavior for route(8) Martin Neitzel
• video (nouveau) speed-up with 10.99.6 Paul Goyette
• Regression in -current Chavdar Ivanov
  • Re: Regression in -current Chavdar Ivanov
  • Re: Regression in -current Robert Nestor
  • Re: Regression in -current Chavdar Ivanov
• build.sh now NETBSDSRCDIR/mk.conf if present Luke Mewburn
  • Re: build.sh now NETBSDSRCDIR/mk.conf if present David Holland
• nvmm pci passthrough? Malte Dehling
• kernel size change Thomas Klausner
  • Re: kernel size change Thomas Klausner
  • Re: kernel size change Jonathan A. Kollasch
  • Re: kernel size change RVP
  • Re: kernel size change Thomas Klausner
  • Re: kernel size change RVP
  • Re: kernel size change Thomas Klausner
  • Re: kernel size change RVP
  • Re: kernel size change RVP
  • Re: kernel size change Thomas Klausner
  • Re: kernel size change Valery Ushakov
  • Re: kernel size change RVP
• Unable to complete build of aarch64 Chavdar Ivanov
  • Re: Unable to complete build of aarch64 Chavdar Ivanov
  • Re: Unable to complete build of aarch64 RVP
  • Re: Unable to complete build of aarch64 Chavdar Ivanov
• support for Raspberry Pi zero 2 w Dave Tyson
• New ddb command: show all tstiles Taylor R Campbell
• fdisk and alignment David Brownlee
  • Re: fdisk and alignment Martin Husemann
  • Re: fdisk and alignment RVP
  • Re: fdisk and alignment Izumi Tsutsui
  • Re: fdisk and alignment David Brownlee
  • Re: fdisk and alignment Martin Husemann
  • Re: fdisk and alignment David Brownlee
• Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Taylor R Campbell
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Brad Spencer
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Taylor R Campbell
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Taylor R Campbell
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Brad Spencer
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Taylor R Campbell
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Brad Spencer
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Brad Spencer
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Brad Spencer
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Brad Spencer
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Taylor R Campbell
  • re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" matthew green
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Taylor R Campbell
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Brad Spencer
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Taylor R Campbell
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Brad Spencer
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Taylor R Campbell
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Brad Spencer
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Taylor R Campbell
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Brad Spencer
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Brad Spencer
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Brad Spencer
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Taylor R Campbell
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Brad Spencer
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Taylor R Campbell
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Brad Spencer
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Taylor R Campbell
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Brad Spencer
  • Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards" Brad Spencer
• modesetting vs intel in 10.0 nia
  • Re: modesetting vs intel in 10.0 David Brownlee
  • Re: modesetting vs intel in 10.0 nia
  • Re: modesetting vs intel in 10.0 David Brownlee
  • Re: modesetting vs intel in 10.0 Lloyd Parkes
  • Re: modesetting vs intel in 10.0 Chavdar Ivanov
  • Re: modesetting vs intel in 10.0 Paul Ripke
  • Re: modesetting vs intel in 10.0 Chavdar Ivanov
  • Re: modesetting vs intel in 10.0 Mike Pumford
  • Re: modesetting vs intel in 10.0 David Brownlee
  • Re: modesetting vs intel in 10.0 David Brownlee
  • Re: modesetting vs intel in 10.0 nia
  • Re: modesetting vs intel in 10.0 Greg Troxel
  • Re: modesetting vs intel in 10.0 nia
  • Re: modesetting vs intel in 10.0 Paul Ripke
  • Re: modesetting vs intel in 10.0 Greg Troxel
  • Re: modesetting vs intel in 10.0 Rhialto
  • Re: modesetting vs intel in 10.0 David Brownlee
  • Re: modesetting vs intel in 10.0 Brian Stuart
  • Re: modesetting vs intel in 10.0 David Brownlee
  • Re: modesetting vs intel in 10.0 Greg Troxel
  • Re: modesetting vs intel in 10.0 Robert Swindells
  • re: modesetting vs intel in 10.0 matthew green
  • Re: modesetting vs intel in 10.0 Robert Swindells
  • re: modesetting vs intel in 10.0 matthew green
  • Re: modesetting vs intel in 10.0 nia
  • Re: modesetting vs intel in 10.0 Mike Pumford
  • Re: modesetting vs intel in 10.0 nia
• Call for testing: New kernel heartbeat(9) checks Taylor R Campbell
  • Re: Call for testing: New kernel heartbeat(9) checks Manuel Bouyer
  • Re: Call for testing: New kernel heartbeat(9) checks Taylor R Campbell
  • Re: Call for testing: New kernel heartbeat(9) checks Manuel Bouyer
  • Re: Call for testing: New kernel heartbeat(9) checks PHO
• Issues with X in NetBSD-current Brett Lymn
  • Re: Issues with X in NetBSD-current RVP
  • Re: Issues with X in NetBSD-current Brett Lymn
  • Re: Issues with X in NetBSD-current RVP
  • Re: Issues with X in NetBSD-current Brett Lymn
• Remove extra unlock in dm9000 driver Lwazi Dube
  • Re: Remove extra unlock in dm9000 driver Martin Husemann
• Build failure for malloc stuff - amd64 HEAD Paul Goyette
  • Re: Build failure for malloc stuff - amd64 HEAD Paul Goyette
• i386/openssl on amd64? Jan-Hinrich Fessel
  • Re: i386/openssl on amd64? Jan-Hinrich Fessel
  • Re: i386/openssl on amd64? Martin Husemann
  • Re: i386/openssl on amd64? Martin Husemann
• tweaks needed for 10 branch Andrew Cagney
  • Re: tweaks needed for 10 branch Martin Husemann
  • Re: tweaks needed for 10 branch Jason Thorpe
  • Re: tweaks needed for 10 branch Andrew Cagney
  • re: tweaks needed for 10 branch matthew green
  • Re: tweaks needed for 10 branch Andrew Cagney
• panic with UFS_DIRHASH Fekete Zoltán
  • Re: panic with UFS_DIRHASH Simon Burge
• NetBSD Security Advisory 2023-006: KDC-spoofing in pam_krb5 NetBSD Security-Officer
• NetBSD Security Advisory 2023-005: su(1) bypass via pam_ksu(8) NetBSD Security-Officer
• NetBSD Security Advisory 2023-004: procfs environ exposure NetBSD Security-Officer
• NetBSD Security Advisory 2023-003: Structure padding memory disclosures NetBSD Security-Officer
• NetBSD Security Advisory 2023-002: Various compatibility syscall memory access issues NetBSD Security-Officer
• NetBSD Security Advisory 2023-001: Multiple buffer overflows in USB drivers NetBSD Security-Officer
• cpu temperature readings Robert Elz
  • Re: cpu temperature readings Michael van Elst
  • Re: cpu temperature readings Michael van Elst
  • Re: cpu temperature readings Masanobu SAITOH
  • Re: cpu temperature readings Robert Elz
  • Re: cpu temperature readings RVP
  • Re: cpu temperature readings Robert Elz
  • Re: cpu temperature readings Robert Elz
  • Re: cpu temperature readings Michael van Elst
  • Re: cpu temperature readings Robert Elz
  • Re: cpu temperature readings Michael van Elst
  • Re: cpu temperature readings Robert Elz
  • Re: cpu temperature readings Rhialto
  • Re: cpu temperature readings Michael van Elst
  • Re: cpu temperature readings Robert Elz
  • Re: cpu temperature readings Michael van Elst
  • Re: cpu temperature readings Robert Elz
  • Re: cpu temperature readings Michael van Elst
  • Re: cpu temperature readings Robert Elz
  • Re: cpu temperature readings Robert Elz
  • Re: cpu temperature readings Michael van Elst
  • Re: cpu temperature readings Robert Elz
  • Re: cpu temperature readings Michael van Elst
  • Re: cpu temperature readings Robert Elz
  • Re: cpu temperature readings Michael van Elst
  • Re: cpu temperature readings Robert Elz
  • Re: cpu temperature readings Michael van Elst
  • Re: cpu temperature readings Masanobu SAITOH
  • Re: cpu temperature readings Robert Elz
  • Re: cpu temperature readings Michael van Elst
  • re: cpu temperature readings matthew green
• Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• Mounting NetBSD partition on voidlinux Sagar Acharya
  • Re: Mounting NetBSD partition on voidlinux Martin Husemann
  • Re: Mounting NetBSD partition on voidlinux Matthias Petermann
  • Re: Mounting NetBSD partition on voidlinux Sagar Acharya
  • Re: Mounting NetBSD partition on voidlinux Sagar Acharya
  • Re: Mounting NetBSD partition on voidlinux Matthias Petermann
  • Re: Mounting NetBSD partition on voidlinux Sagar Acharya
  • Re: Mounting NetBSD partition on voidlinux Martin Husemann
  • Re: FWD: Re: Mounting NetBSD partition on voidlinux Sagar Acharya

• Earlier messages
• Later messages