freebsd-current  

Messages by Thread

• • Re: rtld messing up? John Polstra
  • Re: rtld messing up? Mark Murray
  • Re: rtld messing up? Miguel Mendez
  • Re: rtld messing up? Mark Murray
  • Re: rtld messing up? Darryl Okahata
  • Re: rtld messing up? Darryl Okahata
• Warnings in my bootup (dmesg.boot) Hiten Pandya
  • Re: Warnings in my bootup (dmesg.boot) Terry Lambert
  • Re: Warnings in my bootup (dmesg.boot) Hiten Pandya
  • Re: Warnings in my bootup (dmesg.boot) Terry Lambert
• panics with CardBus Michal Mertl
  • Re: panics with CardBus Gavin Atkinson
  • Re: panics with CardBus M. Warner Losh
  • Re: panics with CardBus Gavin Atkinson
  • Re: panics with CardBus M. Warner Losh
  • Re: panics with CardBus Gavin Atkinson
• 4-5 REL -> 5.0 CUR Jan Stocker
  • Re: 4-5 REL -> 5.0 CUR Sergey A. Osokin
  • Re: 4-5 REL -> 5.0 CUR Makoto Matsushita
  • RE: 4-5 REL -> 5.0 CUR Jan Stocker
• ping with usec resolution Christoph Kukulies
  • Re: ping with usec resolution David Greenman
  • Re: ping with usec resolution Christoph Kukulies
  • Re: ping with usec resolution Terry Lambert
  • Re: ping with usec resolution Christoph Kukulies
• IS YOUR WEB SITE BEING SEEN? IMPORTANT MESSAGE
  • IS YOUR WEB SITE BEING SEEN? IMPORTANT MESSAGE
• Package set for release media Murray Stokely
• [no subject] Liu Siwei
• [no subject] Liu Siwei
• error message Thierry Herbelot
  • Re: error message Terry Lambert
• slight patch to ata-all.c Thierry Herbelot
• b_to_q to a clist with no reserved cblocks Robert Watson
  • Re: b_to_q to a clist with no reserved cblocks Bruce Evans
  • Re: b_to_q to a clist with no reserved cblocks Bill Fenner
• GEOM code ready for testing Poul-Henning Kamp
  • Re: GEOM code ready for testing Carl Makin
  • Re: GEOM code ready for testing Poul-Henning Kamp
  • Re: GEOM code ready for testing Rasmus Skaarup
  • Re: GEOM code ready for testing Poul-Henning Kamp
  • Re: GEOM code ready for testing Rasmus Skaarup
  • Re: GEOM code ready for testing Poul-Henning Kamp
  • Re: GEOM code ready for testing Rasmus Skaarup
  • Re: GEOM code ready for testing Poul-Henning Kamp
  • Re: GEOM code ready for testing Doug White
  • Re: GEOM code ready for testing Dan Nelson
  • Re: GEOM code ready for testing Rasmus Skaarup
  • Re: GEOM code ready for testing Kenneth D. Merry
  • Re: GEOM code ready for testing Justin T. Gibbs
  • Re: GEOM code ready for testing Poul-Henning Kamp
• Serial break into debugger broken from 'cu' on -CURRENT? Robert Watson
  • Re: Serial break into debugger broken from 'cu' on -CURRENT? Wilko Bulte
  • Re: Serial break into debugger broken from 'cu' on -CURRENT? Mark Peek
  • Re: Serial break into debugger broken from 'cu' on -CURRENT? Wilko Bulte
  • Re: Serial break into debugger broken from 'cu' on -CURRENT? Christian Weisgerber
  • Re: Serial break into debugger broken from 'cu' on -CURRENT? Wilko Bulte
  • Re: Serial break into debugger broken from 'cu' on -CURRENT? Bernd Walter
  • Re: Serial break into debugger broken from 'cu' on -CURRENT? Vallo Kallaste
  • Re: Serial break into debugger broken from 'cu' on -CURRENT? Bruce Evans
  • Re: Serial break into debugger broken from 'cu' on -CURRENT? Joerg Wunsch
  • Re: Serial break into debugger broken from 'cu' on -CURRENT? Wilko Bulte
  • Re: Serial break into debugger broken from 'cu' on -CURRENT? Terry Lambert
  • Re: Serial break into debugger broken from 'cu' on -CURRENT? Christian Weisgerber
  • Re: Serial break into debugger broken from 'cu' on -CURRENT? Terry Lambert
  • Re: Serial break into debugger broken from 'cu' on -CURRENT? Glenn Gombert
  • Re: Serial break into debugger broken from 'cu' on -CURRENT? Julian Elischer
  • Re: Serial break into debugger broken from 'cu' on -CURRENT? Greg Lehey
  • Re: Serial break into debugger broken from 'cu' on -CURRENT? Bill Fenner
