freebsd-current

• Date Index

---

• csh history and pts, Pawel Worach
  • Re: csh history and pts, Ed Schouten
    • Re: csh history and pts, Giorgos Keramidas
• DTrace on sparc64, Ruben de Groot
  • Re: DTrace on sparc64, Kris Kennaway
• reboot during upgrade, Matkhamtkha Brekher
  • Re: reboot during upgrade, Chuck Swiger
    • Re: reboot during upgrade, Giorgos Keramidas
    • Re: reboot during upgrade, Daniel O'Connor
  • Re: reboot during upgrade, Alexey Shuvaev
• Booting from gpt on i386/amd64?, Alexey Shuvaev
  • Re: Booting from gpt on i386/amd64?, Paul B. Mahol
    • Re: Booting from gpt on i386/amd64?, Alexey Shuvaev
      • Re: Booting from gpt on i386/amd64?, Paul B. Mahol
    • Re: Booting from gpt on i386/amd64? [SOLVED], Alexey Shuvaev
• rtentry panic with FIB, John Baldwin
  • Re: rtentry panic with FIB, Julian Elischer
  • Re: rtentry panic with FIB, Robert Watson
    • Re: rtentry panic with FIB, Julian Elischer
• System, diagnose thyself: auto-documentation for crashes, Kirk Strauser
  • Re: System, diagnose thyself: auto-documentation for crashes, Igor Mozolevsky
  • Re: System, diagnose thyself: auto-documentation for crashes, John Baldwin
    • Re: System, diagnose thyself: auto-documentation for crashes, Kirk Strauser
      • Re: System, diagnose thyself: auto-documentation for crashes, Wes Morgan
      • Re: System, diagnose thyself: auto-documentation for crashes, John Baldwin
      • Re: System, diagnose thyself: auto-documentation for crashes, Kostik Belousov
      • Re: System, diagnose thyself: auto-documentation for crashes, Giorgos Keramidas
  • Re: System, diagnose thyself: auto-documentation for crashes, Ivan Voras
    • Re: System, diagnose thyself: auto-documentation for crashes, Kirk Strauser
• NFSv4 ACLs., Edward Tomasz Napierala
• if_iwi, boot firmware, Armin Pirkovitsch
  • Re: if_iwi, boot firmware, Lothar Braun
    • Re: if_iwi, boot firmware, Armin Pirkovitsch
• SATA disks no longer showing up after updating CURRENT last night, Pascal Hofstee
  • Re: SATA disks no longer showing up after updating CURRENT last night, Andrey V. Elsukov
    • Re: SATA disks no longer showing up after updating CURRENT last night, Pascal Hofstee
  • Re: SATA disks no longer showing up after updating CURRENT last night, Joao Barros
  • Re: SATA disks no longer showing up after updating CURRENT last night, Christian Weisgerber
• HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST, Rui Paulo
• xpt_config panic: run_interrupt_driven_config_hooks: waited too long, Mark Atkinson
  • Re: xpt_config panic: run_interrupt_driven_config_hooks: waited too long, Robert Watson
    • Re: xpt_config panic: run_interrupt_driven_config_hooks: waited too long, Mark Atkinson
  • Re: xpt_config panic: run_interrupt_driven_config_hooks: waited too long, Scott Long
    • Re: xpt_config panic: run_interrupt_driven_config_hooks: waited too long, Mark Atkinson
      • Re: xpt_config panic: run_interrupt_driven_config_hooks: waited too long, Scott Long
      • Re: xpt_config panic: run_interrupt_driven_config_hooks: waited too long, Mark Atkinson
• Thread-caching added to jemalloc, Jason Evans
• CFT: BSD grep, Gabor Kovesdan
  • Re: CFT: BSD grep, Andrey Chernov
• error building kernel, Martin Smith
  • Re: error building kernel, John Baldwin
• Re: mprof and new systems.., Pietro Cerutti
• How to use lagg and wlan together, Daniel Eischen
  • Subject : wlan is borken with lagg [was Re: How to use lagg and wlan together], Daniel Eischen
  • Re: How to use lagg and wlan together, Andrew Thompson
    • Re: How to use lagg and wlan together, Sam Leffler
    • Re: How to use lagg and wlan together, Daniel Eischen
      • Re: How to use lagg and wlan together, Andrew Thompson
      • Re: How to use lagg and wlan together, Daniel Eischen
• Enormous utmp since mpsafetty, Philip Paeps
  • Re: Enormous utmp since mpsafetty, kevin
    • Re: Enormous utmp since mpsafetty, Philip Paeps
      • Re: Enormous utmp since mpsafetty, Gary Jennejohn
      • Re: Enormous utmp since mpsafetty, Ollivier Robert
      • Re: Enormous utmp since mpsafetty, Robert Watson
      • Re: Enormous utmp since mpsafetty, Gary Jennejohn
      • Re: Enormous utmp since mpsafetty, John Baldwin
      • Re: Enormous utmp since mpsafetty, Peter Wemm
