freebsd-current

• Date Index

---

• zpool v28 and -current, Shawn Webb
  • Re: zpool v28 and -current, Anonymous
    • Re: zpool v28 and -current, Shawn Webb
• Can't dynamically load module uart on amd64-current, Marek Salwerowicz
• cpufreq not working as module on i386/amd64, Jia-Shiun Li
  • Re: cpufreq not working as module on i386/amd64, Alexander Best
• [WORKAROUND] www/seamonkey2 on CURRENT, Alexey Shuvaev
  • Re: [WORKAROUND] www/seamonkey2 on CURRENT, Daniel Eischen
    • Re: [WORKAROUND] www/seamonkey2 on CURRENT, Alexander Kabaev
      • Re: [WORKAROUND] www/seamonkey2 on CURRENT, Alexander Kabaev
      • Re: [WORKAROUND] www/seamonkey2 on CURRENT, Daniel Eischen
  • <Possible follow-ups>
  • Re: [WORKAROUND] www/seamonkey2 on CURRENT, Alexey Shuvaev
    • Re: [WORKAROUND] www/seamonkey2 on CURRENT, Daniel Eischen
    • Re: [WORKAROUND] www/seamonkey2 on CURRENT, Alexander Kabaev
• missing us.dvorakr.kbd, Neil Short
  • Re: missing us.dvorakr.kbd, Gary Jennejohn
    • Re: missing us.dvorakr.kbd, Ulrich Spörlein
• unbounded sleep on [fifoow] while open a named pipe: is it a feature?, Sergey Kandaurov
  • Re: unbounded sleep on [fifoow] while open a named pipe: is it a feature?, Kostik Belousov
  • Re: unbounded sleep on [fifoow] while open a named pipe: is it a feature?, Jilles Tjoelker
• [ath] ath_rate_sample changes; please test, Adrian Chadd
• FreeBSD Status Report - 4Q/2010, Daniel Gerzo
• [ath] AR9285 / AR2427 testers needed!, Adrian Chadd
• amd64 build fails within ESXi guest, Eric Crist
  • Re: amd64 build fails within ESXi guest, Matthew Fleming
• suspend with drm activated ?, David Demelier
• Cannot switch tty's after install xorg, gnome and gdm, LOL
  • Re: Cannot switch tty's after install xorg, gnome and gdm, David Demelier
  • Re: Cannot switch tty's after install xorg, gnome and gdm, Rob Farmer
    • Re: Cannot switch tty's after install xorg, gnome and gdm, Warren Block
      • Re: Cannot switch tty's after install xorg, gnome and gdm, Rob Farmer
      • Re: Cannot switch tty's after install xorg, gnome and gdm, LOL
