|
|||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||
ABSTRACT
A web systems course has long been taught as the first core IT course at Brigham Young University. Along with introducing students to a cross-section of client and server scripting environments, this course also requires students to install and administer a variety of web and database servers under both Linux and Windows. To be done well, the server administration portion of the course requires that each student has free access to his own machine, or some approximation of a dedicated machine. Various approaches to providing this environment to students have been investigated. Possibilities include providing dedicated hardware to each student, setting up virtual servers, requiring students to obtain notebook computers, and rapid workstation imaging over a SAN. An approach that is less expensive to the institution than providing individualized hardware, and less expensive to students than requiring the purchase of a notebook computer, is to require that students obtain inexpensive, portable hard drives. The laboratory portion of the web systems course has been redesigned to use student-provided hard drives. Students install Linux on these drives, and configure them so that they will externally boot when connected to any current PC. Windows XP is also installed on each drive, in a virtual machine. Students then install, configure and script applications using Apache, MySQL, Tomcat, and IIS servers. The result is a configuration that provides each student with a system that includes a windows server, a Linux server, and clients of their choosing, all on a virtual network within any PC to which the disk is connected. This paper describes the course laboratory configuration, and how portable drives help achieve the course objectives. The paper also provides recommendations for others considering similar laboratories, including student feedback concerning drive reliability, hardware interoperability, and instructional value. REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
INDEX TERMS
Primary Classification:
General Terms:
|
|||||||||||||||||||||||||||||||||||||||||||