freebsd-hackers

• Thread Index

---

• Re: strange behaviour with /sbin/init and serial console
  • From: Jeremy Chadwick
• Re: includes, configure, /usr/lib vs. /usr/local/lib, and linux coders
  • From: Tijl Coosemans
• Re: includes, configure, /usr/lib vs. /usr/local/lib, and linux coders
  • From: Daniel Eischen
• Re: strange behaviour with /sbin/init and serial console
  • From: Scott Long
• Re: strange behaviour with /sbin/init and serial console
  • From: Ed Schouten
• Re: includes, configure, /usr/lib vs. /usr/local/lib, and linux coders
  • From: Nate Eldredge
• Re: includes, configure, /usr/lib vs. /usr/local/lib, and linux coders
  • From: Peter Jeremy
• Re: includes, configure, /usr/lib vs. /usr/local/lib, and linux coders
  • From: Steve Franks
• Re: strange behaviour with /sbin/init and serial console
  • From: Ed Schouten
• includes, configure, /usr/lib vs. /usr/local/lib, and linux coders
  • From: Steve Franks
• Re: open(2) and O_NOATIME
  • From: Xin LI
• Re: strange behaviour with /sbin/init and serial console
  • From: Thierry Herbelot
• Re: strange behaviour with /sbin/init and serial console
  • From: Jeremy Chadwick
• Re: memtest86+ can not link: binutils issue?
  • From: Nate Eldredge
• strange behaviour with /sbin/init and serial console
  • From: Thierry Herbelot
• Re: open(2) and O_NOATIME
  • From: Jilles Tjoelker
• Re: open(2) and O_NOATIME
  • From: Paul Schenkeveld
• Re: memtest86+ can not link: binutils issue?
  • From: Andriy Gapon
• Re: Is there virtualbox ports?
  • From: Lars Engels
• Re: open(2) and O_NOATIME
  • From: Igor Mozolevsky
• Re: Is there virtualbox ports?
  • From: Carlos A. M. dos Santos
• Is there virtualbox ports?
  • From: Boern
• Re: open(2) and O_NOATIME
  • From: Jeremy Chadwick
• Re: open(2) and O_NOATIME
  • From: Joerg Sonnenberger
• Re: open(2) and O_NOATIME
  • From: Xin LI
• Re: memtest86+ can not link: binutils issue?
  • From: Peter Jeremy
• memtest86+ can not link: binutils issue?
  • From: Andriy Gapon
• Re: process hibernation and process descriptor table
  • From: jT
• Re: crash at in_pcb.c
  • From: Jerry Toung
• open(2) and O_NOATIME
  • From: Jeremy Chadwick
• Re: process hibernation and process descriptor table
  • From: Dag-Erling Smørgrav
• process hibernation and process descriptor table
  • From: aniket pansare
• 7.0R && amd does not unmount USB-based UFS
  • From: Matthias Apitz
• Re: Usage of "files" for config
  • From: Dag-Erling Smørgrav
• Re: crash at in_pcb.c
  • From: pluknet
• Re: neophyte: tcsetattr() gives 22 error in i386, not in amd64?
  • From: Steve Franks
• Re: crash at in_pcb.c
  • From: Kip Macy
• Re: crash at in_pcb.c
  • From: Jerry Toung
• crash at in_pcb.c
  • From: Jerry Toung
• RTLD changes for non-native system (was: Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit ?binaries?)
  • From: Alexander Leidinger
• Re: Usage of "files" for config
  • From: John Baldwin
• Re: Usage of "files" for config
  • From: Srinivas
• Re: [Testers wanted] /dev/console cleanups
  • From: Ed Schouten
• Re: Usage of "files" for config
  • From: Eygene Ryabinkin
• Re: [Testers wanted] /dev/console cleanups
  • From: Carlos A. M. dos Santos
• Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit ?binaries?
  • From: Daniel O'Connor
• Usage of "files" for config
  • From: Srinivas
• Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit ?binaries?
  • From: M. Warner Losh
