freebsd-current  

Messages by Thread

• Re: kldload: an error occurred while loading module linux. FreeBSD User
• MIT KRB5 in 15-CURRENT Cy Schubert
  • Re: MIT KRB5 in 15-CURRENT Minsoo Choo
  • Re: MIT KRB5 in 15-CURRENT Cy Schubert
• [2 WEEKS LEFT REMINDER] Call for 2025Q2 status reports Lorenzo Salvadore
• Re: if_bridge(): IPv6 EUI-64 seemingly not working Lexi Winter
  • Re: if_bridge(): IPv6 EUI-64 seemingly not working FreeBSD User
  • Re: if_bridge(): IPv6 EUI-64 seemingly not working Lexi Winter
  • Re: if_bridge(): IPv6 EUI-64 seemingly not working A FreeBSD User
  • Re: if_bridge(): IPv6 EUI-64 seemingly not working FreeBSD User
• Re: Bisecting issue in head Brooks Davis
  • Re: Bisecting issue in head Kevin Oberman
• Future of jemalloc on FreeBSD after archive Minsoo Choo
  • Re: Future of jemalloc on FreeBSD after archive Warner Losh
  • Re: Future of jemalloc on FreeBSD after archive David Chisnall
  • Re: Future of jemalloc on FreeBSD after archive Poul-Henning Kamp
  • Re: Future of jemalloc on FreeBSD after archive Brooks Davis
  • Re: Future of jemalloc on FreeBSD after archive Warner Losh
  • Re: Future of jemalloc on FreeBSD after archive Brooks Davis
  • Re: Future of jemalloc on FreeBSD after archive Minsoo Choo
  • Re: Future of jemalloc on FreeBSD after archive David Chisnall
  • Re: Future of jemalloc on FreeBSD after archive Gleb Popov
  • Re: Future of jemalloc on FreeBSD after archive Bakul Shah
  • Re: Future of jemalloc on FreeBSD after archive Brooks Davis
  • Re: Future of jemalloc on FreeBSD after archive Bakul Shah
  • Re: Future of jemalloc on FreeBSD after archive Amar Takhar
  • Re: Future of jemalloc on FreeBSD after archive Adrian Chadd
  • Re: Future of jemalloc on FreeBSD after archive Paul Floyd
  • Re: Future of jemalloc on FreeBSD after archive Bakul Shah
  • Re: Future of jemalloc on FreeBSD after archive Enji Cooper (yaneurabeya)
• Re: Adding kqueue to /dev/dsp Vladimir Kondratyev
  • Re: Adding kqueue to /dev/dsp Goran Mekić
• 2022's "stand: Document EFI consoles" update predates the 2023 "eficom" (vs. older "comconsole") update: going to be documented? Mark Millard
  • Re: 2022's "stand: Document EFI consoles" update predates the 2023 "eficom" (vs. older "comconsole") update: going to be documented? Warner Losh
• Re: base packages orphaned Tomoaki AOKI
  • Re: base packages orphaned grahamperrin
  • Re: base packages orphaned Graham Perrin
• HEADS UP: wireless KPI and KBI and FreeBSD 15 Bjoern A. Zeeb
  • Re: HEADS UP: wireless KPI and KBI and FreeBSD 15 Warner Losh
  • Re: HEADS UP: wireless KPI and KBI and FreeBSD 15 Jan Bramkamp
  • Re: HEADS UP: wireless KPI and KBI and FreeBSD 15 Warner Losh
  • Re: HEADS UP: wireless KPI and KBI and FreeBSD 15 Jan Bramkamp
  • Re: HEADS UP: wireless KPI and KBI and FreeBSD 15 Adrian Chadd
  • Re: HEADS UP: wireless KPI and KBI and FreeBSD 15 Tomoaki AOKI
  • Re: HEADS UP: wireless KPI and KBI and FreeBSD 15 Andrea Venturoli
  • Re: HEADS UP: wireless KPI and KBI and FreeBSD 15 David Chisnall
  • Re: HEADS UP: wireless KPI and KBI and FreeBSD 15 Warner Losh
  • Re: HEADS UP: wireless KPI and KBI and FreeBSD 15 David Chisnall
  • Re: HEADS UP: wireless KPI and KBI and FreeBSD 15 Warner Losh
  • Re: HEADS UP: wireless KPI and KBI and FreeBSD 15 Brooks Davis
  • Re: HEADS UP: wireless KPI and KBI and FreeBSD 15 Adrian Chadd
  • Re: HEADS UP: wireless KPI and KBI and FreeBSD 15 Tomek CEDRO
  • Re: HEADS UP: wireless KPI and KBI and FreeBSD 15 Marek Zarychta
  • Re: HEADS UP: wireless KPI and KBI and FreeBSD 15 Mark Millard
• MIT KRB5 Commits Cy Schubert
• Re: i915kms for Meteor Lake: realistic timeline sought for support Chris
• Re: "duplicate script" warning during installworld? Dag-Erling Smørgrav
• Re: Failed make installworld on a recent -CURRENT Herbert J. Skuhra
  • Re: Failed make installworld on a recent -CURRENT Gordon Bergling
