[Wolves] Software management on networks

[SimonB]

> -----Original Message-----
> From: wolves-bounces at mailman.lug.org.uk 
> [mailto:wolves-bounces at mailman.lug.org.uk] On Behalf Of 
> Stuart Langridge
> Sent: 16 November 2005 10:55
> To: Wolverhampton Linux User Group
> Subject: Re: [Wolves] Software management on networks
> 
> > I'm not claiming to know all issues that ZENworks addresses, however
> > from a software distribution aspect, you just need a number 
> of Debian
> > repositories; customised /etc/apt/sources.list on 
> individual PCs (this
> > assumes PCs can be grouped together in classes) and the 
> ability to login
> > remotely via ssh in an automated manner.
> 
> Point 3 is the hard one there. That's like saying, here is my
> foolproof plan to win the 100m at the Olympics.
> 
> 1. Do a bit of training, lift some weights, go jogging.
> 2. Take a few steroids
> 3. Run the 100m faster than anyone else in the world.
> 4. Collect your gold medal.
> 
> Step 3 is clearly the hard one. How do you allow "the ability to login
> remotely via ssh in an automated manner" without giving all the
> machines the same root password or recording all the root passwords in
> the Master Machine r00table List? Moreover, how do you know a machine
> is turned on? Or do you just ping-flood every IP on the network every
> five minutes?
> 
Ok I admit that the script that I use it a little botched but it works
for what I want it to do. Also we do have the same root password for all
desktops, not that I sue it anyway, Right considering that this is a
small network, around 10pc's its quite easy in that scenario, just not
in the hundred or thousands.

Essentailly what my script does is that uses rlogin and the server is
setup as a repositry surprisingly enougth. Im currentlky trying to get
it to use SSH now and do some more advanced things with it. Also having
to change the script everytime I do it is a pain and doesn’t save much
time, but meh, it'll get there.

Cheers,

SimonB