• Inserting flow-control chars with an mpsafetty kernel, Giorgos Keramidas
  • Re: Inserting flow-control chars with an mpsafetty kernel, swell . k
    • Re: Inserting flow-control chars with an mpsafetty kernel, Giorgos Keramidas
      • Re: Inserting flow-control chars with an mpsafetty kernel, swell . k
      • Re: Inserting flow-control chars with an mpsafetty kernel, Giorgos Keramidas
      • Re: Inserting flow-control chars with an mpsafetty kernel, Christian Weisgerber
      • Re: Inserting flow-control chars with an mpsafetty kernel, Paul B. Mahol
  • Re: Inserting flow-control chars with an mpsafetty kernel, Ed Schouten
    • Re: Inserting flow-control chars with an mpsafetty kernel, Giorgos Keramidas
    • Re: Inserting flow-control chars with an mpsafetty kernel, Giorgos Keramidas
    • Re: Inserting flow-control chars with an mpsafetty kernel, Jilles Tjoelker
      • Re: Inserting flow-control chars with an mpsafetty kernel, Peter Jeremy
• Issue with rc.d/netif script when modifying NIC state after boot, Garrett Cooper
  • Re: Issue with rc.d/netif script when modifying NIC state after boot, Brooks Davis
  • Re: Issue with rc.d/netif script when modifying NIC state after boot, Daniel O'Connor
• How about AMD Puma platform support?, Norikatsu Shigemura
  • Re: How about AMD Puma platform support?, Rui Paulo
    • Re: How about AMD Puma platform support?, Norikatsu Shigemura
      • Re: How about AMD Puma platform support?, Rui Paulo
      • Re: How about AMD Puma platform support?, Norikatsu Shigemura
  • Re: How about AMD Puma platform support?, Norikatsu Shigemura
  • <Possible follow-ups>
  • Re: How about AMD Puma platform support?, Alexander Motin
    • Re: How about AMD Puma platform support?, Norikatsu Shigemura
    • Re: How about AMD Puma platform support?, Norikatsu Shigemura
      • Re: How about AMD Puma platform support?, Norikatsu Shigemura
      • Re: How about AMD Puma platform support?, Alexander Motin
• mouse interactivity (Re: svn commit: r182109 - head/sys/dev/syscons), Kris Kennaway
  • Re: mouse interactivity (Re: svn commit: r182109 - head/sys/dev/syscons), Kris Kennaway
  • Re: mouse interactivity (Re: svn commit: r182109 - head/sys/dev/syscons), Ed Schouten
    • Re: mouse interactivity (Re: svn commit: r182109 - head/sys/dev/syscons), Kris Kennaway
    • Re: mouse interactivity (Re: svn commit: r182109 - head/sys/dev/syscons), Marius Nünnerich
      • Re: mouse interactivity (Re: svn commit: r182109 - head/sys/dev/syscons), Kris Kennaway
• [CFT/R] IPv4 source address selection, Bjoern A. Zeeb
  • Re: [CFT/R] IPv4 source address selection, Bruce M. Simpson
• Weirdness with recently updated NTP on -current?, Richard Todd
  • Re: Weirdness with recently updated NTP on -current?, Philip Paeps
  • Re: Weirdness with recently updated NTP on -current?, Christian Weisgerber
  • Re: Weirdness with recently updated NTP on -current?, Christian Weisgerber
    • Re: Weirdness with recently updated NTP on -current?, Ollivier Robert
• Re: CFT/CFR: NDIS(4) USB support, Paul B. Mahol
  • Re: CFT/CFR: NDIS(4) USB support, Paul B. Mahol
    • Re: CFT/CFR: NDIS(4) USB support, Weongyo Jeong
  • Re: CFT/CFR: NDIS(4) USB support, Weongyo Jeong
• Unicode-based FreeBSD, Alexander Churanov
  • Re: Unicode-based FreeBSD, Ed Schouten
    • Re: Unicode-based FreeBSD, Thomas Dickey
      • Re: Unicode-based FreeBSD, Alexander Churanov
      • Re: Unicode-based FreeBSD, Erik Trulsson
      • Re: Unicode-based FreeBSD, Alexander Churanov
      • Re: Unicode-based FreeBSD, Garrett Cooper
      • Re: Unicode-based FreeBSD, Garrett Cooper
      • Re: Unicode-based FreeBSD, Alexander Churanov
      • Re: Unicode-based FreeBSD, Dmitry Morozovsky
      • Re: Unicode-based FreeBSD, Alexander Churanov
    • Re: Unicode-based FreeBSD, Alexander Churanov
  • Re: Unicode-based FreeBSD, Marcel Moolenaar
    • Re: Unicode-based FreeBSD, Alexander Churanov
    • Re: Unicode-based FreeBSD, Ivan Voras
      • Re: Unicode-based FreeBSD, Alexander Churanov
  • <Possible follow-ups>
  • Re: Unicode-based FreeBSD, Tz-Huan Huang
    • Re: Unicode-based FreeBSD, Alexander Churanov
      • Re: Unicode-based FreeBSD, Svavar Lúthersson
      • Re: Unicode-based FreeBSD, Alexander Churanov
      • Re: Unicode-based FreeBSD, Marcel Moolenaar
      • Re: Unicode-based FreeBSD, Alexander Churanov
      • Re: Unicode-based FreeBSD, Marcel Moolenaar
      • Re: Unicode-based FreeBSD, Alexander Churanov
      • Re: Unicode-based FreeBSD, Oliver Fromme
      • Re: Unicode-based FreeBSD, Alexander Churanov
      • Re: Unicode-based FreeBSD, Peter Wemm
      • Re: Unicode-based FreeBSD, Alexander Churanov
      • Re: Unicode-based FreeBSD, Konrad Jankowski
      • Re: Unicode-based FreeBSD, Alexander Churanov
      • Re: Unicode-based FreeBSD, Alexander Churanov
      • Re: Unicode-based FreeBSD, Marcus von Appen
      • Re: Unicode-based FreeBSD, Peter Jeremy
      • Re: Unicode-based FreeBSD, Alexander Churanov
      • Re: Unicode-based FreeBSD, Alexander Churanov
      • Re: Unicode-based FreeBSD, Tz-Huan Huang
      • Re: Unicode-based FreeBSD, Scott Robbins
      • Re: Unicode-based FreeBSD, Alexander Churanov
      • Re: Unicode-based FreeBSD, Svavar Lúthersson
      • Re: Unicode-based FreeBSD, Alexander Churanov
      • Re: Unicode-based FreeBSD, Svavar Lúthersson
      • Re: Unicode-based FreeBSD, Tz-Huan Huang
      • Re: Unicode-based FreeBSD, Tim Kientzle
      • Re: Unicode-based FreeBSD, Svavar Lúthersson
      • Re: Unicode-based FreeBSD, Mark Linimon
      • Re: Unicode-based FreeBSD, Tz-Huan Huang
