1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
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 à 22:42 -0300, Carlos Carvalho a écrit :
><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>><i> >Le mardi 31 mai 2011 à 18:06 -0300, Carlos Carvalho a écrit :
</I>><i> >> 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>><i> >> >The expected size of the new ISOs is 14G.
</I>><i> >>
</I>><i> >> Ugh... How about using jigdo? If you create the jigdo/templates we can
</I>><i> >> build the isos ourselves (at the least the full/tier1 mirrors).
</I>><i> >
</I>><i> >Wouldn't it be a tradeoff of using less bandwidth by asking more work to
</I>><i> >mirror admins ? ( ie, setting up jigdo, a script to rebuild, or a manual
</I>><i> >run , which mean more coordination ) ?
</I>><i>
</I>><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.
><i> What I do is exclude the isos, build them here (the jigdo script
</I>><i> automatically calls rsync to adjust times/perms/etc.) then remove the
</I>><i> exclusion. At the next run the isos will be new files but when rsync
</I>><i> looks it finds them already so they're just skiped.
</I>><i>
</I>><i> >How does the update feature work with package indexes ?
</I>><i>
</I>><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.
><i> >( and how does it work with hybrid iso, as debian seems to see this as
</I>><i> >problematic, even if I think they may have solved it, I didn't read the
</I>><i> >whole thread :
</I>><i> ><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>><i>
</I>><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>
|
