Skip site navigation (1)Skip section navigation (2)


1996/freebsd-current/19960204.freebsd-current

Messages: 190, sorted by subject
Last page update: Sat Jan 3 13:06:32 UTC 2026

home | up | archive | sorted by: subject - author - date - reverse date
  1. Feb  4 The Amazing Big Guy        -current build problems
  2. Feb  5 Terry Lambert               Re: -current build problems
  3. Feb  6 Andreas S. Wetzel          -current: silo overflows ?
  4. Feb  7 Steve Passe                2.2-960130-SNAP experiences
  5. Feb  8 J Wunsch                    Re: 2.2-960130-SNAP experiences
  6. Feb  9 Jordan K. Hubbard           Re: 2.2-960130-SNAP experiences
  7. Feb  9 Steve Passe                 Re: 2.2-960130-SNAP experiences
  8. Feb  9 Steve Passe                 Re: 2.2-960130-SNAP experiences
  9. Feb  9 Jordan K. Hubbard           Re: 2.2-960130-SNAP experiences
 10. Feb 10 Steve Passe                 Re: 2.2-960130-SNAP experiences
 11. Feb  7 John Soward                7880 driver in SNAP
 12. Feb  7 Rodney W. Grimes            Re: 7880 driver in SNAP
 13. Feb  7 Daniel M. Eischen           Re: 7880 driver in SNAP
 14. Feb  7 Justin T. Gibbs             Re: 7880 driver in SNAP
 15. Feb  5 Wayne Scott                Anyone using AMD with -current?
 16. Feb  6 Garrett A. Wollman          Anyone using AMD with -current?
 17. Feb 10 Bruce Evans                calibrating clocks
 18. Feb  8 Sandy Kovshov              CCITT support in current
 19. Feb  8 Garrett A. Wollman          CCITT support in current
 20. Feb  8 Sandy Kovshov               Re: CCITT support in current

 21. Feb  8 Garrett A. Wollman          Re: CCITT support in current
 22. Feb  8 Julian Elischer             Re: CCITT support in current
 23. Feb  9 Poul-Henning Kamp           Re: CCITT support in current
 24. Feb  9 Jordan K. Hubbard           Re: CCITT support in current
 25. Feb  9 Jordan K. Hubbard           Re: CCITT support in current
 26. Feb  9 Sandy Kovshov               Re: CCITT support in current
 27. Feb  9 Sandy Kovshov               Re: CCITT support in current
 28. Feb  6 Gary Clark II <gclarkii@ma Change to RELNOTES/INSTALL NOTES
 29. Feb  7 Wolfram Schneider          Re: chown in bsd.doc.mk and bsd.info.mk
 30. Feb  6 Stephen McKay              Re: compiles hanging
 31. Feb  6 Stephen McKay               Re: compiles hanging
 32. Feb  4 Poul-Henning Kamp          Re: compiling the kernel with -O2
 33. Feb  7 Terry Lambert              CVS ISSUES
 34. Feb  7 Julian Elischer             Re: CVS ISSUES
 35. Feb  7 Terry Lambert               Re: CVS ISSUES
 36. Feb  8 Nate Williams               Re: CVS ISSUES
 37. Feb  8 Terry Lambert               Re: CVS ISSUES
 38. Feb  9 Garrett A. Wollman         devfs
 39. Feb 10 Peter Dufault              devfs persistence (was FSP:TNG)
 40. Feb  6 Stefan Esser               Re: FIXED: NCR problem until -stable

 41. Feb  6 Terry Lambert              FS PATCHES: THE NEXT GENERATION
 42. Feb  6 Julian Elischer             Re: FS PATCHES: THE NEXT GENERATION
 43. Feb  6 Terry Lambert               Re: FS PATCHES: THE NEXT GENERATION
 44. Feb  6 Julian Elischer             Re: FS PATCHES: THE NEXT GENERATION
 45. Feb  6 Terry Lambert               Re: FS PATCHES: THE NEXT GENERATION
 46. Feb  6 Julian Elischer             Re: FS PATCHES: THE NEXT GENERATION
 47. Feb  6 Terry Lambert               Re: FS PATCHES: THE NEXT GENERATION
 48. Feb  6 Rodney W. Grimes            Re: FS PATCHES: THE NEXT GENERATION
 49. Feb  7 J Wunsch                    Re: FS PATCHES: THE NEXT GENERATION
 50. Feb  7 Bill Fenner                 Re: FS PATCHES: THE NEXT GENERATION
 51. Feb  7 Terry Lambert               Re: FS PATCHES: THE NEXT GENERATION
 52. Feb  7 John Polstra                Re: FS PATCHES: THE NEXT GENERATION
 53. Feb  8 Lutz Albers                 Re: FS PATCHES: THE NEXT GENERATION
 54. Feb  8 Terry Lambert               Re: FS PATCHES: THE NEXT GENERATION
 55. Feb  9 Lutz Albers                 Re: FS PATCHES: THE NEXT GENERATION
 56. Feb  9 Jordan K. Hubbard           Re: FS PATCHES: THE NEXT GENERATION
 57. Feb  9 Poul-Henning Kamp           Re: FS PATCHES: THE NEXT GENERATION
 58. Feb  9 Jordan K. Hubbard           Re: FS PATCHES: THE NEXT GENERATION
 59. Feb  9 Terry Lambert               Re: FS PATCHES: THE NEXT GENERATION
 60. Feb  9 Terry Lambert               Re: FS PATCHES: THE NEXT GENERATION

 61. Feb  9 Ollivier Robert             Re: FS PATCHES: THE NEXT GENERATION
 62. Feb  9 Scott Blachowicz            Re: FS PATCHES: THE NEXT GENERATION
 63. Feb  9 Terry Lambert               Re: FS PATCHES: THE NEXT GENERATION
 64. Feb  9 Julian Elischer             Re: FS PATCHES: THE NEXT GENERATION
 65. Feb  9 Julian Elischer             Re: FS PATCHES: THE NEXT GENERATION
 66. Feb  9 Terry Lambert               Re: FS PATCHES: THE NEXT GENERATION
 67. Feb  9 Jordan K. Hubbard           Re: FS PATCHES: THE NEXT GENERATION
 68. Feb  9 Jordan K. Hubbard           Re: FS PATCHES: THE NEXT GENERATION
 69. Feb  9 Terry Lambert               Re: FS PATCHES: THE NEXT GENERATION
 70. Feb  9 Ollivier Robert             Re: FS PATCHES: THE NEXT GENERATION
 71. Feb  9 Julian Elischer             Re: FS PATCHES: THE NEXT GENERATION
 72. Feb  9 Jordan K. Hubbard           Re: FS PATCHES: THE NEXT GENERATION
 73. Feb  9 Jordan K. Hubbard           Re: FS PATCHES: THE NEXT GENERATION
 74. Feb  9 Terry Lambert               Re: FS PATCHES: THE NEXT GENERATION
 75. Feb  9 Rodney W. Grimes            Re: FS PATCHES: THE NEXT GENERATION
 76. Feb  9 Kent Hamilton               Re: FS PATCHES: THE NEXT GENERATION
 77. Feb  9 Jordan K. Hubbard           Re: FS PATCHES: THE NEXT GENERATION
 78. Feb  9 Jordan K. Hubbard           Re: FS PATCHES: THE NEXT GENERATION
 79. Feb 10 Terry Lambert               Re: FS PATCHES: THE NEXT GENERATION
 80. Feb 10 Terry Lambert               Re: FS PATCHES: THE NEXT GENERATION

 81. Feb 10 Terry Lambert               Re: FS PATCHES: THE NEXT GENERATION
 82. Feb 10 Julian Elischer             Re: FS PATCHES: THE NEXT GENERATION
 83. Feb 10 Terry Lambert               Re: FS PATCHES: THE NEXT GENERATION
 84. Feb 10 Jordan K. Hubbard           Re: FS PATCHES: THE NEXT GENERATION
 85. Feb 10 Terry Lambert               Re: FS PATCHES: THE NEXT GENERATION
 86. Feb 10 Terry Lambert               Re: FS PATCHES: THE NEXT GENERATION
 87. Feb 10 Julian Elischer             Re: FS PATCHES: THE NEXT GENERATION
 88. Feb 10 Jordan K. Hubbard           Re: FS PATCHES: THE NEXT GENERATION
 89. Feb  7 Андрей Чернов (aka Andrey  Hang with sys_pipe 1.9
 90. Feb  9 invalid opcode             How
 91. Feb  9 Terry Lambert               Re: How
 92. Feb  9 Warner Losh                 Re: How
 93. Feb 10 Wayne Scott                 Re: How
 94. Feb 10 Terry Lambert               Re: How
 95. Feb 10 Terry Lambert               Re: How
 96. Feb 10 Warner Losh                 Re: How
 97. Feb 10 Terry Lambert               Re: How
 98. Feb 10 Ollivier Robert             Re: How
 99. Feb 10 Heikki Suonsivu             Re: How
100. Feb  6 Michael Smith              Initial 2.2-SNAP experiences...

101. Feb  9 Jordan K. Hubbard           Re: Initial 2.2-SNAP experiences...
102. Feb  9 Poul-Henning Kamp           Re: Initial 2.2-SNAP experiences...
103. Feb  9 Андрей Чернов (aka Andrey  Kerberos @ freebsd.org?
104. Feb  9 Warner Losh                 Re: Kerberos @ freebsd.org?
105. Feb  9 Dima Ruban                  Re: Kerberos @ freebsd.org?
106. Feb  9 Warner Losh                 Re: Kerberos @ freebsd.org?
107. Feb  9 Mark Murray                 Re: Kerberos @ freebsd.org?
108. Feb  9 Mark Murray                 Re: Kerberos @ freebsd.org?
109. Feb  9 Mark Murray                 Re: Kerberos @ freebsd.org?
110. Feb 10 Paul Traina                 Re: Kerberos @ freebsd.org?
111. Feb 10 Warner Losh                 Re: Kerberos @ freebsd.org?
112. Feb 10 Garrett A. Wollman          Re: Kerberos @ freebsd.org?
113. Feb 10 Louis A. Mamakos            Re: Kerberos @ freebsd.org?
114. Feb 10 Ollivier Robert             Re: Kerberos @ freebsd.org?
115. Feb 10 Warner Losh                 Re: Kerberos @ freebsd.org?
116. Feb 10 Paul Traina                 Re: Kerberos @ freebsd.org?
117. Feb 10 Warner Losh                 Re: Kerberos @ freebsd.org?
118. Feb 10 Dima Ruban                  Re: Kerberos @ freebsd.org?
119. Feb 10 Mark Murray                 Re: Kerberos @ freebsd.org?
120. Feb  4 KATO Takenori              kmem_malloc called at splimp

121. Feb  4 David Greenman              Re: kmem_malloc called at splimp
122. Feb  5 Stefan Esser               Lost some mail ...
123. Feb 10 Jean-Marc Zucconi          make world do not complete
124. Feb  5 Marty Leisner              Re: make world with -fomit-frame-pointer
125. Feb  5 Marty Leisner               Re: make world with -fomit-frame-pointer
126. Feb  5 David Greenman              Re: make world with -fomit-frame-pointer
127. Feb  5 Bruce Evans                 Re: make world with -fomit-frame-pointer
128. Feb  5 Bruce Evans                 Re: make world with -fomit-frame-pointer
129. Feb  6 Marty Leisner               Re: make world with -fomit-frame-pointer
130. Feb  8 KATO Takenori              missing imp.h
131. Feb  4 Paul Richards              missing subdirs
132. Feb  5 Peter Wemm                  Re: missing subdirs
133. Feb  6 Chien-Ta Lee               new pipe is broken (Feb-6)
134. Feb  6 Michael Smith               Re: new pipe is broken (Feb-6)
135. Feb  6 Chien-Ta Lee                Re: new pipe is broken (Feb-6)
136. Feb  6 John Dyson <dyson>          Re: new pipe is broken (Feb-6)
137. Feb  7 Chien-Ta Lee                Re: new pipe is broken (Feb-6)
138. Feb  9 Satoshi Asami               Re: new pipe is broken (Feb-6)
139. Feb  9 Chien-Ta Lee                Re: new pipe is broken (Feb-6)
140. Feb  9 Satoshi Asami               Re: new pipe is broken (Feb-6)

141. Feb  9 John S. Dyson               Re: new pipe is broken (Feb-6)
142. Feb  6 invalid opcode             Please don't shoot me for asking this stupid question.
143. Feb  6 invalid opcode             Please don't shoot me for asking this stupid question. (fwd)
144. Feb  7 Terry Lambert               Re: Please don't shoot me for asking this stupid question. (fwd)
145. Feb  4 Andreas Klemm              Re: SB16 & Current
146. Feb  4 Daniel Baker                Re: SB16 & Current
147. Feb  4 Andreas Klemm               Re: SB16 & Current
148. Feb  4 Daniel Baker                Re: SB16 & Current
149. Feb  4 Andreas S. Wetzel           Re: SB16 & Current
150. Feb  4 Philippe Regnauld           Re: SB16 & Current
151. Feb  5 Frank Durda IV             Re: sup%d is broken - I agree
152. Feb  5 Paul Traina                 Re: sup%d is broken - I agree
153. Feb  5 Jordan K. Hubbard           Re: sup%d is broken - I agree
154. Feb  6 Paul Traina                 Re: sup%d is broken - I agree
155. Feb  6 Richard Wackerbarth         Re: sup%d is broken - I agree
156. Feb  6 Frank Durda IV              Re: sup%d is broken - I agree
157. Feb  6 Justin T. Gibbs             Re: sup%d is broken - I agree
158. Feb  6 John Polstra                Re: sup%d is broken - I agree
159. Feb  6 Frank Durda IV              Re: sup%d is broken - I agree
160. Feb  6 Frank Durda IV              Re: sup%d is broken - I agree

161. Feb  6 invalid opcode              Re: sup%d is broken - I agree
162. Feb  6 Justin T. Gibbs             Re: sup%d is broken - I agree
163. Feb  6 Justin T. Gibbs             Re: sup%d is broken - I agree
164. Feb  7 michael butler              Re: sup%d is broken - I agree
165. Feb  7 Garrett A. Wollman          Re: sup%d is broken - I agree
166. Feb  9 Jordan K. Hubbard           Re: sup%d is broken - I agree
167. Feb  4 Terry Lambert              SUP, config, and opt_sysvipc.h
168. Feb  7 Adam David                 TCP/IP interoperability problem, workaround
169. Feb  8 Andras Olah                 Re: TCP/IP interoperability problem, workaround
170. Feb  8 Adam David                  Re: TCP/IP interoperability problem, workaround
171. Feb  8 Garrett A. Wollman          TCP/IP interoperability problem, workaround
172. Feb  8 Adam David                  Re: TCP/IP interoperability problem, workaround
173. Feb  9 Garrett A. Wollman          Re: TCP/IP interoperability problem, workaround
174. Feb  6 Andreas S. Wetzel          Tired of "isa_dmadone_nobounce" messages
175. Feb  6 Michael Smith               Re: Tired of "isa_dmadone_nobounce" messages
176. Feb  6 Andreas S. Wetzel           Re: Tired of "isa_dmadone_nobounce" messages
177. Feb  6 Michael Smith               Re: Tired of "isa_dmadone_nobounce" messages
178. Feb  6 Michael Smith               Re: Tired of "isa_dmadone_nobounce" messages
179. Feb  6 Julian Elischer             Re: Tired of "isa_dmadone_nobounce" messages
180. Feb  7 J Wunsch                    Re: Tired of "isa_dmadone_nobounce" messages

181. Feb  7 J Wunsch                    Re: Tired of "isa_dmadone_nobounce" messages
182. Feb  7 Andreas S. Wetzel           Re: Tired of "isa_dmadone_nobounce" messages
183. Feb  7 Jim Lowe                    Re: Tired of "isa_dmadone_nobounce" messages
184. Feb  8 Andreas S. Wetzel           Re: Tired of "isa_dmadone_nobounce" messages
185. Feb  8 Michael Smith               Re: Tired of "isa_dmadone_nobounce" messages
186. Feb  8 Andreas S. Wetzel           Re: Tired of "isa_dmadone_nobounce" messages
187. Feb  6 Chris Wiener               Re: Tired of isa_dmadone_nobounce messages
188. Feb  7 J Wunsch                    Re: Tired of isa_dmadone_nobounce messages
189. Feb  5 Ollivier Robert            Wired memory
190. Feb  5 David Greenman              Re: Wired memory

home | up | archive | sorted by: subject - author - date - reverse date