freebsd-current

• Date Index

---

• Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0"., Jan Henrik Sylvester
• Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0"., O. Hartmann
  • Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0"., Daniel Eischen
  • Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0"., Alex Goncharov
    • Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0"., Robert Noland
  • Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0"., Mel
• zyd(4) adapter, Andrew Thompson
• Problem with usbconfig, not working, Arnar Mar Sig
  • Re: Problem with usbconfig, not working, Hans Petter Selasky
    • Re: Problem with usbconfig, not working, Arnar Mar Sig
• RFC: Change mtree nsec handling?, Tim Kientzle
  • Re: RFC: Change mtree nsec handling?, Maxim Sobolev
    • Re: RFC: Change mtree nsec handling?, Poul-Henning Kamp
    • Re: RFC: Change mtree nsec handling?, Peter Jeremy
      • Re: RFC: Change mtree nsec handling?, Maxim Sobolev
  • Re: RFC: Change mtree nsec handling?, Poul-Henning Kamp
    • Re: RFC: Change mtree nsec handling?, Tim Kientzle
      • Re: RFC: Change mtree nsec handling?, Kostik Belousov
      • Re: RFC: Change mtree nsec handling?, Poul-Henning Kamp
• uhub_reattach_port:413: could not allocate new device!, Chris Ruiz
  • Re: uhub_reattach_port:413: could not allocate new device!, Hans Petter Selasky
    • Re: uhub_reattach_port:413: could not allocate new device!, Chris Ruiz
      • Re: uhub_reattach_port:413: could not allocate new device!, Hans Petter Selasky
• ath cannot find my wireless network any more, Lars Engels
  • Re: ath cannot find my wireless network any more, Andrew Thompson
    • Re: ath cannot find my wireless network any more, Lars Engels
      • Re: ath cannot find my wireless network any more, Sam Leffler
      • Re: ath cannot find my wireless network any more, Lars Engels
      • Re: ath cannot find my wireless network any more, Paul B. Mahol
      • Re: ath cannot find my wireless network any more, Lars Engels
• Solaris live upgrade like FreeBSD ZFS-rootfs update, Philipp Wuensche
  • Re: Solaris live upgrade like FreeBSD ZFS-rootfs update, David Schultz
    • Re: Solaris live upgrade like FreeBSD ZFS-rootfs update, Philipp Wuensche
  • Re: Solaris live upgrade like FreeBSD ZFS-rootfs update, Ollivier Robert
    • Re: Solaris live upgrade like FreeBSD ZFS-rootfs update, Philipp Wuensche
• Panic with NTFS, Carlos Corona
  • Re: Panic with NTFS, Attilio Rao
• reminder: bugathon upcoming this weekend, Mark Linimon
• console oddities, Michiel Boland
  • Re: console oddities, Ed Schouten
    • Re: console oddities, Ed Schouten
      • Re: console oddities, Michiel Boland
    • Re: console oddities, Renato Botelho
• sysctl question, Roman Divacky
  • Re: sysctl question, Scott Long
  • Re: sysctl question, John Baldwin
    • Re: sysctl question, Roman Divacky
      • Re: sysctl question, John Baldwin
      • Re: sysctl question, Roman Divacky
• [PATCH] improving netncp locking, Attilio Rao
• Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?), Michel Talon
  • Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?), Chuck Swiger
    • Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?), Daniel O'Connor
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?), Xin LI
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?), Eitan Adler
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?), Christoph Mallon
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?), Garance A Drosihn
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?), Andrew Reilly
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?), Daniel O'Connor
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?), Steve Kargl
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?), Andrew Reilly
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?), Garrett Cooper
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?), Christoph Mallon
  • <Possible follow-ups>
  • Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?), Pedro F. Giffuni
• Panic from wpa_supplicant in uma_large_free(), David Wolfskill
  • Re: Panic from wpa_supplicant in uma_large_free(), Sam Leffler
  • Re: Panic from wpa_supplicant in uma_large_free(), Sam Leffler
  • Re: Panic from wpa_supplicant in uma_large_free(), Sam Leffler
  • <Possible follow-ups>
  • Re: Panic from wpa_supplicant in uma_large_free(), David Wolfskill
• completely stopped work on the ROOT zfs, Gvozdikov Veniamin
• SATA drive device moving on 8.0 current, Barney Cordoba
  • Re: SATA drive device moving on 8.0 current, pluknet
  • Re: SATA drive device moving on 8.0 current, Daniel O'Connor
    • Re: SATA drive device moving on 8.0 current, Nenhum_de_Nos
      • Re: SATA drive device moving on 8.0 current, Daniel O'Connor
      • Re: SATA drive device moving on 8.0 current, Wes Morgan
      • Re: SATA drive device moving on 8.0 current, Barney Cordoba
  • Re: SATA drive device moving on 8.0 current, Andrey V. Elsukov
    • Re: SATA drive device moving on 8.0 current, Barney Cordoba
      • Re: SATA drive device moving on 8.0 current, Richard Tector
• Jemalloc SEGV for 1MB chunk, Channa
  • Re: Jemalloc SEGV for 1MB chunk, Harti Brandt
    • Re: Jemalloc SEGV for 1MB chunk, Channa
  • Re: Jemalloc SEGV for 1MB chunk, Christoph Mallon
    • Re: Jemalloc SEGV for 1MB chunk, Channa
      • Re: Jemalloc SEGV for 1MB chunk, Christoph Mallon
      • Re: Jemalloc SEGV for 1MB chunk, Rink Springer
      • Re: Jemalloc SEGV for 1MB chunk, Danny Braniss
      • Re: Jemalloc SEGV for 1MB chunk, Channa
      • Re: Jemalloc SEGV for 1MB chunk, Christoph Mallon
      • Re: Jemalloc SEGV for 1MB chunk, Channa
      • Re: Jemalloc SEGV for 1MB chunk, Christoph Mallon
      • Re: Jemalloc SEGV for 1MB chunk, Channa
      • Re: Jemalloc SEGV for 1MB chunk, Søren Schmidt
      • Re: Jemalloc SEGV for 1MB chunk, Christoph Mallon
      • Re: Jemalloc SEGV for 1MB chunk, Bernd Walter
• build in /sys/modules broken / other way of building 1 specific module, Nick Hibma
  • Re: build in /sys/modules broken / other way of building 1 specific module, John Baldwin
• Page fault in CURRENT, Mister Olli
  • Re: Page fault in CURRENT, Kip Macy
    • Re: Page fault in CURRENT, Mister Olli
• HEADS UP: svn commit: r187803 - head/sys/net80211, Sam Leffler
• NFS mounts dissapearing, Sean Bruno
  • Re: NFS mounts dissapearing, Michiel Boland
    • Re: NFS mounts dissapearing, Sean Bruno
      • Re: NFS mounts dissapearing, Rick Macklem
      • Re: NFS mounts dissapearing, Jaakko Heinonen
      • Re: NFS mounts dissapearing, Jaakko Heinonen
      • Re: NFS mounts dissapearing, Sean Bruno
• panic: freeing free block, pluknet
  • Re: panic: freeing free block, pluknet
    • Re: panic: freeing free block, Kostik Belousov
      • Re: panic: freeing free block, pluknet
      • Re: panic: freeing free block, Kostik Belousov
      • Re: panic: freeing free block, pluknet
• cpu cooler speed, Nenhum_de_Nos
  • Re: cpu cooler speed, Alex Keda
• Exporting from a preloaded module, Barney Cordoba
• Mplayer in tty*, Carlos Corona
  • Re: Mplayer in tty*, L Campbell
  • Re: Mplayer in tty*, Paul B. Mahol
• [patch] nfs attribute cache mount options broken on CURRENT, Jaakko Heinonen
• duplicate typedefs and system headers ?, Luigi Rizzo
  • Re: duplicate typedefs and system headers ?, Christoph Mallon
    • Re: duplicate typedefs and system headers ?, Luigi Rizzo
      • Re: duplicate typedefs and system headers ?, Christoph Mallon
      • Re: duplicate typedefs and system headers ?, Luigi Rizzo
• Nvidia's feature requests, Marius Nünnerich
  • Re: Nvidia's feature requests, Roman Divacky
  • Re: Nvidia's feature requests, Robert Noland
• UFS Witness LoR, Sean Bruno
  • Re: UFS Witness LoR + 5 other LoRs, Martin
• WANTED! board models with Marvell 61XX chips, Søren Schmidt
  • Re: WANTED! board models with Marvell 61XX chips, Michael Reifenberger
  • Re: WANTED! board models with Marvell 61XX chips, Oliver Pinter
    • Re: WANTED! board models with Marvell 61XX chips, Garrett Cooper
