2000/freebsd-arch/20001119.freebsd-arch
Messages: 127, old messages first
|
Last update: Mon Feb 13 14:14:02 2023
|
|
home | archive sorted by: subject | author | date | reverse date
1. Nov 12 Jeroen Ruigrok/Asmodai Re: updating rdist 2. Nov 12 Will Andrews Re: updating rdist 3. Nov 12 David O'Brien Re: updating rdist 4. Nov 13 Cy Schubert - ITSD Open Sy Re: updating rdist 5. Nov 13 Cy Schubert - ITSD Open Sy Re: updating rdist 6. Nov 13 Cy Schubert - ITSD Open Sy Re: updating rdist 7. Nov 13 John Baldwin Turning on debugging in GENERIC 8. Nov 13 Mark Murray Re: Turning on debugging in GENERIC 9. Nov 14 Daniel C. Sobral Re: Turning on debugging in GENERIC 10. Nov 14 John W. De Boskey Re: Turning on debugging in GENERIC 11. Nov 14 Poul-Henning Kamp RANDOMDEV inspired realitycheck regarding i386/i486... 12. Nov 14 Ben Smithurst Re: RANDOMDEV inspired realitycheck regarding i386/i486... 13. Nov 14 John Baldwin RE: RANDOMDEV inspired realitycheck regarding i386/i486... 14. Nov 14 Terry Lambert Re: RANDOMDEV inspired realitycheck regarding i386/i486... 15. Nov 14 Wilko Bulte Re: RANDOMDEV inspired realitycheck regarding i386/i486... 16. Nov 14 Warner Losh Re: RANDOMDEV inspired realitycheck regarding i386/i486... 17. Nov 14 Warner Losh Re: RANDOMDEV inspired realitycheck regarding i386/i486... 18. Nov 14 John Baldwin Re: RANDOMDEV inspired realitycheck regarding i386/i486... 19. Nov 14 Matthew N. Dodd Re: RANDOMDEV inspired realitycheck regarding i386/i486... 20. Nov 14 Neil Ludban Re: RANDOMDEV inspired realitycheck regarding i386/i486...
21. Nov 14 Kenneth D. Merry new zero copy sockets and NFS snapshot 22. Nov 14 Adrian Chadd Re: RANDOMDEV inspired realitycheck regarding i386/i486... 23. Nov 15 Marius Bendiksen Re: RANDOMDEV inspired realitycheck regarding i386/i486... 24. Nov 15 Marius Bendiksen Re: RANDOMDEV inspired realitycheck regarding i386/i486... 25. Nov 15 Eivind Eklund Re: Turning on debugging in GENERIC 26. Nov 15 Terry Lambert Re: RANDOMDEV inspired realitycheck regarding i386/i486... 27. Nov 15 Terry Lambert Re: RANDOMDEV inspired realitycheck regarding i386/i486... 28. Nov 15 Terry Lambert Re: Turning on debugging in GENERIC 29. Nov 15 John Baldwin Re: Turning on debugging in GENERIC 30. Nov 15 John W. De Boskey Re: Turning on debugging in GENERIC 31. Nov 15 Cy Schubert - ITSD Open Sy Re: RANDOMDEV inspired realitycheck regarding i386/i486... 32. Nov 15 Wilko Bulte Re: RANDOMDEV inspired realitycheck regarding i386/i486... 33. Nov 15 Adrian Chadd Re: RANDOMDEV inspired realitycheck regarding i386/i486... 34. Nov 15 Cy Schubert - ITSD Open Sy Re: Turning on debugging in GENERIC 35. Nov 15 Cy Schubert - ITSD Open Sy Re: RANDOMDEV inspired realitycheck regarding i386/i486... 36. Nov 15 Wilko Bulte Re: RANDOMDEV inspired realitycheck regarding i386/i486... 37. Nov 15 Cy Schubert Re: RANDOMDEV inspired realitycheck regarding i386/i486... 38. Nov 15 Sheldon Hearn Re: RANDOMDEV inspired realitycheck regarding i386/i486... 39. Nov 15 Wilko Bulte Re: RANDOMDEV inspired realitycheck regarding i386/i486... 40. Nov 15 Randell Jesup Re: RANDOMDEV inspired realitycheck regarding i386/i486...
41. Nov 15 Andre Oppermann Re: Green/Yellow/Red state for the VM system. 42. Nov 15 Will Andrews Re: Turning on debugging in GENERIC 43. Nov 15 Mark Murray Re: RANDOMDEV inspired realitycheck regarding i386/i486... 44. Nov 15 Sheldon Hearn Re: Turning on debugging in GENERIC 45. Nov 16 Terry Lambert Re: Turning on debugging in GENERIC 46. Nov 16 Sheldon Hearn Re: Turning on debugging in GENERIC 47. Nov 16 Terry Lambert Re: Turning on debugging in GENERIC 48. Nov 16 Sheldon Hearn Re: Turning on debugging in GENERIC 49. Nov 16 Nate Williams Re: Turning on debugging in GENERIC 50. Nov 16 Alfred Perlstein potentially simpler approach than scheduler activations. 51. Nov 16 David O'Brien Re: RANDOMDEV inspired realitycheck regarding i386/i486... 52. Nov 16 Cy Schubert Re: RANDOMDEV inspired realitycheck regarding i386/i486... 53. Nov 16 Warner Losh Re: RANDOMDEV inspired realitycheck regarding i386/i486... 54. Nov 16 Warner Losh Re: RANDOMDEV inspired realitycheck regarding i386/i486... 55. Nov 16 Matthew Jacob Re: RANDOMDEV inspired realitycheck regarding i386/i486... 56. Nov 16 Warner Losh Re: RANDOMDEV inspired realitycheck regarding i386/i486... 57. Nov 16 Terry Lambert Re: Turning on debugging in GENERIC 58. Nov 16 Nate Williams Re: Turning on debugging in GENERIC 59. Nov 16 Wes Peters Re: RANDOMDEV inspired realitycheck regarding i386/i486... 60. Nov 16 frank xu Re: potentially simpler approach than scheduler activations.
61. Nov 16 frank xu Re: potentially simpler approach than scheduler activations. 62. Nov 16 Alfred Perlstein Re: potentially simpler approach than scheduler activations. 63. Nov 16 Garrett Rooney Re: potentially simpler approach than scheduler activations. 64. Nov 16 Garrett Rooney Re: potentially simpler approach than scheduler activations. 65. Nov 16 Alfred Perlstein Re: potentially simpler approach than scheduler activations. 66. Nov 16 Garrett Rooney Re: potentially simpler approach than scheduler activations. 67. Nov 16 Mark Murray new monotime() call for all architectures. 68. Nov 16 Poul-Henning Kamp Re: new monotime() call for all architectures. 69. Nov 17 Kenjiro Cho Re: new monotime() call for all architectures. 70. Nov 17 John Hay Re: new monotime() call for all architectures. 71. Nov 17 Eivind Eklund Re: Turning on debugging in GENERIC 72. Nov 17 Andrew Gallatin Re: potentially simpler approach than scheduler activations. 73. Nov 17 Dag-Erling Smorgrav Re: RANDOMDEV inspired realitycheck regarding i386/i486... 74. Nov 17 Poul-Henning Kamp Re: RANDOMDEV inspired realitycheck regarding i386/i486... 75. Nov 17 Brian Dean Re: updating rdist 76. Nov 17 David O'Brien Re: potentially simpler approach than scheduler activations. 77. Nov 17 John Baldwin Re: updating rdist 78. Nov 17 John Baldwin Re: new monotime() call for all architectures. 79. Nov 17 John Baldwin RE: new monotime() call for all architectures. 80. Nov 17 Matthew Jacob RE: new monotime() call for all architectures.
81. Nov 17 John Hay Re: new monotime() call for all architectures. 82. Nov 17 John Baldwin Re: new monotime() call for all architectures. 83. Nov 17 Terry Lambert Re: RANDOMDEV inspired realitycheck regarding i386/i486... 84. Nov 17 Poul-Henning Kamp Re: new monotime() call for all architectures. 85. Nov 17 John Baldwin Re: RANDOMDEV inspired realitycheck regarding i386/i486... 86. Nov 17 John Baldwin Re: new monotime() call for all architectures. 87. Nov 17 Matthew D. Fuller Re: new monotime() call for all architectures. 88. Nov 17 Poul-Henning Kamp Re: new monotime() call for all architectures. 89. Nov 17 Jordan Hubbard "Hi, we're the new core team" 90. Nov 17 Poul-Henning Kamp Re: new monotime() call for all architectures. 91. Nov 17 Nate Williams Re: new monotime() call for all architectures. 92. Nov 17 Jonathan Lemon Re: new monotime() call for all architectures. 93. Nov 17 John Baldwin Re: new monotime() call for all architectures. 94. Nov 17 Julian Elischer Threads (KSE etc) comments 95. Nov 17 Sue Blake Re: updating rdist 96. Nov 17 Mark Murray Re: new monotime() call for all architectures. 97. Nov 17 Mark Murray Re: new monotime() call for all architectures. 98. Nov 17 Mark Murray Re: new monotime() call for all architectures. 99. Nov 17 Jean-Marc Zucconi Re: new monotime() call for all architectures. 100. Nov 17 Matthew Jacob RE: new monotime() call for all architectures.
101. Nov 17 Warner Losh Re: new monotime() call for all architectures. 102. Nov 17 Daniel Eischen RE: new monotime() call for all architectures. 103. Nov 17 Peter Dufault Re: new monotime() call for all architectures. 104. Nov 17 Greg Lehey Re: potentially simpler approach than scheduler activations. 105. Nov 17 Wes Peters Re: new monotime() call for all architectures. 106. Nov 17 Wes Peters Re: RANDOMDEV inspired realitycheck regarding i386/i486... 107. Nov 17 Wes Peters Re: RANDOMDEV inspired realitycheck regarding i386/i486... 108. Nov 17 Wes Peters Re: RANDOMDEV inspired realitycheck regarding i386/i486... 109. Nov 17 John Hay Re: new monotime() call for all architectures. 110. Nov 17 Mike Smith Re: new monotime() call for all architectures. 111. Nov 18 Mark Murray Re: new monotime() call for all architectures. 112. Nov 18 Alfred Perlstein Re: potentially simpler approach than scheduler activations. 113. Nov 18 Mark Murray "Monotonic" counter/register call - commit candidate. 114. Nov 18 Daniel Eischen Re: "Monotonic" counter/register call - commit candidate. 115. Nov 18 Mike Smith Re: "Monotonic" counter/register call - commit candidate. 116. Nov 18 Mark Murray Re: "Monotonic" counter/register call - commit candidate. 117. Nov 18 Daniel Eischen Re: "Monotonic" counter/register call - commit candidate. 118. Nov 18 Mark Murray Re: "Monotonic" counter/register call - commit candidate. 119. Nov 18 Wilko Bulte Re: "Monotonic" counter/register call - commit candidate. 120. Nov 18 Bruce Evans RE: new monotime() call for all architectures.
121. Nov 18 Mark Murray Re: new monotime() call for all architectures. 122. Nov 18 Bruce Evans Re: "Monotonic" counter/register call - commit candidate. 123. Nov 18 Mark Murray Re: "Monotonic" counter/register call - commit candidate. 124. Nov 18 Bruce Evans Re: new monotime() call for all architectures. 125. Nov 18 Bruce Evans Re: "Monotonic" counter/register call - commit candidate. 126. Nov 18 Mark Murray Re: new monotime() call for all architectures. 127. Nov 18 Mark Murray Re: "Monotonic" counter/register call - commit candidate.
home | archive sorted by: subject | author | date | reverse date