Skip site navigation (1)Skip section navigation (2)


2012/freebsd-current/20121007.freebsd-current

Messages: 75, sorted by subject
Last page update: Sat Jan 3 13:08:23 UTC 2026

home | up | archive | sorted by: subject - author - date - reverse date
  1. Oct  4 Sean Bruno                 [CFT]hwpmc update for sandybridge-e
  2. Oct  4 Jim Harris                  Re: [CFT]hwpmc update for sandybridge-e
  3. Oct  5 Fabien Thomas               Re: [CFT]hwpmc update for sandybridge-e
  4. Oct  5 Fabien Thomas               Re: [CFT]hwpmc update for sandybridge-e
  5. Oct  3 FreeBSD Tinderbox          [head tinderbox] failure on arm/arm
  6. Oct  3 FreeBSD Tinderbox           [head tinderbox] failure on arm/arm
  7. Oct  3 Ian FREISLICH               Re: [head tinderbox] failure on arm/arm
  8. Oct  2 FreeBSD Tinderbox          [head tinderbox] failure on i386/i386
  9. Oct  2 FreeBSD Tinderbox           [head tinderbox] failure on i386/i386
 10. Oct  3 FreeBSD Tinderbox           [head tinderbox] failure on i386/i386
 11. Oct  3 FreeBSD Tinderbox           [head tinderbox] failure on i386/i386
 12. Oct  4 Gabor Kovesdan             [HEADSUP] Upcoming GNU sort removal
 13. Oct  4 Dennis Glatting             Re: [HEADSUP] Upcoming GNU sort removal
 14. Oct  4 Gabor Kovesdan              Re: [HEADSUP] Upcoming GNU sort removal
 15. Oct  4 C. P. Ghost                 Re: [HEADSUP] Upcoming GNU sort removal
 16. Oct  4 Chuck Burns                 Re: [HEADSUP] Upcoming GNU sort removal
 17. Oct  5 Dennis Glatting             Re: [HEADSUP] Upcoming GNU sort removal
 18. Oct  5 Volodymyr Kostyrko          Re: [HEADSUP] Upcoming GNU sort removal
 19. Oct  5 Volodymyr Kostyrko          Re: [HEADSUP] Upcoming GNU sort removal
 20. Oct  1 Svatopluk Kraus            Re: [patch] mmap() MAP_TEXT implementation (to use for shared libraries)

 21. Oct  4 Marek Salwerowicz          Re: [SPAM]Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
 22. Oct  4 Ian Lepore                  Re: [SPAM]Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
 23. Oct  2 YongHyeon PYUN             Re: Call for bge(4) testers
 24. Oct  2 Sean Bruno                  Re: Call for bge(4) testers
 25. Sep 30 David Wolfskill            clang reports reports errors (buildkernel @r241067)
 26. Oct  5 Glen Barber                FreeBSD 10-CURRENT and 9-STABLE snapshots
 27. Oct  5 Miroslav Lachman            Re: FreeBSD 10-CURRENT and 9-STABLE snapshots
 28. Oct  6 Bruce Cran                  Re: FreeBSD 10-CURRENT and 9-STABLE snapshots
 29. Oct  6 Glen Barber                 Re: FreeBSD 10-CURRENT and 9-STABLE snapshots
 30. Oct  6 O. Hartmann                 Re: FreeBSD 10-CURRENT and 9-STABLE snapshots
 31. Oct  1 Radio młodych bandytów     Re: freebsd-current Digest, Vol 464, Issue 3
 32. Oct  4 Talovikov Boris Aleksandro fusefs-sshfs crash
 33. Oct  1 Andrey V. Elsukov          Re: gpart on macbook air
 34. Oct  1 Raoul MEGELAS               Re: gpart on macbook air
 35. Oct  1 Raoul MEGELAS               Re: gpart on macbook air
 36. Sep 30 Raoul MEGELAS               gpart on macbook air
 37. Sep 30 Andrey V. Elsukov           Re: gpart on macbook air
 38. Sep 30 Raoul MEGELAS               Re: gpart on macbook air
 39. Oct  1 Alexey Reytsman            high interrupts load xhci
 40. Oct  3 Marek Salwerowicz          Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

 41. Oct  4 Lev Serebryakov             Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
 42. Oct  4 Darrel                     memory warnings r240891  |  dmesgg
 43. Oct  5 Darrel                     Re: memory warnings r240891 | dmesg
 44. Oct  4 Sergey Kandaurov           Re: memory warnings r240891 | dmesgg
 45. Oct  1 John Baldwin               Re: panic possibly on on bridge member removal
 46. Oct  1 Kim Culhan                  Re: panic possibly on on bridge member removal
 47. Oct  1 John Baldwin                Re: panic possibly on on bridge member removal
 48. Oct  1 Kim Culhan                  Re: panic possibly on on bridge member removal
 49. Oct  1 Adrian Chadd                Re: panic possibly on on bridge member removal
 50. Oct  1 John Baldwin                Re: panic possibly on on bridge member removal
 51. Oct  1 Doug Barton                Re: squealing/whistling audio
 52. Oct  4 Rick Macklem               svn MFC to stable/8
 53. Oct  4 Sean Bruno                  Re: svn MFC to stable/8
 54. Oct  4 Rick Macklem                Re: svn MFC to stable/8
 55. Oct  4 Eitan Adler                 Re: svn MFC to stable/8
 56. Oct  4 John Baldwin                Re: svn MFC to stable/8
 57. Oct  4 Rick Macklem                Re: svn MFC to stable/8
 58. Oct  5 John Baldwin                Re: svn MFC to stable/8
 59. Oct  3 <freebsd@chrysalisnet.org> sysctl kern.ipc.somaxconn limit 65535 why?
 60. Oct  3 Garrett Cooper              Re: sysctl kern.ipc.somaxconn limit 65535 why?

 61. Oct  3 Adrian Chadd                Re: sysctl kern.ipc.somaxconn limit 65535 why?
 62. Oct  3 Xin Li                      Re: sysctl kern.ipc.somaxconn limit 65535 why?
 63. Oct  3 Adrian Chadd                Re: sysctl kern.ipc.somaxconn limit 65535 why?
 64. Oct  3 Andre Oppermann             Re: sysctl kern.ipc.somaxconn limit 65535 why?
 65. Oct  3 Garrett Cooper              Re: sysctl kern.ipc.somaxconn limit 65535 why?
 66. Oct  3 Xin Li                      Re: sysctl kern.ipc.somaxconn limit 65535 why?
 67. Oct  3 Ryan Stone                  Re: sysctl kern.ipc.somaxconn limit 65535 why?
 68. Oct  3 Garrett Cooper              Re: sysctl kern.ipc.somaxconn limit 65535 why?
 69. Oct  4 Peter Jeremy                Re: sysctl kern.ipc.somaxconn limit 65535 why?
 70. Oct  4 Adrian Chadd                Re: sysctl kern.ipc.somaxconn limit 65535 why?
 71. Oct  5 Ivan Voras                  Re: sysctl kern.ipc.somaxconn limit 65535 why?
 72. Oct  5 Adrian Chadd                Re: sysctl kern.ipc.somaxconn limit 65535 why?
 73. Oct  5 Bernd Walter                Re: sysctl kern.ipc.somaxconn limit 65535 why?
 74. Oct  6 Luigi Rizzo                sysctl-controlled key-value store ?
 75. Oct  6 Andrew Thompson             Re: sysctl-controlled key-value store ?

home | up | archive | sorted by: subject - author - date - reverse date