LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 08-26-2006, 12:58 PM   #1
KaYoS
Member
 
Registered: May 2006
Posts: 32

Rep: Reputation: 15
Keeping a local mirror of packages current


Hi there

I would like to keep a local copy of the slackware current folder on my server.
The reason for this is i have quite a few machines to keep updated (15) and would also like to have my own mirror for some friends to use.

I am just not sure the best way to do it.

My theory goes like this:

1. Copy all the packages from my Slackware 11 cd (when it arrives) to /mnt/server
2. then use rsync to compare it to a mirror local to me, and update as required

The problem is im unsure of how to do the rsync bit, and after reading the man page im still non the wiser!

I am just doing a test run at the mo, so i have copied the files from my 10.2 cd under /mnt/server but im not sure what commands to pass to rsync.

I do not want to do it as a cron job, as i will be updating according to the changelog and when network traffic is light.

the mirror i would like to use is ftp.mirror.ac.uk

Thanks in advance
 
Old 08-26-2006, 01:21 PM   #2
ryanoa
Member
 
Registered: Jan 2006
Location: Santa Cruz, CA
Distribution: Slack 10.2 and 11.0
Posts: 102

Rep: Reputation: 15
Copying the files from your cd to some directory would be a good idea as it would reduce the amount of download time. Just make sure it has the same directory structure as the mirror.

For that mirror the command would be:

rsync -avu --delete ftp.mirror.ac.uk::ftp.slackware.org/slackware-current /nnn/

replace nnn with the directory you copied the contents of the cd to.

The --delete flag will remove the old files from your side that have been updated


Edit: added the -u flag

Last edited by ryanoa; 08-26-2006 at 01:26 PM.
 
Old 08-26-2006, 01:35 PM   #3
KaYoS
Member
 
Registered: May 2006
Posts: 32

Original Poster
Rep: Reputation: 15
Thank you for the quick reply, however when i try it i get this error

Code:
@ERROR: Unknown module 'ftp.slackware.org'
rsync error: error starting client-server protocol (code 5) at main.c(1171)
so im still stuck!

EDIT: it needs to be ftp.slackware.com, not .org!!!

Last edited by KaYoS; 08-26-2006 at 01:37 PM.
 
Old 08-26-2006, 01:52 PM   #4
ryanoa
Member
 
Registered: Jan 2006
Location: Santa Cruz, CA
Distribution: Slack 10.2 and 11.0
Posts: 102

Rep: Reputation: 15
Sorry about that, I guess I read through their module list a little too quickly.
 
Old 10-17-2007, 03:06 AM   #5
digitalboy74
Member
 
Registered: Aug 2004
Location: Matrix
Distribution: slack currrent
Posts: 61

Rep: Reputation: 16
see also

http://www.slackware.com/~alien/tools/rsync_current.sh
 
Old 10-21-2007, 03:26 AM   #6
simcox1
Member
 
Registered: Mar 2005
Location: UK
Distribution: Slackware
Posts: 794
Blog Entries: 2

Rep: Reputation: 30
Here's my rsync script. It excludes certain things as you can see. kde kdei pasture and source. Slackware.com is not a very fast mirror, so using something else like osuosl is much quicker.

#!/bin/sh
#
rsync -rlptD -z -v \
--exclude pasture --exclude slackware/kde --exclude slackware/kdei \
--exclude source \
--delete --delete-excluded \
rsync.osuosl.org::slackware/slackware-current/ \
/home/simon/rsync/slackware-current/
 
Old 10-22-2007, 12:58 AM   #7
MS3FGX
Guru
 
Registered: Jan 2004
Location: NJ, USA
Distribution: Slackware, Debian
Posts: 5,852

Rep: Reputation: 351Reputation: 351Reputation: 351Reputation: 351
Quote:
1. Copy all the packages from my Slackware 11 cd (when it arrives) to /mnt/server
Do you mean Slackware 12 here? Basing your mirror off of a Slack 11 CD would work, but you really won't save yourself that much bandwidth, almost everything was changed from Slackware 11 to 12.
 
Old 10-22-2007, 07:03 AM   #8
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Rep: Reputation: 52
Read the date of the first post. digitalboy74 dredged up an old post. He meant Slackware 11...
 
Old 10-22-2007, 09:56 AM   #9
MS3FGX
Guru
 
