freebsd-current  

Messages by Date

• 2025/11/22 Re: changing from pkgbase to regularbase void
• 2025/11/22 Re: changing from pkgbase to regularbase Tomoaki AOKI
• 2025/11/21 Re: changing from pkgbase to regularbase [ evidence gathering for problems when using a pkgbase system ] Mark Millard
• 2025/11/21 Re: changing from pkgbase to regularbase Lexi Winter
• 2025/11/21 Re: changing from pkgbase to regularbase void
• 2025/11/21 Re: changing from pkgbase to regularbase Lexi Winter
• 2025/11/21 Re: mmap( MAP_ANON) is broken on current. (was Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld) Michal Meloun
• 2025/11/21 Re: mmap( MAP_ANON) is broken on current. (was Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld) Konstantin Belousov
• 2025/11/21 Re: mmap( MAP_ANON) is broken on current. (was Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld) Konstantin Belousov
• 2025/11/21 Re: Still seeing Failed assertion: "p[i] == 0" [ *** i386 chroot on amd64 can get the failure on main 16 too *** ] [failed without new kernel check detection] Mark Millard
• 2025/11/21 Re: mmap( MAP_ANON) is broken on current. (was Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld) Michal Meloun
• 2025/11/21 Re: Still seeing Failed assertion: "p[i] == 0" [ *** i386 chroot on amd64 can get the failure on main 16 too *** ] [failed without new kernel check detection] Mark Millard
• 2025/11/21 Re: Still seeing Failed assertion: "p[i] == 0" [ *** i386 chroot on amd64 can get the failure on main 16 too *** ] Mark Millard
• 2025/11/21 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld bob prohaska
• 2025/11/21 Re: mmap( MAP_ANON) is broken on current. (was Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld) Konstantin Belousov
• 2025/11/21 Re: mmap( MAP_ANON) is broken on current. (was Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld) Konstantin Belousov
• 2025/11/20 mmap( MAP_ANON) is broken on current. (was Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld) Michal Meloun
• 2025/11/20 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Mark Millard
• 2025/11/20 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld bob prohaska
• 2025/11/20 Re: Still seeing Failed assertion: "p[i] == 0" [ *** i386 chroot on amd64 can get the failure on main 16 too *** ] Mark Millard
• 2025/11/20 Re: Still seeing Failed assertion: "p[i] == 0" [ *** i386 chroot on amd64 can get the failure on main 16 too *** ] Mark Millard
• 2025/11/20 Re: changing from pkgbase to regularbase void
• 2025/11/20 Re: changing from pkgbase to regularbase - small addition in step 4) void
• 2025/11/20 Re: changing from pkgbase to regularbase - small addition in step 4) vermaden
• 2025/11/20 Re: changing from pkgbase to regularbase - small addition in step 4) void
• 2025/11/20 Re: changing from pkgbase to regularbase - small addition in step 4) h v
• 2025/11/20 Re: changing from pkgbase to regularbase h v
• 2025/11/20 Re: nvme.c:2012:2: error: call to undeclared function 'memmove' Minsoo Choo
• 2025/11/20 Re: changing from pkgbase to regularbase Matthew Seaman
• 2025/11/20 Re: changing from pkgbase to regularbase Mark Millard
• 2025/11/20 Re: changing from pkgbase to regularbase void
• 2025/11/20 Re: changing from pkgbase to regularbase void
• 2025/11/20 Re: changing from pkgbase to regularbase Dag-Erling Smørgrav
• 2025/11/20 Re: changing from pkgbase to regularbase Mark Millard
• 2025/11/19 Re: nvme.c:2012:2: error: call to undeclared function 'memmove' Minsoo Choo
• 2025/11/19 Re: nvme.c:2012:2: error: call to undeclared function 'memmove' cyric
• 2025/11/19 Re: nvme.c:2012:2: error: call to undeclared function 'memmove' Ian Freislich
• 2025/11/19 Re: nvme.c:2012:2: error: call to undeclared function 'memmove' Minsoo Choo
• 2025/11/19 Re: nvme.c:2012:2: error: call to undeclared function 'memmove' Ian FREISLICH
• 2025/11/19 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #5] [Common range #0..#10 __je_pa_alloc] Mark Millard
• 2025/11/19 Re: nvme.c:2012:2: error: call to undeclared function 'memmove' Minsoo Choo
• 2025/11/19 Re: nvme.c:2012:2: error: call to undeclared function 'memmove' Ian FREISLICH
• 2025/11/19 Re: nvme.c:2012:2: error: call to undeclared function 'memmove' Minsoo Choo
• 2025/11/19 Re: changing from pkgbase to regularbase Dag-Erling Smørgrav
• 2025/11/19 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #5] [Common range #0..#10 __je_pa_alloc] Mark Millard
• 2025/11/19 Re: changing from pkgbase to regularbase Sulev-Madis Silber
• 2025/11/19 Re: changing from pkgbase to regularbase Ronald Klop
• 2025/11/19 Re: changing from pkgbase to regularbase Freddie Cash
• 2025/11/19 Re: changing from pkgbase to regularbase Michael Gmelin
• 2025/11/19 Re: changing from pkgbase to regularbase void
• 2025/11/19 Re: changing from pkgbase to regularbase void
• 2025/11/19 Re: changing from pkgbase to regularbase Minsoo Choo
• 2025/11/19 Re: changing from pkgbase to regularbase void
• 2025/11/19 Re: changing from pkgbase to regularbase Minsoo Choo
• 2025/11/18 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #5] [Common range #0..#10 __je_pa_alloc] Mark Millard
• 2025/11/18 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #4] [New common range #0..#10 __je_pa_alloc] Mark Millard
• 2025/11/18 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #3] Mark Millard
• 2025/11/18 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #2] Mark Millard
• 2025/11/18 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #1] Mark Millard
• 2025/11/18 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #1] Mark Millard
• 2025/11/18 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #1] Mark Millard
• 2025/11/18 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [gdb backtrace! End of area has 0x5a5a5a5a sequence] Mark Millard
• 2025/11/18 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [gdb backtrace! End of area has 0x5a5a5a5a sequence] Mark Millard
• 2025/11/18 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [gdb backtrace!] Mark Millard
• 2025/11/18 Re: FYI: getopt in /usr/src/contrib/diff/lib/getopt.h vs. /usr/obj/usr/src/arm64.aarch64/tmp/usr/include/unistd.h : reported as incompatible with future C23 use Ed Maste
• 2025/11/18 Re: 15.0-ish urgent: Please test iichid/keyboard patch on laptops Poul-Henning Kamp
• 2025/11/18 Re: 15.0-ish urgent: Please test iichid/keyboard patch on laptops Alan Somers
• 2025/11/18 Re: FYI: getopt in /usr/src/contrib/diff/lib/getopt.h vs. /usr/obj/usr/src/arm64.aarch64/tmp/usr/include/unistd.h : reported as incompatible with future C23 use Ed Maste
• 2025/11/17 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Mark Millard
• 2025/11/17 Fwd: git: 396b32e801d6 - main - stand: Add back missing EFIAPI define Warner Losh
• 2025/11/17 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Adrian Chadd
• 2025/11/17 FreeBSD Git Weekly 2025-11-10 to 2025-11-16 Graham Percival
• 2025/11/17 Re: 15.0's and main's [so: 16's] jemalloc man page reports "This manual describes jemalloc 5.2.1-0-gea6b3. . ." but 5.3.0-0-g54eae is in use instead for 15.0+ and main 16. Minsoo Choo
• 2025/11/17 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld bob prohaska
• 2025/11/17 Re: WITHOUT_CLEAN confusion in -current void
• 2025/11/17 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Mark Millard
• 2025/11/17 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Mark Millard
• 2025/11/16 Re: WITHOUT_CLEAN confusion in -current Warner Losh
• 2025/11/16 Re: WITHOUT_CLEAN confusion in -current Herbert J. Skuhra
• 2025/11/16 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Mark Millard
• 2025/11/16 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Konstantin Belousov
• 2025/11/16 15.0's and main's [so: 16's] jemalloc man page reports "This manual describes jemalloc 5.2.1-0-gea6b3. . ." but 5.3.0-0-g54eae is in use instead for 15.0+ and main 16. Mark Millard
• 2025/11/16 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Michal Meloun
• 2025/11/16 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Warner Losh
• 2025/11/16 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld bob prohaska
• 2025/11/16 Re: "etcupdate extract" -- Failed to build new tree. Thomas Schweikle
• 2025/11/15 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Warner Losh
• 2025/11/15 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld bob prohaska
• 2025/11/15 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Herbert J. Skuhra
• 2025/11/14 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Carl Shapiro
• 2025/11/14 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Mark Millard
• 2025/11/14 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld bob prohaska
• 2025/11/14 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Mark Millard
• 2025/11/14 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld bob prohaska
• 2025/11/14 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld bob prohaska
• 2025/11/14 Re: openjdk11 compile fail on armv7 - (Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld) Mark Millard
• 2025/11/14 openjdk11 compile fail on armv7 - (Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld) Ronald Klop
• 2025/11/13 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Herbert J. Skuhra
• 2025/11/13 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Carl Shapiro
• 2025/11/13 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld bob prohaska
• 2025/11/13 Re: keyboard in wrong mode after VT switch from X Bjoern A. Zeeb
• 2025/11/13 native armv7 for struct aiocb offsets and overall size vs. aarch64 for struct aiocb32 offsets and overall size: most fields do not match Mark Millard
• 2025/11/13 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Mark Millard
• 2025/11/13 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld bob prohaska
• 2025/11/13 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Michal Meloun
• 2025/11/13 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Ronald Klop
• 2025/11/13 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Carl Shapiro
• 2025/11/13 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Warner Losh
• 2025/11/13 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Ronald Klop
• 2025/11/12 Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld bob prohaska
• 2025/11/12 Re: keyboard in wrong mode after VT switch from X Andriy Gapon
• 2025/11/12 Re: keyboard in wrong mode after VT switch from X Ed Maste
• 2025/11/12 keyboard in wrong mode after VT switch from X Andriy Gapon
• 2025/11/11 Re: Backout git revision 4179e6b78297369f [that is also stable/15 and releng/15.0 as 62c3b77d1d10] Bjoern A. Zeeb
• 2025/11/11 Re: RFC: Should copy_file_range(2) return after a few seconds? Rick Macklem
• 2025/11/11 main [so: 16] armv7 chroot and lib32 use: example fio command works on real armv7 system boots but fails on aarch64 chroot or lib32 use Mark Millard
• 2025/11/11 Re: Backout git revision 4179e6b78297369f [that is also stable/15 and releng/15.0 as 62c3b77d1d10] Steve Kargl
• 2025/11/11 Re: Backout git revision 4179e6b78297369f [that is also stable/15 and releng/15.0 as 62c3b77d1d10] Ed Maste
• 2025/11/11 Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount bob prohaska
• 2025/11/11 Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount Mark Millard
• 2025/11/11 Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount Mark Millard
• 2025/11/11 Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount Dag-Erling Smørgrav
• 2025/11/11 Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount bob prohaska
• 2025/11/11 Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount bob prohaska
• 2025/11/11 Re: RFC: Should copy_file_range(2) return after a few seconds? Konstantin Belousov
• 2025/11/11 Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount Dag-Erling Smørgrav
• 2025/11/11 Re: RFC: Should copy_file_range(2) return after a few seconds? Peter 'PMc' Much
• 2025/11/11 Re: RFC: Should copy_file_range(2) return after a few seconds? Mark Johnston
• 2025/11/11 Re: RFC: Should copy_file_range(2) return after a few seconds? Konstantin Belousov
• 2025/11/11 Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount Ronald Klop
• 2025/11/11 Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount void
• 2025/11/10 Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount bob prohaska
• 2025/11/10 Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount Mark Millard
• 2025/11/10 Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount void
• 2025/11/10 FreeBSD Git Weekly 2025-11-03 to 2025-11-09 Graham Percival
• 2025/11/10 HEADS UP (16.0 pkgbase): new package for PAM Lexi Winter
• 2025/11/10 Re: RFC: Should copy_file_range(2) return after a few seconds? Rick Macklem
• 2025/11/10 Re: RFC: Should copy_file_range(2) return after a few seconds? Rick Macklem
• 2025/11/10 Re: RFC: Should copy_file_range(2) return after a few seconds? Rick Macklem
• 2025/11/10 Re: RFC: Should copy_file_range(2) return after a few seconds? Bakul Shah
• 2025/11/10 Re: RFC: Should copy_file_range(2) return after a few seconds? Don Lewis
• 2025/11/09 Re: Backout git revision 4179e6b78297369f [ finding drm-* pkg fallout logs ] Mark Millard
• 2025/11/09 Re: Backout git revision 4179e6b78297369f [that is also stable/15 and releng/15.0 as 62c3b77d1d10] Tomoaki AOKI
• 2025/11/09 Re: Backout git revision 4179e6b78297369f [that is also stable/15 and releng/15.0 as 62c3b77d1d10] Bjoern A. Zeeb
• 2025/11/09 Re: Backout git revision 4179e6b78297369f [that is also stable/15 and releng/15.0 as 62c3b77d1d10] Steve Kargl
• 2025/11/09 Re: Backout git revision 4179e6b78297369f [that is also stable/15 and releng/15.0 as 62c3b77d1d10] Bjoern A. Zeeb
• 2025/11/09 Re: RFC: Should copy_file_range(2) return after a few seconds? Rick Macklem
• 2025/11/08 Re: RFC: Should copy_file_range(2) return after a few seconds? Ronald Klop
• 2025/11/08 Re: Backout git revision 4179e6b78297369f [that is also stable/15 and releng/15.0 as 62c3b77d1d10] Steve Kargl
• 2025/11/08 RE: Backout git revision 4179e6b78297369f [that is also stable/15 and releng/15.0 as 62c3b77d1d10] Mark Millard
• 2025/11/08 Re: RFC: Should copy_file_range(2) return after a few seconds? Rick Macklem
• 2025/11/08 Re: RFC: Should copy_file_range(2) return after a few seconds? Konstantin Belousov
• 2025/11/08 Re: RFC: Should copy_file_range(2) return after a few seconds? Rick Macklem
• 2025/11/08 Re: "etcupdate extract" -- Failed to build new tree. Sulev-Madis Silber
• 2025/11/08 Re: RFC: Should copy_file_range(2) return after a few seconds? Konstantin Belousov
• 2025/11/08 Re: "etcupdate extract" -- Failed to build new tree. Thomas Schweikle
• 2025/11/08 Re: "etcupdate extract" -- Failed to build new tree. Sulev-Madis Silber
• 2025/11/08 Re: "etcupdate extract" -- Failed to build new tree. Michael Gmelin
• 2025/11/08 Re: "etcupdate extract" -- Failed to build new tree. Thomas Schweikle
• 2025/11/08 FYI: getopt in /usr/src/contrib/diff/lib/getopt.h vs. /usr/obj/usr/src/arm64.aarch64/tmp/usr/include/unistd.h : reported as incompatible with future C23 use Mark Millard
• 2025/11/07 Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld Sulev-Madis Silber
• 2025/11/07 Re: mongodb - Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld Mark Millard
• 2025/11/07 Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld Ronald Klop
• 2025/11/07 Re: mongodb - Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld John Kennedy
• 2025/11/07 Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld Mark Millard
• 2025/11/07 Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld bob prohaska
• 2025/11/07 Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld Mark Millard
• 2025/11/07 Re: mongodb - Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld Paul Mather
• 2025/11/07 Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld bob prohaska
• 2025/11/07 mongodb - Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld Ronald Klop
• 2025/11/07 Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld Paul Mather
• 2025/11/06 Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld Mark Millard
• 2025/11/06 Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld bob prohaska
• 2025/11/06 Re: Mistakenly started two buildworld instances... Enji Cooper (yaneurabeya)
• 2025/11/06 Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld Mark Millard
• 2025/11/06 Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld bob prohaska
• 2025/11/06 Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld Ronald Klop
• 2025/11/06 Re: Why is the DVD image so large? Tomek CEDRO
• 2025/11/05 RE: make buildworld: "[...] fatal error: 'llvm/Demangle/Demangle.h' file not found", among other errors Mark Millard
• 2025/11/05 Re: make buildworld: "[...] fatal error: 'llvm/Demangle/Demangle.h' file not found", among other errors David Wolfskill
• 2025/11/05 Re: [LDWG] additional requirements to be able to install KDE DESKTOP on FBSD15 from install media. S. Ross Gohlke
• 2025/11/05 Re: RFC: NFS over RDMA Rick Macklem
• 2025/11/05 Re: RFC: NFS over RDMA Rick Macklem
• 2025/11/04 Re: [LDWG] additional requirements to be able to install KDE DESKTOP on FBSD15 from install media. Graham Perrin
• 2025/11/04 [LDWG] additional requiremetns to be able to install KDE DESKTOP on FBSD15 from install media. Lars Tunkrans
• 2025/11/04 Re: db> reset -> panic: lock (sleep mutex) eventhandler not locked @ /usr/src/sys/kern/subr_eventhandler.c:272 Mitchell Horne
• 2025/11/04 Re: "etcupdate extract" -- Failed to build new tree. Sulev-Madis Silber
• 2025/11/04 Re: "etcupdate extract" -- Failed to build new tree. Marek Zarychta
• 2025/11/04 Re: "etcupdate extract" -- Failed to build new tree. Dag-Erling Smørgrav
• 2025/11/03 Re: RFC: NFS over RDMA Rick Macklem
• 2025/11/03 Re: "etcupdate extract" -- Failed to build new tree. Miroslav Lachman
• 2025/11/03 Re: "etcupdate extract" -- Failed to build new tree. Thomas Schweikle
• 2025/11/03 Re: Why is the DVD image so large? Tomek CEDRO
• 2025/11/03 Re: Why is the DVD image so large? Andriy Gapon
• 2025/11/03 Re: RFC: NFS over RDMA Konstantin Belousov
• 2025/11/03 Re: Why is the DVD image so large? Lars Tunkrans
• 2025/11/03 Re: Why is the DVD image so large? Sulev-Madis Silber
• 2025/11/03 Re: Why is the DVD image so large? Tomoaki AOKI
• 2025/11/03 Re: Why is the DVD image so large? Tomek CEDRO
• 2025/11/03 Re: Why is the DVD image so large? Sulev-Madis Silber

• Earlier messages
• Later messages