1996/freebsd-current/19960107.freebsd-current
Messages: 98, sorted by subject
|
Last page update: Sat Jan 3 13:06:31 UTC 2026
|
|
home | up | archive | sorted by: subject - author - date - reverse date
1. Jan 7 Stefan Esser Re: -current kernel problems 2. Jan 7 -Vince- Re: -current kernel problems 3. Jan 7 Stefan Esser Re: -current kernel problems 4. Jan 7 -Vince- Re: -current kernel problems 5. Jan 8 -Vince- Re: -current kernel problems 6. Jan 9 Stefan Esser Re: -current kernel problems 7. Jan 9 -Vince- Re: -current kernel problems 8. Jan 9 -Vince- -current problem 9. Jan 10 Stefan Esser Re: -current problem 10. Jan 11 John Birrell /usr/src/lib/libc/net/getnetbyaddr.c 11. Jan 12 sycheng@cis.ufl.edu [HELP] cannot start X window 12. Jan 7 J Wunsch `make release' almost through 13. Jan 7 Chuck Robey Re: `make release' almost through 14. Jan 7 J Wunsch Re: `make release' almost through 15. Jan 7 Jordan K. Hubbard Re: `make release' almost through 16. Jan 8 J Wunsch Re: `make release' almost through 17. Jan 9 J Wunsch `make release' saga 18. Jan 13 J Wunsch Re: A few NITS about SCSI Tapes 19. Jan 9 Warner Losh Any idea how to ... 20. Jan 9 J Wunsch Re: Any idea how to ...
21. Jan 9 Bruce Evans Re: Any idea how to ... 22. Jan 9 Michael Smith Bootstrapping -current from 2.1, observations 23. Jan 9 Julian H. Stacey Re: conf.c and USL copyright at top 24. Jan 8 Satoshi Asami Re: Current is looking more stable these days..? 25. Jan 8 Jordan K. Hubbard Re: Current is looking more stable these days..? 26. Jan 9 Satoshi Asami Re: Current is looking more stable these days..? 27. Jan 10 rcw@delphos.la.asu.edu Re: current-digest V1 #198 28. Jan 10 J Wunsch Re: current-digest V1 #198 29. Jan 9 Terry Lambert dead list test 30. Jan 7 James FitzGibbon Disposition of unknown PCI ethernet solved 31. Jan 8 Michael Smith Re: Disposition of unknown PCI ethernet solved 32. Jan 8 David Greenman Re: Disposition of unknown PCI ethernet solved 33. Jan 8 Michael Smith Re: Disposition of unknown PCI ethernet solved 34. Jan 8 David Greenman Re: Disposition of unknown PCI ethernet solved 35. Jan 8 J Wunsch Re: Disposition of unknown PCI ethernet solved 36. Jan 8 Stefan Esser Re: Disposition of unknown PCI ethernet solved 37. Jan 8 Michael Smith Re: Disposition of unknown PCI ethernet solved 38. Jan 8 Satoshi Asami Re: Disposition of unknown PCI ethernet solved 39. Jan 9 Bruce Evans Re: Disposition of unknown PCI ethernet solved 40. Jan 7 John Birrell Ethernet packet loss
41. Jan 13 Adam Hawks finger problem going from 2.1R to -current 42. Jan 10 James Leppek general protection faults in current 43. Jan 8 J Wunsch Good News :) 44. Jan 9 Thomas Graichen Re: Good News :) 45. Jan 9 J Wunsch Re: Good News :) 46. Jan 9 J Wunsch Re: Good News :) 47. Jan 13 Sujal Patel ktrace causes vm_page_free: freeing busy page 48. Jan 11 Andras Olah Re: m_copydata panic & tcp_extensions: the full analysis 49. Jan 11 Gang-Ryung Uh make all 50. Jan 12 Ollivier Robert Re: make all 51. Jan 9 Gang-Ryung Uh make world 52. Jan 9 J Wunsch Re: make world 53. Jan 10 Ollivier Robert Re: make world 54. Jan 10 J Wunsch Re: make world 55. Jan 10 John Polstra Re: make world 56. Jan 10 Bruce Evans Re: make world 57. Jan 11 J Wunsch Re: make world 58. Jan 11 John Polstra Re: make world 59. Jan 7 Thomas Graichen Re: manpath.conf 60. Jan 10 KATO Takenori MAXBSIZE
61. Jan 9 Jim Lowe Overloaded PRINTER variable in bsd.doc.mk? 62. Jan 10 John Fieber Re: Overloaded PRINTER variable in bsd.doc.mk? 63. Jan 12 Satoshi Asami Re: Overloaded PRINTER variable in bsd.doc.mk? 64. Jan 13 Ollivier Robert Panic at ahb probe time 65. Jan 13 Justin T. Gibbs Re: Panic at ahb probe time 66. Jan 12 Mark Diekhans Problem compiling current 67. Jan 10 Kent Hauser problem with `sup' server? 68. Jan 7 Jordan K. Hubbard Prognosis of 2.2-960107-SNAP 69. Jan 7 Jake Hamby Re: Prognosis of 2.2-960107-SNAP 70. Jan 7 Jordan K. Hubbard Re: Prognosis of 2.2-960107-SNAP 71. Jan 7 Jordan K. Hubbard Re: Prognosis of 2.2-960107-SNAP 72. Jan 7 Marc G. Fournier Re: Prognosis of 2.2-960107-SNAP 73. Jan 7 Jordan K. Hubbard Re: Prognosis of 2.2-960107-SNAP 74. Jan 8 Bruce Evans Re: Prognosis of 2.2-960107-SNAP 75. Jan 8 Marc G. Fournier Re: Prognosis of 2.2-960107-SNAP 76. Jan 8 J Wunsch Re: Prognosis of 2.2-960107-SNAP 77. Jan 8 J Wunsch Re: Prognosis of 2.2-960107-SNAP 78. Jan 8 Paul Richards Re: Prognosis of 2.2-960107-SNAP 79. Jan 8 Jordan K. Hubbard Re: Prognosis of 2.2-960107-SNAP 80. Jan 8 Poul-Henning Kamp Re: Prognosis of 2.2-960107-SNAP
81. Jan 8 Terry Lambert Re: Prognosis of 2.2-960107-SNAP 82. Jan 8 Satoshi Asami Re: Prognosis of 2.2-960107-SNAP 83. Jan 9 marino.ladavac@aut.alcatel Re: Prognosis of 2.2-960107-SNAP 84. Jan 9 Jonathan M. Bresler Re: Prognosis of 2.2-960107-SNAP 85. Jan 9 Paul Richards Re: Prognosis of 2.2-960107-SNAP 86. Jan 9 Jonathan M. Bresler Re: Prognosis of 2.2-960107-SNAP 87. Jan 9 Satoshi Asami Re: Prognosis of 2.2-960107-SNAP 88. Jan 9 Satoshi Asami Re: Prognosis of 2.2-960107-SNAP 89. Jan 9 Jonathan M. Bresler Re: Prognosis of 2.2-960107-SNAP 90. Jan 7 Justin T. Gibbs Softc changes in teh SCSI code 91. Jan 8 Jordan K. Hubbard Syncing CTM and SNAPS? 92. Jan 9 Poul-Henning Kamp Re: Syncing CTM and SNAPS? 93. Jan 9 Richard Wackerbarth Re: Syncing CTM and SNAPS? 94. Jan 9 Jordan K. Hubbard Re: Syncing CTM and SNAPS? 95. Jan 9 Poul-Henning Kamp Re: Syncing CTM and SNAPS? 96. Jan 9 Richard Wackerbarth Re: Syncing CTM and SNAPS? 97. Jan 9 Poul-Henning Kamp Re: Syncing CTM and SNAPS? 98. Jan 10 Philippe Regnauld Watch (using snoop) command does not take CTRL-C anymore
home | up | archive | sorted by: subject - author - date - reverse date