freebsd-hackers

• Date Index

---

• Request for opinions - gvinum or ccd?, xorquewasp
  • Re: Request for opinions - gvinum or ccd?, Mike Meyer
    • Re: Request for opinions - gvinum or ccd?, xorquewasp
      • Re: Request for opinions - gvinum or ccd?, Mike Meyer
      • Re: Request for opinions - gvinum or ccd?, xorquewasp
      • Re: Request for opinions - gvinum or ccd?, Michael Reifenberger
      • RE: Request for opinions - gvinum or ccd?, krad
      • Re: Request for opinions - gvinum or ccd?, xorquewasp
      • Re: Request for opinions - gvinum or ccd?, Mike Meyer
• pf nat+bridge, Gema niskazhu
• Log message, Sergio Tam
  • Re: Log message, Julian Elischer
  • <Possible follow-ups>
  • Re: Log message, Sergio Tam
• Debugging via DDB, David N
  • Re: Debugging via DDB, Kip Macy
• nfs_diskless_valid question, Danny Braniss
• Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Dag-Erling Smørgrav
  • Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Dag-Erling Smørgrav
  • Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Dag-Erling Smørgrav
    • Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Mel Flynn
      • Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Eygene Ryabinkin
  • Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Eygene Ryabinkin
    • Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Dag-Erling Smørgrav
      • Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Eygene Ryabinkin
      • Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Dag-Erling Smørgrav
      • Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Eygene Ryabinkin
      • Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Dag-Erling Smørgrav
      • Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Dag-Erling Smørgrav
      • Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Eygene Ryabinkin
      • Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Dag-Erling Smørgrav
      • Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Oliver Pinter
      • Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Dag-Erling Smørgrav
  • Message not available
    • Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Dag-Erling Smørgrav
      • Message not available
      • Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Dag-Erling Smørgrav
      • Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Dag-Erling Smørgrav
      • Re: FYI Lighttpd 1.4.23 /kernel (trailing '/' on regular file symlink) vulnerability, Eygene Ryabinkin
• MosChip 7840 dual port ucom, Dmitry Morozovsky
  • Re: MosChip 7840 dual port ucom, Rui Paulo
• Help debugging kernel together with X, Fernando Herrero Carrón
  • Re: Help debugging kernel together with X, Glen Barber
    • Re: Help debugging kernel together with X, Fernando Herrero Carrón
• Disk quota for Jail. Discussion., Menshikov Konstantin
  • Re: Disk quota for Jail. Discussion., Kostik Belousov
    • Re: Disk quota for Jail. Discussion., Menshikov Konstantin
      • Re: Disk quota for Jail. Discussion., Kostik Belousov
      • Re: Disk quota for Jail. Discussion., Menshikov Konstantin
      • Re: Disk quota for Jail. Discussion., Kostik Belousov
      • Re: Disk quota for Jail. Discussion., Tom Evans
      • Re: Disk quota for Jail. Discussion., Menshikov Konstantin
      • Re: Disk quota for Jail. Discussion., Robert Watson
      • Re: Disk quota for Jail. Discussion., Menshikov Konstantin
  • Re: Disk quota for Jail. Discussion., Ivan Voras
    • Re: Disk quota for Jail. Discussion., Menshikov Konstantin
      • Re: Disk quota for Jail. Discussion., Ivan Voras
      • Re: Disk quota for Jail. Discussion., Ivan Voras
• Random(?) Fatal trap 12 in Freebsd 7.2 release, C. C. Tang
• How to visualize cache misses with pmc, Nikola Knežević
• improve my USB knowledge, Rodrigo OSORIO (ros)
  • Re: improve my USB knowledge, Hans Petter Selasky
  • Re: improve my USB knowledge, Daniel O'Connor
  • Re: improve my USB knowledge, Julian Elischer
• Kernel Conference Australia 2009 - one week to go for earlybird registrations, James C. McPherson
• [CFT] ssh/scp/ssh-add/ssh-agent/ssh-keygen on /rescue, Norikatsu Shigemura
• about building the crosstools, Chuck Robey
  • Re: about building the crosstools, M. Warner Losh
• Re: Installation from USB pen, Randy Bush
  • Re: Installation from USB pen, Stanislav Sedov
    • Re: Installation from USB pen, Randy Bush
  • Re: Installation from USB pen, Daniel O'Connor
