Archive for April, 2009

Article Summary #7: Byfield – Expert Shares Secrets to Saving Thousands with K12LTSP

April 15, 2009

Byfield, B.  (2007).  Expert shares secrets to saving thousands with K12LTSP.  <http://www.linux.com/feature/59614>

This is a short article, but one that clarifies some things I have been reading about regarding the K12LTSP.  It also raises a number of issues I have not read elsewhere.

Summary

Robert Arkiletian is a contributor to the K12 Linux Terminal Server Project (K12LTSP).  The K12LTSP is a Linux distribution that allows one standard desktop computer to run a number of other computers as thin clients.  The clients can be older computers, which don’t even need a functioning hard drive.  Depending on the specifications of the computer which acts as a server, 5-30 or more clients can run off of a single computer.  This setup is familiar to system administrators, but the drive of the K12LTSP is to make this setup simple enough for non-technical teachers to administer.

The K12LTSP site lists a set of minimum requirements for the computer acting as a server.  With three years’ experience administering a lab with 30 clients, Arkiletian recommends a more powerful set of capabilities:

  • A dual processor so that runaway processes can be stopped immediately and dealt with at a later time.  This allows the classroom teacher to maintain a functioning network without significantly interrupting the class.
  • Two hard drives which “mirror each other in a RAID 1 array” (p. 1).
  • 100MB of RAM per client.  This number is interesting, because it is a familiar specification to most teachers.  This suggests that a standard teacher’s desktop computer with 1GB of RAM might be capable of running 10 clients.
  • Two ethernet cards.  One creates a private network for the clients, and one connects to the rest of the network.

For client machines, specifications are significantly lower.  However, some features can make the client more responsive to student needs.

  • Processor speed is unimportant.  Arkletian says that anything less than 100Mhz may cause problems, but a computer would have to be around ten years old to have a processor that slow now.
  • A 4MB video card should be sufficient.
  • 128MB of RAM is recommended, to prevent over-reliance on swapping with the server’s hard drive.
  • A light window manager such as IceWM rather than GNOME or KDE can also allow more efficient use of client and server resources.
  • An ethernet card is needed to connect to the server.
  • A USB port allows students to use memory sticks, and presumably external devices like digital cameras.

One of the primary goals of the K12LTSP is to make system administration responsive to teachers’ needs.  These include technical needs such as simplicity and reliability, and pedagogical needs such as the ability to easily monitor students’ work on the computers.  The Fl_TeacherTool supports teachers in these regards.

  • Teachers can see which terminals are in use at any time.
  • Teachers can see which programs are running on each client.
  • Teachers can click a button to see the desktop of any client on their own screen.  This is a tremendous help in watching for appropriate use by students.
  • At any time, the teacher can take control of any student’s desktop.
  • Teachers can send files to students.
  • Teachers can send active copies of whatever the teacher is working on to students’ desktops, thus acting as individual whiteboards.

Arkiletian sees a number of advantages to using the K12LTSP setup with students.

  • Maintenance is low.
  • Software only needs to be installed on the server computer.
  • Problematic clients can be swapped out easily.
  • Computers that are seven or eight years old can be used as clients long after their standalone service has ended.
  • A computer lab can cost one tenth what it would if workstations were used.  This money can be reinvested in smaller workstation-style labs for specific purposes.

The only limitation Arkiletian mentions is that the clients are limited to “standard computing” (p. 3).  Animation requires too much memory swapping for this kind of setup.

Evaluation and Educational Relevance

The use of OS-based systems in education is hardly mentioned in educational literature.  A search for the keyword “Linux” in the ERIC database brings up just 22 results, and most of these articles only talk about the possibilities of using OS applications in schools.  There is very little in the way of describing actual implementations, and even less about evaluating the impact of these implementations.  This motivates me to write up my experience with OS in education.  It also makes me want to publish these articles in non-technical journals and magazines.  The teachers we want to reach most, educators who are not experts, do not read journals like Computers & Education, Tech & Learning, and Newsweek.  They read things like The Reading Teacher and Journal of Social Studies Research.  Writing for non-technical audiences about the pedagogical benefits of OS implementations is sorely needed.

This article points to the need for visionary technology leaders in school districts.  I am reminded of the band aid story.  A student in a first grade classroom went up to the teacher and said, “I just cut my finger!  Can I have a band-aid?”  As the teacher gave the student a colorful band-aid, another student went up to the teacher and said, “If he gets a band-aid, I want one too!”  All too often, this is the conception of fairness that students have.  When it comes to technology, many educators feel the same way.  If one teacher has a new powerful computer, other teachers feel they should have access to the same technology.  People feel this way regardless of whether they have an actual pedagogical need for the more powerful computer.  A better conception of fairness is one in which everyone gets what they need, when they need it.  We need technology leaders who can apply this kind of thinking to district-wide technology decisions.  For example, we might consider putting thin clients in a language-arts based classroom, and powerful workstations in a computer science lab.  The money saved from putting only the necessary resources in each area can be used to hire a computer science teacher with the expertise to teach students to use the full capabilities of the more powerful workstations.  This question of whether we should make teaching programming a priority is another conversation altogether.  This requires the leadership of technology experts in the district who can accurately match resources to actual needs, and explain these distribution decisions in a friendly manner to non-expert teachers.

