2025/freebsd-current/20251117.freebsd-current
Messages: 62, sorted by subject
|
Last page update: Sat Jan 3 13:09:41 UTC 2026
|
|
home | up | archive | sorted by: subject - author - date - reverse date
1. Nov 16 Thomas Schweikle Re: "etcupdate extract" -- Failed to build new tree. 2. Nov 16 Mark Millard 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 inste 3. Nov 10 Mark Millard Re: Backout git revision 4179e6b78297369f [ finding drm-* pkg fallout logs ] 4. Nov 11 Ed Maste Re: Backout git revision 4179e6b78297369f [that is also stable/15 and releng/15.0 as 62c3b77d1d10] 5. Nov 11 Steve Kargl Re: Backout git revision 4179e6b78297369f [that is also stable/15 and releng/15.0 as 62c3b77d1d10] 6. Nov 11 Bjoern A. Zeeb Re: Backout git revision 4179e6b78297369f [that is also stable/15 and releng/15.0 as 62c3b77d1d10] 7. Nov 10 Graham Percival FreeBSD Git Weekly 2025-11-03 to 2025-11-09 8. Nov 10 Lexi Winter HEADS UP (16.0 pkgbase): new package for PAM 9. Nov 10 void kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount 10. Nov 10 void Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount 11. Nov 11 Mark Millard Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount 12. Nov 11 bob prohaska Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount 13. Nov 11 void Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount 14. Nov 11 Ronald Klop Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount 15. Nov 11 Dag-Erling Smørgrav Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount 16. Nov 11 bob prohaska Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount 17. Nov 11 bob prohaska Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount 18. Nov 11 Dag-Erling Smørgrav Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount 19. Nov 11 Mark Millard Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount 20. Nov 11 Mark Millard Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount
21. Nov 11 bob prohaska Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount 22. Nov 12 Andriy Gapon keyboard in wrong mode after VT switch from X 23. Nov 12 Ed Maste Re: keyboard in wrong mode after VT switch from X 24. Nov 12 Andriy Gapon Re: keyboard in wrong mode after VT switch from X 25. Nov 13 Bjoern A. Zeeb Re: keyboard in wrong mode after VT switch from X 26. Nov 11 Mark Millard 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 27. Nov 13 Mark Millard native armv7 for struct aiocb offsets and overall size vs. aarch64 for struct aiocb32 offsets and overall size: most fields do not match 28. Nov 14 Ronald Klop openjdk11 compile fail on armv7 - (Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld) 29. Nov 14 Mark Millard Re: openjdk11 compile fail on armv7 - (Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld) 30. Nov 10 Don Lewis Re: RFC: Should copy_file_range(2) return after a few seconds? 31. Nov 10 Bakul Shah Re: RFC: Should copy_file_range(2) return after a few seconds? 32. Nov 10 Rick Macklem Re: RFC: Should copy_file_range(2) return after a few seconds? 33. Nov 10 Rick Macklem Re: RFC: Should copy_file_range(2) return after a few seconds? 34. Nov 10 Rick Macklem Re: RFC: Should copy_file_range(2) return after a few seconds? 35. Nov 11 Konstantin Belousov Re: RFC: Should copy_file_range(2) return after a few seconds? 36. Nov 11 Mark Johnston Re: RFC: Should copy_file_range(2) return after a few seconds? 37. Nov 11 Peter 'PMc' Much Re: RFC: Should copy_file_range(2) return after a few seconds? 38. Nov 11 Konstantin Belousov Re: RFC: Should copy_file_range(2) return after a few seconds? 39. Nov 11 Rick Macklem Re: RFC: Should copy_file_range(2) return after a few seconds? 40. Nov 12 bob prohaska Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld
41. Nov 13 Ronald Klop Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 42. Nov 13 Warner Losh Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 43. Nov 13 Carl Shapiro Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 44. Nov 13 Ronald Klop Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 45. Nov 13 Michal Meloun Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 46. Nov 13 bob prohaska Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 47. Nov 13 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 48. Nov 14 bob prohaska Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 49. Nov 14 Carl Shapiro Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 50. Nov 14 Herbert J. Skuhra Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 51. Nov 14 bob prohaska Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 52. Nov 14 bob prohaska Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 53. Nov 14 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 54. Nov 14 bob prohaska Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 55. Nov 14 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 56. Nov 14 Carl Shapiro Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 57. Nov 15 Herbert J. Skuhra Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 58. Nov 15 bob prohaska Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 59. Nov 15 Warner Losh Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 60. Nov 16 bob prohaska Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld
61. Nov 16 Warner Losh Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 62. Nov 16 Michal Meloun Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld
home | up | archive | sorted by: subject - author - date - reverse date