@device(imprint10)
@make(report)
@style(spacing 1, font computermodernroman11, indent 0)
@pageheading(left "@b(Project Athena)", center "@value(page)",
right "@b(May 6, 1985)")
@begin(titlepage)
@begin(majorheading, flushright)
Student Accounts at End of Term
@end(majorheading)
@blankspace(1 inch)
@begin(heading,flushright)
MIT Project Athena
Revision C 
May 6, 1985
@end(heading)
@end(titlepage)

@section(Introduction)

As the end of term nears, you may be wondering about the fate of your
Athena account when classes are over.  This handout
provides a general overview of what will happen and what you will need
to do. If you have an Athena account that was established for a course
this term, or if you are on the degree list and plan to graduate in June,
please read on. 

@subsection(If You Have an Athena Course Account . . .)

You should note that your course account and its associated files
will be removed by the end of the term.
If you want to save any of those files,
you must transfer them to your Student Center account,
or to floppy disk.

What accounts will be affected?  All student accounts established for
Athena-supported courses.  These student accounts have
been, in most cases, established on Athena machines located in one of
the following Athena facilities: building 11, building 1, building 66,
building 38, building 2, building 4, building 6.
See your course's account administrator to find out the exact date
at which your account will be removed.
The date will vary from course to course.

If you are an undergraduate student,
you should already have an account
at the Student Center (Building W20).
Those of you who will be registering again next term as an
undergraduate can use this account in the Fall Term apart
from any specific courses.
If you have any files on your course account
that you want to save for next term,
you must move them to your W20 account before the end of this term.
You will be able to transfer your files over the network
using the easy @i(moveme) command or standard Unix file transfer utilities.

If you are a graduate student who received an Athena account this term
for use in a particular course you will not have access to an account at
the Student Center at this time because of lack of space.  You must
therefore copy any files on your course machine that you wish to keep to
floppy disk.  You will be able to do this using IBM PCs located at the
Student Center facility.

@subsection(If You are Graduating . . .)

Note that,
in addition to losing any course accounts
you might have,
you will also lose access to your
W20 account as of June 15, 1985.
If you want to keep any of your files,
you must transfer them to floppy disk before the deadline.
See the last section of this document for the specifics of floppy
disk file transfer.

Note that this policy affects those of you who are
graduating and leaving MIT forever,
@b(as well as) those of you who will be registering next fall as
graduate students.
We just don't have enough space on the Student Center machines for
non-undergraduates.
Sorry!

@subsection(Accounts that Will Remain Unscathed)

What accounts will not be affected?  Students who have accounts that were
established for Athena curriculum development projects will not be
affected (unless of course they are no longer working on these
projects).  Student accounts established at the Student Center facility
for undergraduate students who will be registering again in the Fall
Term will not be affected.  (Student accounts on Student Center machines
belonging to students who are graduating are a special case as mentioned
above.)

The rest of this document contains detailed information on your
Student Center account (for those who have not used their accounts yet),
and shows you how to move files,
either to your Student Center account or to a floppy
disk, and what to do if you have problems.

@section(
Your Student Center Account
)

Those of you who have yet to use your Student Center account
will need to know the following information.
Your Student Center account has been assigned
to one of the W20 "Ringworld" cluster machines
according to the first letter of your last name:
@example{
  Last Name Begins with           Machine

        A-C                       louiswu
        D-H                       nessus
        I-L                       prill
        M-R                       speaker
        S-Z                       teela
}    

What password do you use to login to your W20 account?
Your password should be the same on all your accounts,
so unless you have changed your course account password within the
last twenty-four hours,
use your course account password.
If you have just changed your course account's password,
you may need to use its previous password to login to your
W20 account.
The new password should become effective on your W20 account
within one day.

Your W20 account has the "owner-only"
file protection permissions typical of all
new Athena accounts.
It differs
from your course account in a couple of ways:
@itemize[
@b(Your Student Center account has much less disk space for file storage.)
Whereas your Course account lets you use up to 2500 disk blocks to
store your files
(each disk block holds up to 1024 bytes of information),
your Student Center account limits you to 250 blocks.
Clearly,
you can't store as much information in your Student Center account
as you can in your course account.

Unless you have already transferred
files from your course machine to your
Student Center machine,
your Student Center account does not have any of your
personal files from your course account.
If you want to save any of your course account files,
you must move them to your Student Center account before
your course account gets deleted.
]