The Fl_TeacherTool makes me think of one specific application in my old school.  We had a number of smaller rooms that student groups often used for project work.  These groups were usually not supervised directly.  We hesitated to put computers in these rooms because of the difficulty of monitoring their use.  With the Fl_TeacherTool, I wonder if the server could be placed in a classroom and the clients in the smaller work rooms.  The work rooms would become more productive spaces, and the monitoring would cease to be an issue.

Advertisements

Article Summary #6: Houston – Linux Makes the Grade

April 13, 2009

Houston, M.  (2007).  Linux makes the grade.  Technology & Learning 28(4), 8 pp.

When most people consider why a school or school district might consider implementing a Linux-based technology solution, they think of financial issues.  If you ask the people responsible for these decisions, however, they list a number of other equally significant issues such as reliability, simplicity, flexibility, and security.  Houston describes the experiences some schools have had in implementing Linux-based technology solutions.

Summary

In 2001 the Indiana Department of Education implemented a one-to-one initiative with the goal of having one computer for every student in the Indiana state school system.  They found that despite significant investment in technology, students still spent less than one hour per week using computers.  In making the switch to a Linux-based technology solution, the state saved over $100 million annually on licensing fees.  This money was reinvested in hardware and support throughout the state.  Not only did the state get a significant increase in the number of computers available to students, they also got a more “secure, reliable, and sophisticated” system (p. 1).  Michael Huffman, special assistant for technology in the Indiana State Education Department, said that a Linux-based system is “the only model we’ve come up with that is affordable, repeatable, and sustainable” (p. 1).

A number of developments in the Linux community have made it friendlier to non-expert users.  Linux has graphical user interfaces available that require little understanding of the operating system itself.  These interfaces can be configured to mimic Windows or Mac systems, or they can be customized in ways that go beyond the latest offerings of these proprietary systems.  Linux is known for running free software, but not everyone knows that well-established companies like Red Hat and SUSE offer fee-based support programs for Linux systems.

In 2004 the Saugus Union School District in California implemented a Linux-based system throughout their district.  It was the desire for a flexible system, not financial considerations, that motivated the change.  Jim Klein, head of technology in the district, has this advice for people considering a move to Linux:

Pick up your Windows machine (or Mac, if you are so inclined) that is on your desk and move it across the room.  Make sure that you do not put a chair in front of it, and that you get up and leave your desk to use it. (p. 5)

The Saugus School District ended up with a system of computers that was faster than before, and even the oldest computers in the system were more reliable than most computers had previously been.  The IT staff has spent more time directly supporting teachers, staff, and students and less time focusing on hardware and software issues since the transition went into effect.  They are able to implement new software solutions more quickly, and they are more confident in the security of their system.  “We were able to smile when the latest security vulnerability surfaced, knowing that it wouldn’t affect our systems” (p. 5).

One particular question arises repeatedly in discussions about building an entire school’s technology solution around open source software.  “Are these computers, which don’t easily run the Microsoft OS or applications built to run on Microsoft, actually preparing our students for the workplace in their future” (p. 3)?  David Trask of Vassalboro Community School in Maine uses our understanding of driver education to address this question:

Our kids learn how to use a computer…no matter what the OS or application.  I use the analogy of driver’s ed quite often.  It goes like this:  When you took driver’s ed, did you learn how to drive a Ford?  How about a Chevy?  A Toyota?  Most people can’t remember… why?  Because ya’ learned how to drive a car… regardless of make, model, or size.  Why should computers be any different?  (p. 6)

Evaluation and Educational Relevance

Any entrenched system is difficult to change, and the current technology solution of any school or school district is certainly an entrenched system.  Large systems only change when something makes the change worthwhile, such as a serious problem with the existing system, or a significant benefit of a new solution.  In many cases, including those described in this article, switching from a proprietary technology solution to a Linux or OS solution addresses both of these issues.

One principle in particular can guide us through many of these decisions.  Technology should serve educational goals, and educational goals should not be adjusted to match existing technology.  Effective technology solutions center around a long-term vision, on the order of five to ten years.  With this perspective in mind, Linux and OS solutions make sense for many institutions.  In fact, it can be seen as irresponsible to tie a school to proprietary systems when more reliable and effective open solutions exist.  It is important to document successful and unsuccessful transitions to help technology departments make sound decisions, convince others that their solutions are professional and visionary, and to share expertise across a wide community.

Followup

Two items mentioned in the article are worth investigating further: