freebsd-current

• Date Index

---

• getcwd in kernel space, Eren Erdemli
• kernel panic on today's CURRENT when running sysctl -a, Kazuaki ODA
  • Re: kernel panic on today's CURRENT when running sysctl -a, Kostik Belousov
  • Re: kernel panic on today's CURRENT when running sysctl -a, Gavin Atkinson
• tcsh hangs in sigsuspend, Michiel Boland
  • Re: tcsh hangs in sigsuspend, Steve Kargl
    • Re: tcsh hangs in sigsuspend, Rui Paulo
      • Re: tcsh hangs in sigsuspend, Steve Kargl
      • Re: tcsh hangs in sigsuspend, Rui Paulo
• sigsuspend gets interrupted by ptrace, Michiel Boland
  • Re: sigsuspend gets interrupted by ptrace, John-Mark Gurney
• SCHED_4BSD: More than 1 process running on UP machine?, Ulrich Spoerlein
  • Re: SCHED_4BSD: More than 1 process running on UP machine?, Astrodog
• libthread error, Beech Rintoul
• Wireless NICs not obeying 'SSID' setting., Kevin Gerry
  • Re: Wireless NICs not obeying 'SSID' setting., Sam Leffler
    • Re: Wireless NICs not obeying 'SSID' setting., Sam Leffler
      • Re: Wireless NICs not obeying 'SSID' setting., Kevin Gerry
• mount_smbfs stuck in devdrn, Ivan Voras
  • Re: mount_smbfs stuck in devdrn, Wilkinson, Alex
  • Re: mount_smbfs stuck in devdrn, Kostik Belousov
  • Re: mount_smbfs stuck in devdrn, Vladimir Grebenschikov
• recent USB changes broke multimedia/pwcbsd, Lars Engels
  • Re: recent USB changes broke multimedia/pwcbsd, Rui Paulo
    • Re: recent USB changes broke multimedia/pwcbsd, Lars Engels
• F/W - dhcpd deamon question, Randall Stewart
  • Re: F/W - dhcpd deamon question, Michael Butler
    • Re: F/W - dhcpd deamon question, Randall Stewart
• cam_periph.c compilation errors on the -CURRENT, Eygene Ryabinkin
  • Re: cam_periph.c compilation errors on the -CURRENT, Alexander Kabaev
    • Re: cam_periph.c compilation errors on the -CURRENT, Eygene Ryabinkin
• Nvidia-driver and current lead system reboot with no error message, Daichi GOTO
  • Re: Nvidia-driver and current lead system reboot with no error message, speconly
    • Re: Nvidia-driver and current lead system reboot with no error message, Daichi GOTO
    • Re: Nvidia-driver and current lead system reboot with no error message, Daichi GOTO
      • Re: Nvidia-driver and current lead system reboot with no error message, Daichi GOTO
• SYNCOOKIE authentication problems, Steve Kargl
  • Re: SYNCOOKIE authentication problems, Abdullah Ibn Hamad Al-Marri
  • Re: SYNCOOKIE authentication problems, Eygene Ryabinkin
    • Re: SYNCOOKIE authentication problems, Steve Kargl
      • Re: SYNCOOKIE authentication problems, Julian Elischer
      • Re: SYNCOOKIE authentication problems, Steve Kargl
  • Re: SYNCOOKIE authentication problems, David Malone
    • Re: SYNCOOKIE authentication problems, Steve Kargl
      • Re: SYNCOOKIE authentication problems, David Malone
      • Re: SYNCOOKIE authentication problems, Steve Kargl
    • Re: SYNCOOKIE authentication problems, Steve Kargl
• update 6.2 -> current failed - optimization problem, Alex Keda
  • Re: update 6.2 -> current failed - optimization problem, Randall Stewart
  • Re: update 6.2 -> current failed - optimization problem, Yuri Pankov
    • Re: update 6.2 -> current failed - optimization problem, Andrey Chernov
• buildworld error - ssl_stat.c:249, TAC-TAC computer s.r.o.
• Snapshots on the homepage, Christian Walther
• concept prove patch for ktrace output to all file types, Howard Su
  • Re: concept prove patch for ktrace output to all file types, Robert Watson
    • Re: concept prove patch for ktrace output to all file types, Howard Su
      • Re: concept prove patch for ktrace output to all file types, Robert Watson
• questions re 32bit & 64bit ports in a 64bit world, Bakul Shah
  • Re: questions re 32bit & 64bit ports in a 64bit world, Alexander Leidinger
• Dtrace status in FreeBSD 7.0, Abdullah Ibn Hamad Al-Marri
• FAST_IPSEC import to HEAD is imminent.., gnn
  • Re: FAST_IPSEC import to HEAD is imminent.., Poul-Henning Kamp
    • Re: FAST_IPSEC import to HEAD is imminent.., Bjoern A. Zeeb
      • Re: FAST_IPSEC import to HEAD is imminent.., George V. Neville-Neil
• Dump(8) problems, Thomas Sparrevohn
• nfs on zfs panic, Philippe Pegon
  • Re: nfs on zfs panic, Doug Rabson
    • Re: nfs on zfs panic, Philippe Pegon
    • Re: nfs on zfs panic, Pawel Jakub Dawidek
      • Re: nfs on zfs panic, Doug Rabson
      • Re: nfs on zfs panic, Pawel Jakub Dawidek
      • Re: nfs on zfs panic, Doug Rabson
• ZFS deadlocks or panics, Jan Schmidle
  • Re: ZFS deadlocks or panics, Pawel Jakub Dawidek
    • Re: ZFS deadlocks or panics, Jan Schmidle
      • Re: ZFS deadlocks or panics, Claus Guttesen
      • Re: ZFS deadlocks or panics, Jan Schmidle
• TCP Spurious RST, segment rejected, Brian Donnell
• how to handle name clashes in linux/freebsd kernel sources ?, Luigi Rizzo
  • 'static inline' vs macros for kernel functions ? (was how to handle name clashes in linux/freebsd kernel sources ?), Luigi Rizzo
    • Re: 'static inline' vs macros for kernel functions ? (was how to handle name clashes in linux/freebsd kernel sources ?), John Baldwin
• Is this reasonable ?, Ollivier Robert
  • Re: Is this reasonable ?, Tom Evans
    • Re: Is this reasonable ?, Ollivier Robert
      • Re: Is this reasonable ?, Ollivier Robert
      • Re: Is this reasonable ?, Abdullah Ibn Hamad Al-Marri
      • Re: Is this reasonable ?, Tom Evans
      • Re: Is this reasonable ?, Erik Trulsson
      • Re: Is this reasonable ?, Garrett Cooper
      • Re: Is this reasonable ?, Michael Butler
  • Re: Is this reasonable ?, Dmitry Morozovsky
• [PATCH] Machine Check Architecture on amd64, Suleiman Souhlal
  • Re: [PATCH] Machine Check Architecture on amd64, Ed Schouten
    • Re: [PATCH] Machine Check Architecture on amd64, Suleiman Souhlal
• Issues with 'xl0' keeping link, Kevin Gerry
  • Re: Issues with 'xl0' keeping link, Steve Kargl
    • Re: Issues with 'xl0' keeping link (bge0, em0 as well?), Michael C Voorhis
• Re: The relation between %fs and fs base, Jung-uk Kim
  • Re: The relation between %fs and fs base, jj shen
• ZFS and Jails (dataset does not exist), Axel S. Gruner
• RE: unionfs and tmpfs?, Howard Su
  • Re: unionfs and tmpfs?, Ivan Voras
• binutils/gas compilation problems on i386., Eygene Ryabinkin
• Silent gcc 4.2.0 loop optimization bug with -O2, Andrey Chernov
  • Re: Silent gcc 4.2.0 loop optimization bug with -O2, Andrey Chernov
    • Re: Silent gcc 4.2.0 loop optimization bug with -O2, Alexander Kabaev
      • Re: Silent gcc 4.2.0 loop optimization bug with -O2, Xin LI
      • Re: Silent gcc 4.2.0 loop optimization bug with -O2, Andrey Chernov
      • Re: Silent gcc 4.2.0 loop optimization bug with -O2, Ed Schouten
      • Re: Silent gcc 4.2.0 loop optimization bug with -O2, Andrey Chernov
      • Re: Silent gcc 4.2.0 loop optimization bug with -O2, Ed Schouten
      • Re: Silent gcc 4.2.0 loop optimization bug with -O2, Andrey Chernov
      • Re: Silent gcc 4.2.0 loop optimization bug with -O2, Garrett Cooper
      • Re: Silent gcc 4.2.0 loop optimization bug with -O2, Sascha Holzleiter
      • Re: Silent gcc 4.2.0 loop optimization bug with -O2, Jung-uk Kim
      • RE: Silent gcc 4.2.0 loop optimization bug with -O2, David Schwartz
      • Re: Silent gcc 4.2.0 loop optimization bug with -O2, Alexander Kabaev
• Problem compiling -CURRENT/OpenSSL, Luchezar Petkov
  • Re: Problem compiling -CURRENT/OpenSSL, Yuri Pankov
    • Re: Problem compiling -CURRENT/OpenSSL, Luchezar Petkov
• KSE was Re: open/close/ioctl api change?, Danny Braniss
  • Re: KSE was Re: open/close/ioctl api change?, Julian Elischer
    • Re: KSE was Re: open/close/ioctl api change?, Danny Braniss
      • Re: KSE was Re: open/close/ioctl api change?, Julian Elischer
  • <Possible follow-ups>
  • Re: KSE was Re: open/close/ioctl api change?, Danny Braniss
    • Re: KSE was Re: open/close/ioctl api change?, vehemens
• open/close/ioctl api change?, Danny Braniss
  • Re: open/close/ioctl api change?, Kostik Belousov
• ZFS and gmirror, Axel S. Gruner
  • Re: ZFS and gmirror, Dmitry Morozovsky
    • Re: ZFS and gmirror, Axel S. Gruner
  • Re: ZFS and gmirror, Hugo Silva
• ZFS questions, Dmitry Morozovsky
  • Re: ZFS questions, Pawel Jakub Dawidek
    • Re: ZFS questions, Dmitry Morozovsky
  • Re: ZFS questions, Peter Schuller
• options IPI_PREEMPTION and PREEMPTION in 7.0 AMD64, Abdullah Ibn Hamad Al-Marri
  • Re: options IPI_PREEMPTION and PREEMPTION in 7.0 AMD64, Attilio Rao
    • Re: options IPI_PREEMPTION and PREEMPTION in 7.0 AMD64, Abdullah Ibn Hamad Al-Marri
