freebsd-current

• Date Index

---

• Possible alternate definition of CTASSERT to allow its use in header files, Ryan Stone
• Server setup, Curtis Vaughan
  • Re: Server setup, Ashish Shukla आशीष शुक्ल
• Another ppbus/ppc cleanup patch..., John Baldwin
• LORs during boot with -current (20080930), Harry Starr
  • Re: LORs during boot with -current (20080930), John Baldwin
• LORs during running, Harry Starr
• KDB stack backtrace - i386 on boot, Anton Shterenlikht
  • Re: KDB stack backtrace - i386 on boot, John Baldwin
• I lost ath0 support on current sometime between Sept 20 and Sept 26., eculp
  • Re: I lost ath0 support on current sometime between Sept 20 and Sept 26., आशीष शुक्ल Ashish Shukla
    • Re: I lost ath0 support on current sometime between Sept 20 and Sept 26., Sam Leffler
      • Re: I lost ath0 support on current sometime between Sept 20 and Sept 26., Ashish Shukla आशीष शुक्ल
      • Re: I lost ath0 support on current sometime between Sept 20 and Sept 26., eculp
• Please test ipfw and pf uid/gid/jail rules, Robert Watson
  • Re: Please test ipfw and pf uid/gid/jail rules, Josh Carroll
• Panic: ucom, Ian Freislich
• drmOpen failed - agp - 82845M chipset - i386, Anton Shterenlikht
  • Re: drmOpen failed - agp - 82845M chipset - i386, Eygene Ryabinkin
  • Re: drmOpen failed - agp - 82845M chipset - i386, Oliver Fromme
    • Re: drmOpen failed - agp - 82845M chipset - i386, Anton Shterenlikht
      • Re: drmOpen failed - agp - 82845M chipset - i386, Eygene Ryabinkin
      • Re: drmOpen failed - agp - 82845M chipset - i386, Oliver Fromme
      • SOLVED: Re: drmOpen failed - agp - 82845M chipset - i386, Anton Shterenlikht
  • Re: drmOpen failed - agp - 82845M chipset - i386, Robert Noland
    • Re: drmOpen failed - agp - 82845M chipset - i386, Anton Shterenlikht
      • Re: drmOpen failed - agp - 82845M chipset - i386, Robert Noland
      • Re: drmOpen failed - agp - 82845M chipset - i386, Anton Shterenlikht
• Possible netgraph snafu in build, Bruce M Simpson
• Hard crash with new snd_hda., Frank Mayhar
  • <Possible follow-ups>
  • Re: Hard crash with new snd_hda., Alexander Motin
• Request for testing - top 3.8b1 in the base system, Edwin Groothuis
  • Re: Request for testing - top 3.8b1 in the base system, Alex Keda
    • Re: Request for testing - top 3.8b1 in the base system, Garrett Cooper
      • Re: Request for testing - top 3.8b1 in the base system, Edwin Groothuis
      • Re: Request for testing - top 3.8b1 in the base system, William LeFebvre
      • Re: Request for testing - top 3.8b1 in the base system, Garrett Cooper
    • Re: Request for testing - top 3.8b1 in the base system, William LeFebvre
  • Message not available
    • Re: Request for testing - top 3.8b1 in the base system, Edwin Groothuis
      • Re: Request for testing - top 3.8b1 in the base system, Sergey Matveychuk
  • Re: Request for testing - top 3.8b1 in the base system, sthaug
    • Re: Request for testing - top 3.8b1 in the base system, Edwin Groothuis
    • Re: Request for testing - top 3.8b1 in the base system, William LeFebvre
  • Re: Request for testing - top 3.8b1 in the base system, Václav Haisman
    • Re: Request for testing - top 3.8b1 in the base system, Edwin Groothuis
      • Re: Request for testing - top 3.8b1 in the base system, William LeFebvre
      • Re: Request for testing - top 3.8b1 in the base system, Jaakko Heinonen
  • Re: Request for testing - top 3.8b1 in the base system, Nikola Lečić
    • Re: Request for testing - top 3.8b1 in the base system, Jeremy Chadwick
      • Re: Request for testing - top 3.8b1 in the base system, William LeFebvre
      • Re: Request for testing - top 3.8b1 in the base system, Jeremy Chadwick
  • Re: Request for testing - top 3.8b1 in the base system, Giorgos Keramidas
  • Re: Request for testing - top 3.8b1 in the base system, William LeFebvre
  • Re: Request for testing - top 3.8b1 in the base system, Bruce Cran
    • Re: Request for testing - top 3.8b1 in the base system, Edwin Groothuis
  • Re: Request for testing - top 3.8b1 in the base system, Alfred Perlstein
    • Re: Request for testing - top 3.8b1 in the base system, Edwin Groothuis
  • Re: Request for testing - top 3.8b1 in the base system, Thomas Hurst
    • Re: Request for testing - top 3.8b1 in the base system, Edwin Groothuis
  • <Possible follow-ups>
  • Re: Request for testing - top 3.8b1 in the base system, Oliver Fromme
• RFC: PCI SD host controller driver & mmc/mmcsd modules improvements, Alexander Motin
  • Re: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements, Oleksandr Tymoshenko
    • Re: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements, Carlos A. M. dos Santos
      • Re: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements, Carlos A. M. dos Santos
      • Re: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements, Alexander Motin
  • Re: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements, Rui Paulo
  • Re: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements, M. Warner Losh
  • Re: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements, Alex Keda
• mergemaster broken, Maksim Yevmenkin
  • Re: mergemaster broken, Eygene Ryabinkin
    • Re: mergemaster broken, Eygene Ryabinkin
• FreeBSD and ISCSI, Strange Problem, Daniel Dias Gonçalves
  • Re: FreeBSD and ISCSI, Strange Problem, Boris Samorodov
• Re: ata(4): Call for ICH10 owners' test, Jia-Shiun Li
• Re: ATA subsystem lost drive after resume process, Jia-Shiun Li
  • Re: ATA subsystem lost drive after resume process, Jung-uk Kim
• buildkernel failure on i386, Anton Shterenlikht
  • Re: buildkernel failure on i386, pluknet
  • Re: buildkernel failure on i386, Dimitry Andric
    • Re: buildkernel failure on i386, Anton Shterenlikht
• LSI Logic MegaRAID SAS 8208ELP, Tom Evans
  • Re: LSI Logic MegaRAID SAS 8208ELP, Wes Morgan
  • Re: LSI Logic MegaRAID SAS 8208ELP, Martin Nilsson
    • Re: LSI Logic MegaRAID SAS 8208ELP, John Baldwin
