Re: Comparing update systems
- From: Günther Schwarz <strap@xxxxxx>
- Date: Thu, 03 Jul 2008 21:21:03 +0200
houghi wrote:
Günther Schwarz wrote:
It checks for updates at the repositories, downloads and installs
them. There is no magic involved. It just works nicer than the tools
I have at hand with SuSE.
2) I am completely baffeld with the fact that the two things do the
same in the background and still you [prefere one over the other
I did not write the things in the background. That would be a discussion
about rpm vs. deb package management. I'm fine with both basically.
I looked a bit at the source and it is basicaly just a script that
runs apt-get if I am not mistaken. Just like you can make a script
that does about the same for zypper with very little effort.
Well, the difference is that cron-apt is available in the first
place. So I do not have any work to do myself other than a little
configuration.
From what you seem to want to be doing, configuring the updates via
YaST should be all that you need.
Configuring automatic updates via YAST does nothing but placing
a 'zypper up (-y)' in /etc/cron.d/. I tried to explain that I want to
keep track about updates by collecting reports in an IMAP folder. That
is the method of choice for me as I do not have a more sophisticated
management tools like Zenworks or WSUS at hand. Cron-apt does exactly
that, the SuSE tools do not without additional scripting.
It would be nice this way. But your example is with 11.0 obviously.
The 10.3 systems here won't be retired until 2009, and I have to find
a solution for this. Otherwise they do run nicely, so I have no
intention to go to kernel 2.6.25 anytime soon. It is either parsing
the nasty output to a readable form or switching to smart like I
already did with 10.2 where zypper has proven to be plain horror. I
would like to stay with the default updater, so I'm working now on
the parsing problem.
I agree with you on the output. Perhaps if somebody files a bugreport,
they repair it. It might be worth a try.
I nearly finished now a script that uses the --terse option for zypper.
But I will have to run it for a while in order to see what it does on
different events like the occasional kernel updates.
I am sorry, I fail to see where is does anything that would relate
to a networked enviroment.
Think of a small system with several servers and PCs which share big
parts of their configuration. Maintenance work has to be restricted
to the absolute minimum possible without compromising security and
availability. Automatic updates are vital for such a system as is a
configuration tool like cfengine.
I understand what a network is. I fail to see what extra cron-apt
brings to the table that does things specificaly for a network
enviroment.
See above. It enables me to keep track of things with minimum effort. If
I want to revise the update history of a specific machine I can look it
up quickly in my mail instead of logging in and checking in /var.
How would you do this in a openSUSE network enviroment (non SLE, but
openSUSE)? 1) Have one machine fetch the updates for all the versions
of openSUSE, SUSE and SuSE and even S.u.S.E. you are running. (Might
need to make some updates yourself for certain systems)
That is not needed as I do have a local mirror which is maintained by
the IT staff. I can also configure all systems to get their updates
from download.opensuse.org or wherever as bandwith is not an issue. As
for the enterprise versions: these are bound to one specific update
server anyway due to the license model.
Günther
.
- Follow-Ups:
- Re: Comparing update systems
- From: houghi
- Re: Comparing update systems
- References:
- Re: Comparing update systems
- From: houghi
- Re: Comparing update systems
- From: Günther Schwarz
- Re: Comparing update systems
- From: houghi
- Re: Comparing update systems
- Prev by Date: Re: Problem with replacing system drive in 10.3
- Next by Date: Re: Minimum install - SLES 10
- Previous by thread: Re: Comparing update systems
- Next by thread: Re: Comparing update systems
- Index(es):
Relevant Pages
|