• No root filesystem, Christian Weisgerber
  • Re: No root filesystem, Randy Bush
    • Re: No root filesystem, Garrett Cooper
      • Re: No root filesystem, Garrett Cooper
  • Re: No root filesystem, Christian Weisgerber
    • Re: No root filesystem, John Baldwin
      • Re: No root filesystem, Pascal Hofstee
      • Re: No root filesystem, Pascal Hofstee
      • Re: No root filesystem, John Baldwin
      • Re: No root filesystem, Pascal Hofstee
      • Re: No root filesystem, Christian Weisgerber
      • Re: No root filesystem, Rui Paulo
      • Re: No root filesystem, Christian Weisgerber
      • Re: No root filesystem, Pascal Hofstee
• [XEN] xs_single device/vbd xs_talkv read_reply panic: bad stray interrupt, Brad Pitney
  • Re: [XEN] xs_single device/vbd xs_talkv read_reply panic: bad stray interrupt, Kip Macy
    • Re: [XEN] xs_single device/vbd xs_talkv read_reply panic: bad stray interrupt, Brad Pitney
      • Re: [XEN] xs_single device/vbd xs_talkv read_reply panic: bad stray interrupt, Kip Macy
      • Re: [XEN] xs_single device/vbd xs_talkv read_reply panic: bad stray interrupt, Brad Pitney
      • Re: [XEN] xs_single device/vbd xs_talkv read_reply panic: bad stray interrupt, Kip Macy
      • Re: [XEN] xs_single device/vbd xs_talkv read_reply panic: bad stray interrupt, Brad Pitney
      • Re: [XEN] xs_single device/vbd xs_talkv read_reply panic: bad stray interrupt, Kip Macy
      • Re: [XEN] xs_single device/vbd xs_talkv read_reply panic: bad stray interrupt, Brad Pitney
      • Re: [XEN] xs_single device/vbd xs_talkv read_reply panic: bad stray interrupt, Brad Pitney
      • Re: [XEN] xs_single device/vbd xs_talkv read_reply panic: bad stray interrupt, Kip Macy
      • Re: [XEN] xs_single device/vbd xs_talkv read_reply panic: bad stray interrupt, Brad Pitney
• request for testers - xen support for domU in head, Kip Macy
  • Re: request for testers - xen support for domU in head, Brad Pitney
  • Re: request for testers - xen support for domU in head, Greg Larkin
    • Re: request for testers - xen support for domU in head, Kip Macy
• Detangling the ppbus/ppc interrupt stuff.., John Baldwin
• [BUG] I think sleepqueue need to be protected in sleepq_broadcast, kevinxlinuz
  • Re: [BUG] I think sleepqueue need to be protected in sleepq_broadcast, John Baldwin
    • Re: [BUG] I think sleepqueue need to be protected in sleepq_broadcast, Attilio Rao
      • Re: [BUG] I think sleepqueue need to be protected in sleepq_broadcast, Benjamin Close
  • Re: [BUG] I think sleepqueue need to be protected in sleepq_broadcast, kevin
    • Re: [BUG] I think sleepqueue need to be protected in sleepq_broadcast, Dmitry Morozovsky
      • Re: [BUG] I think sleepqueue need to be protected in sleepq_broadcast, kevin
      • Re: [BUG] I think sleepqueue need to be protected in sleepq_broadcast, Dmitry Morozovsky
      • Re:Re: [BUG] I think sleepqueue need to be protected in sleepq_broadcast, kevin
• sun4v arch, Nikolay Kalev
  • Re: sun4v arch, Kris Kennaway
    • Re: sun4v arch, Pietro Cerutti
      • Re: sun4v arch, M. Warner Losh
    • Re: sun4v arch, Peter Jeremy
      • Re: sun4v arch, Maxim Sobolev
      • Re: sun4v arch, Garrett Cooper
      • Re: sun4v arch, Mark Linimon
      • Re: sun4v arch, Peter Jeremy
      • Re: sun4v arch, Kip Macy
      • Re: sun4v arch, Peter Jeremy
      • Message not available
      • Re: sun4v arch, Kip Macy
      • Re: sun4v arch, Maxim Sobolev
  • <Possible follow-ups>
  • Re: sun4v arch, Brad
