2009/freebsd-hackers/20090118.freebsd-hackers
Messages: 93, new messages first
|
Last update: Mon Feb 13 14:17:40 2023
|
|
home | archive sorted by: subject | author | date | reverse date
1. Jan 17 xorquewasp@googlemail.com gcc 4.3.2 libgcc_s.so exception handling broken? 2. Jan 17 =?ISO-8859-1?Q?Mikko_Ty=F6 Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's 3. Jan 17 lazaax - admin jop 4. Jan 17 =?utf-8?Q?Dag-Erling_Sm=C3 Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's 5. Jan 16 Jason Evans Re: threaded, forked, rethreaded processes will deadlock 6. Jan 16 Xin LI Re: A patch of HPTIOP driver for 7.1-RELEASE 7. Jan 16 Brian Fundakowski Feldman Re: threaded, forked, rethreaded processes will deadlock 8. Jan 16 Stefan Farfeleder Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl (3) setting `odd' errno's 9. Jan 16 Nate Eldredge Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl (3) setting `odd' errno's 10. Jan 16 Garrett Cooper Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl (3) setting `odd' errno's 11. Jan 16 clc@ournetos.com a CD you might interested in 12. Jan 16 Alexej Sokolov Re: How to access kernel memory from user space 13. Jan 16 Thierry Herbelot Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl (3) setting `odd' errno's 14. Jan 16 Stefan Farfeleder Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl (3) setting `odd' errno's 15. Jan 16 Danny Braniss Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl (3) setting `odd' errno's 16. Jan 16 Christoph Mallon Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl (3) setting `odd' errno's 17. Jan 16 Danny Braniss Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl (3) setting `odd' errno's 18. Jan 16 Christoph Mallon Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl (3) setting `odd' errno's 19. Jan 16 Christoph Mallon Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl (3) setting `odd' errno's 20. Jan 16 Garrett Cooper Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl (3) setting `odd' errno's
21. Jan 16 Garrett Cooper Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl (3) setting `odd' errno's 22. Jan 16 Christoph Mallon Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl (3) setting `odd' errno's 23. Jan 16 Christian Kandeler Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl (3) setting `odd' errno's 24. Jan 16 Christoph Mallon Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's 25. Jan 16 Garrett Cooper Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's 26. Jan 16 Jacques Fourie Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's 27. Jan 16 Garrett Cooper Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's 28. Jan 16 Jacques Fourie Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's 29. Jan 16 Maxim Konovalov Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's 30. Jan 16 Garrett Cooper Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's 31. Jan 16 Christoph Mallon Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's 32. Jan 16 Garrett Cooper Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's 33. Jan 16 Garrett Cooper Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's 34. Jan 16 Garrett Cooper Re: panic: Going nowhere without my init! 35. Jan 15 Gerry Weaver Re: How to access kernel memory from user space 36. Jan 15 Alexej Sokolov Re: How to access kernel memory from user space 37. Jan 15 Callum Gibson bg_fsck ignores fstab pass numbers? 38. Jan 15 Kamlesh Patel panic: Going nowhere without my init! 39. Jan 14 Biks N Re: how ipfw firewall is implemented in the kernel 40. Jan 14 Max Laier Re: how ipfw firewall is implemented in the kernel
41. Jan 14 Mikolaj Golub How to calculate current kmem usage? 42. Jan 14 Biks N how ipfw firewall is implemented in the kernel 43. Jan 14 Kostik Belousov Re: kernel dump with 7.1-RELEASE 44. Jan 13 Peter Jeremy Re: 3x read to write ratio on dump/restore 45. Jan 13 Yoshihiro Ota Re: gcache [was: Re: 3x read to write ratio on dump/restore] 46. Jan 12 Julian Elischer Re: panic by unlocking of mutex in KLD 47. Jan 12 Mateusz Guzik Re: panic by unlocking of mutex in KLD 48. Jan 12 Giorgos Keramidas Re: Determine if a kernel is built with a specific option? 49. Jan 12 Alexej Sokolov Re: panic by unlocking of mutex in KLD 50. Jan 12 Alexej Sokolov Re: panic by unlocking of mutex in KLD 51. Jan 12 Mateusz Guzik Re: panic by unlocking of mutex in KLD 52. Jan 12 =?utf-8?Q?Dag-Erling_Sm=C3 Re: kernel panic 53. Jan 12 Garrett Cooper Re: kernel panic 54. Jan 12 Alexej Sokolov Re: panic by unlocking of mutex in KLD 55. Jan 12 Mateusz Guzik Re: panic by unlocking of mutex in KLD 56. Jan 12 Tim Kientzle Re: extattr problems? 57. Jan 12 Andrew Brampton Re: Determine if a kernel is built with a specific option? 58. Jan 12 Alexej Sokolov Re: panic by unlocking of mutex in KLD 59. Jan 12 Andrew Thompson Re: Determine if a kernel is built with a specific option? 60. Jan 12 Robert Watson Re: extattr problems?
61. Jan 12 Eugene Grosbein Re: Determine if a kernel is built with a specific option? 62. Jan 12 Hans Petter Selasky Re: panic by unlocking of mutex in KLD 63. Jan 12 Andrew Brampton Re: Determine if a kernel is built with a specific option? 64. Jan 12 =?utf-8?Q?Dag-Erling_Sm=C3 Re: kernel panic 65. Jan 12 =?utf-8?Q?Dag-Erling_Sm=C3 Re: /dev/dsp* & /dev/audio* devices not present 66. Jan 12 =?utf-8?Q?Dag-Erling_Sm=C3 Re: "/var/log/messages" logs appear in the output of "sysctl -a" 67. Jan 12 Mateusz Guzik Re: panic by unlocking of mutex in KLD 68. Jan 12 Alexej Sokolov panic by unlocking of mutex in KLD 69. Jan 12 pluknet Re: Determine if a kernel is built with a specific option? 70. Jan 12 Matthew Seaman Re: gcache [was: Re: 3x read to write ratio on dump/restore] 71. Jan 12 Andrew Brampton Determine if a kernel is built with a specific option? 72. Jan 12 Christian Brueffer Re: gcache [was: Re: 3x read to write ratio on dump/restore] 73. Jan 12 Ivan Voras Re: gcache [was: Re: 3x read to write ratio on dump/restore] 74. Jan 12 Ollivier Robert Re: 3x read to write ratio on dump/restore 75. Jan 12 Christoph Mallon gcache [was: Re: 3x read to write ratio on dump/restore] 76. Jan 12 Yoshihiro Ota Re: 3x read to write ratio on dump/restore 77. Jan 12 Rick C. Petty Re: /dev/dsp* & /dev/audio* devices not present 78. Jan 12 perryh@pluto.rain.com Re: /dev/dsp* & /dev/audio* devices not present 79. Jan 12 Tim Kientzle Re: extattr problems? 80. Jan 12 Tim Kientzle Re: extattr problems?
81. Jan 11 Christoph Mallon Question about panic in brelse() 82. Jan 11 Garance A Drosehn Re: Small change to 'ps' 83. Jan 11 Omer Faruk Sen Re: kernel dump with 7.1-RELEASE 84. Jan 11 Rick C. Petty Re: /dev/dsp* & /dev/audio* devices not present 85. Jan 11 Kostik Belousov Re: kernel dump with 7.1-RELEASE 86. Jan 11 Peter Jeremy Re: kernel panic 87. Jan 11 pluknet Re: extattr problems? 88. Jan 11 Peter Jeremy Re: 3x read to write ratio on dump/restore 89. Jan 11 M. Warner Losh Re: 3x read to write ratio on dump/restore 90. Jan 11 Pyun YongHyeon Re: support for i45 (ich10) chipsets 91. Jan 11 Tim Kientzle Re: extattr problems? 92. Jan 11 pluknet Re: extattr problems? 93. Jan 11 perryh@pluto.rain.com Re: /dev/dsp* & /dev/audio* devices not present
home | archive sorted by: subject | author | date | reverse date