• compiling system binutils as cross tools, xorquewasp
  • Re: compiling system binutils as cross tools, Robert Watson
    • Re: compiling system binutils as cross tools, xorquewasp
    • Re: compiling system binutils as cross tools, Julian Elischer
  • Re: compiling system binutils as cross tools, Stanislav Sedov
    • Re: compiling system binutils as cross tools, xorquewasp
      • Re: compiling system binutils as cross tools, Stanislav Sedov
      • Re: compiling system binutils as cross tools, xorquewasp
• Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, Yuri
  • Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, Nate Eldredge
    • Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, perryh
      • Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, Nate Eldredge
    • Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, Yuri
      • Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, Bernd Walter
      • Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, Nate Eldredge
      • Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, Matthew Dillon
      • Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, Jonathan McKeown
      • Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, Matthew Dillon
      • Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, Daniel O'Connor
      • Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, Alfred Perlstein
      • Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, Dag-Erling Smørgrav
      • Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, Alfred Perlstein
      • Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, Dag-Erling Smørgrav
      • Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, Alfred Perlstein
    • Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, Thomas Hurst
      • Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, Kostik Belousov
  • Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, Rayson Ho
  • Re: Why kernel kills processes that run out of memory instead of just failing memory allocation system calls?, Ilya Orehov
• Jail limits under CURRENT, Меньшиков Константин
• Question about PCIe networks, Eduardo Morras
  • Re: Question about PCIe networks, Steve Watt
• IPv6 support on BSNMP, Carlos A. M. dos Santos
• Which priority do taskqueues have?, Hans Petter Selasky
  • Re: Which priority do taskqueues have?, John Baldwin
• sshd(8) - alert user when fails to execute from rc.d, Glen Barber
  • Re: bin/134694: gives false-positive when unable to obtain socket [WAS: sshd(8) - alert user when fails to execute from rc.d], Eygene Ryabinkin
    • Re: bin/134694: gives false-positive when unable to obtain socket [WAS: sshd(8) - alert user when fails to execute from rc.d], Dimitry Andric
      • Re: bin/134694: gives false-positive when unable to obtain socket [WAS: sshd(8) - alert user when fails to execute from rc.d], Tobias Fendin
      • Re: bin/134694: gives false-positive when unable to obtain socket [WAS: sshd(8) - alert user when fails to execute from rc.d], Dimitry Andric
      • Re: bin/134694: gives false-positive when unable to obtain socket [WAS: sshd(8) - alert user when fails to execute from rc.d], Glen Barber
      • Re: bin/134694: gives false-positive when unable to obtain socket [WAS: sshd(8) - alert user when fails to execute from rc.d], Dimitry Andric
      • Re: bin/134694: gives false-positive when unable to obtain socket [WAS: sshd(8) - alert user when fails to execute from rc.d], Glen Barber
      • Re: bin/134694: gives false-positive when unable to obtain socket [WAS: sshd(8) - alert user when fails to execute from rc.d], Glen Barber
    • Re: bin/134694: gives false-positive when unable to obtain socket [WAS: sshd(8) - alert user when fails to execute from rc.d], Glen Barber
• porting info for FreeBSD's kernel?, Chuck Robey
  • Re: porting info for FreeBSD's kernel?, Alfred Perlstein
    • Re: porting info for FreeBSD's kernel?, Chuck Robey
      • Re: porting info for FreeBSD's kernel?, Alfred Perlstein
      • Re: porting info for FreeBSD's kernel?, Chuck Robey
      • Re: porting info for FreeBSD's kernel?, Alfred Perlstein
• FreeBSD jobs, Julian Stacey
  • Re: FreeBSD jobs, Rayson Ho
  • Re: FreeBSD jobs, Matt Olander
    • Re: FreeBSD jobs, Julian Stacey
      • Re: FreeBSD jobs, Achim Patzner
      • Re: FreeBSD jobs, Julian Stacey
      • Re: FreeBSD jobs, Mark Linimon
      • Re: FreeBSD jobs, Marcel Moolenaar
    • FreeBSD jobs, Alfred Perlstein
• ipfw uid rules for lo0 interface, Олег Петрачёв
  • Re: ipfw uid rules for lo0 interface, Stanislav Sedov
• In search of a video card, Josef Grosch
  • Re: In search of a video card, Sam Fourman Jr.
    • Re: In search of a video card, Josef Grosch
  • Re: In search of a video card, Mike Meyer
    • Re: In search of a video card, Josef Grosch
      • Re: In search of a video card, Adrian Chadd
      • Re: In search of a video card, Daniel O'Connor
      • Re: In search of a video card, Robert Noland
      • Re: In search of a video card, Rick C. Petty
      • Re: In search of a video card, Mike Meyer
      • Re: In search of a video card, Rick C. Petty
  • Re: In search of a video card, Roman Divacky
  • Re: In search of a video card, xorquewasp
    • Re: In search of a video card, Alexander Sabourenkov
  • Re: In search of a video card, Robert Noland
  • Re: In search of a video card, Rick C. Petty