• LPT Panic at assert lpt.c::222, Sean Bruno
  • <Possible follow-ups>
  • LPT Panic at assert lpt.c::222, Sean Bruno
• kernel: powernow0: set freq failed, err 6, Alex Keda
  • Re: kernel: powernow0: set freq failed, err 6, Alex Keda
• KDE4/DBUS weirdness on -Current, Pegasus Mc Cleaft
  • Re: KDE4/DBUS weirdness on -Current, Alberto Villa
    • Re: KDE4/DBUS weirdness on -Current, Alberto Villa
  • Re: KDE4/DBUS weirdness on -Current, Paul Wootton
    • Message not available
      • Re: KDE4/DBUS weirdness on -Current, Paul Wootton
• DMA bounce buffers, Barney Cordoba
  • Re: DMA bounce buffers, Sepherosa Ziehau
    • Re: DMA bounce buffers, Scott Long
• Re: ASUS mobo for desktop, Dmitry Marakasov
• panic in rtrequest1_fib, Michiel Boland
  • Re: panic in rtrequest1_fib, Michiel Boland
    • Re: panic in rtrequest1_fib, Kip Macy
• Reset register flag versus the actual register, Alexander Sack
  • Re: Reset register flag versus the actual register, Alexander Sack
• Problems with ixgbe, Barney Cordoba
  • Re: Problems with ixgbe, Jack Vogel
    • Re: Problems with ixgbe, Barney Cordoba
• panic: existing znode 0xffffff012629a178 for dbuf 0xffffff003bf99540, Kris Kennaway
• net80211 hostap vs powersave, Bill Paul
  • Re: net80211 hostap vs powersave, Sam Leffler
    • Re: net80211 hostap vs powersave, Chris Buechler
• Noisy make -j output, Kris Kennaway
  • Re: Noisy make -j output, David O'Brien
    • Re: Noisy make -j output, Kris Kennaway
      • Re: Noisy make -j output, David O'Brien
      • Re: Noisy make -j output, Kris Kennaway
• Prblem whit USB in FreeBSD 8, Carlos Corona
  • Re: Prblem whit USB in FreeBSD 8, Hans Petter Selasky
    • Re: Prblem whit USB in FreeBSD 8, Maxim Sobolev
      • Re: Prblem whit USB in FreeBSD 8, Peter Jeremy
      • Re: Prblem whit USB in FreeBSD 8, Szilveszter Adam
      • Re: Prblem whit USB in FreeBSD 8, Maxim Sobolev
      • Re: Prblem whit USB in FreeBSD 8, Hans Petter Selasky
      • Re: Prblem whit USB in FreeBSD 8, Andre Guibert de Bruet
• Problems with ata driver on current / Asus P5Q-E, Scott Gasch
  • Re: Problems with ata driver on current / Asus P5Q-E, Oliver Pinter
    • Re: Re: Problems with ata driver on current / Asus P5Q-E, scott . gasch
      • Re: Re: Problems with ata driver on current / Asus P5Q-E, Oliver Pinter
• Help me select hardware and software options for very large server, Terry Kennedy
  • Re: Help me select hardware and software options for very large server, Freddie Cash
    • Re: Help me select hardware and software options for very large server, Terry Kennedy
      • Re: Help me select hardware and software options for very large server, Freddie Cash
  • Re: Help me select hardware and software options for very large server, Bob Bishop
    • Re: Help me select hardware and software options for very large server, Terry Kennedy
  • Re: Help me select hardware and software options for very large server, Aristedes Maniatis
    • Re: Help me select hardware and software options for very large server, Terry Kennedy
      • Re: Help me select hardware and software options for very large ?server, Oliver Fromme
  • RE: Help me select hardware....Some real world data that might help, Paul Tice
    • Re: Help me select hardware....Some real world data that might help, Freddie Cash
      • RE: Help me select hardware....Some real world data that might help, Paul Tice
      • Re: Help me select hardware....Some real world data that might help, Freddie Cash
      • Re: Help me select hardware....Some real world data that might help, Oliver Fromme
• quickly build a single program ? (was KERNCONF and KERNFAST related), Luigi Rizzo
  • Re: quickly build a single program ?, Giorgos Keramidas
    • Re: quickly build a single program ?, Luigi Rizzo
      • Re: quickly build a single program ?, Giorgos Keramidas
• NFS data corruption, Dmitry Marakasov
  • Re: NFS data corruption, Rick Macklem
  • Data corruption with checksum offloading enabled (Was: NFS data corruption), Dmitry Marakasov
    • Re: Data corruption with checksum offloading enabled, Arno J. Klaassen
      • Re: Data corruption with checksum offloading enabled, Dmitry Marakasov
      • Message not available
      • Re: Data corruption with checksum offloading enabled, Dmitry Marakasov
• Re: [PATCH] for ng_ubt2 stalled transfers, Maksim Yevmenkin
  • Re: [PATCH] for ng_ubt2 stalled transfers, Maksim Yevmenkin
    • Re: [PATCH] for ng_ubt2 stalled transfers, Lars Engels
      • Re: [PATCH] for ng_ubt2 stalled transfers, Lars Engels
      • [PATCH2] for ng_ubt2 stalled transfers, Hans Petter Selasky
      • Re: [PATCH2] for ng_ubt2 stalled transfers, Lars Engels
      • Re: [PATCH] for ng_ubt2 stalled transfers, Maksim Yevmenkin
      • Re: [PATCH] for ng_ubt2 stalled transfers, Lars Engels
• acpi_throttle1: failed to attach P_CNT, Alex Keda
  • Re: acpi_throttle1: failed to attach P_CNT, Alex Keda
    • Re: acpi_throttle1: failed to attach P_CNT, Paul B. Mahol
      • Re: acpi_throttle1: failed to attach P_CNT, Alex Keda
• panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Lars Engels
  • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Hans Petter Selasky
    • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Maksim Yevmenkin
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Hans Petter Selasky
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Maksim Yevmenkin
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Hans Petter Selasky
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Maksim Yevmenkin
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Hans Petter Selasky
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Maksim Yevmenkin
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Julian Elischer
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Hans Petter Selasky
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Maksim Yevmenkin
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Hans Petter Selasky
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Maksim Yevmenkin
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Julian Elischer
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Maksim Yevmenkin
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Hans Petter Selasky
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Maksim Yevmenkin
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Julian Elischer
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Julian Elischer
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Maksim Yevmenkin
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Alfred Perlstein
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Maksim Yevmenkin
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Alfred Perlstein
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Julian Elischer
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Julian Elischer
  • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Ed Schouten
    • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Lars Engels
      • Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127, Maksim Yevmenkin
• sparse file issue?, dd(1) works well but tar(1) not on different partition, Daichi GOTO
  • Re: sparse file issue?, dd(1) works well but tar(1) not on different partition, Tim Kientzle
  • Re: sparse file issue?, dd(1) works well but tar(1) not on different partition, Tim Kientzle
    • Re: sparse file issue?, dd(1) works well but tar(1) not on different partition, Daichi GOTO
• UFS/VFS lock order reversal on stock 8.0-200812-AMD64, Paul Tice
  • Re: UFS/VFS lock order reversal on stock 8.0-200812-AMD64, Gavin Atkinson
    • Re: UFS/VFS lock order reversal on stock 8.0-200812-AMD64, Gavin Atkinson
      • RE: UFS/VFS lock order reversal on stock 8.0-200812-AMD64, Paul Tice
      • RE: UFS/VFS lock order reversal on stock 8.0-200812-AMD64, Gavin Atkinson
• Need testers for a network cleanup patch, Bjoern A. Zeeb
  • Re: Need testers for a network cleanup patch, Bjoern A. Zeeb
    • Re: Need testers for a network cleanup patch, Giorgos Keramidas
• Steps to debug memory/motherboard (Via VB8001) problem, George Hartzell
  • Re: Steps to debug memory/motherboard (Via VB8001) problem, Svein Skogen (listmail account)
  • Re: Steps to debug memory/motherboard (Via VB8001) problem, Chuck Swiger
  • Re: Steps to debug memory/motherboard (Via VB8001) problem, Julian Elischer
• panic on boot with today's kernel, Michiel Boland
  • Re: panic on boot with today's kernel, Dimitry Andric
    • Re: panic on boot with today's kernel, Michiel Boland
      • Re: panic on boot with today's kernel, Alexander Churanov
      • Re: panic on boot with today's kernel, Christoph Mallon