• USB mouse works again in current!!!, youshi10
  • Re: USB mouse works again in current!!!, M. Warner Losh
    • Re: USB mouse works again in current!!!, youshi10
      • Re: USB mouse works again in current!!!, M. Warner Losh
    • Re: USB mouse works again in current!!!, Ian FREISLICH
      • Re: USB mouse works again in current!!!, Ian FREISLICH
      • Re: USB mouse works again in current!!!, Garrett Cooper
      • Re: USB mouse works again in current!!!, M. Warner Losh
      • Re: USB mouse works again in current!!!, Ian FREISLICH
      • Re: USB mouse works again in current!!!, Garrett Cooper
      • Re: USB mouse works again in current!!!, Hans Petter Selasky
      • Re: USB mouse works again in current!!!, Ian FREISLICH
      • Re: USB mouse works again in current!!!, Hans Petter Selasky
      • Re: USB mouse works again in current!!!, Ian FREISLICH
      • Re: USB mouse works again in current!!!, Niki Denev
      • Re: USB mouse works again in current!!!, M. Warner Losh
• DRM Impacted by Recent Changes, vehemens
• FreeBSD status reports due: July 7, 2007, Max Laier
• Building a kernel with SCTP support, Vlad GALU
  • Re: Building a kernel with SCTP support, Kip Macy
    • Re: Building a kernel with SCTP support, Vlad GALU
  • Re: Building a kernel with SCTP support, Yann Berthier
    • Re: Building a kernel with SCTP support, Vlad GALU
      • Re: Building a kernel with SCTP support, Kip Macy
      • Re: Building a kernel with SCTP support, Steve Kargl
      • Re: Building a kernel with SCTP support, Randall Stewart
      • Re: Building a kernel with SCTP support, Randall Stewart
• Xen and 7.0, Petri Helenius
  • Re: Xen and 7.0, Rink Springer
    • Re: Xen and 7.0, Roman Divacky
• weird error with nmh, Gary Jennejohn
  • Re: weird error with nmh, Ian FREISLICH
    • Re: weird error with nmh, Mark Murray
      • Re: weird error with nmh, Ian FREISLICH
      • Re: weird error with nmh, Poul-Henning Kamp
  • Re: weird error with nmh, M. Warner Losh
    • Re: weird error with nmh, Gary Jennejohn
  • Re: weird error with nmh, Harti Brandt
• endlesst loop/panic while attaching SATA disk on the fly, Dmitry Morozovsky
  • Re: endlesst loop/panic while attaching SATA disk on the fly, Dmitry Morozovsky
• kernel panic during reboot, Pascal Hofstee
  • Re: kernel panic during reboot, Kostik Belousov
    • Re: kernel panic during reboot, Pascal Hofstee
• ZFS on 7.X CURRENT /usr refuses to remount after boot, Outback Dingo
  • Re: ZFS on 7.X CURRENT /usr refuses to remount after boot, Thierry Herbelot
    • Re: ZFS on 7.X CURRENT /usr refuses to remount after boot, Outback Dingo
  • Re: ZFS on 7.X CURRENT /usr refuses to remount after boot, Axel S. Gruner
• recent USB changes break building of atausb module, Pascal Hofstee
  • Re: recent USB changes break building of atausb module, Hans Petter Selasky
    • Re: recent USB changes break building of atausb module, M. Warner Losh
• Can't kill WATCH in latest current, Abdullah Ibn Hamad Al-Marri
  • Re: Can't kill WATCH in latest current, Yuri Pankov
• NFS problems with recent -current, Peter Jeremy
  • Re: NFS problems with recent -current, Peter Jeremy
• Port of OpenBSD's sdiff, Steven Kreuzer
  • Re: Port of OpenBSD's sdiff, Doug Barton
  • Re: Port of OpenBSD's sdiff, Gabor Kovesdan
    • Re: Port of OpenBSD's sdiff, Steven Kreuzer
    • Re: Port of OpenBSD's sdiff, Stanislav Sedov
      • Re: Port of OpenBSD's sdiff, Robert Watson
      • Re: Port of OpenBSD's sdiff, Gabor Kovesdan
      • Re: Port of OpenBSD's sdiff, Robert Watson
      • Re: Port of OpenBSD's sdiff, Steven Kreuzer
    • Re: Port of OpenBSD's sdiff, Sean C. Farley
      • Re: Port of OpenBSD's sdiff, Gavin Atkinson
      • Re: Port of OpenBSD's sdiff, Xin LI
      • Re: Port of OpenBSD's sdiff, Ollivier Robert
      • Re: Port of OpenBSD's sdiff, Andrey Chernov
      • Re: Port of OpenBSD's sdiff, LI Xin
      • Re: Port of OpenBSD's sdiff, Andrey Chernov
  • Re: Port of OpenBSD's sdiff, M. Warner Losh
  • Re: Port of OpenBSD's sdiff, Xin LI
    • Q) lockf(flock?) on -current (amd64), Ken Yamada
      • Re: Q) lockf(flock?) on -current (amd64), Daniel O'Connor
      • Re: Q) lockf(flock?) on -current (amd64), Ken Yamada
• UPEK/TouchChip Biometric Device problem, Patrick Tracanelli
  • Re: UPEK/TouchChip Biometric Device problem, Hans Petter Selasky
• PostgreSQL Stats Collector: EINTR on POLL?, Larry Rosenman
• Library problems in current, sac
  • Re: Library problems in current, Rong-en Fan
• em problems on SGI/AltixXE310, Danny Braniss
• Low end video card that won't crash server ... ?, Marc G. Fournier
  • Re: Low end video card that won't crash server ... ?, Garrett Cooper
    • Re: Low end video card that won't crash server ... ?, Marc G. Fournier
      • Re: Low end video card that won't crash server ... ?, Conrad J. Sabatier
    • Re: Low end video card that won't crash server ... ?, Matthew D. Fuller
      • Re: Low end video card that won't crash server ... ?, Garrett Cooper
• ukbd(4) not attaching when loaded as module, Ulrich Spoerlein
  • Re: ukbd(4) not attaching when loaded as module, Harald Schmalzbauer
    • Re: ukbd(4) not attaching when loaded as module, Ian FREISLICH
  • Re: ukbd(4) not attaching when loaded as module, M. Warner Losh
    • Re: ukbd(4) not attaching when loaded as module, Jung-uk Kim
      • Re: ukbd(4) not attaching when loaded as module, M. Warner Losh
      • Re: ukbd(4) not attaching when loaded as module, M. Warner Losh
• Cannot access retail DVDs with external drive, Ulrich Spoerlein
  • Re: Cannot access retail DVDs with external drive, Doug Barton
    • Re: Cannot access retail DVDs with external drive, Ulrich Spoerlein
• Which GigE NIC for reliable use?, Steve Kargl
  • Re: Which GigE NIC for reliable use?, Sameh Ghane
    • Re: Which GigE NIC for reliable use?, Steve Kargl
• Intel PowerTop tool on FreeBSD?, Alexander Leidinger
  • Re: Intel PowerTop tool on FreeBSD?, Andrey V. Elsukov
    • Re: Intel PowerTop tool on FreeBSD?, Alexander Leidinger
• Wireless capture, Eric L. Chen
  • Re: Wireless capture, Sam Leffler
    • Re: Wireless capture, Stefan Ehmann
      • Re: Wireless capture, Henrik Brix Andersen
      • Re: Wireless capture, Niki Denev
      • Re: Wireless capture, Stefan Ehmann
      • Re: Wireless capture, Sam Leffler
• Promise SATA300 TX4 card issues, Nathan Butcher
• ZFS scrub gone wrong, Hugo Silva
  • Re: ZFS scrub gone wrong, Peter Schuller
• Kernel Panic in latest -CURRENT, Kevin Gerry
  • Re: Kernel Panic in latest -CURRENT, Attilio Rao
    • Re: Kernel Panic in latest -CURRENT, Jeff Roberson
      • Re: Kernel Panic in latest -CURRENT, Kevin Gerry
      • Re: Kernel Panic in latest -CURRENT, Kip Macy
      • Re: Kernel Panic in latest -CURRENT, Kevin Gerry
      • Re: Kernel Panic in latest -CURRENT, Kip Macy
      • Re: Kernel Panic in latest -CURRENT, Kevin Gerry
      • Re: Kernel Panic in latest -CURRENT, Kevin Gerry
      • Re: Kernel Panic in latest -CURRENT, Kevin Gerry
      • Re: Kernel Panic in latest -CURRENT, Rong-en Fan
      • Re: Kernel Panic in latest -CURRENT, Kevin Gerry
• AGPGART not found ... ( on Q965), Sateesh Mandava
  • <Possible follow-ups>
  • AGPGART not found ... ( on Q965), Sateesh Mandava
    • Re: AGPGART not found ... ( on Q965), Eric Anholt
  • Re: AGPGART not found ... ( on Q965), V.Chukharev
    • RE: AGPGART not found ... ( on Q965), Sateesh Mandava
• ZFS and deadlock with {nullfs,NFS}, Joe Marcus Clarke
  • Re: ZFS and deadlock with {nullfs,NFS}, Kris Kennaway
    • Re: ZFS and deadlock with {nullfs,NFS}, Joe Marcus Clarke
      • Re: ZFS and deadlock with {nullfs,NFS}, Kris Kennaway
      • Re: ZFS and deadlock with {nullfs,NFS}, Joe Marcus Clarke
    • Re: ZFS and deadlock with {nullfs,NFS}, Dan Mack
      • Re: ZFS and deadlock with {nullfs,NFS}, John Nielsen
      • Re: ZFS and deadlock with {nullfs,NFS}, Dan Mack
      • Re: ZFS and deadlock with {nullfs,NFS}, John Nielsen
      • Re: ZFS and deadlock with {nullfs,NFS}, Joao Barros
• ZFS status now in June? / stable enough for a file server?, Olivier Mueller
  • Re: ZFS status now in June? / stable enough for a file server?, Oliver Fromme
    • Re: ZFS status now in June? / stable enough for a file server?, Kris Kennaway
  • Re: ZFS status now in June? / stable enough for a file server?, Borja Marcos
    • Re: ZFS status now in June? / stable enough for a file server?, Hugo Silva
  • Re: ZFS status now in June? / stable enough for a file server?, Claus Guttesen
  • Re: ZFS status now in June? / stable enough for a file server?, Dennis Berger
    • Re: ZFS status now in June? / stable enough for a file server?, Patrick Tracanelli
  • Re: ZFS status now in June? / stable enough for a file server?, Olivier Mueller
  • Re: ZFS status now in June? / stable enough for a file server?, Brian Donnell
  • Re: ZFS status now in June? / stable enough for a file server?, Nikolay Pavlov
    • Re: ZFS status now in June? / stable enough for a file server?, Alexander Leidinger
      • Re: ZFS status now in June? / stable enough for a file server?, Bernd Walter
      • Re: ZFS status now in June? / stable enough for a file server?, Dmitry Morozovsky
      • Re: ZFS status now in June? / stable enough for a file server?, Bernd Walter
      • Re: ZFS status now in June? / stable enough for a file server?, Ingo Bormuth
      • Re: ZFS status now in June? / stable enough for a file server?, Thierry Herbelot
• Camellia block cipher for geli (GEOM ELI)., Yoshisato YANAGISAWA
• truss(1) gets confused after execve, Michiel Boland
  • Re: truss(1) gets confused after execve, youshi10
    • Re: truss(1) gets confused after execve, Michiel Boland
