2017/freebsd-hackers/20171231.freebsd-hackers
Messages: 44, sorted by subject
|
Last page update: Sat Jan 3 13:10:19 UTC 2026
|
|
home | up | archive | sorted by: subject - author - date - reverse date
1. Dec 26 Benjamin Kaduk Call for 2017Q4 quarterly status reports 2. Dec 25 Warner Losh devmatch(8) committed .... 3. Dec 25 Emmanuel Vadot Re: devmatch(8) committed .... 4. Dec 25 Warner Losh Re: devmatch(8) committed .... 5. Dec 26 Chris H Re: devmatch(8) committed .... 6. Dec 28 Eitan Adler Re: faq/troubleshoot.html#indefinite-wait-buffer has the direction of transfer wrong (head -r326888 /usr/src/) 7. Dec 25 Benjamin Kaduk FreeBSD Quarterly Status Report - Third Quarter 2017 8. Dec 26 Eugene Grosbein idprio(1) broken 9. Dec 26 Eugene Grosbein Re: idprio(1) broken 10. Dec 26 Andriy Gapon Re: idprio(1) broken 11. Dec 26 Eugene Grosbein Re: idprio(1) broken 12. Dec 27 Eugene Grosbein Re: idprio(1) broken 13. Dec 29 Yuri Is it considered to be ok to not check the return code of close(2) in base? 14. Dec 29 Ian Lepore Re: Is it considered to be ok to not check the return code of close(2) in base? 15. Dec 29 Alan Somers Re: Is it considered to be ok to not check the return code of close(2) in base? 16. Dec 29 Eugene Grosbein Re: Is it considered to be ok to not check the return code of close(2) in base? 17. Dec 29 Alfred Perlstein Re: Is it considered to be ok to not check the return code of close(2) in base? 18. Dec 29 Poul-Henning Kamp Re: Is it considered to be ok to not check the return code of close(2) in base? 19. Dec 30 Eugene Grosbein Re: Is it considered to be ok to not check the return code of close(2) in base? 20. Dec 30 Rodney W. Grimes Re: Is it considered to be ok to not check the return code of close(2) in base?
21. Dec 30 Rodney W. Grimes Re: Is it considered to be ok to not check the return code of close(2) in base? 22. Dec 30 Ian Lepore Re: Is it considered to be ok to not check the return code of close(2) in base? 23. Dec 30 Larry McVoy Re: Is it considered to be ok to not check the return code of close(2) in base? 24. Dec 30 Mark Millard Is the clang 5.0.1 use of .rela.plt and R_PPC64_JMP_SLOT for kernel modules a llvm issue? Just a FreeBSD one? 25. Dec 28 Julian Elischer Re: Objections to converting bsd-family-tree to a dot file 26. Dec 29 Eitan Adler Re: Objections to converting bsd-family-tree to a dot file 27. Dec 26 D. Ebdrup RE: OOM problem? 28. Dec 27 Eitan Adler Parsing a comment in stdlib.h 29. Dec 27 Alan Somers Re: Parsing a comment in stdlib.h 30. Dec 27 Warner Losh Re: Parsing a comment in stdlib.h 31. Dec 27 Rodney W. Grimes Re: Parsing a comment in stdlib.h 32. Dec 24 Yuri Possible to prioritize IO requests based on the requesting process? 33. Dec 25 Eugene Grosbein Re: Possible to prioritize IO requests based on the requesting process? 34. Dec 26 Aryeh Friedman Running dual boot windows inside of bhyve 35. Dec 27 Aryeh Friedman Re: Running dual boot windows inside of bhyve 36. Dec 27 Alan Somers Re: Running dual boot windows inside of bhyve 37. Dec 27 Rebecca Cran Re: Running dual boot windows inside of bhyve 38. Dec 27 Patrick M. Hausen Re: Running dual boot windows inside of bhyve 39. Dec 27 Cy Schubert RE: Running dual boot windows inside of bhyve 40. Dec 28 Chris Knight Re: Running dual boot windows inside of bhyve
41. Dec 24 Mark Millard Re: TARGET_ARCH=powerpc64 jump from head -r326192 to -r327075: g_event crashes with "instruction storage interrupt" [clang-built kernel specif 42. Dec 24 Mark Millard Re: TARGET_ARCH=powerpc64 jump from head -r326192 to -r327075: g_event crashes with "instruction storage interrupt" [kldload -n filemon crashe 43. Dec 24 Mark Millard Re: TARGET_ARCH=powerpc64 jump from head -r326192 to -r327075: g_event crashes with "instruction storage interrupt" [kldload -n filemon crashe 44. Dec 24 Mark Millard Re: TARGET_ARCH=powerpc64 jump from head -r326192 to -r327075: g_event crashes with "instruction storage interrupt" [R_PPC64_JMP_SLOT problem]
home | up | archive | sorted by: subject - author - date - reverse date