• Upcoming Releases Schedule..., Ken Smith
  • Re: Upcoming Releases Schedule..., Svein Skogen
    • Re: Upcoming Releases Schedule..., Eugene Grosbein
      • Re: Upcoming Releases Schedule..., Bruce A. Mah
• panic: not waking up swapper, Robert Watson
• ypbind looping, Cy Schubert
• the future of sun4v, Kip Macy
  • Re: the future of sun4v, Peter Jeremy
    • Re: the future of sun4v, Kris Kennaway
      • Re: the future of sun4v, Marius Strobl
      • Re: the future of sun4v, Kip Macy
    • Re: the future of sun4v, Marcel Moolenaar
• gnome2/x11 slow after optimization!, Rohit Tripathi
  • Re: gnome2/x11 slow after optimization!, Kris Kennaway
    • Re: gnome2/x11 slow after optimization!, Steve Kargl
      • Re: gnome2/x11 slow after optimization!, Joseph S. Atkinson
  • Re: gnome2/x11 slow after optimization!, Alexander Leidinger
  • Re: gnome2/x11 slow after optimization!, Andrew Reilly
    • Re: gnome2/x11 slow after optimization!, Rohit Tripathi
  • Re: gnome2/x11 slow after optimization!, Kevin Foo
    • Re: gnome2/x11 slow after optimization!, Rohit Tripathi
• uplcom broken by MPSAFE TTY commit?, Christian Weisgerber
  • Re: uplcom broken by MPSAFE TTY commit?, Ed Schouten
  • Re: uplcom broken by MPSAFE TTY commit?, Christian Weisgerber
• 8.0-CURRENT built on 08/20 crashing with HTT enabled, Renato Botelho
  • Re: 8.0-CURRENT built on 08/20 crashing with HTT enabled, Ed Schouten
    • Re: 8.0-CURRENT built on 08/20 crashing with HTT enabled, Rink Springer
    • Re: 8.0-CURRENT built on 08/20 crashing with HTT enabled, Kostik Belousov
      • Re: 8.0-CURRENT built on 08/20 crashing with HTT enabled, Rink Springer
      • Message not available
      • Re: 8.0-CURRENT built on 08/20 crashing with HTT enabled, Renato Botelho
      • 8.0-CURRENT kernel panic on system boot, kevin
      • Re: 8.0-CURRENT kernel panic on system boot, Kostik Belousov
      • Re: 8.0-CURRENT kernel panic on system boot, Ed Schouten
      • Re: 8.0-CURRENT kernel panic on system boot, kevin
      • Re: 8.0-CURRENT kernel panic on system boot, Kostik Belousov
      • Re: 8.0-CURRENT kernel panic on system boot, kevin
      • Re: 8.0-CURRENT kernel panic on system boot, Ed Schouten
      • Re: 8.0-CURRENT kernel panic on system boot, Ed Schouten
• The FreeBSD Status Reports for the Second Quarter of 2008, Brad Davis
• HEADSUP new usb code coming in., Alfred Perlstein
  • Re: HEADSUP new usb code coming in., Kevin Oberman
    • Re: HEADSUP new usb code coming in., Stefan Lambrev
    • Re: HEADSUP new usb code coming in., Alfred Perlstein
    • Re: HEADSUP new usb code coming in., Hans Petter Selasky
      • Re: HEADSUP new usb code coming in., Bakul Shah
      • Re: HEADSUP new usb code coming in., Warner Losh
      • Re: HEADSUP new usb code coming in., Antony Mawer
      • Re: HEADSUP new usb code coming in., M. Warner Losh
      • Re: HEADSUP new usb code coming in., Antony Mawer
      • Re: Re: HEADSUP new usb code coming in., Volker
      • Re: HEADSUP new usb code coming in., Antony Mawer
      • Re: HEADSUP new usb code coming in., M. Warner Losh
      • Re: HEADSUP new usb code coming in., Antony Mawer
      • Re: HEADSUP new usb code coming in., M. Warner Losh
      • Re: "legacy" usb stack fixes (was: Re: HEADSUP new usb code coming in.), Volker
      • Re: HEADSUP new usb code coming in., Fabian Keil
      • Re: usb/46176: Let's save the horse! [was: HEADSUP new usb code coming in.], Alexey Shuvaev
      • Re: usb/46176: Let's save the horse! [was: HEADSUP new usb code coming in.], Kevin Oberman
      • Re: usb/46176: Let's save the horse! [was: HEADSUP new usb code coming in.], Fabian Keil
      • Re: HEADSUP new usb code coming in., Kevin Oberman
      • Re: HEADSUP new usb code coming in., Janusz Dziedzic
  • Re: HEADSUP new usb code coming in., Wilko Bulte
    • Re: HEADSUP new usb code coming in., Alfred Perlstein
  • Re: HEADSUP new usb code coming in., Maxim Sobolev
    • Re: HEADSUP new usb code coming in., Hans Petter Selasky
      • Re: HEADSUP new usb code coming in., Jeremy Messenger
      • Re: HEADSUP new usb code coming in., Alfred Perlstein
    • Re: HEADSUP new usb code coming in., Maxim Sobolev
      • Re: HEADSUP new usb code coming in., Robert Watson
      • Re: HEADSUP new usb code coming in., Maxim Sobolev
      • Re: HEADSUP new usb code coming in., Warner Losh
  • Re: HEADSUP new usb code coming in., Stefan Lambrev
    • Re: HEADSUP new usb code coming in., Alfred Perlstein
      • Re: HEADSUP new usb code coming in., Aragon Gouveia
  • Re: HEADSUP new usb code coming in., David Naylor
    • Re: HEADSUP new usb code coming in., Hans Petter Selasky
      • Re: HEADSUP new usb code coming in., Kostik Belousov
      • Re: HEADSUP new usb code coming in., Hans Petter Selasky
      • Re: HEADSUP new usb code coming in., Alfred Perlstein
  • <Possible follow-ups>
  • Re: HEADSUP new usb code coming in., Pedro Giffuni
