freebsd-hackers

• Date Index

---

• Updating vmware3 (and missing "avail_end" from /usr/include/machine/pmap.h), fchang
• umass: should the device specific information be moved from C code to the text file?, Yuri
  • Re: umass: should the device specific information be moved from C code to the text file?, Peter Jeremy
    • Re: umass: should the device specific information be moved from C code to the text file?, Ivan Voras
      • Re: umass: should the device specific information be moved from C code to the text file?, Bernd Walter
• problem with ldconfig, Chuck Robey
  • Re: problem with ldconfig, Ben Kaduk
    • Re: problem with ldconfig; nvidia loading fixed, Chuck Robey
      • Re: problem with loading 1/2 fixed, Chuck Robey
      • Re: problem with loading all fixed now, Chuck Robey
• PXE on 7.0 problem and solution, Tim Clewlow
  • Re: PXE on 7.0 problem and solution, Erik Cederstrand
  • Re: PXE on 7.0 problem and solution, Jeremy Chadwick
• pfind() in ithread handler, Yuri Pankov
  • Re: pfind() in ithread handler, pluknet
  • Re: pfind() in ithread handler, Attilio Rao
• Java 1.6 Berkeley Oracle DB XML Bioinformatics, KAYVEN RIESE
• Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?, Yuri
  • Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?, Sam Leffler
    • Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?, Yuri
      • Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?, Pietro Cerutti
      • Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?, Yuri
      • Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?, Sam Leffler
      • Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?, Yuri
    • Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?, KAYVEN RIESE
      • Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?, Yuri
      • Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?, KAYVEN RIESE
  • <Possible follow-ups>
  • Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?, Yuri
• cvs tag renaming after repo copy, John Hein
  • Re: cvs tag renaming after repo copy, Giorgos Keramidas
    • Re: cvs tag renaming after repo copy, John Hein
      • Re: cvs tag renaming after repo copy, Giorgos Keramidas
      • Re: cvs tag renaming after repo copy, Amol Dharmadhikari अमोल धर्माधीकारी
      • Re: cvs tag renaming after repo copy, John Hein
  • Re: cvs tag renaming after repo copy, Simon L. Nielsen
    • Re: cvs tag renaming after repo copy, Dag-Erling Smørgrav
      • Re: cvs tag renaming after repo copy, John E Hein
      • Re: cvs tag renaming after repo copy, Dag-Erling Smørgrav
      • Re: cvs tag renaming after repo copy, John E Hein
      • Re: cvs tag renaming after repo copy, John E Hein
      • Re: cvs tag renaming after repo copy, Dag-Erling Smørgrav
      • Re: cvs tag renaming after repo copy, Simon L. Nielsen
      • Re: cvs tag renaming after repo copy, Skip Ford
• non-blocking io, EINTR, Mark Linn
  • Re: non-blocking io, EINTR, Ed Schouten
  • Re: non-blocking io, EINTR, James Bailie
    • Re: non-blocking io, EINTR, Mark Linn
  • <Possible follow-ups>
  • Re: Re: non-blocking io, EINTR, jimmy
• Re: sbc: isa plug-n-play, Andriy Gapon
• emulate an end-of-media, Martin Laabs
  • Re: emulate an end-of-media, Mike Meyer
  • <Possible follow-ups>
  • Re: emulate an end-of-media, Martin Laabs
    • Re: emulate an end-of-media, Mike Meyer
      • Re: emulate an end-of-media, Alex Zbyslaw
      • Re: emulate an end-of-media, Julian H. Stacey
      • Re: emulate an end-of-media, Tim Kientzle
      • Re: emulate an end-of-media, Alex Zbyslaw
      • Re: emulate an end-of-media, Martin Laabs
      • Re: emulate an end-of-media, Joerg Sonnenberger
      • Re: emulate an end-of-media, Mike Meyer
      • Re: emulate an end-of-media, Joerg Sonnenberger
      • Re: emulate an end-of-media, Mike Meyer
      • Re: emulate an end-of-media, Daniel O'Connor
      • Re: emulate an end-of-media, Peter Jeremy
      • Re: emulate an end-of-media, Martin Laabs
      • Re: emulate an end-of-media, Martin Laabs
• Anybody have a patch for pdksh derivatives, for jails?, cali clarke
  • Re: Anybody have a patch for pdksh derivatives, for jails?, Alexander Leidinger
    • Re: Anybody have a patch for pdksh derivatives, for jails?, xorquewasp
  • Re: Anybody have a patch for pdksh derivatives, for jails?, Tom Evans
    • Re: Anybody have a patch for pdksh derivatives, for jails?, xorquewasp