• Creating swap based ramdisks from rc.initdiskless by default, Attila Nagy
  • Re: Creating swap based ramdisks from rc.initdiskless by default, Igor Mozolevsky
    • Re: Creating swap based ramdisks from rc.initdiskless by default, Attila Nagy
      • Re: Creating swap based ramdisks from rc.initdiskless by default, Igor Mozolevsky
      • Re: Creating swap based ramdisks from rc.initdiskless by default, Ulrich Spörlein
  • Re: Creating swap based ramdisks from rc.initdiskless by default, Brooks Davis
• Backporting of Heimdal 1.1 to 7.*, Gunnar Flygt
  • Re: Backporting of Heimdal 1.1 to 7.*, Graham Todd
    • Re: Backporting of Heimdal 1.1 to 7.*, Rick Macklem
• USB2: ugd round bug? including patch to solve., Daichi GOTO
  • Re: USB2: ugd round bug? including patch to solve., Hans Petter Selasky
    • Re: USB2: ugd round bug? including patch to solve., Daichi GOTO
• dmesg for IBM T60 on 8.0, Ben Adams
  • Re: dmesg for IBM T60 on 8.0, Mister Olli
• Re: [PATCH] ppbus/ppc locking, John Baldwin
  • Re: [PATCH] ppbus/ppc locking, Bruce M. Simpson
    • Re: [PATCH] ppbus/ppc locking, John Baldwin
      • Re: [PATCH] ppbus/ppc locking, Bruce M. Simpson
      • Re: [PATCH] ppbus/ppc locking, Bruce M. Simpson
      • Re: [PATCH] ppbus/ppc locking, Bruce M. Simpson
  • Re: ppc hints ignored? Was: [PATCH] ppbus/ppc locking, Alexey Shuvaev
• KDB panic with 2 vcpus, Mister Olli
  • Re: KDB panic with 2 vcpus, Gavin Atkinson
    • Re: KDB panic with 2 vcpus, Alexander Churanov
      • Re: KDB panic with 2 vcpus, Gavin Atkinson
    • Re: KDB panic with 2 vcpus, Alexander Churanov
    • Re: KDB panic with 2 vcpus, Mister Olli
• memory alignment problems with -current on amd64?, Mark Atkinson
  • Re: memory alignment problems with -current on amd64?, Kostik Belousov
    • Re: memory alignment problems with -current on amd64?, Mark Atkinson
  • Re: memory alignment problems with -current on amd64?, Steve Kargl
• panic in softdep handling routines, Martin
  • Re: panic in softdep handling routines, Chagin Dmitry
• Binding timer interrupt to a cpu core, Barney Cordoba
  • Re: Binding timer interrupt to a cpu core, Ivan Voras
    • Re: Binding timer interrupt to a cpu core, Barney Cordoba
      • Re: Binding timer interrupt to a cpu core, Robert Watson
• [PATCH] bsdcpio core dump, Giorgos Keramidas
  • Re: [PATCH] bsdcpio core dump, Giorgos Keramidas
  • Re: [PATCH] bsdcpio core dump, Christoph Mallon
    • Re: [PATCH] bsdcpio core dump, Giorgos Keramidas
      • Re: [PATCH] bsdcpio core dump, Tim Kientzle
      • Re: [PATCH] bsdcpio core dump, Giorgos Keramidas
  • Re: [PATCH] bsdcpio core dump, Tim Kientzle
  • Re: [PATCH] bsdcpio core dump, Rink Springer
• problem with wifi on fujitsu U810., Alexander Yamshanov
  • Re: problem with wifi on fujitsu U810., Ganael LAPLANCHE
• Running on only some cores, Barney Cordoba
  • Re: Running on only some cores, Christoph Mallon
    • Re: Running on only some cores, Barney Cordoba
    • Re: Running on only some cores, Barney Cordoba
      • Re: Running on only some cores, Astrodog
  • Re: Running on only some cores, Robert Watson
• jemalloc on uniprocessor, Channa
• Re: Why LLVM may be a step forward, bf
• HEADSUP: urtw(4) to be committed soon, Weongyo Jeong
  • Re: HEADSUP: urtw(4) to be committed soon, Robert Watson
    • Re: HEADSUP: urtw(4) to be committed soon, Brooks Davis
  • Re: HEADSUP: urtw(4) to be committed soon, Joel Dahl
    • Re: HEADSUP: urtw(4) to be committed soon, M. Warner Losh
  • Re: HEADSUP: urtw(4) to be committed soon, Kevin Lo
    • Re: HEADSUP: urtw(4) to be committed soon, Weongyo Jeong
• Dump device, Alexander Pyhalov
• NTFS in GENERIC: opt-in or opt-out?, Maxim Sobolev
  • Re: NTFS in GENERIC: opt-in or opt-out?, Erich Dollansky
    • Re: NTFS in GENERIC: opt-in or opt-out?, Maxim Sobolev
      • Re: NTFS in GENERIC: opt-in or opt-out?, Marian Hettwer
      • Re: NTFS in GENERIC: opt-in or opt-out?, Scot Hetzel
      • Re: NTFS in GENERIC: opt-in or opt-out?, Poul-Henning Kamp
      • Re: NTFS in GENERIC: opt-in or opt-out?, Pegasus Mc Cleaft
      • Re: NTFS in GENERIC: opt-in or opt-out?, Erich Dollansky
  • Re: NTFS in GENERIC: opt-in or opt-out?, Luigi Rizzo
    • Re: NTFS in GENERIC: opt-in or opt-out?, Maxim Sobolev
      • Re: NTFS in GENERIC: opt-in or opt-out?, Luigi Rizzo
    • Re: NTFS in GENERIC: opt-in or opt-out?, Robert Watson
      • Re: NTFS in GENERIC: opt-in or opt-out?, Stefan Ehmann
    • Re: NTFS in GENERIC: opt-in or opt-out?, Volodymyr Kostyrko
• arp_proxy: ignoring request, Randy Bush
  • RE: arp_proxy: ignoring request, Li, Qing
    • Re: arp_proxy: ignoring request, Randy Bush
• Kernel traps, Oliver Roeschke
  • Re: Kernel traps, Garrett Cooper
  • Re: Kernel traps, Olivier SMEDTS
• problem with nss_ldap, Hartmut.Brandt
  • Re: problem with nss_ldap, Harti Brandt
• promise sata150 tx4 gone, Rong-en Fan
• ad0: setting up DMA failed / FAILURE - load data ?, Rong-en Fan
• periodic(8) daily should backup bsdlabel(8) / fdisk(8) disk labels, Alexander Best
  • Re: periodic(8) daily should backup bsdlabel(8) / fdisk(8) disk labels, Miroslav Lachman
    • Re: periodic(8) daily should backup bsdlabel(8) / fdisk(8) disk labels, Yoshihiro Ota
  • Re: periodic(8) daily should backup bsdlabel(8) / fdisk(8) disk labels, Maxim Konovalov
    • Re: periodic(8) daily should backup bsdlabel(8) / fdisk(8) disk labels, Maxim Konovalov
• fdisk: Class not found, Alexander Best
  • Re: fdisk: Class not found, Christoph Mallon
    • Re: fdisk: Class not found, Alexander Best
  • Re: fdisk: Class not found, Bruce Cran
• USB2 + ucom + UHCI: still not happy, Poul-Henning Kamp
  • Re: USB2 + ucom + UHCI: still not happy, Hans Petter Selasky
    • Re: USB2 + ucom + UHCI: still not happy, Poul-Henning Kamp
      • Re: USB2 + ucom + UHCI: still not happy, Hans Petter Selasky
      • Re: USB2 + ucom + UHCI: still not happy, Andrew Thompson
      • Re: USB2 + ucom + UHCI: still not happy, Hans Petter Selasky
      • Re: USB2 + ucom + UHCI: still not happy, Andrew Thompson
      • Re: USB2 + ucom + UHCI: still not happy, Hans Petter Selasky
      • Re: USB2 + ucom + UHCI: still not happy, Hans Petter Selasky
• linux compatibility module build problems.., Martin Baumann
  • Re: linux compatibility module build problems.., Paul B. Mahol
    • Re: linux compatibility module build problems.., Martin Baumann
      • Re: linux compatibility module build problems.., Paul B. Mahol
• make release problem?, Dimitry Andric
  • Re: make release problem?, Eric L. Chen
    • Re: make release problem?, Dimitry Andric
• Re: Network slowdown on lo0 introduced with svn186119/186121, Christian Gusenbauer
• Multiple Routing Tables (FIB) + IPFW problem as (I?) expected, Eduardo Meyer
  • Re: Multiple Routing Tables (FIB) + IPFW problem as (I?) expected, Julian Elischer
    • Re: Multiple Routing Tables (FIB) + IPFW problem as (I?) expected, Eduardo Meyer