• Re: libusb for linux-emulation
  • From: M. Warner Losh
• Re: libusb for linux-emulation
  • From: Oliver Fromme
• Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit ?binaries?
  • From: Oliver Fromme
• [Testers wanted] /dev/console cleanups
  • From: Ed Schouten
• Re: linux-libusb done
  • From: Roman Divacky
• linux-libusb done
  • From: Martin Laabs
• problems obtaining kernel dump
  • From: Roman Bogorodskiy
• Re: question about sb->st_blksize in src/sys/kern/vfs_vnops.c
  • From: Bruce Evans
• Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
  • From: Alexander Kabaev
• Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
  • From: Alexander Sack
• Re: Severe DNS Problems, 6.2-RELEASE, BIND 9.5.2
  • From: george+freebsd
• Re: question about sb->st_blksize in src/sys/kern/vfs_vnops.c
  • From: Thierry Herbelot
• Re: neophyte: tcsetattr() gives 22 error in i386, not in amd64?
  • From: en0f
• Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
  • From: Alexander Kabaev
• Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
  • From: Alexander Sack
• Re: neophyte: tcsetattr() gives 22 error in i386, not in amd64?
  • From: N.J. Mann
• Re: neophyte: tcsetattr() gives 22 error in i386, not in amd64?
  • From: N.J. Mann
• Re: zfs & waiting on zio->io_cv
  • From: Danny Braniss
• Re: neophyte: tcsetattr() gives 22 error in i386, not in amd64?
  • From: Jeremy Chadwick
• Re: zfs & waiting on zio->io_cv
  • From: Jeremy Chadwick
• Re: neophyte: tcsetattr() gives 22 error in i386, not in amd64?
  • From: en0f
• Re: neophyte: tcsetattr() gives 22 error in i386, not in amd64?
  • From: Jeremy Chadwick
• Re: neophyte: tcsetattr() gives 22 error in i386, not in amd64?
  • From: en0f
• Re: zfs & waiting on zio->io_cv
  • From: Danny Braniss
• Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
  • From: Daniel O'Connor
• Re: libusb for linux-emulation
  • From: Daniel O'Connor
• Re: Severe DNS Problems, 6.2-RELEASE, BIND 9.5.2
  • From: george+freebsd
• Re: neophyte: tcsetattr() gives 22 error in i386, not in amd64?
  • From: Nate Eldredge
• neophyte: tcsetattr() gives 22 error in i386, not in amd64?
  • From: Steve Franks
• Re: libusb for linux-emulation
  • From: Hans Petter Selasky
• Re: libusb for linux-emulation
  • From: Martin Laabs
• Re: libusb for linux-emulation
  • From: Hans Petter Selasky
• libusb for linux-emulation
  • From: Martin Laabs
• Re: Severe DNS Problems, 6.2-RELEASE, BIND 9.5.2
  • From: Matthew Seaman
• question about sb->st_blksize in src/sys/kern/vfs_vnops.c
  • From: Thierry Herbelot
• Re: zfs & waiting on zio->io_cv
  • From: Dan Nelson
• Severe DNS Problems, 6.2-RELEASE, BIND 9.5.2
  • From: george+freebsd
• Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
  • From: Peter Jeremy
• Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
  • From: Wojciech Puchar
• zfs & waiting on zio->io_cv
  • From: Danny Braniss
• Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
  • From: Dan Nelson
• Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
  • From: Nate Eldredge
• Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
  • From: Alexander Kabaev
• Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
  • From: Alexander Sack
• Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
  • From: Alexander Sack
• Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
  • From: Alexander Sack
• Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
  • From: Dag-Erling Smørgrav
• Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
  • From: Dag-Erling Smørgrav
• Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
  • From: Alexander Sack
• sched_thread_priority in ULE 8.0
  • From: Murty, Ravi
• Re: Laptop suggestions?
  • From: Dag-Erling Smørgrav
• Re: Laptop suggestions?
  • From: Dag-Erling Smørgrav
• Re: Laptop suggestions?
  • From: Gary Kline
• Re: Laptop suggestions?
  • From: Jeremy Chadwick
