Shrinivasan T <tshrinivasan@...> writes:
> We can choose any topic, create documentations on introduction, create
> exercises and verify them.
>
> Please update here, if you wish to contribute for the LAB Manual.
I would like contribute to this. I can provide help in the areas of
Python and GUI Programming.
I have been doing GNU/Linux training for quite sometime and I think I
can provide some useful inputs when it comes to doing a GNU/Linux
lab. The syllabus also seems to have some issues, but I think it can been
fixed up with a little bit or re-ordering and trimming. A few suggestions
for the lab manual:
* There seems to be too many languages: Python, Perl, PHP, Gambas
... I would suggest that one language be used through-out the lab
exercises, and the others be just touched upon.
* One of the problems with labs involving installation of kernel and
software packages, is that the students have to be given root
access. And there will be lot of maintenance overhead for restoring
the system back to a sane state. This can be avoided by installing
the packages within a VM. Within the VMs the students get complete
root access, and even if things screw up, the VM's harddisk image
can be restored from backup.
* The better order would probably be: (I have choosen Python as
the primary language, here. But other combinations are also
imaginable.)
- Running Python
- GUI Programming (using Python)
- Version control systems ...
- Virtualisation
- Setting up the complete network ...
(using a virtual network formed by multiple VMs)
- Installing various software pacakges (within VM)
- Compiling from source (within VM)
- Introduction to package management (within VM)
- Writing user space drivers (using Python)
- Kernel configuration, compilation and installation (within VM)
- Running PHP
- Running Perl
Regards,
Vijay
_______________________________________________
ILUGC Mailing List:
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