• iwn: Errors during make iwn.ko, Flavio Junior
  • Re: iwn: Errors during make iwn.ko, Stephen Montgomery-Smith
    • Re: iwn: Errors during make iwn.ko, Flavio Junior
      • Re: iwn: Errors during make iwn.ko, Stephen Montgomery-Smith
      • Re: iwn: Errors during make iwn.ko, Flavio Junior
• Support AV Stream on FreeBSD, Alex Keda
  • Re: Support AV Stream on FreeBSD, Bruce M. Simpson
    • Re: Support AV Stream on FreeBSD, Alex Keda
      • Re: Support AV Stream on FreeBSD, Thomas Donnelly
      • Re: Support AV Stream on FreeBSD, Mark Linimon
      • Re: Support AV Stream on FreeBSD, Alex Keda
      • Re: Support AV Stream on FreeBSD, Roman Kurakin
  • <Possible follow-ups>
  • Re: Support AV Stream on FreeBSD, Mark Linimon
• gssapi: Undefined symbol "GSS_C_NT_HOSTBASED_SERVICE" and "gss_oid_equal", Boris Samorodov
  • Re: gssapi: Undefined symbol "GSS_C_NT_HOSTBASED_SERVICE" and "gss_oid_equal", Robert Noland
    • Re: gssapi: Undefined symbol "GSS_C_NT_HOSTBASED_SERVICE" and "gss_oid_equal", Boris Samorodov
• ipfw: LOR/panic with uid rules, Stefan Ehmann
  • Re: ipfw: LOR/panic with uid rules, Ben Kaduk
    • Re: ipfw: LOR/panic with uid rules, Stefan Ehmann
  • Re: ipfw: LOR/panic with uid rules, Robert Watson
    • Re: ipfw: LOR/panic with uid rules, Robert Watson
      • Re: ipfw: LOR/panic with uid rules, Stefan Ehmann
      • Re: ipfw: LOR/panic with uid rules, Robert Watson
      • Re: ipfw: LOR/panic with uid rules, Stefan Ehmann
      • Re: ipfw: LOR/panic with uid rules, Robert Watson
      • Re: ipfw: LOR/panic with uid rules, Stefan Ehmann
      • Re: ipfw: LOR/panic with uid rules, Robert Watson
      • Re: ipfw: LOR/panic with uid rules, Stefan Ehmann
      • Re: ipfw: LOR/panic with uid rules, Robert Watson
      • Re: ipfw: LOR/panic with uid rules, Stefan Ehmann
      • Re: ipfw: LOR/panic with uid rules, Robert Watson
      • Re: ipfw: LOR/panic with uid rules, Stefan Ehmann
• Cant build kernel, Johan Hendriks
  • Re: Cant build kernel, Eygene Ryabinkin
• Problem telneting to a new -current, Claude Buisson
  • Re: Problem telneting to a new -current, Ed Schouten
  • Re: Problem telneting to a new -current, Ed Schouten
    • Re: Problem telneting to a new -current, Claude Buisson
      • Re: Problem telneting to a new -current, Claude Buisson
• Regression: 19-9-08 CURRENT won't boot with Promise enabled (was: Re: SATA disks no longer showing up after updating CURRENT last night), Joao Barros
• cosum: Checkout verification PoC, Max Laier
• assertion failed in libc/stdlib/malloc.c, Jille Timmermans
  • Re: assertion failed in libc/stdlib/malloc.c, Max Laier
  • Re: assertion failed in libc/stdlib/malloc.c, Dimitry Andric
    • Re: assertion failed in libc/stdlib/malloc.c, Jille Timmermans
• fdisk bsdlabel compile broken on Current, Manfred Antar
  • Re: fdisk bsdlabel compile broken on Current, Ulf Lilleengen
    • Re: fdisk bsdlabel compile broken on Current, Manfred Antar
      • Re: fdisk bsdlabel compile broken on Current, Tor Egge
      • Re: fdisk bsdlabel compile broken on Current, Manfred Antar
• ZFS panic in zone_dataset_visible, Scott Burns
  • Re: ZFS panic in zone_dataset_visible, Scott Burns
• prvxxx: cxm_iic attach fails, Stefan Ehmann
  • Re: prvxxx: cxm_iic attach fails, John Baldwin
    • Re: prvxxx: cxm_iic attach fails, Stefan Ehmann
• Today build breaks nvidia driver, Diego Depaoli
  • Re: Today build breaks nvidia driver, Aryeh M. Friedman
  • Re: Today build breaks nvidia driver, Attilio Rao
  • Re: Today build breaks nvidia driver, Stefan Ehmann
    • Re: Today build breaks nvidia driver, Diego Depaoli
      • Re: Today build breaks nvidia driver, Bjoern A. Zeeb
• Re: Booting from gpt on i386/amd64? [PATCH], Alexey Shuvaev
  • Re: Booting from gpt on i386/amd64? [PATCH], Marcel Moolenaar
    • Re: Booting from gpt on i386/amd64? [PATCH], Xin LI
• Setting up atheros (168c:001c) wireless NIC in FreeBSD, Ashish Shukla आशीष शुक्ल
  • Re: Setting up atheros (168c:001c) wireless NIC in FreeBSD, Sam Leffler
    • Re: Setting up atheros (168c:001c) wireless NIC in FreeBSD, Ashish Shukla आशीष शुक्ल
      • Re: Setting up atheros (168c:001c) wireless NIC in FreeBSD, fluffles.net
      • Re: Setting up atheros (168c:001c) wireless NIC in FreeBSD, Ashish Shukla आशीष शुक्ल
      • Re: Setting up atheros (168c:001c) wireless NIC in FreeBSD, Ashish Shukla आशीष शुक्ल
  • Re: Setting up atheros (168c:001c) wireless NIC in FreeBSD, Ashish Shukla आशीष शुक्ल
    • Re: Setting up atheros (168c:001c) wireless NIC in FreeBSD, Paul B. Mahol
      • Re: Setting up atheros (168c:001c) wireless NIC in FreeBSD, Paul B. Mahol
      • Re: Setting up atheros (168c:001c) wireless NIC in FreeBSD, Ashish Shukla आशीष शुक्ल
• Compilation error occured during 'make buildkernel', Ashish Shukla आशीष शुक्ल
  • Re: Compilation error occured during 'make buildkernel', Gary Jennejohn
    • Re: Compilation error occured during 'make buildkernel', Ashish Shukla आशीष शुक्ल
• Re: kern/127446: [patch] fix race in sys/dev/kbdmux/kbdmux.c, Maksim Yevmenkin
  • Re: kern/127446: [patch] fix race in sys/dev/kbdmux/kbdmux.c, Eygene Ryabinkin
    • Re: kern/127446: [patch] fix race in sys/dev/kbdmux/kbdmux.c, Eygene Ryabinkin
      • Re: kern/127446: [patch] fix race in sys/dev/kbdmux/kbdmux.c, Eygene Ryabinkin
      • Re: kern/127446: [patch] fix race in sys/dev/kbdmux/kbdmux.c, Eygene Ryabinkin