• gmirror regression from 7.1 to current? (was: Re: GEOM and moving to CURRENT from 7.1), Ben Kaduk
• SATA DMA errors on second ICH10 bus, Dylan Alex Simon
  • Re: SATA DMA errors on second ICH10 bus, Dylan Alex Simon
  • Re: SATA DMA errors on second ICH10 bus, Nenhum_de_Nos
    • Re: SATA DMA errors on second ICH10 bus, Josh Carroll
      • Re: SATA DMA errors on second ICH10 bus, Dylan Alex Simon
      • Re: SATA DMA errors on second ICH10 bus, Oliver Fromme
      • Re: SATA DMA errors on second ICH10 bus, Dylan Alex Simon
      • Re: SATA DMA errors on second ICH10 bus, Christoph Mallon
      • Re: SATA DMA errors on second ICH10 bus, Dylan Alex Simon
• Re: if_le unit number change?, John Baldwin
• Re: lockup booting 8.0-CURRENT-200811 snap image, John Baldwin
  • Re: lockup booting 8.0-CURRENT-200811 snap image, Phil Oleson
  • Re: lockup booting 8.0-CURRENT-200811 snap image, Tor Egge
    • Re: lockup booting 8.0-CURRENT-200811 snap image, John Baldwin
      • Re: lockup booting 8.0-CURRENT-200811 snap image, Phil Oleson
• age link problem., kama
  • Re: age link problem., Pyun YongHyeon
  • Re: age link problem., Bjorn Hellqvist
• Wifi Link 5100 driver ?, Hugo Silva
• Re: [Lcdproc] LCDProc CVS + PicoLCD on FreeBSD, Andre Guibert de Bruet
  • RE: [Lcdproc] LCDProc CVS + PicoLCD on FreeBSD, Gary R. Van Sickle
    • Re: [Lcdproc] LCDProc CVS + PicoLCD on FreeBSD, Andre Guibert de Bruet
      • Re: [Lcdproc] LCDProc CVS + PicoLCD on FreeBSD, Poul-Henning Kamp
      • Re: [Lcdproc] LCDProc CVS + PicoLCD on FreeBSD, Andre Guibert de Bruet
      • Re: [Lcdproc] LCDProc CVS + PicoLCD on FreeBSD, Poul-Henning Kamp
      • Re: [Lcdproc] LCDProc CVS + PicoLCD on FreeBSD, Andre Guibert de Bruet
      • Re: [Lcdproc] LCDProc CVS + PicoLCD on FreeBSD, Hans Petter Selasky
      • RE: [Lcdproc] LCDProc CVS + PicoLCD on FreeBSD, Gary R. Van Sickle
      • Re: [Lcdproc] LCDProc CVS + PicoLCD on FreeBSD, Andre Guibert de Bruet
• Bacula: VERY SLOW on SAME host, Larry Rosenman
  • Re: Bacula: VERY SLOW on SAME host, Kip Macy
    • RE: Bacula: VERY SLOW on SAME host, Li, Qing
      • Message not available
      • RE: Bacula: VERY SLOW on SAME host, Larry Rosenman
      • RE: Bacula: VERY SLOW on SAME host, Li, Qing
      • RE: Bacula: VERY SLOW on SAME host, Li, Qing
      • RE: Bacula: VERY SLOW on SAME host, Larry Rosenman
• Fw: nv-pv2 (Was: I give up), Conrad J. Sabatier
  • Re: nv-pv2 (Was: I give up), Conrad J. Sabatier
    • Re: nv-pv2 (Was: I give up), Søren Schmidt
      • Re: nv-pv2 (Was: I give up), Conrad J. Sabatier
• Re: Request for testers: Option 3G cards, also Sierra, Huawei and Novatel, Mike Tancsa
• Re: freebsd-current Digest, Vol 277, Issue 6, akess
• WITNESS: spin lock %s not in order list, pluknet
• INET6 tcp md5 signature, Guli
  • Re: INET6 tcp md5 signature, Bjoern A. Zeeb
• _rw_wlock_hard: recursing but non-recursive rw radix node head @ /usr/src/sys/net/route.c:831, Yuriy Tsibizov
  • Re: _rw_wlock_hard: recursing but non-recursive rw radix node head @ /usr/src/sys/net/route.c:831, Paul B. Mahol
    • RE: _rw_wlock_hard: recursing but non-recursive rw radix node head @ /usr/src/sys/net/route.c:831, Yuriy Tsibizov
      • Re: _rw_wlock_hard: recursing but non-recursive rw radix node head @ /usr/src/sys/net/route.c:831, Paul B. Mahol
      • Re: _rw_wlock_hard: recursing but non-recursive rw radix node head @ /usr/src/sys/net/route.c:831, Kip Macy
      • RE: _rw_wlock_hard: recursing but non-recursive rw radix node head @ /usr/src/sys/net/route.c:831, Yuriy Tsibizov
      • Re: _rw_wlock_hard: recursing but non-recursive rw radix node head @ /usr/src/sys/net/route.c:831, Paul B. Mahol
• Question about panic in brelse(), Christoph Mallon
  • Re: Question about panic in brelse(), Christoph Mallon
    • Re: Question about panic in brelse(), Christoph Mallon
• [PATCH]: set C dialect when compiling world, Roman Divacky
  • Re: [PATCH]: set C dialect when compiling world, Roman Divacky
    • Re: [PATCH]: set C dialect when compiling world, Dag-Erling Smørgrav
      • Re: [PATCH]: set C dialect when compiling world, Dag-Erling Smørgrav
      • Re: [PATCH]: set C dialect when compiling world, Roman Divacky
• fstab type "dp", Jeremie Le Hen
  • Re: fstab type "dp", Jeremie Le Hen
  • Re: fstab type "dp", Kostik Belousov
    • Re: fstab type "dp", Jeremie Le Hen
      • Re: fstab type "dp", Max Laier
      • Re: fstab type "dp", Gavin Atkinson
  • Re: fstab type "dp", Doug Barton
• WITH_SSP in src.conf(5) breaks the build, Jeremie Le Hen
• About bwi, Alex Keda
  • Re: About bwi, Alex Keda
    • Re: About bwi, Sam Leffler
      • Re: About bwi, Alex Keda
      • Re: About bwi, Paul B. Mahol
      • Re: About bwi, Alex Keda
      • Re: About bwi, Paul B. Mahol
• HEADS UP: imminent TCP ABC commit, Lawrence Stewart
• Warnings when insert USB flash, Alex Keda
  • Re: Warnings when insert USB flash, Hans Petter Selasky
• testing for 'sysconf' interface, n0g0013
• hints on setting up usb cdma modem?, Rohit Tripathi
  • Re: hints on setting up usb cdma modem?, Andrew Thompson
  • Re: hints on setting up usb cdma modem?, Eygene Ryabinkin
    • Re: hints on setting up usb cdma modem?, Hans Petter Selasky
    • Re: hints on setting up usb cdma modem?, Nick Hibma
    • Re: hints on setting up usb cdma modem?, Rohit Tripathi
• [RFC]: flex/lex update, Roman Divacky
  • Re: [RFC]: flex/lex update, Stanislav Sedov
    • Re: [RFC]: flex/lex update, Garrett Cooper
      • Re: [RFC]: flex/lex update, Stanislav Sedov
    • Re: [RFC]: flex/lex update, Xin LI
      • Re: [RFC]: flex/lex update, Stanislav Sedov
    • Re: [RFC]: flex/lex update, Thomas Dickey
  • Re: [RFC]: flex/lex update, Ulf Lilleengen
• FreeBSD panics with 64GiB of RAM, Attila Nagy
  • Re: FreeBSD panics with 64GiB of RAM, Marius Nünnerich
    • Re: FreeBSD panics with 64GiB of RAM, Attila Nagy
  • Re: FreeBSD panics with 64GiB of RAM, Dimitry Andric
    • Re: FreeBSD panics with 64GiB of RAM, Maxim Sobolev
      • Re: FreeBSD panics with 64GiB of RAM, Attila Nagy
      • Re: FreeBSD panics with 64GiB of RAM, Gavin Atkinson
      • Re: FreeBSD panics with 64GiB of RAM, Garrett Cooper
      • Re: FreeBSD panics with 64GiB of RAM, Attila Nagy
      • Re: FreeBSD panics with 64GiB of RAM, Attila Nagy
      • Re: FreeBSD panics with 64GiB of RAM, Attila Nagy
  • <Possible follow-ups>
  • Re: FreeBSD panics with 64GiB of RAM, Alexander Best
    • Re: FreeBSD panics with 64GiB of RAM, Artem Kuchin
    • Re: FreeBSD panics with 64GiB of RAM, Oliver Fromme