• A MUST for all IT-Executives! www.it-report.co.uk
• kern_linker.c rev. 1.75 and newer cause loading problem Steve Kargl
  • Re: kern_linker.c rev. 1.75 and newer cause loading problem Crist J. Clark
  • Re: kern_linker.c rev. 1.75 and newer cause loading problem Steve Kargl
  • Re: kern_linker.c rev. 1.75 and newer cause loading problem Maxim Sobolev
• gvim weird linkage Vallo Kallaste
  • Re: gvim weird linkage Jacques A. Vidrine
  • Re: gvim weird linkage Vallo Kallaste
  • Re: gvim weird linkage Simon Dick
  • Re: gvim weird linkage Vallo Kallaste
  • Re: gvim weird linkage Olivier Houchard
  • Re: gvim weird linkage Vallo Kallaste
  • Re: gvim weird linkage - NOT ONLY Marcin CIEŚLAK
  • Re: gvim weird linkage - NOT ONLY Alexander Kabaev
  • Re: gvim weird linkage David O'Brien
  • Re: gvim weird linkage Vallo Kallaste
• New i386 5.0 packages uploaded (and toolchain problems) Kris Kennaway
  • Re: New i386 5.0 packages uploaded (and toolchain problems) David W. Chapman Jr.
  • Re: New i386 5.0 packages uploaded (and toolchain problems) David O'Brien
  • Re: New i386 5.0 packages uploaded (and toolchain problems) Kris Kennaway
  • Re: New i386 5.0 packages uploaded (and toolchain problems) David O'Brien
  • Re: New i386 5.0 packages uploaded (and toolchain problems) Kris Kennaway
  • Re: New i386 5.0 packages uploaded (and toolchain problems) Will Andrews
  • Re: New i386 5.0 packages uploaded (and toolchain problems) Robert Watson
  • Re: New i386 5.0 packages uploaded (and toolchain problems) Will Andrews
  • Re: New i386 5.0 packages uploaded (and toolchain problems) David O'Brien
• linprocfs.ko and kld loader problem? Steve Kargl
  • Re: linprocfs.ko and kld loader problem? Ollivier Robert
• == Feel & Look 10 Years Younger in 10 Weeks With HGH == 30151076 libertyHGH301510
  • == Feel & Look 10 Years Younger in 10 Weeks With HGH == 30151076 libertyHGH301510
• readpassphrase breaks world Steve Kargl
  • Re: readpassphrase breaks world Alfred Perlstein
• binutils (libintl.h) problem (was: weird binutils problem) Hiten Pandya
  • Re: binutils (libintl.h) problem (was: weird binutils problem) David O'Brien
  • Re: binutils (libintl.h) problem (was: weird binutils problem) Hiten Pandya
  • Re: binutils (libintl.h) problem (was: weird binutils problem) Hiten Pandya
• Keyboard (quasi-)lockup running script David Wolfskill
  • Re: Keyboard (quasi-)lockup running script Julian Elischer
  • Re: Keyboard (quasi-)lockup running script Robert Watson
  • Re: Keyboard (quasi-)lockup running script Robert Watson
  • Re: Keyboard (quasi-)lockup running script Robert Watson
  • Re: Keyboard (quasi-)lockup running script Robert Watson
• Anyone using DIAGNOSTIC td_ucred stuff? John Baldwin
  • Re: Anyone using DIAGNOSTIC td_ucred stuff? Julian Elischer