• Re: Laptop suggestions?
  • From: Nate Eldredge
• Re: Laptop suggestions?
  • From: Gary Kline
• Re: Laptop suggestions?
  • From: Dag-Erling Smørgrav
• Re: Laptop suggestions?
  • From: martinko
• Re: 'libc_r: enter/leave_cancellation_point()
  • From: Alfred Perlstein
• 'libc_r: enter/leave_cancellation_point()
  • From: Norbert Koch
• Re: Pipes, cat buffer size
  • From: Mel
• Re: Pipes, cat buffer size
  • From: Tim Kientzle
• Re: Pipes, cat buffer size
  • From: Dan Nelson
• Re: Pipes, cat buffer size
  • From: Ivan Voras
• gprocessor Error
  • From: Robert Richards
• Re: Pipes, cat buffer size
  • From: Dan Nelson
• Re: Pipes, cat buffer size
  • From: Ivan Voras
• Re: Pipes, cat buffer size
  • From: Dan Nelson
• Pipes, cat buffer size
  • From: Ivan Voras
• Re: conf/128030: [request] Isn't it time to enable IPsec in GENERIC?
  • From: Sam Leffler
• Re: conf/128030: [request] Isn't it time to enable IPsec in GENERIC?
  • From: Max Laier
• Re: [Info required] PC Architecture
  • From: Alfred Perlstein
• Re: how determine all possible drivers for my system
  • From: Freddie Cash
• Re: FreeBSD and ISCSI, Strange Problem
  • From: Dan Nelson
• how determine all possible drivers for my system
  • From: Oleg
• Re: FreeBSD and ISCSI, Strange Problem
  • From: Daniel Dias Gonçalves
• Re: lock test from sh script
  • From: Daniel O'Connor
• Re: lock test from sh script
  • From: Pieter de Goeje
• Re: lock test from sh script
  • From: Dag-Erling Smørgrav
• lock test from sh script
  • From: Igor Pokrovsky
• Re: smbfs hang
  • From: Alex Zbyslaw
• new mailing list for xen
  • From: Kip Macy
• Re: indicating a debug image
  • From: Nate Eldredge
• indicating a debug image
  • From: Chuck Robey
• Re: [Doubt] Can a PCI device communicate with another PCI or other
  • From: Steve Watt
• Re: [Doubt] Can a PCI device communicate with another PCI or other device?
  • From: Srinivas
• Re: smbfs hang
  • From: Attilio Rao
• smbfs hang
  • From: Chris Coleman
• Re: need help with vbox
  • From: Jeremy Messenger
• Re: [Info required] PC Architecture
  • From: Ivan Voras
• Re: need help with vbox
  • From: Ivan Voras
• Re: [Info required] PC Architecture
  • From: Jeroen Ruigrok van der Werven
• [Info required] PC Architecture
  • From: Srinivas
• RE: need help with vbox
  • From: Desmond Chapman
• RE: need help with vbox
  • From: Desmond Chapman
• Re: need help with vbox
  • From: Ivan Voras
• Re: need help with vbox
  • From: Bruce Cran
• Re: need help with vbox
  • From: Ivan Voras
• need help with vbox
  • From: Desmond Chapman
• Re: Call function on sysctl value change
  • From: Matthew Jakeman
• Re: Call function on sysctl value change
  • From: Oliver Fromme
• Re: Call function on sysctl value change
  • From: Dag-Erling Smørgrav
• Re: Call function on sysctl value change
  • From: Dag-Erling Smørgrav
• Invitation to connect on LinkedIn
  • From: Otávio Fernandes
• Call function on sysctl value change
  • From: Matthew Jakeman
• Re: tracing pf code
  • From: alan yang
• tracing pf code
  • From: alan yang
• Re: tracing pf code
  • From: Max Laier
• Re: [Doubt] Can a PCI device communicate with another PCI or other device?
  • From: Pegasus Mc Cleaft
• [Doubt] Can a PCI device communicate with another PCI or other device?
  • From: Srinivas
