freebsd-hackers  

Messages by Thread

• • Re: Call fo comments - raising vfs.ufs.dirhash_reclaimage? RW
  • Re: Call fo comments - raising vfs.ufs.dirhash_reclaimage? Davide Italiano
  • Re: Call fo comments - raising vfs.ufs.dirhash_reclaimage? RW
  • Re: Call fo comments - raising vfs.ufs.dirhash_reclaimage? John Baldwin
  • Re: Call fo comments - raising vfs.ufs.dirhash_reclaimage? Davide Italiano
• Re: [kde-freebsd] virtualbox file dialog problem Andriy Gapon
  • Re: [kde-freebsd] virtualbox file dialog problem Andriy Gapon
  • Re: [kde-freebsd] virtualbox file dialog problem Jilles Tjoelker
• Torture test for atomics and userland locking? Tim Kientzle
• Re: svn commit: r254853 - head/sys/dev/drm2 Adrian Chadd
  • Re: svn commit: r254853 - head/sys/dev/drm2 Jean-Sébastien Pédron
• mpx on laptop produces pointer but does not show usb mouse Super Bisquit
• About CPU cores numbering an processor affinity Dmitry Sivachenko
  • Re: About CPU cores numbering an processor affinity Ivan Voras
  • Re: About CPU cores numbering an processor affinity John Baldwin
• weekly periodic security status Jeremie Le Hen
  • Re: weekly periodic security status Darren Pilgrim
  • Re: weekly periodic security status Royce Williams
  • Re: weekly periodic security status Jeremie Le Hen
  • Re: weekly periodic security status Jeremie Le Hen
  • Re: weekly periodic security status Royce Williams
  • Re: weekly periodic security status Jeremie Le Hen
  • Re: weekly periodic security status James Gosnell
  • Re: weekly periodic security status RW
  • Re: weekly periodic security status Jeremie Le Hen
  • Re: weekly periodic security status Darren Pilgrim
  • Re: weekly periodic security status Jeremie Le Hen
  • Re: weekly periodic security status Darren Pilgrim
  • Re: weekly periodic security status Jeremie Le Hen
  • Re: weekly periodic security status Darren Pilgrim
  • Re: weekly periodic security status Jeremie Le Hen
  • Re: weekly periodic security status Julian Elischer
  • Re: weekly periodic security status RW
  • Re: weekly periodic security status Jeremie Le Hen
  • Re: weekly periodic security status Eitan Adler
  • Re: weekly periodic security status Jeremie Le Hen
  • Re: weekly periodic security status Eitan Adler
  • Re: weekly periodic security status Jeremie Le Hen
• ps_strings Carlos Jacobo Puga Medina
  • Re: ps_strings Super Bisquit
  • Re: ps_strings Fernando Apesteguía
  • Re: ps_strings Chris Torek
  • Re: ps_strings Konstantin Belousov
  • Re: ps_strings Chris Torek
  • Re: ps_strings Konstantin Belousov
  • Re: ps_strings Carlos Jacobo Puga Medina
  • ps_strings Carlos Jacobo Puga Medina
• User Space DTrace and dumping function arguments for user space Shrikanth Kamath
• Re: will 9.2 be called 'diehard'? or maybe Naktomi? Jakub Lach
  • Re: will 9.2 be called 'diehard'? or maybe Naktomi? Darren Pilgrim
  • Re: will 9.2 be called 'diehard'? or maybe Naktomi? Jason Hellenthal
  • Re: will 9.2 be called 'diehard'? or maybe Naktomi? Adrian Chadd
  • Re: will 9.2 be called 'diehard'? or maybe Naktomi? Jordan K. Hubbard
