CSED 430-001, LT-412 (Linux lab)

Week	date
1	8/27/07
	9/3	labor day
2	9/10
3	9/17
4	9/24
5	10/1
	10/8	midsemester break
6	10/15
7	10/22	exam 1
8	10/29
9	11/5	
10	11/12
11	11/19	Thanksgiving
12	11/26
13	12/3	last class

Final:	12/10


LT-410, Wednesdays 5:45-8:15

Week 1:

Introductions, groundrules, midterm+final

Some evenings we will devote some time at the end of class to Labs.

Laptop lab

===============================

We will start with some XP-oriented stuff, and begin using DiNicolo in earnest
later. However, read pp 149-156 on NTFS file permissions for Sept 10.

XP/Windows:
	desktop
	permissions, sharing
	user accounts
	privileges
	the registry
	network clients
	user rights assignment
	user profiles

===============================

1. Unix view of computing
	every user has a HOME DIRECTORY
	everything runs under the ownership of that user
	A user's files are also owned by that user; typically not writeable by others
	No user has write permission to system files
	Users MEMORY is safe from other-user read/write
	
This provides good system integrity: users can't read each others' files (without
permission); users can't modify system files.

2. 1980's PC view of computing: one box, one user
	User has complete control over the machine
	The only reason for gathering your files into one folder is to make
	   backups easier
	Users can install new software: either intentionally or un (viruses)
	
3. Windows Lab: 
	A user can log into any machine, and see the same environment (mostly)
	A machine can be logged into by any user.
		School: 100 machines / 1000 users ???
	Users don't "see" one another
	Users can't modify basic configuration 
		* with good intentions
		* maliciously
		* unintentionally through a virus
	Users have a "home folder" (My Documents)
	
	Network drives
	
Protecting memory: built into operating system

Two ways of protecting files:
	* local permissions ("client-side")
	* network drives mounted "read-only" ("server-side")
	
YES v NO:
	YES: access to network
	YES: access to network drives
	YES: access to other resources such as databases
	YES: user can run installed software
	YES: access to printer
	NO:  access to printing too many pages, or printing without paying
	NO:  write access to system files
	NO:  installation of software (a kind of write access)
	NO:  viewing other users' files
	NO:  monitoring other users' processes
	NO:  viewing other users' registry settings, eg history
	
Summary of general goals:
	Workstations + Server(s)
	Users are prevented from making undesired modifications to Workstations
	Users are prevented from taking undesired actions with Workstations
		(inappropriate browsing; IM; running apps)
	Users in programming classes can run their programs
	Software updates can be propagated from the server
	"Policy" settings and desktop customization can be established from the server
	
Fixed labs versus notebooks
	our notebook lab
	school notebooks issued to students: Kutztown 13
	
===============================================================================

Some models for labs.

Having personal files stored locally on each machine does NOT work.
	
	1. Everyone uses account GUEST, or NTUSER. 
	   No persistent files; no customization
	   problem: how to be sure email, other passwords aren't saved!
	   
	   Can be implemented with a bunch of "standalone" XP hosts; no server
	   
	2. Everyone has their own account, but there is still no disk space 
	   provided. Need a domain controller & domain to handle accounts,
	   but no disk server or backup plan
	   
	3. Everyone has their own account, plus online disk space

===============================================================================

Assembling a PC:
	case
	power supply
	fans
	
	motherboard
	cpu	(how fast)
	ram	(how much)
	cpufan, shround, connector
	
	pci bus
	video: pci, agp, pci-express
	network
	audio
	
	disk
		cost/gig
		disk partitions
	floppy
		still out there
	cd
	
	keyboard, mouse
		Accessibility options
		Mouse alternatives
	connectors
	
Bios versus OS
	A brief word about DRIVERS
	Safe mode
	
Installing windows
	Might not work!

===============================================================================

Assignment 1: 
create a list of parts required to build your own PC, with prices.
Check out newegg.com.
Look for motherboards with onboard video, sound, & Ethernet.
core parts: 
	motherboard, cpu, ram (must match)
	hard drive (ATA)
	case/fan/power (case comes with cables, usually)
	cd-rom
	
Get one discount-type prebuilt computer quote for comparison.

Bundled free software: sometimes an unbeatable deal, 
	other times free & worth every penny

Due: Mon, Sept 10

Remark: if you *do* build systems from parts, one thing you have to deal with
is whenever something doesn't work, even if it's clearly a windows problem
and not a hardware problem, SOMEONE will wonder if it's your fault.

===============================================================================