• Re: What is the time between 2 mi_switches in freebsd.
  • From: John Baldwin
• Re: ZFS boot
  • From: Michel Talon
• Re: Is it possible to recover from SEGV?
  • From: Romain Tartière
• Re: ZFS boot
  • From: Jeremy Chadwick
• Re: ZFS boot
  • From: Doug Rabson
• Re: Is it possible to recover from SEGV?
  • From: Nate Eldredge
• Is it possible to recover from SEGV?
  • From: Yuri
• Re: ZFS boot
  • From: Mike Meyer
• Re: continuous backup solution for FreeBSD
  • From: Mike Meyer
• Re: TIME WARP! Re: HEADS UP: GCC 4.2.0 is coming
  • From: Garrett Cooper
• Re: ZFS boot
  • From: Nate Eldredge
• Re: ZFS boot
  • From: Pegasus Mc Cleaft
• Re: ZFS boot
  • From: Xin LI
• Re: ZFS boot
  • From: Freddie Cash
• Re: ZFS boot
  • From: Nate Eldredge
• Re: ZFS boot
  • From: Freddie Cash
• Re: ZFS boot
  • From: Matthew Dillon
• ZFS boot
  • From: Danny Braniss
• Re: continuous backup solution for FreeBSD
  • From: Matthew Dillon
• Re: continuous backup solution for FreeBSD
  • From: Doug Rabson
• Re: continuous backup solution for FreeBSD
  • From: Jeremy Chadwick
• Re: VirtualBox looks for FreeBSD developer
  • From: Edwin Groothuis
• Re: continuous backup solution for FreeBSD
  • From: Danny Braniss
• Re: continuous backup solution for FreeBSD
  • From: Danny Braniss
• Re: continuous backup solution for FreeBSD
  • From: Jeremy Chadwick
• Re: HPC with ULE vs 4BSD
  • From: Jeremy Chadwick
• HPC with ULE vs 4BSD
  • From: Steve Kargl
• Re: setkey panic freebsd7
  • From: alan yang
• Re: VirtualBox looks for FreeBSD developer
  • From: Dmitry Marakasov
• Re: continuous backup solution for FreeBSD
  • From: Mike Meyer
• Re: continuous backup solution for FreeBSD
  • From: Evren Yurtesen
• Re: continuous backup solution for FreeBSD
  • From: Mike Meyer
• Re: continuous backup solution for FreeBSD
  • From: Jeremy Chadwick
• Re: continuous backup solution for FreeBSD
  • From: Mike Meyer
• Re: continuous backup solution for FreeBSD
  • From: Jeremy Chadwick
• Re: continuous backup solution for FreeBSD
  • From: Evren Yurtesen
• Debugging modify-after-free issue
  • From: Xin LI
• Re: setkey panic freebsd7
  • From: alan yang
• Re: continuous backup solution for FreeBSD
  • From: Matthew Dillon
• Re: continuous backup solution for FreeBSD
  • From: Mike Meyer
• Re: continuous backup solution for FreeBSD
  • From: yurtesen
• Re: continuous backup solution for FreeBSD
  • From: Zaphod Beeblebrox
• Re: FreeBSD support for HP DL180/G5
  • From: Subhro
• Re: setkey panic freebsd7
  • From: VANHULLEBUS Yvan
• FreeBSD support for HP DL180/G5
  • From: Josef Grosch
• Re: continuous backup solution for FreeBSD
  • From: Matthew Dillon
• Re: request for testers - xen support for domU in head
  • From: Willem Jan Withagen
• setkey panic freebsd7
  • From: alan yang
• Re: continuous backup solution for FreeBSD
  • From: Oliver Fromme
• Re: continuous backup solution for FreeBSD
  • From: Oliver Fromme
• Re: Sockstress
  • From: Oliver Fromme
• Sockstress
  • From: Lukasz Jaroszewski
• Re: strftime's %c warning?
  • From: Marc Olzheim
• Re: strftime's %c warning?
  • From: Ivan Voras
• Re: continuous backup solution for FreeBSD
  • From: Bruce R. Montague
• Re: strftime's %c warning?
  • From: Sean C. Farley
• Re: continuous backup solution for FreeBSD
  • From: yurtesen
• Re: continuous backup solution for FreeBSD
  • From: yurtesen
• Re: continuous backup solution for FreeBSD
  • From: Bakul Shah
• Re: continuous backup solution for FreeBSD
  • From: Bakul Shah
• Re: What is the time between 2 mi_switches in freebsd.
  • From: John Baldwin
• Re: What is the time between 2 mi_switches in freebsd.
  • From: Dag-Erling Smørgrav
• Re: continuous backup solution for FreeBSD
  • From: Dag-Erling Smørgrav
• strftime's %c warning?
  • From: Ivan Voras
• Re: continuous backup solution for FreeBSD
  • From: Dag-Erling Smørgrav
• Re: continuous backup solution for FreeBSD
  • From: Dag-Erling Smørgrav
• Re: continuous backup solution for FreeBSD
  • From: Dag-Erling Smørgrav
• Re: What is the time between 2 mi_switches in freebsd.
  • From: Dag-Erling Smørgrav
• Re: continuous backup solution for FreeBSD
  • From: Zaphod Beeblebrox
• Re: What is the time between 2 mi_switches in freebsd.
  • From: John Baldwin
• Re: continuous backup solution for FreeBSD
  • From: Bakul Shah
• Re: continuous backup solution for FreeBSD
  • From: Nate Eldredge
• Re: continuous backup solution for FreeBSD
  • From: Evren Yurtesen
• Re: continuous backup solution for FreeBSD
  • From: Evren Yurtesen
• Re: continuous backup solution for FreeBSD
  • From: Evren Yurtesen
• Re: What is the time between 2 mi_switches in freebsd.
  • From: Jeroen Ruigrok van der Werven
• Re: continuous backup solution for FreeBSD
  • From: Zaphod Beeblebrox
• Re: continuous backup solution for FreeBSD
  • From: Zaphod Beeblebrox
• Re: What is the time between 2 mi_switches in freebsd.
  • From: ushasri tummala
• Re: What is the time between 2 mi_switches in freebsd.
  • From: Dag-Erling Smørgrav
• Re: llvm/clang early test
  • From: Roman Divacky
• Re: continuous backup solution for FreeBSD
  • From: Outback Dingo
• llvm/clang early test
  • From: Volodymyr Kostyrko
• Re: HEADS UP: GCC 4.2.0 is coming
  • From: Vladimir Grebenschikov
• TIME WARP! Re: HEADS UP: GCC 4.2.0 is coming
  • From: Peter Wemm
• Re: HEADS UP: GCC 4.2.0 is coming
  • From: O. Hartmann
• Re: continuous backup solution for FreeBSD
  • From: Oliver Fromme
• Re: HEADS UP: GCC 4.2.0 is coming
  • From: Erik Trulsson
• Re: HEADS UP: GCC 4.2.0 is coming
  • From: Eygene Ryabinkin
• Re: continuous backup solution for FreeBSD
  • From: Dag-Erling Smørgrav
• Re: continuous backup solution for FreeBSD
  • From: Dag-Erling Smørgrav
• What is the time between 2 mi_switches in freebsd.
  • From: ushasri tummala
• Re: kgdb debugging
  • From: Julian Elischer
• Re: kgdb debugging
  • From: Navdeep Parhar
• Re: kgdb debugging
  • From: alan yang
• Re: continuous backup solution for FreeBSD
  • From: Zaphod Beeblebrox
• Re: continuous backup solution for FreeBSD
  • From: Bakul Shah
• Re: continuous backup solution for FreeBSD
  • From: Zaphod Beeblebrox
• Re: continuous backup solution for FreeBSD
  • From: Zaphod Beeblebrox
• Re: continuous backup solution for FreeBSD
  • From: Shaun Amott
• Re: sleep is not working to avoid starvation among threads of same priority
  • From: Jille Timmermans
