чт, 25 июл. 2019 г. в 08:33, Germain Le Chapelain <germ...@lanvaux.fr>: > > On Mon, 22 Apr 2019 12:25:07 +0700 > Robert Elz <k...@munnari.oz.au> wrote: > > > | i know and fully acknowledge that i will have to work hard to understand > > | netbsd internals, and the currently, the only way to do so is by reading > > | the source, over and over again till i get comfortable with it. > > > > Yes, nothing beats that. and for NetBSD, as there is no book that > > actually describes it (that I know of) that will, for many aspects, > > be the only choice. > > > There is a book litteraly called `NetBSD Internals' in the documentation > section of the website: > > http://netbsd.org/docs/internals/en/netbsd-internals.html > > > Sounds like the best complement to the Bach, since it focuses on the > implementation and extending NetBSD.
Far from being complete though: 3.3. Processes and threads creation 3.3.1. fork, clone, and pthread_create usage XXX write me 3.3.2. Overview of fork code path XXX write me 3.3.3. Overview of pthread_create code path XXX write me 3.4. Processes and threads termination 3.4.1. exit, and pthread_exit usage XXX write me 3.4.2. Overview of exit code path XXX write me 3.4.3. Overview of pthread_exit code path XXX write me 3.5. Signal delivery 3.5.1. Deciding what to do with a signal XXX write me etc etc > > (I don't know why I get back to such old messages: I was checking for update > on my thread, came across this one and felt like sharing, > It's because this is one thing that drove me- or, more so, cemented me-to > NetBSD: its perfect website ;) ) > > > -- > Germain >