• Call for 2025Q2 status reports Lorenzo Salvadore
• Re: Building lang/go* and go ports broken on main (amd64)? Herbert J. Skuhra
  • Re: Building lang/go* and go ports broken on main (amd64)? Konstantin Belousov
  • Re: Building lang/go* and go ports broken on main (amd64)? Herbert J. Skuhra
  • Re: Building lang/go* and go ports broken on main (amd64)? Konstantin Belousov
  • Re: Building lang/go* and go ports broken on main (amd64)? Herbert J. Skuhra
  • Re: Building lang/go* and go ports broken on main (amd64)? Cy Schubert
  • Re: Building lang/go* and go ports broken on main (amd64)? Konstantin Belousov
  • Re: Building lang/go* and go ports broken on main (amd64)? Cy Schubert
  • Re: Building lang/go* and go ports broken on main (amd64)? Shawn Webb
  • Re: Building lang/go* and go ports broken on main (amd64)? Shawn Webb
  • Re: Building lang/go* and go ports broken on main (amd64)? Chris
  • Re: Building lang/go* and go ports broken on main (amd64)? Cy Schubert
  • Re: Building lang/go* and go ports broken on main (amd64)? Konstantin Belousov
  • Re: Building lang/go* and go ports broken on main (amd64)? Cy Schubert
• Re: drm panic after new world Steve Kargl
  • Re: drm panic after new world Steve Kargl
  • Re: drm panic after new world Steve Kargl
  • Re: drm panic after new world David Wolfskill
  • Re: drm panic after new world Steve Kargl
  • Re: drm panic after new world Warner Losh
  • Re: drm panic after new world Jamie Landeg-Jones
  • Re: drm panic after new world Matthew Seaman
  • Re: drm panic after new world Steve Kargl
  • Re: drm panic after new world Steve Kargl
  • Re: drm panic after new world Steve Kargl
  • Re: drm panic after new world Steve Kargl
  • Re: drm panic after new world Steve Kargl
  • Re: drm panic after new world Bjoern A. Zeeb
  • Re: drm panic after new world Steve Kargl
  • Re: drm panic after new world Steve Kargl
  • Re: drm panic after new world Bjoern A. Zeeb
  • Re: drm panic after new world Steve Kargl
  • Re: drm panic after new world Bjoern A. Zeeb
  • Re: drm panic after new world Steve Kargl
  • Re: drm panic after new world Bjoern A. Zeeb
  • Re: drm panic after new world Mark Millard
  • Re: drm panic after new world Steve Kargl
• Is any code using LinuxKPI USB? Bjoern A. Zeeb
• HEADS UP: 15.0 pkgbase, manual action required on upgrade Lexi Winter
  • Re: HEADS UP: 15.0 pkgbase, manual action required on upgrade Ronald Klop
  • Re: HEADS UP: 15.0 pkgbase, manual action required on upgrade Lexi Winter
  • Re: HEADS UP: 15.0 pkgbase, manual action required on upgrade Baptiste Daroussin
  • Re: HEADS UP: 15.0 pkgbase, manual action required on upgrade Pete Wright
• Re: Implementing RADSEC Bjoern A. Zeeb
• Re: With poudriere how does one create a jail of a slightly older RELEASE ? [github related notes] Mark Millard
  • Re: With poudriere how does one create a jail of a slightly older RELEASE ? [github related notes] Chris
  • Re: With poudriere how does one create a jail of a slightly older RELEASE ? [github related notes] Alastair Hogge
• Re: mountd(8) Hangs Rick Macklem
• Re: (arm64) link_elf: symbol __floatundidf undefined ... Dimitry Andric
  • Re: (arm64) link_elf: symbol __floatundidf undefined ... Bjoern A. Zeeb
  • Re: (arm64) link_elf: symbol __floatundidf undefined ... Dimitry Andric
  • Re: (arm64) link_elf: symbol __floatundidf undefined ... Dimitry Andric
• May 2025 stabilization week Gleb Smirnoff
  • tag changed! Re: May 2025 stabilization week Gleb Smirnoff
  • Re: tag changed! Re: May 2025 stabilization week Gleb Smirnoff
• New command ts(1) Juraj Lutter
  • Re: New command ts(1) Warner Losh
