diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/20120209/006461.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/20120209/006461.html | 82 |
1 files changed, 82 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20120209/006461.html b/zarb-ml/mageia-discuss/20120209/006461.html new file mode 100644 index 000000000..e785c9ba9 --- /dev/null +++ b/zarb-ml/mageia-discuss/20120209/006461.html @@ -0,0 +1,82 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-discuss] A possible risk ? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20A%20possible%20risk%20%3F&In-Reply-To=%3C4F330E82.6080607%40Rock3d.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="006459.html"> + <LINK REL="Next" HREF="006458.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-discuss] A possible risk ?</H1> + <B>imnotpc</B> + <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20A%20possible%20risk%20%3F&In-Reply-To=%3C4F330E82.6080607%40Rock3d.net%3E" + TITLE="[Mageia-discuss] A possible risk ?">imnotpc at Rock3d.net + </A><BR> + <I>Thu Feb 9 01:08:34 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="006459.html">[Mageia-discuss] A possible risk ? +</A></li> + <LI>Next message: <A HREF="006458.html">[Mageia-discuss] A possible risk ? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6461">[ date ]</a> + <a href="thread.html#6461">[ thread ]</a> + <a href="subject.html#6461">[ subject ]</a> + <a href="author.html#6461">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 02/08/2012 06:36 PM, David W. Hodgins wrote: +><i> On Wed, 08 Feb 2012 13:23:58 -0500, nicolas vigier +</I>><i> <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">boklm at mars-attacks.org</A>> wrote: +</I>><i> +</I>>><i> The problem is the bad update, not that it was allowed without root +</I>>><i> password. Updates should not hose the system, and that's why there is a +</I>>><i> policy on no new versions in update when possible, and qa tests. +</I>><i> +</I>><i> The main problem I've seen with updates breaking a system happens when +</I>><i> there is a large number of updates (such as kde), and the mirror you're +</I>><i> updating from synced in the middle of the main repositories being +</I>><i> updated. +</I>><i> +</I>><i> I think the best solution would require the primary repositories to have +</I>><i> some sort of a lock, so that they cannot be synced from in the middle of +</I>><i> an update, or better yet, some way to have all updates put into a hidden +</I>><i> directory, until they have all been loaded, and then have a single +</I>><i> operation +</I>><i> that puts all of the updates into the active directories without allowing +</I>><i> any downstream mirror to sync while that's happening. +</I>><i> +</I>><i> Regards, Dave Hodgins +</I>I believe if you request/require mirrors to use rsync --delete-after +--delay-updates when they sync it will eliminate this issue since +changes shouldn't become visible until the sync in complete. + +Jeff +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006459.html">[Mageia-discuss] A possible risk ? +</A></li> + <LI>Next message: <A HREF="006458.html">[Mageia-discuss] A possible risk ? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6461">[ date ]</a> + <a href="thread.html#6461">[ thread ]</a> + <a href="subject.html#6461">[ subject ]</a> + <a href="author.html#6461">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss +mailing list</a><br> +</body></html> |