Sun's original assumption that each user has a permanent machine allocated to them is not applicable in most environments. Just as users send mail to 'user' rather than 'user@machine', users want to browse others user's calendars and do not care or want to know where the calendar is actually stored. Here is procedure to accomplish our goal.
All calendars will be stored on a central server. The initial setup must be done on the server. A) Have the user login to the calendar host(calhost) machine.
B) Change everyone's .cm. Rc file so that Calendar. DefaultCal points to user@calhost calhost can be an hostname alias or an actual hostname.
You may want to use the alias just in case you change the "calhost" later. C) Change their Access List and Permissions (under Edit/Properties) to show user@client with BID (browse, insert, delete) permissions for any client machine the user wanted to access their calendar from. Notes: If you use the scheme you should not NFS mount /var/spool/calendar on ... more.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.