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