linuxtraining / lt Goto Github PK

The course should, besides a normal index, also contain a separate index of people mentioned in the book. (There is probably a docbook xml feature for this.)

There is currently no chapter on ldap.
There should be one before the end of 2011 that allows students to:

• setup an ldap server with kerberos
• explain and use a schema
• explain and design OU's
• manage users and groups
• manage permissions
• migrate to and from active directory
• use as a back-end for samba

The modules directory should contain exactly one directory for every chapter (and one chapter for every directory). The filenames in each directory should have a consistent naming scheme. For example :
mod_working_with_directories
mod_working_with_directories/directories_theory.xml
mod_working_with_directories/directories_practice.xml
mod_working_with_directories/directories_solution.xml
mod_working_with_file_contents
mod_working_with_file_contents/filecontents_theory.xml
mod_working_with_file_contents/filecontents_practice.xml
mod_working_with_file_contents/filecontents_solution.xml
mod_working_with_files
mod_working_with_files/files_theory.xml
mod_working_with_files/files_practice.xml
mod_working_with_files/files_solution.xml

This allows (in the future) for easy separation of an 'exercise' book and a 'solutions' book for the students.
This potentially obsoletes (the maintenance of) the books/chapters file.

Paul is currently working on this and will commit when (the fundamentals part is) ready.

Some sections are still in Dutch, they should either be commented out, or translated into English.

updating the docbook libraries and putting them in some kind of submodule, or have the initialization script download/update it.

first: test the newer docbook libs

The Sysadmin book now builds, but its content should be reviewed. Some chapters (like networking) are a mess. I will do this for each minibook in the "System Administration" book.

This requires a little bit of work for:
minibook_process_management

A bit more work for:
minibook_local_disk_management
minibook_boot_management
minibook_system_management
minibook_kernel
minibook_backup

A lot of work for:
minibook_networking

in book linux_fun.pdf on page 279, the number have skippen ---> there is no number 6 exercise.

There is currently no chapter on mail-servers.
There should be one before the end of 2011 that allows students to:

• explain concepts like MTA, MDA, mailbox
• setup an smtp server (sendmail/postfix)
• setup pop3 and IMAP for clients (cyrus)
• manage mailboxes
• migrate from MS Exchange

optional:

• setup spam filtering
• setup antivirus filtering

A lot of modules and minibooks still have a messed up toc. The display of toc should be consistent in all books.

DONE for minibook_processes (20110627)
DONE for minibook_disk_management, uuid, raid (20110627)
TODO minibook_boot_management
TODO minibook_system_management
TODO minibook_kernel
TODO minibook_backup
TODO minibook_networking

A lot of modules barely have key words in the index. All modules should be checked for this, adding keywords to the index.

the build script halts if the reviewers file is empty
(workaround, I put myself as the only reviewer for the Dutch networking course)

Pulled and built, but when I try to open the PDF version of the book, book.pdf seems to be pointing to a broken link

After a git checkout, one still has to git submodule init and git submodule update.
We should have some make script to do that.
That script should also be able to build a tarball with full sources that are needed.

The Servers (aka advanced) book now builds, but its content should be reviewed. Some chapters (like selinux) are a mess. I will slowly start doing this for most of the minibooks here.

This requires quite some work for:
minibook_samba (must be done before October 2011)
minibook_dns (must be done before October 2011)
minibook_dhcp (must be done before October 2011)
minibook_router
minibook_firewall (must be done before December 2011)
minibook_webserver (must be done before December 2011)
minibook_ipv6
minibook_database
minibook_selinux

Hi,

I have been discussing this with Serge last month. Looking at the code/docs I feel that simply using asciidoc (which translates to DocBook perfectly) is a much easier way of developing. You can have different pieces in different files, included in other documents (even with different title levels depending on the document).

If you would be interested, I am happy to discuss and help with the migration, and we can grab a beer too :-D

PS asciidoc/docbook is being used by O'Reilly authors in producing a book (however, O'Reilly's styling has not been made public). If interested I can provide you with a few example documents that show the possibilities.