----------------------------
-Install all needed packages
----------------------------
-See
-<<
-<a href="REQUIREMENTS.html"> REQUIREMENTS </a>
->>
-for a list of required software. You don't need everything listed
-there. In particular, mp3, ogg vorbis and aac support are all
-optional. The configure script will detect what is installed on your
-system and will only try to build those executables that can be built
-with your setup.
-
-Note that no mp3 library (not even the mp3 decoding library libmad)
-is needed for para_server if you only want to stream mp3 files. Also,
-it's fine to use para_server on a box without sound card as para_server
-only sends the audio stream to connected clients.
-
--------------------------
-Install server and client
--------------------------
-
-Install the paraslash package on all machines, you'd like this software
-to run on:
-
- (./configure && make) > /dev/null
-
-There should be no errors but probably some warnings about missing
-software packages which usually implies that not all audio formats will
-be supported. If headers or libs are installed at unusual locations
-you 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,
-
- make install
-
------------------------------------
-Setup user list and create RSA keys
------------------------------------
-
-Note that the RSA keys for paraslash 0.3.x will not work for version
-0.4.x as the new version requires stronger (2048 bit) keys. If you
-already have your 2048 bit keys, skip this step. If you are new to
-paraslash, you have to generate a key pair for each user you want to
-allow to connect. You need at least one user.
-
-Let's assume that you'd like to run the server on host server_host
-as user foo, and that you want to connect from client_host as user bar.
-
-As foo@server_host, create ~/.paraslash/server.users by typing the
-following commands:
-
- user=bar
- target=~/.paraslash/server.users
- key=~/.paraslash/key.pub.$user
- perms=AFS_READ,AFS_WRITE,VSS_READ,VSS_WRITE
- mkdir -p ~/.paraslash
- echo "user $user $key $perms" >> $target
-
-This gives "bar" the full privileges.
-
-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)
-
-Next, extract its public part:
-
- pubkey=~/.paraslash/key.pub.$LOGNAME
- openssl rsa -in $key -pubout -out $pubkey
-
-and 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):
-
- scp $pubkey foo@server_host:.paraslash/
-
-Finally, tell para_client to connect to server_host:
-
- conf=~/.paraslash/client.conf
- echo 'hostname server_host' > $conf
-
------------------
-Start para_server
------------------
-
-Before starting the server make sure you have write permissions to
-the directory /var/paraslash.
-
- sudo chown $LOGNAME /var/paraslash
-
-Alternatively, use the --afs_socket Option to specify a different
-location for the afs command socket.
-
-For this first try, we'll use the info loglevel to make the output
-of para_server more verbose.
-
- para_server -l info
-
-Now you can use para_client to connect to the server and issue
-commands. Open a new shell (as "bar" on "client_host" in the above
-example) and try
-
- para_client help
- para_client si