2007/freebsd-hackers/20070617.freebsd-hackers
Messages: 114, sorted by subject
|
Last update: Mon Feb 13 14:17:35 UTC 2023
|
|
home | up | archive sorted by: subject | author | date | reverse date
1. Jun 14 Roman Divacky [PATCH]: acct_process() locking and exit1() 2. Jun 14 Roman Divacky Re: [PATCH]: acct_process() locking and exit1() 3. Jun 11 Jeremy Chadwick ASCII menu in loader/frames.4th 4. Jun 12 =?utf-8?Q?Dag-Erling_Sm=C3 Re: ASCII menu in loader/frames.4th 5. Jun 12 Jeremy Chadwick Re: ASCII menu in loader/frames.4th 6. Jun 12 =?utf-8?Q?Dag-Erling_Sm=C3 Re: ASCII menu in loader/frames.4th 7. Jun 13 Z.C.B. building images for running from flash 8. Jun 13 Eugene Grosbein Re: building images for running from flash 9. Jun 13 Z.C.B. Re: building images for running from flash 10. Jun 13 Eugene Grosbein Re: building images for running from flash 11. Jun 13 Z.C.B. Re: building images for running from flash 12. Jun 13 Mike Meyer Re: building images for running from flash 13. Jun 13 =?ISO-8859-1?Q?Zavam,_Vin= Re: building images for running from flash 14. Jun 13 Z.C.B. Re: building images for running from flash 15. Jun 10 Ivan Voras Disable mutex spinning? 16. Jun 10 Ivan Voras Re: Disable mutex spinning? 17. Jun 14 Matthew Hagerty Disk block or sector to file mapping? 18. Jun 14 Jeremy Chadwick Re: Disk block or sector to file mapping? 19. Jun 14 Anton Yuzhaninov Re: Disk block or sector to file mapping? 20. Jun 15 Peter Jeremy Re: Disk block or sector to file mapping?
21. Jun 10 Roman Divacky Re: file(1) cannot detect UFS2? 22. Jun 10 Ivan Voras Re: file(1) cannot detect UFS2? 23. Jun 10 Wilkinson, Alex Re: file(1) cannot detect UFS2? 24. Jun 10 Ivan Voras Re: file(1) cannot detect UFS2? 25. Jun 10 Roman Divacky Re: file(1) cannot detect UFS2? 26. Jun 10 Ivan Voras Re: file(1) cannot detect UFS2? 27. Jun 16 David Naylor FreeBSD and Information handling 28. Jun 16 Nikolay Pavlov Re: FreeBSD and Information handling 29. Jun 16 Ivan Voras Re: FreeBSD and Information handling 30. Jun 15 Ali Mashtizadeh Fwd: AMD deciding _now_ what to do about Linux 31. Jun 15 Jeremy Chadwick Re: Fwd: AMD deciding _now_ what to do about Linux 32. Jun 15 Ali Mashtizadeh Re: Fwd: AMD deciding _now_ what to do about Linux 33. Jun 15 youshi10@u.washington.edu Re: Fwd: AMD deciding _now_ what to do about Linux 34. Jun 16 Dieter Re: Fwd: AMD deciding _now_ what to do about Linux 35. Jun 16 Wilko Bulte Re: Fwd: AMD deciding _now_ what to do about Linux 36. Jun 16 Garrett Cooper Re: Fwd: AMD deciding _now_ what to do about Linux 37. Jun 16 Wilko Bulte Re: Fwd: AMD deciding _now_ what to do about Linux 38. Jun 10 Matthew Dillon Re: GPT - (last) call for action 39. Jun 10 Marcel Moolenaar Re: GPT - (last) call for action 40. Jun 10 Matthew Dillon Re: GPT - (last) call for action
41. Jun 10 Rui Paulo Re: GPT - (last) call for action 42. Jun 10 Rui Paulo Re: GPT - (last) call for action 43. Jun 11 Rui Paulo Re: GPT - (last) call for action 44. Jun 11 Rui Paulo Re: GPT - (last) call for action 45. Jun 11 Chuck Swiger Re: GPT - (last) call for action 46. Jun 11 Chuck Swiger Re: GPT - (last) call for action 47. Jun 11 Matthew Dillon Re: GPT - (last) call for action 48. Jun 12 Rui Paulo Re: GPT - (last) call for action 49. Jun 12 Ivan Voras Re: GPT - (last) call for action 50. Jun 12 Rui Paulo Re: GPT - (last) call for action 51. Jun 11 Mark Saad HP SmartArray ( CISS ) and CAMCONTROL 52. Jun 11 Mark Saad Re: HP SmartArray ( CISS ) and CAMCONTROL 53. Jun 11 mjacob@freebsd.org Re: HP SmartArray ( CISS ) and CAMCONTROL 54. Jun 11 mjacob@freebsd.org Re: HP SmartArray ( CISS ) and CAMCONTROL 55. Jun 11 Joao Barros Re: HP SmartArray ( CISS ) and CAMCONTROL 56. Jun 11 Mark Saad Re: HP SmartArray ( CISS ) and CAMCONTROL 57. Jun 11 mjacob@freebsd.org Re: HP SmartArray ( CISS ) and CAMCONTROL 58. Jun 11 Mark Saad Re: HP SmartArray ( CISS ) and CAMCONTROL 59. Jun 11 Wilko Bulte Re: HP SmartArray ( CISS ) and CAMCONTROL 60. Jun 14 Ulf Zimmermann Re: HP SmartArray ( CISS ) and CAMCONTROL
61. Jun 10 =?UTF-8?Q?Karl_Sj=C3=B6dah IPv6 ANSI cleanup 62. Jun 10 Stefan Sperling Re: kern/83807: [sis] [patch] if_sis: Wake On Lan support for FreeBSD 63. Jun 13 Stefan Sperling Re: kern/83807: [sis] [patch] if_sis: Wake On Lan support for FreeBSD 64. Jun 12 Cole Kqueue queries 65. Jun 12 James Bailie Re: Kqueue queries 66. Jun 12 James Bailie Re: Kqueue queries 67. Jun 11 Hans Petter Selasky Re: Lost interrupts during boot 68. Jun 14 Harald Servat PAPI in the ports 69. Jun 10 Jeff Anton pkgdb -F calling portupgrade -a 70. Jun 11 Kris Kennaway Re: pkgdb -F calling portupgrade -a 71. Jun 11 Mike Meyer Re: pkgdb -F calling portupgrade -a 72. Jun 11 Kris Kennaway Re: pkgdb -F calling portupgrade -a 73. Jun 11 Mike Meyer Re: pkgdb -F calling portupgrade -a 74. Jun 11 Kris Kennaway Re: pkgdb -F calling portupgrade -a 75. Jun 15 Christian Kandeler Question about serial console code 76. Jun 15 Marcel Moolenaar Re: Question about serial console code 77. Jun 13 Garrett Cooper Re: Reason for doing malloc / bzero over calloc (performance)? 78. Jun 13 Ed Schouten Re: Reason for doing malloc / bzero over calloc (performance)? 79. Jun 13 youshi10@u.washington.edu Re: Reason for doing malloc / bzero over calloc (performance)? 80. Jun 14 Ivan Voras Re: Reason for doing malloc / bzero over calloc (performance)?
81. Jun 14 youshi10@u.washington.edu Re: Reason for doing malloc / bzero over calloc (performance)? 82. Jun 14 Ivan Voras Re: Reason for doing malloc / bzero over calloc (performance)? 83. Jun 15 Matthew Dillon Re: Reason for doing malloc / bzero over calloc (performance)? 84. Jun 15 youshi10@u.washington.edu Re: Reason for doing malloc / bzero over calloc (performance)? 85. Jun 15 Joerg Sonnenberger Re: Reason for doing malloc / bzero over calloc (performance)? 86. Jun 13 Garrett Cooper Reason for doing malloc / bzero over calloc? 87. Jun 10 Maslan Ricoh r5u870 88. Jun 12 Vladimir Terziev SATA RAID problems 89. Jun 13 Garrett Cooper Using shell commands versus C equivalents 90. Jun 13 Garrett Cooper Re: Using shell commands versus C equivalents 91. Jun 13 Alexander Leidinger Re: Using shell commands versus C equivalents 92. Jun 13 David Wolfskill Re: Using shell commands versus C equivalents 93. Jun 13 Danny Braniss Re: Using shell commands versus C equivalents 94. Jun 13 Mike Meyer Re: Using shell commands versus C equivalents 95. Jun 13 Garrett Cooper Re: Using shell commands versus C equivalents 96. Jun 13 Joerg Sonnenberger Re: Using shell commands versus C equivalents 97. Jun 13 Joerg Sonnenberger Re: Using shell commands versus C equivalents 98. Jun 13 Gregory Shapiro Re: Using shell commands versus C equivalents 99. Jun 13 Rick C. Petty Re: Using shell commands versus C equivalents 100. Jun 13 Joerg Sonnenberger Re: Using shell commands versus C equivalents
101. Jun 13 Joerg Sonnenberger Re: Using shell commands versus C equivalents 102. Jun 13 youshi10@u.washington.edu Re: Using shell commands versus C equivalents 103. Jun 13 youshi10@u.washington.edu Re: Using shell commands versus C equivalents 104. Jun 13 Joerg Sonnenberger Re: Using shell commands versus C equivalents 105. Jun 13 Joerg Sonnenberger Re: Using shell commands versus C equivalents 106. Jun 13 Rick C. Petty Re: Using shell commands versus C equivalents 107. Jun 13 Tim Kientzle Re: Using shell commands versus C equivalents 108. Jun 13 youshi10@u.washington.edu Re: Using shell commands versus C equivalents 109. Jun 13 youshi10@u.washington.edu Re: Using shell commands versus C equivalents 110. Jun 14 Stephen Montgomery-Smith Re: Using shell commands versus C equivalents 111. Jun 14 youshi10@u.washington.edu Re: Using shell commands versus C equivalents 112. Jun 14 Tim Kientzle Re: Using shell commands versus C equivalents 113. Jun 14 Danny Braniss Re: Using shell commands versus C equivalents 114. Jun 14 Alexander Leidinger Re: Using shell commands versus C equivalents
home | up | archive sorted by: subject | author | date | reverse date