• PTE modified bit emulation trap, Dag-Erling Smørgrav
  • Re: PTE modified bit emulation trap, John Baldwin
    • Re: PTE modified bit emulation trap, Dag-Erling Smørgrav
• Kernel Conference Australia 2009 - registrations and agenda pages NOW LIVE, James C. McPherson
• Memory leak on thread removal, Mikolaj Golub
  • Re: Memory leak on thread removal, Marius Nünnerich
    • Re: Memory leak on thread removal, Andriy Tkachuk
    • Re: Memory leak on thread removal, Mikolaj Golub
      • Re: Memory leak on thread removal, Pieter de Goeje
      • Re: Memory leak on thread removal, Marius Nünnerich
      • Re: Memory leak on thread removal, Mikolaj Golub
  • Re: Memory leak on thread removal, Mikolaj Golub
• Re: POSIXfy readlink() call, John Baldwin
  • Re: POSIXfy readlink() call, Kostik Belousov
    • Re: POSIXfy readlink() call, John Baldwin
      • Re: POSIXfy readlink() call, Kostik Belousov
      • Re: POSIXfy readlink() call, John Baldwin
      • Re: POSIXfy readlink() call, Ruslan Ermilov
• contigmalloc & access protection failure, Ray Kinsella
  • Re: contigmalloc & access protection failure, Ryan Stone
  • Re: contigmalloc & access protection failure, Ryan Stone
    • Re: contigmalloc & access protection failure, Ray Kinsella
    • Re: contigmalloc & access protection failure, Ray Kinsella
• FreeBSD Status Reports January - March, 2009, Brad Davis
• Re: SoC 2009: Improving ext2fs and making it GPL free, Subhro Kar
  • Re: SoC 2009: Improving ext2fs and making it GPL free, Aditya Sarawgi
  • <Possible follow-ups>
  • Re: SoC 2009: Improving ext2fs and making it GPL free, Aditya Sarawgi
• kthreads and sched_relinquish, Andrew Brampton
  • Re: kthreads and sched_relinquish, Ryan Stone
    • Re: kthreads and sched_relinquish, Andrew Brampton
• fputsock()/fgetsock() replacement, Danny Braniss
• undetected umass device, Danny Braniss
  • Re: undetected umass device, Hans Petter Selasky
    • Re: undetected umass device, Danny Braniss
• How to invalidate NFS read cache?, Konrad Heuer
  • Re: How to invalidate NFS read cache?, Robert Watson
    • Re: How to invalidate NFS read cache?, Robert Watson
    • Re: How to invalidate NFS read cache?, Konrad Heuer
      • Re: How to invalidate NFS read cache?, Konrad Heuer
• fdescfs brokenness, Tim Kientzle
  • Re: fdescfs brokenness, Kostik Belousov
    • Re: fdescfs brokenness, Jilles Tjoelker
      • Re: fdescfs brokenness, Kostik Belousov
• DAD Detected duplicate ipv6 address - 7.2 Stable, Pegasus Mc Cleaft
• Re: SoC 2009: BSD-licensed libiconv in base system, Gabor Kovesdan
  • Re: SoC 2009: BSD-licensed libiconv in base system, Alexander Churanov
    • Re: SoC 2009: BSD-licensed libiconv in base system, Erik Trulsson
      • Re: SoC 2009: BSD-licensed libiconv in base system, Alexander Churanov
    • Re: SoC 2009: BSD-licensed libiconv in base system, Joerg Sonnenberger
      • Re: SoC 2009: BSD-licensed libiconv in base system, Buganini
• Re: Patch for MS Hyper V (virtualization), David Malone
• concurrent sysctl implementation, jt
  • Re: concurrent sysctl implementation, vasanth raonaik
    • Re: concurrent sysctl implementation, Ed Schouten
      • Re: concurrent sysctl implementation, jt
      • Re: concurrent sysctl implementation, Lars Engels
      • Re: concurrent sysctl implementation, Ed Schouten
      • Re: concurrent sysctl implementation, John Baldwin
      • Re: concurrent sysctl implementation, jt
      • Re: concurrent sysctl implementation, John Baldwin
      • Re: concurrent sysctl implementation, Ed Schouten
      • Re: concurrent sysctl implementation, John Baldwin