Registered: Jan 2004
Location: NJ, USA
Distribution: Slackware, Debian
Posts: 5,852

Rep: Reputation: 351Reputation: 351Reputation: 351Reputation: 351
Ah, so he did.
 
Old 10-22-2007, 10:45 PM   #10
MannyNix
Member
 
Registered: Dec 2005
Location: ~
Distribution: Slackware -current, OpenBSD
Posts: 449

Rep: Reputation: 41
Quote:
Originally Posted by simcox1 View Post
Here's my rsync script...
Thank you simcox1, i think it's great. Based on your script i'm trying to make my own, i'm interested in being able to sync from slackware-current/source, is there a way to avoid downloading the sources? (i'd only like to get: slack-desc, SlackBuilds and patches, etc, but not the sources for compiling the programs) Here's my "slack-sync.sh"
All tips are welcome, thanks!
Code:
#!/bin/sh
CWD=`pwd`
rsync -rlptD -z -v \
--exclude=*.tar.bz2 \
rsync.osuosl.org::slackware/slackware-current/source/ \
$CWD
Edit: Seems: --exclude=*.tar.bz2 \ worked. fixes welcomed.

Nice, a ports-like system

Last edited by MannyNix; 10-22-2007 at 10:56 PM.
 
Old 10-23-2007, 12:06 AM   #11
indeliblestamp
Member
 
Registered: Feb 2006
Distribution: Fedora
Posts: 341
Blog Entries: 3

Rep: Reputation: 38
Okay, I have a dumb doubt here. Once you have a local mirror of -current, how often do you people do an upgradepkg */*tgz? Once a month? Once a release?
I found a nice link for upgrading between releases (I've only been doing reinstalls since 10.2), and it does look a little tedious.
So do people usually upgrade only critical packages and leave the rest for later?
 
Old 10-23-2007, 03:53 AM   #12
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,223

Rep: Reputation: Disabled
It makes little sense to have a local mirror of Slackware-current and then not use it. It wastes your bandwidth.
If you do follow the development in -current, the best thing is to check the ChangeLog.txt daily (or at least weekly) and apply the changes listed in the ChangeLog.
This can mean: upgrade packages, remove packages, change configuration files, etc... it all depends. Usually, a snapshot of slackware-current at any given day will either contain bugs (that you may or may not have encountered) or misses functionality that keep the tree from being promoted to a "stable" release. All in all, you should not stick for too long with a snapshot of slackware-current installed on your system.

Eric
 
Old 10-23-2007, 04:03 AM   #13
indeliblestamp
Member
 
Registered: Feb 2006
Distribution: Fedora
Posts: 341
Blog Entries: 3

Rep: Reputation: 38
That's very good info, thanks. I think I'll lurk around at the Changelogs page and stick with upgrading packages I'm familiar with (or seem important) to start with.
 
Old 10-23-2007, 04:41 AM   #14
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,223

Rep: Reputation: Disabled
It also makes little sense to pick individual packages for upgrade... either you keep current with the development of Slackware (which means act on every update in the ChangeLog) or stick with a stable release of Slackware (and keep that one up[-to-date by following the bugfixes that get added to the /patches directory over time... there is a slackware-security mailing list you can subscribe to if you want to be kept informed of updates).

If you need newer versions of individual packages for your Slackware machine but don't want to be on the bleeding edge, it may be better to download the sources including the SlackBuild script and build yourself a package. That way, you can be certain the package works for your system.

Eric
 
Old 10-23-2007, 05:25 AM   #15
indeliblestamp
Member
 
Registered: Feb 2006
Distribution: Fedora
Posts: 341
Blog Entries: 3

Rep: Reputation: 38
Very well, I think your second recommendation suits me better (stick with stable and upgrade just the security patches). I've subscribed to slackware-security as well now, thanks again for the advice.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Keeping local requests local carcassonne Linux - Networking 4 07-28-2006 05:31 PM
Keeping FreeBSD 4.10-stable (current) vaworx *BSD 20 05-02-2005 10:38 PM
Local mirror for Clamav razametal Linux - Software 1 02-03-2005 08:22 AM
Creating Local Update Mirror wyohman Mandriva 9 12-28-2003 08:03 AM
Mirror of current changelog? Coldfirex Slackware 3 02-04-2003 07:30 AM


All times are GMT -5. The time now is 06:33 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration