diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/20110217/003624.html')
-rw-r--r-- | zarb-ml/mageia-discuss/20110217/003624.html | 86 |
1 files changed, 86 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20110217/003624.html b/zarb-ml/mageia-discuss/20110217/003624.html new file mode 100644 index 000000000..1c5438645 --- /dev/null +++ b/zarb-ml/mageia-discuss/20110217/003624.html @@ -0,0 +1,86 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-discuss] Switzerland Mirror Switch.ch + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Switzerland%20Mirror%20Switch.ch&In-Reply-To=%3C4D5D6D79.30901%40unige.ch%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="003620.html"> + <LINK REL="Next" HREF="003626.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-discuss] Switzerland Mirror Switch.ch</H1> + <B>Juergen Harms</B> + <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Switzerland%20Mirror%20Switch.ch&In-Reply-To=%3C4D5D6D79.30901%40unige.ch%3E" + TITLE="[Mageia-discuss] Switzerland Mirror Switch.ch">Juergen.Harms at unige.ch + </A><BR> + <I>Thu Feb 17 19:48:25 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="003620.html">[Mageia-discuss] Switzerland Mirror Switch.ch +</A></li> + <LI>Next message: <A HREF="003626.html">[Mageia-discuss] Switzerland Mirror Switch.ch +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3624">[ date ]</a> + <a href="thread.html#3624">[ thread ]</a> + <a href="subject.html#3624">[ subject ]</a> + <a href="author.html#3624">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE> >> Well, in fact, given the way tcp work, I do not see how it could + >> suffer from a transmission problem. + +Tcp corrects errors with a certain likelyhood. I do not know what +CRC-something is used by ftp - for CRC-16, depending on the type of +error and the package length, probablilities are smaller than 10 power +-6 (I did these figures many years back, rapid googling does not provide +any evident figures). Anyhow, with this order of magnitude, and with the +100 M bytes(!) of a typical largish package, the probability of +receiving an apparently good package which after all is not so good is +non-negligeable. Doing another check at the application level therefore +may be of substantial merit. Would be good to get input from somebody +who is more competent. + + >>I think the instruction for now are only for cauldron + +That is what I thought. "Production mirrors" like Switch may be +reluctant to deviate from their ordinary schedule of 24 hours. + +I think that the request should be formulated in a subtle way: avoid +that a reject on cauldron terms implies a reject for production mirror +requirements - and a mirror for the stable release is the essential +issue, the stable release Mageia should be present at all major mirror, +that is the priority (cauldron could probably live with a reduced number +of mirrors). But the present pre-release of Mageia is a special case: +there exists no stable alternative, and the initial pre-releases have a +vital interest of being easily accessible. But I am doing what should +not be done: risk to create a problem by talking about it (- + +Juergen +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="003620.html">[Mageia-discuss] Switzerland Mirror Switch.ch +</A></li> + <LI>Next message: <A HREF="003626.html">[Mageia-discuss] Switzerland Mirror Switch.ch +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3624">[ date ]</a> + <a href="thread.html#3624">[ thread ]</a> + <a href="subject.html#3624">[ subject ]</a> + <a href="author.html#3624">[ 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> |