Jump to ContentJump to Main Navigation
CornellA History, 1940-2015$
Users without a subscription are not able to see the full content.

Glenn C. Altschuler and Isaac Kramnick

Print publication date: 2014

Print ISBN-13: 9780801444258

Published to Cornell Scholarship Online: August 2016

DOI: 10.7591/cornell/9780801444258.001.0001

Show Summary Details

The Wars at Home

The Wars at Home

Chapter:
(p.204) 6 The Wars at Home
Source:
Cornell
Author(s):

Glenn C. Altschuler

Isaac Kramnick

Publisher:
Cornell University Press
DOI:10.7591/cornell/9780801444258.003.0006

This chapter examines student activism at Cornell University that began in early 1965. Nathaniel Pierce convened the first meeting of Students for Education (SFE) on March 8 to air students' grievances, including lack of contact with faculty, the grading system, and James Perkins's recurring absences from campus. Perkins declined to meet with anyone from SFE, but Dale Corson decided to talk to six students. Changes came quickly, such as increasing faculty numbers to reduce the size of classes. This chapter considers how Cornell became a key venue for student antiwar activism on America's campuses because of the moral and strategic leadership provided by Cornell United Religious Work (CURW) and the Cornell chapter of the Students for a Democratic Society. In particular, it discusses the ways that Cornell students staged Vietnam War protests and how Cornell addressed the issue of drug use on campus.

Keywords:   student activism, Cornell University, students, faculty, James Perkins, antiwar activism, Cornell United Religious Work, Vietnam War protests, drug use, Students for a Democratic Society

Cornell Scholarship Online requires a subscription or purchase to access the full text of books within the service. Public users can however freely search the site and view the abstracts and keywords for each book and chapter.

Please, subscribe or login to access full text content.

If you think you should have access to this title, please contact your librarian.

To troubleshoot, please check our FAQs, and if you can't find the answer there, please contact us.