@section(
Moving Your Files
)

@b(Athena will not transfer files for you; it is @i(your) responsibility.)
Moving your files should be easy.  But, just in case you encounter
difficulty,
Athena consultants will be available at the Student Center cluster
Sunday through Thursday
from 7 - 9PM, until May 15.
After that date,
please check the white board at the W20 cluster for the
consultants' schedule.
We strongly advise you to move files at the 
Student Center while the consultants are on duty.

Before you begin the process of moving files from your course
account to your W20 account,
you need to decide how you want to do it.
Although Athena has several file transfer programs,
you will probably want to use one of the following two:
@p(moveme), or @p(rcp).

The @i(moveme) utility is used to transfer entire accounts en masse.
You will want to use @i(moveme) if:
@itemize[

You have never used your W20 account,
or have used it sparingly.

You want to save most,
if not all,
of your course account files.]

The @i(rcp) utility is used to transfer individual files
and subdirectories.
You will want to use @i(rcp) if:
@itemize[

You don't want to save all the files in your course account.

Your W20 account is already has a number of files that you want
to keep.]


Perhaps you have a large number of files on both accounts
and you want to save them all.
Unfortunately, you will probably find that your W20 account won't
be able to hold everything you want to keep.
In this instance you will need to move some of your files to floppy disk.
That process is described later in this document.

If you want to transfer your files with @i(moveme),
see the next section.
If you want to use @i(rcp),
see the section "Transferring Files with @i(rcp);
it follows the @i(moveme) section.

@section(
Transferring Files with @i(moveme)
)

@begin(enumerate)
Go to the Student Center Library--fifth floor, W20.

Login to your STUDENT CENTER account first.

@multiple[
Enter the following command: @b(quota)

You will see something like the following:
@begin(example, indent 0)
Disk quotas for dkfritz (uid 7094):
Filsys current quota limit #warns  files quota limit #warns
/mit   134     250   300           16    600   800
@end(example)]

Write down or memorize the number listed under the "current" column;
this is the number of disk blocks you are currently using to store files
on your W20 account.

Get out of your Student Center Account and login to your COURSE account.
(You will be able to login to your Course machine from W20.)
Enter the @i(quota) command and again note the number listed under the
"current" column. This is the number of disk blocks you are using to
store files on your Course account.
Add the two numbers together. If the result is less than 250 disk blocks,
you won't have any problems moving all of your course account files to
your W20 account.
Skip down to step 7.

@begin(multiple)
If the the disk block total is larger than 250,
you won't be able to fit all your files onto your W20 account.
You will have to remove files from either your course account,
your W20 account,
or both.
  
You can do two things with your excess files:  
@enumerate{
delete them forever, or

copy some of them onto a floppy disk first, then delete them from
their respective accounts. If you elect this option see the last section of
this document for directions.
}

If you choose to delete your excess files, you will next have to
decide which to remove.
You can determine how many disk blocks each file in an account
takes up by entering the following command:
@example{
 ls -Rsa | more 
}
(The "R" @i(must) be capitalized.)

This will show you, one file per line,
directory by directory,	how many disk blocks each file takes up.

To size an individual file,
use @i(ls) like this:
@example{
ls -s @i(filename)
}

You will see something like this:
@display{
17 @i(filename)
}
The number displayed in front of @i(filename) indicates
the number of disk blocks used to store the file.

To find the total number of blocks used by a subdirectory
and its associated files,
use @i(ls) like this:
@example{
ls -Ras @i(directoryname)
}
(The "R" @i(must) be capitalized.)

You will see something like this:
@display{
total 42
   1 .	         9 @i(file2)     4 @i(file5)
   1 ..	         1 @i(file3)     7 @i(file6)
   3 @i(file1)  16 @i(file4)
}

The numbers in front of the individual files
indicate the number of disk blocks
used to store them,
and the @i(total) number indicates the number of
blocks used to store the entire directory.

