[clc-devel] rsync files ready
Hi, If you want to get the rsync ports, you can do the following: 1. install rsync 2. get the ports driver from http://www.karsikkopuu.net/crux/misc/rsync 3. move the driver to /etc/ports/drivers and make it executable 4. get http://jw.tks6.net/files/crux/core.rsync http://jw.tks6.net/files/crux/opt.rsync http://jw.tks6.net/files/crux/contrib.rsync 5. mkdir /usr/ports/rsync 6. run ports -u This should give you tthe latest ports in /usr/ports/rsync. Regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net
--- Johannes Winkelmann wrote:
This should give you tthe latest ports in /usr/ports/rsync.
Worked great, and it's very fast. Nice work, guys. Sorry for the 2x mail, cptn - I accidentally fired off my first response to just you ;) Jay Dolan Software Engineer, Systems Analyst Windmill Cycles, Inc. 508.999.4000 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
On Wed, 7 Dec 2005 22:37:32 +0100 Johannes Winkelmann wrote:
Hi, Hi Johannes.
If you want to get the rsync ports, you can do the following:
1. install rsync 2. get the ports driver from http://www.karsikkopuu.net/crux/misc/rsync 3. move the driver to /etc/ports/drivers and make it executable 4. get http://jw.tks6.net/files/crux/core.rsync http://jw.tks6.net/files/crux/opt.rsync http://jw.tks6.net/files/crux/contrib.rsync 5. mkdir /usr/ports/rsync 6. run ports -u
This should give you tthe latest ports in /usr/ports/rsync.
I did all that,and it works great,quicker,IMHO, than with svn repo. A question,if I may. After checkout I get the following : -- Error: Couldn't chroot into /usr/ports/rsync/opt (Operation not permitted) Updating failed --- Same error with contrib,core and contrib-test. Since I'm using Han's pkgutils,I run ports -u as non-root,and all directories under /usr/ports are owned by that user(all permissions are OK,AFAICT). I don't get that error with either cvsup or httup backend. This line from rsync driver trigers it: --- # use chroot as an additional safety measure when removing files chroot($destination) or error("Couldn't chroot into $destination"); chdir('/'); --- How can I resolve this?Is there a workaround? man chroot isn't very helpful :-( How does this chroot thingie work,anyway? Other than that,great work,as always,from CLC crew,thank you <g>
Regards, Johannes
Pedja -- "Hell, just simulate the first unicellular organisms, then have it run four billion years in a minute, and you have instant humans! (Assuming you simulated the rest of the universe correctly.)"
Hi Pedja, On Fri, Dec 09, 2005 at 00:06:20 +0100, Predrag Ivanovic wrote:
On Wed, 7 Dec 2005 22:37:32 +0100 Johannes Winkelmann wrote:
Hi, Hi Johannes.
If you want to get the rsync ports, you can do the following: [...] This should give you tthe latest ports in /usr/ports/rsync.
I did all that,and it works great,quicker,IMHO, than with svn repo. Good to hear. I'm also quite impressed by the speed.
A question,if I may. After checkout I get the following : -- Error: Couldn't chroot into /usr/ports/rsync/opt (Operation not permitted) Updating failed --- Same error with contrib,core and contrib-test. Since I'm using Han's pkgutils,I run ports -u as non-root,and all directories under /usr/ports are owned by that user(all permissions are OK,AFAICT). Okay; well, I
I don't get that error with either cvsup or httup backend. This line from rsync driver trigers it: --- # use chroot as an additional safety measure when removing files chroot($destination) or error("Couldn't chroot into $destination"); chdir('/'); --- How can I resolve this? Is there a workaround? You're the first to report that (and it's good to learn about this now before we switch), thanks.
man chroot isn't very helpful :-( man 2 chroot describes the system call if you look for details
How does this chroot thingie work,anyway? Basically, it just uses /usr/ports/opt as its new root, which is a really effective way to make sure we don't accidently remove other files (since they're not accessible from within this chroot environment). We'll try to find a better solution for it soon, stay tuned :-).
Other than that,great work,as always,from CLC crew,thank you <g> Thank you!
Best regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net
Johannes Winkelmann wrote:
On Fri, Dec 09, 2005 at 00:06:20 +0100, Predrag Ivanovic wrote:
[...]
A question,if I may. After checkout I get the following : -- Error: Couldn't chroot into /usr/ports/rsync/opt (Operation not permitted) Updating failed --- Same error with contrib,core and contrib-test. Since I'm using Han's pkgutils,I run ports -u as non-root,and all directories under /usr/ports are owned by that user(all permissions are OK,AFAICT).
Basically, it just uses /usr/ports/opt as its new root, which is a really effective way to make sure we don't accidently remove other files (since they're not accessible from within this chroot environment). We'll try to find a better solution for it soon, stay tuned :-).
Hi Pedja, I've prepared a new driver file which falls back to plain old chdir() and path validation when running as a normal user. Can you put this to /etc/ports/drivers/rsync and see if it fixes your problem: http://www.karsikkopuu.net/crux/misc/rsync Regards, Jukka
On Sat, 10 Dec 2005 18:32:04 +0200 Jukka Heino wrote: <snip>
Hi Pedja,
I've prepared a new driver file which falls back to plain old chdir() and path validation when running as a normal user. Can you put this to /etc/ports/drivers/rsync and see if it fixes your problem: http://www.karsikkopuu.net/crux/misc/rsync
Works great,thanks :-)
Regards, Jukka
Pedja -- 'Cluids' - def: "Fluids having the effect of restoring or imparting Clue. Eg; beer, coffee,etc." --Dan Holdsworth
Hi, Unfortunately, we didn't consider remember to support different versions of crux in our *.rsync files... changed now. On Wed, Dec 07, 2005 at 22:37:32 +0100, Johannes Winkelmann wrote:
Hi,
If you want to get the rsync ports, you can do the following:
1. install rsync 2. get the ports driver from http://www.karsikkopuu.net/crux/misc/rsync 3. move the driver to /etc/ports/drivers and make it executable 4. get http://jw.tks6.net/files/crux/core.rsync http://jw.tks6.net/files/crux/opt.rsync http://jw.tks6.net/files/crux/contrib.sync I uploaded a new version of those files; please update your local copies.
Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net
Hi, On Fri, Dec 09, 2005 at 20:10:36 +0100, Johannes Winkelmann wrote:
Hi, [...] I uploaded a new version of those files; please update your local copies. In addition, there are httpup repos at http://www.crux.nu/ports/crux-2.1/core and http://www.crux.nu/ports/crux-2.1/opt
Enjoy, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net
On Wed, 7 Dec 2005 22:37:32 +0100 Johannes Winkelmann wrote:
Hi, Hi Johannes.
If you want to get the rsync ports, you can do the following:
1. install rsync 2. get the ports driver from http://www.karsikkopuu.net/crux/misc/rsync 3. move the driver to /etc/ports/drivers and make it executable 4. get http://jw.tks6.net/files/crux/core.rsync http://jw.tks6.net/files/crux/opt.rsync http://jw.tks6.net/files/crux/contrib.rsync 5. mkdir /usr/ports/rsync 6. run ports -u
This should give you tthe latest ports in /usr/ports/rsync.
I did all that,and it works great,very fast,even on dialup. A question,if I may. After checkout I get the following : -- Error: Couldn't chroot into /usr/ports/rsync/opt (Operation not permitted) Updating failed --- Same error with contrib,core and contrib-test. Since I'm using Han's pkgutils,I run ports -u as non-root,and all directories under /usr/ports are owned by that user(all permissions are OK,AFAICT). I don't get that error with either cvsup or httup backend. This line from rsync driver trigers it: --- # use chroot as an additional safety measure when removing files chroot($destination) or error("Couldn't chroot into $destination"); chdir('/'); --- After I commented out this line,I did a checkout again,everything works fine. How does this chroot thingie work,anyway? Is commenting out this line a Bad Idea[tm]? Other than that minor issue,great work,as always,from CLC crew,thank you <g>
Regards, Johannes
Pedja -- "Hell, just simulate the first unicellular organisms, then have it run four billion years in a minute, and you have instant humans! (Assuming you simulated the rest of the universe correctly.)"
participants (5)
-
Jay Dolan -
Johannes Winkelmann -
Jonathan Asghar -
Jukka Heino -
Predrag Ivanovic