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