• Panic in callout_reset(), Peter Jeremy
• Acer Aspire 5100 problems in current, Alin Popa
• Re: i386 with PAE or AMD64 on PowerEdge with 4G RAM, youshi10
  • Re: i386 with PAE or AMD64 on PowerEdge with 4G RAM, Gaspar Chilingarov
• Current does not boot - BIOS problem?, Marinos Ilias
  • Re: Current does not boot - BIOS problem?, Randall Stewart
    • Re: Current does not boot - BIOS problem?, Gary Corcoran
  • Re: Current does not boot - BIOS problem?, Niki Denev
    • Re: Current does not boot - BIOS problem?, ben wilber
      • Re: Current does not boot - BIOS problem?, Rene Ladan
    • Re: Current does not boot - BIOS problem?, Niki Denev
    • Re: Current does not boot - BIOS problem?, Hidetoshi Shimokawa
  • Re: Current does not boot - BIOS problem?, Abdullah Ibn Hamad Al-Marri
  • <Possible follow-ups>
  • Re: Current does not boot - BIOS problem?, Marinos Ilias
    • Re: Current does not boot - BIOS problem?, Garrett Cooper
• ukbd broken as module, Ian FREISLICH
  • Re: ukbd broken as module, Vladimir Grebenschikov
    • Re: ukbd broken as module, M. Warner Losh
• zfs and backup, Claus Guttesen
• pkg_add : works fine when compiled normally ; segfaults when gprof'ed, Garrett Cooper
  • Re: pkg_add : works fine when compiled normally ; segfaults when gprof'ed, Garrett Cooper
• wireless, Andrew Thompson
  • Re: wireless, Craig Boston
    • Re: wireless, Sam Leffler
      • Re: wireless, Craig Boston
      • Re: wireless, Nicolai Petri (lists)
      • Re: wireless, Andrew Thompson
  • Message not available
    • Re: wireless, Andrew Thompson
      • Re: wireless, Pierre DAVID
  • Re: wireless, Kevin Lo
    • Re: wireless [iwi firmware error], Sam Leffler
      • Re: wireless [iwi firmware error], Eric L. Chen
• RFC for wider rc.conf.d/ for jails, Jeremie Le Hen
• HELP: EM bus_alloc_resource_any fails on Dell Dimension 9150, Jack Vogel
  • RE: HELP: EM bus_alloc_resource_any fails on Dell Dimension 9150, David Christensen
• fts(3) patch for review, Yar Tikhiy
  • Re: fts(3) patch for review, Gary Corcoran
    • Re: fts(3) patch for review, Erik Trulsson
      • Re: fts(3) patch for review, Yar Tikhiy
      • Re: fts(3) patch for review, Tim Kientzle
      • Re: fts(3) patch for review, Yar Tikhiy
• HEADS UP: share library version bump, Rong-en Fan
• HELP! weird tcp problem, Maksim Yevmenkin
  • Re: HELP! weird tcp problem, youshi10
  • Re: HELP! weird tcp problem, Niki Denev
    • Re: HELP! weird tcp problem, Vladimir Grebenschikov
      • Re: HELP! weird tcp problem, Sam Baskinger
• Re: [AMD64] X.org build eats all the memory when compiled with GCC 4.2 (fwd), youshi10
• Re: Evaluation of High Precision Event Timer Driver for userland timer facility, Takeharu KATO
  • Re: Evaluation of High Precision Event Timer Driver for userland timer facility, Poul-Henning Kamp
• Why vfs.timestamp_precision is set to 0 by default?, Xin LI
  • Re: Why vfs.timestamp_precision is set to 0 by default?, John Polstra
  • Re: Why vfs.timestamp_precision is set to 0 by default?, Bruce Evans
• Is someone aware of problem with SytemV semaphores?, Alexander Leidinger
• 32bit app crashed on AMD64, Abdullah Ibn Hamad Al-Marri
  • Re: 32bit app crashed on AMD64, Ed Maste
• Multicast problems, Ian FREISLICH
  • Re: Multicast problems, Bruce M. Simpson
    • Re: Multicast problems, Ian FREISLICH
      • Re: Multicast problems, Bruce M. Simpson
    • Re: Multicast problems, Daniel Eischen
      • Re: Multicast problems, Bruce M. Simpson
      • Re: Multicast problems, Daniel Eischen
      • Re: Multicast problems, Bruce M. Simpson
      • Re: Multicast problems [PATCH], Bruce M. Simpson
      • Re: Multicast problems [PATCH], Bruce M Simpson
      • Re: Multicast problems [PATCH], Daniel Eischen
      • Re: Multicast problems [PATCH], Bruce M. Simpson
      • Re: Multicast problems [PATCH], Stefan Farfeleder
      • socklen_t (Re: Multicast problems [PATCH]), Daniel Eischen
      • Re: socklen_t (Re: Multicast problems [PATCH]), Stefan Farfeleder
      • Re: socklen_t (Re: Multicast problems [PATCH]), Harti Brandt
      • Re: socklen_t (Re: Multicast problems [PATCH]), Daniel Eischen
• ath kldunloading hangs the system, Harald Schmalzbauer
  • Re: ath kldunloading hangs the system, Sepherosa Ziehau
  • Re: ath kldunloading hangs the system, Sam Leffler
• Xorg + CURRENT == computer reboot ... ?, Marc G. Fournier
  • Re: Xorg + CURRENT == computer reboot ... ?, Claus Guttesen
  • Re: Xorg + CURRENT == computer reboot ... ?, Norberto Meijome
• -CURRENT + Xorg + nvidia driver == Crash ?, Marc G. Fournier
  • Re: -CURRENT + Xorg + nvidia driver == Crash ?, Juan Segovia Silvero
• Linksys USB200M, Randall Stewart
  • Re: Linksys USB200M, Garrett Cooper
  • Re: Linksys USB200M, Daniel O'Connor
    • Re: Linksys USB200M, Randall Stewart
    • Re: Linksys USB200M, M. Warner Losh
      • Re: Linksys USB200M, Daniel O'Connor
      • Re: Linksys USB200M, Randall Stewart
• Userland problems from kern.pts.enable=1, Kris Kennaway
  • Re: Userland problems from kern.pts.enable=1, Tom Evans
    • Re: Userland problems from kern.pts.enable=1, Kostik Belousov
      • Re: Userland problems from kern.pts.enable=1, Maxim Konovalov
      • Re: Userland problems from kern.pts.enable=1, Kris Kennaway
      • Re: Userland problems from kern.pts.enable=1, Maxim Konovalov
      • Re: Userland problems from kern.pts.enable=1, Maxim Konovalov
    • Re: Userland problems from kern.pts.enable=1, Kris Kennaway
      • Re: Userland problems from kern.pts.enable=1, Steve Kargl
      • Re: Userland problems from kern.pts.enable=1, Kris Kennaway
• patch: acpi usermode suspend API change, Nate Lawson
  • Re: patch: acpi usermode suspend API change, Lars Engels
    • Re: patch: acpi usermode suspend API change, Nate Lawson
      • Re: patch: acpi usermode suspend API change, Lars Engels
      • Re: patch: acpi usermode suspend API change, Nate Lawson
  • Re: patch: acpi usermode suspend API change, Lars Engels
    • Re: patch: acpi usermode suspend API change, Nate Lawson
      • Re: patch: acpi usermode suspend API change, Lars Engels
      • Re: patch: acpi usermode suspend API change, Nate Lawson
      • Re: patch: acpi usermode suspend API change, Lars Engels
      • Re: patch: acpi usermode suspend API change, Ariff Abdullah
• ath(4) problems after sam_wifi merge, Rui Paulo
  • Re: ath(4) problems after sam_wifi merge, Andrew Thompson
    • Re: ath(4) problems after sam_wifi merge, Rui Paulo
      • Re: ath(4) problems after sam_wifi merge, Sepherosa Ziehau
      • Re: ath(4) problems after sam_wifi merge, Rui Paulo
      • Re: ath(4) problems after sam_wifi merge, Sam Leffler
      • Re: ath(4) problems after sam_wifi merge, Sam Leffler
      • Re: ath(4) problems after sam_wifi merge, Rui Paulo
  • Re: ath(4) problems after sam_wifi merge, Ian FREISLICH
    • Re: ath(4) problems after sam_wifi merge, Sepherosa Ziehau
      • Re: ath(4) problems after sam_wifi merge, Ian FREISLICH
  • <Possible follow-ups>
  • Re: ath(4) problems after sam_wifi merge, Ian FREISLICH
• Stop in /usr/src/sys/modules/ahb, Per olof Ljungmark
  • Re: Stop in /usr/src/sys/modules/ahb, Scott Long
• Cannot use iwi(4): "could not load firmware iwi_bss", Jeremie Le Hen
  • Re: Cannot use iwi(4): "could not load firmware iwi_bss", Andrew Thompson
    • Re: Cannot use iwi(4): "could not load firmware iwi_bss", Jeremie Le Hen
• [AMD64] X.org build eats all the memory when compiled with GCC 4.2, Gaspar Chilingarov
  • Re: [AMD64] X.org build eats all the memory when compiled with GCC 4.2, Claus Guttesen
    • Re: [AMD64] X.org build eats all the memory when compiled with GCC 4.2, Garrett Cooper
      • Re: [AMD64] X.org build eats all the memory when compiled with GCC 4.2, Roman Divacky
      • Re: [AMD64] X.org build eats all the memory when compiled with GCC 4.2, Michiel Boland
      • Re: [AMD64] X.org build eats all the memory when compiled with GCC 4.2, Daniel Eischen
      • Re: [AMD64] X.org build eats all the memory when compiled with GCC 4.2, Kris Kennaway
      • Re: [AMD64] X.org build eats all the memory when compiled with GCC 4.2, youshi10
      • Re: [AMD64] X.org build eats all the memory when compiled with GCC 4.2, Garrett Cooper
    • Re: [AMD64] X.org build eats all the memory when compiled with GCC 4.2, Gaspar Chilingarov
  • <Possible follow-ups>
  • [AMD64] X.org build eats all the memory when compiled with GCC 4.2, Gaspar Chilingarov
• Kernel panic, Manfred Antar
  • Re: Kernel panic, Remko Lodder
  • Re: Kernel panic, Jeff Roberson
• Broken RFC1323 slightly broken., Jeremie Le Hen
  • Re: Broken RFC1323 slightly broken., Maxim Konovalov
  • Re: Broken RFC1323 slightly broken., Craig Boston
• Undefined symbol timer_delete()?, Craig Rodrigues
  • Re: Undefined symbol timer_delete()?, Steve Kargl
    • Re: Undefined symbol timer_delete()?, Craig Rodrigues
      • Re: Undefined symbol timer_delete()?, Steve Kargl
      • Re: Undefined symbol timer_delete()?, Daniel Eischen
    • Re: Undefined symbol timer_delete()?, David Xu
• btsocks_rfcomm_session_mtx / so_snd_sx LOR, Lars Engels
  • Re: btsocks_rfcomm_session_mtx / so_snd_sx LOR, Maksim Yevmenkin
    • Re: btsocks_rfcomm_session_mtx / so_snd_sx LOR, Lars Engels
