freebsd-current  

Messages by Thread

• • Re: sysutils/pam_xdg: Cancelled on -CURRENT Emmanuel Vadot
  • Re: sysutils/pam_xdg: Cancelled on -CURRENT Alastair Hogge
  • Re: sysutils/pam_xdg: Cancelled on -CURRENT Emmanuel Vadot
  • Re: sysutils/pam_xdg: Cancelled on -CURRENT Alastair Hogge
• Re: git: e34ea0196f44 - main - tcp: clear all TCP timers in tcp_timer_stop() when in callout Gleb Smirnoff
• kernel= , kern.module_path= , and loader menu selections: how to have it always find the matching, say, nfsd.ko (same directory as the kernel) Mark Millard
• after trivial update, 15.0 ARM64 system no longer boots Lexi Winter
  • Re: after trivial update, 15.0 ARM64 system no longer boots Ryan Stone
  • Re: after trivial update, 15.0 ARM64 system no longer boots Ronald Klop
  • Re: after trivial update, 15.0 ARM64 system no longer boots Lexi Winter
  • Re: after trivial update, 15.0 ARM64 system no longer boots Mark Millard
• [2 WEEKS LEFT REMINDER] Call for 2024Q1 status reports Lorenzo Salvadore
• Chromium can't be compiled because a bug with webrtc. Mario Marietto
• ZPool on iSCSI storage not available after a reboot Dennis Clarke
  • Re: ZPool on iSCSI storage not available after a reboot Alan Somers
  • Re: ZPool on iSCSI storage not available after a reboot Dennis Clarke
• RFC: should a va_bytes option be added to vn_getsize_locked()? Rick Macklem
  • Re: RFC: should a va_bytes option be added to vn_getsize_locked()? Konstantin Belousov
• Boot failure, amd64 (HP EliteBook 650 G10) Graham Perrin
  • Re: Boot failure, amd64 (HP EliteBook 650 G10) Warner Losh
  • Re: Boot failure, amd64 (HP EliteBook 650 G10) Philipp Ost
• Reason why "nocache" option is not displayed in "mount"? Alexander Leidinger
  • Re: Reason why "nocache" option is not displayed in "mount"? Christos Chatzaras
  • Re: Reason why "nocache" option is not displayed in "mount"? Alexander Leidinger
  • Re: Reason why "nocache" option is not displayed in "mount"? Jamie Landeg-Jones
  • Re: Reason why "nocache" option is not displayed in "mount"? Jamie Landeg-Jones
  • Re: Reason why "nocache" option is not displayed in "mount"? Warner Losh
  • Re: Reason why "nocache" option is not displayed in "mount"? Alexander Leidinger
  • Re: Reason why "nocache" option is not displayed in "mount"? Rick Macklem
  • Re: Reason why "nocache" option is not displayed in "mount"? Alexander Leidinger
  • Re: Reason why "nocache" option is not displayed in "mount"? Kirk McKusick
  • Re: Reason why "nocache" option is not displayed in "mount"? Konstantin Belousov
  • Re: Reason why "nocache" option is not displayed in "mount"? Kirk McKusick
  • Re: Reason why "nocache" option is not displayed in "mount"? Konstantin Belousov
  • Re: Reason why "nocache" option is not displayed in "mount"? Alexander Leidinger
  • Re: Reason why "nocache" option is not displayed in "mount"? Konstantin Belousov
  • Re: Reason why "nocache" option is not displayed in "mount"? Mark Millard
• Kernel build broken without "options KTRACE" John Nielsen
  • Re: Kernel build broken without "options KTRACE" Mark Johnston
• Buildworld stops for d3befb534b9 in tests bob prohaska
  • Re: Buildworld stops for d3befb534b9 in tests Mark Millard
  • Re: Buildworld stops for d3befb534b9 in tests bob prohaska
