Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
installer_v0.9.tar.gz | 2013-07-19 | 107.4 MB | |
readme.txt | 2013-07-19 | 3.8 kB | |
installer_v0.8.tar.gz | 2012-09-07 | 107.1 MB | |
installer_v0.7.tar.gz | 2012-05-02 | 107.1 MB | |
installer_v0.7a.tar.gz | 2012-05-02 | 30.3 MB | |
installer_v0.6.tar.gz | 2011-09-07 | 105.9 MB | |
Totals: 6 Items | 457.9 MB | 1 |
Prerequisites ------------- DRBL - https://sourceforge.net/projects/drbl/ Rosie comes with Tomcat so you need a Java JDK (Oracle or OpenJDK) MySQL 5.0 or greater To manage the MySQL database we use phpmyadmin which will also require: Apache2 PHP5 ROSIE v0.1 - v0.4: Zenity - used to display messages on the clients ROSIE v0.5 & upwards: Yad - used to display messages on clients on top of all other dialogs and windows. Yad belongs to the PPA: GetDeb Apps which you will need to add before being able to install it: http://www.ubuntuupdates.org/ppa/getdeb_apps?dist=lucid. Then you should be able to just run sudo apt-get install yad Please note that we have test Rosie on Ubuntu 10.04 and Xubuntu 12.04. We have not had the opportunity to fully test under other operating system that DRBL supports - see Other Flavours Installers ---------- installer_v0.9.tar.gz contains the ROSIE server and client. The server will be installed here: /opt/drbl/is/server The client will be installed here: /opt/drbl/is/client Read the ROSIE Installation Guide (in docs) for more detailed information To install extract the installer. Then in the terminal go into the extract installed directory and run: sudo ./install.sh Security -------- Currently this early version of ROSIE requires running Tomcat as sudo to interact with the various scripts for creating users etc.. If anyone has any reasonable suggestions to avoid this then please let us know. Documentation ------------- A number of PDF guides can be found at: https://sourceforge.net/projects/rosie/files/Docs/ Other Flavours -------------- Some notes about the other systems that DRBL supports and includes comments about the various issues. Debian 6 - seems to work in general except for displaying messages on the client machine. Under Ubuntu when you run the command xhost you will see that the local user is list: SI:localuser:<username>. On Debian this is not the case and means that the remote tty display cannot be exported and used to display the message via ssh. One fix is the following: * in /tftpboot create a file called 60x11-common_localhost * edit this file and in it place: # This file is sourced by Xsession(5), not executed. [ -x /usr/bin/xhost ] && [ -x /usr/bin/id ] && xhost +si:localuser:`id -un` > /dev/null * save the file * create another file in /tftpboot called xhostfix.sh, in this file place: /opt/drbl/sbin/drbl-cp-host /tftpboot/60x11-common_localhost /etc/X11/Xsession.d/60x11-common_localhost * chmod 700 xhostfix.sh * run the file script and it will place the 60x11-common_localhost file win each client NB: you will need to repeat the last step each time you run drblpush. Fedora 14 - seems to work in general, but has not been tested fully OpenSUSE 11.3 - * in order for interaction with the clients via SSH the PermitRootLogin must be set to yes in the /etc/ssh/sshd_config. The easiest way to do this is create a copy on the ssh config file on the server, make the changes and then use drbl-cp-host to copy to all the clients. * due to the way in which users are create under OpenSUSE the client-lockdown script needs to be altered to change the group of the users home directory to 'users' * removal of user account, the home directory is deleted but the user account is never remove, causing problems when creating a new session with the same username * SSH - requires: * the msg.sh shell script to be run as sudo * modified msg.sh that needs to find the xauthority file and export it so that it can find the correct display of the user that is logged in CentOS 5.7 - it seems that yad has to be installed by hand, but fails because 5.7 does not come with gtk+-2.0. The SSH interaction with clients fails, shutdown, messages (using zenity) because SSH wants a password