• sleep is not working to avoid starvation among threads of same priority
  • From: Ramachandran Sathyanarayanan
• sleep is not working to avoid starvation among threads of same priority
  • From: Ramachandran Sathyanarayanan
• Re: continuous backup solution for FreeBSD
  • From: Evren Yurtesen
• Re: continuous backup solution for FreeBSD
  • From: Dag-Erling Smørgrav
• Re: continuous backup solution for FreeBSD
  • From: George Hartzell
• Re: continuous backup solution for FreeBSD
  • From: Zaphod Beeblebrox
• Re: kgdb debugging
  • From: Pietro Cerutti
• Re: continuous backup solution for FreeBSD
  • From: Evren Yurtesen
• kgdb debugging
  • From: alan yang
• Re: continuous backup solution for FreeBSD
  • From: Mike Meyer
• Re: continuous backup solution for FreeBSD
  • From: Zaphod Beeblebrox
• Re: continuous backup solution for FreeBSD
  • From: Evren Yurtesen
• Re: continuous backup solution for FreeBSD
  • From: Evren Yurtesen
• Re: continuous backup solution for FreeBSD
  • From: George Hartzell
• Re: ports/126853: ports-mgmt/portaudit: speed up audit of installed packages
  • From: Eygene Ryabinkin
• Re: ports/126853: ports-mgmt/portaudit: speed up audit of installed packages
  • From: Eygene Ryabinkin
• Re: continuous backup solution for FreeBSD
  • From: Evren Yurtesen
• Re: continuous backup solution for FreeBSD
  • From: Evren Yurtesen
• Re: continuous backup solution for FreeBSD
  • From: Bakul Shah
• Re: continuous backup solution for FreeBSD
  • From: Volker
• Re: touch screen recommendation?
  • From: Volker
• Re: continuous backup solution for FreeBSD
  • From: Zaphod Beeblebrox
• Re: bad NFS/UDP performance
  • From: Danny Braniss
• Re: continuous backup solution for FreeBSD
  • From: Vlad GALU
• Re: continuous backup solution for FreeBSD
  • From: Evren Yurtesen
• Re: ports/126853: ports-mgmt/portaudit: speed up audit of installed packages
  • From: Eygene Ryabinkin
• Re: ports/126853: ports-mgmt/portaudit: speed up audit of installed packages
  • From: Mel
• Re: continuous backup solution for FreeBSD
  • From: Bob Bishop
• Re: ports/126853: ports-mgmt/portaudit: speed up audit of installed packages
  • From: Eygene Ryabinkin
• continuous backup solution for FreeBSD
  • From: Evren Yurtesen
• Re: ports/126853: ports-mgmt/portaudit: speed up audit of installed packages
  • From: Miroslav Lachman
• RE: i386/127710: My driver PCI probe is not calledformycorrespondingdevice ID and Vendor ID
  • From: Bagavathy Kumar Mahendran
• RE: i386/127710: My driver PCI probe is not calledformycorrespondingdevice ID and Vendor ID
  • From: Bagavathy Kumar Mahendran
• RE: i386/127710: My driver PCI probe is not called formycorrespondingdevice ID and Vendor ID
  • From: Bagavathy Kumar Mahendran
• RE: i386/127710: My driver PCI probe is not called for mycorrespondingdevice ID and Vendor ID
  • From: Bagavathy Kumar Mahendran
• Re: ports/126853: ports-mgmt/portaudit: speed up audit of installed packages
  • From: Mel
• Re: ports/126853: ports-mgmt/portaudit: speed up audit of installed packages
  • From: Eygene Ryabinkin
• Re: ports/126853: ports-mgmt/portaudit: speed up audit of installed packages
  • From: Eygene Ryabinkin
• Re: ports/126853: ports-mgmt/portaudit: speed up audit of installed packages
  • From: Mel
• Re: i386/127710: My driver PCI probe is not called formycorrespondingdevice ID and Vendor ID
  • From: Warner Losh