• [ath] more updates; please test (especially if you're using an AR9280), Adrian Chadd
  • Re: [ath] more updates; please test (especially if you're using an AR9280), Adrian Chadd
  • Re: [ath] more updates; please test (especially if you're using an AR9280), Ian FREISLICH
    • Re: [ath] more updates; please test (especially if you're using an AR9280), Adrian Chadd
    • Re: [ath] more updates; please test (especially if you're using an AR9280), Ian FREISLICH
      • Re: [ath] more updates; please test (especially if you're using an AR9280), Adrian Chadd
• Request: AR9285 EEPROM dumps (was Re: More if_ath churn coming your way!), Adrian Chadd
  • Re: Request: AR9285 EEPROM dumps (was Re: More if_ath churn coming your way!), Dima Panov
    • Re: Request: AR9285 EEPROM dumps (was Re: More if_ath churn coming your way!), Adrian Chadd
• FreeBSD-current kernel can not be built, gnehzuil gnehzuil
  • Re: FreeBSD-current kernel can not be built, Adrian Chadd
    • Re: FreeBSD-current kernel can not be built, gnehzuil
• "broken pipe" error during building of port, Alexander Shikoff
  • <Possible follow-ups>
  • Re: "broken pipe" error during building of port, Alex Kozlov
    • Re: "broken pipe" error during building of port, Alexander Shikoff
• RFC vgrind in base (and buildworld), Ulrich Spörlein
  • Re: RFC vgrind in base (and buildworld), Alexander Kabaev
    • Re: RFC vgrind in base (and buildworld), Ulrich Spörlein
      • Re: RFC vgrind in base (and buildworld), Alexander Kabaev
    • Re: RFC vgrind in base (and buildworld), Marcel Moolenaar
      • Re: RFC vgrind in base (and buildworld), Alexander Kabaev
      • Re: RFC vgrind in base (and buildworld), Marcel Moolenaar
  • Re: RFC vgrind in base (and buildworld), Ulrich Spörlein
    • Re: RFC vgrind in base (and buildworld), Gary Jennejohn
      • Re: RFC vgrind in base (and buildworld), Steve Kargl
• More if_ath churn coming your way!, Adrian Chadd
  • Re: More if_ath churn coming your way!, Max Khon
    • Re: More if_ath churn coming your way!, Adrian Chadd
    • Re: More if_ath churn coming your way!, Maciej Milewski
  • Re: More if_ath churn coming your way!, Adrian Chadd
    • Re: More if_ath churn coming your way!, Dima Panov
      • Re: More if_ath churn coming your way!, Adrian Chadd
      • Re: More if_ath churn coming your way!, Dima Panov
      • Re: More if_ath churn coming your way!, Adrian Chadd
  • Re: More if_ath churn coming your way!, Ian FREISLICH
    • Re: More if_ath churn coming your way!, Adrian Chadd
    • Re: More if_ath churn coming your way!, Ian FREISLICH
      • Re: More if_ath churn coming your way!, Adrian Chadd
  • <Possible follow-ups>
  • Re: More if_ath churn coming your way!, b. f.
    • Re: More if_ath churn coming your way!, Adrian Chadd
      • Re: More if_ath churn coming your way!, b. f.
      • Re: More if_ath churn coming your way!, Adrian Chadd
• bsdbox example scripts, Adrian Chadd
• FreeBSD Installer Roadmap, Nathan Whitehorn
• Running linux ldconfig on tmpfs results in unkillable process, Beat Gätzi
  • Re: Running linux ldconfig on tmpfs results in unkillable process, Kostik Belousov
    • Re: Running linux ldconfig on tmpfs results in unkillable process, Beat Gätzi
      • Re: Running linux ldconfig on tmpfs results in unkillable process, Kostik Belousov
      • Re: Running linux ldconfig on tmpfs results in unkillable process, Beat Gätzi
      • Re: Running linux ldconfig on tmpfs results in unkillable process, Kostik Belousov
      • Re: Running linux ldconfig on tmpfs results in unkillable process, Beat Gätzi
• [RFC]: tautological compares in amd64 GENERIC, Roman Divacky
• uma_zalloc_arg: zone "256" with non-sleepable exclusive rw ifnet_rw @ /usr/src/sys/net/if.c:414, Sergey Kandaurov
  • Re: uma_zalloc_arg: zone "256" with non-sleepable exclusive rw ifnet_rw @ /usr/src/sys/net/if.c:414, John Baldwin
    • Re: uma_zalloc_arg: zone "256" with non-sleepable exclusive rw ifnet_rw @ /usr/src/sys/net/if.c:414, Sergey Kandaurov
      • Re: uma_zalloc_arg: zone "256" with non-sleepable exclusive rw ifnet_rw @ /usr/src/sys/net/if.c:414, John Baldwin
      • Re: uma_zalloc_arg: zone "256" with non-sleepable exclusive rw ifnet_rw @ /usr/src/sys/net/if.c:414, Sergey Kandaurov
      • Re: uma_zalloc_arg: zone "256" with non-sleepable exclusive rw ifnet_rw @ /usr/src/sys/net/if.c:414, John Baldwin
      • Re: uma_zalloc_arg: zone "256" with non-sleepable exclusive rw ifnet_rw @ /usr/src/sys/net/if.c:414, Sergey Kandaurov
• Re: Known LoR when taking bringing up bge(4) after system in multiuser?, Sergey Kandaurov
  • Re: Known LoR when taking bringing up bge(4) after system in multiuser?, Garrett Cooper
• fatal kernel trap (cpu 1): trap vector = 0x14 (Page Not Present), Anton Shterenlikht
  • Re: fatal kernel trap (cpu 1): trap vector = 0x14 (Page Not Present), Anton Shterenlikht
• FreeBSD 8.1 re0 shows half duplex, Martin Wilke
  • Message not available
    • Re: FreeBSD 8.1 re0 shows half duplex, Bjoern A. Zeeb
• Soekris net5501 - how to use hardware watchdog?, Marek Salwerowicz
  • Re: Soekris net5501 - how to use hardware watchdog?, Mike Tancsa
    • Re: [Soekris] Soekris net5501 - how to use hardware watchdog?, Mike Tancsa
      • Re: [Soekris] Soekris net5501 - how to use hardware watchdog?, Marek Salwerowicz
      • Re: [Soekris] Soekris net5501 - how to use hardware watchdog?, Mike Tancsa
      • Re: [Soekris] Soekris net5501 - how to use hardware watchdog?, Marek Salwerowicz
• cosmetic nit in mmc.c, Michael Butler
  • <Possible follow-ups>
  • Re: cosmetic nit in mmc.c, Alexander Motin
• TCP resident expert?, William Allen Simpson
  • Re: TCP resident expert?, Doug Barton
  • Re: TCP resident expert?, Robert Watson
• Soekris net5501-70 problem with loading ATA modules on FreeBSD-Current, Marek Salwerowicz
  • Re: Soekris net5501-70 problem with loading ATA modules on FreeBSD-Current, John Baldwin
  • <Possible follow-ups>
  • Re: Soekris net5501-70 problem with loading ATA modules on FreeBSD-Current, Alexander Motin
    • Re: Soekris net5501-70 problem with loading ATA modules onFreeBSD-Current, Marek Salwerowicz
      • Re: Soekris net5501-70 problem with loading ATA modules onFreeBSD-Current, Alexander Motin
      • Re: Soekris net5501-70 problem with loading ATA modulesonFreeBSD-Current, Marek Salwerowicz
      • Re: Soekris net5501-70 problem with loading ATA modulesonFreeBSD-Current, Alexander Motin
      • Re: Soekris net5501-70 problem with loading ATA modulesonFreeBSD-Current, Marek Salwerowicz
      • Re: Soekris net5501-70 problem with loading ATA modulesonFreeBSD-Current, Alexander Motin
• Fwd: HEADSUP: Call for FreeBSD Status Reports - 4Q/2010, Daniel Gerzo
• BSDInstall: merging to HEAD, Nathan Whitehorn
  • Re: BSDInstall: merging to HEAD, Marcel Moolenaar
    • Re: BSDInstall: merging to HEAD, Ade Lovett
      • Re: BSDInstall: merging to HEAD, Anton Shterenlikht
  • Re: BSDInstall: merging to HEAD, Gary Jennejohn
  • Re: BSDInstall: merging to HEAD, krad
    • Re: BSDInstall: merging to HEAD, Garrett Cooper
      • Re: BSDInstall: merging to HEAD, Nathan Whitehorn
  • Re: BSDInstall: merging to HEAD, Marius Nünnerich
  • Re: BSDInstall: merging to HEAD, David Demelier
    • Re: BSDInstall: merging to HEAD, Chuck Swiger
      • Re: BSDInstall: merging to HEAD, Olivier Smedts
      • Re: BSDInstall: merging to HEAD, Doug Barton
      • Re: BSDInstall: merging to HEAD, Nathan Whitehorn
      • Re: BSDInstall: merging to HEAD, Doug Barton
      • Re: BSDInstall: merging to HEAD, Nathan Whitehorn
      • Re: BSDInstall: merging to HEAD, Oliver Pinter
    • Re: BSDInstall: merging to HEAD, Garrett Cooper
      • Re: BSDInstall: merging to HEAD, Nathan Whitehorn
    • Re: BSDInstall: merging to HEAD, James R. Van Artsdalen
• HEADSUP: Realtime thread scheduling changed, John Baldwin
  • Re: HEADSUP: Realtime thread scheduling changed, Daniel Eischen
    • Re: HEADSUP: Realtime thread scheduling changed, John Baldwin
  • Re: HEADSUP: Realtime thread scheduling changed, Alexander Churanov
• Endless CAM messages with recent CURRENT, Rainer Hurling
  • Re: Endless CAM messages with recent CURRENT, Rainer Hurling
    • Re: Endless CAM messages with recent CURRENT, Hans Petter Selasky
      • Re: Endless CAM messages with recent CURRENT, Rainer Hurling
      • Re: Endless CAM messages with recent CURRENT, Hans Petter Selasky
      • Re: Endless CAM messages with recent CURRENT, Rainer Hurling
      • Re: Endless CAM messages with recent CURRENT, Hans Petter Selasky
      • Re: Endless CAM messages with recent CURRENT, Rainer Hurling
      • arp -nf list; work about 35 minutes, Andrey Smagin
• ale(4) causes panic after r217323, Aryeh Friedman
  • Re: ale(4) causes panic after r217323, Andrey V. Elsukov
• Profiling code execution on amd64?, Steve Kargl
  • Re: Profiling code execution on amd64?, Ryan Stone
    • Re: Profiling code execution on amd64?, Steve Kargl
      • Re: Profiling code execution on amd64?, George Neville-Neil
      • Re: Profiling code execution on amd64?, Steve Kargl
      • Re: Profiling code execution on amd64?, Garrett Cooper
      • Re: Profiling code execution on amd64?, Hans Ottevanger
      • Re: Profiling code execution on amd64?, Fabien Thomas
      • Re: Profiling code execution on amd64?, Steve Kargl
• unknown mtx_assert at /usr/src/sys/x86/x86/io_apic.c:161, Michael Jung
  • Re: unknown mtx_assert at /usr/src/sys/x86/x86/io_apic.c:161, John Baldwin
    • Re: unknown mtx_assert at /usr/src/sys/x86/x86/io_apic.c:161, Michael Jung
      • Re: unknown mtx_assert at /usr/src/sys/x86/x86/io_apic.c:161, Michael Jung
• Intel 10GBase-LR Ethernet card detected as 10GBase-SR, sthaug
  • Re: Intel 10GBase-LR Ethernet card detected as 10GBase-SR, sthaug
• R: ahci timeout, Barbara
• My ZFS v28 Testing Experience, Chris Forgeron
  • Re: My ZFS v28 Testing Experience, Pawel Jakub Dawidek
    • RE: My ZFS v28 Testing Experience, Chris Forgeron
      • RE: My ZFS v28 Testing Experience, Chris Forgeron
• [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
• if_ether.c (svn revision 217315) breakage on i386, Michael Butler
  • Re: if_ether.c (svn revision 217315) breakage on i386, Christian Peron
• [head tinderbox] failure on powerpc64/powerpc, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on powerpc64/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc64/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc64/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc64/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc64/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc64/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc64/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc64/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc64/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc64/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc64/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc64/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc64/powerpc, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on powerpc64/powerpc, Ulrich Spörlein
• [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 mips/mips, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on mips/mips, FreeBSD Tinderbox
  • [head tinderbox] failure on mips/mips, FreeBSD Tinderbox
  • [head tinderbox] failure on mips/mips, FreeBSD Tinderbox
  • [head tinderbox] failure on mips/mips, FreeBSD Tinderbox
  • [head tinderbox] failure on mips/mips, FreeBSD Tinderbox
  • [head tinderbox] failure on mips/mips, FreeBSD Tinderbox
  • [head tinderbox] failure on mips/mips, FreeBSD Tinderbox
  • [head tinderbox] failure on mips/mips, FreeBSD Tinderbox
  • [head tinderbox] failure on mips/mips, FreeBSD Tinderbox
  • [head tinderbox] failure on mips/mips, FreeBSD Tinderbox
  • [head tinderbox] failure on mips/mips, FreeBSD Tinderbox
• [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on amd64/amd64, Matthew Fleming
      • Re: [head tinderbox] failure on amd64/amd64, Mike Tancsa
      • Re: [head tinderbox] failure on amd64/amd64, Simon L. B. Nielsen
      • Re: [head tinderbox] failure on amd64/amd64, Peter Jeremy
      • Re: [head tinderbox] failure on amd64/amd64, Simon L. B. Nielsen
      • Re: [head tinderbox] failure on amd64/amd64, Giorgos Keramidas
  • [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 i386/i386, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
• [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
• [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
  • Re: [head tinderbox] failure on arm/arm, Matthew Fleming
    • Re: [head tinderbox] failure on arm/arm, Dimitry Andric
  • <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
• AHCI on ICH7, Anton Yuzhaninov
  • Re: AHCI on ICH7, Michael Butler
    • Re: AHCI on ICH7, Alexander Motin
      • Re: AHCI on ICH7, Michael Butler
  • <Possible follow-ups>
  • Re: AHCI on ICH7, Alexander Motin
• /sbin/init refuses to start with large physmem installed, Sergey Kandaurov
  • Re: /sbin/init refuses to start with large physmem installed, Sergey Kandaurov
• why panic(9) ?, David DEMELIER
  • Re: why panic(9) ?, Xin LI
    • Re: why panic(9) ?, C. P. Ghost
      • Re: why panic(9) ?, Boris Kochergin
      • Re: why panic(9) ?, C. P. Ghost
  • Re: why panic(9) ?, Chuck Swiger
    • Re: why panic(9) ?, David DEMELIER
      • Re: why panic(9) ?, Chuck Swiger
      • Re: why panic(9) ?, C. P. Ghost
      • Re: why panic(9) ?, Nils Holland
      • Re: why panic(9) ?, Erik
      • Re: why panic(9) ?, Matthew Seaman
      • Re: why panic(9) ?, Chris Brennan
      • Re: why panic(9) ?, Bruce Cran
      • Re: why panic(9) ?, Daniel Nebdal
      • Re: why panic(9) ?, Martin Sugioarto
      • Re: why panic(9) ?, Lars Engels
      • Re: why panic(9) ?, Martin Sugioarto
  • Re: why panic(9) ?, C. P. Ghost
  • Re: why panic(9) ?, Boris Kochergin
    • Re: why panic(9) ?, Lowell Gilbert
  • Re: why panic(9) ?, Greg Roberts
  • Re: why panic(9) ?, Garrett Cooper
    • Re: why panic(9) ?, David Demelier
      • Re: why panic(9) ?, Garrett Cooper
      • Re: why panic(9) ?, Anonymous
      • Re: why panic(9) ?, Doug Barton
      • Re: why panic(9) ?, Gary Jennejohn
• R: Recent mouse freeze problem with X, different window managers, any browser and flash., Barbara
  • <Possible follow-ups>
  • R: Recent mouse freeze problem with X, different window managers, any browser and flash., Barbara
    • Re: R: Recent mouse freeze problem with X, different window managers, any browser and flash., Ariff Abdullah
    • Re: R: Recent mouse freeze problem with X, different window managers, any browser and flash., eculp
      • Message not available
      • Re: R: Recent mouse freeze problem with X, different window managers, any browser and flash., Edwin L. Culp W.
      • Re: R: Recent mouse freeze problem with X, different window managers, any browser and flash., Gary Jennejohn
      • Re: R: Recent mouse freeze problem with X, different window managers, any browser and flash., eculp
      • Message not available
      • Message not available
      • Re: R: Recent mouse freeze problem with X, different window managers, any browser and flash., eculp
      • Re: R: Recent mouse freeze problem with X, different window managers, any browser and flash., Ariff Abdullah
      • Re: R: Recent mouse freeze problem with X, different window managers, any browser and flash., eculp
      • Re: R: Recent mouse freeze problem with X, different window managers, any browser and flash., Jung-uk Kim
      • Re: R: Recent mouse freeze problem with X, different window managers, any browser and flash., Jung-uk Kim
      • Re: R: Recent mouse freeze problem with X, different window managers, any browser and flash., Ariff Abdullah
      • Re: R: Recent mouse freeze problem with X, different window managers, any browser and flash., Jung-uk Kim
  • R: Recent mouse freeze problem with X, different window managers, any browser and flash., Barbara
• Recent mouse freeze problem with X, different window managers, any browser and flash., Edwin L. Culp W.
• console freeze after "ifconfig wlan0 scan" with wi(4) pccard device, Anton Shterenlikht
  • Re: console freeze after "ifconfig wlan0 scan" with wi(4) pccard device, Bernhard Schmidt
    • Re: console freeze after "ifconfig wlan0 scan" with wi(4) pccard device, Anton Shterenlikht
      • Re: console freeze after "ifconfig wlan0 scan" with wi(4) pccard device, Chris Brennan
• R: lockup with vidcontrol VESA_800x600, Barbara
• Lock-up with CPU busy at r217145; seems OK now at r217189, David Wolfskill
  • Re: Lock-up with CPU busy at r217145; seems OK now at r217189, Michael Butler
    • Re: Lock-up with CPU busy at r217145; seems OK now at r217189, Andriy Gapon
• Loading uart module fails, Bruce Cran
  • Re: Loading uart module fails, John Baldwin
    • Re: Loading uart module fails, Bruce Cran
      • Re: Loading uart module fails, John Baldwin
      • Re: Loading uart module fails, Bruce Cran
      • Re: Loading uart module fails, John Baldwin
• lockup with vidcontrol VESA_800x600, Marc UBM Bocklet
  • Re: lockup with vidcontrol VESA_800x600, Chris Brennan
    • Re: lockup with vidcontrol VESA_800x600, Marc UBM Bocklet
      • Re: lockup with vidcontrol VESA_800x600, Chris Brennan
  • <Possible follow-ups>
  • lockup with vidcontrol VESA_800x600, Marc UBM Bocklet
  • Re: lockup with vidcontrol VESA_800x600, b. f.
    • Re: lockup with vidcontrol VESA_800x600, Jung-uk Kim
      • Re: lockup with vidcontrol VESA_800x600, b. f.
      • Re: lockup with vidcontrol VESA_800x600, Jung-uk Kim
• NFSv4 and pam_mount - mounting user home directories., Marek Salwerowicz
  • Re: NFSv4 and pam_mount - mounting user home directories., Rick Macklem
  • <Possible follow-ups>
  • Re: NFSv4 and pam_mount - mounting user home directories., Marek Salwerowicz
    • Re: NFSv4 and pam_mount - mounting user home directories., Rick Macklem
      • Re: NFSv4 and pam_mount - mounting user home directories., Marek Salwerowicz
      • Re: NFSv4 and pam_mount - mounting user home directories., Rick Macklem
      • Re: NFSv4 and pam_mount - mounting user home directories., Marek Salwerowicz
      • Re: NFSv4 and pam_mount - mounting user home directories., Rick Macklem
      • Re: NFSv4 and pam_mount - mounting user home directories., Marek Salwerowicz
      • Re: NFSv4 and pam_mount - mounting user home directories., Rick Macklem
      • Re: NFSv4 and pam_mount - mounting user home directories (with security?), Marek Salwerowicz
      • Re: NFSv4 and pam_mount - mounting user home directories (with security?), Rick Macklem
• HEADS UP: Merge of binutils 2.17, Dimitry Andric
  • Re: HEADS UP: Merge of binutils 2.17, Mehmet Erol Sanliturk
    • Re: HEADS UP: Merge of binutils 2.17, Dimitry Andric
  • Re: HEADS UP: Merge of binutils 2.17, Doug Barton
    • Re: HEADS UP: Merge of binutils 2.17, Dimitry Andric
      • Re: HEADS UP: Merge of binutils 2.17, Doug Barton
      • Re: HEADS UP: Merge of binutils 2.17, Ade Lovett
      • Re: HEADS UP: Merge of binutils 2.17, Doug Barton
      • Re: HEADS UP: Merge of binutils 2.17, Ade Lovett
      • Re: HEADS UP: Merge of binutils 2.17, Garrett Cooper
      • Package building for -current (Was: Re: HEADS UP: Merge of binutils 2.17), Doug Barton
      • Message not available
      • Message not available
      • Message not available
      • Re: HEADS UP: Merge of binutils 2.17, Erik Cederstrand
      • Re: HEADS UP: Merge of binutils 2.17, Garrett Cooper
      • Re: HEADS UP: Merge of binutils 2.17, Pav Lucistnik
      • Re: HEADS UP: Merge of binutils 2.17, Dimitry Andric
  • Re: HEADS UP: Merge of binutils 2.17, Anonymous
    • Re: HEADS UP: Merge of binutils 2.17, Dimitry Andric
  • Re: HEADS UP: Merge of binutils 2.17, Anton Shterenlikht
• UDP checksum broken, -head and releng_8, Daniel Eischen
  • Re: UDP checksum broken, -head and releng_8, Bjoern A. Zeeb
    • Re: UDP checksum broken, -head and releng_8, Daniel Eischen
      • Re: UDP checksum broken, -head and releng_8, Daniel Eischen
      • Re: UDP checksum broken, -head and releng_8, Daniel Eischen
      • Re: UDP checksum broken, -head and releng_8, Bjoern A. Zeeb
      • Re: UDP checksum broken, -head and releng_8, Daniel Eischen
      • Re: UDP checksum broken, -head and releng_8, Bjoern A. Zeeb
• Re: xterm -C and TIOCCONS vs. PRIV_TTY_CONSOLE, Garrett Cooper
  • Re: xterm -C and TIOCCONS vs. PRIV_TTY_CONSOLE, Gary Jennejohn
  • Re: xterm -C and TIOCCONS vs. PRIV_TTY_CONSOLE, Claude Buisson
• nfssvc not available or version mismatch (nfsv4 client), Marek Salwerowicz
  • Message not available
    • Message not available
      • Re: nfssvc not available or version mismatch (nfsv4 client), Marek Salwerowicz
      • Re: nfssvc not available or version mismatch (nfsv4 client), Garrett Cooper
      • Re: nfssvc not available or version mismatch (nfsv4 client), Marek Salwerowicz
      • Re: nfssvc not available or version mismatch (nfsv4 client), Rick Macklem
      • Re: nfssvc not available or version mismatch (nfsv4 client), Ivan Voras
      • Re: nfssvc not available or version mismatch (nfsv4 client), Rick Macklem
      • Re: nfssvc not available or version mismatch (nfsv4 client), Ivan Voras
      • Re: nfssvc not available or version mismatch (nfsv4 client), Rick Macklem
      • Re: nfssvc not available or version mismatch (nfsv4 client), Anonymous
      • Re: nfssvc not available or version mismatch (nfsv4 client), Rick Macklem
      • Re: nfssvc not available or version mismatch (nfsv4 client), Marek Salwerowicz
      • Re: nfssvc not available or version mismatch (nfsv4 client), Sergey Kandaurov
• [ANNOUNCE] Playstation 3 support now in HEAD, Nathan Whitehorn
  • Re: [ANNOUNCE] Playstation 3 support now in HEAD, Sevan / Venture37
• Re: ahci timeout, Krzysztof Dajka
• [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
• Request for testing/comments -- import of new dialog/libdialog, Nathan Whitehorn
  • Re: Request for testing/comments -- import of new dialog/libdialog, Nathan Whitehorn
  • Re: Request for testing/comments -- import of new dialog/libdialog, Erik Trulsson
    • Re: Request for testing/comments -- import of new dialog/libdialog, Bruce Cran
    • Re: Request for testing/comments -- import of new dialog/libdialog, Nathan Whitehorn
    • Re: Request for testing/comments -- import of new dialog/libdialog, John Baldwin
  • Re: Request for testing/comments -- import of new dialog/libdialog, Yuri Pankov
    • Re: Request for testing/comments -- import of new dialog/libdialog, Anonymous
      • Re: Request for testing/comments -- import of new dialog/libdialog, Yuri Pankov
      • Re: Request for testing/comments -- import of new dialog/libdialog, Garrett Cooper
      • Re: Request for testing/comments -- import of new dialog/libdialog, Yuri Pankov
• system sleeping, Zhu Sha Zang
• freebsd and, gahn
• RFC regarding usage of ISO 8601 throughout the tree, Ulrich Spörlein
  • Re: RFC regarding usage of ISO 8601 throughout the tree, Kostik Belousov
  • Re: RFC regarding usage of ISO 8601 throughout the tree, Julian H. Stacey
    • Re: RFC regarding usage of ISO 8601 throughout the tree, Ulrich Spörlein
      • Re: RFC regarding usage of ISO 8601 throughout the tree, Miroslav Lachman
      • Re: RFC regarding usage of ISO 8601 throughout the tree, John Baldwin
      • Re: RFC regarding usage of ISO 8601 throughout the tree, Martin Schütte
      • Re: RFC regarding usage of ISO 8601 throughout the tree, Gary Jennejohn
      • Re: RFC regarding usage of ISO 8601 throughout the tree, Julian H. Stacey
  • Re: RFC regarding usage of ISO 8601 throughout the tree, Rob Farmer
• FYI: clang static analyzer page has moved to http://scan.freebsd.your.org/freebsd-head/, Ulrich Spörlein
  • Re: FYI: clang static analyzer page has moved to http://scan.freebsd.your.org/freebsd-head/, Erik Cederstrand
    • Re: FYI: clang static analyzer page has moved to http://scan.freebsd.your.org/freebsd-head/, Erik Cederstrand
      • Re: FYI: clang static analyzer page has moved to http://scan.freebsd.your.org/freebsd-head/, John Baldwin
      • Re: FYI: clang static analyzer page has moved to http://scan.freebsd.your.org/freebsd-head/, Ulrich Spörlein
      • Re: FYI: clang static analyzer page has moved to http://scan.freebsd.your.org/freebsd-head/, Roman Divacky
      • Re: FYI: clang static analyzer page has moved to http://scan.freebsd.your.org/freebsd-head/, Jilles Tjoelker
      • Re: FYI: clang static analyzer page has moved to http://scan.freebsd.your.org/freebsd-head/, Ulrich Spörlein
      • Re: FYI: clang static analyzer page has moved to http://scan.freebsd.your.org/freebsd-head/, Jilles Tjoelker
      • Re: FYI: clang static analyzer page has moved to http://scan.freebsd.your.org/freebsd-head/, Ulrich Spörlein
      • Re: FYI: clang static analyzer page has moved to http://scan.freebsd.your.org/freebsd-head/, Erik Cederstrand
      • Re: FYI: clang static analyzer page has moved to http://scan.freebsd.your.org/freebsd-head/, Tijl Coosemans
      • Re: FYI: clang static analyzer page has moved to http://scan.freebsd.your.org/freebsd-head/, Erik Cederstrand
      • Re: FYI: clang static analyzer page has moved to http://scan.freebsd.your.org/freebsd-head/, Roman Divacky
      • Re: FYI: clang static analyzer page has moved to http://scan.freebsd.your.org/freebsd-head/, Erik Cederstrand
      • Re: FYI: clang static analyzer page has moved to http://scan.freebsd.your.org/freebsd-head/, Roman Divacky
  • Re: FYI: clang static analyzer page has moved to http://scan.freebsd.your.org/freebsd-head/, Tijl Coosemans
• Re: CAM related panic on 8.2-PRERELEASE Was: Re: USB related panic on 8.2-PRERELEASE, Oleg Nauman
• usb-regression (Tyan S3992-E), Arno J. Klaassen
  • Re: usb-regression (Tyan S3992-E), Hans Petter Selasky
  • Re: usb-regression (Tyan S3992-E), John Baldwin
• Re: Next ZFSv28 patchset ready for testing., Pawel Jakub Dawidek
• [RFC]: unnecessary padding in various kernel structures, Roman Divacky
  • Re: [RFC]: unnecessary padding in various kernel structures, Ivan Voras
• Re: Virtio drivers for FreeBSD on KVM, Pete French
  • <Possible follow-ups>
  • Re: Virtio drivers for FreeBSD on KVM, Pete French
    • Re: Virtio drivers for FreeBSD on KVM, Phil Regnauld
• mfiutil and raid level, Danilo G. Baio
  • Re: mfiutil and raid level, John Baldwin
    • Re: mfiutil and raid level, Danilo G. Baio
      • Re: mfiutil and raid level, John Baldwin
      • Re: mfiutil and raid level, Danilo G. Baio
• AMD X2/Opteron Rev E workaround ?, Marco Steinbach
• Another virtio drivers for FreeBSD, Takeshi HASEGAWA
• RE: jailing MYSQL error [SOLVED], dsc fbsd.current
• Re: No human readable message with g_vfs, Ivan Voras
  • Re: No human readable message with g_vfs, Matthias Andree
    • Re: No human readable message with g_vfs, Kostik Belousov
      • Re: No human readable message with g_vfs, Edward Tomasz Napierała
      • Re: No human readable message with g_vfs, Garrett Cooper
      • Re: No human readable message with g_vfs, Anonymous
      • Re: No human readable message with g_vfs, Garrett Cooper
      • Re: No human readable message with g_vfs, Bakul Shah
      • Re: No human readable message with g_vfs, Anonymous
      • Re: No human readable message with g_vfs, Bakul Shah
• Oddities in -current post-eventtimer, Matthew D. Fuller
  • Re: Oddities in -current post-eventtimer, Alexander Motin
    • Re: Oddities in -current post-eventtimer, Matthew D. Fuller
• [Call for testers] FreeBSD VirtIO Network Driver, bv
  • Re: [Call for testers] FreeBSD VirtIO Network Driver, Adam Vande More
• jailing MYSQL error, dsc fbsd.current
  • Re: jailing MYSQL error, J. Hellenthal
• keyboard driver problem?, too . much . dudes
  • Re: keyboard driver problem?, Hans Petter Selasky
  • Re: keyboard driver problem?, Hans Petter Selasky
  • <Possible follow-ups>
  • keyboard driver problem?, I Think
    • Re: keyboard driver problem?, Hans Petter Selasky
  • keyboard driver problem?, too . much . dudes
    • Re: keyboard driver problem?, Hans Petter Selasky
  • Re: keyboard driver problem?, too . much . dudes
• Re: wlan/wpi are more broken than 3 weeks., Steve Kargl
  • Re: wlan/wpi are more broken than 3 weeks., Bernhard Schmidt
• Suddenly slow lstat syscalls on CURRENT from Juli, Beat Gätzi
  • Re: Suddenly slow lstat syscalls on CURRENT from Juli, Alexander Best
    • Re: Suddenly slow lstat syscalls on CURRENT from Juli, Beat Gätzi
      • Re: Suddenly slow lstat syscalls on CURRENT from Juli, Kostik Belousov
      • Re: Suddenly slow lstat syscalls on CURRENT from Juli, Beat Gätzi
      • Re: Suddenly slow lstat syscalls on CURRENT from Juli, Kostik Belousov
      • Re: Suddenly slow lstat syscalls on CURRENT from Juli, Beat Gätzi
      • Re: Suddenly slow lstat syscalls on CURRENT from Juli, Kostik Belousov
      • Re: Suddenly slow lstat syscalls on CURRENT from Juli, Beat Gätzi
      • Re: Suddenly slow lstat syscalls on CURRENT from Juli, Kostik Belousov
      • Re: Suddenly slow lstat syscalls on CURRENT from Juli, Julian Elischer
      • Re: Suddenly slow lstat syscalls on CURRENT from Juli, Beat Gätzi
      • Re: Suddenly slow lstat syscalls on CURRENT from Juli, Beat Gätzi
      • Re: Suddenly slow lstat syscalls on CURRENT from Juli, Alexander Best
• boost libs error, Doug Barton
  • Re: boost libs error, Alexander Churanov
    • Re: boost libs error, Doug Barton
    • Re: boost libs error, Doug Barton
• Re: userland weirdness between r216351 and r216738, Alexander Kabaev
  • Re: userland weirdness between r216351 and r216738, Alexander Best
  • Re: userland weirdness between r216351 and r216738, Alexander Best
    • Re: userland weirdness between r216351 and r216738, Alexander Kabaev
      • Re: userland weirdness between r216351 and r216738, Alexander Best
  • Re: userland weirdness between r216351 and r216738, Rene Ladan
  • <Possible follow-ups>
  • Re: userland weirdness between r216351 and r216738, George Liaskos
  • Re: userland weirdness between r216351 and r216738, poyopoyo
    • Re: userland weirdness between r216351 and r216738, René Ladan
  • Re: userland weirdness between r216351 and r216738, Dimitry Andric

• Security
• UNIX
• Linux
• Coding
• Usenet

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

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