From: Vagrant C. <va...@fr...> - 2009-01-23 22:26:02
|
On Fri, Jan 23, 2009 at 02:49:12PM -0500, Rob Owens wrote: > On Mon, Jan 19, 2009 at 10:18:45AM -0800, Vagrant Cascadian wrote: > > committed to the Debian plugins: > > > > http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/annotate/head%3A/server/plugins/ltsp-build-client/Debian/010-http-proxy > > > > should work on older versions too, just drop the file into > > /usr/share/ltsp/plugins/ltsp-build-client/Debian (or > > /etc/ltsp/plugins/ltsp-build-client). > > > > you can use --http-proxy to specify it from the commandline, or it will > > autodetect it from your /etc/apt/apt.conf* settings. --no-guess-proxy > > will disable autodetection. > > > That worked great! I like the autodetect feature. glad to hear it! > A few notes: > > 1) My lenny installation doesn't have /etc/ltsp/plugins (I imagine it would be a symlink to /usr/share/ltsp/plugins, but it's not there) yes, the /etc/ltsp/plugins directory is entirely optional, so it is not created by default. plugins in /etc/ltsp/plugins/ will override corresponding plugins in /usr/share/ltsp/plugins, so there's no point in symlinking it to /usr/share/ltsp/plugins. /etc/ltsp/plugins is intended to be used by admins to override behavior of a specific plugin in in /usr/share/ltsp/plugins. > 2) I put my proxy information in /etc/apt/apt.conf, because that's where the > installer puts it. Some people create /etc/apt/apt.conf.d/01proxy, and put > their proxy information in there. I tested both methods with the autodetect > feature, and both worked. yes, it uses apt-config, instead of parsing configuration files manually. > 3) I removed my proxy information from apt.conf* and used the --http-proxy option. That worked as well. glad it helps. i've been meaning to write that plugin for ages. thanks for giving me the impetus to actually sit down and write it. live well, vagrant |