• Help me! about MCP78(GF8200) chipset, Gen Otsuji
  • <Possible follow-ups>
  • Re: Help me! about MCP78(GF8200) chipset, Gen Otsuji
• amd opteron NUMA support, Julian Elischer
  • Re: amd opteron NUMA support, Richard Grint
  • <Possible follow-ups>
  • re: amd opteron NUMA support, Peter Grehan
    • Re[2]: amd opteron NUMA support, Lev Serebryakov
• Re: IPSEC/crypto is broken in FreeBSD/powerpc 7.0-RELEASE!, Maxim Sobolev
  • <Possible follow-ups>
  • Re: IPSEC/crypto is broken in FreeBSD/powerpc 7.0-RELEASE!, Maxim Sobolev
• Interface auto-cloning bug or feature?, Maxim Sobolev
  • Re: Interface auto-cloning bug or feature?, Alexey Shuvaev
    • Re: Interface auto-cloning bug or feature?, Maxim Sobolev
      • Re: Interface auto-cloning bug or feature?, Alexey Shuvaev
      • Re: Interface auto-cloning bug or feature?, Maxim Sobolev
      • Re: Interface auto-cloning bug or feature?, Maksim Yevmenkin
      • Re: Interface auto-cloning bug or feature?, Maksim Yevmenkin
      • Re: Interface auto-cloning bug or feature?, Alexey Shuvaev
      • Re: Interface auto-cloning bug or feature?, Maxim Sobolev
      • Re: Interface auto-cloning bug or feature?, Maksim Yevmenkin
      • Re: Interface auto-cloning bug or feature?, Kostik Belousov
      • Re: Interface auto-cloning bug or feature?, Maksim Yevmenkin
      • Re: Interface auto-cloning bug or feature?, Kostik Belousov
      • Re: Interface auto-cloning bug or feature?, Maksim Yevmenkin
      • Re: Interface auto-cloning bug or feature?, Kostik Belousov
      • Re: Interface auto-cloning bug or feature?, Kostik Belousov
      • Re: Interface auto-cloning bug or feature?, Maksim Yevmenkin
      • Re: Interface auto-cloning bug or feature?, Maksim Yevmenkin
  • Re: Interface auto-cloning bug or feature?, Ed Schouten
    • Re: Interface auto-cloning bug or feature?, Ed Schouten
    • Re: Interface auto-cloning bug or feature?, Maksim Yevmenkin
      • Re: Interface auto-cloning bug or feature?, Maxim Sobolev
      • Re: Interface auto-cloning bug or feature?, Maksim Yevmenkin
  • Re: Interface auto-cloning bug or feature?, Maksim Yevmenkin
  • <Possible follow-ups>
  • Interface auto-cloning bug or feature?, Maxim Sobolev
• Re: Fwd: Pending MFC Reminder [cvs commit: src/lib/libc/uuid Symbol.map], Maksim Yevmenkin
  • Re: Fwd: Pending MFC Reminder [cvs commit: src/lib/libc/uuid Symbol.map], Xin LI
  • Re: Fwd: Pending MFC Reminder [cvs commit: src/lib/libc/uuid Symbol.map], Daniel Eischen
  • Re: Fwd: Pending MFC Reminder [cvs commit: src/lib/libc/uuid Symbol.map], Daniel Eischen
    • Re: Fwd: Pending MFC Reminder [cvs commit: src/lib/libc/uuid Symbol.map], Maksim Yevmenkin
• FreeBSD deadlock (with fork?), David Naylor
  • Re: FreeBSD deadlock (with fork?), Ivan Voras
  • Re: FreeBSD deadlock (with fork?), Tom Evans
    • Re: FreeBSD deadlock (with fork?), David Naylor
      • Re: FreeBSD deadlock (with fork?), Daniel Eischen
      • Re: FreeBSD deadlock (with fork?), David Naylor
      • Re: FreeBSD deadlock (with fork?), Daniel Eischen
      • Re: FreeBSD deadlock (with fork?), Jille Timmermans
  • Re: FreeBSD deadlock (with fork?), Julian Elischer
    • Re: FreeBSD deadlock (with fork?), David Naylor
      • Re: FreeBSD deadlock (with fork?), Daniel Eischen
  • Re: FreeBSD deadlock (with fork?), John Baldwin
• Current using -Os -pipe -march=pentium3m, Daniel de Oliveira
  • Re: Current using -Os -pipe -march=pentium3m, Daniel de Oliveira
    • Re: Current using -Os -pipe -march=pentium3m, Gary Jennejohn
  • Re: Current using -Os -pipe -march=pentium3m, Oliver Fromme
    • Re: Current using -Os -pipe -march=pentium3m, Daniel de Oliveira
      • Re: Current using -Os -pipe -march=pentium3m, Daniel de Oliveira
  • Re: Current using -Os -pipe -march=pentium3m, Michael Proto
    • Re: Current using -Os -pipe -march=pentium3m, Daniel de Oliveira
      • Re: Current using -Os -pipe -march=pentium3m, Michael Proto
  • Re: Current using -Os -pipe -march=pentium3m, Alexander Leidinger
• man page for CPU_SET, Stephen Montgomery-Smith
  • Re: man page for CPU_SET, Christian Brueffer
• Unable to boot Asus P5QL-EM w/ acpi enabled, Jia-Shiun Li
  • Re: Unable to boot Asus P5QL-EM w/ acpi enabled, Jia-Shiun Li
    • Re: Unable to boot Asus P5QL-EM w/ acpi enabled, jiashiun li
      • Re: Unable to boot Asus P5QL-EM w/ acpi enabled, John Baldwin
      • Re: Unable to boot Asus P5QL-EM w/ acpi enabled, Jia-Shiun Li
      • Re: Unable to boot Asus P5QL-EM w/ acpi enabled, Navdeep Parhar
      • Re: Unable to boot Asus P5QL-EM w/ acpi enabled, John Baldwin
• dtrace status, Roman Divacky
  • Re: dtrace status, John Birrell
    • Re: dtrace status, Alexey Shuvaev
      • Re: dtrace status, Roman Divacky
    • Re: dtrace status, Lars Engels
      • Re: dtrace status, Daniel Gerzo
      • Re: dtrace status, John Birrell
      • Re: dtrace status, Juergen Lock
• Re: Attansic L2 driver test request, Henri-Pierre Charles
  • Re: Attansic L2 driver test request, Stanislav Sedov
    • Re: Attansic L2 driver test request, Pyun YongHyeon
      • Re: Attansic L2 driver test request, Stanislav Sedov
