Re: apt-get problem
Quoting "Douglas A. Tutty" <[EMAIL PROTECTED]>: On Fri, Jan 04, 2008 at 06:32:52PM -0600, Don Montgomery wrote: Hello, I am having a problem with apt-get (please see below). (I have noted no other network problems: browser and ssh work fine.) I am not sure what is supposed to go on with localhost. Any ideas? Thanks in advance, Don [EMAIL PROTECTED]:/home/don# apt-get update Err http://security.debian.org testing/updates Release.gpg Could not connect to localhost:4001 (127.0.0.1). - connect (111 Connection refused) Err http://security.debian.org testing/updates/main Translation-en_US Could not connect to localhost:4001 (127.0.0.1). - connect (111 Connection refused) It looks like your apt is trying to connect via an http proxy on localhost at port 4001 and is unable to. Does your browser connect via a proxy? ssh uses a different port so wouldn't be involved in a proxy issue. For completeness, give us your /etc/apt/sources.list. I don't know where proxies are set up for apt. /etc/apt/apt.conf might contain some settings, and most likely the place for a proxy. Cheers, Mike
Re: debugging xchat with gdb
On 2 Jan 2008, [EMAIL PROTECTED] wrote: >> gdb xchat >> (no debugging symbols found) >> Using host libthread_db library "/lib/libthread_db.so.1". >> (gdb) >> >> How come gdb won't launch xchat? What's it waiting for? > GDB is waiting your command. so, you need to type "r". You might also be able to debug better if you compiled an xchat with debugging symbols. apt-get source xchat and build your own version. -- Alok Trying to define yourself is like trying to bite your own teeth. -- Alan Watts -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apt-get problem
On Fri, Jan 04, 2008 at 06:32:52PM -0600, Don Montgomery wrote: > Hello, > > I am having a problem with apt-get (please see below). > (I have noted no other network problems: browser and ssh > work fine.) I am not sure what is supposed to go on with > localhost. Any ideas? > > Thanks in advance, Don > > [EMAIL PROTECTED]:/home/don# apt-get update > Err http://security.debian.org testing/updates Release.gpg > Could not connect to localhost:4001 (127.0.0.1). - > connect (111 Connection refused) > Err http://security.debian.org testing/updates/main > Translation-en_US > Could not connect to localhost:4001 (127.0.0.1). - > connect (111 Connection refused) It looks like your apt is trying to connect via an http proxy on localhost at port 4001 and is unable to. Does your browser connect via a proxy? ssh uses a different port so wouldn't be involved in a proxy issue. For completeness, give us your /etc/apt/sources.list. I don't know where proxies are set up for apt. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
apt-get problem
Hello, I am having a problem with apt-get (please see below). (I have noted no other network problems: browser and ssh work fine.) I am not sure what is supposed to go on with localhost. Any ideas? Thanks in advance, Don [EMAIL PROTECTED]:/home/don# apt-get update Err http://security.debian.org testing/updates Release.gpg Could not connect to localhost:4001 (127.0.0.1). - connect (111 Connection refused) Err http://security.debian.org testing/updates/main Translation-en_US Could not connect to localhost:4001 (127.0.0.1). - connect (111 Connection refused) Err http://security.debian.org testing/updates/contrib Translation-en_US Could not connect to localhost:4001 (127.0.0.1). - connect (111 Connection refused) Err http://security.debian.org testing/updates/non-free Translation-en_US Could not connect to localhost:4001 (127.0.0.1). - connect (111 Connection refused) Err http://debian.uchicago.edu testing Release.gpg Could not connect to localhost:4001 (127.0.0.1). - connect (111 Connection refused) Err http://debian.uchicago.edu testing/main Translation-en_US Could not connect to localhost:4001 (127.0.0.1). - connect (111 Connection refused) Err http://debian.uchicago.edu testing/contrib Translation-en_US Could not connect to localhost:4001 (127.0.0.1). - connect (111 Connection refused) Err http://debian.uchicago.edu testing/non-free Translation-en_US Could not connect to localhost:4001 (127.0.0.1). - connect (111 Connection refused) Failed to fetch http://debian.uchicago.edu/debian/dists/testing/Release.gpg Could not connect to localhost:4001 (127.0.0.1). - connect (111 Connection refused) Failed to fetch http://debian.uchicago.edu/debian/dists/testing/main/i18n/Translation-en_US.bz2 Could not connect to localhost:4001 (127.0.0.1). - connect (111 Connection refused) Failed to fetch http://debian.uchicago.edu/debian/dists/testing/contrib/i18n/Translation-en_US.bz2 Could not connect to localhost:4001 (127.0.0.1). - connect (111 Connection refused) Failed to fetch http://debian.uchicago.edu/debian/dists/testing/non-free/i18n/Translation-en_US.bz2 Could not connect to localhost:4001 (127.0.0.1). - connect (111 Connection refused) Failed to fetch http://security.debian.org/dists/testing/updates/Release.gpg Could not connect to localhost:4001 (127.0.0.1). - connect (111 Connection refused) Failed to fetch http://security.debian.org/dists/testing/updates/main/i18n/Translation-en_US.bz2 Could not connect to localhost:4001 (127.0.0.1). - connect (111 Connection refused) Failed to fetch http://security.debian.org/dists/testing/updates/contrib/i18n/Translation-en_US.bz2 Could not connect to localhost:4001 (127.0.0.1). - connect (111 Connection refused) Failed to fetch http://security.debian.org/dists/testing/updates/non-free/i18n/Translation-en_US.bz2 Could not connect to localhost:4001 (127.0.0.1). - connect (111 Connection refused) Reading package lists... Done W: Some index files failed to download, they have been ignored, or old ones used instead. [EMAIL PROTECTED]:/home/don# -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to wifi with ipw3945 on Dell Vostro ???
Helge Hafting wrote: Joost Kraaijeveld wrote: Hi, I am running Debian Lenny on a Dell Vostro laptop which has a ipw3945 wifi card. The card is recognised by the software and it even works somehow (I can see all the wifi networks in my building using wifi-radar). But whatever I do I cannot get a (DHCP) ip address from my Zyxel AP which is using a WEP key (and it did when I still used Windows Vist so I know for a fact that it is possible). You need: * A driver module. If you use the 2.6.22-3 kernel from debian testing, install the ipw3945-modules-2.6.22-3-amd64 package. Then make sure that /etc/modules contains a line with "ipw3945 You probably have this already, or you wouldn't be able to use the card at all. * The package ipw3945d. Install it and make sure the daemon is running, or the card won't work properly. Without this, the card will seem ok but anything you do will fail silently and mysteriously. After that, set it up to associate with your access point. For a quick test, use iwconfig directly. For a permanent setup, put something like this in /etc/network/interfaces: iface eth2 inet dhcp pre-up iwconfig eth2 essid YOURSSID key YOURKEY (Assuming the card is eth2. Use "key off" if there is no encryption. If there is WPA encryption, get additional software for supporting WPA. Get the card working on a open or WEP encrypted net first, to rule out driver problems. WPA is trickier to set up than WEP) Hexadecimal keys are easiest to deal with, as there are two incompatible ways of specifying the key as a text string. The driver uses one way, some access points use the other way. Hex is more typing but works everytime. Also make sure you have a package with dhcp software, for example dhcp3-client Helge Hafting Thought I'd throw in a suggestion that you look into the iwlwifi driver. Intel has moved on to the next "best thing". The iwl driver doesn't require the stupid daemon (a big step). And my initial impression is that it will probably support WEP/WPA more effectively. I haven't used WEP/WPA with it yet but it's on my agenda. I haven't had any issues since I switched from iwp to iwlwifi. http://intellinuxwireless.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: chroot question [* SOLVED *]
On Jan 4, 2008 8:56 AM, Heikki Levanto <[EMAIL PROTECTED]> wrote: > On Fri, Jan 04, 2008 at 11:20:31AM +, A J Stiles wrote: > > I successfully invoked the 32-bit firefox using > > $ iceweasel -a firefox32 > > from within the chroot while simultaneously running a 64-bit instance. > > Flash, > > Java &c. work fine. > > I will have to set up something like that too. Is there a good (up to date!) > page somewhere on the net that explains what I need? Can I use my old root > disk partition as the chroot environment, Yes and still boot to it natively if I > really need some 32-bit stuff? Yes > > Sorry for the newbie questions. > > - Heikki > > -- > Heikki Levanto "In Murphy We Turst" heikki (at) lsd (dot) dk > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- Perhaps the depth of love can be calibrated by the number of different selves that are actively involved in a given relationship. Carl Sagan (Contact) Jaime Ochoa Malagón Integrated Technology Tel: (55) 52 54 26 10
Re: chroot question [* SOLVED *]
On Fri, Jan 04, 2008 at 03:56:57PM +0100, Heikki Levanto wrote: > On Fri, Jan 04, 2008 at 11:20:31AM +, A J Stiles wrote: > > I successfully invoked the 32-bit firefox using > > $ iceweasel -a firefox32 > > from within the chroot while simultaneously running a 64-bit instance. > > Flash, > > Java &c. work fine. > > I will have to set up something like that too. Is there a good (up to date!) > page somewhere on the net that explains what I need? Can I use my old root > disk partition as the chroot environment, and still boot to it natively if I > really need some 32-bit stuff? > > Sorry for the newbie questions. Under what conditions would you need to boot the 32-bit chroot natively? I have never needed to, so my chroot is uner /srv/chroot/etch-ia32. I put /srv on its own LV (I use LVM over raid1). I used debootstrap to install the chroot following (loosly) the instructions in the amd64 howto from the debian website. I access the chroot with $ schroot -pc etch-ia32 which means that I have the schroot package installed on the amd64 system. Once debootstrap gives you a basic system, you schroot into it, run aptitude, and setup what you want. Treat it like its own machine. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: chroot question [* SOLVED *]
On Fri, Jan 04, 2008 at 11:20:31AM +, A J Stiles wrote: > I successfully invoked the 32-bit firefox using > $ iceweasel -a firefox32 > from within the chroot while simultaneously running a 64-bit instance. > Flash, > Java &c. work fine. I will have to set up something like that too. Is there a good (up to date!) page somewhere on the net that explains what I need? Can I use my old root disk partition as the chroot environment, and still boot to it natively if I really need some 32-bit stuff? Sorry for the newbie questions. - Heikki -- Heikki Levanto "In Murphy We Turst" heikki (at) lsd (dot) dk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to wifi with ipw3945 on Dell Vostro ???
Joost Kraaijeveld wrote: Hi, I am running Debian Lenny on a Dell Vostro laptop which has a ipw3945 wifi card. The card is recognised by the software and it even works somehow (I can see all the wifi networks in my building using wifi-radar). But whatever I do I cannot get a (DHCP) ip address from my Zyxel AP which is using a WEP key (and it did when I still used Windows Vist so I know for a fact that it is possible). You need: * A driver module. If you use the 2.6.22-3 kernel from debian testing, install the ipw3945-modules-2.6.22-3-amd64 package. Then make sure that /etc/modules contains a line with "ipw3945 You probably have this already, or you wouldn't be able to use the card at all. * The package ipw3945d. Install it and make sure the daemon is running, or the card won't work properly. Without this, the card will seem ok but anything you do will fail silently and mysteriously. After that, set it up to associate with your access point. For a quick test, use iwconfig directly. For a permanent setup, put something like this in /etc/network/interfaces: iface eth2 inet dhcp pre-up iwconfig eth2 essid YOURSSID key YOURKEY (Assuming the card is eth2. Use "key off" if there is no encryption. If there is WPA encryption, get additional software for supporting WPA. Get the card working on a open or WEP encrypted net first, to rule out driver problems. WPA is trickier to set up than WEP) Hexadecimal keys are easiest to deal with, as there are two incompatible ways of specifying the key as a text string. The driver uses one way, some access points use the other way. Hex is more typing but works everytime. Also make sure you have a package with dhcp software, for example dhcp3-client Helge Hafting -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: chroot question [* SOLVED *]
On Thursday 03 Jan 2008, Peter Makholm wrote: > A J Stiles <[EMAIL PROTECTED]> writes: > > If I already have 64-bit Iceweasel running, and try to start 32-bit > > Iceweasel from inside the chroot, I get another instance of the 64-bit > > browser. If I kill the 64-bit browser, I can start a 32-bit one. If I > > then try to start a 64-bit Iceweasel from the K menu while the 32-bit > > Iceweasel is running, I get another 32-bit Iceweasel. > > You can try to use the -a switch to iceweasel such that the two > iceweasels runs with different application-id's. If that works you can > make an alias for iceweasel inside you chroot to use a non-default > application-id. Thanks for your help! I successfully invoked the 32-bit firefox using $ iceweasel -a firefox32 from within the chroot while simultaneously running a 64-bit instance. Flash, Java &c. work fine. So next, I edited the script .../usr/lib/iceweasel/iceweasel (inside the chroot) so the default application ID is now firefox32. This is what I changed: # WAS # APPLICATION_ID=firefox # NOW # APPLICATION_ID=firefox32 # ENDS # Hope someone else finds this useful. -- AJS delta echo bravo six four at earthshod dot co dot uk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
