2021/freebsd-current/20210912.freebsd-current
Messages: 103, sorted by subject
|
Last page update: Sat Jan 3 13:09:23 UTC 2026
|
|
home | up | archive | sorted by: subject - author - date - reverse date
1. Sep 6 Jeremie Le Hen -CURRENT compilation time 2. Sep 6 Michael Schuster Re: -CURRENT compilation time 3. Sep 6 Guido Falsi via freebsd-cu Re: -CURRENT compilation time 4. Sep 6 David Chisnall Re: -CURRENT compilation time 5. Sep 6 Jeffrey Bouquet Re: -CURRENT compilation time 6. Sep 6 Wolfram Schneider Re: -CURRENT compilation time 7. Sep 6 Wolfram Schneider Re: -CURRENT compilation time 8. Sep 7 Ronald Klop Re: -CURRENT compilation time 9. Sep 7 David Chisnall Re: -CURRENT compilation time 10. Sep 7 Dave Cottlehuber Re: -CURRENT compilation time 11. Sep 7 Stefan Esser Re: -CURRENT compilation time 12. Sep 7 Mark Millard via freebsd-c Re: -CURRENT compilation time 13. Sep 8 David Chisnall Re: -CURRENT compilation time 14. Sep 8 Gary Jennejohn Re: -CURRENT compilation time 15. Sep 8 David Chisnall Re: -CURRENT compilation time 16. Sep 8 Warner Losh Re: -CURRENT compilation time 17. Sep 8 Stefan Esser Re: -CURRENT compilation time 18. Sep 8 Warner Losh Re: -CURRENT compilation time 19. Sep 8 Warner Losh Re: -CURRENT compilation time 20. Sep 8 Tomoaki AOKI Re: -CURRENT compilation time
21. Sep 8 Warner Losh Re: -CURRENT compilation time 22. Sep 9 David Chisnall Re: -CURRENT compilation time 23. Sep 9 FreeBSD User Re: ar: warning: can't open file: ccopy.pieo: No such file or directory 24. Sep 6 Steve Kargl BUG in libm's powf 25. Sep 6 Mark Murray Re: BUG in libm's powf 26. Sep 6 Steve Kargl Re: BUG in libm's powf 27. Sep 6 Mark Murray Re: BUG in libm's powf 28. Sep 6 Steve Kargl Re: BUG in libm's powf 29. Sep 6 Steve Kargl Re: BUG in libm's powf 30. Sep 6 Kurt Jaeger Re: BUG in libm's powf 31. Sep 6 Steve Kargl Re: BUG in libm's powf 32. Sep 7 Kurt Jaeger Re: BUG in libm's powf 33. Sep 7 Mark Murray Re: BUG in libm's powf 34. Sep 9 Banta, Dan Re: Call for participation 35. Sep 10 Gary Jennejohn compile failure in /usr/src/stand/libsa 36. Sep 10 Toomas Soome via current Re: compile failure in /usr/src/stand/libsa 37. Sep 6 Karel Gardas EFI/loader show garbage in console when set to some resolution in loader.conf 38. Sep 6 Toomas Soome via freebsd-c Re: EFI/loader show garbage in console when set to some resolution in loader.conf 39. Sep 6 Karel Gardas Re: EFI/loader show garbage in console when set to some resolution in loader.conf 40. Sep 9 Gary Jennejohn error installing stand/i386/loader_4th in HEAD
41. Sep 9 Warner Losh Re: error installing stand/i386/loader_4th in HEAD 42. Sep 9 Gary Jennejohn Re: error installing stand/i386/loader_4th in HEAD 43. Sep 9 Warner Losh Re: error installing stand/i386/loader_4th in HEAD 44. Sep 10 Gary Jennejohn Re: error installing stand/i386/loader_4th in HEAD 45. Sep 9 Stefan Esser fetch -v error output broken? 46. Sep 9 Baptiste Daroussin Re: fetch -v error output broken? 47. Sep 9 Bruce Cantrall FreeBSD Port: www/php74-opcache had to be disabled after "service apache24 reload" core dumped 48. Sep 6 Karel Gardas Install to ZFS root is using device names hence failing when device tree is changed. 49. Sep 6 Karel Gardas Install to ZFS root is using device names hence failing when device tree is changed. 50. Sep 7 Peter Jeremy Re: Install to ZFS root is using device names hence failing when device tree is changed. 51. Sep 7 Karel Gardas Re: Install to ZFS root is using device names hence failing when device tree is changed. 52. Sep 12 Yuri Tcherkasov ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument 53. Sep 12 Alexander V. Chernikov Re: ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument 54. Sep 12 Yuri Tcherkasov Re: ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument 55. Sep 12 Yuri Tcherkasov Re: ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument 56. Sep 12 Yuri Tcherkasov Re: ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument 57. Sep 12 Alexander V. Chernikov Re: ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument 58. Sep 12 Yuri Tcherkasov Re: ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument 59. Sep 7 Steve Kargl killall, symlinks, and signal delivery? 60. Sep 7 Cy Schubert Re: killall, symlinks, and signal delivery?
61. Sep 8 Steve Kargl Re: killall, symlinks, and signal delivery? 62. Sep 8 Jamie Landeg-Jones Re: killall, symlinks, and signal delivery? 63. Sep 9 Steve Kargl Re: killall, symlinks, and signal delivery? 64. Sep 7 Mehmet Erol Sanliturk Move the Handbook into source tree 65. Sep 7 David Chisnall Re: Move the Handbook into source tree 66. Sep 7 Mehmet Erol Sanliturk Re: Move the Handbook into source tree 67. Sep 7 Wolfram Schneider Re: Move the Handbook into source tree 68. Sep 7 Mehmet Erol Sanliturk Re: Move the Handbook into source tree 69. Sep 9 FreeBSD User OpenSSH issue: 14-Current rejects non-publickey scp/ssh/rsync connectiosn all of the sudden 70. Sep 9 Philipp Ost Re: OpenSSH issue: 14-Current rejects non-publickey scp/ssh/rsync connectiosn all of the sudden 71. Sep 9 Ed Maste Re: OpenSSH issue: 14-Current rejects non-publickey scp/ssh/rsync connectiosn all of the sudden 72. Sep 10 FreeBSD User Re: OpenSSH issue: 14-Current rejects non-publickey scp/ssh/rsync connectiosn all of the sudden 73. Sep 10 Gary Jennejohn Re: OpenSSH issue: 14-Current rejects non-publickey scp/ssh/rsync connectiosn all of the sudden 74. Sep 10 Gary Jennejohn Re: OpenSSH issue: 14-Current rejects non-publickey scp/ssh/rsync connectiosn all of the sudden 75. Sep 10 Ed Maste Re: OpenSSH issue: 14-Current rejects non-publickey scp/ssh/rsync connectiosn all of the sudden 76. Sep 6 Eric McCorkle Re: PAM module for loading ZFS keys on login 77. Sep 6 Eric McCorkle Re: PAM module for loading ZFS keys on login 78. Sep 6 Steffen Nurpmeso Re: PAM module for loading ZFS keys on login 79. Sep 6 Steffen Nurpmeso Re: PAM module for loading ZFS keys on login 80. Sep 7 Konstantin Belousov Re: PAM module for loading ZFS keys on login
81. Sep 7 Steffen Nurpmeso Re: PAM module for loading ZFS keys on login 82. Sep 11 Jeremie Le Hen undefined symbol: rand_range 83. Sep 6 Graham Perrin wlan0 functional for me with n249159-bb61ccd530b (was: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0) 84. Sep 6 Cy Schubert Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 85. Sep 6 Cy Schubert Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 86. Sep 6 Cy Schubert Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 87. Sep 6 Cy Schubert Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 88. Sep 6 Cy Schubert Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 89. Sep 6 Cy Schubert Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 90. Sep 7 Cy Schubert Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 91. Sep 8 Cy Schubert Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 92. Sep 9 Cy Schubert Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 93. Sep 6 Idwer Vollering Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 94. Sep 6 Idwer Vollering Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 95. Sep 6 Oleg V. Nauman Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 96. Sep 6 Oleg V. Nauman Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 97. Sep 6 Oleg V. Nauman Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 98. Sep 6 Oleg V. Nauman Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 99. Sep 6 Filipe da Silva Santos via Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 100. Sep 7 Jakob Alvermark Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0
101. Sep 7 David Wolfskill Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 102. Sep 8 Idwer Vollering Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 103. Sep 8 Filipe da Silva Santos via Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0
home | up | archive | sorted by: subject - author - date - reverse date