• can someone explain this change to bsd.lib.mk ? Luigi Rizzo
  • Re: can someone explain this change to bsd.lib.mk ? Warner Losh
  • Re: can someone explain this change to bsd.lib.mk ? Luigi Rizzo
  • Re: can someone explain this change to bsd.lib.mk ? Ruslan Ermilov
  • Re: can someone explain this change to bsd.lib.mk ? M. Warner Losh
  • Re: can someone explain this change to bsd.lib.mk ? Ruslan Ermilov
• gnome in -currurent Seth Hettich
• linprocfs.ko is broken Steve Kargl
  • Re: linprocfs.ko is broken Kris Kennaway
  • Re: linprocfs.ko is broken Steve Kargl
• Weird binutils error (libintl.h not found) in 5.0-CURRENT Hiten Pandya
  • Re: Weird binutils error (libintl.h not found) in 5.0-CURRENT Michael Lucas
  • Re: Weird binutils error (libintl.h not found) in 5.0-CURRENT Hiten Pandya
  • Re: Weird binutils error (libintl.h not found) in 5.0-CURRENT David O'Brien
  • Re: Weird binutils error (libintl.h not found) in 5.0-CURRENT David O'Brien
  • Re: Weird binutils error (libintl.h not found) in 5.0-CURRENT Hiten Pandya
  • Re: Weird binutils error (libintl.h not found) in 5.0-CURRENT David O'Brien
• HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Murray Stokely
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Jeff Roberson
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Murray Stokely
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Mark Murray
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Andrey A. Chernov
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Brian Somers
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) David W. Chapman Jr.
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Brian Somers
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) David W. Chapman Jr.
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Robert Watson
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) David W. Chapman Jr.
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Will Andrews
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) David W. Chapman Jr.
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Peter Pentchev
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Robert Watson
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Michael G. Petry
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Bruce Evans
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) David W. Chapman Jr.
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Garance A Drosihn
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Garance A Drosihn
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Mike Barcroft
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) David W. Chapman Jr.
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Mike Barcroft
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Dag-Erling Smorgrav
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) David W. Chapman Jr.
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Garance A Drosihn
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) David W. Chapman Jr.
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) David W. Chapman Jr.
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Joel Wilsson
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Mike Barcroft
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) George V. Neville-Neil
  • Preparing innocent users for -current Doug Barton
  • Re: Preparing innocent users for -current Warner Losh
  • Re: Preparing innocent users for -current Hiten Pandya
  • Re: Preparing innocent users for -current Terry Lambert
  • Re: Preparing innocent users for -current Doug Barton
  • Re: Preparing innocent users for -current Hiten Pandya
  • Re: Preparing innocent users for -current Murray Stokely
  • Re: Preparing innocent users for -current Hiten Pandya
  • Re: Preparing innocent users for -current Hiten Pandya
  • Re: Preparing innocent users for -current Doug Barton
  • Re: Preparing innocent users for -current Michael G. Petry
  • Re: Preparing innocent users for -current Will Andrews
  • Re: Preparing innocent users for -current Garance A Drosihn
  • Re: Preparing innocent users for -current Murray Stokely
  • Re: Preparing innocent users for -current Thomas Moestl
  • Re: Preparing innocent users for -current Doug Barton
  • Re: Preparing innocent users for -current Dag-Erling Smorgrav
  • Re: Preparing innocent users for -current Greg Black
  • Re: Preparing innocent users for -current Dag-Erling Smorgrav
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Chris Hedley
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Matthew Jacob
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Wilko Bulte
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Matthew Jacob
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) John Baldwin
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Andrew Gallatin
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Matthew Jacob
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Doug Rabson
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Garance A Drosihn
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Terry Lambert
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Robert Watson
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Jake Burkholder
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Terry Lambert
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Jake Burkholder
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Chris Hedley
  • Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Kris Kennaway
  • Upgrading to 5-CURRENT via sources Lamont Granquist
  • Re: Upgrading to 5-CURRENT via sources Ruslan Ermilov
  • CVS Issues with branch.. Was: Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Peter Wemm
  • Re: CVS Issues with branch.. Was: Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Bruce A. Mah

[Earlier messages] [Later messages]