summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-sysadm/2011-June/003560.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-sysadm/2011-June/003560.html')
-rw-r--r--zarb-ml/mageia-sysadm/2011-June/003560.html104
1 files changed, 104 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2011-June/003560.html b/zarb-ml/mageia-sysadm/2011-June/003560.html
new file mode 100644
index 000000000..2d963e40b
--- /dev/null
+++ b/zarb-ml/mageia-sysadm/2011-June/003560.html
@@ -0,0 +1,104 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-sysadm] Mageia 1 release coming to mirrors
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Mageia%201%20release%20coming%20to%20mirrors&In-Reply-To=%3C1306937536.11044.48.camel%40akroma.ephaone.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="003544.html">
+ <LINK REL="Next" HREF="003545.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-sysadm] Mageia 1 release coming to mirrors</H1>
+ <B>Michael Scherer</B>
+ <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Mageia%201%20release%20coming%20to%20mirrors&In-Reply-To=%3C1306937536.11044.48.camel%40akroma.ephaone.org%3E"
+ TITLE="[Mageia-sysadm] Mageia 1 release coming to mirrors">misc at zarb.org
+ </A><BR>
+ <I>Wed Jun 1 16:12:14 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="003544.html">[Mageia-sysadm] Mageia 1 release coming to mirrors
+</A></li>
+ <LI>Next message: <A HREF="003545.html">[Mageia-sysadm] Where can I get the sha1/md5 signing key 0xDA10B483, since it isn't on the gpg key servers?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#3560">[ date ]</a>
+ <a href="thread.html#3560">[ thread ]</a>
+ <a href="subject.html#3560">[ subject ]</a>
+ <a href="author.html#3560">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le mardi 31 mai 2011 &#224; 22:42 -0300, Carlos Carvalho a &#233;crit :
+&gt;<i> Michael Scherer (<A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">misc at zarb.org</A>) wrote on 1 June 2011 03:07:
+</I>&gt;<i> &gt;Le mardi 31 mai 2011 &#224; 18:06 -0300, Carlos Carvalho a &#233;crit :
+</I>&gt;<i> &gt;&gt; Mageia Sysadmin Team (<A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">root at mageia.org</A>) wrote on 31 May 2011 21:59:
+</I>&gt;<i> &gt;&gt; &gt;The expected size of the new ISOs is 14G.
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt; Ugh... How about using jigdo? If you create the jigdo/templates we can
+</I>&gt;<i> &gt;&gt; build the isos ourselves (at the least the full/tier1 mirrors).
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt;Wouldn't it be a tradeoff of using less bandwidth by asking more work to
+</I>&gt;<i> &gt;mirror admins ? ( ie, setting up jigdo, a script to rebuild, or a manual
+</I>&gt;<i> &gt;run , which mean more coordination ) ?
+</I>&gt;<i>
+</I>&gt;<i> Big mirrors already have it for other distros, so it won't be a pain.
+</I>
+For d-c, the sysadmins ( me and olivier ) prefer to have everything goes
+in the background ( ie sync when it need to be synced ). Now, given
+various peering and traffic arrangement, it may be helpful to optimize
+things by hand, but I do not think we should have a manual procedure as
+the default.
+
+&gt;<i> What I do is exclude the isos, build them here (the jigdo script
+</I>&gt;<i> automatically calls rsync to adjust times/perms/etc.) then remove the
+</I>&gt;<i> exclusion. At the next run the isos will be new files but when rsync
+</I>&gt;<i> looks it finds them already so they're just skiped.
+</I>&gt;<i>
+</I>&gt;<i> &gt;How does the update feature work with package indexes ?
+</I>&gt;<i>
+</I>&gt;<i> I didn't understand.
+</I>
+If I want to update the iso ( one of the selling point of jigdo ), I
+need to recreate the package index on the cd ( or installer would not
+work ). This either mean the package index is a treated like all others
+files ( and then, that mean we will have to update the jigdo file each
+time we create a update ), or to create the index on the fly.
+
+
+&gt;<i> &gt;( and how does it work with hybrid iso, as debian seems to see this as
+</I>&gt;<i> &gt;problematic, even if I think they may have solved it, I didn't read the
+</I>&gt;<i> &gt;whole thread :
+</I>&gt;<i> &gt;<A HREF="http://www.mail-archive.com/debian-cd@lists.debian.org/msg19292.html">http://www.mail-archive.com/debian-cd@lists.debian.org/msg19292.html</A> )
+</I>&gt;<i>
+</I>&gt;<i> I didn't follow it because it's a repository issue, not a mirror one.
+</I>
+Well, if we want to avoid regressions, we need to check that before
+deploying jigdo.
+--
+Michael Scherer
+
+</PRE>
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="003544.html">[Mageia-sysadm] Mageia 1 release coming to mirrors
+</A></li>
+ <LI>Next message: <A HREF="003545.html">[Mageia-sysadm] Where can I get the sha1/md5 signing key 0xDA10B483, since it isn't on the gpg key servers?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#3560">[ date ]</a>
+ <a href="thread.html#3560">[ thread ]</a>
+ <a href="subject.html#3560">[ subject ]</a>
+ <a href="author.html#3560">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm
+mailing list</a><br>
+</body></html>