Source code for arlad.

[wwshen@engin.umich.edu]

   When I run the arlad, I have the following questions.
Type: more /afs/umich.edu/README. Then I get the following
information from the screen: ??? This is my questions???

more /afs/umich.edu/README

SWW>> in process_message res=20
proc_msg: byte = 20
Rec message: opcode = 2 (getroot), size = 20

??? 1. Why does arlad get the opcode for getroot from xfs. This
may be related to the "more"???

cj>> cred_get: type == CRED_NONE
sww>> e->type=0, e->securityindex=0, e->cell=0, e->flags.killme=0
cj>> read_attr calling do_read_attr
SWW>> read_attr calling do_read_attr done ret=0
Multi-send: opcode = 3 (installroot), size = 120

??? 2. Similar to Question 1. Why do we need this function for arlad???

multi-sending wakeup: seq = 338, error = 0
SWW>> Does the arlad send a message to xfs now???
SWW>> in process_message res=20 the 1th time
SWW>> in process_message res=292
proc_msg: byte = 36
Rec message: opcode = 4 (getnode), size = 292
cj>> cred_get: type == CRED_NONE
sww>> e->type=0, e->securityindex=0, e->cell=0, e->flags.killme=0
 
 
SWW 03/29/98:
 
 read_data
 
mmap_copyrx2fd: file size=6144 content:
 
 ................ /* Unreadable text */
  
??? 3. What does the arlad get from the file server ???


************************************
cj>> read_attr calling do_read_attr
SWW>> read_attr calling do_read_attr done ret=0
 
 
SWW 03/29/98:
 
 read_data
 
mmap_copyrx2fd: file size=21 content:
#umich.edu:root.cell.

??? 4. It seems that arlad communicates with the server
again and get the cell name. why???


************************************
cj>> read_attr calling do_read_attr
SWW>> read_attr calling do_read_attr done ret=0
Multi-send: opcode = 5 (installnode), size = 392

??? 5. Why does arlad get the upcode installnode from xfs???

multi-sending wakeup: seq = 339, error = 0
SWW>> Does the arlad send a message to xfs now???
SWW>> in process_message res=292 the 1th time
SWW>> in process_message res=324
proc_msg: byte = 32
Rec message: opcode = 10 (inactivenode), size = 32

??? 6. What does this function do? It seems to be appeared 
many times in this case???

cj>> cred_get: type == 0
sww>> e->type=0, e->securityindex=0, e->cell=0, e->flags.killme=0
SWW>> in process_message res=324 the 1th time
proc_msg: byte = 36
Rec message: opcode = 4 (getnode), size = 292
cj>> cred_get: type == CRED_NONE
sww>> e->type=0, e->securityindex=0, e->cell=0, e->flags.killme=0
 
 
SWW 03/29/98:
 
 read_data
 
mmap_copyrx2fd: file size=2048 content:

   ....
??? 7. Again, arlad gets some unreadable file from the server.
Is it related to the file we want to read???


************************************
cj>> read_attr calling do_read_attr
SWW>> read_attr calling do_read_attr done ret=0
Multi-send: opcode = 5 (installnode), size = 392
multi-sending wakeup: seq = 341, error = 0
SWW>> Does the arlad send a message to xfs now???
SWW>> in process_message res=292 the 2th time
SWW>> in process_message res=68
proc_msg: byte = 32
Rec message: opcode = 10 (inactivenode), size = 32
cj>> cred_get: type == 0
sww>> e->type=0, e->securityindex=0, e->cell=0, e->flags.killme=0
SWW>> in process_message res=68 the 1th time
proc_msg: byte = 36
Rec message: opcode = 6 (getattr), size = 36
cj>> cred_get: type == CRED_NONE
sww>> e->type=0, e->securityindex=0, e->cell=0, e->flags.killme=0
Multi-send: opcode = 7 (installattr), size = 120
multi-sending wakeup: seq = 343, error = 0
SWW>> Does the arlad send a message to xfs now???
SWW>> in process_message res=36 the 2th time
SWW>> in process_message res=100
proc_msg: byte = 32
Rec message: opcode = 10 (inactivenode), size = 32
cj>> cred_get: type == 0
sww>> e->type=0, e->securityindex=0, e->cell=0, e->flags.killme=0
SWW>> in process_message res=100 the 1th time
proc_msg: byte = 32
Rec message: opcode = 10 (inactivenode), size = 32
cj>> cred_get: type == 0
sww>> e->type=0, e->securityindex=0, e->cell=0, e->flags.killme=0
SWW>> in process_message res=68 the 2th time
proc_msg: byte = 36
Rec message: opcode = 6 (getattr), size = 36
cj>> cred_get: type == CRED_NONE
sww>> e->type=0, e->securityindex=0, e->cell=0, e->flags.killme=0
Multi-send: opcode = 7 (installattr), size = 120
multi-sending wakeup: seq = 346, error = 0
SWW>> Does the arlad send a message to xfs now???
SWW>> in process_message res=36 the 3th time
SWW>> in process_message res=72
proc_msg: byte = 32
Rec message: opcode = 10 (inactivenode), size = 32
cj>> cred_get: type == 0
sww>> e->type=0, e->securityindex=0, e->cell=0, e->flags.killme=0
SWW>> in process_message res=72 the 1th time
proc_msg: byte = 40
Rec message: opcode = 12 (open), size = 40
cj>> cred_get: type == CRED_NONE
sww>> e->type=0, e->securityindex=0, e->cell=0, e->flags.killme=0
open: before cm_getattr
open: after cm_getattr
open: before cm_open
SWW 03/29/98: enter cm_open
 
??? 8. Now we get the file but why does arlad do so many
above functions? I can not understand the function inactivenode.??? 
 
SWW 03/29/98:
 
 read_data
 
mmap_copyrx2fd: file size=1291 content:
From: /afs/umich.edu/README
 
 
              umich.edu -- The University of Michigan Cell
 
 
 
Top-level is composed of several directories, containing the following:
 
 
 
Directory       Description
------------+------------------------------------------------------------------
group           One home directory for each group.
                   This tree is a heirarchy of organizations,
                   so the path to a given group would descend
                   through the larger groups of which it is part.
 
system          System binaries for several architectures.
 
class           One home directory for each class.
                   This tree is relatively flat.  Each class
                   has it's own home directory.  Layout within
                   the home directory is up to the class instructors.


   All right. Thank you very much for your answer in advance.
wuwei