On Sun, 2007-10-21 at 21:13 -0400, Daniel Howard wrote: > Justin wrote: > > With K12LTSP growing in popularity, it might even make sense in some > > situations for a teacher to maintain a small collection of images on the > > server. Could this lead to a possible change in what the administrator & teacher > > roles are in IT? > > Excellent Justin! I like the idea of multiple copies of the OS on the > classroom server, perhaps one locked down that can always be recalled so > basic functionality is always available, and others specialized and > customizable by teachers in particular areas like music (a Musix image), > math, etc. Again the admin rears his head: In general, it is good practice to have the ability to rollback a system to a prior state is there is a need. However, complexity and freedom are not always good friends when it comes to software. The multiple OS image idea sounds good until it has to be implemented. So multiple hard drive partitions must be set up by the admin and configured for sandbox use since the technical nature of the task will drive most anyone else to drink. Again, the classroom is generally not a test server environment. That is where the plan is for the teacher to look the most competent and having students wade through buggy software is just a respect-loosing process. > > Marilyn (and other teachers), how would that be for you, to have one > image locked down you knew you could always count on for basic needs, > but still have the freedom to do whatever you wanted with the other > images? In the situation where only a single class uses a single machine, rebooting to access a known stable image is OK. But for larger scale situations it is completely unacceptable for teacher A to reboot the server that teachers B-F are using! > > Daniel > > -- > Daniel Howard > President and CEO > Georgia Open Source Education Foundation > -- James P. Kinney III CEO & Director of Engineering Local Net Solutions,LLC 770-493-8244 http://www.localnetsolutions.com GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics) <jkinney@xxxxxxxxxxxxxxxxxxxxx> Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7
Attachment:
signature.asc
Description: This is a digitally signed message part