• ext3fs, raoul
  • Re: ext3fs, Ivan Voras
  • Re: ext3fs, pluknet
  • Re: ext3fs, Bruce M. Simpson
  • <Possible follow-ups>
  • Re: ext3fs, raoul
  • Re: ext3fs, raoul
• usb2: kernel panic with an USB floppy drive, WATANABE Kazuhiro
  • Re: usb2: kernel panic with an USB floppy drive, Hans Petter Selasky
    • Re: usb2: kernel panic with an USB floppy drive, WATANABE Kazuhiro
• GEOM and moving to CURRENT from 7.1, George Neville-Neil
  • Re: GEOM and moving to CURRENT from 7.1, Wes Morgan
    • Re: GEOM and moving to CURRENT from 7.1, Martin
    • Re: GEOM and moving to CURRENT from 7.1, Randy Bush
      • Re: GEOM and moving to CURRENT from 7.1, Ben Kaduk
      • Re: GEOM and moving to CURRENT from 7.1, Ben Kaduk
      • Re: GEOM and moving to CURRENT from 7.1, Ben Kaduk
      • Re: GEOM and moving to CURRENT from 7.1, Luiz Otavio O Souza
      • Re: GEOM and moving to CURRENT from 7.1, Marcel Moolenaar
      • Re: GEOM and moving to CURRENT from 7.1, Dimitry Andric
      • Re: GEOM and moving to CURRENT from 7.1, Dimitry Andric
      • Re: GEOM and moving to CURRENT from 7.1, Marcel Moolenaar
      • Re: GEOM and moving to CURRENT from 7.1, Luiz Otavio O Souza
      • Re: GEOM and moving to CURRENT from 7.1, Dimitry Andric
      • Re: GEOM and moving to CURRENT from 7.1, Arnar Mar Sig
      • Re: GEOM and moving to CURRENT from 7.1, Marcel Moolenaar
      • Re: GEOM and moving to CURRENT from 7.1, Dimitry Andric
      • Re: GEOM and moving to CURRENT from 7.1, Marcel Moolenaar
      • Re: GEOM and moving to CURRENT from 7.1, Dimitry Andric
      • Re: GEOM and moving to CURRENT from 7.1, Marcel Moolenaar
      • Re: GEOM and moving to CURRENT from 7.1, Wes Morgan
      • Re: GEOM and moving to CURRENT from 7.1, Dimitry Andric
      • Re: GEOM and moving to CURRENT from 7.1, Dimitry Andric
      • Re: GEOM and moving to CURRENT from 7.1, Randy Bush
      • Re: GEOM and moving to CURRENT from 7.1, Randy Bush
      • Re: GEOM and moving to CURRENT from 7.1, Marcel Moolenaar
    • Re: GEOM and moving to CURRENT from 7.1, Dimitry Andric
      • Re: GEOM and moving to CURRENT from 7.1, Dimitry Andric
  • Re: GEOM and moving to CURRENT from 7.1, Robert Watson
• Options handler for userspace programs, Andrea Di Pasquale
• USB2 & umass problem, Pegasus Mc Cleaft
  • Re: USB2 & umass problem, Hans Petter Selasky
• Problem with USB mass storage, Alex Keda
  • Re: Problem with USB mass storage, Hans Petter Selasky
    • Re: Problem with USB mass storage, Alex Keda
      • Re: Problem with USB mass storage, Alex Keda
      • Re: Problem with USB mass storage, Boris Samorodov
  • <Possible follow-ups>
  • Re: Problem with USB mass storage, Michel Talon
• changes after kernel update, Robert Huff
• quagga-0.99.11_1 is marked as broken: does not build., Randy Bush
  • Re: quagga-0.99.11_1 is marked as broken: does not build., Peter Jeremy
    • Re: quagga-0.99.11_1 is marked as broken: does not build., Michael Proto
  • Re: quagga-0.99.11_1 is marked as broken: does not build., Eygene Ryabinkin
    • Re: quagga-0.99.11_1 is marked as broken: does not build., Sergey Matveychuk
      • Re: quagga-0.99.11_1 is marked as broken: does not build., Mark Linimon
      • Re: quagga-0.99.11_1 is marked as broken: does not build., Erwin Lansing
      • Re: quagga-0.99.11_1 is marked as broken: does not build., Sergey Matveychuk
      • Re: quagga-0.99.11_1 is marked as broken: does not build., Sergey Matveychuk
• USB wiki page, Hans Petter Selasky
• Re: rc.d/mountd: confusing message (and behavior?), Garrett Cooper
  • Re: rc.d/mountd: confusing message (and behavior?), Garrett Cooper
• moving to a newer version of binutils, Alexander Best
  • <Possible follow-ups>
  • Re: moving to a newer version of binutils, Pedro F. Giffuni
    • Re: moving to a newer version of binutils, Alexander Best
• Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Pedro F. Giffuni
  • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Roman Divacky
    • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Pedro F. Giffuni
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Roman Divacky
  • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Peter Jeremy
    • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), O. Hartmann
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Pedro F. Giffuni
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Stephen Montgomery-Smith
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Eitan Adler
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Garrett Cooper
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Peter Ross
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Yocto
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Alexander Churanov
      • Why LLVM may be a step forward, Bruce M. Simpson
      • Re: Why LLVM may be a step forward, Christoph Mallon
      • Re: Why LLVM may be a step forward, Roman Divacky
      • Re: Why LLVM may be a step forward, Christoph Mallon
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Pedro F. Giffuni
    • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Robert Huff
    • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Pedro F. Giffuni
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Doug Barton
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Tim Kientzle
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Peter Ross
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Vincent Hoffman
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Peter Ross
  • Re: Alternatives to gcc, Dag-Erling Smørgrav
  • <Possible follow-ups>
  • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Alex Kozlov
  • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Michel Talon
    • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Alexander Churanov
    • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Stephen Montgomery-Smith
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Eitan Adler
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Kevin Oberman
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Stephen Montgomery-Smith
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Eitan Adler
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Brooks Davis
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Maxim Sobolev
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Pegasus Mc Cleaft
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Maxim Sobolev
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Adrian Chadd
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Maxim Sobolev
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Roman Divacky
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Michel Talon
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Dimitry Andric
      • Message not available
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Michel Talon
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Roman Divacky
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Jung-uk Kim
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Roman Divacky
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?), Lesly Bien-Aimé
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?), Roman Divacky
      • Re: Alternatives to gcc, Dag-Erling Smørgrav
      • Re: Alternatives to gcc, Garance A Drosihn
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?), Robert Huff
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?), pluknet
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Doug Barton
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Christoph Mallon
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Pegasus Mc Cleaft
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Roman Divacky
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Steve Kargl
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Roman Divacky
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Garrett Cooper
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will itbecome standard compiler?), Pegasus Mc Cleaft
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), O. Hartmann
  • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Sabeeh Baig
    • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Roman Divacky
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Dimitry Andric
      • Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), FuLLBLaSTstorm
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standardcompiler?), Pegasus Mc Cleaft
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standardcompiler?), Roman Divacky
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standardcompiler?), Christoph Mallon
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standardcompiler?), Roman Divacky
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standardcompiler?), Christoph Mallon
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standardcompiler?), Eygene Ryabinkin
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standardcompiler?), Sean C. Farley
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standardcompiler?), Tim Kientzle
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Christoph Mallon
      • Re: Alternatives to gcc, Dag-Erling Smørgrav
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Maxim Sobolev
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Garrett Cooper
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Anton Shterenlikht
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), O. Hartmann
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Christoph Mallon
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Pegasus Mc Cleaft
      • Re: gcc 4.3: when will it become standard compiler?, Pegasus Mc Cleaft
      • Re: gcc 4.3: when will it become standard compiler?, Garrett Cooper
      • Re: gcc 4.3: when will it become standard compiler?, Steve Kargl
      • Re: gcc 4.3: when will it become standard compiler?, Garrett Cooper
      • Re: gcc 4.3: when will it become standard compiler?, Anton Shterenlikht
      • Re: gcc 4.3: when will it become standard compiler?, Garrett Cooper
      • Re: gcc 4.3: when will it become standard compiler?, Pegasus Mc Cleaft
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Svein Skogen (listmail account)
      • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Christoph Mallon
  • Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?), Pedro F. Giffuni
    • Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?), Sean Cavanaugh