• Re: VM design doc?, Stanislav Sedov
• loader and ficl/Forth help, Jeremy Chadwick
  • Re: loader and ficl/Forth help, Oliver Fromme
    • Re: loader and ficl/Forth help, Jeremy Chadwick
      • Re: loader and ficl/Forth help, Oliver Fromme
      • Re: loader and ficl/Forth help, Jeremy Chadwick
      • Re: loader and ficl/Forth help, Jeremy Chadwick
• Modular type GENERIC?, Adrian Chadd
  • Re: Modular type GENERIC?, Alexander Leidinger
  • Re: Modular type GENERIC?, David O'Brien
    • Re: Modular type GENERIC?, Adrian Chadd
      • Re: Modular type GENERIC?, David O'Brien
      • Re: Modular type GENERIC?, Adrian Chadd
      • Re: Modular type GENERIC?, David O'Brien
      • Re: Modular type GENERIC?, Adrian Chadd
      • Re: Modular type GENERIC?, Pieter de Goeje
      • Re: Modular type GENERIC?, Adrian Chadd
• Security Flaw in Popular Disk Encryption Technologies, Atom Smasher
  • Re: Security Flaw in Popular Disk Encryption Technologies, Pieter de Boer
    • Re: Security Flaw in Popular Disk Encryption Technologies, Jeremy Chadwick
      • Re: Security Flaw in Popular Disk Encryption Technologies, Pieter de Boer
      • Re: Security Flaw in Popular Disk Encryption Technologies, Tim Clewlow
      • Re: Security Flaw in Popular Disk Encryption Technologies, Brooks Davis
      • Re: Security Flaw in Popular Disk Encryption Technologies, Igor Mozolevsky
      • Re: Security Flaw in Popular Disk Encryption Technologies, Achim Patzner
      • Re: Security Flaw in Popular Disk Encryption Technologies, Bill Moran
      • Re: Security Flaw in Popular Disk Encryption Technologies, Igor Mozolevsky
      • Re: Security Flaw in Popular Disk Encryption Technologies, Bill Moran
      • Re: Security Flaw in Popular Disk Encryption Technologies, Igor Mozolevsky
      • Re: Security Flaw in Popular Disk Encryption Technologies, Bill Moran
      • Re: Security Flaw in Popular Disk Encryption Technologies, Igor Mozolevsky
      • Re: Security Flaw in Popular Disk Encryption Technologies, Rink Springer
      • Re: Security Flaw in Popular Disk Encryption Technologies, Christopher Arnold
      • Re: Security Flaw in Popular Disk Encryption Technologies, Bill Moran
      • Zeroing sensitive memory chunks [Was: Security Flaw in Popular Disk Encryption Technologies], Eygene Ryabinkin
      • Re: Zeroing sensitive memory chunks [Was: Security Flaw in Popular Disk Encryption Technologies], Jeremy Chadwick
      • Re: Zeroing sensitive memory chunks [Was: Security Flaw in Popular Disk Encryption Technologies], Eygene Ryabinkin
      • Re: Zeroing sensitive memory chunks [Was: Security Flaw in Popular Disk Encryption Technologies], gregoryd . freebsd
      • Re: Zeroing sensitive memory chunks [Was: Security Flaw in Popular Disk Encryption Technologies], Eygene Ryabinkin
      • Re: Zeroing sensitive memory chunks [Was: Security Flaw in Popular Disk Encryption Technologies], RW
      • synchronous freebsd print, Sanjeev Kumar.S
      • Re: synchronous freebsd print, Peter Jeremy
      • Re: synchronous freebsd print, Sanjeev Kumar.S
      • Re: synchronous freebsd print, Eygene Ryabinkin
      • Re: synchronous freebsd print, James K. Toothman
      • Re: synchronous freebsd print, Julian Elischer
    • Re: Security Flaw in Popular Disk Encryption Technologies, Diomidis Spinellis
  • Re: Security Flaw in Popular Disk Encryption Technologies, David E. Thiel
    • Re: Security Flaw in Popular Disk Encryption Technologies, Achim Patzner
      • Re: Security Flaw in Popular Disk Encryption Technologies, Uwe Doering
      • Re: Security Flaw in Popular Disk Encryption Technologies, Achim Patzner
      • Re: Security Flaw in Popular Disk Encryption Technologies, Uwe Doering
      • Re: Security Flaw in Popular Disk Encryption Technologies, Achim Patzner
      • Re: Security Flaw in Popular Disk Encryption Technologies, Atom Smasher
      • Re: Security Flaw in Popular Disk Encryption Technologies, Achim Patzner
      • Re: Security Flaw in Popular Disk Encryption Technologies, Martin Laabs
      • Re: Security Flaw in Popular Disk Encryption Technologies, Oliver Fromme
  • Re: Security Flaw in Popular Disk Encryption Technologies, Dimitry Andric
    • Re: Security Flaw in Popular Disk Encryption Technologies, Tim Clewlow
  • Re: Security Flaw in Popular Disk Encryption Technologies, Pawel Jakub Dawidek