• math(s) library folks - 128-bit tgammal(3) review please? Mark Murray
• Call for 2024Q1 status reports Lorenzo Salvadore
• Unable to boot -CURRENT on Thinkpad P16s G2 Philipp Ost
  • Re: Unable to boot -CURRENT on Thinkpad P16s G2 Philipp Ost
  • Re: Unable to boot -CURRENT on Thinkpad P16s G2 Doug Ambrisko
  • Re: Unable to boot -CURRENT on Thinkpad P16s G2 Warner Losh
• after commit 5e248c2, kernel module build is broken Michael Butler
  • Re: after commit 5e248c2, kernel module build is broken Zhenlei Huang
  • Re: Fwd: Re: after commit 5e248c2, kernel module build is broken Scheffenegger, Richard
• commit f74352f breaks world Michael Butler
• Missing files on -current bob prohaska
  • Re: Missing files on -current bob prohaska
  • Re: Missing files on -current Gary Jennejohn
  • Re: Missing files on -current bob prohaska
• February 2024 stabilization week Gleb Smirnoff
  • Re: February 2024 stabilization week Konstantin Belousov
  • Re: February 2024 stabilization week Alexander Leidinger
• FreeBSD CURRENT stabilization cycle Gleb Smirnoff
  • RE: FreeBSD CURRENT stabilization cycle Mark Millard
  • Re: FreeBSD CURRENT stabilization cycle Kirill Ponomarev
  • Re: FreeBSD CURRENT stabilization cycle Franco Fichtner
• WITHOUT_CASPER ghost? Michael Dexter
  • Re: WITHOUT_CASPER ghost? Brooks Davis
  • Re: WITHOUT_CASPER ghost? Michael Dexter
  • Re: WITHOUT_CASPER ghost? Brooks Davis
• Re: sanitizers broken (was RE: libc/libsys split coming soon) [errno in libsys: any analogy to __elf_aux_vector ?] Mark Millard
  • Re: sanitizers broken (was RE: libc/libsys split coming soon) [errno in libsys: any analogy to __elf_aux_vector ?] Brooks Davis
• 42fdcd9fd917 broke my snd_uaudio(4) Lexi Winter
  • Re: 42fdcd9fd917 broke my snd_uaudio(4) Florian Walpen
  • Re: 42fdcd9fd917 broke my snd_uaudio(4) Lexi Winter
  • Re: 42fdcd9fd917 broke my snd_uaudio(4) Florian Walpen
• sanitizers broken (was RE: libc/libsys split coming soon) Hartmut.Brandt
  • Re: sanitizers broken (was RE: libc/libsys split coming soon) Mark Johnston
  • Re: sanitizers broken (was RE: libc/libsys split coming soon) Hartmut Brandt
  • Re: sanitizers broken (was RE: libc/libsys split coming soon) Brooks Davis
  • Re: sanitizers broken (was RE: libc/libsys split coming soon) Dimitry Andric
  • Re: sanitizers broken (was RE: libc/libsys split coming soon) Brooks Davis
  • Re: sanitizers broken (was RE: libc/libsys split coming soon) Konstantin Belousov
  • Re: sanitizers broken (was RE: libc/libsys split coming soon) Brooks Davis
  • Re: sanitizers broken (was RE: libc/libsys split coming soon) David Chisnall
  • Re: sanitizers broken (was RE: libc/libsys split coming soon) Alexander Leidinger
  • Re: sanitizers broken (was RE: libc/libsys split coming soon) Mark Millard
  • Re: sanitizers broken (was RE: libc/libsys split coming soon) Mark Millard
  • Re: sanitizers broken (was RE: libc/libsys split coming soon) Mark Millard
• NLNet Labs Ending Dev of drill(1) Pete Wright
  • Re: NLNet Labs Ending Dev of drill(1) Chris
• install: /usr/libexec/kgdb exists but is not a directory Bjoern A. Zeeb
  • Re: install: /usr/libexec/kgdb exists but is not a directory Dimitry Andric
  • Re: install: /usr/libexec/kgdb exists but is not a directory Dimitry Andric