• Re: Unicode-based FreeBSD, Alexander Churanov
• X becomes unresponsive with nvidia and hardlocks with gdb (was Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics), Garrett Cooper
  • Re: X becomes unresponsive with nvidia and hardlocks with gdb (was Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics), Garrett Cooper
    • Re: X becomes unresponsive with nvidia and hardlocks with gdb (was Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics), O. Hartmann
      • Re: X becomes unresponsive with nvidia and hardlocks with gdb (was Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics), Christoph Mallon
      • Re: X becomes unresponsive with nvidia and hardlocks with gdb (was Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics), Christoph Mallon
      • X unresponsive with SCHED_ULE (was: Re: X becomes unresponsive with nvidia and hardlocks with gdb), Gavin Atkinson
      • Re: X becomes unresponsive with nvidia and hardlocks with gdb (was Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics), O. Hartmann
      • Re: X becomes unresponsive with nvidia and hardlocks with gdb (was Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics), Stefan Ehmann
      • Re: X becomes unresponsive with nvidia and hardlocks with gdb (was Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics), Garrett Cooper
• kernel doesn't boot when is built with ukbd/ums, pluknet
  • Re: kernel doesn't boot when is built with ukbd/ums, Alexey Shuvaev
    • Re: kernel doesn't boot when is built with ukbd/ums, Paul B. Mahol
      • Re: kernel doesn't boot when is built with ukbd/ums, pluknet
• 3G modem and USB, old & new, Poul-Henning Kamp
  • Re: 3G modem and USB, old & new, Hans Petter Selasky
    • Re: 3G modem and USB, old & new, Poul-Henning Kamp
      • Re: 3G modem and USB, old & new, Hans Petter Selasky
      • Re: 3G modem and USB, old & new, Poul-Henning Kamp
      • Re: 3G modem and USB, old & new, Hans Petter Selasky
  • Re: 3G modem and USB, old & new, Nick Hibma
    • Re: 3G modem and USB, old & new, Poul-Henning Kamp
      • Re: 3G modem and USB, old & new, Nick Hibma
      • Re: 3G modem and USB, old & new, Poul-Henning Kamp
• Recent changes to pseudofs causing panics -- leaking a vnode lock?, Richard Todd
  • Re: Recent changes to pseudofs causing panics -- leaking a vnode lock?, Joe Marcus Clarke
    • Re: Recent changes to pseudofs causing panics -- leaking a vnode lock?, Richard Todd
    • Re: Recent changes to pseudofs causing panics -- leaking a vnode lock?, Garrett Cooper
      • Re: Recent changes to pseudofs causing panics -- leaking a vnode lock?, Joe Marcus Clarke
• fix tools/tools/usb/print-usb-if-vids.sh, Alexander Best
  • Re: fix tools/tools/usb/print-usb-if-vids.sh, Hans Petter Selasky
  • Re: fix tools/tools/usb/print-usb-if-vids.sh, David O'Brien
• gcc 4.3: when will it become standard compiler?, O. Hartmann
  • Re: gcc 4.3: when will it become standard compiler?, Ollivier Robert
    • Re: gcc 4.3: when will it become standard compiler?, Andrew Reilly
      • Re: gcc 4.3: when will it become standard compiler?, Christoph Mallon
      • Re: gcc 4.3: when will it become standard compiler?, Pegasus Mc Cleaft
      • Re: gcc 4.3: when will it become standard compiler?, Roman Divacky
      • Re: gcc 4.3: when will it become standard compiler?, Roman Divacky
      • Re: gcc 4.3: when will it become standard compiler?, Christoph Mallon
      • Re: gcc 4.3: when will it become standard compiler?, Roman Divacky
      • Re: gcc 4.3: when will it become standard compiler?, B. Estrade
      • Re: gcc 4.3: when will it become standard compiler?, Christoph Mallon
      • Re: gcc 4.3: when will it become standard compiler?, Roman Divacky
      • Re: gcc 4.3: when will it become standard compiler?, Christoph Mallon
      • Re: gcc 4.3: when will it become standard compiler?, Roman Divacky
      • Re: gcc 4.3: when will it become standard compiler?, Christoph Mallon
      • Re: gcc 4.3: when will it become standard compiler?, Roman Divacky
      • Re: gcc 4.3: when will it become standard compiler?, Alexander Churanov
      • Re: gcc 4.3: when will it become standard compiler?, Roman Divacky
      • Re: gcc 4.3: when will it become standard compiler?, Alexander Churanov
      • Re: gcc 4.3: when will it become standard compiler?, Roman Divacky
      • Re: gcc 4.3: when will it become standard compiler?, Alexander Churanov
      • Re: gcc 4.3: when will it become standard compiler?, Christoph Mallon
      • Re: gcc 4.3: when will it become standard compiler?, Christoph Mallon
      • Re: gcc 4.3: when will it become standard compiler?, Carlos A. M. dos Santos
    • Re: gcc 4.3: when will it become standard compiler?, Roman Divacky
      • Re: gcc 4.3: when will it become standard compiler?, Jiawei Ye
      • Re: gcc 4.3: when will it become standard compiler?, Roman Divacky
  • Re: gcc 4.3: when will it become standard compiler?, Steve Kargl
    • Re: gcc 4.3: when will it become standard compiler?, Ollivier Robert
      • Re: gcc 4.3: when will it become standard compiler?, Christoph Mallon
      • Re: gcc 4.3: when will it become standard compiler?, Steve Kargl
  • Re: gcc 4.3: when will it become standard compiler?, Christoph Mallon
    • Re: gcc 4.3: when will it become standard compiler?, Svein Skogen (List Mail Account)
      • Re: gcc 4.3: when will it become standard compiler?, Garrett Cooper
      • Re: gcc 4.3: when will it become standard compiler?, Doug Barton
      • Re: gcc 4.3: when will it become standard compiler?, Eygene Ryabinkin
      • Re: gcc 4.3: when will it become standard compiler?, Doug Barton
      • Re: gcc 4.3: when will it become standard compiler?, David O'Brien
      • Re: gcc 4.3: when will it become standard compiler?, Pegasus Mc Cleaft
• reduce directories in sys/modules ?, Luigi Rizzo
  • Re: reduce directories in sys/modules ?, Julian Elischer
    • Re: reduce directories in sys/modules ?, Luigi Rizzo
  • Re: reduce directories in sys/modules ?, Sam Leffler
    • Re: reduce directories in sys/modules ?, Luigi Rizzo
• possibility of a "severe flaw in the logic of FreeBSD's kernel handling multiple host bridges ...", Manfred_Knick
  • Re: possibility of a "severe flaw in the logic of FreeBSD's kernel handling multiple host bridges ...", Robert Noland
    • Re: possibility of a "severe flaw in the logic of FreeBSD's kernel handling multiple host bridges ...", Manfred_Knick
• Adding a new kernel module?, Barney Cordoba
  • Re: Adding a new kernel module?, Gavin Atkinson
  • Re: Adding a new kernel module?, Szilveszter Adam
• patch to fix burncd bug, Alexander Best
  • Re: patch to fix burncd bug, Michael Proto
    • Re: patch to fix burncd bug, George Hartzell
      • Re: patch to fix burncd bug, Alexander Best
      • Re: patch to fix burncd bug, Jaakko Heinonen
      • Re: patch to fix burncd bug, George Hartzell
      • Re: patch to fix burncd bug, George Hartzell
  • Re: patch to fix burncd bug, Giorgos Keramidas
    • Re: patch to fix burncd bug, Carlos A. M. dos Santos
      • Re: patch to fix burncd bug, Alexander Best
  • Re: patch to fix burncd bug, David O'Brien
• panic: initiate_write_inodeblock_ufs2: already started, Ben Kaduk
• Bug or unwanted behaviour in echo ?, Damien Fleuriot
  • Re: Bug or unwanted behaviour in echo ?, Jelte Jansen
  • Re: Bug or unwanted behaviour in echo ?, David Wolfskill
  • Re: Bug or unwanted behaviour in echo ?, Ed Schouten
• mouse cursor corrupts chars under syscons, Alexander Best
  • Re: mouse cursor corrupts chars under syscons, Ed Schouten
  • Re: mouse cursor corrupts chars under syscons, Christoph Mallon
    • Re: mouse cursor corrupts chars under syscons, Alexander Best
      • Re: mouse cursor corrupts chars under syscons, Christoph Mallon
      • Re: mouse cursor corrupts chars under syscons, Christoph Mallon
