On 21 mars 2005, at 00:21, Donald Arseneau wrote:
Viv Kendon <[EMAIL PROTECTED]> writes:
using (say) rsync tunneling through ssh? It looks (from the man pages) like
it ought to be possible, but rsync needs some extra flags, and I can't find a
way to give them to fink...
e.g., updating from the remote server,
rsync -a --rsh=ssh [EMAIL PROTECTED]:remote/path/ local/path
If you run this unattended, you should set up your ssh keys to allow this remote connection without password (or passphrase).
I am not sure if I understood the original question correctly, but I thought it was about access to a bindist server, that is, what to put into sources.list so that apt-get (and FinkCommander) can understand it for fetching *.debs.
In the man pages for sources.list, they talk about "the rsh/ssh method" which seems to imply that something like
deb ssh://ssh-server.leeds.ac.uk:/fink stable main crypto
should be possible. I think this is a long-standing lie in these man pages, and it never worked. It actually says there also:
"The currently recognized URI types are cdrom, file, http, and ftp."
This is more accurate. So if you don't have access to your server via http or ftp at all, you are out of luck.
You can, however, forget about apt-get and just clone the whole fink hierarchy. This can be done via rsync over ssh, as Donald explained.
If you are allowed to run a web server that can be seen at least locally, even just from the machine where it runs (it can use a non-standard port, for example), then you can export this via an ssh tunnel, and then you can use the standard Fink/apt-get tools.
For example, suppose you run, on your bindist server, a web server that listens on port 16080, and suppose you can access this machine via ssh. Then you can open an ssh tunnel from you local machine
ssh [EMAIL PROTECTED] -N -L 20080:bindist.server.int.uk:16080 &
(here bindist.server.ext.uk is the address of that machine as seen by you or the address of your ssh access point, and bindist.server.int.uk is the address of the bindist server as seen by itself or from the ssh access point. These two addresses can be different even if it's the same machine, because they can be on different networks)
While this ssh tunnel is active, you can have lines
deb http://localhost:20080/fink stable main crypto deb http://localhost:20080/fink unstable main crypto
in your /sw/etc/apt/sources.list and then access the bindist automatically. For apt-get, this looks like the bindist were on your own machine, with a web server listening on port 20080.
-- Martin
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