• new tls-cert-store and cert-bundle methods void
  • Re: new tls-cert-store and cert-bundle methods Dag-Erling Smørgrav
  • Re: new tls-cert-store and cert-bundle methods void
• FreeBSD Status Report - Fourth Quater 2023 Lorenzo Salvadore
• files/edd962f76ea4b5869f3c6f8ee5438fb9750b802d02bb8035fe1b7bd0a8ba7401.gz not found -- snapshot corrupt. Mario Marietto
  • Re: files/edd962f76ea4b5869f3c6f8ee5438fb9750b802d02bb8035fe1b7bd0a8ba7401.gz not found -- snapshot corrupt. Warner Losh
  • Re: files/edd962f76ea4b5869f3c6f8ee5438fb9750b802d02bb8035fe1b7bd0a8ba7401.gz not found -- snapshot corrupt. Mark Millard
  • Re: files/edd962f76ea4b5869f3c6f8ee5438fb9750b802d02bb8035fe1b7bd0a8ba7401.gz not found -- snapshot corrupt. Jamie Landeg-Jones
  • Re: files/edd962f76ea4b5869f3c6f8ee5438fb9750b802d02bb8035fe1b7bd0a8ba7401.gz not found -- snapshot corrupt. Mario Marietto
  • Re: files/edd962f76ea4b5869f3c6f8ee5438fb9750b802d02bb8035fe1b7bd0a8ba7401.gz not found -- snapshot corrupt. Warner Losh
• nvme controller reset failures on recent -CURRENT Don Lewis
  • Re: nvme controller reset failures on recent -CURRENT Maxim Sobolev
  • Re: nvme controller reset failures on recent -CURRENT Don Lewis
  • Re: nvme controller reset failures on recent -CURRENT Warner Losh
  • Re: nvme controller reset failures on recent -CURRENT Don Lewis
  • Re: nvme controller reset failures on recent -CURRENT Pete Wright
  • Re: nvme controller reset failures on recent -CURRENT Craig Leres
  • Re: nvme controller reset failures on recent -CURRENT Patrick M. Hausen
  • Re: nvme controller reset failures on recent -CURRENT Mark Johnston
  • Re: nvme controller reset failures on recent -CURRENT Don Lewis
• Kernel Panic sys/netinet/tcp_subr.c 2386 Wolfram Schneider
• kernel crash in tcp_subr.c:2386 Alexander Leidinger
  • Re: kernel crash in tcp_subr.c:2386 tuexen
  • Re: kernel crash in tcp_subr.c:2386 Cy Schubert
  • Re: kernel crash in tcp_subr.c:2386 Cy Schubert
• segfault in ld-elf.so.1 Alexander Leidinger
  • Re: segfault in ld-elf.so.1 Alexander Leidinger
• How to use the L4 Microkernel with a FreeBSD userland. Mario Marietto
  • Re: How to use the L4 Microkernel with a FreeBSD userland. Mark Millard
  • Re: How to use the L4 Microkernel with a FreeBSD userland. Mario Marietto
  • Re: How to use the L4 Microkernel with a FreeBSD userland. Mark Millard
  • Re: How to use the L4 Microkernel with a FreeBSD userland. Mark Millard
  • Re: How to use the L4 Microkernel with a FreeBSD userland. Mario Marietto
• Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic Mark Millard
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic Bakul Shah
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic Mark Millard
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic Michael Butler
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic John Baldwin
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic Michael Butler
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic Michael Butler
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic Michael Butler
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic Mark Millard
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic John Baldwin
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic Mark Millard
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic Mark Millard
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic Mark Millard
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic Mark Millard
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic Mark Millard
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic John Baldwin
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic Warner Losh
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic John Baldwin
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic Warner Losh
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic Mark Millard
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic Mark Millard
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic John Baldwin
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic Mark Millard
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic [now fixed] Mark Millard
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic [now fixed] Mark Millard
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic [now fixed] John Baldwin
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic [now fixed] John Kennedy
  • Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic John Baldwin
