I 'thought' that was the case, but it seemed in the notes that it would only build the isos, not rsync...

Thanks for the tip. And the clarification.

Now for something slightly more esoteric:

Ok. Server1 mirrors/builds the isos.

Is there a quicky way for Server2 and Server3 to sync with Server1?

Reason I ask, dd or cp chews my lan bandwidth. And I have 2 servers on my lan, (backup, you know?) and a laptop I do nfs installs with.

Thanks. Keep your towel handy.

I updated the script's help text to make that clearer: http://www.slackware.com/~alien/tool...are-current.sh

I'm not sure I understand your question... is an rsync not the right tool for you? Something like
on Server2 and/or Server3 ? Lots of disk space wasted if you ask me, one copy would be enough and you have NFS?

Eric

Not the most reliable of 'servers'...lol. I have had controller failures, and hdd failures. Just my own paranoia.

And that is EXACTLY what I was looking for. Hate wasting bandwidth to the outside world.

A possible improvement:

How easy or difficult would it be to have a progress bar (like in swaret or even, i think wget), so we would know it is actually doing something, or stalled?

Reason why I ask is my internet cut out in a storm and the script was still running on a different terminal. I restored the connection for the os, but the script stayed at the same place for the next two days (My bad. I forgot it was running on a different terminal)

Is it feasible?

Try the latest version of the script at http://www.slackware.com/~alien/tool...are-current.sh

If you use the script parameter '-v' (for 'verbose') you should see progress report on all transfers.

Cheers, Eric

Sorry to make all these revisions...lol

But if it works the way I hope it does...

Actually, I'm not really sorry. I hope my questions have helped 'evolve' this nice piece of code.

Not sure if I agree. I'd like to keep a complete copy of the official mirror's slackware and slackware-current directories on my main server. This to be able to use your script to burn a current-iso at any time, and at the same time have the stable also handy.
Then, for the end-user laptops and desktops, I'd like to have only -current stored locally in the /root directory, so that it's relatively easy to do an upgradepkg whenever something interesting shows up in Pat's -current. One gigabyte give or take means nothing on relatively modern systems, at least not to me.

Thus it'd be great to have a script that on the server syncs _everything_, but on the various PCs skip KDEI, kernels, aaa* and others which I wouldn't want to use with upgradepkg --installnew */*.tgz anyway.

Doable?

-Y1

Alien:

Works like a charm. I'll let you know if I come up with anything else....lol

Keep up the good work.

Just an FYI really here, I'm using the rsync script for slack 10.2 and it's working flawlessly for me and I thank ya Eric.

Yep. It just works. Always had, just minor improvements.

FYI I hacked the script a litle so it now understands the "-r" option. Using that commandline option you are now also able to mirror and create ISOS for another release than just -current:

Try something like to mirror Slackware 10.2 and create a DVD ISO image for it, while getting a lot of verbose output in the process.

Eric

Eric, will this create a 10.2 release DVD ISO or a 10.2 with all of the updates DVD ISO? Just curious.

MagicMan

The DVD ISO you create with the script will contain everything in the slackware-10.2 tree. That includes the /patches directory i.e. all updates to Slackware 10.2 will be available on the DVD for post-installation.

Eric