[WBEL-devel] Re: [WBEL-users] Security updates

Fri, 21 May 2004 12:53:57 -0400

This is a multi-part message in MIME format.
--------------070208090907040801090801
Content-Type: multipart/alternative;
 boundary="------------030303030709020407070800"

--------------030303030709020407070800
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

John Morris wrote:

>On Thu, 20 May 2004, Milan [iso-8859-2] Keršláger wrote:
>
>  
>
>>as there are troubles with WBEL mirrors and with release delays, I
>>suggest to update all needed components by hand. This mean download from
>>http://whiteboxlinux.org/pub/3.0/en/updates already released updates:
>>    
>>
>
>The problem was too many people trying to download direct.  Which is why I
>have killed http access to the whole /pub tree as of this afternoon.  And
>why the rsync appears to have finished between here and NCSU.  Really
>didn't want to have to do that, but it was the only way.  After I get the 
>latest batch of errata posted I'll switch it back on.
>
>Longer term I'm really wondering how to get new versions out.  
>

Would some sort of multi-tiered mirroring be appropriate?  Perhaps you 
can provide the official site, with a few high bandwidth primary 
mirrors. From there the secondary mirrors can rsync the updates.  (that 
is what I do now for my own mirror server. It handles updates for about 
40 boxes)

Then setup and distribute the default up2date and yum configuration 
files to point to a round robin DNS entry such as: 
update.us.mirror.whiteboxlinux.org. (replace "us" where appropriate)

I would not mind hosting such a secondary mirror.  I have a total of 3 
Mbits that does not do too much at night, and I can spare 1 Mbit during 
the day.  If we can get several people to host secondary mirrors for 
updates that would remove your overworked T1 from getting pounded from 
default installs updating.

>The only
>idea that seems to have the potential to really solve the problem is DVD's
>via overnight delivery.  
>
The DVD idea may still be a good idea for the primary mirrors.

~Sean

-----
"Don't count your weasels before they pop." -- The Tick

--------------030303030709020407070800
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
John Morris wrote:
<blockquote cite="midPine.LNX.4.44.0405201938490.5219-100000@mjolnir"
 type="cite">
  <pre wrap="">On Thu, 20 May 2004, Milan [iso-8859-2] Ker&sup1;l&aacute;ger wrote:

  </pre>
  <blockquote type="cite">
    <pre wrap="">as there are troubles with WBEL mirrors and with release delays, I
suggest to update all needed components by hand. This mean download from
<a class="moz-txt-link-freetext" href="http://whiteboxlinux.org/pub/3.0/en/updates">http://whiteboxlinux.org/pub/3.0/en/updates</a> already released updates:
    </pre>
  </blockquote>
  <pre wrap=""><!---->
The problem was too many people trying to download direct.  Which is why I
have killed http access to the whole /pub tree as of this afternoon.  And
why the rsync appears to have finished between here and NCSU.  Really
didn't want to have to do that, but it was the only way.  After I get the 
latest batch of errata posted I'll switch it back on.

Longer term I'm really wondering how to get new versions out. </pre>
</blockquote>
 
Would some sort of multi-tiered mirroring be appropriate?&nbsp; Perhaps you
can provide the official site, with a few high bandwidth primary
mirrors. From there the secondary mirrors can rsync the updates.&nbsp; (that
is what I do now for my own mirror server. It handles updates for about
40 boxes) 
 
Then setup and distribute the default up2date and yum configuration
files to point to a round robin DNS entry such as:
update.us.mirror.whiteboxlinux.org. (replace "us" where appropriate) 
 
I would not mind hosting such a secondary mirror.&nbsp; I have a total of 3
Mbits that does not do too much at night, and I can spare 1 Mbit during
the day.&nbsp; If we can get several people to host secondary mirrors for
updates that would remove your overworked T1 from getting pounded from
default installs updating. 
 
<blockquote cite="midPine.LNX.4.44.0405201938490.5219-100000@mjolnir"
 type="cite">
 <pre wrap="">The only
idea that seems to have the potential to really solve the problem is DVD's
via overnight delivery. </pre>
</blockquote>
The DVD idea may still be a good idea for the primary mirrors. 
 
 
~Sean 
<pre class="moz-signature" cols="72">-----
"Don't count your weasels before they pop." -- The Tick

</pre>
</body>
</html>

--------------030303030709020407070800--

--------------070208090907040801090801
Content-Type: text/x-vcard; charset=utf8;
 name="sean.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="sean.vcf"

begin:vcard
fn:Sean McAdam
n:McAdam;Sean
adr:PMB 293;;905 W. 7th St;Frederick;MD;21701;USA
email;internet:sean@fredcom.com
tel;work:301.619.3744
tel;fax:301.898.8452
tel;pager:beepsean@fredcom.com
tel;home:301.898.7130
tel;cell:301.325.4615
x-mozilla-html:FALSE
url:http://www.fredcom.com/
version:2.1
end:vcard

--------------070208090907040801090801--