• PATCH: crypto/openssl/crypto/engine/eng_table.c, Ian Freislich
  • Re: PATCH: crypto/openssl/crypto/engine/eng_table.c, Ian FREISLICH
  • Re: PATCH: crypto/openssl/crypto/engine/eng_table.c, Mike Tancsa
• msk(4) issues, Ian Freislich
  • Re: msk(4) issues, Rui Paulo
  • Re: msk(4) issues, David Schultz
    • Re: msk(4) issues, Pyun YongHyeon
  • Re: msk(4) issues, Pyun YongHyeon
  • Re: msk(4) issues, Ian FREISLICH
    • Re: msk(4) issues, Pyun YongHyeon
• [CFR/T] multi-/no-IP jail patch for HEAD, Bjoern A. Zeeb
  • Re: [CFR/T] multi-/no-IP jail patch for HEAD, Redd Vinylene
• Re: [CFT/R] IPv4 source address selection, Bjoern A. Zeeb
  • Re: [CFT/R] IPv4 source address selection, Julian Elischer
• Fdisk broken on Current ?, Manfred Antar
• Is fork() hook ever possible?, Andrey Chernov
  • Re: Is fork() hook ever possible?, Bob Bishop
    • Re: Is fork() hook ever possible?, Andrey Chernov
      • Re: Is fork() hook ever possible?, Attilio Rao
      • Re: Is fork() hook ever possible?, Andrey Chernov
      • Re: Is fork() hook ever possible?, Daniel Eischen
      • Re: Is fork() hook ever possible?, Andrey Chernov
      • Re: Is fork() hook ever possible?, Daniel Eischen
      • Re: Is fork() hook ever possible?, Kostik Belousov
  • Re: Is fork() hook ever possible?, Max Laier
    • Re: Is fork() hook ever possible?, Andrey Chernov
      • Re: Is fork() hook ever possible?, Daniel Eischen
      • Re: Is fork() hook ever possible?, Andrey Chernov
      • Re: Is fork() hook ever possible?, Poul-Henning Kamp
      • Re: Is fork() hook ever possible?, John Baldwin
      • Re: Is fork() hook ever possible?, Poul-Henning Kamp
      • Re: Is fork() hook ever possible?, Andrey Chernov
      • Re: Is fork() hook ever possible?, Poul-Henning Kamp
      • Re: Is fork() hook ever possible?, Andrey Chernov
      • Re: Is fork() hook ever possible?, Andrey Chernov
      • Re: Is fork() hook ever possible?, Poul-Henning Kamp
      • Re: Is fork() hook ever possible?, Andrey Chernov
      • Re: Is fork() hook ever possible?, Poul-Henning Kamp
      • Re: Is fork() hook ever possible?, Andrey Chernov
      • Re: Is fork() hook ever possible?, Max Laier
      • Re: Is fork() hook ever possible?, Andrey Chernov
  • Re: Is fork() hook ever possible?, David Schultz
    • Re: Is fork() hook ever possible?, Andrey Chernov
• PERC6/i/e cli, Danny Braniss
  • Re: PERC6/i/e cli, Stefan Lambrev
    • Re: PERC6/i/e cli, Danny Braniss
    • Re: PERC6/i/e cli, Alexander Leidinger
      • Re: PERC6/i/e cli, Stefan Lambrev
      • Re: PERC6/i/e cli, Alexander Leidinger
      • Re: PERC6/i/e cli, Roman Divacky
      • Re: PERC6/i/e cli, Alexander Leidinger
      • Re: PERC6/i/e cli, Danny Braniss
• [PATCH] New patch for cvsmode in csup, Ulf Lilleengen
• Benq S41-HC50 can not setup FreeBSD, ayihu
• [PATCH] Fix get max luns delay for QEMU USB disks, Bruce M Simpson
• sio => uart: one port is gone, Andriy Gapon
  • Re: sio => uart: one port is gone, Mike Tancsa
    • Re: sio => uart: one port is gone, Andriy Gapon
  • Re: sio => uart: one port is gone, Marcel Moolenaar
    • Re: sio => uart: one port is gone, Andriy Gapon
      • Re: sio => uart: one port is gone, Marcel Moolenaar
      • Re: sio => uart: one port is gone, Andriy Gapon
      • Re: sio => uart: one port is gone, Marcel Moolenaar
      • Re: sio => uart: one port is gone, John Baldwin
      • Re: sio => uart: one port is gone, Marcel Moolenaar
      • Re: sio => uart: one port is gone, John Baldwin
      • Re: sio => uart: one port is gone, Brooks Davis
      • Re: sio => uart: one port is gone, Marcel Moolenaar
      • Re: sio => uart: one port is gone, Andriy Gapon
      • Re: sio => uart: one port is gone, Marcel Moolenaar
      • Re: sio => uart: one port is gone, John Baldwin
      • Re: sio => uart: one port is gone, Peter Wemm
      • Re: sio => uart: one port is gone, John Baldwin
      • Re: sio => uart: one port is gone, Ed Schouten
    • Re: sio => uart: one port is gone, Andriy Gapon
      • Re: sio => uart: one port is gone, Danny Braniss
      • Re: sio => uart: one port is gone, Andriy Gapon
• cleandifles in kmod.mk, Dmitry Morozovsky
• pjd's ZFS 2008-07-27 patches against HEAD, Steven Schlansker
  • Message not available
    • Re: pjd's ZFS 2008-07-27 patches against HEAD, Steven Schlansker
  • Re: pjd's ZFS 2008-07-27 patches against HEAD, swell . k
    • Re: pjd's ZFS 2008-07-27 patches against HEAD, Steven Schlansker
  • <Possible follow-ups>
  • pjd's ZFS 2008-07-27 patches against HEAD, Steven Schlansker
