|
|
| Applications |
| Mailing Lists |
| Miscellaneous |
| Operating Systems |
| Programming |
debian-user-digest Digest V2007 #3013
Date: Sun Dec 16 2007 - 14:29:41 EST
Content-Type: text/plain
debian-user-digest Digest Volume 2007 : Issue 3013
Today's Topics:
Re: How to disable ipv6 in Lenny to [ "Amogh Hooshdar" <amoghhooshdar@gma ]
How to Configure Aptitude for Update [ "Geoff Sanders" <sanders.geoffrey@g ]
Date: Mon, 17 Dec 2007 00:03:36 +0530
From: "Amogh Hooshdar" <amoghhooshdar@gmail.com>
To: "Thilo Six" <T.Six@gmx.de>
Cc: debian-user@lists.debian.org
Subject: Re: How to disable ipv6 in Lenny to avoid 1.0.0.0 error in name resolution for AAAA type queries
Message-ID: <78c462ad0712161033y504931ffoc7a006edda1cd33b@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
I raised this question in the debian-ipv6 list. Here is the thread:- http://lists.debian.org/debian-ipv6/2007/12/msg00001.html Got one solution of installing my own bind9 named which works.
On Dec 15, 2007 7:38 PM, Thilo Six <T.Six@gmx.de> wrote:
> Amogh Hooshdar wrote the following on 15.12.2007 14:10
> > Thank you for response. But it did not help. I commented out all the
> > ip6 lines in /etc/hosts and then even rebooted the box.
> >
> > Now see a sample output for aptitude update:-
> >
> > # aptitude update
> > 0% [Connecting to ftp.us.debian.org (1.0.0.0)] [Connecting to security.debian.or
> >
> > I observed it with wireshark and the DNS queries and responses are like this:-
> >
> > DNS Standard query AAAA ftp.us.debian.org
> > DNS Standard query response [Malformed packet]
> > DNS Standrd query A ftp.us.debian.org
> > DNS Standard query response A 1.0.0.0
> >
> > ipv6 doesn't seem to have been disabled because the DNS AAAA type
> > queries are still going out. Please help me to disable ipv6
> > completely.
>
> are yo using KDE?
>
> <-------- grep IP /etc/environment --------
>
> KDE_NO_IPV6=1
> --------------------------------------------->
>
> basically i do not understand how the machine can still do ipv6 when there is
> no kernel modul loaded. ?
>
> Have you got resolvconf or any local dns[proxy|cache] installed?
>
> I just found there is also a list especial for ipv6:
>
> http://lists.debian.org/debian-ipv6/
>
> bye
> --
>
> Thilo
>
> key: 0x4A411E09
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
Date: Sun, 16 Dec 2007 13:07:08 -0600
From: "Geoff Sanders" <sanders.geoffrey@gmail.com>
To: debian-user@lists.debian.org
Subject: How to Configure Aptitude for Update Archive Compression Types?
Message-ID: <bca855f20712161107o74a6b495k43ec2c3d441e1679@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="----=_Part_6518_12192769.1197832028874"
------=_Part_6518_12192769.1197832028874
Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
I'm experiencing an issue with aptitude regarding archive compression types during update. Currently, I have two installed systems (etch stable) that retrieve different update archive types. One system retrieves Packages.bz2, where the other system retrieves Packages.gz during 'aptitude update' (discovered using apt-get --print-uris update). Unfortunately, the *.bz2 archives are producing an md5sum mismatch error on one system, but the *.gz archives do not. Where can I configure apt/aptitude to update using a specific archive type for update/install (*.bz2 or *.gz), and why does one system request updates via Packages.bz2, while the other does it using Packages.gz? I have not configured either system in any particular way for archive updates, and they both point at the same repos for updates and installs. I've looked both through documentation and lists, with no answers to this issue. Assistance is much appreciated.
TIA ------=_Part_6518_12192769.1197832028874
Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
I'm experiencing an issue with aptitude regarding archive compression types during update. Currently, I have two installed systems (etch stable) that retrieve different update archive types. One system retrieves Packages.bz2 , where the other system retrieves Packages.gz during 'aptitude update' (discovered using apt-get --print-uris update). Unfortunately, the *.bz2 archives are producing an md5sum mismatch error on one system, but the *.gz archives do not. Where can I configure apt/aptitude to update using a specific archive type for update/install (*.bz2 or *.gz), and why does one system request updates via Packages.bz2, while the other does it using Packages.gz? I have not configured either system in any particular way for archive updates, and they both point at the same repos for updates and installs. I've looked both through documentation and lists, with no answers to this issue. Assistance is much appreciated. <br><br>TIA<br>
------=_Part_6518_12192769.1197832028874--
End of debian-user-digest Digest V2007 Issue #3013
Received on Sun Dec 16 14:30:02 2007
This archive was generated by hypermail 2.1.8 : Wed Mar 19 2008 - 02:58:05 EDT
|
Contact Us Legal Notices Order Services Online Pantek Home Privacy Policy IT news Site Map Pantek Library |