• Re: i386/127710: My driver PCI probe is not called for mycorrespondingdevice ID and Vendor ID
  • From: Warner Losh
• Re: ports/126853: ports-mgmt/portaudit: speed up audit of installed packages
  • From: Eygene Ryabinkin
• FreeBSD Status Reports due October 19th, 2008
  • From: Brad Davis
• Re: bad NFS/UDP performance
  • From: Robert Watson
• Re: ports/126853: ports-mgmt/portaudit: speed up audit of installed packages
  • From: Eygene Ryabinkin
• Re: ports/126853: ports-mgmt/portaudit: speed up audit of installed packages
  • From: Eygene Ryabinkin
• touch screen recommendation?
  • From: Chuck Robey
• Re: bad NFS/UDP performance
  • From: Danny Braniss
• Re: Major SMP problems with lstat/namei
  • From: Jeff Wheelhouse
• Re: UCLogic tablets
  • From: Chuck Robey
• UCLogic tablets
  • From: Chuck Robey
• Re: bad NFS/UDP performance
  • From: Robert Watson
• Re: bad NFS/UDP performance
  • From: Danny Braniss
• options in configuration file
  • From: Srinivas
• RE: i386/127710: My driver PCI probe is not called for mycorrespondingdevice ID and Vendor ID
  • From: Bagavathy Kumar Mahendran
• RE: FW: i386/127710: My driver PCI probe is not called for my correspondingdevice ID and Vendor ID
  • From: Bagavathy Kumar Mahendran
• Re: bad NFS/UDP performance
  • From: Robert Watson
• Re: bad NFS/UDP performance
  • From: Danny Braniss
• Re: bad NFS/UDP performance
  • From: Danny Braniss
• Re: bad NFS/UDP performance
  • From: Robert Watson
• Re: bad NFS/UDP performance
  • From: Danny Braniss
• Re: bad NFS/UDP performance
  • From: Robert Watson
• Re: bad NFS/UDP performance
  • From: Danny Braniss
• Re: i386/127710: My driver PCI probe is not called for my correspondingdevice ID and Vendor ID
  • From: M. Warner Losh
• Re: Re: Hardware support for AMD Geode CS5536 audio?
  • From: Alec Kloss
• Re: Re: Hardware support for AMD Geode CS5536 audio?
  • From: Alexander Leidinger
• Re: Hardware support for AMD Geode CS5536 audio?
  • From: Joel Dahl
• Re: valgrind on FreeBSD 7
  • From: Jeroen Ruigrok van der Werven
• Re: valgrind on FreeBSD 7
  • From: Yuri
• Re: Re: Hardware support for AMD Geode CS5536 audio?
  • From: ancelgray
• Re: Re: Hardware support for AMD Geode CS5536 audio?
  • From: ancelgray
• Re: SSH Brute Force attempts
  • From: Eitan Adler
• Sched_ule.c - 8.0
  • From: Murty, Ravi
• Re: Major SMP problems with lstat/namei
  • From: John Baldwin
• Re: svn rev. number
  • From: Artis Caune
• Re: FW: i386/127710: My driver PCI probe is not called for my correspondingdevice ID and Vendor ID
  • From: John Baldwin
• RE: i386/127710: My driver PCI probe is not called for my correspondingdevice ID and Vendor ID
  • From: Bagavathy Kumar Mahendran
• FW: i386/127710: My driver PCI probe is not called for my correspondingdevice ID and Vendor ID
  • From: Bagavathy Kumar Mahendran
• Re: svn rev. number
  • From: Danny Braniss
• Re: svn rev. number
  • From: Max Laier
• Re: svn rev. number
  • From: Rui Paulo
• svn rev. number
  • From: Danny Braniss
• Re: ATA Security patch to atacontrol
  • From: Daniel Roethlisberger
• [powerd] Adding different adaptive-mode settings for each power source
  • From: gelraen

• Security
• UNIX
• Linux
• Coding
• Usenet

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

unix.derkeiler.com  > Mailing-Lists  > FreeBSD  > hackers  > 2008-10