| PLEX86 | ||
Updating Linux in a BusinessNot familiar with this specific distribution. Normally, when more than 2-3 users are being updated, the best approach is to implement the upgrade on one "control machine" which has been backed up prior to the update, and can be restored if the update fails. You install the upgrade, confirm that everything works, and resolve any issues necessary on that machine. When you are done, you provide a shell script which can be executed by each member of the team. This will access the hard coded IP address and hard-coded path, and should be done using ssh (OpenSSH actually). Often for larger groups you will have an administrative account for which certificates have already been installed and validated. This allows you to run scripts - including configuration scripts, from a specific "master" machine using the master ID. The access is logged, as is the su, which means that you can now audit and capture any attempt to update the system without authorization - and prosecute the perpetrators. ActiveX in Linux browsers This is probably a *very* dumb question, but I'm curious as to what technical obstacles exist in order to implement... For larger groups, the scripting pays off even bigger dividends, and there are ways to use cron jobs to "pull" the updates - again from a secured locaton inside the corporate firewall. ActiveX in Linux browsers 6620 BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 3 Dec 2005 14:41:41 -0600, Neither is the canvas tag... This is where scripting provides advantage over a GUI based interface. You have to get it right once, but after that you clan clone it to thousands.
|
||||
Linux Advocacy from Newsgroups The #1 Usenet Provider on the Internet
|
||||