• find -lname and -ilname implemented, M. Warner Losh
  • Re: find -lname and -ilname implemented, M. Warner Losh
    • Re: find -lname and -ilname implemented, Mike Meyer
      • Re: find -lname and -ilname implemented, M. Warner Losh
      • Re: find -lname and -ilname implemented, Mike Meyer
      • Re: find -lname and -ilname implemented, Warner Losh
      • Re: find -lname and -ilname implemented, Mike Meyer
      • Re: find -lname and -ilname implemented, Peter Jeremy
      • Re: find -lname and -ilname implemented, M. Warner Losh
      • Re: find -lname and -ilname implemented, Peter Jeremy
      • Re: find -lname and -ilname implemented, M. Warner Losh
      • Re: find -lname and -ilname implemented, M. Warner Losh
      • Re: find -lname and -ilname implemented, Mike Meyer
      • Re: find -lname and -ilname implemented, Julian Elischer
      • Re: find -lname and -ilname implemented, Mike Meyer
      • Re: find -lname and -ilname implemented, M. Warner Losh
      • Re: find -lname and -ilname implemented, David O'Brien
      • Re: find -lname and -ilname implemented, M. Warner Losh
      • Re: find -lname and -ilname implemented, Atom Smasher
      • Re: find -lname and -ilname implemented, Brooks Davis
      • Re: find -lname and -ilname implemented, Mike Meyer
      • Re: find -lname and -ilname implemented, Atom Smasher
      • Re: find -lname and -ilname implemented, Dag-Erling Smørgrav
    • Re: find -lname and -ilname implemented, Stanislav Sedov
      • Re: find -lname and -ilname implemented, M. Warner Losh
      • Re: find -lname and -ilname implemented, Joshua Isom
      • Re: find -lname and -ilname implemented, David O'Brien
      • Re: find -lname and -ilname implemented, Stanislav Sedov
  • <Possible follow-ups>
  • find -lname and -ilname implemented, Jonathan McKeown
    • Re: find -lname and -ilname implemented, Dag-Erling Smørgrav
    • Re: find -lname and -ilname implemented, M. Warner Losh
      • Re: find -lname and -ilname implemented, Jonathan McKeown
      • Re: find -lname and -ilname implemented, Giorgos Keramidas
      • Re: find -lname and -ilname implemented, Alex Zbyslaw
      • Re: find -lname and -ilname implemented, Jonathan McKeown
      • Re: find -lname and -ilname implemented, Peter Jeremy
      • Re: find -lname and -ilname implemented, David O'Brien
      • Re: find -lname and -ilname implemented, Julian Elischer
      • Re: find -lname and -ilname implemented, Giorgos Keramidas
• Winbond IO chip driver, David Duchscher
  • Re: Winbond IO chip driver, Jeremy Chadwick
• Start Fire nic card., Sharad Chandra
• usleep, Sharad Chandra
  • Re: usleep, Heiko Wundram (Beenic)
    • Re: usleep, KAYVEN RIESE
    • Re: usleep, Sharad Chandra
      • Re: usleep, Heiko Wundram (Beenic)
      • Re: usleep, Sharad Chandra
      • Re: usleep, Heiko Wundram (Beenic)
      • Re: usleep, Robert Woolley
      • Re: usleep, Heiko Wundram (Beenic)
      • Re: usleep, KAYVEN RIESE
  • Re: usleep, Andrew Pogrebennyk
    • Re: usleep, Peter Jeremy
• cool feature of dmesg.boot file, Bartosz Giza
  • Re: cool feature of dmesg.boot file, Bernd Walter
  • Re: cool feature of dmesg.boot file, Oliver Fromme
    • Re: cool feature of dmesg.boot file, Jeremy Chadwick
      • Re: memory not cleared on reboot (Was: cool feature of dmesg.boot file), Bert JW Regeer
      • Re: cool feature of dmesg.boot file, Oliver Fromme
      • Re: cool feature of dmesg.boot file, Jeremy Chadwick
      • Re: cool feature of dmesg.boot file, Rink Springer
      • Re: cool feature of dmesg.boot file, Oliver Fromme
      • Re: cool feature of dmesg.boot file, Jeremy Chadwick
      • Re: cool feature of dmesg.boot file, Rink Springer
      • Re: cool feature of dmesg.boot file, soralx
