2019/freebsd-current/20190519.freebsd-current
Messages: 75, new messages first
|
Last update: Mon Feb 13 14:17:13 2023
|
|
home | archive sorted by: subject | author | date | reverse date
1. May 18 Konstantin Belousov Re: panic booting with if_tap_load="YES" in loader.conf 2. May 18 Adam Re: FreeBSD Core Team Response to Controversial Social Media Posts 3. May 18 Warner Losh Re: panic booting with if_tap_load="YES" in loader.conf 4. May 18 Mark Johnston Re: panic booting with if_tap_load="YES" in loader.conf 5. May 18 Konstantin Belousov Re: panic booting with if_tap_load="YES" in loader.conf 6. May 18 Konstantin Belousov Re: panic booting with if_tap_load="YES" in loader.conf 7. May 18 Mark Johnston Re: Panic after update from r347896 to r347950: panic: insanity vmem 0xffffffff81d7c840 8. May 18 Mark Johnston Re: panic booting with if_tap_load="YES" in loader.conf 9. May 18 Rebecca Cran Re: panic booting with if_tap_load="YES" in loader.conf 10. May 18 David Wolfskill Panic after update from r347896 to r347950: panic: insanity vmem 0xffffffff81d7c840 11. May 18 Igor Mozolevsky Re: FreeBSD Core Team Response to Controversial Social Media Posts 12. May 18 Konstantin Belousov Re: panic booting with if_tap_load="YES" in loader.conf 13. May 18 Thomas Mueller Re: Inability to build FreeBSD-current amd64 14. May 18 Mark Johnston Re: panic booting with if_tap_load="YES" in loader.conf 15. May 18 Rebecca Cran panic booting with if_tap_load="YES" in loader.conf 16. May 18 Rebecca Cran panic booting with if_tap_load="YES" in loader.conf 17. May 17 v@researchbsd.org Re: FreeBSD Core Team Response to Controversial Social Media Posts 18. May 17 David Wolfskill Re: mergemaster still having issues 19. May 17 Pete Wright Re: mergemaster still having issues 20. May 17 David Wolfskill Re: mergemaster still having issues
21. May 17 Pete Wright mergemaster still having issues 22. May 16 Mateusz Piotrowski Re: r347638 breaks mergemaster 23. May 16 Igor Mozolevsky Re: FreeBSD Core Team Response to Controversial Social Media Posts 24. May 16 Brad Davis Re: r347638 breaks mergemaster 25. May 16 David Wolfskill r347638 breaks mergemaster 26. May 16 Niclas Zeising Re: Inability to build FreeBSD-current amd64 27. May 16 Thomas Mueller Re: Inability to build FreeBSD-current amd64 28. May 16 Niclas Zeising Re: Inability to build FreeBSD-current amd64 29. May 16 Rick Macklem patch that replaces a single linked list with a hash table of lists (mountd.c) for review 30. May 16 Thomas Mueller Re: Inability to build FreeBSD-current amd64 31. May 15 Ian Lepore Re: Inability to build FreeBSD-current amd64 32. May 15 Thomas Mueller Re: Inability to build FreeBSD-current amd64 33. May 15 Pat McEvoy Updated stream links 34. May 15 Ian Lepore Re: Inability to build FreeBSD-current amd64 35. May 15 Thomas Mueller Re: Inability to build FreeBSD-current amd64 36. May 15 Pat McEvoy Links 37. May 15 Pat McEvoy freeBSD Developer Summit - DMS1160 Stream 38. May 15 O. Hartmann 12-STABLE: poudriere jail installation/updating is failing 39. May 15 <kris@ixsystems.com> Updated Install Images with ZoL 40. May 15 tech-lists Re: Inability to build FreeBSD-current amd64
41. May 15 Thomas Mueller Re: Inability to build FreeBSD-current amd64 42. May 15 Don Lewis Re: error when updating 13.0-CURRENT i386 poudriere jail to r347606 43. May 15 Don Lewis error when updating 13.0-CURRENT i386 poudriere jail to r347606 44. May 15 Enji Cooper Re: Inability to build FreeBSD-current amd64 45. May 14 Konstantin Belousov Re: leaked swap? 46. May 14 Thomas Munro Re: leaked swap? 47. May 14 Brooks Davis Re: FCP-101: obsolete driver removal planned for 2019-05-18 48. May 14 Thomas Mueller Inability to build FreeBSD-current amd64 49. May 14 Kyle Evans Re: panic in tunstart_l2() 50. May 14 Kyle Evans Re: panic in tunstart_l2() 51. May 14 Mark Johnston panic in tunstart_l2() 52. May 14 Bob Bishop Re: leaked swap? 53. May 14 Andriy Gapon Re: leaked swap? 54. May 13 Trev Re: FCP-101: obsolete driver removal planned for 2019-05-18 55. May 13 Joel Dahl Re: FCP-101: obsolete driver removal planned for 2019-05-18 56. May 13 Warner Losh Re: FCP-101: obsolete driver removal planned for 2019-05-18 57. May 13 Rodney W. Grimes Re: FCP-101: obsolete driver removal planned for 2019-05-18 58. May 13 Julian H. Stacey Re: FCP-101: obsolete driver removal planned for 2019-05-18 59. May 12 Ian Lepore Re: FCP-101: obsolete driver removal planned for 2019-05-18 60. May 12 Rodney W. Grimes Re: FCP-101: obsolete driver removal planned for 2019-05-18
61. May 12 Eugene Grosbein Re: FCP-101: obsolete driver removal planned for 2019-05-18 62. May 12 Igor Mozolevsky Re: FreeBSD Core Team Response to Controversial Social Media Posts 63. May 12 Warner Losh Re: FCP-101: obsolete driver removal planned for 2019-05-18 64. May 12 Julian H. Stacey Re: FreeBSD Core Team Response to Controversial Social Media Posts 65. May 12 v@researchbsd.org Re: FreeBSD Core Team Response to Controversial Social Media Posts 66. May 12 Sulev-Madis Silber Re: FreeBSD Core Team Response to Controversial Social Media Posts 67. May 12 Greg V Re: FreeBSD Core Team Response to Controversial Social Media Posts 68. May 12 Marko Zec Re: FreeBSD Core Team Response to Controversial Social Media Posts 69. May 12 Gary Jennejohn Re: FCP-101: obsolete driver removal planned for 2019-05-18 70. May 12 Alexandr Krivulya Re: ipsec not working 71. May 12 Kubilay Kocak Re: ipsec not working 72. May 12 Alexandr Krivulya ipsec not working 73. May 12 Warner Losh Re: FCP-101: obsolete driver removal planned for 2019-05-18 74. May 12 Miroslav Lachman Re: FreeBSD Core Team Response to Controversial Social Media Posts 75. May 11 Eugene Grosbein Re: FCP-101: obsolete driver removal planned for 2019-05-18
home | archive sorted by: subject | author | date | reverse date