• nvidia 7900gs pci-e, do i need device AGP in kerenel?, Georgi Iovchev
• linux-sun-jdk-1.5.0.12,2 - java SIGSEGV and then wait forever, Vladimir Grebenschikov
• kernel panic with pccard insert on recent 7.0 CURRENT, 吴叔坤
  • Re: kernel panic with pccard insert on recent 7.0 CURRENT, Hidetoshi Shimokawa
    • Re: kernel panic with pccard insert on recent 7.0 CURRENT, Dan Nelson
    • Re: kernel panic with pccard insert on recent 7.0 CURRENT, M. Warner Losh
      • Re: kernel panic with pccard insert on recent 7.0 CURRENT, Hidetoshi Shimokawa
      • Re: kernel panic with pccard insert on recent 7.0 CURRENT, Paolo Pisati
      • Re: kernel panic with pccard insert on recent 7.0 CURRENT, Hidetoshi Shimokawa
      • Re: kernel panic with pccard insert on recent 7.0 CURRENT, M. Warner Losh
      • Re: kernel panic with pccard insert on recent 7.0 CURRENT, Paolo Pisati
    • Re: kernel panic with pccard insert on recent 7.0 CURRENT, M. Warner Losh
      • Re: kernel panic with pccard insert on recent 7.0 CURRENT, John-Mark Gurney
      • Re: kernel panic with pccard insert on recent 7.0 CURRENT, M. Warner Losh
      • Re: kernel panic with pccard insert on recent 7.0 CURRENT, John-Mark Gurney
      • Re: kernel panic with pccard insert on recent 7.0 CURRENT, M. Warner Losh
      • Re: kernel panic with pccard insert on recent 7.0 CURRENT, Wilkinson, Alex
      • Re: kernel panic with pccard insert on recent 7.0 CURRENT, Garrett Cooper
      • Re: kernel panic with pccard insert on recent 7.0 CURRENT, Garrett Cooper
      • Re: kernel panic with pccard insert on recent 7.0 CURRENT, John-Mark Gurney
      • Re: kernel panic with pccard insert on recent 7.0 CURRENT, M. Warner Losh
      • Re: kernel panic with pccard insert on recent 7.0 CURRENT, Paolo Pisati
    • Re: kernel panic with pccard insert on recent 7.0 CURRENT, 吴叔坤
• smi speedstep patch, Nate Lawson
  • Re: smi speedstep patch, Nate Lawson
    • Re: smi speedstep patch, Nate Lawson
• pf 4.1 Update available for testing, Max Laier
  • Re: pf 4.1 Update available for testing, Eygene Ryabinkin
  • Re: pf 4.1 Update available for testing, Florian C. Smeets
• bacula-client build failure on recent -CURRENT, Per olof Ljungmark
• Access to tape drive caused following backtrace, Alex Burke
  • Re: Access to tape drive caused following backtrace, Matthew Jacob
  • Re: Access to tape drive caused following backtrace, Scott Long
    • Re: Access to tape drive caused following backtrace, Alex Burke
• [REVIEW]: add multicast NULL route, Poul-Henning Kamp
  • Re: [REVIEW]: add multicast NULL route, John Merryweather Cooper
• German keymap not working, Tory
  • Re: German keymap not working, Oliver Fromme
    • Re: German keymap not working, Raven
      • Re: German keymap not working, Oliver Fromme
• multicast not happy ?, Poul-Henning Kamp
  • Re: multicast not happy ?, John Merryweather Cooper
    • Re: multicast not happy ?, Poul-Henning Kamp
      • Re: multicast not happy ?, John Merryweather Cooper
      • Re: multicast not happy ?, Marko Zec
      • Re: multicast not happy ?, Poul-Henning Kamp
• recent nvidia-driver trouble, Pascal Hofstee
  • Re: recent nvidia-driver trouble, Rink Springer
  • Re: recent nvidia-driver trouble, Ricardo Nabinger Sanchez
    • Re: recent nvidia-driver trouble, Pascal Hofstee
  • Re: recent nvidia-driver trouble, Gary Jennejohn
    • Re: recent nvidia-driver trouble, Craig Rodrigues
      • Re: recent nvidia-driver trouble, Adam K Kirchhoff
      • Re: recent nvidia-driver trouble, Gary Jennejohn
    • Re: recent nvidia-driver trouble, Sam Leffler
      • Re: recent nvidia-driver trouble, Rink Springer
      • Re: recent nvidia-driver trouble, youshi10
      • Re: recent nvidia-driver trouble, Gary Jennejohn
      • Re: recent nvidia-driver trouble, Doug Barton
      • Re: recent nvidia-driver trouble, Marc G. Fournier
    • Re: recent nvidia-driver trouble, Diego Depaoli
    • Re: recent nvidia-driver trouble, Ricardo Nabinger Sanchez
  • Re: recent nvidia-driver trouble, Rainer Alves
  • Re: recent nvidia-driver trouble, Marten
    • Re: recent nvidia-driver trouble, Rainer Hurling
• Swapfile on ZFS & Deadlock, Benjamin Close
  • Re: Swapfile on ZFS & Deadlock, Claus Guttesen
    • Re: Swapfile on ZFS & Deadlock, Ali Mashtizadeh
      • Re: Swapfile on ZFS & Deadlock, Kris Kennaway
  • Re: Swapfile on ZFS & Deadlock, Craig Boston
  • Re: Swapfile on ZFS & Deadlock, Kris Kennaway
    • Re: Swapfile on ZFS & Deadlock, Benjamin Close
      • Re: Swapfile on ZFS & Deadlock, Kris Kennaway
      • Re: Swapfile on ZFS & Deadlock, Benjamin Close
      • Re: Swapfile on ZFS & Deadlock, Benjamin Close
• moused linear acceleration drops, Harald Schmalzbauer
  • Re: moused linear acceleration drops, Oliver Fromme
    • Re: moused linear acceleration drops, Harald Schmalzbauer
      • Re: moused linear acceleration drops, Oliver Fromme
      • Re: moused linear acceleration drops, Harald Schmalzbauer
      • Re: moused linear acceleration drops, Oliver Fromme
      • Re: moused linear acceleration drops, Hagen Kühl
  • Re: moused linear acceleration drops, Oliver Fromme
    • Re: moused linear acceleration drops, Oliver Fromme
      • Re: moused linear acceleration drops, Oliver Fromme
• cached to nscd (was Re: nscd for freebsd), Daniel Eischen
• Intel 965 and AGP, Novembre
  • Re: Intel 965 and AGP, Tim Bishop
    • Re: Intel 965 and AGP, Novembre
• annoying behavior in less(1) after v403 import, Tom Uffner
  • Re: annoying behavior in less(1) after v403 import, Scott Long
    • Re: annoying behavior in less(1) after v403 import, Ruslan Ermilov
      • Re: annoying behavior in less(1) after v403 import, Xin LI
  • Re: annoying behavior in less(1) after v403 import, Tom Uffner
• Sleeping and my T43, Randall Stewart
  • Re: Sleeping and my T43, Kevin Oberman
    • Re: Sleeping and my T43, Randall Stewart
• "kernel: rtfree: 0xc3c4bd98 has 2 refs" on recent current, Artem Naluzhny
  • Re: "kernel: rtfree: 0xc3c4bd98 has 2 refs" on recent current, Artem Naluzhny
    • Re: "kernel: rtfree: 0xc3c4bd98 has 2 refs" on recent current, Artem Naluzhny
      • Re: "kernel: rtfree: 0xc3c4bd98 has 2 refs" on recent current, Artem Naluzhny
• hard-lock with CPU spinning, Giorgos Keramidas
  • Re: hard-lock with CPU spinning, Attilio Rao
    • Re: hard-lock with CPU spinning, Giorgos Keramidas
      • Re: hard-lock with CPU spinning, Alexandre \"Sunny\" Kovalenko
      • Re: hard-lock with CPU spinning, Giorgos Keramidas
      • Re: hard-lock with CPU spinning, Giorgos Keramidas
• ZFS with USB "SCSI", Ali Mashtizadeh
  • Re: ZFS with USB "SCSI", Pawel Jakub Dawidek
    • Re: ZFS with USB "SCSI", Ali Mashtizadeh
• fdc0 doesn't attach on my current machine, Norikatsu Shigemura
  • Re: fdc0 doesn't attach on my current machine, M. Warner Losh
  • Re: fdc0 doesn't attach on my current machine, Norikatsu Shigemura
• Best way to build a "new" AMD64 current, Walter Vaughan
  • Re: Best way to build a "new" AMD64 current, Oliver Fromme
  • Re: Best way to build a "new" AMD64 current, Rainer Duffner
  • Re: Best way to build a "new" AMD64 current, Jeff Roberson
    • Re: Best way to build a "new" AMD64 current, youshi10
      • Re: Best way to build a "new" AMD64 current, Walter Vaughan
      • Re: Best way to build a "new" AMD64 current, Garrett Cooper
• LOR in iwi with new 802.11 work, Stefan Ehmann
  • Re: LOR in iwi with new 802.11 work, Sam Leffler
    • LOR in iwi with new 802.11 work, Stefan Ehmann
      • Re: LOR in iwi with new 802.11 work, Andrew Thompson
      • Re: LOR in iwi with new 802.11 work, Stefan Ehmann
      • Re: LOR in iwi with new 802.11 work, Sam Leffler
      • Re: LOR in iwi with new 802.11 work, Stefan Ehmann
      • Re: LOR in iwi with new 802.11 work, Sam Leffler
      • Re: LOR in iwi with new 802.11 work, Jeremie Le Hen
• panic in drm_ioctl, Michiel Boland
  • Re: panic in drm_ioctl, Stefan Ehmann
• Re: smb related problem, Takanori Saneto
  • Re: smb related problem, John Baldwin
    • Re: smb related problem, Takanori Saneto
      • Re: smb related problem, John Baldwin
      • Re: smb related problem, Takanori Saneto
• Disappearing userland output with -current, Gary Jennejohn
  • Re: Disappearing userland output with -current, Michal Mertl
  • Re: Disappearing userland output with -current, Matthew D. Fuller
    • Re: Disappearing userland output with -current, Gary Jennejohn
      • Re: Disappearing userland output with -current, Matthew D. Fuller
  • Re: Disappearing userland output with -current, Ivan Voras
    • Re: Disappearing userland output with -current, Gary Jennejohn
  • Re: Disappearing userland output with -current, Hidetoshi Shimokawa
    • Re: Disappearing userland output with -current, Gary Jennejohn
• BIND 9.4.1 performance on FreeBSD 6.2 vs. 7.0, Kris Kennaway
  • Re: BIND 9.4.1 performance on FreeBSD 6.2 vs. 7.0, Chuck Swiger
    • Re: BIND 9.4.1 performance on FreeBSD 6.2 vs. 7.0, Kris Kennaway
      • Re: BIND 9.4.1 performance on FreeBSD 6.2 vs. 7.0, Chuck Swiger