• Re: With poudriere how does one create a jail of a slightly older RELEASE ? Michael Gmelin
  • Re: With poudriere how does one create a jail of a slightly older RELEASE ? Dennis Clarke
  • Re: With poudriere how does one create a jail of a slightly older RELEASE ? Michael Gmelin
  • Re: With poudriere how does one create a jail of a slightly older RELEASE ? Mark Millard
  • Re: With poudriere how does one create a jail of a slightly older RELEASE ? Dan Mahoney (Ports)
  • Re: With poudriere how does one create a jail of a slightly older RELEASE ? Dennis Clarke
  • Re: With poudriere how does one create a jail of a slightly older RELEASE ? Michael Gmelin
  • Re: With poudriere how does one create a jail of a slightly older RELEASE ? Dennis Clarke
  • Re: With poudriere how does one create a jail of a slightly older RELEASE ? Warner Losh
  • Re: With poudriere how does one create a jail of a slightly older RELEASE ? Tomoaki AOKI
  • Re: With poudriere how does one create a jail of a slightly older RELEASE ? Alastair Hogge
  • Re: With poudriere how does one create a jail of a slightly older RELEASE ? Rick Macklem
  • Re: With poudriere how does one create a jail of a slightly older RELEASE ? Michael Gmelin
  • Re: With poudriere how does one create a jail of a slightly older RELEASE ? Mark Millard
  • Re: With poudriere how does one create a jail of a slightly older RELEASE ? Dennis Clarke
• Re: NFS Panic Rick Macklem
  • Re: NFS Panic Cy Schubert
• RE: Is there a way to tell poudriere to allocate more memory to a pkg build? Mark Millard
  • Re: Is there a way to tell poudriere to allocate more memory to a pkg build? Dennis Clarke
  • Re: Is there a way to tell poudriere to allocate more memory to a pkg build? Mark Millard
  • Re: Is there a way to tell poudriere to allocate more memory to a pkg build? void
  • Re: Is there a way to tell poudriere to allocate more memory to a pkg build? void
• RE: FreeBSD Status Report - First Quarter 2025 [GCC part of the report] Mark Millard
• FreeBSD Status Report - First Quarter 2025 Lorenzo Salvadore
• Re: Updating build and jail manual pages to include missing or obscure information Dave Cottlehuber
  • Re: Updating build and jail manual pages to include missing or obscure information Alexander Ziaee
  • Re: Updating build and jail manual pages to include missing or obscure information Warner Losh
  • Re: Updating build and jail manual pages to include missing or obscure information Lexi Winter
  • Re: Updating build and jail manual pages to include missing or obscure information resin-freebsd
  • Re: Updating build and jail manual pages to include missing or obscure information Lexi Winter
  • Re: Updating build and jail manual pages to include missing or obscure information Chris
  • Re: Updating build and jail manual pages to include missing or obscure information Chris
  • Re: Updating build and jail manual pages to include missing or obscure information void
  • Re: Updating build and jail manual pages to include missing or obscure information David Wolfskill
• Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument” void
  • Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument” Kristof Provost
  • Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument” Sulev-Madis Silber
  • Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument” void
  • Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument” Andriy Gapon
  • Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument” Lexi Winter
  • Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument” void
• Re: lid state stop changing after suspend/resume Renato Botelho
• RE: Just a question about sys/kern/subr_witness.c where witness_watch may be flipped to -1 Mark Millard
  • Re: Just a question about sys/kern/subr_witness.c where witness_watch may be flipped to -1 Dennis Clarke
  • Re: Just a question about sys/kern/subr_witness.c where witness_watch may be flipped to -1 Mark Millard
• Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument Marek Zarychta
  • Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument A FreeBSD User
  • Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument Alexander Leidinger
  • Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument Marek Zarychta
  • Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument Kristof Provost
  • Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument Marek Zarychta
  • Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument Lexi Winter
  • Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument Patrick M. Hausen
  • Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument A FreeBSD User
  • Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument Patrick M. Hausen
  • Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument Patrick M. Hausen
  • Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument A FreeBSD User
  • Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument A FreeBSD User
  • Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument Lexi Winter
  • Un-sucking EINVAL (was: ip# on bridge members) Poul-Henning Kamp
  • Re: Un-sucking EINVAL (was: ip# on bridge members) Lexi Winter
  • Re: Un-sucking EINVAL Warner Losh
  • Re: Un-sucking EINVAL Adrian Chadd
  • Re: Un-sucking EINVAL Poul-Henning Kamp
  • Re: Un-sucking EINVAL Brooks Davis
  • Re: Un-sucking EINVAL Konstantin Belousov
  • Re: Un-sucking EINVAL Brooks Davis
  • Re: Un-sucking EINVAL Konstantin Belousov
  • Re: Un-sucking EINVAL Chris
  • Re: Un-sucking EINVAL (was: ip# on bridge members) Brooks Davis
  • Re: Un-sucking EINVAL (was: ip# on bridge members) Poul-Henning Kamp
  • Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument A FreeBSD User
• Re: New packages repositories for kernel modules (without typo) Rodrigo Osorio
  • Re: New packages repositories for kernel modules (without typo) Marek Zarychta
  • Re: New packages repositories for kernel modules (without typo) Zhenlei Huang
  • Re: New packages repositories for kernel modules (without typo) Dave Cottlehuber
• Re: epair(4) Cy Schubert
  • Re: epair(4) Kristof Provost
  • Re: epair(4) Cy Schubert
  • Re: epair(4) Kristof Provost
  • Re: epair(4) Marek Zarychta
  • Re: epair(4) Lexi Winter
  • Re: epair(4) Michael Butler

• Earlier messages