Hi evereyone
I am back from my long weekend and finally able to clarify why I have
chosen a differnt kind of grouping. As Kara mentioned in the first mail the
modules should not only be structured, They should be grouped in such an
order that teachers are able to extrapolate lessons and course papers in a
sensible way. So I have taken this approach to which differs from yours (it
is *not* more correct than the one of David. It is just the focus which has
been changed [as David already mentioned]).
Maybe I can show the problems I would have giving a course which is
structured the way David proposed it
Security/access control
(to cover security topics is very hard if you cannot spend a lot
of time with networking basics as they
are absolutely vital)
secure access
ssh
(OK start with ssh. It is correct that this is important
but how do I tell peoples that this is a
deamon which has to be started e.g. runlevels, scripts
and so on)
vpn
(to handle this you have usualy to patch kernels e.g.
SNAT of vpn [except Kernel 2.4])
tcp wrappers
(for proper handling this topic requires very deep knowledge of
TCP/IP and protocol internals)
PAM
(NIS and LDAP are frequently used in that context what do I do?
it is a long time until I get to those
topics)
System administration
(I can do this bunch here but peoples do not know the boot
process deeply enough which is in my eyes vital
for analysing problems and reading logs)
system monitoring
System auditing/logging
file handling
backups
Hardware
(at this point peoples have no knowledge about the proc
filesystem maybe we could move it here [it is
technicaly a fs but from the logical view a complex config
file/point/whatever])
interrupts/ioports
laptops
(patching drivers into kernel?)
PCMCIA
(patching drivers into kernel?)
miscellaneous
Hard disks
(most of these topics are hardware related and therefore very
close to the kernel about which the students
have almost no knowledge so far)
general
RAID/LVM
(patching drivers into kernel?)
maintenance
Filesystems
fstab
(This is the first time important when mounting the fs at bootup
so
/proc
partitions
fs types
(patching drivers into kernel?)
and so on ...
I tried to work from the basics (kernel and surrounding) to the "outer
parts" because peoples in courses (that is at least what I think) should
first learn walking before they should try to fly. Your approach is neither
wrong nor bad it is just (in my eyes) a more technical than teachable
grouping.
Maybe we should first sort out exactly what we want (I might be wrong) then
choose an aproach (according to those goals) and then work on that
approach.
Regards
Martin
--
This message was sent from the lpi-examdev mailing list.
Send `unsubscribe lpi-examdev' in the subject to [EMAIL PROTECTED]
to leave the list.
