Sat Jun  9 15:14:48 PDT 2001
 - still no word from Anthony Joseph.

Need to look at linux VM to see if it's pedagogically correct.

Solaris:
not all kernel threads have lightweight processes
not all lightweight processes have 
on top of lightweight processes have user threads

on the top; a (user) process contains at least 1 lightweight process
usr threads are scheduled on top of lightweight processes.

there are things called "scheduler activations" 


mutexes
o traditional
o spin (polls)
o adaptive (spin and 2ndary threads go to sleep)

r/w locks
1 writer, multiple readers

semaphors

condition variables

things that are scheduled in solaris:
level 15 - 10 cannot hold normal locks - they hold dispatcher locks
they cause other things to get scheduled. 

things from level 10 interrupts and down:
interrupt threads - scheduler runs at this level
real time threads
system threads
system threads
interactive threads

build architechture:
/babylon 
/libraries
/kernel
/user
  /admininstrator
  /applications
  /utilities 

/kernel
        /include
        /libraries
        /filesystems
        /architechtures
        /vm
        /syscalls

Legal stuff: what license?
ask around for best lic for the _course_ (i.e. we need to copyright
things like the lecture notes, this is copyright for an "OS Course")
fdl?  - probably gpl the code itself, but the rest of the lic is ??

Process <-> scheduler activations    user threads
                                     LWP
                                     kernel threads
(kernel threads)

cvs repository located on: /mnt/tda/babylon