[SOLVED] Requirements for ISO images for mirrors

average_user · 07-28-2015, 06:35 AM

Some of mirrors listed at http://mirrors.slackware.com/mirrorlist/ do not provide ISO images but some do. According to http://mirrors.slackware.com/ it's not actually definitely clear to me whether it's a requirement to provide ISO; on the bottom of this page it says:

Quote:

Mirror admins: if you want to have the ISO images but you are unable to find a reliable source to get them, contact me.

However, above that it's described how to get and provide ISO images and it's not mentioned whether it's optional or not. So it a requirement to provide ISO that some mirror admins do not conform to as it's easy to create ISO image locally or it isn't a requirement?

Didier Spaier · 07-28-2015, 07:50 AM

I think that having want in bold in the original text you quoted makes clear enough that it's not required form mirror admins to host ISO images.

I see this example of command (quoted from http://mirrors.slackware.com/guidelines/) as a confirmation as it obviously excludes the iso files:

Code:

  rsync -aPSH --delete \
     --exclude "*-iso/" \
     rsync://your-upstream-mirror/slackware/ \
     /your-toplevel-pub/slackware/

I am jut a Slackware user but if you need an official source of information I see on the bottom of the same page:

Quote:

Responses, feedback, and questions go to mirrors@slackware.com - thanks!

average_user · 07-28-2015, 08:02 AM

But in both 1) and 2) it says (bolding mine):

Quote:

This approach will work fine; you can add an
--exclude "*-iso/" line to your mirroring scripts, so long as you
are okay with manually grabbing ISOs after every release.

Quote:

This will require you to exclude "slackware-iso/" in your rsync script,
and it would still require manually grabbing ISOs after every release.

For me it's contradictory to what it say at the bottom. Doesn't it mean that if someone excludes ISO in his rsync script he must download it manually and put on the server after every release?

Didier Spaier · 07-28-2015, 10:27 AM

The only way to be sure is to ask the admins @ the aforementioned email address, as already stated.

average_user · 07-29-2015, 03:32 PM

I am not going to set up a new mirror. The problem is that I have my favorite mirror added as a bookmark to lftp but it does not provide ISOs. Just of curiosity, I thought that someone here might know the story.

Didier Spaier · 07-29-2015, 03:39 PM

I will refrain to answer what came to my mind, as that wouldn't have been enough polite. Have a good night.

StreamThreader · 07-29-2015, 03:56 PM

Quote:

Originally Posted by average_user

Some of mirrors listed at http://mirrors.slackware.com/mirrorlist/ do not provide ISO images but some do. According to http://mirrors.slackware.com/ it's not actually definitely clear to me whether it's a requirement to provide ISO; on the bottom of this page it says:

However, above that it's described how to get and provide ISO images and it's not mentioned whether it's optional or not. So it a requirement to provide ISO that some mirror admins do not conform to as it's easy to create ISO image locally or it isn't a requirement?

I think primary target for mirroring is a source code, slackbuilds and packages. This components enough for network installation and for create ISO's itself.
Secondary target (if on your mirror server have enough free space) mirroring ISO.

mralk3 · 07-29-2015, 06:12 PM

You can always switch mirrors to one that does provide ISO images. Though the download speeds will probably be slower.

Alternatively, you could mirror your favorite remote repository to your hard drive and build your own ISO images using the following script:

http://www.slackware.com/~alien/tool...are-current.sh

Here is Alien's tutorial for this script:

http://alien.slackbook.org/blog/local-slackware-mirror/

As an added bonus to using this option, you can exclude what you want from the mirror and ISO image. You can also specify architecture and Slackware release.

average_user · 07-30-2015, 03:59 AM

Quote:

Originally Posted by Didier Spaier

I will refrain to answer what came to my mind, as that wouldn't have been enough polite. Have a good night.

What made you so angry?

Quote:

Originally Posted by StreamThreader

I think primary target for mirroring is a source code, slackbuilds and packages. This components enough for network installation and for create ISO's itself.
Secondary target (if on your mirror server have enough free space) mirroring ISO.

It's a correct explanation, I think.

Didier Spaier · 07-30-2015, 04:09 AM

Quote:

Originally Posted by average_user

What made you so angry?

That you did continue asking in the wrong place even knowing the good one.

wildwizard · 07-30-2015, 04:10 AM

The primary mirror does not have the iso's on it.

If you run rsync without the exclude setting it will delete iso images on the receiving mirror that have been acquired via other means.

The primary source for the iso's is via BT as it spreads the sudden load (at release time) better than a single ftp site can handle to get them out there.