I'm recently trying to install alpha-3 image using l-m-c on an AMD64 machine which is behind the company firewall. Though I have apt proxy set on host machine, l-m-c installing system (chroot env?) does not know it. Can we improve the l-m-c a little bit to copy apt proxy setting if any on host machine into installing system? So that the machine behind proxy can survive with l-m-c too.
PS. Actually, I have my machine home which can directly access natty repository, but it's very slow (see below), probably because there is no natty mirror in China yet.
Fetched 15.0 MB in 10min 22s (24.1 kB/s)
When I use vpn to connect company network, speed of accessing ubuntu repository can reach ~200 kB/s. Considering that I'm testing l-m-c back and forth, I really need a faster apt speed within l-m-c.
On 8 March 2011 17:19, Shawn Guo shawn.guo@freescale.com wrote:
I'm recently trying to install alpha-3 image using l-m-c on an AMD64 machine which is behind the company firewall. Though I have apt proxy set on host machine, l-m-c installing system (chroot env?) does not know it. Can we improve the l-m-c a little bit to copy apt proxy setting if any on host machine into installing system? So that the machine behind proxy can survive with l-m-c too.
PS. Actually, I have my machine home which can directly access natty repository, but it's very slow (see below), probably because there is no natty mirror in China yet.
Did you try to switch apt source to China in the updater-manager? Can this work: http://ubuntu.cn99.com/ubuntu/dists/
Fetched 15.0 MB in 10min 22s (24.1 kB/s)
When I use vpn to connect company network, speed of accessing ubuntu repository can reach ~200 kB/s. Considering that I'm testing l-m-c back and forth, I really need a faster apt speed within l-m-c.
-- Regards, Shawn
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
On Tue, Mar 08, 2011, Shawn Guo wrote:
I'm recently trying to install alpha-3 image using l-m-c on an AMD64 machine which is behind the company firewall. Though I have apt proxy set on host machine, l-m-c installing system (chroot env?) does not know it. Can we improve the l-m-c a little bit to copy apt proxy setting if any on host machine into installing system? So that the machine behind proxy can survive with l-m-c too.
Sounds like https://bugs.launchpad.net/linaro-image-tools/+bug/673570
On Tue, Mar 8, 2011 at 10:53 AM, Loïc Minier loic.minier@linaro.org wrote:
On Tue, Mar 08, 2011, Shawn Guo wrote:
I'm recently trying to install alpha-3 image using l-m-c on an AMD64 machine which is behind the company firewall. Though I have apt proxy set on host machine, l-m-c installing system (chroot env?) does not know it. Can we improve the l-m-c a little bit to copy apt proxy setting if any on host machine into installing system? So that the machine behind proxy can survive with l-m-c too.
Sounds like https://bugs.launchpad.net/linaro-image-tools/+bug/673570
yes, thats the proxy problem. But, fwiw, l-m-c shouldn't even try to access the net if the hwpacks has the debs included, see:
https://bugs.launchpad.net/linaro-image-tools/+bug/716479
On Tue, Mar 08, 2011 at 11:04:08AM +0100, Alexander Sack wrote:
On Tue, Mar 8, 2011 at 10:53 AM, Loïc Minier loic.minier@linaro.org wrote:
On Tue, Mar 08, 2011, Shawn Guo wrote:
I'm recently trying to install alpha-3 image using l-m-c on an AMD64 machine which is behind the company firewall. Though I have apt proxy set on host machine, l-m-c installing system (chroot env?) does not know it. Can we improve the l-m-c a little bit to copy apt proxy setting if any on host machine into installing system? So that the machine behind proxy can survive with l-m-c too.
Sounds like https://bugs.launchpad.net/linaro-image-tools/+bug/673570
yes, thats the proxy problem. But, fwiw, l-m-c shouldn't even try to access the net if the hwpacks has the debs included, see:
In that case, l-m-c becomes a very nice tool :)
On Tue, Mar 08, 2011 at 10:53:00AM +0100, Loïc Minier wrote:
On Tue, Mar 08, 2011, Shawn Guo wrote:
I'm recently trying to install alpha-3 image using l-m-c on an AMD64 machine which is behind the company firewall. Though I have apt proxy set on host machine, l-m-c installing system (chroot env?) does not know it. Can we improve the l-m-c a little bit to copy apt proxy setting if any on host machine into installing system? So that the machine behind proxy can survive with l-m-c too.
Sounds like https://bugs.launchpad.net/linaro-image-tools/+bug/673570
Yes, it is. Do we have a quick fix right now? I need it ...
On Tue, Mar 08, 2011, Shawn Guo wrote:
Yes, it is. Do we have a quick fix right now? I need it ...
As a workaround, try disabling your (host's) network entirely before running linaro-media-create; I could run it completely networkless, but I think your proxy is confusing APT.
On Tue, Mar 08, 2011 at 11:53:08AM +0100, Loïc Minier wrote:
On Tue, Mar 08, 2011, Shawn Guo wrote:
Yes, it is. Do we have a quick fix right now? I need it ...
As a workaround, try disabling your (host's) network entirely before running linaro-media-create; I could run it completely networkless, but I think your proxy is confusing APT.
That's not an option for me. Myself is on ssh terminal. I do not have a nice monitor for that machine :)
On Tue, Mar 08, 2011, Shawn Guo wrote:
That's not an option for me. Myself is on ssh terminal. I do not have a nice monitor for that machine :)
Ok; I could propose various network tricks such as changing the routing table to mark your APT repo unreachable, but I guess we really have to fix support for proxies and/or offline.
Hello Guilherme,
On Tue, Mar 08, 2011 at 10:53:00AM +0100, Loïc Minier wrote:
On Tue, Mar 08, 2011, Shawn Guo wrote:
I'm recently trying to install alpha-3 image using l-m-c on an AMD64 machine which is behind the company firewall. Though I have apt proxy set on host machine, l-m-c installing system (chroot env?) does not know it. Can we improve the l-m-c a little bit to copy apt proxy setting if any on host machine into installing system? So that the machine behind proxy can survive with l-m-c too.
Sounds like https://bugs.launchpad.net/linaro-image-tools/+bug/673570
I'm see you have a comment at the #12 floor of above page, saying you have a patch for this limitation. Can you please share it? Otherwise I really can not continue the l-m-c testing in office.
With old version l-m-c, I simply copied file /etc/apt/apt.conf.d/proxy from host machine into chroot path at proper place where l-m-c gets the new root ready and is about to change root. But with the latest l-m-c installed from ppa, this exact place seems not easy for me to catch.
Thanks.
On Wed, Mar 09, 2011 at 08:53:50PM +0800, Shawn Guo wrote:
Hello Guilherme,
On Tue, Mar 08, 2011 at 10:53:00AM +0100, Loïc Minier wrote:
On Tue, Mar 08, 2011, Shawn Guo wrote:
I'm recently trying to install alpha-3 image using l-m-c on an AMD64 machine which is behind the company firewall. Though I have apt proxy set on host machine, l-m-c installing system (chroot env?) does not know it. Can we improve the l-m-c a little bit to copy apt proxy setting if any on host machine into installing system? So that the machine behind proxy can survive with l-m-c too.
Sounds like https://bugs.launchpad.net/linaro-image-tools/+bug/673570
I'm see you have a comment at the #12 floor of above page, saying you have a patch for this limitation. Can you please share it? Otherwise I really can not continue the l-m-c testing in office.
With old version l-m-c, I simply copied file /etc/apt/apt.conf.d/proxy from host machine into chroot path at proper place where l-m-c gets the new root ready and is about to change root. But with the latest l-m-c installed from ppa, this exact place seems not easy for me to catch.
Just to update the thread, Loic and Guilherme sent me the patch on IRC and it works for me.
-
Alexander Sack -
Loïc Minier -
Shawn Guo -
Spring Zhang