Subject: Re: Table of contents addition for intro(9) manual
To: Izumi Tsutsui <email@example.com>
From: Mindaugas R. <rmind@NetBSD.org>
Date: 02/17/2007 14:44:02
Izumi Tsutsui <firstname.lastname@example.org> wrote:
> How about the following (still rough) categorization?
Well, you have listed all manuals. The general intention is to list only
abstract-manuals. But while we still haven't all abstract-manuals in man9, it
probably would be OK.
> * VM system
> cpu_swapout, pmap, uvm
> * memory management
> kmem_alloc, kmem_free, kmem_zalloc, memoryallocators, pool,
> pool_cache, vmem, vmem_alloc, vmem_create, vmem_destroy,
> vmem_free, vmem_xalloc, vmem_xfree
IMHO, these should be merged. And leave only memoryallocators(9) (it's a
general description), uvm (9), pmap(9). And seems cpu_swapout(9), which is
without place :)
> * process control
> cpu_exit, cpu_switch, cpu_idle, cpu_lwp_fork, ctxsw, curproc,
> do_setresuid, fork1, ltsleep, need_resched, preempt, scheduler,
> setrunqueue, signal, suspendsched, userret
While scheduler(9) and others (there should be something like dispatcher(9) )
is not yet improved, it would be OK.
> * file system
> dofileread, extattr, file, fileassoc, filedesc, fisetown, fstrans,
> namecache, namei, pathname, vattr, vfs, vfs_hooks, vfsops, vfssubr,
> vnfileops, vnode, vnodeops, vnsubr
We don't need so much, only general ones. See patch.
Same to networking and other categories.
The rest looks really good for me. At least while we don't have