• X becomes unresponsive with nvidia / xscreensaver and desktop panics, Garrett Cooper
  • Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics, Roman Divacky
    • Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics, Garrett Cooper
      • Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics, Roman Divacky
      • Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics, O. Hartmann
      • Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics, Andrew Reilly
      • Message not available
      • Fwd: X becomes unresponsive with nvidia / xscreensaver and desktop panics, Garrett Cooper
      • Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics, Roman Divacky
      • Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics, Garrett Cooper
  • Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics, Sam Leffler
  • Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics, Doug Barton
    • Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics, Garrett Cooper
      • Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics, Doug Barton
      • Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics, Garrett Cooper
• Extattr portability?, Tim Kientzle
  • bsdtar fan, Bruce M. Simpson
    • Re: bsdtar fan, Marius Nünnerich
      • Re: bsdtar fan, Olivier SMEDTS
      • Re: bsdtar fan, Christian Weisgerber
  • Re: Extattr portability?, Robert Watson
    • Re: Extattr portability?, Dylan Cochran
      • Re: Extattr portability?, Tim Kientzle
      • Re: Extattr portability?, a134qaed
      • Re: Extattr portability?, Tim Kientzle
      • Re: Extattr portability?, Robert Watson
• Best torrent client/server available for FreeBSD?, joe mcguckin
  • Re: Best torrent client/server available for FreeBSD?, Garrett Cooper
  • Re: Best torrent client/server available for FreeBSD?, David N
    • Re: Best torrent client/server available for FreeBSD?, Lucius Windschuh
  • Re: Best torrent client/server available for FreeBSD?, Christof Schulze
    • Re: Best torrent client/server available for FreeBSD?, Robert Noland
  • Re: Best torrent client/server available for FreeBSD?, Ed Schouten
  • Re: Best torrent client/server available for FreeBSD?, Stefan Lambrev
  • Re: Best torrent client/server available for FreeBSD?, Alexander Churanov
• msk Marvell Yukon 88E8038 hangs, Kim Culhan
  • Re: msk Marvell Yukon 88E8038 hangs, Pyun YongHyeon
    • Re: msk Marvell Yukon 88E8038 hangs, Kim Culhan
      • Re: msk Marvell Yukon 88E8038 hangs, Pyun YongHyeon
      • Re: msk Marvell Yukon 88E8038 hangs, Kim Culhan
      • Re: msk Marvell Yukon 88E8038 hangs, Pyun YongHyeon
      • Re: msk Marvell Yukon 88E8038 hangs, Kim Culhan
      • Re: msk Marvell Yukon 88E8038 hangs, Pyun YongHyeon
      • Re: msk Marvell Yukon 88E8038 hangs, Kim Culhan
      • Re: msk Marvell Yukon 88E8038 hangs, Pyun YongHyeon
      • Re: msk Marvell Yukon 88E8038 hangs, Kim Culhan
      • Re: msk Marvell Yukon 88E8038 hangs, Pyun YongHyeon
• Re: ZFS gets stuck, Peter Schuller
• mount_nfs is broken, Steve Kargl
  • Re: mount_nfs is broken, Craig Rodrigues
    • Re: mount_nfs is broken, Steve Kargl
      • Re: mount_nfs is broken, Steve Kargl
      • Re: mount_nfs is broken, Steve Kargl
• pxeboot does not work on Sun X4540, Attila Nagy
  • Re: pxeboot does not work on Sun X4540, Attila Nagy
    • Re: pxeboot does not work on Sun X4540, Danny Braniss
      • Re: pxeboot does not work on Sun X4540, Attila Nagy
• ZFS send core, Guido Falsi
  • Re: ZFS send core, Guido Falsi
• ZFS boot, Alexandre Biancalana
  • Re: ZFS boot, Alexandre Biancalana
    • Re: ZFS boot, Olivier SMEDTS
    • Re: ZFS boot, Hans Petter Selasky
• Problem with usbconfig and powerstate, Alexander Best
  • Re: Problem with usbconfig and powerstate, Hans Petter Selasky
    • Re: Problem with usbconfig and powerstate, Hans Petter Selasky
• Re: need conf/kern.post.mk review, Bjoern A. Zeeb
• Re: RFC: ELF branding. looking to a '.note.ABI-tag' section, giffunip
• Re: Labeling disks, Artis Caune
• snd_hda(4): getting line-in to work, Garrett Cooper
  • Re: snd_hda(4): getting line-in to work, Alexander Motin
    • Re: snd_hda(4): getting line-in to work, Garrett Cooper
      • Re: snd_hda(4): getting line-in to work, Alexander Motin
      • Message not available
      • Re: snd_hda(4): getting line-in to work, Garrett Cooper
      • Re: snd_hda(4): getting line-in to work, Alexander Motin
      • Re: snd_hda(4): getting line-in to work, Garrett Cooper
      • Re: snd_hda(4): getting line-in to work, Alexander Motin
      • Re: snd_hda(4): getting line-in to work, Garrett Cooper
• boot hangs with discrete graphics set in BIOS, Ganbold
• RFC: ELF branding. looking to a ".note.ABI-tag" section, Chagin Dmitry
  • <Possible follow-ups>
  • Re: RFC: ELF branding. looking to a ".note.ABI-tag" section, Pedro F. Giffuni
    • Re: RFC: ELF branding. looking to a ".note.ABI-tag" section, Chagin Dmitry
  • Re: RFC: ELF branding. looking to a ".note.ABI-tag" section, Pedro F. Giffuni
• FreeBSD 8: fails booting from slice ad8s1a, O. Hartmann
  • Re: FreeBSD 8: fails booting from slice ad8s1a, Marcel Moolenaar
    • Re: FreeBSD 8: fails booting from slice ad8s1a, Mark Atkinson
      • Re: FreeBSD 8: fails booting from slice ad8s1a, Mark Atkinson
• [cfr] rc.shutdown patch, Bjoern A. Zeeb
• Re: hangup (livelock) - db> prompt in endless loop, Attilio Rao
  • Re: hangup (livelock) - db> prompt in endless loop, Alexey Shuvaev
• FreeBSD 8-Current AMD64: not compiling world, core dump with new kernel, O. Hartmann
  • RE: FreeBSD 8-Current AMD64: not compiling world, core dump with new kernel, Johan Hendriks
    • Re: FreeBSD 8-Current AMD64: not compiling world, core dump with new kernel, O. Hartmann
• 8.0-SNAPSHOT200812 reversed locks, Petr Holub
  • Re: 8.0-SNAPSHOT200812 reversed locks, John Baldwin
• Re: HEADSUP: arp-v2 has been committed, Garrett Cooper
  • <Possible follow-ups>
  • RE: HEADSUP: arp-v2 has been committed, Gerald Pfeifer
    • Re: HEADSUP: arp-v2 has been committed, Bruce Simpson
    • RE: HEADSUP: arp-v2 has been committed, Li, Qing
      • Re: HEADSUP: arp-v2 has been committed, Garrett Cooper
      • Re: HEADSUP: arp-v2 has been committed, Julian Elischer
      • Re: HEADSUP: arp-v2 has been committed, Garrett Cooper
• Re: gpart, Marcel Moolenaar
  • Re: gpart, Takahashi Yoshihiro
• apcupsd & usb2, Chris Ruiz
  • Re: apcupsd & usb2, Hans Petter Selasky
    • Re: apcupsd & usb2, Stanislav Sedov
    • Re: apcupsd & usb2, Chris Ruiz
      • Re: apcupsd & usb2, Hans Petter Selasky
• upcoming elfdump refactoring, Luigi Rizzo
  • Re: upcoming elfdump refactoring, Maxim Sobolev
    • Re: upcoming elfdump refactoring, Luigi Rizzo
      • Re: upcoming elfdump refactoring, Danny Braniss
    • Re: upcoming elfdump refactoring, Marcel Moolenaar
• panic in bundirty, Volker
  • Re: panic in bundirty, Martin Wilke
  • Re: panic in bundirty, Ben Kaduk
• panic related to ipv6 (afaik), Roman Divacky
  • Re: panic related to ipv6 (afaik), Ed Schouten
    • Re: panic related to ipv6 (afaik), Chris Ruiz
      • Re: panic related to ipv6 (afaik), Robert Watson
• kldload exec format error on amd64 freebsd-7.1-rc2, Christof Schulze
  • Re: kldload exec format error on amd64 freebsd-7.1-rc2, Stanislav Sedov
  • Re: kldload exec format error on amd64 freebsd-7.1-rc2, Christof Schulze
  • Message not available
    • Message not available
      • Re: kldload exec format error on amd64 freebsd-7.1-rc2, Christof Schulze
      • Re: kldload exec format error on amd64 freebsd-7.1-rc2, Barney Cordoba
      • Re: kldload exec format error on amd64 freebsd-7.1-rc2, Dag-Erling Smørgrav
      • Re: kldload exec format error on amd64 freebsd-7.1-rc2, Robert Watson
      • Re: kldload exec format error on amd64 freebsd-7.1-rc2, Barney Cordoba
