SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'd like to make an ISO from slackware-current on a fairly regular basis. I don't have access to rsync, so need to use HTTP/FTP. I am looking for the script that tells me I have a good, consistent set of files, e.g. scanning PACKAGES.TXT, MANIFEST.bz2, CHECKSUMS.md5 and checking that everything matches, in case I happen to be downloading when someone is updating the source, and to verify the downloads.
to sync and create my isos I personally use mirror-slackware-current.sh from Alien Bob but by default it uses rsync.
you can also use it with the -i option (that creates the iso without downloading anything) if you have an up-to-date local mirror.
read it to see configurable variables and switches.
to check the hashes maybe the best option for you is to use directly the file CHECKSUMS.md5 in the root directory of your mirror: read that too for instructions.
OK, so let me get this right - I still run the risk that CHECKSUMS.md5 is still being updating when I read it, and/or it doesn't include files that have been referenced in PACKAGES.TXT, which I presume drives the install, and is the important one. Is that right?
I guess most people just assume the updates don't occur very often and that they won't hit one and hope for the best!
OK, so let me get this right - I still run the risk that CHECKSUMS.md5 is still being updating when I read it, and/or it doesn't include files that have been referenced in PACKAGES.TXT, which I presume drives the install, and is the important one. Is that right?
I guess most people just assume the updates don't occur very often and that they won't hit one and hope for the best!
regards,
Biff.
You could check the timestamp of the most recent entry in ChangeLog.txt? Usually the mirrors synchronize within a day of an update on the master server.
Also, the mirror-slackware-current script does two rsync-s in a row, if the first rsync runs while the remote server is still being updated, the second rsync should show activity (it will sync the files that got added or changed after the first rsync started).
If you really want to know what happens you add a "-v" parameter and watch what the script does.
Lastly, you can check if you have mirrored everything correctly by following the instructions from the header of the CHECKSUMS.md5 file:
Code:
These are the MD5 message digests for the files in this directory.
If you want to test your files, use 'md5sum' and compare the values to
the ones listed here.
To test all these files, use this command:
tail +13 CHECKSUMS.md5 | md5sum -c --quiet - | less
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.