ComputerLab

Differences between revisions 7 and 8
Revision 7 as of 2008-08-06 16:33:48
Size: 3925
Editor: localhost
Comment: converted to 1.6 markup
Revision 8 as of 2008-08-12 20:02:10
Size: 4018
Editor: 205
Comment:
Deletions are marked like this. Additions are marked like this.
Line 15: Line 15:
 * C SetupAndConfigureUbuntu804ThinClientServer
 * A SetupAndConfigureUbuntu606ThinClientServer
 * C HardyClassroomServer (with LTSP and edubuntu)
 * A DapperClassroomServer (with LTSP and edubuntu)
Line 25: Line 25:
 * A SetupPrometheanBoard
Line 28: Line 29:
 * B Dual-boot on Intel based iMac--both Mac and Ubuntu
Line 29: Line 31:

How do you setup and configure the Hardware and Software that will best serve these thin-client-enabled High School Science classrooms?

Description: A Computer Lab in school terminology, at least in MN, refer to a single classroom with a whole bunch of computers where students (typically) come and learn how to use some app or do some computer-oriented task. The computers are often arranged on top of tables around the edge of the room and in an 'island' or islands in the center. This layout of computers in the class is different from what the GCoS project will be using. See this photo for a picture of a partially completed table: http://groosd.blogspot.com/2008/07/less-messy-though-still-all-over-place.html Four students will be sitting at each table, 1 computer per 2 students. Students will view the LCD monitors through the glass table top. The focus of the class isn't computers but instead Science; computers will be an important tool by which the Science is done/learned.

Setting up a Computer Lab

Challenges to solve, tasks to do: All tasks are highly important for a successful ComputerEnabledScienceClassroom and are here for documentation purposes as well as coordinating their accomplishment. Some of the tasks/challenges are more urgent than others in this current project! Deadline is September 1 2008! They are rated for urgency to meet this deadline: A=Most Urgent, B=Urgent, C=Less Urgent (rankings will change as challenges are accomplished). THANKS!

Solving many of these challenges will generally require working on a thin client server. How can this be done? Brian came up with an excellent idea and has generously offered to host the thin client server at his place of work at TIES. Thank you TIES! So, if you would like to help out you can ssh into machine, work on the solution, documenting your efforts on the appropriate wiki page in the list below. At the end of the summer (that is September 1st) we will be erasing the machine, putting a fresh copy of Hardy Heron, and then apply all the solutions documented here in the wiki. E-mail me at <djgroos AT gmail DOT com> if you are interested and I'll set up an account on the machine for you and give you the ip. THANKS!

At this point most if not all of the pages below are just "potential pages", in other words, when you click on the link, it will ask you to select a template for the new wiki page you are creating (I've been using the first one on the list: Accessibility/Testing/Task-Template but use whatever you see as best), and start to customize the page! Any questions/comments let me know! <djgroos AT gmail DOT com>

Find and configure the best Apps for different purposes

Comments:

v1

v2

v3

m1

m2

m3

ComputerLab (last edited 2009-01-19 18:04:03 by 75-168-232-204)