sorry no philosophy here... here's what I'd do. On Thu, Oct 19, 2006 at 04:09:02PM -0700, Andrew Lentvorski wrote: > >If I can get this working, there will be at least 2 instructors at SDSU >using it.
create a group for each set of instructors with write access to n student repositories. >1) Individual authenticated access (per student) create a user for each student, no passwd access. configure sshd to use $PREFIX/sshd/keys/$USER for rsa auth make instructions for users to install the putty suite generate rsa-keys use pagent mail rsa keys to admin generate instructor accounts to and have them submit keys too authenticate the keys ;) and apply to sshd auth keys directory add instructors to their respective group(s) >2) The instructor needs to be able to check out and modify the files of >any student N=/repo/student-n svnadmin create $N chown -R student-n:instructors $N chmod -R ug+rwX,o-rwx $N >3) Must run on Solaris should. >4) Should use the FS repository svnadmin create, just do it. >5) Low maintenance to manage there is a hot backup python script distributed with svn make a checkout, update, commit, stat, diff, add, remove and revert howto. instruct users to start pagent and configure/install TortoiseSVN, Subclipse to use svn+ssh://hostname/repo/$N then right click. done. >Pointers and advice are welcome. However, if you give me a full-blown >solution, I'll take you to Lefty's for pizza and beer. mmm, pizza and beer. ;) // George -- George Georgalis, systems architect, administrator <IXOYE>< -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
