Salut,
I agree an automatic update would be very dangerous, EXCEPT if it is in a
controlled environment. This would be an option, disabled by default...
Scenario:
I make a mirror(1) of the updates.
I look through it and decide that some rpm are not cool
I copy the cool packages on another place(2), and modify the <xml> file to
reflect the changes
My network machines gets updated from (2), without me moving.
Advantage: I can add non mdk packages in (2) and get the machines updated
Extra TODO: In (2) I place a file somemachine.update.xml. It adds the
selected rpms described in somemachine.update.xml to somemachine only.
Documentation: Important to understand the structure of the <xml> files
TODO: An editor that create <xml> files based on the Packages placed in(2).
Mandrake-update is then coming closer to the MS SMS job packaging that we
all know(??).
Problems: security - security. But we are smart enough to put some
safeguards (Machine signature, Kerebos system...)
RESULT: Mandrake the first Linux to grows alone.... Think about all the TCO
saved by having your support people stay in one place, when there is a
package to update due to a security alert.
Mandrake as to start to THINK BIG. With 1000's of machine to update on a
LAN.
Franck Martin
Database Development Officer
SOPAC South Pacific Applied Geoscience Commission
Fiji
E-mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Web site: http://www.sopac.org/ <http://www.sopac.org/>
-----Original Message-----
From: David Odin [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 04, 2000 12:13 AM
To: [EMAIL PROTECTED]
Subject: Re: [Cooker] Helix Gnome + Mandrake menus (mdk7.1)
On Thu, Aug 03, 2000 at 10:24:57PM +1200, Franck Martin wrote:
> The helix updater is not important as long as the helix updated packages
appear in the Mandrake Updates, and fast...
>
> Mandrake DO really need a good updater, with unattended updates.
>
> This is what I have found:
>
> In Mandrake-update.pm file which is installed with the mandrake-update
executable, you find the line
> mirror=http://www.mandrake-soft.com/mirrors.lst.
>
> If you modify this line and point it to your corporate mirror, you control
what gets updated.
>
> It would be nice to upgrade this line by checking in a
/etc/mandrake-update.conf file where we should look for the list
> of mirror. A Network Administrator will remove the default to put his/her
own list of mirrors...
>
> Now the extra, is to pass a switch to "mandrake-update -a" to
automatically update all the packages listed without user
> intervention (a cron job).
>
> Problem: the kernels do not update automatically, despite beeing provided
in update... So there must be a switch in the
> <xml> to stop the automatic update....
>
And glibc doesn't upgrade either, and, and...
An automated updater would be _very_ dangerous.
The new version of MandrakeUpdate (in Cooker) as some facilities to let
people update their system from a Cooker mirror or from any place on a disk.
Try it and tell me what you think.
> This is my 2 Fijian cents.
>
Is that much? ;-)
DindinX
--
[EMAIL PROTECTED] HF Team