• Re: Tracking the open USB2 issues?, Giorgos Keramidas
• Weird arrow key disappearing act with latest syscons, Garrett Cooper
  • Re: Weird arrow key disappearing act with latest syscons, Ed Schouten
    • Re: Weird arrow key disappearing act with latest syscons, Ed Schouten
    • Re: Weird arrow key disappearing act with latest syscons, Garrett Cooper
• Can not build r186708 -CURRENT, Alexey Ivanov
  • Re: Can not build r186708 -CURRENT, Paul B. Mahol
  • Re: Can not build r186708 -CURRENT, Weongyo Jeong
  • Re: Can not build r186708 -CURRENT, Bjoern A. Zeeb
    • Re: Can not build r186708 -CURRENT, Paul B. Mahol
• CFT: altq support for pcn(4), Christian Brueffer
  • Re: CFT: altq support for pcn(4), Christian Brueffer
• kernel complaint about /dev/pts (maybe), Robert Huff
  • Re: kernel complaint about /dev/pts (maybe), Ed Schouten
  • Re: kernel complaint about /dev/pts (maybe), Jilles Tjoelker
• hosts on bridged wlan can not reliably see each other, Randy Bush
  • Re: hosts on bridged wlan can not reliably see each other, Sam Leffler
    • Re: hosts on bridged wlan can not reliably see each other, Randy Bush
      • Re: hosts on bridged wlan can not reliably see each other, Sam Leffler
      • Re: hosts on bridged wlan can not reliably see each other, Randy Bush
• panic on (hdd)load, Uwe Grohnwaldt
  • Re: panic on (hdd)load, Uwe Grohnwaldt
  • Re: panic on (hdd)load, Uwe Grohnwaldt
  • Re: panic on (hdd)load, Uwe Grohnwaldt
    • Re: panic on (hdd)load, Thomas Sparrevohn
      • Re: panic on (hdd)load, Hans Petter Selasky
      • Re: panic on (hdd)load, Uwe Grohnwaldt
      • Re: panic on (hdd)load, Thomas Sparrevohn
• Re: HEADSUP usb2 (usb4bsd) to become default in 2 weeks. [usb2 configuration], M. Warner Losh
  • hald and USB2, Pegasus Mc Cleaft
    • Re: hald and USB2, Joe Marcus Clarke
• Re: HEADSUP usb2 (usb4bsd) to become default in 2 weeks., M. Warner Losh
  • Re: HEADSUP usb2 (usb4bsd) to become default in 2 weeks., Alfred Perlstein
    • Re: HEADSUP usb2 (usb4bsd) to become default in 2 weeks., M. Warner Losh
      • Re: HEADSUP usb2 (usb4bsd) to become default in 2 weeks., Alfred Perlstein
  • <Possible follow-ups>
  • Re: HEADSUP usb2 (usb4bsd) to become default in 2 weeks., Renato Botelho
• New warning, what does it mean?, M. Warner Losh
  • Re: New warning, what does it mean?, David O'Brien
    • Re: New warning, what does it mean?, Marcel Moolenaar
  • Re: New warning, what does it mean?, Marcel Moolenaar
    • Re: New warning, what does it mean?, M. Warner Losh
      • Re: New warning, what does it mean?, Marcel Moolenaar
• Re: 8-current: linux_dist-gentoo-stage3 wonn't bootstrap, Arno J. Klaassen
• build -j3 not working anymore on Current, Johan Hendriks
  • Re: build -j3 not working anymore on Current, Gary Palmer
    • RE: build -j3 not working anymore on Current, Johan Hendriks
      • Re: build -j3 not working anymore on Current, Gary Palmer
      • RE: build -j3 not working anymore on Current, Johan Hendriks
      • RE: build -j3 not working anymore on Current, Johan Hendriks
      • Re: build -j3 not working anymore on Current, M. Warner Losh
  • Re: build -j3 not working anymore on Current, David O'Brien
    • RE: build -j3 not working anymore on Current, Johan Hendriks
      • Re: build -j3 not working anymore on Current, David O'Brien
• Re: gjournal is not automounted any more, David O'Brien
  • Re: gjournal is not automounted any more, Boris Samorodov
  • Re: gjournal is not automounted any more, M. Warner Losh
    • Re: gjournal is not automounted any more, David O'Brien
      • Re: gjournal is not automounted any more, M. Warner Losh
      • Re: gjournal is not automounted any more, David O'Brien
      • Re: gjournal is not automounted any more, M. Warner Losh
      • Re: gjournal is not automounted any more, Marcel Moolenaar
      • Re: gjournal is not automounted any more, M. Warner Losh
      • Re: gjournal is not automounted any more, Marcel Moolenaar
      • Re: gjournal is not automounted any more, M. Warner Losh
      • Re: gjournal is not automounted any more, Marcel Moolenaar
• Warning about uid values larger than 16-bit..., Ken Smith
• gstripe performance oddity, Joel Jacobson
  • Re: gstripe performance oddity, Maxim Sobolev
    • Re: gstripe performance oddity, Joel Jacobson
• RE: SCTP related issue with recent ARP changes?, Li, Qing
  • RE: SCTP related issue with recent ARP changes?, Li, Qing
    • Re: SCTP related issue with recent ARP changes?, Michael Tüxen
• RFC: new utility, kmodpatch, Luigi Rizzo
  • Re: RFC: new utility, kmodpatch, Alex Keda
  • Re: RFC: new utility, kmodpatch, Oliver Pinter
    • Re: RFC: new utility, kmodpatch, Ben Kaduk
      • Re: RFC: new utility, kmodpatch, Luigi Rizzo
      • Re: RFC: new utility, kmodpatch, Gary Jennejohn
  • Re: RFC: new utility, kmodpatch, Christoph Mallon
    • Re: RFC: new utility, kmodpatch, Christoph Mallon
  • Re: RFC: new utility, kmodpatch, M. Warner Losh
    • Re: RFC: new utility, kmodpatch, Luigi Rizzo
      • Re: RFC: new utility, kmodpatch, M. Warner Losh
      • Re: RFC: new utility, kmodpatch, Luigi Rizzo
      • Re: RFC: new utility, kmodpatch, M. Warner Losh
  • Re: RFC: new utility, kmodpatch, Alex Keda
    • Re: RFC: new utility, kmodpatch, Luigi Rizzo
  • Re: RFC: new utility, kmodpatch, dvg_lab
    • Re: RFC: new utility, kmodpatch, Max Laier
      • Re: RFC: new utility, kmodpatch, Vyacheslav Druzhinin
  • kldpatch updated (Re: RFC: new utility, kmodpatch), Luigi Rizzo
• LORs in recent -current, Philipp Ost
• VT100/xterm-support for syscons(4) committed to SVN, Ed Schouten
• Re: Call for axe(4) testers., Hans Petter Selasky
  • Re: Call for axe(4) testers., Norikatsu Shigemura
    • Re: Call for axe(4) testers., Hans Petter Selasky
      • Re: Call for axe(4) testers., Norikatsu Shigemura
      • Re: Call for axe(4) testers., Hans Petter Selasky
      • Re: Call for axe(4) testers., Norikatsu Shigemura
      • Re: Call for axe(4) testers., Norikatsu Shigemura
      • Re: Call for axe(4) testers., Hans Petter Selasky
• [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/sparc64, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on sparc64/sparc64, 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 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 i386/pc98, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [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 amd64/amd64, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
• Re: Changed names of logical disks on recent -CURRENT: part of logical disks not accessible now, Jos Backus
  • Re: Changed names of logical disks on recent -CURRENT: part of logical disks not accessible now, Marcel Moolenaar
    • Re: Changed names of logical disks on recent -CURRENT: part of logical disks not accessible now, Jos Backus
• Re: tar/libarchive gzip problem [was: portsnap corrupted], Tim Kientzle
  • Re: tar/libarchive gzip problem [was: portsnap corrupted], Tim Kientzle
    • Re: tar/libarchive gzip problem [was: portsnap corrupted], Simon L. Nielsen
      • Re: tar/libarchive gzip problem [was: portsnap corrupted], Max Laier

• Security
• UNIX
• Linux
• Coding
• Usenet

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

unix.derkeiler.com  > Mailing-Lists  > FreeBSD  > current  > 2009-01