• FreeBSD panics possibly caused by nfs clients Matthew L. Dailey
  • Re: FreeBSD panics possibly caused by nfs clients Mark Johnston
  • Re: FreeBSD panics possibly caused by nfs clients Matthew L. Dailey
  • Re: FreeBSD panics possibly caused by nfs clients Matthew L. Dailey
  • Re: FreeBSD panics possibly caused by nfs clients Mark Johnston
  • Re: FreeBSD panics possibly caused by nfs clients Zaphod Beeblebrox
  • Re: FreeBSD panics possibly caused by nfs clients Rick Macklem
  • Re: FreeBSD panics possibly caused by nfs clients Matthew L. Dailey
  • Re: FreeBSD panics possibly caused by nfs clients Mark Johnston
  • Re: FreeBSD panics possibly caused by nfs clients Matthew L. Dailey
  • Re: FreeBSD panics possibly caused by nfs clients Matthew L. Dailey
  • Re: FreeBSD panics possibly caused by nfs clients Rick Macklem
  • Re: FreeBSD panics possibly caused by nfs clients Matthew L. Dailey
  • Re: FreeBSD panics possibly caused by nfs clients Rick Macklem
  • Re: FreeBSD panics possibly caused by nfs clients Rick Macklem
  • Re: FreeBSD panics possibly caused by nfs clients Matthew L. Dailey
  • Re: FreeBSD panics possibly caused by nfs clients Rick Macklem
• unsubscribe Ryan R
  • Unsubscribe Lynn Grant
  • UNSUBSCRIBE Ventsislav Nikolov
• libc/libsys split coming soon Brooks Davis
  • Re: libc/libsys split coming soon Steffen Nurpmeso
  • Re: libc/libsys split coming soon Dave Cottlehuber
  • Re: libc/libsys split coming soon Daniel Eischen
  • Re: libc/libsys split coming soon Konstantin Belousov
  • Re: libc/libsys split coming soon Warner Losh
  • Re: libc/libsys split coming soon Konstantin Belousov
  • Re: libc/libsys split coming soon Mateusz Guzik
  • Re: libc/libsys split coming soon David Chisnall
  • Re: libc/libsys split coming soon Mateusz Guzik
  • Re: libc/libsys split coming soon Konstantin Belousov
  • Re: libc/libsys split coming soon Robert Clausecker
  • Re: libc/libsys split coming soon Brooks Davis
  • Re: libc/libsys split coming soon Paul Floyd
  • Re: libc/libsys split coming soon Brooks Davis
  • Re: libc/libsys split coming soon Paul Floyd
  • Re: libc/libsys split coming soon Paul Floyd
• sendmail 8.18.1 imported and merged Gregory Shapiro
• 'poweroff' seems to (only) halt as of main-n267841-0b3f9e435f2b David Wolfskill
  • Re: 'poweroff' seems to (only) halt as of main-n267841-0b3f9e435f2b Tomek CEDRO
  • Re: 'poweroff' seems to (only) halt as of main-n267841-0b3f9e435f2b David Wolfskill
  • Re: 'poweroff' seems to (only) halt as of main-n267841-0b3f9e435f2b Gary Jennejohn
  • Re: 'poweroff' seems to (only) halt as of main-n267841-0b3f9e435f2b David Wolfskill
  • Re: 'poweroff' seems to (only) halt as of main-n267841-0b3f9e435f2b Gary Jennejohn
  • Re: 'poweroff' seems to (only) halt as of main-n267841-0b3f9e435f2b Olivier Cochard-Labbé
  • Re: 'poweroff' seems to (only) halt as of main-n267841-0b3f9e435f2b Mike Karels
  • Re: 'poweroff' seems to (only) halt as of main-n267841-0b3f9e435f2b David Wolfskill
  • Re: 'poweroff' seems to (only) halt as of main-n267841-0b3f9e435f2b Warner Losh

• Earlier messages
• Later messages