• i386/i386/busdma_machdep.c 1.88 breaks isp, Charles DeBardeleben
  • Re: i386/i386/busdma_machdep.c 1.88 breaks isp, Scott Long
  • Message not available
    • Re: i386/i386/busdma_machdep.c 1.88 breaks isp, Manfred Antar
      • Re: i386/i386/busdma_machdep.c 1.88 breaks isp, Matthew Jacob
• ath device appears broken, Steve Kargl
  • Re: ath device appears broken, Andrew Thompson
  • Re: ath device appears broken, Sam Leffler
    • Re: ath device appears broken, Steve Kargl
      • Re: ath device appears broken, Sam Leffler
      • Re: ath device appears broken, Steve Kargl
      • Re: ath device appears broken, Sam Leffler
• KTR and SCTP, Randall Stewart
  • Re: KTR and SCTP, Kris Kennaway
    • Re: KTR and SCTP, Randall Stewart
      • Re: KTR and SCTP, Kris Kennaway
      • Re: KTR and SCTP, Randall Stewart
      • Re: KTR and SCTP, Randall Stewart
      • Re: KTR and SCTP, Attilio Rao
      • Re: KTR and SCTP, Randall Stewart
• old bugs, Volodymyr Kostyrko
  • Re: old bugs, Dave Grochowski
• ZFS tuning tips?, Craig Boston
  • Re: ZFS tuning tips?, Kris Kennaway
    • Re: ZFS tuning tips?, Craig Boston
  • Re: ZFS tuning tips?, Eric Anholt
    • Dualhead with nv (was Re: ZFS tuning tips?), Craig Boston
  • Re: ZFS tuning tips?, Stefan Esser
• (Delayed) HEADS UP: AUDIT in GENERIC, Robert Watson
• HEADS UP: IPX over IP support removed, Robert Watson
  • Re: HEADS UP: IPX over IP support removed, Bruce M. Simpson
    • Re: HEADS UP: IPX over IP support removed, Robert Watson
    • Re: HEADS UP: IPX over IP support removed, Julian H. Stacey
  • Re: HEADS UP: IPX over IP support removed, Andrew Pantyukhin
  • Re: HEADS UP: IPX over IP support removed, Maksim Yevmenkin
    • Re: HEADS UP: IPX over IP support removed, Bernd Walter
      • Re: HEADS UP: IPX over IP support removed, Maksim Yevmenkin
  • Re: HEADS UP: IPX over IP support removed, M. Warner Losh
    • Re: HEADS UP: IPX over IP support removed, Maksim Yevmenkin
• RFC: diff(1) update, LI Xin
  • Re: RFC: diff(1) update, Chuck Swiger
    • Re: RFC: diff(1) update, LI Xin
      • Re: RFC: diff(1) update, Chuck Swiger
• Call for testers, amd64 only, new scheduler., Jeff Roberson
  • Message not available
    • Message not available
      • Re: Call for testers, amd64 only, new scheduler., Milos Vyletel
• HPS stack and ural, Marinos Ilias
  • Re: HPS stack and ural, Kip Macy
    • Re: HPS stack and ural, Hans Petter Selasky
      • Re: HPS stack and ural, Jonathan Fosburgh
• HEADS UP: Source-specific multicast code committed to tree, Bruce M Simpson
  • Re: HEADS UP: Source-specific multicast code committed to tree, Julian Elischer
    • Re: HEADS UP: Source-specific multicast code committed to tree, Bruce M Simpson
• Build failure on amd64, Conrad J. Sabatier
  • Re: Build failure on amd64, Conrad J. Sabatier
• HEADS UP: nfe(4), Default NVIDIA nForce MCP Ethernet Driver., Pyun YongHyeon
• nfe(4) strangeness on the 7-CURRENT, Eygene Ryabinkin
  • Re: nfe(4) strangeness on the 7-CURRENT, Andre Oppermann
    • Re: nfe(4) strangeness on the 7-CURRENT, Eygene Ryabinkin
      • Re: nfe(4) strangeness on the 7-CURRENT, Eygene Ryabinkin
      • Re: nfe(4) strangeness on the 7-CURRENT, Andre Oppermann
      • Connections in the CLOSED state [was: nfe(4) strangeness on the 7-CURRENT], Eygene Ryabinkin
• IBM serveraid ipsstat physical drive state values, Martin Blapp
  • RE: IBM serveraid ipsstat physical drive state values, Jan Mikkelsen
    • RE: IBM serveraid ipsstat physical drive state values, Martin Blapp
• "rtfree: %p has 1 refs", Poul-Henning Kamp
  • Re: "rtfree: %p has 1 refs", Rong-en Fan
    • Re: "rtfree: %p has 1 refs", Bruce M. Simpson
• make release on current ends with "No space left on device" md1 + umount /mnt + mdconfig -d -u md1 *** Error code 1 S, eculp
• new wpa_supplcant and hostapd coming, Sam Leffler
  • Re: new wpa_supplcant and hostapd coming, Henrik Brix Andersen
    • Re: new wpa_supplcant and hostapd coming, Nikolay Pavlov
    • Re: new wpa_supplcant and hostapd coming, Rui Paulo
    • Re: new wpa_supplcant and hostapd coming, Sam Leffler
      • Re: new wpa_supplcant and hostapd coming, Henrik Brix Andersen
  • Re: new wpa_supplcant and hostapd coming, Andrey V. Elsukov
• HEADSUP: new 802.11 work committed, Sam Leffler
  • Re: HEADSUP: new 802.11 work committed, David Wolfskill
    • Re: HEADSUP: new 802.11 work committed, John Nielsen
      • Re: HEADSUP: new 802.11 work committed, Maxime Henrion
    • Re: HEADSUP: new 802.11 work committed, Andrew Thompson
• sun4v Tinderbox !, Nikolay Kalev
  • Re: sun4v Tinderbox !, Kip Macy
    • Re: sun4v Tinderbox !, David Xu
      • Re: sun4v Tinderbox !, Nikolay Kalev
• yacc/gdb issues with 7.0-current, Darren Reed
  • Re: yacc/gdb issues with 7.0-current, Steve Kargl
    • Re: yacc/gdb issues with 7.0-current, Steve Kargl
• zfs problem, Bakul Shah
  • Re: zfs problem, Claus Guttesen
    • Re: zfs problem, Bakul Shah
• Testing changeset for i386 on amd64?, Xin LI
• AMD64 panic on boot, Chris Lee
  • Re: AMD64 panic on boot, Greg Rivers
    • Re: AMD64 panic on boot, Chris Lee
    • Re: AMD64 panic on boot, Garrett Cooper
• Don't know what I was doing but..., Randall Stewart
  • Re: Don't know what I was doing but..., Attilio Rao
    • Re: Don't know what I was doing but..., Attilio Rao
      • Re: Don't know what I was doing but..., Randall Stewart
• Archives of this list, Walter Vaughan
  • Re: Archives of this list, Giorgos Keramidas
  • Re: Archives of this list, Ed Schouten
• panic: mutex process slock not owned ..., Marcel Moolenaar
  • Re: panic: mutex process slock not owned ..., Attilio Rao
• snd_es137x & -CURRENT, /dev/dsp: Invalid argument -- Could not mmap /dev/dsp - linux emulation problem?, Hugo Silva
  • Re: snd_es137x & -CURRENT, /dev/dsp: Invalid argument -- Could not mmap /dev/dsp - linux emulation problem?, Ariff Abdullah
    • Re: snd_es137x & -CURRENT, /dev/dsp: Invalid argument -- Could not mmap /dev/dsp - linux emulation problem?, Hugo Silva
    • Re: snd_es137x & -CURRENT, /dev/dsp: Invalid argument -- Could not mmap /dev/dsp - linux emulation problem?, Roman Divacky
• GPT - (last) call for action, Ivan Voras
  • Re: GPT - (last) call for action, Marcel Moolenaar
    • Message not available
      • Re: GPT - (last) call for action, Marcel Moolenaar
      • Re: GPT - (last) call for action, Matthew Dillon
      • Re: GPT - (last) call for action, Ivan Voras
      • Re: GPT - (last) call for action, Marcel Moolenaar
      • Re: GPT - (last) call for action, Matthew Dillon
      • Re: GPT - (last) call for action, Marcel Moolenaar
      • Re: GPT - (last) call for action, Rui Paulo
      • Re: GPT - (last) call for action, Matthew Dillon
      • Re: GPT - (last) call for action, Rui Paulo
      • Re: GPT - (last) call for action, Ivan Voras
      • Re: GPT - (last) call for action, Chuck Swiger
      • Re: GPT - (last) call for action, Rui Paulo
      • Re: GPT - (last) call for action, Chuck Swiger
      • Re: GPT - (last) call for action, Matthew Dillon
      • Re: GPT - (last) call for action, Ivan Voras
      • Re: GPT - (last) call for action, Rui Paulo
      • Re: GPT - (last) call for action, Rui Paulo
      • Re: GPT - (last) call for action, Rui Paulo
• HEADS UP: a change to pam_nologin(8), Yar Tikhiy
• a gdb patch for fbsd, Zhouyi Zhou
• Threading breaking FreeBSD Foundation's Java?, Walter Vaughan
  • Re: Threading breaking FreeBSD Foundation's Java?, Daniel Eischen
    • Re: Threading breaking FreeBSD Foundation's Java?, Kris Kennaway
      • Re: Threading breaking FreeBSD Foundation's Java?, Walter Vaughan
      • Re: Threading breaking FreeBSD Foundation's Java?, Kris Kennaway
      • Re: Threading breaking FreeBSD Foundation's Java?, Marcus Alves Grando
      • Re: Threading breaking FreeBSD Foundation's Java?, Walter Vaughan
      • Re: Threading breaking FreeBSD Foundation's Java?, Abdullah Ibn Hamad Al-Marri
      • Re: Threading breaking FreeBSD Foundation's Java?, Scott Robbins
• zfs drive configurations?, Josef Karthauser
  • Re: zfs drive configurations?, Bakul Shah
    • Re: zfs drive configurations?, Josef Karthauser
      • Re: zfs drive configurations?, Dan Nelson
      • Re: zfs drive configurations?, Darren Reed
• bge auto-negotiation fails with recent current, Kevin Oberman
  • Re: bge auto-negotiation fails with recent current, Poul-Henning Kamp
    • Re: bge auto-negotiation fails with recent current, Kevin Oberman
    • Re: bge auto-negotiation fails with recent current, Pyun YongHyeon
      • Re: bge auto-negotiation fails with recent current, Matthew Jacob
      • Re: bge auto-negotiation fails with recent current, Kevin Oberman
  • RE: bge auto-negotiation fails with recent current, David Christensen
• ATAPI DVD writer wont operate in DMA mode, Tom Evans
  • Re: ATAPI DVD writer wont operate in DMA mode, Scott Long
    • Re: ATAPI DVD writer wont operate in DMA mode, Tom Evans
• Re: nscd for freebsd, Dmitriy Kirhlarov
• Jun 7.0-CURRENT AMD64 snapshot, Abdullah Ibn Hamad Al-Marri
  • Re: Jun 7.0-CURRENT AMD64 snapshot, Oliver Fromme
    • Re: Jun 7.0-CURRENT AMD64 snapshot, Abdullah Ibn Hamad Al-Marri
      • Re: Jun 7.0-CURRENT AMD64 snapshot, Kris Kennaway
      • Re: Jun 7.0-CURRENT AMD64 snapshot, Abdullah Ibn Hamad Al-Marri
      • Re: Jun 7.0-CURRENT AMD64 snapshot, Kris Kennaway
• rcNG multi-server service dependencies, Dmitriy Kirhlarov
  • Re: rcNG multi-server service dependencies, Peter Jeremy
• panic when removing pccard, Niki Denev
  • Re: panic when removing pccard, Hans Petter Selasky
    • Re: panic when removing pccard, M. Warner Losh
      • Re: panic when removing pccard, Hans Petter Selasky
    • Re: panic when removing pccard, Niki Denev
      • Re: panic when removing pccard, Hans Petter Selasky
      • Re: panic when removing pccard, Niki Denev
      • Re: panic when removing pccard, Hans Petter Selasky
      • Re: panic when removing pccard, Niki Denev
      • Re: panic when removing pccard, Hans Petter Selasky
      • Re: panic when removing pccard, Niki Denev
      • Re: panic when removing pccard, Hans Petter Selasky
      • Re: panic when removing pccard, M. Warner Losh
      • Re: panic when removing pccard, Niki Denev
      • Re: panic when removing pccard, Niki Denev
      • Re: panic when removing pccard, M. Warner Losh
      • Re: panic when removing pccard, Niki Denev
  • Re: panic when removing pccard, M. Warner Losh
    • Re: panic when removing pccard, Pete Carah
      • Re: panic when removing pccard, Hans Petter Selasky
    • Re: panic when removing pccard, Niki Denev
• Connections problem, Arek Czereszewski
• libgpg-error doesn't build with new nawk, Yuri Pankov
  • Re: libgpg-error doesn't build with new nawk, Rong-en Fan
• ddclient on startup, Curtis Vaughan
  • Re: ddclient on startup, Daniel O'Connor
  • Re: ddclient on startup, Stefan Ehmann
• ZFS compatibility, Joe S
  • Re: ZFS compatibility, Claus Guttesen
  • Re: ZFS compatibility, Peter Schuller
• CTF: compat6x port, Marcus Alves Grando
  • Re: CTF: compat6x port, illoai@xxxxxxxxx
    • Re: CTF: compat6x port, Lars Engels
      • Re: CTF: compat6x port, Ion-Mihai Tetcu
  • Re: CTF: compat6x port, Gary Jennejohn
  • Re: CTF: compat6x port, Abdullah Ibn Hamad Al-Marri
    • Re: CTF: compat6x port, Marcus Alves Grando
      • Re: CTF: compat6x port, Abdullah Ibn Hamad Al-Marri
• Re: persistent problem with buildworld on -CURRENT, Tom Evans
• if_msk "failed to allocate DMA'able memory for jumbo buf", Ian FREISLICH
  • Re: if_msk "failed to allocate DMA'able memory for jumbo buf", Pyun YongHyeon
  • <Possible follow-ups>
  • Re: if_msk "failed to allocate DMA'able memory for jumbo buf", Ian FREISLICH
• Why not remove polling(4) from 7.0?, Abdullah Ibn Hamad Al-Marri
  • Re: Why not remove polling(4) from 7.0?, Andrew Thompson
    • Re: Why not remove polling(4) from 7.0?, Abdullah Ibn Hamad Al-Marri
      • Re: Why not remove polling(4) from 7.0?, Chuck Swiger
      • Re: Why not remove polling(4) from 7.0?, Abdullah Ibn Hamad Al-Marri
      • Re: Why not remove polling(4) from 7.0?, Chuck Swiger
      • Re: Why not remove polling(4) from 7.0?, Astrodog
  • Re: Why not remove polling(4) from 7.0?, Julian H. Stacey
• Panic in ipfw, Ian FREISLICH
  • Re: Panic in ipfw, Julian Elischer
  • <Possible follow-ups>
  • Re: Panic in ipfw, Ian FREISLICH
• md(4) broken on CURRENT?, Kazuaki ODA
  • Re: md(4) broken on CURRENT?, youshi10
    • Re: md(4) broken on CURRENT?, youshi10
      • Re: md(4) broken on CURRENT?, illoai@xxxxxxxxx
      • Re: md(4) broken on CURRENT?, Kazuaki ODA
• gjournal + WARNING: R/W mount of / denied. Filesystem not clean - run fsck., Niki Denev
  • Re: gjournal + WARNING: R/W mount of / denied. Filesystem not clean - run fsck., Wilkinson, Alex
    • Re: gjournal + WARNING: R/W mount of / denied. Filesystem not clean - run fsck., Niki Denev
      • Re: gjournal + WARNING: R/W mount of / denied. Filesystem not clean - run fsck., Niki Denev
      • Re: gjournal + WARNING: R/W mount of / denied. Filesystem not clean - run fsck., illoai@xxxxxxxxx
      • Re: gjournal + WARNING: R/W mount of / denied. Filesystem not clean - run fsck., Niki Denev
      • Re: gjournal + WARNING: R/W mount of / denied. Filesystem not clean - run fsck., Niki Denev
      • Anyone using gjournal for root fs? [was : gjournal + WARNING: R/W mount of / denied. Filesystem not clean - run fsck.], Niki Denev
• HEADS UP: Plan to MFC new em driver, Jack Vogel
  • RE: HEADS UP: Plan to MFC new em driver, David Christensen
    • Re: HEADS UP: Plan to MFC new em driver, Kip Macy
  • Re: HEADS UP: Plan to MFC new em driver, Jack Vogel
    • Re: HEADS UP: Plan to MFC new em driver, youshi10
• USER/GROUP rules on the chopping Block [ Re: Panic on boot with April 16 src (lengthy info attached) ], Max Laier
  • Re: USER/GROUP rules on the chopping Block [ Re: Panic on boot with April 16 src (lengthy info attached) ], Chris Marlatt
    • Re: USER/GROUP rules on the chopping Block [ Re: Panic on boot with April 16 src (lengthy info attached) ], Max Laier
  • Re: USER/GROUP rules on the chopping Block [ Re: Panic on boot with April 16 src (lengthy info attached) ], Tillman Hodgson
    • Re: USER/GROUP rules on the chopping Block [ Re: Panic on boot with April 16 src (lengthy info attached) ], Max Laier
      • Re: USER/GROUP rules on the chopping Block [ Re: Panic on boot with April 16 src (lengthy info attached) ], Tillman Hodgson
  • Re: USER/GROUP rules on the chopping Block [ Re: Panic on boot with April 16 src (lengthy info attached) ], ttw+bsd
  • Re: USER/GROUP rules on the chopping Block [ Re: Panic on boot with April 16 src (lengthy info attached) ], Jeremy C. Reed
  • Re: USER/GROUP rules on the chopping Block [ Re: Panic on boot with April 16 src (lengthy info attached) ], Volker
  • Re: USER/GROUP rules on the chopping Block, Volker
• /boot/mbr miscompiled?, Yuri Pankov
  • Re: /boot/mbr miscompiled?, Ruben de Groot
    • Re: /boot/mbr miscompiled?, Yuri Pankov
  • Re: /boot/mbr miscompiled?, Ruslan Ermilov
    • Re: /boot/mbr miscompiled?, Yuri Pankov
      • Re: /boot/mbr miscompiled?, Ruslan Ermilov
      • Re: /boot/mbr miscompiled?, Pav Lucistnik
      • Re: /boot/mbr miscompiled?, Warren Block
      • Re: /boot/mbr miscompiled?, Pav Lucistnik
• VOP_OPEN(): fdidx -> fp => __FreeBSD_version++ ?, Csaba Henk
  • Re: VOP_OPEN(): fdidx -> fp => __FreeBSD_version++ ?, Kostik Belousov
• iSCSI initiator tester wanted, Danny Braniss
  • Re: iSCSI initiator tester wanted, Ivan Voras
    • Re: iSCSI initiator tester wanted, John Nielsen
  • Re: iSCSI initiator tester wanted, Ivan Voras
  • <Possible follow-ups>
  • Re: iSCSI initiator tester wanted, Danny Braniss
    • Re: iSCSI initiator tester wanted, John Nielsen
      • Re: iSCSI initiator tester wanted, Danny Braniss
  • Re: iSCSI initiator tester wanted, John Nielsen
  • Re: iSCSI initiator tester wanted, Nathan Butcher
    • Re: iSCSI initiator tester wanted, Joe Holden
      • Re: iSCSI initiator tester wanted, Nathan Butcher
    • Re: iSCSI initiator tester wanted, Ivan Voras
• INCLUDE_CONFIG_FILE off-by-one problem, Danny Braniss
  • Re: INCLUDE_CONFIG_FILE off-by-one problem, Wojciech A. Koszek
  • <Possible follow-ups>
  • Re: INCLUDE_CONFIG_FILE off-by-one problem, Danny Braniss
    • Re: INCLUDE_CONFIG_FILE off-by-one problem, Wojciech A. Koszek
  • Re: INCLUDE_CONFIG_FILE off-by-one problem, Danny Braniss
• ZFS on 32-bit CPUs?, Sean Hafeez
  • Re: ZFS on 32-bit CPUs?, Ivan Voras
    • Re: ZFS on 32-bit CPUs?, Kris Kennaway
      • Re: ZFS on 32-bit CPUs?, Kris Kennaway
      • Re: ZFS on 32-bit CPUs?, Alexander Leidinger
• arcmsr crash, Matt Reimer
• kernel linking, Krassimir Slavchev
  • Re: kernel linking, Attilio Rao
    • Message not available
      • Re: kernel linking, Garrett Cooper
    • Re: kernel linking, Krassimir Slavchev
      • Re: kernel linking, Attilio Rao
  • Re: kernel linking, Björn König
• nspluginwrapper and linux-flashplayer9 on -CURRENT, Jeremie Le Hen
  • Re: nspluginwrapper and linux-flashplayer9 on -CURRENT, Benjamin Close
    • Re: nspluginwrapper and linux-flashplayer9 on -CURRENT, Sam Fourman Jr.
  • Re: nspluginwrapper and linux-flashplayer9 on -CURRENT, Roman Divacky
• automatik make tree error corrector - automatischer mach baum fehler korrigierer, Tino Engel
• HEADS UP: threadlock going in, likely tonight., Jeff Roberson
  • Re: HEADS UP: threadlock going in, likely tonight., Jeff Roberson
    • Re: HEADS UP: threadlock going in, likely tonight., Jeff Roberson
      • Re: HEADS UP: threadlock going in, likely tonight., youshi10
      • Re: HEADS UP: threadlock going in, likely tonight., Abdullah Ibn Hamad Al-Marri
• CISS(4) dumps core at shutdown, Per olof Ljungmark
  • Re: CISS(4) dumps core at shutdown, Scott Long
• Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Abdullah Ibn Hamad Al-Marri
  • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Alexey Tarasov
    • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Abdullah Ibn Hamad Al-Marri
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Alexey Tarasov
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Kris Kennaway
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, youshi10
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Abdullah Ibn Hamad Al-Marri
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Attilio Rao
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Abdullah Ibn Hamad Al-Marri
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Attilio Rao
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Abdullah Ibn Hamad Al-Marri
    • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Jeff Roberson
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Abdullah Ibn Hamad Al-Marri
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Oliver Fromme
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Ed Schouten
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Diego Depaoli
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Garrett Cooper
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Joel Dahl
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, youshi10
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Sean C. Farley
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Alexander Leidinger
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Joel Dahl
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Marius Nuennerich
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Joel Dahl
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Alexander Leidinger
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Wilkinson, Alex
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Joel Dahl
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Kurt Jaeger
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, eculp
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Wesley Shields
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, eculp
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, youshi10
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Doug Barton
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, youshi10
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Kenneth P. Stox
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, eculp
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, youshi10
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, youshi10
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Dag-Erling Smørgrav
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Freddie Cash
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, eculp
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Adam K Kirchhoff
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, eculp
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, youshi10
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Tom Evans
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Garrett Cooper
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Dimitry Andric
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, youshi10
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Dag-Erling Smørgrav
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Dag-Erling Smørgrav
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Abdullah Ibn Hamad Al-Marri
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Dag-Erling Smørgrav
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Robert Huff
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Vince
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Daniel O'Connor
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Yuri Pankov
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Doug Ambrisko
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, youshi10
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Darren Pilgrim
      • ports broken on amd64 [was: Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386], Mark Linimon
      • Re: ports broken on amd64 [was: Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386], Darren Pilgrim
      • Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386, Abdullah Ibn Hamad Al-Marri
• failed to build java/jdk15 on recent current - gcc4 issue ?, Vladimir Grebenschikov
  • Re: failed to build java/jdk15 on recent current - gcc4 issue ?, Greg Lewis
  • Re: failed to build java/jdk15 on recent current - gcc4 issue ?, Don Lewis
    • Re: failed to build java/jdk15 on recent current - gcc4 issue ?, Greg Lewis
• Fw: Crash during sending print jobs, S.N.Grigoriev
• Re: ZFS does not load and mount at boot time, Gerrit Kühn
  • Re: ZFS does not load and mount at boot time, Gerrit Kühn
    • Re: ZFS does not load and mount at boot time, Darren Reed
  • <Possible follow-ups>
  • Re: ZFS does not load and mount at boot time, Borja Marcos
    • Re: ZFS does not load and mount at boot time, Craig Boston
• Spam: Re: watch(8) stuck in devdrn, Wilkinson, Alex
• if_iwi: gone? HELP!, O. Hartmann
  • Re: if_iwi: gone? HELP!, Andrew Thompson
• [net/citrix_ica/] /usr/local/bin/wfcmgr ... hangs upon exec() [ptsopn], Wilkinson, Alex
  • Re: [net/citrix_ica/] /usr/local/bin/wfcmgr ... hangs upon exec() [ptsopn], Boris Samorodov
    • Re: [net/citrix_ica/] /usr/local/bin/wfcmgr ... hangs upon exec() [ptsopn], Wilkinson, Alex
• IPFilter updated in HEAD, Darren Reed
• Kudos to everyone who worked on the gcc-4.2 merge, youshi10
  • Re: Kudos to everyone who worked on the gcc-4.2 merge, Alexander Kabaev
    • Re: Kudos to everyone who worked on the gcc-4.2 merge, Joao Barros
      • Re: Kudos to everyone who worked on the gcc-4.2 merge, Garrett Cooper
      • Re: Kudos to everyone who worked on the gcc-4.2 merge, Garrett Cooper
    • Re: Kudos to everyone who worked on the gcc-4.2 merge, Garrett Cooper
  • Re: Kudos to everyone who worked on the gcc-4.2 merge, Philipp Ost
• /usr/share/mk/sys.mk and FORTRAN on -CURRENT, Don Lewis
  • Re: /usr/share/mk/sys.mk and FORTRAN on -CURRENT, Steve Kargl
    • Re: /usr/share/mk/sys.mk and FORTRAN on -CURRENT, Garrett Cooper
      • Re: /usr/share/mk/sys.mk and FORTRAN on -CURRENT, Steve Kargl
    • Re: /usr/share/mk/sys.mk and FORTRAN on -CURRENT, Bob Bishop
      • Re: /usr/share/mk/sys.mk and FORTRAN on -CURRENT, Steve Kargl
      • Re: /usr/share/mk/sys.mk and FORTRAN on -CURRENT, Bob Bishop
      • Re: /usr/share/mk/sys.mk and FORTRAN on -CURRENT, Don Lewis
• FreeBSD 7.0-CURRENT weird msgs, Abdullah Ibn Hamad Al-Marri
  • Re: FreeBSD 7.0-CURRENT weird msgs, Ivan Voras
  • Re: FreeBSD 7.0-CURRENT weird msgs, Garrett Cooper
• Couldn't build a release with this morning's sources md1 fixit floppy space problem., eculp
  • Re: Couldn't build a release with this morning's sources md1 fixit floppy space problem., eculp
    • Re: Couldn't build a release with this morning's sources md1 fixit floppy space problem., Garrett Cooper
      • Re: Couldn't build a release with this morning's sources md1 fixit floppy space problem., eculp
• panic in tulip_rx_intr after recent changes, Arne H Juul
  • Re: panic in tulip_rx_intr after recent changes, Pyun YongHyeon
  • Re: panic in tulip_rx_intr after recent changes, Pyun YongHyeon
• Re: ifconfig carp0 destroy = kernel panic, Ed Schouten
  • Message not available
    • Re: ifconfig carp0 destroy = kernel panic, Gleb Smirnoff
• Re: xorg 7.2 & environment variables set in login.conf, Neil Short
  • Re: xorg 7.2 & environment variables set in login.conf, Thomas-Martin Seck
  • Re: xorg 7.2 & environment variables set in login.conf, Stefan Esser
    • Re: xorg 7.2 & environment variables set in login.conf, youshi10
      • Re: xorg 7.2 & environment variables set in login.conf, Dag-Erling Smørgrav
    • Re: xorg 7.2 & environment variables set in login.conf, Neil Short
      • Re: xorg 7.2 & environment variables set in login.conf, Kevin Oberman
      • Re: xorg 7.2 & environment variables set in login.conf, Doug Barton
      • Re: xorg 7.2 & environment variables set in login.conf, Yuri Pankov
      • Re: xorg 7.2 & environment variables set in login.conf, Doug Barton
• ath0: using obsoleted if_watchdog interface, Neil Short
  • Re: ath0: using obsoleted if_watchdog interface, Sam Leffler
• Q) diablo-jdk1.5.0 dumps core @ -current, Ken Yamada
• HEADS UP: BIND 9.4.1 imported, Doug Barton
  • Re: HEADS UP: BIND 9.4.1 imported, Kris Kennaway
    • Re: HEADS UP: BIND 9.4.1 imported, Chuck Swiger
      • Re: HEADS UP: BIND 9.4.1 imported, Kris Kennaway
  • Re: HEADS UP: BIND 9.4.1 imported, Anton Yuzhaninov
    • Re: HEADS UP: BIND 9.4.1 imported, Doug Barton
      • Re: HEADS UP: BIND 9.4.1 imported, Bjoern A. Zeeb
      • Re: HEADS UP: BIND 9.4.1 imported, LI Xin
      • Re: HEADS UP: BIND 9.4.1 imported (no threading libs), Bjoern A. Zeeb
      • Re: HEADS UP: BIND 9.4.1 imported (no threading libs), LI Xin
      • Re: HEADS UP: BIND 9.4.1 imported (no threading libs), Ruslan Ermilov
• Re: HPET vs other timers, Kris Kennaway
  • Re: HPET vs other timers, Nate Lawson
    • Re: HPET vs other timers, Kris Kennaway
      • Re: HPET vs other timers, Larry Rosenman
  • Re: HPET vs other timers, Poul-Henning Kamp
    • Re: HPET vs other timers, Kris Kennaway
      • Re: HPET vs other timers, Poul-Henning Kamp
    • Re: HPET vs other timers, Nate Lawson
      • Re: HPET vs other timers, Poul-Henning Kamp
• su(1) suspends the process, Peter Jeremy
• "-pthread" == "-lpthread" for shared libs in -CURRENT, Vladimir Kushnir
  • Re: "-pthread" == "-lpthread" for shared libs in -CURRENT, Daniel Eischen
  • Re: "-pthread" == "-lpthread" for shared libs in -CURRENT, Alexander Kabaev
    • Re: "-pthread" == "-lpthread" for shared libs in -CURRENT, Vladimir Kushnir
  • Re: "-pthread" == "-lpthread" for shared libs in -CURRENT, Jeremie Le Hen
    • Re: "-pthread" == "-lpthread" for shared libs in -CURRENT, Alexander Kabaev
      • Re: "-pthread" == "-lpthread" for shared libs in -CURRENT, Alexander Leidinger
      • Re: "-pthread" == "-lpthread" for shared libs in -CURRENT, Alexander Kabaev
      • Re: "-pthread" == "-lpthread" for shared libs in -CURRENT, Alexander Leidinger
  • <Possible follow-ups>
  • "-pthread" == "-lpthread" for shared libs in -CURRENT, Vladimir Kushnir
    • Re: "-pthread" == "-lpthread" for shared libs in -CURRENT, Kris Kennaway
• nfe(4) vs. nve(4), Pyun YongHyeon
  • Re: nfe(4) vs. nve(4), Sam Leffler
  • Re: nfe(4) vs. nve(4), Yuri Pankov
    • Re: nfe(4) vs. nve(4), Pyun YongHyeon
  • Re: nfe(4) vs. nve(4), Rainer Hurling
  • Re: nfe(4) vs. nve(4), Ivan Voras
    • Re: nfe(4) vs. nve(4), Ivan Voras
      • Re: nfe(4) vs. nve(4), Pyun YongHyeon
  • Re: nfe(4) vs. nve(4), Gleb Smirnoff
  • Re: nfe(4) vs. nve(4), Gelsema, P \(Patrick\)
• Re: CFT: re(4), Pyun YongHyeon
  • Re: CFT: re(4), Pyun YongHyeon
• locale woes, Neil Short
• Dev isp hangs on current, Manfred Antar
  • Re: Dev isp hangs on current, Matthew Jacob
    • Re: Dev isp hangs on current, Matthew Jacob
      • Message not available
      • Re: Dev isp hangs on current, Manfred Antar
  • Re: Dev isp hangs on current, mjacob
• Re: MacBook patches, Arne Schwabe
  • Re: MacBook patches, Rui Paulo
    • Re: MacBook patches, Arne Schwabe
      • Re: MacBook patches, Rui Paulo
      • Re: MacBook patches, Maxim Sobolev
      • Re: MacBook patches, Joe Marcus Clarke
      • Re: MacBook patches, Rui Paulo
      • Re: MacBook patches, Arne Schwabe
      • Re: MacBook patches, Ian FREISLICH
      • Re: MacBook patches, Rui Paulo
      • Re: MacBook patches, Tyler Gee
  • Re: MacBook patches, Rui Paulo
  • <Possible follow-ups>
  • Re: MacBook patches, Rui Paulo
    • Re: MacBook patches, Joe Marcus Clarke
      • Re: MacBook patches, Rui Paulo
      • Re: MacBook patches, Rui Paulo
      • Re: MacBook patches, Rui Paulo
      • Re: MacBook patches, Joe Marcus Clarke
• Issues with kernel / userland drivers after recent install and upgrade, youshi10
  • Re: Issues with kernel / userland drivers after recent install and upgrade, illoai@xxxxxxxxx
    • Re: Issues with kernel / userland drivers after recent install and upgrade, youshi10
      • Re: Issues with kernel / userland drivers after recent install and upgrade, youshi10
      • Re: Issues with kernel / userland drivers after recent install and upgrade, youshi10
      • Re: Issues with kernel / userland drivers after recent install and upgrade, youshi10
• CFT: major wireless changes, Sam Leffler
  • Re: CFT: major wireless changes, Olivier Warin
    • Re: CFT: major wireless changes, Sam Leffler
      • Re: CFT: major wireless changes, Olivier Warin
      • Re: CFT: major wireless changes, Sam Leffler
  • Re: CFT: major wireless changes, Arne Schwabe
    • Re: CFT: major wireless changes, Sam Leffler
  • Re: CFT: major wireless changes, Stefan Ehmann
    • Re: CFT: major wireless changes, Sam Leffler
      • Re: CFT: major wireless changes, Stefan Ehmann
  • Re: CFT: major wireless changes, David Wolfskill
    • Re: CFT: major wireless changes, David Wolfskill
    • Re: CFT: major wireless changes, David Wolfskill
  • Re: CFT: major wireless changes, Lev Serebryakov
    • Re: CFT: major wireless changes, Sam Leffler
  • Re: CFT: major wireless changes, Yuri Lukin
    • Re: CFT: major wireless changes, Sam Leffler
  • Re: CFT: major wireless changes, Wilkinson, Alex
    • Re: CFT: major wireless changes, Sepherosa Ziehau
  • CFT: major wireless changes #2, Andrew Thompson
    • Re: CFT: major wireless changes #2, Maxim Konovalov
      • Re: CFT: major wireless changes #2, Sam Leffler
      • Re: CFT: major wireless changes #2, Maxim Konovalov
      • Re: CFT: major wireless changes #2, Andrew Thompson
      • Re: CFT: major wireless changes #2, Maxim Konovalov
      • Re: CFT: major wireless changes #2, Maxim Konovalov
• panic when detecting an ES1373 AudioPCI sound card, Thierry Herbelot
  • Re: panic when detecting an ES1373 AudioPCI sound card, Ariff Abdullah
    • Re: panic when detecting an ES1373 AudioPCI sound card, Thierry Herbelot
      • Re: panic when detecting an ES1373 AudioPCI sound card, Ariff Abdullah
• Debugging FreeBSD 7.0 How to savecore in rc.conf?, Abdullah Ibn Hamad Al-Marri
  • Re: Debugging FreeBSD 7.0 How to savecore in rc.conf?, Dominic Marks
• pf(4) status in 7.0-R, Stanislaw Halik
  • Re: pf(4) status in 7.0-R, LI Xin
    • Re: pf(4) status in 7.0-R, Stanislaw Halik
    • Re: pf(4) status in 7.0-R, Hugo Silva
    • Re: pf(4) status in 7.0-R, Max Laier
      • Re: pf(4) status in 7.0-R, Henrik Brix Andersen
      • Re: pf(4) status in 7.0-R, Max Laier
      • RE: pf(4) status in 7.0-R, Greg Hennessy
      • Re: pf(4) status in 7.0-R, Max Laier
      • Re: pf(4) status in 7.0-R, Andre Oppermann
      • Re: pf(4) status in 7.0-R, Max Laier
      • Re: pf(4) status in 7.0-R, Michal Mertl
      • Re: pf(4) status in 7.0-R, Max Laier
      • Re: pf(4) status in 7.0-R, LI Xin
      • Re: pf(4) status in 7.0-R, Gergely CZUCZY
      • Re: pf(4) status in 7.0-R, Max Laier
      • Re: pf(4) status in 7.0-R, Gergely CZUCZY
      • Re: pf(4) status in 7.0-R, Chris Marlatt
      • Re: pf(4) status in 7.0-R, Dag-Erling Smørgrav
      • Re: pf(4) status in 7.0-R, Max Laier
      • Re: pf(4) status in 7.0-R, Dag-Erling Smørgrav
      • Re: pf(4) status in 7.0-R, Max Laier
      • Re: pf(4) status in 7.0-R, Bjoern A. Zeeb
      • Re: pf(4) status in 7.0-R, Doug Barton
      • Re: pf(4) status in 7.0-R, Dag-Erling Smørgrav
      • Re: pf(4) status in 7.0-R, Poul-Henning Kamp
      • Re: pf(4) status in 7.0-R, Julian Elischer
      • Re: pf(4) status in 7.0-R, Julian Elischer
      • Re: pf(4) status in 7.0-R, Roman Divacky
      • Re: pf(4) status in 7.0-R, Max Laier
  • Re: pf(4) status in 7.0-R, Kenneth Vestergaard Schmidt
    • Re: pf(4) status in 7.0-R, Wilkinson, Alex
      • Re: pf(4) status in 7.0-R, Kenneth Vestergaard Schmidt
      • Re: pf(4) status in 7.0-R, Darren Reed
      • Re: pf(4) status in 7.0-R, Abdullah Ibn Hamad Al-Marri
  • Re: pf(4) status in 7.0-R, Brad Davis
    • Re: pf(4) status in 7.0-R, Abdullah Ibn Hamad Al-Marri
• NET_NEEDS_GIANT removal, Robert Watson
  • Re: NET_NEEDS_GIANT removal, Robert Watson
  • Re: NET_NEEDS_GIANT removal, Michael Reifenberger
    • Re: NET_NEEDS_GIANT removal, Robert Watson
    • Re: NET_NEEDS_GIANT removal, Warner Losh
      • Re: NET_NEEDS_GIANT removal, Hans Petter Selasky
  • Re: NET_NEEDS_GIANT removal, Hans Petter Selasky
• Pending TrustedBSD stuff, etc., Robert Watson
  • Re: Pending TrustedBSD stuff, etc., Robert Watson
  • Re: Pending TrustedBSD stuff, etc., Daniel Eischen
  • Re: Pending TrustedBSD stuff, etc., Garance A Drosehn
    • Re: Pending TrustedBSD stuff, etc., Peter Jeremy
      • Re: Pending TrustedBSD stuff, etc., Garance A Drosehn
      • Re: Pending TrustedBSD stuff, etc., Peter Jeremy
• Re: Xorg 7.2 update, illoai@xxxxxxxxx
• Re: Release Engineering plans for 7.0, illoai@xxxxxxxxx
  • <Possible follow-ups>
  • Re: Release Engineering plans for 7.0, Abdullah Ibn Hamad Al-Marri
• Call for testers, significant sched_lock patch., Jeff Roberson
  • Re: Call for testers, significant sched_lock patch., Pieter de Goeje
  • Re: Call for testers, significant sched_lock patch., Abdullah Ibn Hamad Al-Marri
    • Re: Call for testers, significant sched_lock patch., youshi10
• [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
• [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on i386/i386, Bruce M. Simpson
      • Re: [head tinderbox] failure on i386/i386, John-Mark Gurney
      • Re: [head tinderbox] failure on i386/i386, Roman Divacky
      • Re: [head tinderbox] failure on i386/i386, Rui Paulo
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on i386/i386, Henrik Brix Andersen
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on i386/i386, M. Warner Losh
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on i386/i386, M. Warner Losh
• [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on amd64/amd64, Ruslan Ermilov
      • Re: [head tinderbox] failure on amd64/amd64, Doug Barton
      • Re: [head tinderbox] failure on amd64/amd64, John Baldwin
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on amd64/amd64, Garrett Cooper
      • Re: [head tinderbox] failure on amd64/amd64, Doug Barton
      • Re: [head tinderbox] failure on amd64/amd64, Garrett Cooper
      • Re: [head tinderbox] failure on amd64/amd64, youshi10
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
• [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on arm and amd, Doug Barton
      • Re: [head tinderbox] failure on arm and amd, Bernd Walter
      • Re: [head tinderbox] failure on arm and amd, M. Warner Losh
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on arm/arm, Doug Barton
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on sparc64/sun4v, Kip Macy
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on sparc64/sun4v, M. Warner Losh
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on sparc64/sparc64, Doug Barton
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on sparc64/sparc64, Bruce M. Simpson
      • Re: [head tinderbox] failure on sparc64/sparc64, Bruce M. Simpson
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
• Busted world?, Larry Rosenman
  • Re: Busted world?, Jeff Roberson
• [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
• [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on ia64/ia64, Steve Kargl
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
• Re: The mailman bug, Daniel O'Connor
• Re: watch(8) stuck in devdrn, Robert Watson
  • Re: watch(8) stuck in devdrn, Hidetoshi Shimokawa
    • Re: watch(8) stuck in devdrn, Jiawei Ye
      • Re: watch(8) stuck in devdrn, Tai-hwa Liang
      • Re: watch(8) stuck in devdrn, Yuri Pankov
      • Message not available
      • Re: watch(8) stuck in devdrn, Tai-hwa Liang
• Re: glibmm exceptions broken after recent upgrades on CURRENT (debug info included), Alexander Kabaev
  • Re: glibmm exceptions broken after recent upgrades on CURRENT (debug info included), Ted Faber
    • Re: glibmm exceptions broken after recent upgrades on CURRENT (debug info included), Alexander Nedotsukov
      • Re: glibmm exceptions broken after recent upgrades on CURRENT (debug info included), Ted Faber
      • Re: glibmm exceptions broken after recent upgrades on CURRENT (debug info included), Alexander Nedotsukov
      • Re: glibmm exceptions broken after recent upgrades on CURRENT (debug info included), Ted Faber
    • Re: glibmm exceptions broken after recent upgrades on CURRENT (debug info included), Alexander Kabaev
      • Re: glibmm exceptions broken after recent upgrades on CURRENT (debug info included), Ted Faber
      • Re: glibmm exceptions broken after recent upgrades on CURRENT (debug info included), Ted Faber
• Re: New driver coming soon., Jack Vogel
  • Re: New driver coming soon., Wilkinson, Alex
    • Re: New driver coming soon., Kip Macy
      • Re: New driver coming soon., Bruce Stephens
      • Re: New driver coming soon., Kevin Oberman
    • Re: New driver coming soon., O. Hartmann
      • Re: New driver coming soon., Andre Oppermann
• Samba access to ZFS broken, Stefan Eßer
  • RE: Samba access to ZFS broken, Johan Hendriks
    • Re: Samba access to ZFS broken, Stefan Esser
      • Re: Samba access to ZFS broken, Timur I. Bakeyev

We are proud to have Web Hosting and Rack Housing from 9 Net Avenue Deutschland.
(15)