• regex regression?, Yuri Pankov
  • Re: regex regression?, Stanislav Sedov
    • Re: regex regression?, Yuri Pankov
  • <Possible follow-ups>
  • Re: regex regression?, Derek Tattersall
    • Re: regex regression?, Andrey Chernov
• zpool import hanging on unexpectedly-rebooted machine, Colin Moller
  • Re: zpool import hanging on unexpectedly-rebooted machine, Pawel Jakub Dawidek
    • Re: zpool import hanging on unexpectedly-rebooted machine, Colin Moller
• several lock order reversals in VFS suddenly., Alfred Perlstein
  • Re: several lock order reversals in VFS suddenly., Kris Kennaway
    • Re: several lock order reversals in VFS suddenly., Alfred Perlstein
  • Re: several lock order reversals in VFS suddenly., John Baldwin
• HEADS UP: MPSAFE TTY integration on August 20, Ed Schouten
  • HEADS DOWN: MPSAFE TTY layer integrated, Ed Schouten
    • Re: HEADS DOWN: MPSAFE TTY layer integrated, Giorgos Keramidas
    • Re: HEADS DOWN: MPSAFE TTY layer integrated, Tor Egge
      • Re: HEADS DOWN: MPSAFE TTY layer integrated, Ed Schouten
• Possible regression with 200807 amd64 snapshot CD, Garrett Cooper
  • Re: Possible regression with 200807 amd64 snapshot CD, Tim Kientzle
  • Re: Possible regression with 200807 amd64 snapshot CD, Dimitry Andric
    • Re: Possible regression with 200807 amd64 snapshot CD, Tim Kientzle
      • Re: Possible regression with 200807 amd64 snapshot CD, Tim Kientzle
      • Re: Possible regression with 200807 amd64 snapshot CD, Dimitry Andric
  • Re: Possible regression with 200807 amd64 snapshot CD, Tim Kientzle
    • Re: Possible regression with 200807 amd64 snapshot CD, Jose Amengual M
      • Re: Possible regression with 200807 amd64 snapshot CD, Garrett Cooper
      • Re: Possible regression with 200807 amd64 snapshot CD, Dimitry Andric
      • Re: Possible regression with 200807 amd64 snapshot CD, Garrett Cooper
      • Re: Possible regression with 200807 amd64 snapshot CD, Carlos A. M. dos Santos
      • Re: Possible regression with 200807 amd64 snapshot CD, Ken Smith
• lock_initalized, Matt Benjamin
  • Re: lock_initalized, John Baldwin
• Superpages?, Ivan Voras
  • Re: Superpages?, Alan Cox
    • Re: Superpages?, Christian Weisgerber
      • Re: Superpages?, Kris Kennaway
• uninitialized "width" in st_parse.c ?, Rohit Tripathi
  • Re: uninitialized "width" in st_parse.c ?, Rohit Tripathi
• V_HEADS UP (at short notice) kinda headsup.. (fwd), Bjoern A. Zeeb
  • V_HEADS UP II., Bjoern A. Zeeb
    • Re: V_HEADS UP II., Bjoern A. Zeeb
• kernel memory, vehemens
  • Re: kernel memory, Scott Long
• Limiting icmp unreach response fron 348 to 200 packets/sec, Erol Akarsu
  • Re: Limiting icmp unreach response fron 348 to 200 packets/sec, Mike Tancsa
  • Re: Limiting icmp unreach response fron 348 to 200 packets/sec, Julian Elischer
  • Re: Limiting icmp unreach response fron 348 to 200 packets/sec, M. Warner Losh
• Max Kernel Memory?, Barney Cordoba
  • Re: Max Kernel Memory?, David Schultz
• Freeswitch on latest FBSD, Erol Akarsu
  • Re: Freeswitch on latest FBSD, Rui Paulo
  • <Possible follow-ups>
  • Re: Freeswitch on latest FBSD, Erol Akarsu
    • Re: Freeswitch on latest FBSD, David N
    • Re: Freeswitch on latest FBSD, cpghost
  • Re: Freeswitch on latest FBSD, Erol Akarsu
    • Re: Freeswitch on latest FBSD, cpghost
    • Re: Freeswitch on latest FBSD, Christoph Moench-Tegeder
• Re: desktop wireless card, James Harrison
• __tls_get_addr problem with recent current, Bernd Walter
  • Re: __tls_get_addr problem with recent current, Bernd Walter
  • Re: __tls_get_addr problem with recent current, Kostik Belousov
    • Re: __tls_get_addr problem with recent current, Bernd Walter
      • Re: __tls_get_addr problem with recent current, Kostik Belousov
      • Re: __tls_get_addr problem with recent current, Bernd Walter
  • <Possible follow-ups>
  • Re: __tls_get_addr problem with recent current, Bernd Walter
  • Re: __tls_get_addr problem with recent current, Kostik Belousov
    • Re: __tls_get_addr problem with recent current, Artem Belevich
      • Re: __tls_get_addr problem with recent current, Kostik Belousov
      • Re: __tls_get_addr problem with recent current, Artem Belevich
      • Re: __tls_get_addr problem with recent current, Kostik Belousov
      • Re: __tls_get_addr problem with recent current, Kostik Belousov
