On 16 Mar 2005 at 12:23, Thomas Adam wrote:
--- Paul Graydon
wrote: Hmm.. I've got a slackware based test box at home, wonder how it'll take to it :-)
Well, I tried to run it on my Debian box, but I had to spend a considerable amount of time hacking it to death -- it's too dependant on one distro to ever be portable. This may not be a bad thing, if it is designed only for one specific distro -- the only problem with that is I personally wouldn't go near Mandrake...
Been there, done that, got the T-shirt?
Something like that, yes.
we could lock our system down even further, like specifying the workstations can only run x, y & z, program files etc, but that's just too much hassle to implement and maintain!
I wouldn't have said so -- in fact, it would be quite easy to do.
Its easy to add the programs into the client management software. The hardest part I've found is trying to ensure you've got every program that gets used by the programs themselves. I tried to lock down a library machine last week, all I wanted it to run was the library catalogue software, so users could search from it. Some bizarre mapping issues meant we couldn't set the program (which runs from a network drive) as shell, it could see the program but wouldn't see the contents of the catalogue, which is in the same place as the program. Alternative approach was to tell it it could only run that one application, but that didn't work either, as it called on various windows programs and the like, but it was impossible to track the calls. In the end we gave up and just locked out the start menu, run, ctrl+alt+delete, and so on for the unique user account we created, and then set the box up to autologon.----- Paul Graydon Network Technician Haywards Heath College http://www.hhc.ac.uk (01444) 456281 "Joy is not in things; it is in us." Richard Wagner