2013/freebsd-hackers/20130728.freebsd-hackers
Messages: 47, sorted by subject
|
Last update: Mon Feb 13 14:17:55 UTC 2023
|
|
home | up | archive sorted by: subject | author | date | reverse date
1. Jul 26 Tomohiko Sumi Android applications for fsyscall/nexec 2. Jul 21 Ronald F. Guilmette Re: bin/176713: [patch] nc(1) closes network socket too soon 3. Jul 21 Mark Delany Re: bin/176713: [patch] nc(1) closes network socket too soon 4. Jul 21 Adrian Chadd Re: bin/176713: [patch] nc(1) closes network socket too soon 5. Jul 21 =?ISO-8859-1?Q?Fernando_Ap Re: bin/176713: [patch] nc(1) closes network socket too soon 6. Jul 22 Ronald F. Guilmette Re: bin/176713: [patch] nc(1) closes network socket too soon 7. Jul 22 Ronald F. Guilmette Re: bin/176713: [patch] nc(1) closes network socket too soon 8. Jul 22 Ronald F. Guilmette Re: bin/176713: [patch] nc(1) closes network socket too soon 9. Jul 22 Adrian Chadd Re: bin/176713: [patch] nc(1) closes network socket too soon 10. Jul 22 Ronald F. Guilmette Re: bin/176713: [patch] nc(1) closes network socket too soon 11. Jul 22 Adrian Chadd Re: bin/176713: [patch] nc(1) closes network socket too soon 12. Jul 22 Ronald F. Guilmette Re: bin/176713: [patch] nc(1) closes network socket too soon 13. Jul 23 Adrian Chadd Re: bin/176713: [patch] nc(1) closes network socket too soon 14. Jul 23 Ronald F. Guilmette Re: bin/176713: [patch] nc(1) closes network socket too soon 15. Jul 24 Adrian Chadd Re: bin/176713: [patch] nc(1) closes network socket too soon 16. Jul 24 Ronald F. Guilmette Re: bin/176713: [patch] nc(1) closes network socket too soon 17. Jul 25 Adrian Chadd Re: bin/176713: [patch] nc(1) closes network socket too soon 18. Jul 26 Brooks Davis CFR: improvments to cfi(4) flash driver 19. Jul 23 Jia-Shiun Li Re: cpufreq not working as module on i386/amd64 20. Jul 24 Yuri DTrace copyin with struct doesn't work?
21. Jul 24 Andriy Gapon Re: DTrace copyin with struct doesn't work? 22. Jul 23 Super Bisquit Increasing the kernel hertz rate in 10.0, RELEASE, and CURRENT 23. Jul 24 Super Bisquit Kern.hz= +1 hertz at anything 2500 and above. 24. Jul 25 Adrian Chadd Re: Kern.hz= +1 hertz at anything 2500 and above. 25. Jul 25 Super Bisquit Re: Kern.hz= +1 hertz at anything 2500 and above. 26. Jul 25 Wojciech Puchar Re: Kern.hz= +1 hertz at anything 2500 and above. 27. Jul 25 Adrian Chadd Re: Kern.hz= +1 hertz at anything 2500 and above. 28. Jul 25 Super Bisquit Re: Kern.hz= +1 hertz at anything 2500 and above. 29. Jul 22 John Baldwin Re: Kernel crashes after sleep: how to debug? 30. Jul 24 Paul "LeoNerd" Evans Kevent EV_DROP notification support 31. Jul 25 Adrian Chadd Re: Kevent EV_DROP notification support 32. Jul 25 Tugrul Erdogan panic: kmem_map too small at heavy packet traffic 33. Jul 26 Tugrul Erdogan Re: panic: kmem_map too small at heavy packet traffic 34. Jul 26 Mark Felder Re: panic: kmem_map too small at heavy packet traffic 35. Jul 26 Adrian Chadd Re: panic: kmem_map too small at heavy packet traffic 36. Jul 27 Tugrul Erdogan Re: panic: kmem_map too small at heavy packet traffic 37. Jul 27 Adrian Chadd Re: panic: kmem_map too small at heavy packet traffic 38. Jul 23 Yuri Should process run under chroot(8) still see mounts on the original system? 39. Jul 23 Mateusz Guzik Re: Should process run under chroot(8) still see mounts on the original system? 40. Jul 23 Yuri Re: Should process run under chroot(8) still see mounts on the original system?
41. Jul 23 Teske, Devin Re: Should process run under chroot(8) still see mounts on the original system? 42. Jul 24 Mateusz Guzik Re: Should process run under chroot(8) still see mounts on the original system? 43. Jul 22 John Baldwin Re: UFS related panic (daily <-> find) 44. Jul 26 rank1seeker@gmail.com Re: UFS related panic (daily <-> find) 45. Jul 26 John Baldwin Re: UFS related panic (daily <-> find) 46. Jul 26 rank1seeker@gmail.com Re: UFS related panic (daily <-> find) 47. Jul 26 John Baldwin Re: UFS related panic (daily <-> find)
home | up | archive sorted by: subject | author | date | reverse date