[WBEL-users] Security updates

Tom Cooper tcooper@starpower.net
Fri, 21 May 2004 07:20:32 -0400


This is a multi-part message in MIME format.
--------------010601080900010609040904
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

I can appreciate the challenges with bandwidth.  As I've installed 
several WBL boxes, I've accidentally downloaded patches from your site.  
Might it be a good idea to have the default downloald location be a mirror?

Also, I was noticing that the .RPMs are not avaiable on rpmfind.net.  
Have you looked into what it would take to get them there?  That could 
save huge bandwidth, particularly when someone wants a specific package.

Is there any chance that yum can handle http redirection?  If so, I 
wonder if you could redirect to a mirror from whitebox.org?  It's a long 
shot, but I thought I'd mention it.

WRT security updates in particular, what should I expect?  I have had 
good experience at work applying RedHat ES 3 rpm's to some test boxes, 
but I'm not licensed to do that, so doing it on my home system or 
outside a lab is not acceptable.  I think that means that I need to rely 
on whitebox linux security updates.  Are you building those as they are 
released by RedHat? 

Thanks for your hard work.  As I posted on slashdot, I really appreciate 
your labors.

Regards,
Tom Cooper


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.  The only
>idea that seems to have the potential to really solve the problem is DVD's
>via overnight delivery.  Looking at this upcoming respin, assuming one set
>of SRPM images for both arches, it will have nine .iso files without
>considering the possibility of DVD images plus all of the x86_64 files
>also appearing down /pub/3.0/en/os/x86_64.
>
>The bandwidth of the postal service is potentially huge... but the latency 
>isn't all that good.  :)
>
>  
>


--------------010601080900010609040904
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">
I can appreciate the challenges with bandwidth.&nbsp; As I've installed
several WBL boxes, I've accidentally downloaded patches from your
site.&nbsp; Might it be a good idea to have the default downloald location
be a mirror?<br>
<br>
Also, I was noticing that the .RPMs are not avaiable on rpmfind.net.&nbsp;
Have you looked into what it would take to get them there?&nbsp; That could
save huge bandwidth, particularly when someone wants a specific package.<br>
<br>
Is there any chance that yum can handle http redirection?&nbsp; If so, I
wonder if you could redirect to a mirror from whitebox.org?&nbsp; It's a
long shot, but I thought I'd mention it.<br>
<br>
WRT security updates in particular, what should I expect?&nbsp; I have had
good experience at work applying RedHat ES 3 rpm's to some test boxes,
but I'm not licensed to do that, so doing it on my home system or
outside a lab is not acceptable.&nbsp; I think that means that I need to
rely on whitebox linux security updates.&nbsp; Are you building those as
they are released by RedHat?&nbsp; <br>
<br>
Thanks for your hard work.&nbsp; As I posted on slashdot, I really
appreciate your labors.<br>
<br>
Regards,<br>
Tom Cooper<br>
<br>
<br>
John Morris wrote:<br>
<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.  The only
idea that seems to have the potential to really solve the problem is DVD's
via overnight delivery.  Looking at this upcoming respin, assuming one set
of SRPM images for both arches, it will have nine .iso files without
considering the possibility of DVD images plus all of the x86_64 files
also appearing down /pub/3.0/en/os/x86_64.

The bandwidth of the postal service is potentially huge... but the latency 
isn't all that good.  :)

  </pre>
</blockquote>
<br>
</body>
</html>

--------------010601080900010609040904--