Also check the subdirectories on
both accounts for @i(core) files.
The computer creates these files in response to certain error conditions.
They are notorious consumers of disk space,
and unless you are a programmer trying to diagnose bugs in the system,
you can probably do without them.
From each home directory you can use the @i(find) utility to
display the pathnames of all @i(core) files:
@example{
find . -name core -print
}

When you have decided which files to delete,
use @i(rm) and @i(rmdir)
to get rid of the excess. (The free
Athena document @i(Essential Unix) explains how to use these
commands in its "Files" and "Directories" sections.)
Periodically type the @i(quota) command
to determine how you're doing.
When the total number of disk blocks between your W20 and course
accounts reaches 250, you are done.
@end(multiple)

Login to your W20 account.

@begin(multiple)
You are now ready to copy all of your course account files
to your W20 account en masse.
Be aware that @B(if you have already created files on your
W20 account that have the @p(same name) as the "incoming" files on
your course account, these W20 files will be overwritten).

Now, @i(on your W20 machine) type: @b( moveme)

You will see something like:
@example{You are logged into louiswu.  I assume that is where to copy TO.
Is this the case? (Answer y or n)  y
Enter the name of the machine you want to copy FROM:
}

Type the name of your course machine and RETURN.  @i(Moveme) will
give you a running chronicle of the steps it is taking to transfer
your files.  Essentially, it is doing what we told you to do above:
checking to see that there's room on the W20 machine's disk packs
for files, checking to see that you won't exceed your quotas on
your W20 machine, trying to make sure you're doing the copy in
the right direction, etc.

Don't interrupt the process mid-stream.
If you do happen to interrupt @i(moveme) with CTRL-C before it has
completed, it is better to just @i(moveme) all over again from
the beginning than to try to piece things together.  Remember,
@i(moveme) is just a copy operation.  All your files on your
course machine are untouched.
 
If you do not have enough space on your W20 account for your course files,
the @i(moveme) program will abort with an explanatory message.  Go back
to step 2.   Do not pass GO.  Do not collect $200.
@end(multiple)

After @i(moveme) completes the transfer of your files to your W20 account,
you should do a spot check of your files to make sure that the move
went smoothly.
Note that @i(moveme) preserves your original directory structure.
@end(enumerate)

@section(
Transferring Files with @i(rcp)
)

@begin(enumerate)
Go to the Student Center Library--fifth floor, W20.

Login to your STUDENT CENTER account first.

@multiple[
Enter the following command: @b(quota)

You will see something like the following:
@begin(example, indent 0)
Disk quotas for dkfritz (uid 7094):
Filsys current quota limit #warns  files quota limit #warns
/mit   134     250   300           16    600   800
@end(example)]

Note the number listed under the "current" column;
this is the number of disk blocks you are currently using to store files
on your W20 account.
Subtract this number from 250 and that will tell you how many disk
blocks your W20 account has left to store files from your course account.

Get out of your Student Center Account and login to your COURSE account.
(You will be able to log to your Course machine from W20.)

@multiple[
You can use the @i(ls) command with the @i(s) option to
determine the number of disk blocks used by the files and directories
that you plan to move to your W20 account.
To size an individual file,
use @i(ls) like this:
@example{
ls -s @i(filename)
}

You will see something like this:
@display{
17 @i(filename)
}
The number displayed in front of @i(filename) indicates
the number of disk blocks used to store the file.

To find the total number of blocks used by a subdirectory
and its associated files,
use @i(ls) like this:
@example{
ls -Ras @i(directoryname)
}
(The "R" @i(must) be capitalized.)

You will see something like this:
@display{
total 42
   1 .	         9 @i(file2)     4 @i(file5)
   1 ..	         1 @i(file3)     7 @i(file6)
   3 @i(file1)  16 @i(file4)
}

The numbers in front of the individual files
indicate the number of disk blocks
used to store them,
and the @i(total) number indicates the number of
blocks used to store the entire directory.

Add up the number of disk blocks used by all of the
files and subdirectories you want to move from your course
account to your W20 account.
If that number is less than the number of free blocks left
on your Student Center machine,
you can begin transferring the files.
Skip to step 8.
]