• bootstrapping gnat GCC on amd64, xorquewasp
  • Re: bootstrapping gnat GCC on amd64, Daniel Eischen
    • Re: bootstrapping gnat GCC on amd64, xorquewasp
      • Re: bootstrapping gnat GCC on amd64, Daniel Eischen
      • Re: bootstrapping gnat GCC on amd64, xorquewasp
      • Re: bootstrapping gnat GCC on amd64, Daniel Eischen
      • Re: bootstrapping gnat GCC on amd64, xorquewasp
      • Re: bootstrapping gnat GCC on amd64, Daniel Eischen
      • Message not available
      • Message not available
      • Re: bootstrapping gnat GCC on amd64, xorquewasp
      • Message not available
      • Message not available
      • Message not available
      • Re: bootstrapping gnat GCC on amd64, xorquewasp
      • Re: bootstrapping gnat GCC on amd64, xorquewasp
      • Re: bootstrapping gnat GCC on amd64, xorquewasp
      • Re: bootstrapping gnat GCC on amd64, Daniel Eischen
      • Re: bootstrapping gnat GCC on amd64, xorquewasp
      • Re: bootstrapping gnat GCC on amd64, Daniel Eischen
      • Re: bootstrapping gnat GCC on amd64, xorquewasp
      • Re: bootstrapping gnat GCC on amd64, Daniel Eischen
      • Re: bootstrapping gnat GCC on amd64, xorquewasp
• VirtualBox on FreeBSD, Matt Olander
  • Re: VirtualBox on FreeBSD, Guillermo Antonio Amaral Bastidas
• ZFS ARC Cache: What is the lowest tested size, Mark Saad
  • Re: ZFS ARC Cache: What is the lowest tested size, Kip Macy
• Definition of NULL, Andrew Brampton
  • Re: Definition of NULL, Erik Trulsson
    • Re: Definition of NULL, Andrew Brampton
    • Re: Definition of NULL, Andriy Gapon
  • Re: Definition of NULL, John Baldwin
    • Re: Definition of NULL, Joerg Sonnenberger
• SoC2009: Geom-based Disk Schedulers, Fabio Checconi
• SoC2009: Ipfw and dummyent improvements, Marta Carbone
• Why top never shows ~100% CPU usage with heavy PCU load?, Yuri
  • Re: Why top never shows ~100% CPU usage with heavy PCU load?, Alexey Shuvaev
    • Re: Why top never shows ~100% CPU usage with heavy PCU load?, Yuri
• USENIX WebApps '10 Call for Papers Now Available, Lionel Garth Jones
• Cobalt Raq 550, Justin G.
  • Re: Cobalt Raq 550, Simon Dick
    • Re: Cobalt Raq 550, Jukka Ruohonen
      • Re: Cobalt Raq 550, Simon Dick
• Re: IPsec in GENERIC kernel config, Ana Kukec
• vfs_cache panic, 7.2-prerelease (stable), xorquewasp
  • Re: vfs_cache panic, 7.2-prerelease (stable), xorquewasp
    • Re: vfs_cache panic, 7.2-prerelease (stable), Attilio Rao
      • Re: vfs_cache panic, 7.2-prerelease (stable), xorquewasp
  • Re: vfs_cache panic, 7.2-prerelease (stable), Alexander Kabaev
    • Re: vfs_cache panic, 7.2-prerelease (stable), xorquewasp
      • Re: vfs_cache panic, 7.2-prerelease (stable), Alexander Kabaev
      • Re: vfs_cache panic, 7.2-prerelease (stable), xorquewasp