• [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
• Fwd: bin/125932: pkg_add(1) doesn't prompt for root credentials and then fails badly, Garrett Cooper
• Improved multiprocessor usage on amd64, Stephen Montgomery-Smith
  • Re: Improved multiprocessor usage on amd64, Josh Carroll
  • Re: Improved multiprocessor usage on amd64, cpghost
    • Re: Improved multiprocessor usage on amd64, Stephen Montgomery-Smith
    • Re: Improved multiprocessor usage on amd64, Oliver Fromme
      • Re: Improved multiprocessor usage on amd64, cpghost
  • Re: Improved multiprocessor usage on amd64, Martin Cracauer
    • Re: Improved multiprocessor usage on amd64, Stephen Montgomery-Smith
      • Re: Improved multiprocessor usage on amd64, Steve Kargl
      • Re: Improved multiprocessor usage on amd64, Stephen Montgomery-Smith
      • Re: Improved multiprocessor usage on amd64, Stephen Montgomery-Smith
      • Re: Improved multiprocessor usage on amd64, Dan Nelson
      • Re: Improved multiprocessor usage on amd64, Stephen Montgomery-Smith
• [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
• cdevpriv and mmap(2), Kostik Belousov
  • Re: cdevpriv and mmap(2), Robert Watson
    • Re: cdevpriv and mmap(2), Kostik Belousov
  • Re: cdevpriv and mmap(2), Robert Noland
• /usr/src/sys/modules/aout/Makefile, Randy Bush
  • Re: /usr/src/sys/modules/aout/Makefile, Randy Bush
  • Re: /usr/src/sys/modules/aout/Makefile, Peter Jeremy
• FreeBSD 7.1-BETA/6.4-BETA Available..., Ken Smith
• New snd_hda driver came in., Alexander Motin
  • Re: New snd_hda driver came in., Alexander Leidinger
    • Re: New snd_hda driver came in., Alexander Motin
      • Re: New snd_hda driver came in., army.of.root@xxxxxxxxxxxxxx
      • Re: New snd_hda driver came in., Alexander Motin
  • Re: New snd_hda driver came in., Alex Keda
    • Re: New snd_hda driver came in., Alexander Motin
      • Message not available
      • Re: New snd_hda driver came in., Alexander Motin
      • Re: New snd_hda driver came in., Alex Keda
      • Re: New snd_hda driver came in., Alexander Motin
      • Re: New snd_hda driver came in., Alex Keda
      • Re: New snd_hda driver came in., Alex Keda
  • Re: New snd_hda driver came in., Ian FREISLICH
    • Re: New snd_hda driver came in., Alexander Motin
    • Re: New snd_hda driver came in., Ian FREISLICH
      • Re: New snd_hda driver came in., Alexander Motin
      • Re: New snd_hda driver came in., Ian FREISLICH
• Re: mpsafetty and [missing] multi put char, Hans Petter Selasky
  • Re: mpsafetty and [missing] multi put char, Ed Schouten
    • Re: mpsafetty and [missing] multi put char, Hans Petter Selasky
• Re: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST, Alexandre \"Sunny\" Kovalenko
  • Re: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST, Rui Paulo
    • Re: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST, Kostik Belousov
      • Re: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST, Alexandre \"Sunny\" Kovalenko
      • Re: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST, Rui Paulo
  • <Possible follow-ups>
  • Re: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST, Henri-Pierre Charles
    • Re: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST, Henri-Pierre Charles
      • Re: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST, Vincent Hoffman
    • Re: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST, Duane Wessels
      • Re: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST, Frank Mayhar
      • Re: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST, Sam Leffler
      • Re: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST, Frank Mayhar
  • Re: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST, Adam McDougall
• SOLVED? Re: geom_label & firewire & sbp, Igor R
• serial console on 8.x (probably sio vs uart), Garance A Drosihn
  • Re: serial console on 8.x (probably sio vs uart), Marcel Moolenaar
    • Re: serial console on 8.x (probably sio vs uart), Peter Wemm
      • Re: serial console on 8.x (probably sio vs uart), Julian Elischer
      • Re: serial console on 8.x (probably sio vs uart), Marcel Moolenaar
      • Re: serial console on 8.x (probably sio vs uart), Julian Elischer
      • Re: serial console on 8.x (probably sio vs uart), Garance A Drosihn
      • Re: serial console on 8.x (probably sio vs uart), Julian Elischer
      • Re: serial console on 8.x (probably sio vs uart), Garance A Drosihn
      • Re: serial console on 8.x (probably sio vs uart), Julian Elischer
    • Re: serial console on 8.x (probably sio vs uart), Bernd Walter
• nullfs panic with recent current, Oleg Bulyzhin
  • Re: nullfs panic with recent current, John Baldwin
• Re: "legacy" usb stack fixes (was: Re: HEADSUP new usb code coming in.), Hans Petter Selasky
  • Re: "legacy" usb stack fixes (was: Re: HEADSUP new usb code coming in.), Rink Springer
    • Re: "legacy" usb stack fixes, M. Warner Losh
      • Re: "legacy" usb stack fixes, Hans Petter Selasky
      • Re: "legacy" usb stack fixes, John Baldwin
      • Re: "legacy" usb stack fixes, Scott Long
      • Re: "legacy" usb stack fixes, Scott Long
      • Re: "legacy" usb stack fixes, M. Warner Losh
      • Re: "legacy" usb stack fixes, Scott Long
      • Re: "legacy" usb stack fixes, Julian Elischer
      • Re: "legacy" usb stack fixes, Bernd Walter
      • Re: "legacy" usb stack fixes, Hans Petter Selasky
      • Re: "legacy" usb stack fixes, Scott Long
      • Re: "legacy" usb stack fixes, Hans Petter Selasky
    • Re: "legacy" usb stack fixes, Julian Elischer
• [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
• geom_label & firewire & sbp, Igor R
  • Re: geom_label & firewire & sbp, Wojciech A. Koszek
    • Re: geom_label & firewire & sbp, Igor R
• Intel GMA x4500 / xorg help, Tony Sim
  • Re: Intel GMA x4500 / xorg help, Dag-Erling Smørgrav
  • <Possible follow-ups>
  • Intel GMA x4500 / xorg help, vermaden
    • Re: Intel GMA x4500 / xorg help, Tony Sim
      • Re: Intel GMA x4500 / xorg help, Robert Noland
      • Re: Intel GMA x4500 / xorg help, Robert Noland
      • Re: Intel GMA x4500 / xorg help, Robert Noland
• ad4 detached, Alex Keda
  • Re: ad4 detached, Alex Keda
• amd64 hangs on boot, backing out 181987 fixes it, Navdeep Parhar
• wpa_supplicant not started, Alex Keda
  • Re: wpa_supplicant not started, Kevin Oberman
  • Re: wpa_supplicant not started, Brooks Davis
  • Re: wpa_supplicant not started, Dimitry Andric
    • Re: wpa_supplicant not started, Alex Keda
      • Re: wpa_supplicant not started, Dimitry Andric
  • Re: wpa_supplicant not started, Ian FREISLICH
• Re: jails, gahn
• Sun Neptune NIU support, Peter Jeremy
  • Re: Sun Neptune NIU support, Kip Macy
    • Re: Sun Neptune NIU support, Peter Jeremy
• xorgconfig / X -configure / startx causes fatal crash, Tony Sim
  • Re: xorgconfig / X -configure / startx causes fatal crash, Sean Bruno
• mdconfig), uid 0: exited on signal 11, Randy Bush
  • Re: mdconfig), uid 0: exited on signal 11, Randy Bush
    • RE: mdconfig), uid 0: exited on signal 11, Mark Picone
      • Re: mdconfig), uid 0: exited on signal 11, Randy Bush
  • Re: mdconfig), uid 0: exited on signal 11, Jason Fesler
