Enter a random password for auth2 authentication :

This must be up to eight characters in length.

Enter a random password for volutil authentication :

This must be up eight characters in length and different from the auth2 password.

Enter a random password for update authentication :

There are no length limitations, preferable it is different from the auth2 and volutil passwords.

Do you want to start the server at boot time? (y/n)

Answering yes to this question creates the file /vice/srv/STARTFROMBOOT , which must be present for either rc.vice or vice.init to start the server at boot time. Removal of this file will prevent the Coda server from starting automatically at boot time.

Is this the master server, aka the SCM machine? (y/n)

For the first Coda machine being setup in a Coda cell, the answer must be yes . If you are adding a server to an existing Coda cell, the answer must be no .

If you have answered no to the above question, you will be asked for the HOSTNAME of an existing SCM:

Enter the hostname of the SCM machine :

This question is only asked if the machine is not the SCM. The host name entered must be that of the SCM which distributes the Coda cells database and global configuration files.

If you have answered yes to the question about setting up master SCM machine, you will see the message: Now installing files specific to the SCM... and get following questions:

serverid:

All servers in a coda cell need to have a unique number to identify them. The servername to identifier mappings have to be defined by the administrator in the file /vice/db/servers on the SCM according to the following format:

          servernameX .domain.name         1
          servernameY .domain.name         2
          ...

There are currently several limitations to which identifiers are actually usable:

• all numbers must fit in a single byte;

• 0 and -1 (255) are used in error conditions;

• 127 is used to identify `replicated volumes'.

This leaves us with a usable range of 1-126 and 128-245 for server identifiers.

Enter the name of the rootvolume (
<
32 chars) :

Enter the name of your root volume (e.g.

coda.root

)

After creating root volume system will create privileged user for managing Coda servers. You will see following message:

You need to give me a uid (not 0) and username (not root)
for a Coda System:Administrator member on this server,
(sort of a Coda super user)

Enter the uid of this user:

We recommend you to enter uid of your local account, using which you will administer Coda servers.

Enter the username of this user:

Enter your username

If operation was successful, you should see following message:

An initial administrative user


username


(id


uid


) with Coda password changeme now exists.

Are you ready to set up RVM? [yes/no]

RVM is the Recoverable Virtual Memory used to keep a copy of Coda Virtual memory on local disk. Answer yes to this question or the setup will abort.

What is your log partition?

While RVM can be placed in regular file, it is strongly recommended to allocate a small partition on a dedicated disk for this purpose. If you have set aside, for example, /dev/sdc1 under Linux as the log partition, enter the partitions' device name at the prompt.

The maximum template size we provide for and have tested is 30MB.

What is your log size? (enter as e.g.  '12M')

The log partition keeps transaction records for Coda volume updates that may not have been written to the Coda data partition yet. We have not extensively tested values above 30MB and do not recommend more than this. 12MB is a good value for a small to medium sized server. The value may be entered as, 12M or 12288 for 12 Megabytes. Read Section 7.3.1.2 for a more detailed explanation.

What is your data partition (or file)?

This allows you to specify a partition or file. We strongly recommend a partition which can reside with other system partitions. Remember, if you use a partition, you are using it "raw" . it does not contain a file system of any kind. Again, if you are using Linux, you may enter a block device name such as /dev/sdc1 .

What is the size of you data partition (or file) [22M,44M, 90M, 130M]:

This specifies the the size of the RVM data partition. It must be typed exactly as 22M , 44M , 90M , or 130M . These are associated with default parameters that must be feed to codasrv when it is started. The following table provides an approximate RVM data size to total data storage conversion:

• 22M is good for up to 500MB;

• 44M is good for up to 1.0GB;

• 90M is good for up to 2.2GB;

• 130M is good for up to 3.3GB.

For a detailed explanation of the trade off between different RVM data sizes vs. data storage space, please see Section 7.3.1.1 .

Proceed, and wipe out old data? [y/N]

WARNING 
if you have entered erronous entries for RVM log
and RVM data partitions, you could damage your system.  Be sure you
entered correct information!
This is the last chance before any action is taken by the setup script.
Enter

y

to commit or

N

to abort.

Where shall we store your data [/vicepa]?

Older development versions of coda require /vicepa to be present. This version does not. You give a name other than the default. However, we strongly advise not calling it /coda as that can be confused with venus.

Once you successfully complete vice-setup you can start your Coda file-server.