• Re: C99: Suggestions for style(9), Christoph Mallon
  • Re: C99: Suggestions for style(9), Julian Elischer
    • Re: C99: Suggestions for style(9), Bruce Cran
    • Re: C99: Suggestions for style(9), Christoph Mallon
    • Re: C99: Suggestions for style(9), Zaphod Beeblebrox
      • Re: C99: Suggestions for style(9), Christoph Mallon
      • Re: C99: Suggestions for style(9), Julian Elischer
      • Re: C99: Suggestions for style(9), Christoph Mallon
      • Message not available
      • Re: C99: Suggestions for style(9), Christoph Mallon
      • Re: C99: Suggestions for style(9), Daniel Eischen
  • Re: C99: Suggestions for style(9), M. Warner Losh
    • Re: C99: Suggestions for style(9), Christoph Mallon
  • <Possible follow-ups>
  • Re: C99: Suggestions for style(9), Christoph Mallon
    • Re: C99: Suggestions for style(9), Maxim Sobolev
      • Re: C99: Suggestions for style(9), Andriy Gapon
  • Re: C99: Suggestions for style(9), Marius Strobl
    • Re: C99: Suggestions for style(9), Christoph Mallon
      • Re: C99: Suggestions for style(9), Marius Strobl
      • Re: C99: Suggestions for style(9), Christoph Mallon
      • Re: C99: Suggestions for style(9), M. Warner Losh
      • Re: C99: Suggestions for style(9), Julian Elischer
      • Re: C99: Suggestions for style(9), Stanislav Sedov
      • Re: C99: Suggestions for style(9), Christoph Mallon
    • Re: C99: Suggestions for style(9), Danny Braniss
  • Re: C99: Suggestions for style(9), Christoph Mallon
    • C++ incompatability, was C99: Suggestions for style(9), Matthew Fleming
      • Re: C++ incompatability, was C99: Suggestions for style(9), Bakul Shah
      • RE: C++ incompatability, was C99: Suggestions for style(9), Matthew Fleming
    • Re: C99: Suggestions for style(9), Stanislav Sedov
      • Re: C99: Suggestions for style(9), Christoph Mallon
      • Re: C99: Suggestions for style(9), Stanislav Sedov
      • Re: C99: Suggestions for style(9), Christoph Mallon
  • Re: C99: Suggestions for style(9), deeptech71
    • Re: C99: Suggestions for style(9), Christoph Mallon
  • Re: C99: Suggestions for style(9), Rick C. Petty
    • Re: C99: Suggestions for style(9), M. Warner Losh
      • Re: C99: Suggestions for style(9), Christoph Mallon
      • Re: C99: Suggestions for style(9), Julian Elischer
      • Re: C99: Suggestions for style(9), Christoph Mallon
      • Re: C99: Suggestions for style(9), M. Warner Losh
      • Re: C99: Suggestions for style(9), M. Warner Losh
      • Re: C99: Suggestions for style(9), Christoph Mallon
      • Re: C99: Suggestions for style(9), Stanislav Sedov
      • Re: C99: Suggestions for style(9), deeptech71
      • Re: C99: Suggestions for style(9), Stanislav Sedov
  • Re: C99: Suggestions for style(9), David Malone
    • Re: C99: Suggestions for style(9), Christoph Mallon
      • Re: C99: Suggestions for style(9), David Malone
      • Re: C99: Suggestions for style(9), Julian Elischer
      • Re: C99: Suggestions for style(9), Christoph Mallon
    • Re: C99: Suggestions for style(9), Julian Elischer
      • Re: C99: Suggestions for style(9), Christoph Mallon
      • Re: C99: Suggestions for style(9), Julian Elischer
      • Re: C99: Suggestions for style(9), Christoph Mallon
      • Re: C99: Suggestions for style(9), Julian Elischer
      • Re: C99: Suggestions for style(9), Christoph Mallon
      • Re: C99: Suggestions for style(9), Julian Elischer
      • Re: C99: Suggestions for style(9), Christoph Mallon
      • Re: C99: Suggestions for style(9), Julian Elischer
      • Re: C99: Suggestions for style(9), Christoph Mallon
      • Re: C99: Suggestions for style(9), M. Warner Losh
      • Re: C99: Suggestions for style(9), Christoph Mallon
      • Re: C99: Suggestions for style(9), M. Warner Losh
  • Re: C99: Suggestions for style(9), Peter Jeremy
• Re: NetBSD 5.0 statistics, Marcel Moolenaar
  • Re: NetBSD 5.0 statistics, Joerg Sonnenberger
  • <Possible follow-ups>
  • Re: NetBSD 5.0 statistics, Alexander Kabaev
• Re: SoC2009: libpkg, pkg tools rewrite, Jeremy Lea
  • Re: SoC2009: libpkg, pkg tools rewrite, Garrett Cooper
    • Re: SoC2009: libpkg, pkg tools rewrite, Tim Kientzle
  • Re: SoC2009: libpkg, pkg tools rewrite, Tim Kientzle

• Security
• UNIX
• Linux
• Coding
• Usenet

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

unix.derkeiler.com  > Mailing-Lists  > FreeBSD  > hackers  > 2009-05