• freebsd 7.0 and jail, gahn
  • Re: freebsd 7.0 and jail, Oliver Peter
  • Re: freebsd 7.0 and jail, Primeroz lists
    • Re: freebsd 7.0 and jail, gahn
• [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/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
    • Re: [head tinderbox] failure on i386/i386, Kai Wang
  • [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, Roman Kurakin
• [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
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on amd64/amd64, Giorgos Keramidas
• bsd versus linux device drivers, vehemens
  • Re: bsd versus linux device drivers, Kostik Belousov
    • Re: bsd versus linux device drivers, vehemens
      • Re: bsd versus linux device drivers, Robert Watson
      • Re: bsd versus linux device drivers, vehemens
      • cdefpriv usage (was: bsd versus linux device drivers), vehemens
      • Re: cdefpriv usage (was: bsd versus linux device drivers), Kostik Belousov
      • Re: cdefpriv usage (was: bsd versus linux device drivers), vehemens
      • Re: cdefpriv usage (was: bsd versus linux device drivers), vehemens
      • Re: cdefpriv usage (was: bsd versus linux device drivers), Kostik Belousov
      • Re: cdefpriv usage (was: bsd versus linux device drivers), Mark Linimon
      • Re: bsd versus linux device drivers, John Baldwin
• Re: the future of sun4v, Darren Reed
• Crash when loading zfs.ko, Joe Marcus Clarke
  • Re: Crash when loading zfs.ko, Pawel Jakub Dawidek
    • Re: Crash when loading zfs.ko, Joe Marcus Clarke
• AMD Family 10h cpufreq driver, G. Otsuji
  • Re: AMD Family 10h cpufreq driver, fluffles.net
    • Re: AMD Family 10h cpufreq driver, G.Otsuji
      • Re: AMD Family 10h cpufreq driver, fluffles.net
      • Re: AMD Family 10h cpufreq driver, G .Otsuji
      • Re: AMD Family 10h cpufreq driver, fluffles.net
      • Re: AMD Family 10h cpufreq driver, G .Otsuji
      • Re: AMD Family 10h cpufreq driver, fluffles.net
      • Re: AMD Family 10h cpufreq driver, G .Otsuji
      • Re: AMD Family 10h cpufreq driver, G .Otsuji
    • Re: AMD Family 10h cpufreq driver, G. Otsuji
      • Re: AMD Family 10h cpufreq driver, cpghost
      • Re: AMD Family 10h cpufreq driver, fluffles.net
      • Re: AMD Family 10h cpufreq driver, cpghost
      • Re: AMD Family 10h cpufreq driver, Poul-Henning Kamp
      • Re: AMD Family 10h cpufreq driver, G .Otsuji
      • Message not available
      • Re: AMD Family 10h cpufreq driver, G .Otsuji
      • Re: AMD Family 10h cpufreq driver, fluffles.net
      • Re: AMD Family 10h cpufreq driver, G .Otsuji
      • Re: AMD Family 10h cpufreq driver, Poul-Henning Kamp
• ppp not passing long packets (probably after MPSAFE_TTY), Yuriy Tsibizov
  • <Possible follow-ups>
  • Re: ppp not passing long packets (probably after MPSAFE_TTY), Ed Schouten
    • Re: ppp not passing long packets (probably after MPSAFE_TTY), Yuriy Tsibizov
    • Re: ppp not passing long packets (probably after MPSAFE_TTY), Yuriy Tsibizov
• sysctls and if_bridge, Michael Proto
  • Re: sysctls and if_bridge, Michael Proto
    • Re: sysctls and if_bridge, Eygene Ryabinkin
      • Re: sysctls and if_bridge, Michael Proto
      • Re: sysctls and if_bridge, Eygene Ryabinkin
      • Re: sysctls and if_bridge, Michael Proto
      • Re: sysctls and if_bridge, Michael Proto
      • Re: sysctls and if_bridge, Eygene Ryabinkin
• Do you need x11-drivers/xf86-video-radeonhd-devel? (Re: How about AMD Puma platform support?), Norikatsu Shigemura
  • Re: Do you need x11-drivers/xf86-video-radeonhd-devel? (Re: How about AMD Puma platform support?), Boris Samorodov
    • Re: Do you need x11-drivers/xf86-video-radeonhd-devel? (Re: How about AMD Puma platform support?), Norikatsu Shigemura
      • Re: Do you need x11-drivers/xf86-video-radeonhd-devel? (Re: How about AMD Puma platform support?), Norikatsu Shigemura
      • Re: Do you need x11-drivers/xf86-video-radeonhd-devel? (Re: How about AMD Puma platform support?), Boris Samorodov
      • Re: Do you need x11-drivers/xf86-video-radeonhd-devel? (Re: How about AMD Puma platform support?), Kostik Belousov
      • radeon and FreeBSD freeze (was: Re: Do you need x11-drivers/xf86-video-radeonhd-devel?), Boris Samorodov
      • Re: Do you need x11-drivers/xf86-video-radeonhd-devel? (Re: How about AMD Puma platform support?), Ian FREISLICH
      • Re: Do you need x11-drivers/xf86-video-radeonhd-devel? (Re: How about AMD Puma platform support?), Kostik Belousov
      • Re: Do you need x11-drivers/xf86-video-radeonhd-devel? (Re: How about AMD Puma platform support?), Ian FREISLICH
      • Re: Do you need x11-drivers/xf86-video-radeonhd-devel? (Re: How about AMD Puma platform support?), Kostik Belousov
      • Re: Do you need x11-drivers/xf86-video-radeonhd-devel? (Re: How about AMD Puma platform support?), Ian FREISLICH
• Segmentation fault in malloc_usable_size() (libc), Jille Timmermans
  • Re: Segmentation fault in malloc_usable_size() (libc), Jason Evans
    • Re: Segmentation fault in malloc_usable_size() (libc), David Xu
      • Re: Segmentation fault in malloc_usable_size() (libc), Jason Evans
      • [SOLVED] Re: Segmentation fault in malloc_usable_size() (libc), Jille Timmermans
• (another) panic on shutdown (spin lock held too long), Thierry Herbelot
• Panic on boot on Lenovo ThinkCentre, before copyright message appears, Antony Mawer
  • Re: Panic on boot on Lenovo ThinkCentre, before copyright message appears [SOLVED], Antony Mawer
• panic on shutdown anyone (insmntque())?, Xin LI
  • Re: panic on shutdown anyone (insmntque())?, Kris Kennaway
    • Re: panic on shutdown anyone (insmntque())?, Xin LI
      • Re: panic on shutdown anyone (insmntque())?, Kris Kennaway
      • Re: panic on shutdown anyone (insmntque())?, Oliver Peter
      • Re: panic on shutdown anyone (insmntque())?, Kris Kennaway
      • Re: panic on shutdown anyone (insmntque())?, Guy Brand
      • Message not available
      • Re: panic on shutdown anyone (insmntque())?, Richard Todd
      • Re: panic on shutdown anyone (insmntque())?, Kris Kennaway
      • Re: panic on shutdown anyone (insmntque())?, Kostik Belousov
      • Re: panic on shutdown anyone (insmntque())?, Pawel Jakub Dawidek
      • Re: panic on shutdown anyone (insmntque())?, Richard Todd
      • Re: panic on shutdown anyone (insmntque())?, Pawel Jakub Dawidek
      • Re: panic on shutdown anyone (insmntque())?, Richard Todd
• panic in rt_check_fib(), Giorgos Keramidas
  • Re: panic in rt_check_fib(), Robert Watson
    • Re: panic in rt_check_fib(), Robert Watson
      • Re: panic in rt_check_fib(), John Baldwin
    • Re: panic in rt_check_fib(), Julian Elischer
      • Re: panic in rt_check_fib(), Giorgos Keramidas
      • Re: panic in rt_check_fib(), Giorgos Keramidas
      • Re: panic in rt_check_fib(), Julian Elischer
      • Re: panic in rt_check_fib(), Julian Elischer
      • Re: panic in rt_check_fib(), Giorgos Keramidas
      • Re: panic in rt_check_fib(), Julian Elischer
      • Re: panic in rt_check_fib(), Giorgos Keramidas
• [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 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
    • Re: [head tinderbox] failure on ia64/ia64, Kostik Belousov
      • Re: [head tinderbox] failure on ia64/ia64, Marcel Moolenaar
      • Re: [head tinderbox] failure on ia64/ia64, Peter Wemm
      • Re: [head tinderbox] failure on ia64/ia64, Marcel Moolenaar
      • Re: [head tinderbox] failure on ia64/ia64, Peter Wemm
      • Re: [head tinderbox] failure on ia64/ia64, Peter Wemm
• Re: CFT: BSD grep, Gabor Kovesdan
• Panic at shutdown, Guy Brand
  • Re: Panic at shutdown, Oliver Peter
• lockmgr_args, lock order reversal: (sleepable after non-sleepable), David Xu
  • Re: lockmgr_args, lock order reversal: (sleepable after non-sleepable), John Baldwin
• cpio reporting too many 'blocks', Giorgos Keramidas
  • Re: cpio reporting too many 'blocks', Tim Kientzle
    • Re: cpio reporting too many 'blocks', Giorgos Keramidas
      • Re: cpio reporting too many 'blocks', Tim Kientzle
      • Re: cpio reporting too many 'blocks', Giorgos Keramidas
• Kthread kill, kr Lekha
  • Re: Kthread kill, John Baldwin
    • Re: Kthread kill, kr Lekha
      • Re: Kthread kill, Julian Elischer
• install failure for loader, Julian Elischer
  • Re: install failure for loader, Julian Elischer
• MTRR fixup?, Bernd Walter
  • Re: MTRR fixup?, Rink Springer
    • Message not available
      • Re: MTRR fixup?, Richard Todd
  • Re: MTRR fixup?, David Malone
    • Re: MTRR fixup?, Josh Carroll
      • Re: MTRR fixup?, Scott Long
      • Re: MTRR fixup?, Josh Carroll
      • Re: MTRR fixup?, Scott Long
      • Re: MTRR fixup?, Josh Carroll
      • Re: MTRR fixup?, Josh Carroll
      • Re: MTRR fixup?, Scott Long
      • Re: MTRR fixup?, Josh Carroll
    • Re: MTRR fixup?, Josh Carroll
    • Re: MTRR fixup?, Bernd Walter
      • Re: MTRR fixup?, Bernd Walter
      • Re: MTRR fixup?, Bernd Walter
      • Re: MTRR fixup?, John Baldwin
• Why VESA and DPMS are available only for i386?, Carlos A. M. dos Santos
  • Re: Why VESA and DPMS are available only for i386?, Xin LI
    • Re: Why VESA and DPMS are available only for i386?, Carlos A. M. dos Santos
      • Re: Why VESA and DPMS are available only for i386?, Oliver Fromme
      • Re: Why VESA and DPMS are available only for i386?, Jung-uk Kim
      • Re: Why VESA and DPMS are available only for i386?, Carlos A. M. dos Santos
      • Re: Why VESA and DPMS are available only for i386?, Jung-uk Kim
      • Re: Why VESA and DPMS are available only for i386?, Carlos A. M. dos Santos
      • Re: Why VESA and DPMS are available only for i386?, Jung-uk Kim
      • Re: Why VESA and DPMS are available only for i386?, Carlos A. M. dos Santos
      • Re: Why VESA and DPMS are available only for i386?, Oliver Fromme
      • Re: Why VESA and DPMS are available only for i386?, Carlos A. M. dos Santos
      • Re: Why VESA and DPMS are available only for i386?, Xin LI
  • <Possible follow-ups>
  • Re: Why VESA and DPMS are available only for i386?, Pedro Giffuni
    • Re: Why VESA and DPMS are available only for i386?, Peter Wemm
    • Re: Why VESA and DPMS are available only for i386?, Peter Jeremy
• drm causes kernel panic, Steve Kargl
  • Re: drm causes kernel panic, Robert Noland
    • Re: drm causes kernel panic, Steve Kargl
      • Re: drm causes kernel panic, Robert Noland
      • Re: drm causes kernel panic, Steve Kargl
      • Re: drm causes kernel panic, Robert Noland
      • Re: drm causes kernel panic, Steve Kargl
      • Re: drm causes kernel panic, Robert Noland
      • Re: drm causes kernel panic, Steve Kargl
      • Re: drm causes kernel panic, Robert Noland
• m_uiotombuf alignment, Andrew Thompson
  • Re: m_uiotombuf alignment, Maksim Yevmenkin
    • Re: m_uiotombuf alignment, Andrew Thompson
      • Re: m_uiotombuf alignment, Maksim Yevmenkin
• CFT: pts(4) "packet mode" support, Ed Schouten
  • Re: CFT: pts(4) "packet mode" support, Giorgos Keramidas
    • Re: CFT: pts(4) "packet mode" support, Giorgos Keramidas
• Re: rtentry panic with FIB, John Baldwin
  • Re: rtentry panic with FIB, Bjoern A. Zeeb
  • Re: rtentry panic with FIB, Julian Elischer
    • Re: rtentry panic with FIB, Kris Kennaway
• Re: System, diagnose thyself: auto-documentation for crashes, John Baldwin
• Re: Multiple routing table support commited, NAKAJI Hiroyuki
  • Re: Multiple routing table support commited, Julian Elischer
  • Re: Multiple routing table support commited, Julian Elischer
    • Re: Multiple routing table support commited, Julian Elischer
• [patch] ntp no longer compiles using WITHOUT_GNU_SUPPORT, Ben Kelly
  • Re: [patch] ntp no longer compiles using WITHOUT_GNU_SUPPORT, Ollivier Robert
• Re: Marvell Yukon 2 88E8040, rocketboy811
  • Re: Marvell Yukon 2 88E8040, Stephen Montgomery-Smith
    • Re: Marvell Yukon 2 88E8040, Pyun YongHyeon
• powerd and multicore, David Naylor
  • Re: powerd and multicore, Gavin Atkinson
• k8temp choose the higher temp of the two sensors on one core, army.of.root@xxxxxxxxxxxxxx
  • Re: k8temp choose the higher temp of the two sensors on one core, Rui Paulo
  • Re: k8temp choose the higher temp of the two sensors on one core, Dag-Erling Smørgrav
    • Re: k8temp choose the higher temp of the two sensors on one core, Rui Paulo
• Re: __tls_get_addr problem with recent current, Vyacheslav Bocharov
  • Re: __tls_get_addr problem with recent current, Kostik Belousov
    • Re: __tls_get_addr problem with recent current, Adam Jacob Muller
      • Re: __tls_get_addr problem with recent current, Kostik Belousov
      • Re: __tls_get_addr problem with recent current, Adam Jacob Muller
      • Re: __tls_get_addr problem with recent current, Kostik Belousov
  • <Possible follow-ups>
  • Re: __tls_get_addr problem with recent current, Artem Belevich
• Apache.sh on current, Manfred Antar
  • Re: Apache.sh on current, Claus Guttesen
    • Message not available
      • Re: Apache.sh on current, Manfred Antar
      • /usr/bin/limits (WAS: Re: Apache.sh on current), Yuriy Tsibizov
      • Re: /usr/bin/limits (WAS: Re: Apache.sh on current), Ed Schouten
      • Re: /usr/bin/limits (WAS: Re: Apache.sh on current), Yuriy Tsibizov
      • Re: /usr/bin/limits (WAS: Re: Apache.sh on current), Yuriy Tsibizov
      • Re: /usr/bin/limits (WAS: Re: Apache.sh on current), Ed Schouten
• [mgleason@ncftp.com: Re: [wxs@FreeBSD.org: Re: cvs commit: ports/ftp/ncftp3 pkg-plist]], Renato Botelho
• named mystery -- error: dumping master file: master/tmp-wTjhUzoix6, Alex Goncharov
  • Re: named mystery -- error: dumping master file: master/tmp-wTjhUzoix6, Oliver Fromme
    • Re: named mystery -- error: dumping master file: master/tmp-wTjhUzoix6, Alex Goncharov
      • Re: named mystery -- error: dumping master file: master/tmp-wTjhUzoix6, Stefan Bethke
      • Re: named mystery -- error: dumping master file: master/tmp-wTjhUzoix6, Alex Goncharov
      • Re: named mystery -- error: dumping master file: ?master/tmp-wTjhUzoix6, Oliver Fromme
      • Re: named mystery -- error: dumping master file: ?master/tmp-wTjhUzoix6, Alex Goncharov
      • Re: named mystery -- error: dumping master file: ??master/tmp-wTjhUzoix6, Oliver Fromme
      • Re: named mystery -- error: dumping master file: ??master/tmp-wTjhUzoix6, Alex Goncharov
      • Re: named mystery -- error: dumping master file: master/tmp-wTjhUzoix6, Doug Barton
  • Re: named mystery -- error: dumping master file: master/tmp-wTjhUzoix6, Stefan Bethke
    • Re: named mystery -- error: dumping master file: master/tmp-wTjhUzoix6, Alex Goncharov
• Re: csh history and pts, Alexey Shuvaev
  • Re: csh history and pts, Roman Divacky
    • Re: csh history and pts, Thomas Hurst
      • Re: csh history and pts, Roman Divacky
      • Re: csh history and pts, Peter Wemm
• Re: ZFS patches., kevin
  • RE: ZFS patches., Thomas Sparrevohn
• 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, John Baldwin
      • Re: No root filesystem, Garrett Cooper
      • Re: No root filesystem, Pascal Hofstee
      • Re: No root filesystem, clemens fischer
      • Re: No root filesystem, Rui Paulo
      • Re: No root filesystem, Peter Wemm
      • Re: No root filesystem, Christian Weisgerber
      • Re: No root filesystem, John Baldwin
      • 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, John Baldwin
      • Re: No root filesystem, Mark Atkinson
      • Re: No root filesystem, clemens fischer
      • Re: No root filesystem, Mark Atkinson
      • Re: No root filesystem, Peter Wemm
    • Re: No root filesystem, Mark Atkinson
• RFC: moving sysutils/fusefs-kmod to base system, Aryeh M. Friedman
  • Re: RFC: moving sysutils/fusefs-kmod to base system, Oliver Fromme
  • Re: RFC: moving sysutils/fusefs-kmod to base system, Volodymyr Kostyrko
    • Re: RFC: moving sysutils/fusefs-kmod to base system, Daniel O'Connor
      • Re: RFC: moving sysutils/fusefs-kmod to base system, Claus Guttesen
      • Re: RFC: moving sysutils/fusefs-kmod to base system, Daniel O'Connor
      • Re: RFC: moving sysutils/fusefs-kmod to base system, L Campbell
      • Re: RFC: moving sysutils/fusefs-kmod to base system, Daniel O'Connor
• Questions on how to use the Head files Pyun YongHyeon has created for re driver, Tony Sim
  • Re: Questions on how to use the Head files Pyun YongHyeon has created for re driver, Pyun YongHyeon
  • Re: Questions on how to use the Head files Pyun YongHyeon has created for re driver, Aryeh M. Friedman
• Re: [BUG] I think sleepqueue need to be protected in sleepq_broadcast, Tor Egge
  • 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, John Baldwin
    • Re: [BUG] I think sleepqueue need to be protected in sleepq_broadcast, Peter Wemm
      • 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, Peter Wemm
    • 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, Attilio Rao

• Security
• UNIX
• Linux
• Coding
• Usenet

• Mailing-Lists
• Newsgroups
• About
• Privacy
• Search
• Imprint

unix.derkeiler.com  > Mailing-Lists  > FreeBSD  > current  > 2008-09