• ath0 will not associate, Michael W. Lucas
  • Re: ath0 will not associate, Sam Leffler
    • Re: ath0 will not associate, Michael W. Lucas
• OpenBSM & Jails, sam
  • OpenBSM & Jails, sam
  • Re: OpenBSM & Jails, Robert Watson
• OT: Stream structures in bzlib and zlib, Heiko Wundram (Beenic)
  • Re: OT: Stream structures in bzlib and zlib, Joerg Sonnenberger
  • Re: OT: Stream structures in bzlib and zlib, Tim Kientzle
• new syslogd option for adding local timestamp, Thomas Vogt
  • Re: new syslogd option for adding local timestamp, David Malone
    • Re: new syslogd option for adding local timestamp, Thomas Vogt
• [trouble] restart network & vlan`s interface, sam
  • Re: [trouble] restart network & vlan`s interface, Brooks Davis
    • Re: [trouble] restart network & vlan`s interface, sam
      • Re: [trouble] restart network & vlan`s interface, Brooks Davis
      • Re: [trouble] restart network & vlan`s interface, Zaphod Beeblebrox
• Re: cx_lowest and CPU usage, Andriy Gapon
  • Re: cx_lowest and CPU usage, Andriy Gapon
    • Re: cx_lowest and CPU usage, Andriy Gapon
      • PIIX4 chipset: (non-)exit from CPU states C2, C3 on interrupt, Andriy Gapon
      • Re: cx_lowest and CPU usage, Andriy Gapon
      • Re: cx_lowest and CPU usage, Rui Paulo
• /boot/loader graphics support & extensibility, Oliver Fromme
  • Re: /boot/loader graphics support & extensibility, Marcel Moolenaar
    • Re: /boot/loader graphics support & extensibility, Jonathan McKeown
    • Re: /boot/loader graphics support & extensibility, Oliver Fromme
      • Re: /boot/loader graphics support & extensibility, Marcel Moolenaar
      • Re: /boot/loader graphics support & extensibility, Oliver Fromme
      • Re: /boot/loader graphics support & extensibility, Marcel Moolenaar
      • Re: /boot/loader graphics support & extensibility, Joshua Isom
      • Re: /boot/loader graphics support & extensibility, Peter Jeremy
      • Re: /boot/loader graphics support & extensibility, Oliver Fromme
      • Re: /boot/loader graphics support & extensibility, Marcel Moolenaar
      • Re: /boot/loader graphics support & extensibility, Oliver Fromme
      • Re: /boot/loader graphics support & extensibility, Marcel Moolenaar
      • Re: /boot/loader graphics support & extensibility, Oliver Fromme
• Help debugging kernel dump?, Carey Jones
  • Re: Help debugging kernel dump?, Xin LI
• encrypted executables, Jerry Toung
  • Re: encrypted executables, Dimitry Andric
    • Re: encrypted executables, Giorgos Keramidas
    • Re: encrypted executables, Jerry Toung
      • Re: encrypted executables, Giorgos Keramidas
      • Re: encrypted executables, M. Warner Losh
      • Re: encrypted executables, Jeremie Le Hen
      • Re: encrypted executables, Thiago Damas
      • Re: encrypted executables, Mike Meyer
      • Re: encrypted executables, Tim Kientzle
      • Re: encrypted executables, ari edelkind
      • Re: encrypted executables, Joerg Sonnenberger
      • Re: encrypted executables, Bert JW Regeer
      • Re: encrypted executables, ari edelkind
      • Re: encrypted executables, Dag-Erling Smørgrav
      • Re: encrypted executables, Oliver Fromme
      • Re: encrypted executables, ari edelkind
      • Re: encrypted executables, Dag-Erling Smørgrav
      • Re: encrypted executables, Mike Meyer
      • Re: encrypted executables, Jerry Toung
• sched_ule: roundrobin_callout replacement ?, Andriy Gapon
• Re: Synaptics Xorg driver for FreeBSD/amd64, Giulio Ferro
  • Re: Synaptics Xorg driver for FreeBSD/amd64, Eygene Ryabinkin
    • Re: Synaptics Xorg driver for FreeBSD/amd64, Giulio Ferro
      • Re: Synaptics Xorg driver for FreeBSD/amd64, Eygene Ryabinkin
      • Re: Synaptics Xorg driver for FreeBSD/amd64, Giulio Ferro
      • Re: Synaptics Xorg driver for FreeBSD/amd64, Eygene Ryabinkin
      • Re: Synaptics Xorg driver for FreeBSD/amd64, Giulio Ferro
      • Re: Synaptics Xorg driver for FreeBSD/amd64, Eygene Ryabinkin
      • Re: Synaptics Xorg driver for FreeBSD/amd64, Norikatsu Shigemura
      • Re: Synaptics Xorg driver for FreeBSD/amd64, Eygene Ryabinkin
      • Re: Synaptics Xorg driver for FreeBSD/amd64, Norikatsu Shigemura
      • Re: Synaptics Xorg driver for FreeBSD/amd64, Eygene Ryabinkin
      • Re: Synaptics Xorg driver for FreeBSD/amd64, Eygene Ryabinkin
      • Re: Synaptics Xorg driver for FreeBSD/amd64, Giulio Ferro
      • Re: Synaptics Xorg driver for FreeBSD/amd64, Giulio Ferro
      • Re: Synaptics Xorg driver for FreeBSD/amd64, Eygene Ryabinkin
• pci support for /usr/share/example/drivers?, rmgls
  • Re: pci support for /usr/share/example/drivers?, Julian Elischer
• FreeBSD Status Reports for the Fourth Quarter of 2007, Brad Davis
• multiple interrupts between cli and sti, Andriy Gapon
  • Re: multiple interrupts between cli and sti, Erich Dollansky
    • Re: multiple interrupts between cli and sti, Andriy Gapon
• if_start() and sending packets problem, Tofig Suleymanov
  • Re: if_start() and sending packets problem, Max Laier
    • Re: if_start() and sending packets problem, Tofig Suleymanov
  • Re: if_start() and sending packets problem, Hans Petter Selasky
    • Re: if_start() and sending packets problem, Tofig Suleymanov
• cpu stats and another interrupt question, Andriy Gapon
  • Re: cpu stats and another interrupt question, Andriy Gapon
    • Re: cpu stats and another interrupt question, Girish Venkatachalam
• x86: sigaltstack problems, Sergei Trofimovich
  • Re: x86: sigaltstack problems, Rink Springer
  • Message not available
    • Re: x86: sigaltstack problems, Sergei Trofimovich
      • Re: x86: sigaltstack problems, Kostik Belousov
• licensing question APSL, Volker
  • Re: licensing question APSL, Brooks Davis
    • Re: licensing question APSL, Volker
      • Re: licensing question APSL, Brooks Davis
      • Re: licensing question APSL, Volker
      • Re: licensing question APSL, Brooks Davis
      • Re: licensing question APSL, Dag-Erling Smørgrav
      • Re: licensing question APSL, Robert Watson
      • Re: licensing question APSL, Dag-Erling Smørgrav
      • Re: licensing question APSL, Wilko Bulte
• valgrind or workalike on FreeBSD/amd64 7.0/8.0?, Xin LI
  • Re: valgrind or workalike on FreeBSD/amd64 7.0/8.0?, Christian S.J. Peron
    • Re: valgrind or workalike on FreeBSD/amd64 7.0/8.0?, Ulrich Spoerlein
      • Re: valgrind or workalike on FreeBSD/amd64 7.0/8.0?, Heiko Wundram (Beenic)
      • Re: valgrind or workalike on FreeBSD/amd64 7.0/8.0?, Dag-Erling Smørgrav
      • Re: valgrind or workalike on FreeBSD/amd64 7.0/8.0?, Heiko Wundram (Beenic)
• backtrace call comparison, Harald Servat
• gprof: weird output, Sergey Matveychuk
• abort?, Cihan Kömeçoğlu
  • Re: abort?, Remko Lodder
  • Re: abort?, Erik Trulsson
• DEVICE_POLLING IF_EM CPU usage, Daniel Dias Gonçalves
• quotactl returns double values, Ivan Georgiev
  • <Possible follow-ups>
  • quotactl returns double values, Ivan Georgiev
    • Re: quotactl returns double values, Daniel O'Connor
    • Re: quotactl returns double values, Tod McQuillin
      • Re: quotactl returns double values, Mike Pritchard
• USB Graphic Tablets, Chuck Robey
  • Re: USB Graphic Tablets, Julian H. Stacey
    • Re: USB Graphic Tablets, Chuck Robey
      • Re: USB Graphic Tablets, Julian H. Stacey
      • Re: USB Graphic Tablets, Chuck Robey
      • Re: USB Graphic Tablets, Julian H. Stacey
      • Re: USB Graphic Tablets, Chuck Robey
• NOR flash drivers, Andrew Duane
  • Re: NOR flash drivers, M. Warner Losh
• vfork?, Cihan Kömeçoğlu
• nvi strangeness, Dag-Erling Smørgrav
  • Re: nvi strangeness, Eygene Ryabinkin
    • Re: nvi strangeness, Eygene Ryabinkin
  • Re: nvi strangeness, Alex Zbyslaw
    • Re: nvi strangeness, Frank Mayhar
  • Re: nvi strangeness, Julian Elischer
  • Re: nvi strangeness, Peter Jeremy
• Question about http://torrents.freebsd.org:8080/index.html, Sean Bruno
  • Re: Question about http://torrents.freebsd.org:8080/index.html, Kris Kennaway
    • Re: Question about http://torrents.freebsd.org:8080/index.html, Sean Bruno
      • Re: Question about http://torrents.freebsd.org:8080/index.html, Lowell Gilbert
      • Re: Question about http://torrents.freebsd.org:8080/index.html, Sean Bruno
• retrive data from mbuf chain, Biks N
  • Re: retrive data from mbuf chain, Vlad GALU
    • Re: retrive data from mbuf chain, Julian Elischer
  • Re: retrive data from mbuf chain, Sam Leffler
    • Re: retrive data from mbuf chain, Biks N
      • RE: retrive data from mbuf chain, Singh, Vijay
    • Re: retrive data from mbuf chain, Biks N
      • Re: retrive data from mbuf chain, Biks N
  • Re: retrive data from mbuf chain, Robert Watson
• uma_zcreate and number of items to create, Pietro Cerutti
  • Re: uma_zcreate and number of items to create, Ed Schouten
    • Re: uma_zcreate and number of items to create, Pietro Cerutti
• Interesting development discipline model - PostgreSQL, Ivan Voras
• C99 & Posix, Pietro Cerutti
• Any interest in unused hardware being made available for remote developer use?, Wayne Sierke
  • Re: Any interest in unused hardware being made available for remote developer use?, Wayne Sierke
• fs/udf: vm pages "overlap" while reading large dir [patch], Andriy Gapon
  • Re: fs/udf: vm pages "overlap" while reading large dir [patch], Julian Elischer
    • Re: fs/udf: vm pages "overlap" while reading large dir [patch], Pav Lucistnik
      • Re: fs/udf: vm pages "overlap" while reading large dir [patch], Andriy Gapon
      • Re: fs/udf: vm pages "overlap" while reading large dir [patch], Pav Lucistnik
      • Re: fs/udf: vm pages "overlap" while reading large dir [patch], Andriy Gapon
      • Re: fs/udf: vm pages "overlap" while reading large dir [patch], Andriy Gapon
      • Re: fs/udf: vm pages "overlap" while reading large dir [patch], Pav Lucistnik
      • Re: fs/udf: vm pages "overlap" while reading large dir [patch], Andriy Gapon
      • Re: fs/udf: vm pages "overlap" while reading large dir [patch], Pav Lucistnik
      • Re: fs/udf: vm pages "overlap" while reading large dir [patch], Andriy Gapon
      • Re: fs/udf: vm pages "overlap" while reading large dir [patch], Scott Long
      • Re: fs/udf: vm pages "overlap" while reading large dir [patch], Scott Long
      • Re: fs/udf: vm pages "overlap" while reading large dir [patch], Scott Long
      • Re: fs/udf: vm pages "overlap" while reading large dir [patch], Andriy Gapon
      • Re: fs/udf: vm pages "overlap" while reading large dir [patch], Julian Elischer
    • Re: fs/udf: vm pages "overlap" while reading large dir [patch], Andriy Gapon
• fs/udf: vm pages "overlap" while reading large dir, Andriy Gapon
  • Re: fs/udf: vm pages "overlap" while reading large dir, Scott Long
    • Re: fs/udf: vm pages "overlap" while reading large dir, Andriy Gapon
      • Re: fs/udf: vm pages "overlap" while reading large dir, Andriy Gapon
      • Re: fs/udf: vm pages "overlap" while reading large dir, Andriy Gapon
      • Re: fs/udf: vm pages "overlap" while reading large dir, Poul-Henning Kamp
      • Re: fs/udf: vm pages "overlap" while reading large dir, Andriy Gapon
      • Re: fs/udf: vm pages "overlap" while reading large dir, Poul-Henning Kamp
      • Re: fs/udf: vm pages "overlap" while reading large dir, Andriy Gapon
      • Re: fs/udf: vm pages "overlap" while reading large dir, Bruce Evans
      • Re: fs/udf: vm pages "overlap" while reading large dir, Andriy Gapon
      • Re: fs/udf: vm pages "overlap" while reading large dir, Bruce Evans
      • Re: fs/udf: vm pages "overlap" while reading large dir, Andriy Gapon
      • device/disk vnode use by filesystems: vfs_bio, geom_vfs, Andriy Gapon
      • Re: fs/udf: vm pages "overlap" while reading large dir, Bruce Evans
• Re: Synaptics, Eygene Ryabinkin
  • Re: Synaptics, Eygene Ryabinkin
  • Re: Synaptics, Cristian KLEIN
    • Re: Synaptics, Eygene Ryabinkin
      • Re: Synaptics, Cristian KLEIN
      • Re: Synaptics, Eygene Ryabinkin
• SCHED_ULE trouble after ugrade 6.2-RELEASE -> 6.3-RELEASE, sam
  • Re: SCHED_ULE trouble after ugrade 6.2-RELEASE -> 6.3-RELEASE, Xin LI
    • Re: SCHED_ULE trouble after ugrade 6.2-RELEASE -> 6.3-RELEASE, gregoryd . freebsd
      • Re: SCHED_ULE trouble after ugrade 6.2-RELEASE -> 6.3-RELEASE, Xin LI
      • Re: SCHED_ULE trouble after ugrade 6.2-RELEASE -> 6.3-RELEASE, Kris Kennaway
      • Re: SCHED_ULE trouble after ugrade 6.2-RELEASE -> 6.3-RELEASE, gregoryd . freebsd
      • Re: SCHED_ULE trouble after ugrade 6.2-RELEASE -> 6.3-RELEASE, Kris Kennaway
• Netgraph, usleep, and moving to Kernel, Len Gross
• Re: gettimeofday() in hping, Kris Kennaway
  • Re: gettimeofday() in hping, Kris Kennaway
    • Re: gettimeofday() in hping, Kris Kennaway
      • Re: gettimeofday() in hping, Stefan Lambrev
      • Re: gettimeofday() in hping, Kris Kennaway
      • Re: gettimeofday() in hping, Ivan Voras
      • Re: gettimeofday() in hping, Stefan Lambrev
      • Message not available
      • Re: gettimeofday() in hping, Ivan Voras
      • Re: gettimeofday() in hping, Stefan Lambrev
      • Re: gettimeofday() in hping, Kris Kennaway
  • Re: gettimeofday() in hping, Sam Leffler
• getaddrinfo() spec doesn't match behaviour, Heiko Wundram (Beenic)
  • Re: getaddrinfo() spec doesn't match behaviour, Hajimu UMEMOTO
• sort(1) memory usage, Dag-Erling Smørgrav
  • Re: sort(1) memory usage, Ed Schouten
    • Re: sort(1) memory usage, Erik Trulsson
      • Re: sort(1) memory usage, Dag-Erling Smørgrav
      • Re: sort(1) memory usage, Dag-Erling Smørgrav
      • Re: sort(1) memory usage, Erik Trulsson
      • Re: sort(1) memory usage, Ed Schouten
      • Re: sort(1) memory usage, Jeremy Chadwick
      • Re: sort(1) memory usage, Dag-Erling Smørgrav
      • Re: sort(1) memory usage, David Schultz
      • Re: sort(1) memory usage, Dag-Erling Smørgrav
      • Re: sort(1) memory usage, Joerg Sonnenberger
      • Re: sort(1) memory usage, Dag-Erling Smørgrav
    • Re: sort(1) memory usage, Wayne Sierke
• /dev/dsp disappeared after power outage, Aryeh M. Friedman
  • Re: /dev/dsp disappeared after power outage, John Baldwin
    • Re: /dev/dsp disappeared after power outage, Bert JW Regeer
      • Re: /dev/dsp disappeared after power outage, Ulrich Spoerlein
      • Re: /dev/dsp disappeared after power outage, Bert JW Regeer
      • Re: /dev/dsp disappeared after power outage, Ariff Abdullah
      • Re: /dev/dsp disappeared after power outage, usleepless
      • Re: /dev/dsp disappeared after power outage, Jeremie Le Hen
• Re: FreeBSD Status Reports due: January 28th, 2008, Brad Davis
• Re: 'periodic daily' memory usage, Ulrich Spoerlein
  • Re: 'periodic daily' memory usage, Dag-Erling Smørgrav
    • Re: 'periodic daily' memory usage, Dag-Erling Smørgrav
• Re: Squeezing out some 70 bytes out of the boot2 loader, Adrian Penisoara
  • <Possible follow-ups>
  • Re: Squeezing out some 70 bytes out of the boot2 loader, Adrian Penisoara
  • Re: Squeezing out some 70 bytes out of the boot2 loader, Adrian Penisoara
    • Re: Squeezing out some 70 bytes out of the boot2 loader, Dylan Cochran
• vmstat layout, Dag-Erling Smørgrav
  • Re: vmstat layout, Ed Schouten
  • Re: vmstat layout, Garrett Cooper
    • Re: vmstat layout, Julian Elischer
      • Re: vmstat layout, Dag-Erling Smørgrav
      • Re: vmstat layout, Garrett Cooper
• Re: OT: getting the protocol family of a file descriptor, Peter Jeremy
  • <Possible follow-ups>
  • Re: OT: getting the protocol family of a file descriptor, Dag-Erling Smørgrav
    • Re: OT: getting the protocol family of a file descriptor, Heiko Wundram (Beenic)
• double start of scripts in /usr/local/etc/rc.d, sam
  • Re: double start of scripts in /usr/local/etc/rc.d, glen . j . barber
    • Re: double start of scripts in /usr/local/etc/rc.d, sam
      • Re: double start of scripts in /usr/local/etc/rc.d, Julian H. Stacey
  • Re: double start of scripts in /usr/local/etc/rc.d, Julian H. Stacey
    • Re: double start of scripts in /usr/local/etc/rc.d, sam
  • Re: double start of scripts in /usr/local/etc/rc.d, Peter Jeremy
    • Re: double start of scripts in /usr/local/etc/rc.d, sam
      • Re: double start of scripts in /usr/local/etc/rc.d, Tom Evans
      • Re: double start of scripts in /usr/local/etc/rc.d, Eygene Ryabinkin
      • Re: double start of scripts in /usr/local/etc/rc.d, sam
      • Re: double start of scripts in /usr/local/etc/rc.d, Eygene Ryabinkin
      • Re: double start of scripts in /usr/local/etc/rc.d, sam
      • Re: double start of scripts in /usr/local/etc/rc.d, Eygene Ryabinkin
  • RE: double start of scripts in /usr/local/etc/rc.d, Łukasz Wąsikowski
• Re: [OT] Q: what would you choose for a VCS today, Stefan Sperling
  • Re: [OT] Q: what would you choose for a VCS today, Giorgos Keramidas
    • Re: [OT] Q: what would you choose for a VCS today, Giorgos Keramidas
    • Re: [OT] Q: what would you choose for a VCS today, Stefan Sperling
  • <Possible follow-ups>
  • Re: [OT] Q: what would you choose for a VCS today, Stefan Sperling
  • Re: [OT] Q: what would you choose for a VCS today, Adrian Penisoara
    • Re: [OT] Q: what would you choose for a VCS today, Mike Meyer
      • Re: [OT] Q: what would you choose for a VCS today, Ollivier Robert
      • Re: [OT] Q: what would you choose for a VCS today, Aryeh M. Friedman
      • Re: [OT] Q: what would you choose for a VCS today, Ollivier Robert
      • Re: [OT] Q: what would you choose for a VCS today, Aryeh M. Friedman
    • Re: [OT] Q: what would you choose for a VCS today, OutBackDingo
      • Re: [OT] Q: what would you choose for a VCS today, Stefan Sperling
      • Re: [OT] Q: what would you choose for a VCS today, Julian Elischer
• Memory allocation performance, Alexander Motin
  • Re: Memory allocation performance, Alexander Motin
    • Re: Memory allocation performance, Kris Kennaway
      • Re: Memory allocation performance, Alexander Motin
      • Re: Memory allocation performance, Kris Kennaway
  • Re: Memory allocation performance, Kris Kennaway
  • Re: Memory allocation performance, Julian Elischer
    • Re: Memory allocation performance, Alexander Motin
      • Re: Memory allocation performance, Julian Elischer
      • Re: Memory allocation performance, Robert Watson
      • Re: Memory allocation performance, Alexander Motin
      • Re: Memory allocation performance, Bruce Evans
      • Re: Memory allocation performance, Joseph Koshy
      • Re: Memory allocation performance, Alexander Motin
      • Re: Memory allocation performance, Joseph Koshy
      • Re: Memory allocation performance, Alexander Motin
      • Re: Memory allocation performance, Robert Watson
      • Re: Memory allocation performance, Alexander Motin
      • Re: Memory allocation performance, Kris Kennaway
      • Re: Memory allocation performance, Robert Watson
      • Re: Memory allocation performance, Alexander Motin
      • Re: Memory allocation performance, Robert Watson
      • Re: Memory allocation performance, Julian Elischer
      • Re: Memory allocation performance, Dag-Erling Smørgrav
      • Re: Memory allocation performance, Julian Elischer
      • Re: Memory allocation performance, Dag-Erling Smørgrav
      • Re: Memory allocation performance, Alexander Motin
      • Re: Memory allocation performance, Bruce Evans
      • Re: Memory allocation performance, Max Laier
      • Re: Memory allocation performance, Peter Jeremy
      • Re: Memory allocation performance, Alexander Motin
      • Re: Memory allocation performance, Peter Jeremy

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