the plan was to eventually, after the code work is done, have the
man-page for secmodel_bsd44.9 list the listeners and describe further
how they should be used in e.g. overlay model.

however, I guess we can have two man-pages for each model, with one
describing the implications etc. and the other being a kernel programmer
guide. these belong in sections 8 and 9, not 7, though.

if you're going to do that work for secmodel_bsd44, please do it for
secmodel_overlay (it's ~nop) and don't create a symlink to a
"securelevel" man-page. we never had one.

-e.

Pavel Cahyna wrote:
> On Sat, Dec 16, 2006 at 04:53:51PM +0200, Elad Efrat wrote:
>> personally I object because the secmodel man-pages *are* for programmers
>> in case they want to implement an overlay model.
> 
> Is it okay to move the manpage while leaving the #includes ?
> 
> It just seems strange to list #include files in a manpage which does not
> document any declaration or macro from those headers, regardless of the
> section which the manpage belongs to. What is the programmer supposed to
> do with the headers besides #including them?
> 
> If you plan to supply some programming documentation later, would it make
> sense to have both secmodel_bsd44.9 and secmodel_bsd44.7 ?
> 
> Pavel