• New CAM locking preview Alexander Motin
  • Re: New CAM locking preview Hans Petter Selasky
  • Re: New CAM locking preview Steven Hartland
  • Re: New CAM locking preview Adrian Chadd
  • Re: New CAM locking preview Alexander Motin
  • Re: New CAM locking preview Jeremie Le Hen
  • [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Alexander Motin
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Jeremie Le Hen
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Outback Dingo
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Jeremie Le Hen
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Jeremie Le Hen
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Olivier Cochard-Labbé
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Outback Dingo
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Alexander Motin
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Nathan Whitehorn
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Alexander Motin
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Ryan Stone
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Nathan Whitehorn
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking John Baldwin
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Nathan Whitehorn
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Olivier Cochard-Labbé
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Alexander Motin
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Olivier Cochard-Labbé
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Jeremie Le Hen
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Alexander Motin
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Jeremie Le Hen
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Alexander Motin
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking John Baldwin
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Alexander Motin
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking John Baldwin
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Alexander Motin
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Marius Strobl
  • Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Fabian Keil
• [PATCH] Add flag to makefs to require specfile entries to exist Eric van Gyzen
• Kernel DDB doesn't work in VM ? Yuri
• min. sys. requirements Aryeh Friedman
• [PATCH] Add 4K QUIRK for Intel X25-M, MARVELL SD88SA02 and OCZ Agility 2 Richard Yao
  • Re: [PATCH] Add 4K QUIRK for Intel X25-M, MARVELL SD88SA02 and OCZ Agility 2 Steven Hartland
  • Re: [PATCH] Add 4K QUIRK for Intel X25-M, MARVELL SD88SA02 and OCZ Agility 2 Richard Yao
  • Re: [PATCH] Add 4K QUIRK for Intel X25-M, MARVELL SD88SA02 and OCZ Agility 2 Xin Li
  • Re: [PATCH] Add 4K QUIRK for Intel X25-M, MARVELL SD88SA02 and OCZ Agility 2 Steven Hartland
  • Re: [PATCH] Add 4K QUIRK for Intel X25-M, MARVELL SD88SA02 and OCZ Agility 2 Steven Hartland
  • Re: [PATCH] Add 4K QUIRK for Intel X25-M, MARVELL SD88SA02 and OCZ Agility 2 Artem Belevich
  • Re: [PATCH] Add 4K QUIRK for Intel X25-M, MARVELL SD88SA02 and OCZ Agility 2 Richard Yao
• how to make a etc/rc.d start at boot time Aryeh Friedman
  • Re: how to make a etc/rc.d start at boot time Rui Paulo
  • Fwd: how to make a etc/rc.d start at boot time Aryeh Friedman
  • Re: how to make a etc/rc.d start at boot time joris dedieu
• Discussing ideas or wish list Patrick Dung
  • Re: Discussing ideas or wish list Eduardo Morras
  • Re: Discussing ideas or wish list Mark Felder
  • Re: Discussing ideas or wish list Mark Felder
  • Re: Discussing ideas or wish list Matthew Seaman
  • Re: Discussing ideas or wish list Lars Engels
  • Re: Discussing ideas or wish list Patrick Dung
  • Re: Discussing ideas or wish list Darren Pilgrim
  • Re: Discussing ideas or wish list Patrick Dung
  • Re: Discussing ideas or wish list Darren Pilgrim
  • Re: Discussing ideas or wish list Yuri
• I am frustrated Amit Rawat
  • Re: I am frustrated Super Bisquit
• After the FreeBSD VM crash, file system in VM got rolled back to some old previous state causing data loss Yuri
  • Re: After the FreeBSD VM crash, file system in VM got rolled back to some old previous state causing data loss Wojciech Puchar
  • Re: After the FreeBSD VM crash, file system in VM got rolled back to some old previous state causing data loss Yuri
  • Re: After the FreeBSD VM crash, file system in VM got rolled back to some old previous state causing data loss Mark Felder
  • Re: After the FreeBSD VM crash, file system in VM got rolled back to some old previous state causing data loss Sergey Slobodyanyuk
• Problem with lagg driver? Newpol, Richard
• Stacking lots of IP's on a single box - any 'gotchas'? Karl Pielorz
  • Re: Stacking lots of IP's on a single box - any 'gotchas'? Julian Elischer
  • Re: Stacking lots of IP's on a single box - any 'gotchas'? Sergey Kandaurov
  • Re: Stacking lots of IP's on a single box - any 'gotchas'? Diane Bruce
  • Re: Stacking lots of IP's on a single box - any 'gotchas'? Julian Elischer
  • Re: Stacking lots of IP's on a single box - any 'gotchas'? Karl Pielorz
• Symbols in symtab reordered between module.kld and module.ko? Shrikanth Kamath
• Can't override function keys in kbdcontrol Pragm B
  • Re: Can't override function keys in kbdcontrol Fernando Apesteguía
• kldload ipfw, with IPFIREWALL_DEFAULT_TO_ACCEPT Karl Pielorz
  • Re: kldload ipfw, with IPFIREWALL_DEFAULT_TO_ACCEPT Stefan Esser
  • Re: kldload ipfw, with IPFIREWALL_DEFAULT_TO_ACCEPT Karl Pielorz
  • Re: kldload ipfw, with IPFIREWALL_DEFAULT_TO_ACCEPT Simon Dick
  • Re: kldload ipfw, with IPFIREWALL_DEFAULT_TO_ACCEPT Karl Pielorz
  • Re: kldload ipfw, with IPFIREWALL_DEFAULT_TO_ACCEPT Konstantin Belousov
  • Re: kldload ipfw, with IPFIREWALL_DEFAULT_TO_ACCEPT Karl Pielorz
• How to display 256 colors on the vga console shell ? Olivier Cochard-Labbé
• CFR: improvments to cfi(4) flash driver Brooks Davis
• Android applications for fsyscall/nexec Tomohiko Sumi
• panic: kmem_map too small at heavy packet traffic Tugrul Erdogan
  • Re: panic: kmem_map too small at heavy packet traffic Tugrul Erdogan
  • Re: panic: kmem_map too small at heavy packet traffic Mark Felder
  • Re: panic: kmem_map too small at heavy packet traffic Adrian Chadd
  • Re: panic: kmem_map too small at heavy packet traffic Tugrul Erdogan
  • Re: panic: kmem_map too small at heavy packet traffic Adrian Chadd
• Kern.hz= +1 hertz at anything 2500 and above. Super Bisquit
  • Re: Kern.hz= +1 hertz at anything 2500 and above. Adrian Chadd
  • Re: Kern.hz= +1 hertz at anything 2500 and above. Super Bisquit
  • Re: Kern.hz= +1 hertz at anything 2500 and above. Wojciech Puchar
  • Re: Kern.hz= +1 hertz at anything 2500 and above. Adrian Chadd
  • Re: Kern.hz= +1 hertz at anything 2500 and above. Super Bisquit
• Kevent EV_DROP notification support LeoNerd
  • Re: Kevent EV_DROP notification support Adrian Chadd
• DTrace copyin with struct doesn't work? Yuri
  • Re: DTrace copyin with struct doesn't work? Andriy Gapon
• Should process run under chroot(8) still see mounts on the original system? Yuri
  • Re: Should process run under chroot(8) still see mounts on the original system? Mateusz Guzik
  • Re: Should process run under chroot(8) still see mounts on the original system? Yuri
  • Re: Should process run under chroot(8) still see mounts on the original system? Mateusz Guzik
  • Re: Should process run under chroot(8) still see mounts on the original system? Teske, Devin
• Increasing the kernel hertz rate in 10.0, RELEASE, and CURRENT Super Bisquit
• bin/176713: [patch] nc(1) closes network socket too soon Ronald F. Guilmette
  • Re: bin/176713: [patch] nc(1) closes network socket too soon Fernando Apesteguía
  • Re: bin/176713: [patch] nc(1) closes network socket too soon Ronald F. Guilmette
  • Re: bin/176713: [patch] nc(1) closes network socket too soon Mark Delany
  • Re: bin/176713: [patch] nc(1) closes network socket too soon Ronald F. Guilmette
  • Re: bin/176713: [patch] nc(1) closes network socket too soon Fernando Apesteguía
  • Re: bin/176713: [patch] nc(1) closes network socket too soon Ronald F. Guilmette
  • Re: bin/176713: [patch] nc(1) closes network socket too soon Adrian Chadd
  • Re: bin/176713: [patch] nc(1) closes network socket too soon Ronald F. Guilmette
  • Re: bin/176713: [patch] nc(1) closes network socket too soon Adrian Chadd
  • Re: bin/176713: [patch] nc(1) closes network socket too soon Ronald F. Guilmette
  • Re: bin/176713: [patch] nc(1) closes network socket too soon Adrian Chadd
  • Re: bin/176713: [patch] nc(1) closes network socket too soon Ronald F. Guilmette
  • Re: bin/176713: [patch] nc(1) closes network socket too soon Adrian Chadd
  • Re: bin/176713: [patch] nc(1) closes network socket too soon Ronald F. Guilmette
  • Re: bin/176713: [patch] nc(1) closes network socket too soon Adrian Chadd
  • Re: bin/176713: [patch] nc(1) closes network socket too soon Ronald F. Guilmette
  • Re: bin/176713: [patch] nc(1) closes network socket too soon Adrian Chadd
  • Re: bin/176713: [patch] nc(1) closes network socket too soon Ian Lepore
  • Re: bin/176713: [patch] nc(1) closes network socket too soon Ronald F. Guilmette
• UFS related panic (daily <-> find) rank1seeker
  • Re: UFS related panic (daily <-> find) John Baldwin
  • Re: UFS related panic (daily <-> find) rank1seeker
  • Re: UFS related panic (daily <-> find) John Baldwin
  • Re: UFS related panic (daily <-> find) rank1seeker
  • Re: UFS related panic (daily <-> find) John Baldwin
  • Re: UFS related panic (daily <-> find) rank1seeker
  • Re: UFS related panic (daily <-> find) John Baldwin
  • Re: UFS related panic (daily <-> find) rank1seeker
  • Re: UFS related panic (daily <-> find) John Baldwin
  • Re: UFS related panic (daily <-> find) rank1seeker
  • Re: UFS related panic (daily <-> find) John Baldwin
  • Re: UFS related panic (daily <-> find) rank1seeker
• ***HELP*** West Side Family
  • Re: ***HELP*** Jason Hellenthal
  • Re: ***HELP*** Damien Fleuriot
  • Re: ***HELP*** Jason Hellenthal
• am I abusing the UMA allocator? Chris Torek
• Kernel crashes after sleep: how to debug? Yuri

• Earlier messages
• Later messages