Trying to download the 3.1 iso's of CentOS and no matter which mirror I go to, or release 3 version, I always see the 3.6 iso's. URL: http://wuarchive.wustl.edu/pub/linux/distributions/centos/3.1/isos/i386/ Shows all of the 3.6 iso files. Some reason why I can't find the older release files? Thanks, Darren Young Senior UNIX Administrator University of Chicago Graduate School of Business -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20051229/f17a23a5/attachment-0001.html>
On 12/29/05, Young, Darren <Darren.Young at chicagogsb.edu> wrote:> Some reason why I can't find the older release files?Yep. They're obsolete, and we're trying to save space/bandwidth on the mirrors, since the space is donated. 3.6 is 3.1 with all the updates+errata. If you REALLY need 3.1 for some hellish reason, you'll need to get it from the vault. ( vault.centos.org ) -- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
On Thu, 2005-12-29 at 21:07 -0600, Young, Darren wrote:> Trying to download the 3.1 iso's of CentOS and no matter which mirror > I go to, or release 3 version, I always see the 3.6 iso's. > > URL: > http://wuarchive.wustl.edu/pub/linux/distributions/centos/3.1/isos/i386/ > > Shows all of the 3.6 iso files. > > Some reason why I can't find the older release files?yes ... we only mirror the current tree on the main mirrors (and that is more than 100GB at peak times). If you want other items, you can find them at http://vault.centos.org> > Thanks, > > Darren Young-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.centos.org/pipermail/centos/attachments/20051229/14f79d45/attachment-0001.sig>
> Yep. They're obsolete, and we're trying to save > space/bandwidth on the mirrors, since the space is donated. > 3.6 is 3.1 with all the > updates+errata. If you REALLY need 3.1 for some hellish reason, you'll > need to get it from the vault. ( vault.centos.org )Hellish, maybe -> Tivoli Storage Manager. Actually, what I need is kernel 2.4.21-4.0.1 according to IBM. I thought that since that version was in an older version of the "other enterprise linux" it would be in an older CentOS as well. Am I correct in this assumption or fighting a losing battle? Not sure how *hard* that requirement is, might just be kernel 2.4.whatever, but I have to find out. Was that version in 3.0 or 3.1 of CentOS? Also have a requirement for kernel 2.4 from the Tivoli Integrated Solution Console as well. Not sure on this requirement as well, I do know that with CentOS 4 the installer blew up with "unsupported kernel version xxx". Tried tricking the installer by replacing the uname binary with a script that returned what the other linux gives from `uname -a` but it didn't work.
> The oldest kernel that we released with CentOS-3 was 2.4.21-9.0.1. That > was at 3.1 which was the oldest official release.I found an EL rpm for 2.4.21-4.0.1 on RHN, seems to be one of the first 3.x kernels, maybe even *the* first.> I can build you a 2.4.21-4.0.1 kernel ... and maybe even a 2.4.21-4.0.1 > install CD if you absolutely need that (I don't have a CentOS-3 build > environment for spinning CD though, I do CentOS-4) ... IF all (or most) > of the rest of the 3.1 level stuff would work.Many thanks for the offer, I can build a new one if necessary but I'm really trying to avoid it. I'm installing 3.6 into VMware right now to find out how picky the various IBM installers truly are. I do know some of them are 'pickier' than others.> BUT ... if you need all stuff before EL3 update 1, that would be fairly > hard. (In fact it would be building a whole new point release :)Yea, I'll just use "the other" EL if it comes down to that. I think WS will work for what I'm doing, it's just a reference build/environment and not production. It will be interesting to see if CentOS can in fact be used for Tivoli Storage Manager, not so much on the OS side, but if IBM's products actually detect the fact that it's not the "real thing". One thing I did find with their Integrated Solutions Console (ISC) was that it seems to read /etc/redhat-release to determine something... Wasn't paying attention to the system calls all that closely, but I did see open(), fseek() and close() on it. -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 4251 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20051230/1ab049ac/attachment-0001.bin>
> One thing I did find with their Integrated Solutions Console (ISC) was > that it seems to read /etc/redhat-release to determine something... > Wasn't paying attention to the system calls all that closely, but I did > see open(), fseek() and close() on it.You almost always want to replace the contents of /etc/redhat-release with the same contents of that file from the 'other EL'... I'm not sure what the proper contents are on EL3, but on my Centos 4: # cat /etc/redhat-release Red Hat Enterprise Linux AS release 4 (Nahant Update 2) # cat /etc/centos-release CentOS release 4.2 (Final) Makes the HP installers much, much happier. Cheers, MaZe.