X-Git-Url: http://git.tuebingen.mpg.de/?p=paraslash.git;a=blobdiff_plain;f=web%2Fmanual.m4;h=46a2cd62f58e4c25eada652b10a855a60be60f1e;hp=946b9d0953621b23a3a6e30e62c211674d0c6ea5;hb=c41a04fb296e068ebfec78bba9678bf15daea896;hpb=7584638594109184f329bead008f1dcdd9030767 diff --git a/web/manual.m4 b/web/manual.m4 index 946b9d09..46a2cd62 100644 --- a/web/manual.m4 +++ b/web/manual.m4 @@ -251,6 +251,10 @@ Optional: Linux, you'll need to have ALSA's development package libasound2-dev installed. + - XREFERENCE(http://downloads.xiph.org/releases/ao/, + libao). Needed to build the ao writer (ESD, PulseAudio,...). + Debian package: libao-dev. + Installation ~~~~~~~~~~~~ @@ -280,7 +284,11 @@ might need to tell the configure script where to find them. Try ./configure --help to see a list of options. If the paraslash package was compiled -successfully, execute as root, +successfully, execute (optionally) + + make test + +to run the paraslash test suite. If all tests pass, execute as root make install @@ -307,7 +315,7 @@ following commands: user=bar target=~/.paraslash/server.users - key=~/.paraslash/key.pub.$user + key=~/.paraslash/id_rsa.pub.$user perms=AFS_READ,AFS_WRITE,VSS_READ,VSS_WRITE mkdir -p ~/.paraslash echo "user $user $key $perms" >> $target @@ -315,20 +323,25 @@ following commands: Next, change to the "bar" account on client_host and generate the key pair with the commands - key=~/.paraslash/key.$LOGNAME - mkdir -p ~/.paraslash - (umask 077 && openssl genrsa -out $key 2048) + ssh-keygen -t rsa -b 2048 + # hit enter twice to create a key with no passphrase -para_server only needs to know the public key of the key pair just -created. It can be extracted with +This generates the two files id_rsa and id_rsa.pub in ~/.ssh. Note +that paraslash can also read keys generated by the "openssl genrsa" +command. However, since keys created with ssh-keygen can also be used +for ssh, this method is recommended. - pubkey=~/.paraslash/key.pub.$LOGNAME - openssl rsa -in $key -pubout -out $pubkey +Note that para_server refuses to use a key if it is shorter than 2048 +bits. In particular, the RSA keys of paraslash 0.3.x will not work +with version 0.4.x. Moreover, para_client refuses to use a (private) +key which is world-readable. -Copy the public key just created to server_host (you may skip this step -for a single-user setup, i.e. if foo=bar and server_host=client_host): +para_server only needs to know the public key of the key pair just +created. Copy this public key to server_host: - scp $pubkey foo@server_host:.paraslash/ + src=~/.ssh/id_rsa.pub + dest=.paraslash/id_rsa.pub.$LOGNAME + scp $src foo@server_host:$dest Finally, tell para_client to connect to server_host: @@ -560,19 +573,6 @@ execute. The output of contains in the third column the permissions needed to execute the command. -A new RSA key can be created with - - openssl genrsa -out 2048 - -and the public part may be extracted with - - openssl rsa -in -pubout -out - -Note that para_server refuses to use a key if it is shorter than 2048 -bits. In particular, the RSA keys of paraslash 0.3.x will not work -with version 0.4.x. Moreover, para_client refuses to use a (private) -key which is world-readable. - It is possible to make para_server reread the user_list file by executing the paraslash "hup" command or by sending SIGHUP to the PID of para_server. @@ -1500,9 +1500,9 @@ Forward error correction ~~~~~~~~~~~~~~~~~~~~~~~~ As already mentioned REFERENCE(Streaming protocols, earlier), -paraslash uses forward error correction (FEC) for the unreliable -UDP transport. FEC is a technique which was invented already in -1960 by Reed and Solomon and which is widely used for the parity +paraslash uses forward error correction (FEC) for the unreliable UDP +and DCCP transports. FEC is a technique which was invented already +in 1960 by Reed and Solomon and which is widely used for the parity calculations of storage devices (RAID arrays). It is based on the algebraic concept of finite fields, today called Galois fields, in honour of the mathematician Galois (1811-1832). The FEC implementation @@ -1529,7 +1529,7 @@ From these observations it is clear that there are three different FEC parameters: The slice size, the number of data slices k, and the total number of slices n. It is crucial to choose the slice size such that no fragmentation of network packets takes place because -FEC only guards against losses and reodering but fails if slices are +FEC only guards against losses and reordering but fails if slices are received partially. FEC decoding in paralash is performed through the fecdec filter which @@ -1674,6 +1674,11 @@ write the PCM data to a file on the file system rather than playing it through a sound device. It is supported on all platforms and is always compiled in. +*AO*. _Libao_ is a cross-platform audio library which supports a wide +variety of platforms including PulseAudio (gnome), ESD (Enlightened +Sound Daemon), AIX, Solaris and IRIX. The ao writer plays audio +through an output plugin of libao. + Examples ~~~~~~~~ @@ -2028,7 +2033,7 @@ detection of duplicate or reordered packets. Being a connectionless protocol, only minimal internal state about the connection is maintained, which means that there is no protection against packet loss or network congestion. Error checking and correction (if at all) -are performed in the application.' +are performed in the application. *DCCP*. The _Datagram Congestion Control Protocol_ combines the connection-oriented state maintenance known from TCP with the