Tetsuo Handa wrote: > Domains in "Chapter 10" are deployed in serial and domains in "Appendix D" are > deployed in parallel. In other words, "Chapter 10" is the first picture in > chapter-10.html and "Appendix D" is the second picture in chapter-10.html . > > Therefore, I though "Appendix D" can come to the right place if rewritten as > "Chapter 11". > But I also felt that "Appendix D" is easier to try than "Chapter 10" because > "Appendix D" explains complete steps while "Chapter 10" explains only > concepts. > Maybe rewriting "Chapter 10" as "Appendix E" is better.
I'm not really fussed either way. If I had to choose, I would prefer to keep things as they are. Chapter 10 is not really usable without having read all previous chapters and having a fuller understanding of TOMOYO Linux, while Appendix D is more usable as a stand-alone article with less prior knowledge required. > OK. If you have no more changes, let's copy 2.3-tmp/ to 2.3/ . I don't think I have any further changes to do. >> Also, I have started porting 1.8 docs to AKARI. > > Thank you. Documentation for AKARI is very similar to that of TOMOYO 1.8. > What we need to do is to remove some few dozens of lines that explain > > capability > ipc signal > network inet dgram recv > network unix dgram recv Is "network inet raw recv" also missing, as according to http://akari.sourceforge.jp/comparison.html.en ? I have removed references to this also. > and to add few dozens of lines that explain version&config dependency > explained > at http://akari.sourceforge.jp/comparison.html . Appendix G-J applies to > AKARI. Sure, I will add these back. > Guiding users to http://tomoyo.sourceforge.jp/1.8/chapter-4.html after > installation instructions might be possible if errata pages (like > > "capability" section explained at > http://tomoyo.sourceforge.jp/1.8/policy-specification/domain-policy-syntax.html.ja#capability > is not supported by AKARI. > > "ipc signal" section explained at > http://tomoyo.sourceforge.jp/1.8/policy-specification/domain-policy-syntax.html.ja#ipc_signal > is not supported by AKARI. > > ) are provided. I am fine with maintaining separate AKARI pages, but it's up to you. I think it's less confusing for users to have AKARI docs kept separate. However, it does increase maintenance burden for us, but I have created htdocs/1.8/adapt_for_akari.sh to speed up conversion of pages from TOMOYO Linux 1.8.x docs. _______________________________________________ tomoyo-dev-en mailing list tomoyo-dev-en@lists.sourceforge.jp http://lists.sourceforge.jp/mailman/listinfo/tomoyo-dev-en
