2009/freebsd-current/20090104.freebsd-current
Messages: 99, new messages first
|
Last update: Mon Feb 13 14:16:06 2023
|
|
home | archive sorted by: subject | author | date | reverse date
1. Jan 3 Vyacheslav Druzhinin Re: RFC: new utility, kmodpatch 2. Jan 3 Jos Backus Re: Changed names of logical disks on recent -CURRENT: part of logical disks not accessible now 3. Jan 3 Thomas Sparrevohn Re: panic on (hdd)load 4. Jan 3 Thomas Sparrevohn Re: panic on (hdd)load 5. Jan 3 Giorgos Keramidas Re: Tracking the open USB2 issues? 6. Jan 3 Garrett Cooper Re: Weird arrow key disappearing act with latest syscons 7. Jan 3 Ed Schouten Re: Weird arrow key disappearing act with latest syscons 8. Jan 3 Marcel Moolenaar Re: gjournal is not automounted any more 9. Jan 3 Ed Schouten Re: Weird arrow key disappearing act with latest syscons 10. Jan 3 Garrett Cooper Weird arrow key disappearing act with latest syscons 11. Jan 3 Max Laier Re: RFC: new utility, kmodpatch 12. Jan 3 dvg_lab Re: RFC: new utility, kmodpatch 13. Jan 3 Luigi Rizzo Re: RFC: new utility, kmodpatch 14. Jan 3 Alex Keda Re: RFC: new utility, kmodpatch 15. Jan 3 Uwe Grohnwaldt Re: panic on (hdd)load 16. Jan 3 M. Warner Losh Re: gjournal is not automounted any more 17. Jan 3 Paul B. Mahol Re: Can not build r186708 -CURRENT 18. Jan 3 Marcel Moolenaar Re: gjournal is not automounted any more 19. Jan 3 Marcel Moolenaar Re: New warning, what does it mean? 20. Jan 3 M. Warner Losh Re: gjournal is not automounted any more
21. Jan 3 Marcel Moolenaar Re: New warning, what does it mean? 22. Jan 3 Marcel Moolenaar Re: gjournal is not automounted any more 23. Jan 3 M. Warner Losh Re: New warning, what does it mean? 24. Jan 3 Marcel Moolenaar Re: New warning, what does it mean? 25. Jan 3 Christian Brueffer Re: CFT: altq support for pcn(4) 26. Jan 3 Alexey Ivanov Can not build r186708 -CURRENT 27. Jan 3 Marcel Moolenaar Re: Changed names of logical disks on recent -CURRENT: part of logical disks not accessible now 28. Jan 3 Christian Brueffer CFT: altq support for pcn(4) 29. Jan 3 Ed Schouten Re: kernel complaint about /dev/pts (maybe) 30. Jan 3 Robert Huff kernel complaint about /dev/pts (maybe) 31. Jan 3 Gary Jennejohn Re: RFC: new utility, kmodpatch 32. Jan 3 David O'Brien Re: New warning, what does it mean? 33. Jan 3 David O'Brien Re: build -j3 not working anymore on Current 34. Jan 3 M. Warner Losh Re: gjournal is not automounted any more 35. Jan 3 David O'Brien Re: gjournal is not automounted any more 36. Jan 3 Randy Bush hosts on bridged wlan can not reliably see each other 37. Jan 3 M. Warner Losh Re: gjournal is not automounted any more 38. Jan 3 M. Warner Losh Re: RFC: new utility, kmodpatch 39. Jan 3 David O'Brien Re: gjournal is not automounted any more 40. Jan 3 Thomas Sparrevohn Re: panic on (hdd)load
41. Jan 3 Hans Petter Selasky Re: panic on (hdd)load 42. Jan 3 Luigi Rizzo Re: RFC: new utility, kmodpatch 43. Jan 3 Uwe Grohnwaldt Re: panic on (hdd)load 44. Jan 3 Alfred Perlstein Re: HEADSUP usb2 (usb4bsd) to become default in 2 weeks. 45. Jan 2 =?ISO-8859-1?Q?Michael_T=F Re: SCTP related issue with recent ARP changes? 46. Jan 2 M. Warner Losh Re: RFC: new utility, kmodpatch 47. Jan 2 M. Warner Losh Re: HEADSUP usb2 (usb4bsd) to become default in 2 weeks. 48. Jan 2 Alfred Perlstein Re: HEADSUP usb2 (usb4bsd) to become default in 2 weeks. 49. Jan 2 Uwe Grohnwaldt Re: panic on (hdd)load 50. Jan 2 Joe Marcus Clarke Re: hald and USB2 51. Jan 2 Pegasus Mc Cleaft hald and USB2 52. Jan 2 Li, Qing RE: SCTP related issue with recent ARP changes? 53. Jan 2 Luigi Rizzo Re: RFC: new utility, kmodpatch 54. Jan 2 Uwe Grohnwaldt Re: panic on (hdd)load 55. Jan 2 Uwe Grohnwaldt panic on (hdd)load 56. Jan 2 Luigi Rizzo Re: RFC: new utility, kmodpatch 57. Jan 2 M. Warner Losh Re: HEADSUP usb2 (usb4bsd) to become default in 2 weeks. [usb2 configuration] 58. Jan 2 M. Warner Losh Re: HEADSUP usb2 (usb4bsd) to become default in 2 weeks. [usb2 configuration] 59. Jan 2 M. Warner Losh Re: HEADSUP usb2 (usb4bsd) to become default in 2 weeks. 60. Jan 2 M. Warner Losh New warning, what does it mean?
61. Jan 2 M. Warner Losh Re: RFC: new utility, kmodpatch 62. Jan 2 M. Warner Losh Re: gjournal is not automounted any more 63. Jan 2 M. Warner Losh Re: build -j3 not working anymore on Current 64. Jan 2 Arno J. Klaassen Re: 8-current: linux_dist-gentoo-stage3 wonn't bootstrap 65. Jan 2 Johan Hendriks RE: build -j3 not working anymore on Current 66. Jan 2 Johan Hendriks RE: build -j3 not working anymore on Current 67. Jan 2 Gary Palmer Re: build -j3 not working anymore on Current 68. Jan 2 Johan Hendriks RE: build -j3 not working anymore on Current 69. Jan 2 Gary Palmer Re: build -j3 not working anymore on Current 70. Jan 2 Johan Hendriks build -j3 not working anymore on Current 71. Jan 2 Boris Samorodov Re: gjournal is not automounted any more 72. Jan 2 David O'Brien Re: gjournal is not automounted any more 73. Jan 2 Joel Jacobson Re: gstripe performance oddity 74. Jan 2 Maxim Sobolev Re: gstripe performance oddity 75. Jan 2 Ken Smith Warning about uid values larger than 16-bit... 76. Jan 2 Ben Kaduk Re: RFC: new utility, kmodpatch 77. Jan 1 Christoph Mallon Re: RFC: new utility, kmodpatch 78. Jan 1 Joel Jacobson gstripe performance oddity 79. Jan 1 Christoph Mallon Re: RFC: new utility, kmodpatch 80. Jan 1 Li, Qing RE: SCTP related issue with recent ARP changes?
81. Jan 1 Oliver Pinter Re: RFC: new utility, kmodpatch 82. Jan 1 Alex Keda Re: RFC: new utility, kmodpatch 83. Jan 1 Luigi Rizzo RFC: new utility, kmodpatch 84. Jan 1 Philipp Ost LORs in recent -current 85. Jan 1 Max Laier Re: tar/libarchive gzip problem [was: portsnap corrupted] 86. Jan 1 Ed Schouten VT100/xterm-support for syscons(4) committed to SVN 87. Jan 1 FreeBSD Tinderbox [head tinderbox] failure on i386/i386 88. Jan 1 FreeBSD Tinderbox [head tinderbox] failure on amd64/amd64 89. Jan 1 Hans Petter Selasky Re: Call for axe(4) testers. 90. Jan 1 FreeBSD Tinderbox [head tinderbox] failure on sparc64/sun4v 91. Jan 1 Simon L. Nielsen Re: tar/libarchive gzip problem [was: portsnap corrupted] 92. Jan 1 FreeBSD Tinderbox [head tinderbox] failure on sparc64/sparc64 93. Jan 1 FreeBSD Tinderbox [head tinderbox] failure on powerpc/powerpc 94. Jan 1 FreeBSD Tinderbox [head tinderbox] failure on ia64/ia64 95. Jan 1 FreeBSD Tinderbox [head tinderbox] failure on i386/pc98 96. Jan 1 FreeBSD Tinderbox [head tinderbox] failure on i386/i386 97. Jan 1 FreeBSD Tinderbox [head tinderbox] failure on amd64/amd64 98. Jan 1 Jos Backus Re: Changed names of logical disks on recent -CURRENT: part of logical disks not accessible now 99. Jan 1 Tim Kientzle Re: tar/libarchive gzip problem [was: portsnap corrupted]
home | archive sorted by: subject | author | date | reverse date