@multiple[
If the disk block total is larger than the number of free blocks,
you will not be able to fit everything on your W20 account.
You will have to remove files from your W20 account,
or remove files from the set you want to save from your course account.
  
You can do two things with your excess files:  
@enumerate{
delete them forever, or

copy them onto a floppy disk first.
If you elect this option see the last section of
this document for directions.
}

If you choose to delete your excess files, you will next have to
decide which to remove.
First check among the files you want to save on
both accounts for @i(core) files.
The computer creates these files in response to certain error conditions.
They are notorious consumers of disk space,
and unless you are a programmer trying to diagnose bugs in the system,
you can probably do without them.

When you have decided which files can be deleted,
use @i(rm) and @i(rmdir)
to get rid of the excess. (The free
Athena document @i(Essential Unix) explains how to use these
commands in its "Files" and "Directories" sections.)
If you are removing files from your W20 account,
periodically type the @i(quota) command
to determine how many free disk blocks you are creating.
When the number of blocks used to store the course account files you want
to save is less than the number of free blocks contained in your W20 account,
you are ready to use @i(rcp).
@end(multiple)

@begin(multiple)
@i(Rcp) is a versatile utility that lets you
transfer individual files as well as entire subdirectories.
@b(A word of warning before you begin:)
@i(rcp) will overwrite W20 account files and
subdirectories whose pathnames match those of
"incoming" files or subdirectories.
For that reason, we suggest that you create a new directory on your W20
account in which to receive the course files.
You can move the incoming files to other directories within your W20 account
once you have finished transferring them.

Make sure you are logged in to your W20 account and are in your home directory.
Create a new directory as follows:
@example{
mkdir receive
}
(I picked the name "receive" because it makes sense to me;
you can call the directory whatever you wish.)

Next change your current directory to the new directory:
@example{
cd receive
}
Now you are ready to begin transferring files.

If you want to move files over one at a time,
use @i(rcp) as follows:
@example{
rcp @i(machinename:filename)   @b(.)
}
where "machinename is the name of the machine you are
moving files from,
and "filename" is the file's name on that machine.
You must include the "." because it tells @i(rcp)
that you want the file moved to your current directory.

Let's say,
for instance,
that you have a course account on hera.
If you wanted to move your @i(.cshrc) file from that account,
you would use @i(rcp) as follows:
@example{
rcp hera:.cshrc    @b(.)
}
Suppose that you have a directory @i(papers) on your hera account
that you use to store term papers.
If you wanted to move a file named @i(shakespeare) from that
directory,
you would use @i(rcp) like this:
@example{
rcp hera:papers/shakespeare    @b(.)
}

You may want to use @i(rcp) to move an entire subdirectory.
Use it like this:
@example{
rcp -r @i(machinename:directoryname)   @b(.)
}
If,
for instance,
you wanted to move a directory named @i(programs) on your hera account,
the @i(rcp) command would look like this:
@example{
rcp -r hera:programs    @b(.)
}

After you have finished moving your course files to your W20 account,
you should do a spot check to make sure that everything came across
smoothly.
When you are satisfied with the results,
move the "new" files to their appropriate places within
their new home.

@end(multiple)
@end(enumerate)
@section(
Problems
)

What are some of the problems you may encounter when transferring files?

@b(You have trouble logging in to your W20 account.)  Check first to make
sure that you are trying to login to the correct machine at the Student
Center.  There are five possible machines there; check
the assignment list above.  Also, are you using
the right password?  If you cannot successfully login to your
Student Center account you should talk to the student consultant
on duty.  If no consultant is available, call your new all-students
Account Administrator at 3-1548.

@b(You get the message "Network unreachable." when you try to login
to your course account from the Student Center.)
This means that there is a temporary
problem with the network link between W20 and your course machine.  Try again
later. 

@b(You try the @p(moveme) command and get the message "Permission denied".)
This could be several things, each of which would be rather
difficult to diagnose.  It is best to see a Student Consultant.

The rest of @i(moveme)'s error messages are pretty self explanatory.
Most have to do with trivial errors like typing the host machine
name wrong or quota problems.

If you get the message "Tar finished with an indication that something
went wrong,"
spot check the files to see if in fact something did go wrong.
Chances are everything is all right.
If something did go wrong,
try using @i(moveme) again.

If @i(moveme) produces a list of filenames followed by the message
@example{
These files were on@i(from machine), but are not on @i(new machine).
The move must have failed. Try again.
}
You will have to retry @i(moveme).

@b(When using @i(rcp) you get one of the following two messages:
@example{
WARNING:disk quota (/mit) exceeded

or

DISK LIMIT REACHED (/mit) - WRITE FAILED
})
You have tried to transfer too many disk blocks worth of information.
If you don't have enough space on your W20 account to save all the
files you want,
you need to transfer some of those files to floppy disk.
See the next section of this document for directions.
The first message indicates that @i(rcp) was able to move the
file or subdirectory intact to your W20 account.
The second message indicates that the file or subdirectory
didn't make it intact.
Before you logout of your W20 account,
make sure you have removed enough files to get yourself back under
the quota.

In any event, the best thing to do is to see a Student Consultant
for help during the hours noted at the beginning of the "Moving Your
Files" section.

@section(
Transferring Files to Floppy Disk
)
The following paragraphs are for those of you who,
for one reason or another,
need to transfer files from an Athena computer to floppy disk.
The procedure described below will work with any
IBM PC/XT that is located in the W20 cluster;
it will @i(not) work on a non-Athena PC unless
that PC has been configured to look like an Athena IBM XT

Keeping Athena files on floppy disks is useful if you are exceeding
your disk quota but don't want to just delete the data forever.  It is
also useful
to transfer files between machines, to backup important data, and
to archive files.  Do not transfer any files but your own, for both
legal and moral considerations.

There are two kinds of files.  @b(Ascii text files) are files you can read
using the Unix @b(cat) or @b(more) commands.  @b(Binary files) (compiled
and linked programs, usually) appear only as garbage characters when you
try to look at them with @b(cat) or @b(more).  Both kinds
of files, ascii text and binary, can be stored on IBM PC floppy disks
and successfully restored to Unix.  However, only ascii files can be
used with PC-DOS while they are on the floppy because the PC stores
binary data in a different format than Unix.

@subsection(
Where to Buy Floppies
)
Before you can transfer any files to floppy disk, you need a blank
floppy disk.  Most computer stores sell floppies.  Buy
quality; it's your data.  On the MIT campus,
they can be purchased at the
Information Systems Microcomputer Center in 11-209.  The Micro Center is
open 11 a.m. to 3 p.m. weekdays.  You can also sometimes get them
at the Coop.  You must buy floppies with @B(all)
of these characteristics:
@BEGIN(ITEMIZE, SPREAD 0)
5 1/4 inch size

soft-sector  (Sometimes the "soft-sector" part will not be mentioned on
the disk.)

double density  (Sometimes "double" is called "dual.")

double-sided
@END(ITEMIZE)
Each floppy will hold about 360 disk blocks worth of data.
(Each disk block can hold up to 1024 bytes of information.)
To determine the number of disk blocks used by a file
on an Athena machine,
use the @b(ls -s) command.
The Unix
command @b(quota) will show the total number of disk blocks taken
up by all your files.  The PC-DOS command @b(dir a:) will list your
files and their sizes on the floppy disk.
Note that this DOS command gives file size in bytes,
not in Athena disk blocks.
If you want to know how many disk blocks are needed to store
a file stored on floppy disk,
divide its byte-count by 1024 and round up.

@subsection(
To Begin
)
Find an IBM PC/XT in your Athena cluster.
Make sure the XT is displaying a login server prompt.  If hitting
RETURN several times doesn't produce a login prompt, then:
@BEGIN(ITEMIZE,SPREAD 0)
Turn the machine off and wait for at least 15 seconds.

Make sure that there is no floppy disk in drive A; drive A @i(must) be empty.

Turn the machine back on. After a short time, a login prompt will appear.
If the login prompt fails to appear, see a student consultant for assistance.
@END(ITEMIZE)

Login to the Athena machine that has the directory to/from which you will be
transferring your files. Use the Unix @b{cd} command to get into the directory
to/from which the files will be transferred. You can use the @b{mkdir} command
to create a new subdirectory to group together the files being transferred.
@subsection(
Formatting a Floppy
)
A new floppy disk has to be @b(formatted) before it can store data.
To format a new floppy disk or an old one with unneeded data on it:
@BEGIN(ITEMIZE,SPREAD 0)
@i{Warning: Formatting a floppy will permanently destroy all files and data
on it at that time.}

Press:  @B{CTRL-BREAK} (i.e. hold the @b(CTRL) key down while you hit the
@B{BREAK} key in the upper right hand corner of the keyboard).

Type:  @B{Y} in response to the "Terminate batch job?"
prompt and wait for a "C>" prompt, indicating that you are in PC-DOS.

Insert the unformatted PC-DOS floppy disk into drive A.  (See Figure.)
Shut the little tab door.

Type:  @B{format a:} to format the floppy.

You will be asked twice to "Strike a key when ready".  This is a
safety measure to prevent accidental formatting of a floppy disk.  You
may exit from the formatting procedure with the disk unchanged if you
type @B(CTRL-C) before you reply to the second "Strike a key when ready"
prompt.

Type:  @B{Y} in response to the "Format another?" prompt if you want to
format another disk, or type @B{N} to return to terminal mode.
@END(ITEMIZE)

@subsection(
Transferring  Athena Files to the Floppy
)
When naming files to transfer, you can use wildcards (such as *) to
specify a group
of files.  For example, a @I[filename] of @I[*.dat] would transfer all
files in the current Athena directory with extension @I[.dat] (such as:
@i[a.dat, xyz.dat, fred.dat]) to the floppy.  Be careful, however,
that your wildcards do not group together ascii and binary files.
Ascii and binary
must be transferred by different commands.  If you are transferring
binary files you must use @B{-si} instead of
@B{-s} in the command below.  Directories must
be transferred one-by-one; whole subdirectories can @b(not) be transferred
with one command (what Unix calls "recursively").
Some of your files may emerge on the floppy with slightly
different names because PC-DOS has
different file naming rules.

Once you type the Unix @b(kermit)
command below, you have 90 seconds to type @b(receive)
before the
command will time-out and you start to get "Unable to
acknowledge host" messages.  If this happens, type @b(exit) (to kermit) or
@b(c:autoexec) (to PC/DOS) to return to
Unix and start the process over.

@BEGIN(ITEMIZE,SPREAD 0)
Insert the formatted PC-DOS floppy disk that will receive the files
into drive A.  Shut the tab door.

@begin(multiple)
On Unix, type:  @B{/usr/unsupported/kermit -s} @P{filename}

where @I[filename] is
the name of the file(s) on your Athena machine you want to transfer.
After you press the carriage return do not wait for a prompt to
continue. If characters do appear on the screen, just ignore them.
@end(multiple)

Press:  @B{CTRL-BREAK} (i.e. hold the @b(CTRL) key down while you hit the
@B{BREAK} key in the upper right hand corner of the keyboard).

Type:  @B{Y} in response to the "Terminate batch job?"
prompt and wait for a "C>" prompt, indicating that you are in PC-DOS.

Type:  @B{transfer} and wait for the "KERMIT-86>" prompt.

Type:  @B{set baud 9600}

Type:  @B{receive}

Type:  @B{exit} to return to terminal mode.

Remove your floppy disk from drive A, and logout.
@END(ITEMIZE) 

If you get hopelessly stuck, it is best to remove your floppy from the
drive and go back to the "To Begin" subsection.  See an Athena consultant
for help.

You can also use the Kermit program to transfer
your files on floppy back to your Athena account.
For more details,
see the Athena handout @i(Transferring Files between
Athena and PC/XT Floppies).

@section(
Final Words
)

Remember, your course account is doomed to die at the end of the term;
ask your instructor for the exact date.
If you plan to save any of the files associated with that account,
you must move them to your Student Center account
or to floppy disk.

If you have friends who send you mail,
give them your W20 mail address (username@mit-machine).