• Advanced warning: virtualization work will be afoot, Robert Watson
  • Re: Advanced warning: virtualization work will be afoot, Darren Reed
    • Re: Advanced warning: virtualization work will be afoot, Dag-Erling Smørgrav
      • Re: Advanced warning: virtualization work will be afoot, Sam Fourman Jr.
      • Re: Advanced warning: virtualization work will be afoot, Dag-Erling Smørgrav
    • Re: Advanced warning: virtualization work will be afoot, Alexander Leidinger
    • Re: Advanced warning: virtualization work will be afoot, Julian Elischer
      • Re: Advanced warning: virtualization work will be afoot, Darren Reed
      • Re: Advanced warning: virtualization work will be afoot, Dag-Erling Smørgrav
• LOR's on boot, Michael Jung
• [iwn driver] SIOCS80211 error on 4965AGN, Rohit Tripathi
  • Re: [iwn driver] SIOCS80211 error on 4965AGN, rohit . x . tripathi
    • Re: [iwn driver] SIOCS80211 error on 4965AGN, jt
      • Re: [iwn driver] SIOCS80211 error on 4965AGN, Rohit Tripathi
      • Re: [iwn driver] SIOCS80211 error on 4965AGN, Rohit Tripathi
      • Re: [iwn driver] SIOCS80211 error on 4965AGN, Sam Leffler
      • Re: [iwn driver] SIOCS80211 error on 4965AGN, Andrew Thompson
      • Re: [iwn driver] SIOCS80211 error on 4965AGN, Rohit Tripathi
      • Re: [iwn driver] SIOCS80211 error on 4965AGN, Sam Leffler
      • Re: [iwn driver] SIOCS80211 error on 4965AGN, Rohit Tripathi
• POSIX compliant termios.h?, Alexey Shuvaev
  • Re: POSIX compliant termios.h?, Ed Schouten
    • Re: POSIX compliant termios.h?, Ed Schouten
  • Re: POSIX compliant termios.h?, Ed Schouten
    • Re: POSIX compliant termios.h?, Alexey Shuvaev
• cannot delete libc.so.7 from build directories, Rohit Tripathi
  • Re: cannot delete libc.so.7 from build directories, Brooks Davis
  • Re: cannot delete libc.so.7 from build directories, Steve Kargl
• FreeBSD/AVR32 port, Arnar Mar Sig
  • Re: FreeBSD/AVR32 port, M. Warner Losh
    • Re: FreeBSD/AVR32 port, Julian Elischer
      • Re: FreeBSD/AVR32 port, Arnar Mar Sig
      • Re: FreeBSD/AVR32 port, M. Warner Losh
    • Re: FreeBSD/AVR32 port, Arnar Mar Sig
      • Re: FreeBSD/AVR32 port, Arnar Mar Sig
  • Re: FreeBSD/AVR32 port, Wojciech A. Koszek
    • Re: FreeBSD/AVR32 port, Arnar Mar Sig
      • Re: FreeBSD/AVR32 port, Ulf Lilleengen
• Re: kern/113398: [libc] initgroups fails rather than truncates if number of groups &gt; NGROUPS_MAX meaning the user can no longer login, ttw+bsd
• Committing glxsb - any objections?, Philip Paeps
  • Re: Committing glxsb - any objections?, John Baldwin
    • Re: Committing glxsb - any objections?, Philip Paeps
  • Re: Committing glxsb - any objections?, Patrick Lamaizière
    • Re: Committing glxsb - any objections?, Pawel Jakub Dawidek
      • Re: Committing glxsb - any objections?, Philip Paeps
      • Re: Committing glxsb - any objections?, Patrick Lamaizière
      • Re: Committing glxsb - any objections?, Pawel Jakub Dawidek
• MPSAFE TTY schedule delay: 10 days, Ed Schouten
• ucom0 - instant detached, Daniel Bielefeldt
  • Re: ucom0 - instant detached, Hans Petter Selasky
• [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/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
    • Re: [head tinderbox] failure on i386/pc98, M. Warner Losh
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on i386/pc98, Randall Stewart
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on i386/pc98, Attilio Rao
  • [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
  • [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
  • [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
  • [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, Ollivier Robert
      • Re: [head tinderbox] failure on i386/i386, Pieter de Goeje
      • Re: [head tinderbox] failure on i386/i386, Andrew Milton
      • Re: [head tinderbox] failure on i386/i386, Dag-Erling Smørgrav
  • [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
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
• [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
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on amd64/amd64, Dag-Erling Smørgrav
      • Re: [head tinderbox] failure on amd64/amd64, Ruslan Ermilov
      • Re: [head tinderbox] failure on amd64/amd64, Dag-Erling Smørgrav
      • Re: [head tinderbox] failure on amd64/amd64, Ruslan Ermilov
      • Re: [head tinderbox] failure on amd64/amd64, Dag-Erling Smørgrav
      • Re: [head tinderbox] failure on amd64/amd64, Ruslan Ermilov
  • [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 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 amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
• [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 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
• Re: AMD Geode LX crypto accelerator (glxsb), Mike Tancsa
  • Re: AMD Geode LX crypto accelerator (glxsb) (and padlock.ko), Mike Tancsa
    • Re: AMD Geode LX crypto accelerator (glxsb) (and padlock.ko), Patrick Lamaizière
      • Re: AMD Geode LX crypto accelerator (glxsb) (and padlock.ko), Mike Tancsa
      • Re: AMD Geode LX crypto accelerator (glxsb) (and padlock.ko), VANHULLEBUS Yvan
      • Re: AMD Geode LX crypto accelerator (glxsb) (and padlock.ko), John Baldwin
• [O/T] svn co fails for usr.bin/window, Rohit Tripathi
  • Re: [O/T] svn co fails for usr.bin/window, Max Laier
  • Re: [O/T] svn co fails for usr.bin/window, Ed Schouten
    • Re: [O/T] svn co fails for usr.bin/window, Ed Schouten
      • Re: [O/T] svn co fails for usr.bin/window, rohit . x . tripathi
      • Re: [O/T] svn co fails for usr.bin/window, Marcel Moolenaar
      • Re: [O/T] svn co fails for usr.bin/window, Ed Maste
      • Re: [O/T] svn co fails for usr.bin/window, Dag-Erling Smørgrav
      • Re: [O/T] svn co fails for usr.bin/window, Marcin Wisnicki
      • Re: [O/T] svn co fails for usr.bin/window, Rohit Tripathi
• [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
  • [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, Kostik Belousov
  • [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
• bce(4) network wierdness, Ian FREISLICH
  • RE: bce(4) network wierdness, David Christensen
  • <Possible follow-ups>
  • RE: bce(4) network wierdness, Ian Freislich
• ACPI problem: Machine Cannot poweroff., 裴国兴
  • Message not available
    • Re: ACPI problem: Machine Cannot poweroff., 裴国兴
• Re: cpuctl(formely devcpu) patch test request, Stanislav Sedov
  • Re: cpuctl(formely devcpu) patch test request, Kostik Belousov
    • Re: cpuctl(formely devcpu) patch test request, Stanislav Sedov
      • Re: cpuctl(formely devcpu) patch test request, Kostik Belousov
      • Re: cpuctl(formely devcpu) patch test request, Stanislav Sedov
• [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
  • [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
  • [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/sparc64, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [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
  • [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
  • [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
• ral, rum and bi-antenna, David Naylor
  • Re: ral, rum and bi-antenna, Sam Leffler
    • Re: ral, rum and bi-antenna, David Naylor
      • Re: ral, rum and bi-antenna, Sam Leffler
      • Re: ral, rum and bi-antenna, Carlos A. M. dos Santos
• IPFilter build failure, Beech Rintoul
  • Re: IPFilter build failure, Max Laier
    • Re: IPFilter build failure, Beech Rintoul
      • Re: IPFilter build failure, Max Laier
      • Re: IPFilter build failure, Beech Rintoul
      • Re: IPFilter build failure, Max Laier
      • Re: IPFilter build failure, Beech Rintoul
      • Re: IPFilter build failure, Beech Rintoul
    • Re: IPFilter build failure, Darren Reed
• buildworld fails in libcom_err/doc, Raoul
• twa probe failure on Gigabyte RH-115, Dmitry Morozovsky
  • Re: twa probe failure on Gigabyte RH-115, Scott Long
• termcap under single luser, Randy Bush
  • Re: termcap under single luser, Dimitry Andric
    • Re: termcap under single luser, Randy Bush
      • Re: termcap under single luser, Dag-Erling Smørgrav
      • Re: termcap under single luser, Randy Bush
      • Re: termcap under single luser, Dimitry Andric
      • Re: termcap under single luser, Randy Bush
      • Re: termcap under single luser, Giorgos Keramidas
      • Re: termcap under single luser, Oliver Fromme
      • Re: termcap under single luser, Dimitry Andric
      • Re: termcap under single luser, Tod McQuillin
      • Re: termcap under single luser, Matthew D. Fuller
      • Re: termcap under single luser, Randy Bush
      • Re: termcap under single luser, Matthew D. Fuller
      • Re: termcap under single luser, Dimitry Andric
      • Re: termcap under single luser, Dag-Erling Smørgrav
      • Re: termcap under single luser, Thomas Dickey
  • Re: termcap under single luser, Carlos A. M. dos Santos
    • Re: termcap under single luser, Bernd Walter
      • Re: termcap under single luser, Antony Mawer
  • Re: termcap under single luser, M. Warner Losh
  • <Possible follow-ups>
  • Re: termcap under single luser, Alex Kozlov
    • Re: termcap under single luser, Giorgos Keramidas
      • Re: termcap under single luser, Maxim Sobolev
      • Re: termcap under single luser, Giorgos Keramidas
  • Re: termcap under single luser, Alex Kozlov
  • Re: termcap under single luser, Alex Kozlov
• Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (fwd)), Robert Watson
• Re: Call for bfe(4) testers., Ulrich Spoerlein
  • Re: Call for bfe(4) testers., Pyun YongHyeon
    • Re: Call for bfe(4) testers., Ulrich Spoerlein
      • Re: Call for bfe(4) testers., Pyun YongHyeon
      • Re: Call for bfe(4) testers., Ulrich Spoerlein
      • Re: Call for bfe(4) testers., John Baldwin
• [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [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 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 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
• [Call for testers] New cvsmode for csup patch, Ulf Lilleengen
• wpi not working on 11b, Tobias Kirschstein
• /dev/sg* for AMD64, Larry Rosenman
  • <Possible follow-ups>
  • FW: /dev/sg* for AMD64, Larry Rosenman
    • Re: FW: /dev/sg* for AMD64, Roman Divacky
      • RE: FW: /dev/sg* for AMD64, Larry Rosenman
      • RE: FW: /dev/sg* for AMD64, Larry Rosenman
• Re: Upcoming ABI Breakage in RELENG_7, Alfred Perlstein
  • Re: Upcoming ABI Breakage in RELENG_7, Kostik Belousov
• Re: Recent Padlock changes break ssh, Patrick Lamaizière
• Reminder: non-mpsafetty drivers to be connected on Sunday, Ed Schouten
  • Re: Reminder: non-mpsafetty drivers to be connected on Sunday, Ed Schouten
    • Re: Reminder: non-mpsafetty drivers to be connected on Sunday, Peter Jeremy
      • Re: Reminder: non-mpsafetty drivers to be connected on Sunday, Poul-Henning Kamp
      • Re: Reminder: non-mpsafetty drivers to be connected on Sunday, John Baldwin
      • Re: Reminder: non-mpsafetty drivers to be connected on Sunday, Poul-Henning Kamp
      • Re: Reminder: non-mpsafetty drivers to be connected on Sunday, Peter Jeremy
      • Re: Reminder: non-mpsafetty drivers to be *dis*connected on Sunday, Ed Schouten
      • Re: Reminder: non-mpsafetty drivers to be *dis*connected on Sunday, Peter Wemm
      • Re: Reminder: non-mpsafetty drivers to be *dis*connected on Sunday, M. Warner Losh
      • Re: Reminder: non-mpsafetty drivers to be *dis*connected on Sunday, Robert Watson
      • Re: Reminder: non-mpsafetty drivers to be *dis*connected on Sunday, M. Warner Losh
      • Re: Reminder: non-mpsafetty drivers to be *dis*connected on Sunday, Sam Leffler
      • Re: Reminder: non-mpsafetty drivers to be connected on Sunday, Poul-Henning Kamp
      • Re: Reminder: non-mpsafetty drivers to be connected on Sunday, M. Warner Losh
  • Re: Reminder: non-mpsafetty drivers to be connected on Sunday, John Baldwin
  • Re: Reminder: non-mpsafetty drivers to be connected on Sunday, M. Warner Losh
    • Re: Reminder: non-mpsafetty drivers to be connected on Sunday, Ed Schouten
      • Re: Reminder: non-mpsafetty drivers to be connected on Sunday, M. Warner Losh
      • Re: Reminder: non-mpsafetty drivers to be connected on Sunday, Robert Watson
      • Re: Reminder: non-mpsafetty drivers to be connected on Sunday, Ed Schouten
      • Re: Reminder: non-mpsafetty drivers to be connected on Sunday, Robert Watson
• [BSD6] SSH Restriction, karim.bourenane
  • Re: [BSD6] SSH Restriction, Ed Schouten
    • RE: [BSD6] SSH Restriction, karim.bourenane
      • Re: [BSD6] SSH Restriction, Ed Schouten
      • RE: [BSD6] SSH Restriction, karim.bourenane
    • Re: [BSD6] SSH Restriction, Kostik Belousov
      • RE: [BSD6] SSH Restriction, karim.bourenane
      • Re: [BSD6] SSH Restriction, Jacob Frelinger
• Re: SSP on PPC, Peter Grehan
  • Re: SSP on PPC, Justin Hibbits
  • <Possible follow-ups>
  • Re: SSP on PPC, Jeremie Le Hen
• Re: ZFS patches., Benjamin Close
  • <Possible follow-ups>
  • Re: ZFS patches., Claus Guttesen
    • Re: ZFS patches., Claus Guttesen
      • Re: ZFS patches., Claus Guttesen
  • Re: ZFS patches., George Hartzell
  • Re: ZFS patches., Randy Bush
    • Re: ZFS patches., Randy Bush
    • Message not available
      • Re: ZFS patches., Richard Todd
      • Re: ZFS patches., Randy Bush
  • Re: ZFS patches., Norikatsu Shigemura
    • Re: ZFS patches., John Baldwin
      • Re: ZFS patches., Norikatsu Shigemura
  • Re: ZFS patches., Shaun Courtney
    • Re: ZFS patches., Gary Jennejohn
    • Re: ZFS patches., Pawel Jakub Dawidek
  • Re: ZFS patches., John Nielsen
  • Re: ZFS patches., Larry Rosenman
    • Re: ZFS patches., Larry Rosenman
  • Re: ZFS patches., Pascal Hofstee
    • Re: ZFS patches., Weldon S Godfrey 3
      • RE: ZFS patches., Larry Rosenman
      • RE: ZFS patches., Weldon S Godfrey 3
  • Re: ZFS patches., Stefan Lambrev
• Re: Snapshot 8.0-CURRENT-200807-amd64, Bruce Cran
  • <Possible follow-ups>
  • Re: Snapshot 8.